Weblogs

Clouds, Federated User Profiles and IMS: Most Communications Service Providers consider their customer relationships, and the specific knowledge they have of their customers, as the cornerstone of their long-term success. Nearly every major...
Posted by Michael Palmeter (mpalmete) on April 23, 2008 at 12:33 PDT | Comments (0)  

SIP Servlet 1.1:
Posted by Michael Palmeter (mpalmete) on December 03, 2007 at 11:56 PDT | Comments (0)  

Vision and Value: Standards-based, Web-centric Communications Service Delivery Platforms:
Posted by Michael Palmeter (mpalmete) on October 05, 2007 at 17:16 PDT | Comments (0)  

Great BLOG on IMS (and SCIM in particular):
Posted by Michael Palmeter (mpalmete) on July 08, 2007 at 20:10 PDT | Comments (0)  

Why I think "Web 2.0" is Important:
Posted by Michael Palmeter (mpalmete) on July 05, 2007 at 14:50 PDT | Comments (0)  

Caching and REST Web services:
Posted by Michael Palmeter (mpalmete) on July 03, 2007 at 16:07 PDT | Comments (0)  

xcap-client: AJAX XCAP Client:
Posted by Michael Palmeter (mpalmete) on June 29, 2007 at 16:05 PDT | Comments (0)  

microformats | About microformats:
Posted by Michael Palmeter (mpalmete) on June 29, 2007 at 15:49 PDT | Comments (0)  

The Problem Wth Distributed Systems and the Benefit of Co-Location: With so much attention being paid to architectural concepts that involve Internet-scale distributed systems, I sometimes think that there is an important point that is being overlooked. Software architectures that allow for distribution of loosely-coupled, re-usable application components are very helpful in reducing ongoing maintenance, development and integration costs and effort, but no architecture should require that components arbitrarily be distributed. In fact, most implicitly do not, although I think this could be stated more clearly.
Posted by Michael Palmeter (mpalmete) on July 18, 2006 at 14:16 PDT | Comments (1)  

SIP Servlet 1.1 (JSR 289) and the Service Interaction IMS: The JSR 289 (SIP Servlet API 1.1) expert group is being lead by Nasir Khan, the Chief Architect of the BEA WebLogic SIP Server. Nasir has been kind enough to keep us updated on the progress of the specification and I am very enthusiastic about the potential of that JSR to, at least partially, resolve some of the varied concerns about the Service Capability Interaction Manager problem in IMS.
Posted by Michael Palmeter (mpalmete) on July 16, 2006 at 15:08 PDT | Comments (0)  

Representational State Transfer (REST) and Data Distribution in SIP/IMS Networks: Representational State Transfer (REST) is a Web services approach that is the foundation of the World Wide Web, although it may not always be acknowledged as such. Within the IT community, the Web Services Definition Language and Simple Object Access Protocol tend to dominate the discussion about distributed Service Oriented Architectures. The XML Configuration Access Protocol, however, offers a REST solution to the problem of efficient data distribution in SIP networks. Moreover, XCAP may e used in conjunction with SIP for session management and state change notification to create a highly scalable, efficient and flexible system for data distribution. Although this approach may not seem intuitive to many IT architects, it is currently the basis for information management in IMS and is poised to move beyond Presence and Group List Management and into runtime configuration and management of network edge devices, policy distribution and application sesion state management. In short, this set of technologies is poised to become the primary point of contact between the SDP and the IMS core network
Posted by Michael Palmeter (mpalmete) on May 02, 2006 at 07:53 PDT | Comments (0)  

Service Capability Interaction Management (SCIM) in IMS: The Service Capability Interaction Manager (SCIM) is one of the least well defined "entities" introduced by the 3GPP standards for IMS. In fact, it could be argumed that it is not an entity at all, but merely a standard label for a common, but non-standard, problem.
Posted by Michael Palmeter (mpalmete) on February 07, 2006 at 08:57 PDT | Comments (3)  

So What is an "IMS Service", Anyhow?: SIP and IMS buzz is sweeping the Telecommunications industry. This new focus is the result of two divergent needs. In the near term, there is a bottom-line requirement replicate existing communications services on lower cost all-IP infrastucture. In the medium and long terms, service providers need a new network architecture that can support a diverse array of new top-line revenue generating services. In this discussion, however, it can be unclear whet these new "services" actually are - even the term "service" is often used in different contexts and with distinctly different meanings.
Posted by Michael Palmeter (mpalmete) on February 02, 2006 at 12:09 PDT | Comments (3)  

Separating SIP from the VoIP Umbrella: One thing that stands out to me about the current state of the discussion surrounding applications of SIP. SIP is not just about VoIP, although many of the current field of applications for SIP do involve VoIP in the context of multimedia sessions over IP. The truth, however, is that SIP is a relatively application-agnostic protocol that is primarily useful for supporting session management and user mobility. In many ways SIP represents a new layer on the Internet - the "missing protocol" as it were. Although the current buzz is very much driven by VoIP, SIP will come to be seen as something more fundamental than as a supporting protocol for VoIP applications. In fact, VoIP is merely the tip of the iceberg.
Posted by Michael Palmeter (mpalmete) on January 10, 2006 at 07:14 PDT | Comments (1)  

Telecom has an SOA too - the IMS: Although I'm something of a "Telecom guy", based on my recent experience with that industry, there are a number of similarities between the evolution of the Telecom business and the historic changes in Enterprise IT. In some ways, the move toward three-tier client/server architectures from the verticalized applications the last-generation mainframe systems were built to deliver is comparable to what is happening in the Telecommunications business. In the Telecom buisness, though, the leap from tightly-coupled, vertical systems to a fully distributed SOA is happening in one shot. In effect, the lessons of the IT industry and the architectures that drove the World Wide Web are being incorporated into the Next-Generation IP-based communications standards and the architecture that has emerged is similar, at a high level, to the SOAP-based SOA we seem to be referring to when we use that term.
Posted by Michael Palmeter (mpalmete) on January 09, 2006 at 10:49 PDT | Comments (4)