⭐ 欢迎来到虫虫下载站！ | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站
📤 上传资源

📄 001_1.htm

📁 通讯类的标准。对要开发SS7的朋友有很大帮助的。（通讯协议）
💻 HTM
字号:
🔍 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!-- saved from url=(0058)http://www.chinagk.org/technology/IPTech/001/css/001_1.htm -->
<HTML><HEAD><TITLE>001_1</TITLE>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<STYLE type=text/css>.pg {
	LEFT: 0px; WIDTH: 635px; POSITION: absolute; TOP: 0px; HEIGHT: 983px
}
BODY {
	FONT-SIZE: 13px; COLOR: #000000; FONT-FAMILY: ""; BACKGROUND-COLOR: #ffffff
}
A {
	TEXT-DECORATION: none
}
.ps0 {
	LEFT: 45px; WIDTH: 43px; POSITION: absolute; TOP: 64px
}
.ps1 {
	LEFT: 109px; WIDTH: 73px; POSITION: absolute; TOP: 159px
}
.ps2 {
	LEFT: 208px; WIDTH: 314px; POSITION: absolute; TOP: 156px
}
.ps3 {
	LEFT: 64px; WIDTH: 511px; POSITION: absolute; TOP: 210px
}
.ps4 {
	LEFT: 37px; WIDTH: 493px; POSITION: absolute; TOP: 232px
}
.ps5 {
	LEFT: 64px; WIDTH: 529px; POSITION: absolute; TOP: 253px
}
.ps6 {
	LEFT: 37px; WIDTH: 81px; POSITION: absolute; TOP: 272px
}
.ps7 {
	LEFT: 64px; WIDTH: 261px; POSITION: absolute; TOP: 294px
}
.ps8 {
	LEFT: 64px; WIDTH: 529px; POSITION: absolute; TOP: 314px
}
.ps9 {
	LEFT: 37px; WIDTH: 555px; POSITION: absolute; TOP: 334px
}
.ps10 {
	LEFT: 37px; WIDTH: 563px; POSITION: absolute; TOP: 355px
}
.ps11 {
	LEFT: 37px; WIDTH: 545px; POSITION: absolute; TOP: 376px
}
.ps12 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 398px
}
.ps13 {
	LEFT: 37px; WIDTH: 223px; POSITION: absolute; TOP: 417px
}
.ps14 {
	LEFT: 277px; WIDTH: 317px; POSITION: absolute; TOP: 417px
}
.ps15 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 438px
}
.ps16 {
	LEFT: 37px; WIDTH: 150px; POSITION: absolute; TOP: 458px
}
.ps17 {
	LEFT: 64px; WIDTH: 529px; POSITION: absolute; TOP: 479px
}
.ps18 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 500px
}
.ps19 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 520px
}
.ps20 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 541px
}
.ps21 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 562px
}
.ps22 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 582px
}
.ps23 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 603px
}
.ps24 {
	LEFT: 37px; WIDTH: 560px; POSITION: absolute; TOP: 624px
}
.ps25 {
	LEFT: 64px; WIDTH: 529px; POSITION: absolute; TOP: 644px
}
.ps26 {
	LEFT: 37px; WIDTH: 543px; POSITION: absolute; TOP: 665px
}
.ps27 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 687px
}
.ps28 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 706px
}
.ps29 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 727px
}
.ps30 {
	LEFT: 37px; WIDTH: 122px; POSITION: absolute; TOP: 748px
}
.ps31 {
	LEFT: 64px; WIDTH: 530px; POSITION: absolute; TOP: 768px
}
.ps32 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 789px
}
.ps33 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 810px
}
.ps34 {
	LEFT: 37px; WIDTH: 556px; POSITION: absolute; TOP: 830px
}
.ps35 {
	LEFT: 37px; WIDTH: 355px; POSITION: absolute; TOP: 851px
}
.ps36 {
	LEFT: 83px; WIDTH: 500px; POSITION: absolute; TOP: 896px
}
.ft0 {
	FONT-SIZE: 21px; COLOR: #000000; FONT-STYLE: italic; FONT-FAMILY: ""
}
.ft1 {
	FONT-SIZE: 28px; FONT-STYLE: italic; FONT-FAMILY: ""
}
.ft2 {
	FONT-SIZE: 27px; FONT-FAMILY: Arial,Helvetica,sans-serif
}
.ft4 {
	FONT-SIZE: 13px; FONT-FAMILY: "Times New Roman",Times,serif
}
.ft5 {
	FONT-SIZE: 9px; FONT-FAMILY: "Times New Roman",Times,serif
}
.em0 {
	FONT-SIZE: 13px; FONT-FAMILY: "Times New Roman",Times,serif
}
.em1 {
	FONT-SIZE: 13px; FONT-FAMILY: ""
}
.em2 {
	FONT-SIZE: 9px; FONT-FAMILY: "Times New Roman",Times,serif
}
.em3 {
	FONT-SIZE: 27px; FONT-STYLE: normal; FONT-FAMILY: Arial,Helvetica,sans-serif
}
.em4 {
	FONT-SIZE: 28px; FONT-STYLE: italic; FONT-FAMILY: ""
}
.em5 {
	FONT-SIZE: 11px; FONT-FAMILY: ""
}
.im0 {
	LEFT: 47px; WIDTH: 181px; POSITION: absolute; TOP: 24px
}
.im1 {
	LEFT: 261px; WIDTH: 7px; POSITION: absolute; TOP: 414px
}
.im2 {
	LEFT: 35px; WIDTH: 133px; POSITION: absolute; TOP: 887px
}
.im3 {
	LEFT: 65px; WIDTH: 8px; POSITION: absolute; TOP: 896px
}
</STYLE>

