cs8 test sets - spirent...the information contained in this document is subject to change without...

CS8 Test Sets Reference Manual

Spirent 541 Industrial Way West Eatontown, NJ07724USA

Email: [email protected] Web:http://www.spirent.com

AMERICAS1-800-SPIRENT •+1-818-676-2683 •[email protected] EUROPE AND THE MIDDLE EAST+44 (0) 1293 767979 •[email protected] ASIA AND THE PACIFIC +86-10-8518-2539 •[email protected]

This manual applies to CS8 Version 1.00 or higher.

Page Part Number: 71-006770, Version A0

Copyright© 2012 Spirent. All Rights Reserved.

All of the company names and/or brand names and/or product names referred to in this document, in particular, the name “Spirent” and its logo device, are either registered trademarks or trademarks of Spirent plc and its subsidiaries, pending registration in accordance with relevant national laws. All other registered trademarks or trademarks are the property of their respective owners.

The information contained in this document is subject to change without notice and does not represent a commitment on the part of Spirent. The information in this document is believed to be accurate and reliable; however, Spirent assumes no responsibility or liability for any errors or inaccuracies that may appear in the document.

Table of Contents

1. Introduction .......................................................................................... 1

1.1. Overview ...................................................................................... 1

1.2. Acronyms ..................................................................................... 1

1.3. References .................................................................................... 1

2. CS8-TS-LTE-NAS .................................................................................... 4

2.1. Attach in EPS: Test 1101 ............................................................... 4

2.1.1. Test Purpose ...................................................................................... 4

2.1.2. Conformance Requirement ................................................................. 4

2.1.3. Test Description ................................................................................. 4

2.1.4. Specific Message Content ................................................................... 6

2.2. Attach in EPS:Test 1102 ................................................................ 6

2.2.1. Test Purpose ...................................................................................... 7

2.2.2. Conformance Requirement ................................................................. 7

2.2.3. Test Description ................................................................................. 7

2.3. Attach in EPS:Test 1115 ................................................................ 9

2.3.1. Test Purpose ...................................................................................... 9

2.3.2. Conformance Requirement ............................................................... 10

2.3.3. Test Description ............................................................................... 10

2.4. Attach in EPS:Test 1116 .............................................................. 12

2.4.1. Test Purpose ..................................................................................... 13

2.4.2. Conformance Requirement ................................................................ 13

2.4.3. Test Description ................................................................................ 13


2.5.1. Test Purpose .................................................................................... 16



2.6. Attach in EPS: Test 1119 ............................................................. 21

2.6.1. Test Purpose .................................................................................... 21



ii | CS8 Test Sets: Reference Manual


2.7.1. Test Purpose .................................................................................... 23


2.7.3. TestDescription ................................................................................ 23


2.8.1. Test Purpose .................................................................................... 28




2.9.1. Test Purpose .................................................................................... 30




2.10.1. Test Purpose .................................................................................... 33




2.11.1. Test Purpose .................................................................................... 35




2.12.1. Test Purpose .................................................................................... 38



2.13. Attach Failurein EPS: Test 1201 ................................................... 40

2.13.1. Test Purpose .................................................................................... 40



2.14. Attach Failurein EPS:Test 1204 .................................................... 43

2.14.1. Test Purpose .................................................................................... 43




2.15.1. Test Purpose .................................................................................... 44

Table of Contents | iii




2.16.1. Test Purpose .................................................................................... 46



2.17. Combined Attach: Test 1304 ....................................................... 48

2.17.1. Test Purpose .................................................................................... 48



2.18. Combined Attach:Test 1305 ........................................................ 51

2.18.1. Test Purpose ..................................................................................... 51



2.19. Detach: Test 1406 ....................................................................... 52

2.19.1. Test Purpose .................................................................................... 52



2.20. Detach: Test 1407 ....................................................................... 56

2.20.1. Test Purpose .................................................................................... 56

2.20.2. Conformance Requirement ............................................................ 56

2.20.3. Test Description ............................................................................ 56

2.21. Detach: Test 1408 ....................................................................... 58

2.21.1. Test Purpose .................................................................................... 58



2.22. Authentication: Test 1505 ........................................................... 60

2.22.1. Test Purpose .................................................................................... 60



2.23. Service Request: Test 1704 ......................................................... 61

2.23.1. Test Purpose .................................................................................... 61



iv | CS8 Test Sets: Reference Manual

2.24. Service Request:Test 1705 .......................................................... 63

2.24.1. Test Purpose .................................................................................... 63



2.25. Service Request: Test 1706 ......................................................... 65

2.25.1. Test Purpose .................................................................................... 65



3. CS8-TS-LTE-WCDMA-RRM .................................................................... 68

3.1. LTE to UMTS Reselection: Test 2101 ............................................. 68

3.1.1. Test Purpose .................................................................................... 68



3.2. LTE to UMTS Reselection: Test 2103 ............................................. 72

3.2.1. Test Purpose .................................................................................... 72



3.3. LTE to UMTS Redirection: Test 2201 ............................................. 75

3.3.1. Test Purpose .....................................................................................75

3.3.2. Conformance Requirement ................................................................75

3.3.3. TestDescription .................................................................................75


3.4.1. Test Purpose .................................................................................... 78




3.5.1. Test Purpose .................................................................................... 81



3.6. UMTS to LTE Reselection: Test 2403 ............................................. 84

3.6.1. Test Purpose .................................................................................... 84



3.7. UMTS to LTE Redirection: Test 2501 ............................................. 87

Table of Contents | v

3.7.1. Test Purpose .................................................................................... 87




3.8.1. Test Purpose .................................................................................... 89




3.9.1. Test Purpose .................................................................................... 91



3.10. Stress Testing – LTE-UMTS: Test 2703 ......................................... 93

3.10.1. Test Purpose .................................................................................... 93



3.11. Stress Testing – LTE-UMTS: Test 2704 ......................................... 95

3.11.1. Test Purpose .................................................................................... 95



3.12. LTE to UMTS Cell Reselection: Test 2705 ...................................... 97

3.12.1. Test Purpose .................................................................................... 97



3.13. UE Reselection from LTE to UMTS Cell: Test 2707........................ 100

3.13.1. Test Purpose .................................................................................. 100

3.13.2. Conformance Requirement ............................................................. 100

3.13.3. Test Description ............................................................................. 100

3.14. LTE to UMTS(R99) Redirection with Fading and Noise: Test 2709 . 102

3.14.1. Test Purpose .................................................................................. 102



3.15. LTE to HSPA/HSUPA Redirection: Test 2711 ............................... 105

3.15.1. Test Purpose ................................................................................... 105

3.15.2. Conformance Requirement .............................................................. 105

3.15.3. TestDescription .............................................................................. 106

vi | CS8 Test Sets: Reference Manual

3.16. Redirection LTE to UMTS: Test 2730 ........................................... 108

3.16.1. Test Purpose .................................................................................. 108



3.17. Reselection from LTE to UMTS: Test 2731 ................................... 112

3.17.1. Test Purpose ................................................................................... 112


3.17.3. Test Description .............................................................................. 112

3.18. UE Redirection from UMTS: Test 2732 ........................................ 116

3.18.1. Test Purpose ................................................................................... 116



3.19. UE Reselects from UMTS to LTE: Test 2733 ................................. 119

3.19.1. Test Purpose ................................................................................... 119



4. CS8-LTE to UMTS-ENH-TS .................................................................. 124

4.1. LTE to UMTS: Test 2302 ............................................................. 124

4.1.1. Test Purpose ...................................................................................124

4.1.2. Conformance Requirement ..............................................................124

4.1.3. Test Description ..............................................................................124

4.2. LTE to UMTS: Test 2304 ............................................................. 128

4.2.1. Test Purpose .................................................................................. 128



4.3. LTE to UMTS: Test 2301 ............................................................. 131

4.3.1. Test Purpose ................................................................................... 132



4.4. LTE to UMTS Test: 2308 ............................................................. 135

4.4.1. Test Purpose ................................................................................... 135



4.5. LTE to UMTS Active Handover with Fading: Test 2713.................. 138

Table of Contents | vii

4.5.1. Test Purpose .................................................................................. 138



4.6. LTE to UMTS Active Handover with Fading: Test 2716.................. 141

4.6.1. Test Purpose ................................................................................... 141



4.7. LTE to HSPA+ Redirection with Measurement Gap: Test 2206 ...... 143

4.7.1. Test Purpose ................................................................................... 143



4.8. LTE to HSPA+ Redirection with Measurement Gap: Test 2738 ...... 147

4.8.1. Test Purpose ................................................................................... 147



4.9. LTE to HSPA+ Handover with Measurement Gap: Test 2310 ........ 150

4.9.1. Test Purpose ................................................................................... 150



4.10. LTE to HSPA+ Handover with Measurement Gap: Test 2740 ........ 154

4.10.1. Test Purpose ................................................................................... 154



4.11. LTE to HSPA+: Test 2205 ........................................................... 157

4.11.1. Test Purpose ................................................................................... 157



4.12. LTE to HSPA+ Handover without Measurement Gap: Test 2305 ... 160

4.12.1. Test Purpose .................................................................................. 160



4.13. LTE to HSPA+ Reselection: Test 2104 ......................................... 163

4.13.1. Test Purpose .................................................................................. 163



viii | CS8 Test Sets: Reference Manual

5. CS8-TS-LTE-IDLE ................................................................................ 167

5.1. Cell Selection Intra E-UTRAN: Test 3601 ..................................... 167

5.1.1. Test Purpose ................................................................................... 167




5.2.1. Test Purpose .................................................................................. 169




5.3.1. Test Purpose ................................................................................... 172



5.4. Cell Reselection: Test 3612 ....................................................... 175

5.4.1. Test Purpose ................................................................................... 175



6. CS8-TS-LTE-VOLTE-GSMA .................................................................. 178

6.1. SIP Registration Procedure: Test 4101 ....................................... 178

6.1.1. Test Purpose ................................................................................... 178



6.2. SIP Registration Procedure: Test 4102 ....................................... 180

6.2.1. Test Purpose .................................................................................. 180



6.3. Authentication/Security: Test 4201 ........................................... 182

6.3.1. Test Purpose .................................................................................. 182




6.4.1. Test Purpose .................................................................................. 184



Table of Contents | ix


6.5.1. Test Purpose .................................................................................. 186



6.6. Call Establishment and Termination: Test 4301 .......................... 188

6.6.1. Test Purpose .................................................................................. 188



6.7. Call Establishment and Termination: Test 4302 .......................... 193

6.7.1. Test Purpose ................................................................................... 193



7. CS8-TS-LTE-VOLTE-IMTC .................................................................... 197

7.1. Voice Call: Test 4601 ................................................................. 197

7.1.1. Test Purpose ................................................................................... 197



7.2. Voice Call: Test 4602 ................................................................. 203

7.2.1. Test Purpose .................................................................................. 203



7.2.4. Test Procedure Sequence ............................................................... 203

7.3. Voice Call: Test 4603 ................................................................. 210

7.3.1. Test Purpose .................................................................................. 210



7.4. Voice Call: Test 4604 ................................................................. 216

7.4.1. Test Purpose .................................................................................. 216



8. Appendix A ........................................................................................ 224

8.1. Generic Test Procedure ............................................................. 224

8.1.1. UE Registration Procedure .............................................................. 224

8.1.2. UE Registration with Test Mode Activation ...................................... 227

x | CS8 Test Sets: Reference Manual

8.1.3. Generic Radio Bearer Establishment ............................................... 228

8.1.4. Tracking Area Update ...................................................................... 231

9. Appendix B ........................................................................................ 232

9.1. RRC and NAS Messages with Default Parameters ........................ 232

9.1.1. RRCConnectionRequest .................................................................. 232

9.1.2. RRCConnectionSetup ...................................................................... 232

9.1.3. RRCConnectionSetupComplete ....................................................... 233

9.1.4. RRCConnectionReconfiguration ...................................................... 233

10. Appendix C (Pre-Conditions) ............................................... 250

10.1. Network Configurations ............................................................. 250

10.1.1. Operating Bands ............................................................................ 250

10.1.2. Mapping of E-UTRA Bands to Bandwidth .......................................... 251

10.1.3. PLMN Association with MCC and MNC ............................................. 252

10.1.4. PLMN Mapping to Cell .................................................................... 252

10.1.5. General Network Configuration ....................................................... 253

10.1.6. General Cell Configuration .............................................................. 253

10.1.7. Radio Link Parameters .................................................................... 254

10.1.8. UE Categories ................................................................................. 254

10.1.9. UE Categories UL Parameter Support .............................................. 254

10.1.10. Default NAS Parameters for Simulated Cells ................................ 255

10.1.11. Network Configuration for Simulated NAS Cell ............................ 256

10.1.12. Reference Dedicated EPS Bearer Contexts .................................... 257

10.1.13. UTRAN Cell Configuration ........................................................... 259

10.1.14. UTRAN Test Frequency ................................................................ 260

10.1.15. Suitable/Non-Suitable EUTRAN Cell Parameters .......................... 260

10.1.16. Suitable/Non-Suitable UTRAN Cell Parameters ........................... 260

10.1.17. UTRA Reference Radio Parameters and Combinations ................. 260

10.1.18. MIB ............................................................................................ 261

10.1.19. SystemInformationBlockType1 ................................................... 262

10.1.20. SystemInformationBlockType2 ................................................... 264

10.1.21. RadioResourceConfigCommon-DEFAULT ..................................... 265

10.1.22. BCCH-Config-DEFAULT ............................................................... 266

10.1.23. CQI-ReportConfig-DEFAULT ........................................................ 266

10.1.24. DRB-ToAddModList-RECONFIG ................................................... 267

Table of Contents | xi

10.1.25. PCCH-Config-DEFAULT ................................................................ 267

10.1.26. PHICH-Config-DEFAULT .............................................................. 268

10.1.27. PDSCH-ConfigCommon-DEFAULT ................................................ 268

10.1.28. PDSCH-ConfigDedicated-DEFAULT .............................................. 269

10.1.29. PRACH-Config-DEFAULT ............................................................. 269

10.1.30. PUCCH-ConfigCommon-DEFAULT................................................. 271

10.1.31. PUCCH-ConfigDedicated-DEFAULT ............................................... 271

10.1.32. PUSCH-ConfigCommon-DEFAULT ................................................ 272

10.1.33. PUSCH-ConfigDedicated-DEFAULT .............................................. 272

10.1.34. RACH-ConfigCommon-DEFAULT .................................................. 273

10.1.35. SoundingRS-UL-ConfigCommon-DEFAULT .................................. 274

10.1.36. Combinations of System Information Blocks ................................ 275

11. Appendix D ......................................................................... 279

11.1. Contents of EMM Messages ....................................................... 279

11.1.1. ATTACH ACCEPT .............................................................................. 279

11.1.2. -ATTACH COMPLETE ........................................................................ 282

11.1.3. ATTACH REJECT ............................................................................... 282

11.1.4. ATTACH REQUEST ........................................................................... 283

11.1.5. AUTHENTICATION FAILURE .............................................................. 284

11.1.6. AUTHENTICATION REJECT ................................................................ 285

11.1.7. AUTHENTICATION REQUEST ............................................................. 285

11.1.8. AUTHENTICATION RESPONSE .......................................................... 286

11.1.9. CS SERVICE NOTIfICATION ............................................................... 286

11.1.10. DETACH ACCEPT(UE originating detach) ...................................... 287

11.1.11. DETACH ACCEPT(UE terminated detach) .......................................... 287

11.1.12. DETACH REQUEST(UE Originating Detach) ................................... 288

11.1.13. DETACH REQUEST(UE terminated detach) .................................... 288

11.1.14. DOWNLINK NAS TRANSPORT ....................................................... 289

11.1.15. EMM INFORMATION .................................................................... 289

11.1.16. EMM STATUS .............................................................................. 291

11.1.17. EXTENDED SERVICE REQUEST ...................................................... 291

11.1.18. GUTI REALLOCATION COMMAND ................................................. 292

11.1.19. GUTI REALLOCATION COMPLETE .................................................. 292

11.1.20. IDENTITY REQUEST ..................................................................... 293

11.1.21. IDENTITY RESPONSE ................................................................... 293

xii | CS8 Test Sets: Reference Manual

11.1.22. SECURITY MODE COMMAND ....................................................... 294

11.1.23. SECURITY MODE COMPLETE ........................................................ 295

11.1.24. SECURITY MODE REJECT .............................................................. 295

11.1.25. SERVICE REJECT .......................................................................... 296

11.1.26. SERVICE REQUEST ...................................................................... 296

11.1.27. TRACKING AREA UPDATE ACCEPT ................................................. 297

11.1.28. TRACKING AREA UPDATE COMPLETE ............................................ 300

11.1.29. TRACKING AREA UPDATE REJECT .................................................. 301

11.1.30. TRACKING AREA UPDATE REQUEST .............................................. 301

11.1.31. UPLINK NAS TRANSPORT ............................................................. 303

12. Appendix E .......................................................................... 304

12.1. Contents of ESM Messages ....................................................... 304

12.1.1. ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT ........................ 304

12.1.2. ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT ......................... 304

12.1.3. ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST ..................... 305

12.1.4. ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT ............................ 307

12.1.5. ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT ............................. 307

12.1.6. ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST ......................... 308

12.1.7. BEARER RESOURCE ALLOCATION REJECT ........................................... 311

12.1.8. BEARER RESOURCE ALLOCATION REQUEST ....................................... 312

12.1.9. BEARER RESOURCE MODIFICATION REJECT ........................................ 313

12.1.10. BEARER RESOURCE MODIFICATION REQUEST ................................ 314

12.1.11. DEACTIVATE EPS BEARER CONTEXT ACCEPT ................................... 315

12.1.12. DEACTIVATE EPS BEARER CONTEXT REQUEST ............................... 316

12.1.13. ESM INFORMATION REQUEST ....................................................... 317

12.1.14. ESM INFORMATION RESPONSE .................................................... 317

12.1.15. ESM STATUS ............................................................................... 318

12.1.16. MODIFY EPS BEARER CONTEXT ACCEPT ........................................ 318

12.1.17. MODIFY EPS BEARER CONTEXT REJECT .......................................... 319

12.1.18. MODIFY EPS BEARER CONTEXT REQUEST ...................................... 319

12.1.19. PDN CONNECTIVITY REJECT .......................................................... 321

12.1.20. PDN CONNECTIVITY REQUEST ...................................................... 321

12.1.21. PDN DISCONNECT REJECT ............................................................ 323

12.1.22. PDN DISCONNECT REQUEST ....................................................... 323

13. Appendix F .......................................................................... 325

Table of Contents | xiii

13.1. General Parameters for Cell Configuration .................................. 325

14. Appendix G ......................................................................... 326

14.1. Default Messages for IMS Registration ....................................... 326

14.2. Default Messages for Call Setup ................................................ 340

1. Introduction

1.1. Overview

This document provides detailed information about the parameters and functions of CS8 Test Cases based on the 36.523-1 Specifications.

1.2. Acronyms

Acronym Explanation

FT Functional Testing

1.3. References

[1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”.

[2] 3GPP TS 23.003: “Numbering, Addressing and Identification”.

[3] 3GPP TS 23.122: “Non-Access-Stratum functions related to Mobile Station (MS) in idle mode”.

[4] 3GPP TS 24.008: “Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage3”.

[5] 3GPP TS 34.108: “Common Test Environments for User Equipment (UE) Conformance Testing”.

[6] 3GPP TS 34.109: “Terminal logical test interface; Special conformance testing functions”.

[7] 3GPP TS 34.123-1: “User Equipment (UE) conformance specification; Part 1: Protocol conformance specification”.

[8] 3GPP TS 34.123-2: “User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) performance specification”.

[9] 3GPP TS 34.123-3: “User Equipment (UE) conformance specification; Part 3: Abstract Test Suites (ATS)”.

[10] 3GPP TS 36.300: “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2”.

[11]3GPP TS 36.302: “Services provided by the physical layer for E-UTRA”.

2 | CS8 Test Sets: Reference Manual

[12]3GPP TS 36.304: “Evolved Universal Terrestrial Radio Access (E-UTRA) User Equipment (UE) Procedures in idle mode “.

[13]3GPP TS 36.306: “Evolved Universal Terrestrial Radio Access (E-UTRA) User Equipment (UE) Radio Access capabilities “.

[14]3GPP TS 36.321: “Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access Control (MAC) protocol specification”.

[15]3GPP TS 36.322: “Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Link Control (RLC) protocol specification”.

[16]3GPP TS 36.323: “Evolved Universal Terrestrial Radio Access (E-UTRA) Packet Data Convergence Protocol (PDCP) specification”.

[17]3GPP TS 36.331: “Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC) Protocol Specification”.

[18]3GPP TS 36.508: “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); Common Test Environments for User Equipment (UE) Conformance Testing”.

[19]3GPP TS 36.523-2: “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) preform a specification”.

[20]3GPP TS 36.523-3: “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); User Equipment (UE) conformance specification; Part 3: Abstract Test Suites (ATS)”.

[21]3GPP TR 24.801: “3GPP System Architecture Evolution; CT WG1 Aspects”.

[22]3GPP TS 23.401: “3GPP System Architecture Evolution; GPRS enhancements for E-UTRAN access”.

[23]3GPP TS 51.010-1: “Mobile Station (MS) conformance specification; Part 1: Conformance specification”.

[24]ISO/IEC 9646 (all parts): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework”.

[25] 3GPP TS 36.509: “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Special conformance testing functions for User Equipment (UE)”.

[26]3GPP TS 33.102: “3G Security; Security architecture”.

[27]3GPP TS 33.401: “3GPP System Architecture Evolution (SAE); Security architecture”.

[28]3GPP TS 24.301: “Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3”.

Chapter One: Introduction | 3

[29]3GPP TS 36.212: “Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding”.

[30]3GPP TS 36.213: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures”.

[31]3GPP TS 36.101: “Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception”.

[32]3GPP TS 24.008: “Mobile radio interface layer 3 specification; Core network protocols; Stage 3”.

[33]3GPP2 A.S0008-C: “Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Access Network”.

[34]3GPP TS 36.133: “Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management”.

[35]3GPP TS 34.229-1: “Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 1: Protocol conformance specification “.

2. CS8-TS-LTE-NAS

2.1. Attach in EPS: Test 1101

UE performs attach in EPS with IPv4 allocation (capable of IPv6 and IPv4).

2.1.1. Test Purpose

(1)

with { UE is configured to request the DSMIPv6 IPv4 Home Agent Address during Attach procedure }

ensure that {

when { UE is switched on and has established the RRC connection }

then { UE transmits an ATTACH REQUEST and a PDN CONNECTIVITY REQUEST message indicating a request for DSM IPv4 Home Agent Address in the protocol configuration options and MME responds to the ATTACH REQUEST with a DSM IPv4 Home Agent Address and UE transmits an ATTACH COMPLETE message }

}

2.1.2. Conformance Requirement

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 5.5.1.1.

2.1.3. Test Description

2.1.3.1 Setup Configuration

Cell 1:

• Refer to Table 6-10

UE:

• The UE is previously registered on E-UTRAN, and when on E-UTRAN, the UE is last authenticated and registered on Cell 1.

• The UE is configured to request the DSM IPv4 Home Agent Address in the protocol configuration options IE as part of the Attach/PDN connectivity request procedure.

HSS:

• Configuring subscription data in HSS to support only one PDN type i.e. IPv4

Chapter Two: CS8-LTE-NAS-TS | 5

Preamble:

• The UE is in state Switched OFF.

2.1.3.2 Test Procedure Sequence

Table 2-1: Main Behavior

St Procedure Message Sequence TP Verification

UE-eNB

eNB-MME

Message

1 The UE is switched on. - - - -

2 Check: Does the UE transmit an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message with IE PROTOCOL CONFIGURATION OPTIONS indicating a DSM IPv4 Home Agent Address Request?

--> --> ATTACH REQUEST

1

3-11

Steps 5 to 13 of the generic test procedure in Appendix Table 4-1 (Attach procedure) are performed on Cell 1.

- - - -

12 MME responds with ATTACH ACCEPT message including a valid TAI list. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT message, including the IE PROTOCOL CONFIGURATION OPTIONS indicating a DSMIPv4 Home Agent Address

<-- <-- ATTACH ACCEPT

- -

- EXCEPTION: If the “PDN type” in the latest PDN

CONNECTIVITY REQUEST message prior to

this procedure was 'IPv4' or 'IPv4v6' then,

IPv4 address allocation by DHCPv4 may

occur on the user plane bearer established for

the default EPS bearer context activated with

the latest ACTIVATE DEFAULT EPS

BEARER CONTEXT message prior to this

procedure.

- - - -

13 Check: Does the UE transmit an ATTACH COMPLETE message including an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message?

--> --> ATTACH COMPLETE

1


2.1.4. Specific Message Content

Table 2-2: Message ATTACH REQUEST

Information Element Value/Remark Comment Condition

ESM message container PDN CONNECTIVITY REQUEST message

Table 2-3: PDN CONNECTIVITY REQUEST


Protocol configuration options The IE Protocol configuration options contains a configuration protocol option = ‘0009H’ (“DSMI IPv4 Home Agent Address Request”, length of contents = 0).



ESM message container Contains the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message

Table 5.1.1-5Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST


Protocol configuration options The IE Protocol configuration options contains a configuration protocol option = ‘0009H’ (“DSM IPv4 Home Agent Address”, non-zero length), with the value set to the IPv4 address of the Home Agent.

2.2. Attach in EPS:Test 1102

UE performs attach in EPS with IPv6 allocation (capable of IPv6 and IPv4).


2.2.1. Test Purpose

(1)

with { UE is configured to request the IPv6 address of the Home Agent during Attach procedure }

ensure that {

when { UE is switched on and has established the RRC connection }

then { UE transmits an ATTACH REQUEST message and a PDN CONNECTIVITY REQUEST message indicating a request for DSMIPv6 Home Agent Address in the protocol configuration options and MME responds to the ATTACH REQUEST with a IPv6 Home Agent Address and UE transmits an ATTACH COMPLETE message

}

}


References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 5.5.1.1



Cell 1:

Refer to Table 6-10

UE:


• The UE is configured to request the DSMIPv6 IPv4 Home Agent Address in the protocol configuration options IE as part of the Attach/PDN connectivity request procedure.

HSS:

• Configuring subscription data in HSS to support only one PDN type i.e. IPv6

Preamble:

• UE is in state Switched OFF.





UE-eNB

eNB-MME

Message


2 Check: Does the UE transmit an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message with IE PROTOCOL CONFIGURATION OPTIONS indicating a DSMIPv6 Home Agent Address Request?


1

3-11

Steps5 to13 of the generic test procedure in the Appendix Table 4-1 (Attach procedure) are performed on Cell1.

- - - -

12 MME responds with ATTACH ACCEPT message including a valid TAI list. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT message, including the IE PROTOCOL CONFIGURATION OPTIONS indicating a DSMIPv6 Home Agent Address.


- -

- - - - -



1

2.2.3.3 Specific Message Content






Protocol configuration options The IE Protocol configuration options contains a configuration protocol option = ‘0007H’ (“DSMIPv6 Home Agent Address Request”,



length of contents = 0).

Table 2-8: Message ATTACH ACCEPT


ESM message container Contains the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

Table 2-9: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST


Protocol configuration options The IE Protocol configuration options contains a configuration protocol option = ‘0007H’ (“DSMIPv6 Home Agent Address”, non-zero length), with the value set to the IPv6 address of the Home Agent.


UE attaches to network with 1 PDN, 1 default bearer, 1 dedicated bearer being activated after a delay; Verify EPS bearers status and PDN details

2.3.1. Test Purpose

(1)

with { UE in state EMM-DEREGISTERED and is switched off }

ensure that {

when { UE is powered up and sends ATTACH REQUEST and a PDN CONNECTIVITY REQUEST message }

then { UE successfully Attached to network with default bearer established}

}

}

(2)

with { UE successfully Attached to network }

ensure that {

when { UE receives Activate Dedicated EPS Bearer Context Request message in RRC Connection Reconfiguration


}

then { UE sends an RRC Connection Reconfiguration Complete and Activate Dedicated EPS Bearer Context Accept }

}


References: The conformance requirements covered in the present TC are specified in3GPP TS 24.301 clause 5.5.1.1 and 5.5.1.2



Cell 1:

• Refer to Table 6-10 for cell configuration.

UE:


Preamble:





UE-eNB

eNB-MME

Message


2 Check: Does the UE transmit an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message?

--> --> ATTACH REQUEST -

3-11


- - - -

12 Network responds with ATTACH ACCEPT message including a valid TAI list. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT message.

<-- <-- ATTACH ACCEPT - -





1 -

14 The Network transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

NOTE: The Network implicitly reuses the PDN address defined in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.

<-- ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

- -

15 Check: Does the UE transmit an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message as specified?

--> ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

2 -


Table 2-11: RRCConnectionReconfiguration

Information Element

Value/Remark Comment Condition Information Element

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

dedicatedInfoNASList SEQUENCE (SIZE(1..maxDRB)) OF

1 entry

dedicatedInfoNAS[1]

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST with EPS Bearer Identity corresponding to drb-Identity 2

}


Refer Table 5-4 for default RRCConnectionReconfiguration parameters.

Table 2-12: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST


EPS Bearer Identity 6

Procedure Transaction Identity 0 “No procedure transaction identity assigned”

Linked EPS Bearer Identity 5 Network re-uses the EPS Bearer Identity of the default EPS bearer context.

EPS QoS According to reference dedicated EPS bearer context #1 –refer to Table 6-11

TFT According to reference dedicated EPS bearer context #1- refer to Table 6-11

Table 2-13: Message ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT


EPS Bearer Identity 6 Same value as in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST



UE attaches to network with 2 PDNs, 1 default bearer on each PDN; different QCI on each PDN; Verify IMS PDN registration and IMS messages


2.4.1. Test Purpose

(1)

with { UE in EMM-DEREGISTERED state and UE sends ATTACH REQUEST and PDN CONNECTIVITY REQUEST message }

ensure that {

when { Network responds to the ATTACH REQUEST }

then { UE transmits an ATTACH COMPLETE message with ACTIVATE DEFAULT

EPS BEARER CONTEXT ACCEPT message}

}

(2)

with { UE has sent a PDN CONNECTIVITY REQUEST message }

ensure that {

when { UE receives an RRCConnectionReconfiguration message including an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message }

then { UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and SIP messages are send and received by UE }

}


References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 5.5.1.1, 5.5.1.2, 6.4.1.3, 6.5.1.2.



Cell 1:


UE:


Preamble:






UE-eNB

eNB-MME

Message




-

3-11

Steps 5 to 13 of the generic test procedure in Appendix Table 4-1 (Attach procedure) are performed on Cell1.

- - - -

12 Network responds with ATTACH ACCEPT message including a valid TAI list. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with QCI value as 1 is piggybacked in ATTACH ACCEPT message.


13 Check: Does the UE transmit an ATTACH COMPLETEmessage including an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message?


1 -

14

Check: Does the UE transmit a PDNCONNECTIVITY REQUEST message asspecified to request an additional PDN?

--> --> PDN CONNECTIVITY REQUEST

- -

15 The Network responds with ACTIVATE DEFAULTEPS BEARER CONTEXT REQUEST with QCI value set as 3.

<-- <-- ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

- -

16 After rrcConnectionReconfigurationComplete UE sends ActivateDefaultEPSBearerContextAccept Message in ULInformationTransfer

--> --> ACTIVATE DEFAULT EPS

BEARER CONTEXT ACCEPT

2 -

NOTE: The request of connectivity to an additional PDN may be performed by AT command

2.4.3.3 Specific Message Contents

Refer to Step 2 in Table 2-14.


Table 2-15: Message PDN CONNECTIVITY REQUEST

Information Element Value/Remark Comment

EPS Bearer Identity 0000 No EPS Bearer Identity assigned

Access Point Name APN-1 The requested PDN is different from default PDN










Procedure Transaction Identity

PTI-1 Network re-uses the particular PTI defined by UE for this present additional PDN connectivity request procedure.

Access Point Name APN-1 Network re-uses the particular APN defined by UE for this present additional PDN connectivity request procedure

EPS QoS

QCI

QCI 1(1)






PTI-1 Network re-uses the particular PTI defined



by UE for this present additional PDN connectivity request procedure.


EPS QoS

QCI

QCI 3(3)


UE attaches to network with 2 PDNs, 1 default bearer and 1 dedicated bearer on 1st PDN, 1 default bearer on 2nd PDN; different QCI on each PDN; Verify PDN details, EPS bearer status.

2.5.1. Test Purpose

(1)


ensure that {


then { successfully Attached to network with default bearer established }

}

(2)

with { UE successfully Attached to network }

ensure that {

when { UE receives Activate Dedicated EPS Bearer Context Request message in RRC Connection Reconfiguration }

then { UE sends an RRC Connection Reconfiguration Complete and Activate Dedicated EPS Bearer Context Accept }

}

(3)


with { UE has sent a PDN CONNECTIVITY REQUEST message }

ensure that {

when { UE receives an RRC Connection Reconfiguration message including an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message }

then { UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and SIP messages are send and received by UE }

}


References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 5.5.1.1, 5.5.1.2, clause 6.4.1.3, clause 6.5.1.2 and 3GPP TS 23.401 clause Annex F



Cell 1:


UE:


Preamble:





UE-eNB

eNB-MME

Message




3-11


- - - -

12 Network responds with ATTACH ACCEPT <-- <-- ATTACH ACCEPT - -



message including a valid TAI list. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT message.



1 -

14 The Network transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

Note: The Network implicitly reuses the PDN address defined in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.

<-- ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

- -

15 Check: Does the UE transmit an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message as specified?

--> ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

2 -

16

Check: Does the UE transmit a PDN

CONNECTIVITY REQUEST message as

specified to request an additional PDN?


- -

17 The Network responds with ACTIVATE DEFAULT

EPS BEARER CONTEXT REQUEST with QCI value set as 3.


- -

18 After rrcConnectionReconfigurationComplete UE sends ActivateDefaultEPSBearerContextAccept Message in ULInformationTransfer



3 -






c1 CHOICE{




dedicatedInfoNASList SEQUENCE (SIZE(1..maxDRB)) OF

1 entry

dedicatedInfoNAS[1] ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST with EPS Bearer Identity corresponding to drb-Identity 2

}

}

}

}


Table 2-21: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST




Linked EPS Bearer Identity 5 Network re-uses the EPS Bearer Identity of the default EPS bearer context.

EPS QoS According to reference dedicated EPS bearer context #1 –refer toTable 6-11

TFT According to reference dedicated EPS bearer context #1- refer to Table 6-11



















EPS QoS

QCI

QCI 1(1)









EPS QoS

QCI

QCI 3(3)

2.6. Attach in EPS: Test 1119

UE attaches to network with 1 PDN, 1 default bearer, skipping authentication

2.6.1. Test Purpose

(1)

with { UE in EMM-DEREGISTERED state }

ensure that {

when { UE is requested to make an Attach request with

Authentication disabled on network }

then { UE transmits an ATTACH REQUEST message and after

unsuccessful attempt it retries till re-attempt counter

reaches 5}

}


References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 5.2.2.3.2, 5.5.1.2.2, 5.5.2.1 and 6.5.1.2.




Cell 1:


• Authentication is disabled on MME.

UE:

• None

Preamble:





UE-eNB

eNB-MME

Message

1 The UE is switched on, attempt an attach on the UE.

- - - -

2 UE transmits an RRCConnectionRequest

message.

--> RRCConnectionRequest

3 Network transmits an RRCConnectionSetup

message.

<-- RRCConnectionSetup


-->

-->

ATTACH REQUEST -

5 Repeat Steps2-4 five times. - - - -

6 Check: Does the UEsend Attach Request?

-->

-->

ATTACH REQUEST 1 -







UE attaches to network with 1 PDN, 1 default bearer, AS security turned off.

2.7.1. Test Purpose

(1)

with { UE in state EMM-REGISTERED and AS security turned off }

ensure that {

when { UE sends ATTACH REQUEST and PDN CONNECTIVITY REQUEST message }

then { Network responds to the ATTACH REQUEST and UE transmits an ATTACH COMPLETE message with ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message }

}



2.7.3. TestDescription


Cell 1:


UE:


Preamble:

• The UE is in state Switched ON.




Step Procedure Message Sequence TP Verification

UE-eNB eNB-MME

Message

Note: AS security is off on eNB

1 <-- RRC: SYSTEM INFORMATION (BCCH)

2 UE transmits an RRCConnectionRequest

message.

--> RRC: RRCConnectionRequest

3 eNB transmits an RRCConnectionSetup message.

<-- RRC: RRCConnectionSetup

4 The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the Attach procedure by including the ATTACH REQUEST message. The PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST

-->

-->

RRC: RRCConnectionSetupComplete

NAS: ATTACH REQUEST

NAS: PDN CONNECTIVITY REQUEST

5 The Network transmits an AUTHENTICATION REQUEST message to initiate the EPS authentication and AKA procedure.

<--

<--

RRC: DLInformationTransfer

NAS: AUTHENTICATION REQUEST

6 The UE transmits an AUTHENTICATION RESPONSE message and establishes mutual authentication.

-->

-->

RRC: ULInformationTransfer

NAS: AUTHENTICATION RESPONSE



7 The Network transmits a NAS SECURITY MODE COMMAND message to activate NAS security.

<--

<--


NAS: SECURITY MODE COMMAND

8 The UE transmits a NAS SECURITY MODE COMPLETE message and establishes the initial security configuration.

with AS security OFF RRC securityModeCommand

is not exchanged in the network

-->

-->


NAS: SECURITY MODE COMPLETE

- EXCEPTION: Steps 9a1 to 9a2 describe behavior that depends on UE configuration;the “lower case letter” identifies a step sequence that take place if the UE has ESM information which needs to be transferred.

