The 5G Standard

3GPP Specification Change Requests

Go to spec numbering scheme page

Back to series index

Back to spec details

Go to current work plan


3GPP Specification Change Request records for: 25.323

CR no. rev cat Release CR written to vers new vers CR title TSG meeting TSG doc TSG status source WG meeting WG doc WG status cover date work item remarks database record created
0004 - F R99 3.0.0 3.1.0 Bit order of PDCP PDUs RP-07 RP-000041 approved R2 R2-11 R2‑000620 agreed 2000‑03‑02 - -
0005 - F R99 3.0.0 3.1.0 Changes to PDCP RP-07 RP-000041 approved R2 R2-11 R2‑000636 agreed 2000‑02‑28 - -
0006 4 F R99 3.1.0 3.2.0 Changes in PDCP PDU format due to PDCP sequence numbering RP-08 RP-000221 approved R2 R2-13 R2‑001238 agreed 2000‑05‑24 - -
0009 3 F R99 3.2.0 3.3.0 Clarification of PDCP Sequence Numbering RP-09 RP-000359 approved R2 R2-14 R2‑001534 agreed 2000‑07‑03 - -
0011 - F R99 3.2.0 3.3.0 Clarification on how to handle invalid PDUs RP-09 RP-000359 approved R2 R2-15 R2‑001524 agreed 2000‑07‑03 - -
0012 2 F R99 3.2.0 3.3.0 Primitives required for SRNS relocation RP-09 RP-000359 approved R2 R2-15 R2‑001858 agreed 2000‑08‑21 - -
0015 - F R99 3.2.0 3.3.0 Handling of invalid PDCP PDU sequence number RP-09 RP-000359 approved R2 R2-15 R2‑001829 agreed 2000‑07‑03 - -
0017 2 B Rel-4 3.3.0 4.0.0 Robust Header Compression RP-11 RP‑010039 approved R2 R2-19 R2‑010763 agreed 2001‑03‑07 RANimp-RABSE 0
0018 1 F R99 3.3.0 3.4.0 Editorial Corrections RP-11 RP‑010027 approved R2 R2-19 R2‑010684 agreed 2001‑02‑19 - 0
0019 1 F R99 3.3.0 3.4.0 Updates necessary for Rel-4 specification RP-11 RP‑010027 approved R2 R2-19 R2‑010706 agreed 2001‑02‑19 - 0
0020 1 F R99 3.4.0 3.5.0 Clarification on PDCP Sequence numbering RP-12 RP‑010310 approved R2 R2-21 R2‑011321 agreed 2001‑05‑22 TEI 0
0021 - A Rel-4 4.0.0 4.1.0 Clarification on PDCP Sequence numbering RP-12 RP‑010310 approved R2 R2-21 R2‑011355 agreed 2001‑05‑24 TEI 0
0026 - F Rel-4 4.1.0 4.2.0 Selection of the RFC 3095 CID transmission RP-13 RP‑010553 approved R2 R2-23 R2‑011851 agreed 2001‑07‑05 RANimp-RABSE -
0027 - F R99 3.5.0 3.6.0 Header compression protocol reinitialisation during SRNS relocation RP-13 RP‑010543 approved R2 R2-23 R2‑011893 agreed 2001‑08‑18 TEI -
0028 - A Rel-4 4.1.0 4.2.0 Header compression protocol reinitialisation during SRNS relocation RP-13 RP‑010543 approved R2 R2-23 R2‑012164 agreed 2001‑08‑27 TEI -
0029 1 F R99 3.5.0 3.6.0 PDCP SDU Sequence Numbering RP-13 RP‑010543 approved R2 R2-23 R2‑012167 agreed 2001‑08‑30 TEI -
0030 - A Rel-4 4.1.0 4.2.0 PDCP SDU Sequence Numbering RP-13 RP‑010543 approved R2 R2-23 R2‑012194 agreed 2001‑08‑30 TEI -
0035 1 F R99 3.5.0 3.6.0 Corrections to PDCP RP-13 RP‑010543 approved R2 R2-23 R2‑012165 agreed 2001‑08‑27 TEI -
0036 - A Rel-4 4.1.0 4.2.0 Corrections to PDCP RP-13 RP‑010543 approved R2 R2-23 R2‑012166 agreed 2001‑08‑27 TEI -
0037 - - R99 - - General PDCP corrections - - - - R2-25 R2‑012541 revised TEI -
0037 1 F R99 3.6.0 3.7.0 General PDCP corrections RP-14 RP‑010762 approved R2 R2-25 R2‑012658 agreed 2001‑11‑28 TEI -
0038 - A Rel-4 4.2.0 4.3.0 General PDCP corrections RP-14 RP‑010762 approved R2 R2-25 R2‑012659 agreed 2001‑11‑28 TEI -
0039 - F Rel-4 4.2.0 4.3.0 Management of Full Header transmission RP-14 RP‑010772 approved R2 R2-25 R2‑012629 agreed 2001‑11‑29 TEI4 -
0040 - - R99 - - Meaning of version fields for full header packet type in RFC2507 - - - - R2-27 R2‑020235 withdrawn TEI -
0041 - A Rel-4 - - Meaning of version fields for full header packet type in RFC2507 - - - - R2-27 not agreed withdrawn TEI -
0042 - - R99 - - Clarification on PDCP sequence numbering - - - - R2-27 R2‑020237 revised TEI -
0042 1 F R99 3.7.0 3.8.0 Clarification on PDCP sequence numbering RP-15 RP‑020069 approved R2 R2-27 R2‑020411 agreed 2002‑02‑18 TEI -
0043 - A Rel-4 4.3.0 4.4.0 Clarification on PDCP sequence numbering RP-15 RP‑020069 approved R2 R2-27 R2‑020588 agreed 2002‑02‑23 TEI -
0044 - - Rel-4 - - Clarification on handling of erroneous PDCP PDUs - - - - R2-27 R2‑020239 - TEI4 -
0045 - - Rel-4 - - Mismatches between Rel-4 and R'99 in PDCP - - - - R2-27 R2‑020245 - TEI4 -
0046 - - Rel-5 - - RFC 3095 context relocation - - - - R2-27 R2‑020283 - RANimp-RABSE5 -
0047 - F R99 3.8.0 3.9.0 Clarification on PDCP sequence number synchronization procedure RP-16 RP‑020328 approved R2 R2-29 R2‑021241 agreed 2002‑05‑16 TEI -
0048 - A Rel-4 4.4.0 4.5.0 Clarification on PDCP sequence number synchronization procedure RP-16 RP‑020328 approved R2 R2-29 R2‑021242 agreed 2002‑05‑16 TEI -
0049 - A Rel-5 5.0.0 5.1.0 Clarification on PDCP sequence number synchronization procedure RP-16 RP‑020328 approved R2 R2-29 R2‑021243 agreed 2002‑05‑16 TEI -
0050 - B Rel-5 5.0.0 5.1.0 RFC 3095 context relocation RP-16 RP‑020345 approved R2 R2-29 R2‑021465 agreed 2002‑05‑14 RANimp-RABSE5 -
0051 - F R99 3.9.0 3.10.0 Mapping relation between PDCP and RLC RP-17 RP‑020540 approved R2 R2-30 R2‑022366 agreed 2002‑08‑23 TEI -
0052 - A Rel-4 4.5.0 4.6.0 Mapping relation between PDCP and RLC RP-17 RP‑020540 approved R2 R2-30 R2‑022367 agreed 2002‑08‑23 TEI -
0053 - A Rel-5 5.1.0 5.2.0 Mapping relation between PDCP and RLC RP-17 RP‑020540 approved R2 R2-30 R2‑022368 agreed 2002‑08‑23 TEI -
0054 - F Rel-4 4.5.0 4.6.0 Corrections to RFC3095 operation RP-17 RP‑020552 approved R2 R2-31 R2‑022378 agreed 2002‑08‑23 RANimp-RABSE -
0055 - A Rel-5 5.1.0 5.2.0 Corrections to RFC3095 operation RP-17 RP‑020552 approved R2 R2-31 R2‑022379 agreed 2002‑08‑23 RANimp-RABSE -
0056 - F Rel-4 4.5.0 4.6.0 Mismatches between Rel4 and R99 in PDCP RP-17 RP‑020552 approved R2 R2-31 R2‑022380 agreed 2002‑08‑23 TEI4 -
0057 - A Rel-5 5.1.0 5.2.0 Mismatches between Rel4 and R99 in PDCP RP-17 RP‑020552 approved R2 R2-31 R2‑022381 agreed 2002‑08‑23 TEI4 -

page generated from database: 2024-04-22 07:58:53