Add/Delete Indicator

ENUMERATED (

Add,

Delete)

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)

Alternative Format Reporting Indicator

ENUMERATED (Alternative format is allowed, …)

Availability Status

ENUMERATED (

empty,

in test,

failed,

power off,

off line,

off duty,

dependency,

degraded,

not installed,

log full,

…)

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].

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.

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.

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]

Common Transport Channel ID

M

9.2.1.14

C-ID

M

9.2.1.9

Broadcast Reference

BIT STRING (SIZE(24))

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, Dual Cell E-DCH operation enhancements with 10ms and 10ms TTI operation not available, Dual Cell E-DCH operation enhancements with different TTI 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,

…)

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).

Dual Cell E-DCH operation enhancements with 10ms and 10ms TTI operation not available

Dual Cell E-DCH operation enhancements with 10ms and 10ms TTI is not available in the concerned cell(s).

Dual Cell E-DCH operation enhancements with different TTI operation not available

Dual Cell E-DCH operation enhancements with different TTI is not available in the concerned cell(s).

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.

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.

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.

CFN

INTEGER (0..255)

C-ID

INTEGER (0..65535)

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)

maxNrOfSF

Maximum number of Spreading Factors

CHOICE Common Measurement Accuracy

M

>T_UTRAN-GPS Measurement Accuracy Class

>>T_UTRAN-GPS Measurement Accuracy Class

M

T_UTRAN-GPS Accuracy Class

9.2.1.64C

>T_UTRAN-GANSS Measurement Accuracy Class

>>T_UTRAN-GANSS Measurement Accuracy Class

M

T_UTRAN-GANSS Accuracy Class

9.2.1.98

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].]

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

>>>T_UTRAN-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

>>>T_UTRAN-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]

–

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

CHOICE Measurement Availability Indicator

M

>Measurement Available

>>Common Measurement Value

M

9.2.1.12

>Measurement Not Available

NULL

Common Physical Channel ID

INTEGER (0..255)

Common Physical Channel ID

M

9.2.1.13

Resource Operational State

M

9.2.1.52

Availability Status

M

9.2.1.2

Common Transport Channel ID

INTEGER (0..255)

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

Common Transport Channel ID

M

9.2.1.14

Resource Operational State

M

9.2.1.52

Availability Status

M

9.2.1.2

Communication Control Port ID

INTEGER (0..65535)

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.

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

maxNrOfErrors

Maximum number of IE errors allowed to be reported with a single message.

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).

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)

MaxCTFC

Maximum number of the CTFC value is calculated according to the following:

with the notation according to ref. TS 25.331 [18]

DCH ID

INTEGER (0..255)

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.]

maxNrOfSF

Maximum number of Spreading Factors

DL Or Global Capacity Credit

INTEGER (0..65535)

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

maxNrOfDCHs

Maximum number of DCH per UE

DL Power

INTEGER

(-350..150)

Value = DL Power /10
Unit: dB
Range: -35.0 .. +15.0 dB
Step: 0.1dB

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.

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.

–

–

maxNrOfHSDSCH-1

Maximum number of HS-DSCH cells for one UE

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

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 £1.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-s) 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

maxNoSat

Maximum number of satellites for which information can be provided

CHOICE Delayed Activation

M

>CFN

>>Activation CFN

M

CFN 9.2.1.7

>Separate Indication

NULL

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

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

Diversity Control Field

ENUMERATED (

May,

Must,

Must Not,

…)

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.

FN Reporting Indicator

ENUMERATED (

FN Reporting Required,

FN Reporting Not Required)

Frame Handling Priority

INTEGER (0..15)

"0" = lowest priority,

…

"15" = highest priority

Frame Offset

INTEGER (0..255)

Frames

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.

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))

>T_GD

M

BIT STRING (SIZE (8))

>t_oc

M

BIT STRING (SIZE (16))

>af₂

M

BIT STRING (SIZE (8))

>af₁

M

BIT STRING (SIZE (16))

>af₀

M

BIT STRING (SIZE (22))

>C_rs

M

BIT STRING (SIZE (16))

>Dn

M

BIT STRING (SIZE (16))

>M₀

M

BIT STRING (SIZE (32))

>C_uc

M

BIT STRING (SIZE (16))

>e

M

BIT STRING (SIZE (32))

