3GPP 23.369 v20.0.0 — the document's own text
5.5 AIoT Device Profile Management
The ADM may hold AIoT Device Profile Data for the AIoT Device used in the network. If the AIoT Device is managed by the network, then the profile data for an AIoT Device is managed in the ADM, otherwise the corresponding profile data is stored external to the network.
The AIoT Device Permanent Identifier is used by the AIOTF together with local configuration, 3rd party related context to locate the entity which stores the profile data of an AIoT Device.
In case the AIoT Device is managed by the network, the AIOTF checks whether the AIoT Device Permanent Identifier from AIoT Device has the profile data in the network and retrieves the AIoT Device Profile Data. The AIoT Device Profile Data for AIoT Devices is different from the UE subscription data as defined in clause 5.2.3 of TS 23.502 [4], it is stored in the ADM network entity that exclusively supports management of AIoT Device Profile Data. The AIoT Device Permanent Identifier is the primary key for AIoT Device Profile Data in the ADM.
Optionally, the ADM stores AIoT Device Temporary Identifier(s) as described in TS 33.369 [9].
The table 5.5-1 below describes information storage structures for AIoT Device Profile Data.
Table 5.5-1: AIoT Device Profile Data
| Field | Description |
|---|---|
| AIoT Device Permanent Identifier | Uniquely identifies the AIoT Device. |
| AIoT Device Type | Indicates the type of the AIoT Device, i.e. indicating device is DO-A Capable AIoT Device or not, |
| Last known AIOTF information | Indicate the last known AIOTF that served the AIoT Device, or unknown |
| AIoT Device Temporary Identifier(s) | Temporary Identifier(s) may be stored as described in TS 33.369 [9]. |
| Serving AIOTF instance ID | Indicate the AIOTF that is currently serving the DO-A Capable AIoT Device, or unknown |
| Event Subscription information | Single or a list of event subscription information, each of which includes subscription requester ID (i.e. NEF ID or AF ID), the subscribed event ID(i.e. Uplink Application Container Transfer event, DO-A Capable AIoT Device Reachability notification), Notification Endpoint and subscription correlation ID. |
NOTE: In addition to the AIoT Device Profile Data, the ADM also manages AIoT Device security data including device credentials as specified in TS 33.369 [9].