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-Verified Caller #27

Closed
DanXu-ChinaTelecom opened this issue Apr 16, 2024 · 8 comments
Closed

New API proposal-Verified Caller #27

DanXu-ChinaTelecom opened this issue Apr 16, 2024 · 8 comments

Comments

@DanXu-ChinaTelecom
Copy link

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.

@DanXu-ChinaTelecom DanXu-ChinaTelecom added wontfix This will not be worked on and removed wontfix This will not be worked on labels Apr 19, 2024
@TEF-RicardoSerr
Copy link
Collaborator

PR available in camaraproject/WorkingGroups#410

@Jason-ZTE
Copy link

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
Copy link
Collaborator

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
Copy link

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
Copy link
Collaborator

Supporting material available here

@TEF-RicardoSerr
Copy link
Collaborator

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
Copy link
Author

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
Copy link
Collaborator

Subproject have been created here. Closing this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants