Message Type

>Procedure Code

M

INTEGER (0..255)

>Type of Message

M

CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, Outcome, …)

RAB ID

M

BIT STRING (SIZE(8))

>Traffic Class

M

ENUMERATED
(conversational, streaming, interactive, background, …)

Desc.: This IE indicates the type of application for which the Radio Access Bearer service is optimised.

–

>RAB Asymmetry Indicator

M

ENUMERATED
(Symmetric bidirectional, Asymmetric Uni directional downlink, Asymmetric Uni directional Uplink, Asymmetric Bidirectional, …)

Desc.: This IE indicates asymmetry or symmetry of the RAB and traffic direction.

–

>Maximum Bit Rate

M

1 to <nbr-SeparateTrafficDirections>

INTEGER (1..16,000,000)

Desc.: This IE indicates the maximum number of bits delivered by UTRAN and to UTRAN at a SAP within a period of time, divided by the duration of the period.

The unit is: bit/s

This IE shall be ignored if Supported Maximum Bite Rate IE is present.

Usage:

When nbr-SeparateTrafficDirections is equal to 2, then Maximum Bit Rate attribute for downlink is signalled first, then Maximum Bit Rate attribute for uplink.

–

>Guaranteed Bit Rate

C-iftrafficConv-Stream

1 to <nbr-SeparateTrafficDirections>

INTEGER (0..16,000,000)

Desc.: This IE indicates the guaranteed number of bits delivered at a SAP within a period of time (provided that there is data to deliver), divided by the duration of the period. The unit is: bit/s.

This IE shall be ignored if Supported Guaranteed Bite Rate IE is present.

Usage:

1. When nbr-SeparateTrafficDirections is equal to 2, then Guaranteed Bit Rate for downlink is signalled first, then Guaranteed Bit Rate for uplink.

2. Delay and reliability attributes only apply up to the guaranteed bit rate.

3. Conditional value for the case of Support Mode for pre-defined SDU sizes:

Set to highest not rate controllable bitrate, where bitrate is either
– one of the RAB subflow combination bitrate IEs (when present)
or
– one of the calculated values given when dividing the compound Subflow combination SDU sizes by the value of the IE Maximum SDU Size and then multiplying this result by the value of the IE Maximum Bit Rate.

–

>Delivery Order

M

ENUMERATED (delivery order requested, delivery order not requested)

Desc: This IE indicates whether the RAB shall provide in-sequence SDU delivery or not.

Usage:

Delivery order requested: in sequence delivery shall be guaranteed by UTRAN on all RAB SDUs

Delivery order not requested: in sequence delivery is not required from UTRAN.

–

>Maximum SDU Size

M

INTEGER (0..32768)

Desc.: This IE indicates the maximum allowed SDU size.

The unit is: bit.

Usage:

Conditional value:

Set to largest RAB Subflow Combination compound SDU size (when present) among the different RAB Subflow Combinations.

–

>SDU parameters

1 to <maxRABSubflows>

See below

Desc.: This IE contains the parameters characterizing the RAB SDUs

Usage:

Given per subflow with first occurrence corresponding to subflow#1 etc…

–

>Transfer Delay

C-iftrafficConv-Stream

INTEGER (0..65535)

Desc.: This IE indicates the maximum delay for 95th percentile of the distribution of delay for all delivered SDUs during the lifetime of a RAB, where delay for an SDU is defined as the time from a request to transfer an SDU at one SAP to its delivery at the other SAP

The unit is: millisecond.

–

>Traffic Handling Priority

C – iftrafficInteractiv

INTEGER {spare (0), highest (1), .., lowest (14), no priority (15)} (0..15)

Desc.: This IE specifies the relative importance for handling of all SDUs belonging to the radio access bearer compared to the SDUs of other bearers

Usage:

Values between 1 and 14 are ordered in decreasing order of priority, ‘1’ being the highest and ’14’ the lowest.

Value 0 shall be treated as a logical error if received.

–

>Allocation/Retention priority

O

See below

Desc.: This IE specifies the relative importance compared to other Radio access bearers for allocation and retention of the Radio access bearer.

Usage:

If this IE is not received, the request is regarded as it cannot trigger the pre-emption process and it is vulnerable to the pre-emption process.

–

>Source Statistics Descriptor

C-iftrafficConv-Stream

ENUMERATED (speech, unknown, …)

Desc.: This IE specifies characteristics of the source of submitted SDUs.

–

>Relocation Requirement

O

ENUMERATED (lossless, none, …, realtime)

This IE shall be present for RABs towards the PS domain, otherwise it shall not be present.

Desc.: This IE is no longer used.

Usage:

It shall always be set to "none" when sent and it shall always be ignored when received.

Note: If the IE is not received, the procedure should continue based on the other IEs/IE Groups.

–

>Signalling Indication

O

ENUMERATED (signalling, …)

Desc.: Indicates the signalling nature of the submitted SDUs.

YES

ignore

>Extended Maximum Bit Rate

O

1 to <nbr-SeparateTrafficDirections>

INTEGER (16,000,001..256,000,000)

Desc.: This IE indicates the maximum number of bits delivered by UTRAN and to UTRAN at a SAP within a period of time, divided by the duration of the period.

The unit is: bit/s.

Usage:

When nbr-SeparateTrafficDirections is equal to 2, then Maximum Bit Rate attribute for downlink is signalled first, then Maximum Bit Rate attribute for uplink.

YES

reject

>Extended Guaranteed Bit Rate

O

1 to <nbr-SeparateTrafficDirections>

INTEGER (16,000,001..256,000,000)

Desc.: This IE indicates the guaranteed number of bits delivered at a SAP within a period of time (provided that there is data to deliver), divided by the duration of the period. The unit is: bit/s.

Usage:

1. When nbr-SeparateTrafficDirections is equal to 2, then Guaranteed Bit Rate for downlink is signalled first, then Guaranteed Bit Rate for uplink.

2. Delay and reliability attributes only apply up to the guaranteed bit rate.

YES

reject

>Supported Maximum Bit Rate

0 to <nbr-SeparateTrafficDirections>

INTEGER (1..1,000,000,000, …)

Desc.: This IE indicates the maximum number of bits delivered by UTRAN and to UTRAN at a SAP within a period of time, divided by the duration of the period.

The unit is: bit/s.

Usage:

When nbr-SeparateTrafficDirections is equal to 2, then Maximum Bit Rate attribute for downlink is signalled first, then Maximum Bit Rate attribute for uplink.

YES

reject

>Supported Guaranteed Bit Rate

0 to <nbr-SeparateTrafficDirections>

INTEGER (1..1,000,000,000, …)

Desc.: This IE indicates the guaranteed number of bits delivered at a SAP within a period of time (provided that there is data to deliver), divided by the duration of the period. The unit is: bit/s.

Usage:

When nbr-SeparateTrafficDirections is equal to 2, then Guaranteed Bit Rate for downlink is signalled first, then Guaranteed Bit Rate for uplink

Delay and reliability attributes only apply up to the guaranteed bit rate.

YES

reject

nbr-SeparateTrafficDirections

Number of Traffic Directions being signalled separately.

Set to 2 if RAB asymmetry indicator is asymmetric bidirectional.

Set to 1 in all other cases.

maxRABSubflows

Maximum number of Subflows per RAB. Value is 7.

IftrafficConv-Stream

This IE shall be present if the Traffic Class IE is set to "Conversational" or "Streaming"

IftrafficInteractiv

This IE shall be present if the Traffic Class IE is set to "Interactive"

SDU parameters

>SDU Error Ratio

C-ifErroneousSDU

Desc.: This IE indicates the fraction of SDUs lost or detected as erroneous.

This is a Reliability attribute

Usage:

The attribute is coded as follows:

Mantissa * 10 ^{– exponent}.

–

>>Mantissa

M

INTEGER (1..9)

>>Exponent

M

INTEGER (1..6)

>Residual Bit Error Ratio

M

Desc.: This IE indicates the undetected bit error ratio for each subflow in the delivered SDU.

This is a Reliability attribute.

Usage:

The attribute is coded as follows:

Mantissa * 10 ^{– exponent}.

–

>>Mantissa

M

INTEGER (1..9)

>>Exponent

M

INTEGER (1..8)

>Delivery Of Erroneous SDU

M

ENUMERATED (yes, no, no-error-detection-consideration)

Desc.: This IE indicates whether SDUs with detected errors shall be delivered or not. In case of unequal error protection, the attribute is set per subflow

This is a Reliability attribute.

Usage:

Yes: error detection applied, erroneous SDU delivered

No. Error detection is applied , erroneous SDU discarded

no-error-detection-consideration: SDUs delivered without considering error detection.

If the RNC receives this IE set to ‘Yes’ and the User Plane Mode IE is set to ‘transparent mode’, it should consider it as ‘no-error-detection-consideration’.

–

>SDU format information Parameter

O

1 to <maxRABSubflowCombinations>

See below

Desc.: This IE contains the list of possible exact sizes of SDUs and/or RAB Subflow Combination bit rates.

Given per RAB Subflow Combination with first occurrence corresponding to RAB Subflow Combination number 1.

It shall always be present for rate controllable RABs.

–

maxRABSubflowCombinations

Maximum number of RAB Subflow Combinations. Value is 64.

IfErroneousSDU

This IE shall be present if the Delivery Of Erroneous SDU IE is set to "Yes" or "No".

SDU Format Information Parameter

