com- mon APIs based on an open component model with well-defined interoperable protocols and deployment models serve to accomplish the goal. OSS/J initiative is performed under the open Java community process (JCP). Using JCP the initiative will develop the following for each application area: Specification documents: It details the interface APIs. Reference implementation (RI): This is a working version that facilitates use of the APIs. Technology compatibility kit (TCK): A suite of tests, tools, and documen- tation that will allow third parties to determine if their implementation is compliant with the specification. Production of demonstration systems to validate the OSS/J APIs against suitabil- ity for supporting actual field scenarios is a major goal of OSS through the Java initiative. These systems should also meet performance and scalability for usage in actual field scenarios. Defining OSS through Java APIs and maturing APIs from other sources results in the addition of more complete business scenarios to the demonstration systems. The OSS applications are divided into three fundamental parts by the J2EE application model. The three parts are: Components: The application developed is comprised of a set of components. This makes components the key focus area for application developers. Containers: It provides service transparently to both transaction support and resource pooling. Using containers, component behaviors can be specified at deployment time, rather than in the program code. Containers also provide security in addition to transaction support. Connectors: Connectors define a portable service API to plug into existing OSS vendor offerings. It is a layer beneath the J2EE platform and promotes flexibility by enabling a variety of implementations of specific services. System vendors can conceal complexity and remote portability by implementing con- tainers and connectors. Use of OSS/J has many benefits to different players in the telecom value chain. To equipment vendors, it facilitates integration o