1. Idle-State Data Buffering and Paging Framework June 04, 2007 Source companies 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. Source companies are 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 source companies 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 source companies specifically reserve the right to amend or modify the material contained herein and to any intellectual property of source companies other than provided in the copyright statement above. Rajesh Bhalla rabhalla@zteusa.com Yonggang Fang yfang@zteusa.com Zhou Na zhou.na@zte.com.cn Source ：

2. ZTE USA Inc. 2  An idle-AT needs to be Paged as data arrives at the network  Three entities related to Idle-State Data Buffering and Paging  AGW Receives data from the IP Network  DAP The AN that maintains PMIP tunnel with the AGW  SRNC Maintains paging area database and configuration of the idle AT (e.g., registration boundary and paging cycle etc.)  Issues to consider:  Which entity to buffer the data while Paging is in progress  Paging procedures to locate the AT most effectively  No solution is ‘right’ or ‘wrong’  Agree on a solution that meets the stated Objectives Problem Statement

3. ZTE USA Inc. 3  The solution not to violate the UMB Architectural Framework  SRNC is the Session Control entity  AN/DAP is the Bearer Plane entity  Optimal utilization of backhaul resources  Flexibility in the placement of the data buffer at the DAP or the AGW  Solution to be based on the functional entities only  Not to be based on ‘implementation options’  To support interoperable implementations Objectives

4. ZTE USA Inc. 4 UMB Architectural Framework

5. ZTE USA Inc. 5  UMB air-interface supports SmallRegistrationRadius and LargeRegistrationRadius attributes that provide triggers for the Registration of the AT  SmallRegistrationRadius:   Typically configured to be similar to the coverage area of the DAP  The AT would be Paged within coverage area of the DAP  LargeRegistrationRadius:  Area beyond the coverage area of the DAP  Wider area Paging needed  The above stated attributes leveraged to develop Idle-State Buffering and Paging Framework Air Interface Support

6. ZTE USA Inc. 6  Please use slideshow mode

7. ZTE USA Inc. 7  A stationary and low mobility scenario  The AT needs to be Paged within the coverage area of the DAP  Idle-status of the AT need not be communicated to the AGW  AGW forwards data arriving from the network to the DAP  The DAP and SRNC Page the AT and deliver the data to the AT via the new serving AN. SRNC sets Paging in Progress flag  DAP may be relocated to the new serving AN (beyond the scope of the current problem statement) AT within SmallRegistrationRadius

8. ZTE USA Inc. 8 AT within SmallRegistrationRadius (an agreed upon approach !!) AT AN1 Access Gateway S-RNC AN2 AN3 Notification (idle) Page Small Registration Radius Data Attachment Point Data Paging Response Paging Request

9. ZTE USA Inc. 9  The AT moves beyond the coverage area of the DAP  Idle-state status of the AT communicated to the AGW  Policy based determination of data buffer location (at the AGW or the DAP)  Configuration based data buffer location  Paging priority/Application based buffer location  Data buffer policy configurable/negotiable per AT  Policy configurations/negotiations beyond the scope of this contribution  The following graphics illustrate:  Data buffering at the AGW with Paging triggered by the AGW  Data buffering at the DAP with Paging triggered by the DAP AT moves to LargeRegistrationRadius

10. ZTE USA Inc. 10  The AT communicates its idle status to the SRNC  Idle-AT Registers with the SRNC as it moves out of the SmallRegistrationRadius  Policy based decision to buffer the data at the AGW as the AT is being Paged  SRNC notifies AGW of idle-status of the AT  Data for the idle-AT arrives at the AGW  AGW notifies SRNC of arrival of the data for the idle-AT  SRNC initiates Paging of the AT  AT responds at another AN, beyond the (current) DAP  New DAP selected (probably the new serving AN)  AGW PMIP tunnel moved to the new DAP  DAP notifies AGW to resume data transfer  Data delivered to the AT via the new DAP (and new serving AN) AT moves to LargeRegistrationRadius Data Buffering at the AGW with Paging Triggered by the AGW

11. ZTE USA Inc. 11 AT moves to LargeRegistrationRadius (Data Buffering at the AGW) AT AN1 Access Gateway S-RNC AN2 AN3 Notification (idle) Small Registration Radius Register Notification (AT moved) Large Registration Radius Notify (Data) Paging Request Page Data Attachment Point Data Policy Decision : AGW to buffer data when ‘AT Moved Notification’ Sent to AGW Xon

12. ZTE USA Inc. 12  The AT communicates its idle status to the SRNC  Idle-AT Registers with the SRNC as it moves out of the SmallRegistrationRadius  Policy based decision NOT to buffer the data at the AGW as the AT is being Paged  SRNC does not notify the AGW of idle-status of the AT  Data for the idle-AT arrives at the AGW  AGW forwards the data to the DAP  DAP initiates Paging of the AT by communicating with the SRNC  AT responds at another AN, beyond the (current) DAP  New DAP selected (probably the new serving AN)  Buffered data at the old DAP forwarded to the new DAP  AGW PMIP tunnel moved to the new DAP  DAP notifies AGW to resume data transfer  Newly arriving data delivered to the AT via the new DAP (and new serving AN) AT moves to LargeRegistrationRadius Data Buffering at the DAP with Paging Triggered by the DAP

13. ZTE USA Inc. 13 AT moves to LargeRegistrationRadius Data Buffering at the DAP with Paging Triggered by the DAP AT AN1 Access Gateway S-RNC AN2 AN3 Small Registration Radius Register Large Registration Radius Paging Request Page Data Attachment Point Data Paging Request Notification (idle) Xon Policy Decision : AGW NOT to buffer data, ‘AT Moved Notification’ not sent to the AGW

14. ZTE USA Inc. 14  The proposal provides a flexible framework for Idle-state Data Buffering and Paging for UMB Networks  Provides for policy based determination of data buffer location (at the AGW or the DAP)  Configuration based data buffer location  Paging priority/Application based buffer location  Data buffer policy configurable/negotiable per AT  Policy configurations/negotiations would be add-ons to the baseline framework presented herein  The proposed framework is not dependent on any ‘implementation options’  The proposed framework supports Interoperable implementations  Recommendations:  Discuss and adopt Summary and Recommendations