3-2 - S1AP

eRAN2.2

eRAN2.2

S1AP

S1AP

written consent of Huawei Technologies Co., Ltd. written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions Trademarks and Permissions

and other Huawei trademarks are trademarks of

and other Huawei trademarks are trademarks of Huawei TechnoloHuawei Technologies Co., Ltd.gies Co., Ltd.  All

 All other other trademarks trademarks and and trade trade names names mentionementioned d in in this this documendocument t are are the the property property of of their their respectiverespective holders.

holders.

Notice Notice

The purchased products, services and features are stipulated by the contract made between Huawei and The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.

or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd.

 Address:

 Address: Huawei Industrial BaseHuawei Industrial Base Bantian, Longgang Bantian, Longgang Shenzhen 518129 Shenzhen 518129

People's Republic of China People's Republic of China Website:

Website: http://www.huawei.comhttp://www.huawei.com

Email:

written consent of Huawei Technologies Co., Ltd. written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions Trademarks and Permissions

and other Huawei trademarks are trademarks of

and other Huawei trademarks are trademarks of Huawei TechnoloHuawei Technologies Co., Ltd.gies Co., Ltd.  All

 All other other trademarks trademarks and and trade trade names names mentionementioned d in in this this documendocument t are are the the property property of of their their respectiverespective holders.

holders.

Notice Notice

The purchased products, services and features are stipulated by the contract made between Huawei and The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.

or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd.

 Address:

 Address: Huawei Industrial BaseHuawei Industrial Base Bantian, Longgang Bantian, Longgang Shenzhen 518129 Shenzhen 518129

People's Republic of China People's Republic of China Website:

Website: http://www.huawei.comhttp://www.huawei.com

Email:

About This Document

About This Document

Change History

Change History

The change history describes the changes in

The change history describes the changes in each release, and the latest each release, and the latest document contains alldocument contains all change histories in earlier documents.

change histories in earlier documents.

Issue 01 (2011-09-30)

Issue 01 (2011-09-30)

First official release. First official release.

Contents

About This Document...iii

1 Overview...1

2 E-RAB Management... 6

3 Context Management...8

3.1 Initial Context Setup...8

3.2 UE Context Release...9

3.3 UE Context Modification...10

4 Handover Signaling...11

4.1 Handover Preparation...11

4.2 Handover Resource Allocation... 12

4.3 Handover Notification...13

4.4 Path Switch Request...13

4.5 Handover Cancelation...14

4.6 eNodeB Status Transfer...14

4.7 MME Status Transfer...15

5 Paging... 16

6 NAS Transport... 17

6.1 Initial UE Message...17

6.2 Downlink NAS Transport...18

6.3 Uplink NAS Transport...18

6.4 NAS Non Delivery Indication...19

7 Management Procedures...20

7.1 Reset...20

7.2 Error Indication...21

7.4 eNodeB Configuration Update...22

7.5 MME Configuration Update...23

7.6 Overload Start...24

7.7 Overload Stop...24

8 UE Capability Information Indication...25

9 eNodeB Direct Information Transfer...26

10 MME Direct Information Transfer...27

11 eNodeB Configuration Transfer...28

1

Overview

The S1 interface connects the eNodeB and the mobility management entity (MME) or serving gateway (S-GW) and has two planes: user plane and control plane.

1.1 S1 User Plane

The S1 interface transmits data between the eNodeB and the S-GW. The S1 user plane transmits data at the transport network layer based on the Internet Protocol (IP).

Figure 1.1S1 user plane

GTP-U UDP

IP

Data link layer  User plane PDUs

1.2 S1 Control Plane

Figure 1.1S1 control plane

SCTP IP

Data link layer  S1-AP

Physical layer 

The S1 control plane transmits data based on the IP and Stream Control Transmission Protocol (SCTP) to provide reliable data transmission for radio networks.

The S1 Application Protocol (S1AP) transmits signaling between the evolved packet core (EPC) and the evolved universal terrestrial radio access network (E-UTRAN) to provide S1AP services. The S1AP has the following functions:

 E-UTRAN radio access bearer (E-RAB) management. This function is used to establish, modify, and release an E-RAB.

 Initial context transfer. This function is used to establish S1 user equipment (UE)