- -

9a1 If the UE sets the ESM information transfer flag in the last PDN CONNECTIVITY REQUEST message THEN the Network transmits an ESM INFORMATION REQUEST message to initiate exchange of protocol configuration options and/or APN.

<--

<--


NAS: ESM INFORMATION REQUEST



9a2 The UE transmits an ESM INFORMATION RESPONSE message to transfer protocol configuration options and/or APN.

-->

-->


NAS: ESM INFORMATION RESPONSE

10 The Network transmits a UECapabilityEnquiry message to initiate the UE radio access capability transfer procedure.

<-- RRC: UECapabilityEnquiry

11 The UE transmits a UECapabilityInformation message to transfer UE radio access capability.

--> RRC: UECapabilityInformation

12 The Network transmits an RRCConnectionReconfiguration message to establish the default bearer with condition as shown in the Note below. This message includes the ATTACH ACCEPT message. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT.

<--

<--

RRC: RRCConnectionReconfiguration

NAS: ATTACH ACCEPT

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

13 The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of default bearer.

--> RRC: RRCConnectionReconfigurationComplete



14 This message includes the ATTACH COMPLETE message. The ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message is piggybacked in ATTACH COMPLETE.

-->

-->


NAS: ATTACH COMPLETE

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

NOTE:SRB and DRB combination is setup with UE Registration procedure and the Generic Radio Bearer Establishment or Generic Radio Bearer Establishment, UE Test Mode Activated procedure using specific message content - the default RRCConnectionReconfiguration message with condition SRB2-DRB(n, m).



UE attaches to network with 1 PDN, 1 default bearer, NAS security turned off

2.8.1. Test Purpose

(1)

with { UE in state EMM-REGISTERED and NAS security turned off }

ensure that {

when { UE sends ATTACH REQUEST and PDN CONNECTIVITY REQUEST message }

then { Network responds with Authentication request and UE does not send Attach request at attach failure if the attempt counter is equal to 5}





Cell 1:

• Refer toTable 6-10 for cell configuration

UE:


Preamble:

• The UE is in state Switched ON.




UE-eNB

eNB-MME

Message

1 UE transmits an RRCConnectionRequest message.







-->

-->


NAS: ATTACH REQUEST



<--

<--



5 The UE transmits an AUTHENTICATION RESPONSE

-->

-->



6 The eNB transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE (State 2).

<-- RRC: RRCConnectionRelease






-->

-->


NAS: ATTACH REQUEST





<--

<--



11 The UE transmits an AUTHENTICATIONRESPONSE

-->

-->


NAS: AUTHENTICATIONRESPONSE



13 At attach failure and the attempt counter is equal to 5, does UE send ATTACH REQUEST?



Network rejects PDN connection when Invalid APN is used

2.9.1. Test Purpose

(1)

with { UE has sent an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message with invalid APN set on UE }

ensure that {

when { UE receives an ATTACH REJECT message with the reject cause set to “Unknown or missing APN” }

then { UE considers the USIM as invalid for EPS services and non-EPS services and enters state EMM-DEREGISTERED }


References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses5.5.1.2 and 6.5.1.4.




Cell 1:


UE:


Preamble:





UE-eNB

eNB-MME

Message

1 Switch the UE On - - - - -

2 The UE transmits an ATTACH REQUEST including a GUTI and a PDN CONNECTIVITY REQUEST message

--> --> ATTACH REQUEST - -

3 Network transmits an AUTHENTICATION REQUEST message, KSIASME value is different to the KSIASME value provided in the ATTACH REQUEST

<-- <-- AUTHENTICATION REQUEST

- -

4 Check: Does the UE respond with AUTHENTICATION RESPONSE message within 6 seconds and the included RES is equal to the XRES calculated in the Network?

--> --> AUTHENTICATION RESPONSE

- -

5 Network transmits a NAS SECURITY MODE COMMAND message including the KSIASME of the new EPS security context (as provided in step 3)

<-- <-- SECURITY MODE COMMAND

- -

6 Check: Does the UE respond with NAS SECURITY MODE COMPLETE message integrity protected and ciphered with the new EPS security context identified by the KSIASME received inthe SECURITY MODE COMMAND messagein step 5

--> --> SECURITY MODE COMPLETE

- -



- EXCEPTION: Steps 7a1 to 7a2 describe behavior that depends on UE configuration; the “lower case letter” identifies a step sequence that take place if the UE has ESM information which needs to be transferred.

- - - - -

7a1 If the UE sets the ESM information transfer flag in the last PDN CONNECTIVITY REQUEST message THEN the Network transmits an ESM INFORMATION REQUEST message to initiate exchange of protocol configuration options and/or APN.

<-- <-- ESM INFORMATION REQUEST

- -

7a2 The UE transmits an ESM INFORMATION RESPONSE message to transfer protocol configuration options with INVALID APN.

--> --> ESM INFORMATION RESPONSE

- -

8 The Network transmits an ATTACH REJECT message with EMM cause = “Unknown or missing APN” as specified.

<-- <-- ATTACH REJECT 1 P

9 The Network releases the RRC connection. - - - - -






Access Point Name No APN or Invalid APN The requested PDN is different from default PDN

PDN type '011'B The allowed values are respectively IPv4, IPv6, IPv4v6 and “unused but interpreted as IPv6 by the network”

Table 2-32: Message ATTACH REJECT


Security header type 0000 “No security protection”

EMM cause 0001 1011 #27 “Unknown or



missing access point name”

ESM message container

Not present


Network deactivates the InternetPDN after UE initial attach.

2.10.1. Test Purpose

(1)


ensure that {


then { UE successfully Attached to network with default bearer established}

}

}

(2)

with { UE receives Activate Dedicated EPS Bearer Context Request message in RRC Connection Reconfiguration and UE receives an RRC Connection Reconfiguration Complete message and sends Activate Dedicated EPS Bearer Context Accept }

ensure that {

when { Deactivate EPS Bearer Context Request is triggered from network

}

then { UE deletes all EPS bearer contexts identified to the internet PDN and transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT }

}


References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.5.1.1.




Cell 1:

• Refer to Table 6-10.

UE:


• Authentication is disabled on MME.

Preamble:

• The UE is in EMM-CONNECTED state and connected to Internet PDN and default EPS bearer exists.




UE – eNB

eNB-MME

Message

- Cell 1 is the serving cell - - - - -




-

3-11


- - - -



- -



1 -



Table 2-34: Message DEACTIVATE EPS BEARER CONTEXT REQUEST


EPS Bearer Identity Default EBId that was created during ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST during ATTACH procedure

ESM cause 00100100 regular deactivation

Table 2-35: Message DEACTIVATE EPS BEARER CONTEXT ACCEPT


EPS Bearer Identity Default EBId that was created during ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST during ATTACH procedure


Network disconnects the InternetPDN after UE initial attach.


(1)


ensure that {


then { successfully Attached to network with default bearer established }

}

(2)

with { UE has sent a PDN CONNECTIVITY REQUEST message for another PDN }

ensure that {


when { UE receives an RRC Connection Reconfiguration message including an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message and UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message }

then { Network sends PDN Disconnect Request and EPS Bearer Context is deactivated and network sends the Detach Request for second PDN.

}

}


References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 6.5.2.2, and 6.5.2.4.



Cell 1:


UE:


Preamble:

• The UE is in EMM-CONNECTED state and connected to Internet PDN and a default EPS bearer exists.




UE-eNB eNB-MME

Message

- Cell 1 is the serving cell - - - -






3-11 Steps 5 to 13 of the generic test procedure in Appendix Table 4-1 (Attach procedure) are performed on Cell 1.

- - - -




--> --> ATTACH COMPLETE 1 -

14 Check: Does the UE transmit a PDNCONNECTIVITY REQUEST message asspecified to request an additional PDN?


- -

15 The Network responds with ACTIVATE DEFAULTEPS BEARER CONTEXT REQUEST with QCI value set as 3.


- -

16 After RRC Connection Reconfiguration Complete UE sends Activate Default EPS Bearer Context Accept Message in ULInformationTransfer



- -

17 On Network side PDN disconnection is triggered for second PDN

- - -

18 Check: Does Network sends a Deactivate EPS Bearer Context Request?

<-- <-- DEACTIVATE EPS BEARER CONTEXT REQUEST

-

19 Check: does UE transmits Deactivate EPS Bearer Context Accept

--> --> DEACTIVATE EPS BEARER CONTEXT ACCEPT

-



20 Check: does Network send a Detach Request?

<-- <-- DETACH REQUEST -

21 Check: after Detach RRC connection is released

<-- RRC CONNECTION RELEASE Release

2


Table 2-37: Message PDN DISCONNECT REQUEST


EPS Bearer Identity Default EBId created during ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST during ATTACH procedure


UE successfully attaches to network when blank APN used.


(1)

with { UE is configured with Blank APN and is in EMM-REGISTERED state}

ensure that {

when { UE has sent an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message }

then { UE successfully attached to network with default APN from subscription data isused by the MME. }


References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses5.5.1.2 and 6.5.1.4.




Cell 1:


UE:


Preamble:





UE-eNB

eNB-MME

Message

1 Switch the UE on - - - - -

2 The UE transmits an ATTACH REQUEST including a GUTI and a PDN CONNECTIVITY REQUEST message


3 Network transmits an AUTHENTICATION REQUEST message, KSIASME value is different to the KSIASME value provided in the ATTACH REQUEST


- -

4 Check: Does the UE respond with AUTHENTICATION RESPONSE message within 6 seconds and the included RES is equal to the XRES calculated in the Network?


- -

5 Network transmits a NAS SECURITY MODE COMMAND message including the KSIASME of the new EPS security context (as provided in step 3)

<-- <-- SECURITY MODE COMMAND

- -

6 Check: Does the UE respond with NAS SECURITY MODE COMPLETE message integrity protected and ciphered with the new EPS security context identified by the KSIASME received inthe SECURITY MODE COMMAND messagein step 5

--> --> SECURITY MODE COMPLETE

- -



7 MME responds with ATTACH ACCEPT message including a valid TAI list. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT message




1






Access Point Name No APN The requested PDN is different from default PDN

PDN type '011'B The allowed values are respectively IPv4, IPv6, IPv4v6 and “unused but interpreted as IPv6 by the network”

2.13. Attach Failurein EPS: Test 1201

UE receives attach reject with “TA not allowed”.


(1)

with { UE has sent an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message }

ensure that {

when { UE receives an ATTACH REJECT message with the reject cause set to “Tracking area not allowed”and serving cell belongs to TAI where UE was rejected }


then { UE sets the EPS update status to EU3 ROAMING NOT ALLOWED, UE deletes the GUTI, last visited registered TAI and KSI, UE enters the state EMM-DEREGISTERED.LIMITED-SERVICE and UE stores the current TAI in the list of “forbidden tracking areas for regional provision of service” and UE does not attempt to attach on any other cell }

}


References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 5.3.2,5.5.1.2.2, 5.5.1.2.5, 5.2.2.3.2, Annex C and TS 36.304 clause 4.3.



Cell 1 and Cell 2 Home PLMN:


UE:

• The UE is configured to initiate EPS attach.

• The UE is previously registered on E-UTRAN, and when on E-UTRAN, the UE is lastauthenticated and registered on Cell 1.

Preamble:

• UE is in Switched OFF state.




UE-eNB eNB-MME

Message

1 The Network configures:

- Cell 1 as the “Serving cell”.

- Cell 2 as a “Suitable Neighbor cell”.

- - - - -

- The following messages are to be observed on Cell 1 unless explicitly stated otherwise.

- - - - -




3 The UE transmits an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message.


- -

4 The Network transmits an ATTACH REJECT message, EMM cause = “Tracking area not allowed”.(The list of “forbidden tracking areas for regional provision of service“ in the UE should now contain TAI-1)

<-- <-- ATTACH REJECT

-

5 The Network releases the RRC connection.

- - - - -

6 Check:UE does not transmit the ATTACH REQUEST message in the next 30 seconds on Cell 1 or Cell2?


1

7 Initiate attach by MMI or by AT command.

- - - - -

8 Check:UE does nottransmit the ATTACH REQUEST message in the next 30 seconds?


1

- At the end of this test procedure sequence, the UE is in end state E-UTRA idle.

- -

-

-




EMM cause 00001110 #12 “Trackingarea not allowed”

ESM message container Not present



Old GUTI or IMSI IMSI-1 GUTI has been deleted; only IMSI is available.

Last visited registered TAI

Not present TAI has been deleted.


2.14. Attach Failurein EPS:Test 1204

On receiving attach reject with IMSI invalid, UE considers USIM invalid.


(1)


ensure that {

when { UE receives an ATTACH REJECT message with the reject cause set to “Illegal UE” }


}


References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.5.1.2.5.



Cell 1:


UE:



Preamble:





UE-eNB

eNB-MME

Message




- cell 1 as the “Serving cell”.

- - - - -

- The following messages are to be observed on cell 1 unless explicitly stated otherwise.

- - - - -

2 The UE is switched on. - - - - -

3 The UE transmits an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message on Cell 1.


- -

4 The Network transmits an ATTACH REJECT message with EMM cause = “Illegal UE” as specified.


1 -





Old GUTI or IMSI IMSI-1

ESM message container PDN CONNECTIVITY REQUEST message to request PDN connectivity to the default PDN



EMM cause 00000011 #3 “Illegal UE”


UE does not send Attach and consider the USIM as invalid(IMSI Invalid) until switching off, when switch ON again it sends the Attach request with IMSI


(1)


ensure that


when { UE receives an ATTACH REJECT message with the reject cause set to “Illegal UE” }

then { UE considers the USIM as invalid for EPS services and non-EPS services and enters state EMM-DEREGISTERED after UE is switched OFF and Switched ON again it sends the ATTACH REQUEST with IMSI }

}





Cell 1:


UE:



Preamble:





UE-eNB

eNB-MME

Message



- - - - -

- The following messages are to be observed on cell 1 unless explicitly stated otherwise.

- - - - -




- -



4 The Network transmits an ATTACH REJECT message with EMM cause = “Illegal UE” as specified.


- -


6 UE is switched OFF and switched on again - - - - -

7 Check: Does the UE transmit an ATTACH REQUEST message in the next 30 seconds on cell 1?


1




Old GUTI or IMSI IMSI-1

ESM message container PDN CONNECTIVITY REQUEST message to request PDN connectivity to the default PDN



EMM cause 00000011 #3 “Illegal UE”


On receiving attach reject with “Illegal ME”, UE considers USIM invalid


(1)


ensure that {

when { UE receives an ATTACH REJECT message with the reject cause set to “Illegal ME” }


}






Cell 1:

• Refer toTable 6-10

UE:



Preamble:





UE-eNB

eNB-MME

Message



- - - -




- -

4 Transmits an ATTACH REJECT message with EMM cause = “Illegal UE” as specified.


- -

5 The UE releases the RRC connection. - - - - -





EMM cause 0000 0110 #6 “Illegal ME”

2.17. Combined Attach: Test 1304

Combined attach successful on EPS service only.


(1)


ensure that {

when { the UE is powered up or switched on }

then { the UE transmits an ATTACH REQUEST message with the EPS attach type set to “combined

EPS/IMSI attach” and enters EMM-REGISTERED-INITIATED state }

}

(2)

with { UE in state EMM-REGISTERED-INITIATED }

ensure that {

when { the UE receives an ATTACH ACCEPT message with EPS attach result set to “EPS only” and EMM cause set to “IMSI unknown in HNetwork” }

then { the UE transmits an ATTACH COMPLETE message,the UE sets the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number and enters EMM-REGISTERED.NORMAL-SERVICE state and MMIDLE state.The USIM shall be considered as invalid for non-EPS services until switching off or the UICC containing the USIM is removed }

}


References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301, clause 5.5.1.3.4.1.




Cell 1:

• Set to ''Serving cell'' configured as shown inTable 6-11.

UE:

• The UE is configured to initiate combined EPS/IMSI attach;


Preamble:

• The UE isin stateSwitched OFF (state 1)




UE-eNB eNB-MME Message

1 The UE is powered up or switched on.

- - - - -

2 The UE transmits ATTACH REQUEST message with a PDN CONNECTIVITY REQUEST message to request PDN connectivity to the default PDN with EPS attach type set to “combined EPS/IMSI attach”


3-11

Steps 5 to13 of the generic test procedure in Appendix Table 4-1 (Attach procedure) are performed on Cell 1.

- - - -



12 The Network transmits ATTACH ACCEPT message with EPS Attach result IE set to “EPS only” and EMM cause set to “IMSI unknown in HNetwork”, including the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message as specified.


13 Check: Does the UE transmit an ATTACH COMPLETE message including an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message as specified?

--> --> ATTACH COMPLETE 1 P


Table 2-52: ATTACH REQUEST


Old GUTI or IMSI GUTI-1

EPS attach type 010 “combined EPS/IMSI attach”


Last visited registered TAI TAI-1

Old location area identification LAI-1

TMSI status Not present



EPS attach result 001 “EPS only”

The Network accepts Combined attach for EPS services only.

ESM message container ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message



GUTI GUTI-1 The Network assigns a new GUTI

LAI Not present

MS identity Not Present No TMSI is assigned

EMM cause 00000010 #2 “IMSI unknown in HNetwork”

2.18. Combined Attach:Test 1305

Combined attach rejected by network


(1)


ensure that {

when { UE receives an ATTACH REJECT message with the reject cause set to “EPS services not allowed” }

then { UE considers the USIM as invalid for EPS services and enters state EMM-DEREGISTERED and UE does not attempt to attach on any other cell }

}


References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.5.1.3.5



Cell 1:



UE:

• The UE is configured to initiate combined EPS/IMSI attach;

• The UE having invalid IMSI in Usim

Preamble:

• The UE isin stateSwitched OFF (state 1)





1 The Network configuresCell 1 as Suitable cell

- - - - -


3 The UE transmits an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message.


4 The Network transmits an ATTACH REJECT message with the EMM cause set to“Illegal UE”.

<-- <-- ATTACH REJECT - -


- - - - -


Table 2-55: ATTACHREJECT


EMM cause '0000 0111'B EPS Service not allowed

2.19. Detach: Test 1406

UE re-attaches on receiving detach request sent by network(with detach type “ re-attach required”)


(1)


with { UE in EMM-REGISTERED state }

ensure that {

when { Network sends DETACH REQUEST message with the Detach type IE “re-attach required” }

then { UE sends DETACH ACCEPT message and UE initiates an attach procedure with the current EPS security context}

}


References: The conformance requirements covered in the current TC are specified in: TS 24.301, clause 5.5.2.3.2.



Cell 1:


UE:

• None.

Preamble:

• The UE is in state Generic RB established (state 3)on Cell 1.





1 The Network initiates Detach procedure with the Detach Type IE “re-attach required”.

<-- <-- DETACH REQUEST - -

2 Check: Does the UE send DETACH ACCEPT message?

--> --> DETACH ACCEPT 1 P

3 The Network releases RRC connection.

- EXCEPTION: Step 3a describes a behavior which depends on the UE

- - - - -



capability.

3a If NOT pc_Automatic_Re_Attach, initiate an attach by MMI or by AT command.

- - - - -

4 Check: Does the UE send ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message?

--> --> ATTACH REQUEST 1 P

- EXCEPTION: Steps 4Aa1 to 4Aa2 describe behavior that depends on UE configuration; the “lower case letter” identifies a step sequence that take place if the UE has ESM information which needs to be transferred.

- - - - -

4Aa1 If the UE sets the ESM information transfer flag in the last PDN CONNECTIVITY REQUEST message THEN the Network transmits an ESM INFORMATION REQUEST message to initiate exchange of protocol configuration options and/or APN.

<-- <-- ESM INFORMATION REQUEST

- -

4Aa2 The UE transmits an ESM INFORMATION RESPONSE message to transfer protocol configuration options and/or APN.

--> --> ESM INFORMATION RESPONSE

- -

5 The Network sends ATTACH ACCEPT to assign the new GUTI (GUTI-2). The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT message


6 Check: Does the UE send ATTACH COMPLETE message

--> --> ATTACH COMPLETE 1 P



including an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message?



Table 2-57: Message DETACH REQUEST


Detach type '001'B “re-attach required”




NAS key set identifier

NAS key set identifier The value is a same value to be allocated by Network in Preamble.

Old GUTI or IMSI GUTI-1

NOTE: This message is sent within the SECURITY NAS PROTECTED MENetworkAGE


Table 2-59: Message SECURITY PROTECTED NAS MENetworkAGE


Security header type '0001'B Integrity protected

NAS message '01000001'B ''ATTACH REQUEST''




TAI list

Length of tracking area identity list contents ‘00000110’B 6 octets

Number of elements ‘00000’B 1 element

Type of list ‘00’B “list of TACs



belonging to one PLMN, with non-consecutive TAC values”

Partial tracking area identity list TAI-1

GUTI GUTI-2


UE receives detach request with detach type set to “re-attach not required” with no EMM cause IE.


with { UE in EMM-REGISTERED state }

ensure that {

when { UE receives a DETACH REQUEST message with the Detach type IE “re-attach not required” and with no EMM cause IE included }

then { UE delete any GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, KSI, set the update status to EU2 NOT UPDATED and start timer T3402. when T3402 expired, the UE attempts to attach again }

}


References: The conformance requirements covered in the current TC are specified in: TS 24.301, clause 5.5.2.3.4.



Cell 9:


UE:

• None.

Preamble:


• The UE is in state Generic RB established (state 3) on cell 9

• T3402 in the UE is set to 2 minutes.





1 Network initiates Detach procedure with the Detach Type IE “re-attach not required” and no EMM cause IE included

<-- <-- DETACH REQUEST - -


- - - - -

3 Check: When the timer T3402 expires does the UE transmit ATTACH REQUEST message on cell I?

--> --> ATTACH REQUEST 1 P

4-12

Steps 4 to 12 of the generic test procedurein Appendix Table 4-1 (Attach procedure) are performed on Cell 9.

- - - - -





Detach type ‘010’B “re-attach not required”

EMM cause Not present





NAS key set identifier '111'B no key is available



TSC Any allowed value TSC does not apply for NAS key set identifier value “111”.

Old GUTI or IMSI IMSI1

Last visited registered TAI Not present


UE receives detach request with detach type set to “IMSI detach”


with { UE in EMM-REGISTERED state}

ensure that {

when { UE receives DETACH REQUEST message with the Detach type IE = “IMSI detach” }

then { UE sends TRACKING AREA UPDATE REQUEST message with EPS update type IE = “Combined TA/LA updating with IMSI attach”}

}


References: The conformance requirement covered in the present TC is specified in: 3GPP TS 24.301 clauses 5.5.2.3.2.



Cell 1:


UE:

• None.

Preamble:

• The UE is in state Generic RB established (state 3) on Cell 1.






1 Force the Network to initiate Detach procedure with the Detach Type IE “IMSI detach”

<-- DETACH REQUEST

- -

2 The UE may send DETACH ACCEPT message.(Optional)

--> DETACH ACCEPT

- -

3 Check: Does the UE send TRACKING AREA UPDATE REQUEST message?

--> TRACKING AREA UPDATE REQUEST

1 P





Detach type ‘011’B “IMSI detach”



Table 2-66: Message TRACKING AREA UPDATE REQUEST


EPS update type

EPS update type value ‘010’B “Combined TA/LA updating with IMSI attach”

Old GUTI GUTI-1

Last visited registered TAI TAI-1

Old location area identification Not Present

TMSI status ‘0’B “no valid TMSI available”


2.22. Authentication: Test 1505

On receiving invalid AUTN(Invalid MAC), UE sends AUTHENTICATION FAILURE message with “MAC failure”, andnetwork terminate the attach procedure


(1)

with { UE having sent an initial NAS message }

ensure that {

when { as a result of failure due to “MAC failure” of an Authentication procedure , network decides not to initiate the identificationprocedure after an unsuccessful authentication procedure the UE receives an AUTHENTICATION REJECT message}

then { the UE shall set the update status to EU3 ROAMING NOT ALLOWED, delete the stored GUTI, TAI list, last visited registered TAI and KSIASME and enter state EMM-DEREGISTERED }

}


References: The conformance requirements covered in the current TC are specified in: TS 24.301, clauses 5.4.2.5.



Cell 1:


UE:

• None.

Preamble:





UE-eNB eNB- Message



MME

1 Switch the UE on - - - - -

2 The UE transmits an ATTACH REQUEST message including a GUTI and a PDN CONNECTIVITY REQUEST message


3 The Network transmits an AUTHENTICATION REQUEST message without integrity protection and ciphering


- -

4 The UE transmits an AUTHENTICATION RESPONSE.


- -

5 The Network transmits an AUTHENTICATION REJECT message without integrity protectionand ciphering

<-- <-- AUTHENTICATION REJECT

- -

6 Network releases the RRC connection

- - - 1 -

2.23. Service Request: Test 1704

Test 1704 - Service Request rejected due to IMSI invalid('Illegal UE')


(1)

with { UE having sent a SERVICE REQUEST message }

ensure that {

when { UE receives a SERVICE REJECT message with the EMM cause set to 'Illegal UE' }

then { UE considers the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed, enters the state EMM-DEREGISTERED }

}


References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.6.1.5 and TS 24.008, clause 4.7.13.4.




Cell 1:

• Set to ''Serving cell'', and configured as shown inTable 6-11

UE:

• None.

Preamble:

• The UE isin state Registered, Idle mode (state 2) on Cell 1.




UE-eNB

eNB-MME

Message

1 The Network pages the UE using S-TMSI with CN domain indicator set to “PS”.

- - - - -


- - - - -

2 The UE transmits a SERVICE REQUEST message. --> --> SERVICE REQUEST

- -

3 The Network transmits a SERVICE REJECT message with the EMM cause set to 'Illegal UE'.

<-- <-- SERVICE REJECT

- -


5 Check: Does the UE transmit an ATTACH REQUEST message in the next 30 seconds?


1 -

6 UE switched off and brought back to operation. - - - - -



1 -




Table 2-69: SERVICE REJECT


EMM cause '00000011'B Illegal UE







Old GUTI or IMSI IMSI of the UE


Not present

Old location area identification

Not present


2.24. Service Request:Test 1705

Service Request rejected due to EMM cause set to 'Illegal ME.”


(1)


ensure that {

when { UE receives a SERVICE REJECT message with the EMM cause set to 'Illegal ME' }

then { UE considers the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed, enters the state EMM-DEREGISTERED }

}






Cell 1:

• Set to ''Serving cell'', and configured as shown inTable 6-11

UE:

• None.

Preamble:

• The UE isin stateRegistered, Idle mode (state 2) on cell1 as described in TS36.508.




UE-eNB

eNB-MME

Message


- - - - -


- - - - -


- -

3 The Network transmits a SERVICE REJECT message with the EMM cause set to 'Illegal ME'.


- -




1 -




1 -






EMM cause '00000110'B Illegal ME







Old GUTI or IMSI IMSI of the UE


Not present


Not present


2.25. Service Request: Test 1706

Service Request rejected due to EMM cause set to “EPS Services not Allowed”


(1)


ensure that {

when { UE receives a SERVICE REJECT message with the EMM cause set to 'EPS services not allowed' }

then { UE considers USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed and enters the state EMM-DEREGISTERED }

}






Cell 1:

• Set to ''Serving cell'' configured as shown inTable 6-11

UE:

• None.

Preamble:

• The UE isin stateRegistered, Idle mode (state 2) on Cell1.




UE-eNB

eNB-MME

Message


- - - - -


- - - - -


- -

3 The Network transmits a SERVICE REJECT message with the EMM cause set to 'Illegal UE'.


- -




1 -




1 -






EMM cause '00000111'B EPS services not allowed





Old GUTI or IMSI IMSI1

Last visited registered TAI Not present

3. CS8-TS-LTE-WCDMA-RRM

3.1. LTE to UMTS Reselection: Test 2101

UE reselects (LAU/RAU) to UMTS network in RRC_Idle state after initial attach on LTE because LTE cell signal is below threshold

3.1.1. Test Purpose

(1)

with { UE in E-UTRA RRC_IDLE state }

ensure that {

when { the serving cell becomes non-suitable as cell signal is below threshold and there is a suitable UTRA neighbor cell}

then { UE selects the suitable UTRA neighbor cell }


References: The conformance requirements covered in the current TC are specified in: TS 36.304, clause 4.1, 4.3, 5.2.1, 5.2.3.2 and 5.3.1. TS 25.304, clause 5.2.3.2.

The cell selection criterion S is fulfilled when:

Srxlev > 0

Where:

Srxlev = Qrxlevmeas – (Qrxlevmin + Qrxlevminoffset) - Pcompensation

Where:

Srxlev Cell Selection RX level value (dB)

Qrxlevmeas Measured cell RX level value (RSRP).

Qrxlevmin Minimum required RX level in the cell (dBm)

Qrxlevminoffset Offset to the signalled Qrxlevmin taken into account in the Srxlev evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN [5]

Chapter Three: CS8-LTE-WCDMA-RRM-TS | 69

Pcompensation max(PEMAX – PUMAX, 0) (dB)

PEMAX Maximum TX power level an UE may use when transmitting on the uplink in the cell (dBm) defined as PEMAX in [TS 36.101]

PUMAX Maximum RF output power of the UE (dBm) according to the UE power class as defined in [TS 36.101]


for FDD cells: Srxlev > 0 AND Squal > 0

for TDD cells: Srxlev > 0

Where:

Squal = Qqualmeas – Qqualmin

Srxlev = Qrxlevmeas - Qrxlevmin - Pcompensation

Squal Cell Selection quality value (dB)

Applicable only for FDD cells.


Qqualmeas Measured cell quality value. The quality of the received signal expressed in CPICH Ec/N0 (dB) for FDD cells. CPICH Ec/N0 shall be averaged as specified in [10]. Applicable only for FDD cells.

Qrxlevmeas Measured cell RX level value. This is received signal, CPICH RSCP for FDD cells (dBm) and P-CCPCH RSCP for TDD cells (dBm).

Qqualmin Minimum required quality level in the cell (dB). Applicable only for FDD cells.


Pcompensation max(UE_TXPWR_MAX_RACH – P_MAX, 0) (dB)

UE_TXPWR_MAX_RACH Maximum TX power level an UE may use when accessing the cell on RACH (read in system information) (dBm)

P_MAX Maximum RF output power of the UE (dBm)




Cell 1 and Cell 5:

• Cell 1 EUTRA serving E-UTRA cell as shown inTable 6-10

• Cell 5 UTRA cell is neighboring cell as shown inTable 6-13 and Table 6-15

Radio Conditions:

• Cell 1 configured as serving as shown inTable 6-16

• Cell 5 configured as suitable neighbor cell as shown inTable 6-17

System information combination 4 as defined in the table below.

System Information Block Type

Combination No. SIB2 SIB3 SIB4 SIB5 SIB6 SIB7 SIB8 SIB9 SIB10

SIB11

SIB13

4 X X X

Settings of suitable/non-suitable cells (Reference values)

Power Level Type E-UTRAN UTRAN

RSTP Qrxlevmin Srxlev RSTP Qrxlevmin Srxlev

serving cell -85 dBm -106 21 -60 dBm -79 19

suitable Intra RAT -91 dBm -106 15 -70 dBm -79 9

Suitable Inter RAT -97 dBm -106 9 -70 dBm -79 9

Non Suitable -115 dBm -106 -9 -90 dBm -79 -11

Non Suitable Off cell -145 dBm -106 -39 -122 dBm -79 -43

UE:

• None

Preamble:

• UE is in state Registered, Idle Mode (state 2) on Cell 1 (serving cell)




UE-NodeB

NodeB-RNC

Message



1 On NETWORK side re-adjusts the cell-specific reference signal level of Cell 1 so that Srxlev on UE for Cell5 is greater than Cell 1, i.e Cell5 becomes the strongest cell

- - - -

2 The UE transmits a RRC CONNECTION REQUEST message on the cell5

--> RRC: RRC CONNECTION REQUEST

- -

3 Network transmits an RRC CONNECTION SETUP message.

<-- RRC: RRC CONNECTION SETUP

- -

4 The UE transmits an RRC CONNECTION SETUP COMPLETE message.

--> RRC: RRC CONNECTION SETUP COMPLETE

- -

5 The UE transmits a ROUTING AREA UPDATE REQUEST message.

--> --> RRC: INITIAL DIRECT TRANSFER

NAS: ROUTING AREA UPDATE REQUEST

- -

6 The Network transmits a SECURITY MODE COMMAND message.

<-- RRC: SECURITY MODE COMMAND

- -

7 The UE transmits a SECURITY MODE COMPLETE message.

--> RRC: SECURITY MODE COMPLETE

- -

8 The network transmits a ROUTING AREA UPDATE ACCEPT message.

<-- <-- RRC: DOWNLINK DIRECT TRANSFER

NAS: ROUTING AREA UPDATE ACCEPT

- -

9 The UE transmits a ROUTING AREA UPDATE COMPLETE message.

--> --> RRC: UPLINK DIRECT TRANSFER

NAS: ROUTING AREA UPDATE COMPLETE

1 -


Table 3-2: SystemInformationBlockType1


SystemInformationBlockType1 ::= SEQUENCE {



cellSelectionInfo SEQUENCE {

q-Rxlevmin -48

}

}




cellReselectionPriority[n] 7

q-RxLevMin[n] -60

}

}

3.2. LTE to UMTS Reselection: Test 2103

UE reselects to UMTS network in LTE RRC_Connected state with active data transfer resumed on UMTS because LTE cell signal becomes lower than threshold.

3.2.1. Test Purpose

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { the serving cell becomes non-suitable as cell signal is below threshold and there is a suitable UTRA neighbor celland UE receives an RRCConnectionRelease message}

then { UE selects the suitable UTRA neighbor cell and enters RRC_IDLE state }

}


References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.8.3, 5.3.12 and TS 36.304, clause 5.2.7.




Cell 1 and Cell 5:



Radio Conditions:











UE:

• None

Preamble:

• The UE is in state Generic RB Established (state 3) on cell 1




UE-NodeB

NodeB-RNC Message

On NETWORK side re-adjusts the cell-specific reference signal level of Cell 1 so that Srxlev on UE for Cell5 is greater than Cell 1, i.e Cell5 becomes the strongest cell

1 Network transmits an RRCConnectionReleasemessage

<-- RRCConnectionRelease - -



().

2 The UE transmits a RRC CONNECTION REQUEST message on the cell 5


- -

3 The Network transmits an RRC CONNECTION SETUP message.


- -

4

The UE transmits an RRC CONNECTION SETUP COMPLETE message.


- -




- -



- -



- -

8 The Network transmits a ROUTING AREA UPDATE ACCEPT message.



- -




1 -






q-Rxlevmin -48

}

}







q-RxLevMin[n] -60

}

}

3.3. LTE to UMTS Redirection: Test 2201

Network redirects UE from LTE to UMTS R99 through “RRC Connection Release”, active data transfer resumed on UMTS

3.3.1. Test Purpose

(1)


ensure that {

when { the serving cell becomes non-suitable as cell signal is below threshold and there is a suitable UTRA-R99 neighbor celland UE receives an RRCConnectionRelease message including an IE redirectionInformation with utra-CarrierFreq UTRA frequency }

then { UE selects the suitable UTRA-R99 neighbor cell and resume the active data transfer }

}





Cell 1 and Cell 5:

• Cell 1 EUTRA serving E-UTRA cell as shown in Table 6-10

• Cell 5 UTRA-R99 cell is neighboring cell as shown inTable 6-13 and Table 6-15

Radio Conditions:


• Cell 1 configuredas shown inTable 6-16


UE:

• None

Preamble:

• The UE is in state Generic RB Established (state 3) on cell 1




UE-NodeB NodeB-RNC Message

The UE is attached with cell 1 and there is an active UL and DL data transfer on Cell 1.

1 Network transmits an RRCConnectionRelease message (IE redirectionInformation including UTRA-CarrierFreq of Cell 5).




- -



- -



- -




- -



- -

6 The UE transmits a --> RRC: SECURITY MODE - -



SECURITY MODE COMPLETE message.

COMPLETE




- -




1 -

9 Active UL and DL data transferis continued on cell 5


Table 3-8: RRCConnectionRelease Message


RRCConnectionRelease ::= SEQUENCE {


c1 CHOICE {

rrcConnectionRelease-r8 SEQUENCE {

redirectedCarrierInfo ::= CHOICE {

utra-FDD Downlink UARFCN of cell 5

UTRA-FDD

}

}

}

Table 3-9: System Information Block Type 19


SysInfoType19 ::= SEQUENCE {

qRxLevMinEUTRA[n] -50

}

}






q-RxLevMin[n] -60

}

}


Network redirects UE from LTE to UMTS HSDPA/HSUPA through “RRC Connection Release”, active data transfer resumed on UMTS.

3.4.1. Test Purpose

(1)


ensure that {

when { the serving cell becomes non-suitable as cell signal is below threshold and there is a suitable UTRA-HSDPA/HSUPA neighbor celland UE receives an RRCConnectionRelease message including an IE redirectionInformation with utra-CarrierFreq UTRA frequency }

then { UE selects the suitable UTRA-HSDPA/HSUPA neighbor cel and resume the active data transfer }

}




Pre-test Conditions


Cell 1 and Cell 5:


• Cell 5 UTRA-HSDPA/HSUPA cell is neighboring cell as shown inTable 6-13 and Table 6-15


Radio Conditions:



UE:

• -None

Preamble:

• The UE is in state Generic RB Established (state 3) on Cell 1.




UE-NodeB NodeB-RNC Message

The UE is attached with cell 1 and there isan active UL and DL data transfer is on cell 1





- -



- -



- -




- -



- -





- -




- -




1 -

9 ActiveUL and DL data transfer is continued on cell 5.






