3GPP TS 36.413 V8.1.

0 (2008-03)
Technical Specification

3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 8)

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.

Release 8

2

3GPP TS 36.413 V8.1.0 (2008-03)

Keywords
UMTS, radio

3GPP Postal address

3GPP support office address
650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Internet
http://www.3gpp.org

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.
© 2008, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved.

3GPP

Release 8

3

3GPP TS 36.413 V8.1.0 (2008-03)

Contents
Foreword ............................................................................................................................................................8 1 2 3
3.1 3.2 3.3

Scope ........................................................................................................................................................9 References ................................................................................................................................................9 Definitions, symbols and abbreviations ...................................................................................................9
Definitions ......................................................................................................................................................... 9 Symbols ........................................................................................................................................................... 10 Abbreviations................................................................................................................................................... 11

4
4.1 4.2 4.3

General ...................................................................................................................................................11
Procedure Specification Principles .................................................................................................................. 11 Forwards and Backwards Compatibility.......................................................................................................... 11 Specification Notations.................................................................................................................................... 11

5 6 7 8

S1AP Services ........................................................................................................................................13 Services Expected from Signalling Transport........................................................................................14 Functions of S1AP .................................................................................................................................15 S1AP Procedures....................................................................................................................................16
List of S1AP Elementary procedures............................................................................................................... 16 SAE Bearer Management procedures .............................................................................................................. 17 SAE Bearer Setup ...................................................................................................................................... 17 General ................................................................................................................................................. 17 Successful Operation ............................................................................................................................ 17 Unsuccessful Operation........................................................................................................................ 18 Abnormal Conditions ........................................................................................................................... 18 SAE Bearer Modify.................................................................................................................................... 18 General ................................................................................................................................................. 18 Successful Operation ............................................................................................................................ 18 Unsuccessful Operation........................................................................................................................ 19 Abnormal Conditions ........................................................................................................................... 19 SAE Bearer Release ................................................................................................................................... 19 General ................................................................................................................................................. 19 Successful Operation ............................................................................................................................ 20 SAE Bearer Release - MME initiated ............................................................................................. 20 SAE Bearer Release Request - eNB initiated.................................................................................. 21 Abnormal Conditions ........................................................................................................................... 21 Context Management procedures .................................................................................................................... 21 Initial Context Setup .................................................................................................................................. 21 General ................................................................................................................................................ 21 Successful Operation ............................................................................................................................ 22 Unsuccessful Operation........................................................................................................................ 23 Abnormal Conditions ........................................................................................................................... 23 UE Context Release Request - eNB initiated ............................................................................................. 23 General ................................................................................................................................................. 23 Successful Operation ............................................................................................................................ 23 UE Context Release (MME initiated) ........................................................................................................ 24 General ................................................................................................................................................. 24 Successful Operation ............................................................................................................................ 24 UE Context Modification ........................................................................................................................... 24 General ................................................................................................................................................ 24 Successful Operation ............................................................................................................................ 25 Unsuccessful Operation........................................................................................................................ 25 Handover Signalling ........................................................................................................................................ 25 Handover Preparation................................................................................................................................ 25 General ................................................................................................................................................. 25 Successful Operation ............................................................................................................................ 26

8.1 8.2 8.2.1 8.2.1.1 8.2.1.2 8.2.1.3 8.2.1.4 8.2.2 8.2.2.1 8.2.2.2 8.2.2.3 8.2.2.4 8.2.3 8.2.3.1 8.2.3.2 8.2.3.2.1 8.2.3.2.2 8.2.3.3 8.3 8.3.1 8.3.1.1 8.3.1.2 8.3.1.3 8.3.1.4 8.3.2 8.3.2.1 8.3.2.2 8.3.3 8.3.3.1 8.3.3.2 8.3.4 8.3.4.1 8.3.4.2 8.3.4.3 8.4 8.4.1 8.4.1.1 8.4.1.2

3GPP

.................................................................7...................................................7...................................4.....................1......................................7..6.....................................................................................2 Successful Operation .........2 Successful Operation ........ 27 8.............................2.......................................................................4...............................4...............................................................................3................................................4........................................Release 8 4 3GPP TS 36............................. 28 8................4 Abnormal Conditions ...4......... 29 8..............4.......................................................... 38 8................4..................................................2... 30 8....................................1 Initial UE Message ................................... 32 8......................5 Handover Cancellation..4........................................................2.............................................................3 Unsuccessful Operation........ 33 8... 31 8........................4 Abnormal Conditions ................................................ 30 8...................................................................5.......................3 S1 Setup .....3 Abnormal Conditions .......................4...........................1 General ....................4.........................................................................1.......................1................................................3 Abnormal Conditions ...........................1.................................. 31 8................................................................... 32 8.................. 27 8.........................................2 Successful Operation ..................................................................3.....2......................................2 Successful Operation .............................6.......................................................................................7............................................. 37 8.......................................................7.............1 General ................................... 29 8....................... 31 8.............................4.....................................................................3 Unsuccessful Operation........ 32 8..........................................4................................................................................................2.6 NAS transport ....5...................................................7...............................................1 General ........................ 28 8................................................4.............4............................................................ 37 8..4..................................................2.................. 38 3GPP .................................4..................1 General .................5.... 33 8.................................................................................4........... 31 8..........2 Successful Operation........................................ 35 8.......................................................... 32 8.................................4 Abnormal Conditions .......2....................................................4.....................................4..........1 General ..............................................5 Paging ....... 28 8................................................................................6.................................... 32 8..................................................1.................... 37 8..............2 Successful Operation ..3 Crossing of Reset Messages.7....................................................................................................................................................3 Unsuccessful Operation..............................3 Unsuccessful Operation...........................7................4................ 27 8...................6......................... 38 8..............................................................................6.........................4....3 Unsuccessful Operation...........................2 Successful Operation ................4..............................7 MME Status Transfer .................................5................................................................. 33 8................................................................... 30 8........4.......................6..6 eNB Status Transfer .......................................................................................2 Abnormal Condition at the E-UTRAN ........7...........................................4 Abnormal Conditions .........................................7.............................................................................. 29 8...........7....3..............................................2 Successful Operation .............................7......... 30 8...................... 35 8....................................................6.........................................1 General ...3 Unsuccessful Operation................................................................................................7...............4 NAS NON DELIVERY INDICATION ................................ 35 8..................... 30 8............... 31 8...................................6.....4..........................3 Unsuccessful Operation.......................................... 37 8...............................................3 Unsuccessful Operation....... 35 8............................................7........................................ 36 8.................................................4 Abnormal Conditions ..........1 Abnormal Condition at the CN ............................................................................................. 35 8.........7 Management procedures ..7....................................................................................... 34 8..........................................7..............................................................3 UPLINK NAS TRANSPORT ...................................................................................................................4........2.3.............................5....... 35 8....... 33 8........................ 33 8......... 31 8................................................................. 29 8................1 General ......................4...........................2 Successful Operations ........................ 27 8...7................................................................. 28 8......................................................................6............... 37 8.........................................................3....................1......................................................... 33 8...........................................................4.......................1 General ..5......... 33 8..........................................3..........................................5.........................................2............................................................2.........................................................2 Error Indication .......................................................4..3 Abnormal Conditions ..................... 32 8...............................................6.......1 Reset.........................................4..................1 General ............... 37 8...................7.........................................7................................................................................... 29 8......1 Reset Procedure Initiated from the MME ....0 (2008-03) 8...................................................................2 Reset Procedure Initiated from the E-UTRAN ...............................................2 DOWNLINK NAS TRANSPORT .4 Abnormal Conditions ..............................................4...................... 26 8............................................. 28 8.............4................................................1 General .....................4............................1................. 35 8.............................2...2.............................................................................................................1.............................................................................4................................................................................ 31 8.......................................................................2 Successful Operation .........................................4 Path Switch Request...........6....................2 Successful Operation .4 Abnormal Conditions ...............1.................................3.......................4 Abnormal Conditions .......................................................................................................................................................................................5......................................1......................................3 Handover Notification... 38 8.........................2....................1...............................................2 Handover Resource Allocation ...................413 V8............................................................4.....7...........6............... 30 8...................................................................................................1 General ................. 37 8...... 35 8..................3.............................................4............................

....................................................... 57 9............................................................................................................... 41 9...................................................................1.. 50 9................................... 51 9.......................................... 39 S1 CDMA2000 Tunneling Procedures ......... 58 9...............................................1...................................4 8......................................................................................................................................7....14 MME STATUS TRANSFER .........................................1.....5...................................................................................................................... 55 9.6 PAGING............................................................................................5.................................2 DOWNLINK NAS TRANSPORT .......1....................................9 UE CONTEXT MODIFICATION RESPONSE ............................................................................................................................ 62 3GPP ...................................................................................... 62 9...4.........8............................1 Presence.........5...6 SAE BEARER RELEASE COMPLETE ..................1... 41 9.........................1...................7...............................9 PATH SWITCH REQUEST ACKNOWLEDGE.......................1....................... 59 9...................1.......1....1.............................. 61 9..................................................................... 39 Uplink S1 CDMA2000 Tunneling.................................................................................................. 41 9..4 Context Management Messages..........................................................................................3 Range.3....7 SAE BEARER RELEASE REQUEST ............................................................................................................................................. 43 9...............................................................4......................................................................1........5.................. 41 9..1 8.....................2..................................................................4 Assigned Criticality .....7.........9 8.....................5..........8..............................................................413 V8.....3............. 48 9.....................1.1.................................11 HANDOVER CANCEL....5...................................................................5.............................................................................................................................................................1....... 61 9................................................................................................................ 41 9.........13 eNB STATUS TRANSFER ........................................... 45 9...........5....................................................... 62 9..........................3..................1......1.......................................................................................................4...........1........7..............................1.........2 INITIAL CONTEXT SETUP RESPONSE.......3 UPLINK NAS TRANSPORT .........1....................Release 8 5 3GPP TS 36....................41 9...1............................................................1.......................1 RESET........................12 HANDOVER CANCEL ACKNOWLEDGE....................2 Unsuccessful Operation...................................2 8...........................................................................................................................5 UE CONTEXT RELEASE REQUEST.........1..1.....................................................................................................................................................4 NAS NON DELIVERY INDICATION ...............................................5....................1 Message Functional Definition and Content...............................................8......................................................................3.....1..............................................................................3 8.1............ 50 9........... 49 9...................................10 UE CONTEXT MODIFICATION FAILURE ..........................................3........8......................7 HANDOVER NOTIFY ........................... 40 UE Capability Info Indication.......................................................................................................1 HANDOVER REQUIRED........... 39 General ........................................................5.........................2 SAE BEARER SETUP RESPONSE........................1..............4..............................1 8..1 SAE BEARER SETUP REQUEST..................4....... 44 9...................................... 40 General ........................3 HANDOVER PREPARATION FAILURE.......................2 Criticality.......................1................ 51 9..................... 57 9......5.........................................................8.............................1 General ....1.......4 HANDOVER REQUEST......................................................................................7...........................................4 INITIAL CONTEXT SETUP FAILURE ...................................................................................................................................................... 58 9.......8 8.....................7 UE CONTEXT RELEASE COMPLETE.......2 HANDOVER COMMAND ...1...............................8 Management messages..............1......5........1............................4.......... 48 9.....5 Handover Signalling Messages ....................................... 56 9.....4 8.............................................8 UE CONTEXT MODIFICATION REQUEST ..........1..... 50 9.....3...............1.....................................9................................................................................................................................. 39 Successful Operations . 57 9.................................. 50 9.................................................................1..............7............................................................. 41 9.........................5 HANDOVER REQUEST ACKNOWLEDGE .....1...................................... 50 9.............5............................................6 UE CONTEXT RELEASE COMMAND...........................................1................................4............................................................. 61 9...............2......1................................. 42 9....3 8................1...............5......2 8.................1. 57 9..................1 8.............................................. 61 9..................1.................................. 49 9.....................3..............................4 SAE BEARER MODIFY RESPONSE ........1...............1.................3.....................................2 Message Contents.....................8.................................................1.............................................. 52 9.................................. 56 9..6 HANDOVER FAILURE.................................. 39 Downlink S1 CDMA2000 Tunneling...2...........................................................4....... 41 9...................5 SAE BEARER RELEASE COMMAND ..2........................................1.........................................1............... 46 9.........................................................4..........................................7 NAS Transport Messages...............1...................................................1......................1............................................10 PATH SWITCH REQUEST FAILURE...3 SAE BEARER MODIFY REQUEST ..............................................................2...... 38 Abnormal Conditions .............. 53 9................................................................ 48 9..............................................1 INITIAL UE MESSAGE.......................... 49 9................................... 40 9 Elements for S1AP Communication .8........3 SAE Bearer Management Messages ............1 INITIAL CONTEXT SETUP REQUEST.................... 47 9.8 PATH SWITCH REQUEST ................................................. 53 9............... 61 9....................................... 39 Unsuccessful Operation............3...... 40 Successful Operation..................9.............2............................................. 40 Abnormal Conditions ........ 42 9.........................................0 (2008-03) 8.....

..........................................1............................................................................................8...................................................................................................Release 8 6 3GPP TS 36........... 64 9..............................1.........................2 UPLINK S1 CDMA2000 TUNNELING ...................... 68 9.2................................................... 81 9.........1..........................................1.............................................24 CDMA2000 RAT Type .............1..............7 Source eNB to Target eNB Transparent Container ....1 DOWNLINK S1 CDMA2000 TUNNELING ................5 NAS-PDU.14 DL Forwarding ..............................3..... 79 9.......2.............................................. 83 9.....................3....................15 SAE Bearer Level QoS Parameters .........2.......................1.................................................................................... 77 9...26 Security Information.......2........................... 66 9...1...........................................2..................3 Message and Information Element Abstract Syntax (with ASN........................ 64 9............................................................................................................................3....................5 S1 SETUP RESPONSE. 82 9...................................3 Cause ........1............. 71 9...........2...2 GTP-TEID ....................................................2..............................................................21 Criticality Diagnostics ........................................1......................................................... 71 9.3.................25 CDMA2000 Sector ID.................... 77 9........................3.................................... 69 9.....................................................................................................0 (2008-03) 9.......0 General ................. 84 3GPP ..9.... 62 9.....10 UE Identity Index value............................................................................................................................ 65 9................1......................................................................12 MMEC..2.................................. 81 9..............................10 Target RNC to Source RNC Transparent Container................. 80 9............... 77 9..................................................413 V8...................................1..........................................................................................................2........... 73 9.........................................2..................................................3..................................9.....................................................16 Paging DRX........1..........3....8............................................................................................1.......................1...................................................................................................................... 79 9....................................................................................2..............................2 RESET ACKNOWLEDGE......... 64 9...........................................................................................................2..1.................3 MME UE S1AP ID.............................1............................................ 65 9....2....................................................2......................................................1 Usage of private message mechanism for non-standard use ..................................1....... 72 9.................2 Elementary Procedure Definitions ........13 Handover Type .....................................1) .............. 74 9.................. 76 9..................................................2.........2.......6 Target ID ..................................................................2.............................................................. 72 9..................................................... 64 9........................................................................3.........2..............................................................................................................................1.......2 RAC...........................................................................3 NAS Related IEs .2................2....................2.. 74 9................................................ 63 9..2 SAE Bearer ID.................. 71 9........................2.....9 Source RNC to Target RNC Transparent Container..........1............2.. 75 9............... 70 9.2.........2..3............1..............................................3........................................2 Information Element Definitions .............. 78 9.............................................................................27 UE Radio Capability.......................................8....... 81 9....2......................................................4 Trace activation .......................................1........................................1.............................1 Transport Layer Address .....2....... 77 9. 80 9...............................................3 ERROR INDICATION .............1............................6 S1 SETUP FAILURE......... 64 9..........9 S1 CDMA2000 Tunneling Messages..................... 65 9............................19 SAE Bearer Bit Rate......................1......................2........................................................12 Target BSS to Source BSS Transparent Container.......... 78 9..................................................................................5 Source ID......1 LAI ........................... 72 9.......23 CDMA2000-PDU....................2...........................................2....................................................................................................................................................................................... 79 9...2......2.............10 UE CAPABILITY INFO INDICATION ............................ 71 9............1........2.......2....................................................3.................................................13 UE Paging Identity ..............................3....................6 S-TMSI...........................................................................................................2 Transport Network Layer Related IEs............1...................................1.............................1...8 Target eNB to Source eNB Transparent Container .......................... 73 9...........17 Paging Cause ..................2...............................................1 Message Type.....7 TAI ...........4 S1 SETUP REQUEST.........8....20 Aggregate Maximum Bit Rate...................................2.................................................18 SAE Bearer Type.................................................................................................. 73 9........................................2......11 IMSI................ 79 9.....1. 77 9.................................2.......2........................................................2............... 76 9........................................ 78 9................. 77 9......................................................2........................................................... 79 9...............................................2....................................................................................................................................................... 62 9......1 Radio Network Layer Related IEs.....1.......................................0 General .2...............................1..............................................1........... 70 9.....................1.................................................2................................................3..................................................................................................................................................11 Source BSS to Target BSS Transparent Container.................................................................................................2............................................3........................2.........................3......2........................................3....................................1....... 71 9... 83 9......................................................................................................................1.........2...........2................................................................ 66 9.............................................................3..............................................1.............8................................... 80 9..............................................................2......... 78 9................................ 83 9...................................... 65 9.........................................................3......15 Direct Forwarding Path Availability ................................ 63 9................................................... 72 9.......9 GUMMEI ...22 Handover Restriction List.....................................................................................................................................1.........14 Extended RNC-ID ...............4 eNB UE S1AP ID..8 PLMN Identity.................................

............................................................................................................................................. 147 10...........................3 9..................................6 9....................... 142 Timers ...............................................................................................................1.3.....................3.................................................3..... 143 10...... 143 10....................................................................... 142 10 Handling of Unknown..2 Transfer Syntax Error .......................................3..............................................................3............................................................................................................................. 145 10...... 122 Common Definitions........................6 Handling of AP ID........ 146 10................................................................3........................................................3.................................. 138 Message Transfer Syntax............................................................................ 145 10......................4...........................................4.........................................5 9.....................................3 Presence Information ............................................................................................. 134 Constant Definitions.. 143 10..................... 134 Container Definitions ...............................................1A Type of Message.........................Release 8 7 3GPP TS 36...........3................................................................................................................................................................3..........6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present........................3........413 V8. 145 10............................................................ Unforeseen and Erroneous Protocol Data ........3....................... 148 10.............3.............................5 PDU Definitions..............................................2 IEs other than the Procedure Code and Type of Message ....................... 144 10....... 148 10...............................3................................................................................ 144 10...............................................................0 (2008-03) 9..........150 3GPP ........................................................................................................4 Not comprehended IE/IE group ..............7 9........................................................................5 Missing IE or IE group............................................................................................... 149 Annex A (informative): Change history .............................................................................................4 9................4 9...........3 Abstract Syntax Error ...................................................4.............................................................................................. 145 10...1 General ..................................................................... 143 10.............................................4 Logical Error..........................................143 10......................................................................................1 General..........................................5 Exceptions........................................................3............................ 92 Information Element Definitions.................................1 Procedure Code ..2 Criticality Information.....................................................

i. 3 or greater indicates TSG approved document under change control.z where: x the first digit: 1 presented to TSG for information. updates. corrections.0 (2008-03) Foreword This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). 3GPP .1.Release 8 8 3GPP TS 36.413 V8. 2 presented to TSG for approval.y. 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. technical enhancements. y the second digit is incremented for all changes of substance. 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.e. etc. z the third digit is incremented when editorial only changes have been incorporated in the document.

413 V8. Unless otherwise stated by the restrictions.1): Specification of basic notation". A term defined in the present document takes precedence over the definition of the same term.Abstract Syntax Notation One (ASN.691 (07/2002): "Information technology . a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. The S1 Application Protocol (S1AP) supports the functions of S1 interface by signalling procedures defined in this document.) or non-specific. edition number.Abstract Syntax Notation One (ASN. S1AP is developed in accordance to the general principles stated in [2] and [3]. in TR 21.0 (2008-03) 1 Scope The present document specifies the E-UTRAN radio network layer signalling protocol for the S1 interface. Class 2: Elementary Procedures without response. 2 References • References are either specific (identified by date of publication.1.905 [1]. constitute provisions of the present document. • For a specific reference. it is described under the relevant EP description.1 encoding rules: Specification of Packed Encoding Rules (PER)".Release 8 9 3GPP TS 36.401: “E-UTRAN Architecture Description”. symbols and abbreviations Definitions For the purposes of the present document. Two kinds of EPs are used: Class 1: Elementary Procedures with response (success and/or failure).681 (07/2002): "Information technology .1 Definitions. etc. For Class 1 EPs.421: "Trace concepts and requirements". Examples on using several S1AP EPs together with each other and EPs from other interfaces can be found in reference [FFS]. if any. An EP consists of an initiating message and possibly a response message.1): Information object specification". the types of responses can be as follows: 3GPP . 3GPP TS 36. version number. Elementary Procedure: S1AP consists of Elementary Procedures (EPs). the terms and definitions given in TR 21.905: "Vocabulary for 3GPP Specifications". subsequent revisions do not apply. ITU-T Recommendation X. An Elementary Procedure is a unit of interaction between eNBs and the EPC. [1] [2] [3] [4] [5] [6] [7] 3GPP TR 21.680 (07/2002): "Information technology . through reference in this text. If the independence between some EPs is restricted. the latest version applies.ASN. In the case of a reference to a 3GPP document (including a GSM document). ITU-T Recommendation X. ITU-T Recommendation X. These Elementary Procedures are defined separately and are intended to be used to build up complete sequences in a flexible manner. 3GPP TS 36. 3GPP TS 32. The following documents contain provisions which. • For a non-specific reference. 3 3. the EPs may be invoked independently of each other as stand alone procedures.905 [1] and the following apply. which can be active in parallel.410: “S1 General Aspects and Principles”.

] SAE bearer: one or more Service Data Flows between a UE and EPC [according to definition for EPS bearer 23.401]. On time supervision expiry (i.413 V8. There is an one-to-one mapping between the SAE bearer and the SAE Radio Bearer.1. [Note (to be removed once captured in another TS): The MME UE S1AP ID shall be allocated so as to uniquely identify the UE over the S1 interface within the MME. When eNB receives MME UE S1AP ID it shall store it for the duration of the UE-associated logical S1-connection for this UE. Class 2 EPs are considered always successful. The UE-associated logical S1-connection may exist before the S1 UE context is setup in eNB.Release 8 10 3GPP TS 36.401. Successful and Unsuccessful: One signalling message reports both successful and unsuccessful outcome for the different included requests. Once known to eNB this IE is included in all UE associated S1-AP signalling (UL as well as DL). The response message used is the one defined for successful outcome.0 (2008-03) Successful: A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response.401.2 <symbol> Symbols <Explanation> For the purposes of the present document.401]. UE-associated logical S1-connection: The UE-associated logical S1-connection uses the identities MME UE S1AP ID and eNB UE S1AP ID according to definition in [23. 3.e. Once known to MME his IE is included in all UE associated S1-AP signalling (UL as well as DL). absence of expected response). [Note (to be removed once captured in another TS): The eNB UE S1AP ID shall be allocated so as to uniquely identify the UE over the S1 interface within the eNB.401]. UE-associated signalling: When S1-AP messages associated to one UE uses the UE-associated logical S1-connection for association of the message to the UE in eNB and EPC. the following symbols apply: 3GPP . For a received UE associated S1-AP message the MME identifies the associated UE based on the MME UE S1AP ID IE and the eNB identifies the associated UE based on the eNB UE S1AP ID IE. When MME receives eNB UE S1AP ID it shall store it for the duration of the UE-associated logical S1-connection for this UE. SAE bearer identity: the SAE bearer identity uniquely identifies an SAE bearer for one UE [according to definition for EPS bearer identity in 23. Note: The SAE bearer identity remains unique for the UE even if the UE-associated logical S1-connection is released during periods of user inactivity. SAE Radio Bearer: the SAE Radio bearer transports the packets of an SAE bearer between a UE and an eNB. Note: The SAE bearer is either a default SAE bearer or a dedicated SAE bearer. eNB UE S1AP ID: according to definition in 23.] MME UE S1AP ID: according to definition in 23. Unsuccessful: A signalling message explicitly indicates that the EP failed.

These parts can always be decoded regardless of the standard version. but does not support functionality Y. The EPC functional behaviour is left unspecified. if supported. possibly informing the requesting node about the not supported functionality. see Annex A.2.1 Procedure Specification Principles The principle for specifying the procedure logic is to specify the functional behaviour of the eNB exactly and completely. 4. the optional IE shall not be included.g. e. include ID and criticality fields that are coded in a standard format that will not be changed in the future.0 (2008-03) 3. if supported" be executed The procedure text indicates that the receiving node "shall." perform a certain function Y under a certain condition. For examples on how to use the Criticality Diagnostics IE. e.1. the receiving node shall proceed with the execution of the EP. in TR 21.413 V8. For requirements on including Criticality Diagnostics IE. containing an appropriate cause value. 4. 2) Functionality which "shall. forward/backward compatibility issue and specification notations. and IEs or groups of related IEs. the following notations apply: Message 3GPP . the abbreviations given in TR 21. MESSAGE NAME message.905 [1]. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation. The following specification principles have been applied for the procedure text in clause 8: The procedure text discriminates between: 1) Functionality which "shall" be executed The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition.2 Forwards and Backwards Compatibility The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages. SAE procedure. 4.3 Procedure Specification Notations When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure". Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text.3 Abbreviations For the purposes of the present document.g. The EPs Handover Preparation and others (tbd) are exceptions from this principle. if any.Release 8 11 3GPP TS 36. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP. When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message". see section 10. <ACRONYM> <Explanation> 4 General Editor’s Note: Section captures procedure specification principles. the receiving node shall respond with the message used to report unsuccessful outcome for this procedure. If the receiving node supports procedure X.905 [1] and the following apply. For the purposes of the present document. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message.

e. e. When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 9.413 V8.g.1. "Value". Value of an IE 3GPP .0 (2008-03) IE When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE".Release 8 12 3GPP TS 36.g. Information Element IE.2 enclosed by quotation marks.

Release 8 13 3GPP TS 36. 3GPP . UE-associated services: They are related to one UE. S1AP services are divided into two groups: 2. S1AP provides the signalling service between E-UTRAN and the evolved packet core (EPC) that is required to fulfil the S1AP functions described in clause 7.0 (2008-03) 5 S1AP Services 1.413 V8. S1AP functions that provide these services are associated with a UE-associated signalling connection that is maintained for the UE in question.1. Non UE-associated services: They are related to the whole S1 interface instance between the eNB and MME utilising a non UE-associated signalling connection.

S1AP shall be notified if the signalling connection breaks.0 (2008-03) 6 Services Expected from Signalling Transport The signalling connection shall provide in sequence delivery of S1AP messages.413 V8.Release 8 14 3GPP TS 36.1. 3GPP .

to transfer NAS signalling related information when the S1 UE context in the eNB is already established.Release 8 15 3GPP TS 36. Status Transfer: This functionality transfers PDCP SN Status information from source eNB to target eNB in support of in-sequence delivery and duplication avoidance for intra LTE handover. - 3GPP . Overload function to indicate the load situation in the control plane of the S1 interface. modifying and releasing SAE bearers. to setup one or more SAE bearer(s) if requested by the MME. to setup the default IP connectivity. which are triggered by the MME The release of SAE bearers may be triggered by the eNB as well.1. S1AP protocol has the following functions: SAE Bearer management function: This overall functionality is responsible for setting up.413 V8. Mobility Functions for UEs in LTE_ACTIVE in order to enable a change of eNBs within SAE/LTE (Inter MME/Serving SAE-GW Handovers) via the S1 interface (with EPC involvement). and to transfer NAS signalling related information to the eNB if needed. UE Capability Info Indication function: This functionality is used to provide the UE Capability Info when received from the UE to the MME. - S1 UE context Release function: This functionality is responsible to manage the release of UE specific context in the eNB and the MME.0 (2008-03) 7 Functions of S1AP Editor’s Note: Description of S1AP functions. Initial Context Transfer function: This functionality is used to establish an S1UE context in the eNB. - NAS Signalling transport function between the UE and the MME is used: to transfer NAS signalling related information and to establish the S1 UE context in the eNB. Error Indication functionality to allow a proper error reporting/handling in cases where no failure messages are defined. S1 interface management functions comprise the: Reset functionality to ensure a well defined initialisation on the S1 interface. a change of RAN nodes between different RATs (Inter-3GPP-RAT Handovers) via the S1 interface (with EPC involvement). - - Paging: This functionality provides the EPC the capability to page the UE.

413 V8. all EPs are divided into Class 1 and Class 2 EPs (see subclause 3.Release 8 16 3GPP TS 36.1. 3GPP .1 for explanation of the different classes): Table 1: Class 1 procedures Elementary Procedure Handover Preparation Handover Resource Allocation Path Switch Request Handover Cancellation SAE Bearer Setup SAE Bearer Modify SAE Bearer Release Initial Context Setup Reset S1 Setup UE Context Release UE Context Modification Initiating Message HANDOVER REQUIRED HANDOVER REQUEST PATH SWITCH REQUEST HANDOVER CANCEL SAE BEARER SETUP REQUEST SAE BEARER MODIFY REQUEST SAE BEARER RELEASE COMMAND INITIAL CONTEXT SETUP REQUEST RESET S1 SETUP REQUEST UE CONTEXT RELEASE COMMAND UE CONTEXT MODIFICATION REQUEST Successful Outcome Response message HANDOVER COMMAND HANDOVER REQUEST ACKNOWLEDGE PATH SWITCH REQUEST ACKNOWLEDGE HANDOVER CANCEL ACKNOWLEDGE SAE BEARER SETUP RESPONSE SAE BEARER MODIFY RESPONSE SAE BEARER RELEASE COMPLETE INITIAL CONTEXT SETUP RESPONSE RESET ACKNOWLEDGE S1 SETUP RESPONSE UE CONTEXT RELEASE COMPLETE UE CONTEXT MODIFICATION RESPONSE Unsuccessful Outcome Response message HANDOVER PREPARATION FAILURE HANDOVER FAILURE PATH SWITCH REQUEST FAILURE INITIAL CONTEXT SETUP FAILURE S1 SETUP FAILURE UE CONTEXT MODIFICATION FAILURE Table 2: Class 2 procedures Elementary Procedure Handover Notification SAE Bearer Release Request 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 Message HANDOVER NOTIFY SAE BEARER RELEASE REQUEST 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 The following applies concerning interference between Elementary Procedures: The Reset procedure takes precedence over all other EPs.1 S1AP Procedures List of S1AP Elementary procedures In the following tables.0 (2008-03) 8 8.