contexts on an eNodeB, to establish one or more E-RABs if requested by an MME, and to transfer information about non-access stratum (NAS) signaling to the eNodeB.  UE capability information indication.

 UE mobility management in LTE_ACTIVE mode, including intra-LTE handovers and inter-RAT handovers.

 Paging. This function enables the EPC to page UEs.

 S1 interface management. For example, error indication and S1 setup.   NAS signaling transfer between the UE and the MME.

 S1 UE context release.  UE context modification.  Status transfer.

 Tracing

 Location reporting.  LPPa signaling transfer.

Table 1.1Class 1 procedures Elementar y Procedure Initiating Message Successful Outcome Unsuccessful Outcome Response Message Response Message Handover  Preparation HANDOVER  REQUIRED HANDOVER  COMMAND HANDOVER  PREPARATION FAILURE Handover  Resource Allocation HANDOVER  REQUEST HANDOVER  REQUEST ACKNOWLEDGE HANDOVER  FAILURE Path Switch Request PATH SWITCH REQUEST PATH SWITCH REQUEST ACKNOWLEDGE PATH SWITCH REQUEST FAILURE Handover  Cancelation HANDOVER  CANCEL HANDOVER CANCEL ACKNOWLEDGE E-RAB Setup E-RAB SETUP

REQUEST E-RAB SETUP RESPONSE E-RAB Modify E-RAB MODIFY REQUEST E-RAB MODIFY RESPONSE E-RAB Release E-RAB RELEASE COMMAND E-RAB RELEASE RESPONSE Initial Context Setup INITIAL CONTEXT SETUP REQUEST INITIAL CONTEXT SETUP RESPONSE INITIAL CONTEXT SETUP FAILURE

Reset RESET RESET

ACKNOWLEDGE S1 Setup S1 SETUP

REQUEST

S1 SETUP RESPONSE S1 SETUP FAILURE

UE Context Release UE CONTEXT RELEASE COMMAND UE CONTEXT RELEASE COMPLETE UE Context Modification UE CONTEXT MODIFICATION REQUEST UE CONTEXT MODIFICATION RESPONSE UE CONTEXT MODIFICATION FAILURE eNB Configuration Update ENB CONFIGURATION UPDATE ENB CONFIGURATION UPDATE ACKNOWLEDGE ENB CONFIGURATION UPDATE FAILURE MME Configuration Update MME CONFIGURATION UPDATE MME CONFIGURAION UPDATE ACKNOWLEDGE MME CONFIGURATION UPDATE FAILURE

Elementar y Procedure Initiating Message Successful Outcome Unsuccessful Outcome Response Message Response Message Write-Replace Warning WRITE-REPLACE WARNING REQUEST WRITE-REPLACE WARNING RESPONSE

Kill KILL REQUEST KILL RESPONSE

Table 1.2Class 2 procedures

Elementary Procedure Message

Handover Notification HANDOVER NOTIFY

E-RAB Release Indication E-RAB RELEASE INDICATION

Paging PAGING

Initial UE Message INITIAL UE MESSAGE

Downlink NAS Transport DOWNLINK NAS TRANSPORT Uplink NAS Transport UPLINK NAS TRANSPORT

 NAS non delivery indication NAS NON DELIVERY INDICATION Error Indication ERROR INDICATION

UE Context Release Request UE CONTEXT RELEASE REQUEST DownlinkS1 CDMA2000 Tunneling DOWNLINK S1 CDMA2000 TUNNELING Uplink S1 CDMA2000 Tunneling UPLINK S1 CDMA2000 TUNNELING UE Capability Info Indication UE CAPABILITY INFO INDICATION eNB Status Transfer eNB STATUS TRANSFER  

MME Status Transfer MME STATUS TRANSFER   Deactivate Trace DEACTIVATE TRACE Trace Start TRACE START

Trace Failure Indication TRACE FAILURE INDICATION Location Reporting Control LOCATION REPORTING CONTROL Location Reporting Failure Indication LOCATION REPORTING FAILURE

INDICATION