At least one of the Subflow SDU size IE and the RAB Subflow Combination bit rate IE shall be present when SDU format information Parameter IE is present.

For the case subflow SDUs are transmitted at constant time interval, only one of the two IEs shall be present.

Whenever only one IE is included, it shall be the same for all RAB Subflow Combinations.

–

>Subflow SDU Size

O

INTEGER (0..4095)

Desc.: This IE indicates the exact size of the SDU.

The unit is: bit.

Usage:

This IE is only used for RABs that have predefined SDU size(s). It shall be present for RABs having more than one subflow.

For RABs having only one subflow, this IE shall be present only when the RAB is rate controllable and the SDU size of some RAB Subflow Combination(s) is different than the IE Maximum SDU Size.

When this IE is not present and SDU format information Parameter is present, then the Subflow SDU size for the only existing subflow takes the value of the IE Maximum SDU size.

–

>RAB Subflow Combination Bit Rate

O

INTEGER (0..16,000,000)

Desc.: This IE indicates the RAB Subflow Combination bit rate.

The unit is: bit/s.

Usage:

When this IE is not present and SDU format information parameter is present then all Subflow SDUs are transmitted (when there is data to be transmitted) at a constant time interval.

The value of this IE shall not exceed the maximum value of the IEs ‘Maximum Bit Rate’.

The value 0 of RAB Subflow Combination bitrate indicates that the RAB uses discontinuous transfer of the SDUs.

–

Allocation/Retention Priority

–

>Priority Level

M

INTEGER {spare (0), highest (1), .., lowest (14), no priority (15)} (0..15)

Desc.: This IE indicates the priority of the request.

Usage:

Values between 1 and 14 are ordered in decreasing order of priority, ‘1’ being the highest and ’14’ the lowest.

Value 0 shall be treated as a logical error if received.

The priority level and the pre-emption indicators may be used to determine whether the request has to be performed unconditionally and immediately.

>Pre-emption Capability

M

ENUMERATED(shall not trigger pre-emption, may trigger pre-emption)

Desc.: This IE indicates the pre-emption capability of the request on other RABs

Usage:

The RAB shall not pre-empt other RABs or, the RAB may pre-empt other RABs

The Pre-emption Capability indicator applies to the allocation of resources for a RAB and as such it provides the trigger to the pre-emption procedures/processes of the RNS.

>Pre-emption Vulnerability

M

ENUMERATED(not pre-emptable, pre-emptable)

Desc.: This IE indicates the vulnerability of the RAB to pre-emption of other RABs.

Usage:

The RAB shall not be pre-empted by other RABs or the RAB may be pre-empted by other RABs.

Pre-emption Vulnerability indicator applies for the entire duration of the RAB, unless modified and as such indicates whether the RAB is a target of the pre-emption procedures/processes of the RNS.

>Queuing Allowed

M

ENUMERATED(queuing not allowed, queuing allowed)

Desc.: This IE indicates whether the request can be placed into a resource allocation queue or not.

Usage:

Queuing of the RAB is allowed

Queuing of the RAB is not allowed

Queuing allowed indicator applies for the entire duration of the RAB, unless modified.

>>Radio Network Layer Cause

M

INTEGER
(RAB pre-empted(1),

Trelocoverall Expiry(2),

Trelocprep Expiry(3),

Treloccomplete Expiry(4),

Tqueuing Expiry(5),

Relocation Triggered(6),

Unable to Establish During Relocation(8),

Unknown Target RNC(9),

Relocation Cancelled(10),

Successful Relocation(11),

Requested Ciphering and/or Integrity Protection Algorithms not Supported(12),

Conflict with already existing Integrity protection and/or Ciphering information (13),

Failure in the Radio Interface Procedure(14),

Release due to UTRAN Generated Reason(15),

User Inactivity(16),

Time Critical Relocation(17),

Requested Traffic Class not Available(18),

Invalid RAB Parameters Value(19),

Requested Maximum Bit Rate not Available(20),

Requested Maximum Bit Rate for DL not Available(33),

Requested Maximum Bit Rate for UL not Available(34),

Requested Guaranteed Bit Rate not Available(21),

Requested Guaranteed Bit Rate for DL not Available(35),

Requested Guaranteed Bit Rate for UL not Available(36),

Requested Transfer Delay not Achievable(22),

Invalid RAB Parameters Combination(23),

Condition Violation for SDU Parameters(24),

Condition Violation for Traffic Handling Priority(25),

Condition Violation for Guaranteed Bit Rate(26),

User Plane Versions not Supported(27),

Iu UP Failure(28),

TRELOCalloc Expiry (7),

Relocation Failure in Target CN/RNC or Target System (29),

Invalid RAB ID(30),

No remaining RAB(31),

Interaction with other procedure(32),

Repeated Integrity Checking Failure(37),

Requested Request Type not supported(38),

Request superseded(39),

Release due to UE generated signalling connection release(40),

Resource Optimisation Relocation(41),

Requested Information Not Available(42),

Relocation desirable for radio reasons (43),

Relocation not supported in Target RNC or Target system(44),

Directed Retry (45),

Radio Connection With UE Lost(46),

RNC unable to establish all RFCs (47),

Deciphering Keys Not Available(48),

Dedicated Assistance data Not Available(49),

Relocation Target not allowed(50),

Location Reporting Congestion(51),

Reduce Load in Serving Cell (52),

No Radio Resources Available in Target cell (53),

GERAN Iu-mode failure (54),

Access Restricted Due to Shared Networks(55),

Incoming Relocation Not Supported Due To PUESBINE Feature(56),

Traffic Load In The Target Cell Higher Than In The Source Cell(57),

MBMS – No Multicast Service For This UE(58),

MBMS – Unknown UE ID(59),

Successful MBMS Session Start – No Data Bearer Necessary(60),

MBMS – Superseded Due To NNSF(61),

MBMS – UE Linking Already Done(62),

MBMS – UE De-Linking Failure – No Existing UE Linking(63),

TMGI Unknown(64))

Value range is 1 – 64.

>Radio Network Layer

>>Transport Layer Cause

M

INTEGER
(

Signalling Transport Resource Failure(65),

Iu Transport Connection Failed to Establish(66))

Value range is 65 – 80.

>NAS

>>NAS Cause

M

INTEGER
(User Restriction Start Indication(81),

User Restriction End Indication(82),

Normal Release(83) ,

CSG Subscription Expiry(84))

Value range is 81 – 96.

>Protocol

>>Protocol Cause

M

INTEGER
(Transfer Syntax Error(97),

Semantic Error (98),

Message not compatible with receiver state (99),

Abstract Syntax Error (Reject) (100),

Abstract Syntax Error (Ignore and Notify) (101),

Abstract Syntax Error (Falsely Constructed Message) (102))

Value range is 97 – 112.

>Miscellaneous

>>Miscellaneous Cause

M

INTEGER
(O&M Intervention(113),

No Resource Available(114),

Unspecified Failure(115),

Network Optimisation(116))

Value range is 113 – 128.

>Non-standard

>>Non-standard Cause

M

INTEGER

()

Value range is 129 – 256. Cause value 256 shall not be used.

>Radio Network Layer Extension

>>Radio Network Layer Cause Extension

M

INTEGER
(IP Multicast Address And APN Not Valid(257),

MBMS De-Registration Rejected Due To Implicit Registration(258),

MBMS – Request Superseded(259),

MBMS De-Registration During Session Not Allowed(260),

MBMS – No Data Bearer Necessary(261) ,

Periodic Location Information not Available(262),

GTP Resources Unavailable(263),

TMGI in Use and Overlapping MBMS Service Area (264),

MBMS – No cell in MBMS Service Area (265),

No Iu CS UP relocation (266) ,

Successful MBMS Session Start – IP Multicast Bearer established (267),

CS Fallback triggered (268),

invalid CSG Id (269))

Value range is 257 – 512.

Deciphering Keys Not Available

The action failed because RNC is not able to provide requested deciphering keys.

Conflict with already existing Integrity protection and/or Ciphering information

The action was not performed due to that the requested security mode configuration was in conflict with the already existing security mode configuration.

Condition Violation For Guaranteed Bit Rate

The action was not performed due to condition violation for guaranteed bit rate.

Condition Violation For SDU Parameters

The action was not performed due to condition violation for SDU parameters.

Condition Violation For Traffic Handling Priority

The action was not performed due to condition violation for traffic handling priority.

Dedicated Assistance data Not Available

The action failed because RNC is not able to successfully deliver the requested dedicated assistance data to the UE.

Directed Retry

The reason for action is Directed Retry

Failure In The Radio Interface Procedure

Radio interface procedure has failed.

Incoming Relocation Not Supported Due To PUESBINE Feature

The incoming relocation cannot be accepted by the target RNC because of the PUESBINE feature.

Interaction With Other Procedure

Relocation was cancelled due to interaction with other procedure.

Invalid RAB ID

The action failed because the RAB ID is unknown in the RNC.

Invalid RAB Parameters Combination

The action failed due to invalid RAB parameters combination.

Invalid RAB Parameters Value

The action failed due to invalid RAB parameters value.

Iu UP Failure

The action failed due to Iu UP failure.

No remaining RAB

The reason for the action is no remaining RAB.

RAB Pre-empted

The reason for the action is that RAB is pre-empted.

Radio Connection With UE Lost

The action is requested due to losing radio connection to the UE

