7.14 Supported features

7.14.1 General Concepts

The supported features are negotiated separately for each API. For each of the APIs, the applicable list of features is contained in the related API definition defined in 3GPP TS29.122 [4]. The procedure to negotiate applicable features is defined in 3GPP TS29.500 [9]. Each resource for a SCEF API will contain a "supportedFeatures" attribute of the SupportedFeatures data type defined in 3GPP TS 29.571 [10] containing a bitmask to indicate supported features. The features and their positions in that bitmask are defined separately for each API.

The SCEF/3GPP Network Entities will determine the supported features for the corresponding resource by comparing the supported features indicated by an IN-CSE with the supported features the SCEF/3GPP Network Entities support. The SCEF will include the "supportedFeatures" attribute indicating those features in the representation of the resource it returns to the IN-CSE in the response confirming the creation of the resource.

7.14.2 Normal Procedures

This clause introduces normal procedures for a supportedFeatures. If a SCEF receives a Monitoring Event Subscription Request for a Monitoring Event with the corresponding supportedFeatures, the SCEF sends an HTTP POST response to the IN-CSE with a "201 CREATED" status code as described in 3GPP TS29.122 [4].

Figure 7.14.2.-1 shows an example of the normal procedure for a supportedFeatures. A SCEF supports Location Reporting of Monitoring Event API. If an IN-CSE sends a Monitoring Event Subscription Request (monitoringType attribute is set to LOCATION_REPORTING), the supportedFeatures needs to be set to the value of Location_Notifications and the SCEF will response the request by sending the above status code.

If the IN-CSE receives the Monitoring Event Subscription Response, the IN-CSE will identify it as a successful response and continue the procedure for the Monitoring Event.

Figure 7.14.2-1: Normal procedures for a supportedFeatures