In case of the establishment of an SAE bearer the EPC must be prepared to receive user data before the SAE BEARER SETUP RESPONSE message has been received. Upon reception of the SAE BEARER SETUP REQUEST message. The eNB shall allocate the required resources on S1 for the SAE bearers requested to be established. A list of SAE bearers which failed to be established shall be included in the SAE Bearer Failed to Setup List IE.1. in the SAE BEARER SETUP RESPONSE message. The eNB shall pass the NAS-PDU IE and the value contained in the SAE bearer identity IE received for the SAE bearer for each established SAE Radio Bearer to the UE.2 Successful Operation eNB MME SAE BEARER SETUP REQUEST SAE BEARER SETUP RESPONSE Figure 8. When sending the SAE BEARER SETUP REQUEST message the MME shall start the T SAEBearerSetup timer.Release 8 17 3GPP TS 36. the eNB shall execute the requested SAE bearer configuration. Successful operation. 8. If the Trace activation IE is included in the SAE BEARER SETUP REQUEST message then eNB should initiate the requested trace function as described in 32.2.1.2.2 8.2. and if resources are available for the requested configuration.1 8. A list of SAE bearers which are successfully established shall be included in the SAE Bearer Setup List IE. the result for all the requested SAE bearers.2. The MME initiates the procedure by sending an SAE BEARER SETUP REQUEST message to the eNB. Upon reception of the SAE BEARER SETUP RESPONSE message the MME shall stop timer T SAEBearerSetup.413 V8. - The SAE BEARER SETUP REQUEST message shall contain the information required by the eNB to build the SAE bearer configuration consisting of at least one additional SAE bearer including for each SAE bearer to setup in the SAE Bearer to be Setup List IE.1 SAE Bearer Management procedures SAE Bearer Setup General The purpose of the SAE Bearer Setup procedure is to assign resources on Uu and S1 for one or several SAE bearers and to setup corresponding SAE Radio Bearers for a given UE.0 (2008-03) 8.422. For each SAE bearer and based on the SAE Bearer level QoS parameters IE the eNB shall establish an SAE Radio Bearer and allocate the required resources on Uu.1. The procedure uses UE-associated signalling.2-1: SAE Bearer Setup procedure. Interactions with Handover Preparation procedure: If a handover becomes necessary during SAE bearer setup.1. The eNB shall report to the MME. the eNB may interrupt the ongoing SAE bearer Setup procedure and initiate the Handover Preparation procedure as follows: 3GPP .

Upon reception of the SAE BEARER MODIFY REQUEST message. For each SAE bearer that shall be modified and based on the new SAE Bearer level QoS parameters IE the eNB shall modify the SAE Radio Bearer configuration and change allocation of resources on Uu according to the new resource request.2-1: SAE Bearer Modify procedure. if necessary the SAE bearer(s) failed to setup in the SAE Bearer Failed to Setup List IE with the cause "handover triggered" and the SAE bearer(s) successfully setup in the SAE Bearer to be Setup List IE. Successful operation. 3GPP .2. 8.4 Abnormal Conditions Editor’s Note: Further Assessment required.2 8. The eNB shall pass the NAS-PDU IE and the value contained in the SAE bearer identity IE received for the SAE bearer to the UE when modifying the SAE Radio Bearer configuration. The eNB shall trigger the handover procedure by sending a HANDOVER REQUIRED message to the EPC.1 SAE Bearer Modify General The purpose of the SAE Bearer Modify procedure is to enable modifications of already established SAE bearers for a given UE.1.1. 8. and if resources are available for the requested target configuration.413 V8. 3.3 Unsuccessful Operation The unsuccessful operation is specified in the successful operation section.2. The procedure uses UE-associated signalling. The MME initiates the procedure by sending an SAE BEARER MODIFY REQUEST message to the eNB. 8.2. 2. Information shall be present in the SAE BEARER MODIFY REQUEST message only when any previously set value for the SAE bearer configuration is requested to be modified.2.2.Release 8 18 3GPP TS 36.0 (2008-03) 1.2. 8. The EPC shall terminate the SAE bearer Setup procedure at reception of the SAE BEARER SETUP RESPONSE message.2.1. The SAE BEARER MODIFY REQUEST message shall contain the information required by the eNB to modify one or several SAE bearers of the existing SAE Bearer configuration.2. eNB shall change allocation of resources on S1 according to the new resource request. the eNB shall execute the modification of the requested SAE bearer configuration. When sending the SAE BEARER MODIFY REQUEST message the MME shall start the T SAEBearerModify timer. The eNB shall terminate the SAE bearer Setup procedure and shall send the SAE BEARER SETUP RESPONSE message in which the eNB shall indicate.2.2 Successful Operation eNB MME SAE BEARER MODIFY REQUEST SAE BEARER MODIFY RESPONSE Figure 8.

3GPP . The procedure uses UE-associated signalling. in the SAE BEARER MODIFY RESPONSE message. The eNB shall trigger the handover procedure by sending a HANDOVER REQUIRED message to the EPC.3 8.3.3 Unsuccessful Operation The unsuccessful operation is specified in the successful operation section.1. Interactions with Handover Preparation procedure: If a handover becomes necessary during SAE bearer modify.4 Abnormal Conditions Editor’s Note: Further Assessment required.2. 2. the eNB may interrupt the ongoing SAE bearer Modify procedure and initiate the Handover Preparation procedure as follows: 1.413 V8. In case of a modification of an SAE Bearer the EPC must be prepared to receive user data according to the modified SAE bearer profile prior to the SAE BEARER MODIFY RESPONSE message.2.0 (2008-03) If the E-UTRAN failed to modify an SAE Bearer the E-UTRAN shall keep the SAE Bearer configuration as it was configured prior the SAE BEARER MODIFY REQUEST. Upon reception of the SAE BEARER MODIFY RESPONSE the MME shall stop T SAEBearerModify.2. 3. 8. 8.2. 8. the result for all the requested SAE bearers to be modified.2. The eNB shall terminate the SAE bearer Modify procedure and shall send the SAE BEARER MODIFY RESPONSE message in which the eNB shall indicate. if necessary the SAE bearer(s) failed to modify in the SAE Bearer Failed to Modify List IE with the cause "handover triggered" and the SAE bearer(s) successfully modified in the SAE Bearer Modify List IE. A list of SAE bearers which are successfully modified shall be included in the SAE Bearer Modify List IE.Release 8 19 3GPP TS 36. A list of SAE Bearers which failed to be modified shall be included in the SAE Bearer Failed to Modify List IE.2.1 SAE Bearer Release General The purpose of the SAE Bearer Release procedure is to enable the release of already established SAE Bearers for a given UE. The eNB shall report to the MME. The EPC shall terminate the SAE bearer modify procedure at reception of the SAE BEARER MODIFY RESPONSE message.

Upon reception of the SAE BEARER RELEASE COMMAND message the eNB shall execute the release of the requested SAE Bearers. 3.2. The EPC shall terminate the SAE bearer Release procedure at reception of the SAE BEARER RELEASE COMPLETE message. Successful operation.2. When sending the SAE BEARER RELEASE COMMAND message.Release 8 20 3GPP TS 36. if necessary the SAE bearer(s) failed to release in the SAE Bearer Failed to Release List IE with the cause "handover triggered" and the SAE bearer(s) successfully released in SAE Bearer Release List IE. eNB shall release allocate resources on S1 for the SAE bearers requested to be released.1-1: SAE Bearer Releae procedure.1. After sending an SAE BEARER RELEASE COMPLETE message containing an SAE Bearer identity within the SAE Bearer Release List IE . The eNB shall report to the MME.MME initiated eNB MME SAE BEARER RELEASE COMMAND SAE BEARER RELEASE COMPLETE Figure 8. the MME shall start the T SAEBEAERERRELEASE timer. 3GPP . the eNB may interrupt the ongoing SAE bearer Release procedure and initiate the Handover Preparation procedure as follows: 1.2. The eNB shall be prepared to receive an SAE BEARER RELEASE COMMAND message on an established UEassociated logical S1-connection containing an SAE Bearer Release List IE at any time and shall always reply to it with an SAE BEARER RELEASE COMPLETE message. the result for all the SAE bearers to be released..2. A list of SAE bearers which failed to be released shall be included in the SAE Bearer Failed to Release List IE. The SAE BEARER RELEASE COMMAND message shall contain the information required by the eNB to release at least one SAE bearer in the SAE Bearer To Be Released List IE. The eNB shall pass the value contained in the SAE bearer identity IE received for the SAE bearer to the radio interface protocol for each SAE Radio Bearer to be released. 2. The MME initiates the procedure by sending an SAE BEARER RELEASE COMMAND message.1 Successful Operation SAE Bearer Release . A list of SAE bearers which are released successfully shall be included in the SAE Bearer Release List IE. If a handover becomes necessary during SAE bearer release.3. For each SAE bearer to be released the eNB shall release the corresponding SAE Radio Bearer and release the allocated resources on Uu. The eNB shall trigger the handover procedure by sending a HANDOVER REQUIRED message to the EPC. the eNB shall be prepared to receive an SAE BEARER SETUP REQUEST message requesting establishment of an SAE bearer with this SAE bearer identity. in the SAE BEARER RELEASE COMPLETE message.413 V8.3. The eNB shall terminate the SAE bearer Release procedure and shall send the SAE BEARER RELEASE COMPLETE message in which the eNB shall indicate.0 (2008-03) 8.2 8.3.2.

3 8. the MME shall invoke the SAE BEARER RELEASE COMMAND procedure (release SAE bearer) to this effect.3. Interaction with SAE bearer Release procedure (MME initiated): If the EPC decides to release some or all indicated SAE bearers. Upon reception of the SAE BEARER RELEASE REQUEST message the MME should normally initiate the appropriate release procedure for the SAE bearers identified in the SAE BEARER RELEASE REQUEST message as defined in the Interaction with SAE Bearer Release paragraph below. Handover Restriction List.3. Interaction with UE Context Release procedure: If no SAE bearers will remain according to the SAE bearer RELEASE REQUEST message. NAS-PDU etc.3. the MME may initiate the UE Context Release Command procedure if it does not want to keep the UE-associated logical S1-connection. 3GPP .2.Release 8 21 3GPP TS 36.2.2 SAE Bearer Release Request . The procedure uses UE-associated signalling. Successful operation.1 8. UE capability information.2-1: SAE Bearer Release Request procedure. in the SAE Bearer To Be Released List IE.1. The SAE BEARER RELEASE REQUEST message shall contain at least one SAE bearers requested to be released. Editor’s Note: whether this is allowed at all (default bearer handling) needs to be checked.1.2.1 Context Management procedures Initial Context Setup General The purpose of the Initial Context Setup procedure is to establish the necessary overall initial UE Context including SAE Bearer context. Security context.2.3 Abnormal Conditions Editor’s Note: Further Assessment required. see open issue list. 8.3. It is up to the MME to decide how to react to the request. The eNB initiates the procedure by sending an SAE BEARER RELEASE REQUEST message towards the MME.0 (2008-03) 8.eNB initiated eNB MME SAE BEARER RELEASE REQUEST Figure 8. 8.2.3.413 V8.

Successful operation.422. which may contain roaming. store the Handover restriction List in the UE context. area or access restrictions the NAS-PDU IE (FFS) Security (FFS) the UE Radio Capability IE. the target eNB shall consider that no access restriction applies to the UE.1. store the received UE Radio Capabilities in the UE context.2-1: Initial Context Setup procedure.0 (2008-03) 8. If the Trace activation IE is included in the INITIAL CONTEXT SETUP REQUEST message then eNB should initiate the requested trace function as described in 32. and shall contain this Information Element if MME serves more than one PLMN identity.413 V8. When sending the INITIAL CONTEXT SETUP REQUEST message. the MME shall start the T InitialContextSetup timer. - - The eNB should use the information in Handover Restriction List IE to determine a target cell for handover.Release 8 22 3GPP TS 36. In case of the establishment of an SAE Bearer the MME must be prepared to receive user data before the INITIAL CONTEXT SETUP RESPONSE message has been received. The INITIAL CONTEXT SETUP REQUEST message shall contain within the SAE Bearer to be Setup List IE the information required by the eNB to build the new SAE Bearer configuration consisting of at least one additional SAE Bearer. If the Handover Restriction List IE is not contained in the INITIAL CONTEXT SETUP REQUEST message. 3GPP . - Upon receipt of the INITIAL CONTEXT SETUP REQUEST the eNB shall - attempt to execute the requested SAE Bearer configuration. The SAE Bearer to be Setup List IE may contain: - the SAE Bearer level QoS parameters IE The INITIAL CONTEXT SETUP REQUEST message may contain - the Aggregate Maximum Bit Rate IE (Usage for several APNs FFS) the Serving PLMN IE. The content of the NAS-PDU is outside the scope of this specification.3. store the Serving PLMN in the UE context. the Handover Restriction List IE.3. not interpret or modify the information contained in the NAS-PDU IE. pass the value contained in the SAE Bearer ID IE to the radio interface protocol for each SAE Bearer requested to be established.1.1.2 Successful Operation eNB MME INITIAL CONTEXT SETUP REQUEST INITIAL CONTEXT SETUP RESPONSE Figure 8.

the successful establishment of the security procedures with the UE.2. the result for all the requested SAE Bearers in the following way: A list of SAE Bearers which are successfully established shall be included in the SAE Bearer Setup List IE A list of SAE Bearers which failed to be established shall be included in the SAE Bearer Failed to Setup List IE. 8. and.eNB initiated General The purpose of the UE Context Release Request procedure is to enable the eNB to request the MME to release the UEassociated logical S1-connection due to EUTRAN generated reason (e. 8. Unsuccessful operation. 3GPP .3. The procedure uses UE-associated signalling.3.1 UE Context Release Request .413 V8. Upon reception of the INITIAL CONTEXT SETUP RESPONSE message the MME shall stop timer T InitialContextSetup. the procedure is terminated in the eNB.3-1: Initial Context Setup procedure.3 Unsuccessful Operation eNB MME INITIAL CONTEXT SETUP REQUEST INITIAL CONTEXT SETUP FAILURE Figure 8.g. Successful operation.1. in the INITIAL CONTEXT SETUP RESPONSE message. 8.2.3.2 8.0 (2008-03) The eNB shall report to the MME. 8.4 Abnormal Conditions Editor’s Note: Further Assessment required.Release 8 23 3GPP TS 36.1.3.3. “TX2RELOCOverall Expiry”).1.2. After sending the INITIAL CONTEXT SETUP RESPONSE message.3.3.2 Successful Operation eNB MME UE CONTEXT RELEASE REQUEST Figure 8.1.2-1: UE Context Release Request procedure.

