Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.682  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   4.2   4.3…   4.4…   4.5…   4.5.7…   4.5.14…   4.6…   5…   5.3…   5.5…   5.6…   5.6.2…   5.6.6…   5.7…   5.8…   5.9…   5.13…   5.14…   5.15   5.16   5.17…   5.18   5.19…   A…   C…

 

5.16  Procedure for Enhanced Coverage Restriction Control via SCEF |R14|Word‑p. 116

Figure 5.16-1 shows the procedures for Enhanced Coverage Restriction Control via SCEF.
(not reproduced yet)
Figure 5.16-1: Procedure for Enhanced Coverage Restriction Control via SCEF
Up
Step 1.
The SCS/AS sends an Enhanced Coverage Request (External Identifier or MSISDN, SCS/AS Identifier, Request Type, Enhanced Coverage Restriction Data, MTC Provider Information) message to the SCEF. Request Type indicates if the request is to query the status of, or to enable, or to disable the enhanced coverage restriction. Enhanced Coverage Restriction Data provides data related to the Enhanced Coverage Restriction. Enhanced Coverage Restriction Data is only present if Request Type is to either enable or disable the enhanced coverage restriction.
Step 2.
The SCEF stores the SCS/AS Identifier. The SCEF assigns an SCEF Reference ID. Based on operator policies, if either the SCS/AS is not authorized to perform this request (e.g. if the SLA does not allow for it) or the Enhanced Coverage Request is malformed or the SCS/AS has exceeded its quota or rate of submitting Enhanced Coverage requests, the SCEF performs step 9 and provides a Cause value appropriately indicating the failure result.
Step 3.
The SCEF sends an Enhanced Coverage Request (External Identifier or MSISDN, SCEF ID, SCEF Reference ID, Type, MTC Provider Information) message to the HSS.
Step 4.
The HSS examines the Enhanced Coverage Request message, e.g. with regard to the existence of External Identifier or MSISDN, whether any included parameters are in the range acceptable for the operator, whether the Enhanced Coverage restriction is supported by the serving MME/SGSN. If this check fails the HSS follows step 8 and provides a Cause value indicating the reason for the failure condition to the SCEF.
If the Request Type is to get the current status of enhanced coverage HSS retrieves the value and procedure follows at Step 8. Else If the Type is to enable or to disable the enhanced coverage, HSS sets Enhanced Coverage Restricted parameter to the appropriate value and the procedure continues at step 5.
Step 5.
If required by the specific Enhanced Coverage Request Type and when Enhanced Coverage is supported by the serving MME/SGSN, the HSS sends an Insert Subscriber Data Request (Type, SCEF ID, SCEF Reference ID) message to the MME/SGSN.
Step 6.
Based on operator policies, the MME/SGSN may reject the request (e.g. overload or HSS has exceeded its quota or rate of submitting enhanced coverage requests defined by an SLA).
The MME/SGSN updates Enhanced Coverage Restricted parameters in the MME/SGSN context.
The MME/SGSN will transfer the Enhanced Coverage Restricted parameters stored as part of its context information during MME/SGSN change.
Step 7.
If the Enhanced Coverage restriction is updated successful, the MME/SGSN sends an Insert Subscriber Data Answer (Cause) message to the HSS. MME/SGSN may include the Enhanced Coverage Restricted parameter in the Insert Subscriber Data Answer message.
Step 8.
The HSS sends an Enhanced Coverage Response (SCEF Reference ID, Cause) message to the SCEF. HSS includes result = success/failure and in the case of success may include Enhanced Coverage Restriction Data.
In the case of UE mobility, the HSS determines whether the new MME/SGSN supports Enhanced Coverage restriction.
Step 9.
The SCEF sends an Enhanced Coverage Response (Cause, Enhanced Coverage Restriction Data) message to the SCS/AS. Cause indicates success or failure. If in step 1 the Enhanced Coverage Request message is sent to query the status of Enhanced Coverage Restricted, then Enhanced Coverage Restriction Data is included (in the case of success) in the Enhanced Coverage Response message.
Up

Up   Top   ToC