6.2.2.2 Inventory procedure for DO-A Capable AIoT Device

Editor's note : Whether to call the procedure "inventory procedure", or using another name, is FFS.

The DO-A Capable AIoT Device shall have performed the registration procedure according to clause 6.2.6 and the serving AIOTF has stored the corresponding AIoT Device context. Only registered DO-A Capable AIoT Device monitors for paging messages.

Editor's note: Whether and how to perform power saving depends on RAN WGs.

This procedure follows the Inventory Procedure defined in clause 6.2.2.1 with the following differences:

• Step 1.

The information about the target AIoT Device(s) is either one or multiple AIoT Device Permanent Identities, or Filtering Information along with the External Target Area information.

Editor's note: Whether the AF can use Filtering information as information about the target AIoT Device is FFS.

• Step 2.

If one or multiple AIoT Device Permanent Identities are provided in step 1, the NEF selects/determines the serving AIOTF using the individual AIoT Device Permanent Identifier(s) when invoking Nadm_DM_Query service operation towards the ADM.

Editor's note: Whether the NEF can derive the individual AIoT Device Permanent Identities from the Filtering information is FFS.

• Step 3.

The NEF invokes the Naiotf_AIoT_Inventory service operation towards the selected serving AIOTF(s).

• Step 4.

When performing NG-RAN Node and RAN Reader selection as defined in clause 5.3.3, the AIOTF takes into account whether NG-RAN Nodes and RAN Readers support DO-A Capable AIoT Devices.

NOTE: The provisioning of the information whether NG-RAN Nodes and RAN Readers support DO-A Capable AIoT Devices can be performed by OAM.

If the information about the target AIoT Device(s) includes complete AIoT Device Identifier(s) then the AIOTF uses the AIoT Device Identifier(s) to determine whether it has an AIoT Device Contexts for those DO-A Capable AIoT Devices.

If no AIoT Device Contexts can be determined, a reject result is sent in step 5 and step 6 and the procedure stops.

For individual AIoT devices, the AIOTF retrieves the DO-A Capable AIoT Device Temporary Identifier(s) from the stored AIoT Device context(s), when AIoT Device Permanent Identifiers are provided in step 3.

The AIoT Identification Information to be provided to NG-RAN contains the DO-A Capable AIoT Device Temporary Identifier or the ID information for group inventory.

Editor's note: Whether and what ID Information for group inventory can be used will be coordinated with SA WG3.

• Step 7.

The AIOTF sends an Inventory Request message for each DO-A Capable AIoT Device including the DO-A Capable AIoT Device Temporary Identifier or ID information for group inventory as AIoT Identification Information received in step 4. No security parameters are included in the Inventory Request message.

Editor's note: Whether any specific authentication information is included in the NAS response and whether the AIoT Device Permanent Identifier can be used in the AIoT Device response will be decided by SA WG3.

• Step 9.

The AIoT Device includes its DO-A Capable AIoT Device Temporary Identifier.

• Step 11.

The AIOTF does not need to obtain the AIoT Device Permanent Identifier if it is already available in the AIoT Device context. If the AIOTF is not the serving AIOTF for a responding AIoT Device, the AIOTF sends the received DO-A Capable AIoT Device Temporary Identifier to the identified serving AIOTF (e.g. according to the DO-A Capable AIoT Device Temporary Identifier) for AIoT Device Permanent Identifier retrieval.

Editor's note: How the AIOTF performs authentication of the AIoT Device response will be determined by SA WG3.