RAB Assignment Requestawilkinson/prof/UMTS/rabassign.pdf · 8.2 RAB Assignment 8 ... - should be...

3GPP TS 25.413 v3.5.0 (2001-3) CR page 1

RAB Assignment TS25.413v3.6.0 (2001-6)

RANAP Protocol

Jump straight to RAB ASSIGNMENT message

8.2 RAB Assignment

8.2.1 General The purpose of the RAB Assignment procedure is to establish new RABs and/or to enable modifications and/or releases of already established RABs for a given UE. The procedure uses connection oriented signalling.

8.2.2 Successful Operation

CN

RAB ASSIGNMENTREQUEST

RAB ASSIGNMENTRESPONSE

RNC

.

.

.*

* it can be several responses

Figure 1: RAB Assignment procedure. Successful operation.

The CN shall initiate the procedure by sending a RAB ASSIGNMENT REQUEST message. When sending the RAB ASSIGNMENT REQUEST message, the CN shall start the T RABAssgt timer.

The CN may request UTRAN to:

- establish,

- modify,

- release

one or several RABs with one RAB ASSIGNMENT REQUEST message.

The message shall contain the information required by the UTRAN to build the new RAB configuration, such as:

- list of RABs to establish or modify with their bearer characteristics;

- list of RABs to release.

3GPP TS 25.413 v3.5.0 (2001-3) CR page 2

For each RAB requested to establish, the message shall contain:

- RAB ID.

- RAB parameters (including e.g. Allocation/Retention Priority).

- User Plane Mode Information (i e User Plane Mode and UP Mode Versions).

- Transport Layer Address.

- Iu Transport Association.

- PDP Type Information (only for PS)

- Data Volume Reporting Indication (only for PS).

- DL GTP-PDU sequence number (only when GTP-PDU sequence number is available in cases of handover from GPRS to UMTS or when establishing a RAB for an existing PDP context).

- UL GTP-PDU sequence number (only when GTP-PDU sequence number is available in cases of handover from GPRS to UMTS or when establishing a RAB for an existing PDP context).

- DL N-PDU sequence number (only when N-PDU sequence number is available in case of handover from GPRS to UMTS).

- UL N-PDU sequence number (only when N-PDU sequence number is available in case of handover from GPRS to UMTS).

For each RAB requested to modify, the message may contain:

- RAB ID (mandatory).

- NAS Synchronisation Indicator.

- RAB parameters.

- Transport Layer Address.

- Iu Transport Association.

For each RAB request to release, the message shall contain:

- RAB ID.

- Cause.

Upon reception of the RAB ASSIGNMENT REQUEST message UTRAN shall execute the requested RAB configuration.

The RAB ID shall identify uniquely the RAB for the specific CN domain for the particular UE, which makes the RAB ID unique over the Iu connection on which the RAB ASSIGNMENT REQUEST message is received. When a RAB ID already in use over that particular Iu instance is used, the procedure is considered as modification of that RAB.

The RNC shall pass the contents of RAB ID IE to the radio interface protocol for each RAB requested to establish or modify.

The RNC shall establish or modify the resources according to the values of the Allocation/Retention Priority IE (priority level, pre-emption indicators, queuing) and the resource situation as follows:

- The RNC shall consider the priority level of the requested RAB, when deciding on the resource allocation.

- If the requested RAB is allowed for queuing and the resource situation so requires, RNC may place the RAB in the establishment queue.

- The priority levels and the pre-emption indicators may (singularly or in combination) be used to determine whether the RAB assignment has to be performed unconditionally and immediately. If the requested RAB is marked as "may trigger pre-emption" and the resource situation so requires, RNC may trigger the pre-emption procedure which may then cause the forced release of a lower priority RAB which is marked as "pre-emptable".

3GPP TS 25.413 v3.5.0 (2001-3) CR page 3

