FTS - 81436 - Mobility Between UMTS and LTE - Reselection - v01.06

1
3 FTS 81436 - Mobility between UMTS and LTE - Cell

4 reselection
5
6 Document Number: UMT/SYS/APR/028777
7 Document Issue: 01.06 / EN
8 Document Status: Approved_Standard
9 Date: 27/May/2010
10
11
12 Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction
13 Copyright 2007-2009 Alcatel-Lucent, All Rights Reserved

14
15 UNCONTROLLED COPY:
16 The master of this document is stored on an electronic database and is “write protected”; it may be altered only by
17 authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access
18 to the current issue. Any hardcopies taken must be regarded as uncontrolled copies.
19
20 ALCATEL-LUCENT CONFIDENTIAL:
21 The information contained in this document is the property of Alcatel-Lucent. Except as expressly authorized in writing by
22 Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose the information only to its
23 employees with a need to know, and shall protect the information from disclosure and dissemination to third parties. Except
24 as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein.
25 If you have received this document in error, please notify the sender and destroy it immediately.
FTS 81436 - Mobility between UMTS and LTE - Cell reselection
26
27 1 INTRODUCTION.................................................................................................. 9
28 1.1 OBJECT ........................................................................................................ 9
29 1.2 SCOPE OF THIS DOCUMENT ................................................................................. 9
30 1.3 AUDIENCE FOR THIS DOCUMENT ........................................................................... 9
31 1.4 STATUS......................................................................................................... 9
32 1.5 WAIVERS AND EXCEPTIONS.................................................................................. 9
33 2 RELATED DOCUMENTATION..................................................................................11
34 2.1 APPLICABLE DOCUMENTS................................................................................... 11
35 2.1.1 Requirements Documents ........................................................................... 11
36 2.1.1.1 FRS(s)..............................................................................................11
37 2.1.2 Other Applicable Documents........................................................................ 11
38 2.2 REFERENCE DOCUMENTS ................................................................................... 11
39 3 FEATURE OVERVIEW ..........................................................................................12

40 3.1 OVERVIEW .................................................................................................... 12
41 3.2 FRS ANALYSIS ................................................................................................ 14
42 3.2.1 FRS Requirements List ............................................................................... 14
43 3.2.1.1 FRS 81436: Mobility between UMTS and LTE: cell reselection........................14
44 3.2.2 Customer Specific Requirements ................................................................... 15
45 3.2.3 FRS Compliancy Matrix............................................................................... 15
46 3.2.3.1 FRS Compliance Notes .........................................................................15
47 3.2.3.2 Restrictions ......................................................................................16
48 3.2.4 Compliancy Matrix Updates ......................................................................... 17
49 3.3 OPEN ISSUES ................................................................................................. 18
50 4 FEATURE BENEFITS............................................................................................19
51 4.1 CUSTOMER/SERVICE PROVIDER BENEFITS ............................................................... 19
52 4.2 END-USER / SUBSCRIBER BENEFITS ....................................................................... 19
53 5 FEATURE DEFINITION .........................................................................................20

54 5.1 ASSUMPTIONS ................................................................................................ 20
55 5.2 PRINCIPLES ................................................................................................... 20
56 5.2.1 UE capability and mobility towards LTE .......................................................... 20
57 5.2.2 PLMN and RAT selection ............................................................................. 21
Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction
UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 2 of 84

58 5.2.3 Mobility in reselection mode........................................................................ 21
59 5.2.3.1 UE state eligible to reselection towards E-UTRA .........................................21
60 5.2.3.2 SIB impacted .....................................................................................21
61 5.2.3.3 SIB19 content....................................................................................22
62 5.2.3.4 SIB19 reading by UE ............................................................................22
63 5.2.3.5 SIB scheduling ...................................................................................23
64 5.2.3.5.1 MIB/SB1 structure.............................................................................. 23
65 5.2.3.5.2 Number of segments........................................................................... 25
66 5.2.3.5.3 SIB position and repetition period setting by the RNC ................................... 26
67 5.2.3.5.4 SIB scheduling use case ....................................................................... 27
68 5.2.3.6 UE cell Reselection : which process ........................................................28
69 5.2.3.7 UE cell Reselection : criteria when absolute priority and HCS are not used .......29
70 5.2.3.8 UE cell Reselection : criteria when absolute priority is not used and HCS is used29
71 5.2.3.9 UE cell Reselection : criteria when absolute priority is used .........................29
72 5.2.3.9.1 Measurement triggering criteria............................................................. 30
73 5.2.3.9.1.1 Inter frequency measurements criteria .................................................. 30
74 5.2.3.9.2 Cell reselection triggering criteria .......................................................... 31
75 5.2.3.10 UE cell Reselection process using absolute priority ...................................32
76 5.2.3.11 How favoring a reselection towards E-UTRA ............................................33
77 5.2.3.12 Cell re-selection process: number of frequencies and cells .........................34
78 5.2.4 System information update procedure ............................................................ 35
79 5.3 SOLUTION OPTIONS ......................................................................................... 36
80 5.3.1 Absolute priority use for FDD frequencies and GSM Frequencies. ............................ 36
81 5.3.2 Frequency Dedicated priority management ...................................................... 36
82 5.3.3 Others .................................................................................................. 36
83 5.4 FEATURE DEPENDENCIES ................................................................................... 36
84 5.5 INTER SUB-SYSTEM FUNCTIONAL DISTRIBUTION ........................................................ 37
85 5.5.1 Sub System Impacts .................................................................................. 37
86 5.5.1.1 BTS Impacts ......................................................................................37
87 5.5.1.2 RNC Impacts......................................................................................37
88 5.6 REQUIREMENTS .............................................................................................. 37
89 5.7 USE CASES .................................................................................................... 39
90 5.7.1 Initial Cell setup ...................................................................................... 39
91 5.7.2 SIB update error at initial cell setup .............................................................. 40

92 5.7.3 SIB update dynamically initiated by the RNC .................................................... 42
93 5.8 FEATURE INTERWORKING .................................................................................. 43
94 5.9 PERFORMANCE IMPACTS.................................................................................... 43
95 5.9.1 System Performance ................................................................................. 43
96 5.9.2 Dimensioning .......................................................................................... 43
97 5.9.3 Capacity ................................................................................................ 43
98 5.9.4 Dependability, Availability and Reliability........................................................ 43
99 5.9.5 End User Performance ............................................................................... 43
100 5.10 SECURITY.................................................................................................... 43
101 5.11 ENVIRONMENTAL IMPACTS................................................................................ 43
102 5.12 STANDARDS (COMPLIANCY AND SUPPORT) ............................................................. 44
103 5.13 BILLING SYSTEM IMPACT .................................................................................. 44
104 5.14 UPGRADE REQUIREMENTS................................................................................. 44
105 5.14.1 Pre-Checks............................................................................................ 44
106 5.14.2 Functionality Change due to Upgrade............................................................ 44
107 6 INTERFACE REQUIREMENTS..................................................................................45

108 6.1 UMTS INTERFACES........................................................................................... 45
109 6.1.1 Uu Interface ........................................................................................... 46
110 6.1.1.1 SIB19 ..............................................................................................46
111 6.1.1.1.1 System Information Block type 19........................................................... 46
112 6.1.1.1.2 Utra priority info list IE ....................................................................... 46
113 6.1.1.1.3 Gsm priority info list IE ....................................................................... 48
114 6.1.1.1.4 Gsm cell group IE .............................................................................. 48
115 6.1.1.1.5 E-UTRA Frequency and priority info list IE................................................. 50
116 6.1.1.2 SIB scheduling ...................................................................................53
117 6.1.1.2.1 Master information block IE .................................................................. 53
118 6.1.1.2.2 References to other system information blocks and scheduling blocks IE ............ 53
119 6.1.1.2.3 Scheduling block 1 ............................................................................. 55
120 6.1.1.2.4 References to other system information blocks IE ....................................... 55
121 6.1.1.2.5 SIB type extension2 IE......................................................................... 57
122 6.1.2 Iu Interface ............................................................................................ 58
123 6.1.3 Iur Interface ........................................................................................... 59
124 6.1.4 Iub Interface........................................................................................... 60
125 6.1.4.1 System information update request message .............................................60

126 6.1.4.2 System information update response message ...........................................61
127 6.1.4.3 System information update failure message ..............................................61
128 6.1.4.4 IB type IE .........................................................................................61
129 6.2 OAM INTERFACES ............................................................................................ 63
130 6.2.1 3GPP OAM INTERFACES............................................................................... 63
131 6.2.2 External ALU OAM Interfaces ....................................................................... 63
132 6.3 TRANSMISSION NETWORK INTERFACES ................................................................... 63
133 6.3.1 Physical Layer ......................................................................................... 63
134 6.3.2 No impact.Ethernet .................................................................................. 63
135 6.3.3 ATM ..................................................................................................... 63
136 6.3.4 IP ........................................................................................................ 63
137 7 OAM MODEL DESCRIPTION ...................................................................................64

138 7.1 CONFIGURATION MANAGEMENT ........................................................................... 64
139 7.1.1 CM Parameters ........................................................................................ 64
140 7.1.1.1 Spare parameters available in UA07.1.2...................................................64
141 7.1.1.2 CM in UA07.1.2..................................................................................64
142 7.1.1.2.1 Others............................................................................................ 72
143 7.1.1.3 CM in UA08 .......................................................................................72
144 7.1.2 Control Rules .......................................................................................... 72
145 7.1.2.1 UA07.1.2 .........................................................................................72
146 7.1.2.2 UA08...............................................................................................72
147 7.2 FAULT MANAGEMENT ....................................................................................... 73
148 7.2.1 Alarms .................................................................................................. 73
149 7.2.2 Diagnostics ............................................................................................. 73
150 7.2.3 Trouble Shooting ...................................................................................... 73
151 7.2.4 Failure Recovery ...................................................................................... 73
152 7.3 PERFORMANCE MANAGEMENT ............................................................................. 74
153 7.3.1 Counters................................................................................................ 74
154 7.3.2 Metrics.................................................................................................. 74
155 7.3.3 Traces .................................................................................................. 74
156 8 OAM PROCEDURES .............................................................................................75

157 8.1 UPGRADES .................................................................................................... 75
158 8.1.1 OAM Platform Upgrade............................................................................... 75

159 8.1.2 RNC & BTS Upgrade................................................................................... 75
160 8.2 INSTALLATION AND COMMISSIONING PROCEDURES..................................................... 75
161 8.3 MAINTENANCE................................................................................................ 75
162 8.4 FEATURE ACTIVATION ...................................................................................... 75
163 9 FIELD INTRODUCTION .........................................................................................75

164 9.1 HARDWARE CONSTRAINTS.................................................................................. 76
165 9.2 SPARE PARTS CONSTRAINTS ............................................................................... 76
166 9.3 INTER RNS VERSION INTERWORKING ..................................................................... 76
167 9.4 CORE NETWORK INTERWORKING.......................................................................... 76
168 9.5 BACKWARDS COMPATIBILITIES............................................................................. 76
169 10 FUTURE EVOLUTION ..........................................................................................76
170 11 TOOLS IMPACTS ................................................................................................76
171 12 FTS REQUIREMENTS COMPLIANCE AND RESTRICTION TABLE..........................................78

172 12.1 FTS COMPLIANCE NOTES .................................................................................. 78
173 12.2 RESTRICTIONS .............................................................................................. 78
174 12.3 COMPLIANCY MATRIX UPDATES .......................................................................... 78
175 13 ABBREVIATIONS AND DEFINITIONS .........................................................................79
176 14 ANNEX............................................................................................................80
177 14.1 ANNEX A: FEATURE GROUP INDICATORS ............................................................... 80
178 Annex E (Normative): EUTRA Feature group indicators ............................................................. 80
179 14.2 ANNEX B: UE VARIABLES .................................................................................. 81
180 PRIORITY_INFO_LIST ........................................................................................... 81

181
182 Publication History

183 <Guide>Author should complete Publication History, Introduction, and Related Documents as
184 required by the WCDMA Document Control Procedure (SQ/GEN/APP/000011). This template
185 has been developed with UMTS items, for other technologies the UMTS references to
186 equivalents for that technology.
187
188 The following sections: - Publication History, Introduction, Related Documents, Function
189 Overview, Benefits and Definition, Requirements Compliance and Abbreviations should always
190 be utilised. If appropriate the author may decide not to complete other sections, or to add
191 sections if needed.
192
193 All Guidelines as denoted by italic text and the guide / start end markers should be deleted
194 from the document when completed
195
196 Issue Numbers start at 01.01 and the table should be filled in reverse chronological
197 order</Guide>
Date Modifications Issue CR Author
Number
21/09/2009 This first draft edition is build from the first draft of 01.01/EN Creation P.Moquet
the FTS initially created in UA08 to cover cell
reselection, RRC redirection and PS HHO UMTS<->LTE.
The HHO and the redirection parts are removed and
only the reselection part is kept. The feature 81436
was also moved from UA08.0 to UA07.1.2.
20/10/2009 Updated with: 01.02/EN Update P.Moquet

• LTE team feedback:
o RRC redirection towards LTE is not
requested in UA07.1.2;
o The support “blacklisted cell list” IE is not
requested in UA07.1.2;
o The number of LTE frequencies may be
reduced to 2 in UA07.1.2;
• RNC comments:
o SIB11 or SI11bis use: it is a wrong
assumption in the FRS.
o UE capability checking by the RNC is not in
the scope of this feature;

o 3GPP makes a difference between serving
frequency and inter frequencies: this
information is added for a better
understanding;
o Iur is not impacted by this feature
o UTRA cells parameters are in FDD cell
MO and not in RNC MO
• others information:
o No need to support absolute priority for
GSM frequencies and FDD inter
frequencies in UA07.1.2;
o SIB scheduling algorithm reminded and
updated;
o NBAP system information update
procedure detailed with uses cases
o Number of frequencies and cells added:
3GPP requirements
o OAM parameters definition modified;
o Improvements candidate to UA08.
04/11/09 Update with mails comments 01.03/EN Update P.Moquet
24/12/09 Update spares and CM parameters mapping, update 01.04/EN Update R.Baron
paragraph 5.2.3.5.2 (replace segment by transport
block)
25/02/10 Set Status to Approved_Standard 01/05/EN Update R.Baron

27/05/10 Describe how to know the instance describing the E- 01/06/EN Update R.Baron
UTRAN frequency are significant in the spare
parameters

198
199 1 INTRODUCTION
200 <Guide> In the objects below add the lead author's name followed by each of the authors in
201 the author team. </Guide>
202 Prepared by: P.Moquet
203 Author's Name: P.Moquet
204 Co-author's Name: P.Moquet / R.Baron
205 (Repeat for each co-author)
206
207
208 1.1 OBJECT

