search

camaraproject / APIBacklog

Repository to maintain the API Backlog for CAMARA.
https://wiki.camaraproject.org/x/I4tF
Apache License 2.0
4 stars 13 forks source link

New API proposal-Verified Caller #27

Closed DanXu-ChinaTelecom closed 3 weeks ago

DanXu-ChinaTelecom commented 2 months ago

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.

TEF-RicardoSerr commented 2 months ago

PR available in camaraproject/WorkingGroups#410

Jason-ZTE commented 2 months ago

Question: If a fraudulent call is initiated while also sending a fraudulent SMS/RCS message in the format used by the operator, how can the called user identify it? Answer: The criminal can mimic the content of the SMS, but the criminal cannot send from the operator's specific calling number. The called user will only trust messages sent from the operator's specific calling number.

TEF-RicardoSerr commented 2 months ago

Hello.

Could you please provide more details about the technical implementation of this API, including the underlying technologies used? Additionally, we would like to better understand how this API differs from other approaches, such as the eCNAM-based branded calls API, which may also come within the OGW drop#4.

Jason-ZTE commented 2 months ago

Hi,eCNAM is an IP Multimedia Subsystem (IMS) based solution that utilizes the Session Initiation Protocol (SIP) to deliver enhanced caller identification information. However, as it is part of the 3GPP Release 18 specifications, it will only be available after IMS and terminals upgrades for VoLTE (Voice over LTE) and VoNR (Voice over New Radio) networks.

Verified Caller is a more immediate solution that can work with existing fixed line, 2G/3G mobile, and call center infrastructure. It leverages an API that allows enterprises to dynamically provide customized caller identification information on a per-call basis, tailoring the experience for different called parties.The carrier-managed service registration portal, through which the messages are sent under the carrier's brand, ensures the authoritativeness of the information, which is crucial for ordinary called customers.

The attached framework depicts a logical architecture where the Verified Caller service interacts with the enterprise's application servers and the telecom network to deliver the enhanced caller identification information to the called party's device. image

TEF-RicardoSerr commented 1 month ago

Supporting material available here

TEF-RicardoSerr commented 1 month ago

Hello @DanXu-ChinaTelecom, @Jason-ZTE

As for 16-05 TSC Minutes the API is approved and I need you to provide the initial maintainers and codeowners from your side for the upcoiming Verified Caller GitHub Repository

DanXu-ChinaTelecom commented 1 month ago

thx @TEF-RicardoSerr ，we proposed initial codeowners： DanXu-ChinaTelecom and Jason-ZTE @Jason-ZTE ，

and initial maintainers as follows：

Org Name GitHub Username
China Telecom Dan Xu DanXu-ChinaTelecom
China Telecom Xianyang Zhang zxyxwz
ZTE Tu Jiashun Jason-ZTE
China Unicom Yang Fan chinaunicomyangfan
China Mobile Hanbai Wang HanbaiWang
HuaWei Shuting Qing ShutingQing
Whale Cloud Technology Co.,Ltd Yun Wang WangYunyunA
TEF-RicardoSerr commented 3 weeks ago

Subproject have been created here. Closing this issue