Whilst the process and the extent of the pre-emption procedure is operator dependent, the pre-emption indicators, if given in the RAB ASSIGNMENT REQUEST message, shall be treated as follows:

1. The values of the last received Pre-emption Vulnerability IE and Priority Level IE shall prevail.

2. If the Pre-emption Capability IE is set to "may trigger pre-emption", then this allocation request may trigger the pre-emption procedure.

3. If the Pre-emption Capability IE is set to "shall not trigger pre-emption", then this allocation request shall not trigger the pre-emption procedure.

4. If the Pre-emption Vulnerability IE is set to "pre-emptable", then this connection shall be included in the pre-emption process.

5. If the Pre-emption Vulnerability IE is set to "not pre-emptable", then this connection shall not be included in the pre-emption process.

6. If the Priority Level IE is set to "no priority used" the given values for the Pre-emption Capability IE and Pre-emption Vulnerability IE shall not be considered. Instead the values "shall not trigger pre-emption" and "not pre-emptable" shall prevail.

- If the Allocation/Retention Priority IE is not given in the RAB ASSIGNMENT REQUEST message, the allocation request shall not trigger the pre-emption process and the connection may be pre-empted and considered to have the value "lowest" as priority level. Moreover, queuing shall not be allowed.

- The UTRAN pre-emption process shall keep the following rules:

1. UTRAN shall only pre-empt RABs with lower priority, in ascending order of priority.

2. The pre-emption may be done for RABs belonging to the same UE or to other UEs.

If the NAS Synchronisation Indicator IE is contained in the RAB ASSIGNMENT REQUEST message, the RNC shall pass it to the radio interface protocol for the transfer to the UE.

If the RAB ASSIGNMENT REQUEST message includes the PDP Type Information IE, the UTRAN may use this to configure any compression algorithms.

If the Service Handover IE is included, this tells if the RAB

- should be handed over to GSM, i.e. from NAS point of view, the RAB should be handed over to GSM as soon as possible although the final decision whether to perform a handover to GSM is still made in UTRAN.

- should not be handed over to GSM, i.e. from NAS point of view, the RAB should remain in UMTS as long as possible although the final decision whether to perform a handover to GSM is still made in UTRAN.

- shall not be handed over to GSM, i.e. the RAB shall never be handed over to GSM. This means that UTRAN shall not initiate handover to GSM for the UE unless the RABs with this indication have first been released with the normal release procedures.

The value of the Service Handover IE is valid throughout the lifetime of the RAB or until changed by a RAB modification.

The Service Handover IE shall only influence decisions made regarding UTRAN initiated handovers.

If the Service Handover IE is not included, the decision whether to perform a handover to GSM is only an internal UTRAN matter.

UTRAN shall report to CN, in the first RAB ASSIGNMENT RESPONSE message, the result for all the requested RABs, such as:

- List of RABs successfully established or modified.

- List of RABs released.

- List of RABs queued.

- List of RABs failed to establish or modify.

3GPP TS 25.413 v3.5.0 (2001-3) CR page 4

- List of RABs failed to release.

UTRAN shall report the outcome of a specific RAB to establish or modify only after the transport network control plane signalling, which is needed for RAB establishment or modification, has been executed. The transport network control plane signalling shall use the Transport Layer Address IE and Iu Transport Association IE. At a RAB modification, it is up to the RNC to decide if any transport network control plane signalling shall be performed for the possibly included Transport Layer Address IE and Iu Transport Association IE or if the already existing transport bearer shall be used. If the RNC decides to establish a new transport bearer, then the switch over to this new transport bearer shall be done immediately after transport bearer establishment and initialisation of the user plane mode.

Before reporting the outcome of a specific RAB to establish or modify, the RNC shall have executed the initialisation of the user plane mode as requested by the CN in the User Plane Mode IE. This initialisation is described in ref.[6].

In case of establishment of a RAB for the PS domain, the CN must be prepared to receive user data before the RAB ASSIGNMENT RESPONSE message has been received.

