Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Group info
Recent pages and files
Personal Network Management and IMS Supplementary Services Convergence    


 


      

The figure above shows the end to end integrated architecture of the Personal Network Management Server with IMS Supplementary services. As we all know, the PNM server is a device management framework, where the user can log in to a Graphical User Interface and configure his/her personal network of devices. The PNM server stores the user specific service profile in the XDM server. The PNM service can be chained with IMS call control supplementary services as shown above, in addition to other useful services.

 

Let us list each of them below:


1. Wake up Call Reminder service, which the user can configure over SIP or from the GUI.


2. Communication on Hold ( or Call hold) supplementary service.


3. Incoming and Outgoing communication barring based on user preferences.


4. Originating Identity Presentation and Restriction supplementary service.


5. Terminating Identity Presentation and Restriction supplementary service.


6. Call Blocking Service (Unconditional and partial)


7. Intelligent Caller preferences that can be set on SIP or from the GUI.


8. Subscriber privacy management based on the rules set on the GUI


9. Call Screening service (MCID: Malicious Caller Identification)


10. Closed User Group Service (CuG), which will drive the Call Forwarding Services, and other group services.


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) 


12. Message Waiting Indication service can be coupled with the core PNM logic. 


13. Communication Diversion (CDIV)


14. Explicit Call Transfer (ECT)


These services can be chained and combined on the JSLEE framework that consists of the PNM core application, the XDM server and this bouquet of IMS call control services, complete with a rich user interface (GUI). The XDM can serve as a common metadata repository. The GUI will work as a user interface for service provisioning and configuration and the services will be deployed on the JSLEE framework. 


With Regards


Aayush 

Version: 
Latest 3 messages about this page (5 total) - view full discussion
Feb 17 2009 by aayush
hi Ismael.

I have added you to the google code project just now.
Feb 17 2009 by aayush
Yes ismael. Communication is a more technical and formal word to
describe the services. I have tried to make it sound simple..as other
guys might not relate to the IMS lingo :)

CDIV is indeed a composite service, as rightly pointed out by you. In
a couple of days i will publish a list of standards that we will
Feb 17 2009 by Ismael
Hi Aayush,

Very interesting list of services. Just have some remarks. I think we
should prefer the word "Communication" to "Call". In the SIP/IMS
context, services are not just for voice, which the word "Call"
implies but any type of communication (video,messaging,...). Moreover,
all the communication forwarding are particular "Communication
2 more messages »
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google