A.2 Guidelines for Usage of the Criticality Diagnostics IE
25.4133GPPRelease 17TSUTRAN Iu interface Radio Access Network Application Part (RANAP) signalling
A.2.1 EXAMPLE MESSAGE Layout
Assume the following message format:
|
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
|
Message Type |
M |
YES |
reject |
|||
|
A |
M |
YES |
reject |
|||
|
B |
M |
YES |
reject |
|||
|
>E |
1..<maxE> |
EACH |
ignore |
|||
|
>>F |
1..<maxF> |
– |
||||
|
>>>G |
0..3, … |
EACH |
ignore |
|||
|
>>H |
1..<maxH> |
EACH |
ignore |
|||
|
>>>G |
0..3, … |
EACH |
ignore and notify |
|||
|
>>G |
M |
YES |
reject |
|||
|
>>J |
1..<maxJ> |
– |
||||
|
>>>G |
0..3, … |
EACH |
reject |
|||
|
C |
M |
YES |
reject |
|||
|
>K |
1..<maxK> |
EACH |
ignore and notify |
|||
|
>>L |
1..<maxL> |
– |
||||
|
>>>M |
O |
– |
||||
|
D |
M |
YES |
reject |
|||
NOTE 1: The IEs F, J, and L do not have assigned criticality. The IEs F, J, and L are consequently realised as the ASN.1 type SEQUENCE OF of "ordinary" ASN.1 type, e.g. INTEGER. On the other hand, the repeatable IEs with assigned criticality are realised as the ASN.1 type SEQUENCE OF of an IE object, e.g. ProtocolIE-Container.
For the corresponding ASN.1 layout, see subclause A.2.4.
A.2.2 Example on a Received EXAMPLE MESSAGE
Assume further more that a received message based on the above tabular format is according to the figure below.
Figure A.1: Example of content of a received RANAP message based on the EXAMPLE MESSAGE
A.2.3 Content of Criticality Diagnostics
A.2.3.1 Example 1
Figure A.2: Example of a received RANAP message containing a not comprehended IE
If there is an error within the instance marked as grey in the IE G in the IE J shown in the figure A.2 above, this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
|
IE name |
Value |
Comment |
|---|---|---|
|
IE Criticality |
reject |
Criticality for IE on the reported level, i.e. level 4. |
|
IE ID |
id-G |
IE ID from the reported level, i.e. level 4. |
|
Repetition Number |
11 |
Repetition number on the reported level, i.e. level 4. (Since the IE E (level 2) is the lowest level included in the Message Structure IE this is the eleventh occurrence of IE G within the IE E (level 2). |
|
Type of Error |
not understood |
|
|
Message Structure, first repetition |
||
|
>IE ID |
id-B |
IE ID from level 1. |
|
Message Structure, second repetition |
||
|
>IE ID |
id-E |
IE ID from the lowest level above the reported level, i.e. level 2. |
|
>Repetition Number |
3 |
Repetition number from the lowest level above the reported level, i.e. level 2. |
NOTE 2: The IE J on level 3 cannot be included in the Message Structure IE since they have no criticality of their own.
NOTE 3: The repetition number of the reported IE indicates the number of repetitions of IE G received up to the detected erroneous repetition, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2).
A.2.3.2 Example 2
Figure A.3: Example of a received RANAP message containing a not comprehended IE
If there is an error within the second instance (marked as grey) in the sequence (IE L in the tabular format) on level 3 below IE K in the structure shown in the figure A.3 above, this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
|
IE name |
Value |
Comment |
|---|---|---|
|
IE Criticality |
ignore and notify |
Criticality for IE on the reported level, i.e. level 2. |
|
IE ID |
id-K |
IE ID from the reported level, i.e. level 2. |
|
Repetition Number |
3 |
Repetition number on the reported level, i.e. level 2. |
|
Type of Error |
not understood |
|
|
Message Structure, first repetition |
||
|
>IE ID |
id-C |
IE ID from the lowest level above the reported level, i.e. level 1. |
NOTE 4: The IE L on level 3 cannot be reported individually included in the Message Structure IE since it has no criticality of its own.
A.2.3.3 Example 3
Figure A.4: Example of a received RANAP message containing a not comprehended IE
If there is an error within the instance marked as grey in the IE G in the IE H shown in the figure A.4 above, this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
|
IE name |
Value |
Comment |
|---|---|---|
|
IE Criticality |
ignore and notify |
Criticality for IE on the reported level, i.e. level 4. |
|
IE ID |
id-G |
IE ID from the reported level, i.e. level 4. |
|
Repetition Number |
2 |
Repetition number on the reported level, i.e. level 4. |
|
Type of Error |
not understood |
|
|
Message Structure, first repetition |
||
|
>IE ID |
id-B |
IE ID from level 1. |
|
Message Structure, second repetition |
||
|
>IE ID |
id-E |
IE ID from level 2. |
|
>Repetition Number |
3 |
Repetition number from level 2. |
|
Message Structure, third repetition |
||
|
>IE ID |
id-H |
IE ID from the lowest level above the reported level, i.e. level 3. |
|
>Repetition Number |
1 |
Repetition number from the lowest level above the reported level, i.e. level 3. |
NOTE 5: The repetition number of level 4 indicates the number of repetitions of IE G received up to the detected erroneous repetition, counted below the same instance of the previous level with assigned criticality (instance 1 of IE H on level 3).
A.2.3.4 Example 4
Figure A.5: Example of a received RANAP message containing a not comprehended IE
If there is an error within the instance marked as grey in the IE G in the IE E shown in the figure A.5 above, this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
|
IE name |
Value |
Comment |
|---|---|---|
|
IE Criticality |
reject |
Criticality for IE on the reported level, i.e. level 3. |
|
IE ID |
id-G |
IE ID from the reported level, i.e. level 3. |
|
Repetition Number |
5 |
Repetition number on the reported level, i.e. level 3. (Since the IE E (level 2) is the lowest level included in the Message Structure IE this is the fifth occurrence of IE G within the IE E (level 2). |
|
Type of Error |
not understood |
|
|
Message Structure, first repetition |
||
|
>IE ID |
id-B |
IE ID from level 1. |
|
Message Structure, second repetition |
||
|
>IE ID |
id-E |
IE ID from the lowest level above the reported level, i.e. level 2. |
|
>Repetition Number |
3 |
Repetition number from the lowest level above the reported level, i.e. level 2. |
NOTE 6: The repetition number of the reported IE indicates the number of repetitions of IE G received up to the detected erroneous repetition, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2).
A.2.3.5 Example 5
Figure A.6: Example of a received RANAP message with a missing IE
If the instance marked as grey in the IE G in the IE E shown in the figure A.6 above, is missing this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
|
IE name |
Value |
Comment |
|---|---|---|
|
IE Criticality |
reject |
Criticality for IE on the reported level, i.e. level 3. |
|
IE ID |
id-G |
IE ID from the reported level, i.e. level 3. |
|
Repetition Number |
4 |
Repetition number up to the missing IE on the reported level, i.e. level 3. (Since the IE E (level 2) is the lowest level included in the Message Structure IE there have been four occurrences of IE G within the IE E (level 2) up to the missing occurrence. |
|
Type of Error |
missing |
|
|
Message Structure, first repetition |
||
|
>IE ID |
id-B |
IE ID from level 1. |
|
Message Structure, second repetition |
||
|
>IE ID |
id-E |
IE ID from the lowest level above the reported level, i.e. level 2. |
|
>Repetition Number |
3 |
Repetition number from the lowest level above the reported level, i.e. level 2. |
NOTE 7: The repetition number of the reported IE indicates the number of repetitions of IE G received up to but not including the missing occurrence, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2).
A.2.4 ASN.1 of EXAMPLE MESSAGE
ExampleMessage ::= SEQUENCE {
ProtocolIEs ProtocolIE-Container {{ExampleMessage-IEs}},
ProtocolExtensions ProtocolExtensionContainer {{ExampleMessage-Extensions}} OPTIONAL,
…
}
ExampleMessage-IEs RANAP-PROTOCOL-IES ::= {
{ ID id-A CRITICALITY reject TYPE A PRESENCE mandatory} |
{ ID id-B CRITICALITY reject TYPE B PRESENCE mandatory} |
{ ID id-C CRITICALITY reject TYPE C PRESENCE mandatory} |
{ ID id-D CRITICALITY reject TYPE D PRESENCE mandatory} ,
…
}
B ::= SEQUENCE {
e E-List,
iE-Extensions ProtocolExtensionContainer { {B-ExtIEs} } OPTIONAL,
…
}
B-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
…
}
E-List ::= SEQUENCE (SIZE (1..maxE)) OF ProtocolIE-Container { {E-IEs} }
E-IEs RANAP-PROTOCOL-IES ::= {
{ ID id-E CRITICALITY ignore TYPE E PRESENCE mandatory },
…
}
E ::= SEQUENCE {
f F-List,
h H-List,
g G-List1,
j J-List,
iE-Extensions ProtocolExtensionContainer { {E-ExtIEs} } OPTIONAL,
…
}
E-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
…
}
F-List ::= SEQUENCE (SIZE (1..maxF)) OF F
F ::= SEQUENCE {
g G-List2 OPTIONAL,
iE-Extensions ProtocolExtensionContainer { {F-ExtIEs} } OPTIONAL,
…
}
F-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
…
}
G-List2 ::= SEQUENCE (SIZE (1..3, …)) OF ProtocolIE-Container { {G2-IEs} }
G2-IEs RANAP-PROTOCOL-IES ::= {
{ ID id-G CRITICALITY ignore TYPE G PRESENCE mandatory },
…
}
H-List ::= SEQUENCE (SIZE (1..maxH)) OF ProtocolIE-Container { {H-IEs} }
H-IEs RANAP-PROTOCOL-IES ::= {
{ ID id-H CRITICALITY ignore TYPE H PRESENCE mandatory },
…
}
H ::= SEQUENCE {
g G-List3 OPTIONAL,
iE-Extensions ProtocolExtensionContainer { {H-ExtIEs} } OPTIONAL,
…
}
H-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
…
}
G-List3 ::= SEQUENCE (SIZE (1..3, …)) OF ProtocolIE-Container { {G3-IEs} }
G3-IEs RANAP-PROTOCOL-IES ::= {
{ ID id-G CRITICALITY notify TYPE G PRESENCE mandatory },
…
}
G-List1 ::= ProtocolIE-Container { {G1-IEs} }
G1-IEs RANAP-PROTOCOL-IES ::= {
{ ID id-G CRITICALITY reject TYPE G PRESENCE mandatory },
…
}
J-List ::= SEQUENCE (SIZE (1..maxJ)) OF J
J ::= SEQUENCE {
g G-List4 OPTIONAL,
iE-Extensions ProtocolExtensionContainer { {J-ExtIEs} } OPTIONAL,
…
}
J-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
…
}
G-List4 ::= SEQUENCE (SIZE (1..3, …)) OF ProtocolIE-Container { {G4-IEs} }
G4-IEs RANAP-PROTOCOL-IES ::= {
{ ID id-G CRITICALITY reject TYPE G PRESENCE mandatory },
…
}
C ::= SEQUENCE {
k K-List,
iE-Extensions ProtocolExtensionContainer { {C-ExtIEs} } OPTIONAL,
…
}
C-ExtIEsA -PROTOCOL-EXTENSION ::= {
…
}
K-List ::= SEQUENCE (SIZE (1..maxK)) OF ProtocolIE-Container { {K-IEs} }
K-IEs RANAP-PROTOCOL-IES ::= {
{ ID id-K CRITICALITY notify TYPE K PRESENCE mandatory },
…
}
K ::= SEQUENCE {
l L-List,
iE-Extensions ProtocolExtensionContainer { {K-ExtIEs} } OPTIONAL,
…
}
K-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
…
}
L-List ::= SEQUENCE (SIZE (1..maxL)) OF L
L ::= SEQUENCE {
m M OPTIONAL,
iE-Extensions ProtocolExtensionContainer { {L-ExtIEs} } OPTIONAL,
…
}
L-ExtIEs RANAP-PROTOCOL-EXTENSION ::= {
…
}
ExampleMessage-Extensions RANAP-PROTOCOL-EXTENSION ::= {
…
}
Annex B (informative):
RANAP Transparent containers content
Transparent containers are used in order to transfer information from one RAN node to another RAN node. Depending on the particular scenario the behaviour of both involved RAN nodes may be either specified according to the same radio system or according to different radio systems. During an inter-system handover the source RAN node has to adapt to the target RAN node and its requirements.
In RANAP, for intra-system relocation and inter-system handover to and from E-UTRAN, there is a single transparent container defined for transporting information from the source to the target RAN node and a single transparent container for transporting information from the target to the source RAN node during relocation/handover preparation: the Source to Target Transparent Container IE and the Target to Source Transparent Container IE, which may carry either UTRAN or E-UTRAN specific information.
Note: The definition of generic transparent containers for relocation/handover purposes allows to transport them through the core network in a RAT-agnostic way. Inter-system handover to GERAN is not affected by this scheme.
Therefore the container content is encoded according to the rules which are specified for in the target radio system. In subclause 8.6.2, it is described how the transparent container shall be encoded with respect to the scenario in which it is used.
The table below is showing all possible scenarios and definitions according to which the content of the transparent container shall be encoded. Additionally the reference to the specification defining particular IE is given.
Table B.1: Specification of Transparent Containers referenced in RANAP.
|
Scenario |
Source to Target Transparent Container IE in RANAP: RELOCATION REQUIRED message |
Target to Source Transparent Container IE in RANAP: RELOCATION COMMAND message |
||
|
Name of the IE |
Definition in specification |
Name of the IE |
Definition in specification |
|
|
Intra UTRAN relocation |
Source RNC to Target RNC Transparent Container |
25.413 |
Target RNC to Source RNC Transparent Container |
25.413 |
|
Inter-system handover to E-UTRAN |
Source eNB to Target eNB Transparent Container |
36.413 |
Target eNB to Source eNB Transparent Container |
36.413 |
Annex C (informative):
Processing of Transparent Containers at the SGSN
Irrespective of the mobility scenario (inter-RAT or intra-UMTS), the SGSN always processes the Source to Target Transparent Container IE and the Target to Source Transparent Container IE in the following way:
– The SGSN shall convey to the RNC the information received within
– the GTPv1-C "UTRAN transparent field" of the "UTRAN Transparent Container" IE across the Gn interface (see subclause 7.7.38 of TS 29.060 [35]), or
– the GTPv2 "F-container field" of the "F-Container" IE across the S3/S16 interface (see subclause 8.48 of TS 29.274 [36])
by including it in either the Source to Target Transparent Container IE or the Target to Source Transparent Container of the corresponding RANAP message.
– The SGSN shall convey to the GTP peer the information received within either the Source to Target Transparent Container IE or the Target to Source Transparent Container IE by including it in
– the GTPv1-C "UTRAN transparent field" of the "UTRAN Transparent Container" IE across the Gn interface (see subclause 7.7.38 of TS 29.060 [35]), or
– the GTPv2 "F-container field" of the "F-Container" IE across the S3/S16 interface (see subclause 8.48 of TS 29.274 [36]).
Annex D (informative):
Change History
|
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
New |
|
06 |
RP-99746 |
– |
Approved at TSG RAN #6 and placed under Change Control |
3.0.0 |
|
|
07 |
– |
– |
Approved at TSG RAN #7 |
3.1.0 |
|
|
08 |
– |
– |
Approved at TSG RAN #8 |
3.2.0 |
|
|
09 |
RP-000373 |
124- 136, 168- 171, 173, |
Approved at TSG RAN #9 |
3.3.0 |
|
|
09 |
RP-000374 |
175, 177- 179, 181- 184 |
Approved at TSG RAN #9 |
3.3.0 |
|
|
10 |
RP-000613 RP-000695 |
185-191, |
Approved at TSG RAN #10 |
3.4.0 |
|
|
11 |
RP-010110 |
236, |
Approved at TSG RAN #11 |
3.5.0 |
|
|
11 |
RP-010111 |
268, |
Approved at TSG RAN #11 |
3.5.0 |
|
|
11 |
RP-010158 |
271 |
Approved at TSG RAN #11 and placed under Change Control |
4.0.0 |
|
|
11 |
RP-010189 |
265 |
Approved at TSG RAN #11 and placed under Change Control |
4.0.0 |
|
|
11 |
RP-010156 |
272, |
Approved at TSG RAN #11 and placed under Change Control |
4.0.0 |
|
|
11 |
RP-010155 |
252 |
Approved at TSG RAN #11 and placed under Change Control |
4.0.0 |
|
|
11 |
RP-010163 |
250 |
Approved at TSG RAN #11 and placed under Change Control |
4.0.0 |
|
|
12 |
RP-010454 |
277, |
Approved at TSG RAN #12 |
4.1.0 |
|
|
12 |
RP-010375 |
301, |
Approved at TSG RAN #12 |
4.1.0 |
|
|
12 |
RP-010392 |
303, |
Approved at TSG RAN #12 |
4.1.0 |
|
|
13 |
RP-010578 |
324 |
1 |
Correction to the Error handling of the ERROR INDICATION message |
4.2.0 |
|
13 |
RP-010578 |
326 |
1 |
Alignment of Conditional Presence with RAN3 Specification Principles |
4.2.0 |
|
13 |
RP-010578 |
328 |
NAS Synchronisation Indicator also at RAB Establishment |
4.2.0 |
|
|
13 |
RP-010578 |
329 |
2 |
Old BSS to New BSS IE optional in UMTS to GSM handover |
4.2.0 |
|
13 |
RP-010578 |
330 |
Order of elements in bitstrings |
4.2.0 |
|
|
13 |
RP-010578 |
337 |
Data Forwarding related IEs in RELOCATION COMMAND message |
4.2.0 |
|
|
13 |
RP-010578 |
339 |
1 |
Error handling of the Erroneously Present Conditional Ies |
4.2.0 |
|
13 |
RP-010578 |
345 |
1 |
Rapporteurs corrections in RANAP |
4.2.0 |
|
13 |
RP-010578 |
347 |
3 |
Inconsistency in definition of parameters used in INVOKE_TRACE message |
4.2.0 |
|
13 |
RP-010579 |
359 |
1 |
Clarification of chapter 10 |
4.2.0 |
|
13 |
RP-010579 |
364 |
1 |
Condition of SDU format information IE |
4.2.0 |
|
13 |
RP-010579 |
368 |
1 |
Relocation Requirement not to be used |
4.2.0 |
|
13 |
RP-010594 |
297 |
2 |
Clarification on User Plane Version Indication |
4.2.0 |
|
13 |
RP-010594 |
302 |
7 |
Release 4 additions in Iu to support new positioning methods |
4.2.0 |
|
13 |
RP-010698 |
244 |
7 |
N-to-M relation between CN and UTRAN |
4.2.0 |
|
14 |
RP-010895 |
361 |
3 |
CR on Priority range |
4.3.0 |
|
14 |
RP-010848 |
365 |
Bitstrings ordering |
4.3.0 |
|
|
14 |
RP-010848 |
369 |
2 |
UP Versions not supported |
4.3.0 |
|
14 |
RP-010848 |
371 |
1 |
Location Report Area |
4.3.0 |
|
14 |
RP-010848 |
378 |
1 |
Reason for LOCATION REPORT message is not clear |
4.3.0 |
|
14 |
RP-010848 |
380 |
1 |
Corrections to RRC information containers |
4.3.0 |
|
14 |
RP-010848 |
383 |
Procedure Code Criticality in Error Indication |
4.3.0 |
|
|
14 |
RP-010848 |
386 |
2 |
Addition of amendment to clarify the PER encoding of bitstrings |
4.3.0 |
|
14 |
RP-010848 |
388 |
2 |
Chosen Integrity Protection Algorithm IE over MAP/E interface |
4.3.0 |
|
14 |
RP-010848 |
390 |
Rapporteurs corrections in RANAP (MCC/MNC) |
4.3.0 |
|
|
14 |
RP-010849 |
394 |
1 |
Clarification on Location Request not fulfilled |
4.3.0 |
|
14 |
RP-010849 |
396 |
1 |
Subflow SDU Size clarification |
4.3.0 |
|
14 |
RP-010849 |
400 |
Correction the Clause 10 Error Handling |
4.3.0 |
|
|
14 |
RP-010871 |
363 |
1 |
Cause value for not accepted relocation request |
4.3.0 |
|
14 |
RP-010871 |
367 |
1 |
Correction to Release 4 additions in Iu to support new positioning methods |
4.3.0 |
|
14 |
RP-010871 |
372 |
Chapter A.2.1 (EXAMPLE MESSAGE Layout) missing in version 4.2.0 |
4.3.0 |
|
|
14 |
RP-010871 |
373 |
1 |
N-to-M relation between CN and UTRAN impacts on CN initiated Reset Resource procedure |
4.3.0 |
|
14 |
RP-010871 |
374 |
Stop Direct Report |
4.3.0 |
|
|
14 |
RP-010871 |
384 |
1 |
MCC implementation CR for corrections to Release 4 additions in Iu to support new positioning methods. |
4.3.0 |
|
14 |
RP-010871 |
397 |
1 |
Correction to LCS Vertical Accurancy |
4.3.0 |
|
15 |
RP-020164 |
402 |
Question regarding SRNS Context Transfer and SRNS Data Forwarding Initiation |
4.4.0 |
|
|
15 |
RP-020164 |
407 |
Intersystem Change and inter-system Handover corrections |
4.4.0 |
|
|
15 |
RP-020164 |
418 |
RAB Modification Parameters |
4.4.0 |
|
|
15 |
RP-020164 |
422 |
1 |
Delivery of erroneous SDUs |
4.4.0 |
|
15 |
RP-020164 |
424 |
2 |
Handling of Global RNC-ID in Reset and Reset resource |
4.4.0 |
|
15 |
RP-020164 |
426 |
2 |
RABs concerned by contexts transfer |
4.4.0 |
|
15 |
RP-020164 |
432 |
Alignment of definition of Guaranteed Bitrate with 25.415 |
4.4.0 |
|
|
15 |
RP-020262 |
435 |
4 |
Inclusion of "Age of Location IE into LOCATION REPORT" |
4.4.0 |
|
15 |
RP-020179 |
408 |
Requirements on user plane initialisation moved to 25.415 |
4.4.0 |
|
|
15 |
RP-020179 |
429 |
1 |
Correction to LCS Vertical Accuracy Code IE |
4.4.0 |
|
15 |
RP-020189 |
419 |
3 |
Introduction of IP Transport option in UTRAN |
5.0.0 |
|
15 |
RP-020257 |
431 |
1 |
NNSF Functional Description |
5.0.0 |
|
15 |
RP-020188 |
409 |
2 |
Transport Layer Address at RAB modification |
5.0.0 |
|
15 |
RP-020188 |
428 |
3 |
Implementation of Handover/Relocation Solution for Inter-RAN Load Information Exchange between RAN and GERAN for Rel’5 |
5.0.0 |
|
16 |
RP-020423 |
404 |
6 |
Release 5 additions of ROHC context relocation support during SRNS relocation |
5.1.0 |
|
16 |
RP-020401 |
437 |
Criticality Information Decoding Failure Handling |
5.1.0 |
|
|
16 |
RP-020401 |
440 |
2 |
Erroneous Security Mode Control procedure |
5.1.0 |
|
16 |
RP-020401 |
443 |
Correction of Target RNC-ID |
5.1.0 |
|
|
16 |
RP-020401 |
444 |
1 |
SDU Format Information Presence |
5.1.0 |
|
16 |
RP-020417 |
448 |
Extension container for Last Known Service Area IE |
5.1.0 |
|
|
16 |
RP-020401 |
451 |
“EXTENSION INDICATION” PROPOSAL |
5.1.0 |
|
|
16 |
RP-020417 |
453 |
Correction of wrong implementation for CR429 |
5.1.0 |
|
|
16 |
RP-020401 |
462 |
1 |
RNL-TNL coordination in RANAP |
5.1.0 |
|
16 |
RP-020401 |
465 |
2 |
Correction of RNC Iu Coordinated relocation |
5.1.0 |
|
16 |
RP-020421 |
466 |
1 |
IPv4-IPv6 interworking for data forwarding |
5.1.0 |
|
16 |
RP-020401 |
469 |
1 |
Clarification for the usage of the cause value |
5.1.0 |
|
16 |
RP-020417 |
479 |
1 |
Correction due to the wrong implementation of CR326&244 and error in the CR424 |
5.1.0 |
|
17 |
RP-020606 |
481 |
Erroneous criticality in DATA VOLUME REPORT REQUEST a.o. |
5.2.0 |
|
|
17 |
RP-020600 |
484 |
2 |
Handling of security at relocation |
5.2.0 |
|
17 |
RP-020629 |
488 |
1 |
CRRM Corrections |
5.2.0 |
|
17 |
RP-020600 |
495 |
1 |
Codec change during SRNS relocation |
5.2.0 |
|
17 |
RP-020606 |
503 |
1 |
New cause value for RAB release request |
5.2.0 |
|
17 |
RP-020625 |
504 |
2 |
Shared Networks in connected mode – Information Transfer |
5.2.0 |
|
17 |
RP-020624 |
506 |
2 |
GERAN specific impacts on the Iu-cs interface |
5.2.0 |
|
17 |
RP-020600 |
509 |
1 |
Correction to RANAP cause value range |
5.2.0 |
|
17 |
RP-020606 |
513 |
LCS alignment with stage 2 |
5.2.0 |
|
|
17 |
RP-020643 |
515 |
Signalling enhancements for GERAN Iu Mode LCS |
5.2.0 |
|
|
18 |
RP-020517 |
517 |
Correction to RANAP RESET procedure |
5.3.0 |
|
|
18 |
RP-020522 |
522 |
1 |
Rel4 Common CR after RANAP review |
5.3.0 |
|
18 |
RP-020526 |
526 |
4 |
Correction to enable Rel4 extensions in Location Reporting Control procedure. |
5.3.0 |
|
18 |
RP-020529 |
529 |
2 |
Correction of RAB Subflows and SRBs mapping onto the transport channel identifiers of Iur in the Source RNC to Target RNC transparent container |
5.3.0 |
|
18 |
RP-020532 |
532 |
1 |
Correction of coding of GSM IEs |
5.3.0 |
|
18 |
RP-020533 |
533 |
1 |
New cause codes for Network sharing in connected mode |
5.3.0 |
|
18 |
RP-020535 |
535 |
1 |
Encoding of information elements. |
5.3.0 |
|
19 |
RP-030060 |
546 |
1 |
Addition of RAB Subflows mapping onto the transport channel identifiers of Iur in the Source RNC to Target RNC transparent container for HSDPA |
5.4.0 |
|
19 |
RP-030067 |
550 |
Alignment of “Uncertainty Ellipse” with RRC |
5.4.0 |
|
|
19 |
RP-030056 |
552 |
1 |
Duplicated Iu connection identifiers |
5.4.0 |
|
19 |
RP-030060 |
557 |
1 |
Inclusion of IMS Signalling Indication into R5 RANAP |
5.4.0 |
|
19 |
RP-030060 |
558 |
Correction to RANAP due to GERAN Iu mode |
5.4.0 |
|
|
19 |
RP-030056 |
562 |
Essential correction of IMSI coding |
5.4.0 |
|
|
20 |
RP-030314 |
570 |
2 |
Essential Correction of Iu Release Issue |
5.5.0 |
|
20 |
RP-030326 |
572 |
1 |
Correction of Failure message used for logical errors |
5.5.0 |
|
20 |
RP-030339 |
573 |
2 |
Introduction of Early UE Handling – Bitmap Option |
5.5.0 |
|
20 |
RP-030316 |
576 |
2 |
Iu UP Initialisation during RAB modification |
5.5.0 |
|
21 |
RP-030445 |
578 |
Alignment of title and sub-clause text of chapter 10.3.4.2 |
5.6.0 |
|
|
21 |
RP-030437 |
584 |
1 |
Essential Correction of Iu Release Request |
5.6.0 |
|
21 |
RP-030439 |
586 |
2 |
Introduction of positioning methods over Iu |
5.6.0 |
|
21 |
RP-030439 |
590 |
1 |
Alignment of RANAP and RNSAP CRRM solutions |
5.6.0 |
|
21 |
RP-030439 |
594 |
RNC use of IMSI within Relocation Resource Allocation |
5.6.0 |
|
|
21 |
RP-030446 |
595 |
Removal of the note in chapter 10 |
5.6.0 |
|
|
22 |
RP-030671 |
597 |
– |
Backwards Compatibility for LCS- Limited Solution |
5.7.0 |
|
22 |
RP-030676 |
601 |
2 |
Serious Correction for Rescue handover |
5.7.0 |
|
22 |
RP-030676 |
604 |
– |
Serious Correction for Security in Multi-domain calls |
5.7.0 |
|
22 |
RP-030715 |
606 |
2 |
Correction of RAB Release Request Inter-working |
5.7.0 |
|
22 |
RP-030676 |
607 |
3 |
RANAP Review issue 2: Correction of Position Data |
5.7.0 |
|
22 |
RP-030676 |
608 |
– |
RANAP Review issue 3: LCS Accuracy |
5.7.0 |
|
22 |
RP-030671 |
613 |
1 |
Add IE “Criticality Diagnostics” for LOCATION RELATED DATA FAILURE message |
5.7.0 |
|
22 |
RP-030686 |
614 |
1 |
RT Load Value Clarification |
5.7.0 |
|
22 |
RP-030671 |
618 |
1 |
Correction of Reference section |
5.7.0 |
|
22 |
RP-030676 |
620 |
1 |
Corrections to the data volume reporting function |
5.7.0 |
|
22 |
RP-030676 |
622 |
2 |
Big clarification CR based on RANAP Rel-5 review |
5.7.0 |
|
22 |
RP-030676 |
623 |
2 |
Correction to CRRM Iu solution |
5.7.0 |
|
22 |
– |
– |
– |
Introduction of Release 6 specification |
6.0.0 |
|
23 |
RP-040053 |
641 |
Alignment with 23.032 correction of Included Angle for Ellipsoid Arc |
6.1.0 |
|
|
23 |
RP-040062 |
634 |
Correction of GERAN related Release 5 IEs |
6.1.0 |
|
|
23 |
RP-040062 |
636 |
1 |
Causes used in RANAP |
6.1.0 |
|
23 |
RP-040062 |
638 |
Inaccuracies in the specification of the Overload procedure |
6.1.0 |
|
|
23 |
RP-040062 |
643 |
1 |
Clarification on Iu reset procedure |
6.1.0 |
|
23 |
RP-040062 |
652 |
Integrity Status Correction |
6.1.0 |
|
|
23 |
RP-040062 |
654 |
Coding of Discontinuous Transmission/No_Data mode |
6.1.0 |
|
|
24 |
RP-040216 |
658 |
Introduction of an indication of achieved accuracy in Location Report procedure over Iu interface. |
6.2.0 |
|
|
24 |
RP-040174 |
662 |
3 |
Data Volume Reporting Correction |
6.2.0 |
|
24 |
RP-040174 |
667 |
1 |
SNA Coding correction |
6.2.0 |
|
24 |
RP-040182 |
668 |
2 |
Introduction of RIM mechanisms for NACC over the Iu interface |
6.2.0 |
|
24 |
RP-040174 |
672 |
Correction of Transport Layer Address and Iu Transport Association handling in RAB Assignment |
6.2.0 |
|
|
24 |
RP-040183 |
673 |
1 |
Management Based Activation in the UTRAN over the Iu |
6.2.0 |
|
24 |
RP-040183 |
674 |
1 |
Enhancement of Trace handling during Relocation |
6.2.0 |
|
24 |
RP-040183 |
675 |
1 |
Modification of CN Invoke Trace for Subscriber and Equipment Trace support over Iu |
6.2.0 |
|
25 |
RP-040298 |
681 |
4 |
Addition of Relocation Failure cause code to match GERAN cause code |
6.3.0 |
|
25 |
RP-040299 |
692 |
3 |
Data Volume Reporting Correction |
6.3.0 |
|
25 |
RP-040299 |
696 |
2 |
Service Handover Timing and Priority |
6.3.0 |
|
25 |
RP-040299 |
700 |
1 |
presence of ciphering key in the RANAP container |
6.3.0 |
|
26 |
RP-040439 |
701 |
Indication of selected PLMN in shared networks |
6.4.0 |
|
|
26 |
RP-040439 |
702 |
1 |
Rerouting in MOCN |
6.4.0 |
|
26 |
RP-040437 |
706 |
2 |
MBMS stage 3 support over Iu |
6.4.0 |
|
26 |
RP-040439 |
715 |
2 |
Support of full Mobility/Backwards Compatibility in Network Sharing |
6.4.0 |
|
26 |
RP-040441 |
719 |
Correction of reference to outdated ITU-T recommendations |
6.4.0 |
|
|
space removed in ASN.1from "MBMSSessionStartResponse" |
6.4.1 |
||||
|
27 |
RP-050057 |
721 |
3 |
MBMS Session Repetition Number on Session Start |
6.5.0 |
|
27 |
RP-050057 |
724 |
3 |
MBMS RAB Management |
6.5.0 |
|
27 |
RP-050052 |
730 |
2 |
Essential Correction on Direct Transfer Messages |
6.5.0 |
|
27 |
RP-050057 |
734 |
MBMS Contexts |
6.5.0 |
|
|
27 |
RP-050057 |
737 |
3 |
MBMS IE codings |
6.5.0 |
|
27 |
RP-050057 |
738 |
MBMS Session Failure |
6.5.0 |
|
|
27 |
RP-050059 |
739 |
2 |
Support of Network-initiated Scudif (revision of R3-041734) |
6.5.0 |
|
27 |
RP-050052 |
740 |
1 |
Correction of RANAP Containers and CRRM |
6.5.0 |
|
28 |
RP-050227 |
741 |
MBMS Session Duration IE |
6.6.0 |
|
|
28 |
RP-050229 |
742 |
1 |
Addition of E-DCH MAC-d Flow ID in transparent Container |
6.6.0 |
|
28 |
RP-050233 |
743 |
1 |
Correction to the RANAP in Iu-Flex Paging without TMSI. |
6.6.0 |
|
28 |
RP-050227 |
745 |
2 |
Enhancement for MBMS SESSION START message |
6.6.0 |
|
28 |
RP-050233 |
747 |
1 |
Presence information for RAC in Target ID towards PS domain |
6.6.0 |
|
28 |
RP-050217 |
749 |
Correction of CR729 |
6.6.0 |
|
|
28 |
RP-050227 |
750 |
1 |
Correction of MBMS figure title |
6.6.0 |
|
28 |
RP-050236 |
752 |
Release after rerouting attempt |
6.6.0 |
|
|
28 |
RP-050236 |
753 |
No Relocation during MOCN Rerouting |
6.6.0 |
|
|
28 |
RP-050217 |
763 |
Correction of Cell Load Information Group |
6.6.0 |
|
|
28 |
RP-050233 |
768 |
Correction of queuing at relocation |
6.6.0 |
|
|
29 |
RP-050443 |
773 |
MBMS applies for the PS domain |
6.7.0 |
|
|
29 |
RP-050473 |
782 |
Inclusion of Inter-RAT PS Handover between UTRAN and GERAN A/Gb |
6.7.0 |
|
|
29 |
RP-050444 |
784 |
1 |
Clarification of the Relocation Cancel and Relocation Preparation |
6.7.0 |
|
30 |
RP-050692 |
791 |
1 |
Introduction of the Time to MBMS Data Trasfer |
6.8.0 |
|
30 |
RP-050693 |
796 |
Correction of SCUDIF Relocation |
6.8.0 |
|
|
30 |
RP-050693 |
797 |
1 |
Error Handling of unused IEs |
6.8.0 |
|
30 |
RP-050693 |
801 |
1 |
Rewording of interaction text from CR784 |
6.8.0 |
|
30 |
RP-050693 |
803 |
1 |
Rapporteur’s Review of 25.413 |
6.8.0 |
|
30 |
RP-050692 |
804 |
1 |
MBMS Service Area List IE Encoding Correction |
6.8.0 |
|
03/2006 |
– |
– |
Release 7 version created based on v6.8.0 |
7.0.0 |
|
|
31 |
RP-060072 |
0770 |
10 |
Enabling the Providing of Velocity |
7.1.0 |
|
31 |
RP-060061 |
0806 |
Correction of IE name in procedure text for MBMS Session Update |
7.1.0 |
|
|
31 |
RP-060061 |
0810 |
2 |
Correction of signaling bearer mode for MBMS Registration Failure |
7.1.0 |
|
31 |
RP-060061 |
0825 |
2 |
PS/CS coordination in shared RAN for MOCN |
7.1.0 |
|
31 |
RP-060061 |
0827 |
2 |
Inclusion of redirect attempt flag in Initial UE Message |
7.1.0 |
|
31 |
RP-060061 |
0829 |
SRB mapping toward HS-DSCH and E-DCH MAC-d flows |
7.1.0 |
|
|
31 |
RP-060062 |
0831 |
1 |
Iu Release when detecting double Iu |
7.1.0 |
|
32 |
RP-060288 |
0834 |
4 |
Correction of performance measurement point IRATHO.SuccOutPSUE |
7.2.0 |
|
32 |
RP-060289 |
0835 |
1 |
Clarification on setting the Accuracy Fulfilment Indicator IE by the RNC |
7.2.0 |
|
32 |
RP-060278 |
0843 |
3 |
SI/PSI information transfer for PS handover |
7.2.0 |
|
32 |
RP-060386 |
0844 |
2 |
Correction of positioning confidence reporting inconsistencies |
7.2.0 |
|
32 |
RP-060278 |
0849 |
Unclear presence of Selected PLMN identity IE in case of network sharing non supporting UEs |
7.2.0 |
|
|
32 |
RP-060278 |
0851 |
1 |
Handling of preserved nrt RABs |
7.2.0 |
|
32 |
RP-060278 |
0853 |
1 |
Target RNC ID in RIM Routing Information towards an RNC |
7.2.0 |
|
33 |
RP-060499 |
0856 |
1 |
Criticality Diagnostics IE for MBMS RAB Release |
7.3.0 |
|
33 |
RP-060514 |
0857 |
2 |
Status of Service Handover IE |
7.3.0 |
|
33 |
RP-060514 |
0858 |
Alignment of PLMN identity |
7.3.0 |
|
|
33 |
RP-060499 |
0860 |
Correction of the Meaning of cause value |
7.3.0 |
|
|
33 |
RP-060510 |
0861 |
1 |
Addition of Periodic Location Procedures |
7.3.0 |
|
33 |
RP-060579 |
0871 |
2 |
Inclusion of the MBMS Counting Information IE to the MBMS Session Start Request |
7.3.0 |
|
33 |
RP-060590 |
0873 |
Removal of MBMS SAI Semantic Description in RANAP |
7.3.0 |
|
|
34 |
RP-060724 |
0854 |
2 |
Introduction of inter-RAT DTM Handover |
7.4.0 |
|
34 |
RP-060713 |
0865 |
4 |
Introduction of new ciphering algorithm UEA2 and integrity protection algorithm UIA2 |
7.4.0 |
|
34 |
RP-060698 |
0879 |
2 |
Conditions for MBMS RAB set up |
7.4.0 |
|
34 |
RP-060706 |
0883 |
5 |
Introducing Direct Tunnel in RANAP |
7.4.0 |
|
34 |
RP-060698 |
0885 |
3 |
RNC Rejection of MBMS Session Setup with a TMGI already used for another ongoing MBMS session |
7.4.0 |
|
34 |
RP-060698 |
0889 |
1 |
MBMS session Repetition Number Corrections |
7.4.0 |
|
35 |
RP-070063 |
0891 |
2 |
Direct Tunnel Correction |
7.5.0 |
|
35 |
RP-070063 |
0895 |
2 |
Signalling RABs |
7.5.0 |
|
35 |
RP-070063 |
0898 |
1 |
Mandatory use of transport layer information |
7.5.0 |
|
35 |
RP-070063 |
0900 |
Modification of Rules for Building RANAP Messages |
7.5.0 |
|
|
35 |
RP-070054 |
0902 |
2 |
Correction on MBMS SESSION START and MBMS SESSION UPDATE |
7.5.0 |
|
35 |
RP-070061 |
0906 |
3 |
Introduction of MIMO in RANAP |
7.5.0 |
|
35 |
RP-070056 |
0908 |
2 |
MBMS Session setup of a parallel session of the same service in a distinct MBMS service area |
7.5.0 |
|
35 |
RP-070054 |
0910 |
Update of MBMS Session Duration |
7.5.0 |
|
|
36 |
RP-070474 |
0905 |
5 |
Introduction of Extended RNC-ID |
7.6.0 |
|
36 |
RP-070322 |
0914 |
3 |
Clarification on distinguishing MBMS Service Areas of Multiple parallel MBMS Sessions of the same service |
7.6.0 |
|
36 |
RP-070339 |
0924 |
2 |
Frequency Layer Convergence |
7.6.0 |
|
36 |
RP-070337 |
0925 |
2 |
Introduction of GANSS (Galileo and Additional Navigation Systems) in RANAP |
7.6.0 |
|
37 |
RP-070567 |
0928 |
1 |
Correction to GANSS Location Related Data Request |
7.7.0 |
|
37 |
RP-070565 |
0930 |
MBMS broadcast RAB Set Up |
7.7.0 |
|
|
37 |
RP-070578 |
0932 |
Correction for RNC ID |
7.7.0 |
|
|
37 |
RP-070578 |
0934 |
1 |
Maximum number of Iu Signalling Connection Identifiers |
7.7.0 |
|
37 |
RP-070581 |
0935 |
UE Involved Relocation for source RNC not having Iu-cs UP |
7.7.0 |
|
|
38 |
RP-070838 |
0939 |
1 |
ASN1-Tabular alignment for GANSS feature in TS25.413 |
7.8.0 |
|
38 |
RP-070837 |
0941 |
Explicit references to TRs 25.994 and 25.995 |
7.8.0 |
|
|
38 |
RP-070842 |
0942 |
Rapporteurs Review |
7.8.0 |
|
|
38 |
RP-070844 |
0943 |
2 |
Introduction of cause value for CS-triggered relocation |
7.8.0 |
|
40 |
RP-080297 |
0950 |
Correction of the Release of MBMS Signalling Connection |
7.9.0 |
|
|
09/2008 |
– |
– |
Rel-8 version created based on v7.9.0 |
8.0.0 |
|
|
41 |
RP-080589 |
0952 |
2 |
Introduction of Enhanced Relocation |
8.0.0 |
|
41 |
– |
– |
ASN.1 error corrected |
8.0.1 |
|
|
42 |
RP-080852 |
0953 |
Support for additional navigation satellite systems in RANAP |
8.1.0 |
|
|
42 |
RP-080849 |
0959 |
3 |
Introduction of UE History Information |
8.1.0 |
|
42 |
RP-080849 |
0960 |
1 |
Introduction of MBMS Improved Soltuion |
8.1.0 |
|
42 |
RP-080848 |
0961 |
3 |
Inter-RAT Mobility to/from E-UTRAN |
8.1.0 |
|
42 |
RP-080855 |
0962 |
Introduction of the Subscriber Profile ID for RAT/Frequency priority |
8.1.0 |
|
|
42 |
RP-080840 |
0963 |
ASN.1 changes for enhanced relocation |
8.1.0 |
|
|
42 |
RP-080854 |
0965 |
2 |
RANAP changes to support the use of CSG Identifiers |
8.1.0 |
|
42 |
RP-080856 |
0966 |
Removal of Recovery and Restoration from 23.060 |
8.1.0 |
|
|
43 |
RP-090083 |
0971 |
Cause value mapping for CSFB |
8.2.0 |
|
|
43 |
RP-090079 |
0974 |
2 |
Clarification of usage of MBMS RAB release for MBMS broadcast |
8.2.0 |
|
43 |
RP-090075 |
0977 |
2 |
Clarification of usage of Extended MBR and GBR |
8.2.0 |
|
43 |
RP-090076 |
0978 |
Clarification on Source ID |
8.2.0 |
|
|
43 |
RP-090078 |
0979 |
1 |
Editorial Updates TS 25.413 |
8.2.0 |
|
43 |
RP-090245 |
0980 |
Transparent Container content – informative annex |
8.2.0 |
|
|
43 |
RP-090093 |
0981 |
Introduction of HSPA SRVCC |
8.2.0 |
|
|
43 |
RP-090079 |
0982 |
2 |
Further Corrections for Enhanced Relocation |
8.2.0 |
|
43 |
RP-090081 |
0983 |
Inclusion of CSG ID in initial UE message |
8.2.0 |
|
|
43 |
RP-090078 |
0984 |
Clarification on ASN.1 for Generic Container |
8.2.0 |
|
|
43 |
RP-090263 |
0985 |
Rename of Source RNC ID in ENHANCD RELOCATION COMPLETE REQUEST |
8.3.0 |
|
|
March 2009 |
– |
– |
– |
ASN.1 debugging before freezing |
8.3.1 |
|
44 |
RP-090638 |
0988 |
Addition of Integrity Protection Information IE and Encryption Information IE into Enhanced SRNS Relocation |
8.3.0 |
|
|
44 |
RP-090641 |
0989 |
4 |
RANAP changes to support paging optimisation |
8.3.0 |
|
44 |
RP-090633 |
0994 |
Correction of extended alternative bit rate |
8.3.0 |
|
|
44 |
RP-090633 |
0996 |
Structure of prodeure text for Relocation Preparation |
8.3.0 |
|
|
44 |
RP-090635 |
0998 |
1 |
Interaction between Enhanced Relocation and RAB Assignment Procedure |
8.3.0 |
|
44 |
RP-090642 |
0999 |
1 |
Correction of introduction of HSPA SRVCC |
8.3.0 |
|
44 |
RP-090642 |
1000 |
Correction of the Global CN-ID for the PS domain |
8.3.0 |
|
|
44 |
RP-090636 |
1002 |
Introduction of E-UTRAN Service Handover IE |
8.3.0 |
|
|
45 |
RP-090770 |
1015 |
Correction of ASN.1 Target Cell ID missing |
8.4.0 |
|
|
09/2009 |
– |
– |
Rel-9 version created based on v8.4.0 |
9.0.0 |
|
|
45 |
RP-090777 |
1009 |
2 |
Introduction of UE-AMBR Concept in UMTS |
9.0.0 |
|
46 |
RP-091191 |
1008 |
4 |
Support for paging optimization with CSG membership changes |
9.1.0 |
|
46 |
RP-091191 |
1018 |
1 |
Target Cell ID for HNB in-bound HO |
9.1.0 |
|
46 |
RP-091191 |
1037 |
1 |
Inclusion of CSG information for access control in 3G handover procedures and UE prioritization in 3G hybrid cells. |
9.1.0 |
|
47 |
RP-100219 |
1038 |
– |
Correction of CSG Cell and Hybrid Cell Definition |
9.2.0 |
|
47 |
RP-100222 |
1039 |
1 |
Clarification on the Access Control of Non-CSG UE During Inbound Handover |
9.2.0 |
|
47 |
RP-100222 |
1041 |
1 |
Handling of CSG ID check failure in hybrid cells |
9.2.0 |
|
47 |
RP-100215 |
1043 |
– |
Correct name of Target eNB ID to align with 36.413 |
9.2.0 |
|
47 |
RP-100228 |
1044 |
– |
Inter RAT Mobility Load Balancing on Iu |
9.2.0 |
|
47 |
RP-100222 |
1047 |
– |
Correct wrong CSG ID reference |
9.2.0 |
|
47 |
RP-100229 |
1048 |
1 |
Description of Transparent Container Encoding |
9.2.0 |
|
47 |
RP-100229 |
1049 |
– |
Rapporteur’s update for RANAP protocol |
9.2.0 |
|
47 |
RP-100219 |
1051 |
2 |
Addition of IP Source Address in MBMS Synchronisation Information in MBMS Session Start |
9.2.0 |
|
47 |
RP-100348 |
1053 |
4 |
CSG expiry Handling |
9.2.0 |
|
47 |
RP-100214 |
1056 |
1 |
Correction of CSFB |
9.2.0 |
|
48 |
RP-100592 |
1058 |
1 |
UTRAN Trace ID Abnormal Conditions |
9.3.0 |
|
48 |
RP-100595 |
1059 |
– |
Some Corrections to the Inbound Mobility Procedure |
9.3.0 |
|
48 |
RP-100599 |
1061 |
4 |
Introduction of IPv4 and Ipv6 Dual Stack option |
9.3.0 |
|
48 |
RP-100595 |
1063 |
1 |
Correct the description on the Relocation Failure handling |
9.3.0 |
|
48 |
RP-100599 |
1064 |
3 |
Release 7 QoS subscription data for Pre-Release 7 UE |
9.3.0 |
|
48 |
RP-100599 |
1067 |
1 |
Enhancement of Location Reporting functionality interaction with Enhanced Relocation |
9.3.0 |
|
49 |
RP-100907 |
1074 |
– |
Correction of Forwarding TNL IE for Enhanced Relocation |
9.4.0 |
|
49 |
RP-100907 |
1075 |
– |
Correction of the interaction between CN Invoke Trace and Enhanced Relocation |
9.4.0 |
|
49 |
RP-100907 |
1076 |
– |
Correction of inconsistencies between tabular, procedural text and ASN.1 code for Enhanced Relocation |
9.4.0 |
|
50 |
RP-101269 |
1081 |
Correction of Inter-system SRVCC |
9.5.0 |
|
|
12/2010 |
Rel-10 version created based on v9.5.0 |
10.0.0 |
|||
|
50 |
RP-101389 |
1084 |
Introduction of the SIPTO at Iu-PS Function |
10.0.0 |
|
|
50 |
RP-101389 |
1086 |
2 |
LIPA Impact In RAN3 |
10.0.0 |
|
50 |
RP-101304 |
1087 |
2 |
Inter-RAT MRO for Detection of too early inter-RAT handover with no RLF |
10.0.0 |
|
01/2011 |
Editorial change: highlighting removed |
10.0.1 |
|||
|
SP-49 |
SP-100629 |
Clarification on the use of References (TS 21.801 CR#0030) |
10.1.0 |
||
|
51 |
RP-110226 |
1090 |
Correction to Integrity Protection Information and Encryption Information |
10.1.0 |
|
|
51 |
RP-110239 |
1091 |
1 |
Addition of MeasurementBandwidth and ASN.1 clean-up for IRAT measurement configuration |
10.1.0 |
|
51 |
RP-110230 |
1094 |
1 |
Introduction of MDT |
10.1.0 |
|
51 |
RP-110231 |
1095 |
1 |
Additional IEs needed to support optimized HNB-HNB mobility |
10.1.0 |
|
51 |
RP-110233 |
1096 |
3 |
Introduction of Low Priority Traffic Overload support |
10.1.0 |
|
51 |
RP-110226 |
1099 |
2 |
Clarification on TEID value range for RANAP |
10.1.0 |
|
51 |
RP-110225 |
1100 |
1 |
the description usage of NONCE in RNC |
10.1.0 |
|
52 |
RP-110695 |
1104 |
3 |
User consent indication for MDT in RANAP |
10.2.0 |
|
52 |
RP-110713 |
1111 |
1 |
Clarification to detection of unnecessary IRAT handover |
10.2.0 |
|
52 |
RP-110681 |
1114 |
2 |
Correction of SRVCC from LTE to UMTS |
10.2.0 |
|
52 |
RP-110684 |
1115 |
– |
Correction of References |
10.2.0 |
|
52 |
RP-110686 |
1116 |
2 |
General clean-up before Rel-10 ASN.1 closure |
10.2.0 |
|
52 |
RP-110695 |
1118 |
2 |
MDT UTRAN amendments |
10.2.0 |
|
53 |
RP-111197 |
1120 |
1 |
Addition of SRVCC preparation into message type tabular |
10.3.0 |
|
53 |
RP-111195 |
1122 |
– |
Correct definition of condition IfM2 in MDT Configuration |
10.3.0 |
|
53 |
RP-111195 |
1123 |
3 |
Clarification on MDT Recording Session Reference in MDT Configuration |
10.3.0 |
|
53 |
RP-111195 |
1124 |
2 |
Area scope RAI list in MDT configuration |
10.3.0 |
|
53 |
RP-111195 |
1130 |
2 |
Definition of value of bit in Measurements to Activate |
10.3.0 |
|
53 |
RP-111193 |
1132 |
2 |
Correction of Rel-7 QoS handling for Pre-Rel-7 UEs |
10.3.0 |
|
53 |
RP-111196 |
1133 |
– |
Correction of some generic references to dated references |
10.3.0 |
|
53 |
RP-111195 |
1134 |
1 |
Small correction on unnecessary IRAT HO |
10.3.0 |
|
53 |
RP-111198 |
1139 |
– |
Alignment of the transparent containers’ IE names with CT4 specifications |
10.3.0 |
|
54 |
RP-111651 |
1140 |
– |
Introduction of the annex on the processing of transparent containers at SGSN |
10.4.0 |
|
54 |
RP-111649 |
1141 |
2 |
Addition of TCE IP in CN INVOKE TRACE |
10.4.0 |
|
54 |
RP-111646 |
1143 |
– |
Correction of Emergency Call |
10.4.0 |
|
54 |
RP-111651 |
1148 |
1 |
Fast Return after CSFB |
10.4.0 |
|
54 |
RP-111651 |
1149 |
1 |
Correction of Routing |
10.4.0 |
|
55 |
RP-120232 |
1153 |
1 |
Correction on unnecessary HO |
10.5.0 |
|
56 |
RP-120743 |
1166 |
1 |
Correction to assigned criticality of L-GW Transport Layer Address |
10.6.0 |
|
56 |
RP-120752 |
1167 |
1 |
Introduction of the new IE for cell reselection from UTRA connected mode |
11.0.0 |
|
56 |
RP-120752 |
1172 |
1 |
Improved granularity for the time UE stayed in cell |
11.0.0 |
|
57 |
RP-121130 |
1177 |
2 |
Correction on handover to a CSG cell with an emergency call |
11.1.0 |
|
57 |
RP-121135 |
1190 |
2 |
Addition of HO cause value to the UE history information in RANAP |
11.1.0 |
|
57 |
RP-121140 |
1194 |
3 |
Introduction of UE Radio Capability Match procedure |
11.1.0 |
|
57 |
RP-121140 |
1195 |
1 |
Introduction of Anonymization of MDT data for area based MDT in UTRAN |
11.1.0 |
|
58 |
RP-121736 |
1196 |
– |
ASN.1 correction |
11.2.0 |
|
58 |
RP-121736 |
1197 |
– |
Improved granularity for the time UE stayed in cell for enhanced relocation |
11.2.0 |
|
58 |
RP-121728 |
1198 |
– |
Introduction of rSRVCC |
11.2.0 |
|
58 |
RP-121728 |
1202 |
2 |
Introduction of the support for rSRVCC network sharing |
11.2.0 |
|
58 |
RP-121737 |
1203 |
– |
Rapporteur editorial corrections |
11.2.0 |
|
58 |
RP-121730 |
1204 |
2 |
Multi-PLMN MDT |
11.2.0 |
|
58 |
RP-121732 |
1208 |
1 |
Introduction of connectivity between HNB and RNC via HNB-GW for RNSAP signaling: Enhanced Relocation between HNB and RNC |
11.2.0 |
|
58 |
RP-121730 |
1209 |
2 |
Introduction of new MDT measurements |
11.2.0 |
|
58 |
RP-121739 |
1211 |
2 |
New Information for BBF access |
11.2.0 |
|
58 |
RP-121736 |
1214 |
2 |
Clarification of E-UTRAN Service Handover IE for inter-RAT roaming restrictions |
11.2.0 |
|
59 |
RP-130207 |
1217 |
– |
Addition of missing values for MDT report interval |
11.3.0 |
|
59 |
RP-130224 |
1219 |
– |
Introduction of the missing ASN.1 definition for Timing Difference UL-DL IE |
11.3.0 |
|
59 |
RP-130212 |
1220 |
3 |
ASN.1 review for RANAP |
11.3.0 |
|
59 |
RP-130206 |
1222 |
1 |
Correction of rSRVCC capability indicator |
11.3.0 |
|
59 |
RP-130211 |
1223 |
2 |
Addition of TCE IP and Cell Identifier for Anonymization MDT |
11.3.0 |
|
59 |
RP-130237 |
1224 |
1 |
Extending maxEARFCN |
11.3.0 |
|
60 |
RP-130638 |
1225 |
– |
Clarification on Positioning Data Discriminator IE |
11.4.0 |
|
60 |
RP-130643 |
1226 |
– |
Correction of BBAI information |
11.4.0 |
|
60 |
RP-130637 |
1227 |
1 |
Provide IMEISV to RNC to identify UE characteristics |
11.4.0 |
|
60 |
RP-130643 |
1228 |
2 |
Resolution of ambiguity around reject causes in MOCN |
11.4.0 |
|
60 |
RP-130643 |
1234 |
2 |
Redirect indication for NAS rejection cause #17 and #25 |
11.4.0 |
|
60 |
RP-130643 |
1235 |
2 |
Clarification on CS/PS coordination |
11.4.0 |
|
60 |
RP-130639 |
1238 |
1 |
Correction of SRVCC procedure in case of PS handover failure |
11.4.0 |
|
62 |
RP-131902 |
1251 |
2 |
Correction on relocation with an emergency call |
11.5.0 |
|
62 |
RP-131909 |
1239 |
5 |
Introduction of Collocated L-GW for SIPTO@LN |
12.0.0 |
|
62 |
RP-131913 |
1258 |
– |
Clarification on the duplicated PLMN Identities |
12.0.0 |
|
62 |
RP-131906 |
1259 |
1 |
Introduction of support for BDS |
12.0.0 |
|
62 |
RP-131909 |
1260 |
2 |
Introduction of SIPTO@LN Stand-Alone in RANAP |
12.0.0 |
|
63 |
RP-140297 |
1253 |
4 |
Restoration of MBMS Bearer Services and Connections in RNC |
12.1.0 |
|
63 |
RP-140294 |
1262 |
1 |
Introduction of Last E-UTRAN PLMN Identity for CSFB |
12.1.0 |
|
64 |
RP-140905 |
1271 |
– |
Corrections on MBMS Restoration |
12.2.0 |
|
66 |
RP-142093 |
1285 |
1 |
Rapporteur Review |
12.3.0 |
|
66 |
RP-142094 |
1288 |
1 |
Introduction of the increased value range for RSRQ and new RSRQ definition |
12.3.0 |
|
66 |
RP-142084 |
1289 |
1 |
BDS Satellite Specific ICD update to version 2.0 |
12.3.0 |
|
67 |
RP-150356 |
1290 |
– |
Correction of RSRQ type values |
12.4.0 |
|
67 |
RP-150356 |
1291 |
1 |
Rapporteur Review-ASN.1 consistency check |
12.4.0 |
|
70 |
RP-152088 |
1294 |
7 |
Introduction of improvements to CS/PS coordination in UTRAN Shared Network |
13.0.0 |
|
70 |
RP-152108 |
1298 |
2 |
Enhancement of the RESET RESOURCE procedure |
13.0.0 |
|
70 |
RP-152096 |
1303 |
5 |
Introduction of Dedicated Core Network (DCN) feature |
13.0.0 |
|
70 |
RP-152092 |
1304 |
3 |
Support WI Power Saving enhancements for UMTS |
13.0.0 |
|
70 |
RP-152016 |
1307 |
4 |
RAT-Independent positioning enhancements for RANAP |
13.0.0 |
|
71 |
RP-160449 |
1308 |
– |
Rapporteur Review on 25.413 |
13.1.0 |
|
71 |
RP-160448 |
1310 |
1 |
Providing UE Usage Type in Dedicated Core Network Reroute NAS Request procedure |
13.1.0 |
|
72 |
RP-161047 |
1311 |
1 |
Removing signaling of NRI from MSC/SGSN to RNC for CS/PS coordination |
13.2.0 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
03/2017 |
RP-75 |
RP-170542 |
1317 |
|
B |
Introduction of New types of eNB ID |
14.0.0 |
|
03/2017 |
RP-75 |
RP-170544 |
1313 |
5 |
B |
Introduction of eDECOR in RAN |
14.0.0 |
|
03/2017 |
RP-75 |
RP-170545 |
1315 |
3 |
B |
Introduction of QMC for streaming services |
14.0.0 |
|
06/2017 |
RP-76 |
RP-171328 |
1318 |
– |
F |
QoE correction |
14.1.0 |
|
06/2017 |
RP-76 |
RP-171328 |
1320 |
2 |
F |
QoE enhancement during SRNS relocation |
14.1.0 |
|
06/2017 |
RP-76 |
RP-171328 |
1321 |
2 |
F |
Introduction of UE Application Layer Measurement Capability |
14.1.0 |
|
06/2018 |
RP-80 |
RP-181241 |
1323 |
2 |
F |
Introduction of QMC for MTSI in UTRAN |
15.0.0 |
|
2020-03 |
RP-87-e |
RP-200424 |
1325 |
5 |
B |
Support SRVCC from 5G to 3G |
16.0.0 |
|
2022-03 |
SA#95-e |
Promotion to Release 17 without technical change |
17.0.0 |
||||