3-2 - S1ap

Doc.
Code
eRAN2.2
S1AP
Issue Date
01 2011-09-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
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 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 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 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.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China Website: Email: http://www.huawei.com support@huawei.com
Issue 01 (2011-09-30)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
ii
eRAN2.2 S1AP
About This Document
About This Document

Change History
The change history describes the changes in each release, and the latest document contains all change histories in earlier documents.
Issue 01 (2011-09-30)
First official release.
Issue 01 (2011-09-30)
iii
eRAN2.2 S1AP
Contents
Contents
About This Document......................................................................iii 1 Overview...................................................................................... 1
1.1 S1 User Plane............................................................................................................................................................1 1.2 S1 Control Plane.......................................................................................................................................................2
2 E-RAB Management.......................................................................6
2.1 E-RAB Setup............................................................................................................................................................6 2.2 E-RAB Modify.........................................................................................................................................................6 2.3 E-RAB Release.........................................................................................................................................................7
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.3 S1 Setup..................................................................................................................................................................22 Issue 01 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd iv
eRAN2.2 S1AP
Contents
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 12 MME Configuration Transfer.......................................................29
Issue 01 (2011-09-30)
eRAN2.2 S1AP
12 MME Configuration Transfer
1
1.1 S1 User Plane
Figure 1.1 S1 user plane
User plane PDUs
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.
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).
GTP-U UDP IP Data link layer Physical layer
Issue 01 (2011-09-30)
eRAN2.2 S1AP
1.2 S1 Control Plane

Figure 1.1 S1 control plane
S1-AP
SCTP IP Data link layer 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.
S1AP has two classes of basic procedures, as shown in Table 1.1 and Table 1.2.
Issue 01 (2011-09-30)
eRAN2.2 S1AP
Table 1.1 Class 1 procedures Elementar y Procedure Initiating Message Successful Outcome Response Message HANDOVER REQUIRED HANDOVER REQUEST PATH SWITCH REQUEST HANDOVER CANCEL E-RAB SETUP REQUEST E-RAB MODIFY REQUEST E-RAB RELEASE COMMAND INITIAL CONTEXT SETUP REQUEST RESET S1 SETUP REQUEST UE CONTEXT RELEASE COMMAND UE CONTEXT MODIFICATION REQUEST ENB CONFIGURATION UPDATE MME CONFIGURATION UPDATE HANDOVER COMMAND HANDOVER REQUEST ACKNOWLEDGE PATH SWITCH REQUEST ACKNOWLEDGE HANDOVER CANCEL ACKNOWLEDGE E-RAB SETUP RESPONSE E-RAB MODIFY RESPONSE E-RAB RELEASE RESPONSE INITIAL CONTEXT SETUP RESPONSE RESET ACKNOWLEDGE S1 SETUP RESPONSE UE CONTEXT RELEASE COMPLETE UE CONTEXT MODIFICATION RESPONSE ENB CONFIGURATION UPDATE ACKNOWLEDGE MME CONFIGURAION UPDATE ACKNOWLEDGE UE CONTEXT MODIFICATION FAILURE ENB CONFIGURATION UPDATE FAILURE MME CONFIGURATION UPDATE FAILURE S1 SETUP FAILURE INITIAL CONTEXT SETUP FAILURE Unsuccessful Outcome Response Message HANDOVER PREPARATION FAILURE HANDOVER FAILURE PATH SWITCH REQUEST FAILURE
Handover Preparation Handover Resource Allocation Path Switch Request Handover Cancelation E-RAB Setup E-RAB Modify E-RAB Release Initial Context Setup Reset S1 Setup UE Context Release UE Context Modification eNB Configuration Update MME Configuration Update
Issue 01 (2011-09-30)
eRAN2.2 S1AP
Elementar y Procedure
Initiating Message
Successful Outcome Response Message
Unsuccessful Outcome Response Message
Write-Replace Warning Kill
WRITE-REPLACE WARNING REQUEST KILL REQUEST
WRITE-REPLACE WARNING RESPONSE KILL RESPONSE
Table 1.2 Class 2 procedures Elementary Procedure Handover Notification E-RAB Release Indication Paging Initial UE Message Downlink NAS Transport Uplink NAS Transport NAS non delivery indication Error Indication UE Context Release Request DownlinkS1 CDMA2000 Tunneling Uplink S1 CDMA2000 Tunneling UE Capability Info Indication eNB Status Transfer MME Status Transfer Deactivate Trace Trace Start Trace Failure Indication Location Reporting Control Location Reporting Failure Indication Location Report Overload Start Message HANDOVER NOTIFY E-RAB RELEASE INDICATION PAGING INITIAL UE MESSAGE DOWNLINK NAS TRANSPORT UPLINK NAS TRANSPORT NAS NON DELIVERY INDICATION ERROR INDICATION UE CONTEXT RELEASE REQUEST DOWNLINK S1 CDMA2000 TUNNELING UPLINK S1 CDMA2000 TUNNELING UE CAPABILITY INFO INDICATION eNB STATUS TRANSFER MME STATUS TRANSFER DEACTIVATE TRACE TRACE START TRACE FAILURE INDICATION LOCATION REPORTING CONTROL LOCATION REPORTING FAILURE INDICATION LOCATION REPORT OVERLOAD START
Issue 01 (2011-09-30)
eRAN2.2 S1AP
Elementary Procedure Overload Stop eNodeB Direct Information Transfer MME Direct Information Transfer eNodeB Configuration Transfer MME Configuration Transfer Cell Traffic Trace Downlink UE Associated LPPa Transport Uplink UE Associated LPPa Transport Downlink Non UE Associated LPPa Transport Uplink Non UE Associated LPPa Transport
Message OVERLOAD STOP eNB DIRECT INFORMATION TRANSFER MME DIRECT INFORMATION TRANSFER eNB CONFIGURATION TRANSFER MME CONFIGURATION TRANSFER CELL TRAFFIC TRACE DOWNLINK UE ASSOCIATED LPPA TRANSPORT UPLINK UE ASSOCIATED LPPA TRANSPORT DOWNLINK NON UE ASSOCIATED LPPA TRANSPORT UPLINK NON UE ASSOCIATED LPPA TRANSPORT
Issue 01 (2011-09-30)
eRAN2.2 S1AP
2
2.1 E-RAB Setup
eNB
E-RAB Management
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.1 E-RAB Setup procedure (successful operation)
MME
E-RAB SETUP REQUEST
E-RAB SETUP RESPONSE
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