If none of the RABs have been queued, the CN shall stop timer T RABAssgt. And the RAB Assignment procedure terminates. In that case, the procedure shall also be terminated in UTRAN.

When the request to establish or modify one or several RABs is put in the queue, UTRAN shall start the timer TQUEUING. This timer specifies the maximum time for queuing of the request of establishment or modification. The same timer TQUEUING is supervising all RABs being queued.

For each RAB that is queued the following outcomes shall be possible:

- successfully established or modified;

- failed to establish or modify;

- failed due to expiry of the timer TQUEUING.

For the queued RABs, indicated in the first RAB ASSIGNMENT RESPONSE message, UTRAN shall report the outcome of the queuing for every RAB individually or for several RABs in subsequent RAB ASSIGNMENT RESPONSE message(s). This is left to implementation. UTRAN shall stop TQUEUING when all RABs have been either successfully established or modified or failed to establish or modify. The RAB Assignment procedure is then terminated both in CN and UTRAN when all RABs have been responded to.

When CN receives the response that one or several RABs are queued, CN shall expect UTRAN to provide the outcome of the queuing function for each RAB before expiry of the T RABAssgt timer. In case the timer T RABAssgt expires, the CN shall consider the RAB Assignment procedure terminated and the RABs not reported shall be considered as failed.

In the case the timer TQUEUING expires, the RAB Assignment procedure terminates in UTRAN for all queued RABs, and UTRAN shall respond for all of them in one RAB ASSIGNMENT RESPONSE message. The RAB Assignment procedure shall also be terminated in CN.

In case a request to modify or release a RAB contains the RAB ID of a RAB being queued, the RAB shall be taken out of the queue and treated according to the second request. The first request shall be responded to as a RAB failed to setup or modify with the cause value "Request superseded".

When UTRAN reports unsuccessful establishment/modification of a RAB, the cause value should be precise enough to enable the core network to know the reason for unsuccessful establishment/modification. Typical cause values are: "Requested Traffic Class not Available", "Invalid RAB Parameters Value", "Requested Maximum Bit Rate not Available", "Requested Maximum Bit Rate for DL not Available", "Requested Maximum Bit Rate for UL not Available", "Requested Guaranteed Bit Rate not Available", "Requested Guaranteed Bit Rate for DL not Available", "Requested Guaranteed Bit Rate for UL not Available", "Requested Transfer Delay not Achievable", "Invalid RAB Parameters Combination", "Condition Violation for SDU Parameters", "Condition Violation for Traffic Handling Priority", "Condition Violation for Guaranteed Bit Rate", "User Plane Versions not Supported", "Iu UP Failure", “Iu Transport Connection Failed to Establish”.

If the RAB ID of a RAB requested to be released is unknown in the RNC, this shall be reported as a RAB failed to release with the cause value "Invalid RAB ID".

The RNC may indicate an impending directed retry attempt to GSM by sending RAB ASSIGNMENT RESPONSE message with a RAB ID included in the list of RABs failed to setup and a cause value of “Directed Retry”.

3GPP TS 25.413 v3.5.0 (2001-3) CR page 5

The RNC shall be prepared to receive a RAB ASSIGNMENT REQUEST message containing a RABs To Be Released IE at any time and shall always reply to it. If there is an ongoing RAB Assignment procedure for a RAB indicated within the RABs To Be Released IE, the RNC shall discard the preceding RAB Assignment procedure for that specific RAB, release any related resources and report the released RAB within the RAB ASSIGNMENT RESPONSE message.

After sending RAB ASSIGNMENT RESPONSE message containing RAB ID within the RABs Released IE, the RNC shall be prepared to receive new establishment request of a RAB identified by the same RAB ID

8.2.3 Unsuccessful Operation The unsuccessful operation for this Class 3 Elementary procedure is described under the Successful Operation chapter.

8.2.4 Abnormal Conditions

Interactions with Relocation Preparation procedure:

If the relocation becomes necessary during the RAB Assignment procedure, the RNC may interrupt the ongoing RAB Assignment procedure and initiate the Relocation Preparation procedure as follows:

1. The RNC shall terminate the RAB Assignment procedure indicating unsuccessful RAB configuration modification:

- for all queued RABs;

- for RABs not already established or modified, and

- for RABs not already released;

with the cause "Relocation triggered".

2. The RNC shall terminate the RAB Assignment procedure indicating successful RAB configuration modification:

- for RABs already established or modified but not yet reported to the CN, and

- for RABs already released but not yet reported to the CN.

3. The RNC shall report this outcome of the procedure in one RAB ASSIGNMENT RESPONSE message.

4. The RNC shall invoke relocation by sending the RELOCATION REQUIRED message to the active CN node(s).

5. The CN shall terminate the RAB Assignment procedure at reception of the RAB ASSIGNMENT RESPONSE message.

Directed retry from UMTS to GSM (CS domain only):

In the case where the RNC has no RAB configuration for a particular UE in the CS domain, and the RNC receives a RAB ASSIGNMENT REQUEST message for that UE requesting the establishment of one RAB only, a directed retry to GSM may be initiated. In this case the RNC may interrupt the ongoing RAB Assignment procedure and initiate the Relocation Preparation procedure as follows:

1. The RNC shall terminate the RAB Assignment procedure indicating unsuccessful RAB configuration modification of that RAB with the cause "Directed retry".

2. The RNC shall report this outcome of the procedure in one RAB ASSIGNMENT RESPONSE message.

3. The RNC shall invoke relocation by sending the RELOCATION REQUIRED message to the active CN node, with the cause "Directed Retry".

4. The CN shall terminate the RAB Assignment procedure at reception of the RAB ASSIGNMENT RESPONSE message

3GPP TS 25.413 v3.5.0 (2001-3) CR page 6

9 Elements for RANAP Communication

9.1 Message Functional Definition and Content

9.1.1 General Section 9.1 presents the contents of RANAP messages in tabular format. The corresponding ASN.1 definition is presented in section 9.3. In case there is contradiction between the tabular format in section 9.1 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, where the tabular format shall take precedence.

NOTE: The messages have been defined in accordance to the guidelines specified in [18].

3GPP TS 25.413 v3.5.0 (2001-3) CR page 7

9.1.2 Message Contents

9.1.2.1 Presence

All information elements in the message descriptions below are marked mandatory, optional or conditional according to the following table:

Table 4: Meaning of abbreviations used in RANAP messages

Abbreviation Meaning M IEs marked as Mandatory (M) will always be included in the

message. O IEs marked as Optional (O) may or may not be included in the

message. C IEs marked as Conditional (C) will be included in a message only if

the condition is satisfied. Otherwise the IE is not included.

9.1.2.2 Criticality

Each Information Element or Group of Information Elements may have criticality information applied to it. Following cases are possible:

Table 5: Meaning of content within “Criticality” column

Abbreviation Meaning

– No criticality information is applied explicitly. YES Criticality information is applied. This is usable only for non-

repeatable IEs GLOBAL The IE and all its repetitions together have one common criticality

information. This is usable only for repeatable IEs. EACH Each repetition of the IE has its own criticality information. It is not

allowed to assign different criticality values to the repetitions. This is usable only for repeatable IEs.

9.1.2.3 Range

The Range column indicates the allowed number of copies of repetitive IEs/IE groups.

9.1.2.4 Assigned Criticality

This column provides the actual criticality information as defined in chapter 10.3.2, if applicable.

9.1.3 RAB ASSIGNMENT REQUEST back This message is sent by the CN to request the establishment, modification or release of one or more RABs for the same UE.

Direction: CN ? RNC.

Signalling bearer mode: Connection oriented.

3GPP TS 25.413 v3.5.0 (2001-3) CR page 8

