3 Signaling API Specifications

This section describes signaling API specifications

3.1 Operations Supported for NEF Data

This section provides information about the operations supported for NEF Data.

All APIs are supported as per TS29.519 v16.8.0 on UDR. Sample payloads are as follow:

• GET - Access and Mobility Data
• PUT - Access and Mobility Data
• GET - PDUSessionManagementData
• PUT - PDU Session Management Data
• POST - ExposureDataSubscription
• PUT - ExposureDataSubscription

3.2 Operations Supported for EIR Data

This section provides information about the operations supported for EIR Data.

All APIs are supported as per TS 29.511v16 on UDR. Sample payloads are as follow:

• GET-equipment-status

3.3 Operations Supported for PCF Data

This section provides information about the operations supported for PCF Data (PCF as consumer).

All APIs are supported as per TS29.519 v16.8.0 on UDR. Sample payloads are as follow:

• PATCH-SessionManagementPolicyData
• PUT-UEPolicySet
• PUT-UEPolicySet
• PUT-UsageMonitoringInformation

3.3.1 Subscription Operations for Policy Data

This section provides information about the subscription operations for policy data.

All APIs are supported as per TS29.519 v16.8.0 on UDR. Sample payloads are as below:

• POST-Subscription Operations
• PUT-Subscription Operations
• PUT-Subscription Operations

3.3.2 Subscription Notification Formats for PCF Data

This section provides information about the subscription notification formats for PCF data

All APIs are supported as per TS29.519 v16.8.0 on UDR. Sample payloads are as below:

• PUT or PATCH - Subscription Notification
• DELETE DATA - Subscription Notification
• DELETE SUBSCRIBER - Subscription Notification

3.4 Operations Supported for SLF Data

This section provides information about operations supported for SLF Data feature.

All APIs are supported as per 3GPP TS 29.504 v16.2.0 on UDR. Sample payloads are as follow:

• GET-Subscriber ID

3.5 Operations Supported for UDM Data

This section provides information about the operations supported for UDM data

All APIs are supported as per TS29.505 on UDR. Sample payloads are as follow:

• GET-ContextData
• GET - Context Data - SMSF
• PUT - Amf3GppAccessRegistration
• PATCH - Amf3GppAccessRegistration
• GET-Amf3GppAccessRegistration
• GET-Amf3GppAccessRegistration
• PUT-AmfNon3GppAccessRegistration
• GET-AmfNon3GppAccessRegistration
• GET-AmfNon3GppAccessRegistration
• GET-AuthenticationSubscriptionData
• PATCH-AuthenticationSubscriptionData
• PUT-AuthenticationStatus
• GET-AuthenticationStatus
• GET - AccessAndMobilitySubscriptionData
• PUT-AccessAndMobilitySubscriptionData
• GET-SessionManagementSubscriptionData
• GET-ProvisionedData

3.5.1 Subscription Operations for UDM Data

This table provides information about the subscription operations for UDM data.

All APIs are supported as per TS29.505 on UDR. Sample payloads are as follow:

• POST-SDMSubscriptions
• PUT - SDMSubscriptions
• GET-SDMSubscriptions
• Post-Output-SubscriptionDataSubscriptions
• Post-SubscriptionDataSubscriptions
• Get-Output-SubscriptionDataSubscriptions

3.6 UDSF Data Operations

The following table provides information about the UDSF Data Operations.

Table 3-1 UDSF Data Operations

HTTP Method	Sample REST URL	Description	Possible Error Codes
PUT	https://localhost:9443/nudsf-dr/v1/udsf/msisdn-1111111111/udsf-data	Sample data blob for UDSF data is: { "a": 1, "b": 2 } Create or update request that adds or modifies the unstructured data for a given subscriber.	400: "Invalid URI sent from client" 404: "Subscriber does not exist" 400: "Unknown key, the key provided in the request is invalid" 400: "Blob syntax error with corresponding error details"
GET	https://localhost:9443/nudsf-dr/v1/udsf/msisdn-1111111111/udsf-data	Retrieves the unstructured data for the given subscriber.	400: "Invalid URI sent from client" 404: "Subscriber does not exist" 404: "Data field does not exist" 400: "Unknown key, the key provided in the request is invalid"
DELETE	https://localhost:9443/nudsf-dr/v1/udsf/msisdn-1111111111/udsf-data	Deletes the unstructured data for the given subscriber.	400: "Invalid URI sent from client" 404: "Subscriber does not exist" 400: "Unknown key, the key provided in the request is invalid"