|
|
|
 mess@ge home
Table of contents
|
JAIN - Bringing Java technologies into
communications
Service Providers and network operators are mandating standard network interfaces for building open network computing service architectures. With revenues from simple network access in the decline, operators are turning their attention to building out network infrastructure to support differentiated services that bring in more revenue. This is where Java™ and JAIN™ technologies make a difference. The JAIN Initiative points Java right into communications, defining a standard set of interfaces and fusing the Java language with fundamental networking concepts and interfaces. At the "JAIN Community Meetings" at Eurescom on April 22-26, network operators clearly spelled out a common message to the communications vendors: Standard application programming interfaces (APIs) are required to open the network for new cost effective services. So what is the great divide? The difference between what operators want, and what vendors deliver. This may sound mundane and obvious, however, this was a key message repeated by all the network operators at the service provider / operator summit held during the JAIN community meetings at Eurescom. For Paul Jaramillo of Qwest, "System Integration is the key." His message to vendors: "Don’t view your application server as the central point of control for all services in the network. We need to assume a multi-vendor environment where integration is required." He further explained that system integration complexity must be mitigated through the promotion of key interfaces and service architecture convergence. Vendors’ products, Paul Jaramillo is covinced, will need to integrate with other vendors at the right places that the carrier requires, not just at the point that the vendor wants. This sentiment was repeated several times. Hidefumi Nakamura, Senior Architect at NTT, delivered a succinct message: "NTT’s vision for open architecture is to enforce vendors to develop systems according to carrier-oriented API/interfaces, which will reduce costs of network components by introducing competition among vendors". The operators were very forthcoming with their agenda ? open network architectures through standard communications APIs. Chris Shaw of Orange announced that his company would offer JAIN SPA (Service Provider APIs) as one of their external third party access interfaces. Orange regards JAIN SPA as a minimal entry requirement for vendors. "Open network interface is the thrust of our whole Next Generation Services Environment. JAIN SPA in the service creation and service execution layers will definitely be needed as one part of our solution", explained Chris Shaw Steve Mueller of SBC, author of ‘APIs and Protocols for Convergent Network Services’, raised the bar. For him, the question 'Will there be any new services at all?' is more important than time-to-market for new services. He is convinced that"we must have APIs in order to build services. The protocols are the glue, but the APIs are what allow you to do interesting things."
About 100 participants attended the JAIN Technology Workshop So what is JAIN technology? Java into communications, taking Java to the next logical step for network computing: Service Portability, Network Convergence, and Secure Network Access. Let it rain JAIN! The world of enterprise computing meets the world of network computing, and JAIN technology is making it happen. Important facts –
Swee Lim (SUN) explaining the JAIN components The Community moved the JAIN initiative to the next step by introducing a JAIN Council, and focus teams around IP Communications, JAIN Service Provider APIs, and Operators. The Focus teams and the JAIN Council consist of Community members driving technical and marketing direction for the JAIN Community. The JAIN meetings also included:
Conclusion While JAIN technologies are not the panacea to solve all network problems, JAIN Solutions provide an integral path forward to open the network to a wide variety of services and expand the industry into new markets by levelling the playing field. Elmar Weber of Vodafone summarized nicely – "Telco-specific development will be facilitated by using off-the-shelf middleware platforms, along with component-centric software platforms and architectures, such as J2EE and JAIN SLEE. With this we can see a reduction in infrastructure costs and opportunities for new revenue-generating services." For more information: http://java.sun.com/products/jain or e-mail to JAINteam@sun.com JAIN discussion lists: http://archives.java.sun.com Please send us your comments on this article. |
||||||||||