>C_us

M

BIT STRING (SIZE (16))

>(A)^1/2

M

BIT STRING (SIZE (32))

>t_oe

M

BIT STRING (SIZE (16))

>Fit Interval Flag

M

BIT STRING (SIZE (1))

>AODO

M

BIT STRING (SIZE (5))

>C_ic

M

BIT STRING (SIZE (16))

>OMEGA₀

M

BIT STRING (SIZE (32))

>C_is

M

BIT STRING (SIZE (16))

>i₀

M

BIT STRING (SIZE (32))

>C_rc

M

BIT STRING (SIZE (16))

>w

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))

maxNoSat

Maximum number of satellites for which information can be provided

a₀

M

BIT STRING (SIZE (8))

a₁

M

BIT STRING (SIZE (8))

a₂

M

BIT STRING (SIZE (8))

a₃

M

BIT STRING (SIZE (8))

b₀

M

BIT STRING (SIZE (8))

b₁

M

BIT STRING (SIZE (8))

b₂

M

BIT STRING (SIZE (8))

b₃

M

BIT STRING (SIZE (8))

A₁

M

BIT STRING (SIZE (24))

A₀

M

BIT STRING (SIZE (32))

t_ot

M

BIT STRING (SIZE (8))

Dt_LS

M

BIT STRING (SIZE (8))

WN_t

M

BIT STRING (SIZE (8))

WN_LSF

M

BIT STRING (SIZE (8))

DN

M

BIT STRING (SIZE (8))

Dt_LSF

M

BIT STRING (SIZE (8))

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

maxNoSat

Maximum number of satellites for which information can be provided

WN_a

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))

–

>t_oa

M

BIT STRING (SIZE (8))

–

>di

M

BIT STRING (SIZE (16))

–

>OMEGADOT

M

BIT STRING (SIZE (16))

–

>SV Health

M

BIT STRING (SIZE (8))

–

>A^1/2

M

BIT STRING (SIZE (24))

–

>OMEGA₀

M

BIT STRING (SIZE (24))

–

>M₀

M

BIT STRING (SIZE (24))

–

>w

M

BIT STRING (SIZE (24))

–

>af₀

M

BIT STRING (SIZE (11))

–

>af₁

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

maxNoOfSatAlmanac

Maximum number of satellite almanacs for which information can be provided

Latitude Sign

M

ENUMERATED (

North,

South)

Degrees of Latitude

M

INTEGER (0..2²³-1)

The IE value (N) is derived by this formula:

N2²³ X /90  N+1

X being the latitude in degree (0°.. 90°)

Degrees of Longitude

M

INTEGER

(-2²³..2²³-1)

The IE value (N) is derived by this formula:

N2²⁴ X /360  N+1

X being the longitude in degree (-180°..+180°)

Direction of Altitude

M

ENUMERATED (

Height,

Depth)

Altitude

M

INTEGER (0..2¹⁵-1)

The relation between the value (N) and the altitude (a) in meters it describes is N£ a <N+1, except for N=2¹⁵-1 for which the range is extended to include all greater values of (a).

HSDPA Capability

ENUMERATED (HSDPA Capable, HSDPA non Capable)

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

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.

maxNrOfMACdFlows

Maximum number of HS-DSCH MAC-d flows

maxNrOfPriorityQueues

Maximum number of Priority Queues

maxNrOfMACdPDUIndexes

Maximum number of different MAC-d PDU SIDs

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

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.

maxNrOfMACdFlows

Maximum number of HS-DSCH MAC-d flows

maxNrOfPriorityQueues

Maximum number of Priority Queues

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

maxNrOfPriorityQueues

Maximum number of Priority Queues

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

HS-DSCH MAC-d Flow ID

INTEGER (0..7)

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

maxNrOfMACdFlows

Maximum number of HS-DSCH MAC-d flows

maxNrOfPriorityQueues

Maximum number of Priority Queues

maxNrOfMACdPDUIndexes

Maximum number of different MAC-d PDU SIDs

HS-DSCH MAC-d Flows To Delete

1..<maxNrOfMACdFlows>

>HS-DSCH MAC-d Flow ID

M

9.2.1.31I

maxNrOfMACdFlows

Maximum number of HS-DSCH MAC-d flows

HS-DSCH MAC-d PDU Size Capability