1 UE Context Release (MME initiated) General The purpose of the UE Context Release procedure is to enable to MME to order the release of the UE-associated logical connection due to various reasons.4.0 (2008-03) The eNB controlling a UE-associated logical S1-connection initiates the procedure by generating an UE CONTEXT RELEASE REQUEST message towards the affected MME node.3 8.4 8. with security information).3. The UE CONTEXT RELEASE REQUEST message shall indicate the appropriate cause value for the requested UEassociated logical S1-connection release.Release 8 24 3GPP TS 36.3.3.3. The MME initiated UE Context Release procedure may be initiated in response to the eNB initiated UE Context Release Request procedure. Upon reception of the UE CONTEXT RELEASE COMMAND message. 3GPP .3.2 Successful Operation eNB MME UE CONTEXT RELEASE COMMAND UE CONTEXT RELEASE COMPLETE Figure 8. the eNB shall release all related signalling and user data transport resources and reply with the UE CONTEXT RELEASE COMPLETE message.3. The procedure uses UE-associated signalling. The procedure uses UE-associated signalling.413 V8. Editor’s Note:The usage of this procedure to handle detection of two UE-associated logical connections towards one UE is FFS.1 UE Context Modification General The purpose of the UE Context Modification procedure is to modify the established UE Context partly (e. 8.1. for example completion of a transaction between the UE and the EPC or completion of successful handover.3. 8.3.g.2-1: UE Context Release procedure.3. 8. Successful operation.

1 8.4 8. Successful operation. The UE CONTEXT MODIFICATION REQUEST message may contain the security information IE (includes the AS security key) Upon receipt of the UE CONTEXT MODIFICATION REQUEST the eNB shall store the received security information IE and take it into use.4. Editor’s Note: It is FFS whether the eNodeB is allowed to initiate this procedure in case there is an already prepared handover for this particular UE either on S1or on any of its X2 interfaces.4.3. the procedure is terminated in the eNB. in the UE CONTEXT MODIFICATION RESPONSE message to the MME.4.3.Release 8 25 3GPP TS 36.1. the successful update of the UE context: After sending the UE CONTEXT MODIFICATION RESPONSE message.1 Handover Signalling Handover Preparation General The purpose of the Handover Preparation procedure is to request the preparation of resources at the target side via the EPC. 8.3.2 Successful Operation eNB MME UE CONTEXT MODIFICATION REQUEST UE CONTEXT MODIFICATION RESPONSE Figure 8.3 Unsuccessful Operation eNB MME UE CONTEXT MODIFICATION REQUEST UE CONTEXT MODIFICATION FAILURE Figure 8.3.1.4. 3GPP .0 (2008-03) 8. Unsuccessful operation. The eNB shall report. 8.413 V8.4.2-1: UE Context Modification procedure.4. In case the UE context update cannot be performed successfully the eNB shall respond with the UE CONTEXT MODIFICATION FAILURE message to the MME with an appropriate cause value in the Cause IE.3-1: UE Context Modification procedure.

after a HANDOVER REQUIRED message is sent and before the Handover Preparation procedure is terminated. they shall be indicated in the SAE Bearers to Release List IE. the MME responds with the HANDOVER COMMAND message to the source eNodeB. terminate the MME initiated SAE Bearer Management procedure by sending the appropriate response message with the cause value “Handover Triggered” to the MME and then the source eNB shall continue with the handover procedure.1. if available. cancel the Handover Preparation procedure by executing the Handover Cancel procedure with an appropriate cause value "Interaction with other procedure”. the source eNB shall either: 1. After successful completion of the Handover Cancel procedure.2 Successful Operation source eNodeB HANDOVER REQUIRED HANDOVER COMMAND MME Figure 8. the source eNB receives a MME initiated SAE Bearer Management procedure on the same UE associated signaling connection.3 Unsuccessful Operation 3GPP . the source eNB shall continue the MME initiated SAE Bearer Management procedure or 2. including the reservation of resources at the target side is ready. Interactions with SAE Bearer Management procedures: If.1. If there are any SAE bearers that could not be admitted in the target. the source eNodeB may include the Direct Forwarding Path Availability IE in the HANDOVER REQUIRED message. Editor’s note: How to handle and control data forwarding is FFS. If HANDOVER REQUIRED message does not contain the Direct Forwarding Path Availability IE then indirect forwarding may be applied.4.4. 8. If the Target eNodeB to Source eNodeB Transparent Container IE or the Target RNC To Source RNC Transparent Container IE or the Target BSS to Source BSS Transparent Container IE has been received by the MME from the handover target then the transparent container shall be included in the HANDOVER COMMAND message.2-1: Handover preparation: successful operation The source eNodeB initiates the handover preparation by sending the HANDOVER REQUIRED message to the serving MME. When the preparation.1.1. If the DL forwarding IE is included within the Source eNodeB to Target eNodeB Transparent Container IE of the HANDOVER REQUIRED message and it is set to “DL forwarding proposed”.4.413 V8.Release 8 26 3GPP TS 36.0 (2008-03) 8. it indicates that the source eNodeB proposes forwarding of downlink data. For each bearer for which the source eNodeB proposes to do forwarding of downlink data.

the target eNB shall store this information in the UE context. the target eNB shall consider that no access restriction applies to the UE. The HANDOVER REQUEST message may contain the Serving PLMN IE. and shall contain this Information Element if MME serves more than one PLMN identity.1.2-1: Handover resource allocation: successful operation The MME initiates the procedure by sending the HANDOVER REQUEST message to the target eNodeB. If the Handover Restriction List IE is not contained in the HANDOVER REQUEST message.413 V8. The HANDOVER REQUEST message may contain the Handover Restriction List IE.2 8.0 (2008-03) source eNodeB HANDOVER REQUIRED HANDOVER PREPARATION FAILURE MME Figure 8. If the Source eNodeB to Target eNodeB Transparent Container IE or the Source RNC to Target RNC Transparent Container IE or the Source BSS to Target BSS Transparent Container IE has been received by the MME from the source side the MME includes the transparent container in the HANDOVER REQUEST message. the MME sends the HANDOVER PREPARATION FAILURE message with an appropriate cause value to the source eNodeB.2.1.1. The eNB should use the information in Handover Restriction List IE to determine a target cell for handover.1 Handover Resource Allocation General The purpose of the Handover Resource Allocation procedure is to reserve resources at the target eNodeB for the handover of a UE.4.Release 8 27 3GPP TS 36. 8. which may contain roaming area or access restrictions.4.3-1: Handover preparation: unsuccessful operation If the EPC or the target system is not able to accept any of the bearers or a failure occurs during the Handover Preparation.2.2.4. If the Serving PLMN IE or the Handover Restriction List IE is contained in the HANDOVER REQUEST message. 3GPP .4 Abnormal Conditions 8.4.2 Successful Operation target eNodeB HANDOVER REQUEST MME HANDOVER REQUEST ACKNOWLEDGE Figure 8.4.4. 8.

8.2.3. The SAE bearers that have not been admitted in the target cell shall be included in the SAE Bearers Failed to Setup List IE.2.4.413 V8.2.Release 8 28 3GPP TS 36.4. 3GPP .3. For each bearer that target eNB has decided to admit and for which DL forwarding IE is set to “DL forwarding proposed”. the target eNB may include the DL GTP Tunnel endpoint IE within the SAE Bearers Admitted List IEs IE of the HANDOVER REQUEST ACKNOWLEDGE message indicating that it accepts the proposed forwarding of downlink data for this bearer.4.4.3-1: Handover resource allocation: unsuccessful operation If the target eNodeB is not able to admit any of the SAE Bearers or a failure occurs during the Handover Preparation. 8. 8.4 Abnormal Conditions 8.4. The target eNodeB shall include in the SAE Bearers Admitted List IE the SAE Bearers for which resources have been prepared at the target cell.4.2 Successful Operation target eNodeB HANDOVER NOTIFY MME Figure 8. it shall send the HANDOVER REQUEST FAILURE message to the MME with an appropriate cause value.3 8.1 Handover Notification General The purpose of the Handover Notification procedure is to indicate to the MME that the UE has arrived to the target cell and the S1 handover has been successfully completed.3.3 Unsuccessful Operation target eNodeB HANDOVER REQUEST HANDOVER FAILURE MME Figure 8.1.4.2-1: Handover notification The target eNodeB shall send the HANDOVER NOTIFY message to the MME when the UE has been identified in the target cell and the S1 handover has been successfully completed.0 (2008-03) After all necessary resources for the admitted SAE Bearers have been allocated the target eNodeB generates the HANDOVER REQUEST ACKNOWLEDGE message.

Release 8

29

3GPP TS 36.413 V8.1.0 (2008-03)

8.4.3.3

Abnormal Conditions

8.4.4
8.4.4.1

Path Switch Request
General

The purpose of the Path Switch Request procedure is to request the switch of a downlink GTP tunnel towards a new GTP tunnel endpoint.

8.4.4.2

Successful Operation

eNodeB PATH SWITCH REQUEST

MME

PATH SWITCH REQUEST ACKNOWLEDGE

Figure 8.4.4.2-1: Path switch request: successful operation The eNodeB initiates the procedure by sending the PATH SWITCH REQUEST message to the MME. After all necessary updates including the UP path switch have been successfully completed in the EPC, the MME shall send the PATH SWITCH REQUEST ACKNOWLEDGE message to the eNodeB and the procedure ends. Editor’s Note: The procedure text above (and for the failure cases) needs to cover the case where no, all, or some bearers are successfully switched, i.e. when to use the ACK and when to use the FAILURE response messages. Editor’s Note: It is FFS if EPC should have possibilities to change UL TEID with this procedure.

8.4.4.3

Unsuccessful Operation

eNodeB PATH SWITCH REQUEST PATH SWITCH REQUEST FAILURE

MME

Figure 8.4.4.3-1: Path switch request: unsuccessful operation If a failure occurs in the EPC during the execution of the Path Switch Request procedure, the MME shall send the PATH SWITCH REQUEST FAILURE message to the eNodeB with an appropriate cause value.

3GPP

Release 8

30

3GPP TS 36.413 V8.1.0 (2008-03)

8.4.4.4

Abnormal Conditions

8.4.5
8.4.5.1

Handover Cancellation
General

The purpose of the Handover Cancel procedure is to enable a source eNB to cancel an ongoing handover. The Handover Cancel procedure may be initiated by the source eNB during and after the Handover Preparation procedure if either of the following conditions is fulfilled: the source eNB has not yet initiated the execution of the handover via the Uu interface after having initiated the execution of the handover, the UE has returned to the source eNB by transmitting an RRC message which indicates that the UE considers the source eNB as its serving eNB

The procedure uses UE-associated logical S1-connection. Editor’s Note: Whether it is allowed to trigger the cancellation before the Handover Preparation is finalized is FFS.

8.4.5.2

Successful Operation

Source eNB

MME

HANDOVER CANCEL HANDOVER CANCEL ACKNOWLEDGE

Figure 8.4.5.2-1: Handover Cancel procedure. Successful operation. Editor’s Note: Whether a HANDOVER CANCEL ACKNOWLEDGE message is needed is FFS. The source eNB initiates the procedure by sending a HANDOVER CANCEL message to the EPC. The HANDOVER CANCEL message shall indicate the reason for cancelling the handover by the appropriate value of the Cause IE Upon reception of a HANDOVER CANCEL message, the EPC shall terminate the ongoing Handover Preparation procedure, release any resources associated with the handover preparation and send a HANDOVER CANCEL ACKNOWLEDGE message to the source eNB. Transmission and reception of a HANDOVER CANCEL ACKNOWLEDGE message terminate the procedure in the EPC and in the source eNB. After this, the source eNB does not have a prepared handover for that UE-associated logical S1-connection.

8.4.5.3
Not applicable.

Unsuccessful Operation

8.4.5.4
Not applicable.

Abnormal Conditions

3GPP

Release 8

31

3GPP TS 36.413 V8.1.0 (2008-03)

8.4.6
8.4.6.1

eNB Status Transfer
General

The purpose of the eNB Status Transfer procedure is to transfer the uplink PDCP-SN receiver status and the downlink PDCP-SN transmitter status from the source to the target eNodeB via the MME during an intra LTE S1 handover for each respective SAE bearer for which PDCP SN status preservation applies.

8.4.6.2

Successful Operation
eNodeB MME

eNB STATUS TRANSFER

Figure 8.4.6.2-1: eNB Status Transfer procedure The source eNodeB initiates the procedure by stop assigning PDCP SNs to downlink SDUs and sending the eNB STATUS TRANSFER message to the MME at the time point when it considers the transmitter/receiver status to be freezed. At that point of time, the source eNodeB either: discard the uplink packets received out of sequence for a bearer and include the bearer in the SAE Bearers Subject to Status Transfer List IE to indicate that PDCP SN status preservation applies for the bearer, send the uplink packets received out of sequence to the EPC for each bearer for which the PDCP SN status preservation doesn’t apply.

8.4.6.3
Not applicable.

Unsuccessful Operation

8.4.6.4

Abnormal Conditions

Editor’s Note: Further Assessment required.

8.4.7
8.4.7.1

MME Status Transfer
General

The purpose of the MME Status Transfer procedure is to transfer the uplink PDCP-SN receiver status and the downlink PDCP-SN transmitter status from the source to the target eNodeB via the MME during an S1 handover for each respective SAE bearer for which PDCP SN status preservation applies.

3GPP

3 Not applicable. the eNB shall perform paging of the UE in cells which belong to tracking areas as indicated in the List of TAIs IE.2-1: Paging procedure The MME initiates the paging procedure by sending the PAGING message to the eNB. Unsuccessful Operation 8.4. At the reception of the PAGING message.2-1: MME Status Transfer procedure The MME initiates the procedure by sending the MME STATUS TRANSFER message to the eNB.7.Release 8 32 3GPP TS 36.7. the target eNodeB shall ignore the message.4.5. For each bearer in SAE Bearers Subject to Status Transfer List IE received in the STATUS TRANSFER message. the target eNodeB shall use it and not deliver any uplink packet which has a PDCP SN lower than or equal to the value contained in this IE.7.4 Abnormal Conditions If the target eNodeB receives this message for a UE for which no prepared handover exists at the target eNodeB. 3GPP . For each bearer for which the LIS IE is received in the STATUS TRANSFER message.5.1.4.5 8.1 Paging General The purpose of the Paging procedure is to enable the MME to page a UE in the specific eNB.5. 8.4. 8.2 Successful Operation eNodeB MME MME STATUS TRANSFER Figure 8.7. The Paging Cause IE shall be transferred transparently to the UE.2 Successful Operation eNB MME PAGING Figure 8. the target eNodeB shall use DL PDCP-SN Next To Assign IE and the DL PDCP-HFN Next To Assign IE for the first downlink packet for which there is no PDCP SN yet assigned.413 V8. 8.0 (2008-03) 8.

6.1 NAS transport General The purpose of the NAS Transport procedure is to carry UE – MME signalling over the S1 Interface. The NAS messages are not interpreted by the eNB.2. 8. The NAS messages are transported in an IE of the INITIAL UE MESSAGE.1.6. If no UE-associated logical S1-connection exists.1 Successful Operations Initial UE Message eNB MME INITIAL UE MESSAGE Figure 8. the eNB shall invoke the NAS Transport procedure and send the INITIAL UE MESSAGE to the MME including the NAS message as a NAS-PDU IE. 8. and their content is outside the scope of this specification.413 V8. The procedure may use an existing UE-associated logical S1-connection. 8. the eNodeB shall generate one page on the radio interface.6 8.5.0 (2008-03) For each cell that belongs to any of the TA indicated in the List of TAIs IE.5.Release 8 33 3GPP TS 36. 8.3 Unsuccessful Operation Not applicable.2 8. The eNB shall allocate a unique eNB S1-AP UE Identity to be used for the UE and the eNB shall include this identity in the INITIAL UE MESSAGE message.6.6. DOWNLINK NAS TRANSPORT or UPLINK NAS TRANSPORT messages.2.1-1: Initial UE Message procedure When the eNB has received from the radio interface a NAS message to be forwarded to an MME to which no UEassociated logical S1-connection for the UE exists.2.6.2 DOWNLINK NAS TRANSPORT 3GPP .4 Abnormal Conditions Not applicable. Editor’s Note: Paging repetition requires further studies (FFS). 8. the establishment of the UE-associated logical S1-connection is initiated (and may be established) as part of the procedure.

2.2-1: DOWNLINK NAS Transport Procedure If a NAS message shall be sent from the MME to the UE and a UE-associated logical S1-connection exists for the UE or if the MME have received the eNB S1-AP UE Identity IE in an INITIAL UE MESSAGE message. The DOWNLINK NAS TRANSPORT message may contain the Handover Restriction List IE. The NAS-PDU IE contains an UE . The NAS-PDU IE contains an MME – UE message that is transferred without interpretation in the eNB. the target eNB shall store this information in the UE context. The DOWNLINK NAS TRANSPORT message may contain the Serving PLMN IE. and shall contain this Information Element if MME serves more than one PLMN identity. If the UEassociated logical S1-connection is not established the MME shall allocate a unique MME S1-AP UE Identity to be used for the UE and include that in the DOWNLINK NAS TRANSPORT message. 3GPP . By the reception of MME S1-AP UE Identity IE in eNB the UE-associated logical S1-connection is established. the eNB shall send the UPLINK NAS TRANSPORT message to the MME including the NAS message as a NAS-PDU IE. The eNB should use the information in Handover Restriction List IE to determine a target cell for handover.3-1: UPLINK NAS TRANSPORT Procedure When the eNB has received from the radio interface a NAS message to be forwarded to the MME to which an UEassociated logical S1-connection for the UE exists. If the Handover Restriction List IE is not contained in the DOWNLINK NAS TRANSPORT message. the target eNB shall consider that no access restriction applies to the UE. If the Serving PLMN IE or the Handover Restriction List IE is contained in the DOWNLINK NAS TRANSPORT message.6. 8.2.413 V8.1.6. the MME shall send a DOWNLINK NAS TRANSPORT message to the eNB including the NAS message as a NAS-PDU IE.2.MME message that is transferred without interpretation in the eNB.Release 8 34 3GPP TS 36.3 UPLINK NAS TRANSPORT eNB MME UPLINK NAS TRANSPORT Figure 8.0 (2008-03) eNB MME DOWNLINK NAS TRANSPORT Figure 8. which may contain roaming area or access restrictions.6.

1 Successful Operation Reset Procedure Initiated from the MME 3GPP .3 Unsuccessful Operation Not applicable 8.1 Management procedures Reset General Editor’s Note: Placeholder for a procedure description of common procedures as defined in TS 36.2.7.1. 8.6.7.7.4-1: NAS NON DELIVERY INDICATION Procedure When the eNB decides to not start the delivery of a NAS message that has been received over an UE-associated logical S1-connection. 8.g.1.2. handover triggered”.6.1 8.1.0 (2008-03) 8.413 V8. it shall report the non-delivery of this NAS message by sending a NAS NON DELIVERY INDICATION message to the MME including the non-delivered NAS message within the NAS-PDU IE and an appropriate cause value within the Cause IE e.4 NAS NON DELIVERY INDICATION eNB MME NAS NON DELIVERY INDICATION Figure 8.6.300 The purpose of the Reset procedure is to initialise the E-UTRAN in the event of a failure in the EPC or vice versa.7.6. 8.4 Abnormal Conditions Editor’s Note: Further Assessment required.Release 8 35 3GPP TS 36.1.2 8.2.7 8.

0 (2008-03) eNB MME RESET RESET ACKNOWLEDGE Figure 8.1-1: Reset procedure initiated from the MME.1.2 Reset Procedure Initiated from the E-UTRAN eNB MME RESET RESET ACKNOWLEDGE Figure 8. In the event of a failure at the eNB. Interactions with other procedures: In case of interactions with other procedures. Successful operation.2-1: Reset procedure initiated from the E-UTRAN.413 V8. a RESET message shall be sent to the eNB. When an eNB node sends this message towards an MME this message is used by the E-UTRAN to release affected SAE Bearers and to erase all affected signalling connections for the specific eNB node that sent the RESET message. which has resulted in the loss of transaction reference information. Successful operation.2. which has resulted in the loss of transaction reference information.1. In the event of a failure at the MME.1.7. The eNB shall respond with a RESET ACKNOWLEDGE message.7.Release 8 36 3GPP TS 36.7. Interactions with other procedures: In case of interactions with other procedures.2. a RESET message shall be sent to the MME. The MME shall respond with a RESET ACKNOWLEDGE message.1. this message is used by the E-UTRAN to release affected SAE Bearers and to erase all affected signalling connections for the specific MME node that sent the RESET message. the Reset procedure shall always override all other procedures. 8.2. 3GPP . the Reset procedure shall always override all other procedures. When a MME node sends this message towards an eNB.

1 Error Indication General The Error Indication procedure is initiated by a node to report detected errors in one incoming message.7. 8. 3GPP . it shall stop timer TRafC or TRafR and send a RESET ACKNOWLEDGE message to the peer entity.3 Crossing of Reset Messages When an entity that has sent a RESET message and is waiting for a RESET ACKNOWLEDGE message.1. eNB originated. 8.7. MME originated.2-1: Error Indication procedure.7.g. the maintenance system be informed. After the n-th unsuccessful repetition the procedure shall be stopped and e. If the error situation arises due to reception of a message utilising UE associated signalling.g.0 (2008-03) 8.2.7. the Error Indication procedure is initiated by an ERROR INDICATION message sent from the receiving node. 8.1.7. instead receives a RESET message from the peer entity. The sending of the RESET message shall be repeated a maximum of "n" times where n is an operator matter. When the conditions defined in clause 10 are fulfilled. provided they cannot be reported by an appropriate failure message.Release 8 37 3GPP TS 36.3. Successful operation.7.3. After the n-th unsuccessful repetition the procedure shall be stopped and e.2. Otherwise the procedure uses non-UE associated signalling.1.7.1.3.1.2.1 Abnormal Conditions Abnormal Condition at the CN If the MME sends a RESET message to the eNB and receives no RESET ACKNOWLEDGE message within a period TRafR then it shall repeat the entire Reset procedure. the maintenance system be informed.7.2-2: Error Indication procedure. The sending of the RESET message shall be repeated a maximum of "n" times where n is an operator matter.413 V8. Successful operation.3 8. 8. then the Error Indication procedure uses UE associated signalling.2 8.2 Successful Operation eNB ERROR INDICATION MME Figure 8.2 Abnormal Condition at the E-UTRAN If the eNB sends a RESET message to the MME and receives no RESET ACKNOWLEDGE message within a period TRafC then it shall repeat the entire Reset procedure.2. eNB ERROR INDICATION MME Figure 8.7.

If one or both of MME UE S1AP ID IE and the eNB UE S1AP IE are not correct.7.Release 8 38 3GPP TS 36.7.3. This message shall be the first S1AP message sent after the TNL association has become operational. the cause shall be set to appropriate value e. “unknown eNB UE S1AP” or “unknown the pair of UE S1AP ID”.3 Unsuccessful Operation eNodeB S1 SETUP REQUEST S1 SETUP FAILURE MME Figure 8.7.1 S1 Setup General The purpose of the S1 Setup procedure is to exchange application level data needed for the eNodeB and MME to interoperate correctly on the S1 interface.3-1: S1 Setup procedure: Unsuccessful Operation. The MME responds with S1 SETUP RESPONSE including the appropriate data. “unknown MME UE S1AP ID”.1.7.2 Successful Operation eNodeB S1 SETUP REQUEST S1 SETUP RESPONSE MME Figure 8. 3GPP . 8.7.3. If the MME can not accept the setup it should respond with a S1 SETUP FAILURE and appropriate cause value. -FFS 8.7.3.3 8. Abnormal Conditions 8.7.2-1: S1 Setup procedure: Successful Operation.0 (2008-03) The ERROR INDICATION message shall contain at least either the Cause IE or the Criticality Diagnostics IE.3. The exchanged data shall be stored in respective node and used for the duration of the TNL association.413 V8. When this procedure is finished S1 interface is operational and other S1 messages can be exchanged.3.g.2. The eNodeB initiates the procedure by sending a S1 SETUP REQUEST message including the appropriate data to the MME. In case the Error Indication procedure is triggered by utilising UE associated signalling the MME UE S1AP ID IE and the eNB UE S1AP IE shall be included in the ERROR INDICATION message.3 Not applicable. 8.

1 S1 CDMA2000 Tunneling Procedures General The purpose of S1 CDMA2000 Tunneling procedures is to carry CDMA2000 signalling between UE and CDMA2000 RAT over the S1 Interface.8. The CDMA2000 messages are transported in an IE of the DOWNLINK S1 CDMA2000 TUNNELING or UPLINK CDMA2000 TUNNELING messages.Release 8 39 3GPP TS 36.2 8.8.1 Successful Operations Downlink S1 CDMA2000 Tunneling eNB MME DOWNLINK S1 CDMA2000 TUNNELING Figure 8.2. 8. and their content is outside the scope of this specification. The CDMA2000 messages are not interpreted by the eNB.2 Uplink S1 CDMA2000 Tunneling eNB MME UPLINK S1 CDMA2000 TUNNELING Figure 8.2.8 8.7.4 Abnormal Conditions 8. 8.3.2.8.2-1: Uplink S1 CDMA2000 Tunneling Procedure 3GPP .8.8.8.2.413 V8. These procedures use an established UE-associated logical S1-connection. 8.1-1: Downlink S1 CDMA2000 Tunneling Procedure If a CDMA2000 message shall be sent from the MME to the UE and a UE-associated logical S1-connection exists for the UE the MME shall send a DOWNLINK S1 CDMA2000 TUNNELING message to the eNB including the CDMA2000-PDU IE to the UE.1.0 (2008-03) If the S1 SETUP FAILURE messages include the Time To Wait IE the eNodeB shall wait at least for the indicated time before reinitiating the S1 setup towards the same MME.

Release 8 40 3GPP TS 36.8.9. 3GPP .3 Unsuccessful Operation Not applicable 8. The eNB controlling a UE-associated logical S1-connection initiates the procedure by generating an UE CAPABILITY INFO INDICATION message towards the affected MME node including UE capability information.9.413 V8.2 Successful Operation eNB MME UE CAPABILITY INFO INDICATION Figure 8. 8.4 Abnormal Conditions Editor’s Note: Further Assessment required.0 (2008-03) When the eNB has received from the radio interface a CDMA2000 message to be forwarded to the MME to which an UE-associated logical S1-connection for the UE exists. The UE capability information provided to the MME should overwrite respective UE capability related information stored in the MME. the eNB shall send the UPLINK S1 CDMA2000 TUNNELING message to the MME including the CDMA2000 message as a CDMA2000-PDU IE.1. Successful operation. 8.1 UE Capability Info Indication General The purpose of the UE Capability Info Indication procedure is used to enable the eNB to provide this information and relevant updates of this information within the eNB that took place without MME notice within the E-UTRAN to the MME.9 8.8. 8.9.2-1: UE Capability Info Indication procedure.

3GPP .1 Elements for S1AP Communication Message Functional Definition and Content Editor’s Note: Description of functional definition and content. Each repetition of the IE has its own criticality information.1 9.1.2 9.1. if applicable. 9. criticality assignment.2.2. Editor’s note: Tabular format tables content (e. Table 4: Meaning of abbreviations used in S1AP messages Abbreviation M O C Meaning IEs marked as Mandatory (M) shall always be included in the message.2. optional or conditional according to table 4.) will be updated in forthcoming meetings.3.2 Criticality Each Information Element or Group of Information Elements may have criticality information applied to it.1.1.1. This is usable only for repeatable IEs. IEs marked as Optional (O) may or may not be included in the message. Criticality information is applied.Release 8 41 3GPP TS 36. Following cases are possible: Table 5: Meaning of content within “Criticality” column Abbreviation – YES GLOBAL EACH Meaning No criticality information is applied explicitly.413 V8.1 General Message Contents Presence All information elements in the message descriptions below are marked mandatory.g. etc. semantic description.1. This is usable only for repeatable IEs. 9. 9.2. 9. This is usable only for nonrepeatable IEs The IE and all its repetitions together have one common criticality information. Otherwise the IE shall not be included.0 (2008-03) 9 9.1.2. It is not allowed to assign different criticality values to the repetitions. IEs marked as Conditional (C) shall be included in a message only if the condition is satisfied.3 Range The Range column indicates the allowed number of copies of repetitive IEs/IE groups.4 Assigned Criticality This column provides the actual criticality information as defined in subclause 10.

Direction: MME → eNB IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID SAE Bearer to be Setup List >SAE Bearer To Be Setup Item IEs >> SAE Bearer ID Presence M M M M 1 to <maxnoof SAEbearers> M 9.3.1.2.3.2.2.1 SAE Bearer Management Messages SAE BEARER SETUP REQUEST This message is sent by the MME and is used for request the eNB to assign resources on Uu and S1 for one or several SAE bearers.1.2 note: EPC TEID.1.2.2.2.4 9. of SAE bearer allowed towards one UE.2 a value for SAE bearer identity shall only be present once in SAE Bearer to be Setup List IE Includes necessary QoS parameters Range IE type and reference 9.4 Semantics description Criticality YES YES YES YES EACH Assigned Criticality reject reject reject reject reject >> SAE Bearer Level QoS parameters M 9.3.2.0 (2008-03) 9. the maximum value is 256.3 9.1. UDP port - Trace Activation NAS-PDU O M 9.1 9.2.1 9.2.3.1.1.3 9.1.15 - >> Transport Layer Address >> GTP-TEID M M 9. (FFS) 3GPP .5 YES YES ignore reject Range bound maxnoofSAEbearers Explanation Maximum no.2.2.413 V8.Release 8 42 3GPP TS 36.

2.2.3.1. UDP port Range IE type and reference 9. of SAE bearer allowed towards one UE.1.2.3 9.3.Release 8 43 3GPP TS 36.1.2.2 a value for SAE bearer identity shall only be present once in SAE Bearer Failed to Setup List IE YES EACH - ignore ignore >> Cause NAS-PDU M M 9.3.2. (FFS) 3GPP .0 (2008-03) 9.1 9.2 note: eNB TEID.2.5 YES ignore Range bound maxnoofSAEbearers Explanation Maximum no.2.1 9.2.2 SAE BEARER SETUP RESPONSE This message is sent by the eNB and is used to report the outcome of the request from the SAE BEARER SETUP REQUEST message. Direction: eNB → MME IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID SAE Bearer Setup List >SAE Bearer Setup Item IEs >> SAE Bearer ID Presence M M M O 1 to <maxnoof SAEbearers> M a value for SAE bearer identity shall only be present once in SAE Bearer Setup List IE 9.2.1.3.4 Semantics description Criticality YES YES YES YES EACH Assigned Criticality reject reject reject reject reject >> Transport Layer Address >> GTP-TEID M M - SAE Bearer Failed to Setup List >SAE Bearer Failed To Setup Item IEs >> SAE Bearer ID O 1 to <maxnoof SAEbearers> M 9.3 9.413 V8.1.2. the maximum value is 256.

1.2. of SAE bearer allowed towards one UE. Direction: MME → eNB IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID SAE Bearer to be Modified List >SAE Bearer To Be Modified Item IEs >> SAE Bearer ID Presence M M M M 1 to <maxnoof SAEbearers> M 9.1.15 - NAS-PDU M 9.2.3.1. (FFS) 3GPP .0 (2008-03) 9.1.Release 8 44 3GPP TS 36.5 YES ignore Range bound maxnoofSAEbearers Explanation Maximum no. the maximum value is 256.1.3.2.3.2.2 a value for SAE bearer identity shall only be present once in SAE Bearer to be Modified List IE Includes necessary QoS parameters Range IE type and reference 9.3 SAE BEARER MODIFY REQUEST This message is sent by the MME and is used to request the eNB to modify the SAE Radio Bearers and the allocated resources on Uu and S1 for one or several SAE bearers.3 9.2.3.1 9.413 V8.2.4 Semantics description Criticality YES YES YES YES EACH Assigned Criticality reject reject reject reject reject >> SAE Bearer Level QoS Parameters M 9.

2.1 9.1. the maximum value is 256.1.1.2.3.4 SAE BEARER MODIFY RESPONSE This message is sent by the eNB and is used to report the outcome of the request from the SAE BEARER MODIFY REQUEST message.3.3. Direction: eNB → MME IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID SAE Bearer Modify List >SAE Bearer Modify Item IEs >> SAE BearerID Presence M M M O 1 to <maxnoof SAEbearers> M 9.1.3 9.2.413 V8.0 (2008-03) 9.5 YES ignore Range bound maxnoofSAEbearers Explanation Maximum no.4 Semantics description Criticality YES YES YES YES EACH Assigned Criticality reject reject reject reject reject SAE Bearer Failed to Modify List >SAE Bearer Failed To Modify Item IEs >> SAE Bearer ID O 1 to <maxnoof SAEbearers> M 9.2 a value for SAE bearer identity shall only be present once in SAE Bearer Modifiy List IE + SAE Bearer Failed to Modify List YES EACH - ignore ignore >> Cause NAS-PDU M M 9.3.2.Release 8 45 3GPP TS 36.2.1.3 9.2 a value for SAE bearer identity shall only be present once in SAE Bearer Modifiy List IE + SAE Bearer Failed to Modify List Range IE type and reference 9.2. (FFS) 3GPP . of SAE bearer allowed towards one UE.2.1.

3 - Range bound maxnoofSAEbearers Explanation Maximum no.1.Release 8 46 3GPP TS 36.3. of SAE bearer allowed towards one UE.1.1. (FFS) 3GPP .2.3 9.3.1.2. the maximum value is 256.413 V8.1.2..2.3.2 a value for SAE bearer identity shall only be present once in SAE Bearer To Be Released List IE Range IE type and reference 9.1 9.0 (2008-03) 9.5 SAE BEARER RELEASE COMMAND This message is sent by the MME and is used to request the eNB to release allocated resources on Uu and S1 for one or several SAE bearers.2.4 Semantics description Criticality YES YES YES YES EACH Assigned Criticality reject reject reject ignore ignore >> Cause M 9. Direction: MME → eNB IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID SAE Bearer To Be Released List >SAE Bearer To Be Released Item IEs >> SAE bearer ID Presence M M M M 1 to <maxnoof SAEbearers> M 9.

(FFS) 3GPP .3.3 9.2 a value for SAE bearer identity shall only be present once in SAE Bearer Release List IE + SAE Bearer Failed to Release List IE YES EACH - ignore ignore >> Cause M 9.3 - Range bound maxnoofSAEbearers Explanation Maximum no.1.1.413 V8.0 (2008-03) 9.1 9.3. of SAE bearer allowed towards one UE.2.2 a value for SAE bearer identity shall only be present once in SAE Bearer Release List IE + SAE Bearer Failed to Release List IE Range IE type and reference 9.4 Semantics description Criticality YES YES YES YES EACH Assigned Criticality reject reject reject ignore ignore SAE Bearer Failed to Release List >SAE Bearer Failed To Release Item IEs >> SAE bearer ID O 1 to <maxnoof SAEbearers> M 9. the maximum value is 256.Release 8 47 3GPP TS 36. Direction: eNB → MME IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID SAE Bearer Release List >SAE Bearer Release Item IEs >> SAE bearer ID Presence M M M O 1 to <maxnoof SAEbearers> M 9.1.2.1.1.6 SAE BEARER RELEASE COMPLETE This message is sent by the eNB and is used to report the outcome of the request from the SAE BEARER RELEASE COMMAND message.2.1.2.3.2.2.

1.1.2.1.0 (2008-03) 9.27 YES YES YES YES YES YES FFS reject ignore reject ignore ignore ignore FFS 3GPP .2.2.4 9.2.2.3 - Range bound maxnoofSAEbearers Explanation Maximum no.1.2.1.5 9.2 FFS 9.2.2.1.4 9.3.22 9.1.2.3.1 9.2.1 Context Management Messages INITIAL CONTEXT SETUP REQUEST Presence M M M O Range IE type and reference 9.3.3.2.1.413 V8.2 9.2.8 9.20 Semantics description Criticality YES YES YES YES Assigned Criticality reject reject reject reject IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Aggregate Maximum Bit Rate SAE Bearer to Be Setup List > SAE Bearer to Be Setup Item IEs >>SAE Bearer ID >>SAE Bearer Level QoS Parameters FFS: AMBR for several APNs M 1 to <maxnoofSAEbea rers> M M 9.1.2.1.2.2 a value for SAE bearer identity shall only be present once in SAE Bearer To Be Released List IE Range IE type and reference 9.2.3. of SAE bearer allowed towards one UE.4 9.3.1.Release 8 48 3GPP TS 36.1 9.4.3 9.1.2.4 Semantics description Criticality YES YES YES YES EACH Assigned Criticality reject reject reject ignore reject >> Cause M 9.1.3.15 Includes necessary QoS parameters YES EACH ignore reject - >>Transport Layer Address >> GTP TEID Security Trace Activation Serving PLMN Handover Restriction List NAS-PDU UE Radio Capability M M M O O O O O 9.7 SAE BEARER RELEASE REQUEST This message is sent by the eNB and is used to request the MME to release one or several SAE Bearers for one UE.1.1 9. Direction: eNB → MME IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID SAE Bearer To Be Released List >SAE Bearer To Be Released Item IEs >> SAE bearer ID Presence M M M M 1 to <maxnoof SAEbearers> M 9.2.2.3 9.2. the maximum value is 256.2. (FFS) 9.

the maximum value is 256.4 INITIAL CONTEXT SETUP FAILURE Presence M M M M Range IE type and reference 9. (FFS) 9.1.3 Semantics description Criticality YES YES YES YES Assigned Criticality reject reject reject ignore IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Cause 9.2 INITIAL CONTEXT SETUP RESPONSE Presence M M M O 1 to <maxnoofSAEbea rers> M M M O 1 to <maxnoofSAEbea rers> M M 9.4.3.3 9.2.413 V8. of SAE bearer allowed towards one UE.2.1.3 9.2. (FFS) 9.2.2.3.5 UE CONTEXT RELEASE REQUEST This message is sent by the eNB to request the release of the UE-associated S1-logical connection over the S1 interface.1.1.1.1.3.1.2 9.4 Semantics description Criticality YES YES YES YES EACH Assigned Criticality reject reject reject ignore reject IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID SAE Bearer Setup List > SAE Bearer Setup Item IEs >>SAE Bearer Identity >>Transport Layer Address >>GTP TEID SAE Bearer Failed to Setup List > SAE Bearer Failed to Setup Item IEs >>SAE Bearer ID >>Cause YES EACH ignore ignore - Range bound maxnoofSAEbearers Explanation Maximum no.4 9.2.2.3 Semantics description Criticality YES YES YES YES Assigned Criticality ignore reject reject ignore 3GPP .3 9. Direction: eNB → MME IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Cause Presence M M M M Range IE type and reference 9.2.2.3. of SAE bearer allowed towards one UE.3.2.2.1.2.Release 8 Range bound maxnoofSAEbearers 49 3GPP TS 36.2.4 9.1.1.2.3 9.2.2.1 9.2.3. the maximum value is 256.1 9.4.1.2 Range IE type and reference 9.1.2 9.4.0 (2008-03) Explanation Maximum no.1 9.1 9.2.

1.3.3.1.3 9.413 V8.1 9.4 9.1 9.2.2.2.3.1.2.3. 9. Direction: eNB → MME IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Presence M M M Range IE type and reference 9.3.2.1.2.1 9.3 9.9 UE CONTEXT MODIFICATION RESPONSE This message is sent by the eNB to confirm the performed UE context updates.1.1.1.4.Release 8 50 3GPP TS 36. Direction: MME → eNB IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Security Information Presence M M M O Range IE type and reference 9.1 9.2. Direction: MME → eNB IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Cause Presence M M FFS M Range IE type and reference 9.1.4.2.1.2.26 Semantics description Criticality YES YES YES YES Assigned Criticality reject reject reject reject 9.4 Semantics description Criticality YES YES YES Assigned Criticality reject reject reject 9. Direction: eNB → MME IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Presence M M M Range IE type and reference 9.0 (2008-03) 9.3.4 Semantics description Criticality YES YES YES Assigned Criticality reject reject reject 9.2.4 9.1.3 Semantics description Criticality YES YES YES YES Assigned Criticality reject reject reject ignore Editor’s Note: The presence of eNB UE S1AP ID IE in the UE CONTEXT RELEASE COMMAND is FFS until there is an agreement for the timing of S1 handover cancellation.1.7 UE CONTEXT RELEASE COMPLETE This message is sent by the eNB to confirm the release of the UE-associated S1-logical connection over the S1 interface.1.2.2. Direction: eNB → MME 3GPP .4.10 UE CONTEXT MODIFICATION FAILURE This message is sent by the eNB in case the performed UE context update is not successful.2.3.6 UE CONTEXT RELEASE COMMAND This message is sent by the MME to request the release of the UE-associated S1-logical connection over the S1 interface.4.2.3 9.4.3.3 9.8 UE CONTEXT MODIFICATION REQUEST This message is sent by the MME to provide UE Context information changes to the eNB.

3 9.1.5 9.9 FFS if this is mandatory and needed YES reject C. 3GPP .15 YES YES YES YES YES ignore reject reject ignore reject 9.0 (2008-03) Semantics description Criticality YES YES YES YES Assigned Criticality reject reject reject reject 9.4 9.2.413 V8.2.ifILTEto GERAN M 9.2.3.1.3 3GPP TS 36. IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Handover Type Presence M M M M <IntraLTE.1 9.1.ifILTEto UTRAN M 9. Direction: eNodeB → MME.5 9.1 Handover Signalling Messages HANDOVER REQUIRED This message is sent by the source eNodeB to the MME to request the preparation of resources at the target.1.2.1. This IE shall be present if the Handover Type IE is set to the “Value” LTEtoUTRAN.2.2. LTEtoGERAN> Range IE type and reference 9.4 9.1.7 It includes the UE RAN context YES reject C.1.1 9.1. This IE shall be present if the Handover Type IE is set to the “Value” LTEtoGERAN.1. LTEtoUTRAN.3 9.3.6 9.2.2.2.3 9.1.2.2.11 FFS if this is mandatory and needed Condition ifIntraLTE ifLTEtoUTRAN ifLTEtoGERAN Explanation This IE shall be present if the Handover Type IE is set to the “Value” IntraLTE.13 Semantics description Criticality YES YES YES YES Assigned Criticality reject reject reject reject Cause Source ID Target ID Direct Forwarding Path Availability Intra-LTE HO Information ListRequest > Source eNodeB to Target eNodeB Transparent Container LTE to UTRAN HO Information ListRequest > Source RNC To Target RNC Transparent Container LTE to GERAN HO Information ListRequest > Source BSS To Target BSS Transparent Container M M M O CifIntraLTE M 9.Release 8 IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Cause Presence M M M M Range 51 IE type and reference 9.2.1.3.1.1.1.2.5.2.2.3.

13 Semantics description Criticality YES YES YES YES Assigned Criticality reject reject reject reject SAE Bearers Subject to Forwarding List >SAE Bearers Subject to Forwarding Item IEs >> SAE Bearer ID >> DL Transport Layer Address >> DL GTP TEID O 1 to <maxnoof SAEbearers> M M M 9.1. This IE shall be present if the Handover Type IE is set to the “Value” LTEtoGERAN.2. This means that the existence of.10 FFS if this is mandatory and needed YES 9.3 9.1.1.2.12 FFS if this is mandatory and needed reject C. Condition ifIntraLTE ifLTEtoUTRAN ifLTEtoGERAN Explanation This IE shall be present if the Handover Type IE is set to the “Value” IntraLTE.5. IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Handover Type Presence M M M M <IntraLTE.2.0 (2008-03) 9.4 9.1 9.Release 8 52 3GPP TS 36. of SAE Bearers for one UE.2. Value is 256.2.2 9. Range bound maxnoofSAEbearers Explanation Maximum no.2 YES EACH YES ignore ignore reject 9. and the definition of the SAE Bearers Subject to Forwarding List IE is FFS.1.1.2 To deliver forwarded DL PDCP SDUs YES EACH - ignore ignore SAE Bearers to Release List >SAE Bearers to Release Item IEs >> SAE Bearer ID Intra-LTE HO Information ListResponse > Target eNodeB to Source eNodeB Transparent Container LTE to UTRAN HO Information ListResponse > Target RNC to Source RNC Transparent Container LTE to GERAN HO Information ListResponse > Target BSS to Source BSS Transparent Container O 1 to <maxnoof SAEbearers> M CifIntraLTE M 9.2.1.2.413 V8.2. LTEtoGERAN> Range IE type and reference 9.ifILTEto UTRAN M YES 9.2 HANDOVER COMMAND This message is sent by the MME to inform the source eNodeB that resources for the handover have been prepared at the target side.3.8 C. 3GPP .2.2.2.3.1.1. LTEtoUTRAN. Direction: MME → eNodeB.2.1. This IE shall be present if the Handover Type IE is set to the “Value” LTEtoUTRAN.1 9.2.ifILTEto GERAN M reject Editor’s Note: How to handle and control data forwarding is FFS.

if GERAN toLTE M 9.2.3 Semantics description Criticality YES YES YES YES Assigned Criticality reject reject reject ignore 9.8 9.2.13 Semantics description Criticality YES YES YES Assigned Criticality reject reject reject Cause SAE Bearers To Be Setup List >SAE Bearers To Be Setup Item IEs >> SAE Bearer ID >> Transport Layer Address >> GTP TEID >> SAE Bearer Level QoS Parameters M M 1 to <maxnoof SAEbearers> M M M M 9.2.15 To deliver UL PDUs Includes necessary QoS parameters - Intra-LTE HO Information ListRequest > Source eNodeB to Target eNodeB Transparent Container UTRAN to LTE HO Information ListRequest > Source RNC to Target RNC Transparent Container to GERAN to LTE HO Information ListRequest > Source BSS to Target BSS Transparent Container Serving PLMN Handover Restriction List CifIntraLTE M YES 9.1 9.1.1.1.2.4 9.2 9.1.1.2.9 FFS if this is mandatory and needed YES reject C. IE/Group Name Message Type MME UE S1AP ID Handover Type Presence M M M <IntraLTE.5.2.3 HANDOVER PREPARATION FAILURE This message is sent by the MME to inform the source eNodeB that the Handover Preparation has failed.1. Direction: MME → eNodeB.3 9.3.2.3 9.2.2.22 3GPP .1.11 FFS if this is mandatory and needed YES YES reject ignore O O 9.2.2.Release 8 53 3GPP TS 36.1.2.0 (2008-03) 9.4 HANDOVER REQUEST This message is sent by the MME to the target eNodeB to request the preparation of resources.1.1.1.3 YES YES EACH ignore ignore reject 9.1.1 9.7 reject C.5.2.3.1 9. IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Cause Presence M M M M Range IE type and reference 9.2.2.2 9.3.if UTRAN toLTE M YES reject 9. GERANtoLTE> Range IE type and reference 9. UTRANtoLTE.2.3.2. Direction: MME → eNodeB.1.1.2.413 V8.2.

Release 8

54

3GPP TS 36.413 V8.1.0 (2008-03)

Editor’s Note: The details of required IEs to indicate security parameters in the message (e.g., encryption and integrity protection information) are FFS.

Condition IfIntraLTE ifUTRANtoLTE ifGERANtoLTE

Explanation This IE shall be present if the Handover Type IE is set to the “Value” IntraLTE. This IE shall be present if the Handover Type IE is set to the “Value” UTRANtoLTE. This IE shall be present if the Handover Type IE is set to the “Value” GERANtoLTE. Explanation Maximum no. of SAE Bearers for one UE. Value is 256.

Range bound maxnoofSAEbearers

3GPP

Release 8

55

3GPP TS 36.413 V8.1.0 (2008-03)

9.1.5.5

HANDOVER REQUEST ACKNOWLEDGE

This message is sent by the target eNodeB to inform the MME about the prepared resources at the target. Direction: eNodeB → MME.
IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Presence M M M Range IE type and reference 9.2.1.1 9.2.3.3 9.2.3.4 Semantics description Criticality YES YES YES Assigned Criticality reject reject reject

allocated at the target eNodeB

Handover Type

M

<IntraLTE, UTRANtoLTE, GERANtoLTE> 1 to <maxnoof SAEbearers>

9.2.1.13

YES

reject

SAE Bearers Admitted List >SAE Bearers Admitted Item IEs >> SAE Bearer ID >> Transport Layer Address >> GTP TEID >> DL Transport Layer Address >> DL GTP TEID

O

YES EACH 9.2.1.2 9.2.2.1 9.2.2.2 9.2.2.1 9.2.2.2 To deliver forwarded DL PDCP SDUs. To deliver DL PDUs -

ignore reject

M M M O O

SAE Bearers Failed to Setup List >SAE Bearers Failed to Setup Item IEs >>SAE Bearer ID >>Cause Intra-LTE HO Information ListResponse > Target eNodeB to Source eNodeB Transparent Container

O 1 to <maxnoof SAEbearers> M M CifIntraLTE M 9.2.1.2 9.2.1.3

YES EACH YES It includes HO Command info for the UE YES

ignore ignore

reject

9.2.1.8

UTRAN to LTE HO Information ListResponse > Target RNC to Source RNC Transparent Container GERAN to LTE HO Information ListResponse > Target BSS to Source BSS Transparent Container

C- if UTRANtoL TE M

reject

9.2.1.10

FFS if this is mandatory and needed YES reject

C- if GERANto LTE M

9.2.1.12

FFS if this is mandatory and needed

3GPP

Release 8 Condition ifIntraLTE ifUTRANtoLTE ifGERANtoLTE

56

3GPP TS 36.413 V8.1.0 (2008-03)

Explanation This IE shall be present if the Handover Type IE is set to the “Value” IntraLTE. This IE shall be present if the Handover Type IE is set to the “Value” UTRANtoLTE. This IE shall be present if the Handover Type IE is set to the “Value” GERANtoLTE. Explanation Maximum no. of SAE Bearers for one UE. Value is 256.

Range bound maxnoofSAEbearers

9.1.5.6

HANDOVER FAILURE

This message is sent by the target eNodeB to inform the MME that the preparation of resources has failed. Direction: eNodeB → MME.
IE/Group Name Message Type MME UE S1AP ID Cause Presence M M M Range IE type and reference 9.2.1.1 9.2.3.3 9.2.1.3 Semantics description Criticality YES YES YES Assigned Criticality reject reject ignore

9.1.5.7

HANDOVER NOTIFY

This message is sent by the target eNodeB to inform the MME that the UE has been identified in the target cell and the S1 handover has been completed. Direction: eNodeB → MME.
IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Presence M M M Range IE type and reference 9.2.1.1 9.2.3.3 9.2.3.4 Semantics description Criticality YES YES YES Assigned Criticality ignore reject reject

3GPP

IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID SAE Bearer To Be Switched in Downlink List >SAE Bearers Switched in Downlink Item IEs >> SAE bearer Identity >> Transport layer address >> GTP TEID Presence M M M M 1 to <maxnoof SAEbearers> M M M 9.2.1.2.8 PATH SWITCH REQUEST This message is sent by the eNodeB to request the MME to switch DL GTP tunnel termination point(s) from one endpoint to another.9 PATH SWITCH REQUEST ACKNOWLEDGE This message is sent by the MME to inform the eNodeB that the path switch has been successfully completed in the EPC.3.Release 8 57 3GPP TS 36.2 9. Value is 256.5.1.2. Direction: MME → eNodeB. of SAE Bearers for one UE.1.2.1 9.1.3.3.2.5. Direction: MME → eNodeB.1.2.10 PATH SWITCH REQUEST FAILURE This message is sent by the MME to inform the eNodeB that a failure has occurred in the EPC during the Path switch request procedure.1.2.2. Direction: eNodeB → MME. 9.2 To deliver DL PDUs Range IE type and reference 9.2.3 9.11 HANDOVER CANCEL This message is sent by the source eNodeB to the MME to request the cancellation of an ongoing handover.2. IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Cause Presence M M M M Range IE type and reference 9.5.2.5.3 9.2.2. Direction: eNodeB → MME.2.1 9.3.1.2.1.0 (2008-03) 9.4 Semantics description Criticality YES YES YES Assigned Criticality reject reject reject 9.3 Semantics description Criticality YES YES YES YES Assigned Criticality reject reject reject ignore 9.1 9. 3GPP .413 V8.1 9.4 9.1. IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Presence M M M Range IE type and reference 9.3.3 9.1.4 Semantics description Criticality YES YES YES YES EACH Assigned Criticality reject reject reject ignore reject Range bound maxnoofSAEbearers Explanation Maximum no.3.

1.12 HANDOVER CANCEL ACKNOWLEDGE This message is sent by the MME to the source eNodeB to confirm that the ongoing handover was cancelled.1.2. IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Presence M M M Range IE type and reference 9.0 (2008-03) Semantics description Criticality YES YES YES YES Assigned Criticality reject reject reject ignore 9.4 9.3.1 9.5.2.4 Semantics description Criticality YES YES YES Assigned Criticality reject reject reject 9.3 9. 3GPP .413 V8.1. Direction: eNodeB → MME. Direction: MME → eNodeB.1.2.1.2.5.2.3.Release 8 IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Cause Presence M M M M Range 58 IE type and reference 9.2.1.3 9.3.3.13 eNB STATUS TRANSFER This message is sent by the source eNodeB to transfer the PDCP SN receiver and transmitter status.2.1 9.3 3GPP TS 36.

3.11 9.2.14 MME STATUS TRANSFER This message is sent by the MME to transfer the PDCP SN receiver and transmitter status.5.3 9..413 V8.Release 8 IE/Group Name Message Type MME S1-AP UE Identity eNB S1-AP UE Identity SAE Bearers Subject to Status Transfer List >SAE Bearers Subject to Status Transfer Item >> SAE bearer Identity >> LIS HFN Presence M M M M Range 59 IE type and reference 9.0 (2008-03) Semantics description Criticality YES YES YES YES EACH BIT STRING (SIZE (8)) INTEGER – PDCP HFN that the target eNB should assign for the LIS Last in sequence received UL PDCP Sequence Number PDCP-HFN that the target eNB should assign for the next DL SDU not having an SN yet PDCP-SN that the target eNB should assign for the next DL SDU not having an SN yet – Assigned Criticality ignore reject reject ignore ignore – – 1 to <maxnoof SAEbearers> M M >> LIS M INTEGER (0..1. Direction: MME → eNodeB 3GPP . 9.3.1.4095) – – >> DL PDCP-HFN Next to Assign M INTEGER – – >> DL PDCP-SN Next to Assign M INTEGER (0.2.2.4 3GPP TS 36.4095) – – Editor’s note: it is FFS if the procedure may be triggered more than once time during the handover preparation.

0 (2008-03) Semantics description eNB UE X2AP ID allocated at the old eNodeB eNB UE X2AP ID allocated at the new eNodeB Criticality YES YES Assigned Criticality ignore reject eNB S1-AP UE Identity M INTEGER (0..1..4095) YES reject SAE Bearers Subject to Status Transfer List >SAE Bearers Subject to Status Transfer Item >> SAE bearer Identity >> LIS HFN M 1 to <maxnoof SAEbearers> YES EACH BIT STRING (SIZE (8)) INTEGER – PDCP HFN that the target eNB should assign for the LIS Last in sequence received UL PDCP Sequence Number PDCP-HFN that the target eNB should assign for the next DL SDU not having an SN yet PDCP-SN that the target eNB should assign for the next DL SDU not having an SN yet – ignore ignore – – M M >> LIS M INTEGER (0.413 V8.15 INTEGER (0.4095) 3GPP TS 36..2.4095) – – 3GPP .Release 8 IE/Group Name Message Type MME S1-AP UE Identity Presence M M Range 60 IE type and reference 9..4095) – – >> DL PDCP-HFN Next to Assign M INTEGER – – >> DL PDCP-SN Next to Assign M INTEGER (0.

Direction: eNB → MME 3GPP .2.Release 8 61 3GPP TS 36.1.7 9.2.1.2. Value is FFS.4 9.13 9.7.2.2 DOWNLINK NAS TRANSPORT This message is sent by the MME and is used for carrying NAS information over the S1 interface.2.1 9.2.1.3.1.1.2.413 V8.3.3.2. 9.2.0 (2008-03) 9.2.3 UPLINK NAS TRANSPORT This message is sent by the eNB and is used for carrying NAS information over the S1 interface.10 9.1 NAS Transport Messages INITIAL UE MESSAGE This message is sent by the eNB to transfer the initial layer 3 message to the MME over the S1 interface.6 PAGING Presence M M M M M 1 to < Range IE type and reference 9.1 9.7.3.17 Semantics description Criticality YES YES YES YES YES YES EACH Assigned Criticality ignore ignore ignore ignore ignore ignore ignore IE/Group Name Message Type UE Identity Index value UE Paging ID Paging DRX Paging Cause List of TAIs >TAI List Item >>TA Identity maxnoofTAI > M FFS Range bound maxnoofTAI Explanation Maximum no.1.2. Direction: MME → eNB IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID NAS-PDU Serving PLMN Handover Restriction List Presence M M M M O O Range IE type and reference 9. Direction: eNB → MME IE/Group Name Message Type eNB UE S1AP ID NAS-PDU TAI Presence M M M M Range IE type and reference 9.7.3.2. 9.2.1.3.1.1.3.3 9.3.4 9.2. of TAI Identity for one UE.16 9.5 9.8 9.1.1.3.7 Semantics description Criticality YES YES YES YES Assigned Criticality ignore reject reject reject Indicating the Tracking Area from which the UE has sent the NAS message.5 9.22 Semantics description Criticality YES YES YES YES YES YES Assigned Criticality ignore reject reject reject reject ignore 9.2.1 9.1.

2.3.1.1.3.3.1.8.3. Direction: eNB → MME and MME → eNB.3 ERROR INDICATION This message is sent by both the MME and the eNB and is used to indicate that some error has been detected in the node.1.1.2.2. Direction: MME → eNB and eNB → MME 3GPP . IE/Group Name Message Type Criticality Diagnostics Presence M O Range IE type and reference 9.7.21 Semantics description Criticality YES YES Assigned Criticality reject ignore 9.3 9.2.1.8 9.3.8.2.4 9.1. Direction: eNB → MME IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID NAS-PDU Cause Presence M M M M M Range IE type and reference 9.1. Direction: MME → eNB and eNB → MME IE/Group Name Message Type Cause Presence M M Range IE type and reference 9.1 9.4 9.8.1 Management messages RESET This message is sent by both the MME and the eNB and is used to request that the other node be reset.1.2 RESET ACKNOWLEDGE This message is sent by both the MME and the eNB as a response to a RESET message.2.Release 8 IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID NAS-PDU Presence M M M M Range 62 IE type and reference 9.3 9.2.3.4 NAS NON DELIVERY INDICATION This message is sent by the eNB and is used for reporting the non delivery of a NAS PDU previously received within a DOWNLINK NAS TRANSPORT message over the S1 interface.1 9.2.5 3GPP TS 36.5 9.2.3 Semantics description Criticality YES YES YES YES YES Assigned Criticality ignore reject reject ignore ignore 9.0 (2008-03) Semantics description Criticality YES YES YES YES Assigned Criticality ignore reject reject reject 9.1.1.3 Semantics description Criticality YES YES Assigned Criticality reject ignore 9.1 9.2.1 9.413 V8.2.1.2.2.1.

2. of TAIs. Direction: MME → eNB IE/Group Name Message Type MME Name Served PLMNs Presence M M 1.2.<maxnoofP LMNsPer MME> M OCTET STRING (SIZE (3)) 9. Direction: eNB → MME IE/Group Name Message Type eNB Global ID eNB Name Supported TAIs Presence M M M 1.2.3..2. 9.3.1. Value is FFS.<maxnoofBPLM Ns> M OCTET STRING Broadcast PLMNs OCTET STRING (SIZE (3)) - Range bound maxnoofTAIs Range bound maxnoofBPLMNs Explanation Maximum no.1.0 (2008-03) Semantics description Criticality YES YES YES YES YES Assigned Criticality ignore ignore ignore ignore ignore 9.4 S1 SETUP REQUEST This message is sent by the eNB to transfer information for a TNL association.2.1 OCTET STRING Semantics description FSS if IE is optional Criticality YES YES GLOBAL Assigned Criticality reject ignore reject >PLMN Identity - GUMMEI M YES reject 3GPP .8.3.1.21 3GPP TS 36.2.1.1.1.4 9.9 Range IE type and reference 9.Release 8 Presence IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID Cause Criticality Diagnostics M O O O O Range 63 IE type and reference 9.2.3 9.<maxnoofTAIs> Range IE type and reference 9.1.2.1.8.5 S1 SETUP RESPONSE This message is sent by the MME to transfer information for a TNL association. of Broadcasted PLMNs.. Value is FFS. Explanation Maximum no.1 OCTET STRING OCTET STRING Semantics description Coding FFS FSS if IE is optional Supported TAIs in the eNB Criticality YES YES YES GLOBAL Assigned Criticality reject reject ignore reject >TAI >Broadcast PLMNs >>PLMN Identity M 1.413 V8.1 9..3 9.

2 UPLINK S1 CDMA2000 TUNNELING This message is sent by the eNB and is used for carrying CDMA2000 information over the S1 interface.1. Direction: MME → eNB IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID CDMA2000-PDU Presence M M M M Range IE type and reference 9.2.1 9. Value is FFS.1.1 9.2.1.9.3.2.2.1.1 9.10 UE CAPABILITY INFO INDICATION This message is sent by the eNB to provide UE Radio Capability information to the MME.1.1.1. of PLMNs per MME.3 9.1.3. Direction: MME → eNB IE/Group Name Message Type Cause Time to wait Presence M M O Range IE type and reference 9.2.1.2.1. Direction: eNB → MME 3GPP .3 9.8.23 Semantics description Criticality YES YES YES YES YES YES Assigned Criticality ignore reject reject reject reject reject 9. 9.23 Semantics description Criticality YES YES YES YES Assigned Criticality ignore reject reject reject 9.3.1.6 S1 SETUP FAILURE This message is sent by the MME to indicate S1 Setup failure.9 9.3 OCTET STRING Semantics description Criticality YES YES YES Assigned Criticality reject ignore ignore 9.9.4 9.Release 8 Range bound maxnoofPLMNsPer MME 64 3GPP TS 36.1.1 S1 CDMA2000 Tunneling Messages DOWNLINK S1 CDMA2000 TUNNELING This message is sent by the MME and is used for carrying CDMA2000 information over the S1 interface.413 V8.2.24 9.2.2.4 9.1.2.2.0 (2008-03) Explanation Maximum no.2.3.25 9. Direction: eNB → MME IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID CDMA2000 RAT Type CDMA2000 Sector ID CDMA2000-PDU Presence M M M M M M Range IE type and reference 9.1.

if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere.413 V8.1.Release 8 IE/Group Name Message Type MME UE S1AP ID eNB UE S1AP ID UE Radio Capability Presence M M M M Range 65 IE type and reference 9.2 9.0 Information Element Definitions General Editor’s Note: Information element definitions. In case there is contradiction between the tabular format in subclause 9.2.1 9. 9.2.2 and the ASN. The last bit (rightmost bit) contains the least significant bit (LSB). It is mandatory for all messages.2. When specifying information elements which are to be represented by bitstrings.1 shall take precedence.1. except for the definition of conditions for the presence of conditional elements.1 Radio Network Layer Related IEs Message Type The Message Type IE uniquely identifies the message being sent.1 definition is presented in subclause 9. the ASN.1.2 presents the S1AP IE definitions in tabular format.2.3. where the tabular format shall take precedence.3.1.1 definition.3. 3GPP .27 3GPP TS 36. the following principle applies with regards to the ordering of bits: The first bit (leftmost bit) contains the most significant bit (MSB). the first bit of the bitstring contains the first bit of the concerned information.3 9. When importing bitstrings from other specifications.2.2.0 (2008-03) Semantics description Criticality YES YES YES YES Assigned Criticality ignore reject reject ignore 9.1 9. The corresponding ASN.2. Subclause 9.4 9.

2.Release 8 IE/Group Name Message Type >Procedure Code Presence Range 66 IE type and reference 3GPP TS 36. UE Context Release. Handover Notification. UE Context Release Request . Unsuccessful Outcome.2. 3GPP . UE Context Modification. Paging.1. eNB Status Transfer.413 V8.1. Downlink NAS transport.2 SAE Bearer ID This element uniquely identifies a radio access bearer for a specific CN domain for a particular UE. which makes the SAE Bearer ID unique over one S1 connection. Initial Context Setup. The SAE Bearer ID shall remain the same for the duration of the SAE Bearer even if the UE-associated logical S1-connection is released or moved using S1 handover IE/Group Name SAE Bearer ID Presence M Range IE type and reference BIT STRING (8) Semantics description To be checked (FFS) 9. NAS Non Delivery Indication. S1 Setup.3 Cause The purpose of the Cause IE is to indicate the reason for a particular event for the S1AP protocol. Initial UE Message. Handover Resource Allocation. …) 9. Uplink S1 CDMA2000 Tunneling. Handover Cancel. Reset.1. Patch Switch Request. SAE Bearer Release Request. Uplink NAS transport. SAE Bearer Release. SAE Bearer Modify. M >Type of Message M (Handover Preparation. Error Indication. Successful Outcome. SAE Bearer Setup. UE Capability Info Indication.0 (2008-03) Semantics description Assumed max no of messages is 256. Downlink S1 CDMA2000 Tunneling. MME Status Transfer…) CHOICE (Initiating Message.

.. Handover triggered.413 V8. Detach. "not supported" cause values indicate that the related capability is missing..) ENUMERATED (Normal Release.Release 8 IE/Group Name CHOICE Cause Group >Radio Network Layer >>Radio Network Layer Cause Presence M M Range 67 3GPP TS 36. Handover Cancelled. Unspecified.. 3GPP . but insufficient resources were available to perform the requested action. "not available" cause values indicate that the related capability is present. Abstract Syntax Error (Falsely Constructed Message). Not enough User Plane Processing Resources.) >Transport Layer >>Transport Layer Cause M > NAS >> NAS Cause M >Protocol >>Protocol Cause M >Misc >>Miscellaneous Cause M The meaning of the different cause values is described in the following table.) ENUMERATED (Control Processing Overload.1. Release due to E-UTRAN Generated Reason. Semantic Error.0 (2008-03) IE Type and Reference Semantics Description ENUMERATED (Unspecified. On the other hand.. Abstract Syntax Error (Reject). . Authentication failure. In general.. Hardware Failure. Unspecified.. …) ENUMERATED (Transfer Syntax Error. Successful Handover. Message not Compatible with Receiver State. Abstract Syntax Error (Ignore and Notify). …) ENUMERATED (Transport Resource Unavailable. Unspecified. O&M Intervention. Unspecified. TX2RELOCOverall Expiry..

The action is due to detach.0 (2008-03) Meaning Sent for radio network layer cause when none of the specified cause values applies The action is due to a handover that has been triggered. The received message included a semantic error. The reason for the action is cancellation of Handover Meaning The required transport resources are not available Sent when none of the above cause values applies but still the cause is Transport Network Layer related Meaning The release is normal The action is due to authentication failure. Transport Network Layer.4 Trace activation Defines parameters related to a trace activation.2.413 V8.1. Sent when none of the above cause values applies but still the cause is NAS related NAS cause Normal Release Authentication Failure Detach Unspecified Protocol cause Transfer Syntax Error Abstract Syntax Error (Reject) Abstract Syntax Error (Ignore And Notify) Message Not Compatible With Receiver State Semantic Error Abstract Syntax Error (Falsely Constructed Message) Unspecified Miscellaneous cause Control Processing Overload Not Enough User Plane Processing Resources Available Hardware Failure O&M Intervention Unspecified Failure Meaning The received message included a transfer syntax error. 9. Sent when none of the above cause values applies but still the cause is Protocol related Meaning Control processing overload No enough resources are available related to user plane processing. Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer. 3GPP . Release is initiated due to E-UTRAN generated reason. The received message included an abstract syntax error and the concerning criticality indicated "ignore and notify". The timer guarding the handover that takes place over X2 has abnormally expired. NAS or Protocol.Release 8 Radio Network Layer cause Unspecified Handover triggered TX2RELOCOverall Expiry Release due to E-UTRAN generated reason Handover Cancelled Transport Layer cause Transport Resource Unavailable Unspecified 68 3GPP TS 36.1. The received message was not compatible with the receiver state. The received message included an abstract syntax error and the concerning criticality indicated "reject". Action related to hardware failure The action is due to O&M intervention. The received message contained IEs or IE groups in wrong order or with too many occurrences.

5 Source ID The Source ID IE identifies the source for a handover.413 V8.1.2..) ENUMERAT ED( minimum..) >Trace depth M Defined in [6] 9. vendorMediu m.Release 8 IE/Group Name Trace Reference Interfaces To Trace >Interface M Presence M Range 69 IE type and reference OCTET STRING (3) 3GPP TS 36.. . IE/Group Name Source ID >Source eNB-ID Presence Range IE type and reference Semantics description Criticality Assigned Criticality – FFS 3GPP .1. x2 Uu. medium..0 (2008-03) Semantics description Criticality Assigned Criticality 1 to <maxInterfaces> ENUMERAT ED (s1.. vendorMaxi mum. maximum. vendorMinim um.

1111 used as filler digit.1 If the Extended RNC-ID IE is included in the Target ID IE.413 V8.digits 0 to 9. two digits per octet. Semantics description Criticality Assigned Criticality 9.14 YES reject >CGI >> PLMN identity M OCTET STRING (SIZE (3)) - >> LAC >>CI >>RAC M M O OCTET STRING (2) OCTET STRING (2) 9.1. 0000 and FFFE not allowed. the target eNB-ID (for intra SAE/LTE).2. The Extended RNCID IE shall be used if the RNC identity has a value larger than 4095.1. 3GPP .3.1. the RNC-ID (for SAE/LTE-UMTS handover) or the Cell Global ID of the handover target (in case of IE/Group Name Choice Target ID >Target eNB-ID >Target RNC-ID >>LAI >>RAC >>RNC-ID Presence Range IE type and reference FFS M O M 9. the RNC-ID IE shall be ignored.bits 8 to 5 of octet n encoding digit 2n -The PLMN identity consists of 3 digits from MCC followed by either -a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC).4095) >>Extended RNCID O 9.2 YES ignore SAE/LTE to GERAN A/Gb mode handover).3.. This IE is transparent to the EPC.6 Target ID The Target ID IE identifies the target for the handover.bits 4 to 1 of octet n encoding digit 2n-1 . This IE is used for the intra SAE/LTE handover case.g.1. The target ID may be e.2. .2 INTEGER (0.2.2.0 (2008-03) 9.3.2. encoded 0000 to 1001.Release 8 70 3GPP TS 36. 9.7 Source eNB to Target eNB Transparent Container The Source eNB to target eNB Transparent Container IE is an information element that is produced by the source eNB and is transmitted to the target eNB.2. . .

2. Value is 256.018. of SAE Bearers for one UE. This container is used for inter 3GPP RAT handovers from SAE/LTE to GERAN A/Gb mode and vice versa.11 Source BSS to Target BSS Transparent Container This container is used to transparently pass radio related information between the handover source and the handover target through the EPC.10 Target RNC to Source RNC Transparent Container This container is used to transparently pass radio related information between the handover target and the handover source through the EPC. This container is used for inter 3GPP RAT handovers from SAE/LTE to GERAN A/Gb mode and vice versa. 9.12 Target BSS to Source BSS Transparent Container This container is used to transparently pass radio related information between the handover source and the handover target through the EPC.018.1. This container is used for inter 3GPP RAT handovers from SAE/LTE to UTRAN and vice versa.3.1. Content FFS.2. This IE is transparent to EPC.413 V8. Content FFS. This container is used inter 3GPP RAT handovers from SAE/LTE to UTRAN and vice versa. 9. 3GPP . Content FFS. This IE is defined in TS 25.14 - - - - Range bound maxnoofSAEbearers Explanation Maximum no. Content FFS. This IE is used for the intra SAE/LTE handover case. This IE is defined in TS 48.1. This IE defined in TS 25.9 Source RNC to Target RNC Transparent Container This IE is used to transparently pass radio related information between the handover source and the handover target through the EPC. 9.2.1.1. 9.413.413.2. 9.2.8 Target eNB to Source eNB Transparent Container The Target eNB to Source eNB Transparent Container IE is an information element that is produced by the target eNB and is transmitted to the source eNB.Release 8 IE/Group Name RRC Container SAE Bearers Information List > SAE Bearers Information Item >> SAE Bearer ID Presence M M 1 to <maxnoof SAEbearers > 71 Range IE type and reference OCTET STRING 3GPP TS 36.1.2. This IE is defined in TS 48.0 (2008-03) Semantics description Criticality YES EACH Assigned Criticality ignore ignore M >> DL Forwarding O BIT STRING (SIZE (8)) 9. Content FFS.

LTEtoGERAN. IE/Group Name Paging DRX Presence M Range IE type and reference FFS Semantics description Criticality Assigned Criticality 3GPP .15 SAE Bearer Level QoS Parameters This IE defines the QoS to be applied to a SAE bearer.2.13 Handover Type This IE indicates which kind of handover was triggered in the source side.1.: Either GBR or non-GBR Bearer 9.413 V8. LTEtoUTRAN. Editor’s Note: The definition is FFS and should be aligned to RRC 36.2.331 referenced as [xx].. IE/Group Name SAE Bearer Level QoS Parameters >Label Presence Range IE type and reference Semantics description M INTEGER (1.18 >Allocation and Retention Priority >SAE Bearer Type FFS M Coded as specified in TS 23.2. UTRANtoLTE.1..1.16 Paging DRX This IE indicates the Paging DRX as defined in [xx].2.1. IE/Group Name Handover Type Presence M Range IE type and reference ENUMERATED (IntraLTE.1. IE/Group Name Extended RNC-ID Presence M Range IE type and reference INTEGER (4096.14 Extended RNC-ID The Extended RNC-ID is used to identify an RNC. Desc.1.2.256) FFS 9.0 (2008-03) 9. which will be defined in SA2 The ARP definition is left FFS in SA2.xxx.6553 5) Semantics description The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. 9.Release 8 72 3GPP TS 36. GERANtoTLE) Semantics description 9. Note: Application of the Extended RNC-ID IE to very large networks is FFS.

Terminating Background Call.. Terminating High Priority Signalling) Semantics description Criticality Assigned Criticality 9.413 V8.1.2.2.2.19 SAE Bearer Bit Rate 9.: to be added Desc. .19 SAE Bearer Bit Rate 3GPP . Terminating Interactive Call.17 Paging Cause This element indicates the cause for paging a UE. Terminating Low Priority Signalling.2. IE/Group Name Paging Cause Presence M Range IE type and reference ENUMERAT ED( Termina ting Conversatio nal Call.1.1.2.1.19 SAE Bearer Bit Rate 9.Release 8 73 3GPP TS 36.: to be added 9.19 SAE Bearer Bit Rate 9.18 SAE Bearer Type IE/Group Name Choice SAE Bearer Type > GBR bearer >> SAE Bearer Maximum Bit Rate Downlink Presence Range IE type and reference Semantics description M >> SAE Bearer Maximum Bit Rate Uplink >> SAE Bearer Guaranteed Bit Rate Downlink >> SAE Bearer Guaranteed Bit Rate Uplink > Non-GBR bearer >> Non GBR bearer M M M SAE Bearer Bit Rate SAE Bearer Bit Rate 9.2.1. Terminating Streaming Call.19 ENUMERAT ED (Non GBR bearer.…) Desc..1.: to be added Desc.1.: to be added Desc.1.2.0 (2008-03) 9..

21 Criticality Diagnostics The Criticality Diagnostics IE is sent by the eNB or the MME when parts of a received message have not been comprehended or were missing.2.: to be added >Aggregate Maximum Bit Rate Downlink >Aggregate Maximum Bit Rate Uplink M M SAE Bearer Bit Rate 9.000) 3GPP TS 36.1.1.2. (see Annex A. divided by the duration of the period.: to be added 9.1.0 (2008-03) Semantics description Desc.0 00. or if the message contained logical errors.19 Desc.: This IE indicates the maximum number of bits delivered by E-UTRAN and to E-UTRAN within a period of time. For further details on how to use the Criticality Diagnostics IE.: Applicable for non-GBR SAE Bearers.1.19 SAE Bearer Bit Rate 9..2 – FFS).413 V8.10.2.20 Aggregate Maximum Bit Rate IE/Group Name Aggregate Maximum Bit Rate Presence Range IE type and reference Semantics description Desc.provided at initial context setup Desc.Release 8 IE/Group Name SAE Bearer Bit Rate Presence 74 Range IE type and reference INTEGER (0.000.1. it contains information about which IEs were not comprehended or were missing. 3GPP . When applicable.2. The unit is: bit/s 9.

2. and not within the response message of the same procedure that caused the error The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication procedure. successful outcome. ignore. notify) INTEGER (0. notify) 0 to <maxnoof errors> This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure).65535) The IE Criticality is used for reporting the criticality of the triggering IE. it shall overwrite previously received restriction information. If the eNB receives the Handover Restriction List. The value 'ignore' shall not be used. missing. ignore.Release 8 IE/Group Name Criticality Diagnostics >Procedure Code O Presence Range 75 IE type and reference 3GPP TS 36. The value for maxnooferrors is 256. outcome) ENUMERATED( reject.22 Handover Restriction List This IE defines area roaming or access restrictions for handover.255) Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure..1.413 V8. …) Range bound maxnooferrors Explanation Maximum no. >Triggering Message O >Procedure Criticality O ENUMERATED( initiating message. of IE errors allowed to be reported with a single message. 9. Information Element Criticality Diagnostics >IE Criticality M ENUMERATED( reject.1. 3GPP .. The IE ID of the not understood or missing IE >IE ID M >Type of Error M ENUMERATED( not understood. unsuccessful outcome.0 (2008-03) Semantics description INTEGER (0.

<maxnoofFor bLACs> M O 9.3.. Maximum no. 9.. …) inter-3GPP RAT access restrictions Range bound maxnoofEPLMNs maxnooffEPLMNsPlusOne maxnoofforbiddenTAIs maxnoofforbiddenLACs Explanation Maximum no. of equivalent PLMN Ids plus one. Value is 256. Value is 16. IE/Group Name CDMA2000-PDU Presence M Range IE type and reference OCTET STRING Semantics description 9.2.1.2. Maximum no.3.1. of forbidden Location Area Codes. 3GPP .413 V8. Value is 256. UTRAN.2. 1xRTT …) Semantics description This IE is used to identify which CDMA2000 RAT the tunnelled CDMA2000 signalling is associated with. of forbidden Tracking Area Identities. Maximum no.008]. This list corresponds to the list of “equivalent PLMNs” as defined in [TS 24.2..<maxnoofFor bTAIs> M 0.Release 8 IE/Group Name Equivalent PLMNs Presence Range 76 IE type and reference 3GPP TS 36.. of equivalent PLMN Ids.<maxnoofEPL MNsPlusOne> M 1.1.7 OCTET STRING inter-3GPP RAT roaming restrictions 9. GERAN.3.24 CDMA2000 RAT Type This information element .2.2.8 intra LTE roaming restrictions 9.0 (2008-03) Semantics description Allowed PLMNs together with Serving PLMN.<maxnoofEPL MNs> >PLMN Identity Forbidden TAs >PLMN Identity >Forbidden TAIs >>TAI Forbidden LAs >PLMN Identity >Forbidden LACs >>LAC Forbidden inter RATs M 0.<maxnoofEPL MNsPlusOne> M 1. IE/Group Name CDMA2000 RAT Type Presence M Range IE type and reference ENUMERATED (HRPD. along with the CDMA2000 Sector ID IE is used for routing the tunnelled CDMA2000 message to the proper destination node in the CDMA2000 RAT. 9.8 0. Value is 15.3..23 CDMA2000-PDU This information element contains a CDMA2000 message between the UE and CDMA2000 RAT that is transferred without interpretation in the eNB.8 OCTET STRING(2) ENUMERATED( ALL.

413 V8.26 Security Information The purpose of the Security Information IE is to indicate the AS security key. 9. [EUTRAN spec].1.27 UE Radio Capability This IE contains UE Radio Capability information. IE/Group Name AS security key Presence M Range IE Type and Reference BIT STRING (128) Semantics Description 9.331 9.2.160.Release 8 77 3GPP TS 36.25 CDMA2000 Sector ID This information element . 9. It should pass it to the transport layer for interpretation.0 (2008-03) 9.2. For details on the Transport Layer Address.2 9. The CDMA2000 Reference Cell ID is statically configured in the eNB.. 3GPP .1.1.2.2. IE/Group Name UE Radio Capability Presence M Range IE Type and Reference OCTET STRING Semantics Description FFS: reference to TS 36.2. IE/Group Name Transport Layer Address This information element is an IP address to be used for the user plane transport.2.2 GTP-TEID This information element is the GTP Tunnel Endpoint Identifier to be used for the user plane transport between eNB and the serving gateway. along with the RAT Type IE is used for routing the tunnelled CDMA2000 message to the proper destination node in the CDMA2000 RAT.2. see ref.2. IE/Group Name CDMA2000 Sector ID Presence M Range IE type and reference OCTET STRING Semantics description This IE is set to CDMA2000 Reference Cell ID corresponding to the HRPD/1xRTT sector under the HRPD AN/1xBS to which the eNB has initiated the UE to handover to.1 Transport Network Layer Related IEs Transport Layer Address Presence M Range IE type and reference BIT STRING (1.1. …) Semantics description The Radio Network Layer is not supposed to interpret the address information.

two digits per octet.3 9. IE/Group Name LAI >PLMN identity Presence Range IE type and reference OCTET STRING (SIZE (3)) Semantics description M .4095) Semantics description Type and range FFS 3GPP .digits 0 to 9.bits 4 to 1 of octet n encoding digit 2n-1 .2.3.0 (2008-03) Semantics description 9.3 MME UE S1AP ID The MME UE S1AP ID uniquely identify the UE association over the S1 interface within the MME. >LAC M OCTET STRING (2) 9.bits 8 to 5 of octet n encoding digit 2n -The PLMN identity consists of 3 digits from MCC followed by either -a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC).2. IE/Group Name RAC Presence M Range IE type and reference OCTET STRING (1) Semantics description 9. 0000 and FFFE not allowed.1111 used as filler digit.2. .Release 8 IE/Group Name GTP TEID Presence M Range 78 IE type and reference OCTET STRING (4) 3GPP TS 36.3.1. .1 NAS Related IEs LAI This element is used to uniquely identify a Location Area.2 RAC This element is used to identify a Routing Area within a Location Area.3. encoded 0000 to 1001. IE/Group Name MME UE S1AP ID Presence M Range IE type and reference INTEGER (0 . It is used for PS services..2.413 V8.

IE/Group Name MMEC M-TMSI Presence M M Range IE type and reference 9. IE/Group Name NAS-PDU Presence M Range IE type and reference OCTET STRING Semantics description 9.3. 9.3.4095) Semantics description Type and range FFS 9. session management. supplementary services.3. IE/Group Name TAI Presence M Range IE type and reference OCTET STRING Semantics description 9.8 PLMN Identity This information element indicates the PLMN Identity.12 OCTET STRING (SIZE (4)) Semantics description Criticality Assigned Criticality M-TMSI is unique within MME that allocated it.2. used for security reasons to hide the identity of a subscriber.3. IE/Group Name eNB UE S1AP ID Presence M Range IE type and reference INTEGER (0 .3.413 V8.2.4 eNB UE S1AP ID The eNB UE S1AP ID uniquely identify the UE association over the S1 interface within the eNB.2.3..2.5 NAS-PDU This information element contains an EPC – UE or UE – EPC message that is transferred without interpretation in the eNB.2. short message service and mobility management messages. Typically it contains call control.6 S-TMSI Temporary Mobile Subscriber Identity.0 (2008-03) 9.7 TAI This element is used to uniquely identify a Tracking Area.2.1. 3GPP .Release 8 79 3GPP TS 36.

bits 8 to 5 of octet n encoding digit 2n -The Selected PLMN identity consists of 3 digits from MCC followed by either -a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC).Release 8 IE/Group Name PLMN identity Presence M 80 Range 3GPP TS 36. . two digits per octet. . 9.3.10 UE Identity Index value IE/Group Name UE identity Index Value Presence M Range IE type and reference OCTET STRING Semantics description IMSI mod L as defined in FFS.digits 0 to 9.2. IE/Group Name GUMMEI >PLMN identity Presence Range IE type and reference OCTET STRING (SIZE (3)) Semantics description M .bits 4 to 1 of octet n encoding digit 2n-1 .11 IMSI 3GPP .2.1111 used as filler digit.digits 0 to 9.0 (2008-03) IE type and reference OCTET STRING (SIZE (3)) Semantics description .3.1111 used as filler digit.bits 8 to 5 of octet n encoding digit 2n -The Selected PLMN identity consists of 3 digits from MCC followed by either -a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC). encoded 0000 to 1001. 9.2. encoded 0000 to 1001.1. FFS FFS >MME Group ID >MME code M M OCTET STRING (2) OCTET STRING (1) 9. two digits per octet. .413 V8. .3.9 GUMMEI This information element indicates the global unique MME identity.bits 4 to 1 of octet n encoding digit 2n-1 .

Release 8 IE/Group Name IMSI Presence M Range 81 IE type and reference OCTET STRING (SIZE (3.3.2.413 V8.12 MMEC This element represents the MME Code to uniquely identify a MME within an MME pool area.0 (2008-03) Semantics description . .1.2. IE/Group Name DL Forwarding >DL Forwarding Presence Range IE type and reference ENUMERATED (DL forwarding proposed. When the IMSI is made of an odd number of digits. …) Semantics description M 3GPP .3..13 UE Paging Identity This IE represents the Identity with which the UE is paged. . The filler digit shall then be consequently encoded as bit 8 to 5 of octet N. the filler digit shall be added at the end to make an even number of digits of length 2N.1111 used as filler digit.2.2. two digits per octet.11 9. IE/Group Name Choice UE Paging Identity >IMSI >S-TMSI M M 9.2.6 Presence Range IE type and reference Semantics description 9.8)) 3GPP TS 36. IE/Group Name MMEC Presence M Range IE type and reference OCTET STRING (SIZE (1)) Semantics description 9.14 DL Forwarding This element indicates that the SAE bearer is proposed for forwarding of downlink packets.3. 9.bit 8 to 5 of octet n encoding digit 2n -Number of decimal digits shall be from 6 to 15 starting with the digits from the PLMN identity. encoded 0000 to 1001.3.bit 4 to 1 of octet n encoding digit 2n-1 .digits 0 to 9.3.

413 V8.Release 8 82 3GPP TS 36. …) Semantics description 3GPP .0 (2008-03) 9. EPC behaviour on receipt of this IE is specified in [x2].1.2.15 Direct Forwarding Path Availability The availability of a direct forwarding path shall be determined by the source eNB. IE/Group Name Direct Forwarding Path Availability Presence M Range IE type and reference ENUMERATED (Direct Path Available.3.

The ASN. If a S1AP message that is not constructed as defined above is received.1 definition in this subclause and the tabular format in subclause 9.1 - Usage of private message mechanism for non-standard use The private message mechanism for non-standard use may be used: for special operator.6. a sending entity shall construct a S1AP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id.1. to implement and evaluate new algorithms/features before such features are proposed for standardisation.0 (2008-03) 9.0 Message and Information Element Abstract Syntax (with ASN. The private message mechanism shall not be used for basic functionality.1 and 9. for this version of the standard.e.Release 8 83 3GPP TS 36. this shall be considered as Abstract Syntax Error.1 definition specifies the structure and content of S1AP messages.g.3. An IE may appear at most once if the presence field in an object has value "optional" or "conditional". Such functionality shall be standardised.1 definition conforms with [4] and [5].3.1. S1AP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1 definition the list definition is separated into two parts. the ASN.3 presents the Abstract Syntax of S1AP protocol with ASN. If in a tabular format there is multiplicity specified for an IE (i.1.413 V8.3 9. where the tabular format shall take precedence.3..1) General S1AP ASN. The first part defines an IE container list where the list elements reside. The IE container list appears as an IE of its own.1 shall take precedence. 9. then the different occurrences have different IE ids): • • IEs shall be ordered (in an IE container) in the order they appear in object set definitions. 3GPP . an IE list) then in the corresponding ASN. the functionality required for a complete and high-quality specification in order to guarantee multivendor interoperability.2. e. For this version of the standard an IE container list may contain only one kind of list elements. Object set definitions specify how many times IEs may appear.e. In case there is contradiction between the ASN. and the message shall be handled as defined for Abstract Syntax Error in subclause 10. If one IE needed to appear more than once in one object set. except for the definition of conditions for the presence of conditional elements.(and/or vendor) specific features considered not to be part of the basic functionality. The second part defines list elements. Subclause 9. An IE shall appear exactly once if the presence field in an object has value "mandatory". However. i. by vendors for research purposes.

