Skip to main content

Advertisement

Log in

An OSCA architecture characterization of network functionality and data

  • Published:
Journal of Systems Integration

Abstract

This article demonstrates that the Bellcore OSCA architecture can serve as a basis for the metaarchitecture for software architectures that must support interoperability among functionality that traditionally has resided in operation systems and functionality that traditionally has resided in network elements (NE) (i.e., interoperability among operations functionality and network functionality). The need for this interoperability is driven by such telephone company business needs, as the need for customers to access operations capabilities spanning operations systems and NEs, the need for new service offerings to span operations systems and NEs, the need for a flexible environment for service development, and the need to manage all corporate data as a company resource. As a result, it is becoming beneficial to apply interoperability requirements to the network functionality that interfaces with operations systems. Therefore, it is reasonable to apply the OSCA architecture to network functionality. This article applies the OSCA architecture interoperability principles of separation of concerns to current and emerging network functionality. It demonstrates that this functionality can be partitioned among the three OSCA architecture layers of corporate data, processing, and user, and that there are a number of benefits to applying the OSCA interoperability principles to network functionality.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

References

  1. Advanced Intelligent Network Release 1 Baseline Architecture; Bellcore Special Report SR-NPL-001555; Issue 1, March 1990.

  2. B. Armbruster and F. Mellor, BNR, Ltd, “Switch architecture evolution in SONET network,” inIEEE Int. Conf. '90, pp. 310.1–310.1.5 1990.

  3. K. Balasubramanya and G. Rochlin, Telecom Australia, “Universal personal telecommunication: Concepts and requirements,” inIEEE Int. Conf. Comm. '90, pp. 233.1.1–233.1.5, 1990.

  4. S. Banerjee and R.C. Roman, “ISDN primary rate access maintenance,” inIEEE Int. Conf. Comm. '89, pp. 2.61(0058)–2.6.5(0062), 1989.

  5. R. Dreher, DSC Communications Corporation, “A highly distributed switching system architecture,” inIEEE Int. Conf. Comm. '90, pp. 319.2.1–319.2.4, 1990.

  6. J.A. Alfano and A. Mills, “Bringing harmony to heterogeneity: The operations systems computing architecture,” inIEEE Int. Conf. Comm. '89, pp. 29.1.1(0908)–29.1.7(0914), 1989.

  7. J.A. Mills, “The operations systems computing architecture: Semantic integrity of the totality of corporate data, inProc. 1st Int. Conf. Systems Integration, pp. 482, 491, April 1990.

  8. Information Networking Architecture: An Overview, Bellcore Framework Architecture Report FA-INS-001134, August 1990.

  9. Specification of Memory Administration Messages at the Operations System/Network Element Interface, Bellcore Technical Advisory TA-TSY-000199, Issue 4, November 1988.

  10. J.A. Alfano, E. Doran, and J.A. Mills, “The operations systems computing architecture,” inNational Comm. Forum Conf. Proc., pp. 165–172, 1989.

  11. Operations System/Network Element Network Traffic Data Structure and Messages, Bellcore Technical Advisory TA-TSY-000376, Issue 1, February 1987.

  12. Specification of Network Traffic Management Messages at the OS/NE Interface, Bellcore Technical Advisory TA-TSY-000495, Issue 1, March 1988.

  13. The Bellcore OSCA Architecture, Bellcore Technical Advisory TA-STS-000915, Issue 2, July 1990.

  14. An OSCA Architecture Characterization of Network Functionality and Data: Towards an INA Interoperability Architecture, Bellcore Special Report SR-STS-801899, Issue 1, January 1991.

  15. Operations Technology Generic Requirements (OTGR): Introduction, Bellcore Technical Reference TR-TSY-000471, Section 1 of OTGR, Issue 2, February 1988.

  16. Operations Technology Generic Requirements (OTGR): Memory Administration, Bellcore Technical Reference TR-TSY-000472, Section 2 of OTGR, Issue 2, February 1988.

  17. Operations Technology Generic Requirements (OTGR): Measurements and Data Generation, Bellcore Technical Reference TR-TSY-000478, Section 8 of OTGR, Issue 2, February 1988.

  18. I. Shimbo, K. Hayashi, and T. Takemura, “Next generation switching software architecture for intelligent network,” inIEEE Int. Conf. Comm. '90, pp. 319.5.1–319.5.5, 1990.

  19. H. Zimmermann, “Reference model—the ISO model of architecture for open systems interconnection, inIEEE Trans. Comm., vol. com-28(4), April 1980.

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

About this article

Cite this article

Mills, J.A. An OSCA architecture characterization of network functionality and data. Journal of Systems Integration 1, 81–95 (1991). https://doi.org/10.1007/BF02265067

Download citation

  • Received:

  • Revised:

  • Issue Date:

  • DOI: https://doi.org/10.1007/BF02265067

Keywords