1

SharedData

When receiving a Nudm_SDM_Get service operation request to retrieve a UE’s individual subscription data, and the request does not contain a supported-features query parameter indicating support of this feature, the UDM shall not include Shared Data Ids in the response. Instead the UDM may – based on operator policy – take no further action (i.e. allow the UE to get services based on only the UE’s individual subscription data), or send the shared data as individual data (this may result in notifications of individual subscription data change – if so subscribed – when shared data, which are sent as individual data, are modified, and/or when the UE’s Shared Data IDs are modified).

2

ImmediateReport

When a NF consumer detects the UDM support ImmediateReport feature, it can indicate an immediateReport flag when invoking Nudm_SDM_Subscribe service operation. If UDM supports ImmediateReport received Nudm_SDM_Subscribe service operation request, it shall return the resource representation(s) of the monitored resource(s) in the service operation response body.

3

PatchReport

If some of the modifications included in the PATCH request are not successfully implemented, the UDM reports the result of PATCH request execution to the consumer. See clause 5.2.7.2 of 3GPP TS 29.500 [4].

4

Nssaa

If the NF consumer does not support this feature, the UDM shall not include information of S-NSSAI(s) subject to Network Slice-Specific Authentication and Authorization in Get response messages, immediate reports within Subscribe response messages, or data change notifications where the data change is limited to S-NSSAI(s) subject to Network Slice-Specific Authentication and Authorization.

5

CAGFeature

If the NF consumer does not support this feature, the UDM shall not include CAG information list in the message body with "200 OK" response (clause 5.2.2.2.3). The UDM performs action as executes step 2c of clause 5.3.2.2.2 and 5.3.2.2.3 if UE is allowed to access 5GS via CAG cell(s) only.

6

SharedDataTreatment

This feature is an extension to the SharedData feature, i.e. support of SharedDataTreatment requires support of SharedData.

When receiving a Nudm_SDM_Get service operation request to retrieve a UE’s individual subscription data, and the request does not contain a supported-features query parameter indicating support of this feature, the UDM shall not include SharedDataTreatments in the SharedData returned in the response. Instead the UDM may – based on operator policy – take no further action (i.e. allow the UE to get services based on default treatment (i.e. individual data take precedence), or send the shared data which have non-default treatment as individual data.

7

sorTransparentSupport

This flag indicates NF Consumer (e.g. AMF) support of receiving SoR Transparent Container instead of individual IEs from NF Producer (e.g. UDM). If the NF consumer does not support this feature, the NF Producer shall not include sorTransparentContainer, as defined in clause 6.1.6.2.26.

Corresponding flag is also used by UDM to register (in NRF) its support of receiving SoR Transparent Container instead of individual IEs from the NF Consumer (e.g. AMF). If the UDM does not support this feature, the NF Consumer shall not include sorTransparentContainer, as defined in clause 6.1.6.2.25.

8

Nsac

If the NF consumer does not support this feature, the UDM shall not include network slice admission control related information for S-NSSAI(s) in the message body with "200 OK" response (See clause 5.2.2.2.3).

9

SharedSmSubsData

If the NF consumer does not support this feature, the UDM shall not take the alternative to include extendedSmSubsData in SmSubsData (clause 6.1.6.2.79).

10

ENA

Enhanced Network Automation.

If the UDM supports this feature, the UDM shall apply the nfChangeFilter IE received in the sdmSubscription and send the notifications accordingly (See clause 6.1.6.2.16 and 6.1.6.2.70).

11

Nssrg

The NF consumer (i.e. AMF) that supports this feature shall support handling of NSSRG information received along with the subscribed S-NSSAIs as defined in clause 5.15.12 of 3GPP TS 23.501 [2].

If the NF consumer does not support this feature, the UDM may select the subset of the compatible Subscribed S-NSSAIs without including any information of Network Slice Simultaneous Registration Group.

12

upuTransparentSupport

This flag indicates NF Consumer (e.g. AMF) support of receiving UE Parameters Update Transparent Container instead of individual IEs from NF Producer (e.g. UDM). If the NF consumer does not support this feature, the NF Producer shall not include upuTransparentContainer, as defined in clause 6.1.6.2.33.

Corresponding flag is also used by UDM to register (in NRF) its support of receiving UE Parameters Update Transparent Container instead of individual IEs from the NF Consumer (e.g. AMF). If the UDM does not support this feature, the NF Consumer shall not include upuTransparentContainer, as defined in clause 6.1.6.2.25.

13

LimitedSubscriptions

An NF consumer supporting this feature shall use one subscription for the changes of subscription data sets per UE without additional filter criteria, or with a specific filter criteria (e.g. dnn and/or singleNssai).

An NF consumer supporting this feature shall use one subscription for the changes of shared data sets.

14

SNPN-ID

Support of SNPN-ID

This flag indicates whether the NF Consumer (e.g. AMF) or NF producer (UDM) support receiving an SNPN-ID as an extension of the "plmn-id" query parameter, when retrieving Access And Mobility Subscription Data (either by querying the "{supi}" resource or the "{supi}/am-data" resource).

If the NF Consumer is aware (e.g. from previous interactions) that the UDM does not support this feature, the NF Consumer should not send queries on the Nudm_SDM API including SNPN-ID in the "plmn-id" query parameter.

Also, if the NF Consumer sent such query to UDM, and the UDM does not indicate support of this feature in the response, the NF Consumer should consider the response as invalid, since the response from UDM would have not considered the presence of the NID component of the SNPN-ID in the "plmn-id" parameter.

15

UeConSmfDataSubFilter

UE Context in Smf Data Subscription Filter

If the UDM supports this feature, the UDM shall handle the ueConSmfDataSubFilter IE received in the sdmSubscription and sends the notifications only for changes indicated in the IE.