Location Report LOCATION REPORT Overload Start OVERLOAD START

Elementary Procedure Message

Overload Stop OVERLOAD STOP

eNodeB Direct Information Transfer eNB DIRECT INFORMATION TRANSFER  MME Direct Information Transfer MME DIRECT INFORMATION TRANSFER  eNodeB Configuration Transfer eNB CONFIGURATION TRANSFER 

MME Configuration Transfer MME CONFIGURATION TRANSFER  Cell Traffic Trace CELL TRAFFIC TRACE

Downlink UE Associated LPPa Transport

DOWNLINK UE ASSOCIATED LPPA TRANSPORT

Uplink UE Associated LPPa Transport UPLINK UE ASSOCIATED LPPA TRANSPORT Downlink Non UE Associated LPPa

Transport

DOWNLINK NON UE ASSOCIATED LPPA TRANSPORT

Uplink Non UE Associated LPPa Transport

UPLINK NON UE ASSOCIATED LPPA TRANSPORT

2

E-RAB Management

2.1 E-RAB Setup

The purpose of this procedure is to allocate resources to the Uu and the S1 interfaces for one or more E-RABs and to set up data radio bearers (DRBs) for a specific UE.

Figure 1.1E-RAB Setup procedure (successful operation)

E-RAB SETUP RESPONSE E-RAB SETUP REQUEST

eNB MME

The MME sends an E-RAB SETUP REQUEST message to initiate the procedure. After  receiving the message, the eNodeB sends the MME an E-RAB SETUP REQUEST message if  the required resources are available.

If the E-RAB SETUP REQUEST message contains the UE Aggregate Maximum Bit Rate information element (IE), the eNodeB replaces the UE Aggregate Maximum Bit Rate IE with the UE Aggregate Maximum Bit Rate IE.

If the E-RAB SETUP REQUEST message does not contain the UE Aggregate Maximum Bit   Rate IE, the eNodeB uses the UE Aggregate Maximum Bit Rate IE in the UE context.

Resources are set up or modified on an eNodeB based on the  Allocation and Retention  Priority IE.

2.2 E-RAB Modify

Figure 1.1E-RAB Modify procedure (successful operation)

E-RAB MODIFY RESPONSE E-RAB MODIFY REQUEST

eNB MME

The MME sends an E-RAB SETUP REQUEST message to initiate the procedure. An E-RAB MODIFY REQUEST message contains information about one or more configured E-RABs.

2.3 E-RAB Release

The purpose of this procedure is to release a configured E-RAB in either of the following modes:

 MME-initiated E-RAB release

Figure 1.1MME-initiated E-RAB Release procedure (successful operation)

E-RAB RELEASE RESPONSE E-RAB RELEASE COMMAND

eNB MME

 eNodeB-initiated E-RAB release

Figure 1.2eNodeB-initiated E-RAB Release procedure (successful operation)

E-RAB RELEASE INDICATION

3

Context Management

3.1 Initial Context Setup

The purpose of this procedure is to set up mandatory UE contexts, including the E-RAB context, security key, and handover restriction list.

Figure 1.1Initial Context Setup procedure (successful operation)

INITIAL CONTEXT SETUP RESPONSE INITIAL CONTEXT SETUP REQUEST

eNB MME

The EPC must get ready for receiving user-plane data on an E-RAB before the MME receives a CONTEXT SETUP RESPONSE message from an eNodeB.

The eNodeB must perform the following operations after receiving an INITIAL CONTEXT SETUP REQUEST message:

1. Attempts to execute the requested E-RAB configuration.

2. Saves the UE Aggregate Maximum Bit Rate IE in the UE context and uses the received UE Aggregate Maximum Bit Rate IE.

3. Saves the handover restriction list in the UE context. 4. Saves the UE capability in the UE context.

If the eNodeB cannot set up the UE context, it sends an INITIAL CONTEXT SETUP FAILURE message to the MME.

Figure 4.1Initial Context Setup procedure (unsuccessful operation)

INITIAL CONTEXT SETUP FAILURE INITIAL CONTEXT SETUP REQUEST

eNB MME

3.2 UE Context Release