IE/Group Name Presence Range IE type and reference

Semantics description

Criticality Assigned Criticality

Message Type M 9.2.1.1 YES reject RABs To Be Setup Or Modified List

C – ifNoOtherGroup

YES ignore

>RABs To Be Setup Or Modified Item IEs

1 to <maxnoofRABs>

>>First Setup Or Modify Item

M Grouping reason: same criticality

EACH reject

>>>RAB ID M 9.2.1.2 The same RAB ID must only be present in one group.

-

>>>NAS Synchronisation Indicator

C-ifModifandNASInfoProvided

9.2.3.18 -

>>>RAB Parameters

C - ifSetuporNewValues

9.2.1.3 Includes all necessary parameters for RABs (both for MSC and SGSN) including QoS.

-

>>>User Plane Information

C - ifSetuporNewValues

-

>>>>User Plane Mode

M 9.2.1.18 -

>>>>UP Mode Versions

M 9.2.1.19 -

>>>Transport Layer Information

C- ifNot OnlyNSI

-

>>>>Transport Layer Address

M 9.2.2.1 -

>>>>Iu Transport Association

M 9.2.2.2 -

>>>Service Handover

O 9.2.1.41 -

>>Second Setup Or Modify Item

M Grouping reason: same criticality

EACH ignore

>>> PDP Type Information

C – ifPSandSetup

9.2.1.40 -

>>>Data Volume Reporting Indication

C – ifPSandSetup

9.2.1.17 -

>>>DL GTP-PDU Sequence Number

C- ifAvailPSandSetup

9.2.2.3 -

>>>UL GTP-PDU Sequence Number


9.2.2.4 -

>>>DL N-PDU Sequence Number


9.2.1.33 -

>>>UL N-PDU C- 9.2.1.34 -

3GPP TS 25.413 v3.5.0 (2001-3) CR page 9



Criticality Assigned Criticality

Sequence Number ifAvailPSandSetup

RABs To Be Released List

C – ifNoOtherGroup

YES ignore

>RABs To Be Released Item IEs

1 to <maxnoofRABs>

EACH ignore

>>RAB ID M 9.2.1.2 The same RAB ID must only be present in one group.

-

>>Cause M 9.2.1.4 -

Condition Explanation IfPSandSetup This IE is only present for RABs towards the PS domain at RAB

establishment. IfAvailPSandSetup This IE is only present when available for RABs towards the PS

domain at RAB establishment. IfNoOtherGroup This group must be present at least when no other group is present,

i.e. at least one group must be present. IfModifandNASInfoProvided This IE is present at a RAB modification if the relevant NAS

information is provided by the CN. IfSetuporNewValues This IE or IE group is present at a RAB establishment or when any

previously set value shall be modified at a RAB modification. IfNotOnlyNSI This IE group is present at a RAB establishment, and may be

present at a RAB modification if at least one more IE than the RAB ID IE and the NAS Syncronisation Indicator IE is also included.

Range bound Explanation maxnoofRABs Maximum no. of RABs for one UE. Value is 256.

3GPP TS 25.413 v3.5.0 (2001-3) CR page 10

9.2 Information Element Definitions

9.2.0 General Section 9.2 presents the RANAP IE definitions in tabular format. The corresponding ASN.1 definition is presented in section 9.3. In case there is contradiction between the tabular format in section 9.2 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence.

9.2.1 Radio Network Layer Related IEs

9.2.1.1 Message Type back

Message Type IE uniquely identifies the message being sent. It is mandatory for all messages.

IE/Group Name Presence Range IE type and reference Semantics description Message Type Assumed max no of messages