HandoverRequest.0 (2008-03) 9. HandoverCommand. HandoverRequestAcknowledge. PathSwitchRequest.************************************************************** S1AP-PDU-Descriptions { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) eps-Access (20) modules (3) s1ap (1) version1 (1) s1ap-PDU-Descriptions (0)} DEFINITIONS AUTOMATIC TAGS ::= BEGIN -. UplinkNASTransport.Release 8 84 3GPP TS 36.3. SAEBearerSetupResponse. HandoverNotify. InitialUEMessage.2 Elementary Procedure Definitions -. HandoverPreparationFailure.IE parameter types from other modules.Elementary Procedure definitions --. PathSwitchRequestFailure. InitialContextSetupFailure. ProcedureCode FROM S1AP-CommonDataTypes HandoverRequired. InitialContextSetupRequest. InitialContextSetupResponse. SAEBearerModifyRequest.************************************************************** --. SAEBearerModifyResponse. SAEBearerReleaseRequest. Paging.413 V8. SAEBearerSetupRequest.************************************************************** IMPORTS Criticality. --.************************************************************** --. HandoverFailure. SAEBearerReleaseCommand. DownlinkNASTransport. HandoverCancel. SAEBearerReleaseComplete.1. 3GPP . PathSwitchRequestAcknowledge.

