3GPP Scout / Updates / Spec change

Spec changeSA #113TS 33.369

TS 33.369 V19.4.0 names the T-ID update operation and revises L0

Published 2026-10-16Updated 2026-10-163GPP TSG SA #113

At a glance

TS 33.369 V19.4.0 names the ADM's Nadm_SecTID_Update service operation in Ambient Internet of Things (IoT) security work item AmbientIoT-SEC.

What changed

Clause 5.4.4 covers out-of-sync detection and resynchronization of T-ID, the identifier handled in the device profile. The AIOTF requests that the ADM update the stored type T-ID through the ADM's Nadm_SecTID_Update service operation. The ADM follows Annex B.1, stores the updated identifier as T-ID_n in the Ambient IoT Device profile, and returns it. In version 19.3.0, the AIOTF requested a T-ID update from the ADM without naming a service operation. The editor's note in version 19.3.0 read: "The T-ID update service operation is to be updated." ZTE's CR 0103 resolved the editor's note on T-ID update.

Source: 3GPP TS 33.369 V19.3.0, clause 5.4.4. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/33_series/33.369/33369-j30.zip

Annex B.1 now defines L0, a length input in T-ID generation, as the "number of octets in P0". Previously, L0 measured the length of T-ID_n rather than the octet length of input parameter P0.

Source: 3GPP TS 33.369 V19.4.0, clause B.1. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/33_series/33.369/33369-j40.zip

Clause 5.2.2 now continues the TS 23.369 command procedure with steps 8 to 14 of clause 6.2.3. Previously, command steps 8 to 11 continued, while inventory steps 12 to 14 of clause 6.2.2 of TS 23.369 stayed unchanged.

ZTE's CR 0104 concerns alignment with the TS 23.369 command procedure. CR 0105 from Huawei and HiSilicon concerns term alignment on T-ID handling information. CR 0106 rev 1 from Huawei and HiSilicon concerns an input parameter for T-ID derivation.

Sources

  1. 3GPP TS 33.369 V19.4.0, clause 5.4.4. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/33_series/33.369/33369-j40.zip
  2. CR 0103 (S3-262922, ZTE): resolved the EN for T-ID update, approved in SP-260804 at SA #113. Source: 3GPP CR database.
  3. 3GPP TS 33.369 V19.3.0, clause 5.4.4. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/33_series/33.369/33369-j30.zip
  4. 3GPP TS 33.369 V19.4.0, clause B.1. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/33_series/33.369/33369-j40.zip
  5. 3GPP TS 33.369 V19.3.0, clause B.1. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/33_series/33.369/33369-j30.zip
  6. CR 0106 (S3-263447, Huawei, HiSilicon): Update to the input parameter of TID derivation, approved in SP-260804 at SA #113. Source: 3GPP CR database.
  7. 3GPP TS 33.369 V19.4.0, clause 5.2.2. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/33_series/33.369/33369-j40.zip
  8. 3GPP TS 33.369 V19.3.0, clause 5.2.2. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/33_series/33.369/33369-j30.zip
  9. CR 0104 (S3-262923, ZTE): alignment with command procedure in 23.369, approved in SP-260804 at SA #113. Source: 3GPP CR database.
  10. CR 0105 (S3-263122, Huawei, HiSilicon): term alignment on the T-ID handling information, approved in SP-260804 at SA #113. Source: 3GPP CR database.

How this page was made

Written with AI assistance from two versions of the specification indexed by 3GPP Scout and the 3GPP CR database. An AI model (GPT-6 Sol) drafted each sentence and named the source it rests on. Code checked every quote word for word against the stored source text, and the live check fetched each TDoc again before publishing. A second AI model from another company (Claude Opus 5.5) reviewed the page against the same sources. The 3GPP documents themselves govern.