Service continuity ensuring method, control plane gateway, and mobility management network element
15 claims: 6 independent, 9 dependent
- 1サービス継続性保証方法であって、 制御プレーンゲートウェイにより、モビリティ管理ネットワーク要素からユーザ機器の現在位置情報を受信するステップ(201)と、 前記制御プレーンゲートウェイにより、前記ユーザ機器の前記現在位置情報に従って前記ユーザ機器用の少なくとも1つの転送ユーザプレーンゲートウェイを選択するステップ(202)であって、前記少なくとも1つの転送ユーザプレーンゲートウェイは、前記ユーザ機器のダウンリンクユーザプレーンデータを転送するために使用される、ステップと、 前記制御プレーンゲートウェイにより、前記ユーザ機器のために、前記ユーザ機器に奉仕するソースユーザプレーンゲートウェイと前記転送ユーザプレーンゲートウェイとの間のデータ転送トンネル、および前記転送ユーザプレーンゲートウェイと前記ユーザ機器に奉仕するターゲット基地局との間のデータ転送トンネルを確立するステップ(203)であって、両方のデータ転送トンネルが、前記ユーザ機器の移動プロセスにおいて、前記ユーザ機器の前記ダウンリンクユーザプレーンデータを送信するために使用される、ステップと を備える、方法。
- 2前記少なくとも1つの転送ユーザプレーンゲートウェイが第1のユーザプレーンゲートウェイであり、前記制御プレーンゲートウェイが、前記ユーザ機器が現在位置領域に移動した後に使用されるサービング制御プレーンゲートウェイであり、前記制御プレーンゲートウェイが、前記ユーザ機器が前記現在位置領域に移動する前に使用されたサービング制御プレーンゲートウェイと同じであり、前記モビリティ管理ネットワーク要素が、前記ユーザ機器が前記現在位置領域に移動した後に使用されるサービングモビリティ管理ネットワーク要素であり、 前記制御プレーンゲートウェイにより、前記ユーザ機器のために、前記ユーザ機器に奉仕するソースユーザプレーンゲートウェイと前記転送ユーザプレーンゲートウェイとの間のデータ転送トンネル、および前記転送ユーザプレーンゲートウェイと前記ユーザ機器に奉仕するターゲット基地局との間のデータ転送トンネルを確立する前記ステップが、 前記制御プレーンゲートウェイにより、前記モビリティ管理ネットワーク要素から第1の要求を受信するステップであって、前記第1の要求が前記ターゲット基地局のルーティング情報を搬送する、ステップと、 前記制御プレーンゲートウェイにより、前記第1のユーザプレーンゲートウェイに第2の要求を送信するステップであって、前記第2の要求が、前記第1のユーザプレーンゲートウェイと前記ターゲット基地局との間の前記データ転送トンネル、および前記第1のユーザプレーンゲートウェイと前記ソースユーザプレーンゲートウェイとの間の前記データ転送トンネルを確立するように、前記第1のユーザプレーンゲートウェイに要求するために使用され、前記第2の要求が、前記ターゲット基地局の前記ルーティング情報および前記ソースユーザプレーンゲートウェイのルーティング情報を搬送する、ステップと 前記制御プレーンゲートウェイにより、前記ソースユーザプレーンゲートウェイに第3の要求を送信するステップであって、前記第3の要求が、前記ソースユーザプレーンゲートウェイと前記第1のユーザプレーンゲートウェイとの間の前記データ転送トンネルを確立するように、前記ソースユーザプレーンゲートウェイに要求するために使用され、前記第3の要求が、前記第1のユーザプレーンゲートウェイのルーティング情報を搬送する、ステップと を備える、請求項1に記載の方法。
- 3前記少なくとも1つの転送ユーザプレーンゲートウェイが第2のユーザプレーンゲートウェイおよび第3のユーザプレーンゲートウェイを備え、前記制御プレーンゲートウェイが、前記ユーザ機器が現在位置領域に移動した後に使用されるサービング制御プレーンゲートウェイであり、前記制御プレーンゲートウェイが、前記ユーザ機器が前記現在位置領域に移動する前に使用されたサービング制御プレーンゲートウェイと同じであり、前記モビリティ管理ネットワーク要素が、前記ユーザ機器が前記現在位置領域に移動した後に使用されるサービングモビリティ管理ネットワーク要素であり、 前記制御プレーンゲートウェイにより、前記ユーザ機器のために、前記ユーザ機器に奉仕するソースユーザプレーンゲートウェイと前記転送ユーザプレーンゲートウェイとの間のデータ転送トンネル、および前記転送ユーザプレーンゲートウェイと前記ユーザ機器に奉仕するターゲット基地局との間のデータ転送トンネルを確立する前記ステップが、 前記制御プレーンゲートウェイにより、前記モビリティ管理ネットワーク要素から第1の要求を受信するステップであって、前記第1の要求が前記ユーザ機器の前記ターゲット基地局のルーティング情報を搬送する、ステップと、 前記制御プレーンゲートウェイにより、前記第2のユーザプレーンゲートウェイに第2の要求を送信するステップであって、前記第2の要求が、前記第2のユーザプレーンゲートウェイと前記ターゲット基地局との間のデータ転送トンネル、および前記第2のユーザプレーンゲートウェイと前記第3のユーザプレーンゲートウェイとの間のデータ転送トンネルを確立するように、前記第2のユーザプレーンゲートウェイに要求するために使用され、前記第2の要求が、前記ターゲット基地局の前記ルーティング情報および前記第3のユーザプレーンゲートウェイのルーティング情報を搬送する、ステップと、 前記制御プレーンゲートウェイにより、前記第3のユーザプレーンゲートウェイに第3の要求を送信するステップであって、前記第3の要求が、前記第3のユーザプレーンゲートウェイと前記第2のユーザプレーンゲートウェイとの間の前記データ転送トンネル、および前記第3のユーザプレーンゲートウェイと前記ソースユーザプレーンゲートウェイとの間のデータ転送トンネルを確立するように、前記第3のユーザプレーンゲートウェイに要求するために使用され、前記第3の要求が、前記第2のユーザプレーンゲートウェイのルーティング情 報を 搬送する、ステップと、 前記制御プレーンゲートウェイにより、前記ソースユーザプレーンゲートウェイに第4の要求を送信するステップであって、前記第4の要求が、前記ソースユーザプレーンゲートウェイと前記第3のユーザプレーンゲートウェイとの間の前記データ転送トンネルを確立するように、前記ソースユーザプレーンゲートウェイに要求するために使用され、前記第4の要求が、前記第3のユーザプレーンゲートウェイの前記ルーティング情報を搬送する、ステップと を備える、請求項1に記載の方法。
- 4前記少なくとも1つの転送ユーザプレーンゲートウェイが第1のユーザプレーンゲートウェイであり、前記制御プレーンゲートウェイが、前記ユーザ機器が現在位置領域に移動した後に使用されるサービング制御プレーンゲートウェイであり、前記制御プレーンゲートウェイが、前記ユーザ機器が前記現在位置領域に移動する前に使用されたサービング制御プレーンゲートウェイとは異なり、前記モビリティ管理ネットワーク要素が、前記ユーザ機器が前記現在位置領域に移動した後に使用されるサービングモビリティ管理ネットワーク要素であ り、 前 記制御プレーンゲートウェイにより、前記ユーザ機器のために、前記ユーザ機器に奉仕するソースユーザプレーンゲートウェイと前記転送ユーザプレーンゲートウェイとの間のデータ転送トンネル、および前記転送ユーザプレーンゲートウェイと前記ユーザ機器のターゲット基地局との間のデータ転送トンネルを確立する前記ステップが、 前記制御プレーンゲートウェイにより、前記モビリティ管理ネットワーク要素から第1の要求を受信するステップであって、前記第1の要求が前記ターゲット基地局のルーティング情報を搬送する、ステップと、 前記制御プレーンゲートウェイにより、前記第1のユーザプレーンゲートウェイに第2の要求を送信するステップであって、前記第2の要求が、前記第1のユーザプレーンゲートウェイと前記ターゲット基地局との間の前記データ転送トンネル、および前記第1のユーザプレーンゲートウェイと前記ソースユーザプレーンゲートウェイとの間の前記データ転送トンネルを確立するように、前記第1のユーザプレーンゲートウェイに要求するために使用され、前記第2の要求が、前記ターゲット基地局の前記ルーティング情 報を 搬送する、ステップと を備える、請求項1に記載の方法。
- 5前記少なくとも1つの転送ユーザプレーンゲートウェイが第2のユーザプレーンゲートウェイおよび第3のユーザプレーンゲートウェイを備え、前記制御プレーンゲートウェイが、前記ユーザ機器が現在位置領域に移動した後に使用されるサービング制御プレーンゲートウェイであり、前記制御プレーンゲートウェイが、前記ユーザ機器が前記現在位置領域に移動する前に使用されたサービング制御プレーンゲートウェイとは異なり、前記モビリティ管理ネットワーク要素が、前記ユーザ機器が前記現在位置領域に移動した後に使用されるサービングモビリティ管理ネットワーク要素であ り、 前 記制御プレーンゲートウェイにより、前記ユーザ機器のために、前記ユーザ機器に奉仕するソースユーザプレーンゲートウェイと前記転送ユーザプレーンゲートウェイとの間のデータ転送トンネル、および前記転送ユーザプレーンゲートウェイと前記ユーザ機器に奉仕するターゲット基地局との間のデータ転送トンネルを確立する前記ステップが、 前記制御プレーンゲートウェイにより、前記モビリティ管理ネットワーク要素から第1の要求を受信するステップであって、前記第1の要求が前記ターゲット基地局のルーティング情報を搬送する、ステップと、 前記制御プレーンゲートウェイにより、前記第2のユーザプレーンゲートウェイに第2の要求を送信するステップであって、前記第2の要求が、前記第2のユーザプレーンゲートウェイと前記ターゲット基地局との間のデータ転送トンネル、および前記第2のユーザプレーンゲートウェイと前記第3のユーザプレーンゲートウェイとの間のデータ転送トンネルを確立するように、前記第2のユーザプレーンゲートウェイに要求するために使用され、前記第2の要求が、前記ターゲット基地局の前記ルーティング情 報を 搬送する、ステップと、 前記制御プレーンゲートウェイにより、前記第3のユーザプレーンゲートウェイに第3の要求を送信するステップであって、前記第3の要求が、前記第3のユーザプレーンゲートウェイと前記第2のユーザプレーンゲートウェイとの間の前記データ転送トンネル、および前記第3のユーザプレーンゲートウェイと前記ソースユーザプレーンゲートウェイとの間のデータ転送トンネルを確立するように、前記第3のユーザプレーンゲートウェイに要求するために使用され、前記第3の要求が、前記第2のユーザプレーンゲートウェイのルーティング情 報を 搬送する、ステップと を備える、請求項1に記載の方法。
- 6前記制御プレーンゲートウェイにより、ターゲットユーザプレーンゲートウェイにセッション作成要求を送信するステップであって、前記セッション作成要求が、前記ユーザ機器用の前記ターゲットユーザプレーンゲートウェイ上に、ユーザプレーンデータ伝送用のベアラコンテキストを作成するために使用され、各々の作成されたベアラコンテキストが前記ターゲットユーザプレーンゲートウェイのルーティング情報を備え、前記ターゲットユーザプレーンゲートウェイが前記ユーザ機器の現在位置領域に対応するサービングユーザプレーンゲートウェイである、ステップ をさらに備える、請求項1から5のいずれか一項に記載の方法。
- 7前記制御プレーンゲートウェイにより、前記モビリティ管理ネットワーク要素を介して前記ターゲット基地局に前記ターゲットユーザプレーンゲートウェイの前記ルーティング情報を送信するステップ をさらに備える、請求項6に記載の方法。
- 8前記制御プレーンゲートウェイにより、前記モビリティ管理ネットワーク要素を介して前記ターゲット基地局に前記第1のユーザプレーンゲートウェイの前記ルーティング情報を送信するステップ をさらに備える、請求項2または4に記載の方法。
- 9前記第1のユーザプレーンゲートウェイが、前記ユーザ機器の前記現在位置情報に従って、前記ユーザ機器用の前記制御プレーンゲートウェイによって選択されたサービングユーザプレーンゲートウェイである、 請求項2、4、または8に記載の方法。
- 10前記制御プレーンゲートウェイにより、前記モビリティ管理ネットワーク要素を介して前記ターゲット基地局に前記第2のユーザプレーンゲートウェイの前記ルーティング情報を送信するステップ をさらに備える、請求項3または5に記載の方法。
- 11サービス継続性保証方法であって、 ターゲットモビリティ管理ネットワーク要素により、ユーザ機器に奉仕するソースモビリティ管理ネットワーク要素から転送再配置要求を受信するステップ(901)であって、前記転送再配置要求が前記ユーザ機器の現在位置情報を搬送する、ステップと、 前記ターゲットモビリティ管理ネットワーク要素により、前記ユーザ機器の前記現在位置情報に従って前記ユーザ機器のターゲット制御プレーンゲートウェイを選択するステップ(902)と、 前記ターゲットモビリティ管理ネットワーク要素により、前記ターゲット制御プレーンゲートウェイに前記ユーザ機器の前記現在位置情報を送信するステップ(903)であって、その結果、前記ターゲット制御プレーンゲートウェイが、前記ユーザ機器の前記現在位置情報に従って前記ユーザ機器の転送ユーザプレーンゲートウェイを決定し、少なくとも1つの転送ユーザプレーンゲートウェイは、前記ユーザ機器のダウンリンクユーザプレーンデータを転送するために使用される、ステップと、 前記ターゲットモビリティ管理ネットワーク要素により、前記ターゲット制御プレーンゲートウェイにデータ転送トンネル確立要求を送信するステップ(904)であって、前記データ転送トンネル確立要求が、前記ユーザ機器のために、前記転送ユーザプレーンゲートウェイと前記ユーザ機器に奉仕するソースユーザプレーンゲートウェイとの間のデータ転送トンネル、および前記転送ユーザプレーンゲートウェイと前記ユーザ機器に奉仕するターゲット基地局との間のデータ転送トンネルを確立するように、前記ターゲット制御プレーンゲートウェイに要求するために使用される、ステップと を備える、方法。
- 12前記ターゲット制御プレーンゲートウェイが、前記ユーザ機器が現在位置領域に移動する前に使用されたサービング制御プレーンゲートウェイとは異なり、前記方法が、 前記ターゲットモビリティ管理ネットワーク要素により、前記ソースモビリティ管理ネットワーク要素に変更通知メッセージを送信するステップであって、前記変更通知メッセージが、前記ユーザ機器のサービング制御プレーンゲートウェイが前記ターゲット制御プレーンゲートウェイに変わったことを示すために使用される、ステップ をさらに備える、請求項11に記載の方法。
- 13前記ターゲットモビリティ管理ネットワーク要素により、前記変更通知メッセージに従って前記ソースモビリティ管理ネットワーク要素から確認応答メッセージを受信するステップであって、前記確認応答メッセージが前記ソースユーザプレーンゲートウェイのルーティング情報を搬送する、ステップ をさらに備える、請求項12に記載の方法。
- 14請求項1から10の何れか1項に記載の方法を実行するよう構成された制御プレーンゲートウェイ。
- 15請求項11から13の何れか1項に記載の方法を実行するよう構成されたモビリティ管理ネットワーク要素。
Independent claims15
530 paragraphs, as filed
The present invention relates to the field of communications, and more particularly to service continuity assurance methods, control plane gateways, and mobility management network elements.
The Distributed Gateway (DGW) architecture is an extended network architecture proposed based on the existing Evolved Packet System (EPS) network architecture, following the idea of separating the network control plane function from the user plane function. is there. The DGW architecture includes a control plane gateway (C-GW) and a user plane gateway (U-GW).
The C-GW is a centralized control plane gateway and comes in two forms: (1) the control plane function of the Serving Gateway (S-GW) in the existing 3GPP EPS network and the Packet Data Network Gateway. , P-GW) single network element acquired after integration, and (2) existing S-GW control plane function (Control Plane S-GW) and existing P-GW It may have two independent network elements that implement the Control Plane P-GW separately. The C-GW is specifically configured to handle control plane signaling within the 3GPP EPS network, including signaling for features such as mobility management, session management, address management, route management, and accounting management. C-GW interacts with U-GW to control and manage user plane data processing.
U-GW is a distributed user plane gateway. Corresponding to the two forms of C-GW, U-GW also has two forms: (1) User plane function and packet data network gateway of the serving gateway (Serving Gateway, S-GW) in the existing 3GPP EPS network. A single network element acquired after the user plane functionality of (Packet Data Network Gateway, P-GW) is integrated, as well as (2) the existing S-GW user plane functionality (User Plane S-GW) and existing It may have two independent network elements that separately implement the User Plane P-GW of the P-GW. U-GW includes 3GPP including functions such as routing and forwarding, data packet checking, data packet aggregation, and quality of service enforcement. Specially configured to process user plane data in the EPS network. U-GW processes user plane data under the control and control of C-GW. Considering the feature that U-GW can be deployed in a distributed manner, U-GW is sometimes called a distributed gateway (D-GW).
In the existing EPS network architecture, service continuity is implemented by the anchor function of P-GW. That is, in the movement process of the UE in the connection mode in which the user plane service is performed, the user plane data of the UE is always exchanged between the current P-GW and the external data network. Since the P-GW does not change during the move process, the IP address of the user plane is guaranteed to remain the same, and the continuity of the user plane service is guaranteed.
The U-GW (or D-GW) within the DGW architecture provides local access for the user, further reduces the Round-Trip Time (RTT) of the user plane data, and improves the user experience. It may be deployed in a distributed manner depending on service requirements. During deployment, the U-GW may move down towards the metropolitan area network, which is closer to the user and closer to the base station controller. With the downward movement of U-GW, the service range of U-GW is much smaller than the service range of S-GW / P-GW centrally deployed in the EPS network. Therefore, the probability that the serving U-GW will change in the UE movement process increases.
In the DGW architecture, we can see that how to guarantee service continuity in the UE's mobile process is an important issue.
<p> Embodiments of the present invention provide a service continuity assurance method, a control plane gateway, and a mobility management network element to ensure service continuity in the UE's mobile process and to improve the user service experience. -Establish a data transfer tunnel between the GW and the source U-GW and a data transfer tunnel between the transfer U-GW and the UE's target base station for the UE.</p><p> According to the first aspect, a service continuity assurance method is proposed, in which the control plane gateway receives the current location information of the user equipment transmitted by the mobility management network element for the user equipment, and controls. The step of selecting at least one transfer user plane gateway for the user device according to the current location information of the user device by the plane gateway, and the source user plane gateway and transfer that serve the user device for the user device by the control plane gateway. A step of establishing a data transfer tunnel to the user plane gateway and a data transfer tunnel between the transfer user plane gateway and the target base station of the user equipment, the data transfer tunnel is used in the movement process of the user equipment. Includes steps used to transmit uplink user plane data and / or downlink user plane data for the user equipment.</p><p> With reference to the first aspect, in the first possible implementation, at least one transfer user plane gateway is the first user plane gateway and the control plane gateway is after the user equipment has moved to the current location area. The serving control plane gateway used, the control plane gateway is the same as the serving control plane gateway used before the user equipment moved to the current location area, and the mobility management network element is that the user equipment is in the current location area. A serving mobility management network element used after moving to, a data transfer tunnel between the source user plane gateway and the transfer user plane gateway that serves the user equipment for the user equipment, and the transfer by the control plane gateway. The specific implementation of the step of establishing a data transfer tunnel between the user plane gateway and the target base station of the user equipment is The step of receiving the first request sent by the mobility management network element by the control plane gateway, where the first request carries the routing information of the target base station of the user equipment, and by the control plane gateway. , The step of sending a second request to the first user plane gateway, where the second request is the data transfer tunnel between the first user plane gateway and the target base station, and the first user plane. Used to request the first user plane gateway to establish a data transfer tunnel between the gateway and the source user plane gateway, the second request is the target base station routing information and the source user plane gateway. To carry the routing information of, steps and The control plane gateway is the step of sending a third request to the source user plane gateway so that the third request establishes a data transfer tunnel between the source user plane gateway and the first user plane gateway. Used to make a request to the source user plane gateway, the third request is the step of carrying the routing information of the forwarding user plane gateway.</p><p> With reference to the first aspect, in the second possible implementation, at least one forwarding user plane gateway includes a second user plane gateway and a third user plane gateway, and the control plane gateway is a user device. The serving control plane gateway used after moving to the current location area, the control plane gateway is the same as the serving control plane gateway used before the user equipment moved to the current location area, and the mobility management network element is A serving mobility management network element used after the user equipment has moved to the current location area, the control plane gateway between the source user plane gateway and the forwarding user plane gateway serving the user equipment for the user equipment. And the specific implementation of the steps to establish a data transfer tunnel between the transfer user plane gateway and the target base station of the user equipment. The step of receiving the first request sent by the mobility management network element by the control plane gateway, where the first request carries the routing information of the target base station of the user equipment, and by the control plane gateway. , The step of sending a second request to the second user plane gateway, where the second request is the data transfer tunnel between the second user plane gateway and the target base station, and the second user plane. Used to request the second user plane gateway to establish a data transfer tunnel between the gateway and the third user plane gateway, the second request is the routing information of the target base station and the third. Carrying the routing information of the user plane gateway of The control plane gateway is the step of sending a third request to the third user plane gateway, where the third request is the data transfer tunnel between the third user plane gateway and the second user plane gateway. , And used to request the third user plane gateway to establish a data transfer tunnel between the third user plane gateway and the source user plane gateway, and the third request is the second user. The step of carrying the routing information of the plane gateway and the routing information of the source user plane gateway, and the step of sending the fourth request to the source user plane gateway by the control plane gateway, and the fourth request is the source user. Used to request the source user plane gateway to establish a data transfer tunnel between the plane gateway and the third user plane gateway, the fourth request provides the routing information for the third user plane gateway. It is a step to carry.</p><p> With reference to the first aspect, in the third possible implementation, at least one transfer user plane gateway is the first user plane gateway and the control plane gateway is after the user equipment has moved to the current location area. The serving control plane gateway used is that the control plane gateway is different from the serving control plane gateway that was used before the user equipment moved to the current location area, and the mobility management network element is that the user equipment is in the current location area. A serving mobility management network element used after the move, the method further comprises the step of receiving further source user plane gateway routing information sent by the mobility management network element by the control plane gateway, by the control plane gateway. Establish a data transfer tunnel between the source user plane gateway and the transfer user plane gateway serving the user equipment, and a data transfer tunnel between the transfer user plane gateway and the target base station of the user equipment for the user equipment. The specific implementation form of the steps to be performed is The step of receiving the first request sent by the mobility management network element by the control plane gateway, where the first request carries the routing information of the target base station of the user equipment, and by the control plane gateway. , The step of sending a second request to the first user plane gateway, where the second request is the data transfer tunnel between the first user plane gateway and the target base station, and the first user plane. Used to request the first user plane gateway to establish a data transfer tunnel between the gateway and the source user plane gateway, the second request is the target base station routing information and the source user plane gateway. It is a step to carry the routing information of.</p><p> With reference to the first aspect, in the fourth possible implementation, at least one forwarding user plane gateway includes a second user plane gateway and a third user plane gateway, and the control plane gateway is a user device. The mobility management network element is a serving control plane gateway that is used after moving to the current location area, and unlike the serving control plane gateway that was used before the user equipment moved to the current location area. It is a serving mobility management network element used after the user equipment has moved to the current location area, and the method is a step of further receiving the source user plane gateway routing information transmitted by the mobility management network element by the control plane gateway. Including more The control plane gateway provides a data transfer tunnel between the source user plane gateway and the transfer user plane gateway that serves the user equipment for the user equipment, and data between the transfer user plane gateway and the target base station of the user equipment. A specific implementation of the step of establishing a forwarding tunnel is to receive the first request sent by the mobility management network element by the control plane gateway, where the first request is the target base station of the user equipment. To carry the routing information of, steps and The control plane gateway sends a second request to the second user plane gateway, where the second request is the data transfer tunnel between the second user plane gateway and the target base station, and the second. Used to request the second user plane gateway to establish a data transfer tunnel between the second user plane gateway and the third user plane gateway, the second request is the routing of the target base station. A step that carries information and routing information for a third user plane gateway, The control plane gateway is the step of sending a third request to the third user plane gateway, where the third request is a data transfer tunnel between the third user plane gateway and the second user plane gateway. , And used to request the third user plane gateway to establish a data transfer tunnel between the third user plane gateway and the source user plane gateway, and the third request is the second user. A step that carries the plain gateway routing information and the source user plane gateway routing information.</p><p> In the fifth possible implementation, referring to any one of the first possible implementations of the first aspect or the first possible implementation of the first aspect to the fourth possible implementation of the first aspect. The method further includes the step of sending a session creation request to the target user plane gateway by the control plane gateway, where the session creation request provides a bearer context for user plane data transmission on the target user plane gateway for the user equipment. Used to create, each created bearer context contains the routing information of the target user plane gateway, which is the serving user plane gateway corresponding to the current location area of the user equipment.</p><p> With reference to the fifth possible implementation of the first aspect, in the sixth possible implementation, the method is to the target user plane gateway to the target base station via the mobility management network element by the control plane gateway. It further includes a step of transmitting routing information.</p><p> With reference to the first possible implementation of the first aspect or the third possible implementation of the first aspect, in the seventh possible implementation, the method is by means of a control plane gateway, a mobility management network. It further includes a step of transmitting the routing information of the first user plane gateway to the target base station via the element.</p><p> With reference to the first possible implementation of the first aspect or the third possible implementation of the first aspect, in the eighth possible implementation, the first user plane gateway is further user equipment. The serving user plane gateway selected by the control plane gateway for the user equipment according to the current location information of.</p><p> With reference to the second possible implementation of the first aspect or the fourth possible implementation of the first aspect, in the ninth possible implementation, the method is by means of a control plane gateway, a mobility management network. It further includes a step of transmitting the routing information of the second user plane gateway to the target base station via the element.</p><p> According to the second aspect, a service continuity assurance method is proposed, in which the target mobility management network element receives a transfer relocation request sent by the source mobility management network element serving the user equipment. There is a step in which the transfer relocation request carries the current location information of the user equipment, and a step of selecting the target control plane gateway of the user equipment according to the current location information of the user equipment by the target mobility management network element, and target mobility. The management network element is the step of transmitting the current location information of the user equipment to the target control plane gateway, so that the target control plane gateway determines the transfer user plane gateway of the user equipment according to the current location information of the user equipment. , And the step of sending a data transfer tunnel establishment request to the target control plane gateway by the target mobility management network element, where the data transfer tunnel establishment request is sent to the transfer user plane gateway and the user equipment for the user equipment. To request the target control plane gateway to establish a data transfer tunnel between the serving source user plane gateway and a data transfer tunnel between the forwarding user plane gateway and the target base station serving the user equipment. Includes steps used.</p><p> With reference to the second aspect, in the first possible implementation, the target control plane gateway is different from the serving control plane gateway that was used before the user equipment moved to the current location area, the method is target. The mobility management network element further includes the step of sending a change notification message to the source mobility management network element, which is used to indicate that the serving control plane gateway of the user equipment has changed to the target control plane gateway. To.</p><p> With reference to the first possible implementation of the second aspect, in the second possible implementation, the method is the confirmation sent by the target mobility management network element by the source mobility management network element according to the change notification message. It further includes the step of receiving the response message, which carries the routing information of the source user plane gateway of the user equipment.</p><p> According to the third aspect, a service continuity assurance method is proposed, which comprises the step of receiving the current location information of the user equipment transmitted by the mobility management network element by the control plane gateway and the control plane gateway. The step of selecting the target user plane gateway for the user device according to the current position information of the user device and the step of sending the request message to the mobility management network element by the control plane gateway, in which the request message is the first bearer context. Used to request the mobility management network element to release and send a setup request for the second bearer context, with the first bearer context on the source user plane gateway of the user equipment. Includes a step, which is the bearer context of the user equipment established in, and the second bearer context is the bearer context reestablished by the user equipment on the target user plane gateway according to the first bearer context.</p><p> With reference to the third aspect, in the first possible implementation, the request message is a bearer delete request message, the bearer delete request message carries the reactivation request instruction, and the reactivation request instruction is mobility. It is used to indicate to the user equipment to initiate a re-setup request for the bearer context after the bearer context has been deleted by using the management network element.</p><p> According to a fourth aspect, a control plane gateway is proposed, the control plane gateway is a receiving unit configured to receive the current location information of the user equipment transmitted by the mobility management network element, and the current position of the user equipment. Between a selection unit configured to select at least one transfer user plane gateway for a user device according to location information and a source user plane gateway and a transfer user plane gateway that serve the user device for the user device. A data transfer tunnel, and a tunnel establishment unit configured to establish a data transfer tunnel between a transfer user plane gateway and a target base station of the user equipment, where the data transfer tunnel is used in the process of moving the user equipment. Includes a tunnel establishment unit used to transmit uplink user plane data and / or downlink user plane data for user equipment.</p><p> In a possible design, at least one forwarding user plane gateway is the first user plane gateway, and the control plane gateway is the serving control plane gateway used after the user equipment has moved to the current location area, the control plane gateway. Is the same serving control plane gateway that was used before the user equipment moved to the current location area, and the mobility management network element is the serving mobility management network element that is used after the user equipment moves to the current location area. Yes, the receiving unit is further configured to receive the first request sent by the mobility management network element, the first request carries the routing information of the target base station of the user equipment, and the control plane gateway sends. Including more units, the tunnel establishment unit is specifically The transmit unit is configured to send the second request to the first user plane gateway, and the transmit unit is configured to send the third request to the source user plane gateway. The first request is to establish a data transfer tunnel between the first user plane gateway and the target base station, and a data transfer tunnel between the first user plane gateway and the source user plane gateway. Used to make a request to the user plane gateway, the second request carries the target base station routing information and the source user plane gateway routing information, and the third request is the source user plane gateway and the first user. It is used to request the source user plane gateway to establish a data transfer tunnel to and from the plane gateway, and the third request carries the routing information of the transfer user plane gateway.</p><p> In a possible design, at least one forwarding user plane gateway includes a second user plane gateway and a third user plane gateway, and the control plane gateway is the serving control plane used after the user equipment has moved to the current location area. A gateway, the control plane gateway is the same serving control plane gateway that was used before the user equipment moved to the current location area, and the mobility management network element is used after the user equipment has moved to the current location area. Serving mobility management network element, the receiving unit is further configured to receive the first request sent by the mobility management network element, the first request carrying the routing information of the target base station of the user equipment. However, the control plane gateway further includes the transmission unit, and the tunnel establishment unit specifically, Send a second request to the second user plane gateway by using the transmit unit, send a third request to the third user plane gateway by using the transmit unit, and use the transmit unit The second request is configured to send a fourth request to the source user plane gateway, the second request is the data transfer tunnel between the second user plane gateway and the target base station, and the second user. Used to request the second user plane gateway to establish a data transfer tunnel between the plane gateway and the third user plane gateway, the second request is the routing information of the target base station and the second. Carrying the routing information of the 3 user plane gateways, the 3rd request is the data transfer tunnel between the 3rd user plane gateway and the 2nd user plane gateway, and the 3rd user plane gateway and the source user plane. Used to request a third user plane gateway to establish a data transfer tunnel to and from the gateway, the third request is the routing information of the second user plane gateway and the routing of the source user plane gateway. The fourth request is used to carry information and request the source user plane gateway to establish a data transfer tunnel between the source user plane gateway and the third user plane gateway. The request carries the routing information for the third user plane gateway.</p><p> In a possible design, at least one forwarding user plane gateway is the first user plane gateway, and the control plane gateway is the serving control plane gateway used after the user equipment has moved to the current location area, the control plane gateway. Is a serving mobility management network element that is used after the user equipment has moved to the current location area, unlike the serving control plane gateway that was used before the user equipment moved to the current location area. , The receiving unit is further configured to receive the routing information of the source user plane gateway sent by the mobility management network element, and the receiving unit is configured to receive the first request sent by the mobility management network element. Further configured, the first request carries the routing information of the target base station of the user equipment, the control plane gateway further includes the transmission unit, and the tunnel establishment unit specifically. By using a transmit unit, it is configured to send a second request to the first user plane gateway, where the second request is a data transfer tunnel between the first user plane gateway and the target base station. , And used to request the first user plane gateway to establish a data transfer tunnel between the first user plane gateway and the source user plane gateway, and the second request is for the target base station. Carry routing information and source user plane gateway routing information.</p><p> In a possible design, at least one forwarding user plane gateway includes a second user plane gateway and a third user plane gateway, and the control plane gateway is the serving control plane used after the user equipment has moved to the current location area. A gateway, the control plane gateway is different from the serving control plane gateway that was used before the user equipment moved to the current location area, and the mobility management network element is used after the user equipment has moved to the current location area. Serving mobility management network element, the receiving unit is further configured to receive the routing information of the source user plane gateway sent by the mobility management network element, and the receiving unit is the first sent by the mobility management network element. The first request carries the routing information of the target base station of the user equipment, the control plane gateway further includes the transmission unit, and the tunnel establishment unit specifically, The transmit unit is configured to send the second request to the second user plane gateway, and the transmit unit is configured to send the third request to the third user plane gateway. The second request is to establish a data transfer tunnel between the second user plane gateway and the target base station, and a data transfer tunnel between the second user plane gateway and the third user plane gateway. , Used to make a request to the second user plane gateway, the second request carries the routing information of the target base station and the routing information of the third user plane gateway, and the third request is the third request. To the third user plane gateway to establish a data transfer tunnel between the user plane gateway and the second user plane gateway, and a data transfer tunnel between the third user plane gateway and the source user plane gateway. Used to make a request, the third request carries the routing information of the second user plane gateway and the routing information of the source user plane gateway.</p><p> In a possible design, the tunnel establishment unit is further configured to send a session creation request to the target user plane gateway, and the session creation request is a bearer for user plane data transmission on the target user plane gateway for the user equipment. Used to create contexts, each created bearer context contains routing information for the target user plane gateway, which is the serving user plane gateway that corresponds to the current location area of the user equipment.</p><p> In a possible design, the tunnel establishment unit is further configured to send the target user plane gateway routing information to the target base station via the mobility management network element.</p><p> In a possible design, the tunnel establishment unit is further configured to send the routing information of the first user plane gateway to the target base station via the mobility management network element.</p><p> In a possible design, the first user plane gateway is further a serving user plane gateway selected by the control plane gateway for the user equipment according to the current location information of the user equipment.</p><p> In a possible design, the tunnel establishment unit is further configured to send the routing information of the second user plane gateway to the target base station via the mobility management network element.</p><p> According to a fifth aspect, a mobility management network element is proposed, the mobility management network element being configured to receive a transfer relocation request sent by the source mobility management network element serving the user equipment. A receiving unit in which the transfer relocation request carries the current location information of the user equipment, a selection unit configured to select the target control plane gateway of the user equipment according to the current location information of the user equipment, and a target. A transmission unit configured to transmit the current location information of the user equipment to the control plane gateway, so that the target control plane gateway determines the transfer user plane gateway of the user equipment according to the current location information of the user equipment. , The transmit unit is further configured to send a data transfer tunnel establishment request to the target control plane gateway, and the data transfer tunnel establishment request is for the user equipment, the transfer user plane gateway and the user equipment. To require the target control plane gateway to establish a data transfer tunnel between the source user plane gateway serving and a data transfer tunnel between the transfer user plane gateway and the target base station serving the user equipment. Used for.</p><p> In a possible design, the target control plane gateway is different from the serving control plane gateway that was used before the user equipment moved to the current location area, so that the transmit unit sends a change notification message to the source mobility management network element. Further configured in, the change notification message is used to indicate that the serving control plane gateway of the user equipment has changed to the target control plane gateway.</p><p> In a possible design, the receiving unit is further configured to receive the acknowledgment message sent by the source mobility management network element according to the change notification message, which carries the routing information of the source user plane gateway of the user equipment. To do.</p><p> According to the sixth aspect, a control plane gateway is proposed, in which the control plane gateway receives the current location information of the user equipment transmitted by the mobility management network element, and the control plane gateway is the user equipment. The request message releases the first bearer context, including selecting the target user plane gateway for the user equipment according to the current location information of the control plane gateway and sending the request message to the mobility management network element. Used to request the mobility management network element to send a setup request for the second bearer context, the first bearer context is established on the source user plane gateway of the user equipment. The bearer context of the user equipment, the second bearer context is the bearer context reestablished by the user equipment on the target user plane gateway according to the first bearer context.</p><p> In a possible design, the request message is a bearer delete request message, the bearer delete request message carries the reactivation request instruction, and the reactivation request instruction is deleted by the bearer context by using the mobility management network element. After that, it is used to indicate to the user equipment to initiate a re-setup request for the bearer context.</p><p> According to the seventh aspect, a control plane gateway including a memory, a processor, a receiver, and a transmitter is proposed, the memory being configured to store a program and supply data and instructions to the processor. , The processor is configured to execute a program stored in memory, specifically: By using a receiver to receive the current location information of the user equipment transmitted by the mobility management network element and to select at least one transfer user plane gateway for the user equipment according to the current location information of the user equipment. And, for the user equipment, the data transfer tunnel between the source user plane gateway serving the user equipment and the transfer user plane gateway, and the data transfer between the transfer user plane gateway and the target base station serving the user equipment. To establish a tunnel, that is, a data transfer tunnel is used to transmit the uplink user plane data and / or the downlink user plane data of the user equipment in the process of moving the user equipment. Is configured to carry out.</p><p> In a possible design, at least one transfer user plane gateway is the first user plane gateway, and the control plane gateway is the serving control plane gateway used after the user equipment has moved to the current location area, the control plane gateway. Is the same serving control plane gateway that was used before the user equipment moved to the current location area, and the mobility management network element is the serving mobility management network element that is used after the user equipment moves to the current location area. Yes, the processor is further configured to receive the first request sent by the mobility management network element by using the receiver, which carries the routing information of the target base station of the user equipment. And by using the transmitter, for the user equipment, the data transfer tunnel between the source user plane gateway and the transfer user plane gateway, and / or the data transfer between the transfer user plane gateway and the target base station. In the process of establishing a tunnel, the processor specifically The transmitter is configured to send the second request to the first user plane gateway, and the transmitter is configured to send the third request to the source user plane gateway. The first request is to establish a data transfer tunnel between the first user plane gateway and the target base station, and a data transfer tunnel between the first user plane gateway and the source user plane gateway. Used to make a request to the user plane gateway, the second request carries the target base station routing information and the source user plane gateway routing information, and the third request is the source user plane gateway and the first user. Used to request the source user plane gateway to establish a data transfer tunnel to and from the plane gateway, the third request carries the routing information of the first user plane gateway.</p><p> In a possible design, at least one forwarding user plane gateway includes a first user plane gateway and a second user plane gateway, and the control plane gateway is the serving control plane used after the user equipment has moved to the current location area. A gateway, the control plane gateway is the same serving control plane gateway that was used before the user equipment moved to the current location area, and the mobility management network element is used after the user equipment has moved to the current location area. Serving mobility management network element, the processor is further configured to receive the first request sent by the mobility management network element by using a receiver, the first request of the target base station. By transporting routing information and using a transmitter, the data transfer tunnel between the source user plane gateway and the transfer user plane gateway, and between the transfer user plane gateway and the target base station for the user equipment. In the process of establishing a data transfer tunnel, the processor specifically Send a second request to a second user plane gateway by using a transmitter, send a third request to a third user plane gateway by using a transmitter, and use the transmitter The second request is configured to send a fourth request to the source user plane gateway, the second request is the data transfer tunnel between the second user plane gateway and the target base station, and the second user. Used to request the second user plane gateway to establish a data transfer tunnel between the plane gateway and the third user plane gateway, the second request is the routing information of the target base station and the second. Carrying the routing information of the 3 user plane gateways, the 3rd request is the data transfer tunnel between the 3rd user plane gateway and the 2nd user plane gateway, and the 3rd user plane gateway and the source user plane. Used to request a third user plane gateway to establish a data transfer tunnel to and from the gateway, the third request is the routing information of the second user plane gateway and the routing of the source user plane gateway. The fourth request is used to carry information and request the source user plane gateway to establish a data transfer tunnel between the source user plane gateway and the third user plane gateway. The request carries the routing information for the third user plane gateway.</p><p> In a possible design, at least one forwarding user plane gateway is the first user plane gateway, and the control plane gateway is the serving control plane gateway used after the user equipment has moved to the current location area, the control plane gateway. Is a serving mobility management network element that is used after the user equipment has moved to the current location area, unlike the serving control plane gateway that was used before the user equipment moved to the current location area. The processor is further configured to receive the source user plane gateway routing information transmitted by the mobility management network element by using the receiver, and the processor is further configured to receive the mobility management network by using the receiver. Further configured to receive the first request transmitted by the element, the first request carries the routing information of the target base station of the user equipment. By using a transmitter, establish a data transfer tunnel between the source user plane gateway and the transfer user plane gateway, and a data transfer tunnel between the transfer user plane gateway and the target base station for the user equipment. In the process, the processor is specifically configured to send a second request to the first user plane gateway by using a transmitter, the second request with the first user plane gateway. Used to request the first user plane gateway to establish a data transfer tunnel to and from the target base station, and a data transfer tunnel between the first user plane gateway and the source user plane gateway. The second request carries the target base station routing information and the source user plane gateway routing information.</p><p> In a possible design, at least one forwarding user plane gateway includes a first user plane gateway and a second user plane gateway, and the control plane gateway is the serving control plane used after the user equipment has moved to the current location area. A gateway, the control plane gateway is different from the serving control plane gateway that was used before the user equipment moved to the current location area, and the mobility management network element is used after the user equipment has moved to the current location area. A serving mobility management network element, the processor is further configured to receive the source user plane gateway routing information transmitted by the mobility management network element by using the receiver, and the processor uses the receiver. By doing so, it is further configured to receive the first request sent by the mobility management network element, which carries the routing information of the target base station. By using a transmitter, establish a data transfer tunnel between the source user plane gateway and the transfer user plane gateway, and a data transfer tunnel between the transfer user plane gateway and the target base station for the user equipment. In the process, the processor specifically It is configured to send a second request to a second user plane gateway by using a transmitter and a third request to a third user plane gateway by using a transmitter. The second request is to establish a data transfer tunnel between the second user plane gateway and the target base station, and a data transfer tunnel between the second user plane gateway and the third user plane gateway. , Used to make a request to the second user plane gateway, the second request carries the routing information of the target base station and the routing information of the third user plane gateway, and the third request is the third request. To the third user plane gateway to establish a data transfer tunnel between the user plane gateway and the second user plane gateway, and a data transfer tunnel between the third user plane gateway and the source user plane gateway. Used to make a request, the third request carries the routing information of the second user plane gateway and the routing information of the source user plane gateway.</p><p> In a possible design, the processor is further configured to send a session creation request to the target user plane gateway by using a transmitter, and the session creation request is on the target user plane gateway for the user equipment. Used to create bearer contexts for plane data transmission, each created bearer context contains routing information for the target user plane gateway, which is the serving user plane that corresponds to the current location area of the user equipment. It is a gateway.</p><p> In a possible design, the processor is further configured to send the target user plane gateway routing information to the target base station via the mobility management network element.</p><p> In a possible design, the processor is further configured to send the routing information of the first user plane gateway to the target base station via the mobility management network element.</p><p> In a possible design, the first user plane gateway is a serving user plane gateway selected by the control plane gateway for the user equipment according to the current location information of the user equipment.</p><p> In a possible design, the processor is further configured to send the routing information of the second user plane gateway to the target base station via the mobility management network element. According to the eighth aspect, a mobility management network element including a memory, a processor, a receiver, and a transmitter is proposed, the memory being configured to store a program and supply data and instructions to the processor. The processor is configured to execute a program stored in memory, specifically: By using a receiver is to receive a transfer relocation request sent by a source mobility management network element that serves the user equipment, where the transfer relocation request carries and receives the current location information of the user equipment. To select the target control plane gateway of the user device according to the current position information of the user device, and to transmit the current position information of the user device to the target control plane gateway by using the transmitter. As a result, the target control plane gateway determines, transmits, and transmits the transfer user plane gateway of the user equipment according to the current location information of the user equipment. By using a transmitter is to send a data transfer tunnel establishment request to the target control plane gateway, where the data transfer tunnel establishment request serves the transfer user plane gateway and the user equipment for the user equipment. Used to require the target control plane gateway to establish a data transfer tunnel to and from the user plane gateway, and a data transfer tunnel between the transfer user plane gateway and the target base station serving the user equipment. , Is configured to send and perform.</p><p> In a possible design, the target control plane gateway is different from the serving control plane gateway that was used before the user equipment moved to the current location area, and the processor is a source mobility management network element by using a transmitter. It is further configured to send a change notification message, which is used to indicate that the serving control plane gateway of the user equipment has changed to the target control plane gateway.</p><p> In a possible design, the processor is further configured to receive the acknowledgment message sent by the source mobility management network element according to the change notification message by using the receiver, which is the source user of the user equipment. Carry the routing information of the plane gateway.</p><p> According to the ninth aspect, a control plane gateway including a memory, a processor, a receiver, and a transmitter is proposed, the memory being configured to store a program and supply data and instructions to the processor. , The processor is configured to execute a program stored in memory, specifically: By using the receiver, it receives the current location information of the user equipment transmitted by the mobility management network element, selects the target user plane gateway for the user equipment according to the current location information of the user equipment, and transmits. By using the machine, a request message is sent to the mobility management network element, and the request message releases the first bearer context and sends a setup request to the second bearer context. As shown in, the first bearer context used to request the mobility management network element is the user device bearer context established on the user device source user plane gateway, and the second bearer context is the second bearer context. It is configured to perform transmission, which is a bearer context reestablished by the user equipment on the target user plane gateway according to the bearer context of 1.</p><p> In a possible design, the request message is a bearer delete request message, the bearer delete request message carries the reactivation request instruction, and the reactivation request instruction is the first bearer by using the mobility management network element. Used to indicate to the user equipment to initiate a setup request for a second bearer context after the context has been deleted.</p><p> According to the service continuity assurance method, the control plane gateway, and the mobility management network element in the embodiment of the present invention, the control plane gateway is to guarantee the service continuity in the movement process of the UE and to improve the user service experience. Select the transfer U-GW for the UE and set the data transfer tunnel between the transfer U-GW and the source U-GW and the data transfer tunnel between the transfer U-GW and the UE's target base station in the UE. Establish for.</p><p> In order to more clearly describe the technical solution in the embodiments of the present invention, the accompanying drawings required to describe the embodiments or prior art are briefly described below. Obviously, the accompanying drawings in the following description show only some embodiments of the present invention, and one of ordinary skill in the art can further derive other drawings from these attached drawings without creative effort. ..</p>
<figref num="1">It is a schematic diagram of two distributed gateway network architectures according to one embodiment of the present invention.</figref><figref num="2">It is a flowchart of the service continuity guarantee method by one Embodiment of this invention.</figref><figref num="3">It is a dialogue flowchart which guarantees service continuity by one Embodiment of this invention.</figref><figref num="4">It is another dialogue flowchart which guarantees service continuity by one Embodiment of this invention.</figref><figref num="5">It is still another dialogue flowchart which guarantees the service continuity by one Embodiment of this invention.</figref><figref num="6">It is still another dialogue flowchart which guarantees the service continuity by one Embodiment of this invention.</figref><figref num="7">It is still another dialogue flowchart which guarantees the service continuity by one Embodiment of this invention.</figref><figref num="8">It is still another dialogue flowchart which guarantees the service continuity by one Embodiment of this invention.</figref><figref num="9">It is another flowchart of the service continuity guarantee method by one Embodiment of this invention.</figref><figref num="10">It is still another flowchart of the service continuity guarantee method by one Embodiment of this invention.</figref><figref num="11">It is still another dialogue flowchart which guarantees the service continuity by one Embodiment of this invention.</figref><figref num="12">It is a schematic structure diagram of the control plane gateway by one Embodiment of this invention.</figref><figref num="13">It is another schematic structure diagram of the control plane gateway by one Embodiment of this invention.</figref><figref num="14">It is a schematic structure diagram of the mobility management network element by one Embodiment of this invention.</figref><figref num="15">It is another schematic structure diagram of the control plane gateway by one Embodiment of this invention.</figref><figref num="16">It is another schematic structure diagram of the control plane gateway by one Embodiment of this invention.</figref><figref num="17">It is another schematic structure diagram of the mobility management network element by one Embodiment of this invention.</figref><figref num="18">It is still another schematic structure diagram of the control plane gateway by one Embodiment of this invention.</figref>
In the following, the technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the embodiments described are some, but not all, of the embodiments of the present invention. Based on embodiments of the invention without creative effort, all other embodiments acquired by those skilled in the art should fall within the scope of protection of the invention.
The technical solution of the present invention is a global system for mobile communication (GSM®, Global System of Mobile communication), a code division multiple access (CDMA) system, and a wideband code division multiple access (WCDMA). Applies to various communication systems such as Wideband Code Division Multiple Access Wireless), General Packet Radio Service (GPRS), Long Term Evolution (LTE), and 5G networks. In some cases.
In the embodiment of the present invention, the user equipment UE (User Equipment) may be referred to as a mobile terminal and may be any one of the following types. User equipment can be static, mobile, portable, pocket-sized, handheld, computer-embedded, or in-vehicle. User devices are not limited to stations, mobile stations, subscriber units, personal computers, laptop computers, tablet computers. ), Netbook, Cellular Phone, Handheld, Cordless Phone, Personal Digital Assistant (PDA), Data Card, USB Plug-in Device , Mobile WiFi Hotspot Device (MiFi It may include Wearable Devices such as Devices, smartwatches / smart glasses, Modems, wireless routers, and Wireless Local Loop (WLL) stations. User devices are distributed throughout the wireless network and can communicate with one or more core networks by using the wireless access network.
The base station can be a GSM® or transceiver base station (BTS, Base Transceiver Station) in CDMA, a node B (Node B) in WCDMA®, or an advanced node B in LTE. It can be (eNB or e-Node B, evolved Node B). This is not limited in the present invention. However, for ease of explanation, the following embodiments are provided by using eNB as an example.
The Control plane gateway (C-GW) comes in two forms: (1) Control plane function of the Serving Gateway (S-GW) in the existing 3GPP EPS network and Packet Data. A single network element acquired after the network gateway (P-GW) control plane functionality is integrated, as well as (2) the existing S-GW control plane functionality (Control Plane S-GW) and the existing P- It may have two independent network elements that separately implement the GW's Control Plane P-GW. This is not limited in the present invention.
Corresponding to the two forms of C-GW, the user plane gateway (User plane gateway, U-GW ) also, two forms: (1) existing 3GPP EPS networks serving gateway in over click (Serving Gateway, S- A single network element acquired after the integration of the GW) user plane functionality and the Packet Data Network Gateway (P-GW) user plane functionality, as well as (2) existing S-GW users. It may have two independent network elements that separately implement the plane functionality (User Plane S-GW) and the existing P-GW user plane functionality (User Plane P-GW). This is not limited in the present invention. Considering the feature that U-GW can be deployed in a distributed manner, U-GW is sometimes called a distributed gateway (D-GW).
Multiple U-GWs in the same service area can form one U-GW resource pool. U-GWs in one U-GW resource pool can communicate directly with each other. One default U-GW may be configured in each U-GW resource pool to implement communication with U-GWs in different U-GW resource pools.
FIG. 1 is a schematic diagram of two DGW network architectures according to an embodiment of the present invention. DGW architecture 1 is above the dashed line and DGW architecture 2 is below the dashed line.
In DGW Architecture 1, all control plane functions of S-GW and P-GW in the existing EPS network architecture are integrated into C-GW, and all S-GW and P-GW in the existing EPS network architecture. User plane functions will be integrated into U-GW. To implement communication between C-GW and U-GW, two network elements: a new interface, such as the S18 interface, will be introduced between C-GW and U-GW. This network architecture allows other network elements and interfaces to reuse existing EPS network architectures. The newly added S18 interface can reuse an interface protocol between S-GW and P-GW, such as GTP, or another interface protocol, or a newly defined protocol. This is not limited to this embodiment of the present invention.
In DGW Architecture 2, S-GW and P-GW in the existing EPS network architecture have independent control plane functional network elements and independent user plane functional network elements (S-GW-C and S-GW-U, as well as S-GW-C and S-GW-U. , P-GW-C and P-GW-U) separately. S-GW-C and P-GW-C may be collectively referred to as C-GW, and S-GW-U and P-GW-U may be collectively referred to as U-GW. The existing interface between S-GW and P-GW is also divided into control plane interface and user plane interface such as S5-C interface and S5-U interface in DGW architecture 2. To implement communication between S-GW-C and S-GW-U, there are two network elements: a new interface between S-GW-C and S-GW-U, such as the S18 interface. be introduced. To implement communication between P-GW-C and P-GW-U, there are two network elements: a new interface between P-GW-C and P-GW-U, such as the S19 interface. be introduced. This network architecture allows other network elements and interfaces to reuse existing EPS network architectures. The newly added S18 and S19 interfaces can reuse an interface protocol between S-GW and P-GW, such as GTP, or another interface protocol, or a newly defined protocol. This is not limited to this embodiment of the present invention.
The methods and devices in the embodiments of the present invention may be applied to the communication system shown in DGW architecture 1 or DGW architecture 2 of FIG. For ease of explanation, the communication system shown in DGW Architecture 1 is used as an example in the embodiments of the present invention. In the case of the communication system shown in DGW Architecture 2, in this embodiment of the invention, C-GW is equivalent to the integrated network elements of S-GW-C and P-GW-C in DGW Architecture 2. U-GW is equivalent to the integrated network elements of S-GW-U and P-GW-U in DGW Architecture 2.
FIG. 2 is a flowchart of a service continuity guarantee method according to an embodiment of the present invention. The method in Figure 2 is performed by the control plane gateway. The method includes the following steps.
201. C-GW receives the current location information of the UE sent by the mobility management network element.
This embodiment of the present invention is applicable to any one of the following application scenarios: (1) During user plane data transmission, the UE in connection mode moves and the moved position area is the source. After detecting that the UE has moved out of the service range of the source base station beyond the service range of the base station, the source base station decides to start the user plane data service switching procedure in connection mode. The source base station is the serving base station that was used before the UE moved to the current position area.
(2) When uplink user plane data needs to be transmitted, the UE in idle mode moves from the currently registered location area, such as the currently registered tracking area (TA), and the UE Initiates a location update procedure, such as a Tracking Area Update (TAU) procedure.
(3) When uplink user plane data needs to be transmitted, the UE in idle mode moves from the service area of the current serving base station, but is currently registered in the tracking area (TA), etc. The UE initiates the Service Request procedure without moving from the currently registered location area of.
In application scenario (1), after receiving the user plane data switching request sent by the source base station, the mobility management network element can send a service switching notification to the serving C-GW of the UE. It should be understood that the mobility management network element can be an MME or another network element with MME mobility management capabilities. For certain applications, the mobility management network element uses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message. By doing so, the service switch notification can be sent, or the mobility management network element can send the service switch notification by using the newly created message. The specific message used to send the service switch notification is not limited in the present invention.
In application scenario (2), after receiving the location update request sent by the UE, or after successfully creating a wireless access bearer context for the UE, the mobility management network element sends a request message to the UE's serving C-GW. Can be sent. It should be understood that the mobility management network element can be an MME or another network element with MME mobility management capabilities. For certain applications, the mobility management network element uses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message. The request message can be sent by doing so, or the mobility management network element can send the request message by using the newly created message. The specific message used to send the request message is not limited in the present invention.
In application scenario (3), after receiving a service request sent by the UE, or after successfully creating a wireless access bearer context for the UE, the mobility management network element sends a request message to the UE's serving C-GW. Can be sent. It should be understood that the mobility management network element can be an MME or another network element with MME mobility management capabilities. For certain applications, the mobility management network element uses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message. The request message can be sent by doing so, or the mobility management network element can send the request message by using the newly created message. The specific message used to send the request message is not limited in the present invention.
The current position information of the UE includes tracking area identification information (TAI) corresponding to the current position area of the UE, serving base station information corresponding to the current position area of the UE, and the like. The corresponding TAI used when the UE moves to the current position region is the UE's target TAI. The corresponding serving base station information used after the UE has moved to the current location area is the UE's target base station information. The target base station information can be a target base station identification information (Identity, ID), a target cell identifier (Cell Identity, CI), or the like. It should be understood that the current location region of the UE is also referred to as the target location region of the UE, i.e., the location region of the UE after the UE has moved out of the service range of the source serving base station. Similarly, the current position information of the UE is also called the target position information of the UE.
202. C-GW selects at least one forwarding U-GW for UE according to the current location information of UE.
In this embodiment of the invention, the current location area of the UE exceeds the service range of the current serving U-GW of the UE, and the C-GW selects the appropriate transfer U-GW for the UE according to the current position area of the UE. There is a need to.
203. C-GW serves the UE for the data transfer tunnel between the source U-GW serving the UE and the forwarding U-GW, and between the forwarding U-GW and the target base station serving the UE. Establish a data transfer tunnel.
The data transfer tunnel is used in the UE's move process to transmit the UE's uplink user plane data and / or downlink user plane data.
The UE movement process consists of the procedures performed in the above three application scenarios, specifically, the service switching procedure in the application scenario (1), the position update procedure in the application scenario (2), and the service in the application scenario (3). Please understand that it includes the request procedure.
It should be understood that the UE's target base station is the base station that provides access services to the UE after it has moved to the current location area.
The data transfer tunnel creates a user plane bearer context between the source U-GW serving the UE and the transfer U-GW, and a user plane bearer context between the transfer U-GW and the UE's target base station. Please understand that it is implemented by. The user plane bearer context contains the routing information needed to transfer the user plane data. Specifically, the user plane bearer context created on the source U-GW contains the routing information of the forwarding U-GW and the routing information of the source base station serving the UE, and is created on the forwarding U-GW. The user plane bearer context contains the routing information of the source U-GW and the routing information of the target base station, and the user plane bearer context created on the target base station contains the routing information of the forwarding U-GW. In addition, the routing information includes the address (usually the Internet Protocol (IP) address) and the tunnel end point information (usually the GPRS Tunneling). When Protocol (GTP) is used, the tunnel endpoint information may include the GTP tunnel endpoint identifier (TEID).
It should be understood that the forwarding U-GW is at least one forwarding U-GW mentioned in step 202. The data transfer tunnel established by the C-GW for the UE between the source U-GW serving the UE and the transfer U-GW and between the transfer U-GW and the UE's target base station is the source. Established by C-GW between the source U-GW, at least one transfer U-GW, and the target base station to establish a data transfer tunnel between the two network elements from the C-GW to the target base station. It is a communication path to be performed.
For example, when at least one forwarding U-GW contains only one U-GW: U-GW1, the established data forwarding tunnel route is source U-GW U-GW1 target base station. At least one transfer U-GW contains two U-GWs: U-GW1 and U-GW2, U-GW1 can communicate with the source U-GW, and U-GW2 communicates with the target base station. When is possible, the data transfer tunnel route established is source U-GW U-GW1 U-GW2 target base station. Established when at least one transfer U-GW contains three or more U-GWs, including U-GW1 capable of communicating with the source U-GW and U-GW2 capable of communicating with the target base station. The data transfer tunnel route to be performed is source U-GW U-GW1 ... U-GW2 target base station. The data transfer tunnel indicated by U-GW1 ... U-GW2 is a data transfer tunnel between at least one transfer U-GW.
In this embodiment of the invention, the C-GW is a suitable transfer U-GW for the UE according to the current location information after the move to ensure service continuity in the UE move process and improve the user service experience. And establish a data transfer tunnel between the transfer U-GW and the source U-GW, and a data transfer tunnel between the transfer U-GW and the target base station of the UE.
In some cases, in one embodiment, at least one transfer U-GW contains only one U-GW: the first U-GW, and the C-GW is used after the UE has moved to the current position region. Serving C-GW, C-GW is the same serving C-GW used before the UE moved to the current location area, and the mobility management network element is used after the UE moves to the current position area. Serving mobility management network element. In this case, step 203 is specifically implemented as follows: The step of receiving the first request sent by the mobility management network element by the C-GW, where the first request carries the routing information of the UE's target base station, the step, by the C-GW. A step of sending a second request to one U-GW, where the second request is with the data transfer tunnel between the first U-GW and the target base station, and the first U-GW. Used to request the first U-GW to establish a data transfer tunnel to and from the source U-GW, the second request is the target base station's routing information and the source U-GW's routing. The step of transporting information, as well as the step of sending a third request to the source U-GW by the C-GW, where the third request is between the source U-GW and the first U-GW. A step in which a third request carries the routing information of the first U-GW, which is used to request the source U-GW to establish a data transfer tunnel for the first U-GW.
In this embodiment, it is understood that the C-GW is the same as the serving C-GW used before the UE moved to the current position region, i.e., the serving C-GW does not change in the UE moving process. I want to. This embodiment is applicable to scenarios where the serving mobility management network element changes in the UE's mobility process, or where the serving mobility management network element does not change in the UE's mobility process, i.e. the mobility management network element is the UE's. It should be understood that it may be the same as or different from the serving mobility management network element used before moving to the current location area.
Naturally, the C-GW should further receive the second response sent by the first U-GW according to the second request and the third response sent by the source U-GW according to the third request. I want you to understand. The second response is that the first U-GW transfers data between the first U-GW and the target base station, and between the first U-GW and the source U-GW. It is used to confirm that the tunnel has been allowed to be established. In some cases, the second response can carry the routing information of the first U-GW, such as IP address and TEID information, and the third response is that the source U-GW is with the source U-GW. It is used to confirm that the data transfer tunnel to and from the first U-GW has been allowed to be established. After receiving the second and third responses, the C-GW can send the first response of the first request to the mobility management network element.
The first, second, or third request in this embodiment uses an existing message, such as a Create Indirect Data Forwarding Tunnel Request, or a newly defined message. Please note that it may be sent by. This is not limited in the present invention. In addition, the first, second, or third response in this embodiment may be an existing message, such as a Create Indirect Data Forwarding Tunnel Response, or a newly defined message. May be sent by use. This is not limited in the present invention.
In addition, it should be understood that the physical implementation of a tunnel is a bearer context, which contains routing information for the peer termination of the tunnel. The control plane gateway must send requests to the two user plane gateways separately and create bearer contexts separately, and the bearer context contains peer-terminated routing information in this way for the two user plane gateways. A tunnel is established between them.
In some cases, in another embodiment, at least one transfer U-GW includes a second U-GW and a third U-GW, and the C-GW is used after the UE has moved to the current location region. Serving C-GW, which is the same serving C-GW used before the UE moved to the current location region, and the mobility management network element after the UE moved to the current location region. The serving mobility management network element used, which is the same as or different from the serving mobility management network element used before the UE moved to the current location area. In this case, step 203 is specifically implemented as follows: The step of receiving the first request sent by the mobility management network element by the C-GW, where the first request carries the routing information of the UE's target base station, the step, by the C-GW. The step of sending a second request to the second U-GW, where the second request is with the data transfer tunnel between the second U-GW and the target base station, and the second U-GW. Used to request the second U-GW to establish a data transfer tunnel to and from the third U-GW, the second request is the routing information of the target base station and the third U. -The step of carrying the routing information of the GW, the step of sending the third request to the third U-GW by the C-GW, and the third request is the third U-GW and the second. Used to request a third U-GW to establish a data transfer tunnel to and from the U-GW, and a data transfer tunnel between the third U-GW and the source U-GW. , The third request carries the routing information of the second U-GW and the routing information of the source U-GW, the step, and A step in which the C-GW sends a fourth request to the source U-GW so that the fourth request establishes a data transfer tunnel between the source U-GW and the third U-GW. A step in which the fourth request carries the routing information of the third U-GW, which is used to request the source U-GW.
In this embodiment, it is understood that the C-GW is the same as the serving C-GW used before the UE moved to the current position region, i.e., the serving C-GW does not change in the UE moving process. I want to. This embodiment is applicable to scenarios where the serving mobility management network element changes in the UE's mobility process, or where the serving mobility management network element does not change in the UE's mobility process, i.e. the mobility management network element is the UE's. It should be understood that it may be the same as or different from the serving mobility management network element used before moving to the current location area.
Similarly, the C-GW has a second response sent by the second U-GW according to the second request, a third response sent by the third U-GW according to the third request, and a second. Further receive the fourth response sent by the source U-GW in accordance with request 4. The second response is that the second U-GW is a data transfer tunnel between the second U-GW and the target base station, and between the second U-GW and the third U-GW. Used to acknowledge that you have allowed the establishment of a data transfer tunnel. In some cases, the second response can carry the routing information of the second U-GW, such as IP address and TEID information. The third response is that the third U-GW is a data transfer tunnel between the third U-GW and the second U-GW, and between the third U-GW and the source U-GW. Used to acknowledge that you have allowed the establishment of a data transfer tunnel in. In some cases, the third response can carry the routing information of the third U-GW, such as IP address and TEID information. The fourth response is used to confirm that the source U-GW has allowed the establishment of a data transfer tunnel between the source U-GW and the third U-GW. After receiving the second response, the third response, and the fourth response, the C-GW can send the first response of the first request to the mobility management network element.
The first, second, third, or fourth request in this embodiment is an existing message, such as a Create Indirect Data Forwarding Tunnel Request, or is newly defined. Please note that it may be sent by using a tunnel. This is not limited in the present invention. In addition, the first, second, third, or fourth response in this embodiment is an existing message, such as a Create Indirect Data Forwarding Tunnel Response, or a new one. May be sent by using a defined message. This is not limited in the present invention.
At least one forwarding U-GW determined by C-GW can be three or more forwarding U-GWs. The C-GW sends a data transfer tunnel establishment request to each transfer U-GW to establish a data transfer tunnel between the source transfer U-GW, at least one transfer U-GW, and the target base station. For example, at least one forwarding U-GW includes U-GW1, U-GW2, and U-GW3. U-GW1 can communicate with the source U-GW, U-GW3 can communicate with the target U-GW, and the established transfer tunnel route is source U-GW U-GW1 U-GW2. U-GW3 Target U-GW.
In some cases, in yet another embodiment, the C-GW further receives the routing information of the UE source U-GW transmitted by the mobility management network element. At least one transfer U-GW contains only one U-GW: the first U-GW, the C-GW is the serving C-GW used after the UE has moved to the current position region, C- Unlike the serving C-GW that was used before the UE moved to the current location area, the mobility management network element is the serving mobility management network element that is used after the UE moves to the current location area. The mobility management network element is the same as or different from the serving mobility management network element that was used before the UE moved to the current location area. In this case, step 203 is specifically implemented as follows: The step of receiving the first request sent by the mobility management network element by the C-GW, where the first request carries the routing information of the UE's target base station, as well as by the C-GW. The step of sending a second request to the first U-GW, where the second request is the data transfer tunnel between the first U-GW and the target base station, and the first U-GW. Used to request the first U-GW to establish a data transfer tunnel between and the source U-GW, the second request is the routing information of the target base station and the source U-GW. A step that carries routing information.
It should be understood that in this embodiment the C-GW is different from the serving C-GW used before the UE moved to the current position region, i.e., the serving C-GW changes in the UE moving process. This embodiment is applicable to scenarios where the serving mobility management network element changes in the UE's mobility process, or where the serving mobility management network element does not change in the UE's mobility process, i.e. the mobility management network element is the UE's. It should be understood that it may be the same as or different from the serving mobility management network element used before moving to the current location area.
Similarly, the C-GW further receives the second response sent by the first U-GW in accordance with the second request. The second response is that the first U-GW transfers data between the first U-GW and the target base station, and between the first U-GW and the source U-GW. It is used to confirm that the tunnel has been allowed to be established. In some cases, the second response can carry the routing information of the first U-GW, such as IP address and TEID information. After receiving the second response, the C-GW can send the first response of the first request to the mobility management network element.
Of course, in this embodiment of the invention, the serving C-GW of the UE in this embodiment changes in the process of moving the UE, so step 203 in this embodiment specifically refers to the target C-GW, i.e. the UE. It should be understood that this is done by the serving C-GW used after moving to the current location area. In addition, the target C-GW sends a data transfer tunnel establishment request to the source U-GW and the source U-GW through the mobility management network element to send the routing information of the first U-GW. It should be further shown to C-GW. The source C-GW is the serving C-GW used before the UE moved to the current position area, and the source U-GW is the serving U-GW used before the UE moved to the current position area. is there.
When the first or second request in this embodiment is sent by using an existing message, such as a Create Indirect Data Forwarding Tunnel Request, or a newly defined message. Please note that there is. This is not limited in the present invention. In addition, the first or second response in this embodiment is sent by using an existing message, such as a Create Indirect Data Forwarding Tunnel Response, or a newly defined message. May occur. This is not limited in the present invention.
In some cases, in yet another embodiment, the C-GW further receives the routing information of the UE source U-GW transmitted by the mobility management network element. At least one transfer U-GW includes a second U-GW and a third U-GW, where the C-GW is the serving C-GW used after the UE has moved to the current position region, C- Unlike the serving C-GW that was used before the UE moved to the current location area, the mobility management network element is the serving mobility management network element that is used after the UE moves to the current location area. The mobility management network element is the same as or different from the serving mobility management network element that was used before the UE moved to the current location area. In this case, step 203 is specifically implemented as follows: The step of receiving the first request sent by the mobility management network element by the C-GW, where the first request carries the routing information of the UE's target base station, the step, by the C-GW. The step of sending a second request to the second U-GW, where the second request is with the data transfer tunnel between the second U-GW and the target base station, and the second U-GW. Used to request the second U-GW to establish a data transfer tunnel to and from the third U-GW, the second request is the routing information of the target base station and the third U. -The step of carrying the routing information of the GW, and the step of sending the third request to the third U-GW by the C-GW, where the third request is the third U-GW and the third. Used to request a third U-GW to establish a data transfer tunnel between the second U-GW and a data transfer tunnel between the third U-GW and the source U-GW. Then, the third request carries the routing information of the second U-GW and the routing information of the source U-GW, a step.
It should be understood that in this embodiment the C-GW is different from the serving C-GW used before the UE moved to the current position region, i.e., the serving C-GW changes in the UE moving process. This embodiment is applicable to scenarios where the serving mobility management network element changes in the UE's mobility process, or where the serving mobility management network element does not change in the UE's mobility process, i.e. the mobility management network element is the UE's. It should be understood that it may be the same as or different from the serving mobility management network element used before moving to the current location area.
Similarly, the C-GW further adds a second response sent by the second U-GW according to the second request and a third response sent by the third U-GW according to the third request. Receive. The second response is that the second U-GW is a data transfer tunnel between the second U-GW and the target base station, and between the second U-GW and the third U-GW. Used to acknowledge that you have allowed the establishment of a data transfer tunnel. In some cases, the second response can carry the routing information of the second U-GW, such as IP address and TEID information. The third response is that the third U-GW is a data transfer tunnel between the third U-GW and the second U-GW, and between the third U-GW and the source U-GW. Used to acknowledge that you have allowed the establishment of a data transfer tunnel. In some cases, the third response can carry the routing information of the third U-GW, such as IP address and TEID information. After receiving the second and third responses, the C-GW can send the first response of the first request to the mobility management network element.
Of course, in this embodiment of the invention, the serving C-GW of the UE in this embodiment changes in the process of moving the UE, so step 203 in this embodiment specifically refers to the target C-GW, i.e. the UE. It should be understood that this is done by the serving C-GW used after moving to the current location area. In addition, the target C-GW sends a data transfer tunnel establishment request to the source U-GW and the source U-GW through the mobility management network element to send the routing information of the third U-GW. It should be further shown to C-GW. The source C-GW is the serving C-GW used before the UE moved to the current position area, and the source U-GW is the serving U-GW used before the UE moved to the current position area. is there.
The first, second, or third request in this embodiment uses an existing message, such as a Create Indirect Data Forwarding Tunnel Request, or a newly defined message. Please note that it may be sent by. This is not limited in the present invention. In addition, the first, second, or third response in this embodiment may be an existing message, such as a Create Indirect Data Forwarding Tunnel Response, or a newly defined message. May be sent by use. This is not limited in the present invention.
In some cases, in the four specific embodiments described above in FIG. 2, when at least one forwarding U-GW is the first U-GW, the method is by C-GW via the mobility management network element. Further includes the step of transmitting the routing information of the first U-GW to the target base station.
Alternatively, in the four specific embodiments described above in FIG. 2, when at least one transfer U-GW is a second U-GW and a third U-GW, the method is by C-GW. It further includes the step of transmitting the routing information of the second U-GW to the target base station via the mobility management network element.
In some cases, in the four specific embodiments described above in FIG. 2, the method may further include the step of sending a session creation request to the target U-GW by the C-GW. Used to create bearer contexts for user plane data transmission on the target U-GW for UE, each created bearer context is the target U-GW's routing (such as IP address and TEID information). The target U-GW, which contains information, is the serving U-GW that corresponds to the current location region of the UE. It should be understood that the target U-GW is generally a serving U-GW that provides the optimal data transmission path for the UE in the current location region. In addition, the C-GW transmits the routing information of the target U-GW to the target base station via the mobility management network element.
In some cases, in the four specific embodiments described above in FIG. 2, when at least one transfer U-GW is the first U-GW, the first U-GW further provides the current location information of the UE. It can be a serving U-GW selected by C-GW for UE according to. That is, the first U-GW is the target U-GW. In this case, the target D-GW can communicate directly with the source D-GW, that is, the target U-GW also acts as a forwarding U-GW. It should be understood that the forwarding U-GW selected by the C-GW is different from the target U-GW when the target U-GW cannot communicate directly with the source D-GW.
Hereinafter, the method in the embodiment of the present invention will be further described with reference to the specific embodiment. For ease of explanation, MME is used as the mobility management network element in the following embodiments. Of course, for certain applications, the mobility management network element may be, in turn, another device with the mobility management network element function. This is not limited to this embodiment of the present invention.
FIG. 3 is a dialogue flowchart for guaranteeing service continuity according to an embodiment of the present invention. In FIG. 3, the source base station is the serving base station used before the UE moved to the current position region. The target base station is a serving base station that is used after the UE has moved to the current position area. The UE serving MME and serving C-GW remain unchanged before and after the movement of the UE. The source U-GW is the serving U-GW used before the UE moved to the current position area. The target U-GW is the U-GW used after the UE has moved to the current position area. The transfer U-GW is a U-GW that is used after the UE has moved to the current location area and is used for data service switching. Prior to service switching, the uplink / downlink user plane data transmission path is UE source base station source U-GW, that is, the transmission path indicated by the broken lines L1a and L2a in FIG.
The specific service switching procedure in this embodiment of the present invention is as follows.
S301. The source base station starts the user plane data switching procedure for the UE in connection mode.
When the UE source base station detects that the UE has moved out of the service range of the source base station and the UE is performing the user plane data service, the source base station initiates the connection mode user plane data service switching procedure. Can be decided to do.
S302. The source base station sends a service switch request message to the MME.
The service switching request message transmitted to the MME by the source base station is referred to as service switching request message 1 to distinguish it from the service switching request message of another step in this embodiment of the present invention.
The source base station sends a service switch request message 1 to the current serving MME (ie, the MME in FIG. 3) and adds the UE's current location information to the message. The current position information of the UE includes tracking area identification information (TAI) corresponding to the current position area of the UE, serving base station information corresponding to the current position area of the UE, and the like. The corresponding TAI used when the UE moves to the current position region is the UE's target TAI. The corresponding serving base station information used after the UE has moved to the current location area is the UE's target base station information. The target base station information can be a target base station identification information (Identity, ID), a target cell identifier (Cell Identity, CI), or the like. The current location region of the UE is also referred to as the target location region of the UE, that is, the location region of the UE after the UE has moved out of the service range of the source serving base station. Similarly, the current position information of the UE is also called the target position information of the UE.
S303. MME sends a service switching notification message to C-GW.
After receiving the service switch request message 1, the UE's serving MME learns that the UE has now moved out of the service range of the base station (source base station), and then sends a service switch notification message to the current serving C-GW. Send. The service switching notification message carries the current position information of the UE. The service switch notification message is used to notify the C-GW that the UE needs to be handed over to a new target location area. The MME reuses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message, and puts the UE's current message in the message. Location information can be added. Alternatively, the MME can define a new message and send a service switch notification message. This is not limited to this embodiment of the present invention.
S304.C-GW determines the target U-GW and the forwarding U-GW.
After receiving the service switch notification message sent by MME, C-GW needs to reallocate the UE's current serving U-GW (source U-GW) according to the UE's current location information. That is, it can be determined whether the UE has moved out of the service range of the source U-GW. Since C-GW stores the service area information of each U-GW within the service range of C-GW in real time, C-GW follows the current position information of UE (such as target TAI or target base station ID). Note that it is possible to determine if the UE has moved out of the service range of the source U-GW.
If the UE has not moved out of the service range of the source U-GW, the data service switching of the UE may be performed at the source U-GW. For a specific implementation, refer to the prior art method for switching data services by U-GW or P-GW. Details are not described in this embodiment of the invention.
If the C-GW determines that the UE serving U-GW needs to be reassigned, the C-GW selects the appropriate target U-GW according to the UE's current location information and the target U-GW. Ensures that can provide the optimal data transmission path within the current location region for the UE and reduces the transmission RTT of user plane data as much as possible.
In addition, the C-GW needs to check if the target U-GW can communicate directly with the source U-GW. If the target U-GW can communicate directly with the source U-GW, then the target U-GW is the forwarding U-GW, that is, the transmissions made to the forwarding U-GW in all subsequent steps are This is a transmission performed to the target U-GW. If the target U-GW cannot communicate directly with the source U-GW, the U-GW capable of directly communicating with the source U-GW is selected as the forwarding U-GW according to the target location information of the UE. The method for determining the target U-GW and the transfer U-GW in FIGS. 4 to 6 is the same as this method.
Note that there may be more than one forwarding U-GW to ensure service continuity in special scenarios. Normally, when a UE moves to an adjacent U-GW pool, the C-GW communicates with the target U-GW (sometimes called the target transfer U-GW) as a transfer U-GW in the adjacent U-GW pool. Select the default U-GW for. If the default U-GW also cannot communicate directly with the source U-GW, then the C-GW also communicates with the source U-GW (sometimes called the source transfer U-GW) as a transfer U-GW. You can choose the default U-GW in the U-GW pool where the source U-GW is located, and the two forwarding U-GWs are used to ensure service continuity in the UE move process.
S305.C-GW returns a switch notification confirmation response message to MME.
The C-GW returns a switching notification confirmation response message to the MME, and adds the address of the forwarding U-GW selected by the C-GW and the tunnel end point information to the message.
For example, the forwarding U-GW address can be the forwarding U-GW's Internet Protocol (IP) address. The tunnel end information of the forwarding U-GW may change depending on the protocol between MME and C-GW. For example, when GTP is used between MME and C-GW, the tunnel endpoint information of the forwarding U-GW can be the GTP Tunnel Endpoint Identifier (TEID).
In addition, if multiple forwarding U-GWs, such as the source forwarding U-GW and the target forwarding U-GW, are determined in step S304, the C-GW sends the switching notification acknowledgment message to the UE's target location area. Add the address and tunnel end point information of the target forwarding U-GW located in. Existing messages such as a Create Session Response message, a Modify Bearer Response message, or a Modify Access Bearers Response message when a switch notification acknowledgment message is replied to the MME. Note that may be reused or new messages may be defined. This is not limited to this embodiment of the present invention.
S306. MME sends a service switch request message to the target base station.
The service switching request message transmitted by the MME to the target base station is referred to as service switching request message 2 to distinguish it from the service switching request message of another step in this embodiment of the present invention.
The MME sends a service switch request message 2 to the target base station, forwards the forwarding U-GW address and tunnel end point information sent by the C-GW to the target base station, and as a result, the uplink data. The transmission path is handed over to the transfer U-GW. The forwarding U-GW address and tunnel end point information may be sent by using service switch request message 2 or may be sent alone.
S307. The target base station returns a switch request confirmation response message to the MME.
In order to distinguish it from the switching request confirmation response message of another step in this embodiment of the present invention, and to match the numeric identifier of the service switching request message corresponding to the switching request confirmation response message with the corresponding numeric identifier. The switch request acknowledgment message sent to the MME by the target base station is called the switch request acknowledgment message 2.
After receiving the service switch request message 2 sent by the MME, the target base station replies the switch request acknowledgment message 2 to the MME and sends the MME the address (such as the IP address) and (GTP TEID, etc.) of the target base station. ) Tunnel end point information can be sent. Similarly, the target base station address and tunnel end point information may be transmitted by using the switch request acknowledgment message 2 or may be transmitted alone.
S308. MME sends a data transfer tunnel establishment request to C-GW.
The data transfer tunnel establishment request transmitted by the MME to the C-GW is referred to as the data transfer tunnel establishment request 1 to distinguish it from the data transfer tunnel establishment request of another step in this embodiment of the present invention.
The MME sends a data transfer tunnel establishment request 1 to the C-GW, sends the target base station address and tunnel end point information to the C-GW, and as a result, the downlink data transmission path is handed over to the target base station. Will be done.
A data forwarding tunnel establishment request is sent by reusing an existing message, such as a Create Indirect Data Forwarding Tunnel Request or Modify Bearer Request message, or a newly defined message. Please note that it may be done. This is not limited in the present invention. The description is applicable to all embodiments of the present invention.
S309. C-GW sends a data transfer tunnel establishment request to transfer U-GW.
To distinguish from the data transfer tunnel establishment request of another step in this embodiment of the present invention, and to match the numerical identifier of the data transfer tunnel establishment request corresponding to the data transfer tunnel establishment request with the corresponding numeric identifier. , The data transfer tunnel establishment request sent by the C-GW to the transfer U-GW is called the data transfer tunnel establishment request 2.
The C-GW sends a data transfer tunnel establishment request 2 to the transfer U-GW, and transmits the target base station address and tunnel end point information, and the source U-GW address and tunnel end point information to the transfer U-GW. ..
In addition, in step S304, a plurality of transfer U-GWs, such as a source transfer U-GW (ie, the third U-GW described above) and a target transfer U-GW (ie, the second U described above). If -GW) is required, the C-GW should send a data transfer tunnel establishment request to each transfer U-GW, which carries the address of the peer network element and the tunnel end point information. For example, a data transfer tunnel establishment request sent to a source transfer U-GW carries the address and tunnel end point information of the source U-GW and target transfer U-GW, and is sent to the target transfer U-GW. The establishment request carries the source transfer U-GW address and tunnel end point information, as well as the target base station address and tunnel end point information.
S310. Transfer U-GW returns a data transfer tunnel establishment response to C-GW.
To distinguish from the data transfer tunnel establishment response of another step in this embodiment of the present invention, and to match the numerical identifier of the data transfer tunnel establishment request corresponding to the data transfer tunnel establishment response with the corresponding numeric identifier. The data transfer tunnel establishment response sent by the transfer U-GW to the C-GW is called the data transfer tunnel establishment response 2.
The forwarding U-GW returns a data forwarding tunnel establishment response 2 to the C-GW, responds to the data forwarding tunnel establishment request 2 sent by the C-GW, and is between the target base station and the forwarding U-GW. Determines that the establishment of a data transfer tunnel and the establishment of a data transfer tunnel between the source U-GW and the transfer U-GW are allowed. In some cases, the data transfer tunnel establishment response 2 can carry the address of the transfer U-GW and the tunnel end point information.
If multiple transfer U-GWs are required in step S304, the C-GW should send a data transfer tunnel establishment request to each transfer U-GW, and each transfer U-GW responds accordingly. , A data transfer tunnel establishment response should be returned to indicate that the data transfer tunnel establishment is allowed.
It should be understood that all responses to the data transfer tunnel establishment request in the present invention indicate that the establishment of a data transfer tunnel is permitted. The method in this embodiment of the invention is no longer practiced if there is a response indicating that the establishment of a data transfer tunnel is not permitted. This is applicable to:
A data transfer tunnel establishment response is sent by reusing an existing message, such as a Create Indirect Data Forwarding Tunnel Response or Modify Bearer Response message, or a newly defined message. Please note that it may be done. This is not limited in the present invention. The description is applicable to all embodiments of the present invention.
S311.C-GW sends a data transfer tunnel establishment request to the source U-GW.
The data transfer tunnel establishment request transmitted by the C-GW to the source U-GW is referred to as the data transfer tunnel establishment request 3 to distinguish it from the data transfer tunnel establishment request of another step in this embodiment of the present invention. ..
The C-GW sends a data transfer tunnel establishment request 3 to the source U-GW, and sends the address of the transfer U-GW and the tunnel end point information to the source U-GW.
If a plurality of forwarding U-GWs are determined in step S304, the C-GW transmits the address of the source forwarding U-GW located in the current position region of the UE and the tunnel end point information to the source U-GW.
S312. Source U-GW returns a data transfer tunnel establishment response to C-GW.
To distinguish from the data transfer tunnel establishment response of another step in this embodiment of the present invention, and to match the numerical identifier of the data transfer tunnel establishment request corresponding to the data transfer tunnel establishment response with the corresponding numeric identifier. The data transfer tunnel establishment response sent by the source U-GW to the C-GW is called the data transfer tunnel establishment response 3.
The source U-GW returns a data transfer tunnel establishment response 3 to the C-GW, responds to the data transfer tunnel establishment request 3 sent by the C-GW, and is between the transfer U-GW and the source U-GW. Determines that the establishment of a data transfer tunnel is permitted.
S313. Establish a data transfer tunnel between the source U-GW and the transfer U-GW.
After the peer U-GW address and tunnel end point information are obtained, a data transfer tunnel between the source U-GW and the transfer U-GW is established.
Of course, in step S304, if multiple forwarding U-GWs, eg, a source forwarding U-GW and a target forwarding U-GW, are determined, a data forwarding tunnel between the source U-GW and the source forwarding U-GW, And a data transfer tunnel between the source transfer U-GW and the target transfer U-GW is established correspondingly.
S314.C-GW returns a data transfer tunnel establishment response to MME.
To distinguish from the data transfer tunnel establishment response of another step in this embodiment of the present invention, and to match the numerical identifier of the data transfer tunnel establishment request corresponding to the data transfer tunnel establishment response with the corresponding numeric identifier. , The data transfer tunnel establishment response sent by the C-GW to the MME is called the data transfer tunnel establishment response 1.
After the data transfer tunnel is established between the source U-GW and the source transfer U-GW, the C-GW returns the data transfer tunnel establishment response 1 to the MME, the data transfer tunnel is established, and the service is switched. Notify the MME that it can be implemented.
S315. MME sends a switching command to the source base station.
The MME sends a switching command to the source base station, which carries the forwarding U-GW address and tunnel end point information. If multiple forwarding U-GWs are required, for example source forwarding U-GW and target forwarding U-GW, the command is the address and tunnel end information of the source forwarding U-GW located within the source location area of the UE. To carry.
S316. The source base station carries out the data switching procedure.
The next step is for the source base station to continue performing the existing data switching procedure, hand over the UE to the target cell, instruct the UE to access the target cell, and perform a complete handover of the UE to the target location. In, the existing switching procedure can be reused.
In the switching process and after the switching is completed, the uplink / downlink user plane data transmission path is UE target base station transfer U-GW source U-GW, that is, dashed line L3a, dashed line L4a, in FIG. It changes to the transmission path indicated by the dashed line L5a and the dashed line L6a. Note that the uplink / downlink user plane data transmission path passes through the source U-GW before, during, and after switching. However, considering that both the source U-GW and the forwarding U-GW have moved downward towards a position closer to the UE, the source U-GW is also very close to the forwarding U-GW and therefore of the user plane data. RTT does not increase significantly. If the C-GW determines that two or more U-GWs will be used as the forwarding U-GW, the data forwarding tunnel route of the forwarding U-GW goes through all the forwarding U-GWs. For example, if the transfer U-GW includes a target transfer U-GW and a source transfer U-GW, the transmission path changes to UE target base station target transfer U-GW source transfer U-GW source U-GW. ..
The data transfer tunnel established in this embodiment of the present invention is the user plane bearer context between the source U-GW serving the UE and the transfer U-GW, and the transfer U-GW and the target base station of the UE. It should be understood that it is implemented by creating a user plane bearer context between them. The user plane bearer context is the routing information required to transfer user plane data, including the routing information of the source U-GW, the routing information of the forwarding U-GW, and the routing information of the target base station (for example, address and tunnel). End point information) is included. This is also applicable to other embodiments of the present invention.
In this embodiment of the present invention, the C-GW determines the transfer U-GW according to the current position information of the UE. A data transfer tunnel is established between the source U-GW and the transfer U-GW to ensure service continuity in the UE's mobile process and to ensure the user service experience.
FIG. 4 is another dialogue flowchart that guarantees service continuity according to one embodiment of the present invention. In FIG. 4, the source base station is the serving base station used before the UE moved to the current position region. The target base station is a serving base station that is used after the UE has moved to the current position area. The UE serving MME and serving C-GW remain unchanged before and after the movement of the UE. The source U-GW is the serving U-GW used before the UE moved to the current position area. The target U-GW is the U-GW used after the UE has moved to the current position area. The transfer U-GW is a U-GW that is used after the UE has moved to the current location area and is used for data service switching. Prior to service switching, the uplink / downlink user plane data transmission path is the transmission path indicated by the UE source base station source U-GW, ie, the dashed lines L1b and L2b in FIG.
S401. The source base station starts the user plane data switching procedure for the UE in connection mode.
S402. The source base station sends a service switch request message to the MME.
S403.MME sends a service switching notification message to C-GW.
S404.C-GW determines the target U-GW and the forwarding U-GW.
For the specific implementation form of steps S401 to S404, refer to steps S301 to S304 in FIG.
S405.C-GW sends a session creation request to the target U-GW.
After selecting the appropriate target U-GW, the C-GW initiates a session creation request to the target U-GW to create a bearer context for user plane data transmission on the target U-GW for the UE. can do.
S406. Target U-GW sends a session creation response to C-GW.
The target U-GW creates a bearer context for the UE's user plane data transmission for the UE according to the session creation request. Each bearer context created contains the target U-GW's address (such as IP address) and tunnel endpoint information (such as GTP TEID).
After the bearer context has been created, the target U-GW can send a session creation response to the C-GW.
S407.C-GW returns a switch notification confirmation response message to MME.
The C-GW returns a switching notification confirmation response message to the MME, and adds the address of the target U-GW selected by the C-GW and the tunnel end point information to the message.
S408.MME sends a service switch request message to the target base station.
The MME sends a service switch request message to the target base station, which carries the target U-GW address and tunnel end point information sent by the C-GW.
S409. The target base station returns a switch request confirmation response message to the MME.
After receiving the service switch request message sent by the MME, the target base station returns a switch request acknowledgment message to the MME and sends the MME the address (such as the IP address) and the address (such as the GTP TEID) of the target base station. Tunnel end point information can be transmitted. Similarly, the target base station address and tunnel end point information may be transmitted by using a switch request acknowledgment message or may be transmitted alone.
S410.MME sends a data transfer tunnel establishment request to C-GW.
S411.C-GW sends a data transfer tunnel establishment request to transfer U-GW.
S412. The transfer U-GW returns the data transfer tunnel establishment response to the C-GW.
S413.C-GW sends a data transfer tunnel establishment request to the source U-GW.
S414. Source U-GW returns a data transfer tunnel establishment response to C-GW.
S415. Establish a data transfer tunnel between the source U-GW and the transfer U-GW.
S416.C-GW returns a data transfer tunnel establishment response to MME.
S417.MME sends a switching command to the source base station.
For the specific implementation form of steps S410 to S417, refer to steps S308 to S315 in FIG.
S418. The source base station carries out the data switching procedure.
The next step is for the source base station to continue performing the existing data switching procedure, hand over the UE to the target cell, instruct the UE to access the target cell, and perform a complete handover of the UE to the target location. In, the existing switching procedure can be reused.
In the switching process and after the switching is complete, the downlink user plane data transmission path is source base station source U-GW transfer U-GW target base station UE, ie, dashed line L3b, dashed line L4b in FIG. , Dashed line L5b, and dashed line L6b. In the switching process and after the switching is complete, the uplink user plane data transmission path is the UE target base station target U-GW, that is, the transmission path indicated by the dashed lines L7b and L8b in FIG.
In this embodiment of the present invention, the C-GW determines whether the serving U-GW should be changed according to the current position information of the UE, and the selected target U-GW communicates directly with the source U-GW. Select the transfer U-GW depending on whether it can be done. A data transfer tunnel is established between the source U-GW and the transfer U-GW to ensure service continuity in the UE's mobile process and to ensure the user service experience. In addition, the C-GW immediately initiates a bearer context setup request for the target U-GW and notifies the target base station of the target U-GW's routing information via the MME, resulting in the uplink data being forwarded. It can be transmitted directly from the target base station to the target U-GW without passing through the U-GW and the source U-GW, and routing optimization of uplink data transmission is implemented.
It should be understood that the dialogue procedure in the embodiments shown in FIGS. 3 and 4 is applicable to scenarios in which the UE serving MME and serving C-GW remain unchanged before and after the movement of the UE. If the serving MME of the UE changes before and after the movement of the UE, but the serving C-GW does not change, the signaling interaction between the source MME and the target MME increases based on the solution in the embodiments of the present invention. Only. Signaling interaction processes belong to existing techniques and details are not described in the present invention.
FIG. 5 is yet another dialogue flow chart that guarantees service continuity according to one embodiment of the present invention. In FIG. 5, the source base station is the serving base station used before the UE moved to the current position region. The target base station is a serving base station that is used after the UE has moved to the current position area. The source MME is the serving MME used before the UE moved to the current position area. The target MME is the serving MME used after the UE has moved to the current position area. The source C-GW is the serving C-GW used before the UE moved to the current position region. The target C-GW is the serving C-GW used after the UE has moved to the current position area. The source U-GW is the serving U-GW used before the UE moved to the current position area. The target U-GW is the U-GW used after the UE has moved to the current position area. The transfer U-GW is a U-GW that is used after the UE has moved to the current location area and is used for data service switching. Prior to service switching, the uplink / downlink user plane data transmission path is the transmission path indicated by the UE source base station source U-GW, ie, the dashed lines L1c and L2c in FIG.
The specific service switching procedure in this embodiment of the present invention is as follows.
S501. The source base station starts the user plane data switching procedure for the UE in connection mode.
When the UE source base station detects that the UE has moved out of the service range of the source base station and the UE is performing the user plane data service, the source base station initiates the connection mode user plane data service switching procedure. Can be decided to do.
S502. The source base station sends a service switch request message to the source MME.
The service switch request message sent by the source base station to the source MME to distinguish it from the service switch request message of another step in this embodiment of the present invention is referred to as service switch request message 1.
The source base station sends a service switch request message 1 to the current serving MME (ie, the source MME in FIG. 5) and adds the UE's current location information to the message. The current position information of the UE includes TAI corresponding to the current position area of the UE, serving base station information corresponding to the current position area of the UE, and the like. The corresponding TAI used when the UE moves to the current position region is the UE's target TAI. The corresponding serving base station information used after the UE has moved to the current location area is the UE's target base station information. The target base station information can be a target base station identification information (Identity, ID), a target cell identifier (Cell Identity, CI), or the like. It should be understood that the current location region of the UE is also referred to as the target location region of the UE, i.e., the location region of the UE after the UE has moved out of the service range of the source serving base station. Similarly, the current position information of the UE is also called the target position information of the UE.
S503. The source MME sends a forwarding relocation request message to the target MME.
The source MME determines whether the UE has moved out of the service range of the source MME according to the current location information of the UE. When the UE moves out of the service range of the source MME, the source MME selects the appropriate target MME according to the current location information of the UE and sends a transfer relocation request message to the target MME, and the message is the current location information of the UE. To carry. The target MME is the MME that serves the UE after it has moved to the current location area.
S504. Target MME determines target C-GW.
The target MME determines whether the UE's current serving C-GW needs to be reassigned according to the UE's current location information, i.e., whether the UE has moved out of the service range of the source C-GW. When the serving C-GW needs to be reassigned, the target MME selects the appropriate target C-GW according to the current position information of the UE.
S505. The target MME sends a serving C-GW change notification message to the source MME.
The target MME sends a serving C-GW change notification message to the source MME to notify the source MME that the serving C-GW of the UE needs to change. When a serving C-GW change notification message is sent to the source MME, an existing message, for example a Change Notification Request message, may be reused and new directive information is added to the message. , Or a new message may be defined. This is not limited to this embodiment of the present invention.
S506. The source MME sends a service switch notification message to the source C-GW.
The service switching notification message transmitted by the source MME to the source C-GW to distinguish it from the service switching notification message of another step in this embodiment of the present invention is referred to as service switching notification message 1.
After receiving the service switch request message 1, the UE's serving MME (source MME) learns that the UE has moved out of the service range of the current base station (source base station), and then the current serving C-GW ( Send service switch notification message 1 to source C-GW). The message carries the serving C-GW change instruction information. The source MME reuses existing messages, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message, to notify the service switchover. You can send message 1 and add the UE's current location to the message. Alternatively, the source MME can define a new message and send the service switch notification message 1. This is not limited to this embodiment of the present invention.
S507. Source C-GW sends a service switch notification acknowledgment to source MME.
In order to distinguish it from the switching request confirmation response message of another step in this embodiment of the present invention, and to match the numeric identifier of the service switching request message corresponding to the switching notification confirmation response message with the corresponding numeric identifier. The switch request acknowledgment message sent by the source C-GW to the source MME is called the switch notification acknowledgment message 1.
After receiving the service switch notification message 1 sent by the source MME, the source C-GW can return the switch notification acknowledgment message 1 to the source MME, and the message will be from the source U-GW (such as the IP address). ) Carry address and tunnel end information (such as GTP TEID).
S508. The source MME returns a C-GW change notification acknowledgment to the target MME.
The source MME replies to the target MME with a C-GW change notification acknowledgment, which carries the source U-GW's address (such as the IP address) and tunnel endpoint information (such as the GTP TEID).
S509. The target MME sends a service switch notification message to the target C-GW.
The service switching notification message transmitted by the target MME to the target C-GW is referred to as the service switching notification message 2 in order to distinguish it from the service switching notification message of another step in this embodiment of the present invention.
The target MME sends a service switch notification message 2 to the target C-GW. The service switching notification message 2 carries the current position information of the UE, including the target TAI and the target base station information (base station ID). The service switch notification message is used to notify the C-GW that the UE needs to be handed over to a new target location area (ie, the UE's current location area). The target MME reuses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message, to notify the service switchover. You can send message 2 and add UE target location information to the message. Alternatively, the target MME can define a new message and send the service switch notification message 2. This is not limited to this embodiment of the present invention.
S510. Target C-GW determines target U-GW and forwarding U-GW.
After knowing the switch request, the target C-GW selects the appropriate target U-GW according to the current position information of the UE, and the target U-GW provides the optimum data transmission path within the target position for the UE. Guarantee that you can reduce the transmission RTT of user plane data as much as possible.
In addition, the target C-GW needs to check if the target U-GW can communicate directly with the source U-GW. If the target U-GW can communicate directly with the source U-GW, then the target U-GW is the forwarding U-GW, that is, the transmissions made to the forwarding U-GW in all subsequent steps are This is a transmission performed to the target U-GW. If the target U-GW cannot communicate directly with the source U-GW, the target C-GW forwards the U-GW that can communicate directly with the source U-GW according to the current location information of the UE. Select as.
Note that there may be more than one forwarding U-GW to ensure service continuity in special scenarios. Normally, when the UE moves to the adjacent U-GW pool, the target C-GW selects the default U-GW in the adjacent U-GW pool as the target forwarding U-GW. If the default U-GW also cannot communicate directly with the source U-GW, then the target C-GW will also act as the source forwarding U-GW, the default U-GW in the U-GW pool where the source U-GW is located. The two forwarding U-GWs can be selected and are used to ensure service continuity in the UE's mobile process.
S511. The target C-GW sends a switch notification confirmation response message to the target MME.
In order to distinguish it from the switching request confirmation response message of another step in this embodiment of the present invention, and to match the numeric identifier of the service switching request message corresponding to the switching notification confirmation response message with the corresponding numeric identifier. The switch request acknowledgment message sent by the target C-GW to the target MME is called the switch notification acknowledgment message 2.
After determining the forwarding U-GW, the target C-GW replies the switching notification acknowledgment message 2 to the target MME according to the service switching notification message 2 of the target MME, and the forwarding selected by the target C-GW in the message. You can add U-GW addresses (such as IP addresses) and tunnel endpoint information (such as GTP TEID).
If there are multiple forwarding U-GWs, such as the source forwarding U-GW and the target forwarding U-GW, the target C-GW will in the switch notification acknowledgment message the target forwarding U located within the current location region of the UE. -You can add GW address and tunnel end point information. When sending a switch notification acknowledgment message to the target MME, the target C-GW receives a session create response (Create Session Response) message, a bearer modify response (Modify Bearer Response) message, or an access bearer modify response (Modify Access Bearers Response). An existing message, such as a message, can be reused, or a new message can be defined to send the switch notification acknowledgment message 2. This is not limited to this embodiment of the present invention.
S512. The target MME sends a service switch request message to the target base station.
The service switching request message transmitted by the target MME to the target base station is referred to as service switching request message 2 to distinguish it from the service switching request message of another step in this embodiment of the present invention.
The target MME sends a service switch request message 2 to the target base station, sends the forwarding U-GW address and tunnel end point information to the target base station, and as a result, the uplink data transmission path is the forwarding U-GW. Handed over to.
S513. The target base station sends a switch request confirmation response message to the target MME.
In order to distinguish it from the switching request confirmation response message of another step in this embodiment of the present invention, and to match the numeric identifier of the service switching request message corresponding to the switching request confirmation response message with the corresponding numeric identifier. The switch request acknowledgment message sent by the target base station to the target MME is called the switch request acknowledgment message 2.
The target base station returns a switch request confirmation response message 2 and sends the target base station's address (such as IP address) and tunnel end point information (such as GTP TEID) to the target MME.
S514. The target MME sends a data transfer tunnel establishment request to the target C-GW.
The data transfer tunnel establishment request transmitted by the target MME to the target C-GW is referred to as data transfer tunnel establishment request 1 to distinguish it from the data transfer tunnel establishment request of another step in this embodiment of the present invention.
The target MME sends a data transfer tunnel establishment request 1 to the target C-GW, sends the target base station address and tunnel end point information to the C-GW, and as a result, the downlink data transmission path is the target base station. Handed over to.
S515. Target C-GW sends a data transfer tunnel establishment request to transfer U-GW.
To distinguish it from the data transfer tunnel establishment request of another step in this embodiment of the present invention, the data transfer tunnel establishment request transmitted by the target C-GW to the transfer U-GW is the data transfer tunnel establishment request 2. be called.
The target C-GW sends a data transfer tunnel establishment request 2 to the transfer U-GW, and sends the target base station address and tunnel end point information, and the source U-GW address and tunnel end point information to the transfer U-GW. To do.
If multiple forwarding U-GWs are required, the target C-GW should send a data forwarding tunnel establishment request to each forwarding U-GW, which carries the address of the peer network element and the tunnel endpoint information. To do.
S516. The transfer U-GW returns a data transfer tunnel establishment response to the target C-GW.
Target C by the transfer U-GW to distinguish it from the data transfer tunnel establishment response of another step in this embodiment of the invention and to respond to the data transfer tunnel establishment request corresponding to the data transfer tunnel establishment response. -The data transfer tunnel establishment response sent to the GW is called the data transfer tunnel establishment response 2.
The transfer U-GW returns a data transfer tunnel establishment response 2 to the target C-GW, responds to the data transfer tunnel establishment request 2 sent by the target C-GW, and connects the target base station and the transfer U-GW. Determines that the establishment of a data transfer tunnel between and the establishment of a data transfer tunnel between the source U-GW and the transfer U-GW is permitted. In some cases, the data transfer tunnel establishment response 2 can carry the address of the transfer U-GW and the tunnel end point information.
If multiple transfer D-GWs are required in step S510, the C-GW should send a data transfer tunnel establishment request to each transfer D-GW, and each transfer D-GW responds accordingly. , A data transfer tunnel establishment response should be returned to indicate that the data transfer tunnel establishment is allowed.
S517. The target C-GW returns a data transfer tunnel establishment response to the target MME.
To distinguish from the data transfer tunnel establishment response of another step in this embodiment of the present invention, and to match the numerical identifier of the data transfer tunnel establishment request corresponding to the data transfer tunnel establishment response with the corresponding numeric identifier. The data transfer tunnel establishment response sent by the target C-GW to the target MME is called the data transfer tunnel establishment response 1.
After receiving the data transfer tunnel establishment response 2, the target C-GW returns the data transfer tunnel establishment response 1 to the target MME, and the establishment of the data transfer tunnel between the target base station and the transfer U-GW is permitted. Decide to do that.
S518. The target MME sends a transfer relocation response to the source MME.
After deciding that a data transfer tunnel can be established between the target base station and the transfer U-GW, the target MME can send a transfer relocation response to the source MME and the response will be on the transfer U-GW. Carry address and tunnel end point information.
S519. The source MME sends a data transfer tunnel establishment request to the source C-GW.
To distinguish it from the data transfer tunnel establishment request of another step in this embodiment of the present invention, the data transfer tunnel establishment request transmitted by the source MME to the source C-GW is referred to as data transfer tunnel establishment request 3.
The source MME sends a data transfer tunnel establishment request 3 to the source C-GW, and sends the address of the transfer U-GW and the tunnel end point information to the source C-GW.
S520. Source C-GW sends a data transfer tunnel establishment request to source U-GW.
To distinguish it from the data transfer tunnel establishment request of another step in this embodiment of the present invention, the data transfer tunnel establishment request transmitted by the source C-GW to the source U-GW is the data transfer tunnel establishment request 4. be called.
The source C-GW sends a data transfer tunnel establishment request 4 to the source U-GW, and sends the address of the transfer U-GW and the tunnel end point information to the source U-GW.
S521. Source U-GW sends a data transfer tunnel establishment response to source C-GW.
To distinguish from the data transfer tunnel establishment response of another step in this embodiment of the present invention, and to match the numerical identifier of the data transfer tunnel establishment request corresponding to the data transfer tunnel establishment response with the corresponding numeric identifier. , The data transfer tunnel establishment response sent by the source U-GW to the source C-GW is called the data transfer tunnel establishment response 4.
After receiving the data transfer tunnel establishment request 4 sent by the source C-GW, the source U-GW returns a data transfer tunnel establishment response 4 to transfer data between the transfer U-GW and the source U-GW. It can be decided that the establishment of the tunnel is allowed.
S522. Establish a data transfer tunnel between the source U-GW and the transfer U-GW.
After the peer U-GW address and tunnel end point information are obtained, a data transfer tunnel between the source U-GW and the transfer U-GW is established.
Of course, in step S510, if multiple forwarding U-GWs, eg, a source forwarding U-GW and a target forwarding U-GW, are determined, a data forwarding tunnel between the source U-GW and the source forwarding U-GW, And a data transfer tunnel between the source transfer U-GW and the target transfer U-GW is established correspondingly.
S523. Source C-GW sends a data transfer tunnel establishment response to source MME.
To distinguish from the data transfer tunnel establishment response of another step in this embodiment of the present invention, and to match the numerical identifier of the data transfer tunnel establishment request corresponding to the data transfer tunnel establishment response with the corresponding numeric identifier. The data transfer tunnel establishment response sent by the source C-GW to the source MME is called the data transfer tunnel establishment response 3.
After receiving the data transfer tunnel establishment response 4, the source C-GW returns the data transfer tunnel establishment response 3 to the source MME, allowing the establishment of the data transfer tunnel between the transfer U-GW and the source U-GW. You can decide to be done.
S524. The source MME sends a switching command to the source base station.
The source MME sends a switching command to the source base station, which carries the forwarding U-GW address and tunnel end point information.
When multiple forwarding U-GWs are required, the address and tunnel end point information of the source forwarding U-GW located within the source location area of the UE is carried within the switching command.
S525. The source base station continues to implement the existing data switching procedure, hands over the UE to the target cell, tells the UE to access the target cell, and then gives the UE a complete handover to the target location. Reuse existing switching procedures to implement.
In the switching process and after the switching is completed, the uplink / downlink user plane data transmission path is UE target base station transfer U-GW source U-GW, that is, dashed line L3c, dashed line L4c, in FIG. It changes to the transmission path indicated by the dashed line L5c and the dashed line L6c. Note that the uplink / downlink user plane data transmission path passes through the source U-GW before, during, and after switching. However, considering that both the source U-GW and the forwarding U-GW have moved downward towards a position closer to the UE, the source U-GW is also very close to the forwarding U-GW and therefore of the user plane data. RTT does not increase significantly.
In this embodiment of the invention, the target C-GW determines the transfer U-GW according to the current location information of the UE, ensures service continuity in the UE's mobile process, and sources to ensure the user service experience. Establish a data transfer tunnel between the U-GW and the transfer U-GW.
FIG. 6 is yet another dialogue flow chart that guarantees service continuity according to one embodiment of the present invention. In FIG. 6, the source base station is the serving base station used before the UE moved to the current position region. The target base station is a serving base station that is used after the UE has moved to the current position area. The source MME is the serving MME used before the UE moved to the current position area. The target MME is the serving MME used after the UE has moved to the current position area. The source C-GW is the serving C-GW used before the UE moved to the current position region. The target C-GW is the serving C-GW used after the UE has moved to the current position area. The source U-GW is the serving U-GW used before the UE moved to the current position area. The target U-GW is the U-GW used after the UE has moved to the current position area. The transfer U-GW is a U-GW that is used after the UE has moved to the current location area and is used for data service switching. Prior to service switching, the uplink / downlink user plane data transmission path is the transmission path indicated by the UE source base station source U-GW, ie, dashed line L1d and dashed line L2d in FIG.
The specific service switching procedure in this embodiment of the present invention is as follows.
S601. The source base station starts the user plane data switching procedure for the UE in connection mode.
S602. The source base station sends a service switch request message.
S603. The source MME sends a transfer relocation request message.
S604. Target MME determines target C-GW.
S605. The target MME sends a serving C-GW change notification message to the source MME.
S606. The source MME sends a service switch notification message to the source C-GW.
S607. Source C-GW sends a service switch notification acknowledgment to source MME.
S608. The source MME returns a C-GW change notification confirmation response to the target MME.
S609. The target MME sends a service switch notification message to the target C-GW.
S610. Target C-GW determines target U-GW and forwarding U-GW.
For the specific mounting form of steps S601 to S610, refer to steps S501 to S510 in FIG.
S611. Target C-GW sends a session creation request to target U-GW.
After selecting the appropriate target U-GW, the target C-GW makes a session creation request to the target U-GW to create a bearer context for user plane data transmission on the target U-GW for the UE. You can start.
S612. Target U-GW sends a session creation response to target C-GW.
The target U-GW creates a bearer context for the UE's user plane data transmission for the UE according to the session creation request. Each bearer context created contains the target U-GW's address (such as IP address) and tunnel endpoint information (such as GTP TEID).
After the bearer context has been created, the target U-GW can send a session creation response to the target C-GW.
S613. Target C-GW sends a switch notification confirmation response message to target MME.
In order to distinguish it from the switching request confirmation response message of another step in this embodiment of the present invention, and to match the numeric identifier of the service switching request message corresponding to the switching notification confirmation response message with the corresponding numeric identifier. The switch request acknowledgment message sent by the target C-GW to the target MME is called the switch notification acknowledgment message 2.
After determining the forwarding U-GW, the target C-GW returns a switch notification acknowledgment message 2 to the target MME according to the service switch notification message 2 of the target MME, and in the message, the target selected by the target C-GW. You can add U-GW addresses (such as IP addresses) and tunnel endpoint information (such as GTP TEID).
S614. The target MME sends a service switch request message to the target base station.
The service switching request message transmitted by the target MME to the target base station is referred to as service switching request message 2 to distinguish it from the service switching request message of another step in this embodiment of the present invention.
The target MME sends a service switch request message 2 to the target base station, and the message carries the address and tunnel end point information of the target U-GW sent by the target C-GW.
S615. The target base station sends a switch request confirmation response message to the target MME.
In order to distinguish it from the switching request confirmation response message of another step in this embodiment of the present invention, and to match the numeric identifier of the service switching request message corresponding to the switching request confirmation response message with the corresponding numeric identifier. The switch request acknowledgment message sent by the target base station to the target MME is called the switch request acknowledgment message 2.
The target base station returns a switch request confirmation response message 2 and sends the target base station's address (such as IP address) and tunnel end point information (such as GTP TEID) to the target MME.
S616. The target MME sends a data transfer tunnel establishment request to the target C-GW.
S617. The target C-GW sends a data transfer tunnel establishment request to the transfer U-GW.
S618. The transfer U-GW returns a data transfer tunnel establishment response to the target C-GW.
S619. The target C-GW returns a data transfer tunnel establishment response to the target MME.
S620. The target MME sends a transfer relocation response to the source MME.
S621. The source MME sends a data transfer tunnel establishment request to the source C-GW.
S622. Source C-GW sends a data transfer tunnel establishment request to source U-GW.
S623. Source U-GW sends a data transfer tunnel establishment response to source C-GW.
S624. Establish a data transfer tunnel between the source U-GW and the transfer U-GW.
S625. Source C-GW sends a data transfer tunnel establishment response to source MME.
S626. The source MME sends a switching command to the source base station.
For the specific implementation form of steps S616 to S626, refer to steps S514 to S524 in FIG.
S627. The source base station continues to implement the existing data switching procedure, hands over the UE to the target cell, tells the UE to access the target cell, and then gives the UE a complete handover to the target location. Reuse existing switching procedures to implement.
In the switching process and after the switching is complete, the downlink user plane data transmission path is source base station source U-GW transfer U-GW target base station UE, ie, dashed line L3d, dashed line L4d in FIG. , Dashed line L5d, and dashed line L6d. In the switching process and after the switching is complete, the uplink user plane data transmission path is the UE target base station target U-GW, that is, the transmission path indicated by the dashed lines L7d and L8d in FIG.
In this embodiment of the solution of the present invention, the target C-GW determines whether the serving U-GW should be changed according to the current position information of the UE, and the selected target U-GW is the source U-GW. Select the forwarding U-GW depending on whether it can communicate directly. A data transfer tunnel is established between the source U-GW and the transfer U-GW to ensure service continuity in the UE's mobile process and to ensure the user service experience. In addition, the C-GW immediately initiates a bearer context setup request for the target U-GW and notifies the target base station of the target U-GW's routing information via the MME, resulting in the uplink data being forwarded. It can be transmitted directly from the target base station to the target U-GW without passing through the U-GW and the source U-GW, and routing optimization of uplink data transmission is implemented.
It should be understood that the dialogue procedure in the embodiments shown in FIGS. 5 and 6 is applicable to scenarios in which both the UE serving MME and the serving C-GW change before and after the movement of the UE. If the serving C-GW of the UE changes before and after the movement of the UE, but the serving MME does not change, the signaling interaction between the source MME and the target MME is reduced based on the solution in the embodiments of the present invention. Only. Details are not described in the present invention.
FIG. 7 is yet another dialogue flow chart that guarantees service continuity according to one embodiment of the present invention. In FIG. 7, the target base station is a serving base station used when the UE switches from idle mode to connected mode within the current position region. The source U-GW is the serving U-GW used before the UE moved to the current position area. The target U-GW is a serving U-GW used when the UE switches from idle mode to connected mode within the current position area. The transfer U-GW is a U-GW that is used after the UE has moved to the current location area and is used for data service switching. The MME is a serving MME used when the UE switches from idle mode to connected mode within the current position area. The C-GW is a serving C-GW used when the UE switches from idle mode to connected mode within the current position area.
The specific procedure in this embodiment of the present invention is as follows.
S701. UE in idle mode needs to send uplink user plane data.
S702. UE sends a signaling request to MME.
If a UE in idle mode moves out of a currently registered location area (such as the currently registered Tracking Area (TA)), the UE sends a signaling request to the MME to perform the location update procedure. You can start. For example, if the location update procedure is a Tracking Area Update (TAU) procedure, the signaling request is a location update request message.
If the UE in idle mode moves out of the service area of the current serving base station, but does not move out of the currently registered location area (such as the currently registered TA), the UE sends a signaling request to the MME. It can be sent to initiate a service request procedure, and the signaling request is a service request message.
Specifically, the UE can send a signaling request message to the serving MME by using the target base station, and the target base station sends the current position information of the UE to the MME.
The current position information of the UE includes tracking area identification information (TAI) corresponding to the current position area of the UE, serving base station information corresponding to the current position area of the UE, and the like. The corresponding TAI used when the UE moves to the current position region is the UE's target TAI. The corresponding serving base station information used when the UE moves to the current location area is the UE's target base station information. The target base station information can be a target base station identification information (Identity, ID), a target cell identifier (Cell Identity, CI), or the like. The current position area of the UE is also referred to as the target position area of the UE, that is, the position area where the UE is located after the UE has moved out of the service range of the source serving base station. Similarly, the current position information of the UE is also called the target position information of the UE.
S703.MME sends a request message to C-GW and adds the current location information of the UE to the request message.
After receiving the location update request message or service request message, the UE serving MME learns that the UE has moved out of the service range of the current base station (source base station) according to the UE's current location information, and the UE serving MME. Sends a request message to the current serving C-GW. The request message is used to indicate to the C-GW to move the UE to the new target location area. The MME can reuse existing messages such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message, or You can define a new message. This is not limited to this embodiment of the present invention.
S704.C-GW determines the target U-GW and the forwarding U-GW.
After receiving the request message sent by the MME, the C-GW can determine the target U-GW and the forwarding U-GW according to the current location information of the UE. For a specific implementation, refer to step S304 in the embodiment shown in FIG. Details are not described again herein.
S705.C-GW returns a request confirmation response message to MME.
C-GW returns a request confirmation response message to MME. For a specific implementation, refer to step S305 in the embodiment shown in FIG. Details are not described again herein.
S706. MME sends an initial context setup request message to the target base station.
The MME sends an Initial Context Setup Request message to the target base station and forwards the forwarding U-GW address and tunnel end point information sent by the C-GW to the target base station as a result. Then, the uplink data transmission path is handed over to the transfer U-GW.
S707. The target base station returns an initial context setup response message to the MME.
The target base station returns an Initial Context Setup Response message to the MME and sends the target base station's address (such as IP address) and tunnel end information (such as GTP TEID) to the MME.
S708.MME sends a bearer correction request message to C-GW.
The MME sends a bearer correction request message to the C-GW, sends the target base station address and tunnel end point information to the C-GW, and as a result, the downlink data transmission path is then handed over to the target base station. .. In some cases, this step allows the MME to send an access bearer correction request message to the C-GW that carries the target base station address and tunnel endpoint information.
S709.C-GW sends a data transfer tunnel establishment request to transfer U-GW.
S710. Transfer U-GW returns a data transfer tunnel establishment response to C-GW.
S711.C-GW sends a data transfer tunnel establishment request to the source U-GW.
S712. Source U-GW returns a data transfer tunnel establishment response to C-GW.
S713. Establish a data transfer tunnel between the source U-GW and the transfer U-GW.
For the specific implementation form of steps S709 to S713, refer to steps S309 to S313 in the embodiment shown in FIG. Details are not described again herein.
S714.C-GW returns a bearer correction response to MME.
In some cases, in response to step S708, the C-GW may reply to the MME with an access bearer correction response.
In the location update procedure or service request procedure, the uplink / downlink user plane data transmission path is UE target base station transfer U-GW source U-GW, that is, dashed line L1e, dashed line L2e, and dashed line in FIG. It changes to the transmission path indicated by L3e. Note that the uplink / downlink user plane data transmission path passes through the source U-GW. However, considering that both the source U-GW and the forwarding U-GW have moved downward towards a position closer to the UE, the source U-GW is also very close to the forwarding U-GW and therefore of the user plane data. RTT does not increase significantly. If the C-GW determines that two or more U-GWs will be used as the forwarding U-GW, the data forwarding tunnel route of the forwarding U-GW goes through all the forwarding U-GWs. For example, if the transfer U-GW includes a target transfer U-GW and a source transfer U-GW, the transmission path changes to UE target base station target transfer U-GW source transfer U-GW source U-GW. ..
In this embodiment of the present invention, the C-GW determines the transfer U-GW according to the current position information of the UE. A data transfer tunnel is established between the source U-GW and the transfer U-GW to ensure service continuity in the UE's mobile process and to ensure the user service experience.
FIG. 8 is yet another dialogue flow chart that guarantees service continuity according to one embodiment of the present invention. In FIG. 8, the target base station is a serving base station used when the UE switches from idle mode to connected mode within the current position region. The source U-GW is the serving U-GW used before the UE moved to the current position area. The target U-GW is a serving U-GW used when the UE switches from idle mode to connected mode within the current position area. The transfer U-GW is a U-GW that is used after the UE has moved to the current location area and is used for data service switching. The MME is a serving MME used when the UE switches from idle mode to connected mode within the current position area. The C-GW is a serving C-GW used when the UE switches from idle mode to connected mode within the current position area.
The specific procedure in this embodiment of the present invention is as follows.
S801. The UE in idle mode needs to send uplink user plane data.
S802.UE sends a signaling request to the MME.
For the specific implementation form of step S802, refer to step S702 in FIG. Details are not described again herein.
S803. MME sends an initial context setup request message to the target base station.
The MME sends an Initial Context Setup Request message to the target base station. This step is an existing step in an existing location update procedure or service request procedure. Therefore, in the present specification, the MME transmits the address of the source U-GW and the tunnel end point information to the target base station.
S804. The target base station returns an initial context setup response message to the MME.
The target base station returns an Initial Context Setup Response message to the MME and sends the target base station's address (such as IP address) and tunnel end information (such as GTP TEID) to the MME.
S805.MME sends a bearer correction request message to C-GW.
The MME sends a bearer correction request message to the C-GW, and sends the current position information of the UE, the address of the target base station, and the tunnel end point information to the C-GW. In some cases, this step allows the MME to send an access bearer modification request message to the C-GW that carries the UE's current location information, as well as the target base station address and tunnel end point information.
S806.C-GW determines the target U-GW and the forwarding U-GW.
After receiving the bearer modification request message sent by the MME, the C-GW can determine the target U-GW and the forwarding U-GW according to the current location information of the UE. For a specific implementation, refer to step S304 in the embodiment shown in FIG. Details are not described again herein.
S807.C-GW sends a data transfer tunnel establishment request to transfer U-GW.
S808. Transfer U-GW returns a data transfer tunnel establishment response to C-GW.
S809.C-GW sends a data transfer tunnel establishment request to the source U-GW.
S810. Source U-GW returns a data transfer tunnel establishment response to C-GW.
S811. Establish a data transfer tunnel between the source U-GW and the transfer U-GW.
For the specific implementation form of steps S807 to S811, refer to steps S309 to S313 in the embodiment shown in FIG. Details are not described again herein.
S812.C-GW returns a bearer correction response to MME.
The C-GW returns a bearer correction response message to the MME and sends the determined forwarding U-GW address and tunnel end point information to the MME. In some cases, in response to step S805, the C-GW may reply to the MME with an access bearer corrective response message, which carries the forwarding U-GW address and tunnel endpoint information.
S813. MME sends a UE context modification request to the target base station.
The MME sends a UE Context Modification Request message to the target base station and adds the forwarding U-GW address and tunnel endpoint information to the message, resulting in an uplink user plane data transmission path. Is handed over to the transfer U-GW. Note that this step is a new addition to an existing location update procedure or service request procedure.
S814. The target base station returns a UE context correction response message to the MME.
The target base station returns a UE Context Modification Response message to the MME.
In the location update procedure or service request procedure, the uplink / downlink user plane data transmission path is UE target base station transfer U-GW source U-GW, that is, dashed line L1f, dashed line L2f, and dashed line in FIG. It changes to the transmission path indicated by L3f. Note that the uplink / downlink user plane data transmission path passes through the source U-GW. However, considering that both the source U-GW and the forwarding U-GW have moved downward towards a position closer to the UE, the source U-GW is also very close to the forwarding U-GW and therefore of the user plane data. RTT does not increase significantly. If the C-GW determines that two or more U-GWs will be used as the forwarding U-GW, the data forwarding tunnel route of the forwarding U-GW goes through all the forwarding U-GWs. For example, if the transfer U-GW includes a target transfer U-GW and a source transfer U-GW, the transmission path changes to UE target base station target transfer U-GW source transfer U-GW source U-GW. ..
In this embodiment of the present invention, the C-GW determines the transfer U-GW according to the current position information of the UE. A data transfer tunnel is established between the source U-GW and the transfer U-GW to ensure service continuity in the UE's mobile process and to ensure the user service experience.
FIG. 9 is another flowchart of the service continuity guarantee method according to the embodiment of the present invention. The method of Figure 9 is implemented by the target mobility management network element. The method includes the following steps.
901. The target mobility management network element receives the transfer relocation request sent by the source mobility management network element serving the UE.
The transfer relocation request carries the current position information of the UE.
For the specific implementation form of step 901, refer to step S503 in FIG. 5 or step S603 in FIG.
In the application scenario of this embodiment of the invention, when the UE performs service communication, the post-movement location area extends beyond the service scope of the source mobility management network element (such as MME). The source mobility management network element is the serving mobility management network element that was used before the UE moved to the current location area.
902. Target Mobility Management The network element selects the UE's target C-GW according to the UE's current location information.
See step S504 in FIG. 5 or step S604 in FIG. 6 for a specific implementation of step 902.
903. The target mobility management network element sends the UE's current location information to the target C-GW, so that the target C-GW determines the UE's forwarding U-GW according to the UE's current location information.
See step S509 in FIG. 5 or step S609 in FIG. 6 for the specific implementation of step 902.
S904. The target mobility management network element sends a data transfer tunnel establishment request to the target C-GW.
A data transfer tunnel establishment request is made for the user equipment with the data transfer tunnel between the transfer U-GW and the source U-GW serving the user equipment, and with the transfer U-GW and the target base station serving the user equipment. Used to request the target control plane gateway to establish a data transfer tunnel between.
See step S514 in FIG. 5 or step S616 in FIG. 6 for a specific implementation of step 904.
In this embodiment of the invention, after the UE moves out of the service scope of the source mobility management network element, the target mobility management network element ensures service continuity in the UE's movement process and improves the user service experience. , Determine the UE's target C-GW according to the UE's current location information, and use the target C-GW to transfer data between the source U-GW and the UE's target base station for the UE. Establish a tunnel.
In some cases, in one embodiment, the target C-GW is different from the serving C-GW used before the UE moved to the current position region (ie, the serving C-GW changes in the UE moving process). .. In this case, after step 902 and before step 903, the method may further include the step of sending a change notification message to the source mobility management network element by the target mobility management network element. Used to indicate that the UE serving C-GW changes to the target C-GW. See step S505 in FIG. 5 or step S605 in FIG. 6 for a specific implementation.
Further, prior to step 903, the method may further include the step of receiving the acknowledgment message sent by the source mobility management network element according to the change notification message by the target mobility management network element, and the acknowledgment message is Carry the routing information of the UE source U-GW. See step S508 in FIG. 5 or step 608 in FIG. 6 for specific implementations.
In this embodiment of the present invention, refer to the method implemented by the target MME shown in FIG. 5 or FIG. 6 for a specific implementation of the mobility management network element. Details will not be described again in this embodiment of the invention.
FIG. 10 is still another flowchart of the service continuity guarantee method according to the embodiment of the present invention. The method in Figure 10 is carried out by C-GW. The method includes the following steps.
1001. C-GW receives the current location information of the UE sent by the mobility management network element.
This embodiment of the present invention is applicable to one of the following application scenarios: during user plane data transmission, the UE in connection mode moves and the post-movement location area is the source base station. After detecting that the service range has been exceeded and the UE has moved out of the service range of the source base station, the source base station decides to initiate the connection mode user plane data service switching procedure. The source base station is the serving base station that was used before the UE moved to the current location area.
When uplink user plane data needs to be transmitted, the UE in idle mode moves out of the currently registered location area, such as the currently registered tracking area (TA), and the UE tracks. Start a location update procedure, such as a Tracking Area Update (TAU) procedure.
When uplink user plane data needs to be transmitted, the UE in idle mode moves out of the service area of the current serving base station, but is currently registered, such as the currently registered Tracking Area (TA). The UE initiates the Service Request procedure without moving out of the location area.
In application scenario (1), after receiving the user plane data switching request sent by the source base station, the mobility management network element can send a service switching notification to the serving C-GW of the UE. It should be understood that the mobility management network element can be an MME or another network element with MME mobility management capabilities. For certain applications, the mobility management network element uses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message. By doing so, the service switch notification can be sent, or the mobility management network element can send the service switch notification by using the newly created message. The specific message used to send the service switch notification is not limited in the present invention.
In application scenario (2), after receiving the location update request sent by the UE, or after successfully creating a wireless access bearer context for the UE, the mobility management network element sends a request message to the UE's serving C-GW. Can be sent. It should be understood that the mobility management network element can be an MME or another network element with MME mobility management capabilities. For certain applications, the mobility management network element uses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message. The request message can be sent by doing so, or the mobility management network element can send the request message by using the newly created message. The specific message used to send the request message is not limited in the present invention.
In application scenario (3), after receiving a service request sent by the UE, or after successfully creating a wireless access bearer context for the UE, the mobility management network element sends a request message to the UE's serving C-GW. Can be sent. It should be understood that the mobility management network element can be an MME or another network element with MME mobility management capabilities. For certain applications, the mobility management network element uses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message. The request message can be sent by doing so, or the mobility management network element can send the request message by using the newly created message. The specific message used to send the request message is not limited in the present invention.
Note that C-GW is a C-GW that serves the UE.
Note that the mobility management network element is a mobility management network element that serves the UE. For certain applications, the mobility management network element can be an MME or another network element with MME mobility management capabilities.
1002. C-GW selects the target U-GW for UE according to the current position information of UE.
1003. C-GW sends a request message to the mobility management network element.
The request message is used to request the mobility management network element to release the first bearer context and instruct the UE to send a setup request for the second bearer context, the first bearer context. Is the UE bearer context established on the UE source U-GW, and the second bearer context is the bearer context reestablished by the UE on the target U-GW according to the first bearer context.
In some cases, in one embodiment, the request message is a bearer removal request message, the bearer removal request message carries a reactivation request instruction, and the reactivation request instruction uses a mobility management network element. Used to indicate to the UE to initiate a setup request for the second bearer context after the first bearer context has been deleted.
It should be understood that both MME and UE record the first bearer context created by UE on the source U-GW. After receiving the bearer removal request message, the MME tells the UE to remove the first bearer context on the MME and remove the first bearer context on the UE. When the bearer delete request message carries the reactivation request instruction, the MME further sends the reactivation request instruction to the UE to follow the contents of the first bearer context after the first bearer context has been deleted. Indicate the UE to resend the setup request for the bearer context and request that a second bearer context be created. The second bearer context is a bearer context created on the target U-GW according to the first bearer context. The second bearer context typically contains the same Access Point Name (APN) as the first bearer context.
In this embodiment of the invention, before the UE changes from idle mode to connected mode and transmits user plane data, the C-GW determines the UE's serving U-GW according to the UE's current location information and bearer context. Trigger the deactivation procedure, add a reactivation request instruction during the bearer context deactivation procedure, recreate the bearer resource on the target U-GW, and provide service continuity for subsequent user plane data transmissions. Instruct the UE to start the bearer context re-creation procedure to ensure and ensure the user service experience.
Hereinafter, the method in the embodiment of the present invention will be further described with reference to the specific embodiment.
FIG. 11 is yet another dialogue flow chart that guarantees service continuity according to one embodiment of the present invention. In FIG. 11, the target base station is a serving base station used when the UE switches from idle mode to connected mode within the current position region. The target U-GW is a serving U-GW used when the UE switches from idle mode to connected mode within the current position area. The MME is a serving MME used when the UE switches from idle mode to connected mode within the current position area. The C-GW is a serving C-GW used when the UE switches from idle mode to connected mode within the current position area.
The specific procedure in this embodiment of the present invention is as follows.
S1101. UE sends a signaling request to MME.
The idle mode UE needs to send uplink signaling or data, so the idle mode UE sends signaling to the MME requesting a switch to connected mode. The UE initiates a Service Request or Tracking Area Update (TAU) procedure to switch from idle mode to connected mode.
In the process of switching from idle mode to connected mode, the target base station, the UE's current serving base station, reports the UE's current location to the current serving MME, and the UE's current location is the current tracking area. It can be the identification information (Tracking Area Identity, TAI) and / or the current cell identifier (Cell Identity, CI).
S1102. MME sends a location update notification message to C-GW.
After receiving a signaling request sent by the UE to switch from idle mode to connected mode, for example a Service Request message or a TAU request message, the MME presents the UE's current location as reported by the base station. Determine if the UE position has changed according to the information.
If the position of the UE does not change, the prior art method is practiced. Details are not described in this embodiment of the invention. When the position of the UE changes, the MME sends a position update notification message to the C-GW of the UE. As used herein, the MME can determine whether the position of the UE has changed in the following two scenarios.
(a) If the serving MME does not change, the MME can compare the previously stored position information of the UE with the current position information reported by the target base station to determine the change in the position of the UE.
(b) If the MME changes, i.e. the new MME receives the signaling request in the step, the new MME can be considered to have changed the position of the UE.
The MME sends a location update notification message to the serving C-GW, which carries the current location information of the UE, including the current TAI, current cell identifier, and so on. The position update notification message is used to notify the C-GW that the current position area of the UE has changed. Therefore, the MME reuses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message, on the UE. You can carry the current location information, or you can define a new message to carry the current location information of the UE. This is not limited in the present invention.
In addition, the MME determines if the UE's serving C-GW needs to be reassigned according to the UE's current location, that is, if the UE has moved out of the current serving C-GW's service area. can do. If the serving C-GW needs to be reassigned, the MME selects the new C-GW as the serving C-GW according to the current location information of the UE and sends a location update notification message to the new C-GW. In addition, the MME can request the new C-GW to recreate the bearer context for the UE.
S1103.C-GW determines U-GW.
The C-GW determines whether the UE's current serving U-GW needs to be reassigned according to the UE's current location information. If the UE's current serving U-GW needs to be reassigned, the C-GW selects the appropriate target U-GW according to the UE's current location information and performs step S1104. When C-GW is reassigned in S1102, generally, serving U-GW also needs to be reassigned.
S1104.C-GW sends a bearer deletion request to MME.
After sending the bearer removal request to the MME, the C-GW initiates the bearer deactivation procedure for the UE to release all bearer context resources created by the UE on the source U-GW. In addition, the bearer delete request message is a packet data network (PDN) after all bearer context resources in the source D-GW have been deleted in order to recreate the user plane bearer resource on the target D-GW. ) Carry a Reactivation requested instruction to request the UE to start the connection establishment request immediately.
S1105. MME sends a detach request or bearer context deactivation request to the UE.
After receiving the C-GW bearer removal request, the MME takes various actions according to the UE's current Packet Data Network (PDN) connection information: (a) The UE currently has only one PDN. If it has a connection, the MME initiates a detach procedure for the UE and adds a re-attach required instruction to the Detach Request. (b) If the UE currently has multiple PDN connections, the MME initiates the PDN connection deactivation procedure for the UE and reactivates the Deactivate Bearer Context Request. Add instructions.
S1106. UE initiates a PDN connection establishment request.
The UE initiates a PDN connection establishment request to restore the bearer context that the C-GW requested to remove in step S1104. The PDN connection establishment request carries the same APN as the bearer context requested by the C-GW to be deleted in step S1104. In this procedure, C-GW uses the selected target D-GW to create a bearer context for the UE.
If the UE receives the detach request sent by the MME in step S1105, the attach procedure is initiated and the PDN connection establishment procedure is added to the attach procedure. For the specific mounting form, refer to the prior art.
If the UE receives the bearer context deactivation request in step S1105 and deactivates the PDN connection, a separate PDN connection establishment procedure is initiated. For the specific mounting form, refer to the prior art.
In the PDN connection establishment procedure, the uplink / downlink user plane data transmission path is changed to the transmission path indicated by the UE target base station target U-GW, that is, the dashed line L1g and the dashed line L2g in FIG.
In this embodiment of the present invention, whether the C-GW needs to change the serving U-GW according to the current position information of the UE before the UE changes from the idle mode to the connection mode and transmits the user plane data. To trigger the PDN connection deactivation procedure, add a reactivation request instruction during the PDN connection deactivation procedure, recreate the bearer resource on the target U-GW, and follow user plane data. Request the UE to start the PDN connection reestablishment procedure immediately to ensure the service continuity of the transmission and the user service experience.
FIG. 12 is a schematic structural diagram of the control plane gateway 1200 according to the embodiment of the present invention. As shown in FIG. 12, the control plane gateway 1200 may include a receive unit 1201, a select unit 1202, and a tunnel establishment unit 1203.
Receiving unit 1201 is configured to receive the current location information of the UE transmitted by the mobility management network element.
Selection unit 1202 is configured to select at least one transfer U-GW for the UE according to the current location information of the UE.
In this embodiment of the invention, the current location area of the UE exceeds the service range of the current serving U-GW of the UE, and the C-GW selects the appropriate transfer U-GW for the UE according to the current position area of the UE. There is a need to.
The tunnel establishment unit 1203 is a data transfer tunnel between the source U-GW and the transfer U-GW serving the UE and a data transfer tunnel between the transfer U-GW and the UE's target base station for the UE. Is configured to establish. The data transfer tunnel is used in the UE's move process to transmit the UE's uplink user plane data and / or downlink user plane data.
For applicable scenarios of this embodiment of the present invention, see Application Scenarios of the Embodiment Shown in FIG.
In application scenario (1), after receiving the user plane data switching request sent by the source base station, the mobility management network element can send a service switching notification to the serving C-GW of the UE. It should be understood that the mobility management network element can be an MME or another network element with MME mobility management capabilities. For certain applications, the mobility management network element uses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message. By doing so, the service switch notification can be sent, or the mobility management network element can send the service switch notification by using the newly created message. The specific message used to send the service switch notification is not limited in the present invention.
In application scenario (2), after receiving the location update request sent by the UE, or after successfully creating a wireless access bearer context for the UE, the mobility management network element sends a request message to the UE's serving C-GW. Can be sent. It should be understood that the mobility management network element can be an MME or another network element with MME mobility management capabilities. For certain applications, the mobility management network element uses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message. The request message can be sent by doing so, or the mobility management network element can send the request message by using the newly created message. The specific message used to send the request message is not limited in the present invention.
In application scenario (3), after receiving a service request sent by the UE, or after successfully creating a wireless access bearer context for the UE, the mobility management network element sends a request message to the UE's serving C-GW. Can be sent. It should be understood that the mobility management network element can be an MME or another network element with MME mobility management capabilities. For certain applications, the mobility management network element uses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message. The request message can be sent by doing so, or the mobility management network element can send the request message by using the newly created message. The specific message used to send the request message is not limited in the present invention.
The current position information of the UE includes tracking area information (TAI) corresponding to the current position area of the UE, serving base station information corresponding to the current position area of the UE, and the like. The corresponding TAI used when the UE moves to the current position region is the UE's target TAI. The corresponding serving base station information used when the UE moves to the current location area is the UE's target base station information. The target base station information can be a target base station identification information (Identity, ID), a target cell identifier (Cell Identity, CI), or the like. It should be understood that the current location region of the UE is also referred to as the target location region of the UE, i.e., the location region of the UE after the UE has moved out of the service range of the source serving base station. Similarly, the current position information of the UE is also called the target position information of the UE.
The UE movement process consists of the procedures performed in the above three application scenarios, specifically, the service switching procedure in the application scenario (1), the position update procedure in the application scenario (2), and the service in the application scenario (3). Please understand that it includes the request procedure.
It should be understood that the UE's target base station is the base station that provides access services to the UE after it has moved to the current location area.
The data transfer tunnel creates a user plane bearer context between the source U-GW serving the UE and the transfer U-GW, and a user plane bearer context between the transfer U-GW and the UE's target base station. Please understand that it is implemented by. The user plane bearer context contains the routing information needed to transfer the user plane data. Specifically, the user plane bearer context created on the source U-GW contains the routing information of the forwarding U-GW and the routing information of the source base station serving the UE, and is created on the forwarding U-GW. The user plane bearer context contains the routing information of the source U-GW and the routing information of the target base station, and the user plane bearer context created on the target base station contains the routing information of the forwarding U-GW. In addition, the routing information includes the address (usually the Internet Protocol (IP) address) and the tunnel end point information (usually the GPRS Tunneling). When Protocol (GTP) is used, the tunnel endpoint information may include the GTP tunnel endpoint identifier (TEID).
It should be understood that the transfer U-GW is at least one transfer U-GW selected by selection unit 1202. The tunnel establishment unit 1203 serves the UE for the UE, the data transfer tunnel between the source U-GW and the transfer U-GW, and the data transfer tunnel between the transfer U-GW and the target base station of the UE. To establish a source U-GW, at least one transfer U-GW, for the tunnel establishment unit 1203 to establish a data transfer tunnel between the two network elements from the source C-GW to the target base station. And to establish a communication path between the target base stations.
In this embodiment of the invention, the control plane gateway 1200 is a suitable transfer U-for the UE according to the current location information after the move to ensure service continuity in the move process of the UE and improve the user service experience. Determine the GW and establish a data transfer tunnel between the transfer U-GW and the source U-GW, and a data transfer tunnel between the transfer U-GW and the UE target base station.
In addition, as shown in FIG. 13, the control plane gateway may further include transmit unit 1204.
In some cases, in one embodiment, at least one forwarding U-GW is the first U-GW and the control plane gateway is the serving control plane gateway used after the UE has moved to the current location area. The control plane gateway is the same serving control plane gateway that was used before the UE moved to the current location region, and the mobility management network element is the serving mobility management network element that is used after the UE moves to the current location region. Is.
Receiving unit 1201 is further configured to receive the first request sent by the mobility management network element. The first request carries the routing information of the UE's target base station.
Specifically, the tunnel establishment unit 1203 transmits the second request to the first U-GW by using the transmission unit 1204, and the third U-GW to the source U-GW by using the transmission unit 1204. Is configured to send a request for. The second request is to establish a data transfer tunnel between the first U-GW and the target base station, and a data transfer tunnel between the first U-GW and the source U-GW. Used to request one U-GW. The second request carries the routing information of the target base station and the routing information of the source U-GW. The third request is used to request the source U-GW to establish a data transfer tunnel between the source U-GW and the first U-GW, and the third request is the first. It carries the routing information of U-GW.
In this embodiment, it is understood that the control plane gateway 1200 is the same serving C-GW used before the UE moved to the current position area, i.e., the serving C-GW remains unchanged in the UE moving process. I want to be. This embodiment is applicable to scenarios where the serving mobility management network element changes in the UE's mobility process, or where the serving mobility management network element does not change in the UE's mobility process, i.e. the mobility management network element is the UE's. It should be understood that it may be the same as or different from the serving mobility management network element used before moving to the current location area.
Naturally, the control plane gateway 1200 further receives the second response sent by the first U-GW according to the second request and the third response sent by the source U-GW according to the third request. Please understand that. The second response is that the first U-GW transfers data between the first U-GW and the target base station, and between the first U-GW and the source U-GW. It is used to confirm that the tunnel has been allowed to be established. In some cases, the second response can carry the routing information of the first U-GW, such as IP address and TEID information, and the third response is that the source U-GW is with the source U-GW. It is used to confirm that the data transfer tunnel to and from the first U-GW has been allowed to be established. After receiving the second and third responses, the control plane gateway 1200 can send the first response of the first request to the mobility management network element.
The first, second, or third request in this embodiment uses an existing message, such as a Create Indirect Data Forwarding Tunnel Request, or a newly defined message. Please note that it may be sent by. This is not limited in the present invention. In addition, the first, second, or third response in this embodiment may be an existing message, such as a Create Indirect Data Forwarding Tunnel Response, or a newly defined message. May be sent by use. This is not limited in the present invention.
In some cases, in another embodiment, at least one forwarding U-GW includes a first U-GW and a second U-GW, and the control plane gateway is used after the UE has moved to the current location area. Is a serving control plane gateway, the control plane gateway is the same serving control plane gateway that was used before the UE moved to the current location region, and the mobility management network element is after the UE moves to the current location region. The serving mobility management network element used, which is the same as or different from the serving mobility management network element used before the UE moved to the current location area.
Receiving unit 1201 is further configured to receive the first request sent by the mobility management network element. The first request carries the routing information of the UE's target base station.
Specifically, the tunnel establishment unit 1203 transmits the second request to the second U-GW by using the transmission unit 1204, and the transmission unit 1204 is used to send the second request to the third U-GW. By sending a third request and using transmission unit 1204, it is configured to send a fourth request to the source U-GW. The second request is to establish a data transfer tunnel between the second U-GW and the target base station, and a data transfer tunnel between the second U-GW and the third U-GW. , Used to make a request to the second U-GW, the second request carries the routing information of the target base station and the routing information of the third U-GW, and the third request is the third. To the third U-GW to establish a data transfer tunnel between the U-GW and the second U-GW, and a data transfer tunnel between the third U-GW and the source U-GW. Used to make a request, the third request carries the routing information of the second U-GW and the routing information of the source U-GW, and the fourth request carries the routing information of the source U-GW and the third U-. Used to request the source U-GW to establish a data transfer tunnel to and from the GW, the fourth request carries the routing information of the third U-GW.
In this embodiment, it is understood that the C-GW is the same as the serving C-GW used before the UE moved to the current position region, i.e., the serving C-GW does not change in the UE moving process. I want to. This embodiment is applicable to scenarios where the serving mobility management network element changes in the UE's mobility process, or where the serving mobility management network element does not change in the UE's mobility process, i.e. the mobility management network element is the UE's. It should be understood that it may be the same as or different from the serving mobility management network element used before moving to the current location area.
Similarly, the control plane gateway 1200 has a second response sent by the second U-GW according to the second request, a third response sent by the third U-GW according to the third request, and Further receive the fourth response sent by the source U-GW in accordance with the fourth request. The second response is that the second U-GW is a data transfer tunnel between the second U-GW and the target base station, and between the second U-GW and the third U-GW. Used to acknowledge that you have allowed the establishment of a data transfer tunnel. In some cases, the second response can carry the routing information of the second U-GW, such as IP address and TEID information. The third response is that the third U-GW is a data transfer tunnel between the third U-GW and the second U-GW, and between the third U-GW and the source U-GW. Used to acknowledge that you have allowed the establishment of a data transfer tunnel. In some cases, the third response can carry the routing information of the third U-GW, such as IP address and TEID information. The fourth response is used to confirm that the source U-GW has allowed the establishment of a data transfer tunnel between the source U-GW and the third U-GW. After receiving the second response, the third response, and the fourth response, the control plane gateway 1200 can send the first response of the first request to the mobility management network element.
The first, second, third, or fourth request in this embodiment is an existing message, such as a Create Indirect Data Forwarding Tunnel Request, or is newly defined. Please note that it may be sent by using a tunnel. This is not limited in the present invention. In addition, the first, second, third, or fourth response in this embodiment is an existing message, such as a Create Indirect Data Forwarding Tunnel Response, or a new one. May be sent by using a defined message. This is not limited in the present invention.
In some cases, in yet another embodiment, at least one forwarding U-GW is the first U-GW and the control plane gateway is the serving control plane gateway used after the UE has moved to the current location area. Yes, the control plane gateway is different from the serving control plane gateway that was used before the UE moved to the current location region, and the mobility management network element is the serving mobility management network that is used after the UE moves to the current location region. An element, the mobility management network element is the same as or different from the serving mobility management network element used before the UE moved to the current location area.
The receiving unit 1201 is further configured to receive the routing information of the UE source U-GW.
Receiving unit 1201 is further configured to receive the first request sent by the mobility management network element. The first request carries the routing information of the UE's target base station.
The tunnel establishment unit 1203 is specifically configured to transmit a second request to the first U-GW by using the transmission unit 1204. The second request is to establish a data transfer tunnel between the first U-GW and the target base station, and a data transfer tunnel between the first U-GW and the source U-GW. Used to make a request to one U-GW, the second request carries the routing information of the target base station and the routing information of the source U-GW.
It should be understood that in this embodiment the C-GW is different from the serving C-GW used before the UE moved to the current position region, i.e., the serving C-GW changes in the UE moving process. This embodiment is applicable to scenarios where the serving mobility management network element changes in the UE's mobility process, or where the serving mobility management network element does not change in the UE's mobility process, i.e. the mobility management network element is the UE's. It should be understood that it may be the same as or different from the serving mobility management network element used before moving to the current location area.
Similarly, the control plane gateway 1200 further receives a second response sent by the first U-GW according to the second request and a third response sent by the source U-GW according to the third request. To do. The second response is that the first U-GW transfers data between the first U-GW and the target base station, and between the first U-GW and the source U-GW. It is used to confirm that the tunnel has been allowed to be established. In some cases, the second response can carry the routing information of the first U-GW, such as IP address and TEID information, and the third response is that the source U-GW is with the source U-GW. It is used to confirm that the data transfer tunnel to and from the first U-GW has been allowed to be established. After receiving the second and third responses, the control plane gateway 1200 can send the first response of the first request to the mobility management network element.
Naturally, the serving C-GW of the UE in this embodiment changes in the moving process of the UE, so the C-GW is the target C-GW, that is, the serving C-GW used after the UE has moved to the current position region. Please understand that there is. In addition, the target C-GW sends a data transfer tunnel establishment request to the source U-GW and the source U-GW through the mobility management network element to send the routing information of the first U-GW. It should be further shown to C-GW. The source C-GW is the serving C-GW used before the UE moved to the current position area, and the source U-GW is the serving U-GW used before the UE moved to the current position area. is there.
When the first or second request in this embodiment is sent by using an existing message, such as a Create Indirect Data Forwarding Tunnel Request, or a newly defined message. Please note that there is. This is not limited in the present invention. In addition, the first or second response in this embodiment is sent by using an existing message, such as a Create Indirect Data Forwarding Tunnel Response, or a newly defined message. May occur. This is not limited in the present invention.
In some cases, in yet another embodiment, at least one forwarding U-GW includes a first U-GW and a second U-GW, and the control plane gateway is used after the UE has moved to the current location area. Is a serving control plane gateway that is served, and unlike the serving control plane gateway that was used before the UE moved to the current location region, the mobility management network element is after the UE moves to the current location region. The serving mobility management network element used, which is the same as or different from the serving mobility management network element used before the UE moved to the current location area.
The receiving unit 1201 is further configured to receive the routing information of the UE source U-GW.
Receiving unit 1201 is further configured to receive the first request sent by the mobility management network element. The first request carries the routing information of the UE's target base station.
Specifically, the tunnel establishment unit 1203 transmits the second request to the second U-GW by using the transmission unit 1204, and the transmission unit 1204 is used to send the second request to the third U-GW. It is configured to send a third request. The second request is to establish a data transfer tunnel between the second U-GW and the target base station, and a data transfer tunnel between the second U-GW and the third U-GW. , Used to request the second U-GW. The second request carries the routing information of the target base station and the routing information of the third U-GW. The third request is to establish a data transfer tunnel between the third U-GW and the second U-GW, and a data transfer tunnel between the third U-GW and the source U-GW. Used to request a third U-GW. The third request carries the routing information of the second U-GW and the routing information of the source U-GW.
It should be understood that in this embodiment the C-GW is different from the serving C-GW used before the UE moved to the current position region, i.e., the serving C-GW changes in the UE moving process. This embodiment is applicable to scenarios where the serving mobility management network element changes in the UE's mobility process, or where the serving mobility management network element does not change in the UE's mobility process, i.e. the mobility management network element is the UE's. It should be understood that it may be the same as or different from the serving mobility management network element used before moving to the current location area.
Similarly, the control plane gateway 1200 has a second response sent by the second U-GW according to the second request, a third response sent by the third U-GW according to the third request, and Further receive the fourth response sent by the source U-GW in accordance with the fourth request. The second response is that the second U-GW is a data transfer tunnel between the second U-GW and the target base station, and between the second U-GW and the third U-GW. Used to acknowledge that you have allowed the establishment of a data transfer tunnel. In some cases, the second response can carry the routing information of the second U-GW, such as IP address and TEID information. The third response is that the third U-GW is a data transfer tunnel between the third U-GW and the second U-GW, and between the third U-GW and the source U-GW. Used to acknowledge that you have allowed the establishment of a data transfer tunnel. In some cases, the third response can carry the routing information of the third U-GW, such as IP address and TEID information. The fourth response is used to confirm that the source U-GW has allowed the establishment of a data transfer tunnel between the source U-GW and the third U-GW. After receiving the second response, the third response, and the fourth response, the control plane gateway 1200 can send the first response of the first request to the mobility management network element.
Of course, the serving C-GW of the UE in this embodiment changes in the moving process of the UE, so the C-GW in this embodiment is the target C-GW, that is, the serving used after the UE has moved to the current position region. Please understand that it is C-GW. In addition, the target C-GW sends a data transfer tunnel establishment request to the source U-GW and the source U-GW through the mobility management network element to send the routing information of the third U-GW. It should be further shown to C-GW. The source C-GW is the serving C-GW used before the UE moved to the current position area, and the source U-GW is the serving U-GW used before the UE moved to the current position area. is there.
The first, second, or third request in this embodiment uses an existing message, such as a Create Indirect Data Forwarding Tunnel Request, or a newly defined message. Please note that it may be sent by. This is not limited in the present invention. In addition, the first, second, or third response in this embodiment may be an existing message, such as a Create Indirect Data Forwarding Tunnel Response, or a newly defined message. May be sent by use. This is not limited in the present invention. In some cases, in the four specific embodiments shown in FIG. 13, the tunnel establishment unit 1203 provides the mobility management network element when at least one forwarding U-GW is the first U-GW. It is further configured to send the routing information of the target U-GW to the target base station via.
In some cases, in the four specific embodiments shown in FIG. 13, the tunnel establishment unit 1203 provides the mobility management network element when at least one forwarding U-GW is the first U-GW. It is further configured to send the routing information of the first U-GW to the target base station via.
In some cases, in the four specific embodiments shown in FIG. 13, when at least one forwarding U-GW is a second U-GW and a third U-GW, the tunnel establishment unit 1203 Is further configured to send the routing information of the second U-GW to the target base station via the mobility management network element.
In some cases, in the four specific embodiments shown in FIG. 13, the tunnel establishment unit 1203 is further configured to send a session creation request to the target U-GW. The session creation request is used to create a bearer context for user plane data transmission on the target U-GW for the UE. Each created bearer context contains the routing information of the target U-GW, and the target U-GW is a serving U-GW corresponding to the current position region of the UE. It should be understood that the target U-GW is generally a serving U-GW that provides the UE with the optimal data transmission path in the current position region. In addition, the tunnel establishment unit 1203 is further configured to transmit the routing information of the target U-GW to the target base station via the mobility management network element.
In some cases, in the four specific embodiments shown in FIG. 13 described above, when at least one transfer U-GW is the first U-GW, the first U-GW is further of the UE. The serving U-GW selected by the control plane gateway for the UE according to the current location information. That is, the first U-GW is the target U-GW. In this case, the target D-GW can communicate directly with the source D-GW, that is, the target U-GW also acts as a forwarding U-GW. It should be understood that the forwarding U-GW selected by the C-GW is different from the target U-GW when the target U-GW cannot communicate directly with the source D-GW.
The control plane gateway 1200 can further implement the method shown in FIG. 2, the function of the C-GW in the embodiments shown in FIGS. 2 to 4, 7, and 8 as well as in FIG. 5 or FIG. Implement the function of the target C-GW in the embodiment shown in 6. Details will not be described again in this embodiment of the invention.
FIG. 14 is a schematic structural diagram of the mobility management network element 1400 according to an embodiment of the present invention. The mobility management network element 1400 may include a receive unit 1401, a select unit 1402, and a transmit unit 1403.
Receiving unit 1401 is configured to receive forwarding relocation requests sent by the source mobility management network element serving the UE.
The transfer relocation request carries the current position information of the UE.
The selection unit 1402 is configured to select the UE's target C-GW according to the UE's current position information.
The transmission unit 1403 is configured to transmit the current position information of the UE to the target C-GW, so that the target control plane gateway determines the transfer U-GW of the UE according to the current position information of the UE.
Transmission unit 1403 is further configured to send a data transfer tunnel establishment request to the target control plane gateway.
A data transfer tunnel establishment request is made for the UE between the data transfer tunnel between the transfer U-GW and the source U-GW serving the UE, and between the transfer U-GW and the target base station serving the UE. Used to request the target C-GW to establish a data transfer tunnel.
In this embodiment of the invention, after the UE moves out of the service range of the source mobility management network element, the mobility management network element 1400 ensures service continuity in the UE's movement process and improves the user service experience. , Determine the UE's target C-GW according to the UE's current location information, and use the target C-GW to transfer data between the source U-GW and the UE's target base station for the UE. Establish a tunnel.
In some cases, the target control plane gateway is different from the serving control plane gateway that was used before the UE moved to the current location area (ie, the serving C-GW changes during the UE's move process). Transmission unit 1403 is further configured to send change notification messages to the source mobility management network element. The change notification message is used to indicate that the UE's serving control plane gateway has changed to the target control plane gateway.
In addition, receive unit 1401 is further configured to receive acknowledgment messages sent by the source mobility management network element in accordance with change notification messages. The acknowledgment message carries the routing information of the UE source U-GW.
Mobility management network element 1400 can further implement the method of FIG. 9 and implement the functionality of the target MME in the embodiment shown in FIG. 5 or 6. Details will not be described again in this embodiment of the invention.
FIG. 15 is a schematic structural diagram of the control plane gateway 1500 according to the embodiment of the present invention. The control plane gateway 1500 now selects the receiver unit 1501 configured to receive the UE's current location sent by the mobility management network element and the target U-GW for the UE according to the UE's current location. Includes a configured selection unit 1502 and a transmission unit 1503 configured to send request messages to mobility management network elements.
The request message is used to request the mobility management network element to release the first bearer context and indicate to the UE that it will send a setup request for the second bearer context. The first bearer context is the UE bearer context established on the UE source U-GW, and the second bearer context is reestablished by the UE on the target U-GW according to the first bearer context. Beara context.
It should be understood that in this embodiment of the present invention, the position update notification message is used to notify the C-GW that the current position area of the UE has changed. When an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message, is reused for location update notification. Or a new message may be defined. This is not limited in the present invention.
In this embodiment of the invention, does the control plane gateway 1500 need to change the serving U-GW according to the current location information of the UE before the UE changes from idle mode to connection mode and transmits user plane data? Determine if, trigger the bearer context deactivation procedure, add a reactivation request instruction during the bearer context deactivation procedure, recreate the bearer resource on the target U-GW, and follow the user plane. Request the UE to start the bearer context reestablishment procedure immediately to ensure service continuity of data transmission and to ensure the user service experience.
In some cases, in one embodiment, the request message is a bearer removal request message, the bearer removal request message carries a reactivation request instruction, and the reactivation request instruction uses a mobility management network element. Used to indicate to the UE to initiate a setup request for the second bearer context after the first bearer context has been deleted.
It should be understood that both MME and UE record the first bearer context created by UE on the source U-GW. After receiving the bearer removal request message, the MME tells the UE to remove the first bearer context on the MME and remove the first bearer context on the UE. When the bearer delete request message carries the reactivation request instruction, the MME further sends the reactivation request instruction to the UE to follow the contents of the first bearer context after the first bearer context has been deleted. Indicate the UE to resend the setup request for the bearer context and request that a second bearer context be created. The second bearer context is a bearer context created on the target U-GW based on the first bearer context.
The control plane gateway 1500 can further implement the method of FIG. 10 and implement the functionality of the C-GW in the embodiment shown in FIG. Details will not be described again in this embodiment of the invention.
FIG. 16 is a schematic structural diagram of the control plane gateway 1600 according to the embodiment of the present invention. The control plane gateway 1600 may include a processor 1602, a memory 1603, a transmitter 1601, and a receiver 1604.
The receiver 1604, transmitter 1601, processor 1602, and memory 1603 are connected to each other by using bus 1606. Bus 1606 can be an ISA bus, a PCI bus, an EISA bus, and so on. Buses may be classified into address buses, data buses, control buses, and the like. For ease of explanation, in Figure 16, bus 1606 is shown by using only one double-headed arrow. However, it does not indicate that there is only one bus or only one type of bus. For certain applications, transmitter 1601 and receiver 1604 may be coupled to antenna 1605.
Memory 1603 is configured to store programs. Specifically, the program may include program code, which includes computer operation instructions. Memory 1603 may include read-only memory and random access memory to supply instructions and data to processor 1602. Memory 1603 may include high speed RAM memory and may further include non-volatile memory, eg, at least one magnetic disk memory.
Processor 1602 executes a program stored in memory 1603 and specifically receives the current location information of the UE transmitted by the mobility management network element by using receiver 1604: And by selecting at least one forwarding U-GW for the UE according to the UE's current location and by using the transmitter 1601, the source U-GW and forwarding U-GW serving the UE for the UE. Establishing a data transfer tunnel to and from the GW, and a data transfer tunnel between the transfer U-GW and the UE's target base station, where the data transfer tunnel is the UE's uplink in the UE's movement process. It is configured to perform the establishment and used to transmit user plane data and / or downlink user plane data.
For applicable scenarios in this embodiment of the invention, see Application Scenarios in the Embodiment Shown in FIG.
In application scenario (1), after receiving the user plane data switching request sent by the source base station, the mobility management network element can send a service switching notification to the serving C-GW of the UE. It should be understood that the mobility management network element can be an MME or another network element with MME mobility management capabilities. For certain applications, the mobility management network element uses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message. By doing so, the service switch notification can be sent, or the mobility management network element can send the service switch notification by using the newly created message. The specific message used to send the service switch notification is not limited in the present invention.
In application scenario (2), after receiving the location update request sent by the UE, or after successfully creating a wireless access bearer context for the UE, the mobility management network element sends a request message to the UE's serving C-GW. Can be sent. It should be understood that the mobility management network element can be an MME or another network element with MME mobility management capabilities. For certain applications, the mobility management network element uses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message. The request message can be sent by doing so, or the mobility management network element can send the request message by using the newly created message. The specific message used to send the request message is not limited in the present invention.
In application scenario (3), after receiving a service request sent by the UE, or after successfully creating a wireless access bearer context for the UE, the mobility management network element sends a request message to the UE's serving C-GW. Can be sent. It should be understood that the mobility management network element can be an MME or another network element with MME mobility management capabilities. For certain applications, the mobility management network element uses an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message. The request message can be sent by doing so, or the mobility management network element can send the request message by using the newly created message. The specific message used to send the request message is not limited in the present invention.
The current position information of the UE includes tracking area information (TAI) corresponding to the current position area of the UE, serving base station information corresponding to the current position area of the UE, and the like. The corresponding TAI used when the UE moves to the current position region is the UE's target TAI. The corresponding serving base station information used after the UE has moved to the current location area is the UE's target base station information. The target base station information can be a target base station identification information (Identity, ID), a target cell identifier (Cell Identity, CI), or the like. It should be understood that the current location region of the UE is also referred to as the target location region of the UE, i.e., the location region of the UE after the UE has moved out of the service range of the source serving base station. Similarly, the current position information of the UE is also called the target position information of the UE.
The UE movement process consists of the procedures performed in the above three application scenarios, specifically, the service switching procedure in the application scenario (1), the position update procedure in the application scenario (2), and the service in the application scenario (3). Please understand that it includes the request procedure.
It should be understood that the UE's target base station is the base station that provides access services to the UE after it has moved to the current location area.
The data transfer tunnel creates a user plane bearer context between the source U-GW serving the UE and the transfer U-GW, and a user plane bearer context between the transfer U-GW and the UE's target base station. Please understand that it is implemented by. The user plane bearer context includes the routing information required to transfer the user plane data, including the routing information of the source U-GW, the routing information of the forwarding U-GW, and the routing information of the target base station. Specifically, the routing information is the address (usually the Internet Protocol (IP) address) and the tunnel end point information (usually the tunnel end point information when GPRS Tunneling Protocol (GTP) is used). May contain a GTP tunnel endpoint identifier (TEID).
It should be understood that the forwarding U-GW is at least one forwarding U-GW selected by processor 1602. Processor 1602 establishes for the UE a data transfer tunnel between the source U-GW serving the UE and the transfer U-GW, and a data transfer tunnel between the transfer U-GW and the UE's target base station. All that is done is that the processor 1602 uses the source U-GW, at least one transfer U-GW, and the target base station to establish a data transfer tunnel between the two network elements from the source C-GW to the target base station. Is to establish a communication path between.
The aforementioned performed by the C-GW disclosed in any of the embodiments of FIGS. 2-4 of the present invention, or by the target C-GW disclosed in any of the embodiments of FIGS. 5 and 6. Method may be applied to processor 1602 or implemented by processor 1602. Processor 1602 may be an integrated circuit chip and has signal processing capabilities. In one implementation process, the steps of the method described above may be completed by hardware integrated logic circuits in processor 1602, or instructions in the form of software. The processor 1602 is a central processing unit (CPU for short) and a network processor (Network). It can be a general purpose processor, including a Processor (NP for short), or a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), another programmable logic device, an individual gate. Alternatively, it can be a transistor logic device, or an individual hardware component. Processor 1602 can implement or implement the methods, steps, and logical block diagrams disclosed in embodiments of the present invention. The general purpose processor can be a microprocessor, or the processor can be any conventional processor and the like. The steps of the method disclosed with reference to embodiments of the present invention may be performed and completed directly by using a hardware decoding processor, or a combination of hardware and software modules within the decoding processor. May be implemented and completed by. Software modules may be located within mature storage media in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in memory 1603. Processor 1602 reads the information in memory 1603 and combines it with the hardware of processor 1602 to complete the steps of the method described above.
In this embodiment of the invention, the control plane gateway 1600 ensures service continuity in the UE's roaming process and, in order to improve the user service experience, the appropriate forwarding U-for the UE according to the current location information after the roaming. Determine the GW and establish a data transfer tunnel between the transfer U-GW and the source U-GW, and a data transfer tunnel between the transfer U-GW and the UE target base station.
In some cases, in one embodiment, at least one forwarding U-GW is the first U-GW and the control plane gateway is the serving control plane gateway used after the UE has moved to the current location area. The control plane gateway is the same serving control plane gateway that was used before the UE moved to the current location area, and the mobility management network element is the serving mobility management network element that is used after the UE moves to the current location area. And the mobility management network element is the same as or different from the serving mobility management network element used before the UE moved to the current location area.
Processor 1602 is further configured to receive the first request sent by the mobility management network element by using receiver 1604. The first request carries the routing information of the UE's target base station.
By using transmitter 1601, for the UE, a data transfer tunnel between the source U-GW serving the UE and the transfer U-GW, and / or between the transfer U-GW and the UE's target base station. In the process of establishing a data transfer tunnel between, processor 1602 specifically sends a second request to the first U-GW by using transmitter 1601 and uses transmitter 1601. Is configured to send a third request to the source U-GW, the second request being the data transfer tunnel between the first U-GW and the target base station, and the first U-GW. Used to request the first U-GW to allow the establishment of a data transfer tunnel between and the source U-GW, the second request is the routing information of the target base station and the source U-GW. Carrying the GW's routing information, a third request is used to request the source U-GW to establish a data transfer tunnel between the source U-GW and the first U-GW. The third request carries the routing information of the first U-GW.
In this embodiment, it is understood that the control plane gateway 1600 is the same serving C-GW used before the UE moved to the current position region, i.e., the serving C-GW remains unchanged in the UE moving process. I want to be. This embodiment is applicable to scenarios where the serving mobility management network element changes in the UE's mobility process, or where the serving mobility management network element does not change in the UE's mobility process, i.e. the mobility management network element is the UE's. It should be understood that it may be the same as or different from the serving mobility management network element used before moving to the current location area.
Naturally, the control plane gateway 1600 further receives a second response sent by the first U-GW according to the second request and a third response sent by the source U-GW according to the third request. Please understand that. The second response is that the first U-GW transfers data between the first U-GW and the target base station, and between the first U-GW and the source U-GW. It is used to confirm that the tunnel has been allowed to be established. In some cases, the second response can carry the routing information of the first U-GW, such as IP address and TEID information, and the third response is that the source U-GW is with the source U-GW. It is used to confirm that the data transfer tunnel to and from the first U-GW has been allowed to be established. After receiving the second and third responses, the control plane gateway 1600 can send the first response of the first request to the mobility management network element.
The first, second, or third request in this embodiment uses an existing message, such as a Create Indirect Data Forwarding Tunnel Request, or a newly defined message. Please note that it may be sent by. This is not limited in the present invention. In addition, the first, second, or third response in this embodiment may be an existing message, such as a Create Indirect Data Forwarding Tunnel Response, or a newly defined message. May be sent by use. This is not limited in the present invention.
In some cases, in another embodiment, at least one forwarding U-GW includes a first U-GW and a second U-GW, and the control plane gateway is used after the UE has moved to the current location area. Is a serving control plane gateway, the control plane gateway is the same serving control plane gateway that was used before the UE moved to the current location region, and the mobility management network element is after the UE moves to the current location region. The serving mobility management network element used, which is the same as or different from the serving mobility management network element used before the UE moved to the current location area.
Processor 1602 is further configured to receive the first request sent by the mobility management network element by using receiver 1604. The first request carries the routing information of the UE's target base station.
By using the transmitter 1601, for the UE, a data transfer tunnel between the source U-GW serving the UE and the transfer U-GW, and between the transfer U-GW and the UE's target base station. In the process of establishing a data transfer tunnel, the processor 1602 specifically The transmitter 1601 is used to send the second request to the second U-GW, and the transmitter 1601 is used to send the third request to the third U-GW and the transmitter. By using 1601, it is configured to send a fourth request to the source U-GW, the second request being the data transfer tunnel between the second U-GW and the target base station, and the second. Used to request the second U-GW to establish a data transfer tunnel between the second U-GW and the third U-GW, the second request is the routing of the target base station. Carrying information and routing information for the third U-GW, the third request is with the data transfer tunnel between the third U-GW and the second U-GW, and with the third U-GW. Used to request a third U-GW to establish a data transfer tunnel to and from the source U-GW, the third request is the routing information for the second U-GW and the source U-GW. The fourth request is used to request the source U-GW to carry the routing information of the GW and establish a data transfer tunnel between the source U-GW and the third U-GW. The fourth request carries the routing information of the third U-GW.
In this embodiment, it is understood that the control plane gateway 1600 is the same serving C-GW used before the UE moved to the current position region, i.e., the serving C-GW remains unchanged in the UE moving process. I want to be. This embodiment is applicable to scenarios where the serving mobility management network element changes in the UE's mobility process, or where the serving mobility management network element does not change in the UE's mobility process, i.e. the mobility management network element is the UE's. It should be understood that it may be the same as or different from the serving mobility management network element used before moving to the current location area.
Similarly, the control plane gateway 1600 has a second response sent by the second U-GW according to the second request, a third response sent by the third U-GW according to the third request, and Further receive the fourth response sent by the source U-GW in accordance with the fourth request. The second response is that the second U-GW is a data transfer tunnel between the second U-GW and the target base station, and between the second U-GW and the third U-GW. Used to acknowledge that you have allowed the establishment of a data transfer tunnel. In some cases, the second response can carry the routing information of the second U-GW, such as IP address and TEID information. The third response is that the third U-GW is a data transfer tunnel between the third U-GW and the second U-GW, and between the third U-GW and the source U-GW. Used to acknowledge that you have allowed the establishment of a data transfer tunnel. In some cases, the third response can carry the routing information of the third U-GW, such as IP address and TEID information. The fourth response is used to confirm that the source U-GW has allowed the establishment of a data transfer tunnel between the source U-GW and the third U-GW. After receiving the second response, the third response, and the fourth response, the control plane gateway 1600 can send the first response of the first request to the mobility management network element.
The first, second, third, or fourth request in this embodiment is an existing message, such as a Create Indirect Data Forwarding Tunnel Request, or is newly defined. Please note that it may be sent by using a tunnel. This is not limited in the present invention. In addition, the first, second, third, or fourth response in this embodiment is an existing message, such as a Create Indirect Data Forwarding Tunnel Response, or a new one. May be sent by using a defined message. This is not limited in the present invention.
In some cases, in yet another embodiment, at least one forwarding U-GW is the first U-GW and the control plane gateway is the serving control plane gateway used after the UE has moved to the current location area. Yes, the control plane gateway is different from the serving control plane gateway that was used before the UE moved to the current location region, and the mobility management network element is the serving mobility management network that is used after the UE moves to the current location region. An element, the mobility management network element is the same as or different from the serving mobility management network element used before the UE moved to the current location area.
Processor 1602 is further configured to receive the routing information of the UE source U-GW by using receiver 1604.
Processor 1602 is further configured to receive the first request sent by the mobility management network element by using receiver 1604. The first request carries the routing information of the UE's target base station.
By using transmitter 1601, for the UE, a data transfer tunnel between the source U-GW serving the UE and the transfer U-GW, and between the transfer U-GW and the UE's target base station. In the process of establishing a data transfer tunnel, processor 1602 is specifically configured to send a second request to the first U-GW by using transmitter 1601 and the second request is , A first U-GW to establish a data transfer tunnel between the first U-GW and the target base station, and a data transfer tunnel between the first U-GW and the source U-GW. The second request carries the target base station's routing information and the source U-GW's routing information.
It should be understood that in this embodiment, the control plane gateway 1600 is different from the serving C-GW used before the UE moved to the current position region, i.e., the serving C-GW changes in the UE's moving process. .. This embodiment is applicable to scenarios where the serving mobility management network element changes in the UE's mobility process, or where the serving mobility management network element does not change in the UE's mobility process, i.e. the mobility management network element is the UE's. It should be understood that it may be the same as or different from the serving mobility management network element used before moving to the current location area.
Similarly, the control plane gateway 1600 further receives a second response sent by the first U-GW according to the second request and a third response sent by the source U-GW according to the third request. To do. The second response is that the first U-GW transfers data between the first U-GW and the target base station, and between the first U-GW and the source U-GW. It is used to confirm that the tunnel has been allowed to be established. In some cases, the second response can carry the routing information of the first U-GW, such as IP address and TEID information, and the third response is that the source U-GW is with the source U-GW. It is used to confirm that the data transfer tunnel to and from the first U-GW has been allowed to be established. After receiving the second and third responses, the control plane gateway 1600 can send the first response of the first request to the mobility management network element.
Naturally, the serving C-GW of the UE in this embodiment changes in the moving process of the UE, so the control plane gateway 1600 is the target C-GW, that is, the serving C-GW used after the UE has moved to the current position region. Please understand that. In addition, processor 1602 sends a data transfer tunnel establishment request to the source U-GW and sends the routing information of the first U-GW to the source U-GW through the mobility management network element. Should be further indicated to the GW. The source C-GW is the serving C-GW used before the UE moved to the current position area, and the source U-GW is the serving U-GW used before the UE moved to the current position area. is there.
When the first or second request in this embodiment is sent by using an existing message, such as a Create Indirect Data Forwarding Tunnel Request, or a newly defined message. Please note that there is. This is not limited in the present invention. In addition, the first or second response in this embodiment is sent by using an existing message, such as a Create Indirect Data Forwarding Tunnel Response, or a newly defined message. May occur. This is not limited in the present invention.
In some cases, in yet another embodiment, at least one forwarding U-GW includes a first U-GW and a second U-GW, and the control plane gateway is used after the UE has moved to the current location area. Is a serving control plane gateway that is served, and unlike the serving control plane gateway that was used before the UE moved to the current location region, the mobility management network element is after the UE moves to the current location region. The serving mobility management network element used, which is the same as or different from the serving mobility management network element used before the UE moved to the current location area.
Processor 1602 is further configured to receive the routing information of the UE source U-GW by using receiver 1604.
Processor 1602 is further configured to receive the first request sent by the mobility management network element by using receiver 1604. The first request carries the routing information of the UE's target base station.
By using transmitter 1601, for the UE, a data transfer tunnel between the source U-GW serving the UE and the transfer U-GW, and between the transfer U-GW and the UE's target base station. In the process of establishing a data transfer tunnel, processor 1602 specifically sends a second request to a second U-GW by using transmitter 1601 and by using transmitter 1601. It is configured to send a third request to a third U-GW, which is a data transfer tunnel between the second U-GW and the target base station, and a second U-GW. Used to request the second U-GW to establish a data transfer tunnel between the and the third U-GW, the second request is the routing information of the target base station and the third U-GW. Carrying the routing information of the U-GW, the third request is the data transfer tunnel between the third U-GW and the second U-GW, and the third U-GW and the source U-GW. Used to request a third U-GW to establish a data transfer tunnel between, the third request contains the routing information of the second U-GW and the routing information of the source U-GW. Transport.
It should be understood that in this embodiment, the control plane gateway 1600 is different from the serving C-GW used before the UE moved to the current position region, i.e., the serving C-GW changes in the UE's moving process. .. This embodiment is applicable to scenarios where the serving mobility management network element changes in the UE's mobility process, or where the serving mobility management network element does not change in the UE's mobility process, i.e. the mobility management network element is the UE's. It should be understood that it may be the same as or different from the serving mobility management network element used before moving to the current location area.
Similarly, the control plane gateway 1600 has a second response sent by the second U-GW according to the second request, a third response sent by the third U-GW according to the third request, and Further receive the fourth response sent by the source U-GW in accordance with the fourth request. The second response is that the second U-GW is a data transfer tunnel between the second U-GW and the target base station, and between the second U-GW and the third U-GW. Used to acknowledge that you have allowed the establishment of a data transfer tunnel. In some cases, the second response can carry the routing information of the second U-GW, such as IP address and TEID information. The third response is that the third U-GW is a data transfer tunnel between the third U-GW and the second U-GW, and between the third U-GW and the source U-GW. Used to acknowledge that you have allowed the establishment of a data transfer tunnel. In some cases, the third response can carry the routing information of the third U-GW, such as IP address and TEID information. The fourth response is used to confirm that the source U-GW has allowed the establishment of a data transfer tunnel between the source U-GW and the third U-GW. After receiving the second response, the third response, and the fourth response, the control plane gateway 1600 can send the first response of the first request to the mobility management network element.
Of course, the UE serving C-GW in this embodiment changes during the UE movement process, so the control plane gateway 1600 in this embodiment is used after the target C-GW, i.e., the UE has moved to the current location region. Please understand that it is a serving C-GW. In addition, processor 1602 sends a data transfer tunnel establishment request to the source U-GW and sends the routing information of the third U-GW to the source U-GW through the mobility management network element. Should be further indicated to the GW. The source C-GW is the serving C-GW used before the UE moved to the current position area, and the source U-GW is the serving U-GW used before the UE moved to the current position area. is there.
The first, second, or third request in this embodiment uses an existing message, such as a Create Indirect Data Forwarding Tunnel Request, or a newly defined message. Please note that it may be sent by. This is not limited in the present invention. In addition, the first, second, or third response in this embodiment may be an existing message, such as a Create Indirect Data Forwarding Tunnel Response, or a newly defined message. May be sent by use. This is not limited in the present invention.
In some cases, in the four specific embodiments described above in FIG. 16, when at least one forwarding U-GW is the first U-GW, the processor 1602 is mobile by using the transmitter 1601. It is further configured to send the routing information of the target U-GW to the target base station via the management network element.
In some cases, in the four specific embodiments described above in FIG. 16, when at least one forwarding U-GW is the first U-GW, the processor 1602 is the target base station via the mobility management network element. Is further configured to send the routing information of the first U-GW.
In some cases, in the four specific embodiments described above in FIG. 16, processor 1602 is a mobility management network when at least one forwarding U-GW is a second U-GW and a third U-GW. It is further configured to send the routing information of the second U-GW to the target base station via the element.
In some cases, in the four specific embodiments described above in FIG. 16, the processor 1602 is further configured to send a session creation request to the target U-GW by using the transmitter 1601 to create the session. The request is used to create bearer contexts for user plane data transmission on the target U-GW for the UE, and each created bearer context contains the routing information of the target U-GW and the target U- GW is a serving U-GW corresponding to the current position area of the UE. It should be understood that the target U-GW is generally a serving U-GW that provides the optimal data transmission path for the UE in the current location region. In addition, processor 1602 is further configured to send target U-GW routing information to the target base station via the mobility management network element.
In some cases, in the four specific embodiments described above in FIG. 16, when at least one transfer U-GW is the first U-GW, the first U-GW further provides the current location information of the UE. Serving U-GW selected by the control plane gateway for UE according to. That is, the first U-GW is the target U-GW. In this case, the target D-GW can communicate directly with the source D-GW, that is, the target U-GW also acts as a forwarding U-GW. It should be understood that the forwarding U-GW selected by the C-GW is different from the target U-GW when the target U-GW cannot communicate directly with the source D-GW.
The control plane gateway 1600 can further implement the method shown in FIG. 2, the function of the C-GW in the embodiments shown in FIGS. 2 to 4, 7, and 8, and FIG. 5 or The function of the target C-GW in the embodiment shown in FIG. 6 is implemented. Details will not be described again in this embodiment of the invention.
FIG. 17 is a schematic structural diagram of the mobility management network element 1700 according to an embodiment of the present invention. Mobility management network element 1700 may include processor 1702, memory 1703, transmitter 1701, and receiver 1704.
The receiver 1704, transmitter 1701, processor 1702, and memory 1703 are connected to each other by using bus 1706. Bus 1706 can be an ISA bus, a PCI bus, an EISA bus, and so on. Buses may be classified into address buses, data buses, control buses, and the like. For ease of explanation, in Figure 17, bus 1706 is shown by using only one double-headed arrow. However, it does not indicate that there is only one bus or only one type of bus. For certain applications, transmitter 1701 and receiver 1704 may be coupled to antenna 1705.
Memory 1703 is configured to store programs. Specifically, the program may include program code, which includes computer operation instructions. Memory 1703 may include read-only memory and random access memory to supply instructions and data to processor 1702. Memory 1703 may include high speed RAM memory and may further include non-volatile memory, for example at least one magnetic disk memory.
Processor 1702 executes a program stored in memory 1703, specifically: Transfer relocation request sent by a source mobility management network element that serves the UE by using receiver 1704: The transfer relocation request carries and receives the UE's current location information, selects the UE's target C-GW according to the UE's current location information, and uses transmitter 1701. By doing so, the current position information of the UE is transmitted to the C-GW, and as a result, the C-GW determines and transmits the transfer U-GW of the UE according to the current position information of the UE. By using transmitter 1701, a data transfer tunnel establishment request is sent to the target control plane gateway, where the data transfer tunnel establishment request serves the UE for the UE, the transfer U-GW and the source U. -The transmit used to request the target C-GW to establish a data transfer tunnel to and from the GW, and a data transfer tunnel between the transfer U-GW and the target base station serving the UE. It is configured to do and do.
The aforementioned method performed by the mobility management network element disclosed in the embodiment shown in FIG. 9 of the present invention or by the target MME disclosed in the embodiment shown in FIG. 5 or 6. May apply to processor 1702 or may be implemented by processor 1702. Processor 1702 may be an integrated circuit chip and has signal processing capabilities. In one implementation process, the steps of the method described above may be completed by hardware integrated logic circuits in processor 1702, or instructions in the form of software. The processor 1702 is a central processing unit (CPU for short) and a network processor (Network). It can be a general purpose processor, including a Processor (NP for short), or a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), another programmable logic device, an individual gate. Alternatively, it can be a transistor logic device, or an individual hardware component. Processor 1702 can implement or implement the methods, steps, and logical block diagrams disclosed in embodiments of the present invention. The general purpose processor can be a microprocessor, or the processor can be any conventional processor and the like. The steps of the method disclosed with reference to embodiments of the present invention may be performed and completed directly by using a hardware decoding processor, or a combination of hardware and software modules within the decoding processor. May be implemented and completed by. Software modules may be located within mature storage media in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in memory 1703. Processor 1702 reads the information in memory 1703 and combines it with the hardware of processor 1702 to complete the steps of the method described above.
In this embodiment of the invention, after the UE moves out of the service range of the source mobility management network element, the mobility management network element 1700 ensures service continuity in the UE's movement process and improves the user service experience. , Determine the UE's target C-GW according to the UE's current location information, and use the target C-GW to transfer data between the source U-GW and the UE's target base station for the UE. Establish a tunnel.
In some cases, the target control plane gateway is different from the serving control plane gateway that was used before the UE moved to the current location area (ie, the serving C-GW changes during the UE's move process). Processor 1702 is further configured to send change notification messages to the source mobility management network element by using transmitter 1701. The change notification message is used to indicate that the UE's serving control plane gateway has changed to the target control plane gateway.
In addition, processor 1702 is further configured to receive acknowledgment messages sent by the source mobility management network element in accordance with change notification messages by using receiver 1704. The acknowledgment message carries the routing information of the UE source U-GW.
The mobility management network element 1700 can further implement the method of FIG. 9 and implement the functionality of the target MME in the embodiment shown in FIG. 5 or 6. Details will not be described again in this embodiment of the invention.
FIG. 18 is a schematic structural diagram of the control plane gateway 1800 according to the embodiment of the present invention. The control plane gateway 1800 may include a processor 1802, a memory 1803, a transmitter 1801, and a receiver 1804.
The receiver 1804, transmitter 1801, processor 1802, and memory 1803 are connected to each other by using bus 1806. Bus 1806 can be an ISA bus, a PCI bus, an EISA bus, and the like. Buses may be classified into address buses, data buses, control buses, and the like. For ease of explanation, in Figure 18, bus 1806 is shown by using only one double-headed arrow. However, it does not indicate that there is only one bus or only one type of bus. For certain applications, transmitter 1801 and receiver 1804 may be coupled to antenna 1805.
Memory 1803 is configured to store programs. Specifically, the program may include program code, which includes computer operation instructions. Memory 1803 may include read-only memory and random access memory to supply instructions and data to processor 1802. Memory 1803 may include high speed RAM memory and may further include non-volatile memory, eg, at least one magnetic disk memory.
Processor 1802 executes a program stored in memory 1803 and specifically receives the current location information of the UE transmitted by the mobility management network element by using receiver 1804: And, by selecting the target U-GW for the UE according to the current location information of the UE, and by using the transmitter 1801, the request message is sent to the mobility management network element, and the request message is the first. Used to release the bearer context of 1 and request the mobility management network element to send a setup request for the second bearer context, with the first bearer context being the source U-GW of the UE. To perform sending, which is the bearer context of the UE established above, and the second bearer context is the bearer context reestablished by the UE on the target U-GW according to the first bearer context. It is composed.
It should be understood that in this embodiment of the present invention, the position update notification message is used to notify the C-GW that the current position area of the UE has changed. When an existing message, such as a Create Session Request message, a Modify Bearer Request message, or a Modify Access Bearers Request message, is reused for location update notification. Or a new message may be defined. This is not limited in the present invention.
The aforementioned method performed by C-GW disclosed in any of the embodiments of FIGS. 10 and 11 of the present invention may be applied to or implemented by processor 1802. .. Processor 1802 may be an integrated circuit chip and has signal processing capabilities. In one implementation process, the steps of the method described above may be completed by hardware integrated logic circuits in processor 1802, or instructions in the form of software. Processor 1802 is a central processing unit (CPU for short) and a network processor (Network). It can be a general purpose processor, including a Processor (NP for short), or a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), another programmable logic device, an individual gate. Alternatively, it can be a transistor logic device, or an individual hardware component. Processor 1802 can implement or implement the methods, steps, and logical block diagrams disclosed in embodiments of the present invention. The general purpose processor can be a microprocessor, or the processor can be any conventional processor and the like. The steps of the method disclosed with reference to embodiments of the present invention may be performed and completed directly by using a hardware decoding processor, or a combination of hardware and software modules within the decoding processor. May be implemented and completed by. Software modules may be located within mature storage media in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in memory 1803. Processor 1802 reads the information in memory 1803 and is combined with the hardware of processor 1802 to complete the steps of the method described above.
In this embodiment of the invention, does the control plane gateway 1800 need to change the serving U-GW according to the current location information of the UE before the UE changes from idle mode to connection mode and transmits user plane data? Determine if, trigger the bearer context deactivation procedure, add a reactivation request instruction during the bearer context deactivation procedure, recreate the bearer resource on the target U-GW, and follow the user plane. Request the UE to start the bearer context reestablishment procedure immediately to ensure service continuity of data transmission and to ensure the user service experience.
In some cases, in one embodiment, the request message is a bearer delete request message, the bearer delete request message carries the reactivation request instruction, and the reactivation request instruction is the first via the mobility management network element. Used to indicate to the UE to initiate a setup request for a second bearer context after the bearer context has been removed.
It should be understood that both MME and UE record the first bearer context created by UE on the source U-GW. After receiving the bearer removal request message, the MME tells the UE to remove the first bearer context on the MME and remove the first bearer context on the UE. When the bearer delete request message carries the reactivation request instruction, the MME further sends the reactivation request instruction to the UE to follow the contents of the first bearer context after the first bearer context has been deleted. Indicate the UE to resend the setup request for the bearer context and request that a second bearer context be created. The second bearer context is a bearer context created on the target U-GW based on the first bearer context.
The control plane gateway 1800 can further implement the method of FIG. 10 and implement the functionality of the C-GW in the embodiment shown in FIG. Details will not be described again in this embodiment of the invention.
It should be understood that the sequence numbers of the aforementioned processes do not imply execution sequences in various embodiments of the present invention. The process execution sequence should be determined according to the function and internal logic of the process and should not be construed as any limitation on the implementation process of the embodiments of the present invention.
Those skilled in the art will appreciate that the units and algorithm steps may be implemented by electronic hardware, or a combination of computer software and electronic hardware, in combination with the examples described in the embodiments disclosed herein. Will be recognized. Whether the function is performed by hardware or software depends on the specific use and design constraints of the technical solution. One of ordinary skill in the art can use various methods to implement the features described for a particular application, but it should not be considered that the implementation form is beyond the scope of the present invention.
For convenience and concise description, the detailed operating processes of the systems, devices, and units described above can be referenced to the corresponding processes within the method embodiments described above, the details of which are described herein. It will be clearly understood by those skilled in the art that it will not be listed again.
It should be understood that in some embodiments provided in this application, the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described are only examples. For example, the unit division is only a logical functional division, and in the actual implementation form, it may be another division. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented, plus displayed or described. Mutual coupling or direct coupling or communication connection may be implemented by using several interfaces. Indirect coupling or communication connections between devices or units may be implemented in electrical, mechanical, or other forms.
Units listed as separate parts may or may not be physically separated, and the part labeled as a unit may or may not be a physical unit, in one place. It may be located in, or it may be distributed over multiple network units. Some or all of the units may be selected according to the actual needs to achieve the objectives of the solution of the embodiment.
In addition, the functional units in the embodiments of the present invention may be integrated into one processing unit, or each of the units may be physically independent, or two or more units may be one unit. Will be integrated into.
When a feature is implemented in the form of a software functional unit and sold or used as an independent product, the feature may be stored on a computer-readable storage medium. Based on such understanding, the technical solutions of the invention are essentially or parts that contribute to the prior art, or some of the technical solutions are implemented in the form of software products. There is. The software product is stored on a storage medium and instructs the computer device (which may be a personal computer, server, or network device) to perform all or part of the steps of the method described in the embodiments of the present invention. Includes some instructions to do. The above-mentioned storage medium stores program code such as a USB flash drive, a removable hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disk. Includes any medium that can be.
The above description is merely a specific implementation of the present invention and does not limit the scope of protection of the present invention. Any modifications or substitutions readily conceived by those skilled in the art within the technical scope disclosed in the present invention should fall within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should follow the scope of protection of the claims.
1200 Control plane gateway 1201 Receive unit 1202 Select unit 1203 Tunnel establishment unit 1204 Transmit unit 1400 Mobility management network element 1401 Receive unit 1402 Select unit 1403 Send unit 1500 Control plane gateway 1501 Receive unit 1502 Select unit 1503 Transmit unit 1600 Control plane gateway 1601 Transmit Machine 1602 Processor 1603 Memory 1604 Receiver 1605 Antenna 1606 Bus 1700 Mobility Management Network Element 1701 Transmitter 1702 Processor 1703 Memory 1704 Receiver 1705 Antenna 1706 Bus 1800 Control Plane Gateway 1801 Transmitter 1802 Processor 1803 Memory 1804 Receiver 1805 Antenna 1806 Bus
18 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| US20150117408A1 | Cites | United States of America |
26 members in 8 offices
Members26
| Document | Office | Kind | |
|---|---|---|---|
| WO2017054178A1 | World Intellectual Property Organization (WIPO) | A1 | |
| CN107079507A | China | A | |
| KR20180061265A | Republic of Korea | A | |
| EP3346795A1 | European Patent Office (EPO) | A1 | |
| EP3346795A4 | European Patent Office (EPO) | A4 | |
| US2018220479A1 | United States of America | A1 | |
| BR112018006580A2 | Brazil | A2 | |
| JP2018530253A | Japan | A | |
| RU2686596C1 | Russian Federation | C1 | |
| EP3346795B1 | European Patent Office (EPO) | B1 | |
| KR102018635B1 | Republic of Korea | B1 | |
| US2019289652A1 | United States of America | A1 | |
| US10595350B2 | United States of America | B2 | |
| EP3624545A1 | European Patent Office (EPO) | A1 | |
| CN107079507B | China | B | |
| US10638527B2 | United States of America | B2 | |
| US2020137812A1 | United States of America | A1 | |
| US2020137813A1 | United States of America | A1 | |
| JP6699847B2This record | Japan | B2 | |
| US10701744B2 | United States of America | B2 | |
| CN111510986A | China | A | |
| US10827543B2 | United States of America | B2 | |
| US2021029760A1 | United States of America | A1 | |
| EP3624545B1 | European Patent Office (EPO) | B1 | |
| US11432351B2 | United States of America | B2 | |
| CN111510986B | China | B |
16 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| 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 | |
| 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 | |
| Transfer to examiner for re-examination before appeal (zenchi)AppealJAPANESE INTERMEDIATE CODE: A911A911 | A911 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Decision of refusalJAPANESE INTERMEDIATE CODE: A02A02 | A02 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 6699847
- Application
- 2018516449
Titles2
- Japanese
- サービス継続性保証方法、制御プレーンゲートウェイ、およびモビリティ管理ネットワーク要素
- English
- Service continuity assurance methods, control plane gateways, and mobility management network elements
Classification
- CPC, 10
- H04W76/10
- H04W36/00
- H04W76/12
- H04W88/00
- H04W88/16
- H04W36/02
- H04W36/0011
- H04W8/08
- H04W88/02
- H04W88/08
- IPC, 2
- H04W36 12
- H04W76 12