209 The primary objective of the FTS is to provide a technical response to the FRS, with sufficient
210 feature definition detail to technically describe how Alcatel-Lucent solutions will satisfy the
211 customer needs, and to facilitate R&D commitment to deliver the feature. The FTS provides
212 new product requirements derived from the feature requirements, which form the basis for
213 subsequent lower-detailed definition.
214
215 1.2 SCOPE OF THIS DOCUMENT

216 This document covers the following FRS:
217 • FRS 81436: Mobility between UMTS and LTE – Cell reselection
218
219
220 1.3 AUDIENCE FOR THIS DOCUMENT

221 PLM, System Design, Integration and Validation Teams.....
222 1.4 STATUS

Ongoing Completed Comment Next Step
Level 1: Yes Yes
Request Understood
Level 2: Yes Yes
Solution Identified
Level 3: Yes Yes FTS review
Solution Defined
223 1.5 WAIVERS AND EXCEPTIONS

224 Empty.

225 2 RELATED DOCUMENTATION

226 2.1 APPLICABLE DOCUMENTS
227 2.1.1 Requirements Documents
228 2.1.1.1 FRS(s)
229 <Guide>Reference FRS</Guide>
230 FRS 81436 Mobility between UMTS and LTE – Cell reselection
231 FRS 104489 LTE to UMTS HO
232 FRS 36246 3GPP Baseline + additional CRs for UA07
233
234
235 2.1.2 Other Applicable Documents
236 [A1] UMT/SYS/DD/0054 UMTS Radio Mobility
237 [A2] UMT/SYS/ APR/028776 LTE to UMTS HO
238 [A3] FDD-7434 LTE/W-CDMA End-to-End Interworking
239 [A4] UMT/SYS/DD/023089 UTRAN Network scenarios
240 [A5] UMT/SYS/APR/028971 FTS 81213 - Load balancing between HSPA carriers
241
242
243 Open item: LTE system documents to be added? Yes closed
244
245
246 2.2 REFERENCE DOCUMENTS

247 [R1] TS 25.331 v8.7.0 Uu interface RRC signalling
248 [R2] TS 25.304 v8.6.0 User Equipment (UE) procedures in idle mode and
249 procedures for cell reselection in connected mode
250 [R3] TS 25.433 v8.5.0 NBAP protocol
251 [R4] TS 25.413 v7.9.0 RANAP protocol
252 [R5] TS 36.300 v8.9.0 Evolved Universal Terrestrial Radio Access (E-UTRA) and
253 Evolved Universal Terrestrial Radio Access Network (E-UTRAN);Overall
254 description Stage 2
255 [R6] TS 33.401 v8.4.0 3GPP System Architecture Evolution: Security Architecture
256 [R7] TS 23.401 v8.6.0 GPRS enhancements for Evolved Universal terrestrial radio
257 Access Network (E-UTRAN) access

258 [R8] TS 25.133 v8.7.0 Requirements for support of radio resource management
259 (FDD)
260
261 3 FEATURE OVERVIEW

262 <Guide>This is an introduction to the global behaviour of the function across the system /
263 subsystems from a high level point of view.
264
265 It shows the external elements (other subsystems, mobile,…) being in interaction with the
266 subsystem.
267
268
269 3.1 OVERVIEW

270 This features deals with cell reselection mobility from UMTS towards LTE.
271 For information the following picture shows the scenarios of LTE deployment (extract of PLM
272 package):
273
LTE deployment
Main scenarios
LTE and GSM/WCDM A will interwork to form a seamless network
HSPA will be likely activated in the whole 3G networks prior to LTE deployment
D ense
Urban Urban Suburban Rural LTE metropolitan deployment
LTE in dense area, then progressive extension
Initially spotty LTE coverage, or
LTE GSM/ HS PA Get quickly a continuous LTE national macro
coverage using free spectrum (e.g. re-using the
digital dividend band)
Dense
Urban Urban Suburban Rural
HSPA leapfrog
LTE in dense area in parallel with deployment in
GSM sub-urban and rural areas instead of HSPA
LT E HSPA extension is frozen or limited
Re-using digital dividend band or GSM spectrum re-
HS PA
LTE farming (longer term)
Dense
Urban Urban Suburban Rural LTE new entrant
LTE in metropolitan area (without roaming to
2G/3G operators)
M VNO MVNO relationship with 2G/3G operators for
LTE
GSM/ HS PA nation-wide coverage
Alcatel-Lucent Technologies – Proprietar y

7 | 2G /3G/LTE Mobi li ty Management | J une 2009 V0.3 All Rig hts Reserv ed © Alcatel-L ucent 2006, 2008
© 2006 Alcatel-Lucent 2007, 2008 Use pursuant to company instruction 7
274
275
276 Figure 1: LTE deployment scenarios
277

278 In order to cover the different scenarios the UTRAN has to be able:
279 • To accept an incoming HHO from LTE network when a UE leaves the LTE coverage or
280 when a CS call has to be established in the UTRAN;
281 • To trigger an outgoing relocation towards LTE network when:
282 o a UE leaves the UMTS network coverage;
283 o a UE enters in a LTE network coverage where the PS service may be
284 transferred with a higher rate;
285 o The UMTS network is congested and a HHO towards LTE is possible;
286 • To configure system information for reselection purpose in order to favor reselection
287 towards LTE network;
288 • To redirect the call towards the LTE at RRC establishment purpose for service or load
289 purpose.
290
291 This FTS describes RNC, NodeB and OAM impacts to cover the following topic:
292 • SIB19 provisioning and scheduling for cell reselection towards LTE.
293

294 3.2 FRS ANALYSIS

295 <guide>The FRS Analysis section should contain a short commentary on the FRS and a list of
296 the FRS Requirements, additional tables should be added if needed to emphasise items such
297 as security or environmental requirement sets. </Guide>
298 3.2.1 FRS Requirements List
299 3.2.1.1 FRS 81436: Mobility between UMTS and LTE: cell reselection
300 From Version 0.5 of FRS-81436
Req. # General Requirements
R1 The system shall support the cell reselection from UTRAN to E-UTRAN
R1.1 For cell reselection, the system shall be able to configure and update/modify the cell reselection
parameters in relevant system blocks SIB19 support is mandatory. (for SIB3 & SIB11 SIB4 & SIB12 for
cell reselection in connected mode CELL-PCH and URA-PCH to E-UTRAN, the requirement is FFS).
(SIB11-bis should be required to supported this requirement)
-> FTS author: The SIB11/12 are not impacted by the feature 81436.
R1.2 For cell reselection, the system shall be able to propagate, schedule & broadcast all related
above SIB parameters
Cell Reselection Sub-requirements (UTRA to E-UTRA):
1. cell reselection in idle mode
2. cell reselection in CELL-PCH connected mode
3. cell reselection in URA-PCH connected mode
301
Req. # Performance / Capacity / Reliability Requirements
R5 refer to UA07.1.2 release performance feature 83661.
To provide some metrics values
302
Req. # Counter Requirements
R6 None
303
Req. # Fault Management and Alarm Requirements
R7 None

304
305
306
Req. # Configuration Management and Parameter Requirements
R8 The system shall provide required parameters & configuration for cell reselection UTRAN to E-UTRAN
(system information blocks)
307
Req. # Billing Requirements
TBD
308
Req. # Serviceability Requirements
TBD
309
Req. # Specific Documentation Requirements
No
310
311
312 3.2.2 Customer Specific Requirements
313 <Guide>Add any Customer Specific Requirements identified during feature analysis</guide>
314 No TBC. It depends also on trials contents.
315
316 3.2.3 FRS Compliancy Matrix
317 3.2.3.1 FRS Compliance Notes

318 <Guide>Define the compliancy of the system solution to the Feature Requirement
319 Specification, include notes where restrictions apply to FRS requirements that will not be fully
320 developed. Reference to an FRS should be against a specific version/edition/date of the FRS
321 - Each requirement will have both a DR0 and a DR1 answer
322 - DR0 possible answers: Feasible (F)/ Not Feasible (NF)/Partially Feasible(PF)/ Not Studied
323 (NS)/ N/A (NA)
324 - DR1 possible answers: Compliant (C)/ Not Compliant (NC)/ Partially Compliant (PC)/ N/A
325 (NA)
326 - Letters in bold (see above) can be used (instead of full word) but in that case a guide has to
327 be added
328 - In case the answer is “Not Feasible”, “Not Compliant” or “Partial Compliancy”, a Comment
329 is mandatory
330
331 </Guide>
332 Based on FRS v0.5
Req Requirement System RNC NodeB oneBTS OAM Comments
# Description
FRS (Ri)
requirements
R1 See 3.2.1.1 F F F F N/A
R1.1 See 3.2.1.1 F F F F N/A SIB11/11bis and 12 not used to
broadcast E-UTRA information.
R1.2 See 3.2.1.1 F F F F N/A
R5 See 3.2.1.1 F F F F N/A
R6 See 3.2.1.1 F F F F N/A No counter needed for SIB.
R7 F F N/A N/A N/A There is no modification: the
existing SIB creation/update
failure management is applied by
the RNC to SIB19.
R8 See 3.2.1.1 F F N/A N/A F
333
334
335 3.2.3.2 Restrictions
336 <Guide>Track Restrictions to the FRS compliancy during FTS development</Guide>
337 In UA071.2 the following restrictions apply:

338 • The number of eUTRA frequencies broadcasted in SIB19 is limited to 2;
339 • The IE Blacklisted cells per freq list is not supported.
340
341 It has also to be noticed, the following IE of SIB19 are not supported in UA07.1.2:
342 • The IE Gsm priority info list ;
343 • The IE UTRAN FDD frequencies.
344
345 3.2.4 Compliancy Matrix Updates
346 <Guide>Track updates to the FRS compliancy after the FTS document has been placed under
347 change control</Guide>
348
349
350 TBD
351

352 3.3 OPEN ISSUES

353 [OI1] Rel 8 also defines dedicated priority concept. As absolute priority criteria the purpose is to set a
354 priority for each frequency of each technology but it applies to a given call. This information is sent by the
355 RNC towards the UE in the message UTRAN MOBILITY INFORMATION message. This dedicated
356 priority may overwrite absolute priority sent in SIB19. In UA07, ALU uses this message after a HHO from
357 2G CS to send PS domain location information (URA ID).
358 Do we have to support it? No in UA071.2. CLOSED
359 [OI2] There is no mean to restrict SIB19 to UE in idle RRC state. As reselection from cell_pch or ura_pch
360 may be an UE option, the question is: is it also an option at E-UTRA side? If yes there will be perhaps an
361 issue. No UE restriction known for UA071.2. CLOSED
362 [OI3] Can have enough FDD cell parameters in order to define two LTE frequencies per Fdd cell.=> Yes
363 CLOSED
364 [OI4] New SIB=> SIB encoding failure to be based on existing RNC behavior: to be reminded.=>Done.
365 CLOSED.
366 [OI5] There are some dimensioning inconsistency between 25331 and 25133. See mail below. No
367 specific control to apply in UA07.1.2. CLOSED
368
RE Rel 8 Number of
frequencies monitored.msg
369
370
371

372 4 FEATURE BENEFITS

373 4.1 CUSTOMER/SERVICE PROVIDER BENEFITS
374 <Guide>Mandatory paragraph, benefit or loss is shortly described</Guide>
375 Feature 81436 allows:
376 • A UE with LTE capability camping on UTRAN to access E-UTRA in idle, cell_pch or
377 Ura_pch mode;
378 • After a CS fallback procedure and the release of the call, the UE may reselect the E-
379 UTRA;
380 • LTE introduction.
381
382
383 4.2 END-USER / SUBSCRIBER BENEFITS

384 <Guide>If applicable benefit or loss is shortly described</Guide>
385 • Better throughput when the PS call is established in (or moved to) the LTE network.
386

387 5 FEATURE DEFINITION

388 <Guide>This chapter is thoroughly studying the functional details of the function.
389 It should contain a complete feature description:
390 New or modified mechanism or algorithm
391 Activation mode description (mandatory Boolean)
392 . New hardware impact</Guide>
393
394
395 5.1 ASSUMPTIONS

396
397 Assumption 1: UA07.1.2 model cannot be modified: only spare parameters may be used;
398 Assumption 2: Interactions with UA08 features will be managed by UA08 features.
399 Assumption 3: This feature will be tested in end to end environment with our LTE solution.
400 Assumption 4: RRC and NBAP Rel 8 (June) are needed in UA07.1.2.
401 Assumption 5: The purpose of this feature is allowing LTE network trial introduction. The number
402 of UE having LTE capability will be low.
403 Assumption 6: the support of absolute priority for GSM frequencies is not requested in UA071.2
404 Assumption 7: the support of absolute priority for inter-frequency FDD cells is not requested in
405 UA071.2.
406 Assumption 8: the support of “blacklisted cell list” IE is not requested in UA07.1.2.
407 Assumption 9: the number of LTE frequencies to be set in SIB19 may be reduced to 2 in
408 UA07.1.2.
409 Assumption 10: UE with LTE capability supports SIB19.
410
411
412
413 5.2 PRINCIPLES

414 5.2.1 UE capability and mobility towards LTE
415 This section is for information only.
416 All mobility procedures towards LTE will be not supported by all UE having RAT LTE capability.
417 The 3GPP will define (discussions in progress) several mobility capability groups which will be
418 reported in UE Radio access capabilities.
419 An extract of the CR 3698 (25.331) is given in section 14.1. This CR specifies the groups of
420 features dealing with mobility towards LTE. We may give the following comments:

421 • A Rel 8 UE may or shall report the EUTRA Feature Group Indicators IE in the UE multi-
422 mode/multi RAT capability IE (section 6.1.1) of the RRC message: it depends on the
423 3GPP release edition: v8.ee =< v8.60 or v8.ee> v8.60.
424 • Reselection from UTRA cell pch/URA pch towards E-UTRA idle is an option;
425 • Reselection from UTRA cell idle towards E-UTRA idle is another option;
426 • E-UTRAN measurements reporting in connected mode is an option;
427 • Reselection from UTRA cell fach towards E-UTRA idle is not allowed.
428
429 In case a UE supports the reselection towards LTE in several RRC states, there is no mean to
430 restrict the mobility in a given state at RNC level.
431 Open item: Is it an issue when the UE is put in x_pch state? How is managed the service
432 continuity between both technologies->Waiting from LTE SAE team feedback? ALU LTE manages
433 the call continuity.
434 In case the IE is not present, the RNC may assume all reselections procedures are supported by
435 the UE. Otherwise before putting a UE with LTE capability in a given RRC state, the RNC may
436 take as input the UE multi-mode/multi RAT capability IE in order to favor the reselection
437 towards LTE. This management will not be supported in UA07.1.2.
438 A Rel8 UE with LTE capability may not be able to support SIB19 when it is x_pch state: Without
439 SIB19 decoding, the UE will not reselect the LTE network and will stay in UTRAN. There is no
440 RNC impact. We assume it will not induce a UE failure in its reselection process.
441
442
443 5.2.2 PLMN and RAT selection
444 The UTRAN is not impacted by LTE technology introduction. The selection process is described
445 in [R2].
446
447
448 5.2.3 Mobility in reselection mode
449 5.2.3.1 UE state eligible to reselection towards E-UTRA
450 Cell pch, URA PCH and idle modes are eligible modes for reselection towards LTE.
451
452 5.2.3.2 SIB impacted
453 The reselection towards E-UTRA doesn’t impact SIB3/4 and SIB11/12. The management by the
454 UE of reselection may be also based on information given in SIB19 to get:
455 • Frequencies priority for all technologies GSM, UTRA and E-UTRA;
456 • E-UTRA Frequencies in order to be able to detect E-UTRA cells.
457 A Rel 8 UE will be able to detect itself E-UTRA cells but it will read SIB11/12 as usual to
458 identify FDD and GSM cells: SIB19 is used to get UTRA and GSM frequencies priorities.

459
460 Note: Even if neighboring FDD frequencies are not supported in SIB19 for UA071.2 we may add
461 the following remark: the number of neighboring FDD frequencies monitored by a UE (SIB11/12
462 for reselection and RRC Measurement Control for connected mode) cannot be higher than 2
463 (3GPP 25133). SIB19 (25331) allows more than 2 FDD frequencies which doesn’t match with
464 previous definition.
465
466 5.2.3.3 SIB19 content
467 Managing the reselection towards LTE requires the use of SIB19 (new SIB) created in 3GPP Rel
468 8. This SIB contains the following information:
469 • “UTRA priority info list” (IE MP) (description given in section in section 6.1.1.1.2) which
470 contains the “UTRA Serving Cell” IE (MP) and the “UTRAN FDD frequencies” IE (OP).
471 The “UTRAN FDD frequencies” IE will be not supported in UA07.1.2.
472 • “GSM priority info list” (IE OP) (description given in section 6.1.1.1.3). This IE will be
473 not supported in UA07.1.2.
474 • E-UTRA frequency and priority info list (IE OP) (description given in section in section
475 6.1.1.1.2)
476 The definition of each parameter is detailed in section 6.1.1.
477 This new SIB allows setting priorities for different access technologies. Inside a given
478 technology different priorities may be used per frequency.
479 Favoring or not a reselection towards an E-UTRA frequency is described in section 5.2.3.11.
480 The parameters have to be defined at OAM level in order to be provisioned by the operator.
481 The description of the parameters in the UA07.1.2 model is given in section 7.1.
482
483
484
485 5.2.3.4 SIB19 reading by UE
486 This section is formation only: it concerns the UE only.
487 The section 8.1.1.1.2 of [R1] indicates this SIB is read by the UE in idle, cell fach, cell pch and
488 ura pch. The SIB contain is also valid in the same UE RRC states. Except there is a specific
489 behavior in cell fach concerning the E_UTRA frequency information: it is consistent with section
490 5.2.3.1 -> cell fach state is not eligible to mobility towards E-UTRA.
491
492 The section 8.4.1.9.3 of [R1] indicates upon transition from idle mode to CELL_FACH state, the
493 UE shall stop monitoring the list of E-UTRA frequencies assigned in the IE "E-UTRA frequency
494 and priority info list" in System Information Block type 19.
495
496 The section 8.4.1.9a.3 of [R1] indicate upon transition from connected mode to idle mode, the
497 UE shall begin monitoring E-UTRA frequencies listed in the IE "E-UTRA frequency and priority
498 info list" received in System Information Block type 19.

499
500 The section 8.4.1.9a.3 of [R1] indicates upon transition from CELL_FACH to CELL_PCH or
501 URA_PCH, the UE shall begin monitoring E-UTRA frequencies listed in the IE "E-UTRA frequency
502 and priority info list" in System Information Block type 19.
503
504 Open item: For inter frequency and 2G neighboring the reselection process is based on
505 information contained in two types of SIB 11/12 and 19. The modification of SIB11/12 and
506 SIB19 may be not synchronous.
507 => The issue is reduced by setting the same repetition period (RP).
508
509 Open item: Repetition period of SIB11/12 and SIB19: need to be equal? See next section.
510
511
512 5.2.3.5 SIB scheduling
513 5.2.3.5.1 MIB/SB1 structure
514 The support of SIB19 impacts the NodeB (new system information block to broadcast) and the
515 SIB scheduling algorithm of the RNC. This dynamic algorithm is in charge of:
516 • Setting the scheduling of each SIB (position and period);
517 • Building and sending the NBAP System Information Update message.
518
519 The SIB19 is encoded in a SIB type extension2 IE (new RRC IE created in Rel 8).
520
521 The size of the SIB19 will be limited. In order to not impact the repetition period value of
522 others SIB, the repetition period of SIB19 has to be set with the same repetition period as SIB11
523 and SIB12.
524
525 For reminding the structure of the SIB blocks is given below. Due to the number of SIB
526 segments the RNC may use a SB1 block, as an extension of the MIB block, in order to index all
527 SIB segments. The figure below describes the relation btw MIB/SB1 blocks and SIB blocks.
528
529 MIB | ------------->SIB “A”
530 |-------------->……
531 |-------------->SIB”F”
532 |--------------> SIB type extension2[1..maxSIB] (OP)
533 | -------------->SB1| -------------------> SIB “X”
534 | ------------------> …..
535 | ------------------->SIB “W”

536 | ------------------> SIB type extension2[1..maxSIB] (OP)
537
538
539 The use of SB1 is sufficient in UA07.1.2, no need to support the SB2.
540 The reference to the SIB19 may be either in the MIB or in the SB1 block. The new specific RRC
541 IE “References to other extension system information blocks2” has to be used by the RNC:
542 Due to the adding of a new SIB, the NodeB will be impacted: it has to support this new SIB and
543 the impact on the number of transports blocks (= Sum of all segments of each SIB and SB) may
544 be impacted.
545
546 Open item: Impact of SIB type extension2 IE to be detailed in FTS or RNC FS. TBC
547

548 5.2.3.5.2 Number of transport blocks (TB)
549 The number of different transport block is increased with the addition of SIB19 block.
550 Open item: NodeB impacts for each NodeB hardwaretype.
551 OneBTS can support up to 64 TB’s, and iBTS (iCEM, xCEM) configurations can support up to
552 70TB’s.
553
554 UA07.1.1 and UA07.1.2 status
555 The total number of transport blocks (TB) is given below. Even if the total number of TB is not
556 identified for SIB19, the total number of TB will not exceed 64 and may be encoded in one
557 NBAP system information update message.
558
SIB block type Number of TBs The values Feature impacting the
may be lower than 3GPP number of segments
max values.
UA07.1.1 UA7.1.2
(Min..Max
(Min..Max value)
value)
MIB 1..1 1..1
SIB1/7 1..1 1..1
SIB2 0..1 0..1
SIB3 1..3 1..3
SIB4 0..2 0..2
SIB5 1..7 1..8 UA07 MBMS feature 31868

changes the SIB5 max size
to 8.
SIB6 0..4 0..4
SB1 0..2 0..2 Assumption for the worst

case= 2 segments
SIB11 1..16 1..16
SIB12 0..16 0..16
SIB19 0..0 0..2 (max=2 tbc) SIB19 is added in

UA07.1.2. The number of
TBs has to be confirmed
with catapult
Min/Max Number of 6..53 6..56

TBs depending of
SIB19 max size.
559
560 Open item: In UA07.1.1, no new SIB is added and there is no increase of the number of TBs for
561 a given SIB. Based on SIB11/12 feature (UA06), can the RNC confirm the number of segments
562 used by each SIB in UA06?

563
564 5.2.3.5.3 SIB position and repetition period setting by the RNC
565 The current RNC algorithm is reminded with the adding of SIB19.
566 The goal is to map each MIB/SIB segment onto a SFN (each segment needs two SFN).
567 The SIB scheduling information encoding in MIB occur in the following order: SIB1/7, SIB3, SIB4
568 with repetition period RP0 then SIB2, SIB5, SIB6, SIB11, SIB12, SIB19 with repetition period
569 RP1.
570 When all scheduling information of a SIB cannot be coded in one MIB segment, the SB1 block
571 has to be used. To be able to encode the scheduling information SB1 in the MIB, another SIB
572 may also be moved from MIB to SB1.
573 A MIB size shortage may occur during MIB ASN1 encoding. The SIB scheduling information
574 (whatever the SIB) which cannot be encoded in MIB are encoding in SB1.
575 For reading efficiency by the UE, the SB1 position has to be lower and its repetition period
576 lower or equal than the SIBs which have their scheduling information coded in SB1.
577 The ALU NodeB requests a RP (Repetition Period) lower than 512. The RNC will keep the RP
578 max value equal to 256.
579 Repetion (RP) max values are set for performance reason (i.e. SIB reading by the mobile):
580 • SIB 3 and 4 use the same repetition period: RP0. The setting of RP0 has a
581 higher priority than RP1.
582 • SIB 2, 5, 6, 11, 12, 19 use the same period RP1 which depends on the SIB
583 presence and the number of SIB segments to be broadcasted for each SIB.
584
585 Some holes (i.e. SFN empty) may be created in the scheduling.
586
SIB block type Repetition period Comment
Preferred Max
MIB 8 8
SIB1 16 16 SIB1&SIB7 in the same SFN.
SIB2 RP1 RP1
SIB3 RP0=32 128
SIB4 RP0=32 128
SIB5 RP1 RP1
SIB6 RP1 RP1
SIB7 16 16 SIB1&SIB7 in the same SFN
SIB11 RP1 256
SIB12 RP1 256

SIB19 RP1 256 New
SB1 RP0 or RP1 256 The preferred repetition period

depends on the Min RP of the SIB
addressed by SB1.
587
588
589
590
1- SFN=0 Period=8 is affected to the MIB and SFN=2 Period=16 for SIB1/7
2- If all information cannot be coded in one MIB segment, use SB1 and put SIB scheduling
information which cannot be set in MIB. The SB1 repetition period will be set to the lowest
repetition period of the SIB referenced by SB1: either RP0 or RP1.
3- RP0 is set with the lowest preferred value 32 (it concerns SIB3, SIB4 and optionally SB1);
4- Use RP0 and identify:

