8.16 MME Configuration Transfer

36.4133GPPEvolved Universal Terrestrial Radio Access Network (E-UTRAN)Release 17S1 Application Protocol (S1AP)TS

8.16.1 General

The purpose of the MME Configuration Transfer procedure is to transfer RAN configuration information from the MME to the eNB in unacknowledged mode.

This procedure uses non-UE associated signalling.

8.16.2 Successful Operation

8.16.2.1 MME Configuration Transfer

Figure 8.16.2.1-1: MME Configuration Transfer procedure. Successful operation.

The procedure is initiated with an MME CONFIGURATION TRANSFER message sent from the MME to the eNB.

If the eNB receives, in the SON Configuration Transfer IE or the EN-DC SON Configuration Transfer IE, the SON Information IE containing the SON Information Request IE, it may transfer back the requested information either towards the eNB indicated in the Source eNB-ID IE of the SON Configuration Transfer IE or towards the eNB indicated in the Source eNB-ID IE of the EN-DC SON Configuration Transfer IE by initiating the eNB Configuration Transfer procedure. If the X2 TNL Configuration Info IE contains the eNB Indirect X2 Transport Layer Addresses IE, the eNB may use it for the X2 TNL establishment, and may transfer back the received eNB Indirect X2 Transport Layer Addresses towards the eNB indicated in the Source eNB-ID IE of the SON Configuration Transfer IE by initiating the eNB Configuration Transfer procedure or towards the eNB indicated in the Source eNB-ID IE of the EN-DC SON Configuration Transfer IE by initiating the eNB Configuration Transfer procedure.

If the eNB receives, in the SON Configuration Transfer IE, the X2 TNL Configuration Info IE containing the eNB X2 Extended Transport Layer Addresses IE, it may use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed.

If the eNB receives, in the SON Configuration Transfer IE or the EN-DC SON Configuration Transfer IE, the SON Information IE containing the SON Information Reply IE including the X2 TNL Configuration Info IE as an answer to a former request, it may use it to initiate the X2 TNL establishment. If the X2 TNL Configuration Info IE contains the eNB Indirect X2 Transport Layer Addresses IE, the eNB may use it for the X2 TNL establishment.

In case the IP-Sec Transport Layer Address IE is present and the GTP Transport Layer Addresses IE within the eNB X2 Extended Transport Layer Addresses IE is not empty, GTP traffic is conveyed within an IP-Sec tunnel terminated at the IP-Sec tunnel end point given in by the IP-Sec Transport Layer Address IE.

In case the IP-Sec Transport Layer Address IE is not present, GTP traffic is terminated at the end points given by the list of addresses in eNB GTP Transport Layer Addresses IE within the eNB X2 Extended Transport Layer Addresses IE.

In case the eNB GTP Transport Layer Addresses IE is empty and the IP-Sec Transport Layer Address IE is present, SCTP traffic is conveyed within an IP-Sec tunnel terminated at the IP-Sec tunnel end point given in the IP-Sec Transport Layer Address IE, within the eNB X2 Extended Transport Layer Addresses IE.

If the eNB is configured to use one IPsec tunnel for all S1 and X2 traffic (IPsec star topology) then the traffic to the peer eNB shall be routed through this IPsec tunnel and the IP-Sec Transport Layer Address IE shall be ignored.

If the eNB receives the SON Information IE containing the SON Information Reply IE including the Time Synchronisation Info IE as an answer to a former request, it may use it for over-the-air synchronisation by means of network listening and for triggering muting activation request.

If the eNB receives the SON Information IE containing the SON Information Report IE, it may use it as specified in TS 36.300 [14].

If the eNB receives the Inter-system SON Configuration Transfer IE containing the Inter-system SON Information Report IE, it may use it as specified in TS 38.300 [45] or in TS 36.300 [14].

If the eNB receives the Inter-system SON Information IE containing the Inter-system SON Information Reply IE, it may use it as specified in TS 38.300 [45] or in TS 36.300 [14].

If the eNB receives the SON Information IE containing the SON Information Request IE set to “Activate Muting”, the eNB should consider activating for over-the-air synchronisation by means of network listening, taking into account information on the selected source of synchronisation cell and the cells as indicated by the Aggressor E-CGI List IE. In case the Aggressor E-CGI List IE is not present, the eNB may consider the request applicable to all cells.

If the eNB receives the SON Information IE containing the SON Information Reply IE including the Muting Pattern Information IE as an answer to a former request, it may use it for over-the-air synchronisation by means of network listening. The Muting Pattern Information IE may apply to all cells that were requested to mute.

If the eNB receives the SON Information IE containing the SON Information Request IE set to “Deactivate Muting”, the eNB may consider deactivating muting for over-the-air synchronisation that was activated by a former muting request from the corresponding eNB.

8.16.3 Abnormal Conditions

Not applicable.