is 256. >Procedure Code M (RAB Assignment,

RAB Release Request, Iu Release Request, Iu Release, Relocation Preparation, Relocation Resource Allocation, Relocation Detect, Relocation Complete Relocation Cancel, SRNS Context Transfer, SRNS Data Forwarding Initiation, SRNS Context Forwarding from Source RNC to CN, SRNS Context Forwarding to Target RNC from CN, Paging, Common ID, CN Invoke Trace, Security Mode Control, Location Reporting Control Location Report, Data Volume Report, Initial UE Message Direct Transfer, Overload Control, Reset, Error Indication, CN Deactivate Trace, RANAP Relocation Information, Reset Resource, …)

>Type of Message M CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, Outcome,…)

3GPP TS 25.413 v3.5.0 (2001-3) CR page 11

9.2.1.2 RAB ID back

This element uniquely identifies the radio access bearer for a specific CN domain for a particular UE, which makes the RAB ID unique over one Iu connection. The RAB ID shall remain the same for the duration of the RAB even when the RAB is relocated to another Iu connection.

The purpose of the element is to bind data stream from the Non-Access Stratum point of view (e.g. bearer of call or PDP context) and radio access bearer in Access Stratum. The value is also used in the RNC to relate Radio Bearers to a RAB. The content of this information element is transferred unchanged from the CN node (i.e., MSC or SGSN) via RNC to UE by RANAP messages and RRC messages. For RRC messages refer to [10].

The element contains binary representation of either the Stream Identifier (SI) for CS domain or the Network Service Access Point Identifier (NSAPI) for PS domain. These identifiers are coded in the RAB ID element in accordance with the coding of the Stream Identifier IE and with the coding of the NSAPI IE in [8].



RAB ID M BIT STRING (8)

9.2.1.3 RAB Parameters back

The purpose of the RAB parameters IE group and other parameters within the RAB parameters IE group is to indicate all RAB attributes as defined in [7] for both directions.



RAB parameters >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 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

0 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 Usage: 1. When nbr-

SeparateTrafficDirections is equal to 2, then

3GPP TS 25.413 v3.5.0 (2001-3) CR page 12



RAB parameters 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: Set to lowest 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 occurence 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. Usage: -

>Traffic Handling Priority C - iftrafficInteractiv

INTEGER {spare (0), highest (1), lowest (14), no priority used (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:

3GPP TS 25.413 v3.5.0 (2001-3) CR page 13



RAB parameters -

>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 Usage: -

>Relocation Requirement

C-ifPS ENUMERATED (lossless, none, …)

Desc.: This IE specifies in which way the radio access bearer shall be treated in case of relocation Usage: Lossless : lossless relocation is required for this RAB, as defined in [21].

Range Bound Explanation nbr-SeparateTrafficDirection Number of Traffic Directions being signalled

separately. Set to 2 if RAB asymmetry indicator is asymmetric bidirectional. Set to 1 in all other cases.

Range Bound Explanation maxRABSubflows Maximum number of Subflows per RAB. Value

is 7

Condition Explanation IftrafficConv-Stream This IE is only present when traffic class indicates “Conversational”

or “Streaming” IftrafficInteractiv This IE is only present when traffic class indicates “Interactive” IfPS This IE is only present for RABs towards the PS domain.



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

3GPP TS 25.413 v3.5.0 (2001-3) CR page 14

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

>SDU format information Parameter

C - IfPredefinedSDUSize

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 occurence corresponding to RAB Subflow Combination number 1. It shall always be present for rate controllable RABs.

Range Bound Explanation maxRABSubflowCombinations Maximum number of RAB Subflow

Combinations. Value is 64.

Condition Explanation IfErroneousSDU This IE is not present when Delivery Of Erroneous SDU is set to

“no-error-detection-consideration “ IfPredefinedSDUSize This IE shall be present for RABs with pre-defined SDU sizes.

3GPP TS 25.413 v3.5.0 (2001-3) CR page 15



SDU Format Information Parameter

>Subflow SDU Size C-ifalone 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. 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

C-ifalone INTEGER (0..16,000,000)

Desc.: This IE indicates the RAB Subflow Combination bit rate. The unit is: bit/s. Usage: This IE is only present for RABs that have predefined rate controllable bit rates. 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.

Condition Explanation Ifalone At least either of Subflow SDU size IE or RAB Subflow Combination

bit rate IE shall be present when SDU format information parameter is present

3GPP TS 25.413 v3.5.0 (2001-3) CR page 16



Allocation/Retention Priority

>Priority Level M INTEGER {spare (0), highest (1), lowest (14), no priority used (15)} (0..15)

Desc.: This IE indicates the priority of the request. Usage: The priority level and the preemption 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)

Descr.: 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 preemption 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.

9.2.1.4 Cause back

The purpose of the Cause IE is to indicate the reason for a particular event for the RANAP protocol.

3GPP TS 25.413 v3.5.0 (2001-3) CR page 17



Choice Cause >Radio Network Layer

Cause INTEGER

(RAB pre-empted(1),

Trelocoverall Expiry(2),

Trelocprep Expiry(3),

Treloccomplete Expiry(4),

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

Change of Ciphering and/or Integrity Protection is not supported(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

Value range is 1 – 64.

3GPP TS 25.413 v3.5.0 (2001-3) CR page 18



Choice Cause 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),

3GPP TS 25.413 v3.5.0 (2001-3) CR page 19



Choice Cause No remaining RAB(31),

Interaction with other procedure(32),

Repeated Integrity Checking Failure(37),

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

…)

3GPP TS 25.413 v3.5.0 (2001-3) CR page 20



Choice Cause >Transport Layer Cause INTEGER

( Signalling Transport Resource Failure(65), Iu Transport Connection Failed to Establish(66), …)


>NAS Cause INTEGER (User Restriction Start Indication(81),

User Restriction End Indication(82),

Normal Release(83), …)


>Protocol Cause 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),