SFN (i) used after mapping in increasing size order SIB3, SIB4. According to
step 2 if SB1 has the repetition period RP0, it has to be mapped before theses
SIB.
SFN(j) free available for other SIB
5- RP1 is set with the lowest preferred value 32 (it concerns SIB2, 5, 6, 11, 12, 19 and optionally
SB1;
6- Use RP1 and identify SFN(k) for the mapping of other SIBs (in increasing size order).
According to step 2 if SB1 has the repetition period RP1, it has to be mapped before theses SIB.
If SB1 and all SIB may be mapped then the scheduling building is finished
If RP1 < 256 increase RP1 (RP1= RP1 * 2) and re-start the process at the step 5
If RP1 = 256 and RP0 < 128 increase RP0 (RP0= RP0 * 2) and re-start the process
at the step 3
If RP1 = 256 and RP0 = 128 then the scheduling cannot be set: the cell is put in
“Disable-failed” state.
591
592
593 5.2.3.5.4 SIB scheduling use case

594 In case of all segments (SB1 also) are used in UA07.1.2 (see table above) the following table
595 gives a view of the SIB positioning.
596 Note: In this use case SIB5 size is equal to 7 segments.
597
598 The algorithm gives RP0=64 and RP1=256.
599
600
601
TB TB TB TB TB TB TB TB
SFN Content # Content # Content # Content # Content # Content # Content # Content #
0 MIB 1 SIB7+1 2 SIB4-1 3 SIB4-2 4 MIB 1 SIB3-1 5 SIB3-2 6 SIB3-3 7
16 MIB 1 SIB7+1 2 SIB2 8 SIB6-1 9 MIB 1 SIB6-2 10 SIB6-3 11 SIB6-4 12
48 MIB 1 SIB7+1 2 SIB5-6 18 SIB5-7 19 MIB 1 SB1-1 20 SB1-2 21 SIB11-1 22
64 MIB 1 SIB7+1 2 SIB4-1 3 SIB4-2 4 MIB 1 SIB3-1 SIB3-2 15 SIB3-3 43
80 MIB 1 SIB7+1 2 SIB11-2 23 SIB11-3 24 MIB 1 SB11-4 25 SIB11-5 26 SIB11-6 27
SIB11- SIB11-
96 MIB 1 SIB7+1 2 SIB11-7 28 SIB11-8 29 MIB 1 SIB11-9 30 10 31 11 32
SIB11- SIB11- SIB11- SIB11- SIB11-
112 MIB 1 SIB7+1 2 12 33 13 34 MIB 1 14 35 15 36 16 37
SIB12-
160 MIB 1 SIB7+1 2 SIB12-6 43 SIB12-7 44 MIB 1 SIB12-8 45 SIB12-9 46 10 47
SIB12- SIB12- SIB12- SIB12- SIB12-
176 MIB 1 SIB7+1 2 11 48 12 49 MIB 1 13 50 14 51 15 52
SIB12-
208 MIB 1 SIB7+1 2 16 53 SIB19-1 54 MIB 1 SIB19-2 55
224 MIB 1 SIB7+1 2 MIB 1
240 MIB 1 SIB7+1 2 MIB 1
602
603
604
605
606 5.2.3.6 UE cell Reselection : which process
607 The UE reselection process depends on the setting or not of absolute priorities for inter freq
608 and inter rat cells (given by SIB19):
609 • The legacy reselection process applies (see sections 5.2.3.7 and 5.2.3.8) :
610 The basic cell re-selection criteria are used for intra-frequency cells, inter-frequency
611 cells if no absolute priority information for any inter-frequency layer is available to the
612 UE, and inter-RAT cells if no absolute priority information for any inter-RAT layer is
613 available to the UE for that RAT.

614 • If absolute priority criterion is used, a new reselection process applies (see section
615 5.2.3.9).
616 When the absolute priority or a threshold is not given for a frequency or for a subset of
617 frequencies within neighboring cells are configured: these neighboring cells are
618 discarded from the reselection process.
619
620 Open item: It seems the two reselection procedures may be processed simultaneously. If each
621 process identifies a target cell which cell will be selected by the UE: best radio level
622 (suggested by Nicola Puddle but no confirmation found in 3GPP). It has an impact on the way to
623 provision the SIB19 and the control the OAM have to do in order to guarantee a consistency in
624 the provisioning. To be studied. It is confirmed the two reselection process may be processed
625 independently. There is no specific OAM check.
626 For a better understanding of 3GPP reselection process description, it has to be noticed: When
627 3GPP mentions FDD inter frequencies the serving FDD cell is not included.
628
629
630 5.2.3.7 UE cell Reselection : criteria when absolute priority and HCS are not used
631 The criteria to trigger neighboring measurements are described in section “5.2.6.1.1
632 Measurement rules for cell re-selection when HCS is not used” of 3GPP [R2].
633 The criteria to trigger a reselection are described in section “5.6.1.2.4 cell reselection criteria”
634 of 3GPP [R2].
635
636 5.2.3.8 UE cell Reselection : criteria when absolute priority is not used and HCS is used
637 The criteria to trigger neighboring measurements are described in section “5.2.6.1.2
638 Measurement rules for cell re-selection when HCS is used” of 3GPP [R2].
639 The criteria to trigger a reselection are described in section “5.6.1.2.4 cell reselection criteria”
640 of 3GPP [R2].
641
642 5.2.3.9 UE cell Reselection : criteria when absolute priority is used
643 This use case applies when at least one absolute priority value is given for a frequency among
644 all frequencies used in the neighboring provisioning which means:
645
646 • UTRA priority info list (IE MP) is present (at least the serving frequency is always
647 present)
648 OR
649 • GSM priority info list (IE OP) is present
650 OR
651 • E-UTRA frequency and priority info list (IE OP) is present
652

653
654 5.2.3.9.1 Measurement triggering criteria
655 For the UE the criteria to trigger neighboring measurements are described in section
656 “5.2.6.1.2a Measurement rules for inter-frequency and inter-RAT cell reselection when
657 absolute priorities are used” of 3GPP [R2]
658 The UE behavior described in the following sections has the following impacts on the UTRAN
659 provisioning:
660 o It is not mandatory to set the absolute priority for each frequency of a given
661 RAT;
662 o Priority setting of the GSM frequency is optional; a subset of frequency
663 priority setting may be done;
664 o Priority setting of the E-UTRAN frequencies is optional;
665 o The network should ensure that priorities for different Radio Access
666 Technologies are always different.
667
668 The operator has to be aware of the following impact:
669 o When a subset of inter frequencies have no priority (see section 5.2.3.9.2) for
670 a given Rat, the other part of frequencies is not measured;
671 o When no absolute priority value is set for a given RAT(see section 5.2.3.9.2),
672 the basic measurement triggering criteria apply.
673
674 Open item: see open item of section 5.2.3.6. It may have an impact of the way to set the
675 parameters at OAM level. No impact.
676 Open item: Do we have to support the setting of GSM frequency priority. There is a
677 dependency with the open item above. There is no need to support it in UA07.1.2.
678 Open item: The feature purpose is to have a basic management of mobility with LTE
679 technology. The FRS doesn’t request to support absolute priorities for GSM frequencies and
680 for neighboring FDD frequencies. In case the UE cannot access E-UTRA for radio coverage
681 reason, the UE will remain camping on UTRA and the reselection between UTRA frequencies
682 will follow either the legacy cell reselection process if absolute priority is not set for each
683 neighboring inter frequency carrier or the new cell selection process with if absolute priority
684 is used. The choice of the 2G inter rat cell reselection process follows the same assumptions
685 based on the setting or not of absolute priority of each GSM carrier.
686
687 5.2.3.9.1.1 Inter frequency measurements criteria
688 This section deals with UE behavior and is for information purpose.
689
690 Extract of [R2]5.2.6.1.2a:
691 “If the UE has received absolute priority information for inter-frequency layers, the UE shall
692 follow these rules:

693 • The UE shall perform measurements of inter-frequency layers with a priority higher
694 than the priority of the current serving layer.
695 NOTE: The rate of these measurements may vary depending on whether Srxlev and Squal of
696 the serving cell are above or below Sprioritysearch1 and Sprioritysearch2. This is specified in
697 [10].
698 …..
699 …..
700 • For inter-frequency layers with a priority equal or lower than the priority of the
701 current serving layer:
702 - If SrxlevServingCell > Sprioritysearch1 and SqualServingCell >
703 Sprioritysearch2 the UE may choose not to perform measurements of
704 inter-frequency layers of equal or lower priority.
705 - If SrxlevServingCell <= Sprioritysearch1 or SqualServingCell <=
706 Sprioritysearch2 the UE shall perform measurements of inter-frequency
707 layers of equal or lower priority.
708 • The UE shall not perform measurements of inter-frequency layers for which the UE has
709 no absolute priority.
710
711 If the UE has received absolute priority information for inter-RAT layers, the UE shall follow
712 these rules:
713 • The UE shall perform measurements of inter-RAT layers with a priority higher than the
714 priority of the current serving cell.
715 NOTE: The rate of these measurements may vary depending on whether Srxlev and Squal of
716 the serving cell are above or below Sprioritysearch1 and Sprioritysearch2. This is specified in
717 [10].
718 • For inter-RAT layers with a priority lower than the priority of the current serving cell:
719 - If SrxlevServingCell > Sprioritysearch1 and SqualServingCell >
720 Sprioritysearch2 the UE may choose not to perform measurements of
721 inter-RAT layers of lower priority.
722 - If SrxlevServingCell <= Sprioritysearch1 or SqualServingCell <=
723 Sprioritysearch2 the UE shall perform measurements of inter-RAT layers of
724 lower priority.
725 • The UE shall perform measurements according to subclause 5.2.6.1.1 for inter-RAT
726 layers for which the UE has no absolute priority. For all inter-RAT layers belonging to
727 one RAT, either the rules above or the rules in subclause 5.2.6.1.1 or 5.2.6.1.2 shall
728 apply.”
729
730 5.2.3.9.2 Cell reselection triggering criteria
731 This section deals with UE behavior and is for information purpose.
732

733 The criteria to trigger a reselection are described in section “5.2.6.1.4a Absolute priority based
734 criteria for inter-frequency and inter-RAT cell reselection” of 3GPP [R2].
735
736 [R2] Extract:
737
738 “Absolute priorities of different absolute priority layers may be provided to the UE. The
739 following cell reselection criteria are used for inter-frequency cells if absolute priority
740 information for inter-frequency is available to the UE, and inter-RAT cells if absolute priority
741 information for inter-RAT is available to the UE.
742 If priority information is provided for any inter-frequency layers, cells belonging to layers for
743 which no priority or no threshold is assigned shall not be considered for reselection.
744 If priority information is provided for any inter-RAT layers in a RAT of the selected PLMN, cells
745 belonging to layers in that RAT for which no priority or no threshold is assigned shall not be
746 considered for reselection.
747 If none of the inter-frequency layers in UTRAN of the selected PLMN are provided with both
748 priority and threshold parameters, the cell reselection criteria in subclause 5.2.6.1.4 shall
749 apply for inter-frequency layers in UTRAN.
750 If none of the inter-RAT layers in a RAT of the selected PLMN are provided with both priority
751 and threshold parameters, the cell reselection criteria in subclause 5.2.6.1.4 shall apply for
752 that RAT.
753 NOTE: In order not to apply absolute priority but the cell reselection criteria in subclause
754 5.2.6.1.4 for inter-frequencies cell reselection in UTRAN or for inter-RAT cell reselection, the
755 network may choose to configure no inter-frequency layers in UTRAN or no inter-RAT layers in
756 a RAT in SIB19 even though dedicated priorities are provided.
757 For all inter-frequency layers or all inter-RAT layers belonging to one RAT of the selected
758 PLMN, either the criteria below or the criteria in subclause 5.2.6.1.4 shall apply.”
759
760 Open item: Do we have to support the priority setting for each neighboring inter frequency and
761 each GSM frequency in UA07.1.2? Not mandatory but having a reselection process based for a
762 given part only on priority may be not so easy for the operator. We may also face up:
763 • UE bugs when processing the two reselection algorithms;
764 • Design cost to set all IE in SIB19;
765 • Lack of spare parameters in UA07.1.2.
766 It has to be discussed with RNC team.
767 => In UA07.1.2, no priority will be managed for inter frequency and 2 neighboring
768 frequencies.
769
770
771 5.2.3.10 UE cell Reselection process using absolute priority
772 This section deals with UE behavior and is for information only.

773 Extract of [R2] 5.2.6.1.4a:
774 The following definitions apply:
775 - Criterion 1: the SrxlevnonServingCell,x of a cell on an evaluated higher absolute
776 priority layer is greater than Threshx,high during a time interval Treselection;
777 - Criterion 2: SrxlevServingCell < Threshserving,low or SqualServingCell < 0 and the
778 SrxlevnonServingCell,x of a inter-frequency cell on an evaluated equal absolute priority layer
779 is greater than Threshx,low during a time interval Treselection;
780 - Criterion 3: SrxlevServingCell < Threshserving,low or SqualServingCell < 0 and the
781 SrxlevnonServingCell,x of a cell on an evaluated lower absolute priority layer is greater than
782 Threshx,low during a time interval Treselection;
783 Cell reselection to a cell on a higher absolute priority layer than the camped frequency shall
784 be performed if criterion 1 is fulfilled.
785 Cell reselection to an inter-frequency cell on an equal absolute priority layer to the camped
786 frequency shall be performed if criterion 2 is fulfilled.
787 Cell reselection to a cell on a lower absolute priority layer than the camped frequency shall
788 be performed if criterion 3 is fulfilled.
789 If more than one cell meets the above criteria, the UE shall reselect the cell with the highest
790 SrxlevnonServingCell,x among the cells meeting the criteria on the highest absolute priority
791 layer.
792 The UE shall not perform cell reselection to cells for which the cell selection criterion S is not
793 fulfilled.
794 The UE shall not perform cell reselection until more than 1 second has elapsed since the UE
795 camped on the current serving cell.
796 For UE in RRC connected mode states CELL_PCH or URA_PCH the interval Treselections,PCH
797 applies, if provided in SIB4 (see [4]), while for UE in RRC connected mode state CELL_FACH the
798 interval Treselections,FACH applies, if provided in SIB4 (see [4]).
799 In all the above criteria the values of Treselections, Treselections,PCH or Treselections,FACH
800 apply for Treselection and are scaled according to the UE mobility state and target RAT, as
801 specified in 5.2.6.1.1a.
802
803 5.2.3.11 How favoring a reselection towards E-UTRA
804 The main use case we want to cover is:
805 • The UTRAN network is configured with one or several FDD layers. Two 2G layers and a
806 LTE layer are configured as neighboring frequencies.
807 • The feature purpose is to be able to have a basic management of the reselection from
808 UTRA to E-UTRA.
809
810 It would be possible to favor reselection towards LTE for a UE with LTE capability camping on
811 UTRAN by using the following SIB19 setting for a given FDD cell:
812 • Absolute priority and measurements parameters are configured for the FDD serving and
813 for the LTE frequency (priority higher than the FDD serving cell);

814 • no absolute priority for others FDD frequencies and for 2G frequencies.
815
816 The UE will process the following cell reselection process:
817 - inter frequency cell reselection 2G inter rat cell reselection based on the legacy
818 algorithm;
819 - LTE inter rat cell reselection based on the new algorithm using absolute priorities
820
821 In case legacy and new algorithms apply simultaneously (same radio conditions) the UE may
822 select or not the best target cell among the cells selected by each reselection process.
823 If the UTRAN doesn’t want to favor a reselection towards E-UTRAN, it doesn’t have to
824 broadcast SIB19.
825
826 Open item: see open item of section 5.2.3.6.
827 Open item: see open item of section 5.2.3.9.
828
829 5.2.3.12 Cell re-selection process: number of frequencies and cells
830 3GPP document defines the UE measurement requirements during reselection process:
831
832 Extract of [R8] 4.2.2.8 : Number of cells in cell lists
833
834 For idle mode cell re-selection purposes, the UE shall be capable of monitoring:
835 - 32 intra-frequency cells (including serving cell), and
836 - 32 inter-frequency cells, including
837 - FDD cells on maximum 2 additional carriers, and
838 - Depending on UE capability, TDD cells distributed on up to 3 TDD carriers, and
839 - Depending on UE capability, 32 GSM cells distributed on up to 32 GSM carriers, , and
840 - Depending on UE capability, up to 4 E-UTRA carriers, and
841 - Depending on UE capability up to 4 E-UTRA TDD carriers
842 as indicated in cell information lists sent in system information (BCCH).
843
844 For a UE supporting E-UTRA measurements in RRC_IDLE state, the UE shall be capable of
845 monitoring a minimum total of at least 8 carrier frequency layers, including the
846 intrafrequency serving layer and comprising of any allowed combination of E-UTRA FDD, E-
847 UTRA TDD, UTRA FDD, UTRA TDD and GSM layers (one GSM layer corresponds to 32 cells).
848
849 The requirements are the same in cell_pch and ura_pch. We may see the maximum number of
850 E-UTRA carriers is different in documents [R1] and [R8]: see open issue in section 3.3.

851
852
853 5.2.4 System information update procedure
854 The system information are broadcasted by the NodeB over the radio interface. The section 5.7
855 reminds the data flow between UE, NodeB and RNC already used in previous UTRAN releases.
856 Adding SIB19 doesn’t modify the data flow.
857 ALU RNC does not manage relative system information changes. That means each time RNC
858 needs to send an update of one SIB, it recomputes the scheduling of all SIBs. All SIB are present
859 in the NBAP message and SIB previously scheduled are set with the IE “IB Deletion indicator”
860 set to “deletion”. NodeB overwrites the previous information with the newly received
861 information.
862
863 As there is a new SIB, errors may occur at different levels:
864 • During RRC SIB19 content ASN1 encoding with operator provisioning;
865 • When the NodeB processes the NBAP System information message sent by the RNC.
866
867 The RNC and NodeB defense behaviors have to be the same as SIB:
868 • If the SIB19 encoding fails the RNC has to process the same behavior as others optional
869 SIB;
870 Open item: RNC behavior to be checked. If an optional SIB (SIB19, 12,4)fails, the failed SIB
871 is not skipped over. The whole SIB would fail. If this happens during a class3 parameter
872 modification (Cell is operational), the cell is degraded with a SCN. If this happens at cell
873 setup or unlock, the cell is deleted.
874 • If the NodeB doesn’t support the NBAP message with a scheduling including SIB19, it
875 has to return a NBAP System Information Failure as in previous UTRAN release.
876
877

878 5.3 SOLUTION OPTIONS

879 <Guide> define alternative options to solving the FRS Requirements and explain why a
880 particular solution may be preferable</Guide>
881 The following options are not exclusively alternative options but also options given by the
882 3GPP.
883
884 5.3.1 Absolute priority use for FDD frequencies and GSM Frequencies.
885 The absolute priority is optional in case of inter frequency and inter rat reselection process.
886
887 PRO: use case Tbd
888 CONS: use case Tbd
889
890 See open item of sections 5.2.3.6 and 5.2.3.9.
891 => Not requested in UA07.1.2.
892
893
894 5.3.2 Frequency Dedicated priority management
895 3GPP introduces the use of frequency dedicated priority which may overwrite absolute priority
896 broadcasted in system information.
897 PRO: use case Tbd
898 CONS: use case Tbd
899
900 It is proposed to not use dedicated priority management in UA07.1.2.
901
902 5.3.3 Others
903 Empty.
904
905 5.4 FEATURE DEPENDENCIES

906 <Guide>This Chapter describes the dependencies of this function on other functions within the
907 system, or to describes features / functions that are mutually exclusive with this
908 feature/function.</Guide>
909
910 No dependency with UTRAN features.
911 Dependency with UE: UE needs to support SIB19 and LTE capability.

912 5.5 INTER SUB-SYSTEM FUNCTIONAL DISTRIBUTION

913 <Guide>This chapter describes the inter subsystems distribution across network elements and
914 relations of the function</Guide>
915 5.5.1 Sub System Impacts
916 <Guide>This section should be used to provide a reference to how individual FRS requirements
917 are supported by different subsystems so that in the event of FRS requirements being
918 descoped the impacts can be easily identified. Use subheadings relating to each subsystem
919 impacted such as BTS Impacts or RNC Impacts. Rename the sample below if appropriate. A
920 requirements object should be tagged with Object Type / Product Elements / Feature Number
921 / Review Status, all other objects do not need to have these fields populated.</Guide>
922 5.5.1.1 BTS Impacts
923 o SIB19 support;
924 o NBAP Rel 8 to support SIB19.
925
926 The feature is not requested for Micro and pico. Micro and Pico will keep the UA06 functional
927 level. The feature has to be deactivated at cell level (see section 7.1.1.2).
928 The feature is requested for all ALU NodeB types: iBTS and OneBTS.
929 It has the same impact for all iBTS (i/x)CCM and (i/x/e)CEM.
930
931 5.5.1.2 RNC Impacts
932 o SIB19 support
933 o RRC Rel 8 for the SIB19 content setting and encoding;
934 o NBAP Rel 8 to support SIB19.
935
936
937 5.6 REQUIREMENTS

938 <Guide>This chapter offers a set of clear, atomic, verifiable, requirements that will help in
939 the global understanding of the specification. Supporting text is used to provide context to
940 the requirements. A requirements object should be tagged with Object Type / Product
941 Elements / Feature Number / Review Status, all other objects do not need to have these fields
942 populated. Requirements are not limited to this section, where requirements fit in other
943 sections of the document they may do so. Requirements any where in the document should
944 have the attributes noted above completed</Guide>
945 Supporting text here that gives context etc.
946 N/A to UA07.
947 <Start:FTS-XXXX-418>
948 The system / box shall......
949

950 Feature Number:
951 Review Status:
952 Product Elements:
953 <End: FTS-XXXX-418>

954 5.7 USE CASES

955 <Guide>This chapter offers a set of relevant scenarios that will help in the global
956 understanding of the specification, and the definition of the test paths.
957 For example it can show a successful communication scenario, with the complete data flow
958 chain (with and without the activation flag set). This has to be defined at the functional level.
959 Remember to include the typical error and feature activation cases particularly when facing
960 nodes with another functional level (inter-release compatibility).
961 The use cases should mention for each scenario which counters and timers should be
962 incremented, if the scenario triggers emission of a state change or of an alarm, where a trace
963 point should be placed.</Guide>
964 5.7.1 Initial Cell setup
965 For reminding, the cell setup data flow with SIB broadcasting, applicable also in case of SIB19
966 use, is given below.
967
968 Extract of [A4]. The detail of each message purpose is given in this document.

Node B RNC OMC
1. Cell Setup Request
2. Resource check and

action
3. Rx and Tx switch
ON
4. Cell Setup Response
5. Common Transport Channel Setup Request

(for each configured S-CCPCH)
6. Resource check and

action
7. Common Transport Channel Setup Response

(for each configured S-CCPCH)
8. ALCAP Transport bearers establishment

(for each DL CTrCH mapped on S-CCPCH(s))
9. Common Transport Channel Setup Request

(for RACH)
10. Resource check
and action
11. Common Transport Channel Setup Response

(for RACH)
12. ALCAP Transport bearers establishment

(for RACH)
13. PHYSICAL SHARED CHANNEL

RECONFIGURATION (HS-DSCH, E-DCH)
(optional)
14. SYSTEM INFORMATION UPDATE

14. Cell State Change
(Enabled / NS)
15. COMMON MEASUREMENT INTIATION
969
970 Figure 2: Initial cell setup procedure
971
972
973 5.7.2 SIB update error at initial cell setup

974 For reminding, the cell setup data flow with SIB update error, applicable also in case of SIB19
975 use, is given below.
976
977 Extract of [A4]:
978
UE Node B RNC OMC-R
System Information Update Failure

1
2
Cell Deletion
Cell State Change2
Uu Iub
979
980 Figure 3: NBAP System information update failure
981
982
983 1. The Node B sends an NBAP-c System Information Update Failure message to the
984 RNC.
985 2. The RNC triggers a Cell Deletion sequence. The RNC reports the unsuccessful
986 update of the system information via a Cell State change message indicating the
987 Cell state Disabled/Failed to the OMC-R,.
988 The RNC shall consider the cell as disabled. Resolving this situation is then up to
989 the operator (as a reminder, the cell configured in the Node B is not removed by
990 the CRNC). In this case, the operator may realize that there was an error for the
991 setup/update of this cell, and can correct the error in the system information.
992 Two cases must be considered :
993 • The corrected parameter cannot be taken into account on-line in which
994 case a RNC restart is necessary.
995 • The corrected parameter can be taken into account on-line (without
996 outage). In this case it is not useful to restart the RNC and an update is
997 initiated.
998
999
1000

1001 5.7.3 SIB update dynamically initiated by the RNC
1002 For reminding, the SIB update data flow, applicable also to SIB19 setting modification, is given
1003 below.
1004
1005 Extract of [A4]. The detail of each message purpose is given in this document.
1006
UE Node B RNC
System Information Update Request

1
All SIB(s)+new MIB)
System Information Update