id-UECapabilityInfoIndication. MMEStatusTransfer FROM S1AP-PDU-Contents id-HandoverPreparation. S1SetupResponse. id-UplinkS1cdma2000tunneling. UECapabilityInfoIndication. UEContextModificationRequest. id-ErrorIndication. UEContextModificationFailure. id-SAEBearerReleaseRequest. 85 3GPP TS 36. id-SAEBearerModify. ErrorIndication. Reset. id-Paging. id-HandoverResourceAllocation. S1SetupFailure. DownlinkS1cdma2000tunneling. UplinkS1cdma2000tunneling. id-PathSwitchRequest. UEContextReleaseComplete. id-initialUEMessage. id-S1Setup. UEContextReleaseRequest. id-MMEStatusTransfer FROM S1AP-Constants. id-UEContextRelease. UEContextReleaseCommand.0 (2008-03) -. id-NASNonDeliveryIndication. id-SAEBearerSetup. id-HandoverNotification. id-UEContextModification. id-UEContextReleaseRequest. id-Reset. id-downlinkNASTransport.Release 8 HandoverCancelAcknowledge.************************************************************** -- 3GPP . UEContextModificationResponse.413 V8. S1SetupRequest. NASNonDeliveryIndication. id-DownlinkS1cdma2000tunneling. ResetAcknowledge.1. id-HandoverCancel. id-InitialContextSetup. ENBStatusTransfer. id-uplinkNASTransport. id-SAEBearerRelease. id-eNBStatusTransfer.

&UnsuccessfulOutcome ({S1AP-ELEMENTARY-PROCEDURES}{@procedureCode}) } -. &procedureCode ProcedureCode UNIQUE. criticality S1AP-ELEMENTARY-PROCEDURE.0 (2008-03) InitiatingMessage ::= SEQUENCE { procedureCode S1AP-ELEMENTARY-PROCEDURE.. value S1AP-ELEMENTARY-PROCEDURE.&criticality ({S1AP-ELEMENTARY-PROCEDURES}{@procedureCode}).&procedureCode ({S1AP-ELEMENTARY-PROCEDURES}).. successfulOutcome SuccessfulOutcome.413 V8.&criticality ({S1AP-ELEMENTARY-PROCEDURES}{@procedureCode}).Interface Elementary Procedure List 3GPP .&procedureCode ({S1AP-ELEMENTARY-PROCEDURES}).Interface PDU Definition --.************************************************************** S1AP-PDU ::= CHOICE { initiatingMessage InitiatingMessage.Interface Elementary Procedure Class --.************************************************************** --. &criticality Criticality DEFAULT ignore } WITH SYNTAX { INITIATING MESSAGE &InitiatingMessage [SUCCESSFUL OUTCOME &SuccessfulOutcome] [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome] PROCEDURE CODE &procedureCode [CRITICALITY &criticality] } -.&procedureCode ({S1AP-ELEMENTARY-PROCEDURES}). value S1AP-ELEMENTARY-PROCEDURE.************************************************************** --. &UnsuccessfulOutcome OPTIONAL.&SuccessfulOutcome ({S1AP-ELEMENTARY-PROCEDURES}{@procedureCode}) } UnsuccessfulOutcome ::= SEQUENCE { procedureCode S1AP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({S1AP-ELEMENTARY-PROCEDURES}{@procedureCode}) } SuccessfulOutcome ::= SEQUENCE { procedureCode S1AP-ELEMENTARY-PROCEDURE. criticality S1AP-ELEMENTARY-PROCEDURE. . &SuccessfulOutcome OPTIONAL. value S1AP-ELEMENTARY-PROCEDURE.************************************************************** S1AP-ELEMENTARY-PROCEDURE ::= CLASS { &InitiatingMessage . criticality S1AP-ELEMENTARY-PROCEDURE.&criticality ({S1AP-ELEMENTARY-PROCEDURES}{@procedureCode}). unsuccessfulOutcome UnsuccessfulOutcome.Release 8 -.1. } 86 3GPP TS 36.

413 V8.Interface Elementary Procedures --. .0 (2008-03) S1AP-ELEMENTARY-PROCEDURES-CLASS-1 S1AP-ELEMENTARY-PROCEDURE ::= { handoverPreparation | handoverResourceAllocation | pathSwitchRequest | sAEbearerSetup | sAEbearerModify | sAEbearerRelease | initialContextSetup | handoverCancel | reset | s1Setup | uEContextModification | uEContextRelease ... .. } -...************************************************************** --.1. } 87 3GPP TS 36.************************************************************** handoverPreparation S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE HandoverRequired 3GPP . . } S1AP-ELEMENTARY-PROCEDURES-CLASS-2 S1AP-ELEMENTARY-PROCEDURE ::= { handoverNotification | sAEbearerReleaseRequest | paging | downlinkNASTransport | initialUEMessage | uplinkNASTransport | errorIndication | nASNonDeliveryIndication | uEContextReleaseRequest | downlinkS1cdma2000tunneling | uplinkS1cdma2000tunneling | uECapabilityInfoIndication | eNBStatusTransfer | mMEStatusTransfer ..Release 8 --.************************************************************** S1AP-ELEMENTARY-PROCEDURES S1AP-ELEMENTARY-PROCEDURE ::= { S1AP-ELEMENTARY-PROCEDURES-CLASS-1 | S1AP-ELEMENTARY-PROCEDURES-CLASS-2.

Release 8 SUCCESSFUL OUTCOME HandoverCommand UNSUCCESSFUL OUTCOME HandoverPreparationFailure PROCEDURE CODE id-HandoverPreparation CRITICALITY reject } handoverResourceAllocation S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE HandoverRequest SUCCESSFUL OUTCOME HandoverRequestAcknowledge UNSUCCESSFUL OUTCOME HandoverFailure PROCEDURE CODE id-HandoverResourceAllocation CRITICALITY reject } handoverNotification S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE HandoverNotify PROCEDURE CODE id-HandoverNotification CRITICALITY ignore } pathSwitchRequest S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE PathSwitchRequest SUCCESSFUL OUTCOME PathSwitchRequestAcknowledge UNSUCCESSFUL OUTCOME PathSwitchRequestFailure PROCEDURE CODE id-PathSwitchRequest CRITICALITY reject } sAEbearerSetup S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE SAEBearerSetupRequest SUCCESSFUL OUTCOME SAEBearerSetupResponse PROCEDURE CODE id-SAEBearerSetup CRITICALITY reject } sAEbearerModify S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE SAEBearerModifyRequest SUCCESSFUL OUTCOME SAEBearerModifyResponse PROCEDURE CODE id-SAEBearerModify CRITICALITY reject } sAEbearerRelease S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE SAEBearerReleaseCommand SUCCESSFUL OUTCOME SAEBearerReleaseComplete PROCEDURE CODE id-SAEBearerRelease CRITICALITY reject } sAEbearerReleaseRequest S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE SAEBearerReleaseRequest PROCEDURE CODE id-SAEBearerReleaseRequest CRITICALITY ignore 88 3GPP TS 36.1.413 V8.0 (2008-03) 3GPP .

413 V8.Release 8 } initialContextSetup S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE InitialContextSetupRequest SUCCESSFUL OUTCOME InitialContextSetupResponse UNSUCCESSFUL OUTCOME InitialContextSetupFailure PROCEDURE CODE id-InitialContextSetup CRITICALITY reject } uEContextReleaseRequest S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UEContextReleaseRequest PROCEDURE CODE id-UEContextReleaseRequest CRITICALITY ignore } paging S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE Paging PROCEDURE CODE id-Paging CRITICALITY ignore } downlinkNASTransport S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE DownlinkNASTransport PROCEDURE CODE id-downlinkNASTransport CRITICALITY ignore } initialUEMessage S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE InitialUEMessage PROCEDURE CODE id-initialUEMessage CRITICALITY ignore } uplinkNASTransport S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UplinkNASTransport PROCEDURE CODE id-uplinkNASTransport CRITICALITY ignore } nASNonDeliveryIndication S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE NASNonDeliveryIndication PROCEDURE CODE id-NASNonDeliveryIndication CRITICALITY ignore } handoverCancel S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE HandoverCancel SUCCESSFUL OUTCOME HandoverCancelAcknowledge PROCEDURE CODE id-HandoverCancel CRITICALITY reject } reset S1AP-ELEMENTARY-PROCEDURE ::= { 89 3GPP TS 36.1.0 (2008-03) 3GPP .

0 (2008-03) uplinkS1cdma2000tunneling S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UplinkS1cdma2000tunneling PROCEDURE CODE id-UplinkS1cdma2000tunneling CRITICALITY ignore } uEContextModification S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UEContextModificationRequest SUCCESSFUL OUTCOME UEContextModificationResponse UNSUCCESSFUL OUTCOME UEContextModificationFailure PROCEDURE CODE CRITICALITY } uECapabilityInfoIndication S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UECapabilityInfoIndication PROCEDURE CODE id-UECapabilityInfoIndication CRITICALITY ignore } uEContextRelease S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UEContextReleaseCommand SUCCESSFUL OUTCOME UEContextReleaseComplete PROCEDURE CODE id-UEContextRelease CRITICALITY reject } id-UEContextModification reject 3GPP .1.Release 8 INITIATING MESSAGE SUCCESSFUL OUTCOME PROCEDURE CODE CRITICALITY } errorIndication S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE ErrorIndication PROCEDURE CODE id-ErrorIndication CRITICALITY ignore } s1Setup S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE S1SetupRequest SUCCESSFUL OUTCOME S1SetupResponse UNSUCCESSFUL OUTCOME S1SetupFailure PROCEDURE CODE id-S1Setup CRITICALITY reject } downlinkS1cdma2000tunneling INITIATING MESSAGE PROCEDURE CODE CRITICALITY } S1AP-ELEMENTARY-PROCEDURE ::= { DownlinkS1cdma2000tunneling id-DownlinkS1cdma2000tunneling ignore Reset ResetAcknowledge id-Reset reject 90 3GPP TS 36.413 V8.

1.0 (2008-03) 3GPP .413 V8.Release 8 eNBStatusTransfer S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE ENBStatusTransfer PROCEDURE CODE id-eNBStatusTransfer CRITICALITY ignore } mMEStatusTransfer S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE MMEStatusTransfer PROCEDURE CODE id-MMEStatusTransfer CRITICALITY ignore } END 91 3GPP TS 36.

HandoverType. --.Release 8 92 3GPP TS 36. Cause. SAE-Bearer-ID.3. TargetID.1.************************************************************** --. GUMMEI. SAE-BearerLevelQoSParameters. TargeteNodeB-ToSourceeNodeB-TransparentContainer. GTP-TEID. SecurityInformation. 3GPP . PagingDRX. CriticalityDiagnostics. PagingCause. TargetBSS-ToSourceBSS-TransparentContainer.************************************************************** --. SourceBSS-ToTargetBSS-TransparentContainer.IE parameter types from other modules. NAS-PDU. UEPagingID.PDU definitions for S1AP. TraceActivation.************************************************************** IMPORTS AggregateMaximumBitrate. --. TargetRNC-ToSourceRNC-TransparentContainer. ENB-UE-S1AP-ID. SourceeNodeB-ToTargeteNodeB-TransparentContainer. TransportLayerAddress. SAEBearerList. TAId.3 PDU Definitions -. SourceID.0 (2008-03) 9. SourceRNC-ToTargetRNC-TransparentContainer. Cause.413 V8.************************************************************** S1AP-PDU-Contents { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) eps-Access (20) modules (3) s1ap (1) version1 (1) s1ap-PDU-Contents (1) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN -. MME-UE-S1AP-ID.

S1AP-PROTOCOL-IES-PAIR FROM S1AP-Containers id-aggregateMaximumBitrate. id-Bearers-SubjectToStatusTransferMME-List. id-Bearers-SubjectToStatusTransferMME-Item. ProtocolIE-ContainerPair{}. ProtocolIE-SingleContainer{}. id-HandoverType.413 V8. Direct-Forwarding-Path-Availability.Release 8 ENB-Global-ID.0 (2008-03) FROM S1AP-IEs PrivateIE-Container{}. ProtocolIE-ContainerList{}. UEIdentityIndexValue 93 3GPP TS 36. PLMNidentity. SupportedTAIs. ProtocolIE-Container{}. id-eNBname. id-GERANtoLTEHOInformationReq. id-InitialContextSetup.1. MMEname. TimeToWait. ProtocolExtensionContainer{}. id-ENB-Global-ID. PDCP-SN. S1AP-PROTOCOL-EXTENSION. ENBname. id-Intra-LTEHOInformationReq. 3GPP . Cdma2000PDU. id-GERANtoLTEHOInformationRes. Cdma2000RATType. id-eNB-UE-S1AP-ID. SecurityInfo. id-HandoverRestrictionList. id-Intra-LTEHOInformationRes. id-Bearers-SubjectToStatusTransferENB-Item. S1AP-PRIVATE-IES. ServedPLMNs. Cdma2000SectorID. id-Cause. ProtocolIE-ContainerPairList{}. UERadioCapability. id-Bearers-SubjectToStatusTransferENB-List. id-CriticalityDiagnostics. HandoverRestrictionList. S1AP-PROTOCOL-IES. id-Direct-Forwarding-Path-Availability.

id-SAEBearerToBeSetupItemHOReq. id-SAEBearerReleaseItemBearerRelComp. id-UEPagingID. id-SAEBearerSetupItemBearerSURes. id-SAEBearerReleaseListBearerRelComp. id-SAEBearerModifyListBearerModRes. id-SAEBearerFailedToReleaseList.0 (2008-03) 3GPP . id-MME-UE-S1AP-ID. id-SAEBearerSetupListBearerSURes. id-SAEBearerAdmittedItem. id-Security-Information. id-SAEBearerToBeReleasedList. id-SAEBearerToBeSwitchedDLList. 94 3GPP TS 36. id-SAEBearerToBeSwitchedDLItem. id-SAEBearerToBeModifiedItemBearerModReq. id-TAIdItem. id-SAEBearerRelease. id-SAEBearerToBeSetupItemBearerSUReq. id-SAEBearerFailedToModifyList.1. id-SAEBearertoReleaseListHOCmd. id-SAEBearerReleaseRequest.Release 8 id-LTEtoGERANHOInformationReq.413 V8. id-SAEBearerSetup. id-TAIdList. id-SAEBearerToBeSetupListBearerSUReq. id-SAEBearerModifyItemBearerModRes. id-SAEBearerDataForwardingItem. id-LTEtoGERANHOInformationRes. id-SAEBearerToBeSetupItemCtxtSUReq. id-ServingPLMN. id-SAEBearerFailedToSetupListBearerSURes. id-SAEBearerToBeSetupListHOReq. id-LTEtoUTRANHOInformationRes. id-ServedPLMNs. id-SAEBearerAdmittedList. id-SupportedTAIs. id-SAEBearerToBeModifiedListBearerModReq. id-NAS-PDU. id-SAEBearerToBeSetupListCtxtSUReq. id-SAEBearerModify. id-SAEBearerSetupItemCtxtSURes. id-MMEname. id-SAEBearerFailedToSetupListCtxtSURes. id-LTEtoUTRANHOInformationReq. id-pagingCause. id-SAEBearerSetupListCtxtSURes. id-SAEBearerFailedToSetupListHOReqAck. id-pagingDRX. id-SourceID. id-TAId. id-SAEBearerReleaseItemHOCmd. id-SAEBearerSubjecttoDataForwardingList. id-SAEBearerFailedtoSetupItemHOReqAck.

HandoverRequiredIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory { ID id-HandoverType CRITICALITY reject TYPE HandoverType PRESENCE mandatory { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | } | } | 3GPP . maxNrOfSAEBs 95 3GPP TS 36.************************************************************** -.1.************************************************************** --. id-cdma2000SectorID.HANDOVER PREPARATION ELEMTARY PROCEDURE --. { S1AP-PROTOCOL-IES-PAIR : IEsSetParam } ::= ProtocolIE-ContainerPairList { 1.Common Container Lists --.413 V8. id-TimeToWait.0 (2008-03) FROM S1AP-Constants. id-UTRANtoLTEHOInformationReq. id-cdma2000RATType. id-cdma2000PDU. maxNrOfSAEBs. { S1AP-PROTOCOL-IES : IEsSetParam } ::= ProtocolIE-ContainerList { 1. maxNrOfSAEBs.************************************************************** --. id-TraceActivation. id-SecurityInfo..************************************************************** HandoverRequired ::= SEQUENCE { protocolIEs ProtocolIE-Container .************************************************************** SAEB-IE-ContainerList {IEsSetParam} } SAEB-IE-ContainerPairList {IEsSetParam} } ProtocolError-IE-ContainerList {IEsSetParam} } { S1AP-PROTOCOL-IES : IEsSetParam } ::= ProtocolIE-ContainerList { 1. -.Handover Required --.Release 8 id-TargetID. maxnoofTAI. maxNrOfSAEBs. id-UERadioCapability. id-UTRANtoLTEHOInformationRes. -. maxNrOfErrors. } { { HandoverRequiredIEs} }.************************************************************** --. id-UEIdentityIndexValue. id-GUMMEI-ID..

.************************************************************** HandoverCommand ::= SEQUENCE { protocolIEs ProtocolIE-Container { { HandoverCommandIEs} }. } LTEtoUTRANHOInformationReq-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { .....This IE shall be present if the Handover Type IE is set to value “LTEtoUTRAN” -} | { ID id-LTEtoGERANHOInformationReq CRITICALITY reject TYPE LTEtoGERANHOInformationReq PRESENCE conditional -. 3GPP .. } LTEtoGERANHOInformationReq-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . } -.. iE-Extensions ProtocolExtensionContainer { {LTEtoGERANHOInformationReq-ExtIEs} } . iE-Extensions ProtocolExtensionContainer { {LTEtoUTRANHOInformationReq-ExtIEs} } . . } OPTIONAL. .Release 8 96 3GPP TS 36. } Intra-LTEHOInformationReq ::= SEQUENCE { sourceeNodeB-ToTargeteNodeB-TransparentContainer SourceeNodeB-ToTargeteNodeB-TransparentContainer... } Intra-LTEHOInformationReq-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { ..413 V8. .This IE shall be present if Handover Type IE is set to value “IntraLTE” -} | { ID id-LTEtoUTRANHOInformationReq CRITICALITY reject TYPE LTEtoUTRANHOInformationReq PRESENCE conditional -..This IE shall be present if the Handover Type IE is set to value “LTEtoGERAN” -}. } LTEtoUTRANHOInformationReq ::= SEQUENCE { sourceRNC-ToTargetRNC-TransparentContainer SourceRNC-ToTargetRNC-TransparentContainer. iE-Extensions ProtocolExtensionContainer { {Intra-LTEHOInformationReq-ExtIEs} } OPTIONAL. OPTIONAL.************************************************************** --...1..0 (2008-03) { ID id-SourceID CRITICALITY ignore TYPE SourceID PRESENCE mandatory } | { ID id-TargetID CRITICALITY reject TYPE TargetID PRESENCE mandatory } | { ID id-Direct-Forwarding-Path-Availability CRITICALITY ignore TYPE Direct-Forwarding-Path-Availability PRESENCE optional } | { ID id-Intra-LTEHOInformationReq CRITICALITY reject TYPE Intra-LTEHOInformationReq PRESENCE conditional -...Handover Command --. } LTEtoGERANHOInformationReq ::= SEQUENCE { sourceBSS-ToTargetBSS-TransparentContainer SourceBSS-ToTargetBSS-TransparentContainer.

dL-transportLayerAddress TransportLayerAddress. SAEBearerReleaseItemHOCmd ::= SEQUENCE { sAE-Bearer-ID SAE-Bearer-ID. iE-Extensions ProtocolExtensionContainer { { SAEBearerDataForwardingItem-ExtIEs} } .413 V8.This IE shall be present if the Handover Type IE is set to value “LTEtoUTRAN” -} | { ID id-LTEtoGERANHOInformationRes CRITICALITY reject TYPE LTEtoGERANHOInformationRes PRESENCE conditional -. 3GPP . } TYPE SAEBearerReleaseItemHOCmd PRESENCE mandatory }. dL-gTP-TEID GTP-TEID. } Intra-LTEHOInformationRes ::= SEQUENCE { OPTIONAL. iE-Extensions ProtocolExtensionContainer { { SAEBearerReleaseItemHOCmd-ExtIEs} } .... } SAEBearerSubjecttoDataForwardingList ::= SAEB-IE-ContainerList { {SAEBearerDataForwardingItemIEs} } SAEBearerDataForwardingItemIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerDataForwardingItem CRITICALITY ignore . } } | TYPE SAEBearerDataForwardingItem PRESENCE mandatory }.. } SAEBearerReleaseItemHOCmd-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . SAEBearerDataForwardingItem ::= SEQUENCE { sAE-Bearer-ID SAE-Bearer-ID.. } SAEBearerDataForwardingItem-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . ...1.Release 8 97 3GPP TS 36.. SAEBearerReleaseItemHOCmdIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerReleaseItemHOCmd CRITICALITY ignore .. } SAEBearertoReleaseListHOCmd ::= SAEB-IE-ContainerList { {SAEBearerReleaseItemHOCmdIEs} } OPTIONAL..0 (2008-03) HandoverCommandIEs S1AP-PROTOCOL-IES ::= { { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory } | { ID id-SAEBearerSubjecttoDataForwardingList CRITICALITY ignore TYPE SAEBearerSubjecttoDataForwardingList PRESENCE mandatory } | { ID id-SAEBearertoReleaseListHOCmd CRITICALITY ignore TYPE SAEBearertoReleaseListHOCmd PRESENCE mandatory { ID id-Intra-LTEHOInformationRes CRITICALITY reject TYPE Intra-LTEHOInformationRes PRESENCE conditional -...This IE shall be present if the Handover Type IE is set to value “LTEtoGERAN” -}...This IE shall be present if Handover Type IE is set to value “IntraLTE” -} | { ID id-LTEtoUTRANHOInformationRes CRITICALITY reject TYPE LTEtoUTRANHOInformationRes PRESENCE conditional -.

OPTIONAL. } -..... { { HandoverPreparationFailureIEs} }... } -.. } LTEtoUTRANHOInformationRes-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { .************************************************************** --.Release 8 98 3GPP TS 36. } LTEtoGERANHOInformationRes-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { ...************************************************************** HandoverPreparationFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container ..413 V8.HANDOVER RESOURCE ALLOCATION ELEMTARY PROCEDURE --. iE-Extensions ProtocolExtensionContainer { {LTEtoGERANHOInformationRes-ExtIEs} } ..0 (2008-03) targeteNodeB-ToSourceeNodeB-TransparentContainer TargeteNodeB-ToSourceeNodeB-TransparentContainer.1. . } OPTIONAL. } Intra-LTEHOInformationRes-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . } LTEtoGERANHOInformationRes ::= SEQUENCE { targetBSS-ToSourceBSS-TransparentContainer TargetBSS-ToSourceBSS-TransparentContainer. iE-Extensions ProtocolExtensionContainer { {Intra-LTEHOInformationRes-ExtIEs} } OPTIONAL.************************************************************** } | 3GPP ....************************************************************** --.************************************************************** -. HandoverPreparationFailureIEs S1AP-PROTOCOL-IES ::= { { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }.. .Handover Preparation Failure --. } LTEtoUTRANHOInformationRes ::= SEQUENCE { targetRNC-ToSourceRNC-TransparentContainer TargetRNC-ToSourceRNC-TransparentContainer.. iE-Extensions ProtocolExtensionContainer { {LTEtoUTRANHOInformationRes-ExtIEs} } .

iE-Extensions ProtocolExtensionContainer { {UTRANtoLTEHOInformationReq-ExtIEs} } . SAEBearerToBeSetupItemHOReq ::= SEQUENCE { sAE-Bearer-ID SAE-Bearer-ID.1. sAE-BearerlevelQosParameters SAE-BearerLevelQoSParameters.This IE shall be present if the Handover Type IE is set to value “GERANtoLTE” -} | { ID id-ServingPLMN CRITICALITY reject TYPE PLMNidentity PRESENCE optional } | { ID id-HandoverRestrictionList CRITICALITY ignore TYPE HandoverRestrictionList PRESENCE optional }..Handover Request --. HandoverRequestIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory } | { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory } | { ID id-HandoverType CRITICALITY reject TYPE HandoverType PRESENCE mandatory } | { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | { ID id-SAEBearerToBeSetupListHOReq CRITICALITY reject TYPE SAEBearerToBeSetupListHOReq PRESENCE mandatory { ID id-Intra-LTEHOInformationReq CRITICALITY reject TYPE Intra-LTEHOInformationReq PRESENCE conditional -. } TYPE SAEBearerToBeSetupItemHOReq PRESENCE mandatory }..This IE shall be present if the Handover Type IE is set to value “UTRANtoLTE” -} | { ID id-GERANtoLTEHOInformationReq CRITICALITY reject TYPE GERANtoLTEHOInformationReq PRESENCE conditional -. } SAEBearerToBeSetupListHOReq ::= SAEB-IE-ContainerList { {SAEBearerToBeSetupItemHOReqIEs} } } | SAEBearerToBeSetupItemHOReqIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerToBeSetupItemHOReq CRITICALITY ignore . transportLayerAddress TransportLayerAddress. } 99 3GPP TS 36.. OPTIONAL... 3GPP ..413 V8..Release 8 --.************************************************************** HandoverRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container .This IE shall be present if Handover Type IE is set to value “IntraLTE” -} | { ID id-UTRANtoLTEHOInformationReq CRITICALITY reject TYPE UTRANtoLTEHOInformationReq PRESENCE conditional -.0 (2008-03) { {HandoverRequestIEs} }. . } SAEBearerToBeSetupItemHOReq-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { ... } UTRANtoLTEHOInformationReq ::= SEQUENCE { sourceRNC-ToTargetRNC-TransparentContainer SourceRNC-ToTargetRNC-TransparentContainer.. gTP-TEID GTP-TEID. iE-Extensions ProtocolExtensionContainer { {SAEBearerToBeSetupItemHOReq-ExtIEs} } ... } OPTIONAL.

.413 V8. } SAEBearerAdmittedItem ::= SEQUENCE { sAE-Bearer-ID transportLayerAddress TYPE SAEBearerAdmittedItem PRESENCE mandatory }.Release 8 UTRANtoLTEHOInformationReq-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { .. -. } OPTIONAL.This IE shall be present if Handover Type IE is set to value “IntraLTE” -} | { ID id-UTRANtoLTEHOInformationRes CRITICALITY reject TYPE UTRANtoLTEHOInformationRes PRESENCE conditional -.************************************************************** --. } 100 3GPP TS 36. TransportLayerAddress. 3GPP .1. } { {HandoverRequestAcknowledgeIEs} }....This IE shall be present if the Handover Type IE is set to value “GERANtoLTE” -}.....This IE shall be present if the Handover Type IE is set to value “UTRANtoLTE” -} | { ID id-GERANtoLTEHOInformationRes CRITICALITY reject TYPE GERANtoLTEHOInformationRes PRESENCE conditional -. } GERANtoLTEHOInformationReq-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . .Handover Request Acknowledge --. HandoverRequestAcknowledgeIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory } | { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory } | { ID id-HandoverType CRITICALITY reject TYPE HandoverType PRESENCE mandatory } | { ID id-SAEBearerAdmittedList CRITICALITY reject TYPE SAEBearerAdmittedList PRESENCE mandatory { ID id-SAEBearerFailedToSetupListHOReqAck CRITICALITY ignore TYPE SAEBearerFailedtoSetupListHOReqAck mandatory } | { ID id-Intra-LTEHOInformationRes CRITICALITY reject TYPE Intra-LTEHOInformationRes PRESENCE conditional -.. } SAEBearerAdmittedList ::= SAEB-IE-ContainerList { {SAEBearerAdmittedItemIEs} } } | PRESENCE SAEBearerAdmittedItemIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerAdmittedItem CRITICALITY ignore ..0 (2008-03) GERANtoLTEHOInformationReq ::= SEQUENCE { sourceBSS-ToTargetBSS-TransparentContainer SourceBSS-ToTargetBSS-TransparentContainer. SAE-Bearer-ID. iE-Extensions ProtocolExtensionContainer { {GERANtoLTEHOInformationReq-ExtIEs} } .************************************************************** HandoverRequestAcknowledge ::= SEQUENCE { protocolIEs ProtocolIE-Container ..

GTP-TEID OPTIONAL... } UTRANtoLTEHOInformationRes ::= SEQUENCE { targetRNC-ToSourceRNC-TransparentContainer TargetRNC-ToSourceRNC-TransparentContainer. } SAEBearerFailedToSetupItemHOReqAckExtIEs S1AP-PROTOCOL-EXTENSION ::= { .... iE-Extensions ProtocolExtensionContainer { {UTRANtoLTEHOInformationRes-ExtIEs} } . } TYPE SAEBearerFailedToSetupItemHOReqAck PRESENCE mandatory }. } SAEBearerAdmittedItem-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . 101 TransportLayerAddress OPTIONAL. } OPTIONAL. } UTRANtoLTEHOInformationRes-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { .Release 8 gTP-TEID dL-transportLayerAddress dL-gTP-TEID iE-Extensions .1...413 V8. SAEBearerFailedToSetupItemHOReqAck ::= SEQUENCE { sAE-Bearer-ID SAE-Bearer-ID.... ProtocolExtensionContainer { {SAEBearerAdmittedItem-ExtIEs} } 3GPP TS 36.Handover Failure 3GPP .. iE-Extensions ProtocolExtensionContainer { { SAEBearerFailedToSetupItemHOReqAckExtIEs} } ... -. cause Cause..0 (2008-03) OPTIONAL..************************************************************** --. ::= SAEB-IE-ContainerList { {SAEBearerFailedtoSetupItemHOReqAckIEs} } SAEBearerFailedtoSetupItemHOReqAckIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerFailedtoSetupItemHOReqAck CRITICALITY ignore . iE-Extensions ProtocolExtensionContainer { {GERANtoLTEHOInformationRes-ExtIEs} } . } GERANtoLTEHOInformationRes-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { ... OPTIONAL. } GERANtoLTEHOInformationRes ::= SEQUENCE { targetBSS-ToSourceBSS-TransparentContainer TargetBSS-ToSourceBSS-TransparentContainer.. } SAEBearerFailedtoSetupListHOReqAck GTP-TEID. OPTIONAL.

..0 (2008-03) { { HandoverFailureIEs} }.************************************************************** --.************************************************************** -..413 V8.1.. . } 102 3GPP TS 36..PATH SWITCH REQUEST ELEMTARY PROCEDURE --. . } } | { { HandoverNotifyIEs} }.Release 8 --. } | } | { { PathSwitchRequestIEs} }.************************************************************** HandoverFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container .. 3GPP .************************************************************** -.************************************************************** --.************************************************************** HandoverNotify ::= SEQUENCE { protocolIEs ProtocolIE-Container .HANDOVER NOTIFICATION ELEMTARY PROCEDURE --.. } -.Path Switch Request --..Handover Notify --.. HandoverNotifyIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }..************************************************************** --. HandoverFailureIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }. } -.************************************************************** PathSwitchRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container .************************************************************** --.

SAEBearerToBeSwitchedDLItem ::= SEQUENCE { sAE-Bearer-ID SAE-Bearer-ID.413 V8..Release 8 } 103 3GPP TS 36. 3GPP . PathSwitchRequestAcknowledgeIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject { ID id-eNB-UE-S1AP-ID CRITICALITY reject .. } SAEBearerToBeSwitchedDLList ::= SAEB-IE-ContainerList { {SAEBearerToBeSwitchedDLItemIEs} } } | } | PRESENCE mandatory }...1.Path Switch Request Acknowledge --. transportLayerAddress TransportLayerAddress. iE-Extensions ProtocolExtensionContainer { { SAEBearerToBeSwitchedDLItem-ExtIEs} } . { { PathSwitchRequestAcknowledgeIEs} }.Path Switch Request Failure --. SAEBearerToBeSwitchedDLItemIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerToBeSwitchedDLItem CRITICALITY ignore .0 (2008-03) PathSwitchRequestIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory { ID id-HandoverType CRITICALITY reject TYPE HandoverType PRESENCE mandatory { ID id-SAEBearerToBeSwitchedDLList CRITICALITY reject TYPE SAEBearerToBeSwitchedDLList . gTP-TEID GTP-TEID. } TYPE MME-UE-S1AP-ID TYPE ENB-UE-S1AP-ID PRESENCE mandatory } | PRESENCE mandatory }.. } SAEBearerToBeSwitchedDLItem-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { .. } TYPE SAEBearerToBeSwitchedDLItem PRESENCE mandatory }. } -.************************************************************** --. } OPTIONAL......************************************************************** PathSwitchRequestFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container { { PathSwitchRequestFailureIEs} }.************************************************************** PathSwitchRequestAcknowledge ::= SEQUENCE { protocolIEs ProtocolIE-Container ..************************************************************** --. -.

Release 8
... }

104

3GPP TS 36.413 V8.1.0 (2008-03)

PathSwitchRequestFailureIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory } | { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory } | { ID id-Cause CRITICALITY reject TYPE Cause PRESENCE mandatory }, ... } -- ************************************************************** --- HANDOVER CANCEL ELEMTARY PROCEDURE --- ************************************************************** -- ************************************************************** --- Handover Cancel --- ************************************************************** HandoverCancel ::= SEQUENCE { protocolIEs ProtocolIE-Container ... }

{ { HandoverCancelIEs} },

HandoverCancelIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, ... } -- ************************************************************** --- Handover Cancel Request Acknowledge --- ************************************************************** HandoverCancelAcknowledge ::= SEQUENCE { protocolIEs ProtocolIE-Container ... }

} | } |

{ { HandoverCancelAcknowledgeIEs} },

HandoverCancelAcknowledgeIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject { ID id-eNB-UE-S1AP-ID CRITICALITY reject ... }

TYPE MME-UE-S1AP-ID TYPE ENB-UE-S1AP-ID

PRESENCE mandatory PRESENCE mandatory

} | },

-- ************************************************************** --

3GPP

Release 8
-- SAE BEARER SETUP ELEMENTARY PROCEDURE --- ************************************************************** -- ************************************************************** --- SAE Bearer Setup Request --- ************************************************************** SAEBearerSetupRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container ... } SAEBearerSetupRequestIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY { ID id-eNB-UE-S1AP-ID CRITICALITY { ID id-SAEBearerToBeSetupListBearerSUReq { ID id-TraceActivation CRITICALITY { ID id-NAS-PDU CRITICALITY ignore ... }

105

3GPP TS 36.413 V8.1.0 (2008-03)

{ {SAEBearerSetupRequestIEs} },

reject TYPE MME-UE-S1AP-ID PRESENCE mandatory }| reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory }| CRITICALITY reject TYPE SAEBearerToBeSetupListBearerSUReq PRESENCE mandatory ignore TYPE TraceActivation PRESENCE optional }| TYPE NAS-PDU PRESENCE mandatory},

}|

SAEBearerToBeSetupListBearerSUReq ::= SEQUENCE (SIZE(1.. maxNrOfSAEBs)) OF ProtocolIE-SingleContainer { {SAEBearerToBeSetupItemBearerSUReqIEs} } SAEBearerToBeSetupItemBearerSUReqIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerToBeSetupItemBearerSUReq CRITICALITY reject ... }

TYPE SAEBearerToBeSetupItemBearerSUReq

PRESENCE mandatory },

SAEBearerToBeSetupItemBearerSUReq ::= SEQUENCE { sAE-Bearer-ID SAE-Bearer-ID, sAE-BearerlevelQoSParameters SAE-BearerLevelQoSParameters, transportLayerAddress TransportLayerAddress, gTP-TEID GTP-TEID, iE-Extensions ProtocolExtensionContainer { {SAEBearerToBeSetupItemBearerSUReqExtIEs} } OPTIONAL, ... }

SAEBearerToBeSetupItemBearerSUReqExtIEs S1AP-PROTOCOL-EXTENSION ::= { ... }

-- ************************************************************** --- SAE Bearer Setup Response --- ************************************************************** SAEBearerSetupResponse ::= SEQUENCE {

3GPP

Release 8
protocolIEs ... } ProtocolIE-Container

106
{ {SAEBearerSetupResponseIEs} },

3GPP TS 36.413 V8.1.0 (2008-03)

SAEBearerSetupResponseIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory }| { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory }| { ID id-SAEBearerSetupListBearerSURes CRITICALITY reject TYPE SAEBearerSetupListBearerSURes PRESENCE optional }| { ID id-SAEBearerFailedToSetupListBearerSURes CRITICALITY ignore TYPE SAEBearerList PRESENCE optional }| { ID id-NAS-PDU CRITICALITY ignore TYPE NAS-PDU PRESENCE mandatory}, ... }

SAEBearerSetupListBearerSURes ::= SEQUENCE (SIZE(0.. maxNrOfSAEBs)) OF ProtocolIE-SingleContainer { {SAEBearerSetupItemBearerSUResIEs} } SAEBearerSetupItemBearerSUResIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerSetupItemBearerSURes CRITICALITY reject ... }

TYPE SAEBearerSetupItemBearerSURes PRESENCE mandatory },

SAEBearerSetupItemBearerSURes ::= SEQUENCE { sAE-Bearer-ID SAE-Bearer-ID, transportLayerAddress TransportLayerAddress, gTP-TEID GTP-TEID, iE-Extensions ProtocolExtensionContainer { {SAEBearerSetupItemBearerSUResExtIEs} } OPTIONAL, ... }

SAEBearerSetupItemBearerSUResExtIEs S1AP-PROTOCOL-EXTENSION ::= { ... }

-- ************************************************************** --- SAE BEARER MODIFY ELEMENTARY PROCEDURE --- ************************************************************** -- ************************************************************** --- SAE Bearer Modify Request --- ************************************************************** SAEBearerModifyRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container ... }

{ {SAEBearerModifyRequestIEs} },

3GPP

.Release 8 107 3GPP TS 36.. ..************************************************************** --. } -. maxNrOfSAEBs)) OF ProtocolIE-SingleContainer { {SAEBearerModifyItemBearerModResIEs} } 3GPP ... } }| }| PRESENCE optional }| }| SAEBearerModifyListBearerModRes ::= SEQUENCE (SIZE(0. iE-Extensions ProtocolExtensionContainer { {SAEBearerToBeModifyItemBearerModReqExtIEs} } OPTIONAL..413 V8. } SAEBearerToBeModifyItemBearerModReqExtIEs S1AP-PROTOCOL-EXTENSION ::= { . SAEBearerToBeModifiedItemBearerModReq ::= SEQUENCE { sAE-Bearer-ID SAE-Bearer-ID. maxNrOfSAEBs)) OF ProtocolIE-SingleContainer { {SAEBearerToBeModifiedItemBearerModReqIEs} } SAEBearerToBeModifiedItemBearerModReqIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerToBeModifiedItemBearerModReq CRITICALITY reject . .. sAE-BearerLevelQoSParameters SAE-BearerLevelQoSParameters.SAE Bearer Modify Response --. ....0 (2008-03) SAEBearerModifyRequestIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory }| { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory }| { ID id-SAEBearerToBeModifiedListBearerModReq CRITICALITY reject TYPE SAEBearerToBeModifiedListBearerModReq { ID id-NAS-PDU CRITICALITY ignore TYPE NAS-PDU PRESENCE mandatory}... } PRESENCE mandatory }| TYPE SAEBearerToBeModifiedItemBearerModReq PRESENCE mandatory }. } SAEBearerToBeModifiedListBearerModReq ::= SEQUENCE (SIZE(1.. } { {SAEBearerModifyResponseIEs} }.. SAEBearerModifyResponseIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory { ID id-SAEBearerModifyListBearerModRes CRITICALITY ignore TYPE SAEBearerModifyListBearerModRes { ID id-SAEBearerFailedToModifyList CRITICALITY ignore TYPE SAEBearerList PRESENCE optional { ID id-NAS-PDU CRITICALITY ignore TYPE NAS-PDU PRESENCE mandatory}.************************************************************** SAEBearerModifyResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container .1.

3GPP ..************************************************************** --. .************************************************************** --.************************************************************** SAEBearerReleaseCommand ::= SEQUENCE { protocolIEs ProtocolIE-Container ...413 V8.. } { {SAEBearerReleaseCommandIEs} }.. -. } -. } SAEBearerModifyItemBearerModResExtIEs S1AP-PROTOCOL-EXTENSION ::= { .Release 8 SAEBearerModifyItemBearerModResIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerModifyItemBearerModRes CRITICALITY reject .************************************************************** -..SAE Bearer Release Command --... SAEBearerReleaseCommandIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID { ID id-SAEBearerToBeReleasedList CRITICALITY ignore TYPE SAEBearerList ..SAE Bearer Release Complete --. } 108 TYPE SAEBearerModifyItemBearerModRes 3GPP TS 36.************************************************************** --. iE-Extensions ProtocolExtensionContainer { {SAEBearerModifyItemBearerModResExtIEs} } OPTIONAL. SAEBearerModifyItemBearerModRes ::= SEQUENCE { sAE-Bearer-ID SAE-Bearer-ID... { { SAEBearerReleaseCompleteIEs } }..************************************************************** SAEBearerReleaseComplete ::= SEQUENCE { protocolIEs ProtocolIE-Container .1.0 (2008-03) PRESENCE mandatory }.SAE BEARER RELEASE ELEMENTARY PROCEDURE --. } PRESENCE mandatory }| PRESENCE mandatory }| PRESENCE optional }.

SAE Bearer Release Request --..************************************************************** SAEBearerReleaseRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container . } TYPE SAEBearerReleaseItemBearerRelComp PRESENCE mandatory }... } { {SAEBearerReleaseRequestIEs} }.************************************************************** -... PRESENCE optional }| SAEBearerReleaseListBearerRelComp ::= SEQUENCE (SIZE(0.1.SAE BEARER RELEASE REQUEST ELEMENTARY PROCEDURE --. } -.. SAEBearerReleaseRequestIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY ignore TYPE MME-UE-S1AP-ID { ID id-eNB-UE-S1AP-ID CRITICALITY ignore TYPE ENB-UE-S1AP-ID { ID id-SAEBearerToBeReleasedList CRITICALITY ignore TYPE SAEBearerList .413 V8.************************************************************** --.. . SAEBearerReleaseItemBearerRelComp ::= SEQUENCE { sAE-Bearer-ID SAE-Bearer-ID.0 (2008-03) TYPE MME-UE-S1AP-ID PRESENCE mandatory }| TYPE ENB-UE-S1AP-ID PRESENCE mandatory }| CRITICALITY ignore TYPE SAEBearerReleaseListBearerRelComp ignore TYPE SAEBearerList PRESENCE optional }. } SAEBearerReleaseItemBearerRelCompExtIEs S1AP-PROTOCOL-EXTENSION ::= { .... maxNrOfSAEBs)) OF ProtocolIE-SingleContainer { {SAEBearerReleaseItemBearerRelCompIEs} } SAEBearerReleaseItemBearerRelCompIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerReleaseItemBearerRelComp CRITICALITY reject .Release 8 } SAEBearerReleaseCompleteIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject { ID id-eNB-UE-S1AP-ID CRITICALITY reject { ID id-SAEBearerReleaseListBearerRelComp { ID id-SAEBearerFailedToReleaseList CRITICALITY . } 109 3GPP TS 36.. PRESENCE mandatory }| PRESENCE mandatory }| PRESENCE optional }. iE-Extensions ProtocolExtensionContainer { {SAEBearerReleaseItemBearerRelCompExtIEs} } OPTIONAL.************************************************************** --. 3GPP ...