…)


>Miscellaneous Cause INTEGER (O&M Intervention(113),

No Resource Available(114),

Unspecified Failure(115),

Network Optimisation(116), …)


>Non-standard Cause INTEGER Value range is 129 – 256.

3GPP TS 25.413 v3.5.0 (2001-3) CR page 21



Choice Cause (…)

The meaning of the different cause values is described in the following table. In general, "not supported" cause values indicate that the concerning capability is missing. On the other hand, "not available" cause values indicate that the concerning capability is present, but insufficient resources were available to perform the requested action.

3GPP TS 25.413 v3.5.0 (2001-3) CR page 22

Radio Network Layer cause Meaning Change Of Ciphering And/Or Integrity Protection Is Not Supported

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

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.

Directed Retry The reason for action is Directed Retry Failure In The Radio Interface Procedure

Radio interface procedure has failed.

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 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 Report Type Not Supported

The RNC is not supporting the requested location report type.

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.

3GPP TS 25.413 v3.5.0 (2001-3) CR page 23

TQUEUING Expiry The action failed due to expiry of the timer TQUEUING. TRELOCalloc Expiry Relocation Resource Allocation procedure failed due to expiry

of the timer TRELOCalloc. TRELOCcomplete Expiry The reason for the action is expiry of timer TRELOCcomplete. TRELOCoverall Expiry The reason for the action is expiry of timer TRELOCoverall. TRELOCprep Expiry Relocation Preparation procedure is cancelled when timer

TRELOCprep expires. Unable To Establish During Relocation

RAB failed to establish during relocation because it cannot be supported in the target 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. User Plane Versions Not Supported The action failed because requested user plane versions were

not supported.

Transport Layer cause Meaning 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).

NAS cause Meaning 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.

Protocol cause Meaning 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.

Miscellaneous cause Meaning 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.

9.2.1.17 Data Volume Reporting Indication back

This information element indicates whether or not RNC has to calculate the unsuccessfully transmitted NAS data amount for the RAB and to report the amount of data when the RAB is released.



Data Volume Reporting Indication

M ENUMERATED (do report, do not report)

3GPP TS 25.413 v3.5.0 (2001-3) CR page 24