Release Due To UE Generated Signalling Connection Release

Release requested due to UE generated signalling connection release.

Release Due To UTRAN Generated Reason

Release is initiated due to UTRAN generated reason.

Relocation Cancelled

The reason for the action is relocation cancellation.

Relocation Desirable for Radio Reasons

The reason for requesting relocation is radio related.

Relocation Failure In Target CN/RNC Or Target System

Relocation failed due to a failure in target CN/RNC or target system.

Relocation Not Supported In Target RNC Or Target System

Relocation failed because relocation was not supported in target RNC or target system.

Relocation Target not allowed

Relocation to the indicated target cell is not allowed for the UE in question.

Relocation Triggered

The action failed due to relocation.

Repeated Integrity Checking Failure

The action is requested due to repeated failure in integrity checking.

Request Superseded

The action failed because there was a second request on the same RAB.

Requested Ciphering And/Or Integrity Protection Algorithms Not Supported

The UTRAN or the UE is unable to support the requested ciphering and/or integrity protection algorithms.

Requested Guaranteed Bit Rate For DL Not Available

The action failed because requested guaranteed bit rate for DL is not available.

Requested Guaranteed Bit Rate For UL Not Available

The action failed because requested guaranteed bit rate for UL is not available.

Requested Guaranteed Bit Rate Not Available

The action failed because requested guaranteed bit rate is not available.

Requested Information Not Available

The action failed because requested information is not available.

Requested Maximum Bit Rate For DL Not Available

The action failed because requested maximum bit rate for DL is not available.

Requested Maximum Bit Rate For UL Not Available

The action failed because requested maximum bit rate for UL is not available.

Requested Maximum Bit Rate Not Available

The action failed because requested maximum bit rate is not available.

Requested Request Type Not Supported

The RNC is not supporting the requested location request type either because it doesn’t support the requested event or it doesn’t support the requested report area.

Location Reporting Congestion

The action was not performed due to an inability to support location reporting caused by overload.

Requested Traffic Class Not Available

The action failed because requested traffic class is not available.

Requested Transfer Delay Not Achievable

The action failed because requested transfer delay is not achievable.

Resource Optimisation Relocation

The reason for requesting relocation is resource optimisation.

Successful Relocation

The reason for the action is completion of successful relocation.

Time Critical Relocation

Relocation is requested for time critical reason i.e. this cause value is reserved to represent all critical cases where the connection is likely to be dropped if relocation is not performed.

T_QUEUING Expiry

The action failed due to expiry of the timer T_QUEUING.

T_RELOCalloc Expiry

Relocation Resource Allocation procedure failed due to expiry of the timer T_RELOCalloc.

T_{RELOCcomplete} Expiry

The reason for the action is expiry of timer T_{RELOCcomplete}.

T_RELOCoverall Expiry

The reason for the action is expiry of timer T_RELOCoverall.

T_RELOCprep Expiry

Relocation Preparation procedure is cancelled when timer T_RELOCprep expires.

Unable To Establish During Relocation

RAB failed to establish during relocation because it cannot be supported in the target RNC or the RAB did not exist in the source RNC.

Unknown Target RNC

Relocation rejected because the target RNC is not known to the CN.

User Inactivity

The action is requested due to user inactivity on one or several non real time RABs e.g. in order to optimise radio resource.

User Plane Versions Not Supported

The action failed because requested user plane versions were not supported.

RNC unable to establish all RFCs

RNC couldn’t establish all RAB subflow combinations indicated within the RAB Parameters IE.

Reduce Load in Serving Cell

Load on serving cell needs to be reduced.

No Radio Resources Available in Target Cell

Load on target cell is too high.

GERAN Iu-mode failure

The RAB establishment/modification/relocation failed because the GERAN BSC cannot provide an appropriate RAB due to limited capabilities within GERAN.

Access Restricted Due to Shared Networks

Access is not permitted in the cell due to Shared Networks.

Traffic Load In The Target Cell Higher Than In The Source Cell

Relocation to reduce load in the source cell is rejected, as the target cell’s traffic load is higher than that in the source cell.

MBMS – No Multicast Service For This UE

The request for the Multicase Service list of one UE was not fulfilled because the UE does not have any active multicast service.

MBMS – Unknown UE ID

The request for the Multicase Service list of one UE was not fulfilled because the CN does not know the UE.

Successful MBMS Session Start – No Data Bearer Necessary

The MBMS Session Start procedure was successfully performed, but the RNC does not have any interested UE.

MBMS – Superseded Due To NNSF

The MBMS Session Start procedure was rejected because of successful operation towards another CN node.

MBMS – UE Linking Already Done

The UE linking failed, because the UE has already been linked to the given Multicast service.

MBMS – UE De-Linking Failure – No Existing UE Linking

The UE de-linking failed, because the UE had not been linked to the given Multicast service.

TMGI Unknown

The requested MBMS action failed because the indicated TMGI is unknown.

Successful MBMS Session Start – IP Multicast Bearer established

The RNC was able to join the indicated IP Multicast Group.

IP Multicast Address And APN Not Valid

The MBMS registration failed because the IP Multicast Address and APN are not valid.

MBMS De-Registration Rejected Due To Implicit Registration

The MBMS De-registration was rejected because of implicit registration.

MBMS – Request Superseded

The MBMS Registration or De-registration was superseded due to another ongoing procedure.

MBMS De-Registration During Session Not Allowed

The MBMS De-registration is not allowed during the MBMS session.

MBMS – No Data Bearer Necessary

The RNC no longer have any UEs interested in the MBMS data bearer.

Periodic Location Information not Available

No UE position estimate was available when the periodic report was triggered.

GTP Resources Unavailable

The RNC initiates RAB Release Request procedure with this error cause value if it received a GTP-U error indication.

TMGI in Use and overlapping MBMS Service Area

The RNC has an MBMS Session up and running with that TMGI, a parallel MBMS session with the same TMGI in another overlapping MBMS Service Area is not allowed.

MBMS – No Cell in MBMS Service Area

The RNC does not have any cell of the indicated MBMS Service Area.

No Iu CS UP relocation

The relocation is triggered by CS call and the source RNC has no Iu CS user plane.

CS Fallback triggered

The relocation was triggered for CS Fallback reason at the source side.

Invalid CSG Id

The CSG ID provided to the target UTRAN was found invalid.

Iu Transport Connection Failed to Establish

The action failed because the Iu Transport Network Layer connection could not be established.

Signalling Transport Resource Failure

Signalling transport resources have failed (e.g. processor reset).

Normal Release

The release is normal.

User Restriction Start Indication

A location report is generated due to entering a classified area set by O&M.

User Restriction End Indication

A location report is generated due to leaving a classified area set by O&M.

CSG Subscription Expiry

The action is due to the UE becoming a non-member of the currently used CSG.

Abstract Syntax Error (Reject)

The received message included an abstract syntax error and the concerning criticality indicated "reject".

Abstract Syntax Error (Ignore And Notify)

The received message included an abstract syntax error and the concerning criticality indicated "ignore and notify".

Abstract Syntax Error (Falsely Constructed Message)

The received message contained IEs or IE groups in wrong order or with too many occurrences.

Message Not Compatible With Receiver State

The received message was not compatible with the receiver state.

Semantic Error

The received message included a semantic error.

Transfer Syntax Error

The received message included a transfer syntax error.

Network Optimisation

The action is performed for network optimisation.

No Resource Available

No requested resource is available.

O&M Intervention

The action is due to O&M intervention.

Unspecified Failure

Sent when none of the specified cause values applies.

CN Domain Indicator

M

ENUMERATED (CS domain, PS domain)

Trace Type

M

OCTET STRING (SIZE(1))

Coded as the Trace Type specified in 3GPP TS, as defined in TS 52.008 [62].

Trigger ID

M

OCTET STRING (SIZE(3..22))

Typically an OMC identity.

Trace Reference

M

OCTET STRING (SIZE(2..3))

Choice UE Identity

>IMSI

>>IMSI

M

OCTET STRING (SIZE (3..8))

– digits 0 to 9, encoded 0000 to 1001,

– 1111 used as filler digit,

two digits per octet,

– bit 4 to 1 of octet n encoding digit 2n-1,

– bit 8 to 5 of octet n encoding digit 2n.

Number of decimal digits shall be from 6 to 15 starting with the digits from the PLMN identity.

When the IMSI is made of an odd number of digits, the filler digit shall be added at the end to make an even number of digits of length 2N. The filler digit shall then be consequently encoded as bit 8 to 5 of octet N.

>IMEI

>>IMEI

M

OCTET STRING (SIZE (8))

– hexadecimal digits 0 to F, two hexadecimal digits per octet,

– each hexadecimal digit encoded 0000 to 1111,

– 1111 used as filler for bits 8 to 5 of last octet,

– bit 4 to 1 of octet n encoding digit 2n-1,

– bit 8 to 5 of octet n encoding digit 2n.

Number of hexadecimal digits shall be 15.

>IMEISV

>>IMEISV

M

OCTET STRING (SIZE (8))

– hexadecimal digits 0 to F, two hexadecimal digits per octet,

– each hexadecimal digit encoded 0000 to 1111,

– bit 4 to 1 of octet n encoding digit 2n-1,

– bit 8 to 5 of octet n encoding digit 2n.

Number of hexadecimal digits shall be 16.

OMC ID

M

OCTET STRING (SIZE(3..22))