c1 CHOICE {




UTRA-FDD

}

}

}





}

}





q-RxLevMin[n] -60

}

}


Network redirects UE from LTE to UMTS R99 through “RRC Connection Release”, redirection failed, UE returns to LTE and resumes data transfer.

3.5.1. Test Purpose

(1)


ensure that {


then { Network redirects to suitable UTRAN neighboring cell}

(2)

with {UE send RRC CONNECTION REQUEST on UTRA cell and UE in UTRA CELL_DCH state }

ensure that {

when { UE receives an RRC CONNECTION REJECT message including an IE Redirection info with E-UTRA target info E-UTRA frequency }

then { UE enters on E-UTRAN Carrier included in IE Redirection info and resume the active data transfer}

}


References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.8.3, 5.3.12 and TS 36.304, clause 5.2.7, TS 36.331, clauses 5.3.3.2, 5.3.3.3 and 5.3.3.8




Cell 1 and Cell 5:


• Cell 5 UTRA-R99 is a neighboring cell as shown inTable 6-13 and Table 6-15

Radio Conditions:



UE:

• None

Preamble:





UE-eNB

eNB-MME

Message

The UE is attached on cell 1 and there is an active UL and DL data transferis on Cell 1.





1 -

3 The Network transmit a RRC CONNECTION REJECT

<-- RRC CONNECTION REJECT - -

4 The UE transmits a RRCConnectionRequest message on the Cell 1.

--> RRC: RRCConnectionRequest - -

5 Network transmit an RRCConnectionSetup message.

<-- RRC: RRCConnectionSetup - -



6 The UE transmits a RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment anda TRACKING AREA UPDATE REQUESTmessage is sent to update the registration of the actual tracking area.

--> RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST

- -

7 The Network transmits a NAS SECURITY MODE COMMAND message to activate NAS security

<-- RRC: DLInformationTransfer


- -


--> RRC: ULInformationTransfer


- -

9 Network responds with TRACKING AREA UPDATE ACCEPT message.


NAS: TRACKING AREA UPDATE ACCEPT

- -

10 Check: Does the UE send a TRACKING AREA UPDATE COMPLETE on the cell specified in the test case?


NAS: TRACKING AREA UPDATE COMPLETE

2 -

11 ActiveUL and DL data transfer is continued on cell 1






c1 CHOICE {




UTRA-FDD

}

}



}





}

}




q-RxLevMin[n] -60

}

}

3.6. UMTS to LTE Reselection: Test 2403

UE reselects (EPS attach) to LTE network when PS session is active on UMTS but UMTS cell signal becomes lower than threshold,active data transfer resumed on LTE

3.6.1. Test Purpose

(1)

with { UE in UTRA Cell_FACH state with active UDP data transfer}

ensure that {

when { the serving cell becomes non-suitable as cell signal is below threshold and there is a suitable EUTRA neighbor cell}

then { UE selects the suitable EUTRA neighbor cell }


References: The conformance requirements covered in the current TC are specified in: TS 25.304, clause 4.1, 5.2.3.1 and 5.3.1.

The cell reselection criterion and related parameters are same as mentioned in test case 6.3.1 sub clause 6.3.1.2 Conformance Requirement.




Cell 5 and Cell 1:

• Cell 5 UTRA cell as shown inTable 6-13 and Table 6-15

• Cell 1 EUTRA neighbor E-UTRA cell as shown inTable 6-10

Radio Conditions:

• Cell 5 configured as serving cell as shown inTable 6-17

• Cell 1 configured as suitable neighbor as shown inTable 6-16

UE:

• None

Preamble:

• UE is in state Registered, URA_PCH Mode on Cell 5 (serving cell) with active data transfer.




UE-eNB

eNB-MME

Message

1 The UE is attached with cell 5 and there is an active UL and DL data transfer is on cell 5..

- - - -

2 The UE transmits an RRCConnectionRequest message on the Cell 1.


3 Networktransmits an RRCConnectionSetup message.


4 The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment anda TRACKING AREA UPDATE REQUESTmessage is sent to update the registration of the actual tracking area.

--> --> RRC: RRCConnectionSetupCompleteNAS: TRACKING AREA UPDATE REQUEST

- -




<-- <-- RRC: DLInformationTransfer


- -


--> --> RRC: ULInformationTransfer


- -

7 Active data transfer is continued on cell 1

- P






q-Rxlevmin -40

}

}





}

}


3.7. UMTS to LTE Redirection: Test 2501

Network redirects UE from UMTS R99 to LTE through “RRC Connection Release”, active data transfer resumed on LTE

3.7.1. Test Purpose

(1)

with { UE connected to R99 UTRA Cell and is in Connected Mode Cell_FACHstate}

ensure that {

when { UE has active UL and DL data transfer and receives RRC connection release }

then { UE successfully camp on to EUTRAN cell and data transfer is resumed after registration }


References: The conformance requirements covered in the current TC are specified in: TS 25.331, clause 8.5.2.



Cell 5 and Cell 1:



Radio Conditions:



UE:

• None

Preamble:

• UE has both UL and DL active data.




St Procedure Message Sequence TP Verificatio

(UE-NodeB)/(UE-eNB)

eNB-MME

Message

1 The UE is attached on cell 5 and there is an active UL and DL data transfer is on cell 5.

- - - -

2 Network sends RRCConnectionRelease on Cell 5

<-- RRC: RRCConnectionRelease - -



4 Networktransmit an RRCConnectionSetup message.




- -




- -




- -

8 ActiveUL and DL data transfer is continued on cell 1

- P




Table 3-23: RRCConnectionRelease


Release cause Congestion


Network redirects UE from UMTS HSDPA/HSUPA to LTE through “RRC Connection Release”active data transfer resumed on LTE.

3.8.1. Test Purpose

(1)

with { UE connected to HSDPA UTRA Cell and is in RRC Connected Mode Cell_ FACHstate}

ensure that {

when { UE has active data transfer and receives RRC connection release }



References: The conformance requirements covered in the current TC are specified in:TS 25.331 ,clause 8.5.2.



Cell 5 and Cell 1:



Radio Conditions:




UE:

• None

Preamble:

• UE has active data.




UE-eNB

eNB-MME

Message

1 The UE is attached on cell 5 and there is an active UL and DL data transfer is on cell 5

- - - -





4 Networktransmit an RRCConnectionSetup message.




- -




- -




- -

8 Activedata transfer is continued on cell 1

- P





Release cause Congestion

Redirection Information

Frequency info

Inter-RAT Info

Inter-RAT info EUTRA

E-UTRA Target

DL Carrier Frequency EARFCN (DL) Of Cell 1

Physical Cell Identity 1 Cell ID of Cell 1


Network redirects UE from UMTS R99 to LTE through “RRC Connection Release” redirection failed, UE returns to UMTS and resumes data transfer.

3.9.1. Test Purpose

(1)

with { UE connected to R99 UTRA Cell and is in RRC Connected Mode Cell_ FACHstate}

ensure that {


then { UE is unable to camp on the EUTRAN cell , it camps on back to UTRA cell in some time and data transfer is resumed }


References: The conformance requirements covered in the current TC are specified in:TS 25.331, clause 8.5.2.




Cell 5 and Cell 1:



Radio Conditions:



UE:

• None

Preamble:





(UE-NodeB)/(UE-eNB)

eNB-MME

Message


Keep the Cell 1power low.

- - - -



- -

3 The UEis unable totransmit a RRCConnectionRequest message on the Cell 1.

- -

5 The UE transmits an RRC CONNECTION REQUEST message on the cell 5


- -



- -





- -




- -



- -



- -




- -




1 -

13 Active UL and DL data transfer is continued on cell 5

3.10. Stress Testing – LTE-UMTS: Test 2703

UE maintains active data transfer on LTE network for 20 minutes with fading and noise, UMTS network is present.


(1)

with { UE in RRC_connected state in EUTRAN network with active UDP data transfer and UTRAN network also available }

ensure that {

when { in multiple fading and noise conditions}

then { UE is able to maintain connection with EUTRAN network with continuous active data transfer for 20 mins }

}



None (General Stress Testing TC)



Cell 5 and Cell 1:



Radio Conditions:



Introduce fading and noise as shown in the table below.

Test Parameters LTE

Noise SNR = -10

Fading Profile EVA5

TM mode TM2

Data Rate (UL/DL) 8Mbps/37 Mbps

(based on Scheduler Configuration and UE Category)

UE:

• UE is connected to Cell 1

• USIM configuration

USIM Field Priority Value Access Technology

EFPLMNwAcT

EFOPLMNwAcT 1 PLMN2 UTRAN

Preamble:

• PLMN1 is HPLMN. Cell 1 (EUTRAN) belongs to PLMN1.





UE-NodeB

eNB-MME

Message

1 Start data transfer UL – DL UDP and continue it for 20 minutes

1 P

3.10.3.3 Parameter Options

Table 3-28: Parameter Options

Test Parameters LTE Comments

Noise SNR = 0, 10 AWGN is enabled

Fading Profile EPA5, HST

Data Rate (UL(Mbps)/DL(Mbps)) 5/10, 15/25, 20/60 Depending on Cell radio condition and TM mode.

RS EPRE(dBm) -75,-80, -90, -95

PLMN of UTRAN cell (Cell 5) PLMN1 HPLMN

3.11. Stress Testing – LTE-UMTS: Test 2704

UE maintains active data transfer on UMTS network for 20 minutes with fading and noise, LTE network is present.


(1)

with { UE in Cell DCH state in UTRAN network with active UDP data transfer and EUTRAN network also available }

ensure that {

when { in multiple fading and noise conditions}

then { UE is able to maintain connection with UTRAN network with continuous active data transfer for 20 mins }

}


None (General Stress Testing TC).




Cell 5 and Cell 1:



Radio Conditions:



Introduce fading and noise as shown intable below.

Test Parameters UMTS

Noise CPICH_Ec/No = -102.0

Fading Profile PA3

TM mode TM2

Data Rate (UL/DL) .5 Mbps/1 Mbps

(Different TP Value can be used)

UE:

• UE is connected to Cell 1

• USIM configuration

USIM Field Priority Value Access Technology

EFPLMNwAcT

EFOPLMNwAcT 1 PLMN2 EUTRAN

Preamble:

• PLMN1 is HPLMN. Cell 5 (UTRAN) belongs to PLMN1.




UE-NodeB

eNB-MME

Message

1 Start data transfer UL – DL UDP and continue it for 20 minutes

1 P




Test Parameters UMTS Comments

Noise CPICH_Ec/No = 0, 10 AWGN is enabled

Fading Profile PA3, PB3, Case1

CPICH_Ec (dBm) -60, -55,-70

3.12. LTE to UMTS Cell Reselection: Test 2705

(RRC_IDLE). Simultaneously ramp down LTE power(1dB/5sec) and ramp up UMTS power, check for success rate for 30 iterations.


(1)


ensure that {

when { the serving cell power is attenuated at 1dB/5 seconds & non serving cell power is gradually increased}

then { UE reselects the suitable UTRA neighbor cell for 30 such iterations }


References: The conformance requirements covered in the current TC are specified in: TS 36.304, clause 4.1, 4.3, 5.2.1, 5.2.3.2 and 5.3.1. For TS 25.304, clause 5.2.3.2.



Cell 5 and Cell 1:



Radio Conditions:




Introduce fading and noise as shown in table below.

Test Parameters LTE

Noise SNR = -10

Fading Profile High Speed Train

TM mode TM2

UE:

• UE in E-UTRA RRC_IDLE state.

Preamble:

• UE is in state Registered, Idle Mode (state 2) on Cell 1 (serving cell).




UE-NodeB

NodeB-RNC

Message

1a Perform Setup Configuration. Attach the UE to LTE Network (Cell 1), Bring UE to RRC Idle State.

1b Cell power of Cell 1 is attenuated with the rate of 1db/5sec.

- - - -

1c Cell power of Cell 5 is increased gradually (both step 1b and 1c are executed simultaneously)

2 Repeat step 1a and 1b till step 3-10 executes. Capture RSTP level during reselection for each iteration.



- -



- -



- -



NAS: ROUTING

- -



AREA UPDATE REQUEST



- -



- -




- -




1 -

11 Repeat step 1a to 10, 29 more times.

Check for Reselection is successful or not. User can note the Power Levels at which reselection is getting triggered.



Noise SNR = 0, 10 AWGN to be set true.


TM mode TM1,TM2,

Starting RS EPRE(dBm) value for Cell 1 -45,-75,-80,


3.13. UE Reselection from LTE to UMTS Cell: Test 2707

Simultaneously ramp down LTE power(1B/5sec) and ramp up UMTS power, check for success rate for 30 iterations


(1)

with { UE in E-UTRA RRC_Connected state }

ensure that {

when { return to Idle state with the serving cell power is attenuated at 1dB/5 seconds & ramp up of non-serving cell is performed}

then { UE reselects the suitable UTRA neighbor cell for 30 such iterations }


References: The conformance requirements covered in the current TC are specified in: TS 36.304, clause 4.1, 4.3, 5.2.1, 5.2.2, 5.2.3.2 and 5.3.1. For TS 25.304, clause 5.2.3.2.



Cell 5 and Cell 1:



Radio Conditions:

• Cell 1 configured as serving as shown inTable 6-16 for emergency calls only.

• Cell 5 configured as suitable neighbor cell as shown in Table 6-17


Test Parameters LTE

Noise SNR = -10

Fading Profile EVA5

TM mode TM2


UE:

• UE in E-UTRA RRC_CONNECTED state.

Preamble:

• UE is in state Registered, RRC Connected modeon Cell 1 (serving cell)




UE-NodeB

NodeB-RNC

Message

1a UE is in RRC Connection mode on Cell 1and turns to idle state and starts cell reselection.

1b Cell power of Cell 1 is attenuated with the rate of 1db/5sec.

- - - -

1c Power level of Cell5 is increased gradually.(both Step 1b and 1c are executed simultaneously)

Rrc connection release on Cell 1

2 Repeat step 1 till step 3-10 executes.User can capture threshold reading for min, max and avg threshold level throughout iterations.



- -



- -



- -




- -





- -



- -




- -




1 -

11 Repeat step 1a to 10, 29 more times.

Check for reselection is getting triggered or not.



Noise SNR = 0, 10


TM mode TM1,TM2,

Starting Power levelCell 1 -45,-75

3.14. LTE to UMTS(R99) Redirection with Fading and Noise: Test 2709

Note the success rate with 30 iterations.


(1)


ensure that {

when { the serving cell has comparable signal strength against suitable UTRA-R99 neighbor celland UE receives an RRCConnectionRelease message including an IE redirectionInformation with utra-CarrierFreq UTRA frequency

}


then { UE registers on redirected UTRA-R99 neighbor cell and enters RRC_CONNECTED state on UTRA frequency included in IE redirectionInformation & then goes to RRC_Idle state }

}





Cell 1 and Cell 5


• Cell 5 UTRA-R99 is neighboring cell as shown inTable 6-13 and Table 6-15

Radio Conditions:




Test Parameters LTE

Noise SNR = -10

Fading Profile EVA5

TM mode TM2

Data throughput(DL) 37 Mbps

Duplexing FDD

UE:

• None

Preamble:

• The UE is in state Generic RB Established (state 3) on Cell 1. UL and DL active data transfer.





UE-NodeB

NodeB-RNC

Message

1a On NETWORK side re-adjusts the cell-specific reference signal level of Cell 1 so that Srxlev on UE for Cell5 is greater than Cell 1, i.e Cell5 becomes the strongest cell i.e. Suitable Cell condition.

1b Network transmits an RRCConnectionRelease message (IE redirectionInformation including UTRA-CarrierFreq of Cell 5).


1c The UE transmits a RRC CONNECTION REQUEST message on the cell 5


- -



- -



- -




- -



- -



- -




- -

8 The UE transmits a ROUTING AREA UPDATE COMPLETE message and data transfer is resumed.



1 -



9 After 1 min, repeat step 1a to 8, 29 more times and User can note and calculate the redirection success rate.





Fading Profile EPA5,HST

Starting Power Level of Cell 1 -75,-80

3.15. LTE to HSPA/HSUPA Redirection: Test 2711

Test includes Fading and Noise. Note the success rate for 30 iterations.


(1)


ensure that {

when { the serving cell has comparable signal strength compared to a suitable UTRA-R99 neighbor celland UE receives an RRCConnectionRelease message including an IE redirectionInformation with utra-CarrierFreq UTRA frequency

}

then { UE registers on redirected UTRA HSDPA neighbor cell and enters RRC_CONNECTED state on UTRA frequency included in IE redirectionInformation & then goes to RRC_Idle state }

}






Cell 1 and Cell 5


• Cell 5 UTRA-HSDPA cell is neighboring cell as shown inTable 6-13 and Table 6-15

Radio Conditions:




Test Parameters LTE

Noise -10

Fading Profile EVA5

TM mode TM2

Data throughput(UL/DL) 0.5 Mbps/.5 Mbps

Duplexing FDD

UE:

• None

Preamble:

• The UE is in state Generic RB Established (state 3) on Cell 1. UL and DL active data transfer.




UE-NodeB

NodeB-RNC

Message

1a On NETWORK side re-adjusts the power level of Cell 1 and Cell 5 such that both cell falls in suitable cell signal strength. eg. -70 dBm and -65 dBm respectivity.Active data getting pumped.

1b Network transmits an RRCConnectionRelease message




(IE redirectionInformation including UTRA-CarrierFreq of Cell 5).

1c The UE transmits a RRC CONNECTION REQUEST message on the cell 5


- -



- -



- -




- -



- -



- -




- -

8 The UE transmits a ROUTING AREA UPDATE COMPLETE message and data transfer is resumed.



1 -

9 After 1 min, repeat step 1a to 8, 29 more times and User can note and calculate the redirection success rate.




Noise SNR= 0, 10 AWGN to be set true.


TM Mode TM2,



Starting RS EPRE(dBm) value for Cell 1 -75,-80

3.16. Redirection LTE to UMTS: Test 2730

Later UE Reselects the LTE Network.


(1)


ensure that {


then { UE registers on redirected UTRA-R99 neighbor cell and resume the active data transfer after data transfer.Data Transfer is stopped UE is in UTRA Idle state}

}

(2)

with { UE in UTRA IDLE state }

ensure that {

when { the connected UTRA cell becomes non-suitable as cell signal is below threshold and there is a suitable EUTRA neighbor cell available}



References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.8.3, 5.3.12 and TS 36.304, clause 5.2.7 and TS 25.304, clause 4.1, 5.2.3.1 and 5.3.1.



Cell 1 and Cell 5:




Radio Conditions:



UE:

• None

Preamble:





UE-NodeB

NodeB-RNC

Message

The UE is attached with cell 1 and there is an active UL and DL data transfer on Cell 1.

1 Network transmits an RRCConnectionRelease message (IE RedirectionInformation including UTRA-CarrierFreq of Cell 5).




- -


<-- RRC: RRC CONNECTION SETUP - -



- -




- -



- -



- -






- -




1 -

10 Active UL and DL data transferis continued on cell 5.

Stop Data Transfer

11 Network entity, adjusts cell conditions such that Cell 5 becomes Non-Suitable Cell and Cell 1 as suitable cell.

Power measurement configuration can be derived from Table 6-15 and Table 6-16for respective RAT.

- - - -






--> --> RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST

- -




- -




2 -



17 Execute Steps 1-16 thirty times.






c1 CHOICE {




UTRA-FDD

}

}

}





}

}




q-RxLevMin[n] -60

}

}


3.17. Reselection from LTE to UMTS: Test 2731

(RRC_IDLE); later UE is redirected back to LTE Network with active data transfer in progress.


(1)


ensure that {


then { UE selects the suitable UTRA neighbor cell }

(2)


ensure that {


then { UE successfully camp on to EUTRAN cell and data transfer is resumed after registration}


References: The conformance requirements covered in the current TC are specified in: TS 36.304, clause 4.1, 4.3, 5.2.1, 5.2.3.2 and 5.3.1. TS 25.304, clause 5.2.3.2and TS 25.331 clause 8.5.2.



Cell 1 and Cell 5



Radio Conditions:



UE:

• None


Preamble:













UE-NodeB

NodeB-RNC

Message

1 UE is attached on Cell 1, RRC State is Idle.

On NETWORK side re-adjusts the cell-specific reference signal level of Cell 1 so that Srxlev on UE for Cell5 is greater than Cell 1.For instance, Cell5 becomes the strongest cell.

- - - -



- -



- -



- -




- -





- -



- -




- -




1 -

10 The UE is attached on cell 5 and Start an active UL and DL data transferon Cell 5.

- - - -

11 Network sends RRCConnectionRelease on Cell 5.







--> --> RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST

- -




- -






- -

17 ActiveUL and DL data transfer is continued on Cell 1.

2 -

18 Repeat Steps 1-17 twenty-nine times.






q-Rxlevmin -48

}

}





q-RxLevMin[n] -60

}

}


3.18. UE Redirection from UMTS: Test 2732

R99 to LTE Cell with active data transfer. Later UE reselects UMTS Cell.


(1)


ensure that {



(2)

with { UE in E-UTRA RRC_CONNECTED state, , bring UE to RRC Idle State then }

ensure that {

when { the serving cell becomes non-suitable as cell signal is below threshold and there is a suitable UTRA neighbor celland UE receives an RRCConnectionRelease message}

then { UE reselects & registers on the suitable UTRA neighbor cell and enters RRC_IDLE state }

}


References: The conformance requirements covered in the current TC are specified in: TS 25.331, clause 8.5.2 and TS 36.331, clause 5.3.8.3, 5.3.12 and TS 36.304, clause 5.2.7.



Cell 5 and Cell 1:



Radio Conditions:



UE:


• None

Preamble:





(UE-NodeB)/(UE-eNB)

eNB-MME

Message


- - - -









- -




- -




- -

8 Check if activeUL and DL data transfer is continued on Cell 1.

- P



9 On NETWORK side re-adjusts the cell-specific reference signal level of Cell 1 so that Srxlev on UE for Cell5 is greater than Cell 1, i.e Cell5.becomes the strongest cell

10 Network transmits an RRCConnectionRelease message



--> RRC: RRC CONNECTION REQUEST - -





- -




- -


<-- RRC: SECURITY MODE COMMAND - -


--> RRC: SECURITY MODE COMPLETE - -




- -




2 -

19 Repeat Steps 1-18 twenty-nine times








q-Rxlevmin -48

}

}





q-RxLevMin[n] -60

}

}

3.19. UE Reselects from UMTS to LTE: Test 2733

With PS session active on UMTS, UE then get redirected to UMTS.


(1)

with { UE in UTRA IDLE state }

ensure that {

when { the connected UTRA cell becomes non-suitable as cell signal is below threshold and there is a suitable EUTRA neighbor cell available}


(2)


ensure that {


then { UE registers on UTRA-R99 neighbor cell and resume the active data transfer }

}



References: The conformance requirements covered in the current TC are specified in: TS 25.304, clause 4.1, 5.2.3.1 and 5.3.1 and TS 36.331, clause 5.3.8.3, 5.3.12 and TS 36.304, clause 5.2.7.



Cell 5 and Cell 1:



Radio Conditions:



UE:

• None

Preamble:

• UE is in state Registered, UTRA Idle Mode (state 2) on Cell 5 (serving cell).




UE-eNB

eNB-MME

Message

1 Network entity adjusts cell conditions such that Cell 5 becomes a Non-Suitable cell and Cell 1 as a suitable cell.

Power measurement configuration can be derived from Table 6-15 and Table 6-15 for respective RAT.

- - - -









- -




- -




1 -

7 The UE is attached with cell 1 and there is an active UL and DL data transfer on Cell 1.



9 The UE transmits a RRC CONNECTION REQUEST message on Cell 5.

--> RRC: RRC CONNECTION REQUEST - -





- -




- -




<-- RRC: SECURITY MODE COMMAND - -


--> RRC: SECURITY MODE COMPLETE - -




- -




1 -

17 Active UL and DL data transferis continued on Cell 5.

18 Repeat Steps 1-17 five times.






q-Rxlevmin -40

}

}





}

}




q-RxLevMin[n] -60

}



}

4. CS8-LTE to UMTS-ENH-TS

4.1. LTE to UMTS: Test 2302

The following sections provide information on the LTE to UMTS: Active Handover with Measurement Gap Test 2302.

4.1.1. Test Purpose

(1)

with { UE in E-UTRA RRC_CONNECTED state and UE detects entering condition for the event B2 is met }

ensure that {

when { UEreceives a MobilityFromEUTRACommand messageand a DPCH PS RAB combination is configured for an UTRA cell}

then { UE transmits a HANDOVER TO UTRAN-R99 COMPLETE messageon the utra cell in response to this UE transmits UTRAN MOBILITY INFORMATION CONFIRM message and and UE sends MeasurementReport message at regular intervals for the available UTRA cells }

}




4.1.3.1 Pre-Test Conditions

Setup Configuration:

• Cell 1 and Cell 5

• Cell 1 EUTRA serving E-UTRA cell as per Table C-10

• Cell 5 UTRA-R99 cell is neighboring cell as per Table C-13 and Table C-14

• AS-security has been activated and SRB2 with at least one DRB is available on Cell1

Radio Conditions:

• Cell 1 to be configured as serving as per Table C-15

Chapter Four: CS8-LTE to UMTS-ENH-TS | 125

• Cell 5 to be configured as suitable neighbor cell as per Table C-16

System information combination 4 as defined below


Combination No.

SIB2 SIB3 SIB4 SIB5 SIB6 SIB7 SIB8 SIB9 SIB10

SIB11

SIB13

4 X X X

UE:

• None

Preamble:

• The UE is in state Generic RB Established (state 3) on cell 1.



St

Procedure Message Sequence TP Verification

UE-eNB /RNC

eNB /RNC –MME/SGSN

Message

- Network configures UTRA cell 5 to reference configuration according Table C-17, condition UTRA PS RB.

- - - -

1 Check: Does the UE transmit a MeasurementReport message to perform periodical reporting for Cell 5?

--> MeasurementReport - -

2 The network transmits a MobilityFromEUTRACommand message on Cell 1.

<-- MobilityFromEUTRACommand

- -

3 Check: Does the UE transmit a HANDOVER TO UTRAN COMPLETE message on cell 5?

--> HANDOVER TO UTRAN COMPLETE

- -


St


4 The network transmits a SECURITY MODE COMMAND message on Cell 5 in order to activate integrity protection.

<-- SECURITY MODE COMMAND

- -

5 The UE transmits a SECURITY MODE COMPLETE message on Cell 5.

--> SECURITY MODE COMPLETE

- -

6 The network transmits an UTRAN MOBILITY INFORMATION message to notify CN information on Cell 5.

<-- UTRAN MOBILITY INFORMATION

- -

7 The UE transmits an UTRAN MOBILITY INFORMATION CONFIRMmessage on Cell 5.

--> UTRAN MOBILITY INFORMATION CONFIRM

1 -


Table 4-2: MobilityFromEUTRACommand

Information Element Value/remark Comment Condition

MobilityFromEUTRACommand ::= SEQUENCE {


c1 CHOICE{

mobilityFromEUTRACommand-r8SEQUENCE {

purpose CHOICE {

handoverSEQUENCE {

targetRAT-Type utra

targetRAT-MessageContainer HANDOVER TO UTRAN COMMAND

nas-SecurityParamFromEUTRA The 4 least significant bits of the NAS downlink COUNTvalue

systemInformation Not present

}

}

}

}


}

}

Table 4-3: HANDOVER TO UTRAN COMMAND

Refer to Table B.17, condition UTRA PS RB

Table 4-4: UTRAN MOBILITY INFORMATION

Information Element Value/remark

CN information info

- PLMN identity

- MCC 001

- MNC 01

- CN common GSM-MAP NAS system information 00 01H

- CN domain information list full

- CN domain identity PS

- CN domain specific NAS system information 01 00H

- DRX cycle length coefficient 7

- CN domain identity CS

- CN domain specific NAS system information 1E 01H


Table 4-5: MeasurementReport


MeasurementReport ::= SEQUENCE {


c1 CHOICE {

measurementReport-r8 SEQUENCE {

measResults ::= SEQUENCE {

measId 1

measResultServCell ::= SEQUENCE { Report Cell 1

rsrpResult (0..97)

rsrqResult (0..34)

}

measResultNeighCells CHOICE {

measResultListUTRA ::= SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

physCellId[1] CHOICE {

Fdd physicalCellIdentity – Report Cell 5 UTRA-FDD



Cell 5

Tdd physicalCellIdentity – Cell 5

Report Cell 5 UTRA-TDD

}

measResult [1] ::= SEQUENCE {

utra-RSCP (-5..91) UTRA-TDD

utra-EcN0 (0..49) UTRA-FDD

}

}

}

}

}

}

}


This section provides information on the LTE to UMTSActive Handover with Measurement Gap Test: 2304.

4.2.1. Test Purpose

(1)


ensure that {

when { UEreceives a MobilityFromEUTRACommand message and a DPCH and HS-PDSCH PS RAB combination is configured for an UTRA cell}

then { UE transmits a HANDOVER TO UTRAN COMPLETE message on the utra-HSPA cell in response to this UE transmits UTRAN MOBILITY INFORMATION CONFIRM message and UE sends MeasurementReport message at regular intervals for the available UTRA cells }

}





4.2.3.1 Pre-test Conditions




• Cell 5 UTRA-HSDPA cell is neighboring cell as per Table C-13 and Table C-14


Radio Conditions:



• System information combination 4 as defined below



SIB11

SIB13

4 X X X

UE:

• None

Preamble:




St


UE-eNB /RNC


Message

- Network configures UTRA-HSDPA cell 5 to reference configuration according Table C-17, condition UTRA HSDPA RB.

- - - -


St



--> MeasurementReport



- -



- -



- -



- -



- -



1 -






c1 CHOICE{


purpose CHOICE {

handoverSEQUENCE {



targetRAT-Type utra




}

}

}

}

}

}


Refer Table B.17, condition UTRA HSDPA RB



CN information info

- PLMN identity

- MCC 001

- MNC 01










This section provides information on the LTE to UMTS Active Handover without Measurement Gap Test: 2301.


4.3.1. Test Purpose

(1)


ensure that {

when { UEreceives a MobilityFromEUTRACommand messageand a DPCH and HS-PDSCH PS RAB combination is configured for an UTRA cell}

then { UE transmits a HANDOVER TO UTRAN COMPLETE messageon the utra-HSDPA cell in response to this UE transmits UTRAN MOBILITY INFORMATION CONFIRM message }

}










Radio Conditions:






SIB11

SIB13

4 X X X

UE:

• None

Preamble:





St


UE-eNB /RNC


Message

1 Network configures UTRA cell 5 to reference configuration according Table C-17, condition UTRA HSDPA RB.

- - - -



- -



- -



- -



- -



- -



1 -








c1 CHOICE{


purpose CHOICE {

handoverSEQUENCE {

targetRAT-Type utra




}

}

}

}

}

}


Refer Table B.17, condition UTRA HSDPA RB



CN information info

- PLMN identity

- MCC 001

- MNC 01










4.4. LTE to UMTS Test: 2308

This section provides information on the LTE to UMTS Active Handover without Measurement Gap Test: 2308.

4.4.1. Test Purpose

(1)


ensure that {

when { UEreceives a MobilityFromEUTRACommand messageand a DPCH and HS-PDSCH PS RAB combination is configured for an UTRA cell and before timer T304 expires UE re-establishes RRC connection to E-UTRAN}

then { After successful RRC connection UE resume the active data transfer }

}


References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.4.3.3, clause 5.4.3.5







• AS-security has been activated and SRB2 with at least one DRB is available on Cell1.

Radio Conditions:



System information combination 4 as defined below.



SIB11

SIB13

4 X X X


UE:

- None

Preamble:

- The UE is in state Generic RB Established (state 3) on cell 1.




UE-eNB /RNC


Message

1 Network configures UTRA cell 5 to reference configuration according Table C-17, condition UTRA HSDPA RB.

- - - -



- -

3 Before T304 timeout UE transmits a RRCConnectionReestablishmentRequest message on the cell 1.

--> RRC: RRCConnectionReestablishmentRequest

- -

4 Network transmit an RRCConnectionReestablishment message.

<-- RRC: RRCConnectionReestablishment

- -

5 The UE transmits a RRCConnectionReestablishmentComplete message to confirm the successful completion of the connection establishment anda TRACKING AREA UPDATE REQUESTmessage is sent to update the registration of the actual tracking area.

--> RRC: RRCConnectionReestablishmentComplete

NAS: TRACKING AREA UPDATE REQUEST

- -



6 The Network transmits a NAS SECURITY MODE COMMAND message to activate NAS security



- -




- -




- -




1 -






c1 CHOICE{


purpose CHOICE {

handoverSEQUENCE {

targetRAT-Type utra




}

}

}



}

}

}

4.5. LTE to UMTS Active Handover with Fading: Test 2713

4.5.1. Test Purpose

(1)

with { UE in E-UTRA RRC_CONNECTED state on Cell 1 and serving cell is in noise and fading condition}

ensure that {

when { UEreceives a MobilityFromEUTRACommand messageand a DPCH PS RAB combination is configured for an UTRA cell}

then { The UE must perform handover from EUTRAN to UTRAN in all such 30 iterations}

}






- Cell 1 and Cell 5

Cell 1 EUTRA serving E-UTRA cell as per Table C-10

Cell 5 UTRA-R99 cell is neighboring cell as per Table C-13 and Table C-14

- Radio Conditions:

Cell 1 to be configured as serving as per Table C-15

Cell 5 to be configured as suitable neighbor cell as per Table C-16

- Introduce fading and noise as per table below:


Test Parameters LTE

Noise SNR = -10

Fading Profile EPA5

TM mode TM1


Duplexing FDD

UE:

- None

Preamble:

The UE is in state Generic RB Established (state 3) on cell 1. active data transfer.



St


UE-eNB /RNC


Message

1 Network configures cell condition such that cell 5 becomes suitable cell and cell 1 becomes non suitable cell

Power measurement configuration can be derived from Table C-15 and Table C-16 for respective RAT.

2 The network transmits a MobilityFromEUTRACommand messageto Cell 1.

<-- RRC:MobilityFromEUTRACommand

3 The UE transmit a HANDOVER TO UTRAN COMPLETE messagetocell 5

--> RRC: HANDOVER TO UTRAN COMPLETE


<-- RRC:SECURITY MODE COMMAND

5 The UE transmits a SECURITY --> RRC:SECURITY MODE


St


MODE COMPLETE messageto Cell 5.

COMPLETE

6 The network transmits an UTRAN MOBILITY INFORMATION message to notify CN information to Cell 5.

<-- RRC:UTRAN MOBILITY INFORMATION

7 The UE transmits an UTRAN MOBILITY INFORMATION CONFIRMmessageto Cell 5. And data is resumed.

--> RRC:UTRAN MOBILITY INFORMATION CONFIRM

1

8 Configure system as per Setup configuration step in this test case.

Repeat step from 1-7, 29 more times to calculate handover success rate.




Noise SNR = 0, 10

Fading Profile EVA5, EVA70

TM mode TM2,TM3,TM4

Starting RS EPRE(dBm) value for Cell 1 -75,-80, -90, -95

Table 4-18: Message Parameter Options




CPICH_Ec (dBm) -60, -55,-70


4.6. LTE to UMTS Active Handover with Fading: Test 2716

4.6.1. Test Purpose

(1)

with { UE in E-UTRA RRC_CONNECTED state on Cell 1 with noise and fading condition }

ensure that {

when { received power level from the EUTRAN cell decreases and event B2 fires, UE send the measurement report and receives a MobilityFromEUTRACommand message }

then { Then UE must perform handover from EUTRAN to UTRAN in all such 30 iterations }

}


References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.4.3.3, 5.5.4.8.




- Cell 1 and Cell 5


Cell 5 UTRA cell is neighboring cell as per Table C-13 and Table C-14

- Radio Conditions:




Test Parameters LTE

Noise SNR = -10

Fading Profile EPA5

TM mode TM1


Duplexing FDD


UE:

- None

Preamble:

- The UE is in state Generic RB Established (state 3) on cell 1. active data transfer.



St


UE-eNB /RNC


Message



2 The UE transmits measurement report after event B2 is fired to Cell 1

--> RRC:Measurement Report



4 The UE transmit a HANDOVER TO UTRAN COMPLETE message on cell 5

--> RRC:HANDOVER TO UTRAN COMPLETE




--> RRC:SECURITY MODE COMPLETE

7 The network transmits an UTRAN MOBILITY



St


INFORMATION message to notify CN information on Cell 5.



1

9 Configure system as per SetUP configuration step in this test case.

Repeat step from 1-8, 29 more times to calculate handover success rate




Noise SNR = 0, 10

Fading Profile EVA5, EVA70

TM mode TM2,TM3,TM4






CPICH_Ec (dBm) -60, -55,-70

4.7. LTE to HSPA+ Redirection with Measurement Gap: Test 2206

4.7.1. Test Purpose

(1)

with { UE in E-UTRA RRC_CONNECTED state and a Measurement Report message for a configured periodic measurement reporting of UTRA-HSPA+ cells on a configured frequency were sent }

ensure that {


when { A previously reported cell become unavailable or the UE receives reference signal power on a reported UTRA frequency for a cell which was previously not reported and UE receives an RRCConnectionRelease message including an IE redirectionInformation with utra-CarrierFreq UTRA frequency }

then { UE selects the suitable UTRA-HSPA+ neighbour cell and resume the active data transfer and UE sends MeasurementReport message at regular intervals for the available UTRA cells }

}


References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.8.3, 5.3.12 and TS 36.304, clause 5.2.7, TS 36.331, clause 5.5.4.1, 5.5.4.8 and 5.5.5.




- Cell 1 and Cell 5