The UE context can be released in either of the following modes:  eNodeB-initiated UE context release

UE CONTEXT RELEASE REQUEST

eNB MME

A UE CONTEXT RELEASE REQUEST message contains the reasons why UEs are not in the active state and why UEs exit the wireless network.

 MME-initiated UE Context Release procedure

UE CONTEXT RELEASE COMPLETE UE CONTEXT RELEASE COMMAND

eNB MME

The MME sends the eNodeB a UE CONTEXT RELEASE COMMAND message to initiate the procedure. The UE CONTEXT RELEASE COMMAND message contains the UE S1AP   ID pair IE. If the message does not contain the IE, it must contain the MME UE S1AP ID IE.

After receiving the UE CONTEXT RELEASE COMMAND message, the eNodeB releases all related resources for the IEs and user-plane data transmission and responds to the MME with a UE CONTEXT RELEASE COMPLETE message.

3.3 UE Context Modification

This purpose of this procedure is to modify the configured UE context.

Figure 1.1UE Context Modification procedure (successful operation)

UE CONTEXT MODIFICATION RESPONSE UE CONTEXT MODIFICATION REQUEST

eNB MME

A UE CONTEXT MODIFICATION REQUEST message contains the following IEs:  Security Key

 Subscriber Profile ID for RAT/Frequency Priority  UE Aggregate Maximum Bit Rate

 CS Fallback Indicator   UE Security Capabilities  CSG Membership Status  Registered LAI

Figure 1.2UE Context Modification procedure (unsuccessful operation)

UE CONTEXT MODIFICATION FAILURE UE CONTEXT MODIFICATION REQUEST

eNB MME

If UE context modification fails, the eNodeB responds to the MME with a UE CONTEXT MODIFICATION FAILURE message that contains the Cause IE.

4

Handover Signaling

4.1 Handover Preparation

The purpose of this procedure is to enable the EPC to instruct a target eNodeB to prepare all resources before a handover is performed. Each UE has only one handover preparation  process at the same time.

Figure 1.1Handover Preparation procedure (successful operation) source

eNB

HANDOVER REQUIRED

MME

HANDOVER COMMAND

The source eNodeB sends the MME a HANDOVER REQUIRED message to initiate the  procedure. When the source eNodeB sends the message, it starts the TS1RELOCpreptimer. After 

the handover preparation, including resource subscription on the target eNodeB, the MME responds to the source eNodeB a HANDOVER COMMAND message. After receiving the HANDOVER COMMAND message, the source eNodeB stops the TS1RELOCpreptimer and

starts the TS1RELOCOverall timer.

If the EPC or the target eNodeB cannot accept any bearers or the handover fails, the MME sends the source eNodeB a HANDOVER PREPARATION FAILURE message that contains the reason why the failure occurs.

Figure 1.2Handover Preparation procedure (unsuccessful operation)

HANDOVER REQUIRED

MME

HANDOVER PREPARATION FAILURE source

eNB

4.2 Handover Resource Allocation

The purpose of this procedure is to reserve resources at the target eNodeB for a UE to be handed over.

Figure 1.1Hanover Resource Allocation procedure (successful operation)

HANDOVER REQUEST

MME

HANDOVER REQUEST ACKNOWLEDGE target

eNB

The MME sends the target eNodeB a HANDOVER REQUEST message to initiate the  procedure. After receiving the HANDOVER REQUEST message, the target eNodeB saves

the UE Security Capabilities IE and uses the configuration of the IE and related UE access stratum (AS) to encrypt data.

Figure 1.2Hanover Resource Allocation procedure (unsuccessful operation)

HANDOVER REQUEST

MME

HANDOVER FAILURE target

4.3 Handover Notification

The purpose of this procedure is to inform the MME, UE, and target cell of a successful S1 handover.

Figure 1.1Handover Notification procedure

HANDOVER NOTIFY

MME target

eNB

4.4 Path Switch Request

The purpose of this procedure is to request the switch of a downlink GPRS tunneling protocol (GTP) tunnel towards a new GTP tunnel. GPRS is short for general packet radio service.

Figure 1.1Path Switch Request procedure (successful operation) eNB