Coded as the OMC ID specified in UMTS TS, as defined in GSM TS 12.20 [25].

Integrity Protection Information

>Permitted Integrity Protection Algorithms

1 to 16

>>Integrity Protection Algorithm

M

INTEGER ( standard UIA1 (0), standard UIA2 (1) )

Value range is 0 to 15. Only two values used.

>Integrity Protection Key

M

BIT STRING (SIZE(128))

Encryption Information

>Permitted Encryption Algorithms

1 to 16

>>Encryption Algorithm

M

INTEGER (no encryption (0), standard UEA1 (1), standard UEA 2 (2) )

Value range is 0 to 15. Only three values used.

>Encryption Key

M

BIT STRING (SIZE(128))

Chosen Integrity Protection Algorithm

M

INTEGER ( standard UIA1 (0), standard UIA2 (1), no value (15))

Value range is 0 to 15. Only two values used over Iu interface.

The value "no value" shall only be used in case of RANAP signalling over MAP/E TS 29.108 [23].

Chosen Encryption Algorithm

M

INTEGER (no encryption (0), standard UEA1 (1), standard UEA 2 (2) )

Value range is 0 to 15. Only three values used.

Request Type

>Event

M

ENUMERATED(Stop Change of service area, Direct, Change of service area, …, Stop Direct, Periodic, Stop Periodic)

>Report Area

M

ENUMERATED(Service Area, Geographical Area, …)

When the Event IE is set to "Stop Change of service area" or to "Stop Direct", the value of the Report area IE shall be the same as in the LOCATION REPORTING CONTROL message that initiated the location reporting.

>Accuracy Code

O

INTEGER
(0..127)

The requested accuracy "r" is derived from the "accuracy code" k by

r = 10x(1.1^k-1).

The Accuracy Code IE shall be understood as the horizontal accuracy code.

Data Volume Reporting Indication

M

ENUMERATED (do report, do not report)

User Plane Mode

M

ENUMERATED (transparent mode, support mode for predefined SDU sizes, …)

This IE contains the mode of operation of the Iu UP protocol.

UP Mode Versions

M

BIT STRING (SIZE(16))

Indicates the versions of the selected UP mode that are required and supported by the CN.

Choice Paging Area ID

>LAI

>>LAI

M

9.2.3.6

>RAI

>>RAI

>>>LAI

M

9.2.3.6

>>>RAC

M

9.2.3.7

Non Searching Indication

M

ENUMERATED (non-searching, searching)

Relocation Type

M

ENUMERATED (UE not involved in relocation of SRNS,UE involved in relocation of SRNS, …)

Choice Source ID

–

>Source RNC-ID

–

>>PLMN identity

M

9.2.3.55

–

>>RNC-ID

M

INTEGER (0..4095)

If the Extended RNC-ID IE is included in the Source ID IE, the RNC-ID IE shall be ignored.

–

>>Extended RNC-ID

O

9.2.1.39a

The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095.

YES

reject

>SAI

>>SAI

M

9.2.3.9

–

Choice Target ID

–

>Target RNC-ID

–

>>Target RNC-ID

M

>>>LAI

M

9.2.3.6

–

>>>RAC

O

9.2.3.7

–

>>>RNC-ID

M

INTEGER (0..4095)

If the Extended RNC-ID IE is included in the Target ID IE, the RNC-ID IE shall be ignored.

In case of UMTS to E-UTRAN relocation, if included, this IE will contain the Corresponding RNC-ID of the target eNB.

–

>>>Extended RNC-ID

O

9.2.1.39a

The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095.

YES

reject

>CGI

–

>>CGI

M

>>>PLMN identity

M

9.2.3.55

–

>>>LAC

M

OCTET STRING (SIZE(2))

0000 and FFFE not allowed.

–

>>>CI

M

OCTET STRING (SIZE(2))

–

>>>RAC

O

9.2.3.7

YES

ignore

>Target eNB-ID

>>Target eNB-ID

>>>PLMN identity

M

9.2.3.55

–

>>>Choice eNB ID

–

>>>>Macro eNB ID

M

BIT STRING (SIZE(20))

Equal to the 20 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see TS 36.413 [49]) of each cell served by the eNodeB.

–

>>>>Home eNB ID

M

BIT STRING (SIZE(28))

Equal to the Cell Identity IE contained in the E-UTRAN CGI IE (see TS 36.413 [49]) of the cell served by the eNodeB.

NOTE:

Inter-system handover to a Home eNB is not supported in Rel-8.

–

>>>> Short Macro eNB ID

M

BIT STRING (SIZE(18))

Equal to the 18 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see TS 36.413 [49]) of each cell served by the eNodeB.

>>>> Long Macro eNB ID

M

BIT STRING (SIZE(21))

Equal to the 21 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see TS 36.413 [49]) of each cell served by the eNodeB.

>>>Selected TAI

M

9.2.1.30C

Contains the TAC of the target cell and the PLMN selected for that target cell.

–

MS Classmark 2

M

OCTET STRING

Coded as the Mobile Station Classmark 2 IE, as defined in TS 25.331 [10].

MS Classmark 3

M

OCTET STRING

Coded as the Mobile Station Classmark 3 IE, as defined in TS 25.331 [10].

RRC Container

M

OCTET STRING

–

Number of Iu Instances

M

INTEGER (1..2)

–

Relocation Type

M

9.2.1.23

–

Chosen Integrity Protection Algorithm

O

9.2.1.13

Indicates the integrity protection algorithm.

–

Integrity Protection Key

O

BIT STRING (SIZE(128))

–

Chosen Encryption Algorithm

O

9.2.1.14

Indicates the algorithm for ciphering of signalling data.

–

Ciphering Key

O

BIT STRING (SIZE(128))

–

Chosen Encryption Algorithm

O

9.2.1.14

Indicates the algorithm for ciphering of CS user data.

–

Chosen Encryption Algorithm

O

9.2.1.14

Indicates the algorithm for ciphering of PS user data.

–

d-RNTI

C – ifUEnotinvolved

INTEGER (0..1048575)

–

Target Cell ID

C – ifUEinvolved

INTEGER (0..268435455)

This information element identifies a cell uniquely within UTRAN and consists of RNC-ID and C-ID as defined in TS 25.401 [3] or Cell Identity IE as defined in TS 25.331[10] if the target is a HNB TS 25.467 [55].

–

RAB TrCH Mapping

O

1 to <maxnoofRABs>

–

>RAB ID

M

9.2.1.2

–

>RAB Subflow

M

1 to <maxRAB-Subflows>

The RAB Subflows shall be presented in an order that corresponds to the order in which the RBs are presented per RAB in the RRC container included in this IE.

–

>>Transport Channel IDs

–

>>>DCH ID

O

INTEGER (0..255)

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.

–

>>>DSCH ID

O

INTEGER (0..255)

The DSCH ID is the identifier of an active downlink shared transport channel. It is unique for each DSCH among the active DSCHs simultaneously allocated for the same UE.

–

>>>USCH ID

O

INTEGER (0..255)

The USCH ID is the identifier of an active uplink shared transport channel. It is unique for each USCH among the active USCHs simultaneously allocated for the same UE.

–

>>>HS-DSCH MAC-d Flow ID

O

INTEGER (0..7)

The HS-DSCH MAC-d Flow ID is the identifier of an HS-DSCH MAC-d flow over Iur.

YES

ignore

>>>E-DCH MAC-d Flow ID

O

INTEGER (0..7)

The E-DCH MAC-d Flow ID is the identifier of an E-DCH MAC-d flow over Iur.

YES

ignore

>CN Domain Indicator

M

9.2.1.5

YES

ignore

SRB TrCH Mapping

O

1 to <maxnoofSRBs>

GLOBAL

reject

>SRB ID

M

INTEGER (1..32)

The SRB ID is the absolute value of the SRB.

–

>DCH ID

O

INTEGER (0..255)

The DCH ID is the identifier of an active dedicated transport channel over Iur. It is unique for each active DCH among the active DCHs simultaneously allocated for the same UE.

–

>DSCH ID

O

INTEGER (0..255)

The DSCH ID is the identifier of an active downlink shared transport channel over Iur. It is unique for each DSCH among the active DSCHs simultaneously allocated for the same UE.

–

>USCH ID

O

INTEGER (0..255)

The USCH ID is the identifier of an active uplink shared transport channel over Iur. It is unique for each USCH among the active USCHs simultaneously allocated for the same UE.

–

>HS-DSCH MAC-d Flow ID

O

INTEGER (0..7)

The HS-DSCH MAC-d Flow ID is the identifier of an HS-DSCH MAC-d flow over Iur.

YES

ignore

>E-DCH MAC-d Flow ID

O

INTEGER (0..7)

The E-DCH MAC-d Flow ID is the identifier of an E-DCH MAC-d flow over Iur.

YES

ignore

Cell Load Information Group

O

9.2.1.60

For "Cell Load-Based Inter-System Handover".

YES

ignore

Trace Recording Session Information

O

9.2.1.66

YES

ignore

MBMS Linking Information

O

ENUMERATED (UE-has-joined-Multicast-Services, …)

YES

ignore

d-RNTI for No IuCS UP

O

INTEGER (0..1048575)

YES

reject

UE History Information

O

OCTET STRING

Defined in TS 36.413 [49].

YES

ignore

Subscriber Profile ID for RAT/Frequency priority

O

9.2.1.86

YES

ignore

SRVCC Information

