Tech-invite  3GPPspace  IETFspace
◀  ▶  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.369  Word version:  19.1.0

Top   Top   Up   Prev   None
1…   4…   5…   6…   7… 
7 Network Functions Services  7.1 General  7.2 AIOTF services  7.2.1 General  7.2.2 Naiotf_AIoT_Inventory service operation  7.2.3 Naiotf_AIoT_Command service operation  7.2.4 Naiotf_AIoT_Notify service operation  7.3 AMF services  7.3.1 General  7.3.2 Namf_AIoT_MessageDelivery service operation  7.3.3 Namf_AIoT_Notify service operation  7.4 NEF services  7.4.1 General  7.4.2 Nnef_AIoT_Inventory service operation  7.4.3 Nnef_AIoT_Command service operation  7.4.4 Nnef_AIoT_Notify service operation  7.5 ADM services  7.5.1 General  7.5.2 Nadm_DM_Query service operation  7.5.3 Nadm_DM_Update service operation  7.6 UDR Services  7.6.1 Nudr_DataManagement (DM) Service  $ Change history 

 

7  Network Functions Services  p. 32

7.1  General  p. 32

The following clauses provide for each involved NF the NF services it exposes through its service-based interfaces for AIoT Services.

7.2  AIOTF services  p. 32

7.2.1  General  p. 32

The AIOTF supports to expose AIoT services towards the AF or the NEF as described in Table 7.2.1-1.
Service Name Service Operations Operation Semantics Example Consumer(s)
Naiotf_AIoTInventoryRequest/ResponseNEF, AF
CommandRequest/ResponseNEF, AF
NotifySubscribe/NotifyNEF, AF
Up

7.2.2  Naiotf_AIoT_Inventory service operation  p. 33

Service operation name:
Naiotf_AIoT_Inventory.
Description:
The NF consumer requests an inventory operation for one or multiple AIoT Device(s).
Inputs, Required:
  1. AF ID.
  2. At least one of the following parameters are included:
    • Target Area information for the inventory operation.
    • Information about the target AIoT Device(s):
    • either the AIoT Device ID(s) or the filtering information(see clause 5.8) for multiple target AIoT Devices.
  3. Notification Endpoint.
Inputs, Optional:
  1. Information to be used for resource allocation:
    • Approximate number of AIoT Devices.
  2. Time Interval for result aggregation.
  3. Location information requested.
Outputs, Required:
Transaction ID, Result indication (Success or Failure), Failure Cause in case of Failure.
Outputs, Optional:
None.
Up

7.2.3  Naiotf_AIoT_Command service operation  p. 33

Service operation name:
Naiotf_AIoT_Command.
Description:
The NF consumer requests a command operation for one or multiple AIoT Device(s).
Inputs, Required:
  1. AF ID.
  2. At least one of the following parameters are included:
    • Target Area information for the command operation.
    • Information about the target AIoT Device(s):
    • either the AIoT Device ID(s) or the filtering information(see clause 5.8) for multiple AIoT Devices.
  3. Notification Endpoint.
  4. Command Type: Read, Write or Permanent Disable.
Inputs, Optional:
Information to be used for resource allocation:
  • Approximate number of AIoT Devices.
  • Approximate message size from the AIoT Device for Read Operation.
  • If the Command Type is Read, the offset to read application data from and the length of application data to read shall be included.
  • If the Command Type is Write, the offset where to write the application data, the application data to write and its length shall be included.
  • Location information requested.
Outputs, Required:
Transaction ID, Result indication (Success or Failure), Failure Cause in case of Failure.
Outputs, Optional:
None.
Up

7.2.4  Naiotf_AIoT_Notify service operation  p. 34

Service operation name:
Naiotf_AIoT_Notify
Description:
The AIOTF uses this service operation to notify the results or status of the service operation towards the NF consumers. If the NF consumer invokes the Naiotf_AIoT_Inventory, or Naiotf_AIoT_Command service operation, the NF consumer implicitly subscribes to the results of the requested service operation.
Inputs, Required:
  1. Common report information: Transaction ID.
Inputs, Optional:
  1. List of AIoT Device ID or Failure Cause in case of Failure.
  2. Read command specific report information: Information obtained from each target AIoT Device corresponding to each reported AIoT Device ID.
  3. The Last Report Indication, indicating the notify is the last notify for an AIoT service operation.
  4. Location information of each AIoT Device.
Outputs, Required:
Operation execution result indication.
Outputs, Optional:
None.
Up

7.3  AMF services  p. 34

7.3.1  General  p. 34

AMF supports to expose AIoT services towards the AIOTF as described in Table 7.3.1-1. The Namf_AIoT AMF service is used when the NG-RAN and the AIoTF communicate indirectly via an AMF.
Service Name Service Operations Operation Semantics Example Consumer(s)
Namf_AIoTMessageDeliveryRequest/ResponseAIOTF
NotifySubscribe/NotifyAIOTF
Up

7.3.2  Namf_AIoT_MessageDelivery service operation  p. 34

Service operation name:
Namf_AIoT_MessageDelivery
Description:
The NF consumer requests to send AIoT data towards NG-RAN or AIoT devices.
Inputs, Required:
  1. NGAP AIoT Information to deliver to NG-RAN.
  2. NG-RAN ID.
  3. AIoT NGAP Message Type ("Inventory" or "Command").
  4. AIOTF Identifier and Correlation Identifier, this is to allow identifying the association between NG-RAN and AMF.
