{"title":"Telephone switching systems software architecture: where have we been-where are we going?","authors":"W.H. Memmer","doi":"10.1109/ICC.1990.117195","DOIUrl":null,"url":null,"abstract":"Some of the history of telephone switching systems architecture is reviewed, and an overview of the directions being taken in this area is given. The switching software architecture envisioned for the future would allow an operating company to rapidly deploy new services in response to customers' needs. The open interface between call processing and service processing would permit the company to make deployment decisions based on business and operational considerations, in order to optimize service offerings. In fact, it should be possible to migrate service programs from one platform (e.g. the switch) to another (e.g. a centralized control point) and back again as needs dictate. All this could be done without the need for reprogramming call processing or service processing. With the standard program language used for application programming, every switch (independent of supplier) would have the same application software. That software could be acquired, module by module, from many diverse sources.<<ETX>>","PeriodicalId":126008,"journal":{"name":"IEEE International Conference on Communications, Including Supercomm Technical Sessions","volume":"15 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1990-04-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"IEEE International Conference on Communications, Including Supercomm Technical Sessions","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICC.1990.117195","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
Abstract
Some of the history of telephone switching systems architecture is reviewed, and an overview of the directions being taken in this area is given. The switching software architecture envisioned for the future would allow an operating company to rapidly deploy new services in response to customers' needs. The open interface between call processing and service processing would permit the company to make deployment decisions based on business and operational considerations, in order to optimize service offerings. In fact, it should be possible to migrate service programs from one platform (e.g. the switch) to another (e.g. a centralized control point) and back again as needs dictate. All this could be done without the need for reprogramming call processing or service processing. With the standard program language used for application programming, every switch (independent of supplier) would have the same application software. That software could be acquired, module by module, from many diverse sources.<>