According to the questions at the last meeting, we compared the abilities of our API proposal with Device management proposal. The Device management proposal offers the ability to manage the lifecycle. In our proposal, we also provide the management of communication functions like SMS, voice, and data traffic for IoT Sim cards.

Besides, based on the advice，we reviewed other existing API proposals and found that there's a certain connection between ours and the Subscription Status proposal. This proposal currently provides the query ability for services like Voice, Sms, and Data. In our proposal, we also providers the ability to turn on and off the services of SMS, voice, and data traffic. This is the difference between us and other APIs.

In the IoT situation, not all devices need to have SMS and voice services always on. And it's necessary to turn off the data traffic service to control the data usage. In China's IoT applications, this is a standardized ability. It's currently supported by the main operators in China and has formed a unified industry standard for the open connection ability of IoT SIM cards in CCSA of China.

We hope to change the proposal and add new interfaces for the ability to turn on and off SMS, voice, and data traffic services. These can be in the same group as SubscriptionStatus.