Cell 5 UTRA-HSPA+ cell is neighboring cell as per Table C-13 and Table C-14

- Radio Conditions:



UE:

- None

Preamble:





UE-eNB /RNC


Message



-

The UE is attached on cell 1 and there is an active data transfer is on cell 1.


--> MeasurementReport - -





- -



- -



- -




- -



- -



- -




- -




1 -



11 Active data transfer is continued on cell 5.






c1 CHOICE {



utra-FDD 9800(Downlink UARFCN of cell 5)

UTRA-FDD

}

}

}





}

}




q-RxLevMin[n] -60

}

}

Table 4-26: Measurement Report


MeasurementReport ::= SEQUENCE {


c1 CHOICE {

measurementReport-r8 SEQUENCE {



measResults ::= SEQUENCE {

measId 1

measResultServCell ::= SEQUENCE { Report Cell 1

rsrpResult (0..97)

rsrqResult (0..34)

}

measResultNeighCells CHOICE {

measResultListUTRA ::= SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

physCellId[1] CHOICE {

fdd physicalCellIdentity – Cell 5

Report Cell 5 UTRA-FDD

tdd physicalCellIdentity – Cell 5

Report Cell 5 UTRA-TDD

}

measResult [1] ::= SEQUENCE {

utra-RSCP (-5..91) UTRA-TDD

utra-EcN0 (0..49) UTRA-FDD

}

}

}

}

}

}

}

4.8. LTE to HSPA+ Redirection with Measurement Gap: Test 2738

4.8.1. Test Purpose

(1)

with { UE in E-UTRA RRC_CONNECTED state and a Measurement Report message for a configured periodic measurement reporting of UTRA-HSPA+ cells on a configured frequency were sent }

ensure that {

when { A previously reported cell become unavailable or the UE receives reference signal power on a reported UTRA frequency for a


cell which was previously not reported and UE receives an RRCConnectionRelease message including an IE redirectionInformation with utra-CarrierFreq UTRA frequency }

then { UE selects the suitable UTRA-HSPA+ neighbour cell and resume the active data transfer and UE sends MeasurementReport message at regular intervals for the available UTRA cells }

}






- Cell 1 and Cell 5



- Radio Conditions:




Test Parameters LTE

Noise SNR = -10

Fading Profile EVA5

TM mode TM1


Duplexing FDD

UE:

- None

Preamble:

- The UE is in state Generic RB Established (state 3) on cell 1with active data transfer on Cell 1





UE-eNB /RNC


Message

1a On NETWORK side re-adjusts the cell-specific reference signal level of Cell 1 so that Srxlev on UE for Cell5 is greater than cell1, i.e Cell 5 becomes the strongest cell i.e. Suitable Cell condition.

1b The UE transmit a MeasurementReport message to perform periodical reporting for Cell 5

--> RRC:MeasurementReport


<-- RRC:RRCConnectionRelease












8 The UE transmits a --> RRC: SECURITY MODE



SECURITY MODE COMPLETE message.

COMPLETE




10 The UE transmits a ROUTING AREA UPDATE COMPLETE message and resumes active data transfer on Cell 5



1

11 After 1 min, repeat step 1a to 10, 29 more times and calculate the redirection success rate.

4.8.3.3 Parameters Options




Fading Profile EPA5, EVA70

TM mode TM2,TM3,TM4

Starting RS EPRE(dBm) value for Cell 1 -60,-70,-80, -90





CPICH_Ec (dBm) -60, -55,-70

4.9. LTE to HSPA+ Handover with Measurement Gap: Test 2310

4.9.1. Test Purpose

(1)


ensure that {


when { UEreceives a MobilityFromEUTRACommand messageand a DPCH and HS-PDSCH PS RAB combination is configured for an UTRA HSPA+ cell}

then { UE transmits a HANDOVER TO UTRAN COMPLETE messageon the UTRA-HSPA + cell in response to this UE transmits UTRAN MOBILITY INFORMATION CONFIRM message and UE sends MeasurementReport message at regular intervals for the available UTRA HSPA+ cells }

}


References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.4.3.3., 5.5.4.8.




- Cell 1 and Cell 5



AS-security has been activated and SRB2 with at least one DRB is available on Cell1

- Radio Conditions:






SIB11

SIB13

4 X X X

UE:

- None

Preamble:





St


UE-eNB /RNC


Message

1 Network configures UTRA-HSPA+ cell 5 to reference configuration according Table C-17, condition UTRA HSPA+ RB.

2 The UE transmits a MeasurementReport message to perform periodical reporting for Cell 5

--> RRC:MeasurementReport













1







c1 CHOICE{


purpose CHOICE {

handoverSEQUENCE {

targetRAT-Type utra




}

}

}

}

}

}

Table 4-32: Handover to UTRAN Command

Refer Table B.17, condition UTRA HSPA+ RB

Table 4-33: UTRAN Mobility Information


CN information info

- PLMN identity

- MCC 001

- MNC 01











4.10. LTE to HSPA+ Handover with Measurement Gap: Test 2740


(1)

with { UE in E-UTRA RRC_CONNECTED state on Cell 1 with noise and fading condition }

ensure that {

when { received power level from the EUTRAN cell decreases and event B2 fires, UE send the measurement report and receives a MobilityFromEUTRACommand message }

then { Then UE must perform handover from EUTRAN to UTRAN HSPA+ in all such 30 iterations }

}






- Cell 1 and Cell 5



- Radio Conditions:





Test Parameters LTE

Noise SNR = -10

Fading Profile EVA5

TM mode TM1


Duplexing FDD

UE:

- None

Preamble:

- The UE is in state Generic RB Established (state 3) with active data transfer on cell 1.



St


UE-eNB /RNC


Message



2 The UE transmits measurement report after event B2 is fired to Cell 1

--> RRC:Measurement Report






St










1

9 Configure system as per SetUP configuration step in this test case.

Repeat step from 1-8, 29 more times to calculate handover success rate




Noise SNR = 0, 10

Fading Profile EPA5, EVA70

TM mode TM2,TM3,TM4






CPICH_Ec (dBm) -60, -55,-70


4.11. LTE to HSPA+: Test 2205

This section provides information on the LTE to HSPA+ Redirection without Measurement Gap Test: 2205.


(1)


ensure that {

when { the serving cell becomes non-suitable as cell signal is below threshold and there is a suitable UTRA-HSPA+ neighbour cell and UE receives an RRCConnectionRelease message including an IE redirectionInformation with utra-CarrierFreq UTRA frequency }

then { UE selects the suitable UTRA-HSPA+ neighbour cell and resume the active data transfer }

}






- Cell 1 and Cell 5


Cell 5 UTRA-HSPA+ cell is neighboring cell as per Table C-13 and Table C-14

- Radio Conditions:



UE:

- None

Preamble:






UE-eNB /RNC


Message

The UE is aattached with cell 1 and there is an active data transfer is on cell 1





- -



- -



- -




- -



- -



- -




- -

8 The UE transmits a ROUTING AREA UPDATE


1 -



COMPLETE message. NAS: ROUTING AREA UPDATE COMPLETE

9 Active data transfer is continued on cell 5.






c1 CHOICE {



utra-FDD 9800 (Downlink UARFCN of cell 5)

UTRA-FDD

}

}

}





}

}




q-RxLevMin[n] -60

}

}


4.12. LTE to HSPA+ Handover without Measurement Gap: Test 2305


(1)


ensure that {

when { UEreceives a MobilityFromEUTRACommand messageand a DPCH and HS-PDSCH PS RAB combination is configured for an UTRA cell}

then { UE transmits a HANDOVER TO UTRAN COMPLETE messageon the utra-HSUPA cell in response to this UE transmits UTRAN MOBILITY INFORMATION CONFIRM message }

}






- Cell 1 and Cell 5


Cell 5 UTRA-HSUPA cell is neighboring cell as per Table C-13 and Table C-14

AS-security has been activated and SRB2 with at least one DRB is available on Cell1

- Radio Conditions:






SIB11

SIB13

4 X X X

UE:


- None

Preamble:




St


UE-eNB /RNC


Message

1 Network configures UTRA cell 5 to reference configuration according Table C-17, condition UTRA HSUPA RB.

- - - -



- -



- -



- -



- -



- -



1 -







c1 CHOICE{


purpose CHOICE {

handoverSEQUENCE {

targetRAT-Type utra




}

}

}

}

}

}


Refer Table B.17, condition UTRA HSUPA RB

Table 4-44: UTRAN Mobility Information


CN information info

- PLMN identity

- MCC 001

- MNC 01











4.13. LTE to HSPA+ Reselection: Test 2104


(1)

with { UE in E-UTRA RRC_IDLE state on Cell 1}

ensure that {

when { the serving cell becomes non-suitable as cell signal is below threshold and there is a suitable UTRA HSPA+ neighbour cell }

then { UE selects the suitable UTRA HSPA+ neighbour cell }


References: The conformance requirements covered in the current TC are specified in: TS 36.304, clause 4.3, 5.2.1, 5.2.3.2 and 5.3.1. TS 25.304, clause 5.2.3.1


Where:

Where:


Qrxlevmeas Measured cell RX level value (RSRP).


Qrxlevminoffset Offset to the signalled Qrxlevmin taken into account in the Srxlev evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN [5]

Pcompensation max(PEMAX – PUMAX, 0) (dB)

PEMAX Maximum TX power level an UE may use when transmitting on the uplink in the cell (dBm) defined as PEMAX in [TS 36.101]

Srxlev > 0

Srxlev = Qrxlevmeas – (Qrxlevmin + Qrxlevminoffset) - Pcompensation


PUMAX Maximum RF output power of the UE (dBm) according to the UE power class as defined in [TS 36.101]


Where:

Squal Cell Selection quality value (dB)

Applicable only for FDD cells.


Qqualmeas Measured cell quality value. The quality of the received signal expressed in CPICH Ec/N0 (dB) for FDD cells. CPICH Ec/N0 shall be averaged as specified in [10]. Applicable only for FDD cells.

Qrxlevmeas Measured cell RX level value. This is received signal, CPICH RSCP for FDD cells (dBm) and P-CCPCH RSCP for TDD cells (dBm).

Qqualmin Minimum required quality level in the cell (dB). Applicable only for FDD cells.


Pcompensation max(UE_TXPWR_MAX_RACH – P_MAX, 0) (dB)

UE_TXPWR_MAX_RACH

Maximum TX power level an UE may use when accessing the cell on RACH (read in system information) (dBm)

P_MAX Maximum RF output power of the UE (dBm)




- Cell 1 and Cell 5



For FDD cells: Srxlev > 0 AND Squal > 0

Squal = Qqualmeas – (Qqualmin + QqualminOffset)

Srxlev = Qrxlevmeas – (Qrxlevmin + QrxlevminOffset) – Pcompensation


- Radio Conditions:



Table 4-45: System Information Combination 4



SIB11

SIB13

4 X X X

Table 4-46: Cell Configuration

Time Instance Power level

RSTP(dBm) Qrxlevmin(dBm) Srxlev(dB)

T1 Cell1 -60 -106 46

Cell5 -95 -79 -16

T2 Cell1 -120 -106 -14

Cell5 -65 -79 14

UE:

- None

Preamble:

- UE is in state Registered, Idle Mode (state 2) on Cell 1 (serving cell).




UE-eNB /RNC


Message

1 Both cell1 and cell 5 is configured as per T1 in above cell configuration table

2 The Network configures power level of cell 1 and cell 5 as per T2 in above cell configuration table .






















1


Table 4-48: SystemInformationBlockType1 for Cell 1




q-Rxlevmin -53

}

}




q-RxLevMin[n] -39

}

}

5. CS8-TS-LTE-IDLE

5.1. Cell Selection Intra E-UTRAN: Test 3601

5.1.1. Test Purpose

(1)

with { UE is in E-UTRA RRC_IDLE mode state on Cell 1}

ensure that {

when { UE detects an intra frequency E-UTRA Cell whose cell power is same as serving cell and meets the condition Sservingcell<=Sintrasearch}

then {UE doesn’t intiate cell reselection to neighboring cell }

}


References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.304, Clause 5.2.3.2, 5.2.4.2




- Cell 1(Table C10) is set to ''Serving cell'' E-UTRA configured as per table C-15

- Cell 2(Table C10) is set to “Neighboring cell “E- UTRA cell as per table C-15

Table 5-1: System Information Combination 2



SIB11

SIB13

2 X X X

Table 5-2: Cell Configuration

Time Instance Power level E-UTRAN




T1 Cell1 -65 -106 41

Cell2 -115 -106 -9

T2 Cell1 -75 -106 31

cell2 -75 -106 31

Cell ranking and cell priority for both cells are the same.

UE:

- The UE is previously registered on E-UTRAN, and when on E-UTRAN, the UE is last authenticated and registered on cell 1.

Preamble:

- The UE is in state E-UTRA RRC_IDLE state on cell 1.




UE-eNB

eNB-MME

Message


2 The Network configures power level of cell 1 and cell 2 as per T2 in above cell configuration table .

3 UE calculates the Srxlev of serving cell and neighbouring cell and meets the condition Sservingcell<=Sintrasearch

4 UE does not transmits RRCConnectionRequest to cell 2





q-RxLevMin -53

q-RxLevMinOffset 0

Chapter Five: CS8-TS-LTE-IDLE | 169


}

p-Max 0

}

}




q-RxLevMin -53

q-RxLevMinOffset 0

}

p-Max 0

}

}




cellReselectionInfoCommon SEQUENCE {

s-IntraSearch 11

}

}


5.2.1. Test Purpose

(1)

with { UE in E-UTRA RRC_IDLE state on cell 1}

ensure that {

when { Serving cell power becomes less and an intra frequency neighboring cell is available with high cell power than serving cell & Sserving cell< Sintrasearch condition is achieved }

then { UE reselects the neighboring cell }

}






Setup Configuration

Cell 1(Table C10) is set as Serving E- UTRA cell as per Table C-15

Cell 2(Table C10) is set as Neighbouring E- UTRA cell as per Table C-15




SIB11

SIB13

2 X X X

UE:

UE is previously registered on E-UTRAN cell & on E-UTRAN UE is configured on Cell 1

Preamble:

UE is in state E-UTRA RRC idle state on cell 1

Cell Configuration



T1 Cell1 -65 -106 41

Cell2 -115 -106 -9

T2 Cell1 -101 -106 5

cell2 -65 -106 41

Cell ranking and cell priority for both cells are same.


Table 7.6.2.1: Main Behavior St Procedure Message Sequence TP Verification

UE-eNB eNB-MME

Message




2 The Network configures power level of cell 1 and cell 2 as same as per T2 in above cell configuration table.

3 UE calculates the Srxlev of serving cell and neighbouring celland meets the condition Sservingcell<Sintrasearch

4 UE transmits RRCConnectionRequest to cell 2

--> RRC:RRCConnectionRequest

5 The Network transmits RRCConnectionSetup message to cell 2.

<-- RRC:RRCConnectionSetup

6 The UE transmits RRCConnectionSetup Complete message and TRACKING AREA UPDATE REQUEST message for registration of actual tracking area

--> --> RRC:RRCConnectionsetupComplete

NAS:TRACKINGAREAUPDATEREQUEST

7 The Network transmits TRACKINGAREAUPDATE ACCEPT MESSAGE ON CELL 2

<-- <-- RRC:DLInformationTransfer

NAS:TRACKINGAREAUPDATEACCEPT

8 TheUE transmits TRACKINGAREAUPDATECOMPLETE message on cell 2

--> --> RRC:ULInformationTransfer

TRACKING AREA UPDATE COMPLETE


Table 7.6.2-2: SystemInformationBlockType1 for cell 1 Information Element Value/remark Comment Condition


q-RxLevMin -53


q-RxLevMinOffset 0

}

p-Max 0

}

}



q-RxLevMin -53

q-RxLevMinOffset 0

}

p-Max 0

}

}

Table 7.6.2-4: SystemInformationBlockType3 for cell1 Information Element Value/remark Comment Condition


cellReselectionInfoCommon SEQUENCE {

s-IntraSearch 11

}

}


5.3.1. Test Purpose

(1)

with { UE is in E-UTRA RRC_IDLE mode state on Cell 1}

ensure that {

when { UE detects cell reselection criteria for inter frequency cell due to power level of serving cell decreases

}

then {UE reselects to suitable neighboring E-UTRA cell2 }

}



References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.304, Clause 5.2.3.2, 5.2.4.2




- Cell 1 and Cell2 as per Table C-11

- Cell1 and Cell2 are on different frequency.




SIB11

SIB13

3 X X X

Cell configuration TI Power Level


T1 Cell 1 -65 -106 41

Cell2 -115 -106 -9

T2 Cell1 -135 -106 -29

Cell2 -65 -106 41

UE:

- The UE is previously registered on E-UTRAN, and when on E-UTRAN, the UE is last authenticated and registered on cell 1 .

Preamble:

- The UE is in state E-UTRA RRC _IDLE state on cell 1.


Table 7.6.3-1: Main Behavior St Procedure Message Sequence TP Verification

UE-eNB

eNB-MME

Message

1 Both cell1 and cell 2 is configured



as per T1 in above cell configuration table

2 The Network configures power level of cell 1 and cell 2 as same as per T2 in above cell configuration table .

3 The Network configures cell condition such that power level of cell 1 decreases and power level of cell 2 increases and meets the condition( Sservingcell<Sintersearch)





6 The UE transmits RRCConnectionSetup Complete message and ROUTING AREA UPDATE REQUEST message for registration of actual ROUTING area

--> --> RRC: RRCConnectionsetupComplete

NAS: TRACKINGAREAUPDATEREQUEST

7 The Network transmits ROUTINGAREAUPDATE ACCEPT MESSAGE ON CELL 2


NAS: TRACKINGAREAUPDATEACCEPT

8 TheUE transmits ROUTINGAREAUPDATECOMPLETE message on cell



9 The Network transmits an RRCConnectionRelease

message to release RRC connection and

move to RRC_IDLE.




SystemInformationBlockType1 ::



SEQUENCE {

q-RxLevMin -53

q-RxLevMinOffset 0

}

p-Max 0

}

}



SEQUENCE {

q-RxLevMin -53

q-RxLevMinOffset 0

}

p-Max 0

}

}

5.4. Cell Reselection: Test 3612

5.4.1. Test Purpose

(1)

with { UE in E-UTRA RRC_IDLE state on Cell 1}

ensure that {

when { UE detects both intra-frequency and equal priority inter-frequency neigbour cell and inter-frequency cell is the highest ranked cell }

then { UE reselects the inter-frequency cell }

}


References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.2.4.5 and 5.2.4.6.





- Cell 1 (Table C10) is set to ''Serving cell'' E-UTRA configured as per table C-15

- Cell 2 (Table C10) is set to “Neighboring E- UTRA cell” as per table C-15

Cell1 and cell2 are on different frequency band.

UE:

- the UE is previously registered on E-UTRAN, and when on E-UTRAN, the UE is last authenticated and registered on cell 1 .

Preamble:

- The UE is in state E-UTRA RRC _IDLE state on cell 1

Cell Configuration

Parameter Cell 1 Cell 2

T1 Cell-specific RS EPRE -65 -115

T2 Cell-specific RS EPRE -135 -65



UE-eNB

eNB-MME

Message

1 UE is in state RRC-IDLE mode on cell 1 as per row T1 of cell configuration table

2 The Network changes the cells power level setting according to the row "T2" as per cell configuration table


--> RRC:RRCConnectionRequest


<-- RRC:RRCConnectionSetup

5 The UE transmits RRCConnectionSetup Complete

--> --> RRC:RRCConnectionsetupC



message and TRACKING AREA UPDATE REQUEST message for registration of actual tracking area

omplete

NAS:TRACKINGAREAUPDATEREQUEST

6 The Network transmits TRACKINGAREAUPDATE ACCEPT MESSAGE ON CELL 2

<-- <-- RRC:DLInformationTransfer

NAS:TRACKINGAREAUPDATEACCEPT

7 TheUE transmits TRACKINGAREAUPDATECOMPLETE message on cell 2

--> --> RRC:ULInformationTransfer

TRACKING AREA UPDATE COMPLETE




SEQUENCE {

q-RxLevMin -53

q-RxLevMinOffset 0

}

p-Max 0

}

}



SEQUENCE {

q-RxLevMin -53

q-RxLevMinOffset 0

}

p-Max 0

}

}

6. CS8-TS-LTE-VOLTE-GSMA

6.1. SIP Registration Procedure: Test 4101

6.1.1. Test Purpose

(1)

with { UE with default bearer established and not registered to IMS network }

ensure that {

when { UE sends an unprotected REGISTER request }

then { IMS Core Network responds with 200 OK and in response UE subscribes to registration event package }

}


References: The conformance requirements covered in the present TC are specified in: TS 24.229, Clause 5.1.1.2.1, 5.1.1.5.1




UE:

- UE is configured to initiate IMS Registration.

- UE must have USIM and ISIM application installed

Preamble:

- UE is attached to the EPC with default bearer established.



UE-IMS Core Request/Response

Chapter Six: CS8-TS-LTE-VOLTE-GSMA | 179


1 UE sends initial registration for IMS services.

--> REGISTER

2 The IMS Core responds with 200 OK. <-- 200 OK

3 UE subscribes to its registration event package.

--> SUBSCRIBE

4 The IMS Core responds SUBSCRIBE with 200 OK

<-- 200 OK

5 The IMS Core sends initial NOTIFY for registration event package, containing full registration state information for the registered public user identity in the XML body

<-- NOTIFY

6 The UE responds the NOTIFY with 200 OK

--> 200 OK


REGISTER (Step 1)

Use the default message “REGISTER” in annex G.1.1 with condition A1 "Initial unprotected REGISTER" with exception Security-Client header

200 OK for REGISTER (Step 2)

Use the default message “200 OK for REGISTER” in annex G.1.3

SUBSCRIBE (Step 3)

Use the default message “SUBSCRIBE for reg-event package” in annex G.1.4

200 OK for SUBSCRIBE (Step 4)

Use the default message “200 OK for SUBSCRIBE” in annex G.1.5

NOTIFY (Step 5)

Use the default message “NOTIFY for reg-event package” in annex G.1.6

200 OK for NOTIFY (Step 6)

Use the default message “200 OK for other requests than REGISTER or SUBSCRIBE” in annex G.3.1


6.2. SIP Registration Procedure: Test 4102

6.2.1. Test Purpose

(1)


ensure that {

when {UE sends an unprotected REGISTER request with ICSI value in Contact or Accept-Contact header }

then { IMS Core Network responds with 200 OK and in response UE subscribes to registration event package }

}


References: The conformance requirements covered in the present TC are specified in: TS 24.229, Clause 5.1.1.2.1




UE:

- UE is configured to Registered with the IMS network

- The UE supports IMS Multimedia Telephony


Preamble:





1 UE sends initial registration for IMS services. UE includes ICSI value in

--> REGISTER



“Contact” or “Accept-Contact” header.



--> SUBSCRIBE


<-- 200 OK


<-- NOTIFY


--> 200 OK


REGISTER (Step 1)

Use the default message “REGISTER” in annex G.1.1 with condition A1 and A4



SUBSCRIBE (Step 5)




NOTIFY (Step 7)





6.3. Authentication/Security: Test 4201

6.3.1. Test Purpose

(1)


ensure that {

when { UE sends an unprotected REGISTER request message with Sec-Agree and IPSec and gets a 401 unauthorized response with Authentication challenge parameter }

then { UE sends REGISTER Message with proper credential and performs successful registration with IMS network }

}


References: The conformance requirements covered in the present TC are specified in: TS 24.229, Clause 5.1.1.2.1, 5.1.1.5.1




UE:

- UE is configured to initiate IMS Registration.


Preamble:





1 UE sends initial registration for IMS services.

--> REGISTER

2 The IMS Core responds with a valid <-- 401 Unauthorized



AKAv1-MD5 authentication challenge and security mechanisms supported by the network.

3 UE completes the security negotiation procedures, sets up a temporary set of SAs and uses those for sending another REGISTER with AKAv1-MD5 credentials.

--> REGISTER



--> SUBSCRIBE


<-- 200 OK


<-- NOTIFY


--> 200 OK


REGISTER (Step 1)

Use the default message “REGISTER” in annex G.1.1 with condition A1 "Initial unprotected REGISTER"

401 Unauthorized for REGISTER (Step 2)

Use the default message “401 Unauthorized for REGISTER” in annex G.1.2

REGISTER (Step 3)

Use the default message “REGISTER” in annex G.1.1 with condition A2 "Subsequent REGISTER sent over security associations"



SUBSCRIBE (Step 5)





NOTIFY (Step 7)





6.4.1. Test Purpose

(1)

with { UE in IMS un-registered state with default bearer established and UE is equipped with UICC card having ISIM application}

ensure that {

when { UE sends an unprotected REGISTER request with IMPI and IMPU and gets a 401 unauthorized response with challenge parameter IMPI,RAND,AUTN}

then { UE sends REGISTER Message with IMPI and Authentication Response and performs successful registration by using IMS AKA with IMS network}

}


References: The conformance requirements covered in the present TC are specified in: TS 24.229, Clause 5.1.1.1A, TS33.203, Clause 6.1, 6.1.1, 8.1




UE:

- UE is configured to initiate IMS Registration


Preamble:






1 UE sends initial registration for IMS services with IMPI and IMPU to IMS Core to perform IMS registration

--> REGISTER

2 The IMS Core responds with a valid AKAv1-MD5 authentication challenge and security mechanisms supported by the network with IMPI,RAND,AUTN in “www-Authenticate” header

<-- 401 Unauthorized

3 UE completes the security negotiation procedures, sets up a temporary set of SAs and uses those for sending another REGISTER with AKAv1-MD5 credentials and IMPI.

--> REGISTER

4 The IMS Core responds with 200 OK.

<-- 200 OK


--> SUBSCRIBE


<-- 200 OK


<-- NOTIFY


--> 200 OK

6.4.3.3 Specific Message content

REGISTER (Step 1)





REGISTER (Step 3)




SUBSCRIBE (Step 5)



Use the default message “200 OK for SUBSCRIBE” in annex G 1.5

NOTIFY (Step 7)

Use the default message “NOTIFY for reg-event package” in annex G 1.6




6.5.1. Test Purpose

(1)

with { UE in IMS un-registered state with default bearer established and UE is equipped with UICC card having USIM and no ISIM application}

ensure that {

when { UE sends an unprotected REGISTER request with IMPI and IMPU which is derived from IMSI and gets a 401 unauthorized response with challenge parameter IMPI,RAND,AUTN}

then { UE sends REGISTER Message with IMPI and Authentication Response and gets 200 Ok final response for successful registration with IMS network}

}


References: The conformance requirements covered in the present TC are specified in: TS 24.229, Clause 5.1.1.1A, C.2, TS33.203, Clause 6.1, 6.1.1, 8.1





UE:

- UE is configured to initiate IMS Registration


Preamble:





1 UE sends initial registration for IMS services with IMPI and IMPU to IMS Core to perform IMS registration

--> REGISTER

2 The IMS Core responds with a valid AKAv1-MD5 authentication challenge and security mechanisms supported by the network with IMPI,RAND,AUTN in “www-Authenticate” header

<-- 401 Unauthorized

3 UE completes the security negotiation procedures, sets up a temporary set of SAs and uses those for sending another REGISTER with AKAv1-MD5 credentials and IMPI.

--> REGISTER



--> SUBSCRIBE


<-- 200 OK

7 The IMS Core sends initial NOTIFY for registration event package, containing full registration state information for the registered public

<-- NOTIFY



user identity in the XML body


--> 200 OK

6.5.3.3 Specific Message content

REGISTER (Step 1)




REGISTER (Step 3)




SUBSCRIBE (Step 5)



Use the default message “200 OK for SUBSCRIBE” in annex G 1.5

NOTIFY (Step 7)

Use the default message “NOTIFY for reg-event package” in annex G 1.6



6.6. Call Establishment and Termination: Test 4301

6.6.1. Test Purpose

(1)

with { UE is in IMS registered state with default bearer established}

ensure that{


when {UE receives INVITE Request(MT Call) from IMS Core and sends 200 OK final response to Core Network }

then { UE correctly performs IMS mobile terminated speech call setup using IMS Multimedia Telephony }

}


References: The conformance requirements covered in the present TC are specified in: TS 24.229, Clause 5.1.4.1, 6.1.3 and TS 26.114 Clause 5.2.1, 6.2.2.1, 7.3.1, 6.2.5




UE

- UE is registered to IMS services


Preamble:





1 UE is successfully Registered with the IMS network and IMS Core sends INVITE with the first SDP offer.

<-- INVITE

2 Make UE accept the speech AMR offer.

3 Optional: The UE responds with a 100 Trying provisional response

--> 100 Trying

4 The UE responds to INVITE with 180 Ringing.

--> 180 Ringing

5 IMS Core shall send PRACK only if the 180 response contains 100rel

<-- PRACK



option tag within the Require header.

6 The UE acknowledges the PRACK with 200 OK.

--> 200 OK

7 The UE responds to INVITE with a 200 OK final response after the user answers the call.

--> 200 OK

8 The IMS Core acknowledges the receipt of 200 OK for INVITE.

<-- ACK

Generate bidirectional voice traffic

9 The IMS Core sends BYE to release the call.

<-- BYE

10 The UE sends 200 OK for the BYE request and ends the call.

--> 200 OK


INVITE (Step 1)

Use the default message “INVITE for MT Call” in annex G.2.9 with the following exceptions:

Header/param Value/remark

Supported

option-tag precondition

Message-body The following SDP types and values.

Session description:

v=0

o=- 1111111111 1111111111 IN (addrtype) (unicast-address for SS)

s=IMS conformance test

c=IN (addrtype) (connection-address for SS)

b=AS:30

Time description:

t=0 0

Media description:

m=audio (transport port) RTP/AVP 97

b=AS:30



b=RS:0

b=RR:2000

Attributes for media:

a=rtpmap:97 AMR/8000/1

a=fmtp:97 mode-change-capability=2; max-red=220

a=ptime:20

a=maxptime:240

Attributes for preconditions:

a=curr:qos local none

a=curr:qos remote none

a=des:qos mandatory local sendrecv

a=des:qos optional remote sendrecv

100 Trying (Step 3)

Use the default message "100 Trying for INVITE" in annex G.2.2.

183 Session Progress (Step 4)

Use the default message "183 Session Progress" in annex G.2.3 with the following exceptions:


Status-Line

Reason-Phrase Not checked

Require


Message-body The following SDP types and values shall be present.


v=0

o=- (sess-id) (sess-version) IN (addrtype) (unicast-address for UE)


c=IN (addrtype) (connection-address for UE) [Note 1]

b=AS: (bandwidth-value)

Time description:

t=0 0

Media description:

m=audio (transport port) RTP/AVP (fmt)





b=RS: (bandwidth-value)

b=RR: (bandwidth-value)


a=rtpmap:(payload type) AMR/8000/1

a=fmtp:(format)

a=inactive


a=curr:qos local none or a=curr:qos local sendrecv



a=des:qos mandatory remote sendrecv

a=conf:qos remote sendrecv

Note 1: At least one "c=" field shall be present.

180 Ringing (step 4)

Use the default message "180 Ringing for INVITE" in annex G.2.6

PRACK (step 5)

Use the default message "PRACK" in annex G.2.4. No content body is included in this PRACK message

200 OK (step 6)

Use the default message “200 OK for other requests than REGISTER or SUBSCRIBE” in annex G.3.1.

200 OK (step 7)

Use the default message "200 OK for other requests than REGISTER or SUBSCRIBE" in annex G.3.1.

ACK (step 8)

Use the default message "ACK" in annex G.2.7.

BYE (step 9)

Use the default message "BYE" in annex G.2.8.

200 OK (step 10)



6.7. Call Establishment and Termination: Test 4302

6.7.1. Test Purpose

(1)

with { UE is in E-UTRAN connected and IMS registered state}

ensure that {

when { UE initiates INVITE request with ICSI value for IMS multimedia telephony service }

then { IMS session successfully gets created.}

}


References: The conformance requirements covered in the present TC are specified in: TS 24.229, Clause 5.1.1.2.1




UE:

- UE is configured to Registered with the IMS network


Preamble:

- UE is attached to the EPC with default bearer established

- There should be Support for IMS Multimedia Telephony




- UE is successfully Registered with the IMS network

1 UE sends INVITE request with SDP offer with ICSI value

--> INVITE



2 IMS Core Network sends 100 trying message to UE to indicate that call setup is in progress

<-- 100 Trying

3 The Core network responds INVITE with 180.

<-- 180 Ringing

4 UE acknowledges the receipt of 180 response by sending PRACK

--> PRACK

5 The Core network responds PRACK with 200 OK.

<-- 200 OK

6 The Core network responds INVITE with 200 OK to indicate that the virtual remote UE had answered the call.

<-- 200 OK

7 The UE acknowledges the receipt of 200 OK for INVITE

--> ACK

Bidirectional Voice traffic

8 The UE releases the call with BYE. --> BYE

9 The Core network sends 200 OK for BYE.

<-- 200 OK


INVITE (Step 1)

Use the default message “INVITE for MO call setup” in annex G.2.1 with the following exceptions and with condition A3:


Via

via-compression comp=sigcomp (optional)

Route

compression-param

comp=sigcomp (optional)

Contact

compression-param


100 Trying for INVITE (Step 2)

Use the default message “100 Trying for INVITE” in annex G.2.2.

180 Ringing for INVITE (Step 3)


Use the default message “180 Ringing for INVITE” in annex G.2.6 with the following exceptions:


Record-Route The Compression parameter is included in the last route parameter

compression-param

comp=sigcomp

PRACK (Step 4)

Use the default message “PRACK” in annex G.2.4 with the following exceptions:


Via


Route The Compression parameter is included in the first route parameter

compression-param


200 OK for PRACK (Step 5)


200 OK for INVITE (Step 6)


ACK (Step 7)

Use the default message “ACK” in annex G.2.7 with the following exceptions:



compression-param


BYE (Step 8)

Use the default message “BYE” in annex G.2.8 with the following exceptions:


Via



compression- comp=sigcomp (optional)



param

200 OK for BYE (Step 9)


7. CS8-TS-LTE-VOLTE-IMTC

7.1. Voice Call: Test 4601

7.1.1. Test Purpose

(1)

with {UE is in IMS registered state with default bearer established}

ensure that{

when { UE sends the INVITE request, containing an initial SDP, to the IMS Core}

then { UE correctly performs IMS mobile originated voice call setup using IMS Multimedia Telephony}

}


References: The conformance requirements covered in the present TC are specified in: TS 24.229, Clause 5.1.2A.1, 5.1.3.1, 6.1.1 and TS 26.114 Clause 5.2.1, 6.2.2.1, 7.3.1




UE



Preamble:

- UE is attached to the EPC with default bearer and dedicated bearer(QCI=1) established.


Table 8.6.1-1: Main Behavior




1 UE is successfully Registered with the IMS network and UE attempt an IMS speech call

2 UE sends INVITE with the first SDP offer.

--> INVITE

3 IMS Core sends a 100 Trying provisional response.

<-- 100 Trying

4 Optional: IMS Core Network sends an SDP answer.(optional)

<-- 183 Session Progress

5 Optional: UE acknowledges and optionally offer a second SDP if a dedicated EPS bearer is established by the network.(present only if 183 is present)

--> PRACK

6 Optional: IMS Core sends a 200 OK against PRACK and answers the second SDP if present.(optional)

<-- 200 OK

7 Optional: step: UE sends a second SDP if a dedicated EPS bearer is established by the network.(optional)

--> UPDATE

8 Optional step: IMS Core sends a 200 OK.(optional)

<-- 200 OK

9 IMS Core sends a 180 Ringing. <-- 180 Ringing

10 UE acknowledges. --> PRACK

11 IMS Core responds PRACK with 200 OK.

<-- 200 OK

12 IMS Core responds INVITE with 200 OK.

<-- 200 OK

13 UE acknowledges. --> ACK

Generate Bidirection Voice Traffic

14 The UE releases the call with BYE --> BYE

15 The IMS Core sends 200 OK for BYE <-- 200 OK


INVITE (Step 2)

Use the default message “INVITE for MO Call” in annex G.2.1 with the following exceptions:

Chapter Seven: CS8-TS-LTE-VOLTE-IMTC | 199

Header/param Value/Remark

Supported




- v=0

- o=- (sess-id) (sess-version) IN (addrtype) (unicast-address for UE)

- s=(session name)

- c=IN (addrtype) (connection-address for UE) [Note 1]

- b=AS: (bandwidth-value)

Time description:

- t= (start-time) (stop-time)

Media description:

- m=audio (transport port) RTP/AVP (fmt)



- b=RS:0

- b=RR:0


- a=rtpmap: (payload type) AMR/8000/1

- a=fmtp: (format) mode-change-capability=2; max-red=220

- a=rtpmap: (payload type) telephone-event

- a=ptime:20

- a=maxptime:240

- a=inactive


- a=curr:qos local none

- a=curr:qos remote none

- a=des:qos mandatory local sendrecv

- a=des:qos optional remote sendrecv






Supported




- v=0

- o=- 1111111111 1111111111 IN (addrtype) (unicast-address for UE)

- s=IMS conformance test

- c=IN (addrtype) (connection-address for SS)

- b=AS:30

Time description:

- t=0 0

Media description:

- m=audio (transport port) RTP/AVP (fmt) [Note 1]

- b=AS:30

- b=RS:0

- b=RR:0


- a=rtpmap: (payload type) AMR/8000/1 [Note 1]

- a=fmtp: (format) mode-change-capability=2; max-red=220 [Note 1]

- a=ptime:20

- a=maxptime:240





- a=des:qos mandatory remote sendrecv

- a=conf:qos remote sendrecv

Note 1: The value for fmt, payload type and format copied from step 2.

