3GPP TS 25.433 V13.3.0 (2016-06)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
UTRAN Iub interface Node B Application Part (NBAP) signalling
(Release 13)



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




Keywords
UMTS, radio, access

3GPP
Postal address

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

Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.

UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association

Contents
Foreword	25
1	Scope	26
2	References	26
3	Definitions, Symbols and Abbreviations	28
3.1	Definitions	28
3.2	Symbols	28
3.3	Abbreviations	29
4	General	30
4.1	Procedure Specification Principles	30
4.2	Forwards and Backwards Compatibility	31
4.3	Specification Notations	31
5	NBAP Services	32
5.1	Parallel Transactions	32
6	Services Expected from Signalling Transport	32
7	Functions of NBAP	32
8	NBAP Procedures	35
8.1	Elementary Procedures	35
8.2	NBAP Common Procedures	37
8.2.1	Common Transport Channel Setup	37
8.2.1.1	General	37
8.2.1.2	Successful Operation	38
8.2.1.3	Unsuccessful Operation	41
8.2.1.4	Abnormal Conditions	42
8.2.2	Common Transport Channel Reconfiguration	43
8.2.2.1	General	43
8.2.2.2	Successful Operation	43
8.2.2.3	Unsuccessful Operation	45
8.2.2.4	Abnormal Conditions	46
8.2.3	Common Transport Channel Deletion	46
8.2.3.1	General	46
8.2.3.2	Successful Operation	46
8.2.3.3	Unsuccessful Operation	47
8.2.3.4	Abnormal Conditions	47
8.2.4	Block Resource	47
8.2.4.1	General	47
8.2.4.2	Successful Operation	47
8.2.4.3	Unsuccessful Operation	48
8.2.4.4	Abnormal Conditions	49
8.2.5	Unblock Resource	49
8.2.5.1	General	49
8.2.5.2	Successful Operation	49
8.2.5.3	Abnormal Conditions	49
8.2.6	Audit Required	49
8.2.6.1	General	49
8.2.6.2	Successful Operation	50
8.2.6.3	Abnormal Conditions	50
8.2.7	Audit	50
8.2.7.1	General	50
8.2.7.2	Successful Operation	50
8.2.7.3	Unsuccessful Operation	53
8.2.7.4	Abnormal Conditions	53
8.2.8	Common Measurement Initiation	53
8.2.8.1	General	53
8.2.8.2	Successful Operation	53
8.2.8.3	Unsuccessful Operation	62
8.2.8.4	Abnormal Conditions	62
8.2.9	Common Measurement Reporting	66
8.2.9.1	General	66
8.2.9.2	Successful Operation	66
8.2.9.3	Abnormal Conditions	67
8.2.10	Common Measurement Termination	67
8.2.10.1	General	67
8.2.10.2	Successful Operation	67
8.2.10.3	Abnormal Conditions	68
8.2.11	Common Measurement Failure	68
8.2.11.1	General	68
8.2.11.2	Successful Operation	68
8.2.11.3	Abnormal Conditions	68
8.2.12	Cell Setup	68
8.2.12.1	General	68
8.2.12.2	Successful Operation	68
8.2.12.3	Unsuccessful Operation	70
8.2.12.4	Abnormal Conditions	71
8.2.13	Cell Reconfiguration	71
8.2.13.1	General	71
8.2.13.2	Successful Operation	71
8.2.13.3	Unsuccessful Operation	74
8.2.13.4	Abnormal Conditions	74
8.2.14	Cell Deletion	75
8.2.14.1	General	75
8.2.14.2	Successful Operation	75
8.2.14.3	Unsuccessful Operation	75
8.2.14.4	Abnormal Conditions	75
8.2.15	Resource Status Indication	75
8.2.15.1	General	75
8.2.15.2	Successful Operation	76
8.2.15.3	Abnormal Conditions	83
8.2.16	System Information Update	83
8.2.16.1	General	83
8.2.16.2	Successful Operation	83
8.2.16.3	Unsuccessful Operation	84
8.2.16.4	Abnormal Conditions	85
8.2.17	Radio Link Setup	85
8.2.17.1	General	85
8.2.17.2	Successful Operation	86
8.2.17.3	Unsuccessful Operation	112
8.2.17.4	Abnormal Conditions	114
8.2.18	Physical Shared Channel Reconfiguration	118
8.2.18.1	General	118
8.2.18.2	Successful Operation	118
8.2.18.3	Unsuccessful Operation	133
8.2.18.4	Abnormal Conditions	133
8.2.19	Reset	136
8.2.19.1	General	136
8.2.19.2	Successful Operation	136
8.2.19.2.1	Reset Initiated by the CRNC	136
8.2.19.2.2	Reset Initiated by the Node B	137
8.2.19.3	Unsuccessful Operation	137
8.2.19.4	Abnormal Conditions	137
8.2.20	Cell Synchronisation Initiation [TDD]	137
8.2.20.1	General	137
8.2.20.2	Successful Operation	137
8.2.20.3	Unsuccessful Operation	139
8.2.20.4	Abnormal Conditions	139
8.2.21	Cell Synchronisation Reconfiguration [TDD]	139
8.2.21.1	General	139
8.2.21.2	Successful Operation	140
8.2.21.2.1	General	140
8.2.21.2.2	[3.84Mcps TDD - Cell Sync Burst Schedule]	140
8.2.21.2.3	[1.28Mcps TDD - SYNC_DL Code Schedule]	140
8.2.21.2.4	[3.84Mcps TDD - Cell Sync Burst Transmission Reconfiguration] [1.28Mcps TDD - SYNC_DL Code Transmission Reconfiguration]	141
8.2.21.2.5	[3.84Mcps TDD - Cell Sync Burst Measurement Reconfiguration] [1.28Mcps TDD - SYNC_DL Code Measurement Reconfiguration]	142
8.2.21.3	Unsuccessful Operation	143
8.2.21.4	Abnormal Conditions	143
8.2.22	Cell Synchronisation Reporting [TDD]	143
8.2.22.1	General	143
8.2.22.2	Successful Operation	144
8.2.22.3	Abnormal Conditions	144
8.2.23	Cell Synchronisation Termination [TDD]	144
8.2.23.1	General	144
8.2.23.2	Successful Operation	144
8.2.23.3	Abnormal Conditions	145
8.2.24	Cell Synchronisation Failure [TDD]	145
8.2.24.1	General	145
8.2.24.2	Successful Operation	145
8.2.24.3	Abnormal Conditions	145
8.2.25	Cell Synchronisation Adjustment [TDD]	145
8.2.25.1	General	145
8.2.25.2	Successful Operation	145
8.2.25.3	Unsuccessful Operation	146
8.2.25.4	Abnormal Conditions	147
8.2.26	Information Exchange Initiation	147
8.2.26.1	General	147
8.2.26.2	Successful Operation	147
8.2.26.3	Unsuccessful Operation	150
8.2.26.4	Abnormal Conditions	150
8.2.27	Information Reporting	151
8.2.27.1	General	151
8.2.27.2	Successful Operation	151
8.2.27.3	Abnormal Conditions	151
8.2.28	Information Exchange Termination	151
8.2.28.1	General	151
8.2.28.2	Successful Operation	151
8.2.28.3	Abnormal Conditions	152
8.2.29	Information Exchange Failure	152
8.2.29.1	General	152
8.2.29.2	Successful Operation	152
8.2.30	MBMS Notification Update	152
8.2.30.1	General	152
8.2.30.2	Successful Operation	152
8.2.30.3	Abnormal Conditions	153
8.2.31	UE Status Update [FDD and 1.28Mcps TDD]	153
8.2.31.1	General	153
8.2.31.2	Successful Operation	153
8.2.31.3	Abnormal Conditions	153
8.2.32	UE Status Update Confirmation [FDD and 1.28Mcps TDD]	153
8.2.32.1	General	153
8.2.32.2	Successful Operation	153
8.2.32.3	Abnormal Conditions	154
8.3	NBAP Dedicated Procedures	154
8.3.1	Radio Link Addition	154
8.3.1.1	General	154
8.3.1.2	Successful Operation	154
8.3.1.3	Unsuccessful Operation	184
8.3.1.4	Abnormal conditions	186
8.3.2	Synchronised Radio Link Reconfiguration Preparation	189
8.3.2.1	General	189
8.3.2.2	Successful Operation	190
8.3.2.3	Unsuccessful Operation	236
8.3.2.4	Abnormal Conditions	238
8.3.3	Synchronised Radio Link Reconfiguration Commit	244
8.3.3.1	General	244
8.3.3.2	Successful Operation	244
8.3.3.3	Abnormal Conditions	245
8.3.4	Synchronised Radio Link Reconfiguration Cancellation	246
8.3.4.1	General	246
8.3.4.2	Successful Operation	246
8.3.4.3	Abnormal Conditions	246
8.3.5	Unsynchronised Radio Link Reconfiguration	246
8.3.5.1	General	246
8.3.5.2	Successful Operation	246
8.3.5.3	Unsuccessful Operation	287
8.3.5.4	Abnormal Conditions	288
8.3.6	Radio Link Deletion	293
8.3.6.1	General	293
8.3.6.2	Successful Operation	293
8.3.6.3	Unsuccessful Operation	294
8.3.6.4	Abnormal Conditions	294
8.3.7	Downlink Power Control [FDD]	294
8.3.7.1	General	294
8.3.7.2	Successful Operation	294
8.3.7.3	Abnormal Conditions	295
8.3.8	Dedicated Measurement Initiation	295
8.3.8.1	General	295
8.3.8.2	Successful Operation	295
8.3.8.3	Unsuccessful Operation	299
8.3.8.4	Abnormal Conditions	299
8.3.9	Dedicated Measurement Reporting	300
8.3.9.1	General	300
8.3.9.2	Successful Operation	300
8.3.9.3	Abnormal Conditions	301
8.3.10	Dedicated Measurement Termination	301
8.3.10.1	General	301
8.3.10.2	Successful Operation	301
8.3.10.3	Abnormal Conditions	301
8.3.11	Dedicated Measurement Failure	302
8.3.11.1	General	302
8.3.11.2	Successful Operation	302
8.3.11.3	Abnormal Conditions	302
8.3.12	Radio Link Failure	302
8.3.12.1	General	302
8.3.12.2	Successful Operation	302
8.3.12.3	Abnormal Conditions	303
8.3.13	Radio Link Restoration	304
8.3.13.1	General	304
8.3.13.2	Successful Operation	304
8.3.13.3	Abnormal Condition	304
8.3.14	Compressed Mode Command [FDD]	304
8.3.14.1	General	304
8.3.14.2	Successful Operation	305
8.3.14.3	Abnormal Conditions	305
8.3.15	Downlink Power Timeslot Control [TDD]	305
8.3.15.1	General	305
8.3.15.2	Successful Operation	306
8.3.15.3	Abnormal Conditions	306
8.3.16	Radio Link Pre-emption	306
8.3.16.1	General	306
8.3.16.2	Successful Operation	306
8.3.16.3	Abnormal Conditions	307
8.3.17	Bearer Re-arrangement	307
8.3.17.1	General	307
8.3.17.2	Successful Operation	307
8.3.17.3	Abnormal Conditions	307
8.3.18	Radio Link Activation	307
8.3.18.1	General	307
8.3.18.2	Successful Operation	307
8.3.18.3	Abnormal Conditions	308
8.3.19	Radio Link Parameter Update	309
8.3.19.1	General	309
8.3.19.2	Successful Operation	309
8.3.19.3	Abnormal Conditions	310
8.3.20	Secondary UL Frequency Reporting [FDD]	310
8.3.20.1	General	310
8.3.20.2	Successful Operation	310
8.3.20.3	Abnormal Conditions	311
8.3.21	Secondary UL Frequency Update [FDD]	311
8.3.21.1	General	311
8.3.21.2	Successful Operation	311
8.3.21.3	Abnormal Conditions	311
8.4	Error Handling Procedures	312
8.4.1	Error Indication	312
8.4.1.1	General	312
8.4.1.2	Successful Operation	312
8.4.1.3	Abnormal Conditions	313
9	Elements for NBAP communication	313
9.1	Message Functional Definition and Contents	313
9.1.1	General	313
9.1.2	Message Contents	313
9.1.2.1	Presence	313
9.1.2.2	Criticality	314
9.1.2.3	Range	314
9.1.2.4	Assigned Criticality	314
9.1.3	COMMON TRANSPORT CHANNEL SETUP REQUEST	315
9.1.3.1	FDD Message	315
9.1.3.2	TDD Message	319
9.1.4	COMMON TRANSPORT CHANNEL SETUP RESPONSE	329
9.1.5	COMMON TRANSPORT CHANNEL SETUP FAILURE	329
9.1.6	COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST	330
9.1.6.1	FDD Message	330
9.1.6.2	TDD Message	331
9.1.7	COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE	334
9.1.8	COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE	334
9.1.9	COMMON TRANSPORT CHANNEL DELETION REQUEST	335
9.1.10	COMMON TRANSPORT CHANNEL DELETION RESPONSE	335
9.1.11	BLOCK RESOURCE REQUEST	335
9.1.12	BLOCK RESOURCE RESPONSE	336
9.1.13	BLOCK RESOURCE FAILURE	336
9.1.14	UNBLOCK RESOURCE INDICATION	336
9.1.15	AUDIT REQUIRED INDICATION	336
9.1.16	AUDIT REQUEST	337
9.1.17	AUDIT RESPONSE	338
9.1.17A	AUDIT FAILURE	345
9.1.18	COMMON MEASUREMENT INITIATION REQUEST	346
9.1.19	COMMON MEASUREMENT INITIATION RESPONSE	349
9.1.20	COMMON MEASUREMENT INITIATION FAILURE	350
9.1.21	COMMON MEASUREMENT REPORT	351
9.1.22	COMMON MEASUREMENT TERMINATION REQUEST	352
9.1.23	COMMON MEASUREMENT FAILURE INDICATION	352
9.1.24	CELL SETUP REQUEST	353
9.1.24.1	FDD Message	353
9.1.24.2	TDD Message	356
9.1.25	CELL SETUP RESPONSE	360
9.1.26	CELL SETUP FAILURE	360
9.1.27	CELL RECONFIGURATION REQUEST	361
9.1.27.1	FDD Message	361
9.1.27.2	TDD Message	363
9.1.28	CELL RECONFIGURATION RESPONSE	366
9.1.29	CELL RECONFIGURATION FAILURE	366
9.1.30	CELL DELETION REQUEST	366
9.1.31	CELL DELETION RESPONSE	366
9.1.32	RESOURCE STATUS INDICATION	367
9.1.33	SYSTEM INFORMATION UPDATE REQUEST	377
9.1.34	SYSTEM INFORMATION UPDATE RESPONSE	378
9.1.35	SYSTEM INFORMATION UPDATE FAILURE	379
9.1.36	RADIO LINK SETUP REQUEST	380
9.1.36.1	FDD message	380
9.1.36.2	TDD message	384
9.1.37	RADIO LINK SETUP RESPONSE	389
9.1.37.1	FDD message	389
9.1.37.2	TDD Message	391
9.1.38	RADIO LINK SETUP FAILURE	394
9.1.38.1	FDD Message	394
9.1.38.2	TDD Message	396
9.1.39	RADIO LINK ADDITION REQUEST	397
9.1.39.1	FDD Message	397
9.1.39.2	TDD Message	400
9.1.40	RADIO LINK ADDITION RESPONSE	404
9.1.40.1	FDD message	404
9.1.40.2	TDD Message	406
9.1.41	RADIO LINK ADDITION FAILURE	409
9.1.41.1	FDD Message	409
9.1.41.2	TDD Message	410
9.1.42	RADIO LINK RECONFIGURATION PREPARE	411
9.1.42.1	FDD Message	411
9.1.42.2	TDD Message	416
9.1.43	RADIO LINK RECONFIGURATION READY	428
9.1.44	RADIO LINK RECONFIGURATION FAILURE	430
9.1.45	RADIO LINK RECONFIGURATION COMMIT	431
9.1.46	RADIO LINK RECONFIGURATION CANCEL	431
9.1.47	RADIO LINK RECONFIGURATION REQUEST	432
9.1.47.1	FDD Message	432
9.1.47.2	TDD Message	436
9.1.48	RADIO LINK RECONFIGURATION RESPONSE	441
9.1.49	RADIO LINK DELETION REQUEST	443
9.1.50	RADIO LINK DELETION RESPONSE	443
9.1.51	DL POWER CONTROL REQUEST [FDD]	444
9.1.52	DEDICATED MEASUREMENT INITIATION REQUEST	445
9.1.53	DEDICATED MEASUREMENT INITIATION RESPONSE	447
9.1.54	DEDICATED MEASUREMENT INITIATION FAILURE	449
9.1.55	DEDICATED MEASUREMENT REPORT	450
9.1.56	DEDICATED MEASUREMENT TERMINATION REQUEST	451
9.1.57	DEDICATED MEASUREMENT FAILURE INDICATION	452
9.1.58	RADIO LINK FAILURE INDICATION	453
9.1.59	RADIO LINK RESTORE INDICATION	454
9.1.60	COMPRESSED MODE COMMAND [FDD]	454
9.1.61	ERROR INDICATION	455
9.1.62	PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST	455
9.1.62.1	FDD Message	455
9.1.62.2	TDD Message	457
9.1.63	PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE	478
9.1.64	PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE	479
9.1.65	RESET REQUEST	480
9.1.66	RESET RESPONSE	481
9.1.67	DL POWER TIMESLOT CONTROL REQUEST [TDD]	482
9.1.68	RADIO LINK PREEMPTION REQUIRED INDICATION	482
9.1.69	INFORMATION EXCHANGE INITIATION REQUEST	482
9.1.70	INFORMATION EXCHANGE INITIATION RESPONSE	483
9.1.71	INFORMATION EXCHANGE INITIATION FAILURE	483
9.1.72	INFORMATION REPORT	483
9.1.73	INFORMATION EXCHANGE TERMINATION REQUEST	483
9.1.74	INFORMATION EXCHANGE FAILURE INDICATION	484
9.1.75	CELL SYNCHRONISATION INITIATION REQUEST [TDD]	484
9.1.76	CELL SYNCHRONISATION INITIATION RESPONSE [TDD]	485
9.1.77	CELL SYNCHRONISATION INITIATION FAILURE [TDD]	485
9.1.78	CELL SYNCHRONISATION RECONFIGURATION REQUEST [TDD]	486
9.1.79	CELL SYNCHRONISATION RECONFIGURATION RESPONSE [TDD]	488
9.1.80	CELL SYNCHRONISATION RECONFIGURATION FAILURE [TDD]	488
9.1.81	CELL SYNCHRONISATION REPORT [TDD]	488
9.1.82	CELL SYNCHRONISATION TERMINATION REQUEST [TDD]	489
9.1.83	CELL SYNCHRONISATION FAILURE INDICATION [TDD]	490
9.1.84	CELL SYNCHRONISATION ADJUSTMENT REQUEST [TDD]	490
9.1.85	CELL SYNCHRONISATION ADJUSTMENT RESPONSE [TDD]	490
9.1.86	CELL SYNCHRONISATION ADJUSTMENT FAILURE [TDD]	491
9.1.87	BEARER REARRANGEMENT INDICATION	492
9.1.88	RADIO LINK ACTIVATION COMMAND	493
9.1.88.1	FDD Message	493
9.1.88.2	TDD Message	493
9.1.89	RADIO LINK PARAMETER UPDATE INDICATION	494
9.1.89.1	FDD Message	494
9.1.89.2	TDD Message	495
9.1.90	MBMS NOTIFICATION UPDATE COMMAND	495
9.1.91	UE STATUS UPDATE COMMAND	495
9.1.92	SECONDARY UL FREQUENCY REPORT	496
9.1.92.1	FDD Message	496
9.1.93	SECONDARY UL FREQUENCY UPDATE INDICATION	496
9.1.93.1	FDD Message	496
9.1.94	UE STATUS UPDATE CONFIRM REQUEST	496
9.1.95	UE STATUS UPDATE CONFIRM RESPONSE	497
9.2	Information Element Functional Definition and Contents	497
9.2.0	General	497
9.2.1	Common parameters	497
9.2.1.1	Add/Delete Indicator	497
9.2.1.1A	Allocation/Retention Priority	497
9.2.1.1B	Alternative Format Reporting Indicator	498
9.2.1.2	Availability Status	498
9.2.1.3	BCCH Modification Time	498
9.2.1.4	Binding ID	499
9.2.1.4A	BLER	499
9.2.1.5	Blocking Priority Indicator	499
9.2.1.5A	Burst Mode Parameters	499
9.2.1.5B	Broadcast Common Transport Bearer Indication	500
9.2.1.5C	Broadcast Reference	500
9.2.1.6	Cause	501
9.2.1.7	CFN	506
9.2.1.8	CFN Offset	506
9.2.1.9	C-ID	506
9.2.1.9A	Common Channels Capacity Consumption Law	507
9.2.1.9B	Common Measurement Accuracy	508
9.2.1.10	Common Measurement Object Type	508
9.2.1.11	Common Measurement Type	508
9.2.1.12	Common Measurement Value	510
9.2.1.12A	Common Measurement Value Information	516
9.2.1.13	Common Physical Channel ID	516
9.2.1.13A	Common Physical Channel Status Information	517
9.2.1.14	Common Transport Channel ID	517
9.2.1.14A	Common Transport Channel Information Response	517
9.2.1.14B	Common Transport Channel Status Information	517
9.2.1.15	Communication Control Port ID	517
9.2.1.16	Configuration Generation ID	518
9.2.1.17	Criticality Diagnostics	518
9.2.1.18	CRNC Communication Context ID	520
9.2.1.18A	CTFC	520
9.2.1.19	DCH Combination Indicator	521
9.2.1.20	DCH ID	521
9.2.1.20A	Dedicated Channels Capacity Consumption Law	521
9.2.1.20B	DL Or Global Capacity Credit	522
9.2.1.20C	DCH Information Response	523
9.2.1.21	DL Power	523
9.2.1.22	Dedicated Measurement Object Type	523
9.2.1.23	Dedicated Measurement Type	523
9.2.1.24	Dedicated Measurement Value	524
9.2.1.24A	Dedicated Measurement Value Information	527
9.2.1.24B	DGPS Corrections	527
9.2.1.24C	Delayed Activation	528
9.2.1.24D	Delayed Activation Update	529
9.2.1.24E	Discard Timer	529
9.2.1.25	Diversity Control Field	529
9.2.1.26	Diversity Indication	530
9.2.1.26A	DL DPCH Timing Adjustment	530
9.2.1.27	DSCH ID	530
9.2.1.27A	DSCH Information Response	530
9.2.1.28	DSCH Transport Format Set	530
9.2.1.29	DSCH Transport Format Combination Set	530
9.2.1.29A	End Of Audit Sequence Indicator	530
9.2.1.29B	FN Reporting Indicator	530
9.2.1.30	Frame Handling Priority	531
9.2.1.31	Frame Offset	531
9.2.1.31A	IB_OC_ID	531
9.2.1.31B	GPS Navigation Model & Time Recovery	531
9.2.1.31C	GPS Ionospheric Model	533
9.2.1.31D	GPS UTC Model	533
9.2.1.31E	GPS Real-Time Integrity	534
9.2.1.31F	GPS Almanac	534
9.2.1.31G	GPS Receiver Geographical Position (GPS RX Pos)	535
9.2.1.31Ga	HSDPA Capability	536
9.2.1.31H	HS-DSCH Information To Modify	536
9.2.1.31HA	HS-DSCH Information To Modify Unsynchronised	540
9.2.1.31Ha	HS-DSCH Initial Capacity Allocation	543
9.2.1.31Hb	HS-DSCH Initial Window Size	543
9.2.1.31I	HS-DSCH MAC-d Flow ID	543
9.2.1.31IA	HS-DSCH MAC-d Flows Information	544
9.2.1.31IB	HS-DSCH MAC-d Flows To Delete	546
9.2.1.31IC	HS-DSCH MAC-d PDU Size Capability	546
9.2.1.31ID	HS-DSCH MAC-d PDU Size Format	546
9.2.1.31Ia	HS-DSCH Physical Layer Category	546
9.2.1.31Iaa	HS-DSCH Provided Bit Rate Value	547
9.2.1.31Ib	HS-DSCH Provided Bit Rate Value Information	547
9.2.1.31Iba	HS-DSCH Required Power Value	547
9.2.1.31Ic	HS-DSCH Required Power Value Information	547
9.2.1.31J	HS-DSCH RNTI	548
9.2.1.31K	HS-SCCH Code Change Indicator	548
9.2.1.31L	HS-SCCH Code Change Grant	548
9.2.1.31M	HS-PDSCH Code Change Indicator [FDD]	548
9.2.1.31N	HS-PDSCH Code Change Grant [FDD]	549
9.2.1.32	IB_SG_DATA	549
9.2.1.33	IB_SG_POS	549
9.2.1.34	IB_SG_REP	549
9.2.1.35	IB Type	549
9.2.1.36	Indication Type	550
9.2.1.36A	Information Exchange Object Type	550
9.2.1.36B	Information Report Characteristics	551
9.2.1.36C	Information Exchange ID	551
9.2.1.36D	Information Type	551
9.2.1.36E	Information Threshold	554
9.2.1.36F	IPDL Indicator	554
9.2.1.37	Limited Power Increase	554
9.2.1.37A	Local Cell Group ID	554
9.2.1.38	Local Cell ID	555
9.2.1.38A	MAC-d PDU Size	555
9.2.1.38Aa	MAC-hs Guaranteed Bit Rate	555
9.2.1.38Ab	MAC-hs Reordering Buffer Size for RLC-UM	555
9.2.1.38Ac	MAC-hs Reset Indicator	555
9.2.1.38B	MAC-hs Window Size	556
9.2.1.38C	MAC PDU Size Extended	556
9.2.1.39	Maximum DL Power Capability	556
9.2.1.40	Maximum Transmission Power	556
9.2.1.40A	Measurement Availability Indicator	556
9.2.1.40B	Measurement Change Time	556
9.2.1.41	Measurement Filter Coefficient	557
9.2.1.41A	Measurement Hysteresis Time	557
9.2.1.42	Measurement ID	557
9.2.1.43	Measurement Increase/Decrease Threshold	557
9.2.1.43A	Measurement Recovery Behavior	560
9.2.1.43B	Measurement Recovery Reporting Indicator	560
9.2.1.43C	Measurement Recovery Support Indicator	560
9.2.1.44	Measurement Threshold	561
9.2.1.45	Message Discriminator	565
9.2.1.45A	Message Structure	566
9.2.1.46	Message Type	566
9.2.1.46a	MICH CFN	567
9.2.1.46A	Minimum DL Power Capability	567
9.2.1.47	Minimum Spreading Factor	567
9.2.1.47a	Modification Period	567
9.2.1.47A	N_INSYNC_IND	568
9.2.1.47B	N_OUTSYNC_IND	568
9.2.1.47C	Neighbouring FDD Cell Measurement Information	568
9.2.1.47D	Neighbouring TDD Cell Measurement Information	568
9.2.1.47E	Neighbouring TDD Cell Measurement Information LCR	568
9.2.1.47F	NI	569
9.2.1.48	Node B Communication Context ID	569
9.2.1.49	Payload CRC Presence Indicator	569
9.2.1.49A	PICH Power	569
9.2.1.49B	Power Local Cell Group ID	570
9.2.1.49C	Priority Queue ID	570
9.2.1.49D	Process Memory Size	570
9.2.1.50	Puncture Limit	570
9.2.1.50A	QE-Selector	571
9.2.1.51	Report Characteristics	571
9.2.1.51a	Report Periodicity	573
9.2.1.51A	Requested Data Value	573
9.2.1.51B	Requested Data Value Information	575
9.2.1.52	Resource Operational State	575
9.2.1.52A	Retention Priority	575
9.2.1.52B	RLC Mode	575
9.2.1.53	RL ID	575
9.2.1.53a	RNC-Id	576
9.2.1.53b	RTWP* Reporting Indicator	576
9.2.1.53c	RTWP* for Cell Portion Reporting Indicator	576
9.2.1.53A	SFN	576
9.2.1.53B	Segment Type	576
9.2.1.53C	SFN-SFN Measurement Threshold Information	577
9.2.1.53D	SFN-SFN Measurement Time Stamp	577
9.2.1.53E	SFN-SFN Measurement Value Information	577
9.2.1.53F	SFN-SFN Value	578
9.2.1.53G	RL Specific DCH Information	579
9.2.1.53H	Scheduling Priority Indicator	579
9.2.1.53I	SID	579
9.2.1.54	SIB Deletion Indicator	579
9.2.1.55	SIB Originator	579
9.2.1.55A	Signalling Bearer Request Indicator	580
9.2.1.56	Shutdown Timer	580
9.2.1.56a	T1	580
9.2.1.56A	T_RLFAILURE	580
9.2.1.56B	Start Of Audit Sequence Indicator	580
9.2.1.56C	TFCI2 Bearer Request Indicator	581
9.2.1.57	TFCI Presence	581
9.2.1.58	TFCS (Transport Format Combination Set)	581
9.2.1.58A	TNL QoS	582
9.2.1.59	Transport Format Set	583
9.2.1.60	ToAWE	584
9.2.1.61	ToAWS	585
9.2.1.62	Transaction ID	585
9.2.1.62A	Transport Bearer Request Indicator	585
9.2.1.63	Transport Layer Address	585
9.2.1.64	TSTD Indicator	586
9.2.1.64A	TUTRAN-GPS Measurement Value Information	586
9.2.1.64B	TUTRAN-GPS Measurement Threshold Information	587
9.2.1.64C	TUTRAN-GPS Accuracy Class	587
9.2.1.65	UARFCN	587
9.2.1.65A	UL Capacity Credit	587
9.2.1.65B	UTRAN Cell Identifier (UC-Id)	587
9.2.1.65C	Extended RNC-ID	588
9.2.1.66	UL FP Mode	588
9.2.1.67	UL interference level	588
9.2.1.67A	UL SIR	588
9.2.1.68	Unidirectional DCH Indicator	588
9.2.1.69	E-DCH MAC-d Flow Multiplexing List	589
9.2.1.70	E-DCH Capability	589
9.2.1.71	E-DCH Logical Channel Information	589
9.2.1.72	E-DCH Logical Channel To Modify	590
9.2.1.73	E-DCH MAC-d Flows To Delete	591
9.2.1.74	E-DCH MAC-d Flow ID	592
9.2.1.74A	E-DCH MAC-d PDU Size Capability	592
9.2.1.74B	E-DCH MAC-d PDU Size Format	592
9.2.1.75	E-RNTI	592
9.2.1.76	E-DCH DDI Value	592
9.2.1.77	E-DCH Provided Bit Rate Value	593
9.2.1.78	E-DCH Provided Bit Rate Value Information	593
9.2.1.79	E-DCH Processing Overload Level	593
9.2.1.80	Logical channel ID	593
9.2.1.81	Maximum Number Of Retransmissions For E-DCH	594
9.2.1.82	MAC-es Guaranteed Bit Rate	594
9.2.1.83	MAC-e Reset Indicator	594
9.2.1.84	Scheduling Information	594
9.2.1.85	E-DCH Power Offset for Scheduling Info	594
9.2.1.86	MBMS Capability	594
9.2.1.87	Modulation	595
9.2.1.88	DGANSS Corrections	595
9.2.1.89	GANSS Almanac	597
9.2.1.90	GANSS Clock Model	602
9.2.1.90a	GANSS Additional Clock Models	603
9.2.1.91	GANSS Ionospheric Model	605
9.2.1.91a	GANSS Additional Ionospheric Model	605
9.2.1.92	GANSS Navigation Model	605
9.2.1.93	GANSS Orbit Model	605
9.2.1.93a	GANSS Additional Orbit Models	606
9.2.1.94	GANSS Real Time Integrity	611
9.2.1.95	GANSS Receiver Geographical Position (GANSS RX Pos)	612
9.2.1.96	GANSS Time Model	612
9.2.1.96a	GANSS Additional Time Models	613
9.2.1.97	GANSS UTC Model	613
9.2.1.97a	GANSS Additional UTC Models	614
9.2.1.98	TUTRAN-GANSS Accuracy Class	616
9.2.1.99	TUTRAN-GANSS Measurement Threshold Information	616
9.2.1.100	TUTRAN-GANSS Measurement Value Information	617
9.2.1.101	GANSS Reference Time	619
9.2.1.102	HARQ Memory Partitioning	620
9.2.1.103	GANSS Data Bit Assistance	621
9.2.1.104	GANSS ID	621
9.2.1.104a	GANSS Time ID	621
9.2.1.105	GANSS Navigation Model And Time Recovery	621
9.2.1.105a	GANSS Additional Navigation Models And Time Recovery	622
9.2.1.106	GANSS Signal ID	623
9.2.1.107	GANSS Transmission Time	623
9.2.1.107a	GANSS Earth Orientation Parameters	624
9.2.1.107b	SBAS ID	624
9.2.1.107c	GANSS Auxiliary Information	625
9.2.1.107d	Additional Ionospheric Model Request	625
9.2.1.107e	Earth Orientation Parameters Request	625
9.2.1.107f	GANSS Additional Navigation Models And Time Recovery Request	625
9.2.1.107g	GANSS Additional UTC Models Request	626
9.2.1.107h	GANSS Auxiliary Information Request	626
9.2.1.108	IP Multicast Indication	626
9.2.1.109	IP Multicast Data Bearer Indication	626
9.2.1.110	SixtyfourQAM DL Capability	626
9.2.1.111	FACH Measurement Occasion Cycle Length Coefficient	627
9.2.1.112	MAC-ehs Reset Timer	627
9.2.1.113	Paging MAC Flow ID	627
9.2.1.114	Enhanced FACH Capability	627
9.2.1.115	Enhanced PCH Capability	627
9.2.1.116	Enhanced UE DRX Capability	628
9.2.1.117	Priority Queue Information for Enhanced FACH/PCH	628
9.2.1.118	MIMO Capability	628
9.2.1.119	MIMO Activation Indicator	628
9.2.1.120	MIMO Mode Indicator	628
9.2.1.121	SixtyfourQAM DL and MIMO Combined Capability	628
9.2.1.122	DL RLC PDU Size Format	629
9.2.1.123	UE Aggregate Maximum Bit Rate	629
9.2.1.124	Dormant Mode Indicator	630
9.2.1.125	DGNSS Validity Period	630
9.2.1.126	E-RNTI Release Status	630
9.2.1.127	DBDS Corrections	630
9.2.1.128	BDS Ionospheric Grid Model	631
9.2.1.129	Improved Synchronized RRC Indicator	631
9.2.2	FDD specific parameters	632
9.2.2.a	ACK-NACK Repetition Factor	632
9.2.2.b	ACK Power Offset	632
9.2.2.A	Active Pattern Sequence Information	632
9.2.2.B	Adjustment Period	633
9.2.2.C	Adjustment Ratio	633
9.2.2.D	AICH Power	633
9.2.2.1	AICH Transmission Timing	633
9.2.2.1A	AP Preamble Signature	633
9.2.2.1B	AP Sub Channel Number	633
9.2.2.1Ba	Best Cell Portions	634
9.2.2.1Bb	Bundling Mode Indicator	634
9.2.2.1C	CD Sub Channel Numbers	634
9.2.2.1Ca	Cell Portion ID	634
9.2.2.1D	Channel Assignment Indication	634
9.2.2.2	Chip Offset	634
9.2.2.2A	Closed Loop Timing Adjustment Mode	634
9.2.2.3	Common Channels Capacity Consumption Law	635
9.2.2.3A	Compressed Mode Deactivation Flag	635
9.2.2.4	Compressed Mode Method	635
9.2.2.4A	CPCH Allowed Total Rate	635
9.2.2.4B	CPCH Scrambling Code Number	635
9.2.2.4C	CPCH UL DPCCH Slot Format	635
9.2.2.4Ca	CQI Power Offset	635
9.2.2.4Cb	CQI Repetition Factor	635
9.2.2.4D	DCH FDD Information	636
9.2.2.4E	DCHs FDD To Modify	636
9.2.2.4F	DCH Indicator For E-DCH-HSDPA Operation	637
9.2.2.4G	Transport Bearer Not Requested Indicator	637
9.2.2.4H	Transport Bearer Not Setup Indicator	637
9.2.2.5	D-Field Length	637
9.2.2.6	Dedicated Channels Capacity Consumption Law	637
9.2.2.7	Diversity Control Field	637
9.2.2.8	Diversity Indication	637
9.2.2.9	Diversity Mode	638
9.2.2.10	DL DPCH Slot Format	638
9.2.2.10A	DL DPCH Timing Adjustment	638
9.2.2.11	DL frame type	638
9.2.2.12	DL or Global Capacity Credit	638
9.2.2.12A	DL_power_averaging_window_size	638
9.2.2.12B	DL Power Balancing Information	638
9.2.2.12C	DL Power Balancing Activation Indicator	639
9.2.2.12D	DL Power Balancing Updated Indicator	639
9.2.2.13	DL Scrambling Code	639
9.2.2.13A	DL TPC Pattern 01 Count	640
9.2.2.13B	DSCH FDD Information	640
9.2.2.13C	DPC Mode	640
9.2.2.13D	DSCH FDD Common Information	640
9.2.2.13Da	E-DCH FDD Information	640
9.2.2.13DA	E-DCH FDD Update Information	641
9.2.2.13Db	E-DCH FDD Information Response	642
9.2.2.13Dc	E-DCH FDD DL Control Channel Information	642
9.2.2.13De	E-DCH RL Indication	644
9.2.2.13Df	E-DCH FDD Information to Modify	644
9.2.2.13Dh	E-DCH Transport Format Combination Set Information (E-TFCS Information)	647
9.2.2.13Di	E-TTI	648
9.2.2.13Dj	E-DPCCH Power Offset	648
9.2.2.13Dk	E-DCH HARQ Power Offset FDD	648
9.2.2.13Dl	E-DCH MAC-d Flow Multiplexing List	648
9.2.2.13Dm	Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission	648
9.2.2.13Dn	HARQ Process Allocation For 2ms TTI	648
9.2.2.13Dp	Reference E-TFCI Power Offset	649
9.2.2.13Dq	Extended Reference E-TFCI Power Offset	649
9.2.2.13Dr	Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission	649
9.2.2.13E	Enhanced DSCH PC	649
9.2.2.13F	Enhanced DSCH PC Counter	649
9.2.2.13G	Enhanced DSCH PC Indicator	650
9.2.2.13H	Enhanced DSCH PC Wnd	650
9.2.2.13I	Enhanced DSCH Power Offset	650
9.2.2.13Ia	E- RGCH/E-HICH FDD Code Information	650
9.2.2.13Ib	E- AGCH FDD Code Information	650
9.2.2.13Ic	E-RGCH Release Indicator	650
9.2.2.13Id	E-AGCH Power Offset	651
9.2.2.13Ie	E-RGCH Power Offset	651
9.2.2.13If	E-HICH Power Offset	651
9.2.2.13Ig	E-RGCH 2-Index-Step Threshold	651
9.2.2.13Ih	E-RGCH 3-Index-Step Threshold	651
9.2.2.13J	E-DCH Capability	652
9.2.2.13Ja	E-DCH Capacity Consumption Law	652
9.2.2.13K	E-DCH Logical Channel Information	653
9.2.2.13L	E-DCH Logical Channel To Modify	653
9.2.2.13M	E-DCH MAC-d Flows Information	653
9.2.2.13N	E-DCH MAC-d Flows To Delete	655
9.2.2.13O	E-DCH MAC-d Flow ID	655
9.2.2.13P	E-RNTI	655
9.2.2.13Q	E-DCH DDI Value	655
9.2.2.13R	E-DCH Provided Bit Rate Value	655
9.2.2.13S	E-DCH Provided Bit Rate Value Information	655
9.2.2.13T	E-DCH Maximum Bitrate	655
9.2.2.13U	E-DCH Processing Overload Level	655
9.2.2.13V	E-DCH TTI2ms Capability	655
9.2.2.13W	E-DCH SF Capability	656
9.2.2.13X	E-DCH HARQ Combining Capability	656
9.2.2.13Y	E-DCH Reference Power Offset	656
9.2.2.13Z	E-DCH Power Offset for Scheduling Info	656
9.2.2.14	FDD DL Channelisation Code Number	656
9.2.2.14A	FDD DL Code Information	657
9.2.2.14B	FDD S-CCPCH Frame Offset	657
9.2.2.15	FDD SCCPCH Offset	657
9.2.2.16	FDD TPC DL Step Size	657
9.2.2.16a	F-DPCH Capability	658
9.2.2.16A	First RLS Indicator	658
9.2.2.17	Gap Period	658
9.2.2.18	Gap Position Mode	658
9.2.2.18a	HARQ Preamble Mode	658
9.2.2.18b	HARQ Preamble Mode Activation Indicator	658
9.2.2.18ba	HARQ Info for E-DCH	658
9.2.2.18c	Logical channel ID	659
9.2.2.18A	Limited Power Increase	659
9.2.2.18B	Inner Loop DL PC Status	659
9.2.2.18C	IPDL FDD Parameters	659
9.2.2.18Ca	HS-DSCH configured indicator	659
9.2.2.18D	HS-DSCH FDD Information	660
9.2.2.18Da	HS-DSCH FDD Secondary Serving Information	662
9.2.2.18E	HS-DSCH FDD Information Response	664
9.2.2.18EA	HS-DSCH FDD Secondary Serving Information Response	664
9.2.2.18EB	HS-DSCH FDD Secondary Serving Information To Modify	665
9.2.2.18EC	HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised	667
9.2.2.18Ea	HS-DSCH FDD Update Information	668
9.2.2.18Eaa	HS-DSCH FDD Secondary Serving Update Information	669
9.2.2.18Eb	HS-DSCH Serving Cell Change Information	669
9.2.2.18Ec	HS-DSCH Serving Cell Change Information Response	670
9.2.2.18Eca	HS-DSCH Secondary Serving Cell Change Information Response	670
9.2.2.18Ed	E-DCH Serving Cell Change Information Response	670
9.2.2.18Ee	HS-DSCH TB Size Table Indicator	671
9.2.2.18F	HS-PDSCH FDD Code Information	671
9.2.2.18G	HS-SCCH FDD Code Information	671
9.2.2.18H	HS-SCCH ID	672
9.2.2.18I	HS-SCCH Power Offset	672
9.2.2.18K	Initial DL DPCH Timing Adjustment Allowed	672
9.2.2.19	Max Adjustment Period	672
9.2.2.20	Max Adjustment Step	672
9.2.2.20A	Max Number Of PCPCHs	673
9.2.2.20B	Max Number Of UL E-DPDCHs	673
9.2.2.20C	Maximum Set of E-DPDCHs	673
9.2.2.20D	Maximum Number Of Retransmissions For E-DCH	673
9.2.2.20E	MAC-es Guaranteed Bit Rate	673
9.2.2.20F	MAC-e Reset Indicator	673
9.2.2.21	Maximum Number Of UL DPDCHs	673
9.2.2.21a	Maximum Target Received Total Wide Band Power	673
9.2.2.21b	Target Non-serving E-DCH to Total E-DCH Power Ratio	674
9.2.2.21A	Maximum PDSCH Power	674
9.2.2.21B	CQI Feedback Cycle k	674
9.2.2.21C	Measurement Power Offset	674
9.2.2.21D	MICH Mode	674
9.2.2.22	Minimum UL Channelisation Code Length	674
9.2.2.22a	Min UL Channelisation Code Length For E-DCH FDD	675
9.2.2.23	Multiplexing Position	675
9.2.2.23a	NACK Power Offset	675
9.2.2.23A	N_EOT	675
9.2.2.23B	NF_max	675
9.2.2.23C	N_Start_Message	675
9.2.2.23D	Number Of Reported Cell Portions	675
9.2.2.24	Pattern Duration (PD)	675
9.2.2.24A	PCP Length	675
9.2.2.25	PDSCH Code Mapping	675
9.2.2.26	PICH Mode	676
9.2.2.27	Power Adjustment Type	676
9.2.2.28	Power Control Mode	676
9.2.2.29	Power Offset	676
9.2.2.29A	Power_Raise_Limit	676
9.2.2.30	Power Resume Mode	676
9.2.2.31	Preamble Signatures	677
9.2.2.32	Preamble Threshold	677
9.2.2.33	Primary CPICH Power	677
9.2.2.33A	Primary CPICH Usage For Channel Estimation	677
9.2.2.34	Primary Scrambling Code	677
9.2.2.35	Propagation Delay	678
9.2.2.35A	Extended Propagation Delay	678
9.2.2.36	QE-Selector	678
9.2.2.36A	Qth Parameter	678
9.2.2.37	RACH Slot Format	678
9.2.2.38	RACH Sub Channel Numbers	679
9.2.2.39	RL Set ID	679
9.2.2.39a	RL Specific E-DCH Information	679
9.2.2.39A	Received Total Wide Band Power	679
9.2.2.39B	Reference Received Total Wide Band Power	680
9.2.2.39C	Reference Received Total Wide Band Power Reporting	680
9.2.2.39D	Reference Received Total Wide Band Power Support Indicator	680
9.2.2.40	S-Field Length	680
9.2.2.40A	Scheduling Information	680
9.2.2.41	Scrambling Code Change	680
9.2.2.42	Scrambling Code Number	681
9.2.2.43	Secondary CCPCH Slot Format	681
9.2.2.43A	Secondary CPICH Information Change	681
9.2.2.44	SSDT Cell Identity	681
9.2.2.44A	SSDT Cell Identity For EDSCHPC	681
9.2.2.45	SSDT Cell ID Length	681
9.2.2.46	SSDT Support Indicator	681
9.2.2.47	SSDT Indication	681
9.2.2.48	STTD Indicator	682
9.2.2.48A	Synchronisation Indicator	682
9.2.2.48B	Serving E-DCH RL	682
9.2.2.49	T Cell	682
9.2.2.49A	TFCI2 Bearer Information Response	682
9.2.2.50	TFCI Signalling Mode	682
9.2.2.51	TGD	683
9.2.2.52	TGL	683
9.2.2.53	Transmit Diversity Indicator	683
9.2.2.53A	Transmission Gap Pattern Sequence Information	683
9.2.2.53B	Transmission Gap Pattern Sequence Code Information	685
9.2.2.54	UL/DL compressed mode selection	685
9.2.2.55	UL delta SIR	686
9.2.2.56	UL delta SIR after	686
9.2.2.57	UL DPCCH Slot Format	686
9.2.2.58	UL SIR	686
9.2.2.59	UL Scrambling Code	686
9.2.2.60	UL Capacity Credit	686
9.2.2.61	UL DPDCH Indicator For E-DCH Operation	686
9.2.2.62	Fast Reconfiguration Mode	686
9.2.2.63	Fast Reconfiguration Permission	687
9.2.2.64	Continuous Packet Connectivity DTX-DRX Capability	687
9.2.2.65	Continuous Packet Connectivity HS-SCCH less Capability	687
9.2.2.66	Continuous Packet Connectivity DTX-DRX Information	687
9.2.2.67	Continuous Packet Connectivity DTX-DRX Information To Modify	689
9.2.2.68	Continuous Packet Connectivity HS-SCCH less Information	691
9.2.2.69	Continuous Packet Connectivity HS-SCCH less Information Response	691
9.2.2.69A	Continuous Packet Connectivity HS-SCCH less Deactivate Indicator	692
9.2.2.70	MIMO Capability	692
9.2.2.71	MIMO Activation Indicator	692
9.2.2.72	MIMO Mode Indicator	692
9.2.2.73	MIMO Pilot Configuration	692
9.2.2.74	SixtyfourQAM DL Capability	692
9.2.2.74A	Sixtyfour QAM Usage Allowed Indicator	692
9.2.2.74B	SixtyfourQAM DL Usage Indicator	693
9.2.2.75	HS-DSCH Common System Information	693
9.2.2.76	HS-DSCH Paging System Information	695
9.2.2.77	HS-DSCH Common System Information Response	695
9.2.2.78	HS-DSCH Paging System Information Response	696
9.2.2.79	Common MAC Flow ID	696
9.2.2.80	Paging MAC Flow ID	696
9.2.2.81	HSDPA Associated PICH Information	697
9.2.2.82	FACH Measurement Occasion Cycle Length Coefficient	697
9.2.2.83	Priority Queue Information for Enhanced FACH/PCH	697
9.2.2.84	RACH Measurement Result	697
9.2.2.85	BCCH Specific HS-DSCH RNTI Information	697
9.2.2.86	Enhanced FACH Capability	697
9.2.2.87	Enhanced PCH Capability	697
9.2.2.88	SixteenQAM UL Capability	698
9.2.2.88A	SixteenQAM UL Operation Indicator	698
9.2.2.88B	E-TFCI Boost Information	698
9.2.2.88C	SixtyfourQAM UL Operation Indicator	698
9.2.2.89	SixteenQAM UL Information	698
9.2.2.90	SixteenQAM UL Information To Modify	698
9.2.2.91	Modulation Power Offset	698
9.2.2.92	Extended Secondary CCPCH Slot Format	699
9.2.2.93	F-DPCH Slot Format	699
9.2.2.94	F-DPCH Slot Format Capability	699
9.2.2.95	Max UE DTX Cycle	699
9.2.2.96	MIMO N/M Ratio	700
9.2.2.97	Common MAC Flows To Delete	700
9.2.2.98	Paging MAC Flows To Delete	700
9.2.2.99	MAC-ehs Reset Timer	700
9.2.2.100	E-AGCH Table Choice	700
9.2.2.101	Common E-DCH Capability	701
9.2.2.102	E-AI Capability	701
9.2.2.103	Common E-DCH System Information	701
9.2.2.104	Common E-DCH System Information Response	706
9.2.2.105	Common E-DCH MAC-d Flow Specific Information	707
9.2.2.106	Maximum TB Size	708
9.2.2.107	Enhanced UE DRX Capability	708
9.2.2.108	Enhanced UE DRX Information	709
9.2.2.109	E-DPCCH Power Boosting Capability	709
9.2.2.110	SixtyfourQAM DL and MIMO Combined Capability	709
9.2.2.111	HS-DSCH Preconfiguration Info	709
9.2.2.112	HS-DSCH Preconfiguration Setup	711
9.2.2.113	Multi Cell Capability Info	714
9.2.2.114	Minimum Reduced E-DPDCH Gain Factor	714
9.2.2.115	IMB Parameters	715
9.2.2.116	Common E-DCH HS-DPCCH Capability	715
9.2.2.117	UE Support Indicator Extension	715
9.2.2.118	MIMO Power Offset For S-CPICH Capability	716
9.2.2.119	Power Offset For Secondary CPICH for MIMO	716
9.2.2.120	MIMO Pilot Configuration Extension	717
9.2.2.121	TX Diversity on DL Control Channels by MIMO UE Capability	717
9.2.2.122	Single Stream MIMO Capability	717
9.2.2.123	Single Stream MIMO Activation Indicator	717
9.2.2.124	Single Stream MIMO Mode Indicator	717
9.2.2.125	Dual Band Capability Info	717
9.2.2.126	Void	718
9.2.2.127	HS-DSCH MAC-ehs Format	718
9.2.2.128	Activation Information	718
9.2.2.129	Cell Capability Container	719
9.2.2.130	Multicell E-DCH Transport Bearer Mode	723
9.2.2.131	Additional E-DCH FDD Setup Information	724
9.2.2.132	Additional E-DCH RL Specific Information To Setup	724
9.2.2.133	Additional E-DCH RL Specific Information To Add	725
9.2.2.134	Additional E-DCH RL Specific Information To Modify	725
9.2.2.135	Additional E-DCH FDD Information Response	725
9.2.2.136	Additional E-DCH Configuration Change Information	727
9.2.2.137	Additional E-DCH FDD Information	728
9.2.2.138	Additional E-DCH FDD Update Information	729
9.2.2.139	E-RNTI List	729
9.2.2.140	Multicell E-DCH Information	729
9.2.2.141	Additional Modified E-DCH FDD Information Response	729
9.2.2.142	Multicell E-DCH RL Specific Information	730
9.2.2.143	Precoding Weight Set Restriction	730
9.2.2.144	Non-Serving RL Preconfiguration Setup	731
9.2.2.145	Non-Serving RL Preconfiguration Info	731
9.2.2.146	Void	733
9.2.2.147	Usefulness of Battery Optimization	733
9.2.2.148	Common HS-DSCH RNTI List	733
9.2.2.149	Puncturing Handling in First Rate Matching Stage	733
9.2.2.150	Support of Dynamic DTXDRX Related HS-SCCH Order	733
9.2.2.151	UL CLTD Information Reconf	733
9.2.2.152	UL CLTD Information	734
9.2.2.153	UL CLTD Information To Modify	734
9.2.2.154	UL CLTD Information Removal	734
9.2.2.155	UL CLTD State Update Information	735
9.2.2.156	F-TPICH Slot Format	735
9.2.2.157	F-TPICH Offset	735
9.2.2.158	S-DPCCH Power Offset Information	735
9.2.2.159	UL CLTD Activation Information	735
9.2.2.160	F-TPICH Information	736
9.2.2.161	F-TPICH Information To Modify	736
9.2.2.162	F-TPICH Information Removal	736
9.2.2.163	F-TPICH Information Reconf	736
9.2.2.164	MIMO with four transmit antennas Activation Indicator	737
9.2.2.165	MIMO with four transmit antennas Pilot Configuration	737
9.2.2.166	MIMO with four transmit antennas Mode Indicator	737
9.2.2.167	Dual Stream MIMO with four transmit antennas Activation Indicator	737
9.2.2.168	Dual Stream MIMO with four transmit antennas Mode Indicator	737
9.2.2.169	Multiflow Reconfiguration	738
9.2.2.170	Multiflow Information	738
9.2.2.171	Multiflow Information To Modify	738
9.2.2.172	Multiflow Stop	739
9.2.2.173	Multiflow Role	739
9.2.2.174	Multiflow MIMO	739
9.2.2.175	Multiflow Timing	739
9.2.2.176	UL MIMO Reconfiguration	740
9.2.2.177	UL MIMO Information	740
9.2.2.178	UL MIMO Information To Modify	741
9.2.2.179	UL MIMO Removal	741
9.2.2.180	UL MIMO DL Control Channel Information	741
9.2.2.181	E-ROCH Power Offset	741
9.2.2.182	S-E-DPCCH Power Offset	742
9.2.2.183	Inter-stream Interference Compensation Index	742
9.2.2.184	Secondary Transport Block E-HICH Release Indicator	742
9.2.2.185	Further Enhanced UE DRX Information	742
9.2.2.186	Common E-DCH Preamble Control Information extension list	743
9.2.2.187	Common E-DCH Preamble Control Information extension	744
9.2.2.188	Common E-DCH AICH Information	744
9.2.2.189	Common E-RGCH Info	744
9.2.2.190	Common E-DCH HS-DPCCH Information for Concurrent TTI	744
9.2.2.191	Common E-DCH system info parameters for Concurrent TTI	745
9.2.2.192	Precoder weight set restriction	745
9.2.2.193	Multiflow Repetition Factors	745
9.2.2.194	E-DCH Decoupling Indication	746
9.2.2.195	DCH Enhancements Information Reconf	746
9.2.2.196	DCH Enhancements Information	746
9.2.2.197	DCH Enhancements Information to Modify	747
9.2.2.198	DCH Enhancements Information Removal	747
9.2.2.199	Gain Factors 10ms Mode	748
9.2.2.200	Extended E-DPCCH Power Offset	748
9.2.2.201	Radio Links without DPCH/F-DPCH Indication	748
9.2.2.202	UL DPCCH2 Reconfiguration	749
9.2.2.203	UL DPCCH2 Information	749
9.2.2.204	UL DPCCH2 Information To Modify	749
9.2.2.205	UL DPCCH2 Information Removal	749
9.2.2.206	CQI Feedback Cycle2 k	750
9.2.2.207	UE Measurement Forwarding	750
9.2.2.208	UE Measurement Value	750
9.2.2.209	TTI Update Indication	750
9.2.2.210	Activation Delay	750
9.2.2.211	Fast TTI switching Mode Supported	750
9.2.2.212	Fast TTI switching Mode Requested Synchronized	751
9.2.2.213	Fast TTI switching Mode Requested UnSynchronized	751
9.2.2.214	Downlink TPC enhancements Information	751
9.2.2.215	Downlink TPC enhancements Reconf	751
9.2.2.216	Downlink TPC enhancements Information Removal	752
9.2.2.217	TPC slot position	752
9.2.2.218	E-RNTI Set	752
9.2.3	TDD specific Parameters	752
9.2.3.1	Block STTD Indicator	752
9.2.3.2	Burst Type	753
9.2.3.3	CCTrCH ID	753
9.2.3.4	Cell Parameter ID	753
9.2.3.4A	Constant Value	753
9.2.3.4B	DL Timeslot ISCP	753
9.2.3.4C	DCH TDD Information	753
9.2.3.4D	DCHs TDD To Modify	754
9.2.3.4E	DL Timeslot Information	755
9.2.3.4F	DL Time Slot ISCP Info	755
9.2.3.4G	Cell Sync Burst Code	756
9.2.3.4H	Cell Sync Burst Code Shift	756
9.2.3.4I	CSB Measurement ID	756
9.2.3.4J	Cell Sync Burst Repetition Period	756
9.2.3.4K	Cell Sync Burst SIR	756
9.2.3.4L	Cell Sync Burst Timing	757
9.2.3.4La	Cell Sync Burst Timing LCR	757
9.2.3.4M	Cell Sync Burst Timing Threshold	757
9.2.3.4N	CSB Transmission ID	757
9.2.3.4O	DL Timeslot Information LCR	757
9.2.3.4P	DL Time Slot ISCP Info LCR	758
9.2.3.4Q	UpPCH Position LCR	758
9.2.3.5	DPCH ID	758
9.2.3.5a	DSCH ID	759
9.2.3.5b	DSCH Information Response	759
9.2.3.5A	DSCH TDD Information	759
9.2.3.5B	DwPCH Power	760
9.2.3.5C	Frame Adjustment Value	760
9.2.3.5D	IPDL TDD Parameters	760
9.2.3.5E	Max FPACH Power	760
9.2.3.5F	HS-DSCH TDD Information	760
9.2.3.5G	HS-DSCH TDD Information Response	762
9.2.3.5GA	HS-DSCH TDD Update Information	765
9.2.3.5Ga	HS-SCCH ID	765
9.2.3.5Gb	HS-SICH ID	765
9.2.3.5Gc	1.28 Mcps TDD Uplink Physical Channel Capability	765
9.2.3.5H	IPDL TDD Parameters LCR	766
9.2.3.5I	TSN-Length	766
9.2.3.5J	Extended HS-SCCH ID	766
9.2.3.5K	Extended HS-SICH ID	766
9.2.3.6	Max PRACH Midamble Shift	766
9.2.3.7	Midamble Shift And Burst Type	767
9.2.3.7A	Midamble Shift LCR	767
9.2.3.7Aa	Notification Indicator Length	768
9.2.3.7B	Number Of Cycles Per SFN Period	768
9.2.3.7C	Number Of Repetitions Per Cycle Period	768
9.2.3.7D	Number Of Subcycles Per Cycle Period	768
9.2.3.8	Paging Indicator Length	769
9.2.3.9	PCCPCH Power	769
9.2.3.10	PDSCH ID	769
9.2.3.11	PDSCH Set ID	769
9.2.3.11A	Primary CCPCH RSCP	769
9.2.3.11B	Primary CCPCH RSCP Delta	769
9.2.3.12	PUSCH ID	770
9.2.3.13	PUSCH Set ID	770
9.2.3.14	PRACH Midamble	770
9.2.3.14A	Reference Clock Availability	770
9.2.3.14B	Reference SFN Offset	770
9.2.3.15	Repetition Length	771
9.2.3.16	Repetition Period	771
9.2.3.17	SCH Time Slot	771
9.2.3.18	Sync Case	771
9.2.3.18A	Special Burst Scheduling	772
9.2.3.18B	SYNC_DL Code ID	772
9.2.3.18C	Sync Frame Number	772
9.2.3.18D	Synchronisation Report Characteristics	772
9.2.3.18E	Synchronisation Report Type	773
9.2.3.18F	TDD ACK NACK Power Offset	774
9.2.3.19	TDD Channelisation Code	774
9.2.3.19a	TDD Channelisation Code LCR	774
9.2.3.19A	TDD DPCH Offset	774
9.2.3.19B	TDD DL Code Information	775
9.2.3.19C	TDD DL Code Information LCR	775
9.2.3.19D	TDD DL DPCH Time Slot Format LCR	775
9.2.3.20	TDD Physical Channel Offset	776
9.2.3.21	TDD TPC DL Step Size	776
9.2.3.21a	TDD TPC UL Step Size	776
9.2.3.21A	TDD UL Code Information	776
9.2.3.21B	TDD UL Code Information LCR	777
9.2.3.21C	TDD UL DPCH Time Slot Format LCR	777
9.2.3.22	TFCI Coding	777
9.2.3.22a	Timing Adjustment Value	777
9.2.3.22b	Timing Adjustment Value LCR	778
9.2.3.22A	Timing Advance Applied	778
9.2.3.23	Time Slot	778
9.2.3.24	Time Slot Direction	778
9.2.3.24A	Time Slot LCR	778
9.2.3.24B	Time Slot LCR Extension	779
9.2.3.25	Time Slot Status	779
9.2.3.26	Transmission Diversity Applied	779
9.2.3.26A	UL Timeslot ISCP	779
9.2.3.26B	UL PhysCH SF Variation	779
9.2.3.26C	UL Timeslot Information	779
9.2.3.26D	UL Time Slot ISCP Info	780
9.2.3.26E	UL Timeslot Information LCR	780
9.2.3.26F	UL Time Slot ISCP Info LCR	780
9.2.3.26G	Uplink Synchronisation Frequency	781
9.2.3.26H	Uplink Synchronisation Step Size	781
9.2.3.27	USCH ID	781
9.2.3.28	USCH Information	781
9.2.3.29	USCH Information Response	782
9.2.3.30	SCTD Indicator	782
9.2.3.31	PLCCH Information	782
9.2.3.32	PLCCH Sequence Number	783
9.2.3.33	Common Physical Channel ID 7.68Mcps	783
9.2.3.34	TDD Channelisation Code 7.68Mcps	783
9.2.3.35	Midamble Shift And Burst Type 7.68Mcps	783
9.2.3.36	Common Physical Channel Status Information 7.68Mcps	784
9.2.3.37	Neighbouring TDD Cell Measurement Information 7.68Mcps	784
9.2.3.38	UL Timeslot Information 7.68Mcps TDD	784
9.2.3.39	DL Timeslot Information 7.68Mcps TDD	785
9.2.3.40	TDD UL Code Information 7.68Mcps TDD	785
9.2.3.41	TDD DL Code Information 7.68Mcps TDD	785
9.2.3.42	DPCH ID 7.68Mcps	786
9.2.3.43	PDSCH ID 7.68Mcps	786
9.2.3.44	Max E-RUCCH Midamble Shift	786
9.2.3.45	E-PUCH Information	786
9.2.3.45a	E-PUCH Information LCR	787
9.2.3.46	E-TFCS Information TDD	788
9.2.3.47	E-DCH MAC-d Flows Information TDD	789
9.2.3.48	E-DCH Non-scheduled Grant Information TDD	789
9.2.3.48a	E-DCH Non-scheduled Grant Information LCR TDD	790
9.2.3.49	E-DCH TDD Information	791
9.2.3.49a	E-DCH TDD Information LCR	792
9.2.3.50	E-DCH TDD Information Response	794
9.2.3.51	E-AGCH ID TDD	794
9.2.3.51a	E-HICH ID TDD	795
9.2.3.51b	Extended E-HICH ID TDD	795
9.2.3.52	E-DCH TDD Information to Modify	795
9.2.3.53	E-DCH Grant Type TDD	796
9.2.3.54	Timeslot Resource Related Information	797
9.2.3.54a	Timeslot Resource Related Information LCR	797
9.2.3.55	Power Resource Related Information	797
9.2.3.56	E-PUCH Offset	797
9.2.3.57	E-DCH TDD Maximum Bitrate	797
9.2.3.58	LTGI Presence	797
9.2.3.59	E-HICH Time Offset	798
9.2.3.59a	E-HICH Time Offset LCR	798
9.2.3.60	E-DCH TDD Capacity Consumption Law	798
9.2.3.61	E-DCH HARQ Power Offset TDD	798
9.2.3.61a	E-DCH MAC-d Flow Retransmission Timer	798
9.2.3.62	SNPL Reporting Type	799
9.2.3.63	Maximum Generated Received Total Wide Band Power in Other Cells	799
9.2.3.64	E-DCH Non-scheduled Grant Information 7.68Mcps TDD	799
9.2.3.65	E-DCH TDD Information 7.68Mcps	799
9.2.3.66	E-DCH TDD Maximum Bitrate 7.68Mcps	800
9.2.3.67	E-DCH Physical Layer Category LCR	800
9.2.3.67A	Extended E-DCH Physical Layer Category LCR	800
9.2.3.67B	Multi-Carrier E-DCH Physical Layer Category LCR	800
9.2.3.68	E-HICH Type	800
9.2.3.69	Maximum Target Received Total Wide Band Power LCR	801
9.2.3.70	MBSFN Only Mode Indicator	801
9.2.3.71	MBSFN Only Mode Capability	801
9.2.3.72	HS-DSCH Common System Information LCR	801
9.2.3.73	HS-DSCH Paging System Information LCR	803
9.2.3.74	HS-DSCH Common System Information Response LCR	804
9.2.3.75	HS-DSCH Paging System Information Response LCR	805
9.2.3.76	Common MAC Flow ID LCR	806
9.2.3.77	HSDPA Associated PICH Information LCR	806
9.2.3.78	Common MAC Flows To Delete LCR	807
9.2.3.79	Common E-DCH System Information LCR	807
9.2.3.80	Common E-DCH System Information Response LCR	809
9.2.3.81	Common E-DCH MAC-d Flow Specific Information LCR	809
9.2.3.82	Enhanced UE DRX Information LCR	810
9.2.3.83	Common E-PUCH Information LCR	810
9.2.3.84	Common E-RNTI Information LCR	811
9.2.3.85	Paging MAC Flows To Delete LCR	812
9.2.3.86	Common E-DCH MAC-d Flows To Delete LCR	812
9.2.3.87	Common E-DCH MAC-d Flow ID LCR	812
9.2.3.88	HS-SCCH ID LCR	813
9.2.3.89	BCCH Specific HS-DSCH RNTI Information LCR	813
9.2.3.90	MAC-es Maximum Bit Rate LCR	813
9.2.3.91	Semi-Persistent scheduling Capability LCR	813
9.2.3.92	Continuous Packet Connectivity DRX Capability LCR	813
9.2.3.93	Continuous Packet Connectivity DRX Information LCR	814
9.2.3.94	Continuous Packet Connectivity DRX Information To Modify LCR	814
9.2.3.95	Continuous Packet Connectivity DRX Information Response LCR	815
9.2.3.96	HS-DSCH Semi-Persistent scheduling Information LCR	816
9.2.3.96a	HS-DSCH Semi-Persistent scheduling Information to modify LCR	817
9.2.3.97	E-DCH Semi-Persistent scheduling Information LCR	819
9.2.3.97a	E-DCH Semi-Persistent scheduling Information to modify LCR	820
9.2.3.98	HS-DSCH Semi-Persistent scheduling Information Response LCR	820
9.2.3.99	E-DCH Semi-Persistent scheduling Information Response LCR	822
9.2.3.100	HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR	823
9.2.3.101	E-DCH Semi-Persistent scheduling Deactivate Indicator LCR	823
9.2.3.102	Idle Interval Information	823
9.2.3.103	HS-SICH Reference Signal Information	824
9.2.3.104	UE Selected MBMS Service Information	825
9.2.3.105	Best Cell Portions LCR	825
9.2.3.106	Cell Portion Capability LCR	826
9.2.3.107	Cell Portion LCR ID	826
9.2.3.108	Number Of Reported Cell Portions LCR	826
9.2.3.109	TS0 Capability LCR	826
9.2.3.110	UE TS0 Capability LCR	826
9.2.3.111	DCH Measurement Occasion Information	827
9.2.3.112	Multi-Carrier E-DCH Information LCR	828
9.2.3.113	Multi-Carrier E-DCH Transport Bearer Mode LCR	828
9.2.3.114	Multi-Carrier E-DCH Information Response LCR	828
9.2.3.115	Cell Capability Container TDD LCR	829
9.2.3.116	MU-MIMO Information	830
9.2.3.117	MU-MIMO Information To Reconfigure	831
9.2.3.118	MU-MIMO Information Response	831
9.2.3.119	MU-MIMO Capability Container	832
9.2.3.120	MU-MIMO Indicator	832
9.2.3.121	MU-MIMO Usage Indicator	833
9.2.3.122	Adaptive Special Burst Power Capability LCR	833
9.2.3.123	In Sync Indication Information LCR	833
9.2.3.124	AOA per Cell Portion LCR	833
9.2.3.125	UE RF Band Capability LCR	834
9.3	Message and Information Element Abstract Syntax (with ASN.1)	835
9.3.0	General	835
9.3.1	Usage of Private Message mechanism for non-standard use	835
9.3.2	Elementary Procedure Definitions	835
9.3.3	PDU Definitions	854
9.3.4	Information Elements Definitions	1100
9.3.5	Common Definitions	1326
9.3.6	Constant Definitions	1327
9.3.7	Container Definitions	1354
9.4	Message Transfer Syntax	1359
9.5	Timers	1359
10	Handling of Unknown, Unforeseen and Erroneous Protocol Data	1359
10.1	General	1359
10.2	Transfer Syntax Error	1359
10.3	Abstract Syntax Error	1360
10.3.1	General	1360
10.3.2	Criticality Information	1360
10.3.3	Presence Information	1361
10.3.4	Not comprehended IE/IE group	1361
10.3.4.1	Procedure ID	1361
10.3.4.1A	Type of Message	1361
10.3.4.2	IEs Other Than the Procedure ID and Type of Message	1361
10.3.5	Missing IE or IE Group	1363
10.3.6	IEs or IE Groups Received in Wrong Order or With Too Many Occurrences or Erroneously Present	1364
10.4	Logical Error	1364
10.5	Exceptions	1365
Annex A (normative):	Allocation and Pre-emption of Radio Links in the Node B	1366
A.1	Deriving Allocation Information for a Radio Link	1366
A.1.1	Establishment of a New Radio Link	1366
A.1.2	Modification of an Existing Radio Link	1366
A.2	Deriving Retention Information for a Radio Link	1367
A.3	The Allocation/Retention Process	1368
A.4	The Pre-emption Process	1368
Annex B (informative):	Measurement Reporting	1369
Annex C (informative):	Guidelines for Usage of the Criticality Diagnostics IE	1373
C.1	EXAMPLE MESSAGE Layout	1373
C.2	Example on a Received EXAMPLE MESSAGE	1374
C.3	Content of Criticality Diagnostics	1375
C.3.1	Example 1	1375
C.3.2	Example 2	1376
C.3.3	Example 3	1377
C.3.4	Example 4	1378
C.3.5	Example 5	1379
C.4	ASN.1 of EXAMPLE MESSAGE	1380
Annex D (normative):	IB_SG_DATA Encoding	1382
D.1	Overall Description	1382
D.2	IB_SG_DATA Encoding Variant 1	1382
D.3	IB_SG_DATA Encoding Variant 2	1382
Annex E (informative):	Reporting the status of resources used for frequency (1.28 Mcps TDD only)	1383
Annex F (informative):	Change History	1384


Foreword
This Technical Specification has been produced by the 3GPP.
The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x	the first digit:
1	presented to TSG for information;
2	presented to TSG for approval;
3	Indicates TSG approved document under change control.
y	the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
z	the third digit is incremented when editorial only changes have been incorporated in the document.

1	Scope
The present document specifies the radio network layer signalling protocol called Node B Application Part (NBAP) specification to be used for Control Plane over Iub Interface.
2	References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or nonspecific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]	3GPP TS 25.401: "UTRAN Overall Description".
[2]	3GPP TS 25.426: "UTRAN Iur and Iub Interface Data Transport & Transport Signalling for DCH Data Streams".
[3]	CCITT Recommendation X.731 (1992-01): "Information Technology – Open Systems Interconnection – Systems Management: State Management function".
[4]	3GPP TS 25.215: "Physical layer; Measurements (FDD)".
[5]	3GPP TS 25.225: "Physical layer; Measurements (TDD)".
[6]	3GPP TS 25.430: "UTRAN Iub General Aspect and Principle".
[7]	3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)".
[8]	3GPP TS 25.212: "Multiplexing and channel coding (FDD)".
[9]	3GPP TS 25.213: "Spreading and modulation (FDD)".
[10]	3GPP TS 25.214: "Physical layer procedures (FDD)".
[11]	ITUT Recommendation X.691, (2002-07): "Information technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)".
[12]	ITUT Recommendation X.680, (2002-07): "Information Technology - Abstract Syntax Notation One (ASN.1):Specification of basic notation".
[13]	ITUT Recommendation X.681, (2002-07): "Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification".
[14]	3GPP TS 25.104: "UTRA (BS) FDD; Radio Transmission and Reception".
[15]	3GPP TS 25.105: "UTRA (BS) TDD; Radio Transmission and Reception".
[16]	3GPP TS 25.427: "UTRAN Iur/Iub Interface User Plane Protocol for DCH Data Stream".
[17]	3GPP TS 25.402: "Synchronisation in UTRAN Stage2".
[18]	3GPP TS 25.331: "RRC Protocol Specification".
[19]	3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels[TDD]".
[20]	3GPP TS 25.223: "Spreading and modulation (TDD)".
[21]	3GPP TS 25.224: "Physical Layer Procedures (TDD)".
[22]	3GPP TS 25.133: "Requirements for support of Radio Resource management (FDD)".
[23]	3GPP TS 25.123: "Requirements for support of Radio Resource management (TDD)".
[24]	3GPP TS 25.435: "UTRAN Iub Interface: User Plane Protocols for Common Transport Channel Data Streams".
[25]	3GPP TS 25.302: "Services Provided by the Physical Layer".
[26]	3GPP TR 25.921 (version.7.0.0): "Guidelines and Principles for Protocol Description and Error Handling".
[27]	ICD-GPS-200: "Navstar GPS Space Segment/Navigation User Interface".
[28]	RTCM-SC104: "RTCM Recommended Standards for Differential GNSS Service (v.2.2)".
[29]	IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (IPv6) Specification".
[30]	IETF RFC 768 (1980-08): "User Datagram Protocol".
[31]	3GPP TS 25.434: "UTRAN Iub Interface Data Transport & Transport Signalling for Common Transport Channel Data Streams ".
[32]	3GPP TS 25.321: "MAC protocol specification".
[33]	3GPP TS 25.306: "UE Radio Access capabilities".
[34]	3GPP TS 25.222: "Multiplexing and Channel Coding (TDD)".
[35]	IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
[36]	IETF RFC 2475 (1998-12): "An Architecture for Differentiated Services".
[37]	3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode".
[38]	3GPP TS 25.319: "Enhanced Uplink; Overall description; Stage 2".
[39]	Galileo OS Signal in Space ICD (OS SIS ICD), Issue 1.2. February 2014, European Union.
[40]	Void.
[41]	IETF RFC 3376 (2002-12): "Internet Group Management Protocol, Version 3".
[42]	IETF RFC 3810 (2004-06): "Multicast Listener Discovery Version 2 (MLDv2) for IPv6".
[43]	IS-GPS-200, Revision D, Navstar GPS Space Segment/Navigation User Interfaces, March 7th, 2006.
[44]	IS-GPS-705, Navstar GPS Space Segment/User Segment L5 Interfaces, (2005-09-22).
[45]	IS-GPS-800, Navstar GPS Space Segment/User Segment L1C Interfaces, (2008-03-31).
[46]	Specification for the Wide Area Augmentation System (WAAS), US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001.
[47]	IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS, Ver.1.0, (2008-06-17).
[48]	Global Navigation Satellite System GLONASS Interface Control Document, Version 5, 2002.
[49]	3GPP TS 25.308: "High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2"
[50]	3GPP TS 36.133: "Requirements for support of radio resource management".
[51]	BDS-SIS-ICD-2.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal (Version 1.0)", December 2013.
[52]	3GPP TS 25.300: "Universal Terrestrial Radio Access Network (UTRAN); General description; Stage 2".
3	Definitions, Symbols and Abbreviations
3.1	Definitions
For the purposes of the present document, the following terms and definitions apply.
CRNC Communication Context: The CRNC Communication Context contains the necessary information for the CRNC for communication with a specific UE. The CRNC Communication Context is identified by the CRNC Communication Context ID.
Elementary Procedure: The NBAP protocol consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between the CRNC and the Node B.
An EP consists of an initiating message and possibly a response message.
Two kinds of EPs are used:
-	Class 1: Elementary Procedures with response (success or failure).
-	Class 2: Elementary Procedures without response.
For Class 1 EPs, the types of responses can be as follows:
Successful
-	A signalling message explicitly indicates that the elementary procedure has been successfully completed with the receipt of the response.
Unsuccessful
-	A signalling message explicitly indicates that the EP failed.
Class 2 EPs are considered always successful.
Node B Communication Context: The Node B Communication Context contains the necessary information for the Node B for communication with a specific UE. The Node B Communication Context is created by the Radio Link Setup procedure and deleted by the Radio Link Deletion procedure when deleting the last Radio Link within the Node B Communication Context. The Node B Communication Context is identified by the Node B Communication Context ID.
Prepared Reconfiguration: A Prepared Reconfiguration exists when the Synchronised Radio Link Reconfiguration Preparation procedure has been completed successfully. The Prepared Reconfiguration does not exist anymore only after either of the procedures Synchronised Radio Link Reconfiguration Commit or Synchronised Radio Link Reconfiguration Cancellation has been completed. In particular, the Prepared Reconfiguration still exists if the object (e.g. Radio Link) concerned by the Synchronised Radio Link Reconfiguration (e.g. in the case of an HS-DSCH Setup) is removed, but the Node B Communication Context still exists.
3.2	Symbols
Void.
3.3	Abbreviations
For the purposes of the present document, the following abbreviations apply:
A-GPS	Assisted GPS
AICH	Acquisition Indicator Channel
ALCAP	Access Link Control Application Part
ASN.1	Abstract Syntax Notation One
BCCH	Broadcast Control Channel
BDS	BeiDou Navigation Satellite System
CCPCH	Common Control Physical Channel
CFN	Connection Frame Number
CLTD	Closed Loop Transmit Diversity
CM	Compressed Mode
CPICH	Common Pilot Channel
CRNC	Controlling Radio Network Controller
DBDS	Differential BDS
DCH	Dedicated Channel
DGANSS	Differential GANSS
DGPS	Differential GPS
DL	Downlink
DPCCH	Dedicated Physical Control Channel
DPCH	Dedicated Physical Channel
DPDCH	Dedicated Physical Data Channel
DSCH	Downlink Shared Channel
E-AGCH	E-DCH Absolute Grant Channel
E-DCH	Enhanced UL DCH
EGNOS	European Geostationary Navigation Overlay Service
E-HICH	E-DCH HARQ Acknowledgement Indicator Channel
E-PUCH	Enhanced Uplink Physical Channel (TDD only)
E-RNTI	E-DCH RNTI
E-RUCCH	E-DCH Random Access Uplink Control Channel (TDD only)
E-TFCI	E-DCH Transport Format Combination Indicator
E-UCCH	E-DCH Uplink Control Channel (TDD only)
FACH 	Forward Access Channel
FDD	Frequency Division Duplex
F-DPCH	Fractional DPCH
FP	Frame Protocol
FPACH	Fast Physical Access Channel (TDD only)
F-TPICH	Fractional Transmitted Precoding Indicator Channel
GAGAN	GPS Aided Geo Augmented Navigation
GANSS	Galileo and Additional Navigation Satellite Systems
GLONASS	GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System)
GNSS	Global Navigation Satellite System
GPS	Global Positioning System
HSDPA	High Speed Downlink Packet Access
HS-DSCH	High Speed Downlink Shared Channel
HS-PDSCH	High Speed Physical Downlink Shared Channel
HS-SCCH	High Speed Shared Control Channel
HS-SICH	High Speed Shared Information Channel
ICD	Interface Control Document
IMB	Integrated Mobile Broadcast
IP	Internet Protocol
IPDL	Idle Periods in the DownLink
ISCP	Interference Signal Code Power
L1	Layer 1
L2	Layer 2
MBMS	Multimedia Broadcast Multicast Service
MBSFN	MBMS over a Single Frequency Network
MFN	Multicast Frame Number
MIB	Master Information Block
MICH	MBMS Notification Indicator Channel
MIMO	Multiple Input Multiple Output
MSAS	Multi-functional Satellite Augmentation System
NAICS	Network Assisted Interference Cancellation and Suppression
NBAP	Node B Application Part
NI	MBMS Notification Indicator
O&M	Operation and Maintenance
PCCPCH	Primary Common Control Physical Channel
PCH	Paging Channel
PDSCH	Physical Downlink Shared Channel
PICH	Paging Indication Channel
PLCCH	Physical Layer Common Control Channel
PUSCH	Physical Uplink Shared Channel
QZSS	Quasi-Zenith Satellite System
RACH	Random Access Channel
RL	Radio Link
RLS	Radio Link Set
RNC	Radio Network Controller
RRC	Radio Resource Control
SB	Scheduling Block
SBAS	Satellite Based Augmentation System
SCCPCH	Secondary Common Control Physical Channel
SCH	Synchronisation Channel
SCTD	Space Code Transmit Diversity
S-DPCCH	Secondary Dedicated Physical Control Channel
SIB	System Information Block
SRNC	Serving Radio Network Controller
STTD	Space Time Transmit Diversity
TDD	Time Division Duplex
TFC	Transport Format Combination
TFCI	Transport Format Combination Indicator
TFCS	Transport Format Combination Set
TFS	Transport Format Set
TPC	Transmit Power Control
TSTD	Time Switched Transmit Diversity
UARFCN	UTRA Absolute Radio Frequency Channel Number
UDP	User Datagram Protocol
UE	User Equipment
UL	Uplink
UMTS	Universal Mobile Telecommunications System
USCH	Uplink Shared Channel
UTC	Universal Coordinated Time
UTRA	Universal Terrestrial Radio Access
UTRAN	Universal Terrestrial Radio Access Network
WAAS	Wide Area Augmentation System
4	General
4.1	Procedure Specification Principles
The principle for specifying the procedure logic is to specify the functional behaviour of the Node B exactly and completely. The CRNC functional behaviour is left unspecified. The Reset procedure is an exception from this principle.
The following specification principles have been applied for the procedure text in subclause 8:
-	The procedure text discriminates between:
1)	Functionality which "shall" be executed
	The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value. 
2)	Functionality which "shall, if supported" be executed
	The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality. 
-	Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. For requirements on including Criticality Diagnostics IE, see section 10. For examples on how to use the Criticality Diagnostics IE, see Annex C.
4.2	Forwards and Backwards Compatibility
The forwards and backwards compatibility of the protocol is assured by a mechanism in which all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version.
4.3	Specification Notations
For the purposes of the present document, the following notations apply:
[FDD]	This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD.
[TDD]	This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 3.84Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 3.84Mcps TDD and 1.28Mcps TDD.
[3.84Mcps TDD]	This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD.
[1.28Mcps TDD]	This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD.
[7.68Mcps TDD]	This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD.
[FDD - …]	This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs.
[TDD - …]	This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs.
[3.84Mcps TDD - …]	This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs.
[1.28Mcps TDD - …]	This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs.
[7.68Mcps TDD - …]	This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs.
[3.84Mcps TDD IMB -…]	This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD IMB]" applies only to 3.84Mcps TDD IMB. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD IMB]" and the section following the heading applies only to 3.84Mcps TDD IMB.
Procedure	When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Radio Link Setup procedure.
Message	When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message.
IE	When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Transport Format Set IE.
Value of an IE	When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)".
5	NBAP Services
5.1	Parallel Transactions
Unless explicitly indicated in the procedure description, at any instance in time one protocol peer shall have a maximum of one ongoing dedicated NBAP procedure related to a certain Node B Communication Context.
6	Services Expected from Signalling Transport
NBAP requires an assured in-sequence delivery service from the signalling bearer, and notification if the assured in-sequence delivery service is no longer available.
7	Functions of NBAP
The NBAP protocol provides the following functions:
-	Cell Configuration Management. This function gives the CRNC the possibility to manage the cell configuration information in a Node B.
-	Common Transport Channel Management. This function gives the CRNC the possibility to manage the configuration of Common Transport Channels in a Node B.
-	System Information Management. This function gives the CRNC the ability to manage the scheduling of System Information to be broadcast in a cell.
-	Resource Event Management. This function gives the Node B the ability to inform the CRNC about the status of Node B resources.
-	Configuration Alignment. This function gives the CRNC and the Node B the possibility to verify and enforce that both nodes have the same information on the configuration of the radio resources.
-	Measurements on Common Resources. This function allows the CRNC to initiate measurements on common resources in the Node B. The function also allows the Node B to report the result of the measurements.
-	Radio Link Management. This function allows the CRNC to manage radio links using dedicated resources in a Node B.
-	Radio Link Supervision. This function allows the CRNC to report failures and restorations of a Radio Link.
-	Compressed Mode Control [FDD]. This function allows the CRNC to control the usage of compressed mode in a Node B.
-	Measurements on Dedicated Resources. This function allows the CRNC to initiate measurements on dedicated resources in the Node B. The function also allows the Node B to report the result of the measurements.
-	DL Power Drifting Correction [FDD]. This function allows the CRNC to adjust the DL power level of one or more Radio Links in order to avoid DL power drifting between the Radio Links.
-	Reporting of General Error Situations. This function allows reporting of general error situations, for which function specific error messages have not been defined.
-	Physical Shared Channel Management. This function allows the CRNC to manage physical resources in the Node B belonging to High Speed Downlink Shared Channels and High Speed Shared Control Channels [TDD - and High Speed Shared Indication Channels and Shared Channels (USCH/DSCH)].
-	DL Power Timeslot Correction [TDD]. This function enables the Node B to apply an individual offset to the transmission power in each timeslot according to the downlink interference level at the UE.
-	Cell Synchronisation [1.28 Mcps TDD and 3.84 Mcps TDD]. This function allows the synchronisation of cells or Node Bs via the air interface.
-	Information Exchange. This function allows the CRNC to initiate information provision from the Node B. The function also allows the Node B to report the requested information.
-	Bearer Rearrangement. This function allows the Node B to indicate the need for bearer re-arrangement for a Node B Communication Context. The function also allows the CRNC to re-arrange bearers for a Node B Communication Context.
-	MBMS Notification. This function allows the CRNC to send MBMS Notification indicators to the Node B to be broadcasted in a cell.
- UE Status Notification [FDD and 1.28 Mcps TDD]. This function allows the CRNC to update UE related information stored in the Node B.
- Exchanging information about the secondary UL frequency. This function allows the CRNC to transfer information about the secondary UL frequency to the Node B and the Node B to transfer information about the secondary UL frequency to SRNC in Dual-Cell E-DCH operation.
The mapping between the above functions and NBAP elementary procedures is shown in the table below.
Table 1: Mapping between functions and NBAP elementary procedures
Function
Elementary Procedure(s)
Cell Configuration Management
a) Cell Setup
b) Cell Reconfiguration
c) Cell Deletion
Common Transport Channel Management
a) Common Transport Channel Setup
b) Common Transport Channel Reconfiguration
c) Common Transport Channel Deletion
System Information Management
System Information Update
Resource Event Management
a) Block Resource
b) Unblock Resource
c) Resource Status Indication
Configuration Alignment
a) Audit Required
b) Audit
c) Reset
Measurements on Common Resources
a) Common Measurement Initiation
b) Common Measurement Reporting
c) Common Measurement Termination
d) Common Measurement Failure
Radio Link Management.
a) Radio Link Setup
b) Radio Link Addition
c) Radio Link Deletion
d) Unsynchronised Radio Link Reconfiguration
e) Synchronised Radio Link Reconfiguration Preparation
f) Synchronised Radio Link Reconfiguration Commit
g) Synchronised Radio Link Reconfiguration Cancellation
h) Radio Link Pre-emption
i) Radio Link Activation
j) Radio Link Parameter Update
Radio Link Supervision.
a) Radio Link Failure
b) Radio Link Restoration
Compressed Mode Control [FDD]
a) Radio Link Setup
b) Radio Link Addition
c) Compressed Mode Command
d) Unsynchronised Radio Link Reconfiguration
e) Synchronised Radio Link Reconfiguration Preparation
f) Synchronised Radio Link Reconfiguration Commit
g) Synchronised Radio Link Reconfiguration Cancellation
Measurements on Dedicated Resources
a) Dedicated Measurement Initiation
b) Dedicated Measurement Reporting
c) Dedicated Measurement Termination
d) Dedicated Measurement Failure
DL Power Drifting Correction [FDD]
Downlink Power Control
Reporting of General Error Situations
Error Indication
Physical Shared Channel Management
Physical Shared Channel Reconfiguration
DL Power Timeslot Correction [TDD]
Downlink Power Timeslot Control
Cell Synchronisation [1.28 Mcps TDD and 3.84 Mcps TDD]
a) Cell Synchronisation Initiation
b) Cell Synchronisation Reconfiguration
c) Cell Synchronisation Reporting
d) Cell Synchronisation Termination
e) Cell Synchronisation Failure
f) Cell Synchronisation Adjustment
Information Exchange
a) Information Exchange Initiation
b) Information Reporting
c) Information Exchange Termination
d) Information Exchange Failure
Bearer Re-arrangement
a) Bearer Re-arrangement Indication
b) Unsynchronised Radio Link Reconfiguration
c) Synchronised Radio Link Reconfiguration Preparation
d) Synchronised Radio Link Reconfiguration Commit
e) Synchronised Radio Link Reconfiguration Cancellation
MBMS Notification
a) MBMS Notification Update
UE Status Notification [FDD and 1.28 Mcps TDD]
a) UE Status Update
b) UE Status Update Confirmation
Exchanging information about the secondary UL frequency
a) Secondary UL Frequency Reporting
b) Secondary UL Frequency Update

8	NBAP Procedures
8.1	Elementary Procedures
NBAP procedures are divided into common procedures and dedicated procedures.
-	NBAP common procedures are procedures that request initiation of a Node B Communication Context for a specific UE in Node B or are not related to a specific UE. NBAP common procedures also incorporate logical O&M (TS 25.401 [1]) procedures.
-	NBAP dedicated procedures are procedures that are related to a specific Node B Communication Context in Node B. This Node B Communication Context is identified by a Node B Communication Context identity.
The two types of procedures may be carried on separate signalling links.
In the following tables, all EPs are divided into Class 1 and Class 2 EPs:
Table 2: Class 1
Elementary Procedure
Message
Successful Outcome
Unsuccessful Outcome


Response message
Response message
Cell Setup
CELL SETUP REQUEST
CELL SETUP RESPONSE
CELL SETUP FAILURE
Cell Reconfiguration
CELL RECONFIGURATION REQUEST
CELL RECONFIGURATION RESPONSE
CELL RECONFIGURATION FAILURE
Cell Deletion
CELL DELETION REQUEST
CELL DELETION RESPONSE

Common Transport Channel Setup
COMMON TRANSPORT CHANNEL SETUP REQUEST
COMMON TRANSPORT CHANNEL SETUP RESPONSE
COMMON TRANSPORT CHANNEL SETUP FAILURE
Common Transport Channel Reconfiguration
COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST 
COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE
COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE
Common Transport Channel Deletion
COMMON TRANSPORT CHANNEL DELETION REQUEST
COMMON TRANSPORT CHANNEL DELETION RESPONSE

Physical Shared Channel Reconfiguration
PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST 
PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE
PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE
Audit
AUDIT REQUEST 
AUDIT RESPONSE
AUDIT FAILURE
Block Resource
BLOCK RESOURCE REQUEST
BLOCK RESOURCE RESPONSE
BLOCK RESOURCE FAILURE
Radio Link Setup
RADIO LINK SETUP REQUEST
RADIO LINK SETUP RESPONSE
RADIO LINK SETUP FAILURE
System Information Update 
SYSTEM INFORMATION UPDATE REQUEST
SYSTEM INFORMATION UPDATE RESPONSE
SYSTEM INFORMATION UPDATE FAILURE
Common Measurement Initiation
COMMON MEASUREMENT INITIATION REQUEST
COMMON MEASUREMENT INITIATION RESPONSE
COMMON MEASUREMENT INITIATION FAILURE
Radio Link Addition
RADIO LINK ADDITION REQUEST
RADIO LINK ADDITION RESPONSE
RADIO LINK ADDITION FAILURE
Radio Link Deletion
RADIO LINK DELETION REQUEST
RADIO LINK DELETION RESPONSE

Synchronised Radio Link Reconfiguration Preparation
RADIO LINK RECONFIGURATION PREPARE
RADIO LINK RECONFIGURATION READY
RADIO LINK RECONFIGURATION FAILURE
Unsynchronised Radio Link Reconfiguration
RADIO LINK RECONFIGURATION REQUEST
RADIO LINK RECONFIGURATION RESPONSE
RADIO LINK RECONFIGURATION FAILURE
Dedicated Measurement Initiation
DEDICATED MEASUREMENT INITIATION REQUEST
DEDICATED MEASUREMENT INITIATION RESPONSE
DEDICATED MEASUREMENT INITIATION FAILURE
Reset
RESET REQUEST
RESET RESPONSE

Cell Synchronisation Initiation [TDD]
CELL SYNCHRONISATION INITIATION REQUEST
CELL SYNCHRONISATION INITIATION RESPONSE
CELL SYNCHRONISATION INITIATION FAILURE
Cell Synchronisation Reconfiguration [TDD]
CELL SYNCHRONISATION RECONFIGURATION REQUEST
CELL SYNCHRONISATION RECONFIGURATION RESPONSE
CELL SYNCHRONISATION RECONFIGURATION FAILURE
Cell Synchronisation Adjustment [TDD]
CELL SYNCHRONISATION ADJUSTMENT REQUEST
CELL SYNCHRONISATION ADJUSTMENT RESPONSE
CELL SYNCHRONISATION ADJUSTMENT FAILURE
Information Exchange Initiation
INFORMATION EXCHANGE INITIATION REQUEST
INFORMATION EXCHANGE INITIATION RESPONSE
INFORMATION EXCHANGE INITIATION FAILURE
UE Status Update Confirmation
UE STATUS UPDATE CONFIRM REQUEST
UE STATUS UPDATE CONFIRM RESPONSE


Table 3: Class 2
Elementary Procedure
Message
Resource Status Indication
RESOURCE STATUS INDICATION
Audit Required
AUDIT REQUIRED INDICATION
Common Measurement Reporting
COMMON MEASUREMENT REPORT
Common Measurement Termination
COMMON MEASUREMENT TERMINATION REQUEST
Common Measurement Failure
COMMON MEASUREMENT FAILURE INDICATION
Synchronised Radio Link Reconfiguration Commit
RADIO LINK RECONFIGURATION COMMIT
Synchronised Radio Link Reconfiguration Cancellation
RADIO LINK RECONFIGURATION CANCEL
Radio Link Failure
RADIO LINK FAILURE INDICATION
Radio Link Restoration
RADIO LINK RESTORE INDICATION
Dedicated Measurement Reporting
DEDICATED MEASUREMENT REPORT
Dedicated Measurement Termination
DEDICATED MEASUREMENT TERMINATION REQUEST
Dedicated Measurement Failure
DEDICATED MEASUREMENT FAILURE INDICATION
Downlink Power Control [FDD]
DL POWER CONTROL REQUEST
Compressed Mode Command [FDD]
COMPRESSED MODE COMMAND
Unblock Resource
UNBLOCK RESOURCE INDICATION
Error Indication
ERROR INDICATION
Downlink Power Timeslot Control [TDD]
DL POWER TIMESLOT CONTROL REQUEST
Radio Link Pre-emption
RADIO LINK PREEMPTION REQUIRED INDICATION
Cell Synchronisation Reporting [TDD]
CELL SYNCHRONISATION REPORT
Cell Synchronisation Termination [TDD]
CELL SYNCHRONISATION TERMINATION REQUEST
Cell Synchronisation Failure [TDD]
CELL SYNCHRONISATION FAILURE INDICATION
Information Reporting
INFORMATION REPORT
Information Exchange Termination
INFORMATION EXCHANGE TERMINATION REQUEST
Information Exchange Failure
INFORMATION EXCHANGE FAILURE INDICATION
Bearer Re-arrangement
BEARER REARRANGEMENT INDICATION
Radio Link Activation
RADIO LINK ACTIVATION COMMAND
Radio Link Parameter Update 
RADIO LINK PARAMETER UPDATE INDICATION
MBMS Notification Update
MBMS NOTIFICATION UPDATE COMMAND
UE Status Update [FDD and 1.28 Mcps TDD]
UE STATUS UPDATE COMMAND
Secondary UL Frequency Reporting
SECONDARY UL FREQUENCY REPORT
Secondary UL Frequency Update
SECONDARY UL FREQUENCY UPDATE INDICATION

8.2	NBAP Common Procedures
8.2.1	Common Transport Channel Setup
8.2.1.1	General
This procedure is used for establishing the necessary resources in Node B, regarding Secondary CCPCH, PICH, PRACH, AICH [FDD], FACH, PCH, MICH, RACH, BCH, E-RUCCH [3.84 Mcps and 7.68 Mcps TDD], PLCCH [1.28Mcps TDD] and FPACH [1.28Mcps TDD].
8.2.1.2	Successful Operation

Figure 1: Common Transport Channel Setup procedure, Successful Operation
The procedure is initiated with a COMMON TRANSPORT CHANNEL SETUP REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
One message can configure only one of the following combinations:
-	[FDD - one Secondary CCPCH, and FACHs, BCH, PCH, PICH and MICH related to that Secondary CCPCH], or
-	[TDD - one CCTrCH consisting of Secondary CCPCHs and FACHs, PCH with the corresponding PICH and MICH related to that group of Secondary CCPCHs], or
-	one [1.28Mcps TDD - or more] PRACH, one RACH and one AICH [FDD] and one FPACH[1.28Mcps TDD] related to that PRACH, or
-	one PLCCH [1.28Mcps TDD], or
- 	one E-RUCCH [3.84Mcps TDD and 7.68Mcps TDD].
Secondary CCPCH:
[FDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the Secondary CCPCH IE, the Node B shall configure and activate the indicated Secondary CCPCH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message.]
[FDD - If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the FDD S-CCPCH Frame Offset IE within the Secondary CCPCH IE, the Node B shall apply the indicated frame offset for the concerned Secondary CCPCH.]
[TDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the Secondary CCPCH IE, the Node B shall configure and activate the indicated Secondary CCPCH(s) according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message.]
[3.84Mcps TDD and 7.68Mcps TDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the TFCI Presence IE, the Node B shall apply the indicated TFCI presence in the timeslot of the S-CCPCH.  If all the S-CCPCHs defined in a timeslot do not have a TFCI Presence IE included, the Node B shall apply a TFCI field in the lowest numbered S-CCPCH of the timeslot.]
[TDD - FACHs and PCH may be mapped onto a CCTrCH which may consist of several Secondary CCPCHs]
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the FACH Parameters IE, the Node B shall configure and activate the indicated FACH(s) according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message.
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the PCH Parameters IE, the Node B shall configure and activate the concerned PCH and the associated PICH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message.
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the BCH Parameters IE, the Node B shall configure and activate the concerned BCH mapped on SCCPCH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message.
[1.28Mcps TDD - If the PCH Power IE is included in the PCH Parameters IE of the COMMON TRANSPORT CHANNEL SETUP REQUEST, the Node B shall use this value as the power at which the PCH shall be transmitted.]
[TDD - If the TSTD Indicator IE for the S-CCPCH is included and is set to "active" in the COMMON TRANSPORT CHANNEL SETUP REQUEST, the Node B shall activate TSTD diversity for all S-CCPCHs defined in the message that are not beacon channels (TS 25.221 [19], TS 25.224 [21]). If the TSTD Indicator IE is not included or is set to "not active" in the COMMON TRANSPORT CHANNEL SETUP REQUEST, the Node B shall not activate TSTD diversity for the S-CCPCHs defined in the message.]
[1.28Mcps TDD - If the TSTD Indicator IE for the PICH is included and is set to "active" in the COMMON TRANSPORT CHANNEL SETUP REQUEST message, the Node B shall activate TSTD diversity for the PICH if it is not a beacon channel (TS 25.221 [19], TS 25.224 [21]). If the TSTD Indicator IE is set to "not active" or the TSTD Indicator IE is not included for the PICH in the COMMON TRANSPORT CHANNEL SETUP REQUEST message, the Node B shall not activate TSTD diversity for the PICH.]
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the MICH Parameters IE, the Node B shall configure and activate the concerned MICH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message.
[FDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the Modulation Power Offset IE, in the Secondary CCPCH IE, the Node B shall apply the indicated modulation, and power offset in case of 16QAM, for the concerned Secondary CCPCH.]
[FDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the Extended Secondary CCPCH Slot Format IE, in the Secondary CCPCH IE, the Node B shall ignore the Secondary CCPCH Slot Format IE and apply the slot format indicated in the Extended Secondary CCPCH Slot Format IE.]
[3.84Mcps TDD and 7.68Mcps TDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the Modulation IE, the Node B shall apply the indicated modulation for the CCTrCH.]
[3.84Mcps TDD and 7.68Mcps TDD - If a timeslot has been configured for MBSFN operation then the contents of the [3.84Mcps TDD - Midamble Shift and Burst Type IE] [7.68Mcps TDD - Midamble Shift and Burst Type 7.68Mcps IE] shall be ignored and burst type 4, Kcell=1 shall be used (TS 25.221 [19]).]
[1.28 Mcps TDD - If the cell is operating in MBSFN only mode, the MBSFN Special Time Slot LCR IE indicates from CRNC to the Node B whether the channel is deployed on the MBSFN Special Time Slot for MBSFN only mode (TS 25.221 [19]).]
[1.28Mcps TDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the UARFCN IE in the Secondary CCPCHs IE, this Secondary CCPCH providing MBMS service in non-MBSFN only mode shall be setup on the secondary frequency indicated by the UARFCN IE.]
[3.84Mcps TDD IMB - If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the IMB Parameters IE within the Secondary CCPCH IE, the Node B shall apply 3.84Mcps MBSFN IMB operation.]
[3.84Mcps TDD IMB - If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the Last DL Channelisation Code Number IE within the IMB Parameters IE, the Node B may use the indicated range of the DL channelizationn codes in the new configuration.]
PRACH:
When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the PRACH IE, the Node B shall configure and activate the indicated PRACH and the associated RACH [FDD - and the associated AICH] according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message.
[1.28Mcps TDD - The resource indicated by the PRACH IE is used for RACH random access as well as E-DCH random access. The way to differentiate the two access type on PRACH physical resource shall be operated according to TS 25.224 [21].]
[1.28Mcps TDD - When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the UARFCN IE in the PRACH IE, the PRACH shall be set up on the secondary frequency indicated by the UARFCN IE.]
[1.28Mcps TDD - FPACH]:
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the FPACH IE, the Node B shall configure and activate the indicated FPACH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message.
Where more than one FPACH is defined, the FPACH that Node B should use is defined by the UpPCH signature (SYNC_UL) code that the UE used. The FPACH number = N mod M where N denotes the signature number (0..7) and M denotes the number of FPACHs that are defined in a cell. The FPACH number is in ascending order by Common Physical Channel ID IE contained in the COMMON TRANSPORT CHANNEL SETUP REQUEST message.
If the FPACH IE contains the UARFCN IE, the FPACH shall be set up on the secondary frequency indicated by the UARFCN IE.
When the FPACH is set up on the secondary frequency of a multi-frequency cell, if the PRACH LCR IE contains the UARFCN IE, the RACH IE included in the PRACH LCR IE shall be ignored; otherwise all IEs included in the PRACH LCR IE shall be ignored.
[1.28Mcps TDD - PLCCH]:
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the PLCCH IE, the Node B shall configure and activate the indicated PLCCH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message when one or more of the PLCCH sequence numbers have been assigned to one or more radio links.]
[3.84Mcps TDD and 7.68Mcps TDD - E-RUCCH]:
When the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the [3.84Mcps TDD - E-RUCCH IE] [7.68Mcps TDD - E-RUCCH 7.68Mcps IE], the Node B shall configure and activate the indicated E-RUCCH according to the COMMON TRANSPORT CHANNEL SETUP REQUEST message.
RACH, FACH, and PCH:
If the TNL QoS IE is included for a RACH, FACH, or PCH and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related RACH, FACH or PCH.
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the Broadcast Reference IE in the FACH Parameters IE, and one or more established FACH common transport channels with the same Broadcast Reference, the same Transport Format Set, the same ToAWS and the same ToAWE exist (all of them in other distinct cells within the Node B), the Node B may include the Broadcast Common Transport Bearer Indication IE in the Common Transport Channel Information Response IE in the COMMON TRANSPORT CHANNEL SETUP RESPONSE message to inform the CRNC that the existing transport bearer, identified by Broadcast Common Transport Bearer Indication IE, shall be used instead of establishing a new transport bearer.
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the Broadcast Reference IE in the FACH Parameters IE and no common transport channel with the same Broadcast Reference, the same Transport Format Set, the same ToAWS and the same ToAWE exists in another cell within the Node B, or if the Node B decides to establish a new transport bearer, the Node B may store the value of Broadcast Reference IE.
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the IP Multicast Indication IE, and if supported, the Node B may join the indicated IP multicast group if it has not done so yet (IETF RFC 3376 [41] in case of IPv4, IETF RFC 3810 [42] in case of IPv6). If the Node B does join the IP multicast group, or is already joined to the IP multicast group as a result of a previous procedure, the Node B shall include the IP Multicast Data Bearer Indication IE in the COMMON TRANSPORT CHANNEL INFORMATION RESPONSE message to inform the CRNC that the existing IP multicast transport bearer, identified by IP Multicast Indication IE in the corresponding COMMON TRANSPORT CHANNEL SETUP REQUEST message, shall be used instead of using a IP unicast transport bearer. If the COMMON TRANSPORT CHANNEL INFORMATION RESPONSE message does not contain the IP Multicast Data Bearer Indication IE, the CRNC shall send FACH data frames on the IP unicast transport bearer. No matter whether the Node B has joined the indicated IP multicast group, a new transport bearer shall be established using the Transport Layer Address IE and Binding ID IE and FACH specific control frames, e.g. TIMING ADJUSTMENT, shall be sent on the established Iub transport bearer.
General:
After successfully configuring the requested common transport channels and the common physical channels, the Node B shall store the value of Configuration Generation ID IE and it shall respond with the COMMON TRANSPORT CHANNEL SETUP RESPONSE message with the Common Transport Channel ID IE, the Binding ID IE (if no Broadcast Common Transport Bearer Indication IE is included or if no BCH Parameters IE is included) and the Transport Layer Address IE (if no Broadcast Common Transport Bearer Indication IE is included or if no BCH Parameters IE is included) for the configured common transport channels.
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message includes the Transport Layer Address and Binding ID IEs, the Node B may use the transport layer adress and the binding identifier received from the CRNC when establishing a transport bearer for the indicated common transport channels.
After a successful procedure and once the transport bearers are established, the configured common transport channels and the common physical channels shall adopt the state Enabled (TS 25.430 [6]) in the Node B and the common physical channels exist on the Uu interface.
8.2.1.3	Unsuccessful Operation

Figure 2: Common Transport Channel Setup procedure, Unsuccessful Operation
If the Node B is not able to support all or part of the configuration, it shall reject the configuration of all the channels in the COMMON TRANSPORT CHANNEL SETUP REQUEST message. The channels in the COMMON TRANSPORT CHANNEL SETUP REQUEST message shall remain in the same state as prior to the procedure. The Cause IE shall be set to an appropriate value. The value of Configuration Generation ID IE from the COMMON TRANSPORT CHANNEL SETUP REQUEST message shall not be stored.
If the configuration was unsuccessful, the Node B shall respond with a COMMON TRANSPORT CHANNEL SETUP FAILURE message.
Typical cause values are as follows:
Radio Network Layer Cause:
-	Cell not available
-	Power level not supported
-	Node B Resources unavailable
   -	Requested Tx Diversity Mode not supported
   -	UL SF not supported
   -	DL SF not supported
-	Common Transport Channel Type not supported
-	MICH not supported
Transport Layer Cause:
-	Transport Resources Unavailable
Miscellaneous Cause:
-	O&M Intervention
-	Control processing overload
-	HW failure
8.2.1.4	Abnormal Conditions
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the Secondary CCPCH IE, and that IE contains [FDD - neither the FACH Parameters IE nor the PCH Parameters IE, nor the BCH Parameters IE] [TDD - neither the FACH IE nor the PCH IE], the Node B shall reject the procedure using the COMMON TRANSPORT CHANNEL SETUP FAILURE message.
[TDD - If the FACH CCTrCH Id IE or the PCH CCTrCH Id IE does not equal the SCCPCH CCTrCH Id IE, the Node B shall regard the Common Transport Channel Setup procedure as having failed and the Node B shall send the COMMON TRANSPORT CHANNEL SETUP FAILURE message to the CRNC.]
[TDD - If the TDD Physical Channel Offset IE, the Repetition Period IE, and the Repetition Length IE are not equal for each SCCPCH configured within the CCTrCH or the TFCI Presence IE are not equal for any two SCCPCHs configured in the same timeslot, the Node B shall regard the Common Transport Channel Setup procedure as having failed and the Node B shall send the COMMON TRANSPORT CHANNEL SETUP FAILURE message to the CRNC.]
[1.28Mcps TDD - If the Common Transport Channel ID IE, and the Transport Format Set IE are not equal for each RACH configured in PRACH, the Node B shall regard the Common Transport Channel Setup procedure as having failed and the Node B shall send the COMMON TRANSPORT CHANNEL SETUP FAILURE message to the CRNC.]
[1.28Mcps TDD - If the UARFCN IE in the PRACH LCR IE is not equal to the UARFCN IE in any other PRACH LCR IE configured on one RACH, or if the UARFCN IE in PRACH LCR IE is not equal to the UARFCN IE in FPACH IE, the Node B shall regard the Common Transport Channel Setup procedure as having failed and the Node B shall send the COMMON TRANSPORT CHANNEL SETUP FAILURE message to the CRNC.]
If the state is already Enabled or Disabled (TS 25.430 [6]) for at least one channel in the COMMON TRANSPORT CHANNEL SETUP REQUEST message which is received, the Node B shall reject the configuration of all channels with the Cause IE set to "Message not compatible with receiver state".
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the Transport Layer Address IE or the Binding ID IE, and not both are present for a transport channel intended to be established, the Node B shall reject the procedure using the COMMON TRANSPORT CHANNEL SETUP FAILURE message.
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the MICH Parameters IE but not the FACH Parameters IE [FDD - for one S-CCPCH], the Node B shall reject the procedure using the COMMON TRANSPORT CHANNEL SETUP FAILURE message.
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains a Broadcast Reference IE value already associated to an existing FACH in the same cell, or if the message contains the same value for the Broadcast Reference IEs included in the FACH Parameters IEs for several FACHs in the list of FACHs defined on the Secondary CCPCH, the Node B shall reject the procedure, using the COMMON TRANSPORT CHANNEL SETUP FAILURE message.
If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains both the Broadcast Reference IE and the IP Multicast Indication IE, the Node B shall reject the procedure using the COMMON TRANSPORT CHANNEL SETUP FAILURE message.
[3.84Mcps TDD IMB - If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the IMB Parameters IE that includes the Last DL Channelisation Code Number IE and if the Secondary CCPCH Slot Format IE is set to "1", then the Node B shall reject the procedure using the COMMON TRANSPORT CHANNEL SETUP FAILURE message.]
If ALCAP is not used, if the COMMON TRANSPORT CHANNEL SETUP REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in the FACH Parameters IE, PCH Parameters IE and/or [FDD- RACH Parameters][TDD - RACH] IE, then the Node B shall reject the procedure using the COMMON TRANSPORT CHANNEL SETUP FAILURE message.
8.2.2	Common Transport Channel Reconfiguration
8.2.2.1	General
This procedure is used for reconfiguring common transport channels and/or common physical channels, while they still might be in operation.
8.2.2.2	Successful Operation

Figure 3: Common Transport Channel Reconfiguration, Successful Operation
The procedure is initiated with a COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
One message can configure only one of the following combinations:
-	[FDD - FACHs, BCH, one PCH, one PICH and/or one MICH related to one Secondary CCPCH], or
-	[TDD - one CCTrCH consisting of Secondary CCPCHs and FACHs, PCH with the corresponding PICH and MICH related to that group of Secondary CCPCHs], or
-	one RACH and/or one AICH[FDD] and/or one FPACH[1.28Mcps TDD] related to one PRACH,or
-	[1.28Mcps TDD - One UpPCH].
SCCPCH:
[TDD - If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the SCCPCH Power IE, the Node B shall reconfigure the maximum power that the indicated S-CCPCH shall use.]
FACH:
If the FACH Parameters IE is present, the Node B shall reconfigure the indicated FACH(s).
[FDD - If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the Max FACH Power IE, the Node B shall reconfigure the maximum power that the indicated FACH may use.]
[1.28Mcps TDD - If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the Max FACH Power IE, the Node B shall reconfigure the maximum power that the indicated FACH may use.]
If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the ToAWS IE, the Node B shall reconfigure the time of arrival window startpoint that the indicated FACH shall use. In case a transport bearer is used by several FACH channels in different cells, the reconfiguration of the time of arrival window startpoint requested in one cell shall be applied to all these FACH channels.
If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the ToAWE IE, the Node B shall reconfigure the time of arrival window endpoint that the indicated FACH shall use. In case a transport bearer is used by several FACH channels in different cells, the reconfiguration of the time of arrival window endpoint requested in one cell shall be applied to all these FACH channels.
If the TNL QoS IE is included and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related FACH.
PCH:
If the PCH Parameters IE is present, the Node B shall reconfigure the indicated PCH.
[FDD - If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the PCH Power IE, the Node B shall reconfigure the power that the PCH shall use.]
[1.28Mcps TDD - If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the PCH Power IE, the Node B shall reconfigure the power that the PCH shall use.]
If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the ToAWS IE, the Node B shall reconfigure the time of arrival window startpoint that the PCH shall use.
If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the ToAWE IE, the Node B shall reconfigure the time of arrival window endpoint that the PCH shall use.
If the TNL QoS IE is included and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related PCH.
BCH:
If the BCH Parameters IE is present, the Node B shall reconfigure the indicated BCH mapped on SCCPCH.
[FDD - If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the BCH Power IE, the Node B shall reconfigure the power that the BCH shall use.]
PICH:	
If the PICH Parameters IE is present, the Node B shall reconfigure the indicated PICH.
If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the PICH Power IE, the Node B shall reconfigure the power that the PICH shall use.
MICH:
If the MICH Parameters IE is present, the Node B shall reconfigure the MICH.
If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the MICH Power IE, the Node B shall reconfigure the power that the MICH shall use.
[FDD - PRACH]:
If the PRACH Parameters IE is present, the Node B shall reconfigure the indicated PRACH(s).
If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the Preamble Signatures IE, the Node B shall reconfigure the preamble signatures that the indicated PRACH shall use.
If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the Allowed Slot Format Information IE, the Node B shall reconfigure the slot formats that the indicated PRACH shall use.
If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the RACH Sub Channel Numbers IE, the Node B shall reconfigure the sub channel numbers that the indicated PRACH shall use.
If the TNL QoS IE is included and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related RACH.
[FDD - AICH]:
If the AICH Parameters IE is present, the Node B shall reconfigure the indicated AICH(s).
If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the AICH Power IE, the Node B shall reconfigure the power that the indicated AICH shall use.
[1.28Mcps TDD - FPACH]:
If the FPACH Parameters IE is included, the Node B shall reconfigure the indicated FPACH.
If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the Max FPACH Power IE, the Node B shall reconfigure the power that the FPACH shall use.
[1.28Mcps TDD - UpPCH]:
If the UpPCH Parameters IE is included, the Node B shall reconfigure the position of the UpPCH.
For a multi-frequency cell:
-	If the UpPCH Position LCR IE and the UARFCN IE are included, and the indicated frequency is primary frequency, the Node B shall reconfigure the position of the UpPCH on the primary frequency.
-	If the UpPCH Position LCR IE and the UARFCN IE are included, and the indicated frequency is a secondary frequency, the Node B shall configure or reconfigure the position of the UpPCH on the secondary frequency.
-	If the UpPCH Position LCR IE is not included, the Node B may delete the UpPCH on the secondary frequency indicated by the UARFCN IE.
[1.28Mcps TDD - PLCCH]:
If the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message includes the Max PLCCH Power IE, the Node B shall reconfigure the power that the PLCCH shall use.
General:
After a successful procedure, the channels will have adopted the new configuration in the Node B. The channels in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message shall remain in the same state as prior to the procedure. The Node B shall store the value of Configuration Generation ID IE and the Node B shall respond with the COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE message.
8.2.2.3	Unsuccessful Operation

Figure 4: Common Transport Channel Reconfiguration procedure, Unsuccessful Operation
If the Node B is not able to support all or part of the configuration, it shall reject the configuration of all the channels in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message. The channels in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message shall remain in the same state as prior to the procedure. The Cause IE shall be set to an appropriate value. The value of Configuration Generation ID IE from the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message shall not be stored.
If the configuration was unsuccessful, the Node B shall respond with the COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE message.
Typical cause values are as follows:
Radio Network Layer Cause:
-	Cell not available
-	Power level not supported
-	Node B Resources unavailable
Transport Layer Cause:
-	Transport Resources Unavailable
Miscellaneous Cause:
-	O&M Intervention
-	Control processing overload
-	HW failure
8.2.2.4	Abnormal Conditions
[1.28Mcps TDD - For a single frequency cell, if the UpPCH Parameters IE is included in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message but the UpPCH Position LCR IE is not present, the Node B shall reject the procedure by sending a COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE message.]
[1.28Mcps TDD - For a single frequency cell, if the UARFCN IE is included in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message, the Node B shall reject the procedure by sending a COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE message.]
[1.28Mcps TDD - For a multi-frequency cell, if the UpPCH Parameters IE is included in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message but the UpPCH Position LCR IE is not present,and the frequency indicated by the UARFCN IE is primary frequency, the Node B shall reject the procedure by sending a COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE message.]
[1.28Mcps TDD - For a multi-frequency cell, if the UpPCH Parameters IE is included in the COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message but the UpPCH Position LCR IE is not present,and the frequency indicated by the UARFCN IE is secondary frequency on which the UpPCH is not configured, the Node B shall reject the procedure by sending a COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE message.]
8.2.3	Common Transport Channel Deletion
8.2.3.1	General
This procedure is used for deleting common physical channels and common transport channels.
8.2.3.2	Successful Operation

Figure 5: Common Transport Channel Deletion procedure, Successful Operation
The procedure is initiated with a COMMON TRANSPORT CHANNEL DELETION REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
Secondary CCPCH:
If the Common Physical Channel ID IE or Common Physical Channel ID 7.68Mcps IE contained in the COMMON TRANSPORT CHANNEL DELETION REQUEST message indicates a Secondary CCPCH, the Node B shall delete the indicated channel and the FACHs and PCH supported by that Secondary CCPCH. If there is a PCH that is deleted, the PICH associated with that PCH shall also be deleted. If an S-CCPCH is deleted, the MICH associated with that S-CCPCH shall also be deleted.
If the Common Physical Channel ID IE or Common Physical Channel ID 7.68Mcps IE contained in the COMMON TRANSPORT CHANNEL DELETION REQUEST message indicates a common transport channel that is sharing a common transport bearer with other one or several common transport channels, the Node B shall delete the indicated channel but keep the common transport bearer which is shared by the remaining common transport channel(s).
If the Common Physical Channel ID IE or Common Physical Channel ID 7.68Mcps IE contained in the COMMON TRANSPORT CHANNEL DELETION REQUEST message indicates a common transport channel which is using an IP multicast transport bearer, the Node B shall leave the IP multicast group if this channel is the last one in the group (IETF RFC 3376 [41] in case of IPv4, IETF RFC 3810 [42] in case of IPv6).
PRACH:
If the Common Physical Channel ID IE contained in the COMMON TRANSPORT CHANNEL DELETION REQUEST message indicates a PRACH, the Node B shall delete the indicated channel and the RACH supported by the PRACH. [FDD - The AICH associated with the RACH shall also be deleted.]
[1.28Mcps TDD PLCCH:
If the Common Physical Channel ID IE contained in the COMMON TRANSPORT CHANNEL DELETION REQUEST message indicates a PLCCH, the Node B shall delete the indicated channel.]
General:
[TDD - If the requested common physical channel is a part of a CCTrCH, all common transport channels and all common physical channels associated with this CCTrCH shall be deleted.]
After a successful procedure, the channels are deleted in the Node B. The channels in the COMMON TRANSPORT CHANNEL DELETION REQUEST message shall be set to state Not Existing ref. TS 25.430 [6]. The Node B shall store the received value of the Configuration Generation ID IE and respond with the COMMON TRANSPORT CHANNEL DELETION RESPONSE message.
8.2.3.3	Unsuccessful Operation
-
8.2.3.4	Abnormal Conditions
If the C-ID in the COMMON TRANSPORT CHANNEL DELETION REQUEST message is not existing in the Node B or the Common Physical Channel ID does not exist in the Cell, the Node B shall respond with the COMMON TRANSPORT CHANNEL DELETION RESPONSE message.
8.2.4	Block Resource
8.2.4.1	General
The Node B initiates this procedure to request the CRNC to prohibit the usage of the specified logical resources.
The logical resource that can be blocked is a cell.
8.2.4.2	Successful Operation

Figure 6: Block Resource procedure, Successful Operation
The procedure is initiated with a BLOCK RESOURCE REQUEST message sent from the Node B to the CRNC using the Node B Control Port.
Upon reception of the BLOCK RESOURCE REQUEST message, the CRNC shall prohibit the use of the indicated logical resources according to the Blocking Priority Indicator IE.
If the Blocking Priority Indicator IE in the BLOCK RESOURCE REQUEST message indicates "High Priority", the CRNC shall prohibit the use of the logical resources immediately.
If the Blocking Priority Indicator IE in the BLOCK RESOURCE REQUEST message indicates "Normal Priority", the CRNC shall prohibit the use of the logical resources if the resources are idle or immediately upon expiry of the shutdown timer specified by the Shutdown Timer IE in the BLOCK RESOURCE REQUEST message. New traffic shall not be allowed to use the logical resources while the CRNC waits for the resources to become idle and once the resources are blocked.
If the Blocking Priority Indicator IE in the BLOCK RESOURCE REQUEST message indicates "Low Priority", the CRNC shall prohibit the use of the logical resources when the resources become idle. New traffic shall not be allowed to use the logical resources while the CRNC waits for the resources to become idle and once the resources are blocked.
If the resources are successfully blocked, the CRNC shall respond with a BLOCK RESOURCE RESPONSE message. Upon reception of the BLOCK RESOURCE RESPONSE message, the Node B may disable [3.84Mcps TDD - SCH], [FDD - the Primary SCH, the Secondary SCH, the Primary CPICH, if present the Secondary CPICH(s)], [1.28Mcps TDD - DwPCH] and the Primary CCPCH. The other logical resources in the cell shall be considered as blocked.
Reconfiguration of logical resources and change of System Information can be done, even when the logical resources are blocked.
Interactions with the Unblock Resource procedure:
If the UNBLOCK RESOURCE INDICATION message is received by the CRNC while a Block Resource procedure on the same logical resources is in progress, the CRNC shall cancel the Block Resource procedure and proceed with the Unblock Resource procedure.
If the BLOCK RESOURCE RESPONSE message or the BLOCK RESOURCE FAILURE message is received by the Node B after the Node B has initiated an Unblock Resource procedure on the same logical resources as the ongoing Block Resource procedure, the Node B shall ignore the response to the Block Resource procedure.
8.2.4.3	Unsuccessful Operation

Figure 7: Block Resource procedure, Unsuccessful Operation
The CRNC may reject the request to block the logical resources, in which case the logical resources will remain unaffected and the CRNC shall respond to the Node B with the BLOCK RESOURCE FAILURE message. Upon reception of the BLOCK RESOURCE FAILURE message, the Node B shall leave the logical resources in the state that they were in prior to the start of the Block Resource procedure.
Typical cause values are as follows:
Miscellaneous Cause:
-	O&M Intervention
-	Control processing overload
-	HW failure
Radio Network Layer Cause:
-	Priority transport channel established
8.2.4.4	Abnormal Conditions
-
8.2.5	Unblock Resource
8.2.5.1	General
The Node B initiates this procedure to indicate to the CRNC that logical resources are now unblocked.
The logical resource that can be unblocked is a cell.
8.2.5.2	Successful Operation

Figure 8: Unblock Resource procedure, Successful Operation
The procedure is initiated with an UNBLOCK RESOURCE INDICATION message sent from the Node B to the CRNC using the Node B Control Port. The Node B shall enable [3.84Mcps TDD - SCH], [FDD - the Primary SCH, the Secondary SCH, the Primary CPICH, the Secondary CPICH(s) (if present)], [1.28Mcps TDD - DwPCH] and the Primary CCPCH that had been disabled due to the preceding Block Resource procedure before sending the UNBLOCK RESOURCE INDICATION message. Upon reception of the UNBLOCK RESOURCE INDICATION message, the CRNC may permit the use of the logical resources.
All physical channels and transport channels associated to the cell that is unblocked are also unblocked.
8.2.5.3	Abnormal Conditions
-
8.2.6	Audit Required
8.2.6.1	General
The Node B initiates this procedure to request the CRNC to perform an audit of the logical resources at the Node B. This procedure is used to indicate a possible misalignment of state or configuration information.
8.2.6.2	Successful Operation

Figure 9: Audit Required procedure, Successful Operation
The procedure is initiated with an AUDIT REQUIRED INDICATION message sent from the Node B to the CRNC using the Node B Control Port.
If the Node B cannot ensure alignment of the state or configuration information, it should initiate the Audit Required procedure.
Upon receipt of the AUDIT REQUIRED INDICATION message, the CRNC should initiate the Audit procedure.
8.2.6.3	Abnormal Conditions
-
8.2.7	Audit
8.2.7.1	General
This procedure is executed by the CRNC to perform an audit of the configuration and status of the logical resources in the Node B. A complete audit of a Node B is performed by one or more Audit procedures, together performing an audit sequence. The audit may cause the CRNC to re-synchronise the Node B to the status of logical resources known by the CRNC, that the Node B can support.
8.2.7.2	Successful Operation

Figure 10: Audit procedure, Successful Operation
The procedure is initiated with an AUDIT REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
If the Start Of Audit Sequence Indicator IE in the AUDIT REQUEST message is set to "start of audit sequence" a new audit sequence is started, any ongoing audit sequence shall be aborted and the Node B shall provide (part of the) audit information. If the Start Of Audit Sequence Indicator IE is set to "not start of audit sequence", the Node B shall provide (part of) the remaining audit information not already provided during this audit sequence. 
If the information provided in the AUDIT RESPONSE message completes the audit sequence, the Node B shall set the End Of Audit Sequence Indicator IE in the AUDIT RESPONSE message to "End of Audit Sequence". If not all audit information has been provided yet as part of the ongoing audit sequence, the Node B shall set the End Of Audit Sequence Indicator IE in the AUDIT RESPONSE message to "Not End of Audit Sequence".
Information Provided In One Audit Sequence:
The Node B shall include one Local Cell Information IE for each local cell present in the Node B. The Node B shall include the Maximum DL Power Capability IE, the Minimum Spreading Factor IE and the Minimum DL Power Capability IE when any of those values are known by the Node B. The Node B shall include the HSDPA Capability IE set to "HSDPA Capable" and may include HS-DSCH MAC-d PDU Size Capability IE for every HSDPA-capable Local Cell. The Node B shall include the E-DCH Capability IE set to "E-DCH Capable" and may include E-DCH MAC-d PDU Size Capability IE for every E-DCH-capable Local Cell. The Node B shall include the MBMS Capability IE set to "MBMS Capable" for every MBMS-capable Local Cell. [FDD - The Node B shall include the F-DPCH Capability IE set to "F-DPCH Capable" for every F-DPCH-capable Local Cell.] [FDD - The Node B shall include the Continuous Packet Connectivity DTX-DRX Capability IE set to "Continuous Packet Connectivity DTX-DRX Capable" when Continuous Packet Connectivity DTX-DRX is supported for every Local Cell that is both HSDPA-capable and E-DCH-capable.] [FDD - The Node B shall include the Continuous Packet Connectivity HS-SCCH less Capability IE set to "Continuous Packet Connectivity HS-SCCH less Capable" when Continuous Packet Connectivity HS-SCCH less is supported for every Local Cell that is both HSDPA-capable and E-DCH-capable.] [FDD - The Node B shall include the MIMO Capability IE set to "MIMO Capable" for every MIMO-capable Local Cell.] [FDD - The Node B shall include the SixtyfourQAM DL Capability IE set to "SixtyfourQAM DL Capable" for every SixtyfourQAM DL-capable Local Cell.] [FDD - The Node B shall include the Enhanced FACH Capability IE set to "Enhanced FACH Capable" for every Enhanced FACH-capable Local Cell.] [FDD - The Node B shall include the SixteenQAM UL Capability IE set to "SixteenQAM UL Capable" for every SixteenQAM UL-capable Local Cell.] [1.28Mcps TDD - The Node B shall include the MBSFN Only Mode Capability IE set to "MBSFN Only Mode Capable" for every MBSFN Only Mode-capable Local Cell.] [FDD - The Node B shall include the F-DPCH Slot Format Capability IE set to "F-DPCH Slot Format Capable" for every F-DPCH Slot Format-capable Local Cell.] [1.28Mcps TDD - The Node B shall include the SixtyfourQAM DL Capability IE set to "SixtyfourQAM DL Capable" for every SixtyfourQAM DL-capable Local Cell.] [FDD - The Node B shall include the Common E-DCH Capability IE set to "Common E-DCH Capable" for every Common E-DCH capable Local Cell.] The Node B shall include the E-DPCCH Power Boosting Capability IE set to "E-DPCCH Power Boosting Capable " for every E-DPCCH Power Boosting -capable Local Cell. [FDD - The Node B shall include the SixtyfourQAM DL and MIMO Combined Capability IE set to "SixtyfourQAM DL and MIMO Combined Capable" when Combined SixtyfourQAM DL and MIMO is supported for every Local Cell that is both SixtyfourQAM DL-capable and MIMO-capable.][1.28Mcps TDD - The Node B shall include the Enhanced FACH Capability IE set to "Enhanced FACH Capable" for every Enhanced FACH-capable Local Cell.] [1.28Mcps TDD - The Node B shall include the Enhanced PCH Capability IE set to "Enhanced PCH Capable" for every Enhanced PCH-capable Local Cell.] [1.28Mcps TDD - The Node B shall include the Enhanced UE DRX Capability LCR IE set to " Enhanced UE DRX Capable " for every Enhanced UE DRX Capable Local Cell.] [FDD - The Node B shall include the Multi Cell Capability Info IE and set the Multi Cell Capability IE value to "Multi Cell Capable" for every Multi Cell operation capable Local Cell, and if the cell can be the serving HS-DSCH then the possible cells to serve multiple adjacent and/or non-adjacent carrier operation (TS 25.133 [22]) (same or adjacent sector in the same Node B) that can act as secondary serving HS-DSCH shall be listed in the Possible Secondary Serving Cell List IE. For each cell in the Possible Secondary Serving Cell List IE that is Multi Cell E-DCH Capable, indicated in the Cell Capability Container IE with the "Multi Cell E-DCH Capability" bit = "1", and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the Local Cell as the corresponding cell of the primary uplink frequency, the Node B shall include the Multicell E-DCH Restriction IE set to "TRUE" in the Possible Secondary Serving Cell List IE.] [1.28Mcps TDD - The Node B shall include the Semi-Persistent scheduling Capability LCR IE set to "Semi-Persistent scheduling Capable" for every semi-persistent scheduling Capable Local Cell.] [1.28Mcps TDD - The Node B shall include the Continuous Packet Connectivity DRX Capability LCR IE set to "Continuous Packet Connectivity DRX Capability Capable" for Continuous Packet Connectivity DRX Capability Capable Local Cell.] [1.28Mcps TDD- The Node B shall include the MIMO Capability IE set to "MIMO Capable" for every MIMO-capable Local Cell.] [1.28Mcps TDD- The Node B shall include the SixtyfourQAM DL and MIMO Combined Capability IE set to "SixtyfourQAM DL and MIMO Combined Capable" when Combined SixtyfourQAM DL and MIMO is supported for every Local Cell that is both SixtyfourQAM DL-capable and MIMO-capable.] [FDD - The Node B shall include the Enhanced UE DRX Capability IE set to " Enhanced UE DRX Capable" for every Enhanced UE DRX capable Local Cell.] [1.28Mcps TDD- The Node B shall include the Cell Portion Capability LCR IE set to " Cell Portion Capable" for every Cell Portion Capable Local Cell.] [FDD - The Node B shall include the MIMO Power Offset For S-CPICH Capability IE set to "S-CPICH Power Offset Capable " for every MIMO-capable Local Cell able to transmit S-CPICH at a power offset from P-CPICH.] [FDD - The Node B shall include the TX Diversity on DL Control Channels by MIMO UE Capability IE set to "DL Control Channel Tx Diversity for MIMO UE with non-diverse P-CPICH Capable" for every MIMO-capable Local Cell able to support DL control channels in transmit diversity for MIMO UEs when when MIMO is active and P-CPICH is not transmitted in diversity mode (TS 25.211 [7]).] [FDD - The Node B shall include the Single Stream MIMO Capability IE set to "Single Stream MIMO Capable" for every Single Stream MIMO capable Local Cell.] [FDD - The Node B shall include the Dual Band Capability Info IE and set the Dual Band Capability IE value to "Dual Band Capable" for every Dual Band HS-DSCH operation capable Local Cell, and set the Dual Band E-DCH Capability IE value to "Dual Band Capable" for every Dual Band E-DCH operation capable Local Cell, and if the cell can be the serving HS-DSCH then the possible cells to serve multiple dual band carrier operation (TS 25.133 [22]) (same sector) that can act as secondary serving HS-DSCH shall be listed in the Possible Secondary Serving Cell List IE. For each cell in the Possible Secondary Serving Cell List IE that is Multi Band E-DCH Capable, as indicated in the Dual Band E-DCH Capability IE for that cell, and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the Local Cell as the corresponding cell of the primary uplink frequency, the Node B shall include the Multicell E-DCH Restriction IE set to "TRUE" in the Possible Secondary Serving Cell List IE.] [FDD - The Node B shall include the Cell Capability Container IE if the Local Cell is capable of at least one feature listed in 9.2.2.129 and indicate the capabilities listed in 9.2.2.129 for the local cell.][1.28Mcps TDD - The Node B shall include the TS0 Capability LCR IE set to "TS0 Capable" for every TS0 Capable Local Cell.][FDD - For every MIMO-capable and/or Single Stream MIMO Capable Local Cell the Node B may include the Precoding Weight Set Restriction IE set to "Preferred", if configuration of the precoding weight set restriction defined in TS 25.331 [18] is preferred.] [1.28Mcps TDD - The Node B shall include the Cell Capability Container TDD LCR IE if the Local Cell is capable of at least one feature listed in 9.2.3.115 and indicate the capabilities listed in 9.2.3.115 for the local cell.] [1.28Mcps TDD - The Node B shall include MU-MIMO Capability Container IE if the Local Cell is capable of at least one feature listed in 9.2.3.119 and indicate the capabilities listed in 9.2.3.119 for the local cell.][1.28Mcps TDD - The Node B shall include the Adaptive Special Burst Power Capability LCR IE set to "Adaptive Special Burst Power Capable" for every Adaptive Special Burst Power Capable Local Cell.]
[TDD - The Node B shall include the Reference Clock Availability IE to indicate the availability of a Reference clock connected to the Local Cell.]
If the Node B internal resources are pooled for a group of cells, the Node B shall include one Local Cell Group Information IE containing the Node B internal resource capacity and the consumption laws per group of cells [FDD - , including also the E-DCH Capacity consumption Law IE, if E-DCH is supported] [TDD - , including also the E-DCH TDD Capacity Consumption Law IE, if E-DCH is supported]. If the UL Capacity Credit IE is not present in the Local Cell Group Information IE, then the internal resource capabilities of the Node B for the Local Cell Group are modelled as shared resources between Uplink and Downlink.
If the Node B internal power resources are pooled for a group of Local Cells, the Node B shall include one Power Local Cell Group Information IE containing the Maximum DL Power Capability for each Power Local Cell Group for which this value is known by the Node B. In this case, the Node B shall also include the Maximum DL Power Capability IE in the Local Cell Information IE for all the Local Cells belonging to a Power Local Cell Group reported in the Power Local Cell Group Information IE. Furthermore, the sum of the Maximum DL Power Capability of all the Local Cells belonging to the same Power Local Cell Group shall not exceed the Maximum DL Power Capability of the concerned Power Local Cell Group.
The Node B shall include, for each local cell present in the Node B, the Node B internal resource capability and consumption laws within the Local Cell Information IE [FDD - , including also the E-DCH CapacityCconsumption Law, if E-DCH is supported] [TDD - , including also the E-DCH TDD Capacity Consumption Law IE, if E-DCH is supported]. If the UL Capacity Credit IE is not present in the Local Cell Information IE, then the internal resource capabilities of the local cell are modelled as shared resources between Uplink and Downlink. If the Local Cell utilises Node B internal resource capabilities that are pooled for several Local Cell(s), the Local Cell Group ID IE shall contain the identity of the used Local Cell Group. If the Local Cell utilises Node B internal power resources that are pooled for several Local Cells, the Power Local Cell Group ID IE shall contain the identity of the concerned Power Local Cell Group.
The Node B shall include one Cell Information IE for each cell in the Node B and information about all common transport channels and all common physical channels for each cell. If a Configuration Generation ID IE for a cell can not be trusted, the Node B shall set this Configuration Generation ID IE = "0". The Node B shall include the HS-DSCH Resources Information IE for every Cell which has been configured with HS-DSCH resources. [FDD - The Node B shall include the E-DCH Resources Information IE for every Cell which has been configured with E-DCH resources.] [TDD - The Node B shall include the E-DCH Resources Information IE and the [3.84Mcps TDD - E-RUCCH Information IE] [7.68Mcps TDD - E-RUCCH Information 7.68Mcps IE]for every cell which has been configured with E-DCH resources.]
[1.28Mcps TDD - The Node B may include the UpPCH Information LCR IE for each frequency on which the UpPCH channel is not configured in the timeslot of UpPTS.]
[1.28Mcps TDD - For a multi-frequency cell, the Node B may include the UARFCN IE in the HS-DSCH Resources Information IE to report the status of  the HS-DSCH resources on the indicated frequency, the Node B may also not include any UARFCN IE in the HS-DSCH Resources Information IE to report the status of  the HS-DSCH resources for  the whole cell.]
[1.28Mcps TDD - For a multi-frequency cell, the Node B may include the UARFCN IE in the E-DCH Resources Information IE to report the status of the E-DCH resources on the indicated frequency, the Node B may also not include any UARFCN IE in the E-DCH Resources Information IE to report the status of the E-DCH resources for the whole cell.]
The Node B shall also include one Communication Control Port Information IE for each Communication Control Port in the Node B.
[1.28Mcps TDD - For a multi-frequency cell, the Node B should report the status of the resources used for each frequency. A reporting method can be found in Annex E.]
8.2.7.3	Unsuccessful Operation

Figure 10A: Audit procedure, Unsuccessful Operation
If the Node B cannot perform an audit of the configuration and status of the logical resources, it shall send a AUDIT FAILURE message with the Cause IE set to an appropriate value.
8.2.7.4	Abnormal Conditions
If the Node B receives the AUDIT REQUEST message with the Start Of Audit Sequence Indicator IE set to "not start of audit sequence" and there is no ongoing audit sequence, the Node B shall send the AUDIT FAILURE message with the appropriate cause value.
8.2.8	Common Measurement Initiation
8.2.8.1	General
This procedure is used by a CRNC to request the initiation of measurements on common resources in a Node B.
8.2.8.2	Successful Operation

Figure 11: Common Measurement Initiation procedure, Successful Operation
The procedure is initiated with a COMMON MEASUREMENT INITIATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
Upon reception, the Node B shall initiate the requested measurement according to the parameters given in the request. Unless specified below, the meaning of the parameters are given in other specifications.
[TDD - If the [3.84Mcps TDD and 7.68Mcps TDD - Time Slot IE] [1.28Mcps TDD - Time Slot LCR IE] is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to the requested time slot individually.]
[1.28Mcps TDD - If Time Slot LCR IE is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to all the available time slots in the frequency.]
[1.28Mcps TDD - If the Common Measurement Type IE is not set to "HS-DSCH Provided Bit Rate" and UARFCN IE is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to all the frequencies in the cell.] [1.28Mcps TDD - If the Common Measurement Type IE is not set to "HS-DSCH Provided Bit Rate" and neither UARFCN IE nor Time Slot LCR IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to all time slots in all frequencies in which the measurements are applicable.] 
[1.28Mcps TDD - If Additional Time Slot LCR IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to the requested additional time slots indicated in the Additional Time Slot LCR IE.]
[1.28Mcps TDD - If the UpPCH Position LCR IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, and the Common Measurement Type IE is set to "UpPCH interference", the measurement request shall apply to the requested UpPCH position individually.]
If the Common Measurement Type IE is not set to "SFN-SFN Observed Time Difference" and the SFN Reporting Indicator IE is set to "FN Reporting Required", the SFN IE shall be included in the COMMON MEASUREMENT REPORT message or in the COMMON MEASUREMENT RESPONSE message, the latter only in the case the Report Characteristics IE is set to "On Demand". The reported SFN shall be the SFN at the time when the measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]). If the Common Measurement Type IE is set to "SFN-SFN Observed Time Difference", the SFN Reporting Indicator IE shall be ignored.
[FDD - If the Common Measurement Type IE is set to "Received Scheduled E-DCH Power Share" and the RTWP* Reporting Indicator IE is set to "RTWP* Reporting Required", the RTWP* Value IE shall be included in the COMMON MEASUREMENT REPORT message or in the COMMON MEASUREMENT RESPONSE message, the latter only in the case the Report Characteristics IE is set to "On Demand". This is the received total wideband power (RTWP) determined for the same time period during which RSEPS is determined.]
[FDD - If the Common Measurement Type IE is set to "Received Scheduled E-DCH Power Share for Cell Portion" and the RTWP*for Cell Portion Reporting Indicator IE is set to "RTWP* Reporting Required", the RTWP* Value IE shall be included in the COMMON MEASUREMENT REPORT message or in the COMMON MEASUREMENT RESPONSE message, the latter only in the case the Report Characteristics IE is set to "On Demand".]
[1.28Mcps TDD - For a multi-frequency cell, if Common Measurement Type IE is set to "HS-DSCH Provided Bit Rate", and the UARFCN IE is included in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to the indicated frequency, if Common Measurement Type IE is set to "HS-DSCH Provided Bit Rate", and the UARFCN IE is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to the whole cell.] 
[FDD - If the Common Measurement Type IE is set to "E-DCH RACH Report", and the Concurrent Deployment of 2ms and 10ms TTI IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, the 2ms Granted E-DCH RACH Resources IE, 2ms Overridden E-DCH RACH Resources IE and 2ms Denied E-DCH RACH Resources IE should be included in the COMMON MEASUREMENT REPORT message or in the COMMON MEASUREMENT INITIATION RESPONSE message, the latter only in the case the Report Characteristics IE is set to "On Demand".]
Common measurement type:
If the Common Measurement Type IE is set to "SFN-SFN Observed Time Difference", then the Node B shall initiate the SFN-SFN Observed Time Difference measurements between the reference cell identified by C-ID IE and the neighbouring cells identified by the UTRAN Cell Identifier(UC-Id) IE in the Neighbouring Cell Measurement Information IE.
If the Common Measurement Type IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning", then the Node B shall initiate the UTRAN GANSS Timing of Cell Frames measurements using the GNSS system time identified by GANSS Time ID IE included in the COMMON MEASUREMENT INITIATION REQUEST message.
-	If the Common Measurement Type IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning" and the GANSS Time ID IE is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall assume that the corresponding GANSS time is "Galileo" system time.
[FDD and 1.28Mcps TDD - If the Common Measurement Type IE is set to "Received Total Wide Band Power for Cell Portion", "Transmitted Carrier Power for Cell Portion", [FDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH transmission for Cell Portion"], "HS-DSCH Required Power for Cell Portion", "HS-DSCH Provided Bit Rate for Cell Portion"[1.28Mcps TDD - , "E-DCH Provided Bit Rate for Cell Portion", "UpPCH interference for Cell Portion"] or [FDD - "Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"], the Node B shall initiate the corresponding measurements for all the cell portions which are configured under the cell indicated by C-ID IE in the COMMON MEASUREMENT INITIATION REQUEST message.]
Report characteristics:
The Report Characteristics IE indicates how the reporting of the measurement shall be performed. See also Annex B.
If the Report Characteristics IE is set to "On Demand" and if the SFN IE is not provided, the Node B shall return the result of the requested measurement immediately. If the SFN IE is provided, it indicates the frame for which the measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]).
If the Report Characteristics IE is set to "Periodic", the Node B shall periodically initiate a Common Measurement Reporting procedure for this measurement, with the requested report frequency. If the Common Measurement Type IE is set to "SFN-SFN Observed Time Difference", all the available measurement results shall be reported in the Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information IE in the SFN-SFN Measurement Value Information IE and the Node B shall indicate in the Unsuccessful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information IE all the remaining neighbouring cells with no measurement result available in the Common Measurement Reporting procedure. If the SFN IE is provided, it indicates the frame for which the first measurement value of a periodic reporting shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]).
If the Report Characteristics IE is set to "Event A", the Node B shall initiate the Common Measurement Reporting procedure when the measured entity rises above the requested threshold and stays there for the requested hysteresis time. If the Measurement Hysteresis Time IE is not included, the Node B shall use the value zero for the hysteresis time. If the Common Measurement Type IE is set to "HS-DSCH Required Power", the measured entity to be considered is the sum of the HS-DSCH Required Power measurements for each priority class. [FDD and 1.28Mcps TDD - If the Common Measurement Type IE is set to "Received Total Wide Band Power for Cell Portion" or "Transmitted Carrier Power for Cell Portion" or [FDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"] or "HS-DSCH Required Power for Cell Portion"[1.28Mcps TDD - or "UpPCH interference for Cell Portion"] or [FDD - "Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"], the measurement entity to be considered is the corresponding measurement for each cell portion.]
If the Report Characteristics IE is set to "Event B", the Node B shall initiate the Common Measurement Reporting procedure when the measured entity falls below the requested threshold and stays there for the requested hysteresis time. If the Measurement Hysteresis Time IE is not included, the Node B shall use the value zero for the hysteresis time. If the Common Measurement Type IE is set to "HS-DSCH Required Power", the measured entity to be considered is the sum of the HS-DSCH Required Power measurements for each priority class. [FDD and 1.28Mcps TDD - If the Common Measurement Type IE is set to "Received Total Wide Band Power for Cell Portion" or "Transmitted Carrier Power for Cell Portion" or [FDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"] or "HS-DSCH Required Power for Cell Portion"[1.28Mcps TDD - or "UpPCH interference for Cell Portion"] or [FDD -"Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"], the measurement entity to be considered is the corresponding measurement for each cell portion.]
If the Report Characteristics IE is set to "Event C", the Node B shall initiate the Common Measurement Reporting procedure when the measured entity rises by an amount greater than the requested threshold within the requested time. After having reported this type of event, the next C event reporting for the same measurement cannot be initiated before the rising time specified by the Measurement Change Time IE has elapsed since the previous event reporting. [FDD and 1.28Mcps TDD - If the Common Measurement Type IE is set to "Received Total Wide Band Power for Cell Portion" or "Transmitted Carrier Power for Cell Portion"[1.28Mcps TDD - or "UpPCH interference for Cell Portion"] or [FDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"] or [FDD -"Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"], the measurement entity to be considered is the corresponding measurement for each cell portion.]
If the Report Characteristics IE is set to "Event D", the Node B shall initiate the Common Measurement Reporting procedure when the measured entity falls by an amount greater than the requested threshold within the requested time. After having reported this type of event, the next D event reporting for the same measurement cannot be initiated before the falling time specified by the Measurement Change Time IE has elapsed since the previous event reporting.
[FDD and 1.28Mcps TDD - If the Common Measurement Type IE is set to "Received Total Wide Band Power for Cell Portion" or "Transmitted Carrier Power for Cell Portion"[1.28Mcps TDD - or "UpPCH interference for Cell Portion"] or  [FDD -"Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"] or  [FDD - "Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"], the measurement entity to be considered is the corresponding measurement for each cell portion.]
If the Report Characteristics IE is set to "Event E", the Node B shall initiate the Common Measurement Reporting procedure when the measured entity rises above the 'Measurement Threshold 1' and stays there for the 'Measurement Hysteresis Time' (Report A). When the conditions for Report A are met and the Report Periodicity IE is provided, the Node B shall initiate the Common Measurement Reporting procedure periodically. If the conditions for Report A have been met and the measured entity falls below the 'Measurement Threshold 2' and stays there for the 'Measurement Hysteresis Time', the Node B shall initiate the Common Measurement Reporting procedure (Report B) as well as terminate any corresponding periodic reporting. If the Measurement Threshold 2 IE is not present, the Node B shall use the value of the Measurement Threshold 1 IE instead. If the Measurement Hysteresis Time IE is not included, the Node B shall use the value zero as hysteresis times for both Report A and Report B. If the Common Measurement Type IE is set to "HS-DSCH Required Power", the measured entity to be considered is the sum of the HS-DSCH Required Power measurements for each priority class. [FDD and 1.28Mcps TDD - If the Common Measurement Type IE is set to "Received Total Wide Band Power for Cell Portion" or "Transmitted Carrier Power for Cell Portion"[1.28Mcps TDD - or "UpPCH interference for Cell Portion"] or [FDD -"Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"] or "HS-DSCH Required Power for Cell Portion" or [FDD - "Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"], the measurement entity to be considered is the corresponding measurement for each cell portion.]
If the Report Characteristics IE is set to "Event F", the Node B shall initiate the Common Measurement Reporting procedure when the measured entity falls below the 'Measurement Threshold 1' and stays there for the 'Measurement Hysteresis Time' (Report A). When the conditions for Report A are met and the Report Periodicity IE is provided the Node B shall also initiate the Common Measurement Reporting procedure periodically. If the conditions for Report A have been met and the measured entity rises above the 'Measurement Threshold 2' and stays there for the 'Measurement Hysteresis Time', the Node B shall initiate the Common Measurement Reporting procedure (Report B) as well as terminate any corresponding periodic reporting. If the Measurement Threshold 2 IE is not present, the Node B shall use the value of the Measurement Threshold 1 IE instead. If the Measurement Hysteresis Time IE is not included, the Node B shall use the value zero as hysteresis times for both Report A and Report B. If the Common Measurement Type IE is set to "HS-DSCH Required Power", the measured entity to be considered is the sum of the HS-DSCH Required Power measurements for each priority class. [FDD and 1.28Mcps TDD - If the Common Measurement Type IE is set to "Received Total Wide Band Power for Cell Portion" or "Transmitted Carrier Power for Cell Portion"[1.28Mcps TDD - or "UpPCH interference for Cell Portion"] or [FDD -"Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"] or "HS-DSCH Required Power for Cell Portion" or [FDD - "Received Scheduled E-DCH Power Share for Cell Portion"][1.28Mcps TDD - " UL Timeslot ISCP for Cell Portion"], the measurement entity to be considered is the corresponding measurement for each cell portion.]
If the Report Characteristics IE is set to "On Modification" and if the SFN IE is not provided, the Node B shall report the result of the requested measurement immediately. If the SFN IE is provided, it indicates the frame for which the measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]). Then, the Node B shall initiate the Common Measurement Reporting procedure in accordance to the following conditions:
1.	If the Common Measurement Type IE is set to "UTRAN GPS Timing of Cell Frames for UE Positioning":
-	If the TUTRAN-GPS Change Limit IE is included in the TUTRAN-GPS Measurement Threshold Information IE, the Node B shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [25]), calculate the change of TUTRAN-GPS value (Fn). The Node B shall initiate the Common Measurement Reporting procedure and set n equal to zero when the absolute value of Fn rises above the threshold indicated by the TUTRAN-GPS Change Limit IE. The change of TUTRAN-GPS value (Fn) is calculated according to the following:
Fn=0 for n=0
Fn = (Mn – Mn-1) mod 37158912000000 – ((SFNn – SFNn-1) mod 4096) *10*3.84*10^3*16 + Fn-1
		for n>0
Fn is the change of the TUTRAN-GPS value expressed in unit [1/16 chip] when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
Mn is the latest measurement result received after point C in the measurement model (TS 25.302 [25]), measured at SFNn.
Mn-1 is the previous measurement result received after point C in the measurement model (TS 25.302 [25]), measured at SFNn-1.
M1 is the first measurement result received after point C in the measurement model (TS 25.302 [25]), after the first Common Measurement Reporting at initiation or after the last event was triggered.
M0 is equal to the value reported in the first Common Measurement Reporting at initiation or in the Common Measurement Reporting when the event was triggered.
-	If the Predicted TUTRAN-GPS Deviation Limit IE is included in the TUTRAN-GPS Measurement Threshold Information IE, the Node B shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [25]), update the Pn and Fn  The Node B shall initiate the Common Measurement Reporting procedure and set n equal to zero when Fn rises above the threshold indicated by the Predicted TUTRAN-GPS Deviation Limit IE. The Pn and Fn are calculated according to the following:
Pn=b for n=0
Pn = ((a/16) * ((SFNn – SFNn-1) mod 4096)/100 +((SFNn – SFNn-1) mod 4096)*10*3.84*10^3*16 + Pn-1 ) mod 37158912000000		for n>0
Fn = min((Mn - Pn) mod 37158912000000, (Pn - Mn) mod 37158912000000)		for n>0
Pn is the predicted TUTRAN-GPS value when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
a is the last reported TUTRAN-GPS Drift Rate value.
b is the last reported TUTRAN-GPS value.
Fn is the deviation of the last measurement result from the predicted TUTRAN-GPS value (Pn ) when n measurements have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
Mn is the latest measurement result received after point C in the measurement model (TS 25.302 [25]), measured at SFNn.
M1 is the first measurement result received after point C in the measurement model (TS 25.302 [25]), after the first Common Measurement Reporting at initiation or after the last event was triggered.
The TUTRAN-GPS Drift Rate is determined by the Node B in an implementation-dependent way after point B in the measurement model (TS 25.302 [25]).
2.	If the Common Measurement Type IE is set to "SFN-SFN Observed Time Difference":
-	If the SFN-SFN Change Limit IE is included in the SFN-SFN Measurement Threshold Information IE, the Node B shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [25]), calculate the change of SFN-SFN value (Fn). The Node B shall initiate the Common Measurement Reporting procedure in order to report the particular SFN-SFN measurement which has triggered the event and set n equal to zero when Fn rises above the threshold indicated by the SFN-SFN Change Limit IE. The change of the SFN-SFN value is calculated according to the following:
Fn=0		for n=0
[FDD - Fn = (Mn – a) mod 614400		for n>0]
[TDD - Fn = (Mn – a) mod 40960		for n>0]
Fn is the change of the SFN-SFN value expressed in unit [1/16 chip] when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
a is the last reported SFN-SFN.
Mn is the latest measurement result received after point C in the measurement model (TS 25.302 [25]), measured at SFNn.
M1 is the first measurement result received after point C in the measurement model (TS 25.302 [25]) after the first Common Measurement Reporting at initiation or after the last event was triggered.
-	If the Predicted SFN-SFN Deviation Limit IE is included in the SFN-SFN Measurement Threshold Information IE, the Node B shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [25]), update the Pn and Fn The Node B shall initiate the Common Measurement Reporting procedure in order to report the particular SFN-SFN measurement which has triggered the event and set n equal to zero when the Fn rises above the threshold indicated by the Predicted SFN-SFN Deviation Limit IE. The Pn and Fn are calculated according to the following:
Pn=b for n=0
[FDD - Pn = ((a/16) * ((SFNn – SFNn-1) mod 4096)/100 + Pn-1 ) mod 614400		for n>0]
[FDD - Fn = min((Mn - Pn) mod 614400, (Pn - Mn) mod 614400)		for n>0]
[TDD - Pn = ((a/16) * (15*(SFNn – SFNn-1)mod 4096 + (TSn – TSn-1))/1500 + Pn-1 ) mod 40960		for n>0]
[TDD - Fn = min((Mn - Pn) mod 40960, (Pn - Mn) mod 40960)		for n>0]
Pn is the predicted SFN-SFN value when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
a is the last reported SFN-SFN Drift Rate value.
b is the last reported SFN-SFN value.
abs denotes the absolute value.
Fn is the deviation of the last measurement result from the predicted SFN-SFN value (Pn ) when n measurements have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
Mn is the latest measurement result received after point C in the measurement model (TS 25.302 [25]), measured at [TDD - the Time Slot TSn of] the Frame SFNn.
M1 is the first measurement result received after point C in the measurement model (TS 25.302 [25]) after the first Common Measurement Reporting at initiation or after the last event was triggered.
	The SFN-SFN Drift Rate is determined by the Node B in an implementation-dependent way after point B in the measurement model (TS 25.302 [25]).
3.	If the Common Measurement Type IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning":
-	If the TUTRAN-GANSS Change Limit IE is included in the TUTRAN-GANSS Measurement Threshold Information IE, the Node B shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [25]), calculate the change of TUTRAN-GANSS value (Fn). The Node B shall initiate the Common Measurement Reporting procedure and set n equal to zero when the absolute value of Fn rises above the threshold indicated by the TUTRAN-GANSS Change Limit IE. The change of TUTRAN-GANSS value (Fn) is calculated according to the following:
Fn=0 for n=0
Fn = (GAMn – GAMn-1) mod 5308416000000 – ((SFNn – SFNn-1) mod 4096) *10*3.84*10^3*16 + Fn-1
		for n>0
Fn is the change of the TUTRAN-GANSS value expressed in unit [1/16 chip] when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
GAMn is the latest GANSS measurement result received after point C in the GANSS measurement model, measured at SFNn.
GAMn-1 is the previous GANSS measurement result received after point C in the GANSS measurement model, measured at SFNn-1.
GAM1 is the first GANSS measurement result received after point C in the GANSS measurement model, after the first Common Measurement Reporting at initiation or after the last event was triggered.
GAM0 is equal to the value reported in the first Common Measurement Reporting at initiation or in the Common Measurement Reporting when the event was triggered.
GANSS measurement model is the timing between cell j and GANSS Time Of Day. TUE-GANSSj is defined as the time of occurrence of a specified UTRAN event according to GANSS time. The specified UTRAN event is the beginning of a particular frame (identified through its SFN) in the first detected path (in time) of the cell j CPICH, where cell j is a cell chosen by the UE. The reference point for TUE-GANSSj shall be the antenna connector of the UE. 
-	If the Predicted TUTRAN-GANSS Deviation Limit IE is included in the TUTRAN-GANSS Measurement Threshold Information IE, the Node B shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [25]), update the Pn and Fn. The Node B shall initiate the Common Measurement Reporting procedure and set n equal to zero when Fn rises above the threshold indicated by the Predicted TUTRAN-GANSS Deviation Limit IE. The Pn and Fn are calculated according to the following:
Pn=b for n=0
Pn = ((a/16) * ((SFNn – SFNn-1) mod 4096)/100 +((SFNn – SFNn-1) mod 4096)*10*3.84*10^3*16 + Pn-1 ) mod 5308416000000		for n>0
Fn = min((GAMn - Pn) mod 5308416000000, (Pn - GAMn) mod 5308416000000)		for n>0
Pn is the predicted TUTRAN-GANSS value when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
a is the last reported TUTRAN-GANSS Drift Rate value.
b is the last reported TUTRAN-GANSS value.
Fn is the deviation of the last measurement result from the predicted TUTRAN-GANSS value (Pn ) when n measurements have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.
GAMn is the latest GANSS measurement result received after point C in the GANSS measurement model, measured at SFNn.
GAM1 is the first GANSS measurement result received after point C in the GANSS measurement model, after the first Common Measurement Reporting at initiation or after the last event was triggered.
	The TUTRAN-GANSS Drift Rate is determined by the Node B in an implementation-dependent way after point B in the measurement model (TS 25.302 [25]).
If the Report Characteristics IE is not set to "On Demand", the Node B is required to perform reporting for a common measurement object, in accordance with the conditions provided in the COMMON MEASUREMENT INITIATION REQUEST message, as long as the object exists. If no common measurement object(s) for which a measurement is defined exists anymore, the Node B shall terminate the measurement locally, i.e. without reporting this to the CRNC.
If at the start of the measurement, the reporting criteria are fulfilled for any of Event A, Event B, Event E or Event F, the Node B shall initiate the Common Measurement Reporting procedure immediately, and then continue with the measurements as specified in the COMMON MEASUREMENT INITIATION REQUEST message.
Higher layer filtering:
The Measurement Filter Coefficient IE indicates how filtering of the measurement values shall be performed before measurement event evaluation and reporting.
The averaging shall be performed according to the following formula.

The variables in the formula are defined as follows:
Fn is the updated filtered measurement result
Fn-1 is the old filtered measurement result
Mn is the latest received measurement result from physical layer measurements, the unit used for Mn is the same unit as the reported unit in the COMMON MEASUREMENT INITIATION RESPONSE, COMMON MEASUREMENT REPORT messages or the unit used in the event evaluation (i.e. same unit as for Fn)
a = 1/2(k/2) , where k is the parameter received in the Measurement Filter Coefficient IE. If the Measurement Filter Coefficient IE is not present, a shall be set to 1 (no filtering)
In order to initialise the averaging filter, F0 is set to M1 when the first measurement result from the physical layer measurement is received.
Common measurement accuracy:
If the Common Measurement Type IE is set to "UTRAN GPS Timing of Cell Frames for UE Positioning", then the Node B shall use the UTRAN GPS Timing Measurement Accuracy Class IE included in the Common Measurement Accuracy IE according to the following:
-	If the UTRAN GPS Timing Measurement Accuracy Class IE indicates "Class A", then the Node B shall perform the measurement with highest supported accuracy within the accuracy classes A, B and C. 
-	If the UTRAN GPS Timing Measurement Accuracy Class IE indicates "Class B", then the Node B shall perform the measurement with highest supported accuracy within the accuracy classes B and C.
-	If the UTRAN GPS Timing Measurement Accuracy Class IE indicates "Class C", then the Node B shall perform the measurements with the accuracy according to class C.
If the Common Measurement Type IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning", then the Node B shall use the TUTRAN-GANSS Measurement Accuracy Class IE included in the Common Measurement Accuracy IE according to the following: 
-	If the TUTRAN- GANSS Measurement Accuracy Class IE indicates "Class A", then the Node B shall perform the measurement with highest supported accuracy within the accuracy classes A, B and C. 
-	If the TUTRAN- GANSS Measurement Accuracy Class IE indicates "Class B", then the Node B shall perform the measurement with highest supported accuracy within the accuracy classes B and C.
-	If the TUTRAN- GANSS Measurement Accuracy Class IE indicates "Class C", then the Node B shall perform the measurements with the accuracy according to class C.
Measurement Recovery Behavior:
If the Measurement Recovery Behavior IE is included in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall, if Measurement Recovery Behavior is supported, include the Measurement Recovery Support Indicator IE in the COMMON MEASUREMENT INITIATION RESPONSE message and perform the Measurement Recovery Behavior as described in subclause 8.2.9.2.
[FDD - Noise Floor Reporting:]
[FDD - If the Common Measurement Type IE is set to "Received Total Wide Band Power" and if the Reference Received Total Wide Band Power Reporting IE is included in the same COMMON MEASUREMENT INITIATION REQUEST message, the Node B may include the Reference Received Total Wide Band Power IE in the message used to report the common measurement.]
[FDD - If the Reference Received Total Wide Band Power Reporting IE is included in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall if supported, include the Reference Received Total Wide Band Power Support Indicator IE or the Reference Received Total Wide Band Power IE in the COMMON MEASUREMENT INITIATION RESPONSE.]
Response message:
If the Node B was able to initiate the measurement requested by the CRNC, it shall respond with the COMMON MEASUREMENT INITIATION RESPONSE message sent over the Node B Control Port. The message shall include the same Measurement ID that was used in the measurement request. Only in the case where the Report Characteristics IE is set to "On Demand" or "On Modification", the COMMON MEASUREMENT INITIATION RESPONSE message shall include the measurement result and also the Common Measurement Achieved Accuracy IE if the Common Measurement Type IE is set to "UTRAN GPS Timing of Cell Frames for UE Positioning" or "UTRAN GANSS Timing of Cell Frames for UE positioning".
[1.28Mcps TDD –If Time Slot LCR IE is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement response shall apply to all the available time slots in the frequency.]
[1.28Mcps TDD - If the Common Measurement Type IE is not set to "HS-DSCH Provided Bit Rate" and UARFCN IE is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement response shall apply to all the frequencies in the cell.]
[1.28Mcps TDD - If the Common Measurement Type IE is not set to "HS-DSCH Provided Bit Rate" and neither UARFCN IE nor Time Slot LCR IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement response shall apply to all available time slots in all frequencies.]
[1.28Mcps TDD - If Additional Time Slot LCR IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement results of the additional time slot (s) should be included in the COMMON MEASUREMENT INITIATION RESPONSE message.]
If the Common Measurement Type IE is set to "SFN-SFN Observed Time Difference" and the Report Characteristics IE is set to "On Demand" or "On Modification", all the available measurement results shall be reported in the Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information IE in the SFN-SFN Measurement Value Information IE and the Node B shall indicate in the Unsuccessful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information IE all the remaining neighbouring cells with no measurement result available in the COMMON MEASUREMENT INITIATION RESPONSE message. For all available measurement results, the Node B shall include in the Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information IE the SFN-SFN Quality IE and the SFN-SFN Drift Rate Quality IE, if available.
If the Common Measurement Type IE is set to "UTRAN GPS Timing of Cell Frames for UE Positioning" and the Report Characteristics IE is set to "On Demand" or "On Modification", the Node B shall include in the TUTRAN-GPS Measurement Value Information IE the TUTRAN-GPS Quality IE and the TUTRAN-GPS Drift Rate Quality IE, if available.
[FDD and 1.28Mcps TDD - If the Common Measurement Type IE is set to "Received Total Wide Band Power for Cell Portion", "Transmitted Carrier Power for Cell Portion", [FDD -"Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion"][1.28Mcps TDD - "Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion"], "HS-DSCH Required Power for Cell Portion" [1.28Mcps TDD – , "UL Timeslot ISCP for Cell Portion", "E-DCH Provided Bit Rate for Cell Portion", "UpPCH interference for Cell Portion"] or "HS-DSCH Provided Bit Rate for Cell Portion" and the Report Characteristics IE is set to "On Demand", all the available measurement results for each cell portion shall be included in the COMMON MEASUREMENT INITIATION RESPONSE message.]
If the Common Measurement Type IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning" and the Report Characteristics IE is set to "On Demand" or "On Modification", the Node B shall include in the TUTRAN-GANSS Measurement Value Information IE, the TUTRAN-GANSS Quality IE and the TUTRAN-GANSS Drift Rate Quality IE, if available.
8.2.8.3	Unsuccessful Operation

Figure 12: Common Measurement Initiation procedure, Unsuccessful Operation
If the requested measurement cannot be initiated [1.28Mcps TDD-in any time slot], the Node B shall send a COMMON MEASUREMENT INITIATION FAILURE message over the Node B Control Port. The message shall include the same Measurement ID that was used in the COMMON MEASUREMENT INITIATION REQUEST message and the Cause IE set to an appropriate value.
Typical cause values are as follows:
Radio Network Layer Cause:
-	Measurement not supported for the object.
-	Measurement Temporarily not Available
8.2.8.4	Abnormal Conditions
The allowed combinations of the Common Measurement Type received in the Common Measurement Type IE and the Common Measurement Object Type received in the COMMON MEASUREMENT INITIATION REQUEST message are shown in the table below. For not allowed combinations, the Node B shall regard the Common Measurement Initiation procedure as failed.
Table 3a: Allowed Common Measurement Type and Common Measurement Object Type combinations
Common Measurement Type
Common Measurement Object Type

Cell
RACH
Power Local Cell Group
E-DCH RACH
Received Total Wide Band Power 
X



Transmitted Carrier Power
X



Acknowledged PRACH Preambles

X


E-DCH RACH Report



X
UL Timeslot ISCP
X



UTRAN GPS Timing of Cell Frames for UE Positioning
X



SFN-SFN Observed Time Difference
X



[TDD - Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmission]
[FDD - Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission]
X



HS-DSCH Required Power
X



HS-DSCH Provided Bit Rate
X



Received Total Wide Band Power for Cell Portion
FDD and 1.28Mcps TDD only



Transmitted Carrier Power for Cell Portion
FDD and 1.28Mcps TDD only



Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion
FDD only



UpPCH interference
1.28 Mcps TDD only



DL Transmission Branch Load
FDD only

FDD only

HS-DSCH Required Power for Cell Portion
FDD and 1.28Mcps TDD only



HS-DSCH Provided Bit Rate for Cell Portion
FDD and 1.28Mcps TDD only



E-DCH Provided Bit Rate
X



E-DCH Non-serving Relative Grant Down Commands
FDD only



Received Scheduled E-DCH Power Share
FDD only



Received Scheduled E-DCH Power Share for Cell Portion
FDD only



UTRAN GANSS Timing of Cell Frames for UE Positioning
X



UL Timeslot ISCP for Cell Portion
1.28Mcps TDD only



Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH transmission for Cell Portion
1.28Mcps TDD only



E-DCH Provided Bit Rate for Cell Portion
1.28Mcps TDD only



UpPCH interference for Cell Portion
1.28Mcps TDD only




[TDD - If the Common Measurement Type requires the Time Slot Information but the [3.84Mcps TDD and 7.68Mcps TDD - Time Slot IE] [1.28Mcps TDD - Time Slot LCR IE] is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall regard the Common Measurement Initiation procedure as failed.]
[1.28Mcps TDD - For a multi-frequency cell, if the Additional Time Slot LCR IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, only on-demand and period measurement could be used, otherwise, the Node B shall reject the procedure by sending a COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE message.]
If the COMMON MEASUREMENT INITIATION REQUEST message contains the SFN-SFN Measurement Threshold Information IE (in the Measurement Threshold IE contained in the Report Characteristics IE) and it does not contain at least one IE, the Node B shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message.
If the COMMON MEASUREMENT INITIATION REQUEST message contains the TUTRAN-GPS Measurement Threshold Information IE (in the Measurement Threshold IE contained in the Report Characteristics IE) and it does not contain at least one IE, the Node B shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message.
If the Common Measurement Type IE is set to "SFN-SFN Observed Time Difference", but the Neighbouring Cell Measurement Information IE is not received in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall regard the Common Measurement Initiation procedure as failed.
If the Common Measurement Type IE is set to "UTRAN GPS Timing of Cell Frames for UE Positioning", but the TUTRAN-GPS Measurement Accuracy Class IE in the Common Measurement Accuracy IE is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall regard the Common Measurement Initiation procedure as failed. 
If the Common Measurement Type IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning", but the TUTRAN-GANSS Measurement Accuracy Class IE in the Common Measurement Accuracy IE is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the Node B shall regard the Common Measurement Initiation procedure as failed. 
[FDD - If the COMMON MEASUREMENT INITIATION REQUEST message contains the Reference Received Total Wide Band Power Reporting IE and it does not contain the Common Measurement Type IE set to "Received Total Wide Band Power", the Node B shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message.]
The allowed combinations of the Common Measurement Type and Report Characteristics Type are shown in the table below marked with "X". For not allowed combinations, the Node B shall regard the Common Measurement Initiation procedure as failed.
Table 4: Allowed Common Measurement Type and Report Characteristics Type combinations
Common Measurement Type
Report Characteristics Type

On Demand
Periodic
Event A
Event B
Event C
Event D
Event E
Event F
On Modification
Received Total Wide Band Power 
X
X
X
X
X
X
X
X

Transmitted Carrier Power
X
X
X
X
X
X
X
X

Acknowledged PRACH Preambles
X
X
X
X
X
X
X
X

E-DCH RACH Report
X
X
X
X
X
X
X
X

UL Timeslot ISCP
X
X
X
X
X
X
X
X

UTRAN GPS Timing of Cell Frames for UE Positioning
X
X






X
SFN-SFN Observed Time Difference
X
X






X
[TDD - Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmission]
[FDD - Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission]
X
X
X
X
X
X
X
X

HS-DSCH Required Power
X
X
X
X


X
X

HS-DSCH Provided Bit Rate
X
X







[FDD and 1.28Mcps TDD - Received Total Wide Band Power for Cell Portion]
X
X
X
X
X
X
X
X

[FDD and 1.28Mcps TDD - Transmitted Carrier Power for Cell Portion]
X
X
X
X
X
X
X
X

[FDD - Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion]
X
X
X
X
X
X
X
X

UpPTS interference
X
X
X
X
X
X
X
X

UpPCH interference for Cell Portion
X
X
X
X
X
X
X
X

DL Transmission Branch Load
X
X
X
X


X
X

[FDD and 1.28Mcps TDD - HS-DSCH Required Power for Cell Portion]
X
X
X
X


X
X

[FDD and 1.28Mcps TDD - HS-DSCH Provided Bit Rate for Cell Portion]
X
X







E-DCH Provided Bit Rate
X
X







E-DCH Provided Bit Rate for Cell Portion
X
X







E-DCH Non-serving Relative Grant Down Commands
X
X
X
X


X
X

Received Scheduled E-DCH Power Share
X
X
X
X
X
X
X
X

[FDD - Received Scheduled E-DCH Power Share for Cell Portion]
X
X
X
X
X
X
X
X

UTRAN GANSS Timing of Cell Frames for UE Positioning
X
X






X
[1.28Mcps TDD - UL Timeslot ISCP for Cell Portion]
X
X
X
X
X
X
X
X

[1.28Mcps TDD - Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH transmission for Cell Portion]
X
X
X
X
X
X
X
X


If the SFN IE is included in the COMMON MEASUREMENT INITIATION REQUEST message and the Report Characteristics IE is other than "Periodic", "On Demand" or "On Modification", the Node B shall regard the Common Measurement Initiation procedure as failed.
8.2.9	Common Measurement Reporting
8.2.9.1	General
This procedure is used by the Node B to report the result of measurements requested by the CRNC with the Common Measurement Initiation procedure.
8.2.9.2	Successful Operation

Figure 13: Common Measurement Reporting procedure, Successful Operation
If the requested measurement reporting criteria are met, the Node B shall initiate the Common Measurement Reporting procedure. The COMMON MEASUREMENT REPORT message shall use the Node B Control Port.
The Measurement ID IE shall be set to the Measurement ID provided by the CRNC when initiating the measurement with the Common Measurement Initiation procedure.
[1.28Mcps TDD –If Time Slot LCR IE is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement results of all the available time slots in the frequency should be included in the COMMON MEASUREMENT INITIATION REPORT message.]
[1.28Mcps TDD - If UARFCN IE is not present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement results of all the frequencies in the cell should be included in the COMMON MEASUREMENT INITIATION REPORT message.]
[1.28Mcps TDD - If neither UARFCN IE nor Time Slot LCR IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement results of all available time slots in all frequencies should be included in the COMMON MEASUREMENT INITIATION REPORT message.]
[1.28Mcps TDD - If Additional Time Slot LCR IE is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement results of the additional time slot (s) should be included in the COMMON MEASUREMENT INITIATION REPORT message.]
If the achieved measurement accuracy does not fulfil the given accuracy requirement (see ref. TS 25.133 [22] and TS 25.123 [23]) or the measurement is temporarily not available in case Measurement Recovery Behavior is supported, the Common Measurement Value Information IE shall indicate Measurement not Available. If the Node B was configured to perform the Measurement Recovery Behavior, the Node B shall indicate Measurement Available to the CRNC when the achieved measurement accuracy again fulfils the given accuracy requirement (see ref. TS 25.133 [22] and TS 25.123 [23]) and include the Measurement Recovery Report Indicator IE in the COMMON MEASUREMENT REPORT message if the requested measurement reporting criteria are not met.
For measurements included in the Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information IE, the Node B shall include the SFN-SFN Quality IE and the SFN-SFN Drift Rate Quality IE if available.
If the Common Measurement Type provided by RNC when initiating the measurement with the Common Measurement Initiation procedure was "UTRAN GPS Timing of Cell Frames for UE Positioning", then the Node B shall include in the TUTRAN-GPS Measurement Value Information IE the TUTRAN-GPS Quality IE and the TUTRAN-GPS Drift Rate Quality IE, if available.
If the Common Measurement Type provided by RNC when initiating the measurement with the Common Measurement Initiation procedure was "UTRAN GANSS Timing of Cell Frames for UE Positioning", then the Node B shall include in the TUTRAN-GANSS Measurement Value Information IE the TUTRAN-GANSS Quality IE and the TUTRAN-GANSS Drift Rate Quality IE, if available.
[FDD and 1.28Mcps TDD - For Received Total Wide Band Power for Cell Portion, Transmitted Carrier Power for Cell Portion, [FDD -Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission for Cell Portion][1.28Mcps TDD - Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for Cell Portion], HS-DSCH Required Power for Cell Portion, HS-DSCH Provided Bit Rate for Cell Portion[1.28Mcps TDD - , "E-DCH Provided Bit Rate for Cell Portion", "UpPCH interference for Cell Portion"], [FDD - Received Scheduled E-DCH Power Share for Cell Portion][1.28Mcps TDD - UL Timeslot ISCP for Cell Portion] measurements, all the available measurement results for each cell portion shall be included in the COMMON MEASUREMENT REPORT message.]
If the Common Measurement Object Type provided by RNC when initiating the measurement with the Common Measurement Initiation procedure was "Cell" or "RACH", then the Node B, if supported, shall include the C-ID IE in the COMMON MEASUREMENT REPORT message.
8.2.9.3	Abnormal Conditions
-
8.2.10	Common Measurement Termination
8.2.10.1	General
This procedure is used by the CRNC to terminate a measurement previously requested by the Common Measurement Initiation procedure.
8.2.10.2	Successful Operation

Figure 14: Common Measurement Termination procedure, Successful Operation
This procedure is initiated with a COMMON MEASUREMENT TERMINATION REQUEST message, sent from the CRNC to the Node B using the Node B Control Port.
Upon reception, the Node B shall terminate reporting of common measurements corresponding to the received Measurement ID IE.
8.2.10.3	Abnormal Conditions
-
8.2.11	Common Measurement Failure
8.2.11.1	General
This procedure is used by the Node B to notify the CRNC that a measurement previously requested by the Common Measurement Initiation procedure can no longer be reported.
8.2.11.2	Successful Operation

Figure 15: Common Measurement Failure procedure, Successful Operation
This procedure is initiated with a COMMON MEASUREMENT FAILURE INDICATION message, sent from the Node B to the CRNC using the Node B Control Port, to inform the CRNC that a previously requested measurement can no longer be reported. The Node B has locally terminated the indicated measurement.
8.2.11.3	Abnormal Conditions
-
8.2.12	Cell Setup
8.2.12.1	General
This procedure is used to set up a cell in the Node B. The CRNC takes the cell, identified via the C-ID IE, into service and uses the resources in the Node B identified via the Local Cell ID IE.
8.2.12.2	Successful Operation

Figure 16: Cell Setup procedure, Successful Operation
The procedure is initiated with a CELL SETUP REQUEST message sent from the CRNC to the Node B using the Node B Control Port. Upon Reception, the Node B shall reserve the necessary resources and configure the new cell according to the parameters given in the message.
[FDD - If the CELL SETUP REQUEST message includes one or more Secondary CPICH Information IE, the Node B shall configure and activate the Secondary CPICH(s) in the cell according to received configuration data.]
The Maximum Transmission Power IE value shall be stored in the Node B and, at any instance of time, the total maximum output power in the cell shall not be above this value. [1.28Mcps TDD - For a multi-frequency cell, at any instance of time, the total maximum output power for each frequency of the cell shall not be above this value.]
[FDD - If the Closed Loop Timing Adjustment Mode IE is included in the CELL SETUP REQUEST message, the value shall be stored in the Node B and applied when closed loop Feed-Back mode diversity is used on DPCH.]
[TDD - If the Reference SFN Offset IE is included in the CELL SETUP REQUEST message, the Node B where a reference clock is connected shall consider the SFN derived from the synchronisation port and the reference offset for reference time setting. All other Node Bs shall ignore the Reference SFN Offset IE if included.]
[FDD - If the IPDL Parameter Information IE is included in the CELL SETUP REQUEST message, the parameters defining IPDL shall be stored in the Node B and applied according to the IPDL Indicator IE value. If the Burst Mode Parameters IE is included in the IPDL FDD Parameters IE, the IPDL shall be operated in burst mode according to ref TS 25.214 [10].]
[3.84Mcps TDD and 7.68Mcps TDD - If the IPDL Parameter Information IE containing IPDL TDD Parameters IE is included in the CELL SETUP REQUEST message, the parameters defining IPDL in 3.84Mcps TDD and 7.68Mcps TDD modes shall be stored in the Node B and applied according to the IPDL Indicator IE value. If the Burst Mode Parameters IE is included in the IPDL TDD Parameters IE, the IPDL shall be operated in burst mode according to ref TS 25.224 [21].]
[1.28Mcps TDD - If the IPDL Parameter Information LCR IE containing IPDL TDD Parameters LCR IE is included in the CELL SETUP REQUEST message, the parameters defining IPDL in 1.28Mcps TDD mode shall be stored in the Node B and applied according to the IPDL Indicator IE value. For MBSFN only mode, this IE shall be ignored by the Node B. If the Burst Mode Parameters IE is included in the IPDL TDD Parameters LCR IE, the IPDL shall be operated in burst mode according to ref TS 25.224 [21].]
[1.28Mcps TDD - For a multi-frequency cell, the UARFCN Information LCR IE indicates information about the configuration of the frequency and timeslot of the secondary frequency/frequencies.]
When the cell is successfully configured, the Node B shall store the Configuration Generation ID IE value and send a CELL SETUP RESPONSE message as a response.
[FDD - When the cell is successfully configured the CPICH(s), Primary SCH, Secondary SCH, Primary CCPCH and BCH exist.][3.84Mcps TDD and 7.68Mcps TDD - When the cell is successfully configured the SCH, Primary CCPCH and BCH exist and the switching-points for the 3.84Mcps TDD / 7.68Mcps TDD frame structure are defined.] [1.28Mcps TDD - When the cell is successfully configured, the DwPCH, Primary CCPCH and BCH exist and the switching-points for the 1.28Mcps TDD frame structure are defined.] The cell and the channels shall be set to the state Enabled (TS 25.430 [6]).
[1.28Mcps TDD - For a multi-frequency cell, the Node B shall consider the cell as having been successfully configured as long as the primary frequency is normally setup. When the cell is successfully configured, the Node B shall respond with the CELL SETUP RESPONSE message.]
[TDD - The Node B shall ignore the DPCH/PUSCH/PRACH Constant Value IEs.]
[1.28Mcps TDD - For a multi-frequency cell, when the cell is successfully configured, the Node B shall configure the UpPCH channel of the primary frequency in the timeslot of UpPTS.]
[FDD - If the CELL SETUP REQUEST message includes Cell Portion Information IE, the Node B shall associate Associated Secondary CPICH IE to the cell portion indicated by Cell Portion ID IE and the Maximum Transmission Power for Cell Portion IE value shall be stored in the Node B and at any instance of time  the total maximum output power in the cell portion indicated by Cell Portion ID IE shall not be above this value.]
[FDD - If the MIMO Pilot Configuration IE is included in the CELL SETUP REQUEST message, then the parameters defining the pilot configuration for MIMO shall be stored in the Node B and applied when MIMO mode is used according to TS 25.214 [10].]
[3.84Mcps TDD and 7.68Mcps TDD - If the CELL SETUP REQUEST message includes the MBSFN Cell Parameter ID IE, then the Node B shall configure the associated timeslot to operate in MBSFN mode using the scrambling codes and midambles dictated by the MBSFN Cell Parameter ID IE.]
[1.28Mcps TDD - If the CELL SETUP REQUEST message includes the MBSFN Only Mode Indicator IE, the Node B shall configure the associated timeslot(s) to operate as MBSFN time slot(s) using the scrambling codes and basic midamble codes dictated by the Time Slot Parameter ID IE.]
[1.28Mcps TDD - If the cell is operating in MBSFN only mode, the DwPCH Information IE shall be ignored by the Node B.]
[1.28 Mcps TDD - If the cell is operating in MBSFN only mode, the PCCPCH shall be deployed on the MBSFN Special Time Slot (TS 25.221 [19]).]
[FDD - If the MIMO Pilot Configuration Extension IE is included in CELL SETUP REQUEST, then the parameters extending the pilot information for MIMO shall be stored in the Node B and applied when MIMO mode is used according to TS 25.214 [10]]
[FDD - If the MIMO with four transmit antennas Pilot Configuration IE is included in CELL SETUP REQUEST, then the parameters defining the pilot configuration for MIMO with four transmit antennas shall be stored in the Node B and applied when MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode is used according to TS 25.214 [10].]
8.2.12.3	Unsuccessful Operation

Figure 17: Cell Setup procedure: Unsuccessful Operation
If the Node B cannot set up the cell according to the information given in CELL SETUP REQUEST message the CELL SETUP FAILURE message shall be sent to the CRNC.
In this case, the cell is Not Existing in the Node B. The Configuration Generation ID shall not be changed in the Node B.
The Cause IE shall be set to an appropriate value.
Typical cause values are as follows:
Radio Network Layer Cause:
-	S-CPICH not supported
-	Requested Tx Diversity Mode not supported
-	Power level not supported
-	Node B Resources unavailable
-	IPDL not supported
-	[FDD - S-CPICH power offset support not available]

Miscellaneous Cause:
-	O&M Intervention
-	Control processing overload
-	HW failure
8.2.12.4	Abnormal Conditions
If the state of the cell already is Enabled or Disabled (TS 25.430 [6]) when the CELL SETUP REQUEST message is received in the Node B, it shall reject the configuration of the cell and all channels in the CELL SETUP REQUEST message by sending a CELL SETUP FAILURE message with the Cause IE set to "Message not compatible with receiver state".
If the Local Cell on which the cell is mapped does not belong to a Power Local Cell Group and the requested maximum transmission power indicated by the Maximum Transmission Power IE exceeds the Maximum DL Power Capability of the Local Cell, the Node B shall consider the procedure as having failed and send a CELL SETUP FAILURE message to the CRNC.
If the Local Cell on which the cell is mapped belongs to a Power Local Cell Group and the requested maximum transmission power indicated by Maximum Transmission Power IE exceeds the Maximum DL Power Capability of the Power Local Cell Group, the Node B shall consider the procedure as having failed and send a CELL SETUP FAILURE message to the CRNC.
8.2.13	Cell Reconfiguration
8.2.13.1	General
This procedure is used to reconfigure a cell in the Node B.
8.2.13.2	Successful Operation


Figure 18: Cell Reconfiguration procedure, Successful Operation
The procedure is initiated with a CELL RECONFIGURATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port. Upon Reception, the Node B shall reconfigure the cell according to the parameters given in the message.
[FDD - If the CELL RECONFIGURATION REQUEST message includes the Primary SCH Information IE, the Node B shall reconfigure the Primary SCH power in the cell according to Primary SCH Power IE value.]
[FDD - If the CELL RECONFIGURATION REQUEST message includes the Secondary SCH Information IE, the Node B shall reconfigure the Secondary SCH power in the cell according to the Secondary SCH Power IE value.]
[FDD - If the CELL RECONFIGURATION REQUEST message includes the Primary CPICH Information IE, the Node B shall reconfigure the Primary CPICH power in the cell according to the Primary CPICH Power IE value. The Node B shall adjust all the transmitted power levels relative to the Primary CPICH power according to the new value.]
[FDD - If the CELL RECONFIGURATION REQUEST message includes one or more Secondary CPICH Information IE, the Node B shall reconfigure the power for each Secondary CPICH in the cell according to their Secondary CPICH Power IE value.]
[3.84Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the SCH Information IE, the Node B shall reconfigure the SCH power in the cell according to the SCH Power IE value.]
[7.68Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the SCH Information 7.68Mcps IE, the Node B shall reconfigure the SCH power in the cell according to the SCH Power IE value.]
[TDD - If the CELL RECONFIGURATION REQUEST message includes the Timing Advance Applied IE, the Node B shall apply the necessary functions for Timing Advance in that cell including reporting of the Rx Timing Deviation measurement, according to the Timing Advance Applied IE value.]
[FDD - If the CELL RECONFIGURATION REQUEST message includes the Primary CCPCH Information IE, the Node B shall reconfigure the BCH power in the cell according to the BCH Power IE value.]
[1.28Mcps TDD and 3.84Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the PCCPCH Information IE, the Node B shall reconfigure the P-CCPCH power in the cell according to the PCCPCH Power IE value. The Node B shall adjust all the transmitted power levels relative to the Primary CCPCH power according to the new value.]
[7.68Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the PCCPCH Information 7.68Mcps IE, the Node B shall reconfigure the P-CCPCH power in the cell according to the PCCPCH Power IE value. The Node B shall adjust all the transmitted power levels relative to the Primary CCPCH power according to the new value.]
If the CELL RECONFIGURATION REQUEST message includes the Maximum Transmission Power IE, the value shall be stored in the Node B and at any instance of time the total maximum output power in the cell shall not be above this value.
[3.84Mcps TDD and  7.68Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the Time Slot Configuration IE, the Node B shall reconfigure switching-point structure in the cell according to the Time Slot IE value.]
[1.28Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the Time Slot Configuration LCR IE, the Node B shall reconfigure switching-point structure in the cell according to the Time Slot LCR IE value.]
[TDD - If the CELL RECONFIGURATION REQUEST message includes any of the DPCH/PUSCH/PRACH Constant Value IEs, the Node B shall ignore them]
[1.28Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the DwPCH Information IE, the Node B shall reconfigure the DwPCH power in the Cell according to the DwPCH Power IE.]
[FDD - If the CELL RECONFIGURATION REQUEST message includes the IPDL Parameter Information IE with the IPDL Indicator IE set to the value "Active" the Node B shall apply the IPDL in that cell according to the latest received parameters defined by the IPDL FDD Parameters IE. If the Burst Mode Parameters IE is included in the IPDL FDD Parameters IE, the IPDL shall be operated in burst mode according to ref TS 25.214 [10].]
[3.84Mcps TDD and 7.68Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the IPDL Parameter Information IE with the IPDL Indicator IE set to the value "Active", the Node B shall apply the IPDL in that cell according to the latest received parameters defined by the IPDL TDD Parameters IE. If the Burst Mode Parameters IE is included in the IPDL TDD Parameters IE, the IPDL shall be operated in burst mode according to ref TS 25.224 [21].]
[1.28Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the IPDL Parameter Information LCR IE with the IPDL Indicator IE set to the value "Active", the Node B shall apply the IPDL in that cell according to the latest received parameters defined by the IPDL TDD Parameters LCR IE. If the Burst Mode Parameters IE is included in the IPDL TDD Parameters LCR IE, the IPDL shall be operated in burst mode according to ref TS 25.224 [21].]
If the CELL RECONFIGURATION REQUEST message includes the IPDL Parameter Information IE with the IPDL Indicator IE set to the value "Inactive", the Node B shall deactivate the ongoing IPDL.
When the cell is successfully reconfigured, the Node B shall store the new Configuration Generation ID IE value and send a CELL RECONFIGURATION RESPONSE message as a response.
If the CELL RECONFIGURATION REQUEST message includes the Synchronisation Configuration IE, the Node B shall reconfigure the indicated parameters in the cell according to the value of the N_INSYNC_IND, N_OUTSYNC_IND and T_RLFAILURE IEs. When the parameters in the Synchronisation Configuration IE affect the thresholds applied to a RL set, the Node B shall immediately apply the new thresholds. When applying the new thresholds, the Node B shall not change the state or value of any of the timers and counters for which the new thresholds apply.
[FDD - If the CELL RECONFIGURATION REQUEST message includes Cell Portion Information IE, the Maximum Transmission Power for Cell Portion IE value shall be stored in the Node B and at any instance of time the total maximum output power in the cell portion indicated by Cell Portion ID IE shall not be above this value.]
[FDD - If the MIMO Pilot Configuration IE is included in the CELL RECONFIGURATION REQUEST message, then the parameters defining the pilot configuration for MIMO shall be stored in the Node B and applied when MIMO mode is used according to TS 25.214 [10].]
[3.84Mcps TDD and 7.68Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the MBSFN Cell Parameter ID IE, then the Node B shall configure the associated timeslot to operate in MBSFN mode using the scrambling code and midamble dictated by the MBSFN Cell Parameter ID IE.]
[1.28Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the UARFCN Information To Add LCR IE, the Node B shall reserve the necessary resource and add a secondary frequency to the cell according to the information indicated in the UARFCN Information To Add LCR IE.]
[1.28Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the UARFCN Information To Modify LCR IE, the Node B shall reconfigure the configuration of the secondary frequency within the cell according to the information indicated in the UARFCN Information To Modify LCR IE.]
[1.28Mcps TDD - If the CELL RECONFIGURATION REQUEST message includes the UARFCN Information To Delete LCR IE, the Node B shall remove the secondary frequency from the cell and any remaining dedicated channels on the secondary frequency according to the frequency information given in the UARFCN Information To Delete LCR IE. The states for the frequency within the cell shall be set to "Not existing". The Node B shall remove all Radio Links and all Node B Communication Contexts related to the secondary frequency within the cell. The Node B shall also initiate the release of the user plane transport bearers for the removed dedicated channels on the secondary frequency within the cell.]
[1.28 Mcps TDD - If the cell is operating in MBSFN only mode, the PCCPCH shall be deployed on the MBSFN Special Time Slot (TS 25.221 [19]).]
[FDD - If the MIMO Pilot Configuration Extension IE is included in CELL RECONFIGURATION REQUEST, then the parameters extending the pilot information for MIMO shall be stored in the Node B and applied when MIMO mode is used according to TS 25.214 [10].]
[FDD - If the MIMO with four transmit antennas Pilot Configuration IE is included in CELL RECONFIGURATION REQUEST, then the parameters defining the pilot configuration for MIMO with four transmit antennas shall be stored in the Node B and applied when MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode is used according to TS 25.214 [10].]
If the CELL RECONFIGURATION REQUEST message includes the Dormant Mode Indicator IE, the Node B shall initiate the requested function. If Dormant Mode Indicator IE = "Enter Dormant Mode", after completion of the reconfiguration to dormant mode there shall be no power transmitted in the cell. If the Dormant Mode Indicator IE = "Leave Dormant Mode", the Node B shall initiate reconfiguration of the cell and resume the normal operating mode.
8.2.13.3	Unsuccessful Operation


Figure 19: Cell Reconfiguration procedure: Unsuccessful Operation
If the Node B cannot reconfigure the cell according to the information given in CELL RECONFIGURATION REQUEST message, the CELL RECONFIGURATION FAILURE message shall be sent to the CRNC.
In this case, the Node B shall keep the old configuration of the cell and the Configuration Generation ID shall not be changed in the Node B.
The Cause IE shall be set to an appropriate value.
Typical cause values are as follows:
Radio Network Layer Cause:
-	Power level not supported
-	Node B Resources unavailable
-	IPDL not supported
-	[FDD - S-CPICH power offset support not available] 
-	[FDD - Requested Configuration Not Supported]
Miscellaneous Cause:
-	O&M Intervention
-	Control processing overload
-	HW failure
8.2.13.4	Abnormal Conditions
If the IPDL Indicator IE set to the value "Active" is included in the CELL RECONFIGURATION REQUEST message and there is active IPDL ongoing in the Node B, the Node B shall respond with the CELL RECONFIGURATION FAILURE message with the cause value "IPDL already activated".
If the IPDL Indicator IE set to the value "Active" is included in the CELL RECONFIGURATION REQUEST message and there is no IPDL stored in the Node B defining the IPDL, the Node B shall respond with the CELL RECONFIGURATION FAILURE message with the cause value "IPDL parameters not available".
If the Local Cell on which the cell is mapped does not belong to of a Power Local Cell Group and the requested maximum transmission power indicated by the Maximum Transmission Power IE exceeds the Maximum DL Power Capability of the Local Cell, the Node B shall consider the procedure as having failed and send a CELL RECONFIGURATION FAILURE message to the CRNC.
If the Local Cell on which the cell is mapped belongs to a Power Local Cell Group and the requested maximum transmission power indicated by Maximum Transmission Power IE exceeds the Maximum DL Power Capability of the Power Local Cell Group, the Node B shall consider the procedure as having failed and send a CELL RECONFIGURATION FAILURE message to the CRNC.
8.2.14	Cell Deletion
8.2.14.1	General
This procedure is used to delete a cell in the Node B.
8.2.14.2	Successful Operation

Figure 20: Cell Deletion procedure, Successful Operation
The procedure is initiated with a CELL DELETION REQUEST message sent from the CRNC to the Node B using the Node B Control Port. Upon reception, the Node B shall remove the cell and any remaining common and dedicated channels within the cell. The states for the cell and the deleted common channels shall be set to Not Existing (TS 25.430 [6]). The Node B shall remove all Radio Links from the Cell and all Node B Communication Contexts that as a result do not have a Radio Link. The Node B shall also initiate release of the user plane transport bearers for the removed common and dedicated channels except the case that there is at least one FACH channel in this cell using the same transport bearer existing in other cell(s) in the Node B. In this case, the Node B shall remove the cell and any remaining common and dedicated channels within the cell but keep the common transport bearer which is used by the remaining common transport channel(s) in other cell(s).
When the cell is deleted, the Node B shall send a CELL DELETION RESPONSE message as a response.
8.2.14.3	Unsuccessful Operation
-
8.2.14.4	Abnormal Conditions
If the CELL DELETION REQUEST message includes a C-ID IE value that is not existing in the Node B, the Node B shall respond with the CELL DELETION RESPONSE message.
8.2.15	Resource Status Indication
8.2.15.1	General
This procedure is used in the following cases:
1.	When a Local Cell becomes Existing at the Node B.
2.	When a Local Cell is to be deleted in Node B, i.e. becomes Not Existing.
3.	When the capabilities of the Local Cell change at the Node B.
4.	When a cell has changed its capability and/or its resource operational state at the Node B.
5.	When common physical channels and/or common transport channels have changed their capabilities at the Node B.
6.	When a Communication Control Port has changed its resource operational state at the Node B.
7.	When a Local Cell Group has changed its resource capability at the Node B.
8.	[1.28Mcps TDD - For a multi-frequency cell, when a cell has been successfully set up but a secondary frequency failure has occurred within the cell.]
Each of the above cases shall trigger a Resource Status Indication procedure and the RESOURCE STATUS INDICATION message shall contain the logical resources affected for that case and the cause value when applicable.
8.2.15.2	Successful Operation

Figure 21: Resource Status Indication procedure, Successful Operation
The procedure is initiated with a RESOURCE STATUS INDICATION message sent from the Node B to the CRNC using the Node B Control Port.
Local Cell Becomes Existing:
When a Local Cell becomes Existing at the Node B, the Node B shall make it available to the CRNC by sending a RESOURCE STATUS INDICATION message containing a "No Failure" Indication, the Local Cell ID IE and the Add/Delete Indicator IE set equal to "Add".
When the capacity credits and consumption laws are shared between several Local Cells, the Node B includes the Local Cell Group ID IE for the Local Cell. If the Local Cell Group Information IE has not already been reported in a previous RESOURCE STATUS INDICATION message, the Node B shall include the capacity credits and the consumption laws in the Local Cell Group Information IE [FDD - , including also the E-DCH capacity consumption law, if E-DCH is supported].
If the Local Cell IE contains both the DL Or Global Capacity Credit IE and the UL Capacity Credit IE, then the internal resource capabilities of the Local Cell are modelled independently in the Uplink and Downlink direction. If the UL Capacity Credit IE is not present, then the internal resource capabilities of the Local Cell are modelled as shared resources between Uplink and Downlink. If the Local Cell Group Information IE contains both the DL Or Global Capacity Credit IE and the UL Capacity Credit IE, then the internal resource capabilities of the Local Cell Group are modelled independently in the Uplink and Downlink direction. If the UL Capacity Credit IE is not present, then the internal resource capabilities of the Local Cell Group are modelled as shared resources between Uplink and Downlink.
If the Node B internal power resources are pooled for a group of Local Cells, the Node B shall include the Power Local Cell Group ID IE for the Local Cell. If the Power Local Cell Group Information IE has not already been reported in a previous RESOURCE STATUS INDICATION message, the Node B shall include this IE for the concerned Power Local Cell Group in this message. Furthermore, the sum of the Maximum DL Power Capability of all the Local Cells belonging to the same Power Local Cell Group shall not exceed the Maximum DL Power Capability of the concerned Power Local Cell Group.
If the Local Cell is HSDPA-capable when it becomes Existing, the Node B shall include the HSDPA Capability IE set to "HSDPA Capable" and may include HS-DSCH MAC-d PDU Size Capability IE for the Local Cell.
If the Local Cell is E-DCH-capable when it becomes Existing, the Node B shall include the E-DCH Capability IE set to "E-DCH Capable" and may include E-DCH MAC-d PDU Size Capability IE for the Local Cell.
If the Local Cell is MBMS-capable when it becomes Existing, the Node B shall include the MBMS Capability IE set to "MBMS Capable" for the Local Cell.
[FDD - If the Local Cell is F-DPCH-capable when it becomes Existing, the Node B shall include the F-DPCH Capability IE set to "F-DPCH Capable" for the Local Cell.]
[FDD - If the Local Cell is both HSDPA-capable and E-DCH-capable when it becomes Existing, then the Node B shall include the Continuous Packet Connectivity DTX-DRX Capability IE set to "Continuous Packet Connectivity DTX-DRX Capable" for the Local Cell when Continuous Packet Connectivity DTX-DRX is supported.]
[FDD - If the Local Cell is both HSDPA-capable and E-DCH-capable when it becomes Existing, then the Node B shall include the Continuous Packet Connectivity HS-SCCH less Capability IE set to "Continuous Packet Connectivity HS-SCCH less Capable" for the Local Cell when Continuous Packet Connectivity HS-SCCH less is supported.]
[FDD - If the Local Cell is MIMO-capable when it becomes Existing, then the Node B shall include the MIMO Capability IE set to "MIMO Capable" for the Local Cell.]
[FDD - If the Local Cell is SixtyfourQAM DL-capable when it becomes Existing, then the Node B shall include the SixtyfourQAM DL Capability IE set to "SixtyfourQAM DL Capable" for the Local Cell.]
[FDD - If the Local Cell is Enhanced FACH-capable when it becomes Existing, the Node B shall include the Enhanced FACH Capability IE set to "Enhanced FACH Capable" for the Local Cell.]
[FDD - If the Local Cell is SixteenQAM UL-capable when it becomes Existing, then the Node B shall include the SixteenQAM UL Capability IE set to "SixteenQAM UL Capable" for the Local Cell.]
[1.28Mcps TDD - If the Local Cell is MBSFN Only Mode-capable when it becomes Existing, the Node B shall include the MBSFN Only Mode Capability IE set to "MBSFN Only Mode Capable" for the Local Cell.]
[FDD - If the Local Cell is F-DPCH Slot Format-capable when it becomes Existing, then the Node B shall include the F-DPCH Slot Format Capability IE set to " F-DPCH Slot Format Capable" for the Local Cell.]
[1.28Mcps TDD - If the Local Cell is SixtyfourQAM DL-capable when it becomes Existing, then the Node B shall include the SixtyfourQAM DL Capability IE set to "SixtyfourQAM DL Capable" for the Local Cell.]
[FDD - If the Local Cell is Common E-DCH-capable when it becomes Existing, the Node B shall include the Common E-DCH Capability IE set to "Common E-DCH Capable" for the Local Cell.]
If the Local Cell is E-DPCCH Power Boosting-capable when it becomes Existing, the Node B shall include the E-DPCCH Power Boosting Capability IE set to " E-DPCCH Power Boosting Capable" for the Local Cell.
[FDD - If the Local Cell is both SixtyfourQAM DL-capable and MIMO-capable when it becomes Existing, then the Node B shall include the SixtyfourQAM DL and MIMO Combined Capability IE set to "SixtyfourQAM DL and MIMO Combined Capable" for the Local Cell when Combined SixtyfourQAM DL and MIMO is supported.]
[1.28Mcps TDD - If the Local Cell is Enhanced FACH-capable when it becomes Existing, the Node B shall include the Enhanced FACH Capability IE set to "Enhanced FACH Capable" for the Local Cell.]
[1.28Mcps TDD - The Node B shall include the Enhanced PCH Capability IE set to "Enhanced PCH Capable" for every Enhanced PCH-capable Local Cell.] 
[1.28Mcps TDD - The Node B shall include the Enhanced UE DRX Capability LCR IE set to " Enhanced UE DRX Capable " for every Enhanced UE DRX Capable Local Cell.]
[FDD - If the Local Cell is Multi Cell Capable when it becomes Existing, the Node B shall include the Multi Cell Capability Info IE and set the Multi Cell Capability IE value to "Multi Cell Capable" for the Local Cell, and if the cell can be the serving HS-DSCH then the possible cells to serve multicell adjacent and/or non-adjacent carrier operation (TS 25.133 [22]) (same or adjacent sector in the same Node B) that can act as secondary serving HS-DSCH shall be listed in the Possible Secondary Serving Cell List IE. For each cell in the Possible Secondary Serving Cell List IE that is Multi Cell E-DCH Capable, indicated in the Cell Capability Container IE with the "Multi Cell E-DCH Capability" bit = "1", and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the Local Cell as the corresponding cell of the primary uplink frequency, the Node B shall include the Multicell E-DCH Restriction IE set to "TRUE" in the Possible Secondary Serving Cell List IE.]
[1.28Mcps TDD - If the Local Cell is both HSDPA-capable and E-DCH-capable when it becomes Existing, then the Node B shall include the Continuous Packet Connectivity DRX Capability LCR IE set to " Continuous Packet Connectivity DRX Capable " for the Local Cell when Continuous Packet Connectivity DRX is supported.]
[1.28Mcps TDD - If the Local Cell is both HSDPA-capable and E-DCH-capable when it becomes Existing, then the Node B shall include the Semi-Persistent scheduling Capability LCR IE set to " Semi-Persistent scheduling Capable" for the Local Cell when Semi-Persistent scheduling operation is supported.][1.28Mcps TDD- If the Local Cell is MIMO-capable when it becomes Existing, then the Node B shall include the MIMO Capability IE set to "MIMO Capable" for the Local Cell.]
[1.28Mcps TDD - If the Local Cell is both SixtyfourQAM DL-capable and MIMO-capable when it becomes Existing, then the Node B shall include the SixtyfourQAM DL and MIMO Combined Capability IE set to "SixtyfourQAM DL and MIMO Combined Capable" for the Local Cell when Combined SixtyfourQAM DL and MIMO is supported.]
[FDD - If the Local Cell is Enhanced UE DRX-capable when it becomes Existing, the Node B shall include the Enhanced UE DRX Capability IE set to " Enhanced UE DRX Capable" for the Local Cell.] 
[1.28Mcps TDD- If the Local Cell is Cell Portion capable when it becomes Existing, then the Node B shall include the Cell Portion CapabilityLCR IE set to " Cell Portion Capable" for the Local Cell.]
[FDD - If the Local Cell is MIMO-capable  and supports the MIMO Power Offset For S-CPICH Capability when it becomes Existing, the Node B shall include the MIMO Power Offset For S-CPICH Capability IE set to " S-CPICH Power Offset Capable " for the Local Cell.]
[FDD - If the Local Cell is MIMO-capable and supports DL control channels in transmit diversity for MIMO UEs (when MIMO is active and P-CPICH is not transmitted in diversity mode (TS 25.211 [7])) when it becomes Existing, the Node B shall include the TX Diversity on DL Control Channels by MIMO UE Capability IE set to "DL Control Channel Tx Diversity for MIMO UE with non-diverse P-CPICH Capable".]
[FDD - If the Local Cell is Single Stream MIMO-capable when it becomes Existing, then the Node B shall include the Single Stream MIMO Capability IE set to "Single Stream MIMO Capable" for the Local Cell.]
[FDD - If the Local Cell is HS-DSCH Dual Band Capable when it becomes Existing, the Node B shall include the Dual Band Capability Info IE and set the Dual Band Capability IE value to "Dual Band Capable" for the Local Cell. If the cell can be the serving HS-DSCH then the possible cells to serve dual band carrier operation (TS 25.133 [22]) (same sector) that can act as secondary serving HS-DSCH shall be listed in the Possible Secondary Serving Cell List IE If the Local Cell is E-DCH Dual Band Capable, the Node B shall include the Dual Band E-DCH Capability IE in the Dual Band Capability Info IE, and set its value to "Dual Band Capable". For each cell in the Possible Secondary Serving Cell List IE that is Multi Band E-DCH Capable, and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the Local Cell as the corresponding cell of the primary uplink frequency, the Node B shall include the Multicell E-DCH Restriction IE set to "TRUE" in the Possible Secondary Serving Cell List IE.]
 [FDD - If the local cell is capable of at least one feature listed in 9.2.2.129 when it becomes existing, the Node B shall include the Cell Capability Container IE and indicate the capabilities listed in 9.2.2.129 for the local cell.] 
[1.28Mcps TDD - If the Local Cell is TS0-capable when it becomes Existing, the Node B shall include the TS0 Capability LCR IE set to "TS0 Capable" for every TS0 Capable Local Cell.] 
[FDD - If the Local Cell, when it becomes Existing, is MIMO-capable and/or Single Stream MIMO-capable and configuration of the precoding weight set restriction defined in TS 25.331 [18] is preferred, the Node B may include the Precoding Weight Set Restriction IE set to "Preferred" for the Local Cell.] 
[1.28Mcps TDD- If the local cell is capable of at least one feature listed in 9.2.3.115 when it becomes existing, the Node B shall include the Cell Capability Container TDD LCR IE and indicate the capabilities listed in 9.2.3.115 for the local cell.]
[1.28Mcps TDD - If the local cell is capable of at least one feature listed in 9.2.3.119 when it becomes existing, the Node B shall include the MU-MIMO Capability Container IE and indicate the capabilities listed in 9.2.3.119 for the local cell.]
[1.28Mcps TDD - If the Local Cell is Adaptive Special Burst Power Capable when it becomes Existing, the Node B shall include the Adaptive Special Burst Power Capability LCR IE set to "Adaptive Special Burst Power Capable" for every Adaptive Special Burst Power Capable Local Cell.]
Local Cell Deletion:
When a Local Cell is to be deleted in the Node B, i.e. becomes Not Existing, the Node B shall withdraw the Local Cell from the CRNC by sending a RESOURCE STATUS INDICATION message containing a "No Failure" Indication, the Local Cell ID IE and the Add/Delete Indicator IE set to "Delete". The Node B shall not withdraw a previously configured cell at the Node B that the CRNC had configured using the Cell Setup procedure, until the CRNC has deleted that cell at the Node B using the Cell Delete procedure.
Capability Change of a Local Cell:
When the capabilities of a Local Cell change at the Node B, the Node B shall report the new capability by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication and the Local Cell ID IE.
The Node B shall include the Minimum DL Power Capability IE when it is known by the Node B.
If the maximum DL power capability of the Local Cell has changed, the new capability shall be indicated in the Maximum DL Power Capability IE.
If the DL capability for supporting the minimum spreading factor has changed, the new capability shall be indicated in the Minimum Spreading Factor IE.
[TDD - If the availability of the Reference clock connected to a Local Cell has changed, the new availability condition shall be indicated in the Reference Clock Availability IE.]
The Cause IE in the RESOURCE STATUS INDICATION message shall be set to the appropriate value.
If the internal resource capabilities of the Local Cell are affected, it shall be reported in the following way:
-	If the internal resource capabilities of the Local Cell are modelled as shared resources between Uplink and Downlink, the new capacity shall be reported in the DL Or Global Capacity Credit IE.
-	If the internal resource capabilities of the Local Cell are modelled independently in the Uplink and Downlink direction, then the DL Or Global Capacity Credit IE and the UL Capacity Credit IE shall be present in the RESOURCE STATUS INDICATION.
If the Capacity Consumption Law for Common Channels has changed for the Local Cell, the new law shall be reported by the Node B in the Common Channels Capacity Consumption Law IE.
If the Capacity Consumption Law for Dedicated Channels has changed for the Local Cell, the new law shall be reported by the Node B in the Dedicated Channels Capacity Consumption Law IE.
[FDD - If the Capacity Consumption Law for E-DCH has changed for the Local Cell, the new law shall be reported by the Node B in the E-DCH Capacity Consumption Law IE.]
[TDD - If the Capacity Consumption Law for E-DCH has changed for the Local Cell, the new law shall be reported by the Node B in the E-DCH TDD Capacity Consumption Law IE.]
If the HSDPA capability has changed for the Local Cell, the new capability shall be indicated in the HSDPA Capability IE.
If the HS-DSCH MAC-d PDU Size Capability has changed for the Local Cell, the new capability shall be indicated in the HS-DSCH MAC-d PDU Size Capability IE.
If the E-DCH capability has changed for the Local Cell, the new capability shall be indicated in the E-DCH Capability IE. [FDD - The Node B shall include the E-DCH Capability IE if any of the E-DCH TTI2ms, SF or HARQ Combining capabilities has changed for the E-DCH capable Local Cell.]
If the E-DCH MAC-d PDU Size Capability has changed for the Local Cell, the new capability shall be indicated in the E-DCH MAC-d PDU Size Capability IE.
If the MBMS capability has changed for the Local Cell, the new capability shall be indicated in the MBMS Capability IE.
[FDD - If the F-DPCH capability has changed for the Local Cell, the new capability shall be indicated in the F-DPCH Capability IE.]
[FDD - If the Continuous Packet Connectivity DTX-DRX capability has changed for the Local Cell that is both HSDPA-capable and E-DCH-capable, then the new capability shall be indicated in the Continuous Packet Connectivity DTX-DRX Capability IE. The Node B shall include the Continuous Packet Connectivity DTX-DRX Capability IE if the Max UE DTX Cycle supported by the Continuous Packet Connectivity DTX-DRX capable Local Cell has changed. If the Continuous Packet Connectivity HS-SCCH less capability has changed for the Local Cell that is both HSDPA-capable and E-DCH-capable, then the new capability shall be indicated in the Continuous Packet Connectivity HS-SCCH less Capability IE.]
[FDD - If the MIMO capability has changed for the Local Cell, then the new capability shall be indicated in the MIMO Capability IE.]
[FDD - If the SixtyfourQAM DL capability has changed for the Local Cell, then the new capability shall be indicated in the SixtyfourQAM DL Capability IE.]
[FDD - If the Enhanced FACH capability has changed for the Local Cell, the new capability shall be indicated in the Enhanced FACH Capability IE. The Node B shall include the Enhanced FACH Capability IE if the Enhanced PCH capability has changed for the Enhanced PCH capable Local Cell.]
[FDD - If the SixteenQAM UL capability has changed for the Local Cell, then the new capability shall be indicated in the SixteenQAM UL Capability IE.]
[1.28Mcps TDD - If the MBSFN Only Mode capability has changed for the Local Cell, the new capability shall be indicated in the MBSFN Only Mode Capability IE.] 
[FDD - If the F-DPCH Slot Format capability has changed for the Local Cell, then the new capability shall be indicated in the F-DPCH Slot Format Capability IE.]
[1.28Mcps TDD - If the SixtyfourQAM DL capability has changed for the Local Cell, then the new capability shall be indicated in the SixtyfourQAM DL Capability IE.]
[FDD - If the Common E-DCH capability has changed for the Local Cell, the new capability shall be indicated in the Common E-DCH Capability IE. The Node B shall include the Common E-DCH Capabilitty IE if the E-AI capability has changed for the Common E-DCH capable Local Cell. The Node B shall include the Common E-DCH Capability IE if the HS-DPCCH capability for Common E-DCH has changed for the Common E-DCH capable Local Cell.]
If the Support for E-DPCCH Power Boosting Capability has changed for the Local Cell, the new capability shall be indicated in the E-DPCCH Power Boosting Capability IE.
[FDD – If the SixtyfourQAM DL and MIMO Combined capability has changed for the Local Cell that is both SixtyfourQAM DL-capable and MIMO-capable, then the new capability shall be indicated in the SixtyfourQAM DL and MIMO Combined Capability IE.]
[1.28Mcps TDD - If the Enhanced FACH capability has changed for the Local Cell, the new capability shall be indicated in the Enhanced FACH Capability IE. The Node B shall include the Enhanced FACH Capability IE if the Enhanced PCH capability has changed for the Enhanced PCH capable Local Cell.]
[1.28Mcps TDD - If the Enhanced PCH capability has changed for the local cell, the new capability shall be indicated in the Enhanced PCH Capability IE.]
[1.28Mcps TDD - If the Enhanced UE DRX capability has changed for the local cell, the new capability shall be indicated in the Enhanced UE DRX Capability LCR IE.]
[FDD - If the Multi Cell Capability, the list of possible secondary serving cells and/or cells restricted for use as an Additional E-DCH on the secondary uplink frequency have changed for the Local Cell, the new capability including the list of possible secondary serving cells, and optionally the Multicell E-DCH Restriction IE, shall be indicated in the Multi Cell Capability Info.]
[FDD - If the Dual Band Capability, the Dual Band E-DCH Capability, the list of possible secondary serving cells and/or cells restricted for use as an Additional E-DCH on the secondary uplink frequency have changed for the Local Cell, the new capability including the list of possible secondary serving cells, and optionally the Multicell E-DCH Restriction IE, shall be indicated in the Dual Band Capability IE]
[1.28Mcps TDD - If the Continuous Packet Connectivity DRX capability has changed for the Local Cell that is both HSDPA-capable and E-DCH-capable, then the new capability shall be indicated in the Continuous Packet Connectivity DRX Capability LCR IE. If the Semi-Persistent scheduling operation capability has changed for the Local Cell that is both HSDPA-capable and E-DCH-capable, then the new capability shall be indicated in the Semi-Persistent scheduling Capability LCR IE.]
[1.28Mcps TDD- If the MIMO capability has changed for the Local Cell, then the new capability shall be indicated in the MIMO Capability IE.]
[1.28Mcps TDD– If the SixtyfourQAM DL and MIMO Combined capability has changed for the Local Cell that is both SixtyfourQAM DL-capable and MIMO-capable, then the new capability shall be indicated in the SixtyfourQAM DL and MIMO Combined Capability IE.]
[FDD - If the Enhanced UE DRX capability has changed for the Local Cell, the new capability shall be indicated in the Enhanced UE DRX Capability IE.] 
[1.28Mcps TDD- If the Cell Portion capability has changed for the Local Cell, the new capability shall be indicated in the Cell Portion CapabilityLCR IE.]
[FDD - If the support for MIMO Power Offset For S-CPICH Capability has changed for the Local Cell, the new capability shall be indicated in the MIMO Power Offset For S-CPICH Capability IE.]
[FDD - If the support for DL control channels in transmit diversity for MIMO UEs (when MIMO is active and P-CPICH is not transmitted in diversity mode (TS 25.211 [7])) has changed for the Local Cell, the new capability shall be indicated in the TX Diversity on DL Control Channels by MIMO UE Capability IE.]
[FDD - If the Single Stream MIMO capability has changed for the Local Cell, then the new capability shall be indicated in the Single Stream MIMO Capability IE.]
[FDD - If any of the capabilities indicated 9.2.2.129 has changed for the Local Cell, the new capabilities shall be indicated in the Cell Capability Container IE.] 
[1.28Mcps TDD - If the TS0 capability has changed for the Local Cell, then the new capability shall be indicated in the TS0 Capability LCR IE.] 
[FDD - If the preference regarding configuration of the precoding weight set restriction defined in TS 25.331 [18] has changed for the Local Cell, the new value shall be indicated in the Precoding Weight Set Restriction IE.] 
[1.28Mcps TDD - If any of the capabilities indicated 9.2.3.115 has changed for the Local Cell, the new capabilities shall be indicated in the Cell Capability Container TDD LCR IE.]
[1.28Mcps TDD - If any of the capabilities indicated 9.2.3.119 has changed for the Local Cell, the new capabilities shall be indicated in the MU-MIMO Capability Container IE.]
[1.28Mcps TDD - If the Adaptive Special Burst Power capability has changed for the Local Cell, then the new capability shall be indicated in the Adaptive Special Burst Power Capability LCR IE.]
Capability Change of a Cell:
When the capabilities and/or resource operational state of a cell changes at the Node B, the Node B shall report the new capability and/or resource operational state by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication, the Resource Operational State IE and the Availability Status IE. The Cause IE in the RESOURCE STATUS INDICATION message shall be set to the appropriate value.
Capability Change of a Common Physical Channel and/or Common Transport Channel:
The Node B shall not delete any common or dedicated channels due to the cell being "Disabled". For all affected common and dedicated channels, the Node B shall report the impact to the CRNC with the relevant procedures.
When the capabilities and/or resource operational state of common physical channels and/or common transport channels have changed, the Node B shall report the new capability and/or resource operational state by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication, the Resource Operational State IE and the Availability Status IE set to appropriate values for the affected channel(s). The Cause IE in the RESOURCE STATUS INDICATION message shall be set to the appropriate value.
When a power value for a common physical channel and/or a common transport channel becomes beyond the supported power value range due to a change in capability in the Node B, it shall be reported to the CRNC in the RESOURCE STATUS INDICATION message, with the Resource Operational State IE set to "Enabled", the Availability Status IE set to "Degraded" and the Cause IE set to "Power level not supported". Affected channels shall use the nearest power value that is supported.
[1.28Mcps TDD - Capability Change of a UpPCH channel:]
When the capabilities of UpPCH channels which are not configured in the timeslot of UpPTS on one or multiple frequencies have changed, the Node B may include the UpPCH Information LCR IE in the RESOURCE STATUS INDICATION message.
Capability Change of a Communication Control Port:
When the resource operational state of a Communication Control Port has changed, the Node B shall report the new resource operational state by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication and the Communication Control Port ID IE. The Cause IE in the RESOURCE STATUS INDICATION message shall be set to the appropriate value.
Capability Change of HS-DSCH Resources:
When the resource operational state of the HS-DSCH resources has changed, the Node B shall report the new resource operational state by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication. The Cause IE in the RESOURCE STATUS INDICATION message shall be set to the appropriate value.
[1.28Mcps TDD - For a multi-frequency cell, the Node B may include the UARFCN IE in the HS-DSCH Resources Information IE to report the status of the HS-DSCH resources on the indicated frequency, the Node B may also not include any UARFCN IE in the HS-DSCH Resources Information IE to report the status of  the HS-DSCH resources for the whole cell.]
Capability Change of E-DCH Resources:
When the resource operational state of the E-DCH resources has changed, the Node B shall report the new resource operational state by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication. The Cause IE in the RESOURCE STATUS INDICATION message shall be set to the appropriate value.
[1.28Mcps TDD - For a multi-frequency cell, the Node B may include the UARFCN IE in the E-DCH Resources Information IE to report the status of the E-DCH resources on the indicated frequency, the Node B may also not include any UARFCN IE in the E-DCH Resources Information IE to report the status of the E-DCH resources for the whole cell.]
Capability Change of a Local Cell Group:
When the resource capabilities of a Local Cell Group change at the Node B, the Node B shall report the new capability by sending a RESOURCE STATUS INDICATION message containing a "Service Impacting" Indication and the Local Cell Group Information IE reporting the change. The Cause IE in the RESOURCE STATUS INDICATION message shall be set to an appropriate value. If the RESOURCE STATUS INDICATION message contains both the DL Or Global Capacity Credit IE and the UL Capacity Credit IE, then the internal resource capabilities of the Node B are modelled independently in the Uplink and Downlink direction. If the UL Capacity Credit IE is not present, then the internal resource capabilities of the Node B are modelled as shared resources between Uplink and Downlink.
If the Capacity Consumption Law for Common Channels has changed for the Local Cell Group, the new law shall be reported by the Node B in the Common Channels Capacity Consumption Law IE.
If the Capacity Consumption Law for Dedicated Channels has changed for the Local Cell Group, the new law shall be reported by the Node B in the Dedicated Channels Capacity Consumption Law IE.
[FDD - If the Capacity Consumption Law for E-DCH has changed for the Local Cell Group, the new law shall be reported by the Node B in the E-DCH Capacity Consumption Law IE.]
[TDD - If the Capacity Consumption Law for E-DCH has changed for the Local Cell Group, the new law shall be reported by the Node B in the E-DCH TDD Capacity Consumption Law IE.]
Capability Change of a Power Local Cell Group:
When the power capability of a Power Local Cell Group changes at the Node B, the Node B shall report the new capability by sending a RESOURCE STATUS INDICATION message with the Indication Type IE set equal to "Service Impacting" and the Power Local Cell Group Information IE reporting the change. The Cause IE in the RESOURCE STATUS INDICATION message shall be set to an appropriate value. In this case, the Node B shall also include the Maximum DL Power Capability IE in the Local Cell Information IE for all the Local Cells belonging to the concerned Power Local Cell Group. Furthermore, the sum of the Maximum DL Power Capability of all the Local Cells belonging to the same Power Local Cell Group shall not exceed the Maximum DL Power Capability of the concerned Power Local Cell Group.
[1.28Mcps TDD - For a multi-frequency cell, when a cell has been successfully setup but a secondary frequency failure has occurred, the Node B shall report the status of the secondary frequency indicated by UARFCN IE on which the failure occurred by immediately sending a RESOURCE STATUS INDICATION message with the Indication Type IE set equal to "Service Impacting", the Resource Operational State IE and the Availability Status IE. The Cause IE in the RESOURCE STATUS INDICATION message shall be set to an appropriate value.]
General:
When the RESOURCE STATUS INDICATION message is used to report an error, only one cause value for all reported objects can be sent in one message. When the RESOURCE STATUS INDICATION message is used to clear errors, only all errors for one object can be cleared per message. It is not possible to clear one out of several errors for one object.
[1.28Mcps TDD - For a multi-frequency cell, the Node B should report the status of the resources used for each frequency. A reporting method can be found in Annex E.]
8.2.15.3	Abnormal Conditions
-
8.2.16	System Information Update
8.2.16.1	General
The System Information Update procedure performs the necessary operations in order for the Node B to apply the correct scheduling of and/or to include the appropriate contents to the system information segments broadcast on the BCCH.
8.2.16.2	Successful Operation

Figure 22: System Information Update procedure, Successful Operation
The procedure is initiated with a SYSTEM INFORMATION UPDATE REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
The Node B shall consider the requested updates to the BCCH schedule in the same order as the MIB/SB/SIB information is included in the SYSTEM INFORMATION UPDATE REQUEST message.
If the SYSTEM INFORMATION UPDATE REQUEST message includes the BCCH Modification Time IE, the updates to the BCCH schedule (possibly consisting of IB occurrence additions, IB occurrence deletions and IB occurrence contents updates) indicated in the SYSTEM INFORMATION UPDATE REQUEST message shall be applied by the Node B at the first time instance starting from the SFN value set by the BCCH Modification Time IE. If no BCCH Modification Time IE is included, the updates to the BCCH schedule shall be applied as soon as possible.
The Node B shall consider the requested updates to be the BCH mapped on SCCPCH if the BCH mapped on SCCPCH Indication IE is included in the SYSTEM INFORMATION UPDATE REQUEST message.
Information Block addition:
If the SYSTEM INFORMATION UPDATE REQUEST message includes segments of a certain MIB/SB/SIB, the Node B shall assume that all segments for that Information Block are included in the message and ordered with increasing Segment Index (starting from 0). For each included segment, segment type information and IB SG POS IE are also given in the SYSTEM INFORMATION UPDATE REQUEST message.
The Node B shall determine the correct cell system frame number(s) (SFN) for transmission of the segments of system information, from the scheduling parameters provided in the SYSTEM INFORMATION UPDATE REQUEST message. The SFN for transmitting the segments shall be determined by the IB SG REP IE and IB SG POS IE such that:
-	SFN mod IB_SG_REP = IB_SG_POS
If the SYSTEM INFORMATION UPDATE REQUEST message contains Master Information Block (MIB) segments in addition to SIB or SB segments, the MIB segments shall first be sent in the physical channel by the Node B. Once these MIB segments have been sent in the physical channel, the updated SB/SIB segments shall then be sent in the physical channel.
Only if the inclusion of each new IB segment in the BCCH schedule leads to a valid segment combination according to TS 25.331 [18], the Node B shall accept the system information update.
If the SIB Originator IE value is set to "Node B", the Node B shall create the SIB segment of the SIB type given by the IB Type IE and autonomously update the SIB segment and apply the scheduling and repetition as given by the IB SG REP IE and IB SG POS IE.
SIBs originating from the Node B can only be SIBs containing information that the Node B can obtain on its own.
If the SYSTEM INFORMATION UPDATE REQUEST message contains SB3 segment in addition to SIB, the BCH mapped on SCCPCH is used. The SB3 segments shall first be sent in the physical channel SCCPCH by the Node B. Once the SB3 segment has been sent in the physical channel SCCPCH, the updated SIB segments shall then be sent in the physical channel SCCPCH.
Information Block deletion:
If an IB Deletion is indicated in an instance of MIB/SB/SIB information IE in the SYSTEM INFORMATION UPDATE REQUEST message, the Node B shall delete the IB indicated by the IB Type IE and IB OC ID IE from the transmission schedule on BCCH.
If the BCH mapped on SCCPCH Indication IE is included, and an IB Deletion is indicated in an instance of MIB/SB/SIB information IE in the SYSTEM INFORMATION UPDATE REQUEST message, the Node B shall delete the IB indicated by the IB Type IE and IB OC ID IE from the transmission schedule on BCH which is mapped on SCCPCH.
Information Block update:
If the SYSTEM INFORMATION UPDATE REQUEST message contains segments for an IB without IB SG REP IE and IB SG POS IE and there is already an IB in the BCCH schedule with the same IB Type and IB OC ID which is not requested to be deleted from the BCCH schedule by an IB deletion indicated in a MIB/SB/SIB information IE repetition present in the SYSTEM INFORMATION UPDATE REQUEST message before the IB segments are included, then the Node B shall only update the contents of the IB segments without any modification in segment scheduling.
If the SYSTEM INFORMATION UPDATE REQUEST message contains the BCH mapped on SCCPCH Indication IE and the segments for an IB without IB SG REP IE and IB SG POS IE and there is already an IB in the BCH mapped on SCCPCH schedule with the same IB Type and IB OC ID which is not requested to be deleted from the BCH mapped on SCCPCH schedule by an IB deletion indicated in a MIB/SB/SIB information IE repetition present in the SYSTEM INFORMATION UPDATE REQUEST message before the IB segments are included, then the Node B shall only update the contents of the IB segments without any modification in segment scheduling.
If the Node B successfully completes the updating of the physical channel scheduling cycle according to the parameters given in the SYSTEM INFORMATION UPDATE REQUEST message, it shall respond to the CRNC with a SYSTEM INFORMATION UPDATE RESPONSE message.
8.2.16.3	Unsuccessful Operation

Figure 23: System Information Update procedure, Unsuccessful Operation
If the Node B is unable to update the physical channel scheduling cycle according to all the parameters given in the SYSTEM INFORMATION UPDATE REQUEST message, it shall respond with a SYSTEM INFORMATION UPDATE FAILURE message with an appropriate cause value.
The Node B shall not incorporate any of the requested changes into the physical channel scheduling cycle, and the previous system information configuration shall remain intact.
Typical cause values are:
Radio Network Layer Cause:
-	SIB Origination in Node B not Supported
-	BCH mapped on SCCPCH scheduling error
Miscellaneous Cause:
-	Hardware failure
-	Control Processing overload
-	O&M Intervention
8.2.16.4	Abnormal Conditions
The Node B shall reject, with the cause value "SIB origination in Node B not supported", requests for Node B originated system information blocks that make use of a value tag.
The Node B shall reject the requested update with cause value "BCCH scheduling error" if:
-	After having handled a certain MIB/SB/SIB information IE repetition, an illegal BCCH schedule results;
-	If a MIB/SB/SIB Information IE repetition includes an IB SG REP IE or an IB SG POS IE and there is already an IB in the BCCH schedule with the same IB Type and IB OC ID which is not requested to be deleted from the BCCH schedule by an IB deletion indicated in a MIB/SB/SIB information IE repetition present in the SYSTEM INFORMATION UPDATE REQUEST message before the IB addition is indicated. This rule shall apply even if the scheduling instructions in IB SG REP IE and IB SG POS IE were the same as the current scheduling instructions for the concerned IB;
-	If a MIB/SB/SIB Information IE repetition includes no IB SG REP IE and IB SG POS IE and there is no IB in the BCCH schedule with the same IB Type and IB OC ID;
-	If a MIB/SB/SIB Information IE repetition includes no IB SG REP IE and IB SG POS IE and there is already an IB in the BCCH schedule with the same IB Type and IB OC ID but it is requested to be deleted from the BCCH schedule by an IB deletion indicated in a MIB/SB/SIB information IE repetition present in the SYSTEM INFORMATION UPDATE REQUEST message before the IB addition is indicated.
The Node B shall reject the requested update with cause value "BCH mapped on SCCPCH scheduling error":
-	If a MIB/SB/SIB Information IE repetition includes the MIB segement and the SB3 segment in the SYSTEM INFORMATION UPDATE REQUEST message.
-	If a MIB/SB/SIB Information IE repetition includes the SB3 segment in the SYSTEM INFORMATION UPDATE REQUEST message, but the BCH mapped to SCCPCH Indication IE is not set to “InUse”.
8.2.17	Radio Link Setup
8.2.17.1	General
This procedure is used for establishing the necessary resources for a new Node B Communication Context in the Node B.
[FDD - The Radio Link Setup procedure is used to establish one or more radio links. The procedure establishes one or more DCHs on all radio links, and in addition, it can include the establishment of an HS-DSCH on one radio link and it can include the establishment of an E-DCH on one or more radio links.]
[TDD - The Radio Link Setup procedure is used to establish one radio link including one or more transport channels. The transport channels can be a mix of DCHs, DSCHs, and USCHs, or DCHs and an HS-DSCH, or DCHs, an HS-DSCH and an E-DCH, including also combinations where one or more transport channel types are not present.]
8.2.17.2	Successful Operation

Figure 24: Radio Link Setup procedure, Successful Operation
The procedure is initiated with a RADIO LINK SETUP REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
Upon reception of the RADIO LINK SETUP REQUEST message, the Node B shall reserve necessary resources and configure the new Radio Link(s) according to the parameters given in the message.
The Node B shall prioritise resource allocation for the RL(s) to be established according to Annex A.
If the UE Aggregate Maximum Bit Rate IE is contained in the RADIO LINK SETUP REQUEST message, the Node B shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE.
[FDD - If the Usefulness of Battery Optimization IE is contained in the RADIO LINK SETUP REQUEST message, the Node B may store the received value and use it to determine whether this UE can benefit from battery optimization techniques.]
Transport Channels Handling:
DCH(s):
[TDD - If the DCH Information IE is present, the Node B shall configure the new DCH(s) according to the parameters given in the message.]
If the RADIO LINK SETUP REQUEST message includes a DCH Information IE with multiple DCH Specific Info IEs, then the Node B shall treat the DCHs in the DCH Information IE as a set of co-ordinated DCHs. The Node B shall include these DCHs in the new configuration only if it can include all of them in the new configuration.
If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to "Uplink DCH only", the Node B shall ignore the Transport Format Set IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.
If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to "Downlink DCH only", the Node B shall ignore the Transport Format Set IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.
[FDD - For DCHs which do not belong to a set of co-ordinated DCHs with the QE-Selector IE set to "selected", the Transport channel BER from that DCH shall be the base for the QE in the UL data frames. If no Transport channel BER is available for the selected DCH, the Physical channel BER shall be used for the QE, ref. TS 25.427 [16]. If the QE-Selector IE is set to "non-selected", the Physical channel BER shall be used for the QE in the UL data frames, ref. TS 25.427 [16].]
For a set of co-ordinated DCHs, the Transport channel BER from the DCH with the QE-Selector IE set to "selected" shall be used for the QE in the UL data frames, ref. TS 25.427 [16]. [FDD - If no Transport channel BER is available for the selected DCH, the Physical channel BER shall be used for the QE, ref. TS 25.427 [16]. If all DCHs have QE-Selector IE set to "non-selected", the Physical channel BER shall be used for the QE, ref. TS 25.427 [16]].
The Node B shall use the included UL FP Mode IE for a DCH or a set of co-ordinated DCHs as the FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the configuration.
The Node B shall use the included ToAWS IE for a DCH or a set of co-ordinated DCHs as the Time of Arrival Window Startpoint in the user plane for the DCH or the set of co-ordinated DCHs in the configuration.
The Node B shall use the included ToAWE IE for a DCH or a set of co-ordinated DCHs as the Time of Arrival Window Endpoint in the user plane for the DCH or the set of co-ordinated DCHs in the configuration.
The received Frame Handling Priority IE specified for each Transport Channel should be used when prioritising between different frames in the downlink on the radio interface in congestion situations within the Node B once the new RL(s) has been activated.
If the TNL QoS IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related DCH or set of co-ordinated DCHs.
[FDD - The Diversity Control Field IE indicates for each RL (except the first RL in the message) whether the Node B shall combine the concerned RL or not.
-	If the Diversity Control Field IE is set to"May", the Node B shall decide for either of the alternatives.
-	If the Diversity Control Field IE is set to "Must", the Node B shall combine the RL with one of the other RL.
-	If the Diversity Control Field IE is set to "Must not", the Node B shall not combine the RL with any other existing RL.
The signalled Diversity Control Field IE is applied to Dedicated Transport Channels (DCH) only. In case of E-DCH it shall always be assumed to be set to "Must". When a new RL is to be combined, the Node B shall choose which RL(s) to combine it with.]
[FDD - In the RADIO LINK SETUP RESPONSE message, the Node B shall indicate for each RL with the Diversity Indication in the RL Information Response IE whether the RL is combined or not.]
-	[FDD - In case of not combining with a RL previously listed in the RADIO LINK SETUP RESPONSE message or for the first RL in the RADIO LINK SETUP RESPONSE message, and if the DCH Indicator For E-DCH-HSDPA Operation IE is not included in the RADIO LINK SETUP REQUEST message, the Node B shall:]
-	[FDD - include in the DCH Information Response IE in the RADIO LINK SETUP RESPONSE message for which the Transport Bearer Not Requested Indicator IE was not included the Binding ID IE and Transport Layer Address IE for the transport bearer to be established for each DCH of this RL.]
-	[FDD - include in the RADIO LINK SETUP RESPONSE message the Transport Bearer Not Setup Indicator IE for every DCH for which establishment of a transport bearer has not taken place as a result of information in the Transport Bearer Not Requested Indicator IE in the RADIO LINK SETUP REQUEST message.]
-	[FDD - For the first E-DCH RL in the RADIO LINK SETUP RESPONSE message, the Node B shall:]
-	[FDD - include in the E-DCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message the Binding ID IE and Transport Layer Address IE for the transport bearer to be established for each E-DCH MAC-d flow of this RL.]
-	[FDD - include in the RADIO LINK SETUP RESPONSE message the Transport Bearer Not Setup Indicator IE for every E-DCH MAC-d flow for which establishment of a transport bearer has not taken place as a result of information in the Transport Bearer Not Requested Indicator IE in the RADIO LINK SETUP REQUEST message.]
-	[FDD - Otherwise in case of combining, the RL ID IE indicates (one of) the RL(s) previously listed in this RADIO LINK SETUP RESPONSE message with which the concerned RL is combined and if the ALCAP is not used and the transport bearer for the DCH is already established, the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE included in the RL Information IE for a specific RL in the RADIO LINK SETUP REQUEST message, shall not be used. In case of combining an E-DCH RL, one of the RLs previously listed in this RADIO LINK SETUP RESPONSE message including the E-DCH FDD Information Response IE shall be regarded as the RL with which the concerned E-DCH RL is combined.]
[TDD - The Node B shall include in the DCH Information Response IE in the RADIO LINK SETUP RESPONSE message the Binding ID IE and Transport Layer Address IE for the transport bearer to be established for each DCH of this RL.]
[TDD - If an E-DCH has been established, the Node B shall include in the E-DCH TDD Information Response IE in the RADIO LINK SETUP RESPONSE message the Binding ID IE and Transport Layer Address IE for the transport bearer to be established for each E-DCH MAC-d flow of the RL.]
In the case of a set of co-ordinated DCHs, the Binding ID IE and the Transport Layer Address IE shall be specified for only one of the DCHs in the set of co-ordinated DCHs [FDD - where the Transport Bearer Not Requested Indicator IE was not included].
[FDD - If the RADIO LINK SETUP REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer shall not be Established" for a DCH, then the Node B shall not establish a transport bearer for the concerned DCH and shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH in the RADIO LINK SETUP RESPONSE message.] 
[FDD - If the RADIO LINK SETUP REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer may not be Established" for a DCH and:]
-	[FDD - if the Node B establishes a transport bearer for the concerned DCH, the Node B shall include in the RADIO LINK SETUP RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the DCH being established.]
-	[FDD - if the Node B does not establish a transport bearer for the concerned DCH, the Node B shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH in the RADIO LINK SETUP RESPONSE message.]
[FDD – DCH Enhancements]:
[FDD – If the RADIO LINK SETUP REQUEST message includes the DCH Enhancements Information IE, then the Node B shall store the corresponding information  in the concerned Node B communication context, setup the requested DCH Enhancements operation [52], and:]
-	[FDD – Use the PO-SRB IE to set the power boost for the DL DPDCH in particular radio frames as defined in TS 25.214 [10].]
-	[FDD – Use the DL FET Mode IE to configure the DL FET mode [8, 52].]
-	[FDD – Use the information contained in the DL DCH Concatenation IE, if present, to identify the Transport Channels that shall be concatenated according to TS 25.212 [8].]
[TDD - DSCH(s)]:
[TDD - If the DSCH Information IE is present, the Node B shall configure the new DSCH(s) according to the parameters given in the message.]
[TDD - If the RADIO LINK SETUP REQUEST message includes the Transport Layer Address IE and Binding ID IE in the DSCH Information IE, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the DSCH.]
[TDD - The Node B shall include in the DSCH Information Response IE in the RADIO LINK SETUP RESPONSE the Binding ID IE and the Transport Layer Address IE for the transport bearer to be established for each DSCH of this RL.]
[TDD - If the RADIO LINK SETUP REQUEST message includes the TNL QoS IE in the DSCH TDD Information IE and if ALCAP is not used, the Node B may use the TNL QoS IE to determine the transport bearer characteristics to apply in the uplink for the related DSCH.]
[TDD - USCH(s)]:
[TDD - If the USCH Information IE is present, the Node B shall configure the new USCH(s) according to the parameters given in the message.]
[TDD - If the RADIO LINK SETUP REQUEST message includes the Transport Layer Address IE and Binding ID IE in the USCH Information IE, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the USCH.]
[TDD - If the RADIO LINK SETUP REQUEST message includes the TNL QoS IE in the USCH Information IE and if ALCAP is not used, the Node B may use the TNL QoS IE to determine the transport bearer characteristics to apply in the uplink for the related USCH.]
[TDD -If the USCH Information IE is present, the Node B shall include in the USCH Information Response IE in the RADIO LINK SETUP RESPONSE message the Binding ID IE and the Transport Layer Address IE for the transport bearer to be established for each USCH of this RL.]
HS-DSCH:
If the HS-DSCH Information IE is present in the RADIO LINK SETUP REQUEST message, then:
-	The Node B shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE.
-	The Node B shall include the HARQ Memory Partitioning IE in the [FDD - HS-DSCH FDD Information Response IE] [TDD - HS-DSCH TDD Information Response IE] in the RADIO LINK SETUP RESPONSE message. [FDD - The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than "8", if the MIMO Activation Indicator IE or the MIMO with four transmit antennas Activation Indicator IE or Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Information IE.] [1.28Mcps TDD- The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than "8", if the MIMO Activation Indicator IE is included in the HS-DSCH Information IE.]
-	The Node B shall include in the RADIO LINK SETUP RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of transport bearer for every HS-DSCH MAC-d flow being established.
-	If the RADIO LINK SETUP REQUEST message includes the Transport Layer Address IE and Binding ID IE in the HS-DSCH Information IE for an HS-DSCH MAC-d flow, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned HS-DSCH MAC-d flow.
-	If the RADIO LINK SETUP REQUEST message includes the MAC-hs Guaranteed Bit Rate IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
-	If the RADIO LINK SETUP REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
-	If the RADIO LINK SETUP REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue.
-	[FDD – If the RADIO LINK SETUP REQUEST message includes the Puncturing Handling in First Rate Matching Stage IE in the HS-DSCH Information IE , then the Node B shall, if supported, apply  the puncturing during first stage rate matching according to the Puncturing Handling in First Rate Matching Stage IE.]
-	The Node B shall include the HS-DSCH Initial Capacity Allocation IE in the [FDD - HS-DSCH FDD Information Response IE] [TDD - HS-DSCH TDD Information Response IE] in the RADIO LINK SETUP RESPONSE message for every HS-DSCH MAC-d flow being established, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK SETUP REQUEST message includes  HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH  Information IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended  IE to the values of the corresponding peer received in RADIO LINK SETUP REQUEST in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE for a Priority Queue including  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE.
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH Information IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the Measurement Power Offset IE in the HS-DSCH Information IE, then the Node B shall use the measurement power offset as described in ref TS 25.214 [10], subclause 6A.2.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - HS-SCCH Specific Information Response IE] [1.28Mcps TDD - HS-SCCH Specific Information Response LCR IE] [7.68Mcps TDD - HS-SCCH Specific Information Response 7.68Mcps IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the HARQ Preamble Mode IE in the HS-DSCH Information IE, then the Node B shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the Node B shall include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK SETUP RESPONSE message. If the HARQ Preamble Mode IE is not included or if the mode 0 is applied, then the Node B shall not include the HARQ Preamble Mode Activation Indicator IE in the RADIO LINK SETUP RESPONSE message.]
-	[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the HS-SICH SIR Target IE in the HS-DSCH Information IE, the Node B shall use this value to determine the HS-SICH  SIR Target. The HS-SICH SIR Target IE indicates the received UL SIR target of HS-SICH NACK for this UE.]
-	If the RADIO LINK SETUP REQUEST message includes the HS-DSCH MAC-d PDU Size Format  IE  in the HS-DSCH  Information IE, then the Node B shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]). 
-	If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.
-	[FDD - If the Serving Cell Change CFN IE is included in the RADIO LINK SETUP REQUEST message, then the Node B shall activate the resources that are allocated for the new serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC.]
-	[FDD - If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B shall activate the MIMO mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B may if the value is set to "allowed" use 64 QAM for the HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE with value set to "not allowed", then the Node B shall not use 64 QAM for the HS-DSCH Radio Link.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the HS-DSCH MAC-d PDU Size Format IE set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the RADIO LINK SETUP RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - If the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH FDD Information IE, then the Node B may use: ]
-	 [FDD - a different HS-SCCH in consecutive TTIs for this UE]
-	 [FDD - HS-SCCH orders for the case of HS-SCCH-less operation to this UE]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE the Node B may use the supported HSDPA functions for this UE. ]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the Node B shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[1.28Mcps TDD - If the TSN-Length IE is included in the HS-DSCH TDD Information IE, then the IE is used to indicate the TSN bits applied to the MAC-hs PDU frame.]
-	[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the Number of Supported Carriers IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B shall use this information to allocate HSDPA resources over multiple carriers for the UE.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK SETUP REQUEST message includes the Multi-carrier HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B shall use this information together with the HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information IE to allocate HSDPA resources over multiple carriers for the UE.] 
-	[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B may use this information in HSDPA resources allocation for the UE.]
-	[1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH over multiple carriers and include the HS-SCCH Specific Information Response LCR per UARFCN IE in the HS-DSCH TDD Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B shall include the HARQ Memory Partitioning per UARFCN IE in the HS-DSCH TDD Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[1.28Mcps TDD - If the Node B allows UE to apply HSDPA resources distributed over multiple carriers, the Node B may indicate the number of carriers actually used by the UE and include the Multi-Carrier number IE in the HS-DSCH TDD Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B may include the UsedFrequency IE in the HS-SCCH Specific Information Response LCR IE in the RADIO LINK SETUP RESPONSE message.]
-	[1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B may include the UARFCN IE in the HS-SCCH Specific Information Response LCR per UARFCN IE in the RADIO LINK SETUP RESPONSE message.]
-	[1.28 Mcps TDD - If the MIMO Activation Indicator IE is included in the HS-DSCH TDD Information IE, then, the Node B shall activate the MIMO mode for the HS-DSCH Radio Link, decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HS-DSCH TDD Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	If the RADIO LINK SETUP REQUEST message includes the DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DL RLC PDU Size Format IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24].
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the Priority Queue Information IE in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the Node B shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]
-	[FDD - If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B shall activate the Single Stream MIMO mode for the HS-DSCH Radio Link.]
-	[FDD - If the MIMO with four transmit antennas Activation Indicator IE or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B shall activate the MIMO with four transmit antennas mode, or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message]
-	[FDD - The Node B may include the Precoder weight set restriction IE in the HS-DSCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - If the CQI Feedback Cycle2 k IE and the CQI Cycle Switch Timer IE  is included in HS-DSCH FDD Information IE, then the Node B may use the indicated CQI Feedback Cycle2 k value, the CQI Cycle Switch Timer in HSDPA resources allocation for the UE.]
[FDD - Secondary Serving HS-DSCH:]
[FDD - If the Additional HS Cell Information RL Setup IE is present in the RADIO LINK SETUP REQUEST message, then:]
-	[FDD - The Node B shall setup the requested HS-PDSCH resources on the secondary serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - If the Serving Cell Change CFN IE is included in the RADIO LINK SETUP REQUEST message, then the Node B shall activate the resources that are allocated for the new secondary serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC.]
-	[FDD - If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.] 
-	[FDD - If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.]
-	[FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information IE, and more than one secondary serving HS-DSCH Radio Link is setup, then the Node B shall use this value in the physical layer.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
-	[FDD - If Sixtyfour QAM will not be used for the secondary serving HS-DSCH Radio Link, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - If the MIMO with four transmit antennas Activation Indicator IE or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - The Node B may include the Precoder weight set restriction IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.]
[FDD - Multiflow Setup]:
[FDD - If the Multiflow Information IE is present in HS-DSCH FDD Information IE in the RADIO LINK SETUP REQUEST message, then the Node B shall setup the requested Multiflow operation and then:]
-	[FDD – Use Total number of HS-DSCH cells IE to apply the HS-DPCCH format at the physical layer based on the total number of cells provided in this IE.]
-	[FDD – Use Role IE to know whether Multiflow cells configured at this Node B are assisting ones or not, for which Node B must read the correspondent part of the HS-DPCCH feedback channel.]
-	[FDD – Use MIMO IE to decide whether to apply the MIMO HS-DPCCH format at the physical layer.]
-	[FDD – If Timing IE is included, then Node B shall use this information to decide whether Multiflow cells configured at this Node B follow a different HS-DPCCH timing with an offset indicated by this IE.]
-	[FDD – If the Max number of HS-SCCH sets per Node B IE is included, then Node B shall use this information on the upper limit for the number HS-SCCH sets allocated and reported back to CRNC.]
-	[FDD – If the Assisting Repetition Factors IE is included, then the Node B shall use the values indicated in this IE within the Multiflow configuration.]
[FDD - E-DCH]:
[FDD - If the E-TFCS Information IE in the E-DPCH Information IE contains the E-DCH Minimum Set E-TFCI IE the Node B shall use the value for the related resource allocation operation.]
[FDD - If the E-TFCS Information IE in the E-DPCH Information IE contains the E-DPDCH Power Interpolation IE, the Node B shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the E-DPDCH Power Interpolation IE is not present, the Node B shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10].]
[FDD - If the E-TFCS Information IE in the E-DPCH Information IE contains the E-TFCI Boost Information IE, the Node B shall use the information according to TS 25.214 [10]. If the E-TFCI Boost Information IE is not present, the Node B shall use the E-TFCI BetaEC Boost value "127" in the algorithm defined in TS 25.214 [10].]
[FDD - If the RADIO LINK SETUP REQUEST message includes the E-DPCH Information IE, which contains the Minimum Reduced E-DPDCH Gain Factor IE, then the Node B shall use the value to determine the applicable minimum gain factor (βed,k,reduced,min) defined in TS 25.214 [10]. For the case the Minimum Reduced E-DPDCH Gain Factor IE is not available for the Node B Communication Context,  the Node B may use the default value defined in TS 25.331 [18]. ]
[FDD - If the E-DCH FDD Information IE is present in the RADIO LINK SETUP REQUEST message:]
-	[FDD - The Node B shall setup the requested E-DCH resources on the Radio Links indicated by the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the Transport Layer Address IE and Binding ID IE in the RL specific E-DCH FDD Information IE for an E-DCH MAC-d flow, then if the Transport Bearer Not Requested Indicator IE is not included for this E-DCH MAC-d flow, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. The Node B shall include in the RADIO LINK SETUP RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for every E-DCH MAC-d flow being established for which the Transport Bearer Not Requested Indicator IE was not included.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer shall not be Established" for an E-DCH MAC-d flow, then the Node B shall not establish a transport bearer for the concerned E-DCH MAC-d flow and shall include the Transport Bearer Not Setup Indicator IE for the corresponding E-DCH MAC-d flow in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer may not be Established" for an E-DCH MAC-d flow and:]
-	[FDD - if the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow, the Node B shall include in the RADIO LINK SETUP RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the E-DCH MAC-d flow being established.]
-	[FDD - if the Node B does not establish a transport bearer for the concerned E-DCH MAC-d flow, the Node B shall include the Transport Bearer Not Setup Indicator IE for the corresponding E-DCH MAC-d flow in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel Information IE in the E-DCH FDD Information IE, then the Node B shall use this information to optimise MAC-e scheduling decisions for the related reordering queue.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE, the Node B shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If in the RADIO LINK SETUP REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Non-Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE, if included, for the related resource allocation operation.]
-	[FDD - If in the RADIO LINK SETUP REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Scheduled Transmission Grant" the Node B shall assume scheduled grants being configured for the concerned E-DCH MAC-d flow.]
-	[FDD - If the TNL QoS IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
-	[FDD - The Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK SETUP RESPONSE message for every RL indicated by the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the Serving E-DCH RL IE indicating that the Serving E-DCH RL is in this Node B]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the RADIO LINK SETUP RESPONSE message for the initial grant for the serving E-DCH RL.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - The Node B may include the Default Serving Grant in DTX Cycle 2 IE in the RADIO LINK SETUP RESPONSE message for the serving E-DCH RL.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the Bundling Mode Indicator IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE and the Bundling Mode Indicator IE is set to "Bundling" and the E-TTI IE is set to "2ms", then the Node B shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the Node B shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the E-DCH Maximum Bitrate IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the E-DCH Processing Overload Level IE, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the E-DCH ReferencePower Offset IE, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the E-DCH Power Offset for Scheduling Info IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the UPH Filtering Measurement Forwarding Request IE, then the Node B shall use this instruction to handle the UE UPH filtering measurement forwarding.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the E-AGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.] 
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
-	[FDD - If the Serving Cell Change CFN  IE is included in the RADIO LINK SETUP REQUEST message, then the Node B shall activate the resources that are allocated for the new serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the SixteenQAM UL Operation Indicator IE, the Node B shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the SixteenQAM UL Operation Indicator IE.]
-	[FDD - If SixteenQAM UL Operation is activated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [32]. If SixteenQAM UL Operation is deactivated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [32].]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the E-RNTI IE in the E-DPCH Information IE but does not include the E-RNTI IE in the RL Information IE, the Node B shall use the information to detect the information related to the E-RNTI which is configured in the Node B when the UE was in Cell_FACH state.] 
[FDD – Additional E-DCH Setup:]
[FDD - If the Additional E-DCH Cell Information RL Setup Req IE is present in the RADIO LINK SETUP REQUEST message, then the Additional E-DCH Cell Information Setup Req IE defines the new configuration and then:]
-	[FDD - The Node B shall setup the E-DCH on the secondary uplink frequency and setup the requested E-DCH resource on the Radio Links and in the cells indicated by the E-DCH Additional RL ID IE and the C-ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
-	[FDD - If the DL Power Balancing Information IE and/or the Minimum Reduced E-DPDCH Gain Factor IE are present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] 
-	[FDD - If the Secondary UL Frequency Activation State IE is present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the Node B shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.] 
-	[FDD - If the Propagation Delay IE, the F-DPCH Slot Format IE and/or the E-RNTI IE are present in the Additional E-DCH RL Specific Information To Setup IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] 
-	[FDD - If the Extended Propagation Delay IE, the Primary CPICH Usage For Channel Estimation IE, the Secondary CPICH Information IE, the E-AGCH Power Offset IE, the E-RGCH Power Offset IE and/or the E-HICH Power Offset IE are present in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH RL Specific Information To Setup IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Maximum Bitrate IE, the E-DCH Processing Overload Level IE, the E-DCH Minimum Set E-TFCI IE, the Implicit Grant handling IE, the Minimum TEBS threshold IE and/or the DTX Information2 IE are present in the Additional E-DCH FDD Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] 
-	[FDD - If the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to "Separate Iub Transport Bearer Mode" the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
-	[FDD – If the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to "UL Flow Multiplexing Mode" the Node B shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.]
-	[FDD - If Separate Iub Transport Bearer Mode is used in the new configuration, then:]
-	[FDD - The Node B shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow and use the Transport Bearer Not Requested Indicator IE in the E-DCH MAC-d Flow Specific Information IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE to determine the transport bearer configuration in the new configuration for the MAC-d flow of the Secondary Uplink Frequency.] 
-	[FDD - If the Transport Layer Address IE and Binding ID IE is included for an E-DCH MAC-d flow in the Additional E-DCH MAC-d Flows Specific Information IE in the Additional E-DCH FDD Information IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow the Node B shall include in the RADIO LINK SETUP RESPONSE message the Binding ID IE and Transport Layer Address IE in the Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE for establishment of a transport bearer for every E-DCH MAC-d flow being established.] 
-	[FDD - If activation of power balancing for the Additional E-DCH RL by the RADIO LINK SETUP REQUEST message is supported by the Node B, the Node B shall include the DL Power Balancing Activation Indicator IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.]
-	[FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
-	[FDD - For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE for each Additional E-DCH RL in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD – If the Additional Serving E-DCH Radio Link is configured in the Node B, then:] 
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message for the initial grant for the Additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2IE.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.] 
-	[FDD - If the Serving Cell Change CFN IE is included in the RADIO LINK SETUP REQUEST message, then the Node B shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. If the Serving Cell Change CFN IE is not included then the Node B shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link
[FDD - E-DCH - HS-DSCH]:
[FDD - If the RADIO LINK SETUP REQUEST message includes the DCH Indicator For E-DCH-HSDPA Operation IE, then the Node B shall ignore the DCH Information IE in the RADIO LINK SETUP REQUEST message.]
[FDD – E-DCH decoupling operation]
[FDD – If the RADIO LINK SETUP REQUEST message includes the E-DCH Decoupling Indication IE then the Node B shall if supported use this indication for E-DCH decoupling operation.]
[TDD - E-DCH]:
[TDD - If the [3.84Mcps TDD - E-DCH Information IE] [1.28Mcps TDD - E-DCH Information 1.28Mcps IE][7.68Mcps TDD - E-DCH Information 7.68Mcps IE]is present in the RADIO LINK SETUP REQUEST message:]
-	[TDD - The Node B shall setup the requested E-DCH resources on the Radio Link indicated by the E-DCH Serving RL IE.]
-	[TDD - If the TNL QoS IE is included in the E-DCH MAC-d Flows Information TDD IE for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
-	[TDD - If the RADIO LINK SETUP REQUEST message includes the Transport Layer Address IE and Binding ID IE in the E-DCH MAC-d Flows Information TDD IE for an E-DCH MAC-d flow, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow.]
-	[TDD - If the RADIO LINK SETUP REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flows Information TDD IE, the Node B shall use this information for the related resource allocation operation.]
-	[TDD - If in the RADIO LINK SETUP REQUEST message the E-DCH Grant Type IE in the E-DCH MAC-d Flows Information TDD IE is set to "Non-scheduled" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants are configured for that E-DCH MAC-d flow and shall use the information within the [3.84Mcps - E-DCH Non-scheduled Grant Information TDD IE] [1.28Mcps - E-DCH Non-scheduled Grant Information LCR TDD IE] [7.68Mcps - E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE], if included, for the related resource allocation operation.]
-	[TDD - If in the RADIO LINK SETUP REQUEST message the E-DCH Grant Type IE in the E-DCH MAC-d Flows Information TDD IE is set to "Scheduled" the Node B shall assume that it may issue scheduled grants for the concerned E-DCH MAC-d flow.]
-	[TDD - If the RADIO LINK SETUP REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows Information TDD IE, then the Node B shall use this information to optimise MAC-e scheduling decisions for the related queue.]
-	[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the MAC-es Maximum Bit Rate LCR IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows Information TDD IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[TDD - If the RADIO LINK SETUP REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).]
-	[3.84Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the E-DCH TDD Maximum Bitrate IE in the E-DCH TDD Information IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the E-DCH Physical Layer Category LCR IE or Extended E-DCH Physical Layer Category LCR IE in the E-DCH TDD Information LCR IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[7.68Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the E-DCH TDD Maximum Bitrate 7.68Mcps IE in the E-DCH TDD Information 7.68Mcps IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[TDD - If the RADIO LINK SETUP REQUEST message includes the E-DCH Processing Overload Level IE in the [3.84Mcps TDD - E-DCH TDD Information IE] [7.68Mcps TDD - E-DCH TDD Information 7.68Mcps IE][1.28Mcps TDD - E-DCH TDD Information LCR IE], then if the Node B could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]
-	[TDD - If the RADIO LINK SETUP REQUEST message includes the E-DCH Power Offset for Scheduling Info IE in the [3.84Mcps TDD - E-DCH TDD Information IE] [1.28Mcps TDD - E-DCH TDD Information LCR IE] [7.68Mcps TDD - E-DCH TDD Information 7.68Mcps IE], then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
-	[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the Maximum Number of Retransmission for Scheduling Info LCR IE and the E-DCH Retransmission timer for Scheduling Info LCR IE in the E-DCH TDD Information LCR IE, then the Node B shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.]
-	[3.84Mcps TDD and 7.68Mcps TDD - The Node B shall allocate an E-RNTI identifier and include the E-RNTI identifier and the E-AGCH(s), [1.28Mcps - E-HICHs] assigned in the E-DCH Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the Multi-Carrier E-DCH Physical Layer Category LCR IE in the E-DCH TDD Information LCR IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.]
-	[1.28Mcps TDD - If the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE is not present and if the RADIO LINK SETUP REQUEST message includes the UE TS0 Capability LCR IE in the E-DCH TDD Information LCR IE, the Node B can use this information to allocate the downlink resources for the UE according to TS 25.306 [33].]
[1.28 Mcps TDD - Multi-Carrier E-DCH Setup:]
[1.28Mcps TDD - If the Multi-Carrier E-DCH Information IE is present in the RADIO LINK SETUP REQUEST message, then the Multi-Carrier E-DCH Information IE defines the new configuration and then:]
-	[1.28Mcps TDD - The Node B shall setup the requested E-DCH resource on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.]
-	[1.28Mcps TDD - The Node B shall use the corresponding PRXdes_base IE for power control on each uplink frequency according to TS 25.331 [18].] 
-	[1.28Mcps TDD - If the SNPL Carrier Group Indicator IE is present in the Multi-Carrier E-DCH Information LCR IE, the Node B shall use the information to determine which SNPL Carrier Group each frequency indicated by the UARFCN IE belongs to.]
-	[1.28Mcps TDD - If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "Separate Iub transport bearer mode", the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
-	[1.28Mcps TDD - If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "E-DCH UL flow multiplexing mode", the Node B shall use this mode in the new configuration and multiplex MAC-d flow received on the different carriers on one Iub transport bearer.]
-	[1.28Mcps TDD - If the Separate Iub transport bearer mode is used in the new configuration, then the Node B shall include the Binding ID IE and Transport Layer Address IE in the Multi-Carrier E-DCH Information Response LCR IE in the RADIO LINK SETUP RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
-	[1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration, then the Node B shall include the Binding ID IE and Transport Layer Address IE in the E-DCH TDD Information Response IE in the RADIO LINK SETUP RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
Physical Channels Handling:
[FDD - Compressed Mode]:
[FDD - If the RADIO LINK SETUP REQUEST message includes the Transmission Gap Pattern Sequence Information IE, the Node B shall store the information about the Transmission Gap Pattern Sequences to be used in the Compressed Mode Configuration. This Compressed Mode Configuration shall be valid in the Node B until the next Compressed Mode Configuration is configured in the Node B or the Node B Communication Context is deleted.]
[FDD - If the Downlink Compressed Mode Method IE in one or more Transmission Gap Pattern Sequence is set to "SF/2" in the RADIO LINK SETUP REQUEST message, the Node B shall use or not the alternate scrambling code as indicated for each DL Channelisation Code in the Transmission Gap Pattern Sequence Code Information IE.]
[FDD - If the RADIO LINK SETUP REQUEST message includes the Transmission Gap Pattern Sequence Information IE and the Active Pattern Sequence Information IE, the Node B shall use the information to activate the indicated Transmission Gap Pattern Sequence(s) in the new RL. The received CM Configuration Change CFN refers to the latest passed CFN with that value The Node B shall treat the received TGCFN IEs as follows:]
-	[FDD - If any received TGCFN IE has the same value as the received CM Configuration Change CFN IE, the Node B shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.]
-	[FDD - If any received TGCFN IE does not have the same value as the received CM Configuration Change CFN IE but the first CFN after the CM Configuration Change CFN with a value equal to the TGCFN IE has already passed, the Node B shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.]
-	[FDD - For all other Transmission Gap Pattern Sequences included in the Active Pattern Sequence Information IE, the Node B shall activate each Transmission Gap Pattern Sequence at the first CFN after the CM Configuration Change CFN with a value equal to the TGCFN IE for the Transmission Gap Pattern Sequence.]
[FDD - If the RADIO LINK SETUP REQUEST message includes the Transmission Gap Pattern Sequence Information IE and the Active Pattern Sequence Information IE and the concerned Node B Communication Context is configured to use F-DPCH in the downlink, the Node B shall not transmit the F-DPCH during the downlink transmission gaps according to TS 25.211 [7]. But in all slots outside of the downlink transmission gaps the Node B shall transmit the F-DPCH with the normal scrambling code and the assigned slot format, regardless of the configured downlink compressed mode method information and of the transmission gap pattern sequence code information, if existing.]
[FDD - If the RADIO LINK SETUP REQUEST message includes the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with C-ID IE included in Affected HS-DSCH serving cell List IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.]
[FDD - DL Code Information]:
[FDD - When more than one DL DPDCH is assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to TS 25.212 [8]. When p number of DL DPDCHs are assigned to each RL, the first pair of DL Scrambling Code and FDD DL Channelisation Code Number corresponds to "PhCH number 1", the second to "PhCH number 2", and so on until the pth to "PhCH number p".]
[TDD - PDSCH RL ID]:
[TDD - If the PDSCH RL ID IE is included in RADIO LINK SETUP REQUEST message, the Node B shall use the PDSCH RL ID as an identifier for the PDSCH and/or PUSCH in this radio link.]
[FDD - Phase Reference Handling]:
[FDD - If the RADIO LINK SETUP REQUEST message includes the Primary CPICH Usage For Channel Estimation IE and has the value "Primary CPICH shall not be used", the Node B shall assume that the UE is not using the Primary CPICH for channel estimation. If the RADIO LINK SETUP REQUEST message does not include the Primary CPICH Usage For Channel Estimation IE or includes the Primary CPICH Usage For Channel Estimation IE and has the value "Primary CPICH may be used", the Node B shall assume that the UE may use the Primary CPICH for channel estimation.]
[FDD - If the RADIO LINK SETUP REQUEST message includes the Secondary CPICH Information IE, the Node B shall assume that the UE may use the Secondary CPICH indicated by the Common Physical Channel ID IE for channel estimation.]
General:
[FDD - If the Propagation Delay IE and optionally the Extended Propagation Delay IE are included, the Node B may use this information to speed up the detection of L1 synchronisation.]
[FDD - The UL SIR Target IE included in the message shall be used by the Node B as initial UL SIR target for the UL inner loop power control.]
[1.28Mcps TDD - The UL SIR Target IE included in the message shall be used by the Node B as initial UL SIR target for the UL inner loop power control according to TS 25.221 [19] and TS 25.224 [21].]
[FDD - If the received Limited Power Increase IE is set to "Used", the Node B shall, if supported, use Limited Power Increase according to ref. TS 25.214 [10] subclause 5.2.1 for the inner loop DL power control.]
[1.28Mcps TDD - If the UL CCTrCH Information IE includes the TDD TPC UL Step Size IE, the Node B shall configure the uplink TPC step size according to the parameters given in the message.]
[1.28 Mcps TDD - The Node B shall configure the HS-SCCH TPC step size to the same value as the TDD TPC DL Step Size IE of the lowest numbered DL CCTrCH whose DL CCTrCH Information IE includes the TDD TPC DL Step Size IE.]
[1.28 Mcps TDD - If no TDD TPC DL Step Size IE is included in the DL CCTrCH Information IE, the Node B shall use the E-AGCH TPC step size IE in the E-PUCH Information LCR IE in the E-DCH Information 1.28Mcps IE for HS-SCCH inner loop power control related operation.]
[1.28Mcps TDD - If the UL Timeslot Information LCR  IE includes the PLCCH Information IE, the Node B shall transmit TPC /SS bits on a PLCCH according to the parameters given in the message.]
[FDD - DPCH Handling]:
[FDD - If the UL DPDCH Indicator For E-DCH Operation IE is set to "UL DPDCH not present", the Min UL Channelisation Code Length IE, the Puncture Limit IE and the TFCS IE within the UL DPCH Information IE shall be ignored and no UL DPDCH resources shall be allocated.]
[FDD - If the RADIO LINK SETUP REQUEST message includes the DL DPCH Information IE, then the Node B shall configure the concerned Node B Communication Context to use DPCH in the downlink, i.e. with a DL DPCCH and a DL DPDCH.]
[FDD - If the RADIO LINK SETUP REQUEST message includes the F-DPCH Information IE, then the Node B shall configure the concerned Node B Communication Context to use F-DPCH in the downlink, i.e. with transmission of only the TPC field.]
[FDD - Continuous Packet Connectivity Handling]:
[FDD - If the RADIO LINK SETUP REQUEST message includes the Continuous Packet Connectivity DTX-DRX Information IE, then:]
	[FDD - The Node B shall configure the concerned Node B Communication Context for DTX operation according to TS 25.214 [10].]
	[FDD - If DRX Information IE is included in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].]
-	[FDD - If UE DRX Cycle 2 IE is included in the DRX Information IE in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].]
-	[FDD - If Inactivity Threshold for UE DRX Cycle 2 IE is included in the DRX Information IE in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].]
[FDD - If the RADIO LINK SETUP REQUEST message includes the Continuous Packet Connectivity HS-SCCH less Information IE, then:]
-	[FDD - The Node B shall configure the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for Continuous Packet Connectivity HS-SCCH less operation according to TS 25.214 [10].]
-	[FDD - The Node B shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the Continuous Packet Connectivity HS-SCCH less Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD - If at least one of  HS-PDSCH Second Code Support IE is set to "True", then the Node B shall include HS-PDSCH Second Code Index IE in the RADIO LINK SETUP RESPONSE message.]
[1.28 Mcps TDD - Continuous Packet Connectivity Handling]:
[1.28 Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the Continuous Packet Connectivity DRX Information LCR IE, then the Node B shall take account into these parameters to decide the DRX operation related parameters and configure the concerned Node B Communication Context for DRX operation according to TS 25.224 [21] and include the parameter(s) in the Continuous Packet Connectivity DRX Information Response LCR IE in the RADIO LINK SETUP RESPONSE message.]
[1.28 Mcps TDD - If the Inactivity Threshold for UE DRX Cycle Ext IE is included in the Continuous Packet Connectivity DRX Information LCR IE, then the Node B may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [21].]
[1.28 Mcps TDD - If the Enabling Delay Ext IE is included in the Continuous Packet Connectivity DRX Information LCR IE, then the Node B may use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [21].]
[1.28 Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the HS-DSCH Semi-Persistent scheduling Information LCR IE, then:]
-	[1.28 Mcps TDD - The Node B shall configure the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [21].]
-	[1.28 Mcps TDD - The Node B shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the HS-DSCH Semi-Persistent scheduling Information Response LCR IE in the RADIO LINK SETUP RESPONSE message.]
-	[1.28 Mcps TDD - If the HS-DSCH Semi-Persistent Resource Reservation Indicator IE is included in the HS-DSCH Semi-Persistent scheduling Information LCR IE, then the Node B shall include Allcoated HS-PDSCH Semi-persistent resource IE in the RADIO LINK SETUP RESPONSE message.]
-	[1.28 Mcps TDD – The Node B shall include the Buffer Size for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK SETUP RESPONSE message.]
-	[1.28 Mcps TDD – The Node B shall include the Number of Processes for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK SETUP RESPONSE message.]
[1.28 Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the E-DCH Semi-Persistent scheduling Information LCR IE, then:]
-	[1.28 Mcps TDD - The Node B shall configure the Serving E-DCH Radio Link indicated by the E-DCH Serving RL IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [21].]
-	[1.28 Mcps TDD - If the E-DCH Semi-Persistent Resource Reservation Indicator IE is included in the E-DCH Semi-Persistent scheduling Information LCR IE, then the Node B shall include Allocated E-DCH Semi-persistent resource IE in the RADIO LINK SETUP RESPONSE message.]
[1.28 Mcps TDD - MU-MIMO Handling:]
[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the MU-MIMO Information IE, then:]
-	[1.28 Mcps TDD - The Node B can activate MU-MIMO operation on Uplink and/or Downlink indicated by the MU-MIMO indicator IE and shall include the MU-MIMO Information Response IE in the RADIO LINK SETUP RESPONSE message.]
-	[1.28 Mcps TDD - If the Standalone Midamble Channel Information IE is included in the MU-MIMO Information IE, then the Node B shall configure the concerned Node B Communication Context for standalone midamble related operation according to TS 25.224 [21].]
-	[1.28 Mcps TDD - If the Standalone Midamble Channel Information request IE is included in the MU-MIMO Information IE, if the Node B will use MU-MIMO and if the Node B can allocate the standalone midamble resource, then the Node B shall include the Standalone Midamble Channel Information IE in the MU-MIMO Information Response IE in the RADIO LINK SETUP RESPONSE message, else the Node B shall not include the Standalone Midamble Channel Information IE in the MU-MIMO Information Response IE in the RADIO LINK SETUP RESPONSE message].
[FDD - UL CLTD Handling]:
[FDD - If the UL CLTD Information IE is present in the RADIO LINK SETUP REQUEST message, then the Node B shall setup the requested UL CLTD resources for the concerned Node B Communication Context in the cell to determine the precoding weights and then :]
-	[FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the concerned Node B Communication Context, the C-ID IE shall be included in the UL CLTD Information IE, and the Node B shall configure this cell to determine the precoding weights for the concerned Node B Communication Context.] 
-	[FDD - If the UL CLTD Activation Information IE is included in the UL CLTD Information IE, then the Node B shall use this value to configure the state of UL CLTD for the concerned Node B Communication Context.] 
[FDD - UL MIMO Setup]:
[FDD - If the UL MIMO Information IE is present in the RADIO LINK SETUP REQUEST message, then the Node B shall activate UL MIMO operation for the radio link according to the information provided in the IE.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the Serving E-DCH RL IE indicating that the Serving E-DCH RL is in this Node B]
-	[FDD - The Node B shall allocate a Secondary Transport Block E-RNTI for the corresponding RL and include the E-RNTI identifier together with the corresponding E-ROCH Channelization Code in the UL MIMO DL Control Channel Information IE in the RADIO LINK SETUP RESPONSE message. The E-ROCH Channelization code shall be allocated from the pool of E-AGCH channelization codes configured for that cell.]
-	[FDD - If the RADIO LINK SETUP REQUEST message includes the E-ROCH Power Offset IE in the UL MIMO Information IE, then the Node B may use this value to determine the E-ROCH power. The E-ROCH Power Offset should be applied for any E-ROCH transmission to this UE.]
-	[FDD - The Node B may include the the Secondary Transport Block E-HICH Signature Sequence IE in UL MIMO DL Control Channel Information IE in the RADIO LINK SETUP RESPONSE message for every RL indicated by the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE and it should include it for the Serving E-DCH RL.]
Radio Link Handling:
[FDD - Transmit Diversity]:
[FDD - When the Diversity Mode IE is set to "STTD"or "Closedloop mode1", the Node B shall activate/deactivate the Transmit Diversity for each Radio Link in accordance with the Transmit Diversity Indication IE]
[FDD - If the Diversity Mode IE is included in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Setup IE in the RADIO LINK SETUP REQUEST message, the Node B shall apply cell specific transmit diversity configuration and if the Diversity Mode IE is not set to "None" the Node B shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE.]
DL Power Control:
[FDD - The Node B shall start any DL transmission using the initial DL power specified in the message on each DL DPCH or on the F-DPCH of the RL until either UL synchronisation on the Uu interface is achieved for the RLS or Power Balancing is activated. No inner loop power control or balancing shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.214 [10], subclause 5.2.1.2) and the power control procedure (see subclause 8.3.7), but shall always be kept within the maximum and minimum limit specified in the RADIO LINK SETUP REQUEST message. If the Node B Communication Context is configured to use DPCH in the downlink, during compressed mode, the  Pcurr, as described in ref. TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.]
[FDD - If the DPC Mode IE is present in the RADIO LINK SETUP REQUEST message, the Node B shall apply the DPC mode indicated in the message and be prepared that the DPC mode may be changed during the lifetime of the RL. If the DPC Mode IE is not present in the RADIO LINK SETUP REQUEST message, DPC mode 0 shall be applied (see ref. TS 25.214 [10]).]
[3.84 Mcps TDD and 7.68Mcps TDD - The Node B shall determine the initial CCTrCH DL power for each DCH type CCTrCH by the following rule: If the CCTrCH Initial DL Transmission Power IE is included for that CCTrCH, then the Node B shall use that power for the initial CCTrCH DL power, otherwise the initial CCTrCH DL power is the Initial DL Transmission Power IE included in the RL Information IE. The Node B shall start any DL transmission on each DCH type CCTrCH using the initial CCTrCH DL power, as determined above, on each DL DPCH and on each Time Slot of the CCTrCH until the UL synchronisation on the Uu interface is achieved for the CCTrCH. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 4.2.3.4), but shall always be kept within the maximum and minimum limit specified in the RADIO LINK SETUP REQUEST message.]
[3.84 Mcps TDD and 7.68Mcps TDD - The Node B shall determine the maximum DL power for each DCH type CCTrCH by the following rule: If the CCTrCH Maximum DL Transmission Power IE is included for that CCTrCH, then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the Maximum DL Power IE included in the RL Information IE.]
[3.84 Mcps TDD and 7.68Mcps TDD - The Node B shall determine the minimum DL power for each DCH type CCTrCH by the following rule: If the CCTrCH Minimum DL Transmission Power IE is included for that CCTrCH, then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the Minimum DL Power IE included in the RL Information IE.]
[3.84Mcps TDD and 7.68Mcps TDD - The initial power, maximum power, and minimum power for DSCH type CCTrCH shall be determined as follows:
-	If the DSCH type CCTrCH is paired with an uplink CCTrCH(s) for inner loop power control, the minimum, maximum and initial power for each PDSCH is determined in the same way as described above for DCH type CCTrCHs.
-	If the DSCH type CCTrCH is not paired with an uplink CCTrCH(s) for inner loop power control, the PDSCH transmission power is DSCH Data Frame Protocol signalled (TS 25.435 [24]), with the maximum value determined in the same way as described above for DCH type CCTrCHs. The minimum and initial powers, however, are subject to control by the CRNC via the frame protocol].
[1.28 Mcps TDD - The Node B shall determine the initial DL power for each timeslot within the DCH type CCTrCH by the following rule: If the Initial DL Transmission Power IE is included in the DL Timeslot Information LCR IE, then the Node B shall use that power for the Initial DL Power and ignore the DL Time Slot ISCP info LCR IE, otherwise the initial DL Power is the Initial DL Transmission Power IE included in the RL Information IE and if DL Time Slot ISCP info LCR IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged. The Node B shall start any DL transmission on each timeslot within each DCH type CCTrCH using the initial DL power, as determined above, on each DL DPCH and on each timeslot of the CCTrCH until the UL synchronisation on the Uu interface is achieved for the CCTrCH. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4), but shall always be kept within the maximum and minimum limit specified in the RADIO LINK SETUP REQUEST message.]
[1.28 Mcps TDD - The Node B shall determine the maximum DL power for each timeslot within the DCH type CCTrCH by the following rule: If the Maximum DL Power IE is included in the DL Timeslot Information LCR IE, then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the Maximum DL Power IE included in the RL Information IE.]
[1.28 Mcps TDD - The Node B shall determine the minimum DL power for each timeslot within the DCH type CCTrCH by the following rule: If the Minimum DL Power IE is included in the DL Timeslot Information LCR IE, then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the Minimum DL Power IE included in the RL Information IE.]
[1.28Mcps TDD - The Node B shall determine the initial power for each timeslot within the DSCH type CCTrCH by the following rule: If both the CCTrCH Initial DL Transmission Power IE, included in the DL CCTrCH Information IE, and the DL Time Slot ISCP Info LCR IE, included in the RL Information IE, are included then the Node B shall use that power for the PDSCH and ignore the Initial DL Transmission Power IE included in the RL Information IE, otherwise the initial DL Power is the Initial DL Transmission Power IE included in the RL Information IE and if DL Time Slot ISCP info LCR IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged. The Node B shall start any DL transmission on each timeslot within each DSCH type CCTrCH using the initial DL power, as determined above, on each DL PDSCH and on each timeslot of the CCTrCH until the UL synchronisation on the Uu interface is achieved for the CCTrCH. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4), but shall always be kept within the maximum and minimum limit specified in the RADIO LINK SETUP REQUEST message.]
[1.28 Mcps TDD - The Node B shall determine the maximum DL power for each timeslot within the DSCH type CCTrCH by the following rule: If the CCTrCH Maximum DL Transmission Power IE, included in the DL CCTrCH Information IE, is included then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the Maximum DL Power IE included in the RL Information IE.]
[1.28 Mcps TDD - The Node B shall determine the minimum DL power for each timeslot within the DSCH type CCTrCH by the following rule: If the CCTrCH Minimum DL Transmission Power IE, included in the DL CCTrCH Information IE, is included then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the Minimum DL Power IE included in the RL Information IE.]
[3.84Mcps TDD and 7.68Mcps TDD - If the DL Time Slot ISCP Info IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], i.e. it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged.]
[FDD - If the received Inner Loop DL PC Status IE is set to "Active", the Node B shall activate the inner loop DL power control for all RLs. If Inner Loop DL PC Status IE is set to "Inactive", the Node B shall deactivate the inner loop DL power control for all RLs according to ref. TS 25.214 [10].]
[FDD - If the RADIO LINK SETUP REQUEST message includes the DL Power Balancing Information IE and the Power Adjustment Type IE is set to "Common" or "Individual", the Node B shall activate the power balancing, if activation of power balancing by the RADIO LINK SETUP REQUEST message is supported, according to subclause 8.3.7, using the DL Power Balancing Information IE. If the Node B starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. Pinit shall be set to the power level indicated by the Initial DL Transmission Power IE.]
[FDD - If activation of power balancing by the RADIO LINK SETUP REQUEST message is supported by the Node B, the Node B shall include the DL Power Balancing Activation Indicator IE in the RL Information Response IE in the RADIO LINK SETUP RESPONSE message.]
[1.28Mcps TDD - Uplink Synchronisation Parameters LCR]:
[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message contains the Uplink Synchronisation Parameters LCR IE, the Node B shall use the indicated values of Uplink Synchronisation Stepsize IE and Uplink Synchronisation Frequency IE when evaluating the timing of the UL synchronisation.]
[1.28Mcps TDD - Power Control GAP:]
[1.28Mcps TDD - If the Power Control GAP IE is included in the RADIO LINK SETUP REQUEST message, the Node B may use the value for the power control for HS-SCCH and HS-SICH according to TS 25.224 [21].]
[1.28Mcps TDD - E-UTRAN Inter-RAT measurement:]
[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the Idle Interval Information IE, if supported, the Node B shall use the value for E-UTRAN Inter-RAT measurement  according to the TS 25.331 [18].]
[1.28Mcps TDD - HS-DSCH-RNTI for FACH:]
[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the HS-DSCH-RNTI for FACH IE, if supported, the Node B shall store this information and include the E-RNTI for FACH IE in the RADIO LINK SETUP RESPONSE message.]
[1.28Mcps TDD – Inter-frequency/ Inter-RAT measurement:]
[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the Measurement occasion pattern sequence parameters IE in the DCH Measurement Occasion Information IE, the Node B shall store the information about the Measurement occasion pattern sequences and use the value(s) to calculate the Inter-frequency/Inter-RAT measurement occasion according to TS 25.331 [18].]
[FDD – HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change]
[FDD – If the RADIO LINK SETUP REQUEST message includes the HS-DSCH Preconfiguration Setup IE in the RL Information IE for a Radio Link not indicated by the HS-PDSCH RL ID IE the Node B shall if supported preconfigure the indicated cells for Enhanced HS Serving Cell Change acoording to TS 25.308 [49]:]
-	[FDD – The Node B shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the C-ID IE part of the RL Information IE in the RADIO LINK SETUP REQUEST message. The list of secondary serving HS-DSCH cells is designated by the list of C-IDs in the HS-DSCH Preconfiguration Setup IE part of the RL Information IE in the RADIO LINK SETUP REQUEST message.]
-	[FDD – The number of HS-SCCH codes to preconfigure for each cell may be optionally specified:]
-	[FDD – - by the Num Primary HS-SCCH Codes IE in the HS-DSCH Preconfiguration Setup IE, for the primary serving HS-DSCH cell]
-	[FDD – - by the Num Secondary HS-SCCH Codes IE in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE for each of the secondary serving HS-DSCH cells]
-	[FDD – If Num Primary HS-SCCH Codes IE or Num Secondary HS-SCCH Codes IE is not included in the message, the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10].]
-	[FDD – The Node B shall return these codes in the Sets of HS-SCCH Codes IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE of the RADIO LINK SETUP RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK SETUP FAILURE message.]
-	[FDD – The Node B shall use the first in the numbered list of the primary serving HS-DSCH cell’s HS-SCCH codes in the HS-SCCH Preconfigured Codes IE sent to the RNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [18].]
-	[FDD – The Node B shall include, in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK SETUP RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK SETUP FAILURE message, IEs according to the rules defined for HS-DSCH Setup and:]
-	[FDD – - if HARQ Preamble Mode IE is included in the HS-DSCH Preconfiguration Setup IE the HARQ Preamble Mode Activation Indicator IE]
-	[FDD – - if MIMO Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE]
-	[FDD – if Ordinal number of frequency IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE]
-	[FDD – if MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE]
-	[FDD – if Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE]
-	[FDD – if Multiflow ordinal number of frequency IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE]
-	[FDD – - if HS-DSCH MAC-d PDU Size Format IE is included in  the HS-DSCH Preconfiguration Setup IE and set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used in the preconfigured configuration  the HS-DSCH TB Size Table Indicator IE for each preconfigured cell]
-	[FDD – - if Sixtyfour QAM Usage Allowed Indicator is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE or in the HS-DSCH Preconfiguration Setup IE the SixtyfourQAM DL Usage Indicator IE for each preconfigured cell]
-	[FDD – - if Continuous Packet Connectivity HS-SCCH less Information IE is included in the HS-DSCH Preconfiguration Setup IE the Continuous Packet Connectivity HS-SCCH less Information Response IE]
-	[FDD – - if the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH Preconfiguration Setup IE, then the Node B shall store this information in the preconfigured configuration.]
-	[FDD – - if the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE, then the Node B may store this information in the preconfigured configuration.]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the Node B shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH Preconfiguration Info IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD – The Node B shall include in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK SETUP RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK SETUP FAILURE message the E-DCH FDD DL Control Channel Information containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:]
-	[FDD – - The Node B shall allocate for the preconfigured configuration a primary  E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding  E-AGCH in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – -The Node B may configure for the preconfigured configuration the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the E-DCH Indicator IE for a secondary cell, the Node B shall include in the Additional E-DCH Preconfiguration Information IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK SETUP RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK SETUP FAILURE message the E-DCH FDD DL Control Channel Information containing the preconfigured configuration of the Additional E-DCH serving cell, corresponding to the cell indicated with the E-DCH Indicator IE, according to the rules defined for Serving Additional E-DCH Radio Link Change as follows:]
-	[FDD – The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving Additional E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – The Node B may configure for the preconfigured configuration the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving Additional E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the Multiflow Information IE, then the Node B shall allocate resources for the preconfigured Multiflow for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the F-TPICH Information IE, then the Node B shall allocate resources for the preconfigured F-TPICH channel for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the UL CLTD Information IE, then the Node B shall allocate resources for the preconfigured UL CLTD for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the UL MIMO Information IE, then the Node B shall allocate resources for the preconfigured UL MIMO for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the SixteenQAM UL Operation Indicator IE, then the Node B shall allocate resources for the preconfigured UL Sixteen QAM for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the SixtyfourQAM UL Operation Indicator IE, then the Node B shall allocate resources for the preconfigured UL Sixtyfour QAM for the concerned Node B Communication Context.]
[FDD – If the RADIO LINK SETUP REQUEST message includes the Non-Serving RL Preconfiguration Setup IE in the RL Information IE and:]
-	[FDD – if the choice of new Serving RL is "New Serving RL in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE and/or New non-serving RL E-DCH FDD DL Control Channel Information B IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK SETUP RESPONSE message.]
-	[FDD – if the choice of new Serving RL is "New Serving RL Not in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information C IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK SETUP RESPONSE message.]
-	[FDD – if the choice of new Serving RL is "New Serving RL in the Node B or New Serving RL Not in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C IE for the RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD – if the Additional E-DCH Non-Serving RL Preconfiguration Setup IE is included, the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C IE according to the choice of new Serving RL in Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information IE for the additional non serving E-DCH RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK SETUP RESPONSE message.]
-	[FDD –If the F-TPICH Information IE is included, the Node B shall use this information to allocate resources for the preconfigured F-TPICH channel for this RL in the serving RLS according to TS 25.211 [7].]
[1.28Mcps TDD – Non-rectangular resource operation:]
[1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message contains the UE support of non-rectangular resource allocation IE, the Node B shall, if supported, use this information to determine whether includes the Non-rectangular resource allocation indicator IE and the Non-rectangular resource timeslot set IE or not.]
[FDD – UL DPCCH2 Handling:]
[FDD - If the RADIO LINK SETUP REQUEST message includes the UL DPCCH2 Information IE, then:]
-	[FDD – if the serving HS-DSCH RL is in the Node B then the Node B shall configure the concerned Node B Communication Context to use a second F-DPCH in the downlink, i.e. with transmission of only the TPC field and a DPCCH2 in the uplink, i.e. with the transmission of only the second pilot and the TPC field on the Serving HS-DSCH Radio Link and the Node B shall activate UL DPCCH2 operation for the radio link according to the information provided in the IE according to ref TS 25.214 [10].]
-	[FDD – if the serving HS-DSCH is not in the Node B then the Node B may consider the concerned Node B Communication Context to use the UL DPCCH2 configuration on the Serving HS-DSCH Radio Link.]
-	[FDD – If the UL DPCCH2 Information IE includes the Extended E-DPCCH Power Offset IE and if the E-DCH FDD Information IE is present in the RADIO LINK SETUP REQUEST message, the Node B shall use the value to calculate the E-DPCCH gain factor.]
[FDD – Downlink TPC enhancements Handling:]
[FDD - If the RADIO LINK SETUP REQUEST message includes the Downlink TPC enhancements Information IE, then:]
-	[FDD – The Node B shall, if supported, use the Decimation factor for primary frequency IE and/or the Decimation factor for secondary frequency IE to configure all the radio links using F-DPCH on the related frequency with power control Algorithm 3.]
[FDD - If the TPC slot position in the RL Information is included in the RADIO LINK SETUP REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.]
[FDD - If the TPC slot position in the Additional E-DCH Cell Information RL Setup Req is included in the RADIO LINK SETUP REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.]
General:
If the RADIO LINK SETUP REQUEST message includes the RL Specific DCH Information IE, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the DCH or the set of co-ordinated DCHs.
The Node B shall start reception on the new RL(s) after the RLs are successfully established.
[FDD - If the RADIO LINK SETUP REQUEST message includes the Synchronisation Indicator IE, set to "Timing Maintained Synchronisation", the Node B shall use synchronisation procedure B according to subclause 4.3.2.4 in TS 25.214 [10].]
[FDD - If the RADIO LINK SETUP REQUEST message includes the Initial DL DPCH Timing Adjustment Allowed IE, then the Node B may perform an initial DL DPCH Timing Adjustment (i.e. perform a timing advance or a timing delay with respect to the SFN timing) on a Radio Link. In this case, the Node B shall include, for the concerned Radio Link(s), the Initial DL DPCH Timing Adjustment IE in the Radio Link Information Response IE in the RADIO LINK SETUP RESPONSE message.]
[FDD - If the RADIO LINK SETUP REQUEST message includes the F-DPCH Slot Format IE and if the Node B Communication Context is configured to use F-DPCH in the downlink, then the Node B shall use this information to configure the F-DPCH slot format of each RL according to TS 25.211 [7].]
[FDD - If the RADIO LINK SETUP REQUEST message includes the E-RNTI IE in the RL Information IE, the Node B shall use the information to detect the information related to the E-RNTI which is configured in the Node B when the UE was in Cell_FACH state.]
[FDD - If the RADIO LINK SETUP REQUEST message includes the F-TPICH Information IE in the RL Information IE, the Node B shall use this information to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214 [10].]
[FDD - Radio Link Set Handling]:
[FDD - The First RLS Indicator IE indicates if the concerned RL shall be considered part of the first RLS established towards this UE. The First RLS Indicator IE shall be used by the Node B together with the value of the DL TPC Pattern 01 Count IE which the Node B has received in the Cell Setup procedure, to determine the initial TPC pattern in the DL of the concerned RL and all RLs which are part of the same RLS, as described in TS 25.214 [10], section 5.1.2.2.1.2.]
[FDD - For each RL not having a common generation of the TPC commands in the DL with another RL, the Node B shall assign the RL Set ID IE included in the RADIO LINK SETUP RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. In case of E-DCH, the generation of E-HICH related information for RLs in different RL Sets shall not be common.]
[FDD - For all RLs having a common generation of the TPC commands in the DL with another RL, the Node B shall assign the RL Set ID IE included in the RADIO LINK SETUP RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. In case of E-DCH, the generation of E-HICH information for all RLs in a RL Set shall be common.]
[FDD - The UL out-of-sync algorithm defined in TS 25.214 [10] shall, for each of the established RL Set(s), use the maximum value of the parameters N_OUTSYNC_IND and T_RLFAILURE that are configured in the cells supporting the radio links of the RL Set. The UL in-sync algorithm defined in TS 25.214 [10] shall, for each of the established RL Set(s), use the minimum value of the parameters N_INSYNC_IND, that are configured in the cells supporting the radio links of the RL Set.]
[FDD - For each E-DCH RL which has or can have a common generation of E-RGCH information with another RL (current or future) when the Node B would contain the E-DCH serving RL, the Node B shall include the E-DCH RL Set ID IE in the RADIO LINK SETUP RESPONSE message. The value of the E-DCH RL Set ID IE shall allow the RNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.]
[FDD – Radio Links without DPCH/F-DPCH operation]
[FDD – If the Radio Links without DPCH/F-DPCH Indication IE is present in the RADIO LINK SETUP REQUEST message:]
-	[FDD – The Node B shall if supported start operation with Radio Links without DPCH/F-DPCH.]
Response Message:
If the RLs are successfully established, the Node B shall and respond with a RADIO LINK SETUP RESPONSE message.
After sending the RADIO LINK SETUP RESPONSE message the Node B shall continuously attempt to obtain UL synchronisation on the Uu interface.
For each RL for which the Delayed Activation IE is not included in the RADIO LINK SETUP REQUEST message, the Node B shall:
-	[FDD - start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16].]
-	[TDD - start transmission on the new RL immediately as specified in TS 25.427 [16].]
For each RL for which the Delayed Activation IE is included in the RADIO LINK SETUP REQUEST message, the Node B shall:
-	if the Delayed Activation IE indicates "Separate Indication":
-	not start any DL transmission for the concerned RL on the Uu interface;
-	if the Delayed Activation IE indicates "CFN":
-	[FDD - start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16], however never before the CFN indicated in the Activation CFN IE.]
-	[TDD - start transmission on the new RL at the CFN indicated in the Activation CFN IE as specified in TS 25.427 [16].]
8.2.17.3	Unsuccessful Operation

Figure 25: Radio Link Setup procedure, Unsuccessful Operation
If the establishment of at least one radio link is unsuccessful, the Node B shall respond with a RADIO LINK SETUP FAILURE message. The message contains the failure cause in the Cause IE.
[FDD - If some radio links were established successfully, the Node B shall indicate this in the RADIO LINK SETUP FAILURE message in the same way as in the RADIO LINK SETUP RESPONSE message. In this case, the Node B shall include the Communication Control Port Id IE in the RADIO LINK SETUP FAILURE message.]
[FDD - If the RL identified by the HS-PDSCH RL ID IE is a radio link in the Node B and this RL is successfully established, then the Node B shall include the HS-DSCH FDD Information Response IE in the RADIO LINK SETUP FAILURE message.]
[FDD - If the RL identified by the HS-PDSCH RL ID IE in the Additional HS Cell Information RL Setup IE is a radio link in the Node B and this RL is successfully established, then the Node B shall include the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP FAILURE message. If the establishment of the RL identified by the HS-PDSCH RL ID IE in the Additional HS Cell Information RL Setup IE, i.e. secondary serving HS-DSCH Radio Link is unsuccessful but the establishment of the RL identified by the HS-PDSCH RL ID IE for the serving HS-DSCH Radio Link is successful, then the Node B shall indicate the unsuccessful secondary serving HS-DSCH Radio Link in the Unsuccessful RL Information Response IE in the RADIO LINK SETUP FAILURE message by setting the RL ID IE to the same value as the unsuccessful HS-PDSCH RL ID IE in the Additional HS Cell Information RL Setup IE.]
[FDD - If the RL identified by the E-DCH Additional RL ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE is a radio link in the Node B and this RL is successfully established, then the Node B shall include the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK SETUP FAILURE message in the same way as in the RADIO LINK SETUP RESPONSE message. If the establishment of the RL identified by the E-DCH Additional RL ID IE is unsuccessful, then the Node B shall indicate the unsuccessful setup of the Additional E-DCH Radio Link in the Unsuccessful RL Information Response IE in the RADIO LINK SETUP FAILURE message by setting the RL ID IE to the same value as the unsuccessful E-DCH Additional RL ID IE in the Additional E-DCH Cell Information Setup IE.]
Typical cause values are as follows:
Radio Network Layer Cause:
-	Combining not supported
-	Combining Resources not available
-	Requested Tx Diversity Mode not supported
-	Number of DL codes not supported
-	Number of UL codes not supported
-	UL SF not supported
-	DL SF not supported
-	Dedicated Transport Channel Type not supported
-	Downlink Shared Channel Type not supported
-	Uplink Shared Channel Type not supported
-	CM not supported
-	[FDD - DPC mode change not supported]
-	Delayed Activation not supported
-	F-DPCH not supported
-	[FDD - Continuous Packet Connectivity DTX-DRX operation not available]
-	[FDD - Continuous Packet Connectivity UE DTX Cycle not available]
-	[FDD - MIMO not available]
-	E-DCH MAC-d PDU Size Format not available
-	[FDD - SixtyfourQAM DL and MIMO Combined not available]
-	[FDD - Multi Cell operation not available.]
-	[1.28Mcps TDD- MIMO not available]
-	[1.28Mcps TDD - SixtyfourQAM DL and MIMO Combined not available]
-	[FDD - TX diversity for MIMO UE on DL Control Channels not available]
-	[FDD – Single Stream MIMO not available]
-	[FDD - Multi Cell operation with MIMO not available]
-	[FDD - Multi Cell operation with Single Stream MIMO not available]
-	[FDD - Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available]
-	[FDD - Multi Cell E-DCH operation not available]
-	[FDD – Frequency Specific Compressed mode operation not available]
-	[FDD - UL CLTD operation not available]
-	[FDD - MIMO with four transmit antennas not available]
-	[FDD - Dual Stream MIMO with four transmit antennas not available]
-	[FDD – Multiflow operation not available]
-	[FDD - SixtyfourQAM UL operation not available]
-	[FDD – UL MIMO operation not available]
-	[FDD – UL MIMO and SixteenQAM operation not available]
-	[FDD – UL MIMO and SixtyfourQAM operation not available]
-	[FDD – E-DCH decoupling operation not available]
-	[FDD – Basic DCH Enhancements operation not available]
-	[FDD – Full DCH Enhancements operation not available]
-	[FDD – Radio Links without DPCH/F-DPCH operation not available]
-	[FDD –UL DPCCH2 operation not available]
-	[FDD –Downlink TPC enhancements operation not available]
Transport Layer Cause:
-	Transport Resources Unavailable
Miscellaneous Cause:
-	O&M Intervention
-	Control processing overload
-	HW failure
8.2.17.4	Abnormal Conditions
[FDD - If the RADIO LINK SETUP REQUEST message contains the Active Pattern Sequence Information IE, but the Transmission Gap Pattern Sequence Information IE is not present, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
If more than one DCH of a set of co-ordinated DCHs has the QE-Selector IE set to "selected" [TDD - or no DCH of a set of co-ordinated DCHs has the QE-Selector IE set to "selected"], the Node B shall regard the Radio Link Setup procedure as failed and shall respond with a RADIO LINK SETUP FAILURE message.
If the RADIO LINK SETUP REQUEST message includes a DCH Information IE with multiple DCH Specific Info IEs, and if the DCHs in the DCH Information IE do not have the same Transmission Time Interval IE in the Semi-static Transport Format Information IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.
If the RADIO LINK SETUP REQUEST message includes the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE or RL Specific E-DCH Information IE included in the RL Information IE for a specific RL and the Diversity Control Field IE is set to "Must" [FDD - or the RL is combined with an E-DCH RL previously listed in the RADIO LINK SETUP RESPONSE message], the Node B shall regard the Radio Link Setup procedure as failed and respond with the RADIO LINK SETUP FAILURE message.
If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE in the RL Information IE for a specific RL and the Diversity Control Field IE is set to "May", the Node B shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message.
If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE in the RL Information IE for a specific RL and the Diversity Control Field IE is set to "Must Not", the Node B shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message.
If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE for the first RL in the RL Information IE and/or [FDD - in the RL Specific E-DCH Information IE in the RL Information IE for the first E-DCH RL][TDD – in the E-DCH MAC-d Flows Information TDD IE], the Node B shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message.
If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the Transport Layer Address IE and the Binding ID IE for an HS-DSCH MAC-d Flow in the HS-DSCH MAC-d Flows Information IE, the Node B shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message.
[TDD - If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the Transport Layer Address IE and the Binding ID IE for a DSCH in the DSCH TDD Information IE and/or for an USCH in the USCH  Information IE, the Node B shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message.]
If the RADIO LINK SETUP REQUEST message contains the Transport Layer Address IE or the Binding ID IE, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.
If the RADIO LINK SETUP REQUEST message includes an HS-PDSCH RL-ID IE for a serving HS-DSCH not referring to one of the radio links to be established, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.
If the RADIO LINK SETUP REQUEST message contains the HS-DSCH Information IE and if the Priority Queues associated with the same HS-DSCH MAC-d Flow ID IE have the same Scheduling Priority Indicator IE value, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.
If the RADIO LINK SETUP REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, and the HS-DSCH MAC-d PDU Size Format  IE in the HS-DSCH  Information IE has the value  "Indexed MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.
If the RADIO LINK SETUP REQUEST message does not include the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, and the HS-DSCH MAC-d PDU Size Format  IE in the HS-DSCH  Information IE has the value  "Flexible MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.
[FDD - If  the RADIO LINK SETUP REQUEST message contains, for at least one logical channel, the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[TDD - If the RADIO LINK SETUP REQUEST message contains, for at least one logical channel, the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE, and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE is not present, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message includes the Synchronisation Indicator IE, set to "Timing Maintained Synchronisation", and if the First RLS indicator IE is set to "not first RLS", the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the HS-DSCH Information IE and if the Measurement Power Offset IE is not present, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the F-DPCH Information IE and the DL DPCH Information IE configured simultaneously to one downlink frequency, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message includes the  Active Pattern Sequence Information IE, which activates a transmission gap pattern sequence with an SF/2 downlink compressed mode method, and if the concerned Node B Communication Context is configured to use DPCH in downlink and the Transmission Gap Pattern Sequence Code Information is not available for any Radio Link, the Node B shall reject the Radio Link Setup procedure using the RADIO LINK SETUP FAILURE message with the cause value “Invalid CM Settings”.]
[FDD - If the RADIO LINK SETUP REQUEST message includes the Primary CPICH Usage For Channel Estimation IE set to the value "Primary CPICH shall not be used" and doesn’t include the Secondary CPICH Information IE, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message includes one of the Not Used IEs, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the E-DCH RL Indication IE set to "E-DCH", but does not contain the E-DCH FDD Information IE, or if the message contains the E-DCH FDD Information IE, but does not contain the E-DCH RL Indication IE set to "E-DCH", then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
If the RADIO LINK SETUP REQUEST message does not contain the E-DCH Decoupling Indication IE but contains the HS-PDSCH RL ID IE and the Serving E-DCH RL IE, and the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not configured to be in the same cell, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.
[FDD - If the RADIO LINK SETUP REQUEST message contains the HS-PDSCH RL ID IE and the E-DPCH Information IE which includes the HS-DSCH Configured Indicator IE set as “HS-DSCH not configured” then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the E-DPCH Information IE but does not contain the UL DPDCH Indicator For E-DCH Operation IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the Serving Cell Change CFN IE, but neither the Serving E-DCH RL IE nor HS-DSCH Information IE is included, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the Transport Bearer Not Requested Indicator IE for a DCH, but does not contain the Unidirectional DCH indicator IE set to "Uplink DCH only" in the DCH Specific Info IE for the DCH, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[1.28Mcps TDD - For a multi-frequency cell, if the UARFCN IE is not included in the RADIO LINK SETUP REQUEST message, the Node B shall reject the procedure by sending the RADIO LINK SETUP FAILURE message.]
[1.28Mcps TDD - For the cell in which only one frequency is configured, if the UARFCN IE is included in the RADIO LINK SETUP REQUEST message, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the UL DPCH Information IE in the RADIO LINK SETUP REQUEST message contains the UL DPCCH Slot Format set to "4" but does not contain the F-DPCH Information IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the UL DPCH Information IE in the RADIO LINK SETUP REQUEST message contains the UL DPCCH Slot Format set to "0" or "2" and the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the UL DPCH Information IE in the RADIO LINK SETUP REQUEST message contains Diversity Mode IE set to "Closed loop mode 1"and UL DPCCH Slot Format not set to "2" or "3", then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the MIMO Activation Indicator IE, Sixtyfour QAM Usage Allowed Indicator IE set to "Allowed", the the Additional HS Cell Information RL Setup IE, the Single Stream MIMO Activation Indicator IE, the MIMO with four transmit antennas Activation Indicator IE and/or the Dual Stream MIMO with four transmit antennas Activation Indicator IE but does not contain the HS-DSCH MAC-d PDU Size Format IE set to "Flexible MAC-d PDU Size", then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD – If the RADIO LINK SETUP REQUEST message contains the Continuous Packet Connectivity DTX-DRX Information IE but does not contain the F-DPCH Information IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message]
[FDD – If the RADIO LINK SETUP REQUEST message contains the Serving E-DCH RL ID IE but contains the Transport Bearer Not Requested Indicator IE, the Node B shall reject the procedure using the RADIO LINK SETUP  FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message includes the Transport Bearer Not Requested Indicator IE for a DCH for a specific RL and the specific RL is combined with RL which the transport bearer is configured to be established for the DCH, previously listed in the RADIO LINK SETUP RESPONSE message in the Node B, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the Additional HS Cell Information RL Setup IE and if the HS-DSCH Information IE is not present, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
If the RADIO LINK SETUP REQUEST message includes the DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE set to “Flexible RLC PDU Size”, and the HS-DSCH MAC-d PDU Size Format  IE in the HS-DSCH  Information IE has the value  "Indexed MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.
If the RADIO LINK SETUP REQUEST message does not include the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, and the DL RLC PDU Size Format  IE in the HS-DSCH  Information IE has the value  "Flexible RLC PDU Size", the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.
[FDD - If the RADIO LINK SETUP REQUEST message contains a MIMO Activation Indicator IE and a Single Stream MIMO Activation Indicator IE in the HS-DSCH FDD Information IE or in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Setup IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Setup IE the Diversity Mode IE not set to "None" but not the Transmit Diversity Indicator or contains the Transmit Diversity Indicator but not the Diversity Mode IE not set to "None", then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the Additional E-DCH Cell Information RL Setup Req IE and if the E-DPCH Information IE is not present, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the Additional E-DCH Cell Information RL Setup Req IE and the C-ID IE is not included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If  the RADIO LINK SETUP REQUEST message contains the Additional E-DCH Cell Information RL Setup Req IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the Additional HS Cell Information RL Setup IE containing more than one secondary serving HS-DSCH RL, and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1", which are received in the Ordinal Number Of Frequency IE in the in the HS-DSCH FDD Secondary Serving Information IE, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the Additional HS Cell Information RL Setup IE containing more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value “1”, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE and theTransmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message with the cause value “Invalid CM settings”.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the UL CLTD Information IE but does not contain the F-TPICH Information IE, or if it contains HS-DSCH Preconfiguration Setup IE with UL CLTD Information IE but without F-TPICH Information IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the UL MIMO Information IE in E-DCH FDD Information IE but does not contain the UL CLTD Information IE, or if it contains HS-DSCH Preconfiguration Setup IE with UL MIMO Information IE but without UL CLTD Information IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains more than one of a MIMO Activation Indicator IE, a MIMO with four transmit antennas Activation Indicator IE, a Dual Stream MIMO with four transmit antennas Activation Indicator IE in HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message contains the DCH Enhancements Information IE, and either the DL DPCH Slot Format IE is not set to “17” or “18”, or the UL DPCCH Slot Format IE is not set to “5”, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
[FDD - If the RADIO LINK SETUP REQUEST message does not contain the DCH Enhancements Information IE, and either (i) the DL DPCH Slot Format IE is set to “17”, or (ii) the DL DPCH Slot Format IE is set to “18”, or (iii) the UL DPCCH Slot Format IE is set to “5”, then the Node B shall reject the procedure using the RADIO LINK SETUP FAILURE message.]
8.2.18	Physical Shared Channel Reconfiguration
8.2.18.1	General
This procedure is used to assign HS-DSCH related resources to the Node B.
[TDD - This procedure is also used for handling PDSCH Sets and PUSCH Sets in the Node B, i.e.
-	Adding new PDSCH Sets and/or PUSCH Sets,
-	Modifying these, and
-	Deleting them.]
This procedure is also used to assign E-DCH related resources to the Node B.
8.2.18.2	Successful Operation

Figure 26: Physical Shared Channel Reconfiguration, Successful Operation
The procedure is initiated with a PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
Upon reception, the Node B shall activate the new configuration at the head boundary of the SFN according to the parameters given in the message.
If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes an SFN IE, the Node B shall activate the new configuration at the head boundary of that specified SFN. If no SFN IE is included Node B shall activate the new configuration immediately.
E-DCH and HS-DSCH Resources:
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH Total Power IE, the Node B shall not exceed this maximum transmission power on all HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH codes in the cell. If a value has never been set or if the value of the HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH Total Power IE is equal to or greater than the maximum transmission power of the cell the Node B may use all unused power for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH codes.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH And E-HICH Total Power IE in the HSDPA And E-DCH Cell Portion Information IE, the Node B shall not exceed this maximum transmission power on all HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH codes in the cell portion indicated by Cell Portion ID IE. If a value has never been set or if the value of the HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH And E-HICH Total Power IE for the cell portion is equal to or greater than the maximum transmission power of the cell portion, the Node B may use all unused power for HS-PDSCH, HS-SCCH and E-AGCH, E-RGCH and E-HICH codes.]
HS-DSCH Resources:
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes HS-PDSCH And HS-SCCH Scrambling Code IE, the Node B shall use this as the scrambling code for all HS-PDSCHs and HS-SCCHs. If a value has never been set, the Node B shall use the primary scrambling code for all HS-PDSCH and HS-SCCH codes.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes HS-PDSCH FDD Code Information IE, the Node B shall:
-	if the Number Of HS-PDSCH Codes IE is set to "0", delete any existing HS-PDSCH resources from the cell.
-	if the Number Of HS-PDSCH Codes IE is set to any value other than "0" and HS-PDSCH resources are not currently configured in the cell, use this list as the range of codes for HS-PDSCH channels.
-	if the Number Of HS-PDSCH Codes IE is set to any value other than "0" and HS-PDSCH resources are currently configured in the cell, replace the current range of codes with this new range of codes for HS-PDSCH channels.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes HS-SCCH FDD Code Information IE, the Node B shall:
-	If the HS-SCCH FDD Code Information IE contains no codes, delete any existing HS-SCCH resources from the cell.
-	If the HS-SCCH FDD Code Information IE contains one or more codes and HS-SCCH resources are not currently configured in the cell, use this list of codes as the list of codes for HS-SCCH channels.
-	If the HS-SCCH FDD Code Information IE contains one or more codes and HS-SCCH resources are currently configured in the cell, replace the current list of codes with this new list of codes for HS-SCCH channels.]
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes HS-PDSCH and HS-SCCH Total Power IE [1.28 Mcps TDD – or HS-PDSCH and HS-SCCH Total Power per CELL PORTION IE in the DL Timeslot and Code Information LCR per UARFCN IE] for a particular timeslot, the Node B shall not exceed this maximum transmission power on all HS-PDSCH and HS-SCCH codes in that timeslot. If a value has never been set for that timeslot or if the value of the HS-PDSCH and HS-SCCH Total Power IE for that timeslot is equal to or greater than the maximum transmission power of the cell the Node B may use all unused power in that timeslot for HS-PDSCH and HS-SCCH codes.]
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes HS-PDSCH TDD Information IE, the Node B shall:
-	If the HS-PDSCH TDD Information IE contains no [3.84 Mcps TDD - DL Timeslot and Code Information IE] [1.28 Mcps TDD - DL Timeslot and Code Information LCR per UARFCN IE] [7.68 Mcps TDD - DL Timeslot and Code Information 7.68Mcps IE], delete any existing HS-PDSCH resources from the cell.
-	If the HS-PDSCH TDD Information IE contains [3.84 Mcps TDD - DL Timeslot and Code Information IE] [1.28 Mcps TDD - DL Timeslot and Code Information LCR IE] [7.68 Mcps TDD - DL Timeslot and Code Information 7.68Mcps IE] and HS-PDSCH resources are not currently configured in the cell, use this IE as the list of timeslots / codes for HS-PDSCH channels.
-	If the HS-PDSCH TDD Information IE contains [3.84 Mcps TDD - DL Timeslot and Code Information IE] [1.28 Mcps TDD - DL Timeslot and Code Information LCR IE] [7.68 Mcps TDD - DL Timeslot and Code Information 7.68Mcps IE] and HS-PDSCH resources are currently configured in the cell, replace the current list of timeslots / codes with this new list of timeslots / codes for HS-PDSCH channels.]
-	[1.28Mcps TDD - If the HS-PDSCH TDD Information IE contains any DL Timeslot and Code Information LCR per UARFCN IE and HS-PDSCH resources are not currently configured on the indicated frequency within the cell, use this IE as the list of frequency / timeslots / codes for HS-PDSCH channels on the frequency, the HSDPA resources on other frequency shall remain unchanged.]
-	[1.28Mcps TDD - If the HS-PDSCH TDD Information IE contains any DL Timeslot and Code Information LCR per UARFCN IE and HS-PDSCH resources are currently configured on the indicated frequency within the cell, the current list of frequency / timeslots / codes  shall be replaced with this new list of frequency / timeslots / codes for HS-PDSCH channels on this frequency, the HSDPA resources on other frequency/frequencies shall remain unchanged.]
-	[1.28Mcps TDD - If the DL Timeslot and Code Information LCR per UARFCN IE contains no DL Timeslot and Code Information LCR IE but contains UARFCN IE, the existing HS-PDSCH resources on the frequency indicated by the UARFCN IE shall be deleted, the HSDPA resources on other frequency/frequencies shall remain unchanged.]
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes Add to HS-SCCH Resource Pool IE, the Node B shall add this resource to the HS-SCCH resource pool to be used to assign HS-SCCH sets.]
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Modify HS-SCCH Resource Pool IEs and includes any of [3.84Mcps TDD - TDD Channelisation Code IE, Midamble Shift and Burst Type IE, Time Slot IE], [1.28Mcps TDD - First TDD Channelisation Code IE, Second TDD Channelisation Code IE, Midamble Shift LCR IE, Time Slot LCR IE, TDD Channelisation Code IE], [7.68Mcps TDD - TDD Channelisation Code 7.68Mcps IE, Midamble Shift and Burst Type 7.68Mcps IE, Time Slot IE], for either HS-SCCH or HS-SICH channels, the Node B shall apply these as the new values, otherwise the old values specified for this set are still applicable.]
[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Modify HS-SCCH Resource Pool IEs and includes any UARFCN IEs related to HS-SCCH or HS-SICH channels, the Node B shall apply these configurations on the new frequency, otherwise the old frequency is still applicable.]
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Modify HS-SCCH Resource Pool IEs and includes theHS-SCCH Maximum Power IE, the Node B shall apply this value for the specified HS-SCCH code otherwise the old value is still applicable.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Modify HS-SCCH Resource Pool IEs and includes the HS-SICH Reference Signal Information IE in the HS-SICH Reference Signal Information Modify IE, the Node B shall apply this HS-SICH reference signal configuration. Else if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Modify HS-SCCH Resource Pool IEs and includes the HS-SICH Reference Signal Modify IE but does not contain the HS-SICH Reference Signal Information IE in the HS-SICH Reference Signal Modify IE, the Node B shall delete this HS-SICH reference signal configuration for the specified HS-SCCH. Otherwise the old configration is still applicable.]
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Delete from HS-SCCH Resource Pool IEs, the Node B shall delete these resources from the HS-SCCH resource pool.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes Add to Non-HS-SCCH associated HS-SICH Resource Pool IEs and includes UARFCN IEs related to HS-SICH channel, the Node B shall add this resource to the non-HS-SCCH associated HS-SICH resource pool on the indicated frequency, otherwise the Node B shall add this resource to the non-HS-SCCH associated HS-SICH resource pool on the primary frequency.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes Modify Non-HS-SCCH associated HS-SICH Resource Pool IEs and includes UARFCN IEs related to HS-SICH channel, the Node B shall apply these configurations on the new frequency, otherwise the old frequency is still applicable.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Delete from Non-HS-SCCH associated HS-SICH Resource Pool IEs, the Node B shall delete these resources from the non-HS-SCCH associated HS-SICH resource pool.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes HS-PDSCH And HS-SCCH Scrambling Code IE in the HSDPA And E-DCH Cell Portion Information IE, the Node B shall use this as the scrambling code for all HS-PDSCHs and HS-SCCHs for the cell portion indicated by Cell Portion ID. If a value has never been set, the Node B shall use the primary scrambling code for all HS-PDSCH and HS-SCCH codes for the cell portion indicated by Cell Portion ID.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes HS-PDSCH FDD Code Information IE in the HSDPA And E-DCH Cell Portion Information IE, the Node B shall:
-	if the Number Of HS-PDSCH Codes IE is set to "0", delete any existing HS-PDSCH resources from the cell portion indicated by Cell Portion ID IE.
-	if the Number Of HS-PDSCH Codes IE is set to any value other than "0" and HS-PDSCH resources are not currently configured in the cell portion indicated by Cell Portion ID IE, use this list as the range of codes for HS-PDSCH channels.
-	if the Number Of HS-PDSCH Codes IE is set to any value other than "0" and HS-PDSCH resources are currently configured in the cell portion indicated by Cell Portion ID IE, replace the current range of codes with this new range of codes for HS-PDSCH channels.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes HS-SCCH FDD Code Information IE in the HSDPA And E-DCH Cell Portion Information IE, the Node B shall:
-	If the HS-SCCH FDD Code Information IE contains no codes, delete any existing HS-SCCH resources from the cell portion indicated by Cell Portion ID IE.
-	If the HS-SCCH FDD Code Information IE contains one or more codes and HS-SCCH resources are not currently configured in the cell portion indicated by Cell Portion ID IE, use this list of codes as the list of codes for HS-SCCH channels.
-	If the HS-SCCH FDD Code Information IE contains one or more codes and HS-SCCH resources are currently configured in the cell portion indicated by Cell Portion ID IE, replace the current list of codes with this new list of codes for HS-SCCH channels.]
[FDD - Enhanced Cell_FACH Operation]:
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the HS-DSCH Common System Information IE, then the Node B shall: 
-	If the HS-DSCH Common Information IE is included, then the Node B shall apply the parameters to the enhanced FACH in new configuration:
-	If the Discard Timer IE is included in the Priority Queue Information for Enhanced FACH IE, then the Node B shall use this information to discard out-of-date MAC-ehs SDUs from the related HSDPA Priority Queue.
-	If the FACH Measurement Occasion Cycle Length Coefficient IE is included in the HS-DSCH Common Information IE, then the Node B shall use this information for MAC-ehs scheduling decisions. 
-	The Node B shall allocate HS-SCCH codes and include the HS-SCCH Specific Information Response IE in the HS-DSCH Common System Information Response IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message.
-	The Node B shall include the HARQ Memory Partitioning IE in the HS-DSCH Common System Information Response IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message.
-	If the Common MAC Flow Specific Information IE is included, then the Node B shall apply the parameters to the enhanced FACH in new configuration:
-	If the common MAC flow indicated by the Common MAC Flow ID exsits in the Node B, then the Node B shall apply the parameters to modify this common MAC flow; otherwise, the Node B shall apply the parameters to newly establish the common MAC flow.
-	If the Transport Layer Address IE and Binding ID IE are included in the Common MAC Flow Specific Information IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned Common MAC flow or Common MAC flow being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE.
-	If the TNL QoS IE is included and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related transport bearer.
-	The Node B shall include in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of transport bearer for every Common MAC flow being established.
-	The Node B shall include the HS-DSCH Initial Capacity Allocation IE in the HS-DSCH Common System Information Response IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message for every Common MAC flow being established, if the Node B allows the CRNC to start transmission of MAC-c PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. 
-	If the Common MAC Flow Priority Queue Information IE is included in the Common MAC Flow Specific Information IE, the Node B shall use the information for configuring HSDPA Priority Queues.]
-	If the Common HS-DSCH RNTI List IE is included, then the Node B may use this information for MAC-ehs scheduling decisions.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common MAC Flows To Delete IEs, then the Node B shall use this information to delete the indicated Common MAC flows. When a Common MAC flow is deleted, all its associated Priority Queues shall also be removed. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common MAC Flows To Delete IE requesting the deletion of all remaining Common MAC flows, then the Node B shall delete the HS-DSCH common system configuration and release the resources for enhanced FACH.]
[FDD - Enhanced Cell/URA_PCH Operation]:
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the HS-DSCH Paging System Information IE, then the Node B shall: 
-	If the Paging MAC flow indicated by the Paging MAC Flow ID exsits in the Node B, then the Node B shall apply the parameters to modify this Paging MAC flow; otherwise, the Node B shall apply the parameters to newly establish the Paging MAC flow.
-	If the Transport Layer Address IE and Binding ID IE are included in the Paging MAC Flow Specific Information IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned Paging MAC flow or Paging MAC flow being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE.
-	If the TNL QoS IE is included and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related transport bearer.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Paging MAC Flows To Delete IEs, then the Node B shall use this information to delete the indicated Paging MAC flows. When a Paging MAC flow is deleted, all its associated Priority Queues shall also be removed. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Paging MAC Flows To Delete IE requesting the deletion of all remaining Paging MAC flows, then the Node B shall delete the HS-DSCH paging system configuration and release the resources for enhanced PCH.]
[1.28Mcps TDD - Enhanced Cell_FACH Operation]:
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the HS-DSCH Common System Information LCR IE, then the Node B shall: 
-	If the HS-DSCH Common Information LCR IE is included, then the Node B shall apply the parameters to the enhanced FACH in new configuration:
-	If the Discard Timer IE is included in the Priority Queue Information for Enhanced FACH LCR IE, then the Node B shall use this information to discard out-of-date MAC-ehs SDUs from the related HSDPA Priority Queue.
-	If the FACH Measurement Occasion Cycle Length Coefficient IE is included in the HS-DSCH Common Information LCR IE, then the Node B shall use this information for MAC-hs scheduling decisions. 
-	The Node B shall allocate HS-SCCH codes and include the HS-SCCH Specific Information Response LCR IE in the HS-DSCH Common System Information Response LCR IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message.
-	The Node B shall include the HARQ Memory Partitioning IE in the HS-DSCH Common System Information Response LCR IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message. 
-	For a multi-frequency cell, if the HARQ Memory Partitioning IE is included in the HS-DSCH Common System Information Response LCR IE, the Node B shall include the UARFCN IE in the HS-DSCH Common System Information Response LCR IE to indicate the frequency of the HARQ Memory Partitioning IE in the HS-DSCH Common System Information Response LCR IE.
-	For a multi-frequency cell, the Node B can include the HARQ Memory Partitioning Per UARFCN IE in the HS-DSCH Common System Information Response LCR IE to indicate the HARQ Memory Partitioning infomation on the frequency indicated by the UARFCN IE in the HARQ Memory Partitioning Per UARFCN IE. 
-	The Node B shall use the value of the E-AGCH TPC Step Size IE contained in the Common E-PUCH Information LCR IE in the Common E-DCH System Information LCR IE for HS-SCCH inner loop power control.]
-	If the Common MAC Flow Specific Information LCR IE is included, then the Node B shall apply the parameters to the enhanced FACH in new configuration:
-	If the common MAC flow indicated by the Common MAC Flow ID LCR IE exsits in the Node B, then the Node B shall apply the parameters to modify this common MAC flow; otherwise, the Node B shall apply the parameters to newly establish the common MAC flow.
-	If the Transport Layer Address IE and Binding ID IE are included in the Common MAC Flow Specific Information LCR IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned Common MAC flow or Common MAC flow being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE.
-	If the TNL QoS IE is included and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related transport bearer.
-	The Node B shall include in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of transport bearer for every Common MAC flow being established.
-	The Node B shall include the HS-DSCH Initial Capacity Allocation IE in the HS-DSCH Common System Information Response LCR IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message for every Common MAC flow being established, if the Node B allows the CRNC to start transmission of MAC-c PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. 
-	If the Common MAC Flow Priority Queue Information LCR IE is included in the Common MAC Flow Specific Information LCR IE, the Node B shall use the information for configuring HSDPA Priority Queues.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common MAC Flows To Delete LCR IEs, then the Node B shall use this information to delete the indicated Common MAC flows. When a Common MAC flow is deleted, all its associated Priority Queues shall also be removed. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common MAC Flows To Delete LCR IE requesting the deletion of all remaining Common MAC flows, then the Node B shall delete the HS-DSCH common system configuration and release the resources for enhanced FACH.] 
[1.28Mcps TDD - If the Power Control GAP for CELL_FACH IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, the Node B may use the value for the power control for HS-SCCH, HS-SICH and E-AGCH according to TS 25.224 [21].]
[1.28Mcps TDD - If the UL Synchronisation Parameters LCR IE is included in the Common E-DCH System Information LCR IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, the Node B shall use the indicated values of Uplink Synchronisation Step Size IE and Uplink Synchronisation Frequency IE when evaluating the timing of the UL synchronisation.] 
[1.28Mcps TDD - If the Physical Channel ID for Common E-RNTI Requested Indicator IE in the Common E-DCH System Information LCR IE, if supported, the Node B shall included the Associated Phsical Channel ID IE in the Common E-RNTI Information LCR IE in the Common E-DCH System Information Response LCR IE to indicate the E-RUCCH associated with the related common E-RNTI group.]
[1.28Mcps TDD - Enhanced Cell/URA_PCH Operation]:
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the HS-DSCH Paging System Information LCR IE, then the Node B shall: 
-	If the Paging MAC flow indicated by the Paging MAC Flow ID IE exsits in the Node B, then the Node B shall apply the parameters to modify this Paging MAC flow; otherwise, the Node B shall apply the parameters to newly establish the Paging MAC flow.
-	If the Transport Layer Address IE and Binding ID IE are included in the Paging MAC Flow Specific Information LCR IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned Paging MAC flow or Paging MAC flow being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE.
-	If the TNL QoS IE is included and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related transport bearer.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Paging MAC Flows To Delete LCR IEs, then the Node B shall use this information to delete the indicated Paging MAC flows. When a Paging MAC flow is deleted, all its associated Priority Queues shall also be removed. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Paging MAC Flows To Delete LCR IE requesting the deletion of all remaining Paging MAC flows, then the Node B shall delete the HS-DSCH paging system configuration and release the resources for enhanced PCH.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common E-DCH System Information LCR IE, and the Scheduling Priority Indicator IE is present in the Common E-DCH Logical Channel information IE in the Common E-DCH MAC-d Flow Specific Information LCR IE, the Node B may use this IE to do the related scheduling operation.
[FDD - E-DCH Resources]:
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE, the Node B shall use this as the scrambling code for all E-AGCHs, E-RGCHs and E-HICHs. If a value has never been set, the Node B shall use the primary scrambling code for all E-AGCH, E-RGCH and E-HICH codes.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes E-AGCH FDD Code Information IE, the Node B shall:]
-	[FDD - If the E-AGCH FDD Code Information IE contains no codes, delete any existing E-AGCH resources from the cell.]
-	[FDD - If the E-AGCH FDD Code Information IE contains one or more codes and E-AGCH resources are not currently configured in the cell, use this list of codes as the list of codes for E-AGCH channels.]
-	[FDD - If the E-AGCH FDD Code Information IE contains one or more codes and E-AGCH resources are currently configured in the cell, replace the current list of codes with this new list of codes for E-AGCH channels.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes E-RGCH/E-HICH FDD Code Information IE, the Node B shall:]
-	[FDD - If the E-RGCH/E-HICH FDD Code Information IE contains no codes, delete any existing E-RGCH/E-HICH resources from the cell.]
-	[FDD - If the E-RGCH/E-HICH FDD Code Information IE contains one or more codes and E-RGCH/E-HICH resources are not currently configured in the cell, use this list of codes as the list of codes for E-RGCH/E-HICH channels.]
-	[FDD - If the E-RGCH/E-HICH FDD Code Information IE contains one or more codes and E-RGCH/E-HICH resources are currently configured in the cell, replace the current list of codes with this new list of codes for E-RGCH/E-HICH channels.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Maximum Target Received Total Wide Band Power IE, the Node B shall use this value to control E-DCH scheduling.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Reference Received Total Wide Band Power IE, the Node B may use this value to control E-DCH scheduling.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Target Non-serving E-DCH to Total E-DCH Power Ratio IE, the Node B shall store this value and use this value for E-DCH scheduling by controlling the ratio of received E-DCH wide band power from non-serving UEs to the total received E-DCH power.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE in the HSDPA And E-DCH Cell Portion Information IE, the Node B shall use this as the scrambling code for all E-AGCHs, E-RGCHs and E-HICHs for the cell portion indicated by Cell Portion ID. If a value has never been set, the Node B shall use the primary scrambling code for all E-AGCH, E-RGCH and E-HICH codes for the cell portion indicated by Cell Portion ID.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes E-AGCH FDD Code Information IE in the HSDPA And E-DCH Cell Portion Information IE, the Node B shall:] 
-	[FDD - If the E-AGCH FDD Code Information IE contains no codes, delete any existing E-AGCH resources from the cell portion indicated by Cell Portion ID IE.]
-	[FDD - If the E-AGCH FDD Code Information IE contains one or more codes and E-AGCH resources are not currently configured in the cell portion indicated by Cell Portion ID IE, use this list of codes as the list of codes for E-AGCH channels.]
-	[FDD - If the E-AGCH FDD Code Information IE contains one or more codes and E-AGCH resources are currently configured in the cell portion indicated by Cell Portion ID IE, replace the current list of codes with this new list of codes for E-AGCH channels.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes E-RGCH/E-HICH FDD Code Information IE in the HSDPA And E-DCH Cell Portion Information IE, the Node B shall:]
-	[FDD - If the E-RGCH/E-HICH FDD Code Information IE contains no codes, delete any existing E-RGCH/E-HICH resources from the cell portion indicated by Cell Portion ID IE.]
-	[FDD - If the E-RGCH/E-HICH FDD Code Information IE contains one or more codes and E-RGCH/E-HICH resources are not currently configured in the cell portion indicated by Cell Portion ID IE, use this list of codes as the list of codes for E-RGCH/E-HICH channels.]
-	[FDD - If the E-RGCH/E-HICH FDD Code Information IE contains one or more codes and E-RGCH/E-HICH resources are currently configured in the cell portion indicated by Cell Portion ID IE, replace the current list of codes with this new list of codes for E-RGCH/E-HICH channels.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Maximum Target Received Total Wide Band Power IE in the HSDPA And E-DCH Cell Portion Information IE, the Node B shall, if supported, use this value to control E-DCH scheduling in the cell portion indicated by Cell Portion ID IE.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Reference Received Total Wide Band Power IE in the HSDPA And E-DCH Cell Portion Information IE, the Node B may use this value to control E-DCH scheduling in the cell portion indicated by Cell Portion ID IE.]
[TDD - E-DCH Resources]:
[3.84Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes  E-PUCH Information IE, the Node B shall:
-	If the E-PUCH Information IE contains no E-PUCH Timeslot Information IE, then the Node B shall delete any existing E-DCH resources from the cell.
-	If the  E-PUCH Information IE contains E-PUCH Timeslot Information IE and E-DCH resources are not currently configured in the cell, use this IE as the list of timeslots for E-PUCH channels.
-	If the  E-PUCH Information IE contains E-PUCH Timeslot Information IE and E-DCH resources are currently configured in the cell, replace the current list of timeslots with this new list of timeslots for E-PUCH channels.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes  E-PUCH Information 1.28Mcps IE, the Node B shall:
-	If the E-PUCH Information 1.28Mcps IE contains no E-PUCH Timeslot Information 1.28Mcps per UARFCN IE, then the Node B shall delete any existing E-DCH resources from the cell.
-	For a single-frequency cell, if the E-PUCH Information 1.28Mcps IE contains E-PUCH Timeslot Information 1.28Mcps per UARFCN IE and E-DCH resources are not currently configured in the cell, use this IE as the list of timeslots / codes for E-PUCH channels.
-	For a single-frequency cell, if the  E-PUCH Information 1.28Mcps IE contains E-PUCH Timeslot Information 1.28Mcps per UARFCN IE and E-DCH resources are currently configured in the cell, replace the current list of timeslots / codes with this new list of timeslots / codes for E-PUCH channels.
-	For a multi-frequency cell, if the E-PUCH Information 1.28Mcps IE contains E-PUCH Timeslot Information 1.28Mcps per UARFCN IE and E-DCH resources are not currently configured on the indicated frequency in the cell, use this IE as the list of frequency / timeslots / codes for E-PUCH channels, the E-DCH resources on other frequency shall remain unchanged.
-	For a multi-frequency cell, if the E-PUCH Information 1.28Mcps IE contains E-PUCH Timeslot Information 1.28Mcps per UARFCN IE and E-DCH resources are currently configured on the indicated frequency in the cell, replace the current list of frequency / timeslots / codes with this new list of timeslots / codes for E-PUCH channels, the E-DCH resources on other frequency shall remain unchanged.
-	For a multi-frequency cell, if the E-PUCH Information 1.28Mcps IE contains E-PUCH Timeslot Information 1.28Mcps per UARFCN IE but only UARFCN IE is included, then the Node B shall delete the existing E-DCH resources on the frequency indicated by the UARFCN IE from the cell, the E-DCH resources on other frequency shall remain unchanged.]
[7.68Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes  E-PUCH Information 7.68Mcps IE, the Node B shall:
-	If the E-PUCH Information 7.68Mcps IE contains no E-PUCH Timeslot Information IE, then the Node B shall delete any existing E-DCH resources from the cell.
-	If the  E-PUCH Information 7.68Mcps IE contains E-PUCH Timeslot Information IE and E-DCH resources are not currently configured in the cell, use this IE as the list of timeslots for E-PUCH channels.
-	If the  E-PUCH Information 7.68Mcps IE contains E-PUCH Timeslot Information IE and E-DCH resources are currently configured in the cell, replace the current list of timeslots with this new list of timeslots for E-PUCH channels.]
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes [3.84Mcps TDD - Add to E-AGCH Resource Pool IE] [1.28Mcps TDD - Add to E-AGCH Resource Pool 1.28Mcps IE][7.68Mcps TDD - Add to E-AGCH Resource Pool 7.68Mcps IE], the Node B shall add this resource to the E-AGCH resource pool to be used to assign E-AGCH sets.]
[3.84Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Modify E-AGCH Resource Pool IEs and includes any of  TDD Channelisation Code IE, Midamble Shift and Burst Type IE, Time Slot IE, for E-AGCH channels, the Node B shall apply these as the new values, otherwise the old values specified for this set are still applicable.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Modify E-AGCH Resource Pool 1.28Mcps IEs and includes any of  First TDD Channelisation Code IE, Second TDD Channelisation Code IE, Midamble Shift LCR IE, Time Slot LCR IE, UARFCN IE for E-AGCH channels, the Node B shall apply these as the new values, otherwise the old values specified for this set are still applicable.]
[7.68Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Modify E-AGCH Resource Pool 7.68Mcps IEs and includes any of  TDD Channelisation Code 7.68Mcps IE, Midamble Shift and Burst Type 7.68Mcps IE, Time Slot IE, for E-AGCH channels, the Node B shall apply these as the new values, otherwise the old values specified for this set are still applicable.]
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any [3.84Mcps TDD - Modify E-AGCH Resource Pool IEs] [1.28Mcps - Modify E-AGCH Resource Pool 1.28Mcps  IEs ][7.68Mcps TDD - Modify E-AGCH Resource Pool 7.68Mcps IEs]and includes the Maximum E-AGCH Power IE, the Node B shall apply this value for the specified E-AGCH code otherwise the old value is still applicable.]
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Delete from E-AGCH Resource Pool IEs, the Node B shall delete these resources from the E-AGCH resource pool.]
[3.84Mcps TDD and 7.68Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the [3.84Mcps TDD - E-HICH Information IE] [7.68Mcps TDD - E-HICH Information 7.68Mcps IE], the Node B shall configure the E-HICH according to the parameters.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Add to E-HICH Resource Pool 1.28Mcps IE, the Node B shall add this resource to the E-HICH resource pool to be used to assign Scheduled or Non-scheduled E-HICH sets.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Modify E-HICH Resource Pool 1.28Mcps IEs and includes any of  E-HICH Type IE, TDD Channelisation Code IE, Midamble Shift LCR IE, Time Slot LCR IE, UARFCN IE for E-HICH channels, the Node B shall apply these as the new values, otherwise the old values specified for this set are still applicable.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Modify E-HICH Resource Pool 1.28Mcps  IEs and includes the Maximum E-HICH Power IE, the Node B shall apply this value for the specified E-HICH code otherwise the old value is still applicable.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any Delete from E-HICH Resource Pool 1.28Mcps IEs, the Node B shall delete these resources from the E-HICH resource pool.]
[3.84Mcps TDD and 7.68Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Maximum Generated Received Total Wide Band Power in Other Cells IE, the Node B shall use this value to control E-DCH scheduling.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes Maximum Target Received Total Wide Band Power LCR IE, the Node B shall use this value to control E-DCH scheduling.] 
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes Maximum RTWP per UARFCN information LCR IE, the Node B may use this value to control E-DCH scheduling in a multi-frequency cell and ignore the Maximum Target Received Total Wide Band Power LCR IE.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes Maximum Target Received Total Wide Band Power per CELL PORTION LCR IE, the Node B may use this value to control E-DCH scheduling for the cell portion indicated by Cell Portion ID IE.]
[TDD - PDSCH/PUSCH Addition]:
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any PDSCH sets or PUSCH sets to be added, the Node B shall add these new sets to its PDSCH/PUSCH configuration.]
[1.28Mcps TDD - If the TSTD Indicator IE is included in PDSCH To Add Information LCR IE and is set to "active", the Node B shall activate TSTD diversity for PDSCH transmissions using the specified PDSCH Set that are not beacon channels (TS 25.221 [19], TS 25.224 [21]). If the TSTD Indicator IE is set to "not active" or the TSTD Indicator IE is not included in PDSCH To Add Information LCR IE, the Node B shall not activate TSTD diversity for the PDSCH Set.]
[TDD - PDSCH/PUSCH Modification]:
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any PDSCH sets or PUSCH sets to be modified, and includes any of [3.84Mcps TDD - DL/UL Code Information IE, Midamble Shift And Burst Type IE, Time Slot IE], [1.28Mcps TDD - DL/UL Code Information LCR IE, Midamble Shift LCR IE, Time Slot LCR IE], [7.68Mcps TDD - DL/UL Code Information 7.68Mcps IE, Midamble Shift And Burst Type 7.68Mcps IE, Time Slot IE], TDD Physical Channel Offset IE, Repetition Period IE, Repetition Length IE, or TFCI Presence IE, the Node B shall apply these as the new values, otherwise the old values specified for this set are still applicable.]
[TDD - PDSCH/PUSCH Deletion]:
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes any PDSCH sets or PUSCH sets to be deleted the Node B shall delete these sets from its PDSCH/PUSCH configuration.]
[1.28Mcps TDD - SYNC_UL Partition]:
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes SYNC_UL Partition Information IE, the Node B shall store the E-RUCCH SYNC_UL codes bitmap IE used to differentiate the E-DCH random access from the RACH random access according to TS 25.224 [21].]
[FDD – Common E-DCH Operation]:
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common E-DCH System Information IE, then the Node B shall: 
-	If the Common E-DCH UL DPCH Information IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration:
-	If the Common E-DCH E-DPCH Information IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration:
-	If the E-RGCH 2-Index-Step Threshold IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, the Node B shall use the value when the new configuration is being used. For the case of initial assignment of E-DCH related resources to the Node B, if E-RGCH 2-Index-Step Threshold IE is not present, the Node B shall use the default value defined in TS 25.331 [18].
-	If the E-RGCH 3-Index-Step Threshold IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, the Node B shall use the value when the new configuration is being used. For the case of initial assignment of E-DCH related resources to the Node B, if E-RGCH 3-Index-Step Threshold IE is not present, the Node B shall use the default value defined in TS 25.331 [18].
-	If the Common E-DCH Information IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration:
-	If the E-DCH Reference Power Offset IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-i PDU and to determine the value of the actual HARQ power offset.
-	If the E-DCH Power Offset for Scheduling Info IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-is PDUs.
-	If the Maximum TB Sizes IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B may use this information for the Node B scheduler in the new configuration.
-	If the Common E-DCH Additional Transmission Back Off IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B may use this information for the related common E-DCH resource allocation operation.
-	If the Common E-DCH Implicit Release Timer IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this information for the related common E-DCH resource release decision.
-	If the Common E-DCH HS-DPCCH Information IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration.
-	If the Common E-DCH CQI Information is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use the information for CQI operation in the new configuration. 
-	If the Common E-DCH Preamble Control Information IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration:
-	If the E-AI Indicator IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this value for configuration of E-AIs on the AICH.
-	If the Common E-DCH AICH Information IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this information for configuration of AICH.
-	If the Common E-DCH F-DPCH Information IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration. 
-	If the Initial DL Transmission Power IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall, if supported, use this value for configuration of Initial DL Transmission Power on the F-DPCH.
-	If the Maximum DL Power IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall, if supported, use this value for configuration of Maximum DL Power on the F-DPCH.
-	If the Minimum DL Power IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall, if supported, use this value for configuration of Minimum DL Power on the F-DPCH.
-	If the Common E-DCH E-AGCH Channelisation Code Number IE is included, then the Node B shall use the indicated channelization code for the E-AGCH for the common E-DCH in the new configuration. 
-	If the Common E-DCH Resource Combination Information IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration:
-	If the E-RGCH Signature Sequence IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall configure the E-RGCH for the combination and use indicated signature sequence. 
-	If the UL Common MAC Flow Specific Information IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration:
-	If the Transport Layer Address IE and Binding ID IE are included in the UL Common MAC Flow Specific Information IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned UL Common MAC flow.
-	If the TNL QoS IE is included and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related transport bearer.
-	The Node B shall include in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of transport bearer for every UL Common MAC flow being established.
-	If the Bundling Mode Indicator IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message and the Bundling Mode Indicator IE is set to "Bundling" and the E-TTI IE is set to "2ms", then the Node B shall use the bundling mode for the Common E-DCH UL data frames for the related UL Common MAC flow, otherwise the Node B shall use the non-bundling mode for the Common E-DCH UL data frames for the related UL Common MAC flow.
-	If the E-DCH MAC-d Flow Multiplexing List IE is included for a Common E-DCH MAC-d flow in the Common E-DCH MAC-d Flow Specific Information IE, the Node B shall use this information for the related resource allocation operation.]
-	If the Concurrent Deployment of 2ms and 10ms TTI IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message and if the Common E-DCH MAC-d flow info for Concurrent TTI IE is included for a Common E-DCH MAC-d flow in the Common E-DCH MAC-d Flow Specific Information IE, the Node B shall use this information for the transmission with the concurrent TTI.
-	If the E-RNTI List Request IE is included, then the Node B shall, if supported, include the E-RNTI List IE in the Common E-DCH System Information Response IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message.
-	If the E-RNTI Set IE is included, then the Node B shall, if supported, not allocate any E-RNTIs listed in this IE for a UE.
-	If supported, the Node B shall include UE Status Update Confirm Indicator IE in the Common E-DCH System Information Response IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message to indicate that the Node B supports of UE status update confirmation procedure for releasing E-RNTI.
-	If the Concurrent Deployment of 2ms and 10ms TTI IE is included, then the Node B shall, if supported, apply the parameters to the common E-DCH in new configuration:
-	If the E-DPCCH Power Offset, E-RGCH 2-Index-Step Threshold, E-RGCH 3-Index-Step Threshold,or E-DCH Reference Power Offset IE is not included in the Common E-DCH System Info Parameters for Concurrent TTI IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use the corresponding IE included in Common E-DCH E-DPCH Information IE.
-	If the E-DCH Reference Power Offset, E-DCH Power Offset for Scheduling Info, Maximum E-DCH resource allocation for CCCH, Maximum period for collision resolution phase, Maximum TB Sizes, or Common E-DCH Additional Transmission Back Off IE is not included in the Common E-DCH System Info Parameters for Concurrent TTI IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use the corresponding IE included in Common E-DCH Information IE.
-	If the Common E-DCH E-AGCH Channelisation Code Number IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use corresponding IE included in Common E-DCH System Information IE.
-	If the Common E-DCH HS-DPCCH Information for Concurrent TTI IE is included in the Common E-DCH System Info Parameters for Concurrent TTI IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this information for the related HS-DPCCH information in the new configuration.
-	If the Common E-DCH Preamble Control Information extension Type1 IE is included, then the Node B shall, if supported, use this information for 10ms TTI type decisions in new configuration.:
-	If the AICH Info IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this information for configuration of AICH.
-	If the Common E-DCH Preamble Control Information extension Type2 IE is included, then the Node B shall, if supported, use this information for 2ms TTI type and Concurrent TTI capability decisions in new configuration.:
-	If the AICH Info IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this information for configuration of AICH.
-	If the Common E-DCH Preamble Control Information extension Type3 IE is included, then the Node B shall, if supported, use this information for 2ms TTI type and Per HARQ and TTI alignment capability decisions in new configuration.:
-	If the AICH Info IE is included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall use this information for configuration of AICH.
-	If the NodeB Triggered HS-DPCCH Transmission Information IE is included, then the Node B shall, if supported, apply the parameters to the Node B Triggered HS-DPCCH Transmission in new configuration:
-	If the Per HARQ Activation and Deactivation IE is included, then the Node B shall apply the parameters to the Per HARQ Activation and Deactivation in new configuration.
-	If the Coffset IE is included, then the Node B shall, if supported, apply the parameters to the TTI alignment in new configuration.
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common UL MAC Flows To Delete IEs, then the Node B shall use this information to delete the indicated Common UL MAC flows. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common UL MAC Flows To Delete IE requesting the deletion of all remaining Common UL MAC flows, then the Node B shall delete the common E-DCH system configuration and release the resources for Common E-DCH.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common E-DCH MAC-d Flows To Delete IEs, then the Node B shall use this information to delete the indicated Common E-DCH MAC-d flows. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common E-DCH MAC-d Flows To Delete IE requesting the deletion of all remaining Comm E-DCH MAC-d flows associated to a Common UL MAC flow, then the Node B shall release the resources for the Common UL MAC flow.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the E-AGCH Power Offset IE, then the Node B may use this value to determine the E-AGCH power.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the E-RGCH Power Offset IE, then the Node B may use this value to determine the E-RGCH power.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the E-HICH Power Offset IE, then the Node B may use this value to determine the E-HICH power.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common E-RGCH Operation Indicator IE, then the Node B shall, if supported, contain the Common E-RGCH Info IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message.]
[1.28Mcps TDD – Common E-DCH Operation]:
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common E-DCH System Information LCR IE, then the Node B shall: 
-	If the UL Common MAC Flow Specific Information LCR IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration:
-	If the Transport Layer Address IE and Binding ID IE are included in the UL Common MAC Flow Specific Information IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned UL Common MAC flow.
-	If the TNL QoS IE is included and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related transport bearer.
-	The Node B shall include in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of transport bearer for every UL Common MAC flow being established.
-	If the E-DCH MAC-d Flow Multiplexing List IE is included for a Common E-DCH MAC-d flow in the Common E-DCH MAC-d Flow Specific Information LCR IE, the Node B shall use this information for the related resource allocation operation.]
-	If the Common E-PUCH Information LCR IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration.
-	If the E-TFCS Information TDD IE is included, then the Node B shall apply the parameters to the common E-DCH in new configuration.
-	If supported, the Node B shall include UE Status Update Confirm Indicator IE in the Common E-DCH System Information ResponseLCR IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message to indicate that the Node B supports of UE status update confirmation procedure for releasing E-RNTI.
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common E-DCH MAC-d Flows To Delete LCR IEs, then the Node B shall use this information to delete the indicated  Common E-DCH MAC-d flows. If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common UL MAC Flows to Delete LCR IE requesting the deletion of all remaining Comm E-DCH MAC-d flows associated to a Common UL MAC flow, then the Node B shall release the resources for the Common UL MAC flow.]
[FDD – Enhanced UE DRX Operation]:
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Enhanced UE DRX Information IE, then the Node B shall use the information to execute Enhanced UE DRX for the cell.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Further Enhanced UE DRX Information IE, then the Node B shall, if supported, use the information to execute Further Enhanced UE DRX in new configuration:
-	For the case of 1-level DRX is configured to the Node B, if HS-DSCH second Rx burstFACH or T32y IE is not present, the Node B shall use the default value defined in TS 25.331 [18].
-	For the case of 2-level DRX is configured to the Node B, if T32x, HS-DSCH first Rx burstFACH, HS-DSCH first DRX cycleFACH, HS-DSCH second Rx burstFACH, or T32y IE is not present, the Node B shall use the default value defined in TS25.331 [18].
[1.28Mcps DD – Enhanced UE DRX Operation]:
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Enhanced UE DRX Information LCR IE, then the Node B shall use the information to execute Enhanced UE DRX for the cell.] 
[1.28Mcps TDD - Shared physical channels Synchronisation Detection]:
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the Out-of-sync Detection Window IE, then the Node B shall use this IE to detect the synchronization status of UE as described in ref TS 25.224 [21], subclause 5.3.2A.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Treset Usage Indicator IE, if supported, the Node B shall stop using all configured MAC-ehs Reset Timers for the UEs in enhanced CELL_PCH or CELL_FACH with dedicated H-RNTI according to TS 25.321 [32].]
[1.28Mcps TDD – Shared physical channels In Synchronisation Indication]:
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the In Sync Indication Information LCR IE, then the Node B may use this information for MAC-hs/ehs scheduling.]
Response Message:
HS-DSCH/HS-SCCH Resources:
In the successful case involving HS-PDSCH or HS-SCCH resources, the Node B shall store the value of Configuration Generation ID IE and it shall make these resources available to all the current and future HS-DSCH transport channels; and shall respond with PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message.
[TDD - PDSCH/PUSCH Addition/Modification/Deletion]:
[TDD - In the successful case involving PDSCH/PUSCH addition, modification or deletion, the Node B shall add, modify and delete the PDSCH Sets and PUSCH Sets in the Common Transport Channel data base, as requested in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, and shall make these available to all the current and future DSCH and USCH transport channels. The  Node B shall respond with the PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message.]
8.2.18.3	Unsuccessful Operation

Figure 27: Physical Shared Channel Reconfiguration procedure: Unsuccessful Opreration
If the Node B is not able to support all parts of the configuration, it shall reject the configuration of all the channels in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message. The Cause IE shall be set to an appropriate value [TDD - either a single general cause value or PDSCH and PUSCH set specific cause values for each set that caused a failure within the Unsuccessful DL Shared Channel Set IE for PDSCH sets or Unsuccessful UL Shared Channel Set IE for PUSCH sets]. The Configuration Generation ID shall not be changed in the Node B.
If the configuration was unsuccessful, the Node B shall respond with the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message:
[1.28Mcps TDD - For a multi-frequency cell, if the Node B is not able to support all parts of the configuration, in the case the Node B can only support configuration on one or some frequencies, the HSDPA or E-DCH related resources on this or these frequencies may be regarded as having successfully been established/reconfigured/removed, the Node B shall reject the HSDPA or E-DCH related configuration on other failed frequencies. The Node B may respond with the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message. The HS-Cause IE or E-Cause IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message may be set to specific cause values for each frequency that caused a HSDPA or E-DCH related configuration failure. If the failure occurs on the HS-PDSCH, HS-SCCH, E-PUCH or E-AGCH resources, the Node B may store the value of the Configuration Generation ID IE and it shall make these resources available to all the current and future HS-DSCH or E-DCH transport channels. If the Node B is not able to support the HSDPA or E-DCH related configuration on any frequencies, the Cause IE may be set to an appropriate value, which is either a general cause value or specific cause values for each frequency that caused a failure. For the successfully configured HSUPA frequencies, the E-HICH Time Offset LCR per UARFCN IE may be included in the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message. For the successfully configured Enhanced CELL_FACH frequencies, the Common System Information Response LCR IE may be included in the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.]
Typical cause values are as follows:
Radio Network Layer Cause:
-	Cell not available
-	Node B Resources unavailable
Transport Layer Cause:
-	Transport Resources Unavailable
Miscellaneous Cause:
-	O&M Intervention
-	Control processing overload
-	HW failure
8.2.18.4	Abnormal Conditions
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains Add to HS-SCCH Resource Pool IE, the Modify HS-SCCH Resource Pool IE, or the Delete from HS-SCCH Resource Pool IE and does not contain the Configuration Generation ID the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[3.84Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the Add to E-AGCH Resource Pool IE, the Modify E-AGCH Resource Pool IE, or the Delete from E-AGCH Resource Pool IE and does not contain the Configuration Generation ID the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the Add to E-AGCH Resource Pool 1.28Mcps IE, the Modify E-AGCH Resource Pool 1.28Mcps IE, or the Delete from E-AGCH Resource Pool IE and does not contain the Configuration Generation ID the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[1.28Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the Add to E-HICH Resource Pool 1.28Mcps IE, the Modify E-HICH Resource Pool 1.28Mcps IE, or the Delete from E-HICH Resource Pool 1.28Mcps IE and does not contain the Configuration Generation ID the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[7.68Mcps TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the Add to E-AGCH Resource Pool 7.68Mcps IE, the Modify E-AGCH Resource Pool 7.68Mcps IE, or the Delete from E-AGCH Resource Pool IE and does not contain the Configuration Generation ID the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[TDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the Configuration Generation ID IE and does not contain at least one of Add to HS-SCCH Resource Pool IE, the Modify HS-SCCH Resource Pool IE, [3.84Mcps TDD -  the Add to E-AGCH Resource Pool IE, the Modify E-AGCH Resource Pool IE, the Delete from E-AGCH Resource Pool IE,] [1.28Mcps TDD - the Add to E-AGCH Resource Pool 1.28Mcps IE, the Modify E-AGCH Resource Pool 1.28Mcps IE, the Delete from E-AGCH Resource Pool IE, the Add to E-HICH Resource Pool 1.28Mcps IE, the Modify E-HICH Resource Pool 1.28Mcps IE, the Delete from E-HICH Resource Pool 1.28Mcps IE,][7.68Mcps TDD -  the Add to E-AGCH Resource Pool 7.68Mcps IE, the Modify E-AGCH Resource Pool 7.68Mcps IE, the Delete from E-AGCH Resource Pool IE,] or the Delete from HS-SCCH Resource Pool IE the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[FDD - If neither E-AGCH nor E-HICH/E-RGCH resources are configured in the cell, and if one or more codes are included in the E-AGCH FDD Code Information IE and/or E-RGCH/E-HICH FDD Code Information IE but the Maximum Target Received Total Wide Band Power IE is not included in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then the Node B shall send PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE, and the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE is not identical to the scrambling code of the phase reference, then the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE in the HSDPA And E-DCH Cell Portion Information IE, and the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE is not identical to the scrambling code of the phase reference, then the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes HS-DSCH Common Information IE and/or Common MAC Flow Specific Information IE and if the Priority Queues associated with the same Common MAC Flow ID IE have the same Scheduling Priority Indicator IE value, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.]
[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the UARFCN IE in the DL Timeslot and Code Information LCR per UARFCN IE in the HS-PDSCH TDD Information IE, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the UARFCN IE in the HS-SCCH Information LCR IE in the Add to HS-SCCH Resource Pool IE, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the UARFCN IE in the HS-SCCH Information LCR IE in the Modify HS-SCCH Resource Pool IE, the HS-SCCH information on the new frequency shall be provided, otherwise the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the UARFCN IE in the E-AGCH Information 1.28Mcps IE in the Modify E-AGCH Resource Pool 1.28Mcps IE, the E-AGCH information on the new frequency shall be provided, otherwise the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message contains the UARFCN IE in the E-HICH Information 1.28Mcps IE in the Modify E-HICH Resource Pool 1.28Mcps IE, the E-HICH information on the new frequency shall be provided, otherwise the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the DL Timeslot and Code Information LCR IE in the DL Timeslot and Code Information LCR per UARFCN IE in the HS-PDSCH TDD Information IE but contains UARFCN IE, and no HS-DSCH resources are configured on the frequency within the cell, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the UARFCN IE in the E-PUCH Timeslot Information 1.28Mcps per UARFCN IE in the E-PUCH Information 1.28Mcps IE, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the UARFCN IE in the Add to E-AGCH Resource Pool 1.28Mcps IE, the Modify E-AGCH Resource Pool 1.28Mcps IE, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the UARFCN IE in the Add to E-HICH Resource Pool 1.28Mcps IE, the Modify E-HICH Resource Pool 1.28Mcps IE, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[1.28Mcps TDD - For a multi-frequency cell, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not contain the E-PUCH Timeslot Information 1.28Mcps IE in the E-PUCH Timeslot Information 1.28Mcps per UARFCN IE in the E-PUCH Information 1.28Mcps IE but contains UARFCN IE, and no E-DCH resources are configured on the frequency within the cell, the Node B shall consider the procedure as having failed and shall send the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message to the CRNC.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common E-DCH System Information IE and if the message does not contain the HS-DSCH Common System Information IE or the resource for enhanced FACH is not configured for the cell, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Enhanced UE DRX Information IE and if the message does not contain the HS-DSCH Common System Information IE or the resource for enhanced FACH is not configured for the cell, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes HS-DSCH Paging System Information IE and Paging MAC Flow Specific Information IE and if the Priority Queues associated with the same Paging MAC Flow ID IE have the same Scheduling Priority Indicator IE value, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Further Enhanced UE DRX Information IE and if the message does not contain the Enhanced UE DRX Information IE, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.]
[FDD - If the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message includes the Common E-RGCH Operation Indicator IE and if the message does not contain the Common E-DCH System Information IE, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.]
If ALCAP is not used, if the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE for the newly established Common MAC Flow, Paging MAC Flow and/or UL Common MAC Flow, the Node B shall reject the procedure using the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.
8.2.19	Reset
8.2.19.1	General
The purpose of the Reset procedure is to align the resources in the CRNC and the Node B in the event of an abnormal failure. The CRNC or the Node B may initiate the procedure.
8.2.19.2	Successful Operation
8.2.19.2.1	Reset Initiated by the CRNC

Figure 27A Reset procedure (CRNC to Node B), Successful Operation
The procedure is initiated with a RESET REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
If the Reset Indicator IE is set to "Communication Context", the Node B shall remove all the indicated Node B Communication Contexts (identified by a Node B Communication Context ID or a CRNC Communication Context ID IE) and all the radio resources allocated for these Node B Communication Contexts. The Node B shall also initiate release of the user plane transport bearers that were involved in these Contexts. After clearing all related resources, the Node B shall return the RESET RESPONSE message to the CRNC.
If the Reset Indicator IE is set to "Communication Control Port", the Node B shall remove all the Node B Communication Contexts controlled via the indicated Communication Control Port(s) and all the radio resources allocated for these Node B Communication Contexts. The Node B shall also initiate release of the user plane transport bearers that were involved in these Contexts. After clearing all related resources, the Node B shall return the RESET RESPONSE message to the CRNC.
If the Reset Indicator IE is set to "Node B", the Node B shall remove all the Node B Communication Contexts within the Node B and all the radio resources allocated for these Node B Communication Contexts. The Node B shall also initiate release of the user plane transport bearers that were involved in these Contexts. After clearing all related resources, the Node B shall return the RESET RESPONSE message to the CRNC.
8.2.19.2.2	Reset Initiated by the Node B

Figure 27B Reset procedure (Node B to CRNC ), Successful Operation
The procedure is initiated with a RESET REQUEST message sent from the Node B to the CRNC using the Node B Control Port.
If the Reset Indicator IE is set to "Communication Context", for all indicated CRNC Communication Contexts (indicated by a CRNC Communication Context ID or a Node B Communication Context ID IE), the CRNC shall remove the information related to this Node B and all the radio resources allocated in the CRNC. The CRNC shall also initiate release of the user plane transport bearers towards the Node B involved in the indicated CRNC Communication Contexts. After clearing all related resources, the CRNC shall return the RESET RESPONSE message to the Node B.
If the Reset Indicator IE is set to "Communication Control Port", for all the CRNC Communication Contexts controlled via the indicated Communication Control Port(s), the CRNC shall remove the information related to this Node B and all the radio resources allocated in the CRNC. The CRNC shall also initiate release of the user plane transport bearers towards the Node B involved in the CRNC Communication Contexts controlled via the indicated Communication Control Port(s). After clearing all related resources, the CRNC shall return the RESET RESPONSE message to Node B.
If the Reset Indicator IE is set to the "Node B", for all the CRNC Communication Contexts related to this Node B, the CRNC shall remove the information related to this Node B and all the radio resources allocated in the CRNC. The CRNC shall also initiate release of the user plane transport bearers towards the Node B involved in the CRNC Communication Contexts related to this Node B. After clearing all related resources, the CRNC shall return the RESET RESPONSE message to Node B.
8.2.19.3	Unsuccessful Operation
-
8.2.19.4	Abnormal Conditions
If the RESET REQUEST message is received any ongoing procedure related to a CRNC Communication Context in the CRNC or Node B Communication Context in the Node B indicated (explicitly or implicitly) in the message shall be aborted.
8.2.20	Cell Synchronisation Initiation [TDD]
8.2.20.1	General
This procedure is used by a CRNC to request the transmission of [3.84Mcps TDD - Cell Synchronisation Bursts sent in the PRACH time slots] [1.28Mcps TDD - SYNC_DL code sent in the DwPTS] and/or to start measurements on [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC_DL code] in a Node B.
8.2.20.2	Successful Operation


Figure 27C Cell Synchronisation Initiation procedure, Successful Operation
The procedure is initiated with a CELL SYNCHRONISATION INITIATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
Upon reception, the Node B shall initiate the requested transmission according to the parameters given in the request and start the measurement on [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC_DL code] if requested.
[3.84Mcps TDD - Cell Sync Burst Transmission Initiation] [1.28Mcps TDD - SYNC_DL Code Transmission Initiation LCR]:
When the [3.84Mcps TDD - Cell Sync Burst Transmission Initiation Information] [1.28Mcps TDD - SYNC_DL Code Transmission Initiation Information LCR] is present, the Node B shall configure the transmission of the cell synchronisation burst according to the parameters given in the CELL SYNCHRONISATION INITIATION REQUEST message. The SFN IE indicates the frame number when the cell shall start transmitting cell synchronisation bursts.
[3.84Mcps TDD - When the Cell Sync Burst Transmission Initiation Information is present and the "Frequency Acquisition" is indicated within the Synchronisation Report Type IE, the Node B shall first perform only frequency locking on received cell synchronisation bursts. Transmission of the indicated cell synchronisation bursts shall be started only if the frequency locking is performed successfully and "Frequency Acquisition completed" is reported to the RNC.]
[3.84Mcps TDD - Cell Sync Burst Measurement characteristics] [1.28Mcps TDD - SYNC_DL Code Measurement characteristics LCR]:
When the [3.84Mcps TDD - Cell Sync Burst Measurement Initiation Information][1.28Mcps TDD - SYNC_DL Code Measurement Initiation Information LCR] is present, the Node B shall initiate measurements on the indicated cell synchronisation burst.
If the SFN IE is present, the Node B shall after measurement of the indicated [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] adjust the frame number of the indicated cell according to the SFN of the CELL SYNCHRONISATION INITIATION REQUEST message. This adjustment shall only apply to the late entrant cell at the late entrant phase.
Synchronisation Report characteristics:
The Synchronisation Report Characteristics IE indicates how the reporting of the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] measurement shall be performed. Whenever the Cell Synchronisation Initiation procedure is initiated, only [3.84Mcps TDD - the "Frequency Acquisition completed" or] "Frame related" report characteristics type shall apply.
[3.84Mcps TDD - If the Synchronisation Report characteristics type IE is set to "Frequency Acquisition completed", the Node B shall signal completion of frequency acquisition to the RNC when locking is completed.]
If the Synchronisation Report characteristics type IE is set to "Frame related", the Node B shall report the result of the cell synchronisation burst measurement after every measured frame.
[3.84Mcps TDD - If the Cell Sync Burst Arrival Time IE is included in the Cell Sync Burst Information IE of the Synchronisation Report Characteristics IE, it indicates to the Node B the reference time at which the reception of the cell synchronisation burst of a neighbouring cell is expected.]
[3.84Mcps TDD - If the Cell Sync Burst Timing Threshold IE is included in the Cell Sync Burst Information IE of the Synchronisation Report Characteristics IE, the Node B shall use this threshold as a trigger for the CELL SYNCHRONISATION REPORT message.]
[1.28Mcps TDD - If the SYNC_DL Code ID Arrival Time IE is included in the SYNC_DL Code Information LCR IE of the Synchronisation Report Characteristics IE, it indicates to the Node B the reference time at which the reception of the SYNC_DL Code of a neighbouring cell is expected.]
[1.28Mcps TDD - If the SYNC_DL Code ID Timing Threshold IE is included in the SYNC_DL Code Information LCR IE of the Synchronisation Report Characteristics IE, the Node B shall use this threshold as a trigger for the CELL SYNCHRONISATION REPORT message.]
Response message:
If the Node B was able to initiate the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] transmission and/or measurement requested by the CRNC it shall respond with the CELL SYNCHRONISATION INITIATION RESPONSE message sent over the Node B Control Port.
8.2.20.3	Unsuccessful Operation


Figure 27D Cell Synchronisation Initiation procedure, Unsuccessful Operation
If the requested transmission or measurement on [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC_DL Code] cannot be initiated, the Node B shall send a CELL SYNCHRONISATION INITIATION FAILURE message over the Node B control port. The message shall include the Cause IE set to an appropriate value.
Typical cause values are as follows:
Radio Network Layer Cause:
-	Cell Synchronisation not supported
-	Power level not supported
-	Measurement Temporarily not Available
-	Frequency Acquisition not supported
Miscellaneous Cause:
-	O&M Intervention
-	HW failure
8.2.20.4	Abnormal Conditions
-
8.2.21	Cell Synchronisation Reconfiguration [TDD]
8.2.21.1	General
This procedure is used by a CRNC to reconfigure the transmission of [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC_DL Code] and/or to reconfigure measurements on [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC_DL Code] in a Node B.
8.2.21.2	Successful Operation
8.2.21.2.1	General


Figure 27E Cell Synchronisation Reconfiguration procedure, Successful Operation
The procedure is initiated with a CELL SYNCHRONISATION RECONFIGURATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
Upon reception, the Node B shall reconfigure the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] transmission and/or measurements according to the parameters given in the request. 
8.2.21.2.2	[3.84Mcps TDD - Cell Sync Burst Schedule]
Within the CELL SYNCHRONISATION RECONFIGURATION REQUEST message first the schedule for the steady state phase is fixed. I.e. the number of cycles per SFN period is defined with the same schedule. For each cycle, the number of repetitions is defined according to following equations: 
Cycle length:	4096 / value of Number Of Cycles Per SFN Period IE
Repetition period:	Cycle length / value of Number Of Repetitions Per Cycle Period IE
Cell Sync Frame number is calculated by: 
SFN = floor((k-1) * Cycle length + (i-1)* Repetition period)
	k = {1, 2, 3, .. Number of cycle per SFN period}
	i = {1, 2, 3, .. Cell Sync Frame number within cycle period}
8.2.21.2.3	[1.28Mcps TDD - SYNC_DL Code Schedule]
Within the CELL SYNCHRONISATION RECONFIGURATION REQUEST message first the schedule for the steady state phase is fixed. The "schedule" includes
-	the list of frame numbers SFN within the SFN period where SYNC_DL Code transmission or reception takes place, i.e. the "synchronisation frames", and
-	the associated actions (SYNC_DL Code transmission, reception, averaging, reporting etc) to be performed for synchronisation purpose by the Node B at each of these SFNs.
Within the synchronisation frames, only the first subframe shall be used for sending or receiving a SYNC_DL Code in the DwPTS while in the second subframe, normal operation continues.
The synchronisation schedule includes the option of averaging of measured correlation results within the Node B over a sequence of measurements, for increasing the reliability of the Time of Arrival measurement obtained from the correlation results. For this purpose, the concept of "subcycles" has been introduced: Each Synchronisation Cycle is devided into "subcycles" where in each subcycle, the same set of SYNC_DL transmissions and receptions is performed, and averaging takes place over all the subcycles within a Synchronisation Cycle. Since the list of actions (transmission, measurements etc) is the same in each subcycle, and the subcycles are repeated to make up a cycle, and the cycles make up an SFN period, the full list of actions is derived by the actions specified for a subcycle.
The full list of SFNs which make up the synchronisation schedule within the SFN period are calculated in Node B and CRNC autonomously based on the following parameters included in the CELL SYNCHRONISATION RECONFIGURATION REQUEST message: "Number of cycles per SFN period", "Number of subcycles per cycle period", and "Number of repetitions per cycles period", along the following equations:
Cycle length:	4096 / value of Number Of Cycles Per SFN Period IE
Subcycle length:	Cycle length / value of Number Of Subcycles Per Cycle Period IE
Repetition period:	Subcycle length / value of Number Of Repetitions Per Cycle Period IE
	SFN = floor((k-1) * Cycle length + (j-1)*Subcycle length + (i-1)* Repetition period)
	k = {1, 2, 3, .. Number of cycle per SFN period}
	j = {1, 2, 3, .. Number of subcycles per cycle}
	i = {1, 2, 3, .. Number of repetitions per cycle period}
Note that if the Number Of Subcycles Per Cycle IE is equal to 1, then the subcycles are identical to the "Synchronisation Cycles".
If the Number Of Subcycles Per Cycle IE is included in the CELL SYNCHRONISATION RECONFIGURATION REQUEST [TDD] message, then the Node B shall apply this number for dividing the Synchronisation Cycles in Subcycles. If the IE is not present, then the Node B shall assume that there is one subcycle per synchronisation cycle only, which is identical to the synchronisation cycle.
Averaging is performed as follows:
-	From each SYNC_DL code being received according to the schedule, the Node B shall calculate a "correlation function" by matching the received data with the respective expected code.
-	Therefore the set of measurements within one subcycle provides a set of "correlation functions".
-	The set of correlation functions of the first subcycle within a synchronisation cycle is stored in an averaging memory.
-	The sets of correlation functions of the subsequent subcycles within a synchronisation cycle are combined with the available contents of the "averaging memory", to produce an average over all the sets of correlation functions within a synchronisation cycle.
-	At the end of a synchronisation cycle, the Time-of-Arrival measurements for that synchronisation cycle are obtained by evaluating the final set of correlation functions.
These Time-of-Arrival measurements, together with associated SIR values obtained from the averaged correlation functions, are included in a Measurement Report to the CRNC, according to a measurement reporting plan.
In addition, the Time-of-Arrival measurements may optionally be used for autonomous self-adjustment of the timing of the respective cell.
8.2.21.2.4	[3.84Mcps TDD - Cell Sync Burst Transmission Reconfiguration] [1.28Mcps TDD - SYNC_DL Code Transmission Reconfiguration]
When the [3.84Mcps TDD - Cell Sync Burst Transmission Reconfiguration Information] [1.28Mcps TDD - SYNC_DL Code Transmission Reconfiguration Information LCR] is present, the Node B shall reconfigure the transmission of the [3.84Mcps TDD - cell synchronisation burst] [1.28Mcps TDD - SYNC_DL Code] according to the parameters given in the CELL SYNCHRONISATION RECONFIGURATION REQUEST message.
[3.84Mcps TDD - If the CELL SYNCHRONISATION RECONFIGURATION REQUEST message includes the Cell Sync Burst Code IE, the Node B shall reconfigure the synchronisation code in the cell according to the Cell Sync Burst Code IE value.]
[3.84Mcps TDD - If the CELL SYNCHRONISATION RECONFIGURATION REQUEST message includes the Cell Sync Burst Code Shift IE, the Node B shall reconfigure the synchronisation code shift in the cell according to the Cell Sync Burst Code Shift IE value.]
[3.84Mcps TDD - If the CELL SYNCHRONISATION RECONFIGURATION REQUEST message includes the DL Transmission Power IE, the Node B shall reconfigure the DL transmission power of the cell synchronisation burst in the cell according to the DL Transmission Power IE value.]
[1.28Mcps TDD - If the CELL SYNCHRONISATION RECONFIGURATION REQUEST message includes the DwPCH Power IE, the Node B shall store the DwPCH power according to the DwPCH Power IE value. For the duration of those subsequent transmissions of the DwPCH which are specifically for the purpose of Node B synchronisation the power of the DwPCH shall be set to the stored power. During subsequent transmissions of the DwPCH which are for normal operation the power of the DwPCH shall assume its normal level.]
[1.28Mcps TDD - If the CELL SYNCHRONISATION RECONFIGURATION REQUEST message includes the Sync_DL Code ID IE, the Node B shall reconfigure the SYNC_DL Code in the cell according to the Sync_DL Code ID IE value.]
8.2.21.2.5	[3.84Mcps TDD - Cell Sync Burst Measurement Reconfiguration] [1.28Mcps TDD - SYNC_DL Code Measurement Reconfiguration]
When the [3.84Mcps TDD - Cell Sync Burst Measurement Reconfiguration Information] [1.28Mcps TDD - Cell SYNC_DL Code Measurement Reconfiguration Information LCR] is present, the Node B shall reconfigure the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] measurements according the parameters given in the message.
If the CELL SYNCHRONISATION RECONFIGURATION REQUEST message includes the [3.84Mcps TDD -Cell Sync Burst Measurement Information] [1.28Mcps TDD - SYNC_DL Code Measurement Information LCR], the measurements shall apply on the individual [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC_DL Codes] on the requested Sync Frame number.
[1.28Mcps TDD - When the Propagation Delay Compensation IE is present in the SYNC_DL Code Measurement Information LCR, the Node B shall, if supported, perform the following functions: (1) use the respective SYNC_DL measurement (after potential averaging) to perform the self-adjustment of the respective cell’s timing at the end of a Synchronisation Cycle; (2) include the Accumulated Clock Update IE in the CELL SYNCHRONISATION REPORT message, to report the total accumulated amount of timing adjustments since the last report to the RNC. This Accumulated Clock Update value shall also include the adjustments which may have been performed by explicit order from the CRNC in the CELL SYNCHRONISATION ADJUSTMENT REQUEST message. The times for self-adjustment at the end of a synchronisation cycle shall be independent from the measurement reporting characteristics; the Accumulated Adjustment values shall be included in the CELL SYNCHRONISATION REPORT messages without influencing the frequency of measurement reporting.]
If the Synchronisation Report Type IE is provided, the measurement reporting shall apply according the parameter given in the message.
Synchronisation Report characteristics:
The Synchronisation Report Characteristics IE indicates how the reporting of the cell synchronisation burst measurement shall be performed.
If the Synchronisation Report Characteristics Type IE is set to "Frame related", the Node B shall report the result of the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] measurement after every measured frame.
If the Synchronisation Report Characteristics Type IE is set to "SFN period related", the Node B shall report the result of the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] measurements after every SFN period.
If the Synchronisation Report Characteristics Type IE is set to "Cycle length related", the Node B shall report the result of the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] measurements after every cycle length within the SFN period.
If the Synchronisation Report Characteristics Type IE is set to "Threshold exceeding", the Node B shall report the result of the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] measurement when the [3.84Mcps TDD - Cell Synchronisation Burst timing] [1.28Mcps TDD - SYNC_DL Code timing] rises or falls more than the requested threshold value compared to the arrival time in synchronised state which is represented by the [3.84Mcps TDD - Cell Sync Burst Arrival Time IE] [1.28Mcps TDD - SYNC_DL Code ID Arrival Time IE].
[3.84Mcps TDD - If the Cell Sync Burst Arrival Time IE is included in the Cell Sync Burst Information IE of the Synchronisation Report Characteristics IE, it indicates to the Node B the reference time at which the reception of the cell synchronisation burst of a neighbouring cell is expected.]
[3.84Mcps TDD - If the Cell Sync Burst Timing Threshold IE is included in the Cell Sync Burst Information IE of the Synchronisation Report Characteristics IE, the Node B shall use this new threshold as a trigger for the CELL SYNCHRONISATION REPORT message.]
[1.28Mcps TDD - If the SYNC_DL Code ID Arrival Time IE is included in the SYNC_DL Code Information LCR IE of the Synchronisation Report Characteristics IE, it indicates to the Node B the reference time at which the reception of the SYNC_DL Code of a neighbouring cell is expected.]
[1.28Mcps TDD - If the SYNC_DL Code ID Timing Threshold IE is included in the SYNC_DL Code Information LCR IE of the Synchronisation Report Characteristics IE, the Node B shall use this threshold as a trigger for the CELL SYNCHRONISATION REPORT message.]
Response message:
If the Node B was able to reconfigure the [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] transmission and/or measurement requested by the CRNC, it shall respond with the CELL SYNCHRONISATION RECONFIGURATION RESPONSE message sent over the Node B Control Port.
8.2.21.3	Unsuccessful Operation


Figure 27F Cell Synchronisation Reconfiguration procedure, Unsuccessful Operation
If the Node B cannot reconfigure the requested transmission or measurement on [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code], the CELL SYNCHRONISATION RECONFIGURATION FAILURE message shall be sent to the CRNC. The message shall include the Cause IE set to an appropriate value.
Typical cause values are as follows:
Radio Network Layer Cause:
-	Cell Synchronisation not supported
-	Power level not supported
-	Measurement Temporarily not Available
Miscellaneous Cause:
-	O&M Intervention
-	HW failure
8.2.21.4	Abnormal Conditions
-
8.2.22	Cell Synchronisation Reporting [TDD]
8.2.22.1	General
This procedure is used by a Node B to report the result of [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] measurements requested by the CRNC with the Cell Synchronisation Initiation or Cell Synchronisation Reconfiguration procedure.
8.2.22.2	Successful Operation


Figure 27G Cell Synchronisation Reporting procedure, Successful Operation
If the requested synchronisation measurement reporting criteria are met, the Node B shall initiate a Cell Synchronisation Reporting procedure. The CELL SYNCHRONISATION REPORT message shall use the Node B Control Port.
In the steady state phase when several [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC_DL Codes] shall be measured per Sync Frame number, the sequence of the reported measured values shall be the same as defined in the Cell Synchronisation Reconfiguration procedure.
[1.28Mcps TDD - The Node B shall, if supported, include the Accumulated Clock Update IE in the CELL SYNCHRONISATION REPORT message whenever the CRNC has included at least one instance of the Propagation Delay Compensation IE in the CELL SYNCHRONISATION RECONFIGURATION REQUEST message. The Accumulated Clock Update IE shall include the accumulated timing adjustment which has been done as commanded by the CRNC, as well as by self-adjustment, since the last Accumulated Clock Update IE report.]
If the achieved measurement accuracy does not fulfil the given accuracy requirement defined in TS 25.123 [23], the Cell Sync Burst not available shall be reported.
8.2.22.3	Abnormal Conditions
-
8.2.23	Cell Synchronisation Termination [TDD]
8.2.23.1	General
This procedure is used by the CRNC to terminate a [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] transmission or measurement previously requested by the Cell Synchronisation Initiation procedure or Cell Synchronisation Reconfiguration procedure.
8.2.23.2	Successful Operation


Figure 27H Cell Synchronisation Termination procedure, Successful Operation
This procedure is initiated with a CELL SYNCHRONISATION TERMINATION REQUEST message, sent from the CRNC to the Node B using the Node B Control Port.
Upon reception, the Node B shall terminate [3.84Mcps TDD - transmission of Cell Synchronisation Bursts or reporting of Cell Synchronisation Burst measurements] [1.28Mcps TDD - transmission of SYNC_DL Codes or reporting of SYNC_DL Code measurements] corresponding to the CSB Transmission ID IE or CSB Measurement ID IE.
8.2.23.3	Abnormal Conditions
-
8.2.24	Cell Synchronisation Failure [TDD]
8.2.24.1	General
This procedure is used by the Node B to notify the CRNC that a [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] transmission or synchronisation measurement procedure can no longer be supported.
8.2.24.2	Successful Operation


Figure 27I Cell Synchronisation Failure procedure, Successful Operation
This procedure is initiated with a CELL SYNCHRONISATION FAILURE INDICATION message, sent from the Node B to the CRNC using the Node B Control Port, to inform the CRNC that a previously requested transmission or measurement on [3.84Mcps TDD - Cell Synchronisation Bursts] [1.28Mcps TDD - SYNC_DL Codes] can no longer be supported.
If the transmission of a [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] has failed, then the Node B shall include the CSB Transmission ID IE in the CELL SYNCHRONISATION FAILURE INDICATION message to uniquely identify the concerned [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] Transmission.
If the measurement of a [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] has failed, then the Node B shall include the CSB Measurement ID IE in the CELL SYNCHRONISATION FAILURE INDICATION message to uniquely identify the concerned [3.84Mcps TDD - Cell Synchronisation Burst] [1.28Mcps TDD - SYNC_DL Code] Measurement.
8.2.24.3	Abnormal Conditions
-
8.2.25	Cell Synchronisation Adjustment [TDD]
8.2.25.1	General
The purpose of Cell Synchronisation Adjustment procedure is to allow the CRNC to adjust the timing of the radio transmission of a cell within a Node B for time alignment.
8.2.25.2	Successful Operation


Figure 27J Cell Synchronisation Adjustment, Successful Operation
This procedure is initiated with a CELL SYNCHRONISATION ADJUSTMENT REQUEST message sent by the CRNC to the Node B using the Node B Control Port.
Upon reception, the Node B adjusts its timing according to the parameters given in the message. 
If the CELL SYNCHRONISATION ADJUSTMENT REQUEST message includes the Frame Adjustment Value IE the Node B shall apply the frame adjustment in the cell according to the Frame Adjustment Value IE value.
[3.84Mcps TDD - If the CELL SYNCHRONISATION ADJUSTMENT REQUEST message includes the Timing Adjustment Value IE the Node B shall apply the timing adjustment in the cell according to the Timing Adjustment Value IE value.]
[1.28Mcps TDD - If the CELL SYNCHRONISATION ADJUSTMENT REQUEST message includes the Timing Adjustment Value LCR IE the Node B shall apply the timing adjustment in the cell according to the Timing Adjustment Value LCR IE value.]
[3.84Mcps TDD - If the CELL SYNCHRONISATION ADJUSTMENT REQUEST message includes the DL Transmission Power IE, the Node B shall apply the transmission power of the Cell Synchronisation Burst according to the DL Transmission Power IE value.]
[1.28Mcps TDD - If the CELL SYNCHRONISATION ADJUSTMENT REQUEST message includes the DwPCH Power IE, the Node B shall store the DwPCH power according to the DwPCH Power IE value. For the duration of those subsequent transmissions of the DwPCH which are specifically for the purpose of Node B synchronisation the power of the DwPCH shall be set to the stored power. During subsequent transmissions of the DwPCH which are for normal operation the power of the DwPCH shall assume its normal level.]
If the CELL SYNCHRONISATION ADJUSTMENT REQUEST message includes the SFN IE, the Node B shall apply the synchronisation adjustment starting with the SFN number indicated in the message.
When the cell synchronisation adjustment is successfully done by the Node B, the Node B shall respond with a CELL SYNCHRONISATION ADJUSTMENT RESPONSE message.
8.2.25.3	Unsuccessful Operation

Figure 27K Cell Synchronisation Adjustment, Unsuccessful Operation
If the Node B cannot perform the indicated cell synchronisation adjustment due to hardware failure or other problem it shall send the CELL SYNCHRONISATION ADJUSTMENT FAILURE as a response.
Typical cause values are as follows:
Radio Network Layer Cause
-	Cell Synchronisation Adjustment not supported
-	Power level not supported
Miscellaneous Cause
-	O&M Intervention
-	HW failure
8.2.25.4	Abnormal Conditions
-
8.2.26	Information Exchange Initiation
8.2.26.1	General
This procedure is used by a CRNC to request the initiation of information provisioning from a Node B.
8.2.26.2	Successful Operation

Figure 27L: Information Exchange Initiation procedure, Successful Operation
The procedure is initiated with the INFORMATION EXCHANGE INITIATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
Upon reception, the Node B shall provide the requested information according to the Information Type Item IE. Unless specified below, the meaning of the parameters are given in other specifications.
If the Information Type IE contains a GANSS Generic Data IE, at least one of the GANSS Navigation Model And Time Recovery, GANSS Time Model GNSS-GNSS, GANSS UTC Model, GANSS Almanac, GANSS Real Time Integrity, GANSS Data Bit Assistance, GANSS Additional Navigation Models And Time Recovery, GANSS Additional UTC Models, GANSS Auxiliary Information, DBDS Corrections Request, BDS Ionospheric Grid Model Request IEs shall be present in the GANSS Generic Data IE.
-	If the GANSS Generic Data IE does not contain the GANSS ID IE, the Node B shall assume that the corresponding GANSS is "Galileo".
Information Report Characteristics
The Information Report Characteristics IE indicates how the reporting of the information shall be performed.
If the Information Report Characteristics IE is set to "On Demand", the Node B shall report the requested information immediately.
If the Information Report Characteristics IE is set to "Periodic", the Node B shall immediately report the requested information and then shall periodically initiate the Information Reporting procedure for all the requested information, with the requested reporting frequency.
If the Information Report Characteristics IE is set to "On Modification", the Node B shall immediately report the requested information if available. If the requested information is not available at the moment of receiving the INFORMATION EXCHANGE INITIATION REQUEST message, but expected to become available after some acquisition time, the Node B shall initiate the Information Reporting procedure when the requested information becomes available. The Node B shall then initiate the Information Reporting procedure in accordance to the following conditions related to the Information Type IE:
1)	If the Information Type Item IE is set to "DGPS Corrections", the Node B shall initiate the Information Reporting procedure when either the PRC has drifted from the previously reported value more than the threshold indicated in the PRC Deviation IE in the Information Threshold IE or a change has occurred in the IODE. 
2)	If the Information Type Item IE is set to "GPS Information" and the GPS Information Item IE includes "GPS Navigation Model & Time Recovery", the Node B shall initiate the Information Reporting procedure for this specific GPS Information Item when a change has occurred regarding either the IODC or the list of visible satellites, identified by the Sat ID IEs.
3)	If the Information Type Item IE is set to "GPS Information" and the GPS Information Item IE includes "GPS Ionospheric Model", the Node B shall initiate the Information Reporting procedure for this specific GPS Information Item when any change has occurred.
4)	If the Information Type Item IE is set to "GPS Information" and the GPS Information Item IE includes "GPS UTC Model", the Node B shall initiate the Information Reporting procedure for this specific GPS Information Item when a change has occurred in the tot or WNt parameter.
5)	If the Information Type Item IE is set to "GPS Information" and the GPS Information Item IE includes "GPS Almanac", the Node B shall initiate the Information Reporting procedure for this specific GPS Information Item when a change in the toa or WNa parameter has occurred.
6)	If the Information Type Item IE is set to "GPS Information" and the GPS Information Item IE includes "GPS Real-Time Integrity", the Node B shall initiate the Information Reporting procedure for this specific GPS Information Item when any change has occurred.
7)	If the Information Type Item IE is set to "DGANSS Corrections", the Node B shall initiate the Information Reporting procedure when either the PRC has drifted from the previously reported value more than the threshold indicated in the PRC Deviation IE in the Information Threshold IE or a change has occurred in the IOD.
8)	If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS Navigation Model And Time Recovery IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred regarding either the IOD or the list of visible satellites, identified by the Sat ID IEs.
9)	If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS Ionospheric Model IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred.
10)	If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS Time Model IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred.
11)	If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS UTC Model IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the tot or WNt parameter.
12)	If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS Almanac IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change in the Toa, IODa  or Week Number parameter has occurred.
13)	If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS Real Time Integrity IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred
14)	If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS Data Bit Assistance IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred.
15)If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS Additional Navigation Models And Time Recovery IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred regarding either the IOD or the list of visible satellites, identified by the Sat ID IEs.
16)	If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS Additional Ionospheric Model IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred.
17) If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS Additional UTC Models IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the tot,WNot, WNt, or NA parameter.
18)	If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS Earth Orientation Parameters IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the tEOP parameter.
19)	If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS Auxiliary Information IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the Signals Available or Channel Number IE parameter.
20)	If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the DBDS Corrections Request IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred.
21)	If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the BDS Ionospheric Grid Model Request IE, the Node B shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred.
22)	If any of the above Information Type IEs becomes temporarily unavailable, the Node B shall initiate the Information Reporting procedure for this specific Information Item by indicating "Information Not Available" in the Requested Data Value Information IE. If the Information becomes available again, the Node B shall initiate the Information Reporting procedure for this specific Information.
Response message
If the Node B is able to initiate the information provision requested by the CRNC, it shall respond with the INFORMATION EXCHANGE INITIATION RESPONSE message sent over the Node B Control Port. The message shall include the same Information Exchange ID that was included in the INFORMATION EXCHANGE INITIATION REQUEST message. When the Report Characteristics IE is set to "On Modification" or "Periodic", the INFORMATION EXCHANGE INITIATION RESPONSE message shall contain the requested data if the data are available. When the Report Characteristics IE is set to "On Demand", the INFORMATION EXCHANGE INITIATION RESPONSE message shall contain the Requested Data Value IE.
If the Requested Data Value IE contains the GANSS Common Data IE, at least one of the GANSS Ionospheric Model , GANSS RX Pos, GANSS Additional Ionospheric Model, or GANSS Earth Orientation Parameters IEs shall be present.
Any GANSS Generic Data IE associated with a given GANSS included in the Requested Data Value IE shall contain at least one of the DGANSS Corrections, GANSS Navigation Model And Time Recovery, GANSS Time Model, GANSS UTC Model, GANSS Almanac, GANSS Real Time Integrity, GANSS Data Bit Assistance, GANSS Additional Time Models, GANSS Additional Navigation Models And Time Recovery, GANSS Additional UTC Models, GANSS Auxiliary Information, DBDS Corrections, or BDS Ionospheric Grid Model IEs.
-	If the GANSS Generic Data IE does not contain the GANSS ID IE, the corresponding GANSS is "Galileo".
-	The DGANSS Corrections IE contains one or several DGANSS Information IE(s), each of them associated with a GANSS Signal. A DGANSS Information IE for a particular GANSS that does not contain the GANSS Signal ID IE is by default associated with the default signal defined in TS 25.331 [18], clause 10.3.3.45a.
-	The DBDS Corrections IE contains one or several DBDS information IE(s), each of them associated with a GANSS Signal. A DBDS information IE for a particular GANSS that does not contain the GANSS Signal ID IE is by default associated with the default signal defined in TS 25.331 [18], clause 10.3.3.45a.
- 	The GANSS Real Time Integrity IE contains one or several Satellite Information IEs, each of them associated with a satellite and a GANSS Signal. A Satellite Information IE for a particular GANSS that does not contain the Bad GANSS Signal ID IE is by default associated with all the signals of the corresponding satellite (see [39, 43, 44, 45, 46, 47 48]).
If the Information Type Item IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS Time Model GNSS-GNSS IE with exactly one bit set to value "1", the Node B shall include the GANSS Time Model IE in the Requested Data Value IE with the requested time information.
If the Information Type Item  IE is set to "GANSS Information" and the GANSS Information IE includes the GANSS Time Model GNSS-GNSS  IE with more than one bit set to value "1, the Node B shall include the GANSS Additional Time Models IE in Requested Data Value IE with the requested time information for each GANSS. 
If the Information Type Item IE is set to "DGPS Corrections", the Node B shall include the DGPS Corrections IE in Requested Data Value IE with the DGNSS Validity Period IE included, if available.
If the Information Type Item IE is set to "DGANSS Corrections", the Node B shall include the DGANSS Corrections IE in Requested Data Value IE with the DGNSS Validity Period IE included, if available.
If the Information Type Item IE is set to "GPS Almanac", the Node B shall include the GPS Almanac IE in Requested Data Value IE with the Complete Almanac Provided IE included, if available.
If the Information Type Item IE is set to "GANSS Almanac", the Node B shall include the GANSS Almanac IE in Requested Data Value IE with the Complete Almanac Provided IE included, if available.
If the Information Type Item IE is set to "GANSS Time Model GNSS-GNSS", the Node B shall include the GANSS Time Model IE in Requested Data Value IE with the Delta_T IE included, if available.
8.2.26.3	Unsuccessful Operation

Figure 27M: Information Exchange Initiation procedure, Unsuccessful Operation
If the Information Type Item received in the Information Type Item IE indicates a type of information that cannot be provided, the Node B shall regard the Information Exchange Initiation procedure as failed.
If the requested information provision cannot be initiated, the Node B shall send the INFORMATION EXCHANGE INITIATION FAILURE message over the Node B control port. The message shall include the same Information Exchange ID that was used in the INFORMATION EXCHANGE INITIATION REQUEST message and the Cause IE set to an appropriate value.
Typical cause values are as follows:
Radio Network Layer Cause
-	Information temporarily not available.
-	Information Provision not supported for the object.
8.2.26.4	Abnormal Conditions
If the Information Report Characteristics IE is set to "On Modification", and the Information Type Item IE is set to "DGPS Corrections", or "DGANSS Corrections", but the Information Threshold IE is not received in the INFORMATION EXCHANGE INITIATION REQUEST message, the Node B shall regard the Information Exchange Initiation procedure as failed.
If the Information Type Item IE is not set to "DGPS Correction" or "DGANSS Corrections", the Information Report Characteristics IE is set to "On Modification" and the Information Threshold IE is included in the INFORMATION EXCHANGE INITIATION REQUEST message, the Node B shall regard the Information Exchange Initiation procedure as failed.
8.2.27	Information Reporting
8.2.27.1	General
This procedure is used by a Node B to report the information requested by the CRNC with the Information Exchange Initiation procedure.
8.2.27.2	Successful Operation

Figure 27N: Information Reporting procedure, Successful Operation
If the requested information reporting criteria are met, the Node B shall initiate the Information Reporting procedure. The INFORMATION REPORT message shall use the Node B Control Port. Unless specified below, the meaning of the parameters are given in other specifications.
The Information Exchange ID IE shall be set to the Information Exchange ID provided by the CRNC when initiating the Information Exchange with the Information Exchange Initiation procedure.
The Requested Data Value IE shall include at least one IE containing the data to be reported.
8.2.27.3	Abnormal Conditions
-
8.2.28	Information Exchange Termination
8.2.28.1	General
This procedure is used by the CRNC to terminate the provision of information previously requested by the Information Exchange Initiation procedure.
8.2.28.2	Successful Operation

Figure 27O: Information Exchange Termination procedure, Successful Operation
This procedure is initiated with an INFORMATION EXCHANGE TERMINATION REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
Upon reception, the Node B shall terminate the provision of information corresponding to the Information Exchange ID.
8.2.28.3	Abnormal Conditions
-
8.2.29	Information Exchange Failure
8.2.29.1	General
This procedure is used by the Node B to notify the CRNC that information previously requested by the Information Exchange Initiation procedure can no longer be reported.
8.2.29.2	Successful Operation

Figure 27P: Information Exchange Failure procedure, Successful Operation
This procedure is initiated with the INFORMATION EXCHANGE FAILURE INDICATION message sent from the Node B to the CRNC using the Node B Control Port to inform the CRNC that information previously requested by the Information Exchange Initiation procedure can no longer be reported. The message shall include the same Information Exchange ID that was used in the INFORMATION EXCHANGE INITIATION REQUEST message and the Cause IE set to an appropriate value.
8.2.30	MBMS Notification Update
8.2.30.1	General
This procedure is used to update the MBMS Notification Indicators to be sent over the MICH.
8.2.30.2	Successful Operation

Figure 27Q: MBMS Notification Update procedure, Successful Operation
The procedure is initiated with an MBMS NOTIFICATION UPDATE COMMAND message sent from the CRNC to the Node B using the Node B Control Port.
The Node B shall use the different NIs in the NI Information IE to generate, as specified in ref. TS 25.211 [7], the notification indicators it shall transmit on the MICH starting at the next coming MICH CFN equal to the value in the MICH CFN IE and for a duration equal to the Modification Period. If the value of MICH CFN IE is the same as the one in a previously received MBMS NOTIFICATION UPDATE COMMAND message, and if the MICH CFN occurrence has not been reached yet, the Node B shall overwrite the value of the NI Information IE in the previously received MBMS NOTIFICATION UPDATE COMMAND message.
If the Modification Period IE is included in the MBMS NOTIFICATION UPDATE COMMAND message, the Node B shall use this as the new Modification Period starting at the next coming MICH CFN equal to the value in the MICH CFN IE. If the value of MICH CFN IE is the same as the one in a previously received MBMS NOTIFICATION UPDATE COMMAND message, and if the MICH CFN occurrence has not been reached yet, the Node B shall overwrite the value of the Modification Period IE in the previously received MBMS NOTIFICATION UPDATE COMMAND message.
If the Modification Period IE is not included in the MBMS NOTIFICATION UPDATE COMMAND message, the Node B shall use the lastest stored Modification Period.
8.2.30.3	Abnormal Conditions
If the Modification Period IE is not included in the MBMS NOTIFICATION UPDATE COMMAND message and no Modification Period is stored in the Node B, the Node B shall initiate the Error Indication procedure.
8.2.31	UE Status Update [FDD and 1.28Mcps TDD]
8.2.31.1	General
This procedure is used by the CRNC to inform Node B that one or several E-RNTIs, previously allocated to UEs in CELL_FACH or URA_PCH state, may be released as the UE no longer use the E-RNTI.
8.2.31.2	Successful Operation


Figure 27R: UE Status Update procedure, Successful Operation
The procedure is initiated with a UE STATUS UPDATE COMMAND message sent from the CRNC to the Node B using the Node B Control Port.
Upon reception of the UE STATUS UPDATE COMMAND message, the Node B may use the information about vacant E-RNTI in Vacant E-RNTI IE in Cell E-RNTI status information IE to determine which E-RNTIs are no longer used in the cell and thus allowed to be allocated to another UE using E-DCH
8.2.31.3	Abnormal Conditions
-
8.2.32	UE Status Update Confirmation [FDD and 1.28Mcps TDD]
8.2.32.1	General
This procedure is used by the CRNC to inform the Node B that one or several E-RNTIs, previously allocated to UEs in CELL_FACH or URA_PCH state, may be released as the UE no longer uses the E-RNTI. The Node B then responds with the status of the releasing procedure.
8.2.32.2	Successful Operation


Figure 27S: UE Status Update Confirmation procedure, Successful Operation
The procedure is initiated with a UE STATUS UPDATE CONFIRM REQUEST message sent from the CRNC to the Node B using the Node B Control Port.
Upon reception of the UE STATUS UPDATE CONFIRM REQUEST message, the Node B may use the information about vacant E-RNTI in Vacant E-RNTI IE in Cell E-RNTI Status Information IE to determine which E-RNTIs are no longer used in the cell and thus allowed to be allocated to another UE using E-DCH. The Node B shall, if supported, sends UE STATUS UPDATE CONFIRM RESPONSE to indicate that the releasing procedure is performed properly in the Node B.
8.2.32.3	Abnormal Conditions
-
8.3	NBAP Dedicated Procedures
8.3.1	Radio Link Addition
8.3.1.1	General
This procedure is used for establishing the necessary resources in the Node B for one or more additional RLs towards a UE when there is already a Node B Communication Context for this UE in the Node B.
The Radio Link Addition procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
8.3.1.2	Successful Operation

Figure: 28 Radio Link Addition procedure, Successful Operation
The procedure is initiated with a RADIO LINK ADDITION REQUEST message sent from the CRNC to the Node B using the Communication Control Port assigned to the concerned Node B Communication Context.
Upon reception, the Node B shall reserve the necessary resources and configure the new RL(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications.
The Node B shall prioritise resource allocation for the RL(s) to be established according to Annex A.
If the UE Aggregate Maximum Bit Rate IE is contained in the RADIO LINK ADDITION REQUEST message, the Node B shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE.
Physical Channels Handling:
[TDD - If the [3.84Mcps TDD - UL DPCH Information IE] [1.28Mcps TDD - UL DPCH Information LCR IE] [7.68Mcps TDD - UL DPCH Information 7.68Mcps IE] is present, the Node B shall configure the new UL DPCH(s) according to the parameters given in the message.]
[TDD - If the [3.84Mcps TDD - DL DPCH Information IE] [1.28Mcps TDD - DL DPCH Information LCR IE] [7.68Mcps TDD - DL DPCH Information 7.68Mcps IE] is present, the Node B shall configure the new DL DPCH(s) according to the parameters given in the message.]
[1.28Mcps TDD - If the UL Timeslot Information LCR IE includes the PLCCH Information IE, the Node B shall transmit TPC /SS bits on a PLCCH according to the parameters given in the message.]
[FDD - Compressed Mode]:
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Compressed Mode Deactivation Flag IE with value ''Deactivate'', the Node B shall not activate any compressed mode pattern in the new RLs. In all the other cases (Flag set to ''Maintain Active'' or not present), the ongoing compressed mode (if existing) shall be applied also to the added RLs.]
[FDD - If the Node B Communication Context is configured to use DPCH in the downlink and if the RADIO LINK ADDITION REQUEST message contains the Transmission Gap Pattern Sequence Code Information IE for any of the allocated DL Channelisation Codes, the Node B shall apply the alternate scrambling code as indicated for each DL Channelisation Code for which the Transmission Gap Pattern Sequence Code Information IE is set to "Code Change".]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Active Pattern Sequence Information IE, the Node B shall use the information to activate the indicated Transmission Gap Pattern Sequence(s) in the new RL. The received CM Configuration Change CFN refers to the latest passed CFN with that value The Node B shall treat the received TGCFN IEs as follows:]
-	[FDD - If any received TGCFN IE has the same value as the received CM Configuration Change CFN IE, the Node B shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.]
-	[FDD - If any received TGCFN IE does not have the same value as the received CM Configuration Change CFN IE but the first CFN after the CM Configuration Change CFN with a value equal to the TGCFN IE has already passed, the Node B shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.]
-	[FDD - For all other Transmission Gap Pattern Sequences included in the Active Pattern Sequence Information IE, the Node B shall activate each Transmission Gap Pattern Sequence at the first CFN after the CM Configuration Change CFN with a value equal to the TGCFN IE for the Transmission Gap Pattern Sequence.]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with C-ID IE included in Affected HS-DSCH serving cell List IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.]
[FDD - DL Code Information]:
[FDD - When more than one DL DPDCH are assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to ref. TS 25.212 [8]. When p number of DL DPDCHs are assigned to each RL, the first pair of DL Scrambling Code and FDD DL Channelisation Code Number corresponds to "PhCH number 1", the second to "PhCH number 2", and so on until the pth to "PhCH number p".]
[TDD - CCTrCH Handling]:
[TDD - If the UL CCTrCH Information IE is present, the Node B shall configure the new UL CCTrCH(s) according to the parameters given in the message.]
[1.28Mcps TDD - If the UL CCTrCH Information IE includes the TDD TPC UL Step Size IE, the Node B shall configure the uplink TPC step size according to the parameters given in the message, otherwise it shall use the step size configured in other radio link.]
[TDD - If the DL CCTrCH Information IE is present, the Node B shall configure the new DL CCTrCH(s) according to the parameters given in the message.]
[TDD - If the DL CCTrCH Information IE includes the TDD TPC DL Step Size IE, the Node B shall configure the downlink TPC step size according to the parameters given in the message, otherwise it shall use the step size configured in other radio link.]
[1.28 Mcps TDD - The Node B shall configure the HS-SCCH TPC step size to the same value as the TDD TPC DL Step Size IE of the lowest numbered DL CCTrCH whose DL CCTrCH Information IE includes the TDD TPC DL Step Size IE. If no DL CCTrCH Information IE includes the TDD TPC DL Step Size IE, it shall use the step size configured in other radio link.]
[1.28 Mcps TDD - If the TDD TPC DL Step Size IE is not included in the DL CCTrCH Information IE, the Node B shall use the E-AGCH TPC step size IE in the E-PUCH Information LCR IE in the E-DCH Information 1.28Mcps IE for HS-SCCH inner loop power control related operation.]
[FDD - UL CLTD Handling]:
[FDD - If the UL CLTD Information IE is present in the RADIO LINK ADDITION REQUEST message, then the Node B shall setup the requested UL CLTD resources for the concerned Node B Communication Context in the cell to determine the precoding weights and then :]
-	[FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the concerned Node B Communication Context, the C-ID IE shall be included in the UL CLTD Information IE, and the Node B shall configure this cell to determine the precoding weights for the concerned Node B Communication Context.]
-	[FDD - If the UL CLTD Activation Information IE is included in the UL CLTD Information IE, then the Node B shall use this value to configure the state of UL CLTD for the concerned Node B Communication Context.]
[FDD - UL MIMO Setup]:
[FDD - If the UL MIMO Information IE is present in the RADIO LINK ADDITION REQUEST message, then the Node B shall activate UL MIMO operation for the radio link according to the information provided in the IE.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the Serving E-DCH RL IE indicating that the Serving E-DCH RL is in this Node B]
-	[FDD - The Node B shall allocate a Secondary Transport Block E-RNTI for the corresponding RL and include the E-RNTI identifier together with the corresponding E-ROCH Channelization Code in the UL MIMO DL Control Channel Information IE in the RADIO LINK ADDITION RESPONSE message. The E-ROCH Channelization code shall be allocated from the pool of E-AGCH channelization codes configured for that cell.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the E-ROCH Power Offset IE in the UL MIMO Information IE, then the Node B may use this value to determine the E-ROCH power. The E-ROCH Power Offset should be applied for any E-ROCH transmission to this UE.]
-	[FDD - The Node B may include the the Secondary Transport Block E-HICH Signature Sequence IE in UL MIMO DL Control Channel Information IE in the RADIO LINK ADDITION RESPONSE message for every RL indicated by the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE and it should include it for the Serving E-DCH RL.]
Radio Link Handling:
Diversity Combination Control:
The Diversity Control Field IE indicates for each RL whether the Node B shall combine the new RL with existing RL(s) or not.
-	If the Diversity Control Field IE is set to "May", the Node B shall decide for any of the alternatives.
-	If the Diversity Control Field IE is set to "Must", the Node B shall combine the RL with one of the other -	RL.
-	If the Diversity Control Field IE is set to "Must not", the Node B shall not combine the RL with any other existing RL.
[FDD - The signalled Diversity Control Field IE is only applicable for DCHs. In case of E-DCH, if any UARFCN(s) of the cells in the added RL(s) is not equal to at least one of the UARFCN(s) of the cells in the existing RL(s) in the Node B Communication Context, the Diversity Control Field, for those RL(s) shall be assumed to be set to "May", otherwise it shall be assumed to be set to "Must".]
When a new RL is to be combined, the Node B shall choose which RL(s) to combine it with.
In the case of not combining a RL with a RL established with a previous Radio Link Setup or Radio Link Addition Procedure or a RL previously listed in the RADIO LINK ADDITION RESPONSE message, the Node B shall indicate with the Diversity Indication in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message that no combining is done. In this case, the Node B shall:
-	include in the DCH Information Response IE both the Transport Layer Address IE and the Binding ID IE for the transport bearer to be established for each DCH of the RL in the RADIO LINK ADDITION RESPONSE message. [FDD - for which the Transport Bearer Not Requested Indicator IE was not included].
-	[FDD - include in the RADIO LINK ADDITION RESPONSE message the Transport Bearer Not Setup Indicator IE for every DCH for which establishment of a transport bearer has not taken place as a result of information in the Transport Bearer Not Requested Indicator IE in the RADIO LINK ADDITION REQUEST message.]
-	[FDD - For E-DCH, include in the E-DCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE for the transport bearers to be established for each E-DCH MAC-d flow of this RL for which the Transport Bearer Not Requested Indicator IE was not included.]
In the case of combining with a RL established with a previous Radio Link Setup or Radio Link Addition Procedure or with a RL previously listed in this RADIO LINK ADDITION RESPONSE message, the Node B shall indicate with the Diversity Indication in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message that the RL is combined and if the ALCAP is not used [FDD - and the transport bearer for this DCH is already established], the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE included in the RL Information IE for a specific RL in the RADIO LINK ADDITION REQUEST message, shall not be used. In this case, the RL ID IE indicates (one of) the previously established RL(s) or a RL previously listed in this RADIO LINK ADDITION RESPONSE message with which the new RL is combined.
[FDD - In the case of combining with an E-DCH RL established with a previous Radio Link Setup or Radio Link Addition Procedure or with a RL previously listed in this RADIO LINK ADDITION RESPONSE message, one of the previously established RLs or a RL previously listed in this RADIO LINK ADDITION RESPONSE message including the E-DCH FDD Information Response IE shall be regarded as the RL with which the concerned E-DCH RL is combined. In case E-DCH RL is established for  the first time, the Node B shall include  E-DCH FDD Information Response IE instead of using the Diversity Indication of DCH RL in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message. It shall include in the E-DCH FDD Information Response IE the Binding ID IE and Transport Layer Address IE for the transport bearers to be established for each E-DCH MAC-d flow of this E-DCH RL for which the Transport Bearer Not Requested Indicator IE was not included.]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Additional E-DCH Cell Information RL Add Req IE, then:]
-	[FDD - if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to "Separate Iub Transport Bearer Mode" the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
-	[FDD - if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to "UL Flow Multiplexing Mode" the Node B shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.]
-	[FDD - if Separate Iub Transport Bearer Mode is used in the new configuration, then:]
-	[FDD - the Node B shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow and use the Transport Bearer Not Requested Indicator IE in the E-DCH MAC-d Flow Specific Information IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE to determine the transport bearer configuration in the new configuration for the MAC-d flow of the Secondary Uplink Frequency.]
-	[FDD - If the Transport Layer Address IE and Binding ID IE is included for an E-DCH MAC-d flow in the Additional E-DCH MAC-d Flows Specific Information IE in the Additional E-DCH FDD Information IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow the Node B shall include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE in the Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
In the case of a set of co-ordinated DCHs, the Binding ID IE and the Transport Layer Address IE shall be included for only one of the DCHs in a set of coordinated DCHs [FDD - for which the Transport Bearer Not Requested Indicator IE was not included].
[TDD - The Node B shall include in the RADIO LINK ADDITION RESPONSE message both the Transport Layer Address IE and the Binding ID IE for the transport bearer to be established for each DSCH and USCH.]
[FDD - Transmit Diversity]:
[FDD - If the Transmit Diversity Indicator IE and/or Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE is included in the RADIO LINK ADDITION REQUEST message, the Node B shall activate/deactivate the Transmit Diversity for each new Radio Link and/or secondary serving HS-DSCH Radio Link in accordance with the Transmit Diversity Indicator IE and/or Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE and the already known diversity mode for the physical channel.]
DL Power Control:
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Initial DL Transmission Power IE, the Node B shall apply the given power to the transmission on each DL DPCH or on the F-DPCH of the RL when starting transmission until either UL synchronisation on the Uu interface is achieved for the RLS or Power Balancing is activated. If no Initial DL Transmission Power IE is included, the Node B shall use any transmission power level currently used on already existing RLs for this Node B Communication Context. No inner loop power control or balancing shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.214 [10], subclause 5.2.1.2) with DPC MODE currently configured for the relevant Node B Communication Context and the downlink power control procedure (see subclause 8.3.7).]
[3.84 Mcps TDD and 7.68Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Initial DL Transmission Power IE, the Node B shall determine the initial CCTrCH DL power for each DCH type CCTrCH by the following rule: If the CCTrCH Initial DL Transmission Power IE is included for that CCTrCH, then the Node B shall use that power for the initial CCTrCH DL power, otherwise the initial CCTrCH DL power is the Initial DL Transmission Power IE included in the RL Information IE. The Node B shall apply the given power to the transmission on each DL DPCH and on each Time Slot of the CCTrCH when starting transmission until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no Initial DL Transmission Power IE is included (even if CCTrCH Initial DL Transmission Power IEs are included), the Node B shall use any transmission power level currently used on already existing CCTrCHs for this Node B Communication Context. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 4.2.3.4).]
[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Initial DL Transmission Power IE, the Node B shall determine the initial DL power for each timeslot within a DCH type CCTrCH by the following rule: If the Initial DL Transmission Power IE is included in the DL Timeslot Information LCR IE, then the Node B shall use that power for the initial DL power and ignore the DL Time Slot ISCP info LCR, otherwise the initial DL power is the Initial DL Transmission Power IE included in the RL Information IE and if DL Time Slot ISCP info LCR IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged. The Node B shall apply the given power to the transmission on each DL DPCH and on each Time Slot of the CCTrCH when starting transmission until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no Initial DL Transmission Power IE is included, the Node B shall use any transmission power level currently used on already existing RL/timeslots for this Node B Communication Context. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4).]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Maximum DL Power IE, the Node B shall store this value and not transmit with a higher power on any DL DPCH or on the F-DPCH of the RL. If no Maximum DL Power IE is included, any Maximum DL power stored for already existing RLs for this Node B Communication Contextshall be applied. If the Node B Communication Context is configured to use DPCH in the downlink, during compressed mode, the  Pcurr, as described in ref. TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Minimum DL Power IE, the Node B shall store this value and never transmit with a lower power on any DL DPCH or on the F-DPCH of the RL. If no Minimum DL Power IE is included, any Minimum DL power stored for already existing RLs for this Node B Communication Context shall be applied.]
[3.84 Mcps TDD and 7.68Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Maximum DL Power IE, the Node B shall determine the maximum CCTrCH DL power for each DCH type CCTrCH by the following rule: If the CCTrCH Maximum DL Transmission Power IE is included for that CCTrCH, then the Node B shall use that power for the maximum CCTrCH DL power, otherwise the maximum CCTrCH DL power is the Maximum DL Power IE included in the RL Information IE. If no Maximum DL Power IE is included (even if CCTrCH Maximum DL Transmission Power IEs are included), any maximum DL power stored for already existing DCH type CCTrCHs for this Node B Communication Context shall be applied.]
[3.84 Mcps TDD and 7.68Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Minimum DL Power IE, the Node B shall determine the minimum CCTrCH DL power for each DCH type CCTrCH by the following rule: If the CCTrCH Minimum DL Transmission Power IE is included for that CCTrCH, then the Node B shall use that power for the minimum CCTrCH DL power, otherwise the minimum CCTrCH DL power is the Minimum DL Power IE included in the RL Information IE. If no Minimum DL Power IE is included (even if CCTrCH Minimum DL Transmission Power IEs are included), any minimum DL power stored for already existing DCH type CCTrCHs for this Node B Communication Context shall be applied.]
[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Maximum DL Power IE, the Node B shall determine the maximum DL power for each timeslot within a DCH type CCTrCH by the following rule: If the Maximum DL Power IE is included in the DL Timeslot Information LCR IE for that timeslot, then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the Maximum DL Power IE included in the RL Information IE. The Node B shall store this value and not transmit with a higher power on any applicable DL DPCH. If no Maximum DL Power IE is included, any maximum DL power stored for already existing RL/timeslots for this Node B Communication Context shall be applied.]
[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Minimum DL Power IE, the Node B shall determine the minimum DL power for each timeslot within a DCH type CCTrCH by the following rule: If the Minimum DL Power IE is included in the DL Timeslot Information LCR IE for that timeslot, then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the Minimum DL Power IE included in the RL Information IE. The Node B shall store this value and not transmit with a lower power on any applicable DL DPCH. If no Minimum DL Power IE is included, any minimum DL power stored for already existing RL/timeslots for this Node B Communication Context shall be applied.]
[3.84Mcps TDD and 7.68Mcps TDD - The initial power, maximum power, and minimum power for DSCH type CCTrCH shall be determined as follows:
-	If the DSCH type CCTrCH is paired with an uplink CCTrCH(s) for inner loop power control, the minimum, maximum and initial power for each PDSCH is determined in the same way as described above for DCH type CCTrCHs.
-	If the DSCH type CCTrCH is not paired with an uplink CCTrCH(s) for inner loop power control, the PDSCH transmission power is DSCH Data Frame Protocol signalled (TS 25.435 [24]), with the maximum value determined in the same way as described above for DCH type CCTrCHs. The minimum and initial powers, however, are subject to control by the CRNC via the frame protocol].
[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Initial DL Transmission Power IE, the Node B shall determine the initial DL power for each timeslot within a DSCH type CCTrCH by the following rule: If both the CCTrCH Initial DL Transmission Power IE, included in the DL CCTrCH Information IE, and the DL Time Slot ISCP Info LCR IE, included in the RL Information IE, are included then the Node B shall use that power for the PDSCH and ignore the Initial DL Transmission Power IE included in the RL Information IE, otherwise the initial DL Power is the Initial DL Transmission Power IE included in the RL Information IE and if DL Time Slot ISCP info LCR IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged. The Node B shall apply the given power to the transmission on each DL PDSCH and on each Time Slot of the CCTrCH when starting transmission until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no Initial DL Transmission Power IE is included, the Node B shall use any transmission power level currently used on already existing RL/timeslots for this Node B Communication Context. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4).]
[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Maximum DL Power IE, the Node B shall determine the maximum DL power for each timeslot within a DSCH type CCTrCH by the following rule: If the CCTrCH Maximum DL Transmission Power IE, included in the DL CCTrCH Information IE, is included then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the Maximum DL Power IE included in the RL Information IE. The Node B shall store this value and not transmit with a higher power on any applicable PDSCH. If no Maximum DL Power IE is included, any maximum DL power stored for already existing RL/timeslots for this Node B Communication Context shall be applied.]
[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Minimum DL Power IE, the Node B shall determine the minimum DL power for each timeslot within a DSCH type CCTrCH by the following rule: If the CCTrCH Minimum DL Transmission Power IE, included in the DL CCTrCH Information IE, is included then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the Minimum DL Power IE included in the RL Information IE. The Node B shall store this value and not transmit with a lower power on any applicable PDSCH. If no Minimum DL Power IE is included, any minimum DL power stored for already existing RL/timeslots for this Node B Communication Context shall be applied.]
[3.84Mcps TDD and 7.68Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the DL Time Slot ISCP Info IE, the Node B shall use the indicated value when deciding the DL TX Power for each timeslot as specified in ref. TS 25.224 [21], i.e. it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged.]
[FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Individual" in the existing RL(s) and the RADIO LINK ADDITION REQUEST message includes the DL Reference Power IE, the Node B shall activate the power balancing and use the DL Reference Power IE for the power balancing procedure in the new RL(s), if activation of power balancing by the RADIO LINK ADDITION REQUEST message is supported, according to subclause 8.3.7. In this case, the Node B shall include the DL Power Balancing Activation Indicator IE in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message. If the Node B starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. Pinit shall be set to the power level indicated by the Initial DL Transmission Power IE (if received) or the decided DL TX power level on each DL channelisation code of a RL based on power level of existing RLs.]
[1.28Mcps TDD - Uplink Synchronisation Parameters LCR]:
[1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message contains the Uplink Synchronisation Parameters LCR  IE, the Node B shall use the indicated values of Uplink Synchronisation Stepsize IE and Uplink Synchronisation Frequency IE when evaluating the timing of the UL synchronisation.]
[1.28Mcps TDD - Power Control GAP:]
[1.28Mcps TDD - If the Power Control GAP IE is included in the RADIO LINK ADDITION REQUEST message, the Node B may use the value for the power control for HS-SCCH and HS-SICH according to TS 25.224 [21].]
[1.28Mcps TDD - E-UTRAN Inter-RAT measurement:]
[1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Idle Interval Information IE, if supported, the Node B shall use the value for E-UTRAN Inter-RAT measurement according to TS 25.331 [18]. 
[1.28Mcps TDD – Inter-frequency/ Inter-RAT measurement:]
[1.28Mcps TDD - If the RADIO LINK ADDITON REQUEST message includes the Measurement occasion pattern sequence parameters IE in the DCH Measurement Occasion Information IE, the Node B shall store the information about the Measurement occasion pattern sequences and use the value(s) to calculate the Inter-frequency/Inter-RAT measurement occasion according to TS 25.331 [18].]
[FDD – HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change]
[FDD – If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH Preconfiguration Setup IE in the RL Information IE for a Radio Link not indicated by the HS-PDSCH RL ID IE in the HS-DSCH Serving Cell Change Information IE the Node B shall if supported preconfigure the indicated cells or Enhanced HS Serving Cell Change acoording to [49.]:]
-	[FDD – The Node B shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the C-ID IE part of the RL Information IE in the RADIO LINK ADDITION REQUEST message. The list of secondary serving HS-DSCH cells is designated by the list of Secondary C-IDs in the HS-DSCH Preconfiguration Setup IE part of the RL Information IE in the RADIO LINK ADDITION REQUEST message.]
-	[FDD – The number of HS-SCCH codes to preconfigure for each cell may be optionally specified:]
-	[FDD – - by the Num Primary HS-SCCH Codes IE in the HS-DSCH Preconfiguration Setup IE, for the primary serving HS-DSCH cell]
-	[FDD – - by the Num Secondary HS-SCCH Codes IE in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE for each of the secondary serving HS-DSCH cells]
-	[FDD – If Num Primary HS-SCCH Codes IE or Num Secondary HS-SCCH Codes IE is not included in the message the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10].]
-	[FDD – The Node B shall return these codes in the Sets of HS-SCCH Codes IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE of the RADIO LINK ADDITION RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK ADDITION FAILURE message.]
-	[FDD – The Node B shall use the first in the numbered list of the primary serving HS-DSCH cell’s HS-SCCH codes in the HS-SCCH Preconfigured Codes IE sent to the RNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [18].]
-	[FDD – The Node B shall include, in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK ADDITION FAILURE message, IEs according to the rules defined for HS-DSCH Setup at Serving HS-DSCH Radio Link Change and:]
-	[FDD – - if HARQ Preamble Mode IE is included in the HS-DSCH Preconfiguration Setup IE the HARQ Preamble Mode Activation Indicator IE]
-	[FDD – - if MIMO Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE]
-	[FDD – if Ordinal number of frequency IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE]
-	[FDD – if MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE]
-	[FDD – if Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE]
-	[FDD – if Multiflow ordinal number of frequency IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE]
-	[FDD – - if HS-DSCH MAC-d PDU Size Format IE is included in the HS-DSCH Preconfiguration Setup IE and set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used for the cell in the preconfigured configuration the HS-DSCH TB Size Table Indicator IE for each preconfigured cell]
-	[FDD – - if Sixtyfour QAM Usage Allowed Indicator IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE or in the HS-DSCH Preconfiguration Setup IE the SixtyfourQAM DL Usage Indicator IE for each preconfigured cell]
-	[FDD – - if Continuous Packet Connectivity HS-SCCH less Information IE is included in the HS-DSCH Preconfiguration Setup IE the Continuous Packet Connectivity HS-SCCH less Information Response IE]
-	[FDD – - If the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH Preconfiguration Setup IE, then the Node B shall store this information in the preconfigured configuration.]
-	[FDD – - If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE, then the Node B may store this information in the preconfigured configuration.]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the Node B shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH Preconfiguration Info IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD – The Node B shall include in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK ADDITION FAILURE message the E-DCH FDD DL Control Channel Information containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:]
-	[FDD – The Node B shall allocate for the preconfigured configuration a primary  E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding  E-AGCH in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD –-The Node B may configure for the preconfigured configuration the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD –If the HS-DSCH Preconfiguration Setup IE includes the E-DCH Indicator IE for a secondary cell, the Node B shall include in the Additional E-DCH Preconfiguration Information IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK ADDITION FAILURE message the E-DCH FDD DL Control Channel Information IE containing the preconfigured configuration of the Additional E-DCH serving cell, corresponding to the cell indicated with the E-DCH Indicator IE, according to the rules defined for Serving Additional E-DCH Radio Link Change as follows:]
-	[FDD –The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving Additional E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – The Node B may configure for the preconfigured configuration the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving Additional E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the Multiflow Information IE, then the Node B shall allocate resources for the preconfigured Multiflow for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the F-TPICH Information IE, then the Node B shall allocate resources for the preconfigured F-TPICH channel for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the UL CLTD Information IE, then the Node B shall allocate resources for the preconfigured UL CLTD for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the UL MIMO Information IE, then the Node B shall allocate resources for the preconfigured UL MIMO for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the SixteenQAM UL Operation Indicator IE, then the Node B shall allocate resources for the preconfigured UL Sixteen QAM for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the SixtyfourQAM UL Operation Indicator IE, then the Node B shall allocate resources for the preconfigured UL Sixtyfour QAM for the concerned Node B Communication Context.]
[FDD – If the RADIO LINK ADDITION REQUEST message includes the Non-Serving Preconfiguration Setup IE in the RL Information IE and:]
- [FDD – if the choice of new Serving RL is "New Serving RL in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE and/or New non-serving RL E-DCH FDD DL Control Channel Information B IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK ADDITION RESPONSE message.]
- [FDD – if the choice of new Serving RL is "New Serving RL Not in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information C IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK ADDITION RESPONSE message.]
- [FDD – if the choice of new Serving RL is "New Serving RL in the Node B or New Serving RL Not in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C for the RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK ADDITION RESPONSE message.]
- [FDD – if the Additional E-DCH Non-Serving RL Preconfiguration Setup IE is included, the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C IE according to the choice of new Serving RL in Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information IE for the additional non serving E-DCH RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK ADDITION RESPONSE message.]
- [FDD –If the F-TPICH Information IE is included, the Node B shall use this information to allocate resources for the preconfigured F-TPICH channel for this RL in the serving RLS according to TS 25.211 [7].]
[1.28 Mcps TDD –Multi-Carrier E-DCH:]
[1.28Mcps TDD - If the Multi-Carrier E-DCH Information IE is present in the RADIO LINK ADDITION REQUEST message, then the Multi-Carrier E-DCH Information IE defines the new configuration and then:]
-	[1.28Mcps TDD - The Node B shall setup the requested E-DCH resource on the uplink frequecies indicated by the the Multi-Carrier E-DCH Information LCR IE.]
-	[1.28Mcps TDD - The Node B shall use the corresponding PRXdes_base IE for power control on each uplink frequency according to TS 25.331 [18].]
-	[1.28Mcps TDD - If the SNPL Carrier Group Indicator IE is present in the Multi-Carrier E-DCH Information LCR IE, the Node B shall use the information to determine which SNPL Carrier Group each frequency indicated by the UARFCN IE belongs to.]
-	[1.28Mcps TDD - If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "Separate Iub transport bearer mode", the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
-	[1.28Mcps TDD – If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "E-DCH UL flow multiplexing mode", the Node B shall use this mode in the new configuration and multiplex MAC-d flow received on the different carriers on one Iub transport bearer.]
-	[1.28Mcps TDD - If the Separate Iub transport bearer mode is used in the new configuration, then the Node B shall include the Binding ID IE and Transport Layer Address IE in the Multi-Carrier E-DCH Information Response LCR IE in the RADIO LINK ADDITION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
-	[1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration, then the Node B shall include the Binding ID IE and Transport Layer Address IE in the E-DCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
[FDD – UL DPCCH2:]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the UL DPCCH2 Information IE, then:]
-	[FDD – if the serving HS-DSCH RL is in the Node B then the Node B shall configure the concerned Node B Communication Context to use a second F-DPCH in the downlink, i.e. with transmission of only the TPC field and a DPCCH2 in the uplink, i.e. with the transmission of only the second pilot and the TPC field on the Serving HS-DSCH Radio Link and the Node B shall activate UL DPCCH2 operation for the radio link according to the information provided in the IE according to ref TS 25.214 [10].]
-	[FDD – If the UL DPCCH2 Information IE includes the Extended E-DPCCH Power Offset IE and if the E-DCH FDD Information IE is present in the RADIO LINK ADDITION REQUEST message, the Node B shall use the value to calculate the E-DPCCH gain factor.] 
[FDD – Downlink TPC enhancements:]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Downlink TPC enhancements Information IE, then:]
-	[FDD – The NodeB shall, if supported, use the Decimation factor for primary frequency IE and/or the Decimation factor for secondary frequency IE to configure all the radio links using F-DPCH on the related frequency with power control Algorithm 3.]
[FDD - If the TPC slot position in the RL Information is included in the RADIO LINK ADDITION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.]
[FDD - If the TPC slot position in the Additional E-DCHCell Information RL Add Req is included in the RADIO LINK ADDITION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.]
General:
If the RADIO LINK ADDITION REQUEST message includes the RL Specific DCH Information IE, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the DCH or the set of co-ordinated DCHs [FDD - for which the Transport Bearer Not Requested Indicator IE was not included].
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer shall not be Established" for a DCH, then the Node B shall not establish a transport bearer for the concerned DCH and shall include the Transport Bearer Not Setup Indicator IE for every corresponding DCH in the RADIO LINK ADDITION RESPONSE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer may not be Established" for a DCH and:]
-	[FDD - if the Node B establishes a transport bearer for the concerned DCH, the Node B shall include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the DCH being established.]
-	[FDD - if the Node B does not establish a transport bearer for the concerned DCH, the Node B shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH in the RADIO LINK ADDITION RESPONSE message.]
If the RADIO LINK ADDITION REQUEST message includes the RL Specific E-DCH Information IE, the Node B may use the transport layer addresses and the binding identifiers received from the CRNC when establishing transport bearers for the MAC-d flows of the E-DCHs.
The Node B shall start reception on the new RL(s) after the RLs are successfully established.
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Initial DL DPCH Timing Adjustment Allowed IE, then the Node B may perform an initial DL DPCH Timing Adjustment (i.e. perform a timing advance or a timing delay with respect to the SFN timing) on a Radio Link. In this case, the Node B shall include, for the concerned Radio Link(s), the Initial DL DPCH Timing Adjustment IE in the Radio Link Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Synchronisation Indicator IE, set to "Timing Maintained Synchronisation", the Node B shall use synchronisation procedure B according to subclause 4.3.2.4 in TS 25.214 [10]. The Node B shall select the TPC pattern as if "first RLS indicator" is set to "first RLS" according to subclause 5.1.2.2.1.2 in TS 25.214 [10].]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the F-DPCH Slot Format IE and if the Node B Communication Context is configured to use F-DPCH in the downlink, then the Node B shall use this information to configure the F-DPCH slot format of each RL according to TS 25.211 [7].]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the F-TPICH Information IE in the RL Information IE, the Node B shall use this information to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214 [10].]
[FDD - Radio Link Set Handling]:
[FDD - For each RL not having a common generation of the TPC commands in the DL with another RL, the Node B shall assign the RL Set ID IE included in the RADIO LINK ADDITION RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. In case of E-DCH, the generation of E-HICH related information for RLs in different RL Sets shall not be common.]
[FDD - For all RLs having a common generation of the TPC commands in the DL with another new or existing RL, the Node B shall assign the RL Set ID IE included in the RADIO LINK ADDITION RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. In case of E-DCH, the generation of E-HICH information for all RLs in a RL Set shall be common.]
[FDD - After addition of the new RL(s), the UL out-of-sync algorithm defined in TS 25.214 [10] shall, for each of the previously existing and newly established RL Set(s), use the maximum value of the parameters N_OUTSYNC_IND and T_RLFAILURE that are configured in the cells supporting the radio links of the RL Set. The UL in-sync algorithm defined in TS 25.214 [10] shall, for each of the established RL Set(s), use the minimum value of the parameters N_INSYNC_IND, that are configured in the cells supporting the radio links of the RL Set.]
[FDD - For each E-DCH RL which has or can have a common generation of E-RGCH information with another RL (current or future) when the Node B would contain the E-DCH serving RL, the Node B shall include the E-DCH RL Set ID IE in the RADIO LINK ADDITION RESPONSE message. The value of the E-DCH RL Set ID IE shall allow the RNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.]
[FDD - Serving HS-DSCH Radio Link Change]:
[FDD - If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH Serving Cell Change Information IE, then HS-PDSCH RL ID IE indicates the new Serving HS-DSCH Radio Link:]
-	[FDD - In the new configuration the Node B shall allocate the HS-PDSCH resources for the new Serving HS-PDSCH Radio Link.]
-	[FDD - The Node B may include the HARQ Memory Partitioning IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message. The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.]
-	[FDD - If the Node B Communication Context is configured with Sixtyfour QAM allowed for the serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM in the new configuration, then it shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
[FDD - HS-DSCH Setup on a New Radio Link at Serving HS-DSCH Radio Link Change:]
[FDD - If the HS-DSCH Information IE is present in the HS-DSCH Serving Cell Change Information IE, then:]
-	[FDD - The Node B shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE.]
-	[FDD - the HS-DSCH Information IE defines the new HS-DSCH configuration in the Node B to be used on the new HS-DSCH Radio Link.]
-	[FDD - The Node B shall include the HARQ Memory Partitioning IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message. The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than "8", if the MIMO Activation Indicator IE or the MIMO with four transmit antennas Activation Indicator IE, or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Information IE.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the MAC-hs Guaranteed Bit Rate IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue.]
-	[FDD – If the RADIO LINK ADDITION REQUEST message includes the Puncturing Handling in First Rate Matching Stage IE in the HS-DSCH Information IE , then the Node B shall, if supported, apply the puncturing during first stage rate matching according to the Puncturing Handling in First Rate Matching Stage IE.]
-	[FDD - The Node B shall include the HS-DSCH Initial Capacity Allocation IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message for every HS-DSCH MAC-d flow being established, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK ADDITION REQUEST message includes  HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH  Information IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer received in RADIO LINK ADDITION REQUEST in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE for a Priority Queue including  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH Information IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the Measurement Power Offset IE in the HS-DSCH Information IE, then the Node B shall use the measurement power offset as described in ref TS 25.214 [10], subclause 6A.2.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the HARQ Preamble Mode IE in the HS-DSCH Information IE, then the Node B shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the Node B shall include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK ADDITION RESPONSE message. If the HARQ Preamble Mode IE is not included or if the mode 0 is applied, then the Node B shall not include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH MAC-d PDU Size Format  IE in the HS-DSCH  Information IE, then the Node B shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]).]
-	[FDD - If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.]
-	[FDD - If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B shall activate the MIMO mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B may if the value is set to "allowed" use 64 QAM for the HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE with value set to "not allowed", then the Node B shall not use 64 QAM for the HS-DSCH Radio Link.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH MAC-d PDU Size Format IE set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the RADIO LINK ADDITION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - If the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH FDD Information IE, then the Node B may use:]
-	 [FDD - a different HS-SCCH in consecutive TTIs for this UE.]
-	 [FDD - HS-SCCH orders for the case of HS-SCCH-less operation to this UE.]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE the Node B may use the supported HSDPA functions for this UE.]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the Node B shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DL RLC PDU Size Format IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24].]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the Priority Queue Information IE in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall, if supported, consider the data of the HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]
-	[FDD - If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE in the HS-DSCH Serving Cell Change Information IE, then the Node B shall activate the Single Stream MIMO mode for the HS-DSCH Radio Link.] 
-	[FDD - If the MIMO with four transmit antennas Activation Indicator IE or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - The Node B may include the Precoder weight set restriction IE in the  HS-DSCH FDD Information Response IE in the HS-DSCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the CQI Feedback Cycle2 k IE and the CQI Cycle Switch Timer IE  is included in HS-DSCH FDD Information IE, then the Node B may use the indicated CQI Feedback Cycle2 k value, the CQI Cycle Switch Timer in HSDPA resources allocation for the UE.]
-	[FDD - If the Serving Cell Change CFN IE is included into the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. In the new configuration the Node B shall, if applicable, de-allocate the HS-PDSCH resources of the old Serving HS-PDSCH Radio Link. The Node B shall deactivate those resources at the next coming CFN with a value equal to the value requested by the RNC.]
- [FDD - If the Serving Cell Change CFN IE is not included then the Node B shall activate immediately the resources that are allocated for the new serving HS-PDSCH Radio Link, and shall keep active the resources that are allocated for the previous serving HS-PDSCH Radio Link.]
- [FDD - If the Serving Cell Change CFN IE is not included into the RADIO LINK ADDITION REQUEST message, then the Node B shall include the Transport Layer Address IE and the Binding ID IE for HS-DSCH MAC-d flow for the serving HS-PDSCH RL into the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
- [FDD - If the HS-DSCH Information IE is present in the HS-DSCH Serving Cell Change Information IE, then the Node B shall include the Transport Layer Address IE and the Binding ID IE for HS-DSCH MAC-d flow for the serving HS-PDSCH RL into the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
- [FDD - If the Node B needs a bearer re-arrangement, then the Node B may include the Transport Layer Address IE and the Binding ID IE for HS-DSCH MAC-d flow for the serving HS-PDSCH RL into the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
- [FDD - If a reset of the MAC-hs is not required the Node B shall include the MAC-hs Reset Indicator IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the requested Serving HS-DSCH Radio Link Change was successful or unsucessful, the Node B shall indicate this in the HS-DSCH Serving Cell Change Information Response IE  in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the HS-DSCH Serving Cell Change Information IE includes the Continuous Packet Connectivity HS-SCCH less Information IE, then:]
-	[FDD - The Node B shall configure the new Serving HS-DSCH Radio Link for Continuous Packet Connectivity HS-SCCH less operation according to TS 25.214 [10].]
-	[FDD - The Node B shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the Continuous Packet Connectivity HS-SCCH less Information Response IE in the HS-DSCH Serving Cell Change Information Response IE.]
-	[FDD - If at least one of HS-PDSCH Second Code Support IE is set to "True", then the Node B shall include HS-PDSCH Second Code Index IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD – If the HS-DSCH Serving Cell Change Information IE includes the Continuous Packet Connectivity DTX-DRX Information IE, then:]
-	[FDD – The Node B shall configure the concerned Node B Communication Context for Continuous Packet Connectivity DTX operation according to TS 25.214 [10].]
-	[FDD – If DRX Information IE is included in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].]
-	[FDD – If UE DRX Cycle 2 IE is included in the DRX Information IE in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].]
-	[FDD – If Inactivity Threshold for UE DRX Cycle 2 IE is included in the DRX Information IE in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].]
[FDD – Secondary Serving HS-DSCH Radio Link Change]:
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Additional HS Cell Information RL Addition IE, then HS-PDSCH RL ID IE indicates the new secondary serving HS-DSCH Radio Link:]
-	[FDD - In the new configuration the Node B shall allocate the HS-PDSCH resources for the new Secondary Serving HS-PDSCH Radio Link. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
-	[FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the Node B Communication Context is configured with Sixtyfour QAM allowed for the secondary serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM in the new secondary serving HS-DSCH Radio Link, then it shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
[FDD - Secondary Serving HS-DSCH Setup on a New Radio Link at Secondary Serving HS-DSCH Radio Link Change:]
-	[FDD - The Node B shall setup the requested HS-PDSCH resources on the secondary serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE.]
-	[FDD - The HS-DSCH FDD Secondary Serving Information IE defines the new secondary serving HS-DSCH configuration in the Node B to be used on the new secondary serving HS-DSCH Radio Link. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
-	[FDD - If Sixtyfour QAM will not be used for the secondary serving HS-DSCH Radio Link, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - If the Diversity Mode IE is included in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE in the RADIO LINK ADDITION REQUEST message the Node B shall apply cell specific transmit diversity configuration and if the Diversity Mode IE is not set to "None" the Node B shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE.]
-	[FDD - If the Serving Cell Change CFN IE is included into the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new secondary serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. In the new configuration the Node B shall, if applicable, de-allocate the HS-PDSCH resources of the old Serving HS-PDSCH Radio Link. The Node B shall deactivate those resources at the next coming CFN with a value equal to the value requested by the RNC.]
-	[FDD - If the Serving Cell Change CFN IE is not included then the Node B shall activate immediately the resources that are allocated for the new serving HS-PDSCH Radio Link, and shall keep active the resources that are allocated for the previous serving HS-PDSCH Radio Link.]
-	[FDD - If the requested Secondary Serving HS-DSCH Radio Link Change was successful or unsucessful, the Node B shall indicate this in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the MIMO with four transmit antennas Activation Indicator IE or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - Node B may include the Precoder weight set restriction IE in HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
[FDD - Additional Serving E-DCH Radio Link Change:]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Additional E-DCH Cell Information Addition IE  in the Additional E-DCH Cell Information RL Add Req IE and HS-PDSCH RL ID IE the Additional HS Cell Information RL Addition IE, the HS-PDSCH RL ID IE indicates the new Additional Serving E-DCH Radio Link:]
-	[FDD - In the new configuration the Node B shall allocate the E-DCH resources for the new additional serving E-DCH Radio Link on the secondary UL frequency. Non cell specific E-DCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
-	[FDD - If the old Additional Serving E-DCH RL is within this Node B, the Node B shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - The Node B may include in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional E-DCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD – The Node B may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message for any of the other E-DCH Radio Links in the Node B Communication Context that have not been included in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE.]
-	[FDD - If the Serving Cell Change CFN IE is included in the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC, or earlier. In this case, in the new configuration the Node B shall, if applicable, de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link. The Node B shall deactivate those resources at the next coming CFN with a value equal to the value requested by the RNC.]
-	[FDD - If the Serving Cell Change CFN IE is not included then the Node B shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link.]
-	[FDD - If the addition of the requested Additional Serving E-DCH Radio Link was successful but the Additional Serving E-DCH Radio Link change was unsuccessful, the Node B shall indicate this in the Additional E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
[FDD - Multiflow Setup]:
[FDD - If the Multiflow Information IE is present in HS-DSCH FDD Information IE in the RADIO LINK ADDITION REQUEST message, then the Node B shall setup the requested Multiflow operation and then:]
-	[FDD – Use Total number of HS-DSCH cells IE to apply the HS-DPCCH format at the physical layer based on the total number of cells provided in this IE.]
-	[FDD – Use Role IE to know whether Multiflow cells configured at this Node B are assisting ones or not, for which Node B must read the correspondent part of the HS-DPCCH feedback channel.]
-	[FDD – Use MIMO IE to decide whether to apply the MIMO HS-DPCCH format at the physical layer.]
-	[FDD – If Timing IE is included, then Node B shall use this information to decide whether Multiflow cells configured at this Node B follow a different HS-DPCCH timing with an offset indicated by this IE.]
-	[FDD – If the Max number of HS-SCCH sets per Node B IE is included, then Node B shall use this information on the upper limit for the number HS-SCCH sets allocated and reported back to CRNC.]
-	[FDD – If the Assisting Repetition Factors IE is included, then the Node B shall use the values indicated in this IE within the Multiflow configuration.]
[FDD - E-DCH]:
[FDD - If the RADIO LINK ADDITION REQUEST message contains the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE, then for every such RL:]
-	[FDD - The Node B shall setup the E-DCH resources as configured in the Node B Communication Context.]
-	[FDD - The Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE in the E-DCH FDD DL Control Channel Information IE in RL Information Response IE for every RL indicated by the E-DCH RL Indication IE, set to “E-DCH” in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
[FDD - Serving E-DCH Radio Link Change:]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Serving E-DCH RL IE, then Serving E-DCH RL IE indicates the new Serving E-DCH Radio Link:]
-	[FDD - If the new Serving E-DCH RL is in this Node B:]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message for the initial grant for the new serving E-DCH RL.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - The Node B may include the Default Serving Grant in DTX Cycle 2 IE in the RADIO LINK ADDITION RESPONSE message for the new serving E-DCH RL.]
-	[FDD - The Node B may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message for any of the other E-DCH Radio Links in the Node B Communication Context that have not been included in the E-DCH FDD DL Control Channel Information IE in RL Information Response IE.]
-	[FDD - If the Serving Cell Change CFN  IE is included in the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. In the new configuration the Node B shall, if applicable, de-allocate the E-AGCH resources of the old Serving E-DCH Radio Link. The Node B shall deactivate those resources at the next coming CFN with a value equal to the value requested by the SRNC.]
-	[FDD - If the Serving Cell Change CFN IE is not included then the Node B shall activate immediately the resources that are allocated for the new serving E-DCH Radio Link.]
-	[FDD - If the addition of the requested Serving E-DCH Radio Link was successful but the Serving E-DCH Radio Link change was unsuccessful, the Node B shall indicate this in the E-DCH Serving Cell Change Information Response IE  in the RADIO LINK ADDITION RESPONSE  message.]
[FDD - E-DPCH Handling]:
[FDD - If the RADIO LINK ADDITION REQUEST message includes an E-DPCH Information IE it defines the new E-DPCH configuration in the Node B to be used on the new E-DCH Radio Link and, the Node B shall use the new parameters for the related resource allocation operations.]
[FDD - If the E-TFCS Information IE in the E-DPCH Information IE contains the E-DPDCH Power Interpolation IE, the Node B shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the E-DPDCH Power Interpolation IE is not present, the Node B shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10].]
[FDD - If the E-TFCS Information IE in the E-DPCH Information IE contains the E-TFCI Boost Information IE, the Node B shall use the information according to TS 25.214 [10]. If the E-TFCI Boost Information IE is not present, the Node B shall use the E-TFCI BetaEC Boost value "127" in the algorithm defined in TS 25.214 [10].]
[FDD - If the RADIO LINK ADDITION REQUEST message includes an E-DPCH Information IE, which contains the Minimum Reduced E-DPDCH Gain Factor IE, then the Node B shall use the value to determine the applicable minimum gain factor (βed,k,reduced,min) defined in TS 25.214 [10]. For the case the Minimum Reduced E-DPDCH Gain Factor IE is not available for the Node B Communication Context, the Node B may use the default value defined in TS 25.331 [18].]
[FDD - E-DCH Setup on a new Radio Link:]
[FDD - If the E-DCH FDD Information IE is present in the RADIO LINK ADDITION REQUEST message:]
-	[FDD - the E-DCH FDD Information IE defines the new E-DCH FDD configuration in the Node B to be used on the new E-DCH Radio Link.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel information IE in the E-DCH FDD Information IE, then the Node B shall use this information to optimise MAC-e scheduling decisions.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE, then the Node B shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32])
-	[FDD - If the TNL QoS IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the Serving E-DCH RL IE indicating that the Serving E-DCH RL is in this Node B:]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message for the initial grant for the serving E-DCH RL.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new configuration and include the new configuration in the E-DCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - The Node B may include the Default Serving Grant in DTX Cycle 2 IE in the RADIO LINK ADDITION RESPONSE message for the serving E-DCH RL.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Non-Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE, if included, for the related resource allocation operation.]
-	[FDD - If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume scheduled grants being configured for that E-DCH MAC-d flow.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the Bundling Mode Indicator IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE and the Bundling Mode Indicator IE is set to "Bundling" and the E-TTI IE is set to "2ms", then the Node B shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the Node B shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH Maximum Bitrate IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH Processing Overload Level IE, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH Reference Power Offset IE, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the E-AGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH Power Offset for Scheduling Info IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the UPH Filtering Measurement Forwarding Request IE, then the Node B shall use this instruction to handle the UE UPH filtering measurement forwarding.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the SixteenQAM UL Operation Indicator IE, the Node B shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the SixteenQAM UL Operation Indicator IE.]
-	[FDD - If SixteenQAM UL Operation is activated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to (TS 25.321 [32]. If SixteenQAM UL Operation is deactivated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to (TS 25.321 [32].]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer shall not be Established" for an E-DCH MAC-d flow, then the Node B shall not establish a transport bearer for the concerned E-DCH MAC-d flow and shall include the Transport Bearer Not Setup Indicator IE for the corresponding E-DCH MAC-d flow in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer may not be Established" for an E-DCH MAC-d flow and:]
-	[FDD - if the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow, the Node B shall include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the E-DCH MAC-d flow being established.]
-	[FDD - if the Node B does not establish a transport bearer for the concerned E-DCH MAC-d flow, the Node B shall include the Transport Bearer Not Setup Indicator IE for the corresponding E-DCH MAC-d flow in the RADIO LINK ADDITION RESPONSE message.]
[FDD - Additional E-DCH Setup:]
[FDD - If the Additional E-DCH Cell Information RL Add Req IE is present in the RADIO LINK ADDITION REQUEST message and the choice of Setup Or Addition Of E-DCH On Secondary UL Frequency is "Setup", then the Additional E-DCH Cell Information Setup IE defines the new configuration and then:]
-	[FDD - If the C-ID IE is included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the C-ID IE indicates the cell in which the additional E-DCH shall be setup]
-	[FDD - The Node B shall setup the Additional E-DCH on the secondary uplink frequency and setup the requested Additional E-DCH resources on the Radio Links and in the cells indicated by the E-DCH Additional RL ID IE and the C-ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE.]
-	[FDD - If the C-ID IE is not included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the E-DCH Additional RL ID IE indicates the existing RL on which the Additional E-DCH shall be setup.]
-	[FDD - The Node B shall setup the Additional E-DCH on the Radio Links indicated by the E-DCH Additional RL ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE]
-	[FDD - The Node B shall use for the non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters the same values as for the corresponding cell of the Primary uplink frequency.]
-	[FDD - If the DL Power Balancing Information IE and/or the Minimum Reduced E-DPDCH Gain Factor IE are present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the Secondary UL Frequency Activation State IE is present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the Node B shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.]
-	[FDD - If the F-DPCH Slot Format IE is present in the Additional E-DCH RL Specific Information To Setup IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the Primary CPICH Usage For Channel Estimation IE, the Secondary CPICH Information IE, the E-AGCH Power Offset IE, the E-RGCH Power Offset IE and/or the E-HICH Power Offset IE are present in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH RL Specific Information To Setup IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Maximum Bitrate IE, the E-DCH Processing Overload Level IE, the E-DCH Minimum Set E-TFCI IE, the Implicit Grant handling IE, the Minimum TEBS threshold IE and/or the DTX Information2 IE are present in the Additional E-DCH FDD Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If activation of power balancing for the Additional E-DCH RL by the RADIO LINK ADDITION REQUEST message is supported by the Node B, the Node B shall include the DL Power Balancing Activation Indicator IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.]
-	[FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
-	[FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the  Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE for each Additional E-DCH RL in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the Additional Serving E-DCH Radio Link is configured in the Node B, then:]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message for the initial grant for the Additional serving E-DCH RL and may include the  Default Serving Grant in DTX Cycle 2 IE.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - If the Serving Cell Change CFN IE is included in the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. If the Serving Cell Change CFN IE is not included then the Node B shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link.]
[FDD – Additional E-DCH RL Addition:]
[FDD - If the Additional E-DCH Cell Information RL Add Req IE is present in the RADIO LINK ADDITION REQUEST message and the choice of Setup Or Addition Of E-DCH On Secondary UL Frequency is "Addition", then the Additional E-DCH Cell Information Addition IE defines the new configuration and then:]
-	[FDD - The Node B shall setup the requested E-DCH resources as requested, or as configured in the Node B Communication Context, on the Radio Links indicated by the E-DCH Additional RL ID IE in the Additional E-DCH RL Specific Information To Add IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
-	[FDD - if the Multicell E-DCH Information IE is included and contains the Minimum Reduced E-DPDCH Gain Factor IE, the Node B shall use the information in the same way as for the information used on the Primary uplink frequency.]
-	[FDD - I f the Additional E-DCH FDD Information IE is included and contains the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Minimum Set E-TFCI IE, the E-DCH Maximum Bitrate IE, the E-DCH Processing Overload Level IE, the Implicit Grant handling IE, the Minimum TEBS threshold IE and/or the DTX Information IE, the Node B shall use the information in the same way as for the information used on the Primary uplink frequency.]
-	[FDD - If the Initial DL Transmission Power IE, the Maximum DL Power IE, the Minimum DL Power IE  and/or the F-DPCH Slot Format IE are present in the Additional E-DCH RL Specific Information To Add IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the DL Reference Power IE, the E-AGCH Power Offset IE, the E-RGCH Power Offset IE and/or the E-HICH Power Offset IE are present in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH RL Specific Information To Add IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Individual" in the existing Additional E-DCH RL(s) and the RADIO LINK ADDITION REQUEST message includes the DL Reference Power IE, the Node B shall activate the power balancing and use the DL Reference Power IE for the power balancing procedure in the new Additional E-DCH RL(s), if activation of power balancing by the RADIO LINK ADDITION REQUEST message is supported, according to subclause 8.3.7. In this case, the Node B shall include the DL Power Balancing Activation Indicator IE in the E-DCH Additional RL Specific Information Response IE in the Additional E-DCH FDD  Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message. If the Node B starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. Pinit shall be set to the power level indicated by the Initial DL Transmission Power IE (if received) in the Additional E-DCH RL Specific Information To Add IE or the decided DL TX power level on each DL channelisation code of an Additional E-DCH RL based on power level of existing Additional E-DDCH RLs.]
-	[FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.]
-	[FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
-	[FDD - For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]
-	[FDD - For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Add IE in the Additional E-DCH FDD Setup Information IE the Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE for each Additional E-DCH RL in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]
[FDD – E-DCH decoupling operation]
[FDD – If the E-DCH Decoupling Indication IE is present in the RADIO LINK ADDITION REQUEST message, then the Node B shall if supported use this indication for the E-DCH decoupling operation.]
[FDD – Radio Links without DPCH/F-DPCH operation]
[FDD – If the Radio Links without DPCH/F-DPCH Indication IE is present in the RADIO LINK ADDITION REQUEST message:]
-	[FDD – The Node B shall if supported start operation with Radio Links without DPCH/F-DPCH.]
[TDD - HS-DSCH Setup]:
[TDD - If the HS-DSCH Information IE is present in the RADIO LINK ADDITION REQUEST message, then]:
-	[TDD - The Node B shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE.]
-	[TDD - The Node B shall include the HARQ Memory Partitioning IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[TDD - If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH MAC-d PDU Size Format  IE in the HS-DSCH  Information IE, then the Node B shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]).]
-	[TDD - The Node B shall include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of transport bearer for every HS-DSCH MAC-d flow being established.]
-	[TDD - If the RADIO LINK ADDITION REQUEST message includes the Transport Layer Address IE and Binding ID IE in the HS-DSCH Information IE for an HS-DSCH MAC-d flow, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned HS-DSCH MAC-d flow. If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.]
-	[TDD - If the RADIO LINK ADDITION REQUEST message includes the MAC-hs Guaranteed Bit Rate IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.]
-	[TDD - If the RADIO LINK ADDITION REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.]
-	[TDD - If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue.]
-	[TDD - If the RADIO LINK ADDITION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DL RLC PDU Size Format IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24].]
-	[TDD - The Node B shall include the HS-DSCH Initial Capacity Allocation IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message for every HS-DSCH MAC-d flow being established, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK ADDITION REQUEST message includes  HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH  Information IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer received in RADIO LINK ADDITION REQUEST in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE for a Priority Queue including  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE.]
-	[TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - HS-SCCH Specific Information Response IE] [1.28Mcps TDD - HS-SCCH Specific Information Response LCR IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[1.28Mcps TDD - If the TSN-Length IE is included in the HS-DSCH TDD Information IE, then the IE is used to indicate the TSN bits applied to the MAC-hs PDU frame.]
-	[1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Number of Supported Carriers IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B shall use this information to allocate HSDPA resources over multiple carriers for the UE.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK ADDITION REQUEST message includes the Multi-carrier HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B shall use this information together with the HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information IE to allocate HSDPA resources over multiple carriers for the UE.]
-	[1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B may use this information in HSDPA resources allocation for the UE.]
-	[1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH over multiple carriers and include the HS-SCCH Specific Information Response LCR per UARFCN IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B shall include the HARQ Memory Partitioning per UARFCN IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[1.28Mcps TDD - If the Node B allows UE to apply HSDPA resources distributed over multiple carriers, the Node B may indicate the number of carriers actually used by the UE and include the Multi-Carrier number IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B may include the UsedFrequency IE in the HS-SCCH Specific Information Response LCR IE in the RADIO LINK ADDITION RESPONSE message.]
-	[1.28Mcps TDD - If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B may include the UARFCN IE in the HS-SCCH Specific Information Response LCR per UARFCN IE in the RADIO LINK ADDITION RESPONSE message.]
	[1.28 Mcps TDD - If the MIMO Activation Indicator IE is included in the HS-DSCH TDD Information IE, then, the Node B shall activate the MIMO mode for the HS-DSCH Radio Link, decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
[TDD - Intra-Node B Serving HS-DSCH Radio Link Change]:
[TDD - If the RADIO LINK ADDITION REQUEST message includes the HS-PDSCH RL ID IE, this indicates the new Serving HS-DSCH Radio Link]:
-	[TDD - The Node B may include the HARQ Memory Partitioning IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - HS-SCCH Specific Information Response IE] [1.28Mcps TDD - HS-SCCH Specific Information Response LCR IE] [7.68Mcps TDD - HS-SCCH Specific Information Response 7.68Mcps IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
[TDD - E-DCH]:
[TDD - If the [3.84Mcps TDD - E-DCH Information IE][1.28Mcps TDD - E-DCH Information 1.28Mcps IE] [7.68Mcps TDD - E-DCH Information 7.68Mcps IE] is present in the RADIO LINK ADDITION REQUEST message:]
-	[TDD - The Node B shall setup the requested E-DCH resources on the Radio Link indicated by the E-DCH Serving RL IE.]
-	[TDD - If the TNL QoS IE is included in the E-DCH MAC-d Flows Information TDD IE for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
-	[TDD - If the RADIO LINK ADDITION REQUEST message includes the Transport Layer Address IE and Binding ID IE in the E-DCH MAC-d Flows Information TDD IE for an E-DCH MAC-d flow, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow.]
-	[TDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flows Information TDD IE, the Node B shall use this information for the related resource allocation operation.]
-	[TDD - If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type IE in the E-DCH MAC-d Flows Information TDD IE is set to "Non-scheduled" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants are configured for that E-DCH MAC-d flow and shall use the information within the [3.84Mcps TDD - E-DCH Non-scheduled Grant Information TDD IE] [1.28Mcps TDD - E-DCH Non-scheduled Grant Information LCR TDD IE] [7.68Mcps TDD - E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE], if included, for the related resource allocation operation.]
-	[TDD - If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type IE in the E-DCH MAC-d Flows Information TDD IE is set to "Scheduled" the Node B shall assume that it may issue scheduled grants for the concerned E-DCH MAC-d flow.]
-	[TDD - If the RADIO LINK ADDITION REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows Information TDD IE, then the Node B shall use this information to optimise MAC-e scheduling decisions for the related queue.]
-	[1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the MAC-es Maximum Bit Rate LCR IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows Information TDD IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[TDD - If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).]
-	[3.84Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH TDD Maximum Bitrate IE in the E-DCH TDD Information IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH Physical Layer Category LCR IE or Extended E-DCH Physical Layer Category LCR IE in the E-DCH TDD Information LCR IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[7.68Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH TDD Maximum Bitrate 7.68Mcps IE in the E-DCH TDD Information 7.68Mcps IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[TDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH Processing Overload Level IE in the [3.84Mcps TDD - E-DCH TDD Information IE] [7.68Mcps TDD - E-DCH TDD Information 7.68Mcps IE] [1.28Mcps TDD - E-DCH TDD Information LCR IE], then if the Node B could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]
-	[TDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH Power Offset for Scheduling Info IE in the [3.84Mcps TDD - E-DCH TDD Information IE] [1.28Mcps TDD - E-DCH TDD Information LCR IE] [7.68Mcps TDD - E-DCH TDD Information 7.68Mcps IE], then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
-	[1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Maximum Number of Retransmission for Scheduling Info LCR IE and the E-DCH Retransmission timer for Scheduling Info LCR IE in the E-DCH TDD Information LCR IE, then the Node B shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.]
-	[TDD - The Node B shall allocate an E-RNTI identifier and include the E-RNTI identifier and the E-AGCH(s) assigned in the E-DCH Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Multi-Carrier E-DCH Physical Layer Category LCR IE in the E-DCH TDD Information LCR IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.]
-	[1.28Mcps TDD - If the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE is not present and if the RADIO LINK ADDITION REQUEST message includes the UE TS0 Capability LCR IE in the E-DCH TDD Information LCR IE, the Node B can use this information to allocate the downlink resources for the UE according to TS 25.306 [33].]
[TDD - Intra-Node B Serving E-DCH Radio Link Change]:
[TDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH Serving RL IE, this indicates the new Serving E-DCH Radio Link]:
-	[TDD - The Node B shall allocate E-AGCH parameters [1.28Mcps TDD - E-HICH parameters] corresponding to the E-DCH and include the E-AGCH Specific Information Response TDD IE, [1.28Mcps TDD - E-HICH Specific Information Response 1.28Mcps TDD IE] in the E-DCH Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
[1.28 Mcps TDD - Continuous Packet Connectivity Handling]:
[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the Continuous Packet Connectivity DRX Information LCR IE, then the Node B shall take account into these parameters to decide the DRX operation related parameters and configure the concerned Node B Communication Context for DRX operation according to TS 25.224 [21] and include the parameter(s) in the Continuous Packet Connectivity DRX Information Response LCR IE in the RADIO LINK ADDITION RESPONSE message.]
[1.28 Mcps TDD - If the Inactivity Threshold for UE DRX Cycle Ext IE is included in the Continuous Packet Connectivity DRX Information LCR IE, then the Node B may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [21].]
[1.28 Mcps TDD - If the Enabling Delay Ext IE is included in the Continuous Packet Connectivity DRX Information LCR IE, then the Node B may use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [21].]
[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH Semi-Persistent scheduling Information LCR IE, then:]
-	[1.28 Mcps TDD - The Node B shall configure the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [21].]
-	[1.28 Mcps TDD - The Node B shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the HS-DSCH Semi-Persistent scheduling Information Response LCR IE in the RADIO LINK ADDITION RESPONSE message.]
-	[1.28 Mcps TDD - If the HS-DSCH Semi-Persistent Resource Reservation Indicator IE is included in the HS-DSCH Semi-Persistent scheduling Information LCR IE, then the Node B shall include Allcoated HS-PDSCH Semi-persistent resource IE in the RADIO LINK ADDITION RESPONSE message.]
-	[1.28 Mcps TDD - The Node B shall include the Buffer Size for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK SETUP RESPONSE message.]
-	[1.28 Mcps TDD - The Node B shall include the Number of Processes for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK SETUP RESPONSE message.]
[1.28 Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH Semi-Persistent scheduling Information LCR IE, then:]
-	[1.28 Mcps TDD - The Node B shall configure the Serving E-DCH Radio Link indicated by the E-DCH Serving RL IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [21].]
-	[1.28 Mcps TDD - If the E-DCH Semi-Persistent Resource Reservation Indicator IE is included in the E-DCH Semi-Persistent scheduling Information LCR IE, then the Node B shall include Allcoated E-DCH Semi-persistent resource IE in the RADIO LINK ADDITON RESPONSE message.]
[1.28 Mcps TDD - MU-MIMO Handling:]
[1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the MU-MIMO Information IE, then:]
-	[1.28 Mcps TDD - The Node B can activate MU-MIMO operation on Uplink and/or Downlink indicated by the MU-MIMO indicator IE and shall include the MU-MIMO Information Response IE in the RADIO LINK ADDITION RESPONSE message.]
-	[1.28 Mcps TDD - If the Standalone Midamble Channel Information IE is included in the MU-MIMO Information IE, then the Node B shall configure the concerned Node B Communication Context for standalone midamble related operation according to TS 25.224 [21].]
-	[1.28 Mcps TDD - If the Standalone Midamble Channel Information request IE is included in the MU-MIMO Information IE, if the Node B will use MU-MIMO and if the Node B can allocate the standalone midamble resource, then the Node B shall include the Standalone Midamble Channel Information IE in the MU-MIMO Information Response IE in the RADIO LINK ADDITION RESPONSE message, else the Node B shall not include the Standalone Midamble Channel Information IE in the MU-MIMO Information Response IE in the RADIO LINK ADDTION RESPONSE message].
[1.28Mcps TDD – Non-rectangular resource operation:]
[1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message contains the UE support of non-rectangular resource allocation IE, the Node B shall, if supported, use this information to determine whether includes the Non-rectangular resource allocation indicator IE and the Non-rectangular resource timeslot set IE or not.]
Response Message:
If all requested RLs are successfully added, the Node B shall respond with a RADIO LINK ADDITION RESPONSE message.
After sending the RADIO LINK ADDITION RESPONSE message, the Node B shall continuously attempt to obtain UL synchronisation on the Uu interface.
For each RL for which the Delayed Activation IE is not included in the RADIO LINK ADDITION REQUEST message, the Node B shall:
-	[FDD - start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16].]
-	[TDD - start transmission on the new RL immediately as specified in TS 25.427 [16].]
For each RL for which the Delayed Activation IE is included in the RADIO LINK ADDITION REQUEST message, the Node B shall:
-	if the Delayed Activation IE indicates "Separate Indication":
-	not start any DL transmission for the concerned RL on the Uu interface;
-	if the Delayed Activation IE indicates "CFN":
-	[FDD - start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16], however never before the CFN indicated in the Activation CFN IE.]
-	[TDD - start transmission on the new RL at the CFN indicated in the Activation CFN IE as specified in TS 25.427 [16].]
8.3.1.3	Unsuccessful Operation

Figure 29: Radio Link Addition procedure: Unsuccessful Operation
If the establishment of at least one radio link is unsuccessful, the Node B shall respond with a RADIO LINK ADDITION FAILURE message. The message contains the failure cause in the Cause IE.
[FDD - If some RL(s) were established successfully, the Node B shall indicate this in the RADIO LINK ADDITION FAILURE message in the same way as in the RADIO LINK ADDITION RESPONSE message.]
[FDD - If the RADIO LINK ADDITION REQUEST contains a C-ID IE indicating that a Radio Link must be established on a Cell where DPC Mode change is not supported and DPC Mode can be changed for the relevant Node B Communication Context, the Node B shall consider the procedure as failed for the concerned Radio Link and shall respond with a RADIO LINK ADDITION FAILURE with the appropriate cause value ("DPC Mode change not supported").]
[FDD - If the requested Serving HS-DSCH Radio Link Change was successful, or if the addition of the requested serving HS-DSCH Radio Link was successful or existed already but the Serving HS-DSCH Radio Link change was unsucessful, the Node B shall indicate this in the HS-DSCH Serving Cell Change Information Response IE  in the RADIO LINK ADDITION FAILURE message.]
[FDD - If the requested secondary serving HS-DSCH Radio Link Change was successful, or if the addition of the requested secondary serving HS-DSCH Radio Link was successful or existed already but the secondary serving HS-DSCH Radio Link change was unsucessful, the Node B shall indicate this in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION FAILURE message.]
[FDD - If the requested Serving E-DCH Radio Link Change was successful, or if the addition of the requested serving E-DCH Radio Link was successful or existed already but the Serving E-DCH Radio Link change was unsucessful, the Node B shall indicate this in the E-DCH Serving Cell Change Information Response IE  in the RADIO LINK ADDITION FAILURE message.]
[FDD - If the requested additional serving E-DCH Radio Link Change was successful, or if the addition of the requested additional serving E-DCH Radio Link was successful or existed already but the additional serving E-DCH Radio Link change was unsucessful, the Node B shall indicate this in the Additional E-DCH Serving Cell Change Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION FAILURE message.]
Typical cause values are as follows:
Radio Network Layer Cause
-	Combining not supported
-	Combining Resources not available
-	Requested Tx Diversity Mode not supported
-	UL SF not supported
-	DL SF not supported
-	Reconfiguration CFN not elapsed
-	CM not supported
-	[FDD - DPC Mode change not supported]
-	Delayed Activation not supported
-	[FDD - Continuous Packet Connectivity DTX-DRX operation not available]
-	[FDD - Continuous Packet Connectivity UE DTX Cycle not available]
-	[FDD - MIMO not available]
-	[FDD - SixtyfourQAM DL and MIMO Combined not available]
-	[FDD - Multi Cell operation not available.]
-	[1.28Mcps TDD- MIMO not available]
-	[1.28Mcps TDD - SixtyfourQAM DL and MIMO Combined not available]
-	[FDD - TX diversity for MIMO UE on DL Control Channels not available]
-	[FDD – Single Stream MIMO not available]
-	[FDD - Multi Cell operation with MIMO not available.]
-	[FDD - Multi Cell operation with Single Stream MIMO not available.]
-	[FDD - Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available]
-	[FDD - Multi Cell E-DCH operation not available]
-	[FDD – Frequency Specific Compressed mode operation not available]
-	[FDD - UL CLTD operation not available]
-	[FDD - MIMO with four transmit antennas not available]
-	[FDD - Dual Stream MIMO with four transmit antennas not available]
-	[FDD – Multiflow operation not available]
-	[FDD - SixtyfourQAM UL operation not available]
-	[FDD – UL MIMO operation not available]
-	[FDD – UL MIMO and SixteenQAM operation not available]
-	[FDD – UL MIMO and SixtyfourQAM operation not available]
-	[FDD – E-DCH decoupling operation not available]
-	[FDD – Radio Links without DPCH/F-DPCH operation not available]
-	[FDD – UL DPCCH2 operation not available]
-	[FDD – Downlink TPC enhancements operation not available]
Transport Layer Cause
-	Transport Resources Unavailable
Miscellaneous Cause
-	O&M Intervention
-	Control processing overload
-	HW failure
8.3.1.4	Abnormal conditions
[FDD - If the RADIO LINK ADDITION REQUEST message contains the Compressed Mode Deactivation Flag IE with the value ''Deactivate'' when compressed mode is active for the existing RL(s), and at least one of the new RL is added in a cell that has the same UARFCN (both UL and DL) of at least one cell with an already existing RL and frequency specific compressed mode is not supported, the Node B shall regard the Radio Link Addition procedure as failed and shall respond with a RADIO LINK ADDITION FAILURE message with the cause value "Invalid CM settings".]
[FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Individual" in the existing RL(s) and if the DL Reference Power IEs are included in the RL Information IE but the DL Reference Power IE is not present for each RL in the RL Information IE, the Node B shall regard the Radio Link Addition procedure as failed and shall respond with a RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the DL Reference Power IEs in the RL Information IE but the power balancing is not active in the existing RL(s) or the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Common" in the existing RL(s), the Node B shall regard the Radio Link Addition procedure as failed and shall respond with a RADIO LINK ADDITION FAILURE message with the cause value "Power Balancing status not compatible".]
If the RADIO LINK ADDITION REQUEST message includes the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE or RL Specific E-DCH Information IE included in the RL Information IE for a specific RL [FDD - and the E-DCH RL is already configured in the Node B] and the Diversity Control Field IE is set to "Must", the Node B shall regard the Radio Link Addition procedure as failed and respond with the RADIO LINK ADDITION FAILURE message.
If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE in the RL Information IE for a specific RL and the Diversity Control Field IE is set to "May", the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.
If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE in the RL Information IE for a specific RL and the Diversity Control Field IE is set to "Must Not", the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.
If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in [FDD - the RL Specific E-DCH Information IE in the RL Information IE for the first E-DCH RL][TDD – the E-DCH MAC-d Flows Information TDD IE], the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK SETUP FAILURE message.
If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE for an HS-DSCH MAC-d Flow in the HS-DSCH MAC-d Flows Information IE, the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.
If the RADIO LINK ADDITION REQUEST message contains the Transport Layer Address IE or the Binding ID IE, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.
[1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK ADDITION REQUEST message does not include the UARFCN IE, the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.]
[1.28Mcps TDD - For a single frequency cell, if the RADIO LINK ADDITION REQUEST message includes the UARFCN IE, the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.]
[FDD - If the concerned Node B Communication Context is configured to use DPCH in downlink and if a transmission gap pattern sequence is active with an SF/2 downlink compressed mode method and the RADIO LINK ADDITION REQUEST message does not contain the transmission gap pattern sequence code information for any new radio link, the Node B shall reject the Radio Link Addition procedure using the RADIO LINK ADDITION FAILURE message with the cause value "Invalid CM Settings".]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH Serving Cell Change Information IE but not the HS-DSCH FDD Information IE and the Node B Communication Context is not configured for HS-DSCH, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Serving E-DCH RL IE but the Node B Communication Context is not configured for E-DCH, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Serving Cell Change CFN IE but neither the Serving E-DCH RL IE nor HS-DSCH Serving Cell Change Information IE is included into, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the E-DCH FDD Information IE is present in the RADIO LINK ADDITION REQUEST message, but the E-DPCH Information IE is not present, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH RL Indication IE set to "E-DCH", but no E-DCH FDD Information IE, and the Node B Communication Context is not configured for E-DCH, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH FDD Information IE but no E-DCH RL Indication IE set to "E-DCH", then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[TDD - If the RADIO LINK ADDITION REQUEST message includes the HS-PDSCH RL-ID IE not equal to the RL ID IE, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[TDD - If the RADIO LINK ADDITION REQUEST message includes the E-DCH Serving RL IE not equal to the RL ID IE, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[TDD - If the RADIO LINK ADDITION REQUEST message contains the HS-DSCH Information IE and if the Priority Queues associated with the same HS-DSCH MAC-d Flow ID IE have the same Scheduling Priority Indicator IE value, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE [FDD - in the HS-DSCH Serving Cell Change Information]  and the HS-DSCH MAC-d PDU Size Format  IE in the HS-DSCH  Information IE [FDD - in the HS-DSCH Serving Cell Change Information]  has the value  "Indexed MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.
If the RADIO LINK ADDITION REQUEST message does not include the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE [FDD - in the HS-DSCH Serving Cell Change Information]  and the HS-DSCH MAC-d PDU Size Format  IE in the HS-DSCH  Information IE [FDD - in the HS-DSCH Serving Cell Change Information]  has the value  "Flexible MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.
[FDD - If the RADIO LINK ADDITION REQUEST message contains, for at least one logical channel, the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[TDD - If the RADIO LINK ADDITION REQUEST message contains, for at least one logical channel, the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE, and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE is not present, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[TDD - If the RADIO LINK ADDITION REQUEST message contains the Transport Layer Address IE or the Binding ID IE when establishing a transport bearer for HS-DSCH MAC-d flow being added, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[TDD - If the RADIO LINK ADDITION REQUEST message contains the Transport Layer Address IE or the Binding ID IE when establishing a transport bearer for E-DCH MAC-d flow being added, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
If the RADIO LINK ADDITION REQUEST message does not contain the E-DCH Decoupling Indication IE but contains the HS-PDSCH RL ID IE [FDD - in the HS-DSCH Serving Cell Change Information IE] and/or Serving E-DCH RL IE, and if both HS-DSCH and E-DCH are configured in the Node B but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not in the same cell, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.
[FDD - If the RADIO LINK ADDITION REQUEST message contains the HS-DSCH Serving Cell Change Information IE and the E-DPCH Information IE which includes the HS-DSCH Configured Indicator IE set as “HS-DSCH not configured” then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message contains the Transport Bearer Not Requested Indicator IE for a DCH but the DCH is configured to be included as a part of the downlink CCTrCH, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message contains the MIMO Activation Indicator IE, Sixtyfour QAM Usage Allowed Indicator IE set to "Allowed", the Additional HS Cell Information RL Addition IE, the Single Stream MIMO Activation Indicator IE, the MIMO with four transmit antennas Activation Indicator IE and/or the Dual Stream MIMO with four transmit antennas Activation Indicator IE but does not contain the HS-DSCH MAC-d PDU Size Format IE set to "Flexible MAC-d PDU Size", then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD – If the RADIO LINK ADDITION REQUEST message contains the Serving E-DCH RL ID IE but contains the Transport Bearer Not Requested Indicator IE or there is at least one E-DCH MAC-d flow which transport bearer was not configured in the Node B, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE for a DCH for a specific RL and the specific RL is combined with the existing RL which the transport bearer is established for the DCH in Node B, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message contains the Additional HS Cell Information RL Addition IE and if the HS-DSCH is not configured in the Node B Communication Context and the HS-DSCH Information IE is not present, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
If the RADIO LINK ADDITION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE [FDD - in the HS-DSCH Serving Cell Change Information IE] set to “Flexible RLC PDU Size”,  HS-DSCH MAC-d PDU Size Format  IE in the HS-DSCH  Information IE [FDD - in the HS-DSCH Serving Cell Change Information IE]  has the value  "Indexed MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.
If the RADIO LINK ADDITION REQUEST message does not include the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE [FDD - in the HS-DSCH Serving Cell Change Information IE]  and the DL RLC PDU Size Format  IE in the HS-DSCH  Information IE [FDD - in the HS-DSCH Serving Cell Change Information IE]  has the value  "Flexible RLC PDU Size", the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.
[FDD - If the RADIO LINK ADDITION REQUEST message contains a MIMO Activation Indicator IE and a Single Stream MIMO Activation Indicator IE in the HS-DSCH FDD Information IE in the HS-DSCH Serving Cell Change Information IE or in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message contains the Diversity Mode IE in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE and the secondary serving HS-DSCH is already configured in the Node B Communication Context, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the secondary serving HS-DSCH is not configured in the Node B Communication Context and if the RADIO LINK ADDITION REQUEST message contains in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE the Diversity Mode IE not set to "None" but not the Transmit Diversity Indicator or contains the Transmit Diversity Indicator but not the Diversity Mode IE not set to "None", then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message contains the Additional E-DCH Cell Information RL Add Req IE and if the E-DPCH Information IE is not present or the E-DPCH Information was not configured in the Node B Communication Context, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message contains the Additional E-DCH Cell Information RL Add Req IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message contains the Additional E-DCH Cell Information RL Add Req IE and the C-ID IE is not included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, and the Radio Link indicated by the E-DCH Additional RL ID IE is not configured in the current Node B Communication Context as a Secondary Serving HS-DSCH radio link without any configured Additional E-DCH, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message contains the Additional HS Cell Information RL Addition IE and the new configuration contains more than one secondary serving HS-DSCH RL and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1", which are previously assigned to the RL or received in the Ordinal Number Of Frequency IE in the HS-DSCH FDD Secondary Serving Information IE, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message contains the Additional HS Cell Information RL Addition IE and the new configuration contains more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value “1, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message contains the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE and theTransmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message with the cause value “Invalid CM settings”.]
[FDD - If the RADIO LINK ADDITION REQUEST message contains the UL CLTD Information IE but does not contain the F-TPICH Information IE, or if it contains HS-DSCH Preconfiguration Setup IE with UL CLTD Information IE but without F-TPICH Information IE, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message contains the UL MIMO Information IE in E-DCH FDD Information IE but does not contain the UL CLTD Information IE, or if it contains HS-DSCH Preconfiguration Setup IE with UL MIMO Information IE but without UL CLTD Information IE, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
[FDD - If the RADIO LINK ADDITION REQUEST message contains more than one of a MIMO Activation Indicator IE, a MIMO with four transmit antennas Activation Indicator IE, a Dual Stream MIMO with four transmit antennas Activation Indicator IE in HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]
8.3.2	Synchronised Radio Link Reconfiguration Preparation
8.3.2.1	General
The Synchronised Radio Link Reconfiguration Preparation procedure is used to prepare a new configuration of Radio Link(s) related to one Node B Communication Context.
The Synchronised Radio Link Reconfiguration Preparation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
8.3.2.2	Successful Operation

Figure 30: Synchronised Radio Link Reconfiguration Preparation procedure, Successful Operation
The Synchronised Radio Link Reconfiguration Preparation procedure is initiated by the CRNC by sending the RADIO LINK RECONFIGURATION PREPARE message to the Node B. The message shall use the Communication Control Port assigned for this Node B Communication Context.
Upon reception, the Node B shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications.
The Node B shall prioritise resource allocation for the RL(s) to be modified according to Annex A.
If the UE Aggregate Maximum Bit Rate IE is contained in the RADIO LINK RECONFIGURATION PREPARE message, the Node B shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE.
If the Improved Synchronized RRC Indicator IE is contained in the RADIO LINK RECONFIGURATION PREPARE message, the Node B may use this instruction to handle the improved synchronized RRC procedures.
DCH Modification:
If the RADIO LINK RECONFIGURATION PREPARE message includes any DCHs To Modify IE then the Node B shall treat them each as follows:
-	If the DCHs To Modify IE includes the Frame Handling Priority IE, the Node B should store this information for this DCH in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the radio interface in congestion situations within the Node B once the new configuration has been activated.
-	If the DCHs To Modify IE includes the Transport Format Set IE for the UL of a DCH, the Node B shall apply the new Transport Format Set in the Uplink of this DCH in the new configuration.
-	If the DCHs To Modify IE includes the TNL QoS IE for a DCH or a set of co-ordinated DCHs to be modified and if ALCAP is not used, the Node B may store this information for this DCH in the new configuration. The TNL QoS IE may be used to determine the transport bearer characteristics to apply in the uplink for the related DCH or set of co-ordinated DCHs.
-	If the DCHs To Modify IE includes the Transport Format Set IE for the DL of a DCH, the Node B shall apply the new Transport Format Set in the Downlink of this DCH in the new configuration.
-	If the DCHs To Modify IE includes the Allocation/Retention Priority IE for a DCH, the Node B shall apply the new Allocation/Retention Priority to this DCH in the new configuration according to Annex A.
-	If the DCHs To Modify IE includes multiple DCH Specific Info IEs, the Node B shall treat the DCHs in the DCHs to Modify IE as a set of co-ordinated DCHs. The Node B shall include these DCHs in the new configuration only if it can include all of them in the new configuration.
-	[FDD - If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH indicator IE set to "Uplink DCH only", the Node BNode B shall ignore the Transport Format Set IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.]
-	[FDD - If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH indicator IE set to "Downlink DCH only", the Node BNode B shall ignore the Transport Format Set IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.]
-	If the DCHs To Modify IE includes the UL FP Mode IE for a DCH or a DCH which belongs to a set of co-ordinated DCHs, the Node B shall apply the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
-	If the DCHs To Modify IE includes the ToAWS IE for a DCH or a DCH which belongs to a set of co-ordinated DCHs, the Node B shall apply the new ToAWS in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
-	If the DCHs To Modify IE includes the ToAWE IE for a DCH or a DCH which belongs to a set of co-ordinated DCHs, the Node B shall apply the new ToAWE in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
-	[TDD - If the DCHs To Modify IE includes the CCTrCH ID IE for the DL of a DCH to be modified, the Node B shall apply the new CCTrCH ID in the Downlink of this DCH in the new configuration.]
-	[TDD - If the DCHs To Modify IE includes the CCTrCH ID IE for the UL of a DCH to be modified, the Node B shall apply the new CCTrCH ID in the Uplink of this DCH in the new configuration.]
DCH Addition:
If the RADIO LINK RECONFIGURATION PREPARE message includes any DCHs To Add IEs then the Node B shall treat them each as follows:
-	If the DCHs To Add IE includes multiple DCH Specific Info IEs, the Node B shall treat the DCHs in the DCHs To Add IE as a set of co-ordinated DCHs. The Node B shall include these DCHs in the new configuration only if it can include all of them in the new configuration.
-	If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to "Uplink DCH only", the Node B shall ignore the Transport Format Set IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.
-	If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to "Downlink DCH only", the Node B shall ignore the Transport Format Set IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.
-	[FDD - For DCHs which do not belong to a set of co-ordinated DCHs with the QE-Selector IE set to "selected", the Transport channel BER from that DCH shall be the base for the QE in the UL data frames. If no Transport channel BER is available for the selected DCH, the Physical channel BER shall be used for the QE, ref. TS 25.427 [16]. If the QE-Selector IE is set to "non-selected", the Physical channel BER shall be used for the QE in the UL data frames, ref. TS 25.427 [16].]
-	For a set of co-ordinated DCHs, the Transport channel BER from the DCH with the QE-Selector IE set to "selected" shall be used for the QE in the UL data frames, ref. TS 25.427 [16]. [FDD - If no Transport channel BER is available for the selected DCH, the Physical channel BER shall be used for the QE, ref. TS 25.427 [16]. If all DCHs have the QE-Selector IE set to "non-selected", the Physical channel BER shall be used for the QE, ref. TS 25.427 [16].]
-	The Node B should store the Frame Handling Priority IE received for a DCH to be added in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the Uu interface in congestion situations within the Node B once the new configuration has been activated.
-	If the TNL QoS IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the Node B may store this information for this DCH in the new configuration. The TNL QoS IE may be used to determine the transport bearer characteristics to apply for the uplink between the Node B and the CRNC for the related DCH or set of co-ordinated DCHs.
-	The Node B shall use the included UL FP Mode IE for a DCH or a set of co-ordinated DCHs to be added as the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
-	The Node B shall use the included ToAWS IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Startpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
-	The Node B shall use the included ToAWE IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Endpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
-	[TDD - The Node B shall apply the CCTrCH ID IE (for the DL) in the Downlink of this DCH in the new configuration.]
-	[TDD - The Node B shall apply the CCTrCH ID IE (for the UL) in the Uplink of this DCH in the new configuration.]
DCH Deletion:
If the RADIO LINK RECONFIGURATION PREPARE message includes any DCHs To Delete IE, the Node B shall not include the referenced DCHs in the new configuration.
If all of the DCHs belonging to a set of co-ordinated DCHs are requested to be deleted, the Node B shall not include this set of co-ordinated DCHs in the new configuration.
[FDD – DCH Enhancements]:
[FDD - If the DCH Enhancements Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal is "Setup", then the Node B shall store the corresponding information  in the concerned Node B communication context, setup the requested DCH Enhancements operation [52], and:]
-	[FDD – Use the PO-SRB IE to set the power boost for the DL DPDCH in particular radio frames as defined in TS 25.214 [10].]
-	 [FDD – Use the DL_FET Mode IE to configure the DL FET mode [8, 52].]
-	[FDD – Use the information contained in the DL DCH Concatenation IE, if present, to identify the Transport Channels that shall be concatenated according to TS 25.212 [8].]
[FDD - If the DCH Enhancements Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal is "Configuration Change", then the Node B shall modify the corresponding information in the concerned Node B communication context, and: ]
-	 [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the PO-SRB IE, then the Node B shall use this value to to set the power boost for the DL DPDCH in particular radio frames as defined in TS 25.214 [10].]
-	 [FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the DL_FET Mode IE, then the Node B shall configure the DL FET mode accordingly [8, 52].]
-	[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the DL DCH Concatenation IE, then the Node B shall use the respective information to identify the Transport Channels to be concatenated according to TS 25.212 [8].]
[FDD - If the DCH Enhancements Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal is "Removal", then all DCH Enhancements Information shall be removed from the concerned Node B communications context.]
Physical Channel Modification:
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an UL DPCH Information IE, then the Node B shall apply the parameters to the new configuration as follows:]
-	[FDD - If the UL DPCH Information IE includes the Uplink Scrambling Code IE, the Node B shall apply this Uplink Scrambling Code to the new configuration.]
-	[FDD - If the UL DPCH Information IE includes the Min UL Channelisation Code Length IE, the Node B shall apply the value in the new configuration. The Node B shall apply the contents of the Max Number of UL DPDCHs IE (if it is included) in the new configuration.]
-	[FDD - If the UL DPCH Information IE includes the UL SIR Target IE, the Node B shall use the value for the UL inner loop power control when the new configuration is being used.]
-	[FDD - If the UL DPCH Information IE includes the Puncture Limit IE, the Node B shall apply the value in the uplink of the new configuration.]
-	[FDD - The Node B shall use the TFCS IE for the UL (if present) when reserving resources for the uplink of the new configuration. The Node B shall apply the new TFCS in the Uplink of the new configuration.]
-	[FDD - If the UL DPCH Information IE includes the UL DPCCH Slot Format IE, the Node B shall set the new Uplink DPCCH Structure to the new configuration.]
-	[FDD - If the UL DPCH Information IE includes the Diversity Mode IE, the Node B shall apply diversity according to the given value.]
-	[FDD - If the UL DPCH Information IE includes the UL DPDCH Indicator For E-DCH Operation IE and it is set to "UL DPDCH not present", the UL DPDCH resources shall be removed from the configuration.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the DL DPCH Information IE and the concerned Node B Communication Context is configured to use F-DPCH in the downlink in the old configuration, the Node B shall configure the concerned Node B Communication Context to use DPCH in the downlink in the new configuration.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the DL DPCH Power Information IE, the Node B shall use the information contained in it for the power settings of the DL DPCH. In particular, if the received Inner Loop DL PC Status IE is set to "Active", the Node B shall activate the inner loop DL power control for all RLs. If Inner Loop DL PC Status IE is set to "Inactive", the Node B shall deactivate the inner loop DL power control for all RLs according to ref. TS 25.214 [10].]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes a DL DPCH Information IE, the Node B shall apply the parameters to the new configuration as follows:]
-	[FDD - The Node B shall use the TFCS IE for the DL (if it is present) when reserving resources for the downlink of the new configuration. The Node B shall apply the new TFCS in the Downlink of the new configuration.]
-	[FDD - If the DL DPCH Information IE includes the TFCI Signalling Mode IE or the TFCI Presence IE, the Node B shall use the information when building TFCIs in the new configuration.]
-	[FDD - If the DL DPCH Information IE includes the DL DPCH Slot Format IE, the Node B shall set the new Downlink DPCH Structure to the new configuration.]
-	[FDD - If the DL DPCH Information IE includes the Multiplexing Position IE, the Node B shall apply the indicated multiplexing type in the new configuration.]
-	[FDD - If the DL DPCH Information IE includes the Limited Power Increase IE set to "Used", the Node B shall, if supported, use Limited Power Increase according to ref. TS 25.214 [10] subclause 5.2.1 for the inner loop DL power control in the new configuration.]
-	[FDD - If the DL DPCH Information IE includes the Limited Power Increase IE set to "Not Used", the Node B shall not use Limited Power Increase for the inner loop DL power control in the new configuration.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the F-DPCH Information IE, the Node B shall configure the concerned Node B Communication Context to use F-DPCH in the downlink in the new configuration.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Transmission Gap Pattern Sequence Information IE, the Node B shall store the new information about the Transmission Gap Pattern Sequences to be used in the new Compressed Mode Configuration. Any Transmission Gap Pattern Sequences already existing in the previous Compressed Mode Configuration are replaced by the new sequences once the new Compressed Mode Configuration has been activated or once the previous Compressed Mode Configuration has been deactivated. This new Compressed Mode Configuration shall be valid in the Node B until the next Compressed Mode Configuration is configured in the Node B or Node B Communication Context is deleted.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity DTX-DRX Information IE, then:]
-	[FDD - The Node B shall configure the concerned Node B Communication Context for DTX operation according to TS 25.214 [10].]
-	[FDD - If DRX Information IE is included in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].]
-	[FDD - If UE DRX Cycle 2 IE is included in the DRX Information IE in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].]
-	[FDD - If Inactivity Threshold for UE DRX Cycle 2 IE is included in the DRX Information IE in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then:]
-	[FDD - If the UE DTX DRX Offset IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the Node B shall apply the indicated Offset in UE DTX DRX Cycle IE in the new configuration.]
-	[FDD - If the Enabling Delay IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the Node B shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.214 [10].]
-	[FDD - If the DTX Information To Modify IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the Node B shall use this information to modify the indicated DTX Information parameter in the new configuration. If the choice of DTX Information To Modify IE is "Deactivate", then DRX should be deactived together with DTX.]
-	[FDD - If the DRX Information To Modify IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the Node B shall use this information to modify the indicated DRX Information in the new configuration.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity HS-SCCH less Information IE, then:]
-	[FDD - The Node B shall configure the Serving HS-DSCH Radio Link for Continuous Packet Connectivity HS-SCCH less operation in the new configuration according to TS 25.214 [10].]
-	[FDD - The Node B shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the Continuous Packet Connectivity HS-SCCH less Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If at least one of  HS-PDSCH Second Code Support IE is set to "True", then the Node B shall include HS-PDSCH Second Code Index IE in the RADIO LINK RECONFIGURATION READY message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE, then the Node B shall deactivate the Continuous Packet Connectivity HS-SCCH less operation for the HS-DSCH Radio Link.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity DRX Information LCR IE, then the Node B shall take account into these parameters to decide the DRX operation related parameters and configure the concerned Node B Communication Context for DRX operation according to TS 25.224 [21] and include the parameter(s) in the Continuous Packet Connectivity DRX Information Response LCR IE in the RADIO LINK RECONFIGURATION READY message.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity DRX Information To Modify LCR IE, then:]
-	[1.28 Mcps TDD - If the UE DTX DRX Offset IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the Node B shall apply the indicated Offset in UE DTX DRX Cycle IE in the new configuration.]
-	[1.28 Mcps TDD - If the Enabling Delay IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the Node B shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [21].]
-	[1.28 Mcps TDD - If the DRX Information To Modify IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the Node B shall use this information to modify the indicated DRX Information in the new configuration.]
-	[1.28 Mcps TDD - If the Inactivity Threshold for UE DRX Cycle Ext IE is included in the Continuous Packet Connectivity DRX Information LCR IE, then the Node B may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [21].]
-	[1.28 Mcps TDD - If the Enabling Delay Ext IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the Node B may use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [21].]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Semi-Persistent scheduling Information LCR IE, then:]
-	[1.28 Mcps TDD - The Node B shall configure the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [21].]
-	[1.28 Mcps TDD - The Node B shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the HS-DSCH Semi-Persistent scheduling Information Response LCR IE in the RADIO LINK RECONFIGURATION READY message.]
-	[1.28 Mcps TDD - If the HS-DSCH Semi-Persistent Resource Reservation Indicator IE is included in the HS-DSCH Semi-Persistent scheduling Information LCR IE, then the Node B shall include Allocated HS-PDSCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION READY message.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Semi-Persistent scheduling Information LCR IE, then:]
-	[1.28 Mcps TDD - The Node B shall configure the Serving E-DCH Radio Link indicated by the E-DCH Serving RL IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [21].]
	[1.28 Mcps TDD - If the E-DCH Semi-Persistent Resource Reservation Indicator IE is included in the E-DCH Semi-Persistent scheduling Information LCR IE, then the Node B shall include Allocated E-DCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION READY message.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Semi-Persistent scheduling Information to modify LCR IE, then:]
-	[1.28 Mcps TDD - If the Transport Block Size List IE or/and Repetition Period list IE is/are included in the HS-DSCH Semi-Persistent scheduling Information to modify LCR IE, the Node B shall modifiy the configuration of Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [21].
-	[1.28 Mcps TDD - If the Buffer Size for HS-DSCH Semi-Persistent scheduling IE is included in the HS-DSCH Semi-Persistent scheduling Information to modify LCR IE, the Node B shall use this information to modify the buffer size for HS-DSCH Semi-Persistent scheduling operation.
-	[1.28 Mcps TDD - If the Number of Processes for HS-DSCH Semi-Persistent scheduling IE is included in the HS-DSCH Semi-Persistent scheduling Information to modify LCR IE, the Node B shall use this information to allocate the number of processes for HS-DSCH Semi-Persistent scheduling operation.
-	[1.28 Mcps TDD - The Node B shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the HS-DSCH Semi-Persistent scheduling Information Response LCR IE in the RADIO LINK RECONFIGURATION READY message.]
-	[1.28 Mcps TDD - If the HS-DSCH Semi-Persistent Resource Reservation Indicator IE is included in the HS-DSCH Semi-Persistent scheduling Information to modify LCR IE, then the Node B shall include Allcoated HS-PDSCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION READY message.]
	[1.28 Mcps TDD - If the HS-DSCH Semi-Persistent scheduling operation Indicator IE is included in the HS-DSCH Semi-Persistent scheduling Information to modify LCR IE, then the Node B shall apply this information for HS-DSCH Semi-Persistent scheduling operation.]
-	[1.28 Mcps TDD - If the buffer size for HS-DSCH Semi-Persistent scheduling needs to be modified, then the Node B shall include the Buffer Size for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK RECONFIGURATION READY message.]
-	[1.28 Mcps TDD - If the number of processes for HS-DSCH Semi-Persistent scheduling needs to be modified, then the Node B shall include the Number of Processes for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK RECONFIGURATION READY message.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Semi-Persistent scheduling Information to modify LCR IE, then:]
-	[1.28 Mcps TDD - If the Repetition Period list IE is included in the E-DCH Semi-Persistent scheduling Information to modify LCR IE, the Node B shall modifiy the configuration of Serving E-DCH Radio Link indicated by the E-DCH Serving RL IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [21].
	[1.28 Mcps TDD - If the E-DCH Semi-Persistent scheduling Indicator IE is included in the E-DCH Semi-Persistent scheduling Information to modify LCR IE, then the Node B shall apply this information for E-DCH Semi-Persistent scheduling operation.]
-	[1.28 Mcps TDD - If the Semi-Persistent E-DCH releted E-HICH Information IE is included in the E-DCH Semi-Persistent scheduling Information to modify LCR IE, then the Node B shall use this information to modify the configuration of Semi-Persistent E-DCH releted E-HICH.]
-	[1.28 Mcps TDD - If the E-DCH Semi-Persistent Resource Reservation Indicator IE is included in the E-DCH Semi-Persistent scheduling Information to modify LCR IE, then the Node B shall include Allcoated E-DCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION READY message.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR IE, then the Node B shall deactivate the HS-DSCH Semi-Persistent scheduling operation for the HS-DSCH Radio Link.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Semi-Persistent scheduling Deactivate Indicator LCR IE, then the Node B shall deactivate the E-DCH Semi-Persistent scheduling operation for the E-DCH Radio Link.]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the MU-MIMO Information IE, then:]
-	[1.28 Mcps TDD - The Node B can activate MU-MIMO operation on Uplink and/or Downlink indicated by the MU-MIMO indicator IE and shall include the MU-MIMO Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[1.28 Mcps TDD - If the Standalone Midamble Channel Information IE is included in the MU-MIMO Information IE, then the Node B shall configure the concerned Node B Communication Context for standalone midamble related operation according to TS 25.224 [21].]
-	[1.28 Mcps TDD - If the Standalone Midamble Channel Information request IE is included in the MU-MIMO Information IE, if the Node B will use MU-MIMO and if the Node B can allocate the standalone midamble resource, then the Node B shall include the Standalone Midamble Channel Information IE in the MU-MIMO Information Response IE in the RADIO LINK RECONFIGURATION READY message, else the Node B shall not include the Standalone Midamble Channel Information IE in the MU-MIMO Information Response IE in the RADIO LINK RECONFIGURATION READY message].
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the MU-MIMO Information To Reconfigure IE, then:]
-	[1.28Mcps TDD - If the choice of MU-MIMO Information To Reconf  IE is "Modify", then the Node B shall use this information to modify the indicated MU-MIMO Information parameter in the new configuration.]
-	[1.28Mcps TDD - If the choice of MU-MIMO Information To Reconf  IE is "Continue", then the Node B shall continue using the old configuration for MU-MIMO operation.]
[FDD - E-DPCH Handling]:
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an E-DPCH Information IE, the Node B shall apply the parameters to the new configuration as follows:]
-	[FDD - If the E-DPCH Information IE includes the Maximum Set of E-DPDCHs IE, the Node B shall apply the contents of the Maximum Set in the new configuration.]
-	[FDD - If the E-DPCH Information IE includes the Puncture Limit IE, the Node B shall apply the value in the uplink of the new configuration]
-	[FDD - If the E-DPCH Information IE includes the E-TFCS Information IE, the Node B shall use the E-TFCS Information IE for the E-DCH when reserving resources for the uplink of the new configuration. The Node B shall apply the new TFCS in the uplink of the new configuration. If the E-TFCS Information IE contains the E-DCH Minimum Set E-TFCI IE the Node B shall use the value for the related resource allocation operation.]
-	[FDD - If the E-TFCS Information IE in the E-DPCH Information IE contains the E-DPDCH Power Interpolation IE, the Node B shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the E-DPDCH Power Interpolation IE is not present, the Node B shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10] if the E-DCH FDD Information IE is included in the RADIO LINK RECONFIGURATION PREPARE message.]
-	[FDD - If the E-TFCS Information IE in the E-DPCH Information IE contains the E-TFCI Boost Information IE, the Node B shall use the information according to TS 25.214 [10]. If the E-TFCI Boost Information IE is not present, the Node B shall use the E-TFCI BetaEC Boost value "127" in the algorithm defined in TS 25.214 [10] if the E-DCH FDD Information IE is included in the RADIO LINK RECONFIGURATION PREPARE message.]
-	[FDD - If the E-DPCH Information IE includes the E-TTI IE, the Node B shall use the value when the new configuration is being used.]
-	[FDD - If the E-DPCH Information IE includes the E-DPCCH Power Offset IE, the Node B shall use the value when the new configuration is being used.]
-	[FDD - If the E-DPCH Information IE includes the E-RGCH 2-Index-Step Threshold IE, the Node B shall use the value when the new configuration is being used.]
-	[FDD - If the E-DPCH Information IE includes the E-RGCH 3-Index-Step Threshold IE, the Node B shall use the value when the new configuration is being used.]
-	[FDD - If the E-DPCH Information IE includes the HARQ Info for E-DCH  IE, the Node B shall use the value when the new configuration is being used.]
-	[FDD - If the E-DPCH Information IE includes the HS-DSCH Configured Indicator IE, the Node B shall use the value when the new configuration is being used.]
-	[FDD - If the E-DPCH Information IE includes the Minimum Reduced E-DPDCH Gain Factor IE , then the Node B shall use the value to determine the applicable minimum gain factor (βed,k,reduced,min) defined in TS 25.214 [10]. For the case the Minimum Reduced E-DPDCH Gain Factor IE is not available for the Node B Communication Context, the Node B may use the default value defined in TS 25.331 [18].]
[TDD - UL/DL CCTrCH Modification]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes any UL CCTrCH to Modify or DL CCTrCH to Modify IE, then the Node B shall treat them each as follows:]
-	[TDD - If the IE includes any of the TFCS IE, TFCI coding IE or Puncture Limit IE, the Node B shall apply these as the new values, otherwise the old values specified for this CCTrCH are still applicable.]
-	[TDD - If the IE includes any UL DPCH To Add IE, UL DPCH To Add LCR IE, UL DPCH To Add 7.68Mcps IE, DL DPCH To Add 7.68Mcps IE, DL DPCH To Add LCR IE, or DL DPCH To Add IE, the Node B shall include this DPCH in the new configuration.]
-	[TDD - If the IE includes any UL DPCH To Delete IE or DL DPCH To Delete IE, the Node B shall remove this DPCH in the new configuration.]
-	[TDD - If the IE includes any UL DPCH To Modify IE or DL DPCH To Modify IE and includes any of the Repetition Period IE, Repetition Length IE or TDD DPCH Offset IE, or the message includes UL/DL Timeslot Information and includes any of the [3.84Mcps TDD - Midamble Shift And Burst Type IE], [1.28Mcps TDD - Midamble Shift LCR IE], [7.68Mcps TDD - Midamble Shift And Burst Type 7.68Mcps IE], or TFCI Presence IE or the message includes UL/DL Code information and includes [3.84Mcps TDD - TDD Channelisation Code IE], [1.28Mcps TDD - TDD Channelisation Code LCR IE] , [7.68Mcps TDD - TDD Channelisation Code 7.68Mcps IE], [1.28Mcps TDD - TDD UL DPCH Time Slot Format LCR IE or TDD DL DPCH Time Slot Format LCR IE], the Node B shall apply these specified information elements as the new values, otherwise the old values specified for this DPCH configuration are still applicable.]
-	[1.28Mcps TDD - If the UL CCTrCH To Modify IE includes the UL SIR Target IE, the Node B shall use the value for the UL inner loop power control according to TS 25.221 [19] and TS 25.224 [21] when the new configuration is being used.]
-	[1.28Mcps TDD - If the UL CCTrCH to Modify IE includes the TDD TPC UL Step Size IE, the Node B shall apply this value to the uplink TPC step size in the new configuration.]
-	[TDD - If the DL CCTrCH to Modify IE includes the TDD TPC DL Step Size IE, the Node B shall apply this value to the downlink TPC step size in the new configuration.]
-	[1.28Mcps TDD - If the DL DPCH To Modify Per RL IE includes the TDD TPC DL Step Size IE and the RL ID IE in the DL DPCH To Modify Per RL IE is same as the HS-PDSCH RL ID IE , the Node B shall apply this value to the HS-SCCH TPC step size in the new configuration.]
-	[1.28Mcps TDD - If the UL Timeslot Information LCR IE includes the PLCCH Information IE, the Node B shall delete / add / modify  the PLCCH assignment according to the content when the new configuration is used.]
[TDD - UL/DL CCTrCH Addition]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes any UL CCTrCH To Add IE or DL CCTrCH To Add IE, the Node B shall include this CCTrCH in the new configuration.]
[TDD - If the UL/DL CCTrCH To Add IE includes any [3.84Mcps TDD - UL/DL DPCH Information IE] [1.28Mcps TDD - UL/DL DPCH Information LCR IE] [7.68Mcps TDD - TDD Channelisation Code 7.68Mcps IE], the Node B shall reserve necessary resources for the new configuration of the UL/DL DPCH(s) according to the parameters given in the message.]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes TDD TPC DL Step Size IE within a DL CCTrCH To Add IE, the Node B shall set the downlink TPC step size of that CCTrCH to that value, otherwise the Node B shall set the TPC step size of that CCTrCH to the same value as the lowest numbered DL CCTrCH in the current configuration.]
[1.28Mcps TDD - If the UL CCTrCH To Add IE includes the TDD TPC UL Step Size IE, the Node B shall apply the uplink TPC step size in the new configuration.]
[1.28Mcps TDD - The Node B shall use the UL SIR Target IE in the UL CCTrCH To Add IE as the UL SIR value for the inner loop power control for this CCTrCH according to TS 25.221 [19] and TS 25.224 [21] in the new configuration.]
[1.28Mcps TDD - If the DL DPCH To Add Per RL IE includes the TDD TPC DL Step Size IE and the RL ID IE in the DL DPCH To Add Per RL IE is same as the HS-PDSCH RL ID IE , the Node B shall apply this value to the HS-SCCH TPC step size in the new configuration. If no TDD TPC DL Step Size IE is included in the DL DPCH To Add Per RL IE, the value of HS-SCCH TPC Step Size IE should applied to the HS-SCCH TPC step size in the new configuration.]
[1.28Mcps TDD - If the UL Timeslot Information LCR IE includes the PLCCH Information IE, the Node B shall add the PLCCH assignment when the new configuration is used.]
[TDD - UL/DL CCTrCH Deletion]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes any UL or DL CCTrCH to be deleted , the Node B shall remove this CCTrCH in the new configuration.]
[FDD - UL CLTD Setup:]
[FDD - If the UL CLTD Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL CLTD is "Setup", then: the Node B shall setup the requested UL CLTD resources for the concerned Node B Communication Context in the cell to determine the precoding weights according the new configuration defined in the UL CLTD Information IE and then:]
-	[FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the concerned Node B Communication Context, the C-ID IE shall be included in the UL CLTD Information IE, and the Node B shall configure this cell to determine the precoding weights for the concerned Node B Communication Context.] 
-	[FDD - If the UL CLTD Activation Information IE is included in the UL CLTD Information IE, then the Node B shall use this value to configure the state of UL CLTD for the concerned Node B Communication Context.]
[FDD – UL CLTD Modification:]
[FDD - If the UL CLTD Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL CLTD is "Configuration Change", then: the UL CLTD Information To Modify IE defines the new configuration and then:]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the C-ID IE in the UL CLTD Information To Modify IE, then the Node B shall configure this cell to determine the precoding weights for the concerned Node B Communication Context.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the S-DPCCH Power Offset Information IE in the UL CLTD Information To Modify IE, then the Node B shall use this value to determine the S-DPCCH power.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the UL CLTD Activation Information IE in the UL CLTD Information To Modify IE, then the Node B shall use this value to update the local state of UL CLTD for the concerned Node B Communication Context. If the UL CLTD Activation Information IE is set to "De-activated", the Node B should release the F-TPICH resource configured for the concerned Node B Communication Context.]
[FDD - UL CLTD Removal:]
[FDD - If the UL CLTD Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL CLTD is "Removal", then the configured UL CLTD for the concerned Node B Communication Context shall be removed.]
[FDD - UL MIMO Setup:]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the UL MIMO Information IE in the E-DCH FDD Information IE, or the UL MIMO Reconfiguration IE and the choice of Setup, Configuration Change or Removal of UL MIMO is "Setup", then the Node B shall activate UL MIMO operation for the radio link according to the information provided in the IE.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Serving E-DCH RL IE indicating that the Serving E-DCH RL is in this Node B:]
-	[FDD - The Node B shall allocate a Secondary Transport Block E-RNTI for the corresponding RL and include the E-RNTI identifier together with the corresponding E-ROCH Channelization Code in the UL MIMO DL Control Channel Information IE in the RADIO LINK RECONFIGURATION READY. The E-ROCH Channelization code shall be allocated from the pool of E-AGCH channelization codes configured for that cell.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-ROCH Power Offset IE in the UL MIMO Information IE, then the Node B may use this value to determine the E-ROCH power. The E-ROCH Power Offset should be applied for any E-ROCH transmission to this UE.]
-	[FDD - The Node B may include the the Secondary Transport Block E-HICH Signature Sequence IE in UL MIMO DL Control Channel Information IE in the RADIO LINK RECONFIGURATION READY message for every RL indicated by the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE and it should include it for the Serving E-DCH RL.]
[FDD – UL MIMO Modification:]
[FDD - If the UL MIMO Reconfiguration IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL MIMO is "Configuration Change", then the UL MIMO Information To Modify IE defines the new configuration.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Serving E-DCH RL IE:]
-	[FDD – If the old Serving E-DCH RL is in this Node B, the Node B shall de-allocate the E-ROCH resources of the old Serving E-DCH RL at the activation of the new configuration.]
- 	[FDD - If the new Serving E-DCH RL is in this Node B:]
-	[FDD - The Node B shall allocate a Secondary Transport Block E-RNTI for the corresponding RL and include the E-RNTI identifier together with the corresponding E-ROCH Channelization Code in the UL MIMO DL Control Channel Information IE in the RADIO LINK RECONFIGURATION READY. The E-ROCH Channelization code shall be allocated from the pool of E-AGCH channelization codes configured for that cell.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-ROCH Power Offset IE in the UL MIMO Information To Modify IE, then the Node B may use this value to determine the E-ROCH power. The E-ROCH Power Offset should be applied for any E-ROCH transmission to this UE.]
-	[FDD - The Node B may include the the Secondary Transport Block E-HICH Signature Sequence IE or it may alternatively include the Secondary Transport Block E-HICH Release Indicator IE in UL MIMO DL Control Channel Information IE in the RADIO LINK RECONFIGURATION READY message for every RL indicated by the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE and it should include it for the Serving E-DCH RL.]
[FDD - UL MIMO Removal:]
[FDD - If the UL MIMO Reconfiguration IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL MIMO is "Removal", then the configured UL MIMO for the concerned Node B Communication Context shall be removed.]
DL Power Control:
-	[FDD - If the RL Information IE includes the DL Reference Power IEs and the power balancing is active, the Node B shall update the reference power of the power balancing in the indicated RL(s), if updating of power balancing parameters by the RADIO LINK RECONFIGURATION PREPARE message is supported, when the new configuration has been activated, according to subclause 8.3.7, using the DL Reference Power IE. If the CFN modulo the value of the Adjustment Period IE is not equal to 0, the power balancing continues with the old reference power until the end of the current adjustment period, and the updated reference power shall be used from the next adjustment period.]
[FDD - If updating of power balancing parameters by the RADIO LINK RECONFIGURATION PREPARE message is supported by the Node B, the Node B shall include the DL Power Balancing Updated Indicator IE in the RL Information Response IE for each affected RL in the RADIO LINK RECONFIGURATION READY message.]
[TDD - DSCH Addition/Modification/Deletion]:
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes any DSCH To Add, DSCH To Modify or DSCH To Delete IE, then the Node B shall use this information to add/modify/delete the indicated DSCH channels to/from the radio link, in the same way as the DCH info is used to add/modify/release DCHs.]
[TDD - The Node B shall include in the RADIO LINK RECONFIGURATION READY message both the Transport Layer Address IE and the Binding ID IE for the transport bearer to be established for each DSCH.]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the TNL QoS IE in the DSCH TDD Information IE and if ALCAP is not used, the Node B may use the TNL QoS IE to determine the transport bearer characteristics to apply in the uplink for the related DSCH.]
[TDD - USCH Addition/Modification/Deletion]:
-	[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes USCH information for the USCHs to be added/modified/deleted then the Node B shall use this information to add/modify/delete the indicated USCH channels to/from the radio link, in the same way as the DCH info is used to add/modify/release DCHs.]
-	[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes USCH information for the USCHs to be added/modified, if the TNL QoS IE is included and if ALCAP is not used, the Node B may use the TNL QoS IE to determine the transport bearer characteristics to apply between the Node B and the CRNC for the related USCHs.]
-	[TDD - The Node B shall include in the RADIO LINK RECONFIGURATION READY message both the Transport Layer Address IE and the Binding ID IE for the transport bearer to be established for each USCH.]
RL Information:
If the RADIO LINK RECONFIGURATION PREPARE message includes the RL Information IE, the Node B shall treat it as follows:
-	[FDD - When more than one DL DPDCH are assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to TS 25.212 [8]. When p number of DL DPDCHs are assigned to each RL, the first pair of DL Scrambling Code and FDD DL Channelisation Code Number corresponds to "PhCH number 1", the second to "PhCH number 2", and so on until the pth to "PhCH number p".]
-	[FDD - If the RL Information IE includes a DL Code Information IE, the Node B shall apply the values in the new configuration.]
-	[FDD - If the RL Information IE contains the Transmission Gap Pattern Sequence Code Information IE in the DL Code Information IE for any of the allocated DL Channelisation Codes, the Node B shall apply the alternate scrambling code as indicated whenever the downlink compressed mode method SF/2 is active in the new configuration.]
-	[FDD - If the RL Information IE includes the Maximum DL Power and/or the Minimum DL Power IEs, the Node B shall apply the values in the new configuration. During compressed mode, the IPcurr, as described in ref. TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.]
-	[3.84 Mcps TDD and 7.68Mcps TDD - If the DL CCTrCH To Add IE is included, the Node B shall determine the maximum CCTrCH DL power for the DCH type CCTrCH by the following rule: If the CCTrCH Maximum DL Transmission Power IE is included for that CCTrCH, then the Node B shall use that power for the maximum CCTrCH DL power, otherwise the maximum CCTrCH DL power is the Maximum Downlink Power IE included in the RL Information IE. If no Maximum Downlink Power IE is included (even if CCTrCH Maximum DL Transmission Power IEs are included), any maximum DL power stored for already existing DCH type CCTrCHs for this Node B Communication Context shall be applied.]
-	[3.84 Mcps TDD and 7.68Mcps TDD - If the DL CCTrCH To Add IE is included, the Node B shall determine the minimum CCTrCH DL power for the DCH type CCTrCH by the following rule: If the CCTrCH Minimum DL Transmission Power IE is included for that CCTrCH, then the Node B shall use that power for the minimum CCTrCH DL power, otherwise the minimum CCTrCH DL power is the Minimum Downlink Power IE included in the RL Information IE. If no Minimum Downlink Power IE is included (even if CCTrCH Minimum DL Transmission Power IEs are included), any minimum DL power stored for already existing DCH type CCTrCHs for this Node B Communication Context shall be applied.]
-	[3.84 Mcps TDD and 7.68Mcps TDD - If the DL CCTrCH To Modify IE is included and Maximum CCTrCH DL Power to Modify IE and/or Minimum CCTrCH DL Power to Modify IE are included, the Node B shall apply the values in the new configuration for this DCH type CCTrCH. If the RL Information IE includes Maximum Downlink Power and/or the Minimum Downlink Power IEs, the Node B shall apply the values for all other DCH type CCTrCHs of the radio link.]
-	[1.28 Mcps TDD - If the DL CCTrCH To Add IE is included, the Node B shall determine the maximum DL power for each timeslot within a DCH type CCTrCH by the following rule: If the Maximum DL Power IE is included in the DL Timeslot Information LCR IE for that timeslot, then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the Maximum Downlink Power IE included in the RL Information IE. The Node B shall store this value and not transmit with a higher power on any applicable DL DPCH. If no Maximum Downlink Power IE is included, any maximum DL power stored for already existing timeslots for this Node B Communication Context shall be applied.]
-	[1.28 Mcps TDD - If the DL CCTrCH To Add IE is included, the Node B shall determine the minimum DL power for each timeslot within a DCH type CCTrCH by the following rule: If the Minimum DL Power IE is included in the DL Timeslot Information LCR IE for that timeslot, then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the Minimum Downlink Power IE included in the RL Information IE. The Node B shall store this value and not transmit with a lower power on any applicable DL DPCH. If no Minimum Downlink Power IE is included, any minimum DL power stored for already existing timeslots for this Node B Communication Context shall be applied.]
-	[1.28 Mcps TDD - If the DL CCTrCH To Modify IE is included and Maximum DL Power to Modify LCR IE and/or Minimum DL Power to Modify LCR IE are included, the Node B shall apply the values in the new configuration for this timeslot, if the RL Information IE includes Maximum Downlink Power and/or the Minimum Downlink Power IEs, the Node B shall apply the values in the new configuration for all other timeslots.]
-	[3.84Mcps TDD and 7.68Mcps TDD - If the RL Information IE includes the Initial DL Transmission Power IE, the Node B shall determine the initial CCTrCH DL power for each DCH type CCTrCH by the following rule: If the CCTrCH Initial DL Transmission Power IE is included for that CCTrCH, then the Node B shall use that power for the initial CCTrCH DL power, otherwise the initial CCTrCH DL power is the Initial DL Transmission Power IE included in the RL Information IE. The Node B shall apply the determined initial CCTrCH DL power to the transmission on each DPCH of the CCTrCH when starting transmission on a new CCTrCH until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no Initial DL Transmission Power IE is included with a new CCTrCH (even if CCTrCH Initial DL Transmission Power IEs are included), the Node B shall use any transmission power level currently used on already existing CCTrCHs when starting transmission for a new CCTrCH. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 4.2.3.4).]
-	[3.84Mcps TDD and 7.68Mcps TDD - The initial power, maximum power, and minimum power for a DSCH type CCTrCH to be added or modified, shall be determined as follows:
-	If the DSCH type CCTrCH is paired with an uplink CCTrCH(s) for inner loop power control, the minimum, maximum and initial power for each PDSCH is determined in the same way as described above for DCH type CCTrCHs.
-	If the DSCH type CCTrCH is not paired with an uplink CCTrCH(s) for inner loop power control, the PDSCH transmission power is DSCH Data Frame Protocol signalled (TS 25.435 [24]), with the maximum value determined in the same way as described above for DCH type CCTrCHs. The minimum and initial powers, however, are subject to control by the CRNC via the frame protocol].
-	[1.28 Mcps TDD - If the RL Information IE includes the Initial DL Transmission Power IE, the Node B shall determine the initial DL power for each timeslot in a DCH type CCTrCH by the following rule: If the Initial DL Transmission Power IE is included in the DL Timeslot Information LCR IE, then the Node B shall use that power for the initial DL power, otherwise the initial DL power is the Initial DL Transmission Power IE included in the RL Information IE. The Node B shall apply the given power to the transmission on each DL DPCH and on each Time Slot of the CCTrCH when starting transmission until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no Initial DL Transmission Power IE is included, the Node B shall use any transmission power level currently used on already existing timeslots for this Node B Communication Context. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4).]
-	[1.28Mcps TDD - If the RL Information IE includes the Initial DL Transmission Power IE, the Node B shall determine the initial DL power for each timeslot within the DSCH type CCTrCH by the following rule: If both the CCTrCH Initial DL Transmission Power IE and the DL Time Slot ISCP Info LCR IE are included then the Node B shall use that power for the PDSCH power, otherwise the PDSCH power is the Initial DL Transmission Power IE included in the RL Information IE. If DL Time Slot ISCP info LCR IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged.  The Node B shall apply the given power to the transmission on each PDSCH and on each timeslot of the CCTrCH when starting transmission on a new CCTrCH until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no Initial DL Transmission Power IE is included with a new CCTrCH (even if CCTrCH Initial DL Transmission Power IEs are included), the Node B shall use any transmission power level currently used on already existing RL/timeslots when starting transmission for a new CCTrCH. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4).]
-	[1.28 Mcps TDD - If the DL CCTrCH To Add IE is included, the Node B shall determine the maximum DL power for each timeslot within a DSCH type CCTrCH by the following rule: If the CCTrCH Maximum DL Transmission Power IE is included then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the Maximum Downlink Power IE included in the RL Information IE. The Node B shall store this value and not transmit with a higher power on any applicable DL PDSCH. If no Maximum Downlink Power IE is included, any maximum DL power stored for already existing timeslots for this Node B Communication Context shall be applied.]
-	[1.28 Mcps TDD - If the DL CCTrCH To Add IE is included, the Node B shall determine the minimum DL power for each timeslot within a DSCH type CCTrCH by the following rule: If the CCTrCH Minimum DL Transmission Power IE is included then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the Minimum Downlink Power IE included in the RL Information IE. The Node B shall store this value and not transmit with a lower power on any applicable DL PDSCH. If no Minimum Downlink Power IE is included, any minimum DL power stored for already existing timeslots for this Node B Communication Context shall be applied.]
-	[1.28 Mcps TDD - If the DL CCTrCH To Modify IE is included and the Maximum CCTrCH DL Power to Modify IE and/or the Minimum CCTrCH DL Power to Modify IE are included, the Node B shall apply the values in the new configuration for this DSCH type CCTrCH, if the RL Information IE includes Maximum Downlink Power and/or the Minimum Downlink Power IEs, the Node B shall apply the values in the new configuration for all other timeslots.]
-	[FDD - If the RL Information IE includes the DL DPCH Timing Adjustment IE, the Node B shall adjust the timing of the radio link accordingly in the new configuration.]
-	[1.28Mcps TDD - If the RL Information IE message contains the Uplink Synchronisation Parameters LCR  IE, the Node B shall use the indicated values of Uplink Synchronisation Stepsize IE and Uplink Synchronisation Frequency IE when evaluating the timing of the UL synchronisation.]
-	[FDD - If the RL Information IE includes the F-DPCH Slot Format IE and if the Node B Communication Context is configured to use F-DPCH in the downlink, then the Node B shall use this information to configure the F-DPCH slot format of each RL according to TS 25.211 [7].] 
-	[FDD - If the RL Information IE includes the F-TPICH Information Reconf IE and the choice of Setup, Configuration Change or Removal of F-TPICH Information is "Setup", then the Node B shall use the information in F-TPICH Information IE to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214[10].]
-	[FDD - If the RL Information IE includes the F-TPICH Information Reconf IE and the choice of Setup, Configuration Change or Removal of F-TPICH Information is "Configuration Change", then: the F-TPICH Information To Modify IE defines the new configuration and then:]
-	[FDD - If the F-TPICH Information To Modify IE includes the F-TPICH Slot Format IE, then the Node B shall use this information to configure the F-TPICH slot format according to TS 25.211 [7].
-	[FDD - If the F-TPICH Information To Modify IE includes the F-TPICH Offset IE, the Node B shall use this information to configure the time offset of F-TPICH.]
-	[FDD - If the F-TPICH Information To Modify IE includes the F-TPICH Channelisation Code Number IE, the Node B shall use this information to configure the channelization code of F-TPICH.]
-	[FDD - If the RL Information IE includes the F-TPICH Information Reconf IE and the choice of Setup, Configuration Change or Removal of F-TPICH Information is "Removal", then the Node B shall remove the configured F-TPICH for the RL.]
[TDD - PDSCH RL ID]:
-	[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the PDSCH RL ID IE then in the new configuration the Node B shall use the PDSCH and/or PUSCH in this radio link.]
Signalling bearer rearrangement:
If the RADIO LINK RECONFIGURATION PREPARE message includes the Signalling Bearer Request Indicator IE the Node B shall allocate a new Communication Control Port for the control of the Node B Communication Context and include the Target Communication Control Port ID IE in the RADIO LINK RECONFIGURATION READY message.
HS-DSCH Setup:
If the HS-DSCH Information IE is present in the RADIO LINK RECONFIGURATION PREPARE message, then:
-	The Node B shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE.
-	The Node B shall include the HARQ Memory Partitioning IE in the [FDD - HS-DSCH FDD Information Response IE] [TDD - HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION READY message. [FDD - The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than "8", if the MIMO Activation Indicator IE, or the MIMO with four transmit antennas Activation Indicator IE, or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Information IE.] [1.28Mcps TDD- The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than "8", if the MIMO Activation Indicator IE is included in the HS-DSCH Information IE.]
-	If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-hs Guaranteed Bit Rate IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
-	If the RADIO LINK RECONFIGURATION PREPARE message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
-	If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue.
-	[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the Puncturing Handling in First Rate Matching Stage IE in the HS-DSCH Information IE , then the Node B shall , if supported, apply the puncturing during first stage rate matching according to the Puncturing Handling in First Rate Matching Stage IE.]
-	The Node B shall include the HS-DSCH Initial Capacity Allocation IE in the [FDD - HS-DSCH FDD Information Response IE] [TDD - HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION READY message for every HS-DSCH MAC-d flow being established, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK RECONFIGURATION PREPARE message includes  HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH  Information IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer received in RADIO LINK RECONFIGURATION PREPARE in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE for a Priority Queue including  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE.
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-SCCH Power Offset IE in the HS-DSCH Information IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Measurement Power Offset IE in the HS-DSCH Information IE, then the Node B shall use the measurement power offset as described in ref TS 25.214 [10], subclause 6A.2.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - HS-SCCH Specific Information Response IE] [1.28Mcps TDD - HS-SCCH Specific Information Response LCR IE] [7.68Mcps TDD - HS-SCCH Specific Information Response 7.68Mcps IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HARQ Preamble Mode IE in the HS-DSCH Information IE, then the Node B shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the Node B shall include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION READY message. If the HARQ Preamble Mode IE is not included or if the mode 0 is applied, then the Node B shall not include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-SICH SIR Target IE in the HS-DSCH Information IE, the Node B shall use this value to determine the HS-SICH SIR Target. The HS-SICH SIR Target IE indicates the received UL SIR target of HS-SICH NACK for this UE.]
-	If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH MAC-d PDU Size Format  IE in the HS-DSCH  Information IE, then the Node B shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]).
-	If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.
-	[FDD - If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B shall activate the MIMO mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B may if the value is set to "allowed" use 64 QAM for the HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE with value set to "not allowed", then the Node B shall not use 64 QAM for the HS-DSCH Radio Link.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH MAC-d PDU Size Format IE set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - If the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH FDD Information IE, then the Node B may use:]
-	 [FDD -  a different HS-SCCH in consecutive TTIs for this UE]
-	 [FDD - HS-SCCH orders for the case of HS-SCCH-less operation to this UE]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE the Node B may use the supported HSDPA functions for this UE.]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the Node B shall, if supported,  include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK RECONFIGURATION PREPARE message includes the Number of Supported Carriers IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B shall use this information to allocate HSDPA resources over multiple frequencies for UE.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK RECONFIGURATION PREPARE message includes the Multi-carrier HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B shall use this information together with the HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information IE to allocate HSDPA resources over multiple carriers for the UE.]
- 	[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B may use this information in HSDPA resources allocation for the UE.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH over multiple frequencies and include the HS-SCCH Specific Information Response LCR per UARFCN IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B shall include the HARQ Memory Partitioning per UARFCN IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B may indicate the number of multiple frequencies actually used by the UE and include the Multi-Carrier number IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
	[1.28 Mcps TDD - If the MIMO Activation Indicator IE is included in the HS-DSCH TDD Information IE, then, the Node B shall activate the MIMO mode for the HS-DSCH Radio Link, decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	If the RADIO LINK RECONFIGURATION PREPARE message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DL RLC PDU Size Format IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24].
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the Priority Queue Information IE in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the Node B shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]
-	[FDD - If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B shall activate the Single Stream MIMO mode for the HS-DSCH Radio Link.]
-	[FDD - If the MIMO with four transmit antennas Activation Indicator IE or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD – The Node B may include Precoder weight set restriction IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the CQI Feedback Cycle2 k IE and the CQI Cycle Switch Timer IE  is included in HS-DSCH FDD Information IE, then the Node B may use the indicated CQI Feedback Cycle2 k value, the CQI Cycle Switch Timer in HSDPA resources allocation for the UE.]
[FDD – Secondary Serving HS-DSCH Setup:]
[FDD – If the C-ID IE is present in the Additional HS Cell Information RL Reconf Prep IE in the RADIO LINK RECONFIGURATION PREPARE message, and no secondary serving HS-DSCH Radio Link(s) has been configured in the Node B or if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the Ordinal Number Of Frequency IEs, in the HS-DSCH FDD Secondary Serving Information IE or in the HS-DSCH FDD Secondary Serving Information To Modify IE for each instance of the Additional HS Cell Information RL Reconf Prep IE, indicate that new secondary serving HS-DSCH Radio Link(s) shall be setup, then:]
-	[FDD – The Node B shall setup the requested HS-PDSCH resources on the secondary serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-SCCH Power Offset IE in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE,, then the Node B shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
-	[FDD - If, in the new configuration, the concerned Node B Communication Context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH Radio Link, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - If the Diversity Mode IE is included  in the HS-DSCH FDD Secondary Serving Information IE, the Node B shall apply cell specific transmit diversity configuration and if the Diversity Mode IE is not set to "None" the Node B shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE.]
-	[FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.]
-	[FDD - If the MIMO with four transmit antennas Activation Indicator IE or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD – The Node B may include Precoder weight set restriction IE the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
Intra-Node B Serving HS-DSCH Radio Link Change:
If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-PDSCH RL ID IE, this indicates the new Serving HS-DSCH Radio Link:
-	In the new configuration the Node B shall de-allocate the HS-PDSCH resources of the old Serving HS-PDSCH Radio Link and allocate the HS-PDSCH resources for the new Serving HS-PDSCH Radio Link.
-	The Node B may include the HARQ Memory Partitioning IE in the [FDD - HS-DSCH FDD Information Response IE] [TDD - HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION READY message. [FDD - The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.] [1.28Mcps TDD- The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - HS-SCCH Specific Information Response IE] [1.28Mcps TDD - HS-SCCH Specific Information Response LCR IE] [7.68Mcps TDD - HS-SCCH Specific Information Response 7.68Mcps IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.
-	If a reset of the MAC-hs is not required the Node B shall include the MAC-hs Reset Indicator IE in the RADIO LINK RECONFIGURATION READY message.
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH Information To Modify IE and the value is set to "allowed" or if HS-DSCH Information To Modify IE is not included and the Node B Communication Context is configured with Sixtyfour QAM allowed for the serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM in the new configuration, then it shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD – The Node B may include Precoder weight set restriction IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
[FDD – Intra-Node B Secondary Serving HS-DSCH Radio Link Change:]
[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the C-ID IE and the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Prep IE, one or more secondary serving HS-DSCH Radio Link(s) has been configured in the Node B and if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the Ordinal Number Of Frequency IEs, in the HS-DSCH FDD Secondary Serving Information IE for each instance of the Additional HS Cell Information RL Reconf Prep IE, indicate that existing secondary serving HS-DSCH Radio Links shall be subject to intra-Node B secondary serving HS-DSCH Radio Link change then the HS-PDSCH RL ID IE indicates the new secondary serving HS-DSCH Radio Link:]
-	[FDD - In the new configuration the Node B shall de-allocate the HS-PDSCH resources of the old secondary serving HS-PDSCH Radio Link and allocate the HS-PDSCH resources for the new secondary serving HS-PDSCH Radio Link. The Node B shall remove the old secondary serving HS-PDSCH Radio Link if no E-DCH resources are allocated to the RL. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
-	[FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE and the value is set to "allowed" or if HS-DSCH FDD Secondary Serving Information To Modify IE is not included and the Node B Communication Context is configured with Sixtyfour QAM allowed for the secondary serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM for the new secondary serving HS-DSCH Radio Link, then it shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If, in the new configuration, the concerned Node B Communication Context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH Radio Link, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - If the old and/or new configuration contains more than one Secondary Serving HS-DSCH Radio Link the HS-DSCH FDD Secondary Serving Information IE defines the new secondary serving HS-DSCH configuration in the Node B to be used on the new secondary serving HS-DSCH Radio Link, and then:]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-SCCH Power Offset IE in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
-	[FDD - If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
-	[FDD - If the Diversity Mode IE is included in the HS-DSCH FDD Secondary Serving Information IE, the Node B shall apply cell specific transmit diversity configuration and if the Diversity Mode IE is not set to "None" the Node B shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE.]
-	[FDD - If the MIMO with four transmit antennas Activation Indicator IE or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD – The Node B may include the Precoder weight set restriction IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
[FDD - Additional Serving E-DCH Radio Link Change to an existing additional non serving E-DCH RL:]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the C-ID IE in the Additional HS Cell Information RL Reconf Prep IE and an additional non serving E-DCH RL exists in the cell indicated by the C-ID IE, the HS-PDSCH RL ID IE in the Additional HS Cell Information RL Reconf Prep IE indicates the new Additional Serving E-DCH Radio Link.]
-	[FDD - If the old Additional Serving E-DCH RL is within this Node B, the Node B shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the E-DCH FDD DL Control Channel Information IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message for the initial grant for the Additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD -The Node B may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message for every E-DCH Radio Links on secondary UL frequency in the Node B.]
[FDD - Additional Serving E-DCH Radio Link Change to a new RL:]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Additional E-DCH RL Specific Information To Add IE in the Additional E-DCH Configuration Change Information IE in the Additional E-DCH Cell Information RL Reconf Prep IE and the C-ID IE in the Additional HS Cell Information RL Reconf Prep IE and there is no radio links in the cell indicated by the C-ID IE for the Node B Communication Context, the HS-PDSCH RL ID IE indicates the new Additional Serving E-DCH Radio Link on secondary UL frequency.]
-	[FDD - If the old Additional Serving E-DCH RL is within this Node B, the Node B shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.]
-	[FDD - In the new configuration the Node B shall allocate the E-DCH resources for the new additional serving E-DCH Radio Link on the secondary UL frequency. Non cell specific E-DCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - The Node B may include in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message.]
HS-DSCH Modification:
If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Information To Modify IE, then:
-	The Node B shall include the HS-DSCH Initial Capacity Allocation IE for every HS-DSCH MAC-d flow being modified for which the establishment of one or several new Priority Queues was requested, if the Node B allows the CRNC to start the transmission of MAC-d PDUs for the Priority Queue(s) being established before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK RECONFIGURATION PREPARE message includes HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information To Modify IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer received in RADIO LINK RECONFIGURATION PREPARE in the HS-DSCH Information To Modify IE for a Priority Queue including  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE.
-	If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-hs Guaranteed Bit Rate IE in the HS-DSCH Information To Modify IE, the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
-	If the RADIO LINK RECONFIGURATION PREPARE message includes the Discard Timer IE for a Priority Queue in the HS-DSCH Information To Modify IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
-	If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH Information To Modify IE, then the Node B shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue.
-	If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-hs Window Size IE or T1 IE in the HS-DSCH Information To Modify IE, then the Node B shall use the indicated values in the new configuration for the related HSDPA Priority Queue.
-	If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-d PDU Size Index IE in the Modify Priority Queue choice, the Node B shall delete the previous list of MAC-d PDU Size Index values for the related HSDPA Priority Queue and use the MAC-d PDU Size Index values indicated in the MAC-d PDU Size Index IE in the new configuration.
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the CQI Feedback Cycle k IE, the CQI Repetition Factor IE , the ACK-NACK Repetition Factor IE, the ACK Power Offset IE, the NACK Power Offset IE or the CQI Power Offset IE in the HS-DSCH Information To Modify IE, then the Node B shall use the indicated CQI Feedback Cycle k value, the CQI Repetition Factor or the ACK-NACK Repetition Factor, ACK Power Offset, the NACK Power Offset or the CQI Power Offset  in the new configuration.]
-	[FDD - If the CQI Feedback Cycle2 k IE or the CQI Cycle Switch Timer IE  is included in HS-DSCH Information To Modify IE, then the Node B may use the indicated CQI Feedback Cycle2 k value, the CQI Cycle Switch Timer in the new configuration.]
-	[FDD - If the HS-SCCH Power Offset IE is included in the HS-DSCH Information To Modify IE, the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes Measurement Power Offset IE in the HS-DSCH Information IE or the HS-DSCH Information To Modify IE, then the Node B shall use the measurement power offset as described in TS 25.214 [10] subclause 6A.2.]
-	[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the TDD ACK NACK Power Offset IE in the HS-DSCH Information To Modify IE, the Node B shall use the indicated power offset in the new configuration.]
-	[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-SICH SIR Target IE in the HS-DSCH Information To Modify IE, the Node B shall use this value to the SIR Target in the new configuration. The HS-SICH SIR Target IE indicates the received UL SIR target of HS-SICH NACK for this UE.]
-	[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-SICH TPC step size IE in the HS-DSCH Information To Modify IE, the Node B shall use this value to the HS-SICH TPC step size in the new configuration.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK RECONFIGURATION PREPARE message includes the Multi-carrier HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify IE, the Node B shall use this information together with the HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify IE to allocate HSDPA resources over multiple carriers for the UE.]
-	[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify IE, the Node B may use this information in HSDPA resources allocation for the UE.]
-	[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the Puncturing Handling in First Rate Matching Stage IE in the HS-DSCH Information To Modify IE, then the Node B shall, if supported, apply the puncturing during first stage rate matching according to the Puncturing Handling in First Rate Matching Stage IE.]
-	[FDD - If the HS-DSCH Information To Modify IE includes the HS-SCCH Code Change Grant IE, then the Node B may modify the HS-SCCH codes corresponding to the HS-DSCH. The Node B shall then report the codes which are used in the new configuration specified in the HS-SCCH Specific Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[TDD - If the HS-DSCH Information To Modify IE includes the HS-SCCH Code Change Grant IE, then the Node B may modify the HS-SCCH parameters corresponding to the HS-DSCH. The Node B shall then report the values for the parameters which are used in the new configuration specified in the [3.84Mcps TDD - HS-SCCH Specific Information Response] [1.28Mcps TDD - HS-SCCH Specific Information Response LCR] [7.68Mcps TDD - HS-SCCH Specific Information Response 7.68Mcps] IEs in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the HS-DSCH Information To Modify IE includes the HS-PDSCH Code Change Grant IE, then the Node B may modify the HS-PDSCH codes corresponding to the HS-DSCH. The Node B shall then report the codes which are used in the new configuration specified in the Continuous Packet Connectivity HS-SCCH less Information Response IE in the RADIO LINK RECONFIGURATION READY message. If the concerned Node B is not in Continuous Packet Connectivity HS-SCCH less mode, the RNC shall not include the HS-PDSCH Code Change Grant IE in the HS-DSCH Information To Modify IE.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HARQ Preamble Mode IE in the HS-DSCH Information To Modify IE, then the Node B shall use the indicated HARQ Preamble Mode in the new configuration as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the Node B shall include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION READY message. If the HARQ Preamble Mode IE is not included or if the mode 0 is applied, then the Node B shall not include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information To Modify IE, then the Node B shall use, in the new configuration, the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]).
-	If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Physical Layer Category IE in the HS-DSCH Information To Modify IE, the Node B shall use this information in the new configuration and may include the HARQ Memory Partitioning IE in the RADIO LINK RECONFIGURATION READY message. The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.]
-	[FDD - If the MIMO Mode Indicator IE is included in the HS-DSCH Information To Modify IE, then the Node B shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in accordance with the MIMO Mode Indicator IE.]
-	[FDD - If the MIMO Mode Indicator IE is set to "Activate", then the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH Information To Modify IE, then the Node B may if the value is set to "allowed" use 64 QAM for the HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH Information To Modify IE with value set to "not allowed", then the Node B shall not use 64 QAM for the HS-DSCH Radio Link.]
-	[FDD - If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - Any secondary serving HS-DSCH that was applied in the old configuration shall remain in the new configuration unless it is explicitly removed.]
-	[FDD - If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the HS-DSCH Information To Modify IE includes the HS-SCCH Code Change Grant IE, and the Node B allows UE to use HSDPA resources distributed over multiple frequencies, then the Node B may modify the HS-SCCH Codes corresponding to the HS-DSCH over multiple frequencies, the Node B shall then report the codes which are used in the new configuration specified in the HS-SCCH Specific Information Response LCR per UARFCN IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[1.28Mcps TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Physical Layer Category IE in the HS-DSCH Information To Modify IE, the Node B shall use this information in the new configuration and may include the HARQ Memory Partitioning IE in the RADIO LINK RECONFIGURATION READY message. The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.]
-	[1.28Mcps TDD- If the MIMO Mode Indicator IE is included in the HS-DSCH Information To Modify IE, then the Node B shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in accordance with the MIMO Mode Indicator IE.]
-	[1.28 Mcps TDD - If the MIMO Mode Indicator IE is set to "Activate", then the Node B shall decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	If the RADIO LINK RECONFIGURATION PREPARE message includes DL RLC PDU Size Format IE for a Priority Queue in the in the HS-DSCH Information To Modify IE, the DL RLC PDU Size Format IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24].
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Information To Modify IE the Node B may use the supported HSDPA functions for this UE.]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Information To Modify IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the Node B shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the Single Stream MIMO Mode Indicator IE is included in the HS-DSCH Information To Modify IE, then the Node B shall activate/deactivate the Single Stream MIMO mode for the HS-DSCH Radio Link in accordance with the Single Stream MIMO Mode Indicator IE.]
-	[FDD - If the MIMO with four transmit antennas Mode Indicator IE, or the Dual Stream MIMO with four transmit antennas Mode Indicator IE is included in the HS-DSCH Information To Modify IE, then the Node B shall activate/deactivate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link in accordance with the MIMO with four transmit antennas Mode Indicator IE or Dual Stream MIMO with four transmit antennas Mode Indicator IE.]
-	[FDD - The Node B may include the Precoder weight set restriction IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
[FDD – Secondary Serving HS-DSCH Modification:]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH FDD Secondary Serving Information To Modify IE in the Additional HS Cell Information RL Reconf Prep IE, then:]
-	[FDD - If the HS-SCCH Power Offset IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE, the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes Measurement Power Offset IE in the HS-DSCH FDD Secondary Serving Information IE or the HS-DSCH FDD Secondary Serving Information To Modify IE, then the Node B shall use the measurement power offset as described in TS 25.214 [10] subclause 6A.2.]
-	[FDD - If the HS-DSCH FDD Secondary Serving Information To Modify IE includes the HS-SCCH Code Change Grant IE, then the Node B may modify the secondary serving HS-SCCH codes corresponding to the HS-DSCH. The Node B shall then report the codes which are used in the new configuration specified in the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IEin the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the MIMO Mode Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE, then the Node B shall activate/deactivate the MIMO mode for the secondary serving HS-DSCH Radio Link in accordance with the MIMO Mode Indicator IE.]
-	[FDD - If the MIMO Mode Indicator IE is set to "Activate", then the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the Single Stream MIMO Mode Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE, then the Node B shall activate/deactivate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link in accordance with the Single Stream MIMO Mode Indicator IE.]
-	[FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
-	[FDD - If, in the new configuration, the concerned Node B Communication Context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH Radio Link , the Node B shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - If the Diversity Mode IE is included, then:]
-	[FDD- the Node B shall apply cell specific transmit diversity configuration for the secondary serving HS-DSCH radio link according to Diversity Mode IE and Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information To Modify IE]
-	[FDD - If the Diversity Mode IE is not set to "None", the Node B shall apply diversity for the secondary serving HS-DSCH radio link according to the value given in the Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information To Modify IE.]
-	[FDD - If the Non Cell Specific Tx Diversity  IE equals "Tx Diversity" is included, the Node B shall apply non cell specific transmit diversity configuration and reconfigure the transmit diversity setting for the secondary serving HS-DSCH radio link to the same value as defined for the serving HS-DSCH radio link in the new configuration.]
-	[FDD -If the MIMO with four transmit antennas Mode Indicator IE or the Dual Stream MIMO with four transmit antennas Mode Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE, then the Node B shall activate/deactivate the MIMO with four transmit antennas mode or the Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link in accordance with the MIMO with four transmit antennas Mode Indicator IE or the Dual Stream MIMO with four transmit antennas Mode Indicator IE.]
-	[FDD - The Node B may include the Precoder weight set restriction IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
[FDD – Secondary Serving HS-DSCH Removal:]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Secondary Serving Remove IE in the Additional HS Cell Information RL Reconf Prep IE, then the indicated secondary serving HS-DSCH Radio Link shall be removed.]
HS-DSCH MAC-d Flow Addition/Deletion:
If the RADIO LINK RECONFIGURATION PREPARE message includes any HS-DSCH MAC-d Flows To Add or HS-DSCH MAC-d Flows To Delete IEs, then the Node B shall use this information to add/delete the indicated HS-DSCH MAC-d flows. When an HS-DSCH MAC-d flow is deleted, all its associated Priority Queues shall also be removed.
If the RADIO LINK RECONFIGURATION PREPARE message includes an HS-DSCH MAC-d Flows To Delete IE requesting the deletion of all remaining HS-DSCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the HS-DSCH configuration from the Node B Communication Context and release the HS-PDSCH resources.
If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH MAC-d Flows To Add IE, then:
-	The Node B shall include the HS-DSCH Initial Capacity Allocation IE in the RADIO LINK RECONFIGURATION READY message for every HS-DSCH MAC-d flow being added, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If Node B Communication Context is configured to use the "Flexible MAC-d PDU Size" format for the HS-DSCH, then Node B shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer received in RADIO LINK RECONFIGURATION PREPARE message in the HS-DSCH MAC-d Flows To Add IE for a Priority Queue including  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE.
-	If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-hs Guaranteed Bit Rate IE in the HS-DSCH MAC-d Flows To Add IE, the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
-	If the RADIO LINK RECONFIGURATION PREPARE message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
-	If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, then the Node B shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue.
-	The Node B may include the HARQ Memory Partitioning IE in the RADIO LINK RECONFIGURATION READY message. [FDD - The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.]
-	If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.
-	[1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B may include the HARQ Memory Partitioning per UARFCN IE in the RADIO LINK RECONFIGURATION READY message.]
-	If the RADIO LINK RECONFIGURATION PREPARE message includes DL RLC PDU Size Format IE for a Priority Queue in the in the HS-DSCH MAC-d Flows To Add IE, the DL RLC PDU Size Format IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24].
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, the Node B shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]
[FDD – HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change]
[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Preconfiguration Setup IE in the RL Information IE the Node B shall if supported preconfigure the indicated cells for Enhanced HS Serving Cell Change acoording to TS 25.308 [49]:]
-	[FDD – The Node B shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the C-ID IE part of the RL Information IE in the RADIO LINK RECONFIGURATION PREPARE message. The list of secondary serving HS-DSCH cells is designated by the list of C-IDs in the HS-DSCH Preconfiguration Setup IE part of the RL Information IE in the RADIO LINK RECONFIGURATION PREPARE message.]
-	[FDD – The number of HS-SCCH codes to preconfigure for each cell may be optionally specified:]
-	[FDD – by the Num Primary HS-SCCH Codes IE in the HS-DSCH Preconfiguration Setup IE, for the primary serving HS-DSCH cell]
-	[FDD – by the Num Secondary HS-SCCH Codes IE in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE for each of the secondary serving HS-DSCH cells]
-	[FDD – If Num Primary HS-SCCH Codes IE or Num Secondary HS-SCCH Codes IE is not included in the message, the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10].]
-	[FDD – The Node B shall return these codes in the Sets of HS-SCCH Codes IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE of the RADIO LINK RECONFIGURATION READY message.]
-	[FDD – The Node B shall use the first in the numbered list of the primary serving HS-DSCH cell’s HS-SCCH codes in the HS-SCCH Preconfigured Codes IE sent to the RNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [18].]
-	[FDD – The Node B shall include, in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK RECONFIGURATION READY message, IEs according to the rules defined for HS-DSCH Setup and:]
-	[FDD – if HARQ Preamble Mode IE is included in the HS-DSCH Preconfiguration Setup IE the HARQ Preamble Mode Activation Indicator IE.]
-	[FDD – if MIMO Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE.]
-	[FDD – if Ordinal number of frequency IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE]
-	[FDD – if MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE.]
-	[FDD – if Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE.]
-	[FDD – if Multiflow ordinal number of frequency IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE]
-	[FDD – if HS-DSCH MAC-d PDU Size Format IE is included in the HS-DSCH Preconfiguration Setup IE and set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used in the preconfigured configuration the HS-DSCH TB Size Table Indicator IE for each preconfigured cell.]
-	[FDD – if Sixtyfour QAM Usage Allowed Indicator IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE or in the HS-DSCH Preconfiguration Setup IE the SixtyfourQAM DL Usage Indicator IE for each preconfigured cell.]
-	[FDD – if Continuous Packet Connectivity HS-SCCH less Information IE is included in the HS-DSCH Preconfiguration Setup IE the Continuous Packet Connectivity HS-SCCH less Information Response IE.]
-	[FDD – if the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH Preconfiguration Setup IE, then the Node B shall store this information in the preconfigured configuration.]
-	[FDD – if the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE, then the Node B may store this information in the preconfigured configuration.]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the Node B shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH Preconfiguration Info IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD – The Node B shall include in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK RECONFIGURATION READY message the E-DCH FDD DL Control Channel Information containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:]
-	[FDD – The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – The Node B may configure for the preconfigured configuration the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the E-DCH Indicator IE for a secondary cell, the Node B shall include in the Additional E-DCH Preconfiguration Information IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK RECONFIGURATION READY message the E-DCH FDD DL Control Channel Information containing the preconfigured configuration of the Additional E-DCH serving cell, corresponding to the cell indicated with the E-DCH Indicator IE, according to the rules defined for Serving Additional E-DCH Radio Link Change as follows:]
-	[FDD – The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving Additional E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – The Node B may configure for the preconfigured configuration the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving Additional E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the Multiflow Information IE, then the Node B shall allocate resources for the preconfigured Multiflow for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the F-TPICH Information IE, then the Node B shall allocate resources for the preconfigured F-TPICH channel for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the UL CLTD Information IE, then the Node B shall allocate resources for the preconfigured UL CLTD for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the UL MIMO Information IE, then the Node B shall allocate resources for the preconfigured UL MIMO for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the SixteenQAM UL Operation Indicator IE, then the Node B shall allocate resources for the preconfigured UL Sixteen QAM for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the SixtyfourQAM UL Operation Indicator IE, then the Node B shall allocate resources for the preconfigured UL Sixtyfour QAM for the concerned Node B Communication Context.]
[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the Non-Serving Preconfiguration Setup IE in the RL Information IE and:]
-	[FDD – if the choice of new Serving RL is "New Serving RL in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE and/or New non-serving RL E-DCH FDD DL Control Channel Information B IEin the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD – if the choice of new Serving RL is "New Serving RL Not in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information C IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD – if the choice of new Serving RL is "New Serving RL in the Node B or New Serving RL Not in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C for the RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD – if the Additional E-DCH Non-Serving RL Preconfiguration Setup IE is included, the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C IE according to the choice of new Serving RL in Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information IE for the additional non serving E-DCH RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD –If the F-TPICH Information IE is included, the Node B shall use this information to allocate resources for the preconfigured F-TPICH channel for this RL in the serving RLS according to TS 25.211 [7].]
[FDD – Enhanced HS Serving Cell Change:]
[FDD - Upon receipt of the RADIO LINK RECONFIGURATION PREPARE message, if the Enhanced HS Serving Cell Change is preconfigured in the Node B for the Node B Communication Context, the Node B may execute the  Enhanced HS Serving Cell Change procedure according to TS 25.308 [49]]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Enhanced HS Serving CC Abort IE in the HS-DSCH Information To Modify IE or the HS-DSCH FDD Information IE then the Node B shall not execute the synchronized Enhanced HS Serving Cell Change procedure when performing the Intra-Node B Serving HS-DSCH Radio Link Change or, at inter Node B radio link change, the HS-DSCH Setup.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Non-Serving RL Preconfiguration Removal IE, the Node B shall remove the corresponding preconfigured E-DCH DL Control Channel Information according to the information.]
[FDD - Multiflow Setup:]
[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the Multiflow Information IE in HS-DSCH FDD Information IE, or it includes Multiflow Reconfiguration IE in HS-DSCH FDD Information To Modify IE and the choice of Setup or Change or Stop is “Setup”, then the Node B shall setup the requested Multiflow operation and then:]
-	[FDD – Use Total number of HS-DSCH cells IE to apply the HS-DPCCH format at the physical layer based on the total number of cells provided in this IE.]
-	[FDD – Use Role IE to know whether Multiflow cells configured at this Node B are assisting ones or not, for which Node B must read the correspondent part of the HS-DPCCH feedback channel.]
-	[FDD – Use MIMO IE to decide whether to apply the MIMO HS-DPCCH format at the physical layer.]
-	[FDD – If Timing IE is included, then Node B shall use this information to decide whether Multiflow cells configured at this Node B follow a different HS-DPCCH timing with an offset indicated by this IE.]
-	[FDD – If the Max number of HS-SCCH sets per Node B IE is included, then Node B shall use this information on the upper limit for the number HS-SCCH sets allocated and reported back to CRNC.]
-	[FDD – If the Assisting Repetition Factors IE is included, then the Node B shall use the values indicated in this IE within the Multiflow configuration.]
[FDD - Multiflow Modification:]
[FDD - If the Multiflow Reconfiguration IE is present in HS-DSCH Information To Modify IE the RADIO LINK RECONFIGURATION PREPARE message, and the choice of Setup or Change or Stop is “Change”, then the Node B shall use new configuration as follows:]
-	[FDD – If the Total number of HS-DSCH cells IE is included, then apply the HS-DPCCH format at the physical layer based on the total number of cells provided in this IE.]
-	[FDD – If the Role IE is included, then all the Multiflow cells configured at this Node B are assisting ones, for which Node B must read the correspondent part of the HS-DPCCH feedback channel.]
-	[FDD – If the MIMO IE is included, then decide whether to apply the MIMO HS-DPCCH format at the physical layer.]
-	[FDD – If Timing IE is included, then Node B shall use this information to decide whether Multiflow cells configured at this Node B follow a different HS-DPCCH timing with an offset indicated by this IE.]
-	[FDD – If the Max number of HS-SCCH sets per Node B IE is included, then Node B shall use this information on the upper limit for the number HS-SCCH sets allocated and reported back to CRNC.]
-	[FDD – If the Assisting Repetition Factors IE is included, then the Node B shall use the values indicated in this IE within the Multiflow configuration.]
[FDD - Multiflow Removal:]
[FDD - If the Multiflow Reconfiguration IE is present the HS-DSCH Information To Modify IE in the RADIO LINK RECONFIGURATION PREPARE message, and the choice of Setup or Change or Stop is “Stop”, then the Node B shall terminate the Multiflow operation.]
[FDD - E-DCH Setup:]
[FDD - If the E-DCH FDD Information IE is present in the RADIO LINK RECONFIGURATION PREPARE message:]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel information IE in the E-DCH FDD Information IE, then the Node B shall use this information to optimise MAC-e scheduling decisions.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the E-DCH Logical Channel Information IE in the E-DCH FDD Information IE, then the Node B shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).]
-	[FDD - If the TNL QoS IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Reference Power Offset IE, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Power Offset for Scheduling Info IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the UPH Filtering Measurement Forwarding Request IE, then the Node B shall use this instruction to handle the UE UPH filtering measurement forwarding.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Serving E-DCH RL IE indicating that the Serving E-DCH RL is in this Node B:]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the RADIO LINK RECONFIGURATION READY message for the initial grant for the serving E-DCH RL.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - The Node B may include the Default Serving Grant in DTX Cycle 2 IE in the RADIO LINK RECONFIGURATION READY message for the serving E-DCH RL.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If in the RADIO LINK RECONFIGURATION PREPARE message the E-DCH Grant Type is indicated as being "E-DCH Non-Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE, if included, for the related resource allocation operation.]
-	[FDD - If in the RADIO LINK RECONFIGURATION PREPARE message the E-DCH Grant Type is indicated as being "E-DCH Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume scheduled grants being configured for that E-DCH MAC-d flow.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Bundling Mode Indicator IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE and the Bundling Mode Indicator IE is set to "Bundling" and the E-TTI IE is set to "2ms", then the Node B shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the Node B shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Maximum Bitrate IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Processing Overload Level IE, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-AGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the SixteenQAM UL Operation Indicator IE, the Node B shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the SixteenQAM UL Operation Indicator IE.]
-	[FDD - If SixteenQAM UL Operation is activated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [32]. If SixteenQAM UL Operation is deactivated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [32].]
[FDD - E-DCH Radio Link Handling:]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH RL Indication IE in the RL Information IE:]
-	[FDD - The Node B shall setup the E-DCH resources, as requested or as configured in the Node B communication context, on the Radio Links indicated by the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE.]
-	[FDD - The Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION READY message for every RL indicated by the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE.]
-	[FDD - The Node B shall remove the E-DCH resources, if any, on the Radio Links, that are indicated by the E-DCH RL Indication set to "Non E-DCH".]
-	[FDD - For each RL for which the E-DCH RL Indication IE is set to "E-DCH", and which has or can have a common generation of E-RGCH information with another RL (current or future) when the Node B would contain the E-DCH serving RL, the Node B shall include the E-DCH RL Set ID IE in the RADIO LINK RECONFIGURATION READY message. The value of the E-DCH RL Set ID IE shall allow the RNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.]
[FDD - Serving E-DCH Radio Link Change:]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Serving E-DCH RL IE, this indicates the new Serving E-DCH Radio Link:]
-	[FDD - If the old Serving E-DCH RL is in this Node B, the Node B shall de-allocate the E-AGCH resources of the old Serving E-DCH Radio Link at the activation of the new configuration.]
-	[FDD - If the new Serving E-DCH RL is in this Node B:]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the RADIO LINK RECONFIGURATION READY message for the initial grant for the new serving E-DCH RL.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - The Node B may include the Default Serving Grant in DTX Cycle 2 IE in the RADIO LINK RECONFIGURATION READY message for the new serving E-DCH RL.]
-	[FDD - The Node B may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION READY message for every E-DCH Radio Links in the Node B.]
[FDD - E-DCH Modification:]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH FDD Information To Modify IE, then:]
-	[FDD - If the E-DCH FDD Information To Modify IE contains a E-DCH MAC-d Flow Specific Information IE which includes the Allocation/Retention Priority IE, the Node B shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum Number of Retransmissions for E-DCH IE for an E-DCH MAC-d flow then the Node B shall use this information to report if the maximum number of retransmissions has been exceeded.]
-	[FDD - If  the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH HARQ Power Offset FDD IE in the E-DCH FDD Information To Modify IE for an E-DCH MAC-d flow the Node B shall use this information for calculating the unquantised gain factor for an E-TFC ( ed,j,uq)as defined in TS 25.214 [10].]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the E-DCH Grant Type and it is indicated as being "E-DCH Non-Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE, if included, for the related resource allocation operation.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Grant Type and it is indicated as being "E-DCH Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume scheduled grants being configured for that E-DCH MAC-d flow.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information To Modify IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH MAC-d PDU Size Format IE in the E-DCH FDD Information To Modify IE, then the Node B shall use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Logical Channel To Add or E-DCH Logical Channel To Delete IEs, the Node B shall use this information to add/delete the indicated logical channels. When an logical channel is deleted, all its associated configuration data shall also removed.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Logical Channel To Modify IE, the Node B shall use this information to modify the indicated logical channels:]
	[FDD - If the E-DCH Logical Channel To Modify IE includes Scheduling Priority Indicator IE, the Node B shall apply the values in the new configuration.]
-	[FDD - If the E-DCH Logical Channel To Modify IE includes Scheduling Information IE, the Node B shall apply the values in the new configuration.]
-	[FDD - If the E-DCH Logical Channel To Modify IE includes MAC-es Guaranteed Bit Rate IE, the Node B shall apply the values in the new configuration.]
-	[FDD - If the E-DCH Logical Channel To Modify IE includes E-DCH DDI Value IE, the Node B shall apply the values in the new configuration.]
-	[FDD - If the E-DCH Logical Channel To Modify IE includes the Maximum MAC-d PDU Size Extended IE, the Node B shall apply the value in the new configuration.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Bundling Mode Indicator IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information To Modify IE and the Bundling Mode Indicator IE is set to "Bundling" and the E-TTI IE is set to "2ms", then the Node B shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the Node B shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If the E-DCH serving RL is in this Node B, the Node B may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission. In this case the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Maximum Bitrate IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Processing Overload Level IE, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Reference Power Offset IE, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Power Offset for Scheduling Info IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-AGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-e Reset Indicator IE in the E-DCH FDD Information To Modify IE, then the Node B shall use this value to determine whether MAC-e (or MAC-i) Reset is performed in the UE for sending the HARQ Failure Indication.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the SixteenQAM UL Operation Indicator IE in the E-DCH FDD Information To Modify IE, the Node B shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the SixteenQAM UL Operation Indicator IE.]
-	[FDD - If SixteenQAM UL Operation is activated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [32]. If SixteenQAM UL Operation is deactivated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [32].]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH DL Control Channel Grant Information IE in the E-DCH FDD Information To Modify IE, the Node B may modify E-AGCH Channelisation Code, E-RGCH/E-HICH Channelisation Code, E-RGCH Signature Sequence and/or E-HICH Signature Sequence for the E-DCH RL indicated by the E-DCH RL ID IE. The Node B shall then report the modified configuration which is used in the new configuration specified in the E-DCH FDD DL Control Channel Information IE for each E-DCH RL in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the Fast TTI switching Mode Requested Synchronized IE in the E-DCH FDD Information To Modify IE and Mode 1 is indicated, the Node B shall if supported start the TTI swiching process preparation.]
-	[FDD – If the RADIO LINK RECONFIGURATION PREPARE message includes the Fast TTI switching Mode Requested Synchronized IE in the E-DCH FDD Information To Modify IE and Mode 2 is indicated, the Node B shall if supported send the HS-SCCH order at the CFN indicated in Mode 2 to execute the TTI switching process.  Refer to TS 25.214 [10]].
-	[FDD - If the Fast TTI switching Mode Requested Synchronized IE is included in the  E-DCH FDD Information To Modify IE in the RADIO LINK RECONFIGURATION PREPARE message, the Node B may indicate which TTI switching Mode it supports in the Fast TTI switching Mode Supported IE in the E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
[FDD - E-DCH MAC-d Flow Addition/Deletion:]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes any E-DCH MAC-d Flows To Add or E-DCH MAC-d Flows To Delete IEs, then the Node B shall use this information to add/delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration data shall also be removed.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH MAC-d Flows To Add IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an E-DCH MAC-d Flows To Delete IE requesting the deletion of all remaining E-DCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the E-DCH configuration from the Node B Communication Context and release the E-DCH resources.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH MAC-d Flows To Add IE, then:]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH MAC-d Flows To Add IE, the Node B shall use this information to optimise MAC-e scheduling decisions.]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows To Add IE , the Node B shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]
[FDD – Additional E-DCH Setup:]
[FDD - If the Additional E-DCH Cell Information RL Reconf Prep IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency is "Setup", then the Additional E-DCH Cell Information Setup IE defines the new configuration and then:]
-	[FDD - If the C-ID IE is included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the C-ID IE indicates the cell in which the Additional E-DCH shall be setup.]
-	[FDD - The Node B shall setup the Additional E-DCH on the secondary uplink frequency and setup the requested Additional E-DCH resources on the Radio Links and in the cells indicated by the E-DCH Additional RL ID IE and the C-ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE.]
-	[FDD - If the C-ID IE is not included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the E-DCH Additional RL ID IE indicates the existing RL on which the Additional E-DCH shall be setup.]
-	[FDD - The Node B shall setup the Additional E-DCH on the Radio Links indicated by the E-DCH Additional RL ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE.]
-	[FDD - The Node B shall  use for the non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters the same values as for the corresponding cell of the Primary uplink frequency.]
-	[FDD - If the DL Power Balancing Information IE and/or the Minimum Reduced E-DPDCH Gain Factor IE are present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the Secondary UL Frequency Activation State is present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the Node B shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.]
-	[FDD - If the F-DPCH Slot Format IE is present in the Additional E-DCH RL Specific Information To Setup IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] 
-	[FDD - If the Primary CPICH Usage For Channel Estimation IE, the Secondary CPICH Information, the E-AGCH Power Offset IE, the E-RGCH Power Offset IE and/or the E-HICH Power Offset IE are present in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH RL Specific Information To Setup IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Maximum Bitrate IE , the E-DCH Minimum Set E-TFCI IE, the E-DCH Processing Overload Level IE, the Implicit Grant handling IE, the Minimum TEBS threshold IE and/or the DTX Information2 IE are present in the Additional E-DCH FDD Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If activation of power balancing for the Additional E-DCH RL by the RADIO LINK RECONFIGURATION PREPARE message is supported by the Node B, the Node B shall include the DL Power Balancing Activation Indicator IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.]
-	[FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
-	[FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE for each Additional E-DCH RL in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD – If the Additional Serving E-DCH Radio Link is configured in the Node B, then:]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH CellInformation Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message for the initial grant for the Additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message.]
[FDD – Additional E-DCH Configuration Change]
[FDD - If the Additional E-DCH Cell Information RL Reconf Prep IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency is "Configuration Change", then the Additional E-DCH Cell Information Configuration Change IE defines the new configuration and then:]
-	[FDD - If the UL Scrambling Code IE and/or the UL SIR Target IE are present in the UL DPCH Information IE in the Additional E-DCH Configuration Change Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the Minimum Reduced E-DPDCH Gain Factor IE is present in the Multicell E-DCH Information IE in the Additional E-DCH Configuration Change Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the F-DPCH Information IE is present in the Additional E-DCH Configuration Change Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
[FDD – Additional E-DCH RL Addition:]
[FDD - If the Additional E-DCH RL Specific Information To Add IE is present in the Additional E-DCH Configuration Change Information IE, then:]
-	[FDD - The Node B shall setup the E-DCH resources, as requested or as configured in the Node B Communication Context, on the Radio Links indicated by the E-DCH Additional RL ID IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
-	[FDD - If the Initial DL Transmission Power IE, the Maximum DL Power IE, the Minimum DL Power IE and/or the F-DPCH Slot Format IE are present in the Additional E-DCH RL Specific Information To Add IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the DL Reference Power IE, the E-AGCH Power Offset IE, the E-RGCH PowerOffset IE, and/or the E-HICH Power Offset IE are present in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH RL Specific Information To Add IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Individual" in the existing Additional E-DCH RL(s) and the RADIO LINK RECONFIGURATION PREPARE message includes the DL Reference Power IE, the Node B shall activate the power balancing and use the DL Reference Power IE for the power balancing procedure in the new Additional E-DCH RL(s), if activation of power balancing by the RADIO LINK RECONFIGURATION READY message is supported, according to subclause 8.3.7. In this case, the Node B shall include the DL Power Balancing Activation Indicator IE in theE-DCH Additional RL Specific Information Response IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message. If the Node B starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. Pinit shall be set to the power level indicated by the Initial DL Transmission Power IE (if received) in the Additional E-DCH RL Specific Information To Add IE or the decided DL TX power level on each DL channelisation code of an Additional E-DCH RL based on power level of existing Additional E-DCH RLs.]
-	[FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.]
-	[FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
-	[FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Add IE in the Additional E-DCH FDD Setup Information IE the Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE for each Additional E-DCH RL in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION READY message.]
[FDD – Additional E-DCH RL Modification:]
[FDD - If the Additional E-DCH RL Specific Information To Modify IE is present in the Additional E-DCH Configuration Change Information IE, then the RL indicated by the E-DCH Additional RL ID IE indicates the RL on which E-DCH resources shall be modified:]
-	[FDD - If the DL Code Information IE, the Maximum DL Power IE, the Minimum DL Power IE, and/or the F-DPCH Slot Format IE are present in the Additional E-DCH RL Specific Information To Modify IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the DL Reference Power IE, the Primary CPICH Usage For Channel Estimation IE, the Secondary CPICH Information Change IE, the E-AGCH Power Offset IE, the E-RGCH Power Offset IE, the E-HICH Power Offset IE and/or the E-DCH DL Control Channel Grant IE are present in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH RL Specific Information To Modify IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If updating of power balancing parameters by the RADIO LINK RECONFIGURATION PREPARE message is supported by the Node B, the Node B shall include the DL Power Balancing Updated Indicator IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE for each affected RL in the RADIO LINK RECONFIGURATION READY message.]
[FDD – Additional E-DCH Modification:]
[FDD - If the Additional E-DCH FDD Information To Modify IE is present in the Additional E-DCH Configuration Change Information IE, then:]
-	[FDD - If the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE and/or the E-DCH Minimum Set E-TFCI IE is included, the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If the E-DCH Maximum Bitrate IE is included, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[FDD - If the E-DCH Processing Overload Level IE is included, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]
-	[FDD - If the Additional E-DCH serving RL is in this Node B, the Node B may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission. In this case the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional Modified E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[FDD - If the DTX Information2 IE is included, the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If the Implicit Grant handling IE is included, the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If the Minimum TEBS threshold IE is included, the Node B shall use this information for the related resource allocation operation.]
[FDD – Additional E-DCH Removal]
[FDD - If the Additional E-DCH Cell Information RL Reconf Prep IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency is "Removal", then the additional E-DCH on the secondary uplink frequency shall be removed.]
[FDD – Radio Links without DPCH/F-DPCH operation]
[FDD – If the Radio Links without DPCH/F-DPCH Indication IE is present in the RADIO LINK RECONFIGURATION PREPARE message:]
-	[FDD – The Node B shall if supported start operation with Radio Links without DPCH/F-DPCH.]
[TDD - Intra-Node B Serving E-DCH Radio Link Change:]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Serving RL IE, this indicates the new Serving E-DCH Radio Link:]
-	[TDD - In the new configuration the Node B shall de-allocate the E-DCH resources of the old Serving E-DCH Radio Link and allocate the E-DCH resources for the new Serving E-DCH Radio Link.]
-	[TDD - The Node B shall allocate E-AGCH parameters [1.28Mcps TDD - and E-HICH parameters] corresponding to the E-DCH and include the E-AGCH Specific Information Response TDD IE [1.28Mcps TDD - and E-HICH  Specific Information Response TDD IE] in the E-DCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]
-	[TDD - If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.]
[TDD - E-PUCH Handling]:
[3.84Mcps TDD and 7.68Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an E-PUCH Information IE, the Node B shall apply the parameters to the new configuration.]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an E-PUCH Information LCR IE, the Node B shall apply the parameters to the new configuration.]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an E-TFCS Information TDD IE, the Node B shall apply the beta parameters to the new configuration.]
[3.84Mcps TDD - E-DCH Setup]:
[3.84Mcps TDD - the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: E-DCH Serving RL IE, E-PUCH Information IE, E-TFCS Information TDD IE, E-DCH MAC-d Flows to Add IE, E-DCH TDD Information IE and E-DCH Non-scheduled Grant Information TDD IE if there are to be non-scheduled grants.]
[1.28Mcps TDD - E-DCH Setup]:
[1.28Mcps TDD - the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: E-DCH Serving RL IE, E-PUCH Information LCR IE, E-TFCS Information TDD IE, E-DCH MAC-d Flows to Add IE, E-DCH TDD Information LCR IE and E-DCH Non-scheduled Grant Information LCR TDD IE if there are to be non-scheduled grants.]
[1.28Mcps TDD - If the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify IE is not present, or if the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE is not present, and if the RADIO LINK RECONFIGURATION PREPARE message includes the UE TS0 Capability LCR IE in the E-DCH TDD Information LCR IE, the Node B can use this information to allocate the downlink resources for the UE according to TS 25.306 [33].]
[7.68Mcps TDD - E-DCH Setup]:
[7.68Mcps TDD - the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: E-DCH Serving RL IE, E-PUCH Information IE, E-TFCS Information TDD IE, E-DCH MAC-d Flows to Add IE, E-DCH TDD Information 7.68Mcps IE and E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE if there are to be non-scheduled grants.]
[TDD - E-DCH MAC-d Flow Addition/Deletion:]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes any E-DCH MAC-d Flows To Add or E-DCH MAC-d Flows To Delete IEs, then the Node B shall use this information to add/delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration data shall also be removed.]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information TDD IE in the E-DCH MAC-d Flows To Add IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel.]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an E-DCH MAC-d Flows To Delete IE requesting the deletion of all remaining E-DCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the E-DCH configuration from the Node B Communication Context and release the E-DCH resources.]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes an E-DCH MAC-d Flows To Delete IE requesting the deletion of all remaining non-scheduled E-DCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the non-scheduled E-DCH configuration from the Node B Communication Context and release the non-scheduled E-DCH resources [1.28 Mcps TDD - and the related Signature Sequence of the Non-scheduled E-HICH].]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH MAC-d Flows To Add IE, then:]
-	[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH MAC-d Flows To Add IE, the Node B shall use this information to optimise MAC-e scheduling decisions.]
-	[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-es Maximum Bit Rate LCR IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows To Add IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
[3.84Mcps TDD - E-DCH Non-scheduled allocations:]
[3.84Mcps TDD - If the E-DCH Non-scheduled Grant Information TDD IE is present in the RADIO LINK RECONFIGURATION PREPARE message the Node B shall assume that non-scheduled transmissions will take place according to the parameters in the information element.]
[1.28Mcps TDD - E-DCH Non-scheduled allocations:]
[1.28Mcps TDD - If the E-DCH Non-scheduled Grant Information LCR TDD IE is present in the RADIO LINK RECONFIGURATION PREPARE message the Node B shall assume that non-scheduled transmissions will take place according to the parameters in the information element.]
[7.68Mcps TDD - E-DCH Non-scheduled allocations:]
[7.68Mcps TDD - If the E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE is present in the RADIO LINK RECONFIGURATION PREPARE message the Node B shall assume that non-scheduled transmissions will take place according to the parameters in the information element.]
[TDD - E-DCH Modification:]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH TDD Information To Modify IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel.]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH MAC-d PDU Size Format IE in the E-DCH TDD Information To Modify IE, then the Node B shall use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the [3.84Mcps TDD - E-DCH TDD Information  IE][1.28Mcps TDD - E-DCH TDD Information LCR IE][7.68Mcps TDD - E-DCH TDD Information 7.68Mcps IE], then:]
-	[3.84Mcps TDD - If the E-DCH TDD Information IE includes the E-DCH TDD Maximum Bitrate IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[1.28Mcps TDD - If the E-DCH TDD Information LCR IE includes the E-DCH Physical Layer Category LCR  IE or Extended E-DCH Physical Layer Category LCR IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[7.68Mcps TDD - If the E-DCH TDD Information 7.68Mcps IE includes the E-DCH TDD Maximum Bitrate 7.68Mcps IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[TDD - If the [3.84Mcps TDD - E-DCH TDD Information IE] [7.68Mcps TDD - E-DCH TDD Information 7.68Mcps IE] [1.28Mcps TDD - E-DCH TDD Information LCR IE] includes the E-DCH Processing Overload Level IE, then if the Node B could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]
-	[TDD - If the [3.84Mcps TDD - E-DCH TDD Information IE] [1.28Mcps TDD - E-DCH TDD Information LCR IE] [7.68Mcps TDD - E-DCH TDD Information 7.68Mcps IE]includes the E-DCH Power Offset for Scheduling Info IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
-	[1.28Mcps TDD - If the E-DCH TDD Information LCR IE includes the Maximum Number of Retransmission for Scheduling Info LCR IE and the E-DCH Retransmission timer for Scheduling Info LCR IE, then the Node B shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.]
-	[1.28Mcps TDD - If the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify IE is not present, or if the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE is not present, and if the RADIO LINK RECONFIGURATION PREPARE message includes the UE TS0 Capability LCR IE in the E-DCH TDD Information to Modify IE, the Node B can use this information to allocate the downlink resources for the UE according to TS 25.306 [33].]
-	[1.28Mcps TDD - If the E-DCH TDD Information LCR IE includes the Multi-Carrier E-DCH Physical Layer Category LCR IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.]
[TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH TDD Information To Modify IE, then:]
-	[TDD - If the E-DCH TDD Information To Modify IE contains a E-DCH MAC-d Flow Specific Information IE which includes the Allocation/Retention Priority IE, the Node B shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.]
-	[TDD - If the E-DCH TDD Information To Modify IE message includes the Maximum Number of Retransmissions for E-DCH IE for an E-DCH MAC-d flow then the Node B shall use this information to report if the maximum number of retransmissions has been exceeded.]
-	[1.28Mcps TDD - If the E-DCH TDD Information To Modify IE message includes the E-DCH MAC-d Flow Retransmission Timer IE for an E-DCH MAC-d flow then the Node B shall use this information to set the retransmission timer.]
-	[TDD - If  the E-DCH TDD Information To Modify IE message includes the E-DCH HARQ Power Offset TDD IE for an E-DCH MAC-d flow the Node B shall use this new power offset value.]
-	[TDD - If the E-DCH TDD Information To Modify IE includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.]
-	[TDD - If the E-DCH TDD Information To Modify IE includes the E-DCH Grant Type IE, the Node B shall treat the E-DCH MAC-d flow as Scheduled or Non-scheduled accordingly.]
-	[TDD - If the E-DCH TDD Information To Modify IE includes the E-DCH Logical Channel To Add or E-DCH Logical Channel To Delete IEs, the Node B shall use this information to add/delete the indicated logical channels. When a logical channel is deleted, all its associated configuration data shall also removed.]
-	[TDD - If the E-DCH TDD Information To Modify IE includes the E-DCH Logical Channel To Modify IE, the Node B shall use this information to modify the indicated logical channels:]
-	[TDD - If the E-DCH Logical Channel To Modify IE includes Scheduling Priority Indicator IE, the Node B shall apply the values in the new configuration.]
-	[TDD - If the E-DCH Logical Channel To Modify IE includes Scheduling Information IE, the Node B shall apply the values in the new configuration.]
-	[TDD - If the E-DCH Logical Channel To Modify IE includes MAC-es Guaranteed Bit Rate IE, the Node B shall apply the values in the new configuration.]
-	[1.28Mcps TDD - If the E-DCH Logical Channel To Modify IE includes MAC-es Maximum Bit Rate LCR IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[TDD - If the E-DCH Logical Channel To Modify IE includes E-DCH DDI Value IE, the Node B shall apply the values in the new configuration.]
-	[TDD - If the E-DCH Logical Channel To Modify IE includes the Maximum MAC-d PDU Size Extended IE, the Node B shall apply the value in the new configuration.]
-	[TDD - If the E-DCH TDD Information To Modify IE includes the MAC-e Reset Indicator IE in the E-DCH TDD Information To Modify IE, then the Node B shall use this value to determine whether MAC-e (or MAC-i) Reset is performed in the UE for sending the HARQ Failure Indication.]
[FDD - Phase Reference Handling]:
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Primary CPICH Usage For Channel Estimation IE, the Node B shall assume that Primary CPICH usage for channel estimation has been reconfigured.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Secondary CPICH Information Change IE, the Node B shall assume that Secondary CPICH usage for channel estimation has been reconfigured.]
[FDD - Fast Reconfiguration]:
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Fast Reconfiguration Mode IE, the Node B shall, if supported, and if it is possible to base the synchronization of the reconfiguration on the detection of the change in the uplink scrambling code for this reconfiguration, include the Fast ReconfigurationPermission IE in the RADIO LINK RECONFIGURATION READY message.]
[1.28Mcps TDD - Power Control GAP:]
[1.28Mcps TDD - If the Power Control GAP IE is included in the RADIO LINK RECONFIGURATION PREPARE message, the Node B may use the value for the power control for HS-SCCH and HS-SICH according to the TS 25.224 [21].]
[1.28Mcps TDD - E-UTRAN Inter-RAT measurement:]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Idle Interval Information IE, if supported, the Node B shall use the value for E-UTRAN Inter-RAT measurement according to the TS 25.331 [18].]
[1.28Mcps TDD - HS-DSCH-RNTI for FACH:]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH-RNTI for FACH IE, if supported, the Node B shall store this information and include the E-RNTI for FACH IE in the RADIO LINK RECONFIGURATION READY message.]
[1.28Mcps TDD – Inter-frequency/ Inter-RAT measurement:]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Measurement occasion pattern sequence parameters IE in the DCH Measurement Occasion Information IE, the Node B shall store the information about the Measurement occasion pattern sequences and use the value(s) to calculate the Inter-frequency/Inter-RAT measurement occasion according to TS 25.331 [18].] 
[1.28Mcps TDD –Multi-Carrier E-DCH Continue:]
[1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Continue, Setup or Change is "Continue", then the current Multi-Carrier E-DCH configuration shall not be changed.]
[1.28Mcps TDD – Multi-Carrier E-DCH Setup:]
[1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf  IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Continue, Setup or Change is "Setup", then the Multi-Carrier E-DCH Information LCR IE defines the new configuration and then:]
-	[1.28Mcps TDD - The Node B shall use the Multi-Carrier E-DCH Transport Bearer Mode LCR IE to decide the transport bearer mode in the new configuration.]
-	[1.28Mcps TDD - The Node B shall setup the requested E-DCH resource on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.]
[1.28Mcps TDD – Multi-Carrier E-DCH Change:]
[1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf  IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Continue, Setup or Change is "Change", then: the Multi-Carrier E-DCH Information LCR IE defines the new configuration and then:]
-	[1.28Mcps TDD - If the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE is different from current configured frequencies, then the Node B shall setup the E-DCH resources, as requested in the Node B Communication Context, on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.]
-	[1.28Mcps TDD - If the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE is the same as any current configured frequency, then the Node B shall reconfigure the E-DCH resources, as requested or as configured in the Node B Communication Context, on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.]
[1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf  IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Continue, Setup or Change is "Change" and the Removal UL Multi-Carrier info IE is included, then the Node B shall remove the corresponding E-DCH configuration on the uplink frequencies indicated by the UARFCN IE in the Removal UL Multi-Carrier info IE.]
[1.28Mcps TDD – Non-rectangular resource operation:]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the UE support of non-rectangular resource allocation IE, the Node B shall, if supported, use this information to determine whether includes the Non-rectangular resource allocation indicator IE and the Non-rectangular resource timeslot set IE or not.]
[FDD - UL DPCCH2 Setup:]
[FDD - If the UL DPCCH2 Reconfiguration IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL DPCCH2 is "Setup", then:]
-	[FDD – if the serving HS-DSCH RL is in the Node B then the Node B shall configure the concerned Node B Communication Context to use a second F-DPCH in the downlink, i.e. with transmission of only the TPC field and a DPCCH2 in the uplink, i.e. with the transmission of only the second pilot and the TPC field on the Serving HS-DSCH Radio Link and the Node B shall activate UL DPCCH2 operation for the radio link according to the information provided in the IE according to ref TS 25.214 [10].]
-	[FDD – if the serving HS-DSCH is not in the Node B then the Node B may consider the concerned Node B Communication Context to use the UL DPCCH2 configuration on the Serving HS-DSCH Radio Link.]
-	[FDD – If the UL DPCCH2 Reconfiguration IE includes the Extended E-DPCCH Power Offset IE, the concerned Node B shall use the value when the new configuration is being used.]
[FDD – UL DPCCH2 Modification:]
[FDD - If the UL DPCCH2 Reconfiguration IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL DPCCH2 is "Configuration Change", then: the UL DPCCH2 Information To Modify IE defines the new configuration and then:]
-	[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the F-DPCH info IE in the UL DPCCH2 Information To Modify IE and if the serving HS-DSCH RL is in the Node B, then the Node B shall use this value to update the second F-DPCH for the concerned Node B Communication Context.]
-	[FDD – If the UL DPCCH2 Reconfiguration IE includes the Extended E-DPCCH Power Offset IE, the concerned Node B shall use the value when the new configuration is being used.]
[FDD - UL DPCCH2 Removal:]
[FDD - If the UL DPCCH2 Reconfiguration IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL DPCCH2 is "Removal", then the configured UL DPCCH2 for the concerned Node B Communication Context shall be removed.]
[FDD – Downlink TPC enhancements Setup:]
[FDD - If the Downlink TPC enhancements Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of Downlink TPC enhancements is "Setup", then:]
-	[FDD – The NodeB shall, if supported, to use the Decimation factor for primary frequency IE and/or the Decimation factor for secondary frequency IE to configure all the radio links using F-DPCH on the related frequency with power control Algorithm 3.]
[FDD - If the TPC slot position in the RL Information is included in the RADIO LINK RECONFIGURATION PREPARE message, the Node B shall, if supported, use it for power control Algorithm 3.]
[FDD - If the TPC slot position in the Additional E-DCH Cell Information Setup is included in the RADIO LINK RECONFIGURATION PREPARE message, the Node B shall, if supported, use it for power control Algorithm 3.]
[FDD –Downlink TPC enhancements Modification:]
[FDD - If the Downlink TPC enhancements Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of Downlink TPC enhancements is "Configuration Change", then: the Downlink TPC enhancements Information To Modify IE defines the new configuration and then:]
-	[FDD - The NodeB shall, if supported, use the Decimation factor for primary frequency IE and/or the Decimation factor for secondary frequency IE to reconfigure all the radio links using F-DPCH on the related frequency with power control Algorithm 3.]
[FDD - If the TPC slot position in the RL Information is included in the RADIO LINK RECONFIGURATION PREPARE message, the Node B shall, if supported, use it for power control Algorithm 3.]
[FDD - If the TPC slot position in the Additional E-DCH Cell Information Configuration Change is included in the RADIO LINK RECONFIGURATION PREPARE message, the Node B shall, if supported, use it for power control Algorithm 3.]
[FDD - Downlink TPC enhancements Removal:]
[FDD - If the Downlink TPC enhancements Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of Downlink TPC enhancements is "Removal", then the configured power control Algorithm 3 for the concerned Node B Communication Context shall be removed.]
General
If the RADIO LINK RECONFIGURATION PREPARE message includes the Transport Layer Address IE and Binding ID IEs in the [TDD - DSCHs To Modify, DSCHs To Add, USCHs To Modify, USCHs To Add], HS-DSCH Information, HS-DSCH Information To Modify, HS-DSCH MAC-d Flows To Add, [TDD - E-DCH MAC-d Flows to Add, E-DCH TDD Information to Modify IE] [FDD - RL Specific E-DCH Information IE] or in the RL Specific DCH Information IEs, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for any Transport Channel [FDD - for which the Transport Bearer Not Requested Indicator IE is not included] or MAC-d flow [FDD - for which the Transport Bearer Not Requested Indicator IE is not included] being added, or any Transport Channel [FDD - for which the Transport Bearer Not Requested Indicator IE was not included] or MAC-d flow [FDD - for which the Transport Bearer Not Requested Indicator IE was not included] being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE.
If the requested modifications are allowed by the Node B and the Node B has successfully reserved the required resources for the new configuration of the Radio Link(s), it shall respond to the CRNC with the RADIO LINK RECONFIGURATION READY message. When this procedure has been completed successfully there exists a Prepared Reconfiguration, as defined in subclause 3.1.
The Node B shall include in the RADIO LINK RECONFIGURATION READY message the Transport Layer Address IE and the Binding ID IE for any Transport Channel [FDD - for which the Transport Bearer Not Requested Indicator IE was not included] or MAC-d flow [FDD - for which the Transport Bearer Not Requested Indicator IE was not included] being added or any Transport Channel [FDD - for which the Transport Bearer Not Requested Indicator IE was not included] or MAC-d flow [FDD - for which the Transport Bearer Not Requested Indicator IE was not included] being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE.
In the case of a set of co-ordinated DCHs requiring a new transport bearer on the Iub interface, the Transport Layer Address IE and the Binding ID IE in the DCH Information Response IE shall be included [FDD - if the Transport Bearer Not Requested Indicator IE is not included for this DCH,] only for one of the DCH in the set of co-ordinated DCHs.
[FDD - If the RADIO LINK RECONDIGURATION PREPARE message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer shall not be Established" for a DCH or an E-DCH MAC-d flow, then the Node B shall not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow and shall include the Transport Bearer Not Setup Indicator IE for the DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION READY message.]
[FDD - If the RADIO LINK RECONDIGURATION PREPARE message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer may not be Established" for a DCH or an E-DCH MAC-d flow and:]
-	[FDD - if the Node B establishes a transport bearer for the concerned DCH or E-DCH MAC-d flow, the Node B shall include in the RADIO LINK RECONFIGURATION READY message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the DCH or E-DCH MAC-d flow being established.]
-	[FDD - if the Node B does not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow, the Node B shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION READY message.]
In the case of a Radio Link being combined with another Radio Link within the Node B, the Transport Layer Address IE and the Binding ID IE in the DCH Information Response IE shall be included only for one of the combined Radio Links [FDD - if the Transport Bearer Not Requested Indicator IE is not included for this DCH].
[FDD - In the case of an E-DCH RL being combined with another E-DCH RL within the Node B, the E-DCH FDD Information Response IE shall be included only for one of the combined E-DCH RLs.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Additional E-DCH Cell Information RL Reconf Prep IE, then:]
-	[FDD – if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to "Separate Iub Transport Bearer Mode" the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
-	[FDD – if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to "UL Flow Multiplexing Mode" the Node B shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.]
-	[FDD - if Separate Iub Transport Bearer Mode is used in the new configuration, then:]
-	[FDD - the Node B shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the Transport Bearer Not Requested Indicator IE in the E-DCH MAC-d Flow Specific Information IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE and/or the Transport Bearer Request Indicator IE in the E-DCH FDD Information To Modify IE received for the corresponding Radio Link(s) of the Primary Uplink Frequency to determine the transport bearer configuration in the new configuration for the radio links of the Secondary Uplink Frequency.]
-	[FDD - If the Transport Layer Address IE and Binding ID IE is included for an E-DCH MAC-d flow in the Additional E-DCH MAC-d Flows Specific Information IE in the Additional E-DCH FDD Information IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE or in the Additional E-DCH MAC-d Flows Specific Information IE in the Additional E-DCH FDD Information To Modify IE in the Additional E-DCH Configuration Change Information IE in the Additional E-DCH Cell Information Configuration Change IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow the Node B shall, for establishment of the transport bearer, include in the RADIO LINK RECONFIGURATION READY message the Binding ID IE and Transport Layer Address IE in the Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional E-DCH FDD Information Response IE and/or and/or include the Binding ID IE and Transport Layer Address IE for the E-DCH MAC-d flow has been modified in the Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional Modified E-DCH FDD Information Response IE.]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Multi-Carrier E-DCH Information Reconf IE, then:]
-	[1.28Mcps TDD - If the Multi-carrier E-DCH Transport Bearer Mode LCR IE is set to "Separate Iub Transport Bearer Mode" the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
-	[1.28Mcps TDD - If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "UL Flow Multiplexing Mode" the Node B shall use this mode in the new configuration and multiplex each MAC-d flow on one transport bearer.]
-	[1.28Mcps TDD - If the choice of Continue, Setup or Change in the the Multi-Carrier E-DCH Information Reconf  IE is "Setup" and the Separate Iub transport bearer mode is used in the new configuration, or if the choice of Continue, Setup or Change in the the Multi-Carrier E-DCH Information Reconf  IE is "Change" and the Transport Bearer Mode is changed to "Separate Iub Transport Bearer Mode" indicated by Multi-carrier E-DCH Transport Bearer Mode LCR IE, then the Node B shall include the Binding ID IE and Transport Layer Address IE in the Multi-Carrier E-DCH Information Response LCR IE in the RADIO LINK RECONFIGURATION READY message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
-	[1.28Mcps TDD - The Node B shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the Transport Bearer Request Indicator IE in the E-DCH TDD Information to Modify IE received for the corresponding Radio Link to determine the transport bearer configuration in the new configuration for the all Uplink Frequencies.]
-	[1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration and if the Transport Bearer Request Indicator IE is set to " Bearer Requested ", then the Node B shall include the Binding ID IE and Transport Layer Address IE in the E-DCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
8.3.2.3	Unsuccessful Operation

Figure 31: Synchronised Radio Link Reconfiguration Preparation procedure, Unsuccessful Operation
If the Node B cannot reserve the necessary resources for all the new DCHs of one set of co-ordinated DCHs requested to be added, it shall regard the Synchronised Radio Link Reconfiguration Preparation procedure as having failed.
If the requested Synchronised Radio Link Reconfiguration Preparation procedure fails for one or more RLs, the Node B shall send the RADIO LINK RECONFIGURATION FAILURE message to the CRNC, indicating the reason for failure.
Typical cause values are as follows:
Radio Network Layer Cause
-	UL SF not supported
-	DL SF not supported
-	Downlink Shared Channel Type not supported
-	Uplink Shared Channel Type not supported
-	CM not supported
-	Number of DL codes not supported
-	Number of UL codes not supported
-	RL Timing Adjustment not supported
-	F-DPCH not supported
-	[FDD - Continuous Packet Connectivity DTX-DRX operation not available]
-	[FDD - Continuous Packet Connectivity UE DTX Cycle not available]
-	[FDD - MIMO not available]
-	E-DCH MAC-d PDU Size Format not available
-	[FDD - SixtyfourQAM DL and MIMO Combined not available]
-	[FDD - Multi Cell operation not available.]
-	[1.28Mcps TDD- MIMO not available]
-	[1.28Mcps TDD - SixtyfourQAM DL and MIMO Combined not available]
-	[FDD - TX diversity for MIMO UE on DL Control Channels not available]
-	[FDD – Single Stream MIMO not available]
-	[FDD - Multi Cell operation with MIMO not available]
-	[FDD - Multi Cell operation with Single Stream MIMO not available]
-	[FDD - Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available]
-	[FDD - Multi Cell E-DCH operation not available]
-	[FDD - UL CLTD operation not available]
-	[FDD - MIMO with four transmit antennas not available]
-	[FDD - Dual Stream MIMO with four transmit antennas not available]
-	[FDD – Multiflow operation not available]
-	[FDD - SixtyfourQAM UL operation not available]
-	[FDD – UL MIMO operation not available]
-	[FDD – UL MIMO and SixteenQAM operation not available]
-	[FDD – UL MIMO and SixtyfourQAM operation not available]
-	[FDD – E-DCH decoupling operation not available]
-	[FDD – Basic DCH Enhancements operation not available]
-	[FDD – Full DCH Enhancements operation not available]
-	[FDD – Radio Links without DPCH/F-DPCH operation not available]
-	[FDD – UL DPCCH2 operation not available]
-	[FDD – Dowlink TPC enhancements operation not available]
Transport Layer Cause
-	Transport Resources Unavailable
Miscellaneous Cause
-	O&M Intervention
-	Control processing overload
-	HW failure
8.3.2.4	Abnormal Conditions
If only a subset of all the DCHs belonging to a set of co-ordinated DCHs is requested to be deleted, the Node B shall regard the Synchronised Radio Link Reconfiguration Preparation procedure as having failed and shall send the RADIO LINK RECONFIGURATION FAILURE message to the CRNC.
If more than one DCH of a set of co-ordinated DCHs has the QE-Selector IE set to "selected" [TDD - or no DCH of a set of co-ordinated DCHs has the QE-Selector IE set to "selected"], the Node B shall regard the Synchronised Radio Link Reconfiguration Preparation procedure as failed and shall respond with a RADIO LINK RECONFIGURATION FAILURE message.
If the RADIO LINK RECONFIGURATION PREPARE message includes a DCHs To Modify IE or DCHs To Add IE with multiple DCH Specific Info IEs, and if the DCHs in the DCHs To Modify IE or DCHs To Add IE do not have the same Transmission Time Interval IE in the Semi-Static Transport Format Information IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[FDD - If the RL Information IE includes the DL Reference Power IE, but the power balancing is not active in the indicated RL(s), the Node B shall regard the Synchronised Radio Link Reconfiguration Preparation procedure as having failed and the Node B shall respond with the RADIO LINK RECONFIGURATION FAILURE message with the cause value "Power Balancing status not compatible".]
[FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Common" in the existing RL(s) but the RADIO LINK RECONFIGURATION PREPARE message IE includes more than one DL Reference Power IE, the Node B shall regard the Synchronised Radio Link Reconfiguration Preparation procedure as having failed and the Node B shall respond with the RADIO LINK RECONFIGURATION FAILURE message with the cause value "Power Balancing status not compatible".]
If the RADIO LINK RECONFIGURATION PREPARE message contains the Transport Layer Address IE or the Binding ID IE when establishing a transport bearer for any Transport Channel or HS-DSCH MAC-d flow being added, or any Transport Channel or HS-DSCH MAC-d flow being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message is to modify UE channel estimation information for an existing RL and the modification is not allowed according to TS 25.214 [10] subclause 4.3.2.1, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
If the RADIO LINK RECONFIGURATION PREPARE message contains any of the HS-DSCH Information To Modify IE, HS-DSCH MAC-d Flows To Add IE or HS-DSCH MAC-d Flows To Delete IE in addition to the HS-DSCH Information IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If the RADIO LINK RECONFIGURATION PREPARE message contains any of the HS-DSCH Information To Modify IE, HS-DSCH MAC-d Flows To Add IE, HS-DSCH MAC-d Flows To Delete IE or HS-PDSCH RL ID IE and the Serving HS-DSCH Radio Link is not in the Node B, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Information IE and does not include the HS-PDSCH RL-ID IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Information To Modify IE deleting the last remaining Priority Queue of an HS-DSCH MAC-d Flow, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-PDSCH RL-ID IE indicating a Radio Link not existing in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[TDD - If multiple radio links exist within the Node B Communication Context and the RADIO LINK RECONFIGURATION PREPARE message does not include a RL ID IE within each UL DPCH To Add Per RL IE, DL DPCH To Add Per RL IE, UL DPCH To Modify Per RL IE, and DL DPCH To Modify Per RL IE that is present in the message, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
If the RADIO LINK RECONFIGURATION PREPARE message contains any of the HS-DSCH Information IE, HS-DSCH Information To Modify IE, or HS-DSCH MAC-d Flows To Add IE and if in the new configuration the Priority Queues associated with the same HS-DSCH MAC-d Flow ID IE have the same Scheduling Priority Indicator IE value, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If, in the new configuration, the concerned Node B Communication Context is configured to use "Indexed MAC-d PDU Size" for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use Maximum MAC-d PDU Size Extended, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If, in the new configuration, the concerned Node B Communication Context is configured to use "Flexible MAC-d PDU Size" for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use MAC-d PDU Size Index, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If, in the new configuration, the concerned Node B Communication Context is configured to use "Fixed MAC-d PDU Size" for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use  Maximum MAC-d PDU Size Extended, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If, in the new configuration, the concerned Node B Communication Context is configured to use "Flexible MAC-d PDU Size" for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use MAC-d PDU Size List, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the HS-DSCH Information IE and if the Measurement Power Offset IE is not present, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
If the RADIO LINK RECONFIGURATION PREPARE message includes HS-DSCH Information IE and the HS-DSCH is already configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the F-DPCH Information IE and the DL DPCH Information IE configured simultaneously to one downlink frequency, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the concerned the Node B Communication Context is configured to use DPCH in the downlink in the old configuration and the RADIO LINK RECONFIGURATION PREPARE message includes the DL DPCH Power Information IE , then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the concerned Node B Communication Context is configured to use F-DPCH in the downlink in the old configuration and the RADIO LINK RECONFIGURATION PREPARE message includes at least one but not all of the TFCS IE, DL DPCH Slot Format IE, TFCI Signalling Mode IE, Multiplexing Position IE, Limited Power Increase IE and DL DPCH Power Information IE in the DL DPCH Information IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the E-DCH FDD Information IE is present in the RADIO LINK RECONFIGURATION PREPARE message, but the E-DPCH Information IE is not present or if any of the Maximum Set of E-DPDCHs IE, Puncture Limit IE, E-TFCS Information IE, E-TTI IE, E-DPCCH Power Offset IE, E-RGCH 2-Index-Step Threshold IE, E-RGCH 3-Index-Step Threshold IE, HARQ Info for E-DCH IE or HS-DSCH Configured Indicator IE are not present in the E-DPCH Information IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Primary CPICH Usage For Channel Estimation IE and/or Secondary CPICH Information Change IE and if in the new configuration Node B shall assume that the UE is not using the Primary CPICH for channel estimation nor the Secondary CPICH, Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes one of the Not Used IEs, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH RL Indication IE set to "E-DCH", but no E-DCH FDD Information IE, and the Node B Communication Context is not configured for E-DCH, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH FDD Information IE but no E-DCH RL Indication IE set to "E-DCH", then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
If the RADIO LINK RECONFIGURATION PREPARE message does not contain the E-DCH Decoupling Indication IE but contains the HS-PDSCH RL ID IE and/or the Serving E-DCH RL IE, and if both HS-DSCH and E-DCH are configured in the new configuration but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not in the same cell, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the HS-PDSCH RL ID IE and the E-DPCH Information IE which includes the HS-DSCH Configured Indicator IE set as “HS-DSCH not configured” then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains any of the E-DCH FDD Information To Modify IE, E-DCH MAC-d Flows To Add IE or E-DCH MAC-d Flows To Delete IE in addition to the E-DCH FDD Information IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains any of the E-DCH FDD Information To Modify IE, E-DCH MAC-d Flows To Add IE, E-DCH MAC-d Flows To Delete IE and the Node B Communication Context is not configured for E-DCH, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH FDD Information To Modify IE deleting the last remaining E-DCH Logical Channel of an E-DCH MAC-d Flow, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes E-DCH FDD Information IE and the E-DCH is already configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[TDD - if the radio link was not previously configured to support E-DCH, then if the RADIO LINK RECONFIGURATION PREPARE message includes one of the following E-DCH information elements then it shall contain all of them otherwise the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.: E-DCH Serving RL IE, [3.84Mcps TDD and 7.68Mcps TDD - E-PUCH Information IE, E-TFCS Information TDD IE], [1.28Mcps TDD - E-PUCH Information LCR IE, E-TFCS Information TDD IE], E-DCH MAC-d Flows to Add IE, and [3.84Mcps TDD - E-DCH TDD Information IE], [1.28Mcps TDD - E-DCH TDD Information LCR IE] [7.68Mcps TDD - E-DCH TDD Information 7.68Mcps IE].]
[FDD - If the Fast Reconfiguration IE is included in the RADIO LINK RECONFIGURATION PREPARE message and the UL Scrambling Code IE does not indicate an uplink scrambling code different from the currently used uplink scrambling code the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity DTX-DRX Information To Modify IE in addition to the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE in addition to the Continuous Packet Connectivity HS-SCCH less Information IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE while the Continuous Packet Connectivity HS-SCCH less configuration isn’t configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity DTX-DRX Information To Modify IE while the Continuous Packet Connectivity DTX-DRX configuration isn’t configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the DRX Information To Modify IE in Continuous Packet Connectivity DTX-DRX Information To Modify IE while the Continuous Packet Connectivity DRX configuration isn’t configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH Indicator IE set to "Uplink DCH only" but no Transport Format Set IE for the uplink for this DCH and the Node B had ignored the configuration of Transport Format Set for uplink, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH Indicator IE set to "Downlink DCH only" but no Transport Format Set IE for the downlink for this DCH and the Node B had ignored the configuration of Transport Format Set for downlink, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the Transport Bearer Not Requested Indicator IE for a DCH but does not contain the corresponding DCH ID IE and the Unidirectional DCH indicator IE set to "Uplink DCH only" for the DCH in DCH Information To Add IE, the Node B shall reject the procedure using the the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the concerned Node B Communication Context is configured to apply UL DPCCH Slot Format 4 but is not configured to use F-DPCH, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the concerned Node B Communication Context is configured to apply UL DPCCH Slot Format 0 or 2 and execute Continuous Packet Connectivity DTX-DRX operation, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the concerned Node B Communication Context is configured to apply the "Closed loop mode 1" and if the concerned Node B Communication Context is not configured to apply UL DPCCH Slot Format 2 or 3, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the concerned Node B Communication Context is configured to apply MIMO, allowed to apply 64 QAM, establish the the secondary serving HS-DSCH Radio Link or apply Single Stream MIMO in the new configuration but is not configured to use flexible MAC-d PDU Size, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Transport Bearer Not Requested Indicator IE for a DCH in the RL Specific DCH Information IE but does not include the DCH ID IE for the DCH in the DCHs to Add IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD – If the RADIO LINK RECONFIGURATION PREPARE message contains the Continuous Packet Connectivity DTX-DRX Information IE but does not contain the F-DPCH Information IE and the concerned Node B Communication Context is not previously configured to use F-DPCH, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the concerned Node B Communication Context is configured to have the Serving E-DCH Radio Link but there is at least one E-DCH MAC-d flow which the Transport Bearer is not configured in the Node B, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Transport Bearer Not Requested Indicator IE for a DCH for a specific RL and the specific RL is combined with existing RL which the transport bearer is established for the DCH in the Node B, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
If ALCAP is not used, if the concerned Node B Communication Context is configured to establish a DCH, an E-DCH  MAC-d flow and/or an HS-DSCH MAC-d flow but the RADIO LINK RECONFIGURATION PREPARE message does not include the Transport Layer Address IE and the Binding ID IE for the DCH, the E-DCH MAC-d flow and/or the HS-DSCH MAC-d flow, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[TDD - If ALCAP is not used, if the concerned Node B Communication Context is configured to establish a DSCH and/or a USCH  but the RADIO LINK RECONFIGURATION PREPARE message does not include the Transport Layer Address IE and the Binding ID IE for the DSCH and/or the USCH, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Semi-Persistent scheduling Information to Modify LCR IE in addition to the HS-DSCH Semi-Persistent scheduling Information LCR IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Semi-Persistent scheduling Information to Modify LCR IE in addition to the E-DCH Semi-Persistent scheduling Information LCR IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
If, in the new configuration, there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use “Flexible RLC PDU Size” for an HS-DSCH but is not configured to use Maximum MAC-d PDU Size Extended, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If, in the new configuration, the concerned Node B Communication Context is configured to use  MAC-d PDU Size Index for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use “Flexible RLC PDU Size”, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH FDD Secondary Serving Information IE but does not contain the C-ID IE in the Additional HS Cell Information RL Reconf Prep IE or the message includes the C-ID IE but does not contain the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Prep IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains a MIMO Activation Indicator IE and a Single Stream MIMO Activation Indicator IE in the HS-DSCH FDD Information IE or in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Prep IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains more than one of a MIMO Activation Indicator IE, a Single Stream MIMO Activation Indicator IE, a MIMO with four transmit antennas Activation Indicator IE, a Dual Stream MIMO with four transmit antennas Activation Indicator IE in the HS-DSCH FDD Information IE or in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Prep IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the concerned Node B Communication Context is configured to apply MIMO and Single Stream MIMO for the HS-DSCH Radio Link or the Secondary Serving Radio link, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the Diversity Mode IE in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Prep IE and the secondary serving HS-DSCH is already configured in the Node B Communication Context, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the secondary serving HS-DSCH is not configured in the Node B Communication Context and if the RADIO LINK RECONFIGURATION PREPARE message contains in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Prep IE the Diversity Mode IE not set to "None" but not the Transmit Diversity Indicator or contains the Transmit Diversity Indicator but not the Diversity Mode IE not set to "None", then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the Diversity Mode IE in the Secondary Serving Information To Modify IE in the Additional HS Cell Information RL Reconf Prep IE and the Non Cell Specific Tx Diversity IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the Additional E-DCH Cell Information RL Reconf Prep IE and if the E-DPCH Information IE is not present or the E-DPCH Information was not configured in the Node B Communication Context, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the Additional E-DCH Cell Information RL Reconf Prep IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE in the Additional E-DCH Cell Information RL Reconf Prep IE and the C-ID IE is not included but the Radio Link indicated by the E-DCH Additional RL ID IE is not configured in the current Node B Communication Context as a Secondary Serving HS-DSCH radio link without any configured Additional E-DCH, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the Additional HS Cell Information RL Reconf Prep IE and the new configuration contains more than one secondary serving HS-DSCH RL, and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1", which are previously assigned to the RL or received in the Ordinal Number Of Frequency IE in the HS-DSCH FDD Secondary Serving Information IE or the HS-DSCH FDD Secondary Serving Information To Modify IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the Additional HS Cell Information RL Reconf Prep IE and the new configuration contains more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value “1”, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the UL CLTD Information IE but does not contain the F-TPICH Information IE, or if it contains HS-DSCH Preconfiguration Setup IE with UL CLTD Information IE but without F-TPICH Information IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the UL MIMO Reconfiguration IE in E-DCH FDD Information IE, and the choice of Setup, Configuration Change or Removal of UL MIMO is "Setup", but the UL CLTD Information IE is not present and is not previously configured, or if it contains HS-DSCH Preconfiguration Setup IE with UL MIMO Information IE but without UL CLTD Information IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains more than one of a MIMO Activation Indicator IE, a MIMO with four transmit antennas Activation Indicator IE, a Dual Stream MIMO with four transmit antennas Activation Indicator IE in HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the DCH Enhancements Information IE, and either the DL DPCH Slot Format IE is not set to “17” or “18”, or the UL DPCCH Slot Format IE is not set to “5”, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message does not contain the DCH Enhancements Information IE, and either (i) the DL DPCH Slot Format IE is set to “17”, or (ii) the DL DPCH Slot Format IE is set to “18”, or (iii) the UL DPCCH Slot Format IE is set to “5”, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the Fast TTI switching Mode Requested UnSynchronized IE in the E-DCH FDD Information To Modify IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
8.3.3	Synchronised Radio Link Reconfiguration Commit
8.3.3.1	General
This procedure is used to order the Node B to switch to the new configuration for the Radio Link(s) within the Node B, previously prepared by the Synchronised Radio Link Reconfiguration Preparation procedure.
When Mode 1 is used for the fast TTI switching, the procedure shall if supported be used to order the Node B to execute the TTI switching process.
The message shall use the Communication Control Port assigned for this Node B Communication Context.
8.3.3.2	Successful Operation

Figure 32: Synchronised Radio Link Reconfiguration Commit procedure, Successful Operation
[FDD - If the Activation Delay IE is included in the RADIO LINK RECONFIGURATION COMMIT message, the Node B shall if supported send the HS-SCCH order to execute the TTI switching process according to TS 25.214 [10]. The CFN IE in the RADIO LINK RECONFIGURATION COMMIT message shall be ignored by the Node B.]
The Node B shall switch to the new configuration previously prepared by the Synchronised Radio Link Reconfiguration Preparation procedure
-	[TDD - at the next coming CFN with a value equal to the value requested by the CRNC in the CFN IE (see ref. TS 25.402 [17] subclause 9.4) when receiving the RADIO LINK RECONFIGURATION COMMIT message from the CRNC.]
-	[FDD - if the Fast Reconfiguration IE is not included in the RADIO LINK RECONFIGURATION COMMIT message at the next coming CFN with a value equal to the value requested by the CRNC in the CFN IE (see ref. TS 25.402 [17] subclause 9.4) when receiving the RADIO LINK RECONFIGURATION COMMIT message from the CRNC.]
-	[FDD - if the Fast Reconfiguration IE is included in the RADIO LINK RECONFIGURATION COMMIT message as soon as the Node B detects that the UE uses the new configuration in the uplink (e.g. the Node B detects that the UE uses the new scrambling code used for the uplink by sending the RADIO LINK RESTORATION message). In order to limit the period for the detection in the Node B the CFN in the RADIO LINK RECONFIGURATION COMMIT message indicates the earliest possible time instant at which the UE might use the new configuration.]
[FDD - If the Active Pattern Sequence Information IE is included in the RADIO LINK RECONFIGURATION COMMIT message, the CM Configuration Change CFN IE in the Active Pattern Sequence Information IE shall be ignored by the Node B.]
[FDD - If the Active Pattern Sequence Information IE is not included in the RADIO LINK RECONFIGURATION COMMIT message and a new Compressed Mode Configuration exists in the prepared configuration, the Node B shall behave as if an Active Pattern Sequence Information IE with an empty Transmission Gap Pattern Sequence Status IE was included.]
When this procedure has been completed the Prepared Reconfiguration does not exist any more, see subclause 3.1.
In the case of a Transport Channel or MAC-d flow modification for which a new transport bearer was requested and established, the switch to the new transport bearer shall also take place at the configuration switching point (defined above). The detailed frame protocol handling during transport bearer replacement is described in TS 25.427 [16], subclause 5.10.1 and in TS 25.435 [24], subclauses 5.8.2 and 5.8.3.
In the case of a signalling bearer re-arrangement, the new Communication Control Port shall be used once the Node B has received the RADIO LINK RECONFIGURATION COMMIT message via the old Communication Control Port.
[FDD - If the RADIO LINK RECONFIGURATION COMMIT includes the Active Pattern Sequence Information IE, the Node B shall deactivate all the ongoing Transmission Gap Pattern Sequences at the configuration switching point (defined above). From that moment on, all Transmission Gap Pattern Sequences included in Transmission Gap Pattern Sequence Status IE repetitions shall be started when the indicated TGCFN IE elapses. The CFN IE and TGCFN IE for each sequence refer to the next coming CFN with that value. If the values of the CFN IE and the TGCFN IE are equal, the concerned Transmission Gap Pattern Sequence shall be started immediately at the CFN with a value equal to the value received in the CFN IE.]
[FDD - If the RADIO LINK RECONFIGURATION COMMIT message includes the Active Pattern Sequence Information IE and the concerned Node B Communication Context is configured to use F-DPCH in the downlink, the Node B shall not transmit the F-DPCH during the downlink transmission gaps according to TS 25.211 [7]. But in all slots outside of the downlink transmission gaps the Node B shall transmit the F-DPCH with the normal scrambling code and the assigned slot format, regardless of the configured downlink compressed mode method information and of the transmission gap pattern sequence code information, if existing.]
[FDD - If the RADIO LINK RECONFIGURATION COMMIT message includes the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with C-ID IE included in Affected HS-DSCH serving cell List IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.]
8.3.3.3	Abnormal Conditions
If a new transport bearer is required for the new reconfiguration and it is not available at the configuration switching point (defined above), the Node B shall initiate the Radio Link Failure procedure.
[FDD - If the Fast Reconfiguration IE is included in the RADIO LINK RECONFIGURATION COMMIT message and the Node B did not include the Fast ReconfigurationPermission IE in the RADIO LINK RECONFIGURATION READY message, the Node B shall initiate the Radio Link Failure procedure.]
[FDD - If the RADIO LINK RECONFIGURATION COMMIT message includes the Active Pattern Sequence Information IE which activates a downlink transmission gap pattern sequence with an SF/2 downlink compressed mode method and if the concerned Node B Communication Context is configured to use DPCH in downlink and for any Radio Link the transmission gap pattern sequence code information is not available, the Node B shall trigger the Radio Link Failure procedure with the cause value “Invalid CM Settings”.]
[FDD - If the RADIO LINK RECONFIGURATION COMMIT message contains the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE and theTransmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the Node B shall reject the procedure using the RADIO LINK FAILURE message with the cause value “Invalid CM settings”.]
[FDD - If the RADIO LINK RECONFIGURATION COMMIT message contains the Activation Delay IE but the Fast TTI switching Mode Requested Synchronized IE is not presented in the RADIO LINK RECONFIGURATION PREPARE or the Mode 1 is not supported, the Node B shall initiate the Radio Link Failure procedure.]
8.3.4	Synchronised Radio Link Reconfiguration Cancellation
8.3.4.1	General
This procedure is used to order the Node B to release the new configuration for the Radio Link(s) within the Node B, previously prepared by the Synchronised Radio Link Preparation Reconfiguration procedure.
The message shall use the Communication Control Port assigned for this Node B Communication Context.
8.3.4.2	Successful Operation

Figure 33:Synchronised Radio Link Reconfiguration Cancellation procedure, Successful Operation
When receiving the RADIO LINK RECONFIGURATION CANCEL message from the CRNC, the Node B shall release the new configuration ([FDD - including the new Transmission Gap Pattern Sequence parameters (if existing)]) previously prepared by the Synchronised Radio Link Reconfiguration Preparation procedure and continue using the old configuration. When this procedure has been completed the Prepared Reconfiguration does not exist any more, see subclause 3.1.
8.3.4.3	Abnormal Conditions
-
8.3.5	Unsynchronised Radio Link Reconfiguration
8.3.5.1	General
The Unsynchronised Radio Link Reconfiguration procedure is used to reconfigure Radio Link(s) related to one UE-UTRAN connection within a Node B.
The Unsynchronised Radio Link Reconfiguration procedure is used when there is no need to synchronise the time of the switching from the old to the new configuration in one Node B used for a UE-UTRAN connection with any other Node B also used for the UE–UTRAN connection.
The Unsynchronised Radio Link Reconfiguration procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
8.3.5.2	Successful Operation

Figure 34: Unsynchronised Radio Link Reconfiguration Procedure, Successful Operation
The Unsynchronised Radio Link Reconfiguration procedure is initiated by the CRNC by sending the RADIO LINK RECONFIGURATION REQUEST message to the Node B. The message shall use the Communication Control Port assigned for this Node B Communication Context.
Upon reception, the Node B shall modify the configuration of the Radio Link(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications.
The Node B shall prioritise resource allocation for the RL(s) to be modified according to Annex A.
If the UE Aggregate Maximum Bit Rate IE is contained in the RADIO LINK RECONFIGURATION REQUEST message, the Node B shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE.
DCH Modification:
If the RADIO LINK RECONFIGURATION REQUEST message includes any DCHs To Modify IE then the Node B shall treat them each as follows:
-	If the DCHs To Modify IE includes the Frame Handling Priority IE, the Node B should store this information for this DCH in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the Uu interface in congestion situations within the Node B once the new configuration has been activated.
-	If the DCHs To Modify IE includes the TNL QoS IE for a DCH or a set of co-ordinated DCHs to be modified and if ALCAP is not used, the Node B may store this information for this DCH in the new configuration. The TNL QoS IE may be used to determine the transport bearer characteristics to apply for the uplink between the Node B and the CRNC for the related DCH or set of co-ordinated DCHs.
-	If the DCHs To Modify IE includes the Transport Format Set IE for the UL, the Node B shall apply the new Transport Format Set in the Uplink of this DCH in the new configuration.
-	If the DCHs To Modify IE includes the Transport Format Set IE for the DL, the Node B shall apply the new Transport Format Set in the Downlink of this DCH in the new configuration.
-	If the DCHs To Modify IE includes the Allocation/Retention Priority IE for a DCH, the Node B shall apply the new Allocation/Retention Priority to this DCH in the new configuration according to Annex A.
-	If the DCHs To Modify IE includes multiple DCH Specific Info IEs, then the Node B shall treat the DCHs in the DCHs To Modify IE as a set of co-ordinated DCHs. The Node B shall include these DCHs in the new configuration only if it can include all of them in the new configuration.
-	[FDD - If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH indicator IE set to "Uplink DCH only", the Node B shall ignore the Transport Format Set IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.]
-	[FDD - If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH indicator IE set to "Downlink DCH only", the Node B shall ignore the Transport Format Set IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.]
-	If the DCHs To Modify IE includes the UL FP Mode IE for a DCH or a set of co-ordinated DCHs, the Node B shall apply the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
-	If the DCHs To Modify IE includes the ToAWS IE for a DCH or a set of co-ordinated DCHs, the Node B shall apply the new ToAWS in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
-	If the DCHs To Modify IE includes the ToAWE IE for a DCH or a set of co-ordinated DCHs, the Node B shall apply the new ToAWE in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
-	[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the CCTrCH ID IE for the DL of a DCH to be modified, the Node B shall apply the new CCTrCH ID in the Downlink of this DCH in the new configuration.]
-	[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the CCTrCH ID IE for the UL of a DCH to be modified, the Node B shall apply the new CCTrCH ID in the Uplink of this DCH in the new configuration.]
DCH Addition:
If the RADIO LINK RECONFIGURATION REQUEST message includes any DCH To Add IE, the Node B shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message and include these DCHs in the new configuration. In particular:
-	If a DCHs To Add IE includes multiple DCH Specific Info IEs for a DCH to be added, the Node B shall treat the DCHs in the DCHs To Add IE as a set of co-ordinated DCHs. The Node B shall include these DCHs in the new configuration only if it can include all of them in the new configuration.
-	If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to "Uplink DCH only", the Node B shall ignore the Transport Format Set IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.
-	If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to "Downlink DCH only", the Node B shall ignore the Transport Format Set IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.
-	[FDD - For DCHs which do not belong to a set of co-ordinated DCHs with the QE-Selector IE set to "selected", the Node B shall use the Transport channel BER from that DCHas the base for the QE in the UL data frames. If no Transport channel BER is available for the selected DCH, the Physical channel BER shall be used for the QE TS 25.427 [16]. If the QE-Selector IE is set to "non-selected", the Physical channel BER shall be used for the QE in the UL data frames, ref. TS 25.427 [16].]
-	For a set of co-ordinated DCHs, the Node B shall use the Transport channel BER from the DCH with the QE-Selector IE set to "selected" as the QE in the UL data frames TS 25.427 [16]. [FDD - If no Transport channel BER is available for the selected DCH, the Physical channel BER shall be used for the QE TS 25.427 [16]. If all DCHs have the QE-Selector IE set to "non-selected", the Physical channel BER shall be used for the QE TS 25.427 [16].]
-	The Node B should store the Frame Handling Priority IE received for a DCH to be added in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the Uu interface in congestion situations within the Node B once the new configuration has been activated.
-	If the TNL QoS IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the Node B may store this information for this DCH in the new configuration. The TNL QoS IE may be used to determine the transport bearer characteristics to apply for the uplink between the Node B and the CRNC for the related DCH or set of co-ordinated DCHs.
-	The Node B shall use the included UL FP Mode IE for a DCH or a set of co-ordinated DCHs to be added as the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
-	The Node B shall use the included ToAWS IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Startpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
-	The Node B shall use the included ToAWE IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Endpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.
-	[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the CCTrCH ID IE for the DL of a DCH to be added, the Node B shall apply the new CCTrCH ID in the downlink of this DCH in the new configuration.]
-	[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the CCTrCH ID IE for the UL of a DCH to be added, the Node B shall apply the new CCTrCH ID in the Uplink of this DCH in the new configuration.]
DCH Deletion:
If the RADIO LINK RECONFIGURATION REQUEST message includes any DCH to be deleted from the Radio Link(s), the Node B shall not include this DCH in the new configuration.
If all of the DCHs belonging to a set of co-ordinated DCHs are requested to be deleted, the Node B shall not include this set of co-ordinated DCHs in the new configuration.
[FDD - Physical Channel Modification]:
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an UL DPCH Information IE, then the Node B shall apply the parameters to the new configuration as follows:]
-	[FDD - If the UL DPCH Information IE includes the TFCS IE for the UL, the Node B shall apply the new TFCS in the Uplink of the new configuration.]
-	[FDD - If the UL DPCH Information IE includes the UL DPDCH Indicator For E-DCH Operation IE set to "UL DPDCH not present", the UL DPDCH resources shall be removed from the configuration.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes a DL DPCH Information IE, then the Node B shall apply the parameters to the new configuration as follows:]
-	[FDD - If the DL DPCH Information IE includes on the TFCS IE for the DL, the Node B shall apply the new TFCS in the Downlink of the new configuration.]
-	[FDD - If the DL DPCH Information IE includes the TFCI Signalling Mode IE, the Node B shall use the information when building TFCIs in the new configuration.
-	[FDD - If the DL DPCH Information IE includes the Limited Power Increase IE set to "Used", the Node B shall, if supported, use Limited Power Increase according to ref. TS 25.214 [10] subclause 5.2.1 for the inner loop DL power control in the new configuration.]
-	[FDD - If the DL DPCH Information IE includes the Limited Power Increase IE set to "Not Used", the Node B shall not use Limited Power Increase for the inner loop DL power control in the new configuration.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Transmission Gap Pattern Sequence Information IE, the Node B shall store the new information about the Transmission Gap Pattern Sequences to be used in the new Compressed Mode Configuration. Any Transmission Gap Pattern Sequences already existing in the previous Compressed Mode Configuration are replaced by the new sequences once the new Compressed Mode Configuration has been activated. This new Compressed Mode Configuration shall be valid in the Node B until the next Compressed Mode Configuration is configured in the Node B or Node B Communication Context is deleted.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity DTX-DRX Information IE, then:]
-	[FDD - The Node B shall configure the concerned Node B Communication Context for DTX operation according to TS 25.214 [10].]
-	[FDD - If DRX Information IE is included in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].]
-	[FDD - If UE DRX Cycle 2 IE is included in the DRX Information IE in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].]
-	[FDD - If Inactivity Threshold for UE DRX Cycle 2 IE is included in the DRX Information IE in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for DRX operation according to TS 25.214 [10].]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then:]
-	[FDD - If the UE DTX DRX Offset IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the Node B shall apply the indicated Offset in UE DTX DRX Cycle IE in the new configuration.]
-	[FDD - If the Enabling Delay IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the Node B shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.214 [10].]
-	[FDD - If the DTX Information To Modify IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the Node B shall use this information to modify the indicated DTX Information parameter in the new configuration. If the choice of DTX Information To Modify IE is "Deactivate", then DRX should be deactived together with DTX.]
-	[FDD - If the DRX Information To Modify IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the Node B shall use this information to modify the indicated DRX Information in the new configuration.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity HS-SCCH less Information IE, then:]
-	[FDD - The Node B shall configure the Serving HS-DSCH Radio Link for Continuous Packet Connectivity HS-SCCH less operation in the new configuration according to TS 25.214 [10].]
-	[FDD - The Node B shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the Continuous Packet Connectivity HS-SCCH less Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If at least one of  HS-PDSCH Second Code Support IE is set to "True", then the Node B shall include HS-PDSCH Second Code Index IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE, then the Node B shall deactivate the Continuous Packet Connectivity HS-SCCH less operation for the HS-DSCH Radio Link.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity DRX Information LCR IE, then the Node B shall take account into these parameters to decide the DRX operation related parameters and configure the concerned Node B Communication Context for DRX operation according to TS 25.224 [21] and include the parameter(s) in the Continuous Packet Connectivity DRX Information Response LCR IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity DRX Information To Modify LCR IE, then:]
-	[1.28 Mcps TDD - If the UE DTX DRX Offset IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the Node B shall apply the indicated Offset in UE DTX DRX Cycle IE in the new configuration.]
-	[1.28 Mcps TDD - If the Enabling Delay IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the Node B shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [21].]
-	[1.28 Mcps TDD - If the DRX Information To Modify IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the Node B shall use this information to modify the indicated DRX Information in the new configuration.]
-	[1.28 Mcps TDD - If the Inactivity Threshold for UE DRX Cycle Ext IE is included in the Continuous Packet Connectivity DRX Information LCR IE, then the Node B may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [21].]
	[1.28 Mcps TDD - If the Enabling Delay Ext IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the Node B may use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [21].]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH Semi-Persistent scheduling Information LCR IE, then:]
-	[1.28 Mcps TDD - The Node B shall configure the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [21].]
-	[1.28 Mcps TDD - The Node B shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the HS-DSCH Semi-Persistent scheduling Information Response LCR IE in the RADIO LINK RECONFIGURATION READY message.]
-	[1.28 Mcps TDD - If the HS-DSCH Semi-Persistent Resource Reservation Indicator IE is included in the HS-DSCH Semi-Persistent scheduling Information LCR IE, then the Node B shall include Allcoated HS-PDSCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Semi-Persistent scheduling Information LCR IE, then:]
-	[1.28 Mcps TDD - The Node B shall configure the Serving E-DCH Radio Link indicated by the E-DCH Serving RL IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [21].]
-	[1.28 Mcps TDD - If the E-DCH Semi-Persistent Resource Reservation Indicator IE is included in the E-DCH Semi-Persistent scheduling Information LCR IE, then the Node B shall include Allcoated E-DCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH Semi-Persistent scheduling Information to modify LCR IE, then:]
-	[1.28 Mcps TDD - If the Transport Block Size List IE or/and Repetition Period list IE is/are included in the HS-DSCH Semi-Persistent scheduling Information to modify LCR IE, the Node B shall modifiy the configuration of Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [21].
-	[1.28 Mcps TDD - If the Buffer Size for HS-DSCH Semi-Persistent scheduling IE is included in the HS-DSCH Semi-Persistent scheduling Information to modify LCR IE, the Node B shall use this information to modify the buffer size for HS-DSCH Semi-Persistent scheduling operation.
-	[1.28 Mcps TDD - If the Number of Processes for HS-DSCH Semi-Persistent scheduling IE is included in the HS-DSCH Semi-Persistent scheduling Information to modify LCR IE, the Node B shall use this information to allocate the number of processes for HS-DSCH Semi-Persistent scheduling operation.
-	[1.28 Mcps TDD - The Node B shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the HS-DSCH Semi-Persistent scheduling Information Response LCR IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[1.28 Mcps TDD - If the HS-DSCH Semi-Persistent Resource Reservation Indicator IE is included in the HS-DSCH Semi-Persistent scheduling Information to modify LCR IE, then the Node B shall include Allcoated HS-PDSCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
	[1.28 Mcps TDD - If the HS-DSCH Semi-Persistent scheduling operation Indicator IE is included in the HS-DSCH Semi-Persistent scheduling Information to modify LCR IE, then the Node B shall apply this information for HS-DSCH Semi-Persistent scheduling operation.]
-	[1.28 Mcps TDD - If the buffer size for HS-DSCH Semi-Persistent scheduling needs to be modified, then the Node B shall include the Buffer Size for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[1.28 Mcps TDD - If the number of processes for HS-DSCH Semi-Persistent scheduling needs to be modified, then the Node B shall include the Number of Processes for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Semi-Persistent scheduling Information to modify LCR IE, then:]
-	[1.28 Mcps TDD - If the Repetition Period list IE is included in the E-DCH Semi-Persistent scheduling Information to modify LCR IE, the Node B shall modifiy the configuration of Serving E-DCH Radio Link indicated by the E-DCH Serving RL IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [21].
	[1.28 Mcps TDD - If the E-DCH Semi-Persistent scheduling Indicator IE is included in the E-DCH Semi-Persistent scheduling Information to modify LCR IE, then the Node B shall apply this information for E-DCH Semi-Persistent scheduling operation.]
-	[1.28 Mcps TDD - If the Semi-Persistent E-DCH releted E-HICH Information IE is included in the E-DCH Semi-Persistent scheduling Information to modify LCR IE, then the Node B shall use this information to modify the configuration of Semi-Persistent E-DCH releted E-HICH.]
-	[1.28 Mcps TDD - If the E-DCH Semi-Persistent Resource Reservation Indicator IE is included in the E-DCH Semi-Persistent scheduling Information to modify LCR IE, then the Node B shall include Allcoated E-DCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR IE, then the Node B shall deactivate the HS-DSCH Semi-Persistent scheduling operation for the HS-DSCH Radio Link.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Semi-Persistent scheduling Deactivate Indicator LCR IE, then the Node B shall deactivate the E-DCH Semi-Persistent scheduling operation for the E-DCH Radio Link.]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the MU-MIMO Information IE, then:]
-	[1.28 Mcps TDD - The Node B can activate MU-MIMO operation on Uplink and/or Downlink indicated by the MU-MIMO indicator IE and shall include the MU-MIMO Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[1.28 Mcps TDD - If the Standalone Midamble Channel Information IE is included in the MU-MIMO Information IE, then the Node B shall configure the concerned Node B Communication Context for standalone midamble related operation according to TS 25.224 [21].]
-	[1.28 Mcps TDD - If the Standalone Midamble Channel Information request IE is included in the MU-MIMO Information IE, if the Node B will use MU-MIMO and if the Node B can allocate the standalone midamble resource, then the Node B shall include the Standalone Midamble Channel Information IE in the MU-MIMO Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message, else the Node B shall not include the Standalone Midamble Channel Information IE in the MU-MIMO Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message].
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the MU-MIMO Information To Reconfigure IE, then:]
-	[1.28Mcps TDD - If the choice of MU-MIMO Information To Reconf  IE is "Modify", then the Node B shall use this information to modify the indicated MU-MIMO Information parameter in the new configuration.]
-	[1.28Mcps TDD - If the choice of MU-MIMO Information To Reconf  IE is "Continue", then the Node B shall continue using the old configuration for MU-MIMO operation.]
[FDD - E-DPCH Handling]:
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an E-DPCH Information IE which contains the E-TFCS Information IE, the Node B shall use the E-TFCS Information IE for the E-DCH when reserving resources for the uplink of the new configuration. The Node B shall apply the new TFCS in the uplink of the new configuration. If the E-TFCS Information IE contains the E-DCH Minimum Set E-TFCI IE the Node B shall use the value for the related resource allocation operation.]
[FDD - If the E-TFCS Information IE in the E-DPCH Information IE contains the E-DPDCH Power Interpolation IE, the Node B shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the E-DPDCH Power Interpolation IE is not present, the Node B shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10] if the E-DCH FDD Information IE is included in the RADIO LINK RECONFIGURATION REQUEST message.]
[FDD - If the E-TFCS Information IE in the E-DPCH Information IE contains the E-TFCI Boost Information IE, the Node B shall use the information according to TS 25.214 [10]. If the E-TFCI Boost Information IE is not present, the Node B shall use the E-TFCI BetaEC Boost value "127" in the algorithm defined in TS 25.214 [10] if the E-DCH FDD Information IE is included in the RADIO LINK RECONFIGURATION PREPARE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST includes an E-DPCH Information IE which contains the E-DPCCH Power Offset IE, the Node B shall use the value when the new configuration is being used.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST includes an E-DPCH Information IE which contains the E-RGCH 2-Index-Step Threshold IE, the Node B shall use the value when the new configuration is being used.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST includes an E-DPCH Information IE which contains the E-RGCH 3-Index-Step Threshold IE, the Node B shall use the value when the new configuration is being used.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST includes an E-DPCH Information IE which contains the HARQ Info for E-DCH  IE, the Node B shall use the value when the new configuration is being used.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST includes an E-DPCH Information IE which contains the Minimum Reduced E-DPDCH Gain Factor IE, then the Node B shall use the value to determine the applicable minimum gain factor (βed,k,reduced,min) defined in TS 25.214 [10]. For the case the Minimum Reduced E-DPDCH Gain Factor IE is not available for the Node B Communication Context, the Node B may use the default value defined in TS 25.331 [18].]
[TDD - UL/DL CCTrCH Modification]
[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes any UL CCTrCH To Modify IE or DL CCTrCH To Modify IE in the Radio Link(s), the Node B shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message.]
[TDD - If the UL CCTrCH To Modify IE or DL CCTrCH To Modify IE includes TFCS IE and/or Puncture Limit IE, the Node B shall apply these as the new values, otherwise the old values specified for this CCTrCH are still applicable.]
[1.28Mcps TDD - If the UL CCTrCH To Modify IE includes UL SIR Target IE, the Node B shall apply this value as the new configuration and use it for the UL inner loop power control according to TS 25.221 [19] and TS 25.224 [21].]
[TDD - UL/DL CCTrCH Deletion]
[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes any UL CCTrCH To Delete IE or DL CCTrCH To Delete IE, the Node B shall not include this CCTrCH in the new configuration.]
[FDD - UL CLTD Setup:]
[FDD - If the UL CLTD Information Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL CLTD is "Setup", then: the Node B shall setup the requested UL CLTD resources for the concerned Node B Communication Context in the cell to determine the precoding weights according the new configuration defined in the UL CLTD Information IE and then:]
-	[FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the concerned Node B Communication Context, the C-ID IE shall be included in the UL CLTD Information IE, and the Node B shall configure this cell to determine the precoding weights for the concerned Node B Communication Context.]
-	[FDD - If the UL CLTD Activation Information IE is included in the UL CLTD Information IE, then the Node B shall use this value to configure the state of UL CLTD for the concerned Node B Communication Context.]
[FDD - UL CLTD Modification:]
[FDD - If the UL CLTD Information Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL CLTD is "Configuration Change", then: the UL CLTD Information To Modify IE defines the new configuration and then:]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the C-ID IE in the UL CLTD Information To Modify IE, then the Node B shall configure this cell to determine the precoding weights for the concerned Node B Communication Context. Otherwise the Node B shall configure the serving E-DCH cell or the HS_DSCH serving cell to determine the precoding weights as specified in TS 25.319[38]. The UL CLTD configuration is only valid for the cell to determine the precoding weights.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the S-DPCCH Power Offset Information IE in the UL CLTD Information To Modify IE, then the Node B shall use this value to determine the S-DPCCH power.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the UL CLTD Activation  Information IE in the UL CLTD Information To Modify IE, then the Node B shall use this value to update the local state of UL CLTD for the concerned Node B Communication Context. If the UL CLTD Activation Information IE is set to "De-activated", the Node B should release the F-TPICH resource configured for the concerned Node B Communication Context.]
[FDD - UL CLTD Removal:]
[FDD - If the UL CLTD Information Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL CLTD is "Removal", then the configured UL CLTD for the concerned Node B Communication Context shall be removed.]
[FDD - UL MIMO Setup:]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the UL MIMO Information IE in the E-DCH FDD Information IE, or the UL MIMO Reconfiguration IE and the choice of Setup, Configuration Change or Removal of UL MIMO is "Setup", then the Node B shall activate UL MIMO operation for the radio link according to the information provided in the IE.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Serving E-DCH RL IE indicating that the Serving E-DCH RL is in this Node B:]
-	[FDD - The Node B shall allocate a Secondary Transport Block E-RNTI for the corresponding RL and include the E-RNTI identifier together with the corresponding E-ROCH Channelization Code in the UL MIMO DL Control Channel Information IE in the RADIO LINK RECONFIGURATION RESPONSE. The E-ROCH Channelization code shall be allocated from the pool of E-AGCH channelization codes configured for that cell.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-ROCH Power Offset IE in the UL MIMO Information IE, then the Node B may use this value to determine the E-ROCH power. The E-ROCH Power Offset should be applied for any E-ROCH transmission to this UE.]
-	[FDD - The Node B may include the the Secondary Transport Block E-HICH Signature Sequence IE in UL MIMO DL Control Channel Information IE in the RADIO LINK RECONFIGURATION RESPONSE message for every RL indicated by the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE and it should include it for the Serving E-DCH RL.]
[FDD – UL MIMO Modification:]
[FDD - If the UL MIMO Reconfiguration IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL MIMO is "Configuration Change", then the UL MIMO Information To Modify IE defines the new configuration.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Serving E-DCH RL IE:]
-	[FDD – If the old Serving E-DCH RL is in this Node B, the Node B shall de-allocate the E-ROCH resources of the old Serving E-DCH RL at the activation of the new configuration.]
- 	[FDD - If the new Serving E-DCH RL is in this Node B:]
-	[FDD - The Node B shall allocate a Secondary Transport Block E-RNTI for the corresponding RL and include the E-RNTI identifier together with the corresponding E-ROCH Channelization Code in the UL MIMO DL Control Channel Information IE in the RADIO LINK RECONFIGURATION RESPONSE. The E-ROCH Channelization code shall be allocated from the pool of E-AGCH channelization codes configured for that cell.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-ROCH Power Offset IE in the UL MIMO Information To Modify IE, then the Node B may use this value to determine the E-ROCH power. The E-ROCH Power Offset should be applied for any E-ROCH transmission to this UE.]
-	[FDD - The Node B may include the the Secondary Transport Block E-HICH Signature Sequence IE or it may alternatively include the Secondary Transport Block E-HICH Release Indicator IE in UL MIMO DL Control Channel Information IE in the RADIO LINK RECONFIGURATION RESPONSE message for every RL indicated by the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE and it should include it for the Serving E-DCH RL.]
[FDD - UL MIMO Removal:]
[FDD - If the UL MIMO Reconfiguration IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL MIMO is "Removal", then the configured UL MIMO for the concerned Node B Communication Context shall be removed.]
DL Power Control:
-	[FDD - If the Radio Link Information IE includes the DL Reference Power IE and the power balancing is active, the Node B shall update the reference power of the power balancing in the indicated RL(s), if updating of power balancing parameters by the RADIO LINK RECONFIGURATION REQUEST message is supported, using the DL Reference Power IE in the RADIO LINK RECONFIGURATION REQUEST message. The updated reference power shall be used from the next adjustment period.]
[FDD - If updating of power balancing parameters by the RADIO LINK RECONFIGURATION REQUEST message is supported by the Node B, the Node B shall include the DL Power Balancing Updated Indicator IE in the RL Information Response IE for each affected RL in the RADIO LINK RECONFIGURATION RESPONSE message.]
RL Information:
If the RADIO LINK RECONFIGURATION REQUEST message includes the RL Information IE, the Node B shall treat it as follows:
-	[FDD - If the RL Information IE includes the Maximum DL Power IE, the Node B shall apply this value to the new configuration and not transmit with a higher power on any Downlink DPCH or on the F-DPCH of the Radio Link once the new configuration is being used. During compressed mode, the tPcurr, as described in ref. TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.]
-	[FDD - If the RL Information IE includes the Minimum DL Power IE, the Node B shall apply this value to the new configuration and never transmit with a lower power on any Downlink Channelisation Code or on the FDPCH of the Radio Link once the new configuration is being used.]
-	[3.84 Mcps TDD and 7.68Mcps TDD - If the CCTrCH Maximum DL Transmission Power IE and/or the CCTrCH Minimum DL Transmission Power IE are included, the Node B shall apply the values in the new configuration for this DCH type CCTrCH, if the RL Information IE includes Maximum Downlink Power and/or the Minimum Downlink Power IEs, the Node B shall apply the values in the new configuration for all other DCH type CCTrCHs.]
-	[3.84 Mcps TDD and 7.68Mcps TDD - The maximum power and minimum power for a DSCH type CCTrCH to be modified, shall be determined as follows:
-	If the DSCH type CCTrCH is paired with an uplink CCTrCH(s) for inner loop power control, the minimum and maximum power for each PDSCH is determined in the same way as described above for DCH type CCTrCHs.
-	If the DSCH type CCTrCH is not paired with an uplink CCTrCH(s) for inner loop power control, the PDSCH transmission power is DSCH Data Frame Protocol signalled (TS 25.435 [24]), with the maximum value determined in the same way as described above for DCH type CCTrCHs. The minimum power, however, is subject to control by the CRNC via the frame protocol].
-	[1.28 Mcps TDD - If Maximum DL Power IE and/or Minimum DL Power IE are included within DL Timeslot Information LCR IE, the Node B shall apply the values in the new configuration for this timeslot within a DCH type CCTrCH, if the RL Information IE includes Maximum Downlink Power and/or the Minimum Downlink Power IEs, the Node B shall apply the values in the new configuration for all other timeslots.]
-	[1.28 Mcps TDD - If the CCTrCH Maximum DL Transmission Power IE and/or the CCTrCH Minimum DL Transmission Power IE are included, the Node B shall apply the values in the new configuration for this DSCH type CCTrCH, if the RL Information IE includes the Maximum Downlink Power and/or the Minimum Downlink Power IEs, the Node B shall apply the values in the new configuration for other timeslots.]
-	[FDD - If the concerned Node B Communication Context is configured to use DPCH in the downlink and if the RL Information IE contains the Transmission Gap Pattern Sequence Code Information IE in the DL Code Information IE for any of the allocated DL Channelisation Codes, the Node B shall apply the alternate scrambling code as indicated whenever the downlink compressed mode method SF/2 is active in the new configuration.]
-	[1.28Mcps TDD - If the RL Information IE contains the Uplink Synchronisation Parameters LCR IE, the Node B shall use the indicated values of Uplink Synchronisation Stepsize IE and Uplink Synchronisation Frequency IE when evaluating the timing of the UL synchronisation.]
-	[FDD - If the RL Information IE contains the F-DPCH Slot Format IE and if the Node B Communication Context is configured to use F-DPCH in the downlink, then the Node B shall use this information to configure the F-DPCH slot format of each RL according to TS 25.211 [7].]
-	[FDD - If the RL Information IE includes the F-TPICH Information Reconf IE and the choice of Setup, Configuration Change or Removal of F-TPICH Information is "Setup", then the Node B shall use the information in F-TPICH Information IE to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214[10].]
-	[FDD - If the RL Information IE includes the F-TPICH Information Reconf IE and the choice of Setup, Configuration Change or Removal of F-TPICH Information is "Configuration Change", then: the F-TPICH Information To Modify IE defines the new configuration and then:]
-	[FDD - If the F-TPICH Information To Modify IE includes the F-TPICH Slot Format IE, then the Node B shall use this information to configure the F-TPICH slot format according to TS 25.211 [7].
-	[FDD - If the F-TPICH Information To Modify IE includes the F-TPICH Offset IE, the Node B shall use this information to configure the time offset of F-TPICH.]
-	[FDD - If the F-TPICH Information To Modify IE includes the F-TPICH Channelisation Code Number IE, the Node B shall use this information to configure the channelization code of F-TPICH.]
-	[FDD - If the RL Information IE includes the F-TPICH Information Reconf IE and the choice of Setup, Configuration Change or Removal of F-TPICH Information is "Removal", then the Node B shall remove the configured F-TPICH for the RL.]
Signalling Bearer Re-arrangement:
If the RADIO LINK RECONFIGURATION REQUEST message includes the Signalling Bearer Request Indicator IE, the Node B shall allocate a new Communication Control Port for the control of the Node B Communication Context and include the Target Communication Control Port ID IE in the RADIO LINK RECONFIGURATION RESPONSE message.
HS-DSCH Setup:
If the HS-DSCH Information IE is present in the RADIO LINK RECONFIGURATION REQUEST message, then:
-	The Node B shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE.
-	The Node B shall include the HARQ Memory Partitioning IE in the [FDD - HS-DSCH FDD Information Response IE] [TDD - HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION RESPONSE message. [FDD - The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than "8", if the MIMO Activation Indicator IE or MIMO with four transmit antennas Activation Indicator IE, or Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Information IE.] [1.28Mcps TDD- The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than "8", if the MIMO Activation Indicator IE is included in the HS-DSCH Information IE.]
-	If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-hs Guaranteed Bit Rate IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
-	If the RADIO LINK RECONFIGURATION REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
-	If the RADIO LINK RECONFIGURATION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue.
-	The Node B shall include the HS-DSCH Initial Capacity Allocation IE in the [FDD - HS-DSCH FDD Information Response IE] [TDD - HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION RESPONSE message for every HS-DSCH MAC-d flow being established, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK RECONFIGURATION REQUESTmessage includes  HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH  Information IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer received in RADIO LINK RECONFIGURATION REQUEST in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE for a Priority Queue including  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE.
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH Information IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Measurement Power Offset IE in the HS-DSCH Information IE, then the Node B shall use the measurement power offset as described in ref TS 25.214 [10], subclause 6A.2.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - HS-SCCH Specific Information Response IE] [1.28Mcps TDD - HS-SCCH Specific Information Response LCR IE] [7.68Mcps TDD - HS-SCCH Specific Information Response 7.68Mcps IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HARQ Preamble Mode IE in the HS-DSCH Information IE, then the Node B shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the Node B shall include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the HARQ Preamble Mode IE is not included or if the mode 0 is applied, then the Node B shall not include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-SICH SIR Target IE in the HS-DSCH Information IE, the Node B shall use this value to determine the HS-SICH  SIR Target. The HS-SICH SIR Target IE indicates the received UL SIR target of HS-SICH NACK for this UE.]
-	If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH MAC-d PDU Size Format  IE in the HS-DSCH Information IE, then the Node B shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]).
-	[FDD - If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.]
-	[FDD - If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B shall activate the MIMO mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B may if the value is set to "allowed" use 64 QAM for the HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE with value set to "not allowed", then the Node B shall not use 64 QAM for the HS-DSCH Radio Link.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH MAC-d PDU Size Format IE set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - If the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH FDD Information IE, then the Node B may use:]
-	[FDD - a different HS-SCCH in consecutive TTIs for this UE]
-	[FDD - HS-SCCH orders for the case of HS-SCCH-less operation to this UE]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE the Node B may use the supported HSDPA functions for this UE.]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the Node B shall, if supported,  include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK RECONFIGURATION REQUEST message includes the Number of Supported Carriers IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B shall use this information to allocate HSDPA resources over multiple frequencies for UE.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK RECONFIGURATION REQUEST message includes the Multi-carrier HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B shall use this information together with the HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information IE to allocate HSDPA resources over multiple carriers for the UE.]
-	[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B may use this information in HSDPA resources allocation for the UE.]
-	[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the Puncturing Handling in First Rate Matching Stage IE in the HS-DSCH Information IE, then the Node B shall , if supported, apply the puncturing during first stage rate matching according to the Puncturing Handling in First Rate Matching Stage IE.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH over multiple frequencies and include the HS-SCCH Specific Information Response LCR per UARFCN IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B shall include the HARQ Memory Partitioning per UARFCN IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the Node B allows UE to use HSDPA resources distributed over multiple frequencies, the Node B may indicate the number of multiple frequencies actually used by the UE and include the Multi-Carrier number IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
	[1.28 Mcps TDD - If the MIMO Activation Indicator IE is included in the HS-DSCH TDD Information IE, then, the Node B shall activate the MIMO mode for the HS-DSCH Radio Link, decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	If the RADIO LINK RECONFIGURATION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DL RLC PDU Size Format IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24].
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the Priority Queue Information IE in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the Node B shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]
-	[FDD - If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B shall activate the Single Stream MIMO mode for the HS-DSCH Radio Link.]
-	[FDD - If the MIMO with four transmit antennas Activation Indicator IE or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - The Node B may include the Precoder weight set restriction IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the CQI Feedback Cycle2 k IE and the CQI Cycle Switch Timer IE  is included in HS-DSCH FDD Information IE, then the Node B may use the indicated CQI Feedback Cycle2 k value, the CQI Cycle Switch Timer in HSDPA resources allocation for the UE.]
[FDD – Secondary Serving HS-DSCH Setup:]
[FDD – If the C-ID IE is present in the Additional HS Cell Information RL Reconf Req IE in the RADIO LINK RECONFIGURATION REQUEST message, and no secondary serving HS-DSCH Radio Link(s) has been configured in the Node B or if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the Ordinal Number Of Frequency IEs, in the HS-DSCH FDD Secondary Serving Information IE or in the HS-DSCH FDD Secondary Serving Information To ModifyUnsynchronised IE for each instance of the Additional HS Cell Information RL Reconf Req IE, indicate that new secondary serving HS-DSCH Radio Link(s) shall be setup, then:]
-	[FDD – The Node B shall setup the requested HS-PDSCH resources on the secondary serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.]
-	[FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
-	[FDD - If, in the new configuration, the concerned Node B Communication Context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH Radio Link, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - If the MIMO with four transmit antennas Activation Indicator IE or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - The Node B may include the Precoder weight set restriction IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
Intra-Node B Serving HS-DSCH Radio Link Change:
If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-PDSCH RL ID IE, this indicates the new Serving HS-DSCH Radio Link:
-	The Node B shall release the HS-PDSCH resources on the old Serving HS-DSCH Radio Link and setup the HS-PDSCH resources on the new Serving HS-DSCH Radio Link.
-	The Node B may include the HARQ Memory Partitioning IE in the [FDD - HS-DSCH FDD Information Response IE] [TDD - HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION RESPONSE message. [FDD - The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.] [1.28Mcps TDD- The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[TDD - The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD - HS-SCCH Specific Information Response IE] [1.28Mcps TDD - HS-SCCH Specific Information Response LCR IE] [7.68Mcps TDD - HS-SCCH Specific Information Response 7.68Mcps IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.]
-	If a reset of the MAC-hs is not required the Node B shall include the MAC-hs Reset Indicator IE in the RADIO LINK RECONFIGURATION RESPONSE message.
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH Information To Modify IE and the value is set to "allowed" or if HS-DSCH Information To Modify IE is not included and the Node B Communication Context is configured with Sixtyfour QAM allowed for the serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM in the new configuration, then it shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - The Node B may include the Precoder weight set restriction IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
[FDD – Intra-Node B Secondary Serving HS-DSCH Radio Link Change:]
[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the C-ID IE and the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Req IE, one or more secondary serving HS-DSCH Radio Link(s) has been configured in the Node B and if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the Ordinal Number Of Frequency IEs, in the HS-DSCH FDD Secondary Serving Information IE for each instance of the Additional HS Cell Information RL Reconf Req IE, indicate that existing secondary serving HS-DSCH Radio Links shall be subject to intra-Node B secondary serving HS-DSCH Radio Link change and, then the HS-PDSCH RL ID IE indicates the new secondary serving HS-DSCH Radio Link:]
-	[FDD - The Node B shall release the HS-PDSCH resources on the old secondary serving HS-DSCH Radio Link and setup the HS-PDSCH resources on the new secondary serving HS-DSCH Radio Link. The Node B shall remove the old secondary serving HS-PDSCH Radio Link. Non cell specific secondary serving if no E-DCH resources are allocated to the RL. Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]
-	[FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.]
-	[FDD - The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE and the value is set to "allowed" or if HS-DSCH FDD Secondary Serving Information To Modify IE is not included and the Node B Communication Context is configured with Sixtyfour QAM allowed for the secondary serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM for the new secondary serving HS-DSCH Radio Link, then it shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If, in the new configuration, the concerned Node B Communication Context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH Radio Link, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - If the old and/or new configuration contains more than one Secondary Serving HS-DSCH Radio Link the HS-DSCH FDD Secondary Serving Information IE defines the new secondary serving HS-DSCH configuration in the Node B to be used on the new secondary serving HS-DSCH Radio Link, and then:]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
-	[FDD - If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]
-	[FDD - If the MIMO with four transmit antennas Activation Indicator IE or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the MIMO with four transmit antennas mode or the Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - The Node B may include the Precoder weight set restriction IE in the HS-DSCH FDD Secondary Serving Information Response IE  in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
[FDD - Additional Serving E-DCH Radio Link Change to an existing additional non serving E-DCH RL:]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the C-ID IE in the Additional HS Cell Information RL Reconf Req IE and an additional non serving E-DCH RL exists in the cell indicated by the C-ID IE, the HS-PDSCH RL ID IE in the HS Cell Information RL Reconf Req IE indicates the new Additional Serving E-DCH Radio Link.]-	[FDD - If the old Additional Serving E-DCH RL is within this Node B, the Node B shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the E-DCH FDD DL Control Channel Information IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message for the initial grant for the Additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD – The Node B may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the AdditionalModified E-DCH FDD Information Response RL Reconf IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message for every E-DCH Radio Links on secondary UL frequency in the Node B.]
[FDD - Additional Serving E-DCH Radio Link Change to a new RL:]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Additional E-DCH RL Specific Information To Add IE in the Additional E-DCH Configuration Change Information IE in the Additional E-DCH Cell Information RL Reconf Req IE and the C-ID IE in the Additional HS Cell Information RL Reconf Req IE and there is no radio links in the cell indicated by the C-ID IE for the Node B Communication Context, the HS-PDSCH RL ID IE indicates the new Additional Serving E-DCH Radio Link on secondary UL frequency.]
-	[FDD - If the old Additional Serving E-DCH RL is within this Node B, the Node B shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.]
-	[FDD - In the new configuration the Node B shall allocate the E-DCH resources for the new additional serving E-DCH Radio Link on the secondary UL frequency. Non cell specific E-DCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - The Node B may include in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message. ]
HS-DSCH Modification:
If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH Information To ModifyUnsynchronised IE and if the Serving HS-DSCH Radio Link is in the Node B, then:
-	The Node B shall include the HS-DSCH Initial Capacity Allocation IE for every HS-DSCH MAC-d flow being modified for which  the establishment of one or several new Priority Queues was requested, if the Node B allows the CRNC to start the transmission of MAC-d PDUs for the Priority Queue(s) being established before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If Node B Communication Context is configured to use the "Flexible MAC-d PDU Size", then Node B shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer for the Priority Queue of Node B Communication Context.
-	If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-hs Guaranteed Bit Rate IE in the HS-DSCH Information To ModifyUnsynchronised IE, the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
-	If the RADIO LINK RECONFIGURATION REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH Information To ModifyUnsynchronised IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the ACK Power Offset IE, the NACK Power Offset IE or the CQI Power Offset IE in the HS-DSCH Information To ModifyUnsynchronised IE, then the Node B shall use the indicated ACK Power Offset, the NACK Power Offset or the CQI Power Offset  in the new configuration.]
-	[FDD - If the CQI Feedback Cycle2 k IE or the CQI Cycle Switch Timer IE  is included in HS-DSCH Information To Modify IE, then the Node B may use the indicated CQI Feedback Cycle2 k value, the CQI Cycle Switch Timer in the new configuration.]
-	[FDD - If the HS-SCCH Power Offset IE is included in the HS-DSCH Information To ModifyUnsynchronised IE, the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]
-	[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the TDD ACK NACK Power Offset IE in the HS-DSCH Information To ModifyUnsynchronised IE, the Node B shall use the indicated power offset in the new configuration.]
-	[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-SICH SIR Target IE in the HS-DSCH Information To Modify Unsynchronised IE, the Node B shall use this value to the SIR Target in the new configuration. The HS-SICH SIR Target IE indicates the received UL SIR target of HS-SICH NACK for this UE.]
-	[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-SICH TPC step size IE in the HS-DSCH Information To Modify Unsynchronised IE, the Node B shall use this value to the HS-SICH TPC step size in the new configuration.]
-	[1.28Mcps TDD - For a multi-frequency cell, if the RADIO LINK RECONFIGURATION REQUEST message includes the Multi-carrier HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify Unsynchronised IE, the Node B shall use this information together with the HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify Unsynchronised IE to allocate HSDPA resources over multiple carriers for the UE.]
-	[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify Unsynchronised IE, the Node B may use this information in HSDPA resources allocation for the UE.]
-	[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the Puncturing Handling in First Rate Matching Stage IE in the HS-DSCH Information To Modify Unsynchronised IE, then the Node B shall, if supported, apply the puncturing during first stage rate matching according to the Puncturing Handling in First Rate Matching Stage IE.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HARQ Preamble Mode IE in the HS-DSCH Information To ModifyUnsynchronised IE, then the Node B shall use the indicated HARQ Preamble Mode in the new configuration as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the Node B shall include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the HARQ Preamble Mode IE is not included or if the mode 0 is applied, then the Node B shall not include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH Physical Layer Category IE in the HS-DSCH Information To Modify Unsynchronised IE, the Node B shall use this information in the new configuration and may include the HARQ Memory Partitioning IE in the RADIO LINK RECONFIGURATION RESPONSE message. The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.]
-	[FDD - If the MIMO Mode Indicator IE is included in the HS-DSCH Information To Modify Unsynchronised IE, then the Node B shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in accordance with the MIMO Mode Indicator IE.]
-	[FDD - If the MIMO Mode Indicator IE is set to "Activate", then the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH Information To Modify Unsynchronised IE, then the Node B may if the value is set to "allowed" use 64 QAM for the HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH Information To Modify Unsynchronised IE with value set to "not allowed", then the Node B shall not use 64 QAM for the HS-DSCH Radio Link.]
-	[FDD - If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - Any secondary serving HS-DSCH that was applied in the old configuration shall remain in the new configuration unless it is explicitly removed.]
-	[FDD - If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.]
-	[1.28Mcps TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH Physical Layer Category IE in the HS-DSCH Information To Modify Unsynchronised IE, the Node B shall use this information in the new configuration and may include the HARQ Memory Partitioning IE in the RADIO LINK RECONFIGURATION RESPONSE message. The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.]
-	[1.28Mcps TDD- If the MIMO Mode Indicator IE is included in the HS-DSCH Information To Modify Unsynchronised IE, then the Node B shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in accordance with the MIMO Mode Indicator IE.]
-	[1.28 Mcps TDD - If the MIMO Mode Indicator IE is set to "Activate", then the Node B shall decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Information To Modify Unsynchronised IE the Node B may use the supported HSDPA functions for this UE.]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Information To Modify IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the Node B shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH FDD Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the Single Stream MIMO Mode Indicator IE is included in the HS-DSCH Information To Modify Unsynchronised IE, then the Node B shall activate/deactivate the Single Stream MIMO mode for the HS-DSCH Radio Link in accordance with the Single Stream MIMO Mode Indicator IE.]
-	[FDD - The Node B may include the Precoder weight set restriction IE in the HS-DSCH FDD Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
[FDD – Secondary Serving HS-DSCH Modification:]
[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH FDD Secondary Serving Information To ModifyUnsynchronised IE in the Additional HS Cell Information RL Reconf Req IE and if the Secondary Serving HS-DSCH Radio Link is in the Node B, then:]
-	[FDD - If the HS-SCCH Power Offset IE is included in the HS-DSCH FDD Secondary Serving Information To ModifyUnsynchronised IE, the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]
-	[FDD - If the MIMO Mode Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE,then the Node B shall activate/deactivate the MIMO mode for the the secondary serving HS-DSCH Radio Link in accordance with the MIMO Mode Indicator IE.]
-	[FDD - If the MIMO Mode Indicator IE is set to "Activate", then the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the Single Stream MIMO Mode Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE, then the Node B shall activate/deactivate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link in accordance with the Single Stream MIMO Mode Indicator IE.]
-	[FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE with value set to "not allowed", then the Node B shall not use 64 QAM for the Secondary Serving HS-DSCH Radio Link.]
-	[FDD - If, in the new configuration, the concerned Node B Communication Context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH Radio Link, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]
-	[FDD - If the MIMO with four transmit antennas Mode Indicator IE or the Dual Stream MIMO with four transmit antennas Mode Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE, then the Node B shall activate/deactivate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link in accordance with the MIMO with four transmit antennas Mode Indicator IE, or Dual Stream MIMO with four transmit antennas Mode Indicator IE.]
-	[FDD - The Node B may include the Precoder weight set restriction IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
[FDD – Secondary Serving HS-DSCH Removal:]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH Secondary Serving Remove IE in the Additional HS Cell Information RL Reconf Req IE, then the indicated secondary serving HS-DSCH Radio Link shall be removed.]
HS-DSCH MAC-d Flow Addition/Deletion:
If the RADIO LINK RECONFIGURATION REQUEST message includes any HS-DSCH MAC-d Flows To Add or HS-DSCH MAC-d Flows To Delete IEs and if the Serving HS-DSCH Radio Link is in the Node B, then the Node B shall use this information to add/delete the indicated HS-DSCH MAC-d flows on the Serving HS-DSCH Radio Link. When an HS-DSCH MAC-d flow is deleted, all its associated Priority Queues shall also be removed.
If the RADIO LINK RECONFIGURATION REQUEST message includes an HS-DSCH MAC-d Flows To Delete IE requesting the deletion of all remaining HS-DSCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the HS-DSCH configuration from the Node B Communication Context and release any existing HS-PDSCH resources.
If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH MAC-d Flows To Add IE and if the Serving HS-DSCH Radio Link is in the Node B, then:
-	The Node B shall include the HS-DSCH Initial Capacity Allocation IE in the RADIO LINK RECONFIGURATION RESPONSE message for every HS-DSCH MAC-d flow being added, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If Node B Communication Context is configured to use the "Flexible MAC-d PDU Size" format for the HS-DSCH, then Node B shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer received in RADIO LINK RECONFIGURATION REQUEST message in the HS-DSCH MAC-d Flows To Add IE for a Priority Queue including  Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE.
-	If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-hs Guaranteed Bit Rate IE in the HS-DSCH MAC-d Flows To Add IE, the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.
-	If the RADIO LINK RECONFIGURATION REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.
-	If the RADIO LINK RECONFIGURATION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, then the Node B shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue.
-	[FDD - If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.]
-	If the RADIO LINK RECONFIGURATION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the in the HS-DSCH MAC-d Flows To Add IE, the DL RLC PDU Size Format IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24].
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, the Node B shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]
[FDD – HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change]
[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH Preconfiguration Setup IE in the RL Information IE the Node B shall if supported preconfigure the indicated cells for Enhanced HS Serving Cell Change acoording to TS 25.308 [49]: ]
-	[FDD – The Node B shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the C-ID IE part of the RL Information IE in the RADIO LINK RECONFIGURATION REQUEST message. The list of secondary serving HS-DSCH cells is designated by the list of C-IDs in the HS-DSCH Preconfiguration Setup IE part of the RL Information IE in the RADIO LINK RECONFIGURATION REQUEST message. ]
-	[FDD – The number of HS-SCCH codes to preconfigure for each cell may be optionally specified: ]
-	[FDD – by the Num Primary HS-SCCH Codes IE in the HS-DSCH Preconfiguration Setup IE, for the primary serving HS-DSCH cell]
-	[FDD – by the Num Secondary HS-SCCH Codes IE in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE for each of the secondary serving HS-DSCH cells]
-	[FDD – If Num Primary HS-SCCH Codes IE or Num Secondary HS-SCCH Codes IE is not included in the message, the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10]. ]
-	[FDD – The Node B shall return these codes in the Sets of HS-SCCH Codes IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE of the RADIO LINK RECONFIGURATION RESPONSE message. ]
-	[FDD – The Node B shall use the first in the numbered list of the primary serving HS-DSCH cell’s HS-SCCH codes in the HS-SCCH Preconfigured Codes IE sent to the RNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [18]. ]
-	[FDD – The Node B shall include, in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message, IEs according to the rules defined for HS-DSCH Setup and: ]
-	[FDD – if HARQ Preamble Mode IE is included in the HS-DSCH Preconfiguration Setup IE the HARQ Preamble Mode Activation Indicator IE]
-	[FDD – if MIMO Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE]
-	[FDD – if Ordinal number of frequency IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE]
-	[FDD – if MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE]
-	[FDD – if Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE]
-	[FDD – if Multiflow ordinal number of frequency IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE]
-	[FDD – if HS-DSCH MAC-d PDU Size Format IE is included in the HS-DSCH Preconfiguration Setup IE and set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used in the preconfigured configuration the HS-DSCH TB Size Table Indicator IE for each preconfigured cell]
-	[FDD – if Sixtyfour QAM Usage Allowed Indicator IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE or in the HS-DSCH Preconfiguration Setup IE the SixtyfourQAM DL Usage Indicator IE for each preconfigured cell]
-	[FDD – if Continuous Packet Connectivity HS-SCCH less Information IE is included in the HS-DSCH Preconfiguration Setup IE the Continuous Packet Connectivity HS-SCCH less Information Response IE]
-	[FDD – if the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH Preconfiguration Setup IE, then the Node B shall store this information in the preconfigured configuration. ]
-	[FDD – if the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE, then the Node B may store this information in the preconfigured configuration.]
-	[FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the Node B shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the Preconfiguration Info IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD – The Node B shall include in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message the E-DCH FDD DL Control Channel Information containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:]
-	[FDD – The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding  E-AGCH in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – The Node B may configure for the preconfigured configuration the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the E-DCH Indicator IE for a secondary cell, the Node B shall include in the Additional E-DCH Preconfiguration Information IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message the E-DCH FDD DL Control Channel Information containing the preconfigured configuration of the Additional E-DCH serving cell, corresponding to the cell indicated with the E-DCH Indicator IE, according to the rules defined for Serving Additional E-DCH Radio Link Change as follows:]
-	[FDD – The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving Additional E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – The Node B may configure for the preconfigured configuration the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving Additional E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the Multiflow Information IE, then the Node B shall allocate resources for the preconfigured Multiflow for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the F-TPICH Information IE, then the Node B shall allocate resources for the preconfigured F-TPICH channel for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the UL CLTD Information IE, then the Node B shall allocate resources for the preconfigured UL CLTD for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the UL MIMO Information IE, then the Node B shall allocate resources for the preconfigured UL MIMO for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the SixteenQAM UL Operation Indicator IE, then the Node B shall allocate resources for the preconfigured UL Sixteen QAM for the concerned Node B Communication Context.]
-	[FDD – If the HS-DSCH Preconfiguration Setup IE includes the SixtyfourQAM UL Operation Indicator IE, then the Node B shall allocate resources for the preconfigured UL Sixtyfour QAM for the concerned Node B Communication Context.]
[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the Non-Serving Preconfiguration Setup IE in the RL Information IE and:] 
-	[FDD – if the choice of new Serving RL is "New Serving RL in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE and/or New non-serving RL E-DCH FDD DL Control Channel Information B IEin the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD – if the choice of new Serving RL is "New Serving RL Not in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information C IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD – if the choice of new Serving RL is "New Serving RL in the Node B or New Serving RL Not in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C for the RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD – if the Additional E-DCH Non-Serving RL Preconfiguration Setup IE is included, the Node B may include the New non-serving E-DCH RL FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C IE according to the choice of new Serving RL in Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information IE for the additional non serving E-DCH RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD –If the F-TPICH Information IE is included, the Node B shall use this information to allocate resources for the preconfigured F-TPICH channel for this RL in the serving RLS according to TS 25.211 [7].]
[FDD – Enhanced HS Serving Cell Change:]
[FDD - Upon receipt of the RADIO LINK RECONFIGURATION REQUEST message, if the Enhanced HS Serving Cell Change is preconfigured in the Node B for the Node B Communication Context, the Node B may execute the  Enhanced HS Serving Cell Change procedure according to TS 25.308 [49]]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Enhanced HS Serving CC Abort IE in the HS-DSCH Information To Modify Unsynchronised IE or the HS-DSCH FDD Information IE then the Node B shall not execute the unsynchronized Enhanced HS Serving Cell Change procedure when performing the Intra-Node B Serving HS-DSCH Radio Link Change or, at inter Node B radio link change, the HS-DSCH Setup. ]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the No of Target Cell HS-SCCH Order IE then the Node B shall repeat the Target Cell HS-SCCH Order on the HS-SCCH the number of times defined in the IE. ]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Non-Serving RL Preconfiguration Removal IE, the Node B shall remove the corresponding preconfigured E-DCH DL Control Channel Information according to the information.]
[FDD - Multiflow Setup]:
[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the Multiflow Information IE in HS-DSCH FDD Information IE, or it includes the Multiflow Reconfiguration IE in HS-DSCH FDD Information To Modify Unsynchronized IE and the choice of  Setup or Change or Stop is “Setup”, then the Node B shall setup the requested Multiflow operation and then:]
-	[FDD – Use Total number of HS-DSCH cells IE to apply the HS-DPCCH format at the physical layer based on the total number of cells provided in this IE.]
-	[FDD – Use Role IE to know whether Multiflow cells configured at this Node B are assisting ones or not, for which Node B must read the correspondent part of the HS-DPCCH feedback channel.]
-	[FDD – Use MIMO IE to decide whether to apply the MIMO HS-DPCCH format at the physical layer.]
-	[FDD – If Timing IE is included, then Node B shall use this information to decide whether Multiflow cells configured at this Node B follow a different HS-DPCCH timing with an offset indicated by this IE.]
-	[FDD – If the Max number of HS-SCCH sets per Node B IE is included, then Node B shall use this information on the upper limit for the number HS-SCCH sets allocated and reported back to CRNC.]
-	[FDD – If the Assisting Repetition Factors IE is included, then the Node B shall use the values indicated in this IE within the Multiflow configuration.]
[FDD - Multiflow Modification:]
[FDD - If the Multiflow Reconfiguration IE is present in HS-DSCH Information To Modify Unsynchronized IE the RADIO LINK RECONFIGURATION REQUEST message, and the choice of Setup or Change or Stop is “Change”, then the Node B shall use new configuration as follows:]
-	[FDD – If the Total number of HS-DSCH cells IE is included, then apply the HS-DPCCH format at the physical layer based on the total number of cells provided in this IE.]
-	[FDD – If the Role IE is included, then all the Multiflow cells configured at this Node B are assisting ones, for which Node B must read the correspondent part of the HS-DPCCH feedback channel.]
-	[FDD – If the MIMO IE is included, then decide whether to apply the MIMO HS-DPCCH format at the physical layer.]
-	[FDD – If the Timing IE is included, then Node B shall use this information to decide whether Multiflow cells configured at this Node B follow a different HS-DPCCH timing with an offset indicated by this IE.]
-	[FDD – If the Max number of HS-SCCH sets per Node B IE is included, then Node B shall use this information on the upper limit for the number HS-SCCH sets allocated and reported back to CRNC.]
-	[FDD – If the Assisting Repetition Factors IE is included, then the Node B shall use the values indicated in this IE within the Multiflow configuration]
[FDD - Multiflow Removal:]
[FDD - If the Multiflow Reconfiguration IE is present in the RADIO LINK RECONFIGURATION REQUEST message, and the choice of Setup or Change or Stop is “Stop”, then the Node B shall terminate the Multiflow operation.]
[FDD - E-DCH Setup:]
[FDD - If the E-DCH FDD Information IE is present in the RADIO LINK RECONFIGURATION REQUEST message:]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel information IE in the E-DCH MAC-d Flows Information IE, then the Node B shall use this information to optimise MAC-e scheduling decisions.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH Information IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).]
-	[FDD - If the TNL QoS IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Reference Power Offset IE, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH  Power Offset for Scheduling Info IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the UPH Filtering Measurement Forwarding Request IE, then the Node B shall use this instruction to handle the UE UPH filtering measurement forwarding.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Serving E-DCH RL IE:]
-	[FDD - the Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the RADIO LINK RECONFIGURATION RESPONSE message for the initial grant for the serving E-DCH RL.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - The Node B may include the Default Serving Grant in DTX Cycle 2 IE in the RADIO LINK RECONFIGURATION RESPONSE message for the serving E-DCH RL.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If in the RADIO LINK RECONFIGURATION REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Non-Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE, if included, for the related resource allocation operation.]
-	[FDD - If in the RADIO LINK RECONFIGURATION REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume scheduled grants being configured for that E-DCH MAC-d flow.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Bundling Mode Indicator IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE and the Bundling Mode Indicator IE is set to "Bundling" and the E-TTI IE is set to "2ms", then the Node B shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the Node B shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Maximum Bitrate IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] 
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Processing Overload Level IE, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-AGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an E-DPCH Information IE which contains the HS-DSCH Configured Indicator IE and/or the Maximum Set of E-DPDCHs IE, and/or the Puncture Limit IE and/or the E-TTI IE, the Node B shall use and apply the value(s) in the new configuration.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the SixteenQAM UL Operation Indicator IE, the Node B shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the SixteenQAM UL Operation Indicator IE.]
-	[FDD - If SixteenQAM UL Operation is activated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [32]. If SixteenQAM UL Operation is deactivated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [32].]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the E-DCH Logical Channel Information IE in the E-DCH FDD Information IE, the Node B shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]
[FDD - E-DCH Radio Link Handling:]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH RL Indication IE in the RL Information IE:]
-	[FDD - The Node B shall setup the E-DCH resources, as requested or as configured in the Node B communication context, on the Radio Links indicated by the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE.]
-	[FDD - The Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION RESPONSE message for every RL indicated by the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE.]
-	[FDD - The Node B shall remove the E-DCH resources, if any, on the Radio Links, that are indicated by the E-DCH RL Indication set to "Non E-DCH".]
-	[FDD - For each RL for which the E-DCH RL Indication IE is set to "E-DCH", and which has or can have a common generation of E-RGCH information with another RL (current or future) when the Node B would contain the E-DCH serving RL, the Node B shall include the E-DCH RL Set ID IE in the RADIO LINK RECONFIGURATION RESPONSE message. The value of the E-DCH RL Set ID IE shall allow the RNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.]
[FDD - Serving E-DCH Radio Link Change:]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Serving E-DCH RL IE, this indicates the new Serving E-DCH Radio Link:]
-	[FDD - If the old Serving E-DCH RL is in this Node B, the Node B shall de-allocate the E-AGCH resources of the old Serving E-DCH Radio Link.]
-	[FDD - If the New Serving E-DCH RL is in this Node B:]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the RADIO LINK RECONFIGURATION RESPONSE message for the initial grant for the new serving E-DCH RL.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - The Node B may include the Default Serving Grant in DTX Cycle 2 IE in the RADIO LINK RECONFIGURATION RESPONSE message for the new serving E-DCH RL.]
-	[FDD - The Node B may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION RESPONSE message for every E-DCH Radio Links in the Node B.]
[FDD - E-DCH Modification:]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH FDD Information To Modify IE, then:]
-	[FDD - If the E-DCH FDD Information To Modify IE contains a E-DCH MAC-d Flow Specific Information IE which includes the Allocation/Retention Priority IE, the Node B shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Maximum Number of Retransmissions for E-DCH IE for an E-DCH MAC-d flow then the Node B shall use this information to report if the maximum number of retransmissions has been exceeded.]
-	[FDD - If  the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH HARQ Power Offset FDD IE in the E-DCH FDD Information To Modify IE for an E-DCH MAC-d flow the Node B shall use this information for calculating the unquantised gain factor for an E-TFC ( ed,j,uq)as defined in TS 25.214 [10].]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow  the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the E-DCH Grant Type and it is indicated as being "E-DCH Non-Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE, if included, for the related resource allocation operation.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Grant Type and it is indicated as being "E-DCH Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume scheduled grants being configured for that E-DCH MAC-d flow.]
-	[FDD - If the RADIO LINK RECONFIGURATION RE	QUEST message includes the E-DCH Logical Channel To Add or E-DCH Logical Channel To Delete IEs, the Node B shall use this information to add/delete the indicated logical channels. When an logical channel is deleted, all its associated configuration data shall also removed.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Logical Channel To Modify IE, the Node B shall use this information to modify the indicated logical channels:]
-	[FDD - If the E-DCH Logical Channel To Modify IE includes Scheduling Priority Indicator IE, the Node B shall apply the values in the new configuration.]
-	[FDD - If the E-DCH Logical Channel To Modify IE includes Scheduling Information IE, the Node B shall apply the values in the new configuration.]
-	[FDD - If the E-DCH Logical Channel To Modify IE includes MAC-es Guaranteed Bit Rate IE, the Node B shall apply the values in the new configuration.]
-	[FDD - If the E-DCH Logical Channel To Modify IE includes E-DCH DDI Value IE, the Node B shall apply the values in the new configuration.]
-	[FDD - If the E-DCH Logical Channel To Modify IE includes the Maximum MAC-d PDU Size Extended IE, the Node B shall apply the value in the new configuration.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Bundling Mode Indicator IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information To Modify IE and the Bundling Mode Indicator IE is set to "Bundling" and the E-TTI IE is set to "2ms", then the Node B shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the Node B shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If the E-DCH serving RL is in this Node B, the Node B may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission. In this case the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Maximum Bitrate IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Processing Overload Level IE, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Reference Power Offset IE, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Power Offsetfor Scheduling Info  IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-AGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the SixteenQAM UL Operation Indicator IE in the E-DCH FDD Information To Modify IE, the Node B shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the SixteenQAM UL Operation Indicator IE.]
-	[FDD - If SixteenQAM UL Operation is activated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [32]. If SixteenQAM UL Operation is deactivated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [32].]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH DL Control Channel Grant Information IE in the E-DCH FDD Information To Modify IE, the Node B may modify E-AGCH Channelisation Code, E-RGCH/E-HICH Channelisation Code, E-RGCH Signature Sequence and/or E-HICH Signature Sequence for the E-DCH RL indicated by the E-DCH RL ID IE. The Node B shall then report the modified configuration which is used in the new configuration specified in the E-DCH FDD DL Control Channel Information IE for each E-DCH RL in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the Fast TTI switching Mode Requested UnSynchronized IE in the E-DCH FDD Information To Modify IE and Mode 1 is indicated, the Node B shall if supported send the HS-SCCH order to execute the TTI swiching process according  to TS 25.214 [10]].
-	[FDD – If the RADIO LINK RECONFIGURATION REQUEST message includes the Fast TTI switching Mode Requested UnSynchronized IE in the E-DCH FDD Information To Modify IE and Mode 2 is indicated, the Node B shall if supported send the HS-SCCH order at the CFN indicated in Mode 2 to execute the TTI switching process according to TS 25.214 [10]].
[FDD - E-DCH MAC-d Flow Addition/Deletion:]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes any E-DCH MAC-d Flows To Add or E-DCH MAC-d Flows To Delete IEs, then the Node B shall use this information to add/delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration data shall also be removed.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH MAC-d Flows To Add IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an E-DCH MAC-d Flows To Delete IE requesting the deletion of all remaining E-DCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the E-DCH configuration from the Node B Communication Context and release the E-DCH resources.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH MAC-d Flows To Add IE, then:]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH MAC-d Flows To Add IE, the Node B shall use this information to optimise MAC-e scheduling decisions.] 
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows To Add IE, the Node B shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]
[FDD – Additional E-DCH Setup:]
[FDD - If the Additional E-DCH Cell Information RL Reconf Req IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency is "Setup", then: the Additional E-DCH Cell Information Setup IE defines the new configuration and then:] 
-	[FDD - If the C-ID IE is included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the C-ID IE indicates the cell in which the additional E-DCH shall be setup.]
-	[FDD - The Node B shall setup the E-DCH on the secondary uplink frequency and setup the requested E-DCH resources on the Radio Links and in the cells indicated by the E-DCH Additional RL ID IE and the C-ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE.]
-	[FDD - If the C-ID IE is not included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the E-DCH Additional RL ID IE indicates the existing RL on which the additional E-DCH shall be setup.]
-	[FDD - The Node B shall setup the additional E-DCH on the Radio Links indicated by the E-DCH Additional RL ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE.]
-	[FDD - The Node B shall use for the non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters the same values as for the corresponding cell of the Primary uplink frequency.]
-	[FDD - If the DL Power Balancing Information IE and/or the Minimum Reduced E-DPDCH Gain Factor IE are present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the Secondary UL Frequency Activation State is present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the Node B shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.]
-	[FDD - If the F-DPCH Slot Format IE is present in the Additional E-DCH RL Specific Information To Setup IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the Primary CPICH Usage For Channel Estimation IE, the Secondary CPICH Information, the E-AGCH Power Offset IE, the E-RGCH Power Offset IE and/or the E-HICH Power Offset IE are present in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH RL Specific Information To Setup IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Maximum Bitrate IE, the E-DCH Minimum Set E-TFCI IE, the E-DCH Processing Overload Level IE, the Implicit Grant handling IE, the Minimum TEBS threshold IE and/or the DTX Information2 IE are present in the Additional E-DCH FDD Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] 
- [FDD - If activation of power balancing for the Additional E-DCH RL by the RADIO LINK RECONFIGURATION REQUEST message is supported by the Node B, the Node B shall include the DL Power Balancing Activation Indicator IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
- [FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] 
- [FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
- [FDD - For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
- [FDD - For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE for each Additional E-DCH RL in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message.] 
- [FDD - If the Additional Serving E-DCH Radio Link is configured in the Node B, then:]
-	[FDD - The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message for the initial grant for the Additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.]
-	[FDD - If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE and include the new/changed configuration in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message.] 
[FDD – Additional E-DCH Configuration Change]
[FDD - If the Additional E-DCH Cell Information RL Reconf Req IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency is "Configuration Change", then: the Additional E-DCH Cell Information Configuration Change IE defines the new configuration and then]
-	[FDD - If the UL Scrambling Code IE and/or the UL SIR Target IE are present in the UL DPCH Information IE in the Additional E-DCH Configuration Change Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the Minimum Reduced E-DPDCH Gain Factor IE is present in the Multicell E-DCH Information IE in the Additional E-DCH Configuration Change Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] 
-	[FDD - If the F-DPCH Information IE is present in the Additional E-DCH Configuration Change Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
[FDD – Additional E-DCH RL Addition:]
[FDD - If the Additional E-DCH RL Specific Information To Add IE is present in the Additional E-DCH Configuration Change Information IE, then:] 
-	[FDD - The Node B shall setup the E-DCH resources, as requested or as configured in the Node B Communication Context, on the Radio Links indicated by the E-DCH Additional RL ID IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]
-	[FDD - If the Initial DL Transmission Power IE, the Maximum DL Power IE, the Minimum DL Power IE and/or the F-DPCH Slot Format IE are present in the Additional E-DCH RL Specific Information To Add IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] 
-	[FDD - If the DL Reference Power IE, the E-AGCH Power Offset IE, the E-RGCH PowerOffset IE, and/or the E-HICH Power Offset IE are present in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH RL Specific Information To Add IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Individual" in the existing Additional E-DCH RL(s) and the RADIO LINK RECONFIGURATION REQUEST message includes the DL Reference Power IE, the Node B shall activate the power balancing and use the DL Reference Power IE for the power balancing procedure in the new Additional E-DCH RL(s), if activation of power balancing by the RADIO LINK RECONFIGURATION RESPONSE message is supported, according to subclause 8.3.7. In this case, the Node B shall include the DL Power Balancing Activation Indicator IE in the E-DCH Additional RL Specific Information Response IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the Node B starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. Pinit shall be set to the power level indicated by the Initial DL Transmission Power IE (if received) in the Additional E-DCH RL Specific Information To Add IE or the decided DL TX power level on each DL channelisation code of an Additional E-DCH RL based on power level of existing Additional E-DCH RLs.]
-	[FDD - For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] 
-	[FDD - For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]
-	[FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO LINK RECONFIGURATION RESPONSE message.] 
-	[FDD - For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Add IE in the Additional E-DCH FDD Setup Information IE the Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE for each Additional E-DCH RL in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE RL Reconf in the RADIO LINK RECONFIGURATION RESPONSE message.] 
[FDD – Additional E-DCH RL Modification:]
[FDD - If the Additional E-DCH RL Specific Information To Modify IE is present in the Additional E-DCH Configuration Change Information IE, then the RL indicated by the E-DCH Additional RL ID IE indicates the RL on which E-DCH resources shall be modified:]
-	[FDD - If the Maximum DL Power IE, the Minimum DL Power IE, and/or the F-DPCH Slot Format IE are present in the Additional E-DCH RL Specific Information To Modify IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.] 
-	[FDD - If the DL Reference Power IE, the Primary CPICH Usage For Channel Estimation IE, the Secondary CPICH Information Change IE, the E-AGCH Power Offset IE, the E-RGCH Power Offset IE, the E-HICH Power Offset IE and/or the E-DCH DL Control Channel Grant IE are present in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH RL Specific Information To Modify IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]
-	[FDD - If updating of power balancing parameters by the RADIO LINK RECONFIGURATION REQUEST message is supported by the Node B, the Node B shall include the DL Power Balancing Updated Indicator IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE for each affected RL in the RADIO LINK RECONFIGURATION RESPONSE message.]
[FDD – Additional E-DCH Modification:]
[FDD - If the Additional E-DCH FDD Information To Modify IE is present in the Additional E-DCH Configuration Change Information IE, then:]
-	[FDD - If the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE and/or the E-DCH Minimum Set E-TFCI IE is included, the Node B shall use this information for the related resource allocation operation.] 
-	[FDD - If the E-DCH Maximum Bitrate IE is included, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] 
-	[FDD - If the E-DCH Processing Overload Level IE is included, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]
-	[FDD - If the Additional E-DCH serving RL is in this Node B, the Node B may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission. In this case the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional Modified E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[FDD - If the DTX Information2 IE is included, the Node B shall use this information for the related resource allocation operation.] 
-	[FDD - If the Implicit Grant handling IE is included, the Node B shall use this information for the related resource allocation operation.]
-	[FDD - If the Minimum TEBS threshold IE is included, the Node B shall use this information for the related resource allocation operation.]
[FDD – Additional E-DCH Removal]
[FDD - If the Additional E-DCH Cell Information RL Reconf Req IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency is "Removal", then the additional E-DCH on the secondary uplink frequency shall be removed.]
[FDD – E-DCH decoupling operation]
[FDD – If the E-DCH Decoupling Indication IE is present in the RADIO LINK RECONFIGURATION REQUEST message, then the Node B shall if supported use this indication for the E-DCH decoupling operation.]
[FDD – Radio Links without DPCH/F-DPCH operation]
[FDD – If the Radio Links without DPCH/F-DPCH Indication IE is present in the RADIO LINK RECONFIGURATION REQUEST message:]
-	[FDD – The Node B shall if supported start operation with Radio Links without DPCH/F-DPCH.]
[FDD - UL DPCCH2 Setup:]
[FDD - If the UL DPCCH2 Reconfiguration IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL DPCCH2 is "Setup", then:]
-	[FDD – if the serving HS-DSCH RL is in the Node B then the Node B shall configure the concerned Node B Communication Context to use a second F-DPCH in the downlink, i.e. with transmission of only the TPC field and a DPCCH2 in the uplink, i.e. with the transmission of only the second pilot and the TPC field on the Serving HS-DSCH Radio Link and the Node B shall activate UL DPCCH2 operation for the radio link according to the information provided in the IE according to ref TS 25.214 [10].]
-	[FDD – if the serving HS-DSCH is not in the Node B then the Node B may consider the concerned Node B Communication Context to use the UL DPCCH2 configuration on the Serving HS-DSCH Radio Link.]
-	[FDD – If the UL DPCCH2 Reconfiguration IE includes the Extended E-DPCCH Power Offset IE, the concerned Node B shall use the value when the new configuration is being used.]
[FDD – UL DPCCH2 Modification:]
[FDD - If the UL DPCCH2 Reconfiguration IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL DPCCH2 is "Configuration Change", then: the UL DPCCH2 Information To Modify IE defines the new configuration and then:]
-	[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the F-DPCH info IE in the UL DPCCH2 Information To Modify IE and if the serving HS-DSCH RL is in the Node B, then the Node B shall use this value to update the second F-DPCH for the concerned Node B Communication Context.]
-	[FDD – If the UL DPCCH2 Reconfiguration IE includes the Extended E-DPCCH Power Offset IE, the concerned Node B shall use the value when the new configuration is being used.]
[FDD - UL DPCCH2 Removal:]
[FDD - If the UL DPCCH2 Reconfiguration IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL DPCCH2 is "Removal", then the configured UL DPCCH2 for the concerned Node B Communication Context shall be removed.]
[FDD – Downlink TPC enhancements Setup:]
[FDD - If the Downlink TPC enhancements Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of Downlink TPC enhancements is "Setup", then:]
-	[FDD – The NodeB shall, if supported, use the Decimation factor for primary frequency IE and/or the Decimation factor for secondary frequency IE to configure all the radio links using F-DPCH on the related frequency with power control Algorithm 3.]
[FDD - If the TPC slot position in the Radio Link Information is included in the RADIO LINK RECONFIGURATION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.]
[FDD - If the TPC slot position in the Additional E-DCH Cell Information Setup is included in the RADIO LINK RECONFIGURATION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.]
[FDD –Downlink TPC enhancements Modification:]
[FDD - If the Downlink TPC enhancements Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of Downlink TPC enhancements is "Configuration Change", then: the Downlink TPC enhancements Information To Modify IE defines the new configuration and then:]
-	[FDD - The NodeB shall, if supported, use the Decimation factor for primary frequency IE and/or the Decimation factor for secondary frequency IE to reconfigure all the radio links using F-DPCH on the related frequency with power control Algorithm 3.]
[FDD - If the TPC slot position in the Radio Link Information is included in the RADIO LINK RECONFIGURATION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.]
[FDD - If the TPC slot position in the Additional E-DCH Cell Information Configuration Change is included in the RADIO LINK RECONFIGURATION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.]
[FDD - Downlink TPC enhancements Removal:]
[FDD - If the Downlink TPC enhancements Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of Downlink TPC enhancements is "Removal", then the configured power control Algorithm 3 for the concerned Node B Communication Context shall be removed.]
[TDD - Intra-Node B Serving E-DCH Radio Link Change:]
[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Serving RL IE, this indicates the new Serving E-DCH Radio Link:]
-	[TDD - In the new configuration the Node B shall de-allocate the E-DCH resources of the old Serving E-DCH Radio Link and allocate the E-DCH resources for the new Serving E-DCH Radio Link.]
-	[TDD - The Node B shall allocate E-AGCH parameters [1.28Mcps TDD - and E-HICH parameter] corresponding to the E-DCH and include the E-AGCH Specific Information Response TDD IE [1.28Mcps TDD - and E-HICH Specific Information Response TDD IE]in the E-DCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
-	[TDD - If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.]
[TDD - E-PUCH Handling]:
[3.84Mcps TDD and 7.68Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an E-PUCH Information IE, the Node B shall apply the parameters to the new configuration.]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an E-PUCH Information LCR IE, the Node B shall apply the parameters to the new configuration.]
[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an E-TFCS Information TDD IE, the Node B shall apply the beta parameters to the new configuration.]
[1.28 Mcps TDD - The Node B shall configure the HS-SCCH TPC step size to the same value as the E-AGCH TPC step size IE configured in E-PUCH Information LCR IE in the E-DCH Information 1.28Mcps IE.]
[3.84Mcps TDD - E-DCH Setup]:
[3.84Mcps TDD - the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: E-DCH Serving RL IE, E-PUCH Information IE, E-TFCS Information TDD IE, E-DCH MAC-d Flows to Add IE, E-DCH TDD Information IE and E-DCH Non-scheduled Grant Information TDD IE if there are to be non-scheduled grants.]
[1.28Mcps TDD - E-DCH Setup]:
[1.28Mcps TDD - the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: E-DCH Serving RL IE, E-PUCH Information LCR IE, E-TFCS Information TDD IE, E-DCH MAC-d Flows to Add IE, E-DCH TDD Information LCR IE and E-DCH Non-scheduled Grant Information LCR TDD IE if there are to be non-scheduled grants.]
[1.28Mcps TDD - If the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify IE is not present, or if the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE is not present, and if the RADIO LINK RECONFIGURATION REQUEST message includes the UE TS0 Capability LCR IE in the E-DCH TDD Information LCR IE, the Node B can use this information to allocate the downlink resources for the UE according to TS 25.306 [33].]
[7.68Mcps TDD - E-DCH Setup]:
[7.68Mcps TDD - the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: E-DCH Serving RL IE, E-PUCH Information IE, E-TFCS Information TDD IE, E-DCH MAC-d Flows to Add IE, E-DCH TDD Information 7.68Mcps IE and E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE if there are to be non-scheduled grants.]
[TDD - E-DCH MAC-d Flow Addition/Deletion:]
[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes any E-DCH MAC-d Flows To Add or E-DCH MAC-d Flows To Delete IEs, then the Node B shall use this information to add/delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration data shall also be removed.]
[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH MAC-d Flows To Add IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel.] 
[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an E-DCH MAC-d Flows To Delete IE requesting the deletion of all remaining E-DCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the E-DCH configuration from the Node B Communication Context and release the E-DCH resources.]
[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes an E-DCH MAC-d Flows To Delete IE requesting the deletion of all remaining non-scheduled E-DCH MAC-d flows for the Node B Communication Context, then the Node B shall delete the non-scheduled E-DCH configuration from the Node B Communication Context and release the non-scheduled E-DCH resources [1.28 Mcps TDD - and the related Signature Sequence of the Non-scheduled E-HICH].]
[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH MAC-d Flows To Add IE, then if the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH MAC-d Flows To Add IE, the Node B shall use this information to optimise MAC-e scheduling decisions.]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-es Maximum Bit Rate LCR IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows To Add IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
[3.84Mcps TDD - E-DCH Non-scheduled allocations:]
[3.84Mcps TDD - If the E-DCH Non-scheduled Grant Information TDD IE is present in the RADIO LINK RECONFIGURATION REQUEST message the Node B shall assume that non-scheduled transmissions will take place according to the parameters in the information element.]
[1.28Mcps TDD - E-DCH Non-scheduled allocations:]
[1.28Mcps TDD - If the E-DCH Non-scheduled Grant Information LCR TDD IE is present in the RADIO LINK RECONFIGURATION REQUEST message the Node B shall assume that non-scheduled transmissions will take place according to the parameters in the information element.]
[7.68Mcps TDD - E-DCH Non-scheduled allocations:]
[7.68Mcps TDD - If the E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE is present in the RADIO LINK RECONFIGURATION REQUEST message the Node B shall assume that non-scheduled transmissions will take place according to the parameters in the information element.]
[TDD - E-DCH Modification:]
[TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the [3.84Mcps TDD - E-DCH TDD Information  IE] [1.28Mcps TDD - E-DCH TDD Information LCR IE] [7.68Mcps TDD - E-DCH TDD Information 7.68Mcps IE], then:]
-	[3.84Mcps TDD - If the E-DCH TDD Information IE includes the E-DCH TDD Maximum Bitrate IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] 
-	[1.28Mcps TDD - If the E-DCH TDD Information LCR IE includes the E-DCH Physical Layer Category LCR IE or Extended E-DCH Physical Layer Category LCR IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[7.68Mcps TDD - If the E-DCH TDD Information 7.68Mcps IE includes the E-DCH TDD Maximum Bitrate 7.68Mcps IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] 
-	[TDD - If the [3.84Mcps TDD - E-DCH TDD Information IE] [7.68Mcps TDD - E-DCH TDD Information 7.68Mcps IE] [1.28Mcps TDD - E-DCH TDD Information LCR IE] includes the E-DCH Processing Overload Level IE, then if the Node B could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]
-	[TDD - If the [3.84Mcps TDD - E-DCH TDD Information IE] [1.28Mcps TDD - E-DCH TDD Information LCR IE] [7.68Mcps TDD - E-DCH TDD Information 7.68McpsIE]includes the E-DCH Power Offset for Scheduling Info IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]
-	[1.28Mcps TDD - If the E-DCH TDD Information LCR IE includes the Maximum Number of Retransmission for Scheduling Info LCR IE and the E-DCH Retransmission timer for Scheduling Info LCR IE, then the Node B shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.]
-	[1.28Mcps TDD - If the E-DCH TDD Information LCR IE includes the Multi-Carrier E-DCH Physical Layer Category LCR IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.][TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH TDD Information To Modify IE, then:]
-	[TDD - If the E-DCH TDD Information To Modify IE contains a E-DCH MAC-d Flow Specific Information IE which includes the Allocation/Retention Priority IE, the Node B shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.]
-	[TDD - If the E-DCH TDD Information To Modify IE message includes the Maximum Number of Retransmissions for E-DCH IE for an E-DCH MAC-d flow then the Node B shall use this information to report if the maximum number of retransmissions has been exceeded.]
-	[1.28Mcps TDD - If the E-DCH TDD Information To Modify IE message includes the E-DCH MAC-d Flow Retransmission Timer IE for an E-DCH MAC-d flow then the Node B shall use this information to set the retransmissions timer.]
-	[TDD - If  the E-DCH TDD Information To Modify IE message includes the E-DCH HARQ Power Offset TDD IE for an E-DCH MAC-d flow the Node B shall use this new power offset value.]
-	[TDD - If the E-DCH TDD Information To Modify IE includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.]
-	[TDD - If the E-DCH TDD Information To Modify IE includes the E-DCH Grant Type IE, the Node B shall treat the E-DCH MAC-d flow as Scheduled or Non-scheduled accordingly.]
-	[TDD - If the E-DCH TDD Information To Modify IE includes the E-DCH Logical Channel To Add or E-DCH Logical Channel To Delete IEs, the Node B shall use this information to add/delete the indicated logical channels. When a logical channel is deleted, all its associated configuration data shall also removed.]
-	[TDD - If the E-DCH TDD Information To Modify IE includes the E-DCH Logical Channel To Modify IE, the Node B shall use this information to modify the indicated logical channels:]
-	[TDD - If the E-DCH Logical Channel To Modify IE includes Scheduling Priority Indicator IE, the Node B shall apply the values in the new configuration.]
-	[TDD - If the E-DCH Logical Channel To Modify IE includes Scheduling Information IE, the Node B shall apply the values in the new configuration.]
-	[TDD - If the E-DCH Logical Channel To Modify IE includes MAC-es Guaranteed Bit Rate IE, the Node B shall apply the values in the new configuration.]
-	[1.28Mcps TDD - If the E-DCH Logical Channel To Modify IE includes MAC-es Maximum Bit Rate LCR IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]
-	[TDD - If the E-DCH Logical Channel To Modify IE includes E-DCH DDI Value IE, the Node B shall apply the values in the new configuration.]
-	[TDD - If the E-DCH Logical Channel To Modify IE includes the Maximum MAC-d PDU Size Extended IE, the Node B shall apply the value in the new configuration.]
-	[TDD - If the E-DCH TDD Information To Modify IE includes the MAC-e Reset Indicator IE in the E-DCH TDD Information To Modify IE, then the Node B shall use this value to determine whether MAC-e (or MAC-i) Reset is performed in the UE for sending the HARQ Failure Indication.]
-	[1.28Mcps TDD - If the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify IE is not present, or if the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE is not present, and if the RADIO LINK RECONFIGURATION REQUEST message includes the UE TS0 Capability LCR IE in the E-DCH TDD Information to Modify IE, the Node B can use this information to allocate the downlink resources for the UE according to TS 25.306 [33].]
[1.28Mcps TDD - Power Control GAP:]
[1.28Mcps TDD - If the Power Control GAP IE is included in the RADIO LINK RECONFIGURATION REQUEST message, the Node B may use the value for the power control for HS-SCCH and HS-SICH according to TS 25.224 [21].]
[1.28Mcps TDD - E-UTRAN Inter-RAT measurement:]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Idle Interval Information IE, if supported, the Node B shall use the value for E-UTRAN Inter-RAT measurement according to TS 25.331 [18].]
[1.28Mcps TDD - HS-DSCH-RNTI for FACH:]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH-RNTI for FACH IE, if supported, the Node B shall store this information and include the E-RNTI for FACH IE in the RADIO LINK RECONFIGURATION RESPONSE message.]
[1.28Mcps TDD – Inter-frequency/ Inter-RAT measurement:]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Measurement occasion pattern sequence parameters IE in the DCH Measurement Occasion Information IE, the Node B shall store the information about the Measurement occasion pattern sequences and use the value(s) to calculate the Inter-frequency/Inter-RAT measurement occasion according to TS 25.331 [18].] 
[1.28Mcps TDD –Multi-Carrier E-DCH Continue:]
[1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Continue, Setup or Change is "Continue", then the current Multi-Carrier E-DCH configuration shall not be changed.]
[1.28Mcps TDD – Multi-Carrier E-DCH Setup:]
[1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf  IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Continue, Setup or Change is "Setup", then the Multi-Carrier E-DCH Information LCR IE defines the new configuration and then:]
-	[1.28Mcps TDD - The Node B shall use the Multi-Carrier E-DCH Transport Bearer Mode LCR IE to decide the transport bearer mode in the new configuration.]
-	[1.28Mcps TDD - The Node B shall setup the requested E-DCH resource on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.]
[1.28Mcps TDD – Multi-Carrier E-DCH Change:]
[1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Continue, Setup or Change is "Change", then the Multi-Carrier E-DCH Information LCR IE defines the new configuration and then:]
-	[1.28Mcps TDD - If the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE is different from current configured frequencies, then the Node B shall setup the E-DCH resources, as requested in the Node B Communication Context, on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.]
-	[1.28Mcps TDD - If the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE is the same as any current configured frequency, then the Node B shall reconfigure the E-DCH resources, as requested or as configured in the Node B Communication Context, on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.]
[1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf  IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Continue, Setup or Change is "Change" and the Removal UL Multi-Carrier info IE is included, then the Node B shall remove the corresponding E-DCH configuration on the uplink frequencies indicated by the UARFCN IE in the Removal UL Multi-Carrier info IE.]
[1.28Mcps TDD – Non-rectangular resource operation:]
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the UE support of non-rectangular resource allocation IE, the Node B shall, if supported, use this information to determine whether includes the Non-rectangular resource allocation indicator IE and the Non-rectangular resource timeslot set IE or not.]
General
If the RADIO LINK RECONFIGURATION REQUEST message includes the Transport Layer Address IE and Binding ID IEs in the HS-DSCH Information IE, HS-DSCH Information To Modify Unsynchronised IE, HS-DSCH MAC-d Flows To Add IE, [FDD -RL Specific E-DCH Information IE] [TDD - E-DCH MAC-d Flows to Add IE, E-DCH TDD Information to Modify IE] or in the RL Specific DCH Information IE, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for any Transport Channel [FDD - for which the Transport Bearer Not Requested Indicator IE is not included] or MAC-d flow [FDD - for which the Transport Bearer Not Requested Indicator IE is not included] being added or any Transport Channel [FDD - for which the Transport Bearer Not Requested Indicator IE was not included] or MAC-d flow [FDD - for which the Transport Bearer Not Requested Indicator IE was not included] being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE.
If the requested modifications are allowed by the Node B, the Node B has successfully allocated the required resources, and changed to the new configuration, it shall respond to the CRNC with the RADIO LINK RECONFIGURATION RESPONSE message.
The Node B shall include in the RADIO LINK RECONFIGURATION RESPONSE message the Transport Layer Address IE and the Binding ID IE for any Transport Channel [FDD - for which the Transport Bearer Not Requested Indicator IE is not included], or MAC-d flow [FDD - for which the Transport Bearer Not Requested Indicator IE is not included], being added or any Transport Channel [FDD - for which the Transport Bearer Not Requested Indicator IE was not included] or MAC-d flow [FDD - for which the Transport Bearer Not Requested Indicator IE was not included] being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE. The detailed frame protocol handling during transport bearer replacement is described in TS 25.427 [16], subclause 5.10.1 and in TS 25.435 [24], subclause 5.8.3.
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer shall not be Established" for a DCH or an E-DCH MAC-d flow being added, then the Node B shall not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow and shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION RESPONSE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer may not be Established" for a DCH or an E-DCH MAC-d flow being added and:]
-	[FDD - if the Node B establishes a transport bearer for the concerned DCH or E-DCH MAC-d flow, the Node B shall include in the RADIO LINK RECONFIGURATION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the DCH or E-DCH MAC-d flow being established.]
-	[FDD - if the Node B does not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow, the Node B shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION RESPONSE message.]
In the case of a set of co-ordinated DCHs requiring a new transport bearer on the Iub interface, the Transport Layer Address IE and the Binding ID IE in the DCH Information Response IE shall be included only for one of the DCH [FDD - for which the Transport Bearer Not Requested Indicator IE is not included] in the set of coordinated DCHs.
In the case of a Radio Link being combined with another Radio Link within the Node B, the Transport Layer Address IE and the Binding ID IE [FDD - for which the Transport Bearer Not Requested Indicator IE is not included] in the DCH Information Response IE shall be included only for one of the combined Radio Links.
[FDD - In the case of an E-DCH RL being combined with another E-DCH RL within the Node B, the E-DCH FDD Information Response IE shall be included only for one of the combined E-DCH RLs.] 
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Additional E-DCH Cell Information RL Reconf Req IE, then:] 
-	[FDD - if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to "Separate Iub Transport Bearer Mode" the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
-	[FDD - if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to "UL Flow Multiplexing Mode" the Node B shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.] 
-	[FDD - if Separate Iub Transport Bearer Mode is used in the new configuration, then:]
-	[FDD - the Node B shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the Transport Bearer Not Requested Indicator IE in the E-DCH MAC-d Flow Specific Information IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE and/or the Transport Bearer Request Indicator IE in the E-DCH FDD Information To Modify IE received for the corresponding Radio Link(s) of the Primary Uplink Frequency to determine the transport bearer configuration in the new configuration for the radio links of the Secondary Uplink Frequency.]
-	[FDD - If the Transport Layer Address IE and Binding ID IE is included for an E-DCH MAC-d flow in the Additional E-DCH MAC-d Flows Specific Information IE in the Additional E-DCH FDD Information IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE or in the Additional E-DCH MAC-d Flows Specific Information IE in the Additional E-DCH FDD Information To Modify IE in the Additional E-DCH Configuration Change Information IE in the Additional E-DCH Cell Information Configuration Change IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow the Node B shall, for establishment of the transport bearer, include in the RADIO LINK RECONFIGURATION RESPONSE message the Binding ID IE and Transport Layer Address IE in the Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional E-DCH FDD Information Response IE  and/or and/or include the Binding ID IE and Transport Layer Address IE for the E-DCH MAC-d flow has been modified in the Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional Modified E-DCH FDD Information Response IE.] 
[1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Multi-Carrier E-DCH Information Reconf IE, then:]
-	[1.28Mcps TDD - If the Multi-carrier E-DCH Transport Bearer Mode LCR IE is set to "Separate Iub Transport Bearer Mode" the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]
-	[1.28Mcps TDD - If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "UL Flow Multiplexing Mode" the Node B shall use this mode in the new configuration and multiplex each MAC-d flow on one transport bearer.]
-	[1.28Mcps TDD - If the choice of Continue, Setup or Change in the the Multi-Carrier E-DCH Information Reconf  IE is "Setup" and the Separate Iub transport bearer mode is used in the new configuration, or if the choice of Continue, Setup or Change in the the Multi-Carrier E-DCH Information Reconf  IE is "Change" and the Transport Bearer Mode is changed to "Separate Iub Transport Bearer Mode" indicated by Multi-carrier E-DCH Transport Bearer Mode LCR IE, then the Node B shall include the Binding ID IE and Transport Layer Address IE in the Multi-Carrier E-DCH Information Response LCR IE in the RADIO LINK RECONFIGURATION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
-	[1.28Mcps TDD - The Node B shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the Transport Bearer Request Indicator IE in the E-DCH TDD Information to Modify IE received for the corresponding Radio Link to determine the transport bearer configuration in the new configuration for the all Uplink Frequencies.]
-	[1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration and if the Transport Bearer Request Indicator IE is set to " Bearer Requested ", then the Node B shall include the Binding ID IE and Transport Layer Address IE in the E-DCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]
In the case of a signalling bearer re-arrangement, the new Communication Control Port shall be used once the Node B has sent the RADIO LINK RECONFIGURATION RESPONSE message via the old Communication Control Port.
8.3.5.3	Unsuccessful Operation

Figure 35: Unsynchronised Radio Link Reconfiguration procedure, Unsuccessful Operation
If the Node B cannot allocate the necessary resources for all the new DCHs of one set of co-ordinated DCHs requested to be set-up, it shall regard the Unsynchronised Radio Link Reconfiguration procedure as having failed.
If the requested Unsynchronised Radio Link Reconfiguration procedure fails for one or more Radio Link(s), the Node B shall send the RADIO LINK RECONFIGURATION FAILURE message to the CRNC, indicating the reason for failure.
Typical cause values are as follows:
Radio Network Layer Cause
-	CM not supported
-	[FDD - Continuous Packet Connectivity DTX-DRX operation not available]
-	[FDD - Continuous Packet Connectivity UE DTX Cycle not available]
-	[FDD - MIMO not available]
-	E-DCH MAC-d PDU Size Format not available
-	[FDD - SixtyfourQAM DL and MIMO Combined not available]
-	[FDD - Multi Cell operation not available.]
-	[1.28Mcps TDD - MIMO not available]
-	[1.28Mcps TDD - SixtyfourQAM DL and MIMO Combined not available]
-	[FDD – Single Stream MIMO not available]
-	[FDD - Multi Cell operation with MIMO not available]
-	[FDD - Multi Cell operation with Single Stream MIMO not available]
-	[FDD - Multi Cell E-DCH operation not available]
-	[FDD - UL CLTD operation not available]
-	[FDD - MIMO with four transmit antennas not available]
-	[FDD - Dual Stream MIMO with four transmit antennas not available]
-	[FDD – Multiflow operation not available]
-	[FDD - SixtyfourQAM UL operation not available]
-	[FDD – UL MIMO operation not available]
-	[FDD – UL MIMO and SixteenQAM operation not available]
-	[FDD – UL MIMO and SixtyfourQAM operation not available]
-	[FDD – E-DCH decoupling operation not available]
-	[FDD – Radio Links without DPCH/F-DPCH operation not available]
-	[FDD – UL DPCCH2 operation not available]
-	[FDD – Downlink TPC enhancements operation not available]
Transport Layer Cause
-	Transport Resources Unavailable
Miscellaneous Cause
-	O&M Intervention
-	Control processing overload
-	HW failure
8.3.5.4	Abnormal Conditions
If only a subset of all the DCHs belonging to a set of co-ordinated DCHs is requested to be deleted, the Node B shall regard the Unsynchronised Radio Link Reconfiguration procedure as having failed and shall send the RADIO LINK RECONFIGURATION FAILURE message to the CRNC.
[FDD - If the concerned Node B Communication Context is configured to use DPCH in the downlink and if the RL Information IE contains the DL Code Information IE and this IE includes DL Scrambling Code and FDD DL Channelisation Code Number IEs not matching the DL Channelisation code(s) already allocated to the Radio Link identified by RL ID IE, then the Node B shall consider the Unsynchronised Radio Link Reconfiguration procedure as having failed and it shall send the RADIO LINK RECONFIGURATION FAILURE message to the CRNC.]
If more than one DCH of a set of co-ordinated DCHs has the QE-Selector IE set to "selected" [TDD - or no DCH of a set of co-ordinated DCHs has the QE-Selector IE set to "selected"], the Node B shall regard the Unsynchronised Radio Link Reconfiguration Preparation procedure as failed and shall respond with a RADIO LINK RECONFIGURATION FAILURE message.
If the RADIO LINK RECONFIGURATION REQUEST message includes a DCHs To Modify IE or DCHs To Add IE with multiple DCH Specific Info IEs, and if the DCHs in the DCHs To Modify IE or DCHs To Add IE do not have the same Transmission Time Interval IE in the Semi-Static Transport Format Information IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[FDD - If the RL Information IE includes the DL Reference Power IEs, but the power balancing is not active in the indicated RL(s), the Node B shall regard the Unsynchronised Radio Link Reconfiguration procedure as having failed and the Node B shall respond the RADIO LINK RECONFIGURATION FAILURE message with the cause value "Power Balancing status not compatible".]
[FDD - If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Common" in the existing RL(s) but the RL Information IE includes more than one DL Reference Power IEs, the Node B shall regard the Unsynchronised Radio Link Reconfiguration procedure as having failed and the Node B shall respond the RADIO LINK RECONFIGURATION FAILURE message with the cause value "Power Balancing status not compatible".]
If the RADIO LINK RECONFIGURATION REQUEST message contains the Transport Layer Address IE or the Binding ID IE when establishing a transport bearer for any Transport Channel or HS-DSCH MAC-d flow being added or any Transport Channel or HS-DSCH MAC-d flow being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If the RADIO LINK RECONFIGURATION REQUEST message contains any of the HS-DSCH Information To Modify IE, HS-DSCH MAC-d Flows To Add IE or HS-DSCH MAC-d Flows To Delete IE in addition to the HS-DSCH Information IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If the RADIO LINK RECONFIGURATION REQUEST message contains any of the HS-DSCH Information To Modify IE, HS-DSCH MAC-d Flows To Add IE, HS-DSCH MAC-d Flows To Delete IE or HS-PDSCH RL ID IE and the Serving HS-DSCH Radio Link is not in the Node B, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH Information IE and does not include the HS-PDSCH RL-ID IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-PDSCH RL-ID IE indicating a Radio Link not existing in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If the RADIO LINK RECONFIGURATION REQUEST message contains any of the HS-DSCH Information IE, HS-DSCH Information To Modify IE, or HS-DSCH MAC-d Flows To Add IE and if in the new configuration the Priority Queues associated with the same HS-DSCH MAC-d Flow ID IE have the same Scheduling Priority Indicator IE value, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If, in the new configuration, the concerned Node B Communication Context is configured to use "Indexed MAC-d PDU Size" for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use Maximum MAC-d PDU Size Extended, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If, in the new configuration, the concerned Node B Communication Context is configured to use "Flexible MAC-d PDU Size" for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use MAC-d PDU Size Index, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If, in the new configuration, the concerned Node B Communication Context is configured to use "Fixed MAC-d PDU Size" for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use  Maximum MAC-d PDU Size Extended, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If, in the new configuration, the concerned Node B Communication Context is configured to use "Flexible MAC-d PDU Size" for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use MAC-d PDU Size List, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the HS-DSCH Information IE and if the Measurement Power Offset IE is not present, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
If the RADIO LINK RECONFIGURATION REQUEST message includes HS-DSCH Information IE and the HS-DSCH is already configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[FDD - If the concerned Node B Communication Context is configured to use F-DPCH in the downlink and if the RL Information IE contains the DL Code Information IE, then the Node B shall consider the Unsynchronised Radio Link Reconfiguration procedure as having failed and it shall send the RADIO LINK RECONFIGURATION FAILURE message to the CRNC.]
[FDD - If the E-DCH FDD Information IE is present in the RADIO LINK RECONFIGURATION REQUEST message, but the E-DPCH Information IE is not present, or if any of the Maximum Set of E-DPDCHs IE, Puncture Limit IE, E-TFCS Information IE, E-TTI IE, E-DPCCH Power Offset IE, E-RGCH 2-Index-Step Threshold IE, E-RGCH 3-Index-Step Threshold IE, HARQ Info for E-DCH IE or HS-DSCH Configured Indicator IE are not present in the E-DPCH Information IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If any the HS-DSCH Configured Indicator IE, of the Maximum Set of E-DPDCHs IE, Puncture Limit IE or E-TTI IE are present in the E-DPCH Information IE and the E-DCH FDD Information IE is not present in the RADIO LINK RECONFIGURATION REQUEST message, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes one of the Not Used IEs, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH RL Indication IE set to "E-DCH", but no E-DCH FDD Information IE, and the Node B Communication Context is not configured for E-DCH, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH FDD Information IE but no E-DCH RL Indication IE set to "E-DCH", then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
If the RADIO LINK RECONFIGURATION REQUEST message does not contain the E-DCH Decoupling Indication IE but contains the HS-PDSCH RL ID IE and/or the Serving E-DCH RL IE, and if both HS-DSCH and E-DCH are configured in the new configuration but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not in the same cell, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the HS-PDSCH RL ID IE and the E-DPCH Information IE which includes the HS-DSCH Configured Indicator IE set as “HS-DSCH not configured” then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains any of the E-DCH FDD Information To Modify IE, E-DCH MAC-d Flows To Add IE or E-DCH MAC-d Flows To Delete IE in addition to the E-DCH FDD Information IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains any of the E-DCH FDD Information To Modify IE, E-DCH MAC-d Flows To Add IE, E-DCH MAC-d Flows To Delete IE and the Node B Communication Context is not configured for E-DCH, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH FDD Information To Modify IE deleting the last remaining E-DCH Logical Channel of an E-DCH MAC-d Flow, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes E-DCH FDD Information IE and the E-DCH is already configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[TDD - if the radio link was not previously configured to support E-DCH, then if the RADIO LINK RECONFIGURATION REQUEST message includes one of the following E-DCH information elements then it shall contain all of them otherwise the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.: E-DCH Serving RL IE, [3.84Mcps TDD and 7.68Mcps - E-PUCH Information IE, E-TFCS Information TDD IE], [1.28Mcps TDD - E-PUCH Information LCR IE, E-TFCS Information TDD IE], E-DCH MAC-d Flows to Add IE, and [3.84Mcps TDD - E-DCH TDD Information IE] [1.28Mcps TDD - E-DCH TDD Information LCR IE] [7.68Mcps TDD - E-DCH TDD Information 7.68Mcps IE].]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity DTX-DRX Information To Modify IE in addition to the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE in addition to the Continuous Packet Connectivity HS-SCCH less Information IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. ]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE while the Continuous Packet Connectivity HS-SCCH less configuration isn’t configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity DTX-DRX Information To Modify IE while the Continuous Packet Connectivity DTX-DRX configuration isn’t configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the DRX Information To Modify IE in Continuous Packet Connectivity DTX-DRX Information To Modify IE while the Continuous Packet Connectivity DRX configuration isn’t configured in the Node B Communication Context, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH Indicator IE set to "Uplink DCH only" but no Transport Format Set IE for the uplink for this DCH and the Node B had ignored the configuration of Transport Format Set for uplink, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH Indicator IE set to "Downlink DCH only" but no Transport Format Set IE for the downlink for this DCH and the Node B had ignored the configuration of Transport Format Set for downlink, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the Transport Bearer Not Requested Indicator IE for a DCH but does not contain the corresponding DCH ID IE and the Unidirectional DCH indicator IE set to "Uplink DCH only" for the DCH in DCH Information To Add IE, the Node B shall reject the procedure using the the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the concerned Node B Communication Context is configured to apply UL DPCCH Slot Format 0 or 2 and execute Continuous Packet Connectivity DTX-DRX operation, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the concerned Node B Communication Context is configured to apply MIMO, allowed to apply 64 QAM, establish the secondary serving HS-DSCH Radio Link, or apply Single Stream MIMO in the new configuration but is not configured to use flexible MAC-d PDU Size, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Transport Bearer Not Requested Indicator IE for a DCH in the RL Specific DCH Information IE but does not include the DCH ID IE for the DCH in the DCHs to Add IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD – If the RADIO LINK RECONFIGURATION REQUEST message contains the Continuous Packet Connectivity DTX-DRX Information IE but the concerned Node B Communication Context is not previously configured to use F-DPCH, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the concerned Node B Communication Context is configured to have the Serving E-DCH Radio Link but there is at least one E-DCH MAC-d flow which the Transport Bearer is not configured in the Node B, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Transport Bearer Not Requested Indicator IE for a DCH for a specific RL and the specific RL is combined with existing RL which the transport bearer is established for the DCH in the Node B, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
If ALCAP is not used, if the concerned Node B Communication Context is configured to establish a DCH, an E-DCH MAC-d flow and/or an HS-DSCH MAC-d flow but the RADIO LINK RECONFIGURATION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE for the DCH, the E-DCH MAC-d flow and/or HS-DSCH MAC-d flow, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
 [1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Semi-Persistent scheduling Information to Modify LCR IE in addition to the HS-DSCH Semi-Persistent scheduling Information LCR IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[1.28 Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Semi-Persistent scheduling Information to Modify LCR IE in addition to the E-DCH Semi-Persistent scheduling Information LCR IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
If, in the new configuration, there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use “Flexible RLC PDU Size” for an HS-DSCH but is not configured to use Maximum MAC-d PDU Size Extended, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
If, in the new configuration, the concerned Node B Communication Context is configured to use  MAC-d PDU Size Index for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use “Flexible RLC PDU Size”, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH FDD Secondary Serving Information IE but does not contain the C-ID IE in the Additional HS Cell Information RL Reconf Prep IE or the message includes the C-ID IE but does not contain the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Prep IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains a MIMO Activation Indicator IE and a Single Stream MIMO Activation Indicator IE in the HS-DSCH FDD Information IE or in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Req IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains more than one of a MIMO Activation Indicator IE, a Single Stream MIMO Activation Indicator IE, a MIMO with four transmit antennas Activation Indicator IE, a Dual Stream MIMO with four transmit antennas Activation Indicator IE in the HS-DSCH FDD Information IE or in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Req IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the concerned Node B Communication Context is configured to apply MIMO and Single Stream MIMO for the HS-DSCH Radio Link or the Secondary Serving Radio link, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the Additional E-DCH Cell Information RL Reconf Req IE and if the E-DPCH Information IE is not present or the E-DPCH Information was not configured in the Node B Communication Context, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the Additional E-DCH Cell Information RL Reconf Req IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE in the Additional E-DCH Cell Information RL Reconf Req IE and the C-ID IE is not included but the Radio Link indicated by the E-DCH Additional RL ID IE is not configured in the current Node B Communication Context as a Secondary Serving HS-DSCH radio link without any configured Additional E-DCH, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the Additional HS Cell Information RL Reconf Req IE and the new configuration contains more than one secondary serving HS-DSCH RL, and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1"which are previously assigned to the RL or received in the Ordinal Number Of Frequency IE in the HS-DSCH FDD Secondary Serving Information IE or the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the Additional HS Cell Information RL Reconf Req IE and the new configuration contains more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value “1”, the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the UL CLTD Information IE but does not contain the F-TPICH Information IE, or if it contains HS-DSCH Preconfiguration Setup IE with UL CLTD Information IE but without F-TPICH Information IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the UL MIMO Reconfiguration IE in E-DCH FDD Information IE, and the choice of Setup, Configuration Change or Removal of UL MIMO is "Setup", or if it contains HS-DSCH Preconfiguration Setup IE with UL MIMO Information IE but without UL CLTD Information IE, but the UL CLTD Information IE is not present and is not previously configured, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains more than one of a MIMO Activation Indicator IE, a MIMO with four transmit antennas Activation Indicator IE, a Dual Stream MIMO with four transmit antennas Activation Indicator IE in HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
[FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the Fast TTI switching Mode Requested Synchronized IE in the E-DCH FDD Information To Modify IE, then the Node B shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]
8.3.6	Radio Link Deletion
8.3.6.1	General
The Radio Link Deletion procedure is used to release the resources in a Node B for one or more established radio links towards a UE.
The Radio Link Deletion procedure may be initiated by the CRNC at any time when the Node B Communication Context exists.
8.3.6.2	Successful Operation

Figure 36: Radio Link Deletion procedure, Successful Operation
The procedure is initiated with a RADIO LINK DELETION REQUEST message sent from the CRNC to the Node B using the Communication Control Port assigned to the concerned Node B Communication Context.
Upon receipt of this message, the Node B shall delete the radio link(s) identified by the RL ID IE, Node B Communication Context ID IE and CRNC Communication Context ID IE and release all associated resources and respond to the CRNC with a RADIO LINK DELETION RESPONSE message.
[FDD - After deletion of the RL(s), the UL out-of-sync algorithm defined in ref. TS 25.214 [10] shall for each of the remaining RL Set(s) use the maximum value of the parameters N_OUTSYNC_IND and T_RLFAILURE that are configured in the cells supporting the radio links of the RL Set and the UL in-sync algorithm defined in ref. TS 25.214 [10] shall for each of the remaining RL Set(s) use the minimum value of the parameters N_INSYNC_IND that are configured in the cells supporting the radio links of the RL Set.]
[FDD – If the RL indicated by the RL ID IE in the RADIO LINK DELETION REQUEST message is the serving HS-DSCH Radio link and a related secondary serving HS-DSCH Radio Link exists in the Node B, the Node B shall delete the secondary serving HS-DSCH Radio Link.]
[FDD – If the RL indicated by the RL ID IE in the RADIO LINK DELETION REQUEST message is the secondary serving HS-DSCH Radio link, the Node B shall delete the secondary serving HS-DSCH Radio Link.]
8.3.6.3	Unsuccessful Operation
-
8.3.6.4	Abnormal Conditions
If the RL indicated by the RL ID IE, Node B Communication Context ID IE and CRNC Communication Context ID IE does not exist, the Node B shall respond with the RADIO LINK DELETION RESPONSE message and use the CRNC Communication Context ID IE received in the RADIO LINK DELETION REQUEST message.
8.3.7	Downlink Power Control [FDD]
8.3.7.1	General
The purpose of this procedure is to balance the DL transmission powers of one or more Radio Links used for the related UE-UTRAN connection within the Node B. The Downlink Power Control procedure may be initiated by the CRNC at any time when the Node B Communication Context exists, irrespective of other ongoing CRNC initiated dedicated NBAP procedures towards this Node B Communication Context. The only exception occurs when the CRNC has requested the deletion of the last RL via this Node B, in which case the Downlink Power Control procedure shall no longer be initiated.
8.3.7.2	Successful Operation

Figure 37: Downlink Power Control procedure, Successful Operation
The procedure is initiated by the CRNC sending a DL POWER CONTROL REQUEST message to the Node B using the Communication Control Port assigned to the concerned Node B Communication Context.
The Power Adjustment Type IE defines the characteristic of the power adjustment.
If the value of the Power Adjustment Type IE is "Common", the Power Balancing Adjustment Type of the Node B Communication Context shall be set to "Common". As long as the Power Balancing Adjustment Type of the Node B Communication Context is set to "Common", the Node B shall perform the power adjustment (see below) for all existing and future radio links associated with the context identified by the Node B Communication Context ID IE and use a common DL reference power level.
If the value of the Power Adjustment Type IE is "Individual", the Power Balancing Adjustment Type of the Node B Communication Context shall be set to "Individual". The Node B shall perform the power adjustment (see below) for all radio links addressed in the message using the given DL Reference Powers per RL. If the Power Balancing Adjustment Type of the Node B Communication Context was set to "Common" before this message was received, power balancing on all radio links not addressed by the DL POWER CONTROL REQUEST message shall remain to be executed in accordance with the existing power balancing parameters which are now considered RL individual parameters. Power balancing will not be started on future radio links without a specific request.
If the value of the Power Adjustment Type IE is "None", the Power Balancing Adjustment Type of the Node B Communication Context shall be set to "None" and the Node B shall suspend on going power adjustments for all radio links for the Node B Communication Context.
If the Inner Loop DL PC Status IE is present and set to "Active", the Node B shall activate inner loop DL power control for all radio links for the Node B Communication Context. If the Inner Loop DL PC Status IE is present and set to "Inactive", the Node B shall deactivate inner loop DL power control for all radio links for the Node B Communication Context according to ref. TS 25.214 [10].
Power Adjustment
The power balancing adjustment shall be superimposed on the inner loop power control adjustment (see ref. TS 25.214 [10]) if activated. The power balancing adjustment shall be such that:
 with an accuracy of ±0.5 dB
where the sum is performed over an adjustment period corresponding to a number of frames equal to the value of the Adjustment Period IE, Pref is the value of the DL Reference Power IE, PP-CPICH is the power used on the primary CPICH, Pinit is the code power of the last slot of the previous adjustment period and r is given by the Adjustment Ratio IE. If the last slot of the previous adjustment period is within a transmission gap due to compressed mode, Pinit shall be set to the same value as the code power of the slot just before the transmission gap.
The adjustment within one adjustment period shall in any case be performed with the constraints given by the Max Adjustment Step IE and the DL TX power range set by the CRNC.
The power adjustments shall be started at the first slot of a frame with CFN modulo the value of Adjustment Period IE equal to 0 and shall be repeated for every adjustment period and shall be restarted at the first slot of a frame with CFN=0, until a new DL POWER CONTROL REQUEST message is received or the RL is deleted.
8.3.7.3	Abnormal Conditions
-
8.3.8	Dedicated Measurement Initiation
8.3.8.1	General
This procedure is used by a CRNC to request the initiation of measurements on dedicated resources in a Node B.
The Dedicated Measurement Initiation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1 except when the Node B Communication Context ID IE in the DEDICATED MEASUREMENT INITIATION REQUEST message is set to the reserved value "All NBCC".
If the Node B Communication Context ID IE in the DEDICATED MEASUREMENT INITIATION REQUEST message is set to the reserved value "All NBCC", the Dedicated Measurement Initiation procedure may be initiated by the CRNC at any time when the Node B Communication Context exists.
8.3.8.2	Successful Operation

Figure 38: Dedicated Measurement Initiation procedure, Successful Operation
The procedure is initiated with a DEDICATED MEASUREMENT INITIATION REQUEST message sent from the CRNC to the Node B using the Communication Control Port assigned to the Node B Communication Context.
Upon reception, the Node B shall initiate the requested measurement according to the parameters given in the DEDICATED MEASUREMENT INITIATION REQUEST message. Unless specified below the meaning of the parameters are given in other specifications.
If the Node B Communication Context ID IE equals the reserved value "All NBCC", this measurement request shall apply for all current and future Node B Communication Contexts controlled via the Communication Control Port on which the DEDICATED MEASUREMENT INITIATION REQUEST message was received. Otherwise, this measurement request shall apply for the requested Node B Communication Context ID only.
If the Node B Communication Context ID IE equals the reserved value "All NBCC", the measurement request shall be treated as a single measurement, despite applying to multiple contexts. This means that it may only be terminated or failed on "All NBCC".
If the Node B Communication Context ID IE equals the reserved value "All NBCC", the measurement shall be initiated only for those Node B Communication Contexts handling a mode (FDD, 3.84Mcps TDD, 7.68Mcps TDD or 1.28Mcps TDD) for which the concerned measurement is specified in TS 25.215 [4] and TS 25.225 [5]. The initiation of the measurement for a Node B Communication Context may be delayed until the Reconfiguration CFN has elapsed if either a Prepared Reconfiguration exists or a Prepared Reconfiguration no longer exists but the Reconfiguration CFN has not yet elapsed.
If the Dedicated Measurement Object Type is indicated as being "RL" in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all indicated Radio Links.
[FDD - If the Dedicated Measurement Object Type is indicated as being "RLS" in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all indicated Radio Link Sets.]
[FDD - If the Dedicated Measurement Object Type is indicated as being "ALL RL" in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all current and future Radio Links within the Node B Communication Context.]
[TDD - If the Dedicated Measurement Object Type is indicated as being "ALL RL" in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for one existing DPCH per CCTrCH in each used time slot of current and future Radio Links within the Node B Communication Context, provided the measurement type is applicable to the respective DPCH.]
[FDD - If the Dedicated Measurement Object Type is indicated as being "ALL RLS" in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all existing and future Radio Link Sets within the Node B Communication Context.]
[TDD - If the DPCH ID IE or DPCH ID 7.68Mcps IE is provided within the RL Information, the measurement request shall apply for the requested physical channel individually. If no DPCH ID IE, HS-SICH ID IE, DPCH ID 7.68Mcps IE and no PUSCH Information IE is provided within the RL Information, the measurement request shall apply for one existing physical channel per CCTrCH in each used time slot of the Radio Link, provided the measurement type is applicable to this physical channel.]
[TDD - If the PUSCH Information IE is provided within the RL Information, the measurement request shall apply for the requested physical channel individually.]
[TDD - If the HS-SICH Information IE is provided within the RL Information, the measurement request shall apply for the requested physical channel individually.] 
[TDD - If the Dedicated Measurement Type IE is set to "HS-SICH reception quality ", the Node B shall initiate measurements of the failed, missed and total HS-SICH transmissions on all of the HS-SICH assigned to this Node B Communication Context. If either the failed or missed HS-SICH transmission satisfies the requested report characteristics, the Node B shall report the result of both failed and missed transmission measurements along with the total number of transmissions.]
If the CFN Reporting Indicator IE is set to "FN Reporting Required", the CFN IE shall be included in the DEDICATED MEASUREMENT REPORT message or in the DEDICATED MEASUREMENT INITIATION RESPONSE message, the latter only in the case the Report Characteristics IE is set to "On Demand". The reported CFN shall be the CFN at the time when the measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]).
[FDD - If the Number Of Reported Cell Portions IE is included in the DEDICATED MEASUREMENT INITIATION REQUEST message, the value shall be used to determine how many Cell Portion ID IEs and SIR Value IEs shall be included in Best Cell Portions IE in the DEDICATED MEASUREMENT REPORT message or in the DEDICATED MEASUREMENT INITIATION RESPONSE message.] 
[1.28Mcps TDD - If the Number Of Reported Cell Portions LCR IE is included in the DEDICATED MEASUREMENT INITIATION REQUEST message, the value shall be used to determine how many Cell Portion LCR ID IEs and RSCP Value IEs shall be included in Best Cell Portions LCR IE in the DEDICATED MEASUREMENT REPORT message or in the DEDICATED MEASUREMENT INITIATION RESPONSE message.
[1.28Mcps TDD - If the Dedicated Measurement Type IE is set to "AOA per Cell Portion LCR", the Node B shall initiate measurements of the Angle Of Arrival LCR for all Best CELL Portions in the CELL.]
Report characteristics 
The Report Characteristics IE indicates how the reporting of the measurement shall be performed. See also Annex B.
If the Report Characteristics IE is set to "On Demand" and if the CFN IE is not provided, the Node B shall return the result of the measurement immediately. If the CFN IE is provided, it indicates the frame for which the measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]).
If the Report Characteristics IE is set to "Periodic", the Node B shall periodically initiate the Dedicated Measurement Report procedure for this measurement, with the requested report frequency. If the CFN IE is provided, it indicates the frame for which the first measurement value of a periodic reporting shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]).
If the Report Characteristics IE is set to "Event A", the Node B shall initiate the Dedicated Measurement Reporting procedure when the measured entity rises above the requested threshold and stays there for the requested hysteresis time. If the Measurement Hysteresis Time IE is not included, the Node B shall use the value zero for the hysteresis time.
If the Report Characteristics IE is set to "Event B", the Node B shall initiate the Dedicated Measurement Reporting procedure when the measured entity falls below the requested threshold and stays there for the requested hysteresis time. If the Measurement Hysteresis Time IE is not included, the Node B shall use the value zero for the hysteresis time.
If the Report Characteristics IE is set to "Event C", the Node B shall initiate the Dedicated Measurement Reporting procedure when the measured entity rises by an amount greater than the requested threshold within the requested time. After having reported this type of event, the next C event reporting for the same measurement cannot be initiated before the rising time specified by the Measurement Change Time IE has elapsed since the previous event reporting.
If the Report Characteristics IE is set to "Event D", the Node B shall initiate the Dedicated Measurement Reporting procedure when the measured entity falls by an amount greater than the requested threshold within the requested time. After having reported this type of event, the next D event reporting for the same measurement cannot be initiated before the falling time specified by the Measurement Change Time IE has elapsed since the previous event reporting.
If the Report Characteristics IE is set to "Event E", the Node B shall initiate the Dedicated Measurement Reporting procedure when the measured entity rises above the 'Measurement Threshold 1' and stays there for the 'Measurement Hysteresis Time' (Report A). When the conditions for Report A are met and the Report Periodicity IE is provided, the Node B shall also initiate the Dedicated Measurement Reporting procedure periodically. If the conditions for Report A have been met and the measured entity falls below the 'Measurement Threshold 2' and stays there for the 'Measurement Hysteresis Time', the Node B shall initiate the Dedicated Measurement Reporting procedure (Report B) as well as terminate any corresponding periodic reporting. If the Measurement Threshold 2 IE is not present, the Node B shall use the value of the Measurement Threshold 1 IE instead. If the Measurement Hysteresis Time IE is not included, the Node B shall use the value zero as hysteresis times for both Report A and Report B.
If the Report Characteristics IE is set to "Event F", the Node B shall initiate the Dedicated Measurement Reporting procedure when the measured entity falls below the 'Measurement Threshold 1' and stays there for the 'Measurement Hysteresis Time' (Report A). When the conditions for Report A are met and the Report Periodicity IE is provided, the Node B shall also initiate the Dedicated Measurement Reporting procedure periodically. If the conditions for Report A have been met and the measured entity rises above the 'Measurement Threshold 2' and stays there for the 'Measurement Hysteresis Time', the Node B shall initiate the Dedicated Measurement Reporting procedure (Report B) as well as terminate any corresponding periodic reporting. If the Measurement Threshold 2 IE is not present, the Node B shall use the value of the Measurement Threshold 1 IE instead. If the Measurement Hysteresis Time IE is not included, the Node B shall use the value zero as hysteresis times for both Report A and Report B.
If the Report Characteristics IE is set to "On Modification" and if the SFN IE is not provided, the Node B shall report the result of the requested measurement immediately. If the SFN IE is provided, it indicates the frame for which the measurement value shall be provided. Then, the Node B shall initiate the Dedicated Measurement Reporting procedure in accordance to the following conditions:
1. If the Dedicated Measurement Type IE is set to "Best Cell Portions LCR":
-	The Node B shall initiate the Dedicated Measurement Reporting procedure when the Dedicated Measurement Value "Best Cell Portions LCR" changes.
If the Report Characteristics IE is not set to "On Demand", the Node B is required to perform reporting for a dedicated measurement object, in accordance with the conditions provided in the DEDICATED MEASUREMENT INITIATION REQUEST message, as long as the object exists. If no dedicated measurement object for which a measurement is defined exists anymore, the Node B shall terminate the measurement locally, i.e. without reporting this to the CRNC.
If at the start of the measurement, the reporting criteria are fulfilled for any of Event A, Event B, Event E or Event F, the Node B shall initiate the Dedicated Measurement Reporting procedure immediately, and then continue with the measurements as specified in the DEDICATED MEASUREMENT INITIATION REQUEST message.
Higher layer filtering 
The Measurement Filter Coefficient IE indicates how filtering of the measurement values shall be performed before measurement event evaluation and reporting.
The averaging shall be performed according to the following formula.
	
The variables in the formula are defined as follows
Fn is the updated filtered measurement result
Fn-1 is the old filtered measurement result
	Mn is the latest received measurement result from physical layer measurements, the unit used for Mn is the same unit as the reported unit in the DEDICATED MEASUREMENT INITIATION RESPONSE, DEDICATED MEASUREMENT REPORT messages or the unit used in the event evaluation (i.e. same unit as for Fn)
a = 1/2(k/2) , where k is the parameter received in the Measurement Filter Coefficient IE. If the Measurement Filter Coefficient IE is not present, a shall be set to 1 (no filtering)
In order to initialise the averaging filter, F0 is set to M1 when the first measurement result from the physical layer measurement is received.
Measurement Recovery Behavior:
If the Measurement Recovery Behavior IE is included in the DEDICATED MEASUREMENT INITIATION REQUEST message, the Node B shall, if Measurement Recovery Behavior is supported, include the Measurement Recovery Support Indicator IE in the DEDICATED MEASUREMENT INITIATION RESPONSE message and perform the Measurement Recovery Behavior as described in subclause 8.3.9.2.
Response message
If the Node B was able to initiate the measurement requested by the CRNC, it shall respond with the DEDICATED MEASUREMENT INITIATION RESPONSE message using the Communication Control Port assigned to the Node B Communication Context. The message shall include the same Measurement ID that was used in the measurement request. The DEDICATED MEASUREMENT INITIATION RESPONSE message shall be sent even if the initiation is delayed for some Node B Communication Contexts due to an existing Prepared Reconfiguration or that the Reconfiguration CFN has not yet elapsed.
Only in the case where the Report Characteristics IE is set to "On Demand", the DEDICATED MEASUREMENT INITIATION RESPONSE message shall include the Dedicated Measurement Object Type IE containing the measurement result. [TDD - In the case that the measurement was performed on a particular HS-SICH, the Node B shall include the HS-SICH ID IE that indicates which HS-SICH was measured.]
In the case where the Node B Communication Context ID IE is set to "All NBCC", the CRNC Communication Context ID IE in the DEDICATED MEASUREMENT INITIATION RESPONSE shall be set to the value "All CRNCCC", which is reserved for this purpose.
[FDD - If the Alternative Format Reporting Indicator IE is set to "Alternative format is allowed" in the DEDICATED MEASUREMENT INITIATION REQUEST message, the Node B may include the Extended Round Trip Time IE in the DEDICATED MEASUREMENT INITIATION RESPONSE message.]
Interaction with Reset Procedure:
If a measurement has been requested with the Node B Communication Context ID IE set to "All NBCC", the Node B shall terminate the measurement locally if either the CRNC or the Node B initiates the Reset procedure for the relevant Communication Control Port or the entire Node B.
8.3.8.3	Unsuccessful Operation

Figure 39: Dedicated Measurement Initiation procedure: Unsuccessful Operation
If the requested measurement cannot be initiated, the Node B shall send a DEDICATED MEASUREMENT INITIATION FAILURE message using the Communication Control Port assigned to the Node B Communication Context. The message shall include the same Measurement ID that was used in the DEDICATED MEASUREMENT INITIATION REQUEST message and the Cause IE set to an appropriate value.
In the case where the Node B Communication Context ID IE is set to "All NBCC" the CRNC Communication Context ID IE in the DEDICATED MEASUREMENT INITIATION FAILURE shall be set to the value "All CRNCCC", which is reserved for this purpose.
Typical cause values are as follows:
Radio Network Layer cause
-	Measurement not supported for the object
-	Measurement Temporarily not Available
Miscellaneous Cause
-	O&M Intervention
-	Control processing overload
-	HW failure
8.3.8.4	Abnormal Conditions
The allowed combinations of the Dedicated Measurement Type and Report Characteristics Type are shown in the table below marked with "X". For not allowed combinations, the Node B shall regard the Dedicated Measurement Initiation procedure as failed.
Table 4: Allowed Dedicated Measurement Type and Report Characteristics Type combinations
Dedicated Measurement Type
Report Characteristics Type

On Demand
Periodic
Event A
Event B
Event C
Event D
Event E
Event F
On Modification
SIR
X
X
X
X
X
X
X
X

SIR Error
X
X
X
X
X
X
X
X

Transmitted Code Power
X
X
X
X
X
X
X
X

RSCP
X
X
X
X
X
X
X
X

Rx Timing Deviation
X
X
X
X


X
X

Round Trip Time
X
X
X
X
X
X
X
X

Rx Timing Deviation LCR
X
X
X
X


X
X

HS-SICH reception quality
X
X
X
X


X
X

Best Cell Portions
X
X







Angle Of Arrival LCR
X
X







Rx Timing Deviation 7.68Mcps
X
X
X
X


X
X

Rx Timing Deviation 3.84Mcps Extended
X
X
X
X


X
X

Best Cell Portions LCR
X
X






X
AOA per Cell Portion LCR
X
X







UE transmission power headroom
X
X

X



X

DL transport block size
X
X








If the Dedicated Measurement Type received in the Dedicated Measurement Type IE is not defined in ref. TS 25.215 [4] or TS 25.225 [5] to be measured on the Dedicated Measurement Object Type received in the DEDICATED MEASUREMENT INITIATION REQUEST message, the Node B shall regard the Dedicated Measurement Initiation procedure as failed. 
If the CFN IE is included in the DEDICATED MEASUREMENT INITIATION REQUEST message and the Report Characteristics IE is other than "Periodic" or "On Demand", the Node B shall regard the Dedicated Measurement Initiation procedure as failed.
8.3.9	Dedicated Measurement Reporting
8.3.9.1	General
This procedure is used by the Node B to report the result of measurements requested by the CRNC with the Dedicated Measurement Initiation procedure. The Node B may initiate the Dedicated Measurement Reporting procedure at any time after establishing a Radio Link, as long as the Node B Communication Context exists.
8.3.9.2	Successful Operation

Figure 40: Dedicated Measurement Reporting procedure, Successful Operation
If the requested measurement reporting criteria are met, the Node B shall initiate the Dedicated Measurement Reporting procedure. The DEDICATED MEASUREMENT REPORT message shall use the Communication Control Port assigned to the Node B Communication Context. If the measurement was initiated (by the Dedicated Measurement Initiation procedure) for multiple dedicated measurement objects, the Node B may include measurement values for multiple objects in the DEDICATED MEASUREMENT REPORT message. Unless specified below, the meaning of the parameters are given in other specifications.
The Measurement ID IE shall be set to the Measurement ID provided by the CRNC when initiating the measurement with the Dedicated Measurement Initiation procedure.
[TDD - In the case that the measurement was performed on a particular HS-SICH, the Node B shall include the HS-SICH ID IE that indicates which HS-SICH was measured.]
If the achieved measurement accuracy does not fulfil the given accuracy requirement (see ref. TS 25.133 [22] and TS 25.123 [23]) or the measurement is temporarily not available in case Measurement Recovery Behavior is supported, the Measurement not available shall be reported. If the Node B was configured to perform the Measurement Recovery Behavior, the Node B shall indicate Measurement Available to the CRNC when the achieved measurement accuracy again fulfils the given accuracy requirement (see ref. TS 25.133 [22] and TS 25.123 [23]) and include the Measurement Recovery Report Indicator IE in the DEDICATED MEASUREMENT REPORT message if the requested measurement reporting criteria are not met.
[FDD - If the Alternative Format Reporting Indicator IE was set to "Alternative format is allowed" in the DEDICATED MEASUREMENT INITIATION REQUEST message setting up the measurement to be reported, the Node B may include the Extended Round Trip Time IE in the DEDICATED MEASUREMENT REPORT message.]
8.3.9.3	Abnormal Conditions
-
8.3.10	Dedicated Measurement Termination
8.3.10.1	General
This procedure is used by the CRNC to terminate a measurement previously requested by the Dedicated Measurement Initiation procedure.
The Dedicated Measurement Termination procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1 except if the measurement was initiated by the Dedicated Measurement Initiation procedure using the reserved value "All NBCC".
If the measurement was initiated by the Dedicated Measurement Initiation procedure using the reserved value "All NBCC", the Dedicated Measurement Termination procedure may be initiated by the CRNC at any time.
8.3.10.2	Successful Operation

Figure 41: Dedicated Measurement Termination procedure, Successful Operation
This procedure is initiated with a DEDICATED MEASUREMENT TERMINATION REQUEST message, sent from the CRNC to the Node B using the Communication Control Port assigned to the Node B Communication Context.
Upon reception, the Node B shall terminate reporting of dedicated measurements corresponding to the received Measurement ID IE.
8.3.10.3	Abnormal Conditions
-
8.3.11	Dedicated Measurement Failure
8.3.11.1	General
This procedure is used by the Node B to notify the CRNC that a measurement previously requested by the Dedicated Measurement Initiation procedure can no longer be reported. The Node B is allowed to initiate the DEDICATED MEASUREMENT FAILURE INDICATION message at any time after having sent the RADIO LINK SETUP RESPONSE message, as long as the Node B Communication Context exists.
8.3.11.2	Successful Operation

Figure 42: Dedicated Measurement Failure procedure, Successful Operation
This procedure is initiated with a DEDICATED MEASUREMENT FAILURE INDICATION message, sent from the Node B to the CRNC using the Communication Control Port assigned to the Node B Communication Context, to inform the CRNC that a previously requested measurement can no longer be reported. The Node B has locally terminated the indicated measurement.
If the failed measurement was initiated with the Node B Communication Context ID IE set to the reserved value "All NBCC" and the Node B has terminated the measurement reporting of the measurement corresponding to the Measurement ID indicated in the DEDICATED MEASUREMENT FAILURE INDICATION message, the CRNC Communication Context ID IE shall be set to the value "All CRNCCC".
8.3.11.3	Abnormal Conditions
-
8.3.12	Radio Link Failure
8.3.12.1	General
This procedure is used by the Node B to indicate a failure in one or more Radio Links [FDD - or Radio Link Sets][TDD or CCTrCHs within a Radio Link].
The Node B may initiate the Radio Link Failure procedure at any time after establishing a Radio Link.
8.3.12.2	Successful Operation

Figure 43: Radio Link Failure procedure, Successful Operation
When the Node B detects that one or more Radio Link(s) [FDD - or Radio Link Set(s)] [TDD - or CCTrCHs within a Radio Link] are no longer available, it sends the RADIO LINK FAILURE INDICATION message to the CRNC indicating the failed Radio Link(s) or Radio Link Set(s) or CCTrCHs with the most appropriate cause values in the Cause IE. The message shall use the Communication Control Port assigned to the concerned Node B Communication Context.
If the failure concerns one or more individual Radio Link(s), the Node B shall indicate the affected Radio Link(s) using the RL Information IE. [FDD - If the failure concerns one or more Radio Link Set(s), the Node B shall indicate the affected Radio Link Set(s) using the RL Set Information IE.] [TDD - If the failure concerns only the failure of one or more CCTrCHs within a radio link, the Node B shall indicate the affected CCTrCHs using the CCTrCH ID IE.]
When the Radio Link Failure procedure is used to notify the loss of UL synchronisation of a [FDD - Radio Link Set] [TDD - Radio Link or CCTrCHs within a Radio Link] on the Uu interface, the RADIO LINK FAILURE INDICATION message shall be sent, with the Cause IE set to "Synchronisation Failure", when indicated by the UL out-of-sync algorithm defined in TS 25.214 [10] and TS 25.224 [21]. [FDD - The algorithms in TS 25.214 [10] shall use the maximum value of the parameters N_OUTSYNC_IND and T_RLFAILURE, and the minimum value of the parameters N_INSYNC_IND, that are configured in the cells supporting the radio links of the RL Set.]
[FDD - When the Radio Link Failure procedure is used to indicate permanent failure in one or more Radio Link(s) / Radio Link Set(s) due to the occurrence of an UL or DL frame with more than one transmission gap caused by one or more compressed mode pattern sequences, the DL transmission shall be stopped and the RADIO LINK FAILURE INDICATION message shall be sent with the cause value "Invalid CM Settings". After sending the RADIO LINK FAILURE INDICATION message to notify the permanent failure, the Node B shall not remove the Radio Link(s)/Radio Link Set(s) from the Node B Communication Context or the Node B Communication Context itself.]
[FDD - When the Radio Link Failure Procedure is used to indicate E-DCH non serving cell processing issue, the RADIO LINK FAILURE INDICATION shall be sent, with the Cause IE set to "Not enough user plane processing resources".]
In the other cases, the Radio Link Failure procedure is used to indicate that one or more Radio Link(s)/Radio Link Set(s) are permanently unavailable and cannot be restored. After sending the RADIO LINK FAILURE INDICATION message to notify the permanent failure, the Node B shall not remove the Radio Link/Radio Link Set from the Node B Communication Context or the Node B Communication Context itself. When applicable, the retention priorities associated with the transport channels shall be used by the Node B to prioritise which Radio Link(s)/Radio Link Set(s) to indicate as unavailable to the CRNC.
Typical cause values are:
Radio Network Layer Causes:
-	Synchronisation Failure
-	Invalid CM settings
Transport Layer Causes:
-	Transport Resources Unavailable
Miscellaneous Causes:
-	Control Processing Overload
-	HW Failure
-	O&M Intervention
-	Not enough user plane processing resources
8.3.12.3	Abnormal Conditions
-
8.3.13	Radio Link Restoration
8.3.13.1	General
This procedure is used by the Node B to notify the achievement and re-achievement of uplink synchronisation of one or more [FDD - Radio Link Sets][TDD - Radio Links or CCTrCHs within a Radio Link] on the Uu interface.
The Node B may initiate the Radio Link Restoration procedure at any time after establishing a Radio Link.
8.3.13.2	Successful Operation

Figure 44: Radio Link Restoration procedure, Successful Operation
The Node B shall send the RADIO LINK RESTORE INDICATION message to the CRNC when indicated by the UL synchronisation detection algorithm defined in ref. TS 25.214 [10] and TS 25.224 [21] [FDD -, or when the Fast Reconfiguration Mode IE has been included in the RADIO LINK RECONFIGURATION COMMIT message and the Node B has detected that the UE has changed to the new configuration. The algorithm in ref. TS 25.214 [10] shall use the minimum value of the parameters N_INSYNC_IND that are configured in the cells supporting the radio links of the RL Set.] The message shall use the Communication Control Port assigned to the concerned Node B Communication Context.
[TDD - If the re-established Uu synchronisation concerns one or more individual Radio Links, the Node B shall indicate the affected Radio Link(s) using the RL Information IE.] [TDD - If the re-established Uu synchronisation concerns one or more individual CCTrCHs within a radio link, the Node B shall indicate the affected CCTrCHs using the CCTrCH ID IE.] [FDD - If the re-established Uu synchronisation concerns one or more Radio Link Set(s), the Node B shall indicate the affected Radio Link Set(s) using the RL Set Information IE.]
[FDD - The Node B shall send the RADIO LINK RESTORE INDICATION message when the E-DCH processing issue condition has ceased.]
8.3.13.3	Abnormal Condition
-
8.3.14	Compressed Mode Command [FDD]
8.3.14.1	General
The Compressed Mode Command procedure is used to activate or deactivate the compressed mode in the Node B for one Node B Communication Context.
The Compressed Mode Command procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
8.3.14.2	Successful Operation

Figure 47: Compressed Mode Command procedure, Successful Operation
The procedure is initiated by the CRNC sending a COMPRESSED MODE COMMAND message to the Node B using the Communication Control Port assigned to the concerned Node B Communication Context.
The Node B shall deactivate all the ongoing Transmission Gap Pattern Sequences at the CM Configuration Change CFN IE requested by the CRNC when receiving the COMPRESSED MODE COMMAND message from the CRNC. From that moment on, all Transmission Gap Pattern Sequences included in Transmission Gap Pattern Sequence Status IE repetitions (if present) shall be started when the indicated TGCFN IE elapses. The CM Configuration Change CFN IE in the Active Pattern Sequence Information IE and TGCFN IE for each sequence refer to the next coming CFN with that value.
If the values of the CM Configuration Change CFN IE and the TGCFN IE are equal, the concerned Transmission Gap Pattern Sequence shall be started immediately at the CFN with a value equal to the value received in the CM Configuration Change CFN IE.
If the Affected HS-DSCH serving cell List IE is included, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with C-ID IE included in Affected HS-DSCH serving cell List IE.  Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.
If the concerned Node B Communication Context is configured to use F-DPCH in the downlink, the Node B shall not transmit the F-DPCH during the downlink transmission gaps according to TS 25.211 [7]. But in all slots outside of the downlink transmission gaps the Node B shall transmit the F-DPCH with the normal scrambling code and the assigned slot format, regardless of the configured downlink compressed mode method information and of the transmission gap pattern sequence code information, if existing..
8.3.14.3	Abnormal Conditions
[FDD – If the concerned Node B Communication Context is not configured to use F-DPCH in the downlink and if a transmission gap pattern sequence is activated with an SF/2 downlink compressed mode method and for any Radio Link the transmission gap pattern sequence code information is not available, the Node B shall trigger the Radio Link Failure procedure with the cause value "Invalid CM Settings”.]
[FDD - If the COMPRESSED MODE COMMAND message contains the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE and the Transmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the Node B shall reject the procedure using the RADIO LINK FAILURE message with the cause value “Invalid CM settings”.]
8.3.15	Downlink Power Timeslot Control [TDD]
8.3.15.1	General
The purpose of this procedure is to enable the Node B to use the indicated DL Timeslot ISCP values when deciding the DL TX Power for each timeslot.
The Downlink Power Timeslot Control procedure can be initiated by the CRNC at any time when the Node B Communication Context exists, irrespective of other ongoing CRNC initiated dedicated NBAP procedures towards this Node B Communication Context. The only exception occurs when the CRNC has requested the deletion of the last RL via this Node B, in which case the Downlink Power Timeslot Control procedure shall no longer be initiated.
8.3.15.2	Successful Operation

Figure 47A: Downlink Power Timeslot Control procedure, Successful Operation
The procedure is initiated by the CRNC sending a DL POWER TIMESLOT CONTROL REQUEST message to the Node B using the Communication Control Port assigned to the concerned Node B Communication Context.
Upon reception, the Node B shall use the indicated DL Timeslot ISCP value when deciding the DL TX Power for each timeslot as specified in ref. TS 25.224 [21], i.e. it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged.
If the Primary CCPCH RSCP Delta IE is included, the Node B shall assume that the reported value for Primary CCPCH RSCP is in the negative range as per TS 25.123 [23], and the value is equal to the Primary CCPCH RSCP Delta IE. If the Primary CCPCH RSCP Delta IE is not included and the Primary CCPCH RSCP IE is included, the Node B shall assume that the reported value is in the non-negative range as per TS 25.123 [23], and the value is equal to the Primary CCPCH RSCP IE. The Node B should use the indicated value for HS-DSCH scheduling and transmit power adjustment.
8.3.15.3	Abnormal Conditions
-
8.3.16	Radio Link Pre-emption
8.3.16.1	General
This procedure is started by the Node B when resources need to be freed.
The Node B may initiate the Radio Link Pre-emption procedure at any time after establishing a Radio Link.
8.3.16.2	Successful Operation

Figure 47B: Radio Link Pre-emption procedure, Successful Operation
When the Node B detects that a one or more Radio Links should be pre-empted (see Annex A), it shall send the RADIO LINK PREEMPTION REQUIRED INDICATION message to the CRNC using the Communication Control Port assigned to the concerned Node B Communication Context.
If all Radio Links for a CRNC Communication Context ID should be pre-empted, the RL Information IE shall be omitted. If one or several but not all Radio Links should be pre-empted for a CRNC Communication Context, the Radio Links that should be pre-empted shall be indicated in the RL Information IE. The Radio Link(s) that should be pre-empted should be deleted by the CRNC.
8.3.16.3	Abnormal Conditions
-
8.3.17	Bearer Re-arrangement
8.3.17.1	General
This procedure is started by the Node B when Bearers for the Node B Communication Context need to be rearranged.
The Node B may initiate the Bearer Rearrangement procedure at any time after establishing a Radio Link.
8.3.17.2	Successful Operation


Figure 47C: Bearer Re-arrangement Indication, Successful Operation
When the Node B detects that a signaling bearer or a transport bearer or both need to be re-arranged for the Node B Communication Context, it shall send the BEARER REARRANGEMENT INDICATION message to the CRNC. The message shall use the Communication Control Port assigned for this Node B Communication Context.
If the signaling bearer for the control of the Node B Communication Context needs to be rearranged,  the Signalling Bearer Requested Indicator IE shall be included in the BEARER REARRANGEMENT INDICATION message.
If the transport bearer for a transport channel needs to be rearranged, the ID of the transport channel for which a new transport bearer is required, shall be included in the BEARER REARRANGEMENT INDICATION message. 
[FDD - If the separate Iub transportr bearer mode is used and the transport bearer for an E-DCH MAC-d flow needs to be rearranged, the Additional E-DCH Cell Information Bearer Rearrangement IE shall be included in the BEARER REARRANGEMENT INDICATION message.]
8.3.17.3	Abnormal Conditions
-
8.3.18	Radio Link Activation
8.3.18.1	General
This procedure is used to activate or de-activate the DL transmission on the Uu interface regarding selected RLs. 
8.3.18.2	Successful Operation


Figure 47D: Radio Link Activation procedure
This procedure is initiated by sending the RADIO LINK ACTIVATION COMMAND message from the CRNC to the Node B. The message shall use the Communication Control Port assigned for this Node B Communication Context. Upon reception, the Node B shall for each concerned RL:
-	if the Delayed Activation Update IE indicates "Activate":
-	if the Activation Type IE equals "Unsynchronised":
-	[FDD - start transmission on the new RL after synchronisation is achieved in the DL user plane as specified in TS 25.427 [16].]
-	[TDD - start transmission on the new RL immediately as specified in TS 25.427 [16].]
-	if the Activation Type IE equals "Synchronised":
-	[FDD - start transmission on the new RL after synchronisation is achieved in the DL user plane as specified in TS 25.427 [16], however never before the CFN indicated in the Activation CFN IE.]
-	[TDD - start transmission on the new RL at the CFN indicated in the Activation CFN IE as specified in TS 25.427 [16].]
-	[FDD - the Node B shall apply the power level indicated in the Initial DL Tx Power IE to the transmission on each DL DPCH or on the F-DPCH of the RL when starting transmission until either UL synchronisation on the Uu interface is achieved for the RLS or power balancing is activated. During this period no inner loop power control shall be performed and, unless activated by the DL POWER CONTROL REQUEST message, no power balancing shall be performed. The DL power shall then vary according to the inner loop power control (see ref. TS 25.214 [10], subclause 5.2.1.2) and downlink power balancing adjustments (see subclause 8.3.7).]
-	[TDD - the Node B shall apply the power level indicated in the Initial DL Tx Power IE to the transmission on each DL DPCH and on each Time Slot of the RL when starting transmission until the UL synchronisation on the Uu interface is achieved for the RL. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.133 [22], subclause 4.2.3.3).]
-	[FDD - if the Propagation Delay IE and optionally the Extended Propagation Delay IE are included, the Node B may use this information to speed up the detection of UL synchronisation on the Uu interface.]
-	[FDD - if the First RLS Indicator IE is included, it indicates if the concerned RL shall be considered part of the first RLS established towards this UE. The First RLS Indicator IE shall be used by the Node B together with the value of the DL TPC Pattern 01 Count IE which the Node B has received in the Cell Setup procedure, to determine the initial TPC pattern in the DL of the concerned RL and all RLs which are part of the same RLS, as described in TS 25.214 [10], section 5.1.2.2.1.2.]
-	if the Delayed Activation Update IE indicates "Deactivate":
-	stop DL transmission immediately, if the Deactivation Type IE equals "Unsynchronised", or at the CFN indicated by the Deactivation CFN IE, if the Deactivation Type IE equals "Synchronised".
8.3.18.3	Abnormal Conditions 
[FDD - If the Delayed Activation Update IE is included in the RADIO LINK ACTIVATION COMMAND message, it indicates "Activate" and the First RLS Indicator IE is not included, the Node B shall initiate the Error Indication procedure.]
8.3.19	Radio Link Parameter Update 
8.3.19.1	General
The Radio Link Parameter Update procedure is excuted by the Node B when the update of HS-DSCH [FDD - or E-DCH or UL CLTD] related radio link parameter values are needed on the Node B side. With this procedure, Node B can suggest some HS-DSCH [FDD - or E-DCH or UL CLTD] related Radio Link Parameter values to RNC.
The Radio Link Parameter Update procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.
8.3.19.2	Successful Operation

Figure 48: Radio Link Parameter Update Indication, Successful Operartion
The Node B initiates the Radio Link Parameter Update procedure by sending the RADIO LINK PARAMETER UPDATE INDICATION message to the CRNC. The message contains suggested value(s) of the HS-DSCH [FDD - or E-DCH] related parameter(s) that should be reconfigured on the radio link(s).
If the Node B needs to update HS-DSCH related parameters, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including [FDD - HS-DSCH FDD Update Information IE] [TDD - HS-DSCH TDD Update Information IE].
If the Node B needs to allocate new HS-SCCH Codes, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including HS-SCCH Code Change Indicator IE.
[FDD - If the Node B needs to allocate new HS-PDSCH Codes, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including HS-PDSCH Code Change Indicator IE.]
[FDD - If the Node B needs to update the CQI Feedback Cycle k, CQI Feedback Cycle2 k, CQI Cycle Switch Timer, CQI Repetition Factor, ACK-NACK Repetition Factor, CQI Power Offset, ACK Power Offset and/or NACK Power Offset, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including CQI Feedback Cycle k IE, CQI Repetition Factor IE, ACK-NACK Repetition Factor IE, CQI Power Offset IE, ACK Power Offset IE and/or NACK Power Offset IE.]
[FDD - If the Node B needs to update the Precoder weight set restriction, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including Precoder weight set restriction IE.]
[FDD - If the Node B needs to update Secondary Serving HS-DSCH related parameters, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including Additional HS Cell Information RL Param Upd IE.]
-	[FDD - If the Node B needs to allocate new secondary serving HS-SCCH Codes, the Node B shall include the HS-SCCH Code Change Indicator IE in the HS-DSCH FDD Secondary Serving Update Information IE.]
-	[FDD - If the Node B needs to update the Precoder weight set restriction, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including Precoder weight set restriction IE in the HS-DSCH FDD Secondary Serving Update Information IE.]
 [TDD - If the Node B needs to update the TDD ACK-NACK Power Offset the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including TDD ACK-NACK Power Offset IE.]
[FDD - If the Node B needs to update E-DCH related parameters, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including the E-DCH FDD Update Information IE.]
[FDD - If the Node B needs to update the HARQ process allocation for non-scheduled transmission and/or HARQ process allocation for scheduled Transmission, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE for the concerned MAC-d Flows and/or HARQ Process Allocation For 2ms Scheduled Transmission Grant IE.]
[FDD - If the Node B needs to allocate new E-AGCH Channelisation Code, new E-RGCH/E-HICH Channelisation Code, new E-RGCH Signature Sequence and/or new E-HICH Signature Sequence, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including E-DCH DL Control Channel Change Information IE.]
[FDD - If the Node B needs to indicate to RNC that the TTI switching has been triggered and confirmed by the UE, the Node B shall if supported initiate RADIO LINK PARAMETER UPDATE INDICATION message including the TTI Update Indication IE in the E-DCH FDD Update Information IE.]
[FDD - If the Node B needs to update Additional E-DCH related parameters, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including Additional E-DCH Cell Information RL Param Upd IE.]
-	[FDD - If the Node B needs to update the HARQ process allocation for scheduled Transmission, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE for the concerned MAC-d Flows.]
-	[FDD - If the Node B needs to allocate new E-AGCH Channelisation Code, new E-RGCH/E-HICH Channelisation Code, new E-RGCH Signature Sequence and/or new E-HICH Signature Sequence, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including Additional E-DCH DL Control Channel Change Information IE.]
[FDD - If the Node B needs to update the local activation state of UL CLTD of the UE in UL CLTD operation, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION including the UL CLTD State Update Information IE.]
[FDD – If the Node B needs to indicate that the CPC Recovery has been initiated, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including CPC Recovery Report IE.]
[FDD – If the Node B needs to forward the UE measurement, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including UE Measurement Forwarding IE.]
[FDD – If the Node B needs to perform the improved synchronized RRC procedures, the Node B shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including CFN IE.]
8.3.19.3	Abnormal Conditions
-
8.3.20	Secondary UL Frequency Reporting [FDD]
8.3.20.1	General
The purpose of this procedure is to inform the Node B about the activation state of the secondary UL frequency of the UE in Dual Cell E-DCH operation, or change the activation state of the secondary UL frequency of the UE in Dual Cell E-DCH operation when E-DCH decoupling is configured.
8.3.20.2	Successful Operation

Figure 48A: Secondary UL Frequency Reporting procedure
The Secondary UL Frequency Reporting procedure is initiated by sending the SECONDARY UL FREQUENCY REPORT message from the CRNC to the Node B. The message shall use the Communication Control Port assigned for this Node B Communication Context.
The Activation Information IE is included it defines the local activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation, or the change request of activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation when E-DCH decoupling is configured.
- 	If the value of Uu Activation State IE is "Activated": the Node B shall if supported use this information for resource allocation operation of the secondary E-DCH radio link(s), F-DPCH transmission and DPCCH detection.
- 	If the value of Uu Activation State IE is "De-Activated": the Node B shall if supported use this information for release of the related resources for the secondary E-DCH radio link(s), cease of F-DPCH transmission and DPCCH detection.
-	If the value of Uu Activation State IE is “Change Request”: the Node B shall if supported change the activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation when E-DCH decoupling is configured.
8.3.20.3	Abnormal Conditions
-
8.3.21	Secondary UL Frequency Update [FDD]
8.3.21.1	General
The purpose of this procedure is to inform the CRNC about updates to activation state of the secondary UL frequency of the UE in Dual Cell E-DCH operation or change the activation state of the secondary UL frequency of the UE in Dual Cell E-DCH operation when E-DCH decoupling is configured.
8.3.21.2	Successful Operation

Figure 48B: Secondary UL Frequency Update procedure
The Secondary UL Frequency Update procedure is initiated by the Node B by sending the SECONDARY UL FREQUENCY UPDATE INDICATION message to the CRNC. The message shall use the Communication Control Port assigned to the concerned Node B Communication Context.
If the Node B needs to update the local activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation, the Node B shall send SECONDARY UL FREQUENCY UPDATE INDICATION message and include the Activation Information IE.
8.3.21.3	Abnormal Conditions
-
8.4	Error Handling Procedures
8.4.1	Error Indication
8.4.1.1	General
The Error Indication procedure is initiated by a node in order to report detected errors in one incoming message, provided they cannot be reported by an appropriate response message.
8.4.1.2	Successful Operation
When the conditions defined in subclause 10 are fulfilled, the Error Indication procedure is initiated by an ERROR INDICATION message sent from the receiving node.
In case the Error Indication procedure was triggered by a dedicated procedure, the following applies:
-	When the ERROR INDICATION message is sent from a Node B to its CRNC, the CRNC Communication Context ID IE shall be included in the message if the corresponding Node B Communication Context, addressed by the Node B Communication Context ID IE which was received in the message triggering the Error Indication procedure, exists;
-	When the ERROR INDICATION message is sent from a CRNC to a Node B, the Node B Communication Context ID IE shall be included in the message if the corresponding CRNC Communication Context, addressed by the CRNC Communication Context ID IE which was received in the message triggering the Error Indication procedure, exists;
-	When the message triggering the Error Indication procedure is received in the Node B and there is no Node B Communication Context as indicated by the Node B Communication Context ID IE, the Node B shall include the unknown Node B Communication Context ID IE from the received message in the ERROR INDICATION message, unless another handling is specified in the procedure text for the affected procedure.
-	When the message triggering the Error Indication procedure is received in the CRNC and there is no CRNC Communication Context as indicated by the CRNC Communication Context ID IE, the CRNC shall include the unknown CRNC Communication Context ID IE from the received message in the ERROR INDICATION message, unless another handling is specified in the procedure text for the affected procedure.
The ERROR INDICATION message shall include either the Cause IE, or the Criticality Diagnostics IE or both the Cause IE and the Criticality Diagnostics IE.
Typical cause values for the ERROR INDICATION message are:
Protocol Causes:
-	Transfer Syntax Error
-	Abstract Syntax Error (Reject)
-	Abstract Syntax Error (Ignore and Notify)
-	Message not Compatible with Receiver State
-	Unspecified


Figure 49: Error Indication procedure (Node B to CRNC): Successful Operation

Figure 50: Error Indication procedure (CRNC to Node B), Successful Operation
8.4.1.3	Abnormal Conditions
-
9	Elements for NBAP communication
9.1	Message Functional Definition and Contents
9.1.1	General
Subclause 9.1 presents the contents of NBAP messages in tabular format. The corresponding ASN.1 definition is presented in subclause 9.3. In case there is contradiction between the tabular format in subclause 9.1 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, where the tabular format shall take precedence.
NOTE:	The messages have been defined in accordance to the guidelines specified in ref. TR 25.921 [26].
9.1.2	Message Contents
9.1.2.1	Presence
An information element can be of the following types:
M 
IEs marked as Mandatory (M) shall always be included in the message.
O 
IEs marked as Optional (O) may or may not be included in the message.
C
IEs marked as Conditional (C) shall be included in a message only if the condition is satisfied. Otherwise the IE shall not be included.

In case of an Information Element group, the group is preceded by a name for the info group (in bold). It is also indicated how many times a group may be repeated in the message and whether the group is conditional. The presence field of the Information Elements inside one group defines if the Information Element is mandatory, optional or conditional  if the group is present.
9.1.2.2	Criticality
Each Information Element or Group of Information Elements may have a criticality information applied to it. Following cases are possible:
–
No criticality information is applied explicitly.
YES
Criticality information is applied. ‘YES’ is usable only for non-repeatable information elements.
GLOBAL
The information element and all its repetitions together have one common criticality information. ‘GLOBAL’ is usable only for repeatable information elements.
EACH
Each repetition of the information element has its own criticality information. It is not allowed to assign different criticality values to the repetitions. ‘EACH’ is usable only for repeatable information elements.

9.1.2.3	Range
The Range column indicates the allowed number of copies of repetitive IEs.
9.1.2.4	Assigned Criticality
This column provides the actual criticality information as defined in subclause 10.3.2, if applicable.
9.1.3	COMMON TRANSPORT CHANNEL SETUP REQUEST
9.1.3.1	FDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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
Configuration Generation ID
M

9.2.1.16

YES
reject
CHOICE Common Physical Channel To Be Configured
M



YES
ignore
>Secondary CCPCH






>>Secondary CCPCH

1


–

>>>Common Physical Channel ID
M

9.2.1.13

–

>>>FDD SCCPCH Offset
M

9.2.2.15
Corresponds to TS 25.211 [7]: S-CCPCH,k 
–

>>>DL Scrambling Code
C-PCH

9.2.2.13
In case of BCH, ignore the IE.
–

>>>FDD DL Channelisation Code Number
M

9.2.2.14
In case of IMB using multiple channelization codes then this IE indicates the first one.
In case of BCH using 2 to 33.
–

>>>TFCS
M

9.2.1.58
For the DL. In case of BCH, refer to 25.331[18]
–

>>>Secondary CCPCH Slot Format
M

9.2.2.43
If Extended Secondary CCPCH Slot Format IE is present, this IE shall be ignored.
In case of BCH, ignore the IE.
–

>>>TFCI Presence
C-SlotFormat or 3.84Mcps TDD IMB

9.2.1.57
Refer to TS 25.211 [7].
In case of BCH, ignore the IE.
–

>>>Multiplexing Position
M

9.2.2.23

–

>>>Power Offset Information

1


–

>>>>PO1
M

Power Offset
9.2.2.29
Power offset for the TFCI bits
–

>>>>PO3
M

Power Offset
9.2.2.29
Power offset for the pilot bits
–

>>>STTD Indicator
M

9.2.2.48

–

>>>FACH Parameters

0..<maxNrOfFACHs>


GLOBAL
reject
>>>>Common Transport Channel ID
M

9.2.1.14

–

>>>>Transport Format Set
M

9.2.1.59
For the DL.
–

>>>>ToAWS
M

9.2.1.61

–

>>>>ToAWE
M

9.2.1.60

–

>>>>Max FACH Power
M

DL Power
9.2.1.21
Maximum allowed power on the FACH.
–

>>>>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP. 
YES
ignore
>>>>Broadcast Reference
O

9.2.1.5C

YES
ignore

>>>>IP Multicast Indication
O

9.2.1.108

YES
ignore
>>>PCH Parameters

0..1


YES
reject
>>>>Common Transport Channel ID
M

9.2.1.14

–

>>>>Transport Format Set
M

9.2.1.59
For the DL.
–

>>>>ToAWS
M

9.2.1.61

–

>>>>ToAWE
M

9.2.1.60

–

>>>>PCH Power
M

DL Power
9.2.1.21

–

>>>>PICH Parameters

1


–

>>>>>Common Physical Channel ID
M

9.2.1.13

–

>>>>>FDD DL Channelisation Code Number
M

9.2.2.14

–

>>>>>PICH Power
M

9.2.1.49A

–

>>>>>PICH Mode 
M

9.2.2.26
Number of PI per frame
–

>>>>>STTD Indicator
M

9.2.2.48

–

>>>>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP. 
YES
ignore
>>>MICH Parameters

0..1


YES
reject
>>>>Common Physical Channel ID
M

9.2.1.13

–

>>>>FDD DL Channelisation Code Number
M

9.2.2.14

–

>>>>MICH Power
M

PICH Power 9.2.1.49A

–

>>>>MICH Mode 
M

9.2.2.21D
Number of NI per frame
–

>>>>STTD Indicator
M

9.2.2.48

–

>>>FDD S-CCPCH Frame Offset
O

9.2.2.14B

YES
reject
>>>Modulation Power Offset
O

9.2.2.91
Used for MBSFN operation and 3.84Mcps TDD MBSFN IMB operation only
YES
reject
>>>Extended Secondary CCPCH Slot Format
O

9.2.2.92
Used for MBSFN operation only
YES
reject
>>>IMB Parameters
O

9.2.2.115
Used for 3.84Mcps TDD MBSFN IMB operation only
YES
reject
>>>BCH Parameters

0..1


YES
ignore
>>>>Common Transport Channel ID
M

9.2.1.14

–

>>>>BCH Power
M

DL Power
9.2.1.21
Maximum allowed power on the BCH.
–

>PRACH






>>PRACH

1


–

>>>Common Physical Channel ID
M

9.2.1.13

–

>>>Scrambling Code Number
M

9.2.2.42

–

>>>TFCS
M

9.2.1.58
For the UL.
–

>>>Preamble Signatures
M

9.2.2.31

–

>>>Allowed Slot Format Information

1..<maxNrOfSlotFormatsPRACH>


–

>>>>RACH Slot Format
M

9.2.2.37

–

>>>RACH Sub Channel Numbers
M

9.2.2.38

–

>>>Puncture Limit
M

9.2.1.50
For the UL
–

>>>Preamble Threshold
M

9.2.2.32

–

>>>RACH Parameters

1


YES
reject
>>>>Common Transport Channel ID
M

9.2.1.14

–

>>>>Transport Format Set
M

9.2.1.59
For the UL.
–

>>>>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP. 
YES
ignore
>>>AICH Parameters

1


–

>>>>Common Physical Channel ID
M

9.2.1.13

–

>>>>AICH Transmission Timing
M

9.2.2.1

–

>>>>FDD DL Channelisation Code Number
M

9.2.2.14

–

>>>>AICH Power
M

9.2.2.D

–

>>>>STTD Indicator
M

9.2.2.48

–

>Not Used


NULL
This choice shall not be used. Reject procedure if received.



Condition
Explanation
SlotFormat or 3.84Mcps TDD IMB
The IE shall be present if the Secondary CCPCH Slot Format IE is set to any of the values from 8 to 17 or if the IMB Parameters IE is included.
PCH
The IE shall be present if the PCH Parameters IE is not present.

Range Bound
Explanation
maxNrOfFACHs
Maximum number of FACHs that can be defined on a Secondary CCPCH
maxNrOfSlotFormatsPRACH
Maximum number of SF for a PRACH

9.1.3.2	TDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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
Configuration Generation ID
M

9.2.1.16

YES
reject
CHOICE Common Physical Channel To Be Configured
M



YES
ignore
>Secondary CCPCHs






>>SCCPCH CCTrCH ID
M

CCTrCH ID
9.2.3.3
For DL CCTrCH supporting one or several Secondary CCPCHs
–

>>TFCS
M

9.2.1.58
For DL CCTrCH supporting one or several Secondary CCPCHs
–

>>TFCI Coding
M

9.2.3.22

–

>>Puncture Limit
M

9.2.1.50

–

>>CHOICE HCR or LCR or 7.68 Mcps
M


See note 1 below
–

>>>3.84Mcps TDD




–

>>>>Secondary CCPCH

1..<maxNrOfSCCPCHs>

See note 2 below
GLOBAL
reject
>>>>>Common Physical Channel ID
M

9.2.1.13

–

>>>>>TDD Channelisation Code 
M

9.2.3.19

–

>>>>>Time Slot
M

9.2.3.23

–

>>>>>Midamble Shift And Burst Type
M

9.2.3.7

–

>>>>>TDD Physical Channel Offset
M

9.2.3.20

–

>>>>>Repetition Period
M

9.2.3.16

–

>>>>>Repetition Length
M

9.2.3.15

–

>>>>>SCCPCH Power
M

DL Power
9.2.1.21

–

>>>>>TFCI Presence
O

9.2.1.57

YES
notify
>>>1.28Mcps TDD




–

>>>>Secondary CCPCH LCR

1..<maxNrOfSCCPCHLCRs>

See note 2 below
GLOBAL
reject
>>>>>Common Physical Channel ID
M

9.2.1.13

–

>>>>>TDD Channelisation Code LCR 
M

9.2.3.19a

–

>>>>>Time Slot LCR
M

9.2.3.24A

–

>>>>>Midamble Shift LCR
M

9.2.3.7A
For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, the Node B shall ignore the contents of this IE.
–

>>>>>TDD Physical Channel Offset
M

9.2.3.20

–

>>>>>Repetition Period
M

9.2.3.16

–

>>>>>Repetition Length
M

9.2.3.15

–

>>>>>SCCPCH Power
M

DL Power
9.2.1.21

–

>>>>>SCCPCH Time Slot Format LCR
M

TDD DL DPCH Time Slot Format LCR 9.2.3.19D

–

>>>>>MBSFN Special Time Slot LCR
O

Time Slot LCR Extension
9.2.3.24B
Only for 1.28 Mcps TDD MBSFN only mode, this IE indicates the MBSFN Special Time Slot (TS 25.221 [19]). The Time Slot LCR IE for the Secondary CCPCH LCR shall be ignored if this IE appears.
YES
ignore
>>>7.68 Mcps TDD




–

>>>>Secondary CCPCH 7.68 Mcps

1..<maxNrOfSCCPCHs768>


GLOBAL
reject
>>>>>Common Physical Channel ID 7.68Mcps 
M

9.2.3.33

–

>>>>>TDD Channelisation Code 7.68Mcps 
M

9.2.3.34

–

>>>>>Time Slot
M

9.2.3.23

–

>>>>>TFCI Presence
O

9.2.1.57

–

>>>>>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>>>>>TDD Physical Channel Offset
M

9.2.3.20

–

>>>>>Repetition Period
M

9.2.3.16

–

>>>>>Repetition Length
M

9.2.3.15

–

>>>>>SCCPCH Power
M

DL Power
9.2.1.21

–

>>FACH Parameters

0..<maxNrOfFACHs>


GLOBAL
reject
>>>Common Transport Channel ID
M

9.2.1.14

–

>>>FACH CCTrCH ID
M

CCTrCH ID
9.2.3.3

–

>>>Transport Format Set
M

9.2.1.59
For the DL.
–

>>>ToAWS
M

9.2.1.61

–

>>>ToAWE
M

9.2.1.60

–

>>>Max FACH Power
O

DL Power 
9.2.1.21
Applicable to 1.28Mcps TDD only
YES
reject
>>>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP. 
YES
ignore
>>>Broadcast Reference
O

9.2.1.5C

YES
ignore
>>>IP Multicast Indication
O

9.2.1.108

   YES
  ignore
>>PCH Parameters

0..1


YES
reject
>>>Common Transport Channel ID
M

9.2.1.14

–

>>>PCH CCTrCH ID
M

CCTrCH ID
9.2.3.3

–

>>>Transport Format Set
M

9.2.1.59
For the DL.
–

>>>ToAWS
M

9.2.1.61

–

>>>ToAWE
M

9.2.1.60

–

>>>CHOICE HCR or LCR or 7.68Mcps
M


See note 1 below
–

>>>>3.84Mcps TDD




–

>>>>>PICH Parameters

0..1


YES
reject
>>>>>>Common Physical Channel ID
M

9.2.1.13

–

>>>>>>TDD Channelisation Code
M

9.2.3.19

–

>>>>>>Time Slot
M

9.2.3.23

–

>>>>>>Midamble Shift And Burst Type
M

9.2.3.7

–

>>>>>>TDD Physical Channel Offset
M

9.2.3.20

–

>>>>>>Repetition Period
M

9.2.3.16

–

>>>>>>Repetition Length
M

9.2.3.15

–

>>>>>>Paging Indicator Length
M

9.2.3.8

–

>>>>>>PICH Power
M

9.2.1.49A

–

>>>>1.28Mcps TDD




–

>>>>>PICH Parameters LCR

0..1


YES
reject
>>>>>>Common Physical Channel ID
M

9.2.1.13

–

>>>>>>TDD Channelisation Code LCR
M

9.2.3.19a

–

>>>>>>Time Slot LCR
M

9.2.3.24A

–

>>>>>>Midamble Shift LCR
M

9.2.3.7A

–

>>>>>>TDD Physical Channel Offset
M

9.2.3.20

–

>>>>>>Repetition Period
M

9.2.3.16

–

>>>>>>Repetition Length
M

9.2.3.15

–

>>>>>>Paging Indicator Length
M

9.2.3.8

–

>>>>>>PICH Power
M

9.2.1.49A

–

>>>>>>Second TDD Channelisation Code LCR
M

TDD Channelisation Code LCR 9.2.3.19a

–

>>>>>>TSTD Indicator
O

9.2.1.64

YES
reject
>>>>7.68Mcps TDD




–

>>>>>PICH Parameters

0..1


YES
reject
>>>>>Common Physical Channel ID 7.68Mcps 
M

9.2.3.33

–

>>>>>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

>>>>>>Time Slot
M

9.2.3.23

–

>>>>>>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>>>>>>TDD Physical Channel Offset
M

9.2.3.20

–

>>>>>>Repetition Period
M

9.2.3.16

–

>>>>>>Repetition Length
M

9.2.3.15

–

>>>>>>Paging Indicator Length
M

9.2.3.8

–

>>>>>>PICH Power
M

9.2.1.49A

–

>>>PCH Power
O

DL Power 9.2.1.21
Applicable to 1.28Mcps TDD only
YES
reject
>>>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP. 
YES
ignore
>>TSTD Indicator
O

9.2.1.64

YES
reject
>>MICH Parameters

0..1


YES
reject
>>>Common Physical Channel ID
M

9.2.1.13

–

>>>TDD Physical Channel Offset
M

9.2.3.20

–

>>>Repetition Period
M

9.2.3.16

–

>>>Repetition Length
M

9.2.3.15

–

>>>Notification Indicator Length
M

9.2.3.7Aa

–

>>>MICH Power
M

PICH Power 9.2.1.49A

–

>>>CHOICE HCR or LCR or 7.68 Mcps
M



–

>>>>3.84Mcps TDD






>>>>>MICH Parameters HCR

1


–

>>>>>>TDD Channelisation Code
M

9.2.3.19

–

>>>>>>Time Slot
M

9.2.3.23

–

>>>>>>Midamble Shift And Burst Type
M

9.2.3.7

–

>>>>1.28Mcps TDD






>>>>>MICH Parameters LCR

1


–

>>>>>>TDD Channelisation Code LCR
M

9.2.3.19a

–

>>>>>>Time Slot LCR
M

9.2.3.24A

–

>>>>>>Midamble Shift LCR
M

9.2.3.7A
For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, the Node B shall ignore the contents of this IE.
–

>>>>>>Second TDD Channelisation Code LCR
M

TDD Channelisation Code LCR 9.2.3.19a

–

>>>>>>TSTD Indicator
M

9.2.1.64

–

>>>>>>MBSFN Special Time Slot LCR
O

Time Slot LCR Extension 9.2.3.24B
Only for 1.28 Mcps TDD MBSFN only mode, this IE indicates the MBSFN Special Time Slot (TS 25.221 [19]). The Time Slot LCR IE for the MICH parameters LCR shall be ignored if this IE appears.
YES
ignore
>>>>7.68 Mcps TDD






>>>>>MICH Parameters 7.68 Mcps

1


–

>>>>>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

>>>>>>Time Slot
M

9.2.3.23

–

>>>>>>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>>Modulation
O

9.2.1.87
Applicable to 3.84Mcps TDD and 7.68Mcps TDD in MBSFN operation only
YES
reject
>>Time Slot Configuration LCR

0..7

Applicable to 1.28Mcps TDD for MBSFN. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
GLOBAL
reject
>>>Time Slot LCR
M

9.2.3.24A

–

>>>Time Slot Parameter ID
M

Cell Parameter ID
9.2.3.4

–

>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
This IE indicates the frequency of the Secondary Frequency on which SCCPCH is configured. 
Applicable to 1.28Mcps TDD MBSFN. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
reject
>PRACH






>>CHOICE HCR or LCR or 7.68 Mcps
M


See note 1 below
–

>>>3.84Mcps TDD




–

>>>>PRACH

1


YES
reject
>>>>>Common Physical Channel ID
M

9.2.1.13

–

>>>>>TFCS
M

9.2.1.58

–

>>>>>Time Slot
M

9.2.3.23

–

>>>>>TDD Channelisation Code 
M

9.2.3.19

–

>>>>>Max PRACH Midamble Shift
M

9.2.3.6

–

>>>>>PRACH Midamble 
M

9.2.3.14

–

>>>>>RACH

1


YES
reject
>>>>>>Common Transport Channel ID
M

9.2.1.14

–

>>>>>>Transport Format Set
M

9.2.1.59
For the UL
–

>>>>>>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>>>>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>>>>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP. 
YES
ignore
>>>1.28Mcps TDD




–

>>>>PRACH LCR

1..<maxNrOfPRACHLCRs>


GLOBAL
reject
>>>>>Common Physical Channel ID
M

9.2.1.13

–

>>>>>TFCS
M

9.2.1.58

–

>>>>>Time Slot LCR
M

9.2.3.24A

–

>>>>>TDD Channelisation Code LCR
M

9.2.3.19a

–

>>>>>Midamble Shift LCR
M

9.2.3.7A

–

>>>>>RACH

1


YES
reject
>>>>>>Common Transport Channel ID
M

9.2.1.14

–

>>>>>>Transport Format Set
M

9.2.1.59
For the UL
–

>>>>>>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>>>>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>>>>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP. 
YES
ignore
>>>>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
This IE indicates the frequency of the secondary frequency on which PRACH to be set up.
See note 3 below. 
YES
reject
>>>7.68 Mcps TDD




–

>>>>PRACH

1


YES
reject
>>>>>Common Physical Channel ID 7.68Mcps 
M

9.2.3.33

–

>>>>>TFCS
M

9.2.1.58

–

>>>>>Time Slot
M

9.2.3.23

–

>>>>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

>>>>>Max PRACH Midamble Shift
M

9.2.3.6

–

>>>>>PRACH Midamble 
M

9.2.3.14

–

>>>>>RACH

1


YES
reject
>>>>>>Common Transport Channel ID
M

9.2.1.14

–

>>>>>>Transport Format Set
M

9.2.1.59
For the UL
–

>>>>>>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>>>>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>>>>>>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP. 
YES
ignore
>>FPACH

0..1

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
reject
>>>Common Physical Channel ID
M

9.2.1.13

–

>>>TDD Channelisation Code LCR
M

9.2.3.19a

–

>>>Time Slot LCR
M

9.2.3.24A

–

>>>Midamble Shift LCR
M

9.2.3.7A

–

>>>Max FPACH Power
M

9.2.3.5E

–

>>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]). 
This IE indicates the frequency of Secondary Frequency on which FPACH to be set up.
YES
reject
>PLCCH



1.28 Mcps TDD only
YES
ignore
>>Max PLCCH Power
M

DL Power 
9.2.1.21

–

>>Common Physical Channel ID
M

9.2.1.13

–

>>TDD Channelisation Code
M

9.2.3.19

–

>>Time Slot LCR
M

9.2.3.24A

–

>>Midamble Shift LCR
M

9.2.3.7A

–

>E-RUCCH



3.84Mcps TDD only
YES
ignore
>>Common Physical Channel ID
M

9.2.1.13

–

>>Time Slot
M

9.2.3.23

–

>>TDD Channelisation Code 
M

9.2.3.19

–

>>Max E-RUCCH Midamble Shift
M

9.2.3.44

–

>>E-RUCCH Midamble 
M

PRACH Midamble
9.2.3.14

–

>E-RUCCH 7.68Mcps



7.68Mcps TDD only
YES
ignore
>>Common Physical Channel ID 7.68Mcps
M

9.2.3.33

–

>>Time Slot
M

9.2.3.23

–

>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

>>Max E-RUCCH Midamble Shift
M

9.2.3.44

–

>>E-RUCCH Midamble 
M

PRACH Midamble
9.2.3.14

–

NOTE 1:	This information element is a simplified representation of the ASN.1. The choice is in reality performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1.
NOTE 2:	This information element is a simplified representation of the ASN.1. Repetitions 1 to 8 and repetitions 9 to maxNrOfSCCPCHs / maxNrOfSCCPCHLCRs are represented by separate ASN.1 structures.
NOTE 3:	The configured PRACH resources on secondary frequency shall only be used for E-DCH random access.


Range Bound
Explanation
maxNrOfSCCPCHs
Maximum number of Secondary CCPCHs per CCTrCH for 3.84Mcps TDD
maxNrOfSCCPCHLCRs
Maximum number of Secondary CCPCHs per CCTrCH for 1.28Mcps TDD
maxNrOfSCCPCHs768
Maximum number of Secondary CCPCHs per CCTrCH for 7.68 Mcps TDD
maxNrOfFACHs
Maximum number of FACHs that can be defined on a Secondary CCPCH
maxNrOfPRACHLCRs
Maximum number of PRACHs LCR that can be defined on a RACH for 1.28Mcps TDD

9.1.4	COMMON TRANSPORT CHANNEL SETUP RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

FACH Parameters Info

0..<maxNrOfFACHs>

The FACH Parameters may be combined with PCH Parameters
GLOBAL
ignore
>FACH Parameters
M

Common Transport Channel Information Response 9.2.1.14A

–

PCH Parameters
O

Common Transport Channel Information Response 9.2.1.14A
The PCH Parameters may be combined with FACH Parameters
YES
ignore
RACH Parameters
O

Common Transport Channel Information Response 9.2.1.14A
The RACH Parameters shall not be combined with FACH Parameters or PCH Parameters
YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore
BCH Parameters
O

Common Transport Channel Information Response 9.2.1.14A

YES
ignore

Range Bound
Explanation
maxNrOfFACHs
Maximum number of FACHs that can be defined on a Secondary CCPCH[FDD] / a group of Secondary CCPCHs [TDD]

9.1.5	COMMON TRANSPORT CHANNEL SETUP FAILURE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–
–
Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–
–
Cause
M

9.2.1.6

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.6	COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST
9.1.6.1	FDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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
Configuration Generation ID
M

9.2.1.16

YES
reject
CHOICE Common Physical Channel To Be Configured
M



YES
reject
>Secondary CCPCH






>>FACH Parameters

0..<maxFACHCell>


GLOBAL
reject
>>>Common Transport Channel ID
M

9.2.1.14

–

>>>Max FACH Power
O

DL Power
9.2.1.21
Maximum allowed power on the FACH.
–

>>>ToAWS
O

9.2.1.61

–

>>>ToAWE
O

9.2.1.60

–

>>>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer reconfiguration with ALCAP. 
YES
ignore
>>PCH Parameters

0..1


YES
reject
>>>Common Transport Channel ID
M

9.2.1.14

–

>>>PCH Power
O

DL Power
9.2.1.21
Power to be used on the PCH.
–

>>>ToAWS
O

9.2.1.61

–

>>>ToAWE
O

9.2.1.60

–

>>>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer reconfiguration with ALCAP. 
YES
ignore
>>PICH Parameters

0..1


YES
reject
>>>Common Physical Channel ID
M

9.2.1.13

–

>>>PICH Power
O

9.2.1.49A

–

>>MICH Parameters

0..1


YES
reject
>>>Common Physical Channel ID
M

9.2.1.13

–

>>>MICH Power
O

PICH Power 9.2.1.49A

–

>>BCH Parameters

0..1


YES
ignore
>>>Common Transport Channel ID
M

9.2.1.14

–

>>>BCH Power
O

DL Power
9.2.1.21
Power to be used on the BCH
–

>PRACH






>>PRACH Parameters

0..<maxPRACHCell>


GLOBAL
reject
>>>Common Physical Channel ID
M

9.2.1.13

–

>>>Preamble Signatures
O

9.2.2.31

–

>>>Allowed Slot Format Information

0..<maxNrOfSlotFormatsPRACH>


–

>>>>RACH Slot Format
M

9.2.2.37

–

>>>RACH Sub Channel Numbers
O

9.2.2.38

–

>>>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer reconfiguration with ALCAP.
YES
ignore
>>AICH Parameters

0..<maxPRACHCell>


GLOBAL
reject
>>>Common Physical Channel ID
M

9.2.1.13

–

>>>AICH Power
O

9.2.2.D

–

>Not Used


NULL
This choice shall not be used. Reject procedure if received.



Range Bound
Explanation
maxFACHCell
Maximum number of FACHs that can be defined in a Cell
maxPRACHCell
Maximum number of PRACHs and AICHs that can be defined in a Cell
maxNrOfSlotFormatsPRACH
Maximum number of SF for a PRACH

9.1.6.2	TDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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
Configuration Generation ID
M

9.2.1.16

YES
reject
Secondary CCPCH Parameters

0..1


YES
reject
>CCTrCH ID
M

9.2.3.3
For DL CCTrCH supporting one or several Secondary CCPCHs
–

>Secondary CCPCHs To Be Configured

0..<maxNrOfSCCPCHs>

See note 1 below
GLOBAL
reject
>>Common Physical Channel ID
M

9.2.1.13

–

>>SCCPCH Power
O

DL power
9.2.1.21

–

PICH Parameters

0..1


YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>PICH Power
O

9.2.1.49A

–

FACH Parameters

0..<maxNrOfFACHs>


GLOBAL
reject
>Common Transport Channel ID
M

9.2.1.14

–

>ToAWS
O

9.2.1.61

–

>ToAWE
O

9.2.1.60



>Max FACH Power
O

DL Power
9.2.1.21
Applicable to 1.28Mcps TDD only
YES
reject
>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer reconfiguration with ALCAP.
YES
ignore
PCH Parameters

0..1


YES
reject
>Common Transport Channel ID
M

9.2.1.14

–

>ToAWS
O

9.2.1.61

–

>ToAWE
O

9.2.1.60

–

>PCH Power
O

DL Power
9.2.1.21
Applicable to 1.28Mcps TDD only
YES
reject
>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer reconfiguration with ALCAP.
YES
ignore
FPACH Parameters

0..1

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD..
YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>Max FPACH Power
O

9.2.3.5E

–

MICH Parameters

0..1


YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>MICH Power
O

PICH Power 9.2.1.49A

–

PLCCH Parameters

0..1

Applicable to 1.28Mcps TDD only
YES
ignore
>Max PLCCH Power
O

DL Power
9.2.1.21

–

Secondary CCPCH Parameters 7.68Mcps

0..1

Applicable to 7.68 Mcps TDD only
YES
reject
>CCTrCH ID
M

9.2.3.3
For DL CCTrCH supporting one or several Secondary CCPCHs
–

>Secondary CCPCHs To Be Configured

0..<maxNrOfSCCPCHs768>


–

>>Common Physical Channel ID 7.68Mcps
M

9.2.3.33

–

>>SCCPCH Power
O

DL power
9.2.1.21

–

PICH Parameters 7.68Mcps

0..1

Applicable to 7.68 Mcps TDD only
YES
reject
>Common Physical Channel ID 7.68Mcps
M

9.2.3.33

–

>PICH Power
O

9.2.1.49A

–

MICH Parameters 7.68Mcps

0..1

Applicable to 7.68Mcps TDD only
YES
reject
>Common Physical Channel ID 7.68Mcps
M

9.2.3.33

–

>MICH Power
O

PICH Power 9.2.1.49A

–

UpPCH Parameters

0..1

Applicable to 1.28Mcps TDD only
YES
reject
>UpPCH Position LCR
O

9.2.3.4Q
This position of UpPCH. For a multi-frequency cell, if this IE is not included in this message, UpPCH in secondary frequency indicated by "UARFCN" shall be deleted.
–

>UARFCN
O

9.2.1.65
Mandatory for 1.28Mcps TDD when using multiple frequencies. Corresponds to Nt (TS 25.105 [15]).
–

NOTE 1:	This information element is a simplified representation of the ASN.1. Repetitions 1 to 8 and repetitions 9 to maxNrOfSCCPCHs are represented by separate ASN.1 structures. Furthermore, maxNrOfSCCPCHs has different values in the ASN.1 for each of the two TDD options.

Range Bound
Explanation
maxNrOfSCCPCHs
Maximum number of SCCPCHs that can be repeated in a Cell
maxNrOfFACHs
Maximum number of FACHs that can be repeated in a Cell
maxNrOfSCCPCHs768
Maximum number of SCCPCHs that can be repeated in a Cell at 7.68Mcps

9.1.7	COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.8	COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Cause
M

9.2.1.6

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.9	COMMON TRANSPORT CHANNEL DELETION REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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
Common Physical Channel ID
M

9.2.1.13
Indicates the Common Physical Channel for which the Common Transport Channels (together with the Common Physical Channel) shall be deleted.
YES
reject
Configuration Generation ID
M

9.2.1.16

YES
reject
Common Physical Channel ID 7.68Mcps
O

9.2.3.33
Included at 7.68 Mcps when the physical channel ID exceeds the range of " Common Physical Channel ID" 
YES
reject

9.1.10	COMMON TRANSPORT CHANNEL DELETION RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.11	BLOCK RESOURCE REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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
Blocking Priority Indicator
M

9.2.1.5

YES
reject
Shutdown Timer
C-BlockNormal

9.2.1.56

YES
reject

Condition
Explanation
BlockNormal
The IE shall be present if the Blocking Priority Indicator IE indicates "Normal Priority".

9.1.12	BLOCK RESOURCE RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.13	BLOCK RESOURCE FAILURE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Cause
M

9.2.1.6

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.14	UNBLOCK RESOURCE INDICATION
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

C-ID
M

9.2.1.9

YES
ignore

9.1.15	AUDIT REQUIRED INDICATION
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–


9.1.16	AUDIT REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Start Of Audit Sequence Indicator
M

9.2.1.56B

YES
reject

9.1.17	AUDIT RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

End Of Audit Sequence Indicator
M

9.2.1.29A

YES
ignore
Cell Information

0..<maxCellinNodeB>


EACH
ignore
>C-ID
M

9.2.1.9

–

>Configuration Generation ID
M

9.2.1.16

–

>Resource Operational State
M

9.2.1.52

–

>Availability Status
M

9.2.1.2

–

>Local Cell ID
M

9.2.1.38
The local cell that the cell is configured on
–

>Primary SCH Information
O

Common Physical Channel Status Information 9.2.1.13A
Applicable to FDD only
YES
ignore
>Secondary SCH Information
O

Common Physical Channel Status Information 9.2.1.13A
Applicable to FDD only
YES
ignore
>Primary CPICH Information
O

Common Physical Channel Status Information 9.2.1.13A
Applicable to FDD only
YES
ignore
>Secondary CPICH Information

0..<maxSCPICHCell>

Applicable to FDD only
EACH
ignore
>>Secondary CPICH Individual Information
M

Common Physical Channel Status Information 9.2.1.13A

–

>Primary CCPCH Information
O

Common Physical Channel Status Information 9.2.1.13A

YES
ignore
>BCH Information
O

Common Transport Channel Status Information 9.2.1.14B

YES
ignore
>Secondary CCPCH Information

0..<maxSCCPCHCell>

See note 1 below
EACH
ignore
>>Secondary CCPCH Individual Information
M

Common Physical Channel Status Information 9.2.1.13A

–

>PCH Information
O

Common Transport Channel Status Information 9.2.1.14B

YES
ignore
>PICH Information
O

Common Physical Channel Status Information 9.2.1.13A

YES
ignore
>FACH Information

0..<maxFACHCell>


EACH
ignore
>>FACH Individual Information
M

Common Transport Channel Status Information 9.2.1.14B

–

>PRACH Information

0..<maxPRACHCell>


EACH
ignore
>>PRACH Individual Information 
M

Common Physical Channel Status Information 9.2.1.13A

–

>RACH Information

0..<maxRACHCell> 


EACH
ignore
>>RACH Individual Information 
M

Common Transport Channel Status Information 9.2.1.14B

–

>AICH Information

0..<maxPRACHCell>

Applicable to FDD only
EACH
ignore
>>AICH Individual Information 
M

Common Physical Channel Status Information 9.2.1.13A

–

>Not Used 1
O

NULL
This item shall not be used. Ignore if received.
–

>Not Used 2
O

NULL
This item shall not be used. Ignore if received. 
–

>Not Used 3
O
 
NULL
This item shall not be used. Ignore if received. 
–

>Not Used 4
O
 
NULL
This item shall not be used. Ignore if received. 
–

>SCH Information
O

Common Physical Channel Status Information 9.2.1.13A
TDD Sync Channel
Applicable to 3.84Mcps TDD only
YES
ignore
>FPACH Information

0..<maxFPACHCell>

Applicable to 1.28Mcps TDD only
EACH
ignore
>>FPACH Individual lnformation
M

Common Physical Channel Status Information 9.2.1.13A

–

>DwPCH Information
O

Common Physical Channel Status Information 9.2.1.13A
Applicable to 1.28Mcps TDD only
YES
ignore
>HS-DSCH Resources Information

0..<maxFrequencyinCell>

See note 2 below
EACH
ignore
>>Resource Operational State
M

9.2.1.52

–

>>Availability Status
M

9.2.1.2

–

>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Applicable to 1.28Mcps TDD when using multiple frequencies.
YES
ignore
>MICH Information
O

Common Physical Channel Status Information 9.2.1.13A

YES
ignore
>E-DCH Resources Information

0..<maxFrequencyinCell>

See note 2 below
EACH
ignore
>>Resource Operational State
M

9.2.1.52

–

>>Availability Status
M

9.2.1.2

–

>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Applicable to 1.28Mcps TDD when using multiple frequencies.
YES
ignore
>PLCCH Information

0..<maxPLCCHCell>

Applicable to 1.28Mcps TDD only
EACH
ignore
>>PLCCH Individual lnformation
M

Common Physical Channel Status Information 9.2.1.13A

–

>Primary CCPCH Information 7.68Mcps
O

Common Physical Channel Status Information 7.68 Mcps 9.2.3.36

YES
ignore
>Secondary CCPCH Information 7.68Mcps

0..<maxSCCPCHCell768>


EACH
ignore
>>Secondary CCPCH Individual Information 7.68 Mcps
M

Common Physical Channel Status Information 7.68 Mcps 9.2.3.36

–

>PICH Information 7.68Mcps
O

Common Physical Channel Status Information 7.68 Mcps 9.2.3.36

YES
ignore
>PRACH Information 7.68Mcps

0..<maxPRACHCell>


EACH
ignore
>>PRACH Individual Information 7.68Mcps 
M

Common Physical Channel Status Information 7.68 Mcps 9.2.3.36

–

>SCH Information 7.68Mcps
O

Common Physical Channel Status Information 7.68 Mcps 9.2.3.36
TDD Sync Channel
Applicable to 7.68Mcps TDD only
YES
ignore
>MICH Information 7.68Mcps
O

Common Physical Channel Status Information 7.68 Mcps 9.2.3.36

YES
ignore
>E-RUCCH Information

0..<maxE-RUCCHCell>

3.84Mcps TDD only
EACH
ignore
>>E-RUCCH Individual Information 
M

Common Physical Channel Status Information 9.2.1.13A

–

>E-RUCCH Information 7.68Mcps

0..<maxE-RUCCHCell>

7.68Mcps TDD only
EACH
ignore
>>E-RUCCH Individual Information 7.68Mcps
M

Common Physical Channel Status Information 7.68 Mcps 9.2.3.36

–

>UARFCN Information LCR

0..<maxFrequencyinCell>

Applicable to 1.28Mcps TDD when using multiple frequencies.
EACH
ignore
>>UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
–

>>Resource Operational State
M

9.2.1.52

–

>>Availability Status
M

9.2.1.2

–

>UpPCH Information LCR

0..<maxFrequencyinCell>

Applicable to 1.28Mcps TDD only.
EACH
ignore
>>UARFCN
O

9.2.1.65
Mandatory for 1.28Mcps TDD when using multiple frequencies. Corresponds to Nt (TS 25.105 [15]).
–

>>UpPCH Position LCR
M

9.2.3.4Q

–

>>Resource Operational State
M

9.2.1.52

–

>>Availability Status
M

9.2.1.2

–

Communication Control Port Information

0..<maxCCPinNodeB>


EACH
ignore
>Communication Control Port ID
M

9.2.1.15

–

>Resource Operational State
M

9.2.1.52

–

>Availability Status
M

9.2.1.2

–

Local Cell Information

0..<maxLocalCellinNodeB>


EACH
ignore
>Local Cell ID
M

9.2.1.38

–

>DL Or Global Capacity Credit
M

9.2.1.20B

–

>UL Capacity Credit
O

9.2.1.65A

–

>Common Channels Capacity Consumption Law
M

9.2.1.9A

–

>Dedicated Channels Capacity Consumption Law
M

9.2.1.20A

–

>Maximum DL Power Capability
O

9.2.1.39

–

>Minimum Spreading Factor
O

9.2.1.47

–

>Minimum DL Power Capability
O

9.2.1.46A

–

>Local Cell Group ID
O

9.2.1.37A

–

>Reference Clock Availability
O

9.2.3.14A
TDD only
YES
ignore
>Power Local Cell Group ID
O

9.2.1.49B

YES
ignore
>HSDPA Capability
O

9.2.1.31Ga

YES
ignore
>E-DCH Capability
O

9.2.1.70

YES
ignore
>E-DCH TTI2ms Capability
C-EDCHCapability

9.2.2.13V
FDD only
YES
ignore
>E-DCH SF Capability
C-EDCHCapability

9.2.2.13W
FDD only
YES
ignore
>E-DCH HARQ Combining Capability
C-EDCHCapability

9.2.2.13X
FDD only
YES
ignore
>E-DCH Capacity Consumption Law
O

9.2.2.13Ja
FDD only
YES
ignore
>F-DPCH Capability
O

9.2.2.16a
FDD only
YES
ignore
>E-DCH TDD Capacity Consumption Law
O

9.2.3.60
TDD only
YES
ignore
>Continuous Packet Connectivity DTX-DRX Capability
O

9.2.2.64
FDD only
YES
ignore
>Max UE DTX Cycle
C-DTX-DRXCapability

9.2.2.95
FDD only
YES
ignore
>Continuous Packet Connectivity HS-SCCH less Capability
O

9.2.2.65
FDD only
YES
ignore
>MIMO Capability
O

9.2.1.118
FDD and 1.28Mcps TDD only
YES
ignore
>SixtyfourQAM DL Capability
O

9.2.1.110
FDD and 1.28Mcps TDD only
YES
ignore
>MBMS Capability
O

9.2.1.86

YES
ignore
>Enhanced FACH Capability
O

9.2.1.114
FDD and 1.28Mcps TDD only
YES
ignore
>Enhanced PCH Capability
C-EnhancedFACHCapability

9.2.1.115
FDD and 1.28Mcps TDD only
YES
ignore
>SixteenQAM UL Capability
O

9.2.2.88
FDD only
YES
ignore
>HS-DSCH MAC-d PDU Size Capability  
O

9.2.1.31IC

YES
ignore
>MBSFN Only Mode Capability
O

9.2.3.71
1.28Mcps TDD only
YES
ignore
>F-DPCH Slot Format Capability
O

9.2.2.94
FDD only
YES
ignore
>E-DCH MAC-d PDU Size Capability
O

9.2.1.74A

YES
ignore
>Common E-DCH Capability
O

9.2.2.101
FDD only
YES
Ignore
>E-AI Capability
C-CommonEDCHCapability

9.2.2.102
FDD only
YES
Ignore
>Enhanced UE DRX Capability
O

9.2.1.116
FDD only
YES
ignore
>Enhanced UE DRX Capability LCR
O

Enhanced UE DRX Capability
9.2.1.116
1.28Mcps TDD only
YES
ignore
>E-DPCCH Power Boosting Capability
O

9.2.2.109

YES
ignore
>SixtyfourQAM DL and MIMO Combined Capability
O

9.2.1.121
FDD and 1.28Mcps TDD only only 
YES
ignore
>Multi Cell Capability Info
O

9.2.2.113
FDD only
YES
ignore
>Semi-Persistent scheduling Capability LCR
O

9.2.3.91
1.28Mcps TDD only
YES
ignore
>Continuous Packet Connectivity DRX Capability LCR
O

9.2.3.92
1.28Mcps TDD only
YES
ignore
>Common E-DCH HS-DPCCH Capability
C-CommonEDCHCapability

9.2.2.116
FDD only
YES
Ignore
>MIMO Power Offset For S-CPICH Capability
O

9.2.2.118
FDD only
YES
ignore
>TX Diversity on DL Control Channels by MIMO UE Capability
O

9.2.2.121
FDD only
YES
ignore
>Single Stream MIMO Capability
O

9.2.2.122
FDD only
YES
Ignore
>Dual Band Capability Info
O

9.2.2.125
FDD only
YES
ignore
>Cell Portion Capability LCR
O

9.2.3.106
1.28Mcps TDD only
YES
ignore
>Cell Capability Container
O

9.2.2.129
FDD only
YES
ignore
>TS0 Capability LCR
O

9.2.3.109
1.28Mcps TDD only
YES
ignore
>Precoding Weight Set Restriction
O

9.2.2.143
FDD only
YES
ignore
>Cell Capability Container TDD LCR
O

9.2.3.115
1.28Mcps TDD only
YES
ignore
>MU-MIMO Capability Container
O

9.2.3.119
1.28Mcps TDD only
YES
ignore
>Adaptive Special Burst Power Capability LCR
O

9.2.3.122
1.28Mcps TDD only
YES
ignore
Local Cell Group Information

0..<maxLocalCellinNodeB>


EACH
ignore
>Local Cell Group ID
M

9.2.1.37A

–

>DL Or Global Capacity Credit
M

9.2.1.20B

–

>UL Capacity Credit
O

9.2.1.65A

–

>Common Channels Capacity Consumption Law
M

9.2.1.9A

–

>Dedicated Channels Capacity Consumption Law
M

9.2.1.20A

–

>E-DCH Capacity Consumption Law
O

9.2.2.13Ja
FDD only
YES
ignore
>E-DCH TDD Capacity Consumption Law
O

9.2.3.60
TDD only
YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore
Power Local Cell Group Information

0..<maxLocalCellinNodeB>


EACH
ignore
>Power Local Cell Group ID
M

9.2.1.49B

–

>Maximum DL Power Capability
M

9.2.1.39

–

NOTE 1:	This information element is a simplified representation of the ASN.1. [TDD - Repetitions 1 to 8 and repetitions 9 to maxSCCPCHCell are represented by separate ASN.1 structures.] Furthermore, maxSCCPCHCell has different values in the ASN.1 for FDD and for each of the two TDD options.
NOTE 2:	For 1.28Mcps TDD when using multiple frequencies, this information element for Repetition 1 and repetition 2 through maxFrequencyinCell are represented by respective ASN.1 structures with different criticalities.

Condition
Explanation
EDCHCapability
The IE shall be present if the E-DCH Capability IE is set to "E-DCH Capable".
EnhancedFACHCapability
The IE shall be present if the Enhanced FACH Capability IE is set to "Enhanced FACH Capable".
DTX-DRXCapability
The IE shall be present if the Continuous Packet Connectivity DTX-DRX Capability IE is present and set to "Continuous Packet Connectivity DTX-DRX Capable".
CommonEDCHCapability
The IE shall be present if the Common E-DCH Capability IE is set to "Common E-DCH Capable".

Range Bound
Explanation
maxCellinNodeB
Maximum number of Cells that can be configured in Node B
maxCCPinNodeB
Maximum number of Communication Control Ports that can exist in the Node B
maxLocalCellinNodeB
Maximum number of Local Cells that can exist in the Node B
maxSCPICHCell
Maximum number of Secondary CPICHs that can be defined in a Cell.
maxSCCPCHCell
Maximum number of Secondary CCPCHs that can be defined in a Cell.
maxSCCPCHCell768
Maximum number of Secondary CCPCHs that can be defined in a Cell for 7.68 Mcps TDD.
maxFACHCell
Maximum number of FACHs that can be defined in a Cell
maxPRACHCell
Maximum number of PRACHs that can be defined in a Cell
maxRACHCell
Maximum number of RACHs that can be defined in a Cell
maxFPACHCell
Maximum number of FPACHs that can be defined in a Cell
maxPLCCHCell
Maximum number of  PLCCHs that can be defined in a Cell
maxE-RUCCHCell
Maximum number of E-RUCCHs that can be defined in a Cell
maxFrequencyinCell
Maximum number of Frequencies that can be defined in a Cell

9.1.17A	AUDIT FAILURE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Cause
M

9.2.1.6

YES
ignore
Criticality diagnostics
O

9.2.1.17

YES
ignore

9.1.18	COMMON MEASUREMENT INITIATION REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Measurement ID
M

9.2.1.42

YES
reject
CHOICE Common Measurement Object Type
M



YES
reject
>Cell






>>C-ID
M

9.2.1.9

–

>>Time Slot
O

9.2.3.23
Applicable to 3.84McpsTDD and 7.68Mcps TDD only
–

>>Time Slot LCR
O

9.2.3.24A
Applicable to 1.28Mcps TDD only
YES
reject
>>Neighbouring Cell Measurement Information

0..<maxNrOfMeasNCell>


GLOBAL
ignore
>>>CHOICE Neighbouring Cell Measurement Information




–

>>>>Neighbouring FDD Cell Measurement Information



FDD only


>>>>>Neighbouring FDD Cell Measurement Information
M

9.2.1.47C

–

>>>>Neighbouring TDD Cell Measurement Information



Applicable to 3.84Mcps TDD only


>>>>>Neighbouring TDD Cell Measurement Information
M

9.2.1.47D

–

>>>>Additional Neighbouring Cell Measurement Information



See Note 1


>>>>>Neighbouring TDD Cell Measurement Information LCR



Applicable to 1.28Mcps TDD only


>>>>>>Neighbouring TDD Cell Measurement Information LCR
M

9.2.1.47E

YES
reject
>>>>>Neighbouring TDD Cell Measurement Information 7.68Mcps



Applicable to 7.68 Mcps TDD only


>>>>>>Neighbouring TDD Cell Measurement Information 7.68Mcps
M

9.2.3.37

YES
reject
>>UARFCN
O

9.2.1.65
Applicable for 1.28 Mcps TDD only
YES
reject
>>UpPCH Position LCR
O

9.2.3.4Q
Applicable to 1.28Mcps TDD only
YES
reject
>>Additional Time Slot LCR

0..<maxFrequencyinCell – 1>

Applicable to 1.28Mcps TDD only.
If the IE present, the measurement type should also be applied to the time slot (s).
GLOBAL
ignore
>>>UARFCN
M

9.2.1.65

–

>>>Time Slot Initiated LCR

0..6

If the value is zero, the measurement type should be applied to all time slots in the UARFCN which satisfies the requirement of the measurement type
–

>>>>Time Slot LCR 
M

9.2.3.24A

–

>RACH



FDD only


>>C-ID
M

9.2.1.9

–

>>Common Transport Channel ID
M

9.2.1.14

–

>Not Used


NULL
This choice shall not be used. Reject procedure if received. 


>Additional Common Measurement Object Types



See Note 1


>>Power Local Cell Group




–

>>>Power Local Cell Group ID
M

9.2.1.49B

YES
reject
>>E-DCH RACH



FDD only
–

>>>C-ID
M

9.2.1.9

YES
reject
Common Measurement Type
M

9.2.1.11

YES
reject
Measurement Filter Coefficient
O

9.2.1.41

YES
reject
Report Characteristics
M

9.2.1.51

YES
reject
SFN Reporting Indicator
M

FN Reporting Indicator 9.2.1.29B

YES
reject
SFN
O

9.2.1.53A

YES
reject
Common Measurement Accuracy
O

9.2.1.9B

YES
reject
Measurement Recovery Behavior
O

9.2.1.43A

YES
ignore
RTWP* Reporting Indicator
O

9.2.1.53b

YES
reject
RTWP* for Cell Portion Reporting Indicator
O

9.2.1.53c

YES
reject
Reference Received Total Wide Band Power Reporting
O

9.2.2.39C
FDD only
YES
ignore
GANSS Time ID
O

9.2.1.104a
This IE may only be present if the Common Measurement Type IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning". If the Common Measurement Type IE is set to "UTRAN GANSS Timing of Cell Frames for UE Positioning" and this IE is absent, the GANSS time is Galileo system time.
YES
ignore
NOTE 1:	This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1.

Range Bound
Explanation
maxNrOfMeasNCell
Maximum number of neighbouring cells that can be measured on.
maxFrequencyinCell –1
Maximum number of frequencies that can be used in the cell minus 1.

9.1.19	COMMON MEASUREMENT INITIATION RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Measurement ID
M

9.2.1.42

YES
ignore
CHOICE Common Measurement Object Type
O


Common Measurement Object Type that the measurement was initiated with.
YES
ignore
>Cell 






>>Common Measurement Value
M

9.2.1.12
For 1.28Mcps TDD, if the IE Additional Measurement Value is present, this IE shall be ignored.
–

>>Additional Measurement Value

0..<maxFrequencyinCell>

Applicable to 1.28Mcps TDD only.
If more than one measurement value needs to be reported, this IE shall be used.
GLOBAL
ignore
>>>UARFCN
M

9.2.1.65

–

>>>Time Slot Measurement Value LCR

1..6


–

>>>>Time Slot LCR 
M

9.2.3.24A
The IE shall be ignored if the Measurement Type is frequency level.
–

>>>>Common Measurement Value
M

9.2.1.12

–

>RACH



FDD only


>>Common Measurement Value
M

9.2.1.12

–

>Not Used


NULL
This choice shall not be used.


>Additional Common Measurement Object Types



See Note 1


>>Power Local Cell Group




–

>>>Common Measurement Value
M

9.2.1.12

YES 
ignore
>>E-DCH RACH



FDD only


>>>Common Measurement Value
M

9.2.1.12

YES
ignore
SFN
O

9.2.1.53A
Common Measurement Time Reference
YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore
Common Measurement Achieved Accuracy
O

Common Measurement Accuracy 9.2.1.9B

YES
ignore
Measurement Recovery Support Indicator
O

9.2.1.43C

YES
ignore
Reference Received Total Wide Band Power Support Indicator
O

9.2.2.39D
FDD only
YES
ignore
Reference Received Total Wide Band Power
O

9.2.2.39B
FDD only
YES
ignore
NOTE 1:	This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1.

Range Bound
Explanation
maxFrequencyinCell
Maximum number of Frequencies that can be defined in a Cell.

9.1.20	COMMON MEASUREMENT INITIATION FAILURE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Measurement ID
M

9.2.1.42

YES
ignore
Cause
M

9.2.1.6

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.21	COMMON MEASUREMENT REPORT
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Measurement ID
M

9.2.1.42

YES
ignore
CHOICE Common Measurement Object Type
M


Common Measurement Object Type that the measurement was initiated with.
YES
ignore
>Cell 






>>Common Measurement Value Information
M

9.2.1.12A
For 1.28Mcps TDD, if the IE Additional Measurement Value is present, this IE shall be ignored.
–

>>C-ID
O

9.2.1.9

YES
ignore
>>Additional Measurement Value Information

0..<maxFrequencyinCell>

Applicable to 1.28Mcps TDD only.
If more than one measurement value needs to be reported, this IE shall be used.
GLOBAL
ignore
>>>UARFCN


9.2.1.65



>>>Time Slot Measurement Value LCR

1..6




>>>>Time Slot LCR 
M

9.2.3.24A
The IE shall be ignored if the Measurement Type is frequency level.


>>>>Common Measurement Value Information
M

9.2.1.12A



>RACH



FDD only


>>Common Measurement Value Information
M

9.2.1.12A

–

>>C-ID
O

9.2.1.9

YES
ignore
>Not Used


NULL
This choice shall not be used.


>Additional Common Measurement Object Types



See Note 1


>>Power Local Cell Group




–

>>>Common Measurement Value Information
M

9.2.1.12A

YES 
ignore
>>E-DCH RACH



FDD only


>>>Common Measurement Value Information
M

9.2.1.12A

YES
ignore
SFN
O

9.2.1.53A
Common Measurement Time Reference
YES
ignore
Measurement Recovery Reporting Indicator
O

9.2.1.43B

YES
ignore
Reference Received Total Wide Band Power
O

9.2.2.39B
FDD only
YES
ignore
NOTE 1:	This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1.

Range Bound
Explanation
maxFrequencyinCell
Maximum number of Frequencies that can be defined in a Cell.

9.1.22	COMMON MEASUREMENT TERMINATION REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Measurement ID
M

9.2.1.42

YES
ignore

9.1.23	COMMON MEASUREMENT FAILURE INDICATION
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Measurement ID
M

9.2.1.42

YES
ignore
Cause
M

9.2.1.6

YES
ignore

9.1.24	CELL SETUP REQUEST
9.1.24.1	FDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Local Cell ID
M

9.2.1.38

YES
reject
C-ID
M

9.2.1.9

YES
reject
Configuration Generation ID
M

9.2.1.16

YES
reject
T Cell
M

9.2.2.49

YES
reject
UARFCN
M

9.2.1.65
Corresponds to Nu (TS 25.104 [14]) for UTRA operating bands for which it is defined; ignored for UTRA operating bands for which Nu is not defined.
YES
reject
UARFCN
M

9.2.1.65
Corresponds to Nd (TS 25.104 [14])
YES
reject
Maximum Transmission Power
M

9.2.1.40

YES
reject
Closed Loop Timing Adjustment Mode
O

9.2.2.2A

YES
reject
Primary Scrambling Code
M

9.2.2.34

YES
reject
Synchronisation Configuration

1


YES
reject
>N_INSYNC_IND
M

9.2.1.47A

–

>N_OUTSYNC_IND
M

9.2.1.47B

–

>T_RLFAILURE
M

9.2.1.56A

–

DL TPC Pattern 01 Count
M

9.2.2.13A

YES
reject
Primary SCH Information

1


YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>Primary SCH Power
M

DL Power
9.2.1.21

–

>TSTD Indicator
M

9.2.1.64

–

Secondary SCH Information

1


YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>Secondary SCH Power
M

DL Power
9.2.1.21

–

>TSTD Indicator
M

9.2.1.64

–

Primary CPICH Information

1


YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>Primary CPICH power
M

9.2.2.33

–

>Transmit Diversity Indicator
M

9.2.2.53

–

Secondary CPICH Information

0..<maxSCPICHCell>


EACH
reject
>Common Physical Channel ID
M

9.2.1.13

–

>DL Scrambling Code
M

9.2.2.13

–

>FDD DL Channelisation Code Number
M

9.2.2.14

–

>Secondary CPICH Power
M

DL Power
9.2.1.21

–

>Transmit Diversity Indicator
M

9.2.2.53

–

Primary CCPCH Information

1


YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>BCH Information

1
Ignored for UTRA operating bands for which Nu is not defined (TS 25.104 [14]).

–

>>Common Transport Channel ID
M

9.2.1.14

–

>>BCH Power
M

DL Power
9.2.1.21

–

>STTD Indicator
M

9.2.2.48

–

Limited Power Increase Information

1


YES
reject
>Power_Raise_Limit
M

9.2.2.29A

–

>DL_power_averaging_window_size
M

9.2.2.12A

–

IPDL Parameter Information

0..1


YES
reject
>IPDL FDD Parameters
M

9.2.2.18C

–

>IPDL Indicator
M

9.2.1.36F

–

Cell Portion Information

0..<maxNrOfCellPortionsPerCell>


EACH
reject
>Cell Portion ID
M

9.2.2.1Ca

–

>Associated Secondary CPICH
M

Common Physical Channel ID 9.2.1.13

–

>Maximum Transmission Power for Cell Portion
M

Maximum Transmission Power
9.2.1.40

–

MIMO Pilot Configuration
O

9.2.2.73

YES
reject
MIMO Pilot Configuration Extension
O

9.2.2.120
Can only be present if the MIMO Pilot Configuration IE is present
YES
reject
MIMO with four transmit antennas Pilot Configuration
O

9.2.2.165

YES
reject

Range Bound
Explanation
maxSCPICHCell
Maximum number of Secondary CPICHs that can be defined in a Cell.
MaxNrOfCellPortionsPerCell
Maximum number of Cell Portions in a cell 

9.1.24.2	TDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Local Cell ID
M

9.2.1.38

YES
reject
C-ID
M

9.2.1.9

YES
reject
Configuration Generation Id
M

9.2.1.16

YES
reject
UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
For 1.28Mcps TDD, if multiple frequencies exist within the cell indicated by C-ID, this IE indicates the frequency of   Primary Frequency.
YES
reject
Cell Parameter ID
M

9.2.3.4
For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, this IE indicates the preamble code used in the MBSFN Special Time Slot (TS 25.221 [19]).
YES
reject
Maximum Transmission Power
M

9.2.1.40

YES
reject
Transmission Diversity Applied
M

9.2.3.26

YES
reject
Sync Case
M

9.2.3.18

YES
reject
Synchronisation Configuration

1


YES
reject
>N_INSYNC_IND
M

9.2.1.47A

–

>N_OUTSYNC_IND
M

9.2.1.47B

–

>T_RLFAILURE
M

9.2.1.56A

–

DPCH Constant Value
M

Constant Value 9.2.3.4A
This IE shall be ignored by the Node B.
YES
reject
PUSCH Constant Value
M

Constant Value 9.2.3.4A
This IE shall be ignored by the Node B.
YES
reject
PRACH Constant Value
M

Constant Value 9.2.3.4A
This IE shall be ignored by the Node B.
YES
reject
Timing Advance Applied
M

9.2.3.22A

YES
reject
SCH Information

0..1

Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD.
YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>CHOICE Sync Case
M



YES
reject
>>Case 1






>>>Time Slot
M

9.2.3.23

–

>>Case 2






>>>SCH Time Slot 
M

9.2.3.17

–

>SCH Power
M

DL Power
9.2.1.21

–

>TSTD Indicator
M

9.2.1.64

–

PCCPCH Information

0..1

Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD.
YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>TDD Physical Channel Offset
M

9.2.3.20

–

>Repetition Period
M

9.2.3.16

–

>Repetition Length
M

9.2.3.15

–

>PCCPCH Power
M

9.2.3.9

–

>SCTD Indicator
M

9.2.3.30

–

Time Slot Configuration

0..15

Mandatory for 3.84Mcps TDD  and 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD.
GLOBAL
reject
>Time Slot
M

9.2.3.23

–

>Time Slot Status
M

9.2.3.25

–

>Time Slot Direction
M

9.2.3.24

–

>MBSFN Cell Parameter ID
O

Cell Parameter ID
9.2.3.4

YES
reject
Time Slot Configuration LCR

0..7

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
If multiple frequencies exist within the cell indicated by C-ID, this IE indicates the Time Slot configuration of Primary Frequency. 
GLOBAL
reject
>Time Slot LCR
M

9.2.3.24A

–

>Time Slot Status
M

9.2.3.25

–

>Time Slot Direction
M

9.2.3.24

–

>Time Slot Parameter ID
O

Cell Parameter ID
9.2.3.4
Applicable only to MBSFN only mode
YES
reject
PCCPCH Information LCR

0..1

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, PCCPCH is deployed on the MBSFN Special Time Slot (TS 25.221 [19]).
YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>TDD Physical Channel Offset
M

9.2.3.20

–

>Repetition Period
M

9.2.3.16

–

>Repetition Length
M

9.2.3.15

–

>PCCPCH Power
M

9.2.3.9

–

>SCTD Indicator
M

9.2.3.30

–

>TSTD Indicator
M

9.2.1.64

–

DwPCH Information

0..1

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>TSTD Indicator
M

9.2.1.64

–

>DwPCH Power
M

9.2.3.5B

–

Reference SFN Offset
O

9.2.3.14B

YES
ignore
IPDL Parameter Information

0..1

Applicable to 3.84 Mcps TDD and 7.68 Mcps TDD only
YES
reject
>IPDL TDD Parameters
M

9.2.3.5D

–

>IPDL Indicator
M

9.2.1.36F

–

IPDL Parameter Information LCR

0..1

Applicable to 1.28Mcps TDD only
YES
reject
>IPDL TDD Parameters LCR
M

9.2.3.5H

–

>IPDL Indicator
M

9.2.1.36F

–

PCCPCH Information 7.68 Mcps TDD

0..1

Mandatory for 7.68 Mcps TDD. Not Applicable to 1.28Mcps TDD or 3.84 Mcps TDD.
YES
reject
>Common Physical Channel ID 7.68 Mcps
M

9.2.3.33

–

>TDD Physical Channel Offset
M

9.2.3.20

–

>Repetition Period
M

9.2.3.16

–

>Repetition Length
M

9.2.3.15

–

>PCCPCH Power
M

9.2.3.9

–

>SCTD Indicator
M

9.2.3.30

–

SCH Information 7.68Mcps TDD

0..1

Mandatory for 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD or 3.84Mcps TDD.
YES
reject
>Common Physical Channel ID 7.68Mcps
M

9.2.3.33

–

>CHOICE Sync Case
M



YES
reject
>>Case 1






>>>Time Slot
M

9.2.3.23

–

>>Case 2






>>>SCH Time Slot 
M

9.2.3.17

–

>SCH Power
M

DL Power
9.2.1.21

–

>TSTD Indicator
M

9.2.1.64

–

MBSFN Only Mode Indicator
O

9.2.3.70
Mandatory for 1.28Mcps TDD when the cell is operating in MBSFN only mode. Not applicable to FDD, 3.84Mcps TDD or 7.68Mcps TDD
YES
reject
UARFCN Information LCR

0.. <maxFrequencyinCell-1>

Mandatory for 1.28Mcps TDD when using multiple frequencies. 
It indicates the UARFCN and Time Slot configuration information of  the Secondary Frequencies. There could be several secondary frequencies
EACH
reject
>UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
This IE indicates the frequency of a Secondary  Frequency.
–

>Time Slot Configuration LCR

1..7

This IE indicates the Time Slot configuration of a Secondary Frequency.
–

>>Time Slot LCR
M

9.2.3.24A

–

>>Time Slot Status
M

9.2.3.25

–

>>Time Slot Direction
M

9.2.3.24

–

>>Time Slot Parameter ID
O

Cell Parameter ID
9.2.3.4

YES
reject

Range Bound
Explanation
maxFrequencyinCell
Maximum number of Frequencies that can be defined in a Cell

9.1.25	CELL SETUP RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.26	CELL SETUP FAILURE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Cause
M

9.2.1.6

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.27	CELL RECONFIGURATION REQUEST
9.1.27.1	FDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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
Configuration Generation ID
M

9.2.1.16

YES
reject
Maximum Transmission Power
O

9.2.1.40

YES
reject
Synchronisation Configuration

0..1


YES
reject
>N_INSYNC_IND
M

9.2.1.47A

–

>N_OUTSYNC_IND
M

9.2.1.47B

–

>T_RLFAILURE
M

9.2.1.56A

–

Primary SCH Information

0..1


YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>Primary SCH Power
M

DL Power
9.2.1.21

–

Secondary SCH Information

0..1


YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>Secondary SCH Power
M

DL Power
9.2.1.21

–

Primary CPICH Information

0..1


YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>Primary CPICH Power
M

9.2.2.33

–

Secondary CPICH Information

0..<maxSCPICHCell>


EACH
reject
>Common Physical Channel ID
M

9.2.1.13

–

>Secondary CPICH Power
M

DL Power
9.2.1.21

–

Primary CCPCH Information

0..1


YES
reject
>BCH Information

1


–

>>Common Transport Channel ID
M

9.2.1.14

–

>>BCH Power
M

DL Power
9.2.1.21

–

IPDL Parameter Information

0..1


YES
reject
>IPDL FDD Parameters
O

9.2.2.18C

–

>IPDL Indicator
M

9.2.1.36F

–

Cell Portion Information

0..<maxNrOfCellPortionsPerCell>


EACH
reject
>Cell Portion ID
M

9.2.2.1Ca

–

>Maximum Transmission Power for Cell Portion
M

Maximum Transmission Power
9.2.1.40

–

MIMO Pilot Configuration
O

9.2.2.73

YES
reject
MIMO Pilot Configuration Extension
O

9.2.2.120

YES
reject
Dormant Mode Indicator 
O

9.2.1.124

YES
reject
MIMO with four transmit antennas Pilot Configuration
O

9.2.2.165

YES
reject

Range Bound
Explanation
maxSCPICHCell
Maximum number of Secondary CPICH that can be defined in a Cell.
maxNrOfCellPortionsPerCell
Maximum number of Cell Portions in a cell 

9.1.27.2	TDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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
Configuration Generation ID
M

9.2.1.16

YES
reject
Synchronisation Configuration

0..1


YES
reject
>N_INSYNC_IND
M

9.2.1.47A

–

>N_OUTSYNC_IND
M

9.2.1.47B

–

>T_RLFAILURE
M

9.2.1.56A

–

Timing Advance Applied
O

9.2.3.22A

YES
reject
SCH Information

0..1

Applicable to 3.84Mcps TDD only
YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>SCH Power
M

DL Power
9.2.1.21

–

PCCPCH Information

0..1

Not applicable to 7.68Mcps TDD only.
For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, PCCPCH is deployed on the MBSFN Special Time Slot (TS 25.221 [19]).
YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>PCCPCH Power
M

9.2.3.9

–

Maximum Transmission Power
O

9.2.1.40

YES
reject
DPCH Constant Value
O

Constant Value 9.2.3.4A
This IE shall be ignored by the Node B.
YES
reject
PUSCH Constant Value
O

Constant Value 9.2.3.4A
This IE shall be ignored by the Node B.
YES
reject
PRACH Constant Value
O

Constant Value 9.2.3.4A
This IE shall be ignored by the Node B.
YES
reject
Time Slot Configuration

0..15

Mandatory for 3.84Mcps TDD and 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD.
GLOBAL
reject
>Time Slot
M

9.2.3.23

–

>Time Slot Status
M

9.2.3.25

–

>Time Slot Direction
M

9.2.3.24

–

>MBSFN Cell Parameter ID
O

Cell Parameter ID
9.2.3.4

YES
reject
Time Slot Configuration LCR 

0..7

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
If multiple frequencies exist within the cell indicated by C-ID, this IE indicates the Time Slot reconfiguration of Primary Frequency.
GLOBAL
reject
>Time Slot LCR
M

9.2.3.24A

–

>Time Slot Status
M

9.2.3.25

–

>Time Slot Direction
M

9.2.3.24

–

DwPCH Information

0..1

Applicable to 1.28Mcps TDD only.
YES
reject
>Common Physical Channel ID
M

9.2.1.13

–

>DwPCH Power
M

9.2.3.5B

–

IPDL Parameter Information

0..1

Applicable to 3.84Mcps TDD and 7.68Mcps TDD only
YES
reject
>IPDL TDD Parameters
O

9.2.3.5D

–

>IPDL Indicator
M

9.2.1.36F

–

IPDL Parameter Information LCR

0..1

Applicable to 1.28Mcps TDD only
YES
reject
>IPDL TDD Parameters LCR
O

9.2.3.5H

–

>IPDL Indicator
M

9.2.1.36F

–

SCH Information 7.68Mcps 

0..1

Applicable to 7.68Mcps TDD only
YES
reject
>Common Physical Channel ID 7.68Mcps
M

9.2.3.33

–

>SCH Power
M

DL Power
9.2.1.21

–

PCCPCH Information 7.68Mcps

0..1

Applicable to 7.68Mcps TDD only
YES
reject
>Common Physical Channel ID 7.68Mcps
M

9.2.3.33

–

>PCCPCH Power
M

9.2.3.9

–

CHOICE UARFCN Adjustment
O


Applicable to 1.28Mcps TDD when using multiple frequencies 
YES
reject
>Add






>>UARFCN Information To Add LCR

1


–

>>>UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]). 
This IE indicates the frequency of  a Secondary  Frequency to add.
–

>>>Time Slot Configuration LCR

1..7

This IE indicates the Time Slot configuration of a Secondary Frequency to add.
–

>>>>Time Slot LCR
M

9.2.3.24A

–

>>>>Time Slot Status
M

9.2.3.25

–

>>>>Time Slot Direction
M

9.2.3.24

–

>Modify






>>UARFCN Information To Modify LCR

1.. <maxFrequencyinCell-1>

there could be several secondary frequencies
–

>>>UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]). 
This IE indicates the frequency of  a Secondary Frequency to modify.
–

>>>Time Slot Configuration LCR

1..7

This IE indicates the Time Slot reconfiguration of a Secondary Frequency to modify.
–

>>>>Time Slot LCR
M

9.2.3.24A

–

>>>>Time Slot Status
M

9.2.3.25

–

>>>>Time Slot Direction
M

9.2.3.24

–

>Delete






>>UARFCN Information To Delete LCR

1


–

>>>UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]). 
This IE indicates the frequency of  Secondary  Frequency to delete.
–

Dormant Mode Indicator 
O

9.2.1.124

YES
reject

Range Bound
Explanation
maxFrequencyinCell
Maximum number of Frequencies that can be defined in a Cell

9.1.28	CELL RECONFIGURATION RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.29	CELL RECONFIGURATION FAILURE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Cause
M

9.2.1.6

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.30	CELL DELETION REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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

9.1.31	CELL DELETION RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.32	RESOURCE STATUS INDICATION
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

CHOICE Indication Type
M



YES
ignore
>No Failure






>>Local Cell Information

1..<max LocalCellinNode B>


EACH
ignore
>>>Local Cell ID
M

9.2.1.38

–

>>>Add/Delete Indicator
M

9.2.1.1

–

>>>DL Or Global Capacity Credit
C-add

9.2.1.20B

–

>>>UL Capacity Credit
O

9.2.1.65A

–

>>>Common Channels Capacity Consumption Law
C-add

9.2.1.9A

–

>>>Dedicated Channels Capacity Consumption Law
C-add

9.2.1.20A

–

>>>Maximum DL Power Capability
C-add

9.2.1.39

–

>>>Minimum Spreading Factor
C-add

9.2.1.47

–

>>>Minimum DL Power Capability
C-add

9.2.1.46A

–

>>>Local Cell Group ID
O

9.2.1.37A

–

>>>Reference Clock Availability
O

9.2.3.14A
TDD only
YES
ignore
>>>Power Local Cell Group ID
O

9.2.1.49B

YES
ignore
>>>HSDPA Capability
O

9.2.1.31Ga

YES
ignore
>>>E-DCH Capability
O

9.2.1.70

YES
ignore
>>>E-DCH TTI2ms Capability
C-EDCHCapability

9.2.2.13V
FDD only
YES
ignore
>>>E-DCH SF Capability
C-EDCHCapability

9.2.2.13W
FDD only
YES
ignore
>>>E-DCH HARQ Combining Capability
C-EDCHCapability

9.2.2.13X
FDD only
YES
ignore
>>>E-DCH Capacity Consumption Law
O

 9.2.2.13Ja
FDD only
YES
ignore
>>>F-DPCH Capability
O

9.2.2.16a
FDD only
YES
ignore
>>>E-DCH TDD Capacity Consumption Law
O

9.2.3.60
TDD only
YES
ignore
>>>Continuous Packet Connectivity DTX-DRX Capability
O

9.2.2.64
FDD only
YES
ignore
>>>Max UE DTX Cycle
C-DTX-DRXCapability

9.2.2.95
FDD only
YES
ignore
>>>Continuous Packet Connectivity HS-SCCH less Capability
O

9.2.2.65
FDD only
YES
ignore
>>>MIMO Capability
O

9.2.1.118
FDD and 1.28Mcps TDD only
YES
ignore
>>>SixtyfourQAM DL Capability
O

9.2.1.110
FDD and 1.28Mcps TDD only 
YES
ignore
>>>MBMS Capability
O

9.2.1.86

YES
ignore
>>>Enhanced FACH Capability
O

9.2.1.114
FDD and 1.28Mcps TDD only
YES
ignore
>>>Enhanced PCH Capability
C-EnhancedFACHCapability

9.2.1.115
FDD and 1.28Mcps TDD only
YES
ignore
>>>SixteenQAM UL Capability
O

9.2.2.88
FDD only
YES
ignore
>>>HS-DSCH MAC-d PDU Size Capability  
O

9.2.1.31IC

YES
ignore
>>>MBSFN Only Mode Capability
O

9.2.3.71
1.28Mcps TDD only
YES
ignore
>>>F-DPCH Slot Format Capability
O

9.2.2.94
FDD only
YES
ignore
>>>E-DCH MAC-d PDU Size Capability
O

9.2.1.74A

YES
ignore
>>>Common E-DCH Capability
O

9.2.2.101
FDD only
YES
Ignore
>>>E-AI Capability
C-CommonEDCHCapability

9.2.2.102
FDD only
YES
Ignore
>>>Enhanced UE DRX Capability
O

9.2.1.116
FDD only
YES
ignore
>>>Enhanced UE DRX Capability LCR
O

Enhanced UE DRX Capability
9.2.1.116
1.28Mcps TDD only
YES
ignore
>>>E-DPCCH Power Boosting Capability
O

9.2.2.109

YES
ignore
>>>SixtyfourQAM DL and MIMO Combined Capability
O

9.2.1.121
FDD and 1.28Mcps TDD only
YES
ignore
>>>Multi Cell Capability Info
O

9.2.2.113
FDD only
YES
ignore
>>>Semi-Persistent scheduling Capability LCR
O

9.2.3.91
1.28Mcps TDD only
YES
ignore
>>>Continuous Packet Connectivity DRX Capability LCR
O

9.2.3.92
1.28Mcps TDD only
YES
ignore
>>>Common E-DCH HS-DPCCH Capability
C-CommonEDCHCapability

9.2.2.116
FDD only
YES
Ignore
>>>MIMO Power Offset For S-CPICH Capability
O

9.2.2.118
FDD only
YES
ignore
>>>TX Diversity on DL Control Channels by MIMO UE Capability
O

9.2.2.121
FDD only
YES
ignore
>>>Single Stream MIMO Capability
O

9.2.2.122
FDD only
YES
Ignore
>>>Dual Band Capability Info
O

9.2.2.125
FDD only
YES
ignore
>>>Cell Portion Capability LCR
O

9.2.3.106
1.28Mcps TDD only
YES
ignore
>>>Cell Capability Container
O

9.2.2.129
FDD only
YES
ignore
>>>TS0 Capability LCR
O

9.2.3.109
1.28Mcps TDD only
YES
ignore
>>>Precoding Weight Set Restriction
O

9.2.2.143
FDD only
YES
ignore
>>>Cell Capability Container TDD LCR
O

9.2.3.115
1.28Mcps TDD only
YES
ignore
>>>MU-MIMO Capability Container
O

9.2.3.119
1.28Mcps TDD only
YES
ignore
>>>Adaptive Special Burst Power Capability LCR
O

9.2.3.122
1.28Mcps TDD only
YES
ignore
>>Local Cell Group Information

0..<maxLocalCellinNodeB>


EACH
ignore
>>>Local Cell Group ID
M

9.2.1.37A

–

>>>DL Or Global Capacity Credit
M

9.2.1.20B

–

>>>UL Capacity Credit
O

9.2.1.65A

–

>>>Common Channels Capacity Consumption Law
M

9.2.1.9A

–

>>>Dedicated Channels Capacity Consumption Law
M

9.2.1.20A

–

>>>E-DCH Capacity Consumption Law
O

9.2.2.13Ja
FDD only
YES
ignore
>>>E-DCH TDD Capacity Consumption Law
O

9.2.3.60
TDD only
YES
ignore
>>Power Local Cell Group Information

0..<maxLocalCellinNodeB>


EACH
ignore
>>>Power Local Cell Group ID
M

9.2.1.49B

–

>>>Maximum DL Power Capability
M

9.2.1.39

–

>Service Impacting






>>Local Cell Information

0..<maxLocalCellinNodeB>


EACH
ignore
>>>Local Cell ID
M

9.2.1.38

–

>>>DL Or Global Capacity Credit
O

9.2.1.20B

–

>>>UL Capacity Credit
O

9.2.1.65A

–

>>>Common Channels Capacity Consumption Law
O

9.2.1.9A

–

>>>Dedicated Channels Capacity Consumption Law
O

9.2.1.20A

–

>>>Maximum DL Power Capability
O

9.2.1.39

–

>>>Minimum Spreading Factor
O

9.2.1.47

–

>>>Minimum DL Power Capability
O

9.2.1.46A

–

>>>Reference Clock Availability
O

9.2.3.14A
TDD only
YES
ignore
>>>HSDPA Capability
O

9.2.1.31Ga

YES
ignore
>>>E-DCH Capability
O

9.2.1.70

YES
ignore
>>>E-DCH TTI2ms Capability
C-EDCHCapability

9.2.2.13V
FDD only
YES
ignore
>>>E-DCH SF Capability
C-EDCHCapability

9.2.2.13W
FDD only
YES
ignore
>>>E-DCH HARQ Combining Capability
C-EDCHCapability

9.2.2.13X
FDD only
YES
ignore
>>>E-DCH Capacity Consumption Law
O

9.2.2.13Ja
FDD only
YES
ignore
>>>F-DPCH Capability
O

9.2.2.16a

YES
ignore
>>>E-DCH TDD Capacity Consumption Law
O

9.2.3.60
TDD only
YES
ignore
>>>Continuous Packet Connectivity DTX-DRX Capability
O

9.2.2.64
FDD only
YES
ignore
>>>Max UE DTX Cycle
C-DTX-DRXCapability

9.2.2.95
FDD only
YES
ignore
>>>Continuous Packet Connectivity HS-SCCH less Capability
O

9.2.2.65
FDD only
YES
ignore
>>>MIMO Capability
O

9.2.1.118
FDD and 1.28Mcps TDD only
YES
ignore
>>>SixtyfourQAM DL Capability
O

9.2.1.110
FDD and 1.28Mcps TDD only 
YES
ignore
>>>MBMS Capability
O

9.2.1.86

YES
ignore
>>>Enhanced FACH Capability
O

9.2.1.114
FDD only and 1.28Mcps TDD
YES
ignore
>>>Enhanced PCH Capability
C-EnhancedFACHCapability

9.2.1.115
FDD only and 1.28Mcps TDD
YES
ignore
>>>SixteenQAM UL Capability
O

9.2.2.88
FDD only
YES
ignore
>>>HS-DSCH MAC-d PDU Size Capability 
O

9.2.1.31IC

YES
ignore
>>>MBSFN Only Mode Capability
O

9.2.3.71
1.28Mcps TDD only
YES
ignore
>>>F-DPCH Slot Format Capability
O

9.2.2.94
FDD only
YES
ignore
>>>E-DCH MAC-d PDU Size Capability
O

9.2.1.74A

YES
ignore
>>>Common E-DCH Capability
O

9.2.2.101
FDD only
YES
Ignore
>>>E-AI Capability
C-CommonEDCHCapability

9.2.2.102
FDD only
YES
Ignore
>>>Enhanced UE DRX Capability
O

9.2.1.116
FDD only
YES
ignore
>>>Enhanced UE DRX Capability LCR
O

Enhanced UE DRX Capability
9.2.1.116
1.28Mcps TDD only
YES
ignore
>>>E-DPCCH Power Boosting Capability
O

9.2.2.109

YES
ignore
>>>SixtyfourQAM DL and MIMO Combined Capability
O

9.2.1.121
FDD and 1.28Mcps TDD only
YES
ignore
>>>Multi Cell Capability Info
O

9.2.2.113
FDD only
YES
ignore
>>>Semi-Persistent scheduling Capability LCR
O

9.2.3.91
1.28Mcps TDD only
YES
ignore
>>>Continuous Packet Connectivity DRX Capability LCR
O

9.2.3.92
1.28Mcps TDD only
YES
ignore
>>>Common E-DCH HS-DPCCH Capability
C-CommonEDCHCapability

9.2.2.116
FDD only
YES
Ignore
>>>MIMO Power Offset For S-CPICH Capability
O

9.2.2.118
FDD only
YES
ignore
>>>TX Diversity on DL Control Channels by MIMO UE Capability
O

9.2.2.121
FDD only
YES
ignore
>>>Single Stream MIMO Capability
O

9.2.2.122
FDD only
YES
Ignore
>>>Dual Band Capability Info
O

9.2.2.125
FDD only
YES
ignore
>>>Cell Portion Capability LCR
O

9.2.3.106
1.28Mcps TDD only
YES
ignore
>>>Cell Capability Container
O

9.2.2.129
FDD only
YES
ignore
>>>TS0 Capability LCR
O

9.2.3.109
1.28Mcps TDD only
YES
ignore
>>>Precoding Weight Set Restriction
O

9.2.2.143
FDD only
YES
ignore
>>>Cell Capability Container TDD LCR
O

9.2.3.115
1.28Mcps TDD only
YES
ignore
>>>MU-MIMO Capability Container
O

9.2.3.119
1.28Mcps TDD only
YES
ignore
>>>Adaptive Special Burst Power Capability LCR
O

9.2.3.122
1.28Mcps TDD only
YES
ignore
>>Local Cell Group Information

0..<maxLocalCellinNodeB>


EACH
ignore
>>>Local Cell Group ID
M

9.2.1.37A

–

>>>DL Or Global Capacity Credit
O

9.2.1.20B

–

>>>UL Capacity Credit
O

9.2.1.65A

–

>>>Common Channels Capacity Consumption Law
O

9.2.1.9A

–

>>>Dedicated Channels Capacity Consumption Law
O

9.2.1.20A

–

>>>E-DCH Capacity Consumption Law
O

9.2.2.13Ja
FDD only
YES
ignore
>>>E-DCH TDD Capacity Consumption Law
O

9.2.3.60
TDD only
YES
ignore
>>Communication Control Port Information

0..<maxCCPinNodeB>


EACH
ignore
>>>Communication Control Port ID
M

9.2.1.15

–

>>>Resource Operational State
M

9.2.1.52

–

>>>Availability Status
M

9.2.1.2

–

>>Cell Information

0..<maxCellinNodeB>


EACH
ignore
>>>C-ID
M

9.2.1.9

–

>>>Resource Operational State
O

9.2.1.52

–

>>>Availability Status
O

9.2.1.2

–

>>>Primary SCH Information
O

Common Physical Channel Status Information 9.2.1.13A
FDD only
YES
ignore
>>>Secondary SCH Information
O

Common Physical Channel Status Information 9.2.1.13A
FDD only
YES
ignore
>>>Primary CPICH Information
O

Common Physical Channel Status Information 9.2.1.13A
FDD only
YES
ignore
>>>Secondary CPICH Information

0..<maxSCPICHCell>

FDD only
EACH
ignore
>>>>Secondary CPICH Individual Information
M

Common Physical Channel Status Information 9.2.1.13A

–

>>>Primary CCPCH Information
O

Common Physical Channel Status Information 9.2.1.13A

YES
ignore
>>>BCH Information
O

Common Transport Channel Status Information 9.2.1.14B

YES
ignore
>>>Secondary CCPCH Information

0..<maxSCCPCHCell>

See note 1 below
EACH
ignore
>>>>Secondary CCPCH Individual Information
M

Common Physical Channel Status Information 9.2.1.13A

–

>>>PCH Information
O

Common Transport Channel Status Information 9.2.1.14B

YES
ignore
>>>PICH Information
O

Common Physical Channel Status Information 9.2.1.13A

YES
ignore
>>>FACH Information

0..<maxFACHCell>


EACH
ignore
>>>>FACH Individual Information
M

Common Transport Channel Status Information 9.2.1.14B

–

>>>PRACH Information

0..<maxPRACHCell>


EACH
ignore
>>>>PRACH Individual Information
M

Common Physical Channel Status Information 9.2.1.13A

–

>>>RACH Information

0..<maxPRACHCell>


EACH
ignore
>>>>RACH Individual Information
M

Common Transport Channel Status Information 9.2.1.14B

–

>>>AICH Information

0..<maxPRACHCell>

FDD only
EACH
ignore
>>>>AICH Individual Information
M

Common Physical Channel Status Information 9.2.1.13A

–

>>>Not Used 1
O

NULL
This item shall not be used. Ignore if received. 
–

>>>Not Used 2
O

NULL
This item shall not be used. Ignore if received. 
–

>>>Not Used 3
O

NULL
This item shall not be used. Ignore if received. 
–

>>>Not Used 4
O

NULL
This item shall not be used. Ignore if received. 
–

>>>SCH Information
O

Common Physical Channel Status Information 9.2.1.13A
Applicable to 3.84Mcps TDD only
YES
ignore
>>>FPACH Information

0..<maxFPACHCell>

Applicable to 1.28Mcps TDD only
EACH
ignore
>>>>FPACH Individual Information
M

Common Physical Channel Status Information 9.2.1.13A

–

>>>DwPCH Information
O

Common Physical Channel Status Information 9.2.1.13A
Applicable to 1.28Mcps TDD only
YES
ignore
>>>HS-DSCH Resources Information

0.. <maxFrequencyinCell>

See note 2 below
EACH
ignore
>>>>Resource Operational State
M

9.2.1.52

–

>>>>Availability Status
M

9.2.1.2

–

>>>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Applicable to 1.28Mcps TDD when using multiple frequencies.
YES
ignore
>>>MICH Information
O

Common Physical Channel Status Information 9.2.1.13A

YES
ignore
>>>E-DCH Resources Information

0..<maxFrequencyinCell>

See note 2 below
EACH
ignore
>>>>Resource Operational State
M

9.2.1.52

–

>>>>Availability Status
M

9.2.1.2

–

>>>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Applicable to 1.28Mcps TDD when using multiple frequencies.
YES
ignore
>>>PLCCH Information

0..<maxPLCCHCell>

Applicable to 1.28Mcps TDD only
EACH
ignore
>>>>PLCCH Individual Information
M

Common Physical Channel Status Information 9.2.1.13A

–

>>>Primary CCPCH Information 7.68Mcps 
O

Common Physical Channel Status Information 7.68Mcps 9.2.3.36

YES
ignore
>>>Secondary CCPCH Information 7.68Mcps

0..<maxSCCPCHCell768>


EACH
ignore
>>>>Secondary CCPCH Individual Information 7.68Mcps 
M

Common Physical Channel Status Information 7.68Mcps 9.2.3.36

–

>>>PICH Information 7.68Mcps
O

Common Physical Channel Status Information 7.68Mcps 9.2.3.36

YES
ignore
>>>PRACH Information 7.68Mcps

0..<maxPRACHCell>


EACH
ignore
>>>>PRACH Individual Information 7.68Mcps
M

Common Physical Channel Status Information 7.68Mcps 9.2.3.36

–

>>>SCH Information 7.68Mcps
O

Common Physical Channel Status Information 7.68Mcps 9.2.3.36
Applicable to 7.68Mcps TDD only
YES
ignore
>>>MICH Information 7.68Mcps
O

Common Physical Channel Status Information 7.68Mcps 9.2.3.36

YES
ignore
>>>E-RUCCH Information

0..<maxE-RUCCHCell>

Applicable to 3.84Mcps TDD only
EACH
ignore
>>>>E-RUCCH Individual Information
M

Common Physical Channel Status Information 9.2.1.13A

–

>>>E-RUCCH Information 7.68Mcps

0..<maxE-RUCCHCell>

Applicable to 7.68Mcps TDD only
EACH
ignore
>>>>E-RUCCH Individual Information 7.68Mcps
M

Common Physical Channel Status Information 7.68Mcps 9.2.3.36

–

>>>UARFCN Information LCR

0..<maxFrequencyinCell>

Applicable to 1.28Mcps TDD when using multiple frequencies.
EACH
ignore
>>>>UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
–

>>>>Resource Operational State
M

9.2.1.52

–

>>>>Availability Status
M

9.2.1.2

–

>>>>Cause
O

9.2.1.6

–

>>>UpPCH Information LCR

0..<maxFrequencyinCell>

Applicable to 1.28Mcps TDD only.
EACH
ignore
>>>>UARFCN
O

9.2.1.65
Mandatory for 1.28Mcps TDD when using multiple frequencies. Corresponds to Nt (TS 25.105 [15]).
–

>>>>UpPCH Position LCR
M

9.2.3.4Q

–

>>>>Resource Operational State
M

9.2.1.52

–

>>>>Availability Status
M

9.2.1.2

–

>>Power Local Cell Group Information

0..<maxLocalCellinNodeB>


EACH
ignore
>>>Power Local Cell Group ID
M

9.2.1.49B

–

>>>Maximum DL Power Capability
M

9.2.1.39

–

Cause
O

9.2.1.6

YES
ignore
NOTE 1:	This information element is a simplified representation of the ASN.1. [TDD - Repetitions 1 to 8 and repetitions 9 to maxSCCPCHCell are represented by separate ASN.1 structures.] Furthermore, maxSCCPCHCell has different values in the ASN.1 for FDD and for each of the two TDD options.
NOTE 2:	For 1.28Mcps TDD when using multiple frequencies, this information element for Repetition 1 and repetition 2 through maxFrequencyinCell are represented by respective ASN.1 structures with different criticalities.

Condition
Explanation
add
The IE shall be present if the Add/Delete Indicator IE is set to "Add".
EDCHCapability
The IE shall be present if the E-DCH Capability IE is set to "E-DCH Capable".
EnhancedFACHCapability
The IE shall be present if the Enhanced FACH Capability IE is set to "Enhanced FACH Capable".
DTX-DRXCapability
The IE shall be present if the Continuous Packet Connectivity DTX-DRX Capability IE is present and set to " Continuous Packet Connectivity DTX-DRX Capable".
CommonEDCHCapability
The IE shall be present if the Common E-DCH Capability IE is set to "Common E-DCH Capable".

Range Bound
Explanation
maxLocalCellinNodeB
Maximum number of Local Cells that can exist in the Node B
maxCellinNodeB
Maximum number of C-IDs that can be configured in the Node B
maxSCPICHCell
Maximum number of Secondary CPICHs that can be defined in a Cell.
maxSCCPCHCell
Maximum number of Secondary CCPCHs that can be defined in a Cell.
maxFACHCell
Maximum number of FACHs that can be defined in a Cell
maxPRACHCell
Maximum number of PRACHs and AICHs that can be defined in a Cell
maxCCPinNodeB
Maximum number of Communication Control Ports that can exist in the Node B
maxFPACHCell
Maximum number of FPACHs that can be defined in a Cell
maxPLCCHCell
Maximum number of PLCCHs that can be defined in a Cell
maxE-RUCCHCell
Maximum number of E-RUCCHs that can be defined in a Cell
maxFrequencyinCell
Maximum number of Frequencies that can be defined in a Cell

9.1.33	SYSTEM INFORMATION UPDATE REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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 Indicator
M



_

>>No Deletion






>>>SIB Originator
C-SIB

9.2.1.55

–

>>>IB SG REP
O

9.2.1.34

–

>>>Segment Information

1..<maxIBSEG>


GLOBAL
reject
>>>>IB SG POS
O

9.2.1.33

–

>>>>Segment Type
C-CRNCOrigination

9.2.1.53B

–

>>>>IB SG DATA
C-CRNCOrigination

9.2.1.32

–

>>Deletion


NULL



BCH mapped on SCCPCH Indication
O

ENUMERATED (InUse)

YES
reject

Range bound
Explanation
maxIB
Maximum number of information Blocks supported in one message
maxIBSEG
Maximum number of segments for one Information Block

Condition
Explanation
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".

9.1.34	SYSTEM INFORMATION UPDATE RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.35	SYSTEM INFORMATION UPDATE FAILURE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Cause
M

9.2.1.6

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.36	RADIO LINK SETUP REQUEST
9.1.36.1	FDD message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
reject
UL DPCH Information

1


YES
reject
>UL Scrambling Code
M

9.2.2.59

–

>Min UL Channelisation Code Length
M

9.2.2.22

–

>Max Number of UL DPDCHs
C-CodeLen

9.2.2.21

–

>Puncture Limit
M

9.2.1.50
For UL
–

>TFCS
M

9.2.1.58
For UL
–

>UL DPCCH Slot Format
M

9.2.2.57

–

>UL SIR Target
M

UL SIR
9.2.1.67A

–

>Diversity Mode
M

9.2.2.9

–

>Not Used
O

NULL

–

>Not Used
O

NULL

–

>DPC Mode
O

9.2.2.13C

YES
reject
>UL DPDCH Indicator For E-DCH Operation
O

9.2.2.61
This IE may be present without the presence of the E-DPCH Information IE
YES
reject
DL DPCH Information

0..1


YES
reject
>TFCS
M

9.2.1.58
For DL
–

>DL DPCH Slot Format
M

9.2.2.10

–

>TFCI Signalling Mode
M

9.2.2.50

–

>TFCI Presence
C-SlotFormat

9.2.1.57

–

>Multiplexing Position
M

9.2.2.23

–

>Not Used
O

NULL

–

>Not Used
O

NULL

–

>Power Offset Information

1


–

>>PO1
M

Power Offset
9.2.2.29
Power offset for the TFCI bits
–

>>PO2
M

Power Offset
9.2.2.29
Power offset for the TPC bits
–

>>PO3
M

Power Offset
9.2.2.29
Power offset for the pilot bits
_

>FDD TPC DL Step Size
M

9.2.2.16

–

>Limited Power Increase
M

9.2.2.18A

–

>Inner Loop DL PC Status
M

9.2.2.18B

–

DCH Information
M

DCH FDD Information9.2.2.4D

YES
reject
RL Information

1..<maxNrOfRLs>


EACH
notify
>RL ID
M

9.2.1.53

–

>C-ID
M

9.2.1.9

–

>First RLS Indicator
M

9.2.2.16A

–

>Frame Offset
M

9.2.1.31

–

>Chip Offset
M

9.2.2.2

–

>Propagation Delay
O

9.2.2.35

–

>Diversity Control Field
C-NotFirstRL

9.2.1.25

–

>DL Code Information
M

FDD DL Code Information 9.2.2.14A

–

>Initial DL Transmission Power
M

DL Power
9.2.1.21
Initial power on DPCH or on
F-DPCH
–

>Maximum DL Power
M

DL Power
9.2.1.21
Maximum allowed power on DPCH or on F-DPCH
–

>Minimum DL Power
M

DL Power
9.2.1.21
Minimum allowed power on DPCH or on F-DPCH
–

>Not Used
O

NULL

–

>Transmit Diversity Indicator
C-Diversity mode

9.2.2.53

–

>RL Specific DCH Information
O

9.2.1.53G

YES
ignore
>Delayed Activation
O

9.2.1.24C

YES
reject
>Primary CPICH Usage For Channel Estimation
O

9.2.2.33A

YES
ignore
>Secondary CPICH Information
O

Common Physical Channel ID 9.2.1.13

YES
ignore
>E-DCH RL Indication
O

9.2.2.13De

YES
reject
>RL Specific E-DCH Information
O

9.2.2.39a

YES
ignore
>Synchronisation Indicator
O

9.2.2.48A

YES
ignore
>Extended Propagation Delay
O

9.2.2.35A

YES
ignore
>F-DPCH Slot Format
O

9.2.2.93

YES
reject
> HS-DSCH Preconfiguration Setup
O

9.2.2.112

YES
ignore
>E-RNTI
O

9.2.1.75

YES
ignore
>Non-Serving RL Preconfiguration Setup
O

9.2.2.144

YES
ignore
>F-TPICH Information
O

9.2.2.160

YES
ignore
>TPC slot position
O

9.2.2.217

YES
ignore
Transmission Gap Pattern Sequence Information
O

9.2.2.53A

YES
reject
Active Pattern Sequence Information
O

9.2.2.A

YES
reject
DL Power Balancing Information
O

9.2.2.12B

YES
ignore
HS-DSCH Information
O

HS-DSCH FDD Information 9.2.2.18D

YES
reject
HS-DSCH RNTI
C-InfoHSDSCH

9.2.1.31J

YES
reject
HS-PDSCH RL ID
C-InfoHSDSCH

RL ID 9.2.1.53

YES
reject
E-DPCH Information

0..1


YES
reject
>Maximum Set of E-DPDCHs
M

9.2.2.20C

–

>Puncture Limit
M

9.2.1.50

–

>E-TFCS Information
M

9.2.2.13Dh

–

>E-TTI
M

9.2.2.13Di

–

>E-DPCCH Power Offset
M

9.2.2.13Dj

–

>E-RGCH 2-Index-Step Threshold
M

9.2.2.13Ig

–

>E-RGCH 3-Index-Step Threshold
M

9.2.2.13Ih

–

>HARQ Info for E-DCH
M

9.2.2.18ba

–

>HS-DSCH Configured Indicator
M

9.2.2.18Ca

–

>E-RNTI
O

9.2.1.75
Shall be ignored if E-RNTI IE is included in the RL Information IE
YES
reject
>Minimum Reduced E-DPDCH Gain Factor
O

9.2.2.114

YES
ignore
E-DCH FDD Information
C-EDPCHInfo 

9.2.2.13Da

YES
reject
Serving E-DCH RL
O

9.2.2.48B

YES
reject
F-DPCH Information

0..1


YES
reject
>Power Offset Information

1


–

>>PO2
M

Power Offset
9.2.2.29
This IE shall be ignored by Node B.
_

>FDD TPC DL Step Size
M

9.2.2.16

–

>Limited Power Increase
M

9.2.2.18A

–

>Inner Loop DL PC Status
M

9.2.2.18B

–

Initial DL DPCH Timing Adjustment Allowed
O

9.2.2.18K

YES
ignore
DCH Indicator For E-DCH-HSDPA Operation
O

9.2.2.4F

YES
reject
Serving Cell Change CFN
O

CFN
9.2.1.7

YES
reject
Continuous Packet Connectivity DTX-DRX Information
O

9.2.2.66

YES
reject
Continuous Packet Connectivity HS-SCCH less Information
O

9.2.2.68

YES
reject
Additional HS Cell Information RL Setup

0..<maxNrOfHSDSCH-1>

For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. 
EACH
reject
>HS-PDSCH RL ID
M

RL ID
9.2.1.53

–

>C-ID
M

9.2.1.9

–

>HS-DSCH FDD Secondary Serving Information
M

9.2.2.18Da

–

UE Aggregate Maximum Bit Rate
O

9.2.1.123

YES
ignore
Additional E-DCH Cell Information RL Setup Req

0..1

For E-DCH on multiple frequencies in this Node B.
YES
reject
>Multicell E-DCH Transport Bearer Mode

M

9.2.2.130

–

>Additional E-DCH Cell Information Setup 

1..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.
–

>>Additional E-DCH FDD Setup Information
M

9.2.2.131

–

Usefulness of Battery Optimization
O

9.2.2.147

YES
ignore
UL CLTD Information
O

9.2.2.152

YES
reject
E-DCH Decoupling Indication
O

9.2.2.194

YES
reject
DCH Enhancements Information
O

9.2.2.196

YES
reject
Radio Links without DPCH/F-DPCH Indication
O

9.2.2.201

YES
reject
UL DPCCH2 Information
O

9.2.2.203

YES
reject
Downlink TPC enhancements Information
O

9.2.2.214

YES
reject

Condition
Explanation
CodeLen
The IE shall be present if Min UL Channelisation Code Length IE equals to 4.
NotFirstRL
The IE shall be present if the RL is not the first one in the RL Information IE.
SlotFormat
The IE shall be present if the DL DPCH Slot Format IE is equal to any of the values from 12 to 16.
Diversity mode
The IE shall be present if Diversity Mode IE in UL DPCH Information IE is not set to "none".
InfoHSDSCH
The IE shall be present if HS-DSCH Information IE is present.
EDPCHInfo
This IE shall be present if E-DPCH Information IE is present.

Range Bound
Explanation
maxNrOfRLs
Maximum number of RLs for one UE
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE
maxNrOfEDCH-1
Maximum number of uplink frequencies -1 for E-DCH for one UE

9.1.36.2	TDD message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
reject
UL CCTrCH Information

0..<maxNrOfCCTrCHs>


EACH
notify
>CCTrCH ID
M

9.2.3.3

–

>TFCS
M

9.2.1.58

–

>TFCI Coding
M

9.2.3.22

–

>Puncture Limit
M

9.2.1.50

–

>UL DPCH Information

0..1

Applicable to 3.84Mcps TDD only
YES
notify
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD DPCH Offset
M

9.2.3.19A

–

>>UL Timeslot Information
M

9.2.3.26C

–

>UL DPCH Information LCR

0..1

Applicable to 1.28Mcps TDD only
YES
notify
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD DPCH Offset
M

9.2.3.19A

–

>>UL Timeslot Information LCR
M

9.2.3.26E

–

>UL SIR Target
O

UL SIR
9.2.1.67A
Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
reject
>TDD TPC UL Step Size
O

9.2.3.21a
Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
reject
>UL DPCH Information 7.68Mcps

0..1

Applicable to 7.68Mcps TDD only
YES
notify
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD DPCH Offset
M

9.2.3.19A

–

>>UL Timeslot Information 7.68Mcps
M

9.2.3.38

–

DL CCTrCH Information

0..<maxNrOfCCTrCHs>


EACH
notify
>CCTrCH ID
M

9.2.3.3

–

>TFCS
M

9.2.1.58

–

>TFCI Coding
M

9.2.3.22

–

>Puncture Limit
M

9.2.1.50

–

>TDD TPC DL Step Size
M

9.2.3.21

–

>TPC CCTrCH List

0..<maxNrOfCCTrCHs>

List of uplink CCTrCH which provide TPC
–

>>TPC CCTrCH ID 
M

CCTrCH ID
9.2.3.3

–

>DL DPCH information

0..1

Applicable to 3.84Mcps TDD only
YES
notify
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD DPCH Offset
M

9.2.3.19A

–

>>DL Timeslot Information
M

9.2.3.4E

–

>DL DPCH information LCR

0..1

Applicable to 1.28Mcps TDD only
YES
notify
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD DPCH Offset
M

9.2.3.19A

–

>>DL Timeslot Information LCR
M

9.2.3.4O

–

>>TSTD Indicator
M

9.2.1.64

–

>CCTrCH Initial DL  Transmission Power
O

DL Power
9.2.1.21

YES
ignore
>CCTrCH Maximum DL Transmission Power
O

DL Power
9.2.1.21

YES
ignore
>CCTrCH Minimum DL Transmission Power
O

DL Power
9.2.1.21

YES
ignore
>DL DPCH information 7.68Mcps

0..1

Applicable to 7.68Mcps TDD only
YES
notify
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD DPCH Offset
M

9.2.3.19A

–

>>DL Timeslot Information 7.68Mcps
M

9.2.3.39

–

DCH Information
O

DCH TDD Information 9.2.3.4C

YES
reject
DSCH Information
O

DSCH TDD Information 9.2.3.5A

YES
reject
USCH Information
O

9.2.3.28

YES
reject
RL Information

1


YES
reject
>RL ID
M

9.2.1.53

–

>C-ID
M

9.2.1.9

–

>Frame Offset
M

9.2.1.31

–

>Special Burst Scheduling
M

9.2.3.18A

–

>Initial DL Transmission Power
M

DL Power
9.2.1.21

–

>Maximum DL Power
M

DL Power
9.2.1.21

–

>Minimum DL Power
M

DL Power
9.2.1.21

–

>DL Time Slot ISCP Info
O

9.2.3.4F
Applicable to 3.84Mcps TDD and 7.68Mcps TDD only
–

>DL Time Slot ISCP Info LCR
O

9.2.3.4P
Applicable to 1.28Mcps TDD only
YES
reject
>RL Specific DCH Information
O

9.2.1.53G

YES
ignore
>Delayed Activation
O

9.2.1.24C

YES
reject
>UL Synchronisation Parameters LCR

0..1

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
reject
>>Uplink Synchronisation Step Size
M

9.2.3.26H

–

>>Uplink Synchronisation Frequency
M

9.2.3.26G

–

>UARFCN
O

9.2.1.65
Mandatory for 1.28Mcps TDD when using multiple frequencies. 
Corresponds to Nt (TS 25.105 [15]).
YES
reject
HS-DSCH Information
O

HS-DSCH TDD Information 9.2.3.5F

YES
reject
HS-DSCH RNTI
C-InfoHSDSCH

9.2.1.31J

YES
reject
HS-PDSCH RL ID
C-InfoHSDSCH

RL ID 9.2.1.53

YES
reject
PDSCH-RL-ID
O

RL ID
9.2.1.53

YES
ignore
E-DCH Information

0..1

3.84Mcps TDD only
YES
reject
>E-PUCH Information
M

9.2.3.45

–

>E-TFCS Information TDD
M

9.2.3.46

–

>E-DCH MAC-d Flows Information TDD
M

9.2.3.47

–

>E-DCH Non-scheduled Grant Information TDD
O

9.2.3.48

–

>E-DCH TDD Information
M

9.2.3.49

–

E-DCH Serving RL
O

RL ID
9.2.1.53

YES
reject
E-DCH Information 7.68Mcps

0..1

7.68Mcps TDD only
YES
reject
>E-PUCH Information
M

9.2.3.45

–

>E-TFCS Information TDD
M

9.2.3.46

–

>E-DCH MAC-d Flows Information TDD
M

9.2.3.47

–

>E-DCH Non-scheduled Grant Information 7.68Mcps TDD
O

9.2.3.64

–

>E-DCH TDD Information 7.68Mcps
M

9.2.3.65

–

E-DCH Information 1.28Mcps

0..1

1.28Mcps TDD only
YES 
reject
>E-PUCH Information LCR
M

9.2.3.45a

–

>E-TFCS Information TDD
M

9.2.3.46

–

>E-DCH MAC-d Flows Information TDD
M

9.2.3.47

–

>E-DCH Non-scheduled Grant Information LCR TDD
O

9.2.3.48a

–

>E-DCH TDD Information LCR
M

9.2.3.49a

–

Power Control GAP
O

INTEGER (1..255)
Unit: Number of subframes
Applicable to 1.28Mcps TDD only
YES
ignore
Continuous Packet Connectivity DRX Information LCR
O

9.2.3.93
1.28 Mcps TDD only
YES
reject
HS-DSCH Semi-Persistent scheduling Information LCR
O

9.2.3.96
1.28 Mcps TDD only
YES
reject
E-DCH Semi-Persistent scheduling Information LCR
O

9.2.3.97
1.28 Mcps TDD only
YES
reject
Idle Interval Information
O

9.2.3.102
TDD only
YES
ignore
UE Selected MBMS Service Information
O
    
9.2.3.104
This IE indicates the Time Slot information and/or TDM information of UE selected MBMS service in the other frequency. For 1.28Mcps TDD only.
YES
ignore
HS-SCCH TPC step size
O
    
TDD TPC DL Step Size
9.2.3.21
1.28 Mcps TDD only.
This IE is mandatory if DL CCTrCH Information IE and E-DCH Information 1.28Mcps IE are both absent.
YES
ignore
DCH Measurement Occasion Information
O
    
9.2.3.111
Applicable for 1.28 Mcps TDD.
YES
reject
HS-DSCH-RNTI for FACH
O
    
HS-DSCH RNTI
9.2.1.31J
1.28 Mcps TDD only
YES
ignore
Multi-Carrier E-DCH Information

0..1

Applicable for Multi-Carrier E-DCH Operation in 1.28 Mcps TDD only
YES
reject
>Multi-Carrier E-DCH Transport Bearer Mode LCR
M
    
9.2.3.113
1.28 Mcps TDD only
–

>Multi-Carrier E-DCH Information LCR
M
    
9.2.3.112
1.28 Mcps TDD only
–

MU-MIMO Information
O
    
9.2.3.116
1.28 Mcps TDD only
YES
ignore
UE support of non-rectangular resource allocation
O
    
ENUMERATED (support)
1.28 Mcps TDD only.
The absence of this IE indicates that the UE does not support the non-rectangular resource allocation.
YES
ignore


Range Bound
Explanation
maxNrOfCCTrCHs
Number of CCTrCHs for one UE

Condition
Explanation
InfoHSDSCH
The IE shall be present if HS-DSCH Information IE is present.

9.1.37	RADIO LINK SETUP RESPONSE
9.1.37.1	FDD message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
ignore
Communication Control Port ID
M

9.2.1.15

YES
ignore
RL Information Response

1..<maxNrOfRLs>


EACH
ignore
>RL ID
M

9.2.1.53

–

>RL Set ID
M

9.2.2.39

–

>Received Total Wide Band Power
M

9.2.2.39A

–

>CHOICE Diversity Indication
M



–

>>Combining






>>>RL ID
M

9.2.1.53
Reference RL ID for the combining
–

>>Non Combining or First RL






>>>DCH Information Response
M

9.2.1.20C

–

>>>E-DCH FDD Information Response
O

9.2.2.13Db 

YES
ignore
>Not Used
O

NULL

–

>SSDT Support Indicator
M

9.2.2.46

–

>DL Power Balancing Activation Indicator
O

9.2.2.12C

YES
ignore
>E-DCH RL Set ID
O

RL Set ID
9.2.2.39

YES
ignore
>E-DCH FDD DL Control Channel Information
O

9.2.2.13Dc

YES
ignore
>Initial DL DPCH Timing Adjustment
O

DL DPCH Timing Adjustment
9.2.2.10A

YES
ignore
> HS-DSCH Preconfiguration Info
O

9.2.2.111

YES
ignore
>Non-Serving RL Preconfiguration Info
O

9.2.2.145

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore
HS-DSCH Information Response
O

HS-DSCH FDD Information Response 9.2.2.18E

YES
ignore
Continuous Packet Connectivity HS-SCCH less Information Response
O

9.2.2.69

YES
ignore
Additional HS Cell Information Response

0..<maxNrOfHSDSCH-1>

For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. 
EACH
ignore
>HS-PDSCH RL ID
M

RL ID 9.2.1.53

–

>HS-DSCH FDD Secondary Serving Information Response
M

9.2.2.18EA

–

Additional E-DCH Cell Information Response

0..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release 
EACH
ignore
>Additional E-DCH FDD  Information Response
M

9.2.2.135

–


Range Bound
Explanation
maxNrOfRLs
Maximum number of RLs for one UE
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE
maxNrOfEDCH-1
Maximum number of uplink frequencies -1 for E-DCH for one UE

9.1.37.2	TDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
ignore
Communication Control Port ID
M

9.2.1.15

YES
ignore
RL Information Response

0..1

Mandatory for 3.84Mcps TDD and 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD.
YES
ignore
>RL ID
M

9.2.1.53

–

>UL Time Slot ISCP Info
M

9.2.3.26D

–

>UL PhysCH SF Variation
M

9.2.3.26B

–

>DCH Information Response
O

9.2.1.20C

YES
ignore
>DSCH Information Response
O

9.2.3.5b

YES
ignore
>USCH Information Response
O

9.2.3.29

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore
RL Information Response LCR

0..1

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
ignore
>RL ID
M

9.2.1.53

–

>UL Time Slot ISCP Info LCR
M

9.2.3.26F

–

>UL PhysCH SF Variation
M

9.2.3.26B

–

>DCH Information Response
O

9.2.1.20C

YES
ignore
>DSCH Information Response
O

9.2.3.5b

YES
ignore
>USCH Information Response
O

9.2.3.29

YES
ignore
HS-DSCH Information Response
O

HS-DSCH TDD Information Response 9.2.3.5G

YES
ignore
E-DCH Information Response
O

E-DCH TDD Information Response 9.2.3.50

YES
ignore
Continuous Packet Connectivity DRX Information Response LCR
O

9.2.3.95
1.28 Mcps TDD only
YES
ignore
HS-DSCH Semi-Persistent scheduling Information Response LCR
O

9.2.3.98
1.28 Mcps TDD only
YES
ignore
E-DCH Semi-Persistent scheduling Information Response LCR
O

9.2.3.99
1.28 Mcps TDD only
YES
ignore
E-RNTI for FACH
O

E-RNTI
9.2.1.75
1.28 Mcps TDD only
YES
ignore
Multi-Carrier E-DCH Information Response LCR
O

9.2.3.114
1.28 Mcps TDD only
YES
ignore
MU-MIMO Information Response
O

9.2.3.118
1.28 Mcps TDD only
YES
reject
Non-rectangular resource allocation indicator
O

ENUMERATED (activate)
1.28 Mcps TDD only.
The absence of this IE indicates that the non-rectangular resource allocation is not used.
YES
reject
Non-rectangular resource timeslot set
O

BIT STRING (SIZE(7))
1.28 Mcps TDD only.
The absence of this IE means that the specific timeslot(s) of the non-rectangular resource is defined in 3GPP TS 25.222 [34].
This IE indicats which of the timeslot(s) is/are allocated for non-rectangular resource. 
Bit 0 is for timeslot 0. Bit 1 is for timeslot 1. Bit 2 is for timeslot 2. Bit 3 is for timeslot 3. Bit 4 is for timeslot 4. Bit 5 is for timeslot 5. Bit 6 is for timeslot 6.
The value 0 of a bit means the corresponding timeslot is not allocated for non-rectangular resource. The value 1 of a bit means the corresponding timeslot is allocated for non-rectangular resource.
Bit 0 is the first/leftmost bit of the bit string.
YES
reject

9.1.38	RADIO LINK SETUP FAILURE
9.1.38.1	FDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
Node B Communication Context ID
C-Success

9.2.1.48
The reserved value "All NBCC” shall not be used
YES
ignore
Communication Control Port ID
O

9.2.1.15

YES
ignore
CHOICE Cause Level
M



YES
ignore
>General






>>Cause
M

9.2.1.6

–

>RL Specific






>>Unsuccessful RL Information Response

1..<maxNrOfRLs>


EACH
ignore
>>>RL ID
M

9.2.1.53

–

>>>Cause
M

9.2.1.6

–

>>Successful RL Information Response

0..<maxNrOfRLs>

Note: There will never be maxNrOfRLs repetitions of this sequence.
EACH
ignore
>>>RL ID
M

9.2.1.53

–

>>>RL Set ID
M

9.2.2.39

–

>>>Received Total Wide Band Power
M

9.2.2.39A

–

>>>CHOICE Diversity Indication
M



–

>>>>Combining






>>>>>RL ID
M

9.2.1.53
Reference RL ID for the combining
–

>>>>Non Combining or First RL






>>>>>DCH Information Response
M

9.2.1.20C

–

>>>>>E-DCH FDD Information Response
O

9.2.2.13Db

YES
ignore
>>>Not Used
O

NULL

–

>>>Not Used
O

NULL

–

>>>SSDT Support Indicator
M

9.2.2.46

–

>>>DL Power Balancing Activation Indicator
O

9.2.2.12C

YES
ignore
>>>E-DCH RL Set ID
O

RL Set ID
9.2.2.39

YES
ignore
>>>E-DCH FDD DL Control Channel Information
O

9.2.2.13Dc

YES
ignore
>>>Initial DL DPCH Timing Adjustment
O

DL DPCH Timing Adjustment
9.2.2.10A

YES
ignore
>>> HS-DSCH Preconfiguration Info
O

9.2.2.111

YES
ignore
>>>Non-Serving RL Preconfiguration Info
O

9.2.2.145

YES
ignore
>>HS-DSCH Information Response
O

HS-DSCH FDD Information Response
9.2.2.18E

YES
ignore
>>Continuous Packet Connectivity HS-SCCH less Information Response
O

9.2.2.69

YES
ignore
>>Additional HS Cell Information Response

0..<maxNrOfHSDSCH-1>

For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. 
EACH
ignore
>>>HS-PDSCH RL ID
M

RL ID 9.2.1.53

–

>>>HS-DSCH FDD Secondary Serving Information Response
M

9.2.2.18EA

–

>>Additional E-DCH Cell Information Response

0..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release
EACH
ignore
>>>Additional E-DCH FDD Information Response
M

9.2.2.135

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

Condition
Explanation
Success
The IE shall be present if at least one of the radio links has been successfully set up.

Range Bound
Explanation
maxNrOfRLs
Maximum number of RLs for one UE
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE
maxNrOfEDCH-1
Maximum number of uplink frequencies -1 for E-DCH for one UE

9.1.38.2	TDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
CHOICE Cause Level
M



YES
ignore
>General






>>Cause
M

9.2.1.6

–

>RL Specific






>>Unsuccessful RL 
Information Response

1


YES
ignore
>>>RL ID
M

9.2.1.53

–

>>>Cause
M

9.2.1.6

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.39	RADIO LINK ADDITION REQUEST
9.1.39.1	FDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
reject
Compressed Mode Deactivation Flag
O

9.2.2.3A
Shall be ignored if IE “Active Pattern Sequence Information” is present
YES
reject
RL Information 

1..<maxNrOfRLs-1>


EACH
notify
>RL ID
M

9.2.1.53

–

>C-ID
M

9.2.1.9

–

>Frame Offset
M

9.2.1.31

–

>Chip Offset
M

9.2.2.2

–

>Diversity Control Field
M

9.2.1.25

–

>DL Code Information
M

FDD DL  Code Information 9.2.2.14A

–

>Initial DL Transmission Power
O

DL Power
9.2.1.21
Initial power on DPCH or on
F-DPCH
–

>Maximum DL Power
O

DL Power
9.2.1.21
Maximum allowed power on DPCH or on F-DPCH
–

>Minimum DL Power
O

DL Power
9.2.1.21
Minimum allowed power on DPCH or on F-DPCH
–

>Not Used
O

NULL

–

>Transmit Diversity Indicator
O

9.2.2.53

–

>DL Reference Power
O

DL power
9.2.1.21
Power on DPCH or on
F-DPCH
YES
ignore
>RL Specific DCH Information
O

9.2.1.53G

YES
ignore
>Delayed Activation
O

9.2.1.24C

YES
reject
>E-DCH RL Indication
O

9.2.2.13De

YES
reject
>RL Specific E-DCH Information
O

9.2.2.39a

YES
ignore
>Synchronisation Indicator
O

9.2.2.48A

YES
ignore
>F-DPCH Slot Format
O

9.2.2.93

YES
reject
>HS-DSCH Preconfiguration Setup
O

9.2.2.112

YES
ignore
>Non-Serving RL Preconfiguration Setup
O

9.2.2.144

YES
Ignore
>F-TPICH Information
O

9.2.2.160

YES
ignore
>TPC slot position
O

9.2.2.217

YES
ignore
Initial DL DPCH Timing Adjustment Allowed
O

9.2.2.18K

YES
ignore
Serving E-DCH RL
O

9.2.2.48B

YES
reject
Serving Cell Change CFN
O

CFN
9.2.1.7

YES
reject
HS-DSCH Serving Cell Change Information
O

9.2.2.18Eb

YES
reject
E-DPCH Information

0..1


YES
reject
>Maximum Set of E-DPDCHs
M

9.2.2.20C

–

>Puncture Limit
M

9.2.1.50

–

>E-TFCS Information
M

9.2.2.13Dh

–

>E-TTI
M

9.2.2.13Di

–

>E-DPCCH Power Offset
M

9.2.2.13Dj

–

>E-RGCH 2-Index-Step Threshold
M

9.2.2.13Ig

–

>E-RGCH 3-Index-Step Threshold
M

9.2.2.13Ih

–

>HARQ Info for E-DCH
M

9.2.2.18ba

–

>HS-DSCH Configured Indicator
M

9.2.2.18Ca

YES
reject
> Minimum Reduced E-DPDCH Gain Factor
O

9.2.2.114

YES
ignore
E-DCH FDD Information
C-EDPCHInfo 

9.2.2.13Da

YES
reject
Additional HS Cell Information RL Addition

0..<maxNrOfHSDSCH-1>

For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. 
EACH
reject
>HS-PDSCH RL ID
M

RL ID
9.2.1.53

–

>C-ID
M

9.2.1.9

–

>HS-DSCH FDD Secondary Serving Information
M

9.2.2.18Da

–

UE Aggregate Maximum Bit Rate
O

9.2.1.123

YES
ignore
Additional E-DCHCell Information RL Add Req

0..1

For E-DCH on multiple frequencies in this Node B. 
YES
reject
>CHOICE Setup Or Addition Of E-DCH On Secondary UL Frequency
M



–

>>Setup



Used when the secondary UL frequency does not exist or is not configured with E-DCH in the current Node B Communication Context
–

>>>Multicell E-DCH Transport Bearer Mode
M

9.2.2.130

–

>>>Additional E-DCH Cell Information Setup 

1..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.
–

>>>>Additional E-DCH FDD Setup Information
M

9.2.2.131

–

>>Addition



Used when there exist additional E-DCH RLs in the current Node B Communication Context
–

>>>Additional E-DCH Cell Information Addition

1..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.
–

>>>>Additional E-DCH RL Specific Information To Add
M

9.2.2.133

–

>>>>Additional E-DCH FDD Information
O

9.2.2.137

–

>>>>Multicell E-DCH Information
O

9.2.2.140

YES
ignore
Active Pattern Sequence Information
O

9.2.2.A

YES
ignore
UL CLTD Information
O

9.2.2.152

YES
reject
E-DCH Decoupling Indication
O

9.2.2.194

YES
reject
Radio Links without DPCH/F-DPCH Indication
O

9.2.2.201

YES
reject
UL DPCCH2 Information
O

9.2.2.203

YES
reject
Downlink TPC enhancements Information
O

9.2.2.214

YES
reject

Condition
Explanation
EDPCHInfo
This IE shall be present if E-DPCH Information IE is present.

Range Bound
Explanation
maxNrOfRLs
Maximum number of RLs for one UE
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE
maxNrOfEDCH-1
Maximum number of uplink frequencies -1 for E-DCH for one UE

9.1.39.2	TDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
reject
UL CCTrCH Information

0..<maxNrOfCCTrCHs>


GLOBAL
reject
>CCTrCH ID
M

9.2.3.3

–

>UL DPCH Information

0..1

Applicable to 3.84Mcps TDD only
YES
notify
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD DPCH Offset
M

9.2.3.19A

–

>>UL Timeslot Information
M

9.2.3.26C

–

>UL DPCH Information LCR

0..1

Applicable to 1.28Mcps TDD only
YES
notify
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD DPCH Offset
M

9.2.3.19A

–

>>UL Timeslot Information LCR
M

9.2.3.26E

–

>TDD TPC UL Step Size
O

9.2.3.21a
Applicable to 1.28Mcps TDD only
YES
reject
>UL DPCH Information 7.68Mcps

0..1

Applicable to 7.68Mcps TDD only
YES
notify
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD DPCH Offset
M

9.2.3.19A

–

>>UL Timeslot Information 7.68Mcps
M

9.2.3.38

–

DL CCTrCH Information

0..<maxNrOfCCTrCHs>


GLOBAL
reject
>CCTrCH ID
M

9.2.3.3

–

>DL DPCH information

0..1

Applicable to 3.84Mcps TDD only
YES
notify
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD DPCH Offset
M

9.2.3.19A

–

>>DL Timeslot Information
M

9.2.3.4E

–

>DL DPCH information LCR

0..1

Applicable to 1.28Mcps TDD only
YES
notify
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD DPCH Offset
M

9.2.3.19A

–

>>DL Timeslot Information LCR
M

9.2.3.4O

–

>CCTrCH Initial DL Transmission Power
O

DL Power
9.2.1.21

YES
ignore
>TDD TPC DL Step Size
O

9.2.3.21

YES
reject
>CCTrCH Maximum DL Transmission Power
O

DL Power
9.2.1.21

YES
ignore
>CCTrCH Minimum DL Transmission Power
O

DL Power
9.2.1.21

YES
ignore
>DL DPCH information 7.68Mcps

0..1

Applicable to 7.68Mcps TDD only
YES
notify
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD DPCH Offset
M

9.2.3.19A

–

>>DL Timeslot Information 7.68Mcps
M

9.2.3.39

–

RL Information

1


YES
reject
>RL ID
M

9.2.1.53

–

>C-ID
M

9.2.1.9

–

>Frame Offset
M

9.2.1.31

–

>Diversity Control Field
M

9.2.1.25

–

>Initial DL Transmission Power
O

DL Power
9.2.1.21

–

>Maximum DL Power
O

DL Power
9.2.1.21

–

>Minimum DL Power
O

DL Power
9.2.1.21

–

>DL Time Slot ISCP Info
O

9.2.3.4F
Applicable to 3.84Mcps TDD and 7.68Mcps TDD only
–

>DL Time Slot ISCP Info LCR
O

9.2.3.4P
Applicable to 1.28Mcps TDD only
YES
reject
>RL Specific DCH Information
O

9.2.1.53G

YES
ignore
>Delayed Activation
O

9.2.1.24C

YES
reject
>UL Synchronisation Parameters LCR

0..1

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
reject
>>Uplink Synchronisation Step Size
M

9.2.3.26H

–

>>Uplink Synchronisation Frequency
M

9.2.3.26G

–

>UARFCN
O

9.2.1.65
Mandatory for 1.28Mcps TDD when using multiple frequencies. 
Corresponds to Nt (TS 25.105 [15]).
YES
reject
HS-DSCH Information
O

HS-DSCH TDD Information 9.2.3.5F

YES
reject
HS-DSCH RNTI
C-HSDSCHRadioLink

9.2.1.31J

YES
reject
HS-PDSCH RL ID
O

RL ID 9.2.1.53

YES
reject
E-DCH Information

0..1

3.84Mcps TDD only
YES
reject
>E-PUCH Information
M

9.2.3.45

–

>E-TFCS Information TDD
M

9.2.3.46

–

>E-DCH MAC-d Flows Information TDD
M

9.2.3.47

–

>E-DCH Non-scheduled Grant Information TDD
O

9.2.3.48

–

>E-DCH TDD Information
M

9.2.3.49

–

E-DCH Serving RL
O

RL ID
9.2.1.53

YES
reject
E-DCH Information 7.68Mcps

0..1

7.68Mcps TDD only
YES
reject
>E-PUCH Information
M

9.2.3.45

–

>E-TFCS Information TDD
M

9.2.3.46

–

>E-DCH MAC-d Flows Information TDD
M

9.2.3.47

–

>E-DCH Non-scheduled Grant Information 7.68Mcps TDD
O

9.2.3.64

–

>E-DCH TDD Information 7.68Mcps
M

9.2.3.65

–

E-DCH Information 1.28Mcps

0..1

1.28Mcps TDD only
YES 
reject
>E-PUCH Information LCR
M

9.2.3.45a

–

>E-TFCS Information TDD
M

9.2.3.46

–

>E-DCH MAC-d Flows Information TDD
M

9.2.3.47

–

>E-DCH Non-scheduled Grant Information LCR TDD
O

9.2.3.48a

–

>E-DCH TDD Information LCR
M

9.2.3.49a

–

Power Control GAP
O

INTEGER (1..255)
Unit: Number of subframes
Applicable to 1.28Mcps TDD only
YES
ignore
Continuous Packet Connectivity DRX Information LCR
O

9.2.3.93
1.28 Mcps TDD only
YES
reject
HS-DSCH Semi-Persistent scheduling Information LCR
O

9.2.3.96
1.28 Mcps TDD only
YES
reject
E-DCH Semi-Persistent scheduling Information LCR
O

9.2.3.97
1.28 Mcps TDD only
YES
reject
Idle Interval Information
O

9.2.3.102
TDD only
YES
ignore
UE Selected MBMS Service Information
O

9.2.3.104
This IE indicates the Time Slot information and/or TDM information of UE selected MBMS service in the other frequency. For 1.28Mcps TDD only.
YES
ignore
HS-SCCH TPC step size
O

TDD TPC DL Step Size
9.2.3.21
1.28 Mcps TDD only.
This IE is mandatory if DL CCTrCH Information IE and E-DCH Information 1.28Mcps IE are both absent.
YES
ignore
DCH Measurement Occasion Information
O

9.2.3.111
Applicable for 1.28 Mcps TDD.
YES
reject
Multi-Carrier E-DCH Information

0..1

Applicable for Multi-Carrier E-DCH Operation in 1.28 Mcps TDD only
YES
reject
>Multi-carrier E-DCH Transport Bearer Mode LCR
M

9.2.3.113
1.28 Mcps TDD only
–

>Multi-Carrier E-DCH Information LCR
M

9.2.3.112
1.28 Mcps TDD only
–

MU-MIMO Information
O

9.2.3.116
1.28 Mcps TDD only
YES
ignore
UE support of non-rectangular resource allocation
O

ENUMERATED (support)
1.28 Mcps TDD only.
The absence of this IE indicates that the UE does not support the non-rectangular resource allocation.
YES
ignore

Range Bound
Explanation
maxNrOfCCTrCHs
Number of CCTrCH for one UE

Condition
Explanation
HSDSCHRadioLink
The IE shall be present if HS-PDSCH RL ID IE is present

9.1.40	RADIO LINK ADDITION RESPONSE
9.1.40.1	FDD message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
RL Information Response

1..<maxNrOfRLs-1>


EACH
ignore
>RL ID
M

9.2.1.53

–

>RL Set ID
M

9.2.2.39

–

>Received Total Wide Band Power
M

9.2.2.39A

–

>CHOICE Diversity Indication
M



–

>>Combining






>>>RL ID
M

9.2.1.53
Reference RL
–

>>>E-DCH FDD Information Response
O

9.2.2.13Db

YES
ignore
>>Non Combining






>>>DCH Information Response
M

9.2.1.20C

–

>>>E-DCH FDD Information Response
O

9.2.2.13Db

YES
ignore
>SSDT Support Indicator
M

9.2.2.46

–

>DL Power Balancing Activation Indicator
O

9.2.2.12C

YES
ignore
>E-DCH RL Set ID
O

RL Set ID
9.2.2.39

YES
ignore
>E-DCH FDD DL Control Channel Information
O

9.2.2.13Dc

YES
ignore
>Initial DL DPCH Timing Adjustment
O

DL DPCH Timing Adjustment
9.2.2.10A

YES
ignore
> HS-DSCH Preconfiguration Info
O

9.2.2.111

YES
ignore
>Non-Serving RL Preconfiguration Info
O

9.2.2.145

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore
HS-DSCH Serving Cell Change Information Response
O

9.2.2.18Ec

YES
ignore
E-DCH Serving Cell Change Information Response
O

9.2.2.18Ed

YES
ignore
MAC-hs Reset Indicator
O

9.2.1.38Ac

YES
ignore
Additional HS Cell Change Information Response

0..<maxNrOfHSDSCH-1>

For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. 
EACH
ignore
>HS-PDSCH RL ID
M

RL ID 9.2.1.53

–

>HS-DSCH Secondary Serving Cell Change Information Response
M

9.2.2.18Eca

–

Additional E-DCH Cell Information Response RL Add

0..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.
EACH
ignore
> Additional E-DCH FDD  Information Response
O

9.2.2.135

–

>Additional E-DCH Serving Cell Change Information Response
O

E-DCH Serving Cell Change Information Response
9.2.2.18Ed

–


Range Bound
Explanation
maxNrOfRLs
Maximum number of RLs for one UE
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE
maxNrOfEDCH-1
Maximum number of uplink frequencies -1 for E-DCH for one UE

9.1.40.2	TDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
RL Information Response

0..1

Mandatory for 3.84Mcps TDD and 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD.
YES
ignore
>RL ID
M

9.2.1.53

–

>UL Time Slot ISCP Info 
M

9.2.3.26D

–

>UL PhysCH SF Variation
M

9.2.3.26B

–

>DCH Information

0..1


–

>>CHOICE Diversity Indication
M



–

>>>Combining



Indicates whether the old Transport Bearer shall be reused or not


>>>>RL ID
M

9.2.1.53
Reference RL
–

>>>Non Combining






>>>>DCH Information Response
M

9.2.1.20C

–

>DSCH Information Response
O

9.2.3.5b

YES
ignore
>USCH Information Response
O

9.2.3.29

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore
RL Information Response LCR

0..1

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
ignore
>RL ID
M

9.2.1.53

–

>UL Time Slot ISCP Info LCR
M

9.2.3.26F

–

>UL PhysCH SF Variation
M

9.2.3.26B

–

>DCH Information

0..1


–

>>CHOICE Diversity indication
M



–

>>>Combining



Indicates whether the old Transport Bearer shall be reused or not


>>>>RL ID
M

9.2.1.53
Reference RL
–

>>>Non Combining






>>>>DCH Information Response
M

9.2.1.20C

–

>DSCH Information Response
O

9.2.3.5b

YES
ignore
>USCH Information Response
O

9.2.3.29

YES
ignore
HS-DSCH Information Response
O

HS-DSCH TDD Information Response 9.2.3.5G

YES
ignore
E-DCH Information Response
O

E-DCH TDD Information Response 9.2.3.50

YES
ignore
Continuous Packet Connectivity DRX Information Response LCR
O

9.2.3.95
1.28 Mcps TDD only
YES
ignore
HS-DSCH Semi-Persistent scheduling Information Response LCR
O

9.2.3.98
1.28 Mcps TDD only
YES
ignore
E-DCH Semi-Persistent scheduling Information Response LCR
O

9.2.3.99
1.28 Mcps TDD only
YES
ignore
Multi-Carrier E-DCH Information Response LCR
O

9.2.3.114
1.28 Mcps TDD only
YES
ignore
MU-MIMO Information Response
O

9.2.3.118
1.28 Mcps TDD only
 YES
reject
Non-rectangular resource allocation indicator
O

ENUMERATED (activate)
1.28 Mcps TDD only.
The absence of this IE indicates that the non-rectangular resource allocation is not used.
YES
reject
Non-rectangular resource timeslot set
O

BIT STRING (SIZE(7))
1.28 Mcps TDD only.
The absence of this IE means that the specific timeslot(s) of the non-rectangular resource is defined in 3GPP TS 25.222 [34].
This IE indicats which of the timeslot(s) is/are allocated for non-rectangular resource. 
Bit 0 is for timeslot 0. Bit 1 is for timeslot 1. Bit 2 is for timeslot 2. Bit 3 is for timeslot 3. Bit 4 is for timeslot 4. Bit 5 is for timeslot 5. Bit 6 is for timeslot 6.
The value 0 of a bit means the corresponding timeslot is not allocated for non-rectangular resource. The value 1 of a bit means the corresponding timeslot is allocated for non-rectangular resource.
Bit 0 is the first/leftmost bit of the bit string.
YES
reject

9.1.41	RADIO LINK ADDITION FAILURE
9.1.41.1	FDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
CHOICE Cause Level
M



YES
ignore
>General






>>Cause
M

9.2.1.6

–

>RL Specific






>>Unsuccessful RL Information Response

1..<maxNrOfRLs-1>


EACH
ignore
>>>RL ID
M

9.2.1.53

–

>>>Cause
M

9.2.1.6

–

>>Successful RL Information Response

0..<maxNrOfRLs-2>


EACH
ignore
>>>RL ID
M

9.2.1.53

–

>>>RL Set ID
M

9.2.2.39

–

>>>Received Total Wide Band Power
M

9.2.2.39A

–

>>>CHOICE Diversity Indication
M



–

>>>>Combining






>>>>>RL ID
M

9.2.1.53
Reference RL
–

>>>>>E-DCH FDD Information Response
O

9.2.2.13Db

YES
ignore
>>>>Non Combining






>>>>>DCH Information Response
M

9.2.1.20C

–

>>>>>E-DCH FDD Information Response
O

9.2.2.13Db

YES
ignore
>>>SSDT Support Indicator
M

9.2.2.46

–

>>>DL Power Balancing Activation Indicator
O

9.2.2.12C

YES
ignore
>>>E-DCH RL Set ID
O

RL Set ID
9.2.2.39

YES
ignore
>>>E-DCH FDD DL Control Channel Information
O

9.2.2.13Dc

YES
ignore
>>>Initial DL DPCH Timing Adjustment
O

DL DPCH Timing Adjustment
9.2.2.10A

YES
ignore
>>> HS-DSCH Preconfiguration Info
O

9.2.2.111

YES
ignore
>>>Non-Serving RL Preconfiguration Info
O

9.2.2.145

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore
HS-DSCH Serving Cell Change Information Response
O

9.2.2.18Ec

YES
ignore
E-DCH Serving Cell Change Information Response
O

9.2.2.18Ed

YES
ignore
Additional HS Cell Change Information Response

0..<maxNrOfHSDSCH-1>

For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. 
EACH
ignore
>HS-PDSCH RL ID
M

RL ID 9.2.1.53

–

>HS-DSCH Secondary Serving Cell Change Information Response
M

9.2.2.18Eca

–

MAC-hs Reset Indicator
O

9.2.1.38Ac

YES
ignore
Additional E-DCH Cell Information Response RL Add

0..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.. 
EACH
ignore
>Additional E-DCH FDD  Information Response
O

9.2.2.135

–

>Additional E-DCH Serving Cell Change Information Response
O

E-DCH Serving Cell Change Information Response
9.2.2.18Ed

–


Range Bound
Explanation
maxNrOfRLs
Maximum number of RLs for one UE
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE
maxNrOfEDCH-1
Maximum number of uplink frequencies -1 for E-DCH for one UE

9.1.41.2	TDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
CHOICE Cause Level
M



YES
ignore
>General






>>Cause
M

9.2.1.6

–

>RL Specific






>>Unsuccessful RL Information Response

1


YES
ignore
>>>RL ID
M

9.2.1.53

–

>>>Cause
M

9.2.1.6

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.42	RADIO LINK RECONFIGURATION PREPARE
9.1.42.1	FDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
reject
UL DPCH Information

0..1


YES
reject
>UL Scrambling Code
O

9.2.2.59

–

>UL SIR Target
O

UL SIR
9.2.1.67A

–

>Min UL Channelistion Code Length
O

9.2.2.22

–

>Max Number of UL DPDCHs
C-CodeLen

9.2.2.21

–

>Puncture Limit
O

9.2.1.50
For UL
–

>TFCS
O

9.2.1.58

–

>UL DPCCH Slot Format
O

9.2.2.57

–

>Diversity Mode
O

9.2.2.9

–

>Not Used 
O

NULL

–

>Not Used
O

NULL

–

>UL DPDCH Indicator For E-DCH Operation
O

9.2.2.61

YES
reject
DL DPCH Information

0..1


YES
reject
>TFCS
O

9.2.1.58

–

>DL DPCH Slot Format
O

9.2.2.10

–

>TFCI Signalling Mode
O

9.2.2.50

–

>TFCI Presence
C-SlotFormat

9.2.1.57

–

>Multiplexing Position
O

9.2.2.23

–

>Not Used
O

NULL

–

>Not Used
O

NULL

–

>Limited Power Increase
O

9.2.2.18A

–

>DL DPCH Power Information

0..1


YES
reject
>>Power Offset Information

1


–

>>>PO1
M

Power Offset
9.2.2.29
Power offset for the TFCI bits
–

>>>PO2
M

Power Offset
9.2.2.29
Power offset for the TPC bits
–

>>>PO3
M

Power Offset
9.2.2.29
Power offset for the pilot bits
_

>>FDD TPC DL Step Size
M

9.2.2.16

–

>>Inner Loop DL PC Status
M

9.2.2.18B

–

DCHs To Modify
O

DCHs FDD To Modify 9.2.2.4E

YES
reject
DCHs To Add
O

DCH FDD Information 9.2.2.4D

YES
reject
DCHs To Delete

0..<maxNrOfDCHs>


GLOBAL
reject
>DCH ID
M

9.2.1.20

–

RL Information

0..<maxNrOfRLs>


EACH
reject
>RL ID
M

9.2.1.53

–

>DL Code Information
O

FDD DL Code Information 9.2.2.14A

–

>Maximum DL Power
O

DL Power
9.2.1.21
Maximum allowed power on DPCH or on F-DPCH
–

>Minimum DL Power
O

DL Power
9.2.1.21
Minimum allowed power on DPCH or on F-DPCH
–

>Not Used
O

NULL

–

>Not Used
O

NULL

–

>Transmit Diversity Indicator
C-Diversity mode

9.2.2.53

–

>DL Reference Power
O

DL Power
9.2.1.21
Power on DPCH or on
F-DPCH
YES
ignore
>RL Specific DCH Information
O

9.2.1.53G

YES
ignore
>DL DPCH Timing Adjustment
O

9.2.2.10A
Required RL Timing Adjustment 
YES
reject
>Primary CPICH Usage For Channel Estimation
O

9.2.2.33A

YES
ignore
>Secondary CPICH Information Change
O

9.2.2.43A

YES
ignore
>E-DCH RL Indication
O

9.2.2.13De

YES
reject
>RL Specific E-DCH Information
O

9.2.2.39a

YES
ignore
>F-DPCH Slot Format
O

9.2.2.93

YES
reject
>HS-DSCH Preconfiguration Setup
O

9.2.2.112

YES
ignore
>Non-Serving RL Preconfiguration Setup
O

9.2.2.144

YES
ignore
>Non-Serving RL Preconfiguration Removal
O

Non-Serving RL Preconfiguration Setup
9.2.2.144

YES
ignore
>F-TPICH Information Reconf
O

9.2.2.163

YES
ignore
>TPC slot position
O

9.2.2.217

YES
ignore
Transmission Gap Pattern Sequence Information
O

9.2.2.53A

YES
reject
Signalling Bearer Request Indicator
O

9.2.1.55A

YES
reject
HS-DSCH Information
O

HS-DSCH FDD Information 9.2.2.18D

YES
reject
HS-DSCH Information To Modify
O

9.2.1.31H

YES
reject
HS-DSCH MAC-d Flows To Add
O

HS-DSCH MAC-d Flows Information9.2.1.31IA

YES
reject
HS-DSCH MAC-d Flows To Delete
O

9.2.1.31IB

YES
reject
HS-DSCH RNTI
C-HSDSCHRadioLink

9.2.1.31J

YES 
reject
HS-PDSCH RL ID
O

RL ID 9.2.1.53

YES
reject
E-DPCH Information

0..1


YES
reject
>Maximum Set of E-DPDCHs
O

9.2.2.20C

–

>Puncture Limit
O

9.2.1.50

–

>E-TFCS Information
O

9.2.2.13Dh

–

>E-TTI
O

9.2.2.13Di

–

>E-DPCCH Power Offset
O

9.2.2.13Dj

–

>E-RGCH 2-Index-Step Threshold
O

9.2.2.13Ig

–

>E-RGCH 3-Index-Step Threshold
O

9.2.2.13Ih

–

>HARQ Info for E-DCH
O

9.2.2.18ba

–

>HS-DSCH Configured Indicator
O

9.2.2.18Ca

–

> Minimum Reduced E-DPDCH Gain Factor
O

9.2.2.114

YES
ignore
E-DCH FDD Information
O

E-DCH FDD Information 9.2.2.13Da

YES
reject
E-DCH FDD Information To Modify
O

9.2.2.13Df

YES
reject
E-DCH MAC-d Flows To Add
O

E-DCH MAC-d Flows Information 9.2.2.13M

YES
reject
E-DCH MAC-d Flows To Delete
O

9.2.1.73

YES
reject
Serving E-DCH RL
O

9.2.2.48B

YES
reject
F-DPCH Information

0..1


YES
reject
>Power Offset Information

1


–

>>PO2
M

Power Offset
9.2.2.29
This IE shall be ignored by Node B.
_

>FDD TPC DL Step Size
M

9.2.2.16

–

>Limited Power Increase
M

9.2.2.18A

–

>Inner Loop DL PC Status
M

9.2.2.18B

–

Fast Reconfiguration Mode
O

9.2.2.62

YES
ignore
CPC Information

0..1


YES
reject
>Continuous Packet Connectivity DTX-DRX Information
O

9.2.2.66

_

>Continuous Packet Connectivity DTX-DRX Information To Modify
O

9.2.2.67

_

>Continuous Packet Connectivity HS-SCCH less Information
O

9.2.2.68

_

>Continuous Packet Connectivity HS-SCCH less Deactivate Indicator
O

9.2.2.69A

YES
reject
Additional HS Cell Information RL Reconf Prep

0..<maxNrOfHSDSCH-1>

For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. 
EACH
reject
>HS-PDSCH RL ID
M

RL ID
9.2.1.53

–

>C-ID
O

9.2.1.9

–

>HS-DSCH FDD Secondary Serving Information
O

9.2.2.18Da

–

>HS-DSCH FDD Secondary Serving Information To Modify
O

9.2.2.18EB

–

>HS-DSCH Secondary Serving Remove
O

NULL

–

UE Aggregate Maximum Bit Rate
O

9.2.1.123

YES
ignore
Additional E-DCH Cell Information RL Reconf Prep

0..1

For E-DCH on multiple frequencies in this Node B.
YES
reject
>CHOICE Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency

M



–

>>Setup



Used when RLs on the secondary UL frequency does not exist or is not configured with E-DCH in the current Node B Communication Context
–

>>> MultiCell E-DCH Transport Bearer Mode

M

9.2.2.130

–

>>>Additional E-DCH　Cell Information Setup　 

1..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.
–

>>>>Additional E-DCH FDD Setup Information
M

9.2.2.131

–

>>Configuration Change



Used when RLs with additional E-DCH on the secondary UL frequency exist in the current Node B Communication context and the configuration is modified (adding new RLs or modification of existing RLs)
–

>>>Additional E-DCH Cell Information Configuration Change 

1..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.
–

>>>> Additional E-DCH Configuration Change Information
M

9.2.2.136

–

>>Removal



Used when all RLs on the indicated secondary UL frequency is removed.
–

>>>Additional E-DCH Cell Information Removal

1..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.
–

>>>>RL on Secondary UL Frequency
M

ENUMERATED (Remove, ...)
Removal of all RL on secondary UL frequency
–

UL CLTD Information Reconf
O

9.2.2.151

YES
reject
E-DCH Decoupling Indication
O

9.2.2.194

YES
reject
DCH Enhancements Information Reconf
O

9.2.2.195

YES
reject
Radio Links without DPCH/F-DPCH Indication
O

9.2.2.201

YES
reject
UL DPCCH2 Reconfiguration
O

9.2.2.202

YES
reject
Downlink TPC enhancements Reconf
O

9.2.2.215

YES
reject
Improved Synchronized RRC Indicator
O

9.2.1.129

YES
ignore

Condition
Explanation
CodeLen
The IE shall be present if the Min UL Channelisation Code Length IE is equals to 4.
SlotFormat
The IE shall be present if the DL DPCH Slot Format IE is equal to any of the values from 12 to 16.
Diversity mode
The IE shall be present if the Diversity Mode IE is present in the UL DPCH Information IEand is not set to "none".
HSDSCH Radio Link
The IE shall be present if HS-PDSCH RL ID IE is present.

Range Bound
Explanation
maxNrOfDCHs
Maximum number of DCHs for a UE
maxNrOfRLs
Maximum number of RLs for a UE
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE
maxNrOfEDCH-1
Maximum number of uplink frequencies -1 for E-DCH for one UE

9.1.42.2	TDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
reject
UL CCTrCH To Add

0..<maxNrOfCCTrCHs>


GLOBAL
reject
>CCTrCH ID
M

9.2.3.3

–

>TFCS
M

9.2.1.58

–

>TFCI Coding
M

9.2.3.22

–

>Puncture Limit
M

9.2.1.50

–

>UL DPCH To Add Per RL

0..<maxNrOfRLs>

See note 1 below
–

>>UL DPCH Information

0..1

Applicable to 3.84Mcps TDD only
YES
reject
>>>Repetition Period
M

9.2.3.16

–

>>>Repetition Length
M

9.2.3.15

–

>>>TDD DPCH Offset
M

9.2.3.19A

–

>>>UL Timeslot Information
M

9.2.3.26C

–

>>UL DPCH Information LCR

0..1

Applicable to 1.28Mcps TDD only
YES
reject
>>>Repetition Period
M

9.2.3.16

–

>>>Repetition Length
M

9.2.3.15

–

>>>TDD DPCH Offset
M

9.2.3.19A

–

>>>UL Timeslot Information LCR
M

9.2.3.26E

–

>>UL SIR Target
O

UL SIR
9.2.1.67A
Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD
YES
reject
>>TDD TPC UL Step Size
O

9.2.3.21a
Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
reject
>>RL ID
O

9.2.1.53

YES
ignore
>>UL DPCH Information 7.68Mcps 

0..1

Applicable to 7.68Mcps TDD only
YES
reject
>>>Repetition Period
M

9.2.3.16

–

>>>Repetition Length
M

9.2.3.15

–

>>>TDD DPCH Offset
M

9.2.3.19A

–

>>>UL Timeslot Information 7.68Mcps 
M

9.2.3.38

–

UL CCTrCH To Modify

0..<maxNrOfCCTrCHs>


GLOBAL
reject
>CCTrCH ID
M

9.2.3.3

–

>TFCS
O

9.2.1.58

–

>TFCI Coding
O

9.2.3.22

–

>Puncture Limit
O

9.2.1.50

–

>UL DPCH To Modify Per RL

0..<maxNrOfRLs>

See note 1 below
–

>>UL DPCH To Add

0..1

Applicable to 3.84Mcps TDD only
YES
reject
>>>Repetition Period
M

9.2.3.16

–

>>>Repetition Length
M

9.2.3.15

–

>>>TDD DPCH Offset
M

9.2.3.19A

–

>>>UL Timeslot Information
M

9.2.3.26C

–

>>UL DPCH To Modify

0..1


YES
reject
>>>Repetition Period
O

9.2.3.16

–

>>>Repetition Length
O

9.2.3.15

–

>>>TDD DPCH Offset
O

9.2.3.19A

–

>>>UL Timeslot Information

0..<maxNrOfULTSs>

Applicable to 3.84Mcps TDD only
–

>>>>Time Slot
M

9.2.3.23

–

>>>>Midamble Shift And Burst Type
O

9.2.3.7

–

>>>>TFCI Presence
O

9.2.1.57

–

>>>>UL Code Information

0..<maxNrOfDPCHs>


–

>>>>>DPCH ID
M

9.2.3.5

–

>>>>>TDD Channelisation Code
O

9.2.3.19

–

>>>UL Timeslot Information LCR

0..<maxNrOfULTSLCRs>

Applicable to 1.28Mcps TDD only
GLOBAL
reject
>>>>Time Slot LCR
M

9.2.3.24A

–

>>>>Midamble Shift LCR
O

9.2.3.7A



>>>>TFCI Presence
O

9.2.1.57

–

>>>>UL Code Information LCR

0..<maxNrOfDPCHLCRs>


–

>>>>>DPCH ID
M

9.2.3.5

–

>>>>>TDD Channelisation Code LCR
O

9.2.3.19a

–

>>>>>TDD UL DPCH Time Slot Format LCR
O

9.2.3.21C

YES
reject
>>>>PLCCH Information
O

9.2.3.31

YES
reject
>>>UL Timeslot Information 7.68Mcps

0..<maxNrOfULTSs>

Applicable to 7.68Mcps TDD only
GLOBAL
reject
>>>>Time Slot
M

9.2.3.23

–

>>>>Midamble Shift And Burst Type 7.68Mcps 
O

9.2.3.35

–

>>>>TFCI Presence
O

9.2.1.57

–

>>>>UL Code Information 7.68Mcps

0..<maxNrOfDPCHs>


–

>>>>>DPCH ID
M

9.2.3.5

–

>>>>>TDD Channelisation Code 7.68Mcps 
O

9.2.3.34

–

>>UL DPCH To Delete

0..<maxNrOfDPCHs>


GLOBAL
reject
>>>DPCH ID
M

9.2.3.5

–

>>UL DPCH To Add LCR

0..1

Applicable to 1.28Mcps TDD only
YES
reject
>>>Repetition Period
M

9.2.3.16

–

>>>Repetition Length
M

9.2.3.15

–

>>>TDD DPCH Offset
M

9.2.3.19A

–

>>>UL Timeslot Information LCR
M

9.2.3.26E

–

>>UL SIR Target
O

UL SIR
9.2.1.67A
Applicable to 1.28Mcps TDD only
YES
reject
>>TDD TPC UL Step Size
O

9.2.3.21a
Applicable to 1.28Mcps TDD only
YES
reject
>>RL ID
O

9.2.1.53

YES
ignore
>>UL DPCH To Add 7.68Mcps 

0..1

Applicable to 7.68Mcps TDD only
YES
reject
>>>Repetition Period
M

9.2.3.16

–

>>>Repetition Length
M

9.2.3.15

–

>>>TDD DPCH Offset
M

9.2.3.19A

–

>>>UL Timeslot Information 7.68Mcps 
M

9.2.3.38

–

UL CCTrCH To Delete

0..<maxNrOfCCTrCHs>


GLOBAL
reject
>CCTrCH ID
M

9.2.3.3

–

DL CCTrCH To Add

0..<maxNrOfCCTrCHs>


GLOBAL
reject
>CCTrCH ID
M

9.2.3.3

–

>TFCS
M

9.2.1.58

–

>TFCI Coding
M

9.2.3.22

–

>Puncture Limit
M

9.2.1.50

–

>TPC CCTrCH List

0..<maxNrOfCCTrCHs>

List of uplink CCTrCH which provide TPC
–

>>TPC CCTrCH ID 
M

CCTrCH ID
9.2.3.3

–

>DL DPCH To Add Per RL

0..<maxNrOfRLs>

See Note 1 below
–

>>DL DPCH Information

0..1

Applicable to 3.84Mcps TDD only
YES
reject
>>>Repetition Period
M

9.2.3.16

–

>>>Repetition Length
M

9.2.3.15

–

>>>TDD DPCH Offset
M

9.2.3.19A

–

>>>DL Timeslot Information
M

9.2.3.4E

–

>>DL DPCH Information LCR

0..1

Applicable to 1.28Mcps TDD only
YES
reject
>>>Repetition Period
M

9.2.3.16

–

>>>Repetition Length
M

9.2.3.15

–

>>>TDD DPCH Offset
M

9.2.3.19A

–

>>>DL Timeslot Information LCR
M

9.2.3.4O

–

>>CCTrCH Initial DL Transmission Power
O

DL Power
9.2.1.21

YES
ignore
>>TDD TPC DL Step Size
O

9.2.3.21

YES
reject
>>CCTrCH Maximum DL Transmission Power
O

DL Power
9.2.1.21

YES
ignore
>>CCTrCH Minimum DL Transmission Power
O

DL Power
9.2.1.21

YES
ignore
>>RL ID
O

9.2.1.53

YES
ignore
>>DL DPCH Information 7.68Mcps 

0..1

Applicable to 7.68Mcps TDD only
YES
reject
>>>Repetition Period
M

9.2.3.16

–

>>>Repetition Length
M

9.2.3.15

–

>>>TDD DPCH Offset
M

9.2.3.19A

–

>>>DL Timeslot Information 7.68Mcps 
M

9.2.3.39

–

DL CCTrCH To Modify

0..<maxNrOfCCTrCHs>


GLOBAL
reject
>CCTrCH ID
M

9.2.3.3

–

>TFCS
O

9.2.1.58

–

>TFCI Coding
O

9.2.3.22

–

>Puncture Limit
O

9.2.1.50

–

>TPC CCTrCH List

0..<maxNrOfCCTrCHs>

List of uplink CCTrCH which provide TPC
–

>>TPC CCTrCH ID 
M

CCTrCH ID
9.2.3.3

–

>DL DPCH To Modify Per RL

0..<maxNrOfRLs>

See Note 1 below
–

>>DL DPCH To Add

0..1

Applicable to 3.84Mcps TDD only
YES
reject
>>>Repetition Period
M

9.2.3.16

–

>>>Repetition Length
M

9.2.3.15

–

>>>TDD DPCH Offset
M

9.2.3.19A

–

>>>DL Timeslot Information
M

9.2.3.4E

–

>>DL DPCH To Modify

0..1


YES
reject
>>>Repetition Period
O

9.2.3.16

–

>>>Repetition Length
O

9.2.3.15

–

>>>TDD DPCH Offset
O

9.2.3.19A

–

>>>DL Timeslot Information

0..<maxNrOfDLTSs>

Applicable to 3.84Mcps TDD only
–

>>>>Time Slot
M

9.2.3.23

–

>>>>Midamble Shift And Burst Type
O

9.2.3.7

–

>>>>TFCI Presence
O

9.2.1.57

–

>>>>DL Code Information

0..<maxNrOfDPCHs>


–

>>>>>DPCH ID
M

9.2.3.5

–

>>>>>TDD Channelisation Code
O

9.2.3.19

–

>>>DL Timeslot Information LCR

0..<maxNrOfDLTSLCRs>

Applicable to 1.28Mcps TDD only
GLOBAL
reject
>>>>Time Slot LCR
M

9.2.3.24A

–

>>>>Midamble Shift LCR
O

9.2.3.7A



>>>>TFCI Presence
O

9.2.1.57

–

>>>>DL Code Information LCR

0..<maxNrOfDPCHLCRs>


–

>>>>>DPCH ID
M

9.2.3.5

–

>>>>>TDD Channelisation Code LCR
O

9.2.3.19a

–

>>>>>TDD DL DPCH Time Slot Format LCR
O

9.2.3.19D

YES
reject
>>>>Maximum DL Power to Modify LCR 
O

DL Power
9.2.1.21
Maximum allowed power on DPCH 
YES
ignore
>>>>Minimum DL Power to Modify LCR
O

DL Power
9.2.1.21
Minimum allowed power on DPCH
YES
ignore
>>>DL Timeslot Information 7.68Mcps 

0..<maxNrOfDLTSs>

Applicable to 7.68Mcps TDD only
GLOBAL
reject
>>>>Time Slot
M

9.2.3.23

–

>>>>Midamble Shift And Burst Type 7.68Mcps 
O

9.2.3.35

–

>>>>TFCI Presence
O

9.2.1.57

–

>>>>DL Code Information 7.68Mcps 

0..<maxNrOfDPCHs768>


–

>>>>>DPCH ID 7.68Mcps
M

9.2.3.42

–

>>>>>TDD Channelisation Code 7.68Mcps 
O

9.2.3.34

–

>>DL DPCH To Delete

0..<maxNrOfDPCHs>


GLOBAL
reject
>>>DPCH ID
M

9.2.3.5

–

>>DL DPCH To Add LCR

0..1

Applicable to 1.28Mcps TDD only
YES
reject
>>>Repetition Period
M

9.2.3.16

–

>>>Repetition Length
M

9.2.3.15

–

>>>TDD DPCH Offset
M

9.2.3.19A

–

>>>DL Timeslot Information LCR
M

9.2.3.4O

–

>>TDD TPC DL Step Size
O

9.2.3.21

YES
reject
>>Maximum CCTrCH DL Power to Modify
O

DL Power
9.2.1.21

YES
ignore
>>Minimum CCTrCH DL Power to Modify
O

DL Power
9.2.1.21

YES
ignore
>>RL ID
O

9.2.1.53

YES
ignore
>>DL DPCH To Add 7.68Mcps 

0..1

Applicable to 7.68Mcps TDD only
YES
reject
>>>Repetition Period
M

9.2.3.16

–

>>>Repetition Length
M

9.2.3.15

–

>>>TDD DPCH Offset
M

9.2.3.19A

–

>>>DL Timeslot Information 7.68Mcps 
M

9.2.3.39

–

DL CCTrCH To Delete

0..<maxNrOfCCTrCHs>


GLOBAL
reject
>CCTrCH ID
M

9.2.3.3

–

DCHs To Modify
O

DCHs TDD To Modify 9.2.3.4D

YES
reject
DCHs To Add
O

DCH TDD Information 9.2.3.4C

YES
reject
DCHs To Delete

0..<maxNrOfDCHs>


GLOBAL
reject
>DCH ID
M

9.2.1.20

–

DSCH To Modify

0..<maxNrOfDSCHs>


GLOBAL
reject
>DSCH ID
M

9.2.3.5a

–

>CCTrCH ID
O

9.2.3.3
DL CCTrCH in which the DSCH is mapped
–

>Transport Format Set
O

9.2.1.59

–

>Allocation/Retention Priority
O

9.2.1.1A

–

>Frame Handling Priority
O

9.2.1.30

–

>ToAWS
O

9.2.1.61

–

>ToAWE
O

9.2.1.60

–

>Transport Bearer Request Indicator
M

9.2.1.62A

–

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
DSCH To Add
O

DSCH TDD Information 9.2.3.5A

YES
reject
DSCH To Delete

0..<maxNrOfDSCHs>


GLOBAL
reject
>DSCH ID
M

9.2.3.5a

–

USCH To Modify

0..<maxNrOfUSCHs>


GLOBAL
reject
>USCH ID
M

9.2.3.27

–

>Transport Format Set
O

9.2.1.59

–

>Allocation/Retention Priority
O

9.2.1.1A

–

>CCTrCH ID
O

9.2.3.3
UL CCTrCH in which the USCH is mapped
–

>Transport Bearer Request Indicator
M

9.2.1.62A

–

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>TNL QoS
O

9.2.1.58A

YES
ignore
USCH To Add
O

USCH Information 9.2.3.28

YES
reject
USCH To Delete

0..<maxNrOfUSCHs>


GLOBAL
reject
>USCH ID
M

9.2.3.27

–

RL Information

0..<maxNrOfRLs>

See Note 1 below
YES
reject
>RL ID
M

9.2.1.53

–

>Maximum Downlink Power 
O

DL Power
9.2.1.21

–

>Minimum Downlink Power 
O

DL Power
9.2.1.21

–

>Initial DL Transmission Power
O

DL Power
9.2.1.21

YES
ignore
>RL Specific DCH Information
O

9.2.1.53G

YES
ignore
>UL Synchronisation Parameters LCR

0..1

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
ignore
>>Uplink Synchronisation Step Size
M

9.2.3.26H

–

>>Uplink Synchronisation Frequency
M

9.2.3.26G

–

>DL Time Slot ISCP Info LCR
O

9.2.3.4P
Applicable to 1.28Mcps TDD only
YES
ignore
>UARFCN
O

9.2.1.65
Applicable to 1.28Mcps TDD when using multiple frequencies. 
Corresponds to Nt (TS 25.105 [15]).
YES
reject
Signalling Bearer Request Indicator
O

9.2.1.55A

YES
reject
HS-DSCH Information
O

HS-DSCH TDD Information 9.2.3.5F

YES
reject
HS-DSCH Information To Modify
O

9.2.1.31H

YES
reject
HS-DSCH MAC-d Flows To Add
O

HS-DSCH MAC-d Flows Information 9.2.1.31IA

YES
reject
HS-DSCH MAC-d Flows To Delete
O

9.2.1.31IB

YES
reject
HS-DSCH RNTI
C-HSDSCHRadioLink

9.2.1.31J

YES
reject
HS-PDSCH RL ID
O

RL ID 9.2.1.53

YES
reject
PDSCH-RL-ID
O

RL ID
9.2.1.53

YES
ignore
E-DCH Information

0..1

3.84Mcps TDD only
YES
reject
>E-PUCH Information
O

9.2.3.45

–

>E-TFCS Information TDD
O

9.2.3.46

–

>E-DCH MAC-d Flows to Add
O

E-DCH MAC-d Flows Information TDD 9.2.3.47

–

>E-DCH MAC-d Flows to Delete
O

9.2.1.73

–

>E-DCH Non-scheduled Grant Information TDD
O

9.2.3.48

–

>E-DCH TDD Information
O

9.2.3.49

–

>E-DCH TDD Information to Modify
O

9.2.3.52

–

E-DCH Serving RL
O

RL ID
9.2.1.53

YES
reject
E-DCH Information 7.68Mcps

0..1

7.68Mcps TDD only
YES
reject
>E-PUCH Information
O

9.2.3.45

–

>E-TFCS Information TDD
O

9.2.3.46

–

>E-DCH MAC-d Flows to Add
O

E-DCH MAC-d Flows Information TDD 9.2.3.47

–

>E-DCH MAC-d Flows to Delete
O

9.2.1.73

–

>E-DCH Non-scheduled Grant Information 7.68Mcps TDD
O

9.2.3.64

–

>E-DCH TDD Information 7.68Mcps
O

9.2.3.65

–

>E-DCH TDD Information to Modify
O

9.2.3.52

–

E-DCH Information 1.28Mcps

0..1

1.28Mcps TDD only
YES 
reject
>E-PUCH Information LCR
O

9.2.3.45a

–

>E-TFCS Information TDD
O

9.2.3.46

–

>E-DCH MAC-d Flows to Add
O

E-DCH MAC-d Flows Information TDD 9.2.3.47

–

>E-DCH MAC-d Flows to Delete
O

9.2.1.73

–

>E-DCH Non-scheduled Grant Information LCR TDD
O

9.2.3.48a

–

>E-DCH TDD Information LCR 
O

9.2.3.49a

–

>E-DCH TDD Information to Modify
O

9.2.3.52

–

Power Control GAP
O

INTEGER (1..255)
Unit: Number of subframes
Applicable to 1.28Mcps TDD only
YES
ignore
CPC Information

0..1

1.28Mcps TDD only
YES
reject
>Continuous Packet Connectivity DRX Information LCR
O

9.2.3.93

_

>Continuous Packet Connectivity DRX Information To Modify LCR
O

9.2.3.94

_

>HS-DSCH Semi-Persistent scheduling Information LCR
O

9.2.3.96

_

>HS-DSCH Semi-Persistent scheduling Information to modify LCR
O

9.2.3.96a

_

>HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR
O

9.2.3.100

_

>E-DCH Semi-Persistent scheduling Information LCR
O

9.2.3.97

_

>E-DCH Semi-Persistent scheduling Information to modify LCR
O

9.2.3.97a

_

>E-DCH Semi-Persistent scheduling Deactivate Indicator LCR
O

9.2.3.101

_

Idle Interval Information
O

9.2.3.102
TDD only
YES
Ignore
UE Selected MBMS Service Information
O

9.2.3.104
This IE indicates the Time Slot information and/or TDM information of UE selected MBMS service in the other frequency. For 1.28Mcps TDD only.
YES
ignore
HS-SCCH TPC step size
O

TDD TPC DL Step Size
9.2.3.21
1.28 Mcps TDD only.
YES
ignore
DCH Measurement Occasion Information
O

9.2.3.111
Applicable for 1.28 Mcps TDD.
YES
reject
HS-DSCH-RNTI for FACH
O

HS-DSCH RNTI
9.2.1.31J
1.28 Mcps TDD only
YES
ignore
Multi-Carrier E-DCH Information Reconf

0..1

Applicable for Multi-Carrier E-DCH Operation for 1.28 Mcps TDD only
YES
reject
>CHOICE continue,Setup or Change
M



–

   >>continue



Used when a RL with Multi-carrier E-DCH configurations exists in the current Node B Communication context and the configuration keeps unchanged.
–

>>Setup



Used when the Multi-carrier E-DCH is not configured for this RL in the current Node B Communication Context
–

>>>Multi-Carrier E-DCH Transport Bearer Mode LCR
M

9.2.3.113

–

>>>UL Multi-Carrier E-DCH Information LCR
M

9.2.3.112

–

>>change



Used when a RL with Multi-carrier E-DCH configurations exists in the current Node B Communication context and the configuration is modified (adding new frequencies, modification of existing configuration or removing existing frequencies)
–

>>>Multi-Carrier E-DCH Transport Bearer Mode LCR
O

9.2.3.113

–

>>>UL Multi-Carrier E-DCH Information LCR
O

9.2.3.112

–

>>>Removal UL Multi-Carrier info

0..<maxNrOfULCarriersLCR-1>


–

>>>>UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
–

MU-MIMO Information
O

9.2.3.116
1.28 Mcps TDD only
YES
ignore
MU-MIMO Information To Reconfigure
O

9.2.3.117
1.28 Mcps TDD only
YES
ignore
UE support of non-rectangular resource allocation
O

ENUMERATED (support)
1.28 Mcps TDD only.
The absence of this IE indicates that the UE does not support the non-rectangular resource allocation.
YES
ignore
NOTE 1:	This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxNrOfRLs are represented by separate ASN.1 structures with different criticalities.

Condition
Explanation
HSDSCHRadioLink
The IE shall be present if HS-PDSCH RL ID IE is present.

Range Bound
Explanation
maxNrOfDCHs
Maximum number of DCHs for a UE
maxNrOfCCTrCHs
Maximum number of CCTrCHs for a UE
maxNrOfDPCHs
Maximum number of DPCHs in one CCTrCH for 3.84Mcps TDD. Maximum number of uplink DPCHs in one CCTrCH for 7.68Mcps TDD
maxNrOfDPCHLCRs
Maximum number of DPCHs in one CCTrCH for 1.28Mcps TDD
maxNrOfDPCHs768
Maximum number of downlink DPCHs in one CCTrCH for 7.68Mcps TDD
maxNrOfDSCHs
Maximum number of DSCHs for one UE
maxNrOfUSCHs
Maximum number of USCHs for one UE
maxNrOfDLTSs
Maximum number of Downlink time slots per Radio Link for 3.84Mcps TDD
maxNrOfDLTSLCRs
Maximum number of Downlink time slots per Radio Link for 1.28Mcps TDD
maxNrOfULTSs
Maximum number of Uplink time slots per Radio Link for 3.84Mcps TDD
maxNrOfULTSLCRs
Maximum number of Uplink time slots per Radio Link for 1.28Mcps TDD
maxNrOfRLs
Maximum number of RLs for one UE
maxNrOfULCarriersLCR-1
Maximum number of uplink frequencis in Multi-Carrier E-DCH Operation

9.1.43	RADIO LINK RECONFIGURATION READY
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
RL Information Response

0..<maxNrOfRLs>


EACH
ignore
>RL ID
M

9.2.1.53

–

>DCH Information Response
O

9.2.1.20C

YES
ignore
>DSCH Information Response
O

9.2.3.5b
TDD only
YES
ignore
>USCH Information Response
O

9.2.3.29
TDD only
YES
ignore
>Not Used
O

NULL

–

>DL Power Balancing Updated Indicator
O

9.2.2.12D

YES
ignore
>E-DCH RL Set ID
O

RL Set ID
9.2.2.39

YES
ignore
>E-DCH FDD DL Control Channel Information
O

9.2.2.13Dc

YES
ignore
>E-DCH FDD Information Response
O

9.2.2.13Db

YES
ignore
>HS-DSCH Preconfiguration Info
O

9.2.2.111

YES
ignore
>Non-Serving RL Preconfiguration Info
O

9.2.2.145

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore
Target Communication Control Port ID
O

Communication Control Port ID 9.2.1.15

YES
ignore
HS-DSCH FDD Information Response
O

9.2.2.18E
FDD only
YES
ignore
HS-DSCH TDD Information Response
O

9.2.3.5G
TDD only
YES
ignore
E-DCH TDD Information Response
O

E-DCH TDD Information Response 9.2.3.50
TDD only
YES
ignore
MAC-hs Reset Indicator
O

9.2.1.38Ac

YES
ignore
Fast Reconfiguration Permission
O

9.2.2.63
FDD only
YES
ignore
Continuous Packet Connectivity HS-SCCH less Information Response
O

9.2.2.69
FDD only
YES
ignore
Additional HS Cell Information Response

0..<maxNrOfHSDSCH-1>

For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. 
EACH
ignore
>HS-PDSCH RL ID
M

RL ID 9.2.1.53

–

>HS-DSCH FDD Secondary Serving Information Response
M

9.2.2.18EA
FDD only
–

Continuous Packet Connectivity DRX Information Response LCR
O

9.2.3.95
1.28 Mcps TDD only
YES
ignore
HS-DSCH Semi-Persistent scheduling Information Response LCR
O

9.2.3.98
1.28 Mcps TDD only
YES
ignore
E-DCH Semi-Persistent scheduling Information Response LCR
O

9.2.3.99
1.28 Mcps TDD only
YES
ignore
Additional E-DCHCell Information Response RLReconf

0..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. 
EACH
ignore
>Additional E-DCH FDD Information Response
O

9.2.2.135
For new E-DCH Radio Links on secondary uplink frequency
–

>Additional Modified E-DCH FDD Information Response
O

9.2.2.141

–

E-RNTI for FACH
O

E-RNTI
9.2.1.75
1.28 Mcps TDD only
YES
ignore
Multi-Carrier E-DCH Information Response LCR
O

9.2.3.114
1.28 Mcps TDD only
YES
ignore
MU-MIMO Information Response
O

9.2.3.118
1.28 Mcps TDD only
YES
reject
Non-rectangular resource allocation indicator
O

ENUMERATED (activate)
1.28 Mcps TDD only.
The absence of this IE indicates that the non-rectangular resource allocation is not used.
YES
reject
Non-rectangular resource timeslot set
O

BIT STRING (SIZE(7))
1.28 Mcps TDD only.
The absence of this IE means that the specific timeslot(s) of the non-rectangular resource is defined in 3GPP TS 25.222 [34].
This IE indicats which of the timeslot(s) is/are allocated for non-rectangular resource. 
Bit 0 is for timeslot 0. Bit 1 is for timeslot 1. Bit 2 is for timeslot 2. Bit 3 is for timeslot 3. Bit 4 is for timeslot 4. Bit 5 is for timeslot 5. Bit 6 is for timeslot 6.
The value 0 of a bit means the corresponding timeslot is not allocated for non-rectangular resource. The value 1 of a bit means the corresponding timeslot is allocated for non-rectangular resource.
Bit 0 is the first/leftmost bit of the bit string.
YES
reject


Range Bound
Explanation
maxNrOfRLs
Maximum number of RLs for a UE
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE
maxNrOfEDCH-1
Maximum number of uplink frequencies -1 for E-DCH for one UE

9.1.44	RADIO LINK RECONFIGURATION FAILURE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
CHOICE Cause Level
M



YES
ignore
>General






>>Cause
M

9.2.1.6

YES
ignore
>RL Specific






>>RLs Causing Reconfiguration Failure

0..<maxNrOfRLs>


EACH
ignore
>>>RL ID
M

9.2.1.53

–

>>>Cause
M

9.2.1.6

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

Range Bound
Explanation
maxNrOfRLs
Maximum number of RLs for a UE

9.1.45	RADIO LINK RECONFIGURATION COMMIT
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
ignore
CFN
M

9.2.1.7

YES
ignore
Active Pattern Sequence Information
O

9.2.2.A
FDD only
YES
ignore
Fast Reconfiguration Mode
O

9.2.2.62
FDD only
YES
reject
Activation Delay
O

9.2.2.210
FDD only
YES
reject

9.1.46	RADIO LINK RECONFIGURATION CANCEL
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
ignore

9.1.47	RADIO LINK RECONFIGURATION REQUEST
9.1.47.1	FDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
reject
UL DPCH Information

0..1


YES
reject
>TFCS
O

9.2.1.58
For the UL.
–

>UL DPDCH Indicator For E-DCH Operation
O

9.2.2.61

YES
reject
DL DPCH Information

0..1


YES
reject
>TFCS
O

9.2.1.58
For the DL.
–

>TFCI Signalling Mode
O

9.2.2.50

–

>Limited Power Increase
O

9.2.2.18A

–

DCHs To Modify
O

DCHs FDD To Modify 9.2.2.4E

YES
reject
DCHs To Add
O

DCH FDD Information 9.2.2.4D

YES
reject
DCHs To Delete

0..<maxNrOfDCHs>


GLOBAL
reject
>DCH ID
M

9.2.1.20

–

Radio Link Information

0..<maxNrOfRLs>


EACH
reject
>RL ID
M

9.2.1.53

–

>Maximum DL Power
O

DL Power
9.2.1.21
Maximum allowed power on DPCH or on F-DPCH
–

>Minimum DL Power
O

DL Power
9.2.1.21
Minimum allowed power on DPCH or on F-DPCH
–

>DL Code Information
C-SF/2

FDD DL Code Information 9.2.2.14A

–

>DL Reference Power
O

DL Power
9.2.1.21
Power on DPCH or on F-DPCH
YES
ignore
>RL Specific DCH Information
O

9.2.1.53G

YES
ignore
>E-DCH RL Indication
O

9.2.2.13De

YES
reject
>RL Specific E-DCH Information
O

9.2.2.39a

YES
ignore
>F-DPCH Slot Format
O

9.2.2.93

YES
reject
>HS-DSCH Preconfiguration Setup
O

9.2.2.112

YES
ignore
>Non-Serving RL Preconfiguration Setup
O

9.2.2.144

YES
ignore
>Non-Serving RL Preconfiguration Removal
O

Non-Serving RL Preconfiguration Setup
9.2.2.144

YES
ignore
>F-TPICH Information Reconf
O

9.2.2.163

YES
ignore
>TPC slot position
O

9.2.2.217

YES
ignore
Transmission Gap Pattern Sequence Information
O

9.2.2.53A

YES
reject
Signalling Bearer Request Indicator
O

9.2.1.55A

YES
reject
HS-DSCH Information
O

HS-DSCH FDD Information 9.2.2.18D

YES
reject
HS-DSCH Information To Modify Unsynchronised
O

9.2.1.31HA

YES
reject
HS-DSCH MAC-d Flows To Add
O

HS-DSCH MAC-d Flows Information 9.2.1.31IA

YES
reject
HS-DSCH MAC-d Flows To Delete
O

9.2.1.31IB

YES
reject
HS-DSCH RNTI
C-HSDSCHRadioLink

9.2.1.31J

YES
reject
HS-PDSCH RL ID
O

RL ID 9.2.1.53

YES
reject
E-DPCH Information

0..1


YES
reject
>Maximum Set of E-DPDCHs
O

9.2.2.20C

–

>Puncture Limit
O

9.2.1.50

–

>E-TFCS Information 
O

9.2.2.13Dh

–

>E-TTI
O

9.2.2.13Di

–

>E-DPCCH Power Offset
O

9.2.2.13Dj

–

>E-RGCH 2-Index-Step Threshold
O

9.2.2.13Ig

–

>E-RGCH 3-Index-Step Threshold
O

9.2.2.13Ih

–

>HARQ Info for E-DCH
O

9.2.2.18ba

–

>HS-DSCH Configured Indicator
O

9.2.2.18Ca

–

> Minimum Reduced E-DPDCH Gain Factor
O

9.2.2.114

YES
ignore
E-DCH FDD Information
O

E-DCH FDD Information 9.2.2.13Da

YES
reject
E-DCH FDD Information To Modify
O

9.2.2.13Df

YES
reject
E-DCH MAC-d Flows To Add
O

E-DCH FDD MAC-d Flows Information 9.2.2.13M

YES
reject
E-DCH MAC-d Flows To Delete
O

9.2.1.73

YES
reject
Serving E-DCH RL
O

9.2.2.48B

YES
reject
CPC Information

0..1


YES
reject
>Continuous Packet Connectivity DTX-DRX Information
O

9.2.2.66

–

>Continuous Packet Connectivity DTX-DRX Information To Modify
O

9.2.2.67

–

>Continuous Packet Connectivity HS-SCCH less Information
O

9.2.2.68

–

>Continuous Packet Connectivity HS-SCCH less Deactivate Indicator
O

9.2.2.69A

    YES
reject
No of Target Cell HS-SCCH Order  
O

INTEGER (1..30)

    YES
ignore
Additional HS Cell Information RL Reconf Req

0..<maxNrOfHSDSCH-1>

For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. 
EACH
reject
>HS-PDSCH RL ID
M

RL ID
9.2.1.53

–

>C-ID
O

9.2.1.9

–

>HS-DSCH FDD Secondary Serving Information
O

9.2.2.18Da

–

>HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised
O

9.2.2.18EC

–

>HS-DSCH Secondary Serving Remove
O

NULL

–

UE Aggregate Maximum Bit Rate
O

9.2.1.123

YES
ignore
Additional E-DCHCell Information RL Reconf Req

0..1

For E-DCH on multiple frequencies in this Node B.
YES
reject
>CHOICE Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency

M



YES
reject
>>Setup



Used when RLs on the secondary UL frequency does not exist or is not configured with E-DCH in the current Node B Communication Context
–

>>> MultiCell E-DCH Transport Bearer Mode

M

9.2.2.130

–

>>>Additional E-DCH　Cell Information Setup　 

1..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.
–

>>>>Additional E-DCH FDD Setup Information
M

9.2.2.131

–

>>Configuration Change



Used when RLs with additional E-DCH on the secondary UL frequency exist in the current Node B Communication context and the configuration is modified (adding new RLs or modification of existing RLs)
–

>>>Additional E-DCH Cell Information Configuration Change 

1..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.
–

>>>> Additional E-DCH Configuration Change Information
M

9.2.2.136

–

>>Removal



Used when all RLs on the indicated secondary UL frequency is removed.
–

>>>Additional E-DCH Cell Information Removal

1..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.
–

>>>>RL on Secondary UL Frequency
M

ENUMERATED (Remove, ...)
Removal of all RL on secondary UL frequency
–

UL CLTD Information Reconf
O

9.2.2.151

YES
reject
E-DCH Decoupling Indication
O

9.2.2.194

YES
reject
Radio Links without DPCH/F-DPCH Indication
O

9.2.2.201

YES
reject
UL DPCCH2 Reconfiguration
O

9.2.2.202

YES
reject
Downlink TPC enhancements Reconf
O

9.2.2.215

YES
reject

Range Bound
Explanation
maxNrOfDCHs
Maximum number of DCHs for a UE
maxNrOfRLs
Maximum number of RLs for a UE
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE
maxNrOfEDCH-1
Maximum number of uplink frequencies -1 for E-DCH for one UE

Condition
Explanation
SF/2
The IE shall be present if the Transmission Gap Pattern Sequence Information IE is included and the indicated Downlink Compressed Mode method for at least one of the included Transmission Gap Pattern Sequence is set to "SF/2".
HSDSCH Radio Link
The IE shall be present if HS-PDSCH RL ID IE is present.

9.1.47.2	TDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
reject
UL CCTrCH To Modify

0..<maxNrOfCCTrCHs>


EACH
notify
>CCTrCH ID
M

9.2.3.3

–

>TFCS
O

9.2.1.58

–

>Puncture Limit
O

9.2.1.50

–

>UL SIR Target
O

UL SIR
9.2.1.67A
Applicable to 1.28Mcps TDD only
YES
reject
UL CCTrCH To Delete

0..<maxNrOfCCTrCHs>


EACH
notify
>CCTrCH ID
M

9.2.3.3

–

DL CCTrCH To Modify

0..<maxNrOfCCTrCHs>


EACH
notify
>CCTrCH ID
M

9.2.3.3

–

>TFCS
O

9.2.1.58

–

>Puncture Limit
O

9.2.1.50

–

>DL CCTrCH To Modify Per RL

0..<maxNrOfRLs>

See note 1 below


>>DL DPCH To Modify LCR

0..1

Applicable to 1.28Mcps TDD only
YES
 ignore
>>>DL Timeslot Information LCR

0..<maxNrOfDLTSLCRs>


–

>>>>Time Slot LCR
M

9.2.3.24A

–

>>>>Maximum DL Power
O

DL Power
9.2.1.21
Maximum allowed power on DPCH
–

>>>>Minimum DL Power
O

DL Power
9.2.1.21
Minimum allowed power on DPCH
–

>>CCTrCH Maximum DL Transmission Power
O

DL Power
9.2.1.21

YES
ignore
>>CCTrCH Minimum DL Transmission Power
O

DL Power
9.2.1.21

YES
ignore
>>RL ID
O

9.2.1.53

YES
ignore
DL CCTrCH To Delete

0..<maxNrOfCCTrCHs>


EACH
notify
>CCTrCH ID
M

9.2.3.3

–

DCHs To Modify
O

DCHs TDD To Modify 9.2.3.4D

YES
reject
DCHs To Add
O

DCH TDD Information 9.2.3.4C

YES
reject
DCHs To Delete

0..<maxNrOfDCHs>


GLOBAL
reject
>DCH ID
M

9.2.1.20

–

RL Information

0..<maxNrOfRLs>

See note 1 below
YES
reject
>RL ID
M

9.2.1.53

–

>Maximum Downlink Power 
O

DL Power
9.2.1.21

–

>Minimum Downlink Power 
O

DL Power
9.2.1.21

–

>RL Specific DCH Information
O

9.2.1.53G

YES
ignore
>UL Synchronisation Parameters LCR

0..1

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
ignore
>>Uplink Synchronisation Step Size
M

9.2.3.26H

–

>>Uplink Synchronisation Frequency
M

9.2.3.26G

–

Signalling Bearer Request Indicator
O

9.2.1.55A

YES
reject
HS-DSCH Information
O

HS-DSCH TDD Information 
9.2.3.5F

YES
reject
HS-DSCH Information To Modify Unsynchronised
O

9.2.1.31HA

YES
reject
HS-DSCH MAC-d Flows To Add
O

HS-DSCH MAC-d Flows Information 9.2.1.31IA

YES
reject
HS-DSCH MAC-d Flows To Delete
O

9.2.1.31IB

YES
reject
HS-DSCH RNTI
C-HSDSCHRadioLink

9.2.1.31J

YES
reject
HS-PDSCH RL ID
O

RL ID 9.2.1.53

YES
reject
E-DCH Information

0..1

3.84Mcps TDD only
YES
reject
>E-PUCH Information
O

9.2.3.45

–

>E-TFCS Information TDD
O

9.2.3.46

–

>E-DCH MAC-d Flows to Add
O

E-DCH MAC-d Flows Information TDD 9.2.3.47

–

>E-DCH MAC-d Flows to Delete
O

9.2.1.73

–

>E-DCH Non-scheduled Grant Information TDD
O

9.2.3.48

–

>E-DCH TDD Information
O

9.2.3.49

–

>E-DCH TDD Information to Modify
O

9.2.3.52

–

E-DCH Serving RL
O

RL ID
9.2.1.53

YES
reject
E-DCH Information 7.68Mcps

0..1

7.68Mcps TDD only
YES
reject
>E-PUCH Information
O

9.2.3.45

–

>E-TFCS Information TDD
O

9.2.3.46

–

>E-DCH MAC-d Flows to Add
O

E-DCH MAC-d Flows Information TDD 9.2.3.47

–

>E-DCH MAC-d Flows to Delete
O

9.2.1.73

–

>E-DCH Non-scheduled Grant Information 7.68Mcps TDD
O

9.2.3.64

–

>E-DCH TDD Information 7.68Mcps
O

9.2.3.65

–

>E-DCH TDD Information to Modify
O

9.2.3.52

–

E-DCH Information 1.28Mcps

0..1

1.28Mcps TDD only 
YES
reject
>E-PUCH Information LCR
O

9.2.3.45a

–

>E-TFCS Information TDD
O

9.2.3.46

–

>E-DCH MAC-d Flows to Add
O

E-DCH MAC-d Flows Information TDD 9.2.3.47

–

>E-DCH MAC-d Flows to Delete
O

9.2.1.73

–

>E-DCH Non-scheduled Grant Information LCR TDD
O

9.2.3.48a

–

>E-DCH TDD Information LCR
O

9.2.3.49a

–

>E-DCH TDD Information to Modify
O

9.2.3.52

–

Power Control GAP
O

INTEGER (1..255)
Unit: Number of subframes
Applicable to 1.28Mcps TDD only
YES
ignore
CPC Information

0..1


YES
reject
>Continuous Packet Connectivity DRX Information LCR
O

9.2.3.93

_

>Continuous Packet Connectivity DRX Information To Modify LCR
O

9.2.3.94

_

>HS-DSCH Semi-Persistent scheduling Information LCR
O

9.2.3.96

_

>HS-DSCH Semi-Persistent scheduling Information to modify LCR
O

9.2.3.96a

_

>HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR
O

9.2.3.100

YES
reject
>E-DCH Semi-Persistent scheduling Information LCR
O

9.2.3.97

_

>E-DCH Semi-Persistent scheduling Information to modify LCR
O

9.2.3.97a

_

>E-DCH Semi-Persistent scheduling Deactivate Indicator LCR
O

9.2.3.101

YES
reject
Idle Interval Information
O

9.2.3.102
TDD only
YES
Ignore
UE Selected MBMS Service Information
O

9.2.3.104
This IE indicates the Time Slot information and/or TDM information of UE selected MBMS service in the other frequency. For 1.28Mcps TDD only.
YES
ignore
HS-SCCH TPC step size
O

TDD TPC DL Step Size
9.2.3.21
1.28 Mcps TDD only.
This IE is mandatory if ’E-DCH Information 1.28Mcps’ IE is absent.
YES
ignore
DCH Measurement Occasion Information
O

9.2.3.111
Applicable for 1.28 Mcps TDD.
YES
reject
HS-DSCH-RNTI for FACH
O

HS-DSCH RNTI
9.2.1.31J
1.28 Mcps TDD only
YES
ignore
Multi-Carrier E-DCH Information Reconf

0..1

Applicable for Multi-Carrier E-DCH Operation in 1.28 Mcps TDD only
YES
reject
>CHOICE continue,Setup or Change 
M



–

>>continue



Used when a RL with Multi-carrier E-DCH configurations exists in the current Node B Communication context and the configuration keeps unchanged.
–

>>Setup



Used when the Multi-carrier E-DCH is not configured for this RL in the current Node B Communication Context
–

>>>Multi-Carrier E-DCH Transport Bearer Mode LCR
M

9.2.3.113

–

>>>UL Multi-Carrier E-DCH Information LCR
M

9.2.3.112

–

>>change



Used when a RL with Multi-carrier E-DCH configurations exists in the current Node B Communication context and the configuration is modified (adding new frequencies, modification of existing configuration or removing existing frequencies)
–

>>>Multi-Carrier E-DCH Transport Bearer Mode LCR
O

9.2.3.113

–

>>>UL Multi-Carrier E-DCH Information LCR
O

9.2.3.112

–

>>>Removal UL Multi-Carrier info

0..<maxNrOfULCarriersLCR-1>


–

>>>>UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
–

MU-MIMO Information
O

9.2.3.116
1.28 Mcps TDD only
YES
ignore
MU-MIMO Information To Reconfigure
O

9.2.3.117
1.28 Mcps TDD only
YES
ignore
UE support of non-rectangular resource allocation
O

ENUMERATED (support)
1.28 Mcps TDD only.
The absence of this IE indicates that the UE does not support the non-rectangular resource allocation.
YES
ignore
NOTE 1:	This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxNrOfRLs are represented by separate ASN.1 structures with different criticality.

Range Bound
Explanation
maxNrOfCCTrCHs
Maximum number of CCTrCHs for a UE
maxNrOfDLTSLCRs
Maximum number of Downlink time slots per Radio Link for 1.28Mcps TDD
maxNrOfDCHs
Maximum number of DCHs for a UE
maxNrOfRLs
Maximum number of RLs for one UE
maxNrOfULCarriersLCR-1
Maximum number of uplink frequencis in Multi-Carrier E-DCH Operation

Condition
Explanation
HSDSCHRadioLink
The IE shall be present if HS-PDSCH RL ID IE is present.

9.1.48	RADIO LINK RECONFIGURATION RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
RL Information Response

0..<maxNrOfRLs>


EACH
ignore
>RL ID
M

9.2.1.53

–

>DCH Information Response
O

9.2.1.20C

YES
ignore
>DL Power Balancing Updated Indicator
O

9.2.2.12D
FDD only
YES
ignore
>E-DCH RL Set ID
O

RL Set ID
9.2.2.39

YES
ignore
>E-DCH FDD DL Control Channel Information
O

9.2.2.13Dc

YES
ignore
>E-DCH FDD Information Response
O

9.2.2.13Db

YES
ignore
>HS-DSCH Preconfiguration Info
O

9.2.2.111

YES
ignore
>Non-Serving RL Preconfiguration Info
O

9.2.2.145

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore
Target Communication Control Port ID
O

Communication Control Port ID 9.2.1.15

YES
ignore
HS-DSCH FDD Information Response
O

9.2.2.18E
FDD only
YES
ignore
HS-DSCH TDD Information Response
O

9.2.3.5G
TDD only
YES
ignore
E-DCH TDD Information Response
O

E-DCH TDD Information Response 9.2.3.50
TDD only
YES
ignore
MAC-hs Reset Indicator
O

9.2.1.38Ac

YES
ignore
Continuous Packet Connectivity HS-SCCH less Information Response
O

9.2.2.69
FDD only
YES
ignore
Additional HS Cell Information Response

0..<maxNrOfHSDSCH-1>

For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. 
EACH
ignore
>HS-PDSCH RL ID
M

RL ID 9.2.1.53

–

>HS-DSCH FDD Secondary Serving Information Response
M

9.2.2.18EA
FDD only
–

Continuous Packet Connectivity DRX Information Response LCR
O

9.2.3.95
1.28 Mcps TDD only
YES
ignore
HS-DSCH Semi-Persistent scheduling Information Response LCR
O

9.2.3.98
1.28 Mcps TDD only
YES
ignore
E-DCH Semi-Persistent scheduling Information Response LCR
O

9.2.3.99
1.28 Mcps TDD only
YES
ignore
Additional E-DCH Cell Information Response RLReconf

0..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. 
EACH
ignore
>Additional E-DCH FDD Information Response
O

9.2.2.135
For new E-DCH Radio Links on secondary uplink frequency
–

>Additional Modified E-DCH FDD Information Response
O

9.2.2.141

–

E-RNTI for FACH
O

E-RNTI
9.2.1.75
1.28 Mcps TDD only
YES
ignore
Multi-Carrier E-DCH Information Response LCR
O

9.2.3.114
1.28 Mcps TDD only
YES
ignore
MU-MIMO Information Response
O

9.2.3.118
1.28 Mcps TDD only
YES
reject
Non-rectangular resource allocation indicator
O

ENUMERATED (activate)
1.28 Mcps TDD only.
The absence of this IE indicates that the non-rectangular resource allocation is not used.
YES
reject
Non-rectangular resource timeslot set
O

BIT STRING (SIZE(7))
1.28 Mcps TDD only.
The absence of this IE means that the specific timeslot(s) of the non-rectangular resource is defined in 3GPP TS 25.222 [34].
This IE indicats which of the timeslot(s) is/are allocated for non-rectangular resource. 
Bit 0 is for timeslot 0. Bit 1 is for timeslot 1. Bit 2 is for timeslot 2. Bit 3 is for timeslot 3. Bit 4 is for timeslot 4. Bit 5 is for timeslot 5. Bit 6 is for timeslot 6.
The value 0 of a bit means the corresponding timeslot is not allocated for non-rectangular resource. The value 1 of a bit means the corresponding timeslot is allocated for non-rectangular resource.
Bit 0 is the first/leftmost bit of the bit string.
YES
reject

Range Bound
Explanation
maxNrOfRLs
Maximum number of RLs for a UE
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE
maxNrOfEDCH-1
Maximum number of uplink frequencies -1 for E-DCH for one UE

9.1.49	RADIO LINK DELETION REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
reject
CRNC Communication Context ID
M

9.2.1.18

YES
reject
RL Information 

1..<maxNrOfRLs>


EACH
notify
>RL ID
M

9.2.1.53

–


Range Bound
Explanation
maxNrOfRLs
Maximum number of radio links for one UE

9.1.50	RADIO LINK DELETION RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.51	DL POWER CONTROL REQUEST [FDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
ignore
Power Adjustment Type
M

9.2.2.27

YES
ignore
DL Reference Power
C-Common

DL power
9.2.1.21
Power on DPCH or on
F-DPCH
YES
ignore
Inner Loop DL PC Status
O

9.2.2.18B

YES
ignore
DL Reference Power Information
C-Individual
1..<maxNrOfRLs>


EACH
ignore
>RL ID
M

9.2.1.53

–

>DL Reference Power
M

DL power
9.2.1.21
Power on DPCH or on
F-DPCH
–

Max Adjustment Step
C-CommonOrIndividual

9.2.2.20

YES
ignore
Adjustment Period
C-CommonOrIndividual

9.2.2.B

YES
ignore
Adjustment Ratio
C-CommonOrIndividual

9.2.2.C

YES
ignore

Condition
Explanation
Common
The IE shall be present if the Adjustment Type IE is equal to "Common".
Individual
The IE shall be present if the Adjustment Type IE is equal to "Individual".
CommonOrIndividual
The IE shall be present if the Adjustment Type IE is equal to "Common" or "Individual".

Range Bound
Explanation
maxNrOfRLs
Maximum number of Radio Links for a UE

9.1.52	DEDICATED MEASUREMENT INITIATION REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used when the Report characteristics type is set to "On Demand".
YES
reject
Measurement ID
M

9.2.1.42

YES
reject
CHOICE Dedicated Measurement Object Type
M



YES
reject
>RL






>>RL Information

1..<maxNrOfRLs>


EACH
reject
>>>RL ID
M

9.2.1.53

–

>>>DPCH ID
O

9.2.3.5
TDD only
–

>>>PUSCH Information

0..<maxNrOfPUSCHs>

TDD only
GLOBAL
reject
>>>>PUSCH ID
M

9.2.3.12

–

>>>HS-SICH Information

0..<maxNrOfHSSICHs>

TDD only
GLOBAL
reject
>>>>HS-SICH ID
M

9.2.3.5Gb
For 1.28Mcps TDD, if the Extended HS-SICH ID IE is included in the HS-SICH Information IE, the HS-SICH ID IE shall be ignored
–

>>>>Extended HS-SICH ID
O

9.2.3.5K
Applicable to 1.28Mcps TDD only, the Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31.
See note 1 below.
–

>>>DPCH ID 7.68Mcps
O

9.2.3.42
Included for 7.68Mcps TDD for downlink DPCH
YES
reject
>RLS



FDD only


>>RL Set Information

1..<maxNrOfRLSets>


–

>>>RL Set ID
M

9.2.2.39

–

>ALL RL


NULL



>ALL RLS


NULL
FDD only


Dedicated Measurement Type
M

9.2.1.23

YES
reject
Measurement Filter Coefficient
O

9.2.1.41

YES
reject
Report Characteristics
M

9.2.1.51

YES
reject
CFN Reporting Indicator
M

FN Reporting Indicator 9.2.1.29B

YES
reject
CFN
O

9.2.1.7

YES
reject
Number Of Reported Cell Portions
C-BestCellPortionsMeas

9.2.2.23D
FDD only
YES
reject
Measurement Recovery Behavior
O

9.2.1.43A

YES
ignore
Alternative Format Reporting Indicator
O

9.2.1.1B

YES
ignore
Number Of Reported Cell Portions LCR
C-BestCellPortionsMeasLCR

9.2.3.108
1.28Mcps TDD only
YES
reject
Note 1:	This information element is a simplified representation of the ASN.1.


Condition
Explanation
BestCellPortionsMeas
The IE shall be present if the Dedicated Measurement Type IE is set to "Best Cell Portions".
BestCellPortionsMeasLCR
The IE shall be present if the Dedicated Measurement Type IE is set to “Best Cell Portions LCR”.

Range Bound
Explanation
maxNrOfRLs
Maximum number of individual RLs a measurement can be started on
maxNrOfPUSCHs
Maximum number of PUSCHs per RL a measurement can be started on
maxNrOfRLSets
Maximum number of individual RL Sets a measurement can be started on
maxNrOfHSSICHs
Maximum number of HSSICHs per RL a measurement can be started on

9.1.53	DEDICATED MEASUREMENT INITIATION RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18

YES
ignore
Measurement ID
M

9.2.1.42

YES
ignore
CHOICE Dedicated Measurement Object Type
O


Dedicated Measurement Object Type the measurement was initiated with
YES
ignore
>RL or ALL RL



See Note 1


>>RL Information

1..<maxNrOfRLs>


EACH
ignore
>>>RL ID
M

9.2.1.53

–

>>>DPCH ID
O

9.2.3.5
TDD only
–

>>>Dedicated Measurement Value
M

9.2.1.24

–

>>>CFN
O

9.2.1.7
Dedicated Measurement Time Reference
_

>>>PUSCH Information

0..<maxNrOfPUSCHs>

TDD only
See note 3
GLOBAL
reject
>>>>PUSCH ID
M

9.2.3.12

–

>>>>Dedicated Measurement Value
O

9.2.1.24

–

>>>HS-SICH ID
O

9.2.3.5Gb
TDD only
For 1.28Mcps TDD, if the Extended HS-SICH ID IE is included in the HS-SICH Information IE, the HS-SICH ID IE shall be ignored
YES
reject
>>>Multiple Dedicated Measurement Value Information

0..<maxNrOfDPCHsPerRL-1>

Applicable to 3.84Mcps TDD only
GLOBAL
ignore
>>>>DPCH ID
M

9.2.3.5

–

>>>>Dedicated Measurement Value
M

9.2.1.24

–

>>>Multiple Dedicated Measurement Value Information LCR

0..<maxNrOfDPCHsLCRPerRL-1>

Applicable to 1.28McpsTDD only
GLOBAL
ignore
>>>>DPCH ID
M

9.2.3.5

–

>>>>Dedicated Measurement Value
M

9.2.1.24

–

>>>Multiple HS-SICH Measurement Value Information

0..<maxNrOfHSSICHs -1>

TDD only
GLOBAL
ignore
>>>>HS-SICH ID
M

9.2.3.5Gb
For 1.28Mcps TDD, if the Extended HS-SICH ID IE is included in the HS-SICH Information IE, the HS-SICH ID IE shall be ignored
–

>>>>Dedicated Measurement Value
M

9.2.1.24

–

>>>>Extended HS-SICH ID
O

9.2.3.5K
Applicable to 1.28Mcps TDD only, the Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31.
YES
ignore
>>>DPCH ID 7.68Mcps
O

9.2.3.42
Included for 7.68Mcps TDD for downlink DPCH
YES
reject
>>>Multiple Dedicated Measurement Value Information 7.68Mcps

0..<maxNrOfDPCHs768PerRL-1>

Applicable to 7.68McpsTDD only
GLOBAL
ignore
>>>>DPCH ID 7.68Mcps
M

9.2.3.42

–

>>>>Dedicated Measurement Value
M

9.2.1.24

–

>>>Extended HS-SICH ID
O

9.2.3.5K
Applicable to 1.28Mcps TDD only, the Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31.
YES
reject
>RLS or ALL RLS



FDD only
See Note 2


>>RL Set Information

1..<maxNrOfRLSets>


EACH
ignore
>>>RL Set ID
M

9.2.2.39

–

>>>Dedicated Measurement Value
M

9.2.1.24

–

>>>CFN
O

9.2.1.7
Dedicated Measurement Time Reference
_

Criticality Diagnostics
O

9.2.1.17

YES
ignore
Measurement Recovery Support Indicator
O

9.2.1.43C

YES
ignore
Note 1: 	This is a simplified representation of the ASN.1: there are two different choice tags "RL" and "ALL RL" in the ASN.1, each having exactly the same structure.
Note 2: 	This is a simplified representation of the ASN.1: there are two different choice tags "RLS" and "ALL RLS" in the ASN.1, each having exactly the same structure.
Note 3: 	This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxNrOfPUSCHs are represented by separate ASN.1 structures with different criticality.

Range Bound
Explanation
maxNrOfRLs
Maximum number of individual RLs the measurement can be started on
maxNrOfPUSCHs
Maximum number of PUSCHs per RL a measurement can be started on
maxNrOfRLSets
Maximum number of individual RL Sets a measurement can be started on
maxNrOfDPCHsPerRL-1
Maximum number of DPCHs per RL a measurement can be started on for 3.84Mcps TDD
maxNrOfDPCHsLCRPerRL-1
Maximum number of DPCHs per RL a measurement can be started on for 1.28Mcps TDD
maxNrOfHSSICHs
Maximum number of HSSICHs per RL a measurement can be started on
maxNrOfDPCHs768PerRL-1
Maximum number of DPCHs per RL a measurement can be started on for 7.68Mcps TDD

9.1.54	DEDICATED MEASUREMENT INITIATION FAILURE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18

YES
ignore
Measurement ID
M

9.2.1.42

YES
ignore
Cause
M

9.2.1.6

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.55	DEDICATED MEASUREMENT REPORT
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
Measurement ID
M

9.2.1.42

YES
ignore
CHOICE Dedicated Measurement Object Type
M


Dedicated Measurement Object Type the measurement was initiated with
YES
ignore
>RL or ALL RL



See Note 1


>>RL Information

1..<maxNrOfRLs>


EACH
ignore
>>>RL ID
M

9.2.1.53

–

>>>DPCH ID
O

9.2.3.5
TDD only
–

>>>Dedicated Measurement Value Information
M

9.2.1.24A

–

>>>PUSCH Information

0..<maxNrOfPUSCHs>

TDD only
See note 3
GLOBAL
reject
>>>>PUSCH ID
M

9.2.3.12

–

>>>>Dedicated Measurement Value
O

9.2.1.24

–

>>>HS-SICH ID
O

9.2.3.5Gb
TDD only
For 1.28Mcps TDD, if the Extended HS-SICH ID IE is included in the HS-SICH Information IE, the HS-SICH ID IE shall be ignored
YES
reject
>>>DPCH ID 7.68Mcps
O

9.2.3.42
Included for 7.68Mcps TDD for downlink DPCH
YES
reject
>>>Extended HS-SICH ID
O

9.2.3.5K
Applicable to 1.28Mcps TDD only, the Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31.
YES
ignore
>RLS or ALL RLS



FDD only
See Note 2


>>RL Set Information

1..<maxNrOfRLSets>


EACH
ignore
>>>RL Set ID
M

9.2.2.39

–

>>>Dedicated Measurement Value Information
M

9.2.1.24A

–

Measurement Recovery Reporting Indicator
O

9.2.1.43B

YES
ignore
Note 1: 	This is a simplified representation of the ASN.1: there are two different choice tags "RL" and "ALL RL" in the ASN.1, each having exactly the same structure.
Note 2: 	This is a simplified representation of the ASN.1: there are two different choice tags "RLS" and "ALL RLS" in the ASN.1, each having exactly the same structure.
Note 3: 	This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxNrOfPUSCHs are represented by separate ASN.1 structures with different criticality.

Range Bound
Explanation
maxNrOfRLs
Maximum number of individual RLs the measurement can be started on
maxNrOfPUSCHs
Maximum number of PUSCHs per RL a measurement can be started on
maxNrOfRLSets
Maximum number of individual RL Sets a measurement can be started on

9.1.56	DEDICATED MEASUREMENT TERMINATION REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC" shall be used if this value was used when initiating the measurement. Otherwise, the reserved value "All NBCC" shall not be used.
YES
ignore
Measurement ID
M

9.2.1.42

YES
ignore

9.1.57	DEDICATED MEASUREMENT FAILURE INDICATION
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall be used if the Node B Communication Context ID was set to "All NBCC" when initiating the measurement. Otherwise, the reserved value "All CRNCCC" shall not be used.
YES
ignore
Measurement ID
M

9.2.1.42

YES
ignore
Cause
M

9.2.1.6

YES
ignore

9.1.58	RADIO LINK FAILURE INDICATION
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
CHOICE Reporting Object
M


Object for which the Failure shall be reported.
YES
ignore
>RL






>>RL Information

1..<maxNrOfRLs>


EACH
ignore
>>>RL ID
M

9.2.1.53

–

>>>Cause
M

9.2.1.6

–

>RL Set



FDD only


>>RL Set Information

1..<maxNrOfRLSets>


EACH
ignore
>>>RL Set ID
M

9.2.2.39

–

>>>Cause
M

9.2.1.6

–

>CCTrCH



TDD only


>>RL ID
M

9.2.1.53

–

>>CCTrCH List

1..<maxNrOfCCTrCHs>


EACH
ignore
>>>CCTrCH ID 
M

9.2.3.3

–

>>>Cause
M

9.2.1.6

–


Range Bound
Explanation
maxNrOfRLs
Maximum number of RLs for one UE
maxNrOfRLSets
Maximum number of RL Sets for one UE
maxNrOfCCTrCHs 
Maximum number of CCTrCHs for a UE

9.1.59	RADIO LINK RESTORE INDICATION
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
CHOICE Reporting Object
M


Object for which the Restoration shall be reported.
YES
ignore
>RL



TDD only


>>Radio Link Information

1..<maxNrOfRLs>


EACH
ignore
>>>RL ID
M

9.2.1.53

–

>RL Set



FDD only


>>RL Set Information

1..<maxNrOfRLSets>


EACH
ignore
>>>RL Set ID
M

9.2.2.39

–

>CCTrCH



TDD only


>>RL ID
M

9.2.1.53

–

>>CCTrCH List

1..<maxNrOfCCTrCHs>


EACH
ignore
>>>CCTrCH ID 
M

CCTrCH ID
9.2.3.3

–


Range Bound
Explanation
maxNrOfRLs
Maximum number of RLs for one UE
maxNrOfRLSets
Maximum number of RL Sets for one UE
maxNrOfCCTrCHs
Maximum number of CCTrCHs for a UE

9.1.60	COMPRESSED MODE COMMAND [FDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
ignore
Active Pattern Sequence Information
M

9.2.2.A

YES
ignore

9.1.61	ERROR INDICATION
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator 
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
O

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
Node B Communication Context ID
O

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
ignore
Cause
O

9.2.1.6

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.62	PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST
9.1.62.1	FDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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
Configuration Generation ID
M

9.2.1.16

YES
reject
SFN
O

9.2.1.53A

YES
reject
HS-PDSCH, HS-SCCH,E-AGCH, E-RGCH and E-HICH Total Power
O

Maximum Transmission Power
9.2.1.40
Maximum transmission power to be allowed for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH codes
YES
reject
HS-PDSCH And HS-SCCH Scrambling Code
O

DL Scrambling Code 
9.2.2.13
Scrambling code on which HS-PDSCH and HS-SCCH is transmitted.
0= Primary scrambling code of the cell 1…15 = Secondary scrambling code
YES
reject
HS-PDSCH FDD Code Information
O

9.2.2.18F

YES
reject
HS-SCCH FDD Code Information
O

9.2.2.18G

YES
reject
E-AGCH And E-RGCH/E-HICH FDD Scrambling Code
O

DL Scrambling Code 
9.2.2.13
Scrambling code on which E-AGCH, E-RGCH and E-HICH are transmitted.
0= Primary scrambling code of the cell 1…15 = Secondary scrambling code
YES
reject
E-AGCH FDD Code Information
O

9.2.2.13Ib

YES
reject
E-RGCH/E-HICH FDD Code Information
O

9.2.2.13Ia

YES
reject
HSDPA And E-DCH Cell Portion Information

0..<maxNrOfCellPortionsPerCell>


GLOBAL
reject
>Cell Portion ID
M

9.2.2.1Ca

–

>HS-PDSCH And HS-SCCH Scrambling Code
O

DL Scrambling Code 
9.2.2.13
Scrambling code on which HS-PDSCH and HS-SCCH is transmitted over cell portion.
–

>HS-PDSCH FDD Code Information 
O

9.2.2.18F

–

>HS-SCCH FDD Code Information
O

9.2.2.18G

–

>HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH Total Power
O

Maximum Transmission Power
9.2.1.40
Maximum transmission power to be allowed for HS-PDSCH, HS-SCCH and E-AGCH, E-RGCH and E-HICH codes over cell portion

–

>E-AGCH And E-RGCH/E-HICH FDD Scrambling Code
O

DL Scrambling Code 
9.2.2.13
Scrambling code on which E-AGCH, E-RGCH and E-HICH are transmitted over cell portion. 
–

>E-AGCH FDD Code Information
O

9.2.2.13Ib

–

>E-RGCH/E-HICH FDD Code Information
O

9.2.2.13Ia

–

>Maximum Target Received Total Wide Band Power
O

9.2.2.21a

YES
ignore
>Reference Received Total Wide Band Power
O

9.2.2.39B

YES
ignore
Maximum Target Received Total Wide Band Power
O

9.2.2.21a

YES
reject
Reference Received Total Wide Band Power
O

9.2.2.39B

YES
ignore
Target Non-serving E-DCH to Total E-DCH Power ratio
O

9.2.2.21b

YES
reject
HS-DSCH Common System Information
O

9.2.2.75

YES
reject
Common MAC Flows to Delete
O

9.2.2.97

YES
reject
HS-DSCH Paging System Information
O

9.2.2.76

YES
reject
Paging MAC Flows to Delete
O

9.2.2.98

YES
reject
Common E-DCH System Information
O

9.2.2.103

YES
Reject
Common UL MAC Flows to Delete
O

Common MAC Flows to Delete
9.2.2.97

YES
Reject
Common E-DCH MAC-d Flows to Delete
O

E-DCH MAC Flows to Delete
9.2.1.73

YES
Reject
Enhanced UE DRX Information
O

9.2.2.108

YES
reject
Further Enhanced UE DRX Information
O

9.2.2.185

YES
ignore
Common E-RGCH Operation Indicator
O

ENUMERATED(true)

YES
ignore

Range Bound
Explanation
MaxNrOfCellPortionsPerCell
Maximum number of Cell Portions in a cell 

9.1.62.2	TDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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
SFN
O

9.2.1.53A

YES
reject
PDSCH Sets To Add

0..<maxNrOfPDSCHSets>


GLOBAL
reject
>PDSCH Set ID
M

9.2.3.11

–

>PDSCH To Add Information

0..1

Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD.
YES
reject
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD Physical Channel Offset
M

9.2.3.20

–

>>DL Timeslot Information

1..<maxNrOfDLTSs>


–

>>>Time Slot
M

9.2.3.23

–

>>>Midamble Shift And Burst Type
M

9.2.3.7

–

>>>TFCI Presence
M

9.2.1.57

–

>>>DL Code Information

1..<maxNrOfPDSCHs>


–

>>>>PDSCH ID
M

9.2.3.10

–

>>>>TDD Channelisation Code
M

9.2.3.19

–

>PDSCH To Add Information LCR

0..1

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
reject
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD Physical Channel Offset
M

9.2.3.20

–

>>DL Timeslot Information LCR

1..<maxNrOfDLTSLCRs>


–

>>>Time Slot LCR
M

9.2.3.24A

–

>>>Midamble Shift LCR
M

9.2.3.7A

–

>>>TFCI Presence
M

9.2.1.57

–

>>>DL Code Information LCR

1..<maxNrOfPDSCHs>


–

>>>>PDSCH ID
M

9.2.3.10

–

>>>>TDD Channelisation Code LCR
M

9.2.3.19a

–

>>>>TDD DL DPCH Time Slot Format LCR
O

9.2.3.19D

YES
reject
>>TSTD Indicator
O

9.2.1.64

YES
reject
>PDSCH To Add Information 7.68Mcps

0..1

Mandatory for 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD or 3.84Mcps TDD.
YES
reject
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD Physical Channel Offset
M

9.2.3.20

–

>>DL Timeslot Information 7.68Mcps 

1..<maxNrOfDLTSs>


–

>>>Time Slot
M

9.2.3.23

–

>>>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>>>TFCI Presence
M

9.2.1.57

–

>>>DL Code Information 7.68Mcps

1..<maxNrOfPDSCHs>


–

>>>>PDSCH ID 7.68Mcps
M

9.2.3.43

–

>>>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

PDSCH Sets To Modify

0..< maxNrOfPDSCHSets >


GLOBAL
reject
>PDSCH Set ID
M

9.2.3.11

–

>CHOICE HCR or LCR or 7.68 Mcps
M


See note 1 below
–

>>3.84Mcps TDD




–

>>>PDSCH To Modify Information

1


YES
reject
>>>>Repetition Period
O

9.2.3.16

–

>>>>Repetition Length
O

9.2.3.15

–

>>>>TDD Physical Channel Offset
O

9.2.3.20

–

>>>>DL Timeslot Information

0..<maxNrOfDLTSs>


–

>>>>>Time Slot
M

9.2.3.23

–

>>>>>Midamble Shift And Burst Type
O

9.2.3.7

–

>>>>>TFCI Presence
O

9.2.1.57

–

>>>>>DL Code Information

0..<maxNrOfPDSCHs>


–

>>>>>>PDSCH ID
M

9.2.3.10

–

>>>>>>TDD Channelisation Code
M

9.2.3.19

–

>>1.28Mcps TDD




–

>>>PDSCH To Modify Information LCR

1


YES
reject
>>>>Repetition Period
O

9.2.3.16

–

>>>>Repetition Length
O

9.2.3.15

–

>>>>TDD Physical Channel Offset
O

9.2.3.20

–

>>>>DL Timeslot Information LCR

0..<maxNrOfDLTSLCRs>


–

>>>>>Time Slot LCR
M

9.2.3.24A

–

>>>>>Midamble Shift LCR
O

9.2.3.7A

–

>>>>>TFCI Presence
O

9.2.1.57

–

>>>>>DL Code Information LCR

0..<maxNrOfPDSCHs>


–

>>>>>>PDSCH ID
M

9.2.3.10

–

>>>>>>TDD Channelisation Code LCR
M

9.2.3.19a

–

>>>>>>TDD DL DPCH Time Slot Format LCR
O

9.2.3.19D

YES
reject
>>7.68Mcps TDD




–

>>>PDSCH To Modify Information 7.68Mcps 

1


YES
reject
>>>>Repetition Period
O

9.2.3.16

–

>>>>Repetition Length
O

9.2.3.15

–

>>>>TDD Physical Channel Offset
O

9.2.3.20

–

>>>>DL Timeslot Information 7.68Mcps

0..<maxNrOfDLTSs>


–

>>>>>Time Slot
M

9.2.3.23

–

>>>>>Midamble Shift And Burst Type 7.68Mcps 
O

9.2.3.35

–

>>>>>TFCI Presence
O

9.2.1.57

–

>>>>>DL Code Information 7.68Mcps 

0..<maxNrOfPDSCHs>


–

>>>>>>PDSCH ID 7.68Mcps
M

9.2.3.43

–

>>>>>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

PDSCH Sets To Delete

0..< maxNrOfPDSCHSets >


GLOBAL
reject
>PDSCH Set ID
M

9.2.3.11

–

PUSCH Sets To Add

0..< maxNrOfPUSCHSets >


GLOBAL
reject
>PUSCH Set ID
M

9.2.3.13

–

>PUSCH To Add Information

0..1

Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD.
YES
reject
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD Physical Channel Offset
M

9.2.3.20

–

>>UL Timeslot Information

1..<maxNrOfULTSs>


–

>>>Time Slot
M

9.2.3.23

–

>>>Midamble Shift And Burst Type
M

9.2.3.7

–

>>>TFCI Presence
M

9.2.1.57

–

>>>UL Code Information

1..<maxNrOfPUSCHs>


–

>>>>PUSCH ID
M

9.2.3.12

–

>>>>TDD Channelisation Code
M

9.2.3.19

–

>PUSCH To Add Information LCR

0..1

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
reject
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD Physical Channel Offset
M

9.2.3.20

–

>>UL Timeslot Information LCR

1..<maxNrOfULTSLCRs>


–

>>>Time Slot LCR
M

9.2.3.24A

–

>>>Midamble Shift LCR
M

9.2.3.7A

–

>>>TFCI Presence
M

9.2.1.57

–

>>>UL Code Information LCR

1..<maxNrOfPUSCHs>


–

>>>>PUSCH ID
M

9.2.3.12

–

>>>>TDD Channelisation Code LCR
M

9.2.3.19a

–

>>>>TDD UL DPCH Time Slot Format LCR
O

9.2.3.21C

YES
reject
>PUSCH To Add Information 7.68Mcps 

0..1

Mandatory for 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD or 3.84 Mcps TDD.
YES
reject
>>Repetition Period
M

9.2.3.16

–

>>Repetition Length
M

9.2.3.15

–

>>TDD Physical Channel Offset
M

9.2.3.20

–

>>UL Timeslot Information 7.68Mcps 

1..<maxNrOfULTSs>


–

>>>Time Slot
M

9.2.3.23

–

>>>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>>>TFCI Presence
M

9.2.1.57

–

>>>UL Code Information 7.68Mcps 

1..<maxNrOfPUSCHs>


–

>>>>PUSCH ID
M

9.2.3.12

–

>>>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

PUSCH Sets To Modify

0..< maxNrOfPUSCHSets >


GLOBAL
reject
>PUSCH Set ID
M

9.2.3.13

–

>CHOICE HCR or LCR or 7.68Mcps
M


See note 1 below
–

>>3.84Mcps TDD




–

>>>PUSCH To Modify Information

1


YES
reject
>>>>Repetition Period
O

9.2.3.16

–

>>>>Repetition Length
O

9.2.3.15

–

>>>>TDD Physical Channel Offset
O

9.2.3.20

–

>>>>UL Timeslot Information

0..<maxNrOfULTSs>


–

>>>>>Time Slot
M

9.2.3.23

–

>>>>>Midamble Shift And Burst Type
O

9.2.3.7

–

>>>>>TFCI Presence
O

9.2.1.57

–

>>>>>UL Code Information

0..<maxNrOfPUSCHs>


–

>>>>>>PUSCH ID
M

9.2.3.12

–

>>>>>>TDD Channelisation Code
M

9.2.3.19

–

>>1.28Mcps TDD




–

>>>PUSCH To Modify Information LCR 

1


YES
reject
>>>>Repetition Period
O

9.2.3.16

–

>>>>Repetition Length
O

9.2.3.15

–

>>>>TDD Physical Channel Offset
O

9.2.3.20

–

>>>>UL Timeslot Information LCR

0..<maxNrOfULTSLCRs>


–

>>>>>Time Slot LCR
M

9.2.3.24A

–

>>>>>Midamble Shift LCR
O

9.2.3.7A

–

>>>>>TFCI Presence
O

9.2.1.57

–

>>>>>UL Code Information LCR

0..<maxNrOfPUSCHs>


–

>>>>>>PUSCH ID
M

9.2.3.12

–

>>>>>>TDD Channelisation Code LCR
M

9.2.3.19a

–

>>>>>>TDD UL DPCH Time Slot Format LCR
O

9.2.3.21C

YES
reject
>>7.68Mcps TDD




–

>>>PUSCH To Modify Information 7.68Mcps 

1


YES
reject
>>>>Repetition Period
O

9.2.3.16

–

>>>>Repetition Length
O

9.2.3.15

–

>>>>TDD Physical Channel Offset
O

9.2.3.20

–

>>>>UL Timeslot Information 7.68Mcps

0..<maxNrOfULTSs>


–

>>>>>Time Slot
M

9.2.3.23

–

>>>>>Midamble Shift And Burst Type 7.68Mcps
O

9.2.3.35

–

>>>>>TFCI Presence
O

9.2.1.57

–

>>>>>UL Code Information 7.68Mcps

0..<maxNrOfPUSCHs>


–

>>>>>>PUSCH ID
M

9.2.3.12

–

>>>>>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

PUSCH Sets To Delete

0..<maxNrOfPDSCHSets>


GLOBAL
reject
>PUSCH Set ID
M

9.2.3.13

–

HS-PDSCH TDD Information

0..1


GLOBAL
reject
>DL Timeslot and Code Information

0..<maxNrOfDLTSs>

Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD.
–

>>Time Slot
M

9.2.3.23

–

>>Midamble Shift And Burst Type
M

9.2.3.7

–

>>Codes

1..<maxNrOfHSPDSCHs>


–

>>>TDD Channelisation Code
M

9.2.3.19

–

>>HS-PDSCH and HS-SCCH Total Power
O

Maximum Transmission Power
9.2.1.40
Maximum transmission power to be allowed for HS-PDSCH and HS-SCCH codes in the timeslot
YES
reject
>DL Timeslot and Code Information LCR per UARFCN

0.. <maxFrequencyinCell>

Mandatory for 1.28Mcps TDD 
Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
See note 2 below
EACH
reject
>>DL Timeslot and Code Information LCR

0..<maxNrOfDLTSLCRs>

.
–

>>>Time Slot LCR
M

9.2.3.24A

–

>>>Midamble Shift LCR
M

9.2.3.7A

–

>>>Codes LCR

1..<maxNrOfHSPDSCHs>


–

>>>>TDD Channelisation Code
M

9.2.3.19

–

>>>HS-PDSCH and HS-SCCH Total Power
O

Maximum Transmission Power
9.2.1.40
Maximum transmission power to be allowed for HS-PDSCH and HS-SCCH codes in the timeslot
YES
reject
>>>HS-PDSCH and HS-SCCH Total Power per CELL PORTION

0..<maxNrOfCellPortionsPerCellLCR>


EACH
ignore
>>>>Cell Portion LCR ID
M

9.2.3.107

–

>>>> HS-PDSCH and HS-SCCH Total Power Value for CELL PORTION
M

Maximum Transmission Power
9.2.1.40

–

>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Mandatory for 1.28Mcps TDD when using multiple frequencies.
–

>DL Timeslot and Code Information 7.68Mcps

0..<maxNrOfDLTSs>

Mandatory for 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD or 3.84 Mcps TDD.
GLOBAL
reject
>>Time Slot
M

9.2.3.23

–

>>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>>Codes 7.68Mcps

1..< >


–

>>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

>>HS-PDSCH and HS-SCCH Total Power
O

Maximum Transmission Power
9.2.1.40
Maximum transmission power to be allowed for HS-PDSCH and HS-SCCH codes in the timeslot
–
–
Add to HS-SCCH Resource Pool

0..1


GLOBAL
reject
>HS-SCCH Information

0..<maxNrOfHSSCCHs>

Applicable to 3.84Mcps TDD only
–

>>HS-SCCH ID
M

9.2.3.5Ga

–

>>Time Slot
M

9.2.3.23

–

>>Midamble Shift And Burst Type
M

9.2.3.7

–

>>TDD Channelisation Code
M

9.2.3.19

–

>>Maximum HS-SCCH Power
M

DL Power
9.2.1.21

–

>>HS-SICH Information

1


–

>>>HS-SICH ID
M

9.2.3.5Gb

–

>>>Time Slot
M

9.2.3.23

–

>>>Midamble Shift And Burst Type
M

9.2.3.7

–

>>>TDD Channelisation Code
M

9.2.3.19

–

>HS-SCCH Information LCR

0..<maxNrOfHSSCCHs>

Applicable to 1.28Mcps TDD only
See note 3 below
–

>>HS-SCCH ID
M

9.2.3.5Ga
If the Extended HS-SCCH ID IE is included in the HS-SCCH Information LCR IE, the HS-SCCH ID IE shall be ignored.
–

>>Time Slot LCR
M

9.2.3.24A

–

>>Midamble Shift LCR
M

9.2.3.7A

–

>>First TDD Channelisation Code
M

TDD Channelisation Code 9.2.3.19

–

>>Second TDD Channelisation Code
M

TDD Channelisation Code 9.2.3.19

–

>>Maximum HS-SCCH Power
M

DL Power
9.2.1.21

–

>>HS-SICH Information LCR

1


–

>>>HS-SICH ID
M

9.2.3.5Gb
If the Extended HS-SICH ID IE is included in the HS-SICH Information LCR IE, the HS-SICH ID IE shall be ignored.
–

>>>Time Slot LCR
M

9.2.3.24A

–

>>>Midamble Shift LCR
M

9.2.3.7A

–

>>>TDD Channelisation Code
M

9.2.3.19

–

>>>Extended HS-SICH ID
O

9.2.3.5K
The Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31.
YES
ignore
>>Extended HS-SCCH ID
O

9.2.3.5J
The Extended HS-SCCH ID IE shall be used if the HS-SCCH identity has a value larger than 31.
YES
ignore
>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Mandatory for 1.28Mcps TDD when using multiple frequencies.
YES–
ignore
>>HS-SICH Reference Signal Information
O

9.2.3.103

YES
ignore
>HS-SCCH Information 7.68Mcps

0..<maxNrOfHSSCCHs>

Applicable to 7.68Mcps TDD only
GLOBAL
reject
>>HS-SCCH ID
M

9.2.3.5Ga

–

>>Time Slot
M

9.2.3.23

–

>>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

>>Maximum HS-SCCH Power
M

DL Power
9.2.1.21

–

>>HS-SICH Information 7.68Mcps

1


–

>>>HS-SICH ID
M

9.2.3.5Gb

–

>>>Time Slot
M

9.2.3.23

–

>>>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

Modify HS-SCCH Resource Pool

0..1


GLOBAL
reject
>HS-SCCH Information

0..<maxNrOfHSSCCHs>

Applicable to 3.84Mcps TDD only
–

>>HS-SCCH ID
M

9.2.3.5Ga

–

>>Time Slot
O

9.2.3.23

–

>>Midamble Shift And Burst Type
O

9.2.3.7

–

>>TDD Channelisation Code
O

9.2.3.19

–

>>Maximum HS-SCCH Power
O

DL Power
9.2.1.21

–

>>HS-SICH Information

0..1


–

>>>HS-SICH ID
M

9.2.3.5Gb

–

>>>Time Slot
O

9.2.3.23

–

>>>Midamble Shift And Burst Type
O

9.2.3.7

–

>>>TDD Channelisation Code
O

9.2.3.19

–

>HS-SCCH Information LCR

0..<maxNrOfHSSCCHs>

Applicable to 1.28Mcps TDD only
See note 3 below
–

>>HS-SCCH ID
M

9.2.3.5Ga
If the Extended HS-SCCH ID IE is included in the HS-SCCH Information LCR IE, the HS-SCCH ID IE shall be ignored.
–

>>Time Slot LCR
O

9.2.3.24A

–

>>Midamble Shift LCR
O

9.2.3.7A

–

>>First TDD Channelisation Code
O

TDD Channelisation Code 9.2.3.19

–

>>Second TDD Channelisation Code
O

TDD Channelisation Code 9.2.3.19

–

>>Maximum HS-SCCH Power
O

DL Power
9.2.1.21

–

>>HS-SICH Information LCR

0..1


–

>>>HS-SICH ID
M

9.2.3.5Gb
If the Extended HS-SICH ID IE is included in the HS-SICH Information LCR IE, the HS-SICH ID IE shall be ignored.
–

>>>Time Slot LCR
O

9.2.3.24A

–

>>Midamble Shift LCR
O

9.2.3.7A

–

>>>TDD Channelisation Code
O

9.2.3.19

–

>>>Extended HS-SICH ID
O

9.2.3.5K
The Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31.
YES
ignore
>>Extended HS-SCCH ID
O

9.2.3.5J
The Extended HS-SCCH ID IE shall be used if the HS-SCCH identity has a value larger than 31.
YES
ignore
>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Applicable to 1.28Mcps TDD when using multiple frequencies.
YES
ignore
>>HS-SICH Reference Signal Information Modify 

0..1


YES
reject
>>>HS-SICH Reference Signal Information
O

9.2.3.103

–

>HS-SCCH Information 7.68Mcps

0..<maxNrOfHSSCCHs>

Applicable to 7.68Mcps TDD only
GLOBAL
reject
>>HS-SCCH ID
M

9.2.3.5Ga

–

>>Time Slot
O

9.2.3.23

–

>>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

>>Maximum HS-SCCH Power
O

DL Power
9.2.1.21

–

>>HS-SICH Information 7.68Mcps

0..1


–

>>>HS-SICH ID
M

9.2.3.5Gb

–

>>>Time Slot
O

9.2.3.23

–

>>>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

Delete from HS-SCCH Resource Pool

0..<maxnoof HSSCCHs>

For 1.28Mcps TDD ,see note 3 below
GLOBAL
reject
>HS-SCCH ID
M

9.2.3.5Ga
For 1.28Mcps TDD, if the Extended HS-SCCH ID IE is included in the Delete from HS-SCCH Resource Pool IE, the HS-SCCH ID IE shall be ignored
–

>Extended HS-SCCH ID
O

9.2.3.5J
Applicable to 1.28Mcps TDD only, the Extended HS-SCCH ID IE shall be used if the HS-SCCH identity has a value larger than 31.
YES
ignore
Configuration Generation ID
O

9.2.1.16

YES
reject
E-PUCH Information

0..1

3.84Mcps TDD only
GLOBAL
reject
>LTGI Presence
M

9.2.3.58

–

>SNPL Reporting Type
M

9.2.3.62

–

>Midamble Shift And Burst Type
M

9.2.3.7

–

>E-PUCH Timeslot Information

1..<maxNrOfE-PUCHSlots>


–

>>Time Slot
M

9.2.3.23



Add to E-AGCH Resource Pool

0..1

3.84Mcps TDD only
GLOBAL
reject
>E-AGCH Information

0..<maxnoofEAG CHs>


–

>>E-AGCH ID TDD
M

9.2.3.51

–

>>Time Slot
M

9.2.3.23

–

>>Midamble Shift And Burst Type
M

9.2.3.7

–

>>TDD Channelisation Code
M

9.2.3.19

–

>>Maximum E-AGCH Power
M

DL Power
9.2.1.21

–

Modify E-AGCH Resource Pool

0..1

3.84Mcps TDD only
GLOBAL
reject
>E-AGCH Information

0..<maxnoofEAG CHs>


–

>>E-AGCH ID TDD
M

9.2.3.51

–

>>Time Slot
O

9.2.3.23

–

>>Midamble Shift And Burst Type
O

9.2.3.7

–

>>TDD Channelisation Code
O

9.2.3.19

–

>>Maximum E-AGCH Power
O

DL Power
9.2.1.21

–

Delete from E-AGCH Resource Pool

0..<maxnoofEAG CHs>


GLOBAL
reject
>E-AGCH ID TDD
M

9.2.3.51

–

E-HICH Information

0..1

3.84Mcps TDD only
GLOBAL
reject
>Midamble Shift And Burst Type
M

9.2.3.7

–

>TDD Channelisation Code
M

9.2.3.19

–

>Maximum E-HICH Power
M

DL Power
9.2.1.21

–

Maximum Generated Received Total Wide Band Power in Other Cells
O

9.2.3.63
Applicable to 3.84Mcps and 7.68 Mcps TDD only
YES
reject
E-PUCH Information 7.68Mcps

0..1

7.68Mcps TDD only
GLOBAL
reject
>LTGI Presence
M

9.2.3.58

–

>SNPL Reporting Type
M

9.2.3.62

–

>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>E-PUCH Timeslot Information

1..<maxNrOfE-PUCHSlots>


–

>>Time Slot
M

9.2.3.23

–

Add to E-AGCH Resource Pool 7.68Mcps

0..1

7.68Mcps TDD only
GLOBAL
reject
>E-AGCH Information

0..<maxnoofEAG CHs>


–

>>E-AGCH ID TDD
M

9.2.3.51

–

>>Time Slot
M

9.2.3.23

–

>>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

>>Maximum E-AGCH Power
M

DL Power
9.2.1.21

–

Modify E-AGCH Resource Pool 7.68Mcps

0..1

7.68Mcps TDD only
GLOBAL
reject
>E-AGCH Information

0..<maxnoofEAG CHs>


–

>>E-AGCH ID TDD
M

9.2.3.51

–

>>Time Slot
O

9.2.3.23

–

>>Midamble Shift And Burst Type 7.68Mcps
O

9.2.3.35

–

>>TDD Channelisation Code 7.68Mcps
O

9.2.3.34

–

>>Maximum E-AGCH Power
O

DL Power
9.2.1.21

–

E-HICH Information 7.68Mcps

0..1

7.68Mcps TDD only
GLOBAL
reject
>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>TDD Channelisation Code 7.68Mcps
M

9.2.3.34

–

>Maximum E-HICH Power
M

DL Power
9.2.1.21

–

E-PUCH Information 1.28Mcps

0..1

1.28Mcps TDD only
GLOBAL
reject
>LTGI Presence
M

9.2.3.58

–

>SNPL Reporting Type
M

9.2.3.62

–

>E-PUCH Timeslot information 1.28Mcps per UARFCN

0..<maxFrequencyinCell>

See note 2 below


>>E-PUCH Timeslot Information 1.28Mcps

0..<maxNrOfE-PUCHSlotsLCR>


–

>>>Time Slot LCR
M

9.2.3.24A

–

>>>Midamble Shift LCR
M

9.2.3.7A

–

>>>Codes LCR

1..<maxNrOfEPUCHcodes>


–

>>>>TDD Channelisation Code
M

9.2.3.19

–

>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Mandatory for 1.28Mcps TDD when using multiple frequencies.
YES
ignore
Add to E-AGCH Resource Pool 1.28Mcps

0..1

1.28Mcps TDD only
GLOBAL
reject
>E-AGCH Information 1.28Mcps

1..<maxnoofEAG CHs>


–

>>E-AGCH ID TDD
M

9.2.3.51

–

>>Time Slot LCR
M

9.2.3.24A

–

>>Midamble Shift LCR
M

9.2.3.7A

–

>>First TDD Channelisation Code
M

TDD Channelisation Code 9.2.3.19

–

>>Second TDD Channelisation Code
M

TDD Channelisation Code 9.2.3.19

–

>>Maximum E-AGCH Power
M

DL Power
9.2.1.21

–

>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Mandatory for 1.28Mcps TDD when using multiple frequencies.
YES
ignore
Modify E-AGCH Resource Pool 1.28Mcps

0..1

1.28Mcps TDD only
GLOBAL
reject
>E-AGCH Information 1.28Mcps

1..<maxnoofEAG CHs>


–

>>E-AGCH ID TDD
M

9.2.3.51

–

>>Time Slot LCR
O

9.2.3.24A

–

>>Midamble Shift LCR
O

9.2.3.7A

–

>>First TDD Channelisation Code
O

TDD Channelisation Code 9.2.3.19

–

>>Second TDD Channelisation Code
O

TDD Channelisation Code 9.2.3.19

–

>>Maximum E-AGCH Power
O

DL Power
9.2.1.21

–

>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Mandatory for 1.28Mcps TDD when using multiple frequencies.
YES
ignore
Add to E-HICH Resource Pool 1.28Mcps

0..1

1.28Mcps TDD only
GLOBAL
reject
>E-HICH Information 1.28Mcps

1..<maxNrOfEHICHs>


–

>>E-HICH ID TDD
M

9.2.3.51a
If the Extended E-HICH ID TDD IE is included in the E-HICH Information 1.28Mcps IE, the E-HICH ID TDD IE shall be ignored.
–

>>E-HICH Type
M

9.2.3.68

–

>>TDD Channelisation Code
M

9.2.3.19

–

>>Time Slot LCR
M

9.2.3.24A

–

>>Midamble Shift LCR
M

9.2.3.7A

–

>>Maximum E-HICH Power
M

DL Power
9.2.1.21

–

>>Extended E-HICH ID TDD
O

9.2.3.51b
Applicable to 1.28Mcps TDD only, the Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31.
YES
ignore
>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Mandatory for 1.28Mcps TDD when using multiple frequencies.
YES
ignore
Modify E-HICH Resource Pool 1.28Mcps

0..1

1.28Mcps TDD only
GLOBAL
reject
>E-HICH Information 1.28Mcps

1..<maxNrOfEHICHs>


–

>>E-HICH ID TDD
M

9.2.3.51a
If the Extended E-HICH ID TDD IE is included in the E-HICH Information 1.28Mcps IE, the E-HICH ID TDD IE shall be ignored.
–

>>E-HICH Type
O

9.2.3.68

–

>>TDD Channelisation Code
O

9.2.3.19

–

>>Time Slot LCR
O

9.2.3.24A

–

>>Midamble Shift LCR
O

9.2.3.7A

–

>>Maximum E-HICH Power
O

DL Power
9.2.1.21

–

>>Extended E-HICH ID TDD
O

9.2.3.51b
Applicable to 1.28Mcps TDD only, the Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31.
YES
ignore
>>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Mandatory for 1.28Mcps TDD when using multiple frequencies.
YES
ignore
Delete from E-HICH Resource Pool 1.28Mcps

0..<maxNrOfEHICHs>

1.28Mcps TDD only
GLOBAL
reject
>E-HICH ID TDD
M

9.2.3.51a
If the Extended E-HICH ID TDD IE is included in the Delete from E-HICH Resource Pool 1.28Mcps IE, the E-HICH ID TDD IE shall be ignored.
–

>Extended E-HICH ID TDD
O

9.2.3.51b
Applicable to 1.28Mcps TDD only, the Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31.
YES
ignore
SYNC_UL Partition Information

0..1

Applicable to 1.28Mcps TDD to indicate the SYNC_UL partition information for the Primary Frequency. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
GLOBAL
reject
>E-RUCCH SYNC_UL codes bitmap 
M

BIT STRING SIZE(8))
Each bit indicates availability of a SYNC_UL code, where the SYNC_UL codes are numbered "code 0" to "code 7".
The value 1 of a bit indicates that the corresponding SYNC_UL code can be used.
The value 0 of a bit indicates that the corresponding SYNC_UL code can not be used.
–

Maximum Target Received Total Wide Band Power LCR
O

9.2.3.69
1.28Mcps TDD only
YES
reject
HS-DSCH Common System Information LCR
O

9.2.3.72
1.28Mcps TDD only
YES
reject
Common MAC Flows To Delete LCR
O

9.2.3.78
1.28Mcps TDD only
YES
reject
HS-DSCH Paging System Information LCR
O

9.2.3.73
1.28Mcps TDD only
YES
reject
Paging MAC Flows to Delete LCR
O

9.2.3.85
1.28Mcps TDD only
YES
reject
Common E-DCH System Information LCR
O

9.2.3.79
1.28Mcps TDD only
YES
reject
Common UL MAC Flows to Delete LCR
O

Common MAC Flows To Delete LCR
9.2.3.78
1.28Mcps TDD only
YES
reject
Common E-DCH MAC-d Flows to Delete LCR
O

9.2.3.86
1.28Mcps TDD only
YES
reject
Enhanced UE DRX Information LCR
O

9.2.3.82
1.28Mcps TDD only
YES
reject
Add to Non-HS-SCCH associated HS-SICH Resource Pool

0..1

1.28Mcps TDD only
GLOBAL
reject
 >Non-HS-SCCH associated HS-SICH Information

0..<maxNoOfNon-HS-SCCH-Assosiated-HS-SICH>

See note 4 below
–

  >>Non-HS-SCCH associated HS-SICH ID
M

INTEGER (0..255)

–

  >>Time Slot LCR
M

9.2.3.24A

–

  >>Midamble Shift LCR
M

9.2.3.7A

–

  >>TDD Channelisation Code
M

9.2.3.19

–

  >>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Mandatory for 1.28Mcps TDD when using multiple frequencies.
–

Modify Non-HS-SCCH associated HS-SICH Resource Pool

0..1

1.28Mcps TDD only
GLOBAL
reject
 >Non-HS-SCCH associated HS-SICH Information

0..<maxNoOfNon-HS-SCCH-Assosiated-HS-SICH>

See note 4 below
–

  >>Non-HS-SCCH associated HS-SICH ID
M

INTEGER (0..255)

–

  >>Time Slot LCR
O

9.2.3.24A

–

  >>Midamble Shift LCR
O

9.2.3.7A

–

  >>TDD Channelisation Code
O

9.2.3.19

–

  >>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Mandatory for 1.28Mcps TDD when using multiple frequencies.
–

Delete from Non-HS-SCCH associated HS-SICH Resource Pool

0..<maxNoOfNon-HS-SCCH-Assosiated-HS-SICH>

1.28Mcps TDD only.
See note 4 below
GLOBAL
reject
 >Non-HS-SCCH associated HS-SICH ID
M

INTEGER (0..255)

–

Power Control GAP for CELL_FACH
O

INTEGER (1..255)
1) Unit: Number of subframes.
Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
YES
ignore
Maximum RTWP per UARFCN information LCR

0..< maxFrequencyinCell>

1.28Mcps TDD only
GLOBAL
ignore
 >UARFCN
M

9.2.1.65

–

 >Maximum Target Received Total Wide Band Power LCR
M

9.2.3.69
This IE shall be ignored if IE Maximum Target Received Total Wide Band Power per CELL PORTION LCR is included.
–

>Maximum Target Received Total Wide Band Power per CELL PORTION LCR

0..<maxNrOfCellPortionsPerCellLCR>


GLOBAL
ignore
>>Cell Portion LCR ID
M

9.2.3.107

–

>>Maximum Target Received Total Wide Band Power LCR
M

9.2.3.69

–

Out-of-sync Detection Window
O

ENUMERATED (40, 80, 160, 320, 640, 
…)
Unit: ms
Applicable to 1.28Mcps TDD.
YES
reject
Treset Usage Indicator
O

NULL
Applicable to 1.28Mcps TDD only
YES
ignore
In Sync Indication Information LCR
O

9.2.3.123
Applicable to 1.28Mcps TDD only
YES
ignore

Note 1: 	This information element is a simplified representation of the ASN.1. The choice is in reality performed through the use of ProtocolIE-Single-Container within the ASN.1.
Note 2: 	This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxFrequencyinCell are represented by separate ASN.1 structures with different criticalities.
Note 3: 	This information element is a simplified representation of the ASN.1. Repetitions 1 to 32 and repetitions 33 to maxNrOfHSSCCHs are represented by separate ASN.1 structures. 
Note 4: 	This information element is a simplified representation of the ASN.1. Repetitions 1 to 4 and repetitions 5 to maxNoOfNon-HS-SCCH-Assosiated-HS-SICH are represented by separate ASN.1 structures.
Range Bound
Explanation
maxNrOfPDSCHSets
Maximum number of PDSCH Sets in a cell.
maxNrOfPDSCHs
Maximum number of PDSCH in a cell.
maxNrOfPDSCHSets
Maximum number of PUSCH Sets in a cell.
maxNrOfPUSCHs
Maximum number of PUSCH in a cell.
maxNrOfDLTSs
Maximum number of Downlink time slots in a cell for 3.84Mcps TDD.
maxNrOfDLTSLCRs
Maximum number of Downlink time slots in a cell for 1.28Mcps TDD.
maxNrOfULTSs
Maximum number of Uplink time slots in a cell for 3.84Mcps TDD.
maxNrOfULTSLCRs
Maximum number of Uplink time slots in a cell for 1.28Mcps TDD
maxNrOfHSSCCHs
Maximum number of HS-SCCHs in a Cell
maxNrOfHSPDSCHs
Maximum number of HS-PDSCHs in one time slot of a Cell for 1.28Mcps TDD and 3.84Mcps TDD
maxNrOfHSPDSCHs768
Maximum number of HS-PDSCHs in one time slot of a Cell for  7.68Mcps TDD
maxNrOfEAGCHs
Maximum number of E-AGCHs in a Cell
maxNrOfE-PUCHSlots
Maximum number of E-PUCH time slots in a Cell for 3.84Mcps TDD and 7.68Mcps TDD
maxNrOfEHICHs
Maximum number of E-HICHs in a Cell
maxNrOfE-PUCHSlotsLCR
Maximum number of E-PUCH time slots in a Carrier for 1.28Mcps  TDD
maxNrOfEPUCHcodes
Maximum number of E-PUCH codes in one time slot for 1.28Mcps TDD
maxFrequencyinCell
Maximum number of Frequencies that can be defined in a Cell
MaxNrOfCellPortionsPerCellLCR
Maximum number of Cell Portions in a cell for 1.28 Mcps TDD
maxNoOfNon-HS-SCCH-Assosiated-HS-SICH
Maximum number of Non-HS-SCCH associated HS-SICH in a cell for 1.28 Mcps TDD

9.1.63	PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID 
M

9.2.1.62

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore
E-HICH Time Offset
O

9.2.3.59
Applicable to 3.84Mcps and 7.68 Mcps TDD only
YES
reject
E-HICH Time Offset LCR per UARFCN

0.. < maxFrequencyinCell>

1.28Mcps TDD only.
See note 1 below
EACH
reject
>E-HICH Time Offset LCR
M

9.2.3.59a

–

>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15])..
Mandatory for 1.28Mcps TDD when using multiple frequencies.
–

HS-DSCH Common System Information Response
O

9.2.2.77
FDD only
YES
ignore
HS-DSCH Paging System Information Response
O

9.2.2.78
FDD only
YES
ignore
Common E-DCH System Information Response
O

9.2.2.104
FDD only
YES
Ignore
HS-DSCH Common System Information Response LCR
O

9.2.3.74
1.28Mcps TDD only
YES
ignore
HS-DSCH Paging System Information Response LCR
O

9.2.3.75
1.28Mcps TDD only
YES
ignore
Common E-DCH System Information Response LCR
O

9.2.3.80
1.28Mcps TDD only
YES
Ignore
Common E-RGCH Info
O

9.2.2.189
FDD only
YES
ignore
Note 1	This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxFrequencyinCell are represented by separate ASN.1 structures with different criticalities.

Range Bound
Explanation
maxFrequencyinCell
Maximum number of Frequencies that can be defined in a Cell

9.1.64	PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID 
M

9.2.1.62

–

CHOICE Cause Level
M



YES
ignore
>General






>>Cause
M

9.2.1.6

–

>Set Specific



TDD Only


>>Unsuccessful DL Shared Channel Set

0..<maxNrOfPDSCHSets>


EACH
ignore
>>>PDSCH Set ID
M

9.2.3.11

–

>>>Cause 
M

9.2.1.6

–

>>Unsuccessful UL Shared Channel Set

0..<maxNrOfPDSCHSets>


EACH
ignore
>>>PUSCH Set ID
M

9.2.3.13

–

>>>Cause
M

9.2.1.6

–

>Extension Cause Level






>>UARFCN Specific

1

Applicable to 1.28Mcps TDD only when using multiple frequencies
YES
ignore
>>>Unsuccessful UARFCN

0.. <maxFrequencyinCell>


EACH
ignore
>>>>UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Used to indicate the carrier on which HSDPA or E-DCH related resources configuration failure occurs. 
–

>>>>Cause 
M

9.2.1.6

–

>>>>HS-Cause 
O

Cause
9.2.1.6
Used to indicate the cause of HSDPA configuration. failure
YES
ignore
>>>>E-Cause 
O

Cause
9.2.1.6
Used to indicate the cause of E-DCH related configuration failure.
YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore
E-HICH Time Offset LCR per UARFCN

0.. < maxFrequencyinCell>

1.28Mcps TDD only
EACH
ignore
>E-HICH Time Offset LCR
M

9.2.3.59a



>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Used to indicate the carrier on which HSDPA or E-DCH related resources configuration failure occurs.


Common System Information Response LCR

0..1


YES
ignore
>HS-DSCH Common System Information Response LCR
M

9.2.3.74
1.28Mcps TDD only


>HS-DSCH Paging System Information Response LCR
O

9.2.3.75
1.28Mcps TDD only


>Common E-DCH System Information Response LCR
M

9.2.3.80
1.28Mcps TDD only



Range Bound
Explanation
maxNrOfPDSCHSets
Maximum number of PDSCH Sets in a cell
maxNrOfPDSCHSets
Maximum number of PUSCH Sets in a cell
maxFrequencyinCell
Maximum number of Frequencies that can be defined in a Cell

9.1.65	RESET REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CHOICE Reset Indicator 
M



YES
ignore
>Communication Context






>>Communication Context Information

1..<maxCommunicationContext>


EACH
reject
>>>CHOICE Communication Context Type
M



_

>>>>CRNC Communication Context






>>>>>CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
_

>>>>Node B Communication Context






>>>>>Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC" shall not be used.
_

>Communication Control Port






>>Communication Control Port Information

1..<maxCCPinNodeB>


EACH
reject
>>>Communication Control Port ID
M

9.2.1.15

_

>Node B


NULL




Range Bound
Explanation
maxCommunicationContext
Maximum number of Communication Contexts that can exist in the Node B
maxCCPinNodeB
Maximum number of Communication Control Ports that can exist in the Node B

9.1.66	RESET RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.67	DL POWER TIMESLOT CONTROL REQUEST [TDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All NBCC” shall not be used.
YES
ignore
DL Time Slot ISCP Info
O

9.2.3.4F
Mandatory for 3.84Mcps TDD and 7.68Mcps TDD. Not Applicable to 1.28Mcps TDD.
YES
ignore
DL Time Slot ISCP Info LCR
O

9.2.3.4P
Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD and 7.68Mcps TDD.
YES
ignore
Primary CCPCH RSCP
O

9.2.3.11A

YES
ignore
Primary CCPCH RSCP Delta
O

9.2.3.11B

YES
ignore

9.1.68	RADIO LINK PREEMPTION REQUIRED INDICATION
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18

YES
ignore
RL Information

0..<maxNrOfRLs>


EACH
ignore
>RL ID
M

9.2.1.53

–


Range Bound
Explanation
maxNrOfRLs
Maximum number of radio links for one UE

9.1.69	INFORMATION EXCHANGE INITIATION REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Information Exchange ID
M

9.2.1.36C

YES
reject
CHOICE Information Exchange Object Type
M



YES
reject
>Cell






>>C-ID
M

9.2.1.9

–

Information Type
M

9.2.1.36D

YES
reject
Information Report Characteristics
M

9.2.1.36B

YES
reject

9.1.70	INFORMATION EXCHANGE INITIATION RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Information Exchange ID
M

9.2.1.36C

YES
ignore
CHOICE Information Exchange Object Type
O



YES
ignore
>Cell






>>Requested Data Value 
M

9.2.1.51A

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.71	INFORMATION EXCHANGE INITIATION FAILURE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Information Exchange ID
M

9.2.1.36C

YES
ignore
Cause
M

9.2.1.6

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.72	INFORMATION REPORT
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Information Exchange ID
M

9.2.1.36C

YES
ignore
CHOICE Information Exchange Object Type
M



YES
ignore
>Cell






>>Requested Data Value Information
M

9.2.1.51B

–


9.1.73	INFORMATION EXCHANGE TERMINATION REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Information Exchange ID
M

9.2.1.36C

YES
ignore

9.1.74	INFORMATION EXCHANGE FAILURE INDICATION
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Information Exchange ID
M

9.2.1.36C

YES
ignore
Cause
M

9.2.1.6

YES
ignore

9.1.75	CELL SYNCHRONISATION INITIATION REQUEST [TDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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
Cell Sync Burst Repetition Period
M

9.2.3.4J

YES
reject
Time Slot Information

0..15

Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD.
GLOBAL
reject
>Time Slot
M

9.2.3.23

–

Cell Sync Burst Transmission Initiation Information

0..1

Applicable to 3.84Mcps TDD only
GLOBAL
reject
>CSB Transmission ID
M

9.2.3.4N

–

>SFN
M

9.2.1.53A

–

>Cell Sync Burst Code
M

9.2.3.4G

–

>Cell Sync Burst Code Shift
M

9.2.3.4H

–

>Initial DL Transmission Power
M

DL Power
9.2.1.21

–

Cell Sync Burst Measurement Initiation Information

0..1

Applicable to 3.84Mcps TDD only
GLOBAL
reject
>CSB Measurement ID
M

9.2.3.4I

–

>Cell Sync Burst Code
M

9.2.3.4G

–

>Cell Sync Burst Code Shift
M

9.2.3.4H

–

>Synchronisation Report Type
M

9.2.3.18E

–

>SFN
O

9.2.1.53A

–

>Synchronisation Report Characteristics
M

9.2.3.18D

–

SYNC_DL Code Transmission Initiation Information LCR

0..1

Applicable to 1.28Mcps TDD only
GLOBAL
reject
>CSB Transmission ID
M

9.2.3.4N

–

>SFN
M

9.2.1.53A

–

>UARFCN
M

9.2.1.65

–

>SYNC_DL Code ID
M

9.2.3.18B

–

>DwPCH Power
M

9.2.3.5B

–

SYNC_DL Code Measurement Initiation Information LCR

0..1

Applicable to 1.28Mcps TDD only
GLOBAL
reject
>CSB Measurement ID
M

9.2.3.4I

–

>SFN
O

9.2.1.53A

–

>UARFCN
M

9.2.1.65

–

>SYNC_DL Code ID
M

9.2.3.18B

–

>Synchronisation Report Type
M

9.2.3.18E

–

>Synchronisation Report Characteristics
M

9.2.3.18D

–


9.1.76	CELL SYNCHRONISATION INITIATION RESPONSE [TDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.77	CELL SYNCHRONISATION INITIATION FAILURE [TDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Cause
M

9.2.1.6

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore


9.1.78	CELL SYNCHRONISATION RECONFIGURATION REQUEST [TDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
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
Time Slot
M

9.2.3.23
Applicable to 3.84Mcps TDD only.
For 1.28Mcps TDD, the CRNC should set this to 0 and the Node B shall ignore it
YES
reject
Number Of Cycles Per SFN Period
M

9.2.3.7B

YES
reject
Number Of Repetitions Per Cycle Period
M

9.2.3.7C

YES
reject
Cell Sync Burst Transmission Reconfiguration Information

0..<maxNrOfCellSyncBursts>

Applicable to 3.84Mcps TDD only
GLOBAL
reject
>CSB Transmission ID
M

9.2.3.4N

–

>Sync Frame Number To Transmit 
M

Sync Frame Number
9.2.3.18C

–

>Cell Sync Burst Code
O

9.2.3.4G

–

>Cell Sync Burst Code Shift
O

9.2.3.4H

–

>DL Transmission Power
O

DL Power
9.2.1.21

–

Cell Sync Burst Measurement Reconfiguration Information

0..1

Applicable to 3.84Mcps TDD only
YES
reject
>Cell Sync Burst Measurement Information

1..<maxNrOfCellSyncBursts>


GLOBAL
reject
>>Sync Frame Number To Receive
M

Sync Frame Number
9.2.3.18C

–

>>Cell Sync Burst Information

1..<maxNrOfReceptsPerSyncFrame>


–

>>>CSB Measurement ID
M

9.2.3.4I

–

>>>Cell Sync Burst Code
M

9.2.3.4G

–

>>>Cell Sync Burst Code Shift
M

9.2.3.4H

–

>Synchronisation Report Type
O

9.2.3.18E

YES
reject
>Synchronisation Report Characteristics
O

9.2.3.18D

YES
reject
Number Of Subcycles Per Cycle Period
O

9.2.3.7D
Applicable to 1.28Mcps TDD only
YES
reject
SYNC_DL Code Transmission Reconfiguration Information LCR

0..<maxNrOfSyncFramesLCR>

Applicable to 1.28Mcps TDD only
GLOBAL
reject
>CSB Transmission ID
M

9.2.3.4N

–

>Sync Frame Number For Transmission
M

Sync Frame Number
9.2.3.18C

–

>UARFCN
M

9.2.1.65

–

>SYNC_DL Code ID
O

9.2.3.18B

–

>DwPCH Power
O

9.2.3.5B

–

SYNC_DL Code Measurement Reconfiguration Information LCR

0..1

Applicable to 1.28Mcps TDD only
YES
reject
>SYNC_DL Code Measurement Information LCR

1..<maxNrOfSyncDLCodesLCR>


–

>>Sync Frame Number To Receive
M

Sync Frame Number
9.2.3.18C

–

>>Sync_DLCode Information LCR

1..<maxNrOfReceptionsperSyncFrameLCR>


–

>>>CSB Measurement ID
M

9.2.3.4I

–

>>>SYNC_DL Code ID
M

9.2.3.18B

–

>>>UARFCN
M

9.2.1.65

–

>>>Propagation Delay Compensation
O

Timing Adjustment Value LCR 9.2.3.22b

–

>Synchronisation Report Type
O

9.2.3.18E

YES
reject
>Synchronisation Report Characteristics
O

9.2.3.18D

YES
reject

Range Bound
Explanation
maxNrOfCellSyncBursts
Maximum number of cell synchronisation bursts per cycle for 3.84Mcps TDD
maxNrOfReceptsPerSyncFrame
Maximum number of cell synchronisation burst receptions per Sync Frame for 3.84Mcps TDD
maxNrOfSyncFramesLCR
Maximum number of Sync Frames per subcycle for 1.28Mcps TDD
maxNrOfReceptionsperSyncFrameLCR
Maximum number of SYNC_DL Code ID receptions per Sync Frame for 1.28Mcps TDD
maxNrOfSyncDLCodesLCR
Maximum number of SYNC_DL Codes for 1.28Mcps TDD

9.1.79	CELL SYNCHRONISATION RECONFIGURATION RESPONSE [TDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.80	CELL SYNCHRONISATION RECONFIGURATION FAILURE [TDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Cause
M

9.2.1.6

YES
ignore
Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.81	CELL SYNCHRONISATION REPORT [TDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Cell Synchronisation Information

1..<maxCellinNodeB>


GLOBAL
ignore
>C-ID
M

9.2.1.9

YES
ignore
>CHOICE Synchronisation Report Type
O



YES
ignore
>>Initial Phase or Steady-State Phase






>>>Cell Sync Burst Measured Information

0..<maxNrOfCellSyncBursts>

Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD.
–

>>>>SFN
M

9.2.1.53A

–

>>>>Cell Sync Burst Information

1..<maxNrOfReceptsPerSyncFrame>


–

>>>>>CHOICE Cell Sync Burst Availability Indicator
M



–

>>>>>>Cell Sync Burst Available






>>>>>>>Cell Sync Burst Timing
M

9.2.3.4L

–

>>>>>>>Cell Sync Burst SIR
M

9.2.3.4K

–

>>>>>>Cell Sync Burst Not Available


NULL



>>>Accumulated Clock Update
O

Timing Adjustment Value 9.2.3.22a

YES
ignore
>>>SYNC_DL Codes Measured Information

0..<maxNrOfSyncFramesLCR>

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD.
YES
ignore
>>>>SFN
M

9.2.1.53A

–

>>>>SYNC_DL Code Information

1..<maxNrOfReceptionsperSyncFrameLCR>


–

>>>>>CHOICE SYNC_DL Code Availability Indicator
M



–

>>>>>>SYNC_DL Code Available






>>>>>>>SYNC_DL Code ID Timing
M

Cell Sync Burst Timing LCR 9.2.3.4La

–

>>>>>>>SYNC_DL Code ID SIR
M

Cell Sync Burst SIR 9.2.3.4K

–

>>>>>>SYNC_DL Code Not Available


NULL



>>Late-Entrant Cell


NULL



>>Frequency Acquisition


NULL




Range Bound
Explanation
maxCellinNodeB
Maximum number of Cells in a Node B
maxNrOfCellSyncBursts
Maximum number of cell synchronisation bursts per cycle for 3.84Mcps TDD
maxNrOfReceptsPerSyncFrame
Maximum number of cell synchronisation burst receptions per Sync Frame for 3.84Mcps TDD
maxNrOfSyncFramesLCR
Maximum number of SYNC Frames per measurement reporting period for 1.28Mcps TDD
maxNrOfReceptionsperSyncFrameLCR
Maximum number of SYNC_DL Code ID receptions per Sync Frame for 1.28Mcps TDD

9.1.82	CELL SYNCHRONISATION TERMINATION REQUEST [TDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

C-ID
M

9.2.1.9

YES
ignore
CSB Transmission ID
O

9.2.3.4N

YES
ignore
CSB Measurement ID
O

9.2.3.4I

YES
ignore

9.1.83	CELL SYNCHRONISATION FAILURE INDICATION [TDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

C-ID
M

9.2.1.9

YES
ignore
CSB Transmission ID
O

9.2.3.4N

YES
ignore
CSB Measurement ID
O

9.2.3.4I

YES
ignore
Cause
M

9.2.1.6

YES
ignore

9.1.84	CELL SYNCHRONISATION ADJUSTMENT REQUEST [TDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Cell Adjustment Information

1..<maxCellinNodeB>


EACH
ignore
>C-ID
M

9.2.1.9

–

>Frame Adjustment Value
O

9.2.3.5C

–

>Timing Adjustment Value
O

9.2.3.22a
Applicable to 3.84Mcps TDD only
–

>DL Transmission Power
O

DL Power
9.2.1.21
Applicable to 3.84Mcps TDD only
–

>SFN
O

9.2.1.53A

–

>DwPCH Power
O

9.2.3.5B
Applicable to 1.28Mcps TDD only
YES
ignore
>Timing Adjustment Value LCR
O

9.2.3.22b
Applicable to 1.28Mcps TDD only
YES
ignore

Range Bound
Explanation
maxCellinNodeB
Maximum number of Cells in a Node B

9.1.85	CELL SYNCHRONISATION ADJUSTMENT RESPONSE [TDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

9.1.86	CELL SYNCHRONISATION ADJUSTMENT FAILURE [TDD]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

CHOICE Cause Level
M



YES
ignore
>General






>>Cause
M

9.2.1.6

–

>Cell Specific






>>Unsuccessful Cell Information Response

1..<maxCellinNodeB>


EACH
ignore
>>>C-ID
M

9.2.1.9

–

>>>Cause
M

9.2.1.6

–

Criticality Diagnostics
O

9.2.1.17

YES
ignore

Range Bound
Explanation
maxCellinNodeB
Maximum number of Cells in a Node B

9.1.87	BEARER REARRANGEMENT INDICATION
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
Signalling Bearer Request Indicator
O

9.2.1.55A

YES
ignore
DCHs To Re-arrange

0..<maxNrOfDCHs>


GLOBAL
ignore
>DCH ID
M

9.2.1.20

–

DSCHs To Re-arrange

0..<maxNrOfDSCHs>

TDD only
GLOBAL
ignore
>DSCH ID
M

9.2.3.5a

–

USCHs To Re-arrange

0..<maxNrOfUSCHs>

TDD only
GLOBAL
ignore
>USCH ID
M

9.2.3.27

–

HS-DSCHs MAC-d Flow To Re-arrange

0..<maxNrOfMACdFlows>


GLOBAL
ignore
>HS-DSCH MAC-d Flow ID
M

9.2.1.31I

–

E-DCHs MAC-d Flow To Re-arrange

0..<maxNrOfEDCHMACdFlows>


GLOBAL
ignore
>E-DCH MAC-d Flow ID
M

9.2.1.29ad

–

>Additional E-DCH Cell Information Bearer Rearrangement

0..<maxNrOfEDCH-1

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.
EACH
ignore
>>Transport Bearer Rearrangement Indicator for Secondary E-DCH Separate Mode 
M

Enumerated ENUMERATED (bearer for primary carrier, bearer for secondary carrier, bearers for both primary and secondary carriers,…)

–


Range bound
Explanation
maxNrOfDCHs
Maximum number of DCHs for a UE
maxNrOfDSCHs
Maximum number of DSCHs for a UE
maxNrOfUSCHs
Maximum number of USCHs for a UE
maxNrOfMACdFlows
Maximum number of HS-DSCH MAC-d flows
maxNrOfEDCHMACdFlows
Maximum number of E-DCH MAC-d flows
maxNrOfEDCH-1
Maximum number of uplink frequencies -1 for E-DCH for one UE

9.1.88	RADIO LINK ACTIVATION COMMAND
9.1.88.1	FDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48

YES
ignore
Delayed Activation Information

1..<maxNrOfRLs>


EACH
ignore
>RL ID
M

9.2.1.53

–

>Delayed Activation Update
M

9.2.1.24D

–


Range Bound
Explanation
maxNrOfRLs
Maximum number of RLs for one UE

9.1.88.2	TDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48

YES
ignore
Delayed Activation Information

1..<maxNrOfRLs>


EACH
ignore
>RL ID
M

9.2.1.53

–

>Delayed Activation Update
M

9.2.1.24D

–


Range Bound
Explanation
maxNrOfRLs
Maximum number of RLs for one UE

9.1.89	RADIO LINK PARAMETER UPDATE INDICATION
9.1.89.1	FDD Message
IE/Group name
Presence
Range
IE Type and Reference
Semantic Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID 
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
HS-DSCH FDD Update Information
O

9.2.2.18Ea

YES
ignore
E-DCH FDD Update Information
O

9.2.2.13DA

YES
ignore
Additional HS Cell Information RL Param Upd

0..<maxNrOfHSDSCH-1>

For secondary serving HS-DSCH cell. Max 7 in this 3GPP release. 
EACH
ignore
>HS-PDSCH RL ID
M

RL ID 9.2.1.53

–

>HS-DSCH FDD Secondary Serving Update Information
M

9.2.2.18Eaa

–

Additional E-DCH Cell Information RL Param Upd

0..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release. 
EACH
ignore
>>Additional E-DCH FDD  Update Information
M

9.2.2.138

–

CPC Recovery Report
O

ENUMERATED(Initiated, …)

YES
ignore
UL CLTD State Update Information 
O

9.2.2.155

YES
ignore
UE Measurement Forwarding
O

9.2.2.207

YES
ignore
CFN
O

9.2.1.7

YES
ignore

Range Bound
Explanation
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE
maxNrOfEDCH-1
Maximum number of uplink frequencies -1 for E-DCH for one UE

9.1.89.2	TDD Message
IE/Group name
Presence
Range
IE Type and Reference
Semantic Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID 
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
HS-DSCH TDD Update Information
O

9.2.3.5GA

YES
ignore

9.1.90	MBMS NOTIFICATION UPDATE COMMAND
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

C-ID
M

9.2.1.9

YES
ignore
Common Physical Channel ID
M

9.2.1.13

YES
ignore
Modification Period
O

9.2.1.47a
This IE shall be present in the very first message
YES
ignore
MICH CFN
M

9.2.1.46a

YES
ignore
NI Information

1..<maxNrOfNIs>


GLOBAL
ignore
>NI
M

9.2.1.47F

–


Range Bound
Explanation
maxNrOfNIs
Maximum number of NIs

9.1.91	UE STATUS UPDATE COMMAND
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Cell E-RNTI Status Information

1..<maxCellinNodeB>


EACH
ignore
>C-ID
M

9.2.1.9

–

>Vacant E-RNTI

1..<maxErntiToRelease>


EACH
ignore
>>E-RNTI
M

9.2.1.75




Range Bound
Explanation
maxCellinNodeB
Maximum number of Cells in a Node B
maxErntiToRelease
Maximum number of E-RNTI to release per cell

9.1.92	SECONDARY UL FREQUENCY REPORT
9.1.92.1	FDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

Node B Communication Context ID
M

9.2.1.48
The reserved value "All CRNCCC" shall not be used.
YES
ignore
Activation Information
M

9.2.2.128

YES
ignore

9.1.93	SECONDARY UL FREQUENCY UPDATE INDICATION
9.1.93.1	FDD Message
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
ignore
Transaction ID
M

9.2.1.62

–

CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
YES
ignore
Activation Information
M

9.2.2.128

YES
ignore

9.1.94	UE STATUS UPDATE CONFIRM REQUEST
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

Cell E-RNTI Status Information

1..<maxCellinNodeB>


EACH
ignore
>C-ID
M

9.2.1.9

–

>Vacant E-RNTI 

1..<maxErntiToRelease >


EACH
ignore
>>E-RNTI
M

9.2.1.75

-
-

Range Bound
Explanation
maxCellinNodeB
Maximum number of Cells in a Node B
maxErntiToRelease
Maximum number of E-RNTI to release per cell

9.1.95	UE STATUS UPDATE CONFIRM RESPONSE
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Discriminator
M

9.2.1.45

–

Message Type
M

9.2.1.46

YES
reject
Transaction ID
M

9.2.1.62

–

E-RNTI Release Status
M

9.2.1.126

YES
ignore

9.2	Information Element Functional Definition and Contents
9.2.0	General
Subclause 9.2 presents the NBAP IE definitions in tabular format. The corresponding ASN.1 definition is presented in Subclause 9.3. In case there is a contradiction between the tabular format in Subclause 9.2 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence.
When specifying information elements which are to be represented by bitstrings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits:
-	The first bit (leftmost bit) contains the most significant bit (MSB);
-	The last bit (rightmost bit) contains the least significant bit (LSB);
-	When importing bitstrings from other specifications, the first bit of the bitstring contains the first bit of the concerned information;
9.2.1	Common parameters
9.2.1.1	Add/Delete Indicator
The add/delete indicator shall notify the CRNC whether the associated resource has been added to or removed from the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Add/Delete Indicator


ENUMERATED (
Add, 
Delete)


9.2.1.1A	Allocation/Retention Priority
This parameter indicates the priority level in the allocation and retention of Node B internal resources. See Annex A.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Priority Level
M

INTEGER 
 (0..15)
This IE indicates the priority of the request.
Usage:
Value "0" means "Spare"; It shall be treated as a logical error if received.
Values between "1" and "14" are ordered in decreasing order of priority, "1" being the highest and "14" the lowest.
Value "15" means "No Priority".
Pre-emption Capability
M

ENUMERATED (
shall not trigger pre-emption,
may trigger pre-emption)

Pre-emption Vulnerability
M

ENUMERATED (
not pre-emtable,
pre-emptable)


9.2.1.1B	Alternative Format Reporting Indicator
This IE indicates if Node B may report a measurement using an alternative format. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Alternative Format Reporting Indicator


ENUMERATED (Alternative format is allowed, …)


9.2.1.2	Availability Status
The availability status is used to indicate more detailed information of the availability of the resource. In accordance with ref. CCITT Rec. X.731 [3], following values are defined. If the value of this IE is "empty", this implies that none of the status conditions described in ref. CCITT Rec. X.731 [3] are present.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Availability Status


ENUMERATED (
empty, 
in test, 
failed, 
power off, 
off line, 
off duty, 
dependency, 
degraded, 
not installed, 
log full, 
…)


9.2.1.3	BCCH Modification Time
Indicates the time after which the new system information shall be applied on BCCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
BCCH Modification Time


INTEGER (0..511)
All SFN values in which MIB may be mapped are allowed.
The tabular description is presented in TS 25.331 [18].

9.2.1.4	Binding ID
The Binding ID is the identifier of a user data stream. 
In case of transport bearer establishment with ALCAP (TS 25.426 [2], TS 25.434 [31]), this IE contains the identifier that is allocated at the Node B and that is unique for each transport bearer under establishment to/from the Node B.
If the Transport Layer Address contains an IP address (IETF RFC 2460 [29]), this IE contains the UDP port (IETF RFC 768 [30]) intended to be used for the user plane transport.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Binding ID


OCTET STRING (1..4,…)
If the Binding ID includes an UDP port, the UDP port is included in octets 1 and 2. The first octet of the UDP port field shall be included in the first octet of the Binding ID.

9.2.1.4A	BLER
Void.
9.2.1.5	Blocking Priority Indicator
The Blocking priority indicator shall indicate the immediacy with which a resource should be blocked from use.  The following priority classes shall be supported in the Blocking priority indicator.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Blocking Priority Indicator


ENUMERATED (
High, 
Normal, 
Low,
…)
"High" priority: Block resource immediately.
"Normal" priority: Block resource when idle or upon timer expiry.
"Low" priority: Block resource when idle.

9.2.1.5A	Burst Mode Parameters
The Burst Mode Parameters IE provides information to be applied for IPDL burst mode.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Burst Start
M

INTEGER (0..15)
See TS 25.214 [10] and TS 25.224 [21]
Burst Length
M

INTEGER (10..25)
See TS 25.214 [10] and TS 25.224 [21]
Burst Freq
M

INTEGER (1..16)
See TS 25.214 [10] and TS 25.224 [21]

9.2.1.5B	Broadcast Common Transport Bearer Indication
The Broadcast Common Transport Bearer Indication IE is used by the Node B to inform the CRNC that the transport bearer of the existing Common Transport Channel which is indicated by the Common Transport Channel ID IE and C-ID IE, shall be used instead of establishing a new transport bearer. If there are more than one Common Transport Channels sharing the same transport bearer, Node B may include any one of these Common Transport Channels together with its corresponding C-ID in Broadcast Common Transport Bearer Indication IE.

IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common Transport Channel ID
M

9.2.1.14

C-ID
M

9.2.1.9


9.2.1.5C	Broadcast Reference
The Broadcast Reference IE is a unique identifier within the CRNC identifying the intended usage of a requested Common Transport Channel (e.g. the Broadcast Reference IE may identify a particular MBMS session).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Broadcast Reference


BIT STRING (SIZE(24))


9.2.1.6	Cause
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Cause Group
M



>Radio Network Layer




>>Radio Network Layer Cause 
M

ENUMERATED (
unknown C-ID,
Cell not available,
Power level not supported, 
DL radio resources not available,
UL radio resources not available,
RL Already Activated/allocated,
Node B Resources Unavailable,
Measurement not supported for the object,
Combining Resources not available,
Requested configuration not supported,
Synchronization failure,
Priority transport channel established, 
SIB Origination in Node B not Supported,
Requested Tx Diversity Mode not supported,
Unspecified,
BCCH scheduling error,
Measurement Temporarily not Available,
Invalid CM Setting, Reconfiguration CFN not elapsed, 
Number of DL codes not supported, 
S-CPICH not supported,
Combining not supported,
UL SF not supported,
DL SF not supported,
Common Transport Channel Type not supported,
Dedicated Transport Channel Type not supported,
Downlink Shared Channel Type not supported,
Uplink Shared Channel Type not supported,
CM not supported,
Tx diversity no longer supported,
Unknown Local Cell ID,
…,
Number of UL codes not supported,
Information temporarily not available,
Information Provision not supported for the object,
Cell Synchronisation not supported,
Cell Synchronisation Adjustment not supported,
DPC Mode Change not Supported,
IPDL already activated,
IPDL not supported,
IPDL parameters not available,
Frequency Acquisition not supported,
Power Balancing status not compatible,
Requested type of Bearer Re-arrangement not supported, Signalling Bearer Re-arrangement not supported,
Bearer Re-arrangement needed,
Delayed Activation not Supported,
RL Timing Adjustment not supported,
MICH not supported,
F-DPCH Not Supported,
Modification Period not available,
PLCCH not supported,
Continuous Packet Connectivity DTX-DRX operation not available, Continuous Packet Connectivity UE DTX Cycle not available,
MIMO not available,
E-DCH MAC-d PDU Size Format  not available, 
Multi Cell operation not available,
Semi-Persistent scheduling not supported,
Continuous Packet Connectivity DRX not supported,
Continuous Packet Connectivity DRX not available,
SixtyfourQAM DL and MIMO Combined not available,
S-CPICH power offset support not available,
TX diversity for MIMO UE on DL Control Channels not available, Single Stream MIMO not available, Multi Cell operation with MIMO not available,
Multi Cell operation with Single Stream MIMO not available,
Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available,
Multi Cell E-DCH operation not available,
Frequency Specific Compressed Mode not available,
UL CLTD operation not available, MIMO with four transmit antennas not available, Dual Stream MIMO with four transmit antennas not available,
Multiflow operation not available, SixtyfourQAM operation not available, UL MIMO operation not available, UL MIMO and SixteenQAM operation not available, UL MIMO and SixtyfourQAM operation not available,
NodeB Triggered HS-DPCCH Transmission operation not available,
2ms and 10ms TTI Concurrent Deployment operation not available,
Further Enhanced UE DRX operation not available,
Per HARQ Activation and Deactivation operation not available,
TTI alignment operation not available,
Common E-RGCH operation not available,
E-DCH decoupling operation not available,
Basic DCH Enhancements operation not available, Full DCH Enhancements operation not available,
BCH mapped on SCCPCH scheduling error,
Radio Links without DPCH/F-DPCH operation not available,
UL DPCCH2 operation not available, Downlink TPC enhancements operation not available)

>Transport Layer




>>Transport Layer Cause
M

ENUMERATED (
Transport resource unavailable,
Unspecified,
…)

>Protocol




>>Protocol Cause
M

ENUMERATED (
Transfer syntax error,
Abstract syntax error (reject),
Abstract syntax error (ignore and notify),
Message not compatible with receiver state,
Semantic error,
Unspecified, 
Abstract syntax error (falsely constructed message),
…)

>Misc




>>Miscellaneous Cause
M

ENUMERATED (
Control processing overload
Hardware failure,
O&M intervention,
Not enough user plane processing resources,
Unspecified,
…)


The meaning of the different cause values is described in the following table. In general, "not supported" cause values indicate that the concerned capability is missing. On the other hand, "not available" cause values indicate that the concerned capability is present, but insufficient resources were available to perform the requested action.
Radio Network Layer cause
Meaning
BCCH scheduling error
The Node B has detected an illegal BCCH schedule update (see subclause 8.2.16.3).
BCH mapped on SCCPCH scheduling error
The Node B has detected an illegal BCH mapped on SCCPCH schedule update (see subclause 8.2.16.3).
Bearer Re-arrangement needed
The Node B cannot perform the requested Radio Link Reconfiguration without bearer re-arrangement.
Cell not Available
The concerned cell or local cell is not available.
Cell Synchronisation not supported
The concerned cell(s) do not support Cell Synchronisation.
Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available
Cell specific tx diversity handling for multi cell operation not available in the concerned cell(s)
Combining not supported
The Node B does not support RL combining for the concerned cells.
Combining Resources Not Available
The value of the received Diversity Control Field IE was set to "Must", but the Node B cannot perform the requested combining.
CM not supported
The concerned cell(s) do not support Compressed Mode.
Common Transport Channel Type not supported
The concerned cell(s) do not support the RACH and/or FACH Common Transport Channel Type.
Continuous Packet Connectivity  DTX-DRX operation not available
CPC resources for DTX-DRX operation not available in the concerned cell(s).
Continuous Packet Connectivity UE DTX Cycle not available
CPC resources for the UE DTX Cycle not available in the concerned cell(s).
Dedicated Transport Channel Type not supported
The concerned cell(s) do not support the Dedicated Transport Channel Type.
Delayed Activation not Supported
The concerned cell(s) do not support delayed activation of RLs.
DL Radio Resources not Available
The Node B does not have sufficient DL radio resources available.
DL SF not supported
The concerned cell(s) do not support the requested DL SF.
DL Shared Channel Type not supported
The concerned cell(s) do not support the Downlink Shared Channel Type.
DPC Mode Change not Supported
The concerned cells do not support DPC mode changes.
E-DCH MAC-d PDU Size Format  not available
The selected E-DCH MAC-d PDU Size Format is not available in the concerned cell(s).
Frequency Acquisition not supported
The concerned cell(s) do not support Frequency Acquisition.
F-DPCH not supported
The concerned cell(s) do not support the Fractional DPCH
Information Provision not supported for the object
The requested information provision is not supported for the concerned object types.
Information temporarily not available
The requested information can temporarily not be provided.
Invalid CM Settings
The concerned cell(s) consider the requested Compressed Mode settings invalid.
IPDL already activated
The concerned cell(s) have already active IPDL ongoing.
IPDL not supported
The concerned cell(s) do not support the IPDL.
IPDL parameters not available
The concerned cell(s) do not have IPDL parameters defining IPDL to be applied.
Measurement not Supported For The Object
At least one of the concerned cell(s) does not support the requested measurement on the concerned object type.
Measurement Temporarily not Available
The Node B can temporarily not provide the requested measurement value.
MICH not supported
The concerned cell does not support MICH.
MIMO not available
MIMO resources not available in the concerned cell(s).
Modificaton Period  not available
The Node B does not have modification period available.
Multi Cell operation not available
Multi Cell operation resources not available in the concerned cell(s)
Multi Cell operation with MIMO not available
Multi Cell operation resources with MIMO not available in the concerned cell(s)
Multi Cell operation with Single Stream MIMO not available
Multi Cell operation resources with Single Stream MIMO not available in the concerned cell(s)
Multi Cell E-DCH operation not available
Multi Cell E-DCH operation resources not available in the concerned cell(s)
Node B resources unavailable
The Node B does not have sufficient resources available.
Number of DL codes not supported
The concerned cell(s) do not support the requested number of DL codes.
Number of UL codes not supported
The concerned cell(s) do not support the requested number of UL codes.
Power Level not Supported
A DL power level was requested which the concerned cell(s) do not support.
Power Balancing status not compatible
The power balancing status in the SRNC is not compatible with that of the Node B.
PLCCH not supported
The concerned cell does not support PLCCH.
Priority transport channel established
The CRNC cannot perform the requested blocking since a transport channel with a high priority is present.
RL Timing Adjustment not Supported
The concerned cell(s) do not support adjustments of the RL timing.
Reconfiguration CFN not elapsed
The requested action cannot be performed due to that a RADIO LINK RECONFIGURATION COMMIT message was received previously, but the concerned CFN has not yet elapsed.
Requested Configuration not Supported
The concerned cell(s) do not support the requested configuration i.e. power levels, Transport Formats, physical channel parameters.
Requested Type of Bearer Re-arrangement not supported
The Node B does not support the requested type of bearer re-arrangement.
Requested Tx Diversity mode not supported
The concerned cell(s) do not support the requested transmit diversity mode.
RL already Activated/ allocated
The Node B has already allocated an RL with the requested RL-id for this UE context.
S-CPICH not supported
The concerned cell(s) do not support S-CPICH.
S-CPICH power offset support not available
The support for setting up the desired power offset on S-CPICH with respect to P-CPICH is not available
SIB Orgination in Node B not Supported
The Node B does not support the origination of the requested SIB for the concerned cell.
Signalling Bearer Re-arrangement not supported
The Node B does not support the Signalling bearer re-arrangement.
Single Stream MIMO not available
Single Stream MIMO resources not available in the concerned cell(s).
SixtyfourQAM DL and MIMO Combined not available
SixtyfourQAM DL and MIMO Combined not available in the concerned cell(s).
Synchronisation Failure
Loss of UL Uu synchronisation.
Cell Synchronisation Adjustment not supported
The concerned cell(s) do not support Cell Synchronisation Adjustment.
TX diversity for MIMO UE on DL Control Channels not available
The Node B does not have sufficient radio resources available to support transmit diversity on downlink control channels when the UE is configured in MIMO mode with P-CPICH & S-CPICH as phase references (TS 25.211 [7])
Tx diversity no longer supported
Tx diversity can no longer be supported in the concerned cell.
UL Radio Resources not Available
The Node B does not have sufficient UL radio resources available.
UL SF not supported
The concerned cell(s) do not support the requested minimum UL SF.
UL Shared Channel Type not supported
The concerned cell(s) do not support the Uplink Shared Channel Type.
Unknown C-ID
The Node B is not aware of a cell with the provided C-ID.
Unknown Local Cell ID
The Node B is not aware of a local cell with the provided Local Cell ID
Unspecified
Sent when none of the above cause values applies but still the cause is Radio Network layer related.
Semi-Persistent scheduling not supported
The concerned cell(s) do not support the Semi-Persistent scheduling operation (for 1.28Mcps TDD only)
Continuous Packet Connectivity DRX not supported
The concerned cell(s) do not support the Continuous Packet Connectivity DRX operation (for 1.28Mcps TDD only)
Continuous Packet Connectivity DRX not available
HSPA resources for DRX operation not available in the concerned cell(s). (for 1.28Mcps TDD only)
Frequency Specific Compressed Mode not available
Frequency Specific Compressed Mode is not available in the concerned cell(s).
UL CLTD operation not available
UL CLTD resources are not available in the concerned cell(s).
Multiflow operation not available
Multiflow operation is not available in the concerned cell(s).
SixtyfourQAM UL operation not available
SixtyfourQAM UL resources are not available in the concerned cell(s).
UL MIMO operation not available
UL MIMO resources are not available in the concerned cell(s).
UL MIMO and SixteenQAM operation not available
UL MIMO and SixteenQAM resources are not available in the concerned cell(s).
UL MIMO and SixtyfourQAM operation not available
UL MIMO and SixtyfourQAM resources are not available in the concerned cell(s).
NodeB Triggered HS-DPCCH Transmission operation not available
NodeB Triggered HS-DPCCH Transmission operation is not available in the concerned cell(s).
2ms and 10ms TTI Concurrent Deployment operation not available
Concurrent Deployment of 2ms and 10ms TTI operation is not available in the concerned cell(s).
Further Enhanced UE DRX operation not available
Further Enhanced UE DRX operation is not available in the concerned cell(s).
Per HARQ Activation and Deactivation operation not available
Per HARQ Activation and Deactivation operation is not available in the concerned cell(s).
TTI alignment operation not available
TTI alignment operation is not available in the concerned cell(s).
Common E-RGCH operation not available
Common E-RGCH operation is not available in the concerned cell(s).
MIMO with four transmit antennas not available
MIMO with four transmit antenneas not available in the concerned cell(s)
Dual Stream MIMO with four transmit antennas not available
Dual Stream MIMO with four transmit antennas not available in the concerned cell(s).
E-DCH decoupling operation not available
E-DCH decoupling operation is not available in the concerned cell(s).
Basic DCH Enhancements operation not available
Basic DCH Enhancements resources are not available in the concerned cell(s).
Full DCH Enhancements operation not available
Full DCH Enhancements resources are not available in the concerned cell(s).
Radio Links without DPCH/F-DPCH operation not available
Radio Links without DPCH/F-DPCH operation is not available in the concerned cell(s).
UL DPCCH2 operation not available
UL DPCCH2 operation is not available in the concerned cell(s).
Downlink TPC enhancements operation not available
Downlink TPC enhancements is not available in the concerned cell(s).

Transport Network Layer cause
Meaning
Transport resource unavailable
The required transport resources are not available.
Unspecified
Sent when none of the above cause values applies but still the cause is Transport Network layer related.

Protocol cause
Meaning
Abstract Syntax Error (Reject)
The received message included an abstract syntax error and the concerned criticality indicated "reject" (see subclause 10.3).
Abstract Syntax Error (Ignore and Notify)
The received message included an abstract syntax error and the concerned criticality indicated "ignore and notify" (see subclause 10.3).
Abstract syntax error (falsely constructed message)
The received message contained IEs in wrong order or with too many occurrences (see subclause 10.3).
Message not Compatible with Receiver State
The received message was not compatible with the receiver state (see subclause 10.4).
Semantic Error
The received message included a semantic error (see subclause 10.4).
Transfer Syntax Error
The received message included a transfer syntax error (see subclause 10.2).
Unspecified
Sent when none of the above cause values applies but still the cause is protocol related.

Miscellaneous cause
Meaning
Control Processing Overload
Node B control processing overload.
Hardware Failure
Node B hardware failure.
Not enough User Plane Processing Resources
Node B has insufficient user plane processing resources available.
O&M Intervention
Operation and Maintenance intervention related to Node B equipment.
Unspecified
Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer or Protocol.

9.2.1.7	CFN
Connection Frame Number for the radio connection, see ref. TS 25.402 [17].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CFN 


INTEGER (0..255)


9.2.1.8	CFN Offset
Void.
9.2.1.9	C-ID
The C-ID (Cell identifier) is the identifier of a cell in one RNC.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
C-ID


INTEGER (0..65535)


9.2.1.9A	Common Channels Capacity Consumption Law
The capacity consumption law indicates to the CRNC how the Capacity Credit is consumed by NBAP set of procedures, depending on the allocated Spreading Factor. [FDD - For the PRACH, the reference spreading factor shall be the minimum possible spreading factor amongst the ones defined by the RACH Slot Format IE(s) in the Common Transport Channel Setup or Reconfiguration procedures.]
This capacity consumption law indicates the consumption law to be used with the following procedures:
-	Common Transport Channel Setup
-	Common Transport Channel Deletion
-	[FDD - Common Transport Channel Reconfiguration]
For the Common Transport Channel Setup procedure, the cost given in the consumption law shall be debited from the Capacity Credit, whereas it shall be credited to the Capacity Credit for the Common Transport Channel Deletion one.
[FDD - For the Common Transport Channel Reconfiguration procedure, the difference of the consumption cost for the new spreading factor and the consumption cost for the old spreading factor shall be debited from the Capacity Credit (or credited if this difference is negative).]
If the modelling of the internal resource capability of the Node B is modelled independently for the Uplink and Downlink, the "DL cost" shall be applied to the "DL or Global Capacity Credit" and the "UL Cost" shall be applied to the "UL Capacity Credit". If it is modelled as shared resources, both the "DL cost" and the "UL cost" shall be applied to the "DL or Global Capacity Credit".
[FDD - When the Common Transport Channel Setup, Deletion or Reconfiguration procedures are used, the Capacity Credit shall be updated considering all physical channels related in these procedures (S-CCPCH, PICH, PRACH and AICH), i.e. one cost shall be credited to or debited from the Capacity Credit per physical channel.] 
[FDD - The costs given in the consumption law are the costs per channelization code. When multiple channelization codes are used by a physical channel, the cost credited to or debited from the Capacity Credit for this physical channel shall be taken as N times the cost given in the consumption law, where N is the number of channelization codes.]
[TDD - When the Common Transport Channel Setup or Deletion procedures are used, the Capacity Credit shall be updated considering all physical channels related in these procedures (S-CCPCH, PICH, PRACH), i.e. one cost shall be credited to or debited from the Capacity Credit per physical channel.]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SF Allocation Law

1..<maxNrOfSF>

[FDD - For each SF, cost of its allocation: the first instance corresponds to SF = 4, the second to SF = 8, the third to SF = 16 and so on.]
[TDD - For each SF, cost of its allocation: the first instance corresponds to SF = 1, the second to SF = 2, the third to SF = 4 and so on.]
>DL cost
M

INTEGER (0..65535)

>UL cost
M

INTEGER (0..65535)


Range Bound
Explanation
maxNrOfSF
Maximum number of Spreading Factors 

9.2.1.9B	Common Measurement Accuracy
The Common Measurement Accuracy IE indicates the accuracy of the common measurement.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Common Measurement Accuracy
M



>TUTRAN-GPS Measurement Accuracy Class




>>TUTRAN-GPS Measurement Accuracy Class
M

TUTRAN-GPS Accuracy Class
9.2.1.64C

>TUTRAN-GANSS Measurement Accuracy Class




>>TUTRAN-GANSS Measurement Accuracy Class
M

TUTRAN-GANSS Accuracy Class
9.2.1.98


9.2.1.10	Common Measurement Object Type
Void.
9.2.1.11	Common Measurement Type
The Common Measurement Type identifies which measurement that shall be performed.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common Measurement Type


ENUMERATED (
Received Total Wide Band Power, 
Transmitted Carrier Power, 
Acknowledged PRACH Preambles, 
UL Timeslot ISCP, 
NotUsed-1, 
NotUsed-2, 
…, 
UTRAN GPS Timing of Cell Frames for UE Positioning, 
SFN-SFN Observed Time Difference, Transmitted carrier power of all codes not used for HS transmission, HS-DSCH Required Power, 
HS-DSCH Provided Bit Rate, Received Total Wide Band Power for Cell Portion, Transmitted Carrier Power for Cell Portion, Transmitted carrier power of all codes not used for HS-PDSCH  HS-SCCH E-AGCH E-RGCH or E-HICH transmission for Cell Portion, UpPCH Interference, DL Transmission Branch Load,
HS-DSCH Required Power for Cell Portion, HS-DSCH Provided Bit Rate for Cell Portion, E-DCH Provided Bit Rate,
E-DCH Non-serving Relative Grant Down Commands,
Received Scheduled E-DCH Power Share, Received Scheduled E-DCH Power Share for Cell Portion, UTRAN GANSS Timing of Cell Frames for UE Positioning, E-DCH RACH Report, Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH transmission for Cell Portion, UL Timeslot ISCP for Cell Portion, E-DCH Provided Bit Rate for Cell Portion, UpPCH Interference for Cell Portion)
"UL Timeslot ISCP" is used by TDD only, 
"Acknowledged PRACH Preambles", ”DL Transmission Branch Load”, “E-DCH RACH Report” are used by FDD only,
“UpPCH interference” is used by 1.28Mcps TDD only.
This IE shall never be set to the values that are prefixed "NotUsed-".
[TDD - The IE Type "Transmitted carrier power of all codes not used for HS transmission" corresponds to the measurement "Transmitted carrier power of all codes not used for HS-PDSCH [TDD  - E-AGCH, E-HICH] or HS-SCCH transmission" in TS 25.225 [5] and TS 25.123 [23].]
[FDD - The IE Type "Transmitted carrier power of all codes not used for HS transmission" corresponds to the measurement "Transmitted carrier power of all codes not used for HS-PDSCH HS-SCCH E-AGCH E-RGCH or E-HICH transmission" in TS 25.215 [4] and TS 25.133 [22].]


9.2.1.12	Common Measurement Value
The Common Measurement Value shall be the most recent value for this measurement, for which the reporting criteria were met.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
CHOICE Common Measurement Value
M



–

>Transmitted Carrier Power






>>Transmitted Carrier Power Value
M

INTEGER (0..100)
According to mapping in TS 25.133 [22] and TS 25.123 [23]
–

>Received Total Wide Band Power






>>Received Total Wide Band Power Value
M

INTEGER (0..621)
According to mapping in TS 25.133 [22] and TS 25.123 [23]
–

>Acknowledged PRACH Preambles 



FDD Only


>>Acknowledged PRACH Preamble Value
M

INTEGER (0..240,…) 
According to mapping in TS 25.133 [22]
–

>UL Timeslot ISCP



TDD Only


>>UL Timeslot ISCP
M

INTEGER (0..127)
According to mapping in TS 25.123 [23]
–

>Not used 1 


NULL
This choice shall not be used. Ignore if received. 


>Not Used 2 


NULL
This choice shall not be used. Ignore if received. 


>Additional Common Measurement Values



See Note 1


>>UTRAN GPS Timing Of Cell Frames for UE Positioning






>>>TUTRAN-GPS Measurement Value Information
M

9.2.1.64A

YES
ignore
>>SFN-SFN Observed Time Difference






>>>SFN-SFN Measurement Value Information
M

9.2.1.53E

YES
ignore
>>Transmitted Carrier Power Of All Codes Not Used For HSTransmission






>>>Transmitted Carrier Power Of All Codes Not Used For HSTransmission Value
M

INTEGER (0..100)
According to mapping in TS 25.133 [22], measurement "Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICHTransmission" and mapping in TS 25.123 [23], measurement "Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH Or HS-SCCH Transmission"
YES
ignore
>>HS-DSCH Required Power






>>>HS-DSCH Required Power Value Information
M

9.2.1.31Ic

YES
ignore
>>HS-DSCH Provided Bit Rate






>>>HS-DSCH Provided Bit Rate Value Information
M

9.2.1.31Ib

YES
ignore
>>Transmitted Carrier Power For Cell Portion



FDD Only


>>>Transmitted Carrier Power For Cell Portion Value

1..<maxNrOfCellPortions>


GLOBAL
ignore
>>>>Cell Portion ID
M

9.2.2.1Ca

–

>>>>Transmitted Carrier Power Value
M

INTEGER (0..100)
According to mapping in TS 25.133 [22] 
–

>>Received Total Wide Band Power For Cell Portion



FDD Only


>>>Received Total Wide Band Power For Cell Portion Value

1..<maxNrOfCellPortions>


GLOBAL
ignore
>>>>Cell Portion ID
M

9.2.2.1Ca

–

>>>>Received Total Wide Band Power Value
M

INTEGER (0..621)
According to mapping in TS 25.133 [22]
–

>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH Transmission For Cell Portion



FDD Only


>>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH Transmission For Cell Portion Value

1..<maxNrOfCellPortions>


GLOBAL
ignore
>>>>Cell Portion ID
M

9.2.2.1Ca

–

>>>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH,  HS-SCCH, E-AGCH, E-RGCH or E-HICH Transmission Value
M

INTEGER (0..100)
According to mapping in TS 25.133 [22]
–

>>UpPCH interference



1.28Mcps TDD Only


>>>UpPCH interference Value
M

INTEGER (0..127,…)
According to mapping in TS 25.123 [23]
YES
ignore
>>DL Transmission Branch Load



FDD Only


>>>Node B DL Transmission Branch Load Values
M

INTEGER (0..101,…)
According to mapping in TS 25.133 [22]
YES
ignore
>>HS-DSCH Required Power For Cell Portion



FDD Only


>>>HS-DSCH Required Power  For Cell Portion  Information

1..<maxNrOfCellPortions>


GLOBAL
ignore
>>>>Cell Portion ID
M

9.2.2.1Ca

–

>>>>HS-DSCH Required Power Value Information
M

9.2.1.31Ic

–

>>HS-DSCH Provided Bit Rate For Cell Portion



FDD Only


>>>HS-DSCH Provided Bit Rate For Cell Portion Information

1..<maxNrOfCellPortions>


GLOBAL
ignore
>>>>Cell Portion ID
M

9.2.2.1Ca

–

>>>>HS-DSCH Provided Bit Rate Value Information
M

9.2.1.31Ib

–

>>E-DCH Provided Bit Rate






>>>E-DCH Provided Bit Rate Value Information
M

9.2.1.78

YES
ignore
>>E-DCH Non-serving Relative Grant Down Commands



FDD Only


>>>E-DCH Non-serving Relative Grant Down Commands Value Information
M

INTEGER (0..100,…)
Down Commands per second
YES
ignore
>>Received Scheduled E-DCH Power Share 



FDD Only
According to definition in TS 25.215 [4]


>>>Received Scheduled E-DCH Power Share 

1


YES
ignore
>>>>RSEPS Value 
M

INTEGER (0..151)
According to mapping in TS 25.133 [22]
–

>>>>RTWP* Value 
O

INTEGER (0..621)
According to mapping of RTWP in TS 25.133 [22]
–

>>Received Scheduled E-DCH Power Share for Cell Portion 



FDD only
According to definition in TS 25.215 [4]


>>>Received Scheduled E-DCH Power Share For Cell Portion Value

1..<maxNrOfCellPortions>


GLOBAL
ignore
>>>>Cell Portion ID
M

9.2.2.1Ca

–

>>>>RSEPS for Cell Portion Value
M

INTEGER (0..151)
According to mapping in TS 25.133 [22].
–

>>>>RTWP* for Cell Portion Value
O

INTEGER (0..621)
According to mapping of RTWP in TS 25.133 [22]
–

>>UTRAN GANSS Timing Of Cell Frames for UE Positioning






>>>TUTRAN-GANSS Measurement Value Information
M

9.2.1.100

YES
ignore
>>E-DCH RACH Report 



FDD Only


>>>E-DCH RACH Report Information

1..< maxNrOfCommonEDCH >

The maximum repetitions should be limited to 1 so that this information is reported only once for a cell.
GLOBAL
ignore
>>>>Granted E-DCH RACH Resources
M

INTEGER (0..240,…)
According to mapping in TS 25.302 [25]
–

>>>>Denied E-DCH  RACH Resources
M

INTEGER (0..240,…)
According to mapping in TS 25.302 [25]
–

>>>>2ms Granted E-DCH RACH Resources
O

INTEGER (0..240,…)
According to mapping in TS 25.302 [25].
–
ignore
>>>>2ms Overridden E-DCH RACH Resources
O

INTEGER (0..240,…)
According to mapping in TS 25.302 [25].
–
ignore
>>>>2ms Denied E-DCH RACH Resources
O

INTEGER (0..240,…)
According to mapping in TS 25.302 [25].
–
ignore
>>Transmitted Carrier Power For Cell Portion LCR



1.28Mcps TDD Only


>>>Transmitted Carrier Power For Cell Portion Value LCR

1..<maxNrOfCellPortionsPerCellLCR>


GLOBAL
ignore
>>>>Cell Portion LCR ID
M

9.2.3.107

–

>>>>Transmitted Carrier Power Value
M

INTEGER (0..100)
According to mapping in TS 25.123 [23] 
–

>>Received Total Wide Band Power For Cell Portion LCR



1.28Mcps TDD Only


>>>Received Total Wide Band Power For Cell Portion Value LCR

1..<maxNrOfCellPortionsPerCellLCR>


GLOBAL
ignore
>>>>Cell Portion LCR ID
M

9.2.3.107

–

>>>>Received Total Wide Band Power Value
M

INTEGER (0..621)
According to mapping in TS 25.123 [23]
–

>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission For Cell Portion



1.28Mcps TDD Only


>>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission For Cell Portion Value

1..<maxNrOfCellPortionsPerCellLCR>


GLOBAL
ignore
>>>>Cell Portion LCR ID
M

9.2.3.107

–

>>>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH,  HS-SCCH, E-AGCH, or E-HICH Transmission Value
M

INTEGER (0..100)
According to mapping in TS 25.123 [23]
–

>>UL Timeslot ISCP For Cell Portion



1.28Mcps TDD Only


>>>UL Timeslot ISCP For Cell Portion Value

1..<maxNrOfCellPortionsPerCellLCR>


GLOBAL
ignore
>>>>Cell Portion LCR ID
M

9.2.3.107

–

>>UL Timeslot ISCP
M

INTEGER (0..127)
According to mapping in TS 25.123 [23]
–

>>HS-DSCH Required Power For Cell Portion LCR



1.28Mcps TDD Only


>>>HS-DSCH Required Power  For Cell Portion  Information LCR

1..<maxNrOfCellPortionsPerCellLCR>


GLOBAL
ignore
>>>>Cell Portion LCR ID
M

9.2.3.107

–

>>>>HS-DSCH Required Power Value Information
M

9.2.1.31Ic

–

>>HS-DSCH Provided Bit Rate For Cell Portion LCR



1.28Mcps TDD Only


>>>HS-DSCH Provided Bit Rate For Cell Portion Information LCR

1..<maxNrOfCellPortionsPerCellLCR>


GLOBAL
ignore
>>>>Cell Portion LCR ID
M

9.2.3.107

–

>>>>HS-DSCH Provided Bit Rate Value Information
M

9.2.1.31Ib

–

>> E-DCH Provided Bit Rate For Cell Portion



1.28Mcps TDD Only


>>> E-DCH Provided Bit Rate For Cell Portion Information

1..<maxNrOfCellPortionsPerCellLCR>


GLOBAL
ignore
>>>>Cell Portion LCR ID
M

9.2.3.107

–

>>>> E-DCH Provided Bit Rate Value Information
M

9.2.1.78

–

>> UpPCH interference For Cell Portion



1.28Mcps TDD Only


>>> UpPCH interference For Cell Portion Information

1..<maxNrOfCellPortionsPerCellLCR>


GLOBAL
ignore
>>>>Cell Portion LCR ID
M

9.2.3.107

–

>>>> UpPCH interference Value
M

INTEGER (0..127,…)
According to mapping in TS 25.123 [23]
–

Note 1:	This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1.

Range Bound
Explanation
 MaxNrOfCellPortions
Maximum number of Cell Portions in a cell 
maxNrOfCommonEDCH
Maximum number of Common E-DCH Resource Combination for a cell
MaxNrOfCellPortionsPerCellLCR
Maximum number of Cell Portions in a cell for 1.28 Mcps TDD

9.2.1.12A	Common Measurement Value Information
The Common Measurement Value Information IE provides information both on whether the Common Measurement Value is provided in the message or not and if provided also the Common Measurement Value itself.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Measurement Availability Indicator
M



>Measurement Available




>>Common Measurement Value
M

9.2.1.12

>Measurement Not Available


NULL


9.2.1.13	Common Physical Channel ID
Common Physical Channel ID is the unique identifier for one common physical channel within a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common Physical Channel ID


INTEGER (0..255)


9.2.1.13A	Common Physical Channel Status Information
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common Physical Channel ID
M

9.2.1.13

Resource Operational State
M

9.2.1.52

Availability Status
M

9.2.1.2


9.2.1.14	Common Transport Channel ID
Common Transport Channel ID is the unique identifier for one common transport channel within a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common Transport Channel ID


INTEGER (0..255)


9.2.1.14A	Common Transport Channel Information Response
The Common Transport Channel Information Response IE provides information for Common Transport Channels that have been established or modified.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Common Transport Channel ID
M

9.2.1.14

–

Binding ID
O

9.2.1.4

–

Transport Layer Address
O

9.2.1.63

–

Broadcast Common Transport Bearer Indication
O

9.2.1.5B

YES
ignore
IP Multicast Data Bearer Indication
O

9.2.1.109

YES
ignore

9.2.1.14B	Common Transport Channel Status Information
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common Transport Channel ID
M

9.2.1.14

Resource Operational State
M

9.2.1.52

Availability Status
M

9.2.1.2


9.2.1.15	Communication Control Port ID
A Communication Control Port corresponds to one signalling bearer between the CRNC and the Node B for the control of Node B Communication Contexts. The Node B may have multiple Communication Control Ports (one per Traffic Termination Point). The Communication Control Port is selected at creation of the Node B Communication Context. The Communication Control Port ID is the identifier of the Communication Control Port.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Communication Control Port ID


INTEGER (0..65535)


9.2.1.16	Configuration Generation ID
The Configuration Generation ID describes the generation of the configuration of logical resources in a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Configuration Generation ID


INTEGER (0..255)
Value "0" means "No configuration".
At possible wraparound of the ID counter in CRNC the value "0" shall not be used.

9.2.1.17	Criticality Diagnostics
The Criticality Diagnostics IE is sent by a Node B or the CRNC when parts of a received message have not been comprehended or are missing, or if the message contained logical errors. When applicable, it contains information about which IEs that were not comprehended or were missing.
For further details on how to use the Criticality Diagnostics IE, see Annex C.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Procedure ID

0..1

Procedure ID is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error
–

>Procedure Code
M

INTEGER (0..255)

–

>Ddmode
M

ENUMERATED (
TDD, 
FDD,
Common,
…)
"Common" = common to FDD and TDD.
–

Triggering Message 
O

ENUMERATED (
initiating message, successful outcome, unsuccessful outcome, 
outcome)
The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication. 
–

Procedure Criticality
O

ENUMERATED (
reject, 
ignore, 
notify)
This Procedure Criticality is used for reporting the Criticality of the Triggering message 
(Procedure).
–

Transaction ID
O

9.2.1.62

–

Information Element Criticality Diagnostics

0..<maxNrOfErrors>


–

>IE Criticality
M

ENUMERATED (
reject, 
ignore, 
notify)
The IE Criticality is used for reporting the criticality of the triggering IE. The value "ignore" shall never be used. 
–

>IE ID
M

INTEGER (0..65535)
The IE ID of the not understood or missing IE 
–

>Repetition Number
O

INTEGER (0..255)
The Repetition Number IE gives:
	for a not understood IE: 
The number of occurrences of the reported IE up to and including the not understood occurrence
	for a missing IE:
The number of occurrences up to but not including the missing occurrence.
Note: All the counted occurrences of the reported IE must have the same topdown hierarchical message structure of IEs with assigned criticality above them.
–

>Message Structure
O

9.2.1.45A
The Message Structure IE describes the structure where the not understood or missing IE was detected.
This IE is included if the not understood IE is not the top level of the message.
YES
ignore
>Type Of Error
M

ENUMERATED (
not understood, missing, 
…)

YES
ignore

Range Bound
Explanation
maxNrOfErrors
Maximum number of IE errors allowed to be reported with a single message.

9.2.1.18	CRNC Communication Context ID
The CRNC Communication Context ID is the identifier of the Communication Context in the CRNC.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CRNC Communication Context ID


INTEGER (0..2^20 – 1)
"2^20-1" is a reserved value indicating all the CRNC Communication Contexts that can be reached by the Communication Control Port (All CRNCCC).

9.2.1.18A	CTFC
The CTFC is an integer number calculated in accordance with TS 25.331 [18], subclause 14.10. Regarding the channel ordering, for all transport channels, ‘TrCH1’ corresponds to the transport channel having the lowest transport channel identity among all configured transport channels on this CCTrCH. ‘TrCH2’ corresponds to the transport channel having the next lowest transport channel identity, and so on.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE CTFC Format
M



>2 bits long




>>CTFC value
M

INTEGER (0..3)

>4 bits long




>>CTFC value
M

INTEGER (0..15)

>6 bits long




>>CTFC value
M

INTEGER (0..63)

>8 bits long




>>CTFC value
M

INTEGER (0..255)

>12 bits long




>>CTFC value
M

INTEGER (0..4095)

>16 bits long




>>CTFC value
M

INTEGER (0..65535)

>max nb bits long




>>CTFC value
M

INTEGER (0..maxCTFC)


Range Bound
Explanation
MaxCTFC
Maximum number of the CTFC value is calculated according to the following:

with the notation according to ref. TS 25.331 [18]

9.2.1.19	DCH Combination Indicator
Void.
9.2.1.20	DCH ID
The DCH ID is the identifier of an active dedicated transport channel. It is unique for each active DCH among the active DCHs simultaneously allocated for the same UE.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DCH ID


INTEGER (0..255)


9.2.1.20A	Dedicated Channels Capacity Consumption Law
The capacity consumption law indicates to the CRNC how the Capacity Credit is consumed by NBAP set of procedures, depending on the [FDD - allocated Spreading Factor and the RL/RLS situation] [TDD - allocated Spreading Factor on each DPCH and the assigned timeslot]. [FDD - In Uplink, the reference spreading factor shall be the minimum spreading factor signalled in the Radio Link Setup Request message. This is signalled using the Min UL Channelisation Code Length IE.]
This capacity consumption law indicates the consumption law to be used with the following procedures :
-	Radio Link Setup
-	Radio Link Addition
-	Radio Link Reconfiguration
-	Radio Link Deletion
-	[TDD - Physical Shared Channel Reconfiguration]
For the Radio Link Setup and Radio Link Addition procedures, the cost given in the consumption law shall be debited from the Capacity Credit, whereas it shall credited to the Capacity Credit for the Radio Link Deletion procedure. For the Radio Link Reconfiguration procedure, the difference of the consumption cost for the new spreading factor and the consumption cost for the old spreading factor shall be debited from the Capacity Credit (or credited when this difference is negative).
If the modelling of the internal resource capability of the Node B is modelled independently for the Uplink and Downlink, the DL cost shall be applied to the DL or Global Capacity Credit and the UL Cost shall be applied to the UL Capacity Credit. If it is modelled as shared resources, both the DL costs and the UL costs shall be applied to the DL or Global Capacity Credit.
[FDD - For a Radio Link creating a Radio Link Set (first RL of a RLS), the cost for the RL (cost 2) and RLS (cost 1) shall be taken into account. When adding a Radio Link to a Radio Link Set, only the RL cost (cost 2) shall be taken into account.
In the case where multiple Radio Links are established in one procedure, for every created Radio Link Set, the first Radio Link is always the Radio Link with the lowest repetition number.]
[FDD - The costs given in the consumption law are the costs per channelization code. When multiple channelization codes are used by either the radio links, the cost credited to or debited from the Capacity Credit shall be taken as N times the cost for one code, where N is the number of channelization codes.]
[TDD - The cost for a radio link is a sum of the costs for each DPCH. For the first DPCH assigned to any user in a cell within a timeslot, the initial cost for a DPCH in a timeslot (cost 1) and the cost for a DPCH (cost 2) shall be taken into account. For any DPCH that is not the first DPCH assigned for any user in a cell within a timeslot, only the cost for a DPCH (cost 2) shall be taken into account.]
[TDD - The cost for shared channels is the sum of the costs for each PDSCH and PUSCH assigned to a PUSCH or PDSCH set. For the first PDSCH or PUSCH assigned to any user in a cell within a timeslot, the initial cost for a PDSCH/PUSCH in a timeslot (cost 1) and the cost for a PDSCH/PUSCH (cost 2) shall be taken into account. For any PDSCH/PUSCH that is not the first PDSCH/PUSCH assigned to any user in a cell within a timeslot, only the cost for a PDSCH/PUSCH (cost 2) shall be taken into account.]
[TDD - In the case of Physical Shared Channel Reconfiguration, the sum of the consumption cost of the each PDSCH/PUSCH of the previous configuration shall be credited to the capacity credit, and the sum of the consumption cost of each PDSCH/PUSCH of the new configuration shall be subtracted from the capacity credit.]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SF Allocation Law

1..<maxNrOfSF>

[FDD - For each SF, cost of its allocation: the first instance corresponds to SF = 4, the second to SF = 8, the third to SF = 16 and so on.]
[TDD - For each SF, cost of its allocation: the first instance corresponds to SF = 1, the second to SF = 2, the third to SF = 4 and so on.]
>DL Cost 1
M

INTEGER (0..65535)
[FDD - This is the cost of a RLS.]
[TDD - This is the additional cost of the first DPCH/PDSCH/PUSCH assigned to any user in a cell within a timeslot.]
>DL Cost 2
M

INTEGER (0..65535)
[FDD - This is the cost of a RL.]
[TDD - This is the cost of a DPCH/PDSCH/PUSCH]
>UL Cost 1
M

INTEGER (0..65535)
[FDD - This is the cost of a RLS.]
[TDD - This is the additional cost of the first DPCH/PDSCH/PUSCH assigned to any user in a cell within a timeslot.]
>UL Cost 2
M

INTEGER (0..65535)
[FDD - This is the cost of a RL.]
[TDD - This is the cost of a DPCH/PDSCH/PUSCH.]

Range Bound
Explanation
maxNrOfSF
Maximum number of Spreading Factors 

9.2.1.20B	DL Or Global Capacity Credit
The capacity credit indicates to the CRNC the Downlink or global capacity of a Local Cell or a Local Cell Group.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL Or Global Capacity Credit


INTEGER (0..65535)


9.2.1.20C	DCH Information Response
The DCH Information Response IE provides information for DCHs that have been established or modified.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
DCH Information Response

1..<maxNrOfDCHs>

Only one DCH per set of coordinated DCHs shall be included
–

>DCH ID
M

9.2.1.20

–

>Binding ID
O

9.2.1.4

–

>Transport Layer Address
O

9.2.1.63

–

>Transport Bearer Not Setup Indicator
O

9.2.2.4H
FDD only
YES
ignore

Range Bound
Explanation
maxNrOfDCHs 
Maximum number of DCH per UE

9.2.1.21	DL Power
The DL Power IE indicates a power level relative to the [FDD - primary CPICH power] [TDD - primary CCPCH power] configured in a cell. If Transmit Diversity is applied to a downlink physical channel, the DL Power IE indicates the power offset between the linear sum of the power for this downlink physical channel on all branches and the [FDD - primary CPICH power] [TDD - PCCPCH power] configured in a cell. 
[FDD - If referred to a DPCH, it indicates the power of the transmitted DPDCH symbols.] [FDD - If referred to an FDPCH, it indicates the Reference F-DPCH TX Power.]
[TDD - If referred to a DPCH or PDSCH, it indicates the power of a spreading factor 16 code, the power for a spreading factor 1 code would be 12 dB higher. If referred to a SCCPCH, the DL Power IE specifies the maximum power of the SCCPCH.]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL Power


INTEGER 
(-350..150)
Value = DL Power /10
Unit: dB
Range: -35.0 .. +15.0 dB
Step: 0.1dB

9.2.1.22	Dedicated Measurement Object Type
Void.
9.2.1.23	Dedicated Measurement Type
The Dedicated Measurement Type identifies the type of measurement that shall be performed.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Dedicated Measurement Type


ENUMERATED (
SIR,
SIR Error,
Transmitted Code Power,
RSCP,
Rx Timing Deviation,
Round Trip Time,
…,
Rx Timing Deviation LCR, 
Angle Of Arrival LCR,
HS-SICH reception quality, 
Best Cell Portions, Rx Timing Deviation 7.68Mcps,
Rx Timing Deviation 3.84 Mcps Extended, Best Cell Portions LCR,
AOA per Cell Portion LCR, UE transmission power headroom, DL transport block size)
"RSCP" and "HS-SICH reception quality" are used by TDD only.
"Rx Timing Deviation" and "Rx Timing Deviation 3.84 Mcps Extended" are used by 3.84Mcps TDD only.
"Rx Timing Deviation LCR", "Angle Of Arrival LCR" are used by 1.28Mcps TDD only.
"Round Trip Time", "SIR Error" are used by FDD only.
“Best Cell Portions” is used by FDD only. 
“Best Cell Portions LCR” is used by 1.28Mcps TDD only.
"Rx Timing Deviation 7.68Mcps" is used by 7.68Mcps TDD only.
"UE transmission power headroom" is used by FDD, 1.28Mcps TDD, 3.84Mcps TDD and 7.68Mcps TDD.
"DL transport block size" is used by FDD only.
Note:	For definitions of the measurement types refer to TS 25.215 [4] and TS 25.225 [5].

9.2.1.24	Dedicated Measurement Value
The Dedicated Measurement Value shall be the most recent value for this measurement, for which the reporting criteria were met.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
CHOICE Dedicated Measurement Value
M



–

>SIR Value






>>SIR Value
M

INTEGER (0..63)
According to mapping in TS 25.133 [22] and TS 25.123 [23]
–

>SIR Error Value



FDD only


>>SIR Error Value
M

INTEGER (0..125)
According to mapping in TS 25.133 [22]
–

>Transmitted Code Power Value






>>Transmitted Code Power Value
M

INTEGER (0..127)
According to mapping in TS 25.133 [22] and TS 25.123 [23].
Values 0 to 9 and 123 to 127 shall not be used.
–

>RSCP



TDD only


>>RSCP
M

INTEGER (0..127)
According to mapping in TS 25.123 [23]
–

>Rx Timing Deviation Value



Applicable to 3.84Mcps TDD only


>>Rx Timing Deviation
M

INTEGER (0..8191)
According to mapping in TS 25.123 [23]
–

>Round Trip Time



FDD only


>>Round Trip Time
M

INTEGER (0..32767)
According to mapping in TS 25.133 [22]
–

>Additional Dedicated Measurement Values



See  Note 1.


>>Rx Timing Deviation Value LCR



Applicable to 1.28Mcps TDD only


>>>Rx Timing Deviation LCR
M

INTEGER (0..511)
According to mapping in TS 25.123 [23]
YES
reject
>>Angle Of Arrival Value LCR



Applicable to 1.28Mcps TDD only


>>>AOA Value LCR

1


YES
reject
>>>>AOA LCR
M

INTEGER (0..719)
According to mapping in TS 25.123 [23]
–

>>>>AOA LCR Accuracy Class
M

ENUMERATED (
A, B, C, D, E, F, G, H,...)
According to mapping in TS 25.123 [23]
–

>>HS-SICH Reception Quality



Applicable to TDD only


>>>HS-SICH Reception Quality Value 

1


YES
reject
>>>>Failed HS-SICH
M

INTEGER (0..20)
According to mapping in TS 25.123 [23]
–

>>>>Missed HS-SICH 
M

INTEGER (0..20)
According to mapping in TS 25.123 [23]
–

>>>>Total HS-SICH
M

INTEGER (0..20)
According to mapping in TS 25.123 [23]
–

>>>>Failed HS-SICH LCR extension
O

INTEGER (0..20)
According to mapping in TS 25.123 [23]
Mandatory for LCR TDD when there are more than 20 failed HS-SICH 
YES
reject
>>>>Missed HS-SICH LCR extension
O

INTEGER (0..20)
According to mapping in TS 25.123 [23]
Mandatory for LCR TDD when there are more than 20 missed HS-SICH
YES
reject
>>>>Total HS-SICH LCR extension
O

INTEGER (0..20)
According to mapping in TS 25.123 [23]
Mandatory for LCR TDD when there are more than 20 total HS-SICH
YES
reject
>>Best Cell Portions



FDD only


>>>Best Cell Portions
M

9.2.2.1Ba

YES
reject
>>Rx Timing Deviation Value 7.68Mcps



Applicable to 7.68Mcps TDD only


>>>Rx Timing Deviation 7.68Mcps 
M

INTEGER (0..65535)
According to mapping in TS 25.123 [23]
YES
reject
>>Rx Timing Deviation Value 3.84Mcps Extended



Applicable to 3.84Mcps TDD only


>>>Rx Timing Deviation 3.84Mcps Extended
M

INTEGER (0..32767)
According to mapping in TS 25.123 [23]
YES
reject
>>Extended Round Trip Time



FDD only


>>>Extended Round Trip Time Value
M

INTEGER (32767..103041)
Continuation of intervals with step size as defined in TS 25.133 [22].
YES
reject
>>Best Cell Portions LCR



1.28Mcps TDD only


>>>Best Cell Portions LCR
M

9.2.3.105

YES
reject
>>AOA per Cell Portion LCR



1.28Mcps TDD only


>>>AOA per Cell Portion LCR
M

9.2.3.124

YES
reject
>>UE transmission power headroom






>>>UE transmission power headroom
M

INTEGER (0..31)
According to mapping in TS 25.133 [22] and TS 25.123 [23].
YES
reject
>>DL transport block size



FDD only


>>>HS-DSCH Cell List
M
1..<maxNrOfHSDSCH-1>


EACH
reject
>>>>HS-DSCH Cell TBS
M

INTEGER (0.. 160000)
According to mapping of CQI in TS 25.214 [10].
See Note 2.
–
–
Note 1:	This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1.
Note 2: 	In case of Dual Stream MIMO, this information element is the sum of the transport block size values from both streams of the cell.

Range Bound
Explanation
maxNrOfHSDSCH-1
Maximum number of HS-DSCH cells for one UE

9.2.1.24A	Dedicated Measurement Value Information
The Dedicated Measurement Value Information IE provides information both on whether or not the Dedicated Measurement Value is provided in the message or not and if provided also the Dedicated Measurement Value itself.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Measurement Availability Indicator
M



>Measurement Available




>>Dedicated Measurement Value
M

9.2.1.24

>>CFN
O

9.2.1.7
Dedicated Measurement Time Reference
>Measurement Not Available


NULL


9.2.1.24B	DGPS Corrections
The DGPS Corrections IE contains DGPS information used by the UE Positioning A-GPS method. For further details on the meaning of parameters, see RTCM-SC104 [28].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
GPS TOW
M

INTEGER (0..604799)
Time in seconds. This field indicates the baseline time for which the corrections are valid.
–

Status/Health
M

ENUMERATED (
UDRE scale 1.0, UDRE scale 0.75, UDRE scale 0.5, UDRE scale 0.3, UDRE scale 0.1, 
no data, 
invalid data)
This field indicates the status of the differential corrections.
–

Satellite Information

1..<maxNoSat>


–

>SatID
M

INTEGER (0..63)
Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [27].
–

>IODE
M

BIT STRING (SIZE(8))
This IE is the sequence number for the ephemeris for the particular satellite. It can be used to determine if new ephemeris is used for calculating the corrections that are provided. This eight-bit IE is incremented for each new set of ephemeris for the satellite and may occupy the numerical range of [0, 239] during normal operations.
–

>UDRE
M

ENUMERATED (
UDRE U1.0m,
1.0m < UDRE < 4.0m,
4.0m < UDRE < 8.0m,
8.0m < UDRE)
User Differential Range Error. This field provides an estimate of the uncertainty (1- ) in the corrections for the particular satellite. The value in this field shall be multiplied by the UDRE Scale Factor in the common Corrections Status/Health field to determine the final UDRE estimate for the particular satellite
–

>PRC
M

INTEGER 
(-2047..2047)
Pseudo Range Correction
Unit: m (meters)
Step: 0.32 meters
–

>Range Correction Rate
M

INTEGER 
(-127..127)
Unit: m/s
Step: 0.032 m/s 
–

>DGNSS Validity Period
O

9.2.1.125

YES
ignore

Range Bound
Explanation
maxNoSat
Maximum number of satellites for which information can be provided

9.2.1.24C	Delayed Activation
The Delayed Activation IE indicates that the activation of the DL power shall be delayed until an indicated CFN or until a separate activation indication is received.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Delayed Activation
M



>CFN




>>Activation CFN
M

CFN 9.2.1.7

>Separate Indication


NULL


9.2.1.24D	Delayed Activation Update
The Delayed Activation Update IE indicates a change of the activation of the DL power for a specific RL.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned criticality
CHOICE Delayed Activation Update
M



–

>Activate






>>CHOICE Activation Type
M



–

>>>Synchronised






>>>>Activation CFN
M

CFN 9.2.1.7

–

>>>Unsynchronised


NULL



>>Initial DL TX Power
M

DL Power
9.2.1.21

–

>>First RLS Indicator
O

9.2.2.16A
FDD Only
–

>>Propagation Delay
O

9.2.2.35
FDD Only
–

>>Extended Propagation Delay
O

9.2.2.35A
FDD Only
YES
reject
>Deactivate






>>CHOICE Deactivation Type
M



–

>>>Synchronised






>>>>Deactivation CFN
M

CFN 9.2.1.7

–

>>>Unsynchronised


NULL




9.2.1.24E	Discard Timer
The Discard Timer IE defines the time to live for a MAC-hs SDU starting from the instant of its arrival into an HSDPA Priority Queue. The Node B shall use this information to discard out-of-data MAC-hs SDUs from the HSDPA Priority Queues.
IE/Group Name
Presence
Range
IE type and reference
Semantics description
Discard Timer


ENUMERATED (20, 40, 60, 80, 100, 120, 140, 160, 180, 200, 250, 300, 400, 500, 750, 1000, 1250, 1500, 1750, 2000, 2500, 3000, 3500, 4000, 4500, 5000, 7500, …)
Unit: ms


9.2.1.25	Diversity Control Field
The Diversity Control Field indicates if the current RL may, must or must not be combined with the already existing RLs.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Diversity Control Field


ENUMERATED (
May, 
Must, 
Must Not,
…)


9.2.1.26	Diversity Indication
Void.
9.2.1.26A	DL DPCH Timing Adjustment
Void.
9.2.1.27	DSCH ID
Void.
9.2.1.27A	DSCH Information Response
Void
9.2.1.28	DSCH Transport Format Set
Void.
9.2.1.29	DSCH Transport Format Combination Set
Void.
9.2.1.29A	End Of Audit Sequence Indicator
Indicates if the AUDIT RESPONSE message ends an audit sequence or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
End Of Audit Sequence Indicator


ENUMERATED (
End of audit sequence, 
Not end of audit sequence)
"End of audit sequence" = all audit information has been provided by the Node B.
"Not end of audit sequence" = more audit information is available.

9.2.1.29B	FN Reporting Indicator
The Frame Number Reporting Indicator indicates if the SFN or CFN shall be included together with the reported measurement value.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
FN Reporting Indicator


ENUMERATED (
FN Reporting Required, 
FN Reporting Not Required)


9.2.1.30	Frame Handling Priority
This parameter indicates the priority level to be used during the lifetime of the DCH [TDD - DSCH] for temporary restriction of the allocated resources due overload reason.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Frame Handling Priority


INTEGER (0..15)
"0" = lowest priority,
…
"15" = highest priority

9.2.1.31	Frame Offset
The Frame Offset is the required offset between the dedicated channel downlink transmission frames (CFN, Connection Frame Number) and the broadcast channel frame offset (Cell Frame Number). The Frame Offset is used in the translation between Connection Frame Number (CFN) on Iub/Iur and the least significant 8 bits of SFN (System Frame Number) on Uu. The Frame Offset is UE and cell specific.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Frame Offset


INTEGER (0..255)
Frames

9.2.1.31A	IB_OC_ID
The IB OC ID identifies the occurrence of a specific Information Block.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
IB OC ID


INTEGER (1..16)
Value 1 indicates the first occurrence for the specific Information Block. 
Value 2 indicates the second occurrence for the specific Information Block.
…
Value 16 indicates the sixteenth occurrence for the specific Information Block.

9.2.1.31B	GPS Navigation Model & Time Recovery
This IE contains subframes 1 to 3 of the GPS navigation message. For further details on the meaning of parameters, see ICD-GPS-200 [27].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Navigation Message 1to3

1..<maxNoSat>


>Transmission TOW
M

INTEGER (0..1048575)
Time of the Week when the message is broadcast.
>SatID
M

INTEGER (0..63)
Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [27].
>TLM Message
M

BIT STRING (SIZE(14))

>Tlm Revd (C) 
M

BIT STRING (SIZE (2))

>HO-Word
M

BIT STRING (SIZE (22))

>WN
M

BIT STRING (SIZE (10))

>C/A or P on L2
M

BIT STRING (SIZE (2))

>User Range Accuracy Index
M

BIT STRING (SIZE (4))

>SV Health
M

BIT STRING (SIZE (6))

>IODC
M

BIT STRING (SIZE (10))

>L2 P Data Flag
M

BIT STRING (SIZE (1))

>SF 1 Reserved
M

BIT STRING (SIZE (87))

>TGD
M

BIT STRING (SIZE (8))

>toc
M

BIT STRING (SIZE (16))

>af2
M

BIT STRING (SIZE (8))

>af1
M

BIT STRING (SIZE (16))

>af0
M

BIT STRING (SIZE (22))

>Crs
M

BIT STRING (SIZE (16))

>>n
M

BIT STRING (SIZE (16))

>M0
M

BIT STRING (SIZE (32))

>Cuc
M

BIT STRING (SIZE (16))

>e
M

BIT STRING (SIZE (32))

>Cus
M

BIT STRING (SIZE (16))

>(A)1/2
M

BIT STRING (SIZE (32))

>toe
M

BIT STRING (SIZE (16))

>Fit Interval Flag
M

BIT STRING (SIZE (1))

>AODO
M

BIT STRING (SIZE (5))

>Cic
M

BIT STRING (SIZE (16))

>OMEGA0
M

BIT STRING (SIZE (32))

>Cis
M

BIT STRING (SIZE (16))

>i0
M

BIT STRING (SIZE (32))

>Crc
M

BIT STRING (SIZE (16))

>>
M

BIT STRING (SIZE (32))

>OMEGAdot
M

BIT STRING (SIZE (24))

>Idot
M

BIT STRING (SIZE (14))

>Spare/zero fill
M

BIT STRING (SIZE (20))


Range Bound
Explanation
maxNoSat
Maximum number of satellites for which information can be provided

9.2.1.31C	GPS Ionospheric Model
This IE provides the information regarding the GPS Ionospheric Model. For further details on the meaning of parameters, see ICD-GPS-200 [27].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description

0
M

BIT STRING (SIZE (8))


1
M

BIT STRING (SIZE (8))


2
M

BIT STRING (SIZE (8))


3
M

BIT STRING (SIZE (8))


0
M

BIT STRING (SIZE (8))


1
M

BIT STRING (SIZE (8))


2
M

BIT STRING (SIZE (8))


3
M

BIT STRING (SIZE (8))


9.2.1.31D	GPS UTC Model
This IE provides the information regarding the GPS UTC Model. For further details on the meaning of parameters, see ICD-GPS-200 [27].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
A1
M

BIT STRING (SIZE (24))

A0
M

BIT STRING (SIZE (32))

tot
M

BIT STRING (SIZE (8))


tLS
M

BIT STRING (SIZE (8))

WNt
M

BIT STRING (SIZE (8))

WNLSF
M

BIT STRING (SIZE (8))

DN
M

BIT STRING (SIZE (8))


tLSF
M

BIT STRING (SIZE (8))


9.2.1.31E	GPS Real-Time Integrity
This IE provides the information regarding the status of the GPS constellation. For further details on the meaning of parameters, see ICD-GPS-200 [27].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Bad Satellites Presence
M



>Bad Satellites




>>Satellite Information

1..<maxNoSat>


>>>BadSatID
M

INTEGER (0..63)
Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [27].
>No Bad Satellites


NULL


Range Bound
Explanation
maxNoSat
Maximum number of satellites for which information can be provided

9.2.1.31F	GPS Almanac
This IE provides the information regarding the GPS Almanac. For further details on the meaning of parameters, see ICD-GPS-200 [27].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
WNa
M

BIT STRING (SIZE (8))

–

Satellite Information
M
1..<maxNoOfSatAlmanac>

See Note 1.
–

>DataID
M

INTEGER (0..3)

–

>SatID
M

INTEGER (0..63)
Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [27].
–

>e
M

BIT STRING (SIZE (16))

–

>toa
M

BIT STRING (SIZE (8))

–

>>i
M

BIT STRING (SIZE (16))

–

>OMEGADOT
M

BIT STRING (SIZE (16))

–

>SV Health
M

BIT STRING (SIZE (8))

–

>A1/2
M

BIT STRING (SIZE (24))

–

>OMEGA0
M

BIT STRING (SIZE (24))

–

>M0
M

BIT STRING (SIZE (24))

–

>>
M

BIT STRING (SIZE (24))

–

>af0
M

BIT STRING (SIZE (11))

–

>af1
M

BIT STRING (SIZE (11))

–

SV Global Health
O

BIT STRING (SIZE (364))

–

Complete Almanac Provided
O

BOOLEAN
This field indicates whether almanac is provided for the full GPS constellation or not. TRUE means complete GPS almanac is provided
YES
ignore
Note 1:	This information element is a simplified representation of the ASN.1 description. Repetitions 1 through maxNoSat and repetitions maxNoSat+1 through maxNoOfSatAlmanac are represented by separate ASN.1 structures with different criticality.



Range Bound
Explanation
maxNoOfSatAlmanac
Maximum number of satellite almanacs for which information can be provided

9.2.1.31G	GPS Receiver Geographical Position (GPS RX Pos)
The GPS Receiver Geographical Position is used to identify the geographical coordinates of a GPS receiver relevant for a certain Information Exchange Object.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Latitude Sign
M

ENUMERATED (
North, 
South) 

Degrees of Latitude
M

INTEGER (0..223-1)
The IE value (N) is derived by this formula:
NN223 X /90 / N+1
X being the latitude in degree (0°.. 90°)
Degrees of Longitude
M

INTEGER 
(-223..223-1)
The IE value (N) is derived by this formula:
NN224 X /360 / N+1
X being the longitude in degree (-180°..+180°)
Direction of Altitude
M

ENUMERATED (
Height, 
Depth)

Altitude
M

INTEGER (0..215-1)
The relation between the value (N) and the altitude (a) in meters it describes is NT a <N+1, except for N=215-1 for which the range is extended to include all greater values of (a).

9.2.1.31Ga	HSDPA Capability
This parameter defines the HSDPA capability for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HSDPA Capability


ENUMERATED (HSDPA Capable, HSDPA non Capable)


9.2.1.31H	HS-DSCH Information To Modify
The HS-DSCH Information To Modify IE is used for modification of HS-DSCH information in a Node B Communication Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-DSCH MAC-d Flow Specific Information

0..<maxNrOfMACdFlows>


–

>HS-DSCH MAC-d Flow ID
M

9.2.1.31I

–

>Allocation/Retention Priority
O

9.2.1.1A

–

>Transport Bearer Request Indicator
M

9.2.1.62A

–

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
–

>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
–

>TNL QoS 
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
Priority Queue Information

0..<maxNrOfPriorityQueues>


–

>CHOICE Priority Queue
M



–

>>Add Priority Queue






>>>Priority Queue ID
M

9.2.1.49C

–

>>>Associated HS-DSCH MAC-d Flow
M

HS-DSCH MAC-d Flow ID
9.2.1.31I
Shall only refer to an HS-DSCH MAC-d flow already existing in the old configuration.
Multiple Priority Queues can be associated with the same HS-DSCH MAC-d Flow ID.
–

>>>Scheduling Priority Indicator
M

9.2.1.53H

–

>>>T1
M

9.2.1.56a

–

>>>Discard Timer
O

9.2.1.24E

–

>>>MAC-hs Window Size
M

9.2.1.38B

–

>>>MAC-hs Guaranteed Bit Rate
O

9.2.1.38Aa

–

>>>MAC-d PDU Size Index

1..<maxNrOfMACdPDUIndexes>


–

>>>>SID
M

9.2.1.53I
Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.
–

>>>>MAC-d PDU Size
M

9.2.1.38A
Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.
–

>>>RLC Mode
M

9.2.1.52B

–

>>>Maximum MAC-d PDU Size Extended
O

MAC PDU Size Extended
9.2.1.38C

YES
reject
>>>DL RLC PDU Size Format
O

9.2.1.122

Yes
ignore
>>Modify Priority Queue






>>>Priority Queue ID
M

9.2.1.49C
Shall only refer to a Priority Queue already existing in the old configuration.
–

>>>Scheduling Priority Indicator
O

9.2.1.53H

–

>>>T1
O

9.2.1.56a

–

>>>Discard Timer
O

9.2.1.24E

–

>>>MAC-hs Window Size
O

9.2.1.38B

–

>>>MAC-hs Guaranteed Bit Rate
O

9.2.1.38Aa

–

>>>MAC-d PDU Size Index

0..<maxNrOfMACdPDUIndexes>


–

>>>>SID
M

9.2.1.53I
Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.
–

>>>>MAC-d PDU Size
M

9.2.1.38A
Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.
–

>>>Maximum MAC-d PDU Size Extended
O

MAC PDU Size Extended
9.2.1.38C

YES
reject
>>>DL RLC PDU Size Format
O

9.2.1.122

Yes
ignore
>>Delete Priority Queue






>>>Priority Queue ID
M

9.2.1.49C
Shall only refer to a Priority Queue already existing in the old configuration.
–

MAC-hs Reordering Buffer Size for RLC-UM
O

9.2.1.38Ab

–

CQI Feedback Cycle k
O

9.2.2.21B
For FDD only
–

CQI Repetition Factor
O

9.2.2.4Cb
For FDD only
–

ACK-NACK Repetition Factor
O

9.2.2.a
For FDD only
–

CQI Power Offset
O

9.2.2.4Ca
For FDD only 
–

ACK Power Offset
O

9.2.2.b
For FDD only
–

NACK Power Offset
O

9.2.2.23a
For FDD only
–

HS-SCCH Power Offset
O

9.2.2.18I
For FDD only
–

Measurement Power Offset
O

9.2.2.21C
For FDD only
–

HS-SCCH Code Change Grant
O

9.2.1.31L

–

TDD ACK NACK Power Offset
O

9.2.3.18F
For TDD only
–

HARQ Preamble Mode
O

9.2.2.18a
For FDD only
YES
ignore
HS-SICH SIR Target
O

UL SIR
9.2.1.67A
Applicable to 1.28Mcps TDD only
YES
ignore
UE Capabilities Information

0..1


YES
ignore
>HS-DSCH Physical Layer Category
M

9.2.1.31Ia

–

>1.28 Mcps TDD Uplink Physical Channel Capability
O

9.2.3.5Gc
Applicable to 1.28Mcps TDD only
YES
ignore
>Number of Supported Carriers
O

ENUMERATED (
One-one carrier, One-three carrier, Three-three carrier, One-six carrier,
Three-six carrier,
Six-six carrier, ..., One-Two carrier Discontiguous, Two-Twocarrier Discontiguous, One-Two carrier Contiguous, Two-Two carrier Contiguous)
Applicable to 1.28Mcps TDD only
This IE indicates the number of carrier(s) the UE can support at the same time, where ”x-y carrier” means x for the uplink, and y for the downlink.
One-Two carrier Discontiguous and Two-Two carrier Discontiguous mean that the UE is capable of supporting two non-adjacent carriers.
One-Two carrier Contiguous and Two-Two carrier Contiguous mean that the UE is only capable of supporting two adjacent carriers.
YES
reject
>Multi-carrier HS-DSCH Physical Layer Category
O

HS-DSCH Physical Layer Category 9.2.1.31Ia
Applicable to 1.28Mcps TDD only
YES
ignore
>MIMO SF Mode Supported For HS-PDSCH dual stream
O

Enumerated (SF1, SF1/SF16)
Applicable to 1.28Mcps TDD only
YES
ignore
>UE TS0 Capability LCR
O

9.2.3.110
Applicable to 1.28Mcps TDD only.
YES
ignore
>UE RF Band Capability LCR
C-NofSupportedCarriers

9.2.3.125
Applicable to 1.28Mcps TDD only.
YES
ignore
HS-SICH TPC step size
O

TDD TPC UL Step Size 9.2.3.21a
Applicable to 1.28Mcps TDD only
YES
ignore
HS-PDSCH Code Change Grant
O

9.2.1.31N
For FDD only
YES
ignore
MIMO Mode Indicator
O

9.2.1.120
For FDD and 1.28Mcps TDD only
YES
reject
HS-DSCH MAC-d PDU Size Format 
O

9.2.1.31ID

YES
reject
Sixtyfour QAM Usage Allowed Indicator
O

9.2.2.74A
For FDD only
YES
ignore
Enhanced HS Serving CC Abort
O

ENUMERATED (Abort Enhanced HS Serving CC, …)
For FDD only
YES
reject
UE Support Indicator Extension
O

9.2.2.117
 
YES
ignore
Single Stream MIMO Mode Indicator
O

9.2.2.124
For FDD only
YES
reject
Puncturing Handling in First Rate Matching Stage
O

9.2.2.149
For FDD only
YES
ignore
MIMO with four transmit antennas Mode Indicator
O

9.2.2.166
For FDD only
YES
reject
Dual Stream MIMO with four transmit antennas Mode Indicator
O

9.2.2.168
For FDD only
YES
reject
Multiflow Reconfiguration
O

9.2.2.169
For FDD only
YES
reject
CQI Feedback Cycle2 k
O

CQI Feedback Cycle k2
9.2.2.206
For FDD only
YES
ignore
CQI Cycle Switch Timer
O

ENUMERATED (v4, v8, v16, v32, v64, v128, v256, v512, Infinity)
For FDD only, refer to TS 25.331 [16].
YES
ignore

Condition
Explanation
NofSupportedCarriers
This IE shall be present if the Number of Supported Carriers IE is equal to "One-Two carrier Discontiguous" or "Two-Two carrier Discontiguous" and the concerned cell and the UE support more than one RF band.

Range Bound
Explanation
maxNrOfMACdFlows
Maximum number of HS-DSCH MAC-d flows
maxNrOfPriorityQueues
Maximum number of Priority Queues
maxNrOfMACdPDUIndexes
Maximum number of different MAC-d PDU SIDs

9.2.1.31HA	HS-DSCH Information To Modify Unsynchronised
The HS-DSCH Information To Modify Unsynchronised IE is used for modification of HS-DSCH information in a Node B Communication Context with the Unsynchronised Radio Link Reconfiguration procedure.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-DSCH MAC-d Flow Specific Information

0..<maxNrOfMACdFlows>


–

>HS-DSCH MAC-d Flow ID
M

9.2.1.31I

–

>Allocation/Retention Priority
O

9.2.1.1A

–

>Transport Bearer Request Indicator
M

9.2.1.62A

–

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
–

>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
–

>TNL QoS 
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
Priority Queue Information

0..<maxNrOfPriorityQueues>


–

>Priority Queue ID
M

9.2.1.49C

–

>Scheduling Priority Indicator
O

9.2.1.53H

–

>Discard Timer
O

9.2.1.24E

–

>MAC-hs Guaranteed Bit Rate
O

9.2.1.38Aa

–

CQI Power Offset
O

9.2.2.4Ca
For FDD only 
–

ACK Power Offset
O

9.2.2.b
For FDD only
–

NACK Power Offset
O

9.2.2.23a
For FDD only
–

HS-SCCH Power Offset
O

9.2.2.18I
For FDD only
–

TDD ACK NACK Power Offset
O

9.2.3.18F
For TDD only
–

HARQ Preamble Mode
O

9.2.2.18a
For FDD only
YES
ignore
HS-SICH SIR Target
O

UL SIR
9.2.1.67A
Applicable to 1.28Mcps TDD only
YES
ignore
UE Capabilities Information

0..1


YES
ignore
>HS-DSCH Physical Layer Category
M

9.2.1.31Ia

YES
ignore
>1.28 Mcps TDD Uplink Physical Channel Capability
O

9.2.3.5Gc
Applicable to 1.28Mcps TDD only
YES
ignore
>Number of Supported Carriers
O

ENUMERATED (
One-one carrier, One-three carrier, Three-three carrier, One-six carrier,
Three-six carrier,
Six-six carrier, ..., One-Two carrier Discontiguous, Two-Two carrier Discontiguous, One-Two carrier Contiguous, Two-Two carrier Contiguous)
Applicable to 1.28Mcps TDD only
This IE indicates the number of carrier(s) the UE can support at the same time, where ”x-y carrier” means x for the uplink, and y for the downlink.
One-Two carrier Discontiguous and Two-Two carrier Discontiguous mean that the UE is capable of supporting two non-adjacent carriers.
One-Two carrier Contiguous and Two-Two carrier Contiguous mean that the UE is only capable of supporting two adjacent carriers.
YES
reject
>Multi-carrier HS-DSCH Physical Layer Category
O

HS-DSCH Physical Layer Category 9.2.1.31Ia
Applicable to 1.28Mcps TDD only
YES
ignore
>MIMO SF Mode Supported For HS-PDSCH dual stream
O

Enumerated (SF1, SF1/SF16)
Applicable to 1.28Mcps TDD only

YES
ignore
>UE TS0 Capability LCR
O

9.2.3.110
Applicable to 1.28Mcps TDD only.
YES
ignore
>UE RF Band Capability LCR
C-NofSupportedCarriers

9.2.3.125
Applicable to 1.28Mcps TDD only.
YES
ignore
HS-SICH TPC step size
O

TDD TPC UL Step Size 9.2.3.21a
Applicable to 1.28Mcps TDD only
YES
ignore
MIMO Mode Indicator
O

9.2.1.120
For FDD and 1.28Mcps TDD only
YES
reject
Sixtyfour QAM Usage Allowed Indicator
O

9.2.2.74A
For FDD only
YES
ignore
Enhanced HS Serving CC Abort
O

ENUMERATED (Abort Enhanced HS Serving CC, …)
For FDD only
YES
reject
UE Support Indicator Extension
O

9.2.2.117
 
YES
ignore
Single Stream MIMO Mode Indicator
O

9.2.2.124
For FDD only
YES
reject
Puncturing Handling in First Rate Matching Stage
O

9.2.2.149
For FDD only
YES
ignore
MIMO with four transmit antennas Mode Indicator
O

9.2.2.166
For FDD only
YES
reject
Dual Stream MIMO with four transmit antennas Mode Indicator
O

9.2.2.168
For FDD only
YES
reject
Multiflow Reconfiguration
O

9.2.2.169
For FDD only
YES
reject

Condition
Explanation
NofSupportedCarriers
This IE shall be present if the Number of Supported Carriers IE is equal to "One-Two carrier Discontiguous" or "Two-Two carrier Discontiguous" and the concerned cell and the UE support more than one RF band.

Range Bound
Explanation
maxNrOfMACdFlows
Maximum number of HS-DSCH MAC-d flows
maxNrOfPriorityQueues
Maximum number of Priority Queues

9.2.1.31Ha	HS-DSCH Initial Capacity Allocation
The HS-DSCH Initial Capacity Allocation IE provides flow control information for each scheduling priority class for the HS-DSCH FP over Iub.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-DSCH Initial Capacity Allocation

1..<maxNrOfPriorityQueues>


–

>Scheduling Priority Indicator
M

9.2.1.53H

–

>Maximum MAC-d PDU Size
M

MAC-d PDU Size 9.2.1.38A
Shall be ignored if Maximum MAC-d PDU Size Extended  IE is present.
–

>HS-DSCH Initial Window Size
M

9.2.1.31Hb

–

>Maximum MAC-d PDU Size Extended
O

MAC PDU Size Extended
9.2.1.38C

YES
ignore

Range Bound
Explanation
maxNrOfPriorityQueues
Maximum number of Priority Queues

9.2.1.31Hb	HS-DSCH Initial Window Size
Indicates the initial number of MAC-d PDUs (or octets in case HS-DSCH MAC-d PDU Size Format = "Flexible MAC-d PDU Size") that may be transmitted before new credits are received from the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH Initial Window Size


INTEGER (1..255)
Number of MAC-d PDUs
If HS-DSCH MAC-d PDU Size Format = "Flexible MAC-d PDU Size" the credit shall be determined in octets:
credit (in octets)  = Maximum MAC-d PDU Size Extended * HS-DSCH Initial Window Size

9.2.1.31I	HS-DSCH MAC-d Flow ID
HS-DSCH MAC-d Flow ID is the unique identifier for one MAC-d flow.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH MAC-d Flow ID


INTEGER (0..7)


9.2.1.31IA	HS-DSCH MAC-d Flows Information
The HS-DSCH MAC-d Flows Information IE is used for the establishment of HS-DSCH MAC-d flows for a Node B Communication Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-DSCH MAC-d Flow Specific Information

1..<maxNrOfMACdFlows>


–

>HS-DSCH MAC-d Flow ID
M

9.2.1.31I

–

>Allocation/Retention Priority
M

9.2.1.1A

–

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
–

>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
–

>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
Priority Queue Information

1..<maxNrOfPriorityQueues>


–

>Priority Queue ID
M

9.2.1.49C

–

>Associated HS-DSCH MAC-d Flow
M

HS-DSCH MAC-d Flow ID
9.2.1.31I
The HS-DSCH MAC-d Flow ID shall be one of the flow IDs defined in the HS-DSCH MAC-d Flow Specific Information of this IE.
Multiple Priority Queues can be associated with the same HS-DSCH MAC-d Flow ID.
–

>Scheduling Priority Indicator
M

9.2.1.53H

–

>T1
M

9.2.1.56a

–

>Discard Timer
O

9.2.1.24E

–

>MAC-hs Window Size
M

9.2.1.38B

–

>MAC-hs Guaranteed Bit Rate
O

9.2.1.38Aa

–

>MAC-d PDU Size Index

1..<maxNrOfMACdPDUIndexes>


–

>>SID
M

9.2.1.53I
Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.
–

>>MAC-d PDU Size
M

9.2.1.38A
Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.
–

>RLC Mode
M

9.2.1.52B

–

>Maximum MAC-d PDU Size Extended
O

MAC PDU Size Extended
9.2.1.38C

YES
reject
>DL RLC PDU Size Format
O

9.2.1.122

YES
ignore
>UE Aggregate Maximum Bit Rate Enforcement Indicator
O

NULL

YES
ignore

Range Bound
Explanation
maxNrOfMACdFlows
Maximum number of HS-DSCH MAC-d flows
maxNrOfPriorityQueues
Maximum number of Priority Queues
maxNrOfMACdPDUIndexes
Maximum number of different MAC-d PDU SIDs

9.2.1.31IB	HS-DSCH MAC-d Flows To Delete
The HS-DSCH MAC-d Flows To Delete IE is used for the removal of HS-DSCH MAC-d flows from a Node B Communication Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH MAC-d Flows To Delete

1..<maxNrOfMACdFlows>


>HS-DSCH MAC-d Flow ID
M

9.2.1.31I


Range Bound
Explanation
maxNrOfMACdFlows
Maximum number of HS-DSCH MAC-d flows

9.2.1.31IC	HS-DSCH MAC-d PDU Size Capability
This parameter defines the  capability for a Local Cell to support different MAC-d PDU Size formats. If this IE is set to "Flexible Size Capable" the Local Cell  is "Indexed Size Capable" and "Flexible Size Capable". If this IE has not been configured or has been set to "Indexed Size Capable"  the Local Cell is only  "Indexed Size Capable".
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH MAC-d PDU Size Capability  


ENUMERATED (Indexed Size Capable, Flexible Size Capable)


9.2.1.31ID	HS-DSCH MAC-d PDU Size Format
The  HS-DSCH MAC-d PDU Size Format  IE provides information about the type of MAC-d PDU Size Format used for HS-DSCH. "Indexed MAC-d PDU Size" uses MAC-d PDU sizes based on SID IE and MAC-d PDU Size IE of MAC-d PDU Size Index IE. "Flexible MAC-d PDU Size" uses a flexible MAC-d PDU size with a maximum PDU size as defined by Maximum MAC-d PDU Size Extended IE of Priority Queue Information IE. The actual MAC-d PDU size is determined as specified in TS 25.435 [24] and TS 25.321 [32].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH MAC-d PDU Size Format 


ENUMERATED (Indexed MAC-d PDU Size, Flexible MAC-d PDU Size)


9.2.1.31Ia	HS-DSCH Physical Layer Category
The HS-DSCH Physical Layer Category IE defines a set of UE radio access capabilities related to HSDPA, as defined in TS 25.306 [33].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH Physical Layer Category 


INTEGER (1..64,…)


9.2.1.31Iaa	HS-DSCH Provided Bit Rate Value
The HS-DSCH Provided Bit Rate Value IE indicates the HS-DSCH Provided Bit Rate as defined in TS 25.321 [32].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH Provided Bit Rate Value


INTEGER 
(0..2^24-1, …, 2^24..1,000,000,000)
Expressed in bit/s for FDD, 1.28Mcps TDD and 3.84Mcps TDD.
For 7.68Mcps TDD the value shall be doubled to give the value in bit/s.

9.2.1.31Ib	HS-DSCH Provided Bit Rate Value Information
The HS-DSCH Provided Bit Rate Value Information IE reports the HS-DSCH Provided Bit Rate Value IE for each priority class.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH Provided Bit Rate Value Information

1..<maxNrOfPriorityClasses>


>Scheduling Priority Indicator
M

9.2.1.53H

>HS-DSCH Provided Bit Rate Value
M

9.2.1.31Iaa


Range Bound
Explanation
maxNrOfPriorityClasses
Maximum number of HS-DSCH Scheduling Priorities

9.2.1.31Iba	HS-DSCH Required Power Value
The HS-DSCH Required Power Value IE indicates the minimum necessary power for a given priority class to meet the Guaranteed Bit Rate for all the established HS-DSCH connections belonging to this priority class.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH Required Power Value


INTEGER (0..1000)
Expressed in thousandths of the max transmission power

9.2.1.31Ic	HS-DSCH Required Power Value Information
The HS-DSCH Required Power Value Information IE reports the HS-DSCH Required Power Value IE for each priority class. For each priority class, a list of UEs, identified by the CRNC Communication Context IEs, requiring a particularly high amount of power to meet the Guaranteed Bit Rate for their established HS-DSCH connections may be included. Additionally, the HS-DSCH Required Power Per UE Weight IE may be included for each of those UEs.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH Required Power Value Information

1..<maxNrOfPriorityClasses>


>Scheduling Priority Indicator
M

9.2.1.53H

>HS-DSCH Required Power Value
M

9.2.1.31Iba

>HS-DSCH Required Power Per UE Information

0..<maxNrOfContextsOnUeList>

List of UEs with Guaranteed Bit Rate indicating their required power consumption relative to the HS-DSCH Required Power Value.
>>CRNC Communication Context ID
M

9.2.1.18
The reserved value "All CRNCCC" shall not be used.
>>HS-DSCH Required Power Per UE Weight
O

INTEGER (0..100)
Expressed in percentage of the value provided in the HS-DSCH Required Power Value IE 

Range Bound
Explanation
maxNrOfContextsOnUeList
Maximum number of Communication Contexts to include in the list of UEs
maxNrOfPriorityClasses
Maximum number of HS-DSCH Scheduling Priorities

9.2.1.31J	HS-DSCH RNTI
The HS-DSCH RNTI is used for the UE-specific CRC in HS-SCCH and HS-DSCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH RNTI


INTEGER (0..65535)


9.2.1.31K	HS-SCCH Code Change Indicator
The HS-SCCH Code Change Indicator indicates whether the HS-SCCH Code change is needed or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-SCCH Code Change Indicator


ENUMERATED (HS-SCCH Code Change needed)


9.2.1.31L	HS-SCCH Code Change Grant
The HS-SCCH Code Change Grant IE indicates that modification of HS-SCCH Codes is granted.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-SCCH Code Change Grant


ENUMERATED
(Change Granted)


9.2.1.31M	HS-PDSCH Code Change Indicator [FDD]
The HS-PDSCH Code Change Indicator indicates whether the HS-PDSCH Code change is needed or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-PDSCH Code Change Indicator


ENUMERATED (HS-PDSCH Code Change needed)


9.2.1.31N	HS-PDSCH Code Change Grant [FDD]
The HS-PDSCH Code Change Grant IE indicates that modification of HS-PDSCH Codes is granted.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-PDSCH Code Change Grant


ENUMERATED
(Change Granted)


9.2.1.32	IB_SG_DATA
Segment as defined in ref. TS 25.331 [18].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
IB_SG_DATA


BIT STRING
Contains "SIB data fixed" or "SIB data variable" in segment as encoded in ref. TS 25.331 [18].
See Annex D

9.2.1.33	IB_SG_POS
The lowest position of a specific Information Block segment in the SFN cycle (IB_SG_POS < IB_SG_REP).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
IB_SG_POS


INTEGER (0..4094)
Only even positions are allowed.
See ref. TS 25.331 [18]

9.2.1.34	IB_SG_REP
Repetition distance for an Information Block segment. The segment shall be transmitted when SFN mod IB_SG_REP = IB_SG_POS.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
IB_SG_REP


ENUMERATED 
(4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096)
Repetition period for the IB segment in frames

9.2.1.35	IB Type
The IB Type identifies a specific system information block.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
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,
not-Applicable-SIB20,
SIB21,
SIB22,
SIB15.1ter,
SB3,
SIB23,
SIB24,
SIB11ter,
SIB25
)


9.2.1.36	Indication Type
Void.
9.2.1.36A	Information Exchange Object Type
Void.
9.2.1.36B	Information Report Characteristics
The information report characteristics defines how the reporting shall be performed.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Information Report Characteristics Type
M



>On Demand


NULL

>Periodic




>>CHOICE Information Report Periodicity Scale
M


The frequency with which the Node B shall send information reports.
>>>minute




>>>>Report Periodicity Value
M

INTEGER (1..60,…)
Unit: min
>>>hour




>>>>Report Periodicity Value
M

INTEGER (1..24,…)
Unit: h
>On Modification




>>Information Threshold
O

9.2.1.36E


9.2.1.36C	Information Exchange ID
The Information Exchange ID uniquely identifies any requested information per Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Information Exchange ID
M

INTEGER 
(0..2^20-1)


9.2.1.36D	Information Type
The Information Type indicates which kind of information the Node B shall provide.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Information Type Item
M

ENUMERATED (
GPS Information,
DGPS Corrections,
GPS RX Pos, 
…,
GANSS Information, DGANSS Corrections, GANSS RX Pos)

–

GPS Information
C-GPS
0..<maxNoGPSItems>


–

>GPS Information Item


ENUMERATED (
GPS Navigation Model & Time Recovery, 
GPS Ionospheric Model,
GPS UTC Model,
GPS Almanac, 
GPS Real-Time Integrity,
…)

–

GANSS Information
C-GANSS
1


YES
ignore
>GANSS Common Data

0..1


–

>>Ionospheric Model
O

BOOLEAN
True means requested
–

>>Additional Ionospheric Model
O

Additional Ionospheric Model Request 9.2.1.107d
Presence means requested.
YES
ignore
>>Earth Orientation Parameters
O

Earth Orientation Parameters  Request 9.2.1.107e

YES
ignore
>GANSS Generic Data

0..<maxNoGANSS>


–

>>GANSS ID
O

9.2.1.104

–

>>GANSS Navigation Model And Time Recovery
O

BOOLEAN
True means requested
–

>>GANSS Time Model GNSS-GNSS
O

BIT STRING (SIZE(9))
Defines the time model required. 

Bit 1 is the MSB and bit 9 is the LSB (see section 9.2.0).

Bit 1:GPS,
Bit 2:Galileo,
Bit 3:QZSS,
Bit 4: GLONASS,
Bit 5: BDS.

Other bits are reserved.
–

>>GANSS UTC Model
O

BOOLEAN
True means requested
–

>>GANSS Almanac
O

BOOLEAN
True means requested
–

>>GANSS Real Time Integrity
O

BOOLEAN
True means requested
–

>>GANSS Data Bit Assistance

0..1


–

>>>GANSS TOD
M

INTEGER (0..86399)
The GANSS Time Of Day for which the data bits are requested
–

>>>Data Bit Assistance

1


–

>>>>DGANSS Signal ID
M

BIT STRING (SIZE(8))
Defined in TS 25.331 [18]
–

>>>>GANSS Data Bit Interval
M

INTEGER (0..15)
Defined in TS 25.331 [18]
–

>>>>Satellite Information

0..<maxGANSSSat>


–

>>>>Sat ID
M

INTEGER(0..63)
Identifies the satellite and is equal to (SV ID No - 1)
–

>>GANSS Additional Navigation Models And Time Recovery
O

GANSS Additional Navigation Models And Time Recovery  Request 9.2.1.107f

YES
ignore
>>GANSS Additional UTC Models
O

GANSS Additional UTC Models Request 9.2.1.107g

YES
ignore
>>GANSS Auxiliary Information
O

GANSS Auxiliary Information  Request 
9.2.1.107h

YES
ignore
>>SBAS ID
C-GANSS-ID

9.2.1.107b

YES
ignore
>>DBDS Corrections Request

0..1


–

>>>DGANSS Signal ID
M

BIT STRING (SIZE(8))
Defined in TS 25.331 [18]
–

>>BDS Ionospheric Grid Model Request
O

ENUMERATED (requested, …)

YES
ignore
DGANSS Corrections Req
C-DGANSSCorrections
1


YES
ignore
>DGANSS Signal ID
M

BIT STRING (SIZE(8))
Defined in TS 25.331 [18]
–

>GANSS ID
O

9.2.1.104

–


Condition
Explanation
DGANSSCorrections
The IE shall be present if the Information Type Item IE indicates "DGANSS Corrections".
GPS
The IE shall be present if the Information Type Item IE indicates "GPS Information".
GANSS
The IE shall be present if the Information Type Item IE indicates "GANSS Information".
GANSS-ID
This IE shall be present if the GANSS ID IE indicates “SBAS”.

Range Bound
Explanation
maxGANSSSat
Maximum number of satellites for which data is included in the IE
maxNoGPSItems
Maximum number of GPS Information Items supported in one Information Exchange
maxNoGANSS
Maximum number of GANSS Systems

9.2.1.36E	Information Threshold
The Information Threshold indicates which kind of information shall trigger the Information Reporting procedure.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Information Type Item
M



>DGPS




>>PRC Deviation
M

ENUMERATED 
(1, 2, 5, 10, …)
PRC deviation in meters from the previously reported value, which shall trigger a report
>DGANSS




>>PRC Deviation
M

ENUMERATED 
(1, 2, 5, 10, …)
PRC deviation in meters from the previously reported value, which shall trigger a report

9.2.1.36F	IPDL Indicator
Indicates if IPDL periods shall be active or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
IPDL Indicator


ENUMERATED (
active, 
inactive)


9.2.1.37	Limited Power Increase
Void.

9.2.1.37A	Local Cell Group ID
The Local Cell Group ID represents resources in the Node B, which have been pooled from a capacity point of view.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Local Cell Group ID


Local Cell ID
9.2.1.38


9.2.1.38	Local Cell ID
The local cell ID represents resources in the Node B that can be used for the configuration of a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Local Cell ID


INTEGER (0…268435455)


9.2.1.38A	MAC-d PDU Size
The MAC-d PDU Size provides the size in bits of the MAC-d PDU.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MAC-d PDU Size


INTEGER (1..5000,…)
In case of E-DCH, value 8 and values not multiple of 8 shall not be used.

9.2.1.38Aa	MAC-hs Guaranteed Bit Rate
The MAC-hs Guaranteed Bit Rate IE indicates the guaranteed number of bits per second that Node B should deliver over the air interface under normal operating conditions (provided there is data to deliver). If the MAC-hs Guaranteed Bit Rate IE is received with the value set to 0 during RL set up or modification, no guarantee is applied.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MAC-hs Guaranteed Bit Rate


INTEGER 
(0..2^24-1, …, 2^24..1,000,000,000)
Unit: bit/s

9.2.1.38Ab	MAC-hs Reordering Buffer Size for RLC-UM
The MAC-hs Reordering Buffer Size for RLC-UM IE indicates the portion of the buffer in the UE that can be used for RLC-UM traffic (i.e. for Priority Queues whose RLC Mode IE is set to "RLC-UM").
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MAC-hs Reordering Buffer Size


INTEGER
(0..300,…)
Unit: kBytes
And N kBytes = N*1024 Bytes.
The Node B shall use this value to avoid the overflow of the MAC-hs reordering buffer.

9.2.1.38Ac	MAC-hs Reset Indicator
The MAC-hs Reset Indicator IE indicates that a reset of the MAC-hs is not required.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MAC-hs Reset Indicator


ENUMERATED (MAC-hs
Not Reset)


9.2.1.38B	MAC-hs Window Size 
The MAC-hs Window Size IE is used for MAC-hs/MAC-ehs PDU retransmission as defined in TS 25.321 [32]. [FDD - the values 64, 128 and 256 is only allowed when the MAC header type is MAC-ehs and under conditions defined in TS 25.321 [32].]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MAC-hs Window Size


ENUMERATED (4, 6, 8, 12, 16, 24, 32,… , 64, 128, 256)
For 1.28Mcps TDD when TSN length is configured to 9bits, ENUMERATED (32, 64, 96, 128, 160, 192, 256,…)

9.2.1.38C	MAC PDU Size Extended
The MAC PDU Size Extended IE provides the size in octets of the MAC level PDU when an extended MAC level PDU size is required.  
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MAC PDU Size Extended


INTEGER (1..1504,…,1505)
In case of E-DCH, value 1 shall not be used

9.2.1.39	Maximum DL Power Capability
This parameter indicates the maximum DL power capability for a local cell or a Power Local Cell Group within the Node B. The reference point is the antenna connector. If Transmit Diversity can be used in the local cell, the parameter indicates the maximum for the linear sum of the power that can be used on all branches.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Maximum DL Power Capability


INTEGER (0..500)
Unit: dBm
Range: 0..50 dBm
Step: 0.1 dB

9.2.1.40	Maximum Transmission Power
The Maximum Transmission Power is the maximum value for the linear sum of the power of all downlink physical channels, that is allowed to be used in a cell. If Transmit Diversity is applied to one downlink physical channel, the power to be considered for this downlink physical channel is the linear sum of the power used for this downlink physical channel on all branches. [1.28Mcps TDD - For a multi-frequency cell, the Maximum Transmission Power is the maximum value for the linear sum of the power of all downlink physical channels, that is allowed to be used on one frequency in a cell.] The reference point is the antenna connector.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Maximum Transmission Power


INTEGER (0..500)
Unit: dBm
Range: 0..50
Step: 0.1 dB

9.2.1.40A	Measurement Availability Indicator
Void.
9.2.1.40B	Measurement Change Time

IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Time Scale
M



>millisecond




>>Measurement Change Time Value
M

INTEGER (1..6000,…)
Unit: ms
Range: 10..60000 ms
Step: 10 ms

9.2.1.41	Measurement Filter Coefficient
The Measurement Filter Coefficient determines the amount of filtering to be applied for measurements.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Measurement Filter Coefficient


ENUMERATED (
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19,...)


9.2.1.41A	Measurement Hysteresis Time
The Measurement Hysteresis Time provides the duration during which a reporting criterion has to be fulfilled for the Measurement Reporting procedure to be triggered.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Time Scale
M



>millisecond




>>Measurement Hysteresis Time Value
M

INTEGER (1..6000,…)
Unit: ms
Range: 10..60000 ms
Step: 10 ms

9.2.1.42	Measurement ID
The Measurement ID uniquely identifies any measurement per (Node B or Communication) Control Port.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Measurement ID


INTEGER 
(0..2^20-1)


9.2.1.43	Measurement Increase/Decrease Threshold
The Measurement Increase/Decrease Threshold defines the threshold that shall trigger Event C or D.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
CHOICE Measurement Increase/Decrease Threshold
M



–

>Received Total Wide Band Power






>>Received Total Wide Band Power
M

INTEGER (0..620)
Unit: dB
Range: 0..62 dB
Step: 0.1 dB
–

>Transmitted Carrier Power






>>Transmitted Carrier Power
M

INTEGER (0..100)
According to mapping in TS 25.133 [22] and TS 25.123 [23]
–

>Acknowledged PRACH Preambles



FDD only


>>Acknowledged PRACH Preambles
M

INTEGER (0..240,…)
According to mapping in TS 25.133 [22]
–

>UL Timeslot ISCP



TDD only


>>UL Timeslot ISCP
M

INTEGER (0..126)
Unit: dB
Range: 0..63 dB
Step: 0.5 dB
–

>SIR






>>SIR
M

INTEGER (0..62)
Unit: dB
Range: 0..31 dB
Step: 0.5 dB
–

>SIR Error



FDD only


>>SIR Error
M

INTEGER (0..124)
Unit: dB
Range: 0..62 dB
Step: 0.5 dB
–

>Transmitted Code Power






>>Transmitted Code Power
M

INTEGER (0..112,…)
Unit: dB
Range: 0..56 dB
Step: 0.5 dB

–

>RSCP



TDD only


>>RSCP
M

INTEGER (0..126)
Unit: dB
Range: 0..63 dB
Step: 0.5 dB
–

>Round Trip Time



FDD only


>>Round Trip Time
M

INTEGER (0..32766)
Unit: chips
Range: 0 .. 2047.875 chips
Step: 0.625 chips
–

>Not Used 1 


NULL
This choice shall not be used. Reject procedure if received. 


>Not Used 2 


NULL
This choice shall not be used. Reject procedure if received. 


>Additional Measurement Thresholds



See Note 1.


>>Transmitted Carrier Power Of All Codes Not Used For HSTransmission






>>>Transmitted Carrier Power Of All Codes Not Used For HSTransmission
M

INTEGER (0..100)
According to mapping in TS 25.133 [22], measurement "Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICHTransmission" and mapping in TS 25.123 [23], measurement "Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH Or HS-SCCH Transmission"
YES
reject
>>Transmitted Carrier Power For Cell Portion



FDD and 1.28Mcps TDD only


>>>Transmitted Carrier Power For Cell Portion
M

INTEGER (0..100)
Mapping identical to the one for  Transmitted Carrier Power measurement in TS 25.133 [22] and TS 25.123 [23]
YES
reject
>>Received Total Wide Band Power For Cell Portion



FDD and 1.28Mcps TDD only


>>>Received Total Wide Band Power For Cell Portion
M

INTEGER (0..620)
Unit: dB
Range: 0..62 dB
Step: 0.1 dB
YES
reject
>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH Transmission For Cell Portion



FDD only


>>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH Transmission For Cell Portion
M

INTEGER (0..100)
Mapping identical to the one for  Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH Transmission measurement in TS 25.133 [22]
YES
reject
>>UpPCH interference



1.28Mcps TDD Only


>>>UpPCH interference Value
M

INTEGER (0..127,…)
According to mapping in TS 25.123 [23]
YES
reject
>>Received Scheduled E-DCH Power Share



FDD only


>>>RSEPS value
M

INTEGER 
(0..151)
According to mapping in TS 25.133 [22]
YES
reject
>>Received Scheduled E-DCH Power Share For Cell Portion



FDD only


>>>RSEPS value
M

INTEGER 
(0..151)
According to mapping in TS 25.133 [22]
YES
reject
>>E-DCH RACH Report



FDD only


>>> Denied E-DCH RACH Resources
M

INTEGER (0..240,…)
According to mapping in TS 25.302 [25]
YES
reject
>>>2ms Overridden E-DCH RACH Resources
O

INTEGER (0..240,…)
According to mapping in TS 25.302 [25].
YES
ignore
>>>2ms Denied E-DCH RACH Resources
O

INTEGER (0..240,…)
According to mapping in TS 25.302 [25].
YES
ignore
>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission For Cell Portion



1.28Mcps TDD only


>>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission For Cell Portion
M

INTEGER (0..100)
Mapping identical to the one for  Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission measurement in TS 25.123 [23]
YES
reject
>> UL Timeslot ISCP For Cell Portion



1.28Mcps TDD only


>>>UL Timeslot ISCP for Cell Portion
M

INTEGER (0..126)
Unit: dB
Range: 0..63 dB
Step: 0.5 dB
YES
reject
>> UpPCH interference For Cell Portion



1.28Mcps TDD Only


>>>UpPCH interference Value for Cell Portion
M

INTEGER (0..127,…)
According to mapping in TS 25.123 [23]
YES
reject
Note 1:	This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1.

9.2.1.43A	Measurement Recovery Behavior
This IE controls the Measurement Recovery Behavior.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Measurement Recovery Behavior


NULL


9.2.1.43B	Measurement Recovery Reporting Indicator
This IE indicates the Measurement Recovery Reporting.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Measurement Recovery Reporting Indicator


NULL


9.2.1.43C	Measurement Recovery Support Indicator
This IE indicates the Measurement Recovery Support.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Measurement Recovery Support Indicator


NULL


9.2.1.44	Measurement Threshold
The Measurement Threshold defines which threshold that shall trigger Event A, B, E, F or On Modification.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
CHOICE Measurement Threshold
M



–

>Received Total Wide Band Power






>>Received Total Wide Band Power
M

INTEGER (0..621)
According to mapping in TS 25.133 [22] and TS 25.123 [23]
–

>Transmitted Carrier Power






>>Transmitted Carrier Power
M

INTEGER (0..100)
According to mapping in TS 25.133 [22] and TS 25.123 [23]
–

>Acknowledged PRACH Preambles



FDD only


>>Acknowledged PRACH Preambles
M

INTEGER (0..240,…)
According to mapping in TS 25.133 [22]
–

>UL Timeslot ISCP



TDD only


>>UL Timeslot ISCP
M

INTEGER (0..127)
According to mapping in TS 25.123 [23]
–

>SIR






>>SIR
M

INTEGER (0..63)
According to mapping in TS 25.133 [22] and TS 25.123 [23]
–

>SIR Error



FDD only


>>SIR Error
M

INTEGER (0..125)
According to mapping in TS 25.133 [22]
–

>Transmitted Code Power






>>Transmitted Code Power
M

INTEGER (0..127)
According to mapping in TS 25.133 [22] and TS 25.123 [23]
–

>RSCP



TDD only


>>RSCP
M

INTEGER (0..127)
According to mapping in TS 25.123 [23]
–

>Rx Timing Deviation



Applicable to 3.84Mcps TDD only


>>Rx Timing Deviation
M

INTEGER (0..8191)
According to mapping in TS 25.123 [23]
–

>Round Trip Time



FDD only


>>Round Trip Time
M

INTEGER (0..32767)
According to mapping in TS 25.133 [22]
–

>Not Used 1 


NULL
This choice shall not be used. Reject procedure if received. 


>Not Used 2 


NULL
This choice shall not be used. Reject procedure if received. 


>Additional Measurement Thresholds



See Note 1.


>>UTRAN GPS Timing Of Cell Frames For UE Positioning




–

>>>TUTRAN-GPS Measurement Threshold Information
M

9.2.1.64B

YES
reject
>>SFN-SFN Observed Time Difference 






>>>SFN-SFN Measurement Threshold Information
M

9.2.1.53C

YES
reject
>>Rx Timing Deviation LCR



Applicable to 1.28Mcps TDD Only


>>>Rx Timing Deviation LCR
M

INTEGER (0..511)
According to mapping in TS 25.123 [23]
YES 
reject
>>HS-SICH Reception Quality



Applicable to TDD Only


>>>HS-SICH Reception Quality
M

INTEGER (0..20)
According to mapping in TS 25.123 [23]
YES 
reject
>>Transmitted Carrier Power Of All Codes Not Used For HSTransmission






>>>Transmitted Carrier Power Of All Codes Not Used For HSTransmission
M

INTEGER (0..100)
According to mapping in TS 25.133 [22], measurement "Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICHTransmission" and TS 25.123 [23], measurement "Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH Or HS-SCCH Transmission"
YES
reject
>>HS-DSCH Required Power






>>>HS-DSCH Required Power Value
M

9.2.1.31Iba

YES
reject
>>Transmitted Carrier Power For Cell Portion



FDD and 1.28Mcps TDD only


>>>Transmitted Carrier Power For Cell Portion
M

INTEGER (0..100)
Mapping identical to the one for  Transmitted Carrier Power measurement in TS 25.133 [22] and TS 25.123 [23]
YES
reject
>>Received Total Wide Band Power For Cell Portion



FDD and 1.28Mcps TDD only


>>>Received Total Wide Band Power For Cell Portion
M

INTEGER (0..621)
Mapping identical to the one for  Received Total Wide Band Power measurement in TS 25.133 [22] and TS 25.123 [23]
YES
reject
>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH Transmission For Cell Portion



FDD only


>>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH Transmission Value For Cell Portion
M

INTEGER (0..100)
Mapping identical to the one for  Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH Transmission measurement in TS 25.133 [22]
YES
reject
>>UpPCH interference



1.28Mcps TDD Only


>>>UpPCH interference Value
M

INTEGER (0..127,…)
According to mapping in TS 25.123 [23]
YES
reject
>>DL Transmission Branch Load



FDD Only


>>>DL Transmission Branch Load Value
M

INTEGER (0..101,…)
According to mapping in TS 25.133 [22]
YES
reject
>>HS-DSCH Required Power For Cell Portion



FDD and 1.28Mcps TDD only


>>>HS-DSCH Required Power Value For Cell Portion
M

HS-DSCH Required Power Value 9.2.1.31Iba

YES
reject
>>E-DCH Non-serving Relative Grant Down Commands



FDD only


>>>E-DCH Non-serving Relative Grant Down Commands Value
M

INTEGER (0..100,…)
Down Commands per second
YES
reject
>>Rx Timing Deviation 768



Applicable to 7.68Mcps TDD Only


>>>Rx Timing Deviation 768
M

INTEGER (0..65535)
According to mapping in TS 25.123 [23]
YES 
reject
>>Rx Timing Deviation 384 Extended



Applicable to 3.84Mcps TDD Only


>>>Rx Timing Deviation 384 Extended
M

INTEGER (0..32767)
According to mapping in TS 25.123 [23]
YES 
reject
>>Extended Round Trip Time



FDD only


>>>Extended Round Trip Time Value
M

INTEGER (32767..103041)
Continuation of intervals with step size as defined in TS 25.133 [22].
YES
reject
>>Received Scheduled E-DCH Power Share



FDD only


>>>RSEPS value
M

INTEGER (0..151)
According to mapping in TS 25.133 [22]
YES
reject
>>Received Scheduled E-DCH Power Share for Cell Portion



FDD only


>>>RSEPS value
M

INTEGER (0..151)
According to mapping in TS 25.133 [22]
YES
reject
>>Additional HS-SICH Reception Quality



Applicable to 1.28Mcps TDD Only 


>>>HS-SICH Reception Quality LCR
M

INTEGER (0..20)
According to mapping in TS 25.123 [23]
used when the Measurement Threshold Value for HS-SICH Reception Quality are more than 20, Measurement Threshold Value = 20 + IE Value 
YES 
reject
>>UTRAN GANSS Timing Of Cell Frames For UE Positioning






>>>TUTRAN-GANSS Measurement Threshold Information
M

9.2.1.99

YES
reject
>> E-DCH RACH Report



FDD only


>>> Denied E-DCH RACH Resources
M

INTEGER (0..240,…)
According to mapping in TS 25.302 [25]
YES
reject
>>>2ms Overridden E-DCH RACH Resources
O

INTEGER (0..240,…)
According to mapping in TS 25.302 [25]
YES
ignore
>>>2ms Denied E-DCH RACH Resources
O

INTEGER (0..240,…)
According to mapping in TS 25.302 [25]
YES
ignore
>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission For Cell Portion



1.28Mcps TDD only


>>>Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission For Cell Portion
M

INTEGER (0..100)
Mapping identical to the one for  Transmitted Carrier Power Of All Codes Not Used For HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH Transmission measurement in TS 25.123 [23]
YES
reject
>> UL Timeslot ISCP For Cell Portion



1.28Mcps TDD only


>>>UL Timeslot ISCP for Cell Portion
M

INTEGER (0..127)
According to mapping in TS 25.123 [23]
YES
reject
>> UpPCH interference For Cell Portion



1.28Mcps TDD Only


>>>UpPCH interference Value for Cell Portion
M

INTEGER (0..127,…)
According to mapping in TS 25.123 [23]
YES
reject
>>UE transmission power headroom






>>>UE transmission power headroom
M

INTEGER (0..31)
According to mapping in TS 25.133 [22] and TS 25.123 [23].
YES
reject
Note 1:	This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1.

9.2.1.45	Message Discriminator
This field is used to discriminate between Dedicated NBAP and Common NBAP messages.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Message Discriminator


ENUMERATED (
Common, 
Dedicated)


9.2.1.45A	Message Structure
The Message Structure IE gives information for each level with assigned criticality in an hierarchical message structure from top level down to the lowest level above the reported level for the occurred error (reported in the Information Element Criticality Diagnostics IE).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Message Structure

1..<maxNrOfLevels>

The first repetition of the Message Structure IE corresponds to the top level of the message. The last repetition of the Message Structure IE corresponds to the level above the reported level for the occurred error of the message.
>IE ID
M

INTEGER (0..65535)
The IE ID of this level’s IE containing the not understood or missing IE.
>Repetition Number
O

INTEGER (1..256)
The Repetition Number IE gives, if applicable, the number of occurrences of this level’s reported IE up to and including the occurrence containing the not understood or missing IE. 

Note: All the counted occurrences of the reported IE must have the same topdown hierarchical message structure of IEs with assigned criticality above them.

Range Bound
Explanation
maxNrOfLevels
Maximum number of message levels to report. The value for maxNrOfLevels is 256.

9.2.1.46	Message Type
The Message Type uniquely identifies the message being sent.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Procedure ID
M
1


>Procedure Code
M

INTEGER (0..255)

>Ddmode
M

ENUMERATED (
TDD, 
FDD,
Common, 
…)
Common = common to FDD and TDD.
Type of Message
M

ENUMERATED (
Initiating Message, 
Successful Outcome, 
Unsuccessful Outcome, 
Outcome)


9.2.1.46a	MICH CFN
The MICH CFN indicates the Connection Frame Number for the MICH. It corresponds to the Cell SFN of the frame in which the start of the S-CCPCH frame is located, see ref TS 25.211 [7].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MICH CFN


INTEGER (0..4095)


9.2.1.46A	Minimum DL Power Capability
This parameter indicates the minimum DL power capability for a local cell within the Node B. The reference point is the antenna connector. If Transmit Diversity can be used in the local cell, the parameter indicates the minimum for the linear sum of the power that can be used on all branches.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Minimum DL Power Capability 


INTEGER (0..800)
Unit: dBm
Range: -30 .. +50 dBm
Step: 0.1 dB

9.2.1.47	Minimum Spreading Factor
This parameter indicates the minimum spreading factor supported at a cell within the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Minimum Spreading Factor


ENUMERATED 
(4, 8, 16, 32, 64, 128, 256, 512)
[TDD - Mapping scheme for  the minimum spreading factor 1 and 2:
“256” means 1
“512” means 2]

9.2.1.47a	Modification Period
The Modification Period of the MICH, see ref. TS 25.331 [18].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Modification Period


ENUMERATED
(1280, 2560, 5120, 10240,…)
Unit: ms

9.2.1.47A	N_INSYNC_IND
This parameter is used by the Node B for achievement/re-achievement of UL synchronisation on the Uu interface as defined in ref. TS 25.214 [10] and TS 25.224 [21].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
N_INSYNC_IND


INTEGER (1..256)


9.2.1.47B	N_OUTSYNC_IND
This parameter defines the number of consecutive out-of-sync indications after which the timer T_RLFAILURE shall be started (see also ref. TS 25.214 [10] and TS 25.224 [21]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
N_OUTSYNC_IND


INTEGER (1..256)


9.2.1.47C	Neighbouring FDD Cell Measurement Information
This IE provides information on the FDD neighbouring cells used for the purpose of measurements.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UC-Id
M

9.2.1.65B

UARFCN
M

9.2.1.65
Corresponds to Nd (TS 25.104 [14])
Primary Scrambling Code
M

9.2.2.34


9.2.1.47D	Neighbouring TDD Cell Measurement Information
This IE provides information on the 3.84Mcps TDD neighbouring cells used for the purpose of measurements. Since the measurement can be performed on every time slot and midamble shift, the Time Slot IE and Midamble Shift And Burst Type IE shall be included if available.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UC-Id
M

9.2.1.65B

UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Cell Parameter ID
M

9.2.3.4

Time Slot
O

9.2.3.23

Midamble Shift And Burst Type
O

9.2.3.7


9.2.1.47E	Neighbouring TDD Cell Measurement Information LCR
This IE provides information on the neighbouring 1.28Mcps TDD cells used for the purpose of measurements. Since the measurement can be performed on every time slot and midamble shift, the Time Slot LCR IE and Midamble Shift LCR IE shall be included if available.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UC-Id
M

9.2.1.65B

UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Cell Parameter ID
M

9.2.3.4

Time Slot LCR
O

9.2.3.24A

Midamble Shift LCR
O

9.2.3.7A


9.2.1.47F	NI
The NI IE provides a Notification Indicator determined as specified in TS 25.304 [37].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
NI


INTEGER (0..65535)


9.2.1.48	Node B Communication Context ID
The Node B Communication Context ID is the identifier of the Communication Context in the Node B, it corresponds to the dedicated resources which are necessary for an UE using one or more dedicated channels in a given Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Node B Communication Context ID


INTEGER 
(0..2^20-1)
"2^20-1" is a reserved value indicating all the existing and future Node B Communication Contexts that can be reached by the Communication Control Port (All NBCC).

9.2.1.49	Payload CRC Presence Indicator
This parameter indicates whether FP payload 16 bit CRC is used or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Payload CRC Presence Indicator


ENUMERATED (
CRC Included, 
CRC Not Included,
…)


9.2.1.49A	PICH Power
The PICH Power IE indicates a power level relative to the [FDD - Primary CPICH power] [TDD - Primary CCPCH power] configured in a cell. If Transmit Diversity is applied to the PICH (resp. the MICH), the PICH Power IE indicates the power offset between the linear sum of the power for the PICH (resp. the MICH) on all branches and the [FDD - Primary CPICH power] [TDD - Primary CCPCH power] configured in a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
PICH Power


INTEGER (-10..+5)
Unit: dB
Range: -10 .. +5 dB
Step: 1dB

9.2.1.49B	Power Local Cell Group ID
The Power Local Cell Group ID represents resources in the Node B which have been pooled from a DL power capability point of view.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Power Local Cell Group ID


Local Cell ID
9.2.1.38


9.2.1.49C	Priority Queue ID
The Priority Queue ID provides the identity of the Priority Queue. The Priority Queue ID is unique across all MAC-d flows that are currently allocated for one Node B Communication Context or across all Common MAC flows [FDD - within a cell][1.28Mcps TDD - within a carrier].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Priority Queue ID


INTEGER (0..7)


9.2.1.49D	Process Memory Size
The Process Memory Size IE is the size of an HARQ process in the Node B expressed in bits. It provides the maximum number of soft channel bits in the virtual IR buffer (TS 25.212 [8] or TS 25.222 [34]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Process Memory Size


ENUMERATED (
800, 1600, 2400, 3200, 4000, 4800, 5600, 6400, 7200, 8000, 8800, 9600, 10400, 11200, 12000, 12800, 13600, 14400, 15200, 16000, 17600, 19200, 20800, 22400, 24000, 25600, 27200, 28800, 30400, 32000, 36000, 40000, 44000, 48000, 52000, 56000, 60000, 64000, 68000, 72000, 76000, 80000, 88000, 96000, 104000, 112000, 120000, 128000, 136000, 144000, 152000, 160000, 176000, 192000, 208000, 224000, 240000, 256000, 272000, 288000, 304000,…)


9.2.1.50	Puncture Limit
The Puncture Limit limits the amount of puncturing that can be applied in order to minimise the number of dedicated physical channels.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Puncture Limit


INTEGER (0..15)
Unit: %
Range: 40..100 %
Step: 4 %
100% means no puncturing
[FDD - Value "0" is not applicable for E-DPCH.]

9.2.1.50A	QE-Selector
The QE-Selector indicates from which source the value for the quality estimate (QE) shall be taken.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
QE-Selector


ENUMERATED (
Selected, 
Non-Selected)


9.2.1.51	Report Characteristics
The report characteristics define how the reporting shall be performed.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
CHOICE Report Characteristics
M



–

>On Demand


NULL



>Periodic






>>Report Periodicity
M

9.2.1.51a
The frequency with which the Node B shall send measurement reports.
–

>Event A






>>Measurement Threshold
M

9.2.1.44
The threshold for which the Node B shall trigger a measurement report.
–

>>Measurement Hysteresis Time
O

9.2.1.41A

–

>Event B






>>Measurement Threshold
M

9.2.1.44
The threshold for which the Node B shall trigger a measurement report.
–

>>Measurement Hysteresis Time
O

9.2.1.41A

–

>Event C






>>Measurement Increase/Decrease Threshold
M

9.2.1.43

–

>>Measurement Change Time
M

9.2.1.40B
The time the measurement entity shall rise on (in ms), in order to trigger a measurement report.
–

>Event D






>>Measurement Increase/Decrease Threshold
M

9.2.1.43

–

>>Measurement Change Time
M

9.2.1.40B
The time the measurement entity shall fall (in ms), in order to trigger a measurement report.
–

>Event E






>>Measurement Threshold 1
M

Measurement Threshold
9.2.1.44

–

>>Measurement Threshold 2
O

Measurement Threshold
9.2.1.44

–

>>Measurement Hysteresis Time 
O

9.2.1.41A

–

>>Report Periodicity
O

9.2.1.51a
The frequency with which the Node B shall send measurement reports.
–

>Event F






>>Measurement Threshold 1
M

Measurement Threshold
9.2.1.44

–

>>Measurement Threshold 2
O

Measurement Threshold
9.2.1.44

–

>>Measurement Hysteresis Time 
O

9.2.1.41A

–

>>Report Periodicity
O

9.2.1.51a
The frequency with which the Node B shall send measurement reports.
–

>Additional Report Characteristics



See Note 1


>>On Modification






>>>On Modification

1


YES
reject
>>>>Measurement Threshold
M

9.2.1.44
The IE shall be ignored if the Dedicated Measurement Type is set to "Best Cell Portions LCR"
–

Note 1:	This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1.

9.2.1.51a	Report Periodicity
The Report Periodicity defines the frequency at which the Node B shall send measurement reports.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Report Periodicity Scale
M



>millisecond




>>Report Periodicity Value
M

INTEGER (1..6000,…)
Unit: ms
Range: 10..60000 ms
Step: 10 ms
>minute




>>Report Periodicity Value
M

INTEGER (1..60,…)
Unit: min
Range: 1..60 min
Step: 1 min

9.2.1.51A	Requested Data Value
The Requested Data Value IE contains the relevant data concerning the ongoing information exchange. The Requested Data Value IE shall include at least one of the following IE.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
DGPS Corrections
O

9.2.1.24B

–

GPS Navigation Model & Time Recovery
O

9.2.1.31B

–

GPS Ionospheric Model
O

9.2.1.31C

–

GPS UTC Model
O

9.2.1.31D

–

GPS Almanac
O

9.2.1.31F

–

GPS Real-Time Integrity
O

9.2.1.31E

–

GPS RX Pos
O

9.2.1.31G

–

GANSS Common Data

0..1


YES
ignore
>GANSS Ionospheric Model
O

9.2.1.91

–

>GANSS RX Pos
O

9.2.1.95

–

>GANSS Additional Ionospheric Model
O

9.2.1.91a

YES
ignore
>GANSS Earth Orientation Parameters
O

9.2.1.107a

YES
ignore
GANSS Generic Data

0..<maxNoGANSS>


GLOBAL
ignore
>GANSS ID
O

9.2.1.104

–

>DGANSS Corrections
O

9.2.1.88

–

>GANSS Navigation Model And Time Recovery
O

9.2.1.105

–

>GANSS Time Model
O

9.2.1.96

–

>GANSS UTC Model
O

9.2.1.97

–

>GANSS Almanac
O

9.2.1.89

–

>GANSS Real Time Integrity
O

9.2.1.94

–

>GANSS Data Bit Assistance
O

9.2.1.103

–

>GANSS Additional Time Models
O

9.2.1.96a

YES
ignore
>GANSS Additional Navigation Models And Time Recovery
O

9.2.1.105a

YES
ignore
>GANSS Additional UTC Models
O

9.2.1.97a

YES
ignore
>GANSS Auxiliary Information
O

9.2.1.107c

YES
ignore
>SBAS ID
C-GANSS-ID

9.2.1.107b

YES
ignore
>DBDS Corrections
O

9.2.1.127

YES
ignore
>BDS Ionospheric Grid Model
O

9.2.1.128

YES
ignore

Condition
Explanation
GANSS-ID
This IE shall be present if the GANSS ID IE indicates “SBAS”.

Range Bound
Explanation
maxNoGANSS
Maximum number of GANSS Systems

9.2.1.51B	Requested Data Value Information
The Requested Data Value Information IE provides information on whether or not the Requested Data Value is available in the message and also the Requested Data Value itself if available. In case of "Periodic" and "On Modification" reporting, "Information Not Available" shall be used when at least one part of the requested information was not available at the moment of initiating the Information Reporting procedure.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Information Availability Indicator
M



>Information Available




>>Requested Data Value
M

9.2.1.51A

>Information Not Available


NULL


9.2.1.52	Resource Operational State
The Resource Operational State is used to indicate the current operational state of the associated resource following a Node B failure.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Resource Operational State


ENUMERATED (
Enabled, 
Disabled)
When a resource is marked as disabled, then its child resources are implicitly disabled. Cell Resource hierarchy can be referred to TS 25.430 [6].

9.2.1.52A	Retention Priority
Void.
9.2.1.52B	RLC Mode
The RLC Mode IE indicates the RLC Mode used for a Priority Queue.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
RLC Mode


ENUMERATED (
RLC-AM, RLC-UM,…)


9.2.1.53	RL ID
The RL ID is the unique identifier for one RL associated with a UE.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
RL ID


INTEGER (0..31)


9.2.1.53a	RNC-Id
This is the identifier of one RNC in UTRAN.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
RNC-Id


INTEGER (0..4095)


9.2.1.53b	RTWP* Reporting Indicator
The RTWP* Reporting Indicator indicates if the RTWP* measurement value shall be included together with the reported RSEPS measurement value.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
RTWP* Indicator


ENUMERATED (
RTWP* Reporting Required)


9.2.1.53c	RTWP* for Cell Portion Reporting Indicator
The RTWP* for Cell Portion Reporting Indicator indicates if the RTWP* for Cell Portion measurement value shall be included together with the reported RSEPS measurement value.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
RTWP* per Cell Portion Indicator


ENUMERATED (
RTWP* for Cell Portion Reporting Required)


9.2.1.53A	SFN
System Frame Number of the cell, see ref. TS 25.402 [17].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SFN 


INTEGER (0..4095)


9.2.1.53B	Segment Type
Segment type as defined in TS 25.331 [18].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Segment Type 


ENUMERATED (
First segment, 
First segment short,
Subsequent segment,
Last segment, 
Last segment short, 
Complete SIB, 
Complete SIB short,
…)


9.2.1.53C	SFN-SFN Measurement Threshold Information
The SFN-SFN Measurement Threshold Information defines the related thresholds SFN-SFN Observed Time Difference measurements which shall trigger the Event On Modification.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SFN-SFN Change Limit
O

INTEGER(1..256)
Change of SFN-SFN value compared to previously reported value, which shall trigger a new report.
Unit: chip
Step: 1/16 chip
Predicted SFN-SFN Deviation Limit
O

INTEGER(1..256)
Deviation of the predicated SFN-SFN from the latest measurement result, which shall trigger a new report.
Unit: chip
Step: 1/16 chip

9.2.1.53D	SFN-SFN Measurement Time Stamp
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Mode
M



>FDD




>>SFN
M

9.2.1.53A
Indicates the SFN of the reference cell at which the measurement has been performed.
>TDD




>>SFN
M

9.2.1.53A
Indicates the SFN of the reference cell at which the measurement has been performed.
>>Time Slot
M

9.2.3.23
Indicates the Time Slot of the reference cell at which this measurement has been performed.

9.2.1.53E	SFN-SFN Measurement Value Information
The SFN-SFN Measurement Value Information IE indicates the measurement result related to SFN-SFN Observed Time Difference measurements.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information

1..<maxNrOfMeasNCell>


>UC-Id
M

9.2.1.65B

>SFN-SFN Value
M

9.2.1.53F

>SFN-SFN Quality
O

INTEGER (0..255)
Indicates the standard deviation (std) of the SFN-SFN Observed Time Difference measurements in 1/16 chip. SFN-SFN Quality = /E[(x-µ)2] = std of reported SFN-SFN Value, where x is the reported SFN-SFN Value and µ = E[x] is the expectation value of x.
>SFN-SFN Drift Rate
M

INTEGER 
(-100..+100)
Indicates the SFN-SFN drift rate in 1/256 chip per second.
A positive value indicates that the Reference cell clock is running at a greater frequency than the measured neighbouring cell.
>SFN-SFN Drift Rate Quality
O

INTEGER (0..100)
Indicates the standard deviation (std) of the SFN-SFN drift rate measurements in 1/256 chip per second. SFN-SFN Drift Rate Quality = /E[(x-µ)2] = std of reported SFN-SFN Drift Rate, where x is the reported SFN-SFN Drift Rate and µ = E[x] is the expectation value of x.
>SFN-SFN Measurement Time Stamp
M

9.2.1.53D

Unsuccessful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information

0..<maxNrOfMeasNCell-1>


>UC-Id
M

9.2.1.65B


Range Bound
Explanation
maxNrOfMeasNCell
Maximum number of neighbouring cells that can be measured on

9.2.1.53F	SFN-SFN Value
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Mode
M



>FDD




>>SFN-SFN
M

INTEGER (0..614399)
According to mapping in TS 25.133 [22].
>TDD



1.28 Mcps and 3.84 Mcps only
>>SFN-SFN
M

INTEGER (0..40961)
According to mapping in TS 25.123 [23].
>TDD 7.68 Mcps




>>SFN-SFN
M

INTEGER (0..81923)
According to mapping in TS 25.123 [23].

9.2.1.53G	RL Specific DCH Information
The RL Specific DCH Information IE provides RL specific DCH Information for DCHs. In the case of a set of co-ordinated DCHs requiring a new transport bearer on Iub, the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE shall be included only for one of the DCHs in the set of co-ordinated DCHs.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
RL Specific DCH Information

1..<maxNrOfDCHs>


–

>DCH ID
M

9.2.1.20

–

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
–

>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
–

>Transport Bearer Not Requested Indicator
O

9.2.2.4G
FDD Only
YES
ignore

Range Bound
Explanation
maxNrOfDCHs
Maximum number of DCHs for one UE

9.2.1.53H	Scheduling Priority Indicator
Indicates the relative priority of the HS-DSCH [FDD - or E-DCH data frame]. Used by the Node B when scheduling HS-DSCH[FDD - or E-DCH].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Scheduling Priority Indicator


INTEGER (0..15)
Relative priority of the HS-DSCH [FDD - or E-DCH data frame]:
"0" =Lowest Priority
…
"15" =Highest Priority

9.2.1.53I	SID
The SID IE provides the identity of the Size Index.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SID


INTEGER (0..7)


9.2.1.54	SIB Deletion Indicator
Void.
9.2.1.55	SIB Originator 
Indicates if the Node B shall fill in the SIB information or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SIB Originator


ENUMERATED (
Node B, 
CRNC,
…)


9.2.1.55A	Signalling Bearer Request Indicator
The Signalling Bearer Request Indicator IE indicates if a new signalling bearer needs to be established for the control of Node B Communication Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Signalling Bearer Request Indicator


ENUMERATED (Bearer Requested)


9.2.1.56	Shutdown Timer
The shutdown timer shall indicate the length of time available to the CRNC to perform the block of a resource when a Normal priority block is requested.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Shutdown Timer


INTEGER (1..3600)
Unit: second

9.2.1.56a	T1
The T1 IE is used as described in ref TS 25.321 [32] subclause 11.6.2.3.
IE/Group Name
Presence
Range
IE type and reference
Semantics description
T1


ENUMERATED (10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 120, 140, 160, 200, 300, 400, …)
Unit: ms
Node B may use this value to stop the re-transmission of the corresponding MAC-hs PDU.

9.2.1.56A	T_RLFAILURE
The Radio Link Failure procedure shall be triggered after a period of time T_RLFAILURE has elapsed with a persisting out-of-sync indication (see also ref. TS 25.214 [10] and TS 25.224 [21]).
Information Element/Group Name
Presence
Range
IE Type and Reference
Semantics Description
T_RLFAILURE


INTEGER (0..255)
Unit: second
Range: 0 .. 25.5 s
Step: 0.1 s

9.2.1.56B	Start Of Audit Sequence Indicator
Indicates if the AUDIT REQUEST message initiates a new audit sequence or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Start Of Audit Sequence Indicator


ENUMERATED (
Start Of Audit Sequence, 
Not Start Of Audit Sequence)


9.2.1.56C	TFCI2 Bearer Request Indicator
Void.
9.2.1.57	TFCI Presence
The TFCI Presence parameter indicates whether the TFCI shall be included. [TDD - If it is present in the timeslot, it will be mapped to the channelisation code defined by TS 25.221 [19].]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TFCI presence


ENUMERATED (
Present, 
Not Present)


9.2.1.58	TFCS (Transport Format Combination Set)
The Transport Format Combination Set is defined as a set of Transport Format Combinations on a Coded Composite Transport Channel. It is the allowed Transport Format Combinations of the corresponding Transport Channels. The DL Transport Format Combination Set is applicable for DL Transport Channels.

IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
CHOICE TFCS Values
M



-

>Always Used



This choice is always made.
-

>>TFCS

1..<maxNrOfTFCs>

The first instance of the parameter corresponds to TFCI zero, the second to 1 and so on.
[TDD - The first entry (for TFCI 0) should be ignored by the receiver.]
-

>>>CTFC
M

9.2.1.18A

-

>>>CHOICE Gain Factors
C-PhysChan



-

>>>>Signalled Gain Factors




-

>>>>>CHOICE Mode
M



-

>>>>>>FDD




-

>>>>>>>Gain Factor >C
M

INTEGER (0..15)
For UL DPCCH or control part of PRACH; mapping in accordance to TS 25.213 [9]
-

>>>>>>>Gain Factor >D
M

INTEGER (0..15)
For UL DPDCH or data part of PRACH: mapping in accordance to TS 25.213 [9]
-

>>>>>>TDD




-

>>>>>>>Gain Factor >
M

iNTEGER (0..15)
For UL DPCH in TDD; mapping in accordance to TS 25.223 [20].
-

>>>>>Reference TFC nr
O

INTEGER (0..3)
If this TFC is a reference TFC, this IE indicates the reference number.
-

>>>>Computed Gain Factors




-

>>>>>Reference TFC nr
M

INTEGER (0..3)
Indicates the reference TFC to be used to calculate the gain factors for this TFC.
-

>>>Gain Factors 10ms Mode
O

9.2.2.199
For UL DPCCH in FDD, and applicable to 10ms Transmission mode [8].
YES
reject
>Not Used



This choice shall never be made  by the CRNC and the Node B shall consider the procedure as failed if it is received.
-


Condition
Explanation
PhysChan
The IE shall be present if the TFCS concerns a UL DPCH or PRACH channel .

Range Bound
Explanation
maxNrOfTFCs
The maximum number of Transport Format Combinations

9.2.1.58A	TNL QoS 
This IE indicates the TNL QoS characteristics of the transport bearer for the uplink data traffic.
When the DS Field IE is used, the value of this IE is configurable by the operator.
When the Generic Traffic Category IE is used, generic traffic categories are implementation-specific (e.g. they may be determined by the sender from the application parameters). The value assigned to each of these categories and sent in the Generic Traffic Category IE is configurable by the operator, as well as the mapping of this value to DS field (IETF RFC 2474 [35]) at the Node B side.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE TNL QoS type
M



>DS Field




>>DS Field
M

BIT STRING (SIZE((8))
DS Field as defined in IETF RFC 2474 [35].
Typically used when the Node B and its CRNC are in the same DS domain as defined in IETF RFC 2475 [36].
>Generic Traffic Category




>>Generic Traffic Category
M

BIT STRING (SIZE(8))


9.2.1.59	Transport Format Set
The Transport Format Set is defined as the set of Transport Formats associated to a Transport Channel, e.g. DCH.
[TDD - The Transport Format Set for each transport channel within the same CCTrCH shall have the same value for the 2nd Interleaving Mode IE.]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Dynamic Transport Format Information

1..<maxNrOfTFs>

The first instance of the parameter corresponds to TFI zero, the second to 1 and so on.
>Number of Transport Blocks
M

INTEGER (0..512)

>Transport Block Size
C-Blocks

INTEGER (0..5000)
Unit: Bits
>CHOICE Mode 
M



>>TDD




>>>Transmission Time Interval Information
C-TTIdynamic
1..<maxTTI-count>


>>>>Transmission Time Interval
M

ENUMERATED 
(10, 20, 40, 80,…)
Unit: ms
Semi-Static Transport Format Information

1


>Transmission Time Interval
M

ENUMERATED
(10, 20, 40, 80, dynamic,…,5)
Unit: ms;
Value "dynamic” for TDD only;
Value "5” for LCR TDD only;
For FDD DCH, the value "80" is applicable only when DL DPCH Slot Format IE indicates a slot format with SF=512.
>Type Of Channel Coding
M

ENUMERATED (
No codingTDD, Convolutional, Turbo,
…)
[FDD - The value "No codingTDD" shall be treated as logical error if received]
>Coding Rate
C-Coding

ENUMERATED
(1/2, 1/3,…)

>Rate Matching Attribute
M

INTEGER (1..maxRM)

>CRC Size
M

ENUMERATED
(0, 8, 12, 16, 24,…)

>CHOICE Mode
M



>>TDD




>>>2nd Interleaving Mode
M

ENUMERATED (
Frame related, Timeslot related,
…)


Condition
Explanation
Blocks
The IE shall be present if the Number Of Transport Blocks IE is set to a value greater than 0.
Coding
The IE shall be present if the Type Of Channel Coding IE is set to "Convolutional" or "Turbo".
TTIdynamic
The IE shall be present if the Transmission Time Interval IE in the Semi-Static Transport Format Information IE is set to "dynamic”.

Range Bound
Explanation
maxNrOfTFs
Maximum number of different Transport Formats that can be included in the Transport Format Set for one transport channel
maxRM
Maximum number that could be set as rate matching attribute for a transport channel
maxTTI-count
The amount of different TTIs that are possible for that Transport Format

9.2.1.60	ToAWE
TOAWE is the window endpoint. DL data frames are expected to be received before this window endpoint. TOAWE is defined with a positive value relative Latest Time of Arrival (LTOA). A data frame arriving after TOAWE gives a Timing Adjustment Control frame response.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
ToAWE


INTEGER (0..2559)
Unit: ms

9.2.1.61	ToAWS
TOAWS is the window startpoint. DL data frames are expected to be received after this window startpoint. TOAWS is defined with a positive value relative Time of Arrival Window Endpoint (TOAWE). A data frame arriving before TOAWS gives a Timing Adjustment Control frame response.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
ToAWS


INTEGER (0..1279)
Unit: ms

9.2.1.62	Transaction ID
The transaction ID is used to associate all the messages belonging to the same procedure. Messages belonging to the same procedure shall use the same transaction ID.
The transaction ID is determined by the initiating peer of a procedure. For common procedures the transaction ID shall uniquely identify a procedure within all ongoing parallel procedures initiated by one protocol peer, using the same procedure code and signalled over the same Node B Control Port. For dedicated procedures the transaction ID shall uniquely identify a procedure within all ongoing parallel procedures initiated by one protocol peer, using the same procedure code and initiated towards the same Node B/CRNC context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Transaction ID Length



The Transaction ID shall be interpreted for its integer value, not for the type of encoding ("short" or "long").
>Short




>>Transaction ID Value
M

INTEGER (0..127)

>Long




>>Transaction ID Value
M

INTEGER (0..32767)


9.2.1.62A	Transport Bearer Request Indicator
Indicates whether a new transport bearer needs to be established for carrying the concerned transport channel.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Transport Bearer Request Indicator


ENUMERATED (
Bearer Requested, Bearer Not Requested, 
…)


9.2.1.63	Transport Layer Address
In case of transport bearer establishment with ALCAP (TS 25.426 [2], TS 25.434 [31]), this IE contains the address to be used for Transport Network Control Plane signalling to establish the transport bearer according to (TS 25.426 [2], TS 25.434 [31]).
In order to allow transport bearer establishment without ALCAP, this IE contains the address of the transport bearer to be used for the user plane transport.
For details on the Transport Address used see ref. (TS 25.426 [2], TS 25.434 [31]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Transport Layer Address


BIT STRING (SIZE(1..160, …))


9.2.1.64	TSTD Indicator
Indicates if TSTD shall be active or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TSTD Indicator


ENUMERATED (
active, 
inactive)


9.2.1.64A	TUTRAN-GPS Measurement Value Information
The TUTRAN-GPS Measurement Value Information IE indicates the measurement results related to the UTRAN GPS Timing of Cell Frames for UE Positioning measurements.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TUTRAN-GPS

1

Indicates the UTRAN GPS Timing of Cell Frames forUE Positioning.
According to mapping in TS 25.133 [22].
Significant values range from 0 to 37158911999999.
>MS
M

INTEGER
(0..16383)
Most Significant Part
>LS
M

INTEGER
(0..4294967295)
Least Significant Part
TUTRAN-GPS Quality
O

INTEGER (0..255)
Indicates the standard deviation (std) of the TUTRAN-GPS measurements in 1/16 chip.
TUTRAN-GPS Quality =  E[(x-µ)2] = std of reported TUTRAN-GPS Value, where x is the reported TUTRAN-GPS Value and µ = E[x] is the expectation value of x.
TUTRAN-GPS Drift Rate
M

INTEGER (-50..+50)
Indicates the TUTRAN-GPS drift rate in 1/256 chip per second.
A positive value indicates that the UTRAN clock is running at a lower frequency than GPS clock.
TUTRAN-GPS Drift Rate Quality
O

INTEGER (0..50)
Indicates the standard deviation (std) of the TUTRAN-GPS drift rate measurements in 1/256 chip per second.
TUTRAN-GPS Drift Rate Quality =  E[(x-µ)2] = std of reported TUTRAN-GPS Drift Rate, where x is the reported TUTRAN-GPS Drift Rate and µ = E[x] is the expectation value of x.

9.2.1.64B	TUTRAN-GPS Measurement Threshold Information
The TUTRAN-GPS Measurement Threshold Information defines the related thresholds for UTRAN GPS Timing of Cell Frames for UE Positioning measurements shall trigger the event On Modification.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TUTRAN-GPS Change Limit
O

INTEGER (1..256)
Change of TUTRAN-GPS value compared to previously reported value, which shall trigger a new report. 
Unit in 1/16 chip.
Predicted TUTRAN-GPS Deviation Limit
O

INTEGER (1..256)
Deviation of the predicated TUTRAN-GPS from the latest measurement result, which shall trigger a new report. 
Unit in 1/16 chip.

9.2.1.64C	TUTRAN-GPS Accuracy Class
The TUTRAN-GPS Accuracy Class IE indicates the accuracy class of the UTRAN GPS Timing of Cell Frames for UE Positioning measurement.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TUTRAN-GPS Accuracy Class


ENUMERATED (
Accuracy Class A, Accuracy Class B, Accuracy Class C, …)
More information about TUTRAN-GPS Measurement Accuracy Class is included in TS 25.133 [22] and TS 25.123 [23].

9.2.1.65	UARFCN
Designates the carrier frequency.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UARFCN


INTEGER (0..16383,…)
As defined in subclause 5.4.3 in TS 25.104 [14] and TS 25.105 [15]

9.2.1.65A	UL Capacity Credit
The capacity credit indicates to the CRNC the Uplink capacity of a Local Cell or a Local Cell Group.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL Capacity Credit


INTEGER (0..65535)


9.2.1.65B	UTRAN Cell Identifier (UC-Id)
The UC-Id (UTRAN Cell identifier) is the identifier of a cell in one UTRAN.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
RNC-Id
M

9.2.1.53a
If the Extended RNC-ID IE is included in the UC-Id IE, the RNC-Id IE shall be ignored.
–
–
C-Id
M

9.2.1.9

–
–
Extended RNC-ID
O

9.2.1.65C
The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095.
YES
reject

9.2.1.65C	Extended RNC-ID
This is the identifier of one RNC in UTRAN.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Extended RNC-ID


INTEGER(4096..65535)
Note: Application of the Extended RNC-ID IE to very large networks is FFS.

9.2.1.66	UL FP Mode
This parameter defines if normal or silent mode of the Frame Protocol shall be used for the UL.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL FP Mode


ENUMERATED (
Normal, 
Silent,
…)


9.2.1.67	UL interference level
Void.
9.2.1.67A	UL SIR
The UL SIR indicates a received UL SIR.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL SIR


INTEGER (-82..173)
Value = UL SIR/10
Unit: dB
Range: -8.2 .. +17.3 dB
Step: 0.1 dB

9.2.1.68	Unidirectional DCH Indicator
The Unidirectional DCH Indicator IE indicates that the DCH is unidirectional. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Unidirectional DCH Indicator


ENUMERATED (Downlink DCH only, Uplink DCH only)


9.2.1.69	E-DCH MAC-d Flow Multiplexing List
The E-DCH MAC-d Flow Multiplexing List indicates which E-DCH MAC-d flows are allowed to be multiplexed within a MAC-e/MAC-i PDU with the MAC-d flow it is associated to. If the E-DCH MAC-d Flow Multiplexing List is signalled for an E-DCH MAC-d flow it indicates that E-DCH MAC-d PDUs of this E-DCH MAC-d flow are the first E-DCH MAC-d PDU in the MAC-e/MAC-i PDU. If an E-DCH MAC-d Flow Multiplexing List was already received within a previous Radio Link related procedure and no E-DCH MAC-d Flow Multiplexing List is signalled for an E-DCH MAC-d flow, the Node B shall continue to use the previously received one. If no E-DCH MAC-d Flow Multiplexing List was ever received for an E-DCH MAC-d flow no restrictions shall be assumed for the related E-DCH MAC-d flow for multiplexing E-DCH MAC-d flows.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH MAC-d Flow Multiplexing List


BIT STRING (SIZE(8))
The first Bit corresponds to E-DCH MAC-d flow 0,
the second bit corresponds to E-DCH MAC-d flow 1,
etc.
For 1.28Mcps TDD, if the IE is included in the Common E-DCH MAC-d Flow Specific Information LCR IE, the first bit corresponds to E-DCH MAC-d flow with the lowest E-DCH MAC-d Flow ID within the same frequency,
the second bit corresponds to E-DCH MAC-d flow with the second lowest E-DCH MAC-d Flow ID within the same frequency,
etc.

9.2.1.70	E-DCH Capability
This parameter defines the E-DCH capability for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH Capability


ENUMERATED (E-DCH Capable, E-DCH non Capable)


9.2.1.71	E-DCH Logical Channel Information
The E-DCH Logical Channel Information IE is used for the establishment of E-DCH Logical Channels.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-DCH Logical Channel Information

1..<maxnooflogicalchannels>


–

>Logical Channel ID
M

9.2.1.80

–

>Scheduling Priority Indicator
M

9.2.1.53H

–

>Scheduling Information
M

9.2.1.84

–

>MAC-es Guaranteed Bit Rate
O

9.2.1.82

–

>E-DCH DDI Value
M

9.2.1.76
If more than 1 MAC-d PDU size is configured for this Logical Channel, the different sizes will use subsequent DDI values starting from this DDI value.
Value “0x3F” is reserved. 
Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.
–

>MAC-d PDU Size List

1..<maxNrOfMACdPDUSize>


–

>>MAC-d PDU Size
M

9.2.1.38A
Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.
–

>Maximum MAC-d PDU Size Extended
O

MAC PDU Size Extended
9.2.1.38C

YES
reject
>MAC-es Maximum Bit Rate LCR
O

9.2.3.90
1.28Mcps TDD only
YES
ignore
>UE Aggregate Maximum Bit Rate Enforcement Indicator
O

NULL

YES
ignore

Range Bound
Explanation
Maxnooflogicalchannels
Maximum number of logical channels
maxNrOfMACdPDUSize
Maximum number of MAC-d PDU size per Logical Channels

9.2.1.72	E-DCH Logical Channel To Modify
The E-DCH Logical Channel To Modify IE is used for the reconfiguration of E-DCH Logical Channels.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-DCH Logical Channel Information

1..<maxnooflogicalchannels>


–

>Logical Channel ID
M

9.2.1.80

–

>Scheduling Priority Indicator
O

9.2.1.53H

–

>Scheduling Information
O

9.2.1.84

–

>MAC-es Guaranteed Bit Rate
O

9.2.1.82

–

>E-DCH DDI Value
O

9.2.1.76
If more than 1 MAC-d PDU size is configured for this Logical Channel, the different sizes will use subsequent DDI values starting from this DDI value.
Value “0x3F” is reserved. 
Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.
–

>MAC-d PDU Size List

0..< maxNrOfMACdPDUSize>


–

>>MAC-d PDU Size
M

9.2.1.38A
Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.
–

>Maximum MAC-d PDU Size Extended
O

MAC PDU Size Extended
9.2.1.38C

YES
reject
>MAC-es Maximum Bit Rate LCR
O

9.2.3.90
1.28Mcps TDD only
YES
ignore

Range Bound
Explanation
maxnooflogicalchannels
Maximum number of logical channels
maxNrOfMACdPDUSize
Maximum number of MAC-d PDU size per Logical Channels

9.2.1.73	E-DCH MAC-d Flows To Delete
The E-DCH MAC-d Flows To Delete IE is used for the removal of E-DCH MAC-d flows.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH MAC-d Flows To Delete

1..<maxNrOfEDCHMACdFlows>


>E-DCH MAC-d Flow ID
M

9.2.1.74


Range Bound
Explanation
maxNrOfEDCHMACdFlows
Maximum number of E-DCH MAC-d flows

9.2.1.74	E-DCH MAC-d Flow ID
The E-DCH MAC-d Flow ID is the unique identifier for one MAC-d flow on E-DCH.
IE/Group Name
 Presence
 Range
 IE Type and Reference
Semantics Description
 E-DCH MAC-d Flow ID
 
 
 INTEGER
 (0..maxNrOfEDCHMACdFlows - 1)
 

Range Bound
Explanation
maxNrOfEDCHMACdFlows
Maximum number of E-DCH MAC-d flows

9.2.1.74A	E-DCH MAC-d PDU Size Capability
This parameter defines the  capability for a Local Cell to support different MAC-d PDU Size formats. If this IE is set to "Flexible Size Capable" the Local Cell  is "Fixed Size Capable" and "Flexible Size Capable". If this IE has not been configured or has been set to "Fixed Size Capable"  the Local Cell is only  "Fixed Size Capable".
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH MAC-d PDU Size Capability  


ENUMERATED (Fixed Size Capable, Flexible Size Capable)


9.2.1.74B	E-DCH MAC-d PDU Size Format
The  E-DCH MAC-d PDU Size Format  IE provides information about the type of MAC-d PDU Size Format that shall be used for the E-DCH in the new configuration. "Fixed MAC-d PDU Size" uses MAC-d PDU sizes defined in MAC-d PDU Size List IE of the E-DCH Logical Channel Information IE. "Flexible MAC-d PDU Size" uses a flexible MAC-d PDU size with a maximum PDU size as defined by Maximum MAC-d PDU Size Extended IE of E-DCH Logical Channel Information IE. The actual MAC-d PDU size is determined as specified in TS 25.435 [24] and TS 25.321 [32].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH MAC-d PDU Size Format 


ENUMERATED (Fixed MAC-d PDU Size, Flexible MAC-d PDU Size)


9.2.1.75	E-RNTI
The E-RNTI is needed for the UE (or UE group) specific CRC in E-AGCH, see ref. TS 25.319 [38].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-RNTI


INTEGER
(0..65535)


9.2.1.76	E-DCH DDI Value
The E-DCH DDI Value is the Data Description Indicator value identifying a unique combination of E-DCH MAC-d Flow ID and MAC-d PDU Size.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH DDI Value


INTEGER
(0..62)


9.2.1.77	E-DCH Provided Bit Rate Value
The E-DCH Provided Bit Rate Value IE indicates the E-DCH Provided Bit Rate as defined in TS 25.321 [32].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH Provided Bit Rate Value


INTEGER 
(0..2^24-1, …, 2^24..256,000,000)
Expressed in bit/s.

9.2.1.78	E-DCH Provided Bit Rate Value Information
The E-DCH Provided Bit Rate Value Information IE reports the E-DCH Provided Bit Rate Value IE for each priority class.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH Provided Bit Rate Value Information

1..<maxNrOfPriorityClasses>


>Scheduling Priority Indicator
M

9.2.1.53H

>E-DCH Provided Bit Rate Value
M

9.2.1.77


Range Bound
Explanation
maxNrOfPriorityClasses
Maximum number of E-DCH Scheduling Priorities

9.2.1.79	E-DCH Processing Overload Level
The E-DCH Processing Overload Level IE defines the threshold that determines when the Node B shall indicate processing issue problems to the RNC.  
IE/Group Name
Presence
Range
IE type and reference
Semantics description
E-DCH Processing Overload Level


INTEGER (0..10,…)
Number of consecutive TTIs.
The value ‘0’ is a special value that means infinity, i.e. when this value is used, the Node B shall never indicate processing issue to the RNC. 

9.2.1.80	Logical channel ID
The Logical Channel ID IE is used to identify a E-DCH logical channel in Sheduling Information that is sent over Uu. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Logical Channel ID


INTEGER (1..15)


9.2.1.81	Maximum Number Of Retransmissions For E-DCH
The Maximum Number Of Retransmissions For E-DCH IE specifies the upper boundary for retransmissions for a single MAC-d flow.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Maximum Number Of Retransmissions For E-DCH


INTEGER
(0..15)


9.2.1.82	MAC-es Guaranteed Bit Rate
The MAC-es Guaranteed Bit Rate IE indicates the guaranteed number of bits per second to be delivered over the air interface under normal operating conditions (provided there is data to deliver) for which the Node B shall provide sufficient UL resources. If the MAC-es Guaranteed Bit Rate IE is received with the value set to 0 during RL set up or modification, no guarantee is applied.
IE/Group Name
Presence
Range
IE type and reference
Semantics description
MAC-es Guaranteed Bit Rate


INTEGER (0..2^24-1, …, 2^24..256,000,000)
Unit: bit/s

9.2.1.83	MAC-e Reset Indicator
Indicates the MAC-e (or MAC-i) Reset is performed in UE.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MAC-e Reset Indicator


ENUMERATED (MAC-e Reset)
Means MAC-i Reset in case Maximum MAC-d PDU Size Extended is configured for an E-DCH Logical Channel

9.2.1.84	Scheduling Information
The Scheduling Information IE indicates whether the scheduling information is included for the E-DCH logical channel or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Scheduling Information


ENUMERATED (
Included,
Not Included)


9.2.1.85	E-DCH Power Offset for Scheduling Info
The E-DCH Power Offset for Scheduling Info is used to calculate the [FDD - E-DPDCH][TDD - E-PUCH] power for transmision of scheduling information without any MAC-d PDUs.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH Power Offset for Scheduling Info


INTEGER (0..6)
Unit: dB 
Step: 1 dB

9.2.1.86	MBMS Capability
This parameter defines the MBMS capability for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MBMS Capability


ENUMERATED (MBMS Capable, MBMS non Capable)


9.2.1.87	Modulation
Indicates the modulation to be used for a S-CCPCH CCTrCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Modulation


ENUMERATED (
QPSK, 
16QAM, …)


9.2.1.88	DGANSS Corrections
This IE contains DGANSS corrections.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
Criticality
Assigned Criticality
DGANSS Reference Time
M

INTEGER(0..3570 by step of 30)
Seconds.
Time in GNSS system time (modulo 3600 s) when the DGANSS corrections were calculated 
–

DGANSS Information

1 to <maxSgnType>


–

>GANSS Signal ID
O

9.2.1.106

–

>Status/Health
M

ENUMERATED(UDRE scale 1.0, UDRE scale 0.75, UDRE scale 0.5, UDRE scale 0.3, UDRE scale 0.2, UDRE scale 0.1, no data, invalid data)

–

>DGANSS Signal Information
C-Status/Health
1 to <maxGANSSSat>

If the Cipher information is included these fields are ciphered.
–

>>Sat ID
M

INTEGER(0…63)
Defined in TS 25.331 [18].
–

>>IOD
M

BIT STRING (SIZE(10))

–

>>UDRE
M

ENUMERATED(UDRE  1.0 m,
1.0m < UDRE  4.0m,
4.0m < UDRE  8.0m,
8.0m < UDRE)
The value in this field shall be multiplied by the UDRE Scale Factor in the IE Status/Health to determine the final UDRE estimate for the particular satellite.
–

>>PRC
M

INTEGER(-2047..2047)
Scaling factor 0.32 meters
–

>>RRC
M

INTEGER(-127..127)
Scaling factor 0.032 meters/sec
–

>>DGNSS Validity Period
O

9.2.1.125

YES
ignore

Condition
Explanation
Status/Health
This IE shall be present if the Status/Health IE value is not equal to "no data" or "invalid data".

Range Bound
Explanation
maxGANSSSat
Maximum number of satellites for which data is included in the IE
maxSgnType
Maximum number of signals for which data is included in the IE

9.2.1.89	GANSS Almanac
This IE contains a reduced-precision subset of the ephemeris and clock correction parameters.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
Criticality
Assigned Criticality
Week Number
M

INTEGER(0..255)
Almanac reference week , number of weeks since the beginning of GANSS specific system time (mod 256)
–

CHOICE Almanac Model
M



–

>Keplerian Parameters



Model 1
–

>>Toa
M

INTEGER(0..1023)
Scaling factor 600 s 
Reference time of almanac within week in GANSS TOD time base (OS SIS ICD [39]).
–

>>IODa
M

INTEGER(0..15)
Issue-Of –Data, common to all satellites (OS SIS ICD [39]). 
–

>>Satellite Information KP

1 to <maxGANSSSatAlmanac>

Almanacs are in the order of the SV IDs, the smallest ID first.
–

>>>Sat ID
M

INTEGER(0..63)
Defined in TS 25.331 [18].
–

>>>e
M

BIT STRING (SIZE(11))
dimensionless (OS SIS ICD [39])
–

>>>>i
M

BIT STRING (SIZE(11))
semi-circles (OS SIS ICD [39])
–

>>>OMEGADOT
M

BIT STRING (SIZE(11))
semi-circles/sec (OS SIS ICD [39])
–

>>>SV Status INAV
M

BIT STRING (SIZE(4))
Dimensionless (OS SIS ICD [39]). E5bHS occupies the 2 MSBs and E1-BHS the two LSBs.
–

>>>SV Status FNAV
O

BIT STRING (SIZE(2))
Dimensionless. (OS SIS ICD [53]). E5aHS.


>>>delta A1/2
M

BIT STRING (SIZE(13))
(meters)1/2 (OS SIS ICD [39])
–

>>>OMEGA0
M

BIT STRING (SIZE(16))
 semi-circles (OS SIS ICD [39])
–

>>>M0
M

BIT STRING (SIZE(16))
semi-circles (OS SIS ICD [39])
–

>>>>
M

BIT STRING (SIZE(16))
semi-circles (OS SIS ICD [39])
–

>>>af0
M

BIT STRING (SIZE(16))
Seconds (OS SIS ICD [39])
–

>>>af1
M

BIT STRING (SIZE(13))
sec/sec (OS SIS ICD [39])
–

>NAV Keplerian Parameters



Model 2


>>Keplerian NAV Almanac
M



YES
ignore
>>>Toa
M

INTEGER(0..255)
Scaling factor 212 s 
Reference time of almanac within week in GANSS TOD time base
–

>>>Satellite information NAV-KP

1.. <maxGANSSSatAlmanac>


–

>>>>Sat ID
M

INTEGER (0..63)
Defined in TS 25.331 [18].
–

>>>>e
M

BIT STRING (SIZE(16))
Eccentricity, dimensionless IS-QZSS [47]
–

>>>>>i
M

BIT STRING (SIZE(16))
Correction to inclination,
semi-circles IS-QZSS [47]
–

>>>>OMEGADOT
M

BIT STRING (SIZE(16))
Rate of right ascension,
semi-circles/sec IS-QZSS [47]
–

>>>>SV Health
M

BIT STRING (SIZE(8))
Satellite health IS-QZSS [47]
–

>>>>A1/2
M

BIT STRING (SIZE(24))
Square root of the semi-major axis,
meters1/2 IS-QZSS [47]
–

>>>>OMEGA0
M

BIT STRING (SIZE(24))
Longitude of ascending node of orbit plane at weekly epoch,
semi-circles IS-QZSS [47]
–

>>>>>
M

BIT STRING (SIZE(24))
Argument of perigee
semi-circles IS-QZSS [47]
–

>>>>M0
M

BIT STRING (SIZE(24))
Mean anomaly at reference time
semi-circles IS-QZSS [47]
–

>>>>af0
M

BIT STRING (SIZE(11))
Apparent satellite clock correction
seconds IS-QZSS [47]
–

>>>>af1
M

BIT STRING (SIZE(11))
Apparent satellite clock correction
sec/sec IS-QZSS [47]
–

>Reduced Keplerian Parameters



Model 3


>>Keplerian Reduced Almanac
M



YES
ignore
>>>Toa
M

INTEGER(0..255)
Scaling factor 212 s 
Reference time of almanac within week in GANSS TOD time base
–

>>>Satellite information RED-KP

1.. <maxGANSSSatAlmanac>


–

>>>>Sat ID
M

INTEGER (0..63)
Defined in TS 25.331 [18].
–

>>>>>A
M

BIT STRING (SIZE(8))
meters (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>>0
M

BIT STRING (SIZE(7))
semi-circles (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>>0
M

BIT STRING (SIZE(7))
semi-circles (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>L1 Health
M

BIT STRING (SIZE(1))
dimensionless (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>L2 Health
M

BIT STRING (SIZE(1))
dimensionless (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>L5 Health
M

BIT STRING (SIZE(1))
dimensionless (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>Midi Keplerian Parameters



Model 4


>>Keplerian Midi Almanac
M



YES
ignore
>>>Toa
M

INTEGER(0..255)
Scaling factor 212 s 
Reference time of almanac within week in GANSS TOD time base
–

>>>Satellite information MIDI-KP

1.. <maxGANSSSatAlmanac>


–

>>>>Sat ID
M

INTEGER (0..63)
Defined in TS 25.331 [18].
–

>>>>e
M

BIT STRING (SIZE(11))
dimensionless (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>>i
M

BIT STRING (SIZE(11))
semi-circles (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>>_dot
M

BIT STRING (SIZE (11))
semi-circles/sec (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>sqrtA
M

BIT STRING (SIZE(17))
meters1/2 (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>>0
M

BIT STRING (SIZE(16))
semi-circles (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>>
M

BIT STRING (SIZE 16))
semi-circles (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>M0
M

BIT STRING (SIZE(16))
semi-circles (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>afo
M

BIT STRING (SIZE(11))
seconds (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>af1
M

BIT STRING (SIZE(10))
sec/sec (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>L1 Health
M

BIT STRING (SIZE(1))
Dimensionless (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>L2 Health
M

BIT STRING (SIZE(1))
dimensionless (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>>>>L5 Health
M

BIT STRING (SIZE(1))
dimensionless (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
–

>GLONASS Keplerian Parameters



Model 5


>>Keplerian GLONASS
M



YES
ignore
>>>Satellite information GLO-KP

1.. <maxGANSSSatAlmanac>


–

>>>>NA
M

BIT STRING (SIZE(11))
days [48]
–

>>>>nA
M

BIT STRING (SIZE(5))
dimensionless [48]
–

>>>>HnA
M

BIT STRING (SIZE(5))
dimensionless [48]
–

>>>>>nA
M

BIT STRING (SIZE(21))
semi-circles [48]
–

>>>>ttnA
M

BIT STRING (SIZE(21))
seconds [48]
–

>>>>>inA
M

BIT STRING (SIZE(18))
semi-circles [48]
–

>>>>>TnA
M

BIT STRING (SIZE(22))
sec/orbit period [48]
–

>>>>>T_DOTnA
M

BIT STRING (SIZE(7))
sec/orbit period2 [48]
–

>>>>>nA
M

BIT STRING (SIZE(15))
dimensionless [48]
–

>>>>>nA
M

BIT STRING (SIZE(16))
semi-circles [48]
–

>>>>>nA
M

BIT STRING (SIZE(10))
seconds [48]
–

>>>>CnA
M

BIT STRING (SIZE(1))
dimensionless [48]
–

>>>>MnA
O

BIT STRING (SIZE(2))
dimensionless [48]
–

>SBAS ECEF Parameters



Model 6


>>ECEF SBAS Almanac
M



YES
ignore
>>>Satellite information SBAS-ECEF

1.. <maxGANSSSatAlmanac>


–

>>>>Data ID
M

BIT STRING (SIZE(2))
Dimensionless (DTFA01-96-C-00025 [46])
–

>>>>SV ID
M

INTEGER (0..63)
Defined in TS 25.331 [18].
–

>>>>Health
M

BIT STRING (SIZE(8))
Dimensionless (DTFA01-96-C-00025 [46])
–

>>>>XG
M

BIT STRING (SIZE(15))
meters (DTFA01-96-C-00025 [46])
–

>>>>YG
M

BIT STRING (SIZE(15))
meters (DTFA01-96-C-00025 [46])
–

>>>>ZG
M

BIT STRING (SIZE(9))
meters (DTFA01-96-C-00025 [46])
–

>>>>XG Rate-of-Change
M

BIT STRING (SIZE(3))
meters/sec (DTFA01-96-C-00025 [46])
–

>>>>YG Rate-of-Change
M

BIT STRING (SIZE(3))
meters/sec (DTFA01-96-C-00025 [46])
–

>>>>ZG Rate-of-Change
M

BIT STRING (SIZE(4))
meters/sec (DTFA01-96-C-00025 [46])
–

>>>>t0
M

BIT STRING (SIZE(11))
seconds (DTFA01-96-C-00025 [46])
–

>BDS Keplerian Parameters



Model 7.


>>Keplerian BDS Almanac
M



YES
ignore
>>>Satellite information BDS-KP

1 to <maxGANSSSatAlmanac>




>>>>Sat ID
M

INTEGER (0..63)
Defined in TS 25.331 [16].
–

>>>>toa
M

BIT STRING (SIZE(8))
Almanac reference time
(seconds) (BDS-SIS-ICD [51]).
–

>>>>A1/2
M

BIT STRING (SIZE(24))
Square root of semi-major axis
(meters1/2) (BDS-SIS-ICD [51]).
–

>>>>e
M

BIT STRING (SIZE(17))
Eccentricity, 
dimensionless (BDS-SIS-ICD [51]).
–

>>>>>
M

BIT STRING (SIZE(24))
Argument of Perigee
(semi-circles) (BDS-SIS-ICD [51])
–

>>>>M0
M

BIT STRING (SIZE(24))
Mean anomaly at reference time
(semi-circles) (BDS-SIS-ICD [51]).
–

>>>>>0
M

BIT STRING (SIZE(24))
Longitude of ascending node of orbital plane computed according to reference time
(semi-circles) (BDS-SIS-ICD [51]).
–

>>>>>_dot
M

BIT STRING (SIZE(17))
Rate of right ascension
(semi-circles/sec) (BDS-SIS-ICD [51]).
–

>>>>>i
M

BIT STRING (SIZE(16))
Correction of orbit reference inclination at reference time
(semi-circles) (BDS-SIS-ICD [51]).
–

>>>>a0
M

BIT STRING (SIZE(11))
Satellite clock bias
(seconds) (BDS-SIS-ICD [51]).
–

>>>>a1
M

BIT STRING (SIZE(11))
Satellite clock rate
(sec/sec) (BDS-SIS-ICD [51]).
–

>>>>Health
C-Sat-ID

BIT STRING (SIZE(9))
Satellite Health Information
dimensionless (BDS-SIS-ICD [51]).
–

Complete Almanac Provided
O

BOOLEAN
This field indicates whether almanac is provided for the full GANSS constellation or not. TRUE means complete GANSS almanac is provided.
YES
ignore

Condition
Explanation
Sat-ID
This IE shall be present if the IE “Sat ID” is between 0 and 29 and not needed otherwise.

Range Bound
Explanation
maxGANSSSatAlmanac
Maximum number of satellites for which data is included in the IE

9.2.1.90	GANSS Clock Model
The IE contains fields needed to model the GANSS clock parameters.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
Satellite Clock Model

1 to <maxGANSSClockMod>

Model -1
There may be more than one clock model included if defined in SIS ICD (e.g. two for Galileo) (OS SIS ICD [39]).
>toc
M

BIT STRING (SIZE(14))
defined in (OS SIS ICD [39])
>ai2
M

BIT STRING (SIZE(6))
defined in (OS SIS ICD [39])
>ai1
M

BIT STRING (SIZE(21))
defined in (OS SIS ICD [39])
>ai0
M

BIT STRING (SIZE(31))
defined in (OS SIS ICD [39])
>TGD
O

BIT STRING (SIZE(10))
Broadcast Group Delay(BGD) defined in (OS SIS ICD [39])
>SISA
M

BIT STRING (SIZE(8))
Signal-In-Space Accuracy (SISA), defined in OS SIS ICD [39].
>Model ID
O

INTEGER(0..1,…)
Coded as defined in TS 25.331 [18].

Range bound
Explanation
maxGANSSClockMod
Maximum number of satellite clock models for which data is included in the IE. 

9.2.1.90a	GANSS Additional Clock Models
The IE contains fields needed to model the GANSS clock parameters.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
CHOICE Additional Clock Models




>NAV-Clock Model



Model-2
>>toc
M

BIT STRING (SIZE(16))
Time of clock 
(seconds) IS-QZSS [47]
>>af2
M

BIT STRING (SIZE(8))
Clock correction polynomial coefficient
(sec/sec2) IS-QZSS [47]
>>af1
M

BIT STRING (SIZE(16))
Clock correction polynomial coefficient
(sec/sec) IS-QZSS [47]
>>af0
M

BIT STRING (SIZE(22))
Clock correction polynomial coefficient
(seconds) IS-QZSS [47]
>>TGD
M

BIT STRING (SIZE(8))
Group delay
(seconds) IS-QZSS [47]
>CNAV/CNAV-2 Clock Model



Model-3
>>toc
M

BIT STRING (SIZE(11))
Clock data reference time of week
(seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>top
M

BIT STRING (SIZE(11))
Clock data predict time of week
(seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>URAoc Index
M

BIT STRING (SIZE(5))
SV clock accuracy index
(dimensionless) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>URAoc1 Index
M

BIT STRING (SIZE(3))
SV clock accuracy change index
(dimensionless) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>URAoc2 Index
M

BIT STRING (SIZE(3))
SV clock accuracy change rate index
(dimensionless) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>af2-n
M

BIT STRING (SIZE(10))
SV clock drift rate correction coefficient
(sec/sec2) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>af1-n
M

BIT STRING (SIZE(20))
SV clock drift correction coefficient
(sec/sec) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>af0-n
M

BIT STRING (SIZE(26))
SV clock bias correction coefficient
(seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>TGD
M

BIT STRING (SIZE(13))
Group delay correction
(seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>ISCL1CP
O

BIT STRING (SIZE(13))
Inter signal group delay correction
(seconds) (IS-GPS-800 [45], IS-QZSS [47])
>>ISCL1CD
O

BIT STRING (SIZE(13))
Inter signal group delay correction
(seconds) (IS-GPS-800 [45], IS-QZSS [47])
>>ISCL1C/A
O

BIT STRING (SIZE(13))
Inter signal group delay correction
(seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-QZSS [47])
>>ISCL2C
O

BIT STRING (SIZE(13))
Inter signal group delay correction
(seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-QZSS [47])
>>ISCL5I5
O

BIT STRING (SIZE(13))
Inter signal group delay correction
(seconds) (IS-GPS-705 [44], IS-QZSS [47])
>>ISCL5Q5
O

BIT STRING (SIZE(13))
Inter signal group delay correction
(seconds) (IS-GPS-705 [44], IS-QZSS [47])
>GLONASS Satellite Clock Model



Model-4



n(tb)
M

BIT STRING (SIZE(22))
Satellite clock offset
(seconds) [48]



n(tb)
M

BIT STRING (SIZE(11))
Relative frequency offset from nominal value
(dimensionless) [48]




n
O

BIT STRING (SIZE(5))
Time difference between transmission in G2 and G1
(seconds) [48]
>SBAS Satellite Clock Model



Model-5
>>t0
M

BIT STRING (SIZE(13))
(seconds) (DTFA01-96-C-00025 [46])
>>aGfo
M

BIT STRING (SIZE(12))
(seconds) (DTFA01-96-C-00025 [46])
>>aGf1
M

BIT STRING (SIZE(8))
(sec/sec) (DTFA01-96-C-00025 [46])
>BDS Satellite Clock Model



Model-6.
>>toc
M

BIT STRING (SIZE(17))
Time of clock 
(seconds) (BDS-SIS-ICD [51]).
>>a0
M

BIT STRING (SIZE(24))
Clock correction polynomial coefficient
(seconds) (BDS-SIS-ICD [51]).
>>a1
M

BIT STRING (SIZE(22))
Clock correction polynomial coefficient
(sec/sec) (BDS-SIS-ICD [51]).
>>a2
M

BIT STRING (SIZE(11))
Clock correction polynomial coefficient
(sec/sec2) (BDS-SIS-ICD [51]).
>>TGD1
M

BIT STRING (SIZE(10))
Equipment Group Delay Differential
(seconds) (BDS-SIS-ICD [51]).
>>AODC
M

BIT STRING (SIZE(5))
Age of data,clock 
(dimensionless) (BDS-SIS-ICD [51]).

9.2.1.91	GANSS Ionospheric Model
The IE contains fields needed to model the propagation delays of the GANSS signals through the ionosphere.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
ai0
M

BIT STRING (SIZE(11))
Effective Ionisation Level 1st order parameter. This parameter is used as defined in (OS SIS ICD [39])
ai1
M

BIT STRING (SIZE(11))
Effective Ionisation Level 2nd order parameter. This parameter is used as defined in (OS SIS ICD [39])
ai2
M

BIT STRING (SIZE(14))
Effective Ionisation Level 3rd order parameter. This parameter is used as defined in (OS SIS ICD [39])
GANSS Ionosphere Regional Storm Flags

0..1


>Storm Flag 1
M

BOOLEAN
This parameter is used as defined in (OS SIS ICD [39])
>Storm Flag 2
M

BOOLEAN
This parameter is used as defined in (OS SIS ICD [39])
>Storm Flag 3
M

BOOLEAN
This parameter is used as defined in (OS SIS ICD [39])
>Storm Flag 4
M

BOOLEAN
This parameter is used as defined in (OS SIS ICD [39])
>Storm Flag 5
M

BOOLEAN
This parameter is used as defined in (OS SIS ICD [39])

9.2.1.91a	GANSS Additional Ionospheric Model
The IE contains fields needed to model the propagation delays of the GANSS signals through the ionosphere.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
Data ID
M

BIT STRING (SIZE(2))
Coded as defined in TS 25.331 [18]

0
M

BIT STRING (SIZE(8))
seconds (IS-QZSS [47])

1
M

BIT STRING (SIZE(8))
sec/semi-circle (IS-QZSS [47])

2
M

BIT STRING (SIZE(8))
sec/(semi-circle)2 (IS-QZSS [47])

3
M

BIT STRING (SIZE(8))
sec/(semi-circle)3 (IS-QZSS [47])

0
M

BIT STRING (SIZE(8))
seconds (IS-QZSS [47])

1
M

BIT STRING (SIZE(8))
sec/semi-circle (IS-QZSS [47])

2
M

BIT STRING (SIZE(8))
sec/(semi-circle)2 (IS-QZSS [47])

3
M

BIT STRING (SIZE(8))
sec/(semi-circle)3  (IS-QZSS [47])

9.2.1.92	GANSS Navigation Model
Void.
9.2.1.93	GANSS Orbit Model
This IE contains information for GANSS orbit model parameters.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
CHOICE Orbit Model
M



>Keplerian Parameters



Model-1
>>toe
M

BIT STRING (SIZE(14))
Time-of-Ephemeris in seconds, scale factor 60 (OS SIS ICD [39])
>>>
M

BIT STRING (SIZE(32))
Argument of Perigee (semi-circles) (OS SIS ICD [39])
>>>n
M

BIT STRING (SIZE(16))
Mean Motion Difference From Computed Value (semi-circles/sec) (OS SIS ICD [39])
>>M0
M

BIT STRING (SIZE(32))
Mean Anomaly at Reference Time (semi-circles) (OS SIS ICD [39])
>>OMEGAdot
M

BIT STRING (SIZE(24))
Rate of change of right ascension (semi-circles/sec) (OS SIS ICD [39])
>>e
M

BIT STRING (SIZE(32))
Eccentricity, scale factor 2-33 (OS SIS ICD [39])
>>Idot
M

BIT STRING (SIZE(14))
Rate of change of Inclination Angle (semi-circles/sec) (OS SIS ICD [39])
>>sqrtA
M

BIT STRING (SIZE(32))
Square root of Semi-Major Axis in (meters)1/2 , scale factor 2-19 (OS SIS ICD [39])
>>i0
M

BIT STRING (SIZE(32))
Inclination Angle at Reference Time (semi-circles) (OS SIS ICD [39])
>>OMEGA0
M

BIT STRING (SIZE(32))
Longitude of Ascending Node of Orbit Plane at Weekly Epoch (semi-circles) (OS SIS ICD [39])
>>Crs
M

BIT STRING (SIZE(16))
Amplitude of the Sine Harmonic Correction Term to the Orbit Radius (meters) (OS SIS ICD [39])
>>Cis
M

BIT STRING (SIZE(16))
Amplitude of the Sine Harmonic Correction Term To The Angle Of Inclination (radians) (OS SIS ICD [39])
>>Cus
M

BIT STRING (SIZE(16))
Amplitude of the Sine Harmonic Correction Term To The Argument Of Latitude (radians) (OS SIS ICD [39])
>>Crc
M

BIT STRING (SIZE(16))
Amplitude of the Cosine Harmonic Correction Term to the Orbit Radius (meters) (OS SIS ICD [39])
>>Cic
M

BIT STRING (SIZE(16))
Amplitude of the Cosine Harmonic Correction Term To The Angle Of Inclination (radians) (OS SIS ICD [39])
>>Cuc
M

BIT STRING (SIZE(16))
Amplitude of the Cosine Harmonic Correction Term To The Argument Of Latitude (radians) (OS SIS ICD [39])

9.2.1.93a	GANSS Additional Orbit Models
This IE contains information for GANSS orbit model parameters.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
CHOICE Additional Orbit Models




>NAV-Keplerian Parameters



Model-2
>>URA Index
M

BIT STRING (SIZE(4))
SV accuracy
(dimensionless) (IS-QZSS [47])
>>Fit Interval Flag
M

BIT STRING (SIZE(1))
Fit interval indication
(dimensionless) (IS-QZSS [47])
>>toe
M

BIT STRING (SIZE(16))
Time of ephemeris
(seconds) (IS-QZSS [47])
>>>
M

BIT STRING (SIZE(32))
Argument of perigee
(semi-circles) (IS-QZSS [47])
>>>n
M

BIT STRING (SIZE(16))
Mean motion difference from computed value
(semi-circles/sec) (IS-QZSS [47])
>>M0
M

BIT STRING (SIZE(32))
Mean anomaly at reference time
(semi-circles) (IS-QZSS [47])
>>OMEGAdot
M

BIT STRING (SIZE(24))
Rate of right ascension
(semi-circles/sec) (IS-QZSS [47])
>>e
M

BIT STRING (SIZE(32))
Eccentricity
(dimensionless) (IS-QZSS [47])
>>Idot
M

BIT STRING (SIZE(14))
Rate of inclination angle
(semi-circles/sec) (IS-QZSS [47])
>>sqrtA
M

BIT STRING (SIZE(32))
Square root of semi-major axis
(meters1/2) (IS-QZSS [47])
>>i0
M

BIT STRING (SIZE(32))
Inclination angle at reference time
(semi-circles) (IS-QZSS [47])
>>OMEGA0
M

BIT STRING (SIZE(32))
Longitude of ascending node of orbit plane at weekly epoch
(semi-circles) (IS-QZSS [47])
>>Crs
M

BIT STRING (SIZE(16))
Amplitude of sine harmonic correction term to the orbit radius
(meters) (IS-QZSS [47])
>>Cis
M

BIT STRING (SIZE(16))
Amplitude of sine harmonic correction term to the angle of inclination
(radians) (IS-QZSS [47])
>>Cus
M

BIT STRING (SIZE(16))
Amplitude of sine harmonic correction term to the argument of latitude
(radians) (IS-QZSS [47])
>>Crc
M

BIT STRING (SIZE(16))
Amplitude of cosine harmonic correction term to the orbit radius
(meters) (IS-QZSS [47])
>>Cic
M

BIT STRING (SIZE(16))
Amplitude of cosine harmonic correction term to the angle of inclination
(radians) (IS-QZSS [47])
>>Cuc
M

BIT STRING (SIZE(16))
Amplitude of cosine harmonic correction term to the argument of latitude
(radians) (IS-QZSS [47])
>CNAV/CNAV-2 Keplerian Parameters



Model-3
>>top
M

BIT STRING (SIZE(11))
Data predict time of week
(seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>URAoe Index
M

BIT STRING (SIZE(5))
SV accuracy
(dimensionless) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>>A
M

BIT STRING (SIZE(26))
Semi-major axis difference at reference time
(meters) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>A_dot
M

BIT STRING (SIZE(25))
Chane rate in semi-major axis
(meters/sec) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>>n0
M

BIT STRING (SIZE(17))
Mean motion difference from computed value at reference time
(semi-circles/sec) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>>n0_dot
M

BIT STRING (SIZE(23))
Rate of mean motion difference from computed value
(semi-circles/sec2) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>M0-n
M

BIT STRING (SIZE(33))
Mean anomaly at reference time
(semi-circles) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>en
M

BIT STRING (SIZE(33))
Eccentricity
(dimensionless) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>>n
M

BIT STRING (SIZE(33))
Argument of perigee
(semi-circles) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>>0-n
M

BIT STRING (SIZE(33))
Reference right ascension angle
(semi-circles) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>>>_dot
M

BIT STRING (SIZE(17))
Rate of right ascension difference
(semi-circles/sec) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>io-n
M

BIT STRING (SIZE(33))
Inclination angle at reference time
(semi-circles) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>I0-n_dot
M

BIT STRING (SIZE(15))
Rate of inclination angle
(semi-circles/sec) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>Cis-n
M

BIT STRING (SIZE(16))
Amplitude of sine harmonic correction term to the angle of inclination
(radians) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>Cic-n
M

BIT STRING (SIZE(16))
Amplitude of cosine harmonic correction term to the angle of inclination
(radians) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>Crs-n
M

BIT STRING (SIZE(24))
Amplitude of sine harmonic correction term to the orbit radius
(meters) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>Crc-n
M

BIT STRING (SIZE(24))
Amplitude of cosine harmonic correction term to the orbit radius
(meters) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>Cus-n
M

BIT STRING (SIZE(21))
Amplitude of sine harmonic correction term to the argument of latitude
(radians) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>Cuc-n
M

BIT STRING (SIZE(21))
Amplitude of cosine harmonic correction term to the argument of latitude
(radians) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>GLONASS Earth-Centered, Earth-fixed Parameters



Model-4
>>En
M

BIT STRING (SIZE(5))
Age of data
(days) [48]
>>P1
M

BIT STRING (SIZE(2))
Time interval between two adjacent values of tb
(minutes) [48]
>>P2
M

BIT STRING (SIZE(1))
Change of tb flag
(dimensionless) [48]
>>M
O

BIT STRING (SIZE(2))
Type of satellite
(dimensionless) [48]
>>
M

BIT STRING (SIZE(27))
x-coordinate of satellite at time tb
(kilometers) [48]
>>
M

BIT STRING (SIZE(24))
x-coordinate of satellite velocity at time tb
(kilometers/sec) [48]
>>
M

BIT STRING (SIZE(5))
x-coordinate of satellite acceleration at time tb
(kilometers/sec2) [48]
>>
M

BIT STRING (SIZE(27))
y-coordinate of satellite at time tb
(kilometers) [48]
>>
M

BIT STRING (SIZE(24))
y-coordinate of satellite velocity at time tb
(kilometers/sec) [48]
>>
M

BIT STRING (SIZE(5))
y-coordinate of satellite acceleration at time tb
(kilometers/sec2) [48]
>>
M

BIT STRING (SIZE(27))
z-coordinate of satellite at time tb
(kilometers) [48]
>>
M

BIT STRING (SIZE(24))
z-coordinate of satellite velocity at time tb
(kilometers/sec) [48]
>>
M

BIT STRING (SIZE(5))
z-coordinate of satellite acceleration at time tb
(kilometers/sec2) [48]
>SBAS Earth-Centered, Earth-fixed Parameters



Model-5
>>t0
CClockModel

BIT STRING (SIZE(13))
Time of applicability
(seconds) (DTFA01-96-C-00025 [46])
>>Accuracy
M

BIT STRING (SIZE(4))
(dimensionless) (DTFA01-96-C-00025 [46])
>>XG
M

BIT STRING (SIZE(30))
(meters) (DTFA01-96-C-00025 [46])
>>YG
M

BIT STRING (SIZE(30))
(meters) (DTFA01-96-C-00025 [46])
>>ZG
M

BIT STRING (SIZE(25))
(meters) (DTFA01-96-C-00025 [46])
>>XG RateofChange
M

BIT STRING (SIZE(17))
(meters/sec) (DTFA01-96-C-00025 [46])
>>YG RateofChange
M

BIT STRING (SIZE(17))
(meters/sec) (DTFA01-96-C-00025 [46])
>>ZG RateofChange
M

BIT STRING (SIZE(18))
(meters/sec) (DTFA01-96-C-00025 [46])
>>XG Acceleration
M

BIT STRING (SIZE(10))
(meters/sec2) (DTFA01-96-C-00025 [46])
>>YG Acceleration
M

BIT STRING (SIZE(10))
meters/sec2) (DTFA01-96-C-00025 [46])
>>ZG Acceleration
M

BIT STRING (SIZE(10))
meters/sec2) (DTFA01-96-C-00025 [46])
>BDS Keplerian Parameters



Model-6.
>>URA Index
M

BIT STRING (SIZE(4))
SV accuracy
(dimensionless) (BDS-SIS-ICD [51]).
>>toe
M

BIT STRING (SIZE(17))
Ephemeris reference time
(seconds) (BDS-SIS-ICD [51]).
>>A1/2
M

BIT STRING (SIZE(32))
Square root of semi-major axis 
(meters1/2) (BDS-SIS-ICD [51]).
>>e
M

BIT STRING (SIZE(32))
Eccentricity
(dimensionless) (BDS-SIS-ICD [51]).
>>>
M

BIT STRING (SIZE(32))
Argument of perigee
(semi-circles) (BDS-SIS-ICD [51]).
>>>n
M

BIT STRING (SIZE(16))
Mean motion difference from computed value
(semi-circles/sec) (BDS-SIS-ICD [51]).
>>M0
M

BIT STRING (SIZE(32))
Mean anomaly at reference time
(semi-circles) (BDS-SIS-ICD [51]).
>>>0
M

BIT STRING (SIZE(32))
Longitude of ascending node of orbital of plane computed according to reference time 
(semi-circles) (BDS-SIS-ICD [51]).
>>>_dot
M

BIT STRING (SIZE(24))
Rate of right ascension
(semi-circles/sec) (BDS-SIS-ICD [51]).
>>i0
M

BIT STRING (SIZE(32))
Inclination angle at reference time
(semi-circles) (BDS-SIS-ICD [51]).
>>Idot
M

BIT STRING (SIZE(14))
Rate of inclination angle
(semi-circles/sec) (BDS-SIS-ICD [51]).
>>Cuc
M

BIT STRING (SIZE(18))
Amplitude of cosine harmonic correction term to the argument of latitude
(radians) (BDS-SIS-ICD [51]).
>>Cus
M

BIT STRING (SIZE(18))
Amplitude of sine harmonic correction term to the argument of latitude
(radians) (BDS-SIS-ICD [51]).
>>Crc
M

BIT STRING (SIZE(18))
Amplitude of cosine harmonic correction term to the orbit radius 
(meters) (BDS-SIS-ICD [51]).
>>Crs
M

BIT STRING (SIZE(18))
Amplitude of sine harmonic correction term to the orbit radius
(meters) (BDS-SIS-ICD [51]).
>>Cic
M

BIT STRING (SIZE(18))
Amplitude of cosine harmonic correction term to the angle of inclination
(radians) (BDS-SIS-ICD [51]).
>>Cis
M

BIT STRING (SIZE(18))
Amplitude of sine harmonic correction term to the angle of inclination
(radians) (BDS-SIS-ICD [51]).
>>AODE
M

BIT STRING (SIZE(5))
Age of data,ephemeris
(dimensionless) (BDS-SIS-ICD [51]).

Condition
Explanation
ClockModel
This IE shall be present if “SBAS Earth-Centered, Earth-fixed Parameters” (Model-5) in IE GANSS Additional Clock Models is not included in GANSS Additional Navigation Models IE.

9.2.1.94	GANSS Real Time Integrity
This IE contains parameters that describe the real-time status of the GANSS constellation.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
Satellite Information

1 to <maxGANSSSat>


>Bad GANSS Sat ID
M

INTEGER(0..63)
Defined in TS 25.331 [18].
>Bad GANSS Signal ID
O

BIT STRING (SIZE(8))
Coded as defined in TS 25.331 [18].

Range Bound
Explanation
maxGANSSSat
Maximum number of satellites for which data is included in the IE

9.2.1.95	GANSS Receiver Geographical Position (GANSS RX Pos)
The GANSS Receiver Geographical Position IE is used to identify the geographical coordinates of a GANSS receiver relevant for a certain Information Exchange Object.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Latitude Sign
M

ENUMERATED (
North, 
South) 

Degrees of Latitude
M

INTEGER (0..231-1)
The IE value (N) is derived by this formula:
NN231 X /90 / N+1
X being the latitude in degree (0°.. 90°)
Degrees of Longitude
M

INTEGER 
(-231..231-1)
The IE value (N) is derived by this formula:
NN232 X /360 / N+1
X being the longitude in degree (-180°..+180°)
Direction of Altitude
M

ENUMERATED (
Height, 
Depth)

Altitude
M

INTEGER (0..215-1)
The relation between the value (N) and the altitude (a) in meters it describes is NT a <N+1, except for N=215-1 for which the range is extended to include all greater values of (a).

9.2.1.96	GANSS Time Model
The GANSS Time Model IE contains a set of parameters needed to relate GANSS time to selected time reference indicated by GNSS_TO_ID.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
Criticality
Assigned Criticality
GANSS Time Model Reference Time
M

INTEGER(0.. 37799)
GANSS reference time (modulo 1 week) in seconds. The scale factor is 24
–

TA0
M

INTEGER(-2147483648..2147483647)
Seconds, scale factor 2-35
–

TA1
O

INTEGER(-8388608..8388607)
sec/sec, scale factor 2-51
–

TA2
O

INTEGER(-64..63)
sec/sec2 , scale factor 2-68
–

GNSS_TO_ID
M

ENUMERATED(GPS,…,
Galileo, QZSS, GLONASS, BDS)

–

Week Number
O

INTEGER(0..8191)
Reference week of GANSS Time Model
–

Delta_T
O

INTEGER(-128..127)
This field specifies the integer seconds of the GNSS-GNSS Time Offset.
Scale factor 1 second.
YES
ignore

9.2.1.96a	GANSS Additional Time Models
The GANSS Additional Time Models IE contains a set of parameters needed to relate GANSS time to selected time references.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
GNSS-GNSS Time Model

1..<maxGANSS-1>


>GANSS Time Model


9.2.1.96


Range Bound
Explanation
maxGANSS-1
Maximum number of GANSS systems for which data is included in this IE. 

9.2.1.97	GANSS UTC Model
The GANSS UTC Model IE contains a set of parameters needed to relate GANSS time to Universal Time Coordinate (UTC).
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
A1
M

BIT STRING (SIZE(24))
sec/sec (OS SIS ICD [39])
A0
M

BIT STRING (SIZE(32))
seconds (OS SIS ICD [39])
tot
M

BIT STRING (SIZE(8))
seconds (OS SIS ICD [39])
WNt
M

BIT STRING (SIZE(8))
weeks (OS SIS ICD [39])

tLS
M

BIT STRING (SIZE(8))
seconds (OS SIS ICD [39])
WNLSF
M

BIT STRING (SIZE(8))
weeks (OS SIS ICD [39])
DN
M

BIT STRING (SIZE(8))
days (OS SIS ICD [39])

tLSF
M

BIT STRING (SIZE(8))
seconds (OS SIS ICD [39])

9.2.1.97a	GANSS Additional UTC Models
The GANSS Additional UTC Models IE contains several sets of parameters needed to relate GANSS time to Universal Time Coordinate (UTC), as defined in [43,44,45,46,47,48].
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
CHOICE Additional UTC Models




>Model Set 1




>>A0-n
M

BIT STRING (SIZE(16))
Bias coefficient of GNSS time scale relative to UTC time scale
(seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>A1-n
M

BIT STRING (SIZE(13))
Drift coefficient of GNSS time scale relative to UTC time scale
(sec/sec) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>A2-n
M

BIT STRING (SIZE(7))
Drift rate correction coefficient of GNSS time scale relative to UTC time scale
(sec/sec2) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>>tLS
M

BIT STRING (SIZE(8))
Current or past leap second count
(seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>tot
M

BIT STRING (SIZE(16))
Time data reference time of week
(seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>WNot
M

BIT STRING (SIZE(13))
Time data reference week number
(weeks) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>WNLSF
M

BIT STRING (SIZE(8))
Leap second reference week number
(weeks) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>DN
M

BIT STRING (SIZE(4))
Leap second reference day number 
(days) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>>>tLSF
M

BIT STRING (SIZE(8))
Current or future leap second count
(seconds) (IS-GPS-200 [43], IS-GPS-705 [44], IS-GPS-800 [45], IS-QZSS [47])
>Model Set 2




>>NA
M

BIT STRING (SIZE(11))
Callendar day number within four-year period beginning since the leap year
(days) [48]



c
M

BIT STRING (SIZE(32))
GLONASS time scale correction to UTC(SU)
(seconds) [48]
>>Delta UT1
O



>>>B1
M

BIT STRING (SIZE(11))
Coefficient to determine CUT1
(seconds) [48]
>>>B2
M

BIT STRING (SIZE(10))
Coefficient to determine CUT1
(seconds/msd) [48]
>>KP
O

BIT STRING (SIZE(2))
Notification of expected leap second correction
(dimensionless) [48]
>Model Set 3




>>A1WNT
M

BIT STRING (SIZE(24))
sec/sec
(DTFA01-96-C-00025 [46], Message Type 12)
>>A0WNT
M

BIT STRING (SIZE(32))
seconds 
(DTFA01-96-C-00025 [46], Message Type 12)
>>tot
M

BIT STRING (SIZE(8))
seconds
(DTFA01-96-C-00025 [46], Message Type 12)
>>WNt
M

BIT STRING (SIZE(8))
weeks
(DTFA01-96-C-00025 [46], Message Type 12)
>>>tLS
M

BIT STRING (SIZE(8))
seconds
(DTFA01-96-C-00025 [46], Message Type 12)
>>WNLSF
M

BIT STRING (SIZE(8))
weeks
(DTFA01-96-C-00025 [46], Message Type 12)
>>DN
M

BIT STRING (SIZE(8))
days
(DTFA01-96-C-00025 [46], Message Type 12)
>>>tLSF
M

BIT STRING (SIZE(8))
seconds
(DTFA01-96-C-00025 [46], Message Type 12)
>>UTC Standard ID
M

BIT STRING (SIZE(3))
dimensionless
Coded as defined in TS 25.331 [18]
>Model Set 4




>>A0UTC
M

BIT STRING (SIZE(32))
Seconds (BDS-SIS-ICD [51]).
>>A1UTC
M

BIT STRING (SIZE(24))
sec/sec (BDS-SIS-ICD [51]).
>>>tLS
M

BIT STRING (SIZE(8))
Seconds (BDS-SIS-ICD [51]).
>>WNLSF
M

BIT STRING (SIZE(8))
Weeks (BDS-SIS-ICD [51]).
>>DN
M

BIT STRING (SIZE(8))
Days (BDS-SIS-ICD [51]).
>>>tLSF
M

BIT STRING (SIZE(8))
Seconds (BDS-SIS-ICD [51]).

9.2.1.98	TUTRAN-GANSS Accuracy Class
The TUTRAN-GANSS Accuracy Class IE indicates the accuracy class of the UTRAN GANSS Timing of Cell Frames for UE Positioning measurement.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TUTRAN-GANSS Accuracy Class


ENUMERATED (
Accuracy Class A, Accuracy Class B, Accuracy Class C, …)
More information about TUTRAN-GANSS Measurement Accuracy Class is included in TS 25.133 [22] and TS 25.123 [23].

9.2.1.99	TUTRAN-GANSS Measurement Threshold Information
The TUTRAN-GANSS Measurement Threshold Information IE defines the related thresholds for UTRAN GANSS Timing of Cell Frames for UE Positioning measurements shall trigger the event On Modification.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TUTRAN-GANSS Change Limit
O

INTEGER (1..256)
Change of TUTRAN-GANSS value compared to previously reported value, which shall trigger a new report. 
Unit in 1/16 chip.
Predicted TUTRAN-GANSS Deviation Limit
O

INTEGER (1..256)
Deviation of the predicated TUTRAN-GANSS from the latest measurement result, which shall trigger a new report. 
Unit in 1/16 chip.

9.2.1.100	TUTRAN-GANSS Measurement Value Information
The TUTRAN-GANSS Measurement Value Information IE indicates the measurement results related to the UTRAN GANSS Timing of Cell Frames for UE Positioning measurements.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
TUTRAN-GANSS
M


Indicates the UTRAN GANSS Timing of Cell Frames for UE Positioning. According to mapping in TS 25.123 [23]; significant values range from 0 to 37158911999999.
–

  >MS
M

INTEGER(0..16383)
Most Significant Part
–

  >LS
M

INTEGER(0..4294967295)
Least Significant Part
–

TUTRAN-GANSS Quality
O

INTEGER(0..255)
Indicates the standard deviation (std) of the TUTRAN- GANSS measurements in 1/16 chip. TUTRAN- GANSS Quality =  E[(x-µ)2] = std of reported TUTRAN- GANSS Value, where x is the reported TUTRAN-GANSS Value and µ = E[x] is the expectation value of x.
–

TUTRAN-GANSS Drift Rate
M

INTEGER(-50..50)
Indicates the TUTRAN- GANSS drift rate in 1/256 chip per second.
A positive value indicates that the UTRAN clock is running at a lower frequency than GANSS clock.
–

TUTRAN-GANSS Drift Rate Quality
O

INTEGER(0..50)
Indicates the standard deviation (std) of the TUTRAN- GANSS drift rate measurements in 1/256 chip per second. TUTRAN- GANSS Drift Rate Quality =  E[(x-µ)2] = std of reported TUTRAN- GANSS Drift Rate, where x is the reported TUTRAN- GANSS Drift Rate and µ = E[x] is the expectation value of x.
–

GANSS Time ID
O

9.2.1.104a
Absence of this IE means Galileo system time.
YES
ignore

9.2.1.101	GANSS Reference Time
Void.
9.2.1.102	HARQ Memory Partitioning
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
CHOICE HARQ Memory Partitioning

1


–

>Implicit






>>Number of Processes
M

INTEGER (1..8,...12,14,16)
For HARQ process IDs going from 0 to "Number of Processes" – 1 the Total number of soft channel bits TS 25.306 [33] is partitioned equally between all HARQ processes according to the rules in TS 25.331 [18].
–

>Explicit






>>HARQ Memory Partitioning Infomation

1..<maxnoofHARQprocesses>

The first instance of the parameter corresponds to HARQ process with identifier 0, the second instance to HARQ process with identifier 1, and so on.
–

>>>Process Memory Size
M

9.2.1.49D
See TS 25.331 [18]
–

>>HARQ Memory Partitioning Information Extension For MIMO

0, 4, 6 or 8

For FDD and 1.28Mcps TDD only 
The 1st instance corresponds to HARQ process with identifier set to  “maxnoofHARQprocesses”, the 2nd  instance to HARQ process with identifier set to “maxnoofHARQprocesses+1”, and so on.
GLOBAL
ignore
>>>Process Memory Size
M

9.2.1.49D
See TS 25.331 [18]

–


Range Bound
Explanation
MaxnoofHARQprocesses
Maximum number of HARQ processes for one UE [FDD and 1.28Mcps TDD- per stream (the maximum number of HARQ processes per UE is 2 * MaxnoofHARQprocesses in dual stream transmission mode)]

9.2.1.103	GANSS Data Bit Assistance

IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
GANSS TOD
M

INTEGER(0..59,…)
Refererence time (modulo 1 minute) of the first bit of the data in Data Bits IE, in seconds.
Data Bit Assistance List

1..<maxGANSSSat>


>Sat ID
M

INTEGER(0..63)
Defined in TS 25.331 [18].
>Data Bit Assistance Sgn List

1..<maxSgnType>


>>GANSS Signal ID
M

9.2.1.106

>>Data Bits
M

BIT STRING (SIZE(1..1024))
Raw data bits as transmitted from a specific satellite at the time indicated by GANSS_TOD. See TS 25.331 [18].

Range Bound
Explanation
maxGANSSSat
Maximum number of satellites for which data is included in the IE
maxSgnType
Maximum number of GANSS signals included in the IE

9.2.1.104	GANSS ID
This IE defines a particular GANSS.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
GANSS ID
M

INTEGER(0..7,…)
Defines the GANSS and is coded as defined in TS 25.331 [18]. 

9.2.1.104a	GANSS Time ID
This IE defines a particular GANSS system time.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
GANSS Time ID
M

INTEGER(0..7,…)
Defines the GANSS system time for the UTRAN GANSS Timing of Cell Frames for UE Positioning.
Coded as defined in TS 25.331 [18], subclause 10.3.7.93a.

9.2.1.105	GANSS Navigation Model And Time Recovery
This IE contain information required to manage the transfer of precise navigation data to the GANSS-capable UE.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
GANSS Transmission Time
M

9.2.1.107
GANSS Time when the Navigation model has been retrieved
Non-Broadcast Indication
O

ENUMERATED(true)
If this IE is present, GANSS navigation model is not derived from satellite broadcast. See NOTE 1
Satellite Information

1 to <maxGANSSSat>


>Sat ID
M

INTEGER(0..63)
Defined in TS 25.331 [18].
>SV Health
M

BIT STRING (SIZE(9))
Coded as defined in (OS SIS ICD [39])
>IOD
M

BIT STRING (SIZE(10))

>GANSS Clock Model
M

9.2.1.90

>GANSS Orbit Model
M

9.2.1.93

NOTE 1 :	The Non-Broadcast Indication allows to inform that the navigation model is not bit-to-bit the one broadcast by the satellite. If it is set to 1, the UE is informed that techniques such as data wiping off applied to the navigation model may not work for instance. 

Range bound
Explanation
maxGANSSSat
Maximum number of satellites for which data is included in the IE. 

9.2.1.105a	GANSS Additional Navigation Models And Time Recovery
This IE contain information required to manage the transfer of precise navigation data to the GANSS-capable UE.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
GANSS Transmission Time
M

9.2.1.107
GANSS Time when the Navigation model has been retrieved
Non-Broadcast Indication
O

ENUMERATED(true)
If this IE is present, GANSS navigation model is not derived from satellite broadcast. See NOTE 1 in 9.2.1.105.
Satellite Information

1..<maxGANSSSat>


>Sat ID
M

INTEGER(0..63)
Defined in TS 25.331 [18].
>SV Health
M

BIT STRING (SIZE(6))
Coded as defined in TS 25.331 [18].
>IOD
M

BIT STRING (SIZE(11))
Coded as defined in TS 25.331 [18].
>GANSS Additional Clock Models
M

GANSS Addtional Clock Models 9.2.1.90a

>GANSS Additional Orbit Models
M

GANSS Additional Orbit Models 9.2.1.93a


Range bound
Explanation
maxGANSSSat
Maximum number of satellites for which data is included in this IE. The value of maxGANSSSat is 64

9.2.1.106	GANSS Signal ID
This IE defines a specific signal within a particular GANSS.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
GANSS Signal ID
M

INTEGER(0..7,…)
Coded as defined in TS 25.331 [18].

9.2.1.107	GANSS Transmission Time
This IE indicates the GANSS Transmission Time
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
GANSS Day
O

INTEGER(0..8191)
The sequential number of days from the origin of the GNSS system time (indicated by the GANSS_ID given in the Requested Data Value IE) modulo 8192 days (about 22 years).
GANSS TOD
M

INTEGER(0..86399)
GANSS Time of Day in seconds

9.2.1.107a	GANSS Earth Orientation Parameters
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
tEOP
M

BIT STRING (SIZE(16))
EOP data reference time
(seconds) IS-GPS-200 [43]
PM_X
M

BIT STRING (SIZE(21))
X-axis polar motion value at reference time
(arc-seconds) IS-GPS-200 [43]
PM_X_dot
M

BIT STRING (SIZE(15))
X-axis polar motion drift at reference time
(arc-seconds/day) IS-GPS-200 [43]
PM_Y
M

BIT STRING (SIZE(21))
Y-axis polar motion value at reference time
(arc-seconds) IS-GPS-200 [43]
PM_Y_dot
M

BIT STRING (SIZE(15))
Y-axis polar motion drift at reference time
(arc-seconds/day) IS-GPS-200 [43]

UT1
M

BIT STRING (SIZE(31))
UT1-UTC difference at reference time
(seconds) IS-GPS-200 [43]

UT1_dot
M

BIT STRING (SIZE(19))
Rate of UT1-UTC difference at reference time
(seconds/day) IS-GPS-200 [43]

9.2.1.107b	SBAS ID
This IE defines a specific SBAS.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SBAS ID
M

ENUMERATED(
WAAS, 
EGNOS,
MSAS,
GAGAN, … )


9.2.1.107c	GANSS Auxiliary Information
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
CHOICE GANSS-ID




>GANSS-ID-1



This choice may only be present if GANSS ID indicated “Modernized GPS”
>>Aux Info List

1 .. <maxGANSSSat>


>>>Sat ID
M

INTEGER(0..63)
Defined in TS 25.331 [18].
>>>Signals Available
M

BIT STRING (SIZE(8))
Coded as defined in TS 25.331 [18].
>GANSS-ID-3



This choice may be present if GANSS ID indicated “GLONASS”
>>Aux Info List

1 .. <maxGANSSSat>


>>>Sat ID
M

INTEGER(0..63)
Defined in TS 25.331 [18].
>>>Signals Available
M

BIT STRING (SIZE(8))
Coded as defined in TS 25.331 [18].
>>>Channel Number
M

INTEGER (7..13)
This field indicates the GLONASS carrier frequency number of the satellite identified by Sat ID, as defined in [48].

Range Bound
Explanation
maxGANSSSat
Maximum number of GANSS satellites for which data is included in this IE. 

9.2.1.107d	Additional Ionospheric Model Request
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Additional Ionospheric Model Request
M

BIT STRING (SIZE(2))
Data ID for GANSS Additional Ionospheric Model as defined in TS 25.331 [18], subclause 10.3.7.92b.

9.2.1.107e	Earth Orientation Parameters Request
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Earth Orientation Parameters Request
M

BOOLEAN
True means requested.

9.2.1.107f	GANSS Additional Navigation Models And Time Recovery Request
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
GANSS Additional Navigation Models And Time Recovery Request
M

BOOLEAN
True means requested.

9.2.1.107g	GANSS Additional UTC Models Request
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
GANSS Additional UTC Models Request
M

BOOLEAN
True means requested.

9.2.1.107h	GANSS Auxiliary Information Request
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
GANSS Auxiliary Information Request
M

BOOLEAN
True means requested.

9.2.1.108	IP Multicast Indication
The IP Multicast Indication IE indicates the IP multicast group information dedicated to an MBMS service and the CFN Offset, defined as the offset between MFN and CFN for a FACH. When Node B receives such an indication, if supported, it may join the corresponding IP multicast group. When Node B receives data frame from this IP multicast group, it shall consider the value of the CFN field in the data frame as MFN and calculate the actual CFN for the concerned FACH according to following equation:
	CFN = (MFN – CFN Offset) mod 256.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Transport Layer Address
M

9.2.1.63
An MBMS service corresponds to a dedicated IP multicast address.
Binding ID
M

9.2.1.4
Indicating multicast port.
CFN Offset
M

INTEGER (0..255) 


9.2.1.109	IP Multicast Data Bearer Indication
The IP Multicast Data Bearer Indication IE indicates whether the Node B is ready for receiving concerned MBMS service data through IP multicast transport bearer.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
IP Multicast Data Bearer Indication


BOOLEAN
True: IP multicast data bearer is used.
False: IP multicast data bearer is not used.

9.2.1.110	SixtyfourQAM DL Capability
This parameter defines the SixtyfourQAM downlink capability for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SixtyfourQAM DL Capability


ENUMERATED (SixtyfourQAM DL Capable,  SixtyfourQAM DL Non-Capable)


9.2.1.111	FACH Measurement Occasion Cycle Length Coefficient
The FACH Measurement Occasion Cycle Length Coefficient IE provides information used for MAC-hs scheduling decision for MAC-c PDU in Node B. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
FACH Measurement Occasion Cycle Length Coefficient


INTEGER (1..12)


9.2.1.112	MAC-ehs Reset Timer
The MAC-ehs Reset Timer IE is used as Reset Timer(Treset) described in ref TS 25.321 [32] subclause 11.6.4.5.
IE/Group Name
Presence
Range
IE type and reference
Semantics description
MAC-ehs Reset Timer


ENUMERATED (1, 2, 3, 4, …)
Timer in multiples of T1 values (milliseconds). Used when MAC-ehs reordering queue is reset in CELL_FACH and CELL_PCH

9.2.1.113	Paging MAC Flow ID
Paging MAC Flow ID is the unique identifier for one Paging MAC flow.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Paging MAC Flow ID


INTEGER
(0..3)


9.2.1.114	Enhanced FACH Capability
This parameter defines the Enhanced FACH capability for a Local Cell. [1.28Mcps TDD - This parameter defines the Enhanced FACH capability for both uplink and downlink]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Enhanced FACH Capability


ENUMERATED (Enhanced FACH Capable, Enhanced FACH Non-Capable)


9.2.1.115	Enhanced PCH Capability
This parameter defines the Enhanced PCH capability for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Enhanced PCH Capability


ENUMERATED (Enhanced PCH Capable, Enhanced PCH Non-Capable)


9.2.1.116	Enhanced UE DRX Capability
This parameter defines the Enhanced UE DRX capability for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Enhanced UE DRX Capability


ENUMERATED (Enhanced UE DRX Capable, Enhanced UE DRX  non Capable)


9.2.1.117	Priority Queue Information for Enhanced FACH/PCH
The Priority Queue Information for Enhanced FACH/PCH IE provides information associated to HSDPA Priority Queue used for Enhanced FACH and/or Enhanced PCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Priority Queue ID
M

9.2.1.49C

Scheduling Priority Indicator 
M

9.2.1.53H

T1
M

9.2.1.56a

MAC-ehs Reset Timer
M

9.2.1.112

Discard Timer
O

9.2.1.24E
Shall be ignored in case of Enhanced PCH
MAC-hs Window Size
M

9.2.1.38B

Maximum MAC-c PDU Size
M

MAC PDU Size Extended
9.2.1.38C


9.2.1.118	MIMO Capability
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MIMO Capability


ENUMERATED (MIMO Capable,  MIMO Non-Capable)


9.2.1.119	MIMO Activation Indicator
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MIMO Activation Indicator
M

NULL


9.2.1.120	MIMO Mode Indicator
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MIMO Mode Indicator


ENUMERATED (Activate,  Deactivate)


9.2.1.121	SixtyfourQAM DL and MIMO Combined Capability
This parameter defines the SixtyfourQAM downlink and MIMO combined capability for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SixtyfourQAM DL and MIMO Combined Capability


ENUMERATED (SixtyfourQAM DL and MIMO Combined Capable,  SixtyfourQAM DL and MIMO Combined Non-Capable)


9.2.1.122	DL RLC PDU Size Format
The DL RLC PDU Size Format IE indicates the downlink RLC PDU size format used for a Priority Queue.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL RLC PDU Size Format


ENUMERATED (
Fixed RLC PDU size, Flexible RLC PDU size ,...)


9.2.1.123	UE Aggregate Maximum Bit Rate
The UE Aggregate Maximum Bit Rate IE is applicable for all Non-GBR bearers per UE which is defined for the Downlink and the Uplink direction and provided by the CN to the RNC. At least one of the UE Aggregate Maximum Bit Rate Downlink IE and UE Aggregate Maximum Bit Rate Uplink IE shall be included in the UE Aggregate Maximum Bit Rate IE.
IE/Group Name
Presence
Range
IE type and reference
Semantics description
UE Aggregate Maximum Bit Rate



Desc:
Applicable for non-GBR bearers
>UE Aggregate Maximum Bit Rate Downlink
O

INTEGER (1..1,000,000,000)
Desc.: This IE indicates the aggregated maximum number of bits delivered by UTRAN and to UTRAN in DL within a period of time, divided by the duration of the period for all non-GBR bearers in one UE. The MBR of non-GBR bearers shall be ignored if this IE present.
>UE Aggregate Maximum Bit Rate Uplink
O

INTEGER (1..1,000,000,000)
Desc.: This IE indicates the aggregated maximum number of bits delivered by UTRAN and to UTRAN in UL within a period of time, divided by the duration of the period for all non-GBR bearers in one UE. The MBR of non-GBR bearers shall be ignored if this IE present.

9.2.1.124	Dormant Mode Indicator
The Dormant Mode Indicator IE controls the dormant mode for the cell. In dormant mode there is no power transmitted in the cell, but  the cell remains existing in the Node B. When Dormant Mode Indicator IE = "Enter Dormant Mode" the Node B is requested to reconfigure the cell to dormant mode. When Dormant Mode Indicator IE = "Leave Dormant Mode" the Node B is requested to take the cell into normal service.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Dormant Mode Indicator


ENUMERATED (Enter Dormant Mode, Leave Dormant Mode, ...)


9.2.1.125	DGNSS Validity Period
This IE defines the validity period of the GNSS differential corrections provided in DGPS corrections and DGANSS corrections IEs
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UDRE Growth Rate
M

Enumerated(
UDRE growth 1.5, 
UDRE growth 2,
UDRE growth 4,
UDRE growth 6,
UDRE growth 8,
UDRE growth 10,
UDRE growth 12,
UDRE growth 16)
This field provides an estimate of the growth rate of uncertainty (1T) in the corrections. The UDRE at time value specified in the Time of Validity for UDRE Growth Rate field is the value of this field times the value of UDRE provided in DGPS Corrections or DGANSS corrections IE (TS 25.331 [18]).
Time of Validity for UDRE Growth Rate
M

Enumerated(
val20sec, 
val40sec, 
val80sec, 
val160sec, 
val320sec, 
val640sec, 
val1280sec, 
val2560sec)
This field specifies the time when the UDRE Growth Rate field applies (TS 25.331 [18]]).

9.2.1.126	E-RNTI Release Status
Indicates the E-RNTI is released or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-RNTI Release Status


ENUMERATED (released, not-released)


9.2.1.127	DBDS Corrections
This IE contains the DBDS differential corrections.
Information Element/Group name
Need
Multi
Type and Reference
Semantics description
DBDS Reference Time
M

Integer(0..3570 by step of 30)
Seconds.
Time in BDS system time (modulo 3600 s) when the DBDS corrections are valid. 
DBDS information

1 to <maxSgnType>


>DBDS Signal ID
O

9.2.1.106
Absence of this IE means the B1I.
>DBDS signal information

1 to <maxGANSSSat>


>>Sat ID
M

INTEGER (0…63)
Defined in TS 25.331 [18].
>>UDREI
M

INTEGER (0…15)
User Differential Range Error Index  (dimensionless) (BDS-SIS-ICD [51]).
>>RURAI
M

INTEGER (0…15)
BDS Regional User Range Accuracy Index, (dimensionless) (BDS-SIS-ICD [51]).
>>Δt 
M

BIT STRING (SIZE(13))
Equivalent Clock Correction, (meters) (BDS-SIS-ICD [51])

9.2.1.128	BDS Ionospheric Grid Model
This IE contains Ionospheric Grid information to calculate the propagation delays of the B1I signals through the ionosphere.
Information Element/Group name
Need
Multi
Type and Reference
Semantics description
BDS Reference Time
M 

INTEGER (0..3570 by step of 30)
Seconds.
Time in BDS system time (modulo 3600 s) when the BDS Ionospheric Grid Information is valid.
BDS Ionospheric Grid Information

1 to <maxIGPInf>

The maximum number of grid points that can be included in this version of the specification is 16.
>IGP number
M

INTEGER (1..320)
Ionospheric grid point number
(dimensionless) (BDS-SIS-ICD [51]).
>Vertical Delay
M

BIT STRING (SIZE(9))
Vertical Delay at Ionospheric Grid Points ,(meters) (BDS-SIS-ICD [51])
>GIVEI
M

BIT STRING (SIZE(4))
Grid Ionospheric Vertical Error Index
(dimensionless) (BDS-SIS-ICD [51]).

Range bound
Explanation
maxIGPInfo
Maximum number of ionospheric grid points for BDS.

9.2.1.129	Improved Synchronized RRC Indicator
The Improved Synchronized RRC Indicator is used to handle the improved synchronized RRC procedures.
Information Element/Group name
Need
Multi
Type and Reference
Semantics description
Improved Synchronized RRC Indicator
M

ENUMERATED (true)


9.2.2	FDD specific parameters
9.2.2.a	ACK-NACK Repetition Factor
The ACK-NACK Repetiton Factor IE indicates the number of consecutive repetitions of the ACK and NACK.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
ACK-NACK Repetition Factor


INTEGER (1..4,...)
Step: 1

9.2.2.b	ACK Power Offset
The ACK Power Offset IE indicates Power offset used in the UL between the HS-DPCCH slot carrying HARQ ACK information and the associated DPCCH. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
ACK Power Offset


INTEGER (0..8,..., 9..10)
According to mapping in ref. TS 25.213 [9] subclause 4.2.1.

9.2.2.A	Active Pattern Sequence Information
Defines the parameters for the compressed mode gap pattern sequence activation. For details see ref. TS 25.331 [18].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
CM Configuration Change CFN 
M

CFN 
9.2.1.7



Transmission Gap Pattern Sequence Status

0..<maxTGPS>


-

>TGPS Identifier
M

INTEGER (1..maxTGPS)
If the group is not present, none of the pattern sequences are activated. References an already defined sequence.
-

>TGPRC
M

INTEGER (0..511)
The number of transmission gap patterns within the Transmission Gap Pattern Sequence.
"0"=Infinity
-

>TGCFN
M

CFN
9.2.1.7
Connection Frame Number of the first frame of the first pattern 1 within the Transmission Gap Pattern Sequence.
-

>Affected HS-DSCH serving cell List 

0..<maxNrOfHSDSCH>

The HS-DSCH serving cells affected by the TGPS when activating frequency specific compressed mode. Max 4 in this 3GPP release. 
EACH
reject
>>C-ID
M

9.2.1.9
 
-


Range Bound
Explanation
maxTGPS
Maximum number of active pattern sequences. Value 6.
maxNrOfHSDSCH
Maximum number of Primary Serving plus Secondary Serving HS-DSCH cells for one UE

9.2.2.B	Adjustment Period
The Adjustment Period IE defines the period to be used for power balancing.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Adjustment Period


INTEGER (1..256)
Unit: Frames

9.2.2.C	Adjustment Ratio
The Adjustment Ratio IE (Radj) defines the convergence rate used for the associated Adjustment Period.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Adjustment Ratio


INTEGER (0..100)
Unit: None
Range: 0..1
Step: 0.01

9.2.2.D	AICH Power
The AICH Power IE indicates a power level (measured as the power per transmitted acquisition indicator when several AIs are transmitted in parallel) relative to the primary CPICH power configured in a cell. If Transmit Diversity is applied to the AICH, the AICH Power IE indicates the power offset between the linear sum of the power for the AICH on all branches and the Primary CPICH power configured in a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
AICH Power


INTEGER (-22..+5)
Unit: dB
Range: -22 .. +5 dB
Step: 1 dB

9.2.2.1	AICH Transmission Timing
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
AICH Transmission Timing


ENUMERATED 
(0, 1)
See parameter AICH_Transmission_Timing in ref. TS 25.211 [7].

9.2.2.1A	AP Preamble Signature
Void.

9.2.2.1B	AP Sub Channel Number
Void.

9.2.2.1Ba	Best Cell Portions
Best Cell Portions IE indicates the best received cell portions and their SIR values when Cell Portions are defined in the cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Best Cell Portions

1..<maxnoofBestCellPortions>


>Cell Portion ID
M

9.2.2.1Ca

>SIR Value
M

INTEGER (0..63)
According to mapping in TS 25.133 [22] and TS 25.123 [23]

Range Bound
Explanation
maxnoofBestCellPortions
Maximum number of reported Best Received Cell Portions

9.2.2.1Bb	Bundling Mode Indicator
The Bundling Mode Indicator indicates whether the bundling shall be done or shall not be done for Iub.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Bundling Mode Indicator


ENUMERATED (
Bundling, No bundling)
The value "Bundling" is applicable only when E-TTI indicates "2ms".

9.2.2.1C	CD Sub Channel Numbers
Void.
9.2.2.1Ca	Cell Portion ID
Cell Portion ID is the unique identifier for a cell portion within a cell. See TS 25.215 [4].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Cell Portion ID


INTEGER (0..63,…)


9.2.2.1D	Channel Assignment Indication
Void.
9.2.2.2	Chip Offset
The Chip Offset is defined as the radio timing offset inside a radio frame. The Chip offset is used as offset relative to the Primary CPICH timing for the DL DPCH or for the F-DPCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Chip Offset


INTEGER (0..38399)
Unit: chips

9.2.2.2A	Closed Loop Timing Adjustment Mode
Indicates when the phase/amplitude adjustment is performed in the DL in relation to the receipt of the UL feedback command in case of closed loop mode transmit diversity on DPCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Closed Loop Timing Adjustment Mode


ENUMERATED (
Offset1, 
Offset2,
…)
According to ref. TS 25.214 [10] subclause 7.1:
"Offset1" = slot(j+1)mod15
"Offset2" = slot(j+2)mod15

9.2.2.3	Common Channels Capacity Consumption Law
Void.
9.2.2.3A	Compressed Mode Deactivation Flag
The Compressed Mode Deactivation Flag indicates whether Compressed Mode shall be deactivated or not in the new RL.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Compressed Mode Deactivation Flag


ENUMERATED (
Deactivate,
Maintain Active)


9.2.2.4	Compressed Mode Method
Void.
9.2.2.4A	CPCH Allowed Total Rate
Void.
9.2.2.4B	CPCH Scrambling Code Number
Void.
9.2.2.4C	CPCH UL DPCCH Slot Format
Void.
9.2.2.4Ca	CQI Power Offset
The CQI Power Offset IE indicates Power offset used in the UL between the HS-DPCCH slots carrying CQI information and the associated DPCCH. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CQI Power Offset


INTEGER (0..8,..., 9..10)
According to mapping in ref. TS 25.213 [9] subclause 4.2.1.

9.2.2.4Cb	CQI Repetition Factor
The CQI Repetiton Factor IE indicates the number of consecutive repetitions of the CQI.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CQI Repetition Factor


INTEGER (1..4,...)
Step: 1

9.2.2.4D	DCH FDD Information
The DCH FDD Information IE provides information for DCHs to be established.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
DCH FDD Information

1..<maxNrOfDCHs>


–

>Payload CRC Presence Indicator
M

9.2.1.49

–

>UL FP Mode
M

9.2.1.66

–

>ToAWS
M

9.2.1.61

–

>ToAWE
M

9.2.1.60

–

>DCH Specific Info

1..<maxNrOfDCHs>


–

>>DCH ID
M

9.2.1.20

–

>>Transport Format Set 
M

9.2.1.59
For UL
–

>>Transport Format Set 
M

9.2.1.59
For DL
–

>>Allocation/Retention Priority
M

9.2.1.1A

–

>>Frame Handling Priority
M

9.2.1.30

–

>>QE-Selector
M

9.2.1.50A

–

>>Unidirectional DCH Indicator
O

9.2.1.68

YES
reject
>TNL QoS
O

9.2.1.58A

YES
ignore

Range Bound
Explanation
maxNrOfDCHs
Maximum number of DCHs for one UE

9.2.2.4E	DCHs FDD To Modify
The DCHs FDD To Modify IE provides information for DCHs to be modified.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
DCHs FDD To Modify

1..<maxNrOfDCHs>


–

>UL FP Mode
O

9.2.1.66

–

>ToAWS
O

9.2.1.61

–

>ToAWE
O

9.2.1.60

–

>Transport Bearer Request Indicator
M

9.2.1.62A

–

>DCH Specific Info

1..<maxNrOfDCHs>


–

>>DCH ID
M

9.2.1.20

–

>>Transport Format Set
O

9.2.1.59
For the UL.
–

>>Transport Format Set
O

9.2.1.59
For the DL.
–

>>Allocation/Retention Priority
O

9.2.1.1A

–

>>Frame Handling Priority
O

9.2.1.30

–

>>Unidirectional DCH Indicator
O

9.2.1.68

YES
reject
>TNL QoS
O

9.2.1.58A

YES
ignore

Range Bound
Explanation
maxNrOfDCHs
Maximum number of DCHs for one UE

9.2.2.4F	DCH Indicator For E-DCH-HSDPA Operation
The DCH Indicator For E-DCH-HSDPA Operation parameter indicates whether DCH Information IE should be ignored in the message in which the DCH Indicator For E-DCH-HSDPA Operation IE is included.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DCH Indicator For E-DCH-HSDPA Operation


ENUMERATED (DCH not present)


9.2.2.4G	Transport Bearer Not Requested Indicator
The Transport Bearer Not Requested Indicator parameter indicates that a transport bearer shall not be established or may not to be established for a DCH or an E-DCH MAC-d flow.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Transport Bearer Not Requested Indicator


ENUMERATED (Transport Bearer shall not be Established, Transport Bearer may not be Established)


9.2.2.4H	Transport Bearer Not Setup Indicator
The Transport Bearer Not Setup Indicator parameter indicates that a transport bearer will not be established for a DCH or an E-DCH MAC-d flow. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Transport Bearer Not Setup Indicator


ENUMERATED (Transport Bearer Not Setup)


9.2.2.5	D-Field Length
Void.
9.2.2.6	Dedicated Channels Capacity Consumption Law
Void.
9.2.2.7	Diversity Control Field
Void.
9.2.2.8	Diversity Indication
Void.
9.2.2.9	Diversity Mode
Define the diversity mode to be applied.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Diversity Mode


ENUMERATED (
None, 
STTD, 
Closed loop mode 1, 
Not Used,…)
The Diversity Mode IE shall never be set to "Not Used". If received it shall be rejected.

9.2.2.10	DL DPCH Slot Format
Indicates the slot format used in DPCH in DL, accordingly to ref. TS 25.211 [7].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL DPCH Slot Format


INTEGER (0..16,…,17..18)


9.2.2.10A	DL DPCH Timing Adjustment
The DL DPCH Timing Adjustment indicates that a timing adjustment of the related radio link is required or that an Initial DL DPCH Timing Adjustment has been performed by the Node B. It also indicates whether the timing adjustment consists of a timing advance or a timing delay with respect to the SFN timing. The adjustment always consists of 256 chips.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL DPCH Timing Adjustment


ENUMERATED (
timing advance, timing delay)
The size of the timing adjustment is 256 chips.

9.2.2.11	DL frame type
Void.
9.2.2.12	DL or Global Capacity Credit
Void.
9.2.2.12A	DL_power_averaging_window_size
The DL_power_averaging_window_size IE defines the window size when Limited Power Increase is used (TS 25.214 [10]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL_power_averaging_window_size


INTEGER (1..60)
Unit: inner loop power adjustments
Range: 1..60
Step: 1 adjustment

9.2.2.12B	DL Power Balancing Information
The DL Power Balancing Information IE provides information for power balancing to be activated in the relevant RL(s).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Power Adjustment Type
M

9.2.2.27

DL Reference Power
C-Common

DL Power
9.2.1.21
Power on DPCH or on F-DPCH
DL Reference Power Information
C-Individual
1..<maxNrOfRLs>


>RL ID
M

9.2.1.53

>DL Reference Power
M

DL Power
9.2.1.21
Power on DPCH or on F-DPCH
Max Adjustment Step
C-CommonOrIndividual

9.2.2.20

Adjustment Period
C-CommonOrIndividual

9.2.2.B

Adjustment Ratio
C-CommonOrIndividual

9.2.2.C


Condition
Explanation
Common
The IE shall be present if the Power Adjustment Type IE is set to "Common".
Individual
The IE shall be present if the Power Adjustment Type IE is set to "Individual".
CommonOrIndividual
The IE shall be present if the Power Adjustment Type IE is set to "Common" or 'Individual".

Range Bound
Explanation
maxNrOfRLs
Maximum number of Radio Links for a UE

9.2.2.12C	DL Power Balancing Activation Indicator
The DL Power Balancing Activation Indicator IE indicates that the power balancing is activated in the RL.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL Power Balancing Activation Indicator


ENUMERATED 
(DL Power Balancing Activated)


9.2.2.12D	DL Power Balancing Updated Indicator
The DL Power Balancing Updated Indicator IE indicates that the power balancing related parameters is updated in the RL.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL Power Balancing Updated Indicator


ENUMERATED (DL Power Balancing Updated)


9.2.2.13	DL Scrambling Code 
DL scrambling code to be used by the RL. One cell may have multiple DL scrambling codes available.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL Scrambling Code


INTEGER (0..15)
"0" = Primary scrambling code of the cell
"1".."15" = Secondary scrambling code

9.2.2.13A	DL TPC Pattern 01 Count
The DL TPC Pattern 01 Count IE contains the value of the parameter n, which is used for determining the DL TPC pattern on Radio Links marked with "first RLS" by the First RLS indicator IE before UL synchronisation is achieved.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL TPC Pattern 01 Count


INTEGER(0..30,…)


9.2.2.13B	DSCH FDD Information
Void.
9.2.2.13C	DPC Mode
The DPC Mode IE indicates the DPC mode to be applied TS 25.214 [10].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DPC Mode


ENUMERATED (
Mode0, 
Mode1,
…)
"Mode0": The Node B shall estimate the UE transmitted TPC command and update the DL power in every slot

"Mode1": The Node B shall estimate the UE transmitted TPC command  over three slots and shall update the DL power in every three slots

9.2.2.13D	DSCH FDD Common Information
Void.
9.2.2.13Da	E-DCH FDD Information
The E-DCH FDD Information IE provides information for an E-DCH to be established.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-DCH MAC-d Flows Information
M

9.2.2.13M

–

HARQ Process Allocation For 2ms Scheduled Transmission Grant
O

HARQ Process Allocation for 2ms TTI
9.2.2.13Dn
If this IE is not included, scheduled transmission in all HARQ processes is allowed.
–

E-DCH Maximum Bitrate 
O

9.2.2.13T

–

E-DCH Processing Overload Level
O

9.2.1.79

–

E-DCH Reference Power Offset
O

9.2.2.13Y

–

E-DCH Power Offset for Scheduling Info
O

9.2.1.85

YES
ignore
SixteenQAM UL Operation Indicator
O

9.2.2.88A

YES
reject
E-AGCH Table Choice
C- SixteenQAM UL Operation

9.2.2.100
If the SixteenQAM UL operation is not configured for this UE, Table 16B for E-AGCH in TS 25.212 [8] shall be used.
YES
ignore
SixtyfourQAM UL Operation Indicator
O

9.2.2.88C

YES
reject
UL MIMO Information
O

9.2.2.177

YES
reject
UPH Filtering Measurement Forwarding Request
O

ENUMERATED 
(Requested, Not Requested)

YES
reject

Condition
Explanation
SixteenQAM UL Operation
The IE shall be present if the SixteenQAM UL Operation Indicator IE is set to “Activate”.

9.2.2.13DA	E-DCH FDD Update Information
The E-DCH FDD Update Information IE provides information for E-DCH to be updated. At least one IE shall be present.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-DCH MAC-d Flow Specific Update Information

0..<maxNrOfEDCHMACdFlows>


–

>E-DCH MAC-d Flow ID
M

9.2.1.74

–

>HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant
O

HARQ Process Allocation for 2ms TTI
9.2.2.13Dn

–

HARQ Process Allocation For 2ms Scheduled Transmission Grant
O

HARQ Process Allocation for 2ms TTI
9.2.2.13Dn

–

E-DCH DL Control Channel Change Information

0..<maxnoofEDCHRLs>


GLOBAL
Ignore
>E-DCH RL ID
M

RL ID
9.2.1.53

–

TTI Update Indication
O

9.2.2.209

YES
reject

Range bound
Explanation
maxNrOfEDCHMACdFlows
Maximum number of MAC-d flows.
maxnoofEDCHRLs
Maximum number of E-DCH RLs for one UE

9.2.2.13Db	E-DCH FDD Information Response
The E-DCH FDD Information Response IE provides information for E-DCH MAC-d flows that have been established or modified. It also provides additional E-DCH information determined within the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-DCH MAC-d Flow Specific Information Response

0..<maxNrOfEDCHMACdFlows>


–

>E-DCH MAC-d Flow ID
M

9.2.1.74

–

>Binding ID
O

9.2.1.4

–

>Transport Layer Address
O

9.2.1.63

–

>HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant
O

HARQ Process Allocation for 2ms TTI
9.2.2.13Dn

–

>Transport Bearer Not Setup Indicator
O

9.2.2.4H

YES
ignore
HARQ Process Allocation For 2ms Scheduled Transmission Grant
O

HARQ Process Allocation for 2ms TTI
9.2.2.13Dn

–

Fast TTI switching Mode Supported
O

9.2.2.211

YES
ignore

Range bound
Explanation
maxNrOfEDCHMACdFlows
Maximum number of MAC-d flows.

9.2.2.13Dc	E-DCH FDD DL Control Channel Information
The E-DCH FDD DL Control Channel Information IE provides information for E-DCH specific DL Control Channels to be provided to UE via RRC signalling.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-AGCH And E-RGCH/E-HICH FDD Scrambling Code
O

DL Scrambling Code 
9.2.2.13
Scrambling code on which E-AGCH, E-RGCH and E-HICH are transmitted.
–

E-AGCH Channelisation Code
O

FDD DL Channelisation Code Number
9.2.2.14

–

Primary E-RNTI
O

E-RNTI 
9.2.1.75

–

Secondary E-RNTI
O

E-RNTI 
9.2.1.75

–

E-RGCH/E-HICH Channelisation Code
O

FDD DL Channelisation Code Number
9.2.2.14

–

E-RGCH Signature Sequence
O

INTEGER (0.. maxNrofSigSeqRGHI-1)

–

E-HICH Signature Sequence
O

INTEGER (0.. maxNrofSigSeqRGHI-1)

–

Serving Grant Value
O

INTEGER (0..37,38)
(0..37) indicates E-DCH serving grant index as defined in TS 25.321 [32]; index 38 means zero grant
–

Primary/Secondary Grant Selector
O

ENUMERATED (Primary, Secondary)
Indicates whether the Serving Grant Value is granted with a primary E-RNTI or a secondary E-RNTI
–

E-RGCH Release Indicator
O

9.2.2.13Ic

–

Default Serving Grant in DTX Cycle 2
O

INTEGER (0..37,38)
Serving Grant value to be used in DTX-Cycle-2.
(0..37) indicates E-DCH serving grant index as defined in TS 25.321 [32]; index 38 means zero grant
YES
ignore
UL MIMO DL Control Channel information
O

9.2.2.180

YES
ignore

Range bound
Explanation
maxNrofSigSeqRGHI
Maximum number of Signature Sequences for E-RGCH/E-HICH.

9.2.2.13De	E-DCH RL Indication
Indicates whether a RL is an E-DCH RL.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH RL Indication


ENUMERATED(E-DCH, non E-DCH)


9.2.2.13Df	E-DCH FDD Information to Modify
The E-DCH FDD Information to Modify IE is used for the modification of an E-DCH. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-DCH MAC-d Flow Specific Information

0..<maxNrOfEDCHMACdFlows>


–

>E-DCH MAC-d Flow ID
M

9.2.1.74

–

>Allocation/Retention Priority
O

9.2.1.1A

–

>Transport Bearer Request Indicator
M

9.2.1.62A

–

>TNL QoS
O

9.2.1.58A

–

>Maximum Number Of Retransmissions For E-DCH
O

9.2.1.81

–

>E-DCH HARQ Power Offset FDD
O

9.2.2.13Dk

–

>E-DCH MAC-d Flow Multiplexing  List
O

9.2.1.69

–

>CHOICE E-DCH Grant Type
O



–

>>E-DCH Non-Scheduled Transmission  Grant






>>>Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission
M

9.2.2.13Dm
If the Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission IE is present, this IE shall be ignored. 
When Maximum MAC-d PDU Size Extended IE is configured for an E-DCH Logical Channel this IE indicates the maximum number of bits per MAC-i PDU.
–

>>>HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant
O

HARQ Process Allocation for 2ms TTI
9.2.2.13Dn

–

>>>Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission
O

9.2.2.13Dr
When Maximum MAC-d PDU Size Extended IE is configured for an E-DCH Logical Channel this IE indicates the extended maximum number of bits per MAC-i PDU.
YES
reject
>>E-DCH Scheduled Transmission Grant


NULL



>Bundling Mode Indicator
O

9.2.2.1Bb

–

>E-DCH Logical Channel To Add
O

E-DCH Logical Channel Information
9.2.1.71

–

>E-DCH Logical Channel To Modify
O

9.2.1.72

–

>E-DCH Logical Channel To Delete

0..<maxnooflogicalchannels>


–

>>Logical Channel ID
M

9.2.1.80

–

HARQ Process Allocation For 2ms Scheduled Transmission Grant
O

HARQ Process Allocation for 2ms TTI
9.2.2.13Dn

–

E-DCH Maximum Bitrate
O

9.2.2.13T

–

E-DCH Processing Overload Level
O

9.2.1.79

–

E-DCH Reference Power Offset
O

9.2.2.13Y

–

MAC-e Reset Indicator
O

9.2.1.83

–

E-DCH Power Offset for Scheduling Info
O

9.2.1.85

YES
ignore
SixteenQAM UL Operation Indicator
O

9.2.2.88A

YES
reject
E-DCH MAC-d PDU Size Format 
O

9.2.1.74B

YES
reject
E-DCH DL Control Channel Grant Information

0..<maxnoofEDCHRLs>


GLOBAL
ignore
>E-DCH RL ID
M

RL ID
9.2.1.53

–

E-AGCH Table Choice
C- SixteenQAM UL Operation

9.2.2.100
If sixteenQAM UL operation is not used in the new configuration for this UE, Table 16B for E-AGCH in TS 25.212 [8] shall be used in the new configuration.
YES
ignore
SixtyfourQAM UL Operation Indicator
O

9.2.2.88C

YES
reject
UL MIMO Reconfiguration
O

9.2.2.176

YES
reject
Fast TTI switching Mode Requested Synchronized
O

9.2.2.212

YES
reject
Fast TTI switching Mode Requested UnSynchronized
O

9.2.2.213

YES
reject

Condition
Explanation
SixteenQAM UL Operation
The IE shall be present if the SixteenQAM UL Operation Indicator IE is set to “Activate”.

Range bound
Explanation
maxNrOfEDCHMACdFlows
Maximum number of E-DCH MAC-d flows.
maxnooflogicalchannels
Maximum number of logical channels
maxnoofEDCHRLs
Maximum number of E-DCH RLs for one UE

9.2.2.13Dh	E-DCH Transport Format Combination Set Information (E-TFCS Information)
Whereas the related Transport Block sizes are standardised in TS 25.321 [32] this IE gives details on the referenced Transport Block Size Table, the E-DCH Minimum Set E-TFCI, the Reference E-TFCIs and configuration parameters used for the calculation of the gain factors dec and  ed defined in TS 25.214 [10].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-TFCI Table Index
M

INTEGER (0..1,..., 2..7)
Indicates which standardised E-TFCS Transport Block Size Table shall be used. The related tables are specified in TS 25.321 [32].
–

E-DCH Minimum Set E-TFCI
O

INTEGER (0..127)
For the concept of "E-DCH Minimum Set of TFCs" see TS 25.321 [32] and TS 25.331 [18].
–

Reference E-TFCI Information

1..<maxnoofRefETFCIs>


–

>Reference E-TFCI
M

INTEGER (0..127)

–

>Reference E-TFCI Power Offset
M

9.2.2.13Dp
If the Extended Reference E-TFCI Power Offset IE is present, this IE shall be ignored
–

>Extended Reference E-TFCI Power Offset
O

9.2.2.13Dq

YES
reject
E-TFCI Boost Information
O

9.2.2.88B

YES
reject
E-DPDCH Power Interpolation
O

BOOLEAN
True means that the E-DPDCH power interpolation formula shall be applied,
False means that the E-DPDCH power extrapolation formula shall be applied
for the computation of the gain factor ged  according to TS 25.214 [10]
YES
reject

Range Bound
Explanation
maxnoofRefETFCIs
Maximum number of signalled reference E-TFCIs

9.2.2.13Di	E-TTI
The E-TTI parameter indicates the Transmission Time Interval for E-DPCH operation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-TTI


ENUMERATED (2ms, 10ms)


9.2.2.13Dj	E-DPCCH Power Offset
The E-DPCCH Power Offset is used to calculate the E-DPCCH gain factor Eec as defined in TS 25.214 [10], whereas  ec is related to the power difference between DPCCH and E-DPCCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DPCCH Power Offset


INTEGER (0..8)
According to mapping in ref. TS 25.213 [9] subclause 4.2.1.3.

9.2.2.13Dk	E-DCH HARQ Power Offset FDD
The E-DCH HARQ Power Offset FDD is used to calculate the unquantised gain factor for an E-TFC (Ted,j,uq)as defined in TS 25.214 [10].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH HARQ Power Offset FDD


INTEGER (0..6)
According to mapping in ref. TS 25.213 [9] subclause 4.2.1.3.

9.2.2.13Dl	E-DCH MAC-d Flow Multiplexing List
Void.
9.2.2.13Dm	Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission
The Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission indicates the number of bits allowed to be included in a MAC-e (or MAC-i) PDU per E-DCH MAC-d flow configured for non-scheduled transmissions. If the range of the Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission IE is insufficient to represent the value to be sent to the Node B, the Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission IE shall be used to represent the value to be sent to the Node B, see section 9.2.2.13Dr.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission


INTEGER (1..19982)


9.2.2.13Dn	HARQ Process Allocation For 2ms TTI
The HARQ Process Allocation for 2ms TTI indicates those HARQ processes that are allowed. MAC-d PDU’s for a MAC-d flow are only allowed to be transmitted in those processes for which the bit is set to "1".
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HARQ Process Allocation For 2ms TTI


BIT STRING (SIZE(8))
The first Bit corresponds to HARQ process ID = 0,
the second  bit corresponds to HARQ process ID = 1,
etc.
The HARQ process ID for 2ms TTI is defined in TS 25.321 [32], chapter 11.8.1.3.

9.2.2.13Dp	Reference E-TFCI Power Offset
The Reference E-TFCI Power Offset is used to calculate the reference E-TFC gain factor Eed,ref as defined in TS 25.214 [10]. If the range of the Reference E-TFCI Power Offset IE is insufficient to represent the value to be sent to the Node B, the Extended Reference E-TFCI Power Offset IE shall be used to represent the value to be sent to the Node B, see section 9.2.2.13Dq.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Reference E-TFCI Power Offset


INTEGER (0..29)
According to mapping in ref. TS 25.213 [9] subclause 4.2.1.3

9.2.2.13Dq	Extended Reference E-TFCI Power Offset
The Extended Reference E-TFCI Power Offset IE shall be used if the range of the Reference E-TFCI Power Offset IE (see section 9.2.2.13Dp) is insufficient to represent the value of the Reference E-TFCI Power Offset to be sent to the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Extended Reference E-TFCI Power Offset


INTEGER (30..31,…)
According to mapping in ref. TS 25.213 [9] subclause 4.2.1.3

9.2.2.13Dr	Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission
The Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission IE shall be used if the range of the Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission IE (see section 9.2.2.13Dm) is insufficient to represent the value of the Maximum Number of Bits per MAC-e (or MAC-i) PDU for Non-scheduled Transmission to be sent to the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission


INTEGER (19983..22978,…,22979..34507)


9.2.2.13E	Enhanced DSCH PC
Void.
9.2.2.13F	Enhanced DSCH PC Counter
Void.
9.2.2.13G	Enhanced DSCH PC Indicator
Void.
9.2.2.13H	Enhanced DSCH PC Wnd
Void.
9.2.2.13I	Enhanced DSCH Power Offset
Void.
9.2.2.13Ia	E- RGCH/E-HICH FDD Code Information
This parameter defines the codes which will be assigned for E- RGCH and E-HICH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE replaceremove
M



>replace




>>E-RGCH/E-HICH Code

1..<MaxNrOfE-RGCHs-E-HICHs>


>>>Code Number
M

FDD DL Channelisation Code Number
9.2.2.14

>remove


NULL


Range Bound
Explanation
MaxNrOfE-RGCHs-E-HICHs
Maximum number of E-RGCH/E-HICH channelisation codes for one cell.

9.2.2.13Ib	E- AGCH FDD Code Information
This parameter defines the codes which will be assigned for E- AGCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE replaceremove
M



>replace




>>E-AGCH Code

1..<MaxNrOfEAGCHs>


>>>Code Number
M

FDD DL Channelisation Code Number
9.2.2.14

>remove


NULL


Range Bound
Explanation
MaxNrOfEAGCHs
Maximum number of E-AGCH chanellisation codes for one cell.

9.2.2.13Ic	E-RGCH Release Indicator
Indicates the E-RGCH is released.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-RGCH Release Indicator


ENUMERATED (E-RGCH released)


9.2.2.13Id	E-AGCH Power Offset
The E-AGCH Power Offset IE indicates the Power offset relative to the pilot bits on the DL DPCCH except when F-DPCH is configured. When F-DPCH is configured, the E-AGCH Power Offset IE indicates the Power offset relative to the power of transmitted TPC bits on the F-DPCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-AGCH Power Offset


INTEGER (0…255,…)
Unit: dB
Range: -32 .. +31.75 dB
Step: 0.25 dB

9.2.2.13Ie	E-RGCH Power Offset
The E-RGCH Power Offset IE indicates the Power offset relative to the pilot bits on the DL DPCCH except when F-DPCH is configured. When F-DPCH is configured, the E-RGCH Power Offset IE indicates the Power offset relative to the power of transmitted TPC bits on the F-DPCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-RGCH Power Offset


INTEGER (0…255,…)
Unit: dB
Range: -32 .. +31.75 dB
Step: 0.25 dB

9.2.2.13If	E-HICH Power Offset
The E-HICH Power Offset IE indicates the Power offset relative to the pilot bits on the DL DPCCH except when F-DPCH is configured. When F-DPCH is configured, the E-HICH Power Offset IE indicates the Power offset relative to the power of transmitted TPC bits on the F-DPCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-HICH Power Offset


INTEGER (0…255,…)
Unit: dB
Range: -32 .. +31.75 dB
Step: 0.25 dB

9.2.2.13Ig	E-RGCH 2-Index-Step Threshold
The E-RGCH 2-index-step Threshold IE is used to determine the Serving Grant.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-RGCH 2-Index-Step Threshold


 INTEGER
(0..37)
Refers to an index in the "SG-Table" (see TS 25.321 [32]).

9.2.2.13Ih	E-RGCH 3-Index-Step Threshold
The E-RGCH 3-index-step Threshold IE is used to determine the Serving Grant.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-RGCH 3-Index-Step Threshold


 INTEGER
(0..37)
Refers to an index in the "SG-Table" (see TS 25.321 [32]).

9.2.2.13J	E-DCH Capability
Void
9.2.2.13Ja	E-DCH Capacity Consumption Law
The capacity consumption law indicates to the CRNC how the Capacity Credit is consumed by NBAP set of procedures, depending on the RL/RLS situation and the number of uplink E-DPDCHs and their spreading factors. The reference spreading factor and number of E-DPDCH is signalled using the Maximum Set of E-DPDCHs IE.
This capacity consumption law indicates the consumption law to be used with the following procedures :
-	Radio Link Setup
-	Radio Link Addition
-	Radio Link Reconfiguration
-	Radio Link Deletion
For the Radio Link Setup and Radio Link Addition procedures, the cost given in the consumption law shall be debited from the Capacity Credit, whereas it shall credited to the Capacity Credit for the Radio Link Deletion procedure. For the Radio Link Reconfiguration procedure, the difference of the consumption cost for the new spreading factor and the consumption cost for the old spreading factor shall be debited from the Capacity Credit (or credited when this difference is negative).
If the modelling of the internal resource capability of the Node B is modelled independently for the Uplink and Downlink, the DL cost shall be applied to the DL or Global Capacity Credit and the UL Cost shall be applied to the UL Capacity Credit. If it is modelled as shared resources, both the DL costs and the UL costs shall be applied to the DL or Global Capacity Credit.
For a Radio Link creating a Radio Link Set (first RL of a RLS), the cost for the RL (cost 2) and RLS (cost 1) shall be taken into account. When adding a Radio Link to a Radio Link Set, only the RL cost (cost 2) shall be taken into account.
In the case where multiple Radio Links are established in one procedure, for every created Radio Link Set, the first Radio Link is always the Radio Link with the lowest repetition number.
The costs given in the consumption law are the costs per channelization code/no of E-DPDCH. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SF Allocation Law

1..<maxNrOfCombEDPDCH>

The cost of SF allocation: the first instance corresponds to v2xN2plus2xN4, the second to v2xN2, the third to v2xN4, the fourth to vN4, the fifth to vN8, the sixth to vN16, the seventh to vN32 ,the eighth to vN64, the ninth to vN128,the tenth to vN256 and the eleventh to v2xM2plus2xM4.
>UL Cost 1
M

INTEGER (0..65535)
This is the cost of a RLS
>UL Cost 2
M

INTEGER (0..65535)
This is the cost of a RL
DL Cost 1
O

INTEGER (0..65535)
This is the cost of a RLS. If not present, zero cost shall be applied. .
DL Cost 2
O

INTEGER (0..65535)
This is the cost of a RL. If not present, zero cost shall be applied. 

Range Bound
Explanation
maxNrOfCombEDPDCH
Maximum number of Configurations in the Maximum Set of E-DPDCH IE

9.2.2.13K	E-DCH Logical Channel Information
Void
9.2.2.13L	E-DCH Logical Channel To Modify
Void
9.2.2.13M	E-DCH MAC-d Flows Information
The E-DCH MAC-d Flows Information IE is used for the establishment of E-DCH MAC-d flows.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-DCH MAC-d Flow Specific Information

1..<maxNrOfEDCHMACdFlows>


–

>E-DCH MAC-d Flow ID
M

9.2.1.74

–

>Allocation/Retention Priority
M

9.2.1.1A

–

>TNL QoS
O

9.2.1.58A

–

>Payload CRC Presence Indicator
M

9.2.1.49

–

>Maximum Number Of Retransmissions For E-DCH
M

9.2.1.81

–

>E-DCH HARQ Power Offset FDD
M

9.2.2.13Dk

–

>E-DCH MAC-d Flow Multiplexing List
O

9.2.1.69

–

>CHOICE E-DCH Grant Type
M



–

>>E-DCH Non-Scheduled Transmission Grant






>>>Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission
M

9.2.2.13Dm
If the Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission IE is present, this IE shall be ignored.
When Maximum MAC-d PDU Size Extended IE is configured for an E-DCH Logical Channel this IE indicates the maximum number of bits per MAC-i PDU.
–

>>>HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant
O

HARQ Process Allocation for 2ms TTI
9.2.2.13Dn
If this IE is not included, transmission in all HARQ processes is allowed.
–

>>>Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission
O

9.2.2.13Dr
When Maximum MAC-d PDU Size Extended IE is configured for an E-DCH Logical Channel this IE indicates the extended maximum number of bits per MAC-i PDU.
YES
reject
>>E-DCH Scheduled Transmission Grant


NULL



>Bundling Mode Indicator
O

9.2.2.1Bb

–

>E-DCH Logical Channel Information
M

9.2.1.71

–

>Transport Bearer Not Requested Indicator
O

9.2.2.4G

YES
ignore

Range Bound
Explanation
maxNrOfEDCHMACdFlows
Maximum number of E-DCH MAC-d flows

9.2.2.13N	E-DCH MAC-d Flows To Delete
Void
9.2.2.13O	E-DCH MAC-d Flow ID
Void
9.2.2.13P	E-RNTI
Void
9.2.2.13Q	E-DCH DDI Value
Void
9.2.2.13R	E-DCH Provided Bit Rate Value
Void
9.2.2.13S	E-DCH Provided Bit Rate Value Information
Void
9.2.2.13T	E-DCH Maximum Bitrate
The E-DCH Maximum Bitrate parameter indicates the Maximum Bitrate for an E-DCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH Maximum Bitrate


INTEGER (0..5742,…, 5743..11498, 11499..34507)
Bitrate on transport block level. Unit is kbits per second. 

9.2.2.13U	E-DCH Processing Overload Level
Void
9.2.2.13V	E-DCH TTI2ms Capability
This parameter defines the E-DCH TTI Capability for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH TTI2ms Capability 


BOOLEAN
True = TTI 10ms and 2ms supported for E-DCH
False = only TTI 10ms supported for E-DCH

9.2.2.13W	E-DCH SF Capability
This parameter defines the E-DCH Capability for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH SF Capability


ENUMERATED (sf64, sf32, sf16, sf8, sf4, 2sf4, 2sf2, 2sf2and2sf4,…)
Min SF supported by the cell in E-DCH

9.2.2.13X	E-DCH HARQ Combining Capability
This parameter defines the E-DCH HARQ Combining capability for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH HARQ Combining Capability


ENUMERATED (IR Combining Capable, Chase Combining Capable, IR and Chase Combining Capable)


9.2.2.13Y	E-DCH Reference Power Offset
The E-DCH Reference Power Offset is used to estimate the E-DPDCH power from E-TFCI without decoding MAC-e PDUs.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH Reference Power Offset 


INTEGER (0..6)
According to mapping in ref. TS 25.213 [9] subclause 4.2.1.3.

9.2.2.13Z	E-DCH Power Offset for Scheduling Info
Void
9.2.2.14	FDD DL Channelisation Code Number
The DL Channelisation Code Number indicates the DL Channelisation Code number for a specific DL physical channel.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
FDD DL Channelisation Code Number


INTEGER (0..511)
According to the mapping in TS 25.213 [9].
The maximum value is equal to the DL spreading factor –1.

9.2.2.14A	FDD DL Code Information
The FDD DL Code Information IE provides DL Code information for the RL.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
FDD DL Code Information

1..<maxnoofCodes>


>DL Scrambling Code 
M

9.2.2.13

>FDD DL Channelisation Code Number
M

9.2.2.14

>Transmission Gap Pattern Sequence Code Information
O

9.2.2.53B


Range Bound
Explanation
maxnoofCodes
Maximum number of DL code information

9.2.2.14B	FDD S-CCPCH Frame Offset
The FDD S-CCPCH Frame Offset IE represents a frame offset between the concerned S-CCPCH’s CFN (Connection Frame Number) relatively to the P-CCPCH’s SFN (System Frame Number) of the respective cell. The FDD S-CCPCH Frame Offset IE shall be the constant difference between the S-CCPCH’s CFN and the least significant 8 bits of the SFN (System Frame Number) on Uu.

IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
FDD S-CCPCH Frame Offset


ENUMERATED 
(1, 2, 4,…)
Offset in frames (corresponding to 10msec, 20msec or 40msec offset in time)

9.2.2.15	FDD SCCPCH Offset
The Secondary CCPCH offset is defined as the time offset towards the Primary CCPCH in the cell. The offset is a multiple of 256 chips.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
FDD SCCPCH Offset


INTEGER (0..149)
Unit: chip
Range: 0..38144 chips
Step: 256 chips
See ref. TS 25.211 [7]

9.2.2.16	FDD TPC DL Step Size
This parameter indicates step size for the DL power adjustment.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
FDD TPC Downlink Step Size


ENUMERATED 
(0.5, 1, 1.5, 2,…)
Unit: dB

9.2.2.16a	F-DPCH Capability
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
F-DPCH Capability


ENUMERATED (F-DPCH Capable, F-DPCH Non-Capable)


9.2.2.16A	First RLS Indicator
The First RLS Indicator IE indicates if a specific Radio Link and all Radio Links which are part of the same Radio Link Set, shall be considered as the first radio links established towards the UE or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
First RLS Indicator


ENUMERATED (
First RLS, 
Not First RLS,
…)


9.2.2.17	Gap Period
Void.
9.2.2.18	Gap Position Mode
Void.
9.2.2.18a	HARQ Preamble Mode
The HARQ Preamble Mode IE is used as described as in ref TS 25.214 [10].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HARQ Preamble Mode


ENUMERATED (
mode0, 
mode1)
"mode0" means HARQ Preamble Mode =0
"mode1" means HARQ Preamble Mode =1 

9.2.2.18b	HARQ Preamble Mode Activation Indicator
The HARQ Preamble Activation Indicator indicates if the configured HARQ Preamble Mode has been activated in the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HARQ Preamble Mode Activation Indicator


ENUMERATED(HARQ Preamble Mode Activated).


9.2.2.18ba	HARQ Info for E-DCH
The E-DCH HARQ Info is used to indicate the use of redundancy version (RV) for the EDCH HARQ transmissions.
IE/Group name
Presence
Range
IE Type and Reference
Semantics description
HARQ Info for E-DCH


ENUMERATED (rv0, rvtable)
"rv0"  indicates that  the UE will only use E_DCH RV index 0.
"rvtable" indicates that  the UE will use an RSN based RV index as specified in TS 25.212 [8]

9.2.2.18c	Logical channel ID
Void
9.2.2.18A	Limited Power Increase
The parameter is used for a more efficient use of the inner loop DL power control for non real time data.
If the limited power increase is used, the Node B shall use the limited power increase algorithm as specified in TS 25.214 [10], subclause 5.2.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Limited Power Increase


ENUMERATED (
Used, 
Not Used )


9.2.2.18B	Inner Loop DL PC Status
The Inner Loop DL PC Status IE indicates whether inner loop DL control shall be active or inactive for all radio links associated with the context identified by the Node B Communication Context Id IE.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Inner Loop DL PC Status


ENUMERATED (
Active,
Inactive)


9.2.2.18C	IPDL FDD Parameters
The IPDL FDD Parameters IE provides information about IPDL to be applied for FDD when activated.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
IP SpacingFDD
M

ENUMERATED 
(5, 7, 10, 15, 20, 30, 40, 50,…)
See TS 25.214 [10]
IP Length
M

ENUMERATED 
(5, 10)
See TS 25.214 [10]
Seed
M

INTEGER (0..63)
See TS 25.214 [10]
Burst Mode Parameters
O

9.2.1.5A

IP Offset
M

INTEGER (0..9)
See TS 25.214 [10]

9.2.2.18Ca	HS-DSCH configured indicator
The HS-DSCH Configured Indicator IE indicates the configuration of HS-DSCH for the UE. The HS-DSCH Configured Indicator IE shall be used for the configuration of the E-DPDCH IQ branch mapping (TS 25.213 [9]). 
IE/Group Name
Presence
Range
IE type and reference
Semantics description
HS-DSCH Configured Indicator


ENUMERATED (HS-DSCH configured, HS-DSCH not configured)
Indicator of the HS-DSCH forconfiguration of the E-DPDCHs IQ branch mapping (TS 25.213 [9]).

9.2.2.18D	HS-DSCH FDD Information
The HS-DSCH FDD Information IE is used for initial addition of HS-DSCH information to a Node B Communication Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-DSCH MAC-d Flows Information
M

9.2.1.31IA

–

UE Capabilities Information

1


–

>HS-DSCH Physical Layer Category
M

9.2.1.31Ia

–

>1.28 Mcps TDD Uplink Physical Channel Capability
O

9.2.3.5Gc
Not to be used. 
YES
ignore
>Number of Supported Carriers
O

ENUMERATED (
One-one carrier, One-three carrier, Three-three carrier, One-six carrier,
Three-six carrier,
Six-six carrier, ..., One-Two carrier Discontiguous, Two-Two carrier Discontiguous, One-Two carrier Contiguous, Two-Two carrier Contiguous)
Not to be used.
YES
reject
>Multi-carrier HS-DSCH Physical Layer Category
O

9.2.1.31Ia
Not to be used.
YES
ignore
>UE RF Band Capability LCR
C-NofSupportedCarriers

9.2.3.125
Not to be used.
YES
ignore
MAC-hs Reordering Buffer Size for RLC-UM
M

9.2.1.38Ab

–

CQI Feedback Cycle k
M

9.2.2.21B

–

CQI Repetition Factor
C-CQICyclek

9.2.2.4Cb

–

ACK-NACK Repetition Factor
M

9.2.2.a

–

CQI Power Offset 
M

9.2.2.4Ca

–

ACK Power Offset
M

9.2.2.b

–

NACK Power Offset
M

9.2.2.23a

–

HS-SCCH Power Offset
O

9.2.2.18I

–

Measurement Power Offset
O

9.2.2.21C

–

HARQ Preamble Mode
O

9.2.2.18a

YES
ignore
MIMO Activation Indicator
O

9.2.1.119

YES
reject
HS-DSCH MAC-d PDU Size Format 
O

9.2.1.31ID
If not present, "Indexed MAC-d PDU Size" shall be used.
YES
reject
Sixtyfour QAM Usage Allowed Indicator
O

9.2.2.74A

YES
ignore
UE with enhanced HS-SCCH support indicator
O

NULL
UE supports enhanced HS-SCCH functionality:
- UE supports different HS-SCCH in consecutive TTIs and
- in HS-SCCH-less operation mode the UE supports HS-SCCH orders
YES
ignore
Enhanced HS Serving CC Abort
O

ENUMERATED (Abort Enhanced HS Serving CC, …)
Shall be ignored in Radio Link Setup and Radio Link Addition procedures. 
YES
reject
UE Support Indicator Extension
O

9.2.2.117

YES
ignore
Single Stream MIMO Activation Indicator
O

9.2.2.123

YES
reject
Puncturing Handling in First Rate Matching Stage
O

9.2.2.149

YES
ignore
MIMO with four transmit antennas Activation Indicator
O

9.2.2.164

YES
reject
Dual Stream MIMO with four transmit antennas Activation Indicator
O

9.2.2.167

YES
reject
Multiflow Information
O

9.2.2.170
For FDD only
YES
reject
CQI Feedback Cycle2 k
O

CQI Feedback Cycle k2
9.2.2.206
For FDD only
YES
ignore
CQI Cycle Switch Timer
O

ENUMERATED (v4, v8, v16, v32, v64, v128, v256, v512, Infinity)
For FDD only, refer to TS 25.331 [16].
YES
ignore

Condition
Explanation
CQICyclek
The IE shall be present if the CQI Feedback Cycle k IE is set to a value greater than 0.

9.2.2.18Da	HS-DSCH FDD Secondary Serving Information
The HS-DSCH FDD Secondary Serving Information IE is used for initial addition of Secondary Serving HS-DSCH information to a Node B Communication Context and defines the cell specific parameters for the secondary serving HS-DSCH Radio Link.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-SCCH Power Offset
O

9.2.2.18I

-

Measurement Power Offset
M

9.2.2.21C

-

Sixtyfour QAM Usage Allowed Indicator
O

9.2.2.74A

-

HS-DSCH RNTI
M

9.2.1.31J

-

MIMO Activation Indicator
O

9.2.1.119

YES
reject
Single Stream MIMO Activation Indicator 
O

9.2.2.123

YES
reject
Diversity Mode
O

9.2.2.9
If Diversity mode = "Closed loop mode 1" the procedure shall be rejected 
YES
reject
Transmit Diversity Indicator
O

9.2.2.53

YES
reject
Ordinal Number Of Frequency
O

INTEGER (1..32,...)
Value = "1" indicates 1st secondary serving HS-DSCH cell, Value = "2" indicates 2nd secondary serving HS-DSCH cell etc. TS 25.214 [10].
The IE shall be ignored by the Node B if the new configuration contains one secondary serving radio link.
YES
reject
MIMO with four transmit antennas Activation Indicator
O

9.2.2.164

YES
reject
Dual Stream MIMO with four transmit antennas Activation Indicator
O

9.2.2.167

YES
reject
Multiflow Ordinal Number Of Frequency
O

INTEGER (1..32,...)
In intra-Node B multiflow case, the Value specifies the index of the secondary serving or assisting serving or assisting secondary serving HS-DSCH cell for the UL HS-DPCCH as specified in TS 25.212 [8].
In inter-Node B multiflow case, if present, the Value must be “1” when there is one secondary serving HS-DSCH cell. Otherwise the Value specifies the index of this cell for the UL HS-DPCCH as specified in TS 25.212 [8].
YES
reject

9.2.2.18E	HS-DSCH FDD Information Response
The HS-DSCH Information Response provides information for HS-DSCH that have been established or modified. It also provides additional HS-DSCH information determined within the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-DSCH MAC-d Flow Specific Information Response

0..<maxNrOfMACdFlows>


–

>HS-DSCH MAC-d Flow ID
M

9.2.1.31I

–

>Binding ID
O

9.2.1.4

–

>Transport Layer Address
O

9.2.1.63

–

>HS-DSCH Initial Capacity Allocation
O

9.2.1.31Ha

–

HS-SCCH Specific Information Response

0..<maxNrOfHSSCCHCodes>


–

>Code Number
M

INTEGER (0..127)

–

HARQ Memory Partitioning 
O

9.2.1.102

–

HARQ Preamble Mode Activation Indicator
O

9.2.2.18b

YES
ignore
MIMO N/M Ratio
O

9.2.2.96

YES
ignore
SixtyfourQAM DL Usage Indicator
O

9.2.2.74B

YES
ignore
HS-DSCH TB Size Table Indicator
O

9.2.2.18Ee

YES
ignore
Support of dynamic DTXDRX related HS-SCCH order
O

9.2.2.150

YES
ignore
Precoder weight set restriction
O

9.2.2.192

YES
ignore

Range Bound
Explanation
maxNrOfMACdFlows
Maximum number of HS-DSCH MAC-d flows
maxNrOfHSSCCHCodes
Maximum number of HS-SCCH codes

9.2.2.18EA	HS-DSCH FDD Secondary Serving Information Response
The HS-DSCH Secondary Serving Information Response provides information for Secondary Serving HS-DSCH that have been established or modified. It also provides additional HS-DSCH information determined within the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-SCCH Specific Secondary Serving Information Response

0..<maxNrOfHSSCCHCodes>




>Code Number
M

INTEGER (0..127)



SixtyfourQAM DL Usage Indicator
O

9.2.2.74B



HS-DSCH TB Size Table Indicator
O

9.2.2.18Ee



MIMO N/M Ratio
O

9.2.2.96

YES
ignore
Precoder weight set restriction
O

9.2.2.192

YES
ignore

Range Bound
Explanation
maxNrOfHSSCCHCodes
Maximum number of HS-SCCH codes

9.2.2.18EB	HS-DSCH FDD Secondary Serving Information To Modify
The HS-DSCH FDD Secondary Serving Information To Modify IE is used for modification of Secondary Serving HS-DSCH information in a Node B Communication Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-SCCH Power Offset
O

9.2.2.18I

-

Measurement Power Offset
O

9.2.2.21C

-

HS-SCCH Code Change Grant
O

9.2.1.31L

-

Sixtyfour QAM Usage Allowed Indicator
O

9.2.2.74A

-

MIMO Mode Indicator
O

9.2.1.120

YES
reject
Single Stream MIMO Mode Indicator
O

9.2.2.124

YES
reject
Diversity Mode
O

9.2.2.9
If Diversity mode = "Closed loop mode 1" the procedure shall be rejected
YES
reject
Transmit Diversity Indicator
C-DiversityMode

9.2.2.53

YES
reject
Non Cell Specific Tx Diversity
O

ENUMERATED (Tx Diversity, ...)
Value = "Tx Diversity":
Diversity Mode and Transmit Diversity Indicator shall be non cell specific.
YES
reject
Ordinal Number Of Frequency
O

INTEGER (1..32,...)
Value = "1" indicates 1st secondary serving HS-DSCH cell, Value = "2" indicates 2nd secondary serving HS-DSCH cell etc. TS 25.214 [10].
The IE shall be ignored by the Node B if the new configuration contains one secondary serving radio link.
YES
reject
MIMO with four transmit antennas Mode Indicator
O

9.2.2.166
For FDD only
YES
reject
Dual Stream MIMO with four transmit antennas Mode Indicator
O

9.2.2.168
For FDD only
YES
reject
Multiflow Ordinal Number Of Frequency
O

INTEGER (1..32,...)
In intra-Node B multiflow case, the Value specifies the index of the secondary serving or assisting serving or assisting secondary serving HS-DSCH cell for the UL HS-DPCCH as specified in TS 25.212.
In inter-Node B multiflow case, if present, the Value must be “1” when there is one secondary serving HS-DSCH cell. Otherwise the Value specifies the index of this cell for the UL HS-DPCCH as specified in [8].
YES
reject

Condition
Explanation
DiversityMode
The IE shall be present if Diversity Mode IE is is present and not set to "None". 

9.2.2.18EC	HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised
The HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE is used for modification of Secondary Serving HS-DSCH information in a Node B Communication Context with the Unsynchronised Radio Link Reconfiguration procedure.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-SCCH Power Offset
O

9.2.2.18I

-

Sixtyfour QAM Usage Allowed Indicator
O

9.2.2.74A

-

MIMO Mode Indicator
O

9.2.1.120

YES
reject
Single Stream MIMO Mode Indicator
O

9.2.2.124

YES
reject
Ordinal Number Of Frequency
O

INTEGER (1..32,...)
Value = "1" indicates 1st secondary serving HS-DSCH cell, Value = "2" indicates 2nd secondary serving HS-DSCH cell etc. TS 25.214 [10].
The IE shall be ignored by the Node B if the new configuration contains one secondary serving radio link.
YES
reject
MIMO with four transmit antennas Mode Indicator
O

9.2.2.166
For FDD only

YES
reject
Dual Stream MIMO with four transmit antennas Mode Indicator
O

9.2.2.168
For FDD only

YES
reject
Multiflow Ordinal Number Of Frequency
O

INTEGER (1..32,...)
In intra-Node B multiflow case, the Value specifies the index of the secondary serving or assisting serving or assisting secondary serving HS-DSCH cell for the UL HS-DPCCH as specified in TS 25.212.
In inter-Node B multiflow case, if present, the Value must be “1” when there is one secondary serving HS-DSCH cell. Otherwise the Value specifies the index of this cell for the UL HS-DPCCH as specified in [8].
YES
reject

9.2.2.18Ea	HS-DSCH FDD Update Information
The HS-DSCH FDD Update Information IE provides information for HS-DSCH to be updated. At least one IE shall be present.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-SCCH Code Change Indicator
O

9.2.1.31K

–

CQI Feedback Cycle k
O

9.2.2.21B

–

CQI Repetition Factor 
O

9.2.2.4Cb

–

ACK-NACK Repetition Factor
O

9.2.2.a

–

CQI Power Offset
O

9.2.2.4Ca

–

ACK Power Offset
O

9.2.2.b

–

NACK Power Offset
O

9.2.2.23a

–

HS-PDSCH Code Change Indicator
O

9.2.1.31M

YES
ignore
Precoder weight set restriction
O

9.2.2.192

YES
ignore
CQI Feedback Cycle2 k
O

CQI Feedback Cycle k2
9.2.2.206
For FDD only
YES
ignore
CQI Cycle Switch Timer
O

ENUMERATED (v4, v8, v16, v32, v64, v128, v256, v512, Infinity)
For FDD only, refer to TS 25.331 [16].
YES
ignore

9.2.2.18Eaa	HS-DSCH FDD Secondary Serving Update Information
The HS-DSCH FDD Secondary Serving Update Information IE provides information for Secondary Serving HS-DSCH to be updated. At least one IE shall be present.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-SCCH Code Change Indicator
O

9.2.1.31K

–

HS-PDSCH Code Change Indicator
O

9.2.1.31M
This IE shall never be included. If received it shall be ignored.
–

Precoder weight set restriction
O

9.2.2.192

YES
ignore

9.2.2.18Eb	HS-DSCH Serving Cell Change Information
The HS-DSCH Serving Cell Change  Information IE contains information which is used in HS-DSCH Serving Cell change.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-PDSCH RL ID
M

RL ID
9.2.1.53

–

HS-DSCH Information
O

HS-DSCH FDD Information 9.2.2.18D

–

HS-DSCH RNTI
M

9.2.1.31J

–

Continuous Packet Connectivity HS-SCCH less Information
O

9.2.2.68

YES
reject
Continuous Packet Connectivity DTX-DRX Information
O

9.2.2.66

YES
reject

9.2.2.18Ec	HS-DSCH Serving Cell Change Information Response
The HS-DSCH Serving Cell Change Information Response  IE contains information which is used in HS-DSCH Serving Cell change.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
CHOICE Serving Cell Change 




–

>Successful






>>HS-DSCH FDD Information Response
M

9.2.2.18E

–

>>Continuous Packet Connectivity HS-SCCH less Information Response
O

9.2.2.69

YES
ignore
>Unsuccessful






>>Cause
M

9.2.1.6

–


9.2.2.18Eca	HS-DSCH Secondary Serving Cell Change Information Response
The HS-DSCH Secondary Serving Cell Change Information Response IE contains information which is used in HS-DSCH Secondary Serving Cell change.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Secondary Serving Cell Change 




>Successful




>>HS-DSCH FDD Secondary Serving Information Response
M

9.2.2.18EA

>Unsuccessful




>>Cause
M

9.2.1.6


9.2.2.18Ed	E-DCH Serving Cell Change Information Response
The E-DCH Serving Cell Change Information Response  IE contains information which is used in E-DCH Serving Cell change.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Serving Cell Change 




>Successful




>>RL Information Response

0..<maxNrOfRLs>


>>>RL ID
M

9.2.1.53

>>>E-DCH FDD DL Control Channel Information
M

9.2.2.13Dc

>Unsuccessful




>>Cause
M

9.2.1.6


Range bound
Explanation
maxNrOfRLs
Maximum number of RLs for one UE

9.2.2.18Ee	HS-DSCH TB Size Table Indicator
The HS-DSCH TB Size Table Indicator IE is used to indicate that octet aligned table TS 25.321 [32] shall be used. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH TB Size Table Indicator


ENUMERATED (octet aligned)


9.2.2.18F	HS-PDSCH FDD Code Information
This parameter defines the codes which will be assigned for HS-PDSCHs.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Number Of HS-PDSCH Codes
M

INTEGER (0..maxHSPDSCHCodeNrComp-1)

Start Code Number
C-NumCodes

INTEGER (1..maxHSPDSCHCodeNrComp-1)


Condition
Explanation
NumCodes
The IE shall be present if the Number Of HS-PDSCH Codes IE is set to a value greater than 0.

Range Bound
Explanation
MaxHSPDSCHCodeNrComp
Maximum number of codes at the defined spreading factor, within the complete code tree

9.2.2.18G	HS-SCCH FDD Code Information
This parameter defines the codes which will be assigned for HS-SCCH. The Node B will assign codes for HS-SCCHs among these codes when it sets up a HS-DSCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE replaceremove
M



>replace




>>HS-SCCH Code

1..<MaxNrOfHSSCCHs>


>>>Code Number
M

INTEGER (0..maxHSSCCHCodeNrComp-1)

>remove


NULL


Range Bound
Explanation
MaxNrOfHSSCCHs
Maximum number of HS-SCCHs for one cell.
MaxHS-SCCHCodeNrComp
Maximum number of codes at the defined spreading factor, within the complete code tree

9.2.2.18H	HS-SCCH ID
Void.
9.2.2.18I	HS-SCCH Power Offset
The HS-SCCH Power Offset IE indicates the Power offset relative to the pilot bits on the DL DPCCH except when FDPCH is configured. When F-DPCH is configured, the HS-SCCH Power Offset IE indicates the Power offset relative to the power of transmitted TPC bits on the F-DPCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-SCCH Power Offset


INTEGER (0…255)
Unit: dB
Range: -32 .. +31.75 dB
Step: 0.25 dB

9.2.2.18K	Initial DL DPCH Timing Adjustment Allowed
The Initial DL DPCH Timing Adjustment Allowed IE indicates that the Node B is allowed to perform a timing adjustment (either a timing advance or a timing delay with respect to the SFN timing) when establishing a radio link.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Initial DL DPCH Timing Adjustment Allowed


ENUMERATED (
initial DL DPCH Timing Adjustment Allowed)


9.2.2.19	Max Adjustment Period
Void.
9.2.2.20	Max Adjustment Step
Defines the maximum allowed value for the change of DL power level during a certain number of slots that can be utilised by the downlink power balancing algorithm. Max Adjustment Step IE defines a time period, in terms of number of slots, in which the accumulated power adjustment shall be maximum 1dB. This value does not include the DL inner loop PC adjustment.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Max Adjustment Step


INTEGER (1..10)
Unit: Slots

9.2.2.20A	Max Number Of PCPCHs
Void.
9.2.2.20B	Max Number Of UL E-DPDCHs
Void.
9.2.2.20C	Maximum Set of E-DPDCHs
The Maximum Set of E-DPDCHs  as defined in TS 25.212 [8]. Needed by rate matching algorithm.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Maximum Set of E-DPDCHs


ENUMERATED (vN256, vN128, vN64, vN32, vN16, vN8, vN4, v2xN4, v2xN2, v2xN2plus2xN4,…, v2xM2plus2xM4) 


9.2.2.20D	Maximum Number Of Retransmissions For E-DCH
Void
9.2.2.20E	MAC-es Guaranteed Bit Rate
Void
9.2.2.20F	MAC-e Reset Indicator
Void
9.2.2.21	Maximum Number Of UL DPDCHs
Maximum number of uplink DPDCHs to be used during the connection. Needed by the rate matching algorithm.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Max Number Of UL DPDCHs


INTEGER (1..6)


9.2.2.21a	Maximum Target Received Total Wide Band Power
The Maximum Target Received Total Wide Band Power indicates the maximum target UL interference for a certain cell or cell portion under CRNC, including received wide band power from all sources. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Maximum Target Received Total Wide Band Power


INTEGER (0..621)
The Value mapping is according to mapping for measurement type "Received Total Wide Band Power" in TS 25.133 [22].

9.2.2.21b	Target Non-serving E-DCH to Total E-DCH Power Ratio
The Target Non-serving E-DCH to Total E-DCH Power Ratio indicates the target ratio of the received E-DCH power from non-serving UEs to the received total E-DCH power.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Target Non-serving E-DCH to Total E-DCH Power Ratio


INTEGER (0..100)
Unit: %
Range: 0..100 %
Step: 1 %

9.2.2.21A	Maximum PDSCH Power
Void.
9.2.2.21B	CQI Feedback Cycle k
The CQI Feedback Cycle k IE provides the duration of the CQI feedback cycle.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CQI Feedback Cycle k


ENUMERATED 
(0, 2, 4, 8, 10, 20, 40, 80, 160,…, 16, 32, 64)
Unit ms 
The allowed values for this IE depend on the configured CQI Repetition Factor and the HS-DSCH configuration as defined in TS 25.214 [10].

9.2.2.21C	Measurement Power Offset
The Measurement Power Offset IE is used as described in ref TS 25.214 [10] subclause 6A.2.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Measurement Power Offset


INTEGER (-12..26)
Unit: dB
Range: -6..13dB
Step: 0.5dB

9.2.2.21D	MICH Mode
The number of Notification Indicators (NIs) transmitted in a MICH frame.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MICH Mode


ENUMERATED 
(18, 36, 72, 144,…, 16, 32,64,128)
Number of NIs per frame

9.2.2.22	Minimum UL Channelisation Code Length
Minimum UL channelisation code length (spreading factor) of a DPDCH which is used during the connection. Needed by rate matching algorithm.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Min UL Channelisation Code Length


ENUMERATED 
(4, 8, 16, 32, 64, 128, 256,…)


9.2.2.22a	Min UL Channelisation Code Length For E-DCH FDD
Void.
9.2.2.23	Multiplexing Position 
Multiplexing Position specifies whether fixed or flexible positions of transport channels shall be used in the physical channel.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Multiplexing Position


ENUMERATED (
Fixed, 
Flexible)


9.2.2.23a	NACK Power Offset
The NACK Power Offset IE indicates Power offset used in the UL between the HS-DPCCH slot carrying HARQ NACK information and the associated DPCCH. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
NACK Power Offset


INTEGER (0..8,..., 9..10)
According to mapping in ref. TS 25.213 [9] subclause 4.2.1.

9.2.2.23A	N_EOT
Void.
9.2.2.23B	NF_max
Void.
9.2.2.23C	N_Start_Message
Void.
9.2.2.23D	Number Of Reported Cell Portions
Number of Reported Cell Portions indicates the number of Best Cell Portions values which shall be included in the measurement report.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Number Of Reported Cell Portions


INTEGER (1..64,…)


9.2.2.24	Pattern Duration (PD)
Void.
9.2.2.24A	PCP Length
Void.
9.2.2.25	PDSCH Code Mapping
Void.
9.2.2.26	PICH Mode
The number of paging indicators (PIs) in a PICH frame.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
PICH Mode


ENUMERATED 
(18, 36, 72, 144,…)
Number of PIs per frame

9.2.2.27	Power Adjustment Type
Defines the characteristic of the power adjustment.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Power Adjustment Type


ENUMERATED (
None, 
Common, 
Individual)


9.2.2.28	Power Control Mode
Void.
9.2.2.29	Power Offset
This IE defines a power offset relative to the Downlink transmission power of a DPDCH in case the Node B Communication Context is configured to use DPCH in the downlink or relative to a Secondary CCPCH data field.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Power Offset


INTEGER (0..24)
Unit: dB
Range: 0..6 dB
Step: 0.25 dB

9.2.2.29A	Power_Raise_Limit
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Power_Raise_Limit


INTEGER (0..10)
Unit: dB
Range: 0..10 dB
Step: 1 dB

9.2.2.30	Power Resume Mode
Void.
9.2.2.31	Preamble Signatures
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Preamble Signatures


BIT STRING (SIZE(16))
Each bit indicates availability for a signature, where the signatures are numbered "signature 0" up to "signature 15". The value 1 of a bit indicates that the corresponding signature is available and the value 0 that it is not available.The order of bits is to be interpreted according to subclause 9.3.4. See also TS 25.213 [9].

9.2.2.32	Preamble Threshold
The IE sets the threshold for preamble detection. The ratio between received preamble power during the preamble period and interference level shall be above this threshold in order to be acknowledged.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Preamble Threshold


INTEGER (0..72)
Unit: dB
Range: -36 .. 0 dB
Step: 0.5 dB

9.2.2.33	Primary CPICH Power
The Primary CPICH power is the power that shall be used for transmitting the P-CPICH in a cell. The reference point is the antenna connector. If Transmit Diversity is applied to the Primary CPICH, the Primary CPICH power is the linear sum of the power that is used for transmitting the Primary CPICH on all branches.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Primary CPICH Power


INTEGER
(-100..500)
Value = Primary CPICH Power/10
Unit: dBm
Range: -10.0..+50.0 dBm
Step: 0.1 dB

9.2.2.33A	Primary CPICH Usage For Channel Estimation
The Primary CPICH Usage For Channel Estimation IE indicates whether the Primary CPICH may be used for channel estimation or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Primary CPICH Usage For Channel Estimation


ENUMERATED (
Primary CPICH may be used, 
Primary CPICH shall not be used)


9.2.2.34	Primary Scrambling Code
The Primary scrambling code to be used in the cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Primary Scrambling Code


INTEGER (0..511)


9.2.2.35	Propagation Delay
The Propagation delay is the one-way propagation delay of the radio signal from the MS to the Node B. If the range of the Propagation Delay IE is insufficient to represent the measured value, the Propagation Delay IE shall be set to its maximum value, and the Extended Propagation Delay IE shall be used to represent the propagation delay value, see subclause 9.2.2.35A.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Propagation Delay


INTEGER (0..255)
Unit: chip
Range: 0..765 chips
Step: 3 chips

9.2.2.35A	Extended Propagation Delay
The Extended Propagation delay is the one-way propagation delay of the radio signal from the MS to the Node B. It shall be used if the Propagation Delay IE (see 9.2.2.35) cannot represent the measured value, due to range limitation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Extended Propagation Delay


INTEGER (255..1023)
Continuation of intervals as defined in TS 25.133 [22].
Unit: chip
Range: 765..3069 chips
Step: 3 chips

9.2.2.36	QE-Selector
Void.
9.2.2.36A	Qth Parameter
Void.
9.2.2.37	RACH Slot Format
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
RACH Slot Format


ENUMERATED (0..3,...)
See ref. TS 25.211 [7].

9.2.2.38	RACH Sub Channel Numbers
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
RACH Sub Channel Numbers


BIT STRING (SIZE(12))
Each bit indicates availability for a subchannel, where the subchannels are numbered "subchannel 0" to "subchannel 11". The value 1 of a bit indicates that the corresponding subchannel is available and the value 0 indicates that it is not available.The order of bits is to be interpreted according to subclause 9.3.4.

9.2.2.39	RL Set ID
The RL Set ID uniquely identifies one RL Set within a Node B Communication Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
RL Set ID


INTEGER (0..31)


9.2.2.39a	RL Specific E-DCH Information
The RL Specific E-DCH Information IE provides RL specific E-DCH Information. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
RL Specific E-DCH Information

1..<maxNrOfEDCHMACdFlows>


>E-DCH MAC-d Flow ID
M

9.2.1.74

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
E-AGCH Power Offset
O

9.2.2.13Id

E-RGCH Power Offset
O

9.2.2.13Ie

E-HICH Power Offset
O

9.2.2.13If


Range Bound
Explanation
maxNrOfEDCHMACdFlows
Maximum number of E-DCH MAC-d flows

9.2.2.39A	Received Total Wide Band Power
The Received total wide band power indicates the UL interference at a certain cell under CRNC, see ref. TS 25.215 [4].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Received Total Wide Band Power


INTEGER (0..621)
According to mapping in TS 25.133 [22].

9.2.2.39B	Reference Received Total Wide Band Power
When sent by the CRNC, the Reference Received Total Wide Band Power indicates the reference UL interference (received noise level) for a certain cell or cell portion under CRNC. This value may be used for E-DCH scheduling in the Node B.
When reported by the Node B, the Reference Received Total Wide Band Power indicates the reference UL interference (received noise level as an estimate of the noise floor) estimate from the Node B. This value may be used, e.g. for admission or congestion control in the CRNS.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Reference Received Total Wide Band Power


INTEGER (0..621)
The Value mapping is according to mapping for measurement type "Received Total Wide Band Power" in TS 25.133 [22].

9.2.2.39C	Reference Received Total Wide Band Power Reporting
The Reference Received Total Wide Band Power Reporting controls the indication of the Reference Received Total Wide Band Power estimate from the Node B.

IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Reference Received Total Wide Band Power Reporting


ENUMERATED (Reference Received Total Wide Band Power Requested)


9.2.2.39D	Reference Received Total Wide Band Power Support Indicator
The Reference Received Total Wide Band Power Support Indicator indicates whether indication of Reference Received Total Wide Band Power is supported by the Node B.

IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Reference Received Total Wide Band Power Support Indicator


ENUMERATED (Indication of Reference Received Total Wide Band Power supported)


9.2.2.40	S-Field Length
Void.
9.2.2.40A	Scheduling Information
Void
9.2.2.41	Scrambling Code Change
Void.
9.2.2.42	Scrambling Code Number
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Scrambling Code Number


INTEGER (0..15)
Identification of scrambling code see ref. TS 25.213 [9].

9.2.2.43	Secondary CCPCH Slot Format
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Secondary CCPCH Slot Format


INTEGER (0..17,…)


9.2.2.43A	Secondary CPICH Information Change
The Secondary CPICH Information Change IE indicates modification of information of the Secondary CPICH for channel estimation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Secondary CPICH Information Change
M



>New Secondary CPICH




>>Secondary CPICH Information
M

Common Physical Channel ID 9.2.1.13

>Secondary CPICH Shall Not Be Used


NULL


9.2.2.44	SSDT Cell Identity
Void.
9.2.2.44A	SSDT Cell Identity For EDSCHPC
Void.
9.2.2.45	SSDT Cell ID Length
Void.
9.2.2.46	SSDT Support Indicator
The SSDT Support Indicator indicates whether a RL supports SSDT or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SSDT Support Indicator


ENUMERATED (
Not Used,
SSDT Not Supported)
The SSDT Support Indicator IE shall never be set to “Not Used”. If received it shall be rejected.

9.2.2.47	SSDT Indication
Void.
9.2.2.48	STTD Indicator
Indicates if STTD shall be active or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
STTD Indicator


ENUMERATED (
active, 
inactive,
…)


9.2.2.48A	Synchronisation Indicator
The Synchronisation Indicator IE indicates that Timing Maintained Synchronisation shall be used at start of Radio Link, see also TS 25.214 [10].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Synchronisation Indicator


ENUMERATED (Timing Maintained Synchronisation, …)


9.2.2.48B	Serving E-DCH RL
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Serving E-DCH RL
M



>Serving E-DCH RL in this Node B




>>Serving E-DCH RL ID
M

RL ID
9.2.1.53

>Serving E-DCH RL not in this Node B


NULL


9.2.2.49	T Cell
Timing delay used for defining start of SCH, CPICH and the DL scrambling code(s) in a cell relative BFN. Resolution 256 chips.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
T Cell


ENUMERATED 
(0, 1,..,9)
Unit: chip
Range: 0..2304 chips
Step: 256 chips
See ref. TS 25.402 [17]

9.2.2.49A	TFCI2 Bearer Information Response
Void.
9.2.2.50	TFCI Signalling Mode
This parameter indicates if the normal or split mode is used for the TFCI. In the event that the split mode is to be used then the IE indicates whether the split is "Hard" or "Logical", and in the event that the split is "Logical" the IE indicates the number of bits in TFCI (field 2).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TFCI Signalling Option
M

ENUMERATED (
Normal, 
Not Used)
The value "Not Used" shall not be used by the CRNC. The procedure shall be rejected by the Node B if the value "Not Used" is received. 
Not Used
O

NULL

Not Used
O

NULL


9.2.2.51	TGD
Void.
9.2.2.52	TGL
Void.
9.2.2.53	Transmit Diversity Indicator
The Transmit Diversity Indicator indicates whether transmit diversity shall be active or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Transmit Diversity Indicator


ENUMERATED (
active, 
inactive)


9.2.2.53A	Transmission Gap Pattern Sequence Information
Defines the parameters for the compressed mode gap pattern sequence. For details see ref. TS 25.331 [18].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Transmission Gap Pattern Sequence Information

1..<maxTGPS>


>TGPS Identifier
M

INTEGER (1..maxTGPS)
Transmission Gap Pattern Sequence Identifier:
Establish a reference to the compressed mode pattern sequence. Up to <maxTGPS> simultaneous compressed mode pattern sequences can be used.
>TGSN
M

INTEGER (0..14)
Transmission Gap Starting Slot Number:
The slot number of the first transmission gap slot within the TGCFN.
>TGL1
M

INTEGER (1..14)
The length of the first Transmission Gap within the transmission gap pattern expressed in number of slots.
>TGL2
O

INTEGER (1..14)
The length of the second Transmission Gap within the transmission gap pattern. If omitted, then TGL2=TGL1.
>TGD
M

INTEGER 
(0, 15.. 269)
Transmission Gap Distance: indicates the number of slots between the starting slots of two consecutive transmission gaps within a transmission gap pattern. If there is only one transmission gap in the transmission gap pattern, this parameter shall be set to "0" ("0" =undefined).
>TGPL1
M

INTEGER (1..144,…)
The duration of transmission gap pattern 1 in frames.
>Not-to-be-used-1
O

INTEGER (1..144,…)
This IE shall never be included in the IE group. If received it shall be ignored.
>UL/DL Mode
M

ENUMERATED (
UL only, 
DL only, 
UL/DL)
Defines whether only DL, only UL or combined UL/DL compressed mode is used.
>Downlink Compressed Mode Method
C-DL

ENUMERATED (
Not Used, 
SF/2, 
Higher Layer Scheduling,
…)
Method for generating downlink compressed mode gap.The Downlink Compressed Mode Method IE shall never be set to “Not Used”.
>Uplink Compressed Mode Method
C-UL

ENUMERATED (
SF/2, 
Higher Layer Scheduling,
…)
Method for generating uplink compressed mode gap.
>Downlink Frame Type
M

ENUMERATED 
(A, B,…)
Defines if frame structure type "A" or "B" shall be used in downlink compressed mode.
>DeltaSIR1
M

INTEGER (0..30) 
Delta in SIR target value to be set in the Node B during the frame containing the start of the first transmission gap in the transmission gap pattern (without including the effect of the bit-rate increase).
Unit: dB
Range: 0..3 dB
Step: 0.1 dB
>DeltaSIRafter1
M

INTEGER (0..30)
Delta in SIR target value to be set in the Node B one frame after the frame containing the start of the first transmission gap in the transmission gap pattern.
Unit: dB
Range: 0..3 dB
Step: 0.1 dB
>DeltaSIR2
O

INTEGER (0..30)
Delta in SIR target value to be set in the Node B during the frame containing the start of the second transmission gap in the transmission gap pattern (without including the effect of the bit-rate increase).
When omitted, 
DeltaSIR2 = DeltaSIR1.
Unit: dB
Range: 0..3 dB
Step: 0.1 dB
>DeltaSIRafter2
O

INTEGER (0..30)
Delta in SIR target value to be set in the Node B one frame after the frame containing the start of the second transmission gap in the transmission gap pattern.
When omitted, 
DeltaSIRafter2 = DeltaSIRafter1.
Unit: dB
Range: 0..3 dB
Step: 0.1 dB

Condition
Explanation
UL
The IE shall be present if the UL/DL mode IE is set to "UL only" or "UL/DL".
DL
The IE shall be present if the UL/DL mode IE is set to "DL only" or "UL/DL".

Range Bound
Explanation
maxTGPS
Maximum number of transmission gap pattern sequences

9.2.2.53B	Transmission Gap Pattern Sequence Code Information
This IE indicates whether the alternative scrambling code shall used for the Downlink compressed mode method or not in the Transmission Gap Pattern Sequence. For details see TS 25.213 [9].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Transmission Gap Pattern Sequence Code Information


ENUMERATED (
Code Change, 
No Code Change)
Indicates whether the alternative scrambling code is used for compressed mode method "SF/2".

9.2.2.54	UL/DL compressed mode selection
Void.
9.2.2.55	UL delta SIR
Void.
9.2.2.56	UL delta SIR after
Void.
9.2.2.57	UL DPCCH Slot Format
Indicates the slot format used in DPCCH in UL, according to ref. TS 25.211 [7].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL DPCCH Slot Format


INTEGER (0..5,…)
If DCH Enhancement (Basic/Full) capabilities are not supported, value 5 shall not be used. If in this case value 5 is received, the procedure shall be rejected.

9.2.2.58	UL SIR
Void.
9.2.2.59	UL Scrambling Code
The UL Scrambling Code is the scrambling code used by UE. Every UE has its specific UL Scrambling Code.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL Scrambling Code Number
M

INTEGER (0..224-1)

UL Scrambling Code Length
M

ENUMERATED (
Short, 
Long)


9.2.2.60	UL Capacity Credit
Void.
9.2.2.61	UL DPDCH Indicator For E-DCH Operation
The UL DPDCH Indicator For E-DCH Operation parameter indicates whether some UL DPCH parameters should be ignored or not in the message in which the UL DPDCH Indicator For E-DCH Operation IE was included or that any UL DPDCH resources shall be removed from the communication context configuration.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL DPDCH Indicator For E-DCH Operation


ENUMERATED (
UL-DPDCH present,
UL-DPDCH not present)


9.2.2.62	Fast Reconfiguration Mode
The Fast Reconfiguration Mode IE is used to notify the Node B that the SRNC would like to use the activation time “when the UE is detected on the new configuration” as the timing for the reconfiguration. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Fast Reconfiguration Mode


ENUMERATED (
Fast,…)


9.2.2.63	Fast Reconfiguration Permission
The Fast Reconfiguration Permission IE is used to indicate to the CRNC that the Node B can apply the activation time “when the UE is detected on the new configuration” for this reconfiguration. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Fast Reconfiguration Permission


ENUMERATED (
Allowed,…)


9.2.2.64	Continuous Packet Connectivity DTX-DRX Capability
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Continuous Packet Connectivity DTX-DRX Capability


ENUMERATED (Continuous Packet Connectivity DTX-DRX Capable,  Continuous Packet Connectivity DTX-DRX Non-Capable)


9.2.2.65	Continuous Packet Connectivity HS-SCCH less Capability
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Continuous Packet Connectivity HS-SCCH less Capability


ENUMERATED (Continuous Packet Connectivity HS-SCCH less Capable,  Continuous Packet Connectivity HS-SCCH less Non-Capable)


9.2.2.66	Continuous Packet Connectivity DTX-DRX Information
The Continuous Packet Connectivity DTX-DRX Information IE defines the parameters used for Continuous Packet Connectivity DTX-DRX operation (see ref. TS 25.214 [10]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
UE DTX DRX Offset
M

INTEGER (0..159)
Units of subframes. Offset of the UE DTX and DRX cycles at the given TTI
–

Enabling Delay
M

ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128)
Units of radio frames
–

DTX Information

1




>CHOICE E-DCH TTI Length
M



–

>>2ms




–

>>>UE DTX Cycle 1
M

ENUMERATED (1, 4, 5, 8, 10, 16, 20)
Units of subframes
–

>>>UE DTX Cycle 2
M

ENUMERATED (4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160)
Units of subframes
–

>>>MAC DTX Cycle
M

ENUMERATED (1, 4, 5, 8, 10, 16, 20)
Units of subframes
–

>>10ms




–

>>>UE DTX Cycle 1
M

ENUMERATED (1, 5, 10, 20)
Units of subframes
–

>>>UE DTX Cycle 2
M

ENUMERATED (5, 10, 20, 40, 80, 160)
Units of subframes
–

>>>MAC DTX Cycle
M

ENUMERATED (5, 10, 20)
Units of subframes
–

>Inactivity Threshold for UE DTX Cycle 2
M

ENUMERATED (1, 4, 8, 16, 32, 64, 128, 256)
Units of E-DCH TTIs
–

>UE DTX Long Preamble 
M

ENUMERATED (2,4,15)
Units of slots
–

>MAC Inactivity Threshold
M

ENUMERATED (1, 2, 4, 8, 16, 32, 64, 128, 256, 512, Infinity)
Units of E-DCH TTIs
–

>CQI DTX Timer
M

ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, Infinity)
Units of subframes
–

>UE DPCCH burst1
M

ENUMERATED (1, 2, 5)
Units of subframes
–

>UE DPCCH burst2
M

ENUMERATED (1, 2, 5)
Units of subframes
–

DRX Information

0..1




>UE DRX Cycle
M

ENUMERATED (4, 5, 8, 10, 16, 20)
Units of subframes
–

>Inactivity Threshold for UE DRX Cycle
M

ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512)
Units of subframes
–

>Inactivity Threshold for UE Grant Monitoring
M

ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256)
Units of E-DCH TTIs
–

>UE DRX Grant Monitoring
M

BOOLEAN
True: DRX Grant Monitoring shall be applied.
False: DRX Grant Monitoring shall not be applied.
–

>UE DRX Cycle 2
O

ENUMERATED (v4, v5, v8, v10, v16, v20)
Units of subframes, refer to TS 25.331 [16].
YES
ignore
>Inactivity Threshold for UE DRX Cycle 2
O

ENUMERATED (v0, v1, v2, v4, v8, v16, v32, v64, v128, v256, v512)
Units of subframes, refer to TS 25.331 [16].
YES
ignore

9.2.2.67	Continuous Packet Connectivity DTX-DRX Information To Modify
The Continuous Packet Connectivity DTX-DRX Information To Modify IE is used for modification of Continuous Packet Connectivity DTX-DRX information in a Node B Communication Context. The Continuous Packet Connectivity DTX-DRX Information To Modify IE shall include at least one of the following IE.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
UE DTX DRX Offset
O

INTEGER (0..159)
Units of subframes. Offset of the UE DTX and DRX cycles at the given TTI
–

Enabling Delay
O

ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128)
Units of radio frames
–

CHOICE DTX Information To Modify
O





>Modify




–

>>CHOICE E-DCH TTI Length
O



–

>>>2ms






>>>>UE DTX Cycle 1
M

ENUMERATED (1, 4, 5,  8, 10, 16, 20)
Units of subframes
–

>>>>UE DTX Cycle 2
M

ENUMERATED (4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160)
Units of subframes
–

>>>>MAC DTX Cycle
M

ENUMERATED (1, 4, 5, 8, 10, 16, 20)
Units of subframes
–

>>>10ms






>>>>UE DTX Cycle 1
M

ENUMERATED (1, 5, 10, 20)
Units of subframes
–

>>>>UE DTX Cycle 2
M

ENUMERATED (5, 10, 20, 40, 80, 160)
Units of subframes
–

>>>>MAC DTX Cycle
M

ENUMERATED (5, 10, 20)
Units of subframes
–

>>Inactivity Threshold for UE DTX Cycle 2
O

ENUMERATED (1, 4, 8, 16, 32, 64, 128, 256)
Units of E-DCH TTIs
–

>>UE DTX Long Preamble 
O

ENUMERATED (2,4,15)
Units of slots
–

>>MAC Inactivity Threshold
O

ENUMERATED ( 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, Infinity)
Units of E-DCH TTIs
–

>>CQI DTX Timer
O

ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, Infinity)
Units of Subframes
–

>>UE DPCCH burst1
O

ENUMERATED (1, 2, 5)
Units of Subframes
–

>>UE DPCCH burst2
O

ENUMERATED (1, 2, 5)
Units of Subframes
–

>Deactivate


NULL

–

CHOICE DRX Information To Modify 
O





>Modify




–

>>UE DRX Cycle
O

ENUMERATED ( 4, 5, 8, 10, 16, 20)
Units of subframes
–

>>Inactivity Threshold for UE DRX Cycle
O

ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512)
Units of subframes
–

>>Inactivity Threshold for UE Grant Monitoring
O

ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256)
Units of E-DCH TTIs
–

>>UE DRX Grant Monitoring
O

BOOLEAN
True: DRX Grant Monitoring shall be applied.
False: DRX Grant Monitoring shall not be applied.
–

>>UE DRX Cycle 2
O

ENUMERATED ( v4, v5, v8, v10, v16, v20)
Units of subframes, refer to TS 25.331 [16].
YES
ignore
>>Inactivity Threshold for UE DRX Cycle 2
O

ENUMERATED (v0, v1, v2, v4, v8, v16, v32, v64, v128, v256, v512)
Units of subframes, refer to TS 25.331 [16].
YES
ignore
>Deactivate


NULL




9.2.2.68	Continuous Packet Connectivity HS-SCCH less Information 
The Continuous Packet Connectivity HS-SCCH less Information IE defines the parameters used for Continuous Packet Connectivity HS-SCCH less operation (see ref. TS 25.214 [10]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Transport Block Size List

1..<maxNrOfHS-DSCH-TBSs-HS-SCCHless>


>Transport Block Size Index
M

INTEGER (1..maxNrOfHS-DSCH-TBSs)

>HS-PDSCH Second Code Support
M

BOOLEAN
True = The second HS-PDSCH code shall also be used
False = The second HS-PDSCH code shall not be used

Range Bound
Explanation
maxNrOfHS-DSCH-TBSs-HS-SCCHless
Maximum number of HS-DSCH Transport Block Sizes used for HS-SCCH-less operation
maxNrOfHS-DSCH-TBSs
Maximum number of HS-DSCH Transport Block Sizes

9.2.2.69	Continuous Packet Connectivity HS-SCCH less Information Response
The Continuous Packet Connectivity HS-SCCH less Information Response IE provides information for HS-SCCH less operation determined within the Node B (see ref. TS 25.214 [10]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-PDSCH First Code Index
M

INTEGER (1..maxHSPDSCHCodeNrComp-1)
Index of first HS-PDSCH code
HS-PDSCH Second Code Index
O

INTEGER (1..maxHSPDSCHCodeNrComp-1)
Index of second HS-PDSCH code See NOTE 1.
NOTE 1:	The "HS-PDSCH second code index" value is the value of IE "HS-PDSCH First Code Index" incremented by 1. 

9.2.2.69A	Continuous Packet Connectivity HS-SCCH less Deactivate Indicator
The Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE is used to deactivate HS-SCCH less operation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Continuous Packet Connectivity HS-SCCH less Deactivate Indicator
M

NULL


Range Bound
Explanation
maxHSPDSCHCodeNrComp
Maximum number of codes at the defined spreading factor, within the complete code tree

9.2.2.70	MIMO Capability
Void
9.2.2.71	MIMO Activation Indicator
Void
9.2.2.72	MIMO Mode Indicator
Void
9.2.2.73	MIMO Pilot Configuration
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Pilot Configuration
M



>Primary and Secondary CPICH




>>Associated Secondary CPICH
M

Common Physical Channel ID 9.2.1.13

>Normal and Diversity Primary CPICH


NULL


9.2.2.74	SixtyfourQAM DL Capability
Void.
9.2.2.74A	Sixtyfour QAM Usage Allowed Indicator
The Sixtyfour QAM Usage Allowed Indicator IE indicates whether the Node B is allowed to use 64 QAM modulation for HS-DSCH transmission or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Sixtyfour QAM Usage Allowed Indicator
M

ENUMERATED (Allowed, Not-Allowed)


9.2.2.74B	SixtyfourQAM DL Usage Indicator
The SixtyfourQAM DL Usage Indicator IE indicates if the Node B is using 64 QAM modulation for the HS-DSCH transmission, or if the Node B is not using 64 QAM modulation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SixtyfourQAM DL Usage Indicator


ENUMERATED (SixtyfourQAM DL Used,  SixtyfourQAM DL Not Used)


9.2.2.75	HS-DSCH Common System Information
The HS-DSCH Common System Information IE provides information for HS-DSCH configured for UE in Cell_FACH, in Cell_PCH and in URA_PCH and Information related to BCCH modification.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-DSCH Common Information

0..1


–

>CCCH Priority Queue ID



M

Priority Queue ID
9.2.1.49C

–

>SRB#1 Priority Queue ID

M

Priority Queue ID
9.2.1.49C

–

>Associated Common MAC Flow
M

Common MAC Flow ID
9.2.2.79
The Common MAC Flow ID shall be one of the flow IDs defined in the Common MAC Flow Specific Information of this IE or shall only refer to a Common MAC flow already existing in the old configuration.
–

>FACH Measurement Occasion Cycle Length Coefficient
O

9.2.1.111

–

>RACH Measurement Result
M

9.2.2.84

–

>BCCH Specific HS-DSCH-RNTI Information

M

9.2.2.85


–

Common MAC Flow
Specific Information

0..<maxNrOfCommonMACFlows>


–

>Common MAC Flow ID
M

9.2.2.79

–

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
–

>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
–

>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP.
–

>Common MAC Flow Priority Queue Information

0..<maxNrOfcommonMACQueues>


–

>>Priority Queue Information for Enhanced FACH
M

Priority Queue Information for Enhanced FACH/PCH 9.2.1.117

–

>Transport Bearer Request Indicator
O

9.2.1.62A
Shouldn’t be contained if the MAC flow is setup in procedure.
Should be contained if the MAC flow is modified in procedure
–

Common HS-DSCH RNTI List
O

9.2.2.148

YES
ignore

Range bound
Explanation
maxNrOfCommonMACFlows
Maximum number of Common MAC Flows
maxNrOfcommonMACQueues
Maximum number of Priority Queues for Common MAC Flow

9.2.2.76	HS-DSCH Paging System Information
The HS-DSCH Paging System Information IE provides information for HS-DSCH configured for UE in Cell_PCH and URA_PCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Paging MAC Flow Specific Information

1..<maxNrOfPagingMACFlow>


>Paging MAC Flow ID
 
M

9.2.1.113

>HSDPA Associated PICH Information
M

9.2.2.81

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP.
>ToAWS
M

9.2.1.61

>ToAWE
M

9.2.1.60

>Paging MAC Flow Priority Queue Information

0..<maxNrOfpagingMACQueues>


>>Priority Queue Information for Enhanced PCH
M

Priority Queue Information for Enhanced FACH/PCH
9.2.1.117

>Transport Bearer Request Indicator
O

9.2.1.62A
Shouldn’t be contained if the MAC flow is setup in procedure.
Should be contained if the MAC flow is modified in procedure
HS-SCCH Power

M

DL Power
9.2.1.21

HS-PDSCH Power
 
M

DL Power
9.2.1.21

Number of PCCH transmissions
M

INTEGER (1..5)
Number of subframes used to transmit the PCCH.
Transport Block Size List

1..<maxNrOfHS-DSCHTBSsE-PCH>


>Transport Block Size Index for Enhanced PCH
M

INTEGER (1..32)
Index of the value range 1 to 32 of the MAC-ehs transport block size as specified in appendix A of TS 25.321 [32]

Range bound
Explanation
maxNrOfPagingMACFlow
Maximum number of Paging MAC Flows
maxNrOfpagingMACQueues
Maximum number of Priority Queues for Paging MAC Flow
maxNrOfHS-DSCHTBSsE-PCH
Maximum number of HS-DSCH Transport Block Sizes used for Enhanced PCH operation associated HS-SCCH less

9.2.2.77	HS-DSCH Common System Information Response
The HS-DSCH Common System Information Response IE provides information for HS-DSCH configured for UE not in Cell_DCH that have been established or modified.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-SCCH Specific Information Response

0..<maxNrOfHSSCCHCodes>

Channelization codes on HS-SCCH is transmitted for UE not in Cell_DCH
>Code Number
M

INTEGER (0..127)
First indexed HS-SCCH Channelisation code should be used for the BCCH specific H-RNTI.
HARQ Memory Partitioning 
O

9.2.1.102

Common MAC Flow
Specific Information Response

0..<maxNrOfCommonMACFlows>


>Common MAC Flow ID
M

9.2.2.79

>Binding ID
O

9.2.1.4

>Transport Layer Address
O

9.2.1.63

>HS-DSCH Initial Capacity Allocation
O

9.2.1.31Ha


Range Bound
Explanation
maxNrOfCommonMACFlows
Maximum number of Common MAC Flows
maxNrOfHSSCCHCodes
Maximum number of HS-SCCH codes

9.2.2.78	HS-DSCH Paging System Information Response
The HS-DSCH Paging System Information Response IE provides information for HS-DSCH configured for UE in Cell_PCH and URA_PCH that have been established or modified.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Paging MAC Flow Specific Information Response

1..<maxNrOfPagingMACFlow>


>Paging MAC Flow ID
M

9.2.1.113

>Binding ID
O

9.2.1.4

>Transport Layer Address
O

9.2.1.63

>HS-PDSCH Code Index
M

INTEGER (1..maxHSPDSCHCodeNrComp-1)
Index of HS-PDSCH code

Range bound
Explanation
maxNrOfPagingMACFlow
Maximum number of Paging MAC Flows

9.2.2.79	Common MAC Flow ID
Common MAC Flow ID is the unique identifier for one Common MAC flow.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common MAC Flow ID


INTEGER
(0..7)


9.2.2.80	Paging MAC Flow ID
Void.
9.2.2.81	HSDPA Associated PICH Information
The HSDPA Associated PICH Information IE provides information for PICH used for Enhanced PCH operation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE HSDPA PICH




>Shared with PCH




>>Common Physical Channel ID
M

9.2.1.13

>Not shared with PCH




>>Common Physical Channel ID
M

9.2.1.13

>>FDD DL Channelisation Code Number
M

9.2.2.14

>>PICH Power
M

9.2.1.49A

>>PICH Mode
M

9.2.2.26
Number of PI per frame
>>STTD Indicator
M

9.2.2.48


9.2.2.82	FACH Measurement Occasion Cycle Length Coefficient
Void.
9.2.2.83	Priority Queue Information for Enhanced FACH/PCH
Void.
9.2.2.84	RACH Measurement Result
The RACH Measurement Result identifies which RACH measurement result is forwarded to Node B in Frame Protocol.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
RACH Measurement Result


ENUMERATED (CPICH Ec/No, CPICH RSCP, Pathloss,...)


9.2.2.85	BCCH Specific HS-DSCH RNTI Information
The BCCH Specific HS-DSCH RNTI Information IE provides information for BCCH Transmission using HS-DSCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
BCCH Specific HS-DSCH RNTI 
M

HS-DSCH RNTI
9.2.1.31J

HS-SCCH Power 
M

DL Power
9.2.1.21

HS-PDSCH Power
M

DL Power
9.2.1.21


9.2.2.86	Enhanced FACH Capability
Void.
9.2.2.87	Enhanced PCH Capability
Void.
9.2.2.88	SixteenQAM UL Capability
This parameter defines the SixteenQAM uplink capability for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SixteenQAM UL Capability


ENUMERATED (SixteenQAM UL Capable,  SixteenQAM UL Non-Capable)


9.2.2.88A	SixteenQAM UL Operation Indicator
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SixteenQAM UL Operation Indicator


ENUMERATED (Activate,  Deactivate)


9.2.2.88B	E-TFCI Boost Information
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-TFCI BetaEC Boost
M

INTEGER (0..127,…)
E-TFCI threshold beyond which boosting of E-DPCCH is enabled
UL Delta T2TP
C-E-TFCIboost127

INTEGER (0..6,…)
Total E-DPDCH power across all codes to the combined power of DPCCH and E-DPCCH

Condition
Explanation
E-TFCIboost127
The IE shall be present if the E-TFCI BetaEC Boost IE value is not set o 127.

9.2.2.88C	SixtyfourQAM UL Operation Indicator
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SixtyfourQAM UL Operation Indicator


ENUMERATED (Activate,  Deactivate)


9.2.2.89	SixteenQAM UL Information
Void.
9.2.2.90	SixteenQAM UL Information To Modify
Void.
9.2.2.91	Modulation Power Offset
Indicates the modulation, and power offset in case of 16QAM, to be used for the Secondary CCPCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Modulation
M



>QPSK


NULL

>QAM




>>CPICH Secondary CCPCH Power Offset
M

INTEGER (-11..4,…)
Power offset between CPICH and secondary CCPCH.
Unit: dB
Range: -11 .. +4 dB
Step: 1 dB


9.2.2.92	Extended Secondary CCPCH Slot Format
Indicates the slot format used for the Secondary CCPCH. The extended slot format shall only be used for MBSFN.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Extended Secondary CCPCH Slot Format


INTEGER(18..23,…)


9.2.2.93	F-DPCH Slot Format 
The F-DPCH Slot Format IE defines the F-DPCH slot format for the TPC bits, as defined in TS 25.211 [7].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
F-DPCH Slot Format


INTEGER (0..9)


9.2.2.94	F-DPCH Slot Format Capability
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
F-DPCH Slot Format Capability


ENUMERATED (F-DPCH Slot Format Capable,  F-DPCH Slot Format Non-Capable)


9.2.2.95	Max UE DTX Cycle
The Max UE DTX Cycle IE defines the maximum UE DTX cycle supported by the Node B for Continuous Packet Connectivity DTX-DRX operation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Max UE DTX Cycle
M

ENUMERATED (v5, v10, v20, v40, v64, v80, v128, v160,…, v256, v320, v512, v640, v1024, v1280)
Units of subframes

9.2.2.96	MIMO N/M Ratio
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MIMO N/M Ratio
M

ENUMERATED (1/2, 2/3, 3/4, 4/5, 5/6, 6/7, 7/8, 8/9, 9/10, 1/1,…)


9.2.2.97	Common MAC Flows To Delete
The Common MAC Flows To Delete IE is used for the removal of Common MAC flows from a Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common MAC Flows To Delete

1..<maxNrOfCommonMACFlows>


>Common MAC Flow ID
M

9.2.2.79


Range Bound
Explanation
maxNrOfCommonMACFlows
Maximum number of Common MAC Flows

9.2.2.98	Paging MAC Flows To Delete
The Paging MAC Flows To Delete IE is used for the removal of Paging MAC flows from a Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Paging MAC Flows To Delete

1..<maxNrOfPagingMACFlow>


>Paging MAC Flow ID
M

9.2.1.113


Range Bound
Explanation
maxNrOfPagingMACFlow
Maximum number of Paging MAC Flows

9.2.2.99	MAC-ehs Reset Timer
Void.
9.2.2.100	E-AGCH Table Choice
The E-AGCH Table Choice IE indicates the choice of the E-AGCH table in TS 25.212 [8].

IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-AGCH Table Choice
M

ENUMERATED (Table 16B, Table 16B-1, …)
Table 16B indicates the Table 16B: Mapping of Absolute Grant Value in TS 25.212 [8] and Table 16B-1 indicates the Table 16B.1: Alternative Mapping of Absolute Grant Value in TS 25.212 [8].

9.2.2.101	Common E-DCH Capability
This parameter defines the Common E-DCH capability for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common E-DCH Capability


ENUMERATED (Common E-DCH Capable, Common E-DCH non Capable)


9.2.2.102	E-AI Capability
This parameter defines the E-AI capability for a Common E-DCH capable Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-AI Capability


ENUMERATED (E-AI Capable, E-AI non Capable)


9.2.2.103	Common E-DCH System Information
The Common E-DCH System Information IE provides information for E-DCH configured for UE in Cell_FACH and Idle state.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Common E-DCH UL DPCH Information

0..1


–

>UL SIR Target
M

UL SIR
9.2.1.67A

–

>DPC Mode
O

9.2.2.13C
If received, this IE shall be ignored. DPC mode 0 shall be applied for Common E-DCH(see ref. TS 25.214 [10]).
–

Common E-DCH E-DPCH Information

0..1


–

>Maximum Set of E-DPDCHs
M

9.2.2.20C

–

>Puncture Limit
M

9.2.1.50

–

>E-TFCS Information
M

9.2.2.13Dh

–

>E-TTI
M

9.2.2.13Di

–

>E-DPCCH Power Offset
M

9.2.2.13Dj

–

>E-RGCH 2-Index-Step Threshold
O

9.2.2.13Ig

–

>E-RGCH 3-Index-Step Threshold
O

9.2.2.13Ih

–

>HARQ Info for E-DCH
M

9.2.2.18ba

–

Common E-DCH Information

0..1


–

>E-DCH Reference Power Offset
O

9.2.2.13Y

–

>E-DCH Power Offset for Scheduling Info
O

9.2.1.85

–

>Maximum E-DCH resource allocation for CCCH
M

ENUMERATED (8, 12, 16, 24, 32, 40, 80, 120,..., 20)
Interms of TTIs,
Value 120 should  not be used
–

>Maximum period for collision resolution phase
M

INTEGER(8..24,...)
Interms of TTIs
–

>Maximum TB Sizes
O

9.2.2.106

–

>Common E-DCH implicit release indicator
M

BOOLEAN
TRUE means implicit release is in use. FALSE means implicit release is not in use.
–

>Common E-DCH Additional Transmission Back Off
O

INTEGER (0..15,...)

YES
ignore
>Common E-DCH Implicit Release Timer
O

ENUMERATE(
zero, 
more than zero)
Indicates the value of E-DCH transmission continuation back off as defined in TS 25.331 [18].
YES
ignore
Common E-DCH HS-DPCCH Information

0..1


–

>ACK-NACK Repetition Factor
M

9.2.2.a

–

>ACK Power Offset
M

9.2.2.b

–

>NACK Power Offset
M

9.2.2.23a

–

>Common E-DCH CQI Information
O



–

>>CQI Feedback Cycle k
M

9.2.2.21B

–

>>CQI Repetition Factor
C-CQICyclek

9.2.2.4Cb

–

>>CQI Power Offset 
M

9.2.2.4Ca

–

>>Measurement Power Offset
M

9.2.2.21C

–

Common E-DCH Preamble Control Information

0..1


–

>Common Physical Channel ID
M

9.2.1.13

–

>Common E-DCH Preamble Signature
M

Preamble Signatures 9.2.2.31

–

>Scrambling Code Number
M

9.2.2.42

–

>Preamble Threshold
M

9.2.2.32

–

>E-AI Indicator
O

BOOLEAN
TRUE means E-AIs are in use on the AICH. FALSE means E-AIs are not in use on the AICH.
–

>Common E-DCH AICH Information

0..1


–

>>Common Physical Channel ID
M

9.2.1.13

–

>>AICH Transmission Timing
M

9.2.2.1

–

>>FDD DL Channelisation Code Number
M

9.2.2.14

–

>>AICH Power
M

9.2.2.D

–

>>STTD Indicator
M

9.2.2.48

–

Common E-DCH F-DPCH Information

0..1


–

>F-DPCH slot format
M

9.2.2.93

–

>FDD TPC DL Step Size
M

9.2.2.16

–

>Initial DL Transmission Power
O

DL Power
9.2.1.21
Initial power on F-DPCH
YES
ignore
>Maximum DL Power
O

DL Power
9.2.1.21
Maximum allowed power on F-DPCH
YES
ignore
>Minimum DL Power
O

DL Power
9.2.1.21
Minimum allowed power on F-DPCH
YES
ignore
Common E-DCH E-AGCH Channelisation Code Number
O

FDD DL Channelisation Code Number
9.2.2.14

–

Common E-DCH Resource Combination Information

0..<maxNrOfCommonEDCH>


–

>Soffset
M

INTEGER (0..9,...)

–

>F-DPCH DL Code Number

M

FDD DL Channelisation Code Number
9.2.2.14

–

>UL DPCH Scrambling Code
M

UL Scrambling Code
9.2.2.59

–

>E-RGCH/E-HICH Channelisation Code
M

FDD DL Channelisation Code Number
9.2.2.14

–

>E-RGCH Signature Sequence
O

INTEGER (0.. maxNrofSigSeqRGHI-1)

–

>E-HICH Signature Sequence
M

INTEGER (0.. maxNrofSigSeqRGHI-1)

–

UL Common MAC Flow
Specific Information

0..<maxNrOfCommonMACFlows>


–

>UL Common MAC Flow ID
M

Common MAC Flow ID
9.2.2.79

–

>Transport Bearer Request Indicator
M

9.2.1.62A

–

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
–

>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
–

>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP.
–

>Payload CRC Presence Indicator
M

9.2.1.49

–

>Bundling Mode Indicator
O

9.2.2.1Bb

–

>Common E-DCH MAC-d Flow Specific Information
M

9.2.2.105

–

E-RNTI List Request
O

NULL

YES
ignore
E-AGCH Power Offset
O

9.2.2.13Id

YES
ignore
E-RGCH Power Offset
O

9.2.2.13Ie

YES
ignore
E-HICH Power Offset
O

9.2.2.13If

YES
ignore
Concurrent Deployment of 2ms and 10ms TTI
O



YES
ignore
>Concurrent TTI Partition Index
M

INTEGER (maxNrOfCommonEDCH)

–

>Common E-DCH System Info Parameters for Concurrent TTI
M

9.2.2.191

–

Common E-DCH Preamble Control Information extension Type1
O 

Common E-DCH Preamble Control Information extension list
9.2.2.186

YES
ignore
Common E-DCH Preamble Control Information extension Type2
O

Common E-DCH Preamble Control Information extension list
9.2.2.186

YES
ignore
Common E-DCH Preamble Control Information extension Type3
O

Common E-DCH Preamble Control Information extension list
9.2.2.186

YES
ignore
NodeB Triggered HS-DPCCH Transmission Information
O



YES
ignore
>HS-DPCCH transmission continuation back off
M

ENUMERATED (10,20,30,40,80,160,320,800, infinity, …)
In terms of ms. The value infinity means explicit release.
–

Per HARQ Activation and Deactivation 
O



YES
ignore
>Configuration for 2ms TTI Common E-DCH Resources

1..<maxNrOfCommonEDCH>




>>2ms HARQ Process Allocation
M

HARQ Process Allocation for 2ms TTI
9.2.2.13Dn

–

Coffset
O

Integer(0..29)
(0..29) indicates cell offset as defined in [7]
YES
ignore
E-RNTI Set
O

E-RNTI Set  9.2.2.218

YES
ignore

Condition
Explanation
CQICyclek
The IE shall be present if the CQI Feedback Cycle k IE is set to a value greater than 0.

Range bound
Explanation
maxNrOfCommonMACFlows
Maximum number of Common MAC Flows
maxNrOfCommonEDCH
Maximum number of Common E-DCH Resource Combination for a cell
maxNrofSigSeqRGHI
Maximum number of Signature Sequences for E-RGCH/E-HICH.

9.2.2.104	Common E-DCH System Information Response
The Common E-DCH System Information Response IE provides information for E-DCH configured for UE in Cell_FACH and Idle state that have been established or modified.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
UL Common MAC Flow Specific Information Response

1..><maxNrOfCommonMACFlows>>


–

>UL Common MAC Flow ID
M

Common MAC Flow ID
9.2.2.79

–

>Binding ID
O

9.2.1.4

–

>Transport Layer Address
O

9.2.1.63

–

Serving Grant Value
M

INTEGER (0..37,38)
(0..37) indicates E-DCH serving grant index as defined in TS 25.321 [32]; Index 38 is not allowed
–

E-RNTI List
O

9.2.2.139
The Node B shall not allocate any E-RNTIs listed in this IE for a UE
YES
ignore
UE Status Update Confirm Indicator
O

BOOLEAN
TRUE means that the Node B supports UE Status Update Confirmation Procedure
YES
ignore
Serving Grant Value for Concurrent Deployment of 2ms and 10ms TTI
O

INTEGER (0..38)
(0..37) indicates E-DCH serving grant index as defined in TS 25.321 [32]; Index 38 is not allowed.
YES
ignore

Range bound
Explanation
maxNrOfCommonMACFlows
Maximum number of Common MAC Flows

9.2.2.105	Common E-DCH MAC-d Flow Specific Information
The Common E-DCH MAC-d Flow Specific Information IE is used for the establishment or modity Common E-DCH MAC-d flows.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Common E-DCH MAC-d Flow Specific Information

1..<maxNrOfEDCHMACdFlows>


-

>Common E-DCH MAC-d Flow ID
M

E-DCH MAC-d Flow ID 
9.2.1.74
The E-DCH MAC-d flow identity reserved for CCCH transmission is defined in TS 25.331 [18].
-

>Maximum Number Of Retransmissions For E-DCH
M

9.2.1.81

-

>E-DCH HARQ Power Offset FDD
M

9.2.2.13Dk

-

>E-DCH MAC-d Flow Multiplexing List
O

9.2.1.69

-

>Common E-DCH Logical Channel information

1..<maxnooflogicalchannels>


-

>>Logical Channel ID
M

9.2.1.80

-

>>Maximum MAC-c PDU Size Extended
M

MAC PDU Size Extended
9.2.1.38C

-

>>Scheduling Priority Indicator
O

9.2.1.53H

YES
ignore
>Common E-DCH MAC-d flow info for Concurrent TTI

0..1


YES
ignore
>>Maximum Number Of Retransmissions For E-DCH
O

9.2.1.81

-

>>E-DCH HARQ Power Offset FDD
O

9.2.2.13Dk

-


Range bound
Explanation
maxNrOfEDCHMACdFlows
Maximum number of E-DCH MAC-d Flows
maxnooflogicalchannels
Maximum number of logical channels

9.2.2.106	Maximum TB Size
The Maximum TB Size IE may be used by the sheduler in order to minimize the cell edge interference for cell edge users (and other users). 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Maximum TB Size cell edge users
M

INTEGER (0..5000,…)
Unit: Bits
Maximum TB Size other users
M

INTEGER (0..5000,…)
Unit: Bits

9.2.2.107	Enhanced UE DRX Capability
Void.
9.2.2.108	Enhanced UE DRX Information
The Enhanced UE DRX Information IE provides information for configuring the UE in Cell_FACH state to discontinuously receive HS-DSCH. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
T321
M

ENUMERATED (100, 200,  400, 800,…)
Determines the time the UE waits until initiating DRX operation, in ms.
HS-DSCH DRX cycleFACH
M

ENUMERATED (4, 8, 16, 32,…)
Determines the length of the DRX Cycle during DRX operation, in frames
HS-DSCH Rx burstFACH
M

ENUMERATED (1, 2, 4, 8, 16,…)
Determines the period within the DRX Cycle that the UE continuously receives HS-DSCH, in frames
DRX Interruption by HS-DSCH data
M

ENUMERATED (DrxInterruptionConfigured, DrxInterruptionNotConfigured)


9.2.2.109	E-DPCCH Power Boosting Capability
This parameter defines the E-DPCCH Power Boosting Capability for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DPCCH Power Boosting Capability


ENUMERATED (E-DPCCH Power Boosting Capable,  E-DPCCH Power Boosting Non-Capable)


9.2.2.110	SixtyfourQAM DL and MIMO Combined Capability
Void
9.2.2.111	HS-DSCH Preconfiguration Info
The HS-DSCH Preconfiguration Info IE provides information of the target cell preconfiguration in the Node B as defined in TS 25.331 [18].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Sets of HS-SCCH Codes

1…<maxNrOfHSDSCH>

Index 1 refers to the serving HS-DSCH cell
Index 2…<maxNrOfHSDSCH> refer to secondary serving HS-DSCH cells in the order as listed in 9.2.2.112 HS-DSCH Preconfiguration Setup. Max index is 4 in this 3GPP release.
–

> HS-SCCH Preconfigured Codes

1..<maxNrOfHSSCCHCodes>


–

>> Code Number
M

INTEGER (0..127)

–

> SixtyfourQAM DL Usage Indicator
O

9.2.2.74B

–

> HS-DSCH TB Size Table Indicator
O

9.2.2.18Ee

–

> MIMO N/M Ratio
O

9.2.2.96
Applicable for multicarrier mode of operation.
YES
ignore
HARQ Memory Partitioning
M

9.2.1.102

–

E-DCH FDD DL Control Channel Information
O

9.2.2.13Dc
For the primary UL frequency in Dual-cell E-DCH mode of operation.
–

HARQ Preamble Mode Activation Indicator
O

9.2.2.18b

–

MIMO N/M Ratio
O

9.2.2.96
Only applicable for MIMO in singe carrier mode of operation. Shall be ignored in multicarrier mode of operation.
–

Continuous Packet Connectivity HS-SCCH less Information Response
O

9.2.2.69

–

Additional E-DCH Preconfiguration Information

0..<maxNrOfEDCH-1>

For E-DCH on multiple frequencies in this Node B.
E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.
Index 1 correspond to the secondary serving HS-DSCH cells with index 2 in the IE Sets of HS-SCCH Codes. The list is in the order as listed in 9.2.2.112 HS-DSCH Preconfiguration Setup.
EACH
ignore
>E-DCH FDD DL Control Channel Information
M

9.2.2.13Dc
For the secondary  UL frequency In Dual-cell E-DCH mode of operation.
–

Support of dynamic DTXDRX related HS-SCCH order
O

9.2.2.150

YES
ignore

Range bound
Explanation
maxNrOfHSSCCHCodes
Maximum number of HS-SCCH codes
maxNrOfHSDSCH
Maximum number of Primary Serving plus Secondary Serving HS-DSCH cells for one UE

9.2.2.112	HS-DSCH Preconfiguration Setup
The HS-DSCH Preconfiguration Setup IE indicates that the Node B shall preconfigure set(s) of HS-SCCH codes and may contain a list of secondary serving, assisting serving, and assisting secondary serving HS-DSCH cells to be preconfigured for Enhanced Service Cell Change. The Cell Change procedure for Dual Cell operation is described in TS 25.308 [49]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
MAC-hs/ehs reset scheme 
M

ENUMERATED (Always, Inter NodeB Change) 
MAC-hs/ehs reset handling at enhanced HS serving cell change:
"Always" means always reset 
"Inter Node B Change" means  Only reset at Inter Node B cell change
–

HS-DSCH Physical Layer Category
M

9.2.1.31Ia

–

MAC-hs Reordering Buffer Size for RLC-UM
M

9.2.1.38Ab

–

Secondary Cells

0…<maxNrOfHSDSCH-1>

Preconfigured secondary serving HS-DSCH cell. maxNrOfHSDSCH-1 is max 7 in this 3GPP release.
–

>Secondary C-ID
M

C-ID
9.2.1.9
C-ID of the preconfigured secondary serving HS-DSCH cell
–

>Num Secondary HS-SCCH Codes
O

INTEGER (1.. maxNrOfHSSCCHCodes)
For the secondary serving HS-DSCH cell
–

>Sixtyfour QAM Usage Allowed Indicator
O

9.2.2.74A
For the secondary serving HS-DSCH cell
–

>MIMO Activation Indicator
O

9.2.1.119
For the secondary serving HS-DSCH cell
YES
ignore
>E-DCH Indicator
O

NULL
The secondary serving HS-DSCH cell shall be pre-configured with E-DCH.
YES
ignore
>Ordinal Number Of Frequency
O

INTEGER (1..32,...)
Value = "1" indicates 1st secondary serving HS-DSCH cell, Value = "2" indicates 2nd secondary serving HS-DSCH cell etc. TS 25.214 [10].
The IE shall be ignored by the Node B if the new configuration contains one secondary serving radio link.
YES
ignore
>MIMO with four transmit antennas Activation Indicator
O

9.2.2.164
For the secondary serving HS-DSCH cell.
YES
ignore
>Dual Stream MIMO with four transmit antennas Activation Indicator
O

9.2.2.167
For the secondary serving HS-DSCH cell.
YES
ignore
>Multiflow Ordinal Number Of Frequency
O

INTEGER (1..32,...)
In intra-Node B multiflow case, the Value specifies the index of the secondary serving or assisting serving or assisting secondary serving HS-DSCH cell for the UL HS-DPCCH as specified in TS 25.212.
In inter-Node B multiflow case, if present, the Value must be “1” when there is one secondary serving HS-DSCH cell. Otherwise the Value specifies the index of this cell for the UL HS-DPCCH as specified in [8].
YES
ignore
Num Primary HS-SCCH Codes
O

INTEGER (1.. maxNrOfHSSCCHCodes)
For the primary serving HS-DSCH cell
–

HARQ Preamble Mode
O

9.2.2.18a

–

MIMO Activation Indicator
O

9.2.1.119
In multicarrier mode of operation the IE is for the serving HS-DSCH cell
–

HS-DSCH MAC-d PDU Size Format 
O

9.2.1.31ID
If not present, "Indexed MAC-d PDU Size" shall be assumed.
–

Sixtyfour QAM Usage Allowed Indicator
O

9.2.2.74A
For the serving HS-DSCH cell
–

UE with enhanced HS-SCCH support indicator
O

NULL
UE supports enhanced HS-SCCH functionality:
- UE supports different HS-SCCH in consecutive TTIs and
- in HS-SCCH-less operation mode the UE supports HS-SCCH orders
–

Continuous Packet Connectivity HS-SCCH less Information
O

9.2.2.68

–

UE Support Indicator Extension
O

9.2.2.117

YES
ignore
MIMO with four transmit antennas Activation Indicator
O

9.2.2.164
In multicarrier mode of operation the IE is for the serving HS-DSCH cell.
YES
ignore
Dual Stream MIMO with four transmit antennas Activation Indicator
O

9.2.2.167
In multicarrier mode of operation the IE is for the serving HS-DSCH cell.
YES
ignore
Multiflow Information
O

9.2.2.170

YES
ignore
F-TPICH Information
O

9.2.2.160

YES
ignore
UL CLTD Information
O

9.2.2.152

YES
ignore
UL MIMO Information
O

9.2.2.177

YES
ignore
SixteenQAM UL Operation Indicator
O

9.2.2.88A

YES
ignore
SixtyfourQAM UL Operation Indicator
O

9.2.2.88C

YES
ignore

Range bound
Explanation
maxNrOfHSSCCHCodes
Maximum number of HS-SCCH codes
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE

9.2.2.113	Multi Cell Capability Info
This parameter defines the Multi Cell capability information for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Multi Cell Capability
M

ENUMERATED (Multi Cell Capable, Multi Cell non Capable)

–

Possible Secondary Serving Cell List

0..<maxNrOfHSDSCH-1>

For secondary serving HS-DSCH cell.
–

>Possible Secondary Serving Cell
M

Local Cell ID
9.2.1.38
Cells possible to serve in multicell adjacent and/or non-adjacent carrier operationTS 25.133 [22] (same or adjacent sector in the same Node B)
–

>Multicell E-DCH Restriction
O

BOOLEAN
TRUE means restricted
FALSE means not restricted.
If not included in AUDIT RESPONSE message or in RESOURCE STATUS INDICATION message when the cell becomes existing, it means not restricted.
YES
ignore

Range bound
Explanation
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE. See NOTE below.
NOTE: In this case, “maxNrOfHSDSCH-1” represents the maximum number of possible secondary serving cells for a local cell.

9.2.2.114	Minimum Reduced E-DPDCH Gain Factor
The minimum gain factor  (βed,k,reduced,min) defined in TS 25.214 [10].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Minimum Reduced E-DPDCH Gain Factor


ENUMERATED  (8/15, 11/15, 15/15, 21/15, 30/15, 42/15, 60/15, 84/15, ...)


9.2.2.115	IMB Parameters
The IMB Parameters IE contains specific parameters needed for 3.84Mcps MBSFN IMB operation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Sub-frame number
M

INTEGER (0..4,…)

Last DL Channelisation Code Number
O

DL Channelisation Code Number 9.2.2.14
In case of IMB using multiple channelization codes this IE indicates the last one as defined TS 25.331 [18].

9.2.2.116	Common E-DCH HS-DPCCH Capability
This parameter defines the  HS-DPCCH capability for a Common E-DCH capable Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common E-DCH HS-DPCCH Capability


ENUMERATED (HS-DPCCH non-Capable, ACK-NACK Capable, ACK-NACK and CQI Capable)


9.2.2.117	UE Support Indicator Extension
The UE Support Indicator Extension IE is used to indicate the support level in the UE for optional HSDPA functions to the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UE support indicator extension


BIT STRING (SIZE(32))
Each bit indicates whether the UE supports a particular HSDPA function or not. The value 1 of a bit indicates that the corresponding functionality is supported in the UE and value 0 indicates that the corresponding functionality is not supported in the UE. Each bit is defined as follows:
the first bit: Different HS-SCCH In Consecutive TTIs Support Indicator,
the second bit: HS-SCCH orders in HS-SCCH-less Operation Support Indicator,
the third bit: RRC Rel-9 (onwards) handling of DL secondary HS-DSCH (de)activation state Support Indicator,
the fourth bit: UE DTXDRX related HS-SCCH orders uniform behavior indicator,
the fifth bit: UE longer HARQ processing time for simultaneous Multiflow and MIMO operation.
the sixth bit: UE Blind HARQ Retransmissions Indicator for HSDPA.

Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver.

9.2.2.118	MIMO Power Offset For S-CPICH Capability
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MIMO Power Offset For S-CPICH Capability


ENUMERATED (S-CPICH Power Offset Capable,  S-CPICH Power Offset Not Capable)


9.2.2.119	Power Offset For Secondary CPICH for MIMO
The Power Offset For Secondary CPICH for MIMO IE indicates the the relative transmit power of the S-CPICH compared to the primary CPICH transmit power, when S-CPICH is used as a phase reference for a second transmit antenna in MIMO mode TS 25.214 [10].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Power Offset For Secondary CPICH for MIMO


INTEGER(-6 .. 0)
Offset in dB

9.2.2.120	MIMO Pilot Configuration Extension
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Pilot Configuration
M



>Primary and Secondary CPICH




>> Power Offset For Secondary CPICH for MIMO
M

9.2.2.119

>Normal and Diversity Primary CPICH


NULL
This IE is not used in this release.

9.2.2.121	TX Diversity on DL Control Channels by MIMO UE Capability
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TX Diversity on DL Control Channels by MIMO UE Capability


ENUMERATED (DL Control Channel Tx Diversity for MIMO UE with non-diverse P-CPICH Capable, DL Control Channel Tx Diversity for MIMO UE with non-diverse P-CPICH Not Capable)


9.2.2.122	Single Stream MIMO Capability
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Single Stream MIMO Capability


ENUMERATED (Single Stream MIMO Capable,  Single Stream MIMO Non-Capable)


9.2.2.123	Single Stream MIMO Activation Indicator
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Single Stream MIMO Activation Indicator
M

NULL


9.2.2.124	Single Stream MIMO Mode Indicator
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Single Stream MIMO Mode Indicator


ENUMERATED (Activate,  Deactivate)


9.2.2.125	Dual Band Capability Info
This parameter defines the Dual Band capability information for a Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Dual Band Capability
M

ENUMERATED (Dual Band Capable, Dual Band non Capable)
For HS-DSCH
-

Possible Secondary Serving Cell List

0..<maxNrOfHSDSCH-1>

For secondary serving HS-DSCH cell.]
-

>Possible Secondary Serving Cell
M

Local Cell ID
9.2.1.38
Cells possible to serve in multicell HS-DSCH Dual Band operationTS 25.133 [22] (same sector)
-

>Multicell E-DCH Restriction
O

BOOLEAN
TRUE means restricted for E-DCH Dual Band operation
FALSE means not restricted.
If not included in AUDIT RESPONSE message or in RESOURCE STATUS INDICATION message when the cell becomes existing, it means not restricted.
YES
ignore
Dual Band E-DCH Capability
O

ENUMERATED (Dual Band E-DCH Capable, Dual Band E-DCH non Capable)
For E-DCH
YES
ignore

Range bound
Explanation
maxNrOfHSDSCH-1
Maximum number of Secondary Serving HS-DSCH cells for one UE. See NOTE below.
NOTE: In this case, “maxNrOfHSDSCH-1” represents the maximum number of possible secondary serving cells for a local cell.

9.2.2.126	Void
9.2.2.127	HS-DSCH MAC-ehs Format
Void.
9.2.2.128	Activation Information
The Activation Information IE defines the local activation state of the secondary uplink frequency of the UE in Dual Cell E-DCH operation, or the change request of activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation when E-DCH decoupling is configured.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description 
Activation Information

1..<maxNrOfEDCH-1 >
For secondary E-DCH. Max 1 in this 3GPP release.

>Uu Activation State
M

ENUMERATED
(Activated, 
De-activated, ..., Change Request)
The activation state of the secondary UL frequency, or change of the activation state of the secondary UL frequency when E-DCH decoupling is configured.

Range Bound
Explanation
maxNrOfEDCH-1
Maximum number of uplink frequencies -1 for E-DCH for one UE

9.2.2.129	Cell Capability Container
The Cell Capability Container IE indicates the cell capability by setting the corresponding bit in the BIT String.
The cell capability of multi-cell related functions may depend on that the cell is multi-cell capable (adjacent carrier and/or non-adjacent carrier) and/or Dual Band capable. Such capability indicators in this Cell Capability Container IE shall be ignored by the CRNC if the local cell does not have the required cell capability: "Multi Cell Capable" as indicated with Multi Cell Capability Info IE and/or "Dual Band Capable" as indicated with Dual Band Capability Info IE. Capability indicators that depend on multi-cell (adjacent carrier) capability are indicated in the table below with /Adjacent-carrier/. Capability indicators that depend on multi-cell (non-adjacent carrier ) capability are indicated in the table below with /Adjacent-carrier/ if the capability bit “Non-contiguous HSDPA operation Capability” is set. Capability indicators that depend on Dual Band capability are indicated in the table below with /Dual-band/. Capability indicators that depend on that the local cell has one or both of the capabilities multi-cell (adjacent carrier) and Dual Band are indicated in the table below with /Multi-cell/. Capability indicators that depend on that the local cell has one or both of the capabilities multi-cell (non-adjacent carrier) and Dual Band are indicated in the table below with /Multi-cell/ if the capability bit “Non-contiguous HSDPA operation Capability” is set. Cell Capability for the marked capabilities indicate capability regardless of the supported multi-cell type in a multicell configuration for the local cell: supported multi-cell type is - both serving HS-DSCH and secondary serving HS-DSCH, - secondary serving HS-DSCH or - serving HS-DSCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Cell Capability Container


BIT STRING (SIZE(128))
Each bit indicates whether a cell supports a particular functionality or not. The value 1 of a bit indicates that the corresponding functionality is supported in a cell and value 0 indicates that the corresponding functionality is not supported in a cell. Each bit is defined as follows.
The first bit: Cell Specific Tx Diversity Handling For Multi Cell Operation Capability /Multi-cell/.
The second bit: Multi Cell and MIMO Capability/Adjacent-carrier/.
The third bit: Multi Cell and Single Stream MIMO Capability/Adjacent-carrier/.
The fourth bit: Multi Cell E-DCH Capability/Adjacent-carrier/.
This bit shall be ignored by the CRNC if the fifth bit: Separate Iub Transport Bearer Capability = "0" and the sixth bit: E-DCH UL Flow Multiplexing  Capability = "0"
The fifth bit: Separate Iub Transport Bearer Capability/Adjacent-carrier/.
This bit shall be ignored by the CRNC if the fourth bit: Multi Cell E-DCH Capability = "0"
The sixth bit: E-DCH UL Flow Multiplexing  Capability/Adjacent-carrier/.  
This bit shall be ignored by the CRNC if the fourth bit: Multi Cell E-DCH Capability = "0"
The seventh to eleventh bit Maximum No of HSDPA Frequencies capability/Multi-cell/.
This capability is coded as the binary representation of the maximum number of HSDPA frequencies, with the seventh bit as the MSB and the eleventh bit as the LSB. Hexadecimal digit 0 means no support for 3 or more HSDPA.
Hexadecimal digits 1 and 2 are reserved.
The twelfth bit: Dual Band and MIMO Capability/Dual Band/.
The thirteenth bit: HSDPA 3 or more Carrier and MIMO Single Band Capability/Adjacent-carrier/
The fourteenth bit: HSDPA 3 or more Carrier and MIMO Dual Band Capability/Dual Band/.
The fifteenth bit: Dual band and Single Stream MIMO Capability/Dual Band/.
The sixteenth bit: HSDPA 3 or more Carrier and Single Stream MIMO Single Band Capability/Adjacent-Carrier/.
The seventeenth bit: HSDPA 3 or more Carrier and Single Stream MIMO Dual Band Capability/Dual Band/.
The eighteenth bit: Frequency Specific Compressed Mode Capability/Multi-Cell/.
The nineteenth bit: UL CLTD capability.
The twentieth bit: Non-contiguous HSDPA operation Capability.

The twenty-first bit to twenty-third bit: Supported MIMO transmit antennas (N). This capability is coded as the representation of the supported MIMO transmit antennas with the twenty-first bit as the MSB and the twenty-third bit as the LSB. Hexadecimal digit 0 means no support for more than 2 MIMO transmit antennas. Hexadecimal digit 2 means MIMO with four transmit antennas support.
Hexadecimal digit 1 is reserved. Undefined values are considered as spare.

The twenty-fourth bit: MIMO with N transmit antennas Capability Adjacent-carrier.
The twenty-fifth bit: MIMO with N transmit antennas Capability Dual Band/Dual Band.
The twenty-sixth bit: Multi Cell and MIMO with N transmit antennas Capability Adjacent-carrier.
The twenty-seventh bit: Multi Cell and MIMO with N transmit antennas Capability Dual Band/Dual Band.
The twenty-eighth bit: HSPA 3 or more Carrier and MIMO with N transmit antennas Capability Adjacent-carrier.
The twenty-ninth bit: HSPA 3 or more Carrier and MIMO with N transmit antennas Capability Dual Band/Dual Band.

This 3GPP release supports MIMO with four transmit antennas for up to 4 carriers.

The thirtieth bit:
Intra-Node B Multiflow.
The thirty-first bit:
Inter-Node B Multiflow.
The thirty-second to thirty fourth bits: Supported Multiflow configuration, where value 0 indicates support for one frequency two cells, value 1 indicates support for two frequencies three cells, value 2 indicates support for two frequencies four cells. Value 3 indicates support for three frequencies four cells. Values 4-7 are reserved for future use, 
The thirty-fifth bit: Multiflow and MIMO.
The thirty-sixth bit: Cell Specific Tx Diversity Handling For Multiflow Cell Operation
The thirty-seventh bit: Multiflow and single stream MIMO.

The thirty eighth bit: UL SixtyfourQAM capability.
The thirty ninth bit: UL MIMO capability.
The fortieth bit: UL MIMO and UL SixteenQAM capability.
The forty-first bit: UL MIMO and UL SixtyfourQAM capability.

The forty-second bit: NodeB Triggered HS-DPCCH Transmission Capability.
The forty-third bit: 2ms and 10ms TTI Concurrent Deployment Capability.
The forty-fourth bit: Further Enhanced UE DRX Capability.
The forty-fifth bit: Per HARQ Activation and Deactivation Capability.
The forty-sixth bit: TTI alignment Capability.
The forty-seventh bit: Common E-RGCH Capability.
The forty-eighth bit: Fallback to R99 PRACH Capability.
The forty-ninth bit: E-DCH decoupling operation Capability.
The fiftieth bit: Basic DCH Enhancements Capability [52].
The fifty-first bit: Full DCH Enhancements Capability [52].
The fifty-second bit: BCH mapped on SCCPCH Capability.

The fifty-third bit: Radio Links without DPCH/F-DPCH operation Capability.
The fifty-fourth bit: UL DPCCH2 operation Capability.
The fifty-fifth bit: feEUL TTI switching Node B Autonomous Capability.
The fifty-sixth bit: feEUL TTI switching RNC notify Capability.
The fifty-seventh bit: downlink TPC enhancements Capability.

The fifty-eighth bit: NAICS offloading Capability.

The fifty-ninth bit: Multi Cell E-DCH with DPDCH Capability.

Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver. Note that Reserved bits are not considered as a spare bit. They shall however be set to 0 by the transmitter and shall be ignored by the receiver.

9.2.2.130	Multicell E-DCH Transport Bearer Mode
This parameter indicates the Multicell E-DCH Transport Bearer Mode. For Multicell E-DCH Transport Bearer Mode  = "Separate Iub Transport Bearer Mode" the Mac-d flows from each carrier uses different Iub transport bearers, for Multicell E-DCH Transport Bearer Mode  = "UL Flow Multiplexing Mode" the Mac-d flows received on the different carriers in the Node B is multiplexed on one Iub transport bearer (per Mac-d flow). The CRNC should apply the stored cell capabilities for the cell on primary UL frequency for the capabilities related to Multicell E-DCH Transport Bearer Mode.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Multicell E-DCH Transport Bearer Mode


ENUMERATED (Separate Iub Transport Bearer Mode, UL Flow Multiplexing Mode)


9.2.2.131	Additional E-DCH FDD Setup Information
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
UL DPCH Information

1


–

>UL Scrambling Code
M

9.2.2.59

–

>UL SIR Target
M

UL SIR
9.2.1.67A

–

Additional E-DCH RL Specific Information To Setup
M

9.2.2.132

–

Additional E-DCH FDD Information
O

9.2.2.137

–

F-DPCH Information

1


–

>FDD TPC DL Step Size
M

9.2.2.16

–

>Limited Power Increase
M

9.2.2.18A

–

>Inner Loop DL PC Status
M

9.2.2.18B

–

Multicell E-DCH Information
O

9.2.2.140

YES
ignore

9.2.2.132	Additional E-DCH RL Specific Information To Setup
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-DCH Additional RL Specific Information

1..<maxnoofEDCHRLs>


–

>E-DCH Additional RL ID
M

RL ID
9.2.1.53

–

>C-ID
O

9.2.1.9

–

>First RLS Indicator
M

9.2.2.16A

–

>Propagation Delay
O

9.2.2.35

–

>DL Code Information
M

FDD DL Code Information 9.2.2.14A

–

>Initial DL Transmission Power
M

DL Power
9.2.1.21

–

>Maximum DL Power
M

DL Power
9.2.1.21

–

>Minimum DL Power
M

DL Power
9.2.1.21

–

>F-DPCH Slot Format
O

9.2.2.93

–

>E-RNTI 
O

9.2.1.75

–

>Multicell E-DCH RL Specific Information
O

9.2.2.142

YES
ignore
>TPC slot position
O

9.2.2.217

YES
ignore

Range bound
Explanation
maxnoofEDCHRLs
Maximum number of E-DCH RLs for one UE

9.2.2.133	Additional E-DCH RL Specific Information To Add
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-DCH Additional RL Specific Information To Add

1..<maxnoofEDCHRLs>


–

>E-DCH Additional RL ID
M

RL ID
9.2.1.53

–

>C-ID
M

9.2.1.9

–

>DL Code Information
M

FDD DL Code Information 9.2.2.14A

–

>Initial DL Transmission Power
O

DL Power
9.2.1.21

–

>Maximum DL Power
O

DL Power
9.2.1.21

–

>Minimum DL Power
O

DL Power
9.2.1.21

–

>F-DPCH Slot Format
O

9.2.2.93

–

>Multicell E-DCH RL Specific Information
O

9.2.2.142

YES
ignore
>TPC slot position
O

9.2.2.217

YES
ignore

Range bound
Explanation
maxnoofEDCHRLs
Maximum number of E-DCH RLs for one UE

9.2.2.134	Additional E-DCH RL Specific Information To Modify
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-DCH Addiional RL Specific Information To Modify

1..<maxnoofEDCHRLs>


–

>E-DCH Additional RL ID
M

RL ID
9.2.1.53

–

>DL Code Information
O

FDD DL Code Information 9.2.2.14A

–

>Maximum DL Power
O

DL Power
9.2.1.21

–

>Minimum DL Power
O

DL Power
9.2.1.21

–

>F-DPCH Slot Format
O

9.2.2.93

–

>Multicell E-DCH RL Specific Information
O

9.2.2.142

YES
ignore
>TPC slot position
O

9.2.2.217

YES
ignore

Range bound
Explanation
maxnoofEDCHRLs
Maximum number of E-DCH RLs for one UE

9.2.2.135	Additional E-DCH FDD Information Response
The Additional E-DCH FDD Information Response IE provides information for new E-DCH radio links on the secondary UL frequency.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH Additional RL Specific Information Response

0..<maxnoofEDCHRLs>


>E-DCH Additional RL ID
M

RL ID
9.2.1.53

>Received Total Wide Band Power
M

9.2.2.39A

>DL Power Balancing Activation Indicator
O

9.2.2.12C

>RL Set ID
M

9.2.2.39

>E-DCH RL Set ID
M

RL Set ID
9.2.2.39

>E-DCH FDD DL Control Channel Information
M

9.2.2.13Dc

Additiona E-DCH MAC-d Flow Specific Information Response

0..<maxNrOfEDCHMACdFlows>


>E-DCH MAC-d Flow ID
M

9.2.1.74

>Binding ID
O

9.2.1.4

>Transport Layer Address
O

9.2.1.63

HARQ Process Allocation For 2ms Scheduled Transmission Grant
O

HARQ Process Allocation for 2ms TTI
9.2.2.13Dn


Range bound
Explanation
maxnoofEDCHRLs
Maximum number of E-DCH RLs for one UE
maxNrOfEDCHMACdFlows
Maximum number of MAC-d flows.

9.2.2.136	Additional E-DCH Configuration Change Information
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
UL DPCH Information

0..1


–

>UL Scrambling Code
O

9.2.2.59

–

>UL SIR Target
O

UL SIR
9.2.1.67A

–

Additional E-DCH RL Specific Information To Add
O

9.2.2.133
Used when the E-DCH RL to add does not exist in the current Node B Communication Context on the secondary UL frequency.
–

Additional E-DCH RL Specific Information To Modify 
O

9.2.2.134
Used when an existing E-DCH RL on the secondary UL frequency is modified.
–

Additional E-DCH FDD Information To Modify
O

Additional E-DCH FDD Information 9.2.2.137
Used to modify the current additional E-DCH configuration with or without a new RL added in this procedure
–

F-DPCH Information

0..1


–

>FDD TPC DL Step Size
M

9.2.2.16

–

>Limited Power Increase
M

9.2.2.18A

–

>Inner Loop DL PC Status
M

9.2.2.18B

–

Multicell E-DCH Information
O

9.2.2.140

YES
ignore

9.2.2.137	Additional E-DCH FDD Information
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Additional E-DCH MAC-d Flows Specific Information

0..<maxNrOfEDCHMACdFlows>




>E-DCH MAC-d Flow ID
M

9.2.1.74

–

>Binding ID 
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP
–

>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP
–

HARQ Process Allocation For 2ms Scheduled Transmission Grant
O

HARQ Process Allocation for 2ms TTI
9.2.2.13Dn

–

E-DCH Maximum Bitrate 
O

9.2.2.13T

–

E-DCH Processing Overload Level
O

9.2.1.79

–

E-DCH Minimum Set E-TFCI
O

INTEGER (0..127)
For the concept of "E-DCH Minimum Set of TFCs" see TS 25.321 [32] and TS 25.331 [18]
–

DTX Information2

0..1




>UE DTX Cycle 1
M

ENUMERATED (v1, v4, v5, v8, v10, v16, v20,…)
Units of subframes, refer to TS 25.331 [16].
YES
ignore
>UE DTX Cycle 2
M

ENUMERATED (v4, v5, v8, v10, v16, v20, v32, v40, v64, v80, v128, v160, v256, v320, v512, v640, v1024, v1280,…)
Units of subframes, refer to TS 25.331 [16].
YES
ignore
>Inactivity Threshold for UE DTX Cycle 2
M

ENUMERATED (v1, v4, v8, v16, v32, v64, v128, v256,…)
Units of E-DCH TTIs, refer to TS 25.331 [16].
YES
ignore
Implicit Grant handling
O

ENUMERATED (true)
The presence of this information element indicates that Implicit Grant handling is configured on the secondary uplink frequency
YES
ignore
Minimum TEBS threshold
O

ENUMERATED (v2, v4, v8, v16, v32, v64, v128, v256, v512, v1024, v2K, v4K, v8K, v16K, v32K, v64K, v128K, v256K, v512K, v1024K,...)
In bytes
And N Kbytes = N*1024 bytes. Twelve spare values are needed, refer to TS 25.331 [16].
YES
ignore

Range bound
Explanation
maxNrOfEDCHMACdFlows
Maximum number of MAC-d flows.

9.2.2.138	Additional E-DCH FDD Update Information
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HARQ Process Allocation For 2ms Scheduled Transmission Grant
O

HARQ Process Allocation for 2ms TTI
9.2.2.13Dn

Additional E-DCH DL Control Channel Change Information

0..<maxnoofEDCHRLs>


>E-DCH Additional RL ID 
M

RL ID
9.2.1.53


Range bound
Explanation
maxnoofEDCHRLs
Maximum number of E-DCH RLs for one UE

9.2.2.139	E-RNTI List
The E-RNTI List IE provides the list of E-RNTIs which can be allocated by CRNC.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-RNTI List

1..<maxnoofERNTIs>


>E-RNTI
M

9.2.1.75


Range bound
Explanation
MaxnoofERNTIs
Maximum number of ERNTIs that can be allocated by the CRNC

9.2.2.140	Multicell E-DCH Information
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL Power Balancing Information
O

9.2.2.12B

Minimum Reduced E-DPDCH Gain Factor
O

9.2.2.114

Secondary UL Frequency Activation State
O

ENUMERATED (Activated, Deactivated,...)
Activation state signalled to Node B at setup of RL on secondary UL frequency

9.2.2.141	Additional Modified E-DCH FDD Information Response
The Additional Modified E-DCH FDD Information Response IE provides information for RLs on the secondary UL frequency that has been modified and existied in the Node B Communication Context configuration before the reconfiguration procedure.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH Additional Modified RL Specific Information Response

0..<maxnoofEDCHRLs>


>E-DCH Additional RL ID
M

RL ID
9.2.1.53

>DL Power Balancing Updated Indicator
O

9.2.2.12D

>E-DCH FDD DL Control Channel Information
O

9.2.2.13Dc

Additional E-DCH MAC-d Flow Specific Information Response

0..<maxNrOfEDCHMACdFlows>


>E-DCH MAC-d Flow ID
M

9.2.1.74

>Binding ID
O

9.2.1.4

>Transport Layer Address
O

9.2.1.63

HARQ Process Allocation For 2ms Scheduled Transmission Grant
O

HARQ Process Allocation for 2ms TTI
9.2.2.13Dn


Range bound
Explanation
maxnoofEDCHRLs
Maximum number of E-DCH RLs for one UE
maxNrOfEDCHMACdFlows
Maximum number of MAC-d flows.

9.2.2.142	Multicell E-DCH RL Specific Information
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Extended Propagation Delay
O

9.2.2.35A

Primary CPICH Usage For Channel Estimation
O

9.2.2.33A

Secondary CPICH Information
O

Common Physical Channel ID 9.2.1.13

Secondary CPICH Information Change
O

9.2.2.43A

E-AGCH Power Offset
O

9.2.2.13Id

E-RGCH Power Offset
O

9.2.2.13Ie

E-HICH Power Offset
O

9.2.2.13If

DL Reference Power
O

DL power
9.2.1.21
Power on DPCH or on
F-DPCH
E-DCH DL Control Channel Grant
O

NULL


9.2.2.143	Precoding Weight Set Restriction
This parameter defines the preferred precoding weight set restriction configuration as defined in TS 25.331 [18].

IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Precoding Weight Set Restriction


ENUMERATED (Preferred, Not Preferred)


9.2.2.144	Non-Serving RL Preconfiguration Setup
The Non-Serving RL Preconfiguration Setup IE indicates that the Node B may preconfigure E-DCH DL Code Information configured for new non-serving RL for Enhanced Service Cell Change and contains the information for the location of new serving RL after the Enhanced Serving Cell Change.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
CHOICE new Serving RL
M



–

>New Serving RL in the Node B


NULL

–

>New Serving RL Not in the Node B


NULL

–

>New Serving RL in the Node B or New Serving RL Not in the Node B


NULL

–

Additional E-DCH Non-Serving RL Preconfiguration Setup 
O

NULL

YES
ignore
F-TPICH Information
O

9.2.2.160

YES
ignore

9.2.2.145	Non-Serving RL Preconfiguration Info
The Non-Serving RL Preconfiguration Info IE provides information for the new non-serving RL after Enhanced Serving Cell Change.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
New non-serving RL E-DCH FDD DL Control Channel Information A
O

9.2.2.13Dc
E-DCH FDD DL Control Channel Information
E-DCH FDD DL Control Channel Information for non-serving RL in Serving E-DCH RLS    
–

New non-serving RL E-DCH FDD DL Control Channel Information B
O

9.2.2.13Dc
E-DCH FDD DL Control Channel Information
E-DCH FDD DL Control Channel Information for non-serving RL in non serving E-DCH RLS in case serving RL is in the Node 
–

New non-serving RL E-DCH FDD DL Control Channel Information C
O

9.2.2.13Dc
E-DCH FDD DL Control Channel Information
E-DCH FDD DL Control Channel Information for non-serving RL in case serving RL is not in the Node B

–

Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information

0..<maxNrOfEDCH-1>

E-DCH on Secondary uplink frequency - max 1 in this 3GPP release.
EACH
ignore
>New non-serving RL E-DCH FDD DL Control Channel Information A
O

9.2.2.13Dc
E-DCH FDD DL Control Channel Information
E-DCH FDD DL Control Channel Information for Additional non-serving RL in Serving E-DCH RLS  
–

>New non-serving RL E-DCH FDD DL Control Channel Information B
O

9.2.2.13Dc
E-DCH FDD DL Control Channel Information
E-DCH FDD DL Control Channel Information for Additional non-serving RL in non serving E-DCH RLS in case Additional serving RL is in the Node B
–

>New non-serving RL E-DCH FDD DL Control Channel Information C
O

9.2.2.13Dc
E-DCH FDD DL Control Channel Information
E-DCH FDD DL Control Channel Information for Additional non-serving RL in case Additional serving RL is not in the Node B
–


9.2.2.146	Void
9.2.2.147	Usefulness of Battery Optimization
This IE, when present, indicates whether the device can benefit from UTRAN-based battery consumption optimisation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Usefulness of Battery Optimization


Enumerated (
CanBenefit,
CannotBenefit
)


9.2.2.148	Common HS-DSCH RNTI List
The Common HS-DSCH RNTI List IE provides the list of Common HS-DSCH RNTIs.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common HS-DSCH RNTI List

1..<maxnoofCommonHRNTIs>


>Common HS-DSCH RNTI
M

HS-DSCH RNTI
9.2.1.31J


Range bound
Explanation
maxnoofCommonHRNTIs
Maximum number of Common HS-DSCH RNTIs for a cell

9.2.2.149	Puncturing Handling in First Rate Matching Stage
This parameter provides the puncturing handling information in first rate matching stage.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Puncturing Handling in First Rate Matching Stage
M

BOOLEAN
True = No Puncturing in first rate matching stage
False = Normal handling 
If not included: when HS-DSCH is setup, or when HS-DSCH is modified and the puncturing handling is not configured in the Node B Communication Context, value False applies.

9.2.2.150	Support of Dynamic DTXDRX Related HS-SCCH Order
The Support of dynamic DTXDRX related HS-SCCH order IE is to indicate if Node B supports the DRX/DTX related HS-SCCH order for CPC non-uniform UE.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Support of dynamic DTXDRX related HS-SCCH order


ENUMERATED (Supported,Not Supported)


9.2.2.151	UL CLTD Information Reconf
The UL CLTD Information Reconf IE is used for the reconfiguration of the UL CLTD operation in a UE context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Setup, Configuration Change or Removal of UL CLTD

1


>Setup



Used when UL CLTD is not configured in the current UE Context
>>UL CLTD Information
M

9.2.2.152

>Configuration Change



Used when the existing UL CLTD configuration in the current UE context is modified 
>>UL CLTD information To Modify
M

9.2.2.153

>Removal



Used when the existing UL CLTD configuration in the current UE context is removed.
>>UL CLTD information Removal
M

9.2.2.154


9.2.2.152	UL CLTD Information
The UL CLTD Information IE defines the parameters used for UL CLTD operation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
S-DPCCH Power Offset Information
M

9.2.2.158

C-ID
C-DCHorMultiflow

9.2.1.9

UL CLTD Activation Information
O

9.2.2.159


Condition
Explanation
DCHorMultiflow
The IE shall be present if there is no serving E-DCH RL or HS-DSCH RL configuration in the concerned Node B Communication Context. If the Multiflow operation is configured, then this IE may indicate the Multiflow assisting serving cell.

9.2.2.153	UL CLTD Information To Modify 
The UL CLTD information To Modify IE is used for modification of UL CLTD information in a UE Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
S-DPCCH Power Offset Information
O

9.2.2.158

UL CLTD Activation Information
O

9.2.2.159


9.2.2.154	UL CLTD Information Removal
The UL CLTD Information Removal IE is used for removal of UL CLTD information in a UE Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL CLTD Information Removal


ENUMERATED (Remove, ...)


9.2.2.155	UL CLTD State Update Information
The UL CLTD State Update Information IE provides information for the activation state of UL CLTD of the UE to be updated.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description 
UL CLTD State Update Information


ENUMERATED
(Activate,De-activate, ...)
The suggested UL CLTD activation state.

9.2.2.156	F-TPICH Slot Format
Indicates the slot format used in F-TPICH in DL, accordingly to ref. TS 25.211 [7].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
F-TPICH Slot Format


INTEGER (0..9,…)


9.2.2.157	F-TPICH Offset
The F-TPICH Offset is defined as the time offset towards the Primary CCPCH in the cell. The offset is a multiple of 256 chips.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
F-TPICH Offset


INTEGER (0..149)
Range: 0..38144 chips
Step: 256 chips
See ref. TS 25.211 [7]

9.2.2.158	S-DPCCH Power Offset Information
The S-DPCCH Power Offset is used to calculate the S-DPCCH gain factor, -sc, as defined in TS 25.214 [9], whereas    sccis related to the power difference between DPCCH and S-DPCCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
S-DPCCH Power Offset Information


INTEGER (0..6,...)
According to mapping in ref. TS 25.213 [9] subclause 4.2.1.4.

9.2.2.159	UL CLTD Activation Information
The UL CLTD Activation Information IE defines the activation state of the UE in UL CLTD operation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description 
>UL CLTD Activation State
M

ENUMERATED
(Activated, 
De-activated, ...)
The activation state of the UL CLTD.

9.2.2.160	F-TPICH Information
The F-TPICH Information IE defines the parameters used for F-TPICH cofiguration.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
F-TPICH Slot Format
M

9.2.2.156

F-TPICH Offset 
M

9.2.2.157

F-TPICH Channelisation Code Number
M

FDD DL Channelisation Code Number 9.2.2.14


9.2.2.161	F-TPICH Information To Modify
The F-TPICH Information To Modify IE is used for modification of F-TPICH configuration.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
F-TPICH Slot Format
O

9.2.2.156

F-TPICH Offset 
O

9.2.2.157

F-TPICH Channelisation Code Number
O

FDD DL Channelisation Code Number 9.2.2.14


9.2.2.162	F-TPICH Information Removal
The F-TPICH Information Removal IE is used for removal of F-TPICH information of a RL.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
F-TPICH Information Removal


ENUMERATED (Remove, ...)


9.2.2.163	F-TPICH Information Reconf
The F-TPICH Information Reconf IE is used for the reconfiguration of the UL CLTD operation of a RL.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Setup, Configuration Change or Removal of F-TPICH Information

1


>Setup



Used when F-TPICH is not configured in the current RL
>>F-TPICH Information
M

9.2.2.160

>Configuration Change



Used when the existing UL F-TPICH configuration in the current RL is modified 
>>F-TPICH Information To Modify
M

9.2.2.161

>Removal



Used when the existing UL F-TPICH in the current RL is removed.
>>F-TPICH information Removal
M

9.2.2.162


9.2.2.164	MIMO with four transmit antennas Activation Indicator
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MIMO with four transmit antennas Activation Indicator
M

NULL


9.2.2.165	MIMO with four transmit antennas Pilot Configuration
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Pilot Configuration
M



>Primary and Secondary CPICH




>>Secondary CPICH

1..<maxSCPICHCell>

The 3rd and the 4th S-CICH should have the same power offset;
The 3rd and the 4th D-CPICH should have the same power offset.
>>>Associated Secondary CPICH
M

Common Physical Channel ID 9.2.1.13

>>>Power Offset For Associated Secondary CPICH
O

INTEGER (-12..0)

>>>Associated D-CPICH
O

Common Physical Channel ID 9.2.1.13

>>>Power Offset For Associated D-CPICH
O

INTEGER (-12..0)

>Normal and Diversity Primary CPICH


NULL


Range Bound
Explanation
maxSCPICHCell
Maximum number of Secondary CPICHs that can be defined in a Cell.

9.2.2.166	MIMO with four transmit antennas Mode Indicator
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MIMO with four transmit antennas Mode Indicator


ENUMERATED (Activate,  Deactivate)


9.2.2.167	Dual Stream MIMO with four transmit antennas Activation Indicator
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Four Stream MIMO with four transmit antennas Activation Indicator
M

NULL


9.2.2.168	Dual Stream MIMO with four transmit antennas Mode Indicator
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Dual Stream MIMO with four transmit antennas Mode Indicator


ENUMERATED (Activate,  Deactivate)


9.2.2.169	Multiflow Reconfiguration
The Multiflow Reconfiguration IE is used setup, reconfigure, and stop Multiflow operation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Setup, or Change, or Stop 

1


>Setup



Used when Multiflow is not configured.
>>Multiflow Information
M

9.2.2.170

>Change



Used when Multiflow configuration changes.
>>Multiflow Information To Modify
M

9.2.2.171

>Stop



Used when the existing Multiflow configuration is removed.
>>Multiflow Stop
M

9.2.2.172


9.2.2.170	Multiflow Information
The Multiflow Information IE defines parameters to setup Multiflow operation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Total number of HS-DSCH cells
M

INTEGER (2..32,...)
Total number of HS-DSCH cells configured for Multiflow.
-

Role
M

Multiflow Role 9.2.2.173

-

MIMO
M

Multiflow MIMO 9.2.2.174

-

Timing
O

Multiflow Timing 9.2.2.175
In the inter-Node B Multiflow case, if present, this IE provides the timing information.
-

Max number of HS-SCCH sets per Node B
O

INTEGER (1..16,...)
Maximum number of HS-SCCH that can be allocated per Node B.
-

Assisting repetition factors 
O

Multiflow Repetition Factors 9.2.2.193
Additional HS-DPCCH repetition factors
YES
ignore

9.2.2.171	Multiflow Information To Modify
The Multiflow Information To Modify IE defines parameters to reconfigure Multiflow operation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Total number of HS-DSCH cells
O

INTEGER (2..32,...)
Total number of HS-DSCH cells configured for Multiflow.
-

Role
O

Multiflow Role 9.2.2.173

-

MIMO
O

Multiflow MIMO 9.2.2.174

-

Timing
O

Multiflow Timing 9.2.2.175
In the inter-Node B Multiflow case, if present, this IE provides the timing information.
-

Max number of HS-SCCH sets per Node B
O

INTEGER (1..16,...)
Maximum number of HS-SCCH that can be allocated per Node B.
-

Assisting repetition factors 
O

Multiflow Repetition Factors 9.2.2.193
Additional HS-DPCCH repetition factors
YES
ignore

9.2.2.172	Multiflow Stop
The Multiflow Stop IE is used when the Multiflow operation is terminated.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Multiflow Stop


ENUMERATED (Stop, ...)


9.2.2.173	Multiflow Role
The Multiflow Role IE is used to specify primary or assisting Multiflow operation mode.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Multiflow Role


ENUMERATED (Primary, Assisting, ...)
This IE indicates whether Node B is configured with the primary serving HS-DSCH cell or assisting serving HS-DSCH cell.

9.2.2.174	Multiflow MIMO
The Multiflow MIMO IE is used to specify whether MIMO is configured for at least one of the cells.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Multiflow MIMO


ENUMERATED (ON, OFF, ...)


9.2.2.175	Multiflow Timing
The Multiflow Timing IE is used to specify timing information for the Multiflow operation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Time Reference, or Non-time Reference

1


>Time Reference


NULL
This indicates that the cell in the Multiflow time-reference cell (refer to TS 25.211, sub-clause 7.7.1).
>Non-time Reference


INTEGER
(0..30,...)
Unit: chip
Range: 0..7680 chips
Step: 256 chips

This IE indicates that the cell is a non-time reference cell. The value corresponds to the smallest TTX_diff value of the time reference cell (refer to TS25.211, sub-clause 7.7.1) and is used to calculate the HS-DPCCH to UL DPCCH timing difference in the non-time reference cell (refer to TS 25.211, sub-caluse 7.7.2).

9.2.2.176	UL MIMO Reconfiguration
The UL MIMO Reconfiguration IE is used for the reconfiguration of the UL MIMO operation in a UE context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Setup, Configuration Change or Removal of UL MIMO

1


>Setup



Used when UL MIMO is not configured in the current UE Context.
>>UL MIMO Information
M

9.2.2.177

>Configuration Change



Used when the existing UL MIMO configuration in the current UE context is modified.
>>UL MIMO information To Modify
M

9.2.2.178

>Removal



Used when the existing UL MIMO configuration in the current UE context is removed.
>>UL MIMO Removal
M

9.2.2.179


9.2.2.177	UL MIMO Information
The UL MIMO Information IE defines the parameters used for UL MIMO operation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-ROCH Power Offset
O

9.2.2.181

S-E-DPCCH Power Offset 
M

9.2.2.182

Inter-stream Interference Compensation Index
M

9.2.2.183

Minimum E-TFCI for rank 2 transmissions
M

INTEGER (0..127)
For the concept of "Minimum TB size for rank 2 transmissions" see TS 25.321 [32] and TS 25.331 [18].

9.2.2.178	UL MIMO Information To Modify 
The UL MIMO information To Modify IE is used for modification of UL MIMO information in a UE Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-ROCH Power Offset
O

9.2.2.181

S-E-DPCCH Power Offset 
O

9.2.2.182
According to AS-E-DPCCH mapping in ref. TS 25.213 [9] subclause 4.2.1.5.
Inter-stream Interference Compensation Index
O

9.2.2.183

Minimum E-TFCI for rank 2 transmissions
O

INTEGER (0..127)
For the concept of "Minimum TB size for rank 2 transmissions" see TS 25.321 [32] and TS 25.331 [18].

9.2.2.179	UL MIMO Removal
The UL MIMO Removal IE is used for removal of UL MIMO information in a UE Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL MIMO Removal


ENUMERATED (Remove, ...)


9.2.2.180	UL MIMO DL Control Channel Information
UL MIMO DL Control Information contains the Node B allocation of the UL MIMO specific DL control channels. Secondary Transport Block E-HICH Signature Sequence is used to acknowledge the secondary transport block transmitted in the uplink, and it uses the same channelization code as the E-HICH used for non-MIMO and primary transport block acknowledgements. E-ROCH Channelization Code is selected from the pool allocated for E-AGCH codes.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-ROCH Channelization Code
O

FDD DL Channelisation Code Number
9.2.2.14
Should be present for the serving E-DCH cell only
Secondary Transport Block E-RNTI
O

E-RNTI 9.2.1.75
E-ROCH S-E-RNTI as defined in ref. TS 25.212 [8] subclause 4.10A
Secondary Transport Block E-HICH Signature Sequence
O

INTEGER (0..maxnoofSigSeqE-RGHICH - 1)
One Secondary TB E-HICH signature sequence should be present at least for the serving E-DCH cell
Secondary Transport Block E-HICH Release Indicator
O

9.2.2.184


Range Bound
Explanation
maxnoofSigSeqE-RGHICH
Maximum number of Signature Sequences for E-RGCH/E-HICH.

9.2.2.181	E-ROCH Power Offset
The E-ROCH Power Offset IE indicates the power offset relative to the pilot bits.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-ROCH Power Offset


INTEGER (0…255,…)
Unit: dB
Range: -32 .. +31.75 dB
Step: 0.25 dB

9.2.2.182	S-E-DPCCH Power Offset
The S-E-DPCCH Power Offset is used to calculate the S-E-DPCCH gain factor Esec as defined in TS 25.214 [10], whereas  sec is related to the power difference between DPCCH and S-E-DPCCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
S-E-DPCCH Power Offset


INTEGER (0..17,...)
According to AS-E-DPCCH mapping in ref. TS 25.213 [9] subclause 4.2.1.5.

9.2.2.183	Inter-stream Interference Compensation Index
The Inter-stream Interference Compensation Index IE indicates an offset that a UE applies while performig the E-TFC selection for the primary stream.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Inter-stream Interference Compensation Index


INTEGER (0..15,...)
According to AISIImapping in ref. TS 25.213 [9] subclause 4.2.1.3.

9.2.2.184	Secondary Transport Block E-HICH Release Indicator
Indicates the release of the Uplink MIMO transmission’s Secondary Transport Block E-HICH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Secondary Transport Block E-HICH Release Indicator


ENUMERATED (Secondary Transport Block E-HICH released)


9.2.2.185	Further Enhanced UE DRX Information
The Further Enhanced UE DRX Information IE provides information for configuring the UE in Cell_FACH state to discontinuously receive HS-DSCH with the second DRX cycle.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH second DRX cycleFACH
M

ENUMERATED
 (4, 8, 16, 32, 64, 128, 256, 512)
Determines the length of the DRX Cycle during second DRX operation, in frames.
CHOICE DRX level
M


This IE indicates whether both the 1st and the 2nd DRX cycle are used (2-level DRX) or only the 2nd DRX cycle is used (1-level DRX).
>1-level DRX




>> HS-DSCH second Rx burstFACH
O

ENUMERATED
 (1,2)
Determines the period within the second DRX Cycle that the UE continuously receives HS-DSCH, in frames.
>>T32y
O

ENUMERATED
 (0.5,1,2,4)
Determines the time the UE waits until initiating the Second DRX operation, in seconds.
>2-level DRX




>>T32x
O

ENUMERATED
 (20,40,60,80)
Determines the time the UE waits until initiating the first DRX operation, in ms.
>>HS-DSCH first Rx burstFACH
O

ENUMERATED
 (0.4,0.8)
Determines the period within the first DRX Cycle that the UE continuously receives HS-DSCH, in frames.
>>HS-DSCH first DRX cycleFACH
O

ENUMERATED
 (2,4,8,16,32,64)
Determines the length of the DRX Cycle during first DRX operation, in frames.
>>HS-DSCH second Rx burstFACH
O

ENUMERATED
 (1,2)
Determines the period within the second DRX Cycle that the UE continuously receives HS-DSCH, in frames.
>>T32y
O

ENUMERATED
 (0.5,1,2,4)
Determines the time the UE waits until initiating second DRX operation, in seconds.

9.2.2.186	Common E-DCH Preamble Control Information extension list
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common E-DCH Preamble Control Information extension list

1 to < maxnoofPRACHEUL >


>Common E-DCH Preamble Control Information extension
M

Common E-DCH Preamble Control Information extension 9.2.2.187


Range bound
Explanation
maxnoofPRACHEUL
Maximum number of Common E-DCH Preamble Control Information extension for a cell.

9.2.2.187	Common E-DCH Preamble Control Information extension
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common Physical Channel ID
M

9.2.1.13

Scrambling Code Number
M

9.2.2.42

Common E-DCH Preamble Signature
M

Preamble Signatures 9.2.2.31

Preamble Threshold
M

9.2.2.32

Common E-DCH AICH Information
O

9.2.2.188


9.2.2.188	Common E-DCH AICH Information
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common Physical Channel ID
M

9.2.1.13

AICH Transmission Timing
M

9.2.2.1

FDD DL Channelisation Code Number
M

9.2.2.14

AICH Power
M

9.2.2.D

STTD Indicator
M

9.2.2.48


9.2.2.189	Common E-RGCH Info
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-RGCH Channelisation Code
M

FDD DL Channelisation Code Number
9.2.2.14

E-RGCH Signature Sequence
M

INTEGER (0..maxnoofSigSeqE-RGHICH - 1)

Minimum Serving Grant 
O

INTEGER (0..37,38)
(0..37) indicates E-DCH serving grant index as defined in TS 25.321 [32]. Index 38 is not allowed.

Range bound
Explanation
maxnoofSigSeqE-RGHICH
Maximum number of Signature Sequences for E-RGCH/E-HICH.

9.2.2.190	Common E-DCH HS-DPCCH Information for Concurrent TTI
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
ACK-NACK Repetition Factor
M

9.2.2.a

ACK Power Offset
M

9.2.2.b

NACK Power Offset
M

9.2.2.23a

Common E-DCH CQI Information
O



>CQI Feedback Cycle k
M

9.2.2.21B

>CQI Repetition Factor
C-CQICyclek

9.2.2.4Cb

>CQI Power Offset
M

9.2.2.4Ca

>Measurement Power Offset
M

9.2.2.21C


Condition
Explanation
CQICyclek
The IE shall be present if the CQI Feedback Cycle k IE is set to a value greater than 0.

9.2.2.191	Common E-DCH system info parameters for Concurrent TTI
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Maximum Set of E-DPDCHs
M

9.2.2.20C

Puncture Limit
M

9.2.1.50

E-TFCS Information
M

9.2.2.13Dh

E-DPCCH Power Offset
 O

9.2.2.13Dj

E-RGCH 2-Index-Step Threshold
O

9.2.2.13Ig

E-RGCH 3-Index-Step Threshold
O

9.2.2.13Ih

E-DCH Reference Power Offset
O

9.2.2.13Y

E-DCH Power Offset for Scheduling Info
O

9.2.1.85

Maximum E-DCH resource allocation for CCCH Extension
O

ENUMERATED (8, 12, 16, 20,24, 32, 40, 80, …)
Interms of TTIs
Maximum period for collision resolution phase
O

INTEGER (8..24,...)
Interms of TTIs
Maximum TB Sizes
O

9.2.2.106

Common E-DCH Additional Transmission Back Off
O

INTEGER (0..15,...)

Common E-DCH E-AGCH Channelisation Code Number
O

FDD DL Channelisation Code Number
9.2.2.14

Common E-DCH HS-DPCCH Information for Concurrent TTI
O

9.2.2.190


9.2.2.192	Precoder weight set restriction
This parameter defines the preferred precoding weight set restriction configuration as defined in TS 25.214 [10].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Precoder weight set restriction


BIT STRING (SIZE(64))
Each bit indicates whether a code in the Codebook is supported or not. The value 1 of a bit indicates that the corresponding code in the codebook is supported and value 0 indicates that the corresponding code in the Codebook is not supported.

Note:The Bit mapping is as defned in TS 25.331 [18]. If the bit has no corresponding code in the Codebook, it is set to 0.

9.2.2.193	Multiflow Repetition Factors
The Multiflow Repetition Factors IE is used to indicate repetition factors for the HS-DPCCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Assisting CQI Repetition Factor
O

CQI Repetition Factor 9.2.2.4Cb
In the intra-NodeB Multiflow case, if present, this IE provides the Node B with the number of repetitions of the assisting QCI information in the HS-DPCCH [10]. 
Assisting ACK-NACK Repetition Factor
O

ACK-NACK Repetition Factor 9.2.2.a
In the intra-Node B Multiflow case, if present, this IE provides the Node B with the number of repetitions of the assisting ACK-NACK information in the HS-DPCCH [10].

9.2.2.194	E-DCH Decoupling Indication
The E-DCH Decoupling Indication IE indicates the role of cell will be changed to Serving E-DCH cell only or Serving HS-DSCH cell only.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH Decoupling Indication
M

ENUMERATED (Serving E-DCH cell only, Serving HS-DSCH cell only, ...)
This IE indicates whether the related cell in Node B is configured to Serving E-DCH cell only or Serving HS-DSCH cell only for E-DCH decoupling operation.

9.2.2.195	DCH Enhancements Information Reconf
The DCH Enhancements Information Reconf IE is used for the reconfiguration of the DCH Enhancements [52] operation in a UE context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Setup, Configuration Change or Removal of DCH Enhancements




>Setup



Used when DCH Enhancements are not configured in the current UE Context
>>DCH Enhancements Information
M

9.2.2.196

>Configuration Change



Used when the existing DCH Enhancements configuration in the current UE context is modified 
>>DCH Enhancements Information to Modify
M

9.2.2.197

>Removal



Used when the existing DCH Enhancements configuration in the current UE context is removed.
>>DCH Enhancements information Removal
M

9.2.2.198


9.2.2.196	DCH Enhancements Information
The DCH Enhancements Information IE defines the parameters used for DCH Enhancements operation [52].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
PO-SRB
M

Power Offset
9.2.2.29
Power boost to be applied to the DL DPDCH under the conditions defined in [10].
DL FET Mode
M

ENUMERATED (basic,
full,
…)
Indicates the DCH Enhancements configuration mode, as defined in TS 25.300.
DL DCH Concatenation
C-FET
1..<maxNrOfConcatenatedDCH>

If present, this IE provides the list of DL Transport Channels that are subject to concatenation in the physical layer [8].
>DCH ID
M

9.2.1.20


Condition
Explanation
FET
The IE shall be present if the DL FET Mode IE is set to "full".

Range Bound
Explanation
maxNrOfConcatenatedDCH
Maximum number of concatenated DCHs.

9.2.2.197	DCH Enhancements Information to Modify
The DCH Enhancements Information to Modify IE is used for modification of DCH Enhancements information in a UE Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
PO-SRB
O

Power Offset
9.2.2.29
Power boost to be applied to the DL DPDCH under the conditions defined in [10].
DL FET Mode
O

ENUMERATED (basic, 
full,
…)
Indicates the DCH Enhancements configuration mode, as defined in TS 25.300 [52].
DL DCH Concatenation
C-FET
1..<maxNrOfConcatenatedDCH>

If present, this IE provides the list of DL Transport Channels that are subject to concatenation in the physical layer [8].
>DCH ID
M

9.2.1.20


Condition
Explanation
FET
The IE shall be present if the DL FET Mode IE is present and set to "full".

Range Bound
Explanation
maxNrOfConcatenatedDCH
Maximum number of concatenated DCHs.

9.2.2.198	DCH Enhancements Information Removal
The DCH Enhancements Information Removal IE is used for removal of DCH Enhancements information in a UE Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DCH Enhancements Information Removal


ENUMERATED (Remove, ...)


9.2.2.199	Gain Factors 10ms Mode
The Gain Factors 10ms Mode IE is used to configure the gain factors in 10ms Transmission Mode [10].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Gain Factors 10ms




>Signalled Gain Factors 10ms




>>Gain Factor 10ms >C
M

INTEGER (0..15)
For UL DPCCH in FDD with 10ms Transmission Mode; mapping in accordance to TS 25.213 [9]
>>Gain Factor 10ms >D
M

INTEGER (0..15)
For UL DPCCH in FDD with 10ms Transmission Mode; mapping in accordance to TS 25.213 [9]
>>Reference TFC nr 10ms
O

INTEGER (0..3)
If this TFC is a reference TFC, this IE indicates the reference number.
>Computed Gain Factors 10ms




>>Reference TFC nr 10ms
M

INTEGER (0..3)
Indicates the reference TFC to be used to calculate the gain factors for this TFC.

9.2.2.200	Extended E-DPCCH Power Offset
The E-DPCCH Power Offset is used to calculate the E-DPCCH gain factor Eec as defined in TS 25.214 [10], whereas  ec is related to the power difference between DPCCH and E-DPCCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DPCCH Power Offset


INTEGER (9..15)
According to mapping in ref. TS 25.213 [9] subclause 4.2.1.3.

9.2.2.201	Radio Links without DPCH/F-DPCH Indication
The Radio Links without DPCH/F-DPCH Indication IE indicates whether to start operation with Radio Links without DPCH/F-DPCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Radio Links without DPCH/F-DPCH Information

1..<maxNrOfRLs>


>RL ID
M

9.2.1.53

>Radio Links without DPCH/F-DPCH Operation indicator
M

ENUMERATED (true)
This IE indicates that the E-DCH radio link is setup without transmission of DPCH/F-DPCH.

Range bound
Explanation
maxNrOfRLs
Maximum number of Radio Links for one UE.

9.2.2.202	UL DPCCH2 Reconfiguration
The UL DPCCH2 Reconfiguration IE is used for the reconfiguration of the UL DPCCH2 operation in a UE context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Setup, Configuration Change or Removal of UL DPCCH2

1


>Setup



Used when UL DPCCH2 is not configured in the current UE Context
>>UL DPCCH2 Information
M

9.2.2.203

>Configuration Change



Used when the existing UL DPCCH2 configuration in the current UE context is modified 
>>UL DPCCH2 Information To Modify
M

9.2.2.204

>Removal



Used when the existing UL DPCCH2 configuration in the current UE context is removed.
>>UL DPCCH2 information Removal
M

9.2.2.205


9.2.2.203	UL DPCCH2 Information
The UL DPCCH2 Information IE defines the parameters used for UL DPCCH2 operation according to ref TS 25.214 [10].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
F-DPCH info

1

Used when UL DPCCH2 is configured.
>F-DPCH slot format
M

9.2.2.93

>FDD DL Channelisation Code Number
M

9.2.2.14

>Extended E-DPCCH Power Offset
O

9.2.2.200


9.2.2.204	UL DPCCH2 Information To Modify
The UL DPCCH2 Information To Modify IE is used for modification of UL DPCCH2 information in a UE Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
F-DPCH info To Modify

0..1

Used when UL DPCCH2 is configured.
>F-DPCH slot format
O

9.2.2.93

>FDD DL Channelisation Code Number
O

9.2.2.14

>Extended E-DPCCH Power Offset
O

9.2.2.200


9.2.2.205	UL DPCCH2 Information Removal
The UL DPCCH2 Information Removal IE is used for removal of UL DPCCH2 information in a UE Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL DPCCH2 Information Removal


ENUMERATED (Remove, ...)


9.2.2.206	CQI Feedback Cycle2 k
The CQI Feedback Cycle2 k IE provides the duration of the CQI feedback cycle.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CQI Feedback Cycle2 k


ENUMERATED 
(v0, v8, v10, v16, v20, v32, v40, v64, v80, v160,…)
Unit ms 
The allowed values for this IE depend on the configured CQI Repetition Factor and the HS-DSCH configuration as defined in TS 25.331 [16].

CQI Feedback Cycle2 k value shall be an integer multiple of the CQI Feedback Cycle k

9.2.2.207	UE Measurement Forwarding 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Measurement ID
M

9.2.1.42

UE Measurement Value
M

9.2.2.208


9.2.2.208	UE Measurement Value
The UE Measurement Value contains the value to be forwarded.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Dedicated Measurement Value
M



>UPH Filtering Value




>>UPH Filtering Value
M

INTEGER (0..32)
According to mapping in TS 25.321 [32].

9.2.2.209	TTI Update Indication
The TTI Update Indication indicates that the TTI switching has been triggered and confirmed by the UE.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE TTI Update Indication
M



>TTI Update CFN




>>CFN
M

CFN 9.2.1.7

>TTI Update Ind


NULL


9.2.2.210	Activation Delay
The Activation Delay IE is the same value as the RNC sends to the UE for the TTI swiching by the HS-SCCH Order.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Activation Delay


Enumerated (v0, v1, v2, v3, v4, v5, ...)
In radio frames. Refer to TS 25.331 [18]

9.2.2.211	Fast TTI switching Mode Supported
The Fast TTI switching Mode Supported indicates which Fast TTI switching mode is supported by the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Fast TTI Switching Support Mode


ENUMERATED 
(Mode 1, Mode 2)


9.2.2.212	Fast TTI switching Mode Requested Synchronized
The Fast TTI switching Mode Requested Synchronized indicates which Mode is requested.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Fast TTI switching Mode Synchronized
M



>Mode 1


NULL

>Mode 2




>>CFN
M

CFN 9.2.1.7


9.2.2.213	Fast TTI switching Mode Requested UnSynchronized
The Fast TTI switching Mode Requested UnSynchronized indicates which Mode is requested.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Fast TTI switching Mode Unsynchronized
M



>Mode 1




>>Activation Delay
M

9.2.2.210

>Mode 2




>>CFN
M

CFN 9.2.1.7


9.2.2.214	Downlink TPC enhancements Information
The Downlink TPC enhancements Information IE defines the parameters used for Downlink TPC enhancements operation according to ref TS 25.214 [10].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Decimation factor for primary frequency
O

ENUMERATED (3 slots, 5 slots)

Decimation factor for secondary frequency
O

ENUMERATED (3 slots, 5 slots)


9.2.2.215	Downlink TPC enhancements Reconf
The Downlink TPC enhancements Reconf IE is used for the reconfiguration of the Dowlink TPC enhancements operation in a UE context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Setup, Configuration Change or Removal of Downlink TPC enhancements

1


>Setup



Used when Downlink TPC enhancements is not configured in the current UE Context.
>>Downlink TPC enhancements Information
M

9.2.2.214

>Configuration Change



Used when the existing Downlink TPC enhancements configuration in the current UE context is modified.
>>Downlink TPC enhancements Information To Modify
M

9.2.2.214

>Removal



Used when the existing Downlink TPC enhancements configuration in the current UE context is removed.
>>Downlink TPC enhancements information Removal
M

9.2.2.216


9.2.2.216	Downlink TPC enhancements Information Removal
The Downlink TPC enhancements Information Removal IE is used for removal of Downlink TPC enhancements information in a UE Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Downlink TPC enhancements Information Removal


ENUMERATED (Remove, ...)


9.2.2.217	TPC slot position
The TPC slot position IE is used to configure TPC slot position for power control Algorithm 3.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Slot position
O

INTEGER (0..4)


9.2.2.218	E-RNTI Set
The E-RNTI Set IE provides a set of E-RNTIs which can be allocated by CRNC.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Starting E-RNTI
M

9.2.1.75
First E-RNTI value in the set.
Ending E-RNTI
M

9.2.1.75
Last E-RNTI value in the set.

9.2.3	TDD specific Parameters
9.2.3.1	Block STTD Indicator
Void.
9.2.3.2	Burst Type
Void.
9.2.3.3	CCTrCH ID
The CCTrCH ID for dedicated and shared channels identifies unambiguously an uplink or downlink CCTrCH inside a Radio Link. For S-CCPCH, it identifies unambiguously a downlink CCTrCH within a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CCTrCH ID


INTEGER (0..15)


9.2.3.4	Cell Parameter ID
The Cell Parameter ID identifies unambiguously the [3.84 Mcps TDD and 7.68Mcps TDD - Code Groups, Scrambling Codes, Midambles and Toffset] [1.28 Mcps TDD - SYNC-DL and SYNC-UL sequences, the scrambling codes and the midamble codes] (see ref. TS 25.223 [20]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Cell Parameter ID


INTEGER (0..127,…)


9.2.3.4A	Constant Value
The Constant Value is the power margin used by a UE to set the proper uplink power for a DCH, USCH, or a RACH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Constant Value


INTEGER 
(-10..10,…)
Unit: dB
Range: -10 .. +10 dB
Step: 1 dB.

9.2.3.4B	DL Timeslot ISCP
The DL Timeslot ISCP is the measured interference in a downlink timeslot at the UE, see ref. TS 25.225 [5].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL Timeslot ISCP


INTEGER (0..91)
According to mapping in ref. TS 25.225 [5].

9.2.3.4C	DCH TDD Information
The DCH TDD Information IE provides information for DCHs to be established.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
DCH TDD Information

1..<maxNrOfDCHs>


–

>Payload CRC Presence Indicator
M

9.2.1.49

–

>UL FP Mode
M

9.2.1.66

–

>ToAWS
M

9.2.1.61

–

>ToAWE
M

9.2.1.60

–

>DCH Specific Info

1..<maxNrOfDCHs>


–

>>DCH ID
M

9.2.1.20

–

>>CCTrCH ID
M

9.2.3.3
UL CCTrCH in which the DCH is mapped 
–

>>CCTrCH ID
M

9.2.3.3
DL CCTrCH in which the DCH is mapped
–

>>Transport Format Set 
M

9.2.1.59
For UL
–

>>Transport Format Set 
M

9.2.1.59
For DL
–

>>Allocation/Retention Priority
M

9.2.1.1A

–

>>Frame Handling Priority
M

9.2.1.30

–

>>QE-Selector
C-CoorDCH

9.2.1.50A

–

>>Unidirectional DCH Indicator
O

9.2.1.68

YES
reject
>TNL QoS
O

9.2.1.58A

YES
ignore

Condition
Explanation
CoorDCH
The IE shall be present if this DCH is part of a set of coordinated DCHs (number of instances of the DCH Specific Info IE is greater than 1).

Range Bound
Explanation
maxNrOfDCHs
Maximum number of DCHs for one UE

9.2.3.4D	DCHs TDD To Modify
The DCHs TDD To Modify IE provides information for DCHs to be modified. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
DCHs TDD To Modify

1..<maxNrOfDCHs>


–

>UL FP Mode
O

9.2.1.66

–

>ToAWS
O

9.2.1.61

–

>ToAWE
O

9.2.1.60

–

>Transport Bearer Request Indicator
M

9.2.1.62A

–

>DCH Specific Info

1..<maxNrOfDCHs>


–

>>DCH ID
M

9.2.1.20

–

>>CCTrCH ID
O

9.2.3.3
UL CCTrCH in which the DCH is mapped.
–

>>CCTrCH ID
O

9.2.3.3
DL CCTrCH in which the DCH is mapped
–

>>Transport Format Set
O

9.2.1.59
For the UL.
–

>>Transport Format Set
O

9.2.1.59
For the DL.
–

>>Allocation/Retention Priority
O

9.2.1.1A

–

>>Frame Handling Priority
O

9.2.1.30

–

>TNL QoS
O

9.2.1.58A

YES
ignore

Range Bound
Explanation
maxNrOfDCHs
Maximum number of DCHs for one UE

9.2.3.4E	DL Timeslot Information
The DL Timeslot Information IE provides information for DL Time slot to be established.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL Timeslot Information

1..<maxNrOfDLTSs>


>Time Slot
M

9.2.3.23

>Midamble Shift And Burst Type
M

9.2.3.7

>TFCI Presence
M

9.2.1.57

>DL Code Information
M

TDD DL Code Information 9.2.3.19B


Range Bound
Explanation
maxNrOfDLTSs
Maximum number of Downlink time slots per Radio Link

9.2.3.4F	DL Time Slot ISCP Info
The DL Time Slot ISCP Info IE provides information for DL Interference level for each time slot within the Radio Link.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL Time Slot ISCP Info

1..<maxNrOfDLTSs>


>Time Slot
M

9.2.3.23

>DL Timeslot ISCP
M

9.2.3.4B


Range Bound
Explanation
maxNrOfDLTSs
Maximum number of Downlink time slots per Radio Link for 3.84Mcps TDD.

9.2.3.4G	Cell Sync Burst Code
The Cell Sync Burst Code IE indicates which Code is used for a given Cell Sync Burst.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Cell Sync Burst Code 


INTEGER (0..7,…)


9.2.3.4H	Cell Sync Burst Code Shift
The Cell Sync Burst Code Shift IE indicates the number of code shifts used for a given Cell Sync Burst.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Cell Sync Burst Code Shift


INTEGER (0..7)


9.2.3.4I	CSB Measurement ID
The CSB Measurement ID IE uniquely identifies any cell synchronisation burst measurement per Node B Control Port.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CSB Measurement ID


INTEGER (0..65535)


9.2.3.4J	Cell Sync Burst Repetition Period
The Cell Sync Burst Repetition Period IE represents the number of consecutive Radio Frames after which the cell synchronisation burst transmission/measurement is repeated. This means that if the Time Slot K is assigned to the cell synchronisation burst transmission/measurements in the Radio Frame J, the cell synchronisation burst transmission/measurement is also in all the Radio Frames J+n*Repetition Period.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Cell Sync Burst Repetition Period


INTEGER (0..4095)


9.2.3.4K	Cell Sync Burst SIR
Indicates the Signal to Interference Ratio of the cell synchronisation burst measurement according definition in TS 25.225 [5].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Cell Sync Burst SIR


INTEGER (0..31)
According to mapping in TS 25.123 [23]

9.2.3.4L	Cell Sync Burst Timing
The Cell Sync Burst Timing IE defines the time of start (defined by the first detected path in time) of the cell synchronisation burst of a neighbouring cell see TS 25.225 [5] for 3.84Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Phase



According to mapping in TS 25.123 [23]
>Initial Phase




>>Cell Synch Burst Timing Value
M

INTEGER (0..1048575,…)

>Steady State Phase




>>Cell Synch Burst Timing Value
M

INTEGER (0..255,…)


9.2.3.4La	Cell Sync Burst Timing LCR
The Cell Sync Burst Timing LCR IE defines the time of start (defined by the first detected path in time) of the cell synchronisation burst of a neighbouring cell see TS 25.225 [5] for 1.28Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Phase



According to mapping in TS 25.123 [23]
>Initial Phase




>>Cell Synch Burst Timing Value
M

INTEGER (0.. 524287,…)

>Steady State Phase




>>Cell Synch Burst Timing Value
M

INTEGER (0..127,…)


9.2.3.4M	Cell Sync Burst Timing Threshold
The Cell Sync Burst Timing Threshold IE defines the threshold that shall trigger a CELL SYNCHRONISATION REPORT message.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Cell Sync Burst Timing Threshold


INTEGER (0..254)
Unit: chip
Range: 0 .. 31.75 chips
Step: 0.125 chip


9.2.3.4N	CSB Transmission ID
The CSB Transmission ID IE uniquely identifies any cell synchronisation burst transmission per Node B Control Port.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CSB Transmission ID


INTEGER (0..65535)


9.2.3.4O	DL Timeslot Information LCR
The DL Timeslot Information LCR IE provides information for DL Time slot to be established.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
DL Timeslot Information LCR

1..<maxNrOfDLTSLCRs>


–

>Time Slot LCR
M

9.2.3.24A

–

>Midamble Shift LCR
M

9.2.3.7A

–

>TFCI Presence
M

9.2.1.57

–

>DL Code Information 
M

TDD DL Code Information LCR 9.2.3.19C

–

>Initial DL Transmission Power
O

DL Power
9.2.1.21
Initial power on DPCH
YES
ignore
>Maximum DL Power
O

DL Power
9.2.1.21
Maximum allowed power on DPCH
YES
ignore
>Minimum DL Power
O

DL Power
9.2.1.21
Minimum allowed power on DPCH
YES
ignore

Range Bound
Explanation
maxNrOfDLTSLCRs
Maximum number of Downlink time slots per Radio Link for 1.28Mcps TDD.

9.2.3.4P	DL Time Slot ISCP Info LCR
The DL Time Slot ISCP Info LCR IE provides information for DL Interference level for each time slot within the Radio Link.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL Time Slot ISCP Info LCR

1..<maxNrOfDLTSLCRs>


>Time Slot LCR
M

9.2.3.24A

>DL Timeslot ISCP
M

9.2.3.4B


Range Bound
Explanation
maxNrOfDLTSLCRs
Maximum number of Downlink time slots per Radio Link for 1.28Mcps TDD.

9.2.3.4Q	UpPCH Position LCR
The UpPCH Position LCR IE indicates the start point of the UpPCH channel , where the step size is 16chips, the maximum allowed value that can be utilised is 127*16=2032chips, The reference point (UpPCH Position LCR =0) is the startpoint of the  timeslot of UpPTS.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UpPCH Position LCR


INTEGER (0..127)


9.2.3.5	DPCH ID
The DPCH ID identifies unambiguously a DPCH inside a Radio Link.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DPCH ID


INTEGER (0..239)


9.2.3.5a	DSCH ID
The DSCH ID uniquely identifies a DSCH within a Node B Communication Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DSCH ID


INTEGER (0..255)


9.2.3.5b	DSCH Information Response
The DSCH Information Response IE provides information for DSCHs that have been established or modified.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DSCH Information Response

1..<maxNrOfDSCHs>


>DSCH ID
M

9.2.3.5a

>Binding ID
O

9.2.1.4

>Transport Layer Address
O

9.2.1.63


Range Bound
Explanation
maxNrOfDSCHs
Maximum number of DSCHs for one UE

9.2.3.5A	DSCH TDD Information
The DSCH TDD Information IE provides information for DSCHs to be established.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
DSCH TDD Information

1..<maxNrOfDSCHs>


–

>DSCH ID
M

9.2.3.5a

–

>CCTrCH ID
M

9.2.3.3
DL CCTrCH in which the DSCH is mapped
–

>Transport Format Set
M

9.2.1.59
For DSCH
–

>Allocation/Retention Priority
M

9.2.1.1A

–

>Frame Handling Priority
M

9.2.1.30

–

>ToAWS
M

9.2.1.61

–

>ToAWE
M

9.2.1.60

–

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP.
YES
ignore

Range Bound
Explanation
MaxNrOfDSCHs
Maximum number of DSCH for one UE

9.2.3.5B	DwPCH Power
DwPCH Power is the power that shall be used for transmitting the DwPCH in a cell. The reference point is the antenna connector. If Transmit Diversity is applied to the DwPCH, the DwPCH power is the linear sum of the power that is used for transmitting the DwPCH on all branches.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DwPCH Power


INTEGER 
(-150..+400,…)
Unit: dBm
Range: -15 ..+40 dBm
Step: 0.1 dB

9.2.3.5C	Frame Adjustment Value
The Frame Adjustment Value IE represents the frame number correction within the initial synchronisation phase.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Frame Adjustment Value


INTEGER (0..4095)
SFNnew=(SFNold+Frame Adjustment Value) mod 4096

9.2.3.5D	IPDL TDD Parameters
The IPDL TDD Parameters IE provides information about IPDL to be applied for 3.84Mcps TDD or 7.68Mcps TDD when activated.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
IP SpacingTDD
M

ENUMERATED 
(30, 40, 50, 70, 100, ...)
See TS 25.224 [21]
IP Start
M

INTEGER (0..4095)
See TS 25.224 [21]
IP Slot
M

INTEGER (0..14)
See TS 25.224 [21]
IP PCCPCH
M

ENUMERATED (
Switch off 1 frame, Switch off 2 frames)
See TS 25.224 [21]
Burst Mode parameters
O

9.2.1.5A


9.2.3.5E	Max FPACH Power
Max FPACH Power is the maximum power that shall be used for transmitting the FPACH in a cell. The reference point is the antenna connector. If Transmit Diversity is applied to the FPACH, the Max FPACH Power is maximum of the linear sum of the power that is allowed for transmitting the FPACH on all branches.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
FPACH Power


INTEGER 
(-150..+400,…)
Unit: dBm
Range: -15 ..+40 dBm
Step: 0.1 dB

9.2.3.5F	HS-DSCH TDD Information
The HS-DSCH TDD Information IE is used for initial addition of HS-DSCH information to a Node B Communication Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-DSCH MAC-d Flows Information
M

9.2.1.31IA

–

UE Capabilities Information

1


–

>HS-DSCH Physical Layer Category
M

9.2.1.31Ia

–

>1.28 Mcps TDD Uplink Physical Channel Capability
O

9.2.3.5Gc
Applicable to 1.28Mcps TDD only
YES
ignore
>Number of Supported Carriers
O

ENUMERATED (
One-one carrier, One-three carrier, Three-three carrier, One-six carrier,
Three-six carrier,
Six-six carrier, ..., One-Two carrier Discontiguous, Two-Two carrier Discontiguous, One-Two carrier Contiguous, Two-Two carrier Contiguous)
Applicable to 1.28Mcps TDD only
This IE indicates the number of carrier that UE can support at the same time, where ”One-three carrier” means the number of supported carrier is one for the uplink,and three for the downlink.
One-Two carrier Discontiguous and Two-Two carrier Discontiguous mean that the UE is capable of supporting two non-adjacent carriers.
One-Two carrier Contiguous and Two-Two carrier Contiguous mean that the UE is only capable of supporting two adjacent carriers.
YES
reject
>Multi-carrier HS-DSCH Physical Layer Category
O

HS-DSCH Physical Layer Category 9.2.1.31Ia
Applicable to 1.28Mcps TDD only
YES
ignore
>MIMO SF Mode Supported For HS-PDSCH dual stream
O

Enumerated (SF1, SF1/SF16)
Applicable to 1.28Mcps TDD only
YES
ignore
>UE TS0 Capability LCR
O

9.2.3.110
Applicable to 1.28Mcps TDD only. 
YES
ignore
>UE RF Band Capability LCR
C-NofSupportedCarriers

9.2.3.125
Applicable to 1.28Mcps TDD only.
YES
ignore
MAC-hs Reordering Buffer Size for RLC-UM
M

9.2.1.38Ab

–

TDD ACK NACK Power Offset
M

9.2.3.18F

–

HS-SICH SIR Target
O

UL SIR
9.2.1.67A
Applicable to 1.28Mcps TDD only
YES
ignore
HS-SICH TPC step size
O

TDD TPC UL Step Size 9.2.3.21a
Applicable to 1.28Mcps TDD only
YES
ignore
HS-DSCH MAC-d PDU Size Format 
O

9.2.1.31ID
If not present, "Indexed MAC-d PDU Size" shall be used.
YES
reject
TSN-Length
O

9.2.3.5I
Applicable for 1.28Mcps TDD when using multiple frequencies
YES
reject
MIMO Activation Indicator
O

9.2.1.119

YES
reject

Condition
Explanation
NofSupportedCarriers
This IE shall be present if the Number of Supported Carriers IE is equal to "One-Two carrier Discontiguous" or "Two-Two carrier Discontiguous" and the concerned cell and the UE support more than one RF band.

9.2.3.5G	HS-DSCH TDD Information Response
The HS-DSCH TDD Information Response provides information for HS-DSCH MAC-d flows that have been established or modified. It also provides additional HS-DSCH information determined within the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-DSCH MAC-d Flow Specific Information Response

0..<maxNrOfMACdFlows>


–

>HS-DSCH MAC-d Flow ID
M

9.2.1.31I

–

>Binding ID
O

9.2.1.4

–

>Transport Layer Address
O

9.2.1.63

–

>HS-DSCH Initial Capacity Allocation
O

9.2.1.31Ha

–

HS-SCCH Specific Information Response

0..<maxNrOfHSSCCHCodes>

Not applicable to 1.28 Mcps TDD or 7.68Mcps TDD
GLOBAL
reject
>Time Slot
M

9.2.3.23

–

>Midamble Shift And Burst Type
M

9.2.3.7

–

>TDD Channelisation Code
M

9.2.3.19

–

>HS-SICH Information

1


–

>>HS SICH ID
M

9.2.3.5Gb

–

>>Time Slot
M

9.2.3.23

–

>>Midamble Shift And Burst Type
M

9.2.3.7

–

>>TDD Channelisation Code
M

9.2.3.19

–

HS-SCCH Specific Information Response LCR per UARFCN

0..<maxHSDPAFrequency>

Not applicable to 3.84 Mcps TDD or 7.68Mcps TDD
See note1 below
–

>HS-SCCH Specific Information Response LCR

1..<maxNrOfHSSCCHCodes>

Not applicable to 3.84 Mcps TDD or 7.68Mcps TDD
GLOBAL
reject
>>Time Slot LCR
M

9.2.3.24A

–

>>Midamble Shift LCR
M

9.2.3.7A

–

>>First TDD Channelisation Code
M

TDD Channelisation Code 9.2.3.19

–

>>Second TDD Channelisation Code
M

TDD Channelisation Code 9.2.3.19

–

>>HS-SICH Information LCR

1


–

>>>HS SICH ID
M

9.2.3.5Gb
If the Extended HS-SICH ID IE is included in the HS-SICH Information LCR IE, the HS-SICH ID IE shall be ignored.
–

>>>Time Slot LCR
M

9.2.3.24A

–

>>>Midamble Shift LCR
M

9.2.3.7A

–

>>>TDD Channelisation Code
M

9.2.3.19

–

 >>>Extended HS-SICH ID
O

9.2.3.5K
The Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31.
YES
ignore
>>UsedFrequency
O

UARFCN
9.2.1.65
Applicable for 1.28Mcps TDD when using multiple frequencies. this IE indicates the frequency which is actually used by the HS-SCCH.
YES
reject
>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Applicable for 1.28Mcps TDD when using multiple frequencies.
See note2 below
YES
ignore
HARQ Memory Partitioning per UARFCN

0..<maxHSDPAFrequency>

See note 1 below
–

>HARQ Memory Partitioning 
O

9.2.1.102

–

>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Applicable for 1.28Mcps TDD when using multiple frequencies.
See note2 below
YES
ignore
HS-SCCH Specific Information Response 7.68Mcps

0..<maxNrOfHSSCCHCodes>

Not applicable to 3.84 Mcps TDD or 1.28Mcps TDD
GLOBAL
reject
>Time Slot 
M

9.2.3.23

–

>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>Channelisation Code 7.68Mcps
M

TDD Channelisation Code 7.68Mcps 9.2.3.34

–

>HS-SICH Information  7.68Mcps

1


–

>>HS SICH ID
M

9.2.3.5Gb



>>Time Slot 
M

9.2.3.23

–

>>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

–

>>Channelisation Code 7.68Mcps
M

TDD Channelisation Code 7.68Mcps 9.2.3.34

–

Multi-Carrier number
O

INTEGER(1.. maxHSDPAFrequency)
Applicable for 1.28Mcps TDD when using multiple frequencies.
YES
ignore
MIMO SF Mode for HS-PDSCH dual stream
O

Enumerated (SF1, SF1/SF16)
Applicable for 1.28Mcps TDD when MIMO is configured
YES
reject
MIMO Reference Signal Information
O
0..<maxNrOfHSSCCHCodes>

Applicable for 1.28Mcps TDD when MIMO is configured
YES
reject
>HS-SICH Reference Signal Information
M

9.2.3.103

YES

Note 1:	This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxHSDPAFrequency are represented by separate ASN.1 structures with different criticalities. 
Note 2:	The UARFCN IE in the HARQ Memory Partitioning per UARFCN IE has the same content as that in the HS-SCCH Specific Information Response LCR per UARFCN IE. They will be represented by one ASN.1 structure with same criticalities

Range Bound
Explanation
maxNrOfMACdFlows
Maximum number of HS-DSCH MAC-d flows.
maxNrOfHSSCCHCodes
Maximum number of HS-SCCH codes
maxHSDPAFrequency
Maximum number of Frequencies that UE can support

9.2.3.5GA	HS-DSCH TDD Update Information
The HS-DSCH TDD Update Information IE provides information for HS-DSCH to be updated. At least one IE shall be present.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-SCCH Code Change Indicator
O

9.2.1.31K

TDD ACK NACK Power Offset
O

9.2.3.18F


9.2.3.5Ga	HS-SCCH ID
The HS-SCCH ID identifies unambiguously a HS-SCCH and its paired HS-SICH within the set of HS-SCCHs.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS SCCH ID


INTEGER (0..31)


9.2.3.5Gb	HS-SICH ID
The HS-SICH ID identifies unambiguously a HS-SICH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS SICH ID


INTEGER (0..31)


9.2.3.5Gc	1.28 Mcps TDD Uplink Physical Channel Capability
The 1.28 Mcps TDD Uplink Physical Channel Capability IE defines the UE uplink radio access capacity, see ref TS 25.306 [33]. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Maximum Number of timeslots per subframe
M

INTEGER
(1..6)

Maximum number of physical channels per timeslot
M

ENUMERATED
(one, two, ..., three, four)


9.2.3.5H	IPDL TDD Parameters LCR
The IPDL TDD Parameters LCR IE provides information about IPDL to be applied for 1.28Mcps TDD when activated.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
IP SpacingTDD
M

ENUMERATED 
(30, 40, 50, 70, 100, ...)
See TS 25.224 [21]
IP Start
M

INTEGER (0..4095)
See TS 25.224 [21]
IP_Sub 
M

ENUMERATED (
First,
Second,
Both)
See TS 25.224 [21]
Burst Mode Parameters
O

9.2.1.5A


9.2.3.5I	TSN-Length
Indicates the TSN bits applied to the MAC-hs PDU frame.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TSN-Length


ENUMERATED (tsn-6bits, tsn-9bits)


9.2.3.5J	Extended HS-SCCH ID
The Extended HS-SCCH ID LCR identifies unambiguously a HS-SCCH and its paired HS-SICH within the set of HS-SCCHs in a cell for 1.28Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Extended HS-SCCH ID


INTEGER(32..255)
The Extended HS-SCCH ID IE shall be used if the HS-SCCH identity has a value larger than 31.

9.2.3.5K	Extended HS-SICH ID
The Extended HS-SICH ID LCR identifies unambiguously a HS-SICH in a cell for 1.28Mcps TDD
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Extended HS-SICH ID


INTEGER(32..255)
The Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31.

9.2.3.6	Max PRACH Midamble Shift
Indicates the maximum number of Midamble shifts to be used in a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Max PRACH Midamble Shift


ENUMERATED 
(4, 8,…,16)


9.2.3.7	Midamble Shift And Burst Type
This information element indicates burst type and midamble allocation for burst types 1, 2 and 3.
The 256 chip midamble supports 3 different time shifts, the 512 chips midamble may support 8 or even 16 time shifts.
Three different midamble allocation schemes exist:
Default midamble: the midamble is allocated by layer 1 depending on the associated channelisation code (DL and UL)
Common midamble: the midamble is allocated by layer 1 depending on the number of channelisation codes (possible in DL only)
UE specific midamble: a UE specific midamble is explicitly assigned (DL and UL)
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Burst Type




>Type1




>>Midamble Configuration Burst Type 1 And 3
M

ENUMERATED 
(4, 8, 16)
As defined in TS 25.221 [19]
>>CHOICE Midamble Allocation Mode
M



>>>Default Midamble


NULL

>>>Common Midamble


NULL

>>>UE Specific Midamble




>>Midamble Shift Long
M

INTEGER (0..15)

>Type2




>>Midamble Configuration Burst Type 2
M

ENUMERATED 
(3, 6)
As defined in TS 25.221 [19]
>>CHOICE Midamble Allocation Mode
M



>>>Default Midamble


NULL

>>>Common Midamble


NULL

>>>UE Specific Midamble




>>Midamble Shift Short
M

INTEGER (0..5)

>Type3



UL only
>>Midamble Configuration Burst Type 1 And 3
M

ENUMERATED 
(4, 8, 16)
As defined in TS 25.221 [19]
>>CHOICE Midamble Allocation Mode
M



>>>Default Midamble


NULL

>>>UE Specific Midamble




>>Midamble Shift Long
M

INTEGER (0..15)


9.2.3.7A	Midamble Shift LCR
This information element indicates midamble allocation in 1.28Mcps TDD.
Three different midamble allocation schemes exist:
Default midamble: the midamble is allocated by layer 1 depending on the associated channelisation code (DL and UL)
Common midamble: the midamble is allocated by layer 1 depending on the number of channelisation codes (possible in DL only)
UE specific midamble: a UE specific midamble is explicitly assigned (DL and UL)
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Midamble Allocation Mode
M

ENUMERATED (
Default midamble, 
Common midamble, 
UE specific midamble,
…)

Midamble Shift Long
C-UE

INTEGER (0..15)

Midamble Configuration LCR
M

ENUMERATED (2, 4, 6, 8, 10, 12, 14, 16, ...)
As defined in TS 25.221 [19]

Condition
Explanation
UE
The IE shall be present if the Midamble Allocation Mode IE is set to "UE-specific midamble".

9.2.3.7Aa	Notification Indicator Length
The Notification Indicator Length indicates the number of symbols for Notification Indication transmitted in one timeslot (see ref TS 25.221 [19]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Notification Indicator Length


ENUMERATED 
(2, 4, 8,…)


9.2.3.7B	Number Of Cycles Per SFN Period
The Number Of Cycles Per SFN Period IE indicates the number of repetitions per SFN period where the same schedule shall apply.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Number Of Cycles Per SFN Period


ENUMERATED 
(1, 2, 4, 8, ..., 
16, 32, 64)


9.2.3.7C	Number Of Repetitions Per Cycle Period
The Number Of Repetitions Per Cycle Period IE indicates the number of Sync frames per Cycle Length where the [3.84Mcps TDD - cell synchronisation bursts] [1.28Mcps TDD - Sync_DL Codes] shall be transmitted or the cell synchronisation bursts from the neighbouring cells shall be measured.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Number Of Repetitions Per Cycle Period


INTEGER (2..10)


9.2.3.7D	Number Of Subcycles Per Cycle Period
The Number Of Subcycles Per Cycle Period IE indicates the number of subcycles within a Synchronisation Cycle. Within each subcycle, the same sequence of SYNC_DL Code transmissions and receptions is performed.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Number Of Subcycles Per Cycle Period


INTEGER (1..16,...)


9.2.3.8	Paging Indicator Length
The Paging Indicator Length indicates the number of symbols for Page Indication transmitted in one timeslot (see ref TS 25.221 [19]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Paging Indicator Length


ENUMERATED 
(2, 4, 8,…)


9.2.3.9	PCCPCH Power
The Primary CCPCH power is the power that shall be used for transmitting the P CCPCH in a cell. The P CCPCH power is the reference power in a TDD-cell. The reference point is the antenna connector. If Transmit Diversity is applied to the Primary CCPCH, the Primary CCPCH power is the linear sum of the power that is used for transmitting the Primary CCPCH on all branches.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
PCCPCH Power


INTEGER 
(-150..+400,…)
Unit: dBm
Range: -15 ..+40 dBm
Step: 0.1 dB

9.2.3.10	PDSCH ID
The PDSCH ID identifies unambiguously a PDSCH inside a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
PDSCH ID


INTEGER (0..255)


9.2.3.11	PDSCH Set ID
The PDSCH Set Id identifies unambiguously a PDSCH Set inside a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
PDSCH Set ID


INTEGER (0..255)
See ref. TS 25.430 [6]

9.2.3.11A	Primary CCPCH RSCP
Received Signal Code Power is the received power on PCCPCH of the target cell after despreading. The reference point for the RSCP is the antenna connector at the UE, see ref. TS 25.225 [5].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Primary CCPCH RSCP


INTEGER (0..91)
According to mapping of the non-negative values in ref. TS 25.123 [23].

9.2.3.11B	Primary CCPCH RSCP Delta
Primary CCPCH RSCP Delta is the offset used to report the negative reporting range of P-CCPCH RSCP as per TS 25.123 [23].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Primary CCPCH RSCP Delta


INTEGER(-5..-1,…)
If present, the actual value of Primary CCPCH RSCP = Primary CCPCH RSCP Delta

9.2.3.12	PUSCH ID
The PUSCH ID identifies unambiguously a PUSCH inside a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
PUSCH ID


INTEGER (0..255)


9.2.3.13	PUSCH Set ID
The PUSCH Set ID identifies unambiguously a PUSCH Set inside a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
PUSCH Set ID


INTEGER (0..255)
See ref. TS 25.430 [6]

9.2.3.14	PRACH Midamble
The PRACH Midamble indicates if only the Basic Midamble Sequence or also the time-inverted Midamble Sequence is used.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
PRACH Midamble 


ENUMERATED (
Inverted, 
Direct,
…)


9.2.3.14A	Reference Clock Availability
The Reference Clock Availability IE is used to indicate the presence and operating of a Reference Clock connected to a TDD cell for cell synchronisation purpose.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Reference Clock Availability


ENUMERATED (
Available, 
Not Available)


9.2.3.14B	Reference SFN Offset
The Reference SFN Offset IE indicates the number of frames the reference SFN shall be shifted compared to the SFN derived from the synchronisation port.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Reference SFN Offset


INTEGER (0..255)


9.2.3.15	Repetition Length
The Repetition Length represents the number of consecutive Radio Frames inside a Repetition Period in which the same Time Slot is assigned to the same Physical Channel see ref. TS 25.331 [18].
[1.28Mcps TDD - When applied to configure the E-DCH Non-scheduled Grant Information, the Repetition Length represents the number of consecutive Subframes, i.e. 5ms inside a Repetition Period in which the same Time Slot is assigned to the same Physical Channel see ref. TS 25.331 [18].]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Repetition Length


INTEGER (1..63)


9.2.3.16	Repetition Period
The Repetition Period represents the number of consecutive Radio Frames after which the same assignment scheme of Time Slots to a Physical Channel is repeated. This means that if the Time Slot K is assigned to a physical channel in the Radio Frame J, it is assigned to the same physical channel also in all the Radio Frames J+n*Repetition Period (where n is an integer) see ref. TS 25.331 [18].
[1.28Mcps TDD- When applied to configure the E-DCH Non-scheduled Grant Information, the Repetition Period represents the number of consecutive Subframes, i.e. 5ms after which the same assignment scheme of Time Slots to a Physical Channel is repeated see ref. TS 25.331 [18].]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Repetition Period


ENUMERATED 
(1, 2, 4, 8, 16, 32, 64,…)


9.2.3.17	SCH Time Slot
The SCH Time Slot IE represents the first time slot (k) of a pair of time slots inside a Radio Frame that shall be assigned to the Physical Channel SCH. The SCH Time Slot IE is only applicable if the value of Sync Case IE is Case 2 since in this case the SCH is allocated in TS#k and TS#k+8.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SCH Time Slot


INTEGER (0..6)


9.2.3.18	Sync Case
The SCH and PCCPCH are mapped on one or two downlink slots per frame. There are two cases of SCH and PCCPCH allocation as follows:
Case 1)	SCH and PCCPCH allocated in a single TS#k
Case 2)	SCH allocated in two TS: TS#k and TS#k+8
PCCPCH allocated in TS#k
[1.28Mcps TDD - There is no Sync Case indication needed for 1.28Mcps TDD. If the Sync Case IE must be included in a message from CRNC to Node B used for 1.28Mcps TDD, the CRNC should indicate Sync Case 1 and the Node B shall ignore it.]
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Sync Case


INTEGER (1..2,…)


9.2.3.18A	Special Burst Scheduling
The number of frames between special burst transmissions during DTX.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Special Burst Scheduling


INTEGER (1..256)
Number of frames between special burst transmission during DTX

9.2.3.18B	SYNC_DL Code ID
The SYNC_DL Code ID identifies the SYNC_DL Code which used by DwPCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SYNC_DL Code ID


INTEGER (1..32,...)


9.2.3.18C	Sync Frame Number
The Sync Frame Number IE indicates the number of the Sync frame within a Synchronisation Cycle or Subcycle, respectively, where the cell synchronisation bursts shall be transmitted or the cell synchronisation bursts from the neighbouring cells shall be measured. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Sync Frame Number


INTEGER (1..10)


9.2.3.18D	Synchronisation Report Characteristics
The Synchronisation Report Characteristics IE defines how the reporting on measured [3.84Mcps TDD - cell synchronisation bursts] [1.28Mcps TDD - Sync_DL Codes] shall be performed
Different methods shall apply for the measured [3.84Mcps TDD - cell synchronisation burst] [1.28Mcps TDD - Sync_DL Codes] reports. [3.84Mcps TDD - In the frequency acquisition phase the measurement report shall be sent when the frequency locking is completed.] In the initial phase and for the measurement on late-entrant cells an immediate report after the measured frame is expected.
In the steady-state phase measurement reports may be given after every measured frame, after every SFN period, after every cycle length or only when the requested threshold is exceeded.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Synchronisation Report Characteristics Type
M

ENUMERATED (
Frame related, 
SFN period related, 
Cycle length related, 
Threshold exceeding,
Frequency Acquisition completed,
 ...)

–

Threshold Exceeding
C-ThresholdExceeding


Applies only to the Steady State Phase
–

>Cell Sync Burst Threshold Information

0..<maxNrOfCellSyncBursts>

Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD.
–

>>Sync Frame Number To Receive
M

Sync Frame Number
9.2.3.18C

–

>>Cell Sync Burst Information

1..<maxNrOfReceptsPerSyncFrame>


–

>>>Cell Sync Burst Code
M

9.2.3.4G

–

>>>Cell Sync Burst Code Shift
M

9.2.3.4H

–

>>>Cell Sync Burst Arrival Time
O

Cell Sync Burst Timing
9.2.3.4L

–

>>>Cell Sync Burst Timing Threshold
O

9.2.3.4M

–

>SYNC_DL Code Threshold Information LCR

0..<maxNrOfSyncFramesLCR>

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD.
GLOBAL
ignore
>>Sync Frame Number To Receive
M

Sync Frame Number
9.2.3.18C

–

>>SYNC_DL Code Information LCR

1..<maxNrOfReceptionsperSyncFrameLCR>


–

>>>SYNC_DL Code ID
M

9.2.3.18B

–

>>>SYNC_DL Code ID Arrival Time
O

Cell Sync Burst Timing LCR
9.2.3.4La

–

>>>SYNC_DL Code ID Timing Threshold
O

Cell Sync Burst Timing Threshold
9.2.3.4M

–


Range Bound
Explanation
maxNrOfCellSyncBursts
Maximum number of cell synchronisation burst per cycle for 3.84Mcps TDD
maxNrOfReceptsPerSyncFrame
Maximum number of cell synchronisation burst receptions per Sync Frame for 3.84Mcps TDD
maxNrOfSyncFramesLCR
Maximum number of SYNC Frames per repetition period for 1.28Mcps TDD
maxNrOfReceptionsperSyncFrameLCR
Maximum number of SYNC_DL Code ID receptions per Sync Frame for 1.28Mcps TDD

9.2.3.18E	Synchronisation Report Type
The Synchronisation Report Type IE represents the individual types of synchronisation reports that shall apply within the individual synchronisation phases. (see TS 25.402 [17]). 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Synchronisation Report Type


ENUMERATED (
Initial Phase, 
Steady-State Phase, 
Late-Entrant Cell, 
Frequency Acquisition,
...)


9.2.3.18F	TDD ACK NACK Power Offset
The TDD ACK NACK Power Offset IE indicates Power offset used in the UL in the HS-SICH between transmissions carrying positive and negative acknowledgements as per TS 25.331 [18].
IE/Group Name
Presence 
Range 
IE type and reference 
Semantics description 
TDD ACK NACK Power Offset


INTEGER (-7..8,…)
Unit: dB
Range: -7..+8 dB
Step: 1 dB

9.2.3.19	TDD Channelisation Code
The Channelisation Code Number indicates which Channelisation Code is used for a given Physical Channel. In TDD the Channelisation Code is an Orthogonal Variable Spreading Factor code, that can have a spreading factor of 1, 2, 4, 8 or 16.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TDD Channelisation Code 


ENUMERATED (
(1/1), 
(2/1), (2/2), 
(4/1), .. (4/4), 
(8/1), .. (8/8), 
(16/1), .. (16/16),…)


9.2.3.19a	TDD Channelisation Code LCR
The Channelisation Code Number indicates which Channelisation Code is used for a given Physical Channel. In 1.28Mcps TDD the Channelisation Code is an Orthogonal Variable Spreading Factor code, that can have a spreading factor of 1, 2, 4, 8 or 16 and there is a choice between QPSK and 8PSK modulation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TDD Channelisation Code


9.2.3.19

Modulation


ENUMERATED (QPSK, 8PSK,…)
Modulation options for 1.28Mcps TDD in contrast to 3.84Mcps TDD. 8PSK denotes 16QAM for S-CCPCH

9.2.3.19A	TDD DPCH Offset
The Offset represents the phase information for the allocation of a group of dedicated physical channels. The Offset Type IE = "No Initial Offset" is used when a starting offset is not required and the TDD Physical channel offset for each DPCH in the CCTrCH shall be directly determined from the TDD DPCH Offset. The Offset Type IE = "Initial Offset" is used when a starting offset is required. The TDD DPCH Offset shall map to the CFN and the TDD Physical Channel Offet for each DPCH in this CCTrCH shall calculated by TDD DPCH Offset mod Repetition period, see ref. TS 25.331 [18].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Offset Type




>Initial Offset




>>TDD DPCH Offset Value
M

INTEGER (0..255)

>No Initial Offset




>>TDD DPCH Offset Value
M

INTEGER (0..63)


9.2.3.19B	TDD DL Code Information
The TDD DL Code Information IE provides DL Code information for the RL.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TDD DL Code Information

1..<maxNrOfDPCHs>


>DPCH ID
M

9.2.3.5

>TDD Channelisation Code
M

9.2.3.19


Range Bound
Explanation
maxNrOfDPCHs
Maximum number of DPCHs in one CCTrCH

9.2.3.19C	TDD DL Code Information LCR
The TDD DL Code Information LCR IE provides DL Code information for the RL.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TDD DL Code Information LCR

1..<maxNrOfDPCHLCRs>


>DPCH ID
M

9.2.3.5

>TDD Channelisation Code LCR
M

9.2.3.19a

>TDD DL DPCH Time Slot Format LCR
M

9.2.3.19D


Range Bound
Explanation
maxNrOfDPCHLCRs
Maximum number of DPCH in one CCTrCH for 1.28Mcps TDD

9.2.3.19D	TDD DL DPCH Time Slot Format LCR
TDD DL DPCH Time Slot Format LCR indicates the time slot formats used in DL DPCH for 1.28Mcps TDD (see ref. TS 25.221 [19]). It also applies to PDSCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Modulation
M



>QPSK




>>QPSK TDD DL DPCH Time Slot Format LCR
M

INTEGER
(0..24,…)

>8PSK




>>8PSK TDD DL DPCH Time Slot Format LCR
M

INTEGER
(0..24,…)
For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, this IE denotes MBSFN S-CCPCH time slot format , INTEGER (0..11,…).

9.2.3.20	TDD Physical Channel Offset
The Offset represents the phase information for the allocation of a physical channel. (SFN mod Repetition Period = Offset) see ref. TS 25.331 [18].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TDD Physical Channel Offset


INTEGER (0..63)


9.2.3.21	TDD TPC DL Step Size
This parameter indicates step size for the DL power adjustment (see ref. TS 25.224 [21]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TDD TPC Downlink Step Size


ENUMERATED 
(1, 2, 3,…)
Unit: dB

9.2.3.21a	TDD TPC UL Step Size
This parameter indicates step size for the UL power adjustment (see ref. TS 25.224 [21]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TDD TPC Uplink Step Size


ENUMERATED 
(1, 2, 3,…)
Unit: dB

9.2.3.21A	TDD UL Code Information
The TDD UL Code Information IE provides information for UL Code to be established.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TDD UL Code Information

1..<maxNrOfDPCHs>


>DPCH ID
M

9.2.3.5

>TDD Channelisation Code
M

9.2.3.19


Range Bound
Explanation
maxNrOfDPCHs
Maximum number of DPCHs in one CCTrCH

9.2.3.21B	TDD UL Code Information LCR
The TDD UL Code Information LCR IE provides information for UL Code to be established.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TDD UL Code Information LCR

1..<maxNrOfDPCHLCRs>


>DPCH ID
M

9.2.3.5

>TDD Channelisation Code LCR
M

9.2.3.19a

>TDD UL DPCH Time Slot Format LCR
M

9.2.3.21C


Range Bound
Explanation
maxNrOfDPCHLCRs
Maximum number of DPCHs in one CCTrCH for 1.28Mcps TDD

9.2.3.21C	TDD UL DPCH Time Slot Format LCR
TDD UL DPCH Time Slot Format LCR indicates the time slot formats used in UL DPCH for 1.28Mcps TDD (see ref. TS 25.221 [19]). It also applies to PUSCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Modulation
M



>QPSK




>>QPSK TDD UL DPCH Time Slot Format LCR
M

INTEGER
(0..69,…)

>8PSK




>>8PSK TDD UL DPCH Time Slot Format LCR
M

INTEGER
(0..24,…)


9.2.3.22	TFCI Coding
The TFCI Coding describes the way how the TFCI bits are coded. By default 1 TFCI bit is coded with 4 bits, 2 TFCI bits are coded with 8 bits, 3-5 TFCI bits are coded with 16 bits and 6-10 TFCI bits are coded with 32 bits.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TFCI Coding


ENUMERATED 
(4, 8, 16, 32,…)


9.2.3.22a	Timing Adjustment Value
The Timing Adjustment Value IE indicates the timing correction within a Frame for 3.84Mcps TDD. Type 1 is used for the initial phase of Node B synchronisation. Type 2 is used for the steady-state phase of Node B synchronisation. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Phase



According to mapping in TS 25.123 [23]
>Initial Phase




>>Timing Adjustment Value
M

INTEGER (0..1048575,…)

>Steady State Phase




>>Timing Adjustment Value
M

INTEGER (0..255,…)


9.2.3.22b	Timing Adjustment Value LCR
The Timing Adjustment Value LCR IE indicates the timing correction within a Frame for 1.28Mcps TDD. Type 1 is used for the initial phase of Node B synchronisation. Type 2 is used for the steady-state phase of Node B synchronisation. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Phase



According to mapping in TS 25.123 [23]
>Initial Phase




>>Timing Adjustment Value
M

INTEGER (0.. 524287,…)

>Steady State Phase




>>Timing Adjustment Value
M

INTEGER (0..127,…)


9.2.3.22A	Timing Advance Applied 
Defines the need for Rx Timing Deviation measurement results to be reported in a particular cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Timing Advance Applied


ENUMERATED (
Yes, 
No)


9.2.3.23	Time Slot
The Time Slot represents the minimum time interval inside a Radio Frame that can be assigned to a Physical Channel.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Time Slot


INTEGER (0..14)


9.2.3.24	Time Slot Direction
This parameter indicates whether the TS in the cell is used in Uplink or Downlink direction.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Time Slot Direction


ENUMERATED (
UL, 
DL,
…)


9.2.3.24A	Time Slot LCR
The Time Slot LCR is the number of the traffic time slot within a 5 ms subframe of LCR TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Time Slot LCR 


INTEGER (0..6)


9.2.3.24B	Time Slot LCR Extension
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Time Slot LCR Extension


ENUMERATED (ts7,...)
ts7 indicates the MBSFN Special Timeslot for 1.28Mcps TDD MBSFN Dedicated Carrier.

9.2.3.25	Time Slot Status
This parameter indicates whether the TS in the cell is active or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Time Slot Status


ENUMERATED (
Active, 
Not Active,
…)


9.2.3.26	Transmission Diversity Applied
Defines if Transmission Diversity on  physical channels that may use closed loop transmit diversity is to be applied in a cell (see ref. TS 25.221 [19]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Transmission Diversity Applied


BOOLEAN
True: Transmission Diversity shall be applied in this Cell.
False: Transmission Diversity shall not be applied in this Cell.

9.2.3.26A	UL Timeslot ISCP
UL Timeslot ISCP is the measured interference in a uplink timeslot at the Node B, see ref. TS 25.225 [5].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL Timeslot ISCP


INTEGER (0..127)
According to mapping in TS 25.123 [23].

9.2.3.26B	UL PhysCH SF Variation
Indicates whether variation of SF in UL is supported by Radio Link or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL PhysCH SF Variation


ENUMERATED (
SF_Variation_supported, 
SF_Variation_NOT_supported)


9.2.3.26C	UL Timeslot Information
The UL Timeslot Information IE provides information on the time slot allocation for an UL DPCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL Timeslot Information

1..<maxNrOfULTSs>


>Time Slot
M

9.2.3.23

>Midamble Shift And Burst Type
M

9.2.3.7

>TFCI Presence
M

9.2.1.57

>UL Code Information
M

TDD UL Code Information 9.2.3.21A


Range Bound
Explanation
maxNrOfULTSs
Maximum number of Uplink time slots per Radio Link

9.2.3.26D	UL Time Slot ISCP Info
The UL Time Slot ISCP Info IE provides information for UL Interfernce level for each time slot within the Radio Link.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL Time Slot ISCP Info

1..<maxNrOfULTSs>


>Time Slot
M

9.2.3.23

>UL Timeslot ISCP
M

9.2.3.26A


Range Bound
Explanation
maxNrOfULTSs
Maximum number of Uplink time slots per Radio Link

9.2.3.26E	UL Timeslot Information LCR
The UL Timeslot Information IE provides information on the time slot allocation for an UL DPCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
UL Timeslot Information LCR

1..<maxNrOfULTSLCRs>


–

>Time Slot LCR
M

9.2.3.24A

–

>Midamble Shift LCR
M

9.2.3.7A

–

>TFCI Presence
M

9.2.1.57

–

>UL Code Information 
M

TDD UL Code Information LCR 9.2.3.21B

–

>PLCCH Information
O

9.2.3.31

YES
reject

Range Bound
Explanation
maxNrOfULTSLCRs
Maximum number of Uplink time slots per Radio Link for 1.28Mcps TDD.

9.2.3.26F	UL Time Slot ISCP Info LCR
The UL Time Slot ISCP Info LCR IE provides information for UL Interfernce level for each time slot within the Radio Link.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL Time Slot ISCP Info LCR

1..<maxNrOfULTSLCRs>


>Time Slot LCR
M

9.2.3.24A

>UL Timeslot ISCP
M

9.2.3.26A


Range Bound
Explanation
maxNrOfULTSLCRs
Maximum number of Uplink time slots per Radio Link for 1.28Mcps TDD

9.2.3.26G	Uplink Synchronisation Frequency
The Uplink Synchronisation Frequency IE specifies the frequency of the adjustment of the uplink transmission timing.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Uplink Synchronisation Frequency


INTEGER (1..8)
Unit: subframe
Step: 1

9.2.3.26H	Uplink Synchronisation Step Size
The Uplink Synchronisation Step Size IE specifies the step size to be used for the adjustment of the uplink transmission timing.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Uplink Synchronisation Step Size


INTEGER (1..8)
Unit: 1/8 chip
Step: 1.

9.2.3.27	USCH ID
The USCH ID uniquely identifies a USCH within a Node B Communication Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
USCH ID


INTEGER (0..255)


9.2.3.28	USCH Information
The USCH Information IE provides information for USCHs to be established.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
USCH Information

1..<maxNrOfUSCHs>


–

>USCH ID
M

9.2.3.27

–

>CCTrCH ID
M

9.2.3.3
UL CCTrCH in which the USCH is mapped
–

>Transport Format Set
M

9.2.1.59
For USCH
–

>Allocation/Retention Priority
M

9.2.1.1A

–

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
YES
ignore
>TNL QoS
O

9.2.1.58A

YES
ignore

Range Bound
Explanation
maxNrOfUSCHs
Maximum number of USCHs for one UE

9.2.3.29	USCH Information Response
The USCH Information Response IE provides information for USCHs that have been established or modified.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
USCH Information Response

1..<maxNrOfUSCHs>


>USCH ID
M

9.2.3.27

>Binding ID
O

9.2.1.4

>Transport Layer Address
O

9.2.1.63


Range Bound
Explanation
maxNrOfUSCHs
Maximum number of USCHs for one UE

9.2.3.30	SCTD Indicator
Indicates if SCTD antenna diversity is applied or not to beacon channels (see ref. TS 25.221 [19]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SCTD Indicator


ENUMERATED (
active, 
inactive)


9.2.3.31	PLCCH Information
The PLCCH Information IE carries a PLCCH assignment for a timeslot of an UL DCH-type CCTrCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common Physical Channel ID
M

9.2.1.13

PLCCH Sequence Number
M

9.2.3.32


9.2.3.32	PLCCH Sequence Number
This sequence number represents a portion of a PLCCH used to signal TPC / SS bits to a single UE. A value of zero indicates that the PLCCH assignment has been deleted.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
PLCCH Sequence Number


INTEGER (0..14)


9.2.3.33	Common Physical Channel ID 7.68Mcps
Common Physical Channel ID is the unique identifier for one common physical channel within a cell for 7.68Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common Physical Channel ID 7.68 Mcps


INTEGER (0..511)


9.2.3.34	TDD Channelisation Code 7.68Mcps
The Channelisation Code Number indicates which Channelisation Code is used for a given Physical Channel. In 7.68Mcps TDD the Channelisation Code is an Orthogonal Variable Spreading Factor code that can have a spreading factor of 1, 2, 4, 8, 16 or 32.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TDD Channelisation Code 


ENUMERATED((1/1), (2/1), (2/2), (4/1), .. (4/4), (8/1), .. (8/8), (16/1), .. (16/16), (32/1), .. (32,32),… )


9.2.3.35	Midamble Shift And Burst Type 7.68Mcps
This information element indicates burst type and midamble allocation for burst types 1,2 and 3 for 7.68Mcps TDD.
Three different midamble allocation schemes exist:
Default midamble: the midamble is allocated by layer 1 depending on the associated channelisation code (DL and UL)
Common midamble: the midamble is allocated by layer 1 depending on the number of channelisation codes (possible in DL only)
UE specific midamble: a UE specific midamble is explicitly assigned (DL and UL)
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE Burst Type




>Type1




>>Midamble Configuration Burst Type 1 And 3
M

ENUMERATED (4, 8, 16)
As defined in TS 25.221 [19]
>>CHOICE Midamble Allocation Mode
M



>>>Default Midamble


NULL

>>>Common Midamble


NULL

>>>UE Specific Midamble




>>Midamble Shift Long
M

INTEGER (0..15)

>Type2




>>Midamble Configuration Burst Type 2
M

 ENUMERATED 
(4, 8)
As defined in TS 25.221 [19]
>>CHOICE Midamble Allocation Mode
M



>>>Default Midamble


NULL

>>>Common Midamble


NULL

>>>UE Specific Midamble




>>Midamble Shift Short
M

INTEGER (0..7)

>Type3



UL only
>>Midamble Configuration Burst Type 1 And 3
M

ENUMERATED (4, 8, 16)
As defined in TS 25.221 [19]
>>CHOICE Midamble Allocation Mode
M



>>>Default Midamble


NULL

>>>UE Specific Midamble




>>Midamble Shift Long
M

INTEGER (0..15)


9.2.3.36	Common Physical Channel Status Information 7.68Mcps
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common Physical Channel ID 7.68 Mcps
M

9.2.3.33

Resource Operational State
M

9.2.1.52

Availability Status
M

9.2.1.2


9.2.3.37	Neighbouring TDD Cell Measurement Information 7.68Mcps
This IE provides information on the 7.68 Mcps TDD neighbouring cells used for the purpose of measurements. Since the measurement can be performed on every time slot and midamble shift, the Time Slot IE and Midamble Shift And Burst Type 7.68Mcps IE shall be included if available.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UC-Id
M

9.2.1.65B

UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Cell Parameter ID
M

9.2.3.4

Time Slot
O

9.2.3.23

Midamble Shift And Burst Type 7.68Mcps
O

9.2.3.35


9.2.3.38	UL Timeslot Information 7.68Mcps TDD
The UL Timeslot Information IE provides information on the time slot allocation for an UL DPCH for 7.68Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL Timeslot Information

1..<maxNrOfULTSs>


>Time Slot
M

9.2.3.23

>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

>TFCI Presence
M

9.2.1.57

>UL Code Information
M

TDD UL Code Information 7.68Mcps TDD 9.2.3.40


Range Bound
Explanation
maxNrOfULTSs
Maximum number of Uplink time slots per Radio Link

9.2.3.39	DL Timeslot Information 7.68Mcps TDD
The DL Timeslot Information IE provides information for DL Time slot to be established for 7.68Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DL Timeslot Information

1..<maxNrOfDLTSs>


>Time Slot
M

9.2.3.23

>Midamble Shift And Burst Type 7.68Mcps
M

9.2.3.35

>TFCI Presence
M

9.2.1.57

>DL Code Information
M

TDD DL Code Information 7.68Mcps TDD 9.2.3.41


Range Bound
Explanation
maxNrOfDLTSs
Maximum number of Downlink time slots per Radio Link

9.2.3.40	TDD UL Code Information 7.68Mcps TDD
The TDD UL Code Information 7.68Mcps TDD IE provides information for UL Code to be established for 7.68Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TDD UL Code Information

1..<maxNrOfDPCHs>


>DPCH ID
M

9.2.3.5

>TDD Channelisation Code 7.68Mcps
M

9.2.3.34


Range Bound
Explanation
maxNrOfDPCHs
Maximum number of uplink DPCHs in one CCTrCH at 7.68Mcps

9.2.3.41	TDD DL Code Information 7.68Mcps TDD
The TDD Code Information 7.68Mcps TDD IE provides DL Code information for the RL for 7.68Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TDD DL Code Information

1..<maxNrOfDPCHs768>


>DPCH ID
M

9.2.3.5

>TDD Channelisation Code 7.68Mcps
M

9.2.3.34


Range Bound
Explanation
maxNrOfDPCHs768
Maximum number of downlink DPCHs in one CCTrCH at 7.68Mcps

9.2.3.42	DPCH ID 7.68Mcps
The DPCH ID 7.68Mcps identifies unambiguously a DPCH inside a downlink Radio Link for 7.68Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
DPCH ID


INTEGER (0..479)


9.2.3.43	PDSCH ID 7.68Mcps
The PDSCH ID 7.68Mcps identifies unambiguously a PDSCH inside a cell for 7.68Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
PDSCH ID


INTEGER (0..511)


9.2.3.44	Max E-RUCCH Midamble Shift
Indicates the maximum number of Midamble shifts to be used in a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Max E-RUCCH Midamble Shift


ENUMERATED 
(4, 8,…,16)


9.2.3.45	E-PUCH Information
The E-PUCH Information IE provides parameters to configure the E-PUCH physical channel for 3.84Mcps TDD and 7.68 Mcps TDD. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Minimum code rate
M

INTEGER (0..63)

Unit: -
Range: 0.055 ..1
Step: 0.015 
Maximum code rate
M

INTEGER (0..63)

Unit: -
Range: 0.055 ..1
Step: 0.015 
HARQ Info for E-DCH
M

ENUMERATED (rv0, rvtable)

 “rv0”  indicates that  the UE will only use E_DCH RV index 0.
“rvtable” indicates that  the UE will use an RSN based RV index as specified in TS 25.212 [8]
NE-UCCH
M

INTEGER (1..12)
Number of slots that are required to carry TPC and TFCI (consecutively allocated slots beginning with the first). 

9.2.3.45a	E-PUCH Information LCR
The E-PUCH Information LCR IE provides parameters to configure the E-PUCH physical channel for 1.28Mcps TDD. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Minimum code rate
M

INTEGER (0..63)

Unit: -
Range: 0.055 ..1
Step: 0.015 
–

Maximum code rate
M

INTEGER (0..63)

Unit: -
Range: 0.055 ..1
Step: 0.015 
–

HARQ Info for E-DCH
M

ENUMERATED (rv0, rvtable)

 “rv0”  indicates that  the UE will only use E_DCH RV index 0.
“rvtable” indicates that  the UE will use an RSN based RV index as specified in TS 25.212 [8]
–

PRXdes_base
M

INTEGER 
(-112..-50)
dBm. Reference Desired RX power level for E-PUCH.
Reference to Pe-base in TS 25.224 [21] 
–

E-PUCH TPC Step Size 
M

TDD TPC UL Step Size
9.2.3.21a

–

E-AGCH TPC Step Size
M

TDD TPC DL Step Size
9.2.3.21

–

E-PUCH Power Control GAP
O

INTEGER (1..255)
Unit: Number of subframes.
Reference to E-PUCH Power Control for 1.28Mcps TDD in TS 25.224 [21]. If it is not present, UE shall deem it to be infinite in which case closed loop power control shall always be used.
YES
ignore

9.2.3.46	E-TFCS Information TDD
Whereas the related E-DCH Transport Block sizes are standardised in TS 25.321 [32] this IE gives details on the Reference Betas.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Reference Beta Information QPSK

1..<maxnoofRefbeta s>


>Reference Code Rate
M

INTEGER (0..10)

Unit: -
Range: 0 ..1
Step: 0.1 
>Reference Beta
M

INTEGER(-15..16)
Unit: -
Range: -15..+16
Step: 1 dB
Reference Beta Information 16QAM

1..<maxnoofRefbeta s>


>Reference Code Rate
M

INTEGER (0..10)

Unit: -
Range: 0 ..1
Step: 0.1 
>Reference Beta
M

INTEGER(-15..16)
Unit: -
Range: -15..+16
Step: 1 dB

Range Bound
Explanation
maxnoofRefbetas
Maximum number of signalled reference betas

9.2.3.47	E-DCH MAC-d Flows Information TDD
The E-DCH MAC-d Flows Information TDD IE is used for the establishment of E-DCH MAC-d flows for TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH MAC-d Flow Specific Information

1..<maxNrOfEDCHMACdFlows>


>E-DCH MAC-d Flow ID
M

9.2.1.74

>Allocation/Retention Priority
M

9.2.1.1A

>TNL QoS
O

9.2.1.58A

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
>Payload CRC Presence Indicator
M

9.2.1.49

>Maximum Number Of Retransmissions For E-DCH
M

9.2.1.81

>E-DCH HARQ Power Offset TDD
M

9.2.3.61

>E-DCH MAC-d Flow Multiplexing List
O

9.2.1.69

>E-DCH Grant TypeTDD
M

9.2.3.53

>E-DCH Logical Channel Information
M

9.2.1.71

>E-DCH MAC-d Flow Retransmission Timer
O

9.2.3.61a
Mandatory for LCR TDD.
Not applicable for 3.84Mcps TDD and 7.68Mcps TDD.

Range Bound
Explanation
maxNrOfEDCHMACdFlows
Maximum number of E-DCH MAC-d flows

9.2.3.48	E-DCH Non-scheduled Grant Information TDD
The E-DCH Non-scheduled Grant Information TDD IE is used to specify the details of a non-scheduled grant for TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Timeslot Resource Related Information
M

9.2.3.54

Power Resource Related Information
M

9.2.3.55

Repetition Period
M

9.2.3.16

Repetition Length
M

9.2.3.15

TDD E-PUCH Offset
M

9.2.3.56

TDD Channelisation Code
M

9.2.3.19


9.2.3.48a	E-DCH Non-scheduled Grant Information LCR TDD
Only for 1.28Mcps TDD. The E-DCH Non-scheduled Grant Information LCR TDD IE is used to specify the details of a non-scheduled grant for 1.28Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Timeslot Resource Related Information LCR
M

9.2.3.54a

–

Power Resource Related Information
M

9.2.3.55

–

Repetition Period
M

9.2.3.16

–

Repetition Length
M

9.2.3.15

–

Subframe Number
M

ENUMERATED (
0,1)
Used to indicate from which subframe of the Radio Frame indicated by TDD E-PUCH Offset IE the physical resources are assigned to the E-DCH Non-scheduled Grant.
–

TDD E-PUCH Offset
M

9.2.3.56

–

TDD Channelisation Code
M

9.2.3.19

–

NE-UCCH
M

INTEGER (1..8)
Number of E-UCCH and TPC instances within an E-DCH TTI. Details are described in TS 25.221 [19] . 
–

E-HICH Information

1




>E-HICH ID TDD
M

9.2.3.51a
If the Extended E-HICH ID TDD IE is included in the E-HICH Information IE, the E-HICH ID TDD IE shall be ignored.
–

>Signature Sequence Group Index
M

INTEGER (0..19)

–

>Extended E-HICH ID TDD
O

9.2.3.51b
Applicable to 1.28Mcps TDD only, the Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31.
YES
ignore

9.2.3.49	E-DCH TDD Information
The E-DCH TDD Information specifies the details of the maximum bit rate and processing overload level.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH TDD Maximum Bitrate
O

9.2.3.57

E-DCH Processing Overload Level
O

9.2.1.79

E-DCH Power Offset for Scheduling Info
O

9.2.1.85


9.2.3.49a	E-DCH TDD Information LCR
Only for 1.28Mcps TDD. The E-DCH TDD Information LCR IE specifies the details of the UE physical layer category, Node B processing overload level and power offset, Maximum Number of Retransmission and E-DCH Retransmission timer for scheduling info. The E-AGCH Inactivity Monitor Threshold IE is used for E-AGCH channel monitoring control for scheduled transmission.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-DCH Physical Layer Category LCR
O

9.2.3.67
If the Extended E-DCH Physical Layer Category LCR IE is included in the E-DCH TDD Information LCR IE, the E-DCH Physical Layer Category LCR IE shall be ignored.
In case of multi-carrier E-DCH, this IE indicates the capability for each carrier.
–

E-DCH Processing Overload Level
O

9.2.1.79

–

E-DCH Power Offset for Scheduling Info
O

9.2.1.85

–

Extended E-DCH Physical Layer Category LCR
O

9.2.3.67A
The Extended E-DCH Physical Layer Category LCR IE shall be used if the E-DCH Physical Layer Category has a value larger than 5.
In case of multi-carrier E-DCH, this IE indicates the capability for each carrier.
YES
reject
Maximum Number of Retransmission for Scheduling Info LCR
O

Maximum Number of Retransmissions for E-DCH
9.2.1.81

YES
ignore
E-DCH Retransmission timer for Scheduling Info LCR
O

E-DCH MAC-d Flow Retransmission Timer
9.2.3.61a

YES
ignore
E-AGCH Inactivity Monitor Threshold
O

Enumerated (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, spare5, …, infinity)
Units of subframes.

YES
ignore
SNPL Carrier Group Indicator
O

INTEGER 
(1..3)
Applicable to 1.28Mcps TDD in multi-carrier E-DCH operation only. 

Indicate which SNPL carrier group the carrier indicated by the UARFCN IE in the RL Information IE belongs to.

The absence of this IE indicates the corresponding frequency belongs to a separate SNPL carrier group which only contains this carrier. Shall be ignored if Multi-Carrier E-DCH Information is not configured.
YES
ignore
Multi-Carrier E-DCH Physical Layer Category LCR
O

9.2.3.67B
Applicable to 1.28Mcps TDD in multi-carrier E-DCH operation only.
YES
reject
UE TS0 Capability LCR
O

9.2.3.110
Applicable to 1.28Mcps TDD only.
YES
ignore

9.2.3.50	E-DCH TDD Information Response
The E-DCH TDD Information Response IE provides information for E-DCH MAC-d flows that have been established or modified. It also provides additional E-DCH information determined within the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-DCH TDD MAC-d Flow Specific Information Response

0..<maxNrOfEDCHMACdFlows>


–

>E-DCH MAC-d Flow ID
M

9.2.1.74

–

>Binding ID
O

9.2.1.4

–

>Transport Layer Address
O

9.2.1.63

–

E-AGCH Specific Information Response TDD

0..<maxNrOfEAGCHCodes> 


–

>E-AGCH ID TDD
M

9.2.3.51

–

E-RNTI
M

9.2.1.75

–

Scheduled E-HICH Specific Information Response 1.28Mcps TDD 

0..<maxNrOfEHICHCodes>

1.28Mcps TDD only
–

>EI
M

INTEGER (0..3)
E-HICH indication which is used to indicate UE on which E-HICH the feedback info is carried.
–

>E-HICH ID TDD
M

9.2.3.51a
If the Extended E-HICH ID TDD IE is included in the E-HICH Information IE, the E-HICH ID TDD IE shall be ignored
–

>Extended E-HICH ID TDD
O

9.2.3.51b
Applicable to 1.28Mcps TDD only, the Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31.
YES
ignore

Range bound
Explanation
maxNrOfEDCHMACdFlows
Maximum number of MAC-d flows
maxNrOfEAGCHCodes
Maximum number of E-AGCHs assigned to one UE
maxNrOfEHICHCodes
Maximum number of E-HICHs assigned to one UE

9.2.3.51	E-AGCH ID TDD
The E-AGCH ID identifies unambiguously an E-AGCH inside a cell for TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-AGCH ID


INTEGER (0..31,...,32..255)


9.2.3.51a	E-HICH ID TDD
The E-HICH ID TDD IE identifies unambiguously an E-HICH inside a cell for 1.28Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-HICH ID TDD


INTEGER (0..31)


9.2.3.51b	Extended E-HICH ID TDD
The Extended E-HICH ID TDD IE identifies unambiguously an E-HICH inside a cell for 1.28Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Extended E-HICH ID TDD


INTEGER (32..255)


9.2.3.52	E-DCH TDD Information to Modify
The E-DCH TDD Information to Modify IE is used for the modification of an E-DCH. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
E-DCH MAC-d Flow Specific Information

0..<maxNrOfEDCHMACdFlows>


–

>E-DCH MAC-d Flow ID
M

9.2.1.74

–

>Allocation/Retention Priority
O

9.2.1.1A

–

>Transport Bearer Request Indicator
M

9.2.1.62A

–

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
–

>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
–

>TNL QoS
O

9.2.1.58A

–

>Maximum Number Of Retransmissions for E-DCH
O

9.2.1.81

–

>E-DCH HARQ Power Offset TDD
O

9.2.3.61

–

>E-DCH MAC-d Flow Multiplexing  List
O

9.2.1.69

–

>E-DCH Grant Type
O

9.2.3.53

–

>E-DCH Logical Channel To Add
O

E-DCH Logical Channel Information
9.2.1.71

–

>E-DCH Logical Channel To Modify
O

9.2.1.72

–

>E-DCH Logical Channel To Delete 

0..<maxnooflogicalchannels>


–

>>Logical Channel ID
M

9.2.1.80

–

>E-DCH MAC-d Flow Retransmission Timer
O

9.2.3.61a
LCR TDD only.
–

MAC-e Reset Indicator
O

9.2.1.83

–

E-DCH MAC-d PDU Size Format
O

9.2.1.74B

YES
reject
UE TS0 Capability LCR
O

9.2.3.110
Applicable to 1.28Mcps TDD only.
YES
ignore

Range Bound
Explanation
maxNrOfEDCHMACdFlows
Maximum number of E-DCH MAC-d flows
maxnooflogicalchannels
Maximum number of logical channels

9.2.3.53	E-DCH Grant Type TDD
The E-DCH Grant Type identifies whether a MAC-d flow is scheduled or non-scheduled.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH Grant Type


ENUMERATED (Scheduled, Non-scheduled)


9.2.3.54	Timeslot Resource Related Information
The Timeslot Resource Related Information is a bitmap indicating which of the timeslots configured for E-DCH are allocated for non-scheduled transmissions.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Timeslot Resource Related Information


BIT STRING (SIZE(13))


9.2.3.54a	Timeslot Resource Related Information LCR
Only for 1.28Mcps TDD. The Timeslot Resource Related Information LCR IE is a bitmap indicating which of the timeslots configured for E-DCH are allocated for non-scheduled transmissions.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Timeslot Resource Related Information LCR


BIT STRING (SIZE(5))


9.2.3.55	Power Resource Related Information
The Power Resource Related Information specifies the maximum allowed E-PUCH power resource (dB relative to Pe-base) that the UE may use for non-scheduled transmissions.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Power Resource Related Information


INTEGER (1..32)
The Value indicates 0-31 PRRI index for mapping of Absolute Grant Value in TS 25.222 [34].

9.2.3.56	E-PUCH Offset
The E-PUCH Offset represents the CFN offset at which a non-scheduled E-DCH grant begins.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-PUCH Offset


INTEGER (0..255)


9.2.3.57	E-DCH TDD Maximum Bitrate
The E-DCH TDD Maximum Bitrate parameter indicates the Maximum Bitrate for an E-DCH in TDD mode.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH TDD Maximum Bitrate


INTEGER (0..9201,…)
Bitrate on transport block level. Unit is kbits per second. 

9.2.3.58	LTGI Presence
The LTGI Presence indicates to the Node B whether it shall use the Long Term Grant Indicator within E-DCH grants issued in a cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
LTGI Indicator 


BOOLEAN
True = LTGI shall be included

9.2.3.59	E-HICH Time Offset
The E-HICH Time Offset ( aka nE-HICH  (TS 25.221 [19]))is determined by the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-HICH Time Offset 


INTEGER (4..44)


9.2.3.59a	E-HICH Time Offset LCR
Only for 1.28Mcps TDD. The E-HICH Time Offset LCR IE(aka nE-HICH  (TS 25.221 [19]))is determined by the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-HICH Time Offset LCR


INTEGER (4..15)


9.2.3.60	E-DCH TDD Capacity Consumption Law
The capacity consumption law indicates to the CRNC how the Capacity Credit is consumed by NBAP set of procedures, depending on the number of E-AGCH.  
This capacity consumption law indicates the consumption law to be used with the following procedures:
-	Physical Shared Channel Reconfiguration.
When one are more radio links have been configured to use E-DCH (via Radio Link Setup, Radio Link Addition or radio link reconfiguration procedures) the cost given in the consumption law shall be debited from the Capacity Credit, whereas it shall credited to the Capacity Credit for the Radio Link Deletion procedure that removes the last radio link configured for E-DCH. 
If the modelling of the internal resource capability of the Node B is modelled independently for the Uplink and Downlink, the DL cost shall be applied to the DL or Global Capacity Credit and the UL Cost shall be applied to the UL Capacity Credit. If it is modelled as shared resources, both the DL costs and the UL costs shall be applied to the DL or Global Capacity Credit.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UL Cost
M

INTEGER (0..65535)
Cost per timeslot of the E-DCH. If not present, zero cost shall be applied. 
DL Cost
O

INTEGER (0..65535)
Cost per E-AGCH or E-HICH configured. If not present, zero cost shall be applied. .

9.2.3.61	E-DCH HARQ Power Offset TDD
The E-DCH HARQ Power Offset TDD is the power offset measured in dB.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH HARQ Power Offset TDD


INTEGER (0..6)


9.2.3.61a	E-DCH MAC-d Flow Retransmission Timer
Only for 1.28Mcps TDD. The E-DCH MAC-d Flow Retransmission Timer IE is used in the E-DCH retransmission control as defined in TS 25.321 [32].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH MAC-d Flow Retransmission Timer


ENUMERATED (10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 110, 120, 140, 160, 200, 240, 280, 320, 400, 480, 560,…)
Unit: ms
Node B may use this value to stop the re-transmission of the corresponding MAC-e PDU.

9.2.3.62	SNPL Reporting Type
The SNPL Reporting Type indicates to the Node B whether the UEs in a cell shall use the type 1 or type 2 Serving and Neighbour Cell Pathloss metric (TS 25.224 [21]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
SNPL Reporting Type 


ENUMERATED (type1, type2)


9.2.3.63	Maximum Generated Received Total Wide Band Power in Other Cells 
The Maximum Generated Received Total Wide Band Power in Other Cells indicates the maximum aggregate UL interference that may be generated from scheduled transmissions into other (non-serving) cells.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Maximum Generated Received Total Wide Band Power in Other Cells


INTEGER (0..621)
The Value mapping is according to mapping for measurement type "Received Total Wide Band Power" in TS 25.123 [23].

9.2.3.64	E-DCH Non-scheduled Grant Information 7.68Mcps TDD
The E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE is used to specify the details of a non-scheduled grant for 7.68Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Timeslot Resource Related Information
M

9.2.3.54

Power Resource Related Information
M

9.2.3.55

Repetition Period
M

9.2.3.16

Repetition Length
M

9.2.3.15

TDD E-PUCH Offset
M

9.2.3.56

TDD Channelisation Code 7.68Mcps
M

9.2.3.34


9.2.3.65	E-DCH TDD Information 7.68Mcps
The E-DCH TDD Information 7.68Mcps specifies the details of the maximum bit rate and processing overload level for 7.68Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH TDD Maximum Bitrate 7.68Mcps
O

9.2.3.66

E-DCH Processing Overload Level
O

9.2.1.79

E-DCH Power Offset for Scheduling Info
O

9.2.1.85


9.2.3.66	E-DCH TDD Maximum Bitrate 7.68Mcps
The E-DCH TDD Maximum Bitrate 7.68Mcps parameter indicates the Maximum Bitrate for an E-DCH in 7.68Mcps TDD mode.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH TDD Maximum Bitrate 7.68Mcps


INTEGER (0..17713,…)
Bitrate on transport block level. Unit is kbits per second. 

9.2.3.67	E-DCH Physical Layer Category LCR
Only for 1.28Mcps TDD. The E-DCH Physical Layer Category LCR IE parameter indicates the  E-DCH physical layer capability of UE in LCR TDD mode.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH Physical Layer Category LCR


INTEGER(1..5)
As defined in TS 25.306 [33]

9.2.3.67A	Extended E-DCH Physical Layer Category LCR
Only for 1.28Mcps TDD. The Extended E-DCH Physical Layer Category LCR IE parameter indicates the E-DCH physical layer capability of UE in LCR TDD mode.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Extended E-DCH Physical Layer Category LCR


INTEGER(6,...)
As defined in TS 25.306 [33]

9.2.3.67B	Multi-Carrier E-DCH Physical Layer Category LCR
Only for 1.28Mcps TDD. The Multi-Carrier E-DCH Physical Layer Category LCR IE parameter indicates the E-DCH physical layer capability of UE in multi-carrier E-DCH operation mode.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Multi-Carrier E-DCH Physical Layer Category LCR


INTEGER(1..8,…)
As defined in TS 25.306 [33]

9.2.3.68	E-HICH Type
The E-HICH Type IE identifies whether a E-HICH is scheduled or non-scheduled inside a cell for 1.28Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-HICH Type


ENUMERATED (
Scheduled, Non-scheduled)


9.2.3.69	Maximum Target Received Total Wide Band Power LCR
The Maximum Target Received Total Wide Band Power LCR indicates the maximum target UL interference for a certain cell or frequency or cell portion under CRNC, including received wide band power from all sources. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Maximum Target Received Total Wide Band Power LCR


INTEGER (0..621)
The Value mapping is according to mapping for measurement type "Received Total Wide Band Power" in TS 25.123 [23].

9.2.3.70	MBSFN Only Mode Indicator
The MBSFN only mode indicator indicates from CRNC to the Node B whether the cell is setup for MBSFN only mode for 1.28Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MBSFN Only Mode Indicator


ENUMERATED (
MBSFN Only Mode)


9.2.3.71	MBSFN Only Mode Capability
This parameter defines the MBSFN only mode capability for a local cell for 1.28Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MBSFN Only Mode Capability


ENUMERATED (
MBSFN Only Mode capable, MBSFN Only Mode non capable)


9.2.3.72	HS-DSCH Common System Information LCR
The HS-DSCH Common System Information LCR IE provides information for HS-DSCH configured for UE in Cell_FACH, Cell_PCH and URA_PCH and Information related to BCCH modification.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH Common Information LCR

0..1


>CCCH Priority Queue ID



M

Priority Queue ID
9.2.1.49C
Applicable for all carriers when using multiple frequencies.
>SRB#1 Priority Queue ID

M

Priority Queue ID
9.2.1.49C
Applicable for all carriers when using multiple frequencies.
>Associated Common MAC Flow LCR
M

Common MAC Flow ID LCR
9.2.3.76
The Common MAC Flow ID LCR shall be one of the flow IDs defined in the Common MAC Flow Specific Information of this IE or shall only refer to a Common MAC flow already existing in the old configuration.
>FACH Measurement Occasion Cycle Length Coefficient
O

9.2.1.111

>BCCH Specific HS-DSCH RNTI Information LCR
O

9.2.3.89


Common MAC Flow Specific Information LCR

0..<maxNrOfCommonMACFlowsLCR>


>Common MAC Flow ID LCR
M

9.2.3.76

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP.
>Common MAC Flow Priority Queue Information LCR

0..<maxNrOfcommonMACQueues>


>>Priority Queue Information for Enhanced FACH
M

Priority Queue Information for Enhanced FACH/PCH
9.2.1.117

>Transport Bearer Request Indicator
O

9.2.1.62A
Shouldn’t be contained if the MAC flow is setup in procedure.
Should be contained if the MAC flow is modified in procedure
>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Applicable for 1.28Mcps TDD when using multiple frequencies.
Common H-RNTI Information

0..<maxNrOfCommonHRNTI>


>Common H-RNTI
M

HS-DSCH RNTI
9.2.1.31J

Sync Information

0..1


>T-sync
M

ENUMERATED (40, 80, 120, 160, 200, 300, 400, 500, …)
Units of MS.
>T-protect
M

ENUMERATED (40, 60, 80, 100, 120, 200, 400, …)
Units of MS.
>N-protect
M

INTEGER (0..7)

TDD ACK NACK Power Offset
O

9.2.3.18F
9.2.1.67A

HS-SICH SIR Target
O

UL SIR
9.2.1.67A

HS-SICH TPC step size
O

TDD TPC UL Step Size 
9.2.3.21a


Range bound
Explanation
maxNrOfCommonMACFlowsLCR
Maximum number of Common MAC Flows for 1.28Mcps TDD
 maxNrOfcommonMACQueues
Maximum number of Priority Queues for Common MAC Flow for 1.28Mcps TDD
maxNrOfCommonHRNTI
Maximum number of Common H-RNTI

9.2.3.73	HS-DSCH Paging System Information LCR
The HS-DSCH Paging System Information LCR IE provides information for HS-DSCH configured for UE in Cell_PCH and URA_PCH.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Paging MAC Flow Specific Information LCR

0..<maxNrOfPagingMACFlow>


>Paging MAC Flow ID
M

9.2.1.113

>HSDPA Associated PICH Information LCR
O

9.2.3.77

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP.
>ToAWS
O

9.2.1.61

>ToAWE
O

9.2.1.60

>Paging MAC Flow Priority Queue Information LCR

0..<maxNrOfpagingMACQueues>


>>Priority Queue Information for Enhanced PCH
M

Priority Queue Information for Enhanced FACH/PCH
9.2.1.117

>Transport Bearer Request Indicator
O

9.2.1.62A
Shouldn’t be contained if the MAC flow is setup in procedure.
Should be contained if the MAC flow is modified in procedure
HS-SCCH Power
O

DL Power
9.2.1.21

HS-PDSCH Power
O

DL Power
9.2.1.21

DTCH/DCCH Reception window size
O

INTEGER (1..16)
Number of subframes for UE to detect the HS-SCCH
NPCH
O

INTEGER (1..8)

Paging Sub-Channel Size
O

INTEGER (1..3)
number of frames for a Paging sub-channel
Transport Block Size List

0..<maxNrOfHS-DSCHTBSsE-PCH>


>Transport Block Size Index for Enhanced PCH
M

INTEGER (1..32)
Index of the value range 1 to 32 of the MAC-ehs transport block size as specified in TS 25.321 [32]

Range bound
Explanation
maxNrOfPagingMACFlow
Maximum number of Paging MAC Flows
maxNrOfpagingMACQueues
Maximum number of Priority Queues for Paging MAC Flow
maxNrOfHS-DSCHTBSsE-PCH
Maximum number of HS-DSCH Transport Block Sizes used for Enhanced PCH operation associated HS-SCCH less

9.2.3.74	HS-DSCH Common System Information Response LCR
The HS-DSCH Common System Information Response LCR IE provides information for HS-DSCH configured for UE not in Cell_DCH that have been established or modified.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-SCCH Specific Information Response LCR

0..<maxNrOfHSSCCHsLCR>


-

>HS SCCH ID LCR
M

9.2.3.88
The HS-SCCH ID of the HS-SCCH used for the BCCH specific H-RNTI should be the minimum on each frequency.
-

HARQ Memory Partitioning 
O

9.2.1.102

-

Common MAC Flow
Specific Information Response LCR

0..<maxNrOfCommonMACFlowsLCR>


-

>Common MAC Flow ID LCR
M

9.2.3.76

-

>Binding ID
O

9.2.1.4

-

>Transport Layer Address
O

9.2.1.63

-

>HS-DSCH Initial Capacity Allocation
O

9.2.1.31Ha

-

UARFCN
O

9.2.1.65
Applicable to 1.28Mcps TDD when using multiple frequencies. This is the UARFCN for the first Frequency repetition of HARQ Memory Partitioning
YES
reject
HARQ Memory Partitioning Per UARFCN

0..<maxFrequencyinCell-1>

Corresponds to Nt (TS 25.105 [15]).
Applicable for 1.28Mcps TDD when using multiple frequencies.
GLOBAL
reject
>HARQ Memory Partitioning 
M

9.2.1.102

-

>UARFCN
M

9.2.1.65

-


Range Bound
Explanation
maxNrOfCommonMACFlowsLCR
Maximum number of Common MAC Flows for 1.28Mcps TDD
maxNrOfHSSCCHsLCR
Maximum number of HS-SCCH codes for 1.28Mcps TDD
maxFrequencyinCell-1
Maximum number of frequencies that can be used in the cell minus 1

9.2.3.75	HS-DSCH Paging System Information Response LCR
The HS-DSCH Paging System Information Response LCR IE provides information for HS-DSCH configured for UE in Cell_PCH and URA_PCH that have been established or modified.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Paging MAC Flow Specific Information Response LCR

0..<maxNrOfPagingMACFlow>


>Paging MAC Flow ID
M

9.2.1.113

>Binding ID
O

9.2.1.4

>Transport Layer Address
O

9.2.1.63

>HS-PDSCH DL Timeslot and Code Information LCR

0..<maxNrOfDLTSLCRs >


>>Time Slot LCR
M

9.2.3.24A

>>Midamble Shift LCR
M

9.2.3.7A

>>Codes LCR

1..<maxNrOfHSPDSCHs>


>>>TDD Channelisation Code
M

9.2.3.19


Range bound
Explanation
maxNrOfPagingMACFlow
Maximum number of Paging MAC Flows
maxNrOfDLTSLCRs
Maximum number of Downlink time slots in a cell for 1.28Mcps TDD
maxNrOfHSPDSCHs
Maximum number of HS-PDSCHs in one time slot of a Cell for 1.28Mcps TDD

9.2.3.76	Common MAC Flow ID LCR
The Common MAC Flow ID LCR IE is the unique identifier for one Common MAC flow.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common MAC Flow ID LCR


INTEGER
(0..255)


9.2.3.77	HSDPA Associated PICH Information LCR
The HSDPA Associated PICH Information LCR IE provides information for PICH used for Enhanced PCH operation.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE HSDPA PICH




>Shared with PCH




>>Common Physical Channel ID
M

9.2.1.13

>Not shared with PCH LCR




>>Common Physical Channel ID
M

9.2.1.13

>> TDD Channelisation Code LCR
M

9.2.3.19a

>> Time Slot LCR
M

9.2.3.24A

>>Midamble Shift LCR
Offset
M

Midamble Shift LCR
9.2.3.7A

>>TDD Physical Channel offset
M

9.2.3.20

>>Repetition Period
M

9.2.3.16

>>Repetition Length
M

9.2.3.15

>>Paging Indicator Length
M

9.2.3.8

>>PICH Power
M

9.2.1.49A

>> Second TDD Code LCR Code LCR
M

TDD Channelisation Code LCR 9.2.3.19a

>>TSTD Indicator
O

9.2.1.64


9.2.3.78	Common MAC Flows To Delete LCR
The Common MAC Flows To Delete LCR IE is used for the removal of Common MAC flows from a Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common MAC Flows To Delete LCR

1..<maxNrOfCommonMACFlowsLCR>


>Common MAC Flow ID LCR
M

9.2.3.76


Range Bound
Explanation
maxNrOfCommonMACFlowsLCR
Maximum number of Common MAC Flows for 1.28Mcps TDD

9.2.3.79	Common E-DCH System Information LCR
The Common E-DCH System Information LCR IE provides information for E-DCH configured for UE in Cell_FACH and Idle state.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
UL Common MAC Flow Specific Information LCR

0..<maxNrOfCommonMACFlowsLCR>


–

>UL Common MAC Flow ID
M

Common MAC Flow ID LCR
9.2.3.76

–

>Transport Bearer Request Indicator
O

9.2.1.62A

–

>Binding ID
O

9.2.1.4
Shall be ignored if bearer establishment with ALCAP.
–

>Transport Layer Address
O

9.2.1.63
Shall be ignored if bearer establishment with ALCAP.
–

>TNL QoS
O

9.2.1.58A
Shall be ignored if bearer establishment with ALCAP.
–

>Payload CRC Presence Indicator
O

9.2.1.49

–

>Common E-DCH MAC-d Flow Specific Information LCR
O

9.2.3.81

–

>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Applicable for 1.28Mcps TDD when using multiple frequencies.
–

Common E-PUCH Information LCR
O

9.2.3.83

–

E-TFCS Information TDD
O

9.2.3.46

–

Maximum Number of Retransmission for Scheduling Info LCR
O

Maximum Number of Retransmissions for E-DCH 
9.2.1.81

–

E-DCH Retransmission timer for Scheduling Info LCR
O

E-DCH MAC-d Flow Retransmission Timer
9.2.3.61a

–

UL Synchronisation Parameters LCR

0..1


YES
reject
>Uplink Synchronisation Step Size
M

9.2.3.26H

–

>Uplink Synchronisation Frequency
M

9.2.3.26G

–

Physical Channel ID for Common E-RNTI Requested Indicator
O

Enumerated(requested)

YES
ignore

Range bound
Explanation
maxNrOfCommonMACFlowsLCR
Maximum number of Common MAC Flows

9.2.3.80	Common E-DCH System Information Response LCR
The Common E-DCH System Information Response LCR IE provides information for E-DCH configured for UE in Cell_FACH and Idle state that have been established or modified.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
UL Common MAC Flow Specific Information Response LCR

0..<maxnoofEDCHMACFlowsLCR>

See Note 1 below


>UL Common MAC Flow ID
M

Common MAC Flow ID LCR
9.2.3.76

–
–
>Binding ID
O

9.2.1.4

–
–
>Transport Layer Address
O

9.2.1.63

–
–
E-AGCH Specific Information Response TDD

0..<maxNrOfEAGCHsLCR> 




>E-AGCH ID TDD
M

9.2.3.51

–
–
E-HICH Specific Information Response 1.28Mcps TDD 

0..<maxNrOfEHICHsLCR>

1.28Mcps TDD only


>EI
M

INTEGER (0..3)
E-HICH indication which is used to indicate UE on which E-HICH the feedback info is carried.
–
–
>E-HICH ID TDD LCR
M

9.2.3.51a

–
–
Common E-RNTI Information LCR
O

9.2.3.84

–
–
UE Status Update Confirm Indicator
O

BOOLEAN
TRUE means that the Node B supports UE Status Update Confirmation Procedure
YES
ignore
Note1: This information element is a simplified representation of the ASN.1. Repetitions 1 to maxnoofEDCHMACFlows and Repetition maxnoofEDCHMACFlows+1 to maxnoofEDCHMACFlowsLCR are represented by separate ASN.1 structures with different criticality.

Range bound
Explanation
maxNrOfCommonMACFlowsLCR
Maximum number of Common MAC Flows
maxNrOfEAGCHsLCR
Maximum number of E-AGCHs in a Cell
maxNrOfEHICHsLCR
Maximum number of E-HICHs in a Cell

9.2.3.81	Common E-DCH MAC-d Flow Specific Information LCR
The Common E-DCH MAC-d Flow Specific Information LCR IE is used for the establishment or modity Common E-DCH MAC-d flows.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assinged Criticality
Common E-DCH MAC-d Flow Specific Information LCR

1..<maxNrOfEDCHMACdFlowsLCR>


–

>Common E-DCH MAC-d Flow ID LCR
M

9.2.3.87

–

>Maximum Number Of Retransmissions For E-DCH
O

9.2.1.81

–

>E-DCH MAC-d Flow Multiplexing List
O

9.2.1.69

–

>Common E-DCH Logical Channel information
O
1..<maxnooflogicalchannels>


–

>>Logical Channel ID
M

9.2.1.80

–

>>Maximum MAC-c PDU Size Extended
O

MAC PDU Size Extended
9.2.1.38C

–

>>Scheduling Priority Indicator
O

9.2.1.53H

–
ignore
>E-DCH HARQ Power Offset TDD
O

9.2.3.61

–

>E-DCH MAC-d Flow Retransmission Timer
O

9.2.3.61a

–


Range bound
Explanation
maxNrOfEDCHMACdFlowsLCR
Maximum number of E-DCH MAC-d Flows for 1.28Mcps TDD
maxnooflogicalchannels
Maximum number of logical channels

9.2.3.82	Enhanced UE DRX Information LCR
The Enhanced UE DRX Information LCR IE provides information for configuring the UE in Cell_FACH state to discontinuously reception for 1.28Mcps TDD. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
T321
M

ENUMERATED (100, 200,  400, 800,…)
Determines the time the UE waits until initiating DRX operation, in ms.
HS-DSCH DRX cycleFACH
M

ENUMERATED (4, 8, 16, 32,…)
Determines the length of the DRX Cycle during DRX operation, in frames
HS-DSCH Rx burstFACH
M

ENUMERATED (1, 2, 4, 8, 16,…)
Determines the period within the DRX Cycle that the UE continuously receives HS-DSCH, in frames

9.2.3.83	Common E-PUCH Information LCR
The Common E-PUCH Information LCR IE provides parameters to configure the E-PUCH physical channel for 1.28Mcps TDD. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Minimum code rate
M

INTEGER (0..63)

Unit: -
Range: 0.055 ..1
Step: 0.015 
Maximum code rate
M

INTEGER (0..63)

Unit: -
Range: 0.055 ..1
Step: 0.015 
HARQ Info for E-DCH
M

ENUMERATED (rv0, rvtable)

 “rv0”  indicates that  the UE will only use E_DCH RV index 0.
“rvtable” indicates that  the UE will use an RSN based RV index as specified in TS 25.212 [8]
PRXdes_base per UARFCN

0..<maxFrequencyinCell>


>PRXdes_base
M

INTEGER 
(-112..-50)
dBm. Reference Desired RX power level for E-PUCH.
Reference to Pe-base in TS 25.224 [21] 
>UARFCN
O

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
Applicable for 1.28Mcps TDD when using multiple frequencies.
E-PUCH TPC Step Size 
O

TDD TPC UL Step Size
9.2.3.21a

E-AGCH TPC Step Size
O

TDD TPC DL Step Size
9.2.3.21

E-PUCH Power Control GAP
O

INTEGER (1..255)
Unit: Number of subframes.
Reference to E-PUCH Power Control for 1.28Mcps TDD in TS 25.224 [21]. If it is not present, UE shall deem it to be infinite in which case closed loop power control shall always be used.

Range bound
Explanation
maxFrequencyinCell
Maximum number of Frequencies that can be defined in a Cell

9.2.3.84	Common E-RNTI Information LCR
The Common E-RNTI Information LCR IE provides parameters to configure the common E-RNTI used in enhanced CELL_FACH and Idle mode. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Common E-RNTI Information LCR

1..<maxnrofERUCCHsLCR>


–

>Starting E-RNTI
M

E-RNTI
9.2.1.75

–

>Number of group
M

INTEGER (1..32)

–

>Number of E-RNTI per group
M

INTEGER (1..7)
Values 3 to 7 shall not be used.
–

>Associated Phsical Channel ID
O

Common Physical Channel ID 
9.2.1.13

YES
reject

Range bound
Explanation
maxnrofERUCCHsLCR
Maximum number of E-RUCCH that can be defined in a Cell

9.2.3.85	Paging MAC Flows To Delete LCR
The Paging MAC Flows To Delete LCR IE is used for the removal of Paging MAC flows from a Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Paging MAC Flows To Delete LCR

1..<maxNrOfPagingMACFlow>


>Paging MAC Flow ID
M

9.2.1.113


Range Bound
Explanation
maxNrOfPagingMACFlow
Maximum number of Paging MAC Flows

9.2.3.86	Common E-DCH MAC-d Flows To Delete LCR
The Common E-DCH MAC-d Flows To Delete LCR IE is used for the removal of E-DCH MAC-d flows.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Common E-DCH MAC-d Flows To Delete

1..< maxNrOfEDCHMACdFlowsLCR >


>Common E-DCH MAC-d Flow ID LCR
M

9.2.3.87


Range Bound
Explanation
maxNrOfEDCHMACdFlowsLCR
Maximum number of common E-DCH MAC-d flows

9.2.3.87	Common E-DCH MAC-d Flow ID LCR
The Common E-DCH MAC-d Flow ID LCR IE is the unique identifier for one MAC-d flow on E-DCH.
IE/Group Name
 Presence
 Range
 IE Type and Reference
Semantics Description
Common E-DCH MAC-d Flow ID LCR

 
INTEGER
(0..255)
 

9.2.3.88	HS-SCCH ID LCR
The HS-SCCH ID identifies unambiguously a HS-SCCH and its paired HS-SICH within the set of HS-SCCHs for 1.28Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS SCCH ID LCR


INTEGER (0..255)


9.2.3.89	BCCH Specific HS-DSCH RNTI Information LCR
The BCCH Specific HS-DSCH RNTI Information IE provides information for BCCH Transmission using HS-DSCH for 1.28Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
BCCH Specific HS-DSCH RNTI 
M

HS-DSCH RNTI
9.2.1.31J

HS-SCCH Power 
M

DL Power
9.2.1.21

HS-PDSCH Power
M

DL Power
9.2.1.21


9.2.3.90	MAC-es Maximum Bit Rate LCR
The MAC-es Maximum Bit Rate LCR IE indicates the maximum number of bits per second to be delivered over the air interface.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MAC-es Maximum Bit Rate LCR


INTEGER (0..256,000,000,…)
Unit: bit/s

9.2.3.91	Semi-Persistent scheduling Capability LCR
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Semi-Persistent scheduling Capability LCR


ENUMERATED (Semi-Persistent scheduling Capable,  Semi-Persistent scheduling Non-Capable)


9.2.3.92	Continuous Packet Connectivity DRX Capability LCR
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Continuous Packet Connectivity DRX Capability LCR


ENUMERATED (Continuous Packet Connectivity DRX Capable, Continuous Packet Connectivity DRX Non-Capable)


9.2.3.93	Continuous Packet Connectivity DRX Information LCR
The Continuous Packet Connectivity DRX Information LCR IE defines the parameters used for Continuous Packet Connectivity DRX operation for 1.28 Mcps TDD (see ref. TS 25.224 [21]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Enabling Delay
M

ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128)
Units of radio frames
-

HS-SCCH DRX Information

1


-

>UE DRX Cycle
M

ENUMERATED(1,2,4,8,16,32,64,…)
Units of subframes
-

>Inactivity Threshold for UE DRX Cycle
O

ENUMERATED(1,2,4,8,16,32,64,…)
Units of subframes
-

>UE DRX Offset
M

INTEGER (0..63)
Units of subframes. Offset of the UE DRX cycles at the given TTI
-

>Inactivity Threshold for UE DRX Cycle Ext
O

ENUMERATED(128,256,512,…)
Units of subframes
YES
ignore
E-AGCH DRX Information

0..1


-

CHOICE E-AGCH DRX information type
M



-

>Same as HS-SCCH


NULL
Indicate the E-AGCH DRX Cycle and Offset are the same as the HS-SCCH DRX Cycle and Offset, and the E-AGCH Inactivity Monitor Threshold is absent
-

>E-AGCH DRX parameters




-

>>E-AGCH DRX cycle 
M

Enumerated (1,2,4,8,16,32,64)
Units of subframes.
-

>>E-AGCH Inactivity Monitor Threshold
O

Enumerated (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, infinity,…) 
Units of subframes.
-

>>E-AGCH DRX Offset
M

Integer (0.. 63)
Units of subframes. Offset of the E-AGCH DRX cycles.
-

  Enabling Delay Ext
O

Enumerated (infinity,…)

Yes
ignore

9.2.3.94	Continuous Packet Connectivity DRX Information To Modify LCR
The Continuous Packet Connectivity DRX Information To Modify LCR IE is used for modification of Continuous Packet Connectivity DRX information in a Node B Communication Context. The Continuous Packet Connectivity DRX Information To Modify LCR  IE shall include at least one of the following IE.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Enabling Delay
O

ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128)
Units of radio frames
-

CHOICE DRX Information To Modify
O



-

>Modify




-

>>HS-SCCH DRX-Information

0..1


-

>>>UE DRX Cycle
M

ENUMERATED (1,2,4,8,16,32,64,...)
Units of subframes
-

>>>Inactivity Threshold for UE DRX Cycle
O

ENUMERATED (1,2,4,8,16,32,64,...)
Units of subframes
-

>>>UE DRX Offset
M

INTEGER (0..63)
Units of subframes. Offset of the UE DRX cycles at the given TTI.
-

>>>Inactivity Threshold for UE DRX Cycle Ext
O

ENUMERATED (128,256,512,…)
Units of subframes
YES
ignore
>>E-AGCH DRX Information

0..1


-

>>>CHOICE E-AGCH DRX Information type
M



-

>>>>Same as HS-SCCH


NULL
Indicate the E-AGCH DRX Cycle and Offset are the same as the HS-SCCH DRX Cycle and Offset, and the E-AGCH Inactivity Monitor Threshold is absent.
-

>>>>E-AGCH DRX parameters




-

>>>>>E-AGCH DRX cycle
M

ENUMERATED (1,2,4,8,16,32,64)
Units of subframes
-

>>>>>E-AGCH Inactivity Monitor Threshold
O

ENUMERATED (0,1,2,4,8,16,32,64,128,256,512,infinity,...)
Units of subframes
-

>>>>>E-AGCH DRX Offset
M

INTEGER (0..63)
Units of subframes. Offset of the E-AGCH DRX cycles.
-

>Deactivate


NULL

-

Enabling Delay Ext
O

ENUMERATED (infinity,...)

YES
ignore

9.2.3.95	Continuous Packet Connectivity DRX Information Response LCR
Node B uses the Continuous Packet Connectivity DRX Information Response LCR IE to inform the CRNC the parameters used for Continuous Packet Connectivity DRX operation for 1.28 Mcps TDD (see ref. TS 25.224 [21]). Continuous Packet Connectivity DRX related parameters shall be configured by the CRNC. For the parameters which can be accepted by Node B, the Node B shall not included the related IEs in the Continuous Packet Connectivity DRX Information Response LCR IE. For the parameters which can be not accepted by Node B, the Node B shall included the related IEs in the Continuous Packet Connectivity DRX Information Response LCR IE.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Enabling Delay
O

ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128)
Units of radio frames
-

HS-SCCH DRX Information

0..1


-

>UE DRX Cycle
O

ENUMERATED(1,2,4,8,16,32,64,…)
Units of subframes
-

>Inactivity Threshold for UE DRX Cycle
O

ENUMERATED(1,2,4,8,16,32,64,…)
Units of subframes
-

>UE DRX Offset
O

INTEGER (0..63)
Units of subframes. Offset of the UE DRX cycles at the given TTI
-

>Inactivity Threshold for UE DRX Cycle Ext
O

ENUMERATED (128,256,512,…)
Units of subframes
YES
ignore
E-AGCH DRX Information

0..1


-

CHOICE E-AGCH DRX information type
M



-

>Same as HS-SCCH


NULL
Indicate the E-AGCH DRX Cycle and Offset are the same as the HS-SCCH DRX Cycle and Offset, and the E-AGCH Inactivity Monitor Threshold is absent
-

>E-AGCH DRX parameters




-

>>E-AGCH DRX cycle 
O

Enumerated (1,2,4,8,16,32,64,…)
Units of subframes.
-

>>E-AGCH Inactivity Monitor Threshold
O

Enumerated (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, infinity,…)
Units of subframes.
-

>>E-AGCH DRX Offset
O

Integer (0.. 63)
Units of subframes. Offset of the E-AGCH DRX cycles.
-

Enabling Delay Ext
O

Enumerated (infinity,…)
This IE can only be used when the Enabling Delay Ext is included in the request message, otherwise, the IE shall not be used.
Yes
ignore

9.2.3.96	HS-DSCH Semi-Persistent scheduling Information LCR
The HS-DSCH Semi-Persistent scheduling Information LCR IE defines the parameters used for HS-DSCH semi-Persistent scheduling for 1.28 Mcps TDD (see ref. TS 25.224 [21]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Transport Block Size List

1..< maxNoOfTBSs-Mapping-HS-DSCH-SPS >


>Transport Block Size maping Index
M

INTEGER (0.. maxNoOfTBSs-Mapping-HS-DSCH-SPS-1)
Corresponds to the Transport-block size information field carried on HS-SCCH (see ref TS 25.222 [34]).
>Transport Block Size Index
M

INTEGER (1.. maxNoOfHS-DSCH-TBSsLCR)
Corresponds to the TB index in the related Transport Block Size table (see ref TS 25.321 [32]).
Repetition Period list

1..<maxNoOfRepetition-Period-LCR>


>Repetition Period Index
M

INTEGER (0.. maxNoOfRepetition-Period-LCR-1)
Corresponds to the Resource repetition period index field carried on HS-SCCH (see ref TS 25.222 [34]).
>Repetition Period
M

ENUMERATED 
(1, 2, 4, 8, 16, 32, 64,…)
Units of subframes
>Repetition Length
O

INTEGER 
(1..63)
Absence means Repetition Length equal to 1.
HS-DSCH Semi-Persistent Resource Reservation Indicator
O

ENUMERATED(Reserve)
Reserve means the HS-DSCH Semi-Persistent Resource is required to be reserved and be informed via response message.
HS-DSCH Semi-Persistent scheduling operation Indicator

1


 >CHOICE configuration 




  >>Logical Channel level


BIT STRING (SIZE(16))
Available when MAC-ehs is configured.
Indicates the logical channels for which the HS-DSCH Semi-Persistent operation is intended to be uses .
  >> Priority Queue level


BIT STRING (SIZE(8))
Indicates the Priority Queues for which the HS-DSCH Semi-Persistent operation is intended to be used.

Range Bound
Explanation
maxNoOfHS-DSCH-TBSsLCR
Maximum number of HS-DSCH Transport Block Sizes
maxNoOfRepetition-Period-LCR
Maximum number of Repetition Period for 1.28Mcps TDD
maxNoOfTBSs-Mapping-HS-DSCH-SPS
Maximum number of Transport Block Size mapping index on HS-SCCH.

9.2.3.96a	HS-DSCH Semi-Persistent scheduling Information to modify LCR
The HS-PSCH Semi-Persistent scheduling Information to modify LCR IE is used for the modification of HS-DSCH Semi-Persistent scheduling information for 1.28 Mcps TDD (see ref. TS 25.224 [21]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Transport Block Size List

0..< maxNoOfTBSs-Mapping-HS-DSCH-SPS >


-

> Transport Block Size maping Index
M

INTEGER (0.. maxNoOfTBSs-Mapping-HS-DSCH-SPS-1)
Corresponds to the Transport-block size information field carried on HS-SCCH (see ref TS 25.222 [34]).
-

>Transport Block Size Index
M

INTEGER (1.. maxNoOfHS-DSCH-TBSsLCR)
Corresponds to the TB index in the related Transport Block Size table (see ref TS 25.321 [32]).
-

Repetition Period list

0..<maxNoOfRepetition-Period-LCR>


-

>Repetition Period Index
M

INTEGER (0.. maxNoOfRepetition-Period-LCR)
Corresponds to the Resource repetition period index field carried on HS-SCCH (see ref TS 25.222 [34]).
-

>Repetition Period
M

ENUMERATED 
(1, 2, 4, 8, 16, 32, 64,…)
Units of subframes
-

>Repetition Length
O

INTEGER 
(1..63)
Absence means Repetition Length equal to 1.
-

HS-DSCH Semi-Persistent Resource Reservation Indicator
O

ENUMERATED(Reserve)
Reserve means the Semi-Persistent HS-DSCH Resource is required to be reserved and be informed via response message.
YES
ignore
HS-DSCH Semi-Persistent scheduling operation Indicator

0..1


YES
reject
>CHOICE configuration 






    >>Logical Channel level


BIT STRING (SIZE(16))
Available when MAC-ehs is configured.
Indicates the logical channels for which the HS-DSCH Semi-Persistent operation is intended to be used.


    >> Priority Queue level


BIT STRING (SIZE(8))
Indicates the Priority Queues for which the HS-DSCH Semi-Persistent operation is intended to be used.



Range Bound
Explanation
maxNoOfHS-DSCH-TBSsLCR
Maximum number of HS-DSCH Transport Block Sizes
maxNoOfRepetition-Period-LCR
Maximum number of Repetition Period for 1.28Mcps TDD
maxNoOfTBSs-Mapping-HS-DSCH-SPS
Maximum number of Transport Block Size mapping index on HS-SCCH.

9.2.3.97	E-DCH Semi-Persistent scheduling Information LCR
The E-DCH Semi-Persistent scheduling Information LCR IE defines the parameters used for E-DCH semi-Persistent scheduling for 1.28 Mcps TDD (see ref. TS 25.224 [21]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Repetition Period list

1..<maxNoOfRepetition-Period-LCR>


-

>Repetition Period Index
M

INTEGER (0.. maxNoOfRepetition-Period-LCR-1)

-

>Repetition Period
M

ENUMERATED 
(1, 2, 4, 8, 16, 32, 64,…)
Units of subframes
-

>Repetition Length
O

INTEGER 
(1..63)
Absence means Repetition Length equal to 1.
-

E-DCH Semi-Persistent scheduling Indicator
M

BIT STRING (SIZE(16))
Indicates the logical channels for which the E-DCH Semi-Persistent operation is intended to be used.
-

Semi-Persistent E-DCH releted E-HICH Information

1


-

>E-HICH ID TDD
M

9.2.3.51a
If the Extended E-HICH ID TDD IE is included in the E-HICH Information IE, the E-HICH ID TDD IE shall be ignored.
-

>Signature Sequence Group Index
M

INTEGER (0..19)

-

>Extended E-HICH ID TDD
O

9.2.3.51b
The Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31.
-

E-DCH Semi-Persistent Resource Reservation Indicator
O

ENUMERATED(Reserve)
Reserve means the E-DCH Semi-Persistent Resource is required to be reserved and be informed via response message.
YES
ignore

Range Bound
Explanation
maxNoOfRepetition-Period-LCR
Maximum number of Repetition Period for 1.28Mcps TDD

9.2.3.97a	E-DCH Semi-Persistent scheduling Information to modify LCR
The E-DCH Semi-Persistent scheduling Information to modify LCR IE is used for the modification of E-DCH Semi-Persistent scheduling information for 1.28 Mcps TDD (see ref. TS 25.224 [21]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Repetition Period list

0..<maxNoOfRepetition-Period-LCR>


-

>Repetition Period Index
M

INTEGER (0.. maxNoOfRepetition-Period-LCR-1)

-

>Repetition Period
M

ENUMERATED 
(1, 2, 4, 8, 16, 32, 64,…)
Units of subframes
-

>Repetition Length
O

INTEGER 
(1..63)
Absence means Repetition Length equal to 1.
-

E-DCH Semi-Persistent scheduling Indicator
O

BIT STRING (SIZE(16))
Indicates the logical channels for which the E-DCH Semi-Persistent operation is intended to be used.
-

Semi-Persistent E-DCH releted E-HICH Information

0..1


-

>E-HICH ID TDD
M

9.2.3.51a
If the Extended E-HICH ID TDD IE is included in the E-HICH Information IE, the E-HICH ID TDD IE shall be ignored.
-

>Signature Sequence Group Index
M

INTEGER (0..19)

-

>Extended E-HICH ID TDD
O

9.2.3.51b
The Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31.
-

E-DCH Semi-Persistent Resource Reservation Indicator
O

ENUMERATED(Reserve)
Reserve means the E-DCH Semi-Persistent Resource is required to be reserved and be informed via response message.
YES
ignore

Range Bound
Explanation
maxNoOfRepetition-Period-LCR
Maximum number of Repetition Period for 1.28Mcps TDD

9.2.3.98	HS-DSCH Semi-Persistent scheduling Information Response LCR
The HS-DSCH Semi-Persistent scheduling Information Response LCR IE provides information for HS-DSCH Semi-Persistent scheduling determined within the Node B (see ref. TS 25.224 [21]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
HS-SICH information for HS-DSCH Semi-Persistent Scheduling operation

1..< maxNoOf-HS-SICH-SPS>


-

 >HS-SICH mapping index
M

INTEGER (0.. maxNoOf-HS-SICH-SPS-1)

-

 >CHIOCE HS-SICH type




-

  >>HS-SCCH associated HS-SICH




-

   >>>HS-SICH ID
M

9.2.3.5Gb
If the Extended HS-SICH ID IE is included in the HS-SICH Information LCR IE, the HS-SICH ID IE shall be ignored.
-

   >>>Extended HS-SICH ID
O

9.2.3.5K
The Extended HS-SICH ID IE shall be used if the HS-SICH identity has a value larger than 31.
-

  >>Non-HS-SCCH associated HS-SICH




-

   >>>Non-HS-SCCH associated HS-SICH ID
M

INTEGER (0..255)

-

Allocated HS-PDSCH Semi-persistent resource

0..1


-

 > Repetition Period Index
M

INTEGER (0.. maxNoOfRepetition-Period-LCR-1)

-

 >Repetition Length for HS-PDSCH Semi-persistent Resouce
O

INTEGER 
(1..63)
The IE is not used.
-

 >HS-PDSCH offset
M

INTEGER 
(0..63)
Units of subframes
-

 >Timeslot Resource Related Information
M

BIT STRING (SIZE(5))
Each bit indicates availability of a timeslot, where the bit 0 corresponds to TS2, the bit 1 is TS3, the bit 3 is TS4… bit 5 corresponds to TS6. 
The value 1 of a bit indicates that the corresponding timeslot is available. 
Bit 0 is the first/leftmost bit of the bit string.
-

 >Start Code
M

TDD Channelisation Code 9.2.3.19

-

 >End Code
M

TDD Channelisation Code 9.2.3.19

-

 >Transport Block Size Index
M

INTEGER (0.. maxNoOfTBSs-Mapping-HS-DSCH-SPS-1)

-

 >Modulation type
M

ENUMERATED 
(QPSK, 16QAM)

-

 >HS-SICH mapping index
M

INTEGER (0.. maxNoOf-HS-SICH-SPS-1)

-

 >HS-PDSCH Midamble Configuation
O

Midamble Shift LCR 9.2.3.7A

YES
reject
 Buffer Size for HS-DSCH Semi-Persistent scheduling
O

ENUMERATED (800..304000,…)
Indicats the buffer size that shall be reserved for HS-DSCH semi-persistent scheduling operation.

800 .. 16000 by step of 800, 17600 .. 32000 by step of 1600, 36000 .. 80000 by step of 4000, 88000 .. 160000 by step of 8000, 176000 .. 304000 by step of 16000
-

 Number of Processes for HS-DSCH Semi-Persistent scheduling
O

INTEGER (1..16)

-


Range Bound
Explanation
maxNoOf-HS-SICH-SPS
Maximum number of HS-SICH for HS-DSCH Semi-Persistent scheduling operation
maxNoOfTBSs-Mapping-HS-DSCH-SPS
Maximum number of Transport Block Size mapping index on HS-SCCH.

9.2.3.99	E-DCH Semi-Persistent scheduling Information Response LCR
The E-DCH Semi-Persistent scheduling Information Response LCR IE provides information for E-DCH Semi-Persistent scheduling information determined within the Node B (see ref. TS 25.224 [21]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Allcoated E-DCH Semi-persistent resource

1





>Timeslot Resource Related Information LCR
M

9.2.3.54a



>Power Resource Related Information
M

9.2.3.55



 >Repetition Length
M

INTEGER 
(1..63))
The IE shall be ignored.


 >Subframe Number
M

ENUMERATED (
0,1)
Used to indicate from which subframe of the Radio Frame indicated by TDD E-PUCH Offset IE the physical resources are assigned to the E-DCH Non-scheduled Grant.


 >TDD E-PUCH Offset
M

9.2.3.56



 >TDD Channelisation Code
M

9.2.3.19



 >NE-UCCH
M

INTEGER (1..8)
Number of E-UCCH and TPC instances within an E-DCH TTI. Details are described in TS 25.221 [19] . 


>Repetition Period Index
O

INTEGER (0.. maxNoOfRepetition-Period-LCR-1)

YES
reject

9.2.3.100	HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR
The HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR IE is used to deactivate HS-DSCH Semi-Persistent scheduling operation for 1.28 Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
HS-DSCH Semi-Persistent scheduling Deactivate Indicator
M

NULL


9.2.3.101	E-DCH Semi-Persistent scheduling Deactivate Indicator LCR
The E-DCH Semi-Persistent scheduling Deactivate Indicator LCR IE is used to deactivate E-DCH Semi-Persistent schedulung operation for 1.28 Mcps TDD.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
E-DCH Semi-Persistent scheduling Deactivate Indicator
M

NULL


9.2.3.102	Idle Interval Information
The Idle Interval Information IE indicates the idle interval used for E-UTRAN measurements by a multi-RAT UE in CELL_DCH state. Ref TS 36.133 [50].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
K
M

INTEGER (0,2,3)
The actual idle interval period = 2^k.
Value "0" means to delete the configuration related to E-UTRAN measurement 
Offset
M

INTEGER (0..7)
The idle interval position in the period.
The IE shall be ignored when the value of the K IE is set to “0”

9.2.3.103	HS-SICH Reference Signal Information
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Midamble Configuration LCR
M

ENUMERATED (2, 4, 6, 8, 10, 12, 14, 16, ...)
As defined in TS 25.221 [19]


Midamble Shift
M

INTEGER (0..15)



Time Slot LCR
M

9.2.3.24A




9.2.3.104	UE Selected MBMS Service Information
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
CHOICE Status
O





>None


NULL



>Some






>>Selected MBMS Service List

1..<MaxMBMSServiceSelect>




>>>Selected MBMS Service Time Slot Information LCR
M
0..7

This IE indicates the Time Slot information of UE selected MBMS service in the other frequency. For 1.28Mcps TDD only. Mandatory  if the IE UE Selected MBMS Service Action set to Selected. Otherwise optional.
–

>>>>Time Slot LCR
M

9.2.3.24A

–

>>>MBMS Service TDM Information

0..1

Indicating the MBMS service TDM Information


>>>> Transmission Time Interval
M

ENUMERATED 
(10, 20, 40, 80,…)
Unit: ms


>>>>TDM_Rep
M

Integer (2..9)



>>>>TDM_Offset
M

Integer (0..8)



>>>>TDM_Length
M

Integer (1..8)




9.2.3.105	Best Cell Portions LCR
Best Cell Portions LCR  IE indicates the best received cell portions and their RSCP values when Cell Portions are defined in the cell for 1.28 Mcps TDD..
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Best Cell Portions LCR

1..<maxNrOfCellPortionsPerCellLCR>


>Cell Portion LCR ID
M

9.2.3.107

>RSCP Value
M

INTEGER (0..127)
According to mapping in TS 25.123 [23]

Range Bound
Explanation
maxNrOfCellPortionsPerCellLCR
Maximum number of reported Best Received Cell Portions for 1.28 Mcps TDD

9.2.3.106	Cell Portion Capability LCR
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Cell Portion Capability LCR


ENUMERATED (Cell Portion Capable, Cell Portion Non-Capable)


9.2.3.107	Cell Portion LCR ID
Cell Portion LCR ID is the unique identifier for a cell portion within a cell for 1.28 Mcps TDD. See TS 25.225 [5].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Cell Portion LCR ID


INTEGER (0..255,…)


9.2.3.108	Number Of Reported Cell Portions LCR
Number of Reported Cell Portions LCR indicates the number of Best Cell Portions values which shall be included in the measurement report.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Number Of Reported Cell Portions LCR


INTEGER (1..256,…)


9.2.3.109	TS0 Capability LCR
The parameter defines the TS0 capability for a Local Cell. The TS0 Capable indicates that the HS-PDSCH can be configured in TS0 in the Local Cell.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
TS0 Capability LCR


ENUMERATED (TS0 Capable, TS0 Non-Capable)


9.2.3.110	UE TS0 Capability LCR
The UE TS0 Capability LCR IE defines the UE TS0 enhancement capability, see ref TS 25.306 [33].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UE TS0 Capability LCR


ENUMERATED (UE TS0 Capable, UE TS0 Non-Capable)


9.2.3.111	DCH Measurement Occasion Information
The DCH Measurement Occasion Information IE indicates Measurement Occasion Information used for inter-frequency/inter-RAT measurements in CELL_DCH state for 1.28Mcps TDD. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CELL_DCH measurement occasion pattern sequence

1 to <maxNrOfDCHMeasurementOccasionPatternSequence>


>Pattern sequence identifier
M

INTEGER(1.. maxNrOfDCHMeasurementOccasionPatternSequence)
If an already defined pattern sequence is not present, references to the already defined pattern.
>Status Flag
M

ENUMERATED(activate, deactivate)
This flag indicates whether the measurement occasion pattern sequence shall be activated or deactivated.
>Measurement occasion pattern sequence parameters

0..1


>>k
M

INTEGER(1..9)
CELL_DCH measurement occasion cycle length coefficient. The actual measurement occasion period equal to 2k radio frames. Value 0 indicates continuous allocation.
>>Offset
M

INTEGER(0..511)
In frames. The measurement occasion position in the measurement period.
>>M_Length
M

INTEGER(1..512)
The measurement occasion length in frames starting from the Offset.
>>Timeslot Bitmap
M

BIT STRING (SIZE(7))
Bitmap indicating which of the timeslot(s) is/are allocated for measurement. 
Bit 0 is for timeslot 0. Bit 1 is for timeslot 1. Bit 2 is for timeslot 2. Bit 3 is for timeslot 3. Bit 4 is for timeslot 4. Bit 5 is for timeslot 5. Bit 6 is for timeslot 6.
The value 0 of a bit means the corresponding timeslot is not used for measurement. The value 1 of a bit means the corresponding timeslot is used for measurement.
Bit 0 is the first/leftmost bit of the bit string.

Range Bound
Explanation
maxNrOfDCHMeasurementOccasionPatternSequence
Maximum number of measurement occasion pattern sequence

9.2.3.112	Multi-Carrier E-DCH Information LCR
The Multi-Carrier E-DCH Information LCR IE defines the parameters used for Multi-Carrier E-DCH operation for 1.28 Mcps TDD (see ref. TS 25.224 [21]).
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Multi-Carrier E-DCH Information

1..<maxNrOfULCarriersLCR-1>


>UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
>SNPL Carrier Group Indicator
O

INTEGER 
(1..3)
Indicates to which SNPL carrier Group this frequency belongs. The absence of this IE indicates the corresponding frequency belongs to a separate SNPL carrier group which only contains this carrier. The SNPL carrier Group is defined in TS 25.331 [18].
>PRXdes_base
M

INTEGER 
(-112..-50)
dBm. Reference Desired RX power level for E-PUCH.
Reference to Pe-base in TS 25.224 [21]
>Multi-Carrier E-DCH TDD MAC-d Flow Specific Information

0..<maxNrOfEDCHMACdFlows>

Shall be ignored if bearer establishment with ALCAP.

Shall be present only if the Separate Iub transport bearer mode is used.
>>E-DCH MAC-d Flow ID
M

9.2.1.74

>>Binding ID
M

9.2.1.4

>>Transport Layer Address
M

9.2.1.63


Range Bound
Explanation
maxNrOfULCarriersLCR
Maximum number of uplink frequencis in Multi-Carrier E-DCH Operation
maxNrOfEDCHMACdFlows
Maximum number of MAC-d flows.

9.2.3.113	Multi-Carrier E-DCH Transport Bearer Mode LCR
 This parameter indicates the Multi-Carrier E-DCH Transport Bearer Mode. For Mult-icarrier E-DCH Transport Bearer Mode LCR = "Separate Iub transport bearer mode", the Mac-d flows from each carrier uses different Iub transport bearers. For Multi-carrier E-DCH Transport Bearer Mode LCR = "E-DCH UL flow multiplexing mode", one Mac-d flow received on the different carriers in the Node B is multiplexed on one Iub transport bearer.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Multi-Carrier E-DCH Transport Bearer Mode


ENUMERATED (Separate Iub transport bearer mode,E-DCH UL flow multiplexing mode,…)


9.2.3.114	Multi-Carrier E-DCH Information Response LCR
The Multi-Carrier E-DCH Information Response LCR IE provides information for E-DCH MAC-d flows that determined within the Node B. It also provides additional E-DCH information determined within the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Multi-Carrier E-DCH Information Response

1..<maxNrOfULCarriersLCR-1>


>UARFCN
M

9.2.1.65
Corresponds to Nt (TS 25.105 [15]).
>E-DCH TDD MAC-d Flow Specific Information Response

0..<maxNrOfEDCHMACdFlows>


>>E-DCH MAC-d Flow ID
M

9.2.1.74

>>Binding ID
O

9.2.1.4

>>Transport Layer Address
O

9.2.1.63

>E-AGCH Specific Information Response TDD

0..<maxNrOfEAGCHCodes> 


>>E-AGCH ID TDD
M

9.2.3.51

>Scheduled E-HICH Specific Information Response 1.28Mcps TDD 

0..<maxNrOfEHICHCodes>


>>EI
M

INTEGER (0..3)
E-HICH indication which is used to indicate UE on which E-HICH the feedback info is carried.
>>E-HICH ID TDD
O

9.2.3.51a
If the Extended E-HICH ID TDD IE is included in the E-HICH Information IE, the E-HICH ID TDD IE shall be ignored
>>Extended E-HICH ID TDD
O

9.2.3.51b
Applicable to 1.28Mcps TDD only, the Extended E-HICH ID TDD IE shall be used if the E-HICH identity has a value larger than 31.

Range bound
Explanation
maxNrOfULCarriersLCR
Maximum number of uplink frequencis in Multi-Carrier E-DCH Operation
maxNrOfEDCHMACdFlows
Maximum number of MAC-d flows.
maxNrOfEAGCHCodes
Maximum number of E-AGCHs assigned to one UE
maxNrOfEHICHCodes
Maximum number of E-HICHs assigned to one UE

9.2.3.115	Cell Capability Container TDD LCR
The Cell Capability Container TDD LCR IE indicates the cell capability of Multi-Carrier related functions by setting the corresponding bit in the BIT String.. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Cell Capability Container TDD LCR


BIT STRING (SIZE(8))
Each bit indicates whether a cell supports a particular functionality or not. The value 1 of a bit indicates that the corresponding functionality is supported in a cell and value 0 indicates that the corresponding functionality is not supported in a cell. Each bit is defined as follows.
The first bit: Multi-Carrier E-DCH Operation Support Indicator. This bit shall be ignored by the SRNC if the second bit: Separate Iub Transport Bearer Support Indicator = “0” and the third bit: E-DCH UL Flow Multiplexing Support Indicator = “0”.
The second bit: Separate Iub Transport Bearer Support Indicator, /Multi-carrier/.
This bit shall be ignored by the SRNC if the first bit: Multi-Carrier E-DCH Operation Support Indicator = “0”.
The third bit: E-DCH UL Flow Multiplexing Support Indicator, /Multi-carrier/.
This bit shall be ignored by the SRNC if the first bit: Multi-Carrier E-DCH Operation Support Indicator = “0”.

Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver. Note that Reserved bits are not considered as a spare bit. They shall however be set to 0 by the transmitter and shall be ignored by the receiver.

9.2.3.116	MU-MIMO Information
The MU-MIMO Information IE defines the parameters used for MU-MIMO operation for 1.28 Mcps TDD (see ref. TS 25.224 [21]). 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MU-MIMO Indicator
M

9.2.3.120

Standalone Midamble Channel Information request
O

ENUMERATED (stand-alone-Midamble-Resource-Requested, stand-alone-Midamble-Resource-not-Requested)

Standalone Midamble Channel Information

0..1


>Standalone Midamble Configuration
M

ENUMERATED (2,4,6,8,10,12,14,16, ...)
As defined in TS 25.221 [19]
>Standalone Midamble Shift
M

INTEGER (0..15)

>Timeslot
M

9.2.3.24A

>Repetition Period
M

ENUMERATED (1, 2, 4, 8, 16, 32, 64, ...)
Units of subframes. 
>Offset
M

INTEGER (0..63)
Units of subframes. 
>Reference Beta
C-E-DCH

INTEGER (-15..16)
Unit range -15db to +16db


Condition
Explanation
E-DCH
This IE shall be present if IE "E-DCH Information 1.28Mcps" is present, i.e. the E-DCH related resource is configured. Otherwise it is not needed.

9.2.3.117	MU-MIMO Information To Reconfigure
The MU-MIMO Information To Reconfigure IE is used for reconfiguration of MU-MIMO Information in a Node B Communication Context.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
CHOICE MU-MIMO Information To reconf
M



>Modify




>>MU-MIMO Indicator
O

9.2.3.120

>>Standalone Midamble Configuration
O

ENUMERATED (2, 4, 6, 8, 10, 12, 14, 16, ...)
As defined in TS 25.221 [19]
>>Standalone Midamble Shift
O

INTEGER (0..15)

>>Timeslot
O

9.2.3.24A

>>Repetition Period
O

ENUMERATED (1, 2,4, 8, 16, 32, 64, ...)
Units of Subframes
>>Offset
O

INTEGER (0..63)
Units of Subframes
>>Reference Beta
O

INTEGER (-15..16)
Unit range -15db to +16db
>continue


NULL


9.2.3.118	MU-MIMO Information Response
The MU-MIMO Information Response IE indicates if the Node B is using MU-MIMO or not. It also provides Standalone Midamble Channel Information determined within the Node B.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MU-MIMO Usage Indicator
M

9.2.3.121

Standalone Midamble Channel Information

0..1


>Standalone Midamble Configuration
M

ENUMERATED (2, 4, 6, 8, 10, 12, 14, 16, ...)
As defined in TS 25.221 [19]
>Standalone Midamble Shift
M

INTEGER (0..15)

>Timeslot
M

9.2.3.24A

>Repetition Period
M

ENUMERATED (1, 2,4, 8, 16, 32,64)
Units of subframes. 
>Offset
M

INTEGER (0..63)
Units of subframes. 
>Reference Beta
C-E-DCH

INTEGER (-15..16)
Unit range -15db to +16db

Condition
Explanation
E-DCH
This IE shall be present if IE "E-DCH Information 1.28Mcps" is present, i.e. the E-DCH related resource is configured. Otherwise it is not needed.

9.2.3.119	MU-MIMO Capability Container
The MU-MIMO Capability Container IE indicates the MU-MIMO related capabilities by setting the corresponding bit in the BIT String.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MU-MIMO Capability Container


BIT STRING (SIZE(8))
Each bit indicates whether a cell supports a particular functionality or not. The value 1 of a bit indicates that the corresponding functionality is supported in a cell and value 0 indicates that the corresponding functionality is not supported in a cell. Each bit is defined as follows.
The first bit: DL MU-MIMO Capability.
The second bit: UL MU-MIMO Capability.
The third bit: Standalone Midamble Capability.

Note that Reserved bits are not considered as a spare bit. They shall however be set to 0 by the transmitter and shall be ignored by the receiver.

9.2.3.120	MU-MIMO Indicator
The MU-MIMO Indicator IE indicates directions for MU-MIMO operation for 1.28 Mcps TDD. 
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MU-MIMO Indicator
M

ENUMERATED (UL Only, DL Only, UL and DL, ...)


9.2.3.121	MU-MIMO Usage Indicator
The MU-MIMO Usage Indicator IE indicates if the Node B is using MU-MIMO or not.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
MU-MIMO Usage Indicator
M

ENUMERATED (MU-MIMO-Used, MU-MIMO-Not-Used, ...)


9.2.3.122	Adaptive Special Burst Power Capability LCR
This parameter defines whether the Node B supports Adaptive Special Burst Power.
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Adaptive Special Burst Power Capability LCR


ENUMERATED (Adaptive Special Burst Power Capable, Adaptive Special Burst Power non Capable)


9.2.3.123	In Sync Indication Information LCR
The In Sync Indication Information LCR IE is used by RNC to inform Node B the value of N312 and T312 defined in TS 25.331 [18].
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
T312
M

Integer (0..15)
Value in seconds.
N312
M

ENUMERATED (s1, s2, s4, s10, s20, s50, s100, s200, s400, s600, s800, s1000)


9.2.3.124	AOA per Cell Portion LCR
The AOA per Cell Portion LCR IE indicates the AOA measurement in each cell portion for 1.28 Mcps TDD..
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
AOA per Cell Portion LCR

1..<MaxNrOfCellPortionsPerCellLCR>


>Cell Portion LCR ID
M

9.2.3.107

>AOA LCR
M

INTEGER (0..719)
According to mapping in TS 25.123 [23]
>AOA LCR Accuracy Class
M

ENUMERATED (
A, B, C, D, E, F, G, H,...)
According to mapping in TS 25.123 [23]

Range Bound
Explanation
MaxNrOfCellPortionsPerCellLCR
Maximum number of Cell Portions in a cell for 1.28 Mcps TDD

9.2.3.125	UE RF Band Capability LCR
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
UE RF Band Capability Info

1..< maxFreqBandsTDD>


>UE RF Band Capability
M

ENUMERATED (a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,…)
Corresponds to the radio bands definition (TS 25.105 [15]).


9.3	Message and Information Element Abstract Syntax (with ASN.1)
9.3.0	General
NBAP ASN.1 definition conforms with ITU-T Rec. X.680 [12] and ITU-T Rec. X.681 [13].
Subclause 9.3 presents the Abstract Syntax of NBAP protocol with ASN.1. In case there is contradiction between the ASN.1 definition in this subclause and the tabular format in subclauses 9.1 and 9.2, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence.
The ASN.1 definition specifies the structure and content of NBAP messages. NBAP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a NBAP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids):
-	IEs shall be ordered (in an IE container) in the order they appear in object set definitions.
-	Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements.
If a NBAP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax Error in subclause 10.3.6.
9.3.1	Usage of Private Message mechanism for non-standard use
The private message mechanism for non-standard use may be used.
-	For special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multi-vendor inter-operability.
-	By vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation.
The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised.
9.3.2	Elementary Procedure Definitions
-- **************************************************************
--
-- Elementary Procedure definitions
--
-- **************************************************************

NBAP-PDU-Descriptions {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) 
umts-Access (20) modules (3) nbap (2) version1 (1) nbap-PDU-Descriptions (0) }

DEFINITIONS AUTOMATIC TAGS ::= 

BEGIN

-- **************************************************************
--
-- IE parameter types from other modules.
--
-- **************************************************************

IMPORTS
	Criticality,
	ProcedureID,
	MessageDiscriminator,
	TransactionID
FROM NBAP-CommonDataTypes

	CommonTransportChannelSetupRequestFDD,
	CommonTransportChannelSetupRequestTDD,
	CommonTransportChannelSetupResponse,
	CommonTransportChannelSetupFailure,
	CommonTransportChannelReconfigurationRequestFDD,
	CommonTransportChannelReconfigurationRequestTDD,
	CommonTransportChannelReconfigurationResponse,
	CommonTransportChannelReconfigurationFailure,
	CommonTransportChannelDeletionRequest,
	CommonTransportChannelDeletionResponse,
	BlockResourceRequest,
	BlockResourceResponse,
	BlockResourceFailure,
	UnblockResourceIndication,
	AuditFailure,
	AuditRequiredIndication,
	AuditRequest,
	AuditResponse,
	CommonMeasurementInitiationRequest,
	CommonMeasurementInitiationResponse,
	CommonMeasurementInitiationFailure,
	CommonMeasurementReport,
	CommonMeasurementTerminationRequest,
	CommonMeasurementFailureIndication,
	CellSetupRequestFDD,
	CellSetupRequestTDD,
	CellSetupResponse,
	CellSetupFailure,
	CellReconfigurationRequestFDD,
	CellReconfigurationRequestTDD,
	CellReconfigurationResponse,
	CellReconfigurationFailure,
	CellDeletionRequest,
	CellDeletionResponse,
	InformationExchangeInitiationRequest,
	InformationExchangeInitiationResponse,
	InformationExchangeInitiationFailure,
	InformationReport,
	InformationExchangeTerminationRequest,
	InformationExchangeFailureIndication,
	BearerRearrangementIndication,
	ResourceStatusIndication,
	SystemInformationUpdateRequest,
	SystemInformationUpdateResponse,
	SystemInformationUpdateFailure,
	ResetRequest,
	ResetResponse,
	RadioLinkActivationCommandFDD,
	RadioLinkActivationCommandTDD,
	RadioLinkPreemptionRequiredIndication,
	RadioLinkSetupRequestFDD,
	RadioLinkSetupRequestTDD,
	RadioLinkSetupResponseFDD,
	RadioLinkSetupResponseTDD,
	RadioLinkSetupFailureFDD,
	RadioLinkSetupFailureTDD,
	RadioLinkAdditionRequestFDD,
	RadioLinkAdditionRequestTDD,
	RadioLinkAdditionResponseFDD,
	RadioLinkAdditionResponseTDD,
	RadioLinkAdditionFailureFDD,
	RadioLinkAdditionFailureTDD,
	RadioLinkParameterUpdateIndicationFDD,
	RadioLinkParameterUpdateIndicationTDD,
	RadioLinkReconfigurationPrepareFDD,
	RadioLinkReconfigurationPrepareTDD,
	RadioLinkReconfigurationReady,
	RadioLinkReconfigurationFailure,
	RadioLinkReconfigurationCommit,
	RadioLinkReconfigurationCancel,
	RadioLinkReconfigurationRequestFDD,
	RadioLinkReconfigurationRequestTDD,
	RadioLinkReconfigurationResponse,
	RadioLinkDeletionRequest,
	RadioLinkDeletionResponse,
	DL-PowerControlRequest,
	DL-PowerTimeslotControlRequest,
	DedicatedMeasurementInitiationRequest,
	DedicatedMeasurementInitiationResponse,
	DedicatedMeasurementInitiationFailure,
	DedicatedMeasurementReport,
	DedicatedMeasurementTerminationRequest,
	DedicatedMeasurementFailureIndication,
	RadioLinkFailureIndication,
	RadioLinkRestoreIndication,
	CompressedModeCommand,
	ErrorIndication,
	PrivateMessage,
	PhysicalSharedChannelReconfigurationRequestTDD,
	PhysicalSharedChannelReconfigurationRequestFDD,
	PhysicalSharedChannelReconfigurationResponse,
	PhysicalSharedChannelReconfigurationFailure,
	CellSynchronisationInitiationRequestTDD,
	CellSynchronisationInitiationResponseTDD,
	CellSynchronisationInitiationFailureTDD,
	CellSynchronisationReconfigurationRequestTDD,
	CellSynchronisationReconfigurationResponseTDD,
	CellSynchronisationReconfigurationFailureTDD,
	CellSynchronisationAdjustmentRequestTDD,
	CellSynchronisationAdjustmentResponseTDD,
	CellSynchronisationAdjustmentFailureTDD,
	CellSynchronisationReportTDD,
	CellSynchronisationTerminationRequestTDD,
	CellSynchronisationFailureIndicationTDD,
	MBMSNotificationUpdateCommand,
	UEStatusUpdateCommand,
	SecondaryULFrequencyReport,
	SecondaryULFrequencyUpdateIndication,
	UEStatusUpdateConfirmRequest,
	UEStatusUpdateConfirmResponse

FROM NBAP-PDU-Contents

	id-audit,
	id-auditRequired,
	id-blockResource,
	id-cellDeletion,
	id-cellReconfiguration,
	id-cellSetup,
	id-cellSynchronisationInitiation,
	id-cellSynchronisationReconfiguration,
	id-cellSynchronisationReporting,
	id-cellSynchronisationTermination,
	id-cellSynchronisationFailure,
	id-commonMeasurementFailure,
	id-commonMeasurementInitiation,
	id-commonMeasurementReport,
	id-commonMeasurementTermination,
	id-commonTransportChannelDelete,
	id-commonTransportChannelReconfigure,
	id-commonTransportChannelSetup,
	id-compressedModeCommand,
	id-dedicatedMeasurementFailure,
	id-dedicatedMeasurementInitiation,
	id-dedicatedMeasurementReport,
	id-dedicatedMeasurementTermination,
	id-downlinkPowerControl,
	id-downlinkPowerTimeslotControl,
	id-errorIndicationForDedicated,
	id-errorIndicationForCommon,
	id-informationExchangeFailure,
	id-informationExchangeInitiation,
	id-informationReporting,
	id-informationExchangeTermination,
	id-BearerRearrangement,
	id-mBMSNotificationUpdate,
	id-physicalSharedChannelReconfiguration,
	id-privateMessageForDedicated,
	id-privateMessageForCommon,
	id-radioLinkActivation,
	id-radioLinkAddition,
	id-radioLinkDeletion,
	id-radioLinkFailure,
	id-radioLinkParameterUpdate,
	id-radioLinkPreemption,
	id-radioLinkRestoration,
	id-radioLinkSetup,
	id-reset,
	id-resourceStatusIndication,
	id-cellSynchronisationAdjustment,
	id-synchronisedRadioLinkReconfigurationCancellation,
	id-synchronisedRadioLinkReconfigurationCommit,
	id-synchronisedRadioLinkReconfigurationPreparation,
	id-systemInformationUpdate,
	id-unblockResource,
	id-unSynchronisedRadioLinkReconfiguration,
	id-uEStatusUpdate,
	id-secondaryULFrequencyReporting,
	id-secondaryULFrequencyUpdate,
	id-uEStatusUpdateConfirmation

FROM NBAP-Constants;

-- **************************************************************
--
-- Interface Elementary Procedure Class
--
-- **************************************************************

NBAP-ELEMENTARY-PROCEDURE ::= CLASS {
	&InitiatingMessage					,
	&SuccessfulOutcome					OPTIONAL,
	&UnsuccessfulOutcome				OPTIONAL,
	&Outcome							OPTIONAL,
	&messageDiscriminator				MessageDiscriminator,
	&procedureID						ProcedureID 	UNIQUE,
	&criticality						Criticality 	DEFAULT ignore
}

WITH SYNTAX {
	INITIATING MESSAGE					&InitiatingMessage
	[SUCCESSFUL OUTCOME					&SuccessfulOutcome]
	[UNSUCCESSFUL OUTCOME				&UnsuccessfulOutcome]
	[OUTCOME							&Outcome]
	MESSAGE DISCRIMINATOR				&messageDiscriminator
	PROCEDURE ID						&procedureID
	[CRITICALITY						&criticality]
}

-- **************************************************************
--
-- Interface PDU Definition
--
-- **************************************************************

NBAP-PDU ::= CHOICE {
	initiatingMessage		InitiatingMessage,
	succesfulOutcome		SuccessfulOutcome,
	unsuccesfulOutcome		UnsuccessfulOutcome,
	outcome					Outcome,
	...
}

InitiatingMessage ::= SEQUENCE {
	procedureID				NBAP-ELEMENTARY-PROCEDURE.&procedureID	({NBAP-ELEMENTARY-PROCEDURES}),
	criticality				NBAP-ELEMENTARY-PROCEDURE.&criticality	({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}),
	messageDiscriminator	NBAP-ELEMENTARY-PROCEDURE.&messageDiscriminator({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}),
	transactionID 			TransactionID,
	value					NBAP-ELEMENTARY-PROCEDURE.&InitiatingMessage({NBAP-ELEMENTARY-PROCEDURES}{@procedureID})
}

SuccessfulOutcome ::= SEQUENCE {
	procedureID				NBAP-ELEMENTARY-PROCEDURE.&procedureID	({NBAP-ELEMENTARY-PROCEDURES}),
	criticality				NBAP-ELEMENTARY-PROCEDURE.&criticality	({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}),
	messageDiscriminator	NBAP-ELEMENTARY-PROCEDURE.&messageDiscriminator({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}),
 	transactionID 			TransactionID,
	value					NBAP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome({NBAP-ELEMENTARY-PROCEDURES}{@procedureID})
}

UnsuccessfulOutcome ::= SEQUENCE {
	procedureID				NBAP-ELEMENTARY-PROCEDURE.&procedureID	({NBAP-ELEMENTARY-PROCEDURES}),
	criticality				NBAP-ELEMENTARY-PROCEDURE.&criticality	({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}),
	messageDiscriminator	NBAP-ELEMENTARY-PROCEDURE.&messageDiscriminator({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}),
	transactionID 			TransactionID,
	value					NBAP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome({NBAP-ELEMENTARY-PROCEDURES}{@procedureID})
}

Outcome ::= SEQUENCE {
	procedureID				NBAP-ELEMENTARY-PROCEDURE.&procedureID	({NBAP-ELEMENTARY-PROCEDURES}),
	criticality				NBAP-ELEMENTARY-PROCEDURE.&criticality	({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}),
	messageDiscriminator	NBAP-ELEMENTARY-PROCEDURE.&messageDiscriminator({NBAP-ELEMENTARY-PROCEDURES}{@procedureID}),
	transactionID 			TransactionID,
	value					NBAP-ELEMENTARY-PROCEDURE.&Outcome	({NBAP-ELEMENTARY-PROCEDURES}{@procedureID})
}

-- **************************************************************
--
-- Interface Elementary Procedure List
--
-- **************************************************************

NBAP-ELEMENTARY-PROCEDURES NBAP-ELEMENTARY-PROCEDURE ::= {
	NBAP-ELEMENTARY-PROCEDURES-CLASS-1			|
	NBAP-ELEMENTARY-PROCEDURES-CLASS-2			,
	...
}

NBAP-ELEMENTARY-PROCEDURES-CLASS-1 NBAP-ELEMENTARY-PROCEDURE ::= {
	cellSetupFDD										|
	cellSetupTDD										|
	cellReconfigurationFDD								|
	cellReconfigurationTDD								|
	cellDeletion										|
	commonTransportChannelSetupFDD						|
	commonTransportChannelSetupTDD						|
	commonTransportChannelReconfigureFDD				|
	commonTransportChannelReconfigureTDD				|
	commonTransportChannelDelete						|
	audit												|
	blockResource										|
	radioLinkSetupFDD									|
	radioLinkSetupTDD									|
	systemInformationUpdate								|
	commonMeasurementInitiation							|
	radioLinkAdditionFDD								|
	radioLinkAdditionTDD								|
	radioLinkDeletion									|
	reset												|
	synchronisedRadioLinkReconfigurationPreparationFDD	|
	synchronisedRadioLinkReconfigurationPreparationTDD	|
	unSynchronisedRadioLinkReconfigurationFDD			|
	unSynchronisedRadioLinkReconfigurationTDD			|
	dedicatedMeasurementInitiation						|
	physicalSharedChannelReconfigurationTDD				,
	...,
	informationExchangeInitiation						|
	cellSynchronisationInitiationTDD					|
	cellSynchronisationReconfigurationTDD				|
	cellSynchronisationAdjustmentTDD					|
	physicalSharedChannelReconfigurationFDD				|
	ueStatusUpdateConfirmation	
}

NBAP-ELEMENTARY-PROCEDURES-CLASS-2 NBAP-ELEMENTARY-PROCEDURE ::= {
	resourceStatusIndication							|
	auditRequired										|
	commonMeasurementReport								|
	commonMeasurementTermination						|
	commonMeasurementFailure							|
	synchronisedRadioLinkReconfigurationCommit			|
	synchronisedRadioLinkReconfigurationCancellation	|
	radioLinkFailure									|
	radioLinkPreemption									|
	radioLinkRestoration								|
	dedicatedMeasurementReport							|
	dedicatedMeasurementTermination						|
	dedicatedMeasurementFailure							|
	downlinkPowerControlFDD								|
	downlinkPowerTimeslotControl						|
	compressedModeCommand								|
	unblockResource										|
	errorIndicationForDedicated							|
	errorIndicationForCommon							|
	privateMessageForDedicated							|
	privateMessageForCommon								,
	...,
	informationReporting								|
	informationExchangeTermination						|
	informationExchangeFailure							|
	cellSynchronisationReportingTDD						|
	cellSynchronisationTerminationTDD					|
	cellSynchronisationFailureTDD						|
	bearerRearrangement									|
	radioLinkActivationFDD								|
	radioLinkActivationTDD								|
	radioLinkParameterUpdateFDD							|
	radioLinkParameterUpdateTDD							|
	mBMSNotificationUpdate								|
	uEStatusUpdate										|
	secondaryULFrequencyReportingFDD					|
	secondaryULFrequencyUpdateFDD

}

-- **************************************************************
--
-- Interface Elementary Procedures
--
-- **************************************************************

-- Class 1

-- *** CellSetup (FDD) ***
cellSetupFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CellSetupRequestFDD
	SUCCESSFUL OUTCOME		CellSetupResponse
	UNSUCCESSFUL OUTCOME	CellSetupFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-cellSetup, ddMode fdd } 
	CRITICALITY 			reject
}

-- *** CellSetup (TDD) ***
cellSetupTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CellSetupRequestTDD
	SUCCESSFUL OUTCOME		CellSetupResponse
	UNSUCCESSFUL OUTCOME	CellSetupFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-cellSetup, ddMode tdd } 
	CRITICALITY 			reject
}

-- *** CellReconfiguration(FDD) ***
cellReconfigurationFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CellReconfigurationRequestFDD
	SUCCESSFUL OUTCOME		CellReconfigurationResponse
	UNSUCCESSFUL OUTCOME	CellReconfigurationFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-cellReconfiguration, ddMode fdd } 
	CRITICALITY 			reject
}

-- *** CellReconfiguration(TDD) ***
cellReconfigurationTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CellReconfigurationRequestTDD
	SUCCESSFUL OUTCOME		CellReconfigurationResponse
	UNSUCCESSFUL OUTCOME	CellReconfigurationFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-cellReconfiguration,	ddMode tdd } 
	CRITICALITY 			reject
}

-- *** CellDeletion ***
cellDeletion NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CellDeletionRequest
	SUCCESSFUL OUTCOME		CellDeletionResponse
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-cellDeletion, ddMode common } 
	CRITICALITY 			reject
}

-- *** CommonTransportChannelSetup (FDD) ***
commonTransportChannelSetupFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CommonTransportChannelSetupRequestFDD
	SUCCESSFUL OUTCOME		CommonTransportChannelSetupResponse
	UNSUCCESSFUL OUTCOME	CommonTransportChannelSetupFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-commonTransportChannelSetup, ddMode fdd } 
	CRITICALITY 			reject
}

-- *** CommonTransportChannelSetup (TDD) ***
commonTransportChannelSetupTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CommonTransportChannelSetupRequestTDD
	SUCCESSFUL OUTCOME		CommonTransportChannelSetupResponse
	UNSUCCESSFUL OUTCOME	CommonTransportChannelSetupFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-commonTransportChannelSetup, ddMode tdd } 
	CRITICALITY 			reject
}

-- *** CommonTransportChannelReconfigure (FDD) ***
commonTransportChannelReconfigureFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CommonTransportChannelReconfigurationRequestFDD
	SUCCESSFUL OUTCOME		CommonTransportChannelReconfigurationResponse
	UNSUCCESSFUL OUTCOME	CommonTransportChannelReconfigurationFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-commonTransportChannelReconfigure, ddMode fdd } 
	CRITICALITY 			reject
}

-- *** CommonTransportChannelReconfigure (TDD) ***
commonTransportChannelReconfigureTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CommonTransportChannelReconfigurationRequestTDD
	SUCCESSFUL OUTCOME		CommonTransportChannelReconfigurationResponse
	UNSUCCESSFUL OUTCOME	CommonTransportChannelReconfigurationFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-commonTransportChannelReconfigure, ddMode tdd } 
	CRITICALITY 			reject
}

-- *** CommonTransportChannelDelete ***
commonTransportChannelDelete NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CommonTransportChannelDeletionRequest
	SUCCESSFUL OUTCOME		CommonTransportChannelDeletionResponse
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-commonTransportChannelDelete, ddMode common } 
	CRITICALITY 			reject
}

-- *** Audit ***
audit NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		AuditRequest
	SUCCESSFUL OUTCOME		AuditResponse
	UNSUCCESSFUL OUTCOME	AuditFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-audit, ddMode common } 
	CRITICALITY 			reject
}

-- *** BlockResourceRequest ***
blockResource NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		BlockResourceRequest
	SUCCESSFUL OUTCOME		BlockResourceResponse
	UNSUCCESSFUL OUTCOME	BlockResourceFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-blockResource, ddMode common } 
	CRITICALITY 			reject
}

-- *** RadioLinkSetup (FDD) ***
radioLinkSetupFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkSetupRequestFDD
	SUCCESSFUL OUTCOME		RadioLinkSetupResponseFDD
	UNSUCCESSFUL OUTCOME	RadioLinkSetupFailureFDD
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-radioLinkSetup, ddMode fdd } 
	CRITICALITY 			reject
}

-- *** RadioLinkSetup (TDD) ***
radioLinkSetupTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkSetupRequestTDD
	SUCCESSFUL OUTCOME		RadioLinkSetupResponseTDD
	UNSUCCESSFUL OUTCOME	RadioLinkSetupFailureTDD
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-radioLinkSetup, ddMode tdd } 
	CRITICALITY 			reject
}

-- *** SystemInformationUpdate ***
systemInformationUpdate NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		SystemInformationUpdateRequest
	SUCCESSFUL OUTCOME		SystemInformationUpdateResponse
	UNSUCCESSFUL OUTCOME	SystemInformationUpdateFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-systemInformationUpdate, ddMode common } 
	CRITICALITY 			reject
}

-- *** Reset ***
reset NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		ResetRequest
	SUCCESSFUL OUTCOME		ResetResponse
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-reset, ddMode common } 
	CRITICALITY 			reject
}

-- *** CommonMeasurementInitiation ***
commonMeasurementInitiation NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CommonMeasurementInitiationRequest
	SUCCESSFUL OUTCOME		CommonMeasurementInitiationResponse
	UNSUCCESSFUL OUTCOME	CommonMeasurementInitiationFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-commonMeasurementInitiation,	ddMode common } 
	CRITICALITY 			reject
}

-- *** RadioLinkAddition (FDD) ***
radioLinkAdditionFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkAdditionRequestFDD
	SUCCESSFUL OUTCOME		RadioLinkAdditionResponseFDD
	UNSUCCESSFUL OUTCOME	RadioLinkAdditionFailureFDD
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-radioLinkAddition, ddMode fdd } 
	CRITICALITY 			reject
}

-- *** RadioLinkAddition (TDD) ***
radioLinkAdditionTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkAdditionRequestTDD
	SUCCESSFUL OUTCOME		RadioLinkAdditionResponseTDD
	UNSUCCESSFUL OUTCOME	RadioLinkAdditionFailureTDD
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-radioLinkAddition, ddMode tdd } 
	CRITICALITY 			reject
}

-- *** RadioLinkDeletion	***
radioLinkDeletion NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkDeletionRequest
	SUCCESSFUL OUTCOME		RadioLinkDeletionResponse
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-radioLinkDeletion, ddMode common }
	CRITICALITY 			reject
}

-- *** SynchronisedRadioLinkReconfigurationPreparation (FDD) ***
synchronisedRadioLinkReconfigurationPreparationFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkReconfigurationPrepareFDD
	SUCCESSFUL OUTCOME		RadioLinkReconfigurationReady
	UNSUCCESSFUL OUTCOME	RadioLinkReconfigurationFailure
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-synchronisedRadioLinkReconfigurationPreparation, ddMode fdd } 
	CRITICALITY 			reject
}

-- *** SynchronisedRadioLinkReconfigurationPreparation (TDD) ***
synchronisedRadioLinkReconfigurationPreparationTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkReconfigurationPrepareTDD
	SUCCESSFUL OUTCOME		RadioLinkReconfigurationReady
	UNSUCCESSFUL OUTCOME	RadioLinkReconfigurationFailure
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-synchronisedRadioLinkReconfigurationPreparation, ddMode tdd } 
	CRITICALITY 			reject
}

-- *** UnSynchronisedRadioLinkReconfiguration (FDD) ***
unSynchronisedRadioLinkReconfigurationFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkReconfigurationRequestFDD
	SUCCESSFUL OUTCOME		RadioLinkReconfigurationResponse
	UNSUCCESSFUL OUTCOME	RadioLinkReconfigurationFailure
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-unSynchronisedRadioLinkReconfiguration, ddMode fdd } 
	CRITICALITY 			reject
}

-- *** UnSynchronisedRadioLinkReconfiguration (TDD) ***
unSynchronisedRadioLinkReconfigurationTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkReconfigurationRequestTDD
	SUCCESSFUL OUTCOME		RadioLinkReconfigurationResponse
	UNSUCCESSFUL OUTCOME	RadioLinkReconfigurationFailure
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-unSynchronisedRadioLinkReconfiguration, ddMode tdd } 
	CRITICALITY 			reject
}

-- *** DedicatedMeasurementInitiation  ***
dedicatedMeasurementInitiation NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		DedicatedMeasurementInitiationRequest
	SUCCESSFUL OUTCOME		DedicatedMeasurementInitiationResponse
	UNSUCCESSFUL OUTCOME	DedicatedMeasurementInitiationFailure
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-dedicatedMeasurementInitiation, ddMode common }
	CRITICALITY 			reject
}

-- *** PhysicalSharedChannelReconfiguration (FDD) ***
physicalSharedChannelReconfigurationFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE	PhysicalSharedChannelReconfigurationRequestFDD
	SUCCESSFUL OUTCOME	PhysicalSharedChannelReconfigurationResponse
	UNSUCCESSFUL OUTCOME	PhysicalSharedChannelReconfigurationFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 	{ procedureCode id-physicalSharedChannelReconfiguration, ddMode fdd } 
	CRITICALITY 	reject
}

-- *** PhysicalSharedChannelReconfiguration (TDD) ***
physicalSharedChannelReconfigurationTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE	PhysicalSharedChannelReconfigurationRequestTDD
	SUCCESSFUL OUTCOME	PhysicalSharedChannelReconfigurationResponse
	UNSUCCESSFUL OUTCOME	PhysicalSharedChannelReconfigurationFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 	{ procedureCode id-physicalSharedChannelReconfiguration, ddMode tdd } 
	CRITICALITY 	reject
}

-- *** InformationExchangeInitiation ***
informationExchangeInitiation NBAP-ELEMENTARY-PROCEDURE ::= {
    INITIATING MESSAGE		InformationExchangeInitiationRequest
	SUCCESSFUL OUTCOME		InformationExchangeInitiationResponse
	UNSUCCESSFUL OUTCOME	InformationExchangeInitiationFailure
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-informationExchangeInitiation, ddMode common } 
	CRITICALITY 			reject
}

-- *** CellSynchronisationInitiation (TDD only) ***
cellSynchronisationInitiationTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE	CellSynchronisationInitiationRequestTDD
	SUCCESSFUL OUTCOME	CellSynchronisationInitiationResponseTDD
	UNSUCCESSFUL OUTCOME	CellSynchronisationInitiationFailureTDD
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 	{ procedureCode id-cellSynchronisationInitiation, ddMode tdd } 
	CRITICALITY 	reject
}

-- *** CellSynchronisationReconfiguration (TDD only) ***
cellSynchronisationReconfigurationTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE	CellSynchronisationReconfigurationRequestTDD
	SUCCESSFUL OUTCOME	CellSynchronisationReconfigurationResponseTDD
	UNSUCCESSFUL OUTCOME	CellSynchronisationReconfigurationFailureTDD
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 	{ procedureCode id-cellSynchronisationReconfiguration, ddMode tdd } 
	CRITICALITY 	reject
}

-- *** CellSynchronisationAdjustment (TDD only) ***
cellSynchronisationAdjustmentTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE	CellSynchronisationAdjustmentRequestTDD
	SUCCESSFUL OUTCOME	CellSynchronisationAdjustmentResponseTDD
	UNSUCCESSFUL OUTCOME	CellSynchronisationAdjustmentFailureTDD
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 	{ procedureCode id-cellSynchronisationAdjustment, ddMode tdd } 
	CRITICALITY 	reject
}

-- *** UEStatusUpdateConfirmation ***
ueStatusUpdateConfirmation NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		UEStatusUpdateConfirmRequest
	SUCCESSFUL OUTCOME		UEStatusUpdateConfirmResponse
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-uEStatusUpdateConfirmation, ddMode common } 
	CRITICALITY				reject
}

-- Class 2

-- *** ResourceStatusIndication ***
resourceStatusIndication NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		ResourceStatusIndication
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-resourceStatusIndication, ddMode common } 
	CRITICALITY 			ignore
}

-- *** AuditRequired ***
auditRequired NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		AuditRequiredIndication
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-auditRequired, ddMode common } 
	CRITICALITY 			ignore
}

-- *** CommonMeasurementReport ***
commonMeasurementReport NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CommonMeasurementReport
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-commonMeasurementReport, ddMode common } 
	CRITICALITY 			ignore
}

-- *** CommonMeasurementTermination ***
commonMeasurementTermination NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CommonMeasurementTerminationRequest
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-commonMeasurementTermination, ddMode common } 
	CRITICALITY 			ignore
}

-- *** CommonMeasurementFailure ***
commonMeasurementFailure NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CommonMeasurementFailureIndication
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-commonMeasurementFailure, ddMode common } 
	CRITICALITY 			ignore
}

-- *** SynchronisedRadioLinkReconfigurationCommit ***
synchronisedRadioLinkReconfigurationCommit NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkReconfigurationCommit
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-synchronisedRadioLinkReconfigurationCommit, ddMode common } 
	CRITICALITY 			ignore
}

-- *** SynchronisedRadioReconfigurationCancellation ***
synchronisedRadioLinkReconfigurationCancellation NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkReconfigurationCancel
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-synchronisedRadioLinkReconfigurationCancellation, ddMode common } 
	CRITICALITY 			ignore
}

-- *** RadioLinkFailure ***
radioLinkFailure NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkFailureIndication
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-radioLinkFailure, ddMode common }
	CRITICALITY 			ignore
}

-- *** RadioLinkPreemption ***
radioLinkPreemption NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE	RadioLinkPreemptionRequiredIndication
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID	{ procedureCode id-radioLinkPreemption, ddMode common }
	CRITICALITY	ignore
}

-- *** RadioLinkRestoration ***
radioLinkRestoration NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkRestoreIndication
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-radioLinkRestoration, ddMode common }
	CRITICALITY 			ignore
}

-- *** DedicatedMeasurementReport ***
dedicatedMeasurementReport NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		DedicatedMeasurementReport
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-dedicatedMeasurementReport, ddMode common }
	CRITICALITY 			ignore
}

-- *** DedicatedMeasurementTermination  ***
dedicatedMeasurementTermination NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		DedicatedMeasurementTerminationRequest
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-dedicatedMeasurementTermination, ddMode common }
	CRITICALITY 			ignore
}

-- *** DedicatedMeasurementFailure ***
dedicatedMeasurementFailure NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		DedicatedMeasurementFailureIndication
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-dedicatedMeasurementFailure, ddMode common }
	CRITICALITY 			ignore
}

-- *** DLPowerControl (FDD only) ***
downlinkPowerControlFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		DL-PowerControlRequest
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-downlinkPowerControl, ddMode fdd }
	CRITICALITY 			ignore
}

-- *** DLPowerTimeslotControl (TDD only) ***
downlinkPowerTimeslotControl NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		DL-PowerTimeslotControlRequest
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-downlinkPowerTimeslotControl, ddMode tdd }
	CRITICALITY 			ignore
}

-- *** CompressedModeCommand (FDD only) ***
compressedModeCommand NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CompressedModeCommand
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-compressedModeCommand, ddMode fdd }
	CRITICALITY 			ignore
}

-- *** UnblockResourceIndication ***
unblockResource NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		UnblockResourceIndication
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-unblockResource, ddMode common } 
	CRITICALITY 			ignore
}

-- *** ErrorIndication for Dedicated procedures ***
errorIndicationForDedicated NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		ErrorIndication
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode	id-errorIndicationForDedicated, ddMode common }
	CRITICALITY 			ignore
}

-- *** ErrorIndication for Common procedures ***
errorIndicationForCommon NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		ErrorIndication
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode	id-errorIndicationForCommon, ddMode common }
	CRITICALITY 			ignore
}

-- *** CellSynchronisationReporting (TDD only) ***
cellSynchronisationReportingTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CellSynchronisationReportTDD
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode	id-cellSynchronisationReporting, ddMode tdd }
	CRITICALITY 			ignore
}

-- *** CellSynchronisationTermination (TDD only) ***
cellSynchronisationTerminationTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CellSynchronisationTerminationRequestTDD
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode	id-cellSynchronisationTermination, ddMode tdd }
	CRITICALITY 			ignore
}

-- *** CellSynchronisationFailure (TDD only) ***
cellSynchronisationFailureTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		CellSynchronisationFailureIndicationTDD
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode	id-cellSynchronisationFailure, ddMode tdd }
	CRITICALITY 			ignore
}

-- *** PrivateMessage for Dedicated procedures ***
privateMessageForDedicated NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		PrivateMessage
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID			{ procedureCode	id-privateMessageForDedicated, ddMode common }
	CRITICALITY				ignore
}

-- *** PrivateMessage for Common procedures ***
privateMessageForCommon NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		PrivateMessage
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID			{ procedureCode	id-privateMessageForCommon, ddMode common }
	CRITICALITY				ignore
}

-- *** InformationReporting ***
informationReporting NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		InformationReport
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-informationReporting, ddMode common } 
	CRITICALITY 			ignore
}

-- *** InformationExchangeTermination ***
informationExchangeTermination NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		InformationExchangeTerminationRequest
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-informationExchangeTermination, ddMode common } 
	CRITICALITY 			ignore
}

-- *** InformationExchangeFailure ***
informationExchangeFailure NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		InformationExchangeFailureIndication
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-informationExchangeFailure, ddMode common } 
	CRITICALITY 			ignore
}

-- *** BearerRearrangement ***
bearerRearrangement NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		BearerRearrangementIndication
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-BearerRearrangement, ddMode common }
	CRITICALITY 			ignore
}

-- *** RadioLinkActivation (FDD) ***
radioLinkActivationFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkActivationCommandFDD
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID			{ procedureCode id-radioLinkActivation, ddMode fdd }
	CRITICALITY				ignore
}

-- *** RadioLinkActivation (TDD) ***
radioLinkActivationTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkActivationCommandTDD
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID			{ procedureCode id-radioLinkActivation, ddMode tdd }
	CRITICALITY				ignore
}

-- *** RadioLinkParameterUpdate (FDD) ***
radioLinkParameterUpdateFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkParameterUpdateIndicationFDD
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-radioLinkParameterUpdate, ddMode fdd }
	CRITICALITY 			ignore
}

-- *** RadioLinkParameterUpdate (TDD) ***
radioLinkParameterUpdateTDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		RadioLinkParameterUpdateIndicationTDD
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-radioLinkParameterUpdate, ddMode tdd }
	CRITICALITY 			ignore
}

-- *** MBMSNotificationUpdate ***
mBMSNotificationUpdate NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		MBMSNotificationUpdateCommand
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-mBMSNotificationUpdate, ddMode common }
	CRITICALITY 			ignore
}

-- *** UEStatusUpdate  ***
uEStatusUpdate NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		UEStatusUpdateCommand
	MESSAGE DISCRIMINATOR	common
	PROCEDURE ID 			{ procedureCode id-uEStatusUpdate, ddMode common }
	CRITICALITY 			ignore
}

-- *** SecondaryULFrequencyReporting (FDD) ***
secondaryULFrequencyReportingFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		SecondaryULFrequencyReport
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID			{ procedureCode id-secondaryULFrequencyReporting, ddMode fdd }
	CRITICALITY				ignore
}

-- ***secondaryULFrequencyUpdate (FDD)
secondaryULFrequencyUpdateFDD NBAP-ELEMENTARY-PROCEDURE ::= {
	INITIATING MESSAGE		SecondaryULFrequencyUpdateIndication
	MESSAGE DISCRIMINATOR	dedicated
	PROCEDURE ID 			{ procedureCode id-secondaryULFrequencyUpdate, ddMode fdd }
	CRITICALITY 			ignore
}

END
9.3.3	PDU Definitions
-- **************************************************************
--
-- PDU definitions for NBAP.
--
-- **************************************************************

NBAP-PDU-Contents {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) 
umts-Access (20) modules (3) nbap (2) version1 (1) nbap-PDU-Contents (1) }

DEFINITIONS AUTOMATIC TAGS ::= 

BEGIN

-- **************************************************************
--
-- IE parameter types from other modules.
--
-- **************************************************************

IMPORTS
	Active-Pattern-Sequence-Information,
	AddorDeleteIndicator,
	MIMO-withfourtransmitantennas-PilotConfiguration,
	AICH-Power,
	AICH-TransmissionTiming,
	AllocationRetentionPriority,
	AlternativeFormatReportingIndicator,
	AvailabilityStatus,
	ActivationDelay,
	BCCH-ModificationTime,
	BindingID,
	BlockingPriorityIndicator,
	BroadcastReference,
	SCTD-Indicator,
	Cause,
	CCTrCH-ID,
	Cell-ERNTI-Status-Information,
	CellParameterID,
	CellPortionID,
	CellSyncBurstCode,
	CellSyncBurstCodeShift,
	CellSyncBurstRepetitionPeriod,
	CellSyncBurstSIR,
	CellSyncBurstTiming,
	CellSyncBurstTimingThreshold, 
	CellPortion-CapabilityLCR,
	CFN,
	ChipOffset,
	C-ID,
	Closedlooptimingadjustmentmode,
	CommonChannelsCapacityConsumptionLaw,
	Compressed-Mode-Deactivation-Flag,
	Common-MACFlows-to-DeleteFDD,
	CommonMeasurementAccuracy,
	CommonMeasurementType,
	CommonMeasurementValue,
	CommonMeasurementValueInformation,
	CommonPhysicalChannelID,
	CommonPhysicalChannelID768,
	Common-EDCH-Capability,
	Common-E-DCH-HSDPCCH-Capability,
	Common-EDCH-System-InformationFDD,
	Common-EDCH-System-Information-ResponseFDD,
	Common-PhysicalChannel-Status-Information,
	Common-PhysicalChannel-Status-Information768,
	Common-TransportChannel-Status-Information,
	CommonTransportChannelID,
	CommonTransportChannel-InformationResponse,
	CommunicationControlPortID,
	ConfigurationGenerationID,
	ConstantValue,
	ContinuousPacketConnectivityDTX-DRX-Capability,
	ContinuousPacketConnectivityDTX-DRX-Information,
	ContinuousPacketConnectivityHS-SCCH-less-Capability,
	ContinuousPacketConnectivityHS-SCCH-less-Information,
	ContinuousPacketConnectivityHS-SCCH-less-Information-Response,
	ContinuousPacketConnectivity-DRX-CapabilityLCR,
	ContinuousPacketConnectivity-DRX-InformationLCR,
	ContinuousPacketConnectivity-DRX-Information-ResponseLCR,
	CPC-InformationLCR,
	CPC-Information,
	CriticalityDiagnostics,
	CRNC-CommunicationContextID,
	CSBMeasurementID,
	CSBTransmissionID,
	DCH-FDD-Information,
	DCH-Indicator-For-E-DCH-HSDPA-Operation,
	DCH-InformationResponse,
	DCH-ID,
	FDD-DCHs-to-Modify,
	TDD-DCHs-to-Modify,
	DCH-TDD-Information,
	DedicatedChannelsCapacityConsumptionLaw,
	DedicatedMeasurementType,
	DedicatedMeasurementValue,
	DedicatedMeasurementValueInformation,
	DelayedActivation,
	DelayedActivationUpdate,
	DiversityControlField,
	DiversityMode,
	DL-DPCH-SlotFormat,
	DL-DPCH-TimingAdjustment,
	DL-or-Global-CapacityCredit,
	DL-Power,
	DL-PowerBalancing-Information,
	DL-PowerBalancing-ActivationIndicator,
	DLPowerAveragingWindowSize,
	DL-PowerBalancing-UpdatedIndicator,
	DL-ScramblingCode,
	DL-TimeslotISCP,
	DL-Timeslot-Information,
	DL-TimeslotLCR-Information,
	DL-TimeslotISCPInfo,
	DL-TimeslotISCPInfoLCR,
	DL-TPC-Pattern01Count,
	DPC-Mode,
	DPCH-ID,
	DPCH-ID768,
	DSCH-ID,
	DSCH-InformationResponse,
	DSCH-TDD-Information,
	Dual-Band-Capability-Info,
	DwPCH-Power,
	E-AGCH-FDD-Code-Information,
	E-AI-Capability,
	E-DCH-Capability,
	E-DCHCapacityConsumptionLaw,
	E-DCH-Decoupling-Indication,
	E-DCH-TTI2ms-Capability,
	E-DCH-SF-Capability,
	E-DCH-HARQ-Combining-Capability,
	E-DCH-FDD-DL-Control-Channel-Information,
	E-DCH-FDD-Information,
	E-DCH-FDD-Information-Response,
	E-DCH-FDD-Information-to-Modify,
	E-DCH-FDD-Update-Information,
	E-DCH-MACdFlow-ID,
	E-DCH-MACdFlows-Information,
	E-DCH-MACdFlows-to-Delete,
	E-DCH-MACdPDU-SizeCapability,
	E-DCH-RL-Indication,
	E-DCH-Serving-Cell-Change-Info-Response,
	E-DPCCH-PO,
	E-RGCH-E-HICH-FDD-Code-Information,
	E-RGCH-2-IndexStepThreshold,
	E-RGCH-3-IndexStepThreshold,
	End-Of-Audit-Sequence-Indicator,
	Enhanced-FACH-Capability,
	Enhanced-PCH-Capability,
	Enhanced-UE-DRX-Capability,
	Enhanced-UE-DRX-InformationFDD,
	E-TFCS-Information,
	E-TTI,
	ExtendedPropagationDelay,
	Fast-Reconfiguration-Mode,
	Fast-Reconfiguration-Permission,
	FDD-DL-ChannelisationCodeNumber,
	FDD-DL-CodeInformation,
	FDD-S-CCPCH-FrameOffset,
	FDD-S-CCPCH-Offset,
	FDD-TPC-DownlinkStepSize,
	F-DPCH-Capability,
	F-DPCH-SlotFormat,
	F-DPCH-SlotFormatCapability,
	FirstRLS-Indicator,
	FNReportingIndicator,
	FPACH-Power,
	FrameAdjustmentValue,
	FrameHandlingPriority,
	FrameOffset,
	HARQ-Info-for-E-DCH,
	HSDPA-Capability,
	HSDSCH-Common-System-InformationFDD,
	HSDSCH-Common-System-Information-ResponseFDD,
	HSDSCH-Configured-Indicator,
	HSDSCH-Paging-System-InformationFDD,
	HSDSCH-Paging-System-Information-ResponseFDD,
	HS-DSCH-Serving-Cell-Change-Info,
	HS-DSCH-Serving-Cell-Change-Info-Response,
	HSDSCH-MACdPDU-SizeCapability,
	HS-PDSCH-FDD-Code-Information,
	HS-SCCH-ID,
	HS-SCCH-FDD-Code-Information,
	HS-SICH-ID,
	IB-OC-ID,
	IB-SG-DATA,
	IB-SG-POS,
	IB-SG-REP,
	IB-Type,
	InformationExchangeID,
	InformationReportCharacteristics,
	InformationType,
	Initial-DL-DPCH-TimingAdjustment-Allowed,
	InnerLoopDLPCStatus,
	IPDL-FDD-Parameters,
	IPDL-TDD-Parameters,
	IPDL-Indicator,
	IPDL-TDD-Parameters-LCR,
	IPMulticastIndication,
	LimitedPowerIncrease,
	Local-Cell-ID,
	MaximumDL-PowerCapability,
	Maximum-Target-ReceivedTotalWideBandPower,
	MaximumTransmissionPower,
	MaxNrOfUL-DPDCHs,
	Max-Set-E-DPDCHs,
	MaxPRACH-MidambleShifts,
	Max-UE-DTX-Cycle,
	MBMS-Capability,
	MeasurementFilterCoefficient,
	MeasurementID,
	MeasurementRecoveryBehavior,
	MeasurementRecoveryReportingIndicator,
	MeasurementRecoverySupportIndicator,
	MICH-CFN,
	MICH-Mode,
	MidambleAllocationMode,
	MidambleShiftAndBurstType,
	MidambleShiftAndBurstType768,
	MidambleShiftLCR,
	MinimumDL-PowerCapability,
	MinSpreadingFactor,
	MIMO-Capability,
	MIMO-PilotConfiguration,
	MinUL-ChannelisationCodeLength,
	Modification-Period,
	MultiplexingPosition,
	NCyclesPerSFNperiod,
	NRepetitionsPerCyclePeriod,
	N-INSYNC-IND,
	N-OUTSYNC-IND,
	NeighbouringCellMeasurementInformation,
	NeighbouringFDDCellMeasurementInformation,
	NeighbouringTDDCellMeasurementInformation,
	NI-Information,
	NodeB-CommunicationContextID,
	Non-rectangular-resource-allocation-indicator,
	Non-rectangular-resource-timeslot-set,
	NotificationIndicatorLength,
	NumberOfReportedCellPortions, 
	NumberOfReportedCellPortionsLCR,
	NSubCyclesPerCyclePeriod,
	PagingIndicatorLength,
	Paging-MACFlows-to-DeleteFDD,
	PayloadCRC-PresenceIndicator,
	PCCPCH-Power,
	PDSCHSet-ID,
	PDSCH-ID,
	PDSCH-ID768,
	PICH-Mode,
	PICH-Power,
	PLCCHinformation,
	PowerAdjustmentType,
	PowerOffset,
	PowerRaiseLimit,
	PRACH-Midamble,
	PreambleSignatures,
	PreambleThreshold,
	PredictedSFNSFNDeviationLimit,
	PredictedTUTRANGPSDeviationLimit,
	PrimaryCPICH-Power,
	Primary-CPICH-Usage-for-Channel-Estimation,
	PrimaryScramblingCode,
	PropagationDelay,
	SCH-TimeSlot,
	PunctureLimit,
	PUSCHSet-ID,
	PUSCH-ID,
	QE-Selector,
	RACH-SlotFormat,
	RACH-SubChannelNumbers,
	Reference-ReceivedTotalWideBandPower,
	Reference-ReceivedTotalWideBandPowerReporting,
	Reference-ReceivedTotalWideBandPowerSupportIndicator,
	Maximum-Target-ReceivedTotalWideBandPower-LCR,
	ReferenceClockAvailability,
	ReferenceSFNoffset,
	RepetitionLength,
	RepetitionPeriod,
	ReportCharacteristics,
	RequestedDataValue,
	RequestedDataValueInformation,
	ResourceOperationalState,
	RL-Set-ID,
	RL-ID,
	RL-Specific-DCH-Info,
	RL-Specific-E-DCH-Info,
	Received-total-wide-band-power-Value,
	AdjustmentPeriod,
	ScaledAdjustmentRatio,
	MaxAdjustmentStep,
	RNC-ID,
	ScramblingCodeNumber,
	Secondary-CPICH-Information-Change,
	SecondaryCCPCH-SlotFormat,
	Segment-Type,
	Semi-PersistentScheduling-CapabilityLCR,
	Serving-E-DCH-RL-ID,
	SixteenQAM-UL-Capability,
	SixtyfourQAM-DL-Capability,
	SixtyfourQAM-DL-MIMO-Combined-Capability,
	SFN,
	SFNSFNChangeLimit,
	SFNSFNDriftRate,
	SFNSFNDriftRateQuality,
	SFNSFNQuality,
	ShutdownTimer,
	SIB-Originator,
	SpecialBurstScheduling,
	SignallingBearerRequestIndicator,
	Start-Of-Audit-Sequence-Indicator,
	STTD-Indicator,
	SSDT-SupportIndicator,
	E-DPCCH-Power-Boosting-Capability,
	SyncCase,
	SYNCDlCodeId,
	SyncFrameNumber,
	SynchronisationReportCharacteristics,
	SynchronisationReportType,
	Target-NonServing-EDCH-To-Total-EDCH-Power-Ratio,
	T-Cell,
	T-RLFAILURE,
	TDD-ChannelisationCode,
	TDD-ChannelisationCodeLCR,
	TDD-ChannelisationCode768,
	TDD-DL-Code-LCR-Information,
	TDD-DPCHOffset,
	TDD-TPC-DownlinkStepSize,
	TDD-PhysicalChannelOffset,
	TDD-UL-Code-LCR-Information,
	TFCI-Coding,
	TFCI-Presence,
	TFCI-SignallingMode,
	TFCS,
	TimeSlot,
	TimeSlotLCR,
	TimeSlotDirection,
	TimeSlotStatus,
	TimingAdjustmentValue,
	TimingAdvanceApplied,
	TnlQos,
	ToAWE,
	ToAWS,
	TransmissionDiversityApplied,
	TransmitDiversityIndicator,
	TransmissionGapPatternSequenceCodeInformation,
	Transmission-Gap-Pattern-Sequence-Information,
	TransportBearerRequestIndicator,
	TransportFormatSet,
	TransportLayerAddress,
	TSTD-Indicator,
	TUTRANGPS,
	TUTRANGPSChangeLimit,
	TUTRANGPSDriftRate,
	TUTRANGPSDriftRateQuality,
	TUTRANGPSQuality,
	UARFCN,
	UC-Id,
	UE-Support-of-non-rectangular-resource-allocation,
	USCH-Information,
	USCH-InformationResponse,
	UL-CapacityCredit,
	UL-DPCCH-SlotFormat,
	UL-DPDCH-Indicator-For-E-DCH-Operation,
	UL-SIR,
	UL-FP-Mode,
	UL-PhysCH-SF-Variation,
	UL-ScramblingCode,
	UL-Timeslot-Information,
	UL-TimeslotLCR-Information,
	UL-TimeSlot-ISCP-Info,
	UL-TimeSlot-ISCP-LCR-Info,
	UL-TimeslotISCP-Value,
	UL-TimeslotISCP-Value-IncrDecrThres,
	USCH-ID,
	HSDSCH-FDD-Information,
	HSDSCH-FDD-Information-Response,
	HSDSCH-Information-to-Modify,
	HSDSCH-Information-to-Modify-Unsynchronised,
	HSDSCH-MACdFlow-ID,
	HSDSCH-MACdFlows-Information,
	HSDSCH-MACdFlows-to-Delete,
	HSDSCH-RNTI,
	HSDSCH-TDD-Information,
	HSDSCH-TDD-Information-Response,
	PrimaryCCPCH-RSCP,
	HSDSCH-FDD-Update-Information,
	HSDSCH-TDD-Update-Information,
	UL-Synchronisation-Parameters-LCR,
	TDD-DL-DPCH-TimeSlotFormat-LCR,
	TDD-UL-DPCH-TimeSlotFormat-LCR,
	TDD-TPC-UplinkStepSize-LCR,
	CellSyncBurstTimingLCR,
	TimingAdjustmentValueLCR,
	PrimaryCCPCH-RSCP-Delta,
	SynchronisationIndicator,
	TDD-UL-Code-768-Information,
	UL-Timeslot768-Information,
	TDD-DL-Code-768-Information,
	DL-Timeslot768-Information,
	E-DCH-TDD-CapacityConsumptionLaw,
	E-DCH-Information,
	E-DCH-Information-Response,
	E-DCH-Information-Reconfig,
	LTGI-Presence,
	SNPL-Reporting-Type,
	E-AGCH-Id,
	E-HICH-TimeOffset,
	Maximum-Generated-ReceivedTotalWideBandPowerInOtherCells,
	E-DCH-768-Information,
	E-DCH-768-Information-Reconfig,
	RTWP-ReportingIndicator,
	RTWP-CellPortion-ReportingIndicator,
	MAChs-ResetIndicator,
	E-DCH-LCR-Information,
	E-DCH-LCR-Information-Reconfig,
	E-HICH-ID-TDD,
	E-HICH-TimeOffsetLCR,
	E-HICH-Type,
	ModulationPO-MBSFN,
	Secondary-CCPCH-SlotFormat-Extended,
	ModulationMBSFN,
	MBSFN-Only-Mode-Indicator,
	MBSFN-Only-Mode-Capability,
	UPPCHPositionLCR,
	ControlGAP,
	IdleIntervalInformation,
	Extended-HS-SICH-ID,
	Extended-HS-SCCH-ID,
	TimeslotLCR-Extension,
	Extended-E-HICH-ID-TDD,
	AdditionalTimeSlotListLCR,
	AdditionalMeasurementValueList,
	HS-SCCH-ID-LCR,
	Paging-MACFlows-to-DeleteLCR,
	HSDSCH-Paging-System-InformationLCR,
	HSDSCH-Paging-System-Information-ResponseLCR,
	HSDSCH-Common-System-InformationLCR,
	HSDSCH-Common-System-Information-ResponseLCR,
	Enhanced-UE-DRX-InformationLCR,
	E-DCH-MACdFlow-ID-LCR,
	Common-EDCH-System-InformationLCR,
	Common-EDCH-System-Information-ResponseLCR,
	Common-MACFlows-to-DeleteLCR,
	DL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst,
	E-DCH-MACdFlows-to-DeleteLCR,
	HSDSCH-PreconfigurationSetup,
	HSDSCH-PreconfigurationInfo,
	NoOfTargetCellHS-SCCH-Order,
	EnhancedHSServingCC-Abort,
	GANSS-Time-ID,
	HS-DSCH-FDD-Secondary-Serving-Update-Information,
	HS-DSCH-Secondary-Serving-Remove,
	HS-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised,
	HS-DSCH-Secondary-Serving-Information-To-Modify,
	HS-DSCH-Secondary-Serving-Cell-Change-Information-Response,
	HS-DSCH-FDD-Secondary-Serving-Information-Response,
	HS-DSCH-FDD-Secondary-Serving-Information,
	Multi-Cell-Capability-Info,
	MinimumReducedE-DPDCH-GainFactor,
	IMB-Parameters,
	E-RNTI,
	E-DCH-Semi-PersistentScheduling-Information-LCR,
	HS-DSCH-Semi-PersistentScheduling-Information-LCR,
	Add-To-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst,
	Modify-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst,
	Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst, 
	Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext,
	HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR,
	E-DCH-Semi-PersistentScheduling-Information-ResponseLCR,
	HSSICH-ReferenceSignal-InformationLCR,
	UE-Selected-MBMS-Service-Information,
	UE-AggregateMaximumBitRate,
	HSSICH-ReferenceSignal-InformationModifyLCR,
	TimeSlotMeasurementValueListLCR,
	MIMO-PowerOffsetForS-CPICHCapability,
	MIMO-PilotConfigurationExtension,
	TxDiversityOnDLControlChannelsByMIMOUECapability,
	Single-Stream-MIMO-Capability,	
	ActivationInformation,
	Cell-Capability-Container,
	DormantModeIndicator,
	Additional-EDCH-Setup-Info,
	Additional-EDCH-Cell-Information-Response-List,
	Additional-EDCH-Cell-Information-To-Add-List,
	Additional-EDCH-FDD-Update-Information,
	TS0-CapabilityLCR,
	Out-of-Sychronization-Window,
	DCH-MeasurementOccasion-Information,
	Additional-EDCH-Cell-Information-Response-RLReconf-List,
	Setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency,
	Additional-EDCH-Cell-Information-Response-RL-Add-List,
	PrecodingWeightSetRestriction,
	Non-Serving-RL-Preconfig-Setup,
	Non-Serving-RL-Preconfig-Info,
	Cell-Capability-Container-TDD-LCR,
	Multi-Carrier-EDCH-Info,
	Multi-Carrier-EDCH-Reconfigure,
	Multi-Carrier-EDCH-Information-Response,
	MU-MIMO-Capability-ContainerLCR,
	MU-MIMO-InformationLCR,
	MU-MIMO-Information-Response,
	MU-MIMO-Information-To-ReconfigureLCR,
	Adaptive-Special-Burst-Power-CapabilityLCR,
	Usefulness-Of-Battery-Optimization,
	In-Sync-Information-LCR,
	ERNTI-Release-Status,
	CellPortionLCRID,
	CPC-RecoveryReport,
	UL-CLTD-Information,
	UL-CLTD-Information-Reconf,
	UL-CLTD-State-Update-Information,
	FTPICH-Information,
	FTPICH-Information-Reconf,
	Common-E-RGCH-InfoFDD,
	Further-Enhanced-UE-DRX-InformationFDD,
	Common-E-RGCH-Operation-Indicator,
	DCH-ENH-Information,
	DCH-ENH-Information-Reconf,
	BCH-Parameters,
	Radio-Links-without-DPCH-FDPCH-Indication,
	UL-DPCCH2-Information,
	UL-DPCCH2-Information-Reconf,
	UE-Measurement-Value,
	Downlink-TPC-enhancements-Information,
	Downlink-TPC-enhancements-Reconf,
	TPC-slot-position,
	Improved-Synchronized-Indicator

FROM NBAP-IEs

	PrivateIE-Container{},
	ProtocolExtensionContainer{},
	ProtocolIE-Container{},
	ProtocolIE-Single-Container{},
	ProtocolIE-ContainerList{},
	NBAP-PRIVATE-IES,
	NBAP-PROTOCOL-IES,
	NBAP-PROTOCOL-EXTENSION
FROM NBAP-Containers

	id-Active-Pattern-Sequence-Information,
	id-Additional-S-CCPCH-Parameters-CTCH-ReconfRqstTDD,
	id-Additional-S-CCPCH-Parameters-CTCH-SetupRqstTDD,
	id-Additional-S-CCPCH-LCR-Parameters-CTCH-ReconfRqstTDD,
	id-Additional-S-CCPCH-LCR-Parameters-CTCH-SetupRqstTDD,
	id-MIMO-withfourtransmitantennas-PilotConfiguration,
	id-AdjustmentRatio,
	id-AICH-Information,
	id-AICH-ParametersListIE-CTCH-ReconfRqstFDD,
	id-AlternativeFormatReportingIndicator,
	id-BCH-Information,
	id-BCCH-ModificationTime,
	id-bindingID,
	id-BlockingPriorityIndicator,
	id-BroadcastReference,
	id-Cause,
	id-CauseLevel-PSCH-ReconfFailure,
	id-CauseLevel-RL-AdditionFailureFDD,
	id-CauseLevel-RL-AdditionFailureTDD,
	id-CauseLevel-RL-ReconfFailure,
	id-CauseLevel-RL-SetupFailureFDD,
	id-CauseLevel-RL-SetupFailureTDD,
	id-CauseLevel-SyncAdjustmntFailureTDD,
	id-CCP-InformationItem-AuditRsp,
	id-CCP-InformationList-AuditRsp,
	id-CCP-InformationItem-ResourceStatusInd,
	id-CCTrCH-InformationItem-RL-FailureInd,
	id-CCTrCH-InformationItem-RL-RestoreInd,
	id-CCTrCH-Initial-DL-Power-RL-AdditionRqstTDD,
	id-CCTrCH-Initial-DL-Power-RL-ReconfPrepTDD,
	id-CCTrCH-Initial-DL-Power-RL-SetupRqstTDD,
	id-CellAdjustmentInfo-SyncAdjustmntRqstTDD,
	id-CellAdjustmentInfoItem-SyncAdjustmentRqstTDD,
	id-Cell-ERNTI-Status-Information,
	id-Cell-InformationItem-AuditRsp,
	id-Cell-InformationItem-ResourceStatusInd,
	id-Cell-InformationList-AuditRsp,
	id-CellParameterID,
	id-CellPortion-InformationItem-Cell-SetupRqstFDD,
	id-CellPortion-InformationList-Cell-SetupRqstFDD,
	id-CellPortion-InformationItem-Cell-ReconfRqstFDD,
	id-CellPortion-InformationList-Cell-ReconfRqstFDD,
	id-CellSyncBurstTransInit-CellSyncInitiationRqstTDD,
	id-CellSyncBurstMeasureInit-CellSyncInitiationRqstTDD,
	id-cellSyncBurstRepetitionPeriod,
	id-CellSyncBurstTransReconfiguration-CellSyncReconfRqstTDD,
	id-CellSyncBurstTransReconfInfo-CellSyncReconfRqstTDD,
	id-CellSyncBurstMeasReconfiguration-CellSyncReconfRqstTDD,
	id-CellSyncBurstMeasInfoList-CellSyncReconfRqstTDD,
	id-CellSyncBurstInfoList-CellSyncReconfRqstTDD,
	id-CellSyncInfo-CellSyncReprtTDD, 
	id-CellPortion-CapabilityLCR,
	id-CFN,
	id-CFNReportingIndicator,
	id-C-ID,
	id-Closed-Loop-Timing-Adjustment-Mode,
	id-Common-EDCH-Capability,
	id-Common-E-DCH-HSDPCCH-Capability,
	id-Common-EDCH-MACdFlows-to-DeleteFDD,
	id-Common-EDCH-System-InformationFDD,
	id-Common-EDCH-System-Information-ResponseFDD,
	id-Common-MACFlows-to-DeleteFDD,
	id-CommonMeasurementAccuracy,
	id-CommonMeasurementObjectType-CM-Rprt,
	id-CommonMeasurementObjectType-CM-Rqst,
	id-CommonMeasurementObjectType-CM-Rsp,
	id-CommonMeasurementType,
	id-CommonPhysicalChannelID,
	id-CommonPhysicalChannelType-CTCH-ReconfRqstFDD,
	id-CommonPhysicalChannelType-CTCH-SetupRqstFDD,
	id-CommonPhysicalChannelType-CTCH-SetupRqstTDD,
	id-Common-UL-MACFlows-to-DeleteFDD,
	id-CommunicationContextInfoItem-Reset,
	id-CommunicationControlPortID,
	id-CommunicationControlPortInfoItem-Reset,
	id-Compressed-Mode-Deactivation-Flag,
	id-ConfigurationGenerationID,
	id-ContinuousPacketConnectivityDTX-DRX-Capability,
	id-ContinuousPacketConnectivityDTX-DRX-Information,
	id-ContinuousPacketConnectivityHS-SCCH-less-Capability,
	id-ContinuousPacketConnectivityHS-SCCH-less-Information,
	id-ContinuousPacketConnectivityHS-SCCH-less-Information-Response,
	id-ContinuousPacketConnectivity-DRX-CapabilityLCR,
	id-ContinuousPacketConnectivity-DRX-InformationLCR,
	id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR,
	id-CPC-InformationLCR,
	id-CPC-Information,
	id-CRNC-CommunicationContextID,
	id-CriticalityDiagnostics,
	id-CSBTransmissionID,
	id-CSBMeasurementID,
	id-DCHs-to-Add-FDD,
	id-DCHs-to-Add-TDD,
	id-DCH-AddList-RL-ReconfPrepTDD,
	id-DCH-DeleteList-RL-ReconfPrepFDD,
	id-DCH-DeleteList-RL-ReconfPrepTDD,
	id-DCH-DeleteList-RL-ReconfRqstFDD,
	id-DCH-DeleteList-RL-ReconfRqstTDD,
	id-DCH-FDD-Information,
	id-DCH-TDD-Information,
	id-DCH-Indicator-For-E-DCH-HSDPA-Operation,
	id-DCH-InformationResponse,
	id-DCH-RearrangeList-Bearer-RearrangeInd,
	id-DSCH-RearrangeList-Bearer-RearrangeInd,
	id-FDD-DCHs-to-Modify,
	id-FDD-S-CCPCH-FrameOffset-CTCH-SetupRqstFDD,
	id-TDD-DCHs-to-Modify,
	id-DedicatedMeasurementObjectType-DM-Rprt,
	id-DedicatedMeasurementObjectType-DM-Rqst,
	id-DedicatedMeasurementObjectType-DM-Rsp,
	id-DedicatedMeasurementType,
	id-DelayedActivation,
	id-DelayedActivationList-RL-ActivationCmdFDD,
	id-DelayedActivationList-RL-ActivationCmdTDD,
	id-DelayedActivationInformation-RL-ActivationCmdFDD,
	id-DelayedActivationInformation-RL-ActivationCmdTDD,
	id-DL-CCTrCH-InformationAddList-RL-ReconfPrepTDD,
	id-DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD,
	id-DL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD,
	id-DL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD,
	id-DL-CCTrCH-InformationItem-RL-SetupRqstTDD,
	id-DL-CCTrCH-InformationList-RL-AdditionRqstTDD,
	id-DL-CCTrCH-InformationList-RL-SetupRqstTDD,
	id-DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD,
	id-DL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD,
	id-DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD,
	id-DL-DPCH-InformationAddListIE-RL-ReconfPrepTDD,
	id-DL-DPCH-InformationItem-RL-AdditionRqstTDD,
	id-DL-DPCH-InformationList-RL-SetupRqstTDD,
	id-DL-DPCH-InformationModify-AddListIE-RL-ReconfPrepTDD,
	id-DL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD,
	id-DL-DPCH-InformationModify-ModifyListIE-RL-ReconfPrepTDD,
	id-DL-DPCH-Information-RL-ReconfPrepFDD,
	id-DL-DPCH-Information-RL-ReconfRqstFDD,
	id-DL-DPCH-Information-RL-SetupRqstFDD,
	id-DL-DPCH-TimingAdjustment,
	id-DL-DPCH-Power-Information-RL-ReconfPrepFDD,
	id-DL-PowerBalancing-Information,
	id-DL-PowerBalancing-ActivationIndicator,
	id-DL-ReferencePowerInformationItem-DL-PC-Rqst,
	id-DL-PowerBalancing-UpdatedIndicator,
	id-DLReferencePower,
	id-DLReferencePowerList-DL-PC-Rqst,
	id-DL-TPC-Pattern01Count,
	id-DPC-Mode,
	id-DPCHConstant,
	id-DSCHs-to-Add-TDD,
	id-DSCH-Information-DeleteList-RL-ReconfPrepTDD,
	id-DSCH-Information-ModifyList-RL-ReconfPrepTDD,
	id-DSCH-InformationResponse,
	id-DSCH-TDD-Information,
	id-Dual-Band-Capability-Info,
	id-E-AGCH-And-E-RGCH-E-HICH-FDD-Scrambling-Code,
	id-E-AI-Capability,
	id-E-AGCH-FDD-Code-Information,
	id-E-DCH-Capability,
	id-E-DCH-Decoupling-Indication,
	id-E-DCH-TTI2ms-Capability,
	id-E-DCH-SF-Capability,
	id-E-DCH-HARQ-Combining-Capability,
	id-E-DCH-FDD-DL-Control-Channel-Information,
	id-E-DCH-FDD-Information,
	id-E-DCH-FDD-Information-Response,
	id-E-DCH-FDD-Information-to-Modify,
	id-E-DCH-FDD-Update-Information,
	id-E-DCH-MACdFlows-to-Add,
	id-E-DCH-MACdFlows-to-Delete,
	id-E-DCH-RearrangeList-Bearer-RearrangeInd,
	id-E-DCH-Resources-Information-AuditRsp,
	id-E-DCH-Resources-Information-ResourceStatusInd,
	id-E-DCH-RL-Indication,
	id-E-DCH-RL-Set-ID,
	id-E-DCH-Serving-Cell-Change-Info-Response,
	id-E-DCH-CapacityConsumptionLaw,
	id-E-DPCH-Information-RL-ReconfPrepFDD,
	id-E-DPCH-Information-RL-ReconfRqstFDD,
	id-E-DPCH-Information-RL-SetupRqstFDD,
	id-E-DPCH-Information-RL-AdditionReqFDD,
	id-E-RGCH-E-HICH-FDD-Code-Information,
	id-ERACH-CM-Rqst,
	id-ERACH-CM-Rsp,
	id-ERACH-CM-Rprt,
	id-End-Of-Audit-Sequence-Indicator,
	id-Enhanced-FACH-Capability,
	id-Enhanced-PCH-Capability,
	id-Enhanced-UE-DRX-Capability,
	id-Enhanced-UE-DRX-InformationFDD,
	id-ExtendedPropagationDelay,
	id-FACH-Information,
	id-FACH-ParametersList-CTCH-ReconfRqstTDD,
	id-FACH-ParametersList-CTCH-SetupRsp,
	id-FACH-ParametersListIE-CTCH-ReconfRqstFDD,
	id-FACH-ParametersListIE-CTCH-SetupRqstFDD,
	id-FACH-ParametersListIE-CTCH-SetupRqstTDD,
	id-Fast-Reconfiguration-Mode,
	id-Fast-Reconfiguration-Permission,
	id-F-DPCH-Capability,
	id-F-DPCH-Information-RL-ReconfPrepFDD,
	id-F-DPCH-Information-RL-SetupRqstFDD,
	id-F-DPCH-SlotFormat,
	id-F-DPCH-SlotFormatCapability,
	id-HSDPA-And-EDCH-CellPortion-Information-PSCH-ReconfRqst,
	id-HSDSCH-Configured-Indicator,
	id-HS-DSCH-Serving-Cell-Change-Info,
	id-HS-DSCH-Serving-Cell-Change-Info-Response,
	id-IndicationType-ResourceStatusInd,
	id-InformationExchangeID,
	id-InformationExchangeObjectType-InfEx-Rqst,
	id-InformationExchangeObjectType-InfEx-Rsp,
	id-InformationExchangeObjectType-InfEx-Rprt,
	id-InformationReportCharacteristics,	
	id-InformationType,
	id-InitDL-Power,
	id-Initial-DL-DPCH-TimingAdjustment,
	id-Initial-DL-DPCH-TimingAdjustment-Allowed,
	id-InnerLoopDLPCStatus,
	id-IntStdPhCellSyncInfoItem-CellSyncReprtTDD,
	id-IPDLParameter-Information-Cell-ReconfRqstFDD,
	id-IPDLParameter-Information-Cell-SetupRqstFDD,
	id-IPDLParameter-Information-Cell-ReconfRqstTDD,
	id-IPDLParameter-Information-Cell-SetupRqstTDD,
	id-IPMulticastIndication,
	id-LateEntranceCellSyncInfoItem-CellSyncReprtTDD,
	id-Limited-power-increase-information-Cell-SetupRqstFDD,
	id-Local-Cell-ID,
	id-Local-Cell-Group-InformationItem-AuditRsp,
	id-Local-Cell-Group-InformationItem-ResourceStatusInd,
	id-Local-Cell-Group-InformationItem2-ResourceStatusInd,
	id-Local-Cell-Group-InformationList-AuditRsp,
	id-Local-Cell-InformationItem-AuditRsp,
	id-Local-Cell-InformationItem-ResourceStatusInd,
	id-Local-Cell-InformationItem2-ResourceStatusInd,
	id-Local-Cell-InformationList-AuditRsp,
	id-AdjustmentPeriod,
	id-MaxAdjustmentStep,
	id-MaximumTransmissionPower,
	id-Max-UE-DTX-Cycle,
	id-MeasurementFilterCoefficient,
	id-MeasurementID,
	id-MeasurementRecoveryBehavior,
	id-MeasurementRecoveryReportingIndicator,
	id-MeasurementRecoverySupportIndicator,
	id-MIB-SB-SIB-InformationList-SystemInfoUpdateRqst,
	id-MBMS-Capability,
	id-MICH-CFN,
	id-MICH-Information-AuditRsp,
	id-MICH-Information-ResourceStatusInd,
	id-MICH-Parameters-CTCH-ReconfRqstFDD,
	id-MICH-Parameters-CTCH-ReconfRqstTDD,
	id-MICH-Parameters-CTCH-SetupRqstFDD,
	id-MICH-Parameters-CTCH-SetupRqstTDD,
	id-MIMO-Capability,
	id-MIMO-PilotConfiguration,
	id-Modification-Period,
	id-multipleRL-dl-DPCH-InformationList,
	id-multipleRL-dl-DPCH-InformationModifyList,
	id-multipleRL-dl-CCTrCH-InformationModifyList-RL-ReconfRqstTDD,
	id-multiple-RL-Information-RL-ReconfPrepTDD,
	id-multiple-RL-Information-RL-ReconfRqstTDD,
	id-multipleRL-ul-DPCH-InformationList,
	id-multipleRL-ul-DPCH-InformationModifyList,
	id-NCyclesPerSFNperiod,
	id-NeighbouringCellMeasurementInformation,
	id-NI-Information-NotifUpdateCmd,
	id-NodeB-CommunicationContextID,
	id-Non-rectangular-resource-allocation-indicator,
	id-Non-rectangular-resource-timeslot-set,
	id-NRepetitionsPerCyclePeriod,
	id-NumberOfReportedCellPortions, 
	id-NumberOfReportedCellPortionsLCR,
	id-Paging-MACFlows-to-DeleteFDD,
	id-P-CCPCH-Information,
	id-P-CPICH-Information,
	id-P-SCH-Information,
	id-PCCPCH-Information-Cell-ReconfRqstTDD,
	id-PCCPCH-Information-Cell-SetupRqstTDD,
	id-PCH-Parameters-CTCH-ReconfRqstTDD,
	id-PCH-Parameters-CTCH-SetupRsp,
	id-PCH-ParametersItem-CTCH-ReconfRqstFDD,
	id-PCH-ParametersItem-CTCH-SetupRqstFDD,
	id-PCH-ParametersItem-CTCH-SetupRqstTDD,
	id-PCH-Information,
	id-PICH-ParametersItem-CTCH-ReconfRqstFDD,
	id-PDSCH-Information-AddListIE-PSCH-ReconfRqst,
	id-PDSCH-Information-ModifyListIE-PSCH-ReconfRqst,
	id-PDSCH-RL-ID,
	id-PDSCH-Timeslot-Format-PSCH-ReconfRqst-LCR,
	id-PDSCHSets-AddList-PSCH-ReconfRqst,
	id-PDSCHSets-DeleteList-PSCH-ReconfRqst,
	id-PDSCHSets-ModifyList-PSCH-ReconfRqst,
	id-PICH-Information,
	id-PICH-Parameters-CTCH-ReconfRqstTDD,
	id-PICH-ParametersItem-CTCH-SetupRqstTDD,
	id-PLCCH-Information-AuditRsp,
	id-PLCCH-Information-ResourceStatusInd,
	id-PLCCH-Information-RL-ReconfPrepTDDLCR,
	id-PLCCH-InformationList-AuditRsp,
	id-PLCCH-InformationList-ResourceStatusInd,
	id-PLCCH-Parameters-CTCH-ReconfRqstTDD,
	id-PowerAdjustmentType,
	id-Power-Local-Cell-Group-choice-CM-Rqst,
	id-Power-Local-Cell-Group-choice-CM-Rsp,
	id-Power-Local-Cell-Group-choice-CM-Rprt,
	id-Power-Local-Cell-Group-InformationItem-AuditRsp,
	id-Power-Local-Cell-Group-InformationItem-ResourceStatusInd,
	id-Power-Local-Cell-Group-InformationItem2-ResourceStatusInd,
	id-Power-Local-Cell-Group-InformationList-AuditRsp,
	id-Power-Local-Cell-Group-InformationList-ResourceStatusInd,
	id-Power-Local-Cell-Group-InformationList2-ResourceStatusInd,
	id-Power-Local-Cell-Group-ID,
	id-PRACH-Information,
	id-PRACHConstant,
	id-PRACH-ParametersItem-CTCH-SetupRqstTDD,
	id-PRACH-ParametersListIE-CTCH-ReconfRqstFDD,
	id-PrimaryCCPCH-Information-Cell-ReconfRqstFDD,
	id-PrimaryCCPCH-Information-Cell-SetupRqstFDD,
	id-PrimaryCPICH-Information-Cell-ReconfRqstFDD,
	id-PrimaryCPICH-Information-Cell-SetupRqstFDD,
	id-Primary-CPICH-Usage-for-Channel-Estimation,
	id-PrimarySCH-Information-Cell-ReconfRqstFDD,
	id-PrimarySCH-Information-Cell-SetupRqstFDD,
	id-PrimaryScramblingCode,
	id-SCH-Information-Cell-ReconfRqstTDD,
	id-SCH-Information-Cell-SetupRqstTDD,
	id-PUSCH-Information-AddListIE-PSCH-ReconfRqst,
	id-PUSCH-Information-ModifyListIE-PSCH-ReconfRqst,
	id-PUSCH-Timeslot-Format-PSCH-ReconfRqst-LCR,
	id-PUSCHConstant,
	id-PUSCHSets-AddList-PSCH-ReconfRqst,
	id-PUSCHSets-DeleteList-PSCH-ReconfRqst,
	id-PUSCHSets-ModifyList-PSCH-ReconfRqst,
	id-RACH-Information,
	id-RACH-Parameters-CTCH-SetupRsp,
	id-RACH-ParametersItem-CTCH-SetupRqstFDD,
	id-RACH-ParameterItem-CTCH-SetupRqstTDD,
	id-ReferenceClockAvailability,
	id-ReferenceSFNoffset,
	id-ReportCharacteristics,
	id-Reporting-Object-RL-FailureInd,
	id-Reporting-Object-RL-RestoreInd,
	id-ResetIndicator,
	id-RL-ID,
	id-RL-InformationItem-DM-Rprt,
	id-RL-InformationItem-DM-Rqst,
	id-RL-InformationItem-DM-Rsp,
	id-RL-InformationItem-RL-AdditionRqstFDD,
	id-RL-informationItem-RL-DeletionRqst,
	id-RL-InformationItem-RL-FailureInd,
	id-RL-InformationItem-RL-PreemptRequiredInd,
	id-RL-InformationItem-RL-ReconfPrepFDD,
	id-RL-InformationItem-RL-ReconfRqstFDD,
	id-RL-InformationItem-RL-RestoreInd,
	id-RL-InformationItem-RL-SetupRqstFDD,
	id-RL-InformationList-RL-AdditionRqstFDD,
	id-RL-informationList-RL-DeletionRqst,
	id-RL-InformationList-RL-PreemptRequiredInd,
	id-RL-InformationList-RL-ReconfPrepFDD,
	id-RL-InformationList-RL-ReconfRqstFDD,
	id-RL-InformationList-RL-SetupRqstFDD,
	id-RL-InformationResponseItem-RL-AdditionRspFDD,
	id-RL-InformationResponseItem-RL-ReconfReady,
	id-RL-InformationResponseItem-RL-ReconfRsp,
	id-RL-InformationResponseItem-RL-SetupRspFDD,
	id-RL-InformationResponseList-RL-AdditionRspFDD,
	id-RL-InformationResponseList-RL-ReconfReady,
	id-RL-InformationResponseList-RL-ReconfRsp,
	id-RL-InformationResponseList-RL-SetupRspFDD,
	id-RL-InformationResponse-RL-AdditionRspTDD,
	id-RL-InformationResponse-RL-SetupRspTDD,
	id-RL-Information-RL-AdditionRqstTDD,
	id-RL-Information-RL-ReconfRqstTDD,
	id-RL-Information-RL-ReconfPrepTDD,
	id-RL-Information-RL-SetupRqstTDD,
	id-RL-ReconfigurationFailureItem-RL-ReconfFailure,
	id-RL-Set-InformationItem-DM-Rprt,
	id-RL-Set-InformationItem-DM-Rsp,
	id-RL-Set-InformationItem-RL-FailureInd,
	id-RL-Set-InformationItem-RL-RestoreInd,
	id-RL-Specific-DCH-Info,
	id-RL-Specific-E-DCH-Info,
	id-S-CCPCH-Information,
	id-S-CCPCH-InformationListExt-AuditRsp,
	id-S-CCPCH-InformationListExt-ResourceStatusInd,
	id-S-CCPCH-LCR-InformationListExt-AuditRsp,
	id-S-CCPCH-LCR-InformationListExt-ResourceStatusInd,
	id-S-CPICH-Information,
	id-SCH-Information,
	id-S-SCH-Information,
	id-Secondary-CCPCHListIE-CTCH-ReconfRqstTDD,
	id-Secondary-CCPCH-parameterListIE-CTCH-SetupRqstTDD,
	id-Secondary-CCPCH-Parameters-CTCH-ReconfRqstTDD,
	id-Secondary-CPICH-Information,
	id-SecondaryCPICH-InformationItem-Cell-ReconfRqstFDD,
	id-SecondaryCPICH-InformationItem-Cell-SetupRqstFDD,
	id-SecondaryCPICH-InformationList-Cell-ReconfRqstFDD,
	id-SecondaryCPICH-InformationList-Cell-SetupRqstFDD,
	id-Secondary-CPICH-Information-Change,
	id-SecondarySCH-Information-Cell-ReconfRqstFDD,
	id-SecondarySCH-Information-Cell-SetupRqstFDD,
	id-Semi-PersistentScheduling-CapabilityLCR,
	id-SegmentInformationListIE-SystemInfoUpdate,
	id-Serving-Cell-Change-CFN,
	id-Serving-E-DCH-RL-ID,
	id-SixteenQAM-UL-Capability,
	id-SixtyfourQAM-DL-Capability,
	id-SixtyfourQAM-DL-MIMO-Combined-Capability,
	id-SFN,
	id-SFNReportingIndicator,
	id-ShutdownTimer,
	id-SignallingBearerRequestIndicator,
	id-Start-Of-Audit-Sequence-Indicator,
	id-Successful-RL-InformationRespItem-RL-AdditionFailureFDD,
	id-Successful-RL-InformationRespItem-RL-SetupFailureFDD,
	id-E-DPCCH-Power-Boosting-Capability,
	id-Synchronisation-Configuration-Cell-ReconfRqst,
	id-Synchronisation-Configuration-Cell-SetupRqst,
	id-SyncCase,
	id-SyncCaseIndicatorItem-Cell-SetupRqstTDD-PSCH,
	id-SyncFrameNumber,
	id-SynchronisationReportType,
	id-SynchronisationReportCharacteristics,
	id-SyncReportType-CellSyncReprtTDD,
	id-T-Cell,
	id-TargetCommunicationControlPortID,
	id-Transmission-Gap-Pattern-Sequence-Information,
	id-TimeSlotConfigurationList-Cell-ReconfRqstTDD,
	id-TimeSlotConfigurationList-Cell-SetupRqstTDD,
	id-timeslotInfo-CellSyncInitiationRqstTDD,
	id-TimeslotISCPInfo,
	id-TimingAdvanceApplied,
	id-TnlQos,
	id-TransmissionDiversityApplied,
	id-transportlayeraddress,
	id-Tstd-indicator,
	id-UARFCNforNt,
	id-UARFCNforNd,
	id-UARFCNforNu,
	id-UE-Support-of-non-rectangular-resource-allocation,
	id-UL-CCTrCH-InformationAddList-RL-ReconfPrepTDD,
	id-UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD,
	id-UL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD,
	id-UL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD,
	id-UL-CCTrCH-InformationItem-RL-SetupRqstTDD,
	id-UL-CCTrCH-InformationList-RL-AdditionRqstTDD,
	id-UL-CCTrCH-InformationList-RL-SetupRqstTDD,
	id-UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD,
	id-UL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD,
	id-UL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD,
	id-UL-DPCH-InformationAddListIE-RL-ReconfPrepTDD,
	id-UL-DPCH-InformationItem-RL-AdditionRqstTDD,
	id-UL-DPCH-InformationList-RL-SetupRqstTDD,
	id-UL-DPCH-InformationModify-AddListIE-RL-ReconfPrepTDD,
	id-UL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD,
	id-UL-DPCH-InformationModify-ModifyListIE-RL-ReconfPrepTDD,
	id-UL-DPCH-Information-RL-ReconfPrepFDD,
	id-UL-DPCH-Information-RL-ReconfRqstFDD,
	id-UL-DPCH-Information-RL-SetupRqstFDD,
	id-UL-DPDCH-Indicator-For-E-DCH-Operation,
	id-Unsuccessful-cell-InformationRespItem-SyncAdjustmntFailureTDD,
	id-Unsuccessful-PDSCHSetItem-PSCH-ReconfFailureTDD,
	id-Unsuccessful-PUSCHSetItem-PSCH-ReconfFailureTDD,
	id-Unsuccessful-RL-InformationRespItem-RL-AdditionFailureFDD,
	id-Unsuccessful-RL-InformationRespItem-RL-SetupFailureFDD,
	id-Unsuccessful-RL-InformationResp-RL-AdditionFailureTDD,
	id-Unsuccessful-RL-InformationResp-RL-SetupFailureTDD,
	id-USCH-Information-Add,
	id-USCH-Information-DeleteList-RL-ReconfPrepTDD,
	id-USCH-Information-ModifyList-RL-ReconfPrepTDD,
	id-USCH-InformationResponse,
	id-USCH-Information,
	id-USCH-RearrangeList-Bearer-RearrangeInd,
	id-DL-DPCH-LCR-Information-RL-SetupRqstTDD,
	id-DwPCH-LCR-Information	,
	id-DwPCH-LCR-InformationList-AuditRsp,
	id-DwPCH-LCR-Information-Cell-SetupRqstTDD,
	id-DwPCH-LCR-Information-Cell-ReconfRqstTDD,
	id-DwPCH-LCR-Information-ResourceStatusInd,
	id-maxFACH-Power-LCR-CTCH-SetupRqstTDD,
	id-maxFACH-Power-LCR-CTCH-ReconfRqstTDD,
	id-FPACH-LCR-Information,
	id-FPACH-LCR-Information-AuditRsp,
	id-FPACH-LCR-InformationList-AuditRsp,
	id-FPACH-LCR-InformationList-ResourceStatusInd,
	id-FPACH-LCR-Parameters-CTCH-SetupRqstTDD, 
	id-FPACH-LCR-Parameters-CTCH-ReconfRqstTDD,
	id-PCCPCH-LCR-Information-Cell-SetupRqstTDD,
	id-PCH-Power-LCR-CTCH-SetupRqstTDD,
	id-PCH-Power-LCR-CTCH-ReconfRqstTDD,
	id-PICH-LCR-Parameters-CTCH-SetupRqstTDD,
	id-PRACH-LCR-ParametersList-CTCH-SetupRqstTDD, 
	id-RL-InformationResponse-LCR-RL-SetupRspTDD	,
	id-Secondary-CCPCH-LCR-parameterList-CTCH-SetupRqstTDD,
	id-TimeSlot,
	id-TimeSlotConfigurationList-LCR-Cell-ReconfRqstTDD,
	id-TimeSlotConfigurationList-LCR-Cell-SetupRqstTDD,
	id-TimeslotISCP-LCR-InfoList-RL-SetupRqstTDD,
	id-TimeSlotLCR-CM-Rqst,
	id-UL-DPCH-LCR-Information-RL-SetupRqstTDD,
	id-DL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD,
	id-UL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD,
	id-TimeslotISCP-InformationList-LCR-RL-AdditionRqstTDD,
	id-DL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD,
	id-DL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD,
	id-DL-Timeslot-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD,
	id-TimeslotISCPInfoList-LCR-DL-PC-RqstTDD,
	id-UL-DPCH-LCR-InformationAddListIE-RL-ReconfPrepTDD,
	id-UL-DPCH-LCR-InformationModify-AddList,
	id-UL-TimeslotLCR-Information-RL-ReconfPrepTDD,
	id-UL-SIRTarget,
	id-PDSCH-AddInformation-LCR-PSCH-ReconfRqst,
	id-PDSCH-AddInformation-LCR-AddListIE-PSCH-ReconfRqst,
	id-PDSCH-ModifyInformation-LCR-PSCH-ReconfRqst,
	id-PDSCH-ModifyInformation-LCR-ModifyListIE-PSCH-ReconfRqst,
	id-PUSCH-AddInformation-LCR-PSCH-ReconfRqst,
	id-PUSCH-AddInformation-LCR-AddListIE-PSCH-ReconfRqst,
	id-PUSCH-ModifyInformation-LCR-PSCH-ReconfRqst,
	id-PUSCH-ModifyInformation-LCR-ModifyListIE-PSCH-ReconfRqst,
	id-PUSCH-Info-DM-Rqst,
	id-PUSCH-Info-DM-Rsp,
	id-PUSCH-Info-DM-Rprt,
	id-RL-InformationResponse-LCR-RL-AdditionRspTDD,
	id-IPDLParameter-Information-LCR-Cell-SetupRqstTDD,
	id-IPDLParameter-Information-LCR-Cell-ReconfRqstTDD,
	id-HS-PDSCH-HS-SCCH-E-AGCH-E-RGCH-E-HICH-MaxPower-PSCH-ReconfRqst,
	id-HS-PDSCH-HS-SCCH-ScramblingCode-PSCH-ReconfRqst,
	id-HS-PDSCH-FDD-Code-Information-PSCH-ReconfRqst,
	id-HS-SCCH-FDD-Code-Information-PSCH-ReconfRqst,
	id-HS-PDSCH-TDD-Information-PSCH-ReconfRqst,
	id-Add-To-HS-SCCH-Resource-Pool-PSCH-ReconfRqst,
	id-Modify-HS-SCCH-Resource-Pool-PSCH-ReconfRqst,
	id-Delete-From-HS-SCCH-Resource-Pool-PSCH-ReconfRqst,
	id-SYNCDlCodeId-TransInitLCR-CellSyncInitiationRqstTDD,
	id-SYNCDlCodeId-MeasureInitLCR-CellSyncInitiationRqstTDD,
	id-SYNCDlCodeIdTransReconfInfoLCR-CellSyncReconfRqstTDD,
	id-SYNCDlCodeIdMeasReconfigurationLCR-CellSyncReconfRqstTDD,
	id-SYNCDlCodeIdMeasInfoList-CellSyncReconfRqstTDD,
	id-SyncDLCodeIdsMeasInfoList-CellSyncReprtTDD,
	id-NSubCyclesPerCyclePeriod-CellSyncReconfRqstTDD,
	id-DwPCH-Power,
	id-AccumulatedClockupdate-CellSyncReprtTDD,
	id-HSDPA-Capability,
	id-HSDSCH-FDD-Information,
	id-HSDSCH-Common-System-InformationFDD,
	id-HSDSCH-Common-System-Information-ResponseFDD,
	id-HSDSCH-FDD-Information-Response,
	id-HSDSCH-Information-to-Modify,
	id-HSDSCH-Information-to-Modify-Unsynchronised,
	id-HSDSCH-MACdFlows-to-Add,
	id-HSDSCH-MACdFlows-to-Delete,
	id-HSDSCH-Paging-System-InformationFDD,
	id-HSDSCH-Paging-System-Information-ResponseFDD,
	id-HSDSCH-RearrangeList-Bearer-RearrangeInd,
	id-HSDSCH-Resources-Information-AuditRsp,
	id-HSDSCH-Resources-Information-ResourceStatusInd,
	id-HSDSCH-RNTI,
	id-HSDSCH-TDD-Information,
	id-HSDSCH-TDD-Information-Response,
	id-HSPDSCH-RL-ID,
	id-HSSICH-Info-DM-Rprt,
	id-HSSICH-Info-DM-Rqst,
	id-HSSICH-Info-DM-Rsp,
	id-PrimCCPCH-RSCP-DL-PC-RqstTDD,
	id-HSDSCH-FDD-Update-Information,
	id-HSDSCH-TDD-Update-Information,
	id-UL-Synchronisation-Parameters-LCR,
	id-DL-DPCH-TimeSlotFormat-LCR-ModifyItem-RL-ReconfPrepTDD,
	id-UL-DPCH-TimeSlotFormat-LCR-ModifyItem-RL-ReconfPrepTDD,
	id-CCTrCH-Maximum-DL-Power-RL-SetupRqstTDD,
	id-CCTrCH-Minimum-DL-Power-RL-SetupRqstTDD,
	id-CCTrCH-Maximum-DL-Power-RL-AdditionRqstTDD,
	id-CCTrCH-Minimum-DL-Power-RL-AdditionRqstTDD,
	id-CCTrCH-Maximum-DL-Power-InformationAdd-RL-ReconfPrepTDD,
	id-CCTrCH-Minimum-DL-Power-InformationAdd-RL-ReconfPrepTDD, 
	id-CCTrCH-Maximum-DL-Power-InformationModify-RL-ReconfPrepTDD,
	id-CCTrCH-Minimum-DL-Power-InformationModify-RL-ReconfPrepTDD,
	id-Maximum-DL-Power-Modify-LCR-InformationModify-RL-ReconfPrepTDD,
	id-Minimum-DL-Power-Modify-LCR-InformationModify-RL-ReconfPrepTDD,
	id-DL-DPCH-LCR-InformationModify-ModifyList-RL-ReconfRqstTDD,
	id-CCTrCH-Maximum-DL-Power-InformationModify-RL-ReconfRqstTDD,
	id-CCTrCH-Minimum-DL-Power-InformationModify-RL-ReconfRqstTDD,
	id-TDD-TPC-UplinkStepSize-LCR-RL-SetupRqstTDD,
	id-TDD-TPC-UplinkStepSize-LCR-RL-AdditionRqstTDD,
	id-TDD-TPC-DownlinkStepSize-RL-AdditionRqstTDD,
	id-TDD-TPC-UplinkStepSize-InformationAdd-LCR-RL-ReconfPrepTDD,
	id-TDD-TPC-UplinkStepSize-InformationModify-LCR-RL-ReconfPrepTDD,
	id-TDD-TPC-DownlinkStepSize-InformationModify-RL-ReconfPrepTDD,
	id-TDD-TPC-DownlinkStepSize-InformationAdd-RL-ReconfPrepTDD,
	id-TimeslotISCP-LCR-InfoList-RL-ReconfPrepTDD,
	id-TimingAdjustmentValueLCR,
	id-PrimaryCCPCH-RSCP-Delta,
	id-Maximum-Target-ReceivedTotalWideBandPower,
	id-multiple-DedicatedMeasurementValueList-TDD-DM-Rsp,
	id-multiple-DedicatedMeasurementValueList-LCR-TDD-DM-Rsp,
	id-SynchronisationIndicator,
	id-Reference-ReceivedTotalWideBandPower,
	id-Reference-ReceivedTotalWideBandPowerReporting,
	id-Reference-ReceivedTotalWideBandPowerSupportIndicator,
	id-Maximum-Target-ReceivedTotalWideBandPower-LCR,
	id-multiple-PUSCH-InfoList-DM-Rsp,
	id-multiple-PUSCH-InfoList-DM-Rprt,
	id-Target-NonServing-EDCH-To-Total-EDCH-Power-Ratio,
	id-multiple-HSSICHMeasurementValueList-TDD-DM-Rsp,
	id-PCCPCH-768-Information-Cell-SetupRqstTDD,
	id-SCH-768-Information-Cell-SetupRqstTDD,
	id-SCH-768-Information-Cell-ReconfRqstTDD,
	id-PCCPCH-768-Information-Cell-ReconfRqstTDD,
	id-P-CCPCH-768-Information-AuditRsp,
	id-PICH-768-Information-AuditRsp,
	id-PRACH-768-InformationList-AuditRsp,
	id-SCH-768-Information-AuditRsp,
	id-MICH-768-Information-AuditRsp,
	id-CommonPhysicalChannelID768-CommonTrChDeletionReq,
	id-MICH-768-Parameters-CTCH-ReconfRqstTDD,
	id-PICH-768-Parameters-CTCH-SetupRqstTDD,
	id-PICH-768-Parameters-CTCH-ReconfRqstTDD,
	id-PRACH-768-Parameters-CTCH-SetupRqstTDD,
	id-S-CCPCH-768-InformationList-AuditRsp,
	id-S-CCPCH-768-Information-AuditRsp,
	id-S-CCPCH-768-Parameters-CTCH-SetupRqstTDD,
	id-S-CCPCH-768-Parameters-CTCH-ReconfRqstTDD,
	id-S-CCPCH-768-Information-ResourceStatusInd,
	id-P-CCPCH-768-Information-ResourceStatusInd,
	id-PICH-768-Information-ResourceStatusInd,
	id-PRACH-768-InformationList-ResourceStatusInd,
	id-SCH-768-Information-ResourceStatusInd,
	id-MICH-768-Information-ResourceStatusInd,
	id-S-CCPCH-768-InformationList-ResourceStatusInd,
	id-PRACH-768-Information,
	id-UL-DPCH-768-Information-RL-SetupRqstTDD,
	id-DL-DPCH-768-Information-RL-SetupRqstTDD,
	id-DL-DPCH-InformationItem-768-RL-AdditionRqstTDD,
	id-UL-DPCH-InformationItem-768-RL-AdditionRqstTDD,
	id-UL-DPCH-768-InformationAddItemIE-RL-ReconfPrepTDD,
	id-UL-DPCH-768-InformationAddListIE-RL-ReconfPrepTDD,
	id-UL-DPCH-768-InformationModify-AddItem,
	id-UL-DPCH-768-InformationModify-AddList,
	id-UL-Timeslot768-Information-RL-ReconfPrepTDD,
	id-DL-DPCH-768-InformationAddItem-RL-ReconfPrepTDD,
	id-DL-DPCH-768-InformationAddList-RL-ReconfPrepTDD,
	id-DL-DPCH-768-InformationModify-AddItem-RL-ReconfPrepTDD,
	id-DL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD,
	id-DL-Timeslot-768-InformationModify-ModifyList-RL-ReconfPrepTDD,
	id-DPCH-ID768-DM-Rqst,
	id-multiple-DedicatedMeasurementValueList-768-TDD-DM-Rsp,
	id-DPCH-ID768-DM-Rsp,
	id-DPCH-ID768-DM-Rprt,
	id-PDSCH-AddInformation-768-PSCH-ReconfRqst,
	id-PDSCH-ModifyInformation-768-PSCH-ReconfRqst,
	id-PUSCH-AddInformation-768-PSCH-ReconfRqst,
	id-PUSCH-ModifyInformation-768-PSCH-ReconfRqst,
	id-dL-HS-PDSCH-Timeslot-Information-768-PSCH-ReconfRqst,
	id-hS-SCCH-Information-768-PSCH-ReconfRqst,
	id-hS-SCCH-InformationModify-768-PSCH-ReconfRqst,
	id-tFCI-Presence,
	id-E-RUCCH-InformationList-AuditRsp,
	id-E-RUCCH-InformationList-ResourceStatusInd,
	id-E-RUCCH-Information,
	id-E-DCH-Information,
	id-E-DCH-Information-Response,
	id-E-DCH-Information-Reconfig,
	id-E-PUCH-Information-PSCH-ReconfRqst,
	id-Add-To-E-AGCH-Resource-Pool-PSCH-ReconfRqst,
	id-Modify-E-AGCH-Resource-Pool-PSCH-ReconfRqst,
	id-Delete-From-E-AGCH-Resource-Pool-PSCH-ReconfRqst,
	id-E-HICH-Information-PSCH-ReconfRqst,
	id-E-DCH-TDD-CapacityConsumptionLaw,
	id-E-HICH-TimeOffset,
	id-Maximum-Generated-ReceivedTotalWideBandPowerInOtherCells,
	id-E-DCH-Serving-RL-ID,
	id-E-RUCCH-768-InformationList-AuditRsp,
	id-E-RUCCH-768-InformationList-ResourceStatusInd,
	id-E-RUCCH-768-Information,
	id-E-DCH-768-Information,
	id-E-DCH-768-Information-Reconfig,
	id-E-PUCH-Information-768-PSCH-ReconfRqst,
	id-Add-To-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst,
	id-Modify-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst,
	id-E-HICH-Information-768-PSCH-ReconfRqst,
	id-RTWP-ReportingIndicator,
	id-RTWP-CellPortion-ReportingIndicator,
	id-Received-Scheduled-EDCH-Power-Share-Value,
	id-Received-Scheduled-EDCH-Power-Share-For-CellPortion-Value,
	id-Received-Scheduled-EDCH-Power-Share,
	id-Received-Scheduled-EDCH-Power-Share-For-CellPortion,
	id-ueCapability-Info,
	id-MAChs-ResetIndicator,
	id-SYNC-UL-Partition-LCR,
	id-E-DCH-LCR-Information,
	id-E-DCH-LCR-Information-Reconfig,
	id-E-PUCH-Information-LCR-PSCH-ReconfRqst,
	id-Add-To-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst,
	id-Modify-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst,
	id-Add-To-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst,
	id-Modify-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst,
	id-Delete-From-E-HICH-Resource-Pool-PSCH-ReconfRqst,
	id-E-HICH-TimeOffsetLCR,
	id-HSDSCH-MACdPDU-SizeCapability,
	id-ModulationPO-MBSFN,
	id-Secondary-CCPCH-SlotFormat-Extended,
	id-MBSFN-Only-Mode-Indicator-Cell-SetupRqstTDD-LCR,
	id-Time-Slot-Parameter-ID,
	id-MBSFN-Only-Mode-Capability,
	id-MBSFN-Cell-ParameterID-Cell-SetupRqstTDD,
	id-MBSFN-Cell-ParameterID-Cell-ReconfRqstTDD,
	id-S-CCPCH-Modulation,
	id-TimeSlotConfigurationList-LCR-CTCH-SetupRqstTDD,
	id-Cell-Frequency-List-Information-LCR-MulFreq-AuditRsp,
	id-Cell-Frequency-List-InformationItem-LCR-MulFreq-AuditRsp, 
	id-Cell-Frequency-List-LCR-MulFreq-Cell-SetupRqstTDD,
	id-UARFCN-Adjustment,
	id-Cell-Frequency-List-Information-LCR-MulFreq-ResourceStatusInd,
	id-Cell-Frequency-List-InformationItem-LCR-MulFreq-ResourceStatusInd,
	id-UPPCHPositionLCR,
	id-UPPCH-LCR-Parameters-CTCH-ReconfRqstTDD,
	id-UPPCH-LCR-InformationList-AuditRsp,
	id-UPPCH-LCR-InformationItem-AuditRsp,
	id-UPPCH-LCR-InformationList-ResourceStatusInd,
	id-UPPCH-LCR-InformationItem-ResourceStatusInd,
	id-multipleFreq-dL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst,
	id-multipleFreq-HS-DSCH-Resources-InformationList-AuditRsp,
	id-multipleFreq-HS-DSCH-Resources-InformationList-ResourceStatusInd,
	id-UARFCNSpecificCauseList,id-Unsuccessful-UARFCNItem-PSCH-ReconfFailureTDD,
	id-MultipleFreq-DL-HS-PDSCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst,
	id-Extended-HS-SCCH-ID,
	id-Extended-HS-SICH-ID,
	id-HSSICH-InfoExt-DM-Rqst,
	id-Delete-From-HS-SCCH-Resource-PoolExt-PSCH-ReconfRqst,
	id-HS-SCCH-InformationExt-LCR-PSCH-ReconfRqst,
	id-HS-SCCH-InformationModifyExt-LCR-PSCH-ReconfRqst,
	id-PowerControlGAP,
	id-PowerControlGAP-For-CellFACHLCR,
	id-IdleIntervalInformation,
	id-MBSFN-SpecialTimeSlot-LCR,
	id-MultipleFreq-E-DCH-Resources-InformationList-AuditRsp,
	id-MultipleFreq-E-DCH-Resources-InformationList-ResourceStatusInd,
	id-MultipleFreq-E-PUCH-Timeslot-InformationList-LCR-PSCH-ReconfRqst,
	id-MultipleFreq-E-PUCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst,
	id-Extended-E-HICH-ID-TDD,
	id-E-DCH-MACdPDU-SizeCapability,
	id-E-HICH-TimeOffset-Extension,
	id-MultipleFreq-E-HICH-TimeOffsetLCR,
	id-PLCCH-parameters,
	id-E-RUCCH-parameters,
	id-E-RUCCH-768-parameters,
	id-HS-Cause,
	id-E-Cause,
	id-AdditionalTimeSlotListLCR,
	id-AdditionalMeasurementValueList,
	id-HSDSCH-Paging-System-InformationLCR,
	id-HSDSCH-Paging-System-Information-ResponseLCR,
	id-HSDSCH-Common-System-InformationLCR,
	id-HSDSCH-Common-System-Information-ResponseLCR,
	id-Paging-MACFlows-to-DeleteLCR,
	id-Enhanced-UE-DRX-CapabilityLCR,
	id-Enhanced-UE-DRX-InformationLCR,
	id-Common-EDCH-MACdFlows-to-DeleteLCR,
	id-Common-EDCH-System-InformationLCR,
	id-Common-EDCH-System-Information-ResponseLCR,
	id-Common-MACFlows-to-DeleteLCR,
	id-Common-UL-MACFlows-to-DeleteLCR,
	id-HSDSCH-PreconfigurationSetup,
	id-HSDSCH-PreconfigurationInfo,
	id-NoOfTargetCellHS-SCCH-Order,
	id-EnhancedHSServingCC-Abort,
	id-GANSS-Time-ID,
	id-Additional-HS-Cell-Information-RL-Setup,
	id-Additional-HS-Cell-Information-Response,
	id-Additional-HS-Cell-Information-RL-Addition,
	id-Additional-HS-Cell-Change-Information-Response,
	id-Additional-HS-Cell-Information-RL-Reconf-Prep,
	id-Additional-HS-Cell-Information-RL-Reconf-Req,
	id-Additional-HS-Cell-Information-RL-Param-Upd,
	id-Multi-Cell-Capability-Info,
	id-MinimumReducedE-DPDCH-GainFactor,
	id-IMB-Parameters,
	id-E-RNTI,
	id-E-DCH-Semi-PersistentScheduling-Information-LCR,
	id-HS-DSCH-Semi-PersistentScheduling-Information-LCR,
	id-Add-To-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst,
	id-Modify-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst,
	id-Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst,
	id-Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext,
	id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR,
	id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR,
	id-HSSICH-ReferenceSignal-InformationLCR,
	id-UE-Selected-MBMS-Service-Information, 
	id-HSSICH-ReferenceSignal-InformationModifyLCR,
	id-TimeSlotMeasurementValueListLCR,
	id-MIMO-Power-Offset-For-S-CPICH-Capability,
	id-MIMO-PilotConfigurationExtension,
	id-TxDiversityOnDLControlChannelsByMIMOUECapability,
	id-UE-AggregateMaximumBitRate,
	id-Single-Stream-MIMO-Capability,
	id-ActivationInformation, 
	id-Cell-Capability-Container, 
	id-DormantModeIndicator, 
	id-Additional-EDCH-Cell-Information-RL-Setup-Req,
	id-Additional-EDCH-Cell-Information-Response,
	id-Additional-EDCH-Cell-Information-RL-Add-Req,
	id-Additional-EDCH-Cell-Information-Response-RL-Add,
	id-Additional-EDCH-Cell-Information-RL-Reconf-Prep,
	id-Additional-EDCH-Cell-Information-RL-Reconf-Req,
	id-Additional-EDCH-Cell-Information-Bearer-Rearrangement,
	id-Additional-EDCH-Cell-Information-RL-Param-Upd,
	id-Max-RTWP-perUARFCN-Information-LCR-PSCH-ReconfRqst,
	id-E-HICH-TimeOffset-ReconfFailureTDD,
	id-Common-System-Information-ResponseLCR,
	id-TS0-CapabilityLCR,
	id-HSSCCH-TPC-StepSize,
	id-Out-of-Sychronization-Window, 
	id-DCH-MeasurementOccasion-Information,
	id-Additional-EDCH-Cell-Information-ResponseRLReconf, 
	id-PrecodingWeightSetRestriction,
	id-HSDSCH-RNTI-For-FACH,
	id-E-RNTI-For-FACH,
	id-Treset-Usage-Indicator,
	id-Non-Serving-RL-Preconfig-Info,
	id-Non-Serving-RL-Preconfig-Setup,
	id-Non-Serving-RL-Preconfig-Removal,
	id-Cell-Capability-Container-TDD-LCR,
	id-Multi-Carrier-EDCH-Setup,
	id-Multi-Carrier-EDCH-Reconfigure,
	id-Multi-Carrier-EDCH-Response,
	id-MU-MIMO-Capability-ContainerLCR,
	id-MU-MIMO-InformationLCR,
	id-MU-MIMO-Information-Response,
	id-MU-MIMO-Information-To-ReconfigureLCR,
	id-Adaptive-Special-Burst-Power-CapabilityLCR,
	id-Usefulness-Of-Battery-Optimization,
	id-In-Sync-Information-LCR,
	id-ERNTI-Release-Status,
	id-Max-RTWP-perCellPortion-InformationList-LCR-PSCH-ReconfRqst,
	id-CPC-RecoveryReport,
	id-UL-CLTD-Information,
	id-UL-CLTD-Information-Reconf,
	id-UL-CLTD-State-Update-Information,
	id-FTPICH-Information,
	id-FTPICH-Information-Reconf,
	id-Further-Enhanced-UE-DRX-InformationFDD,
	id-Common-E-RGCH-Operation-Indicator,
	id-Common-E-RGCH-InfoFDD,
	id-DCH-ENH-Information,
	id-DCH-ENH-Information-Reconf,
	id-BCH-Parameters,
	id-BCH-Parameters-CTCH-SetupRsp,
	id-BCH-Parameters-CTCH-ReconfRqstFDD,
	id-BCH-mappedOnSCCPCH-Indication,
	id-Radio-Links-without-DPCH-FDPCH-Indication,
	id-UL-DPCCH2-Information,
	id-UL-DPCCH2-Information-Reconf,
	id-UE-Measurement-Forwarding,
	id-ActivationDelay,
	id-Downlink-TPC-enhancements-Information,
	id-Downlink-TPC-enhancements-Reconf,
	id-TPC-slot-position,
	id-Improved-Synchronized-Indicator,

	maxNrOfCCTrCHs,
	maxNrOfCellSyncBursts,
	maxNrOfCodes,
	maxNrOfDCHs,
	maxNrOfDLTSs,
	maxNrOfDLTSLCRs,
	maxNrOfDPCHs,
	maxNrOfDPCHsPerRL-1,
	maxNrOfDPCHLCRs,
	maxNrOfDPCHsLCRPerRL-1,
	maxNrOfDPCHs768,
	maxNrOfDPCHs768PerRL-1,
	maxNrOfDSCHs,
	maxNrOfFACHs,
	maxNrOfRLs,
	maxNrOfRLs-1,
	maxNrOfRLs-2,
	maxNrOfRLSets,
	maxNrOfPDSCHs,
	maxNrOfPUSCHs,
	maxNrOfPUSCHs-1,
	maxNrOfPRACHLCRs,
	maxNrOfPDSCHSets,
	maxNrOfPUSCHSets,
	maxNrOfReceptsPerSyncFrame,
	maxNrOfSCCPCHs,
	maxNrOfSCCPCHsinExt,
	maxNrOfSCCPCHLCRs,
	maxNrOfSCCPCHsLCRinExt,
	maxNrOfSCCPCHs768,
	maxNrOfULTSs,
	maxNrOfULTSLCRs,
	maxNrOfUSCHs,
	maxFACHCell,
	maxFPACHCell,
	maxRACHCell,
	maxPLCCHCell,
	maxPRACHCell,
	maxSCCPCHCell,
	maxSCCPCHCell768,
	maxSCCPCHCellinExt,
	maxSCCPCHCellinExtLCR,
	maxSCPICHCell,
	maxCellinNodeB,
	maxCCPinNodeB,
	maxCommunicationContext,
	maxLocalCellinNodeB,
	maxNrOfSlotFormatsPRACH,
	maxIB,
	maxIBSEG,
	maxNrOfCellPortionsPerCell,
	maxNrOfHSSCCHs,
	maxNrOfHSSICHs,
	maxNrOfHSSICHs-1,
	maxNrOfHSPDSCHs,
	maxNrOfHSPDSCHs768,
	maxNrOfSyncFramesLCR,
	maxNrOfReceptionsperSyncFrameLCR,
	maxNrOfSyncDLCodesLCR,
	maxNrOfMACdFlows,
	maxNrOfEDCHMACdFlows,
	maxE-RUCCHCell,
	maxNrOfE-PUCHSlots,
	maxNrOfEAGCHs,
	maxNrOfEAGCHCodes,
	maxNrOfE-PUCHSlotsLCR,
	maxNrOfEPUCHcodes,
	maxNrOfEHICHs,
	maxFrequencyinCell,
	maxFrequencyinCell-1,
	maxNrOfHSSCCHsinExt,
	maxNrOfHSSCCHsLCR,
	maxNrOfEAGCHsLCR,
	maxNrOfEHICHsLCR,
	maxNrOfHSDSCH-1,
	maxNrOfEDCH-1,
	maxNrOfULCarriersLCR-1,
	maxNrOfCellPortionsPerCellLCR

FROM NBAP-Constants;

-- **************************************************************
--
-- COMMON TRANSPORT CHANNEL SETUP REQUEST FDD
--
-- **************************************************************

CommonTransportChannelSetupRequestFDD ::= SEQUENCE {
	protocolIEs	ProtocolIE-Container	{{CommonTransportChannelSetupRequestFDD-IEs}},
	protocolExtensions	ProtocolExtensionContainer	{{CommonTransportChannelSetupRequestFDD-Extensions}}	OPTIONAL,
	...
}

CommonTransportChannelSetupRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CommonTransportChannelSetupRequestFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-C-ID												CRITICALITY reject		TYPE	C-ID				PRESENCE mandatory	}|
	{ ID	id-ConfigurationGenerationID						CRITICALITY reject		TYPE	ConfigurationGenerationID		PRESENCE mandatory	}|
	{ ID	id-CommonPhysicalChannelType-CTCH-SetupRqstFDD		CRITICALITY ignore		TYPE	CommonPhysicalChannelType-CTCH-SetupRqstFDD		PRESENCE 	mandatory	},
	...
}

CommonPhysicalChannelType-CTCH-SetupRqstFDD ::= CHOICE {
	secondary-CCPCH-parameters		Secondary-CCPCH-CTCH-SetupRqstFDD,
	pRACH-parameters				PRACH-CTCH-SetupRqstFDD,
	notUsed-pCPCHes-parameters		NULL,
	...
}

Secondary-CCPCH-CTCH-SetupRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID	CommonPhysicalChannelID,
	fdd-S-CCPCH-Offset	FDD-S-CCPCH-Offset,
	dl-ScramblingCode	DL-ScramblingCode	OPTIONAL,
	-- This IE shall be present if the PCH Parameters IE is not present
	fdd-DL-ChannelisationCodeNumber	FDD-DL-ChannelisationCodeNumber,
	tFCS	TFCS,
	secondary-CCPCH-SlotFormat	SecondaryCCPCH-SlotFormat,
	tFCI-Presence	TFCI-Presence	OPTIONAL,
	-- This IE shall be present if the Secondary CCPCH Slot Format is set to any of the values from 8 to 17 or if 3.84Mcps TDD IMB is used
	multiplexingPosition	MultiplexingPosition,
	powerOffsetInformation	PowerOffsetInformation-CTCH-SetupRqstFDD,
	sTTD-Indicator	STTD-Indicator,
	fACH-Parameters	FACH-ParametersList-CTCH-SetupRqstFDD		OPTIONAL,
	pCH-Parameters	PCH-Parameters-CTCH-SetupRqstFDD	OPTIONAL,
	iE-Extensions	ProtocolExtensionContainer  { { Secondary-CCPCHItem-CTCH-SetupRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

Secondary-CCPCHItem-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MICH-Parameters-CTCH-SetupRqstFDD			CRITICALITY reject	EXTENSION MICH-Parameters-CTCH-SetupRqstFDD		PRESENCE optional}|
	{ ID id-FDD-S-CCPCH-FrameOffset-CTCH-SetupRqstFDD	CRITICALITY reject	EXTENSION FDD-S-CCPCH-FrameOffset						PRESENCE optional}|
	{ ID id-ModulationPO-MBSFN							CRITICALITY reject	EXTENSION ModulationPO-MBSFN							PRESENCE optional}|
	{ ID id-Secondary-CCPCH-SlotFormat-Extended			CRITICALITY reject	EXTENSION Secondary-CCPCH-SlotFormat-Extended		PRESENCE optional}|
	{ ID id-IMB-Parameters								CRITICALITY reject	EXTENSION IMB-Parameters									PRESENCE optional}|
	{ ID id-BCH-Parameters								CRITICALITY reject	EXTENSION BCH-Parameters									PRESENCE optional},
	...
}

PowerOffsetInformation-CTCH-SetupRqstFDD ::= SEQUENCE {
	pO1-ForTFCI-Bits						PowerOffset,
	pO3-ForPilotBits						PowerOffset,
	iE-Extensions							ProtocolExtensionContainer { { PowerOffsetInformation-CTCH-SetupRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

PowerOffsetInformation-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

FACH-ParametersList-CTCH-SetupRqstFDD ::= ProtocolIE-Single-Container {{ FACH-ParametersListIEs-CTCH-SetupRqstFDD }}

FACH-ParametersListIEs-CTCH-SetupRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-FACH-ParametersListIE-CTCH-SetupRqstFDD   CRITICALITY reject	TYPE FACH-ParametersListIE-CTCH-SetupRqstFDD	PRESENCE mandatory }
}

FACH-ParametersListIE-CTCH-SetupRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfFACHs)) OF FACH-ParametersItem-CTCH-SetupRqstFDD

FACH-ParametersItem-CTCH-SetupRqstFDD ::= SEQUENCE {
	commonTransportChannelID			CommonTransportChannelID,
	transportFormatSet					TransportFormatSet,
	toAWS								ToAWS,
	toAWE								ToAWE,
	maxFACH-Power						DL-Power,
	iE-Extensions						ProtocolExtensionContainer  { { FACH-ParametersItem-CTCH-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

FACH-ParametersItem-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-bindingID						CRITICALITY	ignore		EXTENSION 	BindingID			PRESENCE optional	}|
	{ ID	id-transportlayeraddress			CRITICALITY	ignore		EXTENSION 	TransportLayerAddress		PRESENCE optional	}|
	{ ID	id-TnlQos							CRITICALITY ignore		EXTENSION	TnlQos				PRESENCE optional	}|
	{ ID	id-BroadcastReference				CRITICALITY	ignore		EXTENSION	BroadcastReference						PRESENCE optional	}|
	{ ID	id-IPMulticastIndication			CRITICALITY ignore		EXTENSION	IPMulticastIndication		PRESENCE optional	},
	...
}

PCH-Parameters-CTCH-SetupRqstFDD ::= ProtocolIE-Single-Container {{ PCH-ParametersIE-CTCH-SetupRqstFDD }}

PCH-ParametersIE-CTCH-SetupRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-PCH-ParametersItem-CTCH-SetupRqstFDD   CRITICALITY reject	TYPE PCH-ParametersItem-CTCH-SetupRqstFDD	PRESENCE mandatory }
}

PCH-ParametersItem-CTCH-SetupRqstFDD ::= SEQUENCE {
	commonTransportChannelID			CommonTransportChannelID,
	transportFormatSet					TransportFormatSet,
	toAWS								ToAWS,
	toAWE								ToAWE,	
	pCH-Power							DL-Power,
	pICH-Parameters						PICH-Parameters-CTCH-SetupRqstFDD,
	iE-Extensions						ProtocolExtensionContainer  { { PCH-ParametersItem-CTCH-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

PCH-ParametersItem-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-bindingID						CRITICALITY ignore		EXTENSION 	BindingID		PRESENCE optional	}|
	{ ID	id-transportlayeraddress			CRITICALITY ignore		EXTENSION 	TransportLayerAddress	PRESENCE optional	}|
	{ ID	id-TnlQos							CRITICALITY ignore		EXTENSION	TnlQos			PRESENCE optional	},
	...
}

PICH-Parameters-CTCH-SetupRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID						CommonPhysicalChannelID,
	fdd-dl-ChannelisationCodeNumber				FDD-DL-ChannelisationCodeNumber,
	pICH-Power									PICH-Power,
	pICH-Mode									PICH-Mode,	
	sTTD-Indicator								STTD-Indicator,
	iE-Extensions								ProtocolExtensionContainer { { PICH-Parameters-CTCH-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

PICH-Parameters-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MICH-Parameters-CTCH-SetupRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID						CommonPhysicalChannelID,
	fdd-dl-ChannelisationCodeNumber				FDD-DL-ChannelisationCodeNumber,
	mICH-Power									PICH-Power,
	mICH-Mode									MICH-Mode,
	sTTD-Indicator								STTD-Indicator,
	iE-Extensions								ProtocolExtensionContainer { { MICH-Parameters-CTCH-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

MICH-Parameters-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PRACH-CTCH-SetupRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID	CommonPhysicalChannelID,
	scramblingCodeNumber	ScramblingCodeNumber,
	tFCS	TFCS,
	preambleSignatures	PreambleSignatures,
	allowedSlotFormatInformation	AllowedSlotFormatInformationList-CTCH-SetupRqstFDD,
	rACH-SubChannelNumbers	RACH-SubChannelNumbers,
	ul-punctureLimit	PunctureLimit,
	preambleThreshold	PreambleThreshold,
	rACH-Parameters	RACH-Parameters-CTCH-SetupRqstFDD,
	aICH-Parameters	AICH-Parameters-CTCH-SetupRqstFDD,
	iE-Extensions	ProtocolExtensionContainer { { PRACHItem-CTCH-SetupRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

PRACHItem-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

AllowedSlotFormatInformationList-CTCH-SetupRqstFDD ::= SEQUENCE (SIZE (1.. maxNrOfSlotFormatsPRACH)) OF AllowedSlotFormatInformationItem-CTCH-SetupRqstFDD

AllowedSlotFormatInformationItem-CTCH-SetupRqstFDD ::= SEQUENCE {
	rACHSlotFormat	RACH-SlotFormat,
	iE-Extensions	ProtocolExtensionContainer  { { AllowedSlotFormatInformationItem-CTCH-SetupRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

AllowedSlotFormatInformationItem-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RACH-Parameters-CTCH-SetupRqstFDD ::= ProtocolIE-Single-Container {{ RACH-ParametersIE-CTCH-SetupRqstFDD }}

RACH-ParametersIE-CTCH-SetupRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-RACH-ParametersItem-CTCH-SetupRqstFDD   CRITICALITY reject	TYPE RACH-ParametersItem-CTCH-SetupRqstFDD	PRESENCE mandatory }
}

RACH-ParametersItem-CTCH-SetupRqstFDD ::= SEQUENCE {
 	commonTransportChannelID					CommonTransportChannelID,
 	transportFormatSet							TransportFormatSet,
	iE-Extensions								ProtocolExtensionContainer  { { RACH-ParametersItem-CTCH-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
 }

RACH-ParametersItem-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-bindingID						CRITICALITY ignore		EXTENSION 	BindingID		PRESENCE optional	}|
	{ ID	id-transportlayeraddress			CRITICALITY ignore		EXTENSION 	TransportLayerAddress	PRESENCE optional	}|
	{ ID	id-TnlQos							CRITICALITY ignore		EXTENSION	TnlQos			PRESENCE optional	},
	...
}

AICH-Parameters-CTCH-SetupRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID						CommonPhysicalChannelID,
	aICH-TransmissionTiming						AICH-TransmissionTiming,
	fdd-dl-ChannelisationCodeNumber				FDD-DL-ChannelisationCodeNumber,
	aICH-Power									AICH-Power,
	sTTD-Indicator								STTD-Indicator,
	iE-Extensions								ProtocolExtensionContainer  { { AICH-Parameters-CTCH-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

AICH-Parameters-CTCH-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMMON TRANSPORT CHANNEL SETUP REQUEST TDD
--
-- **************************************************************

CommonTransportChannelSetupRequestTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CommonTransportChannelSetupRequestTDD-IEs}},
	protocolExtensions 		ProtocolExtensionContainer	{{CommonTransportChannelSetupRequestTDD-Extensions}}		OPTIONAL,
	...
}

CommonTransportChannelSetupRequestTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-C-ID											CRITICALITY reject	TYPE C-ID					PRESENCE mandatory	}|
	{ ID	id-ConfigurationGenerationID					CRITICALITY reject	TYPE ConfigurationGenerationID			PRESENCE mandatory	}|
	{ ID	id-CommonPhysicalChannelType-CTCH-SetupRqstTDD	CRITICALITY ignore	TYPE CommonPhysicalChannelType-CTCH-SetupRqstTDD		PRESENCE 	mandatory	},
	...
}

CommonTransportChannelSetupRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CommonPhysicalChannelType-CTCH-SetupRqstTDD ::= CHOICE {
	secondary-CCPCH-parameters					Secondary-CCPCH-CTCH-SetupRqstTDD,
	pRACH-parameters							PRACH-CTCH-SetupRqstTDD,
	...,
	extension-CommonPhysicalChannelType-CTCH-SetupRqstTDD	Extension-CommonPhysicalChannelType-CTCH-SetupRqstTDD
}

Extension-CommonPhysicalChannelType-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container {{ Extension-CommonPhysicalChannelType-CTCH-SetupRqstTDDIE }}

Extension-CommonPhysicalChannelType-CTCH-SetupRqstTDDIE NBAP-PROTOCOL-IES ::= {
	{ ID id-PLCCH-parameters			CRITICALITY ignore	TYPE PLCCH-parameters		PRESENCE mandatory }|
	{ ID id-E-RUCCH-parameters		CRITICALITY ignore	TYPE E-RUCCH-parameters		PRESENCE mandatory }|
	{ ID id-E-RUCCH-768-parameters	CRITICALITY ignore	TYPE E-RUCCH-768-parameters	PRESENCE mandatory },
	...
}

Secondary-CCPCH-CTCH-SetupRqstTDD ::= SEQUENCE {
	sCCPCH-CCTrCH-ID							CCTrCH-ID,	-- For DL CCTrCH supporting one or several Secondary CCPCHs
	tFCS										TFCS,		-- For DL CCTrCH supporting one or several Secondary CCPCHs
	tFCI-Coding									TFCI-Coding,
	punctureLimit								PunctureLimit,
	secondaryCCPCH-parameterList				Secondary-CCPCH-parameterList-CTCH-SetupRqstTDD,
	fACH-ParametersList							FACH-ParametersList-CTCH-SetupRqstTDD		OPTIONAL,
	pCH-Parameters								PCH-Parameters-CTCH-SetupRqstTDD			OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer	{{Secondary-CCPCHItem-CTCH-SetupRqstTDD-ExtIEs}}		OPTIONAL,
	...
}

Secondary-CCPCHItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Tstd-indicator									CRITICALITY reject	EXTENSION TSTD-Indicator				PRESENCE optional	}|
	{ ID id-MICH-Parameters-CTCH-SetupRqstTDD				CRITICALITY reject	EXTENSION MICH-Parameters-CTCH-SetupRqstTDD		PRESENCE optional	}|
	{ ID id-Additional-S-CCPCH-Parameters-CTCH-SetupRqstTDD	CRITICALITY reject	EXTENSION Secondary-CCPCH-parameterExtendedList-CTCH-SetupRqstTDD		PRESENCE optional	}|
	-- Applicable to 3.84Mcps TDD only, used when more than maxNrOfSCCPCHs SCCPCHs are to be established.
	{ ID id-Additional-S-CCPCH-LCR-Parameters-CTCH-SetupRqstTDD	CRITICALITY reject	EXTENSION Secondary-CCPCH-LCR-parameterExtendedList-CTCH-SetupRqstTDD		PRESENCE optional	}|
	-- Applicable to 1.28Mcps TDD only, used when more than maxNrOfSCCPCHLCRs SCCPCHs are to be established.
	{ ID id-S-CCPCH-768-Parameters-CTCH-SetupRqstTDD		CRITICALITY reject	EXTENSION Secondary-CCPCH-768-parameterList-CTCH-SetupRqstTDD		PRESENCE optional	}|
	{ ID id-S-CCPCH-Modulation								CRITICALITY reject	EXTENSION ModulationMBSFN								PRESENCE optional	}|	-- Applicable to 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD
	{ ID id-TimeSlotConfigurationList-LCR-CTCH-SetupRqstTDD	CRITICALITY reject	EXTENSION TimeSlotConfigurationList-LCR-CTCH-SetupRqstTDD		PRESENCE optional }|
	{ ID id-UARFCNforNt		CRITICALITY reject	EXTENSION UARFCN		PRESENCE optional },
	-- Applicable to 1.28Mcps TDD when using multiple frequencies. This IE indicates the frequency of Secondary Frequency on which SCCPCH to be set up
	...
}

Secondary-CCPCH-parameterList-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container {{ Secondary-CCPCH-parameterListIEs-CTCH-SetupRqstTDD }}

Secondary-CCPCH-parameterListIEs-CTCH-SetupRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-Secondary-CCPCH-parameterListIE-CTCH-SetupRqstTDD	CRITICALITY reject	TYPE Secondary-CCPCH-parameterListIE-CTCH-SetupRqstTDD		PRESENCE optional }|
	{ ID id-Secondary-CCPCH-LCR-parameterList-CTCH-SetupRqstTDD	CRITICALITY reject	TYPE Secondary-CCPCH-LCR-parameterList-CTCH-SetupRqstTDD	PRESENCE optional }
}

Secondary-CCPCH-parameterListIE-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHs)) OF Secondary-CCPCH-parameterItem-CTCH-SetupRqstTDD

Secondary-CCPCH-parameterItem-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID						CommonPhysicalChannelID,
	tdd-ChannelisationCode						TDD-ChannelisationCode,
	timeslot									TimeSlot,
	midambleShiftandBurstType					MidambleShiftAndBurstType,
	tdd-PhysicalChannelOffset					TDD-PhysicalChannelOffset,
	repetitionPeriod							RepetitionPeriod,
	repetitionLength							RepetitionLength,
	s-CCPCH-Power								DL-Power,
	iE-Extensions								ProtocolExtensionContainer { { Secondary-CCPCH-parameterItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

Secondary-CCPCH-parameterItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-tFCI-Presence						CRITICALITY notify	EXTENSION TFCI-Presence		PRESENCE optional},
	...
}

Secondary-CCPCH-LCR-parameterList-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHLCRs)) OF Secondary-CCPCH-LCR-parameterItem-CTCH-SetupRqstTDD

Secondary-CCPCH-LCR-parameterItem-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID						CommonPhysicalChannelID,
	tdd-ChannelisationCodeLCR					TDD-ChannelisationCodeLCR,
	timeslotLCR									TimeSlotLCR,
	midambleShiftLCR							MidambleShiftLCR,
	-- For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, NodeB shall ignore the contents of this IE.
	tdd-PhysicalChannelOffset					TDD-PhysicalChannelOffset,
	repetitionPeriod							RepetitionPeriod,
	repetitionLength							RepetitionLength,
	s-CCPCH-Power								DL-Power,
	s-CCPCH-TimeSlotFormat-LCR					TDD-DL-DPCH-TimeSlotFormat-LCR,
	iE-Extensions								ProtocolExtensionContainer { { Secondary-CCPCH-LCR-parameterItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

Secondary-CCPCH-LCR-parameterItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-MBSFN-SpecialTimeSlot-LCR			CRITICALITY ignore		EXTENSION	TimeslotLCR-Extension			PRESENCE optional },
	-- Only for 1.28 Mcps TDD MBSFN only mode, this IE indicates the MBSFN Special Time Slot (TS 25.221 [19]). The IE ”Time Slot LCR” shall be ignored if this IE appears
	...
}

Secondary-CCPCH-768-parameterList-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHs768)) OF Secondary-CCPCH-768-parameterItem-CTCH-SetupRqstTDD

Secondary-CCPCH-768-parameterItem-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID768					CommonPhysicalChannelID768,
	tdd-ChannelisationCode768					TDD-ChannelisationCode768,
	timeslot									TimeSlot,
	tFCI-Presence768							TFCI-Presence		OPTIONAL,
	midambleShiftandBurstType768				MidambleShiftAndBurstType768,
	tdd-PhysicalChannelOffset					TDD-PhysicalChannelOffset,
	repetitionPeriod							RepetitionPeriod,
	repetitionLength							RepetitionLength,
	s-CCPCH-Power								DL-Power,
	iE-Extensions								ProtocolExtensionContainer { { Secondary-CCPCH-parameterItem-768-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

Secondary-CCPCH-parameterItem-768-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

FACH-ParametersList-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container {{ FACH-ParametersListIEs-CTCH-SetupRqstTDD }}

FACH-ParametersListIEs-CTCH-SetupRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-FACH-ParametersListIE-CTCH-SetupRqstTDD   CRITICALITY reject	TYPE FACH-ParametersListIE-CTCH-SetupRqstTDD	PRESENCE mandatory }
}

FACH-ParametersListIE-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfFACHs)) OF FACH-ParametersItem-CTCH-SetupRqstTDD

FACH-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonTransportChannelID				CommonTransportChannelID,
	fACH-CCTrCH-ID							CCTrCH-ID,
	dl-TransportFormatSet					TransportFormatSet,
	toAWS									ToAWS,
	toAWE									ToAWE,
	iE-Extensions							ProtocolExtensionContainer  { { FACH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

FACH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-maxFACH-Power-LCR-CTCH-SetupRqstTDD	CRITICALITY	reject	EXTENSION DL-Power			PRESENCE optional	}|
	-- Applicable to 1.28Mcps TDD only
	{ ID	id-bindingID							CRITICALITY	ignore	EXTENSION BindingID			PRESENCE optional	}|
	-- Shall be ignored if bearer establishment with ALCAP.
	{ ID	id-transportlayeraddress				CRITICALITY	ignore	EXTENSION TransportLayerAddress	PRESENCE optional	}|
	-- Shall be ignored if bearer establishment with ALCAP.
	{ ID	id-TnlQos								CRITICALITY ignore	EXTENSION	TnlQos			PRESENCE optional	}|
	-- Shall be ignored if bearer establishment with ALCAP.
	{ ID	id-BroadcastReference					CRITICALITY	ignore	EXTENSION	BroadcastReference 	PRESENCE	optional	}|
	{ ID	id-IPMulticastIndication				CRITICALITY	ignore	EXTENSION	IPMulticastIndication	PRESENCE	optional	},
	...
}

PCH-Parameters-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container {{ PCH-ParametersIE-CTCH-SetupRqstTDD }}

PCH-ParametersIE-CTCH-SetupRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-PCH-ParametersItem-CTCH-SetupRqstTDD   CRITICALITY reject	TYPE PCH-ParametersItem-CTCH-SetupRqstTDD	PRESENCE mandatory }
}

PCH-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonTransportChannelID				CommonTransportChannelID,
	pCH-CCTrCH-ID							CCTrCH-ID,
	dl-TransportFormatSet					TransportFormatSet,	-- For the DL.
	toAWS									ToAWS,
	toAWE									ToAWE,
	pICH-Parameters							PICH-Parameters-CTCH-SetupRqstTDD,
	iE-Extensions							ProtocolExtensionContainer  { { PCH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PCH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-PCH-Power-LCR-CTCH-SetupRqstTDD	CRITICALITY reject	EXTENSION DL-Power	PRESENCE optional	}|
	{ ID id-bindingID	CRITICALITY ignore	EXTENSION BindingID	PRESENCE optional	}|
	-- Shall be ignored if bearer establishment with ALCAP.
	{ ID id-transportlayeraddress	CRITICALITY ignore	EXTENSION TransportLayerAddress	PRESENCE optional	}|
	-- Shall be ignored if bearer establishment with ALCAP.
	{ ID id-PICH-768-Parameters-CTCH-SetupRqstTDD	CRITICALITY reject	EXTENSION PICH-768-ParametersItem-CTCH-SetupRqstTDD	PRESENCE optional	}|
	{ ID id-TnlQos	CRITICALITY ignore	EXTENSION TnlQos	PRESENCE optional	},
	-- Shall be ignored if bearer establishment with ALCAP.
	...
}

PICH-Parameters-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container {{ PICH-ParametersIE-CTCH-SetupRqstTDD }}

PICH-ParametersIE-CTCH-SetupRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-PICH-ParametersItem-CTCH-SetupRqstTDD	CRITICALITY reject	TYPE PICH-ParametersItem-CTCH-SetupRqstTDD	PRESENCE optional }|
	{ ID id-PICH-LCR-Parameters-CTCH-SetupRqstTDD	CRITICALITY reject	TYPE PICH-LCR-Parameters-CTCH-SetupRqstTDD	PRESENCE optional }
}

PICH-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
 	tdd-ChannelisationCode					TDD-ChannelisationCode,
 	timeSlot  								TimeSlot,
	midambleshiftAndBurstType				MidambleShiftAndBurstType,
 	tdd-PhysicalChannelOffset				TDD-PhysicalChannelOffset,
 	repetitionPeriod						RepetitionPeriod,
 	repetitionLength						RepetitionLength,
 	pagingIndicatorLength					PagingIndicatorLength,
	pICH-Power								PICH-Power,
	iE-Extensions							ProtocolExtensionContainer  { { PICH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PICH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PICH-LCR-Parameters-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
 	tdd-ChannelisationCodeLCR				TDD-ChannelisationCodeLCR,
 	timeSlotLCR  							TimeSlotLCR,
	midambleShiftLCR						MidambleShiftLCR,
	tdd-PhysicalChannelOffset				TDD-PhysicalChannelOffset,
 	repetitionPeriod						RepetitionPeriod,
 	repetitionLength						RepetitionLength,
 	pagingIndicatorLength					PagingIndicatorLength,
	pICH-Power								PICH-Power,
	second-TDD-ChannelisationCodeLCR		TDD-ChannelisationCodeLCR,
	iE-Extensions							ProtocolExtensionContainer { { PICH-LCR-ParametersItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PICH-LCR-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-Tstd-indicator			CRITICALITY	reject		EXTENSION 	TSTD-Indicator		PRESENCE 	optional	},
	-- Applicable to 1.28 Mcps TDD only
	...
}

PICH-768-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID768				CommonPhysicalChannelID768,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	timeSlot  								TimeSlot,
	midambleshiftAndBurstType78				MidambleShiftAndBurstType768,
	tdd-PhysicalChannelOffset				TDD-PhysicalChannelOffset,
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	pagingIndicatorLength					PagingIndicatorLength,
	pICH-Power								PICH-Power,
	iE-Extensions							ProtocolExtensionContainer { { PICH-768-ParametersItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PICH-768-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


MICH-Parameters-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
	tdd-PhysicalChannelOffset				TDD-PhysicalChannelOffset,
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	notificationIndicatorLength				NotificationIndicatorLength,
	mICH-Power								PICH-Power,
	mICH-TDDOption-Specific-Parameters		MICH-TDDOption-Specific-Parameters-CTCH-SetupRqstTDD,
	iE-Extensions							ProtocolExtensionContainer { { MICH-Parameters-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

MICH-Parameters-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MICH-TDDOption-Specific-Parameters-CTCH-SetupRqstTDD ::= CHOICE {
	hCR-TDD									MICH-HCR-Parameters-CTCH-SetupRqstTDD,
	lCR-TDD									MICH-LCR-Parameters-CTCH-SetupRqstTDD,
	...,
	cHipRate768-TDD							MICH-768-Parameters-CTCH-SetupRqstTDD
}

MICH-HCR-Parameters-CTCH-SetupRqstTDD ::= SEQUENCE {
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	timeSlot								TimeSlot,
	midambleshiftAndBurstType				MidambleShiftAndBurstType,
	iE-Extensions							ProtocolExtensionContainer { { MICH-HCR-Parameters-CTCH-SetupRqstTDD-ExtIEs } }		OPTIONAL,
	...
}

MICH-HCR-Parameters-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MICH-LCR-Parameters-CTCH-SetupRqstTDD ::= SEQUENCE {
	tdd-ChannelisationCodeLCR				TDD-ChannelisationCodeLCR,
	timeSlotLCR								TimeSlotLCR,
	midambleShiftLCR						MidambleShiftLCR,
	-- For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, NodeB shall ignore the contents of this IE.
	second-TDD-ChannelisationCodeLCR		TDD-ChannelisationCodeLCR,
	tSTD-Indicator							TSTD-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { MICH-LCR-Parameters-CTCH-SetupRqstTDD-ExtIEs } }		OPTIONAL,
	...
}

MICH-LCR-Parameters-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-MBSFN-SpecialTimeSlot-LCR			CRITICALITY ignore		EXTENSION TimeslotLCR-Extension			PRESENCE optional },
	-- Only for 1.28 Mcps TDD MBSFN only mode, this IE indicates the MBSFN Special Time Slot (TS 25.221 [19]). The IE ”Time Slot LCR” shall be ignored if this IE appears
	...
}

MICH-768-Parameters-CTCH-SetupRqstTDD ::= SEQUENCE {
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	timeSlot								TimeSlot,
	midambleshiftAndBurstType768			MidambleShiftAndBurstType768,
	iE-Extensions							ProtocolExtensionContainer { { MICH-768-Parameters-CTCH-SetupRqstTDD-ExtIEs } }		OPTIONAL,
	...
}

MICH-768-Parameters-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TimeSlotConfigurationList-LCR-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..7)) OF TimeSlotConfigurationItem-LCR-CTCH-SetupRqstTDD

TimeSlotConfigurationItem-LCR-CTCH-SetupRqstTDD ::= SEQUENCE {
	timeslotLCR								TimeSlotLCR,
	timeslotLCR-Parameter-ID				CellParameterID,
	iE-Extensions							ProtocolExtensionContainer { { TimeSlotConfigurationItem-LCR-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

TimeSlotConfigurationItem-LCR-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Secondary-CCPCH-parameterExtendedList-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHsinExt)) OF Secondary-CCPCH-parameterItem-CTCH-SetupRqstTDD
	-- Applicable to 3.84Mcps TDD only, used when more than maxNrOfSCCPCHs SCCPCHs are to be established.

Secondary-CCPCH-LCR-parameterExtendedList-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHsLCRinExt)) OF Secondary-CCPCH-LCR-parameterItem-CTCH-SetupRqstTDD
	-- Applicable to 1.28Mcps TDD only, used when more than maxNrOfSCCPCHLCRs SCCPCHs are to be established.

PRACH-CTCH-SetupRqstTDD ::= SEQUENCE {
	pRACH-Parameters-CTCH-SetupRqstTDD			PRACH-Parameters-CTCH-SetupRqstTDD,
	iE-Extensions								ProtocolExtensionContainer  { { PRACH-CTCH-SetupRqstTDD-ExtIEs } }		OPTIONAL,
	...
}

PRACH-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-FPACH-LCR-Parameters-CTCH-SetupRqstTDD	CRITICALITY reject	EXTENSION FPACH-LCR-Parameters-CTCH-SetupRqstTDD	PRESENCE optional	}|
	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD
	{ ID id-PRACH-768-Parameters-CTCH-SetupRqstTDD	CRITICALITY reject	EXTENSION PRACH-768-ParametersItem-CTCH-SetupRqstTDD	PRESENCE optional	},
	...
}

PRACH-Parameters-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container {{ PRACH-ParametersIE-CTCH-SetupRqstTDD }}

PRACH-ParametersIE-CTCH-SetupRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-PRACH-ParametersItem-CTCH-SetupRqstTDD		CRITICALITY reject	TYPE PRACH-ParametersItem-CTCH-SetupRqstTDD		PRESENCE optional }|
	{ ID id-PRACH-LCR-ParametersList-CTCH-SetupRqstTDD	CRITICALITY reject	TYPE PRACH-LCR-ParametersList-CTCH-SetupRqstTDD	PRESENCE optional }
}


PRACH-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID						CommonPhysicalChannelID,
	tFCS										TFCS,
	timeslot									TimeSlot,
	tdd-ChannelisationCode						TDD-ChannelisationCode,
	maxPRACH-MidambleShifts						MaxPRACH-MidambleShifts,
	pRACH-Midamble 								PRACH-Midamble,
	rACH										RACH-Parameter-CTCH-SetupRqstTDD,
	iE-Extensions								ProtocolExtensionContainer  { { PRACH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PRACH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RACH-Parameter-CTCH-SetupRqstTDD ::= ProtocolIE-Single-Container {{ RACH-ParameterIE-CTCH-SetupRqstTDD }}

RACH-ParameterIE-CTCH-SetupRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-RACH-ParameterItem-CTCH-SetupRqstTDD   CRITICALITY reject	TYPE RACH-ParameterItem-CTCH-SetupRqstTDD	PRESENCE mandatory }
}

RACH-ParameterItem-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonTransportChannelID					CommonTransportChannelID,
	uL-TransportFormatSet						TransportFormatSet,	-- For the UL
	iE-Extensions								ProtocolExtensionContainer  { { RACH-ParameterItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

RACH-ParameterItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-bindingID					CRITICALITY ignore	EXTENSION BindingID					PRESENCE optional }|
		-- Shall be ignored if bearer establishment with ALCAP.
	{ ID id-transportlayeraddress		CRITICALITY ignore	EXTENSION TransportLayerAddress		PRESENCE optional }|
		-- Shall be ignored if bearer establishment with ALCAP.
	{ ID	id-TnlQos					CRITICALITY ignore	EXTENSION TnlQos					PRESENCE optional },
	-- Shall be ignored if bearer establishment with ALCAP.
	...
}

PRACH-LCR-ParametersList-CTCH-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfPRACHLCRs)) OF PRACH-LCR-ParametersItem-CTCH-SetupRqstTDD 

PRACH-LCR-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID						CommonPhysicalChannelID,
	tFCS										TFCS,
	timeslotLCR									TimeSlotLCR,
	tdd-ChannelisationCodeLCR					TDD-ChannelisationCodeLCR,
	midambleShiftLCR							MidambleShiftLCR,
	rACH										RACH-Parameter-CTCH-SetupRqstTDD,
	iE-Extensions								ProtocolExtensionContainer  { { PRACH-LCR-ParametersItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PRACH-LCR-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	 { ID id-UARFCNforNt	CRITICALITY reject		EXTENSION UARFCN		PRESENCE optional },
	-- Applicable to 1.28Mcps TDD when using multiple frequencies. This IE indicates the frequency of secondary on which PRACH to be set up.
	...
}

PRACH-768-ParametersItem-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID768					CommonPhysicalChannelID768,
	tFCS										TFCS,
	timeslot									TimeSlot,
	tdd-ChannelisationCode768					TDD-ChannelisationCode768,
	maxPRACH-MidambleShifts						MaxPRACH-MidambleShifts,
	pRACH-Midamble 								PRACH-Midamble,
	rACH										RACH-Parameter-CTCH-SetupRqstTDD,
	iE-Extensions								ProtocolExtensionContainer  { { PRACH-768-ParametersItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PRACH-768-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

FPACH-LCR-Parameters-CTCH-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID						CommonPhysicalChannelID,
 	tdd-ChannelisationCodeLCR					TDD-ChannelisationCodeLCR,
	timeslotLCR									TimeSlotLCR,
	midambleShiftLCR							MidambleShiftLCR,
	fPACH-Power									FPACH-Power,
	iE-Extensions								ProtocolExtensionContainer  { { FPACH-LCR-ParametersItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

FPACH-LCR-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UARFCNforNt		CRITICALITY reject		EXTENSION UARFCN		PRESENCE optional },
	--  Applicable to 1.28Mcps TDD when using multiple frequencies. This IE indicates the frequency of Secondary Frequency on which FPACH to be set up.
	...
}

PLCCH-parameters  ::= SEQUENCE {
	maxPowerPLCCH								DL-Power,
	commonPhysicalChannelID						CommonPhysicalChannelID,
 	tdd-ChannelisationCode						TDD-ChannelisationCode,
	timeslotLCR									TimeSlotLCR,
	midambleShiftLCR							MidambleShiftLCR,
	iE-Extensions								ProtocolExtensionContainer  { { PLCCH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PLCCH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-RUCCH-parameters  ::= SEQUENCE {
	commonPhysicalChannelID						CommonPhysicalChannelID,
	timeslot									TimeSlot,
	tdd-ChannelisationCode						TDD-ChannelisationCode,
	maxE-RUCCH-MidambleShifts					MaxPRACH-MidambleShifts,
	e-RUCCH-Midamble							PRACH-Midamble,
	iE-Extensions								ProtocolExtensionContainer  { { E-RUCCH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

E-RUCCH-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-RUCCH-768-parameters  ::= SEQUENCE {
	commonPhysicalChannelID768					CommonPhysicalChannelID768,
	timeslot									TimeSlot,
	tdd-ChannelisationCode768					TDD-ChannelisationCode768,
	maxE-RUCCH-MidambleShifts					MaxPRACH-MidambleShifts,
	e-RUCCH-Midamble							PRACH-Midamble,
	iE-Extensions								ProtocolExtensionContainer  { { E-RUCCH-768-ParametersItem-CTCH-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

E-RUCCH-768-ParametersItem-CTCH-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMMON TRANSPORT CHANNEL SETUP RESPONSE
--
-- **************************************************************

CommonTransportChannelSetupResponse ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CommonTransportChannelSetupResponse-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CommonTransportChannelSetupResponse-Extensions}}	OPTIONAL,
	...
}

CommonTransportChannelSetupResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-FACH-ParametersList-CTCH-SetupRsp	CRITICALITY ignore	TYPE FACH-CommonTransportChannel-InformationResponse		PRESENCE optional}|
	{ ID id-PCH-Parameters-CTCH-SetupRsp		CRITICALITY ignore	TYPE CommonTransportChannel-InformationResponse				PRESENCE optional}|
	{ ID id-RACH-Parameters-CTCH-SetupRsp		CRITICALITY ignore	TYPE CommonTransportChannel-InformationResponse				PRESENCE optional}|
	{ ID id-CriticalityDiagnostics				CRITICALITY ignore	TYPE CriticalityDiagnostics											PRESENCE optional}|
	{ ID id-BCH-Parameters-CTCH-SetupRsp		CRITICALITY ignore	TYPE CommonTransportChannel-InformationResponse				PRESENCE optional},
	...
}

CommonTransportChannelSetupResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

FACH-CommonTransportChannel-InformationResponse ::= SEQUENCE (SIZE (1..maxNrOfFACHs)) OF CommonTransportChannel-InformationResponse

-- **************************************************************
--
-- COMMON TRANSPORT CHANNEL SETUP FAILURE
--
-- **************************************************************

CommonTransportChannelSetupFailure ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CommonTransportChannelSetupFailure-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CommonTransportChannelSetupFailure-Extensions}}	OPTIONAL,
	...
}

CommonTransportChannelSetupFailure-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-Cause					CRITICALITY	ignore		TYPE	Cause						PRESENCE	mandatory	}|
	{ ID	id-CriticalityDiagnostics	CRITICALITY	ignore		TYPE	CriticalityDiagnostics		PRESENCE	optional		},
	...
}

CommonTransportChannelSetupFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST FDD
--
-- **************************************************************

CommonTransportChannelReconfigurationRequestFDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CommonTransportChannelReconfigurationRequestFDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CommonTransportChannelReconfigurationRequestFDD-Extensions}}		OPTIONAL,
	...
}

CommonTransportChannelReconfigurationRequestFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-C-ID											CRITICALITY reject	TYPE C-ID							PRESENCE mandatory }|
	{ ID id-ConfigurationGenerationID						CRITICALITY reject	TYPE ConfigurationGenerationID					PRESENCE mandatory }|
	{ ID id-CommonPhysicalChannelType-CTCH-ReconfRqstFDD	CRITICALITY reject	TYPE CommonPhysicalChannelType-CTCH-ReconfRqstFDD	PRESENCE mandatory },
	...
}

CommonTransportChannelReconfigurationRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CommonPhysicalChannelType-CTCH-ReconfRqstFDD ::= CHOICE {
	secondary-CCPCH-parameters		Secondary-CCPCHList-CTCH-ReconfRqstFDD,
	pRACH-parameters				PRACHList-CTCH-ReconfRqstFDD,
	notUsed-cPCH-parameters			NULL,
	...
}

Secondary-CCPCHList-CTCH-ReconfRqstFDD ::= SEQUENCE {
	fACH-ParametersList-CTCH-ReconfRqstFDD		FACH-ParametersList-CTCH-ReconfRqstFDD	OPTIONAL,
	pCH-Parameters-CTCH-ReconfRqstFDD			PCH-Parameters-CTCH-ReconfRqstFDD	OPTIONAL,
	pICH-Parameters-CTCH-ReconfRqstFDD			PICH-Parameters-CTCH-ReconfRqstFDD	OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { Secondary-CCPCH-CTCH-ReconfRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

Secondary-CCPCH-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MICH-Parameters-CTCH-ReconfRqstFDD		CRITICALITY reject	EXTENSION MICH-Parameters-CTCH-ReconfRqstFDD		PRESENCE optional}|
	{ ID id-BCH-Parameters-CTCH-ReconfRqstFDD		CRITICALITY ignore	EXTENSION BCH-Parameters-CTCH-ReconfRqstFDD			PRESENCE optional},
	...
}

FACH-ParametersList-CTCH-ReconfRqstFDD ::= ProtocolIE-Single-Container {{ FACH-ParametersListIEs-CTCH-ReconfRqstFDD }}

FACH-ParametersListIEs-CTCH-ReconfRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-FACH-ParametersListIE-CTCH-ReconfRqstFDD	CRITICALITY reject	TYPE FACH-ParametersListIE-CTCH-ReconfRqstFDD 	PRESENCE	mandatory }
}

FACH-ParametersListIE-CTCH-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxFACHCell)) OF FACH-ParametersItem-CTCH-ReconfRqstFDD

FACH-ParametersItem-CTCH-ReconfRqstFDD ::= SEQUENCE {
	commonTransportChannelID	CommonTransportChannelID,
	maxFACH-Power	DL-Power	OPTIONAL,
	toAWS	ToAWS	OPTIONAL,
	toAWE	ToAWE	OPTIONAL,
	iE-Extensions	ProtocolExtensionContainer  { { FACH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

FACH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-TnlQos			CRITICALITY ignore		EXTENSION TnlQos	PRESENCE optional },
	...
}

PCH-Parameters-CTCH-ReconfRqstFDD ::= ProtocolIE-Single-Container {{ PCH-ParametersIE-CTCH-ReconfRqstFDD }}

PCH-ParametersIE-CTCH-ReconfRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-PCH-ParametersItem-CTCH-ReconfRqstFDD	CRITICALITY reject	TYPE PCH-ParametersItem-CTCH-ReconfRqstFDD 	PRESENCE	mandatory }
}

PCH-ParametersItem-CTCH-ReconfRqstFDD ::= SEQUENCE {
	commonTransportChannelID	CommonTransportChannelID,
	pCH-Power	DL-Power	OPTIONAL,
	toAWS	ToAWS	OPTIONAL,
	toAWE	ToAWE	OPTIONAL,
	iE-Extensions	ProtocolExtensionContainer  { { PCH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

PCH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-TnlQos			CRITICALITY ignore		EXTENSION TnlQos	PRESENCE optional },
	...
}

PICH-Parameters-CTCH-ReconfRqstFDD ::= ProtocolIE-Single-Container {{ PICH-ParametersIE-CTCH-ReconfRqstFDD }}

PICH-ParametersIE-CTCH-ReconfRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-PICH-ParametersItem-CTCH-ReconfRqstFDD	CRITICALITY reject	TYPE PICH-ParametersItem-CTCH-ReconfRqstFDD 	PRESENCE	mandatory }
}

PICH-ParametersItem-CTCH-ReconfRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID				CommonPhysicalChannelID,
	pICH-Power							PICH-Power		OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer  { { PICH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

PICH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MICH-Parameters-CTCH-ReconfRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID				CommonPhysicalChannelID,
	mICH-Power							PICH-Power															OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer  { { MICH-Parameters-CTCH-ReconfRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

MICH-Parameters-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

BCH-Parameters-CTCH-ReconfRqstFDD ::= SEQUENCE {
	commonTransportChannelID	CommonTransportChannelID,
	bCH-Power					DL-Power						OPTIONAL,
	iE-Extensions	ProtocolExtensionContainer { { BCH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

BCH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PRACHList-CTCH-ReconfRqstFDD ::= SEQUENCE {
	pRACH-ParametersList-CTCH-ReconfRqstFDD	PRACH-ParametersList-CTCH-ReconfRqstFDD	OPTIONAL,
	aICH-ParametersList-CTCH-ReconfRqstFDD	AICH-ParametersList-CTCH-ReconfRqstFDD	OPTIONAL,
	iE-Extensions	ProtocolExtensionContainer { { PRACH-CTCH-ReconfRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

PRACH-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PRACH-ParametersList-CTCH-ReconfRqstFDD ::= ProtocolIE-Single-Container {{ PRACH-ParametersListIEs-CTCH-ReconfRqstFDD }}

PRACH-ParametersListIEs-CTCH-ReconfRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-PRACH-ParametersListIE-CTCH-ReconfRqstFDD	CRITICALITY reject	TYPE PRACH-ParametersListIE-CTCH-ReconfRqstFDD 	PRESENCE	mandatory }
}

PRACH-ParametersListIE-CTCH-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF PRACH-ParametersItem-CTCH-ReconfRqstFDD

PRACH-ParametersItem-CTCH-ReconfRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
	preambleSignatures						PreambleSignatures														OPTIONAL,
	allowedSlotFormatInformation			AllowedSlotFormatInformationList-CTCH-ReconfRqstFDD						OPTIONAL,
	rACH-SubChannelNumbers					RACH-SubChannelNumbers													OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer  { { PRACH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

PRACH-ParametersItem-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
{ ID	id-TnlQos			CRITICALITY ignore		EXTENSION TnlQos	PRESENCE optional },
	...
}

AllowedSlotFormatInformationList-CTCH-ReconfRqstFDD ::= SEQUENCE (SIZE (1.. maxNrOfSlotFormatsPRACH)) OF AllowedSlotFormatInformationItem-CTCH-ReconfRqstFDD

AllowedSlotFormatInformationItem-CTCH-ReconfRqstFDD ::= SEQUENCE {
	rACH-SlotFormat	RACH-SlotFormat,
	iE-Extensions	ProtocolExtensionContainer { { AllowedSlotFormatInformationItem-CTCH-ReconfRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

AllowedSlotFormatInformationItem-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

AICH-ParametersList-CTCH-ReconfRqstFDD ::= ProtocolIE-Single-Container {{ AICH-ParametersListIEs-CTCH-ReconfRqstFDD }}

AICH-ParametersListIEs-CTCH-ReconfRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-AICH-ParametersListIE-CTCH-ReconfRqstFDD	CRITICALITY reject	TYPE AICH-ParametersListIE-CTCH-ReconfRqstFDD 	PRESENCE	mandatory }
}

AICH-ParametersListIE-CTCH-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF AICH-ParametersItem-CTCH-ReconfRqstFDD

AICH-ParametersItem-CTCH-ReconfRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID				CommonPhysicalChannelID,
	aICH-Power							AICH-Power		OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer  { { AICH-ParametersItemIE-CTCH-ReconfRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

AICH-ParametersItemIE-CTCH-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST TDD
--
-- **************************************************************

CommonTransportChannelReconfigurationRequestTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CommonTransportChannelReconfigurationRequestTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CommonTransportChannelReconfigurationRequestTDD-Extensions}}		OPTIONAL,
	...
}

CommonTransportChannelReconfigurationRequestTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-C-ID	CRITICALITY reject	TYPE C-ID	PRESENCE mandatory }|
	{ ID id-ConfigurationGenerationID	CRITICALITY reject	TYPE ConfigurationGenerationID	PRESENCE mandatory }|
	{ ID id-Secondary-CCPCH-Parameters-CTCH-ReconfRqstTDD	CRITICALITY reject	TYPE Secondary-CCPCH-Parameters-CTCH-ReconfRqstTDD	PRESENCE optional	}|
	{ ID id-PICH-Parameters-CTCH-ReconfRqstTDD	CRITICALITY reject	TYPE PICH-Parameters-CTCH-ReconfRqstTDD	PRESENCE optional }|
	{ ID id-FACH-ParametersList-CTCH-ReconfRqstTDD	CRITICALITY reject	TYPE FACH-ParametersList-CTCH-ReconfRqstTDD	PRESENCE optional }|
	{ ID id-PCH-Parameters-CTCH-ReconfRqstTDD	CRITICALITY reject	TYPE PCH-Parameters-CTCH-ReconfRqstTDD	PRESENCE optional },
	...
}

CommonTransportChannelReconfigurationRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-FPACH-LCR-Parameters-CTCH-ReconfRqstTDD		CRITICALITY reject	EXTENSION FPACH-LCR-Parameters-CTCH-ReconfRqstTDD						PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-MICH-Parameters-CTCH-ReconfRqstTDD			CRITICALITY reject	EXTENSION MICH-Parameters-CTCH-ReconfRqstTDD							PRESENCE optional }|
	{ ID id-PLCCH-Parameters-CTCH-ReconfRqstTDD			CRITICALITY ignore	EXTENSION PLCCH-Parameters-CTCH-ReconfRqstTDD						PRESENCE optional }|
	{ ID id-S-CCPCH-768-Parameters-CTCH-ReconfRqstTDD	CRITICALITY reject	EXTENSION Secondary-CCPCH-768-Parameters-CTCH-ReconfRqstTDD		PRESENCE optional }|
	{ ID id-PICH-768-Parameters-CTCH-ReconfRqstTDD		CRITICALITY reject	EXTENSION PICH-768-Parameters-CTCH-ReconfRqstTDD					PRESENCE optional }|
	{ ID id-MICH-768-Parameters-CTCH-ReconfRqstTDD		CRITICALITY reject	EXTENSION MICH-768-Parameters-CTCH-ReconfRqstTDD					PRESENCE optional }|
	{ ID id-UPPCH-LCR-Parameters-CTCH-ReconfRqstTDD		CRITICALITY reject	EXTENSION UPPCH-LCR-Parameters-CTCH-ReconfRqstTDD				PRESENCE optional },	-- Applicable to 1.28Mcps TDD only	
	...
}

Secondary-CCPCH-Parameters-CTCH-ReconfRqstTDD::= SEQUENCE {
	cCTrCH-ID						CCTrCH-ID,
	secondaryCCPCHList				Secondary-CCPCHList-CTCH-ReconfRqstTDD			OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer  { { Secondary-CCPCH-CTCH-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

Secondary-CCPCH-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Additional-S-CCPCH-Parameters-CTCH-ReconfRqstTDD			CRITICALITY reject	EXTENSION Secondary-CCPCH-parameterExtendedList-CTCH-ReconfRqstTDD		PRESENCE optional	}|
	-- Applicable to 3.84Mcps TDD only, used when more than maxNrOfSCCPCHs SCCPCHs are to be reconfigured.
	{ ID id-Additional-S-CCPCH-LCR-Parameters-CTCH-ReconfRqstTDD		CRITICALITY reject	EXTENSION Secondary-CCPCH-LCR-parameterExtendedList-CTCH-ReconfRqstTDD	PRESENCE optional	},
	-- Applicable to 1.28Mcps TDD only, used when more than maxNrOfSCCPCHs SCCPCHs are to be reconfigured.
	...
}

Secondary-CCPCHList-CTCH-ReconfRqstTDD ::= ProtocolIE-Single-Container {{ Secondary-CCPCHListIEs-CTCH-ReconfRqstTDD }}

Secondary-CCPCHListIEs-CTCH-ReconfRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-Secondary-CCPCHListIE-CTCH-ReconfRqstTDD	CRITICALITY reject	TYPE Secondary-CCPCHListIE-CTCH-ReconfRqstTDD 	PRESENCE	mandatory }
}

Secondary-CCPCHListIE-CTCH-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHs)) OF Secondary-CCPCHItem-CTCH-ReconfRqstTDD

Secondary-CCPCHItem-CTCH-ReconfRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID				CommonPhysicalChannelID,
	sCCPCH-Power						DL-Power		OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer  { { Secondary-CCPCHItem-CTCH-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

Secondary-CCPCHItem-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Secondary-CCPCH-parameterExtendedList-CTCH-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHsinExt)) OF Secondary-CCPCHItem-CTCH-ReconfRqstTDD
	-- Applicable to 3.84Mcps TDD only, used when more than maxNrOfSCCPCHs SCCPCHs are to be reconfigured.

Secondary-CCPCH-LCR-parameterExtendedList-CTCH-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHsLCRinExt)) OF Secondary-CCPCHItem-CTCH-ReconfRqstTDD
	-- Applicable to 1.28Mcps TDD only, used when more than maxNrOfSCCPCHs SCCPCHs are to be reconfigured.

PICH-Parameters-CTCH-ReconfRqstTDD	 ::= SEQUENCE {
	commonPhysicalChannelID				CommonPhysicalChannelID,
	pICH-Power							PICH-Power		OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer  { { PICH-Parameters-CTCH-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PICH-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

FACH-ParametersList-CTCH-ReconfRqstTDD ::= SEQUENCE (SIZE (0..maxNrOfFACHs)) OF FACH-ParametersItem-CTCH-ReconfRqstTDD

FACH-ParametersItem-CTCH-ReconfRqstTDD ::= SEQUENCE {
 	commonTransportChannelID		CommonTransportChannelID,
	toAWS							ToAWS			OPTIONAL,
 	toAWE							ToAWE			OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer  { { FACH-ParametersItem-CTCH-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

FACH-ParametersItem-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-maxFACH-Power-LCR-CTCH-ReconfRqstTDD			CRITICALITY	reject		EXTENSION DL-Power		PRESENCE optional	}|
	--  Applicable to 1.28Mcps TDD only
	{ ID	id-TnlQos										CRITICALITY ignore		EXTENSION TnlQos		PRESENCE optional },
	...
}

PCH-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE {
	commonTransportChannelID	CommonTransportChannelID,
	toAWS	ToAWS	OPTIONAL,
	toAWE	ToAWE	OPTIONAL,
	iE-Extensions	ProtocolExtensionContainer  { { PCH-Parameters-CTCH-ReconfRqstTDD-ExtIEs} }	OPTIONAL,
	...
}

PCH-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-PCH-Power-LCR-CTCH-ReconfRqstTDD		CRITICALITY reject		EXTENSION DL-Power		PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-TnlQos									CRITICALITY ignore		EXTENSION TnlQos		PRESENCE optional },
	...
}

FPACH-LCR-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE {
	commonPhysicalChannelId			CommonPhysicalChannelID,
	fPACHPower						FPACH-Power		OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer  { { FPACH-LCR-Parameters-CTCH-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

FPACH-LCR-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MICH-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID				CommonPhysicalChannelID,
	mICH-Power							PICH-Power															OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer  { { MICH-Parameters-CTCH-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

MICH-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PLCCH-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE {
	maxPowerPLCCH						DL-Power,
	iE-Extensions						ProtocolExtensionContainer  { { PLCCH-Parameters-CTCH-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PLCCH-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Secondary-CCPCH-768-Parameters-CTCH-ReconfRqstTDD::= SEQUENCE {
	cCTrCH-ID						CCTrCH-ID,
	secondaryCCPCH768List			Secondary-CCPCH-768-List-CTCH-ReconfRqstTDD			OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer  { { Secondary-CCPCH-768-CTCH-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

Secondary-CCPCH-768-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Secondary-CCPCH-768-List-CTCH-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSCCPCHs768)) OF Secondary-CCPCH-768-Item-CTCH-ReconfRqstTDD

Secondary-CCPCH-768-Item-CTCH-ReconfRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID768			CommonPhysicalChannelID768,
	sCCPCH-Power						DL-Power		OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer  { { Secondary-CCPCH-768-Item-CTCH-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

Secondary-CCPCH-768-Item-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PICH-768-Parameters-CTCH-ReconfRqstTDD	 ::= SEQUENCE {
	commonPhysicalChannelID768			CommonPhysicalChannelID768,
	pICH-Power							PICH-Power		OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer  { { PICH-768-Parameters-CTCH-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PICH-768-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MICH-768-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID768			CommonPhysicalChannelID768,
	mICH-Power							PICH-Power																OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer  { { MICH-768-Parameters-CTCH-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

MICH-768-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


UPPCH-LCR-Parameters-CTCH-ReconfRqstTDD ::= SEQUENCE {
	uPPCHPositionLCR	UPPCHPositionLCR	OPTIONAL,
	uARFCN	UARFCN	OPTIONAL,
	-- Mandatory for 1.28Mcps TDD when using multiple frequencies Corresponds to Nt (TS 25.105 [15])
	iE-Extensions	ProtocolExtensionContainer { { UPPCH-LCR-Parameters-CTCH-ReconfRqstTDD-ExtIEs} }	OPTIONAL,
	...
}

UPPCH-LCR-Parameters-CTCH-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE
--
-- **************************************************************

CommonTransportChannelReconfigurationResponse ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CommonTransportChannelReconfigurationResponse-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CommonTransportChannelReconfigurationResponse-Extensions}}		OPTIONAL,
	...
}

CommonTransportChannelReconfigurationResponse-IEs NBAP-PROTOCOL-IES ::= {	
	{ ID	id-CriticalityDiagnostics		CRITICALITY		ignore			TYPE	CriticalityDiagnostics		PRESENCE	optional},
	...
}

CommonTransportChannelReconfigurationResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE
--
-- **************************************************************

CommonTransportChannelReconfigurationFailure ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CommonTransportChannelReconfigurationFailure-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CommonTransportChannelReconfigurationFailure-Extensions}}		OPTIONAL,
	...
}

CommonTransportChannelReconfigurationFailure-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-Cause						CRITICALITY	ignore			TYPE	Cause					PRESENCE	mandatory }|
	{ ID	id-CriticalityDiagnostics		CRITICALITY	ignore			TYPE	CriticalityDiagnostics		PRESENCE	optional	},
	...
}

CommonTransportChannelReconfigurationFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMMON TRANSPORT CHANNEL DELETION REQUEST
--
-- **************************************************************

CommonTransportChannelDeletionRequest ::= SEQUENCE {
	protocolIEs					ProtocolIE-Container		{{CommonTransportChannelDeletionRequest-IEs}},
	protocolExtensions			ProtocolExtensionContainer	{{CommonTransportChannelDeletionRequest-Extensions}}		OPTIONAL,
	...
}

CommonTransportChannelDeletionRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-C-ID								CRITICALITY	reject		TYPE C-ID					PRESENCE mandatory }|
	{ ID	id-CommonPhysicalChannelID			CRITICALITY	reject		TYPE CommonPhysicalChannelID	PRESENCE mandatory }|
	{ ID	id-ConfigurationGenerationID		CRITICALITY	reject		TYPE ConfigurationGenerationID	PRESENCE mandatory },
	...
}

CommonTransportChannelDeletionRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-CommonPhysicalChannelID768-CommonTrChDeletionReq	CRITICALITY reject	EXTENSION CommonPhysicalChannelID768	PRESENCE optional },
	...
}

-- **************************************************************
--
-- COMMON TRANSPORT CHANNEL DELETION RESPONSE
--
-- **************************************************************

CommonTransportChannelDeletionResponse ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CommonTransportChannelDeletionResponse-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CommonTransportChannelDeletionResponse-Extensions}}			OPTIONAL,
	...
}

CommonTransportChannelDeletionResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CriticalityDiagnostics		CRITICALITY		ignore		TYPE	CriticalityDiagnostics		PRESENCE	optional},
	...
}

CommonTransportChannelDeletionResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- BLOCK RESOURCE REQUEST
--
-- **************************************************************

BlockResourceRequest ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{BlockResourceRequest-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{BlockResourceRequest-Extensions}}			OPTIONAL,
	...
}

BlockResourceRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-C-ID							CRITICALITY reject		TYPE C-ID						PRESENCE mandatory	}|
	{ ID id-BlockingPriorityIndicator		CRITICALITY reject		TYPE BlockingPriorityIndicator	PRESENCE mandatory	}|
	{ ID id-ShutdownTimer					CRITICALITY reject		TYPE ShutdownTimer				PRESENCE conditional	},
	-- The IE shall be present if the Blocking Priority Indicator IE indicates "Normal Priority"--
	...
}

BlockResourceRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- BLOCK RESOURCE RESPONSE
--
-- **************************************************************

BlockResourceResponse ::= SEQUENCE {
	protocolIEs					ProtocolIE-Container		{{BlockResourceResponse-IEs}},
	protocolExtensions			ProtocolExtensionContainer	{{BlockResourceResponse-Extensions}}		OPTIONAL,
	...
}

BlockResourceResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CriticalityDiagnostics		CRITICALITY ignore		TYPE CriticalityDiagnostics		PRESENCE optional},
	...
}

BlockResourceResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- BLOCK RESOURCE FAILURE
--
-- **************************************************************

BlockResourceFailure ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{BlockResourceFailure-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{BlockResourceFailure-Extensions}}		OPTIONAL,
	...
}

BlockResourceFailure-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-Cause						CRITICALITY ignore		TYPE Cause							PRESENCE mandatory	}|
	{ ID id-CriticalityDiagnostics		CRITICALITY ignore		TYPE CriticalityDiagnostics 		PRESENCE optional		},
	...
}

BlockResourceFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- UNBLOCK RESOURCE INDICATION
--
-- **************************************************************

UnblockResourceIndication ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{UnblockResourceIndication-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{UnblockResourceIndication-Extensions}}    OPTIONAL,
	...
}

UnblockResourceIndication-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-C-ID			CRITICALITY ignore		TYPE C-ID		PRESENCE mandatory },
	...
}

UnblockResourceIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- AUDIT REQUIRED INDICATION
--
-- **************************************************************

AuditRequiredIndication ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{AuditRequiredIndication-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{AuditRequiredIndication-Extensions}}		OPTIONAL,
	...
}

AuditRequiredIndication-IEs NBAP-PROTOCOL-IES ::= {
	...
}

AuditRequiredIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- AUDIT REQUEST
--
-- **************************************************************

AuditRequest ::= SEQUENCE {
	protocolIEs					ProtocolIE-Container		{{AuditRequest-IEs}},
	protocolExtensions			ProtocolExtensionContainer	{{AuditRequest-Extensions}}		OPTIONAL,
	...
}

AuditRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-Start-Of-Audit-Sequence-Indicator		CRITICALITY reject	TYPE Start-Of-Audit-Sequence-Indicator	 	PRESENCE mandatory },
	...
}

AuditRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- AUDIT RESPONSE
--
-- **************************************************************

AuditResponse ::= SEQUENCE {
	protocolIEs					ProtocolIE-Container		{{AuditResponse-IEs}},
	protocolExtensions			ProtocolExtensionContainer	{{AuditResponse-Extensions}}		OPTIONAL,
	...
}

AuditResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-End-Of-Audit-Sequence-Indicator				CRITICALITY ignore	TYPE End-Of-Audit-Sequence-Indicator				PRESENCE mandatory }|
	{ ID id-Cell-InformationList-AuditRsp				CRITICALITY ignore	TYPE Cell-InformationList-AuditRsp				PRESENCE optional }|
	{ ID id-CCP-InformationList-AuditRsp				CRITICALITY ignore	TYPE CCP-InformationList-AuditRsp				PRESENCE optional }|
	-- CCP (Communication Control Port) --
	{ ID id-Local-Cell-InformationList-AuditRsp			CRITICALITY ignore	TYPE Local-Cell-InformationList-AuditRsp			PRESENCE optional }|
	{ ID id-Local-Cell-Group-InformationList-AuditRsp	CRITICALITY ignore	TYPE Local-Cell-Group-InformationList-AuditRsp	PRESENCE optional }|
	{ ID id-CriticalityDiagnostics						CRITICALITY ignore	TYPE CriticalityDiagnostics				PRESENCE optional },
	...
}

AuditResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Power-Local-Cell-Group-InformationList-AuditRsp	CRITICALITY ignore	EXTENSION Power-Local-Cell-Group-InformationList-AuditRsp		PRESENCE optional },
	...
}

Cell-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxCellinNodeB)) OF ProtocolIE-Single-Container {{ Cell-InformationItemIE-AuditRsp}}

Cell-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID	id-Cell-InformationItem-AuditRsp		CRITICALITY ignore		TYPE Cell-InformationItem-AuditRsp			PRESENCE optional	}
}

Cell-InformationItem-AuditRsp ::= SEQUENCE {
	c-ID	C-ID,
	configurationGenerationID	ConfigurationGenerationID,
	resourceOperationalState	ResourceOperationalState,
	availabilityStatus	AvailabilityStatus,
	local-Cell-ID	Local-Cell-ID,
	primary-SCH-Information	P-SCH-Information-AuditRsp	OPTIONAL,
	secondary-SCH-Information	S-SCH-Information-AuditRsp	OPTIONAL,
	primary-CPICH-Information	P-CPICH-Information-AuditRsp	OPTIONAL,
	secondary-CPICH-InformationList	S-CPICH-InformationList-AuditRsp	OPTIONAL,
	primary-CCPCH-Information	P-CCPCH-Information-AuditRsp	OPTIONAL,
	bCH-Information	BCH-Information-AuditRsp	OPTIONAL,
	secondary-CCPCH-InformationList	S-CCPCH-InformationList-AuditRsp	OPTIONAL,
	pCH-Information	PCH-Information-AuditRsp	OPTIONAL,
	pICH-Information	PICH-Information-AuditRsp	OPTIONAL,
	fACH-InformationList	FACH-InformationList-AuditRsp	OPTIONAL,
	pRACH-InformationList	PRACH-InformationList-AuditRsp	OPTIONAL,
	rACH-InformationList	RACH-InformationList-AuditRsp	OPTIONAL,
	aICH-InformationList	AICH-InformationList-AuditRsp	OPTIONAL,
	notUsed-1-pCPCH-InformationList	NULL	OPTIONAL,	
	notUsed-2-cPCH-InformationList	NULL	OPTIONAL,
	notUsed-3-aP-AICH-InformationList	NULL	OPTIONAL,
	notUsed-4-cDCA-ICH-InformationList	NULL	OPTIONAL,
	sCH-Information	SCH-Information-AuditRsp	OPTIONAL,
	iE-Extensions	ProtocolExtensionContainer  { { Cell-InformationItem-AuditRsp-ExtIEs} }	OPTIONAL,
	...
}

Cell-InformationItem-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-FPACH-LCR-InformationList-AuditRsp		CRITICALITY ignore	EXTENSION FPACH-LCR-InformationList-AuditRsp			PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-DwPCH-LCR-InformationList-AuditRsp		CRITICALITY ignore	EXTENSION Common-PhysicalChannel-Status-Information	PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-HSDSCH-Resources-Information-AuditRsp	CRITICALITY ignore	EXTENSION HS-DSCH-Resources-Information-AuditRsp		PRESENCE optional }|
	-- For 1.28Mcps TDD, this HS-DSCH Resource Information is for the first Frequency repetition, HS-DSCH Resource Information for Frequency repetitions 2 and on, should be defined in MultipleFreq-HS-DSCH-Resources-InformationList-AuditRsp.
	{ ID id-MICH-Information-AuditRsp				CRITICALITY ignore	EXTENSION Common-PhysicalChannel-Status-Information		PRESENCE optional }|
	{ ID id-S-CCPCH-InformationListExt-AuditRsp		CRITICALITY ignore	EXTENSION S-CCPCH-InformationListExt-AuditRsp				PRESENCE optional }|
	-- Applicable to 3.84Mcps TDD only, used when there are more than maxSCCPCHCell SCCPCHs in the cell.
	{ ID id-S-CCPCH-LCR-InformationListExt-AuditRsp	CRITICALITY ignore	EXTENSION S-CCPCH-LCR-InformationListExt-AuditRsp			PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only, used when there are more than maxSCCPCHCell SCCPCHs in the cell.
	{ ID id-E-DCH-Resources-Information-AuditRsp	CRITICALITY ignore	EXTENSION E-DCH-Resources-Information-AuditRsp				PRESENCE optional }|
	-- For 1.28Mcps TDD, this E-DCH Resource Information is for the first Frequency repetition, E-DCH Resource Information for Frequency repetitions 2 and on, should be defined in MultipleFreq-E-DCH-Resources-InformationList-AuditRsp.
	{ ID id-PLCCH-InformationList-AuditRsp			CRITICALITY ignore	EXTENSION PLCCH-InformationList-AuditRsp					PRESENCE optional }|
	{ ID id-P-CCPCH-768-Information-AuditRsp		CRITICALITY ignore	EXTENSION Common-PhysicalChannel-Status-Information768	PRESENCE optional }|
	{ ID id-S-CCPCH-768-InformationList-AuditRsp	CRITICALITY ignore	EXTENSION S-CCPCH-768-InformationList-AuditRsp				PRESENCE optional }|
	{ ID id-PICH-768-Information-AuditRsp			CRITICALITY ignore	EXTENSION Common-PhysicalChannel-Status-Information768	PRESENCE optional }|
	{ ID id-PRACH-768-InformationList-AuditRsp		CRITICALITY ignore	EXTENSION PRACH-768-InformationList-AuditRsp				PRESENCE optional }|
	{ ID id-SCH-768-Information-AuditRsp			CRITICALITY ignore	EXTENSION Common-PhysicalChannel-Status-Information768	PRESENCE optional }|
	{ ID id-MICH-768-Information-AuditRsp			CRITICALITY ignore	EXTENSION Common-PhysicalChannel-Status-Information768	PRESENCE optional }|
	{ ID id-E-RUCCH-InformationList-AuditRsp		CRITICALITY ignore	EXTENSION E-RUCCH-InformationList-AuditRsp					PRESENCE optional }|
	{ ID id-E-RUCCH-768-InformationList-AuditRsp	CRITICALITY ignore	EXTENSION E-RUCCH-768-InformationList-AuditRsp				PRESENCE optional }|
	{ ID id-Cell-Frequency-List-Information-LCR-MulFreq-AuditRsp	CRITICALITY ignore	EXTENSION  Cell-Frequency-List-Information-LCR-MulFreq-AuditRsp	 PRESENCE optional }| 	-- Applicable to 1.28Mcps TDD when using multiple frequencies
	{ ID id-UPPCH-LCR-InformationList-AuditRsp		CRITICALITY ignore	EXTENSION UPPCH-LCR-InformationList-AuditRsp				PRESENCE optional }|
	  -- Applicable to 1.28Mcps TDD only
	{ ID id-multipleFreq-HS-DSCH-Resources-InformationList-AuditRsp	CRITICALITY ignore	EXTENSION MultipleFreq-HS-DSCH-Resources-InformationList-AuditRsp	PRESENCE optional }|
-- Applicable to 1.28Mcps TDD when using multiple frequencies.This HS-DSCH Resource Information is for the 2nd and beyond frequencies.
	{ ID id-MultipleFreq-E-DCH-Resources-InformationList-AuditRsp	CRITICALITY ignore	EXTENSION MultipleFreq-E-DCH-Resources-InformationList-AuditRsp	PRESENCE optional },
	-- Applicable to 1.28Mcps TDD when using multiple frequencies. This E-DCH Resource Information is for the 2nd and beyond frequencies.
	...
}

P-SCH-Information-AuditRsp ::= ProtocolIE-Single-Container {{ P-SCH-InformationIE-AuditRsp }}

P-SCH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-P-SCH-Information	CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information	PRESENCE	mandatory }
}

S-SCH-Information-AuditRsp ::= ProtocolIE-Single-Container {{ S-SCH-InformationIE-AuditRsp }}

S-SCH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-S-SCH-Information	CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information	PRESENCE	mandatory }
}

P-CPICH-Information-AuditRsp ::= ProtocolIE-Single-Container {{ P-CPICH-InformationIE-AuditRsp }}

P-CPICH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-P-CPICH-Information	CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information	PRESENCE	mandatory }
}

S-CPICH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxSCPICHCell)) OF ProtocolIE-Single-Container {{ S-CPICH-InformationItemIE-AuditRsp }}

S-CPICH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-S-CPICH-Information	CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information	PRESENCE mandatory }
}

P-CCPCH-Information-AuditRsp ::= ProtocolIE-Single-Container {{ P-CCPCH-InformationIE-AuditRsp }}

P-CCPCH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-P-CCPCH-Information	CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information	PRESENCE mandatory }
}

BCH-Information-AuditRsp ::= ProtocolIE-Single-Container {{ BCH-InformationIE-AuditRsp }}

BCH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-BCH-Information	CRITICALITY ignore	TYPE Common-TransportChannel-Status-Information	PRESENCE mandatory }
}

S-CCPCH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxSCCPCHCell)) OF ProtocolIE-Single-Container {{ S-CCPCH-InformationItemIE-AuditRsp }}

S-CCPCH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-S-CCPCH-Information	CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information	PRESENCE mandatory }
}

PCH-Information-AuditRsp ::= ProtocolIE-Single-Container {{ PCH-InformationIE-AuditRsp }}

PCH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-PCH-Information	CRITICALITY ignore	TYPE Common-TransportChannel-Status-Information	PRESENCE mandatory }
}

PICH-Information-AuditRsp ::= ProtocolIE-Single-Container {{ PICH-InformationIE-AuditRsp }}

PICH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-PICH-Information	CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information	PRESENCE mandatory }
}

FACH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxFACHCell)) OF ProtocolIE-Single-Container {{ FACH-InformationItemIE-AuditRsp }}

FACH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-FACH-Information	CRITICALITY ignore	TYPE Common-TransportChannel-Status-Information	PRESENCE mandatory }
}

PRACH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE-Single-Container {{ PRACH-InformationItemIE-AuditRsp }}

PRACH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-PRACH-Information	CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information	PRESENCE mandatory }
}

RACH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxRACHCell)) OF ProtocolIE-Single-Container {{ RACH-InformationItemIE-AuditRsp }}

RACH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-RACH-Information	CRITICALITY ignore	TYPE Common-TransportChannel-Status-Information	PRESENCE mandatory }
}

AICH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE-Single-Container {{ AICH-InformationItemIE-AuditRsp }}

AICH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-AICH-Information	CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information	PRESENCE mandatory }
}

SCH-Information-AuditRsp ::= ProtocolIE-Single-Container {{ SCH-InformationIE-AuditRsp }}

SCH-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-SCH-Information	CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information	PRESENCE mandatory }
}

FPACH-LCR-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxFPACHCell)) OF ProtocolIE-Single-Container {{ FPACH-LCR-InformationItemIE-AuditRsp }}

FPACH-LCR-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-FPACH-LCR-Information-AuditRsp	CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information	PRESENCE mandatory }
}

HS-DSCH-Resources-Information-AuditRsp ::= SEQUENCE {
	resourceOperationalState			ResourceOperationalState,
	availabilityStatus					AvailabilityStatus,
	iE-Extensions						ProtocolExtensionContainer  {{ HS-DSCH-Resources-Information-AuditRsp-ExtIEs }}		OPTIONAL,
	...
}

HS-DSCH-Resources-Information-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UARFCNforNt		CRITICALITY ignore		EXTENSION UARFCN		PRESENCE	optional },
	--  Applicable to 1.28Mcps TDD when using multiple frequencies.
	...
}

S-CCPCH-InformationListExt-AuditRsp ::= SEQUENCE (SIZE (1..maxSCCPCHCellinExt)) OF ProtocolIE-Single-Container {{ S-CCPCH-InformationItemIE-AuditRsp }}

S-CCPCH-LCR-InformationListExt-AuditRsp ::= SEQUENCE (SIZE (1..maxSCCPCHCellinExtLCR)) OF ProtocolIE-Single-Container {{ S-CCPCH-InformationItemIE-AuditRsp }}

E-DCH-Resources-Information-AuditRsp ::= SEQUENCE {
	resourceOperationalState			ResourceOperationalState,
	availabilityStatus					AvailabilityStatus,
	iE-Extensions						ProtocolExtensionContainer  {{ E-DCH-Resources-Information-AuditRsp-ExtIEs }}		OPTIONAL,
	...
}

E-DCH-Resources-Information-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UARFCNforNt		CRITICALITY ignore		EXTENSION UARFCN		PRESENCE	optional },
	-- Applicable to 1.28Mcps TDD when using multiple frequencies.
	...
}

PLCCH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxPLCCHCell)) OF ProtocolIE-Single-Container {{ PLCCH-InformationItemIE-AuditRsp }}

PLCCH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-PLCCH-Information-AuditRsp   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

S-CCPCH-768-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxSCCPCHCell768)) OF ProtocolIE-Single-Container {{ S-CCPCH-768-InformationItemIE-AuditRsp }}

S-CCPCH-768-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-S-CCPCH-768-Information-AuditRsp   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information768		PRESENCE mandatory }
}

PRACH-768-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE-Single-Container {{ PRACH-768-InformationItemIE-AuditRsp }}

PRACH-768-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-PRACH-768-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information768		PRESENCE mandatory }
}

E-RUCCH-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxE-RUCCHCell)) OF ProtocolIE-Single-Container {{ E-RUCCH-InformationItemIE-AuditRsp }}

E-RUCCH-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-E-RUCCH-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

E-RUCCH-768-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxE-RUCCHCell)) OF ProtocolIE-Single-Container {{ E-RUCCH-768-InformationItemIE-AuditRsp }}

E-RUCCH-768-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-E-RUCCH-768-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information768		PRESENCE mandatory }
}

Cell-Frequency-List-Information-LCR-MulFreq-AuditRsp ::= SEQUENCE (SIZE (1..maxFrequencyinCell)) OF ProtocolIE-Single-Container {{ Cell-Frequency-List-InformationIE-LCR-MulFreq-AuditRsp }}

Cell-Frequency-List-InformationIE-LCR-MulFreq-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-Cell-Frequency-List-InformationItem-LCR-MulFreq-AuditRsp	CRITICALITY ignore	TYPE Cell-Frequency-List-InformationItem-LCR-MulFreq-AuditRsp		PRESENCE mandatory }
}

Cell-Frequency-List-InformationItem-LCR-MulFreq-AuditRsp ::= SEQUENCE {
	uARFCN								UARFCN,
	resourceOperationalState			ResourceOperationalState,
	availabilityStatus					AvailabilityStatus,
	iE-Extensions						ProtocolExtensionContainer  {{ Cell-Frequency-List-InformationItem-LCR-MulFreq-AuditRsp-ExtIEs }}		OPTIONAL,
	...
}

Cell-Frequency-List-InformationItem-LCR-MulFreq-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UPPCH-LCR-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxFrequencyinCell)) OF ProtocolIE-Single-Container {{ UPPCH-LCR-InformationIE-AuditRsp }}

UPPCH-LCR-InformationIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-UPPCH-LCR-InformationItem-AuditRsp   CRITICALITY ignore	TYPE UPPCH-LCR-InformationItem-AuditRsp		PRESENCE mandatory }
}

UPPCH-LCR-InformationItem-AuditRsp ::= SEQUENCE {
	uARFCN								UARFCN				OPTIONAL,
	uPPCHPositionLCR					UPPCHPositionLCR, 
	resourceOperationalState			ResourceOperationalState,
	availabilityStatus					AvailabilityStatus,
	iE-Extensions						ProtocolExtensionContainer {{ UPPCH-LCR-InformationItem-AuditRsp-ExtIEs }}		OPTIONAL,
	...
}

UPPCH-LCR-InformationItem-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MultipleFreq-HS-DSCH-Resources-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxFrequencyinCell-1)) OF ProtocolIE-Single-Container {{ MultipleFreq-HS-DSCH-Resources-InformationItem-AuditRsp}} 
--Includes the 2nd through the max number of frequencies information repetitions.

MultipleFreq-HS-DSCH-Resources-InformationItem-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-HSDSCH-Resources-Information-AuditRsp	CRITICALITY ignore	TYPE HS-DSCH-Resources-Information-AuditRsp		PRESENCE mandatory }
}

MultipleFreq-E-DCH-Resources-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxFrequencyinCell-1)) OF ProtocolIE-Single-Container {{ MultipleFreq-E-DCH-Resources-InformationItem-AuditRsp}} 
	-- Includes the 2nd through the max number of frequencies information repetitions.

MultipleFreq-E-DCH-Resources-InformationItem-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-E-DCH-Resources-Information-AuditRsp	CRITICALITY ignore	TYPE E-DCH-Resources-Information-AuditRsp		PRESENCE mandatory }
}

CCP-InformationList-AuditRsp ::= SEQUENCE (SIZE (1..maxCCPinNodeB)) OF ProtocolIE-Single-Container {{ CCP-InformationItemIE-AuditRsp }}

CCP-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-CCP-InformationItem-AuditRsp			CRITICALITY ignore			TYPE CCP-InformationItem-AuditRsp			PRESENCE mandatory }
}

CCP-InformationItem-AuditRsp ::= SEQUENCE {
	communicationControlPortID			CommunicationControlPortID,
	resourceOperationalState			ResourceOperationalState,
	availabilityStatus					AvailabilityStatus,
	iE-Extensions						ProtocolExtensionContainer  {{ CCP-InformationItem-AuditRsp-ExtIEs }}		OPTIONAL,
	...
}

CCP-InformationItem-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Local-Cell-InformationList-AuditRsp	 ::=SEQUENCE (SIZE (1..maxLocalCellinNodeB)) OF ProtocolIE-Single-Container {{ Local-Cell-InformationItemIE-AuditRsp }}

Local-Cell-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-Local-Cell-InformationItem-AuditRsp		CRITICALITY ignore	TYPE Local-Cell-InformationItem-AuditRsp	PRESENCE	mandatory}
}

Local-Cell-InformationItem-AuditRsp ::= SEQUENCE {
	local-Cell-ID								Local-Cell-ID,
	dl-or-global-capacityCredit					DL-or-Global-CapacityCredit,
	ul-capacityCredit							UL-CapacityCredit													OPTIONAL,
	commonChannelsCapacityConsumptionLaw 		CommonChannelsCapacityConsumptionLaw,
	dedicatedChannelsCapacityConsumptionLaw 	DedicatedChannelsCapacityConsumptionLaw,
	maximumDL-PowerCapability					MaximumDL-PowerCapability											OPTIONAL,
	minSpreadingFactor							MinSpreadingFactor													OPTIONAL,
	minimumDL-PowerCapability					MinimumDL-PowerCapability											OPTIONAL,
	local-Cell-Group-ID							Local-Cell-ID														OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer  {{ Local-Cell-InformationItem-AuditRsp-ExtIEs}}		OPTIONAL,
	...
}

Local-Cell-InformationItem-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-ReferenceClockAvailability			CRITICALITY ignore	EXTENSION ReferenceClockAvailability		PRESENCE optional }|
	{ ID id-Power-Local-Cell-Group-ID			CRITICALITY ignore	EXTENSION Local-Cell-ID				PRESENCE optional }|
	{ ID id-HSDPA-Capability					CRITICALITY ignore	EXTENSION HSDPA-Capability			PRESENCE optional }|
	{ ID id-E-DCH-Capability					CRITICALITY ignore	EXTENSION E-DCH-Capability			PRESENCE optional }|
	{ ID id-E-DCH-TTI2ms-Capability				CRITICALITY ignore	EXTENSION E-DCH-TTI2ms-Capability		PRESENCE conditional }|
	-- The IE shall be present if E-DCH Capability IE is set to ”E-DCH Capable”.
	{ ID id-E-DCH-SF-Capability					CRITICALITY ignore	EXTENSION E-DCH-SF-Capability		PRESENCE conditional }|
	-- The IE shall be present if E-DCH Capability IE is set to ”E-DCH Capable”.
	{ ID id-E-DCH-HARQ-Combining-Capability		CRITICALITY ignore	EXTENSION E-DCH-HARQ-Combining-Capability		PRESENCE conditional }|
	-- The IE shall be present if E-DCH Capability IE is set to ”E-DCH Capable”.
	{ ID id-E-DCH-CapacityConsumptionLaw		CRITICALITY ignore	EXTENSION E-DCHCapacityConsumptionLaw		PRESENCE optional }|
	{ ID id-F-DPCH-Capability					CRITICALITY ignore	EXTENSION F-DPCH-Capability			PRESENCE optional }|
	{ ID id-E-DCH-TDD-CapacityConsumptionLaw	CRITICALITY ignore	EXTENSION E-DCH-TDD-CapacityConsumptionLaw		PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivityDTX-DRX-Capability	CRITICALITY ignore	EXTENSION ContinuousPacketConnectivityDTX-DRX-Capability	PRESENCE optional }|
	{ ID id-Max-UE-DTX-Cycle					CRITICALITY ignore	EXTENSION Max-UE-DTX-Cycle			PRESENCE conditional }|
	-- The IE shall be present if Continuous Packet Connectivity DTX-DRX Capability IE is present and set to ”Continuous Packet Connectivity DTX-DRX Capable”.
	{ ID id-ContinuousPacketConnectivityHS-SCCH-less-Capability		CRITICALITY ignore	EXTENSION ContinuousPacketConnectivityHS-SCCH-less-Capability	PRESENCE optional }|
	{ ID id-MIMO-Capability						CRITICALITY ignore	EXTENSION MIMO-Capability			PRESENCE optional }|
	{ ID id-SixtyfourQAM-DL-Capability			CRITICALITY ignore	EXTENSION SixtyfourQAM-DL-Capability		PRESENCE optional }|
	{ ID id-MBMS-Capability						CRITICALITY ignore	EXTENSION MBMS-Capability			PRESENCE optional }|
	{ ID id-Enhanced-FACH-Capability			CRITICALITY ignore	EXTENSION Enhanced-FACH-Capability		PRESENCE optional }|
	{ ID id-Enhanced-PCH-Capability				CRITICALITY ignore	EXTENSION Enhanced-PCH-Capability		PRESENCE conditional }|
	-- The IE shall be present if Enhanced FACH Capability IE is set to ”Enhanced FACH Capable”.
	{ ID id-SixteenQAM-UL-Capability			CRITICALITY ignore	EXTENSION SixteenQAM-UL-Capability		PRESENCE optional }|
	{ ID id-HSDSCH-MACdPDU-SizeCapability		CRITICALITY ignore	EXTENSION HSDSCH-MACdPDU-SizeCapability		PRESENCE optional }|
	{ ID id-MBSFN-Only-Mode-Capability			CRITICALITY ignore	EXTENSION MBSFN-Only-Mode-Capability		PRESENCE optional }|
	{ ID id-F-DPCH-SlotFormatCapability			CRITICALITY ignore	EXTENSION F-DPCH-SlotFormatCapability		PRESENCE optional }|
	{ ID id-E-DCH-MACdPDU-SizeCapability		CRITICALITY ignore	EXTENSION E-DCH-MACdPDU-SizeCapability		PRESENCE optional }|
	{ ID id-Common-EDCH-Capability				CRITICALITY ignore	EXTENSION Common-EDCH-Capability		PRESENCE optional }|
	{ ID id-E-AI-Capability						CRITICALITY ignore	EXTENSION E-AI-Capability			PRESENCE optional }|
	-- The IE shall be present if Common E-DCH Capability IE is present and set to ”Common E-DCH Capable”.
	{ ID id-Enhanced-UE-DRX-Capability			CRITICALITY ignore	EXTENSION Enhanced-UE-DRX-Capability		PRESENCE optional }|
	{ ID id-Enhanced-UE-DRX-CapabilityLCR		CRITICALITY ignore	EXTENSION Enhanced-UE-DRX-Capability		PRESENCE optional }|
	{ ID id-E-DPCCH-Power-Boosting-Capability	CRITICALITY ignore	EXTENSION E-DPCCH-Power-Boosting-Capability		PRESENCE optional }|
	{ ID id-SixtyfourQAM-DL-MIMO-Combined-Capability	CRITICALITY ignore	EXTENSION SixtyfourQAM-DL-MIMO-Combined-Capability	PRESENCE optional}|
	{ ID id-Multi-Cell-Capability-Info			CRITICALITY ignore	EXTENSION Multi-Cell-Capability-Info		PRESENCE optional }|
	{ ID id-Semi-PersistentScheduling-CapabilityLCR		CRITICALITY ignore	EXTENSION Semi-PersistentScheduling-CapabilityLCR	PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivity-DRX-CapabilityLCR	CRITICALITY ignore	EXTENSION ContinuousPacketConnectivity-DRX-CapabilityLCR	PRESENCE optional }|
	{ ID id-Common-E-DCH-HSDPCCH-Capability		CRITICALITY ignore	EXTENSION Common-E-DCH-HSDPCCH-Capability		PRESENCE optional }|
	-- The IE shall be present if Common E-DCH Capability IE is present and set to ”Common E-DCH Capable”.
	{ ID id-MIMO-Power-Offset-For-S-CPICH-Capability	CRITICALITY ignore	EXTENSION MIMO-PowerOffsetForS-CPICHCapability	PRESENCE optional }|
	{ ID id-TxDiversityOnDLControlChannelsByMIMOUECapability	CRITICALITY ignore	EXTENSION TxDiversityOnDLControlChannelsByMIMOUECapability	PRESENCE optional }|
	{ ID id-Single-Stream-MIMO-Capability		CRITICALITY ignore	EXTENSION Single-Stream-MIMO-Capability		PRESENCE optional }|
	{ ID id-Dual-Band-Capability-Info			CRITICALITY ignore	EXTENSION Dual-Band-Capability-Info		PRESENCE optional }|
	{ ID id-CellPortion-CapabilityLCR			CRITICALITY ignore	EXTENSION CellPortion-CapabilityLCR		PRESENCE optional }|
	{ ID id-Cell-Capability-Container			CRITICALITY ignore	EXTENSION Cell-Capability-Container		PRESENCE optional }|
	{ ID id-TS0-CapabilityLCR					CRITICALITY ignore	EXTENSION TS0-CapabilityLCR			PRESENCE optional }|
	{ ID id-PrecodingWeightSetRestriction		CRITICALITY ignore	EXTENSION PrecodingWeightSetRestriction		PRESENCE optional }|
	{ ID id-Cell-Capability-Container-TDD-LCR	CRITICALITY ignore	EXTENSION Cell-Capability-Container-TDD-LCR		PRESENCE optional }|
	{ ID id-MU-MIMO-Capability-ContainerLCR		CRITICALITY ignore	EXTENSION MU-MIMO-Capability-ContainerLCR		PRESENCE optional }|
	{ ID id-Adaptive-Special-Burst-Power-CapabilityLCR	CRITICALITY ignore	EXTENSION Adaptive-Special-Burst-Power-CapabilityLCR	PRESENCE optional },
	...
}

Local-Cell-Group-InformationList-AuditRsp	 ::= SEQUENCE (SIZE (1..maxLocalCellinNodeB)) OF ProtocolIE-Single-Container {{ Local-Cell-Group-InformationItemIE-AuditRsp }}

Local-Cell-Group-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-Local-Cell-Group-InformationItem-AuditRsp	CRITICALITY ignore	TYPE Local-Cell-Group-InformationItem-AuditRsp	PRESENCE mandatory}
}

Local-Cell-Group-InformationItem-AuditRsp ::= SEQUENCE {
	local-Cell-Group-ID							Local-Cell-ID,
	dl-or-global-capacityCredit					DL-or-Global-CapacityCredit,
	ul-capacityCredit							UL-CapacityCredit						OPTIONAL,
	commonChannelsCapacityConsumptionLaw 		CommonChannelsCapacityConsumptionLaw,
	dedicatedChannelsCapacityConsumptionLaw 	DedicatedChannelsCapacityConsumptionLaw,
	iE-Extensions								ProtocolExtensionContainer  {{ Local-Cell-Group-InformationItem-AuditRsp-ExtIEs}}		OPTIONAL,
	...
}

Local-Cell-Group-InformationItem-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-CapacityConsumptionLaw		CRITICALITY ignore			EXTENSION E-DCHCapacityConsumptionLaw			PRESENCE	optional }|
	{ ID id-E-DCH-TDD-CapacityConsumptionLaw	CRITICALITY ignore			EXTENSION E-DCH-TDD-CapacityConsumptionLaw		PRESENCE	optional },
	...
}

Power-Local-Cell-Group-InformationList-AuditRsp	 ::= SEQUENCE (SIZE (1..maxLocalCellinNodeB)) OF ProtocolIE-Single-Container {{ Power-Local-Cell-Group-InformationItemIE-AuditRsp }}

Power-Local-Cell-Group-InformationItemIE-AuditRsp NBAP-PROTOCOL-IES ::= {
	{ ID	id-Power-Local-Cell-Group-InformationItem-AuditRsp			CRITICALITY		ignore			TYPE	Power-Local-Cell-Group-InformationItem-AuditRsp		PRESENCE	mandatory}
}

Power-Local-Cell-Group-InformationItem-AuditRsp ::= SEQUENCE {
	power-Local-Cell-Group-ID					Local-Cell-ID,
	maximumDL-PowerCapability					MaximumDL-PowerCapability,
	iE-Extensions								ProtocolExtensionContainer  {{ Power-Local-Cell-Group-InformationItem-AuditRsp-ExtIEs}}		OPTIONAL,
	...
}

Power-Local-Cell-Group-InformationItem-AuditRsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


-- **************************************************************
--
-- AUDIT FAILURE
--
-- **************************************************************

AuditFailure ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{AuditFailure-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{AuditFailure-Extensions}}			OPTIONAL,
	...
}

AuditFailure-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-Cause							CRITICALITY ignore			TYPE Cause						PRESENCE mandatory	}|
	{ ID id-CriticalityDiagnostics			CRITICALITY ignore			TYPE CriticalityDiagnostics		PRESENCE optional		},
	...
}

AuditFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMMON MEASUREMENT INITIATION REQUEST
--
-- **************************************************************

CommonMeasurementInitiationRequest ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CommonMeasurementInitiationRequest-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CommonMeasurementInitiationRequest-Extensions}}		OPTIONAL,
	...
}

CommonMeasurementInitiationRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-MeasurementID							CRITICALITY reject	TYPE MeasurementID				PRESENCE mandatory }|
	{ ID id-CommonMeasurementObjectType-CM-Rqst		CRITICALITY reject	TYPE CommonMeasurementObjectType-CM-Rqst		PRESENCE mandatory }|
	{ ID id-CommonMeasurementType					CRITICALITY reject	TYPE CommonMeasurementType		PRESENCE mandatory }|
	{ ID id-MeasurementFilterCoefficient			CRITICALITY reject	TYPE MeasurementFilterCoefficient		PRESENCE optional }|
	{ ID id-ReportCharacteristics					CRITICALITY reject	TYPE ReportCharacteristics		PRESENCE mandatory }|
	{ ID id-SFNReportingIndicator					CRITICALITY reject	TYPE FNReportingIndicator		PRESENCE mandatory }|
	{ ID id-SFN										CRITICALITY reject	TYPE SFN						PRESENCE optional },
	...
}

CommonMeasurementInitiationRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-CommonMeasurementAccuracy						CRITICALITY reject	EXTENSION CommonMeasurementAccuracy		PRESENCE optional}|
	{ ID id-MeasurementRecoveryBehavior						CRITICALITY ignore	EXTENSION MeasurementRecoveryBehavior		PRESENCE optional	}|
	{ ID id-RTWP-ReportingIndicator							CRITICALITY reject	EXTENSION RTWP-ReportingIndicator										PRESENCE optional}|
	{ ID id-RTWP-CellPortion-ReportingIndicator				CRITICALITY reject	EXTENSION RTWP-CellPortion-ReportingIndicator							PRESENCE optional}|
	{ ID id-Reference-ReceivedTotalWideBandPowerReporting	CRITICALITY ignore	EXTENSION Reference-ReceivedTotalWideBandPowerReporting			PRESENCE optional}|
	{ ID id-GANSS-Time-ID									CRITICALITY ignore	EXTENSION GANSS-Time-ID						PRESENCE optional},
	...
}

CommonMeasurementObjectType-CM-Rqst ::= CHOICE {
	cell							Cell-CM-Rqst,
	rACH							RACH-CM-Rqst,
	notUsed-cPCH					NULL,
	...,
	extension-CommonMeasurementObjectType-CM-Rqst		Extension-CommonMeasurementObjectType-CM-Rqst
}

Extension-CommonMeasurementObjectType-CM-Rqst	::= ProtocolIE-Single-Container {{ Extension-CommonMeasurementObjectType-CM-RqstIE }}

Extension-CommonMeasurementObjectType-CM-RqstIE NBAP-PROTOCOL-IES ::= {
	{ ID id-Power-Local-Cell-Group-choice-CM-Rqst	CRITICALITY reject	TYPE PowerLocalCellGroup-CM-Rqst	PRESENCE mandatory }|
	{ ID id-ERACH-CM-Rqst							CRITICALITY reject	TYPE ERACH-CM-Rqst			PRESENCE mandatory}
		-- FDD only
}

ERACH-CM-Rqst ::= SEQUENCE {
	c-ID							C-ID,
	iE-Extensions					ProtocolExtensionContainer  { { ERACHItem-CM-Rqst-ExtIEs} } OPTIONAL,
	...
}


ERACHItem-CM-Rqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Cell-CM-Rqst ::= SEQUENCE {
	c-ID							C-ID,
	timeSlot						TimeSlot	OPTIONAL, 	-- Applicable to 3.84Mcps TDD and 7.68Mcps TDD only
	iE-Extensions					ProtocolExtensionContainer  { { CellItem-CM-Rqst-ExtIEs} }		OPTIONAL,
	...
}

CellItem-CM-Rqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TimeSlotLCR-CM-Rqst						CRITICALITY reject	EXTENSION TimeSlotLCR				PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ID id-NeighbouringCellMeasurementInformation	CRITICALITY ignore	EXTENSION NeighbouringCellMeasurementInformation	PRESENCE optional }|
	{ID id-UARFCNforNt								CRITICALITY reject	EXTENSION UARFCN					PRESENCE optional }|
	-- Mandatory for 1.28Mcps TDD when using multiple frequencies and the requested common measurementype is the one except for "HS-DSCH Required Power" or "HS-DSCH Provided Bit Rate"
	{ID id-UPPCHPositionLCR							CRITICALITY reject	EXTENSION UPPCHPositionLCR			PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ID id-AdditionalTimeSlotListLCR				CRITICALITY ignore	EXTENSION AdditionalTimeSlotListLCR			PRESENCE optional },
	-- Applicable to 1.28Mcps TDD only
	...
}

RACH-CM-Rqst ::= SEQUENCE {
	c-ID							C-ID,
	commonTransportChannelID		CommonTransportChannelID,
	iE-Extensions					ProtocolExtensionContainer  { { RACHItem-CM-Rqst-ExtIEs} }		OPTIONAL,
	...
}

RACHItem-CM-Rqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PowerLocalCellGroup-CM-Rqst ::= SEQUENCE {
	powerLocalCellGroupID			Local-Cell-ID,
	iE-Extensions					ProtocolExtensionContainer {{ PowerLocalCellGroup-CM-Rqst-ExtIEs }}	OPTIONAL,
	...
}

PowerLocalCellGroup-CM-Rqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMMON MEASUREMENT INITIATION RESPONSE
--
-- **************************************************************

CommonMeasurementInitiationResponse ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CommonMeasurementInitiationResponse-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CommonMeasurementInitiationResponse-Extensions}}		OPTIONAL,
	...
}

CommonMeasurementInitiationResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-MeasurementID							CRITICALITY ignore		TYPE MeasurementID			PRESENCE	mandatory	}|
	{ ID id-CommonMeasurementObjectType-CM-Rsp		CRITICALITY ignore		TYPE CommonMeasurementObjectType-CM-Rsp		PRESENCE	optional	}|
	{ ID id-SFN										CRITICALITY ignore		TYPE SFN					PRESENCE	optional	}|
	{ ID id-CriticalityDiagnostics					CRITICALITY ignore		TYPE CriticalityDiagnostics		PRESENCE	optional	},
	...
}

CommonMeasurementInitiationResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-CommonMeasurementAccuracy				CRITICALITY ignore		EXTENSION CommonMeasurementAccuracy				PRESENCE optional }|
	{ ID id-MeasurementRecoverySupportIndicator		CRITICALITY ignore		EXTENSION MeasurementRecoverySupportIndicator		PRESENCE optional }|
	{ ID id-Reference-ReceivedTotalWideBandPowerSupportIndicator				CRITICALITY ignore							EXTENSION	Reference-ReceivedTotalWideBandPowerSupportIndicator		PRESENCE optional }|
	{ ID id-Reference-ReceivedTotalWideBandPower								CRITICALITY ignore		EXTENSION	Reference-ReceivedTotalWideBandPower						PRESENCE optional },
	...
}

CommonMeasurementObjectType-CM-Rsp ::= CHOICE {
	cell												Cell-CM-Rsp,
	rACH												RACH-CM-Rsp,
	notUsed-cPCH										NULL,
	...,
	extension-CommonMeasurementObjectType-CM-Rsp		Extension-CommonMeasurementObjectType-CM-Rsp
}

Extension-CommonMeasurementObjectType-CM-Rsp ::= ProtocolIE-Single-Container {{ Extension-CommonMeasurementObjectType-CM-RspIE }}

Extension-CommonMeasurementObjectType-CM-RspIE NBAP-PROTOCOL-IES ::= {
	{ ID id-Power-Local-Cell-Group-choice-CM-Rsp	CRITICALITY ignore		TYPE PowerLocalCellGroup-CM-Rsp	PRESENCE mandatory }|
	{ ID id-ERACH-CM-Rsp							CRITICALITY	ignore		TYPE ERACH-CM-Rsp		PRESENCE mandatory }
		-- FDD only
}

ERACH-CM-Rsp ::= SEQUENCE {
	commonMeasurementValue			CommonMeasurementValue,
	iE-Extensions					ProtocolExtensionContainer  { { ERACHItem-CM-Rsp-ExtIEs} } OPTIONAL,
	...
}


ERACHItem-CM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Cell-CM-Rsp ::= SEQUENCE {
	commonMeasurementValue			CommonMeasurementValue,
	iE-Extensions					ProtocolExtensionContainer  { { CellItem-CM-Rsp-ExtIEs} }		OPTIONAL,
	...
}

CellItem-CM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-AdditionalMeasurementValueList 		CRITICALITY ignore	EXTENSION AdditionalMeasurementValueList 	PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ID id-TimeSlotMeasurementValueListLCR	CRITICALITY ignore		EXTENSION TimeSlotMeasurementValueListLCR		PRESENCE optional },
-- Applicable to 1.28Mcps TDD, this IE is for the measurement value from the Primary frequency
	...
}

RACH-CM-Rsp ::= SEQUENCE {
	commonMeasurementValue			CommonMeasurementValue,
	iE-Extensions					ProtocolExtensionContainer  { { RACHItem-CM-Rsp-ExtIEs} }		OPTIONAL,
	...
}

RACHItem-CM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PowerLocalCellGroup-CM-Rsp ::= SEQUENCE {
	commonMeasurementValue			CommonMeasurementValue,
	iE-Extensions					ProtocolExtensionContainer {{ PowerLocalCellGroup-CM-Rsp-ExtIEs}}		OPTIONAL,
	...
}

PowerLocalCellGroup-CM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMMON MEASUREMENT INITIATION FAILURE
--
-- **************************************************************

CommonMeasurementInitiationFailure ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CommonMeasurementInitiationFailure-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CommonMeasurementInitiationFailure-Extensions}}		OPTIONAL,
	...
}

CommonMeasurementInitiationFailure-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-MeasurementID				CRITICALITY ignore			TYPE MeasurementID				PRESENCE	mandatory	}|
	{ ID id-Cause						CRITICALITY ignore			TYPE Cause						PRESENCE	mandatory	}|
	{ ID id-CriticalityDiagnostics		CRITICALITY ignore			TYPE CriticalityDiagnostics		PRESENCE	optional	},
	...
}

CommonMeasurementInitiationFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMMON MEASUREMENT REPORT
--
-- **************************************************************

CommonMeasurementReport ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CommonMeasurementReport-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CommonMeasurementReport-Extensions}}		OPTIONAL,
	...
}

CommonMeasurementReport-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-MeasurementID							CRITICALITY ignore		TYPE MeasurementID				PRESENCE	mandatory	}|
	{ ID id-CommonMeasurementObjectType-CM-Rprt		CRITICALITY ignore		TYPE CommonMeasurementObjectType-CM-Rprt		PRESENCE	mandatory	}|
	{ ID id-SFN										CRITICALITY ignore		TYPE SFN						PRESENCE	optional	},
	...
}

CommonMeasurementReport-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MeasurementRecoveryReportingIndicator	CRITICALITY ignore		EXTENSION MeasurementRecoveryReportingIndicator		PRESENCE optional }|
	{ ID id-Reference-ReceivedTotalWideBandPower	CRITICALITY ignore		EXTENSION Reference-ReceivedTotalWideBandPower		PRESENCE optional },
	...
}

CommonMeasurementObjectType-CM-Rprt ::= CHOICE {
	cell												Cell-CM-Rprt,
	rACH												RACH-CM-Rprt,
	notUsed-cPCH										NULL,
	...,
	extension-CommonMeasurementObjectType-CM-Rprt		Extension-CommonMeasurementObjectType-CM-Rprt
}

Extension-CommonMeasurementObjectType-CM-Rprt ::= ProtocolIE-Single-Container {{ Extension-CommonMeasurementObjectType-CM-RprtIE }}

Extension-CommonMeasurementObjectType-CM-RprtIE NBAP-PROTOCOL-IES ::= {
	{ ID id-Power-Local-Cell-Group-choice-CM-Rprt	CRITICALITY ignore		TYPE PowerLocalCellGroup-CM-Rprt	PRESENCE mandatory }|
	{ ID id-ERACH-CM-Rprt							CRITICALITY ignore		TYPE ERACH-CM-Rprt		PRESENCE mandatory },
	...
}

ERACH-CM-Rprt ::= SEQUENCE {
	commonMeasurementValueInformation	CommonMeasurementValueInformation,
	iE-Extensions						ProtocolExtensionContainer {{ ERACHItem-CM-Rprt-ExtIEs }} OPTIONAL,
	...
}

ERACHItem-CM-Rprt-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Cell-CM-Rprt ::= SEQUENCE {
	commonMeasurementValueInformation	CommonMeasurementValueInformation,
	iE-Extensions						ProtocolExtensionContainer  {{ CellItem-CM-Rprt-ExtIEs }}		OPTIONAL,
	...
}

CellItem-CM-Rprt-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-C-ID								CRITICALITY ignore		EXTENSION C-ID				PRESENCE optional}|
	{ID id-AdditionalMeasurementValueList 	CRITICALITY ignore		EXTENSION AdditionalMeasurementValueList	PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ID id-TimeSlotMeasurementValueListLCR	CRITICALITY ignore		EXTENSION TimeSlotMeasurementValueListLCR		PRESENCE optional },
-- Applicable to 1.28Mcps TDD, this IE is for the measurement value from the Primary frequency
	...
}


RACH-CM-Rprt ::= SEQUENCE {
	commonMeasurementValueInformation	CommonMeasurementValueInformation,
	iE-Extensions						ProtocolExtensionContainer {{ RACHItem-CM-Rprt-ExtIEs }}			OPTIONAL,
	...
}

RACHItem-CM-Rprt-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-C-ID			CRITICALITY ignore			EXTENSION C-ID				PRESENCE optional},
	...
}

PowerLocalCellGroup-CM-Rprt ::= SEQUENCE {
	commonMeasurementValueInformation	CommonMeasurementValueInformation,
	iE-Extensions						ProtocolExtensionContainer {{ PowerLocalCellGroup-CM-Rprt-ExtIEs}}	OPTIONAL,
	...
}

PowerLocalCellGroup-CM-Rprt-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMMON MEASUREMENT TERMINATION REQUEST
--
-- **************************************************************

CommonMeasurementTerminationRequest ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CommonMeasurementTerminationRequest-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CommonMeasurementTerminationRequest-Extensions}}		OPTIONAL,
	...
}

CommonMeasurementTerminationRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-MeasurementID			CRITICALITY ignore				TYPE MeasurementID			PRESENCE mandatory },
	...
}

CommonMeasurementTerminationRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMMON MEASUREMENT FAILURE INDICATION
--
-- **************************************************************

CommonMeasurementFailureIndication ::= SEQUENCE {
	protocolIEs					ProtocolIE-Container		{{CommonMeasurementFailureIndication-IEs}},
	protocolExtensions			ProtocolExtensionContainer	{{CommonMeasurementFailureIndication-Extensions}}				OPTIONAL,
	...
}

CommonMeasurementFailureIndication-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-MeasurementID			CRITICALITY ignore			TYPE MeasurementID			PRESENCE mandatory }|
	{ ID id-Cause					CRITICALITY ignore			TYPE Cause					PRESENCE mandatory },
	...
}

CommonMeasurementFailureIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- CELL SETUP REQUEST FDD
--
-- **************************************************************

CellSetupRequestFDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSetupRequestFDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSetupRequestFDD-Extensions}}		OPTIONAL,
	...
}

CellSetupRequestFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-Local-Cell-ID										CRITICALITY reject	TYPE Local-Cell-ID					PRESENCE mandatory }|
	{ ID id-C-ID												CRITICALITY reject	TYPE C-ID						PRESENCE mandatory }|
	{ ID id-ConfigurationGenerationID							CRITICALITY reject	TYPE ConfigurationGenerationID					PRESENCE mandatory }|
	{ ID id-T-Cell												CRITICALITY reject	TYPE T-Cell						PRESENCE mandatory }|
	{ ID id-UARFCNforNu											CRITICALITY reject	TYPE UARFCN						PRESENCE mandatory }|
	{ ID id-UARFCNforNd											CRITICALITY reject	TYPE UARFCN						PRESENCE mandatory }|
	{ ID id-MaximumTransmissionPower							CRITICALITY reject	TYPE MaximumTransmissionPower					PRESENCE mandatory }|
	{ ID id-Closed-Loop-Timing-Adjustment-Mode					CRITICALITY reject	TYPE Closedlooptimingadjustmentmode			PRESENCE optional }|
	{ ID id-PrimaryScramblingCode								CRITICALITY reject	TYPE PrimaryScramblingCode					PRESENCE mandatory }|
	{ ID id-Synchronisation-Configuration-Cell-SetupRqst		CRITICALITY reject	TYPE Synchronisation-Configuration-Cell-SetupRqst			PRESENCE	mandatory }|
	{ ID id-DL-TPC-Pattern01Count								CRITICALITY reject	TYPE DL-TPC-Pattern01Count					PRESENCE mandatory }|
	{ ID id-PrimarySCH-Information-Cell-SetupRqstFDD			CRITICALITY reject	TYPE PrimarySCH-Information-Cell-SetupRqstFDD				PRESENCE	mandatory }|
	{ ID id-SecondarySCH-Information-Cell-SetupRqstFDD			CRITICALITY reject	TYPE SecondarySCH-Information-Cell-SetupRqstFDD			PRESENCE mandatory }|
	{ ID id-PrimaryCPICH-Information-Cell-SetupRqstFDD			CRITICALITY reject	TYPE PrimaryCPICH-Information-Cell-SetupRqstFDD			PRESENCE	mandatory }|
	{ ID id-SecondaryCPICH-InformationList-Cell-SetupRqstFDD	CRITICALITY reject	TYPE SecondaryCPICH-InformationList-Cell-SetupRqstFDD	PRESENCE	optional }|
	{ ID id-PrimaryCCPCH-Information-Cell-SetupRqstFDD			CRITICALITY reject	TYPE PrimaryCCPCH-Information-Cell-SetupRqstFDD			PRESENCE	mandatory }|
	{ ID id-Limited-power-increase-information-Cell-SetupRqstFDD	CRITICALITY reject	TYPE Limited-power-increase-information-Cell-SetupRqstFDD		PRESENCE mandatory },
	...
}

CellSetupRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-IPDLParameter-Information-Cell-SetupRqstFDD		CRITICALITY reject	EXTENSION IPDLParameter-Information-Cell-SetupRqstFDD				PRESENCE optional }|
	{ ID id-CellPortion-InformationList-Cell-SetupRqstFDD	CRITICALITY reject	EXTENSION CellPortion-InformationList-Cell-SetupRqstFDD			PRESENCE optional }|
	{ ID id-MIMO-PilotConfiguration							CRITICALITY reject	EXTENSION MIMO-PilotConfiguration					PRESENCE optional }|
	{ ID id-MIMO-PilotConfigurationExtension				CRITICALITY reject	EXTENSION MIMO-PilotConfigurationExtension		PRESENCE optional }|
	{ ID id-MIMO-withfourtransmitantennas-PilotConfiguration	CRITICALITY reject	EXTENSION MIMO-withfourtransmitantennas-PilotConfiguration			PRESENCE optional },
...
}

Synchronisation-Configuration-Cell-SetupRqst ::= SEQUENCE {
	n-INSYNC-IND			N-INSYNC-IND,
 	n-OUTSYNC-IND			N-OUTSYNC-IND,
 	t-RLFAILURE				T-RLFAILURE,
	iE-Extensions			ProtocolExtensionContainer { { Synchronisation-Configuration-Cell-SetupRqst-ExtIEs} }		OPTIONAL,
	...
}

Synchronisation-Configuration-Cell-SetupRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PrimarySCH-Information-Cell-SetupRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
	primarySCH-Power						DL-Power,
	tSTD-Indicator							TSTD-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { PrimarySCH-Information-Cell-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

PrimarySCH-Information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SecondarySCH-Information-Cell-SetupRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
	secondarySCH-Power						DL-Power,
	tSTD-Indicator							TSTD-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { SecondarySCH-Information-Cell-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

SecondarySCH-Information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PrimaryCPICH-Information-Cell-SetupRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
	primaryCPICH-Power						PrimaryCPICH-Power,
	transmitDiversityIndicator				TransmitDiversityIndicator,
	iE-Extensions							ProtocolExtensionContainer { { PrimaryCPICH-Information-Cell-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

PrimaryCPICH-Information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SecondaryCPICH-InformationList-Cell-SetupRqstFDD ::= SEQUENCE (SIZE (1..maxSCPICHCell)) OF ProtocolIE-Single-Container{{ SecondaryCPICH-InformationItemIE-Cell-SetupRqstFDD }}

SecondaryCPICH-InformationItemIE-Cell-SetupRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-SecondaryCPICH-InformationItem-Cell-SetupRqstFDD		CRITICALITY reject	TYPE SecondaryCPICH-InformationItem-Cell-SetupRqstFDD		PRESENCE mandatory}
}

SecondaryCPICH-InformationItem-Cell-SetupRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
	dl-ScramblingCode						DL-ScramblingCode,
	fDD-DL-ChannelisationCodeNumber			FDD-DL-ChannelisationCodeNumber,
	secondaryCPICH-Power					DL-Power,
	transmitDiversityIndicator				TransmitDiversityIndicator,
	iE-Extensions							ProtocolExtensionContainer { { SecondaryCPICH-InformationItem-Cell-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

SecondaryCPICH-InformationItem-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PrimaryCCPCH-Information-Cell-SetupRqstFDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
	bCH-information							BCH-Information-Cell-SetupRqstFDD,
	sTTD-Indicator							STTD-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { PrimaryCCPCH-Information-Cell-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

PrimaryCCPCH-Information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

BCH-Information-Cell-SetupRqstFDD ::= SEQUENCE {
 	commonTransportChannelID				CommonTransportChannelID,
 	bCH-Power								DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { BCH-Information-Cell-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
 }

BCH-Information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Limited-power-increase-information-Cell-SetupRqstFDD ::= SEQUENCE {
	powerRaiseLimit							PowerRaiseLimit,
	dLPowerAveragingWindowSize				DLPowerAveragingWindowSize,
	iE-Extensions							ProtocolExtensionContainer { { Limited-power-increase-information-Cell-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

Limited-power-increase-information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

IPDLParameter-Information-Cell-SetupRqstFDD::= SEQUENCE {
	iPDL-FDD-Parameters						IPDL-FDD-Parameters,
	iPDL-Indicator							IPDL-Indicator,	
	iE-Extensions							ProtocolExtensionContainer { { IPDLParameter-Information-Cell-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

IPDLParameter-Information-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellPortion-InformationList-Cell-SetupRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCell)) OF ProtocolIE-Single-Container{{ CellPortion-InformationItemIE-Cell-SetupRqstFDD }}

CellPortion-InformationItemIE-Cell-SetupRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-CellPortion-InformationItem-Cell-SetupRqstFDD	CRITICALITY reject	TYPE CellPortion-InformationItem-Cell-SetupRqstFDD					PRESENCE mandatory }
}

CellPortion-InformationItem-Cell-SetupRqstFDD::= SEQUENCE {
	cellPortionID							CellPortionID,
	associatedSecondaryCPICH				CommonPhysicalChannelID,
	maximumTransmissionPowerforCellPortion	MaximumTransmissionPower,
	iE-Extensions							ProtocolExtensionContainer { { CellPortion-InformationItem-Cell-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

CellPortion-InformationItem-Cell-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
...
}

-- **************************************************************
--
-- CELL SETUP REQUEST TDD
--
-- **************************************************************

CellSetupRequestTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSetupRequestTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSetupRequestTDD-Extensions}}		OPTIONAL,
	...
}

CellSetupRequestTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-Local-Cell-ID									CRITICALITY reject	TYPE Local-Cell-ID					PRESENCE mandatory }|
	{ ID id-C-ID											CRITICALITY reject	TYPE C-ID							PRESENCE mandatory }|
	{ ID id-ConfigurationGenerationID						CRITICALITY reject	TYPE ConfigurationGenerationID					PRESENCE mandatory }|
	{ ID id-UARFCNforNt										CRITICALITY reject	TYPE UARFCN							PRESENCE mandatory }|	-- For 1.28Mcps TDD, if multiple frequencies exist within the cell indicated by C-ID, this IE indicates the frequency of Primary frequency
	{ ID id-CellParameterID									CRITICALITY reject	TYPE CellParameterID					PRESENCE mandatory }|
	-- For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, this IE indicate the Preamble code used in the Speial Time Slot (TS 25.221 [19])
	{ ID id-MaximumTransmissionPower						CRITICALITY reject	TYPE MaximumTransmissionPower					PRESENCE mandatory }|
	{ ID id-TransmissionDiversityApplied					CRITICALITY reject	TYPE TransmissionDiversityApplied					PRESENCE mandatory }|
	{ ID id-SyncCase										CRITICALITY reject	TYPE SyncCase						PRESENCE mandatory }|
	{ ID id-Synchronisation-Configuration-Cell-SetupRqst	CRITICALITY reject	TYPE Synchronisation-Configuration-Cell-SetupRqst	PRESENCE mandatory }|
	{ ID id-DPCHConstant									CRITICALITY reject	TYPE ConstantValue					PRESENCE mandatory }|	-- This IE shall be ignored by the Node B.
	{ ID id-PUSCHConstant									CRITICALITY reject	TYPE ConstantValue					PRESENCE mandatory }|	-- This IE shall be ignored by the Node B.
	{ ID id-PRACHConstant									CRITICALITY reject	TYPE ConstantValue					PRESENCE mandatory }|	-- This IE shall be ignored by the Node B.
	{ ID id-TimingAdvanceApplied							CRITICALITY reject	TYPE TimingAdvanceApplied					PRESENCE mandatory }|
	{ ID id-SCH-Information-Cell-SetupRqstTDD				CRITICALITY reject	TYPE SCH-Information-Cell-SetupRqstTDD				PRESENCE optional }|	-- Mandatory for 3.84Mcps TDD and 7.68Mcps TDD, Not Applicable to 1.28Mcps TDD
	{ ID id-PCCPCH-Information-Cell-SetupRqstTDD			CRITICALITY reject	TYPE PCCPCH-Information-Cell-SetupRqstTDD			PRESENCE optional }|	-- Mandatory for 3.84Mcps TDD, Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD
	{ ID id-TimeSlotConfigurationList-Cell-SetupRqstTDD		CRITICALITY reject	TYPE TimeSlotConfigurationList-Cell-SetupRqstTDD	PRESENCE optional },	-- Mandatory for 3.84Mcps TDD and 7.68Mcps TDD, Not Applicable to 1.28Mcps TDD
	...
}

CellSetupRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TimeSlotConfigurationList-LCR-Cell-SetupRqstTDD		CRITICALITY reject	EXTENSION TimeSlotConfigurationList-LCR-Cell-SetupRqstTDD		PRESENCE optional }|	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. If multiple frequencies exist within the cell indicated by C-ID, this IE indicates the Time Slot configuration of Primary frequency.
	{ ID id-PCCPCH-LCR-Information-Cell-SetupRqstTDD			CRITICALITY reject	EXTENSION PCCPCH-LCR-Information-Cell-SetupRqstTDD				PRESENCE optional }|	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD, For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, PCCPCH is deployed on the MBSFN Special Time Slot (TS 25.221 [19]).
	{ ID id-DwPCH-LCR-Information-Cell-SetupRqstTDD				CRITICALITY reject	EXTENSION DwPCH-LCR-Information-Cell-SetupRqstTDD				PRESENCE optional }|	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD
	{ ID id-ReferenceSFNoffset									CRITICALITY ignore	EXTENSION ReferenceSFNoffset										PRESENCE optional }|
	{ ID id-IPDLParameter-Information-Cell-SetupRqstTDD			CRITICALITY reject	EXTENSION IPDLParameter-Information-Cell-SetupRqstTDD			PRESENCE optional }|	-- Applicable to 3.84Mcps TDD and 7.68Mcps TDD only
	{ ID id-IPDLParameter-Information-LCR-Cell-SetupRqstTDD		CRITICALITY reject	EXTENSION IPDLParameter-Information-LCR-Cell-SetupRqstTDD	PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
	{ ID id-PCCPCH-768-Information-Cell-SetupRqstTDD			CRITICALITY reject	EXTENSION PCCPCH-768-Information-Cell-SetupRqstTDD				PRESENCE optional }|	-- Mandatory for 7.68Mcps TDD, Not Applicable to 3.84Mcps TDD or 1.28Mcps TDD
	{ ID id-SCH-768-Information-Cell-SetupRqstTDD				CRITICALITY reject	EXTENSION SCH-768-Information-Cell-SetupRqstTDD				PRESENCE optional }|	-- Mandatory for 7.68Mcps TDD, Not Applicable to 3.84Mcps TDD or 1.28Mcps TDD
	{ ID id-MBSFN-Only-Mode-Indicator-Cell-SetupRqstTDD-LCR		CRITICALITY reject	EXTENSION MBSFN-Only-Mode-Indicator									PRESENCE optional }|
	{ ID id-Cell-Frequency-List-LCR-MulFreq-Cell-SetupRqstTDD	CRITICALITY reject	EXTENSION Cell-Frequency-List-LCR-MulFreq-Cell-SetupRqstTDD		PRESENCE optional },  -- Mandatory for 1.28Mcps TDD when using multiple frequencies
	...
}

SCH-Information-Cell-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
	syncCaseIndicator						SyncCaseIndicator-Cell-SetupRqstTDD-PSCH,
	sCH-Power								DL-Power,
	tSTD-Indicator							TSTD-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { SCH-Information-Cell-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

SCH-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SyncCaseIndicator-Cell-SetupRqstTDD-PSCH ::= ProtocolIE-Single-Container {{ SyncCaseIndicatorIE-Cell-SetupRqstTDD-PSCH }}

SyncCaseIndicatorIE-Cell-SetupRqstTDD-PSCH NBAP-PROTOCOL-IES ::= {
	{ ID id-SyncCaseIndicatorItem-Cell-SetupRqstTDD-PSCH   CRITICALITY reject	TYPE SyncCaseIndicatorItem-Cell-SetupRqstTDD-PSCH		PRESENCE mandatory }
}

SyncCaseIndicatorItem-Cell-SetupRqstTDD-PSCH ::= CHOICE {
	case1								Case1-Cell-SetupRqstTDD,
	case2								Case2-Cell-SetupRqstTDD,
	...
}

Case1-Cell-SetupRqstTDD ::= SEQUENCE {
	timeSlot							TimeSlot,
	iE-Extensions						ProtocolExtensionContainer { { Case1Item-Cell-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

Case1Item-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Case2-Cell-SetupRqstTDD ::= SEQUENCE {
	sCH-TimeSlot						SCH-TimeSlot,
	iE-Extensions						ProtocolExtensionContainer { { Case2Item-Cell-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

Case2Item-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PCCPCH-Information-Cell-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
	tdd-PhysicalChannelOffset				TDD-PhysicalChannelOffset,
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	pCCPCH-Power							PCCPCH-Power,
	sCTD-Indicator							SCTD-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { PCCPCH-Information-Cell-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PCCPCH-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TimeSlotConfigurationList-Cell-SetupRqstTDD ::= SEQUENCE (SIZE (1..15)) OF TimeSlotConfigurationItem-Cell-SetupRqstTDD

TimeSlotConfigurationItem-Cell-SetupRqstTDD ::= SEQUENCE {
	timeSlot								TimeSlot,
	timeSlotStatus							TimeSlotStatus,
	timeSlotDirection						TimeSlotDirection,
	iE-Extensions							ProtocolExtensionContainer { { TimeSlotConfigurationItem-Cell-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

TimeSlotConfigurationItem-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MBSFN-Cell-ParameterID-Cell-SetupRqstTDD			CRITICALITY reject	EXTENSION CellParameterID		PRESENCE optional },-- Applicable only to for MBSFN only mode
	...
}

TimeSlotConfigurationList-LCR-Cell-SetupRqstTDD ::= SEQUENCE (SIZE (1..7)) OF TimeSlotConfigurationItem-LCR-Cell-SetupRqstTDD

TimeSlotConfigurationItem-LCR-Cell-SetupRqstTDD ::= SEQUENCE {
	timeSlotLCR								TimeSlotLCR,
	timeSlotStatus							TimeSlotStatus,
	timeSlotDirection						TimeSlotDirection,
	iE-Extensions							ProtocolExtensionContainer { { TimeSlotConfigurationItem-LCR-Cell-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

TimeSlotConfigurationItem-LCR-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Time-Slot-Parameter-ID							CRITICALITY reject			EXTENSION CellParameterID				PRESENCE optional },
	...
}

PCCPCH-LCR-Information-Cell-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
	tdd-PhysicalChannelOffset				TDD-PhysicalChannelOffset,
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	pCCPCH-Power							PCCPCH-Power,
	sCTD-Indicator							SCTD-Indicator,
	tSTD-Indicator							TSTD-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { PCCPCH-LCR-Information-Cell-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PCCPCH-LCR-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DwPCH-LCR-Information-Cell-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelId			CommonPhysicalChannelID,
	tSTD-Indicator					TSTD-Indicator,
	dwPCH-Power						DwPCH-Power,
	iE-Extensions					ProtocolExtensionContainer { { DwPCH-LCR-Information-Cell-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

DwPCH-LCR-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

IPDLParameter-Information-Cell-SetupRqstTDD ::= SEQUENCE {
	iPDL-TDD-Parameters						IPDL-TDD-Parameters,
	iPDL-Indicator							IPDL-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { IPDLParameter-Information-Cell-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

IPDLParameter-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

IPDLParameter-Information-LCR-Cell-SetupRqstTDD ::= SEQUENCE {
	iPDL-TDD-Parameters-LCR					IPDL-TDD-Parameters-LCR,
	iPDL-Indicator							IPDL-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { IPDLParameter-Information-LCR-Cell-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

IPDLParameter-Information-LCR-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PCCPCH-768-Information-Cell-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID768				CommonPhysicalChannelID768,
	tdd-PhysicalChannelOffset				TDD-PhysicalChannelOffset,
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	pCCPCH-Power							PCCPCH-Power,
	sCTD-Indicator							SCTD-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { PCCPCH-768-Information-Cell-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PCCPCH-768-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SCH-768-Information-Cell-SetupRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID768				CommonPhysicalChannelID768,
	syncCaseIndicator						SyncCaseIndicator-Cell-SetupRqstTDD-PSCH,
	sCH-Power								DL-Power,
	tSTD-Indicator							TSTD-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { SCH-768-Information-Cell-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

SCH-768-Information-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Cell-Frequency-List-LCR-MulFreq-Cell-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxFrequencyinCell-1)) OF Cell-Frequency-Item-LCR-MulFreq-Cell-SetupRqstTDD

Cell-Frequency-Item-LCR-MulFreq-Cell-SetupRqstTDD ::= SEQUENCE {
	uARFCN													UARFCN,
	-- This IE indicates the frequency of  Secondary frequency 
	timeSlotConfigurationList-LCR-Cell-SetupRqstTDD			TimeSlotConfigurationList-LCR-Cell-SetupRqstTDD,
	-- This IE indicates the Time Slot configuration of Secondary frequency 
	iE-Extensions							ProtocolExtensionContainer { { Cell-Frequency-Item-LCR-MulFreq-Cell-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

Cell-Frequency-Item-LCR-MulFreq-Cell-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- CELL SETUP RESPONSE
--
-- **************************************************************

CellSetupResponse ::= SEQUENCE {
	protocolIEs					ProtocolIE-Container		{{CellSetupResponse-IEs}},
	protocolExtensions			ProtocolExtensionContainer	{{CellSetupResponse-Extensions}}		OPTIONAL,
	...
}

CellSetupResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CriticalityDiagnostics		CRITICALITY ignore			TYPE CriticalityDiagnostics		PRESENCE optional },
	...
}

CellSetupResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- CELL SETUP FAILURE
--
-- **************************************************************

CellSetupFailure ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSetupFailure-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSetupFailure-Extensions}}			OPTIONAL,
	...
}

CellSetupFailure-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-Cause							CRITICALITY ignore			TYPE Cause						PRESENCE mandatory	}|
	{ ID id-CriticalityDiagnostics			CRITICALITY ignore			TYPE CriticalityDiagnostics		PRESENCE optional	},
	...
}

CellSetupFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- CELL RECONFIGURATION REQUEST FDD
--
-- **************************************************************

CellReconfigurationRequestFDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellReconfigurationRequestFDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellReconfigurationRequestFDD-Extensions}} 		OPTIONAL,
	...
}

CellReconfigurationRequestFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-C-ID													CRITICALITY reject	TYPE C-ID												PRESENCE mandatory }|
	{ ID	id-ConfigurationGenerationID							CRITICALITY reject	TYPE ConfigurationGenerationID									PRESENCE mandatory }|
	{ ID	id-MaximumTransmissionPower								CRITICALITY reject	TYPE MaximumTransmissionPower									PRESENCE optional }|
	{ ID	id-Synchronisation-Configuration-Cell-ReconfRqst		CRITICALITY reject	TYPE Synchronisation-Configuration-Cell-ReconfRqst		PRESENCE optional }|
	{ ID	id-PrimarySCH-Information-Cell-ReconfRqstFDD			CRITICALITY reject	TYPE PrimarySCH-Information-Cell-ReconfRqstFDD			PRESENCE optional }|
	{ ID	id-SecondarySCH-Information-Cell-ReconfRqstFDD			CRITICALITY reject	TYPE SecondarySCH-Information-Cell-ReconfRqstFDD			PRESENCE optional }|
	{ ID	id-PrimaryCPICH-Information-Cell-ReconfRqstFDD			CRITICALITY reject	TYPE PrimaryCPICH-Information-Cell-ReconfRqstFDD			PRESENCE optional }|
	{ ID	id-SecondaryCPICH-InformationList-Cell-ReconfRqstFDD	CRITICALITY reject	TYPE SecondaryCPICH-InformationList-Cell-ReconfRqstFDD		PRESENCE optional }|
	{ ID	id-PrimaryCCPCH-Information-Cell-ReconfRqstFDD			CRITICALITY reject	TYPE PrimaryCCPCH-Information-Cell-ReconfRqstFDD			PRESENCE optional },
	...
}

CellReconfigurationRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-IPDLParameter-Information-Cell-ReconfRqstFDD	CRITICALITY reject	EXTENSION IPDLParameter-Information-Cell-ReconfRqstFDD					PRESENCE optional }|
	{ ID id-CellPortion-InformationList-Cell-ReconfRqstFDD	CRITICALITY reject	EXTENSION CellPortion-InformationList-Cell-ReconfRqstFDD			PRESENCE optional }|
	{ ID id-MIMO-PilotConfiguration							CRITICALITY reject	EXTENSION MIMO-PilotConfiguration					PRESENCE optional }|
	{ ID id-MIMO-PilotConfigurationExtension				CRITICALITY reject	EXTENSION MIMO-PilotConfigurationExtension		PRESENCE optional }|
	{ ID id-DormantModeIndicator							CRITICALITY reject	EXTENSION DormantModeIndicator						PRESENCE optional }|
	{ ID id-MIMO-withfourtransmitantennas-PilotConfiguration	CRITICALITY reject	EXTENSION MIMO-withfourtransmitantennas-PilotConfiguration			PRESENCE optional },
	...
}

Synchronisation-Configuration-Cell-ReconfRqst ::= SEQUENCE {
	n-INSYNC-IND			N-INSYNC-IND,
 	n-OUTSYNC-IND			N-OUTSYNC-IND,
 	t-RLFAILURE				T-RLFAILURE,
	iE-Extensions			ProtocolExtensionContainer { { Synchronisation-Configuration-Cell-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Synchronisation-Configuration-Cell-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PrimarySCH-Information-Cell-ReconfRqstFDD ::= SEQUENCE {
 	commonPhysicalChannelID					CommonPhysicalChannelID,
 	primarySCH-Power						DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { PrimarySCH-Information-Cell-ReconfRqstFDD-ExtIEs} }		OPTIONAL,
	...
 }

PrimarySCH-Information-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SecondarySCH-Information-Cell-ReconfRqstFDD ::= SEQUENCE {
 	commonPhysicalChannelID					CommonPhysicalChannelID,
 	secondarySCH-Power						DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { SecondarySCH-Information-Cell-ReconfRqstFDD-ExtIEs} }		OPTIONAL,
	...
 }

SecondarySCH-Information-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PrimaryCPICH-Information-Cell-ReconfRqstFDD ::= SEQUENCE {
 	commonPhysicalChannelID					CommonPhysicalChannelID,
	primaryCPICH-Power						PrimaryCPICH-Power,
	iE-Extensions							ProtocolExtensionContainer { { PrimaryCPICH-Information-Cell-ReconfRqstFDD-ExtIEs} }		OPTIONAL,
	...
 }

PrimaryCPICH-Information-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SecondaryCPICH-InformationList-Cell-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxSCPICHCell)) OF ProtocolIE-Single-Container{{ SecondaryCPICH-InformationItemIE-Cell-ReconfRqstFDD }}

SecondaryCPICH-InformationItemIE-Cell-ReconfRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID	id-SecondaryCPICH-InformationItem-Cell-ReconfRqstFDD	CRITICALITY reject	TYPE	SecondaryCPICH-InformationItem-Cell-ReconfRqstFDD		PRESENCE mandatory }
}

SecondaryCPICH-InformationItem-Cell-ReconfRqstFDD ::= SEQUENCE {
 	commonPhysicalChannelID					CommonPhysicalChannelID,
 	secondaryCPICH-Power					DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { SecondaryCPICH-InformationItem-Cell-ReconfRqstFDD-ExtIEs} }		OPTIONAL,
	...
 }

SecondaryCPICH-InformationItem-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}
 
PrimaryCCPCH-Information-Cell-ReconfRqstFDD ::= SEQUENCE {
 	bCH-information							BCH-information-Cell-ReconfRqstFDD,
	iE-Extensions							ProtocolExtensionContainer { { PrimaryCCPCH-Information-Cell-ReconfRqstFDD-ExtIEs} }		OPTIONAL,
	...
 }

PrimaryCCPCH-Information-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

BCH-information-Cell-ReconfRqstFDD ::= SEQUENCE {
 	commonTransportChannelID				CommonTransportChannelID,
 	bCH-Power								DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { BCH-information-Cell-ReconfRqstFDD-ExtIEs} }		OPTIONAL,
	...
 }

BCH-information-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

IPDLParameter-Information-Cell-ReconfRqstFDD::= SEQUENCE {
	iPDL-FDD-Parameters							IPDL-FDD-Parameters		OPTIONAL,
	iPDL-Indicator								IPDL-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { IPDLParameter-Information-Cell-ReconfRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

IPDLParameter-Information-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellPortion-InformationList-Cell-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCell)) OF ProtocolIE-Single-Container{{ CellPortion-InformationItemIE-Cell-ReconfRqstFDD }}

CellPortion-InformationItemIE-Cell-ReconfRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-CellPortion-InformationItem-Cell-ReconfRqstFDD	CRITICALITY reject	TYPE CellPortion-InformationItem-Cell-ReconfRqstFDD					PRESENCE	mandatory}
}

CellPortion-InformationItem-Cell-ReconfRqstFDD::= SEQUENCE {
	cellPortionID							CellPortionID,
	maximumTransmissionPowerforCellPortion	MaximumTransmissionPower,
	iE-Extensions							ProtocolExtensionContainer { { CellPortion-InformationItem-Cell-ReconfRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

CellPortion-InformationItem-Cell-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
...
}

-- **************************************************************
--
-- CELL RECONFIGURATION REQUEST TDD
--
-- **************************************************************

CellReconfigurationRequestTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellReconfigurationRequestTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellReconfigurationRequestTDD-Extensions}}		OPTIONAL,
	...
}

CellReconfigurationRequestTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-C-ID											CRITICALITY reject	TYPE C-ID						PRESENCE mandatory }|
	{ ID id-ConfigurationGenerationID						CRITICALITY reject	TYPE ConfigurationGenerationID				PRESENCE mandatory }|
	{ ID id-Synchronisation-Configuration-Cell-ReconfRqst	CRITICALITY reject	TYPE Synchronisation-Configuration-Cell-ReconfRqst		PRESENCE optional }|
	{ ID id-TimingAdvanceApplied							CRITICALITY reject	TYPE TimingAdvanceApplied				PRESENCE optional }|
	{ ID id-SCH-Information-Cell-ReconfRqstTDD				CRITICALITY reject	TYPE SCH-Information-Cell-ReconfRqstTDD		PRESENCE optional }|
	-- Applicable to 3.84Mcps TDD only
	{ ID id-PCCPCH-Information-Cell-ReconfRqstTDD			CRITICALITY reject	TYPE PCCPCH-Information-Cell-ReconfRqstTDD	PRESENCE optional }|
	-- Not applicable to 7.68Mcps TDD only. For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, PCCPCH is deployed on the MBSFN Special Time Slot (TS 25.221 [19]).
	{ ID id-MaximumTransmissionPower						CRITICALITY reject	TYPE MaximumTransmissionPower				PRESENCE optional }|
	{ ID id-DPCHConstant									CRITICALITY reject	TYPE ConstantValue				PRESENCE optional }|
	-- This IE shall be ignored by the Node B.
	{ ID id-PUSCHConstant									CRITICALITY reject	TYPE ConstantValue				PRESENCE optional }|
	-- This IE shall be ignored by the Node B.
	{ ID id-PRACHConstant									CRITICALITY reject	TYPE ConstantValue				PRESENCE optional }|
	-- This IE shall be ignored by the Node B.
	{ ID id-TimeSlotConfigurationList-Cell-ReconfRqstTDD	CRITICALITY reject	TYPE TimeSlotConfigurationList-Cell-ReconfRqstTDD		PRESENCE optional },
	-- Mandatory for 3.84Mcps TDD and 7.68Mcps TDD only. Not Applicable to 1.28Mcps TDD.
	...
}

CellReconfigurationRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-TimeSlotConfigurationList-LCR-Cell-ReconfRqstTDD	CRITICALITY reject	EXTENSION TimeSlotConfigurationList-LCR-Cell-ReconfRqstTDD	PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only, If multiple frequencies exist within the cell indicated by C-ID, this IE indicates the Time Slot reconfiguration of Primary frequency 
	{ ID	id-DwPCH-LCR-Information-Cell-ReconfRqstTDD			CRITICALITY reject	EXTENSION DwPCH-LCR-Information-Cell-ReconfRqstTDD			PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
	{ ID	id-IPDLParameter-Information-Cell-ReconfRqstTDD		CRITICALITY reject	EXTENSION IPDLParameter-Information-Cell-ReconfRqstTDD		PRESENCE optional }|	-- Applicable to 3.84Mcps TDD and 7.68Mcps TDD only
	{ ID	id-IPDLParameter-Information-LCR-Cell-ReconfRqstTDD	CRITICALITY reject	EXTENSION IPDLParameter-Information-LCR-Cell-ReconfRqstTDD	PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
	{ ID id-SCH-768-Information-Cell-ReconfRqstTDD				CRITICALITY reject	EXTENSION SCH-768-Information-Cell-ReconfRqstTDD				PRESENCE optional }|	-- Applicable to 7.68Mcps TDD only
	{ ID id-PCCPCH-768-Information-Cell-ReconfRqstTDD			CRITICALITY reject	EXTENSION PCCPCH-768-Information-Cell-ReconfRqstTDD			PRESENCE optional }|	-- Applicable to 7.68Mcps TDD only
	{ ID id-UARFCN-Adjustment									CRITICALITY reject	EXTENSION UARFCN-Adjustment		PRESENCE optional }|	-- Applicable to 1.28Mcps TDD when using multiple frequencies
	{ ID id-DormantModeIndicator							CRITICALITY reject	EXTENSION DormantModeIndicator		PRESENCE optional },	
...
}

SCH-Information-Cell-ReconfRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
	sCH-Power								DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { PSCH-Information-Cell-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PSCH-Information-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PCCPCH-Information-Cell-ReconfRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
	pCCPCH-Power							PCCPCH-Power,
	iE-Extensions							ProtocolExtensionContainer { { PCCPCH-Information-Cell-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PCCPCH-Information-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TimeSlotConfigurationList-Cell-ReconfRqstTDD ::= SEQUENCE (SIZE (1..15)) OF TimeSlotConfigurationItem-Cell-ReconfRqstTDD

TimeSlotConfigurationItem-Cell-ReconfRqstTDD ::= SEQUENCE {
	timeSlot								TimeSlot,
 	timeSlotStatus							TimeSlotStatus,
 	timeSlotDirection						TimeSlotDirection,
	iE-Extensions							ProtocolExtensionContainer { { TimeSlotConfigurationItem-Cell-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
 }

TimeSlotConfigurationItem-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MBSFN-Cell-ParameterID-Cell-ReconfRqstTDD			CRITICALITY reject	EXTENSION 	CellParameterID		PRESENCE optional },
	...
}

TimeSlotConfigurationList-LCR-Cell-ReconfRqstTDD ::= SEQUENCE (SIZE (1..7)) OF TimeSlotConfigurationItem-LCR-Cell-ReconfRqstTDD

TimeSlotConfigurationItem-LCR-Cell-ReconfRqstTDD ::= SEQUENCE {
	timeSlotLCR								TimeSlotLCR,
 	timeSlotStatus							TimeSlotStatus,
 	timeSlotDirection						TimeSlotDirection,
	iE-Extensions							ProtocolExtensionContainer { { TimeSlotConfigurationItem-LCR-Cell-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
 }

TimeSlotConfigurationItem-LCR-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DwPCH-LCR-Information-Cell-ReconfRqstTDD ::= SEQUENCE {
	commonPhysicalChannelId					CommonPhysicalChannelID,
 	dwPCH-Power								DwPCH-Power,
	iE-Extensions							ProtocolExtensionContainer { { DwPCH-LCR-Information-Cell-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
 }

DwPCH-LCR-Information-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

IPDLParameter-Information-Cell-ReconfRqstTDD ::= SEQUENCE {
	iPDL-TDD-Parameters						IPDL-TDD-Parameters		OPTIONAL,
	iPDL-Indicator							IPDL-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { IPDLParameter-Information-Cell-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

IPDLParameter-Information-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

IPDLParameter-Information-LCR-Cell-ReconfRqstTDD ::= SEQUENCE {
	iPDL-TDD-Parameters-LCR					IPDL-TDD-Parameters-LCR		OPTIONAL,
	iPDL-Indicator							IPDL-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { IPDLParameter-Information-LCR-Cell-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

IPDLParameter-Information-LCR-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SCH-768-Information-Cell-ReconfRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID768				CommonPhysicalChannelID768,
	sCH-Power								DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { PSCH-768-Information-Cell-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PSCH-768-Information-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PCCPCH-768-Information-Cell-ReconfRqstTDD ::= SEQUENCE {
	commonPhysicalChannelID768				CommonPhysicalChannelID768,
	pCCPCH-Power							PCCPCH-Power,
	iE-Extensions							ProtocolExtensionContainer { { PCCPCH-768-Information-Cell-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

PCCPCH-768-Information-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UARFCN-Adjustment::= CHOICE {
	cell-Frequency-Add-LCR-MulFreq-Cell-ReconfRqstTDD				Cell-Frequency-Add-LCR-MulFreq-Cell-ReconfRqstTDD,
	cell-Frequency-ModifyList-LCR-MulFreq-Cell-ReconfRqstTDD		Cell-Frequency-ModifyList-LCR-MulFreq-Cell-ReconfRqstTDD,
	cell-Frequency-Delete-LCR-MulFreq-Cell-ReconfRqstTDD			Cell-Frequency-Delete-LCR-MulFreq-Cell-ReconfRqstTDD,
	...
}

Cell-Frequency-Add-LCR-MulFreq-Cell-ReconfRqstTDD ::= SEQUENCE {
	uARFCN													UARFCN,
	-- This IE indicates the frequency of  Secondary frequency to add
	timeSlotConfigurationList-LCR-Cell-ReconfRqstTDD		TimeSlotConfigurationList-LCR-Cell-ReconfRqstTDD,
	-- This IE indicates the Time Slot configuration of Secondary frequency to add
	iE-Extensions							ProtocolExtensionContainer { { Cell-Frequency-Add-LCR-MulFreq-Cell-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

Cell-Frequency-Add-LCR-MulFreq-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Cell-Frequency-ModifyList-LCR-MulFreq-Cell-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxFrequencyinCell-1)) OF Cell-Frequency-ModifyItem-LCR-MulFreq-Cell-ReconfRqstTDD

Cell-Frequency-ModifyItem-LCR-MulFreq-Cell-ReconfRqstTDD ::= SEQUENCE {
	uARFCN													UARFCN,
	-- This IE indicates the frequency of  Secondary frequency to modify
	timeSlotConfigurationList-LCR-Cell-ReconfRqstTDD		TimeSlotConfigurationList-LCR-Cell-ReconfRqstTDD,
	-- This IE indicates the Time Slot reconfiguration of Secondary frequency 
	iE-Extensions							ProtocolExtensionContainer { { Cell-Frequency-ModifyItem-LCR-MulFreq-Cell-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

Cell-Frequency-ModifyItem-LCR-MulFreq-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Cell-Frequency-Delete-LCR-MulFreq-Cell-ReconfRqstTDD ::= SEQUENCE {
	uARFCN													UARFCN,
	-- This IE indicates the frequency of  Secondary  Frequency to delete
	iE-Extensions							ProtocolExtensionContainer { { Cell-Frequency-Delete-LCR-MulFreq-Cell-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

Cell-Frequency-Delete-LCR-MulFreq-Cell-ReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- CELL RECONFIGURATION RESPONSE
--
-- **************************************************************

CellReconfigurationResponse ::= SEQUENCE {
	protocolIEs					ProtocolIE-Container		{{CellReconfigurationResponse-IEs}},
	protocolExtensions			ProtocolExtensionContainer	{{CellReconfigurationResponse-Extensions}}		OPTIONAL,
	...
}

CellReconfigurationResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CriticalityDiagnostics		CRITICALITY ignore			TYPE CriticalityDiagnostics		PRESENCE optional },
	...
}

CellReconfigurationResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- CELL RECONFIGURATION FAILURE
--
-- **************************************************************

CellReconfigurationFailure ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellReconfigurationFailure-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellReconfigurationFailure-Extensions}}		OPTIONAL,
	...
}

CellReconfigurationFailure-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-Cause						CRITICALITY ignore			TYPE Cause							PRESENCE mandatory	}|
	{ ID id-CriticalityDiagnostics		CRITICALITY ignore			TYPE CriticalityDiagnostics			PRESENCE optional	},
	...
}

CellReconfigurationFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- CELL DELETION REQUEST
--
-- **************************************************************

CellDeletionRequest ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellDeletionRequest-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellDeletionRequest-Extensions}}		OPTIONAL,
	...
}

CellDeletionRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-C-ID			CRITICALITY reject			TYPE C-ID		PRESENCE mandatory },
	...
}

CellDeletionRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- CELL DELETION RESPONSE
--
-- **************************************************************

CellDeletionResponse ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellDeletionResponse-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellDeletionResponse-Extensions}}		OPTIONAL,
	...
}

CellDeletionResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CriticalityDiagnostics		CRITICALITY ignore			TYPE CriticalityDiagnostics		PRESENCE optional },
	...
}

CellDeletionResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RESOURCE STATUS INDICATION
--
-- **************************************************************

ResourceStatusIndication ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{ResourceStatusIndication-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{ResourceStatusIndication-Extensions}}		OPTIONAL,
	...
}

ResourceStatusIndication-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-IndicationType-ResourceStatusInd	CRITICALITY ignore	TYPE IndicationType-ResourceStatusInd		PRESENCE mandatory }|
	{ ID id-Cause								CRITICALITY ignore	TYPE Cause							PRESENCE optional },
	...
}

ResourceStatusIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

IndicationType-ResourceStatusInd ::= CHOICE {
	no-Failure								No-Failure-ResourceStatusInd,
	serviceImpacting						ServiceImpacting-ResourceStatusInd,
	...
}

No-Failure-ResourceStatusInd ::= SEQUENCE {
	local-Cell-InformationList				Local-Cell-InformationList-ResourceStatusInd,
	local-Cell-Group-InformationList		Local-Cell-Group-InformationList-ResourceStatusInd	OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { No-FailureItem-ResourceStatusInd-ExtIEs} }	OPTIONAL,
	...
}

No-FailureItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-Power-Local-Cell-Group-InformationList-ResourceStatusInd		CRITICALITY		ignore			EXTENSION	Power-Local-Cell-Group-InformationList-ResourceStatusInd		PRESENCE	optional	},
	...
}

Local-Cell-InformationList-ResourceStatusInd ::= SEQUENCE(SIZE (1..maxLocalCellinNodeB)) OF ProtocolIE-Single-Container {{ Local-Cell-InformationItemIE-ResourceStatusInd }}

Local-Cell-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-Local-Cell-InformationItem-ResourceStatusInd   CRITICALITY ignore	TYPE Local-Cell-InformationItem-ResourceStatusInd		PRESENCE mandatory }
}

Local-Cell-InformationItem-ResourceStatusInd ::= SEQUENCE {
	local-CellID								Local-Cell-ID,
	addorDeleteIndicator						AddorDeleteIndicator,
	dl-or-global-capacityCredit					DL-or-Global-CapacityCredit					OPTIONAL,
	-- This IE shall be present if AddorDeleteIndicator IE is set to “add”
	ul-capacityCredit							UL-CapacityCredit							OPTIONAL,
	commonChannelsCapacityConsumptionLaw 		CommonChannelsCapacityConsumptionLaw		OPTIONAL,
	-- This IE shall be present if AddorDeleteIndicator IE is set to “add”
	dedicatedChannelsCapacityConsumptionLaw 	DedicatedChannelsCapacityConsumptionLaw		OPTIONAL,
	-- This IE shall be present if AddorDeleteIndicator IE is set to “add”
	maximumDL-PowerCapability					MaximumDL-PowerCapability					OPTIONAL,
	-- This IE shall be present if AddorDeleteIndicator IE is set to “add”
	minSpreadingFactor							MinSpreadingFactor							OPTIONAL,
	-- This IE shall be present if AddorDeleteIndicator IE is set to “add”
	minimumDL-PowerCapability					MinimumDL-PowerCapability					OPTIONAL,
	-- This IE shall be present if AddorDeleteIndicator IE is set to “add”
	local-Cell-Group-ID							Local-Cell-ID								OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { Local-Cell-InformationItem-ResourceStatusInd-ExtIEs} }	OPTIONAL,
	...
}

Local-Cell-InformationItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-ReferenceClockAvailability			CRITICALITY ignore	EXTENSION ReferenceClockAvailability		PRESENCE optional }|
	-- This IE shall be present if AddorDeleteIndicator IE is set to “add“ and the Local Cell is related to a TDD cell
	{ ID id-Power-Local-Cell-Group-ID			CRITICALITY ignore	EXTENSION Local-Cell-ID				PRESENCE optional }|
	{ ID id-HSDPA-Capability					CRITICALITY ignore	EXTENSION HSDPA-Capability			PRESENCE optional }|
	{ ID id-E-DCH-Capability					CRITICALITY ignore	EXTENSION E-DCH-Capability			PRESENCE optional }|
	{ ID id-E-DCH-TTI2ms-Capability				CRITICALITY ignore	EXTENSION E-DCH-TTI2ms-Capability		PRESENCE conditional }|
	-- The IE shall be present if E-DCH Capability IE is set to ”E-DCH Capable”.
	{ ID id-E-DCH-SF-Capability					CRITICALITY ignore	EXTENSION E-DCH-SF-Capability		PRESENCE conditional }|
	-- The IE shall be present if E-DCH Capability IE is set to ”E-DCH Capable”.
	{ ID id-E-DCH-HARQ-Combining-Capability		CRITICALITY ignore	EXTENSION E-DCH-HARQ-Combining-Capability		PRESENCE conditional }|
	-- The IE shall be present if E-DCH Capability IE is set to ”E-DCH Capable”.
	{ ID id-E-DCH-CapacityConsumptionLaw		CRITICALITY ignore	EXTENSION E-DCHCapacityConsumptionLaw		PRESENCE optional }|
	{ ID id-F-DPCH-Capability					CRITICALITY ignore	EXTENSION F-DPCH-Capability			PRESENCE optional }|
	{ ID id-E-DCH-TDD-CapacityConsumptionLaw	CRITICALITY ignore	EXTENSION E-DCH-TDD-CapacityConsumptionLaw		PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivityDTX-DRX-Capability	CRITICALITY ignore	EXTENSION ContinuousPacketConnectivityDTX-DRX-Capability	PRESENCE optional }|
	{ ID id-Max-UE-DTX-Cycle					CRITICALITY ignore	EXTENSION Max-UE-DTX-Cycle			PRESENCE conditional }|
	-- The IE shall be present if Continuous Packet Connectivity DTX-DRX Capability IE is present and set to ”Continuous Packet Connectivity DTX-DRX Capable”.
	{ ID id-ContinuousPacketConnectivityHS-SCCH-less-Capability		CRITICALITY ignore	EXTENSION ContinuousPacketConnectivityHS-SCCH-less-Capability		PRESENCE optional }|
	{ ID id-MIMO-Capability						CRITICALITY ignore	EXTENSION MIMO-Capability			PRESENCE optional }|
	{ ID id-SixtyfourQAM-DL-Capability			CRITICALITY ignore	EXTENSION SixtyfourQAM-DL-Capability		PRESENCE optional }|
	{ ID id-MBMS-Capability						CRITICALITY ignore	EXTENSION MBMS-Capability			PRESENCE optional }|
	{ ID id-Enhanced-FACH-Capability			CRITICALITY ignore	EXTENSION Enhanced-FACH-Capability		PRESENCE optional }|
	{ ID id-Enhanced-PCH-Capability				CRITICALITY ignore	EXTENSION Enhanced-PCH-Capability		PRESENCE conditional }|
	-- The IE shall be present if Enhanced FACH Capability IE is set to ”Enhanced FACH Capable”.
	{ ID id-SixteenQAM-UL-Capability			CRITICALITY ignore	EXTENSION SixteenQAM-UL-Capability		PRESENCE optional }|
	{ ID id-HSDSCH-MACdPDU-SizeCapability		CRITICALITY ignore	EXTENSION HSDSCH-MACdPDU-SizeCapability		PRESENCE optional }|
	{ ID id-MBSFN-Only-Mode-Capability			CRITICALITY ignore	EXTENSION MBSFN-Only-Mode-Capability		PRESENCE optional }|
	{ ID id-F-DPCH-SlotFormatCapability			CRITICALITY ignore	EXTENSION F-DPCH-SlotFormatCapability		PRESENCE optional }|
	{ ID id-E-DCH-MACdPDU-SizeCapability		CRITICALITY ignore	EXTENSION E-DCH-MACdPDU-SizeCapability		PRESENCE optional }|
	{ ID id-Common-EDCH-Capability				CRITICALITY ignore	EXTENSION Common-EDCH-Capability		PRESENCE optional }|
	{ ID id-E-AI-Capability						CRITICALITY ignore	EXTENSION E-AI-Capability			PRESENCE optional }|
	-- The IE shall be present if Common E-DCH Capability IE is present and set to ”Common E-DCH Capable”.
	{ ID id-Enhanced-UE-DRX-Capability			CRITICALITY ignore	EXTENSION Enhanced-UE-DRX-Capability		PRESENCE optional }|
	{ ID id-Enhanced-UE-DRX-CapabilityLCR		CRITICALITY ignore	EXTENSION Enhanced-UE-DRX-Capability		PRESENCE optional }|
	{ ID id-E-DPCCH-Power-Boosting-Capability	CRITICALITY ignore	EXTENSION E-DPCCH-Power-Boosting-Capability		PRESENCE optional }|
	{ ID id-SixtyfourQAM-DL-MIMO-Combined-Capability	CRITICALITY ignore	EXTENSION SixtyfourQAM-DL-MIMO-Combined-Capability	PRESENCE optional}|
	{ ID id-Multi-Cell-Capability-Info			CRITICALITY ignore	EXTENSION Multi-Cell-Capability-Info		PRESENCE optional }|
	{ ID id-Semi-PersistentScheduling-CapabilityLCR	CRITICALITY ignore	EXTENSION Semi-PersistentScheduling-CapabilityLCR	PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivity-DRX-CapabilityLCR	CRITICALITY ignore	EXTENSION ContinuousPacketConnectivity-DRX-CapabilityLCR	PRESENCE optional }|
	{ ID id-Common-E-DCH-HSDPCCH-Capability		CRITICALITY ignore	EXTENSION Common-E-DCH-HSDPCCH-Capability		PRESENCE optional }|
	-- The IE shall be present if Common E-DCH Capability IE is present and set to ”Common E-DCH Capable”.
	{ ID id-MIMO-Power-Offset-For-S-CPICH-Capability	CRITICALITY ignore	EXTENSION MIMO-PowerOffsetForS-CPICHCapability	PRESENCE optional }|
	{ ID id-TxDiversityOnDLControlChannelsByMIMOUECapability	CRITICALITY ignore	EXTENSION TxDiversityOnDLControlChannelsByMIMOUECapability 		PRESENCE optional }|
	{ ID id-Single-Stream-MIMO-Capability		CRITICALITY ignore	EXTENSION Single-Stream-MIMO-Capability		PRESENCE optional }|
	{ ID id-Dual-Band-Capability-Info			CRITICALITY ignore	EXTENSION Dual-Band-Capability-Info		PRESENCE optional }|
	{ ID id-CellPortion-CapabilityLCR			CRITICALITY ignore	EXTENSION CellPortion-CapabilityLCR		PRESENCE optional }|
	{ ID id-Cell-Capability-Container			CRITICALITY ignore	EXTENSION Cell-Capability-Container		PRESENCE optional }|
	{ ID id-TS0-CapabilityLCR					CRITICALITY ignore	EXTENSION TS0-CapabilityLCR			PRESENCE optional }|
	{ ID id-PrecodingWeightSetRestriction		CRITICALITY ignore	EXTENSION PrecodingWeightSetRestriction		PRESENCE optional }|
	{ ID id-Cell-Capability-Container-TDD-LCR	CRITICALITY ignore	EXTENSION Cell-Capability-Container-TDD-LCR		PRESENCE optional }|
	{ ID id-MU-MIMO-Capability-ContainerLCR		CRITICALITY ignore	EXTENSION MU-MIMO-Capability-ContainerLCR		PRESENCE optional }|
	{ ID id-Adaptive-Special-Burst-Power-CapabilityLCR	CRITICALITY ignore	EXTENSION Adaptive-Special-Burst-Power-CapabilityLCR	PRESENCE optional },
	...

}

Local-Cell-Group-InformationList-ResourceStatusInd ::= SEQUENCE(SIZE (1..maxLocalCellinNodeB)) OF ProtocolIE-Single-Container {{ Local-Cell-Group-InformationItemIE-ResourceStatusInd }}

Local-Cell-Group-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-Local-Cell-Group-InformationItem-ResourceStatusInd   CRITICALITY ignore	TYPE Local-Cell-Group-InformationItem-ResourceStatusInd		PRESENCE mandatory }
}

Local-Cell-Group-InformationItem-ResourceStatusInd::= SEQUENCE {
	local-Cell-Group-ID							Local-Cell-ID,
	dl-or-global-capacityCredit					DL-or-Global-CapacityCredit,
	ul-capacityCredit							UL-CapacityCredit		OPTIONAL,
	commonChannelsCapacityConsumptionLaw 		CommonChannelsCapacityConsumptionLaw,
	dedicatedChannelsCapacityConsumptionLaw 	DedicatedChannelsCapacityConsumptionLaw,
	iE-Extensions								ProtocolExtensionContainer { { Local-Cell-Group-InformationItem-ResourceStatusInd-ExtIEs} }	OPTIONAL,
	...
}

Local-Cell-Group-InformationItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-CapacityConsumptionLaw		CRITICALITY ignore		EXTENSION E-DCHCapacityConsumptionLaw		PRESENCE optional }|
	{ ID id-E-DCH-TDD-CapacityConsumptionLaw	CRITICALITY ignore		EXTENSION E-DCH-TDD-CapacityConsumptionLaw		PRESENCE optional },
	...
}

Power-Local-Cell-Group-InformationList-ResourceStatusInd ::= SEQUENCE(SIZE (1..maxLocalCellinNodeB)) OF ProtocolIE-Single-Container {{ Power-Local-Cell-Group-InformationItemIE-ResourceStatusInd }}

Power-Local-Cell-Group-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-Power-Local-Cell-Group-InformationItem-ResourceStatusInd	CRITICALITY ignore	TYPE Power-Local-Cell-Group-InformationItem-ResourceStatusInd		PRESENCE mandatory	}
}

Power-Local-Cell-Group-InformationItem-ResourceStatusInd::= SEQUENCE {
	power-Local-Cell-Group-ID					Local-Cell-ID,
	maximumDL-PowerCapability					MaximumDL-PowerCapability,
	iE-Extensions								ProtocolExtensionContainer { { Power-Local-Cell-Group-InformationItem-ResourceStatusInd-ExtIEs} }	OPTIONAL,
	...
}

Power-Local-Cell-Group-InformationItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ServiceImpacting-ResourceStatusInd ::= SEQUENCE {
	local-Cell-InformationList				Local-Cell-InformationList2-ResourceStatusInd	OPTIONAL,
	local-Cell-Group-InformationList		Local-Cell-Group-InformationList2-ResourceStatusInd	OPTIONAL,
	cCP-InformationList						CCP-InformationList-ResourceStatusInd 			OPTIONAL,
	cell-InformationList					Cell-InformationList-ResourceStatusInd 			OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { ServiceImpactingItem-ResourceStatusInd-ExtIEs} }		OPTIONAL,
	...
}

ServiceImpactingItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Power-Local-Cell-Group-InformationList2-ResourceStatusInd		CRITICALITY ignore	EXTENSION Power-Local-Cell-Group-InformationList2-ResourceStatusInd		PRESENCE optional	},
	...
}

Local-Cell-InformationList2-ResourceStatusInd ::= SEQUENCE(SIZE (1..maxLocalCellinNodeB)) OF ProtocolIE-Single-Container {{ Local-Cell-InformationItemIE2-ResourceStatusInd }}

Local-Cell-InformationItemIE2-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-Local-Cell-InformationItem2-ResourceStatusInd   CRITICALITY ignore	TYPE Local-Cell-InformationItem2-ResourceStatusInd		PRESENCE mandatory }
}

Local-Cell-InformationItem2-ResourceStatusInd ::= SEQUENCE {
	local-Cell-ID								Local-Cell-ID,
	dl-or-global-capacityCredit					DL-or-Global-CapacityCredit				OPTIONAL,
	ul-capacityCredit							UL-CapacityCredit						OPTIONAL,
	commonChannelsCapacityConsumptionLaw		CommonChannelsCapacityConsumptionLaw	OPTIONAL,
	dedicatedChannelsCapacityConsumptionLaw		DedicatedChannelsCapacityConsumptionLaw	OPTIONAL,
	maximum-DL-PowerCapability					MaximumDL-PowerCapability				OPTIONAL,
	minSpreadingFactor							MinSpreadingFactor						OPTIONAL,
	minimumDL-PowerCapability					MinimumDL-PowerCapability				OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { Local-Cell-InformationItem2-ResourceStatusInd-ExtIEs} }		OPTIONAL,
	...
}

Local-Cell-InformationItem2-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-ReferenceClockAvailability			CRITICALITY ignore	EXTENSION ReferenceClockAvailability		PRESENCE optional }|
	{ ID id-HSDPA-Capability					CRITICALITY ignore	EXTENSION HSDPA-Capability			PRESENCE optional }|
	{ ID id-E-DCH-Capability					CRITICALITY ignore	EXTENSION E-DCH-Capability			PRESENCE optional }|
	{ ID id-E-DCH-TTI2ms-Capability				CRITICALITY ignore	EXTENSION E-DCH-TTI2ms-Capability		PRESENCE conditional }|
	-- The IE shall be present if E-DCH Capability IE is set to ”E-DCH Capable”.
	{ ID id-E-DCH-SF-Capability					CRITICALITY ignore	EXTENSION E-DCH-SF-Capability		PRESENCE conditional }|
	-- The IE shall be present if E-DCH Capability IE is set to ”E-DCH Capable”.
	{ ID id-E-DCH-HARQ-Combining-Capability		CRITICALITY ignore	EXTENSION E-DCH-HARQ-Combining-Capability		PRESENCE conditional }|
	-- The IE shall be present if E-DCH Capability IE is set to ”E-DCH Capable”.
	{ ID id-E-DCH-CapacityConsumptionLaw		CRITICALITY ignore	EXTENSION E-DCHCapacityConsumptionLaw		PRESENCE optional }|
	{ ID id-F-DPCH-Capability					CRITICALITY ignore	EXTENSION F-DPCH-Capability			PRESENCE optional }|
	{ ID id-E-DCH-TDD-CapacityConsumptionLaw	CRITICALITY ignore	EXTENSION E-DCH-TDD-CapacityConsumptionLaw		PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivityDTX-DRX-Capability	CRITICALITY ignore	EXTENSION ContinuousPacketConnectivityDTX-DRX-Capability	PRESENCE optional }|
	{ ID id-Max-UE-DTX-Cycle					CRITICALITY ignore	EXTENSION Max-UE-DTX-Cycle			PRESENCE conditional }|
	-- The IE shall be present if Continuous Packet Connectivity DTX-DRX Capability IE is present and set to ”Continuous Packet Connectivity DTX-DRX Capable”.
	{ ID id-ContinuousPacketConnectivityHS-SCCH-less-Capability		CRITICALITY ignore	EXTENSION ContinuousPacketConnectivityHS-SCCH-less-Capability	PRESENCE optional }|
	{ ID id-MIMO-Capability						CRITICALITY ignore	EXTENSION MIMO-Capability			PRESENCE optional }|
	{ ID id-SixtyfourQAM-DL-Capability			CRITICALITY ignore	EXTENSION SixtyfourQAM-DL-Capability		PRESENCE optional }|
	{ ID id-MBMS-Capability						CRITICALITY ignore	EXTENSION MBMS-Capability			PRESENCE optional }|
	{ ID id-Enhanced-FACH-Capability			CRITICALITY ignore	EXTENSION Enhanced-FACH-Capability		PRESENCE optional }|
	{ ID id-Enhanced-PCH-Capability				CRITICALITY ignore	EXTENSION Enhanced-PCH-Capability		PRESENCE conditional }|
	-- The IE shall be present if Enhanced FACH Capability IE is set to ”Enhanced FACH Capable”.
	{ ID id-SixteenQAM-UL-Capability			CRITICALITY ignore	EXTENSION SixteenQAM-UL-Capability		PRESENCE optional }|
	{ ID id-HSDSCH-MACdPDU-SizeCapability		CRITICALITY ignore	EXTENSION HSDSCH-MACdPDU-SizeCapability		PRESENCE optional }|
	{ ID id-MBSFN-Only-Mode-Capability			CRITICALITY ignore	EXTENSION MBSFN-Only-Mode-Capability		PRESENCE optional }|
	{ ID id-F-DPCH-SlotFormatCapability			CRITICALITY ignore	EXTENSION F-DPCH-SlotFormatCapability		PRESENCE optional }|
	{ ID id-E-DCH-MACdPDU-SizeCapability		CRITICALITY ignore	EXTENSION E-DCH-MACdPDU-SizeCapability		PRESENCE optional }|
	{ ID id-Common-EDCH-Capability				CRITICALITY ignore	EXTENSION Common-EDCH-Capability		PRESENCE optional }|
	{ ID id-E-AI-Capability						CRITICALITY ignore	EXTENSION E-AI-Capability			PRESENCE optional }|
	-- The IE shall be present if Common E-DCH Capability IE is present and set to ”Common E-DCH Capable”.
	{ ID id-Enhanced-UE-DRX-Capability			CRITICALITY ignore	EXTENSION Enhanced-UE-DRX-Capability		PRESENCE optional }|
	{ ID id-Enhanced-UE-DRX-CapabilityLCR		CRITICALITY ignore	EXTENSION Enhanced-UE-DRX-Capability		PRESENCE optional }|
	{ ID id-E-DPCCH-Power-Boosting-Capability	CRITICALITY ignore	EXTENSION E-DPCCH-Power-Boosting-Capability		PRESENCE optional }|
	{ ID id-SixtyfourQAM-DL-MIMO-Combined-Capability	CRITICALITY ignore	EXTENSION SixtyfourQAM-DL-MIMO-Combined-Capability	PRESENCE optional}|
	{ ID id-Multi-Cell-Capability-Info			CRITICALITY ignore	EXTENSION Multi-Cell-Capability-Info		PRESENCE optional }|
	{ ID id-Semi-PersistentScheduling-CapabilityLCR	CRITICALITY ignore	EXTENSION Semi-PersistentScheduling-CapabilityLCR	PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivity-DRX-CapabilityLCR	CRITICALITY ignore	EXTENSION ContinuousPacketConnectivity-DRX-CapabilityLCR	PRESENCE optional }|
	{ ID id-Common-E-DCH-HSDPCCH-Capability		CRITICALITY ignore	EXTENSION Common-E-DCH-HSDPCCH-Capability		PRESENCE optional }|
	-- The IE shall be present if Common E-DCH Capability IE is present and set to ”Common E-DCH Capable”.
	{ ID id-MIMO-Power-Offset-For-S-CPICH-Capability	CRITICALITY ignore	EXTENSION MIMO-PowerOffsetForS-CPICHCapability	PRESENCE optional } |
	{ ID id-TxDiversityOnDLControlChannelsByMIMOUECapability	CRITICALITY ignore	EXTENSION TxDiversityOnDLControlChannelsByMIMOUECapability	PRESENCE optional }|
	{ ID id-Single-Stream-MIMO-Capability		CRITICALITY ignore	EXTENSION Single-Stream-MIMO-Capability		PRESENCE optional }|
	{ ID id-Dual-Band-Capability-Info			CRITICALITY ignore	EXTENSION Dual-Band-Capability-Info		PRESENCE optional }|
	{ ID id-CellPortion-CapabilityLCR			CRITICALITY ignore	EXTENSION CellPortion-CapabilityLCR		PRESENCE optional }|
	{ ID id-Cell-Capability-Container			CRITICALITY ignore	EXTENSION Cell-Capability-Container		PRESENCE optional }|
	{ ID id-TS0-CapabilityLCR					CRITICALITY ignore	EXTENSION TS0-CapabilityLCR			PRESENCE optional }|
	{ ID id-PrecodingWeightSetRestriction		CRITICALITY ignore	EXTENSION PrecodingWeightSetRestriction		PRESENCE optional }|
	{ ID id-Cell-Capability-Container-TDD-LCR	CRITICALITY ignore	EXTENSION Cell-Capability-Container-TDD-LCR		PRESENCE optional }|
	{ ID id-MU-MIMO-Capability-ContainerLCR		CRITICALITY ignore	EXTENSION MU-MIMO-Capability-ContainerLCR		PRESENCE optional }|
	{ ID id-Adaptive-Special-Burst-Power-CapabilityLCR	CRITICALITY ignore	EXTENSION Adaptive-Special-Burst-Power-CapabilityLCR	PRESENCE optional },
	...
}

Local-Cell-Group-InformationList2-ResourceStatusInd ::= SEQUENCE(SIZE (1..maxLocalCellinNodeB)) OF ProtocolIE-Single-Container {{ Local-Cell-Group-InformationItemIE2-ResourceStatusInd }}

Local-Cell-Group-InformationItemIE2-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-Local-Cell-Group-InformationItem2-ResourceStatusInd   CRITICALITY ignore	TYPE Local-Cell-Group-InformationItem2-ResourceStatusInd		PRESENCE mandatory }
}

Local-Cell-Group-InformationItem2-ResourceStatusInd ::= SEQUENCE {
	local-Cell-Group-ID							Local-Cell-ID,
	dl-or-global-capacityCredit					DL-or-Global-CapacityCredit					OPTIONAL,
	ul-capacityCredit							UL-CapacityCredit							OPTIONAL,
	commonChannelsCapacityConsumptionLaw		CommonChannelsCapacityConsumptionLaw		OPTIONAL,
	dedicatedChannelsCapacityConsumptionLaw		DedicatedChannelsCapacityConsumptionLaw		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { Local-Cell-Group-InformationItem2-ResourceStatusInd-ExtIEs} }		OPTIONAL,
	...
}

Local-Cell-Group-InformationItem2-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-CapacityConsumptionLaw		CRITICALITY ignore		EXTENSION E-DCHCapacityConsumptionLaw		PRESENCE optional }|
	{ ID id-E-DCH-TDD-CapacityConsumptionLaw	CRITICALITY ignore		EXTENSION E-DCH-TDD-CapacityConsumptionLaw	 PRESENCE	optional },
	...
}

CCP-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxCCPinNodeB)) OF ProtocolIE-Single-Container {{ CCP-InformationItemIE-ResourceStatusInd }}

CCP-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-CCP-InformationItem-ResourceStatusInd   CRITICALITY ignore	TYPE CCP-InformationItem-ResourceStatusInd		PRESENCE mandatory }
}

CCP-InformationItem-ResourceStatusInd ::= SEQUENCE {
	communicationControlPortID				CommunicationControlPortID,
	resourceOperationalState				ResourceOperationalState,
	availabilityStatus						AvailabilityStatus,
	iE-Extensions							ProtocolExtensionContainer { { CCP-InformationItem-ResourceStatusInd-ExtIEs} }		OPTIONAL,
	...
}

CCP-InformationItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Cell-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxCellinNodeB)) OF ProtocolIE-Single-Container {{ Cell-InformationItemIE-ResourceStatusInd }}

Cell-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-Cell-InformationItem-ResourceStatusInd   CRITICALITY ignore	TYPE Cell-InformationItem-ResourceStatusInd		PRESENCE mandatory }
}

Cell-InformationItem-ResourceStatusInd  ::= SEQUENCE {
	c-ID									C-ID,
	resourceOperationalState 				ResourceOperationalState						OPTIONAL,
	availabilityStatus						AvailabilityStatus								OPTIONAL,
	primary-SCH-Information					P-SCH-Information-ResourceStatusInd				OPTIONAL, -- FDD only
	secondary-SCH-Information				S-SCH-Information-ResourceStatusInd				OPTIONAL, -- FDD only
	primary-CPICH-Information				P-CPICH-Information-ResourceStatusInd			OPTIONAL, -- FDD only
	secondary-CPICH-Information				S-CPICH-InformationList-ResourceStatusInd		OPTIONAL, -- FDD only
	primary-CCPCH-Information				P-CCPCH-Information-ResourceStatusInd			OPTIONAL,
	bCH-Information							BCH-Information-ResourceStatusInd 				OPTIONAL,
	secondary-CCPCH-InformationList			S-CCPCH-InformationList-ResourceStatusInd		OPTIONAL,
	pCH-Information							PCH-Information-ResourceStatusInd 				OPTIONAL,
	pICH-Information						PICH-Information-ResourceStatusInd				OPTIONAL,
	fACH-InformationList					FACH-InformationList-ResourceStatusInd 			OPTIONAL,
	pRACH-InformationList					PRACH-InformationList-ResourceStatusInd			OPTIONAL,
	rACH-InformationList					RACH-InformationList-ResourceStatusInd 			OPTIONAL,
	aICH-InformationList					AICH-InformationList-ResourceStatusInd 			OPTIONAL, -- FDD only
	notUsed-1-pCPCH-InformationList			NULL											OPTIONAL,
	notUsed-2-cPCH-InformationList			NULL											OPTIONAL,
	notUsed-3-aP-AICH-InformationList		NULL											OPTIONAL,
	notUsed-4-cDCA-ICH-InformationList		NULL											OPTIONAL,
	sCH-Information							SCH-Information-ResourceStatusInd 				OPTIONAL, -- Applicable to 3.84Mcps TDD only
	iE-Extensions							ProtocolExtensionContainer { { Cell-InformationItem-ResourceStatusInd-ExtIEs} }	OPTIONAL,
	...
}

Cell-InformationItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-FPACH-LCR-InformationList-ResourceStatusInd			CRITICALITY ignore	EXTENSION FPACH-LCR-InformationList-ResourceStatusInd			PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
	{ ID id-DwPCH-LCR-Information-ResourceStatusInd				CRITICALITY ignore	EXTENSION DwPCH-LCR-Information-ResourceStatusInd					PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
	{ ID id-HSDSCH-Resources-Information-ResourceStatusInd		CRITICALITY ignore	EXTENSION HS-DSCH-Resources-Information-ResourceStatusInd			PRESENCE optional }|	-- For 1.28Mcps TDD, this HS-DSCH Resource Information is for the first Frequency repetition, HS-DSCH Resource Information for Frequency repetitions 2 and on, should be defined in MultipleFreq-HS-DSCH-Resources-InformationList-ResourceStatusInd.
	{ ID id-MICH-Information-ResourceStatusInd					CRITICALITY ignore	EXTENSION Common-PhysicalChannel-Status-Information				PRESENCE optional }|
	{ ID id-S-CCPCH-InformationListExt-ResourceStatusInd		CRITICALITY ignore	EXTENSION S-CCPCH-InformationListExt-ResourceStatusInd			PRESENCE optional }|
	-- Applicable to 3.84Mcps TDD only, used when there are more than maxSCCPCHCell SCCPCHs in the message.
	{ ID id-S-CCPCH-LCR-InformationListExt-ResourceStatusInd	CRITICALITY ignore	EXTENSION S-CCPCH-LCR-InformationListExt-ResourceStatusInd		PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only, used when there are more than maxSCCPCHCell SCCPCHs in the message.
	{ ID id-E-DCH-Resources-Information-ResourceStatusInd		CRITICALITY ignore	EXTENSION E-DCH-Resources-Information-ResourceStatusInd			PRESENCE optional }|
	-- For 1.28Mcps TDD, this E-DCH Resource Information is for the first Frequency repetition, E-DCH Resource Information for Frequency repetitions 2 and on, should be defined in MultipleFreq-E-DCH-Resources-InformationList-ResourceStatusInd.
	{ ID id-PLCCH-InformationList-ResourceStatusInd				CRITICALITY ignore	EXTENSION PLCCH-InformationList-ResourceStatusInd			
	PRESENCE optional }|
	{ ID id-P-CCPCH-768-Information-ResourceStatusInd			CRITICALITY ignore	EXTENSION Common-PhysicalChannel-Status-Information768			PRESENCE optional }|
	{ ID id-S-CCPCH-768-InformationList-ResourceStatusInd		CRITICALITY ignore	EXTENSION S-CCPCH-768-InformationList-ResourceStatusInd			PRESENCE optional }|
	{ ID id-PICH-768-Information-ResourceStatusInd				CRITICALITY ignore	EXTENSION Common-PhysicalChannel-Status-Information768		PRESENCE optional }|
	{ ID id-PRACH-768-InformationList-ResourceStatusInd			CRITICALITY ignore	EXTENSION PRACH-768-InformationList-ResourceStatusInd			PRESENCE optional }|
	{ ID id-SCH-768-Information-ResourceStatusInd				CRITICALITY ignore	EXTENSION Common-PhysicalChannel-Status-Information768		PRESENCE optional }|
	{ ID id-MICH-768-Information-ResourceStatusInd				CRITICALITY ignore	EXTENSION Common-PhysicalChannel-Status-Information768		PRESENCE optional }|
	{ ID id-E-RUCCH-InformationList-ResourceStatusInd			CRITICALITY ignore	EXTENSION E-RUCCH-InformationList-ResourceStatusInd			PRESENCE optional }|
	{ ID id-E-RUCCH-768-InformationList-ResourceStatusInd		CRITICALITY ignore	EXTENSION E-RUCCH-768-InformationList-ResourceStatusInd			PRESENCE optional }|
	{ ID id-Cell-Frequency-List-Information-LCR-MulFreq-ResourceStatusInd	CRITICALITY ignore	EXTENSION Cell-Frequency-List-Information-LCR-MulFreq-ResourceStatusInd			PRESENCE optional }|	-- Applicable to 1.28Mcps TDD when using multiple frequencies
	{ ID id-UPPCH-LCR-InformationList-ResourceStatusInd			CRITICALITY ignore	EXTENSION UPPCH-LCR-InformationList-ResourceStatusInd					PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
	{ ID id-multipleFreq-HS-DSCH-Resources-InformationList-ResourceStatusInd	CRITICALITY ignore	EXTENSION MultipleFreq-HS-DSCH-Resources-InformationList-ResourceStatusInd	PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD when using multiple frequencies, This HS-DSCH Resource Information is for the 2nd and beyond frequencies.
	{ ID id-MultipleFreq-E-DCH-Resources-InformationList-ResourceStatusInd	CRITICALITY ignore	EXTENSION MultipleFreq-E-DCH-Resources-InformationList-ResourceStatusInd	PRESENCE optional },
	-- Applicable to 1.28Mcps TDD when using multiple frequencies. This E-DCH Resource Information is for the 2nd and beyond frequencies.
	...
}

P-SCH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ P-SCH-InformationIE-ResourceStatusInd }}

P-SCH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-P-SCH-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

S-SCH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ S-SCH-InformationIE-ResourceStatusInd }}

S-SCH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-S-SCH-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

P-CPICH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ P-CPICH-InformationIE-ResourceStatusInd }}

P-CPICH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-P-CPICH-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

S-CPICH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxSCPICHCell)) OF ProtocolIE-Single-Container {{ S-CPICH-InformationItemIE-ResourceStatusInd }}

S-CPICH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-S-CPICH-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

P-CCPCH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ P-CCPCH-InformationIE-ResourceStatusInd }}

P-CCPCH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-P-CCPCH-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

BCH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ BCH-InformationIE-ResourceStatusInd }}

BCH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-BCH-Information   CRITICALITY ignore	TYPE Common-TransportChannel-Status-Information		PRESENCE mandatory }
}

S-CCPCH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxSCCPCHCell)) OF ProtocolIE-Single-Container {{ S-CCPCH-InformationItemIE-ResourceStatusInd }}

S-CCPCH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-S-CCPCH-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

PCH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ PCH-InformationIE-ResourceStatusInd }}

PCH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-PCH-Information   CRITICALITY ignore	TYPE Common-TransportChannel-Status-Information		PRESENCE mandatory }
}

PICH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ PICH-InformationIE-ResourceStatusInd }}

PICH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-PICH-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

FACH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxFACHCell)) OF ProtocolIE-Single-Container {{ FACH-InformationItemIE-ResourceStatusInd }}

FACH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-FACH-Information   CRITICALITY ignore	TYPE Common-TransportChannel-Status-Information		PRESENCE mandatory }
}

PRACH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE-Single-Container {{ PRACH-InformationItemIE-ResourceStatusInd }}

PRACH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-PRACH-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

RACH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE-Single-Container {{ RACH-InformationItemIE-ResourceStatusInd }}

RACH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-RACH-Information   CRITICALITY ignore	TYPE Common-TransportChannel-Status-Information		PRESENCE mandatory }
}

AICH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE-Single-Container {{ AICH-InformationItemIE-ResourceStatusInd }}

AICH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-AICH-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

SCH-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ SCH-InformationIE-ResourceStatusInd }}

SCH-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-SCH-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

FPACH-LCR-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxFPACHCell)) OF ProtocolIE-Single-Container {{ FPACH-LCR-InformationItemIE-ResourceStatusInd }}

FPACH-LCR-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-FPACH-LCR-Information  CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

DwPCH-LCR-Information-ResourceStatusInd ::= ProtocolIE-Single-Container {{ DwPCH-LCR-InformationIE-ResourceStatusInd }}

DwPCH-LCR-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-DwPCH-LCR-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

HS-DSCH-Resources-Information-ResourceStatusInd ::= SEQUENCE {
	resourceOperationalState			ResourceOperationalState,
	availabilityStatus					AvailabilityStatus,
	iE-Extensions						ProtocolExtensionContainer  {{ HS-DSCH-Resources-Information-ResourceStatusInd-ExtIEs }}		OPTIONAL,
	...
}

HS-DSCH-Resources-Information-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-UARFCNforNt		CRITICALITY ignore		EXTENSION UARFCN		PRESENCE optional},
	--  Applicable to 1.28Mcps TDD when using multiple frequencies.
	...
}

S-CCPCH-InformationListExt-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxSCCPCHCellinExt)) OF ProtocolIE-Single-Container {{ S-CCPCH-InformationItemIE-ResourceStatusInd }}

S-CCPCH-LCR-InformationListExt-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxSCCPCHCellinExtLCR)) OF ProtocolIE-Single-Container {{ S-CCPCH-InformationItemIE-ResourceStatusInd }}

E-DCH-Resources-Information-ResourceStatusInd ::= SEQUENCE {
	resourceOperationalState			ResourceOperationalState,
	availabilityStatus					AvailabilityStatus,
	iE-Extensions						ProtocolExtensionContainer  {{ E-DCH-Resources-Information-ResourceStatusInd-ExtIEs }}		OPTIONAL,
	...
}

E-DCH-Resources-Information-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-UARFCNforNt		CRITICALITY ignore		EXTENSION UARFCN		PRESENCE optional},
	--  Applicable to 1.28Mcps TDD when using multiple frequencies.
	...
}

PLCCH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxPLCCHCell)) OF ProtocolIE-Single-Container {{ PLCCH-InformationItemIE-ResourceStatusInd }}

PLCCH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-PLCCH-Information-ResourceStatusInd  CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

S-CCPCH-768-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxSCCPCHCell768)) OF ProtocolIE-Single-Container {{ S-CCPCH-768-InformationItemIE-ResourceStatusInd }}

S-CCPCH-768-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-S-CCPCH-768-Information-ResourceStatusInd   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information768		PRESENCE mandatory }
}

PRACH-768-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxPRACHCell)) OF ProtocolIE-Single-Container {{ PRACH-768-InformationItemIE-ResourceStatusInd }}

PRACH-768-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-PRACH-768-Information   CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information768		PRESENCE mandatory }
}

E-RUCCH-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxE-RUCCHCell)) OF ProtocolIE-Single-Container {{ E-RUCCH-InformationItemIE-ResourceStatusInd }}

E-RUCCH-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-E-RUCCH-Information		CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information		PRESENCE mandatory }
}

E-RUCCH-768-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxE-RUCCHCell)) OF ProtocolIE-Single-Container {{ E-RUCCH-768-InformationItemIE-ResourceStatusInd }}

E-RUCCH-768-InformationItemIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-E-RUCCH-768-Information		CRITICALITY ignore	TYPE Common-PhysicalChannel-Status-Information768		PRESENCE mandatory }
}

Cell-Frequency-List-Information-LCR-MulFreq-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxFrequencyinCell)) OF ProtocolIE-Single-Container {{ Cell-Frequency-List-InformationIE-LCR-MulFreq-ResourceStatusInd }}

Cell-Frequency-List-InformationIE-LCR-MulFreq-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-Cell-Frequency-List-InformationItem-LCR-MulFreq-ResourceStatusInd   CRITICALITY ignore	TYPE Cell-Frequency-List-InformationItem-LCR-MulFreq-ResourceStatusInd		PRESENCE mandatory }
}

Cell-Frequency-List-InformationItem-LCR-MulFreq-ResourceStatusInd ::= SEQUENCE {
	uARFCN								UARFCN,
	resourceOperationalState			ResourceOperationalState,
	availabilityStatus					AvailabilityStatus,
	cause								Cause				OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer {{ Cell-Frequency-List-InformationItem-LCR-MulFreq-ResourceStatusInd-ExtIEs }}		OPTIONAL,
	...
}

Cell-Frequency-List-InformationItem-LCR-MulFreq-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UPPCH-LCR-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxFrequencyinCell)) OF ProtocolIE-Single-Container {{ UPPCH-LCR-InformationIE-ResourceStatusInd }}

UPPCH-LCR-InformationIE-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-UPPCH-LCR-InformationItem-ResourceStatusInd		CRITICALITY ignore	TYPE UPPCH-LCR-InformationItem-ResourceStatusInd		PRESENCE mandatory }
}

UPPCH-LCR-InformationItem-ResourceStatusInd ::= SEQUENCE {
	uARFCN								UARFCN				OPTIONAL,
	uPPCHPositionLCR					UPPCHPositionLCR, 
	resourceOperationalState			ResourceOperationalState,
	availabilityStatus					AvailabilityStatus,
	iE-Extensions						ProtocolExtensionContainer  {{ UPPCH-LCR-InformationItem-ResourceStatusInd-ExtIEs }}		OPTIONAL,
	...
}

UPPCH-LCR-InformationItem-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MultipleFreq-HS-DSCH-Resources-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxFrequencyinCell-1)) OF ProtocolIE-Single-Container{{ MultipleFreq-HS-DSCH-Resources-InformationItem-ResourceStatusInd }} 
--Includes the 2nd through the max number of frequencies information repetitions.

MultipleFreq-HS-DSCH-Resources-InformationItem-ResourceStatusInd  NBAP-PROTOCOL-IES ::= {
	{ ID id-HSDSCH-Resources-Information-ResourceStatusInd	CRITICALITY ignore	TYPE HS-DSCH-Resources-Information-ResourceStatusInd		PRESENCE mandatory }
}

Power-Local-Cell-Group-InformationList2-ResourceStatusInd ::= SEQUENCE(SIZE (1..maxLocalCellinNodeB)) OF ProtocolIE-Single-Container {{ Power-Local-Cell-Group-InformationItemIE2-ResourceStatusInd }}

Power-Local-Cell-Group-InformationItemIE2-ResourceStatusInd NBAP-PROTOCOL-IES ::= {
	{ ID id-Power-Local-Cell-Group-InformationItem2-ResourceStatusInd	CRITICALITY ignore	TYPE Power-Local-Cell-Group-InformationItem2-ResourceStatusInd		PRESENCE mandatory	}
}

Power-Local-Cell-Group-InformationItem2-ResourceStatusInd::= SEQUENCE {
	power-Local-Cell-Group-ID			Local-Cell-ID,
	maximumDL-PowerCapability			MaximumDL-PowerCapability,
	iE-Extensions						ProtocolExtensionContainer { { Power-Local-Cell-Group-InformationItem2-ResourceStatusInd-ExtIEs} }	OPTIONAL,
	...
}

Power-Local-Cell-Group-InformationItem2-ResourceStatusInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MultipleFreq-E-DCH-Resources-InformationList-ResourceStatusInd ::= SEQUENCE (SIZE (1..maxFrequencyinCell-1)) OF ProtocolIE-Single-Container{{ MultipleFreq-E-DCH-Resources-InformationItem-ResourceStatusInd }} 
	--Includes the 2nd through the max number of frequencies information repetitions.

MultipleFreq-E-DCH-Resources-InformationItem-ResourceStatusInd  NBAP-PROTOCOL-IES ::= {
	{ ID id-E-DCH-Resources-Information-ResourceStatusInd	CRITICALITY ignore	TYPE E-DCH-Resources-Information-ResourceStatusInd		PRESENCE mandatory }
}

-- **************************************************************
--
-- SYSTEM INFORMATION UPDATE REQUEST
--
-- **************************************************************

SystemInformationUpdateRequest ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{SystemInformationUpdateRequest-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{SystemInformationUpdateRequest-Extensions}}		OPTIONAL,
	...
}

SystemInformationUpdateRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-C-ID												CRITICALITY reject	TYPE C-ID					PRESENCE mandatory }|
	{ ID id-BCCH-ModificationTime								CRITICALITY reject	TYPE BCCH-ModificationTime				PRESENCE optional }|
	{ ID id-MIB-SB-SIB-InformationList-SystemInfoUpdateRqst		CRITICALITY reject	TYPE MIB-SB-SIB-InformationList-SystemInfoUpdateRqst				PRESENCE mandatory },
	...
}

SystemInformationUpdateRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-BCH-mappedOnSCCPCH-Indication		CRITICALITY reject	EXTENSION BCH-mappedOnSCCPCH-Indication	PRESENCE optional},
	...
}

MIB-SB-SIB-InformationList-SystemInfoUpdateRqst ::= SEQUENCE (SIZE (1..maxIB)) OF MIB-SB-SIB-InformationItem-SystemInfoUpdateRqst

MIB-SB-SIB-InformationItem-SystemInfoUpdateRqst ::= SEQUENCE {
	iB-Type								IB-Type,	
	iB-OC-ID							IB-OC-ID,
	deletionIndicator					DeletionIndicator-SystemInfoUpdate,
	iE-Extensions						ProtocolExtensionContainer { { MIB-SB-SIB-InformationItem-SystemInfoUpdateRqst-ExtIEs} }		OPTIONAL,
	...
}

MIB-SB-SIB-InformationItem-SystemInfoUpdateRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

BCH-mappedOnSCCPCH-Indication ::= ENUMERATED {
	inUse,
	...
}

DeletionIndicator-SystemInfoUpdate ::= CHOICE {
	no-Deletion							No-Deletion-SystemInfoUpdate,
	yes-Deletion						NULL

}

No-Deletion-SystemInfoUpdate ::= SEQUENCE {
	sIB-Originator							SIB-Originator				OPTIONAL,
	-- This IE shall be present if the IB-Type IE is set to "SIB"
	iB-SG-REP								IB-SG-REP					OPTIONAL,
	segmentInformationList					SegmentInformationList-SystemInfoUpdate,
	iE-Extensions							ProtocolExtensionContainer { { No-DeletionItem-SystemInfoUpdate-ExtIEs} }		OPTIONAL,
	...
}

No-DeletionItem-SystemInfoUpdate-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SegmentInformationList-SystemInfoUpdate ::= ProtocolIE-Single-Container {{ SegmentInformationListIEs-SystemInfoUpdate }}

SegmentInformationListIEs-SystemInfoUpdate NBAP-PROTOCOL-IES ::= {
	{ ID id-SegmentInformationListIE-SystemInfoUpdate   CRITICALITY reject	TYPE SegmentInformationListIE-SystemInfoUpdate		PRESENCE mandatory }
}

SegmentInformationListIE-SystemInfoUpdate ::= SEQUENCE (SIZE (1..maxIBSEG)) OF SegmentInformationItem-SystemInfoUpdate

SegmentInformationItem-SystemInfoUpdate ::= SEQUENCE {
	iB-SG-POS								IB-SG-POS			OPTIONAL,
	segment-Type							Segment-Type		OPTIONAL,
	-- This IE shall be present if the SIB Originator IE is set to "CRNC" or the IB-Type IE is set to "MIB", "SB1" or "SB2"
	iB-SG-DATA								IB-SG-DATA			OPTIONAL,
	-- This IE shall be present if the SIB Originator IE is set to "CRNC" or the IB-Type IE is set to "MIB", "SB1" or "SB2"
	iE-Extensions							ProtocolExtensionContainer { { SegmentInformationItem-SystemInfoUpdate-ExtIEs} }	OPTIONAL,
	...
}

SegmentInformationItem-SystemInfoUpdate-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- SYSTEM INFORMATION UPDATE RESPONSE
--
-- **************************************************************

SystemInformationUpdateResponse ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container    	{{SystemInformationUpdateResponse-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{SystemInformationUpdateResponse-Extensions}}		OPTIONAL,
	...
}

SystemInformationUpdateResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CriticalityDiagnostics		CRITICALITY ignore			TYPE CriticalityDiagnostics		PRESENCE optional },
	...
}

SystemInformationUpdateResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- SYSTEM INFORMATION UPDATE FAILURE
--
-- **************************************************************

SystemInformationUpdateFailure ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{SystemInformationUpdateFailure-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{SystemInformationUpdateFailure-Extensions}}		OPTIONAL,
	...
}

SystemInformationUpdateFailure-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-Cause							CRITICALITY ignore			TYPE Cause						PRESENCE	mandatory	}|
	{ ID id-CriticalityDiagnostics			CRITICALITY ignore			TYPE CriticalityDiagnostics		PRESENCE	optional	},
	...
}

SystemInformationUpdateFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK SETUP REQUEST FDD
--
-- **************************************************************

RadioLinkSetupRequestFDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkSetupRequestFDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkSetupRequestFDD-Extensions}}			OPTIONAL,
	...
}

RadioLinkSetupRequestFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID						CRITICALITY reject	TYPE CRNC-CommunicationContextID					PRESENCE mandatory }|
	{ ID id-UL-DPCH-Information-RL-SetupRqstFDD				CRITICALITY reject	TYPE UL-DPCH-Information-RL-SetupRqstFDD			PRESENCE mandatory }|
	{ ID id-DL-DPCH-Information-RL-SetupRqstFDD				CRITICALITY reject	TYPE DL-DPCH-Information-RL-SetupRqstFDD			PRESENCE optional }|
	{ ID id-DCH-FDD-Information								CRITICALITY reject	TYPE DCH-FDD-Information					PRESENCE mandatory }|
	{ ID id-RL-InformationList-RL-SetupRqstFDD				CRITICALITY notify	TYPE RL-InformationList-RL-SetupRqstFDD			PRESENCE mandatory }|
	{ ID id-Transmission-Gap-Pattern-Sequence-Information	CRITICALITY reject	TYPE Transmission-Gap-Pattern-Sequence-Information								PRESENCE optional } |
	{ ID id-Active-Pattern-Sequence-Information				CRITICALITY reject	TYPE Active-Pattern-Sequence-Information			PRESENCE optional },
	...
}

RadioLinkSetupRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-PowerBalancing-Information				CRITICALITY ignore	EXTENSION DL-PowerBalancing-Information				PRESENCE optional}|
	{ ID id-HSDSCH-FDD-Information						CRITICALITY reject	EXTENSION HSDSCH-FDD-Information						PRESENCE optional}|
	{ ID id-HSDSCH-RNTI									CRITICALITY reject	EXTENSION HSDSCH-RNTI										PRESENCE conditional}|
	-- The IE shall be present if HS-DSCH Information IE is present
	{ ID id-HSPDSCH-RL-ID								CRITICALITY reject	EXTENSION RL-ID												PRESENCE conditional}|
	-- The IE shall be present if HS-DSCH Information IE is present
	{ ID id-E-DPCH-Information-RL-SetupRqstFDD			CRITICALITY reject	EXTENSION E-DPCH-Information-RL-SetupRqstFDD		PRESENCE optional}|
	{ ID id-E-DCH-FDD-Information						CRITICALITY reject	EXTENSION E-DCH-FDD-Information						PRESENCE conditional}|
	-- The IE shall be present if E-DPCH Information IE is present
	{ ID id-Serving-E-DCH-RL-ID							CRITICALITY reject	EXTENSION Serving-E-DCH-RL-ID							PRESENCE optional}|
	{ ID id-F-DPCH-Information-RL-SetupRqstFDD			CRITICALITY reject	EXTENSION F-DPCH-Information-RL-SetupRqstFDD		PRESENCE optional}|
	{ ID id-Initial-DL-DPCH-TimingAdjustment-Allowed	CRITICALITY ignore	EXTENSION Initial-DL-DPCH-TimingAdjustment-Allowed	PRESENCE optional}|
	{ ID id-DCH-Indicator-For-E-DCH-HSDPA-Operation		CRITICALITY reject	EXTENSION DCH-Indicator-For-E-DCH-HSDPA-Operation	PRESENCE optional}|
	{ ID id-Serving-Cell-Change-CFN						CRITICALITY reject	EXTENSION CFN												PRESENCE optional}|
	{ ID id-ContinuousPacketConnectivityDTX-DRX-Information	CRITICALITY reject	EXTENSION ContinuousPacketConnectivityDTX-DRX-Information	PRESENCE optional}|
	{ ID id-ContinuousPacketConnectivityHS-SCCH-less-Information	CRITICALITY reject	EXTENSION ContinuousPacketConnectivityHS-SCCH-less-Information	PRESENCE optional}|
	{ ID id-Additional-HS-Cell-Information-RL-Setup		CRITICALITY reject	EXTENSION Additional-HS-Cell-Information-RL-Setup-List	PRESENCE optional}|
	{ ID id-UE-AggregateMaximumBitRate					CRITICALITY ignore	EXTENSION UE-AggregateMaximumBitRate					PRESENCE optional}|
	{ ID id-Additional-EDCH-Cell-Information-RL-Setup-Req	CRITICALITY reject	EXTENSION Additional-EDCH-Setup-Info			PRESENCE optional}|
	{ ID id-Usefulness-Of-Battery-Optimization			CRITICALITY ignore	EXTENSION Usefulness-Of-Battery-Optimization		PRESENCE optional}|
	{ ID id-UL-CLTD-Information							CRITICALITY reject	EXTENSION UL-CLTD-Information							PRESENCE optional}|
	{ ID id-E-DCH-Decoupling-Indication					CRITICALITY reject	EXTENSION E-DCH-Decoupling-Indication				PRESENCE optional}|
	{ ID id-DCH-ENH-Information							CRITICALITY reject	EXTENSION DCH-ENH-Information							PRESENCE optional}|
	{ ID id-Radio-Links-without-DPCH-FDPCH-Indication	CRITICALITY reject	EXTENSION Radio-Links-without-DPCH-FDPCH-Indication		PRESENCE optional}|
	{ ID id-UL-DPCCH2-Information						CRITICALITY reject	EXTENSION UL-DPCCH2-Information						PRESENCE optional}|
	{ ID id-Downlink-TPC-enhancements-Information		CRITICALITY reject	EXTENSION Downlink-TPC-enhancements-Information	PRESENCE optional},
	...
}

Additional-HS-Cell-Information-RL-Setup-List	::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Information-RL-Setup-ItemIEs

Additional-HS-Cell-Information-RL-Setup-ItemIEs	::=SEQUENCE{
	hSPDSCH-RL-ID									RL-ID,
	c-ID											C-ID,
	hS-DSCH-FDD-Secondary-Serving-Information		HS-DSCH-FDD-Secondary-Serving-Information,
	iE-Extensions					ProtocolExtensionContainer { { Additional-HS-Cell-Information-RL-Setup-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-HS-Cell-Information-RL-Setup-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-DPCH-Information-RL-SetupRqstFDD ::= SEQUENCE {
	ul-ScramblingCode						UL-ScramblingCode,
	minUL-ChannelisationCodeLength			MinUL-ChannelisationCodeLength,
	maxNrOfUL-DPDCHs						MaxNrOfUL-DPDCHs		OPTIONAL,
	-- This IE shall be present if Min UL Channelisation Code length IE is set to 4 --
	ul-PunctureLimit						PunctureLimit,
	tFCS									TFCS,
	ul-DPCCH-SlotFormat						UL-DPCCH-SlotFormat,
	ul-SIR-Target							UL-SIR,
	diversityMode							DiversityMode,
	not-Used-sSDT-CellID-Length				NULL					OPTIONAL,
	not-Used-s-FieldLength					NULL					OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-Information-RL-SetupRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

UL-DPCH-Information-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DPC-Mode								CRITICALITY reject	EXTENSION DPC-Mode						PRESENCE optional }|
	{ ID id-UL-DPDCH-Indicator-For-E-DCH-Operation	CRITICALITY reject	EXTENSION UL-DPDCH-Indicator-For-E-DCH-Operation		PRESENCE optional },
	...
}

DL-DPCH-Information-RL-SetupRqstFDD ::= SEQUENCE {
	tFCS									TFCS,
	dl-DPCH-SlotFormat						DL-DPCH-SlotFormat,
	tFCI-SignallingMode						TFCI-SignallingMode,
	tFCI-Presence							TFCI-Presence					OPTIONAL,
	-- this IE shall be present if the DL DPCH slot format IE is set to any of the values from 12 to 16 --	
	multiplexingPosition					MultiplexingPosition,
	not-Used-pDSCH-RL-ID					NULL							OPTIONAL,
	not-Used-pDSCH-CodeMapping				NULL							OPTIONAL,
	powerOffsetInformation					PowerOffsetInformation-RL-SetupRqstFDD,
	fdd-TPC-DownlinkStepSize				FDD-TPC-DownlinkStepSize,
	limitedPowerIncrease					LimitedPowerIncrease,
	innerLoopDLPCStatus						InnerLoopDLPCStatus,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-Information-RL-SetupRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

DL-DPCH-Information-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PowerOffsetInformation-RL-SetupRqstFDD ::= SEQUENCE {
	pO1-ForTFCI-Bits						PowerOffset,
	pO2-ForTPC-Bits							PowerOffset,
	pO3-ForPilotBits						PowerOffset,
	iE-Extensions							ProtocolExtensionContainer { { PowerOffsetInformation-RL-SetupRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

PowerOffsetInformation-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-InformationList-RL-SetupRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF
	ProtocolIE-Single-Container{{ RL-InformationItemIE-RL-SetupRqstFDD }}

RL-InformationItemIE-RL-SetupRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-InformationItem-RL-SetupRqstFDD			CRITICALITY notify			TYPE RL-InformationItem-RL-SetupRqstFDD		PRESENCE mandatory }
}

RL-InformationItem-RL-SetupRqstFDD ::= SEQUENCE {
	rL-ID								RL-ID,
	c-ID								C-ID,
	firstRLS-indicator					FirstRLS-Indicator,
	frameOffset							FrameOffset,
	chipOffset							ChipOffset,
	propagationDelay					PropagationDelay				OPTIONAL,
	diversityControlField				DiversityControlField			OPTIONAL,
	-- This IE shall be present if the RL is not the first one in the RL Information IE
	dl-CodeInformation					FDD-DL-CodeInformation,
	initialDL-transmissionPower			DL-Power,
	maximumDL-power						DL-Power,
	minimumDL-power						DL-Power,
	not-Used-sSDT-Cell-Identity			NULL							OPTIONAL,
	transmitDiversityIndicator			TransmitDiversityIndicator		OPTIONAL,
	-- This IE shall be present if Diversity Mode IE in UL DPCH Information group is not set to “none”
	iE-Extensions						ProtocolExtensionContainer { { RL-InformationItem-RL-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

RL-InformationItem-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-RL-Specific-DCH-Info						CRITICALITY ignore	EXTENSION RL-Specific-DCH-Info					PRESENCE optional}|
	{ ID id-DelayedActivation							CRITICALITY reject	EXTENSION DelayedActivation						PRESENCE optional}|
	{ ID id-Primary-CPICH-Usage-for-Channel-Estimation	CRITICALITY ignore	EXTENSION Primary-CPICH-Usage-for-Channel-Estimation	PRESENCE optional}|
	{ ID id-Secondary-CPICH-Information					CRITICALITY ignore	EXTENSION CommonPhysicalChannelID				PRESENCE optional}|
	{ ID id-E-DCH-RL-Indication							CRITICALITY reject	EXTENSION E-DCH-RL-Indication					PRESENCE optional}|
	{ ID id-RL-Specific-E-DCH-Info						CRITICALITY ignore	EXTENSION RL-Specific-E-DCH-Info				PRESENCE optional}|
	{ ID id-SynchronisationIndicator					CRITICALITY ignore	EXTENSION SynchronisationIndicator			PRESENCE optional}|
	{ ID id-ExtendedPropagationDelay					CRITICALITY ignore	EXTENSION ExtendedPropagationDelay			PRESENCE optional}|
	{ ID id-F-DPCH-SlotFormat							CRITICALITY reject	EXTENSION F-DPCH-SlotFormat						PRESENCE optional}|
	{ ID id-HSDSCH-PreconfigurationSetup				CRITICALITY ignore	EXTENSION HSDSCH-PreconfigurationSetup		PRESENCE optional}|
	{ ID id-E-RNTI										CRITICALITY ignore	EXTENSION E-RNTI									PRESENCE optional}|
	{ ID id-Non-Serving-RL-Preconfig-Setup				CRITICALITY ignore	EXTENSION Non-Serving-RL-Preconfig-Setup	PRESENCE optional}|
	{ ID id-FTPICH-Information							CRITICALITY ignore	EXTENSION FTPICH-Information					PRESENCE optional}|
	{ ID id-TPC-slot-position							CRITICALITY ignore	EXTENSION TPC-slot-position						PRESENCE optional},
	...
}

E-DPCH-Information-RL-SetupRqstFDD ::= SEQUENCE {
	maxSet-E-DPDCHs								Max-Set-E-DPDCHs,
	ul-PunctureLimit							PunctureLimit,
	e-TFCS-Information							E-TFCS-Information,
	e-TTI										E-TTI,
	e-DPCCH-PO									E-DPCCH-PO,
	e-RGCH-2-IndexStepThreshold					E-RGCH-2-IndexStepThreshold,
	e-RGCH-3-IndexStepThreshold					E-RGCH-3-IndexStepThreshold,
	hARQ-Info-for-E-DCH							HARQ-Info-for-E-DCH,
	hSDSCH-Configured-Indicator					HSDSCH-Configured-Indicator,
	iE-Extensions								ProtocolExtensionContainer { { E-DPCH-Information-RL-SetupRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

E-DPCH-Information-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-RNTI									CRITICALITY reject	EXTENSION E-RNTI			PRESENCE optional }|
	{ ID id-MinimumReducedE-DPDCH-GainFactor		CRITICALITY ignore	EXTENSION MinimumReducedE-DPDCH-GainFactor	PRESENCE optional },
	...
}

F-DPCH-Information-RL-SetupRqstFDD ::= SEQUENCE {
	powerOffsetInformation				PowerOffsetInformation-F-DPCH-RL-SetupRqstFDD,
	fdd-TPC-DownlinkStepSize			FDD-TPC-DownlinkStepSize,
	limitedPowerIncrease				LimitedPowerIncrease,
	innerLoopDLPCStatus					InnerLoopDLPCStatus,
	iE-Extensions						ProtocolExtensionContainer { { F-DPCH-Information-RL-SetupRqstFDD-ExtIEs} }					OPTIONAL,
	...
}

F-DPCH-Information-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PowerOffsetInformation-F-DPCH-RL-SetupRqstFDD ::= SEQUENCE {
	pO2-ForTPC-Bits						PowerOffset,
	--This IE shall be ignored by Node B
	iE-Extensions						ProtocolExtensionContainer { { PowerOffsetInformation-F-DPCH-RL-SetupRqstFDD-ExtIEs} }	OPTIONAL,
	...
}

PowerOffsetInformation-F-DPCH-RL-SetupRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK SETUP REQUEST TDD
--
-- **************************************************************

RadioLinkSetupRequestTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkSetupRequestTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkSetupRequestTDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkSetupRequestTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CRNC-CommunicationContextID					CRITICALITY reject	TYPE CRNC-CommunicationContextID					PRESENCE mandatory }|
	{ ID	id-UL-CCTrCH-InformationList-RL-SetupRqstTDD	CRITICALITY notify	TYPE UL-CCTrCH-InformationList-RL-SetupRqstTDD	PRESENCE optional }|
	{ ID	id-DL-CCTrCH-InformationList-RL-SetupRqstTDD	CRITICALITY notify	TYPE DL-CCTrCH-InformationList-RL-SetupRqstTDD	PRESENCE optional }|
	{ ID	id-DCH-TDD-Information							CRITICALITY reject	TYPE DCH-TDD-Information					PRESENCE optional }|
	{ ID	id-DSCH-TDD-Information							CRITICALITY reject	TYPE DSCH-TDD-Information					PRESENCE optional }|
	{ ID	id-USCH-Information								CRITICALITY reject	TYPE USCH-Information					PRESENCE optional }|
	{ ID	id-RL-Information-RL-SetupRqstTDD				CRITICALITY reject	TYPE RL-Information-RL-SetupRqstTDD					PRESENCE mandatory },
	...
}

RadioLinkSetupRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-HSDSCH-TDD-Information			CRITICALITY reject	EXTENSION HSDSCH-TDD-Information				PRESENCE optional }|
	{ ID id-HSDSCH-RNTI						CRITICALITY reject	EXTENSION HSDSCH-RNTI							PRESENCE conditional }|
	-- The IE shall be present if HS-DSCH Information IE is present
	{ ID id-HSPDSCH-RL-ID					CRITICALITY reject	EXTENSION RL-ID									PRESENCE conditional }|
	-- The IE shall be present if HS-DSCH Information IE is present
	{ ID id-PDSCH-RL-ID						CRITICALITY ignore	EXTENSION RL-ID									PRESENCE optional }|
	{ ID id-E-DCH-Information				CRITICALITY reject	EXTENSION E-DCH-Information						PRESENCE optional }|
	{ ID id-E-DCH-Serving-RL-ID				CRITICALITY reject	EXTENSION RL-ID									PRESENCE optional }|
	{ ID id-E-DCH-768-Information			CRITICALITY reject	EXTENSION E-DCH-768-Information					PRESENCE optional }|
	{ ID id-E-DCH-LCR-Information			CRITICALITY reject	EXTENSION E-DCH-LCR-Information					PRESENCE optional }|
	{ ID id-PowerControlGAP					CRITICALITY ignore	EXTENSION ControlGAP							PRESENCE optional }|
	 -- Applicable to 1.28Mcps TDD only
	{ ID id-ContinuousPacketConnectivity-DRX-InformationLCR		CRITICALITY reject	EXTENSION ContinuousPacketConnectivity-DRX-InformationLCR	PRESENCE optional }|
	{ ID id-HS-DSCH-Semi-PersistentScheduling-Information-LCR	CRITICALITY reject	EXTENSION HS-DSCH-Semi-PersistentScheduling-Information-LCR	PRESENCE optional }|
	{ ID id-E-DCH-Semi-PersistentScheduling-Information-LCR		CRITICALITY reject	EXTENSION E-DCH-Semi-PersistentScheduling-Information-LCR	PRESENCE optional }|
	{ ID id-IdleIntervalInformation			CRITICALITY ignore	EXTENSION IdleIntervalInformation				PRESENCE optional }|
	{ ID id-UE-Selected-MBMS-Service-Information	CRITICALITY ignore	EXTENSION UE-Selected-MBMS-Service-Information	PRESENCE optional }|
	{ ID id-HSSCCH-TPC-StepSize				CRITICALITY	ignore	EXTENSION TDD-TPC-DownlinkStepSize			PRESENCE optional }|
	{ ID id-DCH-MeasurementOccasion-Information	CRITICALITY reject	EXTENSION DCH-MeasurementOccasion-Information	PRESENCE optional }|
	{ ID id-HSDSCH-RNTI-For-FACH			CRITICALITY ignore	EXTENSION HSDSCH-RNTI							PRESENCE optional }|
	{ ID id-Multi-Carrier-EDCH-Setup		CRITICALITY reject	EXTENSION Multi-Carrier-EDCH-Info				PRESENCE optional }|
	{ ID id-MU-MIMO-InformationLCR			CRITICALITY ignore	EXTENSION MU-MIMO-InformationLCR				PRESENCE optional }|
	{ ID id-UE-Support-of-non-rectangular-resource-allocation	CRITICALITY ignore	EXTENSION UE-Support-of-non-rectangular-resource-allocation			PRESENCE optional},
	...
}

UL-CCTrCH-InformationList-RL-SetupRqstTDD ::= SEQUENCE (SIZE(1..maxNrOfCCTrCHs)) OF
	ProtocolIE-Single-Container{{ UL-CCTrCH-InformationItemIE-RL-SetupRqstTDD }}

UL-CCTrCH-InformationItemIE-RL-SetupRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-UL-CCTrCH-InformationItem-RL-SetupRqstTDD		CRITICALITY notify		TYPE UL-CCTrCH-InformationItem-RL-SetupRqstTDD		PRESENCE mandatory }
}

UL-CCTrCH-InformationItem-RL-SetupRqstTDD ::= SEQUENCE {
	cCTrCH-ID								CCTrCH-ID,
	tFCS									TFCS,
	tFCI-Coding								TFCI-Coding,
	punctureLimit							PunctureLimit,
	uL-DPCH-Information						UL-DPCH-Information-RL-SetupRqstTDD		OPTIONAL, 	-- Applicable to 3.84Mcps TDD only
	iE-Extensions							ProtocolExtensionContainer { { UL-CCTrCH-InformationItem-RL-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-CCTrCH-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UL-DPCH-LCR-Information-RL-SetupRqstTDD		CRITICALITY notify	EXTENSION UL-DPCH-LCR-Information-RL-SetupRqstTDD	PRESENCE optional	}|	-- Applicable to 1.28Mcps TDD only
	{ ID id-UL-SIRTarget								CRITICALITY reject	EXTENSION UL-SIR						PRESENCE optional	}|
	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
	{ ID id-TDD-TPC-UplinkStepSize-LCR-RL-SetupRqstTDD	CRITICALITY reject	EXTENSION TDD-TPC-UplinkStepSize-LCR					PRESENCE optional	}|
	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
	{ ID id-UL-DPCH-768-Information-RL-SetupRqstTDD		CRITICALITY notify	EXTENSION UL-DPCH-768-Information-RL-SetupRqstTDD	PRESENCE optional	},	-- Applicable to 7.68Mcps TDD only
	...
}

UL-DPCH-Information-RL-SetupRqstTDD ::= ProtocolIE-Single-Container{{ UL-DPCH-InformationIE-RL-SetupRqstTDD }}

UL-DPCH-InformationIE-RL-SetupRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-UL-DPCH-InformationList-RL-SetupRqstTDD		CRITICALITY notify	TYPE UL-DPCH-InformationItem-RL-SetupRqstTDD		PRESENCE mandatory	}
}

UL-DPCH-InformationItem-RL-SetupRqstTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	uL-Timeslot-Information					UL-Timeslot-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-InformationItem-RL-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-DPCH-LCR-Information-RL-SetupRqstTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	uL-TimeslotLCR-Information				UL-TimeslotLCR-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-LCR-InformationItem-RL-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-LCR-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-DPCH-768-Information-RL-SetupRqstTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	uL-Timeslot768-Information				UL-Timeslot768-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-768-InformationItem-RL-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-768-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-CCTrCH-InformationList-RL-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container{{ DL-CCTrCH-InformationItemIE-RL-SetupRqstTDD }}

DL-CCTrCH-InformationItemIE-RL-SetupRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-DL-CCTrCH-InformationItem-RL-SetupRqstTDD	CRITICALITY notify	TYPE DL-CCTrCH-InformationItem-RL-SetupRqstTDD		PRESENCE mandatory}
}

DL-CCTrCH-InformationItem-RL-SetupRqstTDD ::= SEQUENCE {
	cCTrCH-ID								CCTrCH-ID,
	tFCS									TFCS,
	tFCI-Coding								TFCI-Coding,
	punctureLimit							PunctureLimit,
	tdd-TPC-DownlinkStepSize				TDD-TPC-DownlinkStepSize,
	cCTrCH-TPCList							CCTrCH-TPCList-RL-SetupRqstTDD			OPTIONAL,
	dL-DPCH-Information						DL-DPCH-Information-RL-SetupRqstTDD		OPTIONAL, 	-- Applicable to 3.84Mcps TDD only
	iE-Extensions							ProtocolExtensionContainer { { DL-CCTrCH-InformationItem-RL-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-CCTrCH-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-DPCH-LCR-Information-RL-SetupRqstTDD		CRITICALITY notify		EXTENSION DL-DPCH-LCR-Information-RL-SetupRqstTDD		PRESENCE optional	}|	-- Applicable to 1.28Mcps TDD only
	{ ID id-CCTrCH-Initial-DL-Power-RL-SetupRqstTDD		CRITICALITY ignore		EXTENSION DL-Power		PRESENCE optional	}|
	{ ID id-CCTrCH-Maximum-DL-Power-RL-SetupRqstTDD		CRITICALITY ignore		EXTENSION DL-Power		PRESENCE optional	}|
	{ ID id-CCTrCH-Minimum-DL-Power-RL-SetupRqstTDD		CRITICALITY ignore		EXTENSION DL-Power		PRESENCE optional	}|
	{ ID id-DL-DPCH-768-Information-RL-SetupRqstTDD		CRITICALITY notify		EXTENSION DL-DPCH-768-Information-RL-SetupRqstTDD		PRESENCE optional	},	-- Applicable to 7.68Mcps TDD only
	...
}

CCTrCH-TPCList-RL-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF CCTrCH-TPCItem-RL-SetupRqstTDD

CCTrCH-TPCItem-RL-SetupRqstTDD	 ::= SEQUENCE {
	cCTrCH-ID								CCTrCH-ID,
	iE-Extensions							ProtocolExtensionContainer { { CCTrCH-TPCItem-RL-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

CCTrCH-TPCItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-DPCH-Information-RL-SetupRqstTDD ::= ProtocolIE-Single-Container{{ DL-DPCH-InformationIE-RL-SetupRqstTDD }}

DL-DPCH-InformationIE-RL-SetupRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-DL-DPCH-InformationList-RL-SetupRqstTDD		CRITICALITY notify	TYPE DL-DPCH-InformationItem-RL-SetupRqstTDD		PRESENCE mandatory	}
}

DL-DPCH-InformationItem-RL-SetupRqstTDD	 ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	dL-Timeslot-Information					DL-Timeslot-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-InformationItem-RL-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-DPCH-LCR-Information-RL-SetupRqstTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	dL-TimeslotLCR-Information				DL-TimeslotLCR-Information,
	tstdIndicator							TSTD-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-LCR-InformationItem-RL-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-LCR-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-DPCH-768-Information-RL-SetupRqstTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	dL-Timeslot768-Information				DL-Timeslot768-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-768-InformationItem-RL-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-768-InformationItem-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-Information-RL-SetupRqstTDD ::= SEQUENCE {
	rL-ID									RL-ID,
	c-ID									C-ID,
	frameOffset								FrameOffset,
	specialBurstScheduling					SpecialBurstScheduling,
	initialDL-transmissionPower				DL-Power,
	maximumDL-power							DL-Power,
	minimumDL-power							DL-Power,
	dL-TimeSlotISCPInfo						DL-TimeslotISCPInfo	OPTIONAL, 	-- Applicable to 3.84Mcps TDD and 7.68Mcps TDD only
	iE-Extensions							ProtocolExtensionContainer { { RL-Information-RL-SetupRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

RL-Information-RL-SetupRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TimeslotISCP-LCR-InfoList-RL-SetupRqstTDD	CRITICALITY reject		EXTENSION DL-TimeslotISCPInfoLCR				PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-RL-Specific-DCH-Info						CRITICALITY ignore		EXTENSION RL-Specific-DCH-Info				PRESENCE optional }|
	{ ID id-DelayedActivation							CRITICALITY reject		EXTENSION DelayedActivation 				PRESENCE optional }|
	{ ID id-UL-Synchronisation-Parameters-LCR			CRITICALITY reject		EXTENSION UL-Synchronisation-Parameters-LCR	PRESENCE optional }|
	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD
	{ ID id-UARFCNforNt									CRITICALITY reject		EXTENSION UARFCN				PRESENCE optional },
	-- Mandatory for 1.28Mcps TDD when using multiple frequencies
	...
}

-- **************************************************************
--
-- RADIO LINK SETUP RESPONSE FDD
--
-- **************************************************************

RadioLinkSetupResponseFDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkSetupResponseFDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkSetupResponseFDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkSetupResponseFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID					CRITICALITY ignore	TYPE CRNC-CommunicationContextID					PRESENCE mandatory }|
	{ ID id-NodeB-CommunicationContextID				CRITICALITY ignore	TYPE NodeB-CommunicationContextID					PRESENCE mandatory }|
	{ ID id-CommunicationControlPortID					CRITICALITY ignore	TYPE CommunicationControlPortID					PRESENCE mandatory }|
	{ ID id-RL-InformationResponseList-RL-SetupRspFDD	CRITICALITY ignore	TYPE RL-InformationResponseList-RL-SetupRspFDD		PRESENCE mandatory }|
	{ ID id-CriticalityDiagnostics						CRITICALITY ignore	TYPE CriticalityDiagnostics					PRESENCE optional },
	...
}

RadioLinkSetupResponseFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-HSDSCH-FDD-Information-Response				CRITICALITY ignore	EXTENSION HSDSCH-FDD-Information-Response				PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivityHS-SCCH-less-Information-Response		CRITICALITY ignore	EXTENSION	ContinuousPacketConnectivityHS-SCCH-less-Information-Response			PRESENCE optional }|
	{ ID id-Additional-HS-Cell-Information-Response		CRITICALITY ignore	EXTENSION	Additional-HS-Cell-Information-Response-List			PRESENCE optional }|
	{ ID id-Additional-EDCH-Cell-Information-Response		CRITICALITY ignore	EXTENSION	Additional-EDCH-Cell-Information-Response-List			PRESENCE optional },
	...
}
Additional-HS-Cell-Information-Response-List	::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Information-Response-ItemIEs

Additional-HS-Cell-Information-Response-ItemIEs	::=SEQUENCE{
	hSPDSCH-RL-ID										RL-ID,
	hS-DSCH-FDD-Secondary-Serving-Information-Response	HS-DSCH-FDD-Secondary-Serving-Information-Response,
	iE-Extensions					ProtocolExtensionContainer { { Additional-HS-Cell-Information-Response-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-HS-Cell-Information-Response-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-InformationResponseList-RL-SetupRspFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container{{ RL-InformationResponseItemIE-RL-SetupRspFDD }}
	
RL-InformationResponseItemIE-RL-SetupRspFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-InformationResponseItem-RL-SetupRspFDD	CRITICALITY ignore	TYPE RL-InformationResponseItem-RL-SetupRspFDD	PRESENCE mandatory }
}

RL-InformationResponseItem-RL-SetupRspFDD ::= SEQUENCE {
	rL-ID											RL-ID,
	rL-Set-ID										RL-Set-ID,
	received-total-wide-band-power					Received-total-wide-band-power-Value,
	diversityIndication								DiversityIndication-RL-SetupRspFDD,
	not-Used-dSCH-InformationResponseList			NULL							OPTIONAL,
	sSDT-SupportIndicator							SSDT-SupportIndicator,
	iE-Extensions									ProtocolExtensionContainer { { RL-InformationResponseItem-RL-SetupRspFDD-ExtIEs} }		OPTIONAL,
	...
}

RL-InformationResponseItem-RL-SetupRspFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-PowerBalancing-ActivationIndicator		CRITICALITY ignore	EXTENSION DL-PowerBalancing-ActivationIndicator		PRESENCE optional }|
	{ ID id-E-DCH-RL-Set-ID								CRITICALITY ignore	EXTENSION RL-Set-ID												PRESENCE optional }|
	{ ID id-E-DCH-FDD-DL-Control-Channel-Information	CRITICALITY ignore	EXTENSION E-DCH-FDD-DL-Control-Channel-Information	PRESENCE optional }|
	{ ID id-Initial-DL-DPCH-TimingAdjustment			CRITICALITY ignore	EXTENSION DL-DPCH-TimingAdjustment						PRESENCE optional }|
	{ ID id-HSDSCH-PreconfigurationInfo					CRITICALITY ignore	EXTENSION HSDSCH-PreconfigurationInfo					PRESENCE optional }|
	{ ID id-Non-Serving-RL-Preconfig-Info				CRITICALITY ignore	EXTENSION Non-Serving-RL-Preconfig-Info					PRESENCE optional },
	...
}

DiversityIndication-RL-SetupRspFDD ::= CHOICE {
	combining									Combining-RL-SetupRspFDD,
	nonCombiningOrFirstRL						NonCombiningOrFirstRL-RL-SetupRspFDD
}

Combining-RL-SetupRspFDD ::= SEQUENCE {
	rL-ID										RL-ID,
	iE-Extensions								ProtocolExtensionContainer { { Combining-RL-SetupRspFDD-ExtIEs} }		OPTIONAL,
	...
}

Combining-RL-SetupRspFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

NonCombiningOrFirstRL-RL-SetupRspFDD ::= SEQUENCE {
	dCH-InformationResponse						DCH-InformationResponse,
	iE-Extensions								ProtocolExtensionContainer { { NonCombiningOrFirstRLItem-RL-SetupRspFDD-ExtIEs} }		OPTIONAL,
	...
}

NonCombiningOrFirstRLItem-RL-SetupRspFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-FDD-Information-Response		CRITICALITY ignore	EXTENSION E-DCH-FDD-Information-Response		PRESENCE optional },
	...
}

-- **************************************************************
--
-- RADIO LINK SETUP RESPONSE TDD
--
-- **************************************************************

RadioLinkSetupResponseTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkSetupResponseTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkSetupResponseTDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkSetupResponseTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID				CRITICALITY ignore	TYPE CRNC-CommunicationContextID				PRESENCE mandatory }|
	{ ID id-NodeB-CommunicationContextID			CRITICALITY ignore	TYPE NodeB-CommunicationContextID				PRESENCE mandatory }|
	{ ID id-CommunicationControlPortID				CRITICALITY ignore	TYPE CommunicationControlPortID				PRESENCE mandatory }|
	{ ID id-RL-InformationResponse-RL-SetupRspTDD	CRITICALITY ignore	TYPE RL-InformationResponse-RL-SetupRspTDD				PRESENCE optional }|
	-- Mandatory for 3.84Mcps TDD and 7.68Mcps TDD, Not Applicable to 1.28Mcps TDD
	{ ID id-CriticalityDiagnostics					CRITICALITY ignore	TYPE CriticalityDiagnostics				PRESENCE optional },
	...
}

RadioLinkSetupResponseTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-RL-InformationResponse-LCR-RL-SetupRspTDD	CRITICALITY ignore	EXTENSION RL-InformationResponse-LCR-RL-SetupRspTDD	PRESENCE optional }|	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD
	{ ID id-HSDSCH-TDD-Information-Response				CRITICALITY ignore	EXTENSION HSDSCH-TDD-Information-Response				PRESENCE optional }|
	{ ID id-E-DCH-Information-Response					CRITICALITY ignore	EXTENSION E-DCH-Information-Response						PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR	CRITICALITY ignore	EXTENSION ContinuousPacketConnectivity-DRX-Information-ResponseLCR		PRESENCE optional }|
	{ ID id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR	CRITICALITY ignore	EXTENSION HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR		PRESENCE optional }|
	{ ID id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR		CRITICALITY ignore	EXTENSION E-DCH-Semi-PersistentScheduling-Information-ResponseLCR		PRESENCE optional }|
	{ ID id-E-RNTI-For-FACH								CRITICALITY ignore	EXTENSION E-RNTI												PRESENCE optional }|
	{ ID id-Multi-Carrier-EDCH-Response					CRITICALITY ignore	EXTENSION Multi-Carrier-EDCH-Information-Response	PRESENCE optional }|
	{ ID id-MU-MIMO-Information-Response				CRITICALITY reject	EXTENSION MU-MIMO-Information-Response					PRESENCE optional }|
	{ ID id-Non-rectangular-resource-allocation-indicator	CRITICALITY reject	EXTENSION Non-rectangular-resource-allocation-indicator				PRESENCE optional}|
	{ ID id-Non-rectangular-resource-timeslot-set		CRITICALITY reject	EXTENSION Non-rectangular-resource-timeslot-set		PRESENCE optional},
	...
}

RL-InformationResponse-RL-SetupRspTDD ::= SEQUENCE {
	rL-ID											RL-ID,
	uL-TimeSlot-ISCP-Info							UL-TimeSlot-ISCP-Info,
	ul-PhysCH-SF-Variation							UL-PhysCH-SF-Variation,
	dCH-InformationResponseList						DCH-InformationResponseList-RL-SetupRspTDD			OPTIONAL,
	dSCH-InformationResponseList					DSCH-InformationResponseList-RL-SetupRspTDD			OPTIONAL,
	uSCH-InformationResponseList					USCH-InformationResponseList-RL-SetupRspTDD			OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { RL-InformationResponseList-RL-SetupRspTDD-ExtIEs} }		OPTIONAL,
	...
}

RL-InformationResponseList-RL-SetupRspTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DCH-InformationResponseList-RL-SetupRspTDD ::= ProtocolIE-Single-Container{{ DCH-InformationResponseListIEs-RL-SetupRspTDD }}

DCH-InformationResponseListIEs-RL-SetupRspTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-DCH-InformationResponse	CRITICALITY 	ignore		TYPE 	DCH-InformationResponse  PRESENCE	mandatory}
 }

DSCH-InformationResponseList-RL-SetupRspTDD ::= ProtocolIE-Single-Container {{ DSCH-InformationResponseListIEs-RL-SetupRspTDD }}

DSCH-InformationResponseListIEs-RL-SetupRspTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-DSCH-InformationResponse   CRITICALITY ignore	TYPE DSCH-InformationResponse		PRESENCE mandatory }
}

USCH-InformationResponseList-RL-SetupRspTDD ::= ProtocolIE-Single-Container {{ USCH-InformationResponseListIEs-RL-SetupRspTDD }}

USCH-InformationResponseListIEs-RL-SetupRspTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-USCH-InformationResponse   CRITICALITY ignore	TYPE USCH-InformationResponse		PRESENCE mandatory }
}

RL-InformationResponse-LCR-RL-SetupRspTDD ::= SEQUENCE {
	rL-ID											RL-ID,
	uL-TimeSlot-ISCP-LCR-Info						UL-TimeSlot-ISCP-LCR-Info,
	ul-PhysCH-SF-Variation							UL-PhysCH-SF-Variation,
	dCH-InformationResponseList						DCH-InformationResponseList-RL-SetupRspTDD			OPTIONAL,
	dSCH-InformationResponseList					DSCH-InformationResponseList-RL-SetupRspTDD			OPTIONAL,
	uSCH-InformationResponseList					USCH-InformationResponseList-RL-SetupRspTDD			OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { RL-InformationResponseList-LCR-RL-SetupRspTDD-ExtIEs} }		OPTIONAL,
	...
}

RL-InformationResponseList-LCR-RL-SetupRspTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK SETUP FAILURE FDD
--
-- **************************************************************

RadioLinkSetupFailureFDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkSetupFailureFDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkSetupFailureFDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkSetupFailureFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID			CRITICALITY ignore	TYPE CRNC-CommunicationContextID		PRESENCE mandatory }|
	{ ID id-NodeB-CommunicationContextID		CRITICALITY ignore	TYPE NodeB-CommunicationContextID		PRESENCE conditional }|
	-- This IE shall be present if at least one of the radio links has been successfully set up
	{ ID id-CommunicationControlPortID			CRITICALITY ignore	TYPE CommunicationControlPortID		PRESENCE optional }|
	{ ID id-CauseLevel-RL-SetupFailureFDD		CRITICALITY ignore	TYPE CauseLevel-RL-SetupFailureFDD		PRESENCE mandatory }|
	{ ID id-CriticalityDiagnostics				CRITICALITY ignore	TYPE CriticalityDiagnostics			PRESENCE optional },
	...
}

RadioLinkSetupFailureFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CauseLevel-RL-SetupFailureFDD ::= CHOICE {
	generalCause		GeneralCauseList-RL-SetupFailureFDD,
	rLSpecificCause		RLSpecificCauseList-RL-SetupFailureFDD,
	...
}

GeneralCauseList-RL-SetupFailureFDD ::= SEQUENCE {
	cause										Cause,
	iE-Extensions								ProtocolExtensionContainer { { GeneralCauseItem-RL-SetupFailureFDD-ExtIEs} }		OPTIONAL,
	...
}

GeneralCauseItem-RL-SetupFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RLSpecificCauseList-RL-SetupFailureFDD ::= SEQUENCE {
	unsuccessful-RL-InformationRespList-RL-SetupFailureFDD		Unsuccessful-RL-InformationRespList-RL-SetupFailureFDD,
	successful-RL-InformationRespList-RL-SetupFailureFDD		Successful-RL-InformationRespList-RL-SetupFailureFDD	OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { RLSpecificCauseItem-RL-SetupFailureFDD-ExtIEs} }		OPTIONAL,
	...
}

RLSpecificCauseItem-RL-SetupFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-HSDSCH-FDD-Information-Response		CRITICALITY ignore		EXTENSION HSDSCH-FDD-Information-Response			PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivityHS-SCCH-less-Information-Response		CRITICALITY ignore		EXTENSION	ContinuousPacketConnectivityHS-SCCH-less-Information-Response			PRESENCE optional }|
	{ ID id-Additional-HS-Cell-Information-Response		CRITICALITY ignore	EXTENSION	Additional-HS-Cell-Information-Response-List			PRESENCE optional}|
	{ ID id-Additional-EDCH-Cell-Information-Response		CRITICALITY ignore	EXTENSION	Additional-EDCH-Cell-Information-Response-List			PRESENCE optional},
	...
}

Unsuccessful-RL-InformationRespList-RL-SetupFailureFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs))	OF ProtocolIE-Single-Container {{ Unsuccessful-RL-InformationRespItemIE-RL-SetupFailureFDD }}

Unsuccessful-RL-InformationRespItemIE-RL-SetupFailureFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-Unsuccessful-RL-InformationRespItem-RL-SetupFailureFDD	CRITICALITY ignore		TYPE Unsuccessful-RL-InformationRespItem-RL-SetupFailureFDD	PRESENCE mandatory }
}

Unsuccessful-RL-InformationRespItem-RL-SetupFailureFDD ::= SEQUENCE {
	rL-ID								RL-ID,
	cause								Cause,
	iE-Extensions						ProtocolExtensionContainer { { Unsuccessful-RL-InformationRespItem-RL-SetupFailureFDD-ExtIEs} }		OPTIONAL,
	...
}

Unsuccessful-RL-InformationRespItem-RL-SetupFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Successful-RL-InformationRespList-RL-SetupFailureFDD ::= SEQUENCE (SIZE (1.. maxNrOfRLs)) OF ProtocolIE-Single-Container	{{ Successful-RL-InformationRespItemIE-RL-SetupFailureFDD }}

Successful-RL-InformationRespItemIE-RL-SetupFailureFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-Successful-RL-InformationRespItem-RL-SetupFailureFDD		CRITICALITY ignore 		TYPE Successful-RL-InformationRespItem-RL-SetupFailureFDD	PRESENCE mandatory }
}

Successful-RL-InformationRespItem-RL-SetupFailureFDD ::= SEQUENCE {
	rL-ID										RL-ID,
	rL-Set-ID									RL-Set-ID,
	received-total-wide-band-power				Received-total-wide-band-power-Value,
	diversityIndication							DiversityIndication-RL-SetupFailureFDD,
	not-Used-dSCH-InformationResponseList		NULL						OPTIONAL,
	not-Used-tFCI2-BearerInformationResponse	NULL						OPTIONAL,
	sSDT-SupportIndicator						SSDT-SupportIndicator,
	iE-Extensions								ProtocolExtensionContainer { { Successful-RL-InformationRespItem-RL-SetupFailureFDD-ExtIEs} }		OPTIONAL,
	...
}

Successful-RL-InformationRespItem-RL-SetupFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-PowerBalancing-ActivationIndicator		CRITICALITY ignore	EXTENSION DL-PowerBalancing-ActivationIndicator		PRESENCE optional }|
	{ ID id-E-DCH-RL-Set-ID								CRITICALITY ignore	EXTENSION RL-Set-ID												PRESENCE optional }|
	{ ID id-E-DCH-FDD-DL-Control-Channel-Information	CRITICALITY ignore	EXTENSION E-DCH-FDD-DL-Control-Channel-Information	PRESENCE optional }|
	{ ID id-Initial-DL-DPCH-TimingAdjustment			CRITICALITY ignore	EXTENSION DL-DPCH-TimingAdjustment						PRESENCE optional }|
	{ ID id-HSDSCH-PreconfigurationInfo					CRITICALITY ignore	EXTENSION HSDSCH-PreconfigurationInfo					PRESENCE optional }|
	{ ID id-Non-Serving-RL-Preconfig-Info				CRITICALITY ignore	EXTENSION Non-Serving-RL-Preconfig-Info					PRESENCE optional },
	...
}

DiversityIndication-RL-SetupFailureFDD ::= CHOICE {
 	combining									Combining-RL-SetupFailureFDD,
 	nonCombiningOrFirstRL						NonCombiningOrFirstRL-RL-SetupFailureFDD
}

Combining-RL-SetupFailureFDD ::= SEQUENCE {
 	rL-ID										RL-ID,
	iE-Extensions								ProtocolExtensionContainer { { CombiningItem-RL-SetupFailureFDD-ExtIEs} }		OPTIONAL,
	...
 }

CombiningItem-RL-SetupFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

NonCombiningOrFirstRL-RL-SetupFailureFDD ::= SEQUENCE {
 	dCH-InformationResponse						DCH-InformationResponse,
	iE-Extensions									ProtocolExtensionContainer { { NonCombiningOrFirstRLItem-RL-SetupFailureFDD-ExtIEs} }		OPTIONAL,
	...
}

NonCombiningOrFirstRLItem-RL-SetupFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-FDD-Information-Response		CRITICALITY ignore	EXTENSION E-DCH-FDD-Information-Response		PRESENCE optional },
	...
}

-- **************************************************************
--
-- RADIO LINK SETUP FAILURE TDD
--
-- **************************************************************

RadioLinkSetupFailureTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkSetupFailureTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkSetupFailureTDD-Extensions}}			OPTIONAL,
	...
}

RadioLinkSetupFailureTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CRNC-CommunicationContextID			CRITICALITY ignore	TYPE CRNC-CommunicationContextID		PRESENCE mandatory	}|
	{ ID	id-CauseLevel-RL-SetupFailureTDD		CRITICALITY ignore	TYPE CauseLevel-RL-SetupFailureTDD		PRESENCE mandatory	}|
	{ ID	id-CriticalityDiagnostics				CRITICALITY ignore	TYPE CriticalityDiagnostics		PRESENCE optional	},
	...
}

RadioLinkSetupFailureTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CauseLevel-RL-SetupFailureTDD ::= CHOICE {
	generalCause		GeneralCauseList-RL-SetupFailureTDD,
	rLSpecificCause		RLSpecificCauseList-RL-SetupFailureTDD,
	...
}

GeneralCauseList-RL-SetupFailureTDD ::= SEQUENCE {
	cause						Cause,
	iE-Extensions				ProtocolExtensionContainer { { GeneralCauseItem-RL-SetupFailureTDD-ExtIEs} }		OPTIONAL,
	...
}

GeneralCauseItem-RL-SetupFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RLSpecificCauseList-RL-SetupFailureTDD ::= SEQUENCE {
	unsuccessful-RL-InformationRespItem-RL-SetupFailureTDD	Unsuccessful-RL-InformationRespItem-RL-SetupFailureTDD,
	iE-Extensions											ProtocolExtensionContainer { { RLSpecificCauseItem-RL-SetupFailureTDD-ExtIEs} }		OPTIONAL,
	...
}

RLSpecificCauseItem-RL-SetupFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Unsuccessful-RL-InformationRespItem-RL-SetupFailureTDD ::= ProtocolIE-Single-Container { {Unsuccessful-RL-InformationRespItemIE-RL-SetupFailureTDD} }

Unsuccessful-RL-InformationRespItemIE-RL-SetupFailureTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-Unsuccessful-RL-InformationResp-RL-SetupFailureTDD	CRITICALITY	ignore 	TYPE Unsuccessful-RL-InformationResp-RL-SetupFailureTDD		PRESENCE mandatory	}
}

Unsuccessful-RL-InformationResp-RL-SetupFailureTDD ::= SEQUENCE {
	rL-ID								RL-ID,
	cause								Cause,
	iE-Extensions						ProtocolExtensionContainer { { Unsuccessful-RL-InformationResp-RL-SetupFailureTDD-ExtIEs} }		OPTIONAL,
	...
}

Unsuccessful-RL-InformationResp-RL-SetupFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK ADDITION REQUEST FDD
--
-- **************************************************************

RadioLinkAdditionRequestFDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkAdditionRequestFDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkAdditionRequestFDD-Extensions}}			OPTIONAL,
	...
}

RadioLinkAdditionRequestFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-NodeB-CommunicationContextID			CRITICALITY reject	TYPE NodeB-CommunicationContextID		PRESENCE	mandatory	} |
	{ ID id-Compressed-Mode-Deactivation-Flag		CRITICALITY reject	TYPE Compressed-Mode-Deactivation-Flag		PRESENCE optional }|
	{ ID id-RL-InformationList-RL-AdditionRqstFDD	CRITICALITY notify	TYPE RL-InformationList-RL-AdditionRqstFDD		PRESENCE	mandatory	},
	...
}

RadioLinkAdditionRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Initial-DL-DPCH-TimingAdjustment-Allowed	CRITICALITY ignore	EXTENSION Initial-DL-DPCH-TimingAdjustment-Allowed	PRESENCE optional}|
	{ ID id-Serving-E-DCH-RL-ID							CRITICALITY reject	EXTENSION Serving-E-DCH-RL-ID								PRESENCE optional}|
	{ ID id-Serving-Cell-Change-CFN						CRITICALITY reject	EXTENSION CFN													PRESENCE optional}|
	{ ID id-HS-DSCH-Serving-Cell-Change-Info			CRITICALITY reject	EXTENSION HS-DSCH-Serving-Cell-Change-Info				PRESENCE optional}|
	{ ID id-E-DPCH-Information-RL-AdditionReqFDD		CRITICALITY reject	EXTENSION E-DPCH-Information-RL-AdditionReqFDD		PRESENCE optional}|
	{ ID id-E-DCH-FDD-Information						CRITICALITY reject	EXTENSION E-DCH-FDD-Information						PRESENCE conditional}|
	-- This IE shall be present if E-DPCH Information is present
	{ ID id-Additional-HS-Cell-Information-RL-Addition	CRITICALITY reject	EXTENSION Additional-HS-Cell-Information-RL-Addition-List	PRESENCE optional}|
	{ ID id-UE-AggregateMaximumBitRate					CRITICALITY ignore	EXTENSION UE-AggregateMaximumBitRate						PRESENCE optional}|
	{ ID id-Additional-EDCH-Cell-Information-RL-Add-Req	CRITICALITY reject	EXTENSION Additional-EDCH-Cell-Information-RL-Add-Req	PRESENCE optional}|
	{ ID id-Active-Pattern-Sequence-Information			CRITICALITY reject	EXTENSION Active-Pattern-Sequence-Information			PRESENCE optional}|
	{ ID id-UL-CLTD-Information							CRITICALITY reject	EXTENSION UL-CLTD-Information								PRESENCE optional}|
	{ ID id-E-DCH-Decoupling-Indication					CRITICALITY reject	EXTENSION E-DCH-Decoupling-Indication					PRESENCE optional}|
	{ ID id-Radio-Links-without-DPCH-FDPCH-Indication	CRITICALITY reject	EXTENSION Radio-Links-without-DPCH-FDPCH-Indication	PRESENCE optional}|
	{ ID id-UL-DPCCH2-Information						CRITICALITY reject	EXTENSION UL-DPCCH2-Information							PRESENCE optional}|
	{ ID id-Downlink-TPC-enhancements-Information		CRITICALITY reject	EXTENSION Downlink-TPC-enhancements-Information		PRESENCE optional},
	...
}

Additional-HS-Cell-Information-RL-Addition-List	::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Information-RL-Addition-ItemIEs

Additional-EDCH-Cell-Information-RL-Add-Req	::=SEQUENCE{
	setup-Or-Addition-Of-EDCH-On-secondary-UL-Frequency							Setup-Or-Addition-Of-EDCH-On-secondary-UL-Frequency,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-RL-Add-Req-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-Cell-Information-RL-Add-Req-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Setup-Or-Addition-Of-EDCH-On-secondary-UL-Frequency::= CHOICE {
	setup			Additional-EDCH-Setup-Info,
	addition		Additional-EDCH-Cell-Information-To-Add-List,
	...
}

Additional-HS-Cell-Information-RL-Addition-ItemIEs	::=SEQUENCE{
	hSPDSCH-RL-ID								RL-ID,
	c-ID										C-ID,
	hS-DSCH-FDD-Secondary-Serving-Information	HS-DSCH-FDD-Secondary-Serving-Information,
	iE-Extensions					ProtocolExtensionContainer { { Additional-HS-Cell-Information-RL-Addition-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-HS-Cell-Information-RL-Addition-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-InformationList-RL-AdditionRqstFDD	::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF ProtocolIE-Single-Container {{ RL-InformationItemIE-RL-AdditionRqstFDD}}

RL-InformationItemIE-RL-AdditionRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-InformationItem-RL-AdditionRqstFDD	CRITICALITY notify	TYPE RL-InformationItem-RL-AdditionRqstFDD			PRESENCE	mandatory}
}

RL-InformationItem-RL-AdditionRqstFDD ::= SEQUENCE {
	rL-ID										RL-ID,
	c-ID										C-ID,
	frameOffset									FrameOffset,
	chipOffset									ChipOffset,
	diversityControlField						DiversityControlField,
	dl-CodeInformation							FDD-DL-CodeInformation,
	initialDL-TransmissionPower					DL-Power						OPTIONAL,
	maximumDL-Power								DL-Power						OPTIONAL,
	minimumDL-Power								DL-Power						OPTIONAL,
	not-Used-sSDT-CellIdentity					NULL							OPTIONAL,
	transmitDiversityIndicator					TransmitDiversityIndicator		OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { RL-InformationItem-RL-AdditionRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

RL-InformationItem-RL-AdditionRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DLReferencePower					CRITICALITY ignore	EXTENSION DL-Power								PRESENCE optional}|
	{ ID id-RL-Specific-DCH-Info				CRITICALITY ignore	EXTENSION RL-Specific-DCH-Info				PRESENCE optional}|
	{ ID id-DelayedActivation					CRITICALITY reject	EXTENSION DelayedActivation						PRESENCE optional}|
	{ ID id-E-DCH-RL-Indication					CRITICALITY reject	EXTENSION E-DCH-RL-Indication					PRESENCE optional}|
	{ ID id-RL-Specific-E-DCH-Info				CRITICALITY ignore	EXTENSION RL-Specific-E-DCH-Info				PRESENCE optional}|
	{ ID id-SynchronisationIndicator			CRITICALITY ignore	EXTENSION SynchronisationIndicator			PRESENCE optional}|
	{ ID id-F-DPCH-SlotFormat					CRITICALITY reject	EXTENSION F-DPCH-SlotFormat						PRESENCE optional}|
	{ ID id-HSDSCH-PreconfigurationSetup		CRITICALITY ignore	EXTENSION HSDSCH-PreconfigurationSetup		PRESENCE optional}|
	{ ID id-Non-Serving-RL-Preconfig-Setup		CRITICALITY ignore	EXTENSION Non-Serving-RL-Preconfig-Setup	PRESENCE optional}|
	{ ID id-FTPICH-Information					CRITICALITY ignore	EXTENSION FTPICH-Information					PRESENCE optional}|
	{ ID id-TPC-slot-position					CRITICALITY ignore	EXTENSION TPC-slot-position						PRESENCE optional},
	...
}

E-DPCH-Information-RL-AdditionReqFDD ::= SEQUENCE {
	maxSet-E-DPDCHs								Max-Set-E-DPDCHs,
	ul-PunctureLimit							PunctureLimit,
	e-TFCS-Information							E-TFCS-Information,
	e-TTI										E-TTI,
	e-DPCCH-PO									E-DPCCH-PO,
	e-RGCH-2-IndexStepThreshold					E-RGCH-2-IndexStepThreshold,
	e-RGCH-3-IndexStepThreshold					E-RGCH-3-IndexStepThreshold,
	hARQ-Info-for-E-DCH							HARQ-Info-for-E-DCH,
	iE-Extensions								ProtocolExtensionContainer { { E-DPCH-Information-RL-AdditionReqFDD-ExtIEs} }		OPTIONAL,
	...
}

E-DPCH-Information-RL-AdditionReqFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-HSDSCH-Configured-Indicator		CRITICALITY	reject	EXTENSION	HSDSCH-Configured-Indicator		PRESENCE mandatory }|
	-- This shall be present for EDPCH configuration with HSDCH
	{ ID id-MinimumReducedE-DPDCH-GainFactor		CRITICALITY ignore	EXTENSION MinimumReducedE-DPDCH-GainFactor	PRESENCE optional },
	...
}


-- **************************************************************
--
-- RADIO LINK ADDITION REQUEST TDD
--
-- **************************************************************

RadioLinkAdditionRequestTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkAdditionRequestTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkAdditionRequestTDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkAdditionRequestTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-NodeB-CommunicationContextID					CRITICALITY reject	TYPE NodeB-CommunicationContextID						PRESENCE mandatory }|
	{ ID id-UL-CCTrCH-InformationList-RL-AdditionRqstTDD	CRITICALITY reject	TYPE UL-CCTrCH-InformationList-RL-AdditionRqstTDD	PRESENCE optional }|
	{ ID id-DL-CCTrCH-InformationList-RL-AdditionRqstTDD	CRITICALITY reject	TYPE DL-CCTrCH-InformationList-RL-AdditionRqstTDD	PRESENCE optional }|
	{ ID id-RL-Information-RL-AdditionRqstTDD				CRITICALITY reject	TYPE RL-Information-RL-AdditionRqstTDD					PRESENCE mandatory },
	...
}

RadioLinkAdditionRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-HSDSCH-TDD-Information			CRITICALITY reject	EXTENSION HSDSCH-TDD-Information							PRESENCE optional}|
	{ ID id-HSDSCH-RNTI						CRITICALITY reject	EXTENSION HSDSCH-RNTI										PRESENCE conditional}|
	-- The IE shall be present if HS-PDSCH RL ID IE is present.
	{ ID id-HSPDSCH-RL-ID					CRITICALITY reject	EXTENSION RL-ID												PRESENCE optional}|
	{ ID id-E-DCH-Information				CRITICALITY reject	EXTENSION E-DCH-Information									PRESENCE optional}|
	{ ID id-E-DCH-Serving-RL-ID				CRITICALITY reject	EXTENSION RL-ID												PRESENCE optional}|
	{ ID id-E-DCH-768-Information			CRITICALITY reject	EXTENSION E-DCH-768-Information								PRESENCE optional}|
	{ ID id-E-DCH-LCR-Information			CRITICALITY reject	EXTENSION E-DCH-LCR-Information								PRESENCE optional}|
	{ ID id-PowerControlGAP					CRITICALITY ignore	EXTENSION ControlGAP										PRESENCE optional}|
	 -- Applicable to 1.28Mcps TDD only
	{ ID id-ContinuousPacketConnectivity-DRX-InformationLCR		CRITICALITY reject	EXTENSION ContinuousPacketConnectivity-DRX-InformationLCR		PRESENCE optional}|
	{ ID id-HS-DSCH-Semi-PersistentScheduling-Information-LCR	CRITICALITY reject	EXTENSION HS-DSCH-Semi-PersistentScheduling-Information-LCR	PRESENCE optional}|
	{ ID id-E-DCH-Semi-PersistentScheduling-Information-LCR		CRITICALITY reject	EXTENSION E-DCH-Semi-PersistentScheduling-Information-LCR	PRESENCE optional}|
	{ ID id-IdleIntervalInformation			CRITICALITY ignore	EXTENSION IdleIntervalInformation							PRESENCE optional}|
	{ ID id-UE-Selected-MBMS-Service-Information	CRITICALITY ignore	EXTENSION UE-Selected-MBMS-Service-Information	PRESENCE optional}|
	{ ID id-HSSCCH-TPC-StepSize				CRITICALITY ignore	EXTENSION TDD-TPC-DownlinkStepSize						PRESENCE optional}|
	{ ID id-DCH-MeasurementOccasion-Information	CRITICALITY reject	EXTENSION DCH-MeasurementOccasion-Information	PRESENCE optional}|
	{ ID id-Multi-Carrier-EDCH-Setup		CRITICALITY reject	EXTENSION Multi-Carrier-EDCH-Info							PRESENCE optional}|
	{ ID id-MU-MIMO-InformationLCR			CRITICALITY ignore	EXTENSION MU-MIMO-InformationLCR							PRESENCE optional}|
	{ ID id-UE-Support-of-non-rectangular-resource-allocation	CRITICALITY ignore	EXTENSION UE-Support-of-non-rectangular-resource-allocation			PRESENCE optional},
	...
}

UL-CCTrCH-InformationList-RL-AdditionRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF UL-CCTrCH-InformationItem-RL-AdditionRqstTDD

UL-CCTrCH-InformationItem-RL-AdditionRqstTDD ::= SEQUENCE {
	cCTrCH-ID									CCTrCH-ID,
	uL-DPCH-Information							UL-DPCH-InformationList-RL-AdditionRqstTDD		OPTIONAL, -- Applicable to 3.84cps TDD only
	iE-Extensions								ProtocolExtensionContainer { { UL-CCTrCH-InformationItem-RL-AdditionRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-CCTrCH-InformationItem-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD	CRITICALITY notify	EXTENSION UL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD			PRESENCE	optional }|	-- Applicable to 1.28cps TDD only
	{ ID id-TDD-TPC-UplinkStepSize-LCR-RL-AdditionRqstTDD	CRITICALITY reject	EXTENSION TDD-TPC-UplinkStepSize-LCR	PRESENCE optional	}|-- Applicable to 1.28cps TDD only
	{ ID id-UL-DPCH-InformationItem-768-RL-AdditionRqstTDD	CRITICALITY notify	EXTENSION UL-DPCH-InformationItem-768-RL-AdditionRqstTDD			PRESENCE	optional },	-- Applicable to 7.68Mcps TDD only
	...
}

UL-DPCH-InformationList-RL-AdditionRqstTDD ::= ProtocolIE-Single-Container {{ UL-DPCH-InformationItemIE-RL-AdditionRqstTDD }}

UL-DPCH-InformationItemIE-RL-AdditionRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-UL-DPCH-InformationItem-RL-AdditionRqstTDD	CRITICALITY notify	TYPE UL-DPCH-InformationItem-RL-AdditionRqstTDD	PRESENCE optional }
	-- For 3.84Mcps TDD only
}

UL-DPCH-InformationItem-RL-AdditionRqstTDD ::= SEQUENCE {	
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	uL-Timeslot-Information					UL-Timeslot-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-InformationItem-RL-AdditionRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-InformationItem-RL-AdditionRqstTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	uL-TimeslotLCR-Information				UL-TimeslotLCR-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-DPCH-InformationItem-768-RL-AdditionRqstTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	uL-Timeslot768-Information				UL-Timeslot768-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-InformationItem-768-RL-AdditionRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-InformationItem-768-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-CCTrCH-InformationList-RL-AdditionRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL-CCTrCH-InformationItem-RL-AdditionRqstTDD

DL-CCTrCH-InformationItem-RL-AdditionRqstTDD ::= SEQUENCE {
	cCTrCH-ID						CCTrCH-ID,
	dL-DPCH-Information				DL-DPCH-InformationList-RL-AdditionRqstTDD		OPTIONAL, 	-- Applicable to 3.84Mcps TDD only
	iE-Extensions					ProtocolExtensionContainer { { DL-CCTrCH-InformationItem-RL-AdditionRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-CCTrCH-InformationItem-RL-AdditionRqstTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-DL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD	CRITICALITY notify		EXTENSION DL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD			PRESENCE	optional }|	-- Applicable to 1.28Mcps TDD only
	{ ID id-CCTrCH-Initial-DL-Power-RL-AdditionRqstTDD			CRITICALITY ignore		EXTENSION DL-Power				PRESENCE optional	}|
	{ ID id-TDD-TPC-DownlinkStepSize-RL-AdditionRqstTDD			CRITICALITY reject		EXTENSION TDD-TPC-DownlinkStepSize	PRESENCE optional	}|
	{ ID id-CCTrCH-Maximum-DL-Power-RL-AdditionRqstTDD			CRITICALITY ignore		EXTENSION DL-Power				PRESENCE optional	}|
	{ ID id-CCTrCH-Minimum-DL-Power-RL-AdditionRqstTDD			CRITICALITY ignore		EXTENSION DL-Power				PRESENCE optional	}|
	{ ID	id-DL-DPCH-InformationItem-768-RL-AdditionRqstTDD	CRITICALITY notify		EXTENSION DL-DPCH-InformationItem-768-RL-AdditionRqstTDD			PRESENCE	optional },	-- Applicable to 7.68Mcps TDD only
	...
}

DL-DPCH-InformationList-RL-AdditionRqstTDD ::= ProtocolIE-Single-Container {{ DL-DPCH-InformationItemIE-RL-AdditionRqstTDD }}

DL-DPCH-InformationItemIE-RL-AdditionRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-DL-DPCH-InformationItem-RL-AdditionRqstTDD	CRITICALITY notify	TYPE DL-DPCH-InformationItem-RL-AdditionRqstTDD		PRESENCE mandatory }
}

DL-DPCH-InformationItem-RL-AdditionRqstTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	dL-Timeslot-Information					DL-Timeslot-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-InformationItem-RL-AdditionRqstTDD-ExtIEs} }			OPTIONAL,
	...
}

DL-DPCH-InformationItem-RL-AdditionRqstTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	dL-TimeslotLCR-Information				DL-TimeslotLCR-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-DPCH-InformationItem-768-RL-AdditionRqstTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	dL-Timeslot768-Information				DL-Timeslot768-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-InformationItem-768-RL-AdditionRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-InformationItem-768-RL-AdditionRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-Information-RL-AdditionRqstTDD ::= SEQUENCE {
 	rL-ID										RL-ID,
 	c-ID										C-ID,
 	frameOffset									FrameOffset,
 	diversityControlField						DiversityControlField,
	initial-DL-Transmission-Power				DL-Power			OPTIONAL,
 	maximumDL-Power								DL-Power			OPTIONAL,
 	minimumDL-Power								DL-Power			OPTIONAL,
	dL-TimeSlotISCPInfo							DL-TimeslotISCPInfo	OPTIONAL, 	-- Applicable to 3.84Mcps TDD and 7.68Mcps TDD only
	iE-Extensions								ProtocolExtensionContainer { { RL-information-RL-AdditionRqstTDD-ExtIEs} }			OPTIONAL,
	...
 }

RL-information-RL-AdditionRqstTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TimeslotISCP-InformationList-LCR-RL-AdditionRqstTDD	CRITICALITY reject	EXTENSION DL-TimeslotISCPInfoLCR			PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-RL-Specific-DCH-Info								CRITICALITY ignore	EXTENSION RL-Specific-DCH-Info		PRESENCE 	optional	}|
	{ ID id-DelayedActivation 									CRITICALITY reject	EXTENSION DelayedActivation PRESENCE optional }|
	{ ID id-UL-Synchronisation-Parameters-LCR					CRITICALITY reject	EXTENSION UL-Synchronisation-Parameters-LCR		PRESENCE 	optional }|	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD
	{ ID id-UARFCNforNt											CRITICALITY reject	EXTENSION UARFCN		PRESENCE optional },
	  -- Mandatory for 1.28Mcps TDD when using multiple frequencies
	...
}

-- **************************************************************
--
-- RADIO LINK ADDITION RESPONSE FDD
--
-- **************************************************************

RadioLinkAdditionResponseFDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkAdditionResponseFDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkAdditionResponseFDD-Extensions}}			OPTIONAL,
	...
}

RadioLinkAdditionResponseFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID						CRITICALITY ignore	TYPE CRNC-CommunicationContextID						PRESENCE mandatory }|
	{ ID id-RL-InformationResponseList-RL-AdditionRspFDD	CRITICALITY ignore	TYPE RL-InformationResponseList-RL-AdditionRspFDD	PRESENCE mandatory }|
	{ ID id-CriticalityDiagnostics							CRITICALITY ignore	TYPE CriticalityDiagnostics						PRESENCE optional },
	...
}

RadioLinkAdditionResponseFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
{ ID id-HS-DSCH-Serving-Cell-Change-Info-Response		CRITICALITY ignore	EXTENSION HS-DSCH-Serving-Cell-Change-Info-Response					PRESENCE optional }|
{ ID id-E-DCH-Serving-Cell-Change-Info-Response			CRITICALITY ignore	EXTENSION E-DCH-Serving-Cell-Change-Info-Response					PRESENCE optional }|
{ ID id-MAChs-ResetIndicator							CRITICALITY ignore	EXTENSION MAChs-ResetIndicator									PRESENCE optional }|
{ ID id-Additional-HS-Cell-Change-Information-Response	CRITICALITY ignore	EXTENSION Additional-HS-Cell-Change-Information-Response-List	PRESENCE optional }|
{ ID id-Additional-EDCH-Cell-Information-Response-RL-Add	CRITICALITY ignore	EXTENSION Additional-EDCH-Cell-Information-Response-RL-Add-List	PRESENCE optional },
	...
}

Additional-HS-Cell-Change-Information-Response-List	::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Change-Information-Response-ItemIEs

Additional-HS-Cell-Change-Information-Response-ItemIEs	::=SEQUENCE{
	hSPDSCH-RL-ID												RL-ID,
	hS-DSCH-Secondary-Serving-Cell-Change-Information-Response	HS-DSCH-Secondary-Serving-Cell-Change-Information-Response,
	iE-Extensions					ProtocolExtensionContainer { { Additional-HS-Cell-Change-Information-Response-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-HS-Cell-Change-Information-Response-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-InformationResponseList-RL-AdditionRspFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF ProtocolIE-Single-Container {{ RL-InformationResponseItemIE-RL-AdditionRspFDD }}

RL-InformationResponseItemIE-RL-AdditionRspFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-InformationResponseItem-RL-AdditionRspFDD	CRITICALITY ignore	TYPE RL-InformationResponseItem-RL-AdditionRspFDD	PRESENCE mandatory }
}

RL-InformationResponseItem-RL-AdditionRspFDD ::= SEQUENCE {
	rL-ID								RL-ID,
	rL-Set-ID							RL-Set-ID,
	received-total-wide-band-power		Received-total-wide-band-power-Value,
	diversityIndication					DiversityIndication-RL-AdditionRspFDD,
	sSDT-SupportIndicator				SSDT-SupportIndicator,
	iE-Extensions						ProtocolExtensionContainer { { RL-InformationResponseItem-RL-AdditionRspFDD-ExtIEs} }		OPTIONAL,
	...
}

RL-InformationResponseItem-RL-AdditionRspFDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-PowerBalancing-ActivationIndicator		CRITICALITY ignore	EXTENSION DL-PowerBalancing-ActivationIndicator		PRESENCE optional }|
	{ ID id-E-DCH-RL-Set-ID								CRITICALITY ignore	EXTENSION RL-Set-ID												PRESENCE optional }|
	{ ID id-E-DCH-FDD-DL-Control-Channel-Information	CRITICALITY ignore	EXTENSION E-DCH-FDD-DL-Control-Channel-Information	PRESENCE optional }|
	{ ID id-Initial-DL-DPCH-TimingAdjustment			CRITICALITY ignore	EXTENSION DL-DPCH-TimingAdjustment						PRESENCE optional }|
	{ ID id-HSDSCH-PreconfigurationInfo					CRITICALITY ignore	EXTENSION HSDSCH-PreconfigurationInfo					PRESENCE optional }|
	{ ID id-Non-Serving-RL-Preconfig-Info				CRITICALITY ignore	EXTENSION Non-Serving-RL-Preconfig-Info					PRESENCE optional },
	...
}

DiversityIndication-RL-AdditionRspFDD ::= CHOICE {
	combining										Combining-RL-AdditionRspFDD,
	non-combining									Non-Combining-RL-AdditionRspFDD
}

Combining-RL-AdditionRspFDD ::= SEQUENCE {
	rL-ID											RL-ID,
	iE-Extensions									ProtocolExtensionContainer { { CombiningItem-RL-AdditionRspFDD-ExtIEs} }		OPTIONAL,
	...
}

CombiningItem-RL-AdditionRspFDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-FDD-Information-Response				CRITICALITY ignore	EXTENSION E-DCH-FDD-Information-Response				PRESENCE optional },
	...
}

Non-Combining-RL-AdditionRspFDD ::= SEQUENCE {
	dCH-InformationResponse						DCH-InformationResponse,
	iE-Extensions								ProtocolExtensionContainer { { Non-CombiningItem-RL-AdditionRspFDD-ExtIEs} }		OPTIONAL,
	...
}

Non-CombiningItem-RL-AdditionRspFDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-FDD-Information-Response				CRITICALITY ignore	EXTENSION E-DCH-FDD-Information-Response				PRESENCE optional },
	...
}

-- **************************************************************
--
-- RADIO LINK ADDITION RESPONSE TDD
--
-- **************************************************************

RadioLinkAdditionResponseTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkAdditionResponseTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkAdditionResponseTDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkAdditionResponseTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID					CRITICALITY ignore	TYPE CRNC-CommunicationContextID				PRESENCE mandatory	}|
	{ ID id-RL-InformationResponse-RL-AdditionRspTDD	CRITICALITY ignore	TYPE RL-InformationResponse-RL-AdditionRspTDD		PRESENCE optional	}|		-- Mandatory for 3.84Mcps TDD and 7.68Mcps TDD, Not Applicable to 1.28Mcps TDD
	{ ID id-CriticalityDiagnostics						CRITICALITY ignore	TYPE CriticalityDiagnostics				PRESENCE optional	},
	...
}

RadioLinkAdditionResponseTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-RL-InformationResponse-LCR-RL-AdditionRspTDD	CRITICALITY ignore	EXTENSION RL-InformationResponse-LCR-RL-AdditionRspTDD 	PRESENCE optional}|
	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD
	{ ID id-HSDSCH-TDD-Information-Response					CRITICALITY ignore	EXTENSION HSDSCH-TDD-Information-Response			PRESENCE optional}|
	{ ID id-E-DCH-Information-Response						CRITICALITY ignore	EXTENSION E-DCH-Information-Response				PRESENCE optional}|
	{ ID id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR	CRITICALITY ignore	EXTENSION ContinuousPacketConnectivity-DRX-Information-ResponseLCR	PRESENCE optional}|
	{ ID id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR	CRITICALITY ignore	EXTENSION HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR	PRESENCE optional}|
	{ ID id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR		CRITICALITY ignore	EXTENSION E-DCH-Semi-PersistentScheduling-Information-ResponseLCR	PRESENCE optional}|
	{ ID id-Multi-Carrier-EDCH-Response					CRITICALITY ignore	EXTENSION Multi-Carrier-EDCH-Information-Response	PRESENCE optional}|
	{ ID id-MU-MIMO-Information-Response				CRITICALITY reject	EXTENSION MU-MIMO-Information-Response					PRESENCE optional}|
	{ ID id-Non-rectangular-resource-allocation-indicator	CRITICALITY reject	EXTENSION Non-rectangular-resource-allocation-indicator				PRESENCE optional}|
	{ ID id-Non-rectangular-resource-timeslot-set		CRITICALITY reject	EXTENSION Non-rectangular-resource-timeslot-set		PRESENCE optional},
	...
}

RL-InformationResponse-RL-AdditionRspTDD ::= SEQUENCE {
	rL-ID										RL-ID,
	uL-TimeSlot-ISCP-Info						UL-TimeSlot-ISCP-Info,
	ul-PhysCH-SF-Variation						UL-PhysCH-SF-Variation,
	dCH-Information								DCH-Information-RL-AdditionRspTDD											OPTIONAL,
	dSCH-InformationResponseList				DSCH-InformationResponseList-RL-AdditionRspTDD								OPTIONAL,
	uSCH-InformationResponseList				USCH-InformationResponseList-RL-AdditionRspTDD								OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { RL-InformationResponse-RL-AdditionRspTDD-ExtIEs} }		OPTIONAL,
	...
}

RL-InformationResponse-RL-AdditionRspTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DCH-Information-RL-AdditionRspTDD ::= SEQUENCE {
	diversityIndication					DiversityIndication-RL-AdditionRspTDD,
	iE-Extensions						ProtocolExtensionContainer { { DCH-Information-RL-AdditionRspTDD-ExtIEs} } OPTIONAL,
	...
}

DCH-Information-RL-AdditionRspTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DiversityIndication-RL-AdditionRspTDD ::= CHOICE {
	combining									Combining-RL-AdditionRspTDD,	-- Indicates whether the old Transport Bearer shall be reused or not
	non-Combining								Non-Combining-RL-AdditionRspTDD
}

Combining-RL-AdditionRspTDD ::= SEQUENCE {
	rL-ID										RL-ID,	-- Reference RL
	iE-Extensions								ProtocolExtensionContainer { { CombiningItem-RL-AdditionRspTDD-ExtIEs} }		OPTIONAL,
	...
}

CombiningItem-RL-AdditionRspTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Non-Combining-RL-AdditionRspTDD ::= SEQUENCE {
	dCH-InformationResponse						DCH-InformationResponse,
	iE-Extensions								ProtocolExtensionContainer { { Non-CombiningItem-RL-AdditionRspTDD-ExtIEs} }			OPTIONAL,
	...
}

Non-CombiningItem-RL-AdditionRspTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DSCH-InformationResponseList-RL-AdditionRspTDD ::= ProtocolIE-Single-Container {{ DSCH-InformationResponseListIEs-RL-AdditionRspTDD }}

DSCH-InformationResponseListIEs-RL-AdditionRspTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-DSCH-InformationResponse   CRITICALITY ignore	TYPE DSCH-InformationResponse		PRESENCE mandatory }
}

USCH-InformationResponseList-RL-AdditionRspTDD ::= ProtocolIE-Single-Container {{ USCH-InformationResponseListIEs-RL-AdditionRspTDD }}

USCH-InformationResponseListIEs-RL-AdditionRspTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-USCH-InformationResponse   CRITICALITY ignore	TYPE USCH-InformationResponse		PRESENCE mandatory }
}

RL-InformationResponse-LCR-RL-AdditionRspTDD ::= SEQUENCE {
	rL-ID										RL-ID,
	uL-TimeSlot-ISCP-InfoLCR					UL-TimeSlot-ISCP-LCR-Info,
	ul-PhysCH-SF-Variation						UL-PhysCH-SF-Variation,
	dCH-Information								DCH-Information-RL-AdditionRspTDD	OPTIONAL,
	dSCH-InformationResponseList				DSCH-InformationResponseList-RL-AdditionRspTDD	OPTIONAL,
	uSCH-InformationResponseList				USCH-InformationResponseList-RL-AdditionRspTDD	OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { RL-InformationResponse-LCR-RL-AdditionRspTDD-ExtIEs} }	OPTIONAL,
	...
}

RL-InformationResponse-LCR-RL-AdditionRspTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK ADDITION FAILURE FDD
--
-- **************************************************************

RadioLinkAdditionFailureFDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkAdditionFailureFDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkAdditionFailureFDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkAdditionFailureFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID				CRITICALITY ignore		TYPE CRNC-CommunicationContextID					PRESENCE mandatory }|
	{ ID id-CauseLevel-RL-AdditionFailureFDD		CRITICALITY ignore		TYPE CauseLevel-RL-AdditionFailureFDD					PRESENCE mandatory }|
	{ ID id-CriticalityDiagnostics					CRITICALITY ignore		TYPE CriticalityDiagnostics					PRESENCE optional },
	...
}

RadioLinkAdditionFailureFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
{ ID id-HS-DSCH-Serving-Cell-Change-Info-Response		CRITICALITY ignore	EXTENSION HS-DSCH-Serving-Cell-Change-Info-Response					PRESENCE optional }|
{ ID id-E-DCH-Serving-Cell-Change-Info-Response			CRITICALITY ignore	EXTENSION E-DCH-Serving-Cell-Change-Info-Response					PRESENCE optional }|
{ ID id-Additional-HS-Cell-Change-Information-Response	CRITICALITY ignore	EXTENSION Additional-HS-Cell-Change-Information-Response-List	PRESENCE optional }|
{ ID id-MAChs-ResetIndicator							CRITICALITY ignore	EXTENSION MAChs-ResetIndicator									PRESENCE optional }|
{ ID id-Additional-EDCH-Cell-Information-Response-RL-Add	CRITICALITY ignore	EXTENSION Additional-EDCH-Cell-Information-Response-RL-Add-List	PRESENCE optional },
	...
}

CauseLevel-RL-AdditionFailureFDD ::= CHOICE {
	generalCause		GeneralCauseList-RL-AdditionFailureFDD,
	rLSpecificCause		RLSpecificCauseList-RL-AdditionFailureFDD,
	...
}

GeneralCauseList-RL-AdditionFailureFDD ::= SEQUENCE {
	cause										Cause,
	iE-Extensions								ProtocolExtensionContainer { { GeneralCauseItem-RL-AdditionFailureFDD-ExtIEs} }			OPTIONAL,
	...
}

GeneralCauseItem-RL-AdditionFailureFDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RLSpecificCauseList-RL-AdditionFailureFDD ::= SEQUENCE {
	unsuccessful-RL-InformationRespList-RL-AdditionFailureFDD		Unsuccessful-RL-InformationRespList-RL-AdditionFailureFDD,
	successful-RL-InformationRespList-RL-AdditionFailureFDD			Successful-RL-InformationRespList-RL-AdditionFailureFDD					OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { RLSpecificCauseItem-RL-AdditionFailureFDD-ExtIEs} }			OPTIONAL,
	...
}

RLSpecificCauseItem-RL-AdditionFailureFDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Unsuccessful-RL-InformationRespList-RL-AdditionFailureFDD ::= SEQUENCE	(SIZE (1..maxNrOfRLs-1)) OF ProtocolIE-Single-Container {{ Unsuccessful-RL-InformationRespItemIE-RL-AdditionFailureFDD }}

Unsuccessful-RL-InformationRespItemIE-RL-AdditionFailureFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-Unsuccessful-RL-InformationRespItem-RL-AdditionFailureFDD	CRITICALITY ignore	TYPE Unsuccessful-RL-InformationRespItem-RL-AdditionFailureFDD	PRESENCE mandatory }
}

Unsuccessful-RL-InformationRespItem-RL-AdditionFailureFDD ::= SEQUENCE {
	rL-ID						RL-ID,
	cause						Cause,
	iE-Extensions				ProtocolExtensionContainer { { Unsuccessful-RL-InformationRespItem-RL-AdditionFailureFDD-ExtIEs} }			OPTIONAL,
	...
}

Unsuccessful-RL-InformationRespItem-RL-AdditionFailureFDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Successful-RL-InformationRespList-RL-AdditionFailureFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-2)) OF ProtocolIE-Single-Container {{ Successful-RL-InformationRespItemIE-RL-AdditionFailureFDD }}

Successful-RL-InformationRespItemIE-RL-AdditionFailureFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-Successful-RL-InformationRespItem-RL-AdditionFailureFDD	CRITICALITY ignore	TYPE Successful-RL-InformationRespItem-RL-AdditionFailureFDD	PRESENCE mandatory }
}

Successful-RL-InformationRespItem-RL-AdditionFailureFDD ::= SEQUENCE {
	rL-ID										RL-ID,
	rL-Set-ID									RL-Set-ID,
	received-total-wide-band-power				Received-total-wide-band-power-Value,
	diversityIndication							DiversityIndication-RL-AdditionFailureFDD,
	sSDT-SupportIndicator						SSDT-SupportIndicator,
	iE-Extensions								ProtocolExtensionContainer { { Successful-RL-InformationRespItem-RL-AdditionFailureFDD-ExtIEs} }		OPTIONAL,
	...
}

Successful-RL-InformationRespItem-RL-AdditionFailureFDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-PowerBalancing-ActivationIndicator		CRITICALITY ignore	EXTENSION DL-PowerBalancing-ActivationIndicator		PRESENCE optional }|
	{ ID id-E-DCH-RL-Set-ID								CRITICALITY ignore	EXTENSION RL-Set-ID												PRESENCE optional }|
	{ ID id-E-DCH-FDD-DL-Control-Channel-Information	CRITICALITY ignore	EXTENSION E-DCH-FDD-DL-Control-Channel-Information	PRESENCE optional }|
	{ ID id-Initial-DL-DPCH-TimingAdjustment			CRITICALITY ignore	EXTENSION DL-DPCH-TimingAdjustment						PRESENCE optional }|
	{ ID id-HSDSCH-PreconfigurationInfo					CRITICALITY ignore	EXTENSION HSDSCH-PreconfigurationInfo					PRESENCE optional }|
	{ ID id-Non-Serving-RL-Preconfig-Info				CRITICALITY ignore	EXTENSION Non-Serving-RL-Preconfig-Info					PRESENCE optional },
	...
}

DiversityIndication-RL-AdditionFailureFDD ::= CHOICE {
 	combining						Combining-RL-AdditionFailureFDD,
 	non-Combining					Non-Combining-RL-AdditionFailureFDD
}

Combining-RL-AdditionFailureFDD ::= SEQUENCE {
	rL-ID										RL-ID,
	iE-Extensions								ProtocolExtensionContainer { { CombiningItem-RL-AdditionFailureFDD-ExtIEs} }			OPTIONAL,
	...
 }

CombiningItem-RL-AdditionFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-FDD-Information-Response				CRITICALITY ignore	EXTENSION E-DCH-FDD-Information-Response				PRESENCE optional },
	...
}

Non-Combining-RL-AdditionFailureFDD ::= SEQUENCE {
	dCH-InformationResponse						DCH-InformationResponse,
	iE-Extensions								ProtocolExtensionContainer { { Non-CombiningItem-RL-AdditionFailureFDD-ExtIEs} }			OPTIONAL,
	...
}

Non-CombiningItem-RL-AdditionFailureFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-FDD-Information-Response				CRITICALITY ignore	EXTENSION E-DCH-FDD-Information-Response				PRESENCE optional },
	...
}

-- **************************************************************
--
-- RADIO LINK ADDITION FAILURE TDD
--
-- **************************************************************

RadioLinkAdditionFailureTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkAdditionFailureTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkAdditionFailureTDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkAdditionFailureTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CRNC-CommunicationContextID				CRITICALITY ignore		TYPE CRNC-CommunicationContextID			PRESENCE mandatory }|
	{ ID    id-CauseLevel-RL-AdditionFailureTDD			CRITICALITY ignore		TYPE CauseLevel-RL-AdditionFailureTDD		PRESENCE mandatory }|
	{ ID	id-CriticalityDiagnostics					CRITICALITY ignore		TYPE CriticalityDiagnostics			PRESENCE optional },
	...
}

RadioLinkAdditionFailureTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CauseLevel-RL-AdditionFailureTDD ::= CHOICE {
	generalCause		GeneralCauseList-RL-AdditionFailureTDD,
	rLSpecificCause		RLSpecificCauseList-RL-AdditionFailureTDD,
	...
}

GeneralCauseList-RL-AdditionFailureTDD ::= SEQUENCE {
	cause						Cause,
	iE-Extensions				ProtocolExtensionContainer { { GeneralCauseItem-RL-AdditionFailureTDD-ExtIEs} }		OPTIONAL,
	...
}

GeneralCauseItem-RL-AdditionFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RLSpecificCauseList-RL-AdditionFailureTDD ::= SEQUENCE {
	unsuccessful-RL-InformationRespItem-RL-AdditionFailureTDD	Unsuccessful-RL-InformationRespItem-RL-AdditionFailureTDD,
	iE-Extensions												ProtocolExtensionContainer { { RLSpecificCauseItem-RL-AdditionFailureTDD-ExtIEs} }		OPTIONAL,
	...
}

RLSpecificCauseItem-RL-AdditionFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Unsuccessful-RL-InformationRespItem-RL-AdditionFailureTDD ::= ProtocolIE-Single-Container { {Unsuccessful-RL-InformationRespItemIE-RL-AdditionFailureTDD} }

Unsuccessful-RL-InformationRespItemIE-RL-AdditionFailureTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-Unsuccessful-RL-InformationResp-RL-AdditionFailureTDD	CRITICALITY ignore	TYPE Unsuccessful-RL-InformationResp-RL-AdditionFailureTDD	PRESENCE mandatory }
}

Unsuccessful-RL-InformationResp-RL-AdditionFailureTDD ::= SEQUENCE {
	rL-ID							RL-ID,
	cause							Cause,
	iE-Extensions					ProtocolExtensionContainer { { Unsuccessful-RL-InformationResp-RL-AdditionFailureTDD-ExtIEs} }		OPTIONAL,
	...
}

Unsuccessful-RL-InformationResp-RL-AdditionFailureTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK RECONFIGURATION PREPARE FDD
--
-- **************************************************************

RadioLinkReconfigurationPrepareFDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkReconfigurationPrepareFDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkReconfigurationPrepareFDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkReconfigurationPrepareFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-NodeB-CommunicationContextID					CRITICALITY reject	TYPE NodeB-CommunicationContextID							PRESENCE mandatory }|
	{ ID id-UL-DPCH-Information-RL-ReconfPrepFDD			CRITICALITY reject	TYPE UL-DPCH-Information-RL-ReconfPrepFDD					PRESENCE optional }|
	{ ID id-DL-DPCH-Information-RL-ReconfPrepFDD			CRITICALITY reject	TYPE DL-DPCH-Information-RL-ReconfPrepFDD					PRESENCE optional }|
	{ ID id-FDD-DCHs-to-Modify								CRITICALITY reject	TYPE FDD-DCHs-to-Modify							PRESENCE optional }|
	{ ID id-DCHs-to-Add-FDD									CRITICALITY reject	TYPE DCH-FDD-Information							PRESENCE optional }|
	{ ID id-DCH-DeleteList-RL-ReconfPrepFDD					CRITICALITY reject	TYPE DCH-DeleteList-RL-ReconfPrepFDD						PRESENCE optional }|
	{ ID id-RL-InformationList-RL-ReconfPrepFDD				CRITICALITY reject	TYPE RL-InformationList-RL-ReconfPrepFDD					PRESENCE optional }|
	{ ID id-Transmission-Gap-Pattern-Sequence-Information	CRITICALITY reject	TYPE Transmission-Gap-Pattern-Sequence-Information		PRESENCE optional },
	...
}

RadioLinkReconfigurationPrepareFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-SignallingBearerRequestIndicator		CRITICALITY reject	EXTENSION SignallingBearerRequestIndicator		PRESENCE optional}|
	{ ID id-HSDSCH-FDD-Information					CRITICALITY reject	EXTENSION HSDSCH-FDD-Information					PRESENCE optional}|
	{ ID id-HSDSCH-Information-to-Modify			CRITICALITY reject	EXTENSION HSDSCH-Information-to-Modify			PRESENCE optional}|
	{ ID id-HSDSCH-MACdFlows-to-Add					CRITICALITY reject	EXTENSION HSDSCH-MACdFlows-Information			PRESENCE optional}|
	{ ID id-HSDSCH-MACdFlows-to-Delete				CRITICALITY reject	EXTENSION HSDSCH-MACdFlows-to-Delete				PRESENCE optional}|
	{ ID id-HSDSCH-RNTI								CRITICALITY reject	EXTENSION HSDSCH-RNTI									PRESENCE conditional}|
	-- The IE shall be present if HS-PDSCH RL ID IE is present.
	{ ID id-HSPDSCH-RL-ID							CRITICALITY reject	EXTENSION RL-ID											PRESENCE optional}|
	{ ID id-E-DPCH-Information-RL-ReconfPrepFDD		CRITICALITY reject	EXTENSION E-DPCH-Information-RL-ReconfPrepFDD	PRESENCE optional}|
	{ ID id-E-DCH-FDD-Information					CRITICALITY reject	EXTENSION E-DCH-FDD-Information						PRESENCE optional}|
	{ ID id-E-DCH-FDD-Information-to-Modify			CRITICALITY reject	EXTENSION E-DCH-FDD-Information-to-Modify		PRESENCE optional}|
	{ ID id-E-DCH-MACdFlows-to-Add					CRITICALITY reject	EXTENSION E-DCH-MACdFlows-Information				PRESENCE optional}|
	{ ID id-E-DCH-MACdFlows-to-Delete				CRITICALITY reject	EXTENSION E-DCH-MACdFlows-to-Delete				PRESENCE optional}|
	{ ID id-Serving-E-DCH-RL-ID						CRITICALITY reject	EXTENSION Serving-E-DCH-RL-ID						PRESENCE optional}|
	{ ID id-F-DPCH-Information-RL-ReconfPrepFDD		CRITICALITY reject	EXTENSION F-DPCH-Information-RL-ReconfPrepFDD	PRESENCE optional}|
	{ ID id-Fast-Reconfiguration-Mode				CRITICALITY ignore	EXTENSION Fast-Reconfiguration-Mode				PRESENCE optional}|
	{ ID id-CPC-Information							CRITICALITY reject	EXTENSION CPC-Information								PRESENCE optional}|
	{ ID id-Additional-HS-Cell-Information-RL-Reconf-Prep	CRITICALITY reject	EXTENSION Additional-HS-Cell-Information-RL-Reconf-Prep	PRESENCE optional}|
	{ ID id-UE-AggregateMaximumBitRate				CRITICALITY ignore	EXTENSION UE-AggregateMaximumBitRate				PRESENCE optional}|
	{ ID id-Additional-EDCH-Cell-Information-RL-Reconf-Prep	CRITICALITY reject	EXTENSION Additional-EDCH-Cell-Information-RL-Reconf-Prep	PRESENCE optional}|
	{ ID id-UL-CLTD-Information-Reconf				CRITICALITY reject	EXTENSION UL-CLTD-Information-Reconf				PRESENCE optional}|
	{ ID id-E-DCH-Decoupling-Indication				CRITICALITY reject	EXTENSION E-DCH-Decoupling-Indication				PRESENCE optional}|
	{ ID id-DCH-ENH-Information-Reconf				CRITICALITY reject EXTENSION DCH-ENH-Information-Reconf				PRESENCE optional}|
	{ ID id-Radio-Links-without-DPCH-FDPCH-Indication	CRITICALITY reject	EXTENSION Radio-Links-without-DPCH-FDPCH-Indication		PRESENCE optional}|
	{ ID id-UL-DPCCH2-Information-Reconf			CRITICALITY reject	EXTENSION UL-DPCCH2-Information-Reconf			PRESENCE optional}|
	{ ID id-Downlink-TPC-enhancements-Reconf		CRITICALITY reject	EXTENSION Downlink-TPC-enhancements-Reconf		PRESENCE optional}|
	{ ID id-Improved-Synchronized-Indicator			CRITICALITY ignore	EXTENSION Improved-Synchronized-Indicator		PRESENCE optional},
	...
}

Additional-HS-Cell-Information-RL-Reconf-Prep	::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Information-RL-Reconf-Prep-ItemIEs

Additional-HS-Cell-Information-RL-Reconf-Prep-ItemIEs	::=SEQUENCE{
	hSPDSCH-RL-ID									RL-ID,
	c-ID											C-ID												OPTIONAL,
	hS-DSCH-FDD-Secondary-Serving-Information		HS-DSCH-FDD-Secondary-Serving-Information			OPTIONAL,
	hS-DSCH-Secondary-Serving-Information-To-Modify	HS-DSCH-Secondary-Serving-Information-To-Modify	OPTIONAL,
	hS-HS-DSCH-Secondary-Serving-Remove				HS-DSCH-Secondary-Serving-Remove					OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { Additional-HS-Cell-Information-RL-Reconf-Prep-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-HS-Cell-Information-RL-Reconf-Prep-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {

	...
}

Additional-EDCH-Cell-Information-RL-Reconf-Prep	::=SEQUENCE{
	setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency							Setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-RL-Reconf-Prep-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-Cell-Information-RL-Reconf-Prep-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}


UL-DPCH-Information-RL-ReconfPrepFDD ::= SEQUENCE {
	ul-ScramblingCode								UL-ScramblingCode					OPTIONAL,
	ul-SIR-Target									UL-SIR								OPTIONAL,
	minUL-ChannelisationCodeLength					MinUL-ChannelisationCodeLength		OPTIONAL,
	maxNrOfUL-DPDCHs								MaxNrOfUL-DPDCHs					OPTIONAL,
	-- This IE shall be present if minUL-ChannelisationCodeLength Ie is set to 4 
	ul-PunctureLimit								PunctureLimit						OPTIONAL,
	tFCS											TFCS								OPTIONAL,
	ul-DPCCH-SlotFormat								UL-DPCCH-SlotFormat					OPTIONAL,
	diversityMode									DiversityMode						OPTIONAL,
	not-Used-sSDT-CellIDLength						NULL								OPTIONAL,
	not-Used-s-FieldLength							NULL								OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { UL-DPCH-Information-RL-ReconfPrepFDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-Information-RL-ReconfPrepFDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UL-DPDCH-Indicator-For-E-DCH-Operation	CRITICALITY reject	EXTENSION UL-DPDCH-Indicator-For-E-DCH-Operation			PRESENCE optional },
	...
}

DL-DPCH-Information-RL-ReconfPrepFDD ::= SEQUENCE {
	tFCS											TFCS								OPTIONAL,
	dl-DPCH-SlotFormat								DL-DPCH-SlotFormat					OPTIONAL,
	tFCI-SignallingMode								TFCI-SignallingMode					OPTIONAL,
	tFCI-Presence									TFCI-Presence						OPTIONAL,
	-- This IE shall be present if the DL DPCH Slot Format IE is set to any of the values from 12 to 16
	multiplexingPosition							MultiplexingPosition 				OPTIONAL,
	not-Used-pDSCH-CodeMapping						NULL								OPTIONAL,
	not-Used-pDSCH-RL-ID							NULL								OPTIONAL,
	limitedPowerIncrease							LimitedPowerIncrease				OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { DL-DPCH-Information-RL-ReconfPrepFDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-Information-RL-ReconfPrepFDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-DPCH-Power-Information-RL-ReconfPrepFDD	CRITICALITY reject	EXTENSION DL-DPCH-Power-Information-RL-ReconfPrepFDD	PRESENCE optional },
	...
}

DL-DPCH-Power-Information-RL-ReconfPrepFDD ::= SEQUENCE {
	powerOffsetInformation					PowerOffsetInformation-RL-ReconfPrepFDD,
	fdd-TPC-DownlinkStepSize				FDD-TPC-DownlinkStepSize,
	innerLoopDLPCStatus						InnerLoopDLPCStatus,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-Power-Information-RL-ReconfPrepFDD-ExtIEs } }			OPTIONAL,
	...
}

DL-DPCH-Power-Information-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PowerOffsetInformation-RL-ReconfPrepFDD ::= SEQUENCE {
	pO1-ForTFCI-Bits						PowerOffset,
	pO2-ForTPC-Bits							PowerOffset,
	pO3-ForPilotBits						PowerOffset,
	iE-Extensions							ProtocolExtensionContainer { { PowerOffsetInformation-RL-ReconfPrepFDD-ExtIEs} }		OPTIONAL,
	...
}

PowerOffsetInformation-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DCH-DeleteList-RL-ReconfPrepFDD ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-DeleteItem-RL-ReconfPrepFDD

DCH-DeleteItem-RL-ReconfPrepFDD ::= SEQUENCE {
	dCH-ID											DCH-ID,
	iE-Extensions									ProtocolExtensionContainer { { DCH-DeleteItem-RL-ReconfPrepFDD-ExtIEs} }		OPTIONAL,
	...
}

DCH-DeleteItem-RL-ReconfPrepFDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-InformationList-RL-ReconfPrepFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container {{ RL-InformationItemIE-RL-ReconfPrepFDD }}

RL-InformationItemIE-RL-ReconfPrepFDD NBAP-PROTOCOL-IES ::= {
	{ ID	id-RL-InformationItem-RL-ReconfPrepFDD			CRITICALITY		reject			TYPE 	RL-InformationItem-RL-ReconfPrepFDD		PRESENCE	mandatory}
}

RL-InformationItem-RL-ReconfPrepFDD ::= SEQUENCE {
	rL-ID											RL-ID,
	dl-CodeInformation								FDD-DL-CodeInformation						OPTIONAL,
	maxDL-Power										DL-Power									OPTIONAL,
	minDL-Power										DL-Power									OPTIONAL,
	not-Used-sSDT-Indication						NULL										OPTIONAL,
	not-Used-sSDT-Cell-Identity						NULL										OPTIONAL,
	transmitDiversityIndicator						TransmitDiversityIndicator					OPTIONAL,
	-- This IE shall be present if Diversity Mode IE is present in UL DPCH Information IE and it is not set to “none”
	iE-Extensions									ProtocolExtensionContainer { { RL-InformationItem-RL-ReconfPrepFDD-ExtIEs} }		OPTIONAL,
	...
}

RL-InformationItem-RL-ReconfPrepFDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DLReferencePower						CRITICALITY ignore	EXTENSION DL-Power										PRESENCE optional}|
	{ ID id-RL-Specific-DCH-Info					CRITICALITY ignore	EXTENSION RL-Specific-DCH-Info						PRESENCE optional}|
	{ ID id-DL-DPCH-TimingAdjustment				CRITICALITY reject	EXTENSION DL-DPCH-TimingAdjustment					PRESENCE optional}|
	{ ID id-Primary-CPICH-Usage-for-Channel-Estimation	CRITICALITY ignore	EXTENSION Primary-CPICH-Usage-for-Channel-Estimation	PRESENCE optional}|
	{ ID id-Secondary-CPICH-Information-Change		CRITICALITY ignore	EXTENSION Secondary-CPICH-Information-Change	PRESENCE optional}|
	{ ID id-E-DCH-RL-Indication						CRITICALITY reject	EXTENSION E-DCH-RL-Indication						PRESENCE optional}|
	{ ID id-RL-Specific-E-DCH-Info					CRITICALITY ignore	EXTENSION RL-Specific-E-DCH-Info					PRESENCE optional}|
	{ ID id-F-DPCH-SlotFormat						CRITICALITY reject	EXTENSION F-DPCH-SlotFormat							PRESENCE optional}|
	{ ID id-HSDSCH-PreconfigurationSetup			CRITICALITY ignore	EXTENSION HSDSCH-PreconfigurationSetup			PRESENCE optional}|
	{ ID id-Non-Serving-RL-Preconfig-Setup			CRITICALITY ignore	EXTENSION Non-Serving-RL-Preconfig-Setup			PRESENCE optional}|
	{ ID id-Non-Serving-RL-Preconfig-Removal		CRITICALITY ignore	EXTENSION Non-Serving-RL-Preconfig-Setup			PRESENCE optional}|
	{ ID id-FTPICH-Information-Reconf				CRITICALITY ignore	EXTENSION FTPICH-Information-Reconf				PRESENCE optional}|
	{ ID id-TPC-slot-position						CRITICALITY ignore	EXTENSION TPC-slot-position							PRESENCE optional},
	...
}

E-DPCH-Information-RL-ReconfPrepFDD ::= SEQUENCE {
	maxSet-E-DPDCHs								Max-Set-E-DPDCHs													OPTIONAL,
	ul-PunctureLimit							PunctureLimit														OPTIONAL,
	e-TFCS-Information							E-TFCS-Information													OPTIONAL,
	e-TTI										E-TTI																OPTIONAL,
	e-DPCCH-PO									E-DPCCH-PO															OPTIONAL,
	e-RGCH-2-IndexStepThreshold					E-RGCH-2-IndexStepThreshold											OPTIONAL,
	e-RGCH-3-IndexStepThreshold					E-RGCH-3-IndexStepThreshold																	OPTIONAL,
	hARQ-Info-for-E-DCH							HARQ-Info-for-E-DCH																			OPTIONAL,
	hSDSCH-Configured-Indicator					HSDSCH-Configured-Indicator																	OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { E-DPCH-Information-RL-ReconfPrepFDD-ExtIEs} }		OPTIONAL,
	...
}

E-DPCH-Information-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MinimumReducedE-DPDCH-GainFactor		CRITICALITY ignore	EXTENSION MinimumReducedE-DPDCH-GainFactor	PRESENCE optional },
	...
}

F-DPCH-Information-RL-ReconfPrepFDD ::= SEQUENCE {
	powerOffsetInformation				PowerOffsetInformation-F-DPCH-RL-ReconfPrepFDD,
	fdd-TPC-DownlinkStepSize			FDD-TPC-DownlinkStepSize,
	limitedPowerIncrease				LimitedPowerIncrease,
	innerLoopDLPCStatus					InnerLoopDLPCStatus,
	iE-Extensions						ProtocolExtensionContainer { { F-DPCH-Information-RL-ReconfPrepFDD-ExtIEs} }					OPTIONAL,
	...
}

F-DPCH-Information-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PowerOffsetInformation-F-DPCH-RL-ReconfPrepFDD ::= SEQUENCE {
	pO2-ForTPC-Bits						PowerOffset,
	-- This IE shall be ignored by Node B
	iE-Extensions						ProtocolExtensionContainer { { PowerOffsetInformation-F-DPCH-RL-ReconfPrepFDD-ExtIEs} }		OPTIONAL,
	...
}

PowerOffsetInformation-F-DPCH-RL-ReconfPrepFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK RECONFIGURATION PREPARE TDD
--
-- **************************************************************

RadioLinkReconfigurationPrepareTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkReconfigurationPrepareTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkReconfigurationPrepareTDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkReconfigurationPrepareTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-NodeB-CommunicationContextID						CRITICALITY reject	TYPE NodeB-CommunicationContextID				PRESENCE mandatory }|
	{ ID id-UL-CCTrCH-InformationAddList-RL-ReconfPrepTDD		CRITICALITY reject	TYPE UL-CCTrCH-InformationAddList-RL-ReconfPrepTDD			PRESENCE optional }|
	{ ID id-UL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD	CRITICALITY reject	TYPE UL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD			PRESENCE optional }|
	{ ID id-UL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD	CRITICALITY reject	TYPE UL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD			PRESENCE optional }|
	{ ID id-DL-CCTrCH-InformationAddList-RL-ReconfPrepTDD		CRITICALITY reject	TYPE DL-CCTrCH-InformationAddList-RL-ReconfPrepTDD			PRESENCE optional }|
	{ ID id-DL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD	CRITICALITY reject	TYPE DL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD			PRESENCE optional }|
	{ ID id-DL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD	CRITICALITY reject	TYPE DL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD			PRESENCE optional }|
	{ ID id-TDD-DCHs-to-Modify									CRITICALITY reject	TYPE TDD-DCHs-to-Modify					PRESENCE optional }|
	{ ID id-DCHs-to-Add-TDD										CRITICALITY reject	TYPE DCH-TDD-Information					PRESENCE optional }|
	{ ID id-DCH-DeleteList-RL-ReconfPrepTDD						CRITICALITY reject	TYPE DCH-DeleteList-RL-ReconfPrepTDD			PRESENCE optional }|
	{ ID id-DSCH-Information-ModifyList-RL-ReconfPrepTDD		CRITICALITY reject	TYPE DSCH-Information-ModifyList-RL-ReconfPrepTDD				PRESENCE optional }|
	{ ID id-DSCHs-to-Add-TDD									CRITICALITY reject	TYPE DSCH-TDD-Information					PRESENCE optional }|
	{ ID id-DSCH-Information-DeleteList-RL-ReconfPrepTDD		CRITICALITY reject	TYPE DSCH-Information-DeleteList-RL-ReconfPrepTDD				PRESENCE optional }|
	{ ID id-USCH-Information-ModifyList-RL-ReconfPrepTDD		CRITICALITY reject	TYPE USCH-Information-ModifyList-RL-ReconfPrepTDD				PRESENCE optional }|
	{ ID id-USCH-Information-Add								CRITICALITY reject	TYPE USCH-Information					PRESENCE optional }|
	{ ID id-USCH-Information-DeleteList-RL-ReconfPrepTDD		CRITICALITY reject	TYPE USCH-Information-DeleteList-RL-ReconfPrepTDD				PRESENCE optional }|
	{ ID id-RL-Information-RL-ReconfPrepTDD						CRITICALITY reject	TYPE RL-Information-RL-ReconfPrepTDD			PRESENCE optional },
-- This RL Information is the for the 1st RL IE repetition
	...
}

RadioLinkReconfigurationPrepareTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-SignallingBearerRequestIndicator		CRITICALITY reject	EXTENSION SignallingBearerRequestIndicator		PRESENCE optional }|
	{ ID id-HSDSCH-TDD-Information					CRITICALITY reject	EXTENSION HSDSCH-TDD-Information					PRESENCE optional }|
	{ ID id-HSDSCH-Information-to-Modify			CRITICALITY reject	EXTENSION HSDSCH-Information-to-Modify			PRESENCE optional }|
	{ ID id-HSDSCH-MACdFlows-to-Add					CRITICALITY reject	EXTENSION HSDSCH-MACdFlows-Information			PRESENCE optional }|
	{ ID id-HSDSCH-MACdFlows-to-Delete				CRITICALITY reject	EXTENSION HSDSCH-MACdFlows-to-Delete				PRESENCE optional }|
	{ ID id-HSDSCH-RNTI								CRITICALITY reject	EXTENSION HSDSCH-RNTI									PRESENCE conditional }|
	-- The IE shall be present if HS-PDSCH RL ID IE is present.
	{ ID id-HSPDSCH-RL-ID							CRITICALITY reject	EXTENSION RL-ID											PRESENCE optional }|
	{ ID id-PDSCH-RL-ID								CRITICALITY ignore	EXTENSION RL-ID											PRESENCE optional }|
	{ ID id-multiple-RL-Information-RL-ReconfPrepTDD	CRITICALITY reject	EXTENSION MultipleRL-Information-RL-ReconfPrepTDD	PRESENCE optional }|
-- This RL Information is the for the 2nd and beyond repetition of RL information,
	{ ID id-E-DCH-Information-Reconfig				CRITICALITY reject	EXTENSION E-DCH-Information-Reconfig				PRESENCE optional }|
	{ ID id-E-DCH-Serving-RL-ID						CRITICALITY reject	EXTENSION RL-ID											PRESENCE optional }|
	{ ID id-E-DCH-768-Information-Reconfig			CRITICALITY reject	EXTENSION E-DCH-768-Information-Reconfig			PRESENCE optional }|
	{ ID id-E-DCH-LCR-Information-Reconfig			CRITICALITY reject	EXTENSION E-DCH-LCR-Information-Reconfig			PRESENCE optional }|
	{ ID id-PowerControlGAP							CRITICALITY ignore	EXTENSION ControlGAP									PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-CPC-InformationLCR						CRITICALITY reject	EXTENSION CPC-InformationLCR							PRESENCE optional }|
	{ ID id-IdleIntervalInformation					CRITICALITY ignore	EXTENSION IdleIntervalInformation					PRESENCE optional }|
	{ ID id-UE-Selected-MBMS-Service-Information	CRITICALITY ignore	EXTENSION UE-Selected-MBMS-Service-Information	PRESENCE optional }|
	{ ID id-HSSCCH-TPC-StepSize						CRITICALITY ignore	EXTENSION TDD-TPC-DownlinkStepSize					PRESENCE optional }|
	{ ID id-DCH-MeasurementOccasion-Information		CRITICALITY reject	EXTENSION DCH-MeasurementOccasion-Information	PRESENCE optional }|
	{ ID id-HSDSCH-RNTI-For-FACH					CRITICALITY ignore	EXTENSION HSDSCH-RNTI									PRESENCE optional }|
	{ ID id-Multi-Carrier-EDCH-Reconfigure			CRITICALITY reject	EXTENSION Multi-Carrier-EDCH-Reconfigure			PRESENCE optional }|
	{ ID id-MU-MIMO-InformationLCR					CRITICALITY ignore	EXTENSION MU-MIMO-InformationLCR					PRESENCE optional }|
	{ ID id-MU-MIMO-Information-To-ReconfigureLCR	CRITICALITY ignore	EXTENSION MU-MIMO-Information-To-ReconfigureLCR	PRESENCE optional }|
	{ ID id-UE-Support-of-non-rectangular-resource-allocation	CRITICALITY ignore	EXTENSION UE-Support-of-non-rectangular-resource-allocation			PRESENCE optional},
	...
}

UL-CCTrCH-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF UL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD

UL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD ::= SEQUENCE {
	cCTrCH-ID									CCTrCH-ID,
	tFCS										TFCS,
	tFCI-Coding									TFCI-Coding,
	punctureLimit								PunctureLimit,
	ul-DPCH-InformationList						UL-DPCH-InformationAddList-RL-ReconfPrepTDD	OPTIONAL,
-- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 and on, should be defined in MultipleRL-UL-DPCH-InformationAddList-RL-ReconfPrepTDD
	iE-Extensions								ProtocolExtensionContainer { { UL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UL-DPCH-LCR-InformationAddListIE-RL-ReconfPrepTDD	CRITICALITY reject	EXTENSION UL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD		PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
-- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 and on, should be defined in MultipleRL-UL-DPCH-InformationAddList-RL-ReconfPrepTDD
	{ ID id-UL-SIRTarget										CRITICALITY reject	EXTENSION UL-SIR	PRESENCE optional }|
	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
-- This Information is the for the first RL repetition, SIR Target information for RL repetitions 2 and on, should be defined in MultipleRL-UL-DPCH-InformationAddList-RL-ReconfPrepTDD
	{ ID id-TDD-TPC-UplinkStepSize-InformationAdd-LCR-RL-ReconfPrepTDD	CRITICALITY reject	EXTENSION TDD-TPC-UplinkStepSize-LCR	PRESENCE optional	}|
-- This Information is the for the first RL repetition, TPCinformation for RL repetitions 2 and on, should be defined in MultipleRL-UL-DPCH-InformationAddList-RL-ReconfPrepTDD
	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
	{ ID id-RL-ID												CRITICALITY ignore	EXTENSION RL-ID	PRESENCE optional }|
-- This is the RL ID for the first RL repetition
	{ ID id-multipleRL-ul-DPCH-InformationList					CRITICALITY reject	EXTENSION MultipleRL-UL-DPCH-InformationAddList-RL-ReconfPrepTDD	PRESENCE optional }|
-- This Information is the for the 2nd and beyond RL repetition,
	{ ID id-UL-DPCH-768-InformationAddItemIE-RL-ReconfPrepTDD	CRITICALITY reject	EXTENSION UL-DPCH-768-InformationAddList-RL-ReconfPrepTDD		PRESENCE optional },	-- Applicable to 7.68Mcps TDD only, first radio link
	...
}

UL-DPCH-InformationAddList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container {{ UL-DPCH-InformationAddListIEs-RL-ReconfPrepTDD }}

UL-DPCH-InformationAddListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-UL-DPCH-InformationAddListIE-RL-ReconfPrepTDD   CRITICALITY reject		TYPE UL-DPCH-InformationAddItem-RL-ReconfPrepTDD		PRESENCE mandatory }
}

UL-DPCH-InformationAddItem-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	uL-Timeslot-Information					UL-Timeslot-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	uL-Timeslot-InformationLCR				UL-TimeslotLCR-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-LCR-InformationAddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-LCR-InformationAddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MultipleRL-UL-DPCH-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF MultipleRL-UL-DPCH-InformationAddListIE-RL-ReconfPrepTDD
--Includes the 2nd through the max number of radio link repetitions.

MultipleRL-UL-DPCH-InformationAddListIE-RL-ReconfPrepTDD ::= SEQUENCE {
	ul-DPCH-InformationList						UL-DPCH-InformationAddList-RL-ReconfPrepTDD		OPTIONAL,
	ul-DPCH-InformationListLCR					UL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD	OPTIONAL,
	ul-sir-target								UL-SIR											OPTIONAL,
	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
	tDD-TPC-UplinkStepSize-LCR 					TDD-TPC-UplinkStepSize-LCR						OPTIONAL,
	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
	rL-ID										RL-ID											OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { MultipleRL-UL-DPCH-InformationAddListIE-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

MultipleRL-UL-DPCH-InformationAddListIE-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UL-DPCH-768-InformationAddListIE-RL-ReconfPrepTDD	CRITICALITY reject	EXTENSION	UL-DPCH-768-InformationAddList-RL-ReconfPrepTDD	PRESENCE optional },
	...
}

UL-DPCH-768-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	uL-Timeslot-Information768				UL-Timeslot768-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-768-InformationAddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-768-InformationAddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF UL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD

UL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD ::= SEQUENCE {
	cCTrCH-ID									CCTrCH-ID,
	tFCS										TFCS												OPTIONAL,
	tFCI-Coding									TFCI-Coding											OPTIONAL,
	punctureLimit								PunctureLimit 										OPTIONAL,
	ul-DPCH-InformationAddList					UL-DPCH-InformationModify-AddList-RL-ReconfPrepTDD	OPTIONAL,
-- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	ul-DPCH-InformationModifyList				UL-DPCH-InformationModify-ModifyList-RL-ReconfPrepTDD	OPTIONAL,
-- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	ul-DPCH-InformationDeleteList				UL-DPCH-InformationModify-DeleteList-RL-ReconfPrepTDD	OPTIONAL,
-- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	iE-Extensions								ProtocolExtensionContainer { { UL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UL-DPCH-LCR-InformationModify-AddList	 CRITICALITY reject		EXTENSION	 UL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD		PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
-- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	{ ID id-UL-SIRTarget		CRITICALITY reject		EXTENSION		UL-SIR		PRESENCE optional	}|
	-- Applicable to 1.28Mcps TDD only.
-- This Information is the for the first RL repetition, SIR Target information for RL repetitions 2 and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	{ ID id-TDD-TPC-UplinkStepSize-InformationModify-LCR-RL-ReconfPrepTDD		CRITICALITY reject		EXTENSION	TDD-TPC-UplinkStepSize-LCR	PRESENCE optional	}|
	-- Applicable to 1.28Mcps TDD only
-- This Information is the for the first RL repetition, Step Size information for RL repetitions 2 and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	{ ID id-RL-ID										CRITICALITY ignore		EXTENSION		RL-ID		PRESENCE optional	}|
-- This is the RL ID for the first RL repetition
	{ ID id-multipleRL-ul-DPCH-InformationModifyList	CRITICALITY reject		EXTENSION		MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD	PRESENCE optional	}|
-- This DPCH Information is the for the 2nd and beyond RL repetition,
	{ ID id-UL-DPCH-768-InformationModify-AddItem	 CRITICALITY reject		EXTENSION	 UL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD		PRESENCE optional },	-- Applicable to 7.68Mcps TDD only
-- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 and on, should be defined in MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	...
}

UL-DPCH-InformationModify-AddList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container {{ UL-DPCH-InformationModify-AddListIEs-RL-ReconfPrepTDD }}

UL-DPCH-InformationModify-AddListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-UL-DPCH-InformationModify-AddListIE-RL-ReconfPrepTDD   CRITICALITY reject		TYPE UL-DPCH-InformationModify-AddItem-RL-ReconfPrepTDD		PRESENCE mandatory }
}

UL-DPCH-InformationModify-AddItem-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	uL-Timeslot-Information					UL-Timeslot-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-DPCH-InformationModify-ModifyList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container {{ UL-DPCH-InformationModify-ModifyListIEs-RL-ReconfPrepTDD }}

UL-DPCH-InformationModify-ModifyListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-UL-DPCH-InformationModify-ModifyListIE-RL-ReconfPrepTDD   CRITICALITY reject		TYPE UL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD		PRESENCE mandatory }
}

UL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod	OPTIONAL,
	repetitionLength						RepetitionLength	OPTIONAL,
	tdd-DPCHOffset							TDD-DPCHOffset		OPTIONAL,
	uL-Timeslot-InformationModify-ModifyList-RL-ReconfPrepTDD				UL-Timeslot-InformationModify-ModifyList-RL-ReconfPrepTDD			OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UL-TimeslotLCR-Information-RL-ReconfPrepTDD   	CRITICALITY reject		EXTENSION 	UL-TimeslotLCR-InformationModify-ModifyList-RL-ReconfPrepTDD		PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
	{ ID id-UL-Timeslot768-Information-RL-ReconfPrepTDD   	CRITICALITY reject		EXTENSION 	UL-Timeslot768-InformationModify-ModifyList-RL-ReconfPrepTDD		PRESENCE optional },	-- Applicable to 7.68Mcps TDD only
	...
}

UL-Timeslot-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfULTSs)) OF UL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD	-- Applicable to 3.84Mcps TDD only

UL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE {
	timeSlot								TimeSlot,
	midambleShiftAndBurstType				MidambleShiftAndBurstType		OPTIONAL,
	tFCI-Presence							TFCI-Presence					OPTIONAL,
	uL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD				UL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { UL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDPCHs)) OF UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD

UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE {
	dPCH-ID									DPCH-ID,
	tdd-ChannelisationCode					TDD-ChannelisationCode		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-TimeslotLCR-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfULTSLCRs)) OF UL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD	-- Applicable to 1.28Mcps TDD only

UL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE {
	timeSlotLCR								TimeSlotLCR,
	midambleShiftLCR						MidambleShiftLCR	OPTIONAL,
	tFCI-Presence							TFCI-Presence		OPTIONAL,
	uL-Code-InformationModify-ModifyList-RL-ReconfPrepTDDLCR				UL-Code-InformationModify-ModifyList-RL-ReconfPrepTDDLCR		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { UL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-PLCCH-Information-RL-ReconfPrepTDDLCR	CRITICALITY reject		EXTENSION PLCCHinformation	PRESENCE optional },
	...
}

UL-Code-InformationModify-ModifyList-RL-ReconfPrepTDDLCR ::= SEQUENCE (SIZE (1..maxNrOfDPCHLCRs)) OF UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDDLCR

UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDDLCR ::= SEQUENCE {
	dPCH-ID									DPCH-ID,
	tdd-ChannelisationCodeLCR				TDD-ChannelisationCodeLCR		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDDLCR-ExtIEs} }		OPTIONAL,
	...
}

UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDDLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
{ ID id-UL-DPCH-TimeSlotFormat-LCR-ModifyItem-RL-ReconfPrepTDD  CRITICALITY	reject	 EXTENSION TDD-UL-DPCH-TimeSlotFormat-LCR   PRESENCE  optional},

	...
}

UL-Timeslot768-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfULTSs)) OF UL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD	-- Applicable to 7.68Mcps TDD only

UL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE {
	timeSlot								TimeSlot,
	midambleShiftAndBurstType768			MidambleShiftAndBurstType768	OPTIONAL,
	tFCI-Presence							TFCI-Presence					OPTIONAL,
	uL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD768				UL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD768		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { UL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD768 ::= SEQUENCE (SIZE (1..maxNrOfDPCHs)) OF UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD768

UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD768 ::= SEQUENCE {
	dPCH-ID									DPCH-ID,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD768-ExtIEs} }		OPTIONAL,
	...
}

UL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD768-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-DPCH-InformationModify-DeleteList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container {{ UL-DPCH-InformationModify-DeleteListIEs-RL-ReconfPrepTDD }}

UL-DPCH-InformationModify-DeleteListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-UL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD   CRITICALITY reject		TYPE UL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD		PRESENCE mandatory }
}

UL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDPCHs)) OF UL-DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD

UL-DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD ::= SEQUENCE {
	dPCH-ID								DPCH-ID,
	iE-Extensions						ProtocolExtensionContainer { { UL-DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	uL-Timeslot-InformationLCR				UL-TimeslotLCR-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-LCR-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-LCR-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MultipleRL-UL-DPCH-InformationModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF MultipleRL-UL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD
--Includes the 2nd through the max number of radio link information repetitions.

MultipleRL-UL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD ::= SEQUENCE {
	ul-DPCH-InformationAddList					UL-DPCH-InformationModify-AddList-RL-ReconfPrepTDD	OPTIONAL,
	ul-DPCH-InformationModifyList				UL-DPCH-InformationModify-ModifyList-RL-ReconfPrepTDD	OPTIONAL,
	ul-DPCH-InformationDeleteList				UL-DPCH-InformationModify-DeleteList-RL-ReconfPrepTDD	OPTIONAL,
	ul-DPCH-InformationAddListLCR				UL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD	OPTIONAL,
	ul-sir-target								UL-SIR												OPTIONAL,
	tDD-TPC-UplinkStepSize-LCR					TDD-TPC-UplinkStepSize-LCR							OPTIONAL,
	rL-ID										RL-ID												OPTIONAL,
	-- This DPCH Information is the for the 2nd and beyond RL repetitions, 
	iE-Extensions								ProtocolExtensionContainer { { MultipleRL-UL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
...
}

MultipleRL-UL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UL-DPCH-768-InformationModify-AddList	 CRITICALITY reject		EXTENSION UL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD		PRESENCE optional },	-- Applicable to 7.68Mcps TDD only
	...
}

UL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	uL-Timeslot-Information768				UL-Timeslot768-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-DPCH-768-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-768-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF UL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD

UL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD ::= SEQUENCE {
	cCTrCH-ID									CCTrCH-ID,
	iE-Extensions								ProtocolExtensionContainer { { UL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

UL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-CCTrCH-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD

DL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD ::= SEQUENCE {
	cCTrCH-ID										CCTrCH-ID,
	tFCS											TFCS,
	tFCI-Coding										TFCI-Coding,
	punctureLimit									PunctureLimit,
	cCTrCH-TPCList									CCTrCH-TPCAddList-RL-ReconfPrepTDD				OPTIONAL,
	dl-DPCH-InformationList							DL-DPCH-InformationAddList-RL-ReconfPrepTDD 	OPTIONAL,
-- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD
	iE-Extensions									ProtocolExtensionContainer { { DL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs} }			OPTIONAL,
	...
}

DL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD				CRITICALITY reject	EXTENSION DL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD		PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
-- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD
	{ ID id-CCTrCH-Initial-DL-Power-RL-ReconfPrepTDD					CRITICALITY ignore	EXTENSION DL-Power	PRESENCE optional	}|
-- This DL Power information is the for the first RL repetition, DL power information for RL repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD
	{ ID id-TDD-TPC-DownlinkStepSize-InformationAdd-RL-ReconfPrepTDD	CRITICALITY reject	EXTENSION  TDD-TPC-DownlinkStepSize	 PRESENCE optional}|
-- This DL step size is the for the first RL repetition, DL step size information for RL repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD
	{ ID id-CCTrCH-Maximum-DL-Power-InformationAdd-RL-ReconfPrepTDD		CRITICALITY ignore	EXTENSION DL-Power	PRESENCE optional	}|
-- This DL Power information is the for the first RL repetition, DL power information for RL repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD
	{ ID id-CCTrCH-Minimum-DL-Power-InformationAdd-RL-ReconfPrepTDD		CRITICALITY ignore	EXTENSION DL-Power	PRESENCE optional	}|
-- This DL Power information is the for the first RL repetition, DL power information for RL repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD
	{ ID id-RL-ID														CRITICALITY ignore	EXTENSION RL-ID	PRESENCE optional	}|
-- This is the RL ID for the first RL repetition
	{ ID id-multipleRL-dl-DPCH-InformationList							CRITICALITY reject	EXTENSION MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD	PRESENCE optional	}|
-- This DPCH Information is the for the 2nd and beyond RL repetition,
	{ ID id-DL-DPCH-768-InformationAddItem-RL-ReconfPrepTDD				CRITICALITY reject	EXTENSION DL-DPCH-768-InformationAddList-RL-ReconfPrepTDD		PRESENCE optional },	-- Applicable to 7.68Mcps TDD only
	...
}

CCTrCH-TPCAddList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF CCTrCH-TPCAddItem-RL-ReconfPrepTDD		-- Applicable to 3.84Mcps TDD and 7.68Mcps TDD only

CCTrCH-TPCAddItem-RL-ReconfPrepTDD	 ::= SEQUENCE {
	cCTrCH-ID								CCTrCH-ID,
	iE-Extensions							ProtocolExtensionContainer { { CCTrCH-TPCAddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

CCTrCH-TPCAddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-DPCH-InformationAddList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container {{ DL-DPCH-InformationAddListIEs-RL-ReconfPrepTDD }}

DL-DPCH-InformationAddListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-DL-DPCH-InformationAddListIE-RL-ReconfPrepTDD   CRITICALITY reject		TYPE DL-DPCH-InformationAddItem-RL-ReconfPrepTDD		PRESENCE mandatory }
}

DL-DPCH-InformationAddItem-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	dL-Timeslot-Information					DL-Timeslot-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	dL-Timeslot-InformationLCR				DL-TimeslotLCR-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-LCR-InformationAddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-LCR-InformationAddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MultipleRL-DL-DPCH-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF MultipleRL-DL-DPCH-InformationAddListIE-RL-ReconfPrepTDD
	--Includes the 2nd through the max number of radio link information repetitions.

MultipleRL-DL-DPCH-InformationAddListIE-RL-ReconfPrepTDD ::= SEQUENCE {
	dl-DPCH-InformationList										DL-DPCH-InformationAddList-RL-ReconfPrepTDD	OPTIONAL,
	dl-DPCH-InformationListLCR									DL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD	OPTIONAL,
	cCTrCH-Initial-DL-Power										DL-Power							OPTIONAL,
	tDD-TPC-DownlinkStepSize									TDD-TPC-DownlinkStepSize			OPTIONAL,
	cCTrCH-Maximum-DL-Power-InformationAdd-RL-ReconfPrepTDD		DL-Power							OPTIONAL,
	cCTrCH-Minimum-DL-Power-InformationAdd-RL-ReconfPrepTDD		DL-Power							OPTIONAL,
	rL-ID														RL-ID								OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { MultipleRL-DL-DPCH-InformationAddListIE-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

MultipleRL-DL-DPCH-InformationAddListIE-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-DPCH-768-InformationAddList-RL-ReconfPrepTDD		CRITICALITY reject	EXTENSION DL-DPCH-768-InformationAddList-RL-ReconfPrepTDD		PRESENCE optional },	-- Applicable to 7.68Mcps TDD only
	...
}

DL-DPCH-768-InformationAddList-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	dL-Timeslot-Information768				DL-Timeslot768-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-768-InformationAddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-768-InformationAddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD

DL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD ::= SEQUENCE {
	cCTrCH-ID										CCTrCH-ID,
	tFCS											TFCS											OPTIONAL,
	tFCI-Coding										TFCI-Coding										OPTIONAL,
	punctureLimit									PunctureLimit 									OPTIONAL,
	cCTrCH-TPCList									CCTrCH-TPCModifyList-RL-ReconfPrepTDD			OPTIONAL,
	dl-DPCH-InformationAddList						DL-DPCH-InformationModify-AddList-RL-ReconfPrepTDD 	OPTIONAL,
-- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	dl-DPCH-InformationModifyList					DL-DPCH-InformationModify-ModifyList-RL-ReconfPrepTDD 	OPTIONAL,
-- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	dl-DPCH-InformationDeleteList					DL-DPCH-InformationModify-DeleteList-RL-ReconfPrepTDD 	OPTIONAL,
-- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	iE-Extensions									ProtocolExtensionContainer { { DL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD-ExtIEs} }			OPTIONAL,
	...
}

DL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD CRITICALITY reject		EXTENSION 	DL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD		PRESENCE optional }|  -- Applicable to 1.28Mcps TDD only
-- This DPCH Information is the for the first RL repetition, DPCH information for RL repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	{ ID id-TDD-TPC-DownlinkStepSize-InformationModify-RL-ReconfPrepTDD	CRITICALITY reject	EXTENSION TDD-TPC-DownlinkStepSize	PRESENCE optional}|
-- This Step Size Information is the for the first RL repetition, step size information for RL repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	{ ID id-CCTrCH-Maximum-DL-Power-InformationModify-RL-ReconfPrepTDD		CRITICALITY ignore	EXTENSION DL-Power		PRESENCE optional	}|
-- This power Information is the for the first RL repetition, power information for RL repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	{ ID id-CCTrCH-Minimum-DL-Power-InformationModify-RL-ReconfPrepTDD		CRITICALITY ignore	EXTENSION DL-Power		PRESENCE optional	}|
-- This power Information is the for the first RL repetition, power information for RL repetitions 2 and on, should be defined in MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD
	{ ID id-RL-ID		CRITICALITY ignore		EXTENSION		RL-ID		PRESENCE optional	}|
-- This is the RL ID for the first RL repetition
	{ ID id-multipleRL-dl-DPCH-InformationModifyList	CRITICALITY reject		EXTENSION		MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD	PRESENCE optional	}|
-- This DPCH Information is the for the 2nd and beyond RL repetitions,
	{ ID id-DL-DPCH-768-InformationModify-AddItem-RL-ReconfPrepTDD CRITICALITY reject		EXTENSION 	DL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD		PRESENCE optional },  -- Applicable to 7.68Mcps TDD only first radio link
	...
}

CCTrCH-TPCModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF CCTrCH-TPCModifyItem-RL-ReconfPrepTDD

CCTrCH-TPCModifyItem-RL-ReconfPrepTDD	 ::= SEQUENCE {
	cCTrCH-ID								CCTrCH-ID,
	iE-Extensions							ProtocolExtensionContainer { { CCTrCH-TPCModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

CCTrCH-TPCModifyItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-DPCH-InformationModify-AddList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container {{ DL-DPCH-InformationModify-AddListIEs-RL-ReconfPrepTDD }}	
-- Applicable to 3.84Mcps TDD only

DL-DPCH-InformationModify-AddListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-DL-DPCH-InformationModify-AddListIE-RL-ReconfPrepTDD   CRITICALITY reject		TYPE DL-DPCH-InformationModify-AddItem-RL-ReconfPrepTDD		PRESENCE mandatory }
}

DL-DPCH-InformationModify-AddItem-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	dL-Timeslot-Information					DL-Timeslot-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-DPCH-InformationModify-ModifyList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container {{ DL-DPCH-InformationModify-ModifyListIEs-RL-ReconfPrepTDD }}

DL-DPCH-InformationModify-ModifyListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-DL-DPCH-InformationModify-ModifyListIE-RL-ReconfPrepTDD   CRITICALITY reject		TYPE DL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD		PRESENCE mandatory }
}

DL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod			OPTIONAL,
	repetitionLength						RepetitionLength			OPTIONAL,
	tdd-DPCHOffset							TDD-DPCHOffset				OPTIONAL,
	dL-Timeslot-InformationAddModify-ModifyList-RL-ReconfPrepTDD		DL-Timeslot-InformationModify-ModifyList-RL-ReconfPrepTDD			OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-Timeslot-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD   CRITICALITY reject			EXTENSION		 DL-Timeslot-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD		PRESENCE optional }|
	{ ID id-DL-Timeslot-768-InformationModify-ModifyList-RL-ReconfPrepTDD   CRITICALITY reject			EXTENSION		 DL-Timeslot-768-InformationModify-ModifyList-RL-ReconfPrepTDD		PRESENCE optional },
	...
}

DL-Timeslot-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDLTSs)) OF DL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD

DL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD	 ::= SEQUENCE {
	timeSlot								TimeSlot,
	midambleShiftAndBurstType				MidambleShiftAndBurstType			OPTIONAL,
	tFCI-Presence							TFCI-Presence						OPTIONAL,
	dL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD				DL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD			OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-Timeslot-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Code-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (0..maxNrOfDPCHs)) OF DL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD

DL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD	 ::= SEQUENCE {
	dPCH-ID									DPCH-ID,
	tdd-ChannelisationCode					TDD-ChannelisationCode		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-Code-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Timeslot-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDLTSLCRs)) OF DL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD

DL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD	 ::= SEQUENCE {
	timeSlotLCR								TimeSlotLCR,
	midambleShiftLCR						MidambleShiftLCR		OPTIONAL,
	tFCI-Presence							TFCI-Presence			OPTIONAL,
	dL-Code-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD				DL-Code-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD			OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Maximum-DL-Power-Modify-LCR-InformationModify-RL-ReconfPrepTDD	CRITICALITY ignore	EXTENSION DL-Power		PRESENCE optional	}|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-Minimum-DL-Power-Modify-LCR-InformationModify-RL-ReconfPrepTDD	CRITICALITY ignore	EXTENSION DL-Power		PRESENCE optional	},
	-- Applicable to 1.28Mcps TDD only
	...
}

DL-Code-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDPCHLCRs)) OF DL-Code-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD

DL-Code-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD	 ::= SEQUENCE {
	dPCH-ID									DPCH-ID,
	tdd-ChannelisationCodeLCR				TDD-ChannelisationCodeLCR		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-Code-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-Code-LCR-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-DPCH-TimeSlotFormat-LCR-ModifyItem-RL-ReconfPrepTDD	 CRITICALITY	reject	 EXTENSION TDD-DL-DPCH-TimeSlotFormat-LCR   PRESENCE  optional},
	...
}

DL-Timeslot-768-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDLTSs)) OF DL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD

DL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD	 ::= SEQUENCE {
	timeSlot								TimeSlot,
	midambleShiftAndBurstType				MidambleShiftAndBurstType			OPTIONAL,
	tFCI-Presence							TFCI-Presence						OPTIONAL,
	dL-Code-768-InformationModify-ModifyList-RL-ReconfPrepTDD				DL-Code-768-InformationModify-ModifyList-RL-ReconfPrepTDD			OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-Timeslot-768-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Code-768-InformationModify-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDPCHs768)) OF DL-Code-768-InformationModify-ModifyItem-RL-ReconfPrepTDD

DL-Code-768-InformationModify-ModifyItem-RL-ReconfPrepTDD	 ::= SEQUENCE {
	dPCH-ID768								DPCH-ID768,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-Code-768-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-Code-768-InformationModify-ModifyItem-RL-ReconfPrepTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-DPCH-InformationModify-DeleteList-RL-ReconfPrepTDD ::= ProtocolIE-Single-Container {{ DL-DPCH-InformationModify-DeleteListIEs-RL-ReconfPrepTDD }}

DL-DPCH-InformationModify-DeleteListIEs-RL-ReconfPrepTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-DL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD   CRITICALITY reject		TYPE DL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD		PRESENCE mandatory }
}

DL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDPCHs)) OF DL-DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD

DL-DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD ::= SEQUENCE {
	dPCH-ID										DPCH-ID,
	iE-Extensions								ProtocolExtensionContainer { { DL-DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-InformationModify-DeleteItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	dL-Timeslot-InformationLCR				DL-TimeslotLCR-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-LCR-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-LCR-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MultipleRL-DL-DPCH-InformationModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF MultipleRL-DL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD
	--Includes the 2nd through the max number of radio link information repetitions.

MultipleRL-DL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD ::= SEQUENCE {
	dl-DPCH-InformationAddList										DL-DPCH-InformationModify-AddList-RL-ReconfPrepTDD			OPTIONAL,
	dl-DPCH-InformationModifyList									DL-DPCH-InformationModify-ModifyList-RL-ReconfPrepTDD		OPTIONAL,
	dl-DPCH-InformationDeleteList									DL-DPCH-InformationModify-DeleteList-RL-ReconfPrepTDD		OPTIONAL,
	dl-DPCH-InformationAddListLCR									DL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD	OPTIONAL,
	tDD-TPC-DownlinkStepSize-InformationModify-RL-ReconfPrepTDD		TDD-TPC-DownlinkStepSize											OPTIONAL,
	cCTrCH-Maximum-DL-Power-InformationModify-RL-ReconfPrepTDD		DL-Power									OPTIONAL,
	cCTrCH-Minimum-DL-Power-InformationModify-RL-ReconfPrepTDD		DL-Power									OPTIONAL,
	rL-ID															RL-ID										OPTIONAL,
	iE-Extensions													ProtocolExtensionContainer { { MultipleRL-DL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
} 

MultipleRL-DL-DPCH-InformationModifyListIE-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD CRITICALITY reject		EXTENSION 	DL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD		PRESENCE optional },  -- Applicable to 7.68Mcps TDD only
	...
}

DL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-DPCHOffset							TDD-DPCHOffset,
	dL-Timeslot-Information768				DL-Timeslot768-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-768-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-768-InformationModify-AddItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD

DL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD ::= SEQUENCE {
	cCTrCH-ID										CCTrCH-ID,
	iE-Extensions									ProtocolExtensionContainer { { DL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD-ExtIEs} }			OPTIONAL,
	...
}

DL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DCH-DeleteList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-DeleteItem-RL-ReconfPrepTDD

DCH-DeleteItem-RL-ReconfPrepTDD ::= SEQUENCE {
	dCH-ID										DCH-ID,
	iE-Extensions								ProtocolExtensionContainer { { DCH-DeleteItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DCH-DeleteItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DSCH-Information-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDSCHs)) OF DSCH-Information-ModifyItem-RL-ReconfPrepTDD

DSCH-Information-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE {
	dSCH-ID										DSCH-ID,
	cCTrCH-ID									CCTrCH-ID					OPTIONAL,
	-- DL CCTrCH in which the DSCH is mapped
	transportFormatSet							TransportFormatSet			OPTIONAL,
	allocationRetentionPriority					AllocationRetentionPriority	OPTIONAL,
	frameHandlingPriority						FrameHandlingPriority		OPTIONAL,
	toAWS										ToAWS						OPTIONAL,
	toAWE										ToAWE						OPTIONAL,
	transportBearerRequestIndicator				TransportBearerRequestIndicator,
	iE-Extensions								ProtocolExtensionContainer { { DSCH-Information-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
 }

DSCH-Information-ModifyItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-bindingID					CRITICALITY ignore	EXTENSION BindingID					PRESENCE optional	}|
	-- Shall be ignored if bearer establishment with ALCAP.
	{ ID id-transportlayeraddress		CRITICALITY ignore	EXTENSION TransportLayerAddress		PRESENCE optional	}|
	-- Shall be ignored if bearer establishment with ALCAP.
	{ ID id-TnlQos						CRITICALITY ignore	EXTENSION TnlQos					PRESENCE optional	},
	...
}

DSCH-Information-DeleteList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfDSCHs)) OF DSCH-Information-DeleteItem-RL-ReconfPrepTDD

DSCH-Information-DeleteItem-RL-ReconfPrepTDD ::= SEQUENCE {
	dSCH-ID										DSCH-ID,
	iE-Extensions								ProtocolExtensionContainer { { DSCH-Information-DeleteItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

DSCH-Information-DeleteItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

USCH-Information-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfUSCHs)) OF USCH-Information-ModifyItem-RL-ReconfPrepTDD

USCH-Information-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE {
 	uSCH-ID										USCH-ID,
 	transportFormatSet							TransportFormatSet			OPTIONAL,
	allocationRetentionPriority					AllocationRetentionPriority	OPTIONAL,
	cCTrCH-ID									CCTrCH-ID					OPTIONAL,	-- UL CCTrCH in which the USCH is mapped
	transportBearerRequestIndicator				TransportBearerRequestIndicator,
	iE-Extensions								ProtocolExtensionContainer { { USCH-Information-ModifyItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

USCH-Information-ModifyItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-bindingID						CRITICALITY	ignore		EXTENSION BindingID				PRESENCE optional	}|
	-- Shall be ignored if bearer establishment with ALCAP.
	{ ID id-transportlayeraddress			CRITICALITY	ignore		EXTENSION TransportLayerAddress	PRESENCE optional	}|
	-- Shall be ignored if bearer establishment with ALCAP.
	{ ID id-TnlQos							CRITICALITY	ignore		EXTENSION TnlQos				PRESENCE optional	},
	...
}

USCH-Information-DeleteList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfUSCHs)) OF USCH-Information-DeleteItem-RL-ReconfPrepTDD

USCH-Information-DeleteItem-RL-ReconfPrepTDD ::= SEQUENCE {
	uSCH-ID										USCH-ID,
	iE-Extensions								ProtocolExtensionContainer { { USCH-Information-DeleteItem-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...

}

USCH-Information-DeleteItem-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MultipleRL-Information-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF RL-Information-RL-ReconfPrepTDD
--Includes the 2nd through the max number of radio link information repetitions.

RL-Information-RL-ReconfPrepTDD ::= SEQUENCE {
	rL-ID										RL-ID,
	maxDL-Power									DL-Power			OPTIONAL,
	minDL-Power									DL-Power			OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { RL-Information-RL-ReconfPrepTDD-ExtIEs} }		OPTIONAL,
	...
}

RL-Information-RL-ReconfPrepTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-InitDL-Power								CRITICALITY ignore	EXTENSION DL-Power				PRESENCE optional	}|
	{ ID id-RL-Specific-DCH-Info						CRITICALITY ignore	EXTENSION RL-Specific-DCH-Info			PRESENCE optional	}|
	{ ID id-UL-Synchronisation-Parameters-LCR			CRITICALITY ignore	EXTENSION UL-Synchronisation-Parameters-LCR	PRESENCE optional	}|
	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD
	{ ID id-TimeslotISCP-LCR-InfoList-RL-ReconfPrepTDD	CRITICALITY ignore	EXTENSION DL-TimeslotISCPInfoLCR			PRESENCE optional	}|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-UARFCNforNt									CRITICALITY reject	EXTENSION UARFCN				PRESENCE optional	},
	  -- Applicable to 1.28Mcps TDD when using multiple frequencies
	...
}


-- **************************************************************
--
-- RADIO LINK RECONFIGURATION READY
--
-- **************************************************************

RadioLinkReconfigurationReady ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkReconfigurationReady-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkReconfigurationReady-Extensions}}		OPTIONAL,
	...
}

RadioLinkReconfigurationReady-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID					CRITICALITY ignore	TYPE CRNC-CommunicationContextID						PRESENCE mandatory }|
	{ ID id-RL-InformationResponseList-RL-ReconfReady	CRITICALITY ignore	TYPE RL-InformationResponseList-RL-ReconfReady	PRESENCE optional }|
	{ ID id-CriticalityDiagnostics						CRITICALITY ignore	TYPE CriticalityDiagnostics								PRESENCE optional },
	...
}

RadioLinkReconfigurationReady-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TargetCommunicationControlPortID		CRITICALITY ignore	EXTENSION CommunicationControlPortID				PRESENCE optional }|
	{ ID id-HSDSCH-FDD-Information-Response			CRITICALITY ignore	EXTENSION HSDSCH-FDD-Information-Response		PRESENCE optional }|
	-- FDD only
	{ ID id-HSDSCH-TDD-Information-Response			CRITICALITY ignore	EXTENSION HSDSCH-TDD-Information-Response		PRESENCE optional }|
	-- TDD only
	{ ID id-E-DCH-Information-Response				CRITICALITY ignore	EXTENSION E-DCH-Information-Response				PRESENCE optional }|
	{ ID id-MAChs-ResetIndicator					CRITICALITY ignore	EXTENSION MAChs-ResetIndicator						PRESENCE optional }|
	{ ID id-Fast-Reconfiguration-Permission			CRITICALITY ignore	EXTENSION Fast-Reconfiguration-Permission		PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivityHS-SCCH-less-Information-Response	CRITICALITY ignore	EXTENSION ContinuousPacketConnectivityHS-SCCH-less-Information-Response	PRESENCE optional }|
	{ ID id-Additional-HS-Cell-Information-Response	CRITICALITY ignore	EXTENSION Additional-HS-Cell-Information-Response-List	PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR	CRITICALITY ignore	EXTENSION ContinuousPacketConnectivity-DRX-Information-ResponseLCR	PRESENCE optional }|
	{ ID id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR	CRITICALITY ignore	EXTENSION HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR	PRESENCE optional }|
	{ ID id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR		CRITICALITY ignore	EXTENSION E-DCH-Semi-PersistentScheduling-Information-ResponseLCR	PRESENCE optional }|
	{ ID id-Additional-EDCH-Cell-Information-ResponseRLReconf	CRITICALITY ignore	EXTENSION Additional-EDCH-Cell-Information-Response-RLReconf-List	PRESENCE optional }|
	{ ID id-E-RNTI-For-FACH							CRITICALITY ignore	EXTENSION E-RNTI										PRESENCE optional }|
	{ ID id-Multi-Carrier-EDCH-Response				CRITICALITY ignore	EXTENSION Multi-Carrier-EDCH-Information-Response	PRESENCE optional }|
	{ ID id-MU-MIMO-Information-Response			CRITICALITY reject	EXTENSION MU-MIMO-Information-Response			PRESENCE optional }|
	{ ID id-Non-rectangular-resource-allocation-indicator	CRITICALITY reject	EXTENSION Non-rectangular-resource-allocation-indicator				PRESENCE optional}|
	{ ID id-Non-rectangular-resource-timeslot-set	CRITICALITY reject	EXTENSION Non-rectangular-resource-timeslot-set	PRESENCE optional},
	...
}

RL-InformationResponseList-RL-ReconfReady	 ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container {{ RL-InformationResponseItemIE-RL-ReconfReady}}

RL-InformationResponseItemIE-RL-ReconfReady NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-InformationResponseItem-RL-ReconfReady	CRITICALITY ignore	TYPE RL-InformationResponseItem-RL-ReconfReady	PRESENCE mandatory }
}

RL-InformationResponseItem-RL-ReconfReady ::= SEQUENCE {
	rL-ID											RL-ID,
	dCH-InformationResponseList-RL-ReconfReady		DCH-InformationResponseList-RL-ReconfReady	OPTIONAL,
	dSCH-InformationResponseList-RL-ReconfReady		DSCH-InformationResponseList-RL-ReconfReady	OPTIONAL, -- TDD only
	uSCH-InformationResponseList-RL-ReconfReady		USCH-InformationResponseList-RL-ReconfReady	OPTIONAL, -- TDD only
	not-Used-tFCI2-BearerInformationResponse		NULL										OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { RL-InformationResponseItem-RL-ReconfReady-ExtIEs} }		OPTIONAL,
	...
}

RL-InformationResponseItem-RL-ReconfReady-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-PowerBalancing-UpdatedIndicator			CRITICALITY ignore	EXTENSION DL-PowerBalancing-UpdatedIndicator			PRESENCE optional }|
	{ ID id-E-DCH-RL-Set-ID								CRITICALITY ignore	EXTENSION RL-Set-ID												PRESENCE optional }|
	{ ID id-E-DCH-FDD-DL-Control-Channel-Information	CRITICALITY ignore	EXTENSION E-DCH-FDD-DL-Control-Channel-Information	PRESENCE optional }|
	{ ID id-E-DCH-FDD-Information-Response				CRITICALITY ignore	EXTENSION E-DCH-FDD-Information-Response				PRESENCE optional }|
	{ ID id-HSDSCH-PreconfigurationInfo					CRITICALITY ignore	EXTENSION HSDSCH-PreconfigurationInfo					PRESENCE optional }|
	{ ID id-Non-Serving-RL-Preconfig-Info				CRITICALITY ignore	EXTENSION Non-Serving-RL-Preconfig-Info					PRESENCE optional },
	...
}

DCH-InformationResponseList-RL-ReconfReady ::= ProtocolIE-Single-Container {{ DCH-InformationResponseListIEs-RL-ReconfReady }}

DCH-InformationResponseListIEs-RL-ReconfReady NBAP-PROTOCOL-IES ::= {
	{ ID id-DCH-InformationResponse   CRITICALITY ignore	TYPE DCH-InformationResponse	PRESENCE mandatory }
}

DSCH-InformationResponseList-RL-ReconfReady ::= ProtocolIE-Single-Container {{ DSCH-InformationResponseListIEs-RL-ReconfReady }}

DSCH-InformationResponseListIEs-RL-ReconfReady NBAP-PROTOCOL-IES ::= {
	{ ID id-DSCH-InformationResponse   CRITICALITY ignore	TYPE DSCH-InformationResponse	PRESENCE mandatory }
}

USCH-InformationResponseList-RL-ReconfReady ::= ProtocolIE-Single-Container {{ USCH-InformationResponseListIEs-RL-ReconfReady }}

USCH-InformationResponseListIEs-RL-ReconfReady NBAP-PROTOCOL-IES ::= {
	{ ID id-USCH-InformationResponse   CRITICALITY ignore	TYPE USCH-InformationResponse	PRESENCE mandatory }
}

-- **************************************************************
--
-- RADIO LINK RECONFIGURATION FAILURE
--
-- **************************************************************

RadioLinkReconfigurationFailure ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkReconfigurationFailure-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkReconfigurationFailure-Extensions}}		OPTIONAL,
	...
}

RadioLinkReconfigurationFailure-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID			CRITICALITY ignore	TYPE CRNC-CommunicationContextID		PRESENCE mandatory } |
	{ ID id-CauseLevel-RL-ReconfFailure			CRITICALITY ignore	TYPE CauseLevel-RL-ReconfFailure		PRESENCE mandatory } |
	{ ID id-CriticalityDiagnostics				CRITICALITY ignore	TYPE CriticalityDiagnostics			PRESENCE optional },
	...
}

RadioLinkReconfigurationFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CauseLevel-RL-ReconfFailure ::= CHOICE {
	generalCause		GeneralCauseList-RL-ReconfFailure,
	rLSpecificCause		RLSpecificCauseList-RL-ReconfFailure,
	...
}

GeneralCauseList-RL-ReconfFailure ::= SEQUENCE {
	cause										Cause,
	iE-Extensions								ProtocolExtensionContainer { { GeneralCauseItem-RL-ReconfFailure-ExtIEs} }			OPTIONAL,
	...
}

GeneralCauseItem-RL-ReconfFailure-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RLSpecificCauseList-RL-ReconfFailure ::= SEQUENCE {
	rL-ReconfigurationFailureList-RL-ReconfFailure		RL-ReconfigurationFailureList-RL-ReconfFailure		OPTIONAL,
	iE-Extensions										ProtocolExtensionContainer { { RLSpecificCauseItem-RL-ReconfFailure-ExtIEs} }			OPTIONAL,
	...
}

RLSpecificCauseItem-RL-ReconfFailure-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-ReconfigurationFailureList-RL-ReconfFailure ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container {{ RL-ReconfigurationFailureItemIE-RL-ReconfFailure}}

RL-ReconfigurationFailureItemIE-RL-ReconfFailure NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-ReconfigurationFailureItem-RL-ReconfFailure	CRITICALITY ignore	TYPE RL-ReconfigurationFailureItem-RL-ReconfFailure	PRESENCE mandatory}
}

RL-ReconfigurationFailureItem-RL-ReconfFailure ::= SEQUENCE {
 	rL-ID										RL-ID,
	cause										Cause,
	iE-Extensions								ProtocolExtensionContainer { { RL-ReconfigurationFailureItem-RL-ReconfFailure-ExtIEs} }			OPTIONAL,
	...
}

RL-ReconfigurationFailureItem-RL-ReconfFailure-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK RECONFIGURATION COMMIT
--
-- **************************************************************

RadioLinkReconfigurationCommit ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkReconfigurationCommit-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkReconfigurationCommit-Extensions}}		OPTIONAL,
	...
}

RadioLinkReconfigurationCommit-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-NodeB-CommunicationContextID			CRITICALITY ignore	TYPE NodeB-CommunicationContextID	PRESENCE mandatory } |
	{ ID	id-CFN									CRITICALITY ignore	TYPE CFN					PRESENCE mandatory }|
	{ ID 	id-Active-Pattern-Sequence-Information	CRITICALITY ignore	TYPE Active-Pattern-Sequence-Information	PRESENCE optional },
	-- FDD only
	...
}

RadioLinkReconfigurationCommit-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Fast-Reconfiguration-Mode	CRITICALITY reject	EXTENSION Fast-Reconfiguration-Mode		PRESENCE optional }|--FDD only
	{ ID id-ActivationDelay				CRITICALITY reject	EXTENSION ActivationDelay						PRESENCE optional },--FDD only
	...
}

-- **************************************************************
--
-- RADIO LINK RECONFIGURATION CANCEL
--
-- **************************************************************

RadioLinkReconfigurationCancel ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkReconfigurationCancel-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkReconfigurationCancel-Extensions}}		OPTIONAL,
	...
}

RadioLinkReconfigurationCancel-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-NodeB-CommunicationContextID			CRITICALITY ignore		TYPE NodeB-CommunicationContextID			PRESENCE mandatory	},
	...
}

RadioLinkReconfigurationCancel-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK RECONFIGURATION REQUEST FDD
--
-- **************************************************************

RadioLinkReconfigurationRequestFDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkReconfigurationRequestFDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkReconfigurationRequestFDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkReconfigurationRequestFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-NodeB-CommunicationContextID					CRITICALITY reject	TYPE NodeB-CommunicationContextID					PRESENCE mandatory }|
	{ ID id-UL-DPCH-Information-RL-ReconfRqstFDD			CRITICALITY reject	TYPE UL-DPCH-Information-RL-ReconfRqstFDD			PRESENCE optional }|
	{ ID id-DL-DPCH-Information-RL-ReconfRqstFDD			CRITICALITY reject	TYPE DL-DPCH-Information-RL-ReconfRqstFDD			PRESENCE optional }|
	{ ID id-FDD-DCHs-to-Modify								CRITICALITY reject	TYPE FDD-DCHs-to-Modify					PRESENCE optional }|
	{ ID id-DCHs-to-Add-FDD									CRITICALITY reject	TYPE DCH-FDD-Information					PRESENCE optional }|
	{ ID id-DCH-DeleteList-RL-ReconfRqstFDD					CRITICALITY reject	TYPE DCH-DeleteList-RL-ReconfRqstFDD				PRESENCE optional }|
	{ ID id-RL-InformationList-RL-ReconfRqstFDD				CRITICALITY reject	TYPE RL-InformationList-RL-ReconfRqstFDD			PRESENCE optional }|
	{ ID id-Transmission-Gap-Pattern-Sequence-Information	CRITICALITY reject	TYPE Transmission-Gap-Pattern-Sequence-Information	 PRESENCE optional },
	...
}

RadioLinkReconfigurationRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-SignallingBearerRequestIndicator			CRITICALITY reject	EXTENSION SignallingBearerRequestIndicator		PRESENCE optional}|
	{ ID id-HSDSCH-FDD-Information						CRITICALITY reject	EXTENSION HSDSCH-FDD-Information					PRESENCE optional}|
	{ ID id-HSDSCH-Information-to-Modify-Unsynchronised	CRITICALITY reject	EXTENSION HSDSCH-Information-to-Modify-Unsynchronised	PRESENCE optional}|
	{ ID id-HSDSCH-MACdFlows-to-Add						CRITICALITY reject	EXTENSION HSDSCH-MACdFlows-Information			PRESENCE optional}|
	{ ID id-HSDSCH-MACdFlows-to-Delete					CRITICALITY reject	EXTENSION HSDSCH-MACdFlows-to-Delete				PRESENCE optional}|
	{ ID id-HSDSCH-RNTI									CRITICALITY reject	EXTENSION HSDSCH-RNTI									PRESENCE conditional}|
	-- The IE shall be present if HS-PDSCH RL ID IE is present.
	{ ID id-HSPDSCH-RL-ID								CRITICALITY reject	EXTENSION RL-ID											PRESENCE optional}|
	{ ID id-E-DPCH-Information-RL-ReconfRqstFDD			CRITICALITY reject	EXTENSION E-DPCH-Information-RL-ReconfRqstFDD	PRESENCE optional}|
	{ ID id-E-DCH-FDD-Information						CRITICALITY reject	EXTENSION E-DCH-FDD-Information					PRESENCE optional}|
	{ ID id-E-DCH-FDD-Information-to-Modify				CRITICALITY reject	EXTENSION E-DCH-FDD-Information-to-Modify		PRESENCE optional}|
	{ ID id-E-DCH-MACdFlows-to-Add						CRITICALITY reject	EXTENSION E-DCH-MACdFlows-Information			PRESENCE optional}|
	{ ID id-E-DCH-MACdFlows-to-Delete					CRITICALITY reject	EXTENSION E-DCH-MACdFlows-to-Delete				PRESENCE optional}|
	{ ID id-Serving-E-DCH-RL-ID							CRITICALITY reject	EXTENSION Serving-E-DCH-RL-ID						PRESENCE optional}|
	{ ID id-CPC-Information								CRITICALITY reject	EXTENSION CPC-Information							PRESENCE optional}|
	{ ID id-NoOfTargetCellHS-SCCH-Order					CRITICALITY ignore	EXTENSION NoOfTargetCellHS-SCCH-Order			PRESENCE optional}|
	{ ID id-Additional-HS-Cell-Information-RL-Reconf-Req	CRITICALITY reject	EXTENSION Additional-HS-Cell-Information-RL-Reconf-Req	PRESENCE optional}|
	{ ID id-UE-AggregateMaximumBitRate					CRITICALITY ignore	EXTENSION UE-AggregateMaximumBitRate				PRESENCE optional}|
	{ ID id-Additional-EDCH-Cell-Information-RL-Reconf-Req	CRITICALITY reject	EXTENSION Additional-EDCH-Cell-Information-RL-Reconf-Req	PRESENCE optional}|
	{ ID id-UL-CLTD-Information-Reconf					CRITICALITY reject	EXTENSION UL-CLTD-Information-Reconf				PRESENCE optional}|
	{ ID id-E-DCH-Decoupling-Indication					CRITICALITY reject	EXTENSION E-DCH-Decoupling-Indication			PRESENCE optional}|
	{ ID id-Radio-Links-without-DPCH-FDPCH-Indication	CRITICALITY reject	EXTENSION Radio-Links-without-DPCH-FDPCH-Indication		PRESENCE optional}|
	{ ID id-UL-DPCCH2-Information-Reconf				CRITICALITY reject	EXTENSION UL-DPCCH2-Information-Reconf			PRESENCE optional}|
	{ ID id-Downlink-TPC-enhancements-Reconf			CRITICALITY reject	EXTENSION Downlink-TPC-enhancements-Reconf		PRESENCE optional},
...
}

Additional-HS-Cell-Information-RL-Reconf-Req	::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Information-RL-Reconf-Req-ItemIEs

Additional-HS-Cell-Information-RL-Reconf-Req-ItemIEs	::=SEQUENCE{
	hSPDSCH-RL-ID									RL-ID,
	c-ID											C-ID										OPTIONAL,
	hS-DSCH-FDD-Secondary-Serving-Information		HS-DSCH-FDD-Secondary-Serving-Information	OPTIONAL,
	hS-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised		HS-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised	OPTIONAL,
	hS-DSCH-Secondary-Serving-Remove				HS-DSCH-Secondary-Serving-Remove			OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { Additional-HS-Cell-Information-RL-Reconf-Req-ExtIEs} } OPTIONAL,
	...
}

Additional-HS-Cell-Information-RL-Reconf-Req-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Additional-EDCH-Cell-Information-RL-Reconf-Req	::=SEQUENCE{
	setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency							Setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-RL-Reconf-Req-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-Cell-Information-RL-Reconf-Req-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}


UL-DPCH-Information-RL-ReconfRqstFDD ::= SEQUENCE {
	ul-TFCS											TFCS			OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { UL-DPCH-Information-RL-ReconfRqstFDD-ExtIEs} }		OPTIONAL,
	...
}

UL-DPCH-Information-RL-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UL-DPDCH-Indicator-For-E-DCH-Operation	CRITICALITY reject	EXTENSION UL-DPDCH-Indicator-For-E-DCH-Operation		PRESENCE optional },
	...
}

DL-DPCH-Information-RL-ReconfRqstFDD ::= SEQUENCE {
	dl-TFCS											TFCS									OPTIONAL,
 	tFCI-SignallingMode								TFCI-SignallingMode						OPTIONAL,
	limitedPowerIncrease							LimitedPowerIncrease					OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { DL-DPCH-Information-RL-ReconfRqstFDD-ExtIEs} }		OPTIONAL,
	...
 }

DL-DPCH-Information-RL-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DCH-DeleteList-RL-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-DeleteItem-RL-ReconfRqstFDD

DCH-DeleteItem-RL-ReconfRqstFDD ::= SEQUENCE {
	dCH-ID											DCH-ID,
	iE-Extensions									ProtocolExtensionContainer { { DCH-DeleteItem-RL-ReconfRqstFDD-ExtIEs} }			OPTIONAL,
	...

}

DCH-DeleteItem-RL-ReconfRqstFDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-InformationList-RL-ReconfRqstFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container {{ RL-InformationItemIE-RL-ReconfRqstFDD}}

RL-InformationItemIE-RL-ReconfRqstFDD NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-InformationItem-RL-ReconfRqstFDD			CRITICALITY reject		TYPE RL-InformationItem-RL-ReconfRqstFDD		PRESENCE mandatory }
}

RL-InformationItem-RL-ReconfRqstFDD ::= SEQUENCE {
	rL-ID										RL-ID,
	maxDL-Power									DL-Power					OPTIONAL,
	minDL-Power									DL-Power					OPTIONAL,
	dl-CodeInformation							FDD-DL-CodeInformation		OPTIONAL,
	-- The IE shall be present if the Transmission Gap Pattern Sequence Information IE is included and the indicated Downlink Compressed Mode method for at least one of the included Transmission Gap Pattern Sequence is set to "SF/2".
	iE-Extensions								ProtocolExtensionContainer { { RL-InformationItem-RL-ReconfRqstFDD-ExtIEs} }			OPTIONAL,
	...
}

RL-InformationItem-RL-ReconfRqstFDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DLReferencePower					CRITICALITY ignore	EXTENSION DL-Power									PRESENCE optional}|
	{ ID id-RL-Specific-DCH-Info				CRITICALITY ignore	EXTENSION RL-Specific-DCH-Info					PRESENCE optional}|
	{ ID id-E-DCH-RL-Indication					CRITICALITY reject	EXTENSION E-DCH-RL-Indication						PRESENCE optional}|
	{ ID id-RL-Specific-E-DCH-Info				CRITICALITY ignore	EXTENSION RL-Specific-E-DCH-Info					PRESENCE optional}|
	{ ID id-F-DPCH-SlotFormat					CRITICALITY reject	EXTENSION F-DPCH-SlotFormat							PRESENCE optional}|
	{ ID id-HSDSCH-PreconfigurationSetup		CRITICALITY ignore	EXTENSION HSDSCH-PreconfigurationSetup			PRESENCE optional}|
	{ ID id-Non-Serving-RL-Preconfig-Setup		CRITICALITY ignore	EXTENSION Non-Serving-RL-Preconfig-Setup		PRESENCE optional}|
	{ ID id-Non-Serving-RL-Preconfig-Removal	CRITICALITY ignore	EXTENSION Non-Serving-RL-Preconfig-Setup		PRESENCE optional}|
	{ ID id-FTPICH-Information-Reconf			CRITICALITY ignore	EXTENSION FTPICH-Information-Reconf				PRESENCE optional}|
	{ ID id-TPC-slot-position					CRITICALITY ignore	EXTENSION TPC-slot-position							PRESENCE optional},
	...
}

E-DPCH-Information-RL-ReconfRqstFDD ::= SEQUENCE {
	maxSet-E-DPDCHs						Max-Set-E-DPDCHs													OPTIONAL,
	ul-PunctureLimit					PunctureLimit														OPTIONAL,
	e-TFCS-Information					E-TFCS-Information													OPTIONAL,
	e-TTI								E-TTI																OPTIONAL,
	e-DPCCH-PO							E-DPCCH-PO																					OPTIONAL,
	e-RGCH-2-IndexStepThreshold			E-RGCH-2-IndexStepThreshold											OPTIONAL,
	e-RGCH-3-IndexStepThreshold			E-RGCH-3-IndexStepThreshold																	OPTIONAL,
	hARQ-Info-for-E-DCH					HARQ-Info-for-E-DCH													OPTIONAL,
	hSDSCH-Configured-Indicator			HSDSCH-Configured-Indicator											OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { E-DPCH-Information-RL-ReconfRqstFDD-ExtIEs} }			OPTIONAL,
	...
}

E-DPCH-Information-RL-ReconfRqstFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MinimumReducedE-DPDCH-GainFactor		CRITICALITY ignore	EXTENSION MinimumReducedE-DPDCH-GainFactor	PRESENCE optional },
	...
}

-- **************************************************************
--
-- RADIO LINK RECONFIGURATION REQUEST TDD
--
-- **************************************************************

RadioLinkReconfigurationRequestTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkReconfigurationRequestTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkReconfigurationRequestTDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkReconfigurationRequestTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-NodeB-CommunicationContextID						CRITICALITY reject	TYPE NodeB-CommunicationContextID				PRESENCE mandatory }|
	{ ID id-UL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD	CRITICALITY notify	TYPE UL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD		PRESENCE optional } |
	{ ID id-UL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD	CRITICALITY notify	TYPE UL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD		PRESENCE optional } |
	{ ID id-DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD	CRITICALITY notify	TYPE DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD		PRESENCE optional } |
	{ ID id-DL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD	CRITICALITY notify	TYPE DL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD		PRESENCE optional } |
	{ ID id-TDD-DCHs-to-Modify									CRITICALITY reject	TYPE TDD-DCHs-to-Modify					PRESENCE optional }|
	{ ID	id-DCHs-to-Add-TDD									CRITICALITY reject	TYPE DCH-TDD-Information					PRESENCE optional }|
	{ ID id-DCH-DeleteList-RL-ReconfRqstTDD						CRITICALITY reject	TYPE DCH-DeleteList-RL-ReconfRqstTDD			PRESENCE optional }|
	{ ID id-RL-Information-RL-ReconfRqstTDD						CRITICALITY reject	TYPE RL-Information-RL-ReconfRqstTDD			PRESENCE optional },
-- This RL-Information-RL-ReconfRqstTDD is the first RL information repetition in the RL-Information List. Repetition 2 and on, should be defined in Multiple-RL-Information-RL-ReconfRqstTDD,
	...
}

RadioLinkReconfigurationRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-SignallingBearerRequestIndicator			CRITICALITY reject	EXTENSION SignallingBearerRequestIndicator				PRESENCE optional }|
	{ ID id-multiple-RL-Information-RL-ReconfRqstTDD	CRITICALITY reject	EXTENSION Multiple-RL-Information-RL-ReconfRqstTDD	PRESENCE optional }|
--Includes the 2nd through the max number of radio link information repetitions.
	{ ID id-HSDSCH-TDD-Information						CRITICALITY reject	EXTENSION HSDSCH-TDD-Information							PRESENCE optional }|
	{ ID id-HSDSCH-Information-to-Modify-Unsynchronised	CRITICALITY reject	EXTENSION HSDSCH-Information-to-Modify-Unsynchronised	PRESENCE optional }|
	{ ID id-HSDSCH-MACdFlows-to-Add						CRITICALITY reject	EXTENSION HSDSCH-MACdFlows-Information					PRESENCE optional }|
	{ ID id-HSDSCH-MACdFlows-to-Delete					CRITICALITY reject	EXTENSION HSDSCH-MACdFlows-to-Delete						PRESENCE optional }|
	{ ID id-HSDSCH-RNTI									CRITICALITY reject	EXTENSION HSDSCH-RNTI											PRESENCE conditional}|
	-- The IE shall be present if HS-PDSCH RL ID IE is present.
	{ ID id-HSPDSCH-RL-ID								CRITICALITY reject	EXTENSION RL-ID													PRESENCE optional }|
	{ ID id-E-DCH-Information-Reconfig					CRITICALITY reject	EXTENSION E-DCH-Information-Reconfig						PRESENCE optional }|
	{ ID id-E-DCH-Serving-RL-ID							CRITICALITY reject	EXTENSION RL-ID													PRESENCE optional }|
	{ ID id-E-DCH-768-Information-Reconfig				CRITICALITY reject	EXTENSION E-DCH-768-Information-Reconfig				PRESENCE optional }|
	{ ID id-E-DCH-LCR-Information-Reconfig				CRITICALITY reject	EXTENSION E-DCH-LCR-Information-Reconfig				PRESENCE optional }|
	{ ID id-PowerControlGAP								CRITICALITY ignore	EXTENSION ControlGAP											PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-CPC-InformationLCR							CRITICALITY reject	EXTENSION CPC-InformationLCR								PRESENCE optional }|
	{ ID id-IdleIntervalInformation						CRITICALITY ignore	EXTENSION IdleIntervalInformation							PRESENCE optional }|
	{ ID id-UE-Selected-MBMS-Service-Information		CRITICALITY ignore	EXTENSION UE-Selected-MBMS-Service-Information		PRESENCE optional }|
	{ ID id-HSSCCH-TPC-StepSize							CRITICALITY ignore	EXTENSION TDD-TPC-DownlinkStepSize						PRESENCE optional }|
	{ ID id-DCH-MeasurementOccasion-Information			CRITICALITY reject	EXTENSION DCH-MeasurementOccasion-Information			PRESENCE optional }|
	{ ID id-HSDSCH-RNTI-For-FACH						CRITICALITY ignore	EXTENSION HSDSCH-RNTI											PRESENCE optional }|
	{ ID id-Multi-Carrier-EDCH-Reconfigure				CRITICALITY reject	EXTENSION Multi-Carrier-EDCH-Reconfigure				PRESENCE optional }|
	{ ID id-MU-MIMO-InformationLCR						CRITICALITY ignore	EXTENSION MU-MIMO-InformationLCR							PRESENCE optional }|
	{ ID id-MU-MIMO-Information-To-ReconfigureLCR		CRITICALITY ignore	EXTENSION MU-MIMO-Information-To-ReconfigureLCR		PRESENCE optional }|
	{ ID id-UE-Support-of-non-rectangular-resource-allocation	CRITICALITY ignore	EXTENSION UE-Support-of-non-rectangular-resource-allocation			PRESENCE optional},
	...
}

UL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container {{ UL-CCTrCH-InformationModifyItemIE-RL-ReconfRqstTDD}}

UL-CCTrCH-InformationModifyItemIE-RL-ReconfRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD	CRITICALITY notify	TYPE UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD		PRESENCE mandatory}
}

UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD ::= SEQUENCE {
	cCTrCH-ID										CCTrCH-ID,
	tFCS											TFCS			OPTIONAL,
	punctureLimit									PunctureLimit	OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD-ExtIEs} }			OPTIONAL,
	...
}

UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
{ ID id-UL-SIRTarget		CRITICALITY reject		EXTENSION UL-SIR		PRESENCE optional },
	-- Applicable to 1.28Mcps TDD only
	...
}

UL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container {{ UL-CCTrCH-InformationDeleteItemIE-RL-ReconfRqstTDD}}

UL-CCTrCH-InformationDeleteItemIE-RL-ReconfRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD			CRITICALITY notify	TYPE UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD		PRESENCE mandatory }
}

UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD ::= SEQUENCE {
	cCTrCH-ID										CCTrCH-ID,
	iE-Extensions									ProtocolExtensionContainer { { UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD-ExtIEs} }			OPTIONAL,
	...
}

UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container {{ DL-CCTrCH-InformationModifyItemIE-RL-ReconfRqstTDD}}

DL-CCTrCH-InformationModifyItemIE-RL-ReconfRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD		CRITICALITY notify		TYPE DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD	PRESENCE mandatory }
}

DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD ::= SEQUENCE {
	cCTrCH-ID										CCTrCH-ID,
	tFCS											TFCS			OPTIONAL,
	punctureLimit									PunctureLimit	OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD-ExtIEs} }			OPTIONAL,
	...
}

DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-DPCH-LCR-InformationModify-ModifyList-RL-ReconfRqstTDD	CRITICALITY ignore	EXTENSION  DL-DPCH-LCR-InformationModify-ModifyList-RL-ReconfRqstTDD		PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
-- This DPCH LCR Information is the for the first RL repetition, DPCH LCR information for RL repetitions 2 and on, should be defined in MultipleRL-DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD.
	{ ID id-CCTrCH-Maximum-DL-Power-InformationModify-RL-ReconfRqstTDD	CRITICALITY ignore	EXTENSION DL-Power		PRESENCE optional	}|
-- This power Information is the for the first RL repetition, power information for RL repetitions 2 and on, should be defined in MultipleRL-DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD.
	{ ID id-CCTrCH-Minimum-DL-Power-InformationModify-RL-ReconfRqstTDD	CRITICALITY ignore	EXTENSION DL-Power		PRESENCE optional	}|
-- This power Information is the for the first RL repetition, power information for RL repetitions 2 and on, should be defined in MultipleRL-DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD.
	{ ID id-RL-ID														CRITICALITY ignore	EXTENSION RL-ID		PRESENCE optional	}|
-- This is the RL ID for the first RL repetition.
	{ ID id-multipleRL-dl-CCTrCH-InformationModifyList-RL-ReconfRqstTDD	CRITICALITY reject	EXTENSION	MultipleRL-DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD	PRESENCE optional	},
-- This CCTrCH Information is the for the 2nd and beyond RL repetitions.
	...
}

MultipleRL-DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF  MultipleRL-DL-CCTrCH-InformationModifyListIE-RL-ReconfRqstTDD
--Includes the 2nd through the max number of radio link information repetitions.

MultipleRL-DL-CCTrCH-InformationModifyListIE-RL-ReconfRqstTDD ::= SEQUENCE {
	dl-DPCH-LCR-InformationModifyList								DL-DPCH-LCR-InformationModify-ModifyList-RL-ReconfRqstTDD	OPTIONAL,
	cCTrCH-Maximum-DL-Power-InformationModify-RL-ReconfRqstTDD		DL-Power										OPTIONAL,
	cCTrCH-Minimum-DL-Power-InformationModify-RL-ReconfRqstTDD		DL-Power										OPTIONAL,
	rL-ID															RL-ID											OPTIONAL,
	...
}

DL-DPCH-LCR-InformationModify-ModifyList-RL-ReconfRqstTDD ::= SEQUENCE {	
	dL-Timeslot-LCR-InformationModify-ModifyList-RL-ReconfRqstTDD		DL-Timeslot-LCR-InformationModify-ModifyList-RL-ReconfRqstTDD		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-DPCH-LCR-InformationModify-ModifyList-RL-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-DPCH-LCR-InformationModify-ModifyList-RL-ReconfRqstTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Timeslot-LCR-InformationModify-ModifyList-RL-ReconfRqstTDD	::= SEQUENCE (SIZE (1..maxNrOfDLTSLCRs)) OF DL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfRqstTDD	

DL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfRqstTDD	 ::= SEQUENCE {
	timeSlotLCR								TimeSlotLCR,
	maxPowerLCR								DL-Power	OPTIONAL,
	minPowerLCR								DL-Power	OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

DL-Timeslot-LCR-InformationModify-ModifyItem-RL-ReconfRqstTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container {{ DL-CCTrCH-InformationDeleteItemIE-RL-ReconfRqstTDD}}

DL-CCTrCH-InformationDeleteItemIE-RL-ReconfRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD		CRITICALITY notify	TYPE DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD		PRESENCE mandatory }
}

DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD ::= SEQUENCE {
	cCTrCH-ID										CCTrCH-ID,
	iE-Extensions									ProtocolExtensionContainer { { DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD-ExtIEs} }			OPTIONAL,
	...
}

DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DCH-DeleteList-RL-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-DeleteItem-RL-ReconfRqstTDD

DCH-DeleteItem-RL-ReconfRqstTDD ::= SEQUENCE {
	dCH-ID											DCH-ID,
	iE-Extensions									ProtocolExtensionContainer { { DCH-DeleteItem-RL-ReconfRqstTDD-ExtIEs} }			OPTIONAL,
	...
}

DCH-DeleteItem-RL-ReconfRqstTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Multiple-RL-Information-RL-ReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF RL-Information-RL-ReconfRqstTDD
--Includes the 2nd through the max number of radio link information repetitions.

RL-Information-RL-ReconfRqstTDD ::= SEQUENCE {
	rL-ID										RL-ID,
	maxDL-Power									DL-Power		OPTIONAL,
	minDL-Power									DL-Power		OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { RL-InformationItem-RL-ReconfRqstTDD-ExtIEs} }			OPTIONAL,
	...
}

RL-InformationItem-RL-ReconfRqstTDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-RL-Specific-DCH-Info				CRITICALITY	ignore		EXTENSION 	RL-Specific-DCH-Info		PRESENCE optional	}|
	{ ID id-UL-Synchronisation-Parameters-LCR	CRITICALITY	ignore		EXTENSION 	UL-Synchronisation-Parameters-LCR	PRESENCE optional	},
	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD
	...
}

-- **************************************************************
--
-- RADIO LINK RECONFIGURATION RESPONSE
--
-- **************************************************************

RadioLinkReconfigurationResponse ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkReconfigurationResponse-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkReconfigurationResponse-Extensions}}		OPTIONAL,
	...
}

RadioLinkReconfigurationResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CRNC-CommunicationContextID					CRITICALITY	ignore		TYPE	CRNC-CommunicationContextID						PRESENCE	mandatory	} |
	{ ID	id-RL-InformationResponseList-RL-ReconfRsp		CRITICALITY	ignore		TYPE	RL-InformationResponseList-RL-ReconfRsp		PRESENCE	optional	} |
	{ ID	id-CriticalityDiagnostics						CRITICALITY	ignore		TYPE	CriticalityDiagnostics								PRESENCE	optional	},
	...
}

RadioLinkReconfigurationResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TargetCommunicationControlPortID		CRITICALITY ignore	EXTENSION CommunicationControlPortID						PRESENCE optional }|
	{ ID id-HSDSCH-FDD-Information-Response			CRITICALITY ignore	EXTENSION HSDSCH-FDD-Information-Response				PRESENCE optional }|
	-- FDD only
	{ ID id-HSDSCH-TDD-Information-Response			CRITICALITY ignore	EXTENSION HSDSCH-TDD-Information-Response				PRESENCE optional }|
	-- TDD only
	{ ID id-E-DCH-Information-Response				CRITICALITY ignore	EXTENSION E-DCH-Information-Response						PRESENCE optional }|
	{ ID id-MAChs-ResetIndicator					CRITICALITY ignore	EXTENSION MAChs-ResetIndicator								PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivityHS-SCCH-less-Information-Response	CRITICALITY ignore	EXTENSION ContinuousPacketConnectivityHS-SCCH-less-Information-Response	PRESENCE optional }|
	{ ID id-Additional-HS-Cell-Information-Response	CRITICALITY ignore	EXTENSION Additional-HS-Cell-Information-Response-List	PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR	CRITICALITY ignore	EXTENSION ContinuousPacketConnectivity-DRX-Information-ResponseLCR	PRESENCE optional }|
	{ ID id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR	CRITICALITY ignore	EXTENSION HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR	PRESENCE optional }|
	{ ID id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR		CRITICALITY ignore	EXTENSION E-DCH-Semi-PersistentScheduling-Information-ResponseLCR	PRESENCE optional }|
	{ ID id-Additional-EDCH-Cell-Information-ResponseRLReconf	CRITICALITY ignore	EXTENSION Additional-EDCH-Cell-Information-Response-RLReconf-List	PRESENCE optional }|
	{ ID id-E-RNTI-For-FACH							CRITICALITY ignore	EXTENSION E-RNTI												PRESENCE optional }|
	{ ID id-Multi-Carrier-EDCH-Response				CRITICALITY ignore	EXTENSION Multi-Carrier-EDCH-Information-Response		PRESENCE optional }|
	{ ID id-MU-MIMO-Information-Response			CRITICALITY reject	EXTENSION MU-MIMO-Information-Response					PRESENCE optional }|
	{ ID id-Non-rectangular-resource-allocation-indicator		CRITICALITY reject	EXTENSION Non-rectangular-resource-allocation-indicator				PRESENCE optional}|
	{ ID id-Non-rectangular-resource-timeslot-set	CRITICALITY reject	EXTENSION Non-rectangular-resource-timeslot-set		PRESENCE optional},
	...
}

RL-InformationResponseList-RL-ReconfRsp ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container {{RL-InformationResponseItemIE-RL-ReconfRsp}}

RL-InformationResponseItemIE-RL-ReconfRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-InformationResponseItem-RL-ReconfRsp	CRITICALITY ignore	TYPE RL-InformationResponseItem-RL-ReconfRsp	PRESENCE mandatory }
}

RL-InformationResponseItem-RL-ReconfRsp ::= SEQUENCE {
	rL-ID										RL-ID,
	dCH-InformationResponseList-RL-ReconfRsp	DCH-InformationResponseList-RL-ReconfRsp									OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { RL-InformationResponseItem-RL-ReconfRsp-ExtIEs} }		OPTIONAL,
	...
}

RL-InformationResponseItem-RL-ReconfRsp-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DL-PowerBalancing-UpdatedIndicator			CRITICALITY ignore	EXTENSION DL-PowerBalancing-UpdatedIndicator			PRESENCE optional }|
	-- FDD only
	{ ID id-E-DCH-RL-Set-ID								CRITICALITY ignore	EXTENSION RL-Set-ID												PRESENCE optional }|
	{ ID id-E-DCH-FDD-DL-Control-Channel-Information	CRITICALITY ignore	EXTENSION E-DCH-FDD-DL-Control-Channel-Information	PRESENCE optional }|
	{ ID id-E-DCH-FDD-Information-Response				CRITICALITY ignore	EXTENSION E-DCH-FDD-Information-Response				PRESENCE optional }|
	{ ID id-HSDSCH-PreconfigurationInfo					CRITICALITY ignore	EXTENSION HSDSCH-PreconfigurationInfo					PRESENCE optional }|
	{ ID id-Non-Serving-RL-Preconfig-Info				CRITICALITY ignore	EXTENSION Non-Serving-RL-Preconfig-Info					PRESENCE optional },
	...
}

DCH-InformationResponseList-RL-ReconfRsp::= ProtocolIE-Single-Container {{ DCH-InformationResponseListIEs-RL-ReconfRsp }}

DCH-InformationResponseListIEs-RL-ReconfRsp NBAP-PROTOCOL-IES ::= {
	{ ID id-DCH-InformationResponse   CRITICALITY ignore	TYPE DCH-InformationResponse	PRESENCE mandatory }
}

-- **************************************************************
--
-- RADIO LINK DELETION REQUEST
--
-- **************************************************************

RadioLinkDeletionRequest ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkDeletionRequest-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkDeletionRequest-Extensions}}		OPTIONAL,
	...
}

RadioLinkDeletionRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-NodeB-CommunicationContextID					CRITICALITY reject	TYPE NodeB-CommunicationContextID				PRESENCE mandatory }|
	{ ID	id-CRNC-CommunicationContextID					CRITICALITY reject	TYPE CRNC-CommunicationContextID				PRESENCE mandatory }|
	{ ID	id-RL-informationList-RL-DeletionRqst			CRITICALITY notify	TYPE RL-informationList-RL-DeletionRqst		PRESENCE mandatory },
	...
}

RadioLinkDeletionRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-informationList-RL-DeletionRqst ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container {{RL-informationItemIE-RL-DeletionRqst}}

RL-informationItemIE-RL-DeletionRqst NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-informationItem-RL-DeletionRqst		CRITICALITY notify			TYPE RL-informationItem-RL-DeletionRqst	PRESENCE mandatory }
}

RL-informationItem-RL-DeletionRqst ::= SEQUENCE {
 	rL-ID										RL-ID,
	iE-Extensions								ProtocolExtensionContainer { { RL-informationItem-RL-DeletionRqst-ExtIEs} }		OPTIONAL,
	...		
 }

RL-informationItem-RL-DeletionRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK DELETION RESPONSE
--
-- **************************************************************

RadioLinkDeletionResponse ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkDeletionResponse-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkDeletionResponse-Extensions}}		OPTIONAL,
	...
}

RadioLinkDeletionResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CRNC-CommunicationContextID			CRITICALITY ignore	TYPE CRNC-CommunicationContextID				PRESENCE	mandatory	}|
	{ ID	id-CriticalityDiagnostics				CRITICALITY ignore	TYPE CriticalityDiagnostics				PRESENCE	optional	},
	...
}

RadioLinkDeletionResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- DL POWER CONTROL REQUEST FDD
--
-- **************************************************************

DL-PowerControlRequest ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{DL-PowerControlRequest-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{DL-PowerControlRequest-Extensions}}		OPTIONAL,
	...
}

DL-PowerControlRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-NodeB-CommunicationContextID		CRITICALITY	ignore	TYPE NodeB-CommunicationContextID		PRESENCE	mandatory }|
	{ ID id-PowerAdjustmentType					CRITICALITY ignore	TYPE PowerAdjustmentType			PRESENCE mandatory }|
	{ ID id-DLReferencePower					CRITICALITY ignore	TYPE DL-Power						PRESENCE conditional }|
	-- This IE shall be present if the Adjustment Type IE is set to 'Common'
	{ ID id-InnerLoopDLPCStatus					CRITICALITY	ignore	TYPE InnerLoopDLPCStatus			PRESENCE	optional }|
	{ ID id-DLReferencePowerList-DL-PC-Rqst		CRITICALITY ignore	TYPE DL-ReferencePowerInformationList-DL-PC-Rqst	PRESENCE conditional }|
	-- This IE shall be present if the Adjustment Type IE is set to 'Individual'
	{ ID id-MaxAdjustmentStep					CRITICALITY ignore	TYPE MaxAdjustmentStep				PRESENCE conditional }|
	-- This IE shall be present if the Adjustment Type IE is set to 'Common' or 'Individual'
	{ ID id-AdjustmentPeriod					CRITICALITY ignore	TYPE AdjustmentPeriod				PRESENCE conditional }|
	-- This IE shall be present if the Adjustment Type IE is set to 'Common' or 'Individual'
	{ ID id-AdjustmentRatio						CRITICALITY ignore	TYPE ScaledAdjustmentRatio			PRESENCE conditional },
	-- This IE shall be present if the Adjustment Type IE is set to 'Common' or 'Individual'
	...
}

DL-PowerControlRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-ReferencePowerInformationList-DL-PC-Rqst ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container {{DL-ReferencePowerInformationItemIE-DL-PC-Rqst }}

DL-ReferencePowerInformationItemIE-DL-PC-Rqst NBAP-PROTOCOL-IES ::= {
	{ ID id-DL-ReferencePowerInformationItem-DL-PC-Rqst			CRITICALITY ignore			TYPE DL-ReferencePowerInformationItem-DL-PC-Rqst		PRESENCE mandatory }
}

DL-ReferencePowerInformationItem-DL-PC-Rqst ::= SEQUENCE {
	rL-ID									RL-ID,
	dl-ReferencePower						DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { DL-ReferencePowerInformationItem-DL-PC-Rqst-ExtIEs } }		OPTIONAL,
	...		
}

DL-ReferencePowerInformationItem-DL-PC-Rqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- DL POWER TIMESLOT CONTROL REQUEST TDD
--
-- **************************************************************

DL-PowerTimeslotControlRequest ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{DL-PowerTimeslotControlRequest-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{DL-PowerTimeslotControlRequest-Extensions}}		OPTIONAL,
	...
}

DL-PowerTimeslotControlRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-NodeB-CommunicationContextID	CRITICALITY ignore		TYPE NodeB-CommunicationContextID		PRESENCE mandatory } |
	{ ID id-TimeslotISCPInfo				CRITICALITY	ignore		TYPE DL-TimeslotISCPInfo			PRESENCE optional },
	-- Mandatory for 3.84Mcps TDD and 7.68Mcps TDD, Not Applicable to 1.28Mcps TDD
	...
}

DL-PowerTimeslotControlRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TimeslotISCPInfoList-LCR-DL-PC-RqstTDD		CRITICALITY	ignore			EXTENSION	DL-TimeslotISCPInfoLCR		PRESENCE optional }|
	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD
	{ ID id-PrimCCPCH-RSCP-DL-PC-RqstTDD				CRITICALITY ignore			EXTENSION PrimaryCCPCH-RSCP			PRESENCE optional	}|
	{ ID id-PrimaryCCPCH-RSCP-Delta						CRITICALITY	ignore			EXTENSION PrimaryCCPCH-RSCP-Delta		PRESENCE optional	},
	...
}

-- **************************************************************
--
-- DEDICATED MEASUREMENT INITIATION REQUEST
--
-- **************************************************************

DedicatedMeasurementInitiationRequest ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container	{{DedicatedMeasurementInitiationRequest-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{DedicatedMeasurementInitiationRequest-Extensions}}		OPTIONAL,
	...
}

DedicatedMeasurementInitiationRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-NodeB-CommunicationContextID			CRITICALITY reject	TYPE NodeB-CommunicationContextID			PRESENCE mandatory } |
	{ ID id-MeasurementID							CRITICALITY reject	TYPE MeasurementID					PRESENCE mandatory } |
	{ ID id-DedicatedMeasurementObjectType-DM-Rqst	CRITICALITY reject	TYPE DedicatedMeasurementObjectType-DM-Rqst			PRESENCE mandatory } |
	{ ID id-DedicatedMeasurementType				CRITICALITY reject	TYPE DedicatedMeasurementType			PRESENCE mandatory } |
	{ ID id-MeasurementFilterCoefficient			CRITICALITY reject	TYPE MeasurementFilterCoefficient			PRESENCE optional } |
	{ ID id-ReportCharacteristics					CRITICALITY reject	TYPE ReportCharacteristics			PRESENCE mandatory } |
	{ ID id-CFNReportingIndicator					CRITICALITY reject	TYPE FNReportingIndicator			PRESENCE mandatory } |
	{ ID id-CFN										CRITICALITY reject	TYPE CFN							PRESENCE optional } ,
	...
}

DedicatedMeasurementInitiationRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-NumberOfReportedCellPortions			CRITICALITY reject	EXTENSION NumberOfReportedCellPortions			PRESENCE conditional	}|
	-- The IE shall be present if the Dedicated Measurement Type IE is set to ”Best Cell Portions”, FDD only.
	{ ID id-MeasurementRecoveryBehavior				CRITICALITY ignore	EXTENSION MeasurementRecoveryBehavior					PRESENCE optional	}|
	{ ID id-AlternativeFormatReportingIndicator		CRITICALITY ignore	EXTENSION AlternativeFormatReportingIndicator		PRESENCE optional	}|
	{ ID id-NumberOfReportedCellPortionsLCR			CRITICALITY reject	EXTENSION NumberOfReportedCellPortionsLCR			PRESENCE conditional	},
	-- The IE shall be present if the Dedicated Measurement Type IE is set to ”Best Cell Portions LCR”, 1.28Mcps only.
	...
}

DedicatedMeasurementObjectType-DM-Rqst ::= CHOICE {
	rL							RL-DM-Rqst,
	rLS							RL-Set-DM-Rqst, 		-- for FDD only
	all-RL						AllRL-DM-Rqst,
	all-RLS						AllRL-Set-DM-Rqst, 		-- for FDD only
	...
}

RL-DM-Rqst ::= SEQUENCE {
 	rL-InformationList					RL-InformationList-DM-Rqst,
	iE-Extensions						ProtocolExtensionContainer { { RLItem-DM-Rqst-ExtIEs } }		OPTIONAL,
	...		
}

RLItem-DM-Rqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-InformationList-DM-Rqst ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container {{ RL-InformationItemIE-DM-Rqst }}

RL-InformationItemIE-DM-Rqst NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-InformationItem-DM-Rqst   CRITICALITY reject	TYPE RL-InformationItem-DM-Rqst		PRESENCE mandatory }
}

RL-InformationItem-DM-Rqst ::= SEQUENCE {
		rL-ID							RL-ID,	
		dPCH-ID							DPCH-ID				OPTIONAL, -- for TDD only
		iE-Extensions					ProtocolExtensionContainer { { RL-InformationItem-DM-Rqst-ExtIEs } }		OPTIONAL,
		...		
	}

RL-InformationItem-DM-Rqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-PUSCH-Info-DM-Rqst		CRITICALITY reject				EXTENSION	PUSCH-Info-DM-Rqst		PRESENCE optional}|
	-- TDD only
	{ ID id-HSSICH-Info-DM-Rqst		CRITICALITY reject				EXTENSION	HSSICH-Info-DM-Rqst		PRESENCE optional}|
	-- TDD only
	{ ID id-DPCH-ID768-DM-Rqst		CRITICALITY reject				EXTENSION	DPCH-ID768				PRESENCE optional}|
	-- 7.68Mcps TDD only
	{ ID id-HSSICH-InfoExt-DM-Rqst	CRITICALITY reject				EXTENSION	HSSICH-InfoExt-DM-Rqst		PRESENCE optional},
	-- 1.28Mcps TDD only, used if the HS-SICH identity has a value larger than 31
	...
}

PUSCH-Info-DM-Rqst ::= SEQUENCE (SIZE (1..maxNrOfPUSCHs)) OF PUSCH-ID

HSSICH-Info-DM-Rqst ::= SEQUENCE (SIZE (1..maxNrOfHSSICHs)) OF HS-SICH-ID

HSSICH-InfoExt-DM-Rqst::= SEQUENCE (SIZE (1..maxNrOfHSSICHs)) OF Extended-HS-SICH-ID
-- 1.28Mcps TDD only, used if the HS-SICH identity has a value larger than 31

RL-Set-DM-Rqst ::= SEQUENCE {
	rL-Set-InformationList-DM-Rqst			RL-Set-InformationList-DM-Rqst,
	iE-Extensions							ProtocolExtensionContainer { { RL-SetItem-DM-Rqst-ExtIEs } }		OPTIONAL,
	...		
}

RL-SetItem-DM-Rqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-Set-InformationList-DM-Rqst					::= SEQUENCE (SIZE(1..maxNrOfRLSets)) OF RL-Set-InformationItem-DM-Rqst

RL-Set-InformationItem-DM-Rqst ::= SEQUENCE {
	rL-Set-ID						RL-Set-ID,
	iE-Extensions					ProtocolExtensionContainer { { RL-Set-InformationItem-DM-Rqst-ExtIEs} } OPTIONAL,
	...
}

RL-Set-InformationItem-DM-Rqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

AllRL-DM-Rqst ::= NULL

AllRL-Set-DM-Rqst ::= NULL

-- **************************************************************
--
-- DEDICATED MEASUREMENT INITIATION RESPONSE
--
-- **************************************************************

DedicatedMeasurementInitiationResponse ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{DedicatedMeasurementInitiationResponse-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{DedicatedMeasurementInitiationResponse-Extensions}}		OPTIONAL,
	...
}

DedicatedMeasurementInitiationResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID				CRITICALITY ignore	TYPE CRNC-CommunicationContextID		PRESENCE mandatory } |
	{ ID id-MeasurementID							CRITICALITY ignore	TYPE MeasurementID				PRESENCE mandatory } |
	{ ID id-DedicatedMeasurementObjectType-DM-Rsp	CRITICALITY ignore	TYPE DedicatedMeasurementObjectType-DM-Rsp		PRESENCE optional } |
	{ ID id-CriticalityDiagnostics					CRITICALITY ignore	TYPE CriticalityDiagnostics		PRESENCE optional },
	...
}

DedicatedMeasurementInitiationResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MeasurementRecoverySupportIndicator		CRITICALITY ignore	EXTENSION MeasurementRecoverySupportIndicator		PRESENCE optional},
	...
}

DedicatedMeasurementObjectType-DM-Rsp ::= CHOICE {
	rL							RL-DM-Rsp,
	rLS							RL-Set-DM-Rsp, 	-- for FDD only
	all-RL						RL-DM-Rsp,
	all-RLS						RL-Set-DM-Rsp, 	-- for FDD only
	...
}

RL-DM-Rsp ::= SEQUENCE {
	rL-InformationList-DM-Rsp			RL-InformationList-DM-Rsp,
	iE-Extensions						ProtocolExtensionContainer { { RLItem-DM-Rsp-ExtIEs } }		OPTIONAL,
	...
}

RLItem-DM-Rsp-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-InformationList-DM-Rsp ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container {{ RL-InformationItemIE-DM-Rsp }}

RL-InformationItemIE-DM-Rsp NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-InformationItem-DM-Rsp   CRITICALITY ignore	TYPE RL-InformationItem-DM-Rsp		PRESENCE mandatory }
}

RL-InformationItem-DM-Rsp ::= SEQUENCE {
	rL-ID								RL-ID,
	dPCH-ID								DPCH-ID			OPTIONAL, 	-- for TDD only
	dedicatedMeasurementValue			DedicatedMeasurementValue,
	cFN									CFN				OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { RL-InformationItem-DM-Rsp-ExtIEs } }		OPTIONAL,
	...
}

RL-InformationItem-DM-Rsp-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-PUSCH-Info-DM-Rsp		CRITICALITY reject				EXTENSION	PUSCH-Info-DM-Rsp		PRESENCE optional}|
	-- TDD only
	-- This PUSCH Information is the for the first PUSCH repetition, PUSCH information for PUSCH repetitions 2 and on, should be defined in Multiple-PUSCH-InfoList-DM-Rsp.
	{ ID id-HSSICH-Info-DM-Rsp		CRITICALITY reject				EXTENSION	HS-SICH-ID				PRESENCE optional}|
	-- TDD only
	{ ID id-multiple-DedicatedMeasurementValueList-TDD-DM-Rsp	CRITICALITY ignore	EXTENSION Multiple-DedicatedMeasurementValueList-TDD-DM-Rsp	PRESENCE optional	}|
	-- Applicable to 3.84Mcps TDD only. This list of dedicated measurement values is used for the 2nd and beyond measurements of a RL when multiple dedicated measurement values need to be reported.
	{ ID id-multiple-DedicatedMeasurementValueList-LCR-TDD-DM-Rsp	CRITICALITY ignore	EXTENSION Multiple-DedicatedMeasurementValueList-LCR-TDD-DM-Rsp	PRESENCE optional	}|
	-- Applicable to 1.28Mcps TDD only. This list of dedicated measurement values is used for the 2nd and beyond measurements of a RL when multiple dedicated measurement values need to be reported.
	{ ID id-multiple-PUSCH-InfoList-DM-Rsp	CRITICALITY ignore	EXTENSION Multiple-PUSCH-InfoList-DM-Rsp	PRESENCE optional	}|
	-- TDD only, This PUSCH information is the for the 2nd and beyond PUSCH repetitions.
	{ ID id-multiple-HSSICHMeasurementValueList-TDD-DM-Rsp	CRITICALITY ignore	EXTENSION Multiple-HSSICHMeasurementValueList-TDD-DM-Rsp	PRESENCE optional	}|
	-- TDD only. This list of HS-SICH measurement values is used for the 2nd and beyond measurements of a RL when multiple HS-SICH measurement values need to be reported.
	{ ID id-DPCH-ID768-DM-Rsp		CRITICALITY reject				EXTENSION	DPCH-ID768		PRESENCE optional}| 	-- 7.68Mcps TDD only
	{ ID id-multiple-DedicatedMeasurementValueList-768-TDD-DM-Rsp	CRITICALITY ignore	EXTENSION Multiple-DedicatedMeasurementValueList-768-TDD-DM-Rsp	PRESENCE optional	}|
	-- Applicable to 7.68Mcps TDD only. This list of dedicated measurement values is used for the 2nd and beyond measurements of a RL when multiple dedicated measurement values need to be reported.
	{ID id-Extended-HS-SICH-ID		CRITICALITY reject				EXTENSION	Extended-HS-SICH-ID				PRESENCE optional},
	-- 1.28Mcps TDD only, used if the HS-SICH identity has a value larger than 31
	...
}

PUSCH-Info-DM-Rsp ::= SEQUENCE (SIZE (1..maxNrOfPUSCHs)) OF PUSCH-ID

Multiple-PUSCH-InfoList-DM-Rsp ::= SEQUENCE (SIZE (1.. maxNrOfPUSCHs-1)) OF Multiple-PUSCH-InfoListIE-DM-Rsp
-- Includes the 2nd through the max number of PUSCH information repetitions.

Multiple-PUSCH-InfoListIE-DM-Rsp ::= SEQUENCE {
	pUSCH-ID								PUSCH-ID														OPTIONAL,
	dedicatedMeasurementValue				DedicatedMeasurementValue										OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { Multiple-PUSCH-InfoListIE-DM-Rsp-ExtIEs} }		OPTIONAL,
	...
}

Multiple-PUSCH-InfoListIE-DM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Multiple-DedicatedMeasurementValueList-TDD-DM-Rsp ::= SEQUENCE (SIZE (1.. maxNrOfDPCHsPerRL-1)) OF Multiple-DedicatedMeasurementValueItem-TDD-DM-Rsp

Multiple-DedicatedMeasurementValueItem-TDD-DM-Rsp ::= SEQUENCE {
	dPCH-ID								DPCH-ID, 
	dedicatedMeasurementValue			DedicatedMeasurementValue,
	iE-Extensions						ProtocolExtensionContainer { { Multiple-DedicatedMeasurementValueItem-TDD-DM-Rsp-ExtIEs} }		OPTIONAL,
	...
}

Multiple-DedicatedMeasurementValueItem-TDD-DM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Multiple-DedicatedMeasurementValueList-LCR-TDD-DM-Rsp ::= SEQUENCE (SIZE (1.. maxNrOfDPCHsLCRPerRL-1)) OF Multiple-DedicatedMeasurementValueItem-LCR-TDD-DM-Rsp

Multiple-DedicatedMeasurementValueItem-LCR-TDD-DM-Rsp ::= SEQUENCE {
	dPCH-ID								DPCH-ID, 
	dedicatedMeasurementValue			DedicatedMeasurementValue,
	iE-Extensions						ProtocolExtensionContainer { { Multiple-DedicatedMeasurementValueItem-LCR-TDD-DM-Rsp-ExtIEs} }		OPTIONAL,
	...
}

Multiple-DedicatedMeasurementValueItem-LCR-TDD-DM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Multiple-HSSICHMeasurementValueList-TDD-DM-Rsp ::= SEQUENCE (SIZE (1.. maxNrOfHSSICHs-1)) OF Multiple-HSSICHMeasurementValueItem-TDD-DM-Rsp

Multiple-HSSICHMeasurementValueItem-TDD-DM-Rsp ::= SEQUENCE {
	hsSICH-ID							HS-SICH-ID,
	dedicatedMeasurementValue			DedicatedMeasurementValue,
	iE-Extensions						ProtocolExtensionContainer { { Multiple-HSSICHMeasurementValueItem-TDD-DM-Rsp-ExtIEs} }		OPTIONAL,
	...
}

Multiple-HSSICHMeasurementValueItem-TDD-DM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-HS-SICH-ID							CRITICALITY ignore	EXTENSION Extended-HS-SICH-ID	PRESENCE optional},
	 -- 1.28Mcps TDD only, used if the HS-SICH identity has a value larger than 31
	...
}

Multiple-DedicatedMeasurementValueList-768-TDD-DM-Rsp ::= SEQUENCE (SIZE (1.. maxNrOfDPCHs768PerRL-1)) OF Multiple-DedicatedMeasurementValueItem-768-TDD-DM-Rsp

Multiple-DedicatedMeasurementValueItem-768-TDD-DM-Rsp ::= SEQUENCE {
	dPCH-ID768							DPCH-ID768, 
	dedicatedMeasurementValue			DedicatedMeasurementValue,
	iE-Extensions						ProtocolExtensionContainer { { Multiple-DedicatedMeasurementValueItem-768-TDD-DM-Rsp-ExtIEs} }		OPTIONAL,
	...
}

Multiple-DedicatedMeasurementValueItem-768-TDD-DM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-Set-DM-Rsp ::= SEQUENCE {
	rL-Set-InformationList-DM-Rsp		RL-Set-InformationList-DM-Rsp,
	iE-Extensions						ProtocolExtensionContainer { { RL-SetItem-DM-Rsp-ExtIEs } }		OPTIONAL,
	...
}

RL-SetItem-DM-Rsp-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-Set-InformationList-DM-Rsp ::= SEQUENCE (SIZE (1..maxNrOfRLSets)) OF ProtocolIE-Single-Container {{ RL-Set-InformationItemIE-DM-Rsp }}

RL-Set-InformationItemIE-DM-Rsp NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-Set-InformationItem-DM-Rsp		CRITICALITY ignore		TYPE 	RL-Set-InformationItem-DM-Rsp	PRESENCE mandatory}
}

RL-Set-InformationItem-DM-Rsp ::= SEQUENCE {
	rL-Set-ID						RL-Set-ID,
	dedicatedMeasurementValue		DedicatedMeasurementValue,
	cFN								CFN					OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { RL-Set-InformationItem-DM-Rsp-ExtIEs} } OPTIONAL,
	...
}

RL-Set-InformationItem-DM-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- DEDICATED MEASUREMENT INITIATION FAILURE
--
-- **************************************************************

DedicatedMeasurementInitiationFailure ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{DedicatedMeasurementInitiationFailure-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{DedicatedMeasurementInitiationFailure-Extensions}}		OPTIONAL,
	...
}

DedicatedMeasurementInitiationFailure-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CRNC-CommunicationContextID			CRITICALITY		ignore			TYPE	CRNC-CommunicationContextID		PRESENCE	mandatory	} |
	{ ID	id-MeasurementID						CRITICALITY		ignore			TYPE	MeasurementID				PRESENCE	mandatory	} |
	{ ID	id-Cause								CRITICALITY		ignore			TYPE	Cause				PRESENCE	mandatory	} |
	{ ID	id-CriticalityDiagnostics				CRITICALITY		ignore			TYPE	CriticalityDiagnostics				PRESENCE	optional	},
	...
}

DedicatedMeasurementInitiationFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- DEDICATED MEASUREMENT REPORT
--
-- **************************************************************

DedicatedMeasurementReport ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container	{{DedicatedMeasurementReport-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{DedicatedMeasurementReport-Extensions}}		OPTIONAL,
	...
}

DedicatedMeasurementReport-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID				CRITICALITY ignore	TYPE CRNC-CommunicationContextID		PRESENCE	mandatory	} |
	{ ID id-MeasurementID							CRITICALITY ignore	TYPE MeasurementID				PRESENCE	mandatory	} |
	{ ID id-DedicatedMeasurementObjectType-DM-Rprt	CRITICALITY ignore	TYPE DedicatedMeasurementObjectType-DM-Rprt		PRESENCE	mandatory	} ,
	...
}

DedicatedMeasurementReport-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MeasurementRecoveryReportingIndicator	CRITICALITY ignore	EXTENSION	MeasurementRecoveryReportingIndicator		PRESENCE optional	},
	...
}

DedicatedMeasurementObjectType-DM-Rprt ::= CHOICE {
 	rL									RL-DM-Rprt,
	rLS									RL-Set-DM-Rprt, 		-- for FDD only
 	all-RL								RL-DM-Rprt,
	all-RLS								RL-Set-DM-Rprt, 		-- for FDD only
	...
}

RL-DM-Rprt ::= SEQUENCE {
	rL-InformationList-DM-Rprt			RL-InformationList-DM-Rprt,
	iE-Extensions						ProtocolExtensionContainer { { RLItem-DM-Rprt-ExtIEs } }		OPTIONAL,
	...
}

RLItem-DM-Rprt-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-InformationList-DM-Rprt ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container {{ RL-InformationItemIE-DM-Rprt }}

RL-InformationItemIE-DM-Rprt NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-InformationItem-DM-Rprt   CRITICALITY ignore	TYPE RL-InformationItem-DM-Rprt		PRESENCE mandatory }
}

RL-InformationItem-DM-Rprt ::= SEQUENCE {
	rL-ID							RL-ID,
	dPCH-ID							DPCH-ID		OPTIONAL, 		-- for TDD only
	dedicatedMeasurementValueInformation	DedicatedMeasurementValueInformation,
	iE-Extensions					ProtocolExtensionContainer { { RL-InformationItem-DM-Rprt-ExtIEs } }		OPTIONAL,
	...
}

RL-InformationItem-DM-Rprt-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-PUSCH-Info-DM-Rprt		CRITICALITY reject				EXTENSION	PUSCH-Info-DM-Rprt		PRESENCE optional}|
	-- TDD only
	-- This PUSCH Information is the for the first PUSCH repetition, PUSCH information for PUSCH repetitions 2 and on, should be defined in Multiple-PUSCH-InfoList-DM-Rprt.
	{ID id-HSSICH-Info-DM-Rprt		CRITICALITY reject				EXTENSION	HS-SICH-ID				PRESENCE optional}|
	-- TDD only
	{ ID id-multiple-PUSCH-InfoList-DM-Rprt	CRITICALITY ignore		EXTENSION Multiple-PUSCH-InfoList-DM-Rprt		PRESENCE optional	}|
	-- TDD only, This PUSCH information is the for the 2nd and beyond PUSCH repetitions.
	{ ID id-DPCH-ID768-DM-Rprt		CRITICALITY reject				EXTENSION	DPCH-ID768				PRESENCE optional}|
	-- 7.68Mcps TDD only
	{ ID id-Extended-HS-SICH-ID		CRITICALITY ignore				EXTENSION Extended-HS-SICH-ID		PRESENCE optional},
	-- 1.28Mcps TDD only, used if the HS-SICH identity has a value larger than 31
	...
}

PUSCH-Info-DM-Rprt ::= SEQUENCE (SIZE (0..maxNrOfPUSCHs)) OF PUSCH-ID

Multiple-PUSCH-InfoList-DM-Rprt ::= SEQUENCE (SIZE (1.. maxNrOfPUSCHs-1)) OF Multiple-PUSCH-InfoListIE-DM-Rprt
-- Includes the 2nd through the max number of PUSCH information repetitions.

Multiple-PUSCH-InfoListIE-DM-Rprt ::= SEQUENCE {
	pUSCH-ID								PUSCH-ID														OPTIONAL,
	dedicatedMeasurementValue				DedicatedMeasurementValue										OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { Multiple-PUSCH-InfoListIE-DM-Rprt-ExtIEs} }		OPTIONAL,
	...
}

Multiple-PUSCH-InfoListIE-DM-Rprt-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-Set-DM-Rprt ::= SEQUENCE {
	rL-Set-InformationList-DM-Rprt		RL-Set-InformationList-DM-Rprt,
	iE-Extensions						ProtocolExtensionContainer { { RL-SetItem-DM-Rprt-ExtIEs } }		OPTIONAL,
	...
}

RL-SetItem-DM-Rprt-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-Set-InformationList-DM-Rprt ::= SEQUENCE (SIZE (1..maxNrOfRLSets)) OF ProtocolIE-Single-Container {{ RL-Set-InformationItemIE-DM-Rprt }}

RL-Set-InformationItemIE-DM-Rprt NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-Set-InformationItem-DM-Rprt	CRITICALITY ignore	TYPE RL-Set-InformationItem-DM-Rprt		PRESENCE mandatory	}
}

RL-Set-InformationItem-DM-Rprt ::= SEQUENCE {
	rL-Set-ID						RL-Set-ID,
	dedicatedMeasurementValueInformation	DedicatedMeasurementValueInformation,
	iE-Extensions					ProtocolExtensionContainer { { RL-Set-InformationItem-DM-Rprt-ExtIEs} } OPTIONAL,
	...
}

RL-Set-InformationItem-DM-Rprt-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- DEDICATED MEASUREMENT TERMINATION REQUEST
--
-- **************************************************************

DedicatedMeasurementTerminationRequest ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{DedicatedMeasurementTerminationRequest-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{DedicatedMeasurementTerminationRequest-Extensions}}		OPTIONAL,
	...
}

DedicatedMeasurementTerminationRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-NodeB-CommunicationContextID			CRITICALITY		ignore			TYPE	NodeB-CommunicationContextID		PRESENCE	mandatory	} |
	{ ID	id-MeasurementID						CRITICALITY		ignore			TYPE	MeasurementID				PRESENCE	mandatory	},
	...
}

DedicatedMeasurementTerminationRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- DEDICATED MEASUREMENT FAILURE INDICATION
--
-- **************************************************************

DedicatedMeasurementFailureIndication ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{DedicatedMeasurementFailureIndication-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{DedicatedMeasurementFailureIndication-Extensions}}		OPTIONAL,
	...
}

DedicatedMeasurementFailureIndication-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CRNC-CommunicationContextID		CRITICALITY		ignore		TYPE	CRNC-CommunicationContextID		PRESENCE	mandatory	} |
	{ ID	id-MeasurementID					CRITICALITY		ignore		TYPE	MeasurementID		PRESENCE	mandatory	} |
	{ ID	id-Cause							CRITICALITY		ignore		TYPE	Cause				PRESENCE	mandatory	},
	...
}

DedicatedMeasurementFailureIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK FAILURE INDICATION
--
-- **************************************************************

RadioLinkFailureIndication ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkFailureIndication-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkFailureIndication-Extensions}}		OPTIONAL,
	...
}

RadioLinkFailureIndication-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CRNC-CommunicationContextID				CRITICALITY ignore			TYPE CRNC-CommunicationContextID			PRESENCE	mandatory	} |
	{ ID	id-Reporting-Object-RL-FailureInd			CRITICALITY ignore			TYPE Reporting-Object-RL-FailureInd		PRESENCE	mandatory	} ,
	...
}

RadioLinkFailureIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Reporting-Object-RL-FailureInd ::= CHOICE {
	rL						RL-RL-FailureInd,
	rL-Set					RL-Set-RL-FailureInd, --FDD only
	...,
	cCTrCH					CCTrCH-RL-FailureInd --TDD only
}

RL-RL-FailureInd ::= SEQUENCE {
	rL-InformationList-RL-FailureInd		RL-InformationList-RL-FailureInd,
	iE-Extensions							ProtocolExtensionContainer { { RLItem-RL-FailureInd-ExtIEs } }		OPTIONAL,
	...
}

RLItem-RL-FailureInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-InformationList-RL-FailureInd ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container {{ RL-InformationItemIE-RL-FailureInd}}

RL-InformationItemIE-RL-FailureInd NBAP-PROTOCOL-IES ::= {
 	{ ID id-RL-InformationItem-RL-FailureInd			CRITICALITY ignore			TYPE RL-InformationItem-RL-FailureInd			PRESENCE mandatory }
}

RL-InformationItem-RL-FailureInd ::= SEQUENCE {
 	rL-ID										RL-ID,
 	cause										Cause,
	iE-Extensions								ProtocolExtensionContainer { { RL-InformationItem-RL-FailureInd-ExtIEs } }		OPTIONAL,
	...
}

RL-InformationItem-RL-FailureInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-Set-RL-FailureInd ::= SEQUENCE {
	rL-Set-InformationList-RL-FailureInd	RL-Set-InformationList-RL-FailureInd,
	iE-Extensions							ProtocolExtensionContainer { { RL-SetItem-RL-FailureInd-ExtIEs } }		OPTIONAL,
	...
}

RL-SetItem-RL-FailureInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-Set-InformationList-RL-FailureInd ::= SEQUENCE (SIZE (1..maxNrOfRLSets)) OF ProtocolIE-Single-Container {{ RL-Set-InformationItemIE-RL-FailureInd }}

RL-Set-InformationItemIE-RL-FailureInd NBAP-PROTOCOL-IES ::= {
 	{ ID id-RL-Set-InformationItem-RL-FailureInd	CRITICALITY ignore		TYPE RL-Set-InformationItem-RL-FailureInd		PRESENCE mandatory	}
}

RL-Set-InformationItem-RL-FailureInd ::= SEQUENCE {
 	rL-Set-ID				RL-Set-ID,
 	cause					Cause,
	iE-Extensions			ProtocolExtensionContainer { { RL-Set-InformationItem-RL-FailureInd-ExtIEs} } OPTIONAL,
	...
}

RL-Set-InformationItem-RL-FailureInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CCTrCH-RL-FailureInd ::= SEQUENCE {
	rL-ID									RL-ID,
	cCTrCH-InformationList-RL-FailureInd	CCTrCH-InformationList-RL-FailureInd,
	iE-Extensions							ProtocolExtensionContainer { { CCTrCHItem-RL-FailureInd-ExtIEs } }		OPTIONAL,
	...
}

CCTrCHItem-RL-FailureInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CCTrCH-InformationList-RL-FailureInd ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container {{ CCTrCH-InformationItemIE-RL-FailureInd}}

CCTrCH-InformationItemIE-RL-FailureInd NBAP-PROTOCOL-IES ::= {
 	{ ID id-CCTrCH-InformationItem-RL-FailureInd		CRITICALITY ignore		TYPE CCTrCH-InformationItem-RL-FailureInd			PRESENCE mandatory }
}

CCTrCH-InformationItem-RL-FailureInd ::= SEQUENCE {
 	cCTrCH-ID									CCTrCH-ID,
	cause										Cause,
	iE-Extensions								ProtocolExtensionContainer { { CCTrCH-InformationItem-RL-FailureInd-ExtIEs } }		OPTIONAL,
	...
}

CCTrCH-InformationItem-RL-FailureInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK PREEMPTION REQUIRED INDICATION
--
-- **************************************************************

RadioLinkPreemptionRequiredIndication ::= SEQUENCE {
	protocolIEs                     ProtocolIE-Container       {{RadioLinkPreemptionRequiredIndication-IEs}},
	protocolExtensions              ProtocolExtensionContainer {{RadioLinkPreemptionRequiredIndication-Extensions}}                   OPTIONAL,
	...
}

RadioLinkPreemptionRequiredIndication-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID					CRITICALITY ignore	TYPE CRNC-CommunicationContextID				PRESENCE mandatory } |
	{ ID id-RL-InformationList-RL-PreemptRequiredInd	CRITICALITY ignore	TYPE RL-InformationList-RL-PreemptRequiredInd		PRESENCE optional	},
	...
}

RadioLinkPreemptionRequiredIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-InformationList-RL-PreemptRequiredInd ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-InformationItemIE-RL-PreemptRequiredInd}}

RL-InformationItemIE-RL-PreemptRequiredInd NBAP-PROTOCOL-IES ::= {
	{ ID id-RL-InformationItem-RL-PreemptRequiredInd	CRITICALITY ignore	TYPE RL-InformationItem-RL-PreemptRequiredInd		PRESENCE mandatory },
	...
}

RL-InformationItem-RL-PreemptRequiredInd::= SEQUENCE {
	rL-ID						RL-ID,
	iE-Extensions				ProtocolExtensionContainer { {RL-InformationItem-RL-PreemptRequiredInd-ExtIEs} } OPTIONAL,
	...
}

RL-InformationItem-RL-PreemptRequiredInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK RESTORE INDICATION
--
-- **************************************************************

RadioLinkRestoreIndication ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkRestoreIndication-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkRestoreIndication-Extensions}}		OPTIONAL,
	...
}

RadioLinkRestoreIndication-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CRNC-CommunicationContextID			CRITICALITY ignore	TYPE CRNC-CommunicationContextID		PRESENCE	mandatory	} |
	{ ID	id-Reporting-Object-RL-RestoreInd		CRITICALITY ignore	TYPE Reporting-Object-RL-RestoreInd		PRESENCE	mandatory	},
	...
}

RadioLinkRestoreIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Reporting-Object-RL-RestoreInd ::= CHOICE {
	rL						RL-RL-RestoreInd, --TDD only
	rL-Set					RL-Set-RL-RestoreInd, --FDD only
	...,
	cCTrCH					CCTrCH-RL-RestoreInd --TDD only
}

RL-RL-RestoreInd ::= SEQUENCE {
	rL-InformationList-RL-RestoreInd		RL-InformationList-RL-RestoreInd,
	iE-Extensions							ProtocolExtensionContainer { { RLItem-RL-RestoreInd-ExtIEs } }		OPTIONAL,
	...
}

RLItem-RL-RestoreInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-InformationList-RL-RestoreInd ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container {{RL-InformationItemIE-RL-RestoreInd}}

RL-InformationItemIE-RL-RestoreInd NBAP-PROTOCOL-IES ::= {
 	{ ID	id-RL-InformationItem-RL-RestoreInd		CRITICALITY ignore		TYPE	RL-InformationItem-RL-RestoreInd			PRESENCE	mandatory}
}

RL-InformationItem-RL-RestoreInd ::= SEQUENCE {
 	rL-ID									RL-ID,
	iE-Extensions							ProtocolExtensionContainer { { RL-InformationItem-RL-RestoreInd-ExtIEs } }		OPTIONAL,
	...
}

RL-InformationItem-RL-RestoreInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-Set-RL-RestoreInd ::= SEQUENCE {
	rL-Set-InformationList-RL-RestoreInd	RL-Set-InformationList-RL-RestoreInd,
	iE-Extensions							ProtocolExtensionContainer { { RL-SetItem-RL-RestoreInd-ExtIEs } }		OPTIONAL,
	...
}

RL-SetItem-RL-RestoreInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-Set-InformationList-RL-RestoreInd ::= SEQUENCE (SIZE (1..maxNrOfRLSets)) OF ProtocolIE-Single-Container {{ RL-Set-InformationItemIE-RL-RestoreInd }}

RL-Set-InformationItemIE-RL-RestoreInd NBAP-PROTOCOL-IES ::= {
 	{ ID id-RL-Set-InformationItem-RL-RestoreInd	CRITICALITY ignore		TYPE RL-Set-InformationItem-RL-RestoreInd	PRESENCE mandatory	}
}

RL-Set-InformationItem-RL-RestoreInd ::= SEQUENCE {
 	rL-Set-ID				RL-Set-ID,
 	iE-Extensions			ProtocolExtensionContainer { { RL-Set-InformationItem-RL-RestoreInd-ExtIEs} } OPTIONAL,
	...
}

RL-Set-InformationItem-RL-RestoreInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CCTrCH-RL-RestoreInd ::= SEQUENCE {
	rL-ID									RL-ID,
	cCTrCH-InformationList-RL-RestoreInd	CCTrCH-InformationList-RL-RestoreInd,
	iE-Extensions							ProtocolExtensionContainer { { CCTrCHItem-RL-RestoreInd-ExtIEs } }		OPTIONAL,
	...
}

CCTrCHItem-RL-RestoreInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CCTrCH-InformationList-RL-RestoreInd ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container {{ CCTrCH-InformationItemIE-RL-RestoreInd}}

CCTrCH-InformationItemIE-RL-RestoreInd NBAP-PROTOCOL-IES ::= {
	{ ID id-CCTrCH-InformationItem-RL-RestoreInd	CRITICALITY ignore	TYPE CCTrCH-InformationItem-RL-RestoreInd		PRESENCE	mandatory }
}

CCTrCH-InformationItem-RL-RestoreInd ::= SEQUENCE {
	cCTrCH-ID									CCTrCH-ID,
	iE-Extensions								ProtocolExtensionContainer { { CCTrCH-InformationItem-RL-RestoreInd-ExtIEs } }		OPTIONAL,
	...
}

CCTrCH-InformationItem-RL-RestoreInd-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- COMPRESSED MODE COMMAND FDD
--
-- **************************************************************

CompressedModeCommand ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CompressedModeCommand-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CompressedModeCommand-Extensions}}                   OPTIONAL,
	...
}

CompressedModeCommand-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-NodeB-CommunicationContextID			CRITICALITY ignore		TYPE NodeB-CommunicationContextID			PRESENCE mandatory } |
	{ ID id-Active-Pattern-Sequence-Information		CRITICALITY ignore		TYPE Active-Pattern-Sequence-Information		PRESENCE mandatory },
	...
}

CompressedModeCommand-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- ERROR INDICATION
--
-- **************************************************************

ErrorIndication ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{ErrorIndication-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{ErrorIndication-Extensions}}		OPTIONAL,
	...
}

ErrorIndication-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CRNC-CommunicationContextID		CRITICALITY		ignore			TYPE 	CRNC-CommunicationContextID			PRESENCE	optional	} |
	{ ID	id-NodeB-CommunicationContextID		CRITICALITY		ignore			TYPE 	NodeB-CommunicationContextID		PRESENCE	optional	} |
	{ ID	id-Cause							CRITICALITY		ignore			TYPE	Cause				PRESENCE	optional	} |
	{ ID	id-CriticalityDiagnostics			CRITICALITY		ignore			TYPE	CriticalityDiagnostics			PRESENCE	optional	},
	...
}

ErrorIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- PRIVATE MESSAGE
--
-- **************************************************************

PrivateMessage ::= SEQUENCE {
	privateIEs		PrivateIE-Container	{{PrivateMessage-IEs}},
	...
}

PrivateMessage-IEs NBAP-PRIVATE-IES ::= {
	...
}

-- **************************************************************
--
-- PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST FDD
--
-- **************************************************************

PhysicalSharedChannelReconfigurationRequestFDD ::= SEQUENCE {
	protocolIEs			ProtocolIE-Container		{{PhysicalSharedChannelReconfigurationRequestFDD-IEs}},
	protocolExtensions	ProtocolExtensionContainer	{{PhysicalSharedChannelReconfigurationRequestFDD-Extensions}}	OPTIONAL,
	...
}

PhysicalSharedChannelReconfigurationRequestFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-C-ID											CRITICALITY reject	TYPE C-ID							PRESENCE mandatory }|
	{ ID id-ConfigurationGenerationID						CRITICALITY reject	TYPE ConfigurationGenerationID					PRESENCE mandatory }|
	{ ID id-SFN												CRITICALITY reject	TYPE SFN							PRESENCE optional }|
	{ ID id-HS-PDSCH-HS-SCCH-E-AGCH-E-RGCH-E-HICH-MaxPower-PSCH-ReconfRqst		CRITICALITY reject	TYPE MaximumTransmissionPower					PRESENCE optional }|
	{ ID id-HS-PDSCH-HS-SCCH-ScramblingCode-PSCH-ReconfRqst	CRITICALITY reject	TYPE DL-ScramblingCode					PRESENCE optional }|
	{ ID id-HS-PDSCH-FDD-Code-Information-PSCH-ReconfRqst	CRITICALITY reject	TYPE HS-PDSCH-FDD-Code-Information					PRESENCE optional }|
	{ ID id-HS-SCCH-FDD-Code-Information-PSCH-ReconfRqst	CRITICALITY reject	TYPE HS-SCCH-FDD-Code-Information					PRESENCE optional },
	...
}

PhysicalSharedChannelReconfigurationRequestFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-AGCH-And-E-RGCH-E-HICH-FDD-Scrambling-Code			CRITICALITY reject	EXTENSION DL-ScramblingCode										PRESENCE optional }|
	{ ID id-E-AGCH-FDD-Code-Information								CRITICALITY reject	EXTENSION E-AGCH-FDD-Code-Information								PRESENCE optional }|
	{ ID id-E-RGCH-E-HICH-FDD-Code-Information						CRITICALITY reject	EXTENSION E-RGCH-E-HICH-FDD-Code-Information					PRESENCE optional }|
	{ID id-HSDPA-And-EDCH-CellPortion-Information-PSCH-ReconfRqst	CRITICALITY reject	EXTENSION HSDPA-And-EDCH-CellPortion-InformationList-PSCH-ReconfRqst		PRESENCE optional }|
	{ID id-Maximum-Target-ReceivedTotalWideBandPower				CRITICALITY reject	EXTENSION Maximum-Target-ReceivedTotalWideBandPower			PRESENCE optional }|
	{ID id-Reference-ReceivedTotalWideBandPower						CRITICALITY ignore	EXTENSION Reference-ReceivedTotalWideBandPower						 PRESENCE optional }|
	{ID id-Target-NonServing-EDCH-To-Total-EDCH-Power-Ratio			CRITICALITY	reject	EXTENSION Target-NonServing-EDCH-To-Total-EDCH-Power-Ratio		PRESENCE optional }|
	{ ID id-HSDSCH-Common-System-InformationFDD						CRITICALITY reject	EXTENSION HSDSCH-Common-System-InformationFDD				PRESENCE optional }|
	{ ID id-Common-MACFlows-to-DeleteFDD							CRITICALITY reject	EXTENSION Common-MACFlows-to-DeleteFDD									PRESENCE optional }|
	{ ID id-HSDSCH-Paging-System-InformationFDD						CRITICALITY reject	EXTENSION HSDSCH-Paging-System-InformationFDD						PRESENCE optional }|
	{ ID id-Paging-MACFlows-to-DeleteFDD							CRITICALITY reject	EXTENSION Paging-MACFlows-to-DeleteFDD									PRESENCE optional }|
	{ ID id-Common-EDCH-System-InformationFDD						CRITICALITY reject	EXTENSION Common-EDCH-System-InformationFDD							PRESENCE optional }|
	{ ID id-Common-UL-MACFlows-to-DeleteFDD							CRITICALITY reject	EXTENSION Common-MACFlows-to-DeleteFDD									PRESENCE optional }|
	{ ID id-Common-EDCH-MACdFlows-to-DeleteFDD						CRITICALITY reject	EXTENSION E-DCH-MACdFlows-to-Delete										PRESENCE optional }|
	{ ID id-Enhanced-UE-DRX-InformationFDD							CRITICALITY reject	EXTENSION Enhanced-UE-DRX-InformationFDD								PRESENCE optional }|
	{ ID id-Further-Enhanced-UE-DRX-InformationFDD					CRITICALITY ignore	EXTENSION Further-Enhanced-UE-DRX-InformationFDD						PRESENCE optional }|
	{ ID id-Common-E-RGCH-Operation-Indicator						CRITICALITY ignore	EXTENSION Common-E-RGCH-Operation-Indicator							PRESENCE optional },
	...
}

HSDPA-And-EDCH-CellPortion-InformationList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCell)) OF HSDPA-And-EDCH-CellPortion-InformationItem-PSCH-ReconfRqst

HSDPA-And-EDCH-CellPortion-InformationItem-PSCH-ReconfRqst::= SEQUENCE {
	cellPortionID														CellPortionID,
	hS-PDSCH-HS-SCCH-ScramblingCode-PSCH-ReconfRqst						DL-ScramblingCode				OPTIONAL,
	hS-PDSCH-FDD-Code-Information-PSCH-ReconfRqst						HS-PDSCH-FDD-Code-Information		OPTIONAL,
	hS-SCCH-FDD-Code-Information-PSCH-ReconfRqst						HS-SCCH-FDD-Code-Information		OPTIONAL,
	hS-PDSCH-HS-SCCH-E-AGCH-E-RGCH-E-HICH-MaxPower-PSCH-ReconfRqst		MaximumTransmissionPower		OPTIONAL,
	e-AGCH-And-E-RGCH-E-HICH-FDD-Scrambling-Code						DL-ScramblingCode				OPTIONAL,
	e-AGCH-FDD-Code-Information											E-AGCH-FDD-Code-Information		OPTIONAL,
	e-RGCH-E-HICH-FDD-Code-Information									E-RGCH-E-HICH-FDD-Code-Information		OPTIONAL,
	iE-Extensions														ProtocolExtensionContainer { { HSDPA-And-EDCH-CellPortion-InformationItem-PSCH-ReconfRqst-ExtIEs} }	OPTIONAL,
	...
}

HSDPA-And-EDCH-CellPortion-InformationItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-Maximum-Target-ReceivedTotalWideBandPower	CRITICALITY ignore	EXTENSION Maximum-Target-ReceivedTotalWideBandPower	PRESENCE optional }|
	{ID id-Reference-ReceivedTotalWideBandPower			CRITICALITY ignore	EXTENSION Reference-ReceivedTotalWideBandPower	PRESENCE optional },
...
}

-- **************************************************************
--
-- PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST TDD
--
-- **************************************************************

PhysicalSharedChannelReconfigurationRequestTDD ::= SEQUENCE {
	protocolIEs			ProtocolIE-Container		{{PhysicalSharedChannelReconfigurationRequestTDD-IEs}},
	protocolExtensions	ProtocolExtensionContainer	{{PhysicalSharedChannelReconfigurationRequestTDD-Extensions}}	OPTIONAL,
	...
}

PhysicalSharedChannelReconfigurationRequestTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-C-ID									CRITICALITY reject	TYPE C-ID						PRESENCE mandatory }|
	{ ID id-SFN										CRITICALITY reject	TYPE SFN						PRESENCE optional }|
	{ ID id-PDSCHSets-AddList-PSCH-ReconfRqst		CRITICALITY reject	TYPE PDSCHSets-AddList-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-PDSCHSets-ModifyList-PSCH-ReconfRqst	CRITICALITY reject	TYPE PDSCHSets-ModifyList-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-PDSCHSets-DeleteList-PSCH-ReconfRqst	CRITICALITY reject	TYPE PDSCHSets-DeleteList-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-PUSCHSets-AddList-PSCH-ReconfRqst		CRITICALITY reject	TYPE PUSCHSets-AddList-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-PUSCHSets-ModifyList-PSCH-ReconfRqst	CRITICALITY reject	TYPE PUSCHSets-ModifyList-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-PUSCHSets-DeleteList-PSCH-ReconfRqst	CRITICALITY reject	TYPE PUSCHSets-DeleteList-PSCH-ReconfRqst		PRESENCE optional },
	...
}

PhysicalSharedChannelReconfigurationRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-HS-PDSCH-TDD-Information-PSCH-ReconfRqst			CRITICALITY reject	EXTENSION HS-PDSCH-TDD-Information-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-Add-To-HS-SCCH-Resource-Pool-PSCH-ReconfRqst		CRITICALITY reject	EXTENSION Add-To-HS-SCCH-Resource-Pool-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-Modify-HS-SCCH-Resource-Pool-PSCH-ReconfRqst		CRITICALITY reject	EXTENSION Modify-HS-SCCH-Resource-Pool-PSCH-ReconfRqst		PRESENCE optional }|
{ ID id-Delete-From-HS-SCCH-Resource-Pool-PSCH-ReconfRqst	CRITICALITY reject	EXTENSION Delete-From-HS-SCCH-Resource-Pool-PSCH-ReconfRqst	PRESENCE optional }|
	{ ID id-ConfigurationGenerationID							CRITICALITY reject	EXTENSION ConfigurationGenerationID		PRESENCE optional }|
	{ ID id-E-PUCH-Information-PSCH-ReconfRqst					CRITICALITY reject	EXTENSION E-PUCH-Information-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-Add-To-E-AGCH-Resource-Pool-PSCH-ReconfRqst			CRITICALITY reject	EXTENSION Add-To-E-AGCH-Resource-Pool-PSCH-ReconfRqst	PRESENCE optional }|
	{ ID id-Modify-E-AGCH-Resource-Pool-PSCH-ReconfRqst			CRITICALITY reject	EXTENSION Modify-E-AGCH-Resource-Pool-PSCH-ReconfRqst	PRESENCE optional }|
	{ ID id-Delete-From-E-AGCH-Resource-Pool-PSCH-ReconfRqst	CRITICALITY reject	EXTENSION Delete-From-E-AGCH-Resource-Pool-PSCH-ReconfRqst	PRESENCE optional }|
	{ ID id-E-HICH-Information-PSCH-ReconfRqst					CRITICALITY reject	EXTENSION E-HICH-Information-PSCH-ReconfRqst	PRESENCE optional }|
	{ ID id-Maximum-Generated-ReceivedTotalWideBandPowerInOtherCells	CRITICALITY reject	EXTENSION Maximum-Generated-ReceivedTotalWideBandPowerInOtherCells	PRESENCE optional }|-- Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
	{ ID id-E-PUCH-Information-768-PSCH-ReconfRqst				CRITICALITY reject	EXTENSION E-PUCH-Information-768-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-Add-To-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst		CRITICALITY reject	EXTENSION Add-To-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst	PRESENCE optional }|
	{ ID id-Modify-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst		CRITICALITY reject	EXTENSION Modify-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst	PRESENCE optional }|
	{ ID id-E-HICH-Information-768-PSCH-ReconfRqst				CRITICALITY reject	EXTENSION E-HICH-Information-768-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-E-PUCH-Information-LCR-PSCH-ReconfRqst				CRITICALITY reject	EXTENSION E-PUCH-Information-LCR-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-Add-To-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst		CRITICALITY reject	EXTENSION Add-To-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst	PRESENCE optional }|
	{ ID id-Modify-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst		CRITICALITY reject	EXTENSION Modify-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst	PRESENCE optional }|
	{ ID id-Add-To-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst		CRITICALITY reject	EXTENSION Add-To-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-Modify-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst		CRITICALITY reject	EXTENSION Modify-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-Delete-From-E-HICH-Resource-Pool-PSCH-ReconfRqst	CRITICALITY reject	EXTENSION Delete-From-E-HICH-Resource-Pool-PSCH-ReconfRqst	PRESENCE optional }|
	{ ID id-SYNC-UL-Partition-LCR								CRITICALITY reject	EXTENSION SYNC-UL-Partition-LCR				PRESENCE optional }|
	 -- Applicable to 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
	{ ID id-Maximum-Target-ReceivedTotalWideBandPower-LCR		CRITICALITY reject	EXTENSION Maximum-Target-ReceivedTotalWideBandPower-LCR		PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only.
	{ ID id-Delete-From-HS-SCCH-Resource-PoolExt-PSCH-ReconfRqst	CRITICALITY reject	EXTENSION Delete-From-HS-SCCH-Resource-PoolExt-PSCH-ReconfRqst	PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only, used when there are more than maxNrOfHSSCCHs HS-SCCHs in the message.
	{ ID id-HSDSCH-Common-System-InformationLCR					CRITICALITY reject	EXTENSION HSDSCH-Common-System-InformationLCR	PRESENCE optional }|
	{ ID id-Common-MACFlows-to-DeleteLCR						CRITICALITY reject	EXTENSION Common-MACFlows-to-DeleteLCR		PRESENCE optional }|
	{ ID id-HSDSCH-Paging-System-InformationLCR					CRITICALITY reject	EXTENSION HSDSCH-Paging-System-InformationLCR	PRESENCE optional }|
	{ ID id-Paging-MACFlows-to-DeleteLCR						CRITICALITY reject	EXTENSION Paging-MACFlows-to-DeleteLCR		PRESENCE optional }|
	{ ID id-Common-EDCH-System-InformationLCR					CRITICALITY reject	EXTENSION Common-EDCH-System-InformationLCR		PRESENCE optional }|
	{ ID id-Common-UL-MACFlows-to-DeleteLCR						CRITICALITY reject	EXTENSION Common-MACFlows-to-DeleteLCR		PRESENCE optional }|
	{ ID id-Common-EDCH-MACdFlows-to-DeleteLCR					CRITICALITY reject	EXTENSION E-DCH-MACdFlows-to-DeleteLCR		PRESENCE optional }|
	{ ID id-Enhanced-UE-DRX-InformationLCR						CRITICALITY reject	EXTENSION Enhanced-UE-DRX-InformationLCR		PRESENCE optional }|
	{ ID id-Add-To-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst		CRITICALITY reject	EXTENSION Add-To-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst	PRESENCE optional }|
	{ ID id-Modify-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst		CRITICALITY reject	EXTENSION Modify-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst	PRESENCE optional }|
	{ ID	id-Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst		CRITICALITY reject	EXTENSION Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst	PRESENCE optional }|
	{ ID id-PowerControlGAP-For-CellFACHLCR						CRITICALITY ignore	EXTENSION ControlGAP								PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-Max-RTWP-perUARFCN-Information-LCR-PSCH-ReconfRqst	CRITICALITY ignore	EXTENSION Max-RTWP-perUARFCN-Information-LCR-PSCH-ReconfRqst		PRESENCE optional }|
	{ ID id-Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext CRITICALITY reject	EXTENSION Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext	PRESENCE optional }|
	{ ID id-Out-of-Sychronization-Window						CRITICALITY reject	EXTENSION Out-of-Sychronization-Window	PRESENCE optional }|
	{ ID id-Treset-Usage-Indicator								CRITICALITY ignore	EXTENSION NULL				PRESENCE optional }|
	{ ID id-In-Sync-Information-LCR								CRITICALITY ignore	EXTENSION In-Sync-Information-LCR		PRESENCE optional },
	...
}

PDSCHSets-AddList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPDSCHSets)) OF PDSCHSets-AddItem-PSCH-ReconfRqst

PDSCHSets-AddItem-PSCH-ReconfRqst	 ::= SEQUENCE {
	pDSCHSet-ID									PDSCHSet-ID,
	pDSCH-InformationList						PDSCH-Information-AddList-PSCH-ReconfRqst 	OPTIONAL,	-- Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD
	iE-Extensions								ProtocolExtensionContainer { {PDSCHSets-AddItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PDSCHSets-AddItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-PDSCH-AddInformation-LCR-PSCH-ReconfRqst 	CRITICALITY	reject		EXTENSION 	PDSCH-AddInformation-LCR-AddItem-PSCH-ReconfRqst			PRESENCE	optional}| -- Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD.
	{ID id-PDSCH-AddInformation-768-PSCH-ReconfRqst 	CRITICALITY	reject		EXTENSION 	PDSCH-AddInformation-768-AddItem-PSCH-ReconfRqst			PRESENCE	optional}, -- Mandatory for 7.68 Mcps TDD. Not Applicable to 3.84Mcps TDD or 1.28 Mcps TDD.
	...
}

PDSCH-Information-AddList-PSCH-ReconfRqst ::= ProtocolIE-Single-Container {{ PDSCH-Information-AddListIEs-PSCH-ReconfRqst }}
-- Mandatory for 3.84Mcps TDD, Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD

PDSCH-Information-AddListIEs-PSCH-ReconfRqst	NBAP-PROTOCOL-IES ::= { 
	{ID id-PDSCH-Information-AddListIE-PSCH-ReconfRqst 	CRITICALITY	reject		TYPE 	PDSCH-Information-AddItem-PSCH-ReconfRqst			PRESENCE	mandatory}
}

PDSCH-Information-AddItem-PSCH-ReconfRqst ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-PhysicalChannelOffset				TDD-PhysicalChannelOffset,
	dL-Timeslot-InformationAddList-PSCH-ReconfRqst				DL-Timeslot-InformationAddList-PSCH-ReconfRqst,
	iE-Extensions							ProtocolExtensionContainer { {PDSCH-Information-AddItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
	}

PDSCH-Information-AddItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Timeslot-InformationAddList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1.. maxNrOfDLTSs)) OF DL-Timeslot-InformationAddItem-PSCH-ReconfRqst

DL-Timeslot-InformationAddItem-PSCH-ReconfRqst ::= SEQUENCE {
	timeSlot								TimeSlot,
	midambleShiftAndBurstType				MidambleShiftAndBurstType,
	tFCI-Presence							TFCI-Presence,
	dL-Code-InformationAddList-PSCH-ReconfRqst				DL-Code-InformationAddList-PSCH-ReconfRqst,
	iE-Extensions							ProtocolExtensionContainer { { DL-Timeslot-InformationAddItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-Timeslot-InformationAddItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Code-InformationAddList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPDSCHs)) OF DL-Code-InformationAddItem-PSCH-ReconfRqst

DL-Code-InformationAddItem-PSCH-ReconfRqst ::= SEQUENCE {
	pDSCH-ID								PDSCH-ID,
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	iE-Extensions							ProtocolExtensionContainer { { DL-Code-InformationAddItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-Code-InformationAddItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PDSCH-AddInformation-LCR-AddItem-PSCH-ReconfRqst ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-PhysicalChannelOffset				TDD-PhysicalChannelOffset,
	dL-Timeslot-InformationAddList-LCR-PSCH-ReconfRqst				DL-Timeslot-InformationAddList-LCR-PSCH-ReconfRqst,
	iE-Extensions								ProtocolExtensionContainer { {PDSCH-AddInformation-LCR-AddItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
	}

PDSCH-AddInformation-LCR-AddItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
{ID	id-Tstd-indicator			CRITICALITY	reject		EXTENSION 	TSTD-Indicator		PRESENCE 	optional	},
	-- Applicable to 1.28Mcps TDD only
	...
}

DL-Timeslot-InformationAddList-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1.. maxNrOfDLTSLCRs)) OF DL-Timeslot-InformationAddItem-LCR-PSCH-ReconfRqst

DL-Timeslot-InformationAddItem-LCR-PSCH-ReconfRqst ::= SEQUENCE {
	timeSlotLCR								TimeSlotLCR,
	midambleShiftLCR						MidambleShiftLCR,
	tFCI-Presence							TFCI-Presence,
	dL-Code-InformationAddList-LCR-PSCH-ReconfRqst				DL-Code-InformationAddList-LCR-PSCH-ReconfRqst,
	iE-Extensions							ProtocolExtensionContainer { { DL-Timeslot-InformationAddItem-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-Timeslot-InformationAddItem-LCR-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Code-InformationAddList-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPDSCHs)) OF DL-Code-InformationAddItem-LCR-PSCH-ReconfRqst

DL-Code-InformationAddItem-LCR-PSCH-ReconfRqst ::= SEQUENCE {
	pDSCH-ID								PDSCH-ID,
	tdd-ChannelisationCodeLCR				TDD-ChannelisationCodeLCR,
	iE-Extensions							ProtocolExtensionContainer { { DL-Code-InformationAddItem-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-Code-InformationAddItem-LCR-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-PDSCH-Timeslot-Format-PSCH-ReconfRqst-LCR	CRITICALITY reject		EXTENSION TDD-DL-DPCH-TimeSlotFormat-LCR		PRESENCE optional},
	...
}

PDSCH-AddInformation-768-AddItem-PSCH-ReconfRqst ::= SEQUENCE {
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	tdd-PhysicalChannelOffset				TDD-PhysicalChannelOffset,
	dL-Timeslot-InformationAddList-768-PSCH-ReconfRqst				DL-Timeslot-InformationAddList-768-PSCH-ReconfRqst,
	iE-Extensions								ProtocolExtensionContainer { {PDSCH-AddInformation-768-AddItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
	}

PDSCH-AddInformation-768-AddItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Timeslot-InformationAddList-768-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1.. maxNrOfDLTSs)) OF DL-Timeslot-InformationAddItem-768-PSCH-ReconfRqst

DL-Timeslot-InformationAddItem-768-PSCH-ReconfRqst ::= SEQUENCE {
	timeSlot								TimeSlot,
	midambleShiftAndBurstType768			MidambleShiftAndBurstType768,
	tFCI-Presence							TFCI-Presence,
	dL-Code-InformationAddList-768-PSCH-ReconfRqst				DL-Code-InformationAddList-768-PSCH-ReconfRqst,
	iE-Extensions							ProtocolExtensionContainer { { DL-Timeslot-InformationAddItem-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-Timeslot-InformationAddItem-768-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Code-InformationAddList-768-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPDSCHs)) OF DL-Code-InformationAddItem-768-PSCH-ReconfRqst

DL-Code-InformationAddItem-768-PSCH-ReconfRqst ::= SEQUENCE {
	pDSCH-ID768								PDSCH-ID768,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	iE-Extensions							ProtocolExtensionContainer { { DL-Code-InformationAddItem-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-Code-InformationAddItem-768-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PDSCHSets-ModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPDSCHSets)) OF PDSCHSets-ModifyItem-PSCH-ReconfRqst

PDSCHSets-ModifyItem-PSCH-ReconfRqst	 ::= SEQUENCE {
	pDSCHSet-ID									PDSCHSet-ID,
	pDSCH-InformationList						PDSCH-Information-ModifyList-PSCH-ReconfRqst,
	iE-Extensions								ProtocolExtensionContainer { {PDSCHSets-ModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PDSCHSets-ModifyItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-PDSCH-ModifyInformation-768-PSCH-ReconfRqst 	CRITICALITY	reject		EXTENSION 	PDSCH-ModifyInformation-768-ModifyItem-PSCH-ReconfRqst			PRESENCE	optional}, -- For 7.68 Mcps TDD. Not Applicable to 3.84Mcps TDD or 1.28 Mcps TDD.
	...
}

PDSCH-Information-ModifyList-PSCH-ReconfRqst ::= ProtocolIE-Single-Container {{ PDSCH-Information-ModifyListIEs-PSCH-ReconfRqst }}

PDSCH-Information-ModifyListIEs-PSCH-ReconfRqst NBAP-PROTOCOL-IES ::= {
	{ID id-PDSCH-Information-ModifyListIE-PSCH-ReconfRqst	CRITICALITY reject	TYPE PDSCH-Information-ModifyItem-PSCH-ReconfRqst			PRESENCE	optional}|
	{ID id-PDSCH-ModifyInformation-LCR-PSCH-ReconfRqst		CRITICALITY reject	TYPE PDSCH-ModifyInformation-LCR-ModifyItem-PSCH-ReconfRqst			PRESENCE	optional}
}

PDSCH-Information-ModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	repetitionPeriod									RepetitionPeriod								OPTIONAL,
	repetitionLength									RepetitionLength								OPTIONAL,
	tdd-PhysicalChannelOffset							TDD-PhysicalChannelOffset						OPTIONAL,
	dL-Timeslot-InformationModifyList-PSCH-ReconfRqst	DL-Timeslot-InformationModifyList-PSCH-ReconfRqst		OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { {PDSCH-Information-ModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PDSCH-Information-ModifyItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Timeslot-InformationModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1.. maxNrOfDLTSs)) OF DL-Timeslot-InformationModifyItem-PSCH-ReconfRqst

DL-Timeslot-InformationModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	timeSlot										TimeSlot,
	midambleShiftAndBurstType						MidambleShiftAndBurstType							OPTIONAL,
	tFCI-Presence									TFCI-Presence										OPTIONAL,
	dL-Code-InformationModifyList-PSCH-ReconfRqst				DL-Code-InformationModifyList-PSCH-ReconfRqst		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-Timeslot-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-Timeslot-InformationModifyItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Code-InformationModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPDSCHs)) OF DL-Code-InformationModifyItem-PSCH-ReconfRqst

DL-Code-InformationModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	pDSCH-ID								PDSCH-ID,
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	iE-Extensions							ProtocolExtensionContainer { { DL-Code-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-Code-InformationModifyItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PDSCH-ModifyInformation-LCR-ModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	repetitionPeriod											RepetitionPeriod							OPTIONAL,
	repetitionLength											RepetitionLength							OPTIONAL,
	tdd-PhysicalChannelOffset									TDD-PhysicalChannelOffset					OPTIONAL,
	dL-Timeslot-LCR-InformationModifyList-PSCH-ReconfRqst		DL-Timeslot-LCR-InformationModifyList-PSCH-ReconfRqst		OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { {PDSCH-ModifyInformation-LCR-ModifyListIE-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PDSCH-ModifyInformation-LCR-ModifyListIE-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Timeslot-LCR-InformationModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1.. maxNrOfDLTSLCRs)) OF DL-Timeslot-LCR-InformationModifyItem-PSCH-ReconfRqst

DL-Timeslot-LCR-InformationModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	timeSlotLCR												TimeSlotLCR,
	midambleShiftLCR										MidambleShiftLCR							OPTIONAL,
	tFCI-Presence											TFCI-Presence								OPTIONAL,
	dL-Code-LCR-InformationModifyList-PSCH-ReconfRqst		DL-Code-LCR-InformationModifyList-PSCH-ReconfRqst		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-Timeslot-LCR-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-Timeslot-LCR-InformationModifyItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Code-LCR-InformationModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPDSCHs)) OF DL-Code-LCR-InformationModifyItem-PSCH-ReconfRqst

DL-Code-LCR-InformationModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	pDSCH-ID								PDSCH-ID,
	tdd-ChannelisationCodeLCR				TDD-ChannelisationCodeLCR,
	iE-Extensions							ProtocolExtensionContainer { { DL-Code-LCR-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-Code-LCR-InformationModifyItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-PDSCH-Timeslot-Format-PSCH-ReconfRqst-LCR	CRITICALITY reject		EXTENSION TDD-DL-DPCH-TimeSlotFormat-LCR		PRESENCE optional},
	...
}


PDSCH-ModifyInformation-768-ModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	repetitionPeriod											RepetitionPeriod							OPTIONAL,
	repetitionLength											RepetitionLength							OPTIONAL,
	tdd-PhysicalChannelOffset									TDD-PhysicalChannelOffset					OPTIONAL,
	dL-Timeslot-768-InformationModifyList-PSCH-ReconfRqst		DL-Timeslot-768-InformationModifyList-PSCH-ReconfRqst		OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { {PDSCH-ModifyInformation-768-ModifyListIE-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
	}

PDSCH-ModifyInformation-768-ModifyListIE-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Timeslot-768-InformationModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1.. maxNrOfDLTSs)) OF DL-Timeslot-768-InformationModifyItem-PSCH-ReconfRqst

DL-Timeslot-768-InformationModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	timeSlot												TimeSlot,
	midambleShiftAndBurstType768							MidambleShiftAndBurstType768										OPTIONAL,
	tFCI-Presence											TFCI-Presence														OPTIONAL,
	dL-Code-768-InformationModifyList-PSCH-ReconfRqst		DL-Code-768-InformationModifyList-PSCH-ReconfRqst							OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-Timeslot-768-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-Timeslot-768-InformationModifyItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-Code-768-InformationModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPDSCHs)) OF DL-Code-768-InformationModifyItem-PSCH-ReconfRqst

DL-Code-768-InformationModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	pDSCH-ID768								PDSCH-ID768,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	iE-Extensions							ProtocolExtensionContainer { { DL-Code-768-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-Code-768-InformationModifyItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PDSCHSets-DeleteList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPDSCHSets)) OF PDSCHSets-DeleteItem-PSCH-ReconfRqst

PDSCHSets-DeleteItem-PSCH-ReconfRqst	 ::= SEQUENCE {
	pDSCHSet-ID									PDSCHSet-ID,
	iE-Extensions								ProtocolExtensionContainer { {PDSCHSets-DeleteItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PDSCHSets-DeleteItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PUSCHSets-AddList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPUSCHSets)) OF PUSCHSets-AddItem-PSCH-ReconfRqst

PUSCHSets-AddItem-PSCH-ReconfRqst	 ::= SEQUENCE {
	pUSCHSet-ID									PUSCHSet-ID,
	pUSCH-InformationList						PUSCH-Information-AddList-PSCH-ReconfRqst 	OPTIONAL,
	-- Mandatory for 3.84Mcps TDD, Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD
	iE-Extensions								ProtocolExtensionContainer { {PUSCHSets-AddItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PUSCHSets-AddItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-PUSCH-AddInformation-LCR-PSCH-ReconfRqst	CRITICALITY	reject		EXTENSION 	PUSCH-AddInformation-LCR-AddItem-PSCH-ReconfRqst			PRESENCE	optional}|	-- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD
	{ ID id-PUSCH-AddInformation-768-PSCH-ReconfRqst 	CRITICALITY reject		EXTENSION PUSCH-AddInformation-768-AddItem-PSCH-ReconfRqst			PRESENCE optional}, -- Mandatory for 7.68 Mcps TDD. Not Applicable to 3.84Mcps TDD or 1.28 Mcps TDD.
	...
}

PUSCH-Information-AddList-PSCH-ReconfRqst ::=  ProtocolIE-Single-Container {{ PUSCH-Information-AddListIEs-PSCH-ReconfRqst }}

PUSCH-Information-AddListIEs-PSCH-ReconfRqst NBAP-PROTOCOL-IES ::= {
	{ ID id-PUSCH-Information-AddListIE-PSCH-ReconfRqst	CRITICALITY	reject	TYPE PUSCH-Information-AddItem-PSCH-ReconfRqst		PRESENCE mandatory }
}

PUSCH-Information-AddItem-PSCH-ReconfRqst ::= SEQUENCE {
	repetitionPeriod								RepetitionPeriod,
	repetitionLength								RepetitionLength,
	tdd-PhysicalChannelOffset						TDD-PhysicalChannelOffset,
	uL-Timeslot-InformationAddList-PSCH-ReconfRqst	UL-Timeslot-InformationAddList-PSCH-ReconfRqst,
	iE-Extensions									ProtocolExtensionContainer { {PUSCH-Information-AddItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PUSCH-Information-AddItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Timeslot-InformationAddList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfULTSs)) OF UL-Timeslot-InformationAddItem-PSCH-ReconfRqst

UL-Timeslot-InformationAddItem-PSCH-ReconfRqst ::= SEQUENCE {
	timeSlot									TimeSlot,
	midambleShiftAndBurstType					MidambleShiftAndBurstType,
	tFCI-Presence								TFCI-Presence,
	uL-Code-InformationAddList-PSCH-ReconfRqst	UL-Code-InformationAddList-PSCH-ReconfRqst,
	iE-Extensions								ProtocolExtensionContainer { { UL-Timeslot-InformationAddItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

UL-Timeslot-InformationAddItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Code-InformationAddList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPUSCHs)) OF UL-Code-InformationAddItem-PSCH-ReconfRqst

UL-Code-InformationAddItem-PSCH-ReconfRqst ::= SEQUENCE {
	pUSCH-ID								PUSCH-ID,
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	iE-Extensions							ProtocolExtensionContainer { { UL-Code-InformationAddItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

UL-Code-InformationAddItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PUSCH-AddInformation-LCR-AddItem-PSCH-ReconfRqst ::= SEQUENCE {
	repetitionPeriod									RepetitionPeriod,
	repetitionLength									RepetitionLength,
	tdd-PhysicalChannelOffset							TDD-PhysicalChannelOffset,
	uL-Timeslot-InformationAddList-LCR-PSCH-ReconfRqst	UL-Timeslot-InformationAddList-LCR-PSCH-ReconfRqst,
	iE-Extensions								ProtocolExtensionContainer { {PUSCH-AddInformation-LCR-AddItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PUSCH-AddInformation-LCR-AddItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Timeslot-InformationAddList-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1.. maxNrOfULTSLCRs)) OF UL-Timeslot-InformationAddItem-LCR-PSCH-ReconfRqst

UL-Timeslot-InformationAddItem-LCR-PSCH-ReconfRqst ::= SEQUENCE {
	timeSlotLCR										TimeSlotLCR,
	midambleShiftLCR								MidambleShiftLCR,
	tFCI-Presence									TFCI-Presence,
	uL-Code-InformationAddList-LCR-PSCH-ReconfRqst	UL-Code-InformationAddList-LCR-PSCH-ReconfRqst,
	iE-Extensions							ProtocolExtensionContainer { { UL-Timeslot-InformationAddItem-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

UL-Timeslot-InformationAddItem-LCR-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Code-InformationAddList-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPUSCHs)) OF UL-Code-InformationAddItem-LCR-PSCH-ReconfRqst

UL-Code-InformationAddItem-LCR-PSCH-ReconfRqst ::= SEQUENCE {
	pUSCH-ID								PUSCH-ID,
	tdd-ChannelisationCodeLCR				TDD-ChannelisationCodeLCR,
	iE-Extensions							ProtocolExtensionContainer { { UL-Code-InformationAddItem-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

UL-Code-InformationAddItem-LCR-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-PUSCH-Timeslot-Format-PSCH-ReconfRqst-LCR	CRITICALITY reject		EXTENSION TDD-UL-DPCH-TimeSlotFormat-LCR		PRESENCE optional},
	...
}

PUSCH-AddInformation-768-AddItem-PSCH-ReconfRqst ::= SEQUENCE {
	repetitionPeriod									RepetitionPeriod,
	repetitionLength									RepetitionLength,
	tdd-PhysicalChannelOffset							TDD-PhysicalChannelOffset,
	uL-Timeslot-InformationAddList-768-PSCH-ReconfRqst	UL-Timeslot-InformationAddList-768-PSCH-ReconfRqst,
	iE-Extensions								ProtocolExtensionContainer { {PUSCH-AddInformation-768-AddItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PUSCH-AddInformation-768-AddItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Timeslot-InformationAddList-768-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1.. maxNrOfULTSs)) OF UL-Timeslot-InformationAddItem-768-PSCH-ReconfRqst

UL-Timeslot-InformationAddItem-768-PSCH-ReconfRqst ::= SEQUENCE {
	timeSlot										TimeSlot,
	midambleShiftAndBurstType768					MidambleShiftAndBurstType768,
	tFCI-Presence									TFCI-Presence,
	uL-Code-InformationAddList-768-PSCH-ReconfRqst	UL-Code-InformationAddList-768-PSCH-ReconfRqst,
	iE-Extensions							ProtocolExtensionContainer { { UL-Timeslot-InformationAddItem-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

UL-Timeslot-InformationAddItem-768-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Code-InformationAddList-768-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPUSCHs)) OF UL-Code-InformationAddItem-768-PSCH-ReconfRqst

UL-Code-InformationAddItem-768-PSCH-ReconfRqst ::= SEQUENCE {
	pUSCH-ID								PUSCH-ID,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	iE-Extensions							ProtocolExtensionContainer { { UL-Code-InformationAddItem-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

UL-Code-InformationAddItem-768-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PUSCHSets-ModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPUSCHSets)) OF PUSCHSets-ModifyItem-PSCH-ReconfRqst

PUSCHSets-ModifyItem-PSCH-ReconfRqst	 ::= SEQUENCE {
	pUSCHSet-ID									PUSCHSet-ID,
	pUSCH-InformationList						PUSCH-Information-ModifyList-PSCH-ReconfRqst,
	iE-Extensions								ProtocolExtensionContainer { {PUSCHSets-ModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PUSCHSets-ModifyItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-PUSCH-ModifyInformation-768-PSCH-ReconfRqst 	CRITICALITY	reject		EXTENSION 	PUSCH-ModifyInformation-768-ModifyItem-PSCH-ReconfRqst			PRESENCE	optional}, -- For 7.68 Mcps TDD. Not Applicable to 3.84Mcps TDD or 1.28 Mcps TDD.
	...
}

PUSCH-Information-ModifyList-PSCH-ReconfRqst ::= ProtocolIE-Single-Container {{ PUSCH-Information-ModifyListIEs-PSCH-ReconfRqst }}	

PUSCH-Information-ModifyListIEs-PSCH-ReconfRqst NBAP-PROTOCOL-IES ::= {
	{ID id-PUSCH-Information-ModifyListIE-PSCH-ReconfRqst	CRITICALITY reject		TYPE PUSCH-Information-ModifyItem-PSCH-ReconfRqst			PRESENCE	optional}|
	{ID id-PUSCH-ModifyInformation-LCR-PSCH-ReconfRqst		CRITICALITY reject		TYPE PUSCH-ModifyInformation-LCR-ModifyItem-PSCH-ReconfRqst			PRESENCE	optional}
}

PUSCH-Information-ModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	repetitionPeriod									RepetitionPeriod							OPTIONAL,
	repetitionLength									RepetitionLength							OPTIONAL,
	tdd-PhysicalChannelOffset							TDD-PhysicalChannelOffset			OPTIONAL,
	uL-Timeslot-InformationModifyList-PSCH-ReconfRqst	UL-Timeslot-InformationModifyList-PSCH-ReconfRqst		OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { {PUSCH-Information-ModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PUSCH-Information-ModifyItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Timeslot-InformationModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfULTSs)) OF UL-Timeslot-InformationModifyItem-PSCH-ReconfRqst

UL-Timeslot-InformationModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	timeSlot										TimeSlot,
	midambleShiftAndBurstType						MidambleShiftAndBurstType						OPTIONAL,
	tFCI-Presence									TFCI-Presence									OPTIONAL,
	uL-Code-InformationModifyList-PSCH-ReconfRqst	UL-Code-InformationModifyList-PSCH-ReconfRqst		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { UL-Timeslot-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

UL-Timeslot-InformationModifyItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Code-InformationModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPUSCHs)) OF UL-Code-InformationModifyItem-PSCH-ReconfRqst

UL-Code-InformationModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	pUSCH-ID								PUSCH-ID,
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	iE-Extensions							ProtocolExtensionContainer { { UL-Code-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

UL-Code-InformationModifyItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PUSCH-ModifyInformation-LCR-ModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	repetitionPeriod										RepetitionPeriod						OPTIONAL,
	repetitionLength										RepetitionLength						OPTIONAL,
	tdd-PhysicalChannelOffset								TDD-PhysicalChannelOffset				OPTIONAL,
	uL-Timeslot-InformationModifyList-LCR-PSCH-ReconfRqst	UL-Timeslot-LCR-InformationModifyList-PSCH-ReconfRqst	OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { {PUSCH-ModifyInformation-LCR-ModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PUSCH-ModifyInformation-LCR-ModifyItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Timeslot-LCR-InformationModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfULTSLCRs)) OF UL-Timeslot-LCR-InformationModifyItem-PSCH-ReconfRqst

UL-Timeslot-LCR-InformationModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	timeSlotLCR											TimeSlotLCR,
	midambleShiftLCR									MidambleShiftLCR 							OPTIONAL,
	tFCI-Presence										TFCI-Presence								OPTIONAL,
	uL-Code-LCR-InformationModifyList-PSCH-ReconfRqst	UL-Code-LCR-InformationModifyList-PSCH-ReconfRqst	OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { UL-Timeslot-LCR-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

UL-Timeslot-LCR-InformationModifyItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Code-LCR-InformationModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPUSCHs)) OF UL-Code-LCR-InformationModifyItem-PSCH-ReconfRqst

UL-Code-LCR-InformationModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	pUSCH-ID								PUSCH-ID,
	tdd-ChannelisationCodeLCR				TDD-ChannelisationCodeLCR,
	iE-Extensions							ProtocolExtensionContainer { { UL-Code-LCR-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

UL-Code-LCR-InformationModifyItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-PUSCH-Timeslot-Format-PSCH-ReconfRqst-LCR	CRITICALITY reject		EXTENSION TDD-UL-DPCH-TimeSlotFormat-LCR		PRESENCE optional},
	...
}

PUSCH-ModifyInformation-768-ModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	repetitionPeriod										RepetitionPeriod						OPTIONAL,
	repetitionLength										RepetitionLength						OPTIONAL,
	tdd-PhysicalChannelOffset								TDD-PhysicalChannelOffset				OPTIONAL,
	uL-Timeslot-InformationModifyList-768-PSCH-ReconfRqst	UL-Timeslot-768-InformationModifyList-PSCH-ReconfRqst	OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { {PUSCH-ModifyInformation-768-ModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PUSCH-ModifyInformation-768-ModifyItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Timeslot-768-InformationModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfULTSs)) OF UL-Timeslot-768-InformationModifyItem-PSCH-ReconfRqst

UL-Timeslot-768-InformationModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	timeSlot											TimeSlot,
	midambleShiftAndBurstType768						MidambleShiftAndBurstType768								OPTIONAL,
	tFCI-Presence										TFCI-Presence																		OPTIONAL,
	uL-Code-768-InformationModifyList-PSCH-ReconfRqst	UL-Code-768-InformationModifyList-PSCH-ReconfRqst	OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { UL-Timeslot-768-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

UL-Timeslot-768-InformationModifyItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Code-768-InformationModifyList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPUSCHs)) OF UL-Code-768-InformationModifyItem-PSCH-ReconfRqst

UL-Code-768-InformationModifyItem-PSCH-ReconfRqst ::= SEQUENCE {
	pUSCH-ID								PUSCH-ID,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	iE-Extensions							ProtocolExtensionContainer { { UL-Code-768-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

UL-Code-768-InformationModifyItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PUSCHSets-DeleteList-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfPUSCHSets)) OF PUSCHSets-DeleteItem-PSCH-ReconfRqst

PUSCHSets-DeleteItem-PSCH-ReconfRqst	 ::= SEQUENCE {
	pUSCHSet-ID									PUSCHSet-ID,
	iE-Extensions								ProtocolExtensionContainer { {PUSCHSets-DeleteItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

PUSCHSets-DeleteItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-PDSCH-TDD-Information-PSCH-ReconfRqst ::= SEQUENCE {
	dL-HS-PDSCH-Timeslot-Information-PSCH-ReconfRqst					DL-HS-PDSCH-Timeslot-Information-PSCH-ReconfRqst			OPTIONAL,
	dL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst				DL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst		OPTIONAL,
	-- This HS-PDSCH Timeslot Information is for the first Frequency repetition, HS-PDSCH Timeslot information for Frequency repetitions 2 and on, should be defined in MultipleFreq-DL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst
	iE-Extensions								ProtocolExtensionContainer { { HS-PDSCH-TDD-Information-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

HS-PDSCH-TDD-Information-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-dL-HS-PDSCH-Timeslot-Information-768-PSCH-ReconfRqst 								CRITICALITY reject		EXTENSION  DL-HS-PDSCH-Timeslot-Information-768-PSCH-ReconfRqst			PRESENCE	optional }| -- For 7.68 Mcps TDD. Not Applicable to 3.84Mcps TDD or 1.28 Mcps TDD.
	{ ID id-UARFCNforNt																			CRITICALITY ignore		EXTENSION UARFCN																		PRESENCE optional }|
	-- This is the UARFCN for the first Frequency repetition. Mandatory for 1.28Mcps TDD when using multiple frequencies.
	{ ID id-multipleFreq-dL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst					CRITICALITY reject		EXTENSION MultipleFreq-DL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst		PRESENCE optional },
	-- Applicable to 1.28Mcps TDD when using multiple frequencies, This Information is for the 2nd and beyond Frequency repetition
	...
}


DL-HS-PDSCH-Timeslot-Information-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfDLTSs)) OF DL-HS-PDSCH-Timeslot-InformationItem-PSCH-ReconfRqst

DL-HS-PDSCH-Timeslot-InformationItem-PSCH-ReconfRqst::= SEQUENCE {
	timeSlot								TimeSlot,
	midambleShiftAndBurstType				MidambleShiftAndBurstType,
	dl-HS-PDSCH-Codelist-PSCH-ReconfRqst	DL-HS-PDSCH-Codelist-PSCH-ReconfRqst,
	maxHSDSCH-HSSCCH-Power					MaximumTransmissionPower				OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-HS-PDSCH-Timeslot-InformationItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-HS-PDSCH-Timeslot-InformationItem-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-HS-PDSCH-Codelist-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfHSPDSCHs)) OF TDD-ChannelisationCode


DL-HS-PDSCH-Timeslot-Information-768-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfDLTSs)) OF DL-HS-PDSCH-Timeslot-InformationItem-768-PSCH-ReconfRqst

DL-HS-PDSCH-Timeslot-InformationItem-768-PSCH-ReconfRqst::= SEQUENCE {
	timeSlot									TimeSlot,
	midambleShiftAndBurstType768				MidambleShiftAndBurstType768,
	dl-HS-PDSCH-Codelist-768-PSCH-ReconfRqst	DL-HS-PDSCH-Codelist-768-PSCH-ReconfRqst,
	maxHSDSCH-HSSCCH-Power						MaximumTransmissionPower					OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { DL-HS-PDSCH-Timeslot-InformationItem-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-HS-PDSCH-Timeslot-InformationItem-768-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-HS-PDSCH-Codelist-768-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfHSPDSCHs768)) OF TDD-ChannelisationCode768

MultipleFreq-DL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxFrequencyinCell-1)) OF ProtocolIE-Single-Container{{ MultipleFreq-DL-HS-PDSCH-Timeslot-Information-LCRItemIE-PSCH-ReconfRqst}}
	-- Includes the 2nd through the max number of frequency repetitions.

MultipleFreq-DL-HS-PDSCH-Timeslot-Information-LCRItemIE-PSCH-ReconfRqst NBAP-PROTOCOL-IES ::= {
	{ ID id-MultipleFreq-DL-HS-PDSCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst	CRITICALITY  reject	TYPE	MultipleFreq-DL-HS-PDSCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst PRESENCE optional }
}

MultipleFreq-DL-HS-PDSCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst ::= SEQUENCE {
	dL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst	DL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst 	OPTIONAL,
	uARFCN													UARFCN,
	iE-Extensions											ProtocolExtensionContainer { { MultipleFreq-DL-HS-PDSCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

MultipleFreq-DL-HS-PDSCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Add-To-HS-SCCH-Resource-Pool-PSCH-ReconfRqst::= SEQUENCE {
	hS-SCCH-Information-PSCH-ReconfRqst		HS-SCCH-Information-PSCH-ReconfRqst			OPTIONAL,
	hS-SCCH-Information-LCR-PSCH-ReconfRqst	HS-SCCH-Information-LCR-PSCH-ReconfRqst		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { Add-To-HS-SCCH-Resource-Pool-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Add-To-HS-SCCH-Resource-Pool-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-hS-SCCH-Information-768-PSCH-ReconfRqst CRITICALITY	reject		EXTENSION HS-SCCH-Information-768-PSCH-ReconfRqst			PRESENCE optional }|
	-- 7.68 Mcps TDD. Not Applicable to 3.84Mcps TDD or 1.28 Mcps TDD.
	{ ID id-HS-SCCH-InformationExt-LCR-PSCH-ReconfRqst	CRITICALITY ignore	EXTENSION HS-SCCH-InformationExt-LCR-PSCH-ReconfRqst		PRESENCE optional },
	-- Applicable to 1.28Mcps TDD only, used when there are more than maxNrOfHSSCCHs HS-SCCHs in the message.
	...
}

HS-SCCH-Information-PSCH-ReconfRqst::= SEQUENCE (SIZE (1..maxNrOfHSSCCHs)) OF HS-SCCH-InformationItem-PSCH-ReconfRqst

HS-SCCH-InformationItem-PSCH-ReconfRqst	 ::= SEQUENCE {
	hS-SCCH-ID								HS-SCCH-ID,
	timeSlot								TimeSlot,
	midambleShiftAndBurstType				MidambleShiftAndBurstType,
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	hS-SCCH-MaxPower						DL-Power,
	hS-SICH-Information						HS-SICH-Information-PSCH-ReconfRqst,
	iE-Extensions							ProtocolExtensionContainer { { HS-SCCH-InformationItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

HS-SCCH-InformationItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-SICH-Information-PSCH-ReconfRqst	 ::= SEQUENCE {
	hsSICH-ID								HS-SICH-ID,
	timeSlot								TimeSlot,
	midambleShiftAndBurstType				MidambleShiftAndBurstType,
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	iE-Extensions							ProtocolExtensionContainer { { HS-SICH-Information-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

HS-SICH-Information-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-SCCH-Information-LCR-PSCH-ReconfRqst::= SEQUENCE (SIZE (1..maxNrOfHSSCCHs)) OF HS-SCCH-InformationItem-LCR-PSCH-ReconfRqst

HS-SCCH-InformationItem-LCR-PSCH-ReconfRqst	 ::= SEQUENCE {
	hS-SCCH-ID								HS-SCCH-ID,
	timeSlotLCR								TimeSlotLCR,
	midambleShiftLCR						MidambleShiftLCR,
	first-TDD-ChannelisationCode			TDD-ChannelisationCode,
	second-TDD-ChannelisationCode			TDD-ChannelisationCode,
	hS-SCCH-MaxPower						DL-Power,
	hS-SICH-Information-LCR					HS-SICH-Information-LCR-PSCH-ReconfRqst,
	iE-Extensions							ProtocolExtensionContainer { { HS-SCCH-InformationItem-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

HS-SCCH-InformationItem-LCR-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-HS-SCCH-ID							CRITICALITY ignore		EXTENSION Extended-HS-SCCH-ID	PRESENCE optional}|
	-- used if the HS-SCCH identity has a value larger than 31
	{ ID id-UARFCNforNt								CRITICALITY ignore		EXTENSION UARFCN		PRESENCE optional}|
	-- Mandatory for 1.28Mcps TDD when using multiple frequencies
	{ ID id-HSSICH-ReferenceSignal-InformationLCR	CRITICALITY ignore		EXTENSION HSSICH-ReferenceSignal-InformationLCR		PRESENCE optional},
	...
}

HS-SICH-Information-LCR-PSCH-ReconfRqst	 ::= SEQUENCE {
	hsSICH-ID								HS-SICH-ID,
	timeSlotLCR								TimeSlotLCR,
	midambleShiftLCR						MidambleShiftLCR,
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	iE-Extensions							ProtocolExtensionContainer { { HS-SICH-Information-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

HS-SICH-Information-LCR-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-HS-SICH-ID							CRITICALITY ignore	EXTENSION Extended-HS-SICH-ID	PRESENCE optional},
	-- used if the HS-SICH identity has a value larger than 31
	...
}

HS-SCCH-Information-768-PSCH-ReconfRqst::= SEQUENCE (SIZE (1..maxNrOfHSSCCHs)) OF HS-SCCH-InformationItem-768-PSCH-ReconfRqst

HS-SCCH-InformationItem-768-PSCH-ReconfRqst	 ::= SEQUENCE {
	hS-SCCH-ID								HS-SCCH-ID,
	timeSlot								TimeSlot,
	midambleShiftAndBurstType768			MidambleShiftAndBurstType768,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	hS-SCCH-MaxPower						DL-Power,
	hS-SICH-Information-768					HS-SICH-Information-768-PSCH-ReconfRqst,
	iE-Extensions							ProtocolExtensionContainer { { HS-SCCH-InformationItem-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

HS-SCCH-InformationItem-768-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-SICH-Information-768-PSCH-ReconfRqst	 ::= SEQUENCE {
	hsSICH-ID								HS-SICH-ID,
	timeSlot								TimeSlot,
	midambleShiftAndBurstType768			MidambleShiftAndBurstType768,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	iE-Extensions							ProtocolExtensionContainer { { HS-SICH-Information-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

HS-SICH-Information-768-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-SCCH-InformationExt-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1.. maxNrOfHSSCCHsinExt)) OF HS-SCCH-InformationItem-LCR-PSCH-ReconfRqst

Modify-HS-SCCH-Resource-Pool-PSCH-ReconfRqst::= SEQUENCE {
	hS-SCCH-InformationModify-PSCH-ReconfRqst		HS-SCCH-InformationModify-PSCH-ReconfRqst		OPTIONAL,
	hS-SCCH-InformationModify-LCR-PSCH-ReconfRqst	HS-SCCH-InformationModify-LCR-PSCH-ReconfRqst	OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { Modify-HS-SCCH-Resource-Pool-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Modify-HS-SCCH-Resource-Pool-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-hS-SCCH-InformationModify-768-PSCH-ReconfRqst		CRITICALITY reject	EXTENSION HS-SCCH-InformationModify-768-PSCH-ReconfRqst 	PRESENCE	optional }|
	-- 7.68 Mcps TDD. Not Applicable to 3.84Mcps TDD or 1.28 Mcps TDD.
	{ ID id-HS-SCCH-InformationModifyExt-LCR-PSCH-ReconfRqst	CRITICALITY ignore	EXTENSION HS-SCCH-InformationModifyExt-LCR-PSCH-ReconfRqst		PRESENCE optional },
	-- Applicable to 1.28Mcps TDD only, used when there are more than maxNrOfHSSCCHs HS-SCCHs in the message.
	...
}

HS-SCCH-InformationModifyItem-PSCH-ReconfRqst	 ::= SEQUENCE {
	hS-SCCH-ID								HS-SCCH-ID,
	timeSlot								TimeSlot 									OPTIONAL,
	midambleShiftAndBurstType				MidambleShiftAndBurstType 					OPTIONAL,
	tdd-ChannelisationCode					TDD-ChannelisationCode 						OPTIONAL,
	hS-SCCH-MaxPower						DL-Power 									OPTIONAL,
	hS-SICH-Information						HS-SICH-InformationModify-PSCH-ReconfRqst 	OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { HS-SCCH-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

HS-SCCH-InformationModifyItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-SICH-InformationModify-PSCH-ReconfRqst	 ::= SEQUENCE {
	hsSICH-ID								HS-SICH-ID,
	timeSlot								TimeSlot 					OPTIONAL,
	midambleShiftAndBurstType				MidambleShiftAndBurstType 	OPTIONAL,
	tdd-ChannelisationCode					TDD-ChannelisationCode 		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { HS-SICH-InformationModify-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

HS-SICH-InformationModify-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-SCCH-InformationModify-LCR-PSCH-ReconfRqst::= SEQUENCE (SIZE (1..maxNrOfHSSCCHs)) OF HS-SCCH-InformationModifyItem-LCR-PSCH-ReconfRqst

HS-SCCH-InformationModifyItem-LCR-PSCH-ReconfRqst	 ::= SEQUENCE {
	hS-SCCH-ID								HS-SCCH-ID,
	timeSlotLCR								TimeSlotLCR 									OPTIONAL,
	midambleShiftLCR						MidambleShiftLCR 								OPTIONAL,
	first-TDD-ChannelisationCode			TDD-ChannelisationCode							OPTIONAL,
	second-TDD-ChannelisationCode			TDD-ChannelisationCode							OPTIONAL,
	hS-SCCH-MaxPower						DL-Power										OPTIONAL,
	hS-SICH-Information-LCR					HS-SICH-InformationModify-LCR-PSCH-ReconfRqst 	OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { HS-SCCH-InformationModifyItem-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

HS-SCCH-InformationModifyItem-LCR-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-HS-SCCH-ID							CRITICALITY ignore	EXTENSION Extended-HS-SCCH-ID	PRESENCE optional}|
	-- used if the HS-SCCH identity has a value larger than 31
	{ ID id-UARFCNforNt									CRITICALITY ignore	EXTENSION UARFCN		PRESENCE optional}|
	-- Applicable to 1.28Mcps TDD when using multiple frequencies
	{ ID id-HSSICH-ReferenceSignal-InformationModifyLCR		CRITICALITY reject		EXTENSION HSSICH-ReferenceSignal-InformationModifyLCR		PRESENCE optional},
	...
}

HS-SCCH-InformationModifyExt-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1.. maxNrOfHSSCCHsinExt)) OF HS-SCCH-InformationModifyItem-LCR-PSCH-ReconfRqst

HS-SICH-InformationModify-LCR-PSCH-ReconfRqst	 ::= SEQUENCE {
	hsSICH-ID								HS-SICH-ID,
	timeSlotLCR								TimeSlotLCR 			OPTIONAL,
	midambleShiftLCR						MidambleShiftLCR 		OPTIONAL,
	tdd-ChannelisationCode					TDD-ChannelisationCode	OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { HS-SICH-InformationModify-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

HS-SICH-InformationModify-LCR-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-HS-SICH-ID							CRITICALITY ignore	EXTENSION Extended-HS-SICH-ID	PRESENCE optional },
	-- used if the HS-SICH identity has a value larger than 31
	...
}

HS-SCCH-InformationModify-768-PSCH-ReconfRqst::= SEQUENCE (SIZE (1..maxNrOfHSSCCHs)) OF HS-SCCH-InformationModifyItem-768-PSCH-ReconfRqst

HS-SCCH-InformationModifyItem-768-PSCH-ReconfRqst	 ::= SEQUENCE {
	hS-SCCH-ID								HS-SCCH-ID,
	timeSlot								TimeSlot										OPTIONAL,
	midambleShiftAndBurstType768			MidambleShiftAndBurstType768,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	hS-SCCH-MaxPower						DL-Power 																			OPTIONAL,
	hS-SICH-Information-768					HS-SICH-InformationModify-768-PSCH-ReconfRqst 	OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { HS-SCCH-InformationModifyItem-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

HS-SCCH-InformationModifyItem-768-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-SICH-InformationModify-768-PSCH-ReconfRqst	 ::= SEQUENCE {
	hsSICH-ID								HS-SICH-ID,
	timeSlot								TimeSlot										OPTIONAL,
	midambleShiftAndBurstType768			MidambleShiftAndBurstType768,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	iE-Extensions							ProtocolExtensionContainer { { HS-SICH-InformationModify-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

HS-SICH-InformationModify-768-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-SCCH-InformationModify-PSCH-ReconfRqst::= SEQUENCE (SIZE (1..maxNrOfHSSCCHs)) OF HS-SCCH-InformationModifyItem-PSCH-ReconfRqst

Delete-From-HS-SCCH-Resource-Pool-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfHSSCCHs)) OF Delete-From-HS-SCCH-Resource-PoolItem-PSCH-ReconfRqst

Delete-From-HS-SCCH-Resource-PoolItem-PSCH-ReconfRqst	 ::= SEQUENCE {
	hS-SCCH-ID					HS-SCCH-ID,
	iE-Extensions				ProtocolExtensionContainer { { Delete-From-HS-SCCH-Resource-PoolItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Delete-From-HS-SCCH-Resource-PoolItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-HS-SCCH-ID							CRITICALITY ignore	EXTENSION Extended-HS-SCCH-ID	PRESENCE optional },
	-- used if the HS-SCCH identity has a value larger than 31
	...
}

E-PUCH-Information-PSCH-ReconfRqst ::= SEQUENCE {
	lTGI-Presence							LTGI-Presence,
	sNPL-Reporting-Type						SNPL-Reporting-Type,
	midambleShiftAndBurstType				MidambleShiftAndBurstType,
	e-PUCH-Timeslot-Info					E-PUCH-Timeslot-Info,
	iE-Extensions							ProtocolExtensionContainer { { E-PUCH-Information-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

E-PUCH-Information-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-PUCH-Timeslot-Info ::= SEQUENCE (SIZE (1..maxNrOfE-PUCHSlots)) OF TimeSlot

Add-To-E-AGCH-Resource-Pool-PSCH-ReconfRqst::= SEQUENCE {
	e-AGCH-Information-PSCH-ReconfRqst		E-AGCH-Information-PSCH-ReconfRqst		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { Add-To-E-AGCH-Resource-Pool-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Add-To-E-AGCH-Resource-Pool-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-AGCH-Information-PSCH-ReconfRqst::= SEQUENCE (SIZE (1..maxNrOfEAGCHs)) OF E-AGCH-InformationItem-PSCH-ReconfRqst

E-AGCH-InformationItem-PSCH-ReconfRqst	 ::= SEQUENCE {
	e-AGCH-ID								E-AGCH-Id,
	timeSlot								TimeSlot,
	midambleShiftAndBurstType				MidambleShiftAndBurstType,
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	e-AGCH-MaxPower							DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { E-AGCH-InformationItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

E-AGCH-InformationItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Modify-E-AGCH-Resource-Pool-PSCH-ReconfRqst::= SEQUENCE {
	e-AGCH-InformationModify-PSCH-ReconfRqst		E-AGCH-InformationModify-PSCH-ReconfRqst	OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { Modify-E-AGCH-Resource-Pool-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Modify-E-AGCH-Resource-Pool-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-AGCH-InformationModify-PSCH-ReconfRqst::= SEQUENCE (SIZE (1..maxNrOfEAGCHs)) OF E-AGCH-InformationModifyItem-PSCH-ReconfRqst

E-AGCH-InformationModifyItem-PSCH-ReconfRqst	 ::= SEQUENCE {
	e-AGCH-ID								E-AGCH-Id,
	timeSlot								TimeSlot 					OPTIONAL,
	midambleShiftAndBurstType				MidambleShiftAndBurstType 	OPTIONAL,
	tdd-ChannelisationCode					TDD-ChannelisationCode 		OPTIONAL,
	e-AGCH-MaxPower							DL-Power 					OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { E-AGCH-InformationModifyItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

E-AGCH-InformationModifyItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Delete-From-E-AGCH-Resource-Pool-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfEAGCHs)) OF Delete-From-E-AGCH-Resource-PoolItem-PSCH-ReconfRqst

Delete-From-E-AGCH-Resource-PoolItem-PSCH-ReconfRqst	 ::= SEQUENCE {
	e-AGCH-ID							E-AGCH-Id,
	iE-Extensions						ProtocolExtensionContainer { { Delete-From-E-AGCH-Resource-PoolItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Delete-From-E-AGCH-Resource-PoolItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-HICH-Information-PSCH-ReconfRqst	 ::= SEQUENCE {
	midambleShiftAndBurstType				MidambleShiftAndBurstType,
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	e-HICH-MaxPower							DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { E-HICH-Information-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}
E-HICH-Information-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-PUCH-Information-768-PSCH-ReconfRqst ::= SEQUENCE {
	lTGI-Presence							LTGI-Presence,
	sNPL-Reporting-Type						SNPL-Reporting-Type,
	midambleShiftAndBurstType768			MidambleShiftAndBurstType768,
	e-PUCH-Timeslot-Info					E-PUCH-Timeslot-Info,
	iE-Extensions							ProtocolExtensionContainer { { E-PUCH-Information-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

E-PUCH-Information-768-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Add-To-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst::= SEQUENCE {
	e-AGCH-Information-768-PSCH-ReconfRqst		E-AGCH-Information-768-PSCH-ReconfRqst		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { Add-To-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Add-To-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-AGCH-Information-768-PSCH-ReconfRqst::= SEQUENCE (SIZE (1..maxNrOfEAGCHs)) OF E-AGCH-InformationItem-768-PSCH-ReconfRqst

E-AGCH-InformationItem-768-PSCH-ReconfRqst	 ::= SEQUENCE {
	e-AGCH-ID								E-AGCH-Id,
	timeSlot								TimeSlot,
	midambleShiftAndBurstType768			MidambleShiftAndBurstType768,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	e-AGCH-MaxPower							DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { E-AGCH-InformationItem-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

E-AGCH-InformationItem-768-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Modify-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst::= SEQUENCE {
	e-AGCH-InformationModify-768-PSCH-ReconfRqst		E-AGCH-InformationModify-768-PSCH-ReconfRqst	OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { Modify-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Modify-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-AGCH-InformationModify-768-PSCH-ReconfRqst::= SEQUENCE (SIZE (1..maxNrOfEAGCHs)) OF E-AGCH-InformationModifyItem-768-PSCH-ReconfRqst

E-AGCH-InformationModifyItem-768-PSCH-ReconfRqst	 ::= SEQUENCE {
	e-AGCH-ID								E-AGCH-Id,
	timeSlot								TimeSlot 						OPTIONAL,
	midambleShiftAndBurstType768			MidambleShiftAndBurstType768	OPTIONAL,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768		OPTIONAL,
	e-AGCH-MaxPower							DL-Power 						OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { E-AGCH-InformationModifyItem-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

E-AGCH-InformationModifyItem-768-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-HICH-Information-768-PSCH-ReconfRqst	 ::= SEQUENCE {
	midambleShiftAndBurstType768			MidambleShiftAndBurstType768,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	e-HICH-MaxPower							DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { E-HICH-Information-768-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}
E-HICH-Information-768-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-PUCH-Information-LCR-PSCH-ReconfRqst ::= SEQUENCE {
	lTGI-Presence							LTGI-Presence,
	sNPL-Reporting-Type						SNPL-Reporting-Type,
	e-PUCH-Timeslot-InfoLCR					E-PUCH-Timeslot-InfoLCR		OPTIONAL,
	-- This E-PUCH Timeslot Information is for the first Frequency repetition, E-PUCH timeslot information for Frequency repetitions 2 and on, should be defined in MultipleFreq-E-PUCH-Timeslot-InformationList-LCR-PSCH-ReconfRqst.
	iE-Extensions							ProtocolExtensionContainer { { E-PUCH-Information-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

E-PUCH-Information-LCR-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UARFCNforNt															CRITICALITY ignore										EXTENSION UARFCN															PRESENCE optional}|
	-- This is the UARFCN for the first Frequency repetition. Mandatory for 1.28Mcps TDD when using multiple frequencies.
	{ ID id-MultipleFreq-E-PUCH-Timeslot-InformationList-LCR-PSCH-ReconfRqst	CRITICALITY reject										EXTENSION MultipleFreq-E-PUCH-Timeslot-InformationList-LCR-PSCH-ReconfRqst	PRESENCE optional },
	-- Applicable to 1.28Mcps TDD when using multiple frequencies.This E-PUCH Information is for the 2nd and beyond frequencies.
	...
}

E-PUCH-Timeslot-InfoLCR ::= SEQUENCE (SIZE (1..maxNrOfE-PUCHSlotsLCR)) OF E-PUCH-Timeslot-Item-InfoLCR

E-PUCH-Timeslot-Item-InfoLCR ::= SEQUENCE {
	timeSlot								TimeSlotLCR,
	midambleShiftAndBurstType				MidambleShiftLCR,
	e-PUCH-Codelist-LCR						E-PUCH-Codelist-LCR,
	iE-Extensions							ProtocolExtensionContainer { { E-PUCH-Timeslot-Item-InfoLCR-ExtIEs} }		OPTIONAL,
	...
}

E-PUCH-Timeslot-Item-InfoLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-PUCH-Codelist-LCR ::= SEQUENCE (SIZE (1..maxNrOfEPUCHcodes)) OF TDD-ChannelisationCode

Add-To-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst ::= SEQUENCE {
	e-AGCH-Information-LCR-PSCH-ReconfRqst	E-AGCH-Information-LCR-PSCH-ReconfRqst,
	iE-Extensions							ProtocolExtensionContainer { { Add-To-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Add-To-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-AGCH-Information-LCR-PSCH-ReconfRqst::= SEQUENCE (SIZE (1..maxNrOfEAGCHs)) OF E-AGCH-InformationItem-LCR-PSCH-ReconfRqst

E-AGCH-InformationItem-LCR-PSCH-ReconfRqst	 ::= SEQUENCE {
	e-AGCH-ID								E-AGCH-Id,
	timeSlotLCR								TimeSlotLCR,
	midambleShiftLCR						MidambleShiftLCR,
	first-TDD-ChannelisationCode			TDD-ChannelisationCode,
	second-TDD-ChannelisationCode			TDD-ChannelisationCode,
	e-AGCH-MaxPower							DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { E-AGCH-InformationItem-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

E-AGCH-InformationItem-LCR-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UARFCNforNt						CRITICALITY ignore		EXTENSION UARFCN		PRESENCE optional},
	-- Mandatory for 1.28Mcps TDD when using multiple frequencies
	...
}

Modify-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst::= SEQUENCE {
	e-AGCH-InformationModify-LCR-PSCH-ReconfRqst	E-AGCH-InformationModify-LCR-PSCH-ReconfRqst,
	iE-Extensions									ProtocolExtensionContainer { { Modify-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Modify-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-AGCH-InformationModify-LCR-PSCH-ReconfRqst::= SEQUENCE (SIZE (1..maxNrOfEAGCHs)) OF E-AGCH-InformationModifyItem-LCR-PSCH-ReconfRqst

E-AGCH-InformationModifyItem-LCR-PSCH-ReconfRqst	 ::= SEQUENCE {
	e-AGCH-ID								E-AGCH-Id,
	timeSlotLCR								TimeSlotLCR				OPTIONAL,
	midambleShiftLCR						MidambleShiftLCR		OPTIONAL,
	first-TDD-ChannelisationCode			TDD-ChannelisationCode	OPTIONAL,
	second-TDD-ChannelisationCode			TDD-ChannelisationCode	OPTIONAL,
	e-AGCH-MaxPower							DL-Power				OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { E-AGCH-InformationModifyItem-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

E-AGCH-InformationModifyItem-LCR-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UARFCNforNt						CRITICALITY ignore		EXTENSION UARFCN		PRESENCE optional},
	-- Mandatory for 1.28Mcps TDD when using multiple frequencies
	...
}

Add-To-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst ::= SEQUENCE {
	e-HICH-Information-LCR-PSCH-ReconfRqst	E-HICH-Information-LCR-PSCH-ReconfRqst,
	iE-Extensions							ProtocolExtensionContainer { { Add-To-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Add-To-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-HICH-Information-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfEHICHs)) OF E-HICH-InformationItem-LCR-PSCH-ReconfRqst

E-HICH-InformationItem-LCR-PSCH-ReconfRqst	::= SEQUENCE {
	e-HICH-ID-TDD							E-HICH-ID-TDD,
	e-HICH-Type								E-HICH-Type,
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	timeSlotLCR								TimeSlotLCR,
	midambleShiftLCR						MidambleShiftLCR,
	e-HICH-MaxPower							DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { E-HICH-InformationItem-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

E-HICH-InformationItem-LCR-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-E-HICH-ID-TDD			CRITICALITY ignore EXTENSION Extended-E-HICH-ID-TDD PRESENCE optional}|
	-- Applicable to 1.28Mcps TDD only when the E-HICH identity has a value larger than 31.
	{ ID id-UARFCNforNt						CRITICALITY ignore		EXTENSION UARFCN			PRESENCE optional},
	-- Mandatory for 1.28Mcps TDD when using multiple frequencies
	...
}

Modify-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst ::= SEQUENCE {
	e-HICH-InformationModify-LCR-PSCH-ReconfRqst	E-HICH-InformationModify-LCR-PSCH-ReconfRqst,
	iE-Extensions									ProtocolExtensionContainer { { Modify-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Modify-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-HICH-InformationModify-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfEHICHs)) OF E-HICH-InformationModifyItem-LCR-PSCH-ReconfRqst

E-HICH-InformationModifyItem-LCR-PSCH-ReconfRqst ::= SEQUENCE {
	e-HICH-ID-TDD							E-HICH-ID-TDD,
	e-HICH-Type								E-HICH-Type  			OPTIONAL,
	tdd-ChannelisationCode					TDD-ChannelisationCode  OPTIONAL,
	timeSlotLCR								TimeSlotLCR   			OPTIONAL,
	midambleShiftLCR						MidambleShiftLCR   		OPTIONAL,
	e-HICH-MaxPower							DL-Power   				OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { E-HICH-InformationModifyItem-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

E-HICH-InformationModifyItem-LCR-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-E-HICH-ID-TDD			CRITICALITY ignore EXTENSION Extended-E-HICH-ID-TDD PRESENCE optional}|
	--Applicable to 1.28Mcps TDD only when the E-HICH identity has a value larger than 31.
	{ ID id-UARFCNforNt						CRITICALITY ignore		EXTENSION UARFCN			PRESENCE optional},
	-- Mandatory for 1.28Mcps TDD when using multiple frequencies
	...
}

Delete-From-E-HICH-Resource-Pool-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1.. maxNrOfEHICHs)) OF Delete-From-E-HICH-Resource-PoolItem-PSCH-ReconfRqst

Delete-From-E-HICH-Resource-PoolItem-PSCH-ReconfRqst	::= SEQUENCE {
	e-HICH-ID-TDD									E-HICH-ID-TDD,
	iE-Extensions									ProtocolExtensionContainer { { Delete-From-E-HICH-Resource-PoolItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

Delete-From-E-HICH-Resource-PoolItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-E-HICH-ID-TDD			CRITICALITY ignore EXTENSION Extended-E-HICH-ID-TDD PRESENCE optional},
	-- Applicable to 1.28Mcps TDD only when the E-HICH identity has a value larger than 31.
	...
}

SYNC-UL-Partition-LCR ::= SEQUENCE {
	eRUCCH-SYNC-UL-codes-bitmap					BIT STRING (SIZE (8)),
	iE-Extensions								ProtocolExtensionContainer { { SYNC-UL-Partition-LCR-ExtIEs} }		OPTIONAL,
	...
}

SYNC-UL-Partition-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Delete-From-HS-SCCH-Resource-PoolExt-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1.. maxNrOfHSSCCHsinExt)) OF Delete-From-HS-SCCH-Resource-PoolItem-PSCH-ReconfRqst

MultipleFreq-E-PUCH-Timeslot-InformationList-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxFrequencyinCell-1)) OF ProtocolIE-Single-Container {{ MultipleFreq-E-PUCH-Timeslot-InformationItemIE-LCR-PSCH-ReconfRqst}} 
--Includes the 2nd through the max number of frequencies information repetitions.

MultipleFreq-E-PUCH-Timeslot-InformationItemIE-LCR-PSCH-ReconfRqst NBAP-PROTOCOL-IES ::= {
	{ ID id-MultipleFreq-E-PUCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst	CRITICALITY ignore	TYPE MultipleFreq-E-PUCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst		PRESENCE optional }
}

MultipleFreq-E-PUCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst ::= SEQUENCE {
	e-PUCH-Timeslot-InfoLCR					E-PUCH-Timeslot-InfoLCR		OPTIONAL,
	uARFCN													UARFCN,
	iE-Extensions											ProtocolExtensionContainer { { MultipleFreq-E-PUCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

MultipleFreq-E-PUCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Max-RTWP-perUARFCN-Information-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxFrequencyinCell)) OF Max-RTWP-perUARFCN-Information-LCR-PSCH-ReconfRqst-Item

Max-RTWP-perUARFCN-Information-LCR-PSCH-ReconfRqst-Item ::= SEQUENCE {
	uARFCN												UARFCN,
	maximum-Target-ReceivedTotalWideBandPower-LCR		Maximum-Target-ReceivedTotalWideBandPower-LCR,
	iE-Extensions					ProtocolExtensionContainer { { Max-RTWP-perUARFCN-Information-LCR-PSCH-ReconfRqst-Item-ExtIEs} }					OPTIONAL,
	...
}

Max-RTWP-perUARFCN-Information-LCR-PSCH-ReconfRqst-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
{ID id-Max-RTWP-perCellPortion-InformationList-LCR-PSCH-ReconfRqst	CRITICALITY ignore EXTENSION Max-RTWP-perCellPortion-InformationList-LCR-PSCH-ReconfRqst		PRESENCE optional },
	...
}

Max-RTWP-perCellPortion-InformationList-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1.. maxNrOfCellPortionsPerCellLCR)) OF Max-RTWP-perCellPortion-InformationItem-LCR-PSCH-ReconfRqst

Max-RTWP-perCellPortion-InformationItem-LCR-PSCH-ReconfRqst ::= SEQUENCE {
	cellPortionLCRID								CellPortionLCRID,
	maximum-Target-ReceivedTotalWideBandPower-LCR	Maximum-Target-ReceivedTotalWideBandPower-LCR,
	iE-Extensions		ProtocolExtensionContainer { { Max-RTWP-perCellPortion-InformationItem-LCR-PSCH-ReconfRqst-ExtIEs} }	OPTIONAL,
	...
}

Max-RTWP-perCellPortion-InformationItem-LCR-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE
--
-- **************************************************************

PhysicalSharedChannelReconfigurationResponse ::= SEQUENCE {
	protocolIEs			ProtocolIE-Container  		{{PhysicalSharedChannelReconfigurationResponse-IEs}},
	protocolExtensions	ProtocolExtensionContainer {{PhysicalSharedChannelReconfigurationResponse-Extensions}}                   OPTIONAL,
	...
}

PhysicalSharedChannelReconfigurationResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CriticalityDiagnostics		CRITICALITY		ignore		TYPE		CriticalityDiagnostics		PRESENCE	optional	},
	...
}

PhysicalSharedChannelReconfigurationResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-HICH-TimeOffset								CRITICALITY reject	EXTENSION E-HICH-TimeOffset						PRESENCE optional }|
	{ ID id-E-HICH-TimeOffsetLCR							CRITICALITY reject	EXTENSION E-HICH-TimeOffsetLCR					PRESENCE optional }|
	{ ID id-HSDSCH-Common-System-Information-ResponseFDD	CRITICALITY ignore	EXTENSION HSDSCH-Common-System-Information-ResponseFDD			PRESENCE optional }|
	{ ID id-HSDSCH-Paging-System-Information-ResponseFDD	CRITICALITY ignore	EXTENSION HSDSCH-Paging-System-Information-ResponseFDD			PRESENCE optional }|
	{ ID id-UARFCNforNt										CRITICALITY reject	EXTENSION UARFCN										PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD when using multiple frequencies. This is the UARFCN for the first Frequency repetition.
	{ ID id-E-HICH-TimeOffset-Extension						CRITICALITY reject	EXTENSION E-HICH-TimeOffset-ExtensionLCR		PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD when using multiple frequencies. This E-HICH-TimeOffset-ExtensionLCR is the E-HICH Time Offset LCR for the 2nd and beyond frequencies.
	{ ID id-Common-EDCH-System-Information-ResponseFDD		CRITICALITY ignore	EXTENSION Common-EDCH-System-Information-ResponseFDD		PRESENCE optional }|
	-- FDD only
	{ ID id-HSDSCH-Common-System-Information-ResponseLCR	CRITICALITY ignore	EXTENSION HSDSCH-Common-System-Information-ResponseLCR			PRESENCE optional }|
	{ ID id-HSDSCH-Paging-System-Information-ResponseLCR	CRITICALITY ignore	EXTENSION HSDSCH-Paging-System-Information-ResponseLCR			PRESENCE optional }|
	{ ID id-Common-EDCH-System-Information-ResponseLCR		CRITICALITY ignore	EXTENSION Common-EDCH-System-Information-ResponseLCR		PRESENCE optional }|
	{ ID id-Common-E-RGCH-InfoFDD							CRITICALITY ignore	EXTENSION Common-E-RGCH-InfoFDD					PRESENCE optional },
	...
}

E-HICH-TimeOffset-ExtensionLCR ::= SEQUENCE (SIZE (1..maxFrequencyinCell-1)) OF ProtocolIE-Single-Container{{ Multiple-E-HICH-TimeOffsetLCR }}

Multiple-E-HICH-TimeOffsetLCR NBAP-PROTOCOL-IES ::= {
	{ ID id-MultipleFreq-E-HICH-TimeOffsetLCR	CRITICALITY reject	TYPE	MultipleFreq-E-HICH-TimeOffsetLCR PRESENCE optional }
}
MultipleFreq-E-HICH-TimeOffsetLCR ::= SEQUENCE {
	e-HICH-TimeOffsetLCR					E-HICH-TimeOffsetLCR,
	uARFCN									UARFCN,
	iE-Extensions							ProtocolExtensionContainer { { MultipleFreq-E-HICH-TimeOffsetLCR-ExtIEs} }		OPTIONAL,
	...
}
MultipleFreq-E-HICH-TimeOffsetLCR-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE
--
-- **************************************************************

PhysicalSharedChannelReconfigurationFailure ::= SEQUENCE {
	protocolIEs			ProtocolIE-Container  		{{PhysicalSharedChannelReconfigurationFailure-IEs}},
	protocolExtensions	ProtocolExtensionContainer {{PhysicalSharedChannelReconfigurationFailure-Extensions}}                   OPTIONAL,
	...
}

PhysicalSharedChannelReconfigurationFailure-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CauseLevel-PSCH-ReconfFailure		CRITICALITY ignore	TYPE CauseLevel-PSCH-ReconfFailure	PRESENCE mandatory }|
	{ ID id-CriticalityDiagnostics				CRITICALITY ignore	TYPE CriticalityDiagnostics		PRESENCE optional },
	...
}

PhysicalSharedChannelReconfigurationFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-HICH-TimeOffset-ReconfFailureTDD		CRITICALITY ignore	EXTENSION E-HICH-TimeOffset-ReconfFailureTDD				PRESENCE optional }|
	{ ID id-Common-System-Information-ResponseLCR	CRITICALITY ignore	EXTENSION Common-System-Information-ResponseLCR			PRESENCE optional },
	...
}

CauseLevel-PSCH-ReconfFailure ::= CHOICE {
	generalCause								GeneralCauseList-PSCH-ReconfFailure,
	setSpecificCause							SetSpecificCauseList-PSCH-ReconfFailureTDD,
	...,
	extension-CauseLevel-PSCH-ReconfFailure		Extension-CauseLevel-PSCH-ReconfFailure
}


GeneralCauseList-PSCH-ReconfFailure ::= SEQUENCE {
	cause						Cause,
	iE-Extensions				ProtocolExtensionContainer { { GeneralCauseItem-PSCH-ReconfFailure-ExtIEs} }		OPTIONAL,
	...
}

GeneralCauseItem-PSCH-ReconfFailure-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SetSpecificCauseList-PSCH-ReconfFailureTDD ::= SEQUENCE {
	unsuccessful-PDSCHSetList-PSCH-ReconfFailureTDD	Unsuccessful-PDSCHSetList-PSCH-ReconfFailureTDD		OPTIONAL,
	unsuccessful-PUSCHSetList-PSCH-ReconfFailureTDD	Unsuccessful-PUSCHSetList-PSCH-ReconfFailureTDD		OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { SetSpecificCauseItem-PSCH-ReconfFailureTDD-ExtIEs} }		OPTIONAL,
	...
}

SetSpecificCauseItem-PSCH-ReconfFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Unsuccessful-PDSCHSetList-PSCH-ReconfFailureTDD ::= SEQUENCE (SIZE (0.. maxNrOfPDSCHSets)) OF ProtocolIE-Single-Container {{ Unsuccessful-PDSCHSetItemIE-PSCH-ReconfFailureTDD }}

Unsuccessful-PDSCHSetItemIE-PSCH-ReconfFailureTDD NBAP-PROTOCOL-IES ::= {
	{ ID	id-Unsuccessful-PDSCHSetItem-PSCH-ReconfFailureTDD	CRITICALITY ignore	TYPE Unsuccessful-PDSCHSetItem-PSCH-ReconfFailureTDD	PRESENCE mandatory}
}

Unsuccessful-PDSCHSetItem-PSCH-ReconfFailureTDD ::= SEQUENCE {
	pDSCHSet-ID				PDSCHSet-ID,
	cause					Cause,
	iE-Extensions			ProtocolExtensionContainer { {Unsuccessful-PDSCHSetItem-PSCH-ReconfFailureTDD-ExtIEs} }		OPTIONAL,
	...
}

Unsuccessful-PDSCHSetItem-PSCH-ReconfFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Unsuccessful-PUSCHSetList-PSCH-ReconfFailureTDD ::= SEQUENCE (SIZE (0.. maxNrOfPUSCHSets)) OF ProtocolIE-Single-Container {{ Unsuccessful-PUSCHSetItemIE-PSCH-ReconfFailureTDD }}

Unsuccessful-PUSCHSetItemIE-PSCH-ReconfFailureTDD NBAP-PROTOCOL-IES ::= {
	{ ID	id-Unsuccessful-PUSCHSetItem-PSCH-ReconfFailureTDD	CRITICALITY ignore	TYPE Unsuccessful-PUSCHSetItem-PSCH-ReconfFailureTDD	PRESENCE mandatory}
}

Unsuccessful-PUSCHSetItem-PSCH-ReconfFailureTDD ::= SEQUENCE {
	pUSCHSet-ID				PUSCHSet-ID,
	cause					Cause,
	iE-Extensions			ProtocolExtensionContainer { {Unsuccessful-PUSCHSetItem-PSCH-ReconfFailureTDD-ExtIEs} }		OPTIONAL,
	...
}

Unsuccessful-PUSCHSetItem-PSCH-ReconfFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Extension-CauseLevel-PSCH-ReconfFailure	::= ProtocolIE-Single-Container {{ Extension-CauseLevel-PSCH-ReconfFailureIE }}

Extension-CauseLevel-PSCH-ReconfFailureIE NBAP-PROTOCOL-IES ::= {
	{ ID id-UARFCNSpecificCauseList	CRITICALITY ignore	TYPE UARFCNSpecificCauseList-PSCH-ReconfFailureTDD	PRESENCE mandatory }
}

UARFCNSpecificCauseList-PSCH-ReconfFailureTDD ::= SEQUENCE (SIZE (0.. maxFrequencyinCell)) OF ProtocolIE-Single-Container {{ Unsuccessful-UARFCNItemIE-PSCH-ReconfFailureTDD }}

Unsuccessful-UARFCNItemIE-PSCH-ReconfFailureTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-Unsuccessful-UARFCNItem-PSCH-ReconfFailureTDD	CRITICALITY ignore	TYPE Unsuccessful-UARFCNItem-PSCH-ReconfFailureTDD	PRESENCE mandatory }
}

Unsuccessful-UARFCNItem-PSCH-ReconfFailureTDD ::= SEQUENCE {
	uARFCN					UARFCN,
	-- Used for 1.28 Mcps TDD to indicate the carrier on which HSDPA or HSUPA resources configuration failure occurs.
	cause					Cause,
	iE-Extensions			ProtocolExtensionContainer { {Unsuccessful-UARFCNItem-PSCH-ReconfFailureTDD-ExtIEs} }		OPTIONAL,
	...
}

Unsuccessful-UARFCNItem-PSCH-ReconfFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-HS-Cause	CRITICALITY	ignore		EXTENSION	Cause		PRESENCE	optional}|
	-- Used to indicate the cause of HSDPA related configuration failure.
	{ ID	id-E-Cause	CRITICALITY	ignore		EXTENSION	Cause		PRESENCE	optional},
	-- Used to indicate the cause of E-DCH related configuration failure.
	...
}

E-HICH-TimeOffset-ReconfFailureTDD ::= SEQUENCE (SIZE (1..maxFrequencyinCell)) OF ProtocolIE-Single-Container{{ Multiple-E-HICH-TimeOffsetLCR }}

Common-System-Information-ResponseLCR::= SEQUENCE {
	hSDSCH-Common-System-Information-ResponseLCR		HSDSCH-Common-System-Information-ResponseLCR,
	hSDSCH-Paging-System-Information-ResponseLCR		HSDSCH-Paging-System-Information-ResponseLCR		OPTIONAL,
	common-EDCH-System-Information-ResponseLCR		Common-EDCH-System-Information-ResponseLCR,
	iE-Extensions										ProtocolExtensionContainer { { Common-System-Information-ResponseLCR-ExtIEs } }		OPTIONAL,
	...
}

Common-System-Information-ResponseLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RESET REQUEST
--
-- **************************************************************

ResetRequest ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{ResetRequest-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{ResetRequest-Extensions}}		OPTIONAL,
	...
}

ResetRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ID	id-ResetIndicator		CRITICALITY	ignore		TYPE 	ResetIndicator		PRESENCE 	mandatory},
	...
}

ResetRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ResetIndicator ::= CHOICE {
	communicationContext			CommunicationContextList-Reset,
	communicationControlPort		CommunicationControlPortList-Reset,
	nodeB							NULL,
	...
}

CommunicationContextList-Reset ::= SEQUENCE {
	communicationContextInfoList-Reset		CommunicationContextInfoList-Reset,
	iE-Extensions							ProtocolExtensionContainer  { {CommunicationContextItem-Reset-ExtIEs} }		OPTIONAL,
	...
}

CommunicationContextItem-Reset-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CommunicationContextInfoList-Reset ::= SEQUENCE (SIZE (1.. maxCommunicationContext))	OF ProtocolIE-Single-Container {{ CommunicationContextInfoItemIE-Reset }}

CommunicationContextInfoItemIE-Reset NBAP-PROTOCOL-IES ::= {
	{ID id-CommunicationContextInfoItem-Reset		CRITICALITY reject		TYPE CommunicationContextInfoItem-Reset		PRESENCE mandatory}
}

CommunicationContextInfoItem-Reset ::= SEQUENCE {
	communicationContextType-Reset			CommunicationContextType-Reset,
	iE-Extensions							ProtocolExtensionContainer  { { CommunicationContextInfoItem-Reset-ExtIEs} }		OPTIONAL,
	...
}

CommunicationContextInfoItem-Reset-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CommunicationContextType-Reset ::= CHOICE {
	cRNC-CommunicationContextID				CRNC-CommunicationContextID,
	nodeB-CommunicationContextID			NodeB-CommunicationContextID,
	...
}

CommunicationControlPortList-Reset ::= SEQUENCE {
	communicationControlPortInfoList-Reset		CommunicationControlPortInfoList-Reset,
	iE-Extensions								ProtocolExtensionContainer  { {CommunicationControlPortItem-Reset-ExtIEs} }		OPTIONAL,
	...
}

CommunicationControlPortItem-Reset-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CommunicationControlPortInfoList-Reset ::= SEQUENCE (SIZE (1.. maxCCPinNodeB))	OF ProtocolIE-Single-Container {{CommunicationControlPortInfoItemIE-Reset }}

CommunicationControlPortInfoItemIE-Reset NBAP-PROTOCOL-IES ::= {
	{ID id-CommunicationControlPortInfoItem-Reset		CRITICALITY reject		TYPE CommunicationControlPortInfoItem-Reset		PRESENCE mandatory}
}

CommunicationControlPortInfoItem-Reset ::= SEQUENCE {
	communicationControlPortID			CommunicationControlPortID,
	iE-Extensions						ProtocolExtensionContainer { {CommunicationControlPortInfoItem-Reset-ExtIEs} }	OPTIONAL,
	...
}

CommunicationControlPortInfoItem-Reset-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RESET RESPONSE
--
-- **************************************************************

ResetResponse ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{ResetResponse-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{ResetResponse-Extensions}}     		OPTIONAL,
	...
}

ResetResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ID	id-CriticalityDiagnostics		CRITICALITY		ignore		TYPE	CriticalityDiagnostics		PRESENCE	optional},
	...
}

ResetResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- INFORMATION EXCHANGE INITIATION REQUEST
--
-- **************************************************************

InformationExchangeInitiationRequest ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{InformationExchangeInitiationRequest-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{InformationExchangeInitiationRequest-Extensions}}		OPTIONAL,
	...
}

InformationExchangeInitiationRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-InformationExchangeID						CRITICALITY	reject		TYPE InformationExchangeID					PRESENCE mandatory }|
	{ ID id-InformationExchangeObjectType-InfEx-Rqst	CRITICALITY	reject		TYPE InformationExchangeObjectType-InfEx-Rqst	PRESENCE mandatory }|
	{ ID id-InformationType								CRITICALITY	reject		TYPE InformationType					PRESENCE mandatory }|
	{ ID id-InformationReportCharacteristics			CRITICALITY	reject		TYPE InformationReportCharacteristics				PRESENCE mandatory },
	...
}

InformationExchangeInitiationRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

InformationExchangeObjectType-InfEx-Rqst ::= CHOICE {
	cell							Cell-InfEx-Rqst,
	...
}

Cell-InfEx-Rqst ::= SEQUENCE {
	c-ID							C-ID,
	iE-Extensions					ProtocolExtensionContainer  { { CellItem-InfEx-Rqst-ExtIEs} }		OPTIONAL,
	...
}

CellItem-InfEx-Rqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- INFORMATION EXCHANGE INITIATION RESPONSE
--
-- **************************************************************

InformationExchangeInitiationResponse ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{InformationExchangeInitiationResponse-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{InformationExchangeInitiationResponse-Extensions}}		OPTIONAL,
	...
}

InformationExchangeInitiationResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-InformationExchangeID					CRITICALITY	ignore	TYPE InformationExchangeID		PRESENCE mandatory }|
	{ ID id-InformationExchangeObjectType-InfEx-Rsp	CRITICALITY	ignore	TYPE InformationExchangeObjectType-InfEx-Rsp	PRESENCE optional }|
	{ ID id-CriticalityDiagnostics					CRITICALITY	ignore	TYPE CriticalityDiagnostics		PRESENCE optional },
	...
}

InformationExchangeInitiationResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

InformationExchangeObjectType-InfEx-Rsp ::= CHOICE {
 	cell						Cell-InfEx-Rsp,
	...
 }

Cell-InfEx-Rsp ::= SEQUENCE {
 	requestedDataValue			    RequestedDataValue,
	iE-Extensions					ProtocolExtensionContainer  { { CellItem-InfEx-Rsp-ExtIEs} }		OPTIONAL,
	...
 }

CellItem-InfEx-Rsp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- INFORMATION EXCHANGE INITIATION FAILURE
--
-- **************************************************************

InformationExchangeInitiationFailure ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{InformationExchangeInitiationFailure-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{InformationExchangeInitiationFailure-Extensions}}		OPTIONAL,
	...
}

InformationExchangeInitiationFailure-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-InformationExchangeID		CRITICALITY ignore			TYPE InformationExchangeID		PRESENCE	mandatory	}|
	{ ID id-Cause						CRITICALITY ignore			TYPE Cause						PRESENCE	mandatory	}|
	{ ID id-CriticalityDiagnostics		CRITICALITY ignore			TYPE CriticalityDiagnostics		PRESENCE	optional	},
	...
}

InformationExchangeInitiationFailure-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- INFORMATION REPORT
--
-- **************************************************************

InformationReport ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container	{{InformationReport-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{InformationReport-Extensions}}		OPTIONAL,
	...
}

InformationReport-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-InformationExchangeID						CRITICALITY	ignore	TYPE InformationExchangeID				PRESENCE mandatory }|
	{ ID id-InformationExchangeObjectType-InfEx-Rprt	CRITICALITY	ignore	TYPE InformationExchangeObjectType-InfEx-Rprt		PRESENCE mandatory },
	...
}

InformationReport-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

InformationExchangeObjectType-InfEx-Rprt ::= CHOICE {
	cell							Cell-Inf-Rprt,
	...
 }

Cell-Inf-Rprt ::= SEQUENCE {
	requestedDataValueInformation	RequestedDataValueInformation,
	iE-Extensions					ProtocolExtensionContainer  {{ CellItem-Inf-Rprt-ExtIEs }}		OPTIONAL,
	...

 }

CellItem-Inf-Rprt-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- INFORMATION EXCHANGE TERMINATION REQUEST
--
-- **************************************************************

InformationExchangeTerminationRequest ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{InformationExchangeTerminationRequest-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{InformationExchangeTerminationRequest-Extensions}}		OPTIONAL,
	...
}

InformationExchangeTerminationRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-InformationExchangeID			CRITICALITY		ignore				TYPE	InformationExchangeID			PRESENCE	mandatory},
	...
}

InformationExchangeTerminationRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- INFORMATION EXCHANGE FAILURE INDICATION
--
-- **************************************************************

InformationExchangeFailureIndication ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container			{{InformationExchangeFailureIndication-IEs}},
	protocolExtensions			ProtocolExtensionContainer	{{InformationExchangeFailureIndication-Extensions}}				OPTIONAL,
	...
}

InformationExchangeFailureIndication-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-InformationExchangeID	CRITICALITY ignore			TYPE InformationExchangeID		PRESENCE mandatory }|
	{ ID id-Cause					CRITICALITY ignore			TYPE Cause						PRESENCE mandatory },
	...
}

InformationExchangeFailureIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- CELL SYNCHRONISATION INITIATION REQUEST TDD
--
-- **************************************************************

CellSynchronisationInitiationRequestTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSynchronisationInitiationRequestTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSynchronisationInitiationRequestTDD-Extensions}}     OPTIONAL,
	...
}

CellSynchronisationInitiationRequestTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-C-ID							CRITICALITY		reject		TYPE	C-ID							PRESENCE	mandatory	}|
	{ ID	id-cellSyncBurstRepetitionPeriod			CRITICALITY		reject		TYPE	CellSyncBurstRepetitionPeriod		PRESENCE	mandatory	}|
	{ ID	id-timeslotInfo-CellSyncInitiationRqstTDD	CRITICALITY 	reject		TYPE	TimeslotInfo-CellSyncInitiationRqstTDD		PRESENCE 	optional	}|	-- Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD.
	{ ID	id-CellSyncBurstTransInit-CellSyncInitiationRqstTDD		CRITICALITY 	reject		TYPE	CellSyncBurstTransInit-CellSyncInitiationRqstTDD		PRESENCE 	optional	}|	-- Applicable to 3.84Mcps TDD only
	{ ID	id-CellSyncBurstMeasureInit-CellSyncInitiationRqstTDD		CRITICALITY 	reject		TYPE	CellSyncBurstMeasureInit-CellSyncInitiationRqstTDD		PRESENCE 	optional	},	-- Applicable to 3.84Mcps TDD only
	...
}

CellSynchronisationInitiationRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-SYNCDlCodeId-TransInitLCR-CellSyncInitiationRqstTDD		CRITICALITY reject	EXTENSION SYNCDlCodeId-TransInitLCR-CellSyncInitiationRqstTDD	PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
	{ ID id-SYNCDlCodeId-MeasureInitLCR-CellSyncInitiationRqstTDD	CRITICALITY reject	EXTENSION SYNCDlCodeId-MeasureInitLCR-CellSyncInitiationRqstTDD	PRESENCE optional },	-- Applicable to 1.28Mcps TDD only
	...
}

TimeslotInfo-CellSyncInitiationRqstTDD::= SEQUENCE (SIZE (1..15)) OF TimeSlot

CellSyncBurstTransInit-CellSyncInitiationRqstTDD::= SEQUENCE {
	cSBTransmissionID						CSBTransmissionID,
	sfn										SFN,
	cellSyncBurstCode						CellSyncBurstCode,
	cellSyncBurstCodeShift					CellSyncBurstCodeShift,
	initialDLTransPower						DL-Power,
	iE-Extensions							ProtocolExtensionContainer { { CellSyncBurstTransInit-CellSyncInitiationRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

CellSyncBurstTransInit-CellSyncInitiationRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSyncBurstMeasureInit-CellSyncInitiationRqstTDD::= SEQUENCE {
	cSBMeasurementID						CSBMeasurementID,
	cellSyncBurstCode						CellSyncBurstCode,
	cellSyncBurstCodeShift					CellSyncBurstCodeShift,
	synchronisationReportType				SynchronisationReportType,
	sfn										SFN										OPTIONAL,
	synchronisationReportCharacteristics	SynchronisationReportCharacteristics,
	iE-Extensions							ProtocolExtensionContainer { { CellSyncBurstMeasureInit-CellSyncInitiationRqstTDD-ExtIEs} }		OPTIONAL,
	...
 }

CellSyncBurstMeasureInit-CellSyncInitiationRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SYNCDlCodeId-TransInitLCR-CellSyncInitiationRqstTDD::= SEQUENCE {
	cSBTransmissionID						CSBTransmissionID,
	sfn										SFN,
	uARFCN									UARFCN,
	sYNCDlCodeId							SYNCDlCodeId,
	dwPCH-Power								DwPCH-Power,
	iE-Extensions							ProtocolExtensionContainer { { SYNCDlCodeId-TransInitLCR-CellSyncInitiationRqstTDD-ExtIEs } }	OPTIONAL,
	...
}

SYNCDlCodeId-TransInitLCR-CellSyncInitiationRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SYNCDlCodeId-MeasureInitLCR-CellSyncInitiationRqstTDD::= SEQUENCE {
	cSBMeasurementID						CSBMeasurementID,
	sfn										SFN										OPTIONAL,
	uARFCN									UARFCN,
	sYNCDlCodeId							SYNCDlCodeId,
	synchronisationReportType				SynchronisationReportType,
	synchronisationReportCharacteristics	SynchronisationReportCharacteristics,
	iE-Extensions							ProtocolExtensionContainer { { SYNCDlCodeId-MeasureInitLCR-CellSyncInitiationRqstTDD-ExtIEs } }	OPTIONAL,
	...
}

SYNCDlCodeId-MeasureInitLCR-CellSyncInitiationRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- CELL SYNCHRONISATION INITIATION RESPONSE TDD
--
-- **************************************************************

CellSynchronisationInitiationResponseTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSynchronisationInitiationResponseTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSynchronisationInitiationResponseTDD-Extensions}}     OPTIONAL,
	...
}

CellSynchronisationInitiationResponseTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSynchronisationInitiationResponseTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CriticalityDiagnostics			CRITICALITY ignore		TYPE CriticalityDiagnostics			PRESENCE optional },
	...
}

-- **************************************************************
--
-- CELL SYNCHRONISATION INITIATION FAILURE TDD
--
-- **************************************************************

CellSynchronisationInitiationFailureTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSynchronisationInitiationFailureTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSynchronisationInitiationFailureTDD-Extensions}}     OPTIONAL,
	...
}

CellSynchronisationInitiationFailureTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSynchronisationInitiationFailureTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-Cause							CRITICALITY ignore		TYPE Cause						PRESENCE mandatory }|
	{ ID id-CriticalityDiagnostics			CRITICALITY ignore		TYPE CriticalityDiagnostics		PRESENCE optional },
	...
}

-- **************************************************************
--
-- CELL SYNCHRONISATION RECONFIGURATION REQUEST TDD
--
-- **************************************************************

CellSynchronisationReconfigurationRequestTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSynchronisationReconfigurationRequestTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSynchronisationReconfigurationRequestTDD-Extensions}}     OPTIONAL,
	...
}

CellSynchronisationReconfigurationRequestTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-C-ID							CRITICALITY		reject		TYPE	C-ID							PRESENCE		mandatory	}|
	{ ID	id-TimeSlot						CRITICALITY		reject		TYPE	TimeSlot						PRESENCE 	mandatory	}|
	-- Applicable to 3.84Mcps TDD only. For 1.28Mcps TDD, the CRNC should set this to 0 and the Node B shall ignore it.
	{ ID	id-NCyclesPerSFNperiod			CRITICALITY		reject		TYPE	NCyclesPerSFNperiod			PRESENCE 	mandatory	}|
	{ ID	id-NRepetitionsPerCyclePeriod	CRITICALITY		reject		TYPE	NRepetitionsPerCyclePeriod PRESENCE 	mandatory	}|
	{ ID	id-CellSyncBurstTransReconfInfo-CellSyncReconfRqstTDD		CRITICALITY 	reject		TYPE	CellSyncBurstTransReconfInfo-CellSyncReconfRqstTDD		PRESENCE 	optional	}|	-- Applicable to 3.84Mcps TDD only
	{ ID	id-CellSyncBurstMeasReconfiguration-CellSyncReconfRqstTDD		CRITICALITY 	reject		TYPE	CellSyncBurstMeasInfo-CellSyncReconfRqstTDD		PRESENCE 	optional	},	-- Applicable to 3.84Mcps TDD only
	...
}

CellSynchronisationReconfigurationRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-NSubCyclesPerCyclePeriod-CellSyncReconfRqstTDD				CRITICALITY reject	EXTENSION	NSubCyclesPerCyclePeriod										PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
	{ ID id-SYNCDlCodeIdTransReconfInfoLCR-CellSyncReconfRqstTDD			CRITICALITY reject	EXTENSION	SYNCDlCodeIdTransReconfInfoLCR-CellSyncReconfRqstTDD			PRESENCE optional }|	-- Applicable to 1.28Mcps TDD only
	{ ID id-SYNCDlCodeIdMeasReconfigurationLCR-CellSyncReconfRqstTDD		CRITICALITY reject	EXTENSION	SYNCDlCodeIdMeasInfoLCR-CellSyncReconfRqstTDD		PRESENCE optional },	-- Applicable to 1.28Mcps TDD only
	...
}

CellSyncBurstTransReconfInfo-CellSyncReconfRqstTDD ::= SEQUENCE (SIZE (1.. maxNrOfCellSyncBursts)) OF CellSyncBurstTransInfoItem-CellSyncReconfRqstTDD

CellSyncBurstTransInfoItem-CellSyncReconfRqstTDD ::= SEQUENCE {
	cSBTransmissionID							CSBTransmissionID,
	syncFrameNumberToTransmit					SyncFrameNumber,
	cellSyncBurstCode							CellSyncBurstCode			OPTIONAL,
	cellSyncBurstCodeShift						CellSyncBurstCodeShift		OPTIONAL,
	dlTransPower								DL-Power					OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { CellSyncBurstTransInfoItem-CellSyncReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

CellSyncBurstTransInfoItem-CellSyncReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


CellSyncBurstMeasInfo-CellSyncReconfRqstTDD ::= SEQUENCE {
	cellSyncBurstMeasInfoList-CellSyncReconfRqstTDD		CellSyncBurstMeasInfoList-CellSyncReconfRqstTDD,
	synchronisationReportType							SynchronisationReportTypeIE				OPTIONAL,
	synchronisationReportCharacteristics				SynchronisationReportCharacteristicsIE	OPTIONAL,
	iE-Extensions										ProtocolExtensionContainer { { CellSyncBurstMeasInfo-CellSyncReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

CellSyncBurstMeasInfo-CellSyncReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSyncBurstMeasInfoList-CellSyncReconfRqstTDD ::= ProtocolIE-Single-Container {{ CellSyncBurstMeasInfoListIEs-CellSyncReconfRqstTDD }}

CellSyncBurstMeasInfoListIEs-CellSyncReconfRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-CellSyncBurstMeasInfoList-CellSyncReconfRqstTDD   CRITICALITY reject	TYPE CellSyncBurstMeasInfoListIE-CellSyncReconfRqstTDD		PRESENCE mandatory }
}

SynchronisationReportTypeIE ::= ProtocolIE-Single-Container {{ SynchronisationReportTypeIEs }}

SynchronisationReportTypeIEs NBAP-PROTOCOL-IES ::= {
	{ ID id-SynchronisationReportType					CRITICALITY reject	TYPE SynchronisationReportType			 				PRESENCE	mandatory }
}

SynchronisationReportCharacteristicsIE ::= ProtocolIE-Single-Container {{ SynchronisationReportCharacteristicsIEs }}

SynchronisationReportCharacteristicsIEs NBAP-PROTOCOL-IES ::= {
	{ ID id-SynchronisationReportCharacteristics		CRITICALITY reject	TYPE SynchronisationReportCharacteristics		 	PRESENCE	mandatory }
}


CellSyncBurstMeasInfoListIE-CellSyncReconfRqstTDD ::= SEQUENCE (SIZE (1.. maxNrOfCellSyncBursts)) OF CellSyncBurstMeasInfoItem-CellSyncReconfRqstTDD

CellSyncBurstMeasInfoItem-CellSyncReconfRqstTDD ::= SEQUENCE {
	syncFrameNrToReceive					SyncFrameNumber,
	syncBurstInfo							CellSyncBurstInfoList-CellSyncReconfRqstTDD,
	iE-Extensions							ProtocolExtensionContainer { { CellSyncBurstMeasInfoItem-CellSyncReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

CellSyncBurstMeasInfoItem-CellSyncReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSyncBurstInfoList-CellSyncReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfReceptsPerSyncFrame)) OF CellSyncBurstInfoItem-CellSyncReconfRqstTDD

CellSyncBurstInfoItem-CellSyncReconfRqstTDD ::= SEQUENCE {
	cSBMeasurementID							CSBMeasurementID,
	cellSyncBurstCode							CellSyncBurstCode,
	cellSyncBurstCodeShift						CellSyncBurstCodeShift,
	iE-Extensions								ProtocolExtensionContainer { { CellSyncBurstInfoItem-CellSyncReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

CellSyncBurstInfoItem-CellSyncReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SYNCDlCodeIdTransReconfInfoLCR-CellSyncReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfSyncFramesLCR)) OF SYNCDlCodeIdTransReconfItemLCR-CellSyncReconfRqstTDD

SYNCDlCodeIdTransReconfItemLCR-CellSyncReconfRqstTDD ::= SEQUENCE {
	cSBTransmissionID							CSBTransmissionID,
	syncFrameNumberforTransmit					SyncFrameNumber,
	uARFCN										UARFCN,
	sYNCDlCodeId								SYNCDlCodeId	OPTIONAL,
	dwPCH-Power									DwPCH-Power		OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { SYNCDlCodeIdTransReconfInfoLCR-CellSyncReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

SYNCDlCodeIdTransReconfInfoLCR-CellSyncReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


SYNCDlCodeIdMeasInfoLCR-CellSyncReconfRqstTDD::= SEQUENCE {

	sYNCDlCodeIdMeasInfoList					SYNCDlCodeIdMeasInfoList-CellSyncReconfRqstTDD,
	synchronisationReportType					SynchronisationReportType						OPTIONAL,
	synchronisationReportCharacteristics		SynchronisationReportCharacteristics   		OPTIONAL,
	iE-Extensions		ProtocolExtensionContainer	 { { SYNCDlCodeIdMeasInfoLCR-CellSyncReconfRqstTDD-ExtIEs} } OPTIONAL,
	...
}

SYNCDlCodeIdMeasInfoLCR-CellSyncReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SYNCDlCodeIdMeasInfoList-CellSyncReconfRqstTDD::= SEQUENCE (SIZE (1.. maxNrOfSyncDLCodesLCR)) OF SYNCDlCodeIdMeasInfoItem-CellSyncReconfRqstTDD

SYNCDlCodeIdMeasInfoItem-CellSyncReconfRqstTDD ::= SEQUENCE {
	syncFrameNrToReceive					SyncFrameNumber,
	sYNCDlCodeIdInfoLCR						SYNCDlCodeIdInfoListLCR-CellSyncReconfRqstTDD,
	iE-Extensions							ProtocolExtensionContainer { { SYNCDlCodeIdMeasInfoItem-CellSyncReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

SYNCDlCodeIdMeasInfoItem-CellSyncReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SYNCDlCodeIdInfoListLCR-CellSyncReconfRqstTDD ::= SEQUENCE (SIZE (1.. maxNrOfReceptionsperSyncFrameLCR)) OF SYNCDlCodeIdInfoItemLCR-CellSyncReconfRqstTDD

SYNCDlCodeIdInfoItemLCR-CellSyncReconfRqstTDD ::= SEQUENCE {
	cSBMeasurementID							CSBMeasurementID,
	sYNCDlCodeId								SYNCDlCodeId,
	uARFCN										UARFCN,
	propagationDelayCompensation				TimingAdjustmentValueLCR		OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { SYNCDlCodeIdInfoItemLCR-CellSyncReconfRqstTDD-ExtIEs} }		OPTIONAL,
	...
}

SYNCDlCodeIdInfoItemLCR-CellSyncReconfRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- CELL SYNCHRONISATION RECONFIGURATION RESPONSE TDD
--
-- **************************************************************

CellSynchronisationReconfigurationResponseTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSynchronisationReconfigurationResponseTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSynchronisationReconfigurationResponseTDD-Extensions}}     OPTIONAL,
	...
}

CellSynchronisationReconfigurationResponseTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSynchronisationReconfigurationResponseTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CriticalityDiagnostics					CRITICALITY		ignore		TYPE	CriticalityDiagnostics			PRESENCE	optional	},
	...
}

-- **************************************************************
--
-- CELL SYNCHRONISATION RECONFIGURATION FAILURE TDD
--
-- **************************************************************

CellSynchronisationReconfigurationFailureTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSynchronisationReconfigurationFailureTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSynchronisationReconfigurationFailureTDD-Extensions}}     OPTIONAL,
	...
}

CellSynchronisationReconfigurationFailureTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSynchronisationReconfigurationFailureTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-Cause							CRITICALITY ignore		TYPE Cause						PRESENCE mandatory }|
	{ ID id-CriticalityDiagnostics			CRITICALITY ignore		TYPE CriticalityDiagnostics		PRESENCE optional },
	...
}

-- **************************************************************
--
-- CELL SYNCHRONISATION ADJUSTMENT REQUEST TDD
--
-- **************************************************************

CellSynchronisationAdjustmentRequestTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSynchronisationAdjustmentRequestTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSynchronisationAdjustmentRequestTDD-Extensions}}     OPTIONAL,
	...
}

CellSynchronisationAdjustmentRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSynchronisationAdjustmentRequestTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CellAdjustmentInfo-SyncAdjustmntRqstTDD	CRITICALITY	ignore	TYPE CellAdjustmentInfo-SyncAdjustmentRqstTDD	PRESENCE mandatory	},
	...
}

CellAdjustmentInfo-SyncAdjustmentRqstTDD::= SEQUENCE (SIZE (1..maxCellinNodeB)) OF ProtocolIE-Single-Container {{ CellAdjustmentInfoItemIE-SyncAdjustmntRqstTDD }}

CellAdjustmentInfoItemIE-SyncAdjustmntRqstTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-CellAdjustmentInfoItem-SyncAdjustmentRqstTDD	CRITICALITY ignore	TYPE CellAdjustmentInfoItem-SyncAdjustmentRqstTDD	PRESENCE mandatory }
}

CellAdjustmentInfoItem-SyncAdjustmentRqstTDD ::= SEQUENCE {
	c-ID									C-ID,
	frameAdjustmentValue					FrameAdjustmentValue		OPTIONAL,
	timingAdjustmentValue					TimingAdjustmentValue		OPTIONAL,
	dLTransPower							DL-Power					OPTIONAL, -- Applicable to 3.84Mcps TDD only
	sfn										SFN							OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { CellAdjustmentInfoItem-SyncAdjustmntRqstTDD-ExtIEs} }		OPTIONAL,
	...
 }

CellAdjustmentInfoItem-SyncAdjustmntRqstTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DwPCH-Power					CRITICALITY ignore	EXTENSION DwPCH-Power				PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-TimingAdjustmentValueLCR	CRITICALITY ignore	EXTENSION TimingAdjustmentValueLCR	PRESENCE optional },
	-- Applicable to 1.28Mcps TDD only
	...
}

-- **************************************************************
--
-- CELL SYNCHRONISATION ADJUSTMENT RESPONSE TDD
--
-- **************************************************************

CellSynchronisationAdjustmentResponseTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSynchronisationAdjustmentResponseTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSynchronisationAdjustmentResponseTDD-Extensions}}     OPTIONAL,
	...
}

CellSynchronisationAdjustmentResponseTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSynchronisationAdjustmentResponseTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CriticalityDiagnostics			CRITICALITY		ignore		TYPE	CriticalityDiagnostics					PRESENCE	optional	},
	...
}

-- **************************************************************
--
-- CELL SYNCHRONISATION ADJUSTMENT FAILURE TDD
--
-- **************************************************************

CellSynchronisationAdjustmentFailureTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSynchronisationAdjustmentFailureTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSynchronisationAdjustmentFailureTDD-Extensions}}     OPTIONAL,
	...
}

CellSynchronisationAdjustmentFailureTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSynchronisationAdjustmentFailureTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-CauseLevel-SyncAdjustmntFailureTDD	CRITICALITY	ignore		TYPE	CauseLevel-SyncAdjustmntFailureTDD		PRESENCE	mandatory	}|
	{ ID	id-CriticalityDiagnostics				CRITICALITY	ignore		TYPE	CriticalityDiagnostics			PRESENCE	optional	},
	...
}

CauseLevel-SyncAdjustmntFailureTDD ::= CHOICE {
	generalCause			GeneralCauseList-SyncAdjustmntFailureTDD,
	cellSpecificCause		CellSpecificCauseList-SyncAdjustmntFailureTDD,
	...
}

GeneralCauseList-SyncAdjustmntFailureTDD::= SEQUENCE {
	cause										Cause,
	iE-Extensions								ProtocolExtensionContainer { { GeneralCauseList-SyncAdjustmntFailureTDD-ExtIEs} }		OPTIONAL,
	...
}

GeneralCauseList-SyncAdjustmntFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSpecificCauseList-SyncAdjustmntFailureTDD ::= SEQUENCE {
	unsuccessful-cell-InformationRespList-SyncAdjustmntFailureTDD		Unsuccessful-cell-InformationRespList-SyncAdjustmntFailureTDD,
	iE-Extensions								ProtocolExtensionContainer { { CellSpecificCauseList-SyncAdjustmntFailureTDD-ExtIEs} }		OPTIONAL,
	...
}

CellSpecificCauseList-SyncAdjustmntFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Unsuccessful-cell-InformationRespList-SyncAdjustmntFailureTDD ::= SEQUENCE (SIZE (1..maxCellinNodeB))	OF ProtocolIE-Single-Container {{ Unsuccessful-cell-InformationRespItemIE-SyncAdjustmntFailureTDD }}

Unsuccessful-cell-InformationRespItemIE-SyncAdjustmntFailureTDD NBAP-PROTOCOL-IES ::= {
	{ ID	id-Unsuccessful-cell-InformationRespItem-SyncAdjustmntFailureTDD		CRITICALITY		ignore		TYPE	Unsuccessful-cell-InformationRespItem-SyncAdjustmntFailureTDD		PRESENCE	mandatory},
	...
}

Unsuccessful-cell-InformationRespItem-SyncAdjustmntFailureTDD::= SEQUENCE {
	c-ID										C-ID,
	cause										Cause,
	iE-Extensions								ProtocolExtensionContainer { { Unsuccessful-cell-InformationRespItem-SyncAdjustmntFailureTDD-ExtIEs} }		OPTIONAL,
	...
}

Unsuccessful-cell-InformationRespItem-SyncAdjustmntFailureTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- CELL SYNCHRONISATION TERMINATION REQUEST TDD
--
-- **************************************************************

CellSynchronisationTerminationRequestTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSynchronisationTerminationRequestTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSynchronisationTerminationRequestTDD-Extensions}}     OPTIONAL,
	...
}

CellSynchronisationTerminationRequestTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSynchronisationTerminationRequestTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-C-ID							CRITICALITY		ignore		TYPE	C-ID							PRESENCE	mandatory	}|
	{ ID	id-CSBTransmissionID			CRITICALITY		ignore		TYPE	CSBTransmissionID				PRESENCE	optional		}|
	{ ID	id-CSBMeasurementID				CRITICALITY		ignore		TYPE	CSBMeasurementID				PRESENCE	optional		},
	...
}

-- **************************************************************
--
-- CELL SYNCHRONISATION FAILURE INDICATION TDD
--
-- **************************************************************

CellSynchronisationFailureIndicationTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSynchronisationFailureIndicationTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSynchronisationFailureIndicationTDD-Extensions}}     OPTIONAL,
	...
}

CellSynchronisationFailureIndicationTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSynchronisationFailureIndicationTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-C-ID							CRITICALITY		ignore		TYPE	C-ID							PRESENCE	mandatory	}|
	{ ID	id-CSBTransmissionID			CRITICALITY		ignore		TYPE	CSBTransmissionID				PRESENCE	optional		}|
	{ ID	id-CSBMeasurementID				CRITICALITY		ignore		TYPE	CSBMeasurementID				PRESENCE	optional		}|
	{ ID	id-Cause						CRITICALITY		ignore		TYPE	Cause							PRESENCE	mandatory	},
	...
}

-- **************************************************************
--
-- CELL SYNCHRONISATION REPORT TDD
--
-- **************************************************************

CellSynchronisationReportTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{CellSynchronisationReportTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{CellSynchronisationReportTDD-Extensions}}     OPTIONAL,
	...
}

CellSynchronisationReportTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSynchronisationReportTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CellSyncInfo-CellSyncReprtTDD		CRITICALITY ignore		TYPE CellSyncInfo-CellSyncReprtTDD			PRESENCE mandatory },
	...
}

CellSyncInfo-CellSyncReprtTDD ::= SEQUENCE (SIZE (1..maxCellinNodeB))	OF CellSyncInfoItemIE-CellSyncReprtTDD

CellSyncInfoItemIE-CellSyncReprtTDD ::= SEQUENCE {
	c-ID-CellSyncReprtTDD				C-ID-IE-CellSyncReprtTDD,
	syncReportType-CellSyncReprtTDD		SyncReportTypeIE-CellSyncReprtTDD		OPTIONAL,
	...
}

C-ID-IE-CellSyncReprtTDD ::= ProtocolIE-Single-Container {{ C-ID-IEs-CellSyncReprtTDD }}

C-ID-IEs-CellSyncReprtTDD NBAP-PROTOCOL-IES ::= {
	{ ID id-C-ID						CRITICALITY ignore			TYPE C-ID					PRESENCE mandatory }
}

SyncReportTypeIE-CellSyncReprtTDD::= ProtocolIE-Single-Container {{ SyncReportTypeIEs-CellSyncReprtTDD }}

SyncReportTypeIEs-CellSyncReprtTDD NBAP-PROTOCOL-IES ::= {
	{ ID	id-SyncReportType-CellSyncReprtTDD		CRITICALITY	ignore		TYPE SyncReportType-CellSyncReprtTDD		PRESENCE	mandatory}
}


SyncReportType-CellSyncReprtTDD ::= CHOICE {
	intStdPhSyncInfo-CellSyncReprtTDD		IntStdPhCellSyncInfo-CellSyncReprtTDD,
	lateEntrantCell							NULL,
	frequencyAcquisition					NULL,
	...
}

IntStdPhCellSyncInfo-CellSyncReprtTDD ::= SEQUENCE {
	cellSyncBurstMeasuredInfo					CellSyncBurstMeasInfoList-CellSyncReprtTDD,
	iE-Extensions								ProtocolExtensionContainer { { IntStdPhCellSyncInfoList-CellSyncReprtTDD-ExtIEs} }		OPTIONAL,
	...
}

IntStdPhCellSyncInfoList-CellSyncReprtTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-AccumulatedClockupdate-CellSyncReprtTDD		CRITICALITY	ignore	EXTENSION	TimingAdjustmentValue	PRESENCE	optional	}|
	{ ID id-SyncDLCodeIdsMeasInfoList-CellSyncReprtTDD 	CRITICALITY	ignore EXTENSION	SyncDLCodeIdsMeasInfoList-CellSyncReprtTDD	PRESENCE optional }, -- Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD.
	...
}

CellSyncBurstMeasInfoList-CellSyncReprtTDD ::= SEQUENCE (SIZE (0.. maxNrOfCellSyncBursts)) OF CellSyncBurstMeasInfoItem-CellSyncReprtTDD -- Mandatory for 3.84Mcps TDD. Not Applicable to 1.28Mcps TDD.

CellSyncBurstMeasInfoItem-CellSyncReprtTDD ::= SEQUENCE {
	sFN										SFN,
	cellSyncBurstInfo-CellSyncReprtTDD		SEQUENCE (SIZE (1..maxNrOfReceptsPerSyncFrame)) OF CellSyncBurstInfo-CellSyncReprtTDD,
	iE-Extensions							ProtocolExtensionContainer { { CellSyncBurstMeasInfoItem-CellSyncReprtTDD-ExtIEs} }		OPTIONAL,
	...
}

CellSyncBurstMeasInfoItem-CellSyncReprtTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CellSyncBurstInfo-CellSyncReprtTDD ::= CHOICE {
	cellSyncBurstAvailable		CellSyncBurstAvailable-CellSyncReprtTDD,
	cellSyncBurstNotAvailable	NULL,
	...
}

CellSyncBurstAvailable-CellSyncReprtTDD ::= SEQUENCE {
	cellSyncBurstTiming			CellSyncBurstTiming,
	cellSyncBurstSIR			CellSyncBurstSIR,
	iE-Extensions				ProtocolExtensionContainer { { CellSyncBurstAvailable-CellSyncReprtTDD-ExtIEs} }		OPTIONAL,
	...
}

CellSyncBurstAvailable-CellSyncReprtTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SyncDLCodeIdsMeasInfoList-CellSyncReprtTDD ::= SEQUENCE (SIZE (0..maxNrOfSyncFramesLCR)) OF SyncDLCodeIdsMeasInfoItem-CellSyncReprtTDD
-- Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD.

SyncDLCodeIdsMeasInfoItem-CellSyncReprtTDD ::= SEQUENCE {
	sFN										SFN,
	syncDLCodeIdInfo-CellSyncReprtTDD		SyncDLCodeIdInfo-CellSyncReprtTDD,
	iE-Extensions							ProtocolExtensionContainer { { SyncDLCodeIdsMeasInfoItem-CellSyncReprtTDD-ExtIEs } }		OPTIONAL,
	...
}

SyncDLCodeIdsMeasInfoItem-CellSyncReprtTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SyncDLCodeIdInfo-CellSyncReprtTDD ::= SEQUENCE (SIZE (1..maxNrOfReceptionsperSyncFrameLCR)) OF SyncDLCodeIdItem-CellSyncReprtTDD

SyncDLCodeIdItem-CellSyncReprtTDD ::= CHOICE {
	syncDLCodeIdAvailable				SyncDLCodeIdAvailable-CellSyncReprtTDD,
	syncDLCodeIDNotAvailable			NULL,
	...
}

SyncDLCodeIdAvailable-CellSyncReprtTDD ::= SEQUENCE {
	syncDLCodeIdTiming			CellSyncBurstTimingLCR,
	syncDLCodeIdSIR				CellSyncBurstSIR,
	iE-Extensions				ProtocolExtensionContainer { { SyncDLCodeIdAvailable-CellSyncReprtTDD-ExtIEs } }		OPTIONAL,
	...
}

SyncDLCodeIdAvailable-CellSyncReprtTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- BEARER REARRANGEMENT INDICATION
--
-- **************************************************************

BearerRearrangementIndication ::= SEQUENCE {
	protocolIEs                     ProtocolIE-Container       {{BearerRearrangementIndication-IEs}},
	protocolExtensions              ProtocolExtensionContainer {{BearerRearrangementIndication-Extensions}}                   OPTIONAL,
	...
}

BearerRearrangementIndication-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID					CRITICALITY ignore	TYPE CRNC-CommunicationContextID				PRESENCE mandatory } |
	{ ID id-SignallingBearerRequestIndicator			CRITICALITY ignore	TYPE SignallingBearerRequestIndicator				PRESENCE optional } |
	{ ID id-DCH-RearrangeList-Bearer-RearrangeInd		CRITICALITY ignore	TYPE DCH-RearrangeList-Bearer-RearrangeInd			PRESENCE optional } |
	{ ID id-DSCH-RearrangeList-Bearer-RearrangeInd		CRITICALITY ignore	TYPE DSCH-RearrangeList-Bearer-RearrangeInd		PRESENCE optional } |
	-- TDD only.
	{ ID id-USCH-RearrangeList-Bearer-RearrangeInd		CRITICALITY ignore	TYPE USCH-RearrangeList-Bearer-RearrangeInd		PRESENCE optional } |
	-- TDD only.
	{ ID id-HSDSCH-RearrangeList-Bearer-RearrangeInd	CRITICALITY ignore	TYPE HSDSCH-RearrangeList-Bearer-RearrangeInd		PRESENCE optional },
	...
}

BearerRearrangementIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-RearrangeList-Bearer-RearrangeInd		CRITICALITY ignore	EXTENSION E-DCH-RearrangeList-Bearer-RearrangeInd	PRESENCE optional },
	...
}

DCH-RearrangeList-Bearer-RearrangeInd ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-RearrangeItem-Bearer-RearrangeInd

DCH-RearrangeItem-Bearer-RearrangeInd ::= SEQUENCE {
	dCH-ID											DCH-ID,
	iE-Extensions									ProtocolExtensionContainer { { DCH-RearrangeItem-Bearer-RearrangeInd-ExtIEs} }		OPTIONAL,
	...
}

DCH-RearrangeItem-Bearer-RearrangeInd-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DSCH-RearrangeList-Bearer-RearrangeInd ::= SEQUENCE (SIZE (1..maxNrOfDSCHs)) OF DSCH-RearrangeItem-Bearer-RearrangeInd

DSCH-RearrangeItem-Bearer-RearrangeInd ::= SEQUENCE {
	dSCH-ID											DSCH-ID,
	iE-Extensions									ProtocolExtensionContainer { { DSCH-RearrangeItem-Bearer-RearrangeInd-ExtIEs} }		OPTIONAL,
	...
}

DSCH-RearrangeItem-Bearer-RearrangeInd-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

USCH-RearrangeList-Bearer-RearrangeInd ::= SEQUENCE (SIZE (1..maxNrOfUSCHs)) OF USCH-RearrangeItem-Bearer-RearrangeInd

USCH-RearrangeItem-Bearer-RearrangeInd ::= SEQUENCE {
	uSCH-ID											USCH-ID,
	iE-Extensions									ProtocolExtensionContainer { { USCH-RearrangeItem-Bearer-RearrangeInd-ExtIEs} }		OPTIONAL,
	...
}

USCH-RearrangeItem-Bearer-RearrangeInd-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSDSCH-RearrangeList-Bearer-RearrangeInd ::= SEQUENCE (SIZE (1..maxNrOfMACdFlows)) OF HSDSCH-RearrangeItem-Bearer-RearrangeInd

HSDSCH-RearrangeItem-Bearer-RearrangeInd ::= SEQUENCE {
	hsDSCH-MACdFlow-ID								HSDSCH-MACdFlow-ID,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-RearrangeItem-Bearer-RearrangeInd-ExtIEs} }		OPTIONAL,
	...
}

HSDSCH-RearrangeItem-Bearer-RearrangeInd-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-RearrangeList-Bearer-RearrangeInd ::= SEQUENCE (SIZE (1.. maxNrOfEDCHMACdFlows)) OF E-DCH-RearrangeItem-Bearer-RearrangeInd

E-DCH-RearrangeItem-Bearer-RearrangeInd ::= SEQUENCE {
	e-DCH-MACdFlow-ID								E-DCH-MACdFlow-ID,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-RearrangeItem-Bearer-RearrangeInd-ExtIEs} }		OPTIONAL,
	...
}

E-DCH-RearrangeItem-Bearer-RearrangeInd-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Additional-EDCH-Cell-Information-Bearer-Rearrangement		CRITICALITY ignore	EXTENSION	Additional-EDCH-Cell-Information-Bearer-Rearrangement-List			PRESENCE optional },
	...
}

Additional-EDCH-Cell-Information-Bearer-Rearrangement-List	::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-Cell-Information-Bearer-Rearrangement-ItemIEs

Additional-EDCH-Cell-Information-Bearer-Rearrangement-ItemIEs ::= SEQUENCE {
	transport-Bearer-Rearrangement-Indicator-for-Additional-EDCH-Separate-Mode								Transport-Bearer-Rearrangement-Indicator-for-Additional-EDCH-Separate-Mode,
	iE-Extensions									ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-Bearer-Rearrangement-ItemIEs-ExtIEs} }		OPTIONAL,
	...
}

Additional-EDCH-Cell-Information-Bearer-Rearrangement-ItemIEs-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Transport-Bearer-Rearrangement-Indicator-for-Additional-EDCH-Separate-Mode
 ::= ENUMERATED {
	bearer-for-primary-carrier,
	bearer-for-secondary-carrier,
	bearers-for-both-primary-and-secondary-carriers,
	...
}

-- **************************************************************
--
-- RADIO LINK ACTIVATION COMMAND FDD
--
-- **************************************************************

RadioLinkActivationCommandFDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkActivationCommandFDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkActivationCommandFDD-Extensions}}			OPTIONAL,
	...
}

RadioLinkActivationCommandFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-NodeB-CommunicationContextID						CRITICALITY	ignore	TYPE	NodeB-CommunicationContextID								PRESENCE	mandatory	}|
	{ ID	id-DelayedActivationList-RL-ActivationCmdFDD		CRITICALITY	ignore	TYPE	DelayedActivationInformationList-RL-ActivationCmdFDD			PRESENCE	mandatory	},
	...
}

RadioLinkActivationCommandFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DelayedActivationInformationList-RL-ActivationCmdFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { 
	{ DelayedActivationInformation-RL-ActivationCmdFDD-IEs} }

DelayedActivationInformation-RL-ActivationCmdFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-DelayedActivationInformation-RL-ActivationCmdFDD	CRITICALITY ignore	TYPE DelayedActivationInformation-RL-ActivationCmdFDD	PRESENCE optional	}
}

DelayedActivationInformation-RL-ActivationCmdFDD ::= SEQUENCE {
	rL-ID						RL-ID,
	delayed-activation-update	DelayedActivationUpdate,
	iE-Extensions				ProtocolExtensionContainer { { DelayedActivationInformation-RL-ActivationCmdFDD-ExtIEs} } OPTIONAL,
	...
}

DelayedActivationInformation-RL-ActivationCmdFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK ACTIVATION COMMAND TDD
--
-- **************************************************************

RadioLinkActivationCommandTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkActivationCommandTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkActivationCommandTDD-Extensions}}			OPTIONAL,
	...
}

RadioLinkActivationCommandTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-NodeB-CommunicationContextID						CRITICALITY	ignore	TYPE	NodeB-CommunicationContextID								PRESENCE	mandatory	}|
	{ ID	id-DelayedActivationList-RL-ActivationCmdTDD		CRITICALITY	ignore	TYPE	DelayedActivationInformationList-RL-ActivationCmdTDD			PRESENCE	mandatory	},
	...
}

RadioLinkActivationCommandTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DelayedActivationInformationList-RL-ActivationCmdTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { 
	{ DelayedActivationInformation-RL-ActivationCmdTDD-IEs} }

DelayedActivationInformation-RL-ActivationCmdTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-DelayedActivationInformation-RL-ActivationCmdTDD	CRITICALITY ignore	TYPE DelayedActivationInformation-RL-ActivationCmdTDD	PRESENCE optional	}
}

DelayedActivationInformation-RL-ActivationCmdTDD ::= SEQUENCE {
	rL-ID						RL-ID,
	delayed-activation-update	DelayedActivationUpdate,
	iE-Extensions				ProtocolExtensionContainer { { DelayedActivationInformation-RL-ActivationCmdTDD-ExtIEs} } OPTIONAL,
	...
}

DelayedActivationInformation-RL-ActivationCmdTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- RADIO LINK PARAMETER UPDATE INDICATION FDD
--
-- **************************************************************

RadioLinkParameterUpdateIndicationFDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkParameterUpdateIndicationFDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkParameterUpdateIndicationFDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkParameterUpdateIndicationFDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID			CRITICALITY		ignore		TYPE	CRNC-CommunicationContextID			PRESENCE	mandatory	} |
	{ ID id-HSDSCH-FDD-Update-Information		CRITICALITY		ignore		TYPE	HSDSCH-FDD-Update-Information			PRESENCE	optional	},
	...
}

RadioLinkParameterUpdateIndicationFDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-FDD-Update-Information					CRITICALITY ignore	EXTENSION E-DCH-FDD-Update-Information			PRESENCE optional}|
	{ ID id-Additional-HS-Cell-Information-RL-Param-Upd		CRITICALITY ignore	EXTENSION Additional-HS-Cell-Information-RL-Param-Upd		PRESENCE optional}|
	{ ID id-Additional-EDCH-Cell-Information-RL-Param-Upd	CRITICALITY ignore	EXTENSION Additional-EDCH-Cell-Information-RL-Param-Upd		PRESENCE optional}|
	{ ID id-CPC-RecoveryReport								CRITICALITY ignore	EXTENSION CPC-RecoveryReport						PRESENCE optional}|
	{ ID id-UL-CLTD-State-Update-Information				CRITICALITY ignore	EXTENSION UL-CLTD-State-Update-Information	PRESENCE optional}|
	{ ID id-UE-Measurement-Forwarding						CRITICALITY ignore	EXTENSION UE-Measurement-Forwarding				PRESENCE optional}|
	{ ID id-CFN												CRITICALITY ignore	EXTENSION CFN											PRESENCE optional},
	...
}

Additional-HS-Cell-Information-RL-Param-Upd	::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Information-RL-Param-Upd-ItemIEs

Additional-HS-Cell-Information-RL-Param-Upd-ItemIEs	::=SEQUENCE{
	hSPDSCH-RL-ID										RL-ID,
	hS-DSCH-FDD-Secondary-Serving-Update-Information	HS-DSCH-FDD-Secondary-Serving-Update-Information,
	iE-Extensions					ProtocolExtensionContainer { { Additional-HS-Cell-Information-RL-Setup-ExtIEs} } OPTIONAL,
	...
}

Additional-HS-Cell-Information-RL-Setup-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}
Additional-EDCH-Cell-Information-RL-Param-Upd	::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-Cell-Information-RL-Param-Upd-ItemIEs

Additional-EDCH-Cell-Information-RL-Param-Upd-ItemIEs	::=SEQUENCE{
	additional-EDCH-FDD-Update-Information										Additional-EDCH-FDD-Update-Information,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-RL-Param-Upd-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-Cell-Information-RL-Param-Upd-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UE-Measurement-Forwarding ::= SEQUENCE {
	measurementID				MeasurementID,
	uE-Measurement-Value		UE-Measurement-Value,
	iE-Extensions				ProtocolExtensionContainer { {UE-Measurement-Forwarding-ExtIEs} } OPTIONAL,
	...
}

UE-Measurement-Forwarding-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


-- **************************************************************
--
-- RADIO LINK PARAMETER UPDATE INDICATION TDD
--
-- **************************************************************

RadioLinkParameterUpdateIndicationTDD ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container		{{RadioLinkParameterUpdateIndicationTDD-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{RadioLinkParameterUpdateIndicationTDD-Extensions}}		OPTIONAL,
	...
}

RadioLinkParameterUpdateIndicationTDD-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID			CRITICALITY		ignore		TYPE	CRNC-CommunicationContextID			PRESENCE	mandatory	} |
	{ ID id-HSDSCH-TDD-Update-Information		CRITICALITY		ignore		TYPE	HSDSCH-TDD-Update-Information			PRESENCE	optional	},
	...
}

RadioLinkParameterUpdateIndicationTDD-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- MBMS NOTIFICATION UPDATE COMMAND
--
-- **************************************************************

MBMSNotificationUpdateCommand ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container	{{ MBMSNotificationUpdateCommand-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{ MBMSNotificationUpdateCommand-Extensions}}		OPTIONAL,
	...
}

MBMSNotificationUpdateCommand-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-C-ID								CRITICALITY ignore	TYPE C-ID								PRESENCE mandatory	}|
	{ ID id-CommonPhysicalChannelID				CRITICALITY ignore	TYPE CommonPhysicalChannelID			PRESENCE mandatory	}|
	{ ID id-Modification-Period					CRITICALITY ignore	TYPE Modification-Period				PRESENCE optional		}|
	{ ID id-MICH-CFN							CRITICALITY ignore	TYPE MICH-CFN							PRESENCE mandatory	}|
	{ ID id-NI-Information-NotifUpdateCmd		CRITICALITY ignore	TYPE NI-Information						PRESENCE mandatory	},
	...
}

MBMSNotificationUpdateCommand-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}


-- **************************************************************
--
-- UE STATUS UPDATE COMMAND
--
-- **************************************************************

UEStatusUpdateCommand ::= SEQUENCE {
	protocolIEs			ProtocolIE-Container		{{UEStatusUpdateCommand-IEs}},
	protocolExtensions	ProtocolExtensionContainer	{{UEStatusUpdateCommand-Extensions}}	OPTIONAL,
	...
}

UEStatusUpdateCommand-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-Cell-ERNTI-Status-Information					CRITICALITY ignore	TYPE Cell-ERNTI-Status-Information							PRESENCE mandatory },
	...
}

UEStatusUpdateCommand-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- SECONDARY UL FREQUENCY REPORT
--
-- **************************************************************

SecondaryULFrequencyReport ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container	{{SecondaryULFrequencyReport-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{SecondaryULFrequencyReport-Extensions}}			OPTIONAL,
	...
}

SecondaryULFrequencyReport-IEs NBAP-PROTOCOL-IES ::= {
	{ ID	id-NodeB-CommunicationContextID				CRITICALITY	ignore	TYPE	NodeB-CommunicationContextID				PRESENCE	mandatory	}|
	{ ID id-ActivationInformation 	CRITICALITY		ignore		TYPE ActivationInformation		PRESENCE mandatory },
	...
}

SecondaryULFrequencyReport-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- SECONDARY UL FREQUENCY UPDATE INDICATION
--
-- **************************************************************

SecondaryULFrequencyUpdateIndication ::= SEQUENCE {
	protocolIEs				ProtocolIE-Container	{{SecondaryULFrequencyUpdateIndication-IEs}},
	protocolExtensions		ProtocolExtensionContainer	{{SecondaryULFrequencyUpdateIndication-Extensions}}		OPTIONAL,
	...
}


SecondaryULFrequencyUpdateIndication-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-CRNC-CommunicationContextID			CRITICALITY		ignore		TYPE	CRNC-CommunicationContextID			PRESENCE	mandatory	}|
	{ ID id-ActivationInformation 	CRITICALITY		ignore		TYPE ActivationInformation		PRESENCE mandatory },
	...
}

SecondaryULFrequencyUpdateIndication-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- UE STATUS UPDATE CONFIRM REQUEST
--
-- **************************************************************

UEStatusUpdateConfirmRequest ::= SEQUENCE {
	protocolIEs			ProtocolIE-Container		{{UEStatusUpdateConfirmRequest-IEs}},
	protocolExtensions	ProtocolExtensionContainer	{{UEStatusUpdateConfirmRequest-Extensions}}	OPTIONAL,
	...
}

UEStatusUpdateConfirmRequest-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-Cell-ERNTI-Status-Information		CRITICALITY ignore	TYPE Cell-ERNTI-Status-Information	PRESENCE mandatory },
	...
}

UEStatusUpdateConfirmRequest-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- **************************************************************
--
-- UE STATUS UPDATE CONFIRM RESPONSE
--
-- **************************************************************

UEStatusUpdateConfirmResponse ::= SEQUENCE {
	protocolIEs			ProtocolIE-Container		{{UEStatusUpdateConfirmResponse-IEs}},
	protocolExtensions	ProtocolExtensionContainer	{{UEStatusUpdateConfirmResponse-Extensions}}	OPTIONAL,
	...
}

UEStatusUpdateConfirmResponse-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-ERNTI-Release-Status		CRITICALITY ignore	TYPE ERNTI-Release-Status				PRESENCE mandatory },
	...
}

UEStatusUpdateConfirmResponse-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}

END

9.3.4	Information Elements Definitions
--******************************************************************************
--
-- Information Element Definitions
--
--******************************************************************************

NBAP-IEs {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) 
umts-Access (20) modules (3) nbap (2) version1 (1) nbap-IEs (2) }

DEFINITIONS AUTOMATIC TAGS ::=
BEGIN

IMPORTS
	maxNrOfRLs,
	maxNrOfTFCs,
	maxNrOfErrors,
	maxCTFC,
	maxNrOfTFs,
	maxTTI-count,
	maxRateMatching,
	maxHS-PDSCHCodeNrComp-1,
	maxHS-SCCHCodeNrComp-1,
	maxNrOfCellSyncBursts,
	maxNrOfCombEDPDCH,
	maxNrOfEDCH-HARQ-PO-QUANTSTEPs,
	maxNrOfEDCHHARQProcesses2msEDCH,
	maxNrOfBits-MACe-PDU-non-scheduled,
	maxNrOfEDPCCH-PO-QUANTSTEPs,
	maxNrOfRefETFCI-PO-QUANTSTEPs,
	maxNrOfRefETFCIs,
	maxNrOfMeasNCell,
	maxNrOfMeasNCell-1,
	maxNrOfReceptsPerSyncFrame,
	maxNrOfSF,
	maxTGPS,
	maxNrOfUSCHs,
	maxNrOfULTSs,
	maxNrOfULTSLCRs,
	maxNrOfDPCHs,
	maxNrOfDPCHLCRs,
	maxNrOfDPCHs768,
	maxNrOfCodes,
	maxNrOfDSCHs,
	maxNrOfDLTSs,
	maxNrOfDLTSLCRs,
	maxNrOfDCHs,
	maxNrOfLevels,
	maxNoGPSItems,
	maxNoSat,
	maxNrOfCellPortionsPerCell,
	maxNrOfCellPortionsPerCell-1,
	maxNrOfHSSCCHs,
	maxNrOfHSSCCHCodes,
	maxNrOfMACdFlows,
	maxNrOfMACdFlows-1,
	maxNrOfMACdPDUIndexes,
	maxNrOfMACdPDUIndexes-1,
	maxNrOfMACdPDUSize,
	maxNrOfNIs,
	maxNrOfPriorityQueues,
	maxNrOfPriorityQueues-1,
	maxNrOfHARQProcesses,
	maxNrOfSyncDLCodesLCR,
	maxNrOfSyncFramesLCR,
	maxNrOfContextsOnUeList,
	maxNrOfPriorityClasses,
	maxNrOfSatAlmanac-maxNoSat,
	maxNrOfE-AGCHs,
	maxNrOfEDCHMACdFlows,
	maxNrOfEDCHMACdFlows-1,
	maxNrOfE-RGCHs-E-HICHs,
	maxNrofSigSeqRGHI-1,
	maxNoOfLogicalChannels,
	maxNrOfEAGCHs,
	maxNrOfRefBetas,
	maxNrOfEAGCHCodes,
	maxNrOfHS-DSCH-TBSs,
	maxNrOfHS-DSCH-TBSs-HS-SCCHless,
	maxNrOfEHICHCodes,
	maxNrOfCommonMACFlows,
	maxNrOfCommonMACFlows-1,
	maxNrOfPagingMACFlow,
	maxNrOfPagingMACFlow-1,
	maxNrOfcommonMACQueues,
	maxNrOfpagingMACQueues,
	maxNrOfHS-DSCHTBSsE-PCH,
	maxGANSSSat,
	maxNoGANSS,
	maxSgnType,
	maxHSDPAFrequency,
	maxHSDPAFrequency-1,
	maxGANSSSatAlmanac,
	maxGANSSClockMod,
	maxNrOfEDCHRLs,
	maxCellinNodeB,
	maxERNTItoRelease,
	maxNrOfCommonEDCH,
	maxFrequencyinCell-1,
	maxNrOfCommonMACFlowsLCR,
	maxNrOfCommonMACFlowsLCR-1,
	maxNrOfHSSCCHsLCR,
	maxNrOfEDCHMACdFlowsLCR,
	maxNrOfEDCHMACdFlowsLCR-1,
	maxNrOfEAGCHsLCR,
	maxNrOfEHICHsLCR,
	maxnrofERUCCHsLCR,
	maxNrOfHSPDSCHs,
	maxFrequencyinCell,
	maxNrOfHSDSCH-1,
	maxNrOfHSDSCH,
	maxGANSS-1,
	maxNoOfTBSs-Mapping-HS-DSCH-SPS,
	maxNoOfTBSs-Mapping-HS-DSCH-SPS-1,
	maxNoOfHS-DSCH-TBSsLCR,
	maxNoOfRepetition-Period-LCR,
	maxNoOfRepetitionPeriod-SPS-LCR-1,
	maxNoOf-HS-SICH-SPS,
	maxNoOf-HS-SICH-SPS-1,
	maxNoOfNon-HS-SCCH-Assosiated-HS-SICH, 
	maxNoOfNon-HS-SCCH-Assosiated-HS-SICH-Ext,
	maxMBMSServiceSelect,
	maxNrOfCellPortionsPerCellLCR,
	maxNrOfCellPortionsPerCellLCR-1,
	maxNrOfEDCH-1,
	maxNoOfCommonH-RNTI,
	maxNrOfCommonMACFlowsLCRExt,
	maxofERNTI,
	maxNrOfDCHMeasurementOccasionPatternSequence,
	maxNrOfULCarriersLCR-1,
	maxNrOfCommonHRNTI,
	maxFreqBandsTDD,
	maxSCPICHCell,
	maxnoofPRACHEUL,
	maxIGPInfo,
	maxNrofConcatenatedDCH,

	id-BroadcastCommonTransportBearerIndication,
	id-MessageStructure,
	id-ReportCharacteristicsType-OnModification,
	id-Rx-Timing-Deviation-Value-LCR,
	id-SFNSFNMeasurementValueInformation,
	id-SFNSFNMeasurementThresholdInformation,
	id-TUTRANGPSMeasurementValueInformation,
	id-TUTRANGPSMeasurementThresholdInformation,
	id-TypeOfError,
	id-transportlayeraddress,
	id-bindingID,
	id-Angle-Of-Arrival-Value-LCR,
	id-SyncDLCodeIdThreInfoLCR,
	id-neighbouringTDDCellMeasurementInformationLCR,
	id-HS-SICH-Reception-Quality,
	id-HS-SICH-Reception-Quality-Measurement-Value,
	id-Initial-DL-Power-TimeslotLCR-InformationItem,
	id-Maximum-DL-Power-TimeslotLCR-InformationItem,
	id-Minimum-DL-Power-TimeslotLCR-InformationItem,
	id-Received-total-wide-band-power-For-CellPortion,
	id-Received-total-wide-band-power-For-CellPortion-Value,
	id-Transmitted-Carrier-Power-For-CellPortion,
	id-Transmitted-Carrier-Power-For-CellPortion-Value,
	id-TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmission,
	id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmissionCellPortion,
	id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmissionCellPortionValue,
	id-HS-DSCHRequiredPowerValueInformation,
	id-HS-DSCHProvidedBitRateValueInformation,
	id-HS-DSCHRequiredPowerValue,
	id-HS-DSCHRequiredPowerValue-For-Cell-Portion,
	id-HS-DSCHRequiredPowerValueInformation-For-CellPortion,
	id-HS-DSCHProvidedBitRateValueInformation-For-CellPortion,
	id-HSDSCH-MACdPDUSizeFormat,
	id-HS-PDSCH-Code-Change-Grant,
	id-HS-PDSCH-Code-Change-Indicator,
	id-HS-DSCH-SPS-Operation-Indicator,
	id-Best-Cell-Portions-Value,
	id-Unidirectional-DCH-Indicator,
	id-SAT-Info-Almanac-ExtItem,
	id-TnlQos,
	id-UpPTSInterferenceValue,
	id-HARQ-Preamble-Mode,
	id-HARQ-Preamble-Mode-Activation-Indicator,
	id-DLTransmissionBranchLoadValue,
	id-E-DCHProvidedBitRateValueInformation,
	id-E-DCH-Non-serving-Relative-Grant-Down-CommandsValue,
	id-HSSICH-SIRTarget,
	id-PLCCH-Information-UL-TimeslotLCR-Info,
	id-neighbouringTDDCellMeasurementInformation768,
	id-Rx-Timing-Deviation-Value-768,
	id-hsSCCH-Specific-Information-ResponseTDD768,
	id-Rx-Timing-Deviation-Value-384-ext,
	id-E-DCH-PowerOffset-for-SchedulingInfo,
	id-Extended-Round-Trip-Time-Value,
	id-ExtendedPropagationDelay,
	id-HSSICH-TPC-StepSize,
	id-RTWP-CellPortion-ReportingIndicator,
	id-Received-Scheduled-EDCH-Power-Share-Value,
	id-Received-Scheduled-EDCH-Power-Share-For-CellPortion-Value,
	id-Received-Scheduled-EDCH-Power-Share,
	id-Received-Scheduled-EDCH-Power-Share-For-CellPortion,
	id-ueCapability-Info,
	id-ContinuousPacketConnectivityHS-SCCH-less-Information,
	id-ContinuousPacketConnectivityHS-SCCH-less-Information-Response,
	id-PrecoderWeightSetRestriction,
	id-MIMO-ActivationIndicator,
	id-MIMO-Mode-Indicator,
	id-MIMO-N-M-Ratio,
	id-Additional-failed-HS-SICH,
	id-Additional-missed-HS-SICH,
	id-Additional-total-HS-SICH,
	id-Additional-HS-SICH-Reception-Quality-Measurement-Value,
	id-LCRTDD-uplink-Physical-Channel-Capability,
	id-SixteenQAM-UL-Operation-Indicator,
	id-E-AGCH-Table-Choice,
	id-E-TFCI-Boost-Information,
	id-E-DPDCH-PowerInterpolation,
	id-MaximumMACdPDU-SizeExtended,
	id-GANSS-Common-Data,
	id-GANSS-Information,
	id-GANSS-Generic-Data,
	id-TUTRANGANSSMeasurementThresholdInformation,
	id-TUTRANGANSSMeasurementValueInformation,
	id-Extended-RNC-ID,
	id-HARQ-MemoryPartitioningInfoExtForMIMO,
	id-Ext-Reference-E-TFCI-PO,
	id-Ext-Max-Bits-MACe-PDU-non-scheduled,
	id-TransportBearerNotSetupIndicator,
	id-TransportBearerNotRequestedIndicator,
	id-UARFCNforNt,
	id-number-Of-Supported-Carriers,
	id-multipleFreq-HSPDSCH-InformationList-ResponseTDDLCR,
	id-tSN-Length,
	id-multicarrier-number,
	id-Extended-HS-SICH-ID,
	id-Default-Serving-Grant-in-DTX-Cycle2,
	id-SixtyfourQAM-UsageAllowedIndicator,
	id-SixtyfourQAM-DL-UsageIndicator,
	id-IPMulticastDataBearerIndication,
	id-Extended-E-DCH-LCRTDD-PhysicalLayerCategory,
	id-ContinuousPacketConnectivityHS-SCCH-less-Deactivate-Indicator,
	id-Extended-E-HICH-ID-TDD,
	id-E-DCH-MACdPDUSizeFormat,
	id-MaximumNumber-Of-Retransmission-for-Scheduling-Info-LCRTDD,
	id-E-DCH-RetransmissionTimer-for-SchedulingInfo-LCRTDD,
	id-E-PUCH-PowerControlGAP,
	id-HSDSCH-TBSizeTableIndicator,
	id-E-DCH-DL-Control-Channel-Change-Information,
	id-E-DCH-DL-Control-Channel-Grant-Information,
	id-DGANSS-Corrections-Req,
	id-UE-with-enhanced-HS-SCCH-support-indicator,
	id-TransportBearerRequestIndicator,
	id-EnhancedHSServingCC-Abort,
	id-GANSS-Time-ID,
	id-GANSS-AddIonoModelReq,
	id-GANSS-EarthOrientParaReq,
	id-GANSS-AddNavigationModelsReq,
	id-GANSS-AddUTCModelsReq,
	id-GANSS-AuxInfoReq,
	id-GANSS-SBAS-ID,
	id-GANSS-ID,
	id-GANSS-Additional-Ionospheric-Model,
	id-GANSS-Earth-Orientation-Parameters,
	id-GANSS-Additional-Time-Models,
	id-GANSS-Additional-Navigation-Models,
	id-GANSS-Additional-UTC-Models,
	id-GANSS-Auxiliary-Information,
	id-GANSS-alm-keplerianNAVAlmanac,
	id-GANSS-alm-keplerianReducedAlmanac,
	id-GANSS-alm-keplerianMidiAlmanac,
	id-GANSS-alm-keplerianGLONASS,
	id-GANSS-alm-ecefSBASAlmanac,
	id-GANSS-alm-keplerianBDSAlmanac,
	id-DBDS-CorrectionsReq,
	id-DBDS-Corrections,
	id-BDS-IonosphericGridModelReq,
	id-BDS-Ionospheric-Grid-Model,
	id-EDCH-RACH-Report-Value,
	id-EDCH-RACH-Report-IncrDecrThres,
	id-EDCH-RACH-Report-ThresholdInformation,
	id-MACes-Maximum-Bitrate-LCR,
	id-E-AGCH-UE-Inactivity-Monitor-Threshold,
	id-MultiCarrier-HSDSCH-Physical-Layer-Category,
	id-MIMO-ReferenceSignal-InformationListLCR,
	id-MIMO-SFMode-For-HSPDSCHDualStream,
	id-MIMO-SFMode-Supported-For-HSPDSCHDualStream,
	id-DL-RLC-PDU-Size-Format,
	id-schedulingPriorityIndicator,
	id-UE-SupportIndicatorExtension,
	id-UE-AggregateMaximumBitRate-Enforcement-Indicator,
	id-Single-Stream-MIMO-ActivationIndicator,
	id-Single-Stream-MIMO-Mode-Indicator,
	id-MIMO-withfourtransmitantennas-ActivationIndicator,
	id-MIMO-withfourtransmitantennas-Mode-Indicator,
	id-DualStream-MIMO-withfourtransmitantennas-ActivationIndicator,
	id-DualStream-MIMO-withfourtransmitantennas-Mode-Indicator,
	id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmissionCellPortion,
	id-ULTimeslotISCPValue-For-CellPortion,
	id-UpPTSInterferenceValue-For-CellPortion,
	id-Best-Cell-Portions-ValueLCR,
	id-Transmitted-Carrier-Power-For-CellPortion-ValueLCR,
	id-Received-total-wide-band-power-For-CellPortion-ValueLCR,
	id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmissionCellPortionValue,
	id-UL-TimeslotISCP-For-CellPortion-Value,
	id-HS-DSCHRequiredPowerValueInformation-For-CellPortionLCR,
	id-HS-DSCHProvidedBitRateValueInformation-For-CellPortionLCR,
	id-E-DCHProvidedBitRateValueInformation-For-CellPortion,
	id-UpPTSInterference-For-CellPortion-Value,
	id-HS-DSCH-SPS-Reservation-Indicator,
	id-E-DCH-SPS-Reservation-Indicator,
	id-MultipleFreq-HARQ-MemoryPartitioning-InformationList,
	id-DiversityMode,
	id-TransmitDiversityIndicator,
	id-NonCellSpecificTxDiversity,
	id-RepetitionPeriodIndex,
	id-MidambleShiftLCR,
	id-MaxHSDSCH-HSSCCH-Power-per-CELLPORTION,
	id-Additional-EDCH-Preconfiguration-Information,
	id-EDCH-Indicator,
	id-Ul-common-E-DCH-MACflow-Specific-InfoResponseListLCR-Ext,
	id-E-RNTI-List-Request,
	id-E-RNTI-List,
	id-E-RNTI-Set,
	id-UL-Synchronisation-Parameters-For-FACHLCR,
	id-UE-TS0-CapabilityLCR,
	id-Add-To-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext,
	id-Modify-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext,
	id-DGNSS-ValidityPeriod,
	id-AssociatedPhsicalChannelID,
	id-PhysicalChannelID-for-CommonERNTI-RequestedIndicator,
	id-Initial-DL-Transmission-Power,
	id-Maximum-DL-Power,
	id-Minimum-DL-Power,
	id-Multicell-EDCH-InformationItemIEs,
	id-Multicell-EDCH-RL-Specific-InformationItemIEs,
	id-ContinuousPacketConnectivityDTX-DRX-Information,
	id-Additional-E-DCH-Non-Serving-RL-Preconfiguration-Setup,
	id-Additional-E-DCH-New-non-serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList,
	id-Ul-common-E-DCH-MACflow-Specific-InfoListLCR-Ext,
	id-CommonMACFlow-Specific-InfoList-ResponseLCR-Ext,
	id-Enabling-Delay-Ext-LCR,
	id-OrdinalNumberOfFrequency,
	id-Multicell-EDCH-Restriction,
	id-completeAlmanacProvided,
	id-ganss-Delta-T,
	id-SNPL-Carrier-Group-Indicator,
	id-HS-SCCH-Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext,
	id-Multi-Carrier-E-DCH-LCRTDD-PhysicalLayerCategory,
	id-Common-HSDSCH-RNTI-List,
	id-CommonEDCH-AdditionalTransmissionBackOff,
	id-Puncturing-Handling-in-First-Rate-Matching-Stage,
	id-UE-Status-Update-Confirm-Indicator,
	id-AOA-per-CELL-Portion-LCR,
	id-Multiflow-Information,
	id-Multiflow-Reconfiguration,
	id-Multiflow-OrdinalNumberOfFrequency,
	id-Affected-HSDSCH-Serving-Cell-List,
	id-Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order,
	id-UE-RF-Band-CapabilityLCR,
	id-UE-transmission-power-headroom,
	id-Common-E-DCH-Implicit-Release-Timer,
	id-E-AGCH-PowerOffset,
	id-E-RGCH-PowerOffset,
	id-E-HICH-PowerOffset,
	id-UL-MIMO-Information,
	id-UL-MIMO-Reconfiguration,
	id-UL-MIMO-DL-Control-Channel-Information,
	id-SixtyfourQAM-UL-Operation-Indicator,
	id-Concurrent-Deployment-of-2msand10ms-TTI,
	id-Common-EDH-Preamble-Control-Information-extension-Type1,
	id-Common-EDH-Preamble-Control-Information-extension-Type2,
	id-Common-EDH-Preamble-Control-Information-extension-Type3,
	id-NodeB-Triggered-HSDPCCH-Transmission-Information,
	id-Per-HARQ-Activiation-and-Deactiviation,
	id-Coffset,
	id-Common-E-DCH-MAC-d-flow-info-Concurrent-TTI,
	id-Serving-Grant-Value-for-Concurrent-Deployment-of-2msand10ms-TTI,
	id-Two-ms-Grant-E-DCH-RACH-Resources,
	id-Two-ms-Overridden-E-DCH-RACH-Resources,
	id-Two-ms-Denied-E-DCH-RACH-Resources,
	id-FTPICH-Information,
	id-UL-CLTD-Information,
	id-Assisting-RepetitionFactors,
	id-Gainfactors-10ms-mode,
	id-UPH-Filtering-Measurement-Forwarding-Request,
	id-TTI-Update-Indicator,
	id-CQI-Feedback-Cycle2,
	id-CQI-Cycle-Switch-Timer,
	id-UE-DRX-Cycle2,
	id-Inactivity-Threshold-for-UE-DRX-Cycle2,
	id-DTX-Information2,
	id-ImplicitGrantHandling,
	id-MinimumTEBSthreshold,
	id-Fast-TTI-switching-Mode-synchronized,
	id-Fast-TTI-switching-Mode-unsynchronized,
	id-Fast-TTI-switching-Mode-Supported,
	id-TPC-slot-position,
	id-DL-TBS,
	id-Dual-Band-EDCH-Capability



FROM NBAP-Constants

	Criticality,
	ProcedureID,
	ProtocolIE-ID,
	TransactionID,
	TriggeringMessage
FROM NBAP-CommonDataTypes

	NBAP-PROTOCOL-IES,
	ProtocolExtensionContainer{},
	ProtocolIE-Single-Container{},
	NBAP-PROTOCOL-EXTENSION		
FROM NBAP-Containers;

-- ==========================================
--	A
-- ==========================================

AckNack-RepetitionFactor ::= INTEGER (1..4,...)
-- Step: 1

Ack-Power-Offset ::= INTEGER (0..8,..., 9..10)
-- According to mapping in ref. TS 25.213 [9] subclause 4.2.1

Acknowledged-PRACH-preambles-Value ::= INTEGER(0..240,...)
-- According to mapping in TS 25.133 [22].

ActivationDelay ::= ENUMERATED {v0, v1, v2, v3, v4, v5, ...}

ActivationInformation ::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF ActivationInformationItem

ActivationInformationItem ::= SEQUENCE {
	uU-ActivationState	Uu-ActivationState,
	iE-Extensions									ProtocolExtensionContainer { { ActivationInformationItem-ExtIEs} }				OPTIONAL,
	...
}

ActivationInformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Adaptive-Special-Burst-Power-CapabilityLCR ::= ENUMERATED {
	adaptive-Special-Burst-Power-Capable,
	adaptive-Special-Burst-Power-Not-Capable
}

Additional-EDCH-Setup-Info	::=SEQUENCE{
	multicell-EDCH-Transport-Bearer-Mode									Multicell-EDCH-Transport-Bearer-Mode,
	additional-EDCH-Cell-Information-Setup									Additional-EDCH-Cell-Information-Setup,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-Setup-Info-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-Setup-Info-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Multicell-EDCH-Transport-Bearer-Mode ::= ENUMERATED {
	separate-Iub-Transport-Bearer-Mode,
	uL-Flow-Multiplexing-Mode
}


Additional-EDCH-Cell-Information-Setup	::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-FDD-Setup-Cell-Information

Additional-EDCH-FDD-Setup-Cell-Information	::=SEQUENCE{
	additional-EDCH-UL-DPCH-Information-Setup						Additional-EDCH-UL-DPCH-Information-Setup,
	additional-EDCH-RL-Specific-Information-To-Setup				Additional-EDCH-RL-Specific-Information-To-Setup-List,
	additional-EDCH-FDD-Information									Additional-EDCH-FDD-Information		OPTIONAL,
	additional-EDCH-F-DPCH-Information-Setup						Additional-EDCH-F-DPCH-Information,
	multicell-EDCH-Information										Multicell-EDCH-Information			OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-FDD-Setup-Cell-Information-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-FDD-Setup-Cell-Information-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Additional-EDCH-UL-DPCH-Information-Setup	::=SEQUENCE{
	ul-ScramblingCode						UL-ScramblingCode,
	ul-SIR-Target							UL-SIR,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-UL-DPCH-Information-Setup-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-UL-DPCH-Information-Setup-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Additional-EDCH-F-DPCH-Information	::=SEQUENCE{
	fdd-TPC-DownlinkStepSize			FDD-TPC-DownlinkStepSize,
	limitedPowerIncrease				LimitedPowerIncrease,
	innerLoopDLPCStatus					InnerLoopDLPCStatus,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-F-DPCH-Information-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-F-DPCH-Information-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Additional-EDCH-RL-Specific-Information-To-Setup-List	::= SEQUENCE (SIZE (1..maxNrOfEDCHRLs)) OF Additional-EDCH-RL-Specific-Information-To-Setup-ItemIEs


Additional-EDCH-RL-Specific-Information-To-Setup-ItemIEs	::=SEQUENCE{
	eDCH-Additional-RL-ID				RL-ID,
	c-ID								C-ID										OPTIONAL,
	firstRLS-indicator					FirstRLS-Indicator,
	propagationDelay					PropagationDelay							OPTIONAL,
	dl-CodeInformation					FDD-DL-CodeInformation,
	initialDL-transmissionPower			DL-Power,
	maximumDL-power						DL-Power,
	minimumDL-power						DL-Power,
	f-DPCH-SlotFormat					F-DPCH-SlotFormat 							OPTIONAL,
	e-RNTI								E-RNTI 										OPTIONAL,
	multicell-EDCH-RL-Specific-Information	Multicell-EDCH-RL-Specific-Information	OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { Additional-EDCH-RL-Specific-Information-To-Setup-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-RL-Specific-Information-To-Setup-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TPC-slot-position		CRITICALITY ignore	EXTENSION TPC-slot-position			PRESENCE optional},
	...
}

Additional-EDCH-Cell-Information-To-Add-List	::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-Cell-Information-To-Add-ItemIEs

Additional-EDCH-Cell-Information-To-Add-ItemIEs	::=SEQUENCE{
	additional-EDCH-RL-Specific-Information-To-Add-ItemIEs	Additional-EDCH-RL-Specific-Information-To-Add-ItemIEs,
	additional-EDCH-FDD-Information							Additional-EDCH-FDD-Information			OPTIONAL,
	multicell-EDCH-Information								Multicell-EDCH-Information				OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-To-Add-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-Cell-Information-To-Add-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Additional-EDCH-RL-Specific-Information-To-Add-ItemIEs	::= SEQUENCE (SIZE (1.. maxNrOfEDCHRLs)) OF EDCH-Additional-RL-Specific-Information-To-Add-List

EDCH-Additional-RL-Specific-Information-To-Add-List	::=SEQUENCE{
	eDCH-Additional-RL-ID				RL-ID,
	c-ID								C-ID,
	dl-CodeInformation					FDD-DL-CodeInformation,
	initialDL-transmissionPower			DL-Power				OPTIONAL,
	maximumDL-power						DL-Power				OPTIONAL,
	minimumDL-power						DL-Power				OPTIONAL,
	f-DPCH-SlotFormat					F-DPCH-SlotFormat 		OPTIONAL,
	multicell-EDCH-RL-Specific-Information	Multicell-EDCH-RL-Specific-Information 		OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { EDCH-Additional-RL-Specific-Information-To-Add-List-ExtIEs} } OPTIONAL,
	...
}

EDCH-Additional-RL-Specific-Information-To-Add-List-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TPC-slot-position		CRITICALITY ignore	EXTENSION TPC-slot-position		PRESENCE optional},
	...
}

Additional-EDCH-RL-Specific-Information-To-Modify-List	::= SEQUENCE (SIZE (1..maxNrOfEDCHRLs)) OF Additional-EDCH-RL-Specific-Information-To-Modify-ItemIEs

Additional-EDCH-RL-Specific-Information-To-Modify-ItemIEs	::=SEQUENCE{
	eDCH-Additional-RL-ID				RL-ID,
	dl-CodeInformation					FDD-DL-CodeInformation 	OPTIONAL,
	maximumDL-power						DL-Power				OPTIONAL,
	minimumDL-power						DL-Power				OPTIONAL,
	f-DPCH-SlotFormat					F-DPCH-SlotFormat 		OPTIONAL,
 
	multicell-EDCH-RL-Specific-Information		Multicell-EDCH-RL-Specific-Information 	OPTIONAL,	iE-Extensions						ProtocolExtensionContainer { { Additional-EDCH-RL-Specific-Information-To-Modify-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-RL-Specific-Information-To-Modify-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TPC-slot-position		CRITICALITY ignore	EXTENSION TPC-slot-position		PRESENCE optional},
	...
}

Additional-EDCH-FDD-Information	::=SEQUENCE{
	additional-EDCH-MAC-d-Flows-Specific-Information	Additional-EDCH-MAC-d-Flows-Specific-Info-List	OPTIONAL,
	hARQ-Process-Allocation-Scheduled-2ms-EDCH		HARQ-Process-Allocation-2ms-EDCH				OPTIONAL,
	e-DCH-Maximum-Bitrate							E-DCH-Maximum-Bitrate							OPTIONAL,
	e-DCH-Processing-Overload-Level					E-DCH-Processing-Overload-Level					OPTIONAL,
	e-DCH-Min-Set-E-TFCI							E-TFCI																	OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { Additional-EDCH-FDD-Information-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-FDD-Information-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-DTX-Information2		CRITICALITY ignore	EXTENSION DTX-Information2			PRESENCE optional}|
	{ ID id-ImplicitGrantHandling	CRITICALITY ignore	EXTENSION Implicit-Grant-Handling	PRESENCE optional}|
	{ ID id-MinimumTEBSthreshold	CRITICALITY ignore	EXTENSION Minimum-TEBS-threshold	PRESENCE optional},
	...
}

DTX-Information2 ::= SEQUENCE {
	uE-DTX-Cycle1							UE-DTX-Cycle1-2ms,
	uE-DTX-Cycle2							UE-DTX-Cycle2-ext-2ms,
	inactivity-Threshold-for-UE-DTX-Cycle2	Inactivity-Threshold-for-UE-DTX-Cycle2,
	iE-Extensions							ProtocolExtensionContainer { {DTX-Information2-ExtIEs} } OPTIONAL,
	...
}

DTX-Information2-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Implicit-Grant-Handling ::= ENUMERATED {
	true
}

Minimum-TEBS-threshold ::= ENUMERATED {v2, v4, v8, v16, v32, v64, v128, v256, v512, v1024, v2048, v4096, v8192, v16384, v32768, v65536, v131072, v262144, v524288, v1048576,...}

Additional-EDCH-MAC-d-Flows-Specific-Info-List ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF Additional-EDCH-MAC-d-Flows-Specific-Info

Additional-EDCH-MAC-d-Flows-Specific-Info ::= SEQUENCE {
	e-DCH-MACdFlow-ID								E-DCH-MACdFlow-ID,
	bindingID										BindingID																	OPTIONAL,
	transportLayerAddress							TransportLayerAddress														OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { Additional-EDCH-MAC-d-Flows-Specific-Info-ExtIEs} }				OPTIONAL,
	...
}

Additional-EDCH-MAC-d-Flows-Specific-Info-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Additional-EDCH-Cell-Information-Response-List	::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-FDD-Information-Response-ItemIEs

Additional-EDCH-FDD-Information-Response-ItemIEs	::=SEQUENCE{
	eDCH-Additional-RL-Specific-Information-Response						EDCH-Additional-RL-Specific-Information-Response-List	OPTIONAL,
	additional-EDCH-MAC-d-Flow-Specific-Information-Response				Additional-EDCH-MAC-d-Flow-Specific-Information-Response-List		OPTIONAL,
	hARQ-Process-Allocation-Scheduled-2ms-EDCH								HARQ-Process-Allocation-2ms-EDCH					OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-FDD-Information-Response-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-FDD-Information-Response-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

EDCH-Additional-RL-Specific-Information-Response-List	::= SEQUENCE (SIZE (1..maxNrOfEDCHRLs)) OF EDCH-Additional-RL-Specific-Information-Response-ItemIEs

EDCH-Additional-RL-Specific-Information-Response-ItemIEs	::=SEQUENCE{
	eDCH-Additional-RL-ID							RL-ID,
	received-total-wide-band-power					Received-total-wide-band-power-Value,
	dL-PowerBalancing-ActivationIndicator			DL-PowerBalancing-ActivationIndicator	OPTIONAL,
	rL-Set-ID										RL-Set-ID, 
	e-DCH-RL-Set-ID									RL-Set-ID,
	e-DCH-FDD-DL-Control-Channel-Information		E-DCH-FDD-DL-Control-Channel-Information,
	iE-Extensions					ProtocolExtensionContainer { { EDCH-Additional-RL-Specific-Information-Response-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

EDCH-Additional-RL-Specific-Information-Response-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Additional-EDCH-Cell-Information-Response-RLReconf-List::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-FDD-Information-Response-RLReconf-Items

Additional-EDCH-FDD-Information-Response-RLReconf-Items::=SEQUENCE{
	additional-EDCH-FDD-Information-Response-ItemIEs				Additional-EDCH-FDD-Information-Response-ItemIEs					OPTIONAL,
	additional-Modififed-EDCH-FDD-Information-Response-ItemIEs		Additional-Modififed-EDCH-FDD-Information-Response-ItemIEs		OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-FDD-Information-Response-RLReconf-Items-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-FDD-Information-Response-RLReconf-Items-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Additional-Modififed-EDCH-FDD-Information-Response-ItemIEs	::=SEQUENCE{
	eDCH-Additional-Modified-RL-Specific-Information-Response		EDCH-Additional-Modified-RL-Specific-Information-Response-List		OPTIONAL,
	additional-EDCH-MAC-d-Flow-Specific-Information-Response		Additional-EDCH-MAC-d-Flow-Specific-Information-Response-List		OPTIONAL,
	hARQ-Process-Allocation-Scheduled-2ms-EDCH						HARQ-Process-Allocation-2ms-EDCH							OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { Additional-Modififed-EDCH-FDD-Information-Response-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-Modififed-EDCH-FDD-Information-Response-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

EDCH-Additional-Modified-RL-Specific-Information-Response-List	::= SEQUENCE (SIZE (1.. maxNrOfEDCHRLs)) OF EDCH-Additional-Modified-RL-Specific-Information-Response-List-Items

EDCH-Additional-Modified-RL-Specific-Information-Response-List-Items	::=SEQUENCE{
	eDCH-Additional-RL-ID							RL-ID,
	dL-PowerBalancing-UpdatedIndicator				DL-PowerBalancing-UpdatedIndicator			OPTIONAL,
	e-DCH-FDD-DL-Control-Channel-Information		E-DCH-FDD-DL-Control-Channel-Information	OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { EDCH-Additional-Modified-RL-Specific-Information-Response-List-Items-ExtIEs} } OPTIONAL,
	...
}

EDCH-Additional-Modified-RL-Specific-Information-Response-List-Items-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Additional-EDCH-MAC-d-Flow-Specific-Information-Response-List::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF Additional-EDCH-MAC-d-Flows-Specific-Info-Response

Additional-EDCH-MAC-d-Flows-Specific-Info-Response ::= SEQUENCE {
	e-DCH-MACdFlow-ID								E-DCH-MACdFlow-ID,
	bindingID										BindingID																	OPTIONAL,
	transportLayerAddress							TransportLayerAddress														OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { Additional-EDCH-MAC-d-Flows-Specific-Info-Response-ExtIEs} }				OPTIONAL,
	...
}

Additional-EDCH-MAC-d-Flows-Specific-Info-Response-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Additional-EDCH-Cell-Information-Response-RL-Add-List	::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-Cell-Information-Response-RL-Add-ItemIEs

Additional-EDCH-Cell-Information-Response-RL-Add-ItemIEs	::=SEQUENCE{
	additional-EDCH-FDD-Information-Response					Additional-EDCH-FDD-Information-Response-ItemIEs 	OPTIONAL,
	additional-EDCH-Serving-Cell-Change-Information-Response	E-DCH-Serving-Cell-Change-Info-Response 				OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-Response-RL-Add-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-Cell-Information-Response-RL-Add-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Additional-EDCH-Cell-Information-ConfigurationChange-List	::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-ConfigurationChange-Info-ItemIEs

Additional-EDCH-ConfigurationChange-Info-ItemIEs	::=SEQUENCE{
	additional-EDCH-UL-DPCH-Information-Modify							Additional-EDCH-UL-DPCH-Information-Modify		OPTIONAL,
	additional-EDCH-RL-Specific-Information-To-Add						Additional-EDCH-RL-Specific-Information-To-Add-ItemIEs 	OPTIONAL,
	additional-EDCH-RL-Specific-Information-To-Modify					Additional-EDCH-RL-Specific-Information-To-Modify-List 	OPTIONAL,
	additional-EDCH-FDD-Information-To-Modify							Additional-EDCH-FDD-Information		OPTIONAL,
	additional-EDCH-F-DPCH-Information-Modify							Additional-EDCH-F-DPCH-Information		OPTIONAL,
	multicell-EDCH-Information											Multicell-EDCH-Information		OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-ConfigurationChange-Info-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-ConfigurationChange-Info-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Additional-EDCH-UL-DPCH-Information-Modify		::=SEQUENCE{
	ul-ScramblingCode						UL-ScramblingCode 	OPTIONAL,
	ul-SIR-Target							UL-SIR 				OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { Additional-EDCH-UL-DPCH-Information-Modify-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-UL-DPCH-Information-Modify-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Additional-EDCH-Cell-Information-Removal-List	::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-Cell-Information-Removal-Info-ItemIEs

Additional-EDCH-Cell-Information-Removal-Info-ItemIEs	::=SEQUENCE{
	rL-on-Secondary-UL-Frequency							RL-on-Secondary-UL-Frequency,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-Removal-Info-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-Cell-Information-Removal-Info-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RL-on-Secondary-UL-Frequency ::= ENUMERATED {
	remove,
	...
}

Additional-EDCH-FDD-Update-Information	::=SEQUENCE{
	hARQ-Process-Allocation-Scheduled-2ms-EDCH						HARQ-Process-Allocation-2ms-EDCH								OPTIONAL,
	additional-EDCH-DL-Control-Channel-Change-Information			Additional-EDCH-DL-Control-Channel-Change-Information-List					OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-FDD-Update-Information-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-FDD-Update-Information-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}


Additional-EDCH-DL-Control-Channel-Change-Information-List	::= SEQUENCE (SIZE (1..maxNrOfEDCHRLs)) OF Additional-EDCH-DL-Control-Channel-Change-Info-ItemIEs

Additional-EDCH-DL-Control-Channel-Change-Info-ItemIEs	::=SEQUENCE{
	eDCH-Additional-RL-ID				RL-ID,
	iE-Extensions						ProtocolExtensionContainer { { Additional-EDCH-DL-Control-Channel-Change-Info-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-DL-Control-Channel-Change-Info-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

AdditionalMeasurementValueList::= SEQUENCE (SIZE (1..maxFrequencyinCell-1)) OF AdditionalMeasurementValue

AdditionalMeasurementValue ::= SEQUENCE {
	uARFCN									UARFCN, 
	timeSlotMeasurementValueListLCR			TimeSlotMeasurementValueListLCR,
	iE-Extensions							ProtocolExtensionContainer { {AdditionalMeasurementValueList-ExtIEs} } OPTIONAL,
	...
}

AdditionalMeasurementValueList-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

AdditionalTimeSlotListLCR::= SEQUENCE (SIZE (0..maxFrequencyinCell-1)) OF AdditionalTimeSlotLCR

AdditionalTimeSlotLCR ::= SEQUENCE {
	uARFCN								UARFCN,
	timeslot-InitiatedListLCR					TimeSlot-InitiatedListLCR	 OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { {AdditionalTimeSlotLCR-ExtIEs} } OPTIONAL,
	...
}

AdditionalTimeSlotLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

AddorDeleteIndicator ::= ENUMERATED {
	add,
	delete
}

Active-Pattern-Sequence-Information ::= SEQUENCE {
	cMConfigurationChangeCFN								CFN,
	transmission-Gap-Pattern-Sequence-Status	Transmission-Gap-Pattern-Sequence-Status-List	OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { {Active-Pattern-Sequence-Information-ExtIEs} } OPTIONAL,
	...
}

Active-Pattern-Sequence-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Transmission-Gap-Pattern-Sequence-Status-List ::= SEQUENCE (SIZE (0..maxTGPS)) OF
	SEQUENCE {
		tGPSID			TGPSID,
		tGPRC			TGPRC,
		tGCFN			CFN,
		iE-Extensions		ProtocolExtensionContainer { { Transmission-Gap-Pattern-Sequence-Status-List-ExtIEs } } OPTIONAL,
		...
}

Transmission-Gap-Pattern-Sequence-Status-List-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
{ID id-Affected-HSDSCH-Serving-Cell-List	CRITICALITY reject EXTENSION Affected-HSDSCH-Serving-Cell-List	PRESENCE optional},
	...
}

Affected-HSDSCH-Serving-Cell-List ::= SEQUENCE (SIZE (0.. maxNrOfHSDSCH)) OF C-ID

AICH-Power ::= INTEGER (-22..5)
-- Offset in dB.

AICH-TransmissionTiming ::= ENUMERATED {
	v0,
	v1
}

AllocationRetentionPriority ::= SEQUENCE {
	priorityLevel				PriorityLevel,
	pre-emptionCapability		Pre-emptionCapability,
	pre-emptionVulnerability	Pre-emptionVulnerability,
	iE-Extensions				ProtocolExtensionContainer { {AllocationRetentionPriority-ExtIEs} } OPTIONAL,
	...
}

AllocationRetentionPriority-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

AlternativeFormatReportingIndicator ::= ENUMERATED {
alternativeFormatAllowed,...
}

Angle-Of-Arrival-Value-LCR ::= SEQUENCE {
	aOA-LCR						AOA-LCR,
	aOA-LCR-Accuracy-Class		AOA-LCR-Accuracy-Class,
	iE-Extensions				ProtocolExtensionContainer { {Angle-Of-Arrival-Value-LCR-ExtIEs} } OPTIONAL,
...
}

Angle-Of-Arrival-Value-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

AOA-LCR ::= INTEGER (0..719)
-- Angle Of Arrival for 1.28Mcps TDD

AOA-LCR-Accuracy-Class	::= ENUMERATED {a,b,c,d,e,f,g,h,...}

AOA-per-CELL-Portion-LCR ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCellLCR)) OF AOA-per-CELL-Portion-LCR-Item

AOA-per-CELL-Portion-LCR-Item ::= SEQUENCE{
	cellPortionLCRID			CellPortionLCRID,
	aOA-LCR						AOA-LCR,
	aOA-LCR-Accuracy-Class		AOA-LCR-Accuracy-Class,
	iE-Extensions				ProtocolExtensionContainer { { AOA-per-CELL-Portion-LCR-Item-ExtIEs} }	OPTIONAL,
	...
}

AOA-per-CELL-Portion-LCR-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

AvailabilityStatus ::= ENUMERATED {
	empty,
	in-test,
	failed,
	power-off,
	off-line,
	off-duty,
	dependency,
	degraded,
	not-installed,
	log-full,
	...
}

-- ==========================================
--	B
-- ==========================================

BCCH-Specific-HSDSCH-RNTI-Information::= SEQUENCE {
	bCCH-Specific-HSDSCH-RNTI						HSDSCH-RNTI,
	hSSCCH-Power									DL-Power,
	hSPDSCH-Power									DL-Power,
	iE-Extensions									ProtocolExtensionContainer { { BCCH-Specific-HSDSCH-RNTI-Information-ExtIEs } }		OPTIONAL,
	...
}

BCCH-Specific-HSDSCH-RNTI-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


BCCH-Specific-HSDSCH-RNTI-InformationLCR::= SEQUENCE {
	bCCH-Specific-HSDSCH-RNTI						HSDSCH-RNTI,
	hSSCCH-Power									DL-Power,
	hSPDSCH-Power									DL-Power,
	iE-Extensions									ProtocolExtensionContainer { { BCCH-Specific-HSDSCH-RNTI-InformationLCR-ExtIEs } }		OPTIONAL,
	...
}

BCCH-Specific-HSDSCH-RNTI-InformationLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


BCCH-ModificationTime ::= INTEGER  (0..511)
-- Time = BCCH-ModificationTime * 8
-- Range 0 to 4088, step 8
-- All SFN values in which MIB may be mapped are allowed

BDS-IGPInfoList ::= SEQUENCE (SIZE (1..maxIGPInfo)) OF BDS-IGPInfo

BDS-IGPInfo ::= SEQUENCE {
	bds-IGPNumber			INTEGER (1..320),
	bds-VerticalDelay		BIT STRING (SIZE (9)),
	bds-GIVEI				BIT STRING (SIZE (4)),
	ie-Extensions			ProtocolExtensionContainer { { BDS-IGPInfo-ExtIEs } }	OPTIONAL,
	...
}

BDS-IGPInfo-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

BDS-IonosphericGridModelReq ::= ENUMERATED {
	requested,
	...
}

BDS-Ionospheric-Grid-Model ::= SEQUENCE {
	bDS-RefTime				INTEGER (0..119),
-- Time = bDS-RefTime *30
-- Range 0 to 3570, step 30
	bds-IGPInfoList			BDS-IGPInfoList,
	ie-Extensions			ProtocolExtensionContainer { { BDS-Ionospheric-Grid-Model-ExtIEs } }	OPTIONAL,
	...
}

BDS-Ionospheric-Grid-Model-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Best-Cell-Portions-Value::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCell)) OF Best-Cell-Portions-Item

Best-Cell-Portions-Item ::= SEQUENCE {
	cellPortionID				CellPortionID,
	sIRValue					SIR-Value,
	iE-Extensions				ProtocolExtensionContainer { { Best-Cell-Portions-Item-ExtIEs} }	OPTIONAL,
	...
}

Best-Cell-Portions-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Best-Cell-Portions-ValueLCR::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCellLCR)) OF Best-Cell-Portions-ItemLCR

Best-Cell-Portions-ItemLCR ::= SEQUENCE {
	cellPortionLCRID				CellPortionLCRID,
	rSCPValue						RSCP-Value,
	iE-Extensions				ProtocolExtensionContainer { { Best-Cell-Portions-ItemLCR-ExtIEs} }	OPTIONAL,
	...
}

Best-Cell-Portions-ItemLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

BindingID ::= OCTET STRING (SIZE (1..4, ...))
-- If the Binding ID includes a UDP port, the UDP port is included in octet 1 and 2.The first octet of
-- the UDP port field is included in the first octet of the Binding ID.

BetaCD ::= INTEGER (0..15)

BlockingPriorityIndicator ::= ENUMERATED {
	high,
	normal,
	low,
	...
}
-- High priority: Block resource immediately.
-- Normal priority: Block resource when idle or upon timer expiry.
-- Low priority: Block resource when idle.

SCTD-Indicator ::= ENUMERATED {
	active,
	inactive
}

BundlingModeIndicator ::= ENUMERATED {
	bundling,
	no-bundling
}

BroadcastCommonTransportBearerIndication ::= SEQUENCE {
	commonTransportChannelID			CommonTransportChannelID,
	cid									C-ID,
	iE-Extensions						ProtocolExtensionContainer  { { BroadcastCommonTransportBearerIndication-ExtIEs} }		OPTIONAL,
	...
}

BroadcastCommonTransportBearerIndication-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

BroadcastReference ::= BIT STRING (SIZE (24))

-- ==========================================
--	C
-- ==========================================

Cause ::= CHOICE {
	radioNetwork			CauseRadioNetwork,
	transport			CauseTransport,
	protocol				CauseProtocol,
	misc					CauseMisc,
	...
}

CauseMisc ::= ENUMERATED {
	control-processing-overload,
	hardware-failure,
	oam-intervention,
	not-enough-user-plane-processing-resources,
	unspecified,
	...
}

CauseProtocol ::= ENUMERATED {
	transfer-syntax-error,
	abstract-syntax-error-reject,
	abstract-syntax-error-ignore-and-notify,
	message-not-compatible-with-receiver-state,
	semantic-error,
	unspecified,
	abstract-syntax-error-falsely-constructed-message,
	...
}

CauseRadioNetwork ::= ENUMERATED {
	unknown-C-ID,
	cell-not-available,
	power-level-not-supported, 
	dl-radio-resources-not-available,
	ul-radio-resources-not-available,
	rl-already-ActivatedOrAllocated,
	nodeB-Resources-unavailable,
	measurement-not-supported-for-the-object,
	combining-resources-not-available,
	requested-configuration-not-supported,
	synchronisation-failure,
	priority-transport-channel-established,
	sIB-Origination-in-Node-B-not-Supported,
	requested-tx-diversity-mode-not-supported,
	unspecified,
	bCCH-scheduling-error,
	measurement-temporarily-not-available,
	invalid-CM-settings,
	reconfiguration-CFN-not-elapsed,
	number-of-DL-codes-not-supported,
	s-cpich-not-supported,
	combining-not-supported,
	ul-sf-not-supported,
	dl-SF-not-supported, 
	common-transport-channel-type-not-supported,
	dedicated-transport-channel-type-not-supported,
	downlink-shared-channel-type-not-supported,
	uplink-shared-channel-type-not-supported,
	cm-not-supported,
	tx-diversity-no-longer-supported,
	unknown-Local-Cell-ID,
	...,
	number-of-UL-codes-not-supported,
	information-temporarily-not-available,
	information-provision-not-supported-for-the-object,
	cell-synchronisation-not-supported,
	cell-synchronisation-adjustment-not-supported,
	dpc-mode-change-not-supported,
	iPDL-already-activated,
	iPDL-not-supported,
	iPDL-parameters-not-available,
	frequency-acquisition-not-supported,
	power-balancing-status-not-compatible,
	requested-typeofbearer-re-arrangement-not-supported,
	signalling-Bearer-Re-arrangement-not-supported,
	bearer-Re-arrangement-needed,
	delayed-activation-not-supported,
	rl-timing-adjustment-not-supported,
	mich-not-supported,
	f-DPCH-not-supported,
	modification-period-not-available,
	pLCCH-not-supported,
	continuous-packet-connectivity-DTX-DRX-operation-not-available,
	continuous-packet-connectivity-UE-DTX-Cycle-not-available,
	mIMO-not-available,
	e-DCH-MACdPDU-SizeFormat-not-available,
	multi-Cell-operation-not-available,
	semi-Persistent-scheduling-not-supported,
	continuous-Packet-Connectivity-DRX-not-supported,
	continuous-Packet-Connectivity-DRX-not-available,
	sixtyfourQAM-DL-and-MIMO-Combined-not-available,
	s-cpich-power-offset-not-available,
	tx-diversity-for-mimo-on-DL-control-channels-not-available,
	single-Stream-MIMO-not-available,
	multi-Cell-operation-with-MIMO-not-available,
	multi-Cell-operation-with-Single-Stream-MIMO-not-available,
	cellSpecificTxDiversityHandlingForMultiCellOperationNotAvailable,
	multi-Cell-EDCH-operation-not-available,
	frequency-Specific-Compressed-Mode-operation-not-available,
	uL-CLTD-Operation-not-available,
	mimo-withfourtransmitantennas-not-available,
	dualstream-mimo-withfourtransmitantennas-not-available,
	multiflow-operation-not-available,
	ul-SixtyfourQAM-Operation-not-available,
	ul-MIMO-Operation-not-available,
	ul-MIMO-SixteenQAM-Operation-not-available,
	ul-MIMO-SixtyfourQAM-Operation-not-available,
	nodeB-Triggered-HS-DPCCH-Transmission-operation-not-available,
	two-msand10ms-TTI-Concurrent-Deployment-operation-not-available,
	further-Enhanced-UE-DRX-operation-not-available,
	per-HARQ-Activation-and-Deactivation-operation-not-available,
	tTI-alignment-operation-not-available,
	common-E-RGCH-operation-not-available,
	e-DCH-decoupling-operation-not-available,
	basic-dch-enh-not-available,
	full-dch-enh-not-available,
	bCH-mappedOnSCCPCH-scheduling-error,
	radio-Links-without-DPCH-FDPCH-Indication-operation-not-available,
	uL-DPCCH2-operation-not-available,
	downlink-TPC-enhancements-operation-not-available


}

CauseTransport ::= ENUMERATED {
	transport-resource-unavailable,
	unspecified,
	...
}


CCTrCH-ID ::= INTEGER (0..15)

Cell-Capability-Container ::= BIT STRING (SIZE (128))
-- First bit: Cell Specific Tx Diversity Handling For Multi Cell Operation Capability
-- Second bit: Multi Cell and MIMO Capability
-- Third bit: Multi Cell and Single Stream MIMO Capability
-- Fourth bit: Multi Cell E-DCH Capability
-- Fifth bit: Separate Iub Transport Bearer Capability
-- Sixth bit: E-DCH UL Flow Multiplexing Capability
-- Seventh to eleventh bit: Maximum No of HSDPA Frequencies capability
-- Twelfth bit: Dual Band and MIMO Capability
-- Thirteenth bit: 3 or more carrier HSDPA and MIMO Single Band Capability
-- Fourteenth bit: 3 or more carrier HSDPA and MIMO Dual Band Capability
-- Fifteenth bit : Dual Band and Single Stream MIMO Capability
-- Sixteenth bit : 3 or more carrier HSDPA and Single Stream MIMO Single Band Capability
-- Seventeenth bit : 3 or more carrier HSDPA and Single Stream MIMO Dual Band Capability
-- Eighteenth bit: Frequency Specific Compressed Mode Capability
-- Nineteenth bit: UL CLTD Capability
-- Twentieth bit: Non-contiguous HSDPA operation Capability
-- Twenty-first to twentythird bit: Supported MIMO transmit antennas (N).
-- Twenty-fourth bit: MIMO with N transmit antennas Capability Adjacent-carrier.
-- Twenty-fifth bit: MIMO with N transmit antennas Capability Dual Band/Dual Band.
-- Twenty-sixth bit: Multi Cell and MIMO with N transmit antennas Capability Adjacent-carrier.
-- Twenty-seventh bit: Multi Cell and MIMO with N transmit antennas Capability Dual Band/Dual Band.
-- Twenty-eighth bit: HSPA 3 or more Carrier and MIMO with N transmit antennas Capability Adjacent-carrier.
-- Twenty-ninth bit: HSPA 3 or more Carrier and MIMO with N transmit antennas Capability Dual Band/Dual Band.
-- Thirtieth bit: Intra-Node B Multiflow.
-- Thirty-first bit: Inter-Node B Multiflow.
-- Thirty-second to thirty-fourth bits: Supported Multiflow configuration, where:
--   value 0 indicates support for one frequency two cells.
--   value 1 indicates support for two frequencies three cells.
--   value 2 indicates support for two frequencies four cells.
--   value 3 indicates support for three frequencies four cells.
--   values 4-7 are reserved for future use.
-- Thirty-fifth bit: Multiflow and MIMO.
-- Thirty-sixth bit: Cell Specific Tx Diversity Handling For Multiflow Cell Operation.
-- Thirty-seventh bit: Multiflow and single stream MIMO.
-- Thirty-eighth bit: UL 64QAM Capability.
-- Thirty-ninth bit: UL MIMO Capability.
-- Fortieth bit: UL MIMO and UL 16QAM Capability.
-- Forty-first bit: UL MIMO and UL 64QAM Capability.
-- Forty-second bit: NodeB Triggered HS-DPCCH Transmission Capability
-- Forty-third bit: 2ms and 10ms TTI Concurrent Deployment Capability
-- Forty-fourth bit: Further Enhanced UE DRX Capability
-- Forty-fifth bit: Per HARQ Activation and Deactivation Capability
-- Forty-sixth bit: TTI alignment Capability
-- Forty-seventh bit: Common E-RGCH Capability
-- Forty-eighth bit: Fallback to R99 PRACH Capability
-- Forty-ninth bit: E-DCH decoupling operation Capability
-- Fiftieth bit: Basic DCH Enhancements Capability
-- Fifty-first bit: Full DCH Enhancements Capability
-- Fifty-second bit: BCH mapped on SCCPCH Capability
-- Fifty-third bit: Radio Links without DPCH/F-DPCH operation Capability
-- Fifty-fourth bit: UL DPCCH2 operation Capability
-- Fifty-fifth bit: feEUL TTI switching Node B Autonomous Capability.
-- Fifty-sixth bit: feEUL TTI switching RNC notify Capability.
-- Fifty-seventh bit: downlink TPC enhancements Capability.
-- Fifty-eighth bit: NAICS offloading Capability.
-- Fifty-ninth bit: Multi Cell E-DCH with DPDCH Capability.



-- Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver.

Cell-ERNTI-Status-Information		::= SEQUENCE (SIZE (1..maxCellinNodeB)) OF Cell-ERNTI-Status-Information-Item

Cell-ERNTI-Status-Information-Item  ::= SEQUENCE {
	c-ID											C-ID,
	vacant-ERNTI									Vacant-ERNTI,
	...
}

Vacant-ERNTI 		::= SEQUENCE (SIZE (1..maxERNTItoRelease)) OF E-RNTI


CellParameterID ::= INTEGER (0..127,...)

CellPortionID	::= INTEGER (0..maxNrOfCellPortionsPerCell-1,...)

CellPortionLCRID	::= INTEGER (0..maxNrOfCellPortionsPerCellLCR-1,...)

CellPortion-CapabilityLCR ::= ENUMERATED {
	cell-portion-capable,
	cell-portion-non-capable
}

CellSyncBurstCode ::= INTEGER(0..7, ...)

CellSyncBurstCodeShift ::= INTEGER(0..7)

CellSyncBurstRepetitionPeriod ::= INTEGER (0..4095)

CellSyncBurstSIR ::= INTEGER (0..31)

CellSyncBurstTiming ::= CHOICE {
	initialPhase			INTEGER (0..1048575,...),
	steadyStatePhase		INTEGER (0..255,...)
}

CellSyncBurstTimingLCR ::= CHOICE {
	initialPhase			INTEGER (0..524287,...),
	steadyStatePhase		INTEGER (0..127,...)
}

CellSyncBurstTimingThreshold ::= INTEGER(0..254)

CFN ::= INTEGER (0..255)

ChipOffset ::= INTEGER (0..38399)
-- Unit Chip

C-ID ::= INTEGER (0..65535)

Closedlooptimingadjustmentmode	::= ENUMERATED {
	adj-1-slot,
	adj-2-slot,
	...
}

CodeRate ::= INTEGER (0..63)

CodeRate-short ::= INTEGER (0..10)


CommonChannelsCapacityConsumptionLaw ::= SEQUENCE (SIZE(1..maxNrOfSF)) OF
	SEQUENCE {
		dl-Cost		INTEGER (0..65535),
		ul-Cost		INTEGER (0..65535),
		iE-Extensions		ProtocolExtensionContainer { { CommonChannelsCapacityConsumptionLaw-ExtIEs } }		OPTIONAL,
		...
}

CommonChannelsCapacityConsumptionLaw-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


Common-EDCH-Capability ::= ENUMERATED {
	common-EDCH-capable,
	common-EDCH-non-capable
}

Common-E-DCH-HSDPCCH-Capability ::= ENUMERATED {
	hSDPCCH-non-capable,
	aCK-NACK-capable,
	aCK-NACK-CQI-capable
}

Common-EDCH-System-InformationFDD ::= SEQUENCE {
	common-E-DCH-UL-DPCH-Information				Common-E-DCH-UL-DPCH-InfoItem								OPTIONAL,
	common-E-DCH-EDPCH-Information					Common-E-DCH-EDPCH-InfoItem									OPTIONAL,
	common-E-DCH-Information						Common-E-DCH-InfoItem										OPTIONAL,
	common-E-DCH-HSDPCCH-Information				Common-E-DCH-HSDPCCH-InfoItem							OPTIONAL,
	common-E-DCH-Preamble-Control-Information		Common-E-DCH-Preamble-Control-InfoItem						OPTIONAL,
	common-E-DCH-FDPCH-Information					Common-E-DCH-FDPCH-InfoItem									OPTIONAL,
	common-E-DCH-E-AGCH-ChannelisationCodeNumber	FDD-DL-ChannelisationCodeNumber								OPTIONAL,
	common-E-DCH-Resource-Combination-Information	Common-E-DCH-Resource-Combination-InfoList					OPTIONAL,
	ul-common-E-DCH-MACflow-Specific-Information	Ul-common-E-DCH-MACflow-Specific-InfoList					OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { Common-EDCH-System-InformationFDD-ExtIEs } }		OPTIONAL,
	...
}

Common-EDCH-System-InformationFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-E-RNTI-List-Request						CRITICALITY ignore	EXTENSION NULL													PRESENCE optional}|
	{ID id-E-AGCH-PowerOffset						CRITICALITY ignore	EXTENSION E-AGCH-PowerOffset									PRESENCE optional}|
	{ID id-E-RGCH-PowerOffset						CRITICALITY ignore	EXTENSION E-RGCH-PowerOffset									PRESENCE optional}|
	{ID id-E-HICH-PowerOffset						CRITICALITY ignore	EXTENSION E-HICH-PowerOffset									PRESENCE optional}|
	{ID id-Concurrent-Deployment-of-2msand10ms-TTI	CRITICALITY ignore	EXTENSION Concurrent-Deployment-of-2msand10ms-TTI		PRESENCE optional}|
	{ID id-Common-EDH-Preamble-Control-Information-extension-Type1	CRITICALITY ignore	EXTENSION Common-E-DCH-Preamble-Control-Information-extensionList	PRESENCE optional}|
	{ID id-Common-EDH-Preamble-Control-Information-extension-Type2	CRITICALITY ignore	EXTENSION Common-E-DCH-Preamble-Control-Information-extensionList	PRESENCE optional}|
	{ID id-Common-EDH-Preamble-Control-Information-extension-Type3	CRITICALITY ignore	EXTENSION Common-E-DCH-Preamble-Control-Information-extensionList	PRESENCE optional}|
	{ID id-NodeB-Triggered-HSDPCCH-Transmission-Information	CRITICALITY ignore	EXTENSION NodeB-Triggered-HSDPCCH-Transmission-Information	PRESENCE optional}|
	{ID id-Per-HARQ-Activiation-and-Deactiviation	CRITICALITY ignore	EXTENSION Per-HARQ-Activiation-and-Deactiviation		PRESENCE optional}|
	{ID id-Coffset									CRITICALITY ignore	EXTENSION Coffset												PRESENCE optional}|
	{ID id-E-RNTI-Set								CRITICALITY ignore	EXTENSION E-RNTI-Set											PRESENCE optional},
	...
}

E-RNTI-Set ::= SEQUENCE {
	starting-e-rnti			E-RNTI,
	ending-e-rnti			E-RNTI,
	iE-Extensions			ProtocolExtensionContainer { { E-RNTI-Set-ExtIEs } } OPTIONAL,
	...
}

E-RNTI-Set-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-E-DCH-UL-DPCH-InfoItem ::= SEQUENCE {

	uL-SIR-Target						UL-SIR,
	dPC-Mode							DPC-Mode					OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { Common-E-DCH-UL-DPCH-InfoItem-ExtIEs} }					OPTIONAL,
	...
}

Common-E-DCH-UL-DPCH-InfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-E-DCH-EDPCH-InfoItem	 ::= SEQUENCE {
	maxSet-E-DPDCHs								Max-Set-E-DPDCHs,
	ul-PunctureLimit							PunctureLimit,
	e-TFCS-Information							E-TFCS-Information,
	e-TTI										E-TTI,
	e-DPCCH-PO									E-DPCCH-PO,
	e-RGCH-2-IndexStepThreshold					E-RGCH-2-IndexStepThreshold						OPTIONAL,
	e-RGCH-3-IndexStepThreshold					E-RGCH-3-IndexStepThreshold						OPTIONAL,
	hARQ-Info-for-E-DCH							HARQ-Info-for-E-DCH,
	iE-Extensions								ProtocolExtensionContainer { { Common-E-DCH-EDPCH-InfoItem-ExtIEs} }					OPTIONAL,
	...
}

Common-E-DCH-EDPCH-InfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-E-DCH-InfoItem	 ::= SEQUENCE {
	e-DCH-Reference-Power-Offset				E-DCH-Reference-Power-Offset					OPTIONAL,
	e-DCH-PowerOffset-for-SchedulingInfo		E-DCH-PowerOffset-for-SchedulingInfo			OPTIONAL,
	max-EDCH-Resource-Allocation-for-CCCH		Max-EDCH-Resource-Allocation-for-CCCH,
	max-Period-for-Collision-Resolution		Max-Period-for-Collision-Resolution, 
	max-TB-Sizes									Max-TB-Sizes										OPTIONAL,
	common-E-DCH-ImplicitRelease-Indicator		BOOLEAN,
	iE-Extensions								ProtocolExtensionContainer { { Common-E-DCH-InfoItem-ExtIEs} }					OPTIONAL,
	...
}

Common-E-DCH-InfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-CommonEDCH-AdditionalTransmissionBackOff	CRITICALITY ignore	EXTENSION CommonEDCH-AdditionalTransmissionBackOff	PRESENCE optional }|
	{ ID id-Common-E-DCH-Implicit-Release-Timer			CRITICALITY ignore	EXTENSION Common-E-DCH-Implicit-Release-Timer			PRESENCE optional },
	...
}

CommonEDCH-AdditionalTransmissionBackOff::= INTEGER (0..15,...)

Common-E-DCH-HSDPCCH-InfoItem	 ::= SEQUENCE {
	ackNackRepetitionFactor						AckNack-RepetitionFactor,

	ackPowerOffset								Ack-Power-Offset,
	nackPowerOffset								Nack-Power-Offset,
 
	common-E-DCH-CQI-Info						Common-E-DCH-CQI-Info						OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { Common-E-DCH-HSDPCCH-InfoItem-ExtIEs} }					OPTIONAL,
	...
}

Common-E-DCH-HSDPCCH-InfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


Common-E-DCH-CQI-Info	 ::= SEQUENCE {
	cqiFeedback-CycleK							CQI-Feedback-Cycle,
	cqiRepetitionFactor							CQI-RepetitionFactor						OPTIONAL,
	-- This IE shall be present if the CQI Feedback Cycle k is greater than 0
	cqiPowerOffset								CQI-Power-Offset,
	measurement-Power-Offset					Measurement-Power-Offset,
	iE-Extensions								ProtocolExtensionContainer { { Common-E-DCH-CQI-Info-ExtIEs} }					OPTIONAL,
	...
}

Common-E-DCH-CQI-Info-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-E-DCH-Preamble-Control-InfoItem	 ::= SEQUENCE {
	commonPhysicalChannelID						CommonPhysicalChannelID,
	common-E-DCH-PreambleSignatures				PreambleSignatures,
	scramblingCodeNumber						ScramblingCodeNumber, 
	preambleThreshold							PreambleThreshold,
	e-AI-Indicator								E-AI-Indicator						OPTIONAL,
	common-E-DCH-AICH-Information				Common-E-DCH-AICH-Information						OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { Common-E-DCH-Preamble-Control-InfoItem-ExtIEs} }					OPTIONAL,
	...
}

Common-E-DCH-Preamble-Control-InfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-E-DCH-AICH-Information	 ::= SEQUENCE {
	commonPhysicalChannelID						CommonPhysicalChannelID,
	aICH-TransmissionTiming						AICH-TransmissionTiming,
	fdd-dl-ChannelisationCodeNumber				FDD-DL-ChannelisationCodeNumber,
	aICH-Power									AICH-Power,
	sTTD-Indicator								STTD-Indicator,
	iE-Extensions								ProtocolExtensionContainer  { { Common-E-DCH-AICH-Information-ExtIEs} }		OPTIONAL,
	...
}

Common-E-DCH-AICH-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}




Common-E-DCH-FDPCH-InfoItem		 ::= SEQUENCE {
	f-DPCH-SlotFormat							F-DPCH-SlotFormat,
	fdd-TPC-DownlinkStepSize					FDD-TPC-DownlinkStepSize,
	iE-Extensions								ProtocolExtensionContainer { { Common-E-DCH-FDPCH-InfoItem-ExtIEs} }					OPTIONAL,
	...
}

Common-E-DCH-FDPCH-InfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Initial-DL-Transmission-Power	CRITICALITY ignore		EXTENSION DL-Power		PRESENCE optional }|
	{ ID id-Maximum-DL-Power				CRITICALITY ignore		EXTENSION DL-Power		PRESENCE optional }|
	{ ID id-Minimum-DL-Power				CRITICALITY ignore		EXTENSION DL-Power		PRESENCE optional },
	...
}

Common-E-DCH-Resource-Combination-InfoList::= SEQUENCE (SIZE (1.. maxNrOfCommonEDCH)) OF Common-E-DCH-Resource-Combination-InfoList-Item

Common-E-DCH-Resource-Combination-InfoList-Item		 ::= SEQUENCE {
	soffset										Soffset,
	f-DPCH-DL-Code-Number						FDD-DL-ChannelisationCodeNumber,
	ul-DPCH-ScramblingCode						UL-ScramblingCode,
	e-RGCH-E-HICH-Channelisation-Code			FDD-DL-ChannelisationCodeNumber,
	e-RGCH-Signature-Sequence					E-RGCH-Signature-Sequence													OPTIONAL,
	e-HICH-Signature-Sequence					E-HICH-Signature-Sequence,
	iE-Extensions								ProtocolExtensionContainer { { Common-E-DCH-Resource-Combination-InfoList-Item-ExtIEs} }					OPTIONAL,
	...
}

Common-E-DCH-Resource-Combination-InfoList-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-E-DCH-MAC-d-flow-info-Concurrent-TTI		 ::= SEQUENCE {
	maximum-Number-of-Retransmissions-For-E-DCH		Maximum-Number-of-Retransmissions-For-E-DCH			OPTIONAL,
	eDCH-HARQ-PO-FDD								E-DCH-HARQ-PO-FDD									OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer {{Common-E-DCH-MAC-d-flow-info-Concurrent-TTI-ExtIEs} } OPTIONAL,
	...
}

Common-E-DCH-MAC-d-flow-info-Concurrent-TTI-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Ul-common-E-DCH-MACflow-Specific-InfoList		::= SEQUENCE (SIZE (1..maxNrOfCommonMACFlows)) OF Ul-common-E-DCH-MACflow-Specific-InfoList-Item

Ul-common-E-DCH-MACflow-Specific-InfoList-Item		 ::= SEQUENCE {
	ul-Common-MACFlowID									Common-MACFlow-ID,
	transportBearerRequestIndicator						TransportBearerRequestIndicator,
	bindingID											BindingID										OPTIONAL,
	transportLayerAddress								TransportLayerAddress							OPTIONAL,
	tnlQos												TnlQos											OPTIONAL,
	payloadCRC-PresenceIndicator						PayloadCRC-PresenceIndicator,
	bundlingModeIndicator								BundlingModeIndicator							OPTIONAL,
	common-E-DCH-MACdFlow-Specific-Information			Common-E-DCH-MACdFlow-Specific-InfoList,
	iE-Extensions										ProtocolExtensionContainer { { Ul-common-E-DCH-MACflow-Specific-InfoList-Item-ExtIEs} }					OPTIONAL,
	...
}

Ul-common-E-DCH-MACflow-Specific-InfoList-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-E-DCH-MACdFlow-Specific-InfoList::= SEQUENCE (SIZE (1.. maxNrOfEDCHMACdFlows)) OF Common-E-DCH-MACdFlow-Specific-InfoList-Item

Common-E-DCH-MACdFlow-Specific-InfoList-Item		 ::= SEQUENCE {
	common-e-DCH-MACdFlow-ID						E-DCH-MACdFlow-ID,
	maximum-Number-of-Retransmissions-For-E-DCH		Maximum-Number-of-Retransmissions-For-E-DCH,
	eDCH-HARQ-PO-FDD								E-DCH-HARQ-PO-FDD,
	eDCH-MACdFlow-Multiplexing-List					E-DCH-MACdFlow-Multiplexing-List																	OPTIONAL,
	common-E-DCHLogicalChannelInformation			Common-E-DCH-LogicalChannel-InfoList,
	iE-Extensions									ProtocolExtensionContainer { { Common-E-DCH-MACdFlow-Specific-InfoList-Item-ExtIEs} }				OPTIONAL,
	...
}

Common-E-DCH-MACdFlow-Specific-InfoList-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Common-E-DCH-MAC-d-flow-info-Concurrent-TTI	CRITICALITY ignore	EXTENSION Common-E-DCH-MAC-d-flow-info-Concurrent-TTI	PRESENCE optional},
	...
}

Common-E-DCH-LogicalChannel-InfoList::= SEQUENCE (SIZE (1.. maxNoOfLogicalChannels)) OF Common-E-DCH-LogicalChannel-InfoList-Item

Common-E-DCH-LogicalChannel-InfoList-Item	::= SEQUENCE {
	logicalChannelId				LogicalChannelID,
	maximumMACcPDU-SizeExtended		MAC-PDU-SizeExtended,
	iE-Extensions									ProtocolExtensionContainer { { Common-E-DCH-LogicalChannel-InfoList-Item-ExtIEs} }				OPTIONAL,
	...
}

Common-E-DCH-LogicalChannel-InfoList-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
{ ID id-schedulingPriorityIndicator	CRITICALITY ignore		EXTENSION	SchedulingPriorityIndicator	PRESENCE optional},
	...
}


Common-EDCH-System-Information-ResponseFDD		 ::= SEQUENCE {
	ul-common-E-DCH-MACflow-Specific-InfoResponse			Ul-common-E-DCH-MACflow-Specific-InfoResponseList,
	serving-Grant-Value										E-Serving-Grant-Value,
	iE-Extensions											ProtocolExtensionContainer { { Common-EDCH-System-Information-ResponseFDD-ExtIEs} }					OPTIONAL,
	...
}

Common-EDCH-System-Information-ResponseFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
{ ID id-E-RNTI-List								CRITICALITY ignore	EXTENSION E-RNTI-List		PRESENCE optional}|
{ ID id-UE-Status-Update-Confirm-Indicator		CRITICALITY ignore	EXTENSION BOOLEAN			PRESENCE optional}|
{ ID id-Serving-Grant-Value-for-Concurrent-Deployment-of-2msand10ms-TTI		CRITICALITY ignore	EXTENSION E-Serving-Grant-Value		PRESENCE optional},
	...
}

E-RNTI-List 		::= SEQUENCE (SIZE (1..maxofERNTI)) OF E-RNTI

Ul-common-E-DCH-MACflow-Specific-InfoResponseList		::= SEQUENCE (SIZE (1..maxNrOfCommonMACFlows)) OF Ul-common-E-DCH-MACflow-Specific-InfoResponseList-Item

Ul-common-E-DCH-MACflow-Specific-InfoResponseList-Item		 ::= SEQUENCE {
	ul-Common-MACFlowID									Common-MACFlow-ID,
	bindingID											BindingID										OPTIONAL,
	transportLayerAddress								TransportLayerAddress							OPTIONAL, 
	iE-Extensions										ProtocolExtensionContainer { { Ul-common-E-DCH-MACflow-Specific-InfoResponseList-Item-ExtIEs} }					OPTIONAL,
	...
}

Ul-common-E-DCH-MACflow-Specific-InfoResponseList-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-HSDSCH-RNTI-List ::= SEQUENCE (SIZE (1.. maxNrOfCommonHRNTI)) OF HSDSCH-RNTI

Common-MACFlows-to-DeleteFDD ::= SEQUENCE (SIZE (1.. maxNrOfCommonMACFlows)) OF Common-MACFlows-to-DeleteFDD-Item

Common-MACFlows-to-DeleteFDD-Item ::= SEQUENCE {
	common-MACFlow-ID								Common-MACFlow-ID,
	iE-Extensions									ProtocolExtensionContainer { { Common-MACFlows-to-DeleteFDD-Item-ExtIEs} }					OPTIONAL,
	...
}

Common-MACFlows-to-DeleteFDD-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-MACFlow-ID ::= INTEGER (0..maxNrOfCommonMACFlows-1)

CommonMACFlow-Specific-InfoList ::= SEQUENCE (SIZE (1.. maxNrOfCommonMACFlows)) OF CommonMACFlow-Specific-InfoItem

CommonMACFlow-Specific-InfoItem ::= SEQUENCE {
	common-MACFlow-Id								Common-MACFlow-ID, 
	bindingID										BindingID									OPTIONAL,
	transportLayerAddress							TransportLayerAddress						OPTIONAL,
	tnl-qos											TnlQos										OPTIONAL,
	common-MACFlow-PriorityQueue-Information		Common-MACFlow-PriorityQueue-Information	OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { CommonMACFlow-Specific-InfoItem-ExtIEs } }		OPTIONAL,
	...
}

CommonMACFlow-Specific-InfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TransportBearerRequestIndicator 	CRITICALITY ignore	 EXTENSION TransportBearerRequestIndicator 	PRESENCE optional},
	-- This IE should not be contained if the MAC flow is setup in procedure, and it should be contained if the MAC flow is modified in procedure.
	...
}


CommonMACFlow-Specific-InfoList-Response ::= SEQUENCE (SIZE (1..maxNrOfCommonMACFlows)) OF CommonMACFlow-Specific-InfoItem-Response

CommonMACFlow-Specific-InfoItem-Response ::= SEQUENCE {
	commonMACFlow-ID								Common-MACFlow-ID, 
	bindingID										BindingID									OPTIONAL,
	transportLayerAddress							TransportLayerAddress						OPTIONAL,
	hSDSCH-Initial-Capacity-Allocation				HSDSCH-Initial-Capacity-Allocation			OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { CommonMACFlow-Specific-InfoItem-Response-ExtIEs} }			OPTIONAL,
	...
}

CommonMACFlow-Specific-InfoItem-Response-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-MACFlow-PriorityQueue-Information  ::= SEQUENCE (SIZE (1..maxNrOfcommonMACQueues)) OF Common-MACFlow-PriorityQueue-Item  

Common-MACFlow-PriorityQueue-Item  ::= SEQUENCE {
	priority-Queue-Information-for-Enhanced-FACH		Priority-Queue-Information-for-Enhanced-FACH-PCH,
		iE-Extensions									ProtocolExtensionContainer { { Common-MACFlow-PriorityQueue-Item-ExtIEs } }		OPTIONAL,
	...
}

Common-MACFlow-PriorityQueue-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}




CommonMeasurementAccuracy ::= CHOICE {
	tUTRANGPSMeasurementAccuracyClass		TUTRANGPSAccuracyClass,
	...,
	tUTRANGANSSMeasurementAccuracyClass		TUTRANGANSSAccuracyClass
}

CommonMeasurementType ::= ENUMERATED  {
	received-total-wide-band-power,
	transmitted-carrier-power,
	acknowledged-prach-preambles,
	ul-timeslot-iscp,
	notUsed-1-acknowledged-PCPCH-access-preambles,
	notUsed-2-detected-PCPCH-access-preambles,
	...,
	uTRAN-GPS-Timing-of-Cell-Frames-for-UE-Positioning, 
	sFN-SFN-Observed-Time-Difference,
	transmittedCarrierPowerOfAllCodesNotUsedForHSTransmission,
	hS-DSCH-Required-Power,
	hS-DSCH-Provided-Bit-Rate,
	received-total-wide-band-power-for-cellPortion,
	transmitted-carrier-power-for-cellPortion,
	transmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmission-for-cellPortion,
	upPTS-Interference,
	dLTransmissionBranchLoad,
	hS-DSCH-Required-Power-for-cell-portion,
	hS-DSCH-Provided-Bit-Rate-for-cell-portion,
	e-DCH-Provided-Bit-Rate,
	e-DCH-Non-serving-Relative-Grant-Down-Commands,
	received-Scheduled-EDCH-Power-Share,
	received-Scheduled-EDCH-Power-Share-for-cellPortion,
	uTRAN-GANSS-timing-of-cell-frames-for-UE-Positioning,
	eDCH-RACH-report,
	transmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmission-for-cellPortion,
	ul-timeslot-iscp-for-cellPortion,
	upPTS-Interference-for-cellPortion,
	e-DCH-Provided-Bit-Rate-for-cellPortion

}

CommonMeasurementValue ::= CHOICE {
	transmitted-carrier-power							Transmitted-Carrier-Power-Value,
	received-total-wide-band-power						Received-total-wide-band-power-Value,
	acknowledged-prach-preambles						Acknowledged-PRACH-preambles-Value,
	uL-TimeslotISCP										UL-TimeslotISCP-Value,
	notUsed-1-acknowledged-PCPCH-access-preambles		NULL,
	notUsed-2-detected-PCPCH-access-preambles			NULL,
	...,
	extension-CommonMeasurementValue		Extension-CommonMeasurementValue
}

Extension-CommonMeasurementValue	::= ProtocolIE-Single-Container {{ Extension-CommonMeasurementValueIE }}

Extension-CommonMeasurementValueIE NBAP-PROTOCOL-IES ::= {
	{ ID id-TUTRANGPSMeasurementValueInformation			CRITICALITY ignore	TYPE TUTRANGPSMeasurementValueInformation		PRESENCE mandatory }|
	{ ID id-SFNSFNMeasurementValueInformation				CRITICALITY ignore	TYPE SFNSFNMeasurementValueInformation			PRESENCE mandatory }|
	{ ID id-TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmission	CRITICALITY ignore	TYPE TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmissionValue		PRESENCE mandatory }|
	{ ID id-HS-DSCHRequiredPowerValueInformation			CRITICALITY ignore	TYPE HS-DSCHRequiredPower							PRESENCE mandatory }|
	{ ID id-HS-DSCHProvidedBitRateValueInformation			CRITICALITY ignore	TYPE HS-DSCHProvidedBitRate						PRESENCE mandatory }|
	{ ID id-Transmitted-Carrier-Power-For-CellPortion-Value	CRITICALITY ignore	TYPE Transmitted-Carrier-Power-For-CellPortion-Value	PRESENCE mandatory }|
	{ ID id-Received-total-wide-band-power-For-CellPortion-Value	CRITICALITY ignore	TYPE Received-total-wide-band-power-For-CellPortion-Value	PRESENCE mandatory }|
	{ ID id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmissionCellPortionValue	CRITICALITY ignore	TYPE TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmissionCellPortionValue		PRESENCE mandatory }|
	{ ID id-UpPTSInterferenceValue									CRITICALITY ignore	TYPE UpPTSInterferenceValue									PRESENCE mandatory }|
	{ ID id-DLTransmissionBranchLoadValue							CRITICALITY ignore	TYPE DLTransmissionBranchLoadValue							PRESENCE mandatory }|
	{ ID id-HS-DSCHRequiredPowerValueInformation-For-CellPortion	CRITICALITY ignore	TYPE HS-DSCHRequiredPowerValueInformation-For-CellPortion	PRESENCE mandatory }|
	{ ID id-HS-DSCHProvidedBitRateValueInformation-For-CellPortion	CRITICALITY ignore	TYPE HS-DSCHProvidedBitRateValueInformation-For-CellPortion	PRESENCE mandatory }|
	{ ID id-E-DCHProvidedBitRateValueInformation					CRITICALITY ignore	TYPE E-DCHProvidedBitRate										PRESENCE mandatory }|
	{ ID id-E-DCH-Non-serving-Relative-Grant-Down-CommandsValue		CRITICALITY ignore	TYPE E-DCH-Non-serving-Relative-Grant-Down-Commands			PRESENCE mandatory }|
	{ ID id-Received-Scheduled-EDCH-Power-Share-Value	CRITICALITY ignore	TYPE Received-Scheduled-EDCH-Power-Share-Value	PRESENCE mandatory }|
	{ ID id-Received-Scheduled-EDCH-Power-Share-For-CellPortion-Value 	CRITICALITY ignore	TYPE Received-Scheduled-EDCH-Power-Share-For-CellPortion-Value	PRESENCE mandatory }|
	{ ID id-TUTRANGANSSMeasurementValueInformation 		CRITICALITY ignore	TYPE TUTRANGANSSMeasurementValueInformation	PRESENCE mandatory }|
	{ ID id-EDCH-RACH-Report-Value						CRITICALITY ignore	TYPE EDCH-RACH-Report-Value			PRESENCE mandatory }|
		-- FDD only
	{ ID id-Transmitted-Carrier-Power-For-CellPortion-ValueLCR	CRITICALITY ignore	TYPE Transmitted-Carrier-Power-For-CellPortion-ValueLCR	PRESENCE mandatory }|
	{ ID id-Received-total-wide-band-power-For-CellPortion-ValueLCR	CRITICALITY ignore	TYPE Received-total-wide-band-power-For-CellPortion-ValueLCR	PRESENCE mandatory }|
	{ ID id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmissionCellPortionValue	CRITICALITY ignore	TYPE TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmissionCellPortionValue		PRESENCE mandatory }|
	{ ID id-UL-TimeslotISCP-For-CellPortion-Value									CRITICALITY ignore	TYPE UL-TimeslotISCP-For-CellPortion-Value									PRESENCE mandatory }|
	{ ID id-HS-DSCHRequiredPowerValueInformation-For-CellPortionLCR	CRITICALITY ignore	TYPE HS-DSCHRequiredPowerValueInformation-For-CellPortionLCR	PRESENCE mandatory }|
	{ ID id-HS-DSCHProvidedBitRateValueInformation-For-CellPortionLCR	CRITICALITY ignore	TYPE HS-DSCHProvidedBitRateValueInformation-For-CellPortionLCR	PRESENCE mandatory }|
	{ ID id-E-DCHProvidedBitRateValueInformation-For-CellPortion					CRITICALITY ignore	TYPE E-DCHProvidedBitRateValueInformation-For-CellPortion										PRESENCE mandatory }|
	{ ID id-UpPTSInterference-For-CellPortion-Value									CRITICALITY ignore	TYPE UpPTSInterference-For-CellPortion-Value									PRESENCE mandatory }
}

CommonMeasurementValueInformation ::= CHOICE {
	measurementAvailable		CommonMeasurementAvailable,
	measurementnotAvailable		CommonMeasurementnotAvailable
}

CommonMeasurementAvailable::= SEQUENCE {
	commonmeasurementValue		CommonMeasurementValue,
	ie-Extensions					ProtocolExtensionContainer { { CommonMeasurementAvailableItem-ExtIEs} }		OPTIONAL,
	...
}

CommonMeasurementAvailableItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}
CommonMeasurementnotAvailable ::= NULL

CommonPhysicalChannelID ::= INTEGER (0..255)

CommonPhysicalChannelID768 ::= INTEGER (0..511)

Common-PhysicalChannel-Status-Information ::= SEQUENCE {
	commonPhysicalChannelID				CommonPhysicalChannelID,
	resourceOperationalState			ResourceOperationalState,
	availabilityStatus					AvailabilityStatus,
	iE-Extensions						ProtocolExtensionContainer  { { Common-PhysicalChannel-Status-Information-ExtIEs} }		OPTIONAL,
	...
}

Common-PhysicalChannel-Status-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-PhysicalChannel-Status-Information768 ::= SEQUENCE {
	commonPhysicalChannelID768			CommonPhysicalChannelID768,
	resourceOperationalState			ResourceOperationalState,
	availabilityStatus					AvailabilityStatus,
	iE-Extensions						ProtocolExtensionContainer  { { Common-PhysicalChannel-Status-Information768-ExtIEs} }		OPTIONAL,
	...
}

Common-PhysicalChannel-Status-Information768-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


CommonTransportChannelID ::= INTEGER (0..255)

CommonTransportChannel-InformationResponse ::= SEQUENCE {
	commonTransportChannelID			CommonTransportChannelID,
	bindingID							BindingID				OPTIONAL,
	transportLayerAddress				TransportLayerAddress	OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer  { { CommonTransportChannel-InformationResponse-ExtIEs} }		OPTIONAL,
	...
}

CommonTransportChannel-InformationResponse-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID	id-BroadcastCommonTransportBearerIndication	CRITICALITY ignore EXTENSION BroadcastCommonTransportBearerIndication	 PRESENCE optional }|
	{ ID	id-IPMulticastDataBearerIndication			CRITICALITY ignore EXTENSION IPMulticastDataBearerIndication				 PRESENCE optional },
	...
}

Common-TransportChannel-Status-Information ::= SEQUENCE {
	commonTransportChannelID			CommonTransportChannelID,
	resourceOperationalState			ResourceOperationalState,
	availabilityStatus					AvailabilityStatus,
	iE-Extensions						ProtocolExtensionContainer  { { Common-TransportChannel-Status-Information-ExtIEs} }		OPTIONAL,
	...
}

Common-TransportChannel-Status-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CommunicationControlPortID ::= INTEGER (0..65535)

CompleteAlmanacProvided ::= BOOLEAN

Compressed-Mode-Deactivation-Flag ::= ENUMERATED {
	deactivate,
	maintain-Active
}

ConfigurationGenerationID ::= INTEGER (0..255)
-- Value '0' means "No configuration" 

ConstantValue ::= INTEGER (-10..10,...)
-- -10 dB - +10 dB
-- unit dB
-- step 1 dB

ContinuousPacketConnectivityDTX-DRX-Capability ::= ENUMERATED {
	continuous-Packet-Connectivity-DTX-DRX-capable,
	continuous-Packet-Connectivity-DTX-DRX-non-capable
}

ContinuousPacketConnectivityDTX-DRX-Information ::= SEQUENCE {
	uE-DTX-DRX-Offset							UE-DTX-DRX-Offset,
	enabling-Delay								Enabling-Delay,
	dTX-Information								DTX-Information	,
	dRX-Information								DRX-Information							OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { ContinuousPacketConnectivityDTX-DRX-Information-ExtIEs } }			OPTIONAL,
	...
}

ContinuousPacketConnectivityDTX-DRX-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ContinuousPacketConnectivityDTX-DRX-Information-to-Modify ::= SEQUENCE {
	uE-DTX-DRX-Offset							UE-DTX-DRX-Offset						OPTIONAL,
	enabling-Delay								Enabling-Delay							OPTIONAL,
	dTX-Information-to-Modify					DTX-Information-to-Modify				OPTIONAL,
	dRX-Information-to-Modify					DRX-Information-to-Modify				OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { ContinuousPacketConnectivityDTX-DRX-Information-to-Modify-ExtIEs } }			OPTIONAL,
	...
}

ContinuousPacketConnectivityDTX-DRX-Information-to-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


ContinuousPacketConnectivityHS-SCCH-less-Capability ::= ENUMERATED {
	continuous-Packet-Connectivity-HS-SCCH-less-capable,
	continuous-Packet-Connectivity-HS-SCCH-less-capable-non-capable
}


ContinuousPacketConnectivityHS-SCCH-less-Information ::= SEQUENCE (SIZE (1..maxNrOfHS-DSCH-TBSs-HS-SCCHless)) OF ContinuousPacketConnectivityHS-SCCH-less-InformationItem

ContinuousPacketConnectivityHS-SCCH-less-InformationItem ::= SEQUENCE {
	transport-Block-Size-Index				Transport-Block-Size-Index,
	hSPDSCH-Second-Code-Support				HSPDSCH-Second-Code-Support, 
	iE-Extensions							ProtocolExtensionContainer { { ContinuousPacketConnectivityHS-SCCH-less-Information-ExtIEs } }			OPTIONAL,
	...
}

ContinuousPacketConnectivityHS-SCCH-less-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


ContinuousPacketConnectivityHS-SCCH-less-Information-Response ::= SEQUENCE {
	hSPDSCH-First-Code-Index				HSPDSCH-First-Code-Index,
	hSPDSCH-Second-Code-Index				HSPDSCH-Second-Code-Index				OPTIONAL, 
	iE-Extensions							ProtocolExtensionContainer { { ContinuousPacketConnectivityHS-SCCH-less-Information-Response-ExtIEs } }			OPTIONAL,
	...
}

ContinuousPacketConnectivityHS-SCCH-less-Information-Response-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ControlGAP ::= INTEGER (1..255)

CPC-Information ::= SEQUENCE {
	continuousPacketConnectivityDTX-DRX-Information					ContinuousPacketConnectivityDTX-DRX-Information						OPTIONAL,
	continuousPacketConnectivityDTX-DRX-Information-to-Modify		ContinuousPacketConnectivityDTX-DRX-Information-to-Modify		OPTIONAL,
	continuousPacketConnectivityHS-SCCH-less-Information			ContinuousPacketConnectivityHS-SCCH-less-Information				OPTIONAL,
	iE-Extensions				ProtocolExtensionContainer { { CPC-Information-ExtIEs} }														OPTIONAL,
	...
}

CPC-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-ContinuousPacketConnectivityHS-SCCH-less-Deactivate-Indicator 	CRITICALITY reject	 EXTENSION ContinuousPacketConnectivityHS-SCCH-less-Deactivate-Indicator 	PRESENCE optional},
	...
}

CPC-RecoveryReport ::= ENUMERATED {
	initiated,
	...
}

ContinuousPacketConnectivityHS-SCCH-less-Deactivate-Indicator ::= NULL

CQI-DTX-Timer ::= ENUMERATED {v0, v1, v2, v4, v8, v16, v32, v64, v128, v256, v512, infinity}
	-- Unit subframe

CQI-Cycle-Switch-Timer ::= ENUMERATED {v4, v8, v16, v32, v64, v128, v256, v512, infinity}
	-- Unit subframe

CQI-Feedback-Cycle ::= ENUMERATED {v0, v2, v4, v8, v10, v20, v40, v80, v160,..., v16, v32, v64}

CQI-Feedback-Cycle2 ::= ENUMERATED {v0, v8, v10, v16, v20, v32, v40, v64, v80, v160,...}

CQI-Power-Offset ::= INTEGER (0..8,..., 9..10)
-- According to mapping in ref. TS 25.213 [9] subclause 4.2.1

CQI-RepetitionFactor ::= INTEGER (1..4,...)
-- Step: 1

CriticalityDiagnostics ::= SEQUENCE {
	procedureID					ProcedureID				OPTIONAL,
	triggeringMessage			TriggeringMessage			OPTIONAL,
	procedureCriticality		Criticality				OPTIONAL,
	transactionID				TransactionID				OPTIONAL,
	iEsCriticalityDiagnostics	CriticalityDiagnostics-IE-List	OPTIONAL,
	iE-Extensions				ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} }		OPTIONAL,
	...
}

CriticalityDiagnostics-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF
	SEQUENCE {
		iECriticality		Criticality,
		iE-ID				ProtocolIE-ID,
		repetitionNumber	RepetitionNumber0		OPTIONAL,
		iE-Extensions		ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} }		OPTIONAL,
		...
	}

CriticalityDiagnostics-IE-List-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{	ID id-MessageStructure		CRITICALITY ignore		EXTENSION MessageStructure		PRESENCE optional	}|
	{	ID id-TypeOfError			CRITICALITY ignore		EXTENSION TypeOfError			PRESENCE mandatory	},
	...
}

CRNC-CommunicationContextID ::= INTEGER (0..1048575)

CSBMeasurementID ::= INTEGER (0..65535)

CSBTransmissionID ::= INTEGER (0..65535)


Common-EDCH-System-InformationLCR ::= SEQUENCE {
	ul-common-E-DCH-MACflow-Specific-InformationLCR			Ul-common-E-DCH-MACflow-Specific-InfoListLCR					OPTIONAL,
	common-E-PUCH-InformationLCR							Common-E-PUCH-InformationLCR							OPTIONAL,
	e-TFCS-Information-TDD									E-TFCS-Information-TDD									OPTIONAL,
	maximum-Number-of-Retransmissions-For-SchedulingInfo		Maximum-Number-of-Retransmissions-For-E-DCH					OPTIONAL,
	eDCH-Retransmission-Timer-SchedulingInfo				E-DCH-MACdFlow-Retransmission-Timer						OPTIONAL,
	iE-Extensions											ProtocolExtensionContainer { { Common-EDCH-System-InformationLCR-ExtIEs } }		OPTIONAL,
	...
}

Common-EDCH-System-InformationLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
{ ID id-UL-Synchronisation-Parameters-For-FACHLCR				CRITICALITY reject	EXTENSION UL-Synchronisation-Parameters-LCR		PRESENCE optional }|
{ ID id-PhysicalChannelID-for-CommonERNTI-RequestedIndicator	CRITICALITY ignore	EXTENSION PhysicalChannelID-for-CommonERNTI-RequestedIndicator	PRESENCE optional}|
{ ID id-Ul-common-E-DCH-MACflow-Specific-InfoListLCR-Ext		CRITICALITY ignore	EXTENSION Ul-common-E-DCH-MACflow-Specific-InfoListLCR-Ext	PRESENCE optional},
	...
}

Common-E-PUCH-InformationLCR ::= SEQUENCE {
	minCR										CodeRate,
	maxCR										CodeRate,
	harqInfo									HARQ-Info-for-E-DCH,
	pRXdes-base-perURAFCN						PRXdes-base-perURAFCN				OPTIONAL,
	e-PUCH-TPC-StepSize							TDD-TPC-UplinkStepSize-LCR			OPTIONAL,
	e-AGCH-TPC-StepSize							TDD-TPC-DownlinkStepSize			OPTIONAL,
	e-PUCH-PowerControlGAP						ControlGAP							OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { Common-E-PUCH-InformationLCR-ExtIEs } }		OPTIONAL,
	...
}

Common-E-PUCH-InformationLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PRXdes-base-perURAFCN ::= SEQUENCE (SIZE (1.. maxFrequencyinCell)) OF PRXdes-base-Item

PRXdes-base-Item ::= SEQUENCE {
	pRXdes-base									PRXdes-base,
	uARFCN										UARFCN											OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { PRXdes-base-Item-ExtIEs} }		OPTIONAL,
	...
}

PRXdes-base-Item-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}


Ul-common-E-DCH-MACflow-Specific-InfoListLCR ::= SEQUENCE (SIZE (1..maxNrOfCommonMACFlows)) OF Ul-common-E-DCH-MACflow-Specific-InfoList-ItemLCR

Ul-common-E-DCH-MACflow-Specific-InfoListLCR-Ext ::= SEQUENCE (SIZE (1.. maxNrOfCommonMACFlowsLCRExt)) OF Ul-common-E-DCH-MACflow-Specific-InfoList-ItemLCR

Ul-common-E-DCH-MACflow-Specific-InfoList-ItemLCR		 ::= SEQUENCE {
	ul-Common-MACFlowIDLCR								Common-MACFlow-ID-LCR,
	transportBearerRequestIndicator						TransportBearerRequestIndicator					OPTIONAL,
	bindingID											BindingID										OPTIONAL,
	transportLayerAddress								TransportLayerAddress							OPTIONAL, 
	tnlQos												TnlQos											OPTIONAL,
	payloadCRC-PresenceIndicator						PayloadCRC-PresenceIndicator					OPTIONAL,
	common-E-DCH-MACdFlow-Specific-InformationLCR		Common-E-DCH-MACdFlow-Specific-InfoListLCR		OPTIONAL,
	uARFCN												UARFCN											OPTIONAL,
	iE-Extensions										ProtocolExtensionContainer { { Ul-common-E-DCH-MACflow-Specific-InfoList-ItemLCR-ExtIEs} }					OPTIONAL,
	...
}

Ul-common-E-DCH-MACflow-Specific-InfoList-ItemLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-E-DCH-MACdFlow-Specific-InfoListLCR ::= SEQUENCE (SIZE (1.. maxNrOfEDCHMACdFlowsLCR)) OF Common-E-DCH-MACdFlow-Specific-InfoList-ItemLCR

Common-E-DCH-MACdFlow-Specific-InfoList-ItemLCR		 ::= SEQUENCE {
	common-e-DCH-MACdFlow-ID						E-DCH-MACdFlow-ID-LCR,
	maximum-Number-of-Retransmissions-For-E-DCH		Maximum-Number-of-Retransmissions-For-E-DCH			OPTIONAL,
	eDCH-MACdFlow-Multiplexing-List					E-DCH-MACdFlow-Multiplexing-List											OPTIONAL,
	common-E-DCHLogicalChannelInformation			Common-E-DCH-LogicalChannel-InfoList				OPTIONAL,
	eDCH-HARQ-PO-TDD								E-DCH-HARQ-PO-TDD															OPTIONAL,
	eDCH-MACdFlow-Retransmission-Timer				E-DCH-MACdFlow-Retransmission-Timer					OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { Common-E-DCH-MACdFlow-Specific-InfoList-ItemLCR-ExtIEs} }				OPTIONAL,
	...
}

Common-E-DCH-MACdFlow-Specific-InfoList-ItemLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}



Common-EDCH-System-Information-ResponseLCR ::= SEQUENCE {
	ul-common-E-DCH-MACflow-Specific-InfoResponseLCR			Ul-common-E-DCH-MACflow-Specific-InfoResponseListLCR		OPTIONAL,
	common-E-AGCH-ListLCR										Common-E-AGCH-ListLCR						OPTIONAL,
	common-E-HICH-ListLCR										Common-E-HICH-ListLCR						OPTIONAL,
	common-E-RNTI-Info-LCR										Common-E-RNTI-Info-LCR						OPTIONAL,
	iE-Extensions												ProtocolExtensionContainer { { Common-EDCH-System-Information-ResponseLCR-ExtIEs} }					OPTIONAL,
	...
}

Common-EDCH-System-Information-ResponseLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Ul-common-E-DCH-MACflow-Specific-InfoResponseListLCR-Ext	CRITICALITY ignore	EXTENSION Ul-common-E-DCH-MACflow-Specific-InfoResponseListLCR-Ext	PRESENCE optional}|
	{ ID id-UE-Status-Update-Confirm-Indicator							CRITICALITY ignore	EXTENSION BOOLEAN	PRESENCE optional},
	...
}

Ul-common-E-DCH-MACflow-Specific-InfoResponseListLCR ::= SEQUENCE (SIZE (1..maxNrOfCommonMACFlows)) OF Ul-common-E-DCH-MACflow-Specific-InfoResponseList-ItemLCR

Ul-common-E-DCH-MACflow-Specific-InfoResponseListLCR-Ext ::= SEQUENCE (SIZE (1..maxNrOfCommonMACFlowsLCRExt)) OF Ul-common-E-DCH-MACflow-Specific-InfoResponseList-ItemLCR

Ul-common-E-DCH-MACflow-Specific-InfoResponseList-ItemLCR ::= SEQUENCE {
	ul-Common-MACFlowID-LCR								Common-MACFlow-ID-LCR,
	bindingID											BindingID										OPTIONAL,
	transportLayerAddress								TransportLayerAddress							OPTIONAL, 
	uARFCN												UARFCN											OPTIONAL,
	-- the IE is not used.
	iE-Extensions										ProtocolExtensionContainer { { Ul-common-E-DCH-MACflow-Specific-InfoResponseList-ItemLCR-ExtIEs} }					OPTIONAL,
	...
}

Ul-common-E-DCH-MACflow-Specific-InfoResponseList-ItemLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-E-AGCH-ListLCR ::= SEQUENCE (SIZE (1.. maxNrOfEAGCHsLCR)) OF Common-E-AGCH-ItemLCR

Common-E-AGCH-ItemLCR ::= SEQUENCE {
	e-AGCH-ID									E-AGCH-Id,
	uARFCN										UARFCN											OPTIONAL,
	-- the IE is not used.
	iE-Extensions							ProtocolExtensionContainer { { Common-E-AGCH-ItemLCR-ExtIEs} }		OPTIONAL,
	...
}

Common-E-AGCH-ItemLCR-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-E-HICH-ListLCR ::= SEQUENCE (SIZE (1.. maxNrOfEHICHsLCR)) OF Common-E-HICH-ItemLCR

Common-E-HICH-ItemLCR ::= SEQUENCE {
	eI										EI,
	e-HICH-ID								E-HICH-ID-LCR,
	iE-Extensions							ProtocolExtensionContainer { { Common-E-HICH-ItemLCR-ExtIEs} }		OPTIONAL,
	...
}

Common-E-HICH-ItemLCR-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-E-RNTI-Info-LCR ::= SEQUENCE (SIZE (1.. maxnrofERUCCHsLCR)) OF Common-E-RNTI-Info-ItemLCR

Common-E-RNTI-Info-ItemLCR ::= SEQUENCE {
	starting-E-RNTI							E-RNTI,
	number-of-Group							INTEGER(1..32),
	number-of-e-E-RNTI-perGroup				INTEGER(1..7), 
	-- Values 3 to 7 shall not be used.
	iE-Extensions							ProtocolExtensionContainer { { Common-E-RNTI-Info-ItemLCR-ExtIEs} }		OPTIONAL,
	...
}

Common-E-RNTI-Info-ItemLCR-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
{ ID id-AssociatedPhsicalChannelID	CRITICALITY reject		EXTENSION	CommonPhysicalChannelID	PRESENCE optional},
	...
}

Common-MACFlows-to-DeleteLCR ::= SEQUENCE (SIZE (1.. maxNrOfCommonMACFlowsLCR)) OF Common-MACFlows-to-DeleteLCR-Item

Common-MACFlows-to-DeleteLCR-Item ::= SEQUENCE {
	common-MACFlow-ID-LCR							Common-MACFlow-ID-LCR,
	iE-Extensions									ProtocolExtensionContainer { { Common-MACFlows-to-DeleteLCR-Item-ExtIEs} }					OPTIONAL,
	...
}

Common-MACFlows-to-DeleteLCR-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}
Common-MACFlow-ID-LCR ::= INTEGER (0..maxNrOfCommonMACFlowsLCR-1)

CommonMACFlow-Specific-InfoListLCR ::= SEQUENCE (SIZE (1.. maxNrOfCommonMACFlowsLCR)) OF CommonMACFlow-Specific-InfoItemLCR

CommonMACFlow-Specific-InfoItemLCR ::= SEQUENCE {
	common-MACFlow-ID-LCR							Common-MACFlow-ID-LCR,
	bindingID										BindingID									OPTIONAL,
	transportLayerAddress							TransportLayerAddress						OPTIONAL,
	tnl-qos											TnlQos										OPTIONAL,
	common-MACFlow-PriorityQueue-InformationLCR		Common-MACFlow-PriorityQueue-Information	OPTIONAL,
	transportBearerRequestIndicator					TransportBearerRequestIndicator				OPTIONAL,
	uARFCN											UARFCN										OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { CommonMACFlow-Specific-InfoItemLCR-ExtIEs } }		OPTIONAL,
	...
}

CommonMACFlow-Specific-InfoItemLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}



Common-H-RNTI-InformationLCR ::= SEQUENCE (SIZE (1.. maxNoOfCommonH-RNTI)) OF Common-H-RNTI-InfoItemLCR

Common-H-RNTI-InfoItemLCR ::= SEQUENCE {
	common-H-RNTI									HSDSCH-RNTI,
	iE-Extensions									ProtocolExtensionContainer { { Common-H-RNTI-InfoItemLCR-ExtIEs } }		OPTIONAL,
	...
}

Common-H-RNTI-InfoItemLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Sync-InformationLCR ::= SEQUENCE {
	t-SYNC											T-SYNC,
	t-PROTECT										T-PROTECT,
	n-PROTECT										N-PROTECT,
	iE-Extensions									ProtocolExtensionContainer { { Sync-InformationLCR-ExtIEs } }		OPTIONAL,
	...
}

Sync-InformationLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


CommonMACFlow-Specific-InfoList-ResponseLCR ::= SEQUENCE (SIZE (1..maxNrOfCommonMACFlows)) OF CommonMACFlow-Specific-InfoItem-ResponseLCR

CommonMACFlow-Specific-InfoList-ResponseLCR-Ext ::= SEQUENCE (SIZE (1.. maxNrOfCommonMACFlowsLCRExt)) OF CommonMACFlow-Specific-InfoItem-ResponseLCR

CommonMACFlow-Specific-InfoItem-ResponseLCR ::= SEQUENCE {
	common-MACFlow-ID-LCR								Common-MACFlow-ID-LCR, 
	bindingID										BindingID									OPTIONAL,
	transportLayerAddress							TransportLayerAddress						OPTIONAL,
	hSDSCH-Initial-Capacity-Allocation				HSDSCH-Initial-Capacity-Allocation			OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { CommonMACFlow-Specific-InfoItem-ResponseLCR-ExtIEs} }			OPTIONAL,
	...
}

CommonMACFlow-Specific-InfoItem-ResponseLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}
CPC-InformationLCR ::= SEQUENCE {
	continuousPacketConnectivity-DRX-InformationLCR				ContinuousPacketConnectivity-DRX-InformationLCR							OPTIONAL,
	continuousPacketConnectivity-DRX-Information-to-Modify-LCR		ContinuousPacketConnectivity-DRX-Information-to-Modify-LCR			OPTIONAL,
	hS-DSCH-Semi-PersistentScheduling-Information-LCR			HS-DSCH-Semi-PersistentScheduling-Information-LCR							OPTIONAL,
	hS-DSCH-Semi-PersistentScheduling-Information-to-Modify-LCR	HS-DSCH-Semi-PersistentScheduling-Information-to-Modify-LCR				OPTIONAL,
	hS-DSCH-SPS-Deactivate-Indicator-LCR						NULL		OPTIONAL,
	e-DCH-Semi-PersistentScheduling-Information-LCR				E-DCH-Semi-PersistentScheduling-Information-LCR							OPTIONAL,
	e-DCH-Semi-PersistentScheduling-Information-to-Modify-LCR	E-DCH-Semi-PersistentScheduling-Information-to-Modify-LCR				OPTIONAL,
	e-DCH-SPS-Deactivate-Indicator-LCR							NULL		OPTIONAL,
	iE-Extensions				ProtocolExtensionContainer { { CPC-InformationLCR-ExtIEs} }													OPTIONAL,
	...
}

CPC-InformationLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ContinuousPacketConnectivity-DRX-CapabilityLCR ::= ENUMERATED {
	continuous-Packet-Connectivity-DRX-Capable,
	continuous-Packet-Connectivity-DRX-Non-Capable
}


ContinuousPacketConnectivity-DRX-InformationLCR ::= SEQUENCE {
	enabling-Delay								Enabling-Delay,
	hS-SCCH-DRX-Information-LCR					HS-SCCH-DRX-Information-LCR,
	e-AGCH-DRX-Information-LCR					E-AGCH-DRX-Information-LCR 			OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { ContinuousPacketConnectivity-DRX-InformationLCR-ExtIEs } }			OPTIONAL,
	...
}

ContinuousPacketConnectivity-DRX-InformationLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Enabling-Delay-Ext-LCR		CRITICALITY ignore	EXTENSION Enabling-Delay-Ext-LCR		PRESENCE optional },
	...
}

HS-SCCH-DRX-Information-LCR ::= SEQUENCE {
	hS-SCCH-UE-DRX-Cycle-LCR									UE-DRX-Cycle-LCR,
	hS-SCCH-Inactivity-Threshold-for-UE-DRX-Cycle-LCR			Inactivity-Threshold-for-UE-DRX-Cycle-LCR			OPTIONAL,
	hS-SCCH-UE-DRX-Offset-LCR									UE-DRX-Offset-LCR,
	iE-Extensions					ProtocolExtensionContainer { { HS-SCCH-DRX-Information-LCR-ExtIEs} } OPTIONAL,
	...
}

HS-SCCH-DRX-Information-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-HS-SCCH-Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext	CRITICALITY ignore	EXTENSION Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext	PRESENCE optional },
	...
}

E-AGCH-DRX-Information-LCR ::= CHOICE {
	sameAsHS-SCCH				NULL,
	e-AGCH-DRX-Parameters		E-AGCH-DRX-Parameters,
	...
}

E-AGCH-DRX-Parameters ::= SEQUENCE {
	e-AGCH-UE-DRX-Cycle-LCR								UE-DRX-Cycle-LCR,
	e-AGCH-UE-Inactivity-Monitor-Threshold				E-AGCH-UE-Inactivity-Monitor-Threshold			OPTIONAL,
	e-AGCH-UE-DRX-Offset-LCR							UE-DRX-Offset-LCR,
	iE-Extensions										ProtocolExtensionContainer { { E-AGCH-DRX-Parameters-ExtIEs} } OPTIONAL,
	...
}

E-AGCH-DRX-Parameters-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UE-DRX-Cycle-LCR ::= ENUMERATED {v1, v2, v4, v8, v16, v32, v64,...}
	-- Unit subframe

UE-DRX-Offset-LCR ::= INTEGER (0..63)
	-- Unit subframe

Inactivity-Threshold-for-UE-DRX-Cycle-LCR ::= ENUMERATED {v1, v2, v4, v8, v16, v32, v64,...}
	-- Unit subframe

Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext ::= ENUMERATED {v128, v256, v512,...}
	-- Unit subframe

E-AGCH-UE-Inactivity-Monitor-Threshold ::= ENUMERATED {v0, v1, v2, v4, v8, v16, v32, v64, v128, v256, v512, infinity,...}
	-- Unit subframe
 
ContinuousPacketConnectivity-DRX-Information-to-Modify-LCR ::= SEQUENCE {
	enabling-Delay								Enabling-Delay							OPTIONAL,
	dRX-Information-to-Modify-LCR				DRX-Information-to-Modify-LCR			OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { ContinuousPacketConnectivity-DRX-Information-to-Modify-LCR-ExtIEs } }				OPTIONAL,
	...
}

ContinuousPacketConnectivity-DRX-Information-to-Modify-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Enabling-Delay-Ext-LCR		CRITICALITY ignore	EXTENSION Enabling-Delay-Ext-LCR		PRESENCE optional },
	...
}

DRX-Information-to-Modify-LCR ::= CHOICE {
	modify			DRX-Information-to-Modify-Items-LCR,
	deactivate		NULL,
	...
}

DRX-Information-to-Modify-Items-LCR ::= SEQUENCE {
	hS-SCCH-DRX-Information-LCR					HS-SCCH-DRX-Information-LCR			OPTIONAL,
	e-AGCH-DRX-Information-LCR					E-AGCH-DRX-Information-LCR			OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { {DRX-Information-to-Modify-Items-LCR-ExtIEs} } OPTIONAL,
	...
}

DRX-Information-to-Modify-Items-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ContinuousPacketConnectivity-DRX-Information-ResponseLCR ::= SEQUENCE {
	enabling-Delay							Enabling-Delay							OPTIONAL,
	hS-SCCH-DRX-Information-ResponseLCR		HS-SCCH-DRX-Information-ResponseLCR		OPTIONAL,
	e-AGCH-DRX-Information-ResponseLCR		E-AGCH-DRX-Information-ResponseLCR		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { ContinuousPacketConnectivity-DRX-Information-ResponseLCR-ExtIEs } }			OPTIONAL,
	...
}

ContinuousPacketConnectivity-DRX-Information-ResponseLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Enabling-Delay-Ext-LCR		CRITICALITY ignore	EXTENSION Enabling-Delay-Ext-LCR		PRESENCE optional },
	...
}

HS-SCCH-DRX-Information-ResponseLCR ::= SEQUENCE {
	hS-SCCH-UE-DRX-Cycle-LCR									UE-DRX-Cycle-LCR		OPTIONAL,
	hS-SCCH-Inactivity-Threshold-for-UE-DRX-Cycle-LCR			Inactivity-Threshold-for-UE-DRX-Cycle-LCR		OPTIONAL,
	hS-SCCH-UE-DRX-Offset-LCR									UE-DRX-Offset-LCR		OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { HS-SCCH-DRX-Information-ResponseLCR-ExtIEs} } OPTIONAL,
	...
}

HS-SCCH-DRX-Information-ResponseLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-HS-SCCH-Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext	CRITICALITY ignore	EXTENSION Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext	PRESENCE optional },
	...
}

E-AGCH-DRX-Information-ResponseLCR ::= CHOICE {
	sameAsHS-SCCH						NULL,
	e-AGCH-DRX-Parameters-Response		E-AGCH-DRX-Parameters-Response,
	...
}

E-AGCH-DRX-Parameters-Response ::= SEQUENCE {
	e-AGCH-UE-DRX-Cycle-LCR							UE-DRX-Cycle-LCR						OPTIONAL,
	e-AGCH-UE-Inactivity-Monitor-Threshold			E-AGCH-UE-Inactivity-Monitor-Threshold	OPTIONAL,
	e-AGCH-UE-DRX-Offset-LCR						UE-DRX-Offset-LCR						OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { E-AGCH-DRX-Parameters-Response-ExtIEs} } OPTIONAL,
	...
}

E-AGCH-DRX-Parameters-Response-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Cell-Capability-Container-TDD-LCR ::= BIT STRING (SIZE (8))
-- First bit: Multi-Carrier E-DCH Operation Support Indicator
-- Second bit: Separate Iub Transport Bearer Support Indicator
-- Third bit: E-DCH UL flow multiplexing Support Indicator
-- Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver.

Common-E-RGCH-Operation-Indicator ::= ENUMERATED {
true
}


Common-E-RGCH-InfoFDD ::= SEQUENCE {
	e-RGCH-Channelisation-Code			FDD-DL-ChannelisationCodeNumber,
	e-RGCH-Signature-Sequence			E-RGCH-Signature-Sequence,
	minimum-Serving-Grant				E-Serving-Grant-Value				OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { Common-E-RGCH-InfoFDD-ExtIEs} } OPTIONAL,
	...
}

Common-E-RGCH-InfoFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


Concurrent-Deployment-of-2msand10ms-TTI ::= SEQUENCE {
	concurrent-TTI-Partition-Index								Concurrent-TTI-Partition-Index,
	common-E-DCH-System-Info-Parameters-for-Concurrent-TTI		Common-E-DCH-System-Info-Parameters-for-Concurrent-TTI,
	iE-Extensions										ProtocolExtensionContainer { { Concurrent-Deployment-of-2msand10ms-TTI-ExtIEs} } OPTIONAL,
	...
}

Concurrent-Deployment-of-2msand10ms-TTI-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Concurrent-TTI-Partition-Index ::= INTEGER (0..maxNrOfCommonEDCH)


Common-E-DCH-System-Info-Parameters-for-Concurrent-TTI ::= SEQUENCE {
	maxSet-E-DPDCHs										Max-Set-E-DPDCHs,
	ul-PunctureLimit									PunctureLimit,
	e-TFCS-Information									E-TFCS-Information,
	e-DPCCH-PO											E-DPCCH-PO													OPTIONAL,
	e-RGCH-2-IndexStepThreshold							E-RGCH-2-IndexStepThreshold									OPTIONAL,
	e-RGCH-3-IndexStepThreshold							E-RGCH-3-IndexStepThreshold									OPTIONAL,
	e-DCH-Reference-Power-Offset						E-DCH-Reference-Power-Offset								OPTIONAL,
	e-DCH-PowerOffset-for-SchedulingInfo				E-DCH-PowerOffset-for-SchedulingInfo						OPTIONAL,
	max-EDCH-Resource-Allocation-for-CCCH-extension		Max-EDCH-Resource-Allocation-for-CCCH-Extension			OPTIONAL,
	max-Period-for-Collision-Resolution					Max-Period-for-Collision-Resolution							OPTIONAL,
	max-TB-Sizes										Max-TB-Sizes												OPTIONAL,
	commonEDCH-AdditionalTransmissionBackOff			CommonEDCH-AdditionalTransmissionBackOff					OPTIONAL,
	common-E-DCH-E-AGCH-ChannelisationCodeNumber		FDD-DL-ChannelisationCodeNumber								OPTIONAL,
	common-E-DCH-HS-DPCCH-Information-forConcurrentTTI	Common-E-DCH-HS-DPCCH-Information-forConcurrentTTI		OPTIONAL,
	iE-Extensions										ProtocolExtensionContainer { { Common-E-DCH-System-Info-Parameters-for-Concurrent-TTI-ExtIEs} }
	OPTIONAL,
	...
}


Common-E-DCH-System-Info-Parameters-for-Concurrent-TTI-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-E-DCH-HS-DPCCH-Information-forConcurrentTTI ::= SEQUENCE {
	ackNackRepetitionFactor						AckNack-RepetitionFactor,
	ackPowerOffset								Ack-Power-Offset,
	nackPowerOffset								Nack-Power-Offset,
	common-E-DCH-CQI-Info		Common-E-DCH-CQI-Info						OPTIONAL,
	iE-Extensions				ProtocolExtensionContainer { { Common-E-DCH-HS-DPCCH-Information-forConcurrentTTI-ExtIEs} }		OPTIONAL,
	...
}

Common-E-DCH-HS-DPCCH-Information-forConcurrentTTI-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}



Common-E-DCH-Preamble-Control-Information-extensionList ::= SEQUENCE (SIZE (1.. maxnoofPRACHEUL)) OF Common-E-DCH-Preamble-Control-Information-extensionList-Item

Common-E-DCH-Preamble-Control-Information-extensionList-Item ::= SEQUENCE {
	common-E-DCH-Preamble-Control-Information-extension		Common-E-DCH-Preamble-Control-Information-extension,
	iE-Extensions						ProtocolExtensionContainer { { Common-E-DCH-Preamble-Control-Information-extensionList-Item-ExtIEs} }
	OPTIONAL,
	...
}

Common-E-DCH-Preamble-Control-Information-extensionList-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Common-E-DCH-Preamble-Control-Information-extension ::= SEQUENCE {
	commonPhysicalChannelID								CommonPhysicalChannelID,
	scramblingCodeNumber								ScramblingCodeNumber,
	common-E-DCH-PreambleSignatures						PreambleSignatures,
	preambleThreshold									PreambleThreshold,
	common-E-DCH-AICH-Information						Common-E-DCH-AICH-Information						OPTIONAL,
 	iE-Extensions										ProtocolExtensionContainer { { Common-E-DCH-Preamble-Control-Information-extension-Item-ExtIEs} }
	OPTIONAL,
	...
}

Common-E-DCH-Preamble-Control-Information-extension-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


Configuration-for-2msTTI-Common-E-DCH-ResourcesList::= SEQUENCE (SIZE (1.. maxNrOfCommonEDCH)) OF Configuration-for-2msTTI-Common-E-DCH-ResourcesList-Item

Configuration-for-2msTTI-Common-E-DCH-ResourcesList-Item ::= SEQUENCE {
	two-ms-HARQ-Process-Allocation		HARQ-Process-Allocation-2ms-EDCH,
	iE-Extensions						ProtocolExtensionContainer { { Configuration-for-2msTTI-Common-E-DCH-ResourcesList-Item-ExtIEs} }
	OPTIONAL,
	...
}

Configuration-for-2msTTI-Common-E-DCH-ResourcesList-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Coffset ::= INTEGER(0..29)


CHOICE-DRX-level ::= CHOICE {
	one-level-DRX				One-level-DRX,
	two-level-DRX				Two-level-DRX,
	...
}

-- ==========================================
--	D
-- ==========================================



DATA-ID ::= INTEGER (0..3)

DBDS-CorrectionsReq ::= SEQUENCE {
	dGANSS-Signal-ID	BIT STRING (SIZE (8)),
	ie-Extensions		ProtocolExtensionContainer { { DBDS-CorrectionsReq-ExtIEs } } OPTIONAL,
	... 
}

DBDS-CorrectionsReq-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DBDS-Corrections ::= SEQUENCE {
	bDS-RefTime				INTEGER (0..119),
-- Time = bDS-RefTime *30
	dBDS-InfoList			DBDS-InfoList,
	ie-Extensions			ProtocolExtensionContainer { { DBDS-Corrections-ExtIEs } } OPTIONAL,
	... 
}

DBDS-Corrections-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DBDS-Info ::= SEQUENCE {
	dBDS-SignalID			GANSS-Signal-ID		OPTIONAL,
	dBDS-SignalInfoList		DBDS-SignalInfoList,
	ie-Extensions			ProtocolExtensionContainer { { DBDS-Info-ExtIEs } } OPTIONAL,
	...
}

DBDS-Info-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DBDS-SignalInfoList ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF 
						DBDS-SignalInfo

DBDS-SignalInfo ::= SEQUENCE {
	svID 				INTEGER(0..63),
	bds-UDREI			INTEGER (0..15),
	bds-RURAI			INTEGER (0..15),
	bds-ECC-DeltaT		BIT STRING (SIZE (13)),
	ie-Extensions		ProtocolExtensionContainer { { DBDS-SignalInfo-ExtIEs } } OPTIONAL,
	...
}

DBDS-SignalInfo-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DBDS-InfoList ::= SEQUENCE (SIZE (1..maxSgnType)) OF DBDS-Info

DCH-ENH-Information ::= SEQUENCE {
	pO-SRB				PowerOffset,
	dl-FET-Mode			DL-FET-Mode,
	dCH-ENH-Concat		DCH-ENH-Concat		OPTIONAL
-- This IE shall be present if dl-FET-Mode is equal to “full” --,
	iE-Extensions							ProtocolExtensionContainer { { DCH-ENH-Information-ExtIEs } }	OPTIONAL,
	...
}

DCH-ENH-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DCH-ENH-Information-to-Modify ::= SEQUENCE {
	pO-SRB				PowerOffset			OPTIONAL,
	dl-FET-Mode			DL-FET-Mode			OPTIONAL,
	dCH-ENH-Concat		DCH-ENH-Concat		OPTIONAL
-- This IE shall be present if dl-FET-Mode is equal to “full” --,
	iE-Extensions							ProtocolExtensionContainer { { DCH-ENH-Information-to-Modify-ExtIEs } }		OPTIONAL,
	...
}

DCH-ENH-Information-to-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-FET-Mode ::= ENUMERATED {
	basic,
	full,
	...
}

DCH-ENH-Concat ::= SEQUENCE (SIZE (1.. maxNrofConcatenatedDCH)) OF DCH-ID

DCH-ENH-Information-Reconf ::=SEQUENCE{
	setup-Or-ConfigurationChange-Or-Removal-Of-DCH-ENH		Setup-Or-ConfigurationChange-Or-Removal-Of-DCH-ENH,
	iE-Extensions											ProtocolExtensionContainer { { DCH-ENH-Information-Reconf-ExtIEs} } OPTIONAL,
	...
}

DCH-ENH-Information-Reconf-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DCH-ENH-Information-Removal ::= ENUMERATED {
	remove,
	...
}

DCH-ID ::= INTEGER (0..255)

DCH-FDD-Information ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-FDD-InformationItem

DCH-FDD-InformationItem ::= SEQUENCE {
	payloadCRC-PresenceIndicator		PayloadCRC-PresenceIndicator,
	ul-FP-Mode							UL-FP-Mode,
	toAWS								ToAWS,
	toAWE								ToAWE,
	dCH-SpecificInformationList			DCH-Specific-FDD-InformationList,
	iE-Extensions						ProtocolExtensionContainer { { DCH-FDD-InformationItem-ExtIEs} }	OPTIONAL,
	...
}

DCH-FDD-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TnlQos						CRITICALITY ignore		EXTENSION TnlQos		PRESENCE optional	},
	...
}

DCH-Specific-FDD-InformationList ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-Specific-FDD-Item

DCH-Specific-FDD-Item ::=	SEQUENCE {
	dCH-ID								DCH-ID,
	ul-TransportFormatSet				TransportFormatSet,
	dl-TransportFormatSet				TransportFormatSet,
	allocationRetentionPriority			AllocationRetentionPriority,
	frameHandlingPriority				FrameHandlingPriority,
	qE-Selector							QE-Selector,
	iE-Extensions						ProtocolExtensionContainer { { DCH-Specific-FDD-Item-ExtIEs} }	OPTIONAL,
	...
}

DCH-Specific-FDD-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Unidirectional-DCH-Indicator	CRITICALITY reject	EXTENSION Unidirectional-DCH-Indicator	PRESENCE optional	},
	...
}

DCH-Indicator-For-E-DCH-HSDPA-Operation ::= ENUMERATED {
	dch-not-present
}

DCH-InformationResponse ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-InformationResponseItem

DCH-InformationResponseItem ::= SEQUENCE {
	dCH-ID											DCH-ID,
	bindingID										BindingID				OPTIONAL,
	transportLayerAddress							TransportLayerAddress	OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { DCH-InformationResponseItem-ExtIEs} }		OPTIONAL,
	...
}

DCH-InformationResponseItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TransportBearerNotSetupIndicator	CRITICALITY ignore	EXTENSION TransportBearerNotSetupIndicator		PRESENCE optional	}, -- FDD only
	...
}

DCH-MeasurementOccasion-Information ::= SEQUENCE (SIZE (1.. maxNrOfDCHMeasurementOccasionPatternSequence)) OF DchMeasurementOccasionInformation-Item

DchMeasurementOccasionInformation-Item ::= SEQUENCE {
	pattern-Sequence-Identifier					Pattern-Sequence-Identifier,
	status-Flag									Status-Flag,
	measurement-Occasion-Pattern-Sequence-parameters					Measurement-Occasion-Pattern-Sequence-parameters 			OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { DCH-MeasurementOccasion-Information-ExtIEs } }			OPTIONAL,
	...
}

DCH-MeasurementOccasion-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Measurement-Occasion-Pattern-Sequence-parameters ::= SEQUENCE {
	measurement-Occasion-Pattern-Sequence-parameters-k					INTEGER(1..9),
	measurement-Occasion-Pattern-Sequence-parameters-offset				INTEGER(0..511),
	measurement-Occasion-Pattern-Sequence-parameters-M-Length			INTEGER(1..512),
	measurement-Occasion-Pattern-Sequence-parameters-Timeslot-Bitmap	BIT STRING (SIZE (7)),
	iE-Extensions				ProtocolExtensionContainer { { Measurement-Occasion-Pattern-Sequence-parameters-ExtIEs } } OPTIONAL,
	...
}

Measurement-Occasion-Pattern-Sequence-parameters-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DCH-TDD-Information ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-TDD-InformationItem

DCH-TDD-InformationItem ::= SEQUENCE {
	payloadCRC-PresenceIndicator		PayloadCRC-PresenceIndicator,
	ul-FP-Mode							UL-FP-Mode,
	toAWS								ToAWS,
	toAWE								ToAWE,
	dCH-SpecificInformationList			DCH-Specific-TDD-InformationList,
	iE-Extensions							ProtocolExtensionContainer { { DCH-TDD-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

DCH-TDD-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-TnlQos						CRITICALITY ignore		EXTENSION TnlQos		PRESENCE optional},
	...
}

DCH-Specific-TDD-InformationList ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-Specific-TDD-Item

DCH-Specific-TDD-Item ::=	SEQUENCE {
	dCH-ID									DCH-ID,
	ul-CCTrCH-ID							CCTrCH-ID,
	dl-CCTrCH-ID							CCTrCH-ID,
	ul-TransportFormatSet					TransportFormatSet,
	dl-TransportFormatSet					TransportFormatSet,
	allocationRetentionPriority				AllocationRetentionPriority,
	frameHandlingPriority					FrameHandlingPriority,
	qE-Selector								QE-Selector						OPTIONAL,
	-- This IE shall be present if DCH is part of set of Coordinated DCHs
	iE-Extensions							ProtocolExtensionContainer { { DCH-Specific-TDD-Item-ExtIEs} }		OPTIONAL,
	...
}

DCH-Specific-TDD-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Unidirectional-DCH-Indicator	CRITICALITY reject	EXTENSION Unidirectional-DCH-Indicator	PRESENCE optional	},
	...
}

FDD-DCHs-to-Modify ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF FDD-DCHs-to-ModifyItem

FDD-DCHs-to-ModifyItem	 ::= SEQUENCE {
	ul-FP-Mode							UL-FP-Mode		OPTIONAL,
	toAWS								ToAWS			OPTIONAL,
	toAWE								ToAWE			OPTIONAL,
	transportBearerRequestIndicator		TransportBearerRequestIndicator,
	dCH-SpecificInformationList			DCH-ModifySpecificInformation-FDD,
	iE-Extensions						ProtocolExtensionContainer { { FDD-DCHs-to-ModifyItem-ExtIEs} }		OPTIONAL,
	...
}

FDD-DCHs-to-ModifyItem-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-TnlQos						CRITICALITY ignore		EXTENSION TnlQos		PRESENCE optional},
	...
}

DCH-ModifySpecificInformation-FDD::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-ModifySpecificItem-FDD

DCH-ModifySpecificItem-FDD::=	SEQUENCE {
	dCH-ID											DCH-ID,
	ul-TransportFormatSet							TransportFormatSet			OPTIONAL,
	dl-TransportFormatSet							TransportFormatSet			OPTIONAL,
	allocationRetentionPriority						AllocationRetentionPriority	OPTIONAL,
	frameHandlingPriority							FrameHandlingPriority		OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { DCH-ModifySpecificItem-FDD-ExtIEs} }		OPTIONAL,
	...
}

DCH-ModifySpecificItem-FDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-Unidirectional-DCH-Indicator					CRITICALITY reject		EXTENSION Unidirectional-DCH-Indicator		PRESENCE optional},
	...
}


TDD-DCHs-to-Modify ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-ModifyItem-TDD

DCH-ModifyItem-TDD ::= SEQUENCE {
	ul-FP-Mode							UL-FP-Mode		OPTIONAL,
	toAWS								ToAWS			OPTIONAL,
	toAWE								ToAWE			OPTIONAL,
	transportBearerRequestIndicator		TransportBearerRequestIndicator,
	dCH-SpecificInformationList			DCH-ModifySpecificInformation-TDD,
	iE-Extensions						ProtocolExtensionContainer { { TDD-DCHs-to-ModifyItem-ExtIEs} }			OPTIONAL,
	...
}

TDD-DCHs-to-ModifyItem-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-TnlQos						CRITICALITY ignore		EXTENSION TnlQos		PRESENCE optional},
	...
}

DCH-ModifySpecificInformation-TDD ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-ModifySpecificItem-TDD

DCH-ModifySpecificItem-TDD ::=	SEQUENCE {
	dCH-ID											DCH-ID,
	ul-CCTrCH-ID									CCTrCH-ID					OPTIONAL,
	dl-CCTrCH-ID									CCTrCH-ID					OPTIONAL,
	ul-TransportFormatSet							TransportFormatSet			OPTIONAL,
	dl-TransportFormatSet							TransportFormatSet			OPTIONAL,
	allocationRetentionPriority						AllocationRetentionPriority	OPTIONAL,
	frameHandlingPriority							FrameHandlingPriority		OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { DCH-ModifySpecificItem-TDD-ExtIEs} }			OPTIONAL,
	...
}

DCH-ModifySpecificItem-TDD-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DecimationFactor ::= ENUMERATED {
	slots3,
	slots5
}

DedicatedChannelsCapacityConsumptionLaw ::= SEQUENCE ( SIZE(1..maxNrOfSF) ) OF
	SEQUENCE {
		dl-Cost-1		INTEGER (0..65535),
		dl-Cost-2		INTEGER (0..65535),
		ul-Cost-1		INTEGER (0..65535),
		ul-Cost-2		INTEGER (0..65535),
		iE-Extensions		ProtocolExtensionContainer { { DedicatedChannelsCapacityConsumptionLaw-ExtIEs } }		OPTIONAL,
	...
}

DedicatedChannelsCapacityConsumptionLaw-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DedicatedMeasurementType ::= ENUMERATED {
	sir,
	sir-error,
	transmitted-code-power,
	rscp,
	rx-timing-deviation,
	round-trip-time,
	...,
	rx-timing-deviation-LCR,
	angle-Of-Arrival-LCR,
	hs-sich-quality,
	best-Cell-Portions,
	rx-timing-deviation-768,
	rx-timing-deviation-384-extended,
	best-Cell-PortionsLCR,
	aOA-per-CELL-Portion-LCR,
	uE-transmission-power-headroom,
	dl-TBS

}

DedicatedMeasurementValue ::= CHOICE {
	sIR-Value						SIR-Value,
	sIR-ErrorValue					SIR-Error-Value,
	transmittedCodePowerValue			Transmitted-Code-Power-Value,
	rSCP								RSCP-Value,
	rxTimingDeviationValue				Rx-Timing-Deviation-Value,
	roundTripTime						Round-Trip-Time-Value,
	...,
	extension-DedicatedMeasurementValue		Extension-DedicatedMeasurementValue
}

Extension-DedicatedMeasurementValue	::= ProtocolIE-Single-Container {{ Extension-DedicatedMeasurementValueIE }}

Extension-DedicatedMeasurementValueIE NBAP-PROTOCOL-IES ::= {
	{ ID id-Rx-Timing-Deviation-Value-LCR		CRITICALITY reject	TYPE Rx-Timing-Deviation-Value-LCR				PRESENCE mandatory}|
	{ ID id-Angle-Of-Arrival-Value-LCR			CRITICALITY reject	TYPE Angle-Of-Arrival-Value-LCR					PRESENCE mandatory}|
	{ ID id-HS-SICH-Reception-Quality			CRITICALITY reject	TYPE HS-SICH-Reception-Quality-Value			PRESENCE mandatory}|
	{ ID id-Best-Cell-Portions-Value			CRITICALITY reject	TYPE Best-Cell-Portions-Value						PRESENCE mandatory}|
	{ ID id-Rx-Timing-Deviation-Value-768		CRITICALITY reject	TYPE Rx-Timing-Deviation-Value-768				PRESENCE mandatory}|
	{ ID id-Rx-Timing-Deviation-Value-384-ext	CRITICALITY reject	TYPE Rx-Timing-Deviation-Value-384-ext			PRESENCE mandatory}|
	{ ID id-Extended-Round-Trip-Time-Value		CRITICALITY reject	TYPE Extended-Round-Trip-Time-Value				PRESENCE mandatory}|
	{ ID id-Best-Cell-Portions-ValueLCR			CRITICALITY reject	TYPE Best-Cell-Portions-ValueLCR					PRESENCE mandatory}|
	{ ID id-AOA-per-CELL-Portion-LCR			CRITICALITY reject	TYPE AOA-per-CELL-Portion-LCR						PRESENCE mandatory}|
	{ ID id-UE-transmission-power-headroom		CRITICALITY reject	TYPE UE-transmission-power-headroom-Value		PRESENCE mandatory}|
	{ ID id-DL-TBS								CRITICALITY reject 	TYPE DL-TBS											PRESENCE mandatory},
	...
}

DedicatedMeasurementValueInformation ::= CHOICE {
	measurementAvailable		DedicatedMeasurementAvailable,
	measurementnotAvailable		DedicatedMeasurementnotAvailable
}

DedicatedMeasurementAvailable::= SEQUENCE {
	dedicatedmeasurementValue		DedicatedMeasurementValue,
    cFN                             CFN							OPTIONAL,
	ie-Extensions					ProtocolExtensionContainer { { DedicatedMeasurementAvailableItem-ExtIEs} }		OPTIONAL,
	...
}

DedicatedMeasurementAvailableItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DedicatedMeasurementnotAvailable ::= NULL

DelayedActivation ::= CHOICE {
	cfn						CFN,
	separate-indication		NULL
}

DelayedActivationUpdate ::= CHOICE {
	activate		Activate-Info,
	deactivate		Deactivate-Info
}

Activate-Info ::= SEQUENCE {
	activation-type  		Execution-Type,
	initial-dl-tx-power 	DL-Power,
	firstRLS-Indicator		FirstRLS-Indicator											OPTIONAL, --FDD Only
	propagation-delay		PropagationDelay 											OPTIONAL, --FDD Only
	iE-Extensions			ProtocolExtensionContainer { { Activate-Info-ExtIEs} }		OPTIONAL,
	...
}

Activate-Info-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-ExtendedPropagationDelay	CRITICALITY reject	EXTENSION ExtendedPropagationDelay		PRESENCE mandatory }, --FDD Only
	...
}

Deactivate-Info ::= SEQUENCE {
	deactivation-type  		Execution-Type,
	iE-Extensions			ProtocolExtensionContainer { { Deactivate-Info-ExtIEs} }		OPTIONAL,
	...
}

Deactivate-Info-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Execution-Type ::= CHOICE {
	synchronised 	CFN,
	unsynchronised	NULL
}

DeltaSIR				::= INTEGER (0..30)
-- Unit dB, Step 0.1 dB, Range 0..3 dB.

DGANSSCorrections ::= SEQUENCE {
	dGANSS-ReferenceTime				INTEGER(0..119),
	dGANSS-Information					DGANSS-Information,
	ie-Extensions						ProtocolExtensionContainer { { DGANSSCorrections-ExtIEs } }	OPTIONAL,
	...
}

DGANSSCorrections-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DGANSS-Corrections-Req ::= SEQUENCE {
	dGANSS-Signal-ID					BIT STRING (SIZE (8)),
	ie-Extensions		 				ProtocolExtensionContainer { { DGANSS-Corrections-Req-ExtIEs } }	OPTIONAL,
	...
}

DGANSS-Corrections-Req-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-GANSS-ID				CRITICALITY	ignore	EXTENSION	GANSS-ID			PRESENCE	optional},
	...
}

DGANSS-Information ::= SEQUENCE (SIZE (1..maxSgnType)) OF DGANSS-InformationItem

DGANSS-InformationItem ::= SEQUENCE {
	gANSS-SignalId						GANSS-Signal-ID												OPTIONAL,
	gANSS-StatusHealth					GANSS-StatusHealth,
-- The following IE shall be present if the Status Health IE value is not equal to “no data” or “invalid data”
	dGANSS-SignalInformation			DGANSS-SignalInformation									OPTIONAL,
	ie-Extensions		 				ProtocolExtensionContainer { { DGANSS-InformationItem-ExtIEs } }	OPTIONAL,
	...
}

DGANSS-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DGANSS-SignalInformation ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF DGANSS-SignalInformationItem

DGANSS-SignalInformationItem ::= SEQUENCE {
	satId								INTEGER(0..63),
	gANSS-iod							BIT STRING (SIZE (10)),
	udre								UDRE,
	ganss-prc							INTEGER(-2047..2047),
	ganss-rrc							INTEGER(-127..127),
	ie-Extensions						ProtocolExtensionContainer { { DGANSS-SignalInformationItem-ExtIEs } }	OPTIONAL,
	...
}

DGANSS-SignalInformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-DGNSS-ValidityPeriod	CRITICALITY	ignore	EXTENSION	DGNSS-ValidityPeriod	PRESENCE	optional},
	...
}

DGANSSThreshold ::= SEQUENCE {
	pRCDeviation						PRCDeviation,
	ie-Extensions						ProtocolExtensionContainer { { DGANSSThreshold-ExtIEs } }	OPTIONAL,
	...
}

DGANSSThreshold-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DGNSS-ValidityPeriod ::= 			SEQUENCE {
	udreGrowthRate						UDREGrowthRate,
	udreValidityTime					UDREValidityTime,
	iE-Extensions						ProtocolExtensionContainer { { DGNSS-ValidityPeriod-ExtIEs } }		OPTIONAL,
	...
}

DGNSS-ValidityPeriod-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DGPSCorrections ::= SEQUENCE {
   gpstow                GPSTOW,
   status-health         GPS-Status-Health,
   satelliteinfo         SAT-Info-DGPSCorrections,
   ie-Extensions		 ProtocolExtensionContainer { { DGPSCorrections-ExtIEs} }		OPTIONAL,
   ...
}

DGPSCorrections-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DGPSThresholds ::= SEQUENCE {
   prcdeviation         PRCDeviation,
   ie-Extensions		ProtocolExtensionContainer { { DGPSThresholds-ExtIEs} }		OPTIONAL,
   ...
}

DGPSThresholds-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DiscardTimer ::= ENUMERATED {v20,v40,v60,v80,v100,v120,v140,v160,v180,v200,v250,v300,v400,v500,v750,v1000,v1250,v1500,v1750,v2000,v2500,v3000,v3500,v4000,v4500,v5000,v7500,
 ...
}

DiversityControlField ::= ENUMERATED {
	may,
	must,
	must-not,
	...
}

DiversityMode ::= ENUMERATED {
	none, 
	sTTD,
	closed-loop-mode1,
	not-used-closed-loop-mode2,
	...
}

DL-TBS ::= SEQUENCE {
	hs-DSCH-Cell-List			HS-DSCH-Cell-List,
	iE-Extensions				ProtocolExtensionContainer { { DL-TBS-ExtIEs} }		OPTIONAL,
	...
}

DL-TBS-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-DSCH-Cell-List ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF HS-DSCH-Cell

HS-DSCH-Cell ::=SEQUENCE{
	hs-DSCH-Cell-TBS			DL-TBS-Value,
	iE-Extensions				ProtocolExtensionContainer { { HS-DSCH-Cell-ExtIEs} } OPTIONAL,
	...
}

HS-DSCH-Cell-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-TBS-Value ::= INTEGER (0..160000)

DL-DPCH-SlotFormat ::= INTEGER (0..16,...,17..18)

DL-DPCH-TimingAdjustment ::= ENUMERATED {
	timing-advance,
	timing-delay
}

DL-Timeslot-Information ::= SEQUENCE (SIZE (1.. maxNrOfDLTSs)) OF DL-Timeslot-InformationItem

DL-Timeslot-InformationItem	 ::= SEQUENCE {
	timeSlot								TimeSlot,
	midambleShiftAndBurstType				MidambleShiftAndBurstType,
	tFCI-Presence							TFCI-Presence,
	dL-Code-Information						TDD-DL-Code-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-Timeslot-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

DL-Timeslot-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-TimeslotLCR-Information ::= SEQUENCE (SIZE (1.. maxNrOfDLTSLCRs)) OF DL-TimeslotLCR-InformationItem

DL-TimeslotLCR-InformationItem	 ::= SEQUENCE {
	timeSlotLCR								TimeSlotLCR,
	midambleShiftLCR						MidambleShiftLCR,
	tFCI-Presence							TFCI-Presence,
	dL-Code-LCR-Information					TDD-DL-Code-LCR-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-TimeslotLCR-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

DL-TimeslotLCR-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Initial-DL-Power-TimeslotLCR-InformationItem	CRITICALITY ignore   EXTENSION DL-Power		PRESENCE optional	}|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-Maximum-DL-Power-TimeslotLCR-InformationItem	CRITICALITY ignore   EXTENSION DL-Power		PRESENCE optional	}|
	-- Applicable to 1.28Mcps TDD only
	{ ID id-Minimum-DL-Power-TimeslotLCR-InformationItem	CRITICALITY ignore 	EXTENSION DL-Power		PRESENCE optional	},
	-- Applicable to 1.28Mcps TDD only
	...
}

DL-Timeslot768-Information ::= SEQUENCE (SIZE (1.. maxNrOfDLTSs)) OF DL-Timeslot768-InformationItem

DL-Timeslot768-InformationItem	 ::= SEQUENCE {
	timeSlot								TimeSlot,
	midambleShiftAndBurstType768			MidambleShiftAndBurstType768,
	tFCI-Presence							TFCI-Presence,
	dL-Code-768-Information					TDD-DL-Code-768-Information,
	iE-Extensions							ProtocolExtensionContainer { { DL-Timeslot768-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

DL-Timeslot768-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-FrameType ::= ENUMERATED {
	typeA,
	typeB,
	...
}

DL-or-Global-CapacityCredit ::= INTEGER (0..65535)

DL-Power ::= INTEGER (-350..150)
-- Value = DL-Power/10
-- Unit dB, Range -35dB .. +15dB, Step +0.1dB

DLPowerAveragingWindowSize ::= INTEGER (1..60)

DL-PowerBalancing-Information ::= SEQUENCE {
	powerAdjustmentType					PowerAdjustmentType,
    dLReferencePower					DL-Power		OPTIONAL,
	-- This IE shall be present if Power Adjustment Type IE equals to 'Common'
	dLReferencePowerList-DL-PC-Rqst		DL-ReferencePowerInformationList		OPTIONAL,
	-- This IE shall be present if Power Adjustment Type IE equals to 'Individual'
	maxAdjustmentStep					MaxAdjustmentStep		OPTIONAL,
	-- This IE shall be present if Power Adjustment Type IE equals to 'Common' or 'Individual'
	adjustmentPeriod					AdjustmentPeriod		OPTIONAL,
	-- This IE shall be present if Power Adjustment Type IE equals to 'Common' or 'Individual'
	adjustmentRatio						ScaledAdjustmentRatio	OPTIONAL,
	-- This IE shall be present if Power Adjustment Type IE equals to 'Common' or 'Individual'
	iE-Extensions						ProtocolExtensionContainer { { DL-PowerBalancing-Information-ExtIEs } } OPTIONAL,
	...
}

DL-PowerBalancing-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-ReferencePowerInformationList 		::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF DL-ReferencePowerInformationItem

DL-ReferencePowerInformationItem ::= SEQUENCE {
	rL-ID						RL-ID,
	dl-Reference-Power			DL-Power,
	iE-Extensions				ProtocolExtensionContainer { {DL-ReferencePowerInformationItem-ExtIEs} } OPTIONAL,
	...
}

DL-ReferencePowerInformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-PowerBalancing-ActivationIndicator	::= ENUMERATED {
	dL-PowerBalancing-Activated
}

DL-PowerBalancing-UpdatedIndicator	::= ENUMERATED {
	dL-PowerBalancing-Updated
}

DL-ScramblingCode ::= INTEGER (0..15)
-- 0= Primary scrambling code of the cell, 1..15= Secondary scrambling code --

DL-TimeslotISCP ::= INTEGER (0..91)

DL-TimeslotISCPInfo ::= SEQUENCE (SIZE (1..maxNrOfDLTSs)) OF DL-TimeslotISCPInfoItem

DL-TimeslotISCPInfoItem ::= SEQUENCE {
	timeSlot					TimeSlot,
	dL-TimeslotISCP				DL-TimeslotISCP,
	iE-Extensions				ProtocolExtensionContainer { {DL-TimeslotISCPInfoItem-ExtIEs} }			OPTIONAL,
	...
	}

DL-TimeslotISCPInfoItem-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-TimeslotISCPInfoLCR ::= SEQUENCE (SIZE (1..maxNrOfDLTSLCRs)) OF DL-TimeslotISCPInfoItemLCR

DL-TimeslotISCPInfoItemLCR ::= SEQUENCE {
	timeSlotLCR					TimeSlotLCR,
	dL-TimeslotISCP				DL-TimeslotISCP,
	iE-Extensions				ProtocolExtensionContainer { {DL-TimeslotISCPInfoItemLCR-ExtIEs} }			OPTIONAL,
	...
	}

DL-TimeslotISCPInfoItemLCR-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-TPC-Pattern01Count ::= INTEGER (0..30,...)

DLTransmissionBranchLoadValue ::= INTEGER (0..101,...)

Downlink-Compressed-Mode-Method 	::= ENUMERATED {
	not-Used-puncturing,
	sFdiv2,
	higher-layer-scheduling,
	...
}

DL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfDLTSLCRs)) OF DL-HS-PDSCH-Timeslot-InformationItem-LCR-PSCH-ReconfRqst

DL-HS-PDSCH-Timeslot-InformationItem-LCR-PSCH-ReconfRqst::= SEQUENCE {
	timeSlot									TimeSlotLCR,
	midambleShiftAndBurstType					MidambleShiftLCR,
	dl-HS-PDSCH-Codelist-LCR-PSCH-ReconfRqst		DL-HS-PDSCH-Codelist-LCR-PSCH-ReconfRqst,
	maxHSDSCH-HSSCCH-Power						MaximumTransmissionPower					OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { DL-HS-PDSCH-Timeslot-InformationItem-LCR-PSCH-ReconfRqst-ExtIEs} }		OPTIONAL,
	...
}

DL-HS-PDSCH-Timeslot-InformationItem-LCR-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MaxHSDSCH-HSSCCH-Power-per-CELLPORTION						CRITICALITY ignore		EXTENSION MaxHSDSCH-HSSCCH-Power-per-CELLPORTION					PRESENCE optional},
	...
}

MaxHSDSCH-HSSCCH-Power-per-CELLPORTION ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCellLCR)) OF MaxHSDSCH-HSSCCH-Power-per-CELLPORTION-Item

MaxHSDSCH-HSSCCH-Power-per-CELLPORTION-Item::= SEQUENCE {
	cellPortionLCRID							CellPortionLCRID,
	maxHSDSCH-HSSCCH-Power						MaximumTransmissionPower,
	iE-Extensions								ProtocolExtensionContainer { { MaxHSDSCH-HSSCCH-Power-per-CELLPORTION-Item-ExtIEs} }		OPTIONAL,
	...
}

MaxHSDSCH-HSSCCH-Power-per-CELLPORTION-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DL-HS-PDSCH-Codelist-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (1..maxNrOfHSPDSCHs)) OF TDD-ChannelisationCode

Downlink-TPC-enhancements-Information ::= SEQUENCE {
	decimationFactorforPrimaryFrequency			DecimationFactor			OPTIONAL,
	decimationFactorforSecFrequency				DecimationFactor			OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { Downlink-TPC-enhancements-Information-ExtIEs } }		OPTIONAL,
	...
}

Downlink-TPC-enhancements-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Downlink-TPC-enhancements-Reconf ::= SEQUENCE{
	setup-Or-ConfigurationChange-Or-Removal-Of-Downlink-TPC-enhancements			Setup-Or-ConfigurationChange-Or-Removal-Of-Downlink-TPC-enhancements,
	iE-Extensions													ProtocolExtensionContainer { { Downlink-TPC-enhancements-Reconf-ExtIEs} }		OPTIONAL,
	...
}

Downlink-TPC-enhancements-Reconf-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Downlink-TPC-enhancements-Information-Removal ::= ENUMERATED {
	remove,
	...
}

DPC-Mode ::= ENUMERATED {
	mode0,
	mode1,
	...
}

DPCH-ID ::= INTEGER (0..239)

DPCH-ID768 ::= INTEGER (0..479)

DRX-Information ::= SEQUENCE {
	uE-DRX-Cycle							UE-DRX-Cycle,
	inactivity-Threshold-for-UE-DRX-Cycle							Inactivity-Threshold-for-UE-DRX-Cycle,
	inactivity-Threshold-for-UE-Grant-Monitoring					Inactivity-Threshold-for-UE-Grant-Monitoring,
	uE-DRX-Grant-Monitoring 				UE-DRX-Grant-Monitoring,
	iE-Extensions							ProtocolExtensionContainer { {DRX-Information-ExtIEs} } OPTIONAL,
	...
}

DRX-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UE-DRX-Cycle2								CRITICALITY ignore	EXTENSION UE-DRX-Cycle									PRESENCE optional}|
	{ ID id-Inactivity-Threshold-for-UE-DRX-Cycle2		CRITICALITY ignore	EXTENSION Inactivity-Threshold-for-UE-DRX-Cycle	PRESENCE optional},
	...
}

DRX-Information-to-Modify ::= CHOICE {
	modify			DRX-Information-to-Modify-Items,
	deactivate		NULL,
	...
}

DRX-Information-to-Modify-Items ::= SEQUENCE {
	uE-DRX-Cycle													UE-DRX-Cycle											OPTIONAL, 
	inactivity-Threshold-for-UE-DRX-Cycle							Inactivity-Threshold-for-UE-DRX-Cycle				OPTIONAL, 
	inactivity-Threshold-for-UE-Grant-Monitoring					Inactivity-Threshold-for-UE-Grant-Monitoring		OPTIONAL,
	uE-DRX-Grant-Monitoring 										UE-DRX-Grant-Monitoring									OPTIONAL,
	iE-Extensions								 ProtocolExtensionContainer { {DRX-Information-to-Modify-Items-ExtIEs} } OPTIONAL,
	...
}

DRX-Information-to-Modify-Items-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-UE-DRX-Cycle2								CRITICALITY ignore	EXTENSION UE-DRX-Cycle									PRESENCE optional}|
	{ ID id-Inactivity-Threshold-for-UE-DRX-Cycle2		CRITICALITY ignore	EXTENSION Inactivity-Threshold-for-UE-DRX-Cycle	PRESENCE optional},
	...
}


DRX-Interruption-by-HS-DSCH ::= ENUMERATED {
	drx-Interruption-Configured,
	drx-Interruption-Not-Configured,
	...
}

DSCH-ID ::= INTEGER (0..255)

DSCH-InformationResponse ::= SEQUENCE (SIZE (1..maxNrOfDSCHs)) OF DSCH-InformationResponseItem

DSCH-InformationResponseItem ::= SEQUENCE {
	dSCH-ID											DSCH-ID,
	bindingID										BindingID					OPTIONAL,
	transportLayerAddress							TransportLayerAddress		OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { DSCH-InformationResponseItem-ExtIEs } }		OPTIONAL,
	...
}

DSCH-InformationResponseItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DSCH-TDD-Information ::= SEQUENCE (SIZE (1..maxNrOfDSCHs)) OF DSCH-TDD-InformationItem

DSCH-TDD-InformationItem ::= SEQUENCE {
	dSCH-ID									DSCH-ID,
	cCTrCH-ID								CCTrCH-ID,
	transportFormatSet						TransportFormatSet,
	allocationRetentionPriority				AllocationRetentionPriority,
	frameHandlingPriority					FrameHandlingPriority,
	toAWS									ToAWS,
	toAWE									ToAWE,
	iE-Extensions							ProtocolExtensionContainer { { DSCH-TDD-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

DSCH-TDD-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-bindingID					CRITICALITY	ignore		EXTENSION 	BindingID				PRESENCE optional	}|
	-- Shall be ignored if bearer establishment with ALCAP.
	{ ID id-transportlayeraddress		CRITICALITY	ignore		EXTENSION 	TransportLayerAddress	PRESENCE optional	}|
	-- Shall be ignored if bearer establishment with ALCAP.
	{ ID id-TnlQos						CRITICALITY ignore		EXTENSION TnlQos					PRESENCE optional},
	...
}

DsField ::= BIT STRING (SIZE (8))

DTX-Cycle-2ms-Items ::= SEQUENCE {
	uE-DTX-Cycle1-2ms				UE-DTX-Cycle1-2ms,
	uE-DTX-Cycle2-2ms				UE-DTX-Cycle2-2ms,
	mAC-DTX-Cycle-2ms				MAC-DTX-Cycle-2ms,
	iE-Extensions								ProtocolExtensionContainer { { DTX-Cycle-2ms-Items-ExtIEs} }			OPTIONAL,
	...
}

DTX-Cycle-2ms-Items-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DTX-Cycle-2ms-to-Modify-Items ::= SEQUENCE {
	uE-DTX-Cycle1-2ms				UE-DTX-Cycle1-2ms,
	uE-DTX-Cycle2-2ms				UE-DTX-Cycle2-2ms,
	mAC-DTX-Cycle-2ms				MAC-DTX-Cycle-2ms,
	iE-Extensions								ProtocolExtensionContainer { { DTX-Cycle-2ms-to-Modify-Items-ExtIEs} }			OPTIONAL,
	...
}

DTX-Cycle-2ms-to-Modify-Items-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DTX-Cycle-10ms-Items ::= SEQUENCE {
	uE-DTX-Cycle1-10ms				UE-DTX-Cycle1-10ms,
	uE-DTX-Cycle2-10ms				UE-DTX-Cycle2-10ms,
	mAC-DTX-Cycle-10ms				MAC-DTX-Cycle-10ms,
	iE-Extensions								ProtocolExtensionContainer { { DTX-Cycle-10ms-Items-ExtIEs} }			OPTIONAL,
	...
}

DTX-Cycle-10ms-Items-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DTX-Cycle-10ms-to-Modify-Items ::= SEQUENCE {
	uE-DTX-Cycle1-10ms				UE-DTX-Cycle1-10ms,
	uE-DTX-Cycle2-10ms				UE-DTX-Cycle2-10ms,
	mAC-DTX-Cycle-10ms				MAC-DTX-Cycle-10ms,
	iE-Extensions								ProtocolExtensionContainer { { DTX-Cycle-10ms-to-Modify-Items-ExtIEs} }			OPTIONAL,
	...
}

DTX-Cycle-10ms-to-Modify-Items-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

DTX-Information ::= SEQUENCE {
	e-DCH-TTI-Length					E-DCH-TTI-Length, 
	inactivity-Threshold-for-UE-DTX-Cycle2					Inactivity-Threshold-for-UE-DTX-Cycle2,
	uE-DTX-Long-Preamble 				UE-DTX-Long-Preamble,
	mAC-Inactivity-Threshold				MAC-Inactivity-Threshold	,
	cQI-DTX-Timer 				CQI-DTX-Timer,
	uE-DPCCH-burst1				UE-DPCCH-burst1,
	uE-DPCCH-burst2				UE-DPCCH-burst2, 
	iE-Extensions				ProtocolExtensionContainer { {DTX-Information-ExtIEs} } OPTIONAL,
	...
}

DTX-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


DTX-Information-to-Modify ::= CHOICE {
	modify			DTX-Information-to-Modify-Items,
	deactivate		NULL,
	...
}

DTX-Information-to-Modify-Items ::= SEQUENCE {
	e-DCH-TTI-Length-to-Modify		E-DCH-TTI-Length-to-Modify			OPTIONAL, 
	inactivity-Threshold-for-UE-DTX-Cycle2					Inactivity-Threshold-for-UE-DTX-Cycle2					OPTIONAL,
	uE-DTX-Long-Preamble 			UE-DTX-Long-Preamble				OPTIONAL,
	mAC-Inactivity-Threshold			MAC-Inactivity-Threshold				OPTIONAL,
	cQI-DTX-Timer 					CQI-DTX-Timer						OPTIONAL,
	uE-DPCCH-burst1					UE-DPCCH-burst1					OPTIONAL,
	uE-DPCCH-burst2					UE-DPCCH-burst2						OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { {DTX-Information-to-Modify-Items-ExtIEs} } OPTIONAL,
	...
}

DTX-Information-to-Modify-Items-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Dual-Band-Capability ::= ENUMERATED {
	dual-Band-Capable,
	dual-Band-non-Capable
}

Dual-Band-Capability-Info::= SEQUENCE {
	dual-Band-Capability										Dual-Band-Capability, 
-- Above for HS-DSCH only
	possible-Secondary-Serving-Cell-List						Possible-Secondary-Serving-Cell-List		OPTIONAL,
	iE-Extensions				ProtocolExtensionContainer { { Dual-Band-Capability-Info-ExtIEs } }		OPTIONAL,
	...
}

Dual-Band-Capability-Info-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-Dual-Band-EDCH-Capability		CRITICALITY ignore		EXTENSION Dual-Band-Capability	PRESENCE optional},
	...
}


DwPCH-Power ::= INTEGER (-150..400,...)
-- DwPCH-power = power * 10
-- If power <= -15 DwPCH shall be set to -150
-- If power >= 40 DwPCH shall be set to 400
-- Unit dBm, Range -15dBm .. +40 dBm, Step +0.1dB

Improved-Synchronized-Indicator ::= ENUMERATED {true}


-- ==========================================
--	E
-- ==========================================

E-AGCH-Table-Choice ::= ENUMERATED{table16B, table16B-1, ...}

E-AGCH-FDD-Code-Information ::= CHOICE {
	replace					E-AGCH-FDD-Code-List,
	remove					NULL,
	...
}

E-AGCH-FDD-Code-List ::= SEQUENCE (SIZE (1..maxNrOfE-AGCHs)) OF FDD-DL-ChannelisationCodeNumber

E-AI-Capability ::= ENUMERATED {
	e-AI-capable,
	e-AI-non-capable
}

E-AI-Indicator ::= BOOLEAN


E-DCH-Capability ::= ENUMERATED {
	e-DCH-capable,
	e-DCH-non-capable
}

E-DCHCapacityConsumptionLaw ::= SEQUENCE {
		e-DCH-SF-allocation 	E-DCH-SF-allocation, 
		dl-Cost-1				INTEGER (0..65535)														OPTIONAL,
		dl-Cost-2				INTEGER (0..65535)														OPTIONAL,
		iE-Extensions			ProtocolExtensionContainer { { E-DCHCapacityConsumptionLaw-ExtIEs } }		OPTIONAL,
	...
}

E-DCHCapacityConsumptionLaw-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-Decoupling-Indication ::= ENUMERATED {
		serving-E-DCH-cell-only,
		serving-HS-DSCH-cell-only,
		...
}

E-DCH-TDD-CapacityConsumptionLaw ::= SEQUENCE {
		ul-Cost				INTEGER (0..65535),
		dl-Cost				INTEGER (0..65535)														OPTIONAL,
		iE-Extensions			ProtocolExtensionContainer { { E-DCH-TDD-CapacityConsumptionLaw-ExtIEs } }		OPTIONAL,
	...
}

E-DCH-TDD-CapacityConsumptionLaw-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-SF-allocation ::= SEQUENCE ( SIZE(1..maxNrOfCombEDPDCH) ) OF
	SEQUENCE {
		ul-Cost-1		INTEGER (0..65535),
		ul-Cost-2		INTEGER (0..65535),
		iE-Extensions		ProtocolExtensionContainer { { E-DCH-SF-allocation-ExtIEs } }		OPTIONAL,
	...
}

E-DCH-SF-allocation-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-TTI2ms-Capability ::= BOOLEAN 
-- True = TTI 10ms and 2ms supported for E-DCH False = only TTI 10ms supported for E-DCH

E-DCH-SF-Capability ::= ENUMERATED {
	sf64, 
	sf32, 
	sf16, 
	sf8, 
	sf4, 
	sf4x2, 
	sf2x2, 
	sf4x2-and-sf2x2,
	...
}

E-DCH-HARQ-Combining-Capability ::= ENUMERATED {
	iR-Combining-capable,
	chase-Combining-capable,
	iR-and-Chase-Combining-capable
}

E-DCH-DDI-Value ::= INTEGER (0..62)

E-DCH-FDD-DL-Control-Channel-Information ::= SEQUENCE {
	e-AGCH-And-E-RGCH-E-HICH-FDD-Scrambling-Code	DL-ScramblingCode															OPTIONAL,
	e-AGCH-Channelisation-Code						FDD-DL-ChannelisationCodeNumber												OPTIONAL,
	primary-e-RNTI									E-RNTI																		OPTIONAL,
	secondary-e-RNTI								E-RNTI																		OPTIONAL,
	e-RGCH-E-HICH-Channelisation-Code				FDD-DL-ChannelisationCodeNumber												OPTIONAL,
	e-RGCH-Signature-Sequence						E-RGCH-Signature-Sequence													OPTIONAL,
	e-HICH-Signature-Sequence						E-HICH-Signature-Sequence													OPTIONAL,
	serving-Grant-Value								E-Serving-Grant-Value														OPTIONAL,
	primary-Secondary-Grant-Selector				E-Primary-Secondary-Grant-Selector											OPTIONAL,
	e-RGCH-Release-Indicator						E-RGCH-Release-Indicator														OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-FDD-DL-Control-Channel-Information-ExtIEs} }		OPTIONAL,
	...
}

E-DCH-FDD-DL-Control-Channel-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Default-Serving-Grant-in-DTX-Cycle2		CRITICALITY ignore	EXTENSION E-Serving-Grant-Value								PRESENCE optional}|
	{ ID id-UL-MIMO-DL-Control-Channel-Information	CRITICALITY ignore	EXTENSION UL-MIMO-DL-Control-Channel-Information		PRESENCE optional},
	...
}

E-DCH-FDD-Information ::= SEQUENCE {
	e-DCH-MACdFlows-Information						E-DCH-MACdFlows-Information,
	hARQ-Process-Allocation-Scheduled-2ms-EDCH		HARQ-Process-Allocation-2ms-EDCH											OPTIONAL,
	e-DCH-Maximum-Bitrate							E-DCH-Maximum-Bitrate														OPTIONAL,
	e-DCH-Processing-Overload-Level					E-DCH-Processing-Overload-Level												OPTIONAL,
	e-DCH-Reference-Power-Offset					E-DCH-Reference-Power-Offset												OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-FDD-Information-ExtIEs} }								OPTIONAL,
	...
}

E-DCH-FDD-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-PowerOffset-for-SchedulingInfo	CRITICALITY ignore	EXTENSION E-DCH-PowerOffset-for-SchedulingInfo			PRESENCE optional}|
	{ ID id-SixteenQAM-UL-Operation-Indicator		CRITICALITY reject	EXTENSION SixteenQAM-UL-Operation-Indicator				PRESENCE optional}|
	{ ID id-E-AGCH-Table-Choice						CRITICALITY ignore	EXTENSION E-AGCH-Table-Choice								PRESENCE conditional}|
	-- The IE shall be present if the SixteenQAM UL Operation Indicator IE is set to “Activate”--
	{ ID id-SixtyfourQAM-UL-Operation-Indicator		CRITICALITY reject	EXTENSION SixtyfourQAM-UL-Operation-Indicator			PRESENCE optional}|
	{ ID id-UL-MIMO-Information						CRITICALITY reject	EXTENSION UL-MIMO-Information								PRESENCE optional}|
	{ ID id-UPH-Filtering-Measurement-Forwarding-Request	CRITICALITY reject	EXTENSION UPH-Filtering-Measurement-Forwarding-Request	PRESENCE optional},
	...
}

UPH-Filtering-Measurement-Forwarding-Request ::= ENUMERATED {
	requested,
	notRequested
}

E-DCH-FDD-Information-Response ::= SEQUENCE {
	e-DCH-MACdFlow-Specific-InformationResp			E-DCH-MACdFlow-Specific-InformationResp										OPTIONAL,
	hARQ-Process-Allocation-Scheduled-2ms-EDCH		HARQ-Process-Allocation-2ms-EDCH																	OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-FDD-Information-Response-ExtIEs } }					OPTIONAL,
	...
}

E-DCH-FDD-Information-Response-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Fast-TTI-switching-Mode-Supported	CRITICALITY ignore	EXTENSION Fast-TTI-switching-Mode-Supported	PRESENCE optional},
	...
}

E-DCH-FDD-Information-to-Modify ::= SEQUENCE {
	e-DCH-MACdFlow-Specific-Info-to-Modify			E-DCH-MACdFlow-Specific-InfoList-to-Modify															OPTIONAL,
	hARQ-Process-Allocation-Scheduled-2ms-EDCH		HARQ-Process-Allocation-2ms-EDCH																	OPTIONAL,
	e-DCH-Maximum-Bitrate							E-DCH-Maximum-Bitrate																				OPTIONAL,
	e-DCH-Processing-Overload-Level					E-DCH-Processing-Overload-Level																		OPTIONAL,
	e-DCH-Reference-Power-Offset					E-DCH-Reference-Power-Offset												OPTIONAL,
	mACeReset-Indicator								MACeReset-Indicator															OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-FDD-Information-to-Modify-ExtIEs} }					OPTIONAL,
	...
}

E-DCH-FDD-Information-to-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-PowerOffset-for-SchedulingInfo		CRITICALITY ignore	EXTENSION E-DCH-PowerOffset-for-SchedulingInfo	PRESENCE optional}|
	{ ID id-SixteenQAM-UL-Operation-Indicator			CRITICALITY reject	EXTENSION SixteenQAM-UL-Operation-Indicator		PRESENCE optional}|
	{ ID id-E-DCH-MACdPDUSizeFormat 					CRITICALITY reject	EXTENSION E-DCH-MACdPDUSizeFormat						PRESENCE optional}|
	{ ID id-E-DCH-DL-Control-Channel-Grant-Information	CRITICALITY ignore	EXTENSION E-DCH-DL-Control-Channel-Grant-Information	PRESENCE optional}|
	{ ID id-E-AGCH-Table-Choice							CRITICALITY ignore	EXTENSION E-AGCH-Table-Choice							PRESENCE conditional}|
	-- The IE shall be present if the SixteenQAM UL Operation Indicator IE is set to “Activate”--
	{ ID id-SixtyfourQAM-UL-Operation-Indicator			CRITICALITY reject	EXTENSION SixtyfourQAM-UL-Operation-Indicator		PRESENCE optional}|
	{ ID id-UL-MIMO-Reconfiguration						CRITICALITY reject	EXTENSION UL-MIMO-Reconfiguration						PRESENCE optional}|
	{ ID id-Fast-TTI-switching-Mode-synchronized		CRITICALITY reject	EXTENSION Fast-TTI-switching-Mode-synchronized	PRESENCE optional}|
	{ ID id-Fast-TTI-switching-Mode-unsynchronized		CRITICALITY reject	EXTENSION Fast-TTI-switching-Mode-unsynchronized	PRESENCE optional},
	...
}

E-DCH-FDD-Update-Information ::= SEQUENCE {
	e-DCH-MACdFlow-Specific-UpdateInformation		E-DCH-MACdFlow-Specific-UpdateInformation									OPTIONAL,
	hARQ-Process-Allocation-Scheduled-2ms-EDCH		HARQ-Process-Allocation-2ms-EDCH																	OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-FDD-Update-Information-ExtIEs } }					OPTIONAL,
	...
}

E-DCH-FDD-Update-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-DL-Control-Channel-Change-Information			CRITICALITY ignore	EXTENSION E-DCH-DL-Control-Channel-Change-Information			PRESENCE optional}|
	{ ID id-TTI-Update-Indicator								CRITICALITY ignore	EXTENSION TTI-Update-Indicator		PRESENCE optional},
	...
}

TTI-Update-Indicator ::= CHOICE {
	tTI-Update-CFN			CFN,
	tTI-Update-Ind			TTI-Update-Ind
}

TTI-Update-Ind ::= NULL

E-DCH-MACdFlow-Specific-UpdateInformation ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF E-DCH-MACdFlow-Specific-UpdateInformation-Item

E-DCH-MACdFlow-Specific-UpdateInformation-Item ::= SEQUENCE {
	e-DCH-MACdFlow-ID								E-DCH-MACdFlow-ID,
	hARQ-Process-Allocation-NonSched-2ms-EDCH		HARQ-Process-Allocation-2ms-EDCH																	OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-MACdFlow-Specific-UpdateInformation-Item-ExtIEs} }	OPTIONAL,
	...
}

E-DCH-MACdFlow-Specific-UpdateInformation-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-DL-Control-Channel-Change-Information ::= SEQUENCE (SIZE (1..maxNrOfEDCHRLs)) OF E-DCH-DL-Control-Channel-Change-Information-Item

E-DCH-DL-Control-Channel-Change-Information-Item ::= SEQUENCE {
	e-DCH-RL-ID								RL-ID,
	iE-Extensions							ProtocolExtensionContainer { { E-DCH-DL-Control-Channel-Change-Information-Item-ExtIEs} }	OPTIONAL,
	...
}

E-DCH-DL-Control-Channel-Change-Information-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-DL-Control-Channel-Grant-Information ::= SEQUENCE (SIZE (1..maxNrOfEDCHRLs)) OF E-DCH-DL-Control-Channel-Grant-Information-Item

E-DCH-DL-Control-Channel-Grant-Information-Item ::= SEQUENCE {
	e-DCH-RL-ID								RL-ID,
	iE-Extensions							ProtocolExtensionContainer { { E-DCH-DL-Control-Channel-Grant-Information-Item-ExtIEs} }	OPTIONAL,
	...
}

E-DCH-DL-Control-Channel-Grant-Information-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-Grant-Type-Information ::= CHOICE {
	e-DCH-Non-Scheduled-Transmission-Grant		E-DCH-Non-Scheduled-Transmission-Grant-Items,
	e-DCH-Scheduled-Transmission-Grant			NULL,
	...
}

E-DCH-LogicalChannelInformation ::= SEQUENCE (SIZE (1..maxNoOfLogicalChannels)) OF E-DCH-LogicalChannelInformationItem

E-DCH-LogicalChannelInformationItem ::= SEQUENCE {
	logicalChannelId				LogicalChannelID,
	schedulingPriorityIndicator		SchedulingPriorityIndicator,
	schedulingInformation			SchedulingInformation,
	mACesGuaranteedBitRate			MACesGuaranteedBitRate		OPTIONAL,
	e-DCH-DDI-Value					E-DCH-DDI-Value,
	mACd-PDU-Size-List				E-DCH-MACdPDU-SizeList,
	iE-Extensions					ProtocolExtensionContainer { { E-DCH-LogicalChannelInformationItem-ExtIEs } }			OPTIONAL,
	...
}

E-DCH-LogicalChannelInformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MaximumMACdPDU-SizeExtended 	CRITICALITY reject		EXTENSION	MAC-PDU-SizeExtended 		PRESENCE optional}|
	{ ID id-MACes-Maximum-Bitrate-LCR		CRITICALITY ignore		EXTENSION	MACes-Maximum-Bitrate-LCR		PRESENCE optional}| --1.28Mcps TDD only
	{ ID id-UE-AggregateMaximumBitRate-Enforcement-Indicator	CRITICALITY ignore	EXTENSION	UE-AggregateMaximumBitRate-Enforcement-Indicator	PRESENCE optional}, 
	...
}

E-DCH-Maximum-Bitrate ::= INTEGER (0..5742,...,5743..11498|11499..34507)

E-DCH-PowerOffset-for-SchedulingInfo ::= INTEGER (0.. maxNrOfEDCH-HARQ-PO-QUANTSTEPs)

E-DCH-Processing-Overload-Level ::= INTEGER (0..10,...)

E-DCH-Reference-Power-Offset ::= INTEGER (0.. maxNrOfEDCH-HARQ-PO-QUANTSTEPs)

E-DCH-MACdPDU-SizeList ::= SEQUENCE (SIZE (1.. maxNrOfMACdPDUSize)) OF E-DCH-MACdPDU-SizeListItem

E-DCH-MACdPDU-SizeListItem ::= SEQUENCE {
	mACdPDU-Size					MACdPDU-Size,
	iE-Extensions					ProtocolExtensionContainer { { E-DCH-MACdPDU-SizeListItem-ExtIEs } }			OPTIONAL,
	...
}

E-DCH-MACdPDU-SizeListItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-MACdPDU-SizeCapability ::= ENUMERATED {
	fixedSizeCapable,
	flexibleSizeCapable
}

E-DCH-MACdPDUSizeFormat ::= ENUMERATED {
	fixedMACdPDU-Size,
	flexibleMACdPDU-Size
}


E-DCH-LogicalChannelToModify ::= SEQUENCE (SIZE (1..maxNoOfLogicalChannels)) OF E-DCH-LogicalChannelToModifyItem

E-DCH-LogicalChannelToModifyItem ::= SEQUENCE {
	logicalChannelId				LogicalChannelID,
	schedulingPriorityIndicator		SchedulingPriorityIndicator		OPTIONAL,
	schedulingInformation			SchedulingInformation		OPTIONAL,
	mACesGuaranteedBitRate			MACesGuaranteedBitRate		OPTIONAL,
	e-DCH-DDI-Value					E-DCH-DDI-Value					OPTIONAL,
	mACd-PDU-Size-List				E-DCH-MACdPDU-SizeToModifyList, 
	iE-Extensions					ProtocolExtensionContainer { { E-DCH-LogicalChannelToModifyItem-ExtIEs } }			OPTIONAL,
	...
}

E-DCH-LogicalChannelToModifyItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MaximumMACdPDU-SizeExtended 	CRITICALITY reject		EXTENSION	MAC-PDU-SizeExtended 	PRESENCE optional}|
	{ ID id-MACes-Maximum-Bitrate-LCR		CRITICALITY ignore		EXTENSION	MACes-Maximum-Bitrate-LCR		PRESENCE optional}, --1.28Mcps TDD only
	...
}

E-DCH-MACdPDU-SizeToModifyList ::= SEQUENCE (SIZE (0.. maxNrOfMACdPDUSize)) OF E-DCH-MACdPDU-SizeListItem



E-DCH-LogicalChannelToDelete ::= SEQUENCE (SIZE (1..maxNoOfLogicalChannels)) OF E-DCH-LogicalChannelToDeleteItem

E-DCH-LogicalChannelToDeleteItem ::= SEQUENCE {
	logicalChannelId				LogicalChannelID,
	iE-Extensions					ProtocolExtensionContainer { { E-DCH-LogicalChannelToDeleteItem-ExtIEs } }			OPTIONAL,
	...
}

E-DCH-LogicalChannelToDeleteItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

LogicalChannelID ::= INTEGER (1..15)


E-DCH-HARQ-PO-FDD ::= INTEGER (0.. maxNrOfEDCH-HARQ-PO-QUANTSTEPs)

E-DCH-MACdFlow-ID ::= INTEGER (0..maxNrOfEDCHMACdFlows-1)

E-DCH-MACdFlows-Information ::= SEQUENCE {
	e-DCH-MACdFlow-Specific-Info					E-DCH-MACdFlow-Specific-InfoList,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-MACdFlows-Information-ExtIEs} }						OPTIONAL,
	...
}

E-DCH-MACdFlows-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-MACdFlow-Multiplexing-List ::= BIT STRING ( SIZE(maxNrOfEDCHMACdFlows) )

E-DCH-MACdFlow-Specific-InfoList ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF E-DCH-MACdFlow-Specific-InfoItem

E-DCH-MACdFlow-Specific-InfoItem ::= SEQUENCE {
	e-DCH-MACdFlow-ID								E-DCH-MACdFlow-ID,
	allocationRetentionPriority						AllocationRetentionPriority,
	tnlQos											TnlQos																		OPTIONAL,
	payloadCRC-PresenceIndicator					PayloadCRC-PresenceIndicator,
	maximum-Number-of-Retransmissions-For-E-DCH		Maximum-Number-of-Retransmissions-For-E-DCH,
	eDCH-HARQ-PO-FDD								E-DCH-HARQ-PO-FDD,
	eDCH-MACdFlow-Multiplexing-List					E-DCH-MACdFlow-Multiplexing-List																	OPTIONAL,
	eDCH-Grant-Type-Information						E-DCH-Grant-Type-Information,
	bundlingModeIndicator							BundlingModeIndicator														OPTIONAL,
	eDCHLogicalChannelInformation					E-DCH-LogicalChannelInformation,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-MACdFlow-Specific-InfoItem-ExtIEs} }				OPTIONAL,
	...
}

E-DCH-MACdFlow-Specific-InfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TransportBearerNotRequestedIndicator	CRITICALITY ignore	EXTENSION TransportBearerNotRequestedIndicator		PRESENCE optional	},
	...
}

E-DCH-MACdFlow-Specific-InformationResp ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF E-DCH-MACdFlow-Specific-InformationResp-Item

E-DCH-MACdFlow-Specific-InformationResp-Item ::= SEQUENCE {
	e-DCH-MACdFlow-ID								E-DCH-MACdFlow-ID,
	bindingID										BindingID																	OPTIONAL,
	transportLayerAddress							TransportLayerAddress														OPTIONAL,
	hARQ-Process-Allocation-NonSched-2ms-EDCH		HARQ-Process-Allocation-2ms-EDCH																	OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-MACdFlow-Specific-InformationResp-Item-ExtIEs} }	OPTIONAL,
	...
}

E-DCH-MACdFlow-Specific-InformationResp-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TransportBearerNotSetupIndicator	CRITICALITY ignore	EXTENSION TransportBearerNotSetupIndicator		PRESENCE optional	}, -- FDD only
	...
}

E-DCH-MACdFlow-Specific-InfoList-to-Modify ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF E-DCH-MACdFlow-Specific-InfoItem-to-Modify

E-DCH-MACdFlow-Specific-InfoItem-to-Modify ::= SEQUENCE {
	e-DCH-MACdFlow-ID								E-DCH-MACdFlow-ID,
	allocationRetentionPriority						AllocationRetentionPriority													OPTIONAL,
	transportBearerRequestIndicator					TransportBearerRequestIndicator,
	tnlQos											TnlQos																		OPTIONAL,
	maximum-Number-of-Retransmissions-For-E-DCH		Maximum-Number-of-Retransmissions-For-E-DCH									OPTIONAL,
	eDCH-HARQ-PO-FDD								E-DCH-HARQ-PO-FDD																					OPTIONAL,
	eDCH-MACdFlow-Multiplexing-List					E-DCH-MACdFlow-Multiplexing-List																	OPTIONAL,
	eDCH-Grant-Type-Information						E-DCH-Grant-Type-Information																		OPTIONAL,
	bundlingModeIndicator							BundlingModeIndicator																				OPTIONAL,
	eDCH-LogicalChannelToAdd						E-DCH-LogicalChannelInformation																		OPTIONAL,
	eDCH-LogicalChannelToModify						E-DCH-LogicalChannelToModify																		OPTIONAL,
	eDCH-LogicalChannelToDelete						E-DCH-LogicalChannelToDelete																		OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-MACdFlow-Specific-InfoItem-to-Modify-ExtIEs} }		OPTIONAL,
	...
}

E-DCH-MACdFlow-Specific-InfoItem-to-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-MACdFlows-to-Delete ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF E-DCH-MACdFlow-to-Delete-Item

E-DCH-MACdFlow-to-Delete-Item ::= SEQUENCE {
	e-DCH-MACdFlow-ID								E-DCH-MACdFlow-ID,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-MACdFlow-to-Delete-Item-ExtIEs} }					OPTIONAL,
	...
}

E-DCH-MACdFlow-to-Delete-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-Non-Scheduled-Transmission-Grant-Items ::= SEQUENCE {
	-- The following IE shall be ignored if id-Ext-Max-Bits-MACe-PDU-non-scheduled is present in E-DCH-Non-Scheduled-Transmission-Grant-Items-ExtIEs
	maxBits-MACe-PDU-non-scheduled				Max-Bits-MACe-PDU-non-scheduled,
	hARQ-Process-Allocation-NonSched-2ms		HARQ-Process-Allocation-2ms-EDCH												OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { E-DCH-Non-Scheduled-Transmission-Grant-Items-ExtIEs} }		OPTIONAL,
	...
}

E-DCH-Non-Scheduled-Transmission-Grant-Items-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	-- The following IE shall be present if the maximum number of bits to be signalled exceeds maxNrOfBits-MACe-PDU-non-scheduled
	{ ID id-Ext-Max-Bits-MACe-PDU-non-scheduled		CRITICALITY reject		EXTENSION	Ext-Max-Bits-MACe-PDU-non-scheduled		PRESENCE optional},
	...
}

E-DCH-Non-serving-Relative-Grant-Down-Commands ::= INTEGER (0..100,...)

E-DCHProvidedBitRateValue ::= INTEGER(0..16777215,...,16777216..256000000)
-- Unit bit/s, Range 0..2^24-1..2^24..256,000,000, Step 1 bit

Maximum-Target-ReceivedTotalWideBandPower ::= INTEGER (0..621)
-- mapping as for RTWP measurement value, as specified in TS 25.133 [22]

Target-NonServing-EDCH-To-Total-EDCH-Power-Ratio ::= INTEGER (0..100)
-- Unit %, Range 0..100%, Step 1%

E-DCH-RL-Indication ::= ENUMERATED {
	e-DCH,
	non-e-DCH
}


E-DCH-Serving-Cell-Change-Info-Response ::= SEQUENCE {
	e-DCH-serving-cell-choice		E-DCH-serving-cell-choice,
	iE-Extensions					ProtocolExtensionContainer { { E-DCH-serving-cell-informationResponse-ExtIEs} } OPTIONAL,
	...
}

E-DCH-serving-cell-informationResponse-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-serving-cell-choice ::= CHOICE {
	e-DCH-serving-cell-change-successful		E-DCH-serving-cell-change-successful,
	e-DCH-serving-cell-change-unsuccessful		E-DCH-serving-cell-change-unsuccessful,
	...
}

E-DCH-serving-cell-change-successful ::= SEQUENCE {
	e-DCH-RL-InformationList-Rsp			E-DCH-RL-InformationList-Rsp,
	iE-Extensions						ProtocolExtensionContainer { { E-DCH-serving-cell-change-successful-ExtIEs} } OPTIONAL,
	...
}

E-DCH-RL-InformationList-Rsp ::= SEQUENCE (SIZE (0..maxNrOfRLs)) OF E-DCH-RL-InformationList-Rsp-Item 

E-DCH-RL-InformationList-Rsp-Item ::= SEQUENCE {
	rl-ID								RL-ID,
	e-DCH-FDD-DL-Control-Channel-Info	E-DCH-FDD-DL-Control-Channel-Information,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-RL-InformationList-Rsp-Item-ExtIEs} }	OPTIONAL,
	...
}

E-DCH-serving-cell-change-successful-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-RL-InformationList-Rsp-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-serving-cell-change-unsuccessful ::= SEQUENCE {
	cause							Cause,
	iE-Extensions					ProtocolExtensionContainer { { E-DCH-serving-cell-change-unsuccessful-ExtIEs} } OPTIONAL,
	...
}

E-DCH-serving-cell-change-unsuccessful-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- The maximum repetitions should be limited to 1 so that this information is reported only once for a cell.
EDCH-RACH-Report-Value ::= SEQUENCE (SIZE(1.. maxNrOfCommonEDCH)) OF
	SEQUENCE {
		granted-EDCH-RACH-resources		Granted-EDCH-RACH-Resources-Value,
		denied-EDCH-RACH-resources		Denied-EDCH-RACH-Resources-Value,
		iE-Extensions		ProtocolExtensionContainer { { EDCH-RACH-Report-Value-ExtIEs } }	OPTIONAL,
		...
}

EDCH-RACH-Report-Value-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Two-ms-Grant-E-DCH-RACH-Resources		CRITICALITY ignore	EXTENSION Two-ms-Grant-E-DCH-RACH-Resources				PRESENCE optional}|
	{ ID id-Two-ms-Overridden-E-DCH-RACH-Resources	CRITICALITY ignore	EXTENSION Two-ms-Overridden-E-DCH-RACH-Resources		PRESENCE optional}|
	{ ID id-Two-ms-Denied-E-DCH-RACH-Resources		CRITICALITY ignore	EXTENSION Two-ms-Denied-E-DCH-RACH-Resources			PRESENCE optional},
	...
}

E-DCH-TFCI-Table-Index ::= INTEGER (0..1,...,2..7)

E-DCH-TTI-Length ::= CHOICE {
	two-ms		DTX-Cycle-2ms-Items,
	ten-ms		DTX-Cycle-10ms-Items,
	...
}

E-DCH-TTI-Length-to-Modify ::= CHOICE {
	two-ms		DTX-Cycle-2ms-to-Modify-Items,
	ten-ms		DTX-Cycle-10ms-to-Modify-Items,
	...
}


E-DPCCH-PO ::= INTEGER (0..maxNrOfEDPCCH-PO-QUANTSTEPs)

Extended-E-DPCCH-PO ::= INTEGER (9..15)

E-DPDCH-PowerInterpolation ::= BOOLEAN

E-Primary-Secondary-Grant-Selector ::= ENUMERATED {
	primary,
	secondary
}

E-DCH-MACdFlow-ID-LCR ::= INTEGER (0..maxNrOfEDCHMACdFlowsLCR-1)

E-DCH-MACdFlows-to-DeleteLCR ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlowsLCR)) OF E-DCH-MACdFlow-to-Delete-ItemLCR

E-DCH-MACdFlow-to-Delete-ItemLCR ::= SEQUENCE {
	e-DCH-MACdFlow-ID-LCR							E-DCH-MACdFlow-ID-LCR,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-MACdFlow-to-Delete-ItemLCR-ExtIEs} }					OPTIONAL,
	...
}

E-DCH-MACdFlow-to-Delete-ItemLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Enhanced-UE-DRX-InformationLCR  ::= SEQUENCE {
	t321										T321,
	hS-DSCH-DRX-Cycle-FACH						HS-DSCH-DRX-Cycle-FACH,
	hS-DSCH-RX-Burst-FACH						HS-DSCH-RX-Burst-FACH,
	iE-Extensions								ProtocolExtensionContainer { { Enhanced-UE-DRX-InformationLCR-ExtIEs } }		OPTIONAL,
	...
}

Enhanced-UE-DRX-InformationLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-HICH-ID-LCR ::= INTEGER(0..255)
E-HICH-Signature-Sequence ::= INTEGER (0..maxNrofSigSeqRGHI-1)

End-Of-Audit-Sequence-Indicator ::= ENUMERATED {
	end-of-audit-sequence,
	not-end-of-audit-sequence
}

E-Serving-Grant-Value ::= INTEGER (0..38)

E-RGCH-2-IndexStepThreshold ::= INTEGER (0..37)

E-RGCH-3-IndexStepThreshold ::= INTEGER (0..37)

E-RGCH-E-HICH-FDD-Code-Information ::= CHOICE {
	replace					E-RGCH-E-HICH-FDD-Code-List,
	remove					NULL,
	...
}

E-RGCH-E-HICH-FDD-Code-List ::= SEQUENCE (SIZE (1..maxNrOfE-RGCHs-E-HICHs)) OF FDD-DL-ChannelisationCodeNumber

E-RGCH-Release-Indicator ::= ENUMERATED {e-RGCHreleased}

E-RGCH-Signature-Sequence ::= INTEGER (0..maxNrofSigSeqRGHI-1)

E-RNTI ::= INTEGER (0..65535)

E-TFCI ::= INTEGER (0..127)

E-TFCI-BetaEC-Boost ::= INTEGER (0..127,...)


E-TFCI-Boost-Information ::= SEQUENCE {
	e-TFCI-BetaEC-Boost								E-TFCI-BetaEC-Boost,
	uL-Delta-T2TP									UL-Delta-T2TP			OPTIONAL,
	-- This IE shall be present if the E-TFCI BetaEC Boost IE value is not set to 127.
	iE-Extensions									ProtocolExtensionContainer { { E-TFCI-Boost-Information-ExtIEs} }		OPTIONAL,
	...
}

E-TFCI-Boost-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-TFCS-Information ::= SEQUENCE {
	e-DCH-TFCI-Table-Index								E-DCH-TFCI-Table-Index,
	e-DCH-Min-Set-E-TFCI							E-TFCI			OPTIONAL,
	reference-E-TFCI-Information					Reference-E-TFCI-Information,
	iE-Extensions									ProtocolExtensionContainer { {E-TFCS-Information-ExtIEs} }		OPTIONAL,
	...
}

E-TFCS-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-TFCI-Boost-Information		CRITICALITY reject		EXTENSION	E-TFCI-Boost-Information		PRESENCE optional}|
	{ ID id-E-DPDCH-PowerInterpolation	CRITICALITY reject		EXTENSION	E-DPDCH-PowerInterpolation 	PRESENCE optional},
	...
}

E-TTI ::= ENUMERATED {
	e-TTI-2ms,
	e-TTI-10ms
}

E-DCHProvidedBitRate ::= SEQUENCE (SIZE (1..maxNrOfPriorityClasses)) OF E-DCHProvidedBitRate-Item

E-DCHProvidedBitRate-Item ::= SEQUENCE {
	schedulingPriorityIndicator			SchedulingPriorityIndicator,
	e-DCHProvidedBitRateValue			E-DCHProvidedBitRateValue,
	iE-Extensions						ProtocolExtensionContainer { { E-DCHProvidedBitRate-Item-ExtIEs} }		OPTIONAL,
	...
}

E-DCHProvidedBitRate-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCHProvidedBitRateValueInformation-For-CellPortion ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCellLCR)) OF E-DCHProvidedBitRateValueInformation-For-CellPortion-Item

E-DCHProvidedBitRateValueInformation-For-CellPortion-Item ::= SEQUENCE{
	cellPortionLCRID					CellPortionLCRID,
	e-DCHProvidedBitRateValue		E-DCHProvidedBitRate,
	iE-Extensions					ProtocolExtensionContainer { {E-DCHProvidedBitRateValueInformation-For-CellPortion-Item-ExtIEs} }	OPTIONAL,
	...
}

E-DCHProvidedBitRateValueInformation-For-CellPortion-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-AGCH-PowerOffset ::= INTEGER (0..255,...)
-- PowerOffset = -32 + offset * 0.25
-- Unit dB, Range -32dB .. +31.75dB, Step +0.25dB

E-RGCH-PowerOffset ::= INTEGER (0..255,...)
-- PowerOffset = -32 + offset * 0.25
-- Unit dB, Range -32dB .. +31.75dB, Step +0.25dB



E-HICH-PowerOffset ::= INTEGER (0..255,...) 
-- PowerOffset = -32 + offset * 0.25
-- Unit dB, Range -32dB .. +31.75dB, Step +0.25dB

E-HICH-TimeOffset ::= INTEGER (4..44)

E-HICH-TimeOffsetLCR ::= INTEGER (4..15)


E-DCH-Information ::= SEQUENCE {
	e-PUCH-Information 							E-PUCH-Information,
	e-TFCS-Information-TDD 						E-TFCS-Information-TDD,
	e-DCH-MACdFlows-Information-TDD				E-DCH-MACdFlows-Information-TDD,
	e-DCH-Non-Scheduled-Grant-Info 				E-DCH-Non-Scheduled-Grant-Info	OPTIONAL,
	e-DCH-TDD-Information						E-DCH-TDD-Information,
	iE-Extensions								ProtocolExtensionContainer { { E-DCH-Information-ExtIEs} }		OPTIONAL,
	...
}

E-DCH-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-PUCH-Information  ::= SEQUENCE {
	minCR										CodeRate,
	maxCR										CodeRate,
	harqInfo									HARQ-Info-for-E-DCH,
	n-E-UCCH									N-E-UCCH,
	iE-Extensions								ProtocolExtensionContainer { { E-PUCH-Information-ExtIEs } }		OPTIONAL,
	...
}

E-PUCH-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-TFCS-Information-TDD  ::= SEQUENCE {
	e-DCH-QPSK-RefBetaInfo 						E-DCH-QPSK-RefBetaInfo,
	e-DCH-sixteenQAM-RefBetaInfo				E-DCH-sixteenQAM-RefBetaInfo,
	iE-Extensions								ProtocolExtensionContainer { { E-TFCS-Information-TDD-ExtIEs } }		OPTIONAL,
	...
}

E-TFCS-Information-TDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-QPSK-RefBetaInfo ::= SEQUENCE (SIZE (1..maxNrOfRefBetas)) OF E-DCH-RefBeta-Item

E-DCH-sixteenQAM-RefBetaInfo ::= SEQUENCE (SIZE (1..maxNrOfRefBetas)) OF E-DCH-RefBeta-Item

E-DCH-RefBeta-Item  ::= SEQUENCE {
	refCodeRate				CodeRate-short,
	refBeta					RefBeta
}

E-DCH-MACdFlows-Information-TDD  ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF E-DCH-MACdFlow-InfoTDDItem

E-DCH-MACdFlow-InfoTDDItem ::= SEQUENCE {
	e-DCH-MACdFlow-ID								E-DCH-MACdFlow-ID,
	allocationRetentionPriority						AllocationRetentionPriority,
	tnlQos											TnlQos						OPTIONAL,
	bindingID										BindingID					OPTIONAL,
	transportLayerAddress							TransportLayerAddress		OPTIONAL,
	payloadCRC-PresenceIndicator					PayloadCRC-PresenceIndicator,
	maximum-Number-of-Retransmissions-For-E-DCH		Maximum-Number-of-Retransmissions-For-E-DCH,
	eDCH-HARQ-PO-TDD								E-DCH-HARQ-PO-TDD,
	eDCH-MACdFlow-Multiplexing-List					E-DCH-MACdFlow-Multiplexing-List							OPTIONAL,
	eDCH-Grant-TypeTDD								E-DCH-Grant-TypeTDD,
	eDCHLogicalChannelInformation					E-DCH-LogicalChannelInformation,
	eDCH-MACdFlow-Retransmission-Timer				E-DCH-MACdFlow-Retransmission-Timer		OPTIONAL,
	-- Mandatory for LCR TDD,Not applicable for 3.84Mcps TDD and 7.68Mcps TDD
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-MACdFlow-InfoTDDItem-ExtIEs} }				OPTIONAL,
	...
}

E-DCH-MACdFlow-InfoTDDItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}
E-DCH-MACdFlow-Retransmission-Timer ::= ENUMERATED {
	ms10, ms15, ms20, ms25, ms30, ms35, ms40, ms45, ms50, ms55, ms60, ms65,
	ms70, ms75, ms80, ms85, ms90, ms95, ms100, ms110, ms120, ms140, ms160,
	ms200, ms240, ms280, ms320, ms400, ms480, ms560,...
}


E-DCH-HARQ-PO-TDD ::= INTEGER (0..6)

E-DCH-Grant-TypeTDD ::= ENUMERATED {
	scheduled,
	non-scheduled
}
E-DCH-Non-Scheduled-Grant-Info  ::= SEQUENCE {
	timeslotResource							E-DCH-TimeslotResource,
	powerResource								E-DCH-PowerResource,
	repetitionPeriod							RepetitionPeriod,
	repetitionLength							RepetitionLength,
	tddE-PUCH-Offset							TddE-PUCH-Offset,
	tdd-ChannelisationCode						TDD-ChannelisationCode,
	iE-Extensions								ProtocolExtensionContainer { { E-DCH-Non-Scheduled-Grant-Info-ExtIEs } }		OPTIONAL,
	...
}

E-DCH-Non-Scheduled-Grant-Info-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-TimeslotResource ::= BIT STRING (SIZE (13))

E-DCH-TimeslotResourceLCR ::= BIT STRING (SIZE (5))


E-DCH-PowerResource ::= INTEGER(1..32)

TddE-PUCH-Offset ::= INTEGER(0..255)

E-DCH-TDD-Information  ::= SEQUENCE {
	e-DCH-TDD-Maximum-Bitrate						E-DCH-TDD-Maximum-Bitrate							OPTIONAL,
	e-DCH-Processing-Overload-Level					E-DCH-Processing-Overload-Level						OPTIONAL,
	e-DCH-PowerOffset-for-SchedulingInfo			E-DCH-PowerOffset-for-SchedulingInfo				OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-TDD-Information-ExtIEs } }		OPTIONAL,
	...
}

E-DCH-TDD-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-TDD-Maximum-Bitrate ::= INTEGER (0..9201,...)

E-DCH-Information-Response ::= SEQUENCE {
	e-DCH-TDD-MACdFlow-Specific-InformationResp		E-DCH-TDD-MACdFlow-Specific-InformationResp	OPTIONAL,
	e-AGCH-Specific-Information-ResponseTDD			E-AGCH-Specific-InformationRespListTDD	OPTIONAL, 
	e-RNTI											E-RNTI,
	scheduled-E-HICH-Specific-InformationResp		Scheduled-E-HICH-Specific-Information-ResponseLCRTDD	OPTIONAL,	-- 1.28Mcps TDD only
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-Information-Response-ExtIEs } }		OPTIONAL,
	...
}

E-DCH-Information-Response-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Scheduled-E-HICH-Specific-Information-ResponseLCRTDD ::= SEQUENCE (SIZE (1.. maxNrOfEHICHCodes)) OF Scheduled-E-HICH-Specific-InformationItem-ResponseLCRTDD

Scheduled-E-HICH-Specific-InformationItem-ResponseLCRTDD ::= SEQUENCE {
	eI								EI,
	e-HICH-ID-TDD					E-HICH-ID-TDD,
	iE-Extensions								ProtocolExtensionContainer  {{ Scheduled-E-HICH-Specific-InformationItem-ResponseLCRTDD-ExtIEs}}		OPTIONAL,
	...
}

Scheduled-E-HICH-Specific-InformationItem-ResponseLCRTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-E-HICH-ID-TDD	CRITICALITY ignore EXTENSION Extended-E-HICH-ID-TDD PRESENCE optional},
	-- Applicable to 1.28Mcps TDD only when the E-HICH identity has a value larger than 31.
	...
}

EI ::= INTEGER (0..3)

E-HICH-ID-TDD ::= INTEGER (0..31)

E-HICH-Type ::= ENUMERATED {scheduled,non-scheduled}

E-DCH-TDD-MACdFlow-Specific-InformationResp ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF E-DCH-TDD-MACdFlow-Specific-InformationResp-Item

E-DCH-TDD-MACdFlow-Specific-InformationResp-Item ::= SEQUENCE {
	e-DCH-MacdFlow-Id								E-DCH-MACdFlow-ID,
	bindingID										BindingID					OPTIONAL,
	transportLayerAddress							TransportLayerAddress		OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-TDD-MACdFlow-Specific-InformationRespItem-ExtIEs } }		OPTIONAL,
	...
}

E-DCH-TDD-MACdFlow-Specific-InformationRespItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-AGCH-Specific-InformationRespListTDD ::= SEQUENCE (SIZE (1..maxNrOfEAGCHCodes)) OF E-AGCH-Specific-InformationResp-ItemTDD

E-AGCH-Specific-InformationResp-ItemTDD ::= SEQUENCE {
	e-AGCH-Id										E-AGCH-Id,
	iE-Extensions									ProtocolExtensionContainer { { E-AGCH-Specific-InformationResp-ItemTDD-ExtIEs } }		OPTIONAL,
	...
}

E-AGCH-Specific-InformationResp-ItemTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-AGCH-Id ::= INTEGER (0..31,...,32..255)

E-DCH-Information-Reconfig ::= SEQUENCE {
	e-PUCH-Information 							E-PUCH-Information									OPTIONAL,
	e-TFCS-Information-TDD 						E-TFCS-Information-TDD								OPTIONAL,
	e-DCH-MACdFlows-to-Add						E-DCH-MACdFlows-Information-TDD						OPTIONAL,
	e-DCH-MACdFlows-to-Delete					E-DCH-MACdFlows-to-Delete							OPTIONAL,
	e-DCH-Non-Scheduled-Grant-Info 				E-DCH-Non-Scheduled-Grant-Info						OPTIONAL,
	e-DCH-TDD-Information						E-DCH-TDD-Information								OPTIONAL,
	e-DCH-TDD-Information-to-Modify				E-DCH-TDD-Information-to-Modify						OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { E-DCH-Information-Reconfig-ExtIEs} }	OPTIONAL,
	...
}

E-DCH-Information-Reconfig-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-TDD-Information-to-Modify ::= SEQUENCE {
	e-DCH-TDD-Information-to-Modify-List	E-DCH-TDD-Information-to-Modify-List	OPTIONAL,
	mACeReset-Indicator						MACeReset-Indicator						OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { E-DCH-TDD-Information-to-Modify-ExtIEs } }		OPTIONAL,
	...
}

E-DCH-TDD-Information-to-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-DCH-MACdPDUSizeFormat					CRITICALITY reject	EXTENSION E-DCH-MACdPDUSizeFormat		PRESENCE optional}|
	{ ID id-UE-TS0-CapabilityLCR					CRITICALITY ignore	EXTENSION UE-TS0-CapabilityLCR			PRESENCE optional},
	...
}

E-DCH-TDD-Information-to-Modify-List ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF E-DCH-MACdFlow-ModifyTDDItem

E-DCH-MACdFlow-ModifyTDDItem ::= SEQUENCE {
	e-DCH-MACdFlow-ID								E-DCH-MACdFlow-ID,
	allocationRetentionPriority						AllocationRetentionPriority		OPTIONAL,
	transportBearerRequestIndicator					TransportBearerRequestIndicator,
	bindingID										BindingID					OPTIONAL,
	transportLayerAddress							TransportLayerAddress		OPTIONAL,
	tnlQos											TnlQos						OPTIONAL,
	maximum-Number-of-Retransmissions-For-E-DCH		Maximum-Number-of-Retransmissions-For-E-DCH		OPTIONAL,
	eDCH-HARQ-PO-TDD								E-DCH-HARQ-PO-TDD										OPTIONAL,
	eDCH-MACdFlow-Multiplexing-List					E-DCH-MACdFlow-Multiplexing-List						OPTIONAL,
	eDCH-Grant-TypeTDD								E-DCH-Grant-TypeTDD										OPTIONAL,
	e-DCH-LogicalChannelToAdd						E-DCH-LogicalChannelInformation					OPTIONAL,
	e-DCH-LogicalChannelToModify					E-DCH-LogicalChannelToModify					OPTIONAL,
	e-DCH-LogicalChannelToDelete					E-DCH-LogicalChannelToDelete					OPTIONAL,
	eDCH-MACdFlow-Retransmission-Timer				E-DCH-MACdFlow-Retransmission-Timer				OPTIONAL,
	-- LCR TDD only
	iE-Extensions									ProtocolExtensionContainer { {E-DCH-MACdFlow-ModifyTDDItem-ExtIEs } }	OPTIONAL,
	...
}

E-DCH-MACdFlow-ModifyTDDItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Maximum-Generated-ReceivedTotalWideBandPowerInOtherCells ::= INTEGER (0..621)
-- mapping as for RTWP measurement value, as specified in TS 25.123 [23]

E-DCH-768-Information ::= SEQUENCE {
	e-PUCH-Information 							E-PUCH-Information,
	e-TFCS-Information-TDD 						E-TFCS-Information-TDD,
	e-DCH-MACdFlows-Information-TDD				E-DCH-MACdFlows-Information-TDD,
	e-DCH-Non-Scheduled-Grant-Info768			E-DCH-Non-Scheduled-Grant-Info768	OPTIONAL,
	e-DCH-TDD-Information768					E-DCH-TDD-Information768,
	iE-Extensions								ProtocolExtensionContainer { { E-DCH-768-Information-ExtIEs} }		OPTIONAL,
	...
}

E-DCH-768-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-Non-Scheduled-Grant-Info768  ::= SEQUENCE {
	timeslotResource							E-DCH-TimeslotResource,
	powerResource								E-DCH-PowerResource,
	repetitionPeriod							RepetitionPeriod,
	repetitionLength							RepetitionLength,
	tddE-PUCH-Offset							TddE-PUCH-Offset,
	tdd-ChannelisationCode768					TDD-ChannelisationCode768,
	iE-Extensions								ProtocolExtensionContainer { { E-DCH-Non-Scheduled-Grant-Info768-ExtIEs } }		OPTIONAL,
	...
}

E-DCH-Non-Scheduled-Grant-Info768-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-TDD-Information768  ::= SEQUENCE {
	e-DCH-TDD-Maximum-Bitrate768					E-DCH-TDD-Maximum-Bitrate768						OPTIONAL,
	e-DCH-Processing-Overload-Level					E-DCH-Processing-Overload-Level						OPTIONAL,
	e-DCH-PowerOffset-for-SchedulingInfo			E-DCH-PowerOffset-for-SchedulingInfo				OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { E-DCH-TDD-Information768-ExtIEs } }		OPTIONAL,
	...
}

E-DCH-TDD-Information768-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-TDD-Maximum-Bitrate768 ::= INTEGER (0..17713,...)

E-DCH-768-Information-Reconfig ::= SEQUENCE {
	e-PUCH-Information 							E-PUCH-Information									OPTIONAL,
	e-TFCS-Information-TDD 						E-TFCS-Information-TDD								OPTIONAL,
	e-DCH-MACdFlows-to-Add						E-DCH-MACdFlows-Information-TDD						OPTIONAL,
	e-DCH-MACdFlows-to-Delete					E-DCH-MACdFlows-to-Delete							OPTIONAL,
	e-DCH-Non-Scheduled-Grant-Info768			E-DCH-Non-Scheduled-Grant-Info768						OPTIONAL,
	e-DCH-TDD-Information768					E-DCH-TDD-Information768								OPTIONAL,
	e-DCH-TDD-Information-to-Modify				E-DCH-TDD-Information-to-Modify						OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { E-DCH-768-Information-Reconfig-ExtIEs} }	OPTIONAL,
	...
}

E-DCH-768-Information-Reconfig-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-LCR-Information ::= SEQUENCE {
	e-PUCH-LCR-Information 						E-PUCH-LCR-Information,
	e-TFCS-Information-TDD 						E-TFCS-Information-TDD,
	e-DCH-MACdFlows-Information-TDD				E-DCH-MACdFlows-Information-TDD,
	e-DCH-Non-Scheduled-Grant-LCR-Info			E-DCH-Non-Scheduled-Grant-LCR-Info	OPTIONAL,
	e-DCH-LCRTDD-Information					E-DCH-LCRTDD-Information,
	iE-Extensions								ProtocolExtensionContainer { { E-DCH-LCR-Information-ExtIEs} }		OPTIONAL,
	...
}

E-DCH-LCR-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-PUCH-LCR-Information ::= SEQUENCE {
	minCR										CodeRate,
	maxCR										CodeRate,
	harqInfo									HARQ-Info-for-E-DCH,
	pRXdes-base									PRXdes-base,
	e-PUCH-TPC-StepSize							TDD-TPC-UplinkStepSize-LCR,
	e-AGCH-TPC-StepSize							TDD-TPC-DownlinkStepSize,
	iE-Extensions								ProtocolExtensionContainer { { E-PUCH-LCR-Information-ExtIEs } }		OPTIONAL,
	...
}

E-PUCH-LCR-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-E-PUCH-PowerControlGAP		CRITICALITY ignore		EXTENSION ControlGAP		PRESENCE optional	},
	...
}

E-DCH-Non-Scheduled-Grant-LCR-Info ::= SEQUENCE {
	timeslotResourceLCR							E-DCH-TimeslotResourceLCR,
	powerResource								E-DCH-PowerResource,
	repetitionPeriod							RepetitionPeriod,
	repetitionLength							RepetitionLength,
	subframeNumber								ENUMERATED {v0, v1},
	tddE-PUCH-Offset							TddE-PUCH-Offset,
	tdd-ChannelisationCode						TDD-ChannelisationCode,
	n-E-UCCHLCR									N-E-UCCHLCR,
	e-HICH-LCR-Information						E-HICH-LCR-Information,
	iE-Extensions								ProtocolExtensionContainer { { E-DCH-Non-Scheduled-Grant-LCR-Info-ExtIEs } }		OPTIONAL,
	...
}

E-DCH-Non-Scheduled-Grant-LCR-Info-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-HICH-LCR-Information	 ::= SEQUENCE {
	e-HICH-ID-TDD							E-HICH-ID-TDD,
	signatureSequenceGroupIndex					SignatureSequenceGroupIndex,
	iE-Extensions								ProtocolExtensionContainer { { E-HICH-LCR-Information-ExtIEs} }		OPTIONAL,
	...
}

E-HICH-LCR-Information-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-E-HICH-ID-TDD		CRITICALITY ignore	EXTENSION Extended-E-HICH-ID-TDD	PRESENCE optional},
	-- Applicable to 1.28Mcps TDD only when the E-HICH identity has a value larger than 31.
	...
}

E-DCH-LCRTDD-Information ::= SEQUENCE {
	e-DCH-LCRTDD-PhysicalLayerCategory			E-DCH-LCRTDD-PhysicalLayerCategory					OPTIONAL,
	e-DCH-Processing-Overload-Level				E-DCH-Processing-Overload-Level						OPTIONAL,
	e-DCH-PowerOffset-for-SchedulingInfo		E-DCH-PowerOffset-for-SchedulingInfo				OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { E-DCH-LCRTDD-Information-ExtIEs } }		OPTIONAL,
	...
}

E-DCH-LCRTDD-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-E-DCH-LCRTDD-PhysicalLayerCategory				CRITICALITY reject	EXTENSION Extended-E-DCH-LCRTDD-PhysicalLayerCategory	PRESENCE optional }|
	-- This IE shall be used if the E-DCH Physical Layer Category has a value larger than 5.
	{ ID id-MaximumNumber-Of-Retransmission-for-Scheduling-Info-LCRTDD	CRITICALITY ignore	EXTENSION Maximum-Number-of-Retransmissions-For-E-DCH	PRESENCE optional }|
	{ ID id-E-DCH-RetransmissionTimer-for-SchedulingInfo-LCRTDD		CRITICALITY ignore	EXTENSION E-DCH-MACdFlow-Retransmission-Timer		PRESENCE optional }|
	{ ID id-E-AGCH-UE-Inactivity-Monitor-Threshold					CRITICALITY ignore	EXTENSION E-AGCH-UE-Inactivity-Monitor-Threshold		PRESENCE optional }|
	{ ID id-SNPL-Carrier-Group-Indicator							CRITICALITY ignore	EXTENSION SNPL-Carrier-Group-Indicator			PRESENCE optional }|
	{ ID id-Multi-Carrier-E-DCH-LCRTDD-PhysicalLayerCategory		CRITICALITY reject	EXTENSION Multi-Carrier-E-DCH-LCRTDD-PhysicalLayerCategory	PRESENCE optional }|
	{ ID id-UE-TS0-CapabilityLCR									CRITICALITY ignore	EXTENSION UE-TS0-CapabilityLCR		PRESENCE optional},
	...
}

E-DCH-LCRTDD-PhysicalLayerCategory ::= INTEGER(1..5)

E-DCH-LCR-Information-Reconfig ::= SEQUENCE {
	e-PUCH-LCR-Information 						E-PUCH-LCR-Information								OPTIONAL,
	e-TFCS-Information-TDD 						E-TFCS-Information-TDD								OPTIONAL,
	e-DCH-MACdFlows-to-Add						E-DCH-MACdFlows-Information-TDD						OPTIONAL,
	e-DCH-MACdFlows-to-Delete					E-DCH-MACdFlows-to-Delete							OPTIONAL,
	e-DCH-Non-Scheduled-Grant-LCR-Info			E-DCH-Non-Scheduled-Grant-LCR-Info					OPTIONAL,
	e-DCH-LCRTDD-Information					E-DCH-LCRTDD-Information							OPTIONAL,
	e-DCH-TDD-Information-to-Modify				E-DCH-TDD-Information-to-Modify						OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { E-DCH-LCR-Information-Reconfig-ExtIEs} }	OPTIONAL,
	...
}

E-DCH-LCR-Information-Reconfig-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


Enabling-Delay ::= ENUMERATED {v0, v1, v2, v4, v8, v16, v32, v64, v128}
	-- Unit of radio frames

Enabling-Delay-Ext-LCR ::= ENUMERATED {infinity,...}

DormantModeIndicator::= ENUMERATED {
	enterDormantMode,
	leaveDormantMode,
...
}

Enhanced-FACH-Capability ::= ENUMERATED {
	enhanced-FACH-capable,
	enhanced-FACH-non-capable
}

EnhancedHSServingCC-Abort ::= ENUMERATED {abortEnhancedHSServingCC,...}

Enhanced-PCH-Capability ::= ENUMERATED {
	enhanced-PCH-capable,
	enhanced-PCH-non-capable
}


Enhanced-UE-DRX-Capability ::= ENUMERATED {
	enhanced-UE-DRX-capable,
	enhanced-UE-DRX-non-capable
}

Enhanced-UE-DRX-InformationFDD  ::= SEQUENCE {
	t321										T321,
	hS-DSCH-DRX-Cycle-FACH						HS-DSCH-DRX-Cycle-FACH,
	hS-DSCH-RX-Burst-FACH						HS-DSCH-RX-Burst-FACH,
	dRX-Interruption-by-HS-DSCH					DRX-Interruption-by-HS-DSCH,
	iE-Extensions									ProtocolExtensionContainer { { Enhanced-UE-DRX-InformationFDD-ExtIEs } }		OPTIONAL,
	...
}

Enhanced-UE-DRX-InformationFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Extended-E-DCH-LCRTDD-PhysicalLayerCategory ::= INTEGER(6,...)

Multi-Carrier-E-DCH-LCRTDD-PhysicalLayerCategory ::= INTEGER(1..8,...)

Ext-Max-Bits-MACe-PDU-non-scheduled ::= INTEGER(19983..22978,...,22979..34507)

Ext-Reference-E-TFCI-PO ::= INTEGER(30..31,...)

ExtendedPropagationDelay ::= INTEGER(255..1023)

Extended-RNC-ID					::= INTEGER (4096..65535)

Extended-Round-Trip-Time-Value ::= INTEGER(32767..103041)
-- See also mapping in TS 25.133 [22]

Extended-HS-SCCH-ID					::= INTEGER (32..255)

Extended-HS-SICH-ID					::= INTEGER (32..255)

Extended-E-HICH-ID-TDD				::= INTEGER (32..255)

Radio-Links-without-DPCH-FDPCH-Indication ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF Radio-Links-without-DPCH-FDPCH-Information

Radio-Links-without-DPCH-FDPCH-Information ::= SEQUENCE {
	rL-ID													RL-ID,
	radio-Links-without-DPCH-FDPCH-Operation-Indicator		ENUMERATED {true},
	iE-Extensions				ProtocolExtensionContainer { { Radio-Links-without-DPCH-FDPCH-Information-ExtIEs} } OPTIONAL,
	...
}

Radio-Links-without-DPCH-FDPCH-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-DCH-Semi-PersistentScheduling-Information-LCR ::= SEQUENCE {
	repetition-Period-List-LCR				Repetition-Period-List-LCR,
	e-DCH-SPS-Indicator						E-DCH-SPS-Indicator,
	sPS-E-DCH-releted-E-HICH-Information	E-HICH-LCR-Information,
	iE-Extensions							ProtocolExtensionContainer { { E-DCH-Semi-PersistentScheduling-Information-LCR-ExtIEs } }			OPTIONAL,
	...
}

E-DCH-Semi-PersistentScheduling-Information-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
{ ID id-E-DCH-SPS-Reservation-Indicator		CRITICALITY ignore		EXTENSION SPS-Reservation-Indicator	PRESENCE optional },
	...
}

E-DCH-SPS-Indicator ::= BIT STRING (SIZE (16))

E-DCH-Semi-PersistentScheduling-Information-to-Modify-LCR ::= SEQUENCE {
	repetition-Period-List-LCR				Repetition-Period-List-LCR		OPTIONAL,
	e-DCH-SPS-Indicator						E-DCH-SPS-Indicator				OPTIONAL,
	sPS-E-DCH-releted-E-HICH-Information	E-HICH-LCR-Information			OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { E-DCH-Semi-PersistentScheduling-Information-to-Modify-LCR-ExtIEs } }			OPTIONAL,
	...
}

E-DCH-Semi-PersistentScheduling-Information-to-Modify-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
{ ID id-E-DCH-SPS-Reservation-Indicator		CRITICALITY ignore		EXTENSION SPS-Reservation-Indicator	PRESENCE optional },
	...
}

E-DCH-Semi-PersistentScheduling-Information-ResponseLCR ::= SEQUENCE {
	timeslot-Resource-Related-Information		E-DCH-TimeslotResourceLCR,
	powerResource								E-DCH-PowerResource,
	repetition-Period-List-LCR					Repetition-Period-List-LCR, 
	-- the IE shall be ignored
	repetitionLength							RepetitionLength, 
	-- the IE shall be ignored
	subframeNumber								ENUMERATED {v0, v1},
	tddE-PUCH-Offset							TddE-PUCH-Offset,
	tdd-ChannelisationCode						TDD-ChannelisationCode,
	n-E-UCCHLCR									N-E-UCCHLCR,
	iE-Extensions								ProtocolExtensionContainer { { E-DCH-Semi-PersistentScheduling-Information-ResponseLCR-ExtIEs } }			OPTIONAL,
	...
}

E-DCH-Semi-PersistentScheduling-Information-ResponseLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-RepetitionPeriodIndex	CRITICALITY reject	EXTENSION RepetitionPeriodIndex		PRESENCE	optional },
	-- mandaroty for 1.28Mcps TDD.
	...
}

ERNTI-Release-Status ::= ENUMERATED {
	released,
	not-released
}

Common-E-DCH-Implicit-Release-Timer ::= ENUMERATED {
	zero,
	more-than-zero
}

-- ==========================================
--	F
-- ==========================================

FACH-Measurement-Occasion-Cycle-Length-Coefficient ::= INTEGER(1..12)

Fast-Reconfiguration-Mode ::= ENUMERATED {fast,...}
Fast-Reconfiguration-Permission ::= ENUMERATED {allowed,...}

Fast-TTI-switching-Mode-synchronized ::= CHOICE {
	mode1			Mode1-Ind,
	mode2			CFN
}

Mode1-Ind ::= NULL

Fast-TTI-switching-Mode-unsynchronized ::= CHOICE {
	mode1			ActivationDelay,
	mode2			CFN
}

Fast-TTI-switching-Mode-Supported ::= ENUMERATED {mode1, mode2}

FDD-DL-ChannelisationCodeNumber ::= INTEGER(0.. 511)
-- According to the mapping in TS 25.213 [9]. The maximum value is equal to the DL spreading factor -1--

FDD-DL-CodeInformation ::= SEQUENCE (SIZE (1..maxNrOfCodes)) OF FDD-DL-CodeInformationItem

FDD-DL-CodeInformationItem ::= SEQUENCE {
	dl-ScramblingCode						DL-ScramblingCode,
	fdd-DL-ChannelisationCodeNumber			FDD-DL-ChannelisationCodeNumber,
	transmissionGapPatternSequenceCodeInformation		TransmissionGapPatternSequenceCodeInformation		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { FDD-DL-CodeInformationItem-ExtIEs} }	OPTIONAL,
	...
}

FDD-DL-CodeInformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

FDD-S-CCPCH-FrameOffset ::= ENUMERATED {
	v1, v2, v4, ...
}

FDD-S-CCPCH-Offset ::= INTEGER (0..149)
-- 0: 0 chip, 1: 256 chip, 2: 512 chip, .. ,149: 38144 chip (TS 25.211 [7]) --

FDD-TPC-DownlinkStepSize ::= ENUMERATED {
	step-size0-5,
	step-size1,
	step-size1-5,
	step-size2,
	...
}

F-DPCH-Capability ::= ENUMERATED {
	f-DPCH-capable,
	f-DPCH-non-capable
}

F-DPCH-Info ::= SEQUENCE {
	f-DPCH-SlotFormat						F-DPCH-SlotFormat,
	fdd-dl-ChannelisationCodeNumber			FDD-DL-ChannelisationCodeNumber,
	extended-E-DPCCH-PO						Extended-E-DPCCH-PO		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { F-DPCH-Info-ExtIEs } }		OPTIONAL,
	...
}

F-DPCH-Info-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

F-DPCH-Info-To-Modify ::= SEQUENCE {
	f-DPCH-SlotFormat						F-DPCH-SlotFormat						OPTIONAL,
	fdd-dl-ChannelisationCodeNumber			FDD-DL-ChannelisationCodeNumber			OPTIONAL,
	extended-E-DPCCH-PO						Extended-E-DPCCH-PO						OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { F-DPCH-Info-To-Modify-ExtIEs } }		OPTIONAL,
	...
}

F-DPCH-Info-To-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

F-DPCH-SlotFormat ::= INTEGER (0..9)


F-DPCH-SlotFormatCapability ::= ENUMERATED {
	f-DPCH-slot-format-capable,
	f-DPCH-slot-format-non-capable
}

FirstRLS-Indicator ::= ENUMERATED {
	first-RLS,
	not-first-RLS,
	...
}

FNReportingIndicator ::= ENUMERATED {
 fN-reporting-required,
 fN-reporting-not-required
}

FrameHandlingPriority ::= INTEGER (0..15)
-- 0=lowest priority, 15=highest priority --

FrameAdjustmentValue ::= INTEGER(0..4095)

FrameOffset ::= INTEGER (0..255)

FPACH-Power ::= INTEGER (-150..400,...) -- FPACH-power = power * 10
-- If power <= -15 FPACH shall be set to -150
-- If power >= 40 FPACH shall be set to 400
-- Unit dBm, Range -15dBm .. +40 dBm, Step +0.1dB

FTPICH-Information ::= SEQUENCE {
	fTPICH-SlotFormat						FTPICH-SlotFormat,
	fTPICH-Offset							FTPICH-Offset,
	fTPICH-ChannelisationCodeNumber		FDD-DL-ChannelisationCodeNumber,
	iE-Extensions							ProtocolExtensionContainer { { FTPICH-Information-ExtIEs } }		OPTIONAL,
	...
}

FTPICH-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

FTPICH-SlotFormat ::= INTEGER (0..9,...)


FTPICH-Offset ::= INTEGER (0..149,...)
-- 0: 0 chip, 1: 256 chip, 2: 512 chip, .. ,149: 38144 chip (TS 25.211 [7]) --


FTPICH-Information-Removal ::= ENUMERATED {
	remove,
	...
}

FTPICH-Information-To-Modify ::= SEQUENCE {
	fTPICH-SlotFormat						FTPICH-SlotFormat					OPTIONAL,
	fTPICH-Offset							FTPICH-Offset						OPTIONAL,
	fTPICH-ChannelisationCodeNumber			FDD-DL-ChannelisationCodeNumber		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { FTPICH-Information-To-Modify-ExtIEs } }		OPTIONAL,
	...
}

FTPICH-Information-To-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

FTPICH-Information-Reconf		::=SEQUENCE{
	setup-Or-ConfigurationChange-Or-Removal-Of-FTPICH-Information	Setup-Or-ConfigurationChange-Or-Removal-Of-FTPICH-Information,
	iE-Extensions													ProtocolExtensionContainer { { FTPICH-Information-Reconf-ExtIEs} } OPTIONAL,
	...
}

FTPICH-Information-Reconf-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Further-Enhanced-UE-DRX-InformationFDD ::= SEQUENCE {
	hS-DSCH-second-DRX-Cycle-FACH			HS-DSCH-Second-DRX-Cycle-FACH,
	cHOICE-DRX-level						CHOICE-DRX-level,
	iE-Extensions							ProtocolExtensionContainer { { Further-Enhanced-UE-DRX-InformationFDD-ExtIEs } }		OPTIONAL,
	...
}

Further-Enhanced-UE-DRX-InformationFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


-- ==========================================
--	G
-- ==========================================


Gainfactors-10ms-mode ::= CHOICE {
	signalledGainFactors10ms	SEQUENCE {
		gain10ms-betaC				BetaCD,
		gain10ms-betaD				BetaCD,
		gain10ms-refTFCNumber		RefTFCNumber	OPTIONAL,
		iE-Extensions				ProtocolExtensionContainer { { SignalledGainFactors10ms-ExtIEs } }		OPTIONAL,
	...
	},
	computedGainFactors10ms		RefTFCNumber,
	...
}


SignalledGainFactors10ms-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-AddClockModels ::= CHOICE {
	navClockModel			 		GANSS-NAVclockModel,
	cnavClockModel			 		GANSS-CNAVclockModel,
	glonassClockModel		 		GANSS-GLONASSclockModel,
	sbasClockModel			 		GANSS-SBASclockModel,
	...,
	bdsClockModel			 		GANSS-BDSclockModel
}

GANSS-AddIonoModelReq ::= BIT STRING (SIZE(2))

GANSS-AddNavigationModelsReq ::= BOOLEAN

GANSS-AddOrbitModels ::= CHOICE {
	navKeplerianSet	 				GANSS-NavModel-NAVKeplerianSet,
	cnavKeplerianSet				GANSS-NavModel-CNAVKeplerianSet,
	glonassECEF						GANSS-NavModel-GLONASSecef,
	sbasECEF						GANSS-NavModel-SBASecef,
	...,
	bdsKeplerianSet					GANSS-NavModel-BDSKeplerianSet
	}

GANSS-AddUTCModelsReq ::= BOOLEAN

GANSS-Additional-Ionospheric-Model ::= SEQUENCE {
	dataID								BIT STRING (SIZE(2)),
	alpha-beta-parameters				GPS-Ionospheric-Model,
	ie-Extensions						ProtocolExtensionContainer { { GANSS-Additional-Ionospheric-Model-ExtIEs } }	OPTIONAL,
	...
}

GANSS-Additional-Ionospheric-Model-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-Additional-Navigation-Models ::= SEQUENCE {
	ganss-Transmission-Time		GANSS-Transmission-Time,
	non-broadcastIndication		ENUMERATED { true }																	OPTIONAL,
	ganssSatInfoNavList			Ganss-Sat-Info-AddNavList,
	ie-Extensions				ProtocolExtensionContainer { { GANSS-Additional-Navigation-Models-ExtIEs } } OPTIONAL,
	...
}

GANSS-Additional-Navigation-Models-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-Additional-Time-Models ::= SEQUENCE (SIZE (1..maxGANSS-1)) OF GANSS-Time-Model

GANSS-Additional-UTC-Models ::= CHOICE {
	utcModel1			GANSS-UTCmodelSet1,
	utcModel2			GANSS-UTCmodelSet2,
	utcModel3			GANSS-UTCmodelSet3,
	...,
	utcModel4			GANSS-UTCmodelSet4
}

GANSS-Almanac ::= SEQUENCE{
	ganss-wk-number						INTEGER(0..255),
	gANSS-AlmanacModel					GANSS-AlmanacModel,
	ie-Extensions		 				ProtocolExtensionContainer { { GANSS-Almanac-ExtIEs } }		OPTIONAL,
	...
}

GANSS-Almanac-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-completeAlmanacProvided			CRITICALITY ignore		EXTENSION CompleteAlmanacProvided			PRESENCE optional},
	...
}

GANSS-AlmanacModel ::= CHOICE {
	gANSS-keplerianParameters			GANSS-KeplerianParametersAlm,
	...,
	extension-GANSS-AlmanacModel		Extension-GANSS-AlmanacModel
}

Extension-GANSS-AlmanacModel	::= ProtocolIE-Single-Container {{ Extension-GANSS-AlmanacModel-IE }}

Extension-GANSS-AlmanacModel-IE NBAP-PROTOCOL-IES ::= {
	{ ID id-GANSS-alm-keplerianNAVAlmanac			CRITICALITY ignore	TYPE GANSS-ALM-NAVKeplerianSet				PRESENCE mandatory}|
	{ ID id-GANSS-alm-keplerianReducedAlmanac		CRITICALITY ignore	TYPE GANSS-ALM-ReducedKeplerianSet			PRESENCE mandatory}|
	{ ID id-GANSS-alm-keplerianMidiAlmanac			CRITICALITY ignore	TYPE GANSS-ALM-MidiAlmanacSet				PRESENCE mandatory}|
	{ ID id-GANSS-alm-keplerianGLONASS				CRITICALITY ignore	TYPE GANSS-ALM-GlonassAlmanacSet			PRESENCE mandatory}|
	{ ID id-GANSS-alm-ecefSBASAlmanac				CRITICALITY ignore	TYPE GANSS-ALM-ECEFsbasAlmanacSet			PRESENCE mandatory}|
	{ ID id-GANSS-alm-keplerianBDSAlmanac			CRITICALITY ignore	TYPE GANSS-ALM-KEPLERIANBDSALMANAC			PRESENCE mandatory}
}

GANSS-ALM-ECEFsbasAlmanacSet ::= SEQUENCE {
	sat-info-SBASecefList		GANSS-SAT-Info-Almanac-SBASecefList,
	ie-Extensions		 		ProtocolExtensionContainer { { GANSS-ALM-ECEFsbasAlmanacSet-ExtIEs } }		OPTIONAL,
	...
}

GANSS-ALM-ECEFsbasAlmanacSet-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-ALM-GlonassAlmanacSet ::= SEQUENCE {
	sat-info-GLOkpList			GANSS-SAT-Info-Almanac-GLOkpList,
	ie-Extensions		 		ProtocolExtensionContainer { { GANSS-ALM-GlonassAlmanacSet-ExtIEs } }		OPTIONAL,
	...
}

GANSS-ALM-GlonassAlmanacSet-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-ALM-MidiAlmanacSet ::= SEQUENCE {
	t-oa						INTEGER (0..255),
	sat-info-MIDIkpList			GANSS-SAT-Info-Almanac-MIDIkpList,
	ie-Extensions		 		ProtocolExtensionContainer { { GANSS-ALM-MidiAlmanacSet-ExtIEs } }		OPTIONAL,
	...
}

GANSS-ALM-MidiAlmanacSet-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-ALM-NAVKeplerianSet ::= SEQUENCE {
	t-oa						INTEGER (0..255),
	sat-info-NAVkpList			GANSS-SAT-Info-Almanac-NAVkpList,
	ie-Extensions		 		ProtocolExtensionContainer { { GANSS-ALM-NAVKeplerianSet-ExtIEs } }		OPTIONAL,
	...
}

GANSS-ALM-NAVKeplerianSet-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-ALM-KEPLERIANBDSALMANAC ::= SEQUENCE {
	sat-info-BDSkpList			GANSS-SAT-Info-Almanac-BDSkpList,
	ie-Extensions		 		ProtocolExtensionContainer { { GANSS-ALM-KEPLERIANBDSALMANAC-ExtIEs } }	OPTIONAL,
	...
}

GANSS-ALM-KEPLERIANBDSALMANAC-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-ALM-ReducedKeplerianSet ::= SEQUENCE {
	t-oa						INTEGER (0..255),
	sat-info-REDkpList			GANSS-SAT-Info-Almanac-REDkpList,
	ie-Extensions		 		ProtocolExtensionContainer { { GANSS-ALM-ReducedKeplerianSet-ExtIEs } }		OPTIONAL,
	...
}

GANSS-ALM-ReducedKeplerianSet-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-Auxiliary-Information ::= CHOICE {
	ganssID1	GANSS-AuxInfoGANSS-ID1, 	-- This choice may only be present if GANSS ID indicates Modernized GPS
	ganssID3	GANSS-AuxInfoGANSS-ID3, 	-- This choice may only be present if GANSS ID indicates GLONASS
	...
}

GANSS-AuxInfoGANSS-ID1 ::= SEQUENCE (SIZE(1.. maxGANSSSat)) OF GANSS-AuxInfoGANSS-ID1-element

GANSS-AuxInfoGANSS-ID1-element ::= SEQUENCE {
	svID				INTEGER(0..63),
	signalsAvailable	BIT STRING (SIZE(8)),
	ie-Extensions		ProtocolExtensionContainer { { GANSS-AuxInfoGANSS-ID1-element-ExtIEs } }	OPTIONAL,
	...
}

GANSS-AuxInfoGANSS-ID1-element-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-AuxInfoGANSS-ID3 ::= SEQUENCE (SIZE(1.. maxGANSSSat)) OF GANSS-AuxInfoGANSS-ID3-element

GANSS-AuxInfoGANSS-ID3-element  ::= SEQUENCE {
	svID				INTEGER(0..63),
	signalsAvailable	BIT STRING (SIZE(8)),
	channelNumber		INTEGER (-7..13),
	ie-Extensions		ProtocolExtensionContainer { { GANSS-AuxInfoGANSS-ID3-element-ExtIEs } }	OPTIONAL,
	...
}

GANSS-AuxInfoGANSS-ID3-element-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-AuxInfoReq ::= BOOLEAN

GANSS-BDSclockModel ::= SEQUENCE {
	bdsToc				BIT STRING (SIZE (17)),
	bdsa0				BIT STRING (SIZE (24)),
	bdsa1				BIT STRING (SIZE (22)),
	bdsa2				BIT STRING (SIZE (11)),
	bdsTgd1				BIT STRING (SIZE (10)),
	bdsAODC				BIT STRING (SIZE (5)),
	ie-Extensions		ProtocolExtensionContainer { { GANSS-BDSclockModel-ExtIEs } }	OPTIONAL,
	...
}

GANSS-BDSclockModel-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-Clock-Model ::= SEQUENCE (SIZE (1..maxGANSSClockMod)) OF GANSS-SatelliteClockModelItem

GANSS-CNAVclockModel ::= SEQUENCE {
	cnavToc				BIT STRING (SIZE (11)),
	cnavTop				BIT STRING (SIZE (11)),
	cnavURA0			BIT STRING (SIZE (5)),
	cnavURA1			BIT STRING (SIZE (3)),
	cnavURA2			BIT STRING (SIZE (3)),
	cnavAf2				BIT STRING (SIZE (10)),
	cnavAf1				BIT STRING (SIZE (20)),
	cnavAf0				BIT STRING (SIZE (26)),
	cnavTgd				BIT STRING (SIZE (13)),
	cnavISCl1cp			BIT STRING (SIZE (13)) 											OPTIONAL,
	cnavISCl1cd			BIT STRING (SIZE (13))											OPTIONAL,
	cnavISCl1ca			BIT STRING (SIZE (13))											OPTIONAL,
	cnavISCl2c			BIT STRING (SIZE (13))											OPTIONAL,
	cnavISCl5i5			BIT STRING (SIZE (13)) 											OPTIONAL,
	cnavISCl5q5			BIT STRING (SIZE (13))											OPTIONAL,
	ie-Extensions		ProtocolExtensionContainer { { GANSS-CNAVclockModel-ExtIEs } }	OPTIONAL,
	...
}

GANSS-CNAVclockModel-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-Common-Data ::= SEQUENCE {
	ganss-Ionospheric-Model				GANSS-Ionospheric-Model																OPTIONAL,
	ganss-Rx-Pos						GANSS-RX-Pos																		OPTIONAL,
	ie-Extensions						ProtocolExtensionContainer { { GANSS-Common-Data-ExtIEs } }	OPTIONAL,
	...
}

GANSS-Common-Data-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-GANSS-Additional-Ionospheric-Model		CRITICALITY ignore	EXTENSION GANSS-Additional-Ionospheric-Model	PRESENCE optional }|
	{ ID id-GANSS-Earth-Orientation-Parameters		CRITICALITY ignore	EXTENSION GANSS-Earth-Orientation-Parameters	PRESENCE optional },
	...
}

GANSS-CommonDataInfoReq ::= SEQUENCE {
	ionospheric-Model					BOOLEAN																				OPTIONAL,
	ie-Extensions						ProtocolExtensionContainer { { GANSS-CommonDataInfoReq-ExtIEs } }	OPTIONAL,
	...
}

GANSS-CommonDataInfoReq-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-GANSS-AddIonoModelReq		CRITICALITY	ignore	EXTENSION	GANSS-AddIonoModelReq									PRESENCE	optional} |
	{ID id-GANSS-EarthOrientParaReq		CRITICALITY	ignore	EXTENSION	GANSS-EarthOrientParaReq		PRESENCE	optional} ,
	...
}

GANSS-Data-Bit-Assistance ::= SEQUENCE {
	ganssTod							INTEGER (0..59,...),
	dataBitAssistancelist				GANSS-DataBitAssistanceList, 
	ie-Extensions						ProtocolExtensionContainer { { GANSS-Data-Bit-Assistance-ExtIEs } }	OPTIONAL,
	...
}

GANSS-Data-Bit-Assistance-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-DataBitAssistanceList ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF GANSS-DataBitAssistanceItem

GANSS-DataBitAssistanceItem ::= SEQUENCE {
	satId							INTEGER(0..63),
	dataBitAssistanceSgnList		GANSS-DataBitAssistanceSgnList,
	ie-Extensions					ProtocolExtensionContainer { { GANSS-DataBitAssistanceItem-ExtIEs } }	OPTIONAL,
	...
}

GANSS-DataBitAssistanceItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-DataBitAssistanceSgnList ::= SEQUENCE (SIZE (1..maxSgnType)) OF GANSS-DataBitAssistanceSgnItem



GANSS-DataBitAssistanceSgnItem ::= SEQUENCE {
	ganss-SignalId			GANSS-Signal-ID,
	ganssDataBits			BIT STRING (SIZE (1..1024)),
	ie-Extensions			ProtocolExtensionContainer { { GANSS-DataBitAssistanceSgnItem-ExtIEs } }	OPTIONAL,
	...
}

GANSS-DataBitAssistanceSgnItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-Data-Bit-Assistance-ReqItem ::= SEQUENCE {
	ganssTod								INTEGER (0..86399),
	ganss-Data-Bit-Assistance-ReqList		GANSS-Data-Bit-Assistance-ReqList,
	iE-Extensions							ProtocolExtensionContainer { { GANSS-Data-Bit-Assistance-ReqItem-ExtIEs } }	OPTIONAL,
	...
}

GANSS-Data-Bit-Assistance-ReqItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-Data-Bit-Assistance-ReqList ::= SEQUENCE {
	dGANSS-Signal-ID					BIT STRING (SIZE (8)),
	ganss-DataBitInterval				INTEGER(0..15),
	ganss-SatelliteInfo					SEQUENCE (SIZE (1..maxGANSSSat)) OF INTEGER(0..63) 											OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { GANSS-Data-Bit-Assistance-ReqList-ExtIEs } }			OPTIONAL,
	...
}

GANSS-Data-Bit-Assistance-ReqList-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-Delta-T ::= INTEGER(-128..127)

GANSS-DeltaUT1 ::= SEQUENCE {
	b1					BIT STRING (SIZE(11)),
	b2					BIT STRING (SIZE(10)),
	ie-Extensions		ProtocolExtensionContainer { { GANSS-DeltaUT1-ExtIEs } }	OPTIONAL,
	...
}

GANSS-DeltaUT1-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-Earth-Orientation-Parameters ::= SEQUENCE {
	teop				BIT STRING (SIZE (16)),
	pmX					BIT STRING (SIZE (21)),
	pmXdot				BIT STRING (SIZE (15)),
	pmY					BIT STRING (SIZE (21)),
	pmYdot				BIT STRING (SIZE (15)),
	deltaUT1			BIT STRING (SIZE (31)),
	deltaUT1dot			BIT STRING (SIZE (19)),
	ie-Extensions		ProtocolExtensionContainer { { GANSS-Earth-Orientation-Parameters-ExtIEs } }	OPTIONAL,
	...
}

GANSS-Earth-Orientation-Parameters-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-EarthOrientParaReq ::= BOOLEAN

GANSS-GenericDataInfoReqList ::= SEQUENCE (SIZE(1..maxNoGANSS)) OF GANSS-GenericDataInfoReqItem

GANSS-GenericDataInfoReqItem ::= SEQUENCE {
	ganss-Id									GANSS-ID																			OPTIONAL,
	ganss-Navigation-Model-And-Time-Recovery	BOOLEAN															OPTIONAL,
	ganss-Time-Model-GNSS-GNSS					BIT STRING (SIZE (9))											OPTIONAL,
	ganss-UTC-Model								BOOLEAN															OPTIONAL,
	ganss-Almanac								BOOLEAN															OPTIONAL,
	ganss-Real-Time-Integrity					BOOLEAN															OPTIONAL,
	ganss-Data-Bit-Assistance-Req				GANSS-Data-Bit-Assistance-ReqItem								OPTIONAL,
	ie-Extensions								ProtocolExtensionContainer { { GANSS-GenericDataInfoReqItem-ExtIEs } }		OPTIONAL,
	...
}

GANSS-GenericDataInfoReqItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-GANSS-AddNavigationModelsReq	CRITICALITY ignore	EXTENSION GANSS-AddNavigationModelsReq			PRESENCE optional} |
	{ID id-GANSS-AddUTCModelsReq		CRITICALITY ignore	EXTENSION GANSS-AddUTCModelsReq						PRESENCE optional} |
	{ID id-GANSS-AuxInfoReq				CRITICALITY ignore	EXTENSION GANSS-AuxInfoReq							PRESENCE optional} |
-- The following IE shall be present if ‘GANSS-ID’ in ‘GANSS-GenericDataInfoReqItem’ is ‘0’ (SBAS)
	{ID id-GANSS-SBAS-ID				CRITICALITY ignore	EXTENSION GANSS-SBAS-ID								PRESENCE optional} |
	{ID id-DBDS-CorrectionsReq			CRITICALITY ignore	EXTENSION DBDS-CorrectionsReq						PRESENCE optional}|
	{ID id-BDS-IonosphericGridModelReq	CRITICALITY ignore	EXTENSION BDS-IonosphericGridModelReq				PRESENCE optional},
	...
}

GANSS-Generic-Data ::= SEQUENCE (SIZE(1..maxNoGANSS)) OF GANSS-Generic-DataItem

GANSS-Generic-DataItem ::= SEQUENCE {
	ganss-Id									GANSS-ID																			OPTIONAL,
	dganss-Correction							DGANSSCorrections																	OPTIONAL,
	ganss-Navigation-Model-And-Time-Recovery	GANSS-Navigation-Model-And-Time-Recovery											OPTIONAL,
	ganss-Time-Model							GANSS-Time-Model																	OPTIONAL,
	ganss-UTC-TIME								GANSS-UTC-Model																		OPTIONAL,
	ganss-Almanac								GANSS-Almanac																		OPTIONAL,
	ganss-Real-Time-Integrity					GANSS-Real-Time-Integrity															OPTIONAL,
	ganss-Data-Bit-Assistance					GANSS-Data-Bit-Assistance															OPTIONAL,
	ie-Extensions								ProtocolExtensionContainer { { GANSS-Generic-DataItem-ExtIEs } }				OPTIONAL,
	...
}

GANSS-Generic-DataItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-GANSS-Additional-Time-Models			CRITICALITY ignore	EXTENSION GANSS-Additional-Time-Models			PRESENCE optional }|
	{ ID id-GANSS-Additional-Navigation-Models		CRITICALITY ignore	EXTENSION GANSS-Additional-Navigation-Models	PRESENCE optional }|
	{ ID id-GANSS-Additional-UTC-Models				CRITICALITY ignore	EXTENSION GANSS-Additional-UTC-Models				PRESENCE optional }|
	{ ID id-GANSS-Auxiliary-Information				CRITICALITY ignore	EXTENSION GANSS-Auxiliary-Information				PRESENCE optional }|
	-- The following element shall be present if ‘GANSS-ID’ in ‘GANSS-Generic-DataItem’ is ‘0’ (‘SBAS’)
	{ ID id-GANSS-SBAS-ID							CRITICALITY ignore	EXTENSION GANSS-SBAS-ID									PRESENCE optional }|
	{ ID id-DBDS-Corrections						CRITICALITY ignore	EXTENSION DBDS-Corrections							PRESENCE optional }|
	{ ID id-BDS-Ionospheric-Grid-Model				CRITICALITY ignore	EXTENSION BDS-Ionospheric-Grid-Model				PRESENCE optional },
	...
}


GANSS-GLONASSclockModel ::= SEQUENCE {
	gloTau					BIT STRING (SIZE (22)),
	gloGamma				BIT STRING (SIZE (11)),
	gloDeltaTau				BIT STRING (SIZE (5)) 												OPTIONAL,
	ie-Extensions			ProtocolExtensionContainer { { GANSS-GLONASSclockModel-ExtIEs } }	OPTIONAL,
	...
}

GANSS-GLONASSclockModel-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-ID ::= INTEGER(0..7,...)


GANSS-Information ::= SEQUENCE {
	gANSS-CommonDataInfoReq				GANSS-CommonDataInfoReq											OPTIONAL,
	gANSS-GenericDataInfoReqList		GANSS-GenericDataInfoReqList									OPTIONAL,
	ie-Extensions						ProtocolExtensionContainer { { GANSS-Information-ExtIEs } }	OPTIONAL,
	...
}

GANSS-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-Ionospheric-Model ::= SEQUENCE {
	alpha-zero-ionos					BIT STRING (SIZE (11)),
	alpha-one-ionos						BIT STRING (SIZE (11)),
	alpha-two-ionos						BIT STRING (SIZE (14)),
	gANSS-IonosphereRegionalStormFlags	GANSS-IonosphereRegionalStormFlags							OPTIONAL,
	ie-Extensions						ProtocolExtensionContainer { { GANSS-Ionospheric-Model-ExtIEs } }	OPTIONAL,
	...
}

GANSS-Ionospheric-Model-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-IonosphereRegionalStormFlags ::= SEQUENCE {
	storm-flag-one						BOOLEAN,
	storm-flag-two						BOOLEAN,
	storm-flag-three					BOOLEAN,
	storm-flag-four						BOOLEAN,
	storm-flag-five						BOOLEAN,
	ie-Extensions						ProtocolExtensionContainer { { GANSS-IonosphereRegionalStormFlags-ExtIEs } } OPTIONAL,
	...
}

GANSS-IonosphereRegionalStormFlags-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-KeplerianParametersAlm ::= SEQUENCE {
	t-oa								INTEGER(0..1023),
	iod-a								INTEGER(0..15),
	gANSS-SatelliteInformationKP		GANSS-SatelliteInformationKP,
	ie-Extensions		 				ProtocolExtensionContainer { { GANSS-KeplerianParametersAlm-ExtIEs } }		OPTIONAL,
	...
}

GANSS-KeplerianParametersAlm-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-KeplerianParametersOrb ::= SEQUENCE {
	toe-nav								BIT STRING (SIZE (14)),
	ganss-omega-nav						BIT STRING (SIZE (32)),
	delta-n-nav							BIT STRING (SIZE (16)),
	m-zero-nav							BIT STRING (SIZE (32)),
	omegadot-nav						BIT STRING (SIZE (24)),
	ganss-e-nav							BIT STRING (SIZE (32)),
	idot-nav							BIT STRING (SIZE (14)),
	a-sqrt-nav							BIT STRING (SIZE (32)),
	i-zero-nav							BIT STRING (SIZE (32)),
	omega-zero-nav						BIT STRING (SIZE (32)),
	c-rs-nav							BIT STRING (SIZE (16)),
	c-is-nav							BIT STRING (SIZE (16)),
	c-us-nav							BIT STRING (SIZE (16)),
	c-rc-nav							BIT STRING (SIZE (16)),
	c-ic-nav 							BIT STRING (SIZE (16)),
	c-uc-nav							BIT STRING (SIZE (16)),
	ie-Extensions		 				ProtocolExtensionContainer { { GANSS-KeplerianParametersOrb-ExtIEs } }		OPTIONAL,
	...
}

GANSS-KeplerianParametersOrb-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-NAVclockModel ::= SEQUENCE {
	navToc					BIT STRING (SIZE (16)),
	navaf2					BIT STRING (SIZE (8)),
	navaf1					BIT STRING (SIZE (16)),
	navaf0					BIT STRING (SIZE (22)),
	navTgd					BIT STRING (SIZE (8)),
	ie-Extensions			ProtocolExtensionContainer { { GANSS-NAVclockModel-ExtIEs } }	OPTIONAL,
	...
}

GANSS-NAVclockModel-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-Navigation-Model-And-Time-Recovery ::= SEQUENCE {
	ganss-Transmission-Time		GANSS-Transmission-Time,
	non-broadcastIndication		ENUMERATED{true}		OPTIONAL,
	ganssSatInfoNav				GANSS-Sat-Info-Nav,
	ie-Extensions				ProtocolExtensionContainer { { GANSS-Navigation-Model-And-Time-Recovery-ExtIEs } } OPTIONAL,
	...
}

GANSS-Navigation-Model-And-Time-Recovery-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-NavModel-BDSKeplerianSet ::= 		SEQUENCE {
	bdsURAI				BIT STRING (SIZE (4)),
	bdsToe				BIT STRING (SIZE (17)),
	bdsAPowerHalf		BIT STRING (SIZE (32)),
	bdsE				BIT STRING (SIZE (32)),
	bdsW				BIT STRING (SIZE (32)),
	bdsDeltaN			BIT STRING (SIZE (16)),
	bdsM0				BIT STRING (SIZE (32)),
	bdsOmega0			BIT STRING (SIZE (32)),
	bdsOmegaDot			BIT STRING (SIZE (24)),
	bdsI0				BIT STRING (SIZE (32)),
	bdsIDot				BIT STRING (SIZE (14)),
	bdsCuc				BIT STRING (SIZE (18)),
	bdsCus				BIT STRING (SIZE (18)),
	bdsCrc				BIT STRING (SIZE (18)),
	bdsCrs				BIT STRING (SIZE (18)),
	bdsCic				BIT STRING (SIZE (18)),
	bdsCis				BIT STRING (SIZE (18)),
	bdsAODE				BIT STRING (SIZE (5)),
	ie-Extensions		ProtocolExtensionContainer { { GANSS-NavModel-BDSKeplerianSet-ExtIEs } } OPTIONAL,
	...
}

GANSS-NavModel-BDSKeplerianSet-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-NavModel-CNAVKeplerianSet ::= SEQUENCE {
	cnavTop					BIT STRING (SIZE (11)),
	cnavURAindex			BIT STRING (SIZE (5)),
	cnavDeltaA				BIT STRING (SIZE (26)),
	cnavAdot				BIT STRING (SIZE (25)),
	cnavDeltaNo				BIT STRING (SIZE (17)),
	cnavDeltaNoDot			BIT STRING (SIZE (23)),
	cnavMo					BIT STRING (SIZE (33)),
	cnavE					BIT STRING (SIZE (33)),
	cnavOmega				BIT STRING (SIZE (33)),
	cnavOMEGA0				BIT STRING (SIZE (33)),
	cnavDeltaOmegaDot		BIT STRING (SIZE (17)),
	cnavIo					BIT STRING (SIZE (33)),
	cnavIoDot				BIT STRING (SIZE (15)),
	cnavCis					BIT STRING (SIZE (16)),
	cnavCic					BIT STRING (SIZE (16)),
	cnavCrs					BIT STRING (SIZE (24)),
	cnavCrc					BIT STRING (SIZE (24)),
	cnavCus					BIT STRING (SIZE (21)),
	cnavCuc					BIT STRING (SIZE (21)),
	ie-Extensions			ProtocolExtensionContainer { { GANSS-NavModel-CNAVKeplerianSet-ExtIEs } }	OPTIONAL,
	...
}

GANSS-NavModel-CNAVKeplerianSet-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-NavModel-GLONASSecef ::= SEQUENCE {
	gloEn					BIT STRING (SIZE (5)),
	gloP1					BIT STRING (SIZE(2)),
	gloP2					BIT STRING (SIZE (1)),
	gloM					BIT STRING (SIZE (2))																			OPTIONAL,
	gloX					BIT STRING (SIZE (27)),
	gloXdot					BIT STRING (SIZE (24)),
	gloXdotdot				BIT STRING (SIZE (5)),
	gloY					BIT STRING (SIZE (27)),
	gloYdot					BIT STRING (SIZE (24)),
	gloYdotdot				BIT STRING (SIZE (5)),
	gloZ					BIT STRING (SIZE (27)),
	gloZdot					BIT STRING (SIZE (24)),
	gloZdotdot				BIT STRING (SIZE (5)),
	ie-Extensions			ProtocolExtensionContainer { { GANSS-NavModel-GLONASSecef-ExtIEs } }	OPTIONAL,
	...
}

GANSS-NavModel-GLONASSecef-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


GANSS-NavModel-NAVKeplerianSet ::= SEQUENCE {
	navURA					BIT STRING (SIZE (4)),
	navFitFlag				BIT STRING (SIZE (1)),
	navToe					BIT STRING (SIZE (16)),
	navOmega				BIT STRING (SIZE (32)),
	navDeltaN				BIT STRING (SIZE (16)),
	navM0					BIT STRING (SIZE (32)),
	navOmegaADot			BIT STRING (SIZE (24)),
	navE					BIT STRING (SIZE (32)),
	navIDot					BIT STRING (SIZE (14)),
	navAPowerHalf			BIT STRING (SIZE (32)),
	navI0					BIT STRING (SIZE (32)),
	navOmegaA0				BIT STRING (SIZE (32)),
	navCrs					BIT STRING (SIZE (16)),
	navCis					BIT STRING (SIZE (16)),
	navCus					BIT STRING (SIZE (16)),
	navCrc					BIT STRING (SIZE (16)),
	navCic					BIT STRING (SIZE (16)),
	navCuc					BIT STRING (SIZE (16)),
	ie-Extensions			ProtocolExtensionContainer { { GANSS-NavModel-NAVKeplerianSet-ExtIEs } }	OPTIONAL,
	...
}

GANSS-NavModel-NAVKeplerianSet-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-NavModel-SBASecef ::= SEQUENCE {
	-- The following IE shall be present if ‘GANSS-SBASclockModel’ in ‘GANSS-AddClockModels’ is not included in ‘Ganss-Sat-Info-AddNavList’
	sbasTo					BIT STRING (SIZE (13))												OPTIONAL,
	sbasAccuracy			BIT STRING (SIZE (4)),
	sbasXg					BIT STRING (SIZE (30)),
	sbasYg					BIT STRING (SIZE (30)),
	sbasZg					BIT STRING (SIZE (25)),
	sbasXgDot				BIT STRING (SIZE (17)),
	sbasYgDot				BIT STRING (SIZE (17)),
	sbasZgDot				BIT STRING (SIZE (18)),
	sbasXgDotDot			BIT STRING (SIZE (10)),
	sbagYgDotDot			BIT STRING (SIZE (10)),
	sbasZgDotDot			BIT STRING (SIZE (10)),
	ie-Extensions			ProtocolExtensionContainer { { GANSS-NavModel-SBASecef-ExtIEs } }	OPTIONAL,
	...
}

GANSS-NavModel-SBASecef-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-Orbit-Model ::= CHOICE {
	gANSS-keplerianParameters			GANSS-KeplerianParametersOrb,
	...
}

GANSS-Real-Time-Integrity ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF GANSS-RealTimeInformationItem

GANSS-RealTimeInformationItem ::= SEQUENCE {
	bad-ganss-satId						INTEGER(0..63),
	bad-ganss-signalId					BIT STRING(SIZE(8))											OPTIONAL,
	ie-Extensions						ProtocolExtensionContainer { { GANSS-RealTimeInformationItem-ExtIEs } }	OPTIONAL,
	...
}

GANSS-RealTimeInformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-RX-Pos ::= SEQUENCE {
	latitudeSign						ENUMERATED{north,south},
	degreesOfLatitude					INTEGER(0..2147483647),
	degreesOfLongitude					INTEGER(-2147483648..2147483647),
	directionOfAltitude					ENUMERATED{height,depth},
	altitude							INTEGER(0..32767),
	ie-Extensions						ProtocolExtensionContainer { { GANSS-RX-Pos-ExtIEs } }	OPTIONAL,
	...
}

GANSS-RX-Pos-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-SatelliteClockModelItem ::= SEQUENCE {
	t-oc								BIT STRING (SIZE (14)),
	a-i2								BIT STRING (SIZE (6)),
	a-i1								BIT STRING (SIZE (21)),
	a-i0								BIT STRING (SIZE (31)),
	t-gd								BIT STRING (SIZE (10))										OPTIONAL,
	sisa								BIT STRING (SIZE (8)),
	model-id							INTEGER(0..1,...)											OPTIONAL,
	ie-Extensions						ProtocolExtensionContainer { { GANSS-SatelliteClockModelItem-ExtIEs } }	OPTIONAL,
	...
}

GANSS-SatelliteClockModelItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-SatelliteInformationKP ::= SEQUENCE (SIZE (1..maxGANSSSatAlmanac)) OF GANSS-SatelliteInformationKPItem

GANSS-SatelliteInformationKPItem ::= SEQUENCE {
	satId								INTEGER(0..63),
	ganss-e-alm							BIT STRING (SIZE (11)), 
	ganss-delta-I-alm					BIT STRING (SIZE (11)),
	ganss-omegadot-alm					BIT STRING (SIZE (11)),
	ganss-svStatusINAV-alm				BIT STRING (SIZE (4)),
	ganss-svStatusFNAV-alm				BIT STRING (SIZE (2))	OPTIONAL,
	ganss-delta-a-sqrt-alm				BIT STRING (SIZE (13)),
	ganss-omegazero-alm					BIT STRING (SIZE (16)),
	ganss-m-zero-alm					BIT STRING (SIZE (16)),
	ganss-omega-alm						BIT STRING (SIZE (16)),
	ganss-af-zero-alm					BIT STRING (SIZE (16)),
	ganss-af-one-alm 					BIT STRING (SIZE (13)),
	ie-Extensions						ProtocolExtensionContainer { { GANSS-SatelliteInformationKPItem-ExtIEs } }	OPTIONAL,
	...
}

GANSS-SatelliteInformationKPItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Ganss-Sat-Info-AddNavList ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF SEQUENCE {
	satId						INTEGER (0..63),
	svHealth					BIT STRING (SIZE (9)),
	iod							BIT STRING (SIZE (11)),
	ganssAddClockModels			GANSS-AddClockModels,
	ganssAddOrbitModels			GANSS-AddOrbitModels,
	ie-Extensions				ProtocolExtensionContainer { { Ganss-Sat-Info-AddNavList-ExtIEs } } OPTIONAL,
	...
}

Ganss-Sat-Info-AddNavList-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-SAT-Info-Almanac-BDSkpList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF GANSS-SAT-Info-Almanac-BDS

GANSS-SAT-Info-Almanac-BDS ::= SEQUENCE {
	satId						INTEGER(0..63),
	bdsAlmToa					BIT STRING (SIZE (8)),
	bdsAlmSqrtA					BIT STRING (SIZE (24)),
	bdsAlmE						BIT STRING (SIZE (17)),
	bdsAlmW						BIT STRING (SIZE (24)),
	bdsAlmM0					BIT STRING (SIZE (24)),
	bdsAlmOmega0				BIT STRING (SIZE (24)),
	bdsAlmOmegaDot				BIT STRING (SIZE (17)),
	bdsAlmDeltaI				BIT STRING (SIZE (16)),
	bdsAlmA0					BIT STRING (SIZE (11)),
	bdsAlmA1					BIT STRING (SIZE (11)),
	bdsSvHealth					BIT STRING (SIZE(9))	OPTIONAL,
-- Mondatory if the IE “Sat ID” is between 0 and 29 and not needed otherwise
	ie-Extensions				ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-BDS-ExtIEs } } OPTIONAL,
...
}

GANSS-SAT-Info-Almanac-BDS-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-SAT-Info-Almanac-GLOkpList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF GANSS-SAT-Info-Almanac-GLOkp

GANSS-SAT-Info-Almanac-GLOkp ::= SEQUENCE {
	gloAlmNA				BIT STRING (SIZE(11)),
	gloAlmnA				BIT STRING (SIZE(5)),
	gloAlmHA				BIT STRING (SIZE(5)),
	gloAlmLambdaA			BIT STRING (SIZE(21)),
	gloAlmTlambdaA			BIT STRING (SIZE(21)),
	gloAlmDeltaIA			BIT STRING (SIZE(18)),
	gloAkmDeltaTA			BIT STRING (SIZE(22)),
	gloAlmDeltaTdotA		BIT STRING (SIZE(7)),
	gloAlmEpsilonA			BIT STRING (SIZE(15)),
	gloAlmOmegaA			BIT STRING (SIZE(16)),
	gloAlmTauA				BIT STRING (SIZE(10)),
	gloAlmCA				BIT STRING (SIZE(1)),
	gloAlmMA				BIT STRING (SIZE(2)) 																			OPTIONAL,
	ie-Extensions			ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-GLOkp-ExtIEs } }	OPTIONAL,
	...
}

GANSS-SAT-Info-Almanac-GLOkp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-SAT-Info-Almanac-MIDIkpList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF GANSS-SAT-Info-Almanac-MIDIkp

GANSS-SAT-Info-Almanac-MIDIkp ::= SEQUENCE {
	svID					INTEGER(0..63),
	midiAlmE				BIT STRING (SIZE (11)),
	midiAlmDeltaI			BIT STRING (SIZE (11)),
	midiAlmOmegaDot			BIT STRING (SIZE (11)),
	midiAlmSqrtA			BIT STRING (SIZE (17)),
	midiAlmOmega0			BIT STRING (SIZE (16)),
	midiAlmOmega			BIT STRING (SIZE (16)),
	midiAlmMo				BIT STRING (SIZE (16)),
	midiAlmaf0				BIT STRING (SIZE (11)),
	midiAlmaf1				BIT STRING (SIZE (10)),
	midiAlmL1Health			BIT STRING (SIZE (1)),
	midiAlmL2Health			BIT STRING (SIZE (1)),
	midiAlmL5Health			BIT STRING (SIZE (1)),
	ie-Extensions			ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-MIDIkp-ExtIEs } }	OPTIONAL,
	...
}

GANSS-SAT-Info-Almanac-MIDIkp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-SAT-Info-Almanac-NAVkpList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF GANSS-SAT-Info-Almanac-NAVkp

GANSS-SAT-Info-Almanac-NAVkp ::= SEQUENCE {
	svID					INTEGER(0..63),
	navAlmE					BIT STRING (SIZE (16)),
	navAlmDeltaI			BIT STRING (SIZE (16)),
	navAlmOMEGADOT			BIT STRING (SIZE (16)),
	navAlmSVHealth			BIT STRING (SIZE (8)),
	navAlmSqrtA				BIT STRING (SIZE (24)),
	navAlmOMEGAo			BIT STRING (SIZE (24)),
	navAlmOmega				BIT STRING (SIZE (24)),
	navAlmMo				BIT STRING (SIZE (24)),
	navAlmaf0				BIT STRING (SIZE (11)),
	navAlmaf1				BIT STRING (SIZE (11)),
	ie-Extensions			ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-NAVkp-ExtIEs } }	OPTIONAL,
	...
}

GANSS-SAT-Info-Almanac-NAVkp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-SAT-Info-Almanac-REDkpList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF GANSS-SAT-Info-Almanac-REDkp

GANSS-SAT-Info-Almanac-REDkp ::= SEQUENCE {
	svID					INTEGER(0..63),
	redAlmDeltaA			BIT STRING (SIZE (8)),
	redAlmOmega0			BIT STRING (SIZE (7)),
	redAlmPhi0				BIT STRING (SIZE (7)),
	redAlmL1Health			BIT STRING (SIZE (1)),
	redAlmL2Health			BIT STRING (SIZE (1)),
	redAlmL5Health			BIT STRING (SIZE (1)),
	ie-Extensions			ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-REDkp-ExtIEs } }	OPTIONAL,
	...
}

GANSS-SAT-Info-Almanac-REDkp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-SAT-Info-Almanac-SBASecefList ::=	SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF GANSS-SAT-Info-Almanac-SBASecef

GANSS-SAT-Info-Almanac-SBASecef ::=	SEQUENCE {
	sbasAlmDataID			BIT STRING (SIZE(2)),
	svID					INTEGER(0..63),
	sbasAlmHealth			BIT STRING (SIZE(8)),
	sbasAlmXg				BIT STRING (SIZE(15)),
	sbasAlmYg				BIT STRING (SIZE(15)),
	sbasAlmZg				BIT STRING (SIZE(9)),
	sbasAlmXgdot			BIT STRING (SIZE(3)),
	sbasAlmYgDot			BIT STRING (SIZE(3)),
	sbasAlmZgDot			BIT STRING (SIZE(4)),
	sbasAlmTo				BIT STRING (SIZE(11)),
	ie-Extensions			ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-SBASecef-ExtIEs } }	OPTIONAL,
	...
}

GANSS-SAT-Info-Almanac-SBASecef-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


GANSS-Sat-Info-Nav ::= SEQUENCE (SIZE(1..maxGANSSSat)) OF SEQUENCE {
	satId						INTEGER(0..63),
	svHealth					BIT STRING (SIZE(5)),
	iod							BIT STRING (SIZE(10)),
	ganssClockModel				GANSS-Clock-Model,
	ganssOrbitModel				GANSS-Orbit-Model,
	ie-Extensions				ProtocolExtensionContainer { { GANSS-Sat-Info-Nav-ExtIEs } } OPTIONAL,
	...
}

GANSS-Sat-Info-Nav-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


GANSS-SBAS-ID ::= ENUMERATED 	{
								waas,
								egnos,
								msas,
								gagan,
								...
								}

GANSS-SBASclockModel ::= SEQUENCE {
	sbasTo					BIT STRING (SIZE (13)),
	sbasAgfo				BIT STRING (SIZE (12)),
	sbasAgf1				BIT STRING (SIZE (8)),
	ie-Extensions			ProtocolExtensionContainer { { GANSS-SBASclockModel-ExtIEs } }	OPTIONAL,
	...
}

GANSS-SBASclockModel-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-Signal-ID ::= INTEGER(0..7,...)

GANSS-StatusHealth ::= ENUMERATED {
	udre-scale-1dot0,
	udre-scale-0dot75,
	udre-scale-0dot5,
	udre-scale-0dot3,
	udre-scale-0dot2,
	udre-scale-0dot1,
	no-data,
	invalid-data
}

GANSS-Time-ID	::= INTEGER(0..7,...)

GANSS-Time-Model ::= SEQUENCE {
	ganss-time-model-Ref-Time			INTEGER(0..37799),
	ganss-t-a0							INTEGER(-2147483648.. 2147483647),
	ganss-t-a1							INTEGER(-8388608.. 8388607)									OPTIONAL,
	ganss-t-a2							INTEGER(-64..63)											OPTIONAL,
	gnss-to-id							ENUMERATED{gps,...,galileo,qzss,glonass,bds},
	ganss-wk-number						INTEGER(0..8191)											OPTIONAL,
	ie-Extensions						ProtocolExtensionContainer { { GANSS-Time-Model-ExtIEs } }	OPTIONAL,
	...
}

GANSS-Time-Model-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-ganss-Delta-T		CRITICALITY ignore	EXTENSION GANSS-Delta-T		PRESENCE optional},
	...
}

GANSS-Transmission-Time ::= SEQUENCE {
	ganssDay					INTEGER(0..8191)																			OPTIONAL,
	ganssTod					INTEGER(0..86399),
	ie-Extensions				ProtocolExtensionContainer { { GANSS-Transmission-Time-ExtIEs } } 						OPTIONAL,
	...
}

GANSS-Transmission-Time-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-UTC-Model ::= SEQUENCE {
	a-one-utc							BIT STRING (SIZE (24)),
	a-zero-utc							BIT STRING (SIZE (32)),
	t-ot-utc							BIT STRING (SIZE (8)),
	w-n-t-utc							BIT STRING (SIZE (8)),
	delta-t-ls-utc						BIT STRING (SIZE (8)),
	w-n-lsf-utc							BIT STRING (SIZE (8)),
	dn-utc								BIT STRING (SIZE (8)),
	delta-t-lsf-utc						BIT STRING (SIZE (8)),
	ie-Extensions						ProtocolExtensionContainer { { GANSS-UTC-Model-ExtIEs } }	OPTIONAL,
	...
}

GANSS-UTC-Model-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-UTCmodelSet1 ::= SEQUENCE {
	utcA0				BIT STRING (SIZE(16)),
	utcA1				BIT STRING (SIZE(13)),
	utcA2				BIT STRING (SIZE(7)),
	utcDeltaTls			BIT STRING (SIZE(8)),
	utcTot				BIT STRING (SIZE(16)),
	utcWNot				BIT STRING (SIZE(13)),
	utcWNlsf			BIT STRING (SIZE(8)),
	utcDN				BIT STRING (SIZE(4)),
	utcDeltaTlsf		BIT STRING (SIZE(8)),
	ie-Extensions		ProtocolExtensionContainer { { GANSS-UTCmodelSet1-ExtIEs } }	OPTIONAL,
	...
}

GANSS-UTCmodelSet1-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-UTCmodelSet2 ::= SEQUENCE {
	nA					BIT STRING (SIZE(11)),
	tauC				BIT STRING (SIZE(32)),
	deltaUT1			GANSS-DeltaUT1													OPTIONAL,
	kp					BIT STRING (SIZE(2)) 											OPTIONAL,
	ie-Extensions		ProtocolExtensionContainer { { GANSS-UTCmodelSet2-ExtIEs } }	OPTIONAL,
	...
}

GANSS-UTCmodelSet2-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-UTCmodelSet3 ::= SEQUENCE {
	utcA1wnt			BIT STRING (SIZE(24)),
	utcA0wnt			BIT STRING (SIZE(32)),
	utcTot				BIT STRING (SIZE(8)),
	utcWNt				BIT STRING (SIZE(8)),
	utcDeltaTls			BIT STRING (SIZE(8)),
	utcWNlsf			BIT STRING (SIZE(8)),
	utcDN				BIT STRING (SIZE(8)),
	utcDeltaTlsf		BIT STRING (SIZE(8)),
	utcStandardID		BIT STRING (SIZE(3)),
	ie-Extensions		ProtocolExtensionContainer { { GANSS-UTCmodelSet3-ExtIEs } }	OPTIONAL,
	...
}

GANSS-UTCmodelSet3-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GANSS-UTCmodelSet4 ::= SEQUENCE {
	utcA0				BIT STRING (SIZE (32)),
	utcA1				BIT STRING (SIZE (24)),
	utcDeltaTls			BIT STRING (SIZE (8)),
	utcWNlsf			BIT STRING (SIZE (8)),
	utcDN				BIT STRING (SIZE (8)),
	utcDeltaTlsf		BIT STRING (SIZE (8)),
	ie-Extensions		ProtocolExtensionContainer { { GANSS-UTCmodelSet4-ExtIEs } } OPTIONAL,
	...
}

GANSS-UTCmodelSet4-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


GapLength				::= INTEGER (1..14)
-- Unit slot

GapDuration				::= INTEGER (1..144,...)
-- Unit frame

GenericTrafficCategory	::= BIT STRING (SIZE (8))

GPS-Almanac ::= SEQUENCE {
	wna-alm					BIT STRING (SIZE (8)),
	sat-info-almanac		SAT-Info-Almanac,
	sVGlobalHealth-alm		BIT STRING (SIZE (364))	OPTIONAL,
	ie-Extensions			ProtocolExtensionContainer { { GPS-Almanac-ExtIEs} }		OPTIONAL,
   ...
}

GPS-Almanac-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-SAT-Info-Almanac-ExtItem	CRITICALITY ignore		EXTENSION SAT-Info-Almanac-ExtList			PRESENCE optional}|
	{ ID id-completeAlmanacProvided		CRITICALITY ignore		EXTENSION CompleteAlmanacProvided				PRESENCE optional},
	...
}

GPS-Ionospheric-Model ::= SEQUENCE {
	alpha-zero-ionos		BIT STRING (SIZE (8)),
	alpha-one-ionos			BIT STRING (SIZE (8)),
	alpha-two-ionos			BIT STRING (SIZE (8)),
	alpha-three-ionos		BIT STRING (SIZE (8)),
	beta-zero-ionos			BIT STRING (SIZE (8)),
	beta-one-ionos			BIT STRING (SIZE (8)),
	beta-two-ionos			BIT STRING (SIZE (8)),
	beta-three-ionos		BIT STRING (SIZE (8)),
	ie-Extensions		ProtocolExtensionContainer { { GPS-Ionospheric-Model-ExtIEs} }		OPTIONAL,
	...
}

GPS-Ionospheric-Model-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GPS-Information ::= SEQUENCE (SIZE (0..maxNoGPSItems)) OF GPS-Information-Item
-- This IE shall be present if the Information Type Item IE indicates ‘GPS Information’

GPS-Information-Item ::= ENUMERATED {
	gps-navigation-model-and-time-recovery,
	gps-ionospheric-model,
	gps-utc-model,
	gps-almanac,
	gps-rt-integrity,
	...
}

GPS-RealTime-Integrity ::= CHOICE {
	bad-satellites				GPSBadSat-Info-RealTime-Integrity,
	no-bad-satellites			NULL
}

GPSBadSat-Info-RealTime-Integrity ::= SEQUENCE {
	sat-info						SATInfo-RealTime-Integrity,
	ie-Extensions					ProtocolExtensionContainer { { GPSBadSat-Info-RealTime-Integrity-ExtIEs} }		OPTIONAL,
	...
}

GPSBadSat-Info-RealTime-Integrity-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GPS-NavigationModel-and-TimeRecovery ::= SEQUENCE (SIZE (1..maxNoSat)) OF GPS-NavandRecovery-Item

GPS-NavandRecovery-Item ::= SEQUENCE {
	tx-tow-nav							INTEGER (0..1048575),
	sat-id-nav							SAT-ID,
	tlm-message-nav						BIT STRING (SIZE (14)),
	tlm-revd-c-nav						BIT STRING (SIZE (2)),
	ho-word-nav							BIT STRING (SIZE (22)),
	w-n-nav								BIT STRING (SIZE (10)),
	ca-or-p-on-l2-nav					BIT STRING (SIZE (2)),
	user-range-accuracy-index-nav		BIT STRING (SIZE (4)),
	sv-health-nav						BIT STRING (SIZE (6)),
	iodc-nav							BIT STRING (SIZE (10)),
	l2-p-dataflag-nav					BIT STRING (SIZE (1)),
	sf1-reserved-nav					BIT STRING (SIZE (87)),
	t-gd-nav							BIT STRING (SIZE (8)),
	t-oc-nav							BIT STRING (SIZE (16)),
	a-f-2-nav							BIT STRING (SIZE (8)),
	a-f-1-nav							BIT STRING (SIZE (16)),
	a-f-zero-nav						BIT STRING (SIZE (22)),
	c-rs-nav							BIT STRING (SIZE (16)),
	delta-n-nav							BIT STRING (SIZE (16)),
	m-zero-nav							BIT STRING (SIZE (32)),
	c-uc-nav							BIT STRING (SIZE (16)),
	gps-e-nav							BIT STRING (SIZE (32)),
	c-us-nav							BIT STRING (SIZE (16)),
	a-sqrt-nav							BIT STRING (SIZE (32)),
	t-oe-nav							BIT STRING (SIZE (16)),
	fit-interval-flag-nav				BIT STRING (SIZE (1)),
	aodo-nav							BIT STRING (SIZE (5)),
	c-ic-nav							BIT STRING (SIZE (16)),
	omega-zero-nav						BIT STRING (SIZE (32)),
	c-is-nav							BIT STRING (SIZE (16)),
	i-zero-nav							BIT STRING (SIZE (32)),
	c-rc-nav							BIT STRING (SIZE (16)),
	gps-omega-nav						BIT STRING (SIZE (32)),
	omegadot-nav						BIT STRING (SIZE (24)),
	idot-nav							BIT STRING (SIZE (14)),
	spare-zero-fill						BIT STRING (SIZE (20)),
	ie-Extensions						ProtocolExtensionContainer { { GPS-NavandRecovery-Item-ExtIEs} }		OPTIONAL,
	...
}

GPS-NavandRecovery-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


GPS-RX-POS ::= SEQUENCE {
	latitudeSign			ENUMERATED {north, south},
	latitude				INTEGER (0..8388607),
	longitude				INTEGER (-8388608..8388607),
	directionOfAltitude		ENUMERATED {height, depth},
	altitude				INTEGER (0..32767),
	iE-Extensions			ProtocolExtensionContainer { { GPS-RX-POS-ExtIEs} } OPTIONAL,
	...
}

GPS-RX-POS-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

GPS-Status-Health ::= ENUMERATED {
	udre-scale-1dot0,
	udre-scale-0dot75,
	udre-scale-0dot5,
	udre-scale-0dot3,
	udre-scale-0dot1,
	no-data,
	invalid-data
}

GPSTOW ::= INTEGER (0..604799)

GPS-UTC-Model ::= SEQUENCE {
	a-one-utc			BIT STRING (SIZE (24)),
	a-zero-utc			BIT STRING (SIZE (32)),
	t-ot-utc			BIT STRING (SIZE (8)),
	delta-t-ls-utc		BIT STRING (SIZE (8)),
	w-n-t-utc			BIT STRING (SIZE (8)),
	w-n-lsf-utc			BIT STRING (SIZE (8)),
	dn-utc				BIT STRING (SIZE (8)),
	delta-t-lsf-utc		BIT STRING (SIZE (8)),
	ie-Extensions		ProtocolExtensionContainer { { GPS-UTC-Model-ExtIEs} }		OPTIONAL,
	...
}

GPS-UTC-Model-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- ==========================================
--	H
-- ==========================================

HARQ-Info-for-E-DCH ::= ENUMERATED {
	rv0,
	rvtable
}

HARQ-MemoryPartitioning	::= CHOICE {
	implicit		HARQ-MemoryPartitioning-Implicit,
	explicit		HARQ-MemoryPartitioning-Explicit,
	...
	}

HARQ-MemoryPartitioning-Implicit	::= SEQUENCE {
	number-of-Processes			INTEGER (1..8,...,12|14|16),
	iE-Extensions				ProtocolExtensionContainer { { HARQ-MemoryPartitioning-Implicit-ExtIEs } }			OPTIONAL,
	...
}

HARQ-MemoryPartitioning-Implicit-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HARQ-MemoryPartitioning-Explicit	::= SEQUENCE {
	hARQ-MemoryPartitioningList			HARQ-MemoryPartitioningList,
	iE-Extensions						ProtocolExtensionContainer { { HARQ-MemoryPartitioning-Explicit-ExtIEs } }			OPTIONAL,
	...
}

HARQ-MemoryPartitioning-Explicit-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
-- The following IE may only be used in FDD, in MIMO dual stream transmission mode
	{ID id-HARQ-MemoryPartitioningInfoExtForMIMO	CRITICALITY ignore	EXTENSION HARQ-MemoryPartitioningInfoExtForMIMO	PRESENCE optional},
	...
}

HARQ-MemoryPartitioningList	::= SEQUENCE (SIZE (1..maxNrOfHARQProcesses)) OF HARQ-MemoryPartitioningItem

HARQ-MemoryPartitioningInfoExtForMIMO ::= SEQUENCE (SIZE (4|6|8)) OF HARQ-MemoryPartitioningItem

HARQ-MemoryPartitioningItem ::= SEQUENCE {
	process-Memory-Size					ENUMERATED {
										hms800, hms1600, hms2400, hms3200, hms4000,
										hms4800, hms5600, hms6400, hms7200, hms8000,
										hms8800, hms9600, hms10400, hms11200, hms12000,
										hms12800, hms13600, hms14400, hms15200, hms16000,
										hms17600, hms19200, hms20800, hms22400, hms24000,
										hms25600, hms27200, hms28800, hms30400, hms32000,
										hms36000, hms40000, hms44000, hms48000, hms52000,
										hms56000, hms60000, hms64000, hms68000, hms72000,
										hms76000, hms80000, hms88000, hms96000, hms104000,
										hms112000, hms120000, hms128000, hms136000, hms144000,
										hms152000, hms160000, hms176000, hms192000, hms208000,
										hms224000, hms240000, hms256000, hms272000, hms288000,
										hms304000,...},
	iE-Extensions						ProtocolExtensionContainer { { HARQ-MemoryPartitioningItem-ExtIEs } }			OPTIONAL,
	...
}

HARQ-MemoryPartitioningItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HARQ-Preamble-Mode ::= ENUMERATED {
mode0,
mode1
}


HARQ-Process-Allocation-2ms-EDCH ::= BIT STRING ( SIZE(maxNrOfEDCHHARQProcesses2msEDCH) )

HARQ-Preamble-Mode-Activation-Indicator	::=ENUMERATED	{
	harqPreambleModeActivated
}

HSDPA-Capability ::= ENUMERATED {hsdpa-capable, hsdpa-non-capable}

HS-DSCHProvidedBitRate ::= SEQUENCE (SIZE (1..maxNrOfPriorityClasses)) OF HS-DSCHProvidedBitRate-Item

HS-DSCHProvidedBitRate-Item ::= SEQUENCE {
	schedulingPriorityIndicator			SchedulingPriorityIndicator,
	hS-DSCHProvidedBitRateValue			HS-DSCHProvidedBitRateValue,
	iE-Extensions						ProtocolExtensionContainer { { HS-DSCHProvidedBitRate-Item-ExtIEs} }		OPTIONAL,
	...
}

HS-DSCHProvidedBitRate-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-DSCHProvidedBitRateValue ::= INTEGER(0..16777215,...,16777216..256000000)
-- except for 7.68Mcps TDD Unit bit/s, Range 0..2^24-1..2^24..256,000,000, Step 1 bit
-- 7.68Mcps TDD Unit 2bit/s, Range 0..2^24-1..2^24..256,000,000, Step 1


HS-DSCHProvidedBitRateValueInformation-For-CellPortion ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCell)) OF HS-DSCHProvidedBitRateValueInformation-For-CellPortion-Item

HS-DSCHProvidedBitRateValueInformation-For-CellPortion-Item ::= SEQUENCE{
	cellPortionID					CellPortionID,
	hS-DSCHProvidedBitRateValue		HS-DSCHProvidedBitRate,
	iE-Extensions					ProtocolExtensionContainer { {HS-DSCHProvidedBitRateValueInformation-For-CellPortion-Item-ExtIEs} }	OPTIONAL,
	...
}

HS-DSCHProvidedBitRateValueInformation-For-CellPortion-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-DSCHProvidedBitRateValueInformation-For-CellPortionLCR ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCellLCR)) OF HS-DSCHProvidedBitRateValueInformation-For-CellPortionLCR-Item

HS-DSCHProvidedBitRateValueInformation-For-CellPortionLCR-Item ::= SEQUENCE{
	cellPortionLCRID					CellPortionLCRID,
	hS-DSCHProvidedBitRateValue		HS-DSCHProvidedBitRate,
	iE-Extensions					ProtocolExtensionContainer { {HS-DSCHProvidedBitRateValueInformation-For-CellPortionLCR-Item-ExtIEs} }	OPTIONAL,
	...
}

HS-DSCHProvidedBitRateValueInformation-For-CellPortionLCR-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-DSCHRequiredPower ::= SEQUENCE (SIZE (1..maxNrOfPriorityClasses)) OF HS-DSCHRequiredPower-Item

HS-DSCHRequiredPower-Item ::= SEQUENCE {
	schedulingPriorityIndicator				SchedulingPriorityIndicator,
	hS-DSCHRequiredPowerValue				HS-DSCHRequiredPowerValue,
	hS-DSCHRequiredPowerPerUEInformation	HS-DSCHRequiredPowerPerUEInformation						OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { HS-DSCHRequiredPower-Item-ExtIEs} }		OPTIONAL,
	...
}

HS-DSCHRequiredPower-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-DSCHRequiredPowerValue ::= INTEGER(0..1000)
-- Unit %, Range 0 ..1000, Step 0.1%

HS-DSCHRequiredPowerPerUEInformation ::= SEQUENCE (SIZE (1.. maxNrOfContextsOnUeList)) OF HS-DSCHRequiredPowerPerUEInformation-Item


HS-DSCHRequiredPowerPerUEInformation-Item ::= SEQUENCE {
	cRNC-CommunicationContextID				CRNC-CommunicationContextID,
	hS-DSCHRequiredPowerPerUEWeight			HS-DSCHRequiredPowerPerUEWeight		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { HS-DSCHRequiredPowerPerUEInformation-Item-ExtIEs} }		OPTIONAL,
	...
}

HS-DSCHRequiredPowerPerUEInformation-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-DSCHRequiredPowerPerUEWeight ::= INTEGER(0..100)
-- Unit %, Range 0 ..100, Step 1%

HS-DSCHRequiredPowerValueInformation-For-CellPortion ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCell)) OF HS-DSCHRequiredPowerValueInformation-For-CellPortion-Item

HS-DSCHRequiredPowerValueInformation-For-CellPortion-Item ::= SEQUENCE{
	cellPortionID				CellPortionID,
	hS-DSCHRequiredPowerValue	HS-DSCHRequiredPower,
	iE-Extensions				ProtocolExtensionContainer { { HS-DSCHRequiredPowerValueInformation-For-CellPortion-Item-ExtIEs} }		OPTIONAL,
	...
}

HS-DSCHRequiredPowerValueInformation-For-CellPortion-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-DSCHRequiredPowerValueInformation-For-CellPortionLCR ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCellLCR)) OF HS-DSCHRequiredPowerValueInformation-For-CellPortionLCR-Item

HS-DSCHRequiredPowerValueInformation-For-CellPortionLCR-Item ::= SEQUENCE{
	cellPortionLCRID				CellPortionLCRID,
	hS-DSCHRequiredPowerValue	HS-DSCHRequiredPower,
	iE-Extensions				ProtocolExtensionContainer { { HS-DSCHRequiredPowerValueInformation-For-CellPortionLCR-Item-ExtIEs} }		OPTIONAL,
	...
}

HS-DSCHRequiredPowerValueInformation-For-CellPortionLCR-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSDPA-Associated-PICH-Information  ::= CHOICE {
	hsdpa-PICH-Shared-with-PCH						HSDPA-PICH-Shared-with-PCH,
	hsdpa-PICH-notShared-with-PCH					HSDPA-PICH-notShared-with-PCH,
	...
}

HSDPA-PICH-Shared-with-PCH ::= SEQUENCE {
	hsdpa-PICH-SharedPCH-ID							CommonPhysicalChannelID,
	...
}

HSDPA-PICH-notShared-with-PCH ::= SEQUENCE {
	hSDPA-PICH-notShared-ID							CommonPhysicalChannelID,
	fdd-DL-Channelisation-CodeNumber				FDD-DL-ChannelisationCodeNumber,
	pich-Power										PICH-Power,
	pich-Mode										PICH-Mode,
	sttd-Indicator									STTD-Indicator,
	...
}

HSDSCH-Common-System-InformationFDD  ::= SEQUENCE {
	hsdsch-Common-Information						HSDSCH-Common-Information								OPTIONAL,
	commonMACFlow-Specific-Information				CommonMACFlow-Specific-InfoList							OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-Common-System-InformationFDD-ExtIEs } }		OPTIONAL,
	...
}

HSDSCH-Common-System-InformationFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Common-HSDSCH-RNTI-List	CRITICALITY ignore		EXTENSION	Common-HSDSCH-RNTI-List		PRESENCE optional},
	...
}

HSDSCH-Common-System-Information-ResponseFDD  ::= SEQUENCE {
	hsSCCH-Specific-Information-ResponseFDD			HSSCCH-Specific-InformationRespListFDD				OPTIONAL,
	hARQ-MemoryPartitioning							HARQ-MemoryPartitioning								OPTIONAL, 
	commonMACFlow-Specific-Info-Response			CommonMACFlow-Specific-InfoList-Response			OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-Common-System-Information-ResponseFDD-ExtIEs } }		OPTIONAL,
	...
}

HSDSCH-Common-System-Information-ResponseFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSDSCH-Common-Information ::= SEQUENCE {
	cCCH-PriorityQueue-Id											PriorityQueue-Id,
	sRB1-PriorityQueue-Id											PriorityQueue-Id,
	associatedCommon-MACFlow										Common-MACFlow-ID,
	fACH-Measurement-Occasion-Cycle-Length-Coefficient				FACH-Measurement-Occasion-Cycle-Length-Coefficient				OPTIONAL,
	rACH-Measurement-Result											RACH-Measurement-Result,
	bCCH-Specific-HSDSCH-RNTI-Information							BCCH-Specific-HSDSCH-RNTI-Information,
	iE-Extensions						ProtocolExtensionContainer { { HSDSCH-Common-Information-ExtIEs} }		OPTIONAL,
	...
}

HSDSCH-Common-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSDSCH-FDD-Information ::= SEQUENCE {
	hSDSCH-MACdFlows-Information				HSDSCH-MACdFlows-Information,
	ueCapability-Info							UE-Capability-Information,
	mAChs-Reordering-Buffer-Size-for-RLC-UM		MAChsReorderingBufferSize-for-RLC-UM,
	cqiFeedback-CycleK							CQI-Feedback-Cycle,
	cqiRepetitionFactor							CQI-RepetitionFactor						OPTIONAL,
	-- This IE shall be present if the CQI Feedback Cycle k is greater than 0
	ackNackRepetitionFactor						AckNack-RepetitionFactor,
	cqiPowerOffset								CQI-Power-Offset,
	ackPowerOffset								Ack-Power-Offset,
	nackPowerOffset								Nack-Power-Offset,
	hsscch-PowerOffset							HSSCCH-PowerOffset							OPTIONAL,
	measurement-Power-Offset					Measurement-Power-Offset					OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { HSDSCH-FDD-Information-ExtIEs} }		OPTIONAL,
	...
}

HSDSCH-FDD-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-HARQ-Preamble-Mode 							CRITICALITY ignore	EXTENSION HARQ-Preamble-Mode							PRESENCE optional}|
	{ ID id-MIMO-ActivationIndicator					CRITICALITY reject	EXTENSION MIMO-ActivationIndicator					PRESENCE optional}|
	{ ID id-HSDSCH-MACdPDUSizeFormat 					CRITICALITY reject	EXTENSION HSDSCH-MACdPDUSizeFormat					PRESENCE optional}|
	{ ID id-SixtyfourQAM-UsageAllowedIndicator			CRITICALITY ignore	EXTENSION SixtyfourQAM-UsageAllowedIndicator		PRESENCE optional}|
	{ ID id-UE-with-enhanced-HS-SCCH-support-indicator	CRITICALITY ignore	EXTENSION NULL												PRESENCE optional}|
	{ ID id-EnhancedHSServingCC-Abort					CRITICALITY reject	EXTENSION EnhancedHSServingCC-Abort					PRESENCE optional}|
	{ ID id-UE-SupportIndicatorExtension				CRITICALITY ignore	EXTENSION UE-SupportIndicatorExtension				PRESENCE optional}|
	{ ID id-Single-Stream-MIMO-ActivationIndicator		CRITICALITY reject	EXTENSION Single-Stream-MIMO-ActivationIndicator	PRESENCE optional}|
	{ ID id-Puncturing-Handling-in-First-Rate-Matching-Stage	CRITICALITY ignore	EXTENSION Puncturing-Handling-in-First-Rate-Matching-Stage	PRESENCE optional}|
	{ ID id-MIMO-withfourtransmitantennas-ActivationIndicator	CRITICALITY reject	EXTENSION MIMO-withfourtransmitantennas-ActivationIndicator			PRESENCE optional}|
	{ ID id-DualStream-MIMO-withfourtransmitantennas-ActivationIndicator	CRITICALITY reject	EXTENSION DualStream-MIMO-withfourtransmitantennas-ActivationIndicator		PRESENCE optional}|
	{ ID id-Multiflow-Information						CRITICALITY reject	EXTENSION Multiflow-Information						PRESENCE optional}|
	{ ID id-CQI-Feedback-Cycle2							CRITICALITY ignore	EXTENSION CQI-Feedback-Cycle2							PRESENCE optional}|
	{ ID id-CQI-Cycle-Switch-Timer						CRITICALITY ignore	EXTENSION CQI-Cycle-Switch-Timer						PRESENCE optional},
	...
}

HSDSCH-TDD-Information ::= SEQUENCE {
	hSDSCH-MACdFlows-Information				HSDSCH-MACdFlows-Information,
	ueCapability-Info							UE-Capability-Information,
	mAChs-Reordering-Buffer-Size-for-RLC-UM		MAChsReorderingBufferSize-for-RLC-UM,
	tDD-AckNack-Power-Offset					TDD-AckNack-Power-Offset,
	iE-Extensions								ProtocolExtensionContainer { { HSDSCH-TDD-Information-ExtIEs} }		OPTIONAL,
	...
}

HSDSCH-TDD-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-HSSICH-SIRTarget		CRITICALITY	ignore			EXTENSION 	UL-SIR 					PRESENCE 	optional}|
 -- Applicable to 1.28Mcps TDD only
	{ ID id-HSSICH-TPC-StepSize		CRITICALITY	ignore			EXTENSION 	TDD-TPC-UplinkStepSize-LCR	PRESENCE 	optional}|
	 -- Applicable to 1.28Mcps TDD only
	{ ID id-HSDSCH-MACdPDUSizeFormat 	CRITICALITY reject		EXTENSION	HSDSCH-MACdPDUSizeFormat 	PRESENCE optional}|
	{ ID id-tSN-Length				CRITICALITY reject			EXTENSION  TSN-Length				PRESENCE optional }|
	-- Applicable for 1.28Mcps TDD when using multiple frequencies
		{ ID id-MIMO-ActivationIndicator				CRITICALITY reject		EXTENSION	MIMO-ActivationIndicator				PRESENCE optional},
...
}


HSDSCH-Information-to-Modify ::= SEQUENCE {
	hsDSCH-MACdFlow-Specific-Info-to-Modify			HSDSCH-MACdFlow-Specific-InfoList-to-Modify		OPTIONAL,
	priorityQueueInfotoModify						PriorityQueue-InfoList-to-Modify				OPTIONAL,
	mAChs-Reordering-Buffer-Size-for-RLC-UM			MAChsReorderingBufferSize-for-RLC-UM			OPTIONAL,
	cqiFeedback-CycleK								CQI-Feedback-Cycle								OPTIONAL,	-- For FDD only
	cqiRepetitionFactor								CQI-RepetitionFactor							OPTIONAL,	-- For FDD only
	ackNackRepetitionFactor							AckNack-RepetitionFactor						OPTIONAL,	-- For FDD only
	cqiPowerOffset									CQI-Power-Offset								OPTIONAL,	-- For FDD only
	ackPowerOffset									Ack-Power-Offset								OPTIONAL,	-- For FDD only
	nackPowerOffset									Nack-Power-Offset								OPTIONAL,	-- For FDD only
	hsscch-PowerOffset								HSSCCH-PowerOffset								OPTIONAL,	-- For FDD only
	measurement-Power-Offset						Measurement-Power-Offset						OPTIONAL,	-- For FDD only
	hSSCCHCodeChangeGrant							HSSCCH-Code-Change-Grant						OPTIONAL,
	tDDAckNackPowerOffset							TDD-AckNack-Power-Offset						OPTIONAL,	-- For TDD only
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-Information-to-Modify-ExtIEs} }		OPTIONAL,
	...
}

HSDSCH-Information-to-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-HARQ-Preamble-Mode						CRITICALITY ignore	EXTENSION HARQ-Preamble-Mode							PRESENCE optional}|
	{ ID id-HSSICH-SIRTarget						CRITICALITY ignore	EXTENSION UL-SIR										PRESENCE optional}|
	 -- Applicable to 1.28Mcps TDD only
	{ ID id-ueCapability-Info						CRITICALITY ignore	EXTENSION UE-Capability-Information				PRESENCE optional}|
	{ ID id-HSSICH-TPC-StepSize						CRITICALITY ignore	EXTENSION TDD-TPC-UplinkStepSize-LCR				PRESENCE optional}|
	 -- Applicable to 1.28Mcps TDD only
	{ ID id-HS-PDSCH-Code-Change-Grant				CRITICALITY ignore	EXTENSION HS-PDSCH-Code-Change-Grant				PRESENCE optional}|
	 -- Applicable to FDD only
	{ ID id-MIMO-Mode-Indicator						CRITICALITY reject	EXTENSION MIMO-Mode-Indicator						PRESENCE optional}|
	{ ID id-HSDSCH-MACdPDUSizeFormat				CRITICALITY reject	EXTENSION HSDSCH-MACdPDUSizeFormat 				PRESENCE optional}|
	{ ID id-SixtyfourQAM-UsageAllowedIndicator		CRITICALITY ignore	EXTENSION SixtyfourQAM-UsageAllowedIndicator	PRESENCE optional}|
	{ ID id-EnhancedHSServingCC-Abort				CRITICALITY reject	EXTENSION EnhancedHSServingCC-Abort				PRESENCE optional}|
	{ ID id-UE-SupportIndicatorExtension			CRITICALITY ignore	EXTENSION UE-SupportIndicatorExtension			PRESENCE optional}|
	{ ID id-Single-Stream-MIMO-Mode-Indicator		CRITICALITY reject	EXTENSION Single-Stream-MIMO-Mode-Indicator		PRESENCE optional}|
	{ ID id-Puncturing-Handling-in-First-Rate-Matching-Stage	CRITICALITY ignore	EXTENSION Puncturing-Handling-in-First-Rate-Matching-Stage	PRESENCE optional}|
	{ ID id-MIMO-withfourtransmitantennas-Mode-Indicator	CRITICALITY reject	EXTENSION MIMO-withfourtransmitantennas-Mode-Indicator	PRESENCE optional}|
	{ ID id-DualStream-MIMO-withfourtransmitantennas-Mode-Indicator		CRITICALITY reject	EXTENSION DualStream-MIMO-withfourtransmitantennas-Mode-Indicator	PRESENCE optional}|
	{ ID id-Multiflow-Reconfiguration				CRITICALITY reject	EXTENSION Multiflow-Reconfiguration				PRESENCE optional}|
	 -- Applicable to FDD only
	{ ID id-CQI-Feedback-Cycle2						CRITICALITY ignore	EXTENSION CQI-Feedback-Cycle2						PRESENCE optional}|
	{ ID id-CQI-Cycle-Switch-Timer					CRITICALITY ignore	EXTENSION CQI-Cycle-Switch-Timer					PRESENCE optional},
	...
}

HSDSCH-MACdFlow-Specific-InfoList-to-Modify ::= SEQUENCE (SIZE (1..maxNrOfMACdFlows)) OF HSDSCH-MACdFlow-Specific-InfoItem-to-Modify

HSDSCH-MACdFlow-Specific-InfoItem-to-Modify ::= SEQUENCE {
	hsDSCH-MACdFlow-ID					HSDSCH-MACdFlow-ID,
	allocationRetentionPriority			AllocationRetentionPriority					OPTIONAL,
	transportBearerRequestIndicator		TransportBearerRequestIndicator,
	bindingID							BindingID									OPTIONAL,
	transportLayerAddress				TransportLayerAddress						OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { HSDSCH-MACdFlow-Specific-InfoItem-to-Modify-ExtIEs} }		OPTIONAL,
	...
}

HSDSCH-MACdFlow-Specific-InfoItem-to-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID	id-TnlQos			CRITICALITY ignore		EXTENSION TnlQos	PRESENCE optional},
	...
}

HSDSCH-MACdPDUSizeFormat ::= ENUMERATED {
	indexedMACdPDU-Size,
	flexibleMACdPDU-Size
}

HSDSCH-MACdPDU-SizeCapability ::= ENUMERATED {
	indexedSizeCapable,
	flexibleSizeCapable
}

HSDSCH-Information-to-Modify-Unsynchronised ::= SEQUENCE {
	hsDSCH-MACdFlow-Specific-Info-to-Modify			HSDSCH-MACdFlow-Specific-InfoList-to-Modify		OPTIONAL,
	priorityQueueInfotoModifyUnsynchronised			PriorityQueue-InfoList-to-Modify-Unsynchronised	OPTIONAL,
	cqiPowerOffset									CQI-Power-Offset								OPTIONAL,	-- For FDD only
	ackPowerOffset									Ack-Power-Offset								OPTIONAL,	-- For FDD only
	nackPowerOffset									Nack-Power-Offset								OPTIONAL,	-- For FDD only
	hsscch-PowerOffset								HSSCCH-PowerOffset								OPTIONAL,	-- For FDD only
	tDDAckNackPowerOffset							TDD-AckNack-Power-Offset						OPTIONAL,	-- For TDD only
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-Information-to-Modify-Unsynchronised-ExtIEs} }		OPTIONAL,
	...
}

HSDSCH-Information-to-Modify-Unsynchronised-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-HARQ-Preamble-Mode						CRITICALITY ignore	EXTENSION HARQ-Preamble-Mode								PRESENCE optional}|
	{ ID id-HSSICH-SIRTarget						CRITICALITY ignore	EXTENSION UL-SIR											PRESENCE optional}|
	 -- Applicable to 1.28Mcps TDD only
	{ ID id-ueCapability-Info						CRITICALITY ignore	EXTENSION UE-Capability-Information					PRESENCE optional}|
	{ ID id-HSSICH-TPC-StepSize						CRITICALITY ignore	EXTENSION TDD-TPC-UplinkStepSize-LCR					PRESENCE optional}|
	 -- Applicable to 1.28Mcps TDD only
	{ ID id-MIMO-Mode-Indicator						CRITICALITY reject	EXTENSION MIMO-Mode-Indicator							PRESENCE	optional}|
	{ ID id-SixtyfourQAM-UsageAllowedIndicator		CRITICALITY ignore	EXTENSION SixtyfourQAM-UsageAllowedIndicator		PRESENCE optional}|
	{ ID id-EnhancedHSServingCC-Abort				CRITICALITY reject	EXTENSION EnhancedHSServingCC-Abort					PRESENCE optional}|
	{ ID id-UE-SupportIndicatorExtension			CRITICALITY ignore	EXTENSION UE-SupportIndicatorExtension				PRESENCE optional}|
	{ ID id-Single-Stream-MIMO-Mode-Indicator		CRITICALITY reject	EXTENSION Single-Stream-MIMO-Mode-Indicator			PRESENCE optional}|
	{ ID id-Puncturing-Handling-in-First-Rate-Matching-Stage	CRITICALITY ignore	EXTENSION Puncturing-Handling-in-First-Rate-Matching-Stage	PRESENCE optional}|
	{ ID id-MIMO-withfourtransmitantennas-Mode-Indicator		CRITICALITY reject	EXTENSION MIMO-withfourtransmitantennas-Mode-Indicator		PRESENCE optional}|
	{ ID id-DualStream-MIMO-withfourtransmitantennas-Mode-Indicator		CRITICALITY reject	EXTENSION DualStream-MIMO-withfourtransmitantennas-Mode-Indicator	PRESENCE optional}|
	{ ID id-Multiflow-Reconfiguration				CRITICALITY reject	EXTENSION Multiflow-Reconfiguration					PRESENCE optional},
	 -- Applicable to FDD only
	...
}

HSDSCH-FDD-Information-Response ::= SEQUENCE {
	hsDSCH-MACdFlow-Specific-InformationResp		HSDSCH-MACdFlow-Specific-InformationResp							OPTIONAL,
	hsSCCH-Specific-Information-ResponseFDD			HSSCCH-Specific-InformationRespListFDD								OPTIONAL,
	hARQ-MemoryPartitioning							HARQ-MemoryPartitioning												OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-FDD-Information-Response-ExtIEs } }		OPTIONAL,
	...
}

HSDSCH-FDD-Information-Response-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-HARQ-Preamble-Mode-Activation-Indicator		CRITICALITY ignore	EXTENSION HARQ-Preamble-Mode-Activation-Indicator	PRESENCE optional}|
	{ ID id-MIMO-N-M-Ratio								CRITICALITY ignore	EXTENSION MIMO-N-M-Ratio										PRESENCE optional}|
	{ ID id-SixtyfourQAM-DL-UsageIndicator				CRITICALITY ignore	EXTENSION SixtyfourQAM-DL-UsageIndicator				PRESENCE optional}|
	{ ID id-HSDSCH-TBSizeTableIndicator					CRITICALITY ignore	EXTENSION HSDSCH-TBSizeTableIndicator					PRESENCE optional}|
	{ ID id-Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order		CRITICALITY ignore	EXTENSION Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order		PRESENCE optional}|
	{ ID id-PrecoderWeightSetRestriction				CRITICALITY ignore	EXTENSION Precoder-Weight-Set-Restriction				PRESENCE optional},
	...
}

HS-DSCH-FDD-Secondary-Serving-Information ::= SEQUENCE {
	hsscch-PowerOffset						HSSCCH-PowerOffset							OPTIONAL,
	measurement-Power-Offset				Measurement-Power-Offset,
	sixtyfourQAM-UsageAllowedIndicator		SixtyfourQAM-UsageAllowedIndicator			OPTIONAL,
	hSDSCH-RNTI								HSDSCH-RNTI,
	iE-Extensions							ProtocolExtensionContainer { { HS-DSCH-FDD-Secondary-Serving-Information-ExtIEs } }		OPTIONAL,
	...
}

HS-DSCH-FDD-Secondary-Serving-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-MIMO-ActivationIndicator					CRITICALITY reject	EXTENSION MIMO-ActivationIndicator							PRESENCE optional}|
	{ID id-Single-Stream-MIMO-ActivationIndicator	CRITICALITY reject	EXTENSION Single-Stream-MIMO-ActivationIndicator		PRESENCE optional}|
	{ID id-DiversityMode							CRITICALITY reject	EXTENSION DiversityMode											PRESENCE optional}|
	{ID id-TransmitDiversityIndicator				CRITICALITY reject	EXTENSION TransmitDiversityIndicator						PRESENCE optional}|
	{ID id-OrdinalNumberOfFrequency					CRITICALITY reject	EXTENSION OrdinalNumberOfFrequency							PRESENCE optional}|
	{ ID id-MIMO-withfourtransmitantennas-ActivationIndicator	CRITICALITY reject	EXTENSION MIMO-withfourtransmitantennas-ActivationIndicator			PRESENCE optional}|
	{ ID id-DualStream-MIMO-withfourtransmitantennas-ActivationIndicator	CRITICALITY reject	EXTENSION DualStream-MIMO-withfourtransmitantennas-ActivationIndicator		PRESENCE optional}|
	{ID id-Multiflow-OrdinalNumberOfFrequency		CRITICALITY reject	EXTENSION Multiflow-OrdinalNumberOfFrequency			PRESENCE optional},
	...
}

HS-DSCH-FDD-Secondary-Serving-Information-Response ::= SEQUENCE {
	hsSCCH-Specific-Information-ResponseFDD		HSSCCH-Specific-InformationRespListFDD					OPTIONAL,
	sixtyfourQAM-DL-UsageIndicator				SixtyfourQAM-DL-UsageIndicator							OPTIONAL,
	hSDSCH-TBSizeTableIndicator					HSDSCH-TBSizeTableIndicator								OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { HS-DSCH-FDD-Secondary-Serving-Information-Respons-ExtIEs } }			OPTIONAL,
	...
}

HS-DSCH-first-DRX-ycle-FACH ::= ENUMERATED {v2, v4, v8, v16, v32, v64}

HS-DSCH-first-Rx-burst-FACH ::= ENUMERATED { v0dot4, v0dot8}

HS-DSCH-FDD-Secondary-Serving-Information-Respons-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-MIMO-N-M-Ratio						CRITICALITY ignore	EXTENSION MIMO-N-M-Ratio							PRESENCE optional}|
	{ID id-PrecoderWeightSetRestriction			CRITICALITY ignore	EXTENSION Precoder-Weight-Set-Restriction		PRESENCE optional},
	...
}

HS-DSCH-Second-DRX-Cycle-FACH ::= ENUMERATED { v4, v8, v16, v32, v64, v128, v256, v512}

HS-DSCH-second-Rx-burst-FACH ::= ENUMERATED {v1,v2}

HS-DSCH-Secondary-Serving-Information-To-Modify ::= SEQUENCE {
	hsscch-PowerOffset							HSSCCH-PowerOffset									OPTIONAL,
	measurement-Power-Offset					Measurement-Power-Offset							OPTIONAL,
	hSSCCH-CodeChangeGrant						HSSCCH-Code-Change-Grant							OPTIONAL,
	sixtyfourQAM-UsageAllowedIndicator			SixtyfourQAM-UsageAllowedIndicator					OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { HS-DSCH-Secondary-Serving-Information-To-Modify-ExtIEs } }		OPTIONAL,
	...
}

HS-DSCH-Secondary-Serving-Information-To-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-MIMO-Mode-Indicator					CRITICALITY reject	EXTENSION MIMO-Mode-Indicator								PRESENCE optional}|
	{ID id-Single-Stream-MIMO-Mode-Indicator	CRITICALITY reject	EXTENSION Single-Stream-MIMO-Mode-Indicator			PRESENCE optional}|
	{ID id-DiversityMode						CRITICALITY reject	EXTENSION DiversityMode										PRESENCE optional}|
	{ID id-TransmitDiversityIndicator			CRITICALITY reject	EXTENSION TransmitDiversityIndicator					PRESENCE optional}|
-- This IE shall be present if Diversity Mode IE is present and is not set to “none”
	{ID id-NonCellSpecificTxDiversity			CRITICALITY reject	EXTENSION NonCellSpecificTxDiversity					PRESENCE optional}|
	{ID id-OrdinalNumberOfFrequency				CRITICALITY reject	EXTENSION OrdinalNumberOfFrequency						PRESENCE optional}|
	{ID id-MIMO-withfourtransmitantennas-Mode-Indicator		CRITICALITY reject	EXTENSION MIMO-withfourtransmitantennas-Mode-Indicator	PRESENCE optional}|
	{ID id-DualStream-MIMO-withfourtransmitantennas-Mode-Indicator		CRITICALITY reject	EXTENSION DualStream-MIMO-withfourtransmitantennas-Mode-Indicator	PRESENCE optional}|
	{ID id-Multiflow-OrdinalNumberOfFrequency	CRITICALITY reject	EXTENSION Multiflow-OrdinalNumberOfFrequency			PRESENCE optional},
	...
}

HS-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised ::= SEQUENCE {
	hsscch-PowerOffset							HSSCCH-PowerOffset									OPTIONAL,
	sixtyfourQAM-UsageAllowedIndicator			SixtyfourQAM-UsageAllowedIndicator					OPTIONAL,
	iE-Extensions			ProtocolExtensionContainer { { HS-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised-ExtIEs } }			OPTIONAL,
	...
}

HS-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID	id-MIMO-Mode-Indicator								CRITICALITY reject	EXTENSION MIMO-Mode-Indicator							PRESENCE optional}|
	{ID id-Single-Stream-MIMO-Mode-Indicator				CRITICALITY reject	EXTENSION Single-Stream-MIMO-Mode-Indicator		PRESENCE optional}|
	{ID	id-OrdinalNumberOfFrequency							CRITICALITY reject	EXTENSION OrdinalNumberOfFrequency					PRESENCE optional}|
	{ID id-MIMO-withfourtransmitantennas-Mode-Indicator		CRITICALITY reject	EXTENSION MIMO-withfourtransmitantennas-Mode-Indicator	PRESENCE optional}|
	{ID id-DualStream-MIMO-withfourtransmitantennas-Mode-Indicator	CRITICALITY reject	EXTENSION DualStream-MIMO-withfourtransmitantennas-Mode-Indicator		PRESENCE optional}|
	{ID id-Multiflow-OrdinalNumberOfFrequency				CRITICALITY reject	EXTENSION Multiflow-OrdinalNumberOfFrequency		PRESENCE optional},
	...
}

HS-DSCH-FDD-Secondary-Serving-Update-Information ::= SEQUENCE {
	hsSCCHCodeChangeIndicator					HSSCCH-CodeChangeIndicator					OPTIONAL,
	hS-PDSCH-Code-Change-Indicator				HS-PDSCH-Code-Change-Indicator				OPTIONAL,
	-- This IE shall never be included. If received it shall be ignored.
	iE-Extensions								ProtocolExtensionContainer { { HS-DSCH-FDD-Secondary-Serving-Update-Information-ExtIEs } }		OPTIONAL,
	...
}

HS-DSCH-FDD-Secondary-Serving-Update-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-PrecoderWeightSetRestriction			CRITICALITY ignore	EXTENSION Precoder-Weight-Set-Restriction		PRESENCE optional},
	...
}

HS-DSCH-Secondary-Serving-Cell-Change-Information-Response ::= SEQUENCE {
	hS-DSCH-Secondary-Serving-cell-choice		HS-DSCH-Secondary-Serving-cell-change-choice,
	iE-Extensions								ProtocolExtensionContainer { { HS-DSCH-Secondary-Serving-Cell-Change-Information-Response-ExtIEs } }		OPTIONAL,
	...
}

HS-DSCH-Secondary-Serving-Cell-Change-Information-Response-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-DSCH-Secondary-Serving-cell-change-choice ::= CHOICE {
	hS-Secondary-Serving-cell-change-successful			HS-Secondary-Serving-cell-change-successful,
	hS-Secondary-Serving-cell-change-unsuccessful		HS-Secondary-Serving-cell-change-unsuccessful,
	...
}

HS-Secondary-Serving-cell-change-successful ::= SEQUENCE {
	hS-DSCH-FDD-Secondary-Serving-Information-Response		HS-DSCH-FDD-Secondary-Serving-Information-Response,
	iE-Extensions						ProtocolExtensionContainer { { HS-Secondary-Serving-cell-change-successful-ExtIEs} } OPTIONAL,
	...
}

HS-Secondary-Serving-cell-change-successful-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-Secondary-Serving-cell-change-unsuccessful ::= SEQUENCE {
	cause							Cause,
	iE-Extensions					ProtocolExtensionContainer { { HS-Secondary-Serving-cell-change-unsuccessful-ExtIEs} } OPTIONAL,
	...
}

HS-Secondary-Serving-cell-change-unsuccessful-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}
HS-DSCH-Secondary-Serving-Remove ::= NULL


HSDSCH-Paging-System-InformationFDD  ::= SEQUENCE {
	paging-MACFlow-Specific-Information				Paging-MACFlow-Specific-Information,
	hSSCCH-Power									DL-Power,
	hSPDSCH-Power									DL-Power, 
	number-of-PCCH-transmission						Number-of-PCCH-transmission,
	transport-Block-Size-List						Transport-Block-Size-List,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-Paging-System-InformationFDD-ExtIEs } }		OPTIONAL,
	...
}

HSDSCH-Paging-System-InformationFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSDSCH-Paging-System-Information-ResponseFDD ::= SEQUENCE (SIZE (1..maxNrOfPagingMACFlow)) OF HSDSCH-Paging-System-Information-ResponseList

HSDSCH-Paging-System-Information-ResponseList  ::= SEQUENCE {
	pagingMACFlow-ID								Paging-MACFlow-ID, 
	bindingID										BindingID									OPTIONAL,
	transportLayerAddress							TransportLayerAddress						OPTIONAL, 
	hSPDSCH-Code-Index								HSPDSCH-Code-Index,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-Paging-System-Information-ResponseList-ExtIEs } }		OPTIONAL,
	...
}

HSDSCH-Paging-System-Information-ResponseList-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSDSCH-TDD-Information-Response ::= SEQUENCE {
	hsDSCH-MACdFlow-Specific-InformationResp		HSDSCH-MACdFlow-Specific-InformationResp	OPTIONAL,
	hsSCCH-Specific-Information-ResponseTDD			HSSCCH-Specific-InformationRespListTDD		OPTIONAL, -- Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD
	hsSCCH-Specific-Information-ResponseTDDLCR		HSSCCH-Specific-InformationRespListTDDLCR	OPTIONAL, -- Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD,This HSSCCH Specific Information is for the first Frequency repetition, HSSCCH Specific Information for Frequency repetitions 2 and on, should be defined in MultipleFreq-HSPDSCH-InformationList-ResponseTDDLCR
	hARQ-MemoryPartitioning							HARQ-MemoryPartitioning						OPTIONAL, -- This HARQ Memory Partitioning Information is for the first Frequency repetition, HARQ Memory Partitioning Information for Frequency repetitions 2 and on, should be defined in MultipleFreq-HSPDSCH-InformationList-ResponseTDDLCR
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-TDD-Information-Response-ExtIEs } }		OPTIONAL,
	...
}

HSDSCH-TDD-Information-Response-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-hsSCCH-Specific-Information-ResponseTDD768 					CRITICALITY ignore	EXTENSION HSSCCH-Specific-InformationRespListTDD768	PRESENCE optional}|
{ ID id-UARFCNforNt														CRITICALITY ignore	EXTENSION UARFCN																PRESENCE optional}|
	-- Applicable to 1.28Mcps TDD when using multiple frequencies ,This is the UARFCN for the first Frequency repetition
{ ID id-multipleFreq-HSPDSCH-InformationList-ResponseTDDLCR				CRITICALITY ignore	EXTENSION MultipleFreq-HSPDSCH-InformationList-ResponseTDDLCR	PRESENCE optional }|
	-- Applicable to 1.28Mcps TDD when using multiple frequencies ,This MultipleFreq-HSPDSCH-InformationList-ResponseTDDLCR is the HS-SCCH and HARQ Memory Partitioning information for the 2nd and beyond HS-PDSCH frequencies.
{ ID id-multicarrier-number												CRITICALITY ignore	EXTENSION  Multicarrier-Number													PRESENCE optional }|
	-- Applicable for 1.28Mcps TDD when using multiple frequencies
	{ID id-MIMO-SFMode-For-HSPDSCHDualStream			CRITICALITY reject		EXTENSION MIMO-SFMode-For-HSPDSCHDualStream							PRESENCE optional}|	
	{ID id-MIMO-ReferenceSignal-InformationListLCR		CRITICALITY reject	EXTENSION MIMO-ReferenceSignal-InformationListLCR		PRESENCE optional},
	...
}

HSDSCH-MACdFlow-Specific-InformationResp ::= SEQUENCE (SIZE (1..maxNrOfMACdFlows)) OF HSDSCH-MACdFlow-Specific-InformationResp-Item

HSDSCH-MACdFlow-Specific-InformationResp-Item ::= SEQUENCE {
	hsDSCHMacdFlow-Id								HSDSCH-MACdFlow-ID,
	bindingID										BindingID					OPTIONAL,
	transportLayerAddress							TransportLayerAddress		OPTIONAL,
	hSDSCH-Initial-Capacity-Allocation				HSDSCH-Initial-Capacity-Allocation OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-MACdFlow-Specific-InformationRespItem-ExtIEs } }		OPTIONAL,
	...
}

HSDSCH-MACdFlow-Specific-InformationRespItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSDSCH-MACdFlows-Information ::= SEQUENCE {
	hSDSCH-MACdFlow-Specific-Info					HSDSCH-MACdFlow-Specific-InfoList,
	priorityQueue-Info								PriorityQueue-InfoList,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-MACdFlows-Information-ExtIEs } }			OPTIONAL,
	...
}

HSDSCH-MACdFlows-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSDSCH-MACdFlow-Specific-InfoList ::= SEQUENCE (SIZE (1..maxNrOfMACdFlows)) OF HSDSCH-MACdFlow-Specific-InfoItem

HSDSCH-MACdFlow-Specific-InfoItem ::= SEQUENCE {
	hsDSCH-MACdFlow-ID					HSDSCH-MACdFlow-ID,
	allocationRetentionPriority			AllocationRetentionPriority,
	bindingID							BindingID					OPTIONAL,
	transportLayerAddress				TransportLayerAddress		OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { HSDSCH-MACdFlow-Specific-InfoItem-ExtIEs} }		OPTIONAL,
	...
}

HSDSCH-MACdFlow-Specific-InfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID	id-TnlQos			CRITICALITY ignore		EXTENSION TnlQos	PRESENCE optional },
	...
}

HSDSCH-MACdFlows-to-Delete ::= SEQUENCE (SIZE (1..maxNrOfMACdFlows)) OF HSDSCH-MACdFlows-to-Delete-Item

HSDSCH-MACdFlows-to-Delete-Item ::= SEQUENCE {
	hsDSCH-MACdFlow-ID					HSDSCH-MACdFlow-ID,
	iE-Extensions						ProtocolExtensionContainer { { HSDSCH-MACdFlows-to-Delete-Item-ExtIEs} }		OPTIONAL,
	...
}

HSDSCH-MACdFlows-to-Delete-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSDSCH-TBSizeTableIndicator ::= ENUMERATED {
	octet-aligned
}

HSSCCH-PowerOffset ::= INTEGER (0..255)
-- PowerOffset = -32 + offset * 0.25
-- Unit dB, Range -32dB .. +31.75dB, Step +0.25dB

HSDSCH-Initial-Capacity-Allocation::= SEQUENCE (SIZE (1..maxNrOfPriorityQueues)) OF HSDSCH-Initial-Capacity-AllocationItem

HSDSCH-Initial-Capacity-AllocationItem ::= SEQUENCE {
	schedulingPriorityIndicator		SchedulingPriorityIndicator,
	maximum-MACdPDU-Size			MACdPDU-Size,
	hSDSCH-InitialWindowSize		HSDSCH-InitialWindowSize,
	iE-Extensions					ProtocolExtensionContainer { { HSDSCH-Initial-Capacity-AllocationItem-ExtIEs } } OPTIONAL,
	...
}

HSDSCH-Initial-Capacity-AllocationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MaximumMACdPDU-SizeExtended 	CRITICALITY ignore		EXTENSION	MAC-PDU-SizeExtended	PRESENCE optional},
	...
}

HSDSCH-InitialWindowSize			::= INTEGER (1..255)
-- Number of MAC-d PDUs.


HSDSCH-PreconfigurationInfo ::= SEQUENCE {
	setsOfHS-SCCH-Codes		SetsOfHS-SCCH-Codes,
	hARQ-MemoryPartitioning		HARQ-MemoryPartitioning,
	e-DCH-FDD-DL-Control-Channel-Information		E-DCH-FDD-DL-Control-Channel-Information		OPTIONAL,
	hARQ-Preamble-Mode-Activation-Indicator		HARQ-Preamble-Mode-Activation-Indicator		OPTIONAL,
	mIMO-N-M-Ratio			MIMO-N-M-Ratio		OPTIONAL,
	continuousPacketConnectivityHS-SCCH-less-Information-Response	ContinuousPacketConnectivityHS-SCCH-less-Information-Response		OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { HSDSCH-PreconfigurationInfo-ExtIEs} }		OPTIONAL,
	...
}

HSDSCH-PreconfigurationInfo-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Additional-EDCH-Preconfiguration-Information		CRITICALITY ignore	EXTENSION Additional-EDCH-Preconfiguration-Information		PRESENCE optional}|
	{ ID id-Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order		CRITICALITY ignore	EXTENSION Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order		PRESENCE optional},
	...
}

Additional-EDCH-Preconfiguration-Information	::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-Preconfiguration-Information-ItemIEs

Additional-EDCH-Preconfiguration-Information-ItemIEs	::= SEQUENCE {
	e-DCH-FDD-DL-Control-Channel-Information		E-DCH-FDD-DL-Control-Channel-Information,
	iE-Extensions					ProtocolExtensionContainer { { Additional-EDCH-Preconfiguration-Information-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Additional-EDCH-Preconfiguration-Information-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSDSCH-PreconfigurationSetup ::= SEQUENCE {
	mAChsResetScheme		MAChsResetScheme,
	hSDSCH-Physical-Layer-Category		INTEGER (1..64,...),
	mAChs-Reordering-Buffer-Size-for-RLC-UM		MAChsReorderingBufferSize-for-RLC-UM,
	secondaryServingCells		SecondaryServingCells			OPTIONAL,
	numPrimaryHS-SCCH-Codes		NumHS-SCCH-Codes			OPTIONAL,
	hARQ-Preamble-Mode		HARQ-Preamble-Mode						OPTIONAL,
	mIMO-ActivationIndicator		MIMO-ActivationIndicator			OPTIONAL,
	hSDSCH-MACdPDUSizeFormat		HSDSCH-MACdPDUSizeFormat			OPTIONAL,
	sixtyfourQAM-UsageAllowedIndicator		SixtyfourQAM-UsageAllowedIndicator			OPTIONAL,
	uE-with-enhanced-HS-SCCH-support-indicator		NULL		OPTIONAL,
	continuousPacketConnectivityHS-SCCH-less-Information			ContinuousPacketConnectivityHS-SCCH-less-Information		OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { HSDSCHPreconfigurationSetup-ExtIEs } }			OPTIONAL,
	...
}

HSDSCHPreconfigurationSetup-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-UE-SupportIndicatorExtension				CRITICALITY ignore	EXTENSION UE-SupportIndicatorExtension				PRESENCE optional}|
	{ID id-MIMO-withfourtransmitantennas-ActivationIndicator	CRITICALITY ignore	EXTENSION MIMO-withfourtransmitantennas-ActivationIndicator			PRESENCE optional}|
	{ID id-DualStream-MIMO-withfourtransmitantennas-ActivationIndicator	CRITICALITY ignore	EXTENSION DualStream-MIMO-withfourtransmitantennas-ActivationIndicator		PRESENCE optional}|
	{ ID id-Multiflow-Information					CRITICALITY ignore	EXTENSION Multiflow-Information							PRESENCE optional}|
	{ ID id-FTPICH-Information						CRITICALITY ignore	EXTENSION FTPICH-Information								PRESENCE optional}|
	{ ID id-UL-CLTD-Information						CRITICALITY ignore	EXTENSION UL-CLTD-Information							PRESENCE optional}|
	{ ID id-UL-MIMO-Information						CRITICALITY ignore	EXTENSION UL-MIMO-Information							PRESENCE optional}|
	{ ID id-SixteenQAM-UL-Operation-Indicator		CRITICALITY ignore	EXTENSION SixteenQAM-UL-Operation-Indicator			PRESENCE optional}|
	{ ID id-SixtyfourQAM-UL-Operation-Indicator		CRITICALITY ignore	EXTENSION SixtyfourQAM-UL-Operation-Indicator		PRESENCE optional},
	...
}


HS-SCCH-PreconfiguredCodes				::= SEQUENCE (SIZE (1..maxNrOfHSSCCHCodes)) OF HS-SCCH-PreconfiguredCodesItem

HS-SCCH-PreconfiguredCodesItem ::= SEQUENCE {
	hS-SCCH-CodeNumber			HS-SCCH-CodeNumber,
	iE-Extensions			ProtocolExtensionContainer { { HS-SCCH-PreconfiguredCodesItem-ExtIEs} } OPTIONAL,
	...
}

HS-SCCH-PreconfiguredCodesItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-SCCH-CodeNumber ::= INTEGER (0..127)


HSSCCH-Specific-InformationRespListFDD ::= SEQUENCE (SIZE (1..maxNrOfHSSCCHCodes)) OF HSSCCH-Codes

HSSCCH-Codes ::= SEQUENCE {
	codeNumber										INTEGER (0..127),
	iE-Extensions									ProtocolExtensionContainer { { HSSCCH-Specific-InformationRespItemFDD-ExtIEs } }		OPTIONAL,
	...
}

HSSCCH-Specific-InformationRespItemFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSSCCH-Specific-InformationRespListTDD ::= SEQUENCE (SIZE (1..maxNrOfHSSCCHCodes)) OF HSSCCH-Specific-InformationRespItemTDD

HSSCCH-Specific-InformationRespItemTDD ::= SEQUENCE {
	timeslot										TimeSlot,
	midambleShiftAndBurstType						MidambleShiftAndBurstType,
	tDD-ChannelisationCode							TDD-ChannelisationCode,
	hSSICH-Info										HSSICH-Info,
	iE-Extensions									ProtocolExtensionContainer { { HSSCCH-Specific-InformationRespItemTDD-ExtIEs } }			OPTIONAL,
	...
}

HSSCCH-Specific-InformationRespItemTDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSSCCH-Specific-InformationRespListTDDLCR ::= SEQUENCE (SIZE (1..maxNrOfHSSCCHCodes)) OF HSSCCH-Specific-InformationRespItemTDDLCR

HSSCCH-Specific-InformationRespItemTDDLCR ::= SEQUENCE {
	timeslotLCR									TimeSlotLCR,
	midambleShiftLCR							MidambleShiftLCR,
	first-TDD-ChannelisationCode					TDD-ChannelisationCode,
	second-TDD-ChannelisationCode			TDD-ChannelisationCode,
	hSSICH-InfoLCR								HSSICH-InfoLCR,
	iE-Extensions								ProtocolExtensionContainer { { HSSCCH-Specific-InformationRespItemTDDLCR-ExtIEs } }			OPTIONAL,
	...
}

HSSCCH-Specific-InformationRespItemTDDLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-UARFCNforNt		CRITICALITY reject		EXTENSION UARFCN		PRESENCE optional},
	-- Applicable for 1.28Mcps TDD when using multiple frequencies. this IE indicates the frequency which is actually used by the  HS-SCCH
	...
}
HSSCCH-Specific-InformationRespListTDD768 ::= SEQUENCE (SIZE (1..maxNrOfHSSCCHCodes)) OF HSSCCH-Specific-InformationRespItemTDD768

HSSCCH-Specific-InformationRespItemTDD768 ::= SEQUENCE {
	timeslot										TimeSlot,
	midambleShiftAndBurstType768					MidambleShiftAndBurstType768,
	tDD-ChannelisationCode768						TDD-ChannelisationCode768,
	hSSICH-Info768									HSSICH-Info768,
	iE-Extensions									ProtocolExtensionContainer { { HSSCCH-Specific-InformationRespItemTDD768-ExtIEs } }			OPTIONAL,
	...
}

HSSCCH-Specific-InformationRespItemTDD768-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


HSSICH-Info ::= SEQUENCE {
	hsSICH-ID										HS-SICH-ID,
	timeslot										TimeSlot,
	midambleShiftAndBurstType						MidambleShiftAndBurstType,
	tDD-ChannelisationCode							TDD-ChannelisationCode,
	iE-Extensions									ProtocolExtensionContainer { { HSSICH-Info-ExtIEs } }			OPTIONAL,
	...
}

HSSICH-Info-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSSICH-InfoLCR ::= SEQUENCE {
	hsSICH-ID										HS-SICH-ID,
	timeslotLCR										TimeSlotLCR,
	midambleShiftLCR								MidambleShiftLCR,
	tDD-ChannelisationCode						TDD-ChannelisationCode,
	iE-Extensions									ProtocolExtensionContainer { { HSSICH-Info-LCR-ExtIEs } }			OPTIONAL,
	...
}

HSSICH-Info-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-HS-SICH-ID							CRITICALITY ignore	EXTENSION Extended-HS-SICH-ID	PRESENCE optional},
	-- used if the HS-SICH identity has a value larger than 31
	...
}

HSSICH-Info768 ::= SEQUENCE {
	hsSICH-ID										HS-SICH-ID,
	timeslot										TimeSlot,
	midambleShiftAndBurstType768					MidambleShiftAndBurstType768,
	tDD-ChannelisationCode768						TDD-ChannelisationCode768,
	iE-Extensions									ProtocolExtensionContainer { { HSSICH-Info-768-ExtIEs } }			OPTIONAL,
	...
}

HSSICH-Info-768-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


HS-SICH-Reception-Quality-Value ::= SEQUENCE {
	failed-HS-SICH				HS-SICH-failed,
	missed-HS-SICH				HS-SICH-missed,
	total-HS-SICH				HS-SICH-total,
	iE-Extensions				ProtocolExtensionContainer { { HS-SICH-Reception-Quality-Value-ExtIEs} } OPTIONAL,
...
}

HS-SICH-Reception-Quality-Value-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Additional-failed-HS-SICH		CRITICALITY reject		EXTENSION 	HS-SICH-failed			PRESENCE 	optional	}|
	-- Mandatory for 1.28Mcps TDD only, used when there are more than 20 failed HS-SICH
	{ID id-Additional-missed-HS-SICH		CRITICALITY reject		EXTENSION 	HS-SICH-missed			PRESENCE	optional}|
	-- Mandatory for 1.28Mcps TDD only, used when there are more than 20 missed HS-SICH
	{ID id-Additional-total-HS-SICH			CRITICALITY reject		EXTENSION 	HS-SICH-total			PRESENCE	optional},
	-- Mandatory for 1.28Mcps TDD only, used when there are more than 20 total HS-SICH
	...
}

HS-SICH-failed ::= INTEGER (0..20)

HS-SICH-missed ::= INTEGER (0..20)

HS-SICH-total ::= INTEGER (0..20)

HS-SICH-Reception-Quality-Measurement-Value ::= INTEGER (0..20)
-- According to mapping in TS 25.123 [23]

HSDSCH-MACdFlow-ID ::= INTEGER (0..maxNrOfMACdFlows-1)

HSDSCH-RNTI ::= INTEGER (0..65535)

HS-PDSCH-FDD-Code-Information ::= SEQUENCE {
	number-of-HS-PDSCH-codes						INTEGER (0..maxHS-PDSCHCodeNrComp-1),
	hS-PDSCH-Start-code-number 					HS-PDSCH-Start-code-number		OPTIONAL, 
-- Only included when number of HS-DSCH codes > 0
	iE-Extensions				ProtocolExtensionContainer { { HS-PDSCH-FDD-Code-Information-ExtIEs} } OPTIONAL,
	...
}

HS-PDSCH-FDD-Code-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-PDSCH-Start-code-number ::=	INTEGER (1..maxHS-PDSCHCodeNrComp-1)

HS-SCCH-ID ::= INTEGER (0..31)
HS-SICH-ID ::= INTEGER (0..31)

HS-SCCH-FDD-Code-Information::= CHOICE {
	replace					HS-SCCH-FDD-Code-List,
	remove					NULL,
	...
}

HS-SCCH-FDD-Code-List ::= SEQUENCE (SIZE (1..maxNrOfHSSCCHs)) OF HS-SCCH-FDD-Code-Information-Item

HS-SCCH-FDD-Code-Information-Item ::= INTEGER (0..maxHS-SCCHCodeNrComp-1)

HSSCCH-CodeChangeIndicator	::= ENUMERATED {
	hsSCCHCodeChangeNeeded
}

HSSCCH-Code-Change-Grant	::= ENUMERATED {
	changeGranted
}

HS-PDSCH-Code-Change-Indicator	::= ENUMERATED {
	hsPDSCHCodeChangeNeeded
}

HS-PDSCH-Code-Change-Grant	::= ENUMERATED {
	changeGranted
}

HSDSCH-Configured-Indicator::= ENUMERATED {
	configured-HS-DSCH,
	no-configured-HS-DSCH
}

HS-DSCH-Serving-Cell-Change-Info ::= SEQUENCE {
	hspdsch-RL-ID					RL-ID,
	hSDSCH-FDD-Information			HSDSCH-FDD-Information	OPTIONAL,
	hsdsch-RNTI						HSDSCH-RNTI,
	iE-Extensions					ProtocolExtensionContainer { { HS-DSCH-Serving-Cell-Change-Info-ExtIEs} }	OPTIONAL,
	...
}

HS-DSCH-Serving-Cell-Change-Info-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-ContinuousPacketConnectivityHS-SCCH-less-Information	CRITICALITY reject	EXTENSION ContinuousPacketConnectivityHS-SCCH-less-Information		PRESENCE optional }|
	{ ID id-ContinuousPacketConnectivityDTX-DRX-Information		CRITICALITY reject	EXTENSION ContinuousPacketConnectivityDTX-DRX-Information	PRESENCE optional },
	...
}

HS-DSCH-Serving-Cell-Change-Info-Response::= SEQUENCE {
	hS-DSCH-serving-cell-choice		HS-DSCH-serving-cell-choice,
	iE-Extensions					ProtocolExtensionContainer { { HS-DSCH-serving-cell-informationResponse-ExtIEs} } OPTIONAL,
	...
}

HS-DSCH-serving-cell-informationResponse-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-DSCH-serving-cell-choice ::= CHOICE {
	hS-serving-cell-change-successful		HS-serving-cell-change-successful,
	hS-serving-cell-change-unsuccessful		HS-serving-cell-change-unsuccessful,
	...
}

HS-serving-cell-change-successful ::= SEQUENCE {
	hSDSCH-FDD-Information-Response		HSDSCH-FDD-Information-Response,
	iE-Extensions						ProtocolExtensionContainer { { HS-serving-cell-change-successful-ExtIEs} } OPTIONAL,
	...
}

HS-serving-cell-change-successful-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-ContinuousPacketConnectivityHS-SCCH-less-Information-Response	CRITICALITY ignore		EXTENSION ContinuousPacketConnectivityHS-SCCH-less-Information-Response			PRESENCE optional },
	...
}

HS-serving-cell-change-unsuccessful ::= SEQUENCE {
	cause							Cause,
	iE-Extensions					ProtocolExtensionContainer { { HS-serving-cell-change-unsuccessful-ExtIEs} } OPTIONAL,
	...
}

HS-serving-cell-change-unsuccessful-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


HS-DSCH-DRX-Cycle-FACH ::= ENUMERATED {v4,v8,v16,v32,...}

HS-DSCH-RX-Burst-FACH::= ENUMERATED {v1,v2,v4,v8,v16,...}


HSDSCH-FDD-Update-Information ::= SEQUENCE {
	hsSCCHCodeChangeIndicator						HSSCCH-CodeChangeIndicator					OPTIONAL,
	cqiFeedback-CycleK								CQI-Feedback-Cycle							OPTIONAL, 
	cqiRepetitionFactor								CQI-RepetitionFactor						OPTIONAL,
	ackNackRepetitionFactor							AckNack-RepetitionFactor					OPTIONAL,
	cqiPowerOffset									CQI-Power-Offset 							OPTIONAL,
	ackPowerOffset									Ack-Power-Offset							OPTIONAL,
	nackPowerOffset									Nack-Power-Offset							OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-FDD-Update-Information-ExtIEs } }		OPTIONAL,
	...
}

HSDSCH-FDD-Update-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-HS-PDSCH-Code-Change-Indicator		CRITICALITY ignore	EXTENSION HS-PDSCH-Code-Change-Indicator		PRESENCE optional}|
	{ID id-PrecoderWeightSetRestriction			CRITICALITY ignore	EXTENSION Precoder-Weight-Set-Restriction		PRESENCE optional}|
	{ID id-CQI-Feedback-Cycle2					CRITICALITY ignore	EXTENSION CQI-Feedback-Cycle2						PRESENCE optional}|
	{ID id-CQI-Cycle-Switch-Timer				CRITICALITY ignore	EXTENSION CQI-Cycle-Switch-Timer					PRESENCE optional},
	...
}

HSDSCH-TDD-Update-Information ::= SEQUENCE {
	hsSCCHCodeChangeIndicator						HSSCCH-CodeChangeIndicator					OPTIONAL,
	tDDAckNackPowerOffset							TDD-AckNack-Power-Offset					OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-TDD-Update-Information-ExtIEs } }		OPTIONAL,
	...
}

HSDSCH-TDD-Update-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}
HSPDSCH-Code-Index ::= INTEGER (1..maxHS-PDSCHCodeNrComp-1)
-- index of first HS-PDSCH code

HSPDSCH-First-Code-Index ::= INTEGER (1..maxHS-PDSCHCodeNrComp-1)
	-- index of first HS-PDSCH code

HSPDSCH-Second-Code-Index ::= INTEGER (1..maxHS-PDSCHCodeNrComp-1)
	-- index of second HS-PDSCH code

HSPDSCH-Second-Code-Support ::= BOOLEAN
	-- true: applied, false: not applied

HSDPA-Associated-PICH-InformationLCR ::= CHOICE {
	hsdpa-PICH-Shared-with-PCH						HSDPA-PICH-Shared-with-PCH,
	hsdpa-PICH-notShared-with-PCHLCR				HSDPA-PICH-notShared-with-PCHLCR,
	...
}


HSDPA-PICH-notShared-with-PCHLCR ::= SEQUENCE {
	hSDPA-PICH-notShared-ID					CommonPhysicalChannelID,
	tdd-ChannelisationCodeLCR				TDD-ChannelisationCodeLCR,
	timeSlotLCR  							TimeSlotLCR,
	midambleShiftLCR						MidambleShiftLCR,
	tdd-PhysicalChannelOffset				TDD-PhysicalChannelOffset,
	repetitionPeriod						RepetitionPeriod,
	repetitionLength						RepetitionLength,
	pagingIndicatorLength					PagingIndicatorLength,
	pICH-Power								PICH-Power,
	second-TDD-ChannelisationCodeLCR		TDD-ChannelisationCodeLCR,
	sttd-Indicator							STTD-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { HSDPA-PICH-notShared-with-PCHLCR-ExtIEs } }		OPTIONAL,
	...
}

HSDPA-PICH-notShared-with-PCHLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


HSDSCH-Common-System-InformationLCR ::= SEQUENCE {
	hsdsch-Common-InformationLCR					HSDSCH-Common-InformationLCR							OPTIONAL,
	commonMACFlow-Specific-InformationLCR			CommonMACFlow-Specific-InfoListLCR						OPTIONAL,
	common-H-RNTI-InformationLCR					Common-H-RNTI-InformationLCR							OPTIONAL,
	sync-InformationLCR								Sync-InformationLCR										OPTIONAL,
	tDD-AckNack-Power-Offset						TDD-AckNack-Power-Offset								OPTIONAL,
	hSSICH-SIRTarget								UL-SIR													OPTIONAL,
	hSSICH-TPC-StepSize								TDD-TPC-UplinkStepSize-LCR								OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-Common-System-InformationLCR-ExtIEs } }		OPTIONAL,
	...
}

HSDSCH-Common-System-InformationLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSDSCH-Common-System-Information-ResponseLCR  ::= SEQUENCE {
	hsSCCH-Specific-Information-ResponseLCR			HSSCCH-Specific-InformationRespListLCR				OPTIONAL,
	hARQ-MemoryPartitioning							HARQ-MemoryPartitioning								OPTIONAL, 
-- This HARQ Memory Partitioning Information is for the first Frequency repetition, HARQ Memory Partitioning Information for Frequency repetitions 2 and on, should be defined in MultipleFreq-HARQ-MemoryPartitioning-InformationList.
	commonMACFlow-Specific-Info-ResponseLCR			CommonMACFlow-Specific-InfoList-ResponseLCR			OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-Common-System-Information-ResponseLCR-ExtIEs } }		OPTIONAL,
	...
}

HSDSCH-Common-System-Information-ResponseLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
{ ID id-UARFCNforNt											CRITICALITY ignore	EXTENSION UARFCN	PRESENCE optional}|
-- Applicable to 1.28Mcps TDD when using multiple frequencies. This is the UARFCN for the first Frequency repetition
{ ID id-MultipleFreq-HARQ-MemoryPartitioning-InformationList	CRITICALITY ignore	EXTENSION MultipleFreq-HARQ-MemoryPartitioning-InformationList	PRESENCE optional }|
-- Applicable to 1.28Mcps TDD when using multiple frequencies.This HARQ MemoryPartitioning Information is for the 2nd and beyond frequencies. 
{ ID id-CommonMACFlow-Specific-InfoList-ResponseLCR-Ext		CRITICALITY ignore	EXTENSION CommonMACFlow-Specific-InfoList-ResponseLCR-Ext	PRESENCE optional },
	...
}

HSDSCH-Common-InformationLCR ::= SEQUENCE {
	cCCH-PriorityQueue-Id											PriorityQueue-Id,
	sRB1-PriorityQueue-Id											PriorityQueue-Id,
	associatedCommon-MACFlowLCR										Common-MACFlow-ID-LCR,
	fACH-Measurement-Occasion-Cycle-Length-Coefficient				FACH-Measurement-Occasion-Cycle-Length-Coefficient				OPTIONAL,
	bCCH-Specific-HSDSCH-RNTI-InformationLCR						BCCH-Specific-HSDSCH-RNTI-InformationLCR					OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { HSDSCH-Common-InformationLCR-ExtIEs} }					OPTIONAL,
	...
}

HSDSCH-Common-InformationLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSDSCH-Paging-System-InformationLCR ::= SEQUENCE {
	paging-MACFlow-Specific-InformationLCR			Paging-MACFlow-Specific-InformationLCR,
	hSSCCH-Power									DL-Power																OPTIONAL,
	hSPDSCH-Power									DL-Power																OPTIONAL,
	reception-Window-Size							INTEGER(1..16)															OPTIONAL,
	n-PCH											INTEGER(1..8)															OPTIONAL,
	paging-Subchannel-Size							INTEGER(1..3)															OPTIONAL,
	transport-Block-Size-List						Transport-Block-Size-List												OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-Paging-System-InformationLCR-ExtIEs } }		OPTIONAL,
	...
}

HSDSCH-Paging-System-InformationLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSDSCH-Paging-System-Information-ResponseLCR ::= SEQUENCE (SIZE (1..maxNrOfPagingMACFlow)) OF HSDSCH-Paging-System-Information-ResponseListLCR

HSDSCH-Paging-System-Information-ResponseListLCR  ::= SEQUENCE {
	pagingMACFlow-ID								Paging-MACFlow-ID,
	bindingID										BindingID									OPTIONAL,
	transportLayerAddress							TransportLayerAddress						OPTIONAL,
	dL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst		DL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst,
	iE-Extensions									ProtocolExtensionContainer { { HSDSCH-Paging-System-Information-ResponseListLCR-ExtIEs } }		OPTIONAL,
	...
}

HSDSCH-Paging-System-Information-ResponseListLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-SCCH-ID-LCR ::= INTEGER (0..255)

HSSCCH-Specific-InformationRespListLCR ::= SEQUENCE (SIZE (1..maxNrOfHSSCCHsLCR)) OF HSSCCH-Specific-InformationRespItemLCR

HSSCCH-Specific-InformationRespItemLCR ::= SEQUENCE {
	hS-SCCH-ID-LCR									HS-SCCH-ID-LCR,
	iE-Extensions									ProtocolExtensionContainer { { HSSCCH-Specific-InformationRespItemLCR-ExtIEs } }		OPTIONAL,
	...
}

HSSCCH-Specific-InformationRespItemLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}
HS-DSCH-Semi-PersistentScheduling-Information-LCR ::= SEQUENCE {
	transport-Block-Size-List				Transport-Block-Size-List-LCR,
	repetition-Period-List-LCR				Repetition-Period-List-LCR,
	hS-DSCH-SPS-Reservation-Indicator		SPS-Reservation-Indicator				OPTIONAL,
	hS-DSCH-SPS-Operation-Indicator			HS-DSCH-SPS-Operation-Indicator,
	iE-Extensions							ProtocolExtensionContainer { { HS-DSCH-Semi-PersistentScheduling-Information-LCR-ExtIEs } }			OPTIONAL,
	...
}

HS-DSCH-Semi-PersistentScheduling-Information-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Transport-Block-Size-List-LCR ::= SEQUENCE (SIZE (1..maxNoOfTBSs-Mapping-HS-DSCH-SPS)) OF Transport-Block-Size-Item-LCR

Transport-Block-Size-Item-LCR ::= SEQUENCE {
	transport-Block-Size-maping-Index-LCR		Transport-Block-Size-maping-Index-LCR,
	transport-Block-Size-Index-LCR				Transport-Block-Size-Index-LCR,
	iE-Extensions								ProtocolExtensionContainer { { Transport-Block-Size-Item-LCR-ExtIEs } }			OPTIONAL,
	...
}

Transport-Block-Size-Item-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Transport-Block-Size-maping-Index-LCR ::= INTEGER (0..maxNoOfTBSs-Mapping-HS-DSCH-SPS-1)

Transport-Block-Size-Index-LCR ::= INTEGER (1..maxNoOfHS-DSCH-TBSsLCR)

Repetition-Period-List-LCR ::= SEQUENCE (SIZE (1..maxNoOfRepetition-Period-LCR)) OF Repetition-Period-Item-LCR

Repetition-Period-Item-LCR ::= SEQUENCE {
	repetitionPeriodIndex		RepetitionPeriodIndex,
	repetitionPeriod			RepetitionPeriod,
	repetitionLength			RepetitionLength				OPTIONAL,
	iE-Extensions				ProtocolExtensionContainer { { Repetition-Period-Item-LCR-ExtIEs } }			OPTIONAL,
	...
}

Repetition-Period-Item-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

RepetitionPeriodIndex ::= INTEGER (0..maxNoOfRepetitionPeriod-SPS-LCR-1)

SPS-Reservation-Indicator ::= ENUMERATED {
	reserve
}

HS-DSCH-SPS-Operation-Indicator ::= CHOICE {
	logicalChannellevel			LogicalChannellevel,
	priorityQueuelevel			PriorityQueuelevel,
	...
}

LogicalChannellevel ::= BIT STRING (SIZE (16))

PriorityQueuelevel ::= BIT STRING (SIZE (8))

HS-DSCH-Semi-PersistentScheduling-Information-to-Modify-LCR ::= SEQUENCE {
	transport-Block-Size-List				Transport-Block-Size-List-LCR			OPTIONAL,
	repetition-Period-List-LCR				Repetition-Period-List-LCR				OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { HS-DSCH-Semi-PersistentScheduling-Information-to-Modify-LCR-ExtIEs } }							OPTIONAL,
	...
}

HS-DSCH-Semi-PersistentScheduling-Information-to-Modify-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
{ ID id-HS-DSCH-SPS-Reservation-Indicator		CRITICALITY ignore	EXTENSION SPS-Reservation-Indicator	PRESENCE optional }|
{ ID id-HS-DSCH-SPS-Operation-Indicator			CRITICALITY reject	EXTENSION HS-DSCH-SPS-Operation-Indicator	PRESENCE optional },
	...
}

HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR ::= SEQUENCE {
	hS-SICH-InformationList-for-HS-DSCH-SPS		HS-SICH-InformationList-for-HS-DSCH-SPS,
	initial-HS-PDSCH-SPS-Resource				Initial-HS-PDSCH-SPS-Resource			OPTIONAL,
	buffer-Size-for-HS-DSCH-SPS					Process-Memory-Size						OPTIONAL,
	number-of-Processes-for-HS-DSCH-SPS			Number-of-Processes-for-HS-DSCH-SPS		OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR-ExtIEs } }			OPTIONAL,
	...
}

HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-SICH-InformationList-for-HS-DSCH-SPS ::= SEQUENCE (SIZE (1..maxNoOf-HS-SICH-SPS)) OF HS-SICH-InformationItem-for-HS-DSCH-SPS

HS-SICH-InformationItem-for-HS-DSCH-SPS ::= SEQUENCE {
	hS-SICH-Mapping-Index			HS-SICH-Mapping-Index			OPTIONAL,
	-- the IE is madatory for 1.28Mcps TDD.
	hS-SICH-Type					HS-SICH-Type,
	iE-Extensions					ProtocolExtensionContainer { { HS-SICH-InformationItem-for-HS-DSCH-SPS-ExtIEs } }			OPTIONAL,
	...
}

HS-SICH-InformationItem-for-HS-DSCH-SPS-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-SICH-Mapping-Index ::= INTEGER (0..maxNoOf-HS-SICH-SPS-1)

HS-SICH-Type ::= CHOICE {
	hS-SCCH-Associated-HS-SICH			HS-SCCH-Associated-HS-SICH,
	non-HS-SCCH-Associated-HS-SICH		Non-HS-SCCH-Associated-HS-SICH,
	...
}


HS-SCCH-Associated-HS-SICH ::= SEQUENCE {
	hsSICH-ID							HS-SICH-ID,
	extended-HS-SICH-ID					Extended-HS-SICH-ID			OPTIONAL,
...
}


Non-HS-SCCH-Associated-HS-SICH::= SEQUENCE {
	non-HS-SCCH-Aassociated-HS-SICH-ID	Non-HS-SCCH-Aassociated-HS-SICH-ID,
...
}

Non-HS-SCCH-Aassociated-HS-SICH-ID ::= INTEGER (0..255)

Initial-HS-PDSCH-SPS-Resource::= SEQUENCE {
	repetitionPeriodIndex						RepetitionPeriodIndex,
	repetitionLength							RepetitionLength			OPTIONAL,
	-- the IE is not used.
	hS-PDSCH-Offset								TDD-PhysicalChannelOffset,
	timeslot-Resource-Related-Information		HS-DSCH-TimeslotResourceLCR,
	startCode									TDD-ChannelisationCode,
	endCode										TDD-ChannelisationCode,
	transport-Block-Size-Index					Transport-Block-Size-Index-LCR,
	modulationType								ModulationSPS-LCR,
	hS-SICH-Mapping-Index						HS-SICH-Mapping-Index,
	iE-Extensions								ProtocolExtensionContainer { { Initial-HS-PDSCH-SPS-Resource-ExtIEs } }			OPTIONAL,
...
}

Initial-HS-PDSCH-SPS-Resource-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MidambleShiftLCR	CRITICALITY reject	EXTENSION MidambleShiftLCR		PRESENCE	optional },
	-- mandaroty for 1.28Mcps TDD.
	...
}

HS-DSCH-TimeslotResourceLCR ::= BIT STRING (SIZE (5))

ModulationSPS-LCR ::= ENUMERATED {
	qPSK,
	sixteenQAM,
	...
}

Number-of-Processes-for-HS-DSCH-SPS ::= INTEGER (1..16)

Add-To-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst::= SEQUENCE {
	non-HS-SCCH-Associated-HS-SICH-InformationList		Non-HS-SCCH-Associated-HS-SICH-InformationList,
	iE-Extensions										ProtocolExtensionContainer { { Add-To-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-ExtIEs } }			OPTIONAL,
...
}

Add-To-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Add-To-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext	CRITICALITY reject	EXTENSION Non-HS-SCCH-Associated-HS-SICH-InformationList-Ext		PRESENCE	optional },
	...
}

Non-HS-SCCH-Associated-HS-SICH-InformationList ::= SEQUENCE (SIZE (0..maxNoOfNon-HS-SCCH-Assosiated-HS-SICH)) OF Non-HS-SCCH-Associated-HS-SICH-InformationItem

Non-HS-SCCH-Associated-HS-SICH-InformationList-Ext ::= SEQUENCE (SIZE (0..maxNoOfNon-HS-SCCH-Assosiated-HS-SICH-Ext)) OF Non-HS-SCCH-Associated-HS-SICH-InformationItem

Non-HS-SCCH-Associated-HS-SICH-InformationItem ::= SEQUENCE {
	non-HS-SCCH-Aassociated-HS-SICH-ID		Non-HS-SCCH-Aassociated-HS-SICH-ID,
	timeSlotLCR								TimeSlotLCR,
	midambleShiftLCR						MidambleShiftLCR,
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	uARFCN									UARFCN						OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { Non-HS-SCCH-Associated-HS-SICH-InformationItem-ExtIEs } }			OPTIONAL,
	...
}

Non-HS-SCCH-Associated-HS-SICH-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


Modify-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst::= SEQUENCE {
	modify-non-HS-SCCH-Associated-HS-SICH-InformationList		Modify-Non-HS-SCCH-Associated-HS-SICH-InformationList,
	iE-Extensions						ProtocolExtensionContainer { { Modify-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-ExtIEs } }			OPTIONAL,
...
}

Modify-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Modify-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext	CRITICALITY reject	EXTENSION Modify-Non-HS-SCCH-Associated-HS-SICH-InformationList-Ext		PRESENCE	optional },
	...
}

Modify-Non-HS-SCCH-Associated-HS-SICH-InformationList ::= SEQUENCE (SIZE (0..maxNoOfNon-HS-SCCH-Assosiated-HS-SICH)) OF Modify-Non-HS-SCCH-Associated-HS-SICH-InformationItem

Modify-Non-HS-SCCH-Associated-HS-SICH-InformationList-Ext ::= SEQUENCE (SIZE (0.. maxNoOfNon-HS-SCCH-Assosiated-HS-SICH-Ext)) OF Modify-Non-HS-SCCH-Associated-HS-SICH-InformationItem

Modify-Non-HS-SCCH-Associated-HS-SICH-InformationItem ::= SEQUENCE {
	non-HS-SCCH-Aassociated-HS-SICH-ID		Non-HS-SCCH-Aassociated-HS-SICH-ID,
	timeSlotLCR								TimeSlotLCR						OPTIONAL,
	midambleShiftLCR						MidambleShiftLCR				OPTIONAL,
	tdd-ChannelisationCode					TDD-ChannelisationCode			OPTIONAL,
	uARFCN									UARFCN							OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { Modify-Non-HS-SCCH-Associated-HS-SICH-InformationItem-ExtIEs } }			OPTIONAL,
	...
}

Modify-Non-HS-SCCH-Associated-HS-SICH-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst ::= SEQUENCE (SIZE (0..maxNoOfNon-HS-SCCH-Assosiated-HS-SICH)) OF Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqstItem

Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext ::= SEQUENCE (SIZE (0..maxNoOfNon-HS-SCCH-Assosiated-HS-SICH-Ext)) OF Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqstItem

Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqstItem ::= SEQUENCE {
non-HS-SCCH-Aassociated-HS-SICH-ID			Non-HS-SCCH-Aassociated-HS-SICH-ID,
...
}

MIMO-ReferenceSignal-InformationListLCR ::= SEQUENCE (SIZE (1..maxNrOfHSSCCHCodes)) OF HSSICH-ReferenceSignal-InformationLCR

HSSICH-ReferenceSignal-InformationLCR ::= SEQUENCE {
	midambleConfigurationLCR		MidambleConfigurationLCR,
	midambleShift					INTEGER (0..15),
	timeSlotLCR						TimeSlotLCR,
	iE-Extensions					ProtocolExtensionContainer { { HSSICH-ReferenceSignal-InformationLCR-ExtIEs } }		OPTIONAL,
	...
}

HSSICH-ReferenceSignal-InformationLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HSSICH-ReferenceSignal-InformationModifyLCR ::= SEQUENCE {
	hSSICH-ReferenceSignal-InformationLCR		HSSICH-ReferenceSignal-InformationLCR	OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { HSSICH-ReferenceSignal-InformationModifyLCR-ExtIEs } }		OPTIONAL,
	...
}

HSSICH-ReferenceSignal-InformationModifyLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

HS-DPCCH-transmission-continuation-backoff ::= ENUMERATED {v10, v20, v30, v40, v80, v160, v320, v800, infinity, ...}

-- ==========================================
--	I
-- ==========================================

IB-OC-ID ::= INTEGER (1..16)

IB-SG-DATA ::= BIT STRING
-- Contains SIB data fixed" or "SIB data variable" in segment as encoded in ref.TS 25.331 [18].

IB-SG-POS ::= INTEGER (0..4094)
-- Only even positions allowed

IB-SG-REP ::= ENUMERATED {rep4, rep8, rep16, rep32, rep64, rep128, rep256, rep512, rep1024, rep2048, rep4096}

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,
	sIB13dot1,
	sIB13dot2,
	sIB13dot3,
	sIB13dot4,
	sIB14,
	sIB15,
	sIB15dot1,
	sIB15dot2,
	sIB15dot3,
	sIB16,
	...,
	sIB17,
	sIB15dot4,
	sIB18,
	sIB15dot5,
	sIB5bis,
	sIB11bis,
	sIB15bis,
	sIB15dot1bis,
	sIB15dot2bis,
	sIB15dot3bis,
	sIB15dot6,
	sIB15dot7,
	sIB15dot8,
	sIB15dot2ter,
	sIB19,
	not-Applicable-SIB20,
	sIB21,
	sIB22,
	sIB15dot1ter,
	sB3,
	sIB23,
	sIB24,
	sIB11ter,
	sIB25
}

IMB-Parameters ::= SEQUENCE {
	sub-Frame-Number						Sub-Frame-Number,
	fdd-dl-ChannelisationCodeNumber			FDD-DL-ChannelisationCodeNumber							OPTIONAL,
	ie-Extensions							ProtocolExtensionContainer { { IMB-Parameters-ExtIEs} }	OPTIONAL,
	...
}

IMB-Parameters-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

BCH-Parameters ::= SEQUENCE {
	commonTransportChannelID			CommonTransportChannelID,
	bCH-Power							DL-Power,
	iE-Extensions						ProtocolExtensionContainer  { { BCH-ParametersItem-ExtIEs} }		OPTIONAL,
	...
}

BCH-ParametersItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Inactivity-Threshold-for-UE-DRX-Cycle ::= ENUMERATED {v0, v1, v2, v4, v8, v16, v32, v64, v128, v256, v512}
-- Unit subframe

Inactivity-Threshold-for-UE-DTX-Cycle2 ::= ENUMERATED {v1, v4, v8, v16, v32, v64, v128, v256}
-- Unit E-DCH TTI

Inactivity-Threshold-for-UE-Grant-Monitoring ::= ENUMERATED {v0, v1, v2, v4, v8, v16, v32, v64, v128, v256}
-- Unit E-DCH TTI


InformationReportCharacteristics ::= CHOICE {
	onDemand				NULL,
	periodic				InformationReportCharacteristicsType-ReportPeriodicity,
	onModification          InformationReportCharacteristicsType-OnModification,
	...
}

InformationReportCharacteristicsType-ReportPeriodicity ::= CHOICE {
	min 				ReportPeriodicity-Scaledmin,
	hours				ReportPeriodicity-Scaledhour,
	...
}

InformationReportCharacteristicsType-OnModification ::= SEQUENCE {
    information-thresholds        InformationThresholds		OPTIONAL,
    ie-Extensions		          ProtocolExtensionContainer { { InformationReportCharacteristicsType-OnModification-ExtIEs} }	OPTIONAL,
   ...
}

InformationReportCharacteristicsType-OnModification-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

InformationThresholds ::= CHOICE {
    dgps                DGPSThresholds,
   	...,
	dGANSSThreshold		DGANSSThreshold
} 

InformationExchangeID ::= INTEGER (0..1048575)

InformationType ::= SEQUENCE {
	information-Type-Item		Information-Type-Item,
	gPSInformation  			GPS-Information													OPTIONAL,
	-- The IE shall be present if the Information Type Item IE indicates "GPS Information".
	iE-Extensions				ProtocolExtensionContainer { { Information-Type-ExtIEs} }		OPTIONAL,
	...
}

Information-Type-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
-- The following IE shall be present if the Information Type Item IE indicates ‘GANSS Information’
	{ ID id-GANSS-Information			CRITICALITY ignore	EXTENSION GANSS-Information			PRESENCE conditional }|
-- The following IE shall be present if the Information Type Item IE indicates ‘DGANSS Corrections’
	{ ID id-DGANSS-Corrections-Req		CRITICALITY ignore	EXTENSION DGANSS-Corrections-Req	PRESENCE conditional },
	...
}

Information-Type-Item ::= ENUMERATED {
    gpsinformation,
    dgpscorrections,
    gpsrxpos,
    ...,
	gANSSInformation,
	dGANSSCorrections,
	gANSS-RX-Pos
}

Initial-DL-DPCH-TimingAdjustment-Allowed ::= ENUMERATED {
	initial-DL-DPCH-TimingAdjustment-Allowed
}

InnerLoopDLPCStatus ::= ENUMERATED {
	active,
	inactive
}

IPDL-Indicator ::= ENUMERATED {
	active,
	inactive
}


IPDL-FDD-Parameters ::= SEQUENCE {
	iP-SpacingFDD					ENUMERATED{sp5,sp7,sp10,sp15,sp20,sp30,sp40,sp50,...},
	iP-Length						ENUMERATED{len5, len10},
	seed							INTEGER(0..63),
	burstModeParams					BurstModeParams		OPTIONAL,
	iP-Offset						INTEGER(0..9),
	iE-Extensions					ProtocolExtensionContainer { { IPDLFDDParameter-ExtIEs} }	OPTIONAL,
	...
}

IPDLFDDParameter-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

IPDL-TDD-Parameters ::= SEQUENCE {
	iP-SpacingTDD					ENUMERATED{sp30,sp40,sp50,sp70,sp100,...},
	iP-Start						INTEGER(0..4095),
	iP-Slot							INTEGER(0..14),
	iP-PCCPCH						ENUMERATED{switchOff-1-Frame,switchOff-2-Frames},
	burstModeParams					BurstModeParams		OPTIONAL,
	iE-Extensions			ProtocolExtensionContainer { { IPDLTDDParameter-ExtIEs} }	OPTIONAL,
	...
}

IPDL-TDD-Parameters-LCR ::= SEQUENCE {
	iP-SpacingTDD					ENUMERATED{sp30,sp40,sp50,sp70,sp100,...},
	iP-Start						INTEGER(0..4095),
	iP-Sub							ENUMERATED{first,second,both},
	burstModeParams					BurstModeParams		OPTIONAL,
	iE-Extensions			ProtocolExtensionContainer { { IPDLTDDParameterLCR-ExtIEs} }	OPTIONAL,
	...
}

IPMulticastIndication ::= SEQUENCE {
	transportLayerAddress			TransportLayerAddress,
	bindingID						BindingID,
	cFNOffset						INTEGER(0..255),
	iE-Extensions			ProtocolExtensionContainer { { IPMulticastIndication-ExtIEs} }	OPTIONAL,
	...
}

IPMulticastIndication-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

IPMulticastDataBearerIndication ::= BOOLEAN
-- true: IP Multicast used, false: IP Multicast not used

BurstModeParams ::= SEQUENCE {
	burstStart							INTEGER(0..15),
	burstLength							INTEGER(10..25),
	burstFreq							INTEGER(1..16),
	...
}

IPDLTDDParameter-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

IPDLTDDParameterLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

IdleIntervalInformation	::= SEQUENCE {
	idleIntervalInfo-k							INTEGER{none(0),two(2),three(3)} (0..3),
	idleIntervalInfo-offset						INTEGER(0..7),
	...
}

In-Sync-Information-LCR	::= SEQUENCE {
	t312			INTEGER(0..15),
	n312			ENUMERATED{s1, s2, s4, s10, s20, s50, s100, s200, s400, s600, s800, s1000},
	...
}


-- ==========================================
--	J
-- ==========================================

-- ==========================================
--	K
-- ==========================================

-- ==========================================
--	L
-- ==========================================

LimitedPowerIncrease ::= ENUMERATED {
	used,
	not-used
}

Local-Cell-ID ::= INTEGER (0..268435455)

LTGI-Presence ::= BOOLEAN
-- True = the Long Term Grant Indicator shall be used within E-DCH grants

LCRTDD-Uplink-Physical-Channel-Capability ::= SEQUENCE {
	maxTimeslotsPerSubFrame				INTEGER(1..6),
	maxPhysChPerTimeslot				ENUMERATED {one,two,...,three,four},
	iE-Extensions						ProtocolExtensionContainer { { LCRTDD-Uplink-Physical-Channel-Capability-ExtIEs} } OPTIONAL,
	...
}

LCRTDD-Uplink-Physical-Channel-Capability-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- ==========================================
--	M
-- ==========================================

MAC-DTX-Cycle-2ms ::= ENUMERATED {v1, v4, v5, v8, v10, v16, v20}

MAC-DTX-Cycle-10ms ::= ENUMERATED {v5, v10, v20}

MAC-ehs-Reset-Timer ::= ENUMERATED {v1, v2, v3, v4,...}

MACdPDU-Size ::= INTEGER (1..5000,...)
	-- In case of E-DCH value 8 and values not multiple of 8 shall not be used

MAC-PDU-SizeExtended ::= INTEGER (1..1504,...,1505)
	-- In case of E-DCH value 1 shall not be used

MAC-Inactivity-Threshold ::= ENUMERATED {v1, v2, v4, v8, v16, v32, v64, v128, v256, v512, infinity}
	-- Unit subframe

MACdPDU-Size-Indexlist ::= SEQUENCE (SIZE (1..maxNrOfMACdPDUIndexes)) OF MACdPDU-Size-IndexItem

MACdPDU-Size-IndexItem ::= SEQUENCE {
	sID									SID,
	macdPDU-Size						MACdPDU-Size,
	iE-Extensions						ProtocolExtensionContainer { { MACdPDU-Size-IndexItem-ExtIEs} }		OPTIONAL,
	...
}

MACdPDU-Size-IndexItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MACdPDU-Size-Indexlist-to-Modify ::= SEQUENCE (SIZE (1..maxNrOfMACdPDUIndexes)) OF MACdPDU-Size-IndexItem-to-Modify

MACdPDU-Size-IndexItem-to-Modify ::= SEQUENCE {
	sID									SID,
	macdPDU-Size						MACdPDU-Size,
	iE-Extensions						ProtocolExtensionContainer { { MACdPDU-Size-IndexItem-to-Modify-ExtIEs} }		OPTIONAL,
	...
}

MACdPDU-Size-IndexItem-to-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MACesGuaranteedBitRate ::= INTEGER (0..16777215,...,16777216..256000000)

MACes-Maximum-Bitrate-LCR ::= INTEGER (0..256000000,...)

MACeReset-Indicator ::= ENUMERATED {mACeReset}

MAChsGuaranteedBitRate ::= INTEGER (0..16777215,...,16777216..1000000000)

MAChsReorderingBufferSize-for-RLC-UM ::= INTEGER (0..300,...)
-- Unit kBytes

MAC-hsWindowSize		::= ENUMERATED {v4, v6, v8, v12, v16, v24, v32,..., v64, v128, v256}
-- For 1.28Mcps TDD when TSN length is configured to 9bits, ENUMERATED (32, 64, 96, 128, 160, 192, 256,...)


MAChsResetScheme ::= ENUMERATED {
	always,
	interNodeB-change
}


MaximumDL-PowerCapability ::=  INTEGER(0..500)
-- Unit dBm, Range 0dBm .. 50dBm, Step +0.1dB

Max-Bits-MACe-PDU-non-scheduled ::= INTEGER(1..maxNrOfBits-MACe-PDU-non-scheduled)

Max-EDCH-Resource-Allocation-for-CCCH ::= ENUMERATED {v8, v12, v16, v24, v32, v40, v80, v120,..., v20}
-- Value "v120" should not be used

Max-EDCH-Resource-Allocation-for-CCCH-Extension ::= ENUMERATED {v8, v12, v16, v20, v24, v32, v40, v80, ...}

Max-Period-for-Collision-Resolution ::= INTEGER(8..24,...)

Max-TB-Sizes ::= SEQUENCE {
	maximum-TB-Size-cell-edge-users		INTEGER (0..5000,...),
	maximum-TB-Size-other-users			INTEGER (0..5000,...),
	iE-Extensions						ProtocolExtensionContainer { {Max-TB-Sizes-ExtIEs} } OPTIONAL,
	...
	}


Max-TB-Sizes-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Maximum-Number-of-Retransmissions-For-E-DCH ::= INTEGER (0..15)

Maximum-Target-ReceivedTotalWideBandPower-LCR ::= INTEGER (0..621)
-- mapping as for RTWP measurement value, as specified in TS 25.123 [23]

MaximumTransmissionPower ::=  INTEGER(0..500)
-- Unit dBm, Range 0dBm .. 50dBm, Step +0.1dB


MaxNrOfUL-DPDCHs ::= INTEGER (1..6)

MaxPRACH-MidambleShifts ::= ENUMERATED {
	shift4,
	shift8,
	...,
	shift16
}

Max-Set-E-DPDCHs ::= ENUMERATED {
	vN256, vN128, vN64, vN32, vN16, vN8, vN4, v2xN4, v2xN2, v2xN2plus2xN4,
	...,
	v2xM2plus2xM4
	}
-- Values related to TS 25.212 [8]

Max-UE-DTX-Cycle ::= ENUMERATED {
	v5, v10, v20, v40, v64, v80, v128, v160,
	...,v256, v320, v512, v640, v1024, v1280
	}


MBMS-Capability ::= ENUMERATED{
mbms-capable, 
mbms-non-capable
}


MeasurementFilterCoefficient ::= ENUMERATED {k0, k1, k2, k3, k4, k5, k6, k7, k8, k9, k11, k13, k15, k17, k19,...}
-- Measurement Filter Coefficient to be used for measurement

MeasurementID ::= INTEGER (0..1048575)

Measurement-Power-Offset ::= INTEGER(-12 .. 26)
-- Actual value = IE value * 0.5

MeasurementRecoveryBehavior ::= NULL

MeasurementRecoveryReportingIndicator ::= NULL

MeasurementRecoverySupportIndicator ::= NULL

MessageStructure ::= SEQUENCE (SIZE (1..maxNrOfLevels)) OF
	SEQUENCE { 
		iE-ID					ProtocolIE-ID,
		repetitionNumber		RepetitionNumber1		OPTIONAL,
		iE-Extensions			ProtocolExtensionContainer { {MessageStructure-ExtIEs} } OPTIONAL,
		...
	}

MessageStructure-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MICH-CFN ::= INTEGER (0..4095)

MICH-Mode ::= ENUMERATED {
	v18,
	v36,
	v72,
	v144,
	...,
	v16,
	v32,
	v64,
	v128
}

MidambleConfigurationLCR ::=	ENUMERATED {v2, v4, v6, v8, v10, v12, v14, v16, ...}

MidambleConfigurationBurstType1And3 ::=		ENUMERATED {v4, v8, v16}

MidambleConfigurationBurstType2 ::=		ENUMERATED {v3, v6}

MidambleShiftAndBurstType ::=		CHOICE {	
	type1								SEQUENCE {
		midambleConfigurationBurstType1And3	MidambleConfigurationBurstType1And3,
		midambleAllocationMode 				CHOICE {
			defaultMidamble						NULL,
			commonMidamble						NULL,
			ueSpecificMidamble					MidambleShiftLong,
			...
		},
	...
	},
	type2								SEQUENCE {
		midambleConfigurationBurstType2		MidambleConfigurationBurstType2,
		midambleAllocationMode 				CHOICE {
			defaultMidamble						NULL,
			commonMidamble						NULL,
			ueSpecificMidamble					MidambleShiftShort,
			...
		},
		...
	},
	type3								SEQUENCE {
		midambleConfigurationBurstType1And3	MidambleConfigurationBurstType1And3,
		midambleAllocationMode 				CHOICE {
			defaultMidamble						NULL,
			ueSpecificMidamble					MidambleShiftLong,
		...
		},
		...
	},
	...
}

MidambleShiftLong ::=				INTEGER (0..15)

MidambleShiftShort ::=				INTEGER (0..5)

MidambleShiftLCR ::= SEQUENCE {
	midambleAllocationMode		MidambleAllocationMode,
	midambleShift				MidambleShiftLong		OPTIONAL,
	-- The IE shall be present if the Midamble Allocation Mode IE is set to "UE specific midamble".
midambleConfigurationLCR		MidambleConfigurationLCR,
	iE-Extensions				ProtocolExtensionContainer { {MidambleShiftLCR-ExtIEs} }		OPTIONAL,
	...
	}

MidambleAllocationMode ::= ENUMERATED {
	defaultMidamble,
	commonMidamble,
	uESpecificMidamble, 
	...
	}

MidambleShiftLCR-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MidambleShiftAndBurstType768 ::=		CHOICE {	
	type1								SEQUENCE {
		midambleConfigurationBurstType1And3		MidambleConfigurationBurstType1And3,
		midambleAllocationMode 				CHOICE {
			defaultMidamble						NULL,
			commonMidamble						NULL,
			ueSpecificMidamble					MidambleShiftLong,
			...
		},
		...
	},
	type2								SEQUENCE {
		midambleConfigurationBurstType2-768		MidambleConfigurationBurstType2-768,
		midambleAllocationMode 				CHOICE {
			defaultMidamble						NULL,
			commonMidamble						NULL,
			ueSpecificMidamble					MidambleShiftShort768,
			...
		},
		...
	},
	type3								SEQUENCE {
		midambleConfigurationBurstType1And3	MidambleConfigurationBurstType1And3,
		midambleAllocationMode 			CHOICE {
			defaultMidamble						NULL,
			ueSpecificMidamble					MidambleShiftLong,
			...
		},
		...
	},
	...
}

MidambleConfigurationBurstType2-768 ::=		ENUMERATED {v4, v8}

MidambleShiftShort768 ::=				INTEGER (0..7)

MIMO-ActivationIndicator ::= NULL

MIMO-Capability ::= ENUMERATED {
	mimo-capable,
	mimo-non-capable
}


MIMO-Mode-Indicator ::= ENUMERATED {
	activate,
	deactivate
}

MIMO-N-M-Ratio ::= ENUMERATED {v1-2, v2-3, v3-4, v4-5, v5-6, v6-7, v7-8, v8-9, v9-10, v1-1,...}

MIMO-PilotConfiguration ::= CHOICE {
	primary-and-secondary-CPICH				CommonPhysicalChannelID,
	normal-and-diversity-primary-CPICH		NULL,
	...
}

MIMO-PilotConfigurationExtension ::= CHOICE {
	primary-and-secondary-CPICH				PrimaryAndSecondaryCPICHContainer,
	normal-and-diversity-primary-CPICH		NormalAndDiversityPrimaryCPICHContainer,
	...
}


MIMO-PowerOffsetForS-CPICHCapability ::= ENUMERATED {
	s-CPICH-Power-Offset-Capable,  
	s-CPICH-Power-Offset-Not-Capable
}

MIMO-withfourtransmitantennas-ActivationIndicator ::= NULL

MIMO-withfourtransmitantennas-Mode-Indicator ::= ENUMERATED {
	activate,
	deactivate
}

DualStream-MIMO-withfourtransmitantennas-ActivationIndicator ::= NULL

DualStream-MIMO-withfourtransmitantennas-Mode-Indicator ::= ENUMERATED {
	activate,
	deactivate
}

MIMO-withfourtransmitantennas-PilotConfiguration ::= CHOICE {
	primary-and-secondary-CPICH				MIMO-withfourtransmitantennas-SCPICH,
	normal-and-diversity-primary-CPICH		NormalAndDiversityPrimaryCPICHContainer,
	...
}

MIMO-withfourtransmitantennas-SCPICH ::= SEQUENCE (SIZE (1.. maxSCPICHCell)) OF MIMO-withfourtransmitantennas-SCPICH-Configuration

MIMO-withfourtransmitantennas-SCPICH-Configuration ::= SEQUENCE{
	associated-S-CPICH				CommonPhysicalChannelID,
	associated-S-CPICH-poweroffset	PowerOffsetForSCPICH-DCPICHforMIMOwithfourtransmitantennas		OPTIONAL,
	associated-D-CPICH				CommonPhysicalChannelID											OPTIONAL,
	associated-D-CPICH-poweroffset	PowerOffsetForSCPICH-DCPICHforMIMOwithfourtransmitantennas		OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer {{MIMO-withfourtransmitantennas-SCPICH-Configuration-Item-ExtIEs} }		OPTIONAL,
	...
}

MIMO-withfourtransmitantennas-SCPICH-Configuration-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PowerOffsetForSCPICH-DCPICHforMIMOwithfourtransmitantennas ::= INTEGER (-12..0)
-- Unit dB, Range -10dB .. 5dB, Step +1dB

MinimumDL-PowerCapability ::=  INTEGER(0..800)
-- Unit dBm, Range -30dBm .. 50dBm, Step +0.1dB

MinimumReducedE-DPDCH-GainFactor ::= ENUMERATED {m8-15, m11-15, m15-15, m21-15, m30-15, m42-15, m60-15, m84-15,...}

MinSpreadingFactor ::= ENUMERATED {
		v4,
		v8,
		v16,
		v32,
		v64,
		v128,
		v256,
		v512
}
--  TDD Mapping scheme for the minimum spreading factor 1 and 2: "256" means 1, "512" means 2

Modification-Period ::= ENUMERATED { v1280, v2560, v5120, v10240,...}

ModifyPriorityQueue ::= CHOICE {
	addPriorityQueue			PriorityQueue-InfoItem-to-Add,
	modifyPriorityQueue			PriorityQueue-InfoItem-to-Modify,
	deletePriorityQueue			PriorityQueue-Id,
	...
}

Modulation ::= ENUMERATED {
	qPSK,
	eightPSK,
	-- 8PSK denotes 16QAM for S-CCPCH
	...
}

MinUL-ChannelisationCodeLength ::= ENUMERATED {
	v4,
	v8,
	v16,
	v32,
	v64,
	v128,
	v256,
	...
}

MultiplexingPosition ::= ENUMERATED {
	fixed,
	flexible
}

MAChs-ResetIndicator ::= ENUMERATED{
	mAChs-NotReset
}

ModulationMBSFN ::= ENUMERATED {
	qPSK,
	sixteenQAM,
	...
}

MBSFN-CPICH-secondary-CCPCH-power-offset ::= INTEGER(-11..4,...)
-- Unit dB, Step 1 dB, Range -11..4 dB.

ModulationPO-MBSFN ::= CHOICE {
	qPSK				NULL,
	sixteenQAM			MBSFN-CPICH-secondary-CCPCH-power-offset,
	...
}
MBSFN-Only-Mode-Indicator ::= ENUMERATED {
	mBSFN-Only-Mode
}

MBSFN-Only-Mode-Capability ::= ENUMERATED {
	mBSFN-Only-Mode-capable,
	mBSFN-Only-Mode-non-capable
}

Multicarrier-Number ::= INTEGER (1..maxHSDPAFrequency)

MultipleFreq-HARQ-MemoryPartitioning-InformationList ::= SEQUENCE (SIZE (1..maxFrequencyinCell-1)) OF MultipleFreq-HARQ-MemoryPartitioning-InformationItem
--Includes the 2nd through the max number of frequencies information repetitions.

MultipleFreq-HARQ-MemoryPartitioning-InformationItem ::= SEQUENCE {
	hARQ-MemoryPartitioning						HARQ-MemoryPartitioning,
	uARFCN										UARFCN,
	iE-Extensions					ProtocolExtensionContainer { { MultipleFreq-HARQ-MemoryPartitioning-InformationItem-ExtIEs} }					OPTIONAL,
	...
}

MultipleFreq-HARQ-MemoryPartitioning-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MultipleFreq-HSPDSCH-InformationList-ResponseTDDLCR ::= SEQUENCE (SIZE (1.. maxHSDPAFrequency-1)) OF MultipleFreq-HSPDSCH-InformationItem-ResponseTDDLCR
--Includes the 2nd through the max number of frequency repetitions.

MultipleFreq-HSPDSCH-InformationItem-ResponseTDDLCR ::= SEQUENCE{
	hsSCCH-Specific-Information-ResponseTDDLCR		HSSCCH-Specific-InformationRespListTDDLCR	OPTIONAL,
	hARQ-MemoryPartitioning							HARQ-MemoryPartitioning						OPTIONAL,
	uARFCN											UARFCN, -- This is the UARFCN for the second and beyond Frequency repetition.
	iE-Extensions									ProtocolExtensionContainer { { MultipleFreq-HSPDSCH-InformationItem-ResponseTDDLCR-ExtIEs } }		OPTIONAL,
	...
}

MultipleFreq-HSPDSCH-InformationItem-ResponseTDDLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
...
}

Multi-Cell-Capability ::= ENUMERATED {
	multi-Cell-Capable,
	multi-Cell-non-Capable
}

Multi-Cell-Capability-Info::= SEQUENCE {
	multi-Cell-Capability										Multi-Cell-Capability,
	possible-Secondary-Serving-Cell-List						Possible-Secondary-Serving-Cell-List		OPTIONAL,
	iE-Extensions				ProtocolExtensionContainer { { Multi-Cell-Capability-Info-ExtIEs } }		OPTIONAL,
	...
}

Multi-Cell-Capability-Info-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Multicell-EDCH-Information		::= ProtocolIE-Single-Container { {Multicell-EDCH-InformationItem} }

Multicell-EDCH-InformationItem NBAP-PROTOCOL-IES ::= {
	{ ID id-Multicell-EDCH-InformationItemIEs	CRITICALITY ignore	TYPE Multicell-EDCH-InformationItemIEs		PRESENCE mandatory }
}

Multicell-EDCH-InformationItemIEs	::= SEQUENCE {
	dL-PowerBalancing-Information				DL-PowerBalancing-Information				OPTIONAL,
	minimumReducedE-DPDCH-GainFactor			MinimumReducedE-DPDCH-GainFactor			OPTIONAL,
	secondary-UL-Frequency-Activation-State		Secondary-UL-Frequency-Activation-State		OPTIONAL,
	iE-Extensions		ProtocolExtensionContainer { { Multicell-EDCH-InformationItemIEs-ExtIEs } } OPTIONAL,
	...

}

Multicell-EDCH-InformationItemIEs-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Multicell-EDCH-RL-Specific-Information		::= ProtocolIE-Single-Container { { Multicell-EDCH-RL-Specific-InformationItem} }

Multicell-EDCH-RL-Specific-InformationItem NBAP-PROTOCOL-IES ::= {
	{ ID id-Multicell-EDCH-RL-Specific-InformationItemIEs	CRITICALITY ignore	TYPE Multicell-EDCH-RL-Specific-InformationItemIEs		PRESENCE mandatory	}
}

Multicell-EDCH-RL-Specific-InformationItemIEs::= SEQUENCE {
	extendedPropagationDelay					ExtendedPropagationDelay					OPTIONAL,
	primary-CPICH-Usage-for-Channel-Estimation	Primary-CPICH-Usage-for-Channel-Estimation	OPTIONAL,
	secondary-CPICH-Information					CommonPhysicalChannelID						OPTIONAL,
	secondary-CPICH-Information-Change			Secondary-CPICH-Information-Change			OPTIONAL,
	e-AGCH-PowerOffset							E-AGCH-PowerOffset							OPTIONAL, 
	e-RGCH-PowerOffset							E-RGCH-PowerOffset							OPTIONAL, 
	e-HICH-PowerOffset							E-HICH-PowerOffset							OPTIONAL,
	dLReferencePower							DL-Power									OPTIONAL,
	e-DCH-DL-Control-Channel-Grant				NULL	 									OPTIONAL,
	iE-Extensions		ProtocolExtensionContainer { { Multicell-EDCH-RL-Specific-InformationItemIEs-ExtIEs } } OPTIONAL,
	...

}

Multicell-EDCH-RL-Specific-InformationItemIEs-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
} 

Multicell-EDCH-Restriction ::= BOOLEAN

MIMO-SFMode-For-HSPDSCHDualStream ::= ENUMERATED {
	sF1,
	sF1SF16
}

Multi-Carrier-EDCH-Info	::=SEQUENCE{
	multicarrier-EDCH-Transport-Bearer-Mode					Multicarrier-EDCH-Transport-Bearer-Mode,
	multi-carrier-EDCH-Information							Multi-Carrier-EDCH-Information,
	iE-Extensions					ProtocolExtensionContainer { { Multi-Carrier-EDCH-Info-ExtIEs} } OPTIONAL,
	...
}

Multi-Carrier-EDCH-Info-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Multicarrier-EDCH-Transport-Bearer-Mode ::= ENUMERATED {
	separate-Iub-Transport-Bearer-Mode,
	eDCH-UL-Flow-Multiplexing-Mode,
	...
}

Multi-Carrier-EDCH-Information	::= SEQUENCE (SIZE (1..maxNrOfULCarriersLCR-1)) OF Multi-Carrier-EDCH-LCR-InformationItem

Multi-Carrier-EDCH-LCR-InformationItem	::=SEQUENCE{
	uARFCN										UARFCN,
	sNPL-carrier-group-indicator				SNPL-Carrier-Group-Indicator		OPTIONAL,
	pRXdes-base									PRXdes-base,
	multi-Carrier-EDCH-MACdFlows-Information-TDD	Multi-Carrier-EDCH-MACdFlows-Information-TDD		OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { Multi-Carrier-EDCH-LCR-InformationItem-ExtIEs} } OPTIONAL,
	...
}

Multi-Carrier-EDCH-LCR-InformationItem-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SNPL-Carrier-Group-Indicator ::= INTEGER (1..3)
-- for multi-carrier E-DCH operation 1.28Mcps TDD only

Multi-Carrier-EDCH-MACdFlows-Information-TDD ::= SEQUENCE (SIZE (1.. maxNrOfEDCHMACdFlows)) OF Multi-Carrier-EDCH-MACdFlows-Specific-Info

Multi-Carrier-EDCH-MACdFlows-Specific-Info ::= SEQUENCE {
	e-DCH-MACdFlow-ID								E-DCH-MACdFlow-ID,
	bindingID										BindingID,
	transportLayerAddress							TransportLayerAddress,
	iE-Extensions									ProtocolExtensionContainer { { Multi-Carrier-EDCH-MACdFlows-Specific-Info-ExtIEs} }				OPTIONAL,
	...
}

Multi-Carrier-EDCH-MACdFlows-Specific-Info-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}


Multi-Carrier-EDCH-Reconfigure ::= SEQUENCE{
	continue-setup-change-Of-Multi-Carrier-EDCH							Continue-Setup-Change-Multi-Carrier-EDCH,
	iE-Extensions					ProtocolExtensionContainer { { Multi-Carrier-EDCH-Reconfigure-ExtIEs} } OPTIONAL,
	...
}

Multi-Carrier-EDCH-Reconfigure-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Continue-Setup-Change-Multi-Carrier-EDCH ::= CHOICE {
	continue				NULL,
	setup					Multi-Carrier-EDCH-Info,
	change					Multi-Carrier-EDCH-Change-Info,
	...
}

Multi-Carrier-EDCH-Change-Info	::= SEQUENCE{
	multicarrier-EDCH-Transport-Bearer-Mode					Multicarrier-EDCH-Transport-Bearer-Mode	OPTIONAL,
	multi-carrier-EDCH-Information							Multi-Carrier-EDCH-Information			OPTIONAL,
	multi-Carrier-EDCH-Information-Removal-List				Multi-Carrier-EDCH-Information-Removal-List	OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { Multi-Carrier-EDCH-Change-Info-ExtIEs} } OPTIONAL,
	...
}

Multi-Carrier-EDCH-Change-Info-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}


Multi-Carrier-EDCH-Information-Removal-List	::= SEQUENCE (SIZE (1..maxNrOfULCarriersLCR-1)) OF Multi-Carrier-EDCH-Information-Removal-Info-ItemIEs

Multi-Carrier-EDCH-Information-Removal-Info-ItemIEs	::=SEQUENCE{
	uARFCN							UARFCN,
	iE-Extensions					ProtocolExtensionContainer { { Multi-Carrier-EDCH-Information-Removal-Info-ItemIEs-ExtIEs} } OPTIONAL,
	...
}

Multi-Carrier-EDCH-Information-Removal-Info-ItemIEs-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Multi-Carrier-EDCH-Information-Response	::= SEQUENCE (SIZE (1..maxNrOfULCarriersLCR-1)) OF Multi-Carrier-EDCH-LCR-Information-ResponseItem

Multi-Carrier-EDCH-LCR-Information-ResponseItem	::=SEQUENCE{
	uARFCN										UARFCN,
	e-DCH-TDD-MACdFlow-Specific-InformationResp		E-DCH-TDD-MACdFlow-Specific-InformationResp	OPTIONAL,
	e-AGCH-Specific-Information-ResponseTDD			E-AGCH-Specific-InformationRespListTDD	OPTIONAL,
	scheduled-E-HICH-Specific-InformationResp		Scheduled-E-HICH-Specific-Information-ResponseLCRTDD	OPTIONAL,	-- 1.28Mcps TDD only
	iE-Extensions					ProtocolExtensionContainer { { Multi-Carrier-EDCH-LCR-Information-ResponseItem-ExtIEs} } OPTIONAL,
	...
}

Multi-Carrier-EDCH-LCR-Information-ResponseItem-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Multiflow-Reconfiguration ::= CHOICE {
	setup						Multiflow-Information,
	change						Multiflow-Information-To-Modify,
	stop						Multiflow-Stop,
	...
}

Multiflow-Information ::= SEQUENCE {
	total-Number-of-HS-DSCH-Cells			INTEGER (2..32,...),
	role				 					Multiflow-Role,
	mimo									Multiflow-MIMO,
	timing									Multiflow-Timing						OPTIONAL,
	max-Number-of-HS-SCCH-Sets-per-NodeB 	INTEGER (1..16,...)						OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { Multiflow-Information-ExtIEs } }			OPTIONAL,
	...
}

Multiflow-Information-To-Modify ::= SEQUENCE {
	total-Number-of-HS-DSCH-Cells			INTEGER (2..32,...)						OPTIONAL,
	role				 					Multiflow-Role		 					OPTIONAL,
	mimo									Multiflow-MIMO							OPTIONAL,
	timing									Multiflow-Timing						OPTIONAL,
	max-Number-of-HS-SCCH-Sets-per-NodeB	INTEGER (1..16,...)						OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { Multiflow-Information-To-Modify-ExtIEs } }			OPTIONAL,
	...
}

Multiflow-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-Assisting-RepetitionFactors	CRITICALITY ignore	EXTENSION Multiflow-RepetitionFactors	PRESENCE optional},
	...
}

Multiflow-Information-To-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-Assisting-RepetitionFactors	CRITICALITY ignore	EXTENSION Multiflow-RepetitionFactors	PRESENCE optional},
	...
}

Multiflow-RepetitionFactors ::= SEQUENCE {
	assisting-CQI-RepetitionFactor			CQI-RepetitionFactor					OPTIONAL,
	assisting-AckNack-RepetitionFactor		AckNack-RepetitionFactor				OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { Multiflow-RepetitionFactors-ExtIEs } }		OPTIONAL,
	...
}

Multiflow-RepetitionFactors-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Multiflow-Stop ::= ENUMERATED {
	stop,
	...
}

Multiflow-Role ::= ENUMERATED {
	primary,
	assisting,
	...
}

Multiflow-MIMO ::= ENUMERATED {
	on,
	off,
	...
}

Multiflow-Timing ::= CHOICE {
	time-Reference						NULL,
	non-Time-Reference					INTEGER	(0..30,...),
	-- Unit: chip, step size 256 chips
	-- example: 0 = 0chip, 1 = 256chips
	...
}

Multiflow-OrdinalNumberOfFrequency ::= INTEGER (1..32,...)

MU-MIMO-Capability-ContainerLCR ::= BIT STRING (SIZE (8))
-- First bit: DL MU-MIMO Capability Cell Specific Tx Diversity Handling For Multi Cell Operation Capability
-- Second bit: The second bit: UL MU-MIMO Capability Multi Cell and MIMO Capability
-- Third bit: Standalone Midamble Capability Multi Cell and Single Stream MIMO Capability.
-- Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver.

MU-MIMO-InformationLCR ::= SEQUENCE {
	mU-MIMO-IndicatorLCR									MU-MIMO-IndicatorLCR,
	standalone-Midamble-Channel-Information-RequestLCR		Standalone-Midamble-Channel-Information-RequestLCR				OPTIONAL,
	standalone-Midamble-Channel-Information					Standalone-Midamble-Channel-Information OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { MU-MIMO-InformationLCR-ExtIEs} } OPTIONAL,
	...
}

Standalone-Midamble-Channel-Information-RequestLCR ::= ENUMERATED {
	stand-alone-Midamble-Resource-Requested,
	stand-alone-Midamble-Resource-not-Requested
}

Standalone-Midamble-Channel-Information ::= SEQUENCE {
	standalone-Midamble-Configuratnion	Standalone-Midamble-Configuratnion,
	standalone-MidambleShift			Standalone-MidambleShift,
	timeslotLCR							TimeSlotLCR,
	repetitionPeriod					Standalone-Midamble-RepetitionPeriod,
	offset								Standalone-Midamble-Offset,
	referenceBeta						ReferenceBeta					OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { Standalone-Midamble-Channel-Information-ExtIEs} } OPTIONAL,
	...
}

Standalone-Midamble-Configuratnion::= ENUMERATED {
	v2,
	v4,
	v6,
	v8,
	v10,
	v12,
	v14,
	v16,
	...
}

Standalone-MidambleShift ::= INTEGER (0..15)

Standalone-Midamble-RepetitionPeriod ::= ENUMERATED {
	v1,
	v2,
	v4,
	v8,
	v16,
	v32,
	v64,
	...
}

Standalone-Midamble-Offset ::= INTEGER (0..63)

ReferenceBeta ::= INTEGER (-15..16)

Standalone-Midamble-Channel-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MU-MIMO-InformationLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MU-MIMO-Information-Response ::= SEQUENCE {
	mU-MIMO-Usage-IndicatorLCR						MU-MIMO-Usage-IndicatorLCR,
	standalone-Midamble-Channel-Information		Standalone-Midamble-Channel-Information OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { MU-MIMO-Information-Response-ExtIEs} } OPTIONAL,
	...
}

MU-MIMO-Information-Response-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MU-MIMO-Information-To-ReconfigureLCR ::= CHOICE {
	mU-MIMO-Information-To-Modify			MU-MIMO-Information-To-Modify,
	mU-MIMO-Information-To-Continue			NULL,
	...
}

MU-MIMO-Information-To-Modify ::= SEQUENCE {
	mU-MIMO-IndicatorLCR				MU-MIMO-IndicatorLCR		OPTIONAL,
	standalone-Midamble-Configuratnion	Standalone-Midamble-Configuratnion		OPTIONAL,
	standalone-MidambleShift			Standalone-MidambleShift	OPTIONAL,
	timeslotLCR							TimeSlotLCR					OPTIONAL,
	repetitionPeriod					Standalone-Midamble-RepetitionPeriod		OPTIONAL,
	offset								Standalone-Midamble-Offset		OPTIONAL,
	referenceBeta						ReferenceBeta					OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { MU-MIMO-Information-To-Modify-ExtIEs} } OPTIONAL,
	...
}

MU-MIMO-Information-To-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

MU-MIMO-IndicatorLCR::= ENUMERATED {
	uL-Only,
	dL-Only,
	uL-and-DL,
	...
}

MU-MIMO-Usage-IndicatorLCR ::= ENUMERATED {
	mU-MIMO-Used,
	mU-MIMO-Not-Used,
	...
}

-- ==========================================
--	N
-- ==========================================

Nack-Power-Offset ::= INTEGER (0..8,..., 9..10)
-- According to mapping in ref. TS 25.213 [9] subclause 4.2.1

NCyclesPerSFNperiod ::= ENUMERATED {
	v1,
	v2,
	v4,
	v8,
	...,
	v16,
	v32,
	v64
}

NRepetitionsPerCyclePeriod ::= INTEGER (2..10)

N-INSYNC-IND ::= INTEGER (1..256)

N-OUTSYNC-IND ::= INTEGER (1..256)

N-PROTECT ::= INTEGER(0..7)

NeighbouringCellMeasurementInformation ::= SEQUENCE (SIZE (1..maxNrOfMeasNCell)) OF
		CHOICE {
				neighbouringFDDCellMeasurementInformation		NeighbouringFDDCellMeasurementInformation, -- FDD only
				neighbouringTDDCellMeasurementInformation		NeighbouringTDDCellMeasurementInformation,
				-- Applicable to 3.84Mcps TDD only
				...,
				extension-neighbouringCellMeasurementInformation	Extension-neighbouringCellMeasurementInformation
			}

NodeB-Triggered-HSDPCCH-Transmission-Information ::= SEQUENCE {
	hS-DPCCH-transmission-continuation-backoff				HS-DPCCH-transmission-continuation-backoff,
	iE-Extensions					ProtocolExtensionContainer  { { NodeB-Triggered-HSDPCCH-Transmission-Information-ExtIEs} }		OPTIONAL,
	...
}

NodeB-Triggered-HSDPCCH-Transmission-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Extension-neighbouringCellMeasurementInformation	::=	ProtocolIE-Single-Container {{ Extension-neighbouringCellMeasurementInformationIE }}

Extension-neighbouringCellMeasurementInformationIE NBAP-PROTOCOL-IES ::= {
	{ ID id-neighbouringTDDCellMeasurementInformationLCR	CRITICALITY reject	TYPE NeighbouringTDDCellMeasurementInformationLCR	PRESENCE mandatory }|	-- Applicable to 1.28Mcps TDD only
	{ ID id-neighbouringTDDCellMeasurementInformation768	CRITICALITY reject	TYPE NeighbouringTDDCellMeasurementInformation768	PRESENCE mandatory },	-- Applicable to 7.68Mcps TDD only
	...
}

NeighbouringFDDCellMeasurementInformation ::= SEQUENCE {
	uC-Id								UC-Id,
	uARFCN								UARFCN,
	primaryScramblingCode				PrimaryScramblingCode,
	iE-Extensions						ProtocolExtensionContainer { { NeighbouringFDDCellMeasurementInformationItem-ExtIEs} } OPTIONAL,
	...
}

NeighbouringFDDCellMeasurementInformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

NeighbouringTDDCellMeasurementInformation ::= SEQUENCE {
	uC-Id								UC-Id,
	uARFCN								UARFCN,
	cellParameterID						CellParameterID,
	timeSlot							TimeSlot						OPTIONAL,
	midambleShiftAndBurstType			MidambleShiftAndBurstType		OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { NeighbouringTDDCellMeasurementInformationItem-ExtIEs} } OPTIONAL,
	...
}

NeighbouringTDDCellMeasurementInformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

NeighbouringTDDCellMeasurementInformationLCR ::= SEQUENCE {
	uC-Id								UC-Id,
	uARFCN								UARFCN,
	cellParameterID						CellParameterID,
	timeSlotLCR							TimeSlotLCR				OPTIONAL,
	midambleShiftLCR					MidambleShiftLCR		OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { NeighbouringTDDCellMeasurementInformationLCRItem-ExtIEs} } OPTIONAL,
	...
}

NeighbouringTDDCellMeasurementInformationLCRItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

NeighbouringTDDCellMeasurementInformation768 ::= SEQUENCE {
	uC-Id								UC-Id,
	uARFCN								UARFCN,
	cellParameterID						CellParameterID,
	timeSlot							TimeSlot						OPTIONAL,
	midambleShiftAndBurstType768		MidambleShiftAndBurstType768		OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { NeighbouringTDDCellMeasurementInformation768Item-ExtIEs} } OPTIONAL,
	...
}

NeighbouringTDDCellMeasurementInformation768Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Non-rectangular-resource-allocation-indicator ::= ENUMERATED {
	activate
}

Non-rectangular-resource-timeslot-set ::= BIT STRING (SIZE (7))

NonCellSpecificTxDiversity ::= ENUMERATED {
	txDiversity,
	...
}

Non-Serving-RL-Preconfig-Setup	::=	SEQUENCE {
	new-non-serving-RL-selection	New-non-serving-RL-setup-selection,
	iE-Extensions			ProtocolExtensionContainer { {Non-Serving-RL-Preconfig-Setup-ExtIEs} } OPTIONAL,
	...
}

Non-Serving-RL-Preconfig-Setup-ExtIEs	NBAP-PROTOCOL-EXTENSION::=	{
	{ID id-Additional-E-DCH-Non-Serving-RL-Preconfiguration-Setup	CRITICALITY ignore	EXTENSION Additional-E-DCH-Non-Serving-RL-Preconfiguration-Setup PRESENCE optional },
	...
}

Additional-E-DCH-Non-Serving-RL-Preconfiguration-Setup	::= NULL


New-non-serving-RL-setup-selection	::=	CHOICE {
	new-Serving-RL-in-NodeB					NULL,
	new-Serving-RL-Not-in-NodeB				NULL,
	new-Serving-RL-in-or-Not-in-NodeB		NULL,
	...
}


Non-Serving-RL-Preconfig-Info	::=	SEQUENCE {
	new-non-serving-RL-E-DCH-FDD-DL-Control-Channel-Information-A	E-DCH-FDD-DL-Control-Channel-Information OPTIONAL,
	new-non-serving-RL-E-DCH-FDD-DL-Control-Channel-Information-B 	E-DCH-FDD-DL-Control-Channel-Information OPTIONAL,
	new-non-serving-RL-E-DCH-FDD-DL-Control-Channel-Information-C 	E-DCH-FDD-DL-Control-Channel-Information OPTIONAL,
	iE-Extensions			ProtocolExtensionContainer { {Non-Serving-RL-Preconfig-Info-ExtIEs} } OPTIONAL,
	...
}

Non-Serving-RL-Preconfig-Info-ExtIEs	NBAP-PROTOCOL-EXTENSION	::=	{
	{ID id-Additional-E-DCH-New-non-serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList	CRITICALITY ignore	EXTENSION Additional-E-DCH-New-non-serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList PRESENCE optional}|
	{ID id-FTPICH-Information							CRITICALITY ignore	EXTENSION FTPICH-Information				PRESENCE optional},
	...
}

Additional-E-DCH-New-non-serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList	::=	SEQUENCE(SIZE(1.. maxNrOfEDCH-1)) OF SEQUENCE { 
	new-non-serving-RL-E-DCH-FDD-DL-Control-Channel-Information-A	E-DCH-FDD-DL-Control-Channel-Information OPTIONAL,
	new-non-serving-RL-E-DCH-FDD-DL-Control-Channel-Information-B	E-DCH-FDD-DL-Control-Channel-Information OPTIONAL,
	new-non-serving-RL-E-DCH-FDD-DL-Control-Channel-Information-C	E-DCH-FDD-DL-Control-Channel-Information OPTIONAL,
	iE-Extensions			ProtocolExtensionContainer { { Additional-E-DCH-New-non-serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList-ExtIEs} } OPTIONAL,
	...
}

Additional-E-DCH-New-non-serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
...
}


NI-Information ::= SEQUENCE (SIZE (1..maxNrOfNIs)) OF Notification-Indicator

Notification-Indicator ::= INTEGER (0..65535)


NodeB-CommunicationContextID ::= INTEGER (0..1048575)

NormalAndDiversityPrimaryCPICHContainer ::= SEQUENCE {
		iE-Extensions						ProtocolExtensionContainer { { NormalAndDiversityPrimaryCPICHContainer-ExtIEs} } OPTIONAL,
	...
}
 
NormalAndDiversityPrimaryCPICHContainer-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


NotificationIndicatorLength ::= ENUMERATED {
	v2,
	v4,
	v8,
	...
}


NumberOfReportedCellPortions ::= INTEGER (1..maxNrOfCellPortionsPerCell,...) 

NumberOfReportedCellPortionsLCR ::= INTEGER (1..maxNrOfCellPortionsPerCellLCR,...)

Number-of-PCCH-transmission ::= INTEGER (1..5)

NSubCyclesPerCyclePeriod ::= INTEGER (1..16,...)

N-E-UCCH ::= INTEGER (1..12)

N-E-UCCHLCR ::= INTEGER (1..8)

Number-Of-Supported-Carriers  ::= ENUMERATED {
	one-one-carrier,
	one-three-carrier,
	three-three-carrier,
	one-six-carrier,
	three-six-carrier,
	six-six-carrier,
	...,
	one-two-carrier-discontiguous,
	two-two-carrier-discontiguous,
	one-two-carrier-contiguous,
	two-two-carrier-contiguous
}

NumHS-SCCH-Codes ::= INTEGER (1..maxNrOfHSSCCHCodes)

NoOfTargetCellHS-SCCH-Order::= INTEGER (1..30)

-- ==========================================
--	O
-- ==========================================

OrdinalNumberOfFrequency ::= INTEGER (1..32,...)

Out-of-Sychronization-Window ::= ENUMERATED {
	ms40,
	ms80,
	ms160,
	ms320,
	ms640,
	...
}

One-level-DRX ::= SEQUENCE {
	hS-DSCH-second-Rx-burst-FACH		HS-DSCH-second-Rx-burst-FACH							OPTIONAL,
	t32y								T32y													OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { One-level-DRX-ExtIEs } }	OPTIONAL,
	...
}

One-level-DRX-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- ==========================================
--	P
-- ==========================================

PagingIndicatorLength ::= ENUMERATED {
	v2,
	v4,
	v8,
	...
}

Paging-MACFlow-ID ::= INTEGER (0..maxNrOfPagingMACFlow-1)


PayloadCRC-PresenceIndicator ::= ENUMERATED {
	cRC-Included,
	cRC-NotIncluded,
	...
}

PCCPCH-Power ::= INTEGER (-150..400,...)
-- PCCPCH-power = power * 10
-- If power <= -15 PCCPCH shall be set to -150
-- If power >= 40 PCCPCH shall be set to 400
-- Unit dBm, Range -15dBm .. +40 dBm, Step +0.1dB

PDSCH-ID ::= INTEGER (0..255)

PDSCH-ID768 ::= INTEGER (0..511)

PDSCHSet-ID ::= INTEGER (0..255)

PICH-Mode ::= ENUMERATED {
	v18,
	v36,
	v72,
	v144,
	...
}

PICH-Power ::= INTEGER (-10..5)
-- Unit dB, Range -10dB .. +5dB, Step +1dB

Paging-MACFlows-to-DeleteFDD ::= SEQUENCE (SIZE (1.. maxNrOfPagingMACFlow)) OF Paging-MACFlows-to-DeleteFDD-Item

Paging-MACFlows-to-DeleteFDD-Item ::= SEQUENCE {
	paging-MACFlow-ID								Paging-MACFlow-ID,
	iE-Extensions									ProtocolExtensionContainer { { Paging-MACFlows-to-DeleteFDD-Item-ExtIEs} }					OPTIONAL,
	...
}

Paging-MACFlows-to-DeleteFDD-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


Paging-MACFlow-Specific-Information ::= SEQUENCE (SIZE (1.. maxNrOfPagingMACFlow)) OF Paging-MAC-Flow-Specific-Information-Item

Paging-MAC-Flow-Specific-Information-Item ::= SEQUENCE {
	paging-MACFlow-Id								Paging-MACFlow-ID,
	hSDPA-associated-PICH-Info						HSDPA-Associated-PICH-Information, 
	bindingID										BindingID									OPTIONAL,
	transportLayerAddress							TransportLayerAddress						OPTIONAL,
	tnl-qos											TnlQos										OPTIONAL,
	toAWS											ToAWS,
	toAWE											ToAWE,
	paging-MACFlow-PriorityQueue-Information		Paging-MACFlow-PriorityQueue-Information	OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { Paging-MAC-Flow-Specific-Information-Item-ExtIEs } }		OPTIONAL,
	...
}

Paging-MAC-Flow-Specific-Information-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TransportBearerRequestIndicator 	CRITICALITY ignore	 EXTENSION TransportBearerRequestIndicator 	PRESENCE optional},
-- This IE should not be contained if the MAC flow is setup in procedure, and it should be contained if the MAC flow is modified in procedure.
	...
}

Paging-MACFlow-PriorityQueue-Information  ::= SEQUENCE (SIZE (1..maxNrOfpagingMACQueues)) OF Paging-MACFlow-PriorityQueue-Item

Paging-MACFlow-PriorityQueue-Item  ::= SEQUENCE {
	priority-Queue-Information-for-Enhanced-PCH		Priority-Queue-Information-for-Enhanced-FACH-PCH,
		iE-Extensions									ProtocolExtensionContainer { { Paging-MACFlow-PriorityQueue-Item-ExtIEs } }		OPTIONAL,
	...
}

Paging-MACFlow-PriorityQueue-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Pattern-Sequence-Identifier ::= INTEGER (1.. maxNrOfDCHMeasurementOccasionPatternSequence)

PhysicalChannelID-for-CommonERNTI-RequestedIndicator ::= ENUMERATED {
	requested
}

PLCCHsequenceNumber ::= INTEGER (0..14)

PLCCHinformation ::= SEQUENCE {
	commonPhysicalChannelID					CommonPhysicalChannelID,
	sequenceNumber							PLCCHsequenceNumber,
	iE-Extensions							ProtocolExtensionContainer { { PLCCHinformation-ExtIEs} }		OPTIONAL,
	...
}

PLCCHinformation-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

--"maxNrOfHSDSCH-1" represents the maximum number of possible secondary serving cells for a local cell when it applies to the range of "Possible-Secondary-Serving-Cell-List".

Possible-Secondary-Serving-Cell-List ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Possible-Secondary-Serving-Cell

Possible-Secondary-Serving-Cell ::= SEQUENCE {
	local-Cell-ID				Local-Cell-ID,
	iE-Extensions				ProtocolExtensionContainer { { Possible-Secondary-Serving-Cell-ExtIEs } }			OPTIONAL,
	...
}

Possible-Secondary-Serving-Cell-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-Multicell-EDCH-Restriction		CRITICALITY ignore	EXTENSION Multicell-EDCH-Restriction	PRESENCE optional},
	...
}

PowerAdjustmentType ::= ENUMERATED {
	none,
	common,
	individual
}

PowerOffset ::= INTEGER (0..24)
-- PowerOffset = offset * 0.25
-- Unit dB, Range 0dB .. +6dB, Step +0.25dB

PowerOffsetForSecondaryCPICHforMIMO ::= INTEGER (-6..0)
-- Unit dB, Range -6dB .. 0dB, Step +1dB

PowerRaiseLimit ::= INTEGER (0..10)

PRACH-Midamble ::= ENUMERATED {
	inverted,
	direct,
	...
}

PRC ::= INTEGER (-2047..2047)
--pseudo range correction; scaling factor 0.32 meters

PRCDeviation ::= ENUMERATED {
   one,
   two,
   five,
   ten,
   ...
}

PrecodingWeightSetRestriction ::= ENUMERATED {
	preferred,
	not-preferred
}

Precoder-Weight-Set-Restriction ::= BIT STRING (SIZE (64))

PreambleSignatures ::= BIT STRING {
									signature15(0),
									signature14(1),
									signature13(2),
									signature12(3),
									signature11(4),
									signature10(5),
									signature9(6),
									signature8(7),
									signature7(8),
									signature6(9),
									signature5(10),
									signature4(11),
									signature3(12),
									signature2(13),
									signature1(14),
									signature0(15)
									} (SIZE (16))

PreambleThreshold ::= INTEGER (0..72)
-- 0= -36.0dB, 1= -35.5dB, ... , 72= 0.0dB

PredictedSFNSFNDeviationLimit ::=INTEGER (1..256)
-- Unit chip, Step 1/16 chip, Range 1/16..16 chip

PredictedTUTRANGPSDeviationLimit ::= INTEGER (1..256)
-- Unit chip, Step 1/16 chip, Range 1/16..16 chip

Pre-emptionCapability ::= ENUMERATED {
	shall-not-trigger-pre-emption,
	may-trigger-pre-emption
}

Pre-emptionVulnerability ::= ENUMERATED {
	not-pre-emptable,
	pre-emptable
}

PrimaryAndSecondaryCPICHContainer ::= SEQUENCE {
	power-Offset-For-Secondary-CPICH-for-MIMO		PowerOffsetForSecondaryCPICHforMIMO,
	iE-Extensions						ProtocolExtensionContainer { { PrimaryAndSecondaryCPICHContainer-ExtIEs} } OPTIONAL,
	...
}
 

PrimaryAndSecondaryCPICHContainer-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PrimaryCPICH-Power ::= INTEGER(-100..500)
-- step 0.1 (Range –10.0..50.0) Unit is dBm

Primary-CPICH-Usage-for-Channel-Estimation ::= ENUMERATED {
primary-CPICH-may-be-used,
primary-CPICH-shall-not-be-used
}

PrimaryScramblingCode ::= INTEGER (0..511)

PriorityLevel				::= INTEGER (0..15)
-- 0 = spare, 1 = highest priority, ...14 = lowest priority and 15 = no priority

Priority-Queue-Information-for-Enhanced-FACH-PCH ::= SEQUENCE {
	priorityQueue-Id					PriorityQueue-Id,
	schedulingPriorityIndicator			SchedulingPriorityIndicator,
	t1									T1,
	mAC-ehs-Reset-Timer					MAC-ehs-Reset-Timer,
	-- shall be ignored in case of Enhanced PCH
	discardTimer						DiscardTimer							OPTIONAL,
	mAC-hsWindowSize					MAC-hsWindowSize,
	maximum-MACcPDU-Size				MAC-PDU-SizeExtended,
	iE-Extensions						ProtocolExtensionContainer { { Priority-Queue-Information-for-Enhanced-FACH-PCH-ExtIEs } }			OPTIONAL,
	...
}

Priority-Queue-Information-for-Enhanced-FACH-PCH-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PriorityQueue-Id ::= INTEGER (0..maxNrOfPriorityQueues-1)

PriorityQueue-InfoList ::= SEQUENCE (SIZE (1..maxNrOfPriorityQueues)) OF PriorityQueue-InfoItem

PriorityQueue-InfoItem ::= SEQUENCE {
	priorityQueueId						PriorityQueue-Id,
	associatedHSDSCH-MACdFlow			HSDSCH-MACdFlow-ID,
	schedulingPriorityIndicator			SchedulingPriorityIndicator,
	t1									T1,
	discardTimer						DiscardTimer				OPTIONAL,
	mAC-hsWindowSize					MAC-hsWindowSize,
	mAChsGuaranteedBitRate				MAChsGuaranteedBitRate										OPTIONAL,
	macdPDU-Size-Index					MACdPDU-Size-Indexlist,
	rLC-Mode							RLC-Mode,
	iE-Extensions						ProtocolExtensionContainer { { PriorityQueue-InfoItem-ExtIEs} }		OPTIONAL,
	...
}

PriorityQueue-InfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MaximumMACdPDU-SizeExtended		CRITICALITY reject		EXTENSION	MAC-PDU-SizeExtended	PRESENCE optional}|
	{ ID id-DL-RLC-PDU-Size-Format			CRITICALITY ignore		EXTENSION	DL-RLC-PDU-Size-Format		PRESENCE optional}|
	{ ID id-UE-AggregateMaximumBitRate-Enforcement-Indicator	CRITICALITY ignore	EXTENSION	UE-AggregateMaximumBitRate-Enforcement-Indicator	PRESENCE optional},
	...
}

PriorityQueue-InfoList-to-Modify ::= SEQUENCE (SIZE (1..maxNrOfPriorityQueues)) OF ModifyPriorityQueue

PriorityQueue-InfoItem-to-Add ::= SEQUENCE {
	priorityQueueId						PriorityQueue-Id,
	associatedHSDSCH-MACdFlow			HSDSCH-MACdFlow-ID,
	schedulingPriorityIndicator			SchedulingPriorityIndicator,
	t1									T1,
	discardTimer						DiscardTimer												OPTIONAL,
	mAC-hsWindowSize					MAC-hsWindowSize,
	mAChsGuaranteedBitRate				MAChsGuaranteedBitRate										OPTIONAL,
	macdPDU-Size-Index					MACdPDU-Size-Indexlist,
	rLC-Mode							RLC-Mode,
	iE-Extensions						ProtocolExtensionContainer { { PriorityQueue-InfoItem-to-Add-ExtIEs} }		OPTIONAL,
	...
}

PriorityQueue-InfoItem-to-Add-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MaximumMACdPDU-SizeExtended		CRITICALITY reject		EXTENSION	MAC-PDU-SizeExtended		PRESENCE optional} |
	{ ID id-DL-RLC-PDU-Size-Format				CRITICALITY ignore		EXTENSION	DL-RLC-PDU-Size-Format	PRESENCE optional},
	...
}

PriorityQueue-InfoItem-to-Modify ::= SEQUENCE {
	priorityQueueId						PriorityQueue-Id,
	schedulingPriorityIndicator			SchedulingPriorityIndicator									OPTIONAL,
	t1									T1															OPTIONAL,
	discardTimer						DiscardTimer												OPTIONAL,
	mAC-hsWindowSize					MAC-hsWindowSize											OPTIONAL,
	mAChsGuaranteedBitRate				MAChsGuaranteedBitRate										OPTIONAL,
	macdPDU-Size-Index-to-Modify		MACdPDU-Size-Indexlist-to-Modify							OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { PriorityQueue-InfoItem-to-Modify-ExtIEs} }		OPTIONAL,
	...
}

PriorityQueue-InfoItem-to-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-MaximumMACdPDU-SizeExtended		CRITICALITY reject		EXTENSION	MAC-PDU-SizeExtended	PRESENCE optional}|
	{ ID id-DL-RLC-PDU-Size-Format			CRITICALITY ignore		EXTENSION	DL-RLC-PDU-Size-Format	PRESENCE optional},
	...
}

PriorityQueue-InfoList-to-Modify-Unsynchronised ::= SEQUENCE (SIZE (1..maxNrOfPriorityQueues)) OF PriorityQueue-InfoItem-to-Modify-Unsynchronised

PriorityQueue-InfoItem-to-Modify-Unsynchronised ::= SEQUENCE {
	priorityQueueId						PriorityQueue-Id,
	schedulingPriorityIndicator			SchedulingPriorityIndicator															OPTIONAL,
	discardTimer						DiscardTimer																		OPTIONAL,
	mAChsGuaranteedBitRate				MAChsGuaranteedBitRate																OPTIONAL,
	iE-Extensions						ProtocolExtensionContainer { { PriorityQueue-InfoItem-to-Modify-Unsynchronised-ExtIEs} }		OPTIONAL,
	...
}

PriorityQueue-InfoItem-to-Modify-Unsynchronised-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PrimaryCCPCH-RSCP ::= INTEGER (0..91)
-- Mapping of non-negative values according to TS 25.123 [23]

PrimaryCCPCH-RSCP-Delta	::= INTEGER (-5..-1,...)
-- Mapping of negative values according to TS 25.123 [23]

PropagationDelay ::= INTEGER (0..255)
-- Unit: chips, step size 3 chips
-- example: 0 = 0chip, 1 = 3chips

PRXdes-base ::= INTEGER (-112..-50)
-- Unit: dBm, step size 1


SCH-TimeSlot ::= INTEGER (0..6)

PunctureLimit ::= INTEGER (0..15)
-- 0: 40%; 1: 44%; ... 14: 96%; 15: 100%
-- 0 is not applicable for E-DPCH

PUSCH-ID ::= INTEGER (0..255)

UE-Selected-MBMS-Service-Information ::= CHOICE {
	none							NULL,
	selected-MBMS-Service			Selected-MBMS-Service,
	...
}
Selected-MBMS-Service ::= SEQUENCE {
	selected-MBMS-Service-List				Selected-MBMS-Service-List,
	iE-Extensions							ProtocolExtensionContainer { { Selected-MBMS-Service-ExtIEs} }		OPTIONAL,
	...
}

Selected-MBMS-Service-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}


Selected-MBMS-Service-List ::= SEQUENCE (SIZE (1.. maxMBMSServiceSelect)) OF Selected-MBMS-Service-Item


Selected-MBMS-Service-Item ::= SEQUENCE {
	selected-MBMS-Service-TimeSlot-Information-LCR			Selected-MBMS-Service-TimeSlot-Information-LCR		OPTIONAL,
	mBMS-Service-TDM-Information			MBMS-Service-TDM-Information		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { Selected-MBMS-Service-Item-ExtIEs} }		OPTIONAL,
	...
}

Selected-MBMS-Service-Item-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Selected-MBMS-Service-TimeSlot-Information-LCR ::= SEQUENCE (SIZE (1..7)) OF TimeSlotLCR

MBMS-Service-TDM-Information ::= SEQUENCE {
	transmission-Time-Interval			ENUMERATED {v10, v20, v40, v80,...},
	tDM-Rep					INTEGER (2..9),
	tDM-Offset				INTEGER (0..8),
	tDM-Length				INTEGER (1..8),
	iE-Extensions							ProtocolExtensionContainer { { MBMS-Service-TDM-Information-ExtIEs} }		OPTIONAL,
	...
}

MBMS-Service-TDM-Information-ExtIEs  NBAP-PROTOCOL-EXTENSION ::= {
	...
}

PUSCHSet-ID ::= INTEGER (0..255)

Paging-MACFlow-Specific-InformationLCR ::= SEQUENCE (SIZE (1.. maxNrOfPagingMACFlow)) OF Paging-MAC-Flow-Specific-Information-ItemLCR

Paging-MAC-Flow-Specific-Information-ItemLCR ::= SEQUENCE {
	paging-MACFlow-Id								Paging-MACFlow-ID,
	hSDPA-associated-PICH-InfoLCR					HSDPA-Associated-PICH-InformationLCR		OPTIONAL,
	bindingID										BindingID									OPTIONAL,
	transportLayerAddress							TransportLayerAddress						OPTIONAL,
	tnl-qos											TnlQos										OPTIONAL,
	toAWS											ToAWS										OPTIONAL,
	toAWE											ToAWE										OPTIONAL,
	paging-MACFlow-PriorityQueue-InformationLCR		Paging-MACFlow-PriorityQueue-Information	OPTIONAL,
	transportBearerRequestIndicator					TransportBearerRequestIndicator				OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { Paging-MAC-Flow-Specific-Information-ItemLCR-ExtIEs } }		OPTIONAL,
	...
}

Paging-MAC-Flow-Specific-Information-ItemLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Paging-MACFlows-to-DeleteLCR ::= SEQUENCE (SIZE (1.. maxNrOfPagingMACFlow)) OF Paging-MACFlows-to-DeleteLCR-Item

Paging-MACFlows-to-DeleteLCR-Item ::= SEQUENCE {
	paging-MACFlow-ID								Paging-MACFlow-ID,
	iE-Extensions									ProtocolExtensionContainer { { Paging-MACFlows-to-DeleteLCR-Item-ExtIEs} }					OPTIONAL,
	...
}

Paging-MACFlows-to-DeleteLCR-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}
Process-Memory-Size	::=	ENUMERATED {
										hms800, hms1600, hms2400, hms3200, hms4000,
										hms4800, hms5600, hms6400, hms7200, hms8000,
										hms8800, hms9600, hms10400, hms11200, hms12000,
										hms12800, hms13600, hms14400, hms15200, hms16000,
										hms17600, hms19200, hms20800, hms22400, hms24000,
										hms25600, hms27200, hms28800, hms30400, hms32000,
										hms36000, hms40000, hms44000, hms48000, hms52000,
										hms56000, hms60000, hms64000, hms68000, hms72000,
										hms76000, hms80000, hms88000, hms96000, hms104000,
										hms112000, hms120000, hms128000, hms136000, hms144000,
										hms152000, hms160000, hms176000, hms192000, hms208000,
										hms224000, hms240000, hms256000, hms272000, hms288000,
										hms304000,...}

Per-HARQ-Activiation-and-Deactiviation ::= SEQUENCE {
	configuration-for-2msTTI-Common-E-DCH-ResourcesList			Configuration-for-2msTTI-Common-E-DCH-ResourcesList,
	iE-Extensions								ProtocolExtensionContainer  { { Per-HARQ-Activiation-and-Deactiviation-ExtIEs} }		OPTIONAL,
	...
}

Per-HARQ-Activiation-and-Deactiviation-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

-- ==========================================
--	Q
-- ==========================================

QE-Selector ::= ENUMERATED {
	selected,
	non-selected
}

-- ==========================================
--	R
-- ==========================================

RACH-Measurement-Result ::= ENUMERATED {
	cpich-EcNo,
	cpich-RSCP,
	pathloss,
	...
}

RACH-SlotFormat ::= ENUMERATED {
	v0,
	v1,
	v2,
	v3,
	...
}

RACH-SubChannelNumbers ::= BIT STRING {
										subCh11(0),
										subCh10(1),
									 	subCh9(2),
									 	subCh8(3),
									 	subCh7(4),
									 	subCh6(5),
									 	subCh5(6),
									 	subCh4(7),
									 	subCh3(8),
									 	subCh2(9),
									 	subCh1(10),
									 	subCh0(11)
										} (SIZE (12))

RL-Specific-DCH-Info ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF RL-Specific-DCH-Info-Item

RL-Specific-DCH-Info-Item ::= SEQUENCE {
	dCH-id					DCH-ID,
	bindingID				BindingID															OPTIONAL,
	transportlayeraddress	TransportLayerAddress												OPTIONAL,
	iE-Extensions			ProtocolExtensionContainer { { RL-Specific-DCH-Info-Item-ExtIEs} }	OPTIONAL,
	...
}

RL-Specific-DCH-Info-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-TransportBearerNotRequestedIndicator	CRITICALITY ignore	EXTENSION TransportBearerNotRequestedIndicator		PRESENCE optional	}, -- FDD only
	...
}

RL-Specific-E-DCH-Info ::= SEQUENCE {
	rL-Specific-E-DCH-Information		RL-Specific-E-DCH-Information, 
	e-AGCH-PowerOffset					E-AGCH-PowerOffset							OPTIONAL, 
	e-RGCH-PowerOffset					E-RGCH-PowerOffset							OPTIONAL, 
	e-HICH-PowerOffset					E-HICH-PowerOffset							OPTIONAL, 
	iE-Extensions			ProtocolExtensionContainer { { RL-Specific-E-DCH-Info-Item-ExtIEs} }	OPTIONAL,
	...
}

RL-Specific-E-DCH-Info-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


RL-Specific-E-DCH-Information ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF RL-Specific-E-DCH-Information-Item

RL-Specific-E-DCH-Information-Item ::= SEQUENCE {
	e-DCH-MACdFlow-ID		E-DCH-MACdFlow-ID,
	bindingID				BindingID									OPTIONAL,
	transportlayeraddress	TransportLayerAddress						OPTIONAL,
	iE-Extensions			ProtocolExtensionContainer { { RL-Specific-E-DCH-Information-Item-ExtIEs} }	OPTIONAL,
	...
}

RL-Specific-E-DCH-Information-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Range-Correction-Rate ::= INTEGER (-127..127)
-- scaling factor 0.032 m/s

Reference-ReceivedTotalWideBandPower ::= INTEGER (0..621)
-- mapping as for RTWP measurement value, as specified in TS 25.133 [22]


Reference-ReceivedTotalWideBandPowerReporting::= ENUMERATED {
	reference-ReceivedTotalWideBandPower-Requested
}

Reference-ReceivedTotalWideBandPowerSupportIndicator::= ENUMERATED {
	indication-of-Reference-ReceivedTotalWideBandPower-supported
}

ReferenceClockAvailability ::= ENUMERATED {
	available,
	notAvailable
}

ReferenceSFNoffset ::= INTEGER (0..255)

Reference-E-TFCI-Information ::= SEQUENCE (SIZE (1..maxNrOfRefETFCIs)) OF Reference-E-TFCI-Information-Item

Reference-E-TFCI-Information-Item ::= SEQUENCE {
	reference-E-TFCI				E-TFCI,
	-- The following IE shall be ignored if id-Ext-Reference-E-TFCI-PO is present in Reference-E-TFCI-Information-Item-ExtIEs
	reference-E-TFCI-PO				Reference-E-TFCI-PO,
	iE-Extensions					ProtocolExtensionContainer { { Reference-E-TFCI-Information-Item-ExtIEs} }		OPTIONAL,
	...
}

Reference-E-TFCI-Information-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	-- The following IE shall be present if the ref E-TFCI power offset to be signalled exceeds maxNrOfRefETFCI-PO-QUANTSTEPs
	{ ID id-Ext-Reference-E-TFCI-PO		CRITICALITY reject		EXTENSION	Ext-Reference-E-TFCI-PO		PRESENCE optional},
	...
}

Reference-E-TFCI-PO ::= INTEGER (0.. maxNrOfRefETFCI-PO-QUANTSTEPs)

RepetitionLength ::= INTEGER (1..63)

RepetitionPeriod ::= ENUMERATED {
	v1,
	v2,
	v4,
	v8,
	v16,
	v32,
	v64,
	...
}

RepetitionNumber0 ::= INTEGER (0..255)

RepetitionNumber1 ::= INTEGER (1..256)

RefTFCNumber ::= INTEGER (0..3)

ReportCharacteristics ::= CHOICE {
	onDemand			NULL,
	periodic			ReportCharacteristicsType-ReportPeriodicity,
	event-a				ReportCharacteristicsType-EventA,
	event-b				ReportCharacteristicsType-EventB,
	event-c				ReportCharacteristicsType-EventC,
	event-d				ReportCharacteristicsType-EventD,
	event-e				ReportCharacteristicsType-EventE,
	event-f				ReportCharacteristicsType-EventF,
	...,
	extension-ReportCharacteristics		Extension-ReportCharacteristics
}

Extension-ReportCharacteristics	::= ProtocolIE-Single-Container {{ Extension-ReportCharacteristicsIE }}

Extension-ReportCharacteristicsIE NBAP-PROTOCOL-IES ::= {
	{ ID id-ReportCharacteristicsType-OnModification	CRITICALITY reject	TYPE ReportCharacteristicsType-OnModification		PRESENCE mandatory }
}

ReportCharacteristicsType-EventA ::= SEQUENCE {
	measurementThreshold			ReportCharacteristicsType-MeasurementThreshold,
	measurementHysteresisTime		ReportCharacteristicsType-ScaledMeasurementHysteresisTime			OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { ReportCharacteristicsType-EventA-ExtIEs} }		OPTIONAL,
	...
	}

ReportCharacteristicsType-EventA-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ReportCharacteristicsType-EventB ::= SEQUENCE {
	measurementThreshold			ReportCharacteristicsType-MeasurementThreshold,
	measurementHysteresisTime		ReportCharacteristicsType-ScaledMeasurementHysteresisTime			OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { ReportCharacteristicsType-EventB-ExtIEs} }		OPTIONAL,
	...
	}

ReportCharacteristicsType-EventB-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ReportCharacteristicsType-EventC ::= SEQUENCE {
	measurementIncreaseThreshold	ReportCharacteristicsType-MeasurementIncreaseDecreaseThreshold,
	measurementChangeTime			ReportCharacteristicsType-ScaledMeasurementChangeTime,
	iE-Extensions					ProtocolExtensionContainer { { ReportCharacteristicsType-EventC-ExtIEs} }		OPTIONAL,
	...
	}

ReportCharacteristicsType-EventC-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ReportCharacteristicsType-EventD ::= SEQUENCE {
	measurementDecreaseThreshold	ReportCharacteristicsType-MeasurementIncreaseDecreaseThreshold,
	measurementChangeTime			ReportCharacteristicsType-ScaledMeasurementChangeTime,
	iE-Extensions					ProtocolExtensionContainer { { ReportCharacteristicsType-EventD-ExtIEs} }		OPTIONAL,
	...
	}

ReportCharacteristicsType-EventD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ReportCharacteristicsType-EventE ::= SEQUENCE {
	measurementThreshold1			ReportCharacteristicsType-MeasurementThreshold,
	measurementThreshold2			ReportCharacteristicsType-MeasurementThreshold				OPTIONAL,
	measurementHysteresisTime		ReportCharacteristicsType-ScaledMeasurementHysteresisTime	OPTIONAL,
	reportPeriodicity				ReportCharacteristicsType-ReportPeriodicity					OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { ReportCharacteristicsType-EventE-ExtIEs} }		OPTIONAL,
	...
	}

ReportCharacteristicsType-EventE-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ReportCharacteristicsType-EventF ::= SEQUENCE {
	measurementThreshold1			ReportCharacteristicsType-MeasurementThreshold,
	measurementThreshold2			ReportCharacteristicsType-MeasurementThreshold				OPTIONAL,
	measurementHysteresisTime		ReportCharacteristicsType-ScaledMeasurementHysteresisTime	OPTIONAL,
	reportPeriodicity				ReportCharacteristicsType-ReportPeriodicity					OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { ReportCharacteristicsType-EventF-ExtIEs} }		OPTIONAL,
	...
	}

ReportCharacteristicsType-EventF-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ReportCharacteristicsType-OnModification ::= SEQUENCE {
	measurementThreshold			ReportCharacteristicsType-MeasurementThreshold,
	iE-Extensions					ProtocolExtensionContainer { { ReportCharacteristicsType-OnModification-ExtIEs} }		OPTIONAL,
		...
	}

ReportCharacteristicsType-OnModification-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ReportCharacteristicsType-MeasurementIncreaseDecreaseThreshold ::= CHOICE {
	received-total-wide-band-power							Received-total-wide-band-power-Value-IncrDecrThres,
	transmitted-carrier-power		Transmitted-Carrier-Power-Value,
	acknowledged-prach-preambles			Acknowledged-PRACH-preambles-Value,
	uL-TimeslotISCP					UL-TimeslotISCP-Value-IncrDecrThres,
	sir							SIR-Value-IncrDecrThres,
	sir-error					SIR-Error-Value-IncrDecrThres,
	transmitted-code-power			Transmitted-Code-Power-Value-IncrDecrThres,
	rscp							RSCP-Value-IncrDecrThres,
	round-trip-time					Round-Trip-Time-IncrDecrThres,
	notUsed-1-acknowledged-PCPCH-access-preambles		NULL,
	notUsed-2-detected-PCPCH-access-preambles			NULL,
	...,
	extension-ReportCharacteristicsType-MeasurementIncreaseDecreaseThreshold		Extension-ReportCharacteristicsType-MeasurementIncreaseDecreaseThreshold
}

Extension-ReportCharacteristicsType-MeasurementIncreaseDecreaseThreshold	::= ProtocolIE-Single-Container {{ Extension-ReportCharacteristicsType-MeasurementIncreaseDecreaseThresholdIE }}

Extension-ReportCharacteristicsType-MeasurementIncreaseDecreaseThresholdIE NBAP-PROTOCOL-IES ::= {
{ ID id-TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmission			CRITICALITY reject	TYPE TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmissionValue PRESENCE mandatory}|
{ ID id-Transmitted-Carrier-Power-For-CellPortion		CRITICALITY reject	TYPE Transmitted-Carrier-Power-Value		PRESENCE mandatory }|
{ ID id-Received-total-wide-band-power-For-CellPortion	CRITICALITY reject	TYPE Received-total-wide-band-power-Value-IncrDecrThres		PRESENCE mandatory }|
{ ID id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmissionCellPortion	CRITICALITY reject	TYPE TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmissionValue		PRESENCE mandatory }|
{ ID id-UpPTSInterferenceValue		CRITICALITY reject	TYPE 	UpPTSInterferenceValue					PRESENCE mandatory }|
{ ID id-Received-Scheduled-EDCH-Power-Share		CRITICALITY reject	TYPE RSEPS-Value-IncrDecrThres		PRESENCE mandatory }|
{ ID id-Received-Scheduled-EDCH-Power-Share-For-CellPortion	CRITICALITY reject	TYPE RSEPS-Value-IncrDecrThres		PRESENCE mandatory }|
{ ID id-EDCH-RACH-Report-IncrDecrThres						CRITICALITY reject	TYPE EDCH-RACH-Report-IncrDecrThres		PRESENCE mandatory }|
	-- FDD only
{ ID id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmissionCellPortion	CRITICALITY reject	TYPE TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmissionValue		PRESENCE mandatory }|
{ ID id-ULTimeslotISCPValue-For-CellPortion		CRITICALITY reject	TYPE 	UL-TimeslotISCP-Value-IncrDecrThres					PRESENCE mandatory }|
{ ID id-UpPTSInterferenceValue-For-CellPortion		CRITICALITY reject	TYPE 	UpPTSInterferenceValue					PRESENCE mandatory }
}

EDCH-RACH-Report-IncrDecrThres ::= SEQUENCE {
	denied-EDCH-RACH-resources		Denied-EDCH-RACH-Resources-Value,
	iE-Extensions		ProtocolExtensionContainer { { EDCH-RACH-Report-IncrDecrThres-ExtIEs } } OPTIONAL,
		...
}

EDCH-RACH-Report-IncrDecrThres-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Two-ms-Overridden-E-DCH-RACH-Resources	CRITICALITY ignore	EXTENSION Two-ms-Overridden-E-DCH-RACH-Resources		PRESENCE optional}|
	{ ID id-Two-ms-Denied-E-DCH-RACH-Resources		CRITICALITY ignore	EXTENSION Two-ms-Denied-E-DCH-RACH-Resources			PRESENCE optional},
	...
}

Granted-EDCH-RACH-Resources-Value ::= INTEGER(0..240,...)
-- According to mapping in TS 25.302 [25].

Denied-EDCH-RACH-Resources-Value ::= INTEGER(0..240,...)
-- According to mapping in TS 25.302 [25].

ReportCharacteristicsType-MeasurementThreshold ::= CHOICE {
	received-total-wide-band-power							Received-total-wide-band-power-Value,
	transmitted-carrier-power		Transmitted-Carrier-Power-Value,
	acknowledged-prach-preambles			Acknowledged-PRACH-preambles-Value,
	uL-TimeslotISCP					UL-TimeslotISCP-Value,
	sir							SIR-Value,
	sir-error					SIR-Error-Value,
	transmitted-code-power			Transmitted-Code-Power-Value,
	rscp							RSCP-Value,
	rx-timing-deviation				Rx-Timing-Deviation-Value,
	round-trip-time					Round-Trip-Time-Value,
	notUsed-1-acknowledged-PCPCH-access-preambles		NULL,
	notUsed-2-detected-PCPCH-access-preambles			NULL,
	...,
	extension-ReportCharacteristicsType-MeasurementThreshold		Extension-ReportCharacteristicsType-MeasurementThreshold
}

Extension-ReportCharacteristicsType-MeasurementThreshold	::= ProtocolIE-Single-Container {{ Extension-ReportCharacteristicsType-MeasurementThresholdIE }}

Extension-ReportCharacteristicsType-MeasurementThresholdIE NBAP-PROTOCOL-IES ::= {
	{ ID id-TUTRANGPSMeasurementThresholdInformation	CRITICALITY reject	TYPE TUTRANGPSMeasurementThresholdInformation		PRESENCE mandatory }|
	{ ID id-SFNSFNMeasurementThresholdInformation		CRITICALITY reject	TYPE SFNSFNMeasurementThresholdInformation			PRESENCE mandatory }|
	{ ID id-Rx-Timing-Deviation-Value-LCR				CRITICALITY reject	TYPE Rx-Timing-Deviation-Value-LCR					PRESENCE mandatory }|
	{ ID id-HS-SICH-Reception-Quality-Measurement-Value	CRITICALITY reject	TYPE HS-SICH-Reception-Quality-Measurement-Value	PRESENCE mandatory }|
	-- For 1.28Mcps TDD, used when the Measurement Threshold Value for HS-SICH Reception Quality are less than or equal to 20
	{ ID id-TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmission CRITICALITY reject	TYPE TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmissionValue PRESENCE mandatory }|
	{ ID id-HS-DSCHRequiredPowerValue					CRITICALITY reject	TYPE HS-DSCHRequiredPowerValue							PRESENCE mandatory }|
	{ ID id-Transmitted-Carrier-Power-For-CellPortion	CRITICALITY reject	TYPE Transmitted-Carrier-Power-Value					PRESENCE mandatory }|
	{ ID id-Received-total-wide-band-power-For-CellPortion	CRITICALITY reject	TYPE Received-total-wide-band-power-Value		PRESENCE mandatory }|
	{ ID id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmissionCellPortion	 CRITICALITY reject	TYPE TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmissionValue		PRESENCE mandatory }|
	{ ID id-UpPTSInterferenceValue						CRITICALITY reject	TYPE UpPTSInterferenceValue								PRESENCE mandatory }|
	{ ID id-DLTransmissionBranchLoadValue				CRITICALITY reject	TYPE DLTransmissionBranchLoadValue					PRESENCE mandatory }|
	{ ID id-HS-DSCHRequiredPowerValue-For-Cell-Portion	CRITICALITY reject	TYPE HS-DSCHRequiredPowerValue							PRESENCE mandatory }|
	{ ID id-E-DCH-Non-serving-Relative-Grant-Down-CommandsValue		CRITICALITY reject	TYPE E-DCH-Non-serving-Relative-Grant-Down-Commands			PRESENCE mandatory }|
	{ ID id-Rx-Timing-Deviation-Value-768				CRITICALITY reject	TYPE Rx-Timing-Deviation-Value-768					PRESENCE mandatory }|
	{ ID id-Rx-Timing-Deviation-Value-384-ext			CRITICALITY reject	TYPE Rx-Timing-Deviation-Value-384-ext				PRESENCE mandatory }|
	{ ID id-Extended-Round-Trip-Time-Value				CRITICALITY reject	TYPE Extended-Round-Trip-Time-Value					PRESENCE mandatory }|
	{ ID id-Received-Scheduled-EDCH-Power-Share			CRITICALITY reject	TYPE RSEPS-Value-IncrDecrThres							PRESENCE mandatory }|
	{ ID id-Received-Scheduled-EDCH-Power-Share-For-CellPortion	CRITICALITY reject	TYPE RSEPS-Value-IncrDecrThres				PRESENCE mandatory }|
	{ ID id-Additional-HS-SICH-Reception-Quality-Measurement-Value	CRITICALITY reject	TYPE HS-SICH-Reception-Quality-Measurement-Value			PRESENCE mandatory}|
	-- Applicable to 1.28Mcps TDD only, used when the Measurement Threshold Value for HS-SICH Reception Quality are more than 20, Measurement Threshold Value = 20 + IE Value
	{ ID id-TUTRANGANSSMeasurementThresholdInformation	CRITICALITY reject	TYPE TUTRANGANSSMeasurementThresholdInformation	PRESENCE mandatory }|
	{ ID id-EDCH-RACH-Report-ThresholdInformation		CRITICALITY reject	TYPE EDCH-RACH-Report-ThresholdInformation			PRESENCE mandatory }|
	-- FDD only
	{ ID id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmissionCellPortion	CRITICALITY reject	TYPE TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmissionValue		PRESENCE mandatory }|
	{ ID id-ULTimeslotISCPValue-For-CellPortion			CRITICALITY reject	TYPE UL-TimeslotISCP-Value								PRESENCE mandatory }|
	{ ID id-UpPTSInterferenceValue-For-CellPortion		CRITICALITY reject	TYPE UpPTSInterferenceValue								PRESENCE mandatory }|
	{ ID id-UE-transmission-power-headroom				CRITICALITY reject	TYPE UE-transmission-power-headroom-Value			PRESENCE mandatory }
}

EDCH-RACH-Report-ThresholdInformation ::= SEQUENCE {
	denied-EDCH-RACH-resources		Denied-EDCH-RACH-Resources-Value,
	iE-Extensions		ProtocolExtensionContainer { { EDCH-RACH-Report-ThresholdInformation-ExtIEs } } OPTIONAL,
		...
}

EDCH-RACH-Report-ThresholdInformation-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Two-ms-Overridden-E-DCH-RACH-Resources		CRITICALITY ignore	EXTENSION Two-ms-Overridden-E-DCH-RACH-Resources		PRESENCE optional}|
	{ ID id-Two-ms-Denied-E-DCH-RACH-Resources			CRITICALITY ignore	EXTENSION Two-ms-Denied-E-DCH-RACH-Resources			PRESENCE optional},
	...
}

ReportCharacteristicsType-ScaledMeasurementChangeTime ::= CHOICE {
	msec				MeasurementChangeTime-Scaledmsec,
	...
}

MeasurementChangeTime-Scaledmsec ::= INTEGER (1..6000,...)
-- MeasurementChangeTime-Scaledmsec = Time * 10
-- Unit ms, Range 10ms .. 60000ms(1min), Step 10ms

ReportCharacteristicsType-ScaledMeasurementHysteresisTime ::= CHOICE {
	msec				MeasurementHysteresisTime-Scaledmsec,
	...
}

MeasurementHysteresisTime-Scaledmsec ::= INTEGER (1..6000,...)
-- MeasurementHysteresisTime-Scaledmsec = Time * 10
-- Unit ms, Range 10ms .. 60000ms(1min), Step 10ms

ReportCharacteristicsType-ReportPeriodicity ::= CHOICE {
	msec 				ReportPeriodicity-Scaledmsec,
	min					ReportPeriodicity-Scaledmin,
	...
}

ReportPeriodicity-Scaledmsec ::= INTEGER (1..6000,...)
-- ReportPeriodicity-msec = ReportPeriodicity * 10
-- Unit ms, Range 10ms .. 60000ms(1min), Step 10ms

ReportPeriodicity-Scaledmin ::= INTEGER (1..60,...)
-- Unit min, Range 1min .. 60min(hour), Step 1min

ReportPeriodicity-Scaledhour ::= INTEGER (1..24,...)
-- Unit hour, Range 1hour .. 24hours(day), Step 1hour

ResourceOperationalState ::= ENUMERATED {
	enabled,
	disabled
}

RL-ID ::= INTEGER (0..31)

RL-Set-ID				::= INTEGER (0..31)

RLC-Mode	::= ENUMERATED {
	rLC-AM,
	rLC-UM,
	...
}

DL-RLC-PDU-Size-Format	::= ENUMERATED {
	fixed-RLC-PDU-Size,
	flexible-RLC-PDU-Size,
	...
}

Round-Trip-Time-IncrDecrThres ::= INTEGER(0..32766)

RNC-ID					::= INTEGER (0..4095)

Round-Trip-Time-Value ::= INTEGER(0..32767)
-- According to mapping in TS 25.133 [22]

RSCP-Value ::= INTEGER (0..127)
-- According to mapping in TS 25.123 [23]

RSCP-Value-IncrDecrThres ::= INTEGER (0..126)

Received-total-wide-band-power-For-CellPortion-Value ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCell)) OF Received-total-wide-band-power-For-CellPortion-Value-Item

Received-total-wide-band-power-For-CellPortion-Value-Item ::= SEQUENCE{
	cellPortionID							CellPortionID, 
	received-total-wide-band-power-value	Received-total-wide-band-power-Value,
	iE-Extensions							ProtocolExtensionContainer { { Received-total-wide-band-power-For-CellPortion-Value-Item-ExtIEs} }		OPTIONAL,
...
}

Received-total-wide-band-power-For-CellPortion-Value-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Received-total-wide-band-power-For-CellPortion-ValueLCR ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCellLCR)) OF Received-total-wide-band-power-For-CellPortion-ValueLCR-Item

Received-total-wide-band-power-For-CellPortion-ValueLCR-Item ::= SEQUENCE{
	cellPortionLCRID							CellPortionLCRID, 
	received-total-wide-band-power-value	Received-total-wide-band-power-Value,
	iE-Extensions							ProtocolExtensionContainer { { Received-total-wide-band-power-For-CellPortion-ValueLCR-Item-ExtIEs} }		OPTIONAL,
...
}

Received-total-wide-band-power-For-CellPortion-ValueLCR-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Received-total-wide-band-power-Value ::= INTEGER(0..621)
-- According to mapping in TS 25.133 [22]/TS 25.123 [23]

Received-total-wide-band-power-Value-IncrDecrThres ::= INTEGER (0..620)

Received-Scheduled-EDCH-Power-Share-For-CellPortion-Value ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCell)) OF Received-Scheduled-EDCH-Power-Share-For-CellPortion-Value-Item

Received-Scheduled-EDCH-Power-Share-For-CellPortion-Value-Item ::= SEQUENCE{
	cellPortionID							CellPortionID, 
	received-Scheduled-power-share-value	RSEPS-Value,
	received-total-wide-band-power-value	Received-total-wide-band-power-Value		OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { Received-Scheduled-EDCH-Power-Share-For-CellPortion-Value-Item-ExtIEs} }		OPTIONAL,
	...
	}

Received-Scheduled-EDCH-Power-Share-For-CellPortion-Value-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Received-Scheduled-EDCH-Power-Share-Value ::= SEQUENCE{
	received-Scheduled-power-share-value	RSEPS-Value,
	received-total-wide-band-power-value	Received-total-wide-band-power-Value		OPTIONAL,
	...
	}

RSEPS-Value-IncrDecrThres ::= INTEGER (0..151)


RSEPS-Value ::= INTEGER (0..151)
-- According to mapping in TS 25.133 [22]


RequestedDataValueInformation ::= CHOICE {
	informationAvailable		InformationAvailable,
	informationnotAvailable		InformationnotAvailable
}

InformationAvailable::= SEQUENCE {
	requesteddataValue		RequestedDataValue,
	ie-Extensions			ProtocolExtensionContainer { { InformationAvailableItem-ExtIEs} }		OPTIONAL,
	...
}

InformationAvailableItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

InformationnotAvailable ::= NULL

RequestedDataValue ::= SEQUENCE {
	dgps-corrections		DGPSCorrections													OPTIONAL,
	gps-navandrecovery		GPS-NavigationModel-and-TimeRecovery							OPTIONAL,
	gps-ionos-model			GPS-Ionospheric-Model											OPTIONAL,
	gps-utc-model			GPS-UTC-Model													OPTIONAL,
	gps-almanac				GPS-Almanac														OPTIONAL,
	gps-rt-integrity		GPS-RealTime-Integrity											OPTIONAL,
	gpsrxpos				GPS-RX-POS														OPTIONAL,
	iE-Extensions			ProtocolExtensionContainer { { RequestedDataValue-ExtIEs} }		OPTIONAL,
	...
}

RequestedDataValue-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-GANSS-Common-Data			CRITICALITY ignore		EXTENSION GANSS-Common-Data				PRESENCE optional }|
	{ ID id-GANSS-Generic-Data			CRITICALITY ignore		EXTENSION GANSS-Generic-Data									PRESENCE optional },
	...
}

Rx-Timing-Deviation-Value ::= INTEGER (0..8191)
-- According to mapping in TS 25.123 [23]

Rx-Timing-Deviation-Value-LCR ::= INTEGER (0..511)
-- According to mapping in TS 25.123 [23]

Rx-Timing-Deviation-Value-768 ::= INTEGER (0..65535)
-- According to mapping in TS 25.123 [23]

Rx-Timing-Deviation-Value-384-ext ::= INTEGER (0..32767)
-- According to mapping in TS 25.123 [23]

RefBeta ::= INTEGER (-15..16)

RTWP-ReportingIndicator ::= ENUMERATED {
	rTWP-reporting-required}

RTWP-CellPortion-ReportingIndicator ::= ENUMERATED {
	rTWP-CellPortion-reporting-required}


-- ==========================================
--	S
-- ==========================================

AdjustmentPeriod			::= INTEGER(1..256)
-- Unit Frame

E-DPCCH-Power-Boosting-Capability ::= ENUMERATED {
	e-DPCCH-Power-Boosting-capable,
	e-DPCCH-Power-Boosting-non-capable
}

SAT-ID ::= INTEGER (0..63) 

SAT-Info-Almanac ::= SEQUENCE (SIZE (1..maxNoSat)) OF SAT-Info-Almanac-Item

SAT-Info-Almanac-Item ::= SEQUENCE {
	data-id			   DATA-ID,
    sat-id             SAT-ID,
    gps-e-alm          BIT STRING (SIZE (16)),
    gps-toa-alm        BIT STRING (SIZE (8)),     
    gps-delta-I-alm    BIT STRING (SIZE (16)),
    omegadot-alm       BIT STRING (SIZE (16)),
    svhealth-alm       BIT STRING (SIZE (8)),
    gps-a-sqrt-alm     BIT STRING (SIZE (24)),
    omegazero-alm      BIT STRING (SIZE (24)),
    m-zero-alm         BIT STRING (SIZE (24)),
    gps-omega-alm      BIT STRING (SIZE (24)),
    gps-af-zero-alm    BIT STRING (SIZE (11)),
    gps-af-one-alm     BIT STRING (SIZE (11)),
    ie-Extensions	   ProtocolExtensionContainer { { SAT-Info-Almanac-Item-ExtIEs} }		OPTIONAL,
   ...
}	-- This GPS-Almanac-Information is for the 1st 16 satellites

SAT-Info-Almanac-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
} 

SAT-Info-Almanac-ExtList	::= SEQUENCE (SIZE (1..maxNrOfSatAlmanac-maxNoSat)) OF SAT-Info-Almanac-ExtItem

SAT-Info-Almanac-ExtItem	::= SEQUENCE {
	data-id			   DATA-ID,
    sat-id             SAT-ID,
    gps-e-alm          BIT STRING (SIZE (16)),
    gps-toa-alm        BIT STRING (SIZE (8)),     
    gps-delta-I-alm    BIT STRING (SIZE (16)),
    omegadot-alm       BIT STRING (SIZE (16)),
    svhealth-alm       BIT STRING (SIZE (8)),
    gps-a-sqrt-alm     BIT STRING (SIZE (24)),
    omegazero-alm      BIT STRING (SIZE (24)),
    m-zero-alm         BIT STRING (SIZE (24)),
    gps-omega-alm      BIT STRING (SIZE (24)),
    gps-af-zero-alm    BIT STRING (SIZE (11)),
    gps-af-one-alm     BIT STRING (SIZE (11)),
    ie-Extensions	   ProtocolExtensionContainer { { SAT-Info-Almanac-ExtItemIEs } }		OPTIONAL,
   ...
}	--	Includes the GPS-Almanac-Information for 17th through 32nd satellites.

SAT-Info-Almanac-ExtItemIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SAT-Info-DGPSCorrections ::= SEQUENCE (SIZE (1..maxNoSat)) OF SAT-Info-DGPSCorrections-Item

SAT-Info-DGPSCorrections-Item ::= SEQUENCE {
    sat-id                                	SAT-ID,
    iode-dgps                           	BIT STRING (SIZE (8)),
    udre            						UDRE,
    prc             						PRC,
    range-correction-rate             		Range-Correction-Rate,
    ie-Extensions							ProtocolExtensionContainer { { SAT-Info-DGPSCorrections-Item-ExtIEs} }  OPTIONAL,
   ...
}

SAT-Info-DGPSCorrections-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-DGNSS-ValidityPeriod	CRITICALITY	ignore	EXTENSION	DGNSS-ValidityPeriod	PRESENCE	optional},
	...
}

SATInfo-RealTime-Integrity ::= SEQUENCE (SIZE (1..maxNoSat)) OF SAT-Info-RealTime-Integrity-Item

SAT-Info-RealTime-Integrity-Item ::= SEQUENCE {
  bad-sat-id       SAT-ID,
  ie-Extensions	   ProtocolExtensionContainer { { SAT-Info-RealTime-Integrity-Item-ExtIEs} }		OPTIONAL,
   ...
}

SAT-Info-RealTime-Integrity-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ScaledAdjustmentRatio			::= INTEGER(0..100)
-- AdjustmentRatio  = ScaledAdjustmentRatio / 100

MaxAdjustmentStep			::= INTEGER(1..10)
-- Unit Slot

SchedulingInformation 			::= ENUMERATED {
	included,
	not-included
}

SecondaryServingCells ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF SecondaryServingCellsItem

SecondaryServingCellsItem ::= SEQUENCE {
	secondaryC-ID				C-ID,
	numSecondaryHS-SCCH-Codes		NumHS-SCCH-Codes		OPTIONAL,
	sixtyfourQAM-UsageAllowedIndicator		SixtyfourQAM-UsageAllowedIndicator 		OPTIONAL,
	iE-Extensions									ProtocolExtensionContainer { { SecondaryServingCellsItem-ExtIEs} }				OPTIONAL,
	...
}

SecondaryServingCellsItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-MIMO-ActivationIndicator					CRITICALITY ignore	EXTENSION MIMO-ActivationIndicator						PRESENCE optional}|
	{ID id-EDCH-Indicator							CRITICALITY ignore	EXTENSION NULL												PRESENCE optional}|
	{ID id-OrdinalNumberOfFrequency					CRITICALITY ignore	EXTENSION OrdinalNumberOfFrequency						PRESENCE optional}|
	{ID id-MIMO-withfourtransmitantennas-ActivationIndicator		CRITICALITY ignore	EXTENSION MIMO-withfourtransmitantennas-ActivationIndicator			PRESENCE optional}|
	{ID id-DualStream-MIMO-withfourtransmitantennas-ActivationIndicator	CRITICALITY ignore	EXTENSION DualStream-MIMO-withfourtransmitantennas-ActivationIndicator			PRESENCE optional}|
	{ID id-Multiflow-OrdinalNumberOfFrequency		CRITICALITY ignore	EXTENSION Multiflow-OrdinalNumberOfFrequency		PRESENCE optional},
	...
}

Secondary-UL-Frequency-Activation-State ::= ENUMERATED {
	activated,
	deactivated,
		...
}

SchedulingPriorityIndicator 			::= INTEGER (0..15)		 -- lowest (0), highest (15)

SID ::= INTEGER (0..maxNrOfMACdPDUIndexes-1)

ScramblingCodeNumber ::= INTEGER (0..15)

Secondary-CPICH-Information-Change ::= CHOICE {
	new-secondary-CPICH					CommonPhysicalChannelID,
	secondary-CPICH-shall-not-be-used	NULL,
...
}

SecondaryCCPCH-SlotFormat ::= INTEGER(0..17,...)

Secondary-CCPCH-SlotFormat-Extended ::= INTEGER(18..23,...)

Segment-Type ::= ENUMERATED {
		first-segment, 
		first-segment-short,
		subsequent-segment,
		last-segment, 
		last-segment-short, 
		complete-SIB, 
		complete-SIB-short,
		...
}

Serving-E-DCH-RL-ID ::= CHOICE {
	serving-E-DCH-RL-in-this-NodeB				Serving-E-DCH-RL-in-this-NodeB,
	serving-E-DCH-RL-not-in-this-NodeB			NULL,
	...
}

Serving-E-DCH-RL-in-this-NodeB ::= SEQUENCE {
	rL-ID										RL-ID,
	iE-Extensions								ProtocolExtensionContainer { { Serving-E-DCH-RL-in-this-NodeB-ExtIEs} }			OPTIONAL,
	...
}

Serving-E-DCH-RL-in-this-NodeB-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SetsOfHS-SCCH-Codes ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH)) OF SetsOfHS-SCCH-CodesItem

SetsOfHS-SCCH-CodesItem ::= SEQUENCE {
	hS-SCCH-PreconfiguredCodes		HS-SCCH-PreconfiguredCodes,
	sixtyfourQAM-DL-UsageIndicator		SixtyfourQAM-DL-UsageIndicator		OPTIONAL,
	hSDSCH-TBSizeTableIndicator		HSDSCH-TBSizeTableIndicator				OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { SetsOfHS-SCCH-CodesItem-ExtIEs} } OPTIONAL,
	...
}

SetsOfHS-SCCH-CodesItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID	id-MIMO-N-M-Ratio				CRITICALITY ignore		EXTENSION MIMO-N-M-Ratio			PRESENCE optional},
	...
}

Setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency::= CHOICE {
	setup					Additional-EDCH-Setup-Info,
	configurationChange		Additional-EDCH-Cell-Information-ConfigurationChange-List, 
	removal					Additional-EDCH-Cell-Information-Removal-List,
	...
}

Setup-Or-ConfigurationChange-Or-Removal-Of-Downlink-TPC-enhancements ::= CHOICE {
	setup					Downlink-TPC-enhancements-Information,
	configurationChange		Downlink-TPC-enhancements-Information,
	removal					Downlink-TPC-enhancements-Information-Removal,
	...
}

Setup-Or-ConfigurationChange-Or-Removal-Of-UL-CLTD ::= CHOICE {
	setup					UL-CLTD-Information,
	configurationChange		UL-CLTD-Information-To-Modify,
	removal					UL-CLTD-Information-Removal,
	...
}

Setup-Or-ConfigurationChange-Or-Removal-Of-UL-DPCCH2 ::= CHOICE {
	setup					UL-DPCCH2-Information,
	configurationChange		UL-DPCCH2-Information-To-Modify,
	removal					UL-DPCCH2-Information-Removal,
	...
}

Setup-Or-ConfigurationChange-Or-Removal-Of-FTPICH-Information ::= CHOICE {
	setup					FTPICH-Information,
	configurationChange		FTPICH-Information-To-Modify,
	removal					FTPICH-Information-Removal,
	...
}

Setup-Or-ConfigurationChange-Or-Removal-Of-DCH-ENH ::= CHOICE {
	setup					DCH-ENH-Information,
	configurationChange		DCH-ENH-Information-to-Modify,
	removal					DCH-ENH-Information-Removal,
	...
}

SFN ::= INTEGER (0..4095)

SFNSFN-FDD ::= INTEGER (0..614399)

SFNSFN-TDD ::= INTEGER (0..40961) 

SFNSFN-TDD768 ::= INTEGER (0..81923)

SFNSFNChangeLimit ::= INTEGER (1..256)
-- Unit chip, Step 1/16 chip, Range 1/16..16 chip

SFNSFNDriftRate ::= INTEGER (-100..100)
-- Unit chip/s, Step 1/256 chip/s, Range -100/256..+100/256 chip/s

SFNSFNDriftRateQuality ::= INTEGER (0..100)
-- Unit chip/s, Step 1/256 chip/s, Range 0..100/256 chip/s

SFNSFNMeasurementThresholdInformation::= SEQUENCE {
	sFNSFNChangeLimit					SFNSFNChangeLimit					OPTIONAL,
	predictedSFNSFNDeviationLimit		PredictedSFNSFNDeviationLimit		OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { SFNSFNMeasurementThresholdInformation-ExtIEs} }		OPTIONAL,
	...
}

SFNSFNMeasurementThresholdInformation-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SFNSFNMeasurementValueInformation ::= SEQUENCE {
	successfullNeighbouringCellSFNSFNObservedTimeDifferenceMeasurementInformation		SEQUENCE (SIZE(1..maxNrOfMeasNCell)) OF
		SEQUENCE {
			uC-Id						UC-Id,
			sFNSFNValue					SFNSFNValue,
			sFNSFNQuality				SFNSFNQuality				OPTIONAL,
			sFNSFNDriftRate				SFNSFNDriftRate,
			sFNSFNDriftRateQuality		SFNSFNDriftRateQuality		OPTIONAL,
			sFNSFNTimeStampInformation	SFNSFNTimeStampInformation,
			iE-Extensions		ProtocolExtensionContainer { { SuccessfullNeighbouringCellSFNSFNObservedTimeDifferenceMeasurementInformationItem-ExtIEs} }		OPTIONAL,
			...
		},
	unsuccessfullNeighbouringCellSFNSFNObservedTimeDifferenceMeasurementInformation		SEQUENCE (SIZE(0..maxNrOfMeasNCell-1)) OF
		SEQUENCE {
			uC-Id						UC-Id,
			iE-Extensions		ProtocolExtensionContainer { { UnsuccessfullNeighbouringCellSFNSFNObservedTimeDifferenceMeasurementInformationItem-ExtIEs} }		OPTIONAL,
				...
		},
	iE-Extensions		ProtocolExtensionContainer { { SFNSFNMeasurementValueInformationItem-ExtIEs} }		OPTIONAL,
	...
}

SFNSFNMeasurementValueInformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SuccessfullNeighbouringCellSFNSFNObservedTimeDifferenceMeasurementInformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UnsuccessfullNeighbouringCellSFNSFNObservedTimeDifferenceMeasurementInformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SFNSFNQuality ::= INTEGER (0..255)
-- Unit chip, Step 1/16 chip, Range 0.. 255/16 chip

ShutdownTimer ::= INTEGER (1..3600)
-- Unit sec

SIB-Originator ::= ENUMERATED {
	nodeB, 
	cRNC,
	...
}

SIR-Error-Value ::= INTEGER (0..125)
-- According to mapping in TS 25.133 [22]

SFNSFNTimeStampInformation ::= CHOICE {
	sFNSFNTimeStamp-FDD		SFN,
	sFNSFNTimeStamp-TDD		SFNSFNTimeStamp-TDD,
	...}

SFNSFNTimeStamp-TDD::= SEQUENCE {
	sFN					SFN,
	timeSlot			TimeSlot,
	iE-Extensions					ProtocolExtensionContainer { { SFNSFNTimeStamp-ExtIEs} }		OPTIONAL,
	...
}

SFNSFNTimeStamp-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SFNSFNValue ::= CHOICE {
	sFNSFN-FDD		SFNSFN-FDD,
	sFNSFN-TDD		SFNSFN-TDD,			--- 1.28Mcps and 3.84Mcps TDD only
	...,
	sFNSFN-TDD768	SFNSFN-TDD768
}

Single-Stream-MIMO-ActivationIndicator ::= NULL

Single-Stream-MIMO-Capability ::= ENUMERATED {
	single-stream-mimo-capable,
	single-stream-mimo-non-capable
}


Single-Stream-MIMO-Mode-Indicator ::= ENUMERATED {
	activate,
	deactivate
}

SIR-Error-Value-IncrDecrThres ::= INTEGER (0..124)

SIR-Value ::= INTEGER (0..63)
-- According to mapping in TS 25.133 [22]/TS 25.123 [23]

SIR-Value-IncrDecrThres ::= INTEGER (0..62)

SignallingBearerRequestIndicator::= ENUMERATED {bearerRequested}


SixtyfourQAM-UsageAllowedIndicator ::= ENUMERATED {
	allowed,
	not-allowed
}

SixtyfourQAM-DL-UsageIndicator ::= ENUMERATED {
	sixtyfourQAM-DL-used,
	sixtyfourQAM-DL-not-used
}

SixtyfourQAM-DL-Capability ::= ENUMERATED {
	sixtyfourQAM-DL-supported,
	sixtyfourQAM-DL-not-supported
}

SixtyfourQAM-DL-MIMO-Combined-Capability ::= ENUMERATED {
	sixtyfourQAM-DL-MIMO-Combined-capable,
	sixtyfourQAM-DL-MIMO-Combined-non-capable
}

SignatureSequenceGroupIndex ::= INTEGER (0..19)


SixteenQAM-UL-Capability ::= ENUMERATED {
	sixteenQAM-UL-capable,
	sixteenQAM-UL-non-capable
}

SixteenQAM-UL-Operation-Indicator ::= ENUMERATED {
	activate,
	deactivate
}

SixtyfourQAM-UL-Operation-Indicator ::= ENUMERATED {
	activate,
	deactivate
}

SNPL-Reporting-Type ::= ENUMERATED {
	type1,
	type2
}

Soffset ::= INTEGER (0..9,...)

SpecialBurstScheduling ::= INTEGER (1..256)	-- Number of frames between special burst transmission during DTX

Start-Of-Audit-Sequence-Indicator ::= ENUMERATED {
	start-of-audit-sequence,
	not-start-of-audit-sequence
}

Status-Flag ::= ENUMERATED {
	activate,
	deactivate
}

STTD-Indicator ::= ENUMERATED {
	active,
	inactive,
	...
}

SSDT-SupportIndicator ::= ENUMERATED {
	not-Used-sSDT-Supported,
	sSDT-not-supported
}

Sub-Frame-Number ::= INTEGER (0..4,...)

Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order ::= ENUMERATED {
	supported,
	not-supported
}

SyncCase ::= INTEGER (1..2,...)

SYNCDlCodeId ::= INTEGER (1..32,...)

SyncFrameNumber ::= INTEGER (1..10)

SynchronisationReportCharacteristics ::= SEQUENCE {
	synchronisationReportCharacteristicsType	SynchronisationReportCharacteristicsType,
	synchronisationReportCharactThreExc			SynchronisationReportCharactThreExc		OPTIONAL,
		-- This IE shall be included if the synchronisationReportCharacteristicsType IE is set to “thresholdExceeding”.
	iE-Extensions								ProtocolExtensionContainer { { SynchronisationReportCharacteristics-ExtIEs } }	OPTIONAL,
	...
}

SynchronisationReportCharacteristics-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-SyncDLCodeIdThreInfoLCR	CRITICALITY	ignore EXTENSION	SyncDLCodeIdThreInfoLCR		PRESENCE optional },
	...
}

SynchronisationReportCharactThreExc ::= 	SEQUENCE (SIZE (1..maxNrOfCellSyncBursts)) OF SynchronisationReportCharactThreInfoItem  -- Mandatory for 3.84Mcps TDD only. Not Applicable to 1.28Mcps TDD.

SynchronisationReportCharactThreInfoItem ::= SEQUENCE {
	syncFrameNumber				SyncFrameNumber,
	cellSyncBurstInformation	SEQUENCE (SIZE (1.. maxNrOfReceptsPerSyncFrame)) OF SynchronisationReportCharactCellSyncBurstInfoItem,
	iE-Extensions				ProtocolExtensionContainer { { SynchronisationReportCharactThreInfoItem-ExtIEs } }		OPTIONAL,
	...
}

SynchronisationReportCharactThreInfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SynchronisationReportCharactCellSyncBurstInfoItem ::= SEQUENCE {
	cellSyncBurstCode 				CellSyncBurstCode,
	cellSyncBurstCodeShift 			CellSyncBurstCodeShift,
	cellSyncBurstTiming 			CellSyncBurstTiming				OPTIONAL,
	cellSyncBurstTimingThreshold 	CellSyncBurstTimingThreshold	OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { SynchronisationReportCharactCellSyncBurstInfoItem-ExtIEs } }		OPTIONAL,
	...
}

SynchronisationReportCharactCellSyncBurstInfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SyncDLCodeIdThreInfoLCR ::= SEQUENCE (SIZE (0..maxNrOfSyncFramesLCR)) OF SyncDLCodeIdThreInfoList  --Mandatory for 1.28Mcps TDD only. Not Applicable to 3.84Mcps TDD.

SyncDLCodeIdThreInfoList ::= SEQUENCE {
	syncFrameNoToReceive			SyncFrameNumber,
	syncDLCodeIdInfoLCR				SyncDLCodeInfoListLCR,
	iE-Extensions					ProtocolExtensionContainer { { SyncDLCodeIdThreInfoList-ExtIEs } }		OPTIONAL,
	...
}

SyncDLCodeIdThreInfoList-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SyncDLCodeInfoListLCR ::= SEQUENCE (SIZE (1..maxNrOfSyncDLCodesLCR)) OF SyncDLCodeInfoItemLCR

SyncDLCodeInfoItemLCR ::= SEQUENCE {
	syncDLCodeId					SYNCDlCodeId,
	syncDLCodeIdArrivTime			CellSyncBurstTimingLCR				OPTIONAL,
	syncDLCodeIdTimingThre			CellSyncBurstTimingThreshold		OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { SyncDLCodeInfoItem-LCR-ExtIEs } }		OPTIONAL,
	...
}

SyncDLCodeInfoItem-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SDPCCH-PowerOffsetInformation ::= INTEGER (0..6,...)

SynchronisationReportCharacteristicsType ::= ENUMERATED {
	frameRelated,
	sFNperiodRelated,
	cycleLengthRelated,
	thresholdExceeding,
	frequencyAcquisitionCompleted,
	...
}

SynchronisationReportType ::= ENUMERATED {
	initialPhase,
	steadyStatePhase,
	lateEntrantCell,
	frequencyAcquisition,
	...
}
Semi-PersistentScheduling-CapabilityLCR ::= ENUMERATED {
	semi-Persistent-scheduling-Capable,
	semi-Persistent-scheduling-Non-Capable
}

-- ==========================================
--	T
-- ==========================================

T1 ::= ENUMERATED {v10,v20,v30,v40,v50,v60,v70,v80,v90,v100,v120,v140,v160,v200,v300,v400,...}

T321 ::= ENUMERATED {v100,v200,v400,v800,...}

T-Cell ::= ENUMERATED {
	v0,
	v1,
	v2,
	v3,
	v4,
	v5,
	v6,
	v7,
	v8,
	v9
}

T-RLFAILURE ::= INTEGER (0..255)
-- Unit seconds, Range 0s .. 25.5s, Step 0.1s

T-PROTECT ::= ENUMERATED {v40,v60,v80,v100,v120,v200,v400,...}
T-SYNC ::= ENUMERATED {v40,v80,v120,v160,v200,v300,v400,v500,...}

TDD-AckNack-Power-Offset ::= INTEGER (-7..8,...)
-- Unit dB, Range –7dB .. +8dB, Step 1dB

TDD-ChannelisationCode ::= ENUMERATED {
	chCode1div1,
	chCode2div1,
	chCode2div2,
	chCode4div1,
	chCode4div2,
	chCode4div3,
	chCode4div4,
	chCode8div1,
	chCode8div2,
	chCode8div3,
	chCode8div4,
	chCode8div5,
	chCode8div6,
	chCode8div7,
	chCode8div8,
	chCode16div1,
	chCode16div2,
	chCode16div3,
	chCode16div4,
	chCode16div5,
	chCode16div6,
	chCode16div7,
	chCode16div8,
	chCode16div9,
	chCode16div10,
	chCode16div11,
	chCode16div12,
	chCode16div13,
	chCode16div14,
	chCode16div15,
	chCode16div16,
	...
}

Puncturing-Handling-in-First-Rate-Matching-Stage ::= BOOLEAN

TDD-ChannelisationCodeLCR ::= SEQUENCE {
	tDD-ChannelisationCode			TDD-ChannelisationCode,
	modulation						Modulation, -- Modulation options for 1.28Mcps TDD in contrast to 3.84Mcps TDD or 7.68Mcps TDD
	iE-Extensions							ProtocolExtensionContainer { { TDD-ChannelisationCodeLCR-ExtIEs} }		OPTIONAL,
	...
}

TDD-ChannelisationCodeLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}


TDD-ChannelisationCode768 			::= ENUMERATED {
	chCode1div1,
	chCode2div1,
	chCode2div2,
	chCode4div1,
	chCode4div2,
	chCode4div3,
	chCode4div4,
	chCode8div1,
	chCode8div2,
	chCode8div3,
	chCode8div4,
	chCode8div5,
	chCode8div6,
	chCode8div7,
	chCode8div8,
	chCode16div1,
	chCode16div2,
	chCode16div3,
	chCode16div4,
	chCode16div5,
	chCode16div6,
	chCode16div7,
	chCode16div8,
	chCode16div9,
	chCode16div10,
	chCode16div11,
	chCode16div12,
	chCode16div13,
	chCode16div14,
	chCode16div15,
	chCode16div16,
	chCode32div1,
	chCode32div2,
	chCode32div3,
	chCode32div4,
	chCode32div5,
	chCode32div6,
	chCode32div7,
	chCode32div8,
	chCode32div9,
	chCode32div10,
	chCode32div11,
	chCode32div12,
	chCode32div13,
	chCode32div14,
	chCode32div15,
	chCode32div16,
	chCode32div17,
	chCode32div18,
	chCode32div19,
	chCode32div20,
	chCode32div21,
	chCode32div22,
	chCode32div23,
	chCode32div24,
	chCode32div25,
	chCode32div26,
	chCode32div27,
	chCode32div28,
	chCode32div29,
	chCode32div30,
	chCode32div31,
	chCode32div32,
	...
}

TDD-DL-Code-Information ::= SEQUENCE (SIZE (1..maxNrOfDPCHs)) OF TDD-DL-Code-InformationItem

TDD-DL-Code-InformationItem	 ::= SEQUENCE {
	dPCH-ID									DPCH-ID,
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	iE-Extensions							ProtocolExtensionContainer { { TDD-DL-Code-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

TDD-DL-Code-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TDD-DL-Code-LCR-Information ::= SEQUENCE (SIZE (1..maxNrOfDPCHLCRs)) OF TDD-DL-Code-LCR-InformationItem

TDD-DL-Code-LCR-InformationItem ::= SEQUENCE {
	dPCH-ID									DPCH-ID,
	tdd-ChannelisationCodeLCR				TDD-ChannelisationCodeLCR,
	tdd-DL-DPCH-TimeSlotFormat-LCR			TDD-DL-DPCH-TimeSlotFormat-LCR,
	iE-Extensions							ProtocolExtensionContainer { { TDD-DL-Code-LCR-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

TDD-DL-Code-LCR-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TDD-DL-Code-768-Information ::= SEQUENCE (SIZE (1..maxNrOfDPCHs768)) OF TDD-DL-Code-768-InformationItem

TDD-DL-Code-768-InformationItem	 ::= SEQUENCE {
	dPCH-ID									DPCH-ID,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	iE-Extensions							ProtocolExtensionContainer { { TDD-DL-Code-768-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

TDD-DL-Code-768-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TDD-DL-DPCH-TimeSlotFormat-LCR ::= CHOICE {
	qPSK						QPSK-DL-DPCH-TimeSlotFormatTDD-LCR,
	eightPSK					EightPSK-DL-DPCH-TimeSlotFormatTDD-LCR,
	-- For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, this IE denotes MBSFN S-CCPCH time slot format
	...
}

QPSK-DL-DPCH-TimeSlotFormatTDD-LCR ::= INTEGER(0..24,...)

EightPSK-DL-DPCH-TimeSlotFormatTDD-LCR ::= INTEGER(0..24,...)
-- For 1.28 Mcps TDD, if the cell is operating in MBSFN only mode, this IE denotes MBSFN S-CCPCH time slot format，INTEGER(0..11,...)

TDD-DPCHOffset ::= CHOICE {
	initialOffset		INTEGER (0..255),
	noinitialOffset		INTEGER (0..63)
}

TDD-PhysicalChannelOffset ::= INTEGER (0..63)

TDD-TPC-DownlinkStepSize ::= ENUMERATED {
	step-size1,
	step-size2,
	step-size3,
	...
}

TDD-TPC-UplinkStepSize-LCR ::= ENUMERATED {
	step-size1,
	step-size2,
	step-size3,
	...
}

TransportFormatCombination-Beta ::= CHOICE {
	signalledGainFactors		SEQUENCE {
		gainFactor					CHOICE {
			fdd							SEQUENCE {
				betaC						BetaCD,
				betaD						BetaCD,
				iE-Extensions		ProtocolExtensionContainer { { GainFactorFDD-ExtIEs } }		OPTIONAL,
				...
			},
			tdd							BetaCD,
			...
		},
	    refTFCNumber				RefTFCNumber	OPTIONAL,
		iE-Extensions			ProtocolExtensionContainer { { SignalledGainFactors-ExtIEs } }		OPTIONAL,
		...
	},
	computedGainFactors				RefTFCNumber,
	...
}

GainFactorFDD-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

SignalledGainFactors-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TDD-UL-Code-Information ::= SEQUENCE (SIZE (1..maxNrOfDPCHs)) OF TDD-UL-Code-InformationItem

TDD-UL-Code-InformationItem ::= SEQUENCE {
	dPCH-ID									DPCH-ID,
	tdd-ChannelisationCode					TDD-ChannelisationCode,
	iE-Extensions							ProtocolExtensionContainer { { TDD-UL-Code-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

TDD-UL-Code-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TDD-UL-Code-LCR-Information ::= SEQUENCE (SIZE (1..maxNrOfDPCHLCRs)) OF TDD-UL-Code-LCR-InformationItem

TDD-UL-Code-LCR-InformationItem ::= SEQUENCE {
	dPCH-ID									DPCH-ID,
	tdd-ChannelisationCodeLCR				TDD-ChannelisationCodeLCR,
	tdd-UL-DPCH-TimeSlotFormat-LCR			TDD-UL-DPCH-TimeSlotFormat-LCR,
	iE-Extensions							ProtocolExtensionContainer { { TDD-UL-Code-LCR-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

TDD-UL-Code-LCR-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}
TDD-UL-Code-768-Information ::= SEQUENCE (SIZE (1..maxNrOfDPCHs)) OF TDD-UL-Code-768-InformationItem

TDD-UL-Code-768-InformationItem ::= SEQUENCE {
	dPCH-ID									DPCH-ID,
	tdd-ChannelisationCode768				TDD-ChannelisationCode768,
	iE-Extensions							ProtocolExtensionContainer { { TDD-UL-Code-768-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

TDD-UL-Code-768-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TDD-UL-DPCH-TimeSlotFormat-LCR ::= CHOICE {
	qPSK						QPSK-UL-DPCH-TimeSlotFormatTDD-LCR,
	eightPSK					EightPSK-UL-DPCH-TimeSlotFormatTDD-LCR,
	...
}

QPSK-UL-DPCH-TimeSlotFormatTDD-LCR ::= INTEGER(0..69,...)

EightPSK-UL-DPCH-TimeSlotFormatTDD-LCR ::= INTEGER(0..24,...)

TFCI-Coding ::= ENUMERATED {
	v4,
	v8,
	v16,
	v32,
	...
}

TFCI-Presence ::= ENUMERATED {
	present,
	not-present
}

TFCI-SignallingMode ::= SEQUENCE {
	tFCI-SignallingOption		TFCI-SignallingMode-TFCI-SignallingOption,
	not-Used-splitType			NULL				OPTIONAL,
	not-Used-lengthOfTFCI2		NULL				OPTIONAL,
	iE-Extensions				ProtocolExtensionContainer { { TFCI-SignallingMode-ExtIEs} }		OPTIONAL,
	...
}

TFCI-SignallingMode-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TFCI-SignallingMode-TFCI-SignallingOption ::= ENUMERATED {
	normal,
	not-Used-split
}

TGD					::= INTEGER (0|15..269)
-- 0 = Undefined, only one transmission gap in the transmission gap pattern sequence 

TGPRC 				::= INTEGER (0..511)
-- 0 = infinity

TGPSID				::= INTEGER (1.. maxTGPS)

TGSN				::= INTEGER (0..14)

TimeSlot ::= INTEGER (0..14)

TimeSlotDirection ::= ENUMERATED {
	ul,
	dl,
	...
}

TimeSlot-InitiatedListLCR ::= SEQUENCE (SIZE (0..6)) OF TimeSlotLCR

TimeSlotLCR ::= INTEGER (0..6)

TimeslotLCR-Extension ::= ENUMERATED {
	ts7,
	...
}
-- ts7 indicates the MBSFN Special Timeslot for 1.28Mcps TDD MBSFN Dedicated Carrier.

TimeSlotMeasurementValueListLCR::= SEQUENCE (SIZE (1..6)) OF TimeSlotMeasurementValueLCR

TimeSlotMeasurementValueLCR ::= SEQUENCE {
	timeSlotLCR					TimeSlotLCR, 
	commonMeasurementValue		CommonMeasurementValue, 
	iE-Extensions				ProtocolExtensionContainer { {TimeSlotMeasurementValueListLCR-ExtIEs} } OPTIONAL,
	...
}

TimeSlotMeasurementValueListLCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TimeSlotStatus ::= ENUMERATED {
	active,
	not-active,
	...
}

TimingAdjustmentValue ::= CHOICE {
	initialPhase		INTEGER (0..1048575,...),
	steadyStatePhase	INTEGER (0..255,...)
}

TimingAdjustmentValueLCR ::= CHOICE {
	initialPhase		INTEGER (0..524287,...),
	steadyStatePhase	INTEGER (0..127,...)
}

TimingAdvanceApplied ::= ENUMERATED {
	yes,
	no
}

SynchronisationIndicator ::= ENUMERATED {
	timingMaintainedSynchronisation,
	...
}

TnlQos ::= CHOICE {
	dsField					DsField,
	genericTrafficCategory	GenericTrafficCategory,
	...
}

ToAWE ::= INTEGER (0..2559)
-- Unit ms

ToAWS ::= INTEGER (0..1279)
-- Unit ms

Transmission-Gap-Pattern-Sequence-Information ::= SEQUENCE (SIZE (1..maxTGPS)) OF
	SEQUENCE {
		tGPSID			TGPSID,
		tGSN			TGSN,
		tGL1			GapLength,
		tGL2			GapLength	OPTIONAL,
		tGD				TGD,
		tGPL1			GapDuration,
		not-to-be-used-1			GapDuration	OPTIONAL,
			-- This IE shall never be included in the SEQUENCE. If received it shall be ignored
		uL-DL-mode		UL-DL-mode,
		downlink-Compressed-Mode-Method		Downlink-Compressed-Mode-Method		OPTIONAL,
			-- This IE shall be present if the UL/DL mode IE is set to "DL only" or "UL/DL"
		uplink-Compressed-Mode-Method		Uplink-Compressed-Mode-Method		OPTIONAL,
			-- This IE shall be present if the UL/DL mode IE is set to "UL only" or "UL/DL"
		dL-FrameType		DL-FrameType,
		delta-SIR1			DeltaSIR,
		delta-SIR-after1	DeltaSIR,
		delta-SIR2			DeltaSIR	OPTIONAL,
		delta-SIR-after2	DeltaSIR	OPTIONAL,
		iE-Extensions			ProtocolExtensionContainer { {Transmission-Gap-Pattern-Sequence-Information-ExtIEs} } OPTIONAL,
		...
	}

Transmission-Gap-Pattern-Sequence-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TransmissionGapPatternSequenceCodeInformation	::= ENUMERATED{
code-change,
nocode-change
}

TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmissionCellPortionValue ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCell)) OF TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmissionCellPortionValue-Item

TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmissionCellPortionValue-Item ::= SEQUENCE{
	cellPortionID							CellPortionID,
	transmittedCarrierPowerOfAllCodesNotUsedForHSTransmissionValue	TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmissionValue,
	iE-Extensions							ProtocolExtensionContainer { { TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmissionCellPortionValue-Item-ExtIEs} }		OPTIONAL,
	...
}

TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmissionCellPortionValue-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmissionCellPortionValue ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCellLCR)) OF TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmissionCellPortionValue-Item

TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmissionCellPortionValue-Item ::= SEQUENCE{
	cellPortionLCRID							CellPortionLCRID,
	transmittedCarrierPowerOfAllCodesNotUsedForHSTransmissionValue	TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmissionValue,
	iE-Extensions							ProtocolExtensionContainer { { TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmissionCellPortionValue-Item-ExtIEs} }		OPTIONAL,
	...
}

TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmissionCellPortionValue-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmissionValue ::= INTEGER(0..100)
-- According to mapping in TS 25.133 [22] and TS 25.123 [23]

Transmitted-Carrier-Power-For-CellPortion-Value ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCell)) OF Transmitted-Carrier-Power-For-CellPortion-Value-Item

Transmitted-Carrier-Power-For-CellPortion-Value-Item ::= SEQUENCE{
	cellPortionID							CellPortionID, 
	transmitted-Carrier-Power-Value			Transmitted-Carrier-Power-Value,
	iE-Extensions							ProtocolExtensionContainer { { Transmitted-Carrier-Power-For-CellPortion-Value-Item-ExtIEs} }		OPTIONAL,
	...
}

Transmitted-Carrier-Power-For-CellPortion-Value-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Transmitted-Carrier-Power-For-CellPortion-ValueLCR ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCellLCR)) OF Transmitted-Carrier-Power-For-CellPortion-ValueLCR-Item

Transmitted-Carrier-Power-For-CellPortion-ValueLCR-Item ::= SEQUENCE{
	cellPortionLCRID							CellPortionLCRID, 
	transmitted-Carrier-Power-Value			Transmitted-Carrier-Power-Value,
	iE-Extensions							ProtocolExtensionContainer { { Transmitted-Carrier-Power-For-CellPortion-ValueLCR-Item-ExtIEs} }		OPTIONAL,
	...
}

Transmitted-Carrier-Power-For-CellPortion-ValueLCR-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Transmitted-Carrier-Power-Value ::= INTEGER(0..100)
-- According to mapping in TS 25.133 [22]/TS 25.123 [23]

Transmitted-Code-Power-Value ::= INTEGER (0..127)
-- According to mapping in TS 25.133 [22]/TS 25.123 [23]. Values 0 to 9 and 123 to 127 shall not be used.

Transmitted-Code-Power-Value-IncrDecrThres ::= INTEGER (0..112,...)

TransmissionDiversityApplied ::= BOOLEAN
-- true: applied, false: not applied

TransmitDiversityIndicator ::= ENUMERATED {
	active,
	inactive
}

TFCS ::= SEQUENCE {
	tFCSvalues					CHOICE {
		no-Split-in-TFCI			TFCS-TFCSList,
		not-Used-split-in-TFCI		NULL,
		-- This choice shall never be made by the CRNC and the Node B shall consider the procedure as failed if it is received.
		...
	},
	iE-Extensions		ProtocolExtensionContainer  { { TFCS-ExtIEs} }		OPTIONAL,
	...
}

TFCS-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TFCS-TFCSList ::= SEQUENCE (SIZE (1..maxNrOfTFCs)) OF
	SEQUENCE {
		cTFC				TFCS-CTFC,
		tFC-Beta		TransportFormatCombination-Beta 	OPTIONAL,
		-- The IE shall be present if the TFCS concerns a UL DPCH or PRACH channel [FDD – or PCPCH channel].
		iE-Extensions		ProtocolExtensionContainer  { { TFCS-TFCSList-ExtIEs} }		OPTIONAL,
		...
}

TFCS-TFCSList-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-Gainfactors-10ms-mode	CRITICALITY reject	EXTENSION Gainfactors-10ms-mode		PRESENCE optional},
	...
}

TFCS-CTFC ::= CHOICE {
	ctfc2bit							INTEGER (0..3),
	ctfc4bit							INTEGER (0..15),
	ctfc6bit							INTEGER (0..63),
	ctfc8bit							INTEGER (0..255),
	ctfc12bit							INTEGER (0..4095),
	ctfc16bit							INTEGER (0..65535),
	ctfcmaxbit							INTEGER (0..maxCTFC)
}

TPC-slot-position ::= SEQUENCE {
	slot-position			INTEGER(0..4)		OPTIONAL,
	iE-Extensions			ProtocolExtensionContainer { { TPC-slot-position-ExtIEs } }		OPTIONAL,
	...
}

TPC-slot-position-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

Transport-Block-Size-Index ::= INTEGER(1..maxNrOfHS-DSCH-TBSs)

Transport-Block-Size-Index-for-Enhanced-PCH ::= INTEGER(1..32)
-- Index of the value range 1 to 32 of the MAC-ehs transport block size as specified in appendix A of TS 25.321 [32]

Transport-Block-Size-List ::= SEQUENCE (SIZE (1..maxNrOfHS-DSCHTBSsE-PCH)) OF
	SEQUENCE {
		transport-Block-Size-Index-for-Enhanced-PCH			Transport-Block-Size-Index-for-Enhanced-PCH,
		iE-Extensions				ProtocolExtensionContainer  { { Transport-Block-Size-List-ExtIEs} }		OPTIONAL,
		...
	}

Transport-Block-Size-List-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TransportBearerRequestIndicator ::= ENUMERATED {
	bearerRequested,
	bearerNotRequested,
	...
}

TransportBearerNotRequestedIndicator ::= ENUMERATED {
	transport-bearer-shall-not-be-established,
	transport-bearer-may-not-be-established
}

TransportBearerNotSetupIndicator ::= ENUMERATED {
	transport-bearer-not-setup
}

TransportFormatSet ::= SEQUENCE {
	dynamicParts			TransportFormatSet-DynamicPartList,
	semi-staticPart			TransportFormatSet-Semi-staticPart,
	iE-Extensions			ProtocolExtensionContainer  { { TransportFormatSet-ExtIEs} }		OPTIONAL,
	...
}

TransportFormatSet-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TransportFormatSet-DynamicPartList ::= SEQUENCE (SIZE (1..maxNrOfTFs)) OF
	SEQUENCE {
		nrOfTransportBlocks			TransportFormatSet-NrOfTransportBlocks,
		transportBlockSize			TransportFormatSet-TransportBlockSize		OPTIONAL,
		-- This IE shall be present if the Number of Transport Blocks IE is set to a value greater than 0
		mode						TransportFormatSet-ModeDP,
		iE-Extensions				ProtocolExtensionContainer  { { TransportFormatSet-DynamicPartList-ExtIEs} }		OPTIONAL,
		...
	}

TransportFormatSet-DynamicPartList-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TDD-TransportFormatSet-ModeDP ::= SEQUENCE {
	transmissionTimeIntervalInformation		TransmissionTimeIntervalInformation		OPTIONAL,
	-- This IE shall be present if the Transmission Time Interval IE in the Semi-static Transport Format Information IE is set to “dynamic”
	iE-Extensions							ProtocolExtensionContainer { {TDD-TransportFormatSet-ModeDP-ExtIEs} } OPTIONAL,
	...
	}

TDD-TransportFormatSet-ModeDP-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TransmissionTimeIntervalInformation ::= SEQUENCE (SIZE (1..maxTTI-count)) OF
	SEQUENCE {
		transmissionTimeInterval		TransportFormatSet-TransmissionTimeIntervalDynamic,
	iE-Extensions						ProtocolExtensionContainer { { TransmissionTimeIntervalInformation-ExtIEs} }		OPTIONAL,
	...
}

TransmissionTimeIntervalInformation-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TransportFormatSet-Semi-staticPart ::= SEQUENCE {
	transmissionTimeInterval	 		TransportFormatSet-TransmissionTimeIntervalSemiStatic,
	channelCoding					TransportFormatSet-ChannelCodingType,
	codingRate						TransportFormatSet-CodingRate				OPTIONAL,
	-- This IE shall be present if the Type of channel coding IE is set to 'convolutional' or 'turbo' 
	rateMatchingAttribute			TransportFormatSet-RateMatchingAttribute,
	cRC-Size						TransportFormatSet-CRC-Size,
	mode							TransportFormatSet-ModeSSP	,
	iE-Extensions					ProtocolExtensionContainer { { TransportFormatSet-Semi-staticPart-ExtIEs} }		OPTIONAL,
	...
}

TransportFormatSet-Semi-staticPart-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TransportFormatSet-ChannelCodingType ::= ENUMERATED {
	no-codingTDD,
	convolutional-coding,
	turbo-coding,
	...
}

TransportFormatSet-CodingRate ::= ENUMERATED {
	half,
	third,
	...
}

TransportFormatSet-CRC-Size ::= ENUMERATED {
	v0,
	v8,
	v12,
	v16,
	v24,
	...
}

TransportFormatSet-ModeDP ::= CHOICE {
	tdd 				TDD-TransportFormatSet-ModeDP,
	notApplicable				NULL,
	...
}

TransportFormatSet-ModeSSP ::= CHOICE {
	tdd				TransportFormatSet-SecondInterleavingMode,
	notApplicable				NULL,
	...
}

TransportFormatSet-NrOfTransportBlocks ::= INTEGER (0..512)

TransportFormatSet-RateMatchingAttribute ::= INTEGER (1..maxRateMatching)

TransportFormatSet-SecondInterleavingMode ::= ENUMERATED {
	frame-related,
	timeSlot-related,
	...
}

TransportFormatSet-TransmissionTimeIntervalDynamic ::= ENUMERATED {
	msec-10,
	msec-20,
	msec-40,
	msec-80,
	...
}

TransportFormatSet-TransmissionTimeIntervalSemiStatic ::= ENUMERATED {
	msec-10,
	msec-20,
	msec-40,
	msec-80,
	dynamic,
	...,
	msec-5
}

TransportFormatSet-TransportBlockSize ::= INTEGER (0..5000)

TransportLayerAddress ::= BIT STRING (SIZE (1..160, ...))

TS0-CapabilityLCR ::= ENUMERATED {
	tS0-Capable,
	tS0-Not-Capable
}

TSTD-Indicator ::= ENUMERATED {
	active,
	inactive
}


TSN-Length ::= ENUMERATED {
	tsn-6bits,
	tsn-9bits
}

TUTRANGANSS ::= SEQUENCE {
	mS				INTEGER(0..16383),
	lS				INTEGER(0..4294967295)
}

TUTRANGANSSAccuracyClass ::= ENUMERATED {
	ganssAccuracy-class-A,
	ganssAccuracy-class-B,
	ganssAccuracy-class-C,
	...
}

TUTRANGANSSMeasurementThresholdInformation ::= SEQUENCE {
	tUTRANGANSSChangeLimit				INTEGER(1..256)												OPTIONAL,
	predictedTUTRANGANSSDeviationLimit	INTEGER(1..256)												OPTIONAL,
	ie-Extensions			ProtocolExtensionContainer { { TUTRANGANSSMeasurementThresholdInformation-ExtIEs } }	OPTIONAL,
	...
}

TUTRANGANSSMeasurementThresholdInformation-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TUTRANGANSSMeasurementValueInformation ::= SEQUENCE {
	tUTRANGANSS						TUTRANGANSS,
	tUTRANGANSSQuality				INTEGER(0..255)													OPTIONAL,
	tUTRANGANSSDriftRate			INTEGER(-50..50),
	tUTRANGANSSDriftRateQuality		INTEGER(0..50)													OPTIONAL,
	ie-Extensions			ProtocolExtensionContainer { { TUTRANGANSSMeasurementValueInformation-ExtIEs } }	OPTIONAL,
	...
}

TUTRANGANSSMeasurementValueInformation-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-GANSS-Time-ID			CRITICALITY ignore		EXTENSION GANSS-Time-ID		PRESENCE 	optional},
	...
}

TUTRANGPS ::= SEQUENCE {
	ms-part 	INTEGER (0..16383),
	ls-part		INTEGER (0..4294967295)
}

TUTRANGPSChangeLimit ::= INTEGER (1..256)
-- Unit chip, Step 1/16 chip, Range 1/16..16 chip

TUTRANGPSDriftRate ::= INTEGER (-50..50)
-- Unit chip/s, Step 1/256 chip/s, Range -50/256..+50/256 chip/s

TUTRANGPSDriftRateQuality ::= INTEGER (0..50)
-- Unit chip/s, Step 1/256 chip/s, Range 0..50/256 chip/s

TUTRANGPSAccuracyClass ::= ENUMERATED {
	accuracy-class-A,
	accuracy-class-B,
	accuracy-class-C,
	...
}

TUTRANGPSMeasurementThresholdInformation ::= SEQUENCE {
	tUTRANGPSChangeLimit					TUTRANGPSChangeLimit					OPTIONAL,
	predictedTUTRANGPSDeviationLimit		PredictedTUTRANGPSDeviationLimit		OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { TUTRANGPSMeasurementThresholdInformation-ExtIEs} }		OPTIONAL,
	...
}

TUTRANGPSMeasurementThresholdInformation-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TUTRANGPSMeasurementValueInformation ::= SEQUENCE {
		tUTRANGPS						TUTRANGPS,
		tUTRANGPSQuality				TUTRANGPSQuality				OPTIONAL,
		tUTRANGPSDriftRate				TUTRANGPSDriftRate,
		tUTRANGPSDriftRateQuality		TUTRANGPSDriftRateQuality		OPTIONAL,
		iE-Extensions					ProtocolExtensionContainer { {TUTRANGPSMeasurementValueInformationItem-ExtIEs} }		OPTIONAL,
		...
}

TUTRANGPSMeasurementValueInformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

TUTRANGPSQuality ::= INTEGER (0..255)
-- Unit chip, Step 1/16 chip, Range 0.. 255/16 chip

TxDiversityOnDLControlChannelsByMIMOUECapability ::= ENUMERATED {
	dL-Control-Channel-Tx-Diversity-for-MIMO-UE-with-non-diverse-P-CPICH-Capable,
	dL-Control-Channel-Tx-Diversity-for-MIMO-UE-with-non-diverse-P-CPICH-Not-Capable
}

TypeOfError ::= ENUMERATED {
	not-understood,
	missing,
	...
}

Two-ms-Overridden-E-DCH-RACH-Resources ::= INTEGER(0..240,...)
-- According to mapping in TS 25.302 [25].

Two-ms-Grant-E-DCH-RACH-Resources ::= INTEGER(0..240,...)
-- According to mapping in TS 25.302 [25].

Two-ms-Denied-E-DCH-RACH-Resources ::= INTEGER(0..240,...)
-- According to mapping in TS 25.302 [25].

Two-msand10msTTI-Concurrent-Deployment-Capability ::= ENUMERATED {
	twomsand10msTTI-Concurrent-Deployment-capable,
	twomsand10msTTI-Concurrent-Deployment-non-capable
}

Two-level-DRX ::= SEQUENCE {
	t32x							T32x													OPTIONAL,
	hS-DSCH-first-Rx-burst-FACH		HS-DSCH-first-Rx-burst-FACH								OPTIONAL,
	hS-DSCH-first-DRX-ycle-FACH		HS-DSCH-first-DRX-ycle-FACH								OPTIONAL,
	hS-DSCH-second-Rx-burst-FACH	HS-DSCH-second-Rx-burst-FACH							OPTIONAL,
	t32y							T32y													OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { Two-level-DRX-ExtIEs } }	OPTIONAL,
	...
}


Two-level-DRX-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

T32x ::= ENUMERATED {v20, v40, v60, v80}

T32y ::= ENUMERATED {v0dot5, v1, v2, v4}

-- ==========================================
--	U
-- ==========================================

UARFCN ::= INTEGER (0..16383, ...)
-- corresponds to 0MHz .. 3276.6MHz

UC-Id ::= SEQUENCE {
	rNC-ID				RNC-ID,
	c-ID				C-ID,
	iE-Extensions			ProtocolExtensionContainer { {UC-Id-ExtIEs} } OPTIONAL,
	...
}
UC-Id-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-Extended-RNC-ID		CRITICALITY  reject		EXTENSION	Extended-RNC-ID	PRESENCE	optional},
	...
}

UDRE ::= ENUMERATED {
    udre-minusequal-one-m,
    udre-betweenoneandfour-m,
    udre-betweenfourandeight-m,
    udre-greaterequaleight-m
}

UDREGrowthRate ::=					ENUMERATED { 	
										growth-1-point-5, 
										growth-2,
										growth-4,
										growth-6,
										growth-8,
										growth-10,
										growth-12,
										growth-16	}

UDREValidityTime	::=					ENUMERATED {
											val-20sec,
											val-40sec,
											val-80sec,
											val-160sec,
											val-320sec,
											val-640sec,
											val-1280sec,
											val-2560sec	}

UE-AggregateMaximumBitRate ::= SEQUENCE {
	uE-AggregateMaximumBitRateDownlink		UE-AggregateMaximumBitRateDownlink	OPTIONAL,
	uE-AggregateMaximumBitRateUplink		UE-AggregateMaximumBitRateUplink	OPTIONAL,
	...
}

UE-AggregateMaximumBitRateDownlink			::= INTEGER (1..1000000000)
-- Unit is bits per sec

UE-AggregateMaximumBitRateUplink			::= INTEGER (1..1000000000)
-- Unit is bits per sec

UE-AggregateMaximumBitRate-Enforcement-Indicator ::= NULL

UE-Capability-Information ::= SEQUENCE {
	hSDSCH-Physical-Layer-Category		INTEGER (1..64,...),
	iE-Extensions						ProtocolExtensionContainer { { UE-Capability-Information-ExtIEs } }			OPTIONAL,
	...
}

UE-Capability-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ID id-LCRTDD-uplink-Physical-Channel-Capability	CRITICALITY ignore	EXTENSION LCRTDD-Uplink-Physical-Channel-Capability	PRESENCE optional}|
	{ID id-number-Of-Supported-Carriers					CRITICALITY reject	EXTENSION Number-Of-Supported-Carriers		PRESENCE optional}|
	{ID id-MultiCarrier-HSDSCH-Physical-Layer-Category	CRITICALITY ignore	EXTENSION LCRTDD-HSDSCH-Physical-Layer-Category	PRESENCE optional}|
	{ID id-MIMO-SFMode-Supported-For-HSPDSCHDualStream	CRITICALITY ignore	EXTENSION MIMO-SFMode-For-HSPDSCHDualStream		PRESENCE optional}|
	{ID id-UE-TS0-CapabilityLCR							CRITICALITY ignore	EXTENSION UE-TS0-CapabilityLCR			PRESENCE optional}|
	{ID id-UE-RF-Band-CapabilityLCR						CRITICALITY ignore	EXTENSION UE-RF-Band-CapabilityLCR		PRESENCE conditional},
--This IE shall be present if the Number of Supported Carriers IE is equal to "One-Two carrier Discontiguous" or "Two-Two carrier Discontiguous" and the concerned cell and the UE support more than one RF band.--
	...
}

UE-RF-Band-CapabilityLCR ::= SEQUENCE (SIZE (1.. maxFreqBandsTDD)) OF Radio-Frequency-BandItem

Radio-Frequency-BandItem ::= SEQUENCE {
	radio-Frequency-Band					Radio-Frequency-Band,
	iE-Extensions							ProtocolExtensionContainer { { Radio-Frequency-BandItem-ExtIEs } }			OPTIONAL,
	...
}

UE-TS0-CapabilityLCR ::= ENUMERATED {
	uE-TS0-Capable,
	uE-TS0-Not-Capable
}

Radio-Frequency-Band ::= ENUMERATED {
	a,
	b,
	c,
	d,
	e,
	f,
	g,
	h,
	i,
	j,
	k,
	l,
	m,
	n,
	o,
	p,
...
}

Radio-Frequency-BandItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UE-Support-of-non-rectangular-resource-allocation ::= ENUMERATED {
	support
}

UE-SupportIndicatorExtension ::= BIT STRING (SIZE (32))
-- First bit: Different HS-SCCH In Consecutive TTIs Support Indicator
-- Second bit: HS-SCCH orders in HS-SCCH-less Operation Support Indicator
-- Third bit: RRC Rel-9 (onwards) handling of DL secondary HS-DSCH (de)activation state Support Indicator
-- Fourth bit: UE DTX/DRX related HS-SCCH orders uniform behavior indicator
-- Fifth bit: UE longer HARQ processing time for Multiflow and MIMO indicator
-- Sixth bit: UE blind HARQ retransmissions indicator for HSDPA
-- Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver.

LCRTDD-HSDSCH-Physical-Layer-Category ::= INTEGER (1..64)

UE-DPCCH-burst1 ::= ENUMERATED {v1, v2, v5}
	-- Unit subframe

UE-DPCCH-burst2 ::= ENUMERATED {v1, v2, v5}
	-- Unit subframe

UE-DRX-Cycle ::= ENUMERATED {v4, v5, v8, v10, v16, v20}
	-- Unit subframe

UE-DRX-Grant-Monitoring ::= BOOLEAN
	-- true: applied, false: not applied

UE-DTX-Cycle1-2ms ::= ENUMERATED {v1, v4, v5, v8, v10, v16, v20}
	-- Unit subframe

UE-DTX-Cycle1-10ms ::= ENUMERATED {v1, v5, v10, v20}
	-- Unit subframe

UE-DTX-Cycle2-2ms ::= ENUMERATED {v4, v5, v8, v10, v16, v20, v32, v40, v64, v80, v128, v160}
	-- Unit subframe

UE-DTX-Cycle2-ext-2ms ::= ENUMERATED {v4, v5, v8, v10, v16, v20, v32, v40, v64, v80, v128, v160, v256, v320, v512, v640, v1024, v1280}
	-- Unit subframe

UE-DTX-Cycle2-10ms ::= ENUMERATED {v5, v10, v20, v40, v80, v160}
	-- Unit subframe

UE-DTX-DRX-Offset ::= INTEGER (0..159)
	-- Unit subframe

UE-DTX-Long-Preamble ::= ENUMERATED {v2, v4, v15}
	-- Units of slots

UE-transmission-power-headroom-Value ::= INTEGER (0..31)

UE-Measurement-Value ::= CHOICE {
	uPHFiltering-Value						UPHFiltering-Value,
	extension-UE-Measurement-Value		Extension-UE-Measurement-Value
}

Extension-UE-Measurement-Value ::= ProtocolIE-Single-Container {{ Extension-UE-Measurement-ValueIE}}

Extension-UE-Measurement-ValueIE NBAP-PROTOCOL-IES ::= {
	...
}

UPHFiltering-Value ::= INTEGER (0..32)
-- According to mapping in TS 25.321

UL-CapacityCredit ::= INTEGER (0..65535)

UL-Delta-T2TP ::= INTEGER (0..6,...)

UL-DL-mode ::= ENUMERATED {
	ul-only,
	dl-only,
	both-ul-and-dl
}

UL-DPDCH-Indicator-For-E-DCH-Operation ::= ENUMERATED {
	ul-DPDCH-present,
	ul-DPDCH-not-present
}

Uplink-Compressed-Mode-Method 	::= ENUMERATED {
	sFdiv2,
	higher-layer-scheduling,
	...
}

UL-Timeslot-Information ::= SEQUENCE (SIZE (1..maxNrOfULTSs)) OF UL-Timeslot-InformationItem

UL-Timeslot-InformationItem ::= SEQUENCE {
	timeSlot								TimeSlot,
	midambleShiftAndBurstType				MidambleShiftAndBurstType,
	tFCI-Presence							TFCI-Presence,
	uL-Code-InformationList					TDD-UL-Code-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-Timeslot-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

UL-Timeslot-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-TimeslotLCR-Information ::= SEQUENCE (SIZE (1..maxNrOfULTSLCRs)) OF UL-TimeslotLCR-InformationItem

UL-TimeslotLCR-InformationItem ::= SEQUENCE {
	timeSlotLCR								TimeSlotLCR,
	midambleShiftLCR						MidambleShiftLCR,
	tFCI-Presence							TFCI-Presence,
	uL-Code-InformationList					TDD-UL-Code-LCR-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-TimeslotLCR-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

UL-TimeslotLCR-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
{ ID id-PLCCH-Information-UL-TimeslotLCR-Info	CRITICALITY reject		EXTENSION PLCCHinformation	PRESENCE optional },
	...
}

UL-Timeslot768-Information ::= SEQUENCE (SIZE (1..maxNrOfULTSs)) OF UL-Timeslot768-InformationItem

UL-Timeslot768-InformationItem ::= SEQUENCE {
	timeSlot								TimeSlot,
	midambleShiftAndBurstType768			MidambleShiftAndBurstType768,
	tFCI-Presence							TFCI-Presence,
	uL-Code-InformationList					TDD-UL-Code-768-Information,
	iE-Extensions							ProtocolExtensionContainer { { UL-Timeslot768-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

UL-Timeslot768-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-DPCCH-SlotFormat ::= INTEGER (0..5,...)

UL-SIR ::= INTEGER (-82..173)
-- According to mapping in TS 25.427 [16]

UL-FP-Mode ::= ENUMERATED {
	normal,
	silent,
	...
}

UL-PhysCH-SF-Variation ::= ENUMERATED {
	sf-variation-supported,
	sf-variation-not-supported
}

UL-ScramblingCode ::= SEQUENCE {
	uL-ScramblingCodeNumber			UL-ScramblingCodeNumber,
	uL-ScramblingCodeLength			UL-ScramblingCodeLength,
	iE-Extensions					ProtocolExtensionContainer { { UL-ScramblingCode-ExtIEs } }		OPTIONAL,
	...
}

UL-ScramblingCode-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-ScramblingCodeNumber ::= INTEGER (0..16777215)

UL-ScramblingCodeLength ::= ENUMERATED {
	short,
	long
}

UL-Synchronisation-Parameters-LCR ::= SEQUENCE {
	uL-Synchronisation-StepSize			UL-Synchronisation-StepSize,
	uL-Synchronisation-Frequency		UL-Synchronisation-Frequency,
	iE-Extensions						ProtocolExtensionContainer { { UL-Synchronisation-Parameters-LCR-ExtIEs } }		OPTIONAL,
	...
}

UL-Synchronisation-Parameters-LCR-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-Synchronisation-StepSize ::= INTEGER (1..8)

UL-Synchronisation-Frequency ::= INTEGER (1..8)

UPPCHPositionLCR ::= INTEGER (0..127)

UL-TimeSlot-ISCP-Info ::= SEQUENCE (SIZE (1..maxNrOfULTSs)) OF	UL-TimeSlot-ISCP-InfoItem

UL-TimeSlot-ISCP-InfoItem ::= SEQUENCE {
 	timeSlot						TimeSlot,
	iSCP							UL-TimeslotISCP-Value,
	iE-Extensions					ProtocolExtensionContainer { { UL-TimeSlot-ISCP-InfoItem-ExtIEs} }		OPTIONAL,
	...
 }

UL-TimeSlot-ISCP-InfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-TimeSlot-ISCP-LCR-Info ::= SEQUENCE (SIZE (1..maxNrOfULTSLCRs)) OF	UL-TimeSlot-ISCP-LCR-InfoItem

UL-TimeSlot-ISCP-LCR-InfoItem ::= SEQUENCE {
 	timeSlotLCR						TimeSlotLCR,
	iSCP							UL-TimeslotISCP-Value,
	iE-Extensions					ProtocolExtensionContainer { { UL-TimeSlot-ISCP-LCR-InfoItem-ExtIEs} }		OPTIONAL,
	...
 }

UL-TimeSlot-ISCP-LCR-InfoItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UpPTSInterference-For-CellPortion-Value ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCellLCR)) OF UpPTSInterference-For-CellPortion-Value-Item

UpPTSInterference-For-CellPortion-Value-Item ::= SEQUENCE{
	cellPortionLCRID							CellPortionLCRID, 
	upPTSInterferenceValue						UpPTSInterferenceValue,
	iE-Extensions							ProtocolExtensionContainer { { UpPTSInterference-For-CellPortion-Value-Item-ExtIEs} }		OPTIONAL,
	...
}

UpPTSInterference-For-CellPortion-Value-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UpPTSInterferenceValue ::= INTEGER (0..127,...)

Unidirectional-DCH-Indicator	::= ENUMERATED {
	downlink-DCH-only,
	uplink-DCH-only
}

USCH-Information ::= SEQUENCE (SIZE (1..maxNrOfUSCHs)) OF USCH-InformationItem

USCH-InformationItem ::= SEQUENCE {
	uSCH-ID									USCH-ID,
	cCTrCH-ID								CCTrCH-ID,			-- UL CCTrCH in which the USCH is mapped
	transportFormatSet						TransportFormatSet,	-- For USCH
	allocationRetentionPriority				AllocationRetentionPriority,
	iE-Extensions							ProtocolExtensionContainer { { USCH-InformationItem-ExtIEs} }		OPTIONAL,
	...
}

USCH-InformationItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	{ ID id-bindingID						CRITICALITY	ignore		EXTENSION 	BindingID			PRESENCE 	optional	}|
	-- Shall be ignored if bearer establishment with ALCAP.
	{ ID id-transportlayeraddress			CRITICALITY	ignore		EXTENSION 	TransportLayerAddress	PRESENCE 	optional	}|
	-- Shall be ignored if bearer establishment with ALCAP.
{ ID id-TnlQos							CRITICALITY ignore		EXTENSION	TnlQos	PRESENCE optional	},
	...
}

USCH-InformationResponse ::= SEQUENCE (SIZE (1..maxNrOfUSCHs)) OF USCH-InformationResponseItem

USCH-InformationResponseItem ::= SEQUENCE {
	uSCH-ID										USCH-ID,
	bindingID									BindingID				OPTIONAL,
	transportLayerAddress						TransportLayerAddress	OPTIONAL,
	iE-Extensions								ProtocolExtensionContainer { { USCH-InformationResponseItem-ExtIEs} }		OPTIONAL,
	...
}

USCH-InformationResponseItem-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-CLTD-Information ::= SEQUENCE {
	sDPCCH-PowerOffsetinformation		SDPCCH-PowerOffsetInformation,
	c-ID									C-ID								OPTIONAL,
-- The IE shall be present if there is no serving E-DCH RL or HS-DSCH RL configuration in the concerned Node B Communication Context.
	uL-CLTD-Activation-Information 		UL-CLTD-Activation-Information	OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { UL-CLTD-Information-ExtIEs } }		OPTIONAL,
	...
}

UL-CLTD-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-CLTD-Information-Reconf ::=SEQUENCE{
	setup-Or-ConfigurationChange-Or-Removal-Of-UL-CLTD			Setup-Or-ConfigurationChange-Or-Removal-Of-UL-CLTD,
	iE-Extensions												ProtocolExtensionContainer { { UL-CLTD-Information-Reconf-ExtIEs} } OPTIONAL,
	...
}

UL-CLTD-Information-Reconf-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-CLTD-Information-To-Modify ::= SEQUENCE {
	sDPCCH-PowerOffsetInformation				SDPCCH-PowerOffsetInformation				OPTIONAL,
	uL-CLTD-Activation-Information 			UL-CLTD-Activation-Information			OPTIONAL,
	iE-Extensions							ProtocolExtensionContainer { { UL-CLTD-Information-To-Modify-ExtIEs } }		OPTIONAL,
	...
}

UL-CLTD-Information-To-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-CLTD-Information-Removal ::= ENUMERATED {
	remove,
	...
}

UL-CLTD-State-Update-Information ::= ENUMERATED {
	activate,
	de-activate,
	...
}

UL-CLTD-Activation-Information ::= ENUMERATED {
	activated,
	de-activated,
	...
}

UL-DPCCH2-Information ::= SEQUENCE {
	f-DPCH-Info				F-DPCH-Info,
	iE-Extensions			ProtocolExtensionContainer { { UL-DPCCH2-Information-ExtIEs } }		OPTIONAL,
	...
}

UL-DPCCH2-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-DPCCH2-Information-Reconf ::=SEQUENCE{
	setup-Or-ConfigurationChange-Or-Removal-Of-UL-DPCCH2		Setup-Or-ConfigurationChange-Or-Removal-Of-UL-DPCCH2,
	iE-Extensions												ProtocolExtensionContainer { { UL-DPCCH2-Information-Reconf-ExtIEs} } OPTIONAL,
	...
}

UL-DPCCH2-Information-Reconf-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-DPCCH2-Information-Removal ::= ENUMERATED {
	remove,
	...
}

UL-DPCCH2-Information-To-Modify ::= SEQUENCE {
	f-DPCH-Info				F-DPCH-Info-To-Modify		OPTIONAL,
	iE-Extensions			ProtocolExtensionContainer { { UL-DPCCH2-Information-To-Modify-ExtIEs } }		OPTIONAL,
	...
}

UL-DPCCH2-Information-To-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-MIMO-Information ::= SEQUENCE {
	e-roch-power-offset			E-ROCH-PowerOffset				OPTIONAL,
	s-e-dpcch-power-offset		S-E-DPCCH-PowerOffset,
	interstream-compensation	InterStream-Interference-Compensation,
	minimum-E-TFCI-rank2		INTEGER(0..127),
	iE-Extensions				ProtocolExtensionContainer { { UL-MIMO-Information-ExtIEs } } OPTIONAL,
	...
}

UL-MIMO-Information-To-Modify ::= SEQUENCE {
	e-roch-power-offset			E-ROCH-PowerOffset						OPTIONAL,
	s-e-dpcch-power-offset		S-E-DPCCH-PowerOffset					OPTIONAL,
	interstream-compensation	InterStream-Interference-Compensation	OPTIONAL,
	minimum-E-TFCI-rank2		INTEGER(0..127)							OPTIONAL,
	iE-Extensions				ProtocolExtensionContainer { { UL-MIMO-Information-To-Modify-ExtIEs } } OPTIONAL,
	...
}

UL-MIMO-Reconfiguration ::= CHOICE {
	setup					UL-MIMO-Information,
	configurationChange		UL-MIMO-Information-To-Modify,
	removal					UL-MIMO-Removal
}

UL-MIMO-Removal ::= ENUMERATED {
	remove,
	...
}

UL-MIMO-DL-Control-Channel-Information ::= SEQUENCE {
	e-roch-channelization-code		FDD-DL-ChannelisationCodeNumber,
	s-e-rnti						E-RNTI,
	s-signature-sequence			E-RGCH-Signature-Sequence,
	s-e-roch-release-indicator		S-E-ROCH-Release-Indicator			OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { { UL-MIMO-DL-Control-Channel-Information-ExtIEs } } OPTIONAL,
	...
}

UL-MIMO-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-MIMO-Information-To-Modify-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-MIMO-DL-Control-Channel-Information-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-ROCH-PowerOffset ::= INTEGER(0..255,...)

S-E-DPCCH-PowerOffset ::= INTEGER(0..17,...)

InterStream-Interference-Compensation ::= INTEGER(0..15,...)

S-E-ROCH-Release-Indicator ::= ENUMERATED {s-E-ROCHreleased}

UL-TimeslotISCP-For-CellPortion-Value ::= SEQUENCE (SIZE (1..maxNrOfCellPortionsPerCellLCR)) OF UL-TimeslotISCP-For-CellPortion-Value-Item

UL-TimeslotISCP-For-CellPortion-Value-Item ::= SEQUENCE{
	cellPortionLCRID							CellPortionLCRID, 
	uL-TimeslotISCP-Value						UL-TimeslotISCP-Value,
	iE-Extensions							ProtocolExtensionContainer { { UL-TimeslotISCP-For-CellPortion-Value-Item-ExtIEs} }		OPTIONAL,
	...
}

UL-TimeslotISCP-For-CellPortion-Value-Item-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

UL-TimeslotISCP-Value ::= INTEGER (0..127)
-- According to mapping in TS 25.123 [23]

UL-TimeslotISCP-Value-IncrDecrThres ::= INTEGER (0..126)

USCH-ID ::= INTEGER (0..255)

Usefulness-Of-Battery-Optimization ::= ENUMERATED {can-benefit, cannot-benefit}

Uu-ActivationState ::= ENUMERATED {
	activated,
	de-activated,
	...,
	changeRequest
}

-- ==========================================
--	V
-- ==========================================

-- ==========================================
--	W
-- ==========================================

-- ==========================================
--	X
-- ==========================================

-- ==========================================
--	Y
-- ==========================================

-- ==========================================
--	Z
-- ==========================================

END

9.3.5	Common Definitions
-- **************************************************************
--
-- Common definitions
--
-- **************************************************************

NBAP-CommonDataTypes {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) 
umts-Access (20) modules (3) nbap (2) version1 (1) nbap-CommonDataTypes (3)  }

DEFINITIONS AUTOMATIC TAGS ::= 

BEGIN

-- **************************************************************
--
-- Extension constants
--
-- **************************************************************

maxPrivateIEs 					INTEGER ::= 65535
maxProtocolExtensions 			INTEGER ::= 65535
maxProtocolIEs					INTEGER ::= 65535

-- **************************************************************
--
-- Common Data Types
--
-- **************************************************************

Criticality		::= ENUMERATED { reject, ignore, notify }

MessageDiscriminator	::= ENUMERATED { common, dedicated }

Presence		::= ENUMERATED { optional, conditional, mandatory }

PrivateIE-ID	::= CHOICE {
	local				INTEGER (0..maxPrivateIEs),
	global				OBJECT IDENTIFIER
}

ProcedureCode	::= INTEGER (0..255)

ProcedureID		::= SEQUENCE {
	procedureCode			ProcedureCode,
	ddMode					ENUMERATED { tdd, fdd, common, ... }
}

ProtocolIE-ID		::= INTEGER (0..maxProtocolIEs)

TransactionID 		::= CHOICE {
	shortTransActionId		INTEGER (0..127),
	longTransActionId		INTEGER (0..32767)
}

TriggeringMessage	::= ENUMERATED { initiating-message, successful-outcome, unsuccessfull-outcome, outcome }

END

9.3.6	Constant Definitions
-- **************************************************************
--
-- Constant definitions
--
-- **************************************************************

NBAP-Constants {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) 
umts-Access (20) modules (3) nbap (2) version1 (1) nbap-Constants (4)}

DEFINITIONS AUTOMATIC TAGS ::= 

BEGIN

IMPORTS
	ProcedureCode,
	ProtocolIE-ID
FROM NBAP-CommonDataTypes;

-- **************************************************************
--
-- Elementary Procedures
--
-- **************************************************************

id-audit 												ProcedureCode ::= 0
id-auditRequired 										ProcedureCode ::= 1
id-blockResource 										ProcedureCode ::= 2
id-cellDeletion 										ProcedureCode ::= 3
id-cellReconfiguration 									ProcedureCode ::= 4
id-cellSetup 											ProcedureCode ::= 5
id-cellSynchronisationInitiation						ProcedureCode ::= 45
id-cellSynchronisationReconfiguration					ProcedureCode ::= 46
id-cellSynchronisationReporting							ProcedureCode ::= 47
id-cellSynchronisationTermination						ProcedureCode ::= 48
id-cellSynchronisationFailure							ProcedureCode ::= 49
id-commonMeasurementFailure 							ProcedureCode ::= 6
id-commonMeasurementInitiation 							ProcedureCode ::= 7
id-commonMeasurementReport 								ProcedureCode ::= 8
id-commonMeasurementTermination 						ProcedureCode ::= 9
id-commonTransportChannelDelete 						ProcedureCode ::= 10
id-commonTransportChannelReconfigure 					ProcedureCode ::= 11
id-commonTransportChannelSetup 							ProcedureCode ::= 12
id-compressedModeCommand 								ProcedureCode ::= 14
id-dedicatedMeasurementFailure 							ProcedureCode ::= 16
id-dedicatedMeasurementInitiation 						ProcedureCode ::= 17
id-dedicatedMeasurementReport 							ProcedureCode ::= 18
id-dedicatedMeasurementTermination 						ProcedureCode ::= 19
id-downlinkPowerControl 								ProcedureCode ::= 20
id-downlinkPowerTimeslotControl 						ProcedureCode ::= 38
id-errorIndicationForCommon								ProcedureCode ::= 35
id-errorIndicationForDedicated							ProcedureCode ::= 21
id-informationExchangeFailure							ProcedureCode ::= 40
id-informationExchangeInitiation						ProcedureCode ::= 41
id-informationExchangeTermination						ProcedureCode ::= 42
id-informationReporting									ProcedureCode ::= 43
id-BearerRearrangement									ProcedureCode ::= 50
id-mBMSNotificationUpdate								ProcedureCode ::= 53
id-physicalSharedChannelReconfiguration 				ProcedureCode ::= 37
id-privateMessageForCommon								ProcedureCode ::= 36
id-privateMessageForDedicated							ProcedureCode ::= 22
id-radioLinkAddition 									ProcedureCode ::= 23
id-radioLinkDeletion 									ProcedureCode ::= 24
id-radioLinkFailure 									ProcedureCode ::= 25
id-radioLinkPreemption									ProcedureCode ::= 39
id-radioLinkRestoration 								ProcedureCode ::= 26
id-radioLinkSetup 										ProcedureCode ::= 27
id-reset												ProcedureCode ::= 13
id-resourceStatusIndication 							ProcedureCode ::= 28
id-cellSynchronisationAdjustment						ProcedureCode ::= 44
id-synchronisedRadioLinkReconfigurationCancellation		ProcedureCode ::= 29
id-synchronisedRadioLinkReconfigurationCommit			ProcedureCode ::= 30
id-synchronisedRadioLinkReconfigurationPreparation 		ProcedureCode ::= 31
id-systemInformationUpdate 								ProcedureCode ::= 32
id-unblockResource 										ProcedureCode ::= 33
id-unSynchronisedRadioLinkReconfiguration 				ProcedureCode ::= 34
id-radioLinkActivation									ProcedureCode ::= 51
id-radioLinkParameterUpdate								ProcedureCode ::= 52
id-uEStatusUpdate										ProcedureCode ::= 54
id-secondaryULFrequencyReporting						ProcedureCode ::= 55
id-secondaryULFrequencyUpdate							ProcedureCode ::= 56
id-uEStatusUpdateConfirmation							ProcedureCode ::= 57

-- **************************************************************
--
-- Lists
--
-- **************************************************************

maxNrOfCodes				INTEGER ::= 10
maxNrOfDLTSs				INTEGER ::= 15
maxNrOfDLTSLCRs				INTEGER ::= 6
maxNrOfErrors				INTEGER ::= 256
maxNrOfTFs					INTEGER ::= 32
maxNrOfTFCs					INTEGER ::= 1024
maxNrOfRLs					INTEGER ::= 16
maxNrOfRLs-1				INTEGER ::= 15	-- maxNrOfRLs – 1
maxNrOfRLs-2				INTEGER ::= 14	-- maxNrOfRLs – 2
maxNrOfRLSets				INTEGER ::= maxNrOfRLs
maxNrOfDPCHs				INTEGER ::= 240
maxNrOfDPCHsPerRL-1			INTEGER ::= 239 -- maxNrofCCTrCH*maxNrOfULTSs-1
maxNrOfDPCHLCRs				INTEGER ::= 240
maxNrOfDPCHsLCRPerRL-1		INTEGER ::= 95  -- maxNrofCCTrCH*maxNrOfULTSLCRs-1
maxNrOfDPCHs768				INTEGER ::= 480
maxNrOfDPCHs768PerRL-1		INTEGER ::= 479
maxNrOfSCCPCHs				INTEGER ::= 8
maxNrOfSCCPCHsinExt			INTEGER ::= 232
maxNrOfSCCPCHs768			INTEGER ::= 480
maxNrOfDCHs					INTEGER ::= 128
maxNrOfDSCHs				INTEGER ::= 32
maxNrOfFACHs				INTEGER ::= 8
maxNrOfCCTrCHs				INTEGER ::= 16
maxNrOfPDSCHs				INTEGER ::= 256
maxNrOfHSPDSCHs				INTEGER ::= 16
maxNrOfHSPDSCHs768			INTEGER ::= 32
maxNrOfPUSCHs				INTEGER ::= 256
maxNrOfPUSCHs-1				INTEGER ::= 255
maxNrOfPDSCHSets			INTEGER ::= 256
maxNrOfPRACHLCRs			INTEGER ::= 8
maxNrOfPUSCHSets			INTEGER ::= 256
maxNrOfSCCPCHLCRs			INTEGER ::= 8
maxNrOfSCCPCHsLCRinExt		INTEGER ::= 88
maxNrOfULTSs				INTEGER ::= 15
maxNrOfULTSLCRs				INTEGER ::= 6
maxNrOfUSCHs				INTEGER ::= 32
maxNrOfSlotFormatsPRACH		INTEGER ::= 8
maxCellinNodeB				INTEGER ::= 256
maxCCPinNodeB				INTEGER ::= 256
maxCTFC						INTEGER ::= 16777215
maxLocalCellinNodeB			INTEGER ::= maxCellinNodeB
maxFPACHCell				INTEGER ::= 8
maxRACHCell					INTEGER ::= maxPRACHCell
maxPLCCHCell				INTEGER ::= 16
maxPRACHCell				INTEGER ::= 16
maxSCCPCHCell				INTEGER ::= 32
maxSCCPCHCellinExt			INTEGER ::= 208	-- maxNrOfSCCPCHs + maxNrOfSCCPCHsinExt - maxSCCPCHCell
maxSCCPCHCellinExtLCR		INTEGER ::= 64	-- maxNrOfSCCPCHLCRs + maxNrOfSCCPCHsLCRinExt - maxSCCPCHCell
maxSCCPCHCell768			INTEGER ::= 480
maxSCPICHCell				INTEGER ::= 32
maxTTI-count				INTEGER ::= 4
maxIBSEG					INTEGER ::= 16
maxIB						INTEGER ::= 64
maxFACHCell 				INTEGER ::= 256	-- maxNrOfFACHs * maxSCCPCHCell
maxRateMatching				INTEGER ::= 256
maxHS-PDSCHCodeNrComp-1		INTEGER ::= 15
maxHS-SCCHCodeNrComp-1		INTEGER ::= 127
maxNrOfCellSyncBursts		INTEGER ::= 10
maxNrOfReceptsPerSyncFrame	INTEGER ::= 16
maxNrOfMeasNCell			INTEGER ::= 96
maxNrOfMeasNCell-1			INTEGER ::= 95	-- maxNrOfMeasNCell – 1
maxNrOfSF					INTEGER ::= 8
maxTGPS						INTEGER ::= 6
maxCommunicationContext		INTEGER ::= 1048575
maxNrOfLevels				INTEGER ::= 256
maxNoSat					INTEGER ::= 16
maxNoGPSItems				INTEGER ::= 8
maxNrOfHSSCCHs				INTEGER ::= 32
maxNrOfHSSICHs				INTEGER ::= 4
maxNrOfHSSICHs-1			INTEGER ::= 3
maxNrOfSyncFramesLCR		INTEGER ::= 512
maxNrOfReceptionsperSyncFrameLCR	INTEGER ::=	8
maxNrOfSyncDLCodesLCR		INTEGER ::= 32
maxNrOfHSSCCHCodes				INTEGER ::= 4
maxNrOfMACdFlows				INTEGER ::= 8
maxNrOfMACdFlows-1				INTEGER ::= 7	-- maxNrOfMACdFlows - 1
maxNrOfMACdPDUIndexes			INTEGER ::= 8
maxNrOfMACdPDUIndexes-1			INTEGER ::= 7	-- maxNoOfMACdPDUIndexes – 1
maxNrOfMACdPDUSize				INTEGER ::= 32
maxNrOfNIs						INTEGER ::= 256
maxNrOfPriorityQueues			INTEGER ::= 8
maxNrOfPriorityQueues-1			INTEGER ::= 7	-- maxNoOfPriorityQueues - 1
maxNrOfHARQProcesses			INTEGER ::= 8
maxNrOfContextsOnUeList			INTEGER ::= 16
maxNrOfCellPortionsPerCell		INTEGER ::= 64
maxNrOfCellPortionsPerCell-1	INTEGER ::= 63
maxNrOfPriorityClasses			INTEGER ::= 16
maxNrOfSatAlmanac-maxNoSat		INTEGER ::= 16  -- maxNrofSatAlmanac - maxNoSat
maxNrOfE-AGCHs					INTEGER ::= 32
maxNrOfEDCHMACdFlows			INTEGER ::= 8
maxNrOfEDCHMACdFlows-1			INTEGER ::= 7
maxNrOfE-RGCHs-E-HICHs			INTEGER ::= 32
maxNrOfEDCH-HARQ-PO-QUANTSTEPs	INTEGER ::= 6
maxNrOfEDCHHARQProcesses2msEDCH	INTEGER ::= 8
maxNrOfEDPCCH-PO-QUANTSTEPs		INTEGER ::= 8
maxNrOfBits-MACe-PDU-non-scheduled	INTEGER ::= 19982
maxNrOfRefETFCIs				INTEGER ::= 8
maxNrOfRefETFCI-PO-QUANTSTEPs	INTEGER ::= 29
maxNrofSigSeqRGHI-1				INTEGER ::= 39
maxNoOfLogicalChannels			INTEGER ::= 16 -- only maximum 15 can be used
maxNrOfCombEDPDCH				INTEGER ::= 12
maxE-RUCCHCell					INTEGER ::= 16
maxNrOfEAGCHCodes				INTEGER ::= 4
maxNrOfRefBetas					INTEGER ::= 8
maxNrOfE-PUCHSlots				INTEGER ::= 13
maxNrOfEAGCHs					INTEGER ::= 32
maxNrOfHS-DSCH-TBSs-HS-SCCHless	INTEGER ::= 4
maxNrOfHS-DSCH-TBSs				INTEGER ::= 90
maxNrOfEHICHCodes				INTEGER ::= 4
maxNrOfE-PUCHSlotsLCR			INTEGER ::= 5
maxNrOfEPUCHcodes				INTEGER ::= 16
maxNrOfEHICHs					INTEGER ::= 32
maxNrOfCommonMACFlows			INTEGER ::= 8
maxNrOfCommonMACFlows-1			INTEGER ::= 7
maxNrOfPagingMACFlow			INTEGER ::= 4 
maxNrOfPagingMACFlow-1			INTEGER ::= 3
maxNrOfcommonMACQueues			INTEGER ::= 8
maxNrOfpagingMACQueues			INTEGER ::= 8
maxNrOfHS-DSCHTBSsE-PCH			INTEGER ::= 2
maxGANSSSat						INTEGER ::= 64
maxNoGANSS						INTEGER ::= 8
maxSgnType						INTEGER ::= 8
maxFrequencyinCell				INTEGER ::= 12
maxFrequencyinCell-1			INTEGER ::= 11
maxHSDPAFrequency				INTEGER ::= 8
maxHSDPAFrequency-1				INTEGER ::= 7
maxNrOfHSSCCHsinExt				INTEGER ::= 224
maxGANSSSatAlmanac				INTEGER ::= 36
maxGANSSClockMod				INTEGER ::= 4
maxNrOfEDCHRLs					INTEGER ::= 4
maxERNTItoRelease				INTEGER ::= 256
maxNrOfCommonEDCH				INTEGER ::= 32
maxNrOfCommonHRNTI				INTEGER ::= 4
maxNrOfCommonMACFlowsLCR		INTEGER ::= 256
maxNrOfCommonMACFlowsLCR-1		INTEGER ::= 255
maxNrOfHSSCCHsLCR				INTEGER ::= 256
maxNrOfEDCHMACdFlowsLCR			INTEGER ::= 256
maxNrOfEDCHMACdFlowsLCR-1		INTEGER ::= 255
maxNrOfEAGCHsLCR				INTEGER ::= 256
maxNrOfEHICHsLCR				INTEGER ::= 256
maxnrofERUCCHsLCR				INTEGER ::= 32
maxNrOfHSDSCH-1					INTEGER ::= 32
maxNrOfHSDSCH					INTEGER ::= 33
maxGANSS-1						INTEGER ::= 7
maxNoOfTBSs-Mapping-HS-DSCH-SPS					INTEGER ::= 4
maxNoOfTBSs-Mapping-HS-DSCH-SPS-1				INTEGER ::= 3
maxNoOfHS-DSCH-TBSsLCR							INTEGER ::= 64
maxNoOfRepetition-Period-LCR					INTEGER ::= 4
maxNoOfRepetitionPeriod-SPS-LCR-1				INTEGER ::= 3
maxNoOf-HS-SICH-SPS								INTEGER ::= 4
maxNoOf-HS-SICH-SPS-1							INTEGER ::= 3
maxNoOfNon-HS-SCCH-Assosiated-HS-SICH			INTEGER ::= 4
maxNoOfNon-HS-SCCH-Assosiated-HS-SICH-Ext		INTEGER ::= 44
maxMBMSServiceSelect							INTEGER ::= 256
maxNrOfCellPortionsPerCellLCR					INTEGER ::= 256
maxNrOfCellPortionsPerCellLCR-1					INTEGER ::= 255
maxNrOfEDCH-1									INTEGER ::= 32
maxNoOfCommonH-RNTI								INTEGER ::= 256
maxNrOfCommonMACFlowsLCRExt						INTEGER ::= 248
-- maxNrOfCommonMACFlowsLCR-maxNrOfCommonMACFlows
maxofERNTI										INTEGER ::= 256
maxNrOfDCHMeasurementOccasionPatternSequence	INTEGER ::= 6
maxNrOfULCarriersLCR-1							INTEGER ::= 5
maxFreqBandsTDD									INTEGER ::= 16
maxnoofPRACHEUL									INTEGER ::= 16
maxIGPInfo										INTEGER ::= 320
maxNrofConcatenatedDCH							INTEGER ::= 3

-- **************************************************************
--
-- IEs
--
-- **************************************************************

id-AICH-Information													ProtocolIE-ID ::= 0
id-AICH-InformationItem-ResourceStatusInd							ProtocolIE-ID ::= 1
id-BCH-Information													ProtocolIE-ID ::= 7
id-BCH-InformationItem-ResourceStatusInd							ProtocolIE-ID ::= 8
id-BCCH-ModificationTime											ProtocolIE-ID ::= 9
id-BlockingPriorityIndicator										ProtocolIE-ID ::= 10
id-Cause															ProtocolIE-ID ::= 13
id-CCP-InformationItem-AuditRsp										ProtocolIE-ID ::= 14
id-CCP-InformationList-AuditRsp										ProtocolIE-ID ::= 15
id-CCP-InformationItem-ResourceStatusInd							ProtocolIE-ID ::= 16
id-Cell-InformationItem-AuditRsp									ProtocolIE-ID ::= 17
id-Cell-InformationItem-ResourceStatusInd							ProtocolIE-ID ::= 18
id-Cell-InformationList-AuditRsp									ProtocolIE-ID ::= 19
id-CellParameterID													ProtocolIE-ID ::= 23
id-CFN																ProtocolIE-ID ::= 24
id-C-ID																ProtocolIE-ID ::= 25
id-CommonMeasurementAccuracy										ProtocolIE-ID ::= 39
id-CommonMeasurementObjectType-CM-Rprt								ProtocolIE-ID ::= 31
id-CommonMeasurementObjectType-CM-Rqst								ProtocolIE-ID ::= 32
id-CommonMeasurementObjectType-CM-Rsp								ProtocolIE-ID ::= 33
id-CommonMeasurementType											ProtocolIE-ID ::= 34
id-CommonPhysicalChannelID											ProtocolIE-ID ::= 35
id-CommonPhysicalChannelType-CTCH-SetupRqstFDD						ProtocolIE-ID ::= 36
id-CommonPhysicalChannelType-CTCH-SetupRqstTDD						ProtocolIE-ID ::= 37
id-CommunicationControlPortID										ProtocolIE-ID ::= 40
id-ConfigurationGenerationID										ProtocolIE-ID ::= 43
id-CRNC-CommunicationContextID										ProtocolIE-ID ::= 44
id-CriticalityDiagnostics											ProtocolIE-ID ::= 45
id-DCHs-to-Add-FDD													ProtocolIE-ID ::= 48
id-DCH-AddList-RL-ReconfPrepTDD										ProtocolIE-ID ::= 49
id-DCHs-to-Add-TDD													ProtocolIE-ID ::= 50
id-DCH-DeleteList-RL-ReconfPrepFDD									ProtocolIE-ID ::= 52
id-DCH-DeleteList-RL-ReconfPrepTDD									ProtocolIE-ID ::= 53
id-DCH-DeleteList-RL-ReconfRqstFDD									ProtocolIE-ID ::= 54
id-DCH-DeleteList-RL-ReconfRqstTDD									ProtocolIE-ID ::= 55
id-DCH-FDD-Information												ProtocolIE-ID ::= 56
id-DCH-TDD-Information												ProtocolIE-ID ::= 57
id-DCH-InformationResponse											ProtocolIE-ID ::= 59
id-FDD-DCHs-to-Modify												ProtocolIE-ID ::= 62
id-TDD-DCHs-to-Modify												ProtocolIE-ID ::= 63
id-DCH-ModifyList-RL-ReconfRqstTDD									ProtocolIE-ID ::= 65
id-DCH-RearrangeList-Bearer-RearrangeInd							ProtocolIE-ID ::= 135
id-DedicatedMeasurementObjectType-DM-Rprt							ProtocolIE-ID ::= 67
id-DedicatedMeasurementObjectType-DM-Rqst							ProtocolIE-ID ::= 68
id-DedicatedMeasurementObjectType-DM-Rsp							ProtocolIE-ID ::= 69
id-DedicatedMeasurementType											ProtocolIE-ID ::= 70
id-DL-CCTrCH-InformationItem-RL-SetupRqstTDD						ProtocolIE-ID ::= 72
id-DL-CCTrCH-InformationList-RL-AdditionRqstTDD						ProtocolIE-ID ::= 73
id-DL-CCTrCH-InformationList-RL-SetupRqstTDD						ProtocolIE-ID ::= 76
id-DL-DPCH-InformationItem-RL-AdditionRqstTDD						ProtocolIE-ID ::= 77
id-DL-DPCH-InformationList-RL-SetupRqstTDD							ProtocolIE-ID ::= 79
id-DL-DPCH-Information-RL-ReconfPrepFDD								ProtocolIE-ID ::= 81
id-DL-DPCH-Information-RL-ReconfRqstFDD								ProtocolIE-ID ::= 82
id-DL-DPCH-Information-RL-SetupRqstFDD								ProtocolIE-ID ::= 83
id-DL-DPCH-TimingAdjustment											ProtocolIE-ID ::= 21
id-DL-ReferencePowerInformationItem-DL-PC-Rqst						ProtocolIE-ID ::= 84
id-DLReferencePower													ProtocolIE-ID ::= 85
id-DLReferencePowerList-DL-PC-Rqst									ProtocolIE-ID ::= 86
id-Unused-ProtocolIE-ID-87											ProtocolIE-ID ::= 87
id-Unused-ProtocolIE-ID-89											ProtocolIE-ID ::= 89
id-Unused-ProtocolIE-ID-91											ProtocolIE-ID ::= 91
id-Unused-ProtocolIE-ID-93											ProtocolIE-ID ::= 93
id-DSCHs-to-Add-TDD													ProtocolIE-ID ::= 96
id-DSCH-Information-DeleteList-RL-ReconfPrepTDD						ProtocolIE-ID ::= 98
id-DSCH-Information-ModifyList-RL-ReconfPrepTDD						ProtocolIE-ID ::= 100
id-DSCH-InformationResponse											ProtocolIE-ID ::= 105
id-Unused-ProtocolIE-ID-106											ProtocolIE-ID ::= 106
id-DSCH-TDD-Information												ProtocolIE-ID ::= 107
id-Unused-ProtocolIE-ID-108											ProtocolIE-ID ::= 108
id-Unused-ProtocolIE-ID-112											ProtocolIE-ID ::= 112
id-DSCH-RearrangeList-Bearer-RearrangeInd							ProtocolIE-ID ::= 136
id-End-Of-Audit-Sequence-Indicator 									ProtocolIE-ID ::= 113
id-FACH-Information													ProtocolIE-ID ::= 116
id-FACH-InformationItem-ResourceStatusInd							ProtocolIE-ID ::= 117
id-FACH-ParametersList-CTCH-ReconfRqstTDD							ProtocolIE-ID ::= 120
id-FACH-ParametersListIE-CTCH-SetupRqstFDD							ProtocolIE-ID ::= 121
id-FACH-ParametersListIE-CTCH-SetupRqstTDD							ProtocolIE-ID ::= 122
id-IndicationType-ResourceStatusInd									ProtocolIE-ID ::= 123
id-Local-Cell-ID													ProtocolIE-ID ::= 124
id-Local-Cell-Group-InformationItem-AuditRsp						ProtocolIE-ID ::= 2
id-Local-Cell-Group-InformationItem-ResourceStatusInd				ProtocolIE-ID ::= 3
id-Local-Cell-Group-InformationItem2-ResourceStatusInd				ProtocolIE-ID ::= 4
id-Local-Cell-Group-InformationList-AuditRsp						ProtocolIE-ID ::= 5
id-Local-Cell-InformationItem-AuditRsp								ProtocolIE-ID ::= 125
id-Local-Cell-InformationItem-ResourceStatusInd						ProtocolIE-ID ::= 126
id-Local-Cell-InformationItem2-ResourceStatusInd					ProtocolIE-ID ::= 127
id-Local-Cell-InformationList-AuditRsp								ProtocolIE-ID ::= 128
id-AdjustmentPeriod													ProtocolIE-ID ::= 129
id-MaxAdjustmentStep												ProtocolIE-ID ::= 130
id-MaximumTransmissionPower											ProtocolIE-ID ::= 131
id-MeasurementFilterCoefficient										ProtocolIE-ID ::= 132
id-MeasurementID													ProtocolIE-ID ::= 133
id-MessageStructure													ProtocolIE-ID ::= 115
id-MIB-SB-SIB-InformationList-SystemInfoUpdateRqst					ProtocolIE-ID ::= 134
id-NodeB-CommunicationContextID										ProtocolIE-ID ::= 143
id-NeighbouringCellMeasurementInformation							ProtocolIE-ID ::= 455
id-P-CCPCH-Information												ProtocolIE-ID ::= 144
id-P-CCPCH-InformationItem-ResourceStatusInd						ProtocolIE-ID ::= 145
id-P-CPICH-Information												ProtocolIE-ID ::= 146
id-P-CPICH-InformationItem-ResourceStatusInd						ProtocolIE-ID ::= 147
id-P-SCH-Information												ProtocolIE-ID ::= 148
id-PCCPCH-Information-Cell-ReconfRqstTDD							ProtocolIE-ID ::= 150
id-PCCPCH-Information-Cell-SetupRqstTDD								ProtocolIE-ID ::= 151
id-PCH-Parameters-CTCH-ReconfRqstTDD								ProtocolIE-ID ::= 155
id-PCH-ParametersItem-CTCH-SetupRqstFDD								ProtocolIE-ID ::= 156
id-PCH-ParametersItem-CTCH-SetupRqstTDD								ProtocolIE-ID ::= 157
id-PCH-Information													ProtocolIE-ID ::= 158
id-PDSCH-Information-AddListIE-PSCH-ReconfRqst						ProtocolIE-ID ::= 161
id-PDSCH-Information-ModifyListIE-PSCH-ReconfRqst					ProtocolIE-ID ::= 162
id-PDSCHSets-AddList-PSCH-ReconfRqst								ProtocolIE-ID ::= 163
id-PDSCHSets-DeleteList-PSCH-ReconfRqst								ProtocolIE-ID ::= 164
id-PDSCHSets-ModifyList-PSCH-ReconfRqst								ProtocolIE-ID ::= 165
id-PICH-Information													ProtocolIE-ID ::= 166
id-PICH-Parameters-CTCH-ReconfRqstTDD								ProtocolIE-ID ::= 168
id-PowerAdjustmentType												ProtocolIE-ID ::= 169
id-PRACH-Information												ProtocolIE-ID ::= 170
id-PrimaryCCPCH-Information-Cell-ReconfRqstFDD						ProtocolIE-ID ::= 175
id-PrimaryCCPCH-Information-Cell-SetupRqstFDD						ProtocolIE-ID ::= 176
id-PrimaryCPICH-Information-Cell-ReconfRqstFDD						ProtocolIE-ID ::= 177
id-PrimaryCPICH-Information-Cell-SetupRqstFDD						ProtocolIE-ID ::= 178
id-PrimarySCH-Information-Cell-ReconfRqstFDD						ProtocolIE-ID ::= 179
id-PrimarySCH-Information-Cell-SetupRqstFDD							ProtocolIE-ID ::= 180
id-PrimaryScramblingCode											ProtocolIE-ID ::= 181
id-SCH-Information-Cell-ReconfRqstTDD								ProtocolIE-ID ::= 183
id-SCH-Information-Cell-SetupRqstTDD								ProtocolIE-ID ::= 184
id-PUSCH-Information-AddListIE-PSCH-ReconfRqst						ProtocolIE-ID ::= 185
id-PUSCH-Information-ModifyListIE-PSCH-ReconfRqst					ProtocolIE-ID ::= 186
id-PUSCHSets-AddList-PSCH-ReconfRqst								ProtocolIE-ID ::= 187
id-PUSCHSets-DeleteList-PSCH-ReconfRqst								ProtocolIE-ID ::= 188
id-PUSCHSets-ModifyList-PSCH-ReconfRqst								ProtocolIE-ID ::= 189
id-RACH-Information													ProtocolIE-ID ::= 190
id-RACH-ParametersItem-CTCH-SetupRqstFDD							ProtocolIE-ID ::= 196
id-RACH-ParameterItem-CTCH-SetupRqstTDD								ProtocolIE-ID ::= 197
id-ReportCharacteristics											ProtocolIE-ID ::= 198
id-Reporting-Object-RL-FailureInd									ProtocolIE-ID ::= 199
id-Reporting-Object-RL-RestoreInd									ProtocolIE-ID ::= 200
id-RL-InformationItem-DM-Rprt										ProtocolIE-ID ::= 202
id-RL-InformationItem-DM-Rqst										ProtocolIE-ID ::= 203
id-RL-InformationItem-DM-Rsp										ProtocolIE-ID ::= 204
id-RL-InformationItem-RL-AdditionRqstFDD							ProtocolIE-ID ::= 205
id-RL-informationItem-RL-DeletionRqst								ProtocolIE-ID ::= 206
id-RL-InformationItem-RL-FailureInd									ProtocolIE-ID ::= 207
id-RL-InformationItem-RL-PreemptRequiredInd							ProtocolIE-ID ::= 286
id-RL-InformationItem-RL-ReconfPrepFDD								ProtocolIE-ID ::= 208
id-RL-InformationItem-RL-ReconfRqstFDD								ProtocolIE-ID ::= 209
id-RL-InformationItem-RL-RestoreInd									ProtocolIE-ID ::= 210
id-RL-InformationItem-RL-SetupRqstFDD								ProtocolIE-ID ::= 211
id-RL-InformationList-RL-AdditionRqstFDD							ProtocolIE-ID ::= 212
id-RL-informationList-RL-DeletionRqst								ProtocolIE-ID ::= 213
id-RL-InformationList-RL-PreemptRequiredInd							ProtocolIE-ID ::= 237
id-RL-InformationList-RL-ReconfPrepFDD								ProtocolIE-ID ::= 214
id-RL-InformationList-RL-ReconfRqstFDD								ProtocolIE-ID ::= 215
id-RL-InformationList-RL-SetupRqstFDD								ProtocolIE-ID ::= 216
id-RL-InformationResponseItem-RL-AdditionRspFDD						ProtocolIE-ID ::= 217
id-RL-InformationResponseItem-RL-ReconfReady						ProtocolIE-ID ::= 218
id-RL-InformationResponseItem-RL-ReconfRsp							ProtocolIE-ID ::= 219
id-RL-InformationResponseItem-RL-SetupRspFDD						ProtocolIE-ID ::= 220
id-RL-InformationResponseList-RL-AdditionRspFDD						ProtocolIE-ID ::= 221
id-RL-InformationResponseList-RL-ReconfReady						ProtocolIE-ID ::= 222
id-RL-InformationResponseList-RL-ReconfRsp							ProtocolIE-ID ::= 223
id-RL-InformationResponseList-RL-SetupRspFDD						ProtocolIE-ID ::= 224
id-RL-InformationResponse-RL-AdditionRspTDD							ProtocolIE-ID ::= 225
id-RL-InformationResponse-RL-SetupRspTDD							ProtocolIE-ID ::= 226
id-RL-Information-RL-AdditionRqstTDD								ProtocolIE-ID ::= 227
id-RL-Information-RL-ReconfRqstTDD									ProtocolIE-ID ::= 228
id-RL-Information-RL-ReconfPrepTDD									ProtocolIE-ID ::= 229
id-RL-Information-RL-SetupRqstTDD									ProtocolIE-ID ::= 230
id-RL-ReconfigurationFailureItem-RL-ReconfFailure					ProtocolIE-ID ::= 236
id-RL-Set-InformationItem-DM-Rprt									ProtocolIE-ID ::= 238
id-RL-Set-InformationItem-DM-Rsp									ProtocolIE-ID ::= 240
id-RL-Set-InformationItem-RL-FailureInd								ProtocolIE-ID ::= 241
id-RL-Set-InformationItem-RL-RestoreInd								ProtocolIE-ID ::= 242
id-S-CCPCH-Information												ProtocolIE-ID ::= 247
id-S-CPICH-Information												ProtocolIE-ID ::= 249
id-SCH-Information													ProtocolIE-ID ::= 251
id-S-SCH-Information												ProtocolIE-ID ::= 253
id-Secondary-CCPCHListIE-CTCH-ReconfRqstTDD							ProtocolIE-ID ::= 257
id-Secondary-CCPCH-parameterListIE-CTCH-SetupRqstTDD				ProtocolIE-ID ::= 258
id-Secondary-CCPCH-Parameters-CTCH-ReconfRqstTDD					ProtocolIE-ID ::= 259
id-SecondaryCPICH-InformationItem-Cell-ReconfRqstFDD				ProtocolIE-ID ::= 260
id-SecondaryCPICH-InformationItem-Cell-SetupRqstFDD					ProtocolIE-ID ::= 261
id-SecondaryCPICH-InformationList-Cell-ReconfRqstFDD				ProtocolIE-ID ::= 262
id-SecondaryCPICH-InformationList-Cell-SetupRqstFDD					ProtocolIE-ID ::= 263
id-SecondarySCH-Information-Cell-ReconfRqstFDD						ProtocolIE-ID ::= 264
id-SecondarySCH-Information-Cell-SetupRqstFDD						ProtocolIE-ID ::= 265
id-SegmentInformationListIE-SystemInfoUpdate						ProtocolIE-ID ::= 266
id-SFN																ProtocolIE-ID ::= 268
id-SignallingBearerRequestIndicator									ProtocolIE-ID ::= 138
id-ShutdownTimer													ProtocolIE-ID ::= 269
id-Start-Of-Audit-Sequence-Indicator								ProtocolIE-ID ::= 114
id-Successful-RL-InformationRespItem-RL-AdditionFailureFDD			ProtocolIE-ID ::= 270
id-Successful-RL-InformationRespItem-RL-SetupFailureFDD				ProtocolIE-ID ::= 271
id-SyncCase															ProtocolIE-ID ::= 274
id-SyncCaseIndicatorItem-Cell-SetupRqstTDD-PSCH						ProtocolIE-ID ::= 275
id-T-Cell															ProtocolIE-ID ::= 276
id-TargetCommunicationControlPortID									ProtocolIE-ID ::= 139
id-TimeSlotConfigurationList-Cell-ReconfRqstTDD						ProtocolIE-ID ::= 277
id-TimeSlotConfigurationList-Cell-SetupRqstTDD						ProtocolIE-ID ::= 278
id-TransmissionDiversityApplied										ProtocolIE-ID ::= 279
id-TypeOfError														ProtocolIE-ID ::= 508
id-UARFCNforNt														ProtocolIE-ID ::= 280
id-UARFCNforNd														ProtocolIE-ID ::= 281
id-UARFCNforNu														ProtocolIE-ID ::= 282
id-UL-CCTrCH-InformationItem-RL-SetupRqstTDD						ProtocolIE-ID ::= 284
id-UL-CCTrCH-InformationList-RL-AdditionRqstTDD						ProtocolIE-ID ::= 285
id-UL-CCTrCH-InformationList-RL-SetupRqstTDD						ProtocolIE-ID ::= 288
id-UL-DPCH-InformationItem-RL-AdditionRqstTDD						ProtocolIE-ID ::= 289
id-UL-DPCH-InformationList-RL-SetupRqstTDD							ProtocolIE-ID ::= 291
id-UL-DPCH-Information-RL-ReconfPrepFDD								ProtocolIE-ID ::= 293
id-UL-DPCH-Information-RL-ReconfRqstFDD								ProtocolIE-ID ::= 294
id-UL-DPCH-Information-RL-SetupRqstFDD								ProtocolIE-ID ::= 295
id-Unsuccessful-RL-InformationRespItem-RL-AdditionFailureFDD		ProtocolIE-ID ::= 296
id-Unsuccessful-RL-InformationRespItem-RL-SetupFailureFDD			ProtocolIE-ID ::= 297
id-Unsuccessful-RL-InformationResp-RL-AdditionFailureTDD			ProtocolIE-ID ::= 300
id-Unsuccessful-RL-InformationResp-RL-SetupFailureTDD				ProtocolIE-ID ::= 301
id-USCH-Information-Add												ProtocolIE-ID ::= 302
id-USCH-Information-DeleteList-RL-ReconfPrepTDD						ProtocolIE-ID ::= 304
id-USCH-Information-ModifyList-RL-ReconfPrepTDD						ProtocolIE-ID ::= 306
id-USCH-InformationResponse											ProtocolIE-ID ::= 309
id-USCH-Information													ProtocolIE-ID ::= 310
id-USCH-RearrangeList-Bearer-RearrangeInd							ProtocolIE-ID ::= 141
id-Active-Pattern-Sequence-Information 								ProtocolIE-ID ::= 315
id-AICH-ParametersListIE-CTCH-ReconfRqstFDD							ProtocolIE-ID ::= 316
id-AdjustmentRatio													ProtocolIE-ID ::= 317
id-Not-Used-320														ProtocolIE-ID ::= 320
id-Not-Used-322														ProtocolIE-ID ::= 322
id-FACH-ParametersListIE-CTCH-ReconfRqstFDD							ProtocolIE-ID ::= 323
id-CauseLevel-PSCH-ReconfFailure									ProtocolIE-ID ::= 324
id-CauseLevel-RL-AdditionFailureFDD									ProtocolIE-ID ::= 325
id-CauseLevel-RL-AdditionFailureTDD									ProtocolIE-ID ::= 326
id-CauseLevel-RL-ReconfFailure										ProtocolIE-ID ::= 327
id-CauseLevel-RL-SetupFailureFDD									ProtocolIE-ID ::= 328
id-CauseLevel-RL-SetupFailureTDD									ProtocolIE-ID ::= 329
id-Not-Used-330														ProtocolIE-ID ::= 330
id-Not-Used-332														ProtocolIE-ID ::= 332
id-Closed-Loop-Timing-Adjustment-Mode								ProtocolIE-ID ::= 333
id-CommonPhysicalChannelType-CTCH-ReconfRqstFDD						ProtocolIE-ID ::= 334
id-Compressed-Mode-Deactivation-Flag								ProtocolIE-ID ::= 335
id-Not-Used-336														ProtocolIE-ID ::= 336
id-Not-Used-342														ProtocolIE-ID ::= 342
id-Not-Used-343														ProtocolIE-ID ::= 343
id-DL-CCTrCH-InformationAddList-RL-ReconfPrepTDD					ProtocolIE-ID ::= 346
id-DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD					ProtocolIE-ID ::= 347
id-DL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD					ProtocolIE-ID ::= 348
id-DL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD					ProtocolIE-ID ::= 349
id-DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD					ProtocolIE-ID ::= 350
id-DL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD					ProtocolIE-ID ::= 351
id-DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD					ProtocolIE-ID ::= 352
id-DL-DPCH-InformationAddListIE-RL-ReconfPrepTDD					ProtocolIE-ID ::= 353
id-DL-DPCH-InformationModify-AddListIE-RL-ReconfPrepTDD				ProtocolIE-ID ::= 355
id-DL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD			ProtocolIE-ID ::= 356
id-DL-DPCH-InformationModify-ModifyListIE-RL-ReconfPrepTDD			ProtocolIE-ID ::= 357
id-DL-TPC-Pattern01Count 											ProtocolIE-ID ::= 358
id-DPC-Mode															ProtocolIE-ID ::= 450
id-DPCHConstant														ProtocolIE-ID ::= 359
id-Unused-ProtocolIE-ID-94											ProtocolIE-ID ::= 94
id-Unused-ProtocolIE-ID-110											ProtocolIE-ID ::= 110
id-Unused-ProtocolIE-ID-111											ProtocolIE-ID ::= 111
id-FACH-ParametersList-CTCH-SetupRsp								ProtocolIE-ID ::= 362
id-Limited-power-increase-information-Cell-SetupRqstFDD				ProtocolIE-ID ::= 369
id-PCH-Parameters-CTCH-SetupRsp										ProtocolIE-ID ::= 374
id-PCH-ParametersItem-CTCH-ReconfRqstFDD							ProtocolIE-ID ::= 375
id-Not-Used-376														ProtocolIE-ID ::= 376
id-PICH-ParametersItem-CTCH-ReconfRqstFDD							ProtocolIE-ID ::= 380
id-PRACHConstant													ProtocolIE-ID ::= 381
id-PRACH-ParametersListIE-CTCH-ReconfRqstFDD						ProtocolIE-ID ::= 383
id-PUSCHConstant													ProtocolIE-ID ::= 384
id-RACH-Parameters-CTCH-SetupRsp									ProtocolIE-ID ::= 385
id-Unused-ProtocolIE-ID-443											ProtocolIE-ID ::= 443
id-Synchronisation-Configuration-Cell-ReconfRqst					ProtocolIE-ID ::= 393
id-Synchronisation-Configuration-Cell-SetupRqst						ProtocolIE-ID ::= 394
id-Transmission-Gap-Pattern-Sequence-Information					ProtocolIE-ID ::= 395
id-UL-CCTrCH-InformationAddList-RL-ReconfPrepTDD					ProtocolIE-ID ::= 396
id-UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD					ProtocolIE-ID ::= 397
id-UL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD					ProtocolIE-ID ::= 398
id-UL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD					ProtocolIE-ID ::= 399
id-UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD					ProtocolIE-ID ::= 400
id-UL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD					ProtocolIE-ID ::= 401
id-UL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD					ProtocolIE-ID ::= 402
id-UL-DPCH-InformationAddListIE-RL-ReconfPrepTDD					ProtocolIE-ID ::= 403
id-UL-DPCH-InformationModify-AddListIE-RL-ReconfPrepTDD				ProtocolIE-ID ::= 405
id-UL-DPCH-InformationModify-DeleteListIE-RL-ReconfPrepTDD			ProtocolIE-ID ::= 406
id-UL-DPCH-InformationModify-ModifyListIE-RL-ReconfPrepTDD			ProtocolIE-ID ::= 407
id-Unsuccessful-PDSCHSetItem-PSCH-ReconfFailureTDD					ProtocolIE-ID ::= 408
id-Unsuccessful-PUSCHSetItem-PSCH-ReconfFailureTDD					ProtocolIE-ID ::= 409
id-CommunicationContextInfoItem-Reset								ProtocolIE-ID ::= 412
id-CommunicationControlPortInfoItem-Reset							ProtocolIE-ID ::= 414
id-ResetIndicator													ProtocolIE-ID ::= 416
id-Unused-ProtocolIE-ID-417											ProtocolIE-ID ::= 417
id-Unused-ProtocolIE-ID-418											ProtocolIE-ID ::= 418
id-Unused-ProtocolIE-ID-419											ProtocolIE-ID ::= 419
id-Unused-ProtocolIE-ID-142											ProtocolIE-ID ::= 142
id-TimingAdvanceApplied												ProtocolIE-ID ::= 287
id-CFNReportingIndicator											ProtocolIE-ID ::= 6
id-SFNReportingIndicator											ProtocolIE-ID ::= 11
id-InnerLoopDLPCStatus												ProtocolIE-ID ::= 12
id-TimeslotISCPInfo													ProtocolIE-ID ::= 283
id-PICH-ParametersItem-CTCH-SetupRqstTDD							ProtocolIE-ID ::= 167
id-PRACH-ParametersItem-CTCH-SetupRqstTDD							ProtocolIE-ID ::= 20
id-CCTrCH-InformationItem-RL-FailureInd								ProtocolIE-ID ::= 46
id-CCTrCH-InformationItem-RL-RestoreInd								ProtocolIE-ID ::= 47
id-CauseLevel-SyncAdjustmntFailureTDD								ProtocolIE-ID ::= 420
id-CellAdjustmentInfo-SyncAdjustmntRqstTDD							ProtocolIE-ID ::= 421
id-CellAdjustmentInfoItem-SyncAdjustmentRqstTDD						ProtocolIE-ID ::= 494
id-CellSyncBurstInfoList-CellSyncReconfRqstTDD						ProtocolIE-ID ::= 482
id-CellSyncBurstTransInit-CellSyncInitiationRqstTDD					ProtocolIE-ID ::= 422
id-CellSyncBurstMeasureInit-CellSyncInitiationRqstTDD				ProtocolIE-ID ::= 423
id-CellSyncBurstTransReconfiguration-CellSyncReconfRqstTDD			ProtocolIE-ID ::= 424
id-CellSyncBurstMeasReconfiguration-CellSyncReconfRqstTDD			ProtocolIE-ID ::= 425
id-CellSyncBurstTransInfoList-CellSyncReconfRqstTDD					ProtocolIE-ID ::= 426
id-CellSyncBurstMeasInfoList-CellSyncReconfRqstTDD					ProtocolIE-ID ::= 427
id-CellSyncBurstTransReconfInfo-CellSyncReconfRqstTDD				ProtocolIE-ID ::= 428
id-CellSyncInfo-CellSyncReprtTDD									ProtocolIE-ID ::= 429
id-CSBTransmissionID												ProtocolIE-ID ::= 430
id-CSBMeasurementID													ProtocolIE-ID ::= 431
id-IntStdPhCellSyncInfoItem-CellSyncReprtTDD						ProtocolIE-ID ::= 432
id-NCyclesPerSFNperiod 												ProtocolIE-ID ::= 433
id-NRepetitionsPerCyclePeriod										ProtocolIE-ID ::= 434
id-SyncFrameNumber													ProtocolIE-ID ::= 437
id-SynchronisationReportType										ProtocolIE-ID ::= 438
id-SynchronisationReportCharacteristics								ProtocolIE-ID ::= 439
id-Unsuccessful-cell-InformationRespItem-SyncAdjustmntFailureTDD	ProtocolIE-ID ::= 440
id-LateEntranceCellSyncInfoItem-CellSyncReprtTDD					ProtocolIE-ID ::= 119
id-ReferenceClockAvailability										ProtocolIE-ID ::= 435
id-ReferenceSFNoffset												ProtocolIE-ID ::= 436
id-InformationExchangeID											ProtocolIE-ID ::= 444
id-InformationExchangeObjectType-InfEx-Rqst							ProtocolIE-ID ::= 445
id-InformationType													ProtocolIE-ID ::= 446
id-InformationReportCharacteristics									ProtocolIE-ID ::= 447
id-InformationExchangeObjectType-InfEx-Rsp							ProtocolIE-ID ::= 448
id-InformationExchangeObjectType-InfEx-Rprt							ProtocolIE-ID ::= 449
id-IPDLParameter-Information-Cell-ReconfRqstFDD						ProtocolIE-ID ::= 451
id-IPDLParameter-Information-Cell-SetupRqstFDD						ProtocolIE-ID ::= 452
id-IPDLParameter-Information-Cell-ReconfRqstTDD						ProtocolIE-ID ::= 453
id-IPDLParameter-Information-Cell-SetupRqstTDD						ProtocolIE-ID ::= 454
id-DL-DPCH-LCR-Information-RL-SetupRqstTDD							ProtocolIE-ID ::= 74
id-DwPCH-LCR-Information											ProtocolIE-ID ::= 78
id-DwPCH-LCR-InformationList-AuditRsp								ProtocolIE-ID ::= 90
id-DwPCH-LCR-Information-Cell-SetupRqstTDD							ProtocolIE-ID ::= 97
id-DwPCH-LCR-Information-Cell-ReconfRqstTDD							ProtocolIE-ID ::= 99
id-DwPCH-LCR-Information-ResourceStatusInd							ProtocolIE-ID ::= 101
id-maxFACH-Power-LCR-CTCH-SetupRqstTDD								ProtocolIE-ID ::= 154
id-maxFACH-Power-LCR-CTCH-ReconfRqstTDD								ProtocolIE-ID ::= 174
id-FPACH-LCR-Information											ProtocolIE-ID ::= 290
id-FPACH-LCR-Information-AuditRsp									ProtocolIE-ID ::= 292
id-FPACH-LCR-InformationList-AuditRsp								ProtocolIE-ID ::= 22
id-FPACH-LCR-InformationList-ResourceStatusInd						ProtocolIE-ID ::= 311
id-FPACH-LCR-Parameters-CTCH-SetupRqstTDD							ProtocolIE-ID ::= 312
id-FPACH-LCR-Parameters-CTCH-ReconfRqstTDD							ProtocolIE-ID ::= 314
id-PCCPCH-LCR-Information-Cell-SetupRqstTDD							ProtocolIE-ID ::= 456
id-PCH-Power-LCR-CTCH-SetupRqstTDD									ProtocolIE-ID ::= 457
id-PCH-Power-LCR-CTCH-ReconfRqstTDD									ProtocolIE-ID ::= 458
id-PICH-LCR-Parameters-CTCH-SetupRqstTDD							ProtocolIE-ID ::= 459
id-PRACH-LCR-ParametersList-CTCH-SetupRqstTDD						ProtocolIE-ID ::= 461
id-RL-InformationResponse-LCR-RL-SetupRspTDD						ProtocolIE-ID ::= 463
id-Secondary-CCPCH-LCR-parameterList-CTCH-SetupRqstTDD				ProtocolIE-ID ::= 465
id-TimeSlot															ProtocolIE-ID ::= 495
id-TimeSlotConfigurationList-LCR-Cell-ReconfRqstTDD					ProtocolIE-ID ::= 466
id-TimeSlotConfigurationList-LCR-Cell-SetupRqstTDD					ProtocolIE-ID ::= 467
id-TimeslotISCP-LCR-InfoList-RL-SetupRqstTDD						ProtocolIE-ID ::= 468
id-TimeSlotLCR-CM-Rqst												ProtocolIE-ID ::= 469
id-UL-DPCH-LCR-Information-RL-SetupRqstTDD							ProtocolIE-ID ::= 470
id-DL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD					ProtocolIE-ID ::= 472
id-UL-DPCH-InformationItem-LCR-RL-AdditionRqstTDD					ProtocolIE-ID ::= 473
id-TimeslotISCP-InformationList-LCR-RL-AdditionRqstTDD				ProtocolIE-ID ::= 474
id-DL-DPCH-LCR-InformationAddList-RL-ReconfPrepTDD					ProtocolIE-ID ::= 475
id-DL-DPCH-LCR-InformationModify-AddList-RL-ReconfPrepTDD			ProtocolIE-ID ::= 477
id-DL-Timeslot-LCR-InformationModify-ModifyList-RL-ReconfPrepTDD	ProtocolIE-ID ::= 479
id-TimeslotISCPInfoList-LCR-DL-PC-RqstTDD							ProtocolIE-ID ::= 480
id-UL-DPCH-LCR-InformationAddListIE-RL-ReconfPrepTDD				ProtocolIE-ID ::= 481
id-UL-DPCH-LCR-InformationModify-AddList							ProtocolIE-ID ::= 483
id-UL-TimeslotLCR-Information-RL-ReconfPrepTDD						ProtocolIE-ID ::= 485
id-UL-SIRTarget														ProtocolIE-ID ::= 510
id-PDSCH-AddInformation-LCR-PSCH-ReconfRqst							ProtocolIE-ID ::= 486
id-PDSCH-AddInformation-LCR-AddListIE-PSCH-ReconfRqst				ProtocolIE-ID ::= 487
id-Unused-ProtocolIE-ID-26											ProtocolIE-ID ::=  26
id-Unused-ProtocolIE-ID-27											ProtocolIE-ID ::=  27
id-PDSCH-ModifyInformation-LCR-PSCH-ReconfRqst						ProtocolIE-ID ::= 488
id-PDSCH-ModifyInformation-LCR-ModifyListIE-PSCH-ReconfRqst			ProtocolIE-ID ::= 489
id-PUSCH-AddInformation-LCR-PSCH-ReconfRqst							ProtocolIE-ID ::= 490
id-PUSCH-AddInformation-LCR-AddListIE-PSCH-ReconfRqst				ProtocolIE-ID ::= 491
id-PUSCH-ModifyInformation-LCR-PSCH-ReconfRqst						ProtocolIE-ID ::= 492
id-PUSCH-ModifyInformation-LCR-ModifyListIE-PSCH-ReconfRqst			ProtocolIE-ID ::= 493
id-timeslotInfo-CellSyncInitiationRqstTDD							ProtocolIE-ID ::= 496
id-SyncReportType-CellSyncReprtTDD									ProtocolIE-ID ::= 497
id-Power-Local-Cell-Group-InformationItem-AuditRsp					ProtocolIE-ID ::= 498
id-Power-Local-Cell-Group-InformationItem-ResourceStatusInd			ProtocolIE-ID ::= 499
id-Power-Local-Cell-Group-InformationItem2-ResourceStatusInd		ProtocolIE-ID ::= 500
id-Power-Local-Cell-Group-InformationList-AuditRsp					ProtocolIE-ID ::= 501
id-Power-Local-Cell-Group-InformationList-ResourceStatusInd			ProtocolIE-ID ::= 502
id-Power-Local-Cell-Group-InformationList2-ResourceStatusInd		ProtocolIE-ID ::= 503
id-Power-Local-Cell-Group-ID										ProtocolIE-ID ::= 504
id-PUSCH-Info-DM-Rqst												ProtocolIE-ID ::= 505
id-PUSCH-Info-DM-Rsp												ProtocolIE-ID ::= 506
id-PUSCH-Info-DM-Rprt												ProtocolIE-ID ::= 507
id-InitDL-Power														ProtocolIE-ID ::= 509
id-cellSyncBurstRepetitionPeriod									ProtocolIE-ID ::= 511
id-ReportCharacteristicsType-OnModification							ProtocolIE-ID ::= 512
id-SFNSFNMeasurementValueInformation								ProtocolIE-ID ::= 513
id-SFNSFNMeasurementThresholdInformation							ProtocolIE-ID ::= 514
id-TUTRANGPSMeasurementValueInformation								ProtocolIE-ID ::= 515
id-TUTRANGPSMeasurementThresholdInformation							ProtocolIE-ID ::= 516
id-Rx-Timing-Deviation-Value-LCR									ProtocolIE-ID ::= 520
id-RL-InformationResponse-LCR-RL-AdditionRspTDD						ProtocolIE-ID ::= 51
id-DL-PowerBalancing-Information									ProtocolIE-ID ::= 28
id-DL-PowerBalancing-ActivationIndicator							ProtocolIE-ID ::= 29
id-DL-PowerBalancing-UpdatedIndicator								ProtocolIE-ID ::= 30
id-CCTrCH-Initial-DL-Power-RL-SetupRqstTDD							ProtocolIE-ID ::= 517
id-CCTrCH-Initial-DL-Power-RL-AdditionRqstTDD						ProtocolIE-ID ::= 518
id-CCTrCH-Initial-DL-Power-RL-ReconfPrepTDD							ProtocolIE-ID ::= 519
id-IPDLParameter-Information-LCR-Cell-SetupRqstTDD					ProtocolIE-ID ::= 41
id-IPDLParameter-Information-LCR-Cell-ReconfRqstTDD					ProtocolIE-ID ::= 42
id-HS-PDSCH-HS-SCCH-E-AGCH-E-RGCH-E-HICH-MaxPower-PSCH-ReconfRqst	ProtocolIE-ID ::= 522
id-HS-PDSCH-HS-SCCH-ScramblingCode-PSCH-ReconfRqst					ProtocolIE-ID ::= 523
id-HS-PDSCH-FDD-Code-Information-PSCH-ReconfRqst					ProtocolIE-ID ::= 524
id-HS-SCCH-FDD-Code-Information-PSCH-ReconfRqst						ProtocolIE-ID ::= 525
id-HS-PDSCH-TDD-Information-PSCH-ReconfRqst							ProtocolIE-ID ::= 526
id-Add-To-HS-SCCH-Resource-Pool-PSCH-ReconfRqst						ProtocolIE-ID ::= 527
id-Modify-HS-SCCH-Resource-Pool-PSCH-ReconfRqst						ProtocolIE-ID ::= 528
id-Delete-From-HS-SCCH-Resource-Pool-PSCH-ReconfRqst				ProtocolIE-ID ::= 529
id-bindingID														ProtocolIE-ID ::= 102
id-RL-Specific-DCH-Info												ProtocolIE-ID ::= 103
id-transportlayeraddress 											ProtocolIE-ID ::= 104
id-DelayedActivation 												ProtocolIE-ID ::= 231
id-DelayedActivationList-RL-ActivationCmdFDD						ProtocolIE-ID ::= 232
id-DelayedActivationInformation-RL-ActivationCmdFDD					ProtocolIE-ID ::= 233
id-DelayedActivationList-RL-ActivationCmdTDD						ProtocolIE-ID ::= 234
id-DelayedActivationInformation-RL-ActivationCmdTDD					ProtocolIE-ID ::= 235
id-neighbouringTDDCellMeasurementInformationLCR						ProtocolIE-ID ::= 58
id-SYNCDlCodeId-TransInitLCR-CellSyncInitiationRqstTDD				ProtocolIE-ID ::= 543
id-SYNCDlCodeId-MeasureInitLCR-CellSyncInitiationRqstTDD			ProtocolIE-ID ::= 544
id-SYNCDlCodeIdTransReconfInfoLCR-CellSyncReconfRqstTDD				ProtocolIE-ID ::= 545
id-SYNCDlCodeIdMeasReconfigurationLCR-CellSyncReconfRqstTDD			ProtocolIE-ID ::= 546
id-SYNCDlCodeIdMeasInfoList-CellSyncReconfRqstTDD					ProtocolIE-ID ::= 547
id-SyncDLCodeIdsMeasInfoList-CellSyncReprtTDD						ProtocolIE-ID ::= 548
id-SyncDLCodeIdThreInfoLCR											ProtocolIE-ID ::= 549
id-NSubCyclesPerCyclePeriod-CellSyncReconfRqstTDD					ProtocolIE-ID ::= 550
id-DwPCH-Power														ProtocolIE-ID ::= 551
id-AccumulatedClockupdate-CellSyncReprtTDD							ProtocolIE-ID ::= 552
id-Angle-Of-Arrival-Value-LCR										ProtocolIE-ID ::= 521
id-HSDSCH-FDD-Information											ProtocolIE-ID ::= 530
id-HSDSCH-FDD-Information-Response									ProtocolIE-ID ::= 531
id-HSDSCH-Information-to-Modify										ProtocolIE-ID ::= 534
id-HSDSCH-RNTI														ProtocolIE-ID ::= 535
id-HSDSCH-TDD-Information											ProtocolIE-ID ::= 536
id-HSDSCH-TDD-Information-Response									ProtocolIE-ID ::= 537
id-HSPDSCH-RL-ID													ProtocolIE-ID ::= 541
id-PrimCCPCH-RSCP-DL-PC-RqstTDD										ProtocolIE-ID ::= 542
id-Unused-ProtocolIE-ID-64											ProtocolIE-ID ::= 64
id-PDSCH-RL-ID														ProtocolIE-ID ::= 66
id-HSDSCH-RearrangeList-Bearer-RearrangeInd							ProtocolIE-ID ::= 553
id-UL-Synchronisation-Parameters-LCR								ProtocolIE-ID ::= 554
id-HSDSCH-FDD-Update-Information									ProtocolIE-ID ::= 555
id-HSDSCH-TDD-Update-Information									ProtocolIE-ID ::= 556
id-DL-DPCH-TimeSlotFormat-LCR-ModifyItem-RL-ReconfPrepTDD			ProtocolIE-ID ::= 558
id-UL-DPCH-TimeSlotFormat-LCR-ModifyItem-RL-ReconfPrepTDD			ProtocolIE-ID ::= 559
id-TDD-TPC-UplinkStepSize-LCR-RL-SetupRqstTDD						ProtocolIE-ID ::= 560
id-TDD-TPC-UplinkStepSize-LCR-RL-AdditionRqstTDD					ProtocolIE-ID ::= 561
id-TDD-TPC-DownlinkStepSize-RL-AdditionRqstTDD						ProtocolIE-ID ::= 562
id-TDD-TPC-UplinkStepSize-InformationAdd-LCR-RL-ReconfPrepTDD		ProtocolIE-ID ::= 563
id-TDD-TPC-UplinkStepSize-InformationModify-LCR-RL-ReconfPrepTDD	ProtocolIE-ID ::= 564
id-TDD-TPC-DownlinkStepSize-InformationModify-RL-ReconfPrepTDD		ProtocolIE-ID ::= 565
id-TDD-TPC-DownlinkStepSize-InformationAdd-RL-ReconfPrepTDD			ProtocolIE-ID ::= 566
id-CCTrCH-Maximum-DL-Power-RL-SetupRqstTDD							ProtocolIE-ID ::= 567
id-CCTrCH-Minimum-DL-Power-RL-SetupRqstTDD							ProtocolIE-ID ::= 568
id-CCTrCH-Maximum-DL-Power-RL-AdditionRqstTDD						ProtocolIE-ID ::= 569
id-CCTrCH-Minimum-DL-Power-RL-AdditionRqstTDD						ProtocolIE-ID ::= 570
id-CCTrCH-Maximum-DL-Power-InformationAdd-RL-ReconfPrepTDD			ProtocolIE-ID ::= 571
id-CCTrCH-Minimum-DL-Power-InformationAdd-RL-ReconfPrepTDD			ProtocolIE-ID ::= 572
id-CCTrCH-Maximum-DL-Power-InformationModify-RL-ReconfPrepTDD		ProtocolIE-ID ::= 573
id-CCTrCH-Minimum-DL-Power-InformationModify-RL-ReconfPrepTDD		ProtocolIE-ID ::= 574
id-Maximum-DL-Power-Modify-LCR-InformationModify-RL-ReconfPrepTDD	ProtocolIE-ID ::= 575
id-Minimum-DL-Power-Modify-LCR-InformationModify-RL-ReconfPrepTDD	ProtocolIE-ID ::= 576
id-DL-DPCH-LCR-InformationModify-ModifyList-RL-ReconfRqstTDD		ProtocolIE-ID ::= 577
id-CCTrCH-Maximum-DL-Power-InformationModify-RL-ReconfRqstTDD		ProtocolIE-ID ::= 578
id-CCTrCH-Minimum-DL-Power-InformationModify-RL-ReconfRqstTDD		ProtocolIE-ID ::= 579
id-Initial-DL-Power-TimeslotLCR-InformationItem						ProtocolIE-ID ::= 580
id-Maximum-DL-Power-TimeslotLCR-InformationItem						ProtocolIE-ID ::= 581
id-Minimum-DL-Power-TimeslotLCR-InformationItem						ProtocolIE-ID ::= 582
id-HS-DSCHProvidedBitRateValueInformation							ProtocolIE-ID ::= 583
id-HS-DSCHRequiredPowerValueInformation								ProtocolIE-ID ::= 585
id-HS-DSCHRequiredPowerValue										ProtocolIE-ID ::= 586
id-TransmittedCarrierPowerOfAllCodesNotUsedForHSTransmission		ProtocolIE-ID ::= 587
id-HS-SICH-Reception-Quality 										ProtocolIE-ID ::= 588
id-HS-SICH-Reception-Quality-Measurement-Value 						ProtocolIE-ID ::= 589
id-HSSICH-Info-DM-Rprt 												ProtocolIE-ID ::= 590
id-HSSICH-Info-DM-Rqst												ProtocolIE-ID ::= 591
id-HSSICH-Info-DM-Rsp												ProtocolIE-ID ::= 592
id-Best-Cell-Portions-Value											ProtocolIE-ID ::= 593
id-Primary-CPICH-Usage-for-Channel-Estimation						ProtocolIE-ID ::= 594
id-Secondary-CPICH-Information-Change								ProtocolIE-ID ::= 595
id-NumberOfReportedCellPortions										ProtocolIE-ID ::= 596
id-CellPortion-InformationItem-Cell-SetupRqstFDD					ProtocolIE-ID ::= 597
id-CellPortion-InformationList-Cell-SetupRqstFDD					ProtocolIE-ID ::= 598
id-TimeslotISCP-LCR-InfoList-RL-ReconfPrepTDD						ProtocolIE-ID ::= 599
id-Secondary-CPICH-Information										ProtocolIE-ID ::= 600
id-Received-total-wide-band-power-For-CellPortion					ProtocolIE-ID ::= 601
id-Unidirectional-DCH-Indicator										ProtocolIE-ID ::= 602
id-TimingAdjustmentValueLCR											ProtocolIE-ID ::= 603
id-multipleRL-dl-DPCH-InformationList								ProtocolIE-ID ::= 604
id-multipleRL-dl-DPCH-InformationModifyList							ProtocolIE-ID ::= 605
id-multipleRL-ul-DPCH-InformationList								ProtocolIE-ID ::= 606
id-multipleRL-ul-DPCH-InformationModifyList							ProtocolIE-ID ::= 607
id-RL-ID															ProtocolIE-ID ::= 608
id-SAT-Info-Almanac-ExtItem											ProtocolIE-ID ::= 609
id-HSDPA-Capability													ProtocolIE-ID ::= 610
id-HSDSCH-Resources-Information-AuditRsp							ProtocolIE-ID ::= 611
id-HSDSCH-Resources-Information-ResourceStatusInd					ProtocolIE-ID ::= 612
id-HSDSCH-MACdFlows-to-Add											ProtocolIE-ID ::= 613
id-HSDSCH-MACdFlows-to-Delete										ProtocolIE-ID ::= 614
id-HSDSCH-Information-to-Modify-Unsynchronised						ProtocolIE-ID ::= 615
id-TnlQos															ProtocolIE-ID ::= 616
id-Received-total-wide-band-power-For-CellPortion-Value				ProtocolIE-ID ::= 617
id-Transmitted-Carrier-Power-For-CellPortion						ProtocolIE-ID ::= 618
id-Transmitted-Carrier-Power-For-CellPortion-Value 					ProtocolIE-ID ::= 619
id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmissionCellPortion	ProtocolIE-ID ::= 620
id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCH-E-RGCHOrE-HICHTransmissionCellPortionValue	ProtocolIE-ID ::= 621
id-UpPTSInterferenceValue											ProtocolIE-ID ::= 622
id-PrimaryCCPCH-RSCP-Delta											ProtocolIE-ID ::= 623
id-MeasurementRecoveryBehavior										ProtocolIE-ID ::= 624
id-MeasurementRecoveryReportingIndicator							ProtocolIE-ID ::= 625
id-MeasurementRecoverySupportIndicator								ProtocolIE-ID ::= 626
id-Tstd-indicator													ProtocolIE-ID ::= 627
id-multiple-RL-Information-RL-ReconfPrepTDD							ProtocolIE-ID ::= 628
id-multiple-RL-Information-RL-ReconfRqstTDD							ProtocolIE-ID ::= 629
id-DL-DPCH-Power-Information-RL-ReconfPrepFDD						ProtocolIE-ID ::= 630
id-F-DPCH-Information-RL-ReconfPrepFDD								ProtocolIE-ID ::= 631
id-F-DPCH-Information-RL-SetupRqstFDD								ProtocolIE-ID ::= 632
id-Additional-S-CCPCH-Parameters-CTCH-ReconfRqstTDD					ProtocolIE-ID ::= 633
id-Additional-S-CCPCH-Parameters-CTCH-SetupRqstTDD					ProtocolIE-ID ::= 634
id-Additional-S-CCPCH-LCR-Parameters-CTCH-ReconfRqstTDD				ProtocolIE-ID ::= 635
id-Additional-S-CCPCH-LCR-Parameters-CTCH-SetupRqstTDD				ProtocolIE-ID ::= 636
id-MICH-CFN															ProtocolIE-ID ::= 637
id-MICH-Information-AuditRsp										ProtocolIE-ID ::= 638
id-MICH-Information-ResourceStatusInd								ProtocolIE-ID ::= 639
id-MICH-Parameters-CTCH-ReconfRqstFDD								ProtocolIE-ID ::= 640
id-MICH-Parameters-CTCH-ReconfRqstTDD								ProtocolIE-ID ::= 641
id-MICH-Parameters-CTCH-SetupRqstFDD								ProtocolIE-ID ::= 642
id-MICH-Parameters-CTCH-SetupRqstTDD								ProtocolIE-ID ::= 643
id-Modification-Period												ProtocolIE-ID ::= 644
id-NI-Information-NotifUpdateCmd									ProtocolIE-ID ::= 645
id-S-CCPCH-InformationListExt-AuditRsp								ProtocolIE-ID ::= 646
id-S-CCPCH-InformationListExt-ResourceStatusInd						ProtocolIE-ID ::= 647
id-S-CCPCH-LCR-InformationListExt-AuditRsp							ProtocolIE-ID ::= 648
id-S-CCPCH-LCR-InformationListExt-ResourceStatusInd					ProtocolIE-ID ::= 649
id-HARQ-Preamble-Mode												ProtocolIE-ID ::= 650
id-Initial-DL-DPCH-TimingAdjustment									ProtocolIE-ID ::= 651
id-Initial-DL-DPCH-TimingAdjustment-Allowed							ProtocolIE-ID ::= 652
id-DLTransmissionBranchLoadValue									ProtocolIE-ID ::= 653
id-Power-Local-Cell-Group-choice-CM-Rqst							ProtocolIE-ID ::= 654
id-Power-Local-Cell-Group-choice-CM-Rsp								ProtocolIE-ID ::= 655
id-Power-Local-Cell-Group-choice-CM-Rprt							ProtocolIE-ID ::= 656
id-SynchronisationIndicator											ProtocolIE-ID ::= 657
id-HSDPA-And-EDCH-CellPortion-Information-PSCH-ReconfRqst			ProtocolIE-ID ::= 658
id-Unused-ProtocolIE-ID-659											ProtocolIE-ID ::= 659
id-HS-DSCHRequiredPowerValue-For-Cell-Portion						ProtocolIE-ID ::= 660
id-HS-DSCHRequiredPowerValueInformation-For-CellPortion				ProtocolIE-ID ::= 661
id-HS-DSCHProvidedBitRateValueInformation-For-CellPortion			ProtocolIE-ID ::= 662
id-E-AGCH-And-E-RGCH-E-HICH-FDD-Scrambling-Code						ProtocolIE-ID ::= 663
id-E-AGCH-FDD-Code-Information										ProtocolIE-ID ::= 664
id-E-DCH-Capability													ProtocolIE-ID ::= 665
id-E-DCH-FDD-DL-Control-Channel-Information							ProtocolIE-ID ::= 666
id-E-DCH-FDD-Information											ProtocolIE-ID ::= 667
id-E-DCH-FDD-Information-Response									ProtocolIE-ID ::= 668
id-E-DCH-FDD-Information-to-Modify									ProtocolIE-ID ::= 669
id-E-DCH-MACdFlows-to-Add											ProtocolIE-ID ::= 670
id-E-DCH-MACdFlows-to-Delete										ProtocolIE-ID ::= 671
id-E-DCH-Resources-Information-AuditRsp								ProtocolIE-ID ::= 672
id-E-DCH-Resources-Information-ResourceStatusInd					ProtocolIE-ID ::= 673
id-E-DCH-RL-Indication												ProtocolIE-ID ::= 674
id-E-DCH-RL-Set-ID													ProtocolIE-ID ::= 675
id-E-DPCH-Information-RL-ReconfPrepFDD								ProtocolIE-ID ::= 676
id-E-DPCH-Information-RL-SetupRqstFDD								ProtocolIE-ID ::= 677
id-E-RGCH-E-HICH-FDD-Code-Information								ProtocolIE-ID ::= 678
id-Serving-E-DCH-RL-ID												ProtocolIE-ID ::= 679
id-UL-DPDCH-Indicator-For-E-DCH-Operation							ProtocolIE-ID ::= 680
id-FDD-S-CCPCH-FrameOffset-CTCH-SetupRqstFDD						ProtocolIE-ID ::= 681
id-E-DPCH-Information-RL-ReconfRqstFDD								ProtocolIE-ID ::= 682
id-Maximum-Target-ReceivedTotalWideBandPower						ProtocolIE-ID ::= 683
id-E-DCHProvidedBitRateValueInformation								ProtocolIE-ID ::= 684
id-HARQ-Preamble-Mode-Activation-Indicator							ProtocolIE-ID ::= 685
id-RL-Specific-E-DCH-Info											ProtocolIE-ID ::= 686
id-E-DCH-CapacityConsumptionLaw										ProtocolIE-ID ::= 687
id-multiple-DedicatedMeasurementValueList-TDD-DM-Rsp				ProtocolIE-ID ::= 688
id-multiple-DedicatedMeasurementValueList-LCR-TDD-DM-Rsp			ProtocolIE-ID ::= 689
id-E-DCH-RearrangeList-Bearer-RearrangeInd							ProtocolIE-ID ::= 690
id-Unused-ProtocolIE-ID-691											ProtocolIE-ID ::= 691
id-multipleRL-dl-CCTrCH-InformationModifyList-RL-ReconfRqstTDD		ProtocolIE-ID ::= 692
id-Target-NonServing-EDCH-To-Total-EDCH-Power-Ratio					ProtocolIE-ID ::= 693
id-CellPortion-InformationItem-Cell-ReconfRqstFDD					ProtocolIE-ID ::= 694
id-CellPortion-InformationList-Cell-ReconfRqstFDD					ProtocolIE-ID ::= 695
id-multiple-PUSCH-InfoList-DM-Rsp									ProtocolIE-ID ::= 696
id-multiple-PUSCH-InfoList-DM-Rprt									ProtocolIE-ID ::= 697
id-Reference-ReceivedTotalWideBandPower								ProtocolIE-ID ::= 698
id-E-DCH-Serving-Cell-Change-Info-Response							ProtocolIE-ID ::= 699
id-HS-DSCH-Serving-Cell-Change-Info									ProtocolIE-ID ::= 700
id-HS-DSCH-Serving-Cell-Change-Info-Response						ProtocolIE-ID ::= 701
id-Serving-Cell-Change-CFN											ProtocolIE-ID ::= 702
id-E-DCH-HARQ-Combining-Capability									ProtocolIE-ID ::= 703
id-E-DCH-TTI2ms-Capability											ProtocolIE-ID ::= 704
id-E-DCH-SF-Capability												ProtocolIE-ID ::= 705
id-E-DCH-FDD-Update-Information										ProtocolIE-ID ::= 706
id-F-DPCH-Capability												ProtocolIE-ID ::= 707
id-E-DCH-Non-serving-Relative-Grant-Down-CommandsValue				ProtocolIE-ID ::= 708
id-HSSICH-SIRTarget													ProtocolIE-ID ::= 709
id-multiple-HSSICHMeasurementValueList-TDD-DM-Rsp					ProtocolIE-ID ::= 710
id-PLCCH-Information-AuditRsp 										ProtocolIE-ID ::= 711
id-PLCCH-Information-ResourceStatusInd								ProtocolIE-ID ::= 712
id-PLCCH-Information-RL-ReconfPrepTDDLCR							ProtocolIE-ID ::= 713
id-PLCCH-Information-UL-TimeslotLCR-Info							ProtocolIE-ID ::= 714
id-PLCCH-InformationList-AuditRsp									ProtocolIE-ID ::= 715
id-PLCCH-InformationList-ResourceStatusInd							ProtocolIE-ID ::= 716
id-PLCCH-Parameters-CTCH-ReconfRqstTDD								ProtocolIE-ID ::= 717
id-S-CCPCH-768-Parameters-CTCH-SetupRqstTDD							ProtocolIE-ID ::= 718
id-PICH-768-Parameters-CTCH-SetupRqstTDD							ProtocolIE-ID ::= 719
id-PRACH-768-Parameters-CTCH-SetupRqstTDD							ProtocolIE-ID ::= 720
id-S-CCPCH-768-Parameters-CTCH-ReconfRqstTDD						ProtocolIE-ID ::= 721
id-PICH-768-Parameters-CTCH-ReconfRqstTDD							ProtocolIE-ID ::= 722
id-MICH-768-Parameters-CTCH-ReconfRqstTDD							ProtocolIE-ID ::= 723
id-CommonPhysicalChannelID768-CommonTrChDeletionReq					ProtocolIE-ID ::= 724
id-S-CCPCH-768-InformationList-AuditRsp								ProtocolIE-ID ::= 725
id-S-CCPCH-768-Information-AuditRsp									ProtocolIE-ID ::= 726
id-neighbouringTDDCellMeasurementInformation768						ProtocolIE-ID ::= 727
id-PCCPCH-768-Information-Cell-SetupRqstTDD							ProtocolIE-ID ::= 728
id-SCH-768-Information-Cell-SetupRqstTDD							ProtocolIE-ID ::= 729
id-SCH-768-Information-Cell-ReconfRqstTDD							ProtocolIE-ID ::= 730
id-PCCPCH-768-Information-Cell-ReconfRqstTDD 						ProtocolIE-ID ::= 731
id-P-CCPCH-768-Information-AuditRsp									ProtocolIE-ID ::= 732
id-PICH-768-Information-AuditRsp									ProtocolIE-ID ::= 733
id-PRACH-768-InformationList-AuditRsp								ProtocolIE-ID ::= 734
id-SCH-768-Information-AuditRsp										ProtocolIE-ID ::= 735
id-MICH-768-Information-AuditRsp									ProtocolIE-ID ::= 736
id-PRACH-768-Information											ProtocolIE-ID ::= 737
id-S-CCPCH-768-Information-ResourceStatusInd						ProtocolIE-ID ::= 738
id-P-CCPCH-768-Information-ResourceStatusInd						ProtocolIE-ID ::= 739
id-PICH-768-Information-ResourceStatusInd							ProtocolIE-ID ::= 740
id-PRACH-768-InformationList-ResourceStatusInd						ProtocolIE-ID ::= 741
id-SCH-768-Information-ResourceStatusInd							ProtocolIE-ID ::= 742
id-MICH-768-Information-ResourceStatusInd							ProtocolIE-ID ::= 743
id-S-CCPCH-768-InformationList-ResourceStatusInd					ProtocolIE-ID ::= 744
id-UL-DPCH-768-Information-RL-SetupRqstTDD							ProtocolIE-ID ::= 745
id-DL-DPCH-768-Information-RL-SetupRqstTDD							ProtocolIE-ID ::= 746
id-DL-DPCH-InformationItem-768-RL-AdditionRqstTDD					ProtocolIE-ID ::= 747
id-UL-DPCH-InformationItem-768-RL-AdditionRqstTDD					ProtocolIE-ID ::= 748
id-UL-DPCH-768-InformationAddItemIE-RL-ReconfPrepTDD				ProtocolIE-ID ::= 749
id-UL-DPCH-768-InformationAddListIE-RL-ReconfPrepTDD				ProtocolIE-ID ::= 750
id-UL-DPCH-768-InformationModify-AddItem							ProtocolIE-ID ::= 751
id-UL-DPCH-768-InformationModify-AddList							ProtocolIE-ID ::= 752
id-UL-Timeslot768-Information-RL-ReconfPrepTDD						ProtocolIE-ID ::= 753
id-DL-DPCH-768-InformationAddItem-RL-ReconfPrepTDD					ProtocolIE-ID ::= 754
id-DL-DPCH-768-InformationAddList-RL-ReconfPrepTDD					ProtocolIE-ID ::= 755
id-DL-DPCH-768-InformationModify-AddItem-RL-ReconfPrepTDD			ProtocolIE-ID ::= 756
id-DL-DPCH-768-InformationModify-AddList-RL-ReconfPrepTDD			ProtocolIE-ID ::= 757
id-DL-Timeslot-768-InformationModify-ModifyList-RL-ReconfPrepTDD	ProtocolIE-ID ::= 758
id-DPCH-ID768-DM-Rqst												ProtocolIE-ID ::= 759
id-multiple-DedicatedMeasurementValueList-768-TDD-DM-Rsp			ProtocolIE-ID ::= 760
id-DPCH-ID768-DM-Rsp												ProtocolIE-ID ::= 761
id-Rx-Timing-Deviation-Value-768									ProtocolIE-ID ::= 762
id-DPCH-ID768-DM-Rprt												ProtocolIE-ID ::= 763
id-PDSCH-AddInformation-768-PSCH-ReconfRqst							ProtocolIE-ID ::= 764
id-PDSCH-ModifyInformation-768-PSCH-ReconfRqst						ProtocolIE-ID ::= 765
id-PUSCH-AddInformation-768-PSCH-ReconfRqst							ProtocolIE-ID ::= 766
id-PUSCH-ModifyInformation-768-PSCH-ReconfRqst						ProtocolIE-ID ::= 767
id-dL-HS-PDSCH-Timeslot-Information-768-PSCH-ReconfRqst				ProtocolIE-ID ::= 768
id-hS-SCCH-Information-768-PSCH-ReconfRqst							ProtocolIE-ID ::= 769
id-hS-SCCH-InformationModify-768-PSCH-ReconfRqst					ProtocolIE-ID ::= 770
id-hsSCCH-Specific-Information-ResponseTDD768						ProtocolIE-ID ::= 771
id-E-DPCH-Information-RL-AdditionReqFDD								ProtocolIE-ID ::= 772
id-PDSCH-Timeslot-Format-PSCH-ReconfRqst-LCR						ProtocolIE-ID ::= 775
id-PUSCH-Timeslot-Format-PSCH-ReconfRqst-LCR						ProtocolIE-ID ::= 780
id-E-DCH-PowerOffset-for-SchedulingInfo								ProtocolIE-ID ::= 782
id-HSDSCH-Configured-Indicator										ProtocolIE-ID ::= 783
id-Rx-Timing-Deviation-Value-384-ext								ProtocolIE-ID ::= 786
id-RTWP-ReportingIndicator											ProtocolIE-ID ::= 787
id-RTWP-CellPortion-ReportingIndicator								ProtocolIE-ID ::= 788
id-Received-Scheduled-EDCH-Power-Share-Value						ProtocolIE-ID ::= 789
id-Received-Scheduled-EDCH-Power-Share-For-CellPortion-Value		ProtocolIE-ID ::= 790
id-Received-Scheduled-EDCH-Power-Share								ProtocolIE-ID ::= 791
id-Received-Scheduled-EDCH-Power-Share-For-CellPortion				ProtocolIE-ID ::= 792
id-tFCI-Presence													ProtocolIE-ID ::= 793
id-HSSICH-TPC-StepSize												ProtocolIE-ID ::= 794
id-E-RUCCH-InformationList-AuditRsp									ProtocolIE-ID ::= 795
id-E-RUCCH-InformationList-ResourceStatusInd						ProtocolIE-ID ::= 796
id-E-DCH-TDD-CapacityConsumptionLaw									ProtocolIE-ID ::= 797
id-E-RUCCH-Information												ProtocolIE-ID ::= 798
id-E-DCH-Information												ProtocolIE-ID ::= 799
id-E-DCH-Information-Response										ProtocolIE-ID ::= 800
id-E-DCH-Information-Reconfig										ProtocolIE-ID ::= 801
id-E-PUCH-Information-PSCH-ReconfRqst								ProtocolIE-ID ::= 802
id-Add-To-E-AGCH-Resource-Pool-PSCH-ReconfRqst						ProtocolIE-ID ::= 803
id-Modify-E-AGCH-Resource-Pool-PSCH-ReconfRqst						ProtocolIE-ID ::= 804
id-Delete-From-E-AGCH-Resource-Pool-PSCH-ReconfRqst					ProtocolIE-ID ::= 805
id-E-HICH-Information-PSCH-ReconfRqst								ProtocolIE-ID ::= 806
id-E-HICH-TimeOffset												ProtocolIE-ID ::= 807
id-Maximum-Generated-ReceivedTotalWideBandPowerInOtherCells			ProtocolIE-ID ::= 808
id-E-DCH-Serving-RL-ID 												ProtocolIE-ID ::= 809
id-E-RUCCH-768-InformationList-AuditRsp								ProtocolIE-ID ::= 810
id-E-RUCCH-768-InformationList-ResourceStatusInd					ProtocolIE-ID ::= 811
id-E-RUCCH-768-Information											ProtocolIE-ID ::= 812
id-E-DCH-768-Information											ProtocolIE-ID ::= 813
id-E-DCH-768-Information-Reconfig									ProtocolIE-ID ::= 814
id-E-PUCH-Information-768-PSCH-ReconfRqst							ProtocolIE-ID ::= 815
id-Add-To-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst					ProtocolIE-ID ::= 816
id-Modify-E-AGCH-Resource-Pool-768-PSCH-ReconfRqst					ProtocolIE-ID ::= 817
id-E-HICH-Information-768-PSCH-ReconfRqst							ProtocolIE-ID ::= 818
id-ExtendedPropagationDelay											ProtocolIE-ID ::= 819
id-Extended-Round-Trip-Time-Value									ProtocolIE-ID ::= 820
id-AlternativeFormatReportingIndicator								ProtocolIE-ID ::= 821
id-DCH-Indicator-For-E-DCH-HSDPA-Operation							ProtocolIE-ID ::= 822
id-Reference-ReceivedTotalWideBandPowerReporting					ProtocolIE-ID ::= 823
id-Reference-ReceivedTotalWideBandPowerSupportIndicator				ProtocolIE-ID ::= 824
id-ueCapability-Info												ProtocolIE-ID ::= 825
id-MAChs-ResetIndicator												ProtocolIE-ID ::= 826
id-Fast-Reconfiguration-Mode										ProtocolIE-ID ::= 827
id-Fast-Reconfiguration-Permission									ProtocolIE-ID ::= 828
id-BroadcastReference												ProtocolIE-ID ::= 829
id-BroadcastCommonTransportBearerIndication							ProtocolIE-ID ::= 830
id-ContinuousPacketConnectivityDTX-DRX-Capability					ProtocolIE-ID ::= 831
id-ContinuousPacketConnectivityDTX-DRX-Information					ProtocolIE-ID ::= 832
id-ContinuousPacketConnectivityHS-SCCH-less-Capability				ProtocolIE-ID ::= 833
id-ContinuousPacketConnectivityHS-SCCH-less-Information				ProtocolIE-ID ::= 834
id-ContinuousPacketConnectivityHS-SCCH-less-Information-Response	ProtocolIE-ID ::= 835
id-CPC-Information													ProtocolIE-ID ::= 836
id-MIMO-Capability													ProtocolIE-ID ::= 837
id-MIMO-PilotConfiguration											ProtocolIE-ID ::= 838
id-MBSFN-Cell-ParameterID-Cell-SetupRqstTDD							ProtocolIE-ID ::= 841
id-MBSFN-Cell-ParameterID-Cell-ReconfRqstTDD						ProtocolIE-ID ::= 842
id-S-CCPCH-Modulation												ProtocolIE-ID ::= 843
id-HS-PDSCH-Code-Change-Grant										ProtocolIE-ID ::= 844
id-HS-PDSCH-Code-Change-Indicator									ProtocolIE-ID ::= 845
id-SYNC-UL-Partition-LCR											ProtocolIE-ID ::= 846
id-E-DCH-LCR-Information											ProtocolIE-ID ::= 847
id-E-DCH-LCR-Information-Reconfig									ProtocolIE-ID ::= 848
id-E-PUCH-Information-LCR-PSCH-ReconfRqst							ProtocolIE-ID ::= 852
id-Add-To-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst					ProtocolIE-ID ::= 853
id-Modify-E-AGCH-Resource-Pool-LCR-PSCH-ReconfRqst					ProtocolIE-ID ::= 854
id-Add-To-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst					ProtocolIE-ID ::= 855
id-Modify-E-HICH-Resource-Pool-LCR-PSCH-ReconfRqst					ProtocolIE-ID ::= 856
id-Delete-From-E-HICH-Resource-Pool-PSCH-ReconfRqst					ProtocolIE-ID ::= 857
id-E-HICH-TimeOffsetLCR												ProtocolIE-ID ::= 858
id-SixtyfourQAM-DL-Capability										ProtocolIE-ID ::= 860
id-SixteenQAM-UL-Capability											ProtocolIE-ID ::= 861
id-HSDSCH-MACdPDU-SizeCapability									ProtocolIE-ID ::= 864
id-HSDSCH-MACdPDUSizeFormat											ProtocolIE-ID ::= 865
id-MaximumMACdPDU-SizeExtended										ProtocolIE-ID ::= 866
id-F-DPCH-SlotFormat												ProtocolIE-ID ::= 870
id-F-DPCH-SlotFormatCapability										ProtocolIE-ID ::= 871
id-LCRTDD-uplink-Physical-Channel-Capability						ProtocolIE-ID ::= 872
id-Extended-RNC-ID													ProtocolIE-ID ::= 873
id-Max-UE-DTX-Cycle													ProtocolIE-ID ::= 874
id-Secondary-CCPCH-SlotFormat-Extended								ProtocolIE-ID ::= 876
id-MBSFN-Only-Mode-Indicator-Cell-SetupRqstTDD-LCR					ProtocolIE-ID ::= 878
id-MBSFN-Only-Mode-Capability										ProtocolIE-ID ::= 879
id-Time-Slot-Parameter-ID											ProtocolIE-ID ::= 880
id-Additional-failed-HS-SICH										ProtocolIE-ID ::= 881
id-Additional-missed-HS-SICH										ProtocolIE-ID ::= 882
id-Additional-total-HS-SICH											ProtocolIE-ID ::= 883
id-Additional-HS-SICH-Reception-Quality-Measurement-Value			ProtocolIE-ID ::= 884
id-GANSS-Common-Data												ProtocolIE-ID ::= 887
id-GANSS-Information												ProtocolIE-ID ::= 888
id-GANSS-Generic-Data												ProtocolIE-ID ::= 889
id-TUTRANGANSSMeasurementThresholdInformation						ProtocolIE-ID ::= 890
id-TUTRANGANSSMeasurementValueInformation							ProtocolIE-ID ::= 891
id-ModulationPO-MBSFN												ProtocolIE-ID ::= 892
id-Enhanced-FACH-Capability											ProtocolIE-ID ::= 895
id-Enhanced-PCH-Capability											ProtocolIE-ID ::= 896
id-HSDSCH-Common-System-InformationFDD								ProtocolIE-ID ::= 897
id-HSDSCH-Common-System-Information-ResponseFDD						ProtocolIE-ID ::= 898
id-HSDSCH-Paging-System-InformationFDD								ProtocolIE-ID ::= 899
id-HSDSCH-Paging-System-Information-ResponseFDD						ProtocolIE-ID ::= 900
id-MBMS-Capability													ProtocolIE-ID ::= 901
id-Ext-Reference-E-TFCI-PO											ProtocolIE-ID ::= 902
id-Ext-Max-Bits-MACe-PDU-non-scheduled								ProtocolIE-ID ::= 903
id-HARQ-MemoryPartitioningInfoExtForMIMO							ProtocolIE-ID ::= 904
id-MIMO-ActivationIndicator											ProtocolIE-ID ::= 905
id-MIMO-Mode-Indicator												ProtocolIE-ID ::= 906
id-MIMO-N-M-Ratio													ProtocolIE-ID ::= 907
id-IPMulticastIndication											ProtocolIE-ID ::= 908
id-IPMulticastDataBearerIndication									ProtocolIE-ID ::= 909
id-TransportBearerNotSetupIndicator									ProtocolIE-ID ::= 910
id-TransportBearerNotRequestedIndicator								ProtocolIE-ID ::= 911
id-TimeSlotConfigurationList-LCR-CTCH-SetupRqstTDD					ProtocolIE-ID ::= 912
id-Cell-Frequency-List-Information-LCR-MulFreq-AuditRsp				ProtocolIE-ID ::= 913
id-Cell-Frequency-List-InformationItem-LCR-MulFreq-AuditRsp			ProtocolIE-ID ::= 914
id-Cell-Frequency-List-LCR-MulFreq-Cell-SetupRqstTDD				ProtocolIE-ID ::= 915
id-UARFCN-Adjustment												ProtocolIE-ID ::= 916
id-Cell-Frequency-List-Information-LCR-MulFreq-ResourceStatusInd	ProtocolIE-ID ::= 917
id-Cell-Frequency-List-InformationItem-LCR-MulFreq-ResourceStatusInd	ProtocolIE-ID ::= 918
id-UPPCHPositionLCR													ProtocolIE-ID ::= 919
id-UPPCH-LCR-Parameters-CTCH-ReconfRqstTDD							ProtocolIE-ID ::= 920
id-UPPCH-LCR-InformationList-AuditRsp								ProtocolIE-ID ::= 921
id-UPPCH-LCR-InformationItem-AuditRsp								ProtocolIE-ID ::= 922
id-UPPCH-LCR-InformationList-ResourceStatusInd						ProtocolIE-ID ::= 923
id-UPPCH-LCR-InformationItem-ResourceStatusInd						ProtocolIE-ID ::= 924
id-multipleFreq-dL-HS-PDSCH-Timeslot-Information-LCR-PSCH-ReconfRqst	ProtocolIE-ID ::= 925
id-number-Of-Supported-Carriers										ProtocolIE-ID ::= 926
id-multipleFreq-HSPDSCH-InformationList-ResponseTDDLCR				ProtocolIE-ID ::= 927
id-Unsuccessful-UARFCNItem-PSCH-ReconfFailureTDD					ProtocolIE-ID ::= 928
id-multipleFreq-HS-DSCH-Resources-InformationList-AuditRsp			ProtocolIE-ID ::= 929
id-multipleFreq-HS-DSCH-Resources-InformationList-ResourceStatusInd	ProtocolIE-ID ::= 930
id-UARFCNSpecificCauseList											ProtocolIE-ID ::= 931
id-tSN-Length														ProtocolIE-ID ::= 932
id-MultipleFreq-DL-HS-PDSCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst	ProtocolIE-ID ::= 933
id-multicarrier-number												ProtocolIE-ID ::= 934
id-Extended-HS-SCCH-ID												ProtocolIE-ID ::= 935
id-Extended-HS-SICH-ID												ProtocolIE-ID ::= 936
id-HSSICH-InfoExt-DM-Rqst											ProtocolIE-ID ::= 937
id-Delete-From-HS-SCCH-Resource-PoolExt-PSCH-ReconfRqst				ProtocolIE-ID ::= 938
id-HS-SCCH-InformationExt-LCR-PSCH-ReconfRqst						ProtocolIE-ID ::= 939
id-HS-SCCH-InformationModifyExt-LCR-PSCH-ReconfRqst					ProtocolIE-ID ::= 940
id-PowerControlGAP													ProtocolIE-ID ::= 941
id-MBSFN-SpecialTimeSlot-LCR										ProtocolIE-ID ::= 942
id-Common-MACFlows-to-DeleteFDD										ProtocolIE-ID ::= 943
id-Paging-MACFlows-to-DeleteFDD										ProtocolIE-ID ::= 944
id-E-TFCI-Boost-Information											ProtocolIE-ID ::= 945
id-SixteenQAM-UL-Operation-Indicator								ProtocolIE-ID ::= 946
id-SixtyfourQAM-UsageAllowedIndicator								ProtocolIE-ID ::= 947
id-SixtyfourQAM-DL-UsageIndicator									ProtocolIE-ID ::= 948
id-Default-Serving-Grant-in-DTX-Cycle2								ProtocolIE-ID ::= 949
id-Maximum-Target-ReceivedTotalWideBandPower-LCR					ProtocolIE-ID ::= 950
id-E-DPDCH-PowerInterpolation										ProtocolIE-ID ::= 951
id-Extended-E-DCH-LCRTDD-PhysicalLayerCategory						ProtocolIE-ID ::= 952
id-MultipleFreq-E-DCH-Resources-InformationList-AuditRsp			ProtocolIE-ID ::= 953
id-MultipleFreq-E-DCH-Resources-InformationList-ResourceStatusInd	ProtocolIE-ID ::= 954
id-MultipleFreq-E-PUCH-Timeslot-InformationList-LCR-PSCH-ReconfRqst	ProtocolIE-ID ::= 955
id-MultipleFreq-E-PUCH-Timeslot-Information-LCRItem-PSCH-ReconfRqst	ProtocolIE-ID ::= 956
id-Extended-E-HICH-ID-TDD											ProtocolIE-ID ::= 957
id-ContinuousPacketConnectivityHS-SCCH-less-Deactivate-Indicator	ProtocolIE-ID ::= 958
id-E-DCH-MACdPDU-SizeCapability										ProtocolIE-ID ::= 959
id-E-DCH-MACdPDUSizeFormat											ProtocolIE-ID ::= 960
id-MaximumNumber-Of-Retransmission-for-Scheduling-Info-LCRTDD		ProtocolIE-ID ::= 961
id-E-DCH-RetransmissionTimer-for-SchedulingInfo-LCRTDD				ProtocolIE-ID ::= 962
id-E-HICH-TimeOffset-Extension										ProtocolIE-ID ::= 963
id-MultipleFreq-E-HICH-TimeOffsetLCR								ProtocolIE-ID ::= 964
id-E-PUCH-PowerControlGAP											ProtocolIE-ID ::= 965
id-HSDSCH-TBSizeTableIndicator										ProtocolIE-ID ::= 966
id-E-DCH-DL-Control-Channel-Change-Information						ProtocolIE-ID ::= 967
id-E-DCH-DL-Control-Channel-Grant-Information						ProtocolIE-ID ::= 968
id-DGANSS-Corrections-Req											ProtocolIE-ID ::= 969
id-UE-with-enhanced-HS-SCCH-support-indicator						ProtocolIE-ID ::= 970
id-AdditionalTimeSlotListLCR										ProtocolIE-ID ::= 971
id-AdditionalMeasurementValueList									ProtocolIE-ID ::= 972
id-E-AGCH-Table-Choice					 							ProtocolIE-ID ::= 978
id-PLCCH-parameters													ProtocolIE-ID ::= 981
id-E-RUCCH-parameters												ProtocolIE-ID ::= 982
id-E-RUCCH-768-parameters											ProtocolIE-ID ::= 983
id-HS-Cause															ProtocolIE-ID ::= 984
id-E-Cause															ProtocolIE-ID ::= 985
id-Common-EDCH-Capability											ProtocolIE-ID ::= 987
id-E-AI-Capability													ProtocolIE-ID ::= 988
id-Common-EDCH-System-InformationFDD								ProtocolIE-ID ::= 989
id-Common-UL-MACFlows-to-DeleteFDD									ProtocolIE-ID ::= 990
id-Common-EDCH-MACdFlows-to-DeleteFDD								ProtocolIE-ID ::= 991
id-Common-EDCH-System-Information-ResponseFDD						ProtocolIE-ID ::= 992
id-Cell-ERNTI-Status-Information									ProtocolIE-ID ::= 993
id-Enhanced-UE-DRX-Capability										ProtocolIE-ID ::= 994
id-Enhanced-UE-DRX-InformationFDD									ProtocolIE-ID ::= 995
id-TransportBearerRequestIndicator									ProtocolIE-ID ::= 996
id-SixtyfourQAM-DL-MIMO-Combined-Capability							ProtocolIE-ID ::= 997
id-E-RNTI															ProtocolIE-ID ::= 998
id-MinimumReducedE-DPDCH-GainFactor									ProtocolIE-ID ::= 999
id-GANSS-Time-ID													ProtocolIE-ID ::= 1000
id-GANSS-AddIonoModelReq											ProtocolIE-ID ::= 1001
id-GANSS-EarthOrientParaReq											ProtocolIE-ID ::= 1002
id-GANSS-AddNavigationModelsReq										ProtocolIE-ID ::= 1003
id-GANSS-AddUTCModelsReq											ProtocolIE-ID ::= 1004
id-GANSS-AuxInfoReq													ProtocolIE-ID ::= 1005
id-GANSS-SBAS-ID													ProtocolIE-ID ::= 1006
id-GANSS-ID															ProtocolIE-ID ::= 1007
id-GANSS-Additional-Ionospheric-Model								ProtocolIE-ID ::= 1008
id-GANSS-Earth-Orientation-Parameters								ProtocolIE-ID ::= 1009
id-GANSS-Additional-Time-Models										ProtocolIE-ID ::= 1010
id-GANSS-Additional-Navigation-Models								ProtocolIE-ID ::= 1011
id-GANSS-Additional-UTC-Models										ProtocolIE-ID ::= 1012
id-GANSS-Auxiliary-Information										ProtocolIE-ID ::= 1013
id-ERACH-CM-Rqst													ProtocolIE-ID ::= 1014
id-ERACH-CM-Rsp														ProtocolIE-ID ::= 1015
id-ERACH-CM-Rprt													ProtocolIE-ID ::= 1016
id-EDCH-RACH-Report-Value											ProtocolIE-ID ::= 1017
id-EDCH-RACH-Report-IncrDecrThres									ProtocolIE-ID ::= 1018
id-EDCH-RACH-Report-ThresholdInformation							ProtocolIE-ID ::= 1019
id-E-DPCCH-Power-Boosting-Capability								ProtocolIE-ID ::= 1020
id-HSDSCH-Common-System-InformationLCR								ProtocolIE-ID ::= 1021
id-HSDSCH-Common-System-Information-ResponseLCR						ProtocolIE-ID ::= 1222
id-HSDSCH-Paging-System-InformationLCR								ProtocolIE-ID ::= 1023
id-HSDSCH-Paging-System-Information-ResponseLCR						ProtocolIE-ID ::= 1024
id-Common-MACFlows-to-DeleteLCR										ProtocolIE-ID ::= 1025
id-Paging-MACFlows-to-DeleteLCR										ProtocolIE-ID ::= 1026
id-Common-EDCH-System-InformationLCR								ProtocolIE-ID ::= 1027
id-Common-UL-MACFlows-to-DeleteLCR									ProtocolIE-ID ::= 1028
id-Common-EDCH-MACdFlows-to-DeleteLCR								ProtocolIE-ID ::= 1029
id-Common-EDCH-System-Information-ResponseLCR						ProtocolIE-ID ::= 1030
id-Enhanced-UE-DRX-CapabilityLCR									ProtocolIE-ID ::= 1031
id-Enhanced-UE-DRX-InformationLCR									ProtocolIE-ID ::= 1032
id-HSDSCH-PreconfigurationSetup										ProtocolIE-ID ::= 1033
id-HSDSCH-PreconfigurationInfo										ProtocolIE-ID ::= 1034
id-NoOfTargetCellHS-SCCH-Order										ProtocolIE-ID ::= 1035
id-EnhancedHSServingCC-Abort										ProtocolIE-ID ::= 1036
id-Additional-HS-Cell-Information-RL-Setup							ProtocolIE-ID ::= 1037
id-Additional-HS-Cell-Information-Response							ProtocolIE-ID ::= 1038
id-Additional-HS-Cell-Information-RL-Addition						ProtocolIE-ID ::= 1039
id-Additional-HS-Cell-Change-Information-Response					ProtocolIE-ID ::= 1040
id-Additional-HS-Cell-Information-RL-Reconf-Prep					ProtocolIE-ID ::= 1041
id-Additional-HS-Cell-Information-RL-Reconf-Req						ProtocolIE-ID ::= 1042
id-Additional-HS-Cell-Information-RL-Param-Upd						ProtocolIE-ID ::= 1043
id-Multi-Cell-Capability-Info										ProtocolIE-ID ::= 1044
id-IMB-Parameters													ProtocolIE-ID ::= 1045
id-MACes-Maximum-Bitrate-LCR										ProtocolIE-ID ::= 1046
id-Semi-PersistentScheduling-CapabilityLCR							ProtocolIE-ID ::= 1047
id-E-DCH-Semi-PersistentScheduling-Information-LCR					ProtocolIE-ID ::= 1048
id-HS-DSCH-Semi-PersistentScheduling-Information-LCR				ProtocolIE-ID ::= 1049
id-Add-To-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst	ProtocolIE-ID ::= 1050
id-Modify-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst	ProtocolIE-ID ::= 1051
id-Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst	ProtocolIE-ID ::= 1052
id-ContinuousPacketConnectivity-DRX-CapabilityLCR					ProtocolIE-ID ::= 1053
id-ContinuousPacketConnectivity-DRX-InformationLCR					ProtocolIE-ID ::= 1054
id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR			ProtocolIE-ID ::= 1055
id-CPC-InformationLCR												ProtocolIE-ID ::= 1056
id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR		ProtocolIE-ID ::= 1057
id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR			ProtocolIE-ID ::= 1058
id-E-AGCH-UE-Inactivity-Monitor-Threshold							ProtocolIE-ID ::= 1059
id-IdleIntervalInformation											ProtocolIE-ID ::= 1063
id-GANSS-alm-keplerianNAVAlmanac									ProtocolIE-ID ::= 1064
id-GANSS-alm-keplerianReducedAlmanac								ProtocolIE-ID ::= 1065
id-GANSS-alm-keplerianMidiAlmanac									ProtocolIE-ID ::= 1066
id-GANSS-alm-keplerianGLONASS										ProtocolIE-ID ::= 1067
id-GANSS-alm-ecefSBASAlmanac										ProtocolIE-ID ::= 1068
id-HSSICH-ReferenceSignal-InformationLCR							ProtocolIE-ID ::= 1070
id-MIMO-ReferenceSignal-InformationListLCR							ProtocolIE-ID ::= 1071
id-MIMO-SFMode-For-HSPDSCHDualStream								ProtocolIE-ID ::= 1072
id-MIMO-SFMode-Supported-For-HSPDSCHDualStream						ProtocolIE-ID ::= 1073
id-UE-Selected-MBMS-Service-Information								ProtocolIE-ID ::= 1074
id-MultiCarrier-HSDSCH-Physical-Layer-Category 						ProtocolIE-ID ::= 1077
id-Common-E-DCH-HSDPCCH-Capability									ProtocolIE-ID ::= 1078
id-DL-RLC-PDU-Size-Format											ProtocolIE-ID ::= 1079
id-HSSICH-ReferenceSignal-InformationModifyLCR						ProtocolIE-ID ::= 1080
id-schedulingPriorityIndicator										ProtocolIE-ID ::= 1081
id-TimeSlotMeasurementValueListLCR									ProtocolIE-ID ::= 1082
id-UE-SupportIndicatorExtension										ProtocolIE-ID ::= 1085
id-Single-Stream-MIMO-ActivationIndicator							ProtocolIE-ID ::= 1088
id-Single-Stream-MIMO-Capability									ProtocolIE-ID ::= 1089
id-Single-Stream-MIMO-Mode-Indicator								ProtocolIE-ID ::= 1090
id-Dual-Band-Capability-Info										ProtocolIE-ID ::= 1091
id-UE-AggregateMaximumBitRate										ProtocolIE-ID ::= 1092
id-UE-AggregateMaximumBitRate-Enforcement-Indicator					ProtocolIE-ID ::= 1093
id-MIMO-Power-Offset-For-S-CPICH-Capability							ProtocolIE-ID ::= 1101
id-MIMO-PilotConfigurationExtension									ProtocolIE-ID ::= 1102
id-TxDiversityOnDLControlChannelsByMIMOUECapability					ProtocolIE-ID ::= 1103
id-ULTimeslotISCPValue-For-CellPortion								ProtocolIE-ID ::= 1104
id-UpPTSInterferenceValue-For-CellPortion							ProtocolIE-ID ::= 1105
id-Best-Cell-Portions-ValueLCR										ProtocolIE-ID ::= 1106
id-Transmitted-Carrier-Power-For-CellPortion-ValueLCR				ProtocolIE-ID ::= 1107
id-Received-total-wide-band-power-For-CellPortion-ValueLCR			ProtocolIE-ID ::= 1108
id-UL-TimeslotISCP-For-CellPortion-Value							ProtocolIE-ID ::= 1109
id-HS-DSCHRequiredPowerValueInformation-For-CellPortionLCR			ProtocolIE-ID ::= 1110
id-HS-DSCHProvidedBitRateValueInformation-For-CellPortionLCR		ProtocolIE-ID ::= 1111
id-E-DCHProvidedBitRateValueInformation-For-CellPortion				ProtocolIE-ID ::= 1112
id-UpPTSInterference-For-CellPortion-Value							ProtocolIE-ID ::= 1113
id-NumberOfReportedCellPortionsLCR									ProtocolIE-ID ::= 1114
id-CellPortion-CapabilityLCR										ProtocolIE-ID ::= 1115
id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmissionCellPortionValue	ProtocolIE-ID ::= 1116
id-TransmittedCarrierPowerOfAllCodesNotUsedForHS-PDSCH-HS-SCCH-E-AGCHOrE-HICHTransmissionCellPortion		ProtocolIE-ID ::= 1117
id-ActivationInformation											ProtocolIE-ID ::= 1119
id-Additional-EDCH-Cell-Information-RL-Setup-Req					ProtocolIE-ID ::= 1120
id-Additional-EDCH-Cell-Information-Response						ProtocolIE-ID ::= 1121
id-Additional-EDCH-Cell-Information-RL-Add-Req						ProtocolIE-ID ::= 1122
id-Additional-EDCH-Cell-Information-Response-RL-Add					ProtocolIE-ID ::= 1123
id-Additional-EDCH-Cell-Information-RL-Reconf-Prep					ProtocolIE-ID ::= 1124
id-Additional-EDCH-Cell-Information-RL-Reconf-Req					ProtocolIE-ID ::= 1125
id-Additional-EDCH-Cell-Information-Bearer-Rearrangement			ProtocolIE-ID ::= 1126
id-Additional-EDCH-Cell-Information-RL-Param-Upd					ProtocolIE-ID ::= 1127
id-Additional-EDCH-Preconfiguration-Information						ProtocolIE-ID ::= 1128
id-EDCH-Indicator													ProtocolIE-ID ::= 1129
id-HS-DSCH-SPS-Reservation-Indicator								ProtocolIE-ID ::= 1131
id-E-DCH-SPS-Reservation-Indicator									ProtocolIE-ID ::= 1132
id-MultipleFreq-HARQ-MemoryPartitioning-InformationList				ProtocolIE-ID ::= 1133
id-Ul-common-E-DCH-MACflow-Specific-InfoResponseListLCR-Ext			ProtocolIE-ID ::= 1134
id-RepetitionPeriodIndex											ProtocolIE-ID ::= 1135
id-MidambleShiftLCR													ProtocolIE-ID ::= 1136
id-MaxHSDSCH-HSSCCH-Power-per-CELLPORTION							ProtocolIE-ID ::= 1137
id-DormantModeIndicator												ProtocolIE-ID ::= 1138
id-DiversityMode													ProtocolIE-ID ::= 1139
id-TransmitDiversityIndicator										ProtocolIE-ID ::= 1140
id-NonCellSpecificTxDiversity										ProtocolIE-ID ::= 1141
id-Cell-Capability-Container										ProtocolIE-ID ::= 1142
id-E-RNTI-List-Request												ProtocolIE-ID ::= 1143
id-E-RNTI-List														ProtocolIE-ID ::= 1144
id-PowerControlGAP-For-CellFACHLCR									ProtocolIE-ID ::= 1145
id-UL-Synchronisation-Parameters-For-FACHLCR						ProtocolIE-ID ::= 1147
id-HS-DSCH-SPS-Operation-Indicator									ProtocolIE-ID ::= 1148
id-HSDSCH-RNTI-For-FACH												ProtocolIE-ID ::= 1149
id-E-RNTI-For-FACH													ProtocolIE-ID ::= 1150
id-Out-of-Sychronization-Window										ProtocolIE-ID ::= 1151
id-Max-RTWP-perUARFCN-Information-LCR-PSCH-ReconfRqst				ProtocolIE-ID ::= 1152
id-E-HICH-TimeOffset-ReconfFailureTDD								ProtocolIE-ID ::= 1153
id-HSSCCH-TPC-StepSize												ProtocolIE-ID ::= 1154
id-TS0-CapabilityLCR												ProtocolIE-ID ::= 1155
id-UE-TS0-CapabilityLCR												ProtocolIE-ID ::= 1156
id-Common-System-Information-ResponseLCR							ProtocolIE-ID ::= 1157
id-Additional-EDCH-Cell-Information-ResponseRLReconf				ProtocolIE-ID ::= 1158
id-Multicell-EDCH-InformationItemIEs								ProtocolIE-ID ::= 1159
id-Multicell-EDCH-RL-Specific-InformationItemIEs					ProtocolIE-ID ::= 1160
id-Add-To-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext 	ProtocolIE-ID ::= 1161
id-Modify-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext	ProtocolIE-ID ::= 1162
id-Delete-From-Non-HS-SCCH-Associated-HS-SICH-Resource-Pool-LCR-PSCH-ReconfRqst-Ext	ProtocolIE-ID ::= 1163
id-Initial-DL-Transmission-Power									ProtocolIE-ID ::= 1164
id-Maximum-DL-Power													ProtocolIE-ID ::= 1165
id-Minimum-DL-Power													ProtocolIE-ID ::= 1166
id-DCH-MeasurementOccasion-Information								ProtocolIE-ID ::= 1167
id-AssociatedPhsicalChannelID										ProtocolIE-ID ::= 1168
id-DGNSS-ValidityPeriod												ProtocolIE-ID ::= 1169
id-PhysicalChannelID-for-CommonERNTI-RequestedIndicator				ProtocolIE-ID ::= 1170
id-PrecodingWeightSetRestriction									ProtocolIE-ID ::= 1171
id-Treset-Usage-Indicator											ProtocolIE-ID ::= 1172
id-Non-Serving-RL-Preconfig-Info									ProtocolIE-ID ::= 1173
id-Non-Serving-RL-Preconfig-Setup									ProtocolIE-ID ::= 1174
id-Non-Serving-RL-Preconfig-Removal									ProtocolIE-ID ::= 1175
id-Additional-E-DCH-Non-Serving-RL-Preconfiguration-Setup			ProtocolIE-ID ::= 1176
id-Additional-E-DCH-New-non-serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList	ProtocolIE-ID ::= 1177
id-Ul-common-E-DCH-MACflow-Specific-InfoListLCR-Ext					ProtocolIE-ID ::= 1178
id-CommonMACFlow-Specific-InfoList-ResponseLCR-Ext					ProtocolIE-ID ::= 1179
id-Enabling-Delay-Ext-LCR											ProtocolIE-ID ::= 1180
id-OrdinalNumberOfFrequency											ProtocolIE-ID ::= 1181
id-Multicell-EDCH-Restriction										ProtocolIE-ID ::= 1183
id-completeAlmanacProvided											ProtocolIE-ID ::= 1184
id-ganss-Delta-T													ProtocolIE-ID ::= 1185
id-Cell-Capability-Container-TDD-LCR								ProtocolIE-ID ::= 1186
id-Multi-Carrier-EDCH-Setup											ProtocolIE-ID ::= 1187
id-Multi-Carrier-EDCH-Reconfigure									ProtocolIE-ID ::= 1188
id-Multi-Carrier-EDCH-Response										ProtocolIE-ID ::= 1189
id-SNPL-Carrier-Group-Indicator										ProtocolIE-ID ::= 1190
id-MU-MIMO-Capability-ContainerLCR									ProtocolIE-ID ::= 1191
id-MU-MIMO-InformationLCR											ProtocolIE-ID ::= 1192
id-MU-MIMO-Information-Response										ProtocolIE-ID ::= 1193
id-MU-MIMO-Information-To-ReconfigureLCR							ProtocolIE-ID ::= 1194
id-HS-SCCH-Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext			ProtocolIE-ID ::= 1195
id-Adaptive-Special-Burst-Power-CapabilityLCR						ProtocolIE-ID ::= 1196
id-Usefulness-Of-Battery-Optimization								ProtocolIE-ID ::= 1197
id-Multi-Carrier-E-DCH-LCRTDD-PhysicalLayerCategory					ProtocolIE-ID ::= 1198
id-Common-HSDSCH-RNTI-List											ProtocolIE-ID ::= 1199
id-CommonEDCH-AdditionalTransmissionBackOff							ProtocolIE-ID ::= 1200
id-In-Sync-Information-LCR											ProtocolIE-ID ::= 1201
id-Puncturing-Handling-in-First-Rate-Matching-Stage					ProtocolIE-ID ::= 1202
id-ERNTI-Release-Status												ProtocolIE-ID ::= 1203
id-UE-Status-Update-Confirm-Indicator								ProtocolIE-ID ::= 1204
id-Max-RTWP-perCellPortion-InformationList-LCR-PSCH-ReconfRqst		ProtocolIE-ID ::= 1205
id-AOA-per-CELL-Portion-LCR											ProtocolIE-ID ::= 1206
id-UL-CLTD-Information												ProtocolIE-ID ::= 1208
id-UL-CLTD-Information-Reconf										ProtocolIE-ID ::= 1209
id-UL-CLTD-State-Update-Information									ProtocolIE-ID ::= 1211
id-Affected-HSDSCH-Serving-Cell-List								ProtocolIE-ID ::= 1212
id-Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order					ProtocolIE-ID ::= 1213
id-CPC-RecoveryReport												ProtocolIE-ID ::= 1214
id-FTPICH-Information												ProtocolIE-ID ::= 1215
id-FTPICH-Information-Reconf										ProtocolIE-ID ::= 1216
id-UE-RF-Band-CapabilityLCR											ProtocolIE-ID ::= 1217
id-E-AGCH-PowerOffset												ProtocolIE-ID ::= 1218
id-E-RGCH-PowerOffset												ProtocolIE-ID ::= 1219
id-E-HICH-PowerOffset												ProtocolIE-ID ::= 1220
id-UE-transmission-power-headroom									ProtocolIE-ID ::= 1225
id-MIMO-withfourtransmitantennas-ActivationIndicator				ProtocolIE-ID ::= 1226
id-MIMO-withfourtransmitantennas-Mode-Indicator						ProtocolIE-ID ::= 1227
id-MIMO-withfourtransmitantennas-PilotConfiguration					ProtocolIE-ID ::= 1228
id-DualStream-MIMO-withfourtransmitantennas-ActivationIndicator		ProtocolIE-ID ::= 1229
id-DualStream-MIMO-withfourtransmitantennas-Mode-Indicator			ProtocolIE-ID ::= 1230
id-UL-MIMO-Information												ProtocolIE-ID ::= 1231
id-UL-MIMO-Reconfiguration											ProtocolIE-ID ::= 1232
id-UL-MIMO-DL-Control-Channel-Information							ProtocolIE-ID ::= 1233
id-SixtyfourQAM-UL-Operation-Indicator								ProtocolIE-ID ::= 1234
id-Common-E-DCH-Implicit-Release-Timer								ProtocolIE-ID ::= 1236
id-Multiflow-Information											ProtocolIE-ID ::= 1237
id-Multiflow-Reconfiguration										ProtocolIE-ID ::= 1238
id-Multiflow-OrdinalNumberOfFrequency								ProtocolIE-ID ::= 1239
id-Concurrent-Deployment-of-2msand10ms-TTI							ProtocolIE-ID ::= 1240
id-Common-EDH-Preamble-Control-Information-extension-Type1			ProtocolIE-ID ::= 1241
id-Common-EDH-Preamble-Control-Information-extension-Type2			ProtocolIE-ID ::= 1242
id-Common-EDH-Preamble-Control-Information-extension-Type3			ProtocolIE-ID ::= 1243
id-NodeB-Triggered-HSDPCCH-Transmission-Information					ProtocolIE-ID ::= 1244
id-Per-HARQ-Activiation-and-Deactiviation							ProtocolIE-ID ::= 1245
id-Coffset															ProtocolIE-ID ::= 1246
id-Common-E-DCH-MAC-d-flow-info-Concurrent-TTI						ProtocolIE-ID ::= 1247
id-Serving-Grant-Value-for-Concurrent-Deployment-of-2msand10ms-TTI	ProtocolIE-ID ::= 1248
id-Two-ms-Grant-E-DCH-RACH-Resources								ProtocolIE-ID ::= 1249
id-Two-ms-Overridden-E-DCH-RACH-Resources							ProtocolIE-ID ::= 1250
id-Two-ms-Denied-E-DCH-RACH-Resources								ProtocolIE-ID ::= 1251
id-Further-Enhanced-UE-DRX-InformationFDD							ProtocolIE-ID ::= 1252
id-Common-E-RGCH-Operation-Indicator								ProtocolIE-ID ::= 1253
id-Common-E-RGCH-InfoFDD											ProtocolIE-ID ::= 1254
id-PrecoderWeightSetRestriction										ProtocolIE-ID ::= 1255
id-Non-rectangular-resource-allocation-indicator					ProtocolIE-ID ::= 1256
id-Non-rectangular-resource-timeslot-set							ProtocolIE-ID ::= 1257
id-UE-Support-of-non-rectangular-resource-allocation				ProtocolIE-ID ::= 1258
id-DBDS-CorrectionsReq												ProtocolIE-ID ::= 1267
id-DBDS-Corrections													ProtocolIE-ID ::= 1268
id-BDS-IonosphericGridModelReq										ProtocolIE-ID ::= 1269
id-BDS-Ionospheric-Grid-Model										ProtocolIE-ID ::= 1270
id-GANSS-alm-keplerianBDSAlmanac									ProtocolIE-ID ::= 1271
id-Assisting-RepetitionFactors										ProtocolIE-ID ::= 1276
id-UE-Measurement-Forwarding										ProtocolIE-ID ::= 1277
id-UPH-Filtering-Measurement-Forwarding-Request						ProtocolIE-ID ::= 1278
id-TTI-Update-Indicator												ProtocolIE-ID ::= 1279
id-CQI-Feedback-Cycle2												ProtocolIE-ID ::= 1280
id-CQI-Cycle-Switch-Timer											ProtocolIE-ID ::= 1281
id-UE-DRX-Cycle2													ProtocolIE-ID ::= 1282
id-Inactivity-Threshold-for-UE-DRX-Cycle2							ProtocolIE-ID ::= 1283
id-DTX-Information2													ProtocolIE-ID ::= 1284
id-BCH-Parameters													ProtocolIE-ID ::= 1286
id-BCH-Parameters-CTCH-SetupRsp										ProtocolIE-ID ::= 1287
id-BCH-Parameters-CTCH-ReconfRqstFDD								ProtocolIE-ID ::= 1288
id-BCH-mappedOnSCCPCH-Indication									ProtocolIE-ID ::= 1291
id-DCH-ENH-Information												ProtocolIE-ID ::= 1292
id-DCH-ENH-Information-Reconf										ProtocolIE-ID ::= 1293
id-Gainfactors-10ms-mode											ProtocolIE-ID ::= 1294
id-E-DCH-Decoupling-Indication										ProtocolIE-ID ::= 1295
id-Radio-Links-without-DPCH-FDPCH-Indication						ProtocolIE-ID ::= 1296
id-UL-DPCCH2-Information											ProtocolIE-ID ::= 1297
id-UL-DPCCH2-Information-Reconf										ProtocolIE-ID ::= 1298
id-ImplicitGrantHandling											ProtocolIE-ID ::= 1299
id-MinimumTEBSthreshold												ProtocolIE-ID ::= 1300
id-ActivationDelay													ProtocolIE-ID ::= 1301
id-Fast-TTI-switching-Mode-synchronized								ProtocolIE-ID ::= 1302
id-Fast-TTI-switching-Mode-unsynchronized							ProtocolIE-ID ::= 1303
id-Fast-TTI-switching-Mode-Supported								ProtocolIE-ID ::= 1304
id-Dual-Band-EDCH-Capability										ProtocolIE-ID ::= 1305
id-Improved-Synchronized-Indicator									ProtocolIE-ID ::= 1306
id-Downlink-TPC-enhancements-Information							ProtocolIE-ID ::= 1307
id-Downlink-TPC-enhancements-Reconf									ProtocolIE-ID ::= 1308
id-TPC-slot-position												ProtocolIE-ID ::= 1309
id-E-RNTI-Set														ProtocolIE-ID ::= 1310
id-DL-TBS															ProtocolIE-ID ::= 1311

END

9.3.7	Container Definitions
-- **************************************************************
--
-- Container definitions
--
-- **************************************************************

NBAP-Containers {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) 
umts-Access (20) modules (3) nbap (2) version1 (1) nbap-Containers (5) }

DEFINITIONS AUTOMATIC TAGS ::= 

BEGIN

-- **************************************************************
--
-- IE parameter types from other modules.
--
-- **************************************************************

IMPORTS
	maxProtocolExtensions,
	maxPrivateIEs,
	maxProtocolIEs,
	Criticality,
	Presence,
	PrivateIE-ID,
	ProtocolIE-ID
FROM NBAP-CommonDataTypes;

-- **************************************************************
--
-- Class Definition for Protocol IEs
--
-- **************************************************************

NBAP-PROTOCOL-IES ::= CLASS {
	&id		ProtocolIE-ID 			UNIQUE,
	&criticality	Criticality,
	&Value,
	&presence	Presence
}
WITH SYNTAX {
	ID		&id
	CRITICALITY	&criticality
	TYPE		&Value
	PRESENCE	&presence
}

-- **************************************************************
--
-- Class Definition for Protocol IEs
--
-- **************************************************************

NBAP-PROTOCOL-IES-PAIR ::= CLASS {
	&id			ProtocolIE-ID 			UNIQUE,
	&firstCriticality	Criticality,
	&FirstValue,
	&secondCriticality	Criticality,
	&SecondValue,
	&presence		Presence
}
WITH SYNTAX {
	ID			&id
	FIRST CRITICALITY	&firstCriticality
	FIRST TYPE		&FirstValue
	SECOND CRITICALITY 	&secondCriticality
	SECOND TYPE		&SecondValue
	PRESENCE		&presence
}

-- **************************************************************
--
-- Class Definition for Protocol Extensions
--
-- **************************************************************

NBAP-PROTOCOL-EXTENSION ::= CLASS {
	&id		ProtocolIE-ID 		UNIQUE,
	&criticality	Criticality,
	&Extension,
	&presence		Presence
}
WITH SYNTAX {
	ID		&id
	CRITICALITY	&criticality
	EXTENSION	&Extension
	PRESENCE	&presence
}

-- **************************************************************
--
-- Class Definition for Private IEs
--
-- **************************************************************

NBAP-PRIVATE-IES ::= CLASS {
	&id		PrivateIE-ID,
	&criticality	Criticality,
	&Value,
	&presence		Presence
}
WITH SYNTAX {
	ID		&id
	CRITICALITY	&criticality
	TYPE	&Value
	PRESENCE	&presence
}

-- **************************************************************
--
-- Container for Protocol IEs
--
-- **************************************************************

ProtocolIE-Container {NBAP-PROTOCOL-IES : IEsSetParam} ::= 
	SEQUENCE (SIZE (0..maxProtocolIEs)) OF
	ProtocolIE-Field {{IEsSetParam}}

ProtocolIE-Single-Container {NBAP-PROTOCOL-IES : IEsSetParam} ::=
	ProtocolIE-Field {{IEsSetParam}}

ProtocolIE-Field {NBAP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE {
	id		NBAP-PROTOCOL-IES.&id		({IEsSetParam}),
	criticality		NBAP-PROTOCOL-IES.&criticality	({IEsSetParam}{@id}),
	value		NBAP-PROTOCOL-IES.&Value	 ({IEsSetParam}{@id})
}

-- **************************************************************
--
-- Container for Protocol IE Pairs
--
-- **************************************************************

ProtocolIE-ContainerPair {NBAP-PROTOCOL-IES-PAIR : IEsSetParam} ::= 
	SEQUENCE (SIZE (0..maxProtocolIEs)) OF
	ProtocolIE-FieldPair {{IEsSetParam}}

ProtocolIE-FieldPair {NBAP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE {
	id				NBAP-PROTOCOL-IES-PAIR.&id			({IEsSetParam}),
	firstCriticality		NBAP-PROTOCOL-IES-PAIR.&firstCriticality	({IEsSetParam}{@id}),
	firstValue			NBAP-PROTOCOL-IES-PAIR.&FirstValue	({IEsSetParam}{@id}),
	secondCriticality		NBAP-PROTOCOL-IES-PAIR.&secondCriticality	({IEsSetParam}{@id}),
	secondValue			NBAP-PROTOCOL-IES-PAIR.&SecondValue	({IEsSetParam}{@id})
}

-- **************************************************************
--
-- Container Lists for Protocol IE Containers
--
-- **************************************************************

ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, NBAP-PROTOCOL-IES : IEsSetParam} ::=
	SEQUENCE (SIZE (lowerBound..upperBound)) OF
	ProtocolIE-Container {{IEsSetParam}}

ProtocolIE-ContainerPairList {INTEGER : lowerBound, INTEGER : upperBound, NBAP-PROTOCOL-IES-PAIR : IEsSetParam} ::=
	SEQUENCE (SIZE (lowerBound..upperBound)) OF
	ProtocolIE-ContainerPair {{IEsSetParam}}

-- **************************************************************
--
-- Container for Protocol Extensions
--
-- **************************************************************

ProtocolExtensionContainer {NBAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= 
	SEQUENCE (SIZE (1..maxProtocolExtensions)) OF
	ProtocolExtensionField {{ExtensionSetParam}}

ProtocolExtensionField {NBAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE {
	id		NBAP-PROTOCOL-EXTENSION.&id	({ExtensionSetParam}),
	criticality	NBAP-PROTOCOL-EXTENSION.&criticality	({ExtensionSetParam}{@id}),
	extensionValue	NBAP-PROTOCOL-EXTENSION.&Extension	({ExtensionSetParam}{@id})
}

-- **************************************************************
--
-- Container for Private IEs
--
-- **************************************************************

PrivateIE-Container {NBAP-PRIVATE-IES : IEsSetParam} ::= 
	SEQUENCE (SIZE (1..maxPrivateIEs)) OF
	PrivateIE-Field {{IEsSetParam}}

PrivateIE-Field {NBAP-PRIVATE-IES : IEsSetParam} ::= SEQUENCE {
	id			NBAP-PRIVATE-IES.&id	
	({IEsSetParam}),
	criticality			NBAP-PRIVATE-IES.&criticality
	({IEsSetParam}{@id}),
	value		NBAP-PRIVATE-IES.&Value
	({IEsSetParam}{@id})
}

END


9.4	Message Transfer Syntax
NBAP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ref. ITU T Rec. X.691 [11].
9.5	Timers
TPreempt
-	Specifies the maximum time that a Node B may wait for pre-emption of resources for establishment or reconfiguration of Radio Links.
10	Handling of Unknown, Unforeseen and Erroneous Protocol Data
10.1	General
Protocol Error cases can be divided into three classes:
-	Transfer Syntax Error
-	Abstract Syntax Error
-	Logical Error
Protocol errors can occur in the following functions within a receiving node:

Figure 38: Protocol Errors in NBAP.
The information stated in subclauses 10.2, 10.3 and 10.4, to be included in the message used when reporting an error, is what at minimum shall be included. Other optional information elements within the message may also be included, if available. This is also valid for the case when the reporting is done with a response message. The latter is an exception to what is stated in subclause 4.1.
10.2	Transfer Syntax Error
A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message. Transfer syntax errors are always detected in the process of ASN.1 decoding. If a Transfer Syntax Error occurs, the receiver should initiate Error Indication procedure with appropriate cause value for the Transfer Syntax protocol error.
Examples for Transfer Syntax Errors are:
-	Violation of value ranges in ASN.1 definition of messages. e.g.: If an IE has a defined value range of 0 to 10 (ASN.1: INTEGER (0..10)), and 12 will be received, then this will be treated as a transfer syntax error.
-	Violation in list element constraints. e.g.: If a list is defined as containing 1 to 10 elements, and 12 elements will be received, than this case will be handled as a transfer syntax error.
-	Missing mandatory elements in ASN.1 SEQUENCE definitions (as sent by the originator of the message).
-	Wrong order of elements in ASN.1 SEQUENCE definitions (as sent by the originator of the message).
10.3	Abstract Syntax Error
10.3.1	General
An Abstract Syntax Error occurs when the receiving functional NBAP entity:
1.	receives IEs or IE groups that cannot be understood (unknown id);
2.	receives IEs for which the logical range is violated (e.g.: ASN.1 definition: 0 to 15, the logical range is 0 to 10 (values 11 to 15 are undefined), and 12 will be received; this case will be handled as an abstract syntax error using criticality information sent by the originator of the message);
3.	does not receive IEs or IE groups but according to the specified presence of the concerned object, the IEs or IE groups should have been present in the received message;
4.	receives IEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of the same IE or IE group;
5.	receives IEs or IE groups but according to the conditional presence of the concerned object and the specified condition, the IEs or IE groups should not have been present in the received message.
Cases 1 and 2 (not comprehended IE/IE group) are handled based on received Criticality information. Case 3 (missing IE/IE group) is handled based on Criticality information and Presence information for the missing IE/IE group specified in the version of the specification used by the receiver. Case 4 (IEs or IE groups in wrong order or with too many occurrences) and Case 5 (erroneously present conditional IEs or IE groups) result in rejecting the procedure.
If an Abstract Syntax Error occurs, the receiver shall read the remaining message and shall then for each detected Abstract Syntax Error that belong to cases 1-3 act according to the Criticality Information and Presence Information for the IE/IE group due to which Abstract Syntax Error occurred in accordance with subclauses 10.3.4 and 10.3.5. The handling of cases 4 and 5 is specified in subclause 10.3.6.
10.3.2	Criticality Information
In the NBAP messages there is criticality information set for individual IEs and/or IE groups. This criticality information instructs the receiver how to act when receiving an IE or an IE group that is not comprehended, i.e. the entire item (IE or IE group) which is not (fully or partially) comprehended shall be treated in accordance with its own criticality information as specified in subclause 10.3.4.
In addition, the criticality information is used in case of the missing IE/IE group abstract syntax error (see subclause 10.3.5).
The receiving node shall take different actions depending on the value of the Criticality Information. The three possible values of the Criticality Information for an IE/IE group are:
-	Reject IE
-	Ignore IE and Notify Sender
	Ignore IE
The following rules restrict when a receiving entity may consider an IE, an IE group or an EP not comprehended (not implemented), and when action based on criticality information is applicable:
1.	IE or IE group: When one new or modified IE or IE group is implemented for one EP from a standard version, then other new or modified IEs or IE groups specified for that EP in that standard version shall be considered comprehended by the receiving entity (some may still remain unsupported).
2.	EP: The comprehension of different EPs within a standard version or between different standard versions is not mandated. Any EP that is not supported may be considered not comprehended, even if another EP from that standard version is comprehended, and action based on criticality shall be applied.
10.3.3	Presence Information
For many IEs/IE groups which are optional according to the ASN.1 transfer syntax, NBAP specifies separately if the presence of these IEs/IE groups is optional or mandatory with respect to RNS application by means of the presence field of the concerned object of class NBAP-PROTOCOL-IES, NBAP-PROTOCOL-IES-PAIR, NBAP-PROTOCOL-EXTENSION or NBAP-PRIVATE-IES.
The presence field of the indicated classes supports three values:
- Optional;
- Conditional;
- Mandatory.
If an IE/IE group is not included in a received message and the presence of the IE/IE group is mandatory or the presence is conditional and the condition is true according to the version of the specification used by the receiver, an abstract syntax error occurs due to a missing IE/IE group.
If an IE/IE group is included in a received message and the presence of the IE/IE group is conditional and the condition is false according to the version of the specification used by the receiver, an abstract syntax error occurs due to this erroneously present conditional IE/IE group.
10.3.4	Not comprehended IE/IE group
10.3.4.1	Procedure ID
The receiving node shall treat the different types of received criticality information of the Procedure ID according to the following:
Reject IE:
-	If a message is received with a Procedure ID marked with "Reject IE" which the receiving node does not comprehend, the receiving node shall reject the procedure using the Error Indication procedure.
Ignore IE and Notify Sender:
-	If a message is received with a Procedure ID marked with "Ignore IE and Notify Sender" which the receiving node does not comprehend, the receiving node shall ignore the procedure and initiate the Error Indication procedure.
Ignore IE:
-	If a message is received with a Procedure ID marked with "Ignore IE" which the receiving node does not comprehend, the receiving node shall ignore the procedure.
When using the Error Indication procedure to reject a procedure or to report an ignored procedure it shall include the Procedure ID IE, the Triggering Message IE, and the Procedure Criticality IE in the Criticality Diagnostics IE.
10.3.4.1A	Type of Message
When the receiving node cannot decode the Type of Message IE, the Error Indication procedure shall be initiated with an appropriate cause value.
10.3.4.2	IEs Other Than the Procedure ID and Type of Message
The receiving node shall treat the different types of received criticality information of an IE/IE group other than the Procedure ID IE and Type of Message IE according to the following:
Reject IE:
-	If a message initiating a procedure is received containing one or more IEs/IE groups marked with "Reject IE" which the receiving node does not comprehend; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the rejection of one or more IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
-	If a message initiating a procedure that does not have a message to report unsuccessful outcome is received containing one or more IEs/IE groups marked with "Reject IE" which the receiving node does not comprehend, the receiving node shall terminate the procedure and initiate the Error Indication procedure.
-	If a response message is received containing one or more IEs/IE groups marked with "Reject IE" that the receiving node does not comprehend, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.
Ignore IE and Notify Sender:
-	If a message initiating a procedure is received containing one or more IEs/IE groups marked with "Ignore IE and Notify Sender" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and report in the response message of the procedure that one or more IEs/IE groups have been ignored. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
-	If a message initiating a procedure that does not have a message to report the outcome of the procedure is received containing one or more IEs/IE groups marked with "Ignore IE and Notify Sender" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and initiate the Error Indication procedure to report that one or more IEs/IE groups have been ignored.
-	If a response message is received containing one or more IEs/IE groups marked with "Ignore IE and Notify Sender" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and initiate the Error Indication procedure.
Ignore IE:
- If a message initiating a procedure is received containing one or more IEs/IE groups marked with "Ignore IE" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups.
- If a response message is received containing one or more IEs/IE groups marked with "Ignore IE" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups.
When reporting not comprehended IEs/IE groups marked with "Reject IE" or "Ignore IE and Notify Sender" using a response message defined for the procedure, the Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported IE/IE group. In the Information Element Criticality Diagnostics IE the Repetition Number IE shall be included and in addition, if the not comprehended IE/IE group is not at message hierarchy level 1 (top level; see annex C) also the Message Structure IE shall be included.
When reporting not comprehended IEs/IE groups marked with "Reject IE" or "Ignore IE and Notify Sender" using the Error Indication procedure, the Procedure ID IE, the Triggering Message IE, Procedure Criticality IE, the Transaction ID IE, and the Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported IE/IE group. In the Information Element Criticality Diagnostics IE the Repetition Number IE shall be included and in addition, if the not comprehended IE/IE group is not at message hierarchy level 1 (top level; see annex C) also the Message Structure IE shall be included.
10.3.5	Missing IE or IE Group
The receiving node shall treat the missing IE/IE group according to the criticality information for the missing IE/IE group in the received message specified in the version of this specification used by the receiver:
Reject IE:
1. If a received message initiating a procedure is missing one or more IEs/IE groups with specified criticality "Reject IE"; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the missing IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
-	If a received message initiating a procedure that does not have a message to report unsuccessful outcome is missing one or more IEs/IE groups with specified criticality "Reject IE", the receiving node shall terminate the procedure and initiate the Error Indication procedure.
-	If a received response message is missing one or more IEs/IE groups with specified criticality "Reject IE", the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.
Ignore IE and Notify Sender:
-	If a received message initiating a procedure is missing one or more IEs/IE groups with specified criticality "Ignore IE and Notify Sender", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and report in the response message of the procedure that one or more IEs/IE groups were missing. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
-	If a received message initiating a procedure that does not have a message to report the outcome of the procedure is missing one or more IEs/IE groups with specified criticality "Ignore IE and Notify Sender", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing.
-	If a received response message is missing one or more IEs/IE groups with specified criticality "Ignore IE and Notify Sender", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing.
Ignore IE:
2. If a received message initiating a procedure is missing one or more IEs/IE groups with specified criticality "Ignore IE", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message.
3. If a received response message is missing one or more IEs/IE groups with specified criticality "Ignore IE", the receiving node shall ignore that those IEs/IE groups are missing and continue with the procedure based on the other IEs/IE groups present in the message.
When reporting missing IEs/IE groups with specified criticality "Reject IE" or "Ignore IE and Notify Sender" using a response message defined for the procedure, the Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported IE/IE group. In the Information Element Criticality Diagnostics IE the Repetition Number IE shall be included and in addition, if the missing IE/IE group is not at message hierarchy level 1 (top level; see annex C) also the Message Structure IE shall be included.
When reporting missing IEs/IE groups with specified criticality "Reject IE" or "Ignore IE and Notify Sender" using the Error Indication procedure, the Procedure ID IE, the Triggering Message IE, Procedure Criticality IE, the Transaction ID IE, and the Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported IE/IE group. In the Information Element Criticality Diagnostics IE the Repetition Number IE shall be included and in addition, if the missing IE/IE group is not at message hierarchy level 1 (top level; see annex C) also the Message Structure IE shall be included.
10.3.6	IEs or IE Groups Received in Wrong Order or With Too Many Occurrences or Erroneously Present
If a message with IEs or IE groups in wrong order or with too many occurrences is received or if IEs or IE groups with a conditional presence are present when the condition is not met (i.e. erroneously present), the receiving node shall behave according to the following:
-	If a message initiating a procedure is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the cause value "Abstract Syntax Error (Falsely Constructed Message)" using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure.
4.	If a message initiating a procedure that does not have a message to report unsuccessful outcome is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall terminate the procedure and initiate the Error Indication procedure, and use cause value "Abstract Syntax Error (Falsely Constructed Message)".
-	If a response message is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.
When determining the correct order only the IEs specified in the specification version used by the receiver shall be considered.
10.4	Logical Error
Logical error situations occur when a message is comprehended correctly, but the information contained within the message is not valid (i.e. semantic error), or describes a procedure which is not compatible with the state of the receiver. In these conditions, the following behaviour shall be performed (unless otherwise specified) as defined by the class of the elementary procedure, irrespective of the criticality of the IEs/IE groups containing the erroneous values.
Class 1:
Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. 
Typical cause values are:
-	Protocol Causes:
1.	Semantic Error
2.	Message not compatible with receiver state
Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the ERROR INDICATION procedure shall be initiated with an appropriate cause value. The Procedure ID IE, the Triggering Message IE and the Transaction ID IE within the Criticality Diagnostics IE shall then be included in order to identify the message containing the logical error.
Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated.
Class 2:
Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the ERROR INDICATION procedure shall be initiated with an appropriate cause value. The Procedure ID IE, the Triggering Message IE and the Transaction ID IE within the Criticality Diagnostics IE shall then be included in order to identify the message containing the logical error.
10.5	Exceptions
The error handling for all the cases described hereafter shall take precedence over any other error handling described in the other subclause of clause 10.
-	If any type of error (Transfer Syntax Error, Abstract Syntax Error or Logical Error) is detected in the ERROR INDICATION message, it shall not trigger the Error Indication procedure in the receiving Node but local error handling.
-	In case a response message or ERROR INDICATION message needs to be returned, but the information necessary to determine the receiver of that message is missing, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated.
-	If an error that terminates a procedure occurs, the returned cause value shall reflect the error that caused the termination of the procedure even if one or more abstract syntax errors with criticality “ignore and notify” have earlier occurred within the same procedure.

Annex A (normative):
Allocation and Pre-emption of Radio Links in the Node B
A.1	Deriving Allocation Information for a Radio Link
A.1.1	Establishment of a New Radio Link
The Allocation Information for a Radio Link in the case of establishment of a new Radio Link shall be derived as follows:
-	The latest received Allocation/Retention Priority IE for each transport channel shall be used.
NOTE:	The Allocation/Retention Priority IE for a transport channel may have been received in 
a) the procedure that establishes the first Radio Link for the Node B Communication Context in the Node B or
b) a procedure adding or modifying the transport channel.
-	If the Priority Level IE in the Allocation/Retention Priority IE for all transport channels that are intended to use the Radio Link is set to "no priority", the pre-emption capability of the Radio Link shall be set to "shall not trigger pre-emption".
-	If the Priority Level IE in the Allocation/Retention Priority IE for one or more of the transport channels that are intended to use the Radio Link is not set to "no priority", the allocation priority and the pre-emption capability of the Radio Link shall be set according to the following:
-	The transport channels that have the Priority Level IE in the Allocation/Retention Priority IE set to "no priority" shall be excluded when setting the allocation priority and pre-emption capability of a Radio Link.
-	The allocation priority for a Radio Link shall be set to highest priority level, given by the Priority Level IE in the Allocation/Retention Priority IE, for all non excluded transport channels that are intended to use the Radio Link.
-	If all non-excluded transport channels that are intended to use a Radio Link to be established have the pre-emption capability, given by the Pre-emption Capability IE in the Allocation/Retention Priority IE, set to "shall not trigger pre-emption", the pre-emption capability of the Radio Link shall be set to "shall not trigger pre-emption".
If one or more non-excluded transport channels that are intended to use the Radio Link to be established have the value of the Pre-emption Capability IE in the Allocation/Retention Priority IE set to "may trigger pre-emption", the pre-emption capability of the Radio Link shall be set to "may trigger pre-emption".
The derived allocation priority and pre-emption capability are only valid during this allocation/retention process.
A.1.2	Modification of an Existing Radio Link 
The Allocation Information for a Radio Link in the case of modification of a Radio Link (addition or modification of transport channels using the Radio Link) shall be derived as follows:
-	The latest received Allocation/Retention Priority IE for each transport channel shall be used.
NOTE:	The Allocation/Retention Priority IE for a transport channel may have been received in 
a) the procedure that establishes the first Radio Link for the Node B Communication Context in the Node B,
b) a previous procedure adding or modifying the transport channel, or
c) the current procedure adding or modifying the transport channel.
-	If the Priority Level IE in the Allocation/Retention Priority IE for all transport channels to be added or modified in the Radio Link is set to "no priority", the pre-emption capability of the Radio Link to be modified shall be set to "shall not trigger pre-emption".
-	If the Priority Level IE in the Allocation/Retention Priority IE for one or more of the transport channels to be added or modified in the Radio Link is not set to "no priority", the allocation priority of and the pre-emption capability of the Radio Link to be modified shall be set according to the following:
-	The transport channels to be added or modified that have the Priority Level IE in the Allocation/Retention Priority IE set to "no priority" shall be excluded when setting the allocation priority and pre-emption capability of a Radio Link to be modified.
-	The allocation priority for a Radio Link to be modified shall be set to highest priority level, given by the Priority Level IE in the Allocation/Retention Priority IE, for all the non-excluded transport channels that are to be added or modified.
-	If all non-excluded transport channels that are to be added or modified in the Radio Link have the pre-emption capability, given by the Pre-emption Capability IE in the Allocation/Retention Priority IE, set to "shall not trigger pre-emption", the pre-emption capability of the Radio Link to be modified shall be set to "shall not trigger pre-emption".
If one or more of the non-excluded transport channels to be added or modified in the Radio Link have the value of the Pre-emption Capability IE in the Allocation/Retention Priority IE set to "may trigger pre-emption", the pre-emption capability of the Radio Link to be modified shall be set to "may trigger pre-emption".
The derived allocation priority and pre-emption capability are only valid during this allocation/retention process.
A.2	Deriving Retention Information for a Radio Link
The Retention Information for an existing Radio Link shall be derived as follows:
-	The latest received Allocation/Retention Priority IE for each transport channel shall be used.
NOTE:	The Allocation/Retention Priority IE for a transport channel may have been received in 
a) the procedure that establishes the first Radio Link for the Node B Communication Context in the Node B or
b) a procedure adding or modifying the transport channel.
-	If the Priority Level IE in the Allocation/Retention Priority IE for one or more transport channels using the Radio Link is set to "no priority", the pre-emption vulnerability of the Radio Link shall be set to "not pre-emptable".
-	If the Priority Level IE in the Allocation/Retention Priority IE for all the transport channels using the Radio Link is not set to "no priority", the retention priority of the Radio Link and the pre-emption vulnerability of the Radio Link shall be set according to the following:
-	The retention priority for a Radio Link shall be set to highest priority level, given by the Priority Level IE in the Allocation/Retention Priority IE, for all transport channels that uses the Radio Link.
-	If all transport channels that uses the Radio Link have the pre-emption vulnerability, given by the Pre-emption Vulnerability IE in the Allocation/Retention Priority IE, set to "pre-emptable", the pre-emption vulnerability of the Radio Link shall be set to "pre-emptable".
If one or more transport channels that uses the Radio Link have the value of the Pre-emption Vulnerability IE in the Allocation/Retention Priority IE set to "not pre-emptable", the pre-emption vulnerability of the Radio Link shall be set to "not pre-emptable".
The derived retention priority and pre-emption vulnerability are valid until they are changed, or until the Radio Link is deleted. When new transport channels are added to or deleted from the Radio Link or when existing transport channels are modified with regards to the Allocation/Retention Priority IE, the retention information shall be derived again according to above.
A.3	The Allocation/Retention Process
The Node B shall establish or modify the resources for a Radio Link according to:
- The value of the Allocation Information (allocation priority and pre-emption capability) of the Radio Link to be established or modified. The Allocation Information is derived according to clause A.1.
- The value of the Retention Information (retention priority and pre-emption vulnerability) of existing Radio Links. The Retention Information derived according to clause A.2.
- The resource situation in the cell.
Whilst the process and the extent of the pre-emption functionality is operator dependent, the pre-emption indicators (pre-emption capability and pre-emption vulnerability) shall be treated as follows:
-.	If the pre-emption capability for a Radio Link to be established or modified is set to "may trigger pre-emption" and the resource situation so requires, the Node B may trigger the pre-emption process in clause A.4 to free resources for this allocation request.
-.	If the pre-emption capability for a Radio Link to be established or modified is set to "shall not trigger pre-emption", then this allocation request shall not trigger the pre-emption process in clause A.4.
-.	If the pre-emption vulnerability for an existing Radio Link is set to "pre-emptable", then this Radio Link shall be included in the pre-emption process in clause A.4.
-.	If the pre-emption vulnerability for an existing Radio Link is set to "not pre-emptable", then this Radio Link shall not be included in the pre-emption process in clause A.4.
A.4	The Pre-emption Process
The pre-emption process shall only pre-empt Radio Links with lower retention priority than the allocation priority of the Radio Link to be established or modified. The Radio Links to be pre-empted shall be selected in ascending order of the retention priority.
When the pre-emption process detects that one or more Radio Links have to be pre-empted to free resources for a Radio Link(s) to be established or modified, the Node B shall initiate the Radio Link Pre-emption procedure for all the Node B Communication Contexts having Radio Links selected for pre-emption and start the TPreempt timer.
When enough resources are freed to establish or modify the Radio Link(s) according to the request, the Node B shall stop the TPreempt timer and complete the procedure that triggered the pre-emption process in accordance with the "Successful Operation" subclause of the procedure.
If the TPreempt timer expires, the Node B shall regard the procedure that triggered the pre-emption process as failed and complete the procedure in accordance with the "Unsuccessful Operation" subclause of the procedure.

Annex B (informative):
Measurement Reporting
When the Report Characteristics IE is set to "Event A" (figure B.1), the Measurement Reporting procedure is initiated when the measured entity rises above the requested threshold and stays there for the requested hysteresis time. If no hysteresis time is given, the value zero shall be used for the hysteresis time.


Figure B.1: Event A reporting with Hysteresis Time specified
When the Report Characteristics IE is set to "Event B" (figure B.2), the Measurement Reporting procedure is initiated when the measured entity falls below the requested threshold and stays there for the requested hysteresis time. If no hysteresis time is given, the value zero shall be used for the hysteresis time.

Figure B.2: Event B reporting with Hysteresis Time specified
When the Report Characteristics IE is set to "Event C" (figure B.3), the Measurement Reporting procedure is initiated always when the measured entity rises by an amount greater than the requested threshold within the requested time. The reporting in figure B.3 is initiated if the Rising Time T1 is less than the requested time.


Figure B.3: Event C reporting
When the Report Characteristics IE is set to "Event D" (figure B.4), the Measurement Reporting procedure is initiated always when the measured entity falls by an amount greater than the requested threshold within the requested time. The reporting in figure B.4 is initiated if the Falling Time T1 is less than the requested time.


Figure B.4: Event D reporting

When the Report Characteristics IE is set to "Event E" (figure B.5), the Measurement Reporting procedure (Report A) is initiated always when the measured entity rises above the ‘Measurement Threshold 1’ and stays there for the ‘Measurement Hysteresis Time’ (T1 in figure B.5). If Report Periodicity IE is provided Node B shall also initiate Measurement Reporting procedure periodically. The periodic reporting continues although the measured entity falls below the ‘Measurement Threshold 1’ and is terminated by the Report B.
When the Report A conditions have been met and the measured entity falls below the ‘Measurement Threshold 2’ and stays there for the ‘Measurement Hysteresis Time’ (T1) Measurement Reporting procedure (Report B) is initiated and the periodic reporting is terminated.

Figure B.5: Event E reporting with Hysteresis Time specified and Periodic Reporting requested
When the Report Characteristics IE is set to "Event F" (figure B.6), the Measurement Reporting procedure (Report A) is initiated always when the measured entity falls below the ‘Measurement Threshold 1’ and stays there for the ‘Measurement Hysteresis Time’ (T1 in figure B.6). If Report Periodicity IE is provided Node B shall also initiate Measurement Reporting procedure periodically. The periodic reporting continues although the measured entity rises above the ‘Measurement Threshold 1’ and is terminated by the Report B.
When the Report A conditions have been met and the measured entity rises above the ‘Measurement Threshold 2’ and stays there for the ‘Measurement Hysteresis Time’ (T1) Measurement Reporting procedure (Report B) is initiated and the periodic reporting is terminated.


Figure B.6: Event F reporting with Hysteresis Time specified and Periodic Reporting requested

Annex C (informative):
Guidelines for Usage of the Criticality Diagnostics IE
C.1	EXAMPLE MESSAGE Layout
Assume the following message format:
IE/Group Name
Presence
Range
IE Type and Reference
Semantics Description
Criticality
Assigned Criticality
Message Type
M



YES
reject
Transaction ID
M



–

A
M



YES
reject
B
M



YES
reject
>E

1..<maxE>


EACH
ignore
>>F

1..<maxF>


–

>>>G

0..3, …


EACH
ignore
>>H

1..<maxH>


EACH
ignore
>>>G

0..3, …


EACH
ignore and notify
>>G
M



YES
reject
>>J

1..<maxJ>


–

>>>G

0..3, …


EACH
reject
C
M



YES
reject
>K

1..<maxK>


EACH
ignore and notify
>>L

1..<maxL>


–

>>>M
O



–

D
M



YES
reject

NOTE 1:	The IEs F, J, and L do not have assigned criticality. The IEs F, J, and L are consequently realised as the ASN.1 type SEQUENCE OF of "ordinary" ASN.1 type, e.g. INTEGER. On the other hand, the repeatable IEs with assigned criticality are realised as the ASN.1 type SEQUENCE OF of an IE object, e.g. ProtocolIE-Single-Container.
For the corresponding ASN.1 layout, see subclause C.4.

C.2	Example on a Received EXAMPLE MESSAGE
Assume further more that a received message based on the above tabular format is according to the figure below.

Figure C.1: Example of content of a received NBAP message based on the EXAMPLE MESSAGE


C.3	Content of Criticality Diagnostics
C.3.1	Example 1

Figure C.2: Example of a received NBAP message containing a not comprehended IE
If there is an error within the instance marked as grey in the IE G in the IE J shown in the figure C.2 above, this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
IE name
Value
Comment
IE Criticality
reject
Criticality for IE on the reported level, i.e. level 4.
IE ID
id-G
IE ID from the reported level, i.e. level 4.
Repetition Number
11
Repetition number on the reported level, i.e. level 4. 
(Since the IE E (level 2) is the lowest level included in the Message Structure IE this is the eleventh occurrence of IE G within the IE E (level 2).
Type of Error
not understood

Message Structure, first repetition
>IE ID
id-B
IE ID from level 1. 
Message Structure, second repetition
>IE ID
id-E
IE ID from the lowest level above the reported level, i.e. level 2. 
>Repetition Number
3
Repetition number from the lowest level above the reported level, i.e. level 2. 

NOTE 2:	The IE J on level 3 cannot be included in the Message Structure IE since they have no criticality of their own.
NOTE 3:	The repetition number of the reported IE indicates the number of repetitions of IE G received up to the detected erroneous repetition, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2).

C.3.2	Example 2

Figure C.3: Example of a received NBAP message containing a not comprehended IE
If there is an error within the second instance (marked as grey) in the sequence (IE L in the tabular format) on level 3 below IE K in the structure shown in the figure C.3 above, this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
IE name
Value
Comment
IE Criticality
ignore and notify
Criticality for IE on the reported level, i.e. level 2.
IE ID
id-K
IE ID from the reported level, i.e. level 2.
Repetition Number
3
Repetition number on the reported level, i.e. level 2. 
Type of Error
not understood

Message Structure, first repetition
>IE ID
id-C
IE ID from the lowest level above the reported level, i.e. level 1. 

NOTE 4:	The IE L on level 3 cannot be reported individually included in the Message Structure IE since it has no criticality of its own.

C.3.3	Example 3

Figure C.4: Example of a received NBAP message containing a not comprehended IE
If there is an error within the instance marked as grey in the IE G in the IE H shown in the figure C.4 above, this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
IE name
Value
Comment
IE Criticality
ignore and notify
Criticality for IE on the reported level, i.e. level 4.
IE ID
id-G
IE ID from the reported level, i.e. level 4.
Repetition Number
2
Repetition number on the reported level, i.e. level 4. 
Type of Error
not understood

Message Structure, first repetition
>IE ID
id-B
IE ID from level 1. 
Message Structure, second repetition
>IE ID
id-E
IE ID from level 2. 
>Repetition Number
3
Repetition number from level 2. 
Message Structure, third repetition
>IE ID
id-H
IE ID from the lowest level above the reported level, i.e. level 3. 
>Repetition Number
1
Repetition number from the lowest level above the reported level, i.e. level 3. 

NOTE 5:	The repetition number of level 4 indicates the number of repetitions of IE G received up to the detected erroneous repetition, counted below the same instance of the previous level with assigned criticality (instance 1 of IE H on level 3).

C.3.4	Example 4

Figure C.5: Example of a received NBAP message containing a not comprehended IE
If there is an error within the instance marked as grey in the IE G in the IE E shown in the figure C.5 above, this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
IE name
Value
Comment
IE Criticality
reject
Criticality for IE on the reported level, i.e. level 3.
IE ID
id-G
IE ID from the reported level, i.e. level 3.
Repetition Number
5
Repetition number on the reported level, i.e. level 3. 
(Since the IE E (level 2) is the lowest level included in the Message Structure IE this is the fifth occurrence of IE G within the IE E (level 2).
Type of Error
not understood

Message Structure, first repetition
>IE ID
id-B
IE ID from level 1. 
Message Structure, second repetition
>IE ID
id-E
IE ID from the lowest level above the reported level, i.e. level 2. 
>Repetition Number
3
Repetition number from the lowest level above the reported level, i.e. level 2. 

NOTE 6:	The repetition number of the reported IE indicates the number of repetitions of IE G received up to the detected erroneous repetition, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2).

C.3.5	Example 5

Figure C.6: Example of a received NBAP message with a missing IE
If the instance marked as grey in the IE G in the IE E shown in the figure C.6 above, is missing this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
IE name
Value
Comment
IE Criticality
reject
Criticality for IE on the reported level, i.e. level 3.
IE ID
id-G
IE ID from the reported level, i.e. level 3.
Repetition Number
4
Repetition number up to the missing IE on the reported level, i.e. level 3.
(Since the IE E (level 2) is the lowest level included in the Message Structure IE there have been four occurrences of IE G within the IE E (level 2) up to the missing occurrence.
Type of Error
missing

Message Structure, first repetition
>IE ID
id-B
IE ID from level 1.
Message Structure, second repetition
>IE ID
id-E
IE ID from the lowest level above the reported level, i.e. level 2.
>Repetition Number
3
Repetition number from the lowest level above the reported level, i.e. level 2.

NOTE 7:	The repetition number of the reported IE indicates the number of repetitions of IE G received up to but not including the missing occurrence, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2).

C.4	ASN.1 of EXAMPLE MESSAGE
ExampleMessage ::= SEQUENCE {
	ProtocolIEs			ProtocolIE-Container		{{ExampleMessage-IEs}},
	ProtocolExtensions	ProtocolExtensionContainer	{{ExampleMessage-Extensions}}	OPTIONAL,
	...
}

ExampleMessage-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-A	CRITICALITY reject	TYPE A	PRESENCE mandatory} |
	{ ID id-B	CRITICALITY reject	TYPE B	PRESENCE mandatory} |
	{ ID id-C	CRITICALITY reject	TYPE C	PRESENCE mandatory} |
	{ ID id-D	CRITICALITY reject	TYPE D	PRESENCE mandatory} ,
	...
}

B ::= SEQUENCE {
	e				E-List,
	iE-Extensions	ProtocolExtensionContainer { {B-ExtIEs} }	OPTIONAL,
	...
}

B-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

E-List ::= SEQUENCE (SIZE (1..maxE)) OF ProtocolIE-Single-Container { {E-IEs} }

E-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-E	CRITICALITY ignore	TYPE E	PRESENCE mandatory	}
}

E ::= SEQUENCE {
	f				F-List,
	h				H-List,
	g				G-List1,
	j				J-List,
	iE-Extensions	ProtocolExtensionContainer { {E-ExtIEs} }	OPTIONAL,
	...
}

E-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

F-List ::= SEQUENCE (SIZE (1..maxF)) OF F

F ::= SEQUENCE {
	g				G-List2	OPTIONAL,
	iE-Extensions	ProtocolExtensionContainer { {F-ExtIEs} }	OPTIONAL,
	...
}

F-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

G-List2 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Single-Container { {G2-IEs} }

G2-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-G	CRITICALITY ignore	TYPE G	PRESENCE mandatory	}
}

H-List ::= SEQUENCE (SIZE (1..maxH)) OF ProtocolIE-Single-Container { {H-IEs} }

H-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-H	CRITICALITY ignore	TYPE H	PRESENCE mandatory	}
}

H ::= SEQUENCE {
	g				G-List3	OPTIONAL,
	iE-Extensions					ProtocolExtensionContainer { {H-ExtIEs} } OPTIONAL,
	...
}

H-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

G-List3 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Single-Container { {G3-IEs} }

G3-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-G	CRITICALITY notify	TYPE G	PRESENCE mandatory	}
}

G-List1 ::= ProtocolIE-Single-Container { {G1-IEs} }

G1-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-G	CRITICALITY reject	TYPE G	PRESENCE mandatory	}
}

J-List ::= SEQUENCE (SIZE (1..maxJ)) OF J

J ::= SEQUENCE {
	g				G-List4	OPTIONAL,
	iE-Extensions	ProtocolExtensionContainer { {J-ExtIEs} }	OPTIONAL,
	...
}

J-ExtIEs	NBAP-PROTOCOL-EXTENSION ::= {
	...
}

G-List4 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Single-Container { {G4-IEs} }

G4-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-G	CRITICALITY reject	TYPE G	PRESENCE mandatory	}
}

C ::= SEQUENCE {
	k				K-List,
	iE-Extensions	ProtocolExtensionContainer { {C-ExtIEs} }	OPTIONAL,
	...
}

C-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

K-List ::= SEQUENCE (SIZE (1..maxK)) OF ProtocolIE-Single-Container { {K-IEs} }

K-IEs NBAP-PROTOCOL-IES ::= {
	{ ID id-K	CRITICALITY notify	TYPE K	PRESENCE mandatory	}
}

K ::= SEQUENCE {
	l				L-List,
	iE-Extensions	ProtocolExtensionContainer { {K-ExtIEs} }	OPTIONAL,
	...
}

K-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

L-List ::= SEQUENCE (SIZE (1..maxL)) OF L

L ::= SEQUENCE {
	m				M	OPTIONAL,
	iE-Extensions	ProtocolExtensionContainer { {L-ExtIEs} }	OPTIONAL,
	...
}

L-ExtIEs NBAP-PROTOCOL-EXTENSION ::= {
	...
}

ExampleMessage-Extensions NBAP-PROTOCOL-EXTENSION ::= {
	...
}



Annex D (normative):
IB_SG_DATA Encoding
D.1	Overall Description
There exist two variants for encoding IB_SG_DATA IE (see section 9.2.1.32), which are detailed in subsections below. To avoid incorrect transmission of System Information on Uu, the following behaviour is required:
-	For each Iub, CRNC shall use the encoding variant supported by the Node B for the IB_SG_DATA IE (see section 9.2.1.32) when sending the SYSTEM INFORMATION UPDATE REQUEST message to the Node B. This is supported by configuration in the CRNC.
D.2	IB_SG_DATA Encoding Variant 1
This variant corresponds to the algorithm, that ASN.1 length encoding for the conveyed SIB segment is performed by the RNC. Building of IB_SG_DATA segments involves two steps:
1)	Segmentation of MIB/SIB/SB and
2)	RRC encoding of the segments, which includes the PER encoding of the length in case of "SIB data variable".


Figure D.1: The Building of Segments

D.3	IB_SG_DATA Encoding Variant 2
This variant corresponds to the algorithm, that ASN.1 length encoding for the conveyed segment is not performed by the RNC. Segments are built in the CRNC by segmentation of a MIB/SIB/SB.


Figure D.2: The Building of Segments

Annex E (informative):
Reporting the status of resources used for frequency (1.28 Mcps TDD only) 
For a multi-frequency cell, the Local Cell represents the resources in the Node B that can be used for the configuration of a number of frequencies in the cell. The resources for a frequency in Node B are defined as FPM (Frequency Process Module) and is identified by FPM ID.
In the Cell Setup procedure, RNC should configure FPM for each frequency by including FPM ID IE in the CELL SETUP REQUEST message.
In the Cell Reconfiguration procedure, RNC should configure FPM for each added frequency by including FPM ID IE in the CELL RECONFIGURATION REQUEST message.
In Audit procedure, the Node B should include the FPM ID IE and the Local Cell ID IE in the Local Cell Information IE to report the status of a FPM in the AUDIT RESPONSE message.
In Resource Status Indication procedure, the Node B should include the FPM ID IE and the Local Cell ID IE in the Local Cell Information IE to report the status of a FPM in the RESOURCE STATUS INDICATION message.

Annex F (informative):
Change History
TSG #
TSG Doc.
CR
Rev
Subject/Comment
New
09/2009
-
-
-
Creation of Rel-9 version based on 8.6.0
9.0.0
45
RP-090777
1648
2
Introduction of UE AMBR concept in UMTS
9.0.0
45
RP-090774
1658
2
Introduction of TxAA extension for non-MIMO UEs
9.0.0
45
RP-090772
1659
2
Introduction of Dual Band-HSDPA
9.0.0
45
RP-090773
1667
1
Introduction of MIMO for DC HSDPA
9.0.0
46
RP-091188
1671

Introduction of Cell Portion for 1.28 Mcps TDD
9.1.0
46
RP-091187
1672
1
Single Stream MIMO for DC-HSDPA
9.1.0
46
RP-091186
1673

Activation and deactivation of secondary carrier in non serving Node B
9.1.0
46
RP-091178
1676

Correction to ASN.1 for MiMO Power offset
9.1.0
46
RP-091181
1678

Clarification of DPC mode configuration for common E-DCH
9.1.0
46
RP-091182
1680
1
Correction of abnormal conditions for Dual cell HS-DSCH in RL Addition procedure
9.1.0
46
RP-091180
1688
2
Correction on ASN.1 errors in IE Common E-DCH System Information Response LCR for 1.28Mcps TDD
9.1.0
46
RP-091180
1690
2
Correction on the SPS resource configuration for 1.28Mcps TDD
9.1.0
46
RP-091180
1696
1
Addition of ans.1 definition for the E-DCH Semi-Persistent Resource Reservation Indicator IE
9.1.0
46
RP-091180
1698
1
Correction of several IEs’ names for 1.28 Mcps TDD
9.1.0
46
RP-091180
1700
1
Correction of an error in the HS-DSCH Common System Information LCR IE
9.1.0
46
RP-091180
1702
1
Correction of HARQ Memory Partitioning configuration in Enhanced Cell_FACH Operation for 1.28 Mcps TDD
9.1.0
46
RP-091180
1704
1
Clarification of Priority Queue ID for Ehanced CELL_FACH for 1.28Mcps TDD
9.1.0
46
RP-091188
1707
2
The Power configuration method per Cell Portion for 1.28 Mcps TDD
9.1.0
46
RP-091181
1714
1
Application of MAC-e Reset Indicator for MAC-i Reset
9.1.0
46
RP-091182
1716

Further Corrections for DC-HSDPA
9.1.0
46
RP-091181
1718

Introduction of E-RNTI in RL Information in RL Setup Request
9.1.0
46
RP-091186
1719
4
Introduction of Dual-Cell HSUPA
9.1.0
46
RP-091179
1723

STTD is cell specific in Dual-Cell HSDPA
9.1.0
46
RP-091187
1729

Removal of MAC-ehs format indicator
9.1.0
46
RP-091179
1731

Correction on IE “E-AGCH Table Choice”
9.1.0
46
RP-091186
1732
1
Introduction of Re9 HSPA Capability into NBAP
9.1.0
46
RP-091195
1733

Introduction of dormant mode
9.1.0
46



Table of Contents updated
9.1.1
47
RP-100219
1734
2
E-RNTI Allocation for UE moves to Cell_FACH from Cell_DCH
9.2.0
47
RP-100215
1736
1
Allow reconfiguration of some IEs in RL Addition procedure
9.2.0
47
RP-100217
1741
1
Clarification of HS-DSCH Paging System Information LCR
9.2.0
47
RP-100217
1743
2
Addition of power control and synchronization control configurations for enhanced CELL_FACH for 1.28Mcps TDD
9.2.0
47
RP-100217
1745
2
Correction of description for RSI procedure for 1.28Mcps TDD
9.2.0
47
RP-100218
1747
1
Correction for the description of E-DCH serving radio link IE for E-DCH semi-persistent operation
9.2.0
47
RP-100219
1749
1
Correction of the presence of Sixtyfour QAM DL and MIMO Combined Capability IE
9.2.0
47
RP-100218
1751
1
A missing IE in ASN.1 for 1.28 Mcps TDD
9.2.0
47
RP-100218
1754
1
Correction on RTWP configutation in multiple frquencies cell 1.28Mcps TDD
9.2.0
47
RP-100217
1756
2
Correction on the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE for 1.28Mcps TDD
9.2.0
47
RP-100230
1757
2
Introduction of HS-PDSCH resources on TS0 for 1.28Mcps TDD
9.2.0
47
RP-100218
1763
1
Corrections to the number of Non-HS-SCCH Associated HS-SICH for 1.28Mcps TDD
9.2.0
47
RP-100230
1764
2
Corrections from NBAP ASN.1 review
9.2.0
47
RP-100218
1766
2
Clarification of HS-SCCH TPC step size configuration
9.2.0
47
RP-100230
1767
2
Addition of DGNSS Validity Period in NBAP
9.2.0
47
RP-100229
1770
1
Introduction of UE Aggregate Maximum Bit Rate Enforcement Indicator
9.2.0
47
RP-100218
1772
1
Syncronization detection window configuration in CPC for 1.28 Mcps TDD
9.2.0
47
RP-100217
1774
1
Addition of Physical Channel ID in the common E-RNTI configuration for 1.28 Mcps TDD
9.2.0
47
RP-100230
1777
2
Measurement occasion configuration in CELL_DCH for 1.28Mcps TDD
9.2.0
47
RP-100219
1780
1
Addition of F-DPCH TX Power info in Common E-DCH System Information
9.2.0
47
RP-100224
1783
2
Small Correction/Improvements for DC-HSUPA
9.2.0
47
RP-100219
1785
1
Removal of procedural text for DPC Mode IE in Common E-DCH System Information
9.2.0
47
RP-100216
1787

Correction for Procedural Text on E-RNTI Allocation at E-DCH Serving Cell Change
9.2.0
47
RP-100199
1790

Indication of Precoding Weight Set Restriction preference
9.2.0
47
RP-100221
1791
1
Remove Cell Specific HARQ memory partitioning for DC HSDPA+MIMO
9.2.0
47
RP-100216
1792

Correction of E-DCH RACH Report
9.2.0
47
RP-100216
1794

Correction of common E-DCH mac-d flow for CCCH transmission
9.2.0
48
RP-100593
1761
3
Correction to state transition of Enhanced CELL_FACH UE for LCR TDD
9.3.0
48
RP-100593
1804
1
Clarification on the usage of Treset for 1.28 Mcps TDD
9.3.0
48
RP-100592
1808
1
CPC parameters missing for serving HS-DSCH RL change in RL Addition procedure
9.3.0
48
RP-100593
1810

Correction of procedure text that appears to be duplicated and mis-placed
9.3.0
48
RP-100594
1811
2
CQI Feedback Cycle k for DC-HSDPA and MIMO operation
9.3.0
48
RP-100599
1815
1
Correction for IE Definition for HS-DSCH/E-DCH MAC PDU Size Capability
9.3.0
48
RP-100593
1818

Specify the HS-SCCH used for the BCCH specific H-RNTI at NBAP
9.3.0
48
RP-100545
1820
1
Correction for Enhanced Serving Cell Change
9.3.0
49
RP-100904
1825
1
Clarification of 64 QAM usage at intra Node B serving HS-DSCH RL change
9.4.0
49
RP-100909
1830

Best CELL Portions measurement report On Modification for 1.28Mcps TDD
9.4.0
49
RP-100905
1833

Correction of procedure text for E-DCH SPS operation
9.4.0
49
RP-100907
1837
3
Clarifications to the common measurement for 1.28Mcps TDD
9.4.0
49
RP-100905
1839
2
Corrections to the mismatch between tabular and ASN.1 for E-FACH 1.28Mcps TDD
9.4.0
49
RP-100905
1841
2
Corrections to the range of Enabling Delay for CPC 1.28Mcps TDD
9.4.0
49
RP-100909
1842

Corrections to HSDPA cell capability container
9.4.0
09/2010



Creation of Rel-10 version based on 9.4.0
10.0.0
49
RP-100911
1831
2
Introduction of 4C-HSDPA
10.0.0
49
RP-100910
1834
1
Small Technical Enhancements and Improvements for GNSS (NBAP)
10.0.0
50
RP-101275
1843

Correction of 4C-HSDPA secondary serving HS-DSCH RL change
10.1.0
50
RP-101274
1844
2
Introduction of MC-HSUPA to NBAP
10.1.0
50
RP-101277
1845
2
Introduction of MU-MIMO to NBAP
10.1.0
50
RP-101271
1848
1
Adding abnormal conditions to Enhanced Cell/URA_PCH
10.1.0
50
RP-101269
1851

Corrections to E-DCH MAC-d Flow Multiplexing for 1.28Mcps TDD
10.1.0
50
RP-101269
1854
1
Correction of Inactivity Threshold for UE DRX Cycle for 1.28Mcps TDD
10.1.0
50
RP-101316
1856
1
Adaptive Special Burst Power for 1.28Mcps TDD
10.1.0
50
RP-101275
1857
1
Addition of simultaneous cell capability for Multi-Carrier HSDPA and Single Stream MIMO
10.1.0
50
RP-101275
1859
3
Throughput/Energy Savings tradeoff for Dual Band UEs
10.1.0
SP-49
SP-100629


Clarification on the use of References (TS 21.801 CR#0030)
10.2.0
51
RP-110224
1860

Correction of Extended E-HICH ID TDD for 1.28 Mcps TDD Multi-Carrier E-DCH
10.2.0
51
RP-110222
1862

Changed values for a sub-IE in "Common E-DCH Information for E-DCH" IE
10.2.0
51
RP-110224
1863

Addition of Multi-Carrier E-DCH capability IEs for MC-HSUPA to NBAP
10.2.0
51
RP-110224
1864

Correction of SNPL carrier group indicator for 1.28 Mcps TDD Multi-Carrier E-DCH
10.2.0
51
RP-110228
1865
1
Battery optimization - tabular/ASN.1 mismatch cleanup
10.2.0
51
RP-110226
1866

Introduction of Common H-RNTI List for Common HS-DSCH SRB1 Transmission
10.2.0
51
RP-110222
1868

Inclusion of "Additional E-DCH Transmission Back Off" in "Common E-DCH Information"
10.2.0
51
RP-110226
1874
1
Add T312 and N312 for 1.28Mcps TDD
10.2.0
51
RP-110225
1876
1
Introduction of independent HSUPA schedule based on cell portion
10.2.0
51
RP-110226
1877
2
Addition of CLASS 1 procedure for Common E-DCH resource release
10.2.0
51
RP-110226
1878
2
Corrections on HS-DSCH Transmission without UE category
10.2.0
52
RP-110688
1881
1
Clarification on the Range of Possible Secondary Serving Cell List
10.3.0
52
RP-110684
1882
2
Correction of references
10.3.0
52
RP-110686
1883

ASN.1 Corrections and Tabular alignment
10.3.0
52
RP-110686
1884
1
Review Corrections
10.3.0
52
RP-110689
1885
4
Extend the Number of Supported Carriers for Multi-Carrier HSDPA for 1.28Mcps TDD
10.3.0
52
RP-110689
1890
2
Addition of AOA measurement in distributed antenna scenarios for 1.28Mcps TDD
10.3.0
52
RP-110681
1894

Correction to the MIMO capability for 1.28Mcps TDD
10.3.0
52
RP-110681
1897

Correction to the number of E-RNTI per group for 1.28Mcps TDD
10.3.0
52
RP-110689
1898
1
Introduction of cell portion based RTWP control for 1.28Mcps TDD
10.3.0
52
RP-110681
1900
1
UE Support Indicator for DL secondary HS-DSCH Activation state according to RRC Rel-9
10.3.0
52
RP-110690
1901

Correction of abnormal condition text
10.3.0
53
RP-111196
1910

Correction of some generic references to dated references
10.4.0
53
RP-111196
1911
2
Correction of the CELL_DCH Measurement Occasion Information for 1.28Mcps TDD
10.4.0
54
RP-111646
1914

Correct missing SPI reference in tabular
10.5.0
54
RP-111651
1916
1
Introduction of frequency specific compressed mode
10.5.0
54
RP-111645
1925
2
Support of dynamic HS-SCCH order for DTXDRX
10.5.0
12/2011



Creation of Rel-11 version based on 10.5.0

54
RP-111653
1915
1
Introduction of UL CLTD
11.0.0
54
RP-111652
1923
1
Introduction of 8-carrier HSDPA
11.0.0
56
RP-120815
1934
1
Clarification of the carrier capability for two-carrier HSDPA for 1.28Mcps TDD
11.1.0
56
RP-120745
1935
1
Some Corrections for UL CLTD
11.1.0
56
RP-120744
1938
-
Clarification of the enhanced TS0 capability for 1.28Mcps TDD
11.1.0
56
RP-120746
1948
3
Supporting Non-adjacent multi-carrier operation
11.1.0
56
RP-120751
1949
-
Introduction of enhanced DC-HSDPA
11.1.0
57
RP-121131
1951
1
Corrections on Multicell E-DCH Restriction of Possible Secondary cell list
11.2.0
57
RP-121132
1952
-
Further Corrections on UL CLTD
11.2.0
58
RP-121730
1959
1
Introduction of UPH in dedicated measurement procedure
11.3.0
58
RP-121723
1963
-
Introduction of Common E-DCH Implicit Release Timer
11.3.0
58
RP-121723
1967
-
Correction to DL control channel power control for E-DCH in Cell_FACH
11.3.0
58
RP-121726
1968
-
Supporting MIMO with four transmit antennas
11.3.0
58
RP-121737
1969
-
Editorial and minor corrections
11.3.0
58
RP-121727
1970
3
Introduction of Multiflow in TS 25.433
11.3.0
58
RP-121729
1971
2
Introduction of Uplink MIMO and 64QAM in TS 25.433
11.3.0
58
RP-121725
1972
2
Introduction of Further Enhancements to CELL_FACH feature
11.3.0
58
RP-121726
1975
-
ESCC support in MIMO with four transmit antennas
11.3.0
59
RP-130212
1976
2
Corrections from ASN.1 review
11.4.0
59
RP-130205
1979
1
Adding enhanced serving cell change support for 4C-HSDPA, 8C-HSDPA, Multflow, UL CLTD, UL MIMO, UL 16QAM and 64QAM
11.4.0
59
RP-130206
1985
1
Correction of Power Offset for Multiflow
11.4.0
59
RP-130206
1986
1
Correction on the values of Non-time Reference IE
11.4.0
59
RP-130206
1989
1
Codebook restriction in MIMO with four transmit antennas
11.4.0
59
RP-130206
1992
-
Extending the range of the 2nd DRX cycle length
11.4.0
60
RP-130643
1993
-
Correction tabular for Scheduling Priority Indicator IE.
11.5.0
60
RP-130641
1994
-
Correction of System Information Update to include the support for the new SIBs introduced in Rel 11
11.5.0
61
RP-131180
2002
1
Correct criticality of UL MIMO DL Control Channel Information
11.6.0
61
RP-131180
2007
-
Clarification on Flexible MAC-d PDU Size in Abnormal conditions
11.6.0
62
RP-131647
2013
2
Correction to Galileo Assistance Data Elements
11.7.0
62
RP-131905
1995
3
Introduction of HSPA signalling enhancements for more efficient resource usage for 1.28Mcps TDD
12.0.0
62
RP-131906
2008
2
Introduction of BeiDou Navigation Satellite System
12.0.0
62
RP-131648
2014
3
Correction to Galileo Assistance Data Elements
12.0.0
64
RP-140900
2017
2
Supporting L-band for Supplemental Downlink in UTRA
12.1.0
64
RP-140898
2036
-
Adding assisting HS-DPCCH repetition factors for multiflow
12.1.0
65
RP-141516
2026
3
Introduction of UTRAN Heterogeneous Networks
12.2.0
65
RP-141515
2027
5
Introduction of DCH Enhancements
12.2.0
65
RP-141524
2031
3
Supporting Enhanced Broadcast of System Information
12.2.0
65
RP-141516
2038
2
Introduction of sub-features for UTRAN Hetnet
12.2.0
65
RP-141519
2041
-
Introducing new SIB for WLAN/3GPP radio interworking
12.2.0
66
RP-142086
2042
7
Introduction of further EUL Enhancement
12.3.0
66
RP-142085
2043
1
Corrections on Enhanced Broadcast of System Information
12.3.0
66
RP-142094
2044
2
Rapporteur’s review
12.3.0
66
RP-142095
2046
1
Introduction of the UL CLTD feedback from the Multiflow assisting serving cell
12.3.0
66
RP-142087
2047
1
Introducing new SIB for Work Item: Increasing the minimum number of carriers for UE monitoring in UTRA and E-UTRA
12.3.0
66
RP-142086
2048
3
RNC to inform the serving Node B about the TTI switching decision
12.3.0
66
RP-142093
2050
-
Correction of abnormal case handling when value 5 is used in UL DPCCH Slot Format
12.3.0
66
RP-142084
2057
1
BDS Satellite Specific ICD update to version 2.0
12.3.0
66
RP-142081
2058
1
Correction to Galileo Assistance Data
12.3.0
67
RP-150349
2060
-
Correction on the value of Activation Delay
12.4.0
67
RP-150349
2062
-
Correction of ASN.1 for Fast TTI switching Mode Supported
12.4.0
68
RP-150942
2067
1
Corrections of EUL Enhancements
12.5.0
69
RP-151453
2068
2
Introduction of the Multiflow 3F-4C configuration
13.0.0
70
RP-152090
2069
3
Introduction of blind HARQ retransmissions
13.1.0
70
RP-152095
2070
1
System Information Update to support the new SIBs introduced in ACDC
13.1.0
70
RP-152089
2071
1
Introduction of TPC enhancements
13.1.0
70
RP-152093
2072
2
Introduction of NAICS
13.1.0
70
RP-152090
2073
1
Introduction of improved synchronized RRC procedures
13.1.0
70
RP-152087
2074
1
Introduction of Dual-Band Dual-Cell HSUPA Carrier Aggregation
13.1.0
70
RP-152094
2075
1
Introduce Dual Carrier/Dual Band HSUPA operation with DPDCH channel feature
13.1.0
70
RP-152090
2077
1
Introduction of URA_PCH with seamless transition
13.1.0
71
RP-160448
2080
1
Restriction removing for Dual-carrier HSUPA enhancements for UTRAN CS
13.2.0
71
RP-160449
2081
1
Rapporteur’s review
13.2.0
72
RP-161049
2083
-
Correction on DL DPCH Slot Format configuration for DCH enhancements
13.3.0

Page 3


Release 13	56	3GPP TS 25.433 V13.3.0 (2016-06)

Release 13	1386	3GPP TS 25.433 V13.3.0 (2016-06)