<META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD>
<BODY>
<DIV class=pg></DIV><!-- bitmap and vector images are written here -->
<DIV class=im0><IMG height=44 src="1-1.files/001_1_1.jpg" width=181 
border=0></DIV>
<DIV 
style="LEFT: 35px; BORDER-LEFT: #000000 1px solid; POSITION: absolute; TOP: 61px; HEIGHT: 27px"></DIV>
<DIV 
style="BORDER-TOP: #000000 1px solid; LEFT: 35px; WIDTH: 63px; POSITION: absolute; TOP: 61px"></DIV>
<DIV 
style="LEFT: 98px; BORDER-LEFT: #000000 1px solid; POSITION: absolute; TOP: 61px; HEIGHT: 27px"></DIV>
<DIV 
style="BORDER-TOP: #000000 1px solid; LEFT: 35px; WIDTH: 63px; POSITION: absolute; TOP: 87px"></DIV>
<DIV 
style="LEFT: 36px; WIDTH: 61px; POSITION: absolute; TOP: 61px; HEIGHT: 25px; BACKGROUND-COLOR: #ff8000"></DIV>
<DIV class=im1><IMG height=7 src="1-1.files/001_1_2.jpg" width=7 border=0></DIV>
<DIV class=im2><IMG height=2 src="1-1.files/001_1_3.jpg" width=133 
border=0></DIV>
<DIV class=im3><IMG height=9 src="1-1.files/001_1_4.jpg" width=8 border=0></DIV><!-- text starts here --><SPAN class=ps0><NOBR><SPAN 
class=ft0>文档</SPAN></NOBR></SPAN> <SPAN class=ps1><NOBR><SPAN class=ft1>第<SPAN 
class=em3>1</SPAN>章</SPAN></NOBR></SPAN> <SPAN class=ps2><NOBR><SPAN 
class=ft2>IP<SPAN class=em4>语音和交互应用的协议</SPAN></SPAN></NOBR></SPAN> <SPAN 
class=ps3><NOBR>通信界已经花了相当大的精力，要定义一个新的信号和介质传输的机制集，以期以同</NOBR></SPAN> <SPAN 
class=ps4><NOBR><SPAN class=ft4>PSTN<SPAN 
class=em1>相当的质量传输语音和语音带宽电话信号。这些工作集中在两个主要的领域：</SPAN></SPAN></NOBR></SPAN> <SPAN 
class=ps5><NOBR><SPAN class=ft4>1) <SPAN 
class=em1>开发支持普通电话服务的所有呼叫特性的复杂的信令服务，同时也支持下一代交互式</SPAN></SPAN></NOBR></SPAN> 
<SPAN class=ps6><NOBR>多媒体服务。</NOBR></SPAN> <SPAN class=ps7><NOBR><SPAN 
class=ft4>2) <SPAN class=em1>开发以最高质量传输介质流的传输机制。</SPAN></SPAN></NOBR></SPAN> 
<SPAN class=ps8><NOBR>在第<SPAN class=em0>1</SPAN>章中，将研究<SPAN 
class=em0>IP</SPAN>电话中使用的主流的信令协议，并与数据协议进行比较。<SPAN 
class=em0>IP</SPAN>网络中</NOBR></SPAN> <SPAN class=ps9><NOBR>的介质传输机制是实时传输协议（<SPAN 
class=em0>Real-time Transport Protocol</SPAN>，<SPAN class=em0>RTP</SPAN>，<SPAN 
class=em0>RFC 1889</SPAN>），而实时传</NOBR></SPAN> <SPAN class=ps10><NOBR>输控制协议（<SPAN 
class=em0>Real-time Transport Control Protocol</SPAN>，<SPAN 
class=em0>RTCP</SPAN>）为呼叫中的参与者提供<SPAN class=em0>QoS</SPAN>信息。</NOBR></SPAN> 
<SPAN class=ps11><NOBR>呼叫建立中的信令因为其内在的复杂性而非常富有挑战性，这种复杂性是因为它支持过多的</NOBR></SPAN> 
<SPAN class=ps12><NOBR><SPAN class=ft4>POTS<SPAN 
class=em1>电话特性和附加的增值服务。</SPAN>POTS<SPAN 
class=em1>服务可能已经过时，但是它的普通性和简单性正是</SPAN></SPAN></NOBR></SPAN> <SPAN 
class=ps13><NOBR>新技术中要实现的。支持客户<SPAN class=em0>CLASS</SPAN></NOBR></SPAN> <SPAN 
class=ps14><NOBR>特性集是<SPAN class=em0>VoIP</SPAN>服务要实现的一个艰巨任务，缺少这种</NOBR></SPAN> 
<SPAN class=ps15><NOBR>支持能力，<SPAN 
class=em0>VoIP</SPAN>在市场上将很难被接受。当在服务全景图中加入集成的实时服务时，不难看</NOBR></SPAN> <SPAN 
class=ps16><NOBR>出这个问题的严重程度。</NOBR></SPAN> <SPAN 
class=ps17><NOBR>在信令和呼叫处理领域中，目前发现的最受欢迎的方法和标准是来自<SPAN class=em0>ITU</SPAN>的<SPAN 
class=em0>H.323<SPAN class=em1>，</SPAN></SPAN>即会</NOBR></SPAN> <SPAN 
class=ps18><NOBR>话初始化协议（<SPAN class=em0>Session Initiation Protocol</SPAN>，<SPAN 
class=em0>SIP</SPAN>，<SPAN class=em0>RFC 
2543</SPAN>）和另一个复杂的协议标准，后面</NOBR></SPAN> <SPAN class=ps19><NOBR>称为<SPAN 
class=em0>S/MGCP</SPAN>。<SPAN class=em0>SIP</SPAN>和<SPAN 
class=em0>MGCP</SPAN>是<SPAN class=em0>IETF</SPAN>的<SPAN 
class=em0>RFC</SPAN>标准。<SPAN class=em0>SGCP</SPAN>是最初的协议，但是结合<SPAN 
class=em0>IPDC</SPAN>协议和</NOBR></SPAN> <SPAN class=ps20><NOBR>它自身的优点以后得到了<SPAN 
class=em0>MGCP<SPAN class=em1>，</SPAN></SPAN>这时就不再使用<SPAN 
class=em0>SGCP</SPAN>协议了。我们将在本章中讨论所有这</NOBR></SPAN> <SPAN 
class=ps21><NOBR>些术语。作者见到过很多这种情况，即一种特定的设计方法的优点的反馈开始源源不断出现</NOBR></SPAN> <SPAN 
class=ps22><NOBR>时，该方法的增强性的建议也开始出现，而其中的一些意见往往与市场上建立起来的方法背</NOBR></SPAN> <SPAN 
class=ps23><NOBR>道而驰。虽然目标是要尽量找到一种无差错地控制<SPAN 
class=em0>VoIP</SPAN>网络的解决方法，但是市场力量最终</NOBR></SPAN> <SPAN 
class=ps24><NOBR>占了上风，具有最大的市场接受能力的产品将占据主导，而不管新的方法有什么潜在的优点。</NOBR></SPAN> <SPAN 
class=ps25><NOBR>其他的基于<SPAN 
class=em0>IP</SPAN>的协议由于对信令协议的支持，也找到了一席之地。这些辅助协议中的一</NOBR></SPAN> <SPAN 
class=ps26><NOBR>部分通过提供可预报的<SPAN 
class=em0>QoS</SPAN>的方法，增强了基本信令机制的服务性能，其中的一个例子是</NOBR></SPAN> <SPAN 
class=ps27><NOBR><SPAN class=ft4>RSVP<SPAN class=em1>。会话描述协议（<SPAN 
class=em0>Session Description Protocol</SPAN>，<SPAN class=em0>SDP</SPAN>，<SPAN 
class=em0>RFC 2327</SPAN>）是另一个辅助机制协</SPAN></SPAN></NOBR></SPAN> <SPAN 
class=ps28><NOBR>议，为基本的信令协议提供描述呼叫会话参数的能力。随着服务供应商开始深入讨论提供交</NOBR></SPAN> <SPAN 
class=ps29><NOBR>互式多媒体服务和<SPAN class=em0>VoIP</SPAN>技术的成熟，<SPAN 
class=em0>VoIP</SPAN>呼叫控制有望包含一组基于<SPAN 
class=em0>IP</SPAN>协议的套件，用于实</NOBR></SPAN> <SPAN 
class=ps30><NOBR>现基本的信令功能。</NOBR></SPAN> <SPAN 
class=ps31><NOBR>由于服务供应商相信他们选择的标准将超越其他基于<SPAN 
class=em0>IP</SPAN>的信令实现的建议和标准，使用</NOBR></SPAN> <SPAN 
class=ps32><NOBR>所有三种主流信令方法的产品有望最早得到接受。点到点和会议式的呼叫标准有时很容易混</NOBR></SPAN> <SPAN 
class=ps33><NOBR>淆，即使在该领域中富有经验的人也是如此。从阅读<SPAN 
class=em0>RFC</SPAN>和一些规范中很难断定某种特定解</NOBR></SPAN> <SPAN 
class=ps34><NOBR>决方案被接受的程度。选择实现方案和标准的代价相当高。与工业界的准则一致，&nbsp;<SPAN 
class=em0>VoIP</SPAN>信令</NOBR></SPAN> <SPAN 
class=ps35><NOBR>中的有些计划离它们的支持者的长期看法有着不小的差距。</NOBR></SPAN> <SPAN 
class=ps36><NOBR><SPAN class=ft5>CLASS<SPAN class=em5>代表自定义局域信令服务（<SPAN 
class=em2>Custom Local Area Signaling Services</SPAN>），例如呼叫者</SPAN>ID<SPAN 
class=em5>、特色振铃等。</SPAN></SPAN></NOBR></SPAN> </BODY></HTML>

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -