From 39a6e57a85703b6922d9b13f416991fd1f500acd Mon Sep 17 00:00:00 2001 From: Luke Mewburn Date: Wed, 28 Sep 2022 11:43:02 +1000 Subject: [PATCH] TS 33.128 CR0412 - notes for pTCCCPDU vs nIDDCCPDU The CCPDU tag numbers for pTCCCPDU differ between Rel-16 and Rel-17: - In Rel-16: pTCCCPDU [4] PTCCCPDU - In Rel-17 and newer: nIDDCCPDU [4] NIDDCCPDU pTCCCPDU [5] PTCCCPDU Both types are OCTET STRING so a Rel-17 decoder should be able to decode a Rel-16 CCPDU. However, the meaning of the field differs. Add comment note to Rel-16 to not reuse CCPDU tag 5. --- 33128/r16/TS33128Payloads.asn | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/33128/r16/TS33128Payloads.asn b/33128/r16/TS33128Payloads.asn index 6576c098..05bdfbd2 100644 --- a/33128/r16/TS33128Payloads.asn +++ b/33128/r16/TS33128Payloads.asn @@ -254,7 +254,15 @@ CCPDU ::= CHOICE uPFCCPDU [1] UPFCCPDU, extendedUPFCCPDU [2] ExtendedUPFCCPDU, mMSCCPDU [3] MMSCCPDU, + + -- In Rel-17 and newer (threeGPP(4) ts33128(19) r17(17) version1(1)), + -- tag 4 is nIDDCCPDU and tag 5 is pTCCCPDU. + -- Rel-16 decoders should not decode tag 4 contents as PTCCCPDU if + -- r17 or newer is used in cCPayloadOID. pTCCCPDU [4] PTCCCPDU + + -- Tag 5 is reserved for pTCCCPDU in Rel-17 and newer. + } -- =========================== -- GitLab