From b16fc0f2a353eb74df51fb607baa0ed817b5b84a Mon Sep 17 00:00:00 2001 From: Dan Xu <131235276+DanXu-ChinaTelecom@users.noreply.github.com> Date: Wed, 17 Apr 2024 17:54:37 +0800 Subject: [PATCH 1/3] Create new API proposal-Verified Caller --- .../API proposals/NewAPIproposal_Verified Caller.txt | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.txt diff --git a/APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.txt b/APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.txt new file mode 100644 index 00000000..55cbfdfd --- /dev/null +++ b/APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.txt @@ -0,0 +1,12 @@ +| **Field** | Description | +| :---------------------------------------- | ------------------------------------------------------------ | +| API family name | Verified Caller | +| API family owner | China Telecom, China Unicom，ZTE | +| API family summary | **High-level description**. This API allows accurate operator-certified "Verified Caller" information, including SMS and video clips, to be displayed on the phone screen of the called user before they answer the call. This API enables enterprise customers to vividly present their multimedia business cards and reduces the incidence of malicious calls. It is applicable to customers in industries such as government, finance, express delivery, healthcare, education, etc., who have outbound call requirements. For instance, when a hospital arranges follow-ups and communication between customer service and rehabilitation patients, patients might doubt the hospital's identity and typically refuse the calls. By utilizing this API, the hospital's identity can be displayed, thereby improving connection rates and significantly enhancing customer service satisfaction. **Input params**: APIserviceID, TargetNumber, SenderNumber, TemplateCode, TemplateParams. **Output params**: API success or failure response. | +| Technical viability | This API leverages existing SMS and RCS services provided by operators. | +| Commercial viability | This API has been commercially launched in China Telecom and several other operators. However, the API is not yet standardized. In order to achieve a wider range of commercialization and easy use for enterprises and developers, it is necessary to standardize the service API. | +| YAML code available? | TBD | +| Validated in lab/productive environments? | YES, Commercially launched in China Telecom. | +| Validated with real customers? | Yes | +| Validated with operators? | Yes, China Mobile, China Unicom. | +| Supporters in API Backlog Working Group | | \ No newline at end of file From 7c24433645918de01690c077643f0ba8da0810fd Mon Sep 17 00:00:00 2001 From: Eric Murray Date: Thu, 25 Apr 2024 14:41:36 +0100 Subject: [PATCH 2/3] Update and rename NewAPIproposal_Verified Caller.txt to NewAPIproposal_Verified Caller.md --- ...al_Verified Caller.txt => NewAPIproposal_Verified Caller.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename APIBacklog/documentation/SupportingDocuments/API proposals/{NewAPIproposal_Verified Caller.txt => NewAPIproposal_Verified Caller.md} (97%) diff --git a/APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.txt b/APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.md similarity index 97% rename from APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.txt rename to APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.md index 55cbfdfd..be949006 100644 --- a/APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.txt +++ b/APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.md @@ -9,4 +9,4 @@ | Validated in lab/productive environments? | YES, Commercially launched in China Telecom. | | Validated with real customers? | Yes | | Validated with operators? | Yes, China Mobile, China Unicom. | -| Supporters in API Backlog Working Group | | \ No newline at end of file +| Supporters in API Backlog Working Group | | From d77a44306766b2cb79a90de79d2392edfecafb7e Mon Sep 17 00:00:00 2001 From: Dan Xu <131235276+DanXu-ChinaTelecom@users.noreply.github.com> Date: Fri, 26 Apr 2024 14:51:45 +0800 Subject: [PATCH 3/3] Update NewAPIproposal_Verified Caller.md This API supports fixed line and mobile phone customers to use. --- .../API proposals/NewAPIproposal_Verified Caller.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.md b/APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.md index be949006..df0f61a5 100644 --- a/APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.md +++ b/APIBacklog/documentation/SupportingDocuments/API proposals/NewAPIproposal_Verified Caller.md @@ -2,7 +2,7 @@ | :---------------------------------------- | ------------------------------------------------------------ | | API family name | Verified Caller | | API family owner | China Telecom, China Unicom，ZTE | -| API family summary | **High-level description**. This API allows accurate operator-certified "Verified Caller" information, including SMS and video clips, to be displayed on the phone screen of the called user before they answer the call. This API enables enterprise customers to vividly present their multimedia business cards and reduces the incidence of malicious calls. It is applicable to customers in industries such as government, finance, express delivery, healthcare, education, etc., who have outbound call requirements. For instance, when a hospital arranges follow-ups and communication between customer service and rehabilitation patients, patients might doubt the hospital's identity and typically refuse the calls. By utilizing this API, the hospital's identity can be displayed, thereby improving connection rates and significantly enhancing customer service satisfaction. **Input params**: APIserviceID, TargetNumber, SenderNumber, TemplateCode, TemplateParams. **Output params**: API success or failure response. | +| API family summary | **High-level description**. This API allows accurate operator-certified "Verified Caller" information, including SMS and video clips, to be displayed on the phone screen of the called user before they answer the call. This API enables enterprise customers to vividly present their multimedia business cards and reduces the incidence of malicious calls. It is applicable to customers in industries such as government, finance, express delivery, healthcare, education, etc., who have outbound call requirements. For instance, when a hospital arranges follow-ups and communication between customer service and rehabilitation patients, patients might doubt the hospital's identity and typically refuse the calls. By utilizing this API, the hospital's identity can be displayed, thereby improving connection rates and significantly enhancing customer service satisfaction.This API supports fixed line and mobile phone customers to use. **Input params**: APIserviceID, TargetNumber, SenderNumber, TemplateCode, TemplateParams. **Output params**: API success or failure response. | | Technical viability | This API leverages existing SMS and RCS services provided by operators. | | Commercial viability | This API has been commercially launched in China Telecom and several other operators. However, the API is not yet standardized. In order to achieve a wider range of commercialization and easy use for enterprises and developers, it is necessary to standardize the service API. | | YAML code available? | TBD |