PATH SWITCH REQUEST

MME

PATH SWITCH REQUEST ACKNOWLEDGE

An eNodeB sends to the MME a PATH SWITCH REQUEST message to initiate the  procedure.

Figure 1.2Path Switch Request procedure (unsuccessful operation)

PATH SWITCH REQUEST

MME

PATH SWITCH REQUEST FAILURE eNB

REQUEST FAILURE message that contains the reason why the failure occurs.

4.5 Handover Cancelation

The purpose of this procedure is to enable a source eNodeB to cancel ongoing handover   preparations or a prepared handover.

Figure 1.1Handover Cancelation procedure (successful operation)

HANDOVER CANCEL

Source eNB MME

HANDOVER CANCEL  ACKNOWLEDGE

The source eNodeB sends the MME a HANDOVER CANCEL message to initiate the  procedure. A HANDOVER CANCEL message contains the Cause IE. After receiving the

HANDOVER CANCEL message, the EPC stops the ongoing process, releases resources for a handover, and sends the source eNodeB a HANDOVER CANCEL ACKNOWLEDGE

message.

4.6 eNodeB Status Transfer

In this procedure, two types of status are transmitted: the receiving status of uplink Packet Data Convergence Protocol-sequence number (PDCP-SN) and hyper frame number (HFN) and the transmitting status of downlink PDCP-SN and HFN.

Figure 1.1eNodeB Status Transfer procedure eNB

eNB STATUS TRANSFER

4.7 MME Status Transfer

Figure 1.1MME Status Transfer procedure eNB

MME STATUS TRANSFER

5

Paging

The purpose of this procedure is to enable the MME to page UEs.

Figure 1.1Paging procedure

PAGING

6

NAS Transport

The purpose of this procedure is to carry UE–MME signaling over the S1 in terface. The NAS messages are transported in an IE of the INITIAL UE MESSAGE, DOWNLINK NAS

TRANSPORT, or UPLINK NAS TRANSPORT message.

6.1 Initial UE Message

Figure 1.1Initial UE Message procedure

INITIAL UE MESSAGE

eNB MME

After receiving the first UL NAS message transmitted on a radio resource control (RRC) connection to be forwarded to an MME, the eNodeB must activate the NAS transport  procedure and send the MME an INITIAL UE MESSAGE message.

6.2 Downlink NAS Transport

Figure 1.1Downlink NAS Transport procedure

DOWNLINK NAS TRANSPORT

eNB MME

The MME sends a UE an NAS message through the eNodeB.

6.3 Uplink NAS Transport

Figure 1.1Uplink NAS Transport procedure

UPLINK NAS TRANSPORT

6.4 NAS Non Delivery Indication

Figure 1.1 NAs Non Delivery Indication procedure

NAS NON DELIVERY I NDICATION

eNB MME

If an eNodeB decides not to start the delivery of a NAS message or the eNodeB cannot ensure that a UE receives the message, the eNodeB reports the non-delivery of this NAS message by sending the MME an NAS NON DELIVERY INDICATION message.

7

Management Procedures

7.1 Reset

The reset procedure can be initiated by either the MME or the E-UTRAN. MME-initiated reset procedure:

Figure 1.1MME-initiated Reset procedure (successful operation)

MME eNB

RESET

RESET ACKNOWLEDGE

If the MME loses some or all transaction reference information, it sends the eNodeB a RESET message. After receiving the RESET message, the eNodeB releases all allocated resources over the S1 interface and Uu interface related to UEs. Then, the eNodeB responds to the MME with a RESET ACKNOWLEDGE message.

Figure 1.2E-UTRAN-initiated Reset procedure (successful operation)

MME eNB

RESET

RESET ACKNOWLEDGE

If the eNodeB loses some or all transaction reference information, it sends the MME a RESET message. After receiving the RESET message, the MME releases all allocated

resources over the S1 interface related to UEs. Then, the MME responds to the eNodeB with a RESET ACKNOWLEDGE message.

7.2 Error Indication

The purpose of this procedure is to report detected errors in one incoming message at one node. This procedure can be initiated either by the MME or by an eNodeB.

