Presentation on theme: "HUAWEI TECHNOLOGIES CO., LTD. www.huawei.com Huawei Technologies Co., Ltd. grant a free, irrevocable license to 3GPP2 and its Organizational Partners to."— Presentation transcript:
HUAWEI TECHNOLOGIES CO., LTD. www.huawei.com Huawei Technologies Co., Ltd. grant a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner's standards publication. Huawei Technologies Co., Ltd. is also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution. This document has been prepared by Huawei Technologies Co., Ltd., to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on Huawei Technologies Co., Ltd.. Huawei Technologies Co., Ltd. specifically reserve the right to amend or modify the material contained herein and to any intellectual property of Huawei Technologies Co., Ltd. other than provided in the copyright statement above. Lizhiminglizhiming@email@example.com A30-20110523-xxx Comments to ALU’s A13 registration request proposal
Security level: Open HUAWEI TECHNOLOGIES Co., Ltd. Page 2 A13 IP address issue Problem statement Per A30-20110523-009r0, “the macrocell cannot know or find out the IP address of the Femto either for A13 paging or Femto-to-Macro session transfer without changes to standards.” F1 F3 F2 FGWAN Network model
Security level: Open HUAWEI TECHNOLOGIES Co., Ltd. A13 IP address issue Analysis: 1. When AT performs dormant HO from femto to AN, macro AN is configured with FGW’s A13 IP addr and CC, FGW also knows AT’s latest FAP identity,A13 IP addr and CC, so FGW can retrieve HRPD session from FAP for macro AN. 2. When macro AN performs A13 paging, macro AN is configured with FGW’s A13 IP addr and CC, FGW also knows AT’s latest FAP identity,A13 IP addr and CC if AT has HRPD session with FAP before. If AT doesn’t have any HRPD session with any FAP under this FGW, then FGW rejects A13 paging because AT never appear under this FGW. Conclusion: the macro AN can retrieve HRPD session without standard change. 3 Page 3 Huawei Technologies - Proprietary
Security level: Open HUAWEI TECHNOLOGIES Co., Ltd. A13 Session transfer signaling load with SCC issue Page 4 Problem statement Per A30-20110725-xxxr0, “Hence the AN would need to page across more subnets than the current one – including the neighboring subnets configured in the secondary color code group” F1 F3 F2 FGW (SCC=AN) AN (SCC=FGW) Network model F1/F2/F3’s SCC=AN AT registers to F1 before idle handover to AN
Security level: Open HUAWEI TECHNOLOGIES Co., Ltd. A13 Session transfer signaling load with SCC issue Page 5 Analysis: 1. Since AN’s SCC is set to FGW and configured with FGW’s A13 IP addr, so when inter-AN paging procedure is triggered by AN, FGW receives A13 Paging Request msg. FGW will page AT through F1 since the AT registers to F1 before. The FGW also can enlarge paging area including F1 neighbor FAPs. 2. F1/F2/F3’s SCC is set to AN and configured with AN’s A13 IP addr, so when F1 triggers inter-AN paging procedure, FGW can forward A13 Paging msg to AN. Conclusion: With SCC method, paging load is not a issue.
Security level: Open HUAWEI TECHNOLOGIES Co., Ltd. Other comments Compatible issue Macro AN’s impact In figure 3, macro AN need to distinguish the regular UATIRequest msg from the proposed solution. In figure 6,macro AN need to perform additional check for AT HW-ID. Femtocell’s impact femtocell need to check each CC in UATIRequest msg and msg type, then acts differently per CC type(firgure 2 for mCC vs figure 4 for mCC vs figure 5 for femto CC). Signaling load issue Extra signaling load between femtocell and AN due to additional A13 registration procedure. 6 Page 6