1. TSG-A WG3 Title: iRAT SON in 3GPP Source: Yuanfang Yu, Xiaowu Zhao, Ting Lu, Yonggang Fang Abstract: This contribution provides some information about the solution for SON between LTE and UTRAN/GEREN defined in 3GPP. Date: 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. SON between E-UTRAN and UTRAN/GERAN 3GPP has used RIM(RAN Information Message) messages to support the SON features (e.g. MLB, MRO) between E-UTRAN and UTRAN/GEREN. The related standardized work for iRAT MLB between E-UTRAN and UTRAN/GEREN has been completed in 3GPP R10 which influences TS36.413/ TS36.423/ TS48.018, the related standardized work for iRAT MRO between E-UTRAN and UTRAN/GEREN will be completed in 3GPP R11. SON between E- UTRAN and eHRPD which has been included in 3GPP2 SON WI-00299 cannot be supported by 3GPP specifications now.

3. RIM in 3GPP -0 The information from TS 36.413 (S1AP) eNB DIRECT INFORMATION TRANSFER – 9.1.14eNB DIRECT INFORMATION TRANSFER (Direction: eNB  MME) This message is sent by the eNB in order to transfer specific information. MME DIRECT INFORMATION TRANSFER – 9.1.15MME DIRECT INFORMATION TRANSFER (Direction: MME  eNB) IE/Group NamePresenceRangeIE type and reference Semantics description CriticalityAssigned Criticality Message TypeM9.2.1.1YESignore Inter-system Information Transfer Type M9.2.1.55YESignore  9.2.1.55Inter-system Information Transfer Type IE/Group NamePresenceRangeIE type and reference Semantics description CHOICE Inter-system Information Transfer Type >RIM >>RIM Transfer9.2.3.23 IE/Group NamePresenceRangeIE type and reference Semantics description RIM Transfer >RIM InformationM9.2.3.24 >RIM Routing Address O9.2.3.25  9.2.3.23RIM Transfer

4. – 9.2.3.24RIM Information IE/Group NamePresenceRangeIE type and reference Semantics description Criticalit y Assigned 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) If the Extended RNC- ID IE is included in the Target ID IE, the RNC- ID IE shall be ignored. - >>Extended RNC- ID O9.2.1.14The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. -  9.2.3.25RIM Routing Address IE/Group NamePresenceRangeIE type and reference Semantics description RIM Information >RIM InformationMOCTET STRINGContains the BSSGP RIM PDU as defined in ref TS 48.018 [18].

5. RIM in 3GPP -1 The information from TS 48.018 (BSSGP) – 8c.1.3RIM PDUs description 8c.1.3.1RAN-INFORMATION-REQUEST PDU 8c.1.3.2RAN-INFORMATION PDU 8c.1.3.3RAN-INFORMATION-ACK PDU 8c.1.3.4RAN-INFORMATION-ERROR PDU 8c.1.3.5RAN-INFORMATION-APPLICATION-ERROR PDU – 10.6PDU functional definitions and contents at RIM SAP Information elementsType / ReferencePresenceFormatLength PDU typePDU type/11.3.26MV1 Destination Cell IdentifierRIM Routing Information/11.3.70MTLV3-? Source Cell IdentifierRIM Routing Information/11.3.70MTLV3-? RIM ContainerRAN-INFORMATION-REQUEST/ RAN-INFORMATION/ -ACK/ - ERROR/ -APPLICATION-ERROR RIM Container/11.3.62a.1/-.2/ -.3/ -.4/ -.5 MTLV3-?