PRACK (Step 5)

Use the default message “PRACK” in annex G.2.4 with the exceptions:




Message-body Header optional

Contents if present: The following SDP types and values shall be present.


- v=0

- o=- (sess-id) (sess-version) IN (addrtype) (unicast-address for UE) [Note 2]

- s=(session name)



Time description:

- t=0 0

Media description:




- b=RS: (bandwidth-value)

- b=RR: (bandwidth-value)



- a=fmtp: (format)

- a= sendrecv


- a=curr:qos local sendrecv





Note 2: The sess-version shall been increased.


Use the default message “200 OK for other requests than REGISTER or SUBSCRIBE” in annex G.3.1 with the following exceptions:




Content-Type Header optional

Contents if present:

media-type application/sdp

Content-Length Contents if header Content-Type is present:

Value length of message-body

Message-body Header present if Prack (step 5) contained SDP.

Contents if present: SDP body of the 200 response copied from the received PRACK and modified as follows:

- IP address on "o=" and "c=" lines and transport port on "m=" lines changed to indicate to which IP address and port the UE should start sending the media;


a=curr:qos remote sendrecv

UPDATE (Step 7)

Use the default message “UPDATE” in annex G.2.5 with the following exceptions:


Message-body Same contents as specified in step 5.

200 OK for UPDATE (Step 8)








Message-body SDP body of the 200 response copied from the received UPDATE and modified as follows:







7.2.1. Test Purpose

(1)


ensure that{

when {UE receives INVITE Request from IMS Core and sends 200 OK final response to Core Network }

then { UE correctly performs IMS mobile terminated speech call setup using IMS Multimedia Telephony }

}


References: The conformance requirements covered in the present TC are specified in: TS 24.229, Clause 5.1.4.1, 6.1.3 and TS 26.114 Clause 5.2.1, 6.2.2.1, 7.3.1, 6.2.5




UE



Preamble:

- UE is attached to the EPC with default bearer and dedicated bearer(QCI=1)established.

7.2.4. Test Procedure Sequence





1 UE is successfully Registered with the IMS network and IMS Core sends INVITE with the first SDP offer.

<-- INVITE


3 Optional: The UE responds with a 100 Trying provisional response

--> 100 Trying

4 Optional: The UE sends 183 response reliably with the SDP answer to the offer in INVITE(Optional as per UE specific behavior)

--> 183 Session Progress

5 Optional: IMS Core acknowledges the receipt of 183 response from the UE(present only if 183 is present)

<-- PRACK

6 Optional: UE responds to PRACK with 200 OK.(present if PRACK is present)

--> 200 OK

7 Optional: IMS Core sends an UPDATE with SDP offer indicating SS reserved resources.(Optional)

<-- UPDATE

8 Optional: The UE acknowledges the UPDATE with 200 OK and includes SDP answer to acknowledge its current precondition status.(Optional)

--> 200 OK

9 Optional: The UE responds to INVITE with 180 Ringing.

--> 180 Ringing

10 Optional: IMS Core shall send PRACK only if the 180 response contains 100rel option tag within the Require header.

<-- PRACK

11 Optional: The UE acknowledges the PRACK with 200 OK.

--> 200 OK


--> 200 OK


<-- ACK



<-- BYE

15 The UE sends 200 OK for the BYE --> 200 OK



request and ends the call.


INVITE (Step 1)



Supported




v=0




b=AS:30

Time description:

t=0 0

Media description:


b=AS:30

b=RS:0

b=RR:2000




a=ptime:20

a=maxptime:240








100 Trying (Step 3)





Status-Line


Require




v=0





Time description:

t=0 0

Media description:








a=fmtp:(format)

a=inactive










PRACK (step 5)

Use the default message "PRACK" in annex G.2.4. No content body is included in this PRACK message.

200 OK (Step 6)


UPDATE (step 7)

Use the default message "UPDATE" in annex G.2.5 with the following exceptions:




v=0




b=AS:30

Time description:

t=0 0

Media description:


b=AS:30

b=RS:0

b=RR:2000






a=ptime:20

a=maxptime:240

a=sendrecv


a=curr:qos local sendrecv

a=curr:qos remote none or curr:qos remote sendrecv [Note 1]



Note 1: Use the value (none/sendrecv) received from 183 Session Progress and attribute a=curr:qos local.

200 OK (step 8)

Use the default message "200 OK for other requests than REGISTER or SUBSCRIBE" in annex G.3.1 with the following exceptions:


Content-Type


Content-Length

value length of message-body



v=0





Time description:

t=0 0

Media description:










a=fmtp:(format)

a=sendrecv









PRACK (step 10)


200 OK (step 11)


200 OK (step 12)


ACK (step 13)


BYE (step 14)


200 OK (step 15)




7.3.1. Test Purpose

(1)

with {UE is in IMS registered state with default bearer established}

ensure that{

when { UE sends the INVITE request}

then { UE correctly performs IMS mobile originated voice call with P-access network info header in all request messages and ICSI value in P-Preffered service }

}


References: The conformance requirements covered in the present TC are specified in: TS 24.229, Clause 7.2A.4




UE:


- UE supports MTSI


Preamble:



Table8.6.3-1: Main Behavior St Procedure Message Sequence TP Verification


1 Make the UE attempt an IMS speech call



2 UE sends INVITE with the P-access network info header and ICSI value in its Contact or Accept-Contact header.

--> INVITE

3 IMS Core sends a 100 Trying provisional response.

<-- 100 Trying

4 Optional: IMS Core Network sends an SDP answer.(Optional)

<-- 183 Session Progress

5 Optional: UE acknowledges and optionally offer a second SDP if a dedicated EPS bearer is established by the network.(present only if 183 is sent)

--> PRACK

6 Optional: IMS Core sends a 200 OK and answers the second SDP if present.(present only if PRACK is sent)

<-- 200 OK

7 Optional: UE sends a second SDP if a dedicated EPS bearer is established by the network.(optional)

--> UPDATE

8 Optional: IMS Core sends a 200 OK.(optional)

<-- 200 OK

9 IMS Core sends a 180 Ringing. <-- 180 Ringing

10 UE acknowledges. --> PRACK

11 IMS Core responds PRACK with 200 OK.

<-- 200 OK

12 IMS Core responds INVITE with 200 OK.

<-- 200 OK

13 UE acknowledges. --> ACK


14 The UE releases the call with BYE --> BYE

15 The IMS Core sends 200 OK for BYE <-- 200 OK

NOTE: UE will send P-access network info header in all request message and ICSI value in Contact or Accept Contact or P-Preferred-Services header of initial INVITE message.


INVITE (Step 2)

Use the default message “INVITE for MO Call” in annexG.2.1 with the following exceptions:



Supported

option-tag Precondition



- v=0

- o=- (sess-id) (sess-version) IN (addrtype) (unicast-address for UE)

- s=(session name)



Time description:

- t= (start-time) (stop-time)

Media description:




- b=RS:0

- b=RR:0



- a=fmtp: (format) mode-change-capability=2; max-red=220

- a=rtpmap: (payload type) telephone-event

- a=ptime:20

- a=maxptime:240

- a=inactive











Supported

option-tag Precondition



- v=0

- o=- 1111111111 1111111111 IN (addrtype) (unicast-address for UE)

- s=IMS conformance test

- c=IN (addrtype) (connection-address for SS)

- b=AS:30

Time description:

- t=0 0

Media description:

- m=audio (transport port) RTP/AVP (fmt) [Note 1]

- b=AS:30

- b=RS:0

- b=RR:0


- a=rtpmap: (payload type) AMR/8000/1 [Note 1]

- a=fmtp: (format) mode-change-capability=2; max-red=220 [Note 1]

- a=ptime:20

- a=maxptime:240





- a=des:qos mandatory remote sendrecv

- a=conf:qos remote sendrecv

Note 1: The value for fmt, payload type and format copied from step 2.

PRACK (Step 5)

Use the default message “PRACK” in annex G.2.4 with the exceptions:




Message-body Header optional

Contents if present: The following SDP types and values shall be present.


- v=0

- o=- (sess-id) (sess-version) IN (addrtype) (unicast-address for UE) [Note 2]

- s=(session name)



Time description:

- t=0 0

Media description:




- b=RS: (bandwidth-value)

- b=RR: (bandwidth-value)



- a=fmtp: (format)

- a= sendrecv


- a=curr:qos local sendrecv





Note 2: The sess-version shall been increased.










Message-body Header present if Prack (step 5) contained SDP.

Contents if present: SDP body of the 200 response copied from the received PRACK and modified as follows:




UPDATE (Step 7)

Use the default message “UPDATE” in annex G.2.5 with the following exceptions:


Message-body Same contents as specified in step 5.

200 OK for UPDATE (Step 8)








Message-body SDP body of the 200 response copied from the received UPDATE and modified as follows:






BYE (Step 14)

Use the default message “BYE” in annex G 2.8.

200 OK for BYE (Step 15)



7.4.1. Test Purpose

(1)


ensure that{

when {UE receives INVITE Request from IMS Core and sends 200 OK final response to Core Network. }

then { UE correctly performs IMS mobile terminated speech call setup using IMS Multimedia Telephony and includes an IMEI URN "+sip.instance" in the contact header of REGISTER Request}

}


References: The conformance requirements covered in the present TC are specified in: TS 23.003, Clause 13.8




UE:

- UE is configured to initiate IMS Registration.- UE must have USIM and ISIM application installed

Preamble:






1 The UE sends REGISTER Request to IMS Core for initial registration containing “+ sip.instance” URN in contact header field

--> REGISTER

2 The IMS Core sends 200 ok final response to UE for successfully registered with IMS Core

<-- 200 OK

3 IMS Core sends INVITE with the first SDP offer.

<-- INVITE


5 Optional) The UE responds with a 100 Trying provisional response

--> 100 Trying

6 Optional: The UE sends 183 response reliably with the SDP answer to the offer in INVITE(optional)

--> 183 Session Progress

7 Optional: IMS Core acknowledges the receipt of 183 response from the UE(present if 183 should be reliably acknowledged).

<-- PRACK

8 Optional: UE responds to PRACK with 200 OK.(present if PRACK is available)

--> 200 OK

9 Optional: IMS Core sends an UPDATE with SDP offer indicating SS reserved resources.(optional)

<-- UPDATE

10 Optional: The UE acknowledges the UPDATE with 200 OK and includes SDP answer to acknowledge its current precondition status.(optional)

--> 200 OK

11 Optional: The UE responds to INVITE with 180 Ringing.

--> 180 Ringing

12 Optional: IMS Core shall send PRACK only if the 180 response contains 100rel option tag within the Require header.

<-- PRACK

13 Optional: The UE acknowledges the PRACK with 200 OK.

--> 200 OK




--> 200 OK


<-- ACK

Generate birectional Voice traffic


<-- BYE

17 The UE sends 200 OK for the BYE request and ends the call.

--> 200 OK


REGISTER (Step 1)

Use the default message “REGISTER” in annex G.1.1 with condition A1 and A5 "Initial unprotected REGISTER" with exception Security-Client header



INVITE (Step 3)



Supported




v=0




b=AS:30

Time description:

t=0 0

Media description:




b=AS:30

b=RS:0

b=RR:2000




a=ptime:20

a=maxptime:240






100 Trying (Step 5)





Status-Line


Require




v=0





Time description:



t=0 0

Media description:








a=fmtp:(format)

a=inactive








PRACK (step 7)

Use the default message "PRACK" in annex G.2.4. No content body is included in this PRACK message.

200 OK (Step 8)


UPDATE (step 9)

Use the default message "UPDATE" in annex G.2.5 with the following exceptions:




v=0






b=AS:30

Time description:

t=0 0

Media description:


b=AS:30

b=RS:0

b=RR:2000




a=ptime:20

a=maxptime:240

a=sendrecv



a=curr:qos remote none or curr:qos remote sendrecv [Note 1]



Note 1: Use the value (none/sendrecv) received from 183 Session Progress and attribute a=curr:qos local.

200 OK (step 10)

Use the default message "200 OK for other requests than REGISTER or SUBSCRIBE" in annex G.3.1 with the following exceptions:


Content-Type


Content-Length






v=0





Time description:

t=0 0

Media description:








a=fmtp:(format)

a=sendrecv









PRACK (step 12)


200 OK (step 13)



200 OK (step 14)


ACK (step 15)


BYE (step 16)


200 OK (step 17)


8. Appendix A

8.1. Generic Test Procedure

8.1.1. UE Registration Procedure

Table 8-1: UE Registration Procedure

Step Procedure Message Sequence

UE-eNB

eNB-MME

Message







-->

-->


NAS: ATTACH REQUEST



<--

<--



6 The UE transmits an AUTHENTICATION RESPONSE message and establishes mutual authentication.

-->

-->



7 The Network transmits a NAS SECURITY MODE COMMAND message to activate NAS security.

<--

<--



Chapter Eight: Appendix A | 225



-->

-->



- EXCEPTION: Steps 9a and 9b describe behavior that depends on UE configuration;the “lower case letter” identifies a step sequence that take place if the UE has ESM information that needs to be transferred.

- -

9a If the UE sets the ESM information transfer flag in the last PDN CONNECTIVITY REQUEST message THEN the Network transmits an ESM INFORMATION REQUEST message to initiate exchange of protocol configuration options and/or APN.

<--

<--


NAS: ESM INFORMATION REQUEST

9b The UE transmits an ESM INFORMATION RESPONSE message to transfer protocol configuration options and/or APN.

-->

-->


NAS: ESM INFORMATION RESPONSE

10 The Network transmits a SecurityModeCommand message to activate AS security.

<-- RRC: SecurityModeCommand

11 The UE transmits a SecurityModeComplete message and establishes the initial security configuration.

--> RRC: SecurityModeComplete







14 The Network transmits an RRCConnectionReconfiguration message to establish the default bearer with condition SRB2-DRB(1, 0) according to 4.8.2.2.1.1.

This message includes the ATTACH ACCEPT message. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT.

<--

<--


NAS: ATTACH ACCEPT


15 The UE transmits an RRCConnectionReconfigurationComplete

message to confirm the establishment of default bearer.


- EXCEPTION: In parallel to the event described in Step 16 below, if initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.508 sub clause 4.5A.1 takes place performing IP address allocation in the U-plane.

- EXCEPTION: In parallel to the event described in step 16 below the generic procedure for IMS signaling in the U-plane specified in TS 36.508 sub clause 4.5A.3 takes place if requested by the UE


-->

-->







8.1.2. UE Registration with Test Mode Activation

Table 8-2: UE Registration with Test Mode Activation Procedure


UE-eNB

eNB-MME

Message

1 to 9a2

Same procedure for steps 1 to 9a2 as specified in the procedure in clause 4.5.2.3

- -

10 The Network transmits an ACTIVATE TEST MODE message to activate UE radio bearer test mode procedure.


TC: ACTIVATE TEST MODE

11 The UE transmits an ACTIVATE TEST MODE COMPLETE message.


TC: ACTIVATE TEST MODE COMPLETE









16 The Network transmits an RRCConnectionReconfiguration message to establish the default bearer with condition SRB2-DRB(1, 0) according to 4.8.2.2.1.1.

This message includes the ATTACH ACCEPT message. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT.

<--

<--


NAS: ATTACH ACCEPT


17 The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of default bearer.




- EXCEPTION: In parallel to the event described in step 18 below the generic procedure for IP address allocation in the U-plane specified in TS 36.508 sub clause 4.5A.1 takes place performing IP address allocation in the U-plane if requested by the UE.

- EXCEPTION: In parallel to the event described in step 18 below the generic procedure for IMS signaling in the U-plane specified in TS 36.508 sub clause 4.5A.3 takes place if requested by the UE


-->

-->




19 The Network transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE (State 2A).


8.1.3. Generic Radio Bearer Establishment

Table 8-3: Generic Radio Bearer Establishment Procedure


UE-eNB

eNB-MME

Message


2 Network sends a Paging message to the UE on the appropriate paging block, and including the UE identity in one entry of the IE pagingRecordLists.

<-- RRC: Paging (PCCH)



4 Network transmit an RRCConnectionSetup message.




5 The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message. (State3)

-->

-->


NAS: SERVICE REQUEST





8 The Network configures a new data radio bearer, associated with the default EPS bearer context.

If the test case using state 3 as an initial state is using N additional data radio bearers (0 ≤ N ≤ 7), the RRCConnectionReconfiguration message contains the configuration of these additional data radio bearers in the drb-ToAddModify IE and one ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message per additional data radio bearer.

The RRCConnectionReconfiguration message is using condition SRB2-DRB(1+n, m) where n and m are the number of DRBs associated with dedicated EPS bearer contexts and configured respectively withRLC-AM and RLC-UM (n+m = N).

<--

<--


NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

...

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

- EXCEPTION: the steps 9 and 10a1 to 10a3 (if present) happen in any order.

- -

9 The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the default EPS bearer context.




10a If N ≥ 1 (refer to Step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 1st ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in Step 8.

-->

-->


NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

10b If N ≥ 2 (refer to Step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 2nd ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in Step 8.

-->

-->



10c If N ≥ 3 (refer to Step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 3rd ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in Step 8.

-->

-->



10d If N ≥ 4 (refer to Step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 4th ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in Step 8.

-->

-->



10e If N ≥ 5 (refer to Step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 5th ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in Step 8.

-->

-->



10f If N ≥ 6 (refer to Step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 6th ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in Step 8.

-->

-->



10g If N = 7 (refer to Step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 7th ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in Step 8.

-->

-->




8.1.4. Tracking Area Update

Table 8-4: Tracking Area Updating Procedure


UE-eNB eNB-MME

Message

1 The Network transmits system information on the cell specified in the test case.

<-- RRC: SYSTEM INFORMATION (BCCH)

2 The UE transmits an RRCConnectionRequest message on the cell specified in the test case.


3 Network transmits an RRCConnectionSetup message.


4 The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and a TRACKING AREA UPDATE REQUEST message is sent to update the registration of the actual tracking area.

-->

-->

RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST


<--

<--



6 The UE transmits a TRACKING AREA UPDATE COMPLETE

-->

-->



7 The Network transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE.


9. Appendix B

9.1. RRC and NAS Messages with Default Parameters

9.1.1. RRCConnectionRequest

Table 9-1: RRCConnectionRequest


RRCConnectionRequest ::= SEQUENCE {


rrcConnectionRequest-r8 SEQUENCE {

FDD

establishmentCause mt-Access TDD

}

}

}

Condition Explanation Condition Explanation

FDD FDD cell environment FDD FDD cell environment

TDD TDD cell environment TDD TDD cell environment

9.1.2. RRCConnectionSetup

Table 9-2: RRCConnectionSetup


RRCConnectionSetup ::= SEQUENCE {

rrc-TransactionIdentifier RRC-TransactionIdentifier-DL


c1 CHOICE {

rrcConnectionSetup-r8 SEQUENCE {

Chapter Nine: Appendix B | 233


radioResourceConfigDedicated RadioResourceConfigDedicated-SRB1

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

9.1.3. RRCConnectionSetupComplete

Table 9-3: RRCConnectionSetupComplete


RRCConnectionSetupComplete ::= SEQUENCE {

rrc-TransactionIdentifier RRC-TransactionIdentifier-UL


c1 CHOICE {

rrcConnectionSetupComplete-r8 SEQUENCE {

selectedPLMN-Identity 1

registeredMME Not checked

dedicatedInfoNAS Present but contents not checked


Not checked

}

}

}

}

9.1.4. RRCConnectionReconfiguration








c1 CHOICE{


measConfig Not present

MeasConfig-DEFAULT

MEAS

mobilityControlInfo Not present

MobilityControlInfo-HO

HO, HO-TO-EUTRA

dedicatedInfoNASList Not present

Set according to specific message content

SRB2-DRB(n, m)

DRB(n, m)

SRB1-SRB2-DRB(n,m)

AM-DRB-ADD(bid)

UM-DRB-ADD(bid)

DRB-REL(bid)

DRB-Mod

radioResourceConfigDedicated Not present

RadioResourceConfigDedicated-SRB2-DRB(n, m)

RadioResourceConfigDedicated-DRB(n, m)

RadioResourceConfigDedicated-AM-DRB-ADD(bid)

RadioResourceConfigDedicated-UM-DRB-ADD(bid)

RadioResourceConfigDedicated-DRB-REL(bid)

RadioResourceConfigDedicated-HO

RadioResourceConfigDedicated-HO-TO-EUTRA(n, m)

RadioResourceConfigDedicated-

SRB2-DRB(n, m)

DRB(n, m)

AM-DRB-ADD(bid)

UM-DRB-ADD(bid)

DRB-REL(bid)

HO

HO-TO-EUTRA(n,m)

DRB-Mod



DRB-Mod

securityConfigHO Not present

SecurityConfigHO-DEFAULT

HO, HO-TO-EUTRA


Not present

}

}

}

}


SRB2-DRB(n,m) Establishment of a SRB and DRB combination with n x AM DRB and m x UM DRB (including establishment of SRB2)

SRB2-DRB(n,m) Establishment of a SRB and DRB combination with n x AM DRB and m x UM DRB (including establishment of SRB2)

DRB(n,m) Establishment of additional n x AM DRB:s and m x UM DRB:s (SRB2 should already be established)

DRB(n,m) Establishment of additional n x AM DRB:s and m x UM DRB:s (SRB2 should already be established)

AM-DRB-ADD(bid) Establishment of a single additional AM DRB with bearer identity bid (SRB2 should already be established)

AM-DRB-ADD(bid) Establishment of a single additional AM DRB with bearer identity bid (SRB2 should already be established)

UM-DRB-ADD(bid) Establishment of a single additional UM DRB with bearer identity bid (SRB2 should already be established)

UM-DRB-ADD(bid) Establishment of a single additional UM DRB with bearer identity bid (SRB2 should already be established)

DRB-REL(bid) Release of the DRB with bearer identity bid

DRB-REL(bid) Release of the DRB with bearer identity bid

HO Intra LTE handover HO Intra LTE handover



MEAS A measurement is configured

MEAS A measurement is configured

HO-TO-EUTRA(n,m) Inter-RAT handover to E-UTRA including the establishment of a SRB1, SRB2 and n x AM DRB plus m x UM DRB

HO-TO-EUTRA(n,m) Inter-RAT handover to E-UTRA including the establishment of a SRB1, SRB2 and n x AM DRB plus m x UM DRB

DRB-Mod Modification of already established DRB ID 2 and is used for sending Modify EPS Bearer Context Request message (SRB2 should already be established)

DRB-Mod Modification of already established DRB ID 2 and is used for sending Modify EPS Bearer Context Request message (SRB2 should already be established)

9.1.4.1 RRCConnectionReconfigurationComplete

Table 9-5: RRCConnectionReconfigurationComplete


RRCConnectionReconfigurationComplete ::= SEQUENCE {



rrcConnectionReconfigurationComplete-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {} Not checked

}

}

}

9.1.4.2 SecurityModeCommand

Table 9-6: SecurityModeCommand


SecurityModeCommand



::= SEQUENCE {



c1 CHOICE{

securityModeCommand-r8 SEQUENCE {

securityConfigSMC SecurityConfigSMC-DEFAULT


Not present

}

}

}

9.1.4.3 SecurityModeComplete

Table 9-7: SecurityModeComplete


SecurityModeComplete ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-UL


securityModeComplete-r8 SEQUENCE {


Not checked

}

}

}


9.1.4.4 RRCConnectionRelease






c1 CHOICE {


releaseCause other

redirectedCarrierInfo Not present

idleModeMobilityControlInfo Not present


Not present

}

}

}

}

9.1.4.5 UECapabilityEnquiry

Table 9-9: UECapabilityEnquiry


UECapabilityEnquiry ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL


c1 CHOICE {

ueCapabilityEnquiry-r8 SEQUENCE {

ue-CapabilityRequest eutra

nonCriticalExtension Not present



SEQUENCE {}

}

}

}

}

9.1.4.6 UECapabilityInformation

Table 9-10: UECapabilityInformation


UECapabilityInformation ::= SEQUENCE {



c1 CHOICE{

ueCapabilityInformation-r8 SEQUENCE {

ue-CapabilityRAT-ContainerList

Stated capability shall be compatible with 3GPP TS 36.523-2 (ICS statements) and the user settings


Not checked

}

}

}

}

9.1.4.7 Paging

Table 9-11: Paging


Paging::= SEQUENCE {

id- Set to the



UEIdentityIndexValue UEIdentityIndex of the UE

id-UEPagingID Set to the value of the S-TMSI of the UE

id-pagingDRX

id-CNDomain ps

id-TAIList ::= SEQUENCE{

tAI Set to PLMN identity and TAC to identify the tracking area of the UE

iE-Extensions

}

id-CSG-IdList

}

9.1.4.8 UEContextReleaseCommand

Table 9-12: UEContextReleaseCommand Message


UEContextReleaseCommand::= SEQUENCE {

id-UE-S1AP-IDs

id-Cause

}

9.1.4.9 RRCConnectionRelease





c1 CHOICE {





eutra

}

}

}

}

}

9.1.4.10 InitialUEMessage

Table 9-14: InitialUEMessage


InitialUEMessage::= SEQUENCE {

id-eNB-UE-S1AP-ID

id-NAS-PDU UE – EPC message

id-TAI Set to the PLMN Identity and TAC value

id-EUTRAN-CGI Set to the PLMN Identity and Cell Identity.

id-RRC-Establishment-Cause

id-S-TMSI

id-CSG-Id

id-GUMMEI-ID

}

9.1.4.11 InitialContextSetupRequest

Table 9-15: InitialContextSetupRequest


InitialContextSetupRequest::= SEQUENCE {

id-MME-UE-S1AP-ID

id-eNB-UE-S1AP-ID



id-uEaggregateMaximumBitrate

Valid Bit rate value

id-E-RABToBeSetupListCtxtSUReq

Set to valid values for E-RAB to Be Setup List

id-UESecurityCapabilities Supported algorithms for encryption and integrity protection

id-SecurityKey

id-TraceActivation

id-HandoverRestrictionList

id-UERadioCapability

id-SubscriberProfileIDforRFP

id-CSFallbackIndicator

id-SRVCCOperationPossible

}

9.1.4.12 InitialContextSetupResponse

Table 9-16: InitialContextSetupResponse


InitialContextSetupResponse::= SEQUENCE {

id-MME-UE-S1AP-ID

id-eNB-UE-S1AP-ID

id-E-RABSetupListCtxtSURes::=SEQUENCE {

SIZE(1.. maxNrOfE-RABs)) of SEQUENCE {

e-RAB-ID

transportLayerAddress IP address

gTP-TEID GTP Tunnel Endpoint Identifier

iE-Extensions

}



}

id-E-RABFailedToSetupListCtxtSURes::= SEQUENCE{

id-MME-UE-S1AP-ID

id-eNB-UE-S1AP-ID

id-Cause

id-CriticalityDiagnostics

}

id-CriticalityDiagnostics

}

9.1.4.13 Handover to UTRAN Command



New U-RNTI U-RNTI-Short

- SRNC identity 0000 0000 0001B

- S-RNTI 0000 0000 0000 0000 0001B

Ciphering algorithm UEA0 or UEA1. The indicated algorithm must be one of the algorithms supported by the UE.

RNC support for change of UE capability

FALSE

New H-RNTI Not present UTRA PS RB, UTRA Speech, UTRA PS RB + Speech

'1010 1010 1010 1010'

UTRA HSDPA RB, UTRA HSUPA/HSDPA RB

New Primary E-RNTI Not present UTRA PS RB, UTRA HSDPA RB, UTRA Speech, UTRA PS RB + Speech

'1010 1010 1010 1010'

UTRA HSUPA/HSDPA RB



New Secondary E-RNTI Not present

Default configuration for CELL_FACH

Not present

CHOICE specification mode

Complete specification

Signaling RB information to setup List

Same as the corresponding IE in the RRC CONNECTION SETUP message (Transition to CELL_DCH or HS-PDSCH in CELL_FACH) using condition A1 in TS 34.108 clause 9.1.1

UTRA PS RB, UTRA HSDPA RB, UTRA Speech, UTRA PS RB + Speech

Same as the corresponding IE in the RRC CONNECTION SETUP message (Transition to CELL_DCH or HS-PDSCH in CELL_FACH) using condition A3 in TS 34.108 clause 9.1.1

UTRA HSUPA/HSDPA RB

RAB information to setup list

Same as the corresponding IE in the RADIO BEARER SETUP message using condition A2 in TS 34.108 clause 9.1.1

UTRA Speech, UTRA PS RB + Speech


UTRA PS RB, UTRA PS RB + Speech


UTRA HSDPA RB




UTRA HSUPA/HSDPA RB

UL Transport channel information common for all transport channels




UTRA PS RB


UTRA HSDPA RB

Same content as the corresponding IE in the RADIO BEARER SETUP message using condition A14 in TS 34.108 clause 9.1.1

UTRA HSUPA/HSDPA RB

Added or Reconfigured UL TrCH information




UTRA PS RB




UTRA HSDPA RB


UTRA HSUPA/HSDPA RB

DL Transport channel information common for all transport channels




UTRA PS RB


UTRA HSDPA RB

Same content as the corresponding IE in the RADIO BEARER SETUP message using condition A14 in TS 34.108 clause 9.1.1

UTRA HSUPA/HSDPA RB

Added or Reconfigured DL TrCH information






UTRA PS RB


UTRA HSDPA RB


UTRA HSUPA/HSDPA RB

Uplink DPCH info Same as the corresponding IE in the RADIO BEARER SETUP message using condition A2 in TS 34.108 clause 9.1.1



UTRA PS RB


UTRA HSDPA RB


UTRA HSUPA/HSDPA RB



E-DCH Info Not present UTRA PS RB, UTRA HSDPA RB, UTRA Speech, UTRA PS RB + Speech


UTRA HSUPA/HSDPA RB

Downlink HS-PDSCH Information

Not present UTRA PS RB, UTRA Speech, UTRA PS RB + Speech


UTRA HSDPA RB


UTRA HSUPA/HSDPA RB

Downlink information common for all radio links




UTRA PS RB


UTRA HSDPA RB




UTRA HSUPA/HSDPA RB

Downlink information for each radio link list




UTRA PS RB


UTRA HSDPA RB


UTRA HSUPA/HSDPA RB

Frequency info Set according to the frequency of the target UTRA cell.

Multi-frequency Info Not present

Maximum allowed UL TX power

33dBm

10. Appendix C (Pre-Conditions)

10.1. Network Configurations

10.1.1. Operating Bands

Table 10-1: Operating Bands

E-UTRA Operating Band

Uplink (UL) operating band BS receive UE transmit

Downlink (DL) operating band BS transmit UE receive

Duplex Mode

FUL_low –FUL_high FDL_low –FDL_high

1 1920 MHz – 1980 MHz 2110 MHz – 2170 MHz FDD

2 1850 MHz – 1910MHz 1930 MHz – 1990 MHz FDD



5 824 MHz – 849 MHz 869 MHz – 894MHz FDD

61 830 MHz – 840MHz 875 MHz – 885 MHz FDD



9 1749.9 MHz

– 1784.9 MHz

1844.9 MHz – 1879.9 MHz

FDD


11 1427.9 MHz

– 1447.9 MHz

1475.9 MHz – 1495.9 MHz

FDD




15 Reserved Reserved FDD

16 Reserved Reserved FDD





Chapter Ten: Appendix C | 251

E-UTRA Operating Band

Uplink (UL) operating band BS receive UE transmit

Downlink (DL) operating band BS transmit UE receive

Duplex Mode

21 1447.9 MHz

– 1462.9 MHz

1495.9 MHz – 1510.9 MHz

FDD

10.1.2. Mapping of E-UTRA Bands to Bandwidth

Table 10-2: Mapping of E-UTRA Bands to Bandwidth

E-UTRA Band/Channel Bandwidth

E-UTRA Band 1.4 MHz 3 MHz 5 MHz 10MHz 15 MHz 20MHz

1 Yes Yes Yes Yes

2 Yes Yes Yes Yes Yes[1] Yes[1]

3 Yes Yes Yes Yes Yes[1] Yes[1]

4 Yes Yes Yes Yes Yes Yes

5 Yes Yes Yes Yes[1]

6 Yes Yes[1]



9 Yes Yes Yes[1] Yes[1]

10 Yes Yes Yes Yes

11 Yes Yes[1]

12 Yes Yes Yes[1] Yes[1]

13 Yes[1] Yes[1]

14 Yes[1] Yes[1]

...

17 Yes[1] Yes[1]

18 Yes Yes[1] Yes[1]


20 Yes Yes[1] Yes[1] Yes[1]


...

33 Yes Yes Yes Yes

34 Yes Yes Yes




E-UTRA Band/Channel Bandwidth

37 Yes Yes Yes Yes

38 Yes Yes Yes Yes

39 Yes Yes Yes Yes

40 Yes Yes Yes Yes

NOTE:Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (Clause 7.3) is allowed.

10.1.3. PLMN Association with MCC and MNC

Table 10-3: PLMN association with MCC and MNC

PLMN MCC1 MCC2 MCC3 MNC1 MNC2 MNC3 TAC

1 0 0 1 0 1 Not present Refer to Table 6-4

2 0 0 2 1 1 Not present















10.1.4. PLMN Mapping to Cell

Table 10-4: PLMN Mapping to Cell

Cell PLMN name MCC MNC

1 PLMN1 001 01

2 PLMN2 001 11

3 PLMN3 001 21

4 PLMN4 001 31


10.1.5. General Network Configuration

Table 10-5: General Network Configuration

Cell ID PLMN name MCC MNC TAC MME Group ID

MME Code

1 PLMN1 001 01 1 32769 1

2 PLMN1 001 01 2 32769 1

3 PLMN1 001 01 3 32769 1

4 PLMN2 001 11 2 32769 1

5 PLMN3 001 21 3 32769 1

6 PLMN4 001 31 4 32769 1

10.1.6. General Cell Configuration

Table 10-6: General Cell Configuration

Cell ID

E-UTRAN Cell Identifier Physical layer cell identity

rootSequenceIndex FDD

rootSequenceIndex TDD

eNB Identifier Cell Identity

Cell 1

'0000 0000 0000 0000 0001'B

'0000 0000'B

0 22 0

Cell 2

'0000 0000 0000 0000 0001'B

'0000 0010'B

2 86 8

Cell 3

'0000 0000 0000 0000 0010'B

'0000 0011'B

3 22 0

Cell 4

'0000 0000 0000 0000 0011'B

'0000 0100'B

4 150 16

Cell 6

'0000 0000 0000 0000 0100'B

'0000 0110'B

6 22 0

Cell 10

'0000 0000 0000 0000 0101'B

'0000 1010'B

10 22 0

Cell 11

'0000 0000 0000 0000 0110'B

'0000 1011'B

11 214 24

Cell 12

'0000 0000 0000 0000 0010'B

'0000 1100'B

12 86 8

Cell 13

'0000 0000 0000 0000 0100'B

'0000 1101'B

13 86 8

Cell 14

'0000 0000 0000 0000 0111'B

'0000 1110'B

14 22 0


10.1.7. Radio Link Parameters

Table 10-7: Radio Link Parameters

Configuration RS EPRE Qrxlevmin EARFCN(UL/DL) Frequency Band

1 -73 -100 22650/4650 10

10.1.8. UE Categories

Table 10-8: UE Categories

UE Category Maximum number of DL-SCH transport block bits received within a TTI

Maximum number of bits of a DL-SCH transport block received within a TTI

Total number of soft channel bits

Maximum number of supported layers for spatial multiplexing in DL

Category 1 10296 10296 250368 1

Category 2 51024 51024 1237248 2

Category 3 102048 75376 1237248 2

Category 4 150752 75376 1827072 2

Category 5 299552 149776 3667200 4

10.1.9. UE Categories UL Parameter Support

Table 10-9: UE Categories UL Parameter Support

UE Category

Maximum number of bits of an UL-SCH transport block transmitted within a TTI

Support for 64QAM in UL

Category 1 5160 No

Category 2 25456 No

Category 3 51024 No

Category 4 51024 No

Category 5 75376 Yes


10.1.10. Default NAS Parameters for Simulated Cells

Table 10-10: Default NAS Parameters for Simulated Cells

Cell ID Tracking Area TA# List *Note 1

GUTI *Note 2

TA# PLMN TAC MME Identifier M-TMSI

MCC MNC MME Group ID

MME Code

Cell 1 TAI-1

*Note 3 1 TAI-1 32769 1 Arbitrarily selected according to TS23.003 subclause 2.8 [2]. Cell 2 TAI-

1 *Note 3 1 TAI-1 32769 1

Cell 3 TAI-1

*Note 3 1 TAI-1 32769 1

Cell 4 TAI-1

*Note 3 1 TAI-1 32769 1

Cell 6 TAI-1

*Note 3 1 TAI-1 32769 1

Cell 10 TAI-1

*Note 3 1 TAI-1 32769 1

Cell 11 TAI-2

*Note 3 2 TAI-2 32769 1

Cell 23 TAI-2

*Note 3 2 TAI-2 32769 1

Cell 12, Cell 28

TAI-3

002 11 1 TAI-3 32769 1

Cell 13,Cell 29

TAI-4

003 21 1 TAI-4 32769 1

Cell 14, Cell 30

TAI-5

004 31 1 TAI-5 32769 1

*Note 1:The value(s) in the column TA# list indicates TAI(s) included in the response messages of the registration procedure (ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT) when the UE performs the registration procedure on a corresponding cell.

Note 2:The value in the column GUTI indicates GUTI included in the response messages of the registration procedure (ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT) when the UE performs the registration procedure on a corresponding cell.

Note 3:Set to the same Mobile Country Code and Mobile Network Codestored in EFIMSI on the test USIM card (subclause 4.9.3).


10.1.11. Network Configuration for Simulated NAS Cell

