ETSI TS 129 276 V8.3.0 (2009-10)

Universal Mobile Telecommunications System (UMTS); LTE; Optimized Handover Procedures and Protocols between EUTRAN Access and cdma2000 HRPD Access (3GPP TS 29.276 version 8.3.0 Release 8)

RTS/TSGC-0429276v830

General Information

• Status: Published
• Publication Date: 07-Oct-2009
• Technical Committee: 3GPP CT 4 - MAP/CAMEL/GTP/BCH/SS/TrFO/IMS/GUP/WLAN (formely CN4)
• Current Stage: 12 - Completion
• Due Date: 13-Oct-2009
• Completion Date: 08-Oct-2009

Standards Content (Sample)

ETSI TS 129 276 V8.3.0 (2009-10)
Technical Specification


Universal Mobile Telecommunications System (UMTS);
LTE;
Optimized Handover Procedures and Protocols between
EUTRAN Access and cdma2000 HRPD Access
(3GPP TS 29.276 version 8.3.0 Release 8)

---------------------- Page: 1 ----------------------
3GPP TS 29.276 version 8.3.0 Release 8 1 ETSI TS 129 276 V8.3.0 (2009-10)



Reference
RTS/TSGC-0429276v830
Keywords
LTE, UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2009.
All rights reserved.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TS 29.276 version 8.3.0 Release 8 2 ETSI TS 129 276 V8.3.0 (2009-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
ETSI

---------------------- Page: 3 ----------------------
3GPP TS 29.276 version 8.3.0 Release 8 3 ETSI TS 129 276 V8.3.0 (2009-10)
Contents
Intellectual Property Rights . 2
Foreword . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 General . 7
5 Transmission Order and Bit Definitions. 8
6 S101 Message Header . 8
6.1 Introduction . 8
6.2 S101 Message Header . 8
7 S101 Messages and Message Formats . 9
7.1 Introduction . 9
7.2 Path Management Messages . 9
7.2.1 Introduction. 9
7.2.2 Echo Request message . 10
7.2.3 Echo Response message . 10
7.2.4 Version Not Supported message . 10
7.3 S101 Messages . 10
7.3.1 Introduction. 10
7.3.2 Direct Transfer Request message . 10
7.3.3 Direct Transfer Response message . 11
7.3.4 Notification Request message . 12
7.3.5 Notification Response message . 12
7.4 Reliable Delivery of Signalling Messages . 13
7.5 Information Elements . 13
7.5.1 Information Element Assignments . 13
7.5.2 Session ID . 15
7.5.3 Cause . 15
7.5.4 Recovery . 15
7.5.5 HRPD Sector ID . 16
7.5.6 S101 Transparent Container . 16
7.5.7 Handover Indicator . 16
7.5.8 Private Extension . 17
7.5.9 PDN GW PMIP GRE Tunnel Info . 17
7.5.10 S103 GRE Tunnel Info . 17
7.5.11 S103 HSGW IP Address . 18
7.5.12 Tracking Area Identity . 18
8 Path Protocols . 18
9 Error Handling . 18
9.1 Protocol Errors . 18
9.2 Path Failure . 18
9.3 Restoration and Recovery . 18
10 Security provided to Communication over the S101 Interface . 19
11 IP - The Networking Technology used by S101 . 19
11.1 IP Version . 19
11.2 IP Fragmentation . 19
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 29.276 version 8.3.0 Release 8 4 ETSI TS 129 276 V8.3.0 (2009-10)
12 S101 Parameters . 19
12.1 General . 19
12.2 Timers . 19
12.3 Others . 19
13 S103 Interface Specification . 19
13.1 Introduction . 19
13.2 S103 Interface . 19
Annex A (informative): Change history . 20
History . 21

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 29.276 version 8.3.0 Release 8 5 ETSI TS 129 276 V8.3.0 (2009-10)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI

---------------------- Page: 6 ----------------------
3GPP TS 29.276 version 8.3.0 Release 8 6 ETSI TS 129 276 V8.3.0 (2009-10)
1 Scope
The present document specifies the stage 3 of the Evolved Packet System S101 interface between the MME and the
HRPD Access Network. The S101 interface supports procedures for Pre-Registration, Session Maintenance and Active
handoffs between E-UTRAN and HRPD networks.
It also specifies the S103 interface between the Serving GW and HRPD PDSN. This User Plane interface is used to
forward DL data to minimize packet losses in mobility from E-UTRAN to HRPD. Signalling procedures on the S101
interface are used to set up tunnels on the S103 interface.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses".
[3] IETF RFC 3232: "Assigned Numbers".
[4] IETF RFC 2784: "Generic Routing Encapsulation (GRE)".
[5] IETF RFC 2890: "Key and Sequence Number Extensions to GRE".
[6] 3GPP TS 29.274: "Evolved GPRS Tunnelling Protocol for Control Plane (GTPv2-C); Stage 3".
[7] 3GPP2 C.S0024- A v3.0: "cdma2000 High Rate Packet Data Air Interface Specification".
[8] 3GPP TS 23.007: "Restoration procedures".
[9] 3GPP2 C.S0087-0: "E-UTRAN - HRPD and CDMA2000 1x Connectivity and Interworking: Air
Interface Aspects".
[10] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage
3".
[11] 3GPP TS 33.402: "3GPP System Architecture Evolution: Security Architecture".
[12] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access (E-UTRA) ; S1 Application
Protocol (S1AP)".
[13] 3GPP TS 24.008: " Mobile radio interface Layer 3 specification; Core network protocols; Stage
3".
[14] 3GPP TS 29.280: "3GPP EPS Sv interface (MME to MSC) for SRVCC".
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 29.276 version 8.3.0 Release 8 7 ETSI TS 129 276 V8.3.0 (2009-10)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
HRPD Access: Combination of the eAN - PCF of the cdma2000 access
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].
AN Access Network
eAN enhanced AN
eGTP enhanced Gateway Tunnelling Protocol
eNodeB enhanced Node B
E-UTRAN Enhanced UMTS Terrestial Radio Access Network
GRE Generic Routing Encapsulation
GW Gateway
HO HandOver
HRPD High Rate Packet Data
HSGW HRPD Serving GateWay
IMSI International Mobile Station Identity
IP Internet Protocol
MME Mobility Management Entity
PCF Packet Control Function
PDN Packet data Network
PDSN Packet Data Serving Node
PMIP Proxy Mobile IP
TEID Tunnel End Point Identifier
UDP User Datagram Protocol
VS Vendor Specific
4 General
The S101 reference point is defined between the MME and the HRPD access, enabling interactions between E-UTRAN
Access and cdma2000 HRPD Access. The S101 interface is required to perform procedures related to optimise HO
between the E-UTRAN Access and cdma2000 HRPD Access to allow for pre-registration and handover signalling with
the target system.
The S103 interface is defined between the Serving GW and HRPD PDSN and supports the forwarding of DL data
during mobility from E-UTRAN to HRPD. Signalling procedures on the S101 interface are used to set up tunnels on the
S103 interface.
The requirements for these interfaces are defined in 3GPP TS 23.402 [2].
The protocol stack used for the S101 interface shall be based on GTPv2-C, see 3GPP TS 29.274 [6] Figure 4.3.
The UDP header and port numbers definitions shall be as defined in GTPv2-C, see 3GPP TS 29.274 [6] section 4.3.1.
The IP header and IP addresses definitions shall be as defined in GTPv2-C, see 3GPP TS 29.274 [6] section 4.3.2.
Layer 1 and Layer 2 requirements shall as defined in GTPv2-C, see 3GPP TS 29.274 [6] sections 4.3.3 and 4.3.4.
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 29.276 version 8.3.0 Release 8 8 ETSI TS 129 276 V8.3.0 (2009-10)
5 Transmission Order and Bit Definitions
Transmission Order and Bit Definitions shall be as defined in GTPv2-C, see 3GPP TS 29.274 [6] section 4.4.
6 S101 Message Header
6.1 Introduction
The S101 Message Header is conformant to the GTPv2-C Message Header, see 3GPP TS 29.274 [6] section 5. All S101
messages shall have a header that includes specific parameters. The following list of header parameters are defined for
the S101 interface:
- Version
- Flags (T = TEID Included)
- Message Type
- Length
6.2 S101 Message Header
The S101 header is a variable length header. The minimum length of the S101 header is eight octets. Space has been
reserved for four flags that may be used in the future to signal the presence of additional optional header fields or
utilities.
- Bit 4 (the T bit) may be set to one to indicate that a TEID is present in the header, as per 3GPP TS 29.274 [6].
The T bit shall be set to zero to indicate that the TEID field shall not be present in any message sent on the S101
interface.
If the header fields do not occupy a full eight octets, then spare octets shall be added after the last valid field in the S101
header to complete eight octets. Spare octets and bits shall be set to zero.
Always present fields:
- Version field: This field is used to determine the version of the S101 protocol. The version number shall be set
to '010'.
- Message Type: This field indicates the type of S101 message. The valid values of the message type are defined
in clause 7.1. Note that values chosen for Message Type shall be coordinated with and shall not overlap the
Message Type values chosen for GTPv2-C in 3GPP TS 29.274 [6].
- Length: This field indicates the length in octets of the payload, i.e. the rest of the packet following the
mandatory part of the S101 header (that is the first 4 octets).
- Sequence Number: This field enables the target system to identify any missing receipt of messages and is used
also for acknowledgement of messages.
ETSI

