5.3.3 NG-RAN Node and RAN Reader Selection

The AIOTF selects NG-RAN node(s) and optionally RAN Readers based on the configured NG-RAN configuration information and the received AIoT service operation request. The AIOTF may also select a RAN Reader based on the stored last known RAN Reader information.

The AIOTF obtains the NG-RAN configuration information that can be used for selection. For each NG-RAN node, the following is provided:

• Served AIoT Area ID List of the NG-RAN node: The AIoT Areas that are not configured in the RAN Reader List, e.g. when RAN Reader List is not configured.
• RAN Reader List: For each RAN Reader, the following information is provided:
• Served AIoT Area ID List of the RAN Reader.
• Optionally, location information.

For each NG-RAN node, the AIOTF obtains a served AIoT Area ID List of the NG-RAN node, a RAN Reader List, or both. The provisioning of the NG-RAN configuration information can be performed via OAM or local configuration.

When the AIOTF receives an AIoT service operation request, based on the received Target Area information in the AIoT service operation request and the NG-RAN configuration information, the AIOTF selects the NG-RAN node(s) and optionally RAN Reader(s) to handle the request and the AIOTF determines a Requested Service Area Information for each selected NG-RAN node. The Requested Service Area Information provided by the AIOTF to each selected NG-RAN node can be empty, or includes a list of AIoT Area IDs, a list of RAN Reader IDs, or both a list of AIoT Area IDs and a list of RAN Reader IDs. How the NG-RAN node determines RAN Readers based on the Requested Service Area Information is specified in TS 38.300 [5].

NOTE 1: The Target Area information in a received AIoT service operation request can span multiple NG-RAN node(s) or can be a subset of the supported AIoT areas of a single NG-RAN node.

The AIOTF sends the AIoT service operation request to each selected NG-RAN node, either directly or through the selected AMF, including the Requested Service Area Information for the NG-RAN node.

If an AIoT service operation request received by the AIOTF includes individual target AIoT Device Permanent ID(s), the AIOTF may consider the last known serving RAN Reader, if available from the AIoT Device context to determine the NG-RAN node and RAN Reader(s) for the request. In this case the last known serving RAN Reader ID is sent as the Requested Service Area to the selected NG-RAN node.

NOTE 2: The RAN Reader ID is not exposed to the AF.

NOTE 3: An AIOTF receives the Inventory Report from an NG-RAN node includes a RAN Reader ID that represents the AIoT Device’s location at Reader granularity.

NOTE 4: The AIOTF uses the RAN Reader ID and the NG-RAN node to update the last known serving RAN Reader information in the local AIoT Device context.