O

9.2.1.89

Included only in case of intra-UMTS SRVCC.

YES

reject

PS RAB To Be Replaced

O

RAB ID

9.2.1.2

Included only in case of intra-UMTS SRVCC.

YES

reject

CSFB Information

O

ENUMERATED (CSFB, CSFB High Priority, …)

YES

ignore

IRAT Measurement Configuration

O

9.2.1.96

YES

ignore

Management Based MDT Allowed

O

9.2.1.110

YES

ignore

Management Based MDT PLMN List

O

MDT PLMN List

9.2.1.116

YES

ignore

Last E-UTRAN PLMN Identity

O

9.2.3.55

PLMN Identity

Indicates the E-UTRAN PLMN ID where the UE formerly requested CS Fallback to UTRAN.

YES

ignore

SRVCC Source

O

ENUMERATED (v5G, …)

Indicates the SRVCC source RAN.

YES

ignore

IfUEnotinvolved

This IE shall be present if the Relocation type IE is set to "UE not involved in relocation of SRNS".

IfUEinvolved

This IE shall be present if the Relocation type IE is set to "UE involved in relocation of SRNS".

maxnoofRABs

Maximum no. of RABs for one UE. Value is 256.

maxRABSubflows

Maximum no. of subflows per RAB. Value is 7.

maxnoofSRBs

Maximum no. of SRBs per RAB. Value is 8.

Old BSS To New BSS Information

M

OCTET STRING

Coded as the Old BSS to New BSS information elements field of the Old BSS to New BSS Information IE defined in TS 48.008 [11].

RRC Container

M

OCTET STRING

d-RNTI

O

INTEGER (0..1048575)

May be included to allow the triggering of the Relocation Detect procedure from the Iur Interface.

UE Application Layer Measurement Support Indication

O

BITSTRING

(SIZE(8))

Each bit in the bitmap indicates an UE Application layer measurement.

Bit 0 = QoE for streaming service

Bit 1 = QoE for MTSI

Value ‘1’ indicates “Supported” and value ‘0’ indicates “not Supported”.

Unused bits are reserved for future use.

YES

ignore

Source to Target Transparent Container

M

OCTET STRING

This IE includes a transparent container from the source RAN node to the target RAN node. In inter-system handovers from UTRAN, the IE is encoded according to the specifications of the target system.

Note: In the current version of this specification, this IE may either carry the Source RNC to Target RNC Transparent Container or the Source eNB to Target eNB Transparent Container IE as defined in TS 36.413 [49].

Target to Source Transparent Container

M

OCTET STRING

Note: In the current version of this specification, this IE may either carry the Target RNC to Source RNC Transparent Container or the Target eNB to Source eNB Transparent Container IE as defined in TS 36.413 [49].

PLMN identity

M

9.2.3.55

TAC

M

OCTET STRING (SIZE (2))

L3 Information

M

OCTET STRING

Coded as the value part of the Layer 3 Information IE defined in TS 48.008 [11] (i.e. excluding the Element Identifier and the Length fields).

Number Of Steps

M

INTEGER (1..16)

DL N-PDU Sequence Number

M

INTEGER (0 ..65535)

This IE indicates the sequence number of the next DL N-PDU that would have been sent to the UE by a source system.

This is the 16 bit sequence number.

UL N-PDU Sequence Number

M

INTEGER (0 ..65535)

This IE indicates the sequence number of the next UL N-PDU that would have been expected from the UE by a source system.

This is the 16 bit sequence number.

Criticality Diagnostics

>Procedure Code

O

INTEGER (0..255)

Procedure Code 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.

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

>Procedure Criticality

O

ENUMERATED(reject, ignore, notify)

This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure).

Information Element Criticality Diagnostics

0 to <maxnooferrors>

>IE Criticality

M

ENUMERATED(reject, ignore, notify)

The IE Criticality is used for reporting the criticality of the triggering IE. The value ‘ignore’ shall not 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

– in case of a not understood IE:
The number of occurrences of the reported IE up to and including the not understood occurrence

– in case of 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.42

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

maxnooferrors

Maximum no. of IE errors allowed to be reported with a single message. The value for maxnooferrors is 256.

Key Status

M

ENUMERATED (old, new, …)

DRX Cycle Length Coefficient

M

INTEGER
(6..9)

Iu Signalling Connection Identifier

M

BIT STRING (SIZE(24))

The most significant bit of this IE shall indicate the node, that has assigned the value.

MSB = "0": assigned by the RNC;

MSB = "1": assigned by the CN.

PLMN identity

M

9.2.3.55

RNC-ID

M

INTEGER (0..4095)

If the Extended RNC-ID IE is included in the message, the RNC-ID IE shall be ignored.

Extended RNC-ID

M

INTEGER (4096..65535)

The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095.

Note: Application of the Extended RNC-ID IE to very large networks is FFS.

PDP Type Information

M

1 to <maxnoofPDPDirections>

ENUMERATED(empty, PPP, OSP:IHOSS, IPv4, IPv6,…)

PDP Type is defined in TS 24.008 [8], and the restrictions on usage shall comply with TS 24.008 [8].

Usage:

When the IE is repeated then PDP Type for downlink is signalled first, followed by PDP Type for uplink; when the IE is not repeated, the PDP Type shall apply to both uplink and downlink.

OSP:IHOSS: This value shall not be used.

maxnoofPDPDirections

Number of directions for which PDP Type is signalled separately

PDP Type Information extension

M

1 to <maxnoofPDPDirections>

ENUMERATED(IPv4 and IPv6,…)

PDP Type is defined in TS 24.008 [8], and the restrictions on usage shall comply with TS 24.008 [8].

Usage:

When the IE is repeated then PDP Type for downlink is signalled first, followed by PDP Type for uplink; when the IE is not repeated, the PDP Type shall apply to both uplink and downlink.

maxnoofPDPDirections

Number of directions for which PDP Type is signalled separately

Service Handover

M

ENUMERATED (Handover to GSM should be performed, Handover to GSM should not be performed, Handover to GSM shall not be performed, …)

Message structure

1 to <maxnooflevels>

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.

GLOBAL

ignore

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

–

maxnooflevels

Maximum no. of message levels to report. The value for maxnooflevels is 256.

Alternative RAB parameter values

>Alternative Maximum Bit Rate information

O

Included only if negotiation is allowed for this IE.

–

>>Type of Alternative Maximum Bit Rate Information

M

ENUMERATED (Unspecified, Value range, Discrete values,…)

Unspecified means that negotiation is allowed, but no alternative values are provided from the CN, i.e., the RNC is allowed to assign any value equal or below the ones indicated in the RAB Parameters IE.

>>Alternative Maximum Bit Rates

C – ifValueRangeorDiscreteValuesMBR

1 to <nrb-Alternative Values>

For Value Range, one value limit is given here and the other given by Maximum Bit Rate in the RAB Parameters IE.

For Discrete Values; 1 to 16 discrete values can be given.

>>>Bit Rate

M

1 to <nbr-SeparateTrafficDirections>

INTEGER (1..16,000,000)

When nbr-SeparateTrafficDirections is equal to 2, then the Bit Rate attribute for downlink is signalled first, then the Bit Rate attribute for uplink.

>Alternative Guaranteed Bit Rate Information

O

Included only if negotiation is allowed for this IE.

–

>>Type of Alternative Guaranteed Bit Rate Information

M

ENUMERATED (Unspecified, Value range, Discrete values,…)

Unspecified means that negotiation is allowed, but no alternative values are provided from the CN, i.e., the RNC is allowed to assign any value equal or below the ones indicated in the RAB Parameters IE.

>>Alternative Guaranteed Bit Rates

C – ifValueRangeorDiscreteValuesGBR

1 to <nrb-Alternative Values>

For Value Range, one value limit is given here and the other given by Guaranteed Bit Rate in the RAB Parameters IE.

For Discrete Values, 1 to 16 discrete values can be given.

>>>Bit Rate

M

1 to <nbr-SeparateTrafficDirections>

INTEGER (1..16,000,000)

When nbr-SeparateTrafficDirections is equal to 2, then the Bit Rate attribute for downlink is signalled first, then the Bit Rate attribute for uplink.

>Alternative RAB Configuration

O

RAB Parameters 9.2.1.3

Indicates the possibility for RNC to request CN to execute the included alternative RAB configuration, e.g., for network-initiated SCUDIF purpose TS 23.172 [43].

YES

ignore

>Extended Alternative Guaranteed Bit Rate Information

O

Included only if negotiation is allowed for this IE.

YES

ignore

>>Type of Extended Alternative Guaranteed Bit Rate Information

M

ENUMERATED (Unspecified, Value range, Discrete values,…)

Unspecified means that negotiation is allowed, but no alternative values are provided from the CN, i.e., the RNC is allowed to assign any value equal or below the ones indicated in the RAB Parameters IE.

>>Extended Alternative Guaranteed Bit Rates

C – ifValueRangeorDiscreteValuesGBR

1 to <nrb-Alternative Values

For Value Range, one value limit is given here and the other given by Extended Guaranteed Bit Rate in the RAB Parameters IE.

For Discrete Values; 1 to 16 discrete values can be given.

>>>Extended Bit Rate

M

1 to <nbr-SeparateTrafficDirections>

INTEGER (16,000,001..256,000,000)

When nbr-SeparateTrafficDirections is equal to 2, then the Bit Rate attribute for downlink is signalled first, then the Bit Rate attribute for uplink.

