In order to subscribe to a new monitoring event configuration, the SCS/AS shall send an HTTP POST message to the SCEF targeting the resource "Monitoring Event Subscriptions". The body of the HTTP POST message shall include:
-
SCS/AS Identifier;
-
Monitoring Type;
-
Notification Destination Address; and
-
One of External Identifier, MSISDN or External Group Identifier. The External Identifier or the MSISDN identifies the subscription of an individual UE and the External Group Identifier points to a group of UEs.
-
In addition, the HTTP POST request may include:
-
Maximum Number of Reports;
-
Monitoring Duration indicated by the property "monitorExpireTime";
-
Group Reporting Guard Time.
If the Subscription_modification feature is supported, the SCS/AS may send an HTTP PUT message in order to update an existing monitoring event subscription. The HTTP PUT request targets the resource "Individual Monitoring Event Subscription" replacing all properties in the existing configuration.
For one-time monitoring type of requests, the SCS/AS shall include the Maximum Number of Reports with a value set to 1 and not include the Monitoring Duration in the HTTP request message sent to the SCEF.
Upon receipt of the HTTP POST or PUT request message, if the SCS/AS is authorized to perform such request, the SCEF shall check whether the parameters (e.g. Maximum Number of Reports, Monitoring Duration, Maximum Latency, Maximum Response Time, Suggested number of downlink packets) in the HTTP request body are within the range defined by operator policies. If one or more of these parameters are not within the range, the SCEF shall:
-
either reject the request message by sending an HTTP response to the SCS/AS with a status code set to 403 Forbidden and may include the "PARAMETER_OUT_OF_RANGE" error in the "cause" attribute of the "ProblemDetails" structure and indicate which parameters are out of the range in the "invalidParams" attribute of the "ProblemDetails" structure; or
-
modify the parameters which are not within the range by selecting different values which are in the range.
For individual UE configuration requests, the SCEF shall also check whether the Idle Status Indication is included for UE reachability event. If the Idle Status Indication is received in the request but not supported by the network, the SCEF may reject the request message by sending an HTTP response to the SCS/AS with a status code set to 403 Forbidden and may include the "IDLE_STATUS_UNSUPPORTED" error in the "cause" attribute of the "ProblemDetails" structure.
If the SCEF receives an HTTP POST request to create a subscription resource for a monitoring event, but without an indication of the support for the feature corresponding to the requested monitoring event, the SCEF shall reject the request by sending a "400 Bad Request" HTTP error response with the application error "EVENT_FEATURE_MISMATCH".
If the SCEF receives an HTTP POST request to create a subscription resource for a monitoring event that it does not support, the SCEF shall reject the request by sending a "500 Internal Server Error" HTTP error response with the application error "EVENT_UNSUPPORTED".
After validation, the SCEF shall store the parameters and
-
may assign an SCEF Reference ID related to the created monitoring event subscription resource; and based on operator policies, shall
-
map the accuracy into permissible granularity for location reporting event;
-
map the location area into a list of cells, eNodeB(s) and/or RAI(s)/TAI(s) and derive the corresponding MME(s)/SGSN(s), for number of UEs present in a geographic area event.
In order to delete a previous active configured monitoring event subscription at the SCEF, the SCS/AS shall send an HTTP DELETE message to the SCEF targeting the resource "Individual Monitoring Event Subscription" which is previously received in the response to the request that has created the monitoring events subscription resource. The SCEF shall detemine the SCEF Reference ID related to the active monitoring subscription resource.