From 6e3669e01a3af857e56a0cedad93744393e02f24 Mon Sep 17 00:00:00 2001 From: Luke Mewburn Date: Wed, 28 Sep 2022 12:01:42 +1000 Subject: [PATCH] TS 33.128 CR0413 - 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-17 and newer describing the difference. --- 33128/r17/TS33128Payloads.asn | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/33128/r17/TS33128Payloads.asn b/33128/r17/TS33128Payloads.asn index 1304ee37..212e8720 100644 --- a/33128/r17/TS33128Payloads.asn +++ b/33128/r17/TS33128Payloads.asn @@ -397,8 +397,14 @@ CCPDU ::= CHOICE uPFCCPDU [1] UPFCCPDU, extendedUPFCCPDU [2] ExtendedUPFCCPDU, mMSCCPDU [3] MMSCCPDU, + + -- In Rel-16 (threeGPP(4) ts33128(19) r16(16) version9(9)), + -- tag 4 is pTCCCPDU and tag 5 is not used. + -- Rel-17 or newer decoders should decode tag 4 contents as PTCCCPDU if + -- r16 is used in cCPayloadOID. nIDDCCPDU [4] NIDDCCPDU, pTCCCPDU [5] PTCCCPDU, + iMSCCPDU [6] IMSCCPDU } -- GitLab