>Extended Alternative Maximum Bit Rate Information

O

Included only if negotiation is allowed for this IE.

YES

ignore

>>Type of Extended Alternative Maximum Bit Rate Information

M

ENUMERATED (Unspecified, Value range, Discrete values,…)

Unspecified means that negotiation is allowed, but no alternative values are provided from the CN, i.e., the RNC is allowed to assign any value equal or below the ones indicated in the RAB Parameters IE.

>>Extended Alternative Maximum Bit Rates

C – ifValueRangeorDiscreteValuesMBR

1 to <nrb-Alternative Values>

For Value Range, one value limit is given here and the other given by Extended Maximum Bit Rate in the RAB Parameters IE.

For Discrete Values; 1 to 16 discrete values can be given.

>>>Extended Bit Rate

M

1 to <nbr-SeparateTrafficDirections>

INTEGER (16,000,001..256,000,000)

When nbr-SeparateTrafficDirections is equal to 2, then the Bit Rate attribute for downlink is signalled first, then the Bit Rate attribute for uplink.

>Supported Alternative Maximum Bit Rate Information

O

Included only if negotiation is allowed for this IE.

EACH

reject

>>Type of Supported Alternative Maximum Bit Rate Information

M

ENUMERATED (Unspecified, Value range, Discrete values,…)

Unspecified means that negotiation is allowed, but no alternative values are provided from the CN, i.e., the RNC is allowed to assign any value equal or below the ones indicated in the RAB Parameters IE.

–

>>Supported Alternative Maximum Bit Rates

C – ifValueRangeorDiscreteValuesGBR

1 to <nrb-Alternative Values>

For Value Range, one value limit is given here and the other given by Supported Maximum Bit Rate in the RAB Parameters IE.

For Discrete Values; 1 to 16 discrete values can be given.

–

>>>Supported Bit Rate

1 to <nbr-SeparateTrafficDirections>

INTEGER (1..1,000,000,000,…)

When nbr-SeparateTrafficDirections is equal to 2, then the Supported Bit Rate attribute for downlink is signalled first, then the Supported Bit Rate attribute for uplink.

–

>Supported Alternative Guaranteed Bit Rate Information

O

Included only if negotiation is allowed for this IE.

EACH

reject

>>Type of Supported Alternative Guaranteed Bit Rate Information

M

ENUMERATED (Unspecified, Value range, Discrete values,…)

Unspecified means that negotiation is allowed, but no alternative values are provided from the CN, i.e., the RNC is allowed to assign any value equal or below the ones indicated in the RAB Parameters IE.

–

>>Supported Alternative Guaranteed Bit Rates

C – ifValueRangeorDiscreteValuesGBR

1 to <nrb-Alternative Values>

For Value Range, one value limit is given here and the other given by Supported Guaranteed Bit Rate in the RAB Parameters IE.

For Discrete Values; 1 to 16 discrete values can be given.

–

>>>Supported Bit Rate

1 to <nbr-SeparateTrafficDirections>

INTEGER (1..1,000,000,000,…)

When nbr-SeparateTrafficDirections is equal to 2, then the Supported Bit Rate attribute for downlink is signalled first, then the Supported Bit Rate attribute for uplink.

–

nbr-AlternativeValues

Maximum number of alternative values.

Value is 1 in case of Value Range and

16 in case of Discrete Values.

nbr-SeparateTrafficDirections

Number of Traffic Directions being signalled separately.

Set to 2 if RAB asymmetry indicator is asymmetric bidirectional.

Set to 1 in all other cases.

ifValueRangeorDiscreteValuesMBR

This IE shall be present if the Type of Alternative Maximum Bit Rates Information IE is set to "Value range" or "Discrete values".

ifValueRangeorDiscreteValuesGBR

This IE shall be present if the Type of Guaranteed Bit Rates Information IE is set to "Value range" or "Discrete values".

>Assigned Maximum Bit Rate

O

1 to <nbr-SeparateTrafficDirections>

INTEGER (1..16,000,000)

When nbr-SeparateTrafficDirections is equal to 2, then Assigned Maximum Bit Rate attribute for downlink is signalled first, then Assigned Maximum Bit Rate attribute for uplink.

–

>Assigned Guaranteed Bit Rate

O

1 to <nbr-SeparateTrafficDirections>

INTEGER (0..16,000,000)

When nbr-SeparateTrafficDirections is equal to 2, then Assigned Guaranteed Bit Rate for downlink is signalled first, then Assigned Guaranteed Bit Rate for uplink.

–

>Extended Assigned Maximum Bit Rate

O

1 to <nbr-SeparateTrafficDirections>

INTEGER (16,000,001..256,000,000)

When nbr-SeparateTrafficDirections is equal to 2, then Assigned Maximum Bit Rate attribute for downlink is signalled first, then Assigned Maximum Bit Rate attribute for uplink.

YES

reject

>Extended Assigned Guaranteed Bit Rate

O

1 to <nbr-SeparateTrafficDirections>

INTEGER (16,000,001..256,000,000)

When nbr-SeparateTrafficDirections is equal to 2, then Assigned Guaranteed Bit Rate for downlink is signalled first, then Assigned Guaranteed Bit Rate for uplink.

YES

reject

>Supported Assigned Maximum Bit Rate

O

0 to <nbr-SeparateTrafficDirections>

INTEGER (1..1,000,000,000, …)

When nbr-SeparateTrafficDirections is equal to 2, then Supported Assigned Maximum Bit Rate attribute for downlink is signalled first, then Supported Assigned Maximum Bit Rate attribute for uplink.

YES

ignore

>Supported Assigned Guaranteed Bit Rate

O

0 to <nbr-SeparateTrafficDirections>

INTEGER (1..1,000,000,000, …)

When nbr-SeparateTrafficDirections is equal to 2, then Supported Assigned Guaranteed Bit Rate for downlink is signalled first, then Supported Assigned Guaranteed Bit Rate for uplink.

YES

ignore

nbr-SeparateTrafficDirections

Number of Traffic Directions being signalled separately.

Set to 2 if RAB asymmetry indicator is asymmetric bidirectional.

Set to 1 in all other cases.

>Requested Maximum Bit Rate

O

1 to <nbr-SeparateTrafficDirections>

INTEGER (1..16,000,000)

When nbr-SeparateTrafficDirections is equal to 2, Requested Maximum Bit Rate attribute for downlink is signalled first, then Requested Maximum Bit Rate attribute for uplink.

–

>Requested Guaranteed Bit Rate

O

1 to <nbr-SeparateTrafficDirections>

INTEGER (0..16,000,000)

When nbr-SeparateTrafficDirections is equal to 2, Requested Guaranteed Bit Rate for downlink is signalled first, then Requested Guaranteed Bit Rate for uplink.

–

>Alternative RAB Configuration Request

O

ENUMERATED (Alternative RAB configuration Requested, …)

Indicates a request to trigger the execution of the alternative RAB Configuration e.g. for network-initiated SCUDIF purpose TS 23.172 [43].

YES

ignore

>Extended Requested Maximum Bit Rate

O

1 to <nbr-SeparateTrafficDirections>

INTEGER (16,000,001..256,000,000)

When nbr-SeparateTrafficDirections is equal to 2, Requested Maximum Bit Rate attribute for downlink is signalled first, then Requested Maximum Bit Rate attribute for uplink.

YES

reject

>Extended Requested Guaranteed Bit Rate

O

1 to <nbr-SeparateTrafficDirections>

INTEGER (16,000,001..256,000,000)

When nbr-SeparateTrafficDirections is equal to 2, Requested Guaranteed Bit Rate for downlink is signalled first, then Requested Guaranteed Bit Rate for uplink.

YES

reject

>Supported Requested Maximum Bit Rate

O

0 to <nbr-SeparateTrafficDirections>

INTEGER (1..1,000,000,000, …)

When nbr-SeparateTrafficDirections is equal to 2, Supported Requested Maximum Bit Rate attribute for downlink is signalled first, then Supported Requested Maximum Bit Rate attribute for uplink.

YES

reject

>Supported Requested Guaranteed Bit Rate

O

0 to <nbr-SeparateTrafficDirections>

INTEGER (1..1,000,000,000, …)

When nbr-SeparateTrafficDirections is equal to 2, Supported Requested Guaranteed Bit Rate for downlink is signalled first, then Supported Requested Guaranteed Bit Rate for uplink.

YES

reject

nbr-SeparateTrafficDirections

Number of Traffic Directions being signalled separately.

Set to 2 if RAB Asymmetry Indicator is asymmetric bidirectional.

Set to 1 in all other cases.

PLMN identity

M

9.2.3.55

CN-ID

M

INTEGER (0..4095)

Vertical Accuracy Code

M

INTEGER
(0..127)

The requested accuracy "v" is derived from the "accuracy code" k by

v = 45x(1.025^k-1).

Response Time

M

ENUMERATED (Low Delay, Delay Tolerant, …)

The value refers to TS 22.071 [30].

Positioning Priority

M

ENUMERATED(High Priority, Normal Priority, …)

The value refers to TS 22.071 [30].

Client Type

M

ENUMERATED(Emergency Services, Value Added Services, PLMN Operator Services, Lawful Intercept Services, PLMN Operator – broadcast services, PLMN Operator – O&M, PLMN Operator – anonymous statistics, PLMN Operator – Target MS service support, …)