The purpose of this procedure is to modify an E-RAB configured for UEs.
Issue 01 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 6
eRAN2.2 S1AP
Figure 1.1 E-RAB Modify procedure (successful operation)
eNB
MME
E-RAB MODIFY REQUEST
E-RAB MODIFY RESPONSE
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.1 MME-initiated E-RAB Release procedure (successful operation)
eNB E-RAB RELEASE COMMAND
MME
E-RAB RELEASE RESPONSE
eNodeB-initiated E-RAB release
Figure 1.2 eNodeB-initiated E-RAB Release procedure (successful operation)
eNB
MME
E-RAB RELEASE INDICATION
Issue 01 (2011-09-30)
eRAN2.2 S1AP
3
eNB
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.1 Initial Context Setup procedure (successful operation)
MME
INITIAL CONTEXT SETUP REQUEST
INITIAL CONTEXT SETUP RESPONSE
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. 2. 3. 4. Attempts to execute the requested E-RAB configuration. Saves the UE Aggregate Maximum Bit Rate IE in the UE context and uses the received UE Aggregate Maximum Bit Rate IE. Saves the handover restriction list in the UE context. 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.
Issue 01 (2011-09-30)
eRAN2.2 S1AP
Figure 4.1 Initial Context Setup procedure (unsuccessful operation)
eNB INITIAL CONTEXT SETUP REQUEST
MME
INITIAL CONTEXT SETUP FAILURE
3.2 UE Context Release

The UE context can be released in either of the following modes:
eNodeB-initiated UE context release
eNB
MME
UE CONTEXT RELEASE REQUEST
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
eNB UE CONTEXT RELEASE COMMAND
MME
UE CONTEXT RELEASE COMPLETE
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.
eRAN2.2 S1AP
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.1 UE Context Modification procedure (successful operation)
eNB
MME
UE CONTEXT MODIFICATION REQUEST
UE CONTEXT MODIFICATION RESPONSE
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.2 UE Context Modification procedure (unsuccessful operation)
eNB
MME
UE CONTEXT MODIFICATION REQUEST
UE CONTEXT MODIFICATION FAILURE
If UE context modification fails, the eNodeB responds to the MME with a UE CONTEXT MODIFICATION FAILURE message that contains the Cause IE.
Issue 01 (2011-09-30)
10
eRAN2.2 S1AP
4
source eNB
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.1 Handover Preparation procedure (successful operation) MME HANDOVER REQUIRED 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 TS1 RELOCprep timer. 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 TS1 RELOCprep timer 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.
Issue 01 (2011-09-30)
11
eRAN2.2 S1AP
Figure 1.2 Handover Preparation procedure (unsuccessful operation) source eNB HANDOVER REQUIRED HANDOVER PREPARATION FAILURE MME
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.1 Hanover Resource Allocation procedure (successful operation) target eNB HANDOVER REQUEST HANDOVER REQUEST ACKNOWLEDGE MME
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.2 Hanover Resource Allocation procedure (unsuccessful operation) target eNB HANDOVER REQUEST HANDOVER FAILURE MME
Issue 01 (2011-09-30)
12
eRAN2.2 S1AP
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.1 Handover Notification procedure target eNB HANDOVER NOTIFY MME
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.1 Path 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.2 Path Switch Request procedure (unsuccessful operation)
eNB PATH SWITCH REQUEST PATH SWITCH REQUEST FAILURE
MME
If the handover fails on the EPC, the MME responds to the eNodeB with a PATH SWITCH
eRAN2.2 S1AP
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.1 Handover Cancelation procedure (successful operation)
Source eNB HANDOVER CANCEL HANDOVER CANCEL ACKNOWLEDGE
MME
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.1 eNodeB Status Transfer procedure eNB MME
eNB STATUS TRANSFER
Issue 01 (2011-09-30)
14
eRAN2.2 S1AP
4.7 MME Status Transfer

Figure 1.1 MME Status Transfer procedure eNB MME
MME STATUS TRANSFER
Issue 01 (2011-09-30)
15
eRAN2.2 S1AP
5
The purpose of this procedure is to enable the MME to page UEs. Figure 1.1 Paging procedure
Paging
eNB
MME PAGING
Issue 01 (2011-09-30)
16
eRAN2.2 S1AP
6
6.1 Initial UE Message
Figure 1.1 Initial UE Message procedure
NAS Transport
The purpose of this procedure is to carry UEMME signaling over the S1 interface. The NAS messages are transported in an IE of the INITIAL UE MESSAGE, DOWNLINK NAS TRANSPORT, or UPLINK NAS TRANSPORT message.
eNB
MME
INITIAL UE MESSAGE
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.
Issue 01 (2011-09-30)
17
eRAN2.2 S1AP
6.2 Downlink NAS Transport

Figure 1.1 Downlink NAS Transport procedure
eNB
MME
DOWNLINK NAS TRANSPORT
The MME sends a UE an NAS message through the eNodeB.
6.3 Uplink NAS Transport

Figure 1.1 Uplink NAS Transport procedure
eNB
MME
UPLINK NAS TRANSPORT
Issue 01 (2011-09-30)
18
eRAN2.2 S1AP
6.4 NAS Non Delivery Indication

Figure 1.1 NAs Non Delivery Indication procedure
eNB
MME
NAS NON DELIVERY INDICATION
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.
Issue 01 (2011-09-30)
19
eRAN2.2 S1AP
7
7.1 Reset
eNB
Management Procedures
The reset procedure can be initiated by either the MME or the E-UTRAN. MME-initiated reset procedure: Figure 1.1 MME-initiated Reset procedure (successful operation)
MME
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. E-UTRAN-initiated reset procedure:
Issue 01 (2011-09-30)
20
eRAN2.2 S1AP
Figure 1.2 E-UTRAN-initiated Reset procedure (successful operation)
eNB
MME
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.1 MME-initiated Error Indication procedure (successful operation)
eNB ERROR INDICATION
MME
Figure 1.2 eNodeB-initiated Error Indication procedure (successful operation)
eNB ERROR INDICATION
MME
An ERROR INDICATION message must contain a minimum of one Cause IE or Criticality Diagnostics IE.
eRAN2.2 S1AP
7.3 S1 Setup
Figure 1.1 S1 Setup procedure (successful operation)
eNB S1 SETUP REQUEST S1 SETUP RESPONSE
MME
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.2 S1 Setup procedure (unsuccessful operation)
eNB S1 SETUP REQUEST S1 SETUP FAILURE
MME
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.1 eNodeB Configuration Update procedure (successful operation) eNB ENB CONFIGURATION UPDATE ENB CONFIGURATION UPDATE ACKNOWLEDGE MME
Issue 01 (2011-09-30)
22
eRAN2.2 S1AP
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.2 eNodeB Configuration Update procedure (unsuccessful operation) eNB ENB CONFIGURATION UPDATE ENB CONFIGURATION UPDATE FAILURE MME
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.1 MME Configuration Update procedure (successful operation) eNB MME CONFIGURATION UPDATE MME CONFIGURATION UPDATE ACKNOWLEDGE MME
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 CONFIGURATION UPDATE FAILURE message.
Issue 01 (2011-09-30)
23
eRAN2.2 S1AP
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.1 Overload Start procedure
eNB
MME OVERLOAD START
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.1 Overload Stop procedure
eNB
MME OVERLOAD STOP
Issue 01 (2011-09-30)
24
eRAN2.2 S1AP
8
eNB
UE Capability Information Indication
The purpose of this procedure is to enable an eNodeB to provide UE capability information for the MME. Figure 1.1 UE Capability Information Indication procedure (successful operation)
MME
UE CAPABILITY INFO INDICATION
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.
Issue 01 (2011-09-30)
25
eRAN2.2 S1AP
9
eNB
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.1 eNodeB Direct Information Transfer procedure (successful operation) MME
ENB DIRECT INFORMATION TRANSFER
Issue 01 (2011-09-30)
26
eRAN2.2 S1AP
10
eNB
MME Direct Information Transfer
The MME sends an eNodeB a DIRECT INFORMATION TRANSFER message to initiate the procedure. Figure 1.1 MME Direct Information Transfer procedure (successful operation) MME
MME DIRECT INFORMATION TRANSFER
Issue 01 (2011-09-30)
27
eRAN2.2 S1AP
11
eNB
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.1 eNodeB Configuration Transfer procedure (successful operation) MME
ENB CONFIGURATION TRANSFER
Issue 01 (2011-09-30)
28
eRAN2.2 S1AP
12
eNB
MME Configuration Transfer
The purpose of this procedure is to transfer RAN configuration information from the MME to an eNodeB in unacknowledged mode. Figure 1.1 MME Configuration Transfer procedure (successful operation) MME
MME CONFIGURATION TRANSFER
Issue 01 (2011-09-30)
29

3-2 - S1ap

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

3-2 - S1ap

Încărcat de

Drepturi de autor:

Formate disponibile

Doc.

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

About This Document

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

5 Paging........................................................................................ 16 6 NAS Transport............................................................................. 17

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

12 MME Configuration Transfer

GTP-U UDP IP Data link layer Physical layer

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

12 MME Configuration Transfer

1.2 S1 Control Plane

SCTP IP Data link layer Physical layer

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

12 MME Configuration Transfer

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

12 MME Configuration Transfer

Successful Outcome Response Message

Unsuccessful Outcome Response Message

Write-Replace Warning Kill

WRITE-REPLACE WARNING REQUEST KILL REQUEST

WRITE-REPLACE WARNING RESPONSE KILL RESPONSE

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

12 MME Configuration Transfer

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

12 MME Configuration Transfer

E-RAB SETUP REQUEST

E-RAB SETUP RESPONSE

2.2 E-RAB Modify

12 MME Configuration Transfer

Figure 1.1 E-RAB Modify procedure (successful operation)

E-RAB MODIFY REQUEST

E-RAB MODIFY RESPONSE

2.3 E-RAB Release

MME-initiated E-RAB release

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

eNB E-RAB RELEASE COMMAND

E-RAB RELEASE RESPONSE

eNodeB-initiated E-RAB release

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

E-RAB RELEASE INDICATION

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

12 MME Configuration Transfer

3.1 Initial Context Setup

INITIAL CONTEXT SETUP REQUEST

INITIAL CONTEXT SETUP RESPONSE

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

12 MME Configuration Transfer

Figure 4.1 Initial Context Setup procedure (unsuccessful operation)

eNB INITIAL CONTEXT SETUP REQUEST

INITIAL CONTEXT SETUP FAILURE

3.2 UE Context Release

eNodeB-initiated UE context release

UE CONTEXT RELEASE REQUEST

MME-initiated UE Context Release procedure

eNB UE CONTEXT RELEASE COMMAND

UE CONTEXT RELEASE COMPLETE

12 MME Configuration Transfer