1. TSG-A WG3 Title: Possible solution for HRPD-LTE SON Source: Yuanfang Yu, Xiaowu Zhao, Ting Lu, Yonggang Fang Abstract: This contribution provides a possible solution for HRPD-LTE SON which requires both 3GPP and 3GPP2 support. Data: February 6, 2012 Recommendation: FYI. © 2012 ZTE ZTE grants 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. ZTE 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 ZTE 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 Alcatel-Lucent. ZTE specifically reserves the right to amend or modify the material contained herein and to any intellectual property of ZTE other than provided in the copyright statement above.

2. S101 definition in 3GPP Spec – Message types for S101 Message Type value (Decimal) MessageReference 0Reserved3GPP TS 29.274 [6] 1Echo Request 3GPP TS 29.274 [6] 2Echo Response 3GPP TS 29.274 [6] 3Version Not Supported Indication 3GPP TS 29.274 [6] 4Direct Transfer Request message7.3.2 5Direct Transfer Response message7.3.3 6Notification Request message7.3.4 7Notification Response message7.3.5 8-24For future S101 interface use 25-31Reserved for Sv interface3GPP TS 29.280 [14] 32-255Reserved for GTPv2-C spec3GPP TS 29.274 [6] In TS29.276, S101 interface includes reserved message types for future use which might be used for RIM messages between eHRPD and LTE to support SON features.

3. Proposed Point 1: Enhanced S101 interface Message Type 8 ： RAN Information Transfer Request Message – Direction: MME eAN – Information Elements RIM Information RIM Routing Address Message Type 9 ： RAN Information Transfer Response Message – Direction: : MME eAN – Information Elements Cause

4. Proposed Point 2: RIM Routing Address Adding new HRPD Routing Address in S1AP (TS36.413) IE/Group NamePresenceRangeIE type and reference Semantics descriptionCriticalityAssigned Criticality CHOICE RIM Routing Address >GERAN-Cell-ID- >>LAIM.1- >>RACM9.2.3.2- >>CIMOCTET STRING (2) - >Target RNC-ID- >>LAIM9.2.3.1- >>RACO9.2.3.2- >>RNC-IDMINTEGER (0..4095) - >>Extended RNC-IDO9.2.1.14- >HRPD-Cell-ID >>HRPD SectorIDM 参考 TS29.276

5. Proposed Point 3: RIM Routing Information Add new HRPD type for RIM Routing information in TS48.018 – RIM Routing Address discriminator 0000A Cell Identifier is used to identify a GERAN cell. 0001An RNC identifier is used to identify a UTRAN RNC. 0010An eNB identifier is used to identify an E-UTRAN eNodeB or HeNB 0011 A HRPD AN identifier is used to identify a HRPD AN 87654321 octet 1IEI octet 2, 2aLength Indicator octet 3SpareRIM Routing Address discriminator octet 4-nRIM Routing Address

6. Proposed Point 4: RAT discriminator Add new HRPD type for RAT discriminator in TS48.018 – RAT discriminator 0000The reporting RAT is GERAN. 0001The reporting RAT is UTRAN. 0010The reporting RAT is E-UTRAN. 0011 The reporting RAT is HRPD.