6. – 11.3.62aRIM Container 11.3.62a.1RAN-INFORMATION-REQUEST RIM Container 11.3.62a.2RAN-INFORMATION RIM Container 87654321 Octet 1IEI Octet 2, 2aLength Indicator Octet 3-?RAN-INFORMATION RIM Container Contents coded as defined in table 11.3.62a.2b Information ElementsType / ReferencePresenceFormatLength RIM Application IdentityRIM Application Identity /11.3.61MTLV3 RIM Sequence NumberRIM Sequence Number /11.3.62MTLV6 RIM PDU IndicationsRIM PDU Indications /11.3.65.MTLV3 RIM Protocol Version NumberRIM Protocol Version Number/11.3.67OTLV3 Application Container (NOTE 1)RAN-INFORMATION Application Container /11.3.63.2 C (Note 1)TLV4-? Application Error Container (NOTE 1)Application Error Container/11.3.64C (Note 1)TLVn SON Transfer Application Identity (note 2) SON Transfer Application Identity/11.3.108CTLV3-m NOTE 1:The presence of application information depends on the value of the RIM Application Identity IE. If application information is mandatory either the Application Error Container IE or the Application Container IE is present. NOTE 2:The SON Transfer Application Identity IE shall be present if and only if the RIM Application Identity IE is set to "SON Transfer". Table 11.3.62a.2.b: RAN-INFORMATION RIM Container Contents Table 11.3.62a.2.a: RAN-INFORMATION RIM Container IE

7. – 11.3.63.2RAN-INFORMATION Application Container Unit 11.3.63.2.4 RAN-INFORMATION Application Container for the SON Transfer Application ： SON Transfer Response Container （ RAT discriminator 只定义了 E-UTRAN, UTRAN, GEREN ） Table 11.3.63.2.4: RAN-INFORMATION Application Container coding for SON Transfer 87654321 Octet 1IEI Octet 2, 2aLength Indicator Octet 3SpareRAT discriminator Octet 4-mReporting Cell Identifier Octet (m+1)- n SON Transfer Response Container

8. RIM in 3GPP -2 The information from TS 36.413 (S1AP) – B.1.3SON Transfer Response Container ： Cell Load Reporting Response – B.1.5Cell Load Reporting Response (used for E-UTRAN, UTRAN, GERAN) – B.1.6E-UTRAN Cell Load Reporting Response ： Composite Available Capacity Group IE/Group NamePresenceRangeIE type and reference Semantics description CHOICE SON Transfer ApplicationM >Cell Load Reporting >>Cell Load Reporting ResponseMB.1.5 >Multi-Cell Load Reporting >>Multi-Cell Load Reporting Response MB.1.9 >Event-Triggered Cell Load Reporting >>Event-triggered Cell Load Reporting Response MB.1.12 >HO ReportingNULL IE/Group NamePresenceRangeIE type and referenceSemantics description CHOICE Reporting RATM >E-UTRAN >>E-UTRAN ResponseME-UTRAN Cell Load Reporting Response B.1.6 >UTRAN >>UTRAN ResponseMOCTET STRING >GERAN >>GERAN ResponseMOCTET STRING B.1.3 B.1.5

9. RIM in 3GPP -3 The information from TS 36.423 (X2AP) ， LTE loading information indication for iRAT scenario: – 9.2.44Composite Available Capacity Group: Composite Available Capacity Downlink/Uplink – 9.2.45Composite Available Capacity: Cell Capacity Class Value(1-100, 1 indicates minimum capacity)/ Capacity Value(0~100) IE/Group NamePresenceRangeIE type and reference Semantics descriptionCriticalityAssigned Criticality Composite Available Capacity Downlink MComposite Available Capacity 9.2.45 For the Downlink-- Composite Available Capacity Uplink MComposite Available Capacity 9.2.45 For the Uplink-- IE/Group NamePresenceRangeIE type and reference Semantics description CriticalityAssigned Criticality Cell Capacity Class ValueO9.2.46-- Capacity ValueM9.2.47‘0’ indicates no resource is available, Measured on a linear scale. -- 9.2.44 9.2.45

10. RIM in 3GPP -4 The information from TS 29.274 (S3 between SGSN and MME) – 7.3.19RAN Information Relay Information elementsPCondition / CommentIE TypeIns. BSS ContainerMAll information elements from the RIM messages, starting from and including the BSSGP "PDU type", shall be contained within the BSS Container and forwarded to the destination MME/SGSN in the RAN Information Relay message. F-Container0 RIM Routing AddressCThis IE shall be included if the RIM Routing Address information is included in the message sent from the source RAN node. This IE identifies the destination RAN node where the RAN Information needs to be relayed to. It contains: - the destination RNC Identity when the target is GERAN Iu mode or UTRAN; or - the destination Cell Identity when the target is GERAN; or - the Target eNodeB ID when the target is E-UTRAN. Target Identification0 Private ExtensionONonePrivate ExtensionVS