New API Proposal - IoT SIM Fraud Prevention

[chenfr2-ChinaTelecom]

Which issue(s) this PR fixes:

Fixes #96

[jgarciahospital]

Suggested change

	| API family name | IoT SIM Fraud Prevention Subscibition | |
	| API family name | IoT SIM Fraud Prevention Subscription | |

[jgarciahospital]

Same change to be applied in file name

[chenfr2-ChinaTelecom]

Hi @jgarciahospital, I have updated the spelling mistake, thank you for your review

[jgarciahospital]

Both APIs, as related, will be included in same single line of proposal.

[chenfr2-ChinaTelecom]

One point that was not mentioned in our proposal is that we need to subscribe to a service with SIM card binding and regional restriction first, for the SIM card binding service, the SIM card and IMEI must be bound together when subcribe the service. When the IMEI reported in the message doesn't match the binding one, the network serices will be blocked. When the IMEI reported in the message matches the binding one, the network service of the SIM card will be restored.

The ability provided by the regional restriction is similar to that of SIM card binding, but what's bound is the regional information (the regional information is mapped to the corresponding region based on the base station ID reported in the message).
In the query api mentioned in this proposal, returned status means match (network access is enabled) / no match (network blocking).

Meanwhile，we added binding and unbinding APIs under this proposal.