9.2.1.18 User Plane Mode back

This element indicates the mode of operation of the Iu User plane requested for realising the RAB. The Iu User plane modes are defined in [6].



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

9.2.1.19 UP Mode Versions back

UP mode versions IE is an information element that is sent by CN to RNC. It is a bit string that indicates the versions for the selected Iu UP mode that are supported by the CN. The Iu User plane mode versions are defined in [6].



UP Mode Versions M BIT STRING (16)

Indicates the versions of the selected UP mode that are supported by the CN Bit 0 set to ‘1' equals version 1 Bit 1 set to ‘1' equals version 2 , …

9.2.1.33 DL N-PDU Sequence Number back

This IE indicates the radio interface sequence number (PDCP) [17] of the next downlink N-PDU (PDCP SDU) that would have been sent to the UE by a source system.



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.

9.2.1.34 UL N-PDU Sequence Number back

This IE indicates the radio interface sequence number (PDCP) [17] of the next uplink N-PDU (PDCP SDU) that would have been expected from the UE by a source system.



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.

3GPP TS 25.413 v3.5.0 (2001-3) CR page 25

9.2.1.40 PDP Type Information back



PDP Type Information >PDP Type M 1 to

<maxnoofPDPDirections>

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

PDP Type is defined in [8], and the restrictions on usage shall comply with [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.

Range bound Explanation maxnoofPDPDirections Number of directions for which PDP Type is signalled separately

9.2.1.41 Service Handover back

This IE tells if intersystem handover to GSM should, should not, or shall not be performed for the RAB in question.



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

3GPP TS 25.413 v3.5.0 (2001-3) CR page 26

9.2.2 Transport Network Layer Related IEs

9.2.2.1 Transport Layer Address back

For the PS domain this information element is an IP address to be used for the user plane transport. For the CS domain this address is to be used for Transport Network Control Plane signalling to set up the transport bearer.



Transport Layer Address M BIT STRING (1..160, …)

The Radio Network layer is not supposed to interpret the address information. It should pass it to the transport layer for interpretation. For details on the Transport Layer Address, see ref. [9].

9.2.2.2 Iu Transport Association back

This element is used to associate the RAB and the corresponding transport bearer. For the CS domain this information element is the Binding ID to be used in Transport Network Control Plane signalling during set up of the transport bearer. In PS domain this information element is the GTP Tunnel Endpoint Identifier.



Choice Iu Transport Association

>GTP TEID C – ifPS OCTET STRING (4)

>Binding ID C - ifCS OCTET STRING (4)

Condition Explanation IfPS This IE is only present for RABs towards the PS domain. IfCS This IE is only present for RABs towards the CS domain.

9.2.2.3 DL GTP-PDU Sequence Number back

This IE indicates the sequence number of the GTP-PDU which is the next to be sent to the UE.



DL GTP-PDU Sequence Number

M INTEGER (0 ..65535)

This IE indicates the sequence number of the GTP-PDU which is next to be sent to the UE.

9.2.2.4 UL GTP-PDU Sequence Number back

This IE indicates the sequence number of the GTP-PDU which is the next to be sent to the SGSN.



UL GTP-PDU Sequence Number

M INTEGER (0 ..65535)

This IE indicates the sequence number of the GTP-PDU which is next to be sent to the SGSN.

3GPP TS 25.413 v3.5.0 (2001-3) CR page 27

9.2.3 NAS Related IEs

9.2.3.18 NAS Synchronisation Indicator back

This information element contains transparent NAS information that is transferred without interpretation in the RNC.



NAS Synchronisation Indicator

M BIT STRING (4)

RAB Assignment Requestawilkinson/prof/UMTS/rabassign.pdf · 8.2 RAB Assignment 8 ... - should be...

Documents

Transcript of RAB Assignment Requestawilkinson/prof/UMTS/rabassign.pdf · 8.2 RAB Assignment 8 ... - should be...