Table 10-11: Network Configuration Simulated NAS Cell

NAS Cell ID

Tracking Area TA# List *Note 1

GUTI *Note 2

TA# PLMN TAC MME Identifier M-TMSI

MCC MNC MME Group ID

MME Code

Cell 1 TAI-1 *Note 3 1 TAI-1 32769 1 Arbitrarily selected Cell 2 TAI-2 *Note 3 2 TAI-2 32770 1

Cell 3 TAI-3 *Note 3 3 TAI-3 32771 1

Cell 4 TAI-4 *Note 3 4 TAI-4 32772 1

Cell 5 TAI-12 002 101 3 TAI-12 32777 1

Cell 6

Cell 7 TAI-7 *Note 4

02 1 TAI-7 32775 1

Cell 8 TAI-8 *Note 4

02 2 TAI-8 32776 1

Cell 9 TAI-9 002 101 1 TAI-9 32777 1

Cell 10 TAI-10 003 101 1 TAI-10 32778 1

Cell 11 TAI-9 002 101 1 TAI-9 32777 1

Cell 12 TAI-11 002 101 2 TAI-11 32779 1

Cell 13 TAI-1 *Note 3 1 TAI-1 32769 1

*Note 1: The value(s) in the column TA# list indicates TAI(s) included in the response messages of the registration procedure (ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT) when the UE performs the registration procedure on a corresponding cell.

Note 2: The value in the column GUTI indicates GUTI included in the response messages of the registration procedure (ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT) when the UE performs the registration procedure on a corresponding cell.

Note 3:Set to the same Mobile Country Code and Mobile Network Codestored in EFIMSI on the test USIM card (sub clause4.9.3).

Note 4:Set to the same Mobile Country Codestored in EFIMSI on the test USIM card (sub clause4.9.3).

Note 5: Cell 1 is a serving cell and the other cells are suitable neighbor cells. The definitions are specified in sub clause 6.2.2.1.


10.1.12. Reference Dedicated EPS Bearer Contexts

Table 10-12: Reference Dedicated EPS Bearer Contexts

Parameters Reference dedicated EPS bearer context #1

Reference dedicated EPS bearer context #2


Linked EPS Bearer Identity

Reference default EPS bearer #1

Reference default EPS bearer #1

FFS

EPS QoS

QCI

(Note 1)

1

(GBR QCI)

5

(non-GBR QCI)

FFS

Maximum bit rate for uplink

384 kbps 384 kbps

(Note 2)

FFS

Maximum bit rate for downlink

384 kbps 384 kbps

(Note 2)

FFS

Guaranteedbit rate for uplink

128 kbps 128 kbps

(Note 2)

FFS

Guaranteed bit rate for downlink

128 kbps 128 kbps

(Note 2)

FFS

Maximum bit rate for uplink (extended)

0 0 FFS

Maximum bit rate for downlink (extended)

0 0 FFS

Guaranteed bit rate for uplink (extended)

0 0 FFS

Guaranteed bit rate for downlink (extended)

0 0 FFS

TFT

TFT operation code “create new TFT” “create new TFT” FFS

E bit 0 0 FFS

Packet filters

(Note 5)

1, 2 3 FFS

Negotiated QoS

Traffic Class conversational Refer to PDP context3 (Note 3, Note 6)

FFS

Delivery Order 'yes' Refer to PDP context3 (Note 3, Note 6)

FFS





Delivery of erroneous SDU

'no' Refer to PDP context3 (Note 3, Note 6)

FFS

Maximum SDU size 150 Refer to PDP context3 (Note 3, Note 6)

FFS

Maximum bit rate for uplink

384 kbps Refer to PDP context3 (Note 3, Note 6)

FFS

Maximum bit rate for downlink

384 kbps Refer to PDP context3 (Note 3, Note 6)

FFS

Residual BER 5*10-2 Refer to PDP context3 (Note 3, Note 6)

FFS

SDU error ratio 10-2 Refer to PDP context3 (Note 3, Note 6)

FFS

Transfer delay 80 ms Refer to PDP context3 (Note 3, Note 6)

FFS

Traffic Handling priority

0 Refer to PDP context3 (Note 3, Note 6)

FFS

Guaranteed bit rate for uplink


FFS

Guaranteed bit rate for downlink


FFS

Signaling Indication 0 Refer to PDP context3 (Note 3, Note 6)

FFS

Source Statistics Descriptor


FFS

Maximum bit rate for downlink (extended)


FFS

Guaranteed bit rate for downlink (extended)


FFS

Maximum bit rate for uplink (extended)


FFS

Guaranteed bit rate for uplink (extended)


FFS

Negotiated LLC SAPI 3 (Note 6) Refer to PDP context3 (Note 6)

FFS

Radio priority 1 (Note 6) Refer to PDP context3 (Note 6)

FFS





Protocol configuration options

- - FFS

Note 1: For all non-GBR QCIs, the maximum and guaranteed bit rates shall be ignored.

Note 2: According to TS 24.301, the UE ignores these parameters for a non-GBR QCI.

Note 3: Parameters included for UEs capable of UTRAN according to TS 34.123-3 clause 8.10.

Note 5: This row refers to the reference packet filters defined in the tables below. For each reference dedicated EPS bearer context, a list of reference packet filter numbers is provided.

Note 6: Parameter included for UEs capable of GERAN when value is not provided then value from TS 51.010 sub-clause 40.5 is applied.

10.1.13. UTRAN Cell Configuration

Table 10-13: Default Parameters for Simulated UTRA Cells

Cell ID Primary scrambling code for FDD Cell parameters ID for TDD

Cell 5 100 0

Cell 7 150 4

Cell 8 200 8

Cell 9 250 12

Table 10-14: Default NAS Parameters for Simulated UTRA Cells

PLMN Location Area Identification

Routing Area Identification

TMSI P-TMSI signature

MCC MNC LA# LAC RA# RAC

Cell 5

(Note 1) LAI-1 1 RAI-1 1 Arbitrarily selected according to TS23.003

sub clause 2.4 [2].

Arbitrarily selected according to TS23.003

sub clause 2.7 [2]. Cell 7

(Note 1) LAI-1 1 RAI-1 1

Cell 8


Cell 9


Note 1: Set to the same Mobile Country Code and Mobile Network Codestored in EFIMSI on the test USIM card (sub clause4.9.3).


10.1.14. UTRAN Test Frequency

Table 10-15: UTRAN Test Frequency in FDD Mode

Cell ID UARFCN Frequency of Uplink UARFCN Frequency of Downlink

Cell 5 9 613 1 922.6 MHz 10 563 2 112.6 MHz

10.1.15. Suitable/Non-Suitable EUTRAN Cell Parameters

Table 10-16: Default Settings of Suitable/Non-suitable EUTRAN Cells

Power Level Type E-UTRAN

Unit Power Level

Serving cell dBm/15kHz -85

Suitable neighbor intra-frequency cell dBm/15kHz -91

Suitable neighbor inter-frequency cell dBm/15kHz -97

Non-suitable cell dBm/15kHz -115

Non-suitable “Off” cell dBm/15kHz ≤ -145

10.1.16. Suitable/Non-Suitable UTRAN Cell Parameters

Table 10-17: Default Settings of Suitable/Non-suitable UTRAN Cells

Power Level Type UTRAN Cell Parameters

Qqualmin Qrxlevmin UE_TXPWR_MAX_RACH

CPICH Ec

(dB) (dBm) (dBm) dBm/3.84 MHz

Serving cell -24 -79 21 -60

Suitable neighbor intra-frequency cell

-24 -79 21 -70

Suitable neighbor inter-frequency cell

-24 -79 21 -70

Non-suitable cell -24 -79 21 -90

Non-suitable “Off” cell -24 -79 21 ≤ -122

10.1.17. UTRA Reference Radio Parameters and Combinations

Table 10-18: UTRA Reference Radio Parameters and Combinations

Condition Comment

UTRA Speech Conversational/speech/UL:12.2 DL:12.2 kbps/CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH


Condition Comment

UTRA PS RB Interactive or background/UL:64 DL: 64 kbps/PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

UTRA HSDPA RB Interactive or background/UL:64 DL: [max bit rate depending on UE category]/PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

UTRA HSUPA/HSDPA RB Streaming or interactive or background/UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category]/PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH

UTRA PS RB + Speech Conversational/speech/UL:12.2 DL:12.2 kbps/CS RAB + Interactive or background/UL:64 DL:64 kbps/PS RAB+ UL:3.4 DL: 3.4 kbps SRBs for DCCH

10.1.18. MIB

10.1.18.1 MIB Configuration Sample 1 –Default

The MasterInformationBlock includes the system information transmitted on BCH.

Table 10-19: MasterInformationBlock


MasterInformationBlock ::= SEQUENCE {

dl-Bandwidth n50.

phich-ConfigSEQUENCE {}

PHICH-Config-DEFAULT

Refer to Table 6-20

systemFrameNumber Formula SFN mod 4 = 0 , this value can be 0,4,8 ,12

Spare '0000 0000 00'B

}

Table 10-20: PHICH-Config-DEFAULT


PHICH-Config-DEFAULT ::= SEQUENCE {

phich-Duration Normal



phich-Resource One Ng=1 has been selected to ensure enough PHICH resources from the real network point of view.

10.1.19. SystemInformationBlockType1

10.1.19.1 SIB1 Configuration Sample 1 –Default

Table 10-21: SystemInformationBlockType1 Contents



cellAccessRelatedInfo SEQUENCE {

plmn-IdentityList SEQUENCE (SIZE (1..6)) OF SEQUENCE {

1 entry

plmn-Identity[1] SEQUENCE {

mcc SEQUENCE (SIZE (3)) OF MCC-NMC-Digit

Cell 1 Configuration from PLMN mapping to cell

mnc SEQUENCE (SIZE (2..3)) OF MCC-NMC-Digit

Cell 1 Configuration from PLMN mapping to cell

}

cellReservedForOperatorUse[1] notReserved

}

trackingAreaCode Cell 1 Configuration from Table 6-5: General Network Configuration

This code is common for a set of eNodeBs under a MME

cellIdentity Cell 1 Configuration of Table 6-5: General Network Configuration

Cell ID for the simulated cell

cellBarred notBarred

intraFreqReselection notAllowed



csg-Indication FALSE

csg-Identity Not present

}


q-RxLevMin Configuration 1 of Table 6-7: Radio Link Parameters

For RF/RRM test cases

q-RxLevMinOffset Not present

}

p-Max Not present

freqBandIndicator Configuration 1 of Table 6-7: Radio Link Parameters

Also Based on UE

schedulingInfoList SEQUENCE (SIZE (1..maxSI-Message)) OF SEQUENCE {}

Table 6-39: Scheduling for Combination 1

tdd-ConfigSEQUENCE {} Not present FDD

tdd-ConfigSEQUENCE {} TDD-Config-DEFAULT

TDD

si-WindowLength ms20 To allow sufficient number of retransmissions.

systemInfoValueTag 0

nonCriticalExtensionSEQUENCE {}

Not present


10.1.20. SystemInformationBlockType2

10.1.20.1 SIB2 Configuration Sample 1 –Default

The IE SystemInformationBlockType2 contains radio resource configuration information that is common for all UEs.

Table 10-22: SystemInformationBlockType2 Contents



ac-BarringInfo SEQUENCE {} Not present

radioResourceConfigCommon SEQUENCE {}

RadioResourceConfigCommonSIB-DEFAULT

ue-TimersAndConstants SEQUENCE {

t300 ms1000 Typical value in real network



n310 n1


n311 n1

}

freqInfo SEQUENCE {

ul-CarrierFreq Not present Default UL EARFCN applies

ul-Bandwidth Not Present

additionalSpectrumEmission

1 (NS_01) A-MPR doesn’t apply by default.

Refer to TS36.101Table6.2.4-1.

}

mbsfn-SubframeConfiguration

Not present



timeAlignmentTimerCommon

sf750 ‘sf750’ is applicable to the widest range of mobility (up to about 360km/h).

}

10.1.21. RadioResourceConfigCommon-DEFAULT

Table 10-23: RadioResourceConfigCommon-DEFAULT


