Mobile wireless communication system and access gateway
Abstract
This record has no abstract on file.
Term
Projected expiry 7 April 2028.
- Priority and filed
- Granted
- Today
- Projected expiry
18 claims: 4 independent, 14 dependent
- 1移動局と無線通信するための複数の基地局と、コア網に接続されるアクセスゲートウェイ(AGW)とからなり、 前記 各基地局と 前記 AGWとの間にデータパケット転送用のトンネルが形成される移動無線通信システムにおいて、 前記 AGWが、アクセス網を介して 前記 複数の基地局と制御メッセージを交信する制御用のアクセスゲートウェイ部(C-AGW)と、 前記 アクセス網を介して 前記 複数の基地局とデータパケットを交信するデータ転送用のアクセスゲートウェイ部(U-AGW)とからなり、 前記 C-AGWが、 移動局の識別子と対応づけて、トンネルの1端となる基地局のアドレスと、該トンネルの他端となるU-AGWのアドレスとを記憶した複数のテーブルエントリからなる第1の管理テーブルと、 何れか の基地局から、移動局識別子を含むトンネル設定要求メッセージを受信したとき、トンネルの終端となるべきU-AGWのアドレスを示す応答メッセージを 前記 基地局に返送する制御部とを有し、 前記 制御部が、 前記 第1の管理テーブルから 前記 トンネル設定要求メッセージが示す移動局識別子 に 対応するテーブルエントリを検索し、 前記トンネル設定用メッセージが示す移動局識別子に対応するテーブルエントリが前記第1の管理テーブルに登録済みの場合は 、該テーブルエントリが示すU-AGWのアドレスを 前記 応答メッセージで 前記 基地局に通知し、 前記トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリが前記 第1の管理テーブルに未登録の場合は、 前記 複数のU-AGWのうちから選択された特定のU-AGWのアドレスを 前記 応答メッセージで 前記 基地局に通知することを特徴とする移動無線通信システム。
- 2前記C-AGWの制御部が、前記第1の管理テーブルに 前記トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ が未登録の場合、前記トンネル設定要求メッセージが示す移動局識別子と対応づけて、該トンネル設定要求メッセージの送信元基地局のアドレスと、前記特定のU-AGWのアドレスとを示す新たなテーブルエントリを 前記 第1の管理テーブルに登録することを特徴とする請求項1に記載の移動無線通信システム。
- 3前記トンネル設定要求メッセージが、前記移動局識別子をもつ移動局のハンドオーバ先となる基地局から送信されたものであった場合、前記C-AGWの制御部が、前記第1の管理テーブルに登録されている 、前記トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ の基地局アドレスを、 前記 トンネル設定要求メッセージの送信元基地局のアドレスに書き換えることを特徴とする請求項2に記載の移動無線通信システム。
- 4前記トンネル設定要求メッセージが、前記移動局識別子をもつ移動局が使用中の第1のトンネルと共存すべき第2のトンネルの設定要求であった場合、前記C-AGWの制御部が、前記第1の管理テーブルに、 前記 トンネル設定要求メッセージが示す移動局識別子と対応づけて、該トンネル設定要求メッセージの送信元基地局のアドレスと、前記 第1のトンネルの設定要求時に前記複数のU-AGWのうちから選択された U-AGWのアドレスと 同一のU-AGWのアドレス を示す新たなテーブルエントリを登録することを特徴とする請求項2に記載の移動無線通信システム。
- 5前記C-AGWが、前記U-AGW毎に消費された通信リソース量を示すU-AGW状態テーブルを備え、 前記 トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ が前記第1の管理テーブルに未登録の場合、前記制御部が、 前記 U-AGW状態テーブルから消費通信リソース量が最小のU-AGWを選択して、該U-AGWのアドレスを前記応答メッセージで前記基地局に通知することを特徴とする請求項1~請求項4の何れかに記載の移動無線通信システム。
- 6前記C-AGWが、前記移動局の識別子と対応づけて、該移動局に保証すべき通信品質情報を記憶した複数のテーブルエントリからなる第2の管理テーブルを有し、 前記 トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ が前記第1の管理テーブルに未登録の場合、前記制御部が、 前記 第2の管理テーブルから前記トンネル設定要求メッセージが示す移動局識別子と対応する通信品質情報を検索し、前記複数のU-AGWの中から 前記 通信品質情報に応じた特定のU-AGWを選択することを特徴とする請求項1~請求項4の何れかに記載の移動無線通信システム。
- 7前記複数のU-AGWのうちの少なくとも1つが、特定の通信サービス用に専用化されており、 前記第2の管理テーブルに記憶された通信品質情報が通信サービスクラス情報を含み、 前記 トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ が前記第1の管理テーブルに未登録の場合、前記制御部が、 前記 第2の管理テーブルから前記トンネル設定要求メッセージが示す移動局識別子と対応するテーブルエントリを検索し、該テーブルエントリが 前記 特定の通信サービスと対応する通信サービスクラス情報を含んでいたとき、 前記 特定の通信サービス用に専用化されたU-AGWを選択することを特徴とする請求項6に記載の移動無線通信システム。
- 8前記第2の管理テーブルに記憶された通信品質情報がサービス優先度を含み、 前記 トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ が前記第1の管理テーブルに未登録の場合、前記制御部が、 前記 第1の管理テーブルと第2の管理テーブルに基づいて、前記U-AGW毎にサービス優先度が最上位となるトンネル本数を算出し、該トンネル本数が最小となるU-AGWを選択することを特徴とする請求項6に記載の移動無線通信システム。
- 9前記第2の管理テーブルに記憶された通信品質情報が帯域値を含み、 前記 トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ が前記第1の管理テーブルに未登録の場合、前記制御部が、 前記 第1の管理テーブルと第2の管理テーブルに基づいて、前記U-AGW毎に設定済みのトンネルに保証した帯域の合計値を算出し、該帯域の合計値が最小となるU-AGWを選択することを特徴とする請求項6に記載の移動無線通信システム。
- 10移動局と無線通信するための複数の基地局とコア網との間に配置されるアクセスゲートウェイ(AGW)であって、 アクセス網を介して 前記 複数の基地局と制御メッセージを交信する制御用のアクセスゲートウェイ部(C-AGW)と、 前記 アクセス網を介して 前記 複数の基地局とデータパケットを交信するデータ転送用のアクセスゲートウェイ部(U-AGW)とからなり、 前記 C-AGWが、 移動局の識別子と対応づけて、トンネルの1端となる基地局のアドレスと、該トンネルの他端となるU-AGWのアドレスとを記憶した複数のテーブルエントリからなる第1の管理テーブルと、 何れか の基地局から、移動局識別子を含むトンネル設定要求メッセージを受信したとき、トンネルの終端となるべきU-AGWのアドレスを示す応答メッセージを 前記 基地局に返送する制御部とを有し、 前記 制御部が、 前記 第1の管理テーブルから 前記 トンネル設定要求メッセージが示す移動局識別子 に 対応するテーブルエントリを検索し、 前記トンネル設定用メッセージが示す移動局識別子に対応するテーブルエントリが前記第1の管理テーブルに登録済みの場合は 、該テーブルエントリが示すU-AGWのアドレスを 前記 応答メッセージで 前記 基地局に通知し、 前記トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリが前記 第1の管理テーブルに未登録の場合は、 前記 複数のU-AGWのうちから選択された特定のU-AGWのアドレスを 前記 応答メッセージで 前記 基地局に通知することを特徴とするアクセスゲートウェイ。
- 11前記C-AGWの制御部が、前記第1の管理テーブルに 前記トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ が未登録の場合、前記トンネル設定要求メッセージが示す移動局識別子と対応づけて、該トンネル設定要求メッセージの送信元基地局のアドレスと、前記特定のU-AGWのアドレスとを示す新たなテーブルエントリを 前記 第1の管理テーブルに登録することを特徴とする請求項10に記載のアクセスゲートウェイ。
- 12前記トンネル設定要求メッセージが、前記移動局識別子をもつ移動局のハンドオーバ先となる基地局から送信されたものであった場合、前記C-AGWの制御部が、前記第1の管理テーブルに登録されている 、前記トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ の基地局アドレスを、 前記 トンネル設定要求メッセージの送信元基地局のアドレスに書き換えることを特徴とする請求項11に記載のアクセスゲートウェイ。
- 13前記トンネル設定要求メッセージが、前記移動局識別子をもつ移動局が使用中の第1のトンネルと共存すべき第2のトンネルの設定要求であった場合、前記C-AGWの制御部が、前記第1の管理テーブルに、 前記 トンネル設定要求メッセージが示す移動局識別子と対応づけて、該トンネル設定要求メッセージの送信元基地局のアドレスと、前記 第1のトンネルの設定要求時に前記複数のU-AGWのうちから選択された U-AGWのアドレスと 同一のU-AGWのアドレス を示す新たなテーブルエントリを登録することを特徴とする請求項11に記載のアクセスゲートウェイ。
- 14前記C-AGWが、前記U-AGW毎に消費された通信リソース量を示すU-AGW状態テーブルを備え、 前記 トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ が前記第1の管理テーブルに未登録の場合、前記制御部が、 前記 U-AGW状態テーブルから消費通信リソース量が最小のU-AGWを選択して、該U-AGWのアドレスを前記応答メッセージで前記基地局に通知することを特徴とする請求項10~請求項13の何れかに記載のアクセスゲートウェイ。
- 15前記C-AGWが、前記移動局の識別子と対応づけて、該移動局に保証すべき通信品質情報を記憶した複数のテーブルエントリからなる第2の管理テーブルを有し、 前記 トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ が前記第1の管理テーブルに未登録の場合、前記制御部が、 前記 第2の管理テーブルから前記トンネル設定要求メッセージが示す移動局識別子と対応する通信品質情報を検索し、前記複数のU-AGWの中から 前記 通信品質情報に応じた特定のU-AGWを選択することを特徴とする請求項10~請求項13の何れかに記載のアクセスゲートウェイ。
- 16前記複数のU-AGWのうちの少なくとも1つが、特定の通信サービス用に専用化されており、 前記第2の管理テーブルに記憶された通信品質情報が通信サービスクラス情報を含み、 前記 トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ が前記第1の管理テーブルに未登録の場合、前記制御部が、 前記 第2の管理テーブルから前記トンネル設定要求メッセージが示す移動局識別子と対応するテーブルエントリを検索し、該テーブルエントリが 前記 特定の通信サービスと対応する通信サービスクラス情報を含んでいたとき、 前記 特定の通信サービス用に専用化されたU-AGWを選択することを特徴とする請求項15に記載のアクセスゲートウェイ。
- 17前記第2の管理テーブルに記憶された通信品質情報がサービス優先度を含み、 前記 トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ が前記第1の管理テーブルに未登録の場合、前記制御部が、 前記 第1の管理テーブルと第2の管理テーブルに基づいて、前記U-AGW毎にサービス優先度が最上位となるトンネル本数を算出し、該トンネル本数が最小となるU-AGWを選択することを特徴とする請求項15に記載のアクセスゲートウェイ移動無線通信システム。
- 18前記第2の管理テーブルに記憶された通信品質情報が帯域値を含み、 前記 トンネル設定要求メッセージが示す移動局識別子に対応するテーブルエントリ が前記第1の管理テーブルに未登録の場合、前記制御部が、 前記 第1の管理テーブルと第2の管理テーブルに基づいて、前記U-AGW毎に設定済みのトンネルに保証した帯域の合計値を算出し、該帯域の合計値が最小となるU-AGWを選択することを特徴とする請求項15に記載のアクセスゲートウェイ。
Independent claims18
79 paragraphs, as filed
The present invention relates to a mobile wireless communication system, and more particularly to a mobile wireless communication system including an access gateway (AGW: Access Gateway) between an access network accommodating a plurality of radio base stations and a core network.
In a radio access network, a tunnel is set up between a radio base station (BS: Base Station) and an access gateway (AGW) using the Mobile IP (Mobile Internet Protocol) of the IETF (Internet Engineering Task Force). User data is transmitted through. Mobile IP tunnels are set up by communicating, for example, PMIP (Proxy Mobile IP) registration request (RRQ) messages and registration request response (RRP) messages between BS and AGW. Will be done. The format of PMIP RRQ messages and RRP messages is disclosed , for example, in Sections 3.1 and 3.2 of IETF RFC 3344 (Non-Patent Document 1).
On the other hand, in wireless access networks such as UMB (Ultra Mobile Broadband) / CAN (Converged Access Network) of 3GPP2 (3rd Generation Partnership Project 2), the control plane that handles control messages and the user plane that handles user data are being separated. Has been done. For example, Sections 4.4 and 4.6 of 3GPP2 X.S0054-100-0 v1.0 (Non-Patent Document 2) disclose that the data path and the signaling path are separated by AGW in UMB / CAN.
Figure 3 shows an example of a conventional radio access network. The mobile IP home agent (HA: Home Agent) 2 and the AAA (Authentication Authorization and Accounting) server 3 that performs user authentication, access authorization, and billing are connected to the core network 1. The radio base station (BS: Base Station) 10 (10A, 10B, ... 10N) is connected to the core network 1 via the access gateway AGW4. 7 indicates a session controller (SRNC: Session Reference Network Controller), and 20 (20A, 20B, ...) Indicates a mobile station.
The AGW4 includes a control AGW unit 5 that processes a control message (control packet) and a user data AGW unit 6 that processes user data (user packet). In the following description, the control AGW unit 5 is referred to as a C-AGW (Control plane AGW), and the user data AGW unit 6 is referred to as a U-AGW (User plane AGW). In the radio access network, the control packet is forwarded via the C-AGW5 as shown by the dashed line, and the user packet is forwarded via the U-AGW6 as shown by the solid line.
FIG. 4 shows an example of a communication sequence in the wireless access network shown in FIG. 3, for example, when a tunnel for user data transfer is set between BS10A and AGW4 when the AT20A is connected to the core network 1. Is shown. When a connection request is issued from AT20A, an access authentication procedure is executed between AAA server 3 and AT20A via BS10A, SRNC7, and C-AGW5 (SQ10a, SQ10b, SQ10c). At this time, the IP address of C-AGW5 is notified to BS10A from C-AGW5 as AGW-ID (SQ11), and AT<u style="single">2</u>From 0A to C-AGW5, the identifier (ATID) of AT20A to be authenticated is notified (SQ12).
When the access authentication of AT20A is completed, after executing the configuration (SQ14a, SQ14b) for wirelessly connecting AT20A to BS10A, set the tunnel for user data including the identifier (ATID) of AT20A from BS10A to C-AGW5. A request message, here a PMIP RRQ message, is sent (SQ15). When the AGW4 has a system configuration that allows the setting of multiple tunnels for the same AT, the BS10A adds control information (Primary) indicating that it is the first tunnel setting to the PMIP RRQ message.
When the C-AGW5 receives the PMIP RRQ message, it sends a response message, in this example, a PMIP RRP message to BS10A (SQ16). The PMIP RRP message contains the IP address of the U-AGW6 as information indicating the end of the tunnel (Endpoint). When the BS10A receives the PMIP RRP message from the C-AGW5, it sets up a tunnel with the U-AGW6 specified by "Endpoint" (SQ18). This allows AT<u style="single">2</u>0A is in a state where user data can be communicated with the communication partner connected to the core network 1 through the tunnel set between BS10A and U-AGW6 (SQ19a, SQ19b, SQ19c).
<nplcit num="1"><text>IETF RFC3344</text></nplcit><nplcit num="2"><text>3GPP2 X.S0054-100-0 v1.0</text></nplcit>
<p num="0010"> When there is one U-AGW6 included in AGW4 as in the radio access network shown in Fig. 3, C-AGW5 sends the same U-AGW at Endpoint for all tunnel setting requests received from BS. I should have returned the specified response message. However, when AGW4 is composed of C-AGW and multiple U-AGWs, C-AGW5 is most suitable for AT considering the load state of each U-AGW when receiving a tunnel setting request from BS. U-AGW needs to be assigned. Non-Patent Document 2 does not disclose a method of assigning U-AGW to AT in AGW4 having a plurality of U-AGWs.</p><p num="0011"> Further, in a wideband mobile wireless communication system such as UMB (Ultra Mobile Broadband), in order to realize high-speed and high-efficiency data transmission, fine-grained handover control accompanying the movement of AT is required. There is. In the UMB communication system, for example, in AT20 and BS10, the state of the wireless propagation path in the upward direction from AT to BS and the state of the wireless propagation path in the downward direction from BS to AT are monitored, and each direction of uplink and downlink is monitored. BS switching control is performed so that the AT is connected to the BS in which the state of the propagation path is the best. In this case, depending on the condition of the propagation path, the BS-to-BS handover may occur frequently in a short period of time for the same AT, and as a result, a useless control procedure may be executed. Further, since it takes a certain amount of time to set the tunnel between the BS and the AGW, there is a limit for the BS and the AGW to follow these handovers when the handover conditions between the BSs occur frequently.</p><p num="0012"> An object of the present invention is to provide a mobile radio communication system and an access gateway (AGW) capable of assigning an optimum U-AGW selected from a plurality of U-AGWs when a tunnel setting request is generated from a base station. There is. Another object of the present invention is a mobile wireless communication system capable of assigning a U-AGW to a tunnel setting request source so that the load is distributed among a plurality of U-AGWs when a tunnel setting request is generated from a base station. To provide an access gateway (AGW).</p>
<p num="0013"> In order to achieve the above object, the present invention comprises a plurality of base stations for wireless communication with a mobile station and an access gateway (AGW) connected to a core network, and between each of the base stations and the AGW. In a mobile wireless communication system in which a tunnel for data packet transfer is formed in, the AGW has a control access gateway unit (C-AGW) for communicating control messages with the plurality of base stations via an access network. It consists of an access gateway unit (U-AGW) for data transfer that communicates data packets with the plurality of base stations via the access network. The C-AGW consists of a plurality of table entries that store the address of the base station at one end of the tunnel and the address of the U-AGW at the other end of the tunnel in association with the identifier of the mobile station. When a tunnel setting request message including a mobile station identifier is received from the management table of 1 and any of the above base stations, a response message indicating the address of the U-AGW that should be the end of the tunnel is returned to the above base station. Has a control unit The control unit searches the table entry corresponding to the mobile station identifier indicated by the tunnel setting request message from the first management table, and when the target table entry is searched, the U-AGW indicated by the table entry is searched. When the target table entry is not registered in the first management table, the address of the specific U-AGW selected from the plurality of U-AGWs is notified. The address is notified to the base station by the response message.</p><p num="0014"> More specifically, when the target table is not registered in the first management table, the control unit of the C-AGW associates the tunnel setting request message with the mobile station identifier indicated by the tunnel setting request message. A new table entry indicating the address of the source base station and the address of the specific U-AGW is registered in the first management table.</p><p num="0015"> When the tunnel setting request message is, for example, transmitted from a base station that is a handover destination of a mobile station having the mobile station identifier, the control unit of the C-AGW is set in the first management table. The base station address of the registered target table entry is rewritten to the address of the source base station of the above tunnel setting request message.</p><p num="0016"> When the tunnel setting request message is, for example, a setting request for a second tunnel in which the mobile station having the mobile station identifier should coexist with the first tunnel in use, the control unit of the C-AGW may perform the setting request. The first management table is associated with the mobile station identifier indicated by the tunnel setting request message, and a new address indicating the address of the source base station of the tunnel setting request message and the address of the specific U-AGW are indicated. Register the table entry.</p><p num="0017"> One feature of the present invention is that the C-AGW includes a U-AGW status table showing the amount of communication resources consumed for each U-AGW, and the target table entry is not registered in the first management table. In the case of, the control unit of the C-AGW selects the U-AGW having the smallest amount of communication resources from the U-AGW status table, and notifies the base station of the address of the U-AGW by the response message. I have done so.</p><p num="0018"> In one embodiment of the present invention, the C-AGW has a second management table consisting of a plurality of table entries that store communication quality information to be guaranteed in the mobile station in association with the identifier of the mobile station. When the target table entry is not registered in the first management table, the control unit of the C-AGW has a communication quality corresponding to the mobile station identifier indicated by the tunnel setting request message from the second management table. It is characterized in that information is searched and a specific U-AGW corresponding to the above communication quality information is selected from a plurality of U-AGWs.</p><p num="0019"> In another embodiment of the present invention, at least one of the plurality of U-AGWs is dedicated to a specific communication service, and the communication quality information stored in the second management table is the communication service. When the above-mentioned target table entry including the class information is not registered in the first management table, the control unit of the above-mentioned C-AGW corresponds to the mobile station identifier indicated by the above-mentioned tunnel setting request message from the above-mentioned second management table. When the table entry contains the communication service class information corresponding to the specific communication service, the U-AGW dedicated to the specific communication service is selected. To do.</p><p num="0020"> The communication quality information indicated by the second management table includes, for example, a service priority. In this case, when the target table entry is not registered in the first management table, the control unit of C-AGW provides a service for each U-AGW based on the first management table and the second management table. The number of tunnels with the highest priority (the number of connected ATs) is calculated, and the U-AGW with the smallest number of tunnels is selected.</p><p num="0021"> The communication quality information indicated by the second management table may include a bandwidth value guaranteed to the mobile station. In this case, when the target table is not registered in the first management table, the control unit of C-AGW has already been set for each U-AGW based on the first management table and the second management table. Calculate the total value of the bands guaranteed for the tunnel, and select the U-AGW that minimizes the total value of the bands.</p>
<p num="0022"> According to the present invention, when a tunnel setting request is generated from the destination base station due to the position change of the mobile station, the C-AGW is the same U as the end point of the tunnel formed by the mobile source base station. -Since the AGW is assigned to the mobile destination base station, even if the base station wirelessly connected to the mobile station is switched, the transmitted / received packets of the mobile station can be continuously transferred by the same U-AGW. It will be possible.</p><p num="0023"> Further, according to the present invention, when the first tunnel setting request for the mobile station is received from the base station, the C-AGW is applied to the mobile station so that the load is distributed among the plurality of U-AGWs in the AGW. Should be assigned<u style="single">U</u>-Since AGW is selected, it is possible to avoid the occurrence of packet transfer delay in a specific U-AGW due to uneven load. In addition, C-AGW refers to the communication quality required by the mobile station and is suitable for mobile station communication.<u style="single">U</u>-By selecting AGW, it is possible to transfer data packets with guaranteed communication quality to mobile stations.</p>
Hereinafter, examples of the present invention will be described with reference to the drawings. FIG. 1 shows an example of a mobile wireless communication system to which the present invention is applied. The illustrated mobile radio communication system is a core including an access network 8 accommodating a session controller (SRNC) 7 and a plurality of radio base stations 10 (10A, 10B, ... 10N), a home agent HA2, and an AAA server 3. AGW4 equipped with a plurality of U-AGW6s (6-1 to 6-m) is arranged between the network 1 and the AGW4. These U-AGW6 (6-1 to 6-m) are connected to C-AGW5 by the bus 40 in the AGW.
FIG. 2 shows the logical connection relationship of BS10, SRNC7, AGW4, HA2, and AAA server 3 shown in FIG. In the mobile wireless communication system of the present invention, the control message (control packet) is processed by the C-AGW5 as shown by the broken line, but the user data (user packet) is processed by a plurality of U- as shown by the solid line. Distributed processing is performed with AGW6-1 ~ 6-m.
As will be described later, the C-AGW5 is associated with the identifier of the mobile station (AT) that has succeeded in access authentication, and the information (user QoS profile) indicating the communication quality required by the AT and the tunnel for the AT. It has a management table for storing the addresses of the base station (BS) and U-AGW at both ends of. When the C-AGW5 receives the tunnel setting request message including the AT identifier from the BS10, the C-AGW5 searches the management table for the table entry having the AT identifier. If the table entry corresponding to the AT identifier is not registered in the management table, C-AGW5 determines the load status of each U-AGW from the management table, and U-AGW6-1 to U-AGW6- Select the U-AGW that should be the end of the tunnel so that the load is distributed by m, and notify the requesting BS of the address of the U-AGW.
In FIG. 2, user packets sent and received by AT20A pass through a tunnel 9A set between BS10A and U-AGW6-1, and user packets sent and received by AT20B are between BS10B and U-AGW6-2. User packets sent and received by the tunnel 9B and AT20C set in are forwarded via the tunnel 9C set between BS10N and U-AGW6-m.
Here, it is assumed that the AT20A moves from the communication range of BS10A to the communication range of BS10B as shown by the arrow. A table entry for AT20A has already been registered in the above management table when tunnel 9A is set. In this case, when the C-AGW5 receives the tunnel setting request for AT20A from BS10B, it searches the above management table for the address of U-AGW6-1 stored in association with the identifier of AT20A, and sends it to BS10B. On the other hand, the address of U-AGW6-1 is notified as the tunnel termination address. As a result, a new tunnel 9A'for AT20A will be set up between BS10B and U-AGW6-1. According to the present invention, since the existing tunnel 9A and the new tunnel 9A'are terminated by the same U-AGW, even if the BS changes, the transmission / reception packet of the AT20A is the same as the previous U-AGW6-. Transfer control can be performed by 1.
FIG. 5 shows the format of RRQ (Registration Request) message 80 of PMIP (Proxy Mobile IP) as an example of the tunnel setting request message transmitted from each base station (BS) 10 to C-AGW5. The RRQ message 80 consists of a message body 81 and an extension unit 82. The message body 81 is the Registration Request message described in Section 3.3 of Non-Patent Document 1 excluding the Extension part, and includes a message type 81a indicating that this message is an RRQ message, an IP address, and the like. It consists of information 81b. The extension unit 82 includes a mobile station identifier (ATID) 83, a binding type 84 indicating the type of tunnel, and other information 85.
Binding type 84 is whether the tunnel requested to be configured by RRQ message 80 is the first tunnel for the mobile station identified by ATID83 (Primary) or the second and subsequent tunnels configured for uplink (RL). (Reverse Link) Only "). The other information 85 includes, for example, information such as a service class requested by the AT.
FIG. 6 shows the format of PMIP's RRP message 90 that C-AGW5 returns to BS10 as a response message to RRQ message 80. The RRP message consists of a message body 91 and an extension unit 92. The message body 91 is the Registration Replay message described in Section 3.4 of Non-Patent Document 1 excluding the Extension part, and includes a message type 91a indicating that this message is an RRP message, an IP address, and the like. It consists of information 91b. The extension unit 92 consists of a mobile station identifier (ATID) 93, a tunnel endpoint 94, and other information 95. The IP address of any of U-AGW6-1 to U-AGW6-m selected by C-AGW5 is set in Tunnel Endpoint 94.
FIG. 7 shows the format of the User QoS Profile message 70 sent from the AAA server 3 to the C-AGW5. The User QoS Profile message consists of a control information unit 71, a mobile station identifier (ATID) 72, and a user QoS profile 73 indicating the communication service quality (QoS) guaranteed for the AT specified by ATID 72.
The control information unit 71 includes a message type indicating that this message 70 is a user QoS profile message, and other information. User QoS profile 73 includes, for example, communication service priority 74, maximum bandwidth (BW) 75 available for AT, and other information 76.
FIG. 8 is a block configuration diagram showing one embodiment of C-AGW5. The C-AGW5 is a control unit (processor) 51, a program memory 52 in which a protocol processing routine executed by the control unit 51 and other control programs are stored, a data memory 53, and a network interface connected to the core network 1. (NW-INF) 54-1 and network interface (NW-INF) 54-2 connected to access network 8, AGW interface (AGW-INF) 55 connected to bus 40 in AGW, and user interface 56. It consists of an internal bus 57 that interconnects these elements. A QoS information table 58, a U-AGW address table 59, and other data storage areas are formed in the data memory 53.
FIG. 9 is a block configuration diagram showing one embodiment of U-AGW6. The U-AGW6 includes a control unit (processor) 61, a program memory 62 in which various control programs executed by the control unit 61 are stored, a data memory 63, and a network interface (NW-INF) connected to the core network 1. ) 64-1 and network interface (NW-INF) 64-2 connected to access network 8, AGW interface (AGW-INF) 65 connected to bus 40 in AGW, and the internal interconnecting these elements. It consists of bus 67.
The network interface (NW-INF) 64-2 connected to the access network 8 together with the NW-INF64-2 of other U-AGWs in the same AGW4 via the packet switch provided with the AGW4. You may connect to access network 8.
FIGS. 10A and 10B show one embodiment of the QoS information table 58 formed in the memory 53 of the C-AGW5. The QoS information table 58 consists of a plurality of table entries indicating the correspondence between the mobile station identifier (ATID) 581 and the user QoS profile 582.
The user QoS profile 582, for example, shows the communication service or resource allocation priority 582A for the mobile station specified by ATID 581 and the maximum bandwidth (BW) that can be used by the mobile station, as shown in FIG. 10 (A). Shows 582B.
The user QoS profile 582 is, for example, in addition to the resource allocation priority 582A and maximum bandwidth (BW) 582B, as shown in FIG. 10 (B), and yet other such as the communication service class (Allowed Service Class). Information 582C may be included. The communication service class stores designated information of the communication service class guaranteed to the AT user by a prior contract, for example, a service class such as data communication, voice communication, and video communication.
FIG. 11 shows one embodiment of the U-AGW address table 59 formed in the memory 53 of the C-AGW5. The U-AGW address table 59 consists of a U-AGW address 592, a base station (BS) address 593, and a plurality of table entries indicating the binding type 594, in association with the mobile station identifier (ATID) 591.
U-AGW address 592 and BS address 593 indicate the IP addresses of the U-AGW and the base station, which are the terminations of the transfer tunnel for user packets, respectively. In the binding type 594, if the tunnel set between the base station indicated by BS address 593 and the U-AGW indicated by U-AGW address 592 is the first tunnel for the mobile station specified by ATID 591. "Primary" and "RL Only" are stored for the second and subsequent tunnels that coexist with the first tunnel. As for the binding type, for example, a management device for managing the session state of the mobile station is installed as a higher-level device of the base station, and each base station is set to "Primary" according to the control information sent from the management device. It should be decided whether it should be "RL Only" or "RL Only".
In FIG. 11, for example, the table entry EN1 is a tunnel set between the base station 10A having the IP address IP10A and the U-AGW6-1 having the IP address IP6-1 (tunnel in FIG. 2). 9A) indicates that it is the first tunnel for AT20A. In the table entry EN2, the tunnel set between the base station 10B having the IP address "IP10B" and the U-AGW6-2 having the IP address "IP6-2" (tunnel 9B in Fig. 2) is It shows that it is the first tunnel for AT20B.
In Fig. 12, AT20A, which was communicating through tunnel 9A, moved from the communication range of base station 10A to the communication range of base station 10B with the IP address "IP10B", and the base station 10B and U-AGW6-1 The state of the U-AGW address table 59 when a new tunnel (tunnel 9A'in FIG. 2) is set between them is shown.
FIG. 12 (A) shows the state of the U-AGW address table 59 when a plurality of tunnels coexist as a tunnel for AT20A. Here, in the table entry EN11, the tunnel set between the base station 10B having the IP address "IP10B" and the U-AGW6-1 having the IP address "IP6-1" is the second and subsequent tunnels for the AT20A. Indicates that it is a tunnel (RL Only).
FIG. 12B shows the state of the U-AGW address table 59 when the AT20A is handed over from the base station 10A to the base station 10B and a new tunnel 9A'is set in place of the existing tunnel 9A. .. When the AT20A is handed over from the base station 10A to the base station 10B, the BS address 593 of the table entry EN1 is rewritten from the IP address "IP10A" of the base station 10A to the IP address "IP10B" of the base station 10B. The binding type 594 of table entry EN1 is "Primary".
FIG. 13 shows a first embodiment of a communication sequence in the case of setting a tunnel for user data transfer between the base station 10 and the U-AGW 6 in the mobile wireless communication system of the present invention. Here, in the radio access network shown in FIG. 2, the communication sequence when the AT20A is connected to the core network 1 will be described as in FIG. However, the description will be simplified by applying the same reference numerals as those in FIG. 4 to the same sequence portion as in the conventional case described in FIG.
In the access authentication procedure SQ10a to SQ10c of the mobile station (AT) 20A, the AAA server 3 is AT.<u style="single">2</u>If 0A access authentication (including user authentication) is successful, AT will be applied to C-AGW5.<u style="single">2</u>Notify the 0A user of the User QoS profile, which indicates the acceptable quality of service quality (SQ13).
When the control unit 51 of the C-AGW 5 receives the user QoS profile from the AAA server 3, the control unit 51 executes the user QoS profile reception processing routine 100 shown in FIG. In the user QoS profile reception processing routine 100, the control unit 51 checks whether or not the AT identifier (ATID) notified from the AT20A in step SQ12 of FIG. 13 has been registered as the ATID561 in the QoS information table 58 (step 101). ). The control unit 51 terminates this routine if the ATID of the AT20A is already registered in the QoS information table 58, and if the ATID of the AT20A is not registered in the QoS information table 58, the ATID and the AAA server 3 A new table entry indicating the correspondence with the user QoS profile notified by is added to the QoS information table 58 (102), and this routine is terminated.
When the access authentication of the AT user is completed, the BS10A executes the configuration for wirelessly connecting the AT20A (SQ14a, SQ14b), and then connects to the C-AGW5 with a tunnel for user data transfer including the AT20A identifier (ATID). Send a configuration request (PMIP RRQ) message (SQ15).
When the control unit 51 of the C-AGW5 receives the above tunnel setting request (PMIP RRQ) message, the U-AGW (in this example, the U-AGW6) to be assigned to the AT20A from the U-AGW6-1 to 6-m. -1) is selected and a response message (PMIP RRP) containing the IP address of the U-AGW is returned to BA10A as the tunnel termination (SQ18). At this time, the control unit 51 of the C-AGW 5 associates the IP address of the selected U-AGW with the ATID indicated by the PMIP RRQ message, and the IP address of the BS that is the source of the PMIP RRQ message. A new table entry indicating the binding type indicated by the above PMIP RRQ message is recorded in the U-AGW address table of memory 53.
FIG. 15 shows an RRQ reception processing routine 200 executed by the control unit 51 when a tunnel setting request (PMIP RRQ) message is received. In the RRQ reception processing routine 200, the control unit 51 checks whether or not the ATID indicated by the received PMIP RRQ message is registered as ATID591 in the U-AGW address table 59 (step 201).
In this example, the ATID indicated by the PMIP RRQ message has not yet been registered in the U-AGW address table 59. In this case, the control unit 51 assigns the new U-AGW (U-AGW6-1 in this example) to the AT20A (210), and assigns the above ATID and the IP address of the U-AGW to the U-AGW address table 59. , Added a new table entry showing the correspondence between the IP address of the PMIP RRQ message source BS (BS10A) and the binding type indicated by the PMIP RRQ message (204), and added the PMIP RRQ message source BS (BS10A). Returns a response message (PMIP RRP) containing the above U-AGW6-1 IP address (IP6-1) as the Endpoint (205, SQ16 in FIG. 13), and terminates this routine.
If the ATID indicated by the PMIP RRQ message is already registered as ATID 591 in the U-AGW address table 59, the control unit 51 sets the U-AGW address 592 of the table entry registered in the U-AGW address table 59. Assign the indicated U-AGW to the AT20A (202) and determine the binding type indicated by the PMIP RRQ message (203).
When the binding type is "RL Only", that is, the mobile wireless communication system shown in FIG. 1 can set multiple tunnels for the same AT as described in FIG. 12 (A). If, in step 204, the control unit 51 displays the above ATID, the IP address of the U-AGW, and the IP address of the source BS (BS10A) of the PMIP RRQ message in the U-AGW address table 59. After adding a new table entry showing the correspondence with the binding type indicated by the PMIP RRQ message, the response message (PMIP RRP) is returned to the source BS (BS10A) of the PMIP RRQ message (205), and this routine To finish.
When the binding type is "Primary", that is, the mobile wireless communication system hands over the AT between base stations as described in FIG. 12 (B).<u style="single">To do</u>In the case of a system configuration, the control unit 51 rewrites the BS address 593 of the table entry registered in the U-AGW address table 59 (206). After that, the control unit 51 returns a response message (PMIP RRP) including the IP address of the U-AGW assigned in step 202 as the endpoint to the source BS (BS10A) of the PMIP RRQ message (207), and before the handover. Release the existing tunnel used for (208) and exit this routine.
FIG. 16 shows a detailed flowchart of the new U-AGW allocation (210) in the RRP reception processing routine 200. In the allocation of the new U-AGW (210), the control unit 51 calculates the estimated value of the communication resource already consumed for each U-AGW included in the AGW 4 (211), and determines the U-AGW with the minimum consumed resource. Select (212) and assign it to AT. As for the resource consumption for each U-AGW, for example, as shown in FIG. 17, a U-AGW status table 300 indicating the resource consumption amount 302 for each IP address 301 of the U-AGW is prepared in the memory 53, and the U-AGW is used. It can be estimated by accumulating the communication resource amount of each U-AGW obtained from the AGW address table 59 and the QoS information table 58 as the consumption resource amount 302.
For example, when the total value of the maximum BW guaranteed by each U-AGW to the AT is adopted as the resource consumption 302, the control unit 51 reads the values of ATID 591 and U-AGW address 592 from the U-AGW address table 59. , The value of the maximum BW corresponding to ATID591 is searched from the QoS information table 58, and the maximum BW found is found.<u style="single">528B</u>The value of may be accumulated in the U-AGW status table 300, assuming that the resource consumption amount 302 corresponding to the U-AGW address 592. However, when multiple table entries with the same ATID591 are registered in the U-AGW address table 59 as in the entries EN1 and EN11 shown in FIG. 11, the cumulative total of the maximum BW582B is the first searched table. Make entries and exclude the remaining table entries with the same ATID from the maximum BW cumulative target.
FIG. 18 shows a flowchart in the case where the total value of the maximum BW guaranteed to the AT by each U-AGW is used as the consumption resource as one example of the allocation of the new U-AGW (210). In this embodiment, the control unit 51 uses the U-AGW status table 300 described above to calculate the total value of the maximum BW582B already guaranteed by the AT for each U-AGW (IP address) (211A). , Select the U-AGW with the smallest total value of maximum BW (resource consumption 302) (212A) and assign it to AT. According to this embodiment, since the loads of a plurality of U-AGWs 6-1 to 6-m can be averaged, it is possible to prevent a data packet transfer delay from occurring in a specific U-AGW.
FIG. 19 shows another example of the allocation of the new U-AGW (210), in which the number of tunnels (the number of ATs) having the highest communication service priority connected to each U-AGW is adopted as the consumption resource. The flowchart is shown. In this embodiment, the control unit 51 uses the U-AGW status table 300 described above to count the number of ATs having a priority of 582A as the maximum priority for each U-AGW (IP address). (211B), select the U-AGW with the lowest number of ATs with the highest priority (resource consumption 302) and assign it to the AT (212B). According to this embodiment, U-AGWs can be assigned so that a large number of ATs (users) whose high priority is guaranteed do not concentrate on a specific U-AGW.
By selecting the U-AGW using QoS information such as the maximum bandwidth and service priority described above, tunnels for high-priority data packets can be concentrated on a specific U-AGW, or the communication speed or bandwidth used. Large AT tunnels can be avoided from concentrating on a particular U-AGW.
FIG. 20 shows yet another embodiment of the new U-AGW allocation (210). In this embodiment, as shown in FIG. 10B, the service class 5 stored in the QoS information table 58 in association with the ATID 581.<u style="single">8</u>Select U-AGW using 2C. Here, for the sake of simplicity, service class 5<u style="single">8</u>2<u style="single">C</u>Has two classes, "data" and "voip". As a configuration of AGW4, U-AGW6-1 is optimized for packet transfer for voip, and other U-AGW6-2 ~ 6-m Is optimized for packet forwarding for data.
The control unit 51 of the C-AGW5 uses the ATID included in the RRQ message received from the BS10A as a search key to obtain the service class 5 from the QoS information table 58.<u style="single">8</u>Search 2C and check if the service class is "voip" (213). Acceptable service class 5<u style="single">8</u>When 2C is "voip", the control unit 51 selects U-AGW6-1 and assigns it to AT20A. When the searched service class 592C is other than "voip", the control unit 51 uses the procedure described in Fig. 16 from among U-AGW6-2 to 6-m to minimize the estimated value of consumed resources. Select AGW (211 and 212) and assign it to AT20A. The procedure described with reference to FIGS. 18 and 19 may be applied to steps 211 and 212 of FIG.
When multiple U-AGWs are optimized for data packet transfer for voip in the configuration of AGW4, the control unit 51 follows the procedure shown in FIG. 16 in step 214 of FIG. 20 to perform multiple U-AGWs for voip. From the U-AGW, the U-AGW with the lowest estimated value of consumed resources may be selected.
Here, the U-AGW for voip and the U-AGW for data are realized by optimizing hardware or software. Hardware optimization includes, for example, increasing the capacity of the data memory 63, increasing the speed of the control unit (processor) 61, and increasing the speed of the NW INF64. Further, as software optimization, for example, specialization of software stored in the program memory 62, addition of functions according to the service type, and the like can be mentioned.
Here, the case where the service classes are "data" and "voip" has been described, but the service classes may be 3 or more. Also, the classification of data and voip is just one example, and communication services may be classified from different perspectives.
In the embodiment, the service class 5 stored in the QoS information table 58 as part of the user QoS profile 582.<u style="single">8</u>The U-AGW to be assigned to each AT is selected based on 2C, but the control unit 51 selects the U-AGW by referring to the information other than the service class in step 213 of the new U-AGW allocation process 210. You may try to do it. For example, in U-AGW6-1 to 6-m, a high-speed U-AGW6-j dedicated for forwarding wideband data packets is prepared, and the control unit 51 has a maximum BW of a certain value or more. The above U-AGW6-j may be assigned to AT. A plurality of U-AGWs for forwarding broadband data packets may be provided in the AGW4, and the U-AGWs may be allocated so that the load is distributed among these dedicated U-AGWs.
For the selection of U-AGW, the QoS information of the link layer between AT20 and BS10 (radio section) may be used. There is a correlation between the QoS of the wireless link layer and the QoS of the IP layer, which is the upper layer, and users who require high QoS at the wireless link layer also need high QoS at the IP layer. Therefore, even if the QoS information of the wireless link layer is adopted as an index of the consumption of communication resources and the U-AGW to be assigned to each AT is selected so that the load is distributed among the U-AGWs. Good.
Returning to FIG. 13, when the BS10A receives the PMIP RRP message from the C-AGW5, the BS10A and the U-AGW6-1 follow the IP address of the C-AGW6-1 indicated by the Endpoint of the received message (IP6-1). Set up a tunnel in between (SQ18). This allows AT<u style="single">2</u>0A is in a state where user data can be communicated with the communication partner via BS10A and U-AGW7 (SQ19a, SQ19b, SQ19c). As described above, according to this embodiment, it is possible to set a tunnel in which the load is distributed among a plurality of U-AGWs.
Next, with reference to FIG. 21, a handover communication sequence executed when the AT20A moves from the communication range of BS10A shown in FIG. 2 to the communication range of BS10B will be described. However, in FIG. 21, since the sequences SQ10a to SQ19c are the same as those in FIG. 13, the description thereof will be omitted.
AT that was communicating via the tunnel set between BS10A and U-AGW6-1<u style="single">2</u>It is assumed that 0A moves to the communication range (service area) of BS10B. AT<u style="single">2</u>0A periodically measures the quality of the received signals (pilot signals) from BS10A and BS10B, or monitors the state of the radio transmission line of each base station by the control information communicating with these base stations. AT<u style="single">2</u>0A starts the handover from BS10A to BS10B when the condition of the radio propagation path with the new BS10B becomes better than the condition of the radio propagation path with BS10A. AT<u style="single">2</u>Handover of 0A is for base stations (BS10A, BS10<u style="single">B)</u>It may be executed on the initiative.
BS10B is AT<u style="single">2</u>When a handover request is received from 0A, the AAA server goes through SRNC7 and C-AGW5.<u style="single">3</u>With AT<u style="single">2</u>Perform the 0A access authentication procedure (SQ20a, SQ20b, SQ20c). At this time, as in the first access authentication procedure (SQ10a, SQ10b, SQ10c) detailed in FIG. 13, the IP address of C-AGW5 in which BS10B is stored is notified from C-AGW5 to BS10B, and AT<u style="single">2</u>The AT identifier (ATID) is notified from 0A to C-AGW5, and the user QoS profile corresponding to the above ATID is notified from AAA server 3 to C-AGW5.
When the control unit 51 of the C-AGW 5 receives the user QoS profile from the AAA server 3, the control unit 51 executes the user QoS profile reception processing routine 100 shown in FIG. This time, in the QoS information table 58, the table entry corresponding to the ATID of AT20A has already been registered, so the QoS information table 58 is not updated. When the access authentication procedure (SQ20a, SQ20b, SQ20c) is completed, BS10B sends a tunnel setting request (PMIP RRQ) message to C-AGW5 after executing the configuration (SQ24a, SQ24b) for wirelessly connecting the AT20A. (SQ25). The PMIP RRQ message sent from BS10B to C-AGW5 is AT.<u style="single">2</u>An identifier (ATID) of 0A and a binding type "Primary" are added.
When the control unit 51 of the C-AGW5 receives the PMIP RRQ message from the BS10B, the control unit 51 executes the RRQ reception processing routine 200 shown in FIG. 15 to select the U-AGW to be assigned to the AT20A. This time, since the table entry EN1 corresponding to the AT20A identifier (ATID) has already been registered in the U-AGW address table 59, the control unit 51 is indicated by the U-AGW address 592 of the above table entry EN1. Select U-AGW6-1 and return the response message (PMIP RRP) with the IP address "IP6-1" of U-AGW6-1 specified in Endpoint to BS1-B (SQ26). At this time, the control unit 51 updates the table entry EN1 of the U-AGW address table 59 in step 206 of the RRQ reception processing routine 200, as shown in FIG. 12 (B).
After transmitting the PMIP RRP message, the control unit 51 releases the tunnel 9A set between the BS10A and the U-AGW6-1 by, for example, transmitting a tunnel release message to the BS10A (SQ27). To release the tunnel, the control unit 51 may instruct the U-AGW6-1 to release the tunnel via the bus in the AGW, and the U-AGW6-1 may send a tunnel release message to the BS10A. The existing tunnel is opened, for example, by timer control when a predetermined time elapses after the PMIP RRP message is transmitted.
When BS10B receives a response message (PMIP RRP) from C-AGW5, it sets a tunnel with U-AGW6-1 specified by Endpoint (SQ28). This allows AT<u style="single">2</u>0A is in a state where user data can be communicated via BS10B and U-AGW6-1 (SQ29a, SQ29b, SQ29c).
According to the present invention, since the C-AGW5 can assign the same U-AGW6-1 as before the handover as the tunnel termination after the handover of the AT20A, it is necessary to change the route between the AGW4 and the core network. It is possible to realize an inter-base station handover that does not occur.
Next, with reference to FIG. 22, a communication sequence when a plurality of tunnels are set in parallel for the AT20A will be described. However, the description of the sequence common to that in FIG. 21 will be omitted or simplified.
AT that was communicating via the tunnel set between BS10A and U-AGW6-1<u style="single">2</u>It is assumed that 0A moves to the communication range (service area) of BS10B. In this embodiment, AT<u style="single">2</u>When 0A moves within the communication range of BS10B, a new tunnel 9A'via BS10B is set up coexisting with the existing tunnel 9A via BS10A.
BS10B is AT<u style="single">2</u>When 0A is detected, it will be AT to and from AAA server 2 via SRNC7 and C-AGW5.<u style="single">2</u>Perform the 0A access authentication procedure (SQ20a, SQ20b, SQ20c). At this time, C-AGW5 notifies BS10B of the IP address of C-AGW5 in which BS10B is stored, and AT<u style="single">2</u>The AT identifier (ATID) is notified from 0A to C-AGW5, and the user QoS profile corresponding to the above ATID is notified from AAA server 3 to C-AGW5.
When the control unit 51 of the C-AGW 5 receives the user QoS profile from the AAA server 3, the control unit 51 executes the user QoS profile reception processing routine 100 shown in FIG. This time, in the QoS information table 58, the table entry corresponding to the ATID of AT20A has already been registered, so the QoS information table 58 is not updated.
When the access authentication procedure (SQ20a, SQ20b, SQ20c) is completed, BS10B sends a tunnel setting request (PMIP RRQ) message to C-AGW5 after executing the configuration (SQ24a, SQ24b) for wirelessly connecting the AT20A. (SQ25'). Here, AT after the first tunnel (primary) 9A in both Reverse Link / Forward Link directions is set.<u style="single">2</u>As a new tunnel 9A'for 0A, it is assumed that a tunnel (RL only) only in the upstream direction (Reverse Link) can be set. Such a tunnel setting function is provided in the above-mentioned UMB (Ultra Mobile Broadband) wireless system.
The PMIP RRQ message sent from BS10B to C-AGW5 is AT.<u style="single">2</u>The identifier (ATID) of 0A and the tunnel for which the setting was requested are AT.<u style="single">2</u>A binding type "RL only" is added to indicate that it is the second and subsequent tunnels for 0A. When the control unit 51 of the C-AGW5 receives the PMIP RRQ message from the BS10B, the control unit 51 executes the RRQ reception processing routine 200 shown in FIG. 15 to select the U-AGW to be assigned to the AT20A. This time, the table entry EN1 corresponding to the AT20A identifier (ATID) has already been registered in the U-AGW address table 59. Therefore, the control unit 51 selects U-AGW6-1 indicated by the U-AGW address 592 of the above table entry EN1 in step 202 of the RRQ reception processing routine 200, and in step 204, the U-AGW address table 59 is displayed. As shown in Fig. 12 (A), after the new table entry EN11 is added, the response message (PMIP RRP) with the IP address "IP6-1" of U-AGW6-1 specified in Endpoint is returned to BS1-B. (SQ26).
When BS10B receives a response message (PMIP RRP) from C-AGW5, it sets a tunnel with U-AGW6-1 specified by Endpoint (SQ28). This allows AT<u style="single">2</u>0A is in a state where user data can be communicated via BS10B and U-AGW6-1 (SQ29a, SQ29b, SQ29c).
It takes a certain amount of time to set up the tunnel between BS and U-AGW6. So, for example, AT<u style="single">2</u>When 0A moves within the communication range of BS10B, AT<u style="single">2</u>Immediately hand over 0A from BS10A to BS10B, AT<u style="single">2</u>When 0A returns to the communication range of BS10A, the handover from BS10B to BS10A will occur, and the load of C-AGW5 will increase due to the frequent occurrence of handover between BSs.
According to this embodiment, since a tunnel is set in parallel between two BSs (BS10A and BS10B in FIG. 22) and AGW4, which are likely to cause handover, the AT20A is the boundary between BS10A and BS10B. Even if you wander around, you can prevent the load on the C-AGW5 from increasing due to the occurrence of handover between BSs.
In the present invention, AT via BS10A<u style="single">2</u>AT via BS10B after setting the first tunnel 9A for 0A<u style="single">2</u>When setting the second tunnel 9A'for 0A, the control unit 51 of C-AGW5 selects the U-AGW so that the end of the second tunnel is the same as the end of the first tunnel. Because there is AT<u style="single">2</u>Even if 0A moves, within AGW4, AT with the same U-AGW<u style="single">2</u>It can transfer 0A data packets. Therefore, according to the present invention, for example, AT<u style="single">2</u>When the BS that relays the uplink packet transmitted from 0A is switched, the uplink packet can be continuously processed by the same U-AGW (U-AGW6-1 in this example).
If the first and second tunnels used by the same AT are terminated by different U-AGWs, when the AT moves, the U-AGW also switches in conjunction with the BS, so especially from core network 1 to AT. In the transfer of the outgoing packet, complicated control such as data transfer and signal transfer between U and AGW in AGW4 is required, and in the present invention, such special control can be eliminated. ..
<figref num="1">The figure which shows an example of the mobile wireless communication system to which this invention is applied.</figref><figref num="2">The figure which showed the logical connection relationship of BS10, SRNC7, AGW4, HA2, and AAA server 3 in the mobile wireless communication system shown in FIG.</figref><figref num="3">The figure which shows an example of the conventional radio access network.</figref><figref num="4">The figure for demonstrating the setting sequence of the tunnel for user data transfer in the radio access network shown in FIG.</figref><figref num="5">A format diagram showing an example of a tunnel setting request message sent from BS10 to C-AGW5.</figref><figref num="6">A format diagram showing an example of a response message returned from C-AGW5 to BS10.</figref><figref num="7">Format diagram of the User QoS Profile message sent from AAA Server 3 to C-AGW5.</figref><figref num="8">Block configuration diagram showing one embodiment of C-AGW5.</figref><figref num="9">A block configuration diagram showing one embodiment of U-AGW6.</figref><figref num="10">The figure which shows 1 Example of the QoS information table 58 formed in the memory 53 of C-AGW5.</figref><figref num="11">The figure which shows 1 Example of the U-AGW address table 59 formed in the memory 53 of C-AGW5.</figref><figref num="12">The figure which shows the content change of the U-AGW address table 59.</figref><figref num="13">The communication sequence diagram for demonstrating the function of C-AGW5 of this invention.</figref><figref num="14">The flowchart which shows 1 Example of the user QoS profile reception processing routine 100 executed by the control part 51 of C-AGW5.</figref><figref num="15">The flowchart which shows 1 Example of RRQ reception processing routine 200 executed by the control part 51 of C-AGW5.</figref><figref num="16">Detailed flowchart of new U-AGW allocation (210) in RRP reception processing routine 200.</figref><figref num="17">The figure which shows 1 Example of the U-AGW state table 300 formed in the memory 53 of C-AGW5.</figref><figref num="18">The flowchart which shows 1 Example of the allocation (210) of the new U-AGW.</figref><figref num="19">A flowchart showing another embodiment of the new U-AGW allocation (210).</figref><figref num="20">A flowchart showing still another embodiment of the new U-AGW allocation (210).</figref><figref num="21">The communication sequence diagram for demonstrating the function of C-AGW5 of this invention.</figref><figref num="22">The communication sequence diagram for demonstrating the function of C-AGW5 of this invention.</figref>
Code description
1: Core net,<u style="single">2</u>: Home Agent (HA),<u style="single">3</u>: AAA server, 4: AGW, 5: C-AGW, 6: U-AGW, 7: SRNC, 8: Access network, 10: Base station (BS), 20: Mobile station (AT), 51, 61: Control Department, 52, 62: Program memory, 53, 63: Data memory, 54, 64: Network interface, 55, 65: AGW interface, 56: User interface, 58: QoS information table, 58: U-AGW address table, 300 : U-AGW status table.
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US10595350B2 | Cited by | United States of America | Applicant |
| US10701744B2 | Cited by | United States of America | Applicant |
| US10827543B2 | Cited by | United States of America | Applicant |
| CN107079507A | Cited by | China | Search report |
| US11432351B2 | Cited by | United States of America | Applicant |
| US10638527B2 | Cited by | United States of America | Applicant |
| JP2005027192A | Cites | Japan | – |
6 members in 2 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 2008099326 | Japan | A | |
| JP20080099326 | – | – | – |
Members6
| Document | Office | Kind | |
|---|---|---|---|
| US2009252133A1 | United States of America | A1 | |
| JP2009253678A | Japan | A | |
| US8315668B2 | United States of America | B2 | |
| US2013058299A1 | United States of America | A1 | |
| JP5203780B2This record | Japan | B2 | |
| US8923922B2 | United States of America | B2 |
12 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| 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 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 | |
| Notification of change in applicantJAPANESE INTERMEDIATE CODE: A712A711 | A711 |
Numbers
- Publication
- 5203780
- Publication, DOCDB
- 5203780
- Publication, EPODOC
- JP5203780B
- Application
- 99326
- Application, DOCDB
- 2008099326
- Application, EPODOC
- JP20080099326
Titles2
- Japanese
- 移動無線通信システムおよびアクセスゲートウェイ
- English
- Mobile wireless communication system and access gateway
Classification
- CPC, 3
- H04W76/12
- H04W88/16
- H04W28/086
- IPC, 2
- H04W28 08
- H04W88 16