Intelligent network application programming interface server architecture

C. Solomonides, M. Scaric
{"title":"Intelligent network application programming interface server architecture","authors":"C. Solomonides, M. Scaric","doi":"10.1109/INW.2000.868163","DOIUrl":null,"url":null,"abstract":"This article consists of a collection of slides from the author's PowerPoint conference presentation. The paper argues that the diversity of services and networks, demands a fresh approach to service creation. The authors argue that the Application Programming Interface (API) approach promises to meet many of the demands of service creation in the new environment. Formalising at the level of the API in service creation allows the underlying control structures the flexibility to be ahnost completely proprietary in nature. However it will be argued that the API approach demands new additional structures to make the model commercially viable. This paper examines the requirements of the API server and introduces the notion of an API state-machine. An API server allows third party software providers or end users access to control resources without regard to how the offered services are to be implemented. It must therefore provide the flexibility of service creation with the restriction placed by policing functions to protect against misuse of code or malicious intent The server must also provide access to support infrastructures such as billing systems and management systems. In addition it also needs to be capable of fme grained process control. Hence, the aims of the state machine are complex. The paper describes work being done at UCL in defining a state machine, similar in many respects to that of the Basic Call State Model and the Call Party Handling model but for the API server case. The state machine aims to mask the service on offer from the external requests. It also aims to reduce the interfaces between service providers to a simple state machine view that seeks to eliminates problems such as deadlock or integrity violations between complex multiple service provider interactions. The paper also examines the relationship between API approaches and the TINA framework. It argues that TINA evolution can be pushed forward by an intermediate API stage in development","PeriodicalId":430457,"journal":{"name":"Proceedings 2000 IEEE Intelligent Network Workshop","volume":"410 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2000-05-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings 2000 IEEE Intelligent Network Workshop","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/INW.2000.868163","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0

Abstract

This article consists of a collection of slides from the author's PowerPoint conference presentation. The paper argues that the diversity of services and networks, demands a fresh approach to service creation. The authors argue that the Application Programming Interface (API) approach promises to meet many of the demands of service creation in the new environment. Formalising at the level of the API in service creation allows the underlying control structures the flexibility to be ahnost completely proprietary in nature. However it will be argued that the API approach demands new additional structures to make the model commercially viable. This paper examines the requirements of the API server and introduces the notion of an API state-machine. An API server allows third party software providers or end users access to control resources without regard to how the offered services are to be implemented. It must therefore provide the flexibility of service creation with the restriction placed by policing functions to protect against misuse of code or malicious intent The server must also provide access to support infrastructures such as billing systems and management systems. In addition it also needs to be capable of fme grained process control. Hence, the aims of the state machine are complex. The paper describes work being done at UCL in defining a state machine, similar in many respects to that of the Basic Call State Model and the Call Party Handling model but for the API server case. The state machine aims to mask the service on offer from the external requests. It also aims to reduce the interfaces between service providers to a simple state machine view that seeks to eliminates problems such as deadlock or integrity violations between complex multiple service provider interactions. The paper also examines the relationship between API approaches and the TINA framework. It argues that TINA evolution can be pushed forward by an intermediate API stage in development
智能网络应用编程接口服务器架构
本文由作者的PowerPoint会议演示的幻灯片集合组成。本文认为,服务和网络的多样性需要一种新的服务创造方法。作者认为,应用程序编程接口(API)方法有望满足新环境中服务创建的许多需求。在服务创建的API级别进行形式化,使得底层控制结构的灵活性在本质上几乎是完全专有的。然而,有人认为,API方法需要新的附加结构,以使该模型具有商业可行性。本文研究了API服务器的需求,并介绍了API状态机的概念。API服务器允许第三方软件提供商或最终用户访问控制资源,而无需考虑所提供的服务如何实现。因此,它必须在监管功能的限制下提供服务创建的灵活性,以防止代码滥用或恶意意图。服务器还必须提供对支持基础设施(如计费系统和管理系统)的访问。此外,它还需要能够进行细粒度的过程控制。因此,状态机的目标是复杂的。本文描述了UCL在定义状态机方面所做的工作,在许多方面类似于基本调用状态模型和呼叫方处理模型,但针对API服务器的情况。状态机的目的是对外部请求屏蔽所提供的服务。它还旨在将服务提供者之间的接口简化为一个简单的状态机视图,以消除复杂的多个服务提供者交互之间的死锁或完整性违反等问题。本文还研究了API方法与TINA框架之间的关系。它认为,在开发的中间API阶段可以推动TINA的发展
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信