Outputs, Required:
Result indication (Success or Failure), Failure Cause in case of Failure.
Up

7.3.3  Namf_AIoT_Notify service operation  p. 35

Service operation name:
Namf_AIoT_Notify
Description:
The NF consumer requests to receive AIoT data from NG-RAN or AIoT devices. If the NF consumer invokes the Namf_AIoT_MessageDelivery, the NF consumer implicitly subscribes to receive the AIoT data from NG-RAN or AIoT devices.
Inputs, Required:
  1. NGAP Information received from NG-RAN.
Input, Optional:
None.
Outputs, Required:
Operation execution result indication.
Output, Optional:
None.
Up

7.4  NEF services  p. 35

7.4.1  General  p. 35

In addition to those defined in clause 7.2.8 of TS 23.501 and clause 5.2.6 of TS 23.502, Table 7.4.1-1 illustrates additional NEF services to support AIoT.
Service Name Service Operations Operation Semantics Example Consumer(s)
Nnef_AIoTInventoryRequest/ResponseAF
CommandRequest/ResponseAF
NotifySubscribe/NotifyAF
Up

7.4.2  Nnef_AIoT_Inventory service operation  p. 35

Service operation name:
Nnef_AIoT_Inventory
Description:
The consumer requests to perform an inventory operation for an AIoT Device or multiple AIoT Devices.
Input, Required:
  1. AF ID.
  2. At least one of the following parameters are included:
    • External Target Area information.
    • Either AIoT Device ID(s) or AIoT Device ID filter information for the inventory operation.
  3. Notification Endpoint.
Input, Optional:
Approximate number of AIoT Devices, time interval, location information requested.
Output, Required:
AF Transaction ID, Result indication, Failure cause in case of Failure.
Output, Optional:
None.
Up

7.4.3  Nnef_AIoT_Command service operation  p. 36

Service operation name:
Nnef_AIoT_Command
Description:
The consumer requests to perform a command operation for an AIoT Device or multiple AIoT Devices.
Input, Required:
  1. AF ID.
  2. At least one of the following parameters are included:
    • External Target Area information.
    • Either AIoT Device ID(s) or AIoT Device ID filter information for the command operation.
  3. Notification Endpoint.
  4. Command type (Read, Write, or Permanent Disable).
Input, Optional:
Approximate number of AIoT Devices, if the Command Type is Read, the offset to read application data from and the length of application data to read shall be included, if the Command Type is Write the offset where to write the application data, the application data to write and its length shall be included, Approximate message size from the AIoT Device for Read command type, location information requested.
Output, Required:
AF Transaction ID, Result indication, Failure cause in case of Failure.
Output, Optional:
None.
Up

7.4.4  Nnef_AIoT_Notify service operation  p. 36

Service operation name:
Nnef_AIoT_Notify
Description:
The consumer receives notification of the status or results of the requested service operation. If the consumer invokes the Nnef_AIoT_Inventory, or Nnef_AIoT_Command service operation, the consumer implicitly subscribes to the results of the requested service operation.
Input, Required:
  1. AF Transaction ID.
Input, Optional:
  1. a list of AIoT Device ID(s), Failure Cause in case of Failure.
  2. Read command specific report information: Information obtained from each target AIoT Device.
  3. The Last Report Indication, indicating the notify is the last notify for an AIoT service operation.
  4. Location information of each target AIoT Device.
Output, Required:
Result indication.
Output, Optional:
None.
Up

7.5  ADM services  p. 36

7.5.1  General  p. 36

The following Table shows the Nadm_DM Service and Service Operations.
Service Name Service Operations Operation Semantics Example Consumer(s)
Nadm_DMQueryRequest/ResponseAIOTF, NEF
UpdateRequest/ResponseAIOTF
Up

7.5.2  Nadm_DM_Query service operation  p. 37

Service operation name:
Nadm_DM_Query
Description:
NF service consumer may request the AIoT device profile data or the AF authorization data from the ADM.
Inputs, Required:
AIoT Device Permanent ID or AF ID.
Input, Optional:
None.
Outputs, Required:
the AIoT device profile data or the AF authorization data.
Output, Optional:
None.

7.5.3  Nadm_DM_Update service operation  p. 37

Service operation name:
Nadm_DM_Update
Description:
NF service consumer may update the AIoT device profile data in the ADM.
Inputs, Required:
AIoT Device Permanent ID, updated AIoT device profile data.
Input, Optional:
None.
Outputs, Required:
Result indication (Success or Failure), Failure Cause in case of Failure.
Output, Optional:
None.

7.6  UDR Services  p. 37

7.6.1  Nudr_DataManagement (DM) Service  p. 37

7.6.1.1  General  p. 37

The ADM makes use of the Nudr_DM service for Ambient IoT Data, as described in clause 5.2.12 of TS 23.502.
The Ambient IoT Data includes AIoT Device Profile Data and AF Authorization Data. The AIoT Device Permanent ID is the Data Key of AIoT Device Profile Data, while the AF ID is the Data Key of AF Authorization Data, as illustrated in Table 7.6.1.1-1.
Data Set Data Subset Data Key Data Sub Key
Ambient IoT DataAIoT Device Profile DataAIoT Device Permanent ID-
AF Authorization DataAF ID-
Up

$  Change history  p. 38

Up   Top