generated from camaraproject/Template_API_Repository
-
Notifications
You must be signed in to change notification settings - Fork 23
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 Fraud Prevention #103
Open
chenfr2-ChinaTelecom
wants to merge
6
commits into
camaraproject:main
Choose a base branch
from
chenfr2-ChinaTelecom:proposal1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
6dea180
New API Proposal - IoT SIM Fraud Prevention
chenfr2-ChinaTelecom eefdb11
Update and rename API_Proposal_IoT_SIM_Fraud_Prevention_Subscibition.…
chenfr2-ChinaTelecom 1e66c4d
Add files via upload
chenfr2-ChinaTelecom 2289157
Add files via upload
chenfr2-ChinaTelecom aef41d8
delete the ppt file, reupload to SupportingDocuments directory
chenfr2-ChinaTelecom 1c7447e
Add files via upload
chenfr2-ChinaTelecom File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
12 changes: 12 additions & 0 deletions
12
documentation/API proposals/API_Proposal_IoT_SIM_Fraud_Prevention_Query.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| | **Field** | Description | | | ||
| | ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | | ||
| | API family name | IoT SIM Fraud Prevention Query | | | ||
| | API family owner | China Telecom | | | ||
| | API summary | This API allows enterprise customers to query risk control information related to IoT SIM cards, such as machine-card binding, region restriction. With this information, enterprises can assess the security and reliability of IoT cards, helping to assess security, detect, and prevent possible fraud.<br><br>Input:<br>1. Device: The developer can choose to provide the below specified device identifiers: ipv4Address, ipv6Address, phoneNumber,networkAccessIdentifier.<br>2. Query Type: Such as arealimit or imeibind<br><br>Output:<br>1. Card arealimit or imeibind status | | | ||
| | Technical viability | This API parses the Radius and CHF messages of the accessed SIM card to get the IMEI and region information of the card, and determines whether it matches the preset binding information. | | | ||
| | Commercial viability | The API is suitable for organizations that need to secure and comply with IoT devicesl such as financial institutions, sensor data transfer. | | | ||
| | 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
12
documentation/API proposals/API_Proposal_IoT_SIM_Fraud_Prevention_Subscibition.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| | **Field** | Description | | | ||
| | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | | ||
| | API family name | IoT SIM Fraud Prevention Subscibition | | | ||
| | API family owner | China Telecom | | | ||
| | API summary | This API allows enterprise customers to subscribe to risk control information related to IoT SIM cards. When the device or region bound to the IoT card changes, the customer can be notified in a timely manner through the callback address registered by the customer, making it convenient for the customer to identify endpoint risks in a timely manner.<br><br>Input:<br>1. Device: The developer can choose to provide the below specified device identifiers: ipv4Address, ipv6Address, phoneNumber,networkAccessIdentifier.<br>2. Subscibition Type: Such as arealimit or imeibind<br>3. Sink: The address to which events shall be delivered using the selected protocol.<br>4. SinkCredential: A sink credential provides authentication or authorization information necessary to enable delivery of events to a target.<br><br>Output:<br>1. SubscriptionId | | | ||
| | Technical viability | This API parses the Radius and CHF messages of the accessed SIM card to get the IMEI and region information of the card, and determines whether it matches the preset binding information. | | | ||
| | Commercial viability | The API is suitable for organizations that need to secure and comply with IoT devicesl such as financial institutions, sensor data transfer. | | | ||
| | 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 added
BIN
+1.31 MB
documentation/SupportingDocuments/API_Proposal_IoT_SIM_Fraud_Prevention.pptx
Binary file not shown.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same change to be applied in file name
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @jgarciahospital, I have updated the spelling mistake, thank you for your review