RadioResourceConfigCommon-DEFAULT ::= SEQUENCE {

rach-ConfigCommon RACH-ConfigCommon-DEFAULT

prach-Config PRACH-Config-DEFAULT

pdsch-ConfigCommon Not present

pusch-ConfigCommon PUSCH-ConfigCommon-DEFAULT

phich-Config Not present

pucch-ConfigCommon Not present

soundingRSUL-ConfigCommon SoundingRS-UL-ConfigCommon-DEFAULT

uplinkPowerControlCommon Not present

antennaInfoCommon Not present

antennaInfoCommon SEQUENCE {

2TX

antennaPortsCount an2

}

p-Max Not present

tdd-Config Not present FDD

TDD-Config-DEFAULT TDD

ul-CyclicPrefixLength len1


10.1.22. BCCH-Config-DEFAULT

Table 10-24: BCCH-Config-DEFAULT


BCCH-Config-DEFAULT::= SEQUENCE {

modificationPeriodCoeff n4 To provide reliable delivery of SI change notifications.

}

10.1.23. CQI-ReportConfig-DEFAULT

Table 10-25: CQI-ReportConfig-DEFAULT


CQI-ReportConfig-DEFAULT ::= SEQUENCE {

cqi-ReportModeAperiodic rm30

nomPDSCH-RS-EPRE-Offset 0

cqi-ReportPeriodic Not present

cqi-ReportPeriodic CHOICE { CQI_PERIODIC

setup SEQUENCE {

cqi-PUCCH-ResourceIndex 0

cqi-pmi-ConfigIndex 25 (Refer to Table 7.2.2-1Ain TS 36.213)

FDD

24 (Refer toTable 7.2.2-1C in TS 36.213)

TDD

cqi-FormatIndicatorPeriodic CHOICE {

widebandCQI NULL

}

ri-ConfigIndex 483 (Refer to Table 7.2.2-1B in TS 36.213)

FDD



484 (Refer to Table 7.2.2-1B in TS 36.213) This value for TDD is selected together with cqi-pmi-ConfigIndex based on TDD Configuration 1.

TDD

simultaneousAckNackAndCQI FALSE

}

}

}

10.1.24. DRB-ToAddModList-RECONFIG

Table 10-26: DRB-ToAddModList-RECONFIG

Condition Explanation

CQI_PERIODIC When periodic CQI reporting should be enabled

FDD FDD cell environment

TDD TDD cell environment

10.1.25. PCCH-Config-DEFAULT


DRB-ToAddModList ::= SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {

2 Entries

eps-BearerIdentity[1] Not present

drb-Identity[1] 1

pdcp-Config[1] Not present

rlc-Config[1] RLC-Config-DRB-AM-RECONFIG

logicalChannelIdentity[1] Not present

logicalChannelConfig[1] Not present

eps-BearerIdentity[2] Not present



drb-Identity[2] 2

pdcp-Config[2] Not present

rlc-Config[2] RLC-Config-DRB-AM-RECONFIG

logicalChannelIdentity[2] Not present

logicalChannelConfig[2] Not present

}

Table 10-27: PCCH-Config-DEFAULT


PCCH-Config-DEFAULT::= SEQUENCE {

defaultPagingCycle rf128 Typical value in real network.

nB oneT

}

10.1.26. PHICH-Config-DEFAULT

Table 10-28: PHICH-Config-DEFAULT


PHICH-Config-DEFAULT ::= SEQUENCE {

phich-Duration normal

phich-Resource one Ng=1 has been selected to ensure enough PHICH resources from the real network point of view.

10.1.27. PDSCH-ConfigCommon-DEFAULT

Table 10-29: PDSCH-ConfigCommon-DEFAULT


PDSCH-ConfigCommon-DEFAULT ::= SEQUENCE {

referenceSignalPower 18 (dBm)

p-b 0 ( AB ρρ / = 1)

1TX



1 ( AB ρρ / = 1)

2TX


1TX 1 Network Tx antenna environment

2TX 2 Network Tx antenna environment

10.1.28. PDSCH-ConfigDedicated-DEFAULT

Table 10-30: PDSCH-ConfigDedicated-DEFAULT


PDSCH-ConfigDedicated-DEFAULT ::= SEQUENCE {

p-a dB-3 for signaling test cases;

dB0 for others

dB-3for signaling test cases to reduce interferencefrom PDSCH of intra-frequency neighbor cells

1TX

dB-3 2TX

}

10.1.29. PRACH-Config-DEFAULT

Table 10-31: PRACH-Config-DEFAULT


PRACH-Config-DEFAULT ::= SEQUENCE {

rootSequenceIndex Refer toTable 6-6and Table 6-10.

Refer to Table 5.7.2-4 in TS 36.211for PRACH format 0-3

FDD

Refer toTable 6-6and Table 6-10.

Refer to Table 5.7.2-5 in TS 36.211 for PRACH format 4

TDD

prach-ConfigInfo SEQUENCE {

prach-ConfigIndex 3 Typical value in real FDD



network for FDD (Refer to Table 5.7.1-1 and 5.7.1-2 in TS 36.211)

51 Typical value in real network for TDD (Refer to table 5.7.1-3 and 5.7.1-4 in TS 36.211)

TDD

highSpeedFlag FALSE (Unrestricted set)

High speed train configuration doesn’t apply by default.

zeroCorrelationZoneConfig 5 (Ncs configuration = 5)

Assuming cell radius is up to approximately 3 km.

FDD

4 (Ncs configuration = 4)

Assuming cell radius is up to approximately 1 km.

TDD

prach-FreqOffset Refer to sub clause 4.6.8

Channel-bandwidth-dependent parameter

}

}

Note: Although PRACH format 0-3 is applicable for both FDD and TDD, the PRACH format 4 is used as default for testing for TDD.





10.1.30. PUCCH-ConfigCommon-DEFAULT

Table 10-32: PUCCH-ConfigCommon-DEFAULT


PUCCH-ConfigCommon-DEFAULT ::= SEQUENCE {

deltaPUCCH-Shift ds2 Assuming typical values of the maximum delay spread

nRB-CQI Refer to sub clause 4.6.8


nCS-AN 6

n1PUCCH-AN 0

}

10.1.31. PUCCH-ConfigDedicated-DEFAULT

Table 10-33: PUCCH-ConfigDedicated-DEFAULT


PUCCH-ConfigDedicated-DEFAULT ::= SEQUENCE {

ackNackRepetition CHOICE {

release NULL

}

tddAckNackFeedbackMode Not present FDD

multiplexing Multiplexing is selected as default to align with RAN4’s assumptions in RF tests.

TDD

}





10.1.32. PUSCH-ConfigCommon-DEFAULT

Table 10-34: PUSCH-ConfigCommon-DEFAULT


PUSCH-ConfigCommon-DEFAULT ::= SEQUENCE {

pusch-ConfigBasic SEQUENCE {

n-SB 1 Typical configuration in real network

hoppingMode interSubFrame Typical configuration in real network

pusch-HoppingOffset Refer tosub clause 4.6.8


enable64QAM FALSE

}

ul-ReferenceSignalsPUSCH SEQUENCE {

groupHoppingEnabled TRUE In accordance with “the RAN5 LTE UE Feature list”.

groupAssignmentPUSCH 0 Typical value in real network

sequenceHoppingEnabled FALSE In accordance with “the RAN5 LTE UE Feature list”.

cyclicShift 0

}

}

10.1.33. PUSCH-ConfigDedicated-DEFAULT

Table 10-35: PUSCH-ConfigDedicated-DEFAULT


PUSCH-ConfigDedicated-DEFAULT ::= SEQUENCE {



betaOffset-ACK-Index 9

betaOffset-RI-Index 6

betaOffset-CQI-Index 6

}

10.1.34. RACH-ConfigCommon-DEFAULT

Table 10-36: RACH-ConfigCommon-DEFAULT


RACH-ConfigCommon-DEFAULT ::= SEQUENCE {

preambleInfo SEQUENCE {

numberOfRA-Preambles n52 Assuming the number of dedicated preambles is 12.

preamblesGroupAConfigSEQUENCE {}

Not present

}

powerRampingParameters SEQUENCE {

powerRampingStep dB2

preambleInitialReceivedTargetPower dBm-104 (default)

Thermal noise = -113 dBm

NF = 5 dB

IoT = 6 dB

Required SNR = -8 dB (Refer to Table 8.4.2-1 in TS 36.104 [30])

-> -110 dB

(default value is acceptable)

}

ra-SupervisionInfo SEQUENCE {



preambleTransMax n6 Under the condition of Case 1 in RAN1 simulation assumptions, an UE with pathloss of CDF = 90% reaches the maximum transmit power in 4 successive retransmissions.

6 has been selected considering the margin of 2.

ra-ResponseWindowSize sf10 The maximum value is preferable.

mac-ContentionResolutionTimer sf48 Allows for a sufficient number of msg3 retransmissions.

}

maxHARQ-Msg3Tx 4 Under the condition of Target SIR = 2 dB, the probability of 2 transmissions is less than 1%. 4 has been selected considering the margin of 2.

}

10.1.35. SoundingRS-UL-ConfigCommon-DEFAULT

Table 10-37: SoundingRS-UL-ConfigCommon-DEFAULT


SoundingRS-UL-ConfigCommon-DEFAULT ::= SEQUENCE {

setup SEQUENCE {



-srs-BandwidthConfig Refer tosub clause 4.6.8


srs-SubframeConfig sc0 Assuming SRS density is high.Refer to Table 5.5.3.3-1 in TS 36.211.

FDD

sc4 Assuming SRS density is high.

Refer to Table 5.5.3.3-2 in TS 36.211.

TDD

ackNackSRS-SimultaneousTransmission

TRUE Typical value in real network

srs-MaxUpPts Not Present

}

}

10.1.36. Combinations of System Information Blocks

Table 10-38: Combinations of System Information Blocks



SIB11

SIB13

1 X X

2 X X X

3 X X X

4 X X X

5 X X X

6 X X X

7 X X X X

8 X X X X

9 X X X X

10 X X X X

10a X X X X X

11 X X X X X

12 X X X X



13 X X X X X

14 X X X X X

15 X X

16 X X X X

Combination 1 is the default combination which applies to the following test case scenarios:

• E-UTRA FDD single cell scenario

• E-UTRA TDD single cell scenario

• E-UTRA FDD intra-frequency multi cell scenario

• E-UTRA TDD intra-frequency multi cell scenario

• E-UTRA FDD + E-UTRA TDD dual mode multi cell in different PLMN scenario

NOTE: Different PLMN scenarios are intended for Roaming Scenarios only. Handover and Cell Reselection scenario configurations are FFS.

Combination 2 applies to the following test case scenarios:

• E-UTRA FDD intra-frequency multi cell scenario with neighboring cell related information

• E-UTRA TDD intra-frequency multi cell scenario with neighboring cell related information


• E-UTRA FDD inter-frequency multi cell scenario

• E-UTRA TDD inter-frequency multi cell scenario

• E-UTRA FDD inter-band multi cell scenario

• E-UTRA TDD inter-band multi cell scenario

• E-UTRA FDD + E-UTRA TDD dual mode multi cell in single PLMN scenario

NOTE: Single PLMN scenarios are intended for Roaming Scenarios only. Handover and Cell Reselection scenario configurations are FFS.


• 3GPP inter-RAT E-UTRA FDD + UTRA FDD multi cell scenario

• 3GPP inter-RAT E-UTRA TDD + UTRA LCR TDD multi cell scenario

• 3GPP inter-RAT E-UTRA TDD + UTRA FDD multi cell scenario


• 3GPP inter-RAT E-UTRA FDD + GERAN multi cell scenario

• 3GPP inter-RAT E-UTRA TDD + GERAN multi cell scenario



• 3GPP2 inter-RAT E-UTRA FDD + HRPD multi cell scenario

• 3GPP2 inter-RAT E-UTRA TDD + HRPD multi cell scenario

• 3GPP2 inter-RAT E-UTRA FDD + 1xRTT multi cell scenario

• 3GPP2 inter-RAT E-UTRA TDD + 1xRTT multi cell scenario

NOTE: 3GPP2 Inter-RAT multi cell scenarios with E-UTRA + HRPD + 1xRTT are FFS.


• E-UTRA FDD + home eNB multi cell scenario

• E-UTRA TDD + home eNB multi cell scenario


• E-UTRA FDD ETWS single cell scenario

• E-UTRA TDD ETWS single cell scenario


• E-UTRA FDD inter-frequency + 3GPP inter-RAT UTRA multi-cell scenario

• E-UTRA TDD inter-frequency + 3GPP inter-RAT UTRA multi-cell scenario


• 3GPP inter-RAT E-UTRA FDD + UTRA FDD + GERAN multi cell scenario

• 3GPP inter-RAT E-UTRA TDD + UTRA LCR TDD + GERAN multi cell scenario.

Combination 10a applies to the following test case scenarios:

• E-UTRA FDD inter-frequency+ 3GPP inter-RAT E-UTRA FDD + UTRA FDD + GERAN multi cell scenario

• E-UTRA TDD inter-frequency + 3GPP inter-RAT E-UTRA TDD + UTRA LCR TDD + GERAN multi cell scenario


• 3GPP inter-RAT E-UTRA FDD + UTRA FDD + home eNB multi cell scenario

• 3GPP inter-RAT E-UTRA TDD + UTRA LCR TDD + home eNB multi cell scenario


• E-UTRA FDD inter-frequency + GERAN cell scenario

• E-UTRA TDD inter-frequency + GERAN cell scenario


• E-UTRA FDD inter-frequency + home eNB

• E-UTRA TDD inter-frequency + home eNB


• 3GPP inter-RAT E-UTRA FDD + GERAN + home eNB multi cell scenario


• 3GPP inter-RAT E-UTRA TDD + GERAN + home eNB multi cell scenario


• 3GPP E-UTRA FDD + MBMS

• 3GPP E-UTRA TDD + MBMS


• 3GPP E-UTRA FDD + MBMS

• 3GPP E-UTRA TDD + MBMS

Scheduling for combination 1

Table 10-39: Scheduling for Combination 1

Scheduling Information No. Periodicity

[radio frames]

Mapping of System Information Blocks

1 16 SIB2

2 Refer to sub clause 4.4.3.4 SIB3

11. Appendix D

11.1. Contents of EMM Messages

11.1.1. ATTACH ACCEPT

This message is sent by the Network to the UE.

Table 11-1: ATTACH ACCEPT

Information Element

Value/Remark Comment Condition

Protocol discriminator

EMM

Security header type

'0000'B Plain NAS message, not security protected

Attach accept message identity

'01000010'B Attach accept

EPS attach result '0001'B EPS only EPS_only

'0010'B combined EPS/IMSI attach

combined_EPS_IMSI

Spare half octet '0000'B

T3412 value

Timer value '0 0000'B

Unit '111'B value indicates that the timer is deactivated.

TAI list

Length of tracking area identity list contents

'0000 0110'B 6 octets

Partial tracking area identity list 1

Number of elements

'0 0000'B 1 element

Type of list '00'B list of TACs belonging to one PLMN, with non-


Information Element


consecutive TAC values

MCC Refer to Table 6-10. For NAS test cases, refer to Table 6-11.

MNC Refer to Table 6-10. For NAS test cases, refer to Table 6-11.

TAC 1 Refer to Table 6-10. For NAS test cases, refer to Table 6-11.


ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message to activate the default bearer

GUTI

Length of EPS mobile identity contents

'0000 1011'B 11 octets

Type of identity '110'B GUTI

Odd/even indication

'0'B even number of identity digits and also when the GUTI is used

MCC Refer to Table 6-10. For NAS test cases, refer to Table 6-11.

MNC Refer to Table 6-10. For NAS test cases, refer to Table 6-11.

MME Group ID Refer to Table 6-10. For NAS test cases, refer to Table 6-11.

MME Code Refer to Table 6-10. For NAS test cases, refer to Table 6-11.

M-TMSI Refer to Table 6-10. For NAS test cases, refer to Table 6-11.

Location area identification

Not present EPS_only


combined_EPS_IMSI

MCC MCC of the EUTRA cell from which this message is sent

MNC MCC of the EUTRA cell from which this message

Chapter Eleven: Appendix D | 281

Information Element


is sent

LAC 1

MS identity Not present EPS_only

MS identity combined_EPS_IMSI

Length of mobile identity contents

'0000 0101'B 5 octets

Type of identity '100'B TMSI/P-TMSI/M-TMSI

Odd/even indication

'0'B even number of identity digits and also when the TMSI/P-TMSI or TMGI and optional MBMS Session Identity is used

TMSI TMSI-1


T3402 value Not present


Equivalent PLMNs

Not present

Emergency number list

Not present

EPS network feature support

'0000 0001'B IMS voice over PS session in S1 mode supported


'0000 0011'B IMS voice over PS session in S1 mode supported, emergency bearer services in S1 mode supported

Rel-9

Additional update result

Not present


‘10’ B “SMS only” additional_update_result_SMS


EPS_only This condition applies if the UE is configured to initiate EPS attach or if explicitly specified.

combined_EPS_IMSI This condition applies if the UE is configured to initiate combined EPS/IMSI attach or if explicitly specified.



additional_update_result_SMS If the UE requested “SMS only” in the Additional update type IE and combined_EPS_IMSI condition applies

NOTE:This message is always sent within SECURITY PROTECTED NAS MENetworkAGE message.

11.1.2. -ATTACH COMPLETE

This message is sent by the UE to the Network.

Table 11-2: ATTACH COMPLETE


Protocol discriminator EMM

Security header type '0000'B Plain NAS message, not security protected

Attach complete message identity

'01000011'B Attach complete


ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message

NOTE: This message is always sent within SECURITY PROTECTED NAS MENetworkAGE message.

11.1.3. ATTACH REJECT


Table 11-3: ATTACH REJECT




Attach reject message identity

'01000100'B Attach reject

EMM cause Set according to specific message content.




Set according to specific message content.

NOTE: If this message includes the EMM cause set to #25, it is sent within SECURITY PROTECTED NAS MENetworkAGE message. Otherwise this message is sent without integrity protection.

11.1.4. ATTACH REQUEST






Attach request message identity

'01000001'B Attach request

EPS attach type '0001'B EPS attach EPS_only

'0010'B combined EPS/IMSI attach

combined_EPS_IMSI

NAS key set identifier Any allowed value

Old GUTI or IMSI Any allowed value

UE network capability Any allowed value


PDN CONNECTIVITY REQUEST message to request PDN connectivity to the default PDN

Old P-TMSI signature Not present or any allowed value

Additional GUTI Not present or any allowed value


Not present or any allowed value

DRX parameter Not present or any allowed value



MS network capability Not present or any allowed value



TMSI status Not present or any allowed value

Mobile station classmark 2




Supported Codecs Not present or any allowed value

Additional update type

Not present EPS_only



combined_EPS_IMSI


EPS_only Refer to the definition in Table 7-5.

combined_EPS_IMSI Refer to the definition in Table 7-5.

NOTE: This message is sent integrity protected when a valid security context exists and without integrity protection otherwise.

11.1.5. AUTHENTICATION FAILURE


Table 11-5: AUTHENTICATION FAILURE




Authentication failuremessage type

'01011100'B Authentication failure

EMM cause '0001 0100'B Mac failure

Authentication failure parameter

Not present Refer to TS24.301[28] sub clause8.2.5.2


NOTE:The security protection of this message is the same as the previous AUTHENTICATION REQUEST message.

11.1.6. AUTHENTICATION REJECT


Table 11-6: AUTHENTICATION REJECT




Authentication reject message type

'01010100'B Authentication reject

NOTE: This message is sent without integrity protection..

11.1.7. AUTHENTICATION REQUEST


Table 11-7: AUTHENTICATION REQUEST




Authentication request message type

'01010010'B Authentication request

NAS key set identifierASME

NAS key set identifier An arbitrarily selected value between '000'B and '110'B, different from the valid NAS key set identifier of the UE if such a value exists.

TSC '0'B native security context (for KSIASME)




Authentication parameter RAND (EPS challenge)

An arbitrarily selected 128 bits value

Authentication parameter AUTN (EPS challenge)

Refer to TS24.301 [28] sub clause 9.9.3.2.

NOTE:Within a test execution this message is sent without integrity protection before NAS security mode control procedure has been successfully completed; and sent integrity protected and ciphered within SECURITY PROTECTED NAS MENetworkAGE message after NAS security mode control procedure has been successfully completed. Network does not maintain information for NAS security mode control procedure after a TC is completed.

11.1.8. AUTHENTICATION RESPONSE


Table 11-8: AUTHENTICATION RESPONSE




Authentication response message type

'01010011'B Authentication response

Authentication response parameter

Refer to TS24.301 [28] sub clause 9.9.3.4

NOTE:When sent in response to an AUTHENTICATION REQUEST message which is not integrity protected and not ciphered, the AUTHENTICATION RESPONSE message may be sent integrity protected when a valid security context exists and without integrity protection otherwise.

11.1.9. CS SERVICE NOTIfICATION


Table 11-9: CS SERVICE NOTIFICATION






CS service notification message identity

'01100100'B CS Service notification

Paging identity ‘1’B TMSI

CLI Not present

Network Code Not present

LCS indicator Not present

LCS client identity Not present


11.1.10. DETACH ACCEPT(UE originating detach)


Table 11-10: DETACH ACCEPT




Detach accept message identity

'01000110'B Detach accept

NOTE: This message is sent using the same security protection as in the previous DETACH REQUEST message received from the UE.

11.1.11. DETACH ACCEPT(UE terminated detach)


Table 11-11: DETACH ACCEPT




Detach accept message identity

'01000110'B Detach accept


NOTE: This message is sent without integrity protection before NAS security mode control procedure has been successfully completed and sent within SECURITY PROTECTED NAS MENetworkAGE message after NAS security mode control procedure has been successfully completed.

11.1.12. DETACH REQUEST(UE Originating Detach)


Table 11-12: DETACH REQUEST




Detach request message identity

'01000101'B Detach request

Detach type

Type of detach '001'B EPS detach EPS_only

‘011’B combined EPS/IMSI detach

Combined_EPS_IMSI

Switch off '1'B switch off


NAS key set identifier Thevalid NAS key set identifier.

TSC Any Value

GUTI or IMSI If the UE has a valid GUTI, set to the GUTI, otherwise set to the IMSI of the UE.

NOTE: This message is sent with integrity protection before Network has started the ciphering and integrity and ciphered protected after Network has started the ciphering.

11.1.13. DETACH REQUEST(UE terminated detach)


Table 11-13: DETACH REQUEST






Detach request message identity

'01000101'B Detach request

Detach type Set according to specific message content.




11.1.14. DOWNLINK NAS TRANSPORT


Table 11-14: DOWNLINK NAS TRANSPORT




Downlink NAS transport message identity

'01100010'B Downlink NAS transport

NAS message container



11.1.15. EMM INFORMATION


Table 11-15: EMM INFORMATION






EMM information message identity

'01100001'B EMM information

Full name for network Set according to specific message content.

Short name for network


Local time zone Set according to specific message content.

Universal time and local time zone


Network daylight saving time




11.1.16. EMM STATUS

This message is sent by the UE or by the Network.

Table 11-16: EMM STATUS




EMM status message identity

'01100000'B EMM status



11.1.17. EXTENDED SERVICE REQUEST


Table 11-17: EXTENDED SERVICE REQUEST




Extended service request message identity

'0100 1100'B Extended service request

Service type '0001'B mobile terminating CS fallback or 1xCS fallback




M-TMSI If the UE has a valid M-TMSI, set to the M-TMSI, otherwise set to the IMSI of the UE.



CSFB response ’001’B CS fallback accepted by the UE


11.1.18. GUTI REALLOCATION COMMAND


Table 11-18: GUTI REALLOCATION COMMAND




GUTI reallocation command message identity

'01010000'B GUTI reallocation command

GUTI Set according to specific message content.

TAI list Set according to specific message content.


11.1.19. GUTI REALLOCATION COMPLETE


Table 11-19: GUTI REALLOCATION COMPLETE




GUTI reallocation complete message identity

'01010001'B GUTI reallocation complete



11.1.20. IDENTITY REQUEST


Table 11-20: IDENTITY REQUEST




Identity request message identity

'01010101'B Identity request

Identity type '0001'B IMSI


NOTE:This message is sent without integrity protection before NAS security mode control procedure has been successfully completed and sent within SECURITY PROTECTED NAS MENetworkAGE message after NAS security mode control procedure has been successfully completed.

11.1.21. IDENTITY RESPONSE


Table 11-21: IDENTITY RESPONSE




Identity response message

'01010110'B Identity response

Mobile identity IMSI of the UE

NOTE: This message is sent without integrity protection before NAS security mode control procedure has been successfully completed and sent within SECURITY PROTECTED NAS MENetworkAGE message after NAS security mode control procedure has been successfully completed.


11.1.22. SECURITY MODE COMMAND


Table 11-22: SECURITY MODE COMMAND




Security mode command message identity

'01011101'B Security mode command

Selected NAS security algorithms

Type of integrity protection algorithm

Set according to PIXIT parameter for default integrity protection algorithm [FFS]

Type of ciphering algorithm

Set according to PIXIT parameter for default ciphering algorithm [FFS]





Replayed UE security capabilities

Set according to thereceived UE security capabilities

IMEISV request Not present

Replayed nonceUE Not present

NonceMME Not present

NOTE: This message is always sent integrity protected with new EPS security context.


11.1.23. SECURITY MODE COMPLETE


Table 11-23: SECURITY MODE COMPLETE




Security mode complete message identity

'01011110'B Security mode complete

IMEISV Not present

NOTE:This message is always sent within SECURITY PROTECTED NAS MENetworkAGE message with new EPS security context.

11.1.24. SECURITY MODE REJECT


Table 11-24: SECURITY MODE REJECT




Security mode reject message identity

'01011111'B Security mode reject

EMM cause The value is set according to specific message content.



11.1.25. SERVICE REJECT






Service reject message identity

'01001110'B Service reject



NOTE:If this message includes the EMM cause set to #25, it is sent within SECURITY PROTECTED NAS MENetworkAGE message. Otherwise this message is sent without integrity protection.

11.1.26. SERVICE REQUEST


Table 11-26: SERVICE REQUEST



Security header type '1100'B Security header for the SERVICE REQUEST message

KSI and sequence number

Sequence number (short)

The 5 least significant bits of the NAS COUNT value applicable when this message is sent for sequence number.

KSI The effective KSI value.

Message authentication code

The 2 least significant octets of the resulting



(short) message authentication code

11.1.27. TRACKING AREA UPDATE ACCEPT


Table 11-27: TRACKING AREA UPDATE ACCEPT

Information Element



EMM

Security header type

'0000'B Plain NAS message, not security protected

Tracking area update accept message identity

'01001001'B Tracking area update accept

EPS update result

'0000'B TA updated TA_only

'0001'B combined TA/LA updated

combined_TA_LA


T3412 value Not present Periodic

T3412 value

Timer value '0 0000'B

Unit '111'B value indicates that the timer is deactivated.

GUTI

Length of EPS mobile identity contents

'0000 1011'B 11 octets

Type of identity '110'B GUTI

Odd/even indication

'0'B even number of identity digits and also when the GUTI is used


Information Element


MCC Refer to Table 6-10.

For NAS test cases, refer to Table 6-11.

MNC Refer to Table 6-10.


MME Group ID Refer to Table 6-10.


MME Code Refer to Table 6-10.


M-TMSI Refer to Table 6-10.


TAI list

Length of tracking area identity list contents

'0000 0110'B 6 octets

Partial tracking area identity list 1

Number of elements

'0 0000'B 1 element

Type of list '00'B list of TACs belonging to one PLMN, with non-consecutive TAC values

MCC Refer to Table 6-10.


MNC Refer to Table 6-10.


TAC 1 Refer to Table 6-10.



Information Element


EPS bearer context status

The same value as the value set in TRACKING AREA UPDATE REQUEST message


Not present TA_only


combined_TA_LA

MCC MCC of the EUTRA cell from which this message is sent

MNC MCC of the EUTRA cell from which this message is sent

LAC 1

MS identity Not present TA_only

MS identity combined_TA_LA

Length of mobile identity contents

'0000 0101'B 5 octets

Type of identity '100'B TMSI/P-TMSI/M-TMSI

Odd/even indication

'0'B even number of identity digits and also when the TMSI/P-TMSI or TMGI and optional MBMS Session Identity is used

TMSI TMSI-1




Equivalent PLMNs

Not present


Information Element


Emergency number list

Not present


0000 0001'B IMS voice over PS session in S1 mode supported


Not present


‘10’ B “SMS only” TAU_additional_update_result_SMS


TA_only This condition applies if the UE is configured to initiate EPS attach or if explicitly specified.

combined_TA_LA This condition applies if the UE is configured to initiate combined EPS/IMSI attach or if explicitly specified.

Periodic This condition applies if in the last TRACKING AREA UPDATE REQUEST sent prior to this message, the EPS update type Value = '011'B (periodic updating).

TAU_additional_update_result_SMS If the UE requested “SMS only” in the Additional update type IE and combined_TA_LA.


11.1.28. TRACKING AREA UPDATE COMPLETE


Table 11-28: TRACKING AREA UPDATE COMPLETE




Tracking area update complete message identity

'01001010'B Tracking area update complete



11.1.29. TRACKING AREA UPDATE REJECT


Table 11-29: TRACKING AREA UPDATE REJECT




Tracking area update rejectmessage identity

'01001011'B Tracking area update reject


NOTE:If this message includes the EMM cause set to #25, it is sent within SECURITY PROTECTED NAS MENetworkAGE message. Otherwise this message is sent without integrity protection.

11.1.30. TRACKING AREA UPDATE REQUEST


Table 11-30: TRACKING AREA UPDATE REQUEST




Tracking area update request message identity

'01001000'B Tracking area update request

EPS update type

EPS update typeValue '000'B TA updating TA_only

'001'B Combined TA/LA updating

combined_TA_LA

“Active” flag '0'B No bearer



establishment requested


NAS key set identifier Thevalid NAS key set identifier of the UE


Old GUTI Any allowed value

Non-current native NAS key set identifier

Not present

GPRS ciphering key sequence number

Not present

Old P-TMSI signature Not present

Additional GUTI Not present

NonceUE Not present

UE network capability Not present or any allowed value



DRX parameter Not present TA_only

DRX parameter Not present or any allowed value

combined_TA_LA

UE radio capability information update needed


EPS bearer context status

Not present or (octet 3 = '00100000'B and octet 4 = '00000000'B)

MS network capability Not present or any allowed value



TMSI status Not present or any allowed value







Supported Codecs Not present or any allowed value


Not present TA_only



combined_TA_LA


TA_only Refer to the definition in Table 7-31.

combined_TA_LA Refer to the definition in Table 7-31.


11.1.31. UPLINK NAS TRANSPORT


Table 11-31: UPLINK NAS TRANSPORT




Uplink NAS transport message identity

'0100 0011'B Uplink NAS transport

NAS message container



12. Appendix E

12.1. Contents of ESM Messages

12.1.1. ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT


Table 12-1: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT


Protocol discriminator ESM

EPS Bearer Identity The same value as the value set in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message


'0000 0000'B No procedure transaction identity assigned

Activate dedicated EPS bearer context accept message identity

'11000110'B Activate dedicated EPS bearer context accept




12.1.2. ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT

This message is sent by UE to the Network.

Table 12-2: ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT



EPS Bearer Identity The same value as the value set in ACTIVATE

Chapter Twelve: Appendix E | 305


DEDICATED EPS BEARER CONTEXT REQUEST message.



Activate dedicated EPS bearer context reject message identity

'11000111'B Activate dedicated EPS bearer context reject

ESM cause The value is set according to specific message content.


Not present


12.1.3. ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST


Table 12-3: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST



EPS Bearer Identity Arbitrarily selected value between '0101'B and '1111'B.



NETWORK-INITIATED

The same value as the value set in BEARER RESOURCE MODIFICATION REQUEST message or BEARER RESOURCE ALLOCATION REQUEST message

UE-INITIATED



Activate dedicated EPS bearer context request message identity

'11000101'B Activate dedicated EPS bearer context request


The EPS Bearer Identity of the associated default bearer


EPS QoS Refer toReference dedicated EPS bearer context #1 in Table 8-1.

TFT Refer toReference dedicated EPS bearer context #1 in Table 8-1.

Transaction identifier Not present

Distinct value between 0 and 127 calculated on basis of the EPS Bearer Identity.

pc_UTRAN AND/OR pc_GERAN

Negotiated QoS Refer toReference dedicated EPS bearer context #1 in Table 8-1.

Negotiated LLC SAPI Refer toReference dedicated EPS bearer context #1 in Table 8-1.

Radio priority Refer toReference dedicated EPS bearer context #1 in Table 8-1.

Packet flow Identifier Not present

'0000 0000'B Best Effort pc_GERAN


Refer toReference dedicated EPS bearer context #1 in Table 8-1.



NETWORK-INITIATED Network initiated ESM procedures

UE-INITIATED UE initiated ESM procedures

12.1.4. ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT


Table 12-4: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT



EPS Bearer Identity The same value as the value set in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message



Activate default EPS bearer context accept message identity

'11000010'B Activate default EPS bearer context accept




12.1.5. ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT

This message is sent by UE to the Network.

Table 12-5: ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT



EPS Bearer Identity The same value as the value set in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.





Activate default EPS bearer context reject message identity

'11000011'B Activate default EPS bearer context reject



Not present


12.1.6. ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST


Table 12-6: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

Information Element



ESM

EPS Bearer Identity

An arbitrarily selected value between '0101'B and '1111'B.


The same value as the value set in the latest PDN CONNECTIVITY REQUEST message sent prior to this message.

Activate default EPS bearer context request message identity

'11000001'B Activate default EPS bearer context request

EPS QoS Refer to the default EPS bearer context #1 in Table 8-1. NOT IMS APN

EPS QoS Refer to the default EPS bearer context #2 in Table 8-1. IMS APN

Access Point Name

The Network defines a Default APN or, if the UE transmits an ESM INFORMATION RESPONSE message providing an APN, the Network shall use this value

NOT IMS APN


Information Element


Access Point Name

IMS.apn.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org

The <MNC> and<MCC> are set to the same values as in IMSI.

IMS APN

PDN address IPv4

Length of PDN address contents

5 octets

PDN type value ‘001’B IPv4

PDN address information

IPv4 address The Network provides a valid IPv4 address

NOT IPv4-DHCP

0.0.0.0 DHCPv4 is to be used to allocate the IPv4 address

IPv4-DHCP

PDN address IPv6


9 octets

PDN type value ‘010’B IPv6

PDN address information

IPv6 interface identifier The Network provides a valid IPv6 interface identifier

PDN address IPv4v6


13 octets

PDN type value ‘011’B IPv4v6

PDN address information (Octets 4 to 11)

IPv6 interface identifier The Network provides a valid IPv6 interface identifier

PDN address information (Octets 12 to 15)

IPv4 address The Network provides a valid IPv4 address

NOT IPv4-DHCP

0.0.0.0 DHCPv4 is to be used to allocate the IPv4 address

IPv4-DHCP


Information Element


Transaction identifier

Not present

Distinct value between 0 and 127 calculated on basis of the EPS Bearer Identity.

pc_UTRAN AND/OR pc_GERAN

Negotiated QoS

Refer toReference default EPS bearer context #1 in Table 8-1.

Negotiated LLC SAPI


Radio priority Refer toReference default EPS bearer context #1 in Table 8-1.

Packet flow Identifier

Not present


APN-AMBR Refer toReference default EPS bearer context #1 in Table 8-1.

ESM cause Not present


Configuration protocol


Container ID 1 ‘0001’H P-CSCF IPv6

Length of container ID 1 contents

Length value determined by the TTCN implementation

Container ID 1 contents

IPv6 address P-CSCF IPv6 Address

Container ID 1 ‘000C’H P-CSCF IPv4

Length of container ID 1 contents

Length value determined by the TTCN implementation

Container ID 1 contents

IPv4 address P-CSCF IPv4 Address



IPv4 If in the last PDN CONNECTIVITY REQUEST sent prior to this message, the PDN type = '001'B

IPv6 If in the last PDN CONNECTIVITY REQUEST sent prior to this message, the PDN type = '010'B

IPv4v6 If in the last PDN CONNECTIVITY REQUEST sent prior to this message, the PDN type = '011'B

IPv4-DHCP If in the last PDN CONNECTIVITY REQUEST sent prior to this message, the IE Protocol configuration options contains a configuration protocol option = '000B00H' (“IPv4 address allocation via DHCPv4”, length of contents = 0).

Note: This condition is used in conjunction with IPv4 or IPv4v6 as indicated in the “PDN address row” just above.

P-CSCF IPv6 If in the last PDN CONNECTIVITY REQUEST sent prior to this message, the Protocol configuration options and the additional parameter list was included with a “P-CSCF IPv6 Address Request”

Note: This condition is only applicable for UEs with IMS support (TS 36.523-2 A.4.4-1/25).

P-CSCF IPv4 If in the last PDN CONNECTIVITY REQUEST sent prior to this message, the Protocol configuration options and the additional parameter list was included with a “P-CSCF IPv4 Address Request”

Note: This condition is only applicable for UEs with IMS support (TS 36.523-2 A.4.4-1/25).

IMS APN If the UE indicate IMS support (TS 36.523-2 A.4.4-1/25).


12.1.7. BEARER RESOURCE ALLOCATION REJECT


Table 12-7: BEARER RESOURCE ALLOCATION REJECT





EPS Bearer Identity '0000'B No EPS Bearer Identity assigned


The value indicated in BEARER RESOURCE ALLOCATION REQUEST message.

Bearer resource allocation reject message identity

'11010101'B Bearer resource allocation reject

ESM cause Set according to specific message content.


Not present


12.1.8. BEARER RESOURCE ALLOCATION REQUEST


Table 12-8: BEARER RESOURCE ALLOCATION REQUEST





Any value from 1 to 254

Bearer resource allocation request message identity

'11010100'B Bearer resource allocation request


The EPS Bearer Identity of the associated default bearer.


Traffic flow aggregate

Number of packet Greater than 0 and



filters less than or equal to 16

E bit Anyallowed value

TFT operation code '001'B Create new TFT

Packet filter list Anyallowed value

Parameters list Not present or anyallowed value

Required traffic flow QoS

Any allowed value




12.1.9. BEARER RESOURCE MODIFICATION REJECT


Table 12-9: BEARER RESOURCE MODIFICATION REJECT





The value indicated in BEARER RESOURCE MODIFICATION REQUEST message.

Bearer resource modification reject message identity

'11010111'B Bearer resource modification reject



Not present



12.1.10. BEARER RESOURCE MODIFICATION REQUEST


Table 12-10: BEARER RESOURCE MODIFICATION REQUEST






Bearer resource modification request message identity

'11010110'B Bearer resource modification request

EPS Bearer Identity for packet filter

The EPS Bearer Identity of the associated dedicated EPS bearer related with packet filter.


Traffic flow aggregate Anyallowed value

Traffic flow aggregate RELEASE-REQUESTED

Number of packet filters

Greater than 0 and less than or equal to 16

E bit Anyallowed value

TFT operation code '101'B Delete packet filters from existing TFT

Packet filter list Anyallowed value

Parameters list Not present or anyallowed value

Required traffic flow QoS


ESM cause Not present

'0010 0100'B Regular deactivation RELEASE-REQUESTED


RELEASE-REQUESTED UE requeststhe release of bearer resources.

NOTE:This message is always sent within SECURITY PROTECTED NAS


MENetworkAGE message.

12.1.11. DEACTIVATE EPS BEARER CONTEXT ACCEPT


Table 12-11: DEACTIVATE EPS BEARER CONTEXT ACCEPT



EPS Bearer Identity The same value as the value set in DEACTIVATE EPS BEARER CONTEXT REQUEST message.


'00000000'B No procedure transaction identity assigned

Deactivate EPS bearer context accept message identity

'11001110'B Deactivate EPS bearer context accept


Not present



12.1.12. DEACTIVATE EPS BEARER CONTEXT REQUEST


Table 12-12: DEACTIVATE EPS BEARER CONTEXT REQUEST



EPS Bearer Identity Set according to specific message content.



NETWORK-INITIATED

The same value as the value set in PDN DISCONNECT REQUEST message or BEARER RESOURCE MODIFICATION REQUEST message.

UE-INITIATED

Deactivate EPS bearer context request message identity

'11001101'B Deactivate EPS bearer context request



Not present






12.1.13. ESM INFORMATION REQUEST


Table 12-13: ESM INFORMATION REQUEST





The value indicated in PDN CONNECTIVITY REQUEST message.

ESM information request message identity

'11011001'B ESM information request


12.1.14. ESM INFORMATION RESPONSE


Table 12-14: ESM INFORMATION RESPONSE





The same value as the value set inESM INFORMATION REQUEST message.

ESM information response message identity

'11011010'B ESM information response

Access Point Name Not present or any allowed value





12.1.15. ESM STATUS

This message is sent by the UE or by the Network.

Table 12-15: ESM STATUS






ESM status message identity

'11101000'B ESM status



12.1.16. MODIFY EPS BEARER CONTEXT ACCEPT


Table 12-16: MODIFY EPS BEARER CONTEXT ACCEPT



EPS Bearer Identity The same value as the value set in MODIFY EPS BEARER CONTEXT REQUEST message.



Modify EPS bearer context accept message identity

'11001010'B Modify EPS bearer context accept




Not present


12.1.17. MODIFY EPS BEARER CONTEXT REJECT


Table 12-17: MODIFY EPS BEARER CONTEXT REJECT



EPS Bearer Identity The same value as the value set in MODIFY EPS BEARER CONTEXT REQUEST message.



Modify EPS bearer context reject message identity

'11001011'B Modify EPS bearer context reject



Not present


12.1.18. MODIFY EPS BEARER CONTEXT REQUEST


Table 12-18: MODIFY EPS BEARER CONTEXT REQUEST








NETWORK-INITIATED

The same value as the value set in BEARER RESOURCE MODIFICATION REQUEST messageor BEARER RESOURCE ALLOCATION REQUEST message.

UE-INITIATED

Modify EPS bearer context request message identity

'11001001'B Modify EPS bearer context request

New EPS QoS Use the same value as used in Activate EPSBearer Context Request message

TFT According to reference dedicated EPS bearer context #2except for TFT operation code which is set to ‘100’B and TFT identifier is set to ‘00110000’B..

New QoS Not Present.

Negotiated LLC SAPI Not Present.

Radio priority Not Present.

Packet flow Identifier Not Present.


APN-AMBR Not Present.


Not present







12.1.19. PDN CONNECTIVITY REJECT


Table 12-19: PDN CONNECTIVITY REJECT





The same value as the value set in PDN CONNECTIVITY REQUEST message.

PDN connectivity reject message identity

'11010001'B PDN connectivity reject



Not present


12.1.20. PDN CONNECTIVITY REQUEST










PDN connectivity request message identity

'11010000'B PDN connectivity request

Request type '0001'B initial request

PDN type Any value between '001'B, '010'B, '011'B and '100'B

The allowed values are respectively IPv4, IPv6, IPv4v6 and “unused but interpreted as IPv6 by the network”

ESM informationtransfer flag


Access Point Name Not present The value is mandatory when the PDN CONNECTIVITY REQUEST message is sent together with an ATTACH REQUEST message.



The value received from the UE does not affect the possible verdict associated with the message when received by the Network. The Network shall remember if this IE is present and its contents because this affects subsequent Network behavior, e.g. coding of ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST.



12.1.21. PDN DISCONNECT REJECT


Table 12-21: PDN DISCONNECT REJECT





The value indicated in PDN DISCONNECT REQUEST message.

PDN disconnect reject message identity

'11010011'B PDN disconnect reject



Not present


12.1.22. PDN DISCONNECT REQUEST


Table 12-22: PDN DISCONNECT REQUEST








PDN disconnect request message identity

'11010010'B PDN disconnect request


The EPS Bearer Identity of the associated default bearer.



Not present


13. Appendix F

13.1. General Parameters for Cell Configuration

Test Parameters Range

Frequency Band 4, 13, 7, 17

PDN Type IPv4, IPv6

APN InternetPDN, IMS

Authentication Parameters VZW UICC; Spirent USIM

RSTP -40 to -120 dBm

PDSCH channel Power pA = -6, 0, 3; pB = 0, 3

Transmission Mode TM1, TM2, TM3, TM4, TM6

Downlink Bandwidth 5MHz, 10 MHz, 20 Mhz

Scheduling Mode Static, Autonomous

Modulation (UL/DL) QPSK, 16QAM

14. Appendix G

14.1. Default Messages for IMS Registration Table 14-1: REGISTER

Header/param Cond Value/remark

Request-Line

Method REGISTER

Request-URI SIP URI formed from px_HomeDomainName (when using ISIM) or

SIP URI formed from home domain name derived from px_IMSI (when no ISIM available on the UICC)

SIP-Version SIP/2.0

Route (if present)

route-param A1, A3 <sip:px_pcscf;lr>

route-param A2 <sip:px_pcscf:protected server port of P-CSCF;lr>

<sip:px_scscf;lr>(optional for Re-REGISTER)

Via

sent-protocol SIP/2.0/UDP (when using UDP) or

SIP/2.0/TCP (when using TCP)

sent-by A1, A3 IP address or FQDN, port (optional) and not checked

sent-by A2 IP address or FQDN and protected server port of the UE

via-branch value starting with ‘z9hG4bk’

response-port A1 rport

From

addr-spec A1, A2 any IMPU within the set of IMPUs on ISIM (when using ISIM) or

public user identity derived from px_IMSI (when no ISIM available on the UICC)

addr-spec

addr-spec

A3

A7

public user identity derived from px_IMSI

px_EmergencyPublicUserIdentity(if the UE is already registered to IMS or if the UE is using ISIM) or public user identity derived from px_IMSI (when UE is using USIM and UE is not yet registered to IMS)

tag must be present, value not checked

To

addr-spec A1, A2 any IMPU within the set of IMPUs on ISIM (when using ISIM) or



public user identity derived from px_IMSI (when no ISIM available on the UICC)

addr-spec

addr-spec

A3

A7

public user identity derived from px_IMSI px_EmergencyPublicUserIdentity(if the UE is already registered to IMS or if the UE is using ISIM) or public user identity derived from px_IMSI (when UE is using USIM and UE is not yet registered to IMS)

tag must not be present

Contact

addr-spec A1, A3 SIP URI to either indicate an unprotected port selected by the UE or no port at all. When A7 the SIP URI shall contain the req-type=sos URI parameter.

addr-spec A2 SIP URI with IP address or FQDN and protected server port of UE. When A7 the SIP URI shall contain the req-type=sos URI parameter.

feature-param A4 +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel" (see NOTE 2)

feature-param A6 +g.3gpp.smsip

c-p-instance A5 +sip.instance media feature tag with the instance ID of the UE

expires

600000 (if present)

Expires (if present)

delta-seconds 600000

Require A1, A2

option-tag sec-agree

Proxy-Require A1, A2


Supported

option-tag A5 gruu

option-tag path

CSeq

value A1, A3 must be present, value not checked

value A2 must be incremented from the previous REGISTER

method REGISTER

Call-ID

callid value not checked

Security-Client A1, A2

mechanism- ipsec-3gpp



name

algorithm hmac-md5-96

protocol esp (if present)

mode trans (if present)

encrypt-algorithm

des-ede3-cbc or aes-cbc, if UE supports IPSec ESP confidentiality protection null or parameter not present, if the UE does not support IPSec ESP confidentiality protection

spi-c SPI number of the inbound SA at the protected client port

spi-s SPI number of the inbound SA at the protected server port

port-c protected client port

port-s protected server port

mechanism-name

ipsec-3gpp

algorithm hmac-sha-1-96

protocol esp (if present)

mode trans (if present)

encrypt-algorithm

des-ede3-cbc or aes-cbc, if UE supports IPSec ESP confidentiality protection null or parameter not present, if the UE does not support IPSec ESP confidentiality protection



port-c protected client port

port-s protected server port

Security-Verify A2 (not present when A1, A3)

sec-mechanism A2 same value as SecurityServer header sent by SS

Authorization A1

username A1 px_PrivateUserIdentity (when using ISIM) or

private user identity derived from px_IMSI (when no ISIM available on the UICC)

realm A1 px_HomeDomainName (when using ISIM) or

home domain name derived from px_IMSI (when no ISIM available on the UICC)

nonce A1 set to an empty value

digest-uri A1 SIP URI formed from px_HomeDomainName (when using ISIM) or formed from home domain name derived from px_IMSI (when no ISIM



available on the UICC)

response A1 set to an empty value

Authorization A2

username A2 px_PrivateUserIdentity (when using ISIM) or

private user identity derived from px_IMSI (when no ISIM available on the UICC)

realm A2 same value as received in the realm directive in the WWW Authenticate header sent by SS

nonce A2 same value as in WWW-Authenticate header sent by SS

opaque A2 px_Opaque

digest-uri A2 SIP URI formed from px_HomeDomainName (when using ISIM) or formed from home domain name derived from px_IMSI (when no ISIM available on the UICC)

qop-value A2 auth

cnonce-value A2 value assigned by UE affecting the response calculation

nonce-count A2 counter to indicate how many times UE has sent the same value of nonce within successive REGISTERs, initial value shall be 1

response A2 response calculated by UE

algorithm A2 AKAv1-MD5

Max-Forwards

value non-zero value

P-Access-Network-Info A2 (header optional when A1, A3)

access-net-spec A2 access network technology and, if applicable, the cell ID

Content-Length

value length of request body, if such is present


A1 Initial unprotected REGISTER (IMS security, A.6a/2 3GPP TS 34.229-2 [5])

A2 Subsequent REGISTER sent over security associations (IMS security, A.6a/2 3GPP TS 34.229-2 [5])

A3 REGISTER for the case UE supports GIBA (A.6a/1 3GPP TS 34.229-2 [5])

A4 The UE supports IMS Multimedia Telephony (MTSI) (G.12/18 3GPP TS 34.229-2 [5])

A5 obtaining and using GRUUs in the Session Initiation Protocol (SIP) (A.4/53 3GPP TS 34.229-2 [5])

A6

A7

The UE supports SM-over-IP receiver (A.12/nn 3GPP TS 34.229-2 [5])

Initial IMS emergency registration


NOTE 1: All choices for applicable conditions are described for each header. NOTE 2: The “=” may include optional linear white spaces according to the EQUAL definition in chapter 25.1, RFC 3261 [15].

Table 14-2: 401 Unauthorized for REGISTER


Status-Line

SIP-Version SIP/2.0

Status-Code 401

Reason-Phrase Unauthorized

Via

via-parm same value as received in REGISTER message

To

addr-spec same value as received in REGISTER message

tag px_ToTagRegister

From


tag same value as received in REGISTER message

Call-ID

callid same value as received in REGISTER message

CSeq

value same value as received in REGISTER message

WWW-Authenticate

realm px_HomeDomainName or home domain name derived from px_IMSI NOTE: this value could be set different by the SS (see CP-060230)

algorithm AKAv1-MD5

qop-value auth

nonce Base 64 encoding of RAND and AUTN

opaque px_Opaque

Security-Server

mechanism-name ipsec-3gpp

algorithm px_IpSecAlgorithm (hmac-md5-96 or hmac-sha-1-96)



port-c px_SSProtectedClientPort

port-s px_SSProtectedServerPort

Encrypt-algorithm des-ede3-cbc or aes-cbc, if UE supports IPSec ESP confidentiality protection



(px_CiphAlgo_Def)

q 0.9

Mechanism-name Ipsec-3gpp

algorithm Algorithm not selected by px_IpSecAlgorithm (hmac-sha-1-96 or hmac-md5-96)



port-c px_SSProtectedClientPort

port-s px_SSProtectedServerPort

encrypt-algorithm des-ede3-cbc or aes-cbc, if UE supports IPSec ESP confidentiality protection (px_CiphAlgo_Def)

q 0.7

Content-Length

value 0

Table 14-3: 200 OK for REGISTER


Status-Line

SIP-Version SIP/2.0

Status-Code 200

Reason-Phrase OK

Via


To



From


tag same value as received in REGISTER message

Call-ID


CSeq


Contact


pub-gruu A1 Public GRUU as the SIP URI got from the To header of the REGISTER request, together with the gr parameter with an



arbitrary value

temp-gruu A1 Temporary GRUU with an arbitrary value in the user part and the host part matching with the domain of the To header of the REGISTER and gr parameter without any value (temp-gruu parameter missing when A3)

expires px_RegisterExpiration

P-Associated-URI order of the parameters in this header must be like in this table

addr-spec A2 all the IMPUs within the set of IMPUs on ISIM

addr-spec

A2

px_AssociatedTelUri any arbitrary TEL URI for the user

addr-spec A3 px_EmergencyPublicUserIdentity

Service-Route (header missing when A3)

addr-spec A2 px_scscf

uri-parameter lr

Path

addr-spec px_pcscf

uri-parameter lr

Content-Length

value 0



A2 Response for an non-emergency registration

A3 Response for an emergency registration

Table 14-4: SUBSCRIBE for Reg-event Package


Request-Line

Method SUBSCRIBE

Request-URI any IMPU within the set of IMPUs on ISIM

SIP-Version SIP/2.0

Route order of the parameters in this header must be like in this table

route-param A1 <sip:px_pcscf:protected server port of P-CSCF;lr>, <sip:px_scscf;lr>

route-param A2 <sip:px_pcscf: unprotected server port of P-CSCF (optional);lr>, <sip:px_scscf;lr>



Via

sent-protocol SIP/2.0/UDP when using UDP or SIP/2.0/TCP when using TCP


sent-by A2 IP address or FQDN, port (optional) and not checked


From

addr-spec any IMPU within the set of IMPUs on ISIM

tag must be present, value not checked but stored for later reference

To



Contact

addr-spec A1 SIP URI with IP address or FQDN and protected server port of UE or GRUU as returned by the SS in registration

addr-spec A2 SIP URI with IP address or FQDN and unprotected server port of UE or GRUU as returned by the SS in registration

Expires


Security-Verify A1

sec-mechanism same value as SecurityServer header sent by SS

Require A1


Proxy-Require A1


CSeq

value must be present, value not checked

method SUBSCRIBE

Call-ID

callid value not checked, but stored for later reference

Max-Forwards


P-Access-Network-Info A1 (header optional when A2)

access-net-spec access network technology and, if applicable, the cell ID

Accept (if present)

media-range application/reginfo+xml



Event

event-type reg

Content-Length



A1 IMS security (A.6a/2 3GPP TS 34.229-2 [5])

A2 GIBA (A.6a/1 3GPP TS 34.229-2 [5])

NOTE: All choices for applicable conditions are described for each header.

Table 14-5: 200 OK for SUBSCRIBE


Status-Line

SIP-Version SIP/2.0

Status-Code 200

Reason-Phrase OK

Via

via-parm same value as received in SUBSCRIBE message

To


tag px_ToTagSubscribeDialog

From

addr-spec same value as received in SUBSCRIBE message

tag same value as received in SUBSCRIBE message

Call-ID

callid same value as received in SUBSCRIBE message

CSeq

value same value as received in SUBSCRIBE message

Contact

addr-spec <sip:px_scscf>

Expires


Record-Route

addr-spec A1 px_pcscf: protected server port of SS

addr-spec A2 px_pcscf: unprotected server port of SS (optional)



uri-parameter lr

Content-Length

value 0



A2 GIBA (A.6a/1 3GPP TS 34.229-2 [5])


Table 14-6: NOTIFY for Reg-event Package


Request-Line

Method NOTIFY

Request-URI A1 SIP URI with IP address or FQDN and protected server port of UE

Request-URI A2 SIP URI with IP address or FQDN and unprotected server port of UE

SIP-Version SIP/2.0

Via order of the parameters in this header must be like in this table

via-parm1:

Sent-protocol

SIP/2.0/UDP when using UDP or SIP/2.0/TCP when using TCP

sent-by A1 IP address and protected server port of SS

sent-by A2 IP address and unprotected server port of SS (optional)

via-branch

value starting with ‘z9hG4bk’

via-parm2:

sent-protocol


sent-by px_scscf

via-branch


From



To




tag same value as received in From tag of SUBSCRIBE message

Call-ID

callid same as value received in SUBSCRIBE message

CSeq A1,A2

value 1

method NOTIFY

Contact


Content-Type

media-type application/reginfo+xml

Event A1,A2

event-type reg

Max-Forwards

value 69

Subscription-State

substate-value active

expires 600000

Content-Length


Message-body A3 <?xml version=”1.0?>

<reginfo xmlns=”urn:ietf:params:xml:ns:reginfo” version=”0” state=”full”>

<registration aor=”px_PublicUserIdentity1” id=”a100” state=”active”>

<contact id=”980” state=”active” event=”registered”>

<uri>same value as in Contact header of REGISTER request</uri>

</contact>

</registration>

<registration aor=”px_AssociatedTelUri” id=”a101” state=”active”>

<contact id=”981” state=”active” event=”created”>


</contact>

</registration>






</contact>

</registration>




</contact>

</registration>

</reginfo>

A4 <?xml version=”1.0?>

<reginfo xmlns=”urn:ietf:params:xml:ns:reginfo” xmlns:gr="urn:ietf:params:xml:ns:gruuinfo" version=”0” state=”full”>


<contact id=”980” state=”active” event=”registered” callid="Call-Id of most recent REGISTER" cseq="CSeq value of most recent REGISTER">

<uri>same value as in Contact header of REGISTER request</uri> <allOneLine>

<unknown-param name="+sip.instance">

"Instance ID of the UE;"

</unknown-param>

</allOneLine>

<allOneLine>

<gr:pub-gruu uri="public GRUU for the UE"/>

</allOneLine>

<allOneLine>

<gr:temp-gruu uri="temporary GRUU for the UE" first-cseq="CSeq of the REGISTER request that caused the temporary GRUU to assigned for the UE"/>

</allOneLine>

</contact>

</registration>

<registration aor=”px_AssociatedTelUri” id=”a101” state=”active”>

<contact id=”981” state=”active” event=”created”>


<allOneLine>





</unknown-param>

</allOneLine>

<allOneLine>


</allOneLine>

<allOneLine>


</allOneLine>

</contact>

</registration>

<registration aor=”px_PublicUserIdentity2” id” id=”a102” state=”active”>





</unknown-param>

</allOneLine>

<allOneLine>


</allOneLine>

<allOneLine>


</allOneLine>

</contact>

</registration>

<registration aor=”px_PublicUserIdentity3” id” id=”a103” state=”active”>







</unknown-param>

</allOneLine>

<allOneLine>


</allOneLine>

<allOneLine>


</allOneLine>

</contact>

</registration>

</reginfo>



A2 GIBA (A.6a/1 3GPP TS 34.229-2 [5]

A3 NOT obtaining and using GRUUs in the Session Initiation Protocol (SIP) (A.4/53 3GPP TS 34.229-2 [5])



Table 14-7: 423 Interval Too Brief for REGISTER


Status-Line

SIP-Version SIP/2.0

Status-Code 423

Reason-Phrase Interval Too Brief

Via


To



From




Call-ID


CSeq


Min-Expires

delta-seconds T (a decimal integer number of seconds from 0 to

(2**32)-1)

Table 14-8: 420 Bad Extension for REGISTER


Status-Line

SIP-Version SIP/2.0

Status-Code 420

Reason-Phrase Bad Extension

Via


To



From


Call-ID


CSeq


Unsupported


14.2. Default Messages for Call Setup Table 14-9: INVITE for MO Call Setup


Request-Line

Method INVITE

Request-URI A4 Px_CalleeUri



px_CalleeURI may be either SIP or Tel URI. It may contain a dialstring and phone-context parameter, when calling to dialstring. When calling to dialstring SIP URI must also contain user=phone or user=dialstring parameter.

The dialstring, if used, may be global, home local number or geo-local number. For home local numbers the value of phone-context parameter must equal the home domain name i.e. px_HomeDomainName. For geo-local numbers the home domain name must be prefixed by string “geo-local.” or access technology specific prefix, if the UE supports that option.

Note: The way how the UE determines whether numbers in a non-international format are geo-local, home-local or relating to another network, is UE implementation specific. For instance the UE might have a UI setting.

Request-URI A5 px_CalleeContactUri

Request-URI A6, A7 emergency service URN beginning as urn:service:sos

SIP-Version SIP/2.0

Via



sent-by A1, A7 IP address or FQDN and protected server port of the UE

A2 IP address or FQDN, port (optional) and not checked

A6 IP address and unprotected server port of the UE

response-port A6 rport

via-branch



route-param A1 <sip:px_pcscf:px_SSProtectedServerPort;lr>, <sip:px_scscf;lr>

A2 <sip:px_pcscf:px_SSUnprotectedServerPort (optional);lr>, <sip:px_scscf;lr

A6 <sip:px_pcscf:px_SSUnprotectedServerPort>

A7 <sip:px_pcscf:px_SSProtectedServerPort>

From

addr-spec A6 Any SIP URI with display name as “Anonymous”

A7 px_EmergencyPublicUserIdentity



A4 any SIP URI (except public user identity derived from px_IMSI) matching with the URI within the P-Preferred-Identity header or any IMPU within the set of IMPUs on ISIM if there is no P-Preferred-Identity header within the INVITE request

Tag A4 must be present, value not checked

addr-spec A5 local SIP URI of the UE as used in any previous request in the same dialog (In the earlier requests within the same dialog this URI appears in From header within requests sent by the UE and in To header within requests sent by the SS)

Tag A5 local tag value corresponding to the SIP URI of the UE in the same dialog. (In the earlier requests within the same dialog this tag appears in From header within requests sent by the UE and in To header within requests sent by the SS)

To

addr-spec A6, A7 emergency service URN beginning as urn:service:sos

addr-spec A4 px_CalleeUri

tag A4 not present

addr-spec A5 remote SIP URI of SS (i.e. the remote UE) as used in any previous request in the same dialog (In the earlier requests within the same dialog this URI appears in To header within requests sent by the UE and in From header within requests sent by the SS)

Tag A5 remote tag value corresponding to the SIP URI of the SS in the same dialog. (In the earlier requests within the same dialog this tag appears in To header within requests sent by the UE and in From header within requests sent by the SS)

Call-ID

Callid A4 value different to that received in REGISTER message

Callid A5 value of Call-ID as in any previous request in the same dialog

Cseq

Value A4 must be present, value not checked

Value A5 value of CSeq sent by the UE within its previous request in the same dialog but increased by one

Method INVITE

Supported

option-tag 100rel

option-tag A8 geolocation

Geolocation A8

locationURI cid-url indicating the Content-Id of the PIDF-LO within the multipart MIME body of INVITE request.



(Note that location-by-reference URI is not allowed as the SS does not provide any external storage for location info for the UE to refer.)

inserted-param inserted-by=“ value of sent-by within the Via header”

routing-param routing-allowed=yes

Require (header optional in A2 and not present in A6)

option-tag A1, A7 sec-agree

Proxy-Require (header optional in A2 and not present in A6)

option-tag A1, A7 sec-agree

Security-Verify A1, A7 (not present in A2 or A6)


Contact

addr-spec A1, A7 SIP URI with IP address or FQDN and protected server port of UE or GRUU as returned by the SS in registration

A2 SIP URI with IP address or FQDN and unprotected server port of UE or GRUU as returned by the SS in registration

A6 SIP URI with IP address and unprotected server port of UE

feature-param A6

+sip.instance="<urn:gsma:imei:<gsma-specifier-defined-substring>” where gsma-specifier-defined-substring shall be the IMEI code of the UE, coded as specified in draft-montemurro-gsma-imei-urn, without optional parameters

A3 +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel" (see NOTE 2)

Content-Type

media-type application/sdp or

multipart/mixed (when A8)

Max-Forwards

Value non-zero value

P-Access-Network-Info (header optional when A2)


Accept (header optional when A5)

Media-range A4 application/sdp,application/3gpp-ims+xml (additional medias can be added in any order)



P-Preferred-Service

Service-ID A3 urn:urn-7:3gpp-service.ims.icsi.mmtel

P-Preferred-Identity

PPreferredID-value A7 px_EmergencyPublicUserIdentity

Accept-Contact

ac-value A3 +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel" (see NOTE 2)

Content-Length


Message-body The message body shall contain the following elements:

a) SDP offer, contents as specified within the specific test cases referring to this common message. If condition A8 applies the SDP shall be one element within the multipart-MIME encapsulation;

b) if condition A8 applies, the multipart-mime body shall also contain a PIDF-LO element be mapped to the same Content-ID which can be found from the Geolocation header

The PIDF-LO shall contain at least the following elements:

- One or more 'geopriv' elements, each containing:

- One 'location-info' element describing the location of the UE. The coordinates given in this element shall match with the related input signals given by the test environment, within the accuracy provided by the positioning method used by the UE; and

- One 'usage-rules' element describing the limitations of the usage of the location info.



A2 GIBA (A.6a/1 3GPP TS 34.229-2 [5])

A3 UE supports MTSI (A.12/18 3GPP TS 34.229-2 [5])

A4 INVITE creating a dialog

A5 re-INVITE within a dialog

A6 INVITE for creating an emergency session in case of no registration

A7 INVITE for creating an emergency session within an emergency registration

A8 UE uses Geolocation header to provide its geographical location for emergency session setup, has obtained its location and is setting up an emergency session


NOTE 1: All choices for applicable conditions are described for each header. NOTE 2: The “=” may include optional linear white spaces according to the EQUAL definition in chapter 25.1, RFC 3261 [15].

Table 14-10: 100 Trying for INVITE


Status-Line

SIP-Version SIP/2.0

Status-Code 100

Reason-Phrase Trying

Via

via-parm same value as received in INVITE message

From

addr-spec same value as received in INVITE message

tag same value as received in INVITE message

To


tag not present

Call-ID

callid same value as received in INVITE message

CSeq

value same value as received in INVITE message

Content-Length

value 0

Table 14-11: 183 Session Progress for INVITE


Status-Line

SIP-Version SIP/2.0

Status-Code 183

Reason-Phrase Session Progress

Record-Route order of the parameters in this header must be like in this table

rec-route A1,A2 <sip:pcscf.other.com;lr>, <sip:scscf.other.com;lr>,<sip:orig@px_scscf;lr>, <sip:px_pcscf:px_SSProtectedServerPort;lr>

rec-route A3,A4 <sip:pcscf.other.com;lr>, <sip:scscf.other.com;lr>,<sip:orig@px_scscf;lr>, <sip:px_pcscf:px_SSUnprotectedServerPort (optional);lr>

Via




Require

option-tag

100rel

From



To


tag px_InviteToTag

P-Asserted-Identity A5 px_EmergencyTelURI

addr-spec A tel URI that can be recognized as valid emergency numbers if dialled by the user are specified in 3GPP TS 22.101 [39]. The emergency numbers 112 and 911 are stored on the ME, in accordance with 3GPP TS 22.101 [39]

uri-parameter lr

Contact

addr-spec A1, A3 px_CalleeContactUri

addr-spec A2 SIP URI with IP address or FQDN and protected server port of UE

addr-spec A4 SIP URI with IP address or FQDN and unprotected server port of UE

feature-param +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"(see NOTE 2)

Rseq

response-num px_RSeqNumFor183

Call-ID


CSeq


Allow

method UPDATE

Content-Type


Content-Length




A1 183 sent by the SS (IMS security ,A.6a/2 3GPP TS 34.229-2 [5])

A2 183 sent by the UE (IMS security ,A.6a/2 3GPP TS 34.229-2 [5])

A3 183 sent by the SS (GIBA, A.6a/1 3GPP TS 34.229-2 [5])

A4 183 sent by the UE (GIBA, A.6a/1 3GPP TS 34.229-2 [5])

A5 183 sent by the SS for INVITE for creating an emergency session

NOTE 1: All choices for applicable conditions are described for each header.

NOTE 2: The “=” may include optional linear white spaces according to the EQUAL definition in Chapter 25.1, RFC 3261 [15].

Table 14-12: PRACK


Request-Line

Method PRACK

Request-URI same URI value as the recipient of PRACK has earlier sent in its Contact header within the same dialog

SIP-Version SIP/2.0

Via



sent-by same value as in INVITE message

via-branch


Route (header missing when A3 or A4)

route-param A1, A2 URIs of the Record-Route header of 183 response (or 180 when applicable) in reverse order

From

addr-spec SIP URI of the UE when PRACK is sent by the UE, but SIP URI of the SS when PRACK is sent by the SS. URI must be the same as used for the endpoint in the earlier requests within the dialog.

tag tag value corresponding to the SIP URI in the From header

To

addr-spec SIP URI of the SS when PRACK is sent by the UE, but SIP URI of the UE when PRACK is sent by the SS. URI must be the same as used for the endpoint in the earlier requests within the dialog.

tag tag value corresponding to the SIP URI in the To header

Call-ID




CSeq

value value as in reliable response incremented by one

method PRACK

Max-Forwards


RAck

response-num same value as in RSeq header of the reliable response

cseq-num same value as in CSeq of reliable response

method same value as in CSeq of reliable response

P-Access-Network-Info A1 (header optional when A2) , header missing when A3 or A4

access-net-spec

access network technology and, if applicable, the cell ID

Content-Type header shall be present only if there is SDP in message-body


Content-Length


Message-body Optional SDP body. If included then the contents of the SDP shall be checked as described in the Test requirements section of the test case.


A1 PRACK sent by the UE (IMS security ,A.6a/2 3GPP TS 34.229-2 [5])

A2 PRACK sent by the UE (GIBA, A.6a/1 3GPP TS 34.229-2 [5])

A3 PRACK sent by the SS (IMS security ,A.6a/2 3GPP TS 34.229-2 [5])

A4 PRACK sent by the SS (GIBA, A.6a/1 3GPP TS 34.229-2 [5])

Table 14-13: UPDATE


Request-Line

Method UPDATE

Request-URI same URI value as the recipient of UPDATE has earlier sent in its Contact header within the same dialog

SIP-Version SIP/2.0

Via






via-branch



route-param A1, A2 URIs of the Record-Route header of 183 response in reverse order

From

addr-spec SIP URI of the UE when UPDATE is sent by the UE, but SIP URI of the SS when UPDATE is sent by the SS. URI must be the same as used for the endpoint in the earlier requests within the dialog.


To

addr-spec SIP URI of the SS when UPDATE is sent by the UE, but SIP URI of the UE when UPDATE is sent by the SS. URI must be the same as used for the endpoint in the earlier requests within the dialog.


Call-ID


CSeq

value value of CSeq sent by the endpoint within its previous request in the same dialog but increased by one

method UPDATE

Require (header optional in A2) , header missing when A3 or A4

option-tag A1 sec-agree

Proxy-Require (header optional in A2) , header missing when A3 or A4

option-tag A1 Sec-agree

Max-Forwards

value Non-zero value

Security-Verify A1 (header missing when A2, A3 or A4)


P-Access-Network-Info A1 (header optional when A2) (header missing when A2, A3 or A4)

access-net-spec


Content-Type


Content-Length




Message-body Contents of the SDP body shall be checked as described in the Test requirements section of the test case.


A1 UPDATE sent by the UE (IMS security ,A.6a/2 3GPP TS 34.229-2 [5])

A2 UPDATE sent by the UE (GIBA, A.6a/1 3GPP TS 34.229-2 [5])

A3 UPDATE sent by the SS (IMS security ,A.6a/2 3GPP TS 34.229-2 [5])

A4 UPDATE sent by the SS (GIBA, A.6a/1 3GPP TS 34.229-2 [5])

NOTE1: All choices for applicable conditions are described for each header.

Table 14-14: 180 Ringing for INVITE


Status-Line

SIP-Version SIP/2.0

Status-Code 180

Reason-Phrase Ringing

Record-Route

rec-route as defined for the common 183 response, see G.2.3

Via


Require

option-tag

A3 100rel

From



To


tag as defined for the common 183 response, see G.2.3



uri-parameter lr



Contact

addr-spec as defined for the common 183 response, see G.2.3

Rseq

response-num A3 previous RSeq number sent in the same direction incremented by one

Call-ID


CSeq


P-Access-Network-Info (header missing when A1)

access-net-spec

A2 access network technology and, if applicable, the cell ID

Content-Length



A1 180 sent by the SS

A2 180 sent by the UE

A3 Response sent reliably (e.g. always when it contains an SDP body)

A4 180 sent by the SS when setting up an emergency call

Table 14-15: ACK


Request-Line

Method ACK

Request-URI same value as in PRACK message

SIP-Version SIP/2.0

Via


Route (header missing when A2)

route-param A1 URIs of the Record-Route header of 183, 180 or 200 response (whichever response used for INVITE to be acknowledged and contained Record-Route header) in reverse order

From

addr-spec SIP URI of the UE when BYE is sent by the UE, but SIP URI of the SS when BYE is sent by the SS. URI must be the same as used for the endpoint in the earlier requests within the dialog.




To

addr-spec SIP URI of the SS when BYE is sent by the UE, but SIP URI of the UE when BYE is sent by the SS. URI must be the same as used for the endpoint in the earlier requests within the dialog.


Call-ID


CSeq


method ACK

Max-Forwards


P-Access-Network-Info must not be present

Content-Length

value 0


A1 ACK sent by the UE

A2 ACK sent by the SS

Table 14-16: BYE


Request-Line

Method BYE

Request-URI same URI value as the recipient of BYE has earlier sent in its Contact header within the same dialog

SIP-Version SIP/2.0

Via






route-param A1, A2 URIs of the Record-Route header of 183 response in reverse order

From



addr-spec SIP URI of the UE when BYE is sent by the UE, but SIP URI of the SS when BYE is sent by the SS. URI must be the same as used for the endpoint in the earlier requests within the dialog.


To

addr-spec SIP URI of the SS when BYE is sent by the UE, but SIP URI of the UE when BYE is sent by the SS. URI must be the same as used for the endpoint in the earlier requests within the dialog.


Call-ID


CSeq

value value of CSeq sent by the UE within its previous request in the same dialog but increased by one

method BYE

Require (header optional in A2) , header missing when A3 or A4


Proxy-Require (header optional in A2) , header missing when A3 or A4


Max-Forwards


Security-Verify A1 (header missing when A2, A3 or A4)


P-Access-Network-Info A1 (header optional in A2) , header missing when A3 or A4


Content-Length

value length of message body


A1 BYE sent by the UE (IMS security ,A.6a/2 3GPP TS 34.229-2 [5])

A2 BYE sent by the UE (GIBA, A.6a/1 3GPP TS 34.229-2 [5])

A3 BYE sent by the SS (IMS security ,A.6a/2 3GPP TS 34.229-2 [5])

A4 BYE sent by the SS (GIBA, A.6a/1 3GPP TS 34.229-2 [5])



Table 14-17: INVITE for MT Call


Request-Line

Method INVITE

Request-URI A4 UE’s registered contact address in SIP URI form, as provided in the Contact header of the REGISTER message

Request-URI A5 UE’s contact address in SIP URI form, as provided in the Contact header within any response or request within the dialog

SIP-Version SIP/2.0

Via



sent-by A1 px_pcscf:px_SSProtectedServerPort

sent-by A2 IP address or FQDN and unprotected server port of the SS (optional)

via-branch

Value starting with ‘z9hG4bk’

Via In addition to the via-parm entry for the SS, the following via-parm entries are included:

via-parm SIP/2.0/UDP scscf1.3gpp.org;branch=z9hG4bK1234567890, SIP/2.0/UDP scscf2.3gpp.org;branch=z9hG4bK2345678901, SIP/2.0/UDP pcscf2.3gpp.org;branch=z9hG4bk3456789012,

SIP/2.0/UDP caller.3gpp.org:6543;branch=z9hG4bk4567890123

Note that the branch values shown above are examples only. All of them must start with the magic cookie z9hG4bk but SS can build the rest of the string in a random way.

Record-Route

rec-route A1 <sip:px_pcscf:px_SSProtectedServerPort;lr>

rec-route A2 SIP URI with FQDN or IP address and unprotected server port of the SS (optional)

Record-Route In addition to the rec-route entry for the SS, the following rec-route entries are included:

rec-route <sip:[email protected];lr>, <sip:[email protected];lr>, <sip:pcscf2.3gpp.org;lr>

From

addr-spec A4 an SIP URI of the SS representing the calling UE

tag A4 any value (e.g. abc1)

addr-spec A5 SIP URI of SS (i.e. the remote UE) as used in any previous request in the same dialog (In the earlier requests within the same dialog this URI appears in To header within requests sent by the UE and in From



header within requests sent by the SS)

tag A5 tag value corresponding to the SIP URI of the SS in the same dialog. (In the earlier requests within the same dialog this tag appears in To header within requests sent by the UE and in From header within requests sent by the SS)

To

addr-spec A4 SIP or TEL URI of the UE

tag A4 not present

addr-spec A5 SIP URI of the UE as used in any previous request in the same dialog (In the earlier requests within the same dialog this URI appears in From header within requests sent by the UE and in To header within requests sent by the SS)

tag A5 tag value corresponding to the SIP URI of the UE in the same dialog. (In the earlier requests within the same dialog this tag appears in From header within requests sent by the UE and in To header within requests sent by the SS)

Call-ID

callid A4 a random text string generated by the SS

callid A5 value of Call-ID as in any previous request in the same dialog

CSeq

value A4 any value (e.g. 4711)

value A5 value of CSeq sent by the SS within its previous request in the same dialog but increased by one

method INVITE

Supported

option-tag 100rel

P-Called-Party-ID One of the UE’s registered, non-barred public ID

Contact

addr-spec A1 SIP URI with IP address or FQDN and protected server port of the calling UE, for example “sip:[email protected]:6543”

addr-spec A2 SIP URI with IP address or FQDN and unprotected server port of the calling UE

feature-param A3 +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"

Content-Type


Max-Forwards




Accept

media-range A4 application/sdp, application/3gpp-ims+xml

P-Asserted-Service

Service-ID A3 urn:urn-7:3gpp-service.ims.icsi.mmtel

Accept-Contact

ac-value A3 *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"

Content-Length




A2 GIBA (A.6a/1 3GPP TS 34.229-2 [5])

A3 UE supports MTSI (A.12/18 3GPP TS 34.229-2 [5])

A4 INVITE creating a dialog

A5 re-INVITE within a dialog


Table 14-18: MO REFER


Request-Line

Method REFER

Request-URI same URI value as the SS has earlier sent in its Contact header within the same dialog

SIP-Version SIP/2.0

Via




A2 IP address or FQDN and unprotected server port of the UE

via-branch







From

addr-spec local SIP URI of the UE which must be the same URI as used for the UE in the earlier requests within the dialog


To

addr-spec remote SIP URI of the SS which must be the same URI as used for SS in the earlier requests within the dialog.


Call-ID

callid same value as in the first INVITE during the call setup

CSeq

value value of CSeq sent by the UE within its previous request in the same dialog but increased by one

method REFER

Require (header optional in A2)


Proxy-Require (header optional in A2)


Security-Verify A1 (not present in A2)


Contact

addr-spec A1 SIP URI with IP address or FQDN and protected server port of UE or GRUU as returned by the SS in registration

A2 SIP URI with IP address or FQDN and unprotected server port of UE or GRUU as returned by the SS in registration

Refer-To

addr-spec SIP or Tel URI of the transfer target

Max-Forwards




Content-Length





A2 GIBA (A.6a/1 3GPP TS 34.229-2 [5])

Table 14-19: MT NOTIFY for Refer Package


Request-Line

Method NOTIFY

Request-URI same URI value which the UE sent in its Contact header within the REFER request

SIP-Version SIP/2.0


via-parm1:

Sent-protocol




via-branch


via-parm2: In addition to the via-parm entry for the SS, the following via-parm entries are included:


SIP/2.0/UDP uas.3gpp.org:6543;branch=z9hG4bk4567890123


From

addr-spec SIP URI of the SS which must be the same URI as used for the SS in the earlier requests within the dialog


To

addr-spec SIP URI of the UE which must be the same as used for the UE in the earlier requests within the dialog.


Call-ID

callid same value as in the INVITE (and REFER) message



CSeq A1,A2

value value of CSeq sent by the SS within its previous request in the same dialog but increased by one

method NOTIFY

Contact

addr-spec A1 SIP URI with IP address or FQDN and protected server port of the SS (transferee)

addr-spec A2 SIP URI with IP address or FQDN and unprotected server port of the SS (transferee)

Content-Type

media-type message/sipfrag

Event A1,A2

event-type refer

Max-Forwards

value 69

Subscription-State


expires 300

Content-Length




A2 GIBA (A.6a/1 3GPP TS 34.229-2 [5])

Table 14-20: MT REFER


Request-Line

Method REFER

Request-URI same URI value as that which the UE has earlier sent in its Contact header within the dialog created by the INVITE sent by the UE when initiating the call to be transferred

SIP-Version SIP/2.0


via-parm1:

Sent-protocol






via-branch


via-parm2: In addition to the via-parm entry for the SS, the following via-parm entries are included:


SIP/2.0/UDP uas.3gpp.org:6543;branch=z9hG4bk4567890123


From

addr-spec SIP URI of the SS which must be the same URI as used for the SS in the earlier requests within the dialog created by the INVITE sent by the UE when initiating the call to be transferred


To

addr-spec SIP URI of the UE which must be the same URI as used for UE in the earlier requests within the dialog created by the INVITE sent by the UE when initiating the call to be transferred


Call-ID

callid same value as in the first INVITE sent by the UE during setup of the call to be transferred

CSeq

value value of CSeq sent by the SS within its previous request in the dialog created by the INVITE sent by the UE when initiating the call to be transferred, but increased by one

method REFER

Contact

addr-spec A1 SIP URI with IP address or FQDN and protected server port of the SS (transferor)

A2 SIP URI with IP address or FQDN and unprotected server port of the SS (transferor)

Refer-To



addr-spec SIP or Tel URI of the transfer target

Max-Forwards




Content-Length



A1 IMS security (A.6a/2 TS 34.229-2 [5])

A2 GIBA (A.6a/1 TS 34.229-2 [5])

Table 14-21: MO NOTIFY for Refer Package


Request-Line

Method NOTIFY

Request-URI same URI value which the SS sent in its Contact header within the REFER request

SIP-Version SIP/2.0

Via

sent-protocol

SIP/2.0/UDP when using UDP or

SIP/2.0/TCP when using TCP


A2 IP address or FQDN and unprotected server port of UE

via-branch





From

addr-spec Local SIP URI of the UE which must be the same URI as used for the UE in the earlier requests within the dialog created by the INVITE sent by the UE when initiating the call to be transferred


To

addr-spec Remote SIP URI of the SS which must be the same as used for the SS



in the earlier requests within the dialog created by the INVITE sent by the UE when initiating the call to be transferred.


Call-ID

callid same value as in the INVITE (and REFER) message

CSeq A1,A2

value value of CSeq sent by the SS within its previous request in the dialog created by the INVITE sent by the UE when initiating the call to be transferred, but increased by one

method NOTIFY

Contact

addr-spec A1 SIP URI with IP address or FQDN and protected server port of the UE or GRUU as returned by the SS in registration

addr-spec A2 SIP URI with IP address or FQDN and unprotected server port of UE or GRUU as returned by the SS in registration

Content-Type

media-type message/sipfrag

Event A1,A2

event-type refer

Max-Forwards


Subscription-State


expires non-zero value

Content-Length



A1 IMS security (A.6a/2 TS 34.229-2 [5])

A2 GIBA (A.6a/1 TS 34.229-2 [5])

Table 14-22: 181 Call is Being Forwarded


Status-Line

SIP-Version SIP/2.0

Status-Code 181

Reason-Phrase Call is being forwarded



Via


From



To


tag px_InviteToTag

History-Info

hi-targeted-to-uri <sip:[email protected]>

hi-index 1

Call-ID


CSeq


Content-Length

value 0

Table 14-23: CANCEL


Request-Line

Method CANCEL

Request-URI same value as in the INVITE being cancelled

SIP-Version SIP/2.0

Via

via-parm same value as in the INVITE being cancelled

From

addr-spec same value as in the INVITE being cancelled

Tag same value as in the INVITE being cancelled

To

addr-spec same value as in the INVITE being cancelled

tag same value as in the INVITE being cancelled

Call-ID

Callid same value as in the INVITE being cancelled

CSeq



Numeric value same value as received in INVITE message

Method CANCEL

Content-Length

Value 0

Table 14-24: 487 Request Terminated


Status-Line

SIP-Version SIP/2.0

Status-Code 487

Reason-Phrase Request Terminated

Via


From



To


tag px_InviteToTag

Call-ID


CSeq


Content-Length

value 0

14.2.1.1 G.3 Generic Common Messages

Table 14-25: 200 OK for Requests other than REGISTER or SUBSCRIBE


Status-Line

SIP-Version SIP/2.0

Status-Code 200

Reason-Phrase OK

Via

via-parm same value as received in request



Record-Route order of the parameters in this header must be like in this table

rec-route A1,A2 <sip:pcscf.other.com;lr>, <sip:scscf.other.com;lr>,<sip:orig@px_scscf;lr>, <sip:px_pcscf:px_SSProtectedServerPort;lr>

rec-route A3,A4 <sip:pcscf.other.com;lr>, <sip:scscf.other.com;lr>,<sip:orig@px_scscf;lr>, <sip:px_pcscf:px_SSUnprotectedServerPort (optional);lr>

From

addr-spec same value as received in request

tag same value as received in request

To


tag same value as received in request or

px_InviteToTag added if missing from request



uri-parameter lr

Contact

addr-spec A1, A3 px_CalleeContactUri



Call-ID

callid same value as received in request

CSeq

value same value as received in request

P-Access-Network-Info

access-net-spec A5 access network technology and, if applicable, the cell ID

Content-Length

value 0


A1 Response sent by SS for INVITE (IMS security ,A.6a/2 TS 34.229-2 [5]))



A2 Response sent by UE for INVITE (IMS security ,A.6a/2 TS 34.229-2 [5]))

