# Fusion of Telecommunications and IT Services Boosted by Application Programming Interfaces
## 4 Fusion of Telco and IT Services
### Nokia TAS Open API Use Cases  
With the usage of Telco APIs, the traditional telecommunication service domain can easily be enriched with IT API-based services, as shown in Figure 8.  
Besides the examples shown in Figure 8, hereby some examples are listed of what kind of possibilities are provided for the operators utilizing various APIs (when changing from Telco-only services):  
* Call Direction API: This suspends the call and triggers the application to take the appropriate route decision or change the calling line ID. The operator can develop applications such as the following: \(\bigcirc\) Nuisance call blocking, which recognizes and blocks robocalls or telemarketing calls in the network according to call blocking application settings; \(\bigcirc\) Blocking all calls to children during school time; \(\bigcirc\) Mashing up connected car data to change the calling pattern while driving (i.e., call blocking with a personal exception list); \(\bigcirc\) Calendar-based call forwarding that extends end users' reachability conditions with a personal/office calendar application (e.g., Google Calendar); \(\bigcirc\) Caller ID enrichment with the name of the calling party, which can enable companies to reach out to their customers with an increased success rate; \(\bigcirc\) Posting automatic social media advertisements by the application for personal benefits (e.g., when user calls a restaurant for booking, the API service can advertise the restaurant on a personal Facebook page in return for a discount); \(\bigcirc\) Temporary call ID that enables two parties to call each other without sharing their personal phone numbers and therefore increases communication privacy; Basic parental/elder care is also possible by notifying parents/caregivers about calls from children/older people.
* Call Event Notification API: This notifies call events without having the possibility of influencing the call. The operators may develop services like the following: \(\bigcirc\) Integration with Over-the-Top (OTT) phone applications; for example, based on the network notification of an incoming call, the service may send a push notification to the OTT application that can include the user's previous personal notes on the caller; \(\bigcirc\) It can also help to build a smart home: e.g., blinking a lamp could notify the subscriber about incoming calls;  
Figure 8: Use cases after IT–Telco fusions.  
Notification of missed calls to IT/social media services (e.g., callback reminder to Google Calendar or a Twitter personal message) to increase the notification space of the end user; Building a personal server-based call history database that can be accessed on a web portal.
* Call Control API: Third-party call control functions, which can initiate a call and manage call participants (e.g., add or drop participants), such as the following: Service center call management: monitoring of agent availabilities and providing customer callback when an agent becomes available for a call; Ordered call conference: A service initiated or a scheduled call conference between two or more parties.
* SMS API: This sends an SMS to a user and notifies service logic on a received SMS, including the following: Two-factor authentication with SMS; SMS notification of a missed incoming call; SMS televoting; SMS chatbot (ChatGPT [70] service reservation and support center); SMS-based advertisement.