---------------------- Page: 9 ----------------------
3GPP TS 29.276 version 8.3.0 Release 8 9 ETSI TS 129 276 V8.3.0 (2009-10)

 Bits
Octets 8 7 6 5 4 3 2 1
1 Version=010 (*) T=0 (*) (*) (*)
2 Message Type
st
3 Length (1 Octet)
nd
4 Length (2 Octet)
st
5 Sequence Number (1 Octet)
nd
6 Sequence Number (2 Octet)
rd
7 Sequence Number (3 Octet)
8 Spare

NOTE 0: (*) This bit is a spare bit. It shall be sent as '0'. The receiver shall not evaluate this bit.

Figure 6.2-1: Layout of the S101 Message Header
7 S101 Messages and Message Formats
7.1 Introduction
This section is divided into path management which defines the general messages for the pre-configured tunnel and a
section for the specific messages used for information transfer over the control plane.
Table 7.1 specifies GTPv2-C message types that are used across the S101 interface.
Table 7.1: Message types for S101
Message Type Message Reference
value (Decimal)
0 Reserved 3GPP TS 29.274 [6]
1 Echo Request 3GPP TS 29.274 [6]
2 Echo Response 3GPP TS 29.274 [6]
3 Version Not Supported Indication 3GPP TS 29.274 [6]
4 Direct Transfer Request message 7.3.2
5 Direct Transfer Response message 7.3.3
6 Notification Request message 7.3.4
7 Notification Response message 7.3.5
8-24 For future S101 interface use
25-31 Reserved for Sv interface 3GPP TS 29.280 [14]
32-255 Reserved for GTPv2-C spec 3GPP TS 29.274 [6]

