|
| 36.101 | 2977 | 1 | F | 12.7.0 | Rel-12 | CR on corrections to D2D RF core requirements |
R4-153728
| agreed | RAN4#75 | |
RP-150957
| approved | RAN#68 | R4 | 12.8.0 | LTE_D2D_Prox |
|
|
| 36.101 | 2977 | - | F | | Rel-12 | CR on corrections to D2D RF core requirements |
R4-153075
| revised | RAN4#75 | |
| | | | | LTE_D2D_Prox |
|
|
| 36.101 | 2973 | 1 | F | 12.7.0 | Rel-12 | Corrections to EVM requirements for ProSe and Annex F of 36.101 |
R4-153727
| agreed | RAN4#75 | |
RP-150957
| approved | RAN#68 | R4 | 12.8.0 | LTE_D2D_Prox |
|
|
| 36.101 | 2973 | - | F | | Rel-12 | Corrections to EVM requirements for ProSe and Annex F of 36.101 |
R4-152977
| revised | RAN4#75 | |
| | | | | LTE_D2D_Prox |
|
|
| 36.101 | 2910 | 1 | F | 12.7.0 | Rel-12 | Clarification on RMC for D2D UE |
R4-152434
| agreed | RAN4#74-BIS | |
RP-150957
| approved | RAN#68 | R4 | 12.8.0 | LTE_D2D_Prox |
|
|
| 36.101 | 2910 | - | F | 12.7.0 | Rel-12 | Clarification on RMC for D2D UE |
R4-151926
| revised | RAN4#74-BIS | |
| | | | | LTE_D2D_Prox |
|
|
| 36.133 | 2896 | - | F | 12.7.0 | Rel-12 | CR on editorial corrections/clarifications for D2D |
R4-151866
| noted | RAN4#74-BIS | |
| | | | | LTE_D2D_Prox |
|
|
| 36.212 | 0162 | 1 | B | 12.2.0 | Rel-12 | Introduction of D2D feature into 36.212 |
R1-144505
| revised | RAN1#78-BIS | Huawei |
| | | R1 | | LTE_D2D_Prox |
|
|
| 36.212 | 0162 | - | B | 12.2.0 | Rel-12 | Introduction of D2D feature into 36.212 |
R1-143697
| revised | RAN1#78-BIS | Huawei |
| | | R1 | | LTE_D2D_Prox |
|
|
| 36.322 | 0113 | - | F | 12.3.0 | Rel-12 | Clarification on BSR for data available for transmission |
R2-156325
| not pursued | RAN2#92 | Innovative Tech... |
| | | | | LTE_D2D_Prox |
|
|
| 36.323 | 0147 | - | F | 12.4.0 | Rel-12 | Clarification on BSR for data available for transmission |
R2-156331
| not pursued | RAN2#92 | Innovative Tech... |
| | | | | LTE_D2D_Prox |
|