Identifies the type of client.

New BSS To Old BSS Information

M

OCTET STRING

Contents defined in TS 48.008 [11].

Downlink Cell Load Information

O

Cell Load Information 9.2.1.49

For the Downlink.

Uplink Cell Load Information

O

Cell Load Information 9.2.1.49

For the Uplink.

Cell Capacity Class Value

M

9.2.1.50

Load Value

M

9.2.1.51

RT Load Value

O

9.2.1.52

NRT Load Information Value

O

9.2.1.53

Cell Capacity Class Value

M

INTEGER (1..100,…)

Value 1 shall indicate the minimum cell capacity, and 100 shall indicate the maximum cell capacity. There should be linear relation between cell capacity and Cell Capacity Class Value.

Load Value

M

INTEGER (0..100)

Value 0 shall indicate the minimum load, and 100 shall indicate the maximum load. Load Value should be measured on a linear scale.

RT Load Value

M

INTEGER (0..100)

NRT Load Information Value

M

INTEGER (0..3)

Mapping of the status:

0: low: The NRT load is low.

1: medium: The NRT load is medium.

2: high: NRT load is high. Probability to admit a new user is low.

3: overloaded: NRT overload. The probability to admit a new user is low, packets are discarded and the source is recommended to reduce the data flow.

RRC Container

M

OCTET STRING

Information Transfer ID

M

INTEGER (0..2^20-1)

Choice Provided Data

>SNA

>>Shared Network Information

M

9.2.3.23

GERAN Classmark

M

OCTET STRING

Contents defined in TS 48.008 [11].

GERAN BSC Container

M

OCTET STRING

Contents defined in TS 48.008 [11].

UESBI-IuA

O

BIT STRING (SIZE(1..128))

The UESBI-IuA provides either compliance status information about the UE with regards to specific behaviours described in TR 25.994 [31] or a bit string length 64 containing IMEISV. Length 64 is reserved for IMEISV other bit string lengths may be used for UESBI.

TR 25.994 [31] defines the mapping between the descriptions in TR 25.994 [31] and the UESBI-IuA.

Each bit on a certain position is associated with a certain behaviour described in TR 25.994 [31].

UESBI-IuB

O

BIT STRING (SIZE(1..128))

The UESBI-IuB provides compliance status information about the UE with regards to specific behaviours described in TR 25.995 [32].

TR 25.995 [32] defines the mapping between the descriptions in TR 25.995 [32] and the UESBI-IuB.

Each bit on a certain position is associated with a certain behaviour described in TR 25.995 [32].

Source Cell Identifier

M

9.2.1.61

The source cell identifier the downlink and uplink cell load information correspond to.

Downlink Cell Load Information

O

Cell Load Information 9.2.1.49

For the Downlink.

Uplink Cell Load Information

O

Cell Load Information 9.2.1.49

For the Uplink.

Choice Source Cell Identifier

>UTRAN

>>UTRAN Source Cell ID

M

>>>PLMN identity

M

9.2.3.55

>>>Source Cell ID

M

INTEGER (0..268435455)

This information element identifies a cell uniquely within UTRAN and consists of RNC-ID and C-ID as defined in TS 25.401 [3].

>GERAN

>>GERAN Source Cell ID

M

>>>PLMN identity

M

9.2.3.55

>>>LAC

M

OCTET STRING (SIZE(2))

0000 and FFFE not allowed.

>>>CI

M

OCTET STRING (SIZE(2))

Choice Inter-system Information Transfer Type

>RIM

>>RIM Transfer

M

9.2.3.30

Choice Information Transfer Type

>RNC Trace

>>RNC Trace Session Information

M

9.2.1.64

Trace Reference

M

9.2.1.8

–

–

Trace Activation Indicator

M

ENUMERATED (

Activated, Deactivated)

–

–

Equipments To Be Traced

C-IfActivated

9.2.1.65

–

–

Trace Recording Session Reference

O

9.2.1.67

YES

ignore

IMSI

O

OCTET STRING (SIZE (3..8))

– digits 0 to 9, encoded 0000 to 1001,

– 1111 used as filler digit,

two digits per octet,

– bit 4 to 1 of octet n encoding digit 2n-1

– bit 8 to 5 of octet n encoding digit 2n

-Number of decimal digits shall be from 6 to 15 starting with the digits from the PLMN identity.

When the IMSI is made of an odd number of digits, the filler digit shall be added at the end to make an even number of digits of length 2N. The filler digit shall then be consequently encoded as bit 8 to 5 of octet N.

YES

ignore

Trace Collection Entity IP Address

O

Transport Layer Address

9.2.2.1

YES

ignore

Serving Cell Identifier

O

UTRAN Cell Identifier

9.2.1.122

Immediate MDT only.

YES

ignore

ifActivated

This IE shall be present if the Trace Activation Indicator IE is set to "Activated".

Choice Equipments To Be Traced

>IMEI List

>>IMEI List

1 to <MaxUEsToBeTraced>

>>>IMEI

M

OCTET STRING (SIZE (8))

– hexadecimal digits 0 to F, two hexadecimal digits per octet,

– each hexadecimal digit encoded 0000 to 1111,

– 1111 used as filler for bits 8 to 5 of last octet

– bit 4 to 1 of octet n encoding digit 2n-1

– bit 8 to 5 of octet n encoding digit 2n

Number of hexadecimal digits shall be 15.

>IMEISV List

>>IMEISV List

1 to <MaxUEsToBeTraced>

>>>IMEISV

M

OCTET STRING (SIZE (8))

– hexadecimal digits 0 to F, two hexadecimal digits per octet,

– each hexadecimal digit encoded 0000 to 1111,

– bit 4 to 1 of octet n encoding digit 2n-1

– bit 8 to 5 of octet n encoding digit 2n

Number of hexadecimal digits shall be 16.

>IMEI Group

>>IMEI

M

OCTET STRING (SIZE (8))

– hexadecimal digits 0 to F, two hexadecimal digits per octet,

– each hexadecimal digit encoded 0000 to 1111,

– 1111 used as filler for bits 8 to 5 of last octet

– bit 4 to 1 of octet n encoding digit 2n-1

– bit 8 to 5 of octet n encoding digit 2n

Number of hexadecimal digits shall be 15.

>>IMEI Mask

M

BIT STRING (SIZE (7))

>IMEISV Group

>>IMEISV

M

OCTET STRING (SIZE (8))

– hexadecimal digits 0 to F, two hexadecimal digits per octet,

– each hexadecimal digit encoded 0000 to 1111,

– bit 4 to 1 of octet n encoding digit 2n-1

– bit 8 to 5 of octet n encoding digit 2n

Number of hexadecimal digits shall be 16.

>>IMEISV Mask

BIT STRING (SIZE (8))

MaxUEsToBeTraced

Maximum number of UEs To Be Traced by the RNC in a Trace Session. Value is 64.

Trace Reference

M

9.2.1.8

Trace Recording Session Reference

M

9.2.1.67

Trace Recording Session Reference

M

INTEGER (0..65535)

Trace Recording Session Reference

M

9.2.1.67

Trace Depth

M

9.2.1.69

List Of Interfaces To Trace

O

9.2.1.70

Trace Depth

M

ENUMERATED(

Minimum,

Medium,

Maximum, …)

See TS 32.422 [38].

List Of Interfaces To Trace

>Interfaces To Trace

1 to <maxInterfaces>

>>Interface

M

ENUMERATED(Iu-CS, Iu-PS,

Iur,

Iub,

Uu, …)

maxInterfaces

Maximum no. of different UTRAN interfaces to trace. The value for maxInterfaces is 16.

Information Exchange ID

M

INTEGER (0..2^20-1)

Information Exchange Type

M

ENUMERATED(transfer,

request, …)

Choice Information Request Type

>MBMS IP MC Address and APN Request

>>MBMS IP Multicast Address and APN Request

M

9.2.1.78

>Permanent NAS UE ID

>>Permanent NAS UE Identity

M

9.2.3.1

Choice Information Requested

>Requested MBMS IP MC Address and APN

>>Requested MBMS IP Multicast Address and APN

M

9.2.3.46

>Requested MC Service List

>>Requested Multicast Service List

M

9.2.3.47

PTP RAB ID

M

BIT STRING (SIZE(8))

Frequency Layer Convergence Flag

M

ENUMERATED(

no-FLC-flag, …)

Session Update ID

M

INTEGER (0..2^20-1)

MBMS IP Multicast Address and APN Request

>TMGI

M

1 to <maxnoofMulticastServicesPerRNC>

9.2.3.37

maxnoofMulticastServicesPerRNC

Maximum no. of Multicast Services that a RNC can have context for. Value is 512.

Source BSS to Target BSS Transparent Container

M

OCTET STRING

Coded as the value (V) part of the Source BSS to Target BSS Transparent Container IE defined in TS 48.018 [36].

Target BSS to Source BSS Transparent Container

M

OCTET STRING

Coded as the value (V) part of the Target BSS to Source BSS Transparent Container IE defined in TS 48.018 [36].

Include Velocity

M

ENUMERATED(requested)

Reporting Amount

M

INTEGER(1.. 8639999,…)

This IE indicates the amount of periodic reports.

Reporting Interval

M

INTEGER(1.. 8639999,…)

This IE indicates the reporting interval in seconds.

UTRAN Cell ID

1

–

>PLMN identity

M

9.2.3.55

–

>Cell ID

M

