Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New API Proposal - IoT SIM Status Mgmt #105

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
| **Field** | Description |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| API family name | Device Communication Function Mgmt |
| API family owner | China Telecom |
| API summary | This API allows enterprise customers to manage the communication function of IoT cards, including close and open voice, sms, data services. <br><br>Input:<br>1. Device: The developer can choose to provide the below specified device identifiers: ipv4Address, ipv6Address, phoneNumber,networkAccessIdentifier.<br>2. BusiType: Type of service to be managed, such as traffic, voice or SMS<br>3. Action: such as open, close<br><br>Output:<br>1. Card specific type service status |
| Technical viability | Operators can obtain the status of by querying the information in the Connection Management Platform and UDM/HSS contracted network element devices of the mobile network . |
| Commercial viability | The API is suitable for organizations that require traffic control, such as automotive companies. |
| YAML code available? | NO |
| Validated in lab/productive environments? | YES<br>The API has been validated in China Telecom IOT Connection Management Platform. |
| Validated with real customers? | YES |
| Validated with operators? | YES<br>China Telecom has verified it in China Telecom IOT connection management platform. |
| Supporters in API Backlog Working Group | |
12 changes: 12 additions & 0 deletions documentation/API proposals/API_Proposal_IoT_SIM_Status_Mgmt.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
| **Field** | Description | |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- |
| API family name | IoT SIM Status Mgmt | |
| API family owner | China Telecom | |
| API summary | This API allows enterprise customers to query and manage the full lifecycle status of IoT cards, as well as the activation and deactivation of voice, SMS, data, and specified APNs, ensuring real-time monitoring of card status and realizing precise control of traffic to prevent traffic overload.<br><br>The API is suitable for organizations that require traffic control and card status management, such as automotive companies.<br><br>Input:<br>1. Device: The developer can choose to provide the below specified device identifiers: ipv4Address, ipv6Address, phoneNumber,networkAccessIdentifier.<br>2. BusiType: Type of service to be managed, such as APN, traffic, voice or SMS, SIM card status<br>3. Action: such as open, close, query, update<br>4. BusiParam: Business parameters, such as apn name, sim card status<br><br>Output:<br>1. Card specific type service status | |
| Technical viability | Operators can obtain the status of by querying the information in the Connection Management Platform and UDM/HSS contracted network element devices of the mobile network . | |
| Commercial viability | The API is suitable for organizations that require traffic control and card status management, such as automotive companies. | |
| YAML code available? | NO | |
| Validated in lab/productive environments? | YES<br>The API has been validated in China Telecom IOT Connection Management Platform. | |
| Validated with real customers? | YES | |
| Validated with operators? | YES<br>China Telecom has verified it in China Telecom IOT connection management platform. | |
| Supporters in API Backlog Working Group | | |
Binary file not shown.
Binary file not shown.