Optimize your protocol-stack design
作者:Jim Darroch   发布时间:2007-04-06 11:53:05   浏览次数:642

GETTING THE MOST OUT OF ONE ASPECT OF YOUR DESIGN NEED NOT MEAN GIVING UP ANOTHER.

Implementations of single protocols, such as the SS7 (Signaling System Seven) telephony protocol often split into many layers. Definitions of other protocols specify individual or groups of layers, which may combine to meet the target application, such as with Sigtran (signaling transport). In most cases, a protocol layer feeds a higher protocol layer, an application, or a user at a terminal. Similarly, a protocol layer likely uses the services of a lower protocol layer or a physical device. Thus, a typical protocol layer comprises an upper layer interface-processing module, a state-machine engine that provides the layer's processing capability, and a lower layer interface-processing module.

A single protocol layer may have to serve multiple users accessing either multiple lower layer services or multiple instances of a single service (Figure 1). The interface portions of the protocol layer extend beyond the limits of the layer itself. The user portion contains both the layer's public API (application-program interface) and the layer's functions that implement the API. The layer's service portion contains both the lower layer public API and the functions that access it (Figure 2).





<< 1 2 3 >> ALL



本文评论

请填写详细信息发表评论

评论名字:
电子邮件:
评论内容:
验证字码:验证码

广告赞助商

边栏广告

Bigger the Ship,Longer the Travel,Thicker the Logs; cvl7163cf2485故知网站包括CMS、BBS和三个BLOG;详情可见“友情连接”;欢迎访问,欢迎指导。e-Mail: cf_John0@hotmail.com; cf_civill@126.com; cf_John0@mail2world.com