INTEGER (0..268435455)

This information element identifies a cell uniquely within UTRAN and consists of RNC-ID and C-ID as defined in TS 25.401 [3].

–

Cell Type

M

ENUMERATED(macro, micro, pico, femto, …)

Defined in TS 25.104 [50].

–

Time UE Stayed In Cell

M

INTEGER (0..4095)

The duration of the time the UE stayed in the cell in seconds. If the UE stays in a cell more than 4095s, this IE is set to 4095.

–

Time UE stayed in Cell Enhanced Granularity

O

INTEGER (0..40950)

The duration of the time the UE stayed in the cell in 1/10 seconds. If the UE stays in a cell more than 4095s, this IE is set to 40950.

YES

ignore

HO Cause Value

O

Cause

9.2.1.4

The cause for the outgoing relocation.

YES

ignore

MBMS HC Indicator

M

ENUMERATED (uncompressed header, compressed header, …)

CSG Id

M

BIT STRING (SIZE (27))

Subscriber Profile ID for RAT/Frequency Priority

M

INTEGER (1..256)

SRVCC operation possible

M

ENUMERATED
(SRVCC possible,…)

SRVCC HO Indication

M

ENUMERATED
(PS and CS, CS only,…)

SRVCC Information

>NONCE

M

BIT STRING (SIZE(128))

The usage of NONCE IE is described in TS 33.102 [60].

E-UTRAN Service Handover

M

ENUMERATED (Handover to E-UTRAN shall not be performed, …)

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.

CSG Membership Status

M

ENUMERATED (member, non-member,…)

Cell Access Mode

M

ENUMERATED (hybrid,…)

Access Point Name

M

OCTET STRING (SIZE(1..255))

This IE indicates the Access Point Name of the RAB to be offloaded. Defined in TS 23.003 [19].

Charging Characteristics

M

OCTET STRING (SIZE(2))

This IE indicates the charging characteristics of the RAB to be offloaded. Defined in TS 29.060 [57].

MSISDN

M

OCTET STRING (SIZE (1..9))

Coded as the MSISDN IE, as defined in TS 29.002 [24].

RSRP

O

INTEGER (0..97)

Threshold of RSRP.

–

–

RSRQ

O

INTEGER (0..34)

Threshold of RSRQ.

–

–

IRAT Measurement Parameters

M

–

–

>Measurement Duration

M

INTEGER

(1..100)

The period of time following the successful IRAT handover, during which the target RAT instructs the UE to measure cells of the source RAT. Unit: [second].

–

–

>E-UTRA frequencies

0 to <maxnoofEUTRAFreqs>

If present, designates the specific E-UTRAN frequencies which the target RAT may instruct the UE to measure.

–

–

>>E-ARFCN

M

INTEGER (0..65535)

EARFCN of the downlink carrier frequency TS 36.101 [58].

–

–

>>Measurement Bandwidth

O

ENUMERATED(6,15,25,50,75,100)

Measurement bandwidth of the carrier frequency as defined in TS 25.331 [10].

–

–

>>E-ARFCN-Extended

O

INTEGER (65536..262143, …)

EARFCN of the downlink carrier frequency TS 36.101 [58]. If this IE is present, the value signalled in the IE “E-ARFCN” is ignored.

YES

reject

RSRQ Type

O

YES

ignore

>All Symbols

M

BOOLEAN

TRUE indicates use of all OFDM symbols when performing RSRQ measurements.

–

–

>Wide band

M

BOOLEAN

TRUE indicates use of a wider bandwidth when performing RSRQ measurements.

–

–

RSRQ Extension

O

INTEGER (-30..46, …)

YES

ignore

maxnoofEUTRAFreqs

Maximum no of EUTRA centre frequencies to measure

MDT Activation

M

ENUMERATED(Immediate MDT only, Logged MDT only, Immediate MDT and Trace, …)

–

–

CHOICE MDT Area Scope

M

–

–

>Cell Based

–

–

>>Cell ID List

1 to <maxnoofCellID>

–

–

>>>Cell-ID

M

INTEGER (0..268435455)

This information element identifies a cell uniquely within UTRAN and consists of RNC-ID and C-ID as defined in TS 25.401 [3].

The Cell is derived using the current serving PLMN.

–

–

>LA Based

–

–

>>LAI List

1 to <maxnoofLAIs>

–

–

>>>LAI

M

9.2.3.6

–

–

>RA Based

–

–

>>RAI List

1 to <maxnoofRAIs>

–

–

>>>RAI

This element identifies an area in which the MDT Configuration applies.

–

–

>>>>LAI

M

9.2.3.6

–

–

>>>>RAC

M

9.2.3.7

–

–

>PLMN Area Based

NULL

–

–

CHOICE MDT mode

–

–

>immediate MDT

–

–

>>Measurements to Activate

M

BITSTRING

(SIZE(8))

Each position in the bitmap indicates a MDT measurement, as defined in TS 37.320 [64].

First Bit = M1,

Second Bit = M2,

Third Bit = M3,

Fourth Bit = M4,

Fifth Bit = M5,

Sixth Bit = M6

Seventh Bit = M7.

Eighth bit = logging of M1 or M2 from event triggered measurement reports according to existing RRM configuration [31].

Value ‘1’ indicates “activate” and value ‘0’ indicates “do not activate”.

–

–

>>M1 Report

C-ifM1

9.2.1.98

M1: FDD only: CPICH RSCP and CPICH Ec/No measurement by UE.

–

–

>>M2 Report

C-ifM2

9.2.1.99

M2: TDD only: P-CCPCH RSCP and Timeslot ISCP for UTRA 1.28 TDD.

–

–

>>M4 Report

C-ifM4

9.2.1.117

M4: UPH measurement by UE.

YES

ignore

>>M5 Report

C-ifM5

9.2.1.118

M5: RTWP measurement by NodeB.

YES

ignore

>>M6 Report

C-ifM6

9.2.1.119

M6: Data volume measurement by RNC.

YES

ignore

>>M7 Report

C-ifM7

9.2.1.120

M7: Throughput measurement by RNC.

YES

ignore

>logged MDT

–

–

>>logging interval

M

ENUMERATED (1.28, 2.56, 5.12,10.24,20.48, 30.72, 40.96 and 61.44, …)

The unit of this IE is second. This IE is defined in TS 25.331[10].

–

–

>>logging duration

M

ENUMERATED (10, 20, 40, 60, 90 and 120, …)

The unit of this IE is minute. This IE is defined in TS 25.331[10].

–

–

Signalling based MDT PLMN List

MDT PLMN List

9.2.1.116

YES

ignore

maxnoofCellID

Maximum no. of Cell ID subject for MDT scope. Value is 32.

maxnoofLAIs

Maximum no. of LAI subject for MDT scope. Value is 8.

maxnoofRAIs

Maximum no of RAI subject for MDT scope. Value is 8.

ifM1

This IE shall be present if the Measurements to Activate IE has the first bit set to “1”.

ifM2

This IE shall be present if the Measurements to Activate IE has the second bit set to “1”.

ifM4

This IE shall be present if the Measurements to Activate IE has the fourth bit set to “1”.

ifM5

This IE shall be present if the Measurements to Activate IE has the fifth bit set to “1”.

ifM6

This IE shall be present if the Measurements to Activate IE has the sixth bit set to “1”.

ifM7

This IE shall be present if the Measurements to Activate IE has the seventh bit set to “1”.

CHOICE M1 Report trigger

>Periodic

>>MDT Report Parameters

M

9.2.1.100

>event1F

>>Measurement quantity

M

ENUMERATED(

CPICH Ec/N0,

CPICH RSCP,

pathloss, …)

>>threshold

M

INTEGER(-120..165)

Range used depends on

measurement quantity.

CPICH RSCP -120..-25

dBm

CPICH Ec/No -24..0 dB

Pathloss 30..165dB

CHOICE M2 Report trigger

>Periodic

>>MDT Report Parameters

M

9.2.1.100

>Event1I

>>threshold

M

INTEGER(-120..-25)

Report interval

M

ENUMERATED ( ms250, ms500, ms1000, ms2000, ms3000, ms4000, ms6000, ms12000, ms16000, ms20000, ms24000, ms32000, ms64000, …, ms8000, ms28000)

This IE is defined in TS 25.331[10].

Report amount

M

ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity, …)

RAB Parameters List

O

9.2.1.102

Location Reporting Transfer Information

O

9.2.1.105

Trace Information

O

9.2.1.106

Source SAI

O

SAI

9.2.3.9

maxnoofRABs

Maximum no. of RABs for one UE. Value is 256.

Relocation Parameters List

1 to <maxnoofRABs>

>RAB ID

M

9.2.1.2

>CN Domain Indicator

M

9.2.1.5

>RAB Data Volume Report

O

9.2.1.103

>UP Information

O

9.2.1.104

RAB Data Volume Report

>RAB Data Volume Report Item IEs

1 to <maxnoofVol>

>>Unsuccessfully Transmitted DL Data Volume

M

Unsuccessfully transmitted data volume

9.2.3.12

>>Data Volume Reference

O

9.2.3.13

maxnoofVol

Maximum no. of reported data volume for one RAB. Value is 2.

Frame Sequence Number UL

M

Frame Sequence Number

9.2.1.107

–

–

Frame Sequence Number DL

M

Frame Sequence Number

9.2.1.107

–

–

PDU Type 14 Frame Sequence Number UL