2
Response
3
PCCH/PCH: Paging Type 1 (new MIB)
4
BCCH/FACH: System Information Change Indication
BCCH/BCH: System Information

5
(new MIB)
BCCH/BCH: System Information

6
(all SIBs)
1007 Uu Iub
1008 Figure 4: NBAP System Information update procedure

1009 5.8 FEATURE INTERWORKING

1010 No impact.
1011
1012 5.9 PERFORMANCE IMPACTS

1013 <Guide>This chapter describes the impacts of the function on performance aspects of the
1014 system</Guide>
1015 5.9.1 System Performance
1016 SIB process is impacted at RNC and NodeB: more information to be broadcasted.
1017
1018 5.9.2 Dimensioning
1019 NodeB: number of transport blocks is increased.
1020
1021 5.9.3 Capacity
1022 No impact
1023
1024 5.9.4 Dependability, Availability and Reliability
1025 - The support of SIB19 by the RNC, NodeB and UE is needed.
1026 - The reselection in CELL PCH and URA PCH depends on the PS core network capability to
1027 retrieve the PDP context after reselection. => supported by ALU LTE solution in LA2.0.
1028
1029 5.9.5 End User Performance
1030 The UE may be able to select automatically the LTE technology when camping in UTRA.
1031 The reselection process may be a bit heavier.
1032
1033 5.10 SECURITY

1034 <Guide>Description of the security requirements impacts when products, systems, services
1035 and/or platforms are introduced into the Wireless Network Services environment</Guide>
1036 Nothing
1037 5.11 ENVIRONMENTAL IMPACTS

1038 <Guide>This chapter defines if there are any environmental impacts from adding this function
1039 to the system</Guide>
1040 N/A
1041

1042
1043
1044 5.12 STANDARDS (COMPLIANCY AND SUPPORT)

1045 The feature is introduced in UA07.1.2. The UA07 initially recommends the support of 3GPP Rel
1046 7. But this feature needs some 3GPP Rel 8 definitions in NBAP and RRC to support SIB19.
1047 There are two possibilities: introduction of a set of CRs OR use the complete Rel 8 for NBAP and
1048 RRC.
1049 Open topic: to be confirmed by UA07.1.2 Project management. Rel 8 of June for NBAP and RRC
1050 Confirmed.
1051
1052
1053 5.13 BILLING SYSTEM IMPACT

1054 N/A
1055 5.14 UPGRADE REQUIREMENTS

1056 <Guide>This chapter defines system requirements and impacts on the system during upgrade
1057 related to the feature defined in this FTS. OAM upgrade routines are defined insection
1058 8.1</Guide>
1059 5.14.1 Pre-Checks
1060 <Guide>Define any checks that should be made before applying the Features defined in this
1061 FTS</Guide>
1062 Feature is deactivated.
1063
1064 5.14.2 Functionality Change due to Upgrade
1065 <Guide>Define changes in system functionality when this feature is applied in particular any
1066 items that are degraded or removed should be detailed</Guide>
1067 Reselection depends on UE capability/performance and LTE network reliability.
1068

1069 6 INTERFACE REQUIREMENTS

1070 <Guide>Description of the new or modified procedures and messages taken into account.
1071 If a chapter is not relevant (or respectively remains unchanging) indicate "not applicable" (or
1072 respectively "no modification"). Interfaces listed here are for the UMTS Product Stream, Adjust
1073 the headings as appropriate for interface sets for other product streams when
1074 required</Guide>
1075 6.1 UMTS INTERFACES

1076
1078 The system / box shall......
1079
1080 Feature Number:
1081 Review Status:
1084
1085 The FRS 36246 gives the 3GPP baseline:
1086
Interface 3GPP Release Spec Version

Iu-CS 3GPP R7 March 2008 except June 2008 for
Uu.
Iu-PS 3GPP R7
Iur 3GPP R7
Iub 3GPP R8
Radio (Uu) 3GPP R8
Iu-BC 3GPP R7
Iu-PC (*) 3GPP R7
1087
1088 Tableau 1: 3GPP Interface Releases references

1089
1090 Open item: SIB19 supports needs Iub and RRC Rel 8 or a set of CRs. Iub and Rrc rel8 confirmed
1091 in UA07.1.2.
1092

1093 6.1.1 Uu Interface
1094 6.1.1.1 SIB19
1095 The IE to be set by the feature are tagged “->to be set”.
1096
1097 6.1.1.1.1 System Information Block type 19
1098 Extract of [R1] 10.2.48.8.22
1099 The system information block type 19 contains Inter-RAT frequency and priority information to be
1100 used in the cell.
Information Element/Group Need Multi Type and Semantics Version
name reference description
UTRA priority info list MP UTRA REL-8
-> to be set see 6.1.1.1.2 priority info
list
10.3.7.113
GSM priority info list OP GSM priority REL-8
-> TBC see 6.1.1.1.3 . Not used info list
in UA07.1.2. 10.3.7.114
E-UTRA frequency and priority OP E-UTRA REL-8
info list frequency
-> to be set see 6.1.1.1.5 and priority
info list
10.3.7.115
1101
1102
1103
1104 6.1.1.1.2 Utra priority info list IE
1105 Extract of [R1] 10.3.7.113
1106
1107 Contains priority based reselection information for UTRA.