Figure 1.1MME-initiated Error Indication procedure (successful operation)

MME eNB

ERROR INDICATION

Figure 1.2eNodeB-initiated Error Indication procedure (successful operation)

MME eNB

ERROR INDICATION

An ERROR INDICATION message must contain a minimum of one Cause IE or Criticality  Diagnostics IE.

7.3 S1 Setup

Figure 1.1S1 Setup procedure (successful operation) eNB

S1 SETUP REQUEST

MME

S1 SETUP RESPONSE

The eNodeB sends the MME an S1 SETUP REQUEST message to initiate the procedure. Then, the MME responds to the eNodeB with an S1 SETUP RESPONSE message. When this  procedure is finished, the S1 interface is operational and other S1 messages can be exchanged.

Figure 1.2S1 Setup procedure (unsuccessful operation) eNB

S1 SETUP REQUEST

MME

S1 SETUP FAILURE

If the MME cannot accept the setup, it responds to the eNodeB with an S1 SETUP FAILURE message.

7.4 eNodeB Configuration Update

The purpose of this procedure is to update configuration data at the application layer over the S1 interface.

Figure 1.1eNodeB Configuration Update procedure (successful operation)

eNB

ENB CONFIGURATION UPDATE

MME

An eNodeB sends the MME an ENB CONFIGURATION UPDATE message including a set of updated configuration data. If the MME successfully updates the configuration data, it sends the eNodeB an ENB CONFIGURATION UPDATE ACKNOWLEDGE message. If the MME cannot update the configuration data, it responds to the eNodeB with an ENB

CONFIGURATION UPDATE FAILURE message.

Figure 1.2eNodeB Configuration Update procedure (unsuccessful operation)

eNB

ENB CONFIGURATION UPDATE

MME

ENB CONFIGURATION UPDATE FAILURE

7.5 MME Configuration Update

The purpose of this procedure is to update configuration data at the application layer over the S1 interface.

Figure 1.1MME Configuration Update procedure (successful operation)

eNB

MME CONFIGURATION UPDATE

MME

MME CONFIGURATION UPDATE ACKNOWLEDGE

The MME sends an eNodeB an MME CONFIGURATION UPDATE message including a set of updated configuration data. If the eNodeB successfully updates the configuration data, it sends the MME an MME CONFIGURATION UPDATE ACKNOWLEDGE message. If the eNodeB cannot update the configuration data, it responds to the MME with an MME

7.6 Overload Start

The purpose of this procedure is to inform an eNodeB to reduce the signaling load towards the connected MME.

Figure 1.1Overload Start procedure

OVERLOAD START

eNB MME

7.7 Overload Stop

The purpose of this procedure is to inform an eNodeB that the overload status at the MME has ended and normal operation resumes.

Figure 1.1Overload Stop procedure

OVERLOAD STOP

8

UE Capability Information

Indication

The purpose of this procedure is to enable an eNodeB to provide UE capability information for the MME.

Figure 1.1UE Capability Information Indication procedure (successful operation)

UE CAPABILITY INFO INDICATION

eNB MME

An eNodeB sends the MME a UE CAPABILITY INFO INDICATION message to provide UE capability information for the MME. After obtaining UE capability information in the received message, the MME replaces any previously stored UE capability information for  UEs.

9

eNodeB Direct Information

Transfer

The purpose of this procedure is to transfer RAN information from an eNodeB to the MME in unacknowledged mode.

Figure 1.1eNodeB Direct Information Transfer procedure (successful operation) eNB

ENB DIRECT INFORMATION TRANSFER MME

10

MME Direct Information

Transfer

The MME sends an eNodeB a DIRECT INFORMATION TRANSFER message to initiate the  procedure.

Figure 1.1MME Direct Information Transfer procedure (successful operation) eNB

MME DIRECT INFORMATION TRANSFER MME

11

eNodeB Configuration

Transfer

The purpose of this procedure is to transfer RAN configuration information from an eNodeB to the MME in unacknowledged mode.

Figure 1.1eNodeB Configuration Transfer procedure (successful operation) eNB

ENB CONFIGURATION TRANSFER