Selectable packet-switched and circuit-switched services in a mobile communications network
Abstract
(57) [Summary] Applications running on mobile stations or external network entities such as Internet service providers can specify the required quality of service on an individual application flow basis. The quality of service requested determines the type of bearer that is best suited to transfer the application flow over the mobile communications network. For example, circuit-switched bearers can be assigned if the request is for a real-time service, and packet-switched bearers can be assigned if the request is for a non-real-time type service. Various other criteria can be adopted. Mobile station and mobile network gateway nodes each include a mapper that maps individual application flows to either a circuit-switched network or a packet-switched network, depending on the quality of service required for the individual application flows. The network layer quality of service parameters for individual application flows are mapped to circuit-switched bearer parameters if the application flow is mapped to a circuit-switched network, and to the circuit-switched bearer parameter if the application flow is mapped to a packet-switched network. Maps to circuit-switched bearer parameters. A gateway node is a single common access for mobile stations to first establish a communication session with an external network entity and then use either a circuit-switched network or a packet-switched network for subsequent communication. Includes a common access server that allows you to carry out the procedure. After the common access procedure is complete, a simplified procedure is used to establish a subsequent application flow between the mobile station and the external network entity without the need to access the external network entity.
Term
Term ended
Projected expiry passed 15 September 2018, 8 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
1 claim: 1 independent, 0 dependent
- 1【特許請求の範囲】 【請求項1】 回線交換(CS)サービスとパケット交換(PS)サービスとを提供する移動体通信ネットワークにおける方法であって、 前記移動局が、アプリケーションと関連づけられた複数のフローが移動局と外部ネットワーク・エンティティとの間で通信される前記移動体通信ネットワークとの通信を確立するステップと、 前記複数のアプリケーションフローのそれぞれについて、前記移動局から前記外部ネットワーク・エンティティに向けて、回線交換ベアラ又はパケット交換ベアラのいずれが確立されるべきかを判断するステップと、 前記判断されたベアラを前記複数のアプリケーションフローのそれぞれに割り当てるステップとを含むことを特徴とする方法。 【請求項2】 前記各アプリケーションフローは対応するサービス品質の要求に関連づけられており、 前記複数のアプリケーションフローのそれぞれについて、対応する要求されたサービス品質に基づいて、回線交換ベアラ又はパケット交換ベアラのいずれが前記アプリケーションフローを運ぶのにより適しているかを判断するステップを含むことを特徴とする請求項1に記載の方法。 【請求項3】 前記アプリケーションフローについて、前記移動体通信ネットワークにおいて入手可能なリソースを予約して、前記要求されたサービス品質ならびに回線交換ベアラとパケット交換ベアラのうち選択された方をサポートするステップを更に含むことを特徴とする請求項2に記載の方法。 【請求項4】 回線交換ベアラ又はパケット交換ベアラのいずれを使用してパケットを搬送すべきかを示す標識を、前記アプリケーションフローにおける情報の各パケットに含めるステップと、 各パケットの標識に基づいて、各パケットを搬送するために前記回線交換ベアラと前記パケット交換ベアラのうち一方を選択するステップと更にを含むことを特徴とする請求項3に記載の方法。 【請求項5】 アプリケーションフローにリソースが予約された場合に、前記標識は前記アプリケーションフローにおける全てのパケットについて同じであることを特徴とする請求項4に記載の方法。 【請求項6】 前記標識は、同じサービス・クラスの全てのパケットがクラス標識によって判断されるタイプのベアラ上で搬送される、複数のサービス・クラスの1つに基づいたクラス標識であることを特徴とする請求項4に記載の方法。 【請求項7】 移動局に提供される回線交換ベアラ・サービスとパケット交換ベアラ・サービスの両方に関する課金情報を記憶する課金記録を確立するステップを更に含むことを特徴とする請求項1に記載の方法。 【請求項8】 前記複数のアプリケーションフローのそれぞれについて、前記アプリケーションフローがリアルタイム・タイプのサービスを要求するか非リアルタイム・タイプのサービスを要求するかを判断するステップと、 前記要求がリアルタイム・タイプのサービスに関するものである場合には回線交換ベアラを割り当て、前記要求が非リアルタイム・タイプのサービスに関するものである場合にはパケット交換ベアラを割り当てるステップとを更に含むことを特徴とする請求項1に記載の方法。 【請求項9】 パケット交換ベアラを割り当てて、セッション制御操作情報を含むアプリケーションフローを搬送するステップを更に含むことを特徴とする請求項8に記載の方法。 【請求項10】 リアルタイム・サービスはオーディオサービス及びビデオサービスの一方又は両方を含み、非リアルタイム・サービスはファイル転送アプリケーション、eメール・アプリケーション、ワールド・ワイド・ウェブからの情報検索アプリケーション及びテレメトリ・アプリケーションの1つ又は複数を含むことを特徴とする請求項8に記載の方法。 【請求項11】 前記アプリケーションフローが低遅延又は小ジッタを要求する場合には回線交換ベアラを割り当て、前記アプリケーションフローが高速チャンネル・アクセス又はバースティ・データ転送能力を要求する場合にはパケット交換ベアラを割り当てるステップを更に含むことを特徴とする請求項1に記載の方法。 【請求項12】 前記複数のアプリケーションフローのそれぞれについて、送信される情報量とセットアップ遅延感度を判断するステップと、 大量の情報が送信される場合又は前記アプリケーションフローがセットアップ遅延に対して感度がない場合に、回線交換ベアラを割り当てるステップと、 上記以外の場合に、パケット交換ベアラを割り当てるステップとを更に含むことを特徴とする請求項1に記載の方法。 【請求項13】 個々のアプリケーションフローにより要求された複数のサービス品質パラメータを検出するステップと、 異なったレベルの重要度を前記サービス品質パラメータの個別のパラメータに割り当てるステップと、 より高い重要度を有するサービス品質パラメータに優先順位を与えるベアラを判断するステップとを更に含むことを特徴とする請求項1に記載の方法。 【請求項14】 前記移動局は1回に1タイプのベアラだけを送信又は受信できるクラスBの移動局であり、 アプリケーションフローについて前記移動局への回線交換ベアラが存在するかどうかを判断するステップと、 もし存在すれば、前記既存の回線交換ベアラ上でパケット交換情報を送信するステップとを更に含むことを特徴とする請求項1に記載の方法。 【請求項15】 前記外部ネットワークはインターネットであり、前記外部ネットワーク・エンティティはインターネット・サービス・プロバイダ(ISP)であって、 前記移動局と関連づけられた異なったアプリケーションフローを搬送するために、回線交換ベアラとパケット交換ベアラが個別に割り当てられた前記移動体通信ネットワークにおいて、リンク層のサービスをネットワーク層に提供するステップを更に含むことを特徴とする請求項1に記載の方法。 【請求項16】 前記アプリケーションは、各アプリケーションフローについて回線交換ベアラを選択すべきかパケット交換ベアラを選択すべきかを判断し、前記選択されたベアラを前記IPリンク層サービスに要求することを特徴とする請求項15に記載の方法。 【請求項17】 前記IPリンク層サービスは、前記移動局の、前記ISPとインターフェイスする移動体ネットワーク・ゲートウェイ・ノードで提供されることを特徴とする請求項16に記載の方法。 【請求項18】 前記移動局は、回線交換サービスとパケット交換サービスとの両方についてチャンネルを監視することを特徴とする請求項1に記載の方法。 【請求項19】 前記移動局は、1回に前記回線交換サービスと前記パケット交換サービスの一方のみ又は両方で動作することを特徴とする請求項18に記載の方法。 【請求項20】 回線交換移動体ネットワークとパケット交換移動体ネットワークとを含む移動体通信システムにおける方法であって、 前記移動局が、前記移動局と外部ネットワーク・エンティティとの間で、それぞれが対応するサービス品質の要求を有する複数のアプリケーションフローが通信される、前記移動体通信ネットワークでの通信セッションを確立するステップと、 前記個々のアプリケーションフローのそれぞれに対応するサービス品質に応じて、前記アプリケーションフローの個々のフローを前記回線交換ネットワークと前記パケット交換ネットワークの一方にマップするステップとを含むことを特徴とする方法。 【請求項21】 前記マップするステップは、 前記回線交換ネットワークが選択された場合に、回線交換ネットワーク・リンクを前記アプリケーションフローに割り当てるステップと、 前記パケット交換ネットワークが選択された場合に、パケット交換ネットワーク・リンクを前記アプリケーションフローに割り当てるステップとを更に含むことを特徴とする請求項20に記載の方法。 【請求項22】 前記アプリケーションフローが前記回線交換ネットワークにマップされた場合には、対応する個々のアプリケーションフローについて要求されたサービス品質パラメータを回線交換パラメータにマップし、前記アプリケーションフローが前記パケット交換ネットワークにマップされた場合には、対応する個々のアプリケーションフローについて要求されたサービス品質パラメータをパケット交換パラメータにマップするステップを更に含むことを特徴とする請求項20に記載の方法。 【請求項23】 前記移動体通信システムはGSMシステムであり、前記回線交換ネットワークはGSM回線交換ネットワークであり、前記パケット交換ネットワークはGSM・GPRSネットワークであることを特徴とする請求項20に記載の方法。 【請求項24】 回線交換移動体ネットワークとパケット交換移動体ネットワークとを含む移動体通信システムにおける方法であって、 移動局が、アプリケーションの複数のフローが前記移動局と外部ネットワーク・エンティティとの間で通信される、前記移動体通信ネットワークとの通信セッションの確立を開始するステップと、 前記回線交換ネットワークと前記パケット交換ネットワークの両方について、前記移動局と前記外部ネットワーク・エンティティとの間で共通アクセス手順を遂行するステップとを含み、 前記共通アクセス手順の後に、前記複数のアプリケーションフローの後続の1つが、前記外部ネットワーク・エンティティを関与させるもう1つのアクセス手順を遂行することなく、前記移動局と前記外部ネットワーク・エンティティとの間に確立されることを特徴とする方法。 【請求項25】 前記共通アクセス手順は、その後、前記移動局が、前記回線交換ネットワークと前記パケット交換ネットワークの両方を通して、前記外部ネットワーク・エンティティとの前記複数のアプリケーションフローのうち後続のフローについて許可される、前記移動局のアイデンティティを前記外部ネットワーク・エンティティと認証する共通認証手順を含むことを特徴とする請求項24に記載の方法。 【請求項26】 前記共通認証手順は、前記移動局のIDとパスワードを確認して、前記移動局が前記外部ネットワーク・エンティティと通信しそのサービスを利用することを許可されているかどうか判断するステップを含むことを含むことを特徴とする請求項25に記載の方法。 【請求項27】 前記後続のアプリケーションフローについて、前記移動体ネットワークにおいて簡略化された認証手順のみが遂行されることを特徴とする請求項25に記載の方法。 【請求項28】 前記共通アクセス手順は、その後、前記移動局は前記回線交換ネットワークと前記パケット交換ネットワークとの両方を通して前記外部ネットワーク・エンティティとの前記複数のアプリケーションフローのうち後続のフローについて、共通ネットワーク・アドレスで環境設定される、前記移動局を前記外部ネットワーク・エンティティと環境設定する共通環境設定手順を含むことを特徴とする請求項24に記載の方法。 【請求項29】 前記共通環境設定手順は、 前記移動局に、前記外部ネットワーク・エンティティによって前記移動局に割り当てられたネットワーク層アドレスを含む、外部ネットワーク・エンティティとの通信に必要なパラメータを提供するステップと、 前記パラメータを前記移動体通信ネットワークに記憶するステップとを含み、 前記セッションの間、前記移動局を関与させる後続のアプリケーション・ストリームについて、前記方法は、前記外部ネットワーク・エンティティを関与させることなく、前記後続のアプリケーション・ストリームを環境設定するために前記記憶されたパラメータを検索するステップを更に含むことを特徴とする請求項28に記載の方法。 【請求項30】 前記移動体通信システムは前記外部ネットワーク・エンティティとインターフェイスするためのゲートウェイ・ノードを含み、 前記方法は、 前記移動局を前記ゲートウェイ・ノードに登録するステップと、 前記移動局が前記移動局と前記外部ネットワーク・エンティティとの間の端末間環境設定を要求するステップとを含み、 前記端末間環境設定の要求は、前記移動ホストと前記ゲートウェイ・ノードとの間にネットワーク層ベアラを確立して、ネットワーク層アドレスが前記移動ホストに割り当てられていなくても前記外部ネットワーク・エンティティと前記移動ホストとの間のデータ・パケットの中継を可能にすることを特徴とする請求項24に記載の方法。 【請求項31】 前記ゲートウェイ・ノードは、クライアントとしての前記移動局にサービスするダイナミック・ホスト・コンフィギュレーション・リレー・エージェントとして機能し、前記移動局と前記外部ネットワーク・エンティティとの間で情報を中継することを特徴とする請求項30に記載の方法。 【請求項32】 移動局識別子に対応するリモート・エージェントIDを前記外部ネットワーク・エンティティに向けられたメッセージに付加するステップを更に含むことを特徴とする請求項31に記載の方法。 【請求項33】 環境設定の間、前記ダイナミック・ホスト・コンフィギュレーション・エージェントは、前記確立されたセッションに関する前記移動局用の独特なネットワーク層アドレスと、前記確立されたセッションの間に作動される全てのアプリケーションフローを捕獲して記憶することを特徴とする請求項32に記載の方法。 【請求項34】 前記ネットワーク層ベアラに対応するデータ通信トンネルを、前記ゲートウェイ・ノードと前記移動局との間に確立するステップと、 移動局の識別子、前記確立されたトンネル及び、前記確立されたセッションに関する前記移動局用の前記ネットワーク層アドレスとの間に前記ゲートウェイ・ノードにおける関係を確立するステップとを更に含むことを特徴とする請求項33に記載の方法。 【請求項35】 回線交換移動体ネットワークとパケット交換移動体ネットワークとを含む移動体通信システムにける方法であって、 前記移動局が、アプリケーションの複数のフローが前記移動局と外部ネットワーク・エンティティとの間で通信される、前記移動体通信ネットワークとの通信セッションの確立を開始するステップと、 前記回線交換ネットワークと前記パケット交換ネットワークの両方について前記移動局の共通認証手順を遂行し、前記移動体通信システムと前記外部ネットワーク・エンティティへのアクセス及びそれらの使用について前記移動局を認証するステップとを含み、 前記共通認証手順の後に、前記外部ネットワーク・エンティティを関与させるもう1つの認証手順を遂行することなく、後続のアプリケーションフローを前記外部ネットワーク・エンティティとの間に確立することを特徴とする方法。 【請求項36】 前記移動体通信システムにおけるノードでの前記共通認証手順から得られる1つ又は複数のパラメータを記憶するステップと、 前記後続のアプリケーションフローについて、前記記憶された1つ又は複数のパラメータを前記後続のアプリケーションフローに関連づけられた認証要求と比較するステップとを更に含み、 前記比較が適合するという結果になった場合に、前記後続のアプリケーションフローは認証されることを特徴とする請求項35に記載の方法。 【請求項37】 回線交換移動体ネットワークとパケット交換移動体ネットワークとを含む移動体通信システムにおける方法であって、 前記移動局が、アプリケーションの複数のフローが前記移動局と外部ネットワーク・エンティティとの間で通信される、前記移動体通信ネットワークとの通信セッションの確立を開始するステップと、 前記回線交換ネットワークと前記パケット交換ネットワークの両方について、前記外部ネットワーク・エンティティとの前記移動局の共通環境設定手順を遂行し、前記外部ネットワーク・エンティティとの通信のために前記移動局を環境設定するステップとを含み、 前記共通環境設定手順の後に、前記外部ネットワーク・エンティティを関与させるもう1つの環境設定手順を遂行することなく、後続のアプリケーションフローを前記外部ネットワーク・エンティティとの間に確立することを特徴とする方法。 【請求項38】 前記移動体通信システムにおけるノードでの前記共通環境設定手順から得られる1つ又は複数のパラメータを記憶するステップと、 前記後続のアプリケーションフローについて、前記記憶された1つ又は複数のパラメータを前記後続のアプリケーションフローに関連づけられた環境設定要求と比較するステップとを更に含み、 前記比較が適合するという結果になった場合に、前記後続のアプリケーションフローは環境設定されることを特徴とする請求項37に記載の方法。 【請求項39】 前記1つ又は複数のパラメータは、前記外部ネットワーク・エンティティからのIPアドレス、ドメイン・ネーム・サーバ識別子、ワールドワイド・ウェブ・サーバ識別子及び会議ゲートキーパを含むことを特徴とする請求項38に記載の方法。 【請求項40】 アプリケーションに関連づけられた複数のフローを備えたアプリケーションを有する移動局と、 前記アプリケーションフローのそれぞれに関連づけられたサービスのタイプに応じて、前記移動局とゲートウェイ・ノードの間で情報を搬送するために、前記複数のアプリケーションフローの1つを回線交換ベアラとパケット交換ベアラの一方にマップするマッパを含み、前記移動局が外部ネットワークにおける・エンティティと通信するのに通るゲートウェイ・ノードとを含むことを特徴とする外部ネットワークに接続された移動体通信システム。 【請求項41】 前記アプリケーションは、前記アプリケーションフローのそれぞれについてネットワーク層レベルでのサービス品質を指定し、 前記マッパは、前記アプリケーションフローに関連づけられたサービス品質に応じて、各アプリケーションフローを前記ベアラの一方にマップすることを特徴とする請求項40に記載の移動体通信システム。 【請求項42】 前記指定されたサービス品質が保証されたサービス品質である場合に、前記マッパは前記関連づけられたアプリケーションフローを前記回線交換ベアラにマップし、前記指定されたサービス品質が最善の努力サービス品質である場合に、前記マッパは前記関連づけられたアプリケーションフローを前記パケット交換ベアラにマップすることを特徴とする請求項41に記載の移動体通信システム。 【請求項43】 前記移動局は、前記アプリケーションフローのそれぞれに関連づけられたサービスのタイプに応じて、前記外部ネットワーク・エンティティから前記移動局への前記アプリケーションフローのそれぞれ1つを、前記回線交換ベアラと前記パケット交換ベアラの一方にマップするマッパを含むことを特徴とする請求項40に記載の移動体通信システム。 【請求項44】 回線交換ベアラに割り当てられた各アプリケーションフローについて、回線交換リンクが前記移動局と直接アクセス・ユニットとの間に確立される直接アクセス・ユニットを含む回線交換ネットワークと、 パケット交換ベアラに割り当てられた各アプリケーションフローについて、パケット交換リンクが前記移動局とサービング・ノードとの間に確立されるサービング・ノードを含むパケット交換ネットワークとを更に含むことを特徴とする請求項40に記載の移動体通信システム。 【請求項45】 回線交換トンネルが前記直接アクセス・ユニットと前記ゲートウェイ・ノードとの間に確立され、パケット交換トンネルが前記サービング・ノードと前記ゲートウェイ・ノードとの間に確立されることを特徴とする請求項44に記載の移動体通信システム。 【請求項46】 前記移動体通信システムはGSMであり、前記直接アクセス・ユニットは移動体交換センターで提供され、前記パケット交換ネットワークはGPRSネットワークであり、前記サービング・ノードはサービングサポートGPRSノード(SSGN)であり、前記ゲートウェイ・ノードはゲートウェイGPRSサポートノード(GGSN)であり、前記回線交換リンクは無線リンク・プロトコル接続であり、前記パケット交換リンクはリンク層接続であり、前記SSGNと前記GGSNとの間のトンネルはGPRSトンネリング・プロトコル(GTP)を採用しており、前記直接アクセス・ユニットと前記GGSNとの間のトンネルは層2トンネリング・プロトコル(L2TP)であることを特徴とする請求項45に記載の移動体通信システム。 【請求項47】 前記移動局は、回線交換サービス・ネットワークとパケット交換サービス・ネットワークとの同時登録をサポートするが、同時の回線交換トラフィックとパケット交換トラフィックはサポートしないクラスBの移動局であり、 回線交換ベアラがアプリケーションフローについて確立された場合に、パケット交換データが前記確立された回線交換ベアラ上で送信されることを特徴とする請求項40に記載の移動体通信システム。 【請求項48】 回線交換ベアラが解除された場合に、パケット交換データがパケット交換ベアラ上を前記クラスBの移動局に送信されることを特徴とする請求項47に記載の移動体通信システム。 【請求項49】 前記ゲートウェイ・ノードは、回線交換ベアラと前記パケット交換ベアラの両方について、前記外部ネットワーク・エンティティと前記移動局との間に通信を確立する共通アクセス・サーバを含むことを特徴とする請求項40に記載の移動体通信システム。 【請求項50】 前記移動局と前記外部ネットワーク・エンティティとの間に最初にセッションを確立するために、前記共通アクセス・サーバは、前記回線交換ネットワークと前記パケット交換ネットワークの両方について、前記移動局と前記外部ネットワーク・エンティティとの間で共通アクセス手順を遂行することを特徴とする請求項49に記載の移動体通信システム。 【請求項51】 前記共通アクセス手順の後に、前記外部ネットワークを関与させるもう1つのアクセス手順を遂行することなく、前記外部ネットワークとの間に後続のアプリケーションフローが確立されることを特徴とする請求項50に記載の移動体通信システム。 【請求項52】 前記共通アクセス・サーバは、前記移動局が、回線交換サービスとパケット交換サービスの両方について、前記外部ネットワークと前記複数のアプリケーションフローのうち後続の1つについて環境設定されるように、前記移動局を前記外部ネットワーク・エンティティと認証する共通認証手順を遂行することを特徴とする請求項49に記載の移動体通信システム。 【請求項53】 前記共通認証手順は、前記移動局のアイデンティティと、前記移動局が前記外部ネットワーク・エンティティと通信することを許可されているかどうかを確認する手順を含むことを特徴とする請求項52に記載の移動体通信システム。 【請求項54】 前記共通アクセス・サーバは、前記移動局と前記外部ネットワーク・エンティティとの間の共通移動認証手順の間に、移動局識別子とパスワードを記憶し、前記共通アクセス・サーバは前記記憶された情報を使ってアプリケーションフローのうち後続の1つを認証することを特徴とする請求項50に記載の移動体通信システム。 【請求項55】 前記共通アクセス・サーバが、後続のアプリケーションフローに関連づけられた前記移動局から受信した移動識別子及びパスワードが前記記憶された情報と適合すると判断した場合に、前記後続のアプリケーションフローは、前記外部ネットワーク・エンティティを関与させることなく許可されることを特徴とする請求項54に記載の移動体通信システム。 【請求項56】 前記共通アクセス手順は、前記移動局が、回線交換サービスとパケット交換サービスの両方について、前記外部ネットワーク・エンティティと後続のアプリケーションフローについて環境設定されるように、前記移動局を前記外部ネットワーク・エンティティと環境設定する共通環境設定手順を含むことを特徴とする請求項50に記載の移動体通信システム。 【請求項57】 前記共通環境設定手順において、前記共通アクセス・サーバは、前記移動局に、ネットワーク層アドレスを含む前記外部ネットワーク・エンティティと通信するのに必要な1つ又は複数のパラメータを提供し、前記1つ又は複数のパラメータを記憶し、前記セッションの間に前記移動局を関与させる後続のアプリケーション・ストリームについて、前記記憶されたパラメータを検索して、前記外部ネットワーク・エンティティを関与させることなく、前記後続のアプリケーションを環境設定することを特徴とする請求項56に記載の移動体通信システム。 【請求項58】 前記共通アクセス・サーバは、前記移動局と前記外部ネットワーク・エンティティとの間のダイナミック・コンフィギュレーション・リレー・エージェントとして機能することを特徴とする請求項57に記載の移動体通信システム。 【請求項59】 外部ネットワーク・エンティティに接続された回線交換ネットワーク及びパケット交換ネットワークを含む移動体通信システムにおいて使用する移動端末であって、 それぞれが対応するサービス品質と関連づけられた複数のアプリケーションフローを備えたアプリケーションと、 前記アプリケーションフローのそれぞれと関連づけられたサービスのタイプに応じて、回線交換ベアラとパケット交換ベアラの一方に前記アプリケーションフローの1つをマップするマッパとを含むことを特徴とする移動端末。 【請求項60】 前記アプリケーションは、前記アプリケーションフローのそれぞれに対してネットワーク層レベルでのサービス品質を指定し、 前記マッパは、前記アプリケーションフローに関連づけられたサービスの品質に応じて、前記ベアラの一方に各アプリケーションフローをマップすることを特徴とする請求項59に記載の移動端末。 【請求項61】 前記指定されたサービス品質が保証されたサービス品質である場合に、前記マッパは、前記関連づけられたアプリケーションフローを前記回線交換ベアラにマップし、前記指定されたサービス品質が最善努力のサービス品質である場合に、前記マッパは、前記関連づけられたアプリケーションフローを前記パケット交換ベアラにマップすることを特徴とする請求項60に記載の移動端末。
115 paragraphs, as filed
Description: TECHNICAL FIELD [Detailed description of the invention]
【0001】
[Related application]
This application claims the priority of US Provisional Patent Application No. 60 / 060,062 filed on September 25, 1997. This application is also related to the commonly assigned U.S. Patent Application No. 09 / 087,496 filed May 29, 1998, the disclosure of which is incorporated herein by reference. [0002]
[Technical Field of Invention]
The present invention relates to mobile communications, and more particularly to different services and features employed to establish and enhance communications between mobile stations and external network entities in mobile communications networks. [0003]
Background and Outline of the Invention
The main applications of most mobile wireless systems, such as the Global System for Mobile Communications (GSM), support only circuit-switched communications, where the normally guaranteed "fixed" line is dedicated to the user during a call. It was a mobile telephone system. However, packet-switched applications such as facsimile transmission and short message switching are becoming common in mobile networks. Examples of data applications include wireless personal computers, mobile offices, electronic money transfers, road traffic telemetry, field service businesses, and fleet management. These data applications are characterized by long-running "bursty" traffic in which relatively large amounts of data are transmitted at relatively short time intervals, followed by little or no data. [0004]
Bursty traffic can also be sent using circuit-switched channels, but the channels are reserved but not used, that is, there is no information sent or received by the user, long intervals between bursts. Because of this, such transmissions do not fully utilize the channel. From an efficiency standpoint, this is a waste of transmit resources, especially limited to wireless communications. However, from the viewpoint of customer service, the circuit-switched channel is not shared with other users, so that the user is basically guaranteed a certain quality of service. In addition to efficiency, it takes a relatively long time to establish and terminate a circuit-switched call compared to individual packet route assignments in a packet-switched session. In the situation of bursty traffic, packet-switched bearers make better use of communication bandwidth because communication resources are used only when there is data to send. Therefore, the communication channel is usually shared by many users. Another advantage is that packet-switched data services charge according to the amount of data actually transmitted and the quality of service of their communications, as opposed to time-based billing applied to circuit-switched connections. It makes it possible. [0005]
To provide such mobile data applications, packet-wired network services employ high-bandwidth, efficient, unconnected packet-switched data services. One example is General Packet Radio Service (GPRS), which is embedded in existing circuit-switched GSM networks. Another example is the Cellular Digital Packet Data (CDPD) network, which is used by incorporating it into an existing D-AMPS network. A major benefit to end users of mobile packet data services such as GPRS is that wireless PCs can transfer files, send and receive email over the Worldwide Web, and traditionally "surf" the Internet. To support internet-based applications. Conferencing and playback applications, including video and multimedia, are also important services supported by mobile networks. [0006]
Circuit-switched services are well known in mobile networks, but mobile packet-switched services are very new. Therefore, a brief description of the latter using GSM / GPRS as an example is given here. [0007]
FIG. 1 shows a mobile data service from the user's point of view in the context of the mobile communication system 10. The end user uses, for example, a mobile host 12 including a laptop computer 14 connected to a mobile terminal 16 to communicate data packets. The mobile host 12 is local through, for example, one or more routers 24, a packet data network 26, and a router 28 in the local area network 20 through a mobile packet data support node 22. -Communicates with the fixed computer terminal 18 built into the area network (LAN) 20. Of course, one of ordinary skill in the art will appreciate that this drawing is simplified in that the "path" is a logical path rather than an actual physical path or connection. In unconnected data packet communication between mobile host 12 and fixed terminal 18, packets are independently routed from source to destination and do not always follow the same path (although they can). [0008]
Therefore, independent packet route allocation and forwarding within the mobile network is supported by the mobile packet data support node 22 acting as a logical interface or gateway to the external packet network. Subscribers can send and receive data in terminal-to-terminal packet transfer mode without using any circuit-switched mode network resources. In addition, multiple two-point parallel applications are possible. For example, a mobile host, such as a mobile PC, could run video conferencing applications, email applications, fax applications, web browsing applications, and more at the same time. Video conferencing applications will typically require multiple data streams (hereinafter referred to as application flows). [0009]
FIG. 2 shows a more detailed mobile communication system that supports both circuit-switched and packet-switched communications and uses an example of a GSM mobile communication model that includes circuit-switched network 35 and packet-switched network 51. The mobile host 12, including the computer terminal 14 and the mobile radio 16, communicates on a wireless interface having one or more base stations (BS) 32. Each base station 32 is located in the corresponding cell 30. The plurality of base stations 32 are connected to a base station controller (BSC) 34 that manages the allocation and deallocation of radio resources and controls the delivery of mobile stations from one base station to another. The base station controller and its associated base stations are sometimes referred to as base station subsystems (BSS). BSC34 is a GSM circuit-switched network 35 that mediates circuit-switched communication with other networks 38 such as the Public Switched Telephone Network (PSTN) and Integrated Services Digital Network (ISDN). , Connected to Mobile Switching Center (MSC) 36. [0010]
The MSC36 is also connected to the Home Location Register (HLR) 42, Visitor Location Register (VLR) 44, and Authentication Center (AUC) 46 via the Signaling System Number 7 (SS7) Network 40. There is. The VLR44 has a database containing information about all mobile stations currently located at the corresponding location, as well as temporary subscriber information required by the MSC to service the mobile in its service area. ing. Normally, when a mobile station enters a visiting network or service area, the corresponding VLR44 requests data about the roaming mobile station from the mobile HLR, receives it, and stores that data. As a result, when the visiting mobile station joins the call, the VLR44 already has the information needed to set up the call. [0011]
HLR42 is a database node that stores and manages subscriptions. For each "home" mobile subscriber, the HLR will use the Mobile Station ISDN Number (MSISDN), which uniquely identifies the mobile telephone subscription in the PSTN numbering plan, and the signal transmission assigned to each subscriber in the mobile network. Includes permanent subscriber data such as the International Mobile Subscriber Identity (IMSI), which is a unique identity that is created. All network-related subscriber information is connected to the IMSI. The HLR42 also includes a list of services that the mobile subscriber is allowed to use, along with the current subscriber location number that corresponds to the address of the VLR currently serving the mobile subscriber. [0012]
Each BSC34 is a servicing GPRS support node (SGSN) 50 responsible for delivering packets to mobile stations within its service area and is also connected to a GSM packet-switched network that supports GPRS network 51. The gateway GPRS support node (GGSN) 54 acts as a logical interface to an external data packet network, such as the IP data network 56. The SGSN node 50 and the GGSN node 54 are connected by an intra PLMN / IP backbone 52. Therefore, between SGSN50 and GGSN54, the Internet Protocol (IP) is used as the backbone for forwarding data packets. [0013]
Within GPRS network 51, packets or protocol data units (PDUs) are encapsulated at the source GPRS support node and decapsulated at the destination GPRS support node. This encapsulation / decapsulation at the IP level between SGSN50 and GGSN54 is called "tunneling" in GPRS. The GGSN54 maintains the route assignment information used to "tunnel" the PDU to the SGSN50, which currently serves the mobile station. The general GPRS Tunnel Protocol (GTP) allows different underlying packet data protocols to be adopted even if they are not supported by all SGSNs. All GPRS user-related data required by the SGSN to perform route allocation and data transfer functions is accessed from the HLR 42 over the SS7 network 40. The HLR42 stores route allocation information, maps each PDP address to one or more GGSNs, and maps the IMSI to one or more Packet Data Protocols (PDPs). [0014]
Before the mobile host sends packet data to an external network such as the Internet Service Provider (ISP) 58 shown in Figure 2, the mobile host 12 "belongs" to (1) GPRS network 51. It must be informed of its existence, (2) create a packet data protocol (PDP) context, and establish a relationship with the GGSN54 for the external network being accessed by the mobile station. This affiliation procedure is performed between mobile host 12 and SGSN50 to establish a logical link. As a result, a temporary logical link identity is assigned to mobile host 12. The PDP context is established between the mobile host and the GGSN54. The choice of GGSN54 is based on the name of the external network to access. [0015]
One or more application flows (sometimes referred to as "route allocation contexts") can be established for a single PDP context through negotiations with GGSN54. The application flow corresponds to a stream of data packets that can be distinguished as associated with a particular host application. An example application flow is an email message from a mobile host to a fixed terminal. Another example of an application flow is a graphic file downloaded from a website. Both of these application flows are associated with the same mobile host and the same PDP context. [0016]
Packet-switched data communication is usually based on specific protocol procedures that are divided into different layers. Figure 3 shows a GPRS "transmission plane" modeled on a multi-layer protocol stack. Between the GGSN and SGSN, the GPRS Tunneling Protocol (GTP) tunnels the PDU through the GPRS backbone network 52 by encapsulating the PDU with route allocation information. The GTP header contains a tunnel termination identifier (TID) for two-point and multicast packets and a group identity (GID) for one-pair and multi-point packets. In addition, it contains a PDU type and a type field that specifies the quality of the service profile associated with the PDP context session. Under GTP, the well-known Transmission Control Protocol / User Diagram Protocol (TCP / UDP) and Internet Protocol (IP) are used as GPRS backbone network layer protocols. Ethernet, Frame Relay (FR) or Asynchronous Teller Mode (ATM) based protocols can be used for links and physical layers, depending on the operator's network architecture. [0017]
Between the SGSN and the mobile station / host, the Subnetwork Dependent Convergence Protocol (SNDCP) maps network-level protocol characteristics to basic logical link control (LLC), like multiple transmissions of network layer messages. Provides functionality for a single virtual logical connection, encryption, partitioning and compression. The Base Station System GPRS Protocol (BSSGP) is a flow control protocol that allows a base station system to start and stop PDUs sent by the SGSN. This ensures that the BSS is not flooded with packets, even if the wireless link capability is reduced, for example due to fading or other adverse conditions. Route assignment and quality of service information are also communicated. Frame relays and ATMs may be used to relay PDU frames on the physical layer. [0018]
Wireless communication between the mobile station and the GPRS network covers the functionality of the physical and data link layers. The physical layer is divided into a physical link sublayer (PLL) and a physical RF sublayer (RFL). RFL performs modulation and demodulation of physical waveforms and specifies carrier frequency, radio channel structure and raw channel data rate. The PLL provides services for information transfer over physical radio channels, including data unit framing, data coding, and detection / modification of physical media transmission areas. The data link layer is separated into two separate sublayers. The Radio Link Control / Medium Access Control (RLC / MAC) sublayer arbitrates access to shared physical radio media between multiple mobile stations and the GPRS network. RLC / MAC multiplexes data and signal information to perform contention solutions, service quality control and error handling. The logical link control (LLC) layer operates above the MAC layer and provides a logical link between the mobile station and the SGSN. [0019]
It is important to be able to provide a particular communication service with the required quality. For example, some multimedia applications, or even simple audio phone calls, require guarantees of transmission accuracy, reliability, and speed. In packet-switched communication, "best effort" is usually adopted, and no special attention is paid to guaranteeing delay or throughput. In general, the quality of service parameters is definitive (used for manual real-time applications), statistical (used for soft real-time applications), and best effort (not guaranteed). It can be qualitatively characterized in three service classes, including (everything else). Quantitative parameters include throughput (such as average or peak data rate), reliability, delay, and jitter corresponding to delay changes between the minimum and maximum delay times that a message incurs. [0020]
In the context of providing quality of service (QoS) in mobile data communications systems, one QoS approach is to assign specific priorities to each PDP context. However, this approach is inadequate. As mentioned above, each PDP context may have multiple application flows, and each application flow may have different needs. For example, real-time applications such as telephone systems require guaranteed low-latency services, while image video requires predictable delay services. More specifically, elastic applications such as bidirectional bursts, bidirectional mass transfers and asynchronous mass transfers require different degrees of best effort or as soon as possible delay service. [0021] [0021]
An important object of the present invention is a quality-based radio of service to support multiple application services, including audio, data and multimedia, where some of the applications can have multiple application flows running simultaneously. To provide internet access. In the case of Internet-intensive services, key service quality factors are the perceived transport link layer delay, jitter, bandwidth, and reliability. Rather than limiting the quality of service to a single PDP context, the present invention defines the quality of service for each individual application flow as described below and in the patent application above. Furthermore, the present invention makes it possible to select a particular type of transfer mechanism that is best suited to transfer individual application flows according to the quality of service requirements. [0022]
Network technology typically transfers data according to only one type of forwarding mechanism (either circuit-switched or packet-switched), even in GSM, which includes both circuit-switched and packet-switched networks that share the same wireless access interface. .. In the present invention, the optimum type of transfer service (circuit-switched transfer service or packet-switched transfer service) of a mobile communication network is specified on an individual application flow basis. Circuit-switched services can be selected for real-time (low latency and low jitter) application flows, such as audio and video. Packet-switched bearers are for non-real-time Internet-type data applications such as surfing, file transfer, email and telnet on the Worldwide Web, all of which require high-speed channel access and bursty data transfer capabilities. You can choose. [0023]
Originally, mobile stations register with mobile communication networks to establish communication with external network entities such as Internet Service Providers (ISPs). During that communication, the application can initiate different data streams or application flows (hereinafter referred to as application flows) between the mobile station and the external network entity. For each application flow, it is determined whether to establish a circuit-switched bearer or a packet-switched bearer. Beara "brings" or carries information from the mobile station through the mobile communication network to an external network entity and transports the information from the external network to the mobile station through the mobile communication network. [0024]
Each application flow can have a corresponding quality of service requirement. Based on the corresponding quality of service, it is determined whether a circuit-switched bearer or a packet-switched bearer is more suitable for carrying the application flow. The quality of service parameters specified by the application for each application flow are mapped to the corresponding quality of service parameters for the selected circuit-switched bearer or packet-switched bearer. Mobile communication resources and corresponding quality of service parameters for the selected bearer can be reserved in advance for each application flow (resource reservation approach). Alternatively, the header of each information packet in the application flow specifies a generally recognized class of service that determines whether a circuit-switched bearer or a packet-switched bearer carries the packet when read. It can also be (discriminatory service approach). [0025]
Various algorithms can be used to determine the type of bearer assigned to a particular application flow. For example, it is possible to determine whether an application flow requires a real-time service or a non-real-time service. Circuit-switched bearers are assigned when the request is for real-time services, and packet-switched bearers are assigned when the request is for non-real-time services. Other criteria may be adopted. For example, circuit-switched bearers are assigned when the application flow requires low latency or low jitter per packet, and packet-switched bearers are assigned when the application flow requires high-speed channel access or bursty data transfer capability. Can be done. Yet another approach may be to determine the amount of information transmitted and / or the duration of that flow for each application flow. Circuit-switched bearers can be assigned when large amounts of information are transmitted or when the life of the application flow is long. Otherwise, packet-switched bearers will be assigned. [0026]
It is preferable to employ packet-switched bearers to carry control information because both bearer allocation approaches are bursty and concise in nature and the setup and release times provided by packet-switched bearers are short. Although not done). On the other hand, when a circuit-switched bearer to a mobile station already exists for the application flow, the packet-switched type information is an existing circuit-switched information even if the information is more suitable for transfer on the packet-switched bearer. Can be transferred (because it exists) on the bearer. This approach is used with mobile stations that cannot terminate concurrent circuit-switched and packet-switched traffic, such as so-called Class B GPRS mobile stations. [0027]
A major advantage of the present invention is that applications running on external network entities such as mobile stations or Internet service providers can identify the required quality of service on an individual application flow basis and this information. Therefore, it is possible to select the type of bearer to be adopted when transferring the application flow through the mobile communication network. Both the quality of service characteristics for the application flow and the type of bearer / transfer mechanism can be selected at the application layer, which is advantageous because the application has the best inter-terminal visibility of communication. [0028]
Each mobile station and mobile network gateway node maps individual application flows to one of circuit-switched network bearers and packet-switched network bearers, depending on the quality of service required for each application flow. Including mapper. The quality of service parameters for individual application flows are also mapped to circuit-switched parameters if the application flow is mapped to a circuit-switched network and to packet-switched parameters if the application flow is mapped to a packet-switched network. Will be done. [0029]
The gateway node allows the mobile station to first establish a communication session with an external network entity and use either a circuit-switched network or a packet-switched network to perform only a single common access procedure for subsequent communications. Includes a common access server that allows you to. After the common access procedure is completed, a subsequent application flow between the mobile station and the external network entity is established without having to perform another access procedure involving the external network entity. [0030]
Common access procedures include common authentication procedures for authenticating mobile station identities with external network entities. The mobile station is then allowed subsequent application flows with external network entities for both circuit-switched and packet-switched networks. A common authentication procedure involves checking the mobile station's ID and password to determine if the mobile station is allowed to communicate with external network entities. [0031]
The common access procedure also uses the common environment setup procedure for setting up the mobile station environment with external network entities. The mobile station is then configured for both circuit-switched and packet-switched networks with a common network address for subsequent application flows with external network entities. A common configuration procedure involves providing the mobile station with the parameters necessary to communicate with an external network entity, including the network layer address assigned to the mobile station. The preference parameter finds the parameters stored by the Common Access Server for subsequent application streams that involved a mobile station during a session and allows subsequent application streams without involving external network entities. Stored by the Common Access Server to configure. [0032]
The present invention differs by allowing individual application flows to independently select (1) quality of service parameters and (2) the type of forwarding mechanism (either circuit-switched bearers or packet-switched bearers). Provide better service to different types of applications. At the same time, the common access procedure for all application flows in a session provides a much faster service. In fact, the authentication and configuration procedure between the mobile station and the Internet service provider can take up to 20 to 30 seconds to complete when using circuit-switched bearers. This large delay is even more burdensome if such access procedures must be performed for each of multiple application flows. Consider the length of delay associated with a conferencing application that requires multiple application flows to run at the same time. [0033]
These burdensome delays are eliminated in the present invention. In mobile registration, the initial authentication and environment setting procedure using packet-switched bearers takes less than half of the above 20 to 30 seconds. This authentication and configuration procedure is not performed for each subsequent individual application flow, further saving time. Instead, in just a few seconds, the Common Access Server performs a simplified authentication and configuration procedure for subsequent flows contained within the mobile communications network. [0034]
The aforementioned and other objects, features and advantages of the present invention will become apparent from the following description of preferred embodiments set forth in the accompanying drawings in which reference numerals refer to the same parts in all of the various figures. There will be. The drawings emphasize the illustration of the principles of the invention and are not necessarily drawn to a constant scale. [0035]
[Detailed explanation of drawings]
In the following description, clear details such as specific embodiments, hardware, techniques, etc. have been described in order to fully understand the present invention, without any limitation for purposes of explanation. However, it will be apparent to those skilled in the art that the invention can also be practiced in other embodiments that depart from these clear details. For example, a clear embodiment of the invention is described in the context of a GSM / GPRS cellular telephone network, but those skilled in the art will appreciate that the invention makes any movement using other mobile data communication architectures and / or protocols. It will be understood that it can be implemented in mobile communication systems. In other examples, detailed descriptions of well-known methods, interfaces, devices and signaling techniques have been omitted so as not to obscure the description of the invention with unnecessary details. [0036]
As already described above, each application flow contains a corresponding stream of data. For mobile stations to communicate with external network entities such as Internet Service Providers (ISPs), mobile stations use dial-out circuit-switched connections or through authenticated packet-switched tunnels. Communication with the network must be established. The present invention uses the latter approach to first establish an application session to avoid the set time required for dial-out calls. [0037]
In the GSM / GPRS example, the mobile station initiates a packet data protocol (PDP) context activation, registers with the mobile communication system, and initiates a data session. HLR42 in Figure 2 remembers the PDP context for each mobile subscriber in the corresponding subscription record. The PDP subscription record includes MSids such as subscribed quality of service profiles / parameters, subscribed external networks, and IMSI (International Mobile Subscriber Identity). When the mobile station belongs to the GPRS network, the mobile station subscription record is received by the HLR42. As a result of the PDP context activation, a network layer bearer is established between the mobile station and the gateway GPRS Support Node (GGSN) 54. [0038]
After PDP context activation, a network layer, such as IP, host configuration operation, is performed and network layer (IP) bearer communication is established between the mobile host and an external network entity such as an ISP. IP preferences relate to assigning network layer (IP) addresses to mobile stations, worldwide web (WWW) servers, domain name servers (DNS), Address Resolution Protocol (ARP) cache, etc. Includes setting default values. When the IP bearer between the mobile host and the GGSN established in PDP context activation is extended from the GGSN to the ISP, data packets can travel back and forth between the mobile station and the ISP's terminal system. [0039]
As mentioned above, an important object of the present invention is to provide quality-based wireless Internet access for services to simultaneously support multiple services, including audio, data and multimedia. Internet applications may require quality of service that specifies one or more of the following elements: That is, the recognized transport link layer delay, jitter, bandwidth and / or reliability. One or more of these quality elements of service can be better provided by certain types of bearers, depending on their value. Circuit-switched bearers are better suited to perform real-time services such as audio and video that require low latency and / or low jitter. Traditional Internet data applications such as WWW, file transfer, email and telnet are better served by packet-switched bearers that are better suited for high-speed channel access and bursty data transfer. [0040]
The present invention does not limit all application flows to a single quality of service and / or a single transfer mechanism, but an application uses a particular quality of service and a particular type of mobile network switching for each application flow. It provides mobile subscribers with great flexibility and a wide range of services by allowing them to choose a mechanism (circuit-switched bearer or packet-switched bearer). FIG. 4 shows the optimal bearer selection routine (block 60). Here, it is assumed that the mobile station is already registered in the mobile network, for example using the PDP context activation procedure described above (block 61). [0041]
After registration, multiple application flows are communicated between the mobile station and an external network entity such as the Internet Service Provider (ISP) shown in Figure 2. An application (such as a multimedia conference) requires one or more quality of service (QoS) parameters for one or more individual application flows (block 62). Based on the quality of service required for a particular application flow, choose the best one of the circuit-switched bearers and packet-switched bearers to carry that particular application flow (block 64). The quality of service parameters required for each application flow, including, for example, peak bit rate, bucket depth (maximum buffering requirements for flow), and delay per packet, are peaked, for example, in the case of packet-switched bearers. -Mapped to the bearer parameters of the selected bearer, including throughput, burst size, and delay class (block 66). As a result, each application stream receives the best service in terms of quality of service parameters and the type of transfer mechanism that is most suitable for carrying the type of information transferred in that particular application flow. [0042]
In general, a typical application with multiple application flows requesting communication between a mobile station and an external network entity such as an ISP will follow the example steps below. [0043]
(1) Mobile stations register using common access procedures for both circuit-switched bearer and packet-switched bearer communications at ISPs that use "low-cost" packet-switched bearer and full dynamic host configuration support. To do. After that, only a simplified authentication and configuration procedure is required for the subsequent complete application flow, as described in more detail below. [0044]
(2) Send an application control message using the packet-switched bearer service using the expected quality of service delay class. [0045]
(3) Adopt packet switching bearer service and make the best effort to transfer a large amount of data with quality of service delay class. [0046]
(4) Transfer audio or video components by adopting the low latency quality of service provided by circuit switching bearer service. [0047]
Figure 5 shows a protocol model that allows individual application streams to be served individually, rather than simply serving a single application. The protocol procedure shown in FIG. 5 can be performed at a mobile station and at a mobile communication network gateway node, such as a GSM / GPRS GGSN. Assuming that an application (eg, a conferencing or playback application) contains a control signal as well as multiple substantive application flows, the application has a service quality application programming in each application flow (including the control signal flow associated with the application). · Request the corresponding quality of service using the interface (API). WinSock 2.0 or Win32, which can be purchased from Microsoft, is a possible option for quality of service APIs. [0048]
Quality of service is then mapped towards IP reservation protocols such as RSVP established by the Internet Engineering Task Force (IETF). Reliable Transport Protocol (TCP) or Unreliable Transport Protocol (UDP) can be applied, depending on the nature of the application flow. Using bearer / link selection and the mapping layer of quality of service parameters according to the present invention, RSVP quality of service can be achieved by circuit-switched bearers supported by circuit-switched networks in mobile communication systems, or by packet-switched networks in mobile communication systems. Map to a supported circuit-switched bearer. [0049]
When RSVP quality of service requirements are mapped to circuit-switched or packet-switched bearers, the quality of service parameters specified for each individual application flow map to circuit-switched or packet-switched parameters, depending on the bearer type selection. Will be done. In circuit-switched networks, mapping of such quality of service parameters requires, for example, selecting the appropriate number of radio channels (eg, time slots in TDMA-based systems, spreading codes in CDMA systems, etc.). It is relevant to correspond to the bandwidth. In packet-switched networks, there are multiple options to consider to support quality of service at different protocol layers. [0050]
A generalized group of quality of service parameters can be defined for the transfer mechanism, which is called the bearer's quality of service profile. The quality of service profile of Beara can be used to determine the quality of service at the wireless link control layer, the logical link control layer at the packet-switched bearer in Figure 3, and the tunneling protocol (GTP) layer at GPRS. The quality of service between terminals can be established. The wireless link control layer is affected by the packet delay and reliability quality of the service parameters of the better quality of service profile, while the logical link control layer is also affected by the bit rate and precedence / priority information. The GPRS tunneling protocol between the GPRS serving and gateway nodes, SGSN and GGSN must ensure that the tunnel does not violate any of the parameters in the quality of service profile. This requirement is usually met because wireless links are the bottleneck of mobile communication system architectures. [0051]
The corresponding layers in the circuit-switched bearer of FIG. 6 are the wireless link protocol and the layer 2 tunneling protocol. The wireless link protocol allocates one or more time slots to mobile stations to allocate or change the bandwidth of circuit-switched connections. The wireless link protocol also provides a secondary choice of bearer service types within the scope of circuit-switched bearers. The bearer service type can be optimized for audio, video or data. For example, V.110 is optimized for data modems as shown in Figure 6. Bearer service types (audio, video or data) in circuit-switched bearers are roughly different in quality of service compared to individual QoS parameters in terms of reliability, delay and priority provided in packet-switched link-layer control. It can be seen as being. [0052]
The circuit-switched layer 2 tunneling protocol basically has the same role as the GPRS tunneling protocol in packet-switched bearers. That is, it tunnels calls between the gateway node and the mobile exchange center on the IP infrastructure. The control phase in the Layer 2 tunneling protocol contains all the information about a successful GSM circuit-switched call. In contrast to the GPRS tunneling protocol, which carries IP directly, the Layer 2 tunneling protocol carries IP packets in a point-to-point protocol (PPP). The addition of the two-point protocol is necessary for packet subdivision, call authentication, and environment settings for terminal functions already built into the GPRS tunneling protocol. [0053]
FIG. 7 shows a specific mobile application (4 application flows in total) with examples of 3 application flows including video application flow, audio application flow, and conferencing application flow, along with system control operation flow. .. Each flow has a quality of service associated with it recognized on the IP layer. At the transport layer, each application flow uses different coding and messaging protocols, if appropriate. Video and audio application flows are typically processed through codecs, such as H.263 / H.261 for video and GSM06.10 for audio, and Real-Time Transport Protocol (RTP) for delay-sensitive transport terminals. Encapsulated in. Application flows that contain control data about an application session, such as a conference session, do not require a codec, but instead require real-time session control (RTSP), session invitation (SIP), and session announcement (SAP) protocols. use. These protocols are further encapsulated in UDP or TCP to build the entire transport layer. The final "application flow" is related to system control and relies on other flows, such as RSVP, and the transport protocol that handles the dynamic configuration of mobile stations, such as DHCP resource reservation. [0054]
Rather than using one type of bearer, a multiplexer that multiplexes all four application flow types for transport with circuit-switched bearers such as V.110 modems, such as H.223, the present invention presents the present invention. It provides a bearer selection and quality of service parameter mapping layer that selects the most suitable one of circuit-switched bearers and packet-switched bearers for each application flow at the IP layer. In this example shown in Figure 7, the circuit-switched bearer is shown as a V.110 modem with IP / PPP protocol, and the packet-switched bearer is shown as a GPRS modem with IP over SNDCP protocol. .. Circuit-switched modem connections are established by dialing a telephone number and establishing a dedicated connection where individual IP packets are not routed. Point-to-Point Protocol (PPP) is an encapsulation protocol used to carry IP packets over dial-up connections on any serial line and is therefore well suited for circuit-switched bearers. Conversely, the GPRS modem routes each IP packet based on its header information. The Subnetwork Dependent Convergence Protocol (SNDCP) separates and compresses headers and data between mobile stations and GPRS SGSN. SNDCP was specifically developed to carry IP packets directly, thereby avoiding PPP. [0055]
Suitable and more detailed, but also in embodiments that are also examples of the present invention, the selection of specific types of bearers and the mapping of quality of service parameters are the bearer selection and QoS shown in the functional block diagram of FIG. It can be performed according to different prioritized criteria, as described herein with a mapping routine (block 70). Initially, individual application flows are discovered with the corresponding application flow identifier or associated quality of service class. In the resource reservation embodiment, individual application flows can be reserved with the desired IP level and quality of service parameters specified in advance. Alternatively, in a differentiated service embodiment, a new predefined class of service can be associated with an individual application flow, and all packets within that application flow are processed according to that quality of service class. Will be done. The resource reservation approach allows greater flexibility in choosing different IP level quality of service parameters. Differentiated service approaches, predefined quality of service parameters associated with each general service class are easier to manage. [0056]
Some of the specified IP level quality of service parameters can be given even greater importance than others. For example, in block 74, it is determined whether the IP quality of service parameter corresponding to the packet delay exists, and if so, below, above, or within the limit value (T) range. Delay in this example is a parameter given greater importance. If the delay parameter exists and is above the limit, a new packet-switched (PS) bearer is established. If packet-switched bearers have already been established, existing packet-switched bearers can be modified to accommodate newly detected delay parameters (block 84). Therefore, the IP quality of service parameters are mapped to the quality of service parameters of the packet-switched bearers. On the other hand, if the associated delay parameter is below the limit range, a new circuit-switched (CS) bearer is established or an existing circuit-switched bearer is modified to accommodate the newly detected delay parameter. (Block 86). Similar to the mapping function in block 84, the IP quality of service parameters requested by the IP are mapped to the corresponding circuit-switched bearer quality of service parameters. [0057]
Therefore, packet-switched bearers are selected if the application flow can tolerate a large amount of delay. Circuit-switched bearers are selected if delays are tolerated with little or no. However, if the detected delay parameter is within or absent from the limit range, then the next lowest priority quality of service parameter, in this example the bucket depth (necessary to remember the message sent). It is determined whether (corresponding to the buffer size) does not exist, is below, above, or within the limit range. If the bucket depth exists and is above the limit range, the packet-switched bearer feature is selected (block 84). If the bucket depth is below the limit range, the circuit-switched bearer procedure is selected (block 86). Bucket depth can be analogized to the burstiness quality of the application flow. Very bursty application flows are better suited to be carried by packet-switched bearers. Conversely, application flows with little or no burstiness (ie, continuous) are better suited for circuit-switched bearers. [0058] [0058]
If the bucket depth parameter does not exist or is within the limit range for that application flow, then another determination of whether a service class is specified for this particular application flow is made in block 78. If the best effort service class is specified, the packet-switched bearer is selected according to the procedure in block 84. If a guaranteed class of service exists, the circuit-switched bearer procedure in block 86 is selected. However, if no service class is specified or if there is a "controlled load" (ie, somewhere between the best effort and the guaranteed type of service), it will survive in block 80. It is determined whether the time (TTL) parameter does not exist, is below, above, or within the limit range. If the application has a short lifetime, the packet-switched bearer is selected according to the procedure in block 84, erasing the connection setup time associated with the circuit-switched bearer, and preferably communicating data before its lifetime expires. On the other hand, if the duration parameter is above the limit range, the application flow has sufficient lifetime to wait for the circuit-switched bearer to be established, so circuit-switched according to the procedure outlined in block 86. Beara is selected. [0059]
If the lifetime parameter does not exist or is within the limit range, then the amount of application flow (which can be determined by multiplying the lifetime parameter by the average bit rate (MBR)) does not exist or the limit value. Whether it is below, above, or within the range is determined in block 82. If the flow volume is below the limit range and indicates a very small amount, the packet-switched bearer is more optimal and block 84 is selected. Alternatively, if you have a large amount of data, it is best to follow the steps in block 86 to select circuit-switched bearers. To simplify the explanation, if the amount is within the limit value or does not exist, the default judgment is made and the packet-switched bearer is selected. Of course, those skilled in the art will appreciate that other quality of service parameters can be requested in a similar manner. [0060]
Both blocks 84 and 86 show the mapping of quality of service to specific bearer service quality parameters. An example of mapping an IP quality of service (QoS) parameter to a packet-switched QoS parameter (such as that used for GPRS) is as follows: [0061]
IP QoS parameters PS QoS parameters Peak Bit Rate Peak Throughput Average Bit Rate Average Throughput Time to Live (TTL) Average Throughput Bucket depth burst size Total packet delay Delay class Service class Reliability class Service class Priority class A similar example of quality of service mapping is described for circuit-switched bearers. [0062]
IP QoS parameters CS QoS parameters Service class Beara service type Peak Bit Rate Time Slots Average Bit Rate Time Slots Here, reference is made to FIG. 9 showing the mobile communication system in the form of a functional block diagram based on the example of the GSM / GPRS model adopted in the embodiment of the present invention. The mobile communication system 100 has a mobile station 102 including a dynamic host configuration protocol (DHCP) client 104, a point-to-point protocol (PPP) client 106, and a bearer selection and service quality parameter mapper 107. ing. Mobile station 102 is connected to base station subsystem (BSS) 108 on a radio interface (via circuit-switched bearers and / or packet-switched bearers). A BSS includes a base station that communicates with a mobile station attached to its base station controller. As shown in FIG. 2, the base station controller of BSS108 routes circuit-switched communication on the circuit-switched bearer to the direct access unit (DAU) 102 in MSC110 of the GSM circuit-switched network 35, and packets on the packet-switched bearer. Route switching is assigned to SGSN114 in GSM packet-switched (GPRS) network 51. The direct access unit 102 terminates the wireless link protocol and V.110 modem call. DAU102 creates a Layer 2 tunnel to the GGSN as directed by the HLR carried through the MSC. The DAU102 uses the telephone number and subscription information of the external / entity received from the HLR such as the mobile IMSI to determine which particular GGSN to establish the L2TP tunnel. [0063]
For calls made by the mobile station, the network and network bearer selection for the application flow originating from the mobile station 102 is made by the mobile mapper 107. The circuit-switched bearer is transferred to an external network gateway node corresponding to GGSN116 using the IP / PPP / L2TP protocol of the embodiment. The IP tunnel is created with a V.110 modem connection terminated by the direct access unit. The term "Layer 2 tunneling over IP" means that it also utilizes the L2TP protocol, which carries IP traffic between terminals, as well as a fundamental IP network as a transport mechanism between the direct access unit and the GGSN. [0064]
Packet-switched application flows are forwarded using the DHCP / IP / GPRS tunneling protocol. DHCP is only applied at the set time. Subsequent IP packets (after configuration) are carried directly on the GPRS bearer. The GPRS Tunneling Protocol (GTP) encapsulates terminal-to-terminal IP packets between the serving node and the gateway node, and like L2TP, is the basic transport mechanism between the GPRS serving node and the gateway node. IP network is used. Therefore, both circuit-switched data and packet-switched data from MSC110 and SGSN114 to GGSN116 go through the IP tunnel, respectively. The use of IP as a transport mechanism provides a flexible and scalable implementation of the Internet-based mobile communication backbone. [0065]
The GGSN116 includes a common access server 118, a configuration relay agent 120, a PPP server 122, an L2TP server 124, an RTP translator 126, and a mapper 128 similar to the mapper 107 shown on the mobile station 102. The Common Access Server 118 will be responsible for the interface to external network entities and will allow or disallow mobile station communications to reach destinations on the external network using remote authentication protocols such as RADIUS. If you want to interact with an external network entity. The RADIUS protocol (or other security negotiation protocol) is used to agree with the external network entity about security measures for the transport mechanism between the GGSN's common access server and the entry point of the external network entity. be able to. [0066]
The configuration relay agent 120 relays DHCP messages between the DHCP client of the mobile station and the DHCP server of the external network when setting the environment. The configuration relay agent 120 obtains the IP address assigned to the mobile station in detail and uses it, for example, via PPP for subsequent configuration of other mobile communication bearer services. The configuration relay agent 120 adds security measures to the environment settings by applying an identifier check on all information between the DHCP client and server. [0067]
The PPP server 122 terminates the PPP link established on the circuit-switched mobile communication bearer from the mobile station to the GGSN. In particular, PPP server 122 terminates the request for authentication and environment settings from the mobile station regarding the circuit-switched bearer, and uses the information from the common access server 118 and the configuration relay agent 120 to make the request from the mobile station. Respond to. [0068]
The L2TP server establishes and terminates a "virtual call" on the IP network between the GGSN and the MSC110 direct access unit 112. The virtual call contains the same information as the actual circuit-switched call between the direct access unit 112 and the mobile station and has the same duration. The RTP translator 126 performs translation of the coding scheme between the coding scheme applied in the high speed network between the GGSN and the external network entity and the coding scheme that is more optimal for low speed wireless networks in GSM. To do. The RTP translator 126 can provide a user profile for each mobile user, eg, via RADIUS, to perform a dedicated RTP translation for a particular mobile station. RTP translation functionally increases the likelihood that two entities can communicate with each other. [0069]
Mapper 128 performs link layer selection and QoS mapping functions for each individual application flow. More specifically, as mentioned above, the mapper 128 determines whether the application reservation request is mapped to a circuit-switched mobile communication bearer or a packet-switched mobile communication bearer, and from the application "view" the mobile. Translate the quality of service parameters to the communication bearer "view". However, the mapper can change the link layer bearer selection on a packet-by-packet basis in certain circumstances. [0070]
One such situation is when a class B mobile has already established a circuit-switched connection and also receives packet data during the circuit-switched connection. As mobile data communications progress, different classes of mobile stations with different capabilities may emerge. For example, GSM currently defines three different classes of mobiles. That is, it is class A, class B and class C. Class A mobiles can create and / or receive traffic simultaneously for both circuit-switched and packet-switched bearers. Class B mobiles simultaneously support the activation and monitoring of circuit-switched and packet-switched services, but can only send or receive traffic corresponding to the application flow on one type of bearer at a time. Class C mobiles are the least flexible and only support communication traffic on one type of bearer. In the situation where a class B mobile establishes a circuit-switched connection, Mappa 128 does not wait to establish a packet-switched bearer when the circuit-switched bearer is released, but rather data on this same circuit-switched bearer. Is also sent. [0071]
The GGSN116 is connected to an Internet Service Provider (ISP) using IP tunneling or a link layer permanent virtual circuit. IP tunneling is scalable because IP tunnels must only be configured at the end of the tunnel, i.e. at the GGSN and external network entities, while permanent virtual circuits must also be configured at each intermediate node. It is suitable from the viewpoint of. However, in certain cases, built-in security in Asynchronous Transfer Mode (ATM) and Frame Relay (FR) Permanent Virtual Circuits may be preferable to more vulnerable IP tunnels. [0072]
Internet service providers include an authentication server 132, a preference server 134, and a conference server 136. An example of an authentication server intended for illustration purposes only is the Remote Authentication Dial-in User Service (RADIUS), a protocol for authentication, authorization, configuration, and billing between GGSN's Common Access Server 118 and ISP130. is there. An example of an environment setting server used in the following description is a DHCP server that passes environment setting information between hosts in a TCP / IP network. An example application server used in the following description is the conference server 136, which acts as the gatekeeper for the entire conference. The gatekeeper conference server 136 keeps a record of who is attending the conference and what type of application flow it is using. [0073]
Both the packet-switched bearer service and the circuit-switched bearer service share the same billing relationship with the ISP. For example, a RADIUS server maintains a single data record for a mobile station. The data record collects billing information for both types of bearer services keyed into the billing record identifier corresponding to the mobile MSid. [0074]
FIG. 10 shows an example of a message signal between various nodes of the communication system shown in FIG. 9 in which the best circuit-switched bearer service or packet-switched bearer service is selected for different application flows. Assuming that the ISP relationship has already been established between the mobile station and the ISP conference server, the mobile station has already received some application control packets on the packet switching bearer. In this example, the ISP conference server 136 then sends an IP packet corresponding to the real-time application flow from the conference to the mobile station, which is received by the GGSN in the mobile communication system. The GGSN selects the optimal packet-switched or circuit-switched bearer and other parameters such as coding and / or compression ratio. [0075]
In this example, the RTP translator 126 in the GGSN 116 modifies the stream coding from the fast conferencing server 136 to the slow mobile communication network based on the mobile station profile shown in the packet header and the current RTP coding. To do. Circuit-switched bearers are established based on the real-time characteristics of incoming flows. The mobile station profile is administratively configured and configured by an authentication (RADIUS) server or by some other user interface. The GGSN uses the mobile station profile to select the optimal coding and bearer service for each application flow, as described in Figure 8 above. The GGSN uses mobile station classes along with the type of bearer service to switch between packet-switched bearer services and circuit-switched bearer services for class B mobiles. [0076]
In reference to Figure 10, in response to a real-time IP packet received from the ISP conference server, the GGSN either initiates a circuit-switched application flow over L2TP or packets over GTP, depending on when the best bearer is selected. Start the exchange application flow. The GTP protocol between SGSN and GGSN is "extended" by the MS class parameter "allowing GGSN to determine if a mobile station is a Class A, B or C mobile. As mentioned earlier, the GGSN applies special rules to class B mobiles. [0077]
Assuming that the circuit-switched bearer is selected based on the real-time characteristics of incoming packets, the GGSN is an L2TP outgoing call request containing the dialed phone number corresponding to the MSid (the mobile is called in this example), Send the call ID and circuit-switched bearer service type. Circuit-switched virtual calls are received by the direct access unit 112 at a mobile exchange center that establishes circuit-switched calls with mobile stations over wireless links. [0078]
In this example, the GGSN merges IP packets from the non-real-time application flow with the real-time traffic flow while the circuit-switched bearer is still established. Although these non-real-time packets are better suited for packet-switched bearers, the GGSN is in line with the already established circuit-switched bearers because the mover is a class B mover and can only support one type of bearer at a time. Sends an IP packet. Non-real-time packets (ie, protocol data units (PDUs)) relay these PDUs to mobile stations over circuit-switched radio links as two-point protocol frames over the circuit-switched bearer's L2TP tunnel. Sent to the MSC direct access unit. [0079]
The mobile station then decides to end the call and releases the circuit-switched bearer. The mobile sends a disconnect notification message over L2TP to the GGSN that enables circuit-switched bearer release via the direct access unit. Subsequently, the ISP conference server sends a non-real-time IP packet to the mobile. Since there is no existing circuit-switched bearer, GGSN determines that the packet-switched bearer service is more suitable for non-real-time type packets and establishes a packet-switched bearer to carry the packet to the mobile station. In particular, packet-switched tunnels are established between the GGSN and SGSN on GTP tunnels that carry IP packets with the corresponding tunnel identifier (TID). The SGSN then establishes a logical data link (logical link control (LLC)) between the SGSN and the mobile station and sends the packet to the mobile station on the basis of best effort. [0080] [0080]
One of the important advantages of the present invention is that a common access procedure is adopted between the mobile station and the Internet service provider for both circuit-switched bearer service and packet-switched bearer service. This common access procedure is performed using a "low cost" packet-switched bearer and includes a common authentication procedure and a common environment setup procedure. After the common access procedure is completed with the initial registration, subsequent application flows are approved and configured using a very simple procedure that does not require contact with the ISP. [0081]
FIG. 11 shows an example of a procedure for a common external network access routine (block 170) according to another aspect of the invention. When a mobile station establishes a session with a mobile communication network, only a single common access procedure is performed to provide the mobile station with access to both circuit-switched and packet-switched services (block 172). In particular, only one authentication procedure is performed and one or more authentication parameters resulting from that procedure, such as MSid, Userid, password, etc., are stored for subsequent use (block 174). The common access procedure also involves performing only configuration between a single ISP / mobile station host for both circuit-switched bearer services and packet-switched bearer services, and the resulting configuration parameters are also for subsequent use. Remembered for (block 176). [0082]
Optimal type of mobile network bearer is selected for each application flow as described above using a dynamic booking approach or a differentiated services approach (block 178). In the dynamic reservation approach, communication resources such as radio channels are pre-reserved so that the selected bearer provides the QoS parameters specifically requested for that bearer. In a differentiated service approach, each packet header is analyzed to determine if the header specifies one of several common service classes that indicate circuit-switched bearers or transport by packet-switched bearers. .. In this example, the dynamic reservation approach is preferred. For subsequent application flows involving this mobile station, stored authentication and configuration parameters are adopted to perform simplified (fast) authentication and configuration settings without the need to involve external network entities. (Block 180). [0083]
The common external network access procedure is effectively performed only once for all application flows after the initial registration is completed. Common authentication and configuration procedures are performed using packet-switched bearers in less than half the normal time required by traditional registration procedures using circuit-switched bearers. The initial authentication and configuration steps do not have to be performed for each subsequent individual application flow, thus saving even more time. Instead, simplified authentication and configuration are performed on a common access server in seconds for subsequent flows within the mobile communications network. [0084]
The common authentication procedure is now described with reference to FIG. 12, which shows an example of message exchange between various nodes in FIG. Assuming that the PDP context was requested, created, and accepted by the GGSN, the mobile initiates a common dynamic host configuration procedure (interleaved with a common authentication procedure) that is unique to the mobile station. To the GGSN by sending a DHCP discoverer message that provides an identifier (MSid), user identifier (Userid), password, and possibly other parameters that will be used to identify and authenticate the mobile station. Establish a logical relationship between. [0085]
The GGSN maps DHCP authentication requests to Radius requests by selecting the Radius authentication server 132 at the ISP 130 based on the Userid if the Userid is in the form User @ ISP. In other cases, the static mapping of the user to the ISP applies to the GGSN. Assuming that the information sent is genuine, the Radius server 132 sends an access accept message with tunneling configuration information to the GGSN's common access server. The tunneling configuration information is used by the GGSN to send common host configuration messages and other IP packets to the ISP. The GGSN remembers the mobile station's MSid (based on the mobile's IMSI), Userid, and password, and proceeds with the common host environment setup procedure described in more detail below. At this point, the common authentication procedure with the ISP is complete for both circuit-switched bearer services and packet-switched bearer services. [0086]
Also referring to Figure 12, assume that a new application flow is initiated at the mobile station of choice for the circuit-switched bearer (eg, an audio call from the mobile (party A) to caller B). The MSC110 direct access unit 112 terminates the modem connection corresponding to the circuit-switched bearer selected for its new application flow. The direct access unit 112 analyzes the caller's B phone number and selects an L2TP termination point based on the B number and the HLR subscription data, that is, the appropriate GGSN to connect the call to B. The direct access unit 112 then sends an authentication request, shown in the form of a password authentication protocol (PAP) or challenge authentication protocol (CHAP) request in the example of Figure 12, to the common access server of the selected GGSN. Then, the mobile station authentication parameters including the MSid, Userid, and password are sent to the common access server. [0087]
Rather than performing another authentication procedure involving an external ISP, the MSid, Userid and password received in the PAP / CHAP request are compared to the values stored on the common access server during the initial authentication procedure. Will be done. If the received value matches the value stored on the access server, the authentication confirmation is sent as a CHAP / PAP response to the mobile station through the MSC's direct access unit. The Common Access Server matches the information provided with the stored information to authenticate the mobile without the need for another authentication procedure with the ISP's Radius server. This simplified authentication procedure of the same type is also performed for other subsequent application flows initiated during the session. [0088]
The common access procedure further defines a common IP host environment setting procedure for both the circuit-switched server and the packet-switched server, as described together with the signal sequence shown in FIG. The IP host configuration is transparent to the bearer setup, except that it includes the DHCP configuration relay agent 120 on the GGSN. The DHCP relay agent 120 acts as an intermediary between the DHCP client 104 of the mobile station 102 and the DHCP server 134 of the ISP 130. Relay agent 120 preserves message transfer between DHCP client 104 and server 134 by appending an agent identifier (corresponding to MSid) to each DHCP message sent to the ISP's DHCP configuration server 134. To do. The configuration relay agent 120 then shuts down using the agent identifier to filter out packets to and from mobile stations that did not have the correct IP address in the header. The agent remote identifier (remote ID), subnet mask, and gateway IP address (giaddr), which is the address that identifies the GGSN, are sent to the ISP 130, where they are checked and stored. [0089]
The ISP130 returns the response to the GGSN using the subnet mask and giaddr, which sends the response to the mobile station based on the agent remote ID. The agent remote identity also gives the ISP additional confirmation that the mobile station has not "forged" its identity during the dynamic host configuration procedure. Therefore, following the common authentication procedure above, the configuration relay agent 120 appends the IP address of the GGSN to the giaddr field and relays the DHCP discoverer message to the DHCP server. [0090]
The ISP's DHCP server 134 has a discover message that is passed to the mobile station by the GGSN relay agent 120 and contains an offer message containing the "offered" preferences that the DHCP server 134 can provide (after checking the ingress and egress tunnel identifiers). Respond to. You can receive numerous offers from various DHCP servers. The mobile station selects the DHCP offer that best meets the requirements and sends a DHCP request message to the DHCP server that provided the selected offer. The DHCP server then provides the IP address to the GGSN in the DHCP reception notification message. The IP address is placed in the table along with the mobile agent remote ID and agent line ID / tunnel identifier. [0091]
The DHCP reception notification message is relayed to a mobile host configured with a set of selected DHCP parameters including IP address, DNS server name, and so on. The GGSN common access server stores authentication parameters such as MSid, Userid, password, etc. as well as these configuration parameters such as the IP address assigned to the mobile station. [0092]
Since the circuit-switched bearer service and the packet-switched bearer service share the same IP termination / IP address at the mobile station, the common IP host environment setting made on the packet-switched (GPRS) bearer service is the circuit-switched bearer service. Covers subsequent circuit-switched PPP sessions from the same mobile station using the service. When a mobile station initiates a new application flow on a circuit-switched bearer, that is, by sending a PPP conformation request to the GGSN over the L2TP tunnel in the example shown in Figure 13. The Common Access Server compares the PPP tunnel request parameters, including the MSid and default preferences parameters, with the stored DHCP preferences information and returns a receipt notification if the comparison results match. .. No additional configuration operation is required on the ISP DHCP server. After this simplified configuration procedure, the common access server simply returns a PPP configuration receipt notification to the mobile station via the direct access unit, and the selected circuit-switched bearer begins to carry the desired information. .. [0093]
The present invention combines both circuit-switched bearer services and packet-switched bearer services in order to provide end users with enhanced and efficient applications at low cost. Both circuit-switched services and packet-switched services can be applied where best suited to the individual application flow. Further, the present invention provides a common access procedure for accessing an external network entity such as an ISP at a very low cost and in a significantly short setup time. The initial authentication and configuration procedure with the gateway node's common access server only needs to be done once during initial registration and is valid for both circuit-switched bearer services and packet-switched bearer services. After that, a simplified authentication and configuration procedure is only required between the mobile station and the common access server for subsequent new application flows. [0094]
Although the present invention has been described with respect to specific embodiments, one of ordinary skill in the art will recognize that the invention is not limited to the particular embodiments described and illustrated herein. To practice the present invention, different forms, embodiments and applications other than those shown and described herein, as well as many modifications, modifications and equivalent arrangements can be used. For example, instead of the GSM circuit-switched network in the example above, a wireless local area network (WLAN) or digital audio / video broadcast (DAB / DVB) may be used. Similarly, other packet-switched networks may be used. Accordingly, the present invention has been described in the context of its preferred embodiments, but this disclosure is merely an explanation and description of the invention, with the sole purpose of providing a complete and feasible disclosure of the invention. It should be understood that. Therefore, the present invention is limited only by the gist and scope of the claims.
[Simple explanation of drawings]
[Figure 1]
It is a schematic diagram which showed the data communication between a mobile host and a fixed host. [Figure 2]
It is a more detailed diagram showing a GSM mobile communication system including a general packet radio service (GPRS) data network. [Fig. 3]
It is a figure which showed the example of the data communication protocol adopted between different nodes in the packet switching GPRS data communication network in GSM. [Fig. 4]
It is a flowchart which showed the optimum bearer selection procedure for every application flow according to embodiment of this invention. [Fig. 5]
FIG. 5 is a protocol stack diagram illustrating an embodiment of mapping an application flow to a particular bearer according to a particular quality of service parameters according to the present invention. [Fig. 6]
It is a figure which showed the example of the data communication protocol adopted between different nodes in a circuit-switched mobile communication network in GSM. [Fig. 7]
FIG. 5 shows some mobile application flows managed and mapped according to embodiments of the present invention. [Fig. 8]
It is a flowchart which showed the example of the priority determination which selects the bearer and the corresponding QoS bearer parameter with respect to the application flow according to the Embodiment of this invention. [Fig. 9]
It is a functional block diagram which showed the embodiment of this invention in a GSM / GPRS mobile communication system. [Fig. 10]
It is a diagram of a messaging sequence showing an example of an application flow in which both a circuit-switched bearer service and a packet-switched bearer service are selected. [Fig. 11]
It is a flowchart which showed the common external network access procedure according to embodiment of this invention. [Fig. 12]
It is a figure of the messaging sequence which showed the example of the common authentication procedure for both circuit switching service and packet switching service. [Fig. 13]
It is a figure of the messaging sequence which showed the example of the common IP host environment setting for both the circuit-switched bearer service and the packet-switched bearer service.
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| JP2009510546A | Cited by | Japan | Examiner |
| JP2013526790A | Cited by | Japan | Examiner |
| JP2007520910A | Cited by | Japan | Search report |
| JP2009542119A | Cited by | Japan | Examiner |
| JP2011130455A | Cited by | Japan | Examiner |
| JP2008522486A | Cited by | Japan | Search report |
| US8705550B2 | Cited by | United States of America | Applicant |
| JP2012054963A | Cited by | Japan | Search report |
| JP2007531411A | Cited by | Japan | Examiner |
| JP2006050594A | Cited by | Japan | Search report |
| JP2006203923A | Cited by | Japan | Search report |
| JP2009508416A | Cited by | Japan | Examiner |
| JP2011130455A | Cited by | Japan | Search report |
| JP2013526790A | Cited by | Japan | Search report |
| JP2009526424A | Cited by | Japan | Search report |
| JP2012009041A | Cited by | Japan | Examiner |
| US8768386B2 | Cited by | United States of America | Applicant |
| JP2003506981A | Cited by | Japan | Examiner |
| WO2006004157A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US7319676B2 | Cited by | United States of America | Applicant |
| JP2006054841A | Cited by | Japan | Search report |
| JP2010213324A | Cited by | Japan | Examiner |
| JP4889174B2 | Cited by | Japan | Search report |
| JP2010516167A | Cited by | Japan | Search report |
| JP4768818B2 | Cited by | Japan | Examiner |
| US9049096B2 | Cited by | United States of America | Applicant |
| US8102839B2 | Cited by | United States of America | Applicant |
| JP2003507969A | Cited by | Japan | Search report |
18 members in 12 offices
Priority claims14
| Document | Office | Kind | Date |
|---|---|---|---|
| 60060061 | United States of America | – | |
| 6006197 | United States of America | P | |
| 6006197 | United States of America | P | |
| 09121678 | United States of America | – | |
| 12167898 | United States of America | A | |
| 12167898 | United States of America | A | |
| 9801649 | Sweden | W | |
| 9801649 | Sweden | W | |
| 1997060061 | – | – | – |
| 1998121678 | – | – | – |
| 199801649 | – | – | – |
| US19970060061P | – | – | – |
| US19980121678 | – | – | – |
| WO1998SE01649 | – | – | – |
Members18
| Document | Office | Kind | |
|---|---|---|---|
| CA2304863A1 | Canada | A1 | |
| WO9916266A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU9287698A | Australia | A | |
| EP1018275A1 | European Patent Office (EPO) | A1 | |
| BR9812522A | Brazil | A | |
| KR20010030725A | Republic of Korea | A | |
| JP2001517910AThis record | Japan | A | |
| AU742647B2 | Australia | B2 | |
| NZ503466A | New Zealand | A | |
| US2003039237A1 | United States of America | A1 | |
| US6608832B2 | United States of America | B2 | |
| EP1018275B1 | European Patent Office (EPO) | B1 | |
| DE69829764D1 | Germany | D1 | |
| ES2242295T3 | Spain | T3 | |
| MY121314A | Malaysia | A | |
| DE69829764T2 | Germany | T2 | |
| JP4307709B2 | Japan | B2 | |
| CA2304863C | Canada | C |
25 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 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| 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 | |
| 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 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Written amendmentJAPANESE 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 reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 2001-517910
- Publication, DOCDB
- 2001517910
- Publication, EPODOC
- JP2001517910
- Application
- 2000513425
- Application, DOCDB
- 2000513425
- Application, EPODOC
- JP20000513425
Titles2
- Japanese
- 【発明の名称】移動体通信ネットワークにおける選択可能なパケット交換及び回線交換サービス
- English
- Description: Selectable packet switching and circuit switching services in mobile communication networks.
Classification
- CPC, 6
- H04W28/18
- H04L63/029
- H04L63/08
- H04L63/083
- H04W4/24
- H04W28/26
- IPC, 7
- H04L12 28
- H04L12 56
- H04L12 64
- H04L29 06
- H04W4 24
- H04W28 18
- H04W28 26