UTRA Serving Cell MP REL-8
>priority MP Integer 0 is the lowest REL-8
-> to be set (0..<maxPrio priority and
–1>) maxPrio-1 is the
highest
>Sprioritysearch1 MP Integer dB REL-8
-> to be set (0..62 by
step of 2)
>Sprioritysearch2 MD Integer (0..7 dB, default value REL-8
-> to be set by step of 1) is 0
>Threshserving,low MP Integer RSCP, dB REL-8
-> to be set (0..62 by
step of 2)
UTRAN FDD Frequencies OP 1 to < REL-8
-> not used in UA07.1.2. maxNumF
DDFreqs>
>UARFCN MP Integer(0..16 REL-8
-> TBC not used in UA07.1.2. 383)
-> not used in UA07.1.2. (0..<maxPrio priority and
highest.
>Threshx, high MP Integer RSCP, dB REL-8
-> not used in UA07.1.2. (0..62 by
step of 2)
>Threshx, low MP Integer RSCP, dB REL-8
-> not used in UA07.1.2. (0..62 by
step of 2)
>QqualminFDD MD Integer (- Ec/N0, [dB] REL-8
-> not used in UA07.1.2. 24..0) Default value is
Qqualmin for the
serving cell
>QrxlevminFDD MD Integer (- RSCP, [dBm] REL-8
-> not used in UA07.1.2. 119..-25 by Default value is
step of 2) Qrxlevmin for the
serving cell
UTRAN TDD Frequencies OP 1 to < REL-8
-> not used maxNumT
DDFreqs>
>UARFCN MP Integer(0..16 REL-8
-> not used 383)
-> not used (0..<maxPrio priority and
highest.
>Threshx, high MP Integer RSCP, dB REL-8
-> not used (0..62 by
step of 2)
>Threshx, low MP Integer RSCP, dB REL-8
-> not used (0..62 by
step of 2)
>QrxlevminTDD MD Integer (- RSCP, [dBm] REL-8
-> not used 119..-25 by Default value is
step of 2) Qrxlevmin for the
serving cell

1108
1109 NOTE: The network should ensure that priorities for different Radio Access Technologies are always
1110 different.
1111
1112 6.1.1.1.3 Gsm priority info list IE
1113
1114 The support of this IE has to be confirmed see 5.2.3.11: this IE is not used in UA07.1.2.
1115
1116 Extract of [R1] 10.3.7.114
1117
1118 Contains priority based reselection information for GSM.
GSM Priority Info MP 1 to REL-8
-> not used in UA07.1.2. <maxNum
GSMCellG
roup>
>GSM cell group List MP GSM cell REL-8
-> not used in UA07.1.2. group
10.3.7.9a
-> not used in UA07.1.2. (0..<maxPrio priority and
highest.
>QrxlevminGSM MP Integer (- GSM RSSI, [dBm] REL-8
-> TBC not used in UA07.1.2. 115..-25 by
step of 2)
>Threshx, high MP Integer GSM RSSI, dB REL-8
-> not used in UA07.1.2. (0..62 by
step of 2)
>Threshx, low MP Integer GSM RSSI, dB REL-8
-> not used in UA07.1.2. (0..62 by
step of 2)
1119
1121 different.
1122
1123 6.1.1.1.4 Gsm cell group IE
1124
1125 The support of this IE has to be confirmed see 5.2.3.11: this IE is not used in UA07.1.2.
1126
1127
1128 Extract of [R1] 10.3.7.9A

1129
1130 This IE encodes a list of GSM cells specified by their ARFCN values [45].
Starting ARFCN MP Integer First ARFCN REL-8
(0..1023) value in the set
Band Indicator MP Enumerated GSM REL-8
(dcs1800, BAND_INDICATO
pcs1900) R [45]
CHOICE Following ARFCNs MP REL-8
>Explicit list REL-8
>>List of ARFCNs MP 0 to 31 Integer Following ARFCN REL-8
(0..1023) values
>Equally spaced REL-8
>>ARFCN spacing MP Integer (1..8) Increment "d" REL-8
ARFCN values
>>Number of following ARFCNs MP Integer Number "n" of REL-8
(0..31) following ARFCN
values, NOTE 1
>Variable bitmap format REL-8
>>Bitmap MP Octet string NOTE 2 REL-8
(1..16)
>Continuous range REL-8
>>Ending ARFCN MP Integer
Last ARFCN REL-8
(0..1023)
value in the set,
NOTE 3
NOTE 1: Let the IE "Starting ARFCN" = s. The complete set of (n+1) ARFCN values is defined as: {s, ((s + d)
mod 1024), ((s + 2*d) mod 1024) ... ((s + n*d) mod 1024)}.
NOTE 2: Bitmap representing the following ARFCN values in the set. Let the IE "Starting ARFCN" = s. The
first bit of the first octet in the bitmap corresponds to ARFCN = ((s + 1) mod 1024), the next bit to the
ARFCN = ((s + 2) mod 1024), and so on. If the bitmap consist of N octets, the last bit of octet N
corresponds to ARFCN = ((s + 8*N) mod 1024). The complete set of ARFCN values consists of
ARFCN = s and the ARFCN values, where the corresponding bit in the bitmap is set to "1".
NOTE 3: Let the IEs "Starting ARFCN" = s and "Ending ARFCN" = t. The complete set of ARFCN values is
defined as: {s, ((s + 1) mod 1024), ((s + 2) mod 1024) ... ((t − 1) mod 1024), t}.
1131
1132
1133

1134 6.1.1.1.5 E-UTRA Frequency and priority info list IE
1135 Extract of [R1] 10.3.7.115
1136 Contains information about neighbour E-UTRA frequencies (with associated blacklists), together
1137 with priority based reselection information.

E-UTRA frequency and priority 1 to REL-8
<maxNum
EUTRAFre
qs>
>EARFCN MP Integer(0..65 EARFCN of the REL-8
->to be set 535) downlink carrier
frequency
[36.101]
>Measurement Bandwidth MD Enumerated( Measurement REL-8
->to be set 6, 15, 25, 50, bandwidth
75, 100) information
common for all
neighbouring cells
on the carrier
frequency. It is
defined by the
parameter
Transmission
Bandwidth
Configuration, NRB
[36.104]. The
values indicate
the number of
resource blocks
over which the UE
could measure.
Default value is 6.
->to be set (0..<maxPrio priority and
highest.
>QrxlevminEUTRA MP Integer (- RSRP, [dBm] REL-8
->to be set 140..-44 by
step of 2)
>Threshx, high MP Integer RSRP, dB REL-8
->to be set (0..62 by
step of 2)
>Threshx, low MP Integer RSRP, dB REL-8
->to be set (0..62 by
step of 2)
>Blacklisted cells per freq list OP 1 to REL-8
->to be set ? not used in <maxEUT
UA07.1.2. RACellPer
Freq>
>>Physical Cell identity MP Integer A list of blacklisted REL-8
->to be set ? not used in (0..503) cells can be
UA07.1.2. signalled per
frequency
>E-UTRA detection MP Boolean ‘TRUE’ means REL-8
->to be set that the UE may
detect the
presence of a E-
UTRA cell and
report to NAS
1138

1140 different.
1141 maxNumEUTRAFreqs=8. In UA07.1.2, the number of E-UTRA frequencies will be limited to 2.

1142
1143 maxPrio=8
1144
1145 Extract of [R1] section 8.6.2.5:
1146 If the IE "E-UTRA detection" is included in a received message and set to TRUE and the UE is in
1147 CELL_PCH, URA_PCH state or idle mode, the UE may detect the presence of a E-UTRA cell on a
1148 frequency with a priority lower than the current UTRA cell and report the information to the
1149 NAS.
1150

1151 6.1.1.2 SIB scheduling
1152 6.1.1.2.1 Master information block IE
1153
1154 Extract of [R1] 10.2.48.8.1.
Information Element/Group Need Multi Type and Semantics description Version
name reference
Other information elements
MIB Value tag MP MIB Value
-> to be set tag 10.3.8.9
CN information elements
Supported PLMN types MP PLMN Type
-> to be set 10.3.1.12
PLMN Identity CV-GSM PLMN
-> to be set if needed Identity
10.3.1.11
Multiple PLMN List OP Multiple If present, this IE specifies the REL-6
->used PLMN List PLMNs of the cell. If absent,
10.3.1.7a the IE “PLMN Identity”
specifies the PLMN of the cell.
ANSI-41 information elements
ANSI-41 Core Network CV-ANSI- ANSI-41
Information 41 Core
->not used Network
Information
10.3.9.1
References to other system MP References
information blocks and to other
scheduling blocks system
-> to be set information
see 6.1.1.2.2 blocks and
scheduling
blocks
10.3.8.14
CSG Indicator OP Enumerated If present, the cell is a CSG REL-8
->not used (TRUE) cell (see [4]). Default value is
“FALSE” [to be covered in 4]
1155
Condition Explanation
GSM The IE is mandatory present if the IE "Supported
PLMN Types" is set to 'GSM-MAP' or 'GSM-MAP
AND ANSI-41', and not needed otherwise
ANSI-41 The IE is mandatory present if the IE "Supported
PLMN Types" is set to 'ANSI-41' or 'GSM-MAP AND
ANSI-41', and not needed otherwise
1156
1157
1158 6.1.1.2.2 References to other system information blocks and scheduling blocks IE
1159
1160 Extract of [R1] 10.3.8.14.

Information element/Group Need Multi Type and Semantics Version
References to other system MP 1 to System
information blocks <maxSIB> information blocks
-> to be used for which multiple
occurrences are
used, may appear
more than once in
this list
>Scheduling information MP Scheduling
-> to be used information,
10.3.8.16
>SIB and SB type MP SIB and SB
-> to be used (SIB or SB1) Type,
10.3.8.18a
References to other extension OP 1 to System REL-6
system information blocks <maxSIB> information blocks
->not used for which multiple
occurrences are
used, may appear
more than once in
this list
>Scheduling information MP Scheduling REL-6
->not used information,
10.3.8.16
>Extension SIB type MP SIB type REL-6
->not used extension
10.3.8.18b
system information blocks2 <maxSIB> information blocks
->to be set if SB1 not needed for which multiple
occurrences are
used, may appear
more than once in
this list
->to be set if SB1 not needed information,
10.3.8.16
->to be set if SB1 not needed extension2
See 6.1.1.2.5 10.3.8.18c
References to GANSS system OP 1 to REL-8
information blocks <maxGAN
-> not used SS>
>GANSS ID OP Integer (0..7) Absence of this IE REL-8
-> not used means Galileo.
Coded as defined
in NOTE 1 of
10.3.7.90b
>SBAS ID CV- UE REL-8
-> not used GANSS- positioning
ID-SBAS GANSS
SBAS ID
10.3.7.97e
>GANSS system information MP 1 to System REL-8
blocks scheduling <maxSIB> information blocks
-> not used for which multiple

occurrences are
used, may appear
more than once in
this list
>>Scheduling information MP Scheduling REL-8
-> not used information,
10.3.8.16
>>GANSS SIB type MP GANSS SIB REL-8
-> not used type
10.3.8.18d
1161
GANSS-ID-SBAS This IE is mandatory present if the IE “GANSS ID” is
“SBAS”, and not needed otherwise.
1162
1163
1164 6.1.1.2.3 Scheduling block 1
1165
1166 Extract of [R1] 10.2.48.8.2.
1167
Information Element/Group Need Multi Type and Semantics description
name reference
References to other system MP References
information blocks to other
->to be set system
See 6.1.1.2.4 information
blocks
10.3.8.13
1168
1169
1170
1171 6.1.1.2.4 References to other system information blocks IE
1172
1173 Extract of [R1] 10.3.8.13.
1174

Information element/Group Need Multi Type and Semantics Version
References to other system MP 1 to System
information blocks <maxSIB> information blocks
-> to be set (if SB1 used) for which multiple
occurrences are
used, may appear
more than once in
this list
>Scheduling information MP Scheduling
-> to be set (if SB1 used) information,
10.3.8.16
>SIB type SIBs only MP SIB Type
-> to be set (if SB1 used) SIBs only,
10.3.8.22
system information blocks <maxSIB> information blocks
-> not used for which multiple
occurrences are
used, may appear
more than once in
this list
-> not used information,
10.3.8.16
-> not used extension
10.3.8.18b
system information blocks2 <maxSIB> information blocks
-> to be set (if SB1 used) for which multiple
occurrences are
used, may appear
more than once in
this list
-> to be set (if SB1 used) information,
10.3.8.16
-> to be set (if SB1 used) extension2
See 6.1.1.2.5 10.3.8.18c
References to GANSS system OP 1 to REL-8
information blocks <maxGAN
->not used SS>
>GANSS ID OP Integer (0..7) Absence of this IE REL-8
->not used means Galileo.
Coded as defined
in NOTE 1 of
10.3.7.90b
>SBAS ID CV- UE REL-8
->not used GANSS- positioning
ID-SBAS GANSS
SBAS ID
10.3.7.97e
>GANSS system information MP 1 to System REL-8
blocks scheduling <maxSIB> information blocks
->not used for which multiple

occurrences are
used, may appear
more than once in
this list
>>Scheduling information MP Scheduling REL-8
->not used information,
10.3.8.16
>>GANSS SIB type MP GANSS SIB REL-8
->not used type
10.3.8.18d
1175
GANSS-ID-SBAS This IE is mandatory present if the IE “GANSS ID” is
“SBAS”, and not needed otherwise.
1176
1177
1178
1179 6.1.1.2.5 SIB type extension2 IE
1180
1181 Extract of [R1] 10.3.8.18C.
1182
1183 The SIB type identifies a specific extension system information block.
SIB type extension2 MP Enumerated, Five spare values REL-8
->to be set see below are needed
1184
List of enumerated values Version
System Information Type 19 REL-8
System Information Type 15.2ter
System Information Type 20
1185
1186
1187
1188

1189 6.1.2 Iu Interface
1190 No impact.

1191 6.1.3 Iur Interface
1192
1193 No impact.

1194 6.1.4 Iub Interface
1195 - SIB19 to be put in System information update message.
1196 The content of the NBAP messages is reminded. When SIB19 is used, it has to be indicated in
1197 the NBAP message.
1198
1199 6.1.4.1 System information update request message
1200 Extract of [R3] section 9.1.33
1201
IE/Group Name Presence Range IE Type Semantics Criticality Assigned
and Description Criticality
Reference
Message Discriminator M 9.2.1.45 –
Message Type M 9.2.1.46 YES reject
Transaction ID M 9.2.1.62 –
C-ID M 9.2.1.9 YES reject
BCCH Modification Time O 9.2.1.3 YES reject
MIB/SB/SIBInformation 1..<maxIB GLOBAL reject
>
>IB Type M 9.2.1.35 –
>IB OC ID M 9.2.1.31A In one _
message, every
occurrence of
IB Type can
only be deleted
once and/or
added once.
>CHOICE IB Deletion M _
Indicator
>>No Deletion
>>>SIB Originator C-SIB 9.2.1.55 –
>>>IB SG REP O 9.2.1.34 –
>>>Segment 1..<maxIB GLOBAL reject
Information SEG>
>>>>IB SG POS O 9.2.1.33 –
>>>>Segment Type C- 9.2.1.53B –
CRNCOrig
ination
>>>>IB SG DATA C- 9.2.1.32 –
CRNCOrig
ination
>>Deletion set ->to be set NULL
for all SIB already present
in the previous scheduling
1202

Range bound Explanation
maxIB Maximum number of information Blocks supported in one message
maxIBSEG Maximum number of segments for one Information Block
1203
CRNCOrigination The IE shall be present if the SIB Originator IE is set to "CRNC" or if the
IB Type IE is set to "MIB", "SB1" or "SB2".
SIB The IE shall be present if the IB Type IE is set to "SIB".
1204
1205 maxIBSEG:= 16
1206 maxIB= 64
1207
1208 6.1.4.2 System information update response message
1210
1211
Reference
Criticality Diagnostics O 9.2.1.17 YES ignore
1212
1213
1214 6.1.4.3 System information update failure message
1216
Reference
Cause M 9.2.1.6 YES ignore
Criticality Diagnostics O 9.2.1.17 YES ignore
1217
1218
1219 6.1.4.4 IB type IE
1220 Extract of [R3] section 9.2.1.35
1221

1222 The IB Type identifies a specific system information block.
IE/Group Name Presence Range IE Type and Semantics Description
Reference
IB Type ENUMERATED (
MIB,
SB1,
SB2,
SIB1,
SIB2,
SIB3,
SIB4,
SIB5,
SIB6,
SIB7,
not-Used-SIB8,
not-Used-SIB9,
not-Used-SIB10,
SIB11,
SIB12,
SIB13,
SIB13.1,
SIB13.2,
SIB13.3,
SIB13.4,
SIB14,
SIB15,
SIB15.1,
SIB15.2,
SIB15.3,
SIB16,
…,
SIB17,
SIB15.4,
SIB18,
SIB15.5,
SIB5bis,
SIB11bis,
SIB15bis,
SIB15.1bis,
SIB15.2bis,
SIB15.3bis,
SIB15.6,
SIB15.7,
SIB15.8,
SIB15.2ter,
SIB19)
1223
1224
1225
1226

1227 6.2 OAM INTERFACES

1228 6.2.1 3GPP OAM INTERFACES
1229 Interface btw LTE OMC and UMTS OMC for LTE frequencies exchange.
1230
1231 6.2.2 External ALU OAM Interfaces
1232 Open item: Are LTE frequencies communicated by LTE OAM to UTRAN OAM ?
1233
1234 6.3 TRANSMISSION NETWORK INTERFACES

1235 6.3.1 Physical Layer
1236 6.3.2 No impact.Ethernet
1237 No impact.
1238 6.3.3 ATM
1239 No impact.
1240 6.3.4 IP
1241 No impact.

1242 7 OAM MODEL DESCRIPTION

1243 <Guide>This chapter describes any changes or updates to the information models, note the
1244 data format shown is yet to be finalised.</Guide>
1245 7.1 CONFIGURATION MANAGEMENT

1246 <Guide>Description of the new or modified (or deleted) configuration objects / parameters.
1247 /Guide>
1248 7.1.1 CM Parameters
1249 <Guide>Generic CM parameter example is included below. This should define how parameters
1250 are to be added or adjusted and the parameter fully defined in the appropriate parameter
1251 modelling database.</Guide>
1252
1253 7.1.1.1 Spare parameters available in UA07.1.2
1254
1255 See document [A5] to get a global view of spares used by features 104489, 81436 and 81213.
1256
1257 7.1.1.2 CM in UA07.1.2
1258 No model modification can be done in UA07.1.2: reserved parameters have to be used.
1259 Even if all reserved parameters were created as “required” parameters, the presence of each
1260 feature parameter is indicated in a functional scope.
1261 Bit 0 is the LSB of a byte.
1262
1263 SIB19 activation:
1264 A parameter is needed to allow SIB 19 activation in the RNC for upgrade and feature
1265 introduction reason.
1266 Parameter: isSib19Allowed;
1267 Definition: Allows SIB 19 activation.
1268 Type: Boolean (True/false);
1269 Class: 3A-1
1270 Presence: Required
1271 MO: RadioAccessService -> to be created among reserved 0..7 parameters
1272 RadioAccessService.reserved3 (all bytes)
1273
1274
1275
1276 SIB19 activation:

1277 Parameter: sib19Enable;
1278 Definition: Allows the RNC to configure the SIB19 in the Fdd cell.
1279 Type: Boolean (True/false); /*default = false */-> may be coded in one bit
1280 Class: 3A-1
1281 Presence: required.
1282 MO: FddCell -> to be created among reserved 0..7 parameters
1283 FDDCell.reserved4(byte0) bit 3
1284
1285 SIB19 parameters: UTRA serving cell information
1286 Parameter: utraServingCellPriority;
1287 Definition: Absolute priority of the serving Fdd cell set in SIB19.
1288 Type: integer [0..7]; -> may be coded in three bits
1289 Class: 3A-1
1290 Presence: Required if SIB19 feature is activated.
1292 FddCell.reserved4(byte0) bit 0-2
1293
1294 Parameter: utraSPrioritySearch1;
1295 Definition: Srxlev of the UTRA cell used for neighboring measurement triggering. This
1296 information is set in SIB19.
1297 Type: integer (0..62 by step of 2); -> may be coded in six bits
1298 Unit: dB.
1299 Class: 3A-1
1303
1304 Parameter: utraSPrioritySearch2;
1305 Definition: Squal of the UTRA cell used for neighboring measurement triggering. This
1306 information is set in SIB19.
1307 Type: integer (0..7 by step of 1); -> may be coded in six bits.
1308 Unit: dB.
1309 Class: 3A-1

1313
1314 Parameter: utranThreshSLow;
1315 Definition: RSCP threshold Low of the UTRA cell used by the UE reselection process.
1316 This information is set in SIB19.
1317 Type: integer (0..62 by step of 2); may be coded in six bits
1318 Unit: dB.
1319 Class: 3A-1
1321 MO: FddCell-> to be created among reserved 0..7 parameters
1323
1324
1325 SIB19 parameters: E-UTRA frequencies information
1326 The following parameters are defined per E-UTRA frequency. 3GPP defines 8 priorities.
1327
1328 Open item: waiting from LTE SAE feedback if a lower dimensioning is allowed. Yes 2.
1329
1330 Parameter: eUtraTargetDlCarrierFrequencyList is a table restricted to 2 instances (instead of
1331 8) for spare availability reason. Each instance has several parameters. The description of both
1332 instances is given below.
1333
1334 Instance [0]:
1335 Parameter: eUtraTargetDlCarrierFrequencyArfcn[0]
1336 Definition: List of E-UTRA frequencies to be used in cell reselection procedure.
1337 Type: Integer (0..65535) -> may be coded in two bytes.
1338 Class: 3A-1
1340 MO: FddCell ->
1341 FddCell.reserved5 (byte0 and 1)
1342
1343
1344 Parameter: eUtraTargetFreqencyMeasurementBandwidth[0];
1345 Definition: Measurement bandwidth information used by SIB19 and common for all
1346 neighbouring cells on the carrier frequency.
1347 Type: Enumerated (6,15,25,50,75,100); -> may be coded in three bits.

1348
1349 Class: 3A-1
1350 Presence: Required if LTE frequency[0] created.
1352 FddCell.reserved5 (byte2) bit 0-2
1353
1354
1355 Parameter: eUtraTargetFrequencyPriority[0];
1356 Definition: set a priority of a E-UTRA frequency in SIB19
1357 Type: byte [0..7]; -> may be coded in three bits.
1358 Class: 3A-1
1362
1363 Parameter: eUtraTargetFrequencyQrxlevmin[0];
1364 Definition: Qrxlevmin (RSRQ) of the E-UTRA cell used for S criteria of the reselection
1365 process. This information is set in SIB19.
1366 Type: integer (-140..-44 by step of 2); -> may be coded in six bits.
1367 Unit: dBm
1368 Class: 3A-1
1372
1373 Parameter: eUtraTargetFrequencyThreshxHigh[0];
1374 Definition: RxLev (RSRP) Threshold High of the E-UTRA cell used by the UE reselection
1377 Unit: dB
1378 Class: 3A-1
1382

1383 Parameter: eUtraTargetFrequencyThreshxLow[0];
1384 Definition: RxLev (RSRP) Threshold Low of the E-UTRA cell used by the UE reselection
1387 Unit: dBm
1388 Class: 3A-1
1392
1393 Parameter: eUtraTargetFrequencyDetection[0];
1394 Definition: ‘TRUE’ means that the UE may detect the presence of a E-UTRA cell and
1395 report to NAS. This information is set in SIB19.
1396 Type: boolean; -> may be coded in one bit.
1397 Class: 3A-1
1400 FddCell.reserved5 (byte2) bit 6
1401
1402 Parameter: eUtraTargetFrequencyBlacklistedCells;
1403 Open item: Not supported in UA07.1.2:
1404
1405 Instance [1]:
1406 Parameter: eUtraTargetDlCarrierFrequencyArfcn[1]
1407 Definition: List of E-UTRA frequencies to be used in cell reselection procedure.
1408 Type: Integer (0..65535) -> may be coded in two bytes
1409 Class: 3A-1
1410 Presence: Optional.
1411 MO: FddCell ->
1412 FddCell.reserved6 (byte0 and 1)
1413
1414
1415 Parameter: eUtraTargetFrequencyMeasurementBandwidth[1];
1416 Definition: Measurement bandwidth information used by SIB19 and common for all
1417 neighbouring cells on the carrier frequency.

1418 Type: Enumerated (6,15,25,50,75,100). -> may be coded in three bits
1419 In case the three bits are set to 1, instance[1] is not significant.
1420 Class: 3A-1.
1424
1425
1426 Parameter: eUtraTargetFrequencyPriority[1];
1427 Definition: set a priority of a E-UTRA frequency in SIB19
1428 Type: integer [0..7]. -> may be coded in three bits
1429 Class: 3A-1.
1433
1434 Parameter: eUtraTargetFrequencyQrxlevmin[1];
1435 Definition: Qrxlevmin (RSRQ) of the E-UTRA cell used for S criteria of the reselection
1437 Type: integer (-140..-44 by step of 2); -> may be coded in six bits
1438 Unit: dBm
1439 Class: 3A-1.
1440 Presence: Required if LTE frequency[1] created. MO: FddCell -> to be created among
1441 reserved 0..7 parameters
1443
1444 Parameter: eUtraTargetFrequencyThreshxHigh[1];
1445 Definition: RxLev (RSRP) Threshold High of the E-UTRA cell used by the UE reselection
1447 Type: integer (0..62 by step of 2). -> may be coded in six bits
1448 Unit: dB
1449 Class: 3A-1.

1453
1454 Parameter: eUtraTargetFrequencyThreshxLow[1];
1455 Definition: RxLev (RSRP) Threshold Low of the E-UTRA cell used by the UE reselection
1457 Type: integer (0..62 by step of 2). -> may be coded in six bits
1458 Unit: dB
1459 Class: 3A-1.
1463
1464 Parameter: eUtraTargetFrequencyDetection[1];
1465 Definition: ‘TRUE’ means that the UE may detect the presence of a E-UTRA cell and
1466 report to NAS. This information is set in SIB19.
1467 Type: Boolean (true,false). -> may be coded in one bit
1468 Class: 3A-1
1471 FddCell.reserved6 (byte2) bit 6
1472
1473 Parameter: eUtraTargetFrequencyBlacklistedCells;
1474 Open item: Not supported in UA07.1.2:
1475
1476

sib19Enable utraServingCellPriority
FddCell 81436 (proposed by Scott)
utraThreshSLow utraSPrioritySearch2 utraSPrioritySearch1
reserved4
byte3 byte2 byte1 byte0

measurementBandwidth[0]
priority[0]
detection[0] arfcn[0]
qRxLevMin[1]
qRxLevMin[0]
reserved5
measurementBandwidth[1]
priority[1]
detection[1] arfcn[1]
qRxLevMin[1]
reserved6
threshXHigh[1] threshXLow[1] threshXHigh[0] threshXLow[0]
reserved7
1477
1478
1479 color coding : white=un-used, non-white=occupied
1480
1481 Parameter: isDynamicSibAlgoWithSbAllowed
1482 Definition : This parameter activate/deactivate the use of SB block in the dynamic SIB
1483 scheduling algorithm used to broadcast SIB on the Air interface. It has to be set to true
1484 in order to broadcast SIB4 and SIB12.
1485
1486 The definition shall be updated to add SIB19.
1487
1488
1490 Parameter Name:
1491 Parameter Location:
1492 Status: New/Modified

1493 Change Summary:
1494
1495
1497 Review Status:
1500
1501
1502 7.1.1.2.1 Others
1503 Tbd
1504
1505 7.1.1.3 CM in UA08
1506 Spare parameters have to be replaced by dedicated parameters.
1507 As for GSM neighboring provisioning a conf class may be created to gather LTE frequencies. The
1508 thresholds parameters may be defined in a sub MO (LteNeighbourinFrequencies) of FddCell MO.
1509 It has to be confirmed during UA08 studies.
1510 7.1.2 Control Rules
1511 7.1.2.1 UA07.1.2
1512 As spare parameters are used all parameter are defined in the model as “required parameters”
1513 but no value range may be verified by the model itself.
1514 As most of the parameters values may be set by 0 (value allowed in the range), there is no
1515 mean for WIPS to check all parameters setting.
1516 If the parameter sib19Enable is true, the control rules have to be applied by WIPS:
1517 • The priority of the serving FDD frequency has to be different than priorities of the
1518 neighboring E-UTRAN frequencies. E-UTRAN neighboring frequencies of the Fdd serving
1519 cell may have the same priority.
1520 • Flag isDynamicSibAlgoWithSbAllowed is set to TRUE in RadioAccessService
1521 • Flag isSib19Allowed is set to TRUE in RadioAccessService
1522
1523
1524 7.1.2.2 UA08
1525 Dedicated parameters (table and structure) will be created. The presence of each parameter
1526 has to take into account the 3GPP tabular definition. The range of each parameter may be
1527 checked in the Model definition.

1528 7.2 FAULT MANAGEMENT

1529 <Guide>Description of the new or modified (or deleted) alarm notifications</Guide>
1530 7.2.1 Alarms
1531 No impact.
1532 7.2.2 Diagnostics
1533 No impact.
1534 7.2.3 Trouble Shooting
1535 No impact.
1536
1537 7.2.4 Failure Recovery
1538 No impact.

1539 7.3 PERFORMANCE MANAGEMENT

1540 <Guide>Description of the new or modified (or deleted) performance counters</Guide>
1541 7.3.1 Counters
1542 Example Performance Counter is included below.
1543
1545 Counter Id:either NEW or <number> DELETE or <number> in case of modification
1546 3GPP Name: external name used by the customer
1547 Location: Location / Object basis
1548 Type <CUM / VAL / Load>
1549 Meaning, Description: Purpose of the counter (customer view)
1550 Triggering Event: Clear, concise conditions when counter is pegged
1551 Screening Criteria: NONE if no screening applies
1552 Screening x: Description 3GPP name Modification (opt)
1553 to be repeated for each screening
1554 Modification: optional, only in case of modification, type of modification
1555 Notes: optional, e.g.. Impacted KPIs, related counters, non-customer viewable details
1556
1557
1558
1560 Review Status:
1563
1564 No counter.
1565
1566
1567 7.3.2 Metrics
1568 No impact.
1569
1570 7.3.3 Traces
1571 No impact.

1572 8 OAM PROCEDURES

1573 8.1 UPGRADES
1574 <Guide>Mainly focused to compliancy between releases this chapter defines OAM upgrade
1575 routines and methods</Guide>
1576 8.1.1 OAM Platform Upgrade
1577 <Guide>Description of the upgrade constraints.
1578 OAM parameter values</Guide>
1579 No impact.
1580 8.1.2 RNC & BTS Upgrade
1581 <Guide>Description of the upgrade and how performance is maintained over the upgrade
1582 period</Guide>
1583 The feature has to be deactivated at OAM level: SIB19 has not to be set by the RNC and the
1584 NodeB will be not impacted.
1585
1586 8.2 INSTALLATION AND COMMISSIONING PROCEDURES

1587 <Guide>Description of the feature impact on I&C procedures</Guide>
1588 8.3 MAINTENANCE

1589 <Guide>Description of the feature impact on standard maintenance procedures</Guide>
1590 If the System information update procedure fails the SIB19 feature ahs to be deactivated.
1591
1592 8.4 FEATURE ACTIVATION

1593 <Guide>Description of the feature impact on standard operation procedures
1594 General description of the Feature Activation procedures concerning the feature activation
1595 and deactivation mode</Guide>
1596 Feature activation at RNC level (the feature is optional and is eligible to the licensing function)
1597
1598 See section 7.1.1.2.
1599
1600 9 FIELD INTRODUCTION

1601 <Guide>Description of how the feature is introduced into the field</Guide>
1602 The feature may be activated in one cell in order to check the impact on NodeB and UE.
1603

1604 9.1 HARDWARE CONSTRAINTS

1605 <Guide>HW/feature compatibility and degraded mode
1606 HW interworking policy</Guide>
1607 No impact.
1608
1609 9.2 SPARE PARTS CONSTRAINTS

1610 <Guide>Retrofit HW.
1611 Version compatibility matrix.</Guide>
1612 No impact.
1613
1614 9.3 INTER RNS VERSION INTERWORKING

1615 <Guide>UTRAN version interworking policy (for example: criticality)
1616
1617 Feature activation strategy must be well described, in particular partial introduction of a
1618 feature in a live network:</Guide>
1619 The feature is C-RNS feature. There is no impact on inter RNC version.
1620
1621 9.4 CORE NETWORK INTERWORKING

1622 <Guide>UTRAN/CN interworking policy </Guide>
1623 There is no impact.
1624
1625 9.5 BACKWARDS COMPATIBILITIES

1626 <Guide>Backwards compatibility issues and strategy</Guide>
1627 N/A
1628 10 FUTURE EVOLUTION

1629 <Guide> Optional - Describe any possible identified evolution paths for the Feature</Guide>
1630 The restrictions given in section 3.2.3.2 are candidate to be removed in UA08.
1631 The exchange of LTE parameters (frequencies ID) between LTE OAM and UMTS OAM may be
1632 enhanced in U0A8.
1633
1634 11 TOOLS IMPACTS

1635 <Guide>Describe impact of the function on system tools (maintenance, engineering, validation
1636 tools etc)
1637 </Guide>
1638 Uu and IUB are Rel8: ASN1 coding/decoding tools (Catapult, spy…) are impacted in UA07.1.2.
1639

1640 12 FTS REQUIREMENTS COMPLIANCE AND RESTRICTION

1641 TABLE
1642 <Guide>Define the compliancy of the system solution to the Feature Technical Specification,
1643 include notes where restrictions apply to FTS requirements that will not be fully developed. -
1644 Each requirement will have a DR1 answer
1645
1646 - DR1 possible answers: Compliant (C)/ Not Compliant (N)/ Partially Compliant (P)/ N/A (NA)
1647 - Letters in bold (see above) can be used (instead of full word) but in that case a guide has to
1648 be added
1649 - In case the answer is “Not Feasible”, “Not Compliant” or “Partial Compliancy”, a Comment
1650 is mandatory
1651 </Guide>
1652 Empty. See 3.2.3.
1653 12.1 FTS COMPLIANCE NOTES

1654 Empty. See 3.2.3.
1655
Req # Requirement Description RNC NodeB oneBTS OAM Comments
R1
R1.1
R1.2
R5
R8
1656 12.2 RESTRICTIONS

1657 <Guide> Track Restrictions to the FTS compliancy during FTS development </Guide>
1658
1659 Empty. See 3.2.3.
1660
1661
1662 12.3 COMPLIANCY MATRIX UPDATES

1663 <Guide>Track updates to the FTS compliancy after the FTS document has been placed under
1664 change control</Guide>
1665 Empty. See 3.2.3.
1666

1667
1668 13 ABBREVIATIONS AND DEFINITIONS

1669 <Guide> add and remove acronyms as required</Guide>
1670 3GPP 3rd Generation Partnership Project
1671 AKA Authentication and Key Agreement
1672 ALCAP Access Link Control Application Part
1673 ALTP Alcatel-Lucent Technical Publication
1674 DR1 Level of feature maturity allowing a code start (note: not the DR1 for the global program)
1675 FRS Feature Requirement Specification, usually created by PLM and capturing "business level"
1676 requirements.
1677 FTS Feature Technical Specification, technical counterpart of the FRS produced by Systems
1678 Engineering / Design or Feature Architecture Prime
1679 GAN: Generic Access
1680 POS: Position. It is the lowest position of a specific Information Block segment in the SFN cycle
1681 (IB_SG_POS < IB_SG_REP).
1682 RP: Repetition Period. It is the repetition distance for an Information Block segment. The
1683 segment shall be transmitted when SFN mod IB_SG_REP = IB_SG_POS.
1684 RSRP: Reference Signal Received Power
1685 RSRQ: Reference Signal Received Quality
1686
1687
1688 Parameters class definition:
1689 Class 0: the parameter cannot be modified and a new object instance must be created or
1690 recreated with the requested value thanks to build process or on line creation command.
1691
1692 Class 2: the object instance (or the parent object instance) must be locked to modify the
1693 parameter and the modification will be taken into account after the object instance (or the
1694 parent object instance) has been unlocked.
1695
1696 Class 3: the parameter can be changed on-line without impact on the service. The new value is
1697 taken into account either immediately or for new calls only.
1698
1699 Class 3-A1 new value immediately taken into account.
1700 Class 3-A2 new value taken into account upon event reception (service establishment, SRLR, for
1701 instance...).
1702
1703 Class 3-B new value taken into account for next calls.

1704 14 ANNEX
1705 14.1 ANNEX A: FEATURE GROUP INDICATORS
1706 Extract of CR 3698 (RP- 090584).
1707 Annex E (Normative):

1708 EUTRA Feature group indicators
1709 This annex contains the definitions of the bits in EUTRA Feature Group Indicators.
1710 In this release of the specification the UE shall include the optional EUTRA Feature Group Indicators IE in the UE
1711 multi-mode/multi RAT capability IE of the RRC message. For a specific indicator, if all functionalities for a
1712 feature group listed in Table E.1 have been implemented and tested, the UE shall set the indicator as "true" (as
1713 one), else (i.e. if any one of the functionalities in a feature group listed in Table E.1 have not been implemented
1714 or tested), the UE shall set the indicator as "false" (as zero).
1715 The UE shall set all indicators, which do not have a definition in the table E.1, as "false" (as zero).
1716 If the optional EUTRA Feature Group Indicators IE is not included by a UE supporting a future release of the
1717 specification, the network may assume the UE supports all features in the feature groups listed in table E.1 and
1718 deployed in the network.
1719 Table E.1: Defintions of feature group indicators
Index of Definition Notes

indicator (description of the supported functionality, if indicator set to ‘true’)
(bit
number)
1 (leftmost - UTRA CELL_PCH to EUTRA RRC_IDLE cell reselection UEs may indicate support in this release
bit) - UTRA URA_PCH to EUTRA RRC_IDLE cell reselection of the specification.
UEs may indicate support in earlier
releases of the specification.
2 - UTRA IDLE to EUTRA RRC_IDLE cell reselection UEs shall indicate support in this release
- RRC release with redirection procedure of the specification.
- RRC reject with redirection procedure UEs may indicate support in earlier
releases of the specification.
3 - EUTRAN measurements and reporting in connected mode UEs shall indicate support in this release
of the specification.
UEs may indicate support in earlier
releases of the specification
4 Undefined
1720
1721 Clarification for mobility to EUTRAN
1722 For mobility to E-UTRAN, it is assumed that we have 6 main "functions":
1723 A. Support of measurements and cell reselection procedure in idle mode
1724 B. Support of measurements and cell reselection procedure in CELL/URA_PCH
1725 C. Support of RRC release with redirection procedure
1726 D. Support of RRC reject with redirection procedure
1727 E. Support of EUTRAN measurements and reporting in connected mode
1728 F. Support of handover procedure in connected mode


1729 In this release of the specification:
1730 Of the above, all UEs support A), C), D) and E) for all EUTRA bands they support. UEs shall indicate support of
1731 Group 2 and Group 3 (Group 2 and Group 3 are set to “true”).
1732 For B) above, UEs indicate support by Group 1 (if Group 1 is set to “true”, it is supported for all EUTRA bands the
1733 UE supports).
1734 For F) above, UEs indicate support by the separate UE capability signaling “Support of Inter-RAT PS Handover to
1735 E-UTRA FDD/TDD” defined in TS 25.306 (if this bit is set to “true”, PS handover is supported for all EUTRA bands
1736 the UE supports).
1737
1738 14.2 ANNEX B: UE VARIABLES

