A fews days ago, I had posted a unified architecture of the whitelassi PNM application server, fully integrated with IMS supplementary services and IMS service enablers such as the XDM server.
The diagram showed the potential of user/device management services such as that of PNM (Personal Network Management). It also gives insight and the value proposition that PNM can enrich and add value to IMS call control services.
The entire architecture can be seen here: PNM-IMS-SERVICE-INTEGRATION
This architecture shows, that a device management framework such as PNM can be leveraged upon to act as a valuable utility for other services as well, especially those services that rely on user preferences and privacy. Some of the services that are shown on the page are listed below. Let us talk about them briefly and discuss the possibilities that they present to us:
1. Wake up Call Reminder service, which the user can configure over SIP or from the GUI.
This service would enable the user to set a wake up call time on the GUI of the PNM server. The PNM application, will read the user’s input from the GUI, and schedule a timer to wake him/her up. This service can also be re-used as a reminder service. Hence, the PNM component here enables the user to manage his preferences and avail of a value added service in the form of Wake up service. The user who owns multiple devices, can also schedule a wake up call on multiple devices if he wishes so !
2. Communication on Hold ( or Call hold) supplementary service.
This is a famous and widely used service in the telecom world. The user can set preferences that whenever an active IMS session is put on hold, a special ringtone is played on the line. These preferences can be set on the GUI and stored as a XML file in the XDM server.
3. Incoming and Outgoing communication barring based on user preferences.
The user can specify preferences on blocking certain numbers (prank callers) on the GUI. Moreover, the PNM controller (master device) can also present restrictions on other devices (PNM controlees), such as those pertaining to parental control.
4. Originating Identity Presentation and Restriction supplementary service.
This is a popular legacy supplementary service that has been carried forward in the SIP and IMS world.
5. Terminating Identity Presentation and Restriction supplementary service.
Same as point 4 above, the only differnence being that this service is invoked for the terminating side of the call.
6. Call Blocking Service (Unconditional and partial)
This is a special variant of communication barring. Similarities can be invstigated further.
7. Intelligent Caller preferences that can be set on SIP or from the GUI.
From the GUI, the user can set multiple preferences, such as those for messaging, call control etc. SIP allows the user to set a variety of preferences to provide a customized experience to the user.
8. Subscriber privacy management based on the rules set on the GUI
The user can set privacy filters on the PNM server, that are enforced during call control. This is an essential enabler for call control supplementary services.
9. Call Screening service (MCID: Malicious Caller Identification)
This service is a variant of lawful intercept. However, it does not intercept the bearer, but only records the call trace and signaling information, that can later be used for security purposes by the operator.
10. Closed User Group Service (CuG), which will drive the Call Forwarding Services, and other group services.
The user can define a closed user group (buddy list) here. This is in addition to the personal network of devices that the user may own. Special services and tariffs can be applied to calls within a CuG.
11. Call Forwarding Service (which has the following variants):
11 a) Call Forwarding Unconditional (CFU)
11 b) Call Forwarding Busy (CFB)
11 c) Call Forwarding No Reply (CFNR)
11 d) Call Forwarding Not Logged in (CFNL)
11 e) Call Forwarding No Reply Conditional (CFNRc)
11 f) Communication Deflection (CD)
This is yet another popular supplementary service: both in the legacy world and the IMS world.
12. Message Waiting Indication service can be coupled with the core PNM logic.
MWI can be extended to all kinds of messages: SMS, IM, MMS and Voicemail. The user can get a reminder or alert that messages are waiting for him to be read/heard !
13. Communication Diversion (CDIV)
Communication sessions can be diverted based on user preferences on the GUI.
14. Explicit Call Transfer (ECT)
This is a variant of third party call control. It enables consultative and immediate transfer of ongoing SIP sessions. The call transfer can be facilitated by the PNM communications server.
So, this is the end game for the PNM server and the actual goal of this open source project:
“To provide value to the users, not by doing something very complicated or great, but by doing the simple things competently. “
By providing the user with simple utilities, everyday services can be enriched and made more user friendly. This is how we can add value to the user-experience for the customer. By clubbing existing services, we can create new ones, while still adding value to existing services.
I invite suggestions/feedback/additions regarding this post and the project in general. Contributions in any form or shape are welcome !!
Best Regards
Aayush
