My presentation at the BROADBANDCOM '09 conference in Wroclaw Poland on the potential for the use of a JAIN SLEE compliant server to model a service broker / SCIM for the IP Multimedia Subsystem
1. JAIN SLEE as a SCIM for the IP Multimedia Subsystem MosiuoaTsietsi Convergence Research Group Rhodes University, South Africa
2. Presentation Outline Service Triggering in the IMS Standards and Service Capabilities SCIM Interfaces and Interaction Models Architectural models for a SCIM JAIN SLEE Component architecture Analysis of JAIN SLEE Conclusion
5. Standards and Service Capabilities (1) Services have not been standardised by 3GPP Service capabilities have been defined: “basic mechanisms needed to realise services” Examples of service capabilities: Presence Messaging Conferencing Service capabilities can be combined to enable advanced services
8. Interfaces and Interaction Models (2) Use Case: iFC: Do SC1 on AS1, Do SC4 on AS2, Do SC6 on AS3 Interaction Logic: If History contains (SC1, Result a) SKIP SC4 and do SC6 If History contains (SC4, Result b) REPEAT SC4 If History contains (SC4, Result c) SKIP SC6 and STOP
11. Analysis of JAIN SLEE as SCIM (1) Implementation of Interfaces ISC developed using the JAIN SIP 1.1 or 1.2 API Cx interface developed using JDiameter stack Interaction logic Storage of iFC in SLEE Profiles?? Parent-child SBB relationships SLEE router Static and dynamic event delivery mechanism Shared attributes and Activity Contexts Architectural models Standalone SLEE server Peered SLEE server
14. Conclusion SCIM for IMS is not yet fully understood JAIN SLEE is fulfils the existing requirements of SCIM for IMS Providing interfaces Enabling dynamic chaining of services Fostering different architectural models The Mobicents projects provides potential development sandbox for modelling a SCIM