1739 Extract of [R1] 10.3.4.15C
1740 PRIORITY_INFO_LIST
1741 This variable contains cell information on UTRA and inter-RAT priorities to be applied to neighbour
1742 cells stored in CELL_INFO_LIST and EUTRA_FREQUENCY_INFO_LIST, as received in messages System
1743 Information Block Type 19 and UTRAN MOBILITY INFORMATION.
1744 The contents of this variable are inherited at inter-RAT cell (re)selection, including the remaining
1745 validity time (i.e., T320 in E-UTRAN, T322 in UTRAN, and [T3230, FFS] in GERAN), if configured.
1746 This variable can be configured in CELL_DCH, CELL_FACH, CELL_PCH, URA_PCH and Idle states.
1747 However, it is only used in CELL_FACH, CELL_PCH, URA_PCH and Idle states.

Information Need Multi Type and Semantics Version
Element/Group name reference description
Priority status MP Enumerated REL-8
(sys_info_priori
ty,
dedicated_prior
ity)
UTRA Serving Cell OP REL-8
>priority OP Integer Absence of this REL-8
(0..<maxPrio– IE indicates
1>) that the lowest
priority is
assigned to the
serving
frequency
(lower than any
assigned
priority)
>Sprioritysearch1 MP Integer (0..62 RSCP, dB REL-8
by step of 2)
>Sprioritysearch2 MD Integer (0..7 by dB, default REL-8
step of 1) value is 0
>Threshserving,low MP Integer (0..62 RSCP, dB REL-8
by step of 2)
Priority Info List OP 1 to REL-8
<maxNumPrio>
>priority OP Integer Absence of this REL-8
(0..<maxPrio– IE indicates
1>) that no priority
is assigned to
the indicated
frequencies
>CHOICE Radio Access MP REL-8
Technology
>>UTRA FDD REL-8
>>>Frequency List 1 to
<maxNumFDD
Freqs>
>>>>UARFCN MP Integer (0.. REL-8
16383)
>>>>QqualminFDD MD Integer (-24..0) Ec/N0, [dB] REL-8
Default value is
-24.
>>>>QrxlevminFDD MD Integer (-119..- RSCP, dBm REL-8

25 by step of 2) Default value is
-119.
>>>>Threshx, high OP Integer (0..62 RSCP, dB REL-8

by step of 2)
>>>>Threshx, low OP Integer (0..62 RSCP, dB REL-8
by step of 2)
>>UTRA TDD REL-8
<maxNumTDD
Freqs>
>>>>UARFCN MP Integer (0.. REL-8

16383)
>>>>QrxlevminTDD MD Integer (-119..- RSCP, dBm REL-8
-119.
>>>>Threshx, high OP Integer (0..62 RSCP, dB REL-8

by step of 2)
>>>>Threshx, low OP Integer (0..62 RSCP, dB REL-8
by step of 2)
>>E-UTRA REL-8
<maxNumEUT
RAFreqs>
>>>>EARFCN MP Integer(0 .. EARFCN of the REL-8
65535) downlink
carrier
frequency
[36.101]
>>>>QrxlevminEUTRA MD Integer (-140..- RSRP, dBm REL-8
-140.
>>>> Threshx, high OP Integer (0..62 RSRP, dB REL-8

by step of 2)
>>>>Threshx, low OP Integer (0..62 RSRP, dB REL-8
by step of 2)
>>GSM REL-8
>>>NCC permitted MD Bit string (8) Bitmap
{NCC 0 to 7} indicating NCC
values;
reselection of
GERAN cells is
permitted when
the
corresponding
NCC bit = "1".
Default is
“11111111”
>>>Frequency List MP 1 to < REL-8
maxCellMeas>
>>>>Band indicator MP Enumerated Indicates how REL-8
(DCS 1800 to interpret the
band used, BCCH ARFCN
PCS 1900
band used)
>>>>BCCH ARFCN MP Integer [45] REL-8
(0..1023)
>>>>QrxlevminGSM MD Integer (-115..- GSM RSSI, REL-8
56 by step of 2) dBm
Default value is
-115.
>>>>Threshx, high OP Integer (0..62 GSM RSSI, dB REL-8

by step of 2)
>>>>Threshx, low OP Integer (0..62 GSM RSSI, dB REL-8
by step of 2)
E-UTRA detection OP Boolean ‘TRUE’ means REL-8

that the UE
may detect the
presence of a
E-UTRA cell
and report to
NAS
1748

FTS - 81436 - Mobility Between UMTS and LTE - Reselection - v01.06

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FTS - 81436 - Mobility Between UMTS and LTE - Reselection - v01.06

Uploaded by

Copyright:

Available Formats

1

3 FTS 81436 - Mobility between UMTS and LTE - Cell

13 Copyright 2007-2009 Alcatel-Lucent, All Rights Reserved

39 3 FEATURE OVERVIEW ..........................................................................................12

53 5 FEATURE DEFINITION .........................................................................................20

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 2 of 84

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 3 of 84

107 6 INTERFACE REQUIREMENTS..................................................................................45

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 4 of 84

137 7 OAM MODEL DESCRIPTION ...................................................................................64

156 8 OAM PROCEDURES .............................................................................................75

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 5 of 84

163 9 FIELD INTRODUCTION .........................................................................................75

169 10 FUTURE EVOLUTION ..........................................................................................76

170 11 TOOLS IMPACTS ................................................................................................76

171 12 FTS REQUIREMENTS COMPLIANCE AND RESTRICTION TABLE..........................................78

175 13 ABBREVIATIONS AND DEFINITIONS .........................................................................79

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 6 of 84

182 Publication History

20/10/2009 Updated with: 01.02/EN Update P.Moquet

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 7 of 84

25/02/10 Set Status to Approved_Standard 01/05/EN Update R.Baron

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 8 of 84

208 1.1 OBJECT

215 1.2 SCOPE OF THIS DOCUMENT

220 1.3 AUDIENCE FOR THIS DOCUMENT

222 1.4 STATUS

223 1.5 WAIVERS AND EXCEPTIONS

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 9 of 84

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 10 of 84

225 2 RELATED DOCUMENTATION

246 2.2 REFERENCE DOCUMENTS

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 11 of 84

261 3 FEATURE OVERVIEW

269 3.1 OVERVIEW

Alcatel-Lucent Technologies – Proprietar y

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 12 of 84

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 13 of 84

294 3.2 FRS ANALYSIS

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 14 of 84

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 15 of 84

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 16 of 84

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 17 of 84

352 3.3 OPEN ISSUES

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

UMT/SYS/APR/028777 01.06 / EN Approved_Standard 27/May/2010 Page 18 of 84

372 4 FEATURE BENEFITS