. maxNrOfSAEBs)) OF ProtocolIE-SingleContainer { {SAEBearerToBeSetupItemCtxtSUReqIEs} } 3GPP . } }| {{UEContextReleaseRequest-IEs}}.0 (2008-03) { {InitialContextSetupRequestIEs} }.. TYPE MME-UE-S1AP-ID TYPE ENB-UE-S1AP-ID TYPE Cause PRESENCE mandatory} | PRESENCE mandatory} | PRESENCE mandatory} .. SAEBearerToBeSetupListCtxtSUReq ::= SEQUENCE (SIZE(1. } -..************************************************************** UEContextReleaseRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container .Release 8 } -..************************************************************** --...UE CONTEXT RELEASE REQUEST --.INITIAL CONTEXT SETUP ELEMENTARY PROCEDURE --.413 V8. InitialContextSetupRequestIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory }| { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory }| { ID id-aggregateMaximumBitrate CRITICALITY reject TYPE AggregateMaximumBitrate PRESENCE optional }| { ID id-SAEBearerToBeSetupListCtxtSUReq CRITICALITY reject TYPE SAEBearerToBeSetupListCtxtSUReq PRESENCE mandatory { ID id-Security-Information CRITICALITY ignore TYPE SecurityInformation PRESENCE mandatory }| { ID id-TraceActivation CRITICALITY ignore TYPE TraceActivation PRESENCE optional }| { ID id-ServingPLMN CRITICALITY reject TYPE PLMNidentity PRESENCE optional } | { ID id-HandoverRestrictionList CRITICALITY ignore TYPE HandoverRestrictionList PRESENCE optional }| { ID id-NAS-PDU CRITICALITY ignore TYPE NAS-PDU PRESENCE optional}| { ID id-UERadioCapability CRITICALITY ignore TYPE UERadioCapability PRESENCE optional }. } 110 3GPP TS 36.************************************************************** --. } UEContextReleaseRequest-IEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject { ID id-eNB-UE-S1AP-ID CRITICALITY reject { ID id-Cause CRITICALITY ignore .1.************************************************************** --..Initial Context Setup Request --. .************************************************************** InitialContextSetupRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container .************************************************************** -..

. iE-Extensions .. transportLayerAddress TransportLayerAddress. TransportLayerAddress. gTP-TEID GTP-TEID.. .. iE-Extensions ProtocolExtensionContainer { {SAEBearerSetupItemCtxtSUResExtIEs} } OPTIONAL.0 (2008-03) TYPE SAEBearerToBeSetupItemCtxtSUReq PRESENCE mandatory }. 111 3GPP TS 36. maxNrOfSAEBs)) OF ProtocolIE-SingleContainer { {SAEBearerSetupItemCtxtSUResIEs} } SAEBearerSetupItemCtxtSUResIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerSetupItemCtxtSURes CRITICALITY reject . ProtocolExtensionContainer { {SAEBearerToBeSetupItemCtxtSUReqExtIEs} } OPTIONAL. } TYPE SAEBearerSetupItemCtxtSURes PRESENCE mandatory }....413 V8.1. InitialContextSetupResponseIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory }| { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory }| { ID id-SAEBearerSetupListCtxtSURes CRITICALITY reject TYPE SAEBearerSetupListCtxtSURes PRESENCE optional }| { ID id-SAEBearerFailedToSetupListCtxtSURes CRITICALITY ignore TYPE SAEBearerList PRESENCE optional }. } -. } { {InitialContextSetupResponseIEs} }. } SEQUENCE { SAE-Bearer-ID. SAEBearerSetupItemCtxtSURes ::= SEQUENCE { sAE-Bearer-ID SAE-Bearer-ID.. 3GPP .. } SAEBearerSetupListCtxtSURes ::= SEQUENCE (SIZE(1. } SAEBearerToBeSetupItemCtxtSUReq ::= sAE-Bearer-ID sAE-BearerlevelQoSParameters transportLayerAddress gTP-TEID GTP-TEID...************************************************************** --..Release 8 SAEBearerToBeSetupItemCtxtSUReqIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerToBeSetupItemCtxtSUReq CRITICALITY reject .Initial Context Setup Response --.. SAEBearerToBeSetupItemCtxtSUReqExtIEs S1AP-PROTOCOL-EXTENSION ::= { .************************************************************** InitialContextSetupResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container . SAE-BearerLevelQoSParameters.

.. maxnoofTAI)) OF ProtocolIE-SingleContainer {{TAIdItemIEs}} TAIdItemIEs S1AP-PROTOCOL-IES ::= { { ID id-TAIdItem CRITICALITY ignore .. PagingIEs S1AP-PROTOCOL-IES ::= { { ID id-UEIdentityIndexValue { ID id-UEPagingID { ID id-pagingDRX { ID id-pagingCause { ID id-TAIdList . } ProtocolIE-Container {{PagingIEs}}.************************************************************** InitialContextSetupFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container .************************************************************** --. } -. { reject reject ignore TYPE MME-UE-S1AP-ID TYPE ENB-UE-S1AP-ID TYPE Cause PRESENCE mandatory }| PRESENCE mandatory }| PRESENCE mandatory }.Paging --.413 V8. 3GPP .. } TYPE TAIdItem PRESENCE mandatory }. } | TAIdList::= SEQUENCE (SIZE(1..************************************************************** --.. } { {InitialContextSetupFailureIEs} }. } CRITICALITY ignore TYPE UEIdentityIndexValue PRESENCE mandatory } | CRITICALITY ignore TYPE UEPagingID PRESENCE mandatory CRITICALITY ignore TYPE PagingDRX PRESENCE mandatory } | CRITICALITY ignore TYPE PagingCause PRESENCE mandatory } | CRITICALITY ignore TYPE TAIdList PRESENCE mandatory }......Release 8 .0 (2008-03) SAEBearerSetupItemCtxtSUResExtIEs S1AP-PROTOCOL-EXTENSION ::= { .. -.. } 112 3GPP TS 36.************************************************************** Paging ::= SEQUENCE { protocolIEs ...Initial Context Setup Failure --.1. } InitialContextSetupFailureIEs S1AP-PROTOCOL-IES ::= { ID id-MME-UE-S1AP-ID CRITICALITY { ID id-eNB-UE-S1AP-ID CRITICALITY { ID id-Cause CRITICALITY .

UE Context Release Command --.************************************************************** --.UE CONTEXT RELEASE ELEMENTARY PROCEDURE --.. TYPE MME-UE-S1AP-ID TYPE ENB-UE-S1AP-ID TYPE Cause PRESENCE mandatory} | PRESENCE mandatory} | PRESENCE mandatory} .. -. } UEContextReleaseComplete-IEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject { ID id-eNB-UE-S1AP-ID CRITICALITY reject .************************************************************** --. } -.1. } {{UEContextReleaseComplete-IEs}}.************************************************************** --.************************************************************** UEContextReleaseComplete ::= SEQUENCE { protocolIEs ProtocolIE-Container . -. } 113 3GPP TS 36.************************************************************** -....FFS ProtocolExtensionContainer { {TAIdItemExtIEs} } OPTIONAL..Release 8 TAIdItem ::= SEQUENCE { tAId iE-Extensions . 3GPP ...UE Context Release Complete --. TYPE MME-UE-S1AP-ID TYPE ENB-UE-S1AP-ID PRESENCE mandatory} | PRESENCE mandatory} ... } UEContextReleaseCommand-IEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject { ID id-eNB-UE-S1AP-ID CRITICALITY reject { ID id-Cause CRITICALITY ignore . } {{UEContextReleaseCommand-IEs}}.413 V8. TAIdItemExtIEs S1AP-PROTOCOL-EXTENSION ::= { ..************************************************************** UEContextReleaseCommand ::= SEQUENCE { protocolIEs ProtocolIE-Container .0 (2008-03) TAId..

UEContextModificationResponseIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID .************************************************************** --....************************************************************** UEContextModificationRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container .. }-.413 V8..0 (2008-03) -....************************************************************** -.UE Context Modification Response --.************************************************************** --. { { UEContextModificationResponseIEs} }.UE Context Modification --. UEContextModificationFailureIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory PRESENCE mandatory } | } | 3GPP .UE Context Modification Failure --. } PRESENCE mandatory } | PRESENCE mandatory } | PRESENCE optional }.. } PRESENCE mandatory PRESENCE mandatory }.. UEContextModificationRequestIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID { ID id-SecurityInfo CRITICALITY reject TYPE SecurityInfo } -. } { { UEContextModificationRequestIEs} }. . } | { { UEContextModificationFailureIEs} }.************************************************************** UEContextModificationResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container .************************************************************** UEContextModificationFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container .************************************************************** --.Release 8 114 3GPP TS 36.1.************************************************************** --.UE Context Modification Request --.

