tsg-a wg3 title: irat son in 3gpp source: yuanfang yu, xiaowu zhao, ting lu, yonggang fang abstract:...
TRANSCRIPT
TSG-A WG3
Title: iRAT SON in 3GPPSource: 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.
SON between E-UTRAN and UTRAN/GERAN
SGSNBSS
MMEeNodeB
E-UTRAN
GERAN
Gb/Iu
RIM Signaling
Relaying RIM Signaling S3/Gn
S1
RIM Signaling
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.
RIM in 3GPP -0
• The information from TS 36.413 (S1AP)– 9.1.14 eNB DIRECT INFORMATION TRANSFER (Direction: eNB MME)This message is sent by the eNB in order to transfer specific information.– 9.1.15 MME DIRECT INFORMATION TRANSFER (Direction: MME eNB)
IE/Group Name Presence Range IE type and reference
Semantics description
Criticality Assigned Criticality
Message Type M 9.2.1.1 YES ignoreInter-system Information Transfer Type
M 9.2.1.55 YES ignore
9.2.1.55 Inter-system Information Transfer TypeIE/Group Name Presence Range IE type and
referenceSemantics description
CHOICE Inter-system Information Transfer Type
>RIM>>RIM Transfer 9.2.3.23
IE/Group Name Presence Range IE type and reference
Semantics description
RIM Transfer>RIM Information M 9.2.3.24>RIM Routing Address
O 9.2.3.25
9.2.3.23 RIM Transfer
– 9.2.3.24 RIM Information
IE/Group Name Presence Range IE type and reference
Semantics description
Criticality
Assigned Criticality
CHOICE RIM Routing Address
>GERAN-Cell-ID ->>LAI M .1 ->>RAC M 9.2.3.2 ->>CI M OCTET
STRING (2)-
>Target RNC-ID ->>LAI M 9.2.3.1 ->>RAC O 9.2.3.2 ->>RNC-ID M INTEGER
(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
O 9.2.1.14 The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095.
-
9.2.3.25 RIM Routing Address
IE/Group Name Presence Range IE type and reference
Semantics description
RIM Information>RIM Information M OCTET STRING Contains the BSSGP RIM
PDU as defined in ref TS 48.018 [18].
RIM in 3GPP -1
• The information from TS 48.018 (BSSGP)– 8c.1.3 RIM PDUs description
• 8c.1.3.1 RAN-INFORMATION-REQUEST PDU• 8c.1.3.2 RAN-INFORMATION PDU• 8c.1.3.3 RAN-INFORMATION-ACK PDU• 8c.1.3.4 RAN-INFORMATION-ERROR PDU• 8c.1.3.5 RAN-INFORMATION-APPLICATION-ERROR PDU
– 10.6 PDU functional definitions and contents at RIM SAP
Information elements Type / Reference Presence Format Length
PDU type PDU type/11.3.26 M V 1
Destination Cell Identifier RIM Routing Information/11.3.70 M TLV 3-?
Source Cell Identifier RIM Routing Information/11.3.70 M TLV 3-?
RIM Container RAN-INFORMATION-REQUEST/ RAN-INFORMATION/ -ACK/ -ERROR/ -APPLICATION-ERROR RIM Container/11.3.62a.1/-.2/ -.3/ -.4/ -.5
M TLV 3-?
– 11.3.62a RIM Container• 11.3.62a.1 RAN-INFORMATION-REQUEST RIM Container• 11.3.62a.2 RAN-INFORMATION RIM Container
8 7 6 5 4 3 2 1Octet 1 IEI
Octet 2, 2a Length IndicatorOctet 3-? RAN-INFORMATION RIM Container Contents coded as defined in
table 11.3.62a.2b
Information Elements Type / Reference Presence Format LengthRIM Application Identity RIM Application Identity /11.3.61 M TLV 3RIM Sequence Number RIM Sequence Number /11.3.62 M TLV 6
RIM PDU Indications RIM PDU Indications /11.3.65. M TLV 3RIM Protocol Version Number RIM Protocol Version Number/11.3.67 O TLV 3
Application Container (NOTE 1) RAN-INFORMATION Application Container /11.3.63.2
C (Note 1) TLV 4-?
Application Error Container (NOTE 1) Application Error Container/11.3.64 C (Note 1) TLV nSON Transfer Application Identity (note
2)SON Transfer Application Identity/11.3.108 C TLV 3-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
– 11.3.63.2 RAN-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
8 7 6 5 4 3 2 1
Octet 1 IEI
Octet 2, 2a Length Indicator
Octet 3 Spare RAT discriminator
Octet 4-m Reporting Cell Identifier
Octet (m+1)-n
SON Transfer Response Container
RIM in 3GPP -2• The information from TS 36.413 (S1AP)
– B.1.3 SON Transfer Response Container: Cell Load Reporting Response– B.1.5 Cell Load Reporting Response (used for E-UTRAN, UTRAN, GERAN)– B.1.6 E-UTRAN Cell Load Reporting Response: Composite Available Capacity Group
IE/Group Name Presence Range IE type and reference
Semantics description
CHOICE SON Transfer Application M>Cell Load Reporting
>>Cell Load Reporting Response M B.1.5>Multi-Cell Load Reporting
>>Multi-Cell Load Reporting Response
M B.1.9
>Event-Triggered Cell Load Reporting
>>Event-triggered Cell Load Reporting Response
M B.1.12
>HO Reporting NULL
IE/Group Name Presence Range IE type and reference Semantics description
CHOICE Reporting RAT M>E-UTRAN
>>E-UTRAN Response M E-UTRAN Cell Load Reporting Response B.1.6
>UTRAN>>UTRAN Response M OCTET STRING
>GERAN>>GERAN Response M OCTET STRING
B.1.3
B.1.5
RIM in 3GPP -3
• The information from TS 36.423 (X2AP), LTE loading information indication for iRAT scenario:
– 9.2.44 Composite Available Capacity Group: Composite Available Capacity Downlink/Uplink– 9.2.45 Composite Available Capacity: Cell Capacity Class Value(1-100, 1 indicates minimum
capacity)/ Capacity Value(0~100)
IE/Group Name Presence Range IE type and reference
Semantics description Criticality Assigned Criticality
Composite Available Capacity Downlink
M Composite Available Capacity 9.2.45
For the Downlink - -
Composite Available Capacity Uplink
M Composite Available Capacity 9.2.45
For the Uplink - -
IE/Group Name Presence Range IE type and reference
Semantics description
Criticality Assigned Criticality
Cell Capacity Class Value O 9.2.46 - -Capacity Value M 9.2.47 ‘0’ indicates no
resource is available, Measured on a linear scale.
- -
9.2.44
9.2.45
RIM in 3GPP -4
• The information from TS 29.274 (S3 between SGSN and MME)– 7.3.19 RAN Information Relay
Information elements P Condition / Comment IE Type Ins.
BSS Container M All 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-Container 0
RIM Routing Address C This 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 Identification 0
Private Extension O None Private Extension VS