A3 Response sent by SS for INVITE (GIBA, A.6a/1 TS 34.229-2 [5]))

A4 Response sent by UE for INVITE (GIBA, A.6a/1 TS 34.229-2 [5]))

A5 Any response sent by the UE within a dialog

A6 Response sent by SS for INVITE for emergency call

Table 14-26: 403 FORBIDDEN


Status-Line

SIP-Version SIP/2.0

Status-Code 403

Reason-Phrase Forbidden

Via

via-parm same value as received in the previous REGISTER message

To

addr-spec same value as received in the previous REGISTER message


From

addr-spec same value as received in the previous REGISTER message

Call-ID

value same value as received in the previous REGISTER message

CSeq

value same value as received in the previous REGISTER message

Content-length

value 0

Table 14-27: 202 Accepted


Status-Line

SIP-Version SIP/2.0

Status-Code 202

Reason-Phrase Accepted

Via


From





To



Call-ID


CSeq


Content-Length

value 0

14.2.1.2 G.4 Other Default Messages

Table 14-28: 380 Alternative Service


Status-Line

SIP-Version SIP/2.0

Status-Code 380

Reason-Phrase Alternative Service

Via


From



To


tag same value as received in request or

px_InviteToTag added

P-Asserted-Identity

addr-spec px_pcscf

uri-parameter lr

Call-ID


CSeq




Content-Length

value Length of message-body

Content-Type

media-type application/3gpp-ims+xml

Message-body <?xml version="1.0"?>

<ims-3gpp version="1">

<alternative-service>

<type>emergency</type>

<reason/>

</alternative-service>

</ims-3gpp>

Table 14-29: 503 Service Unavailable


Status-Line

SIP-Version SIP/2.0

Status-Code 503

Reason-Phrase Service Unavailable

Via


From



To


tag any arbitrary tag value added

Call-ID


CSeq


Content-Length

value 0

Retry-after

period 60 (referred to as T in the test procedure and test requirement)

duration Not present

comment Not present


Table 14-30: PUBLISH


Request-Line

Method PUBLISH

Request-URI any IMPU within the set of IMPUs on ISIM

SIP-Version SIP/2.0




Via



sent-by A2 IP address or FQDN, port (optional) and not checked


From



To



Expires Optional

delta-seconds same as registration timer

Security-Verify A1


Require A1 Optional

option-tag Not checked

Proxy-Require A1 Optional

option-tag Not checked

CSeq


method PUBLISH

Call-ID


Max-Forwards






Event

event-type value not checked

SIP-If-Match optional

entry-tag

Content-Length


Message-body optional


A1 IMS security (A.6a/2 TS 34.229-2 [5]))

A2 GIBA (A.6a/1 TS 34.229-2 [5]))


Table 14-31: 200 OK for PUBLISH


Status-Line

SIP-Version SIP/2.0

Status-Code 200

Reason-Phrase OK

Via

via-parm same value as received in PUBLISH message

To



From

addr-spec same value as received in PUBLISH message

tag same value as received in PUBLISH message

Call-ID

callid same value as received in PUBLISH message

CSeq

value same value as received in PUBLISH message

Contact




Expires


SIP-ETag

entry-tag unique generated tag for every request

Content-Length

value 0

Table 14-32: 302 Moved Temporarily


Status-Line

SIP-Version SIP/2.0

Status-Code 302

Reason-Phrase Moved Temporarily

Via


From



To



Call-ID


CSeq


Content-Length

value 0

Contact

addr-spec sip:[email protected]

Table 14-33: 504 Server Time-out


Status-Line

SIP-Version SIP/2.0

Status-Code 504

Reason-Phrase Server Time-out



Via


From



To



P-Asserted-Identity

addr-spec px_scscf

uri-parameter lr

Call-ID


CSeq


Content-Length

value Length of message-body

Content-Type

media-type application/3gpp-ims+xml

Message-body <?xml version="1.0"?>

<ims-3gpp version="1">

<alternative-service>

<type>restoration</type>

<reason/>

<action>initial-registration</action>

</alternative-service>

</ims-3gpp>

14.2.1.3 Default Messages for Conferencing

Table 14-34: SUBSCRIBE for Conference Event Package


Request-Line

Method SUBSCRIBE

Request-URI px_FinalConferenceUri

SIP-Version SIP/2.0






Via



sent-by A2 IP address or FQDN and unprotected server port of the UE


From



To

addr-spec px_FinalConferenceUri

tag not present

Contact



Expires

delta-seconds must be present but value not checked

Security-Verify A1


Require A1


Proxy-Require A1


CSeq


method SUBSCRIBE

Call-ID


Max-Forwards






Accept

media-range application/conference-info+xml

Event

event-type conference

Content-Length




A2 GIBA (A.6a/1 TS 34.229-2 [5]))


Table 14-35: 200 OK for SUBSCRIBE


Status-Line

SIP-Version SIP/2.0

Status-Code 200

Reason-Phrase OK

Via

via-parm same value as received in SUBSCRIBE message

To


tag px_ToTagSubscribeConferenceDialog

From

addr-spec same value as received in SUBSCRIBE message

tag same value as received in SUBSCRIBE message

Call-ID

callid same value as received in SUBSCRIBE message

CSeq

value same value as received in SUBSCRIBE message

Contact


Expires

delta-seconds 7200



Record-Route

addr-spec A1 px_pcscf: protected server port of SS

addr-spec A2 px_pcscf: unprotected server port of SS (optional)

uri-parameter Lr

Content-Length

value 0



A2 GIBA (A.6a/1 TS 34.229-2 [5]))


Table 14-36: NOTIFY for Conference Event Package


Request-Line

Method NOTIFY

Request-URI UE’s contact address in SIP URI form, as provided in the Contact header within the SUBSCRIBE creating the dialog

SIP-Version SIP/2.0


via-parm1:

Sent-protocol




via-branch


via-parm2:

sent-protocol


sent-by px_scscf

via-branch


From





To



Call-ID


CSeq A1,A2


method NOTIFY

Contact


Content-Type

media-type application/conference-info+xml

Event A1,A2

event-type conference

Max-Forwards

value 69

Subscription-State


expires 7200

Content-Length


Message-body <?xml version="1.0" encoding="UTF-8"?>

<conference-info xmlns="urn:ietf:params:xml:ns:conference-info">

entity="px_FinalConferenceUri"

state="full"

version="0"

<users>

<user entity="any IMPU within the set of IMPUs on ISIM">

<endpoint entity=" Contact URI of the UE">

<status>connected</status>

<joining-method>dialed-in</joining-method>

<media id="1">

<type>audio</type>

<label>34567</label>

<src-id>SSRC of UE's RTP packets</src-id>



<status>sendrecv</status>

</media>

</endpoint>

</users>

</conference-info>



A2 GIBA (A.6a/1 TS 34.229-2 [5]))


14.2.1.4 Default Messages for Message Waiting Indication

Table 14-37: SUBSCRIBE for Message-Summary Event Package


Request-Line

Method SUBSCRIBE

Request-URI any IMPU within the set of IMPUs on ISIM or px_MessageAccountIdentity.

UE shall use px_MessageAccountIdentity when that is configured to the phone as Public service identity of the message account.

SIP-Version SIP/2.0




Via



sent-by A2 IP address or FQDN and unprotected server port of the UE


From



To



addr-spec any IMPU within the set of IMPUs on ISIM or px_MessageAccountIdentity.

UE shall use px_MessageAccountIdentity when that is configured to the phone as Public service identity of the message account.

tag not present

Contact



Expires

delta-seconds must be present but value not checked

Security-Verify A1


Require A1


Proxy-Require A1


CSeq


method SUBSCRIBE

Call-ID


Max-Forwards




Accept

media-range application/simple-message-summary

Event

event-type message-summary

Content-Length



A1 IMS security (A.6a/2)



A2 GIBA (A.6a/1)


Table 14-38: NOTIFY for Message-Summary Event Package


Request-Line

Method NOTIFY

Request-URI UE’s contact address in SIP URI form, as provided in the Contact header within the SUBSCRIBE creating the dialog

SIP-Version SIP/2.0


via-parm1:

Sent-protocol




via-branch


via-parm2:

sent-protocol


sent-by px_scscf

via-branch


via-parm3:

sent-protocol


sent-by px_MessageServerDomainName

via-branch


From

addr-spec any IMPU within the set of IMPUs on ISIM or px_MessageAccountIdentity.

SS shall use px_MessageAccountIdentity when that is configured to the phone as Public service identity of the message account.


To





Call-ID


CSeq A1,A2


method NOTIFY

Contact

addr-spec px_MessageServerContactUri

Content-Type

media-type application/simple-message-summary

Event A1,A2

event-type message-summary

Max-Forwards

value 69

Subscription-State


expires 7200

Content-Length


Message-body Messages-Waiting: no

Message-Account: any IMPU within the set of IMPUs on ISIM or px_MessageAccountIdentity as in From header


A1 IMS security (A.6a/2)

A2 GIBA (A.6a/1)


14.2.1.5 Default Messages for SMS

Table 14-39: MESSAGE for MT SMS


Request-Line



Method MESSAGE

Request-URI UE’s registered contact address in SIP URI form, as provided in the Contact header of the REGISTER message

SIP-Version SIP/2.0

Via

sent-protocol SIP/2.0/UDP

sent-by px_pcscf:px_SSProtectedServerPort

via-branch


From

addr-spec a SIP URI of the SS

tag any value

To

addr-spec SIP URI of the UE

tag not present

Call-ID

callid a random text string generated by the SS

CSeq

value any value

method MESSAGE

Max-Forwards


Accept-Contact

ac-value +g.3gpp.smsip;require;explicit

Request-Disposition

fork-directive no-fork

P-Asserted-Identity

addr-spec a SIP URI of the SS representing IP-SM-GW

P-Called-Party-ID

called-pty-id-spec UE’s registered contact address in SIP URI form, as provided in the Contact header of the REGISTER message

Content-Type

media-type application/vnd.3gpp.sms

Content-Length




Message-body RP-DATA message including a SMS-DELIVER TPDU equal to px_MT_SMS if px_MT_SMS_defined is set to ‘TRUE’

otherwise

- TP-MTI=’00’B

- TP-MMS=’1’B (No more messages are waiting for the MS in this SC)

- TP-RP=any allowed value

- TP-OA=any allowed value

- TP-PID=any allowed value

- TP-DCS=any allowed value

- TP-SCTS=any allowed value

- TP-UDL=set according to length of TP-UD field

- TP-UD=a valid SMS generated by SS

Table 14-40: MESSAGE for Delivery Report


Request-Line

Method MESSAGE

Request-URI same URI as received in G.7.1

SIP-Version SIP/2.0

Via


sent-by not checked

via-branch


From

addr-spec a SIP URI of the SS representing the calling UE

tag any value

To

addr-spec SIP URI of the SS

tag not present

Call-ID

callid not checked

CSeq

value any value

method MESSAGE

Max-Forwards




Content-Type


Content-Length


Message-body RP-ACK message with RP-User Data including a SMS-DELIVER-REPORT TPDU

- TP-MTI=’00’B

- TP-PI=any allowed value

Table 14-41: MESSAGE for MO SMS


Request-Line

Method MESSAGE

Request-URI px_psi_SMSC

SIP-Version SIP/2.0

Via


sent-by IP address or FQDN and protected server port of the UE

via-branch


From

addr-spec any SIP URI

tag any value

To

addr-spec px_CalleeUri

tag not present

Call-ID

callid must be present, value not checked

CSeq

value any value

method MESSAGE

Max-Forwards


P-Access-Network-Info



access-net-spec


Route

route-param <sip:px_pcscf:px_SSProtectedServerPort;lr>, <sip:px_scscf;lr>

Content-Type


Content-Length


Message-body

RP-DATA message with RP-User Data set to SMS-SUBMIT type equal to px_MO_SMS if px_MO_SMS_defined is set to ‘TRUE’

otherwise:

- TP-MTI=’ 01’B (SMS-SUBMIT)

- TP-RD=any allowed value

- TP-VPF=any allowed value

- TP-RP=any allowed value

- TP-MR=any allowed value

- TP-DA=any allowed value

- TP-PID=any allowed value

- TP-DCS=any allowed value

- TP-UDL=set according to length of TP-UD field

- TP-UD=must be present and non-empty

Table 14-42: Submission Report for MO SMS


Request-Line

Method MESSAGE

Request-URI UE's registered contact address in SIP URI form, as provided in the Contact header of the REGISTER messageSIP/2.0

SIP-Version MESSAGE

Via


sent-by not checked

via-branch


From


Tag any value



To



Call-ID

Callid any value

In-Reply-to

callid any value

Cseq

value any value

method MESSAGE

Max-Forwards


Request-Disposition

fork-directive Fork

P-Called-Party-ID

value any value

P-Asserted-Identity

value px_psi_SMSC

Content-Type


Content-Length


Message-body RP-ACK message with RP-User Data including SMS-SUBMIT-REPORT:

- TP-MTI=‘01’B (SMS-SUBMIT-REPORT)

- TP-PI=‘00000000’B

- TP-SCTS=set by the SS (encoded as specified in TS 23.040 clause 9.2.3.11)

Table 14-43: Status Report for MO SMS


Request-Line

Method MESSAGE

Request-URI UE's registered contact address in SIP URI form, as provided in the Contact header of the REGISTER message

SIP-Version SIP/2.0

Via




sent-by not checked

via-branch


From


Tag any value

To



Call-ID

Callid any value

P-Asserted-Identity

addr-spec px_psi_SMSC

Cseq

Value any value

method MESSAGE

Max-Forwards


Request-Disposition

fork-directive no-fork

Accept-Contact

ac-value +g.3gpp.smsip;require;explicit

Content-Type


Content-Length


Message-body RP-DATA message with RP-User Data including SMS-STATUS-REPORT:

- TP-MTI=’10’B (SMS-STATUS-REPORT)

- TP-MMS=’0’B

- TP-SRQ=’0’B

- TP-MR=same value as that set by the UE in the RP-DATA of the MO SMS

- TP-RA=same value as the TP-DA set by the UE in the RP-DATA of



the MO SMS

- TP-SCTS=same value as that set by the SS in the RP-ACK acknowledging the MO SMS

- TP-DT=set by the SS (encoded as specified in TS 23.040 clause 9.2.3.11)

- TP-ST=’0000000’B (Short message received by the SME)

Table 14-44: Delivery Report for MO SMS


Request-Line

Method MESSAGE

Request-URI same URI as received in G.7.5

SIP-Version SIP/2.0

Via


sent-by not checked

via-branch


From

addr-spec a SIP URI of the SS representing the calling UE

tag any value

To

addr-spec SIP URI of SS

tag not present

Call-ID

callid not checked

CSeq

value any value

method MESSAGE

Max-Forwards


Content-Type


Content-Length


Message-body RP-ACK message with RP-User Data including a SMS-DELIVER-REPORT TPDU:



- TP-MTI=’00’B (SMS-DELIVER-REPORT)

- TP-PI=any allowed value

Table 14-45: RP-DATA Message (UE to Network)

Information Element Value/Remark

RP-Message Type ‘000’B

RP-Message Reference Any valid value

RP-Originator Address 0 length address

RP-Destination Address px_SMSC_addr

RP-User Data Any valid value

cs8 test sets - spirent...the information contained in this document is subject to change without...

Documents