.413 V8.. } CRITICALITY ignore TYPE Cause 115 PRESENCE mandatory }..************************************************************** UplinkNASTransport ::= SEQUENCE { protocolIEs ..************************************************************** --..INITIAL UE MESSAGE --.************************************************************** InitialUEMessage ::= SEQUENCE { protocolIEs .1. 3GPP TS 36.. InitialUEMessage-IEs S1AP-PROTOCOL-IES ::= { { ID id-eNB-UE-S1AP-ID CRITICALITY reject { ID id-NAS-PDU CRITICALITY reject { ID id-TAId CRITICALITY reject ....Release 8 { ID id-Cause . } TYPE ENB-UE-S1AP-ID TYPE NAS-PDU TYPE TAId PRESENCE mandatory} | PRESENCE mandatory} | PRESENCE mandatory}. } -.0 (2008-03) {{DownlinkNASTransport-IEs}}.************************************************************** --.UPLINK NAS TRANSPORT --. -. ProtocolIE-Container {{UplinkNASTransport-IEs}}. ..************************************************************** DownlinkNASTransport ::= SEQUENCE { protocolIEs ProtocolIE-Container ..DOWNLINK NAS TRANSPORT --. 3GPP . DownlinkNASTransport-IEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory} | { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory} | { ID id-NAS-PDU CRITICALITY reject TYPE NAS-PDU PRESENCE mandatory} | { ID id-ServingPLMN CRITICALITY reject TYPE PLMNidentity PRESENCE optional } | { ID id-HandoverRestrictionList CRITICALITY ignore TYPE HandoverRestrictionList PRESENCE optional }.************************************************************** --.. } ProtocolIE-Container {{InitialUEMessage-IEs}}. } -.

} PRESENCE mandatory} | PRESENCE mandatory} | PRESENCE mandatory} . -.************************************************************** --.************************************************************** --...************************************************************** -..413 V8. } CRITICALITY ignore TYPE Cause PRESENCE mandatory }.RESET ELEMENTARY PROCEDURE --.... ResetIEs S1AP-PROTOCOL-IES ::= { { ID id-Cause . } ProtocolIE-Container { {ResetIEs} }.Reset --. TYPE TYPE TYPE TYPE MME-UE-S1AP-ID ENB-UE-S1AP-ID NAS-PDU Cause PRESENCE mandatory} | PRESENCE mandatory} | PRESENCE mandatory} | PRESENCE mandatory} .1.0 (2008-03) UplinkNASTransport-IEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID { ID id-NAS-PDU CRITICALITY reject TYPE NAS-PDU .************************************************************** --..************************************************************** Reset ::= SEQUENCE { protocolIEs ..************************************************************** -- 3GPP . -...NAS NON DELIVERY INDICATION --. } -. } NASNonDeliveryIndication-IEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject { ID id-eNB-UE-S1AP-ID CRITICALITY reject { ID id-NAS-PDU CRITICALITY ignore { ID id-Cause CRITICALITY ignore . {{NASNonDeliveryIndication-IEs}}.Release 8 } 116 3GPP TS 36.************************************************************** NASNonDeliveryIndication ::= SEQUENCE { protocolIEs ProtocolIE-Container .

S1 SETUP ELEMENTARY PROCEDURE --.************************************************************** --.413 V8.. } TYPE TYPE TYPE TYPE MME-UE-S1AP-ID ENB-UE-S1AP-ID Cause CriticalityDiagnostics PRESENCE PRESENCE PRESENCE PRESENCE optional } optional } optional } optional } | | | .************************************************************** ResetAcknowledge ::= SEQUENCE { protocolIEs ProtocolIE-Container . } 117 3GPP TS 36. ErrorIndicationIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY ignore { ID id-eNB-UE-S1AP-ID CRITICALITY ignore { ID id-Cause CRITICALITY ignore { ID id-CriticalityDiagnostics CRITICALITY ignore . -. } {{ErrorIndicationIEs}}.0 (2008-03) { {ResetAcknowledgeIEs} }.************************************************************** --. -.1. ResetAcknowledgeIEs S1AP-PROTOCOL-IES ::= { { ID id-CriticalityDiagnostics CRITICALITY ignore ..************************************************************** -...************************************************************** -.Release 8 -.. } TYPE CriticalityDiagnostics PRESENCE optional }.************************************************************** --..Reset Acknowledge --.************************************************************** --.S1 Setup Request --.ERROR INDICATION ELEMENTARY PROCEDURE --.Error Indication --. 3GPP ..************************************************************** ErrorIndication ::= SEQUENCE { protocolIEs ProtocolIE-Container .************************************************************** S1SetupRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container { {S1SetupRequestIEs} }..

************************************************************** S1SetupResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container . .1....************************************************************** 3GPP .************************************************************** --... } PRESENCE mandatory }| PRESENCE mandatory }| PRESENCE mandatory }. } 118 3GPP TS 36. S1SetupResponseIEs S1AP-PROTOCOL-IES ::= { { ID id-MMEname CRITICALITY ignore TYPE MMEname { ID id-ServedPLMNs CRITICALITY reject TYPE ServedPLMNs { ID id-GUMMEI-ID CRITICALITY reject TYPE GUMMEI ..************************************************************** --.S1 Setup Response --.Release 8 . { {S1SetupFailureIEs} }..DOWNLINK S1 CDMA2000 TUNNELING ELEMTARY PROCEDURE --.************************************************************** --..0 (2008-03) S1SetupRequestIEs S1AP-PROTOCOL-IES ::= { { ID id-ENB-Global-ID CRITICALITY reject TYPE ENB-Global-ID PRESENCE mandatory { ID id-eNBname CRITICALITY ignore TYPE ENBname PRESENCE mandatory }| { ID id-SupportedTAIs CRITICALITY reject TYPE SupportedTAIs PRESENCE mandatory }.. } -.************************************************************** S1SetupFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container .413 V8.. } TYPE Cause TYPE TimeToWait PRESENCE mandatory }| PRESENCE optional }. } }| { {S1SetupResponseIEs} }. S1SetupFailureIEs S1AP-PROTOCOL-IES ::= { { ID id-Cause CRITICALITY ignore { ID id-TimeToWait CRITICALITY ignore . -. } -.S1 Setup Failure --..************************************************************** -..

1. } TYPE MME-UE-S1AP-ID TYPE ENB-UE-S1AP-ID TYPE Cdma2000PDU PRESENCE mandatory PRESENCE mandatory PRESENCE mandatory } | } | }..************************************************************** UplinkS1cdma2000tunneling ::= SEQUENCE { protocolIEs ProtocolIE-Container .************************************************************** -.UE CAPABILITY INFO INDICATION PROCEDURE --.************************************************************** DownlinkS1cdma2000tunneling ::= SEQUENCE { protocolIEs ProtocolIE-Container ..UPLINK S1 CDMA2000 TUNNELING ELEMTARY PROCEDURE --.************************************************************** --. } 119 3GPP TS 36. DownlinkS1cdma2000tunnelingIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject { ID id-eNB-UE-S1AP-ID CRITICALITY reject { ID id-cdma2000PDU CRITICALITY reject ..413 V8.************************************************************** --.Release 8 --.Downlink S1 CDMA2000 Tunneling --. } TYPE TYPE TYPE TYPE TYPE MME-UE-S1AP-ID ENB-UE-S1AP-ID Cdma2000RATType Cdma2000SectorID Cdma2000PDU PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE mandatory mandatory mandatory mandatory mandatory } | } | } | } | }.UE Capability Info Indication -- 3GPP .Uplink S1 CDMA2000 Tunneling --.0 (2008-03) { {DownlinkS1cdma2000tunnelingIEs} }.... } { {UplinkS1cdma2000tunnelingIEs} }.. UplinkS1cdma2000tunnelingIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject { ID id-eNB-UE-S1AP-ID CRITICALITY reject { ID id-cdma2000RATType CRITICALITY reject { ID id-cdma2000SectorID CRITICALITY reject { ID id-cdma2000PDU CRITICALITY reject ..************************************************************** --.************************************************************** -.************************************************************** --. -. -.

413 V8... } UECapabilityInfoIndicationIEs S1AP-PROTOCOL-IES ::= { ID id-MME-UE-S1AP-ID CRITICALITY { ID id-eNB-UE-S1AP-ID CRITICALITY { ID id-UERadioCapability CRITICALITY . { reject reject ignore TYPE MME-UE-S1AP-ID TYPE ENB-UE-S1AP-ID TYPE UERadioCapability PRESENCE mandatory } | PRESENCE mandatory } | PRESENCE mandatory } . ENBStatusTransferIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory} | { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory} | { ID id-Bearers-SubjectToStatusTransferENB-List CRITICALITY ignore TYPE Bearers-SubjectToStatusTransferENB-List . } { {ENBStatusTransferIEs} }.. lIS-HFN PDCP-SN.eNB STATUS TRANSFER --. ::= SAEB-IE-ContainerList { { Bearers-SubjectToStatusTransferENB-ItemIEs } } Bearers-SubjectToStatusTransferENB-ItemIEs S1AP-PROTOCOL-IES ::= { { ID id-Bearers-SubjectToStatusTransferENB-Item CRITICALITY ignore } TYPE Bearers-SubjectToStatusTransferENB-Item PRESENCE mandatory } Bearers-SubjectToStatusTransferENB-Item ::= SEQUENCE { sAE-Bearer-ID SAE-Bearer-ID. } 3GPP ..eNB Status Transfer --.************************************************************** UECapabilityInfoIndication ::= SEQUENCE { protocolIEs ProtocolIE-Container .1. dL-PDCP-SN-NextToAssign PDCP-SN.************************************************************** --.Release 8 -.************************************************************** ENBStatusTransfer ::= SEQUENCE { protocolIEs ProtocolIE-Container .. } Bearers-SubjectToStatusTransferENB-List PRESENCE mandatory} . } 120 3GPP TS 36.0 (2008-03) { { UECapabilityInfoIndicationIEs} }.. lIS PDCP-SN..************************************************************** --. dL-PDCP-HFN-NextToAssign PDCP-SN..************************************************************** -. -.. .. iE-Extensions ProtocolExtensionContainer { {Bearers-SubjectToStatusTransferENB-ItemExtIEs} } OPTIONAL.

lIS PDCP-SN..MME STATUS TRANSFER --..Release 8 121 3GPP TS 36. iE-Extensions ProtocolExtensionContainer { {Bearers-SubjectToStatusTransferMME-ItemExtIEs} } OPTIONAL..************************************************************** --..1..MME Status Transfer --.. lIS-HFN PDCP-SN.************************************************************** -.413 V8. } Bearers-SubjectToStatusTransferMME-ItemExtIEs S1AP-PROTOCOL-EXTENSION ::= { . ::= SAEB-IE-ContainerList { { Bearers-SubjectToStatusTransferMME-ItemIEs } } Bearers-SubjectToStatusTransferMME-ItemIEs S1AP-PROTOCOL-IES ::= { { ID id-Bearers-SubjectToStatusTransferMME-Item CRITICALITY ignore } TYPE Bearers-SubjectToStatusTransferMME-Item PRESENCE mandatory } Bearers-SubjectToStatusTransferMME-Item ::= SEQUENCE { sAE-Bearer-ID SAE-Bearer-ID.************************************************************** MMEStatusTransfer ::= SEQUENCE { protocolIEs ProtocolIE-Container .. MMEStatusTransferIEs S1AP-PROTOCOL-IES ::= { { ID id-MME-UE-S1AP-ID CRITICALITY reject TYPE MME-UE-S1AP-ID PRESENCE mandatory} | { ID id-eNB-UE-S1AP-ID CRITICALITY reject TYPE ENB-UE-S1AP-ID PRESENCE mandatory} | { ID id-Bearers-SubjectToStatusTransferMME-List CRITICALITY ignore TYPE Bearers-SubjectToStatusTransferMME-List .. . } -. } { {MMEStatusTransferIEs} }. dL-PDCP-HFN-NextToAssign PDCP-SN. } END 3GPP . dL-PDCP-SN-NextToAssign PDCP-SN.0 (2008-03) Bearers-SubjectToStatusTransferENB-ItemExtIEs S1AP-PROTOCOL-EXTENSION ::= { . } Bearers-SubjectToStatusTransferMME-List PRESENCE mandatory} ..************************************************************** --..

4 Information Element Definitions -.A AllocationRetentionPriority ::= SEQUENCE { priorityLevel PriorityLevel. id-SAEBearerItem. ProtocolIE-ID.413 V8. maxnoofForbTAIs FROM S1AP-Constants Criticality. maxNrOfErrors.. -.. S1AP-PROTOCOL-EXTENSION.Release 8 122 3GPP TS 36. ProtocolIE-SingleContainer{}.************************************************************** --. 3GPP .0 (2008-03) 9. . maxnoofTAIs.************************************************************** S1AP-IEs { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) eps-Access (20) modules (3) s1ap (1) version1 (1) s1ap-IEs (2) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS id-SAEBearerInformationListItem. maxnoofEPLMNs. maxnoofForbLACs. iE-Extensions ProtocolExtensionContainer { {AllocationRetentionPriority-ExtIEs} } OPTIONAL. maxNrOfSAEBs. S1AP-PROTOCOL-IES FROM S1AP-Containers. ProcedureCode. maxNrOfInterfaces.3. maxnoofPLMNsPerMME.1. TriggeringMessage FROM S1AP-CommonDataTypes ProtocolExtensionContainer{}. maxnoofEPLMNsPlusOne. maxnoofBPLMNs.Information Element Definitions --.

. maxnoofBPLMNs)) OF PLMNidentity -.B BPLMNs ::= SEQUENCE (SIZE(1. CauseMisc.. unspecified.Release 8 } AllocationRetentionPriority-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . } 3GPP . CauseTransport. CauseNas.0 (2008-03) SAE-Bearer-BitRate. om-intervention.. } CauseRadioNetwork.. } 123 3GPP TS 36. SAE-Bearer-BitRate. hardware-failure. unspecified.. Aggregate-MaximumBitrates-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . CauseProtocol. abstract-syntax-error-reject. } -. } CauseProtocol ::= ENUMERATED { transfer-syntax-error.. abstract-syntax-error-falsely-constructed-message.. message-not-compatible-with-receiver-state.C Cause ::= CHOICE { radioNetwork transport nas protocol misc . abstract-syntax-error-ignore-and-notify. } AggregateMaximumBitrate ::= SEQUENCE { aggregateMaximumBitRateDL aggregateMaximumBitRateUL iE-Extensions .1. semantic-error.... . CauseMisc ::= ENUMERATED { control-processing-overload. not-enough-user-plane-processing-resources.413 V8. .. ProtocolExtensionContainer { {Aggregate-MaximumBitrates-ExtIEs} } OPTIONAL...

. .413 V8. } Cdma2000SectorID ::= OCTET STRING CGI ::= SEQUENCE { pLMNidentity lAC cI } PLMNidentity. CriticalityDiagnostics-IE-List OPTIONAL.. } CauseNas ::= ENUMERATED { normal-release. TriggeringMessage OPTIONAL.1. tx2relocoverall-expiry.0 (2008-03) Cdma2000PDU ::= OCTET STRING Cdma2000RATType ::= ENUMERATED { hRPD. Criticality OPTIONAL. } 3GPP .. ProtocolExtensionContainer {{CriticalityDiagnostics-ExtIEs}} OPTIONAL. handover-cancelled.Release 8 CauseRadioNetwork ::= ENUMERATED { unspecified.. } CauseTransport ::= ENUMERATED { transport-resource-unavailable... . . authentication-failure. onexRTT. unspecified.. CI CI ::= OCTET STRING (SIZE (2)) { ProcedureCode OPTIONAL. LAC.. handover-triggered. } 124 3GPP TS 36... detach. release-due-to-eutran-generated-reason. CriticalityDiagnostics ::= SEQUENCE procedureCode triggeringMessage procedureCriticality iEsCriticalityDiagnostics iE-Extensions . unspecified. successful-handover. .

. iE-ID ProtocolIE-ID..F ForbiddenInterRATs ::= ENUMERATED { all.65535) ::= TBCD-STRING ::= INTEGER (0...maxnoofEPLMNs)) OF PLMNidentity ExtendedRNC-ID -. utran.. iE-Extensions ProtocolExtensionContainer {{CriticalityDiagnostics-IE-Item-ExtIEs}} OPTIONAL. } 125 3GPP TS 36..... typeOfError TypeOfError OPTIONAL.1. maxnoofEPLMNsPlusOne)) OF ForbiddenTAs-Item ::= INTEGER (4096..65535) 3GPP ..D DL-Forwarding ::= ENUMERATED { dL-Forwarding-proposed. } ForbiddenTAs ::= SEQUENCE (SIZE(1. } -. . } -. geran.E ENB-UE-S1AP-ID ENB-Global-ID ENBname ::= OCTET STRING EPLMNs ::= SEQUENCE (SIZE(1. .. } CriticalityDiagnostics-IE-Item-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { .. . } Direct-Forwarding-Path-Availability ::= ENUMERATED { directPathAvailable.413 V8. ..0 (2008-03) CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1.maxNrOfErrors)) OF CriticalityDiagnostics-IE-Item CriticalityDiagnostics-IE-Item ::= SEQUENCE { iECriticality Criticality...Release 8 CriticalityDiagnostics-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { ..

iE-Extensions ProtocolExtensionContainer { {HandoverRestrictionList-ExtIEs} } OPTIONAL.H HandoverRestrictionList ::= SEQUENCE { equivalentPLMNs EPLMNs OPTIONAL.. ltetogeran. forbiddenLACs ForbiddenLACs } ForbiddenLACs ::= SEQUENCE (SIZE(1.. ltetoutran. forbiddenInterRATs ForbiddenInterRATs OPTIONAL. utrantolte.. forbiddenTAIs ForbiddenTAIs } ForbiddenTAIs ::= SEQUENCE (SIZE(1.. forbiddenLAs ForbiddenLAs OPTIONAL. } -.. mMME-Code MME-Code. 3GPP .G GTP-TEID ::= OCTET STRING (SIZE (4)) GUMMEI ::= SEQUENCE { pLMN-Identity PLMNidentity. iE-Extensions ProtocolExtensionContainer { {GUMMEI-ExtIEs} } OPTIONAL.1..413 V8. .0 (2008-03) ForbiddenLAs ::= SEQUENCE (SIZE(1. . } HandoverType ::= ENUMERATED { intralte.maxnoofForbTAIs)) OF TAI 126 3GPP TS 36.maxnoofEPLMNsPlusOne)) OF ForbiddenLAs-Item ForbiddenLAs-Item ::= SEQUENCE { pLMN-Identity PLMNidentity.. mME-Group-ID MME-Group-ID.Release 8 ForbiddenTAs-Item ::= SEQUENCE { pLMN-Identity PLMNidentity. } HandoverRestrictionList-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { .. forbiddenTAs ForbiddenTAs OPTIONAL... } GUMMEI-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { .maxnoofForbLACs)) OF LAC -..

8)) 127 3GPP TS 36. LAC ::= OCTET STRING (SIZE (2)) LAI ::= SEQUENCE { pLMNidentity lAC iE-Extensions } PLMNidentity.maxNrOfInterfaces)) OF InterfacesToTraceItem InterfacesToTraceItem ::= SEQUENCE { interfaceType InterfaceType. LAC..I IMSI ::= OCTET STRING (SIZE (3. . } -... x2..M MMEname ::= OCTET STRING MME-Group-ID MME-Code ::= OCTET STRING (SIZE (2)) ::= OCTET STRING (SIZE (1)) 3GPP ..J -.256) OPTIONAL. ProtocolExtensionContainer { {LAI-ExtIEs} } OPTIONAL LAI-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { .0 (2008-03) InterfacesToTraceList ::= SEQUENCE (SIZE (1.K -. } InterfaceType ::= ENUMERATED { s1.. traceDepth TraceDepth.413 V8..L Label ::= INTEGER (1. iE-Extensions ProtocolExtensionContainer { {InterfacesToTraceItem-ExtIEs} } .1... } -... } -. } InterfacesToTraceItem-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . ..Release 8 gerantolte. uu..

.Release 8 MME-UE-S1AP-ID M-TMSI ::= TBCD-STRING ::= OCTET STRING (SIZE (4)) 128 3GPP TS 36... maxNrOfSAEBs)) OF ProtocolIE-SingleContainer { { SAEBearerInformationListIEs } } SAEBearerInformationList SAEBearerInformationListIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerInformationListItem CRITICALITY ignore .0 (2008-03) -.15) -...FFS PLMNidentity PriorityLevel ::= TBCD-STRING ::= INTEGER (0..1. terminating-streaming-call...P PagingDRX ::= INTEGER (0.O -.. 3GPP .Q -. terminating-background-call.R RAC ::= OCTET STRING (SIZE (1)) RNC-ID RRC-Container -.S SAE-Bearer-ID ::= INTEGER (0.4095) ::= OCTET STRING ::= OCTET STRING ::= SEQUENCE (SIZE (1. terminating-low-priority-signalling.4095) PagingCause ::= ENUMERATED { terminating-conversational-call. terminating-interactive-call. . terminating-high-priority-signalling } PDCP-SN ::= INTEGER -.N NAS-PDU ::= OCTET STRING -.413 V8. } SAEBearerInformationListItem ::= SEQUENCE { TYPE SAEBearerInformationListItem PRESENCE mandatory }.

. allocationRetentionPriority AllocationRetentionPriority OPTIONAL. } TYPE SAEBearerItem PRESENCE mandatory }.. } SAEBearerInformationListItem-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . Cause. } SAE-Bearer-QoSParameters-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . SAE-Bearer-BitRate.. ProtocolExtensionContainer { {SAEBearerInformationListItem-ExtIEs} } 3GPP TS 36.... SAE-Bearer-ID..10000000) SAE-BearerLevelQoSParameters ::= SEQUENCE { label Label. ProtocolExtensionContainer { {SAEBearerItem-ExtIEs} } OPTIONAL. . 3GPP .0 (2008-03) OPTIONAL.. } SAE-Bearer-BitRate ::= INTEGER (0. } SAE-Bearer-Type ::= CHOICE { sAE-GBR-Bearer SAE-GBR-Bearer. sAE-non-GBR-Bearer SAE-non-GBR-Bearer. maxNrOfSAEBs)) OF ProtocolIE-SingleContainer { {SAEBearerItemIEs} } SAEBearerItemIEs S1AP-PROTOCOL-IES ::= { { ID id-SAEBearerItem CRITICALITY reject ..Release 8 sAE-Bearer-ID dL-Forwarding iE-Extensions . } SAE-GBR-Bearer ::= SEQUENCE { sAE-Bearer-MaximumBitrateDL sAE-Bearer-MaximumBitrateUL sAE-Bearer-GuaranteedBitrateDL SAE-Bearer-BitRate. DL-Forwarding. SAEBearerItem-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . SAE-Bearer-BitRate... sAE-BearerType SAE-Bearer-Type.413 V8. .. } 129 SAE-Bearer-ID..... iE-Extensions ProtocolExtensionContainer { {SAE-Bearer-QoSParameters-ExtIEs} } OPTIONAL.. } SAEBearerItem ::= SEQUENCE { sAE-Bearer-ID cause iE-Extensions .1. SAEBearerList ::= SEQUENCE (SIZE(0..

.. iE-Extensions ProtocolExtensionContainer { { SecurityInformation-ExtIEs} } OPTIONAL.. } SecurityInfo ::= SEQUENCE { securityKey SecurityKey.. . } SecurityInformation ::= SEQUENCE { securityPlaceHolder SecurityPlaceHolder. } SecurityInformation-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { .. } SAE-non-GBR-Bearer-Parameters-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { .0 (2008-03) SAE-non-GBR-Bearer ::= SEQUENCE { sAE-non-GBR-Bearer-Type iE-Extensions . ..413 V8. 3GPP TS 36.1. SAE-non-GBR-Bearer-Type ::= ENUMERATED { non-GBR-Bearer. .. } SAE-non-GBR-Bearer-Type..Release 8 sAE-Bearer-GuaranteedBitrateUL iE-Extensions . ProtocolExtensionContainer { {SAE-non-GBR-Bearer-Parameters-ExtIEs} } OPTIONAL..... } 3GPP .. .. } SecurityPlaceHolder ::= ENUMERATED { whatever. } SecurityKey ::= BIT STRING (SIZE(128)) SecurityInfo-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { .. } 130 SAE-Bearer-BitRate. iE-Extensions ProtocolExtensionContainer { { SecurityInfo-ExtIEs} } OPTIONAL.... } SAE-GBR-Bearer-Parameters-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . ProtocolExtensionContainer { {SAE-GBR-Bearer-Parameters-ExtIEs} } OPTIONAL...

..T TAI ::= OCTET STRING TAId ::= OCTET STRING TBCD-STRING ::= OCTET STRING (SIZE (3)) 3GPP .. m-TMSI M-TMSI. iE-Extensions ProtocolExtensionContainer { {SourceeNodeB-ToTargeteNodeB-TransparentContainer-ExtIEs} } OPTIONAL. PLMNidentity. ENB-Global-ID -.0 (2008-03) SourceeNB-ID..413 V8.. . . maxnoofTAIs)) OF SupportedTAs-Item SupportedTAs-Item ::= tAI broadcastPLMNs . } SourceeNodeB-ToTargeteNodeB-TransparentContainer-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { . maxnoofPLMNsPerMME)) OF PLMNidentity SupportedTAIs ::= SEQUENCE (SIZE(1. BPLMNs. { -. } S-TMSI ::= SEQUENCE { mMEC MME-Code..1..... sAEBearerInformationList SAEBearerInformationList OPTIONAL. } SourceeNB-ID ::= SEQUENCE { pLMNidentity eNB-Global-ID } ::= OCTET STRING 131 3GPP TS 36.Release 8 SourceBSS-ToTargetBSS-TransparentContainer SourceID ::= SEQUENCE { sourceeNB-ID . } SEQUENCE TAId...FFS SourceeNodeB-ToTargeteNodeB-TransparentContainer ::= SEQUENCE { rRC-Container RRC-Container. } SourceRNC-ToTargetRNC-TransparentContainer ::= OCTET STRING ServedPLMNs ::= SEQUENCE (SIZE(1.

} TraceReference ::= OCTET STRING (SIZE (3)) TypeOfError ::= ENUMERATED { not-understood. .1... TargetRNC-ID. ..FFS OPTIONAL.Release 8 TargetID ::= CHOICE { targeteNB-ID targetRNC-ID cGI CGI. vendorMaximum..413 V8... maximum. 3GPP .. vendorMinimum. vendorMedium. missing.0 (2008-03) PLMNidentity. medium. ENB-Global-ID -. rAC RAC rNC-ID RNC-ID } TargeteNB-ID. . } TargeteNB-ID ::= SEQUENCE { pLMNidentity eNB-Global-ID } TargetRNC-ID ::= SEQUENCE { lAI LAI. 132 3GPP TS 36. } TraceDepth ::= ENUMERATED { minimum. TargeteNodeB-ToSourceeNodeB-TransparentContainer ::= OCTET STRING TargetRNC-ToSourceRNC-TransparentContainer ::= OCTET STRING TargetBSS-ToSourceBSS-TransparentContainer ::= OCTET STRING TimeToWait ::= OCTET STRING TransportLayerAddress ::= OCTET STRING TraceActivation ::= SEQUENCE { traceReference interfacesToTraceList iE-Extensions } TraceReference.. InterfacesToTraceList. ProtocolExtensionContainer { { TraceActivation-ExtIEs} } OPTIONAL TraceActivation-ExtIEs S1AP-PROTOCOL-EXTENSION ::= { .

. .0 (2008-03) -----END V W X Y Z 3GPP .Release 8 } -..413 V8.U UEIdentityIndexValue UEPagingID ::= CHOICE { s-TMSI S-TMSI. } UERadioCapability ::= OCTET STRING ::= OCTET STRING 133 3GPP TS 36.1. iMSI IMSI.

3. OBJECT IDENTIFIER ::= INTEGER (0.3. unsuccessfull-outcome } 9..Common definitions --..************************************************************** --.65535) ::= ENUMERATED { initiating-message.1.Release 8 134 3GPP TS 36. notify } ::= ENUMERATED { optional.5 Common Definitions -.Constant definitions --.************************************************************** S1AP-Constants { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) eps-Access (20) modules (3) s1ap (1) version1 (1) s1ap-Constants (4) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN 3GPP .255) ProtocolExtensionID ::= INTEGER (0. ignore.************************************************************** --.************************************************************** S1AP-CommonDataTypes { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) eps-Access (20) modules (3) s1ap (1) version1 (1) s1ap-CommonDataTypes (3) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN Criticality Presence PrivateIE-ID local global } ProcedureCode ::= ENUMERATED { reject. mandatory } ::= CHOICE { INTEGER (0..6 Constant Definitions -.0 (2008-03) 9. conditional. successful-outcome.413 V8..65535).65535) ProtocolIE-ID TriggeringMessage END ::= INTEGER (0.

1.************************************************************** --.0 (2008-03) -.************************************************************** id-HandoverPreparation id-HandoverResourceAllocation id-HandoverNotification id-PathSwitchRequest id-HandoverCancel id-SAEBearerSetup id-SAEBearerModify id-SAEBearerRelease id-SAEBearerReleaseRequest id-InitialContextSetup id-Paging id-downlinkNASTransport id-initialUEMessage id-uplinkNASTransport id-Reset id-ErrorIndication id-NASNonDeliveryIndication id-S1Setup id-UEContextReleaseRequest id-DownlinkS1cdma2000tunneling id-UplinkS1cdma2000tunneling id-UEContextModification id-UECapabilityInfoIndication id-UEContextRelease id-eNBStatusTransfer id-MMEStatusTransfer ProcedureCode ::= 0 ProcedureCode ::= 1 ProcedureCode ::= 2 ProcedureCode ::= 3 ProcedureCode ::= 4 ProcedureCode ::= 5 ProcedureCode ::= 6 ProcedureCode ::= 7 ProcedureCode ::= 8 ProcedureCode ::= 9 ProcedureCode ::= 10 ProcedureCode ::= 11 ProcedureCode ::= 12 ProcedureCode ::= 13 ProcedureCode::= 14 ProcedureCode ::= 15 ProcedureCode ::= 16 ProcedureCode ::= 17 ProcedureCode ::= 18 ProcedureCode ::= 19 ProcedureCode ::= 20 ProcedureCode ::= 21 ProcedureCode ::= 22 ProcedureCode ::= 23 ProcedureCode ::= 24 ProcedureCode ::= 25 -. --. ProtocolIE-ID FROM S1AP-CommonDataTypes.************************************************************** 3GPP .Elementary Procedures --.Extension constants --.************************************************************** --.413 V8.Release 8 -.************************************************************** IMPORTS ProcedureCode.IE parameter types from other modules.************************************************************** --. 135 3GPP TS 36.

Release 8 maxPrivateIEs INTEGER ::= 65535 maxProtocolExtensions INTEGER ::= 65535 maxProtocolIEs INTEGER ::= 65535 -.1.IEs --.************************************************************** id-MME-UE-S1AP-ID id-HandoverType id-Cause id-SourceID id-TargetID id-Intra-LTEHOInformationReq id-LTEtoUTRANHOInformationReq id-LTEtoGERANHOInformationReq id-eNB-UE-S1AP-ID id-Intra-LTEHOInformationRes id-LTEtoUTRANHOInformationRes id-LTEtoGERANHOInformationRes id-SAEBearerSubjecttoDataForwardingList id-SAEBearertoReleaseListHOCmd id-SAEBearerDataForwardingItem id-SAEBearerReleaseItemBearerRelComp id-SAEBearerToBeSetupListBearerSUReq id-SAEBearerToBeSetupItemBearerSUReq id-SAEBearerAdmittedList id-SAEBearerFailedToSetupListHOReqAck id-SAEBearerAdmittedItem id-SAEBearerFailedtoSetupItemHOReqAck id-SAEBearerToBeSwitchedDLList ProtocolIE-ID ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ProtocolIE-ID ::= ::= 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 3GPP .Lists --.FFS Value to be checked -.FFS Value to be checked 256 -.413 V8.FFS 256 -.************************************************************** --.FFS 15 16 256 -.************************************************************** maxNrOfSAEBs maxNrOfInterfaces maxnoofTAI maxNrOfErrors maxnoofBPLMNs maxnoofPLMNsPerMME maxnoofTAIs maxnoofEPLMNs maxnoofEPLMNsPlusOne maxnoofForbLACs maxnoofForbTAIs INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 136 3GPP TS 36.0 (2008-03) 256 3 --FFS 256 --FFS 256 6 32 -.************************************************************** --.

413 V8.Release 8 id-SAEBearerToBeSwitchedDLItem id-SAEBearerToBeSetupListCtxtSUReq id-TraceActivation id-NAS-PDU id-SAEBearerToBeSetupItemHOReq id-SAEBearerSetupListBearerSURes id-SAEBearerFailedToSetupListBearerSURes id-SAEBearerToBeModifiedListBearerModReq id-SAEBearerModifyListBearerModRes id-SAEBearerFailedToModifyList id-SAEBearerToBeReleasedList id-SAEBearerFailedToReleaseList id-SAEBearerItem id-SAEBearerToBeModifiedItemBearerModReq id-SAEBearerModifyItemBearerModRes id-SAEBearerReleaseItem id-SAEBearerSetupItemBearerSURes id-Security-Information id-HandoverRestrictionList id-UEPagingID id-pagingDRX id-pagingCause id-TAIdList id-TAIdItem id-SAEBearerFailedToSetupListCtxtSURes id-SAEBearerReleaseItemHOCmd id-SAEBearerSetupItemCtxtSURes id-SAEBearerSetupListCtxtSURes id-SAEBearerToBeSetupItemCtxtSUReq id-SAEBearerToBeSetupListHOReq id-GERANtoLTEHOInformationReq id-GERANtoLTEHOInformationRes id-UTRANtoLTEHOInformationReq id-UTRANtoLTEHOInformationRes id-CriticalityDiagnostics id-ENB-Global-ID id-eNBname id-MMEname id-ServedPLMNs id-SupportedTAIs id-TimeToWait id-aggregateMaximumBitrate id-TAId id-ServingPLMN id-SAEBearerReleaseListBearerRelComp id-cdma2000PDU id-cdma2000RATType id-cdma2000SectorID id-SecurityInfo id-UERadioCapability id-GUMMEI-ID id-Bearers-SubjectToStatusTransferENB-List id-Bearers-SubjectToStatusTransferENB-Item ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 137 3GPP TS 36.1.0 (2008-03) 3GPP .

************************************************************** --.3. -.Class Definition for Protocol IEs --. ProtocolIE-ID FROM S1AP-CommonDataTypes maxPrivateIEs. --. Presence.7 Container Definitions -.************************************************************** S1AP-Containers { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) eps-Access (20) modules (3) s1ap (1) version1 (1) s1ap-Containers (5) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN -.************************************************************** --.Container definitions --.IE parameter types from other modules.Release 8 id-SAEBearerInformationListItem id-Direct-Forwarding-Path-Availability id-UEIdentityIndexValue id-Bearers-SubjectToStatusTransferMME-List id-Bearers-SubjectToStatusTransferMME-Item END ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= 78 79 80 80 81 138 3GPP TS 36.1.************************************************************** --. 3GPP . maxProtocolExtensions.413 V8. maxProtocolIEs FROM S1AP-Constants.0 (2008-03) 9. ProtocolExtensionID. PrivateIE-ID.************************************************************** IMPORTS Criticality.************************************************************** S1AP-PROTOCOL-IES ::= CLASS { &id ProtocolIE-ID UNIQUE.

Presence 139 3GPP TS 36.1. &Extension.************************************************************** S1AP-PROTOCOL-IES-PAIR ::= CLASS { &id ProtocolIE-ID &firstCriticality Criticality. 3GPP .413 V8. &presence Presence } WITH SYNTAX { ID &id CRITICALITY &criticality EXTENSION &Extension PRESENCE &presence } UNIQUE.Class Definition for Protocol IEs --.************************************************************** S1AP-PROTOCOL-EXTENSION ::= CLASS { &id ProtocolExtensionID &criticality Criticality. &presence } WITH SYNTAX { ID CRITICALITY TYPE PRESENCE } Criticality.Release 8 &criticality &Value.************************************************************** --. &secondCriticality Criticality.0 (2008-03) &id &criticality &Value &presence -. &presence Presence } WITH SYNTAX { ID &id FIRST CRITICALITY &firstCriticality FIRST TYPE &FirstValue SECOND CRITICALITY &secondCriticality SECOND TYPE &SecondValue PRESENCE &presence } UNIQUE. -. &FirstValue.Class Definition for Protocol Extensions --. &SecondValue.************************************************************** --.

3GPP .Container for Protocol IE Pairs --.&criticality ({IEsSetParam}{@id}).maxProtocolIEs)) OF ProtocolIE-FieldPair {{IEsSetParam}} ProtocolIE-FieldPair {S1AP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE { id S1AP-PROTOCOL-IES-PAIR. value S1AP-PROTOCOL-IES. firstValue S1AP-PROTOCOL-IES-PAIR. secondCriticality S1AP-PROTOCOL-IES-PAIR.&secondCriticality ({IEsSetParam}{@id}).0 (2008-03) ProtocolIE-Field {S1AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { id S1AP-PROTOCOL-IES.************************************************************** --. &presence Presence } WITH SYNTAX { ID &id CRITICALITY &criticality TYPE &Value PRESENCE &presence } -.maxProtocolIEs)) OF ProtocolIE-Field {{IEsSetParam}} ProtocolIE-SingleContainer {S1AP-PROTOCOL-IES : IEsSetParam} ::= ProtocolIE-Field {{IEsSetParam}} 140 3GPP TS 36.************************************************************** --. criticality S1AP-PROTOCOL-IES.Container for Protocol IEs --.&Value ({IEsSetParam}{@id}) } -. firstCriticality S1AP-PROTOCOL-IES-PAIR.************************************************************** S1AP-PRIVATE-IES ::= CLASS { &id PrivateIE-ID.&id ({IEsSetParam}).Release 8 -... &Value.************************************************************** ProtocolIE-ContainerPair {S1AP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE (SIZE (0.&firstCriticality ({IEsSetParam}{@id}).&FirstValue ({IEsSetParam}{@id}).1.Class Definition for Private IEs --.************************************************************** --.413 V8.&id ({IEsSetParam}). &criticality Criticality.************************************************************** ProtocolIE-Container {S1AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE (SIZE (0.

maxProtocolExtensions)) OF ProtocolExtensionField {{ExtensionSetParam}} ProtocolExtensionField {S1AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { id S1AP-PROTOCOL-EXTENSION.0 (2008-03) ProtocolIE-ContainerList {INTEGER : lowerBound. criticality S1AP-PROTOCOL-EXTENSION.************************************************************** S1AP-PROTOCOL-IES-PAIR.************************************************************** PrivateIE-Container {S1AP-PRIVATE-IES : IEsSetParam } ::= SEQUENCE (SIZE (1.&criticality ({IEsSetParam}{@id}).Container Lists for Protocol IE Containers --.Container for Private IEs --.&Value ({IEsSetParam}{@id}) } END 3GPP .&criticality ({ExtensionSetParam}{@id}).upperBound)) OF ProtocolIE-SingleContainer {{IEsSetParam}} ProtocolIE-ContainerPairList {INTEGER : lowerBound.upperBound)) OF ProtocolIE-ContainerPair {{IEsSetParam}} -.************************************************************** --. INTEGER : upperBound.************************************************************** --..1.. extensionValue S1AP-PROTOCOL-EXTENSION.&id ({IEsSetParam}).&id ({ExtensionSetParam}). S1AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE (SIZE (lowerBound.&SecondValue 141 ({IEsSetParam}{@id}) 3GPP TS 36.Container for Protocol Extensions --.Release 8 secondValue } -. INTEGER : upperBound..************************************************************** ProtocolExtensionContainer {S1AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE (SIZE (1. value S1AP-PRIVATE-IES.&Extension ({ExtensionSetParam}{@id}) } -. maxPrivateIEs)) OF PrivateIE-Field {{IEsSetParam}} PrivateIE-Field {S1AP-PRIVATE-IES : IEsSetParam} ::= SEQUENCE { id S1AP-PRIVATE-IES.************************************************************** --.413 V8. S1AP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE (SIZE (lowerBound. criticality S1AP-PRIVATE-IES..

Specifies the maximum time for Reset procedure in the MME. Specifies a guard period in the eNB before sending a RESET ACKNOWLEDGE message. 9.5 TRafC TRatC TRafR TRatR - Timers Specifies the maximum time for Reset procedure in the eNB.413 V8. Specifies a guard period in the CN before sending a RESET ACKNOWLEDGE message.1.0 (2008-03) 9. 3GPP .Release 8 142 3GPP TS 36.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ref. [3].4 Message Transfer Syntax S1AP shall use the ASN.

3 and 10. E. Examples for Transfer Syntax Errors are: Violation of value ranges in ASN. Logical Error.1 Abstract Syntax Error General An Abstract Syntax Error occurs when the receiving functional S1AP entity: 3GPP .1. Violation in list element constraints.2 Transfer Syntax Error A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message.1 decoding. The information stated in subclauses 10. If a Transfer Syntax Error occurs.g. Missing mandatory elements in ASN.1 SEQUENCE definitions (as sent by the originator of the message). This is also valid for the case when the reporting is done with a response message. 10.3.4. The latter is an exception to what is stated in subclause 4.Release 8 143 3GPP TS 36.1 - Handling of Unknown.1: INTEGER (0. and 12 elements will be received. Wrong order of elements in ASN. Unforeseen and Erroneous Protocol Data General Protocol Error cases can be divided into three classes: Transfer Syntax Error. is what at minimum shall be included.1 SEQUENCE definitions (as sent by the originator of the message).1 definition of messages.0 (2008-03) 10 10.: If an IE has a defined value range of 0 to 10 (ASN. 10. Abstract Syntax Error.413 V8. then this will be treated as a transfer syntax error. Protocol errors can occur in the following functions within a receiving node: S1AP functional entity Logical Errors Abstract Syntax Errors ASN.1. 10.g.1 Decoding Transfer Syntax Errors Figure 10. and 12 will be received. Transfer syntax errors are always detected in the process of ASN. to be included in the message used when reporting an error.: If a list is defined as containing 1 to 10 elements. than this case will be handled as a transfer syntax error. if available.10)).1: Protocol Errors in S1AP. the receiver should initiate Error Indication procedure with appropriate cause value for the Transfer Syntax protocol error.2..3 10. Other optional information elements within the message may also be included. E.

the entire item (IE or IE group) which is not (fully or partially) comprehended shall be treated in accordance with its own criticality information as specified in subclause 10. and when action based on criticality information is applicable: 1. The handling of cases 4 and 5 is specified in subclause 10. and 12 will be received.e. receives IEs or IE groups that cannot be understood (unknown IE ID). the criticality information is used in case of the missing IE/IE group abstract syntax error (see subclause 10. this case will be handled as an abstract syntax error using criticality information sent by the originator of the message). Cases 1 and 2 (not comprehended IE/IE group) are handled based on received Criticality information. or an EP not comprehended (not implemented). S1AP specifies separately if the presence of these IEs/IE groups is optional or mandatory with respect to RNS application by means of the presence field of the concerning object of class S1AP-PROTOCOL-IES. In addition.3.413 V8. 10. S1AP-PROTOCOLEXTENSION or S1AP-PRIVATE-IES. even if another EP from that standard version is comprehended. 2. an IE group.3.: ASN. and action based on criticality shall be applied. the receiver shall read the remaining message and shall then for each detected Abstract Syntax Error that belong to cases 1-3 act according to the Criticality Information and Presence Information for the IE/IE group due to which Abstract Syntax Error occurred in accordance with subclauses 10.2 Criticality Information In the S1AP messages there is criticality information set for individual IEs and/or IE groups. receives IEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of the same IE or IE group. EP: The comprehension of different Eps within a standard version or between different standard versions is not mandated.3.5. does not receive IEs or IE groups but according to the specified presence of the concerning object.1 transfer syntax. IE or IE group: When one new or modified IE or IE group is implemented for one EP from a standard version.3.4 and 10. S1AP-PROTOCOL-IES-PAIR. receives IEs or IE groups but according to the conditional presence of the concerning object and the specified condition. Case 4 (IEs or IE groups in wrong order or with too many occurrences) and Case 5 (erroneously present conditional IEs or IE groups) result in rejecting the procedure. Case 3 (missing IE/IE group) is handled based on Criticality information and Presence information for the missing IE/IE group specified in the version of the specification used by the receiver. the IEs or IE groups should not have been present in the received message. The presence field of the indicated classes supports three values: 3GPP . Ignore IE and Notify Sender.4. The three possible values of the Criticality Information for an IE/IE group are: Reject IE. The receiving node shall take different actions depending on the value of the Criticality Information.3. 10. The following rules restrict when a receiving entity may consider an IE. This criticality information instructs the receiver how to act when receiving an IE or an IE group that is not comprehended.3.g. the IEs or IE groups should have been present in the received message.3. 4.1.6. Any EP that is not supported may be considered not comprehended. receives IEs for which the logical range is violated (e. then other new or modified IEs or IE groups specified for that EP in that standard version shall be considered comprehended by a receiving entity (some may still remain unsupported). the logical range is 0 to 10 (values 11 to 15 are undefined). i.Release 8 144 3GPP TS 36.3 Presence Information For many IEs/IE groups which are optional according to the ASN. 5. If an Abstract Syntax Error occurs. 3. 2.5).1 definition: 0 to 15.0 (2008-03) 1. Ignore IE.

the receiving node shall ignore the procedure and initiate the Error Indication procedure.4.3.4. When using the Error Indication procedure to reject a procedure or to report an ignored procedure it shall include the Procedure Code IE. 2.413 V8.Release 8 145 3GPP TS 36.1.1 Not comprehended IE/IE group Procedure Code The receiving node shall treat the different types of received criticality information of the Procedure Code IE according to the following: Reject IE: If a message is received with a Procedure Code IE marked with "Reject IE" which the receiving node does not comprehend.4. the receiving node shall terminate the procedure and initiate the Error Indication procedure. 10. Conditional. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure. 10. - 3GPP . 3. the Triggering Message IE.3. If a message initiating a procedure that does not have a message to report unsuccessful outcome is received containing one or more IEs/IE groups marked with "Reject IE" which the receiving node does not comprehend.1A Type of Message When the receiving node cannot decode the Type of Message IE. the receiving node shall ignore the procedure. Mandatory. Ignore IE and Notify Sender: If a message is received with a Procedure Code IE marked with "Ignore IE and Notify Sender" which the receiving node does not comprehend. and the Procedure Criticality IE in the Criticality Diagnostics IE. The receiving node shall reject the procedure and report the rejection of one or more IEs/IE group using the message normally used to report unsuccessful outcome of the procedure. If an IE/IE group is not included in a received message and the presence of the IE/IE group is mandatory or the presence is conditional and the condition is true according to the version of the specification used by the receiver. the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. Ignore IE: If a message is received with a Procedure Code IE marked with "Ignore IE" which the receiving node does not comprehend.3. the Error Indication procedure shall be initiated with an appropriate cause value. Optional.4 10. an abstract syntax error occurs due to this erroneously present conditional IE/IE group. none of the functional requests of the message shall be executed. If an IE/IE group is included in a received message and the presence of the IE/IE group is conditional and the condition is false according to the version of the specification used by the receiver. the receiving node shall reject the procedure using the Error Indication procedure.0 (2008-03) 1. an abstract syntax error occurs due to a missing IE/IE group.3. 10.2 IEs other than the Procedure Code and Type of Message The receiving node shall treat the different types of received criticality information of an IE/IE group other than the Procedure Code IE and Type of Message IE according to the following: Reject IE: If a message initiating a procedure is received containing one or more IEs/IE group marked with "Reject IE" which the receiving node does not comprehend.

Release 8

146

3GPP TS 36.413 V8.1.0 (2008-03)

-

If a response message is received containing one or more IEs marked with "Reject IE", that the receiving node does not comprehend, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.

Ignore IE and Notify Sender: If a message initiating a procedure is received containing one or more IEs/IE groups marked with "Ignore IE and Notify Sender" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and report in the response message of the procedure that one or more IEs/IE groups have been ignored. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. if a message initiating a procedure that does not have a message to report the outcome of the procedure is received containing one or more IEs/IE groups marked with "Ignore IE and Notify Sender" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and initiate the Error Indication procedure to report that one or more IEs/IE groups have been ignored. If a response message is received containing one or more IEs/IE groups marked with "Ignore IE and Notify Sender" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and initiate the Error Indication procedure.

-

-

Ignore IE: If a message initiating a procedure is received containing one or more IEs/IE groups marked with "Ignore IE" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups. If a response message is received containing one or more IEs/IE groups marked with "Ignore IE" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups.

-

When reporting not comprehended IEs/IE groups marked with "Reject IE" or "Ignore IE and Notify Sender" using a response message defined for the procedure, the Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported IE/IE group. When reporting not comprehended IEs/IE groups marked with "Reject IE" or "Ignore IE and Notify Sender" using the Error Indication procedure, the Procedure Code IE, the Triggering Message IE, Procedure Criticality IE, and the Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported IE/IE group.

10.3.5

Missing IE or IE group

The receiving node shall treat the missing IE/IE group according to the criticality information for the missing IE/IE group in the received message specified in the version of this specification used by the receiver: Reject IE: if a received message initiating a procedure is missing one or more IEs/IE groups with specified criticality "Reject IE"; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the missing IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.

3GPP

Release 8

147

3GPP TS 36.413 V8.1.0 (2008-03)

-

if a received message initiating a procedure that does not have a message to report unsuccessful outcome is missing one or more IEs/IE groups with specified criticality "Reject IE", the receiving node shall terminate the procedure and initiate the Error Indication procedure. if a received response message is missing one or more IEs/IE groups with specified criticality "Reject IE, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.

-

Ignore IE and Notify Sender: if a received message initiating a procedure is missing one or more IEs/IE groups with specified criticality "Ignore IE and Notify Sender”, the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and report in the response message of the procedure that one or more IEs/IE groups were missing. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. if a received message initiating a procedure that does not have a message to report the outcome of the procedure is missing one or more IEs/IE groups with specified criticality "Ignore IE and Notify Sender”, the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. if a received response message is missing one or more IEs/IE groups with specified criticality "Ignore IE and Notify Sender", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing.

-

-

Ignore IE: if a received message initiating a procedure is missing one or more IEs/IE groups with specified criticality “Ignore IE”, the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message. if a received response message is missing one or more IEs/IE groups with specified criticality “Ignore IE”, the receiving node shall ignore that those IEs/IE groups are missing and continue with the procedure based on the other IEs/IE groups present in the message.

-

When reporting missing IEs/IE groups with specified criticality “Reject IE” or “Ignore IE and Notify Sender” using a response message defined for the procedure, the Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported IE/IE group. When reporting missing IEs/IE groups with specified criticality “Reject IE” or “Ignore IE and Notify Sender” using the Error Indication procedure, the Procedure Code IE, the Triggering Message IE, Procedure Criticality IE, and the Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported IE/IE group.

10.3.6

IEs or IE groups received in wrong order or with too many occurrences or erroneously present

If a message with IEs or IE groups in wrong order or with too many occurrences is received or if IEs or IE groups with a conditional presence are present when the condition is not met (i.e. erroneously present), the receiving node shall behave according to the following: If a message initiating a procedure is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the cause value "Abstract Syntax Error (Falsely Constructed Message)" using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. If a message initiating a procedure that does not have a message to report unsuccessful outcome is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving

-

3GPP

Release 8

148

3GPP TS 36.413 V8.1.0 (2008-03)

node shall terminate the procedure and initiate the Error Indication procedure, and use cause value "Abstract Syntax Error (Falsely Constructed Message)". If a response message is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.

When determining the correct order only the IEs specified in the specification version used by the receiver shall be considered.

10.4 Logical Error
Logical error situations occur when a message is comprehended correctly, but the information contained within the message is not valid (i.e. semantic error), or describes a procedure which is not compatible with the state of the receiver. In these conditions, the following behaviour shall be performed (unless otherwise specified) as defined by the class of the elementary procedure, irrespective of the criticality information of the IEs/IE groups containing the erroneous values. Class 1: Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are: Semantic Error. Message not compatible with receiver state.

Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The Procedure Code IE and the Triggering Message IE within the Criticality Diagnostics IE shall then be included in order to identify the message containing the logical error. Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. Class 2: Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The Procedure Code IE and the Triggering Message IE within the Criticality Diagnostics IE shall then be included in order to identify the message containing the logical error.

10.5 Exceptions
The error handling for all the cases described hereafter shall take precedence over any other error handling described in the other subclauses of clause 10. If any type of error (Transfer Syntax Error, Abstract Syntax Error or Logical Error) is detected in the ERROR INDICATION message, it shall not trigger the Error Indication procedure in the receiving Node but local error handling. In case a response message or Error Indication message needs to be returned, but the information necessary to determine the receiver of that message is missing, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. If an error that terminates a procedure occurs, the returned cause value shall reflect the error that caused the termination of the procedure even if one or more abstract syntax errors with criticality “ignore and notify” have earlier occurred within the same procedure.

-

-

3GPP

both nodes shall initiate a local release of any established UE-associated logical connection having the erroneous AP ID as local or remote identifier. The peer node shall initiate a local release of any established UE-associated logical connection having the AP ID as identifier. the node shall initiate an Error Indication procedure with inclusion of only the previously received AP ID from the peer node and an appropriate cause value. If a subsequent message followed by the first message is to be sent before receiving a first returned message from the peer node.6 Note: Handling of AP ID The “first message” and the “first returned message” as shown below correspond to the message for a UE-associated logical connection. If a node receives a message other than the first message that include an AP ID which is unknown to the node.g. If a node detects a first message that includes an AP ID which is erroneous e. If a node receives an unrecognized message the node shall initiate an Error Indication procedure with inclusion of only the previously received AP ID from the peer node and an appropriate cause value.Release 8 149 3GPP TS 36. the receiving node shall return an ERROR INDICATION message with inclusion of only the previously received AP ID from the peer node and an appropriate cause value. an AP ID for the same peer node which have been stored previously for another UE-associated logical connection. Thereafter the two APIDs are included in all messages over the UE-associated logical connection. The node which receives such a subsequent message shall not initiate an Error Indication procedure. The “first message” has a new AP ID from the sending node and the “first returned message” is the first response message. which have a new APID from the node sending the “first returned message”.1.413 V8. In this case.0 (2008-03) 10. the subsequent message shall include the previously sent AP ID. Editor’s Note: How to retrieve the APID of the peer node from the unrecognized message is FFS 3GPP . If such subsequent message is the last message for this UEassociated logical connection. the node which receives such a subsequent message initiates a local release of any established UE-associated logical connection having the received AP ID as remote node identifier.

0.1.0.0.0.0 1.0 2.1.0 ASN.2.413 V8. R3-072420.0.1.0 0. V120 then served as a base for RAN3#58 Updates according to agreements in R3-072320 and R3. The content is related to tabular message representation with tabular representation of Information Elements and ASN. R3072435.3.0 2007-10 2007-11 2007-11 2007-12 2008-03 3GPP .2.1 framework and error handling. R3-072348.0. R3-072423. R3-072032.0 072355 achieved in RAN3#58 and according to post RAN3#58 email check: R3-072417.0 8.0 0.1 0.0 0.1 0.0 0.0 1. eNB UE S1AP ID within all messages Updates according to agreements on the RAN3 email 1.0 8. R3-072437. R3-072422.0. Skeleton inclusion of post-RAN3#55bis-email agreed text proposals inclusion of post-RAN3#56-email agreed text-proposals Updates according to discussions in RAN3#57 Presentation to TSG-RAN for information -version 1. R3-072034 and R3-072035.0 (2008-03) Annex A (informative): Change history Change history Date TSG # TSG Doc.1. R3072436.0 2.0 1.0.0. CR Rev Subject/Comment Old New 2007-01 2007-05 2007-06 2007-08 2007-09 2007-10 37 Scope.0 8.Release 8 150 3GPP TS 36.1.0 1.1.1 code.0 Updates according to agreements in RAN3#57bis for 1.0 0.2.3.413 1. 38 38 39 RP-080080 58 RP-070851 Presentation to TSG-RAN for approval specification approved at TSG-RAN and placed under change control RAN3 agreed changes for TS 36.0.0.2.0 reflector following the “complementing” exercise. R3-072422.0 0. MME UE S1AP ID.1. The incorporated documents are R3-072031. R3072033.

Sign up to vote on this title
UsefulNot useful