7.2 Path Management Messages
7.2.1 Introduction
The path from the MME to the non-3GPP Access Network operationally requires management capabilities. The
following GTPv2-C messages support path management for the S101 interface:
- Echo Request
- Echo Response
- Version Not Supported
These messages are defined for GTPv2-C and the handling and definition shall also be as defined in GTPv2-C, see
3GPP TS 29.274 [6].
ETSI

---------------------- Page: 10 ----------------------
3GPP TS 29.276 version 8.3.0 Release 8 10 ETSI TS 129 276 V8.3.0 (2009-10)
7.2.2 Echo Request message
An MME or an HRPD access node may send an Echo Request to find out if the peer HRPD access node or MME is
alive (see section Path Failure). When and how often an Echo Request message may be sent is implementation specific
but an Echo Request shall not be sent more often than every 60 s on each path.
An MME or an HRPD access node shall be prepared to receive an Echo Request at any time and it shall reply with an
Echo Response. The optional Private Extension contains vendor or operator specific information.
3GPP TS 29.274 [6] specifies the information elements included in the Echo Request message.

7.2.3 Echo Response message
The message shall be sent as a response to a received Echo Request.
3GPP TS 29.274 [6] specifies the information elements included in the Echo Response message.
The Recovery information element contains the local Restart Counter (see section Restoration and Recovery) value for
the node that sends the Echo Response message.
The MME or an HRPD access node that receives an Echo Response from a peer MME or an HRPD access node shall
compare the Restart Counter value received with the previous Restart Counter value stored for that peer MME or HRPD
access node. If no previous value was stored, the Restart Counter value received in the Echo Response shall be stored
for the peer MME or HRPD access node.
The value of a Restart Counter previously stored for a peer MME or HRPD access node may differ from the Restart
Counter value received in the Echo Response from that peer MME or HRPD access node. In this case, the MME or
HRPD access node that sent the Echo Response shall be considered as restarted by the MME or HRPD access node that
received the Echo Response. The new Restart Counter value received shall be stored by the receiving entity, replacing
the value previously stored for the sending MME or HRPD access node.
The optional Private Extension contains vendor or operator specific information.
7.2.4 Version Not Supported message
This message contains only the S101 header and indicates the latest S101 version that the MME or HRPD access node
entity on the identified UDP/IP address can support (see subclause 6.2).
3GPP TS 29.274 [6] specifies the detailed handling and information elements included in the Version Not Supported
message.
7.3 S101 Messages
7.3.1 Introduction
The following messages are used to support interworking between the MME and the non-3GPP access network:
- Direct Transfer Request
- Direct Transfer Response
- Notification Request
- Notification Response
7.3.2 Direct Transfer Request message
A Direct Transfer Request shall be sent from an MME or HRPD access node to transport an HRPD or an E-UTRAN
message to the peer HRPD access node or MME.
ETSI

---------------------- Page: 11 ----------------------
3GPP TS 29.276 version 8.3.0 Release 8 11 ETSI TS 129 276 V8.3.0 (2009-10)
Table 7.3.2-1 specifies the information elements included in the Direct Transfer message.
Table 7.3.2-1: Information Elements in a Direct Transfer Request
Information elements Presence Reference Instance
Requirement
Session ID Mandatory 7.5.2 0
HRPD Sector ID Conditional 7.5.5 0
S101 Transparent Container Mandatory 7.5.6 0
PDN GW PMIP GRE Tunnel Info Conditional 7.5.9 0
S103 GRE Tunnel Info Conditional 7.5.10 0
S103 HSGW IP Address Conditional 7.5.11 0
Handover Indicator Conditional 7.5.7 0
Tracking Area Identity Conditional 7.5.12 0
Recovery Conditional 7.5.4 0
Private Extension Optional 7.5.8 VS

The HRPD Sector ID parameter shall be included if this message is being sent from the MME to the HRPD access node
in case of handover from E-UTRAN to HRPD.
If an HRPD message is being tunnelled between an MME and an HRPD access node, the S101 Transparent Container
shall contain the HRPD message.
The Tracking Area Identity parameter shall be included if this message is being sent from the HRPD access node to the
MME in case of handover from HRPD to E-UTRAN.
If an E-UTRAN message is being tunnelled between an MME and an HRPD access node, the S101 Transparent
Container shall contain the E-UTRAN message.
If the Direct Transfer Request message is sent from the MME to the HRPD AN and the MME has the PDN GW IP
Address and the PDN GW GRE Key for a PDN Connection, the PDN GW PMIP GRE Tunnel Info IE shall be included
when the MME receives CDMA2000 HO Required Indication from the eNodeB, see 3GPP TS 36.413 [12]. The PDN
GW PMIP GRE Tunnel Info shall include the PDN Identity and the PDN GW GRE Key for the PDN connection. The
S103 HSGW IP Address IE shall also be included in this case in the message but only one occurrence. The Handover
Indicator shall indicate Handover Required in this case. For each PDN GW PMIP GRE Tunnel of the UE, there shall be
a PDN GW PMIP GRE Tunnel Info Information Element included in the message.
If the Handover Indicator IE indicates HO Ready during optimized active handover from E-UTRAN to HRPD, the
S101 Transparent Container contains the HRPD message (=HRPD TCA message). If data forwarding applies, S103
GRE Tunnel Info field shall be included, which includes the PDN ID, HSGW Address and the HSGW GRE Key for a
PDN connection. For each PDN connection of the UE which requires data forwarding towards the HSGW, there will be
a S103 GRE Tunnel Info information element included in the message.
The Handover Indicator parameter shall be included, if the encapsulated message being carried will cause the UE to
leave the source system and tune its radio to the target system. It shall also be included for the case of LTE to HRPD
handover, if a Direct Transfer Request message is sent from the MME to the HRPD AN, the MME shall include a
Handover Required indication in the Handover Indicator IE, if a Handover Required was received by the MME from
the eNodeB.
If the node is contacting its peer for the first time or if the node has restarted recently and the new Restart Counter value
has not yet been indicated to the peer, the Recovery IE shall be included.
7.3.3 Direct Transfer Response message
The message shall be sent from an MME or HRPD access node to its peer HRPD access node or MME as a response to
a Direct Transfer Request.
Table 7.3.3-1 specifies the information elements included in the Direct Transfer Response message.
ETSI

---------------------- Page: 12 ----------------------
3GPP TS 29.276 version 8.3.0 Release 8 12 ETSI TS 129 276 V8.3.0 (2009-10)
Table 7.3.3-1: Information Elements in a Direct Transfer Response message
Information elements Pres
...