- 浏览: 175008 次
- 性别:
- 来自: 成都
文章分类
最新评论
-
行动与思考:
你好!请问GraphicString这个类型是什么类型呀?怎么 ...
ACSE-1 (osi 8650-1)abstract syntax -
gaozon:
楼主,你好,请问用lua能编写这样一种插件吗:我想更改网络层i ...
编程语言 Lua -
langzhe:
percept:profile("test.dat& ...
erlang r12 新增加Percept并发性能调测模块 -
mryufeng:
解释epmd等2进制协议是erlang的拿手呀
Use Erlang NIF to snoop, capture packets(in Windows XP), in OTP-R13B04 -
xumingyong:
GeoffCant在git clone git://git.e ...
Use Erlang NIF to snoop, capture packets(in Windows XP), in OTP-R13B04
Get from http://wiki.wireshark.org/IsoProtocolFamily
Summary
Packet-based vs. stream-based:
COTP transports packets of data from one user to the other, so the receiver will get exactly the same data boundaries as the sender transmitted.
TCP transports a continuous stream of data to the receiver, so the protocol on top of TCP often has to add such boundaries itself (see the TPKT protocol for such a protocol).
TSAPs vs. ports:
To multiplex several conversations between two hosts, COTP uses TSAP's which are variable length binary blobs (often a meaningful string is used).
These TSAP's are matched at connection establishing phase, and replaced by the 2 byte (destination/source) references at data transfer.
TCP uses ports for this. One notable difference is that TSAP's are singletons - if a TSAP is used for a connection it cannot be used by another. XXX - Needs clarification. A single TSAP (Transport Service Access Point) may be used by multiple connections.
Tranport Layer:
Protocol Note
------------ ---------------------------------------------------------------------------------------
COTP
TPKT = TPKT works on TCP port 102 to emulate COTP
TCP
----------------------------------------------------------------------------------------------------------------
1. TPKT = RFC 1006
It start with \x03\X00.
TPKT is used to "emulate" ISO transport services COTP on top of TCP. The two major points missing in TCP (compared to COTP) are the TSAP addressing and the detection of packet boundaries on the receiving host.
Note that only TPDUs formatted for transport class 0 [TP0] are exchanged (different transport classes may use slightly different formats).
Include Packet Header and TPDU, The format of the TPDU is defined in [ISO8073].
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| vrsn | reserved | packet length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Header:version = always 3, 1 byte
TPDU = max. 65531. Based on the size of the data transfer (DT) TPDU, this permits a maximum TSDU size of 65524 octets.
2. COTP = ISO 8073 / RFC983
Connection-oriented transport protocol
To support expedited data, a non-standard TPDU, for expedited data is permitted. The format used for the ED TPDU is nearly identical to the format for the normal data, DT, TPDU. The only difference is that the value used for the TPDU's code is ED, not DT:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| header length | code |credit |TPDU-NR and EOT| user data |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... | ... | ... |
| ... | ... | ... | ... |
| ... | ... | ... | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TPDU Code
-------------------
CR = 0xE0, Connection Request
CC = 0xD0, Connection Confirm
DR = 0x80, Disconnection Request
DT = 0xF0, Data Transfer
ED = 0x70, Expected Data transfer
After the credit field (which is always ZERO on output and ignored on input), there is one additional field prior to the user data.
TPDU-NR and EOT = 8 bits
Bit 7 (the high-order bit, bit mask 1000 0000) indicates the end of a TSDU. All other bits should be ZERO on output and ignored on input.
The format of a CR or CC TPDU is:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| header length | code | credit| destination reference |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| source reference | class |options| variable data |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... | ... | ... |
| ... | ... | ... | ... |
| ... | user data | ... | ... |
| ... | ... | ... | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format of a DR TPDU is:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| header length | code | credit| destination reference |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| source reference | reason | variable data |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... | ... | ... |
| ... | ... | ... | ... |
| ... | user data | ... | ... |
| ... | ... | ... | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format of a DT or ED TPDU is:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+
| header length | code | credit| TPDU-NR and EOT |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| user data | ... | ... | ... |
| ... | ... | ... | ... |
| ... | ... | ... | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3. ISO 8327-1
ISO Session Protocol
Format
-----------------------------------------------
SPDU Type -- 1 byte
Length -- 1 byte
Connect Accept Item -- 8 bytes
Session Requirement -- 4 bytes
Calling Session Selector -- 4 bytes
Called Session Selector -- 4 bytes
Session User Data -- ...
ISO Session Protocol (ISO-SP) Messages:
Functional unit |
SPDU code |
SPDU name |
Kernel |
CN |
CONNECT |
Negotiated release |
NF |
NOT FINISHED |
Half-duplex |
GT |
GIVE TOKENS |
Duplex |
|
No additional associated SPDUs |
Expedited data |
EX |
EXPEDITED DATA |
Typed data |
TD |
TYPED DATA |
Capability data exchange |
CD |
CAPABILITY DATA |
Minor synchronize |
MIP |
MINOR SYNC POINT |
Symmetric synchronize |
MIP |
MINOR SYNC POINT |
Data separation |
|
No additional associated SPDUs |
Major synchronize |
MAP |
MAJOR SYNC POINT |
Resynchronize |
RS |
RESYNCHRONIZE |
Exceptions |
ER |
EXCEPTION REPORT |
Activity management |
AS |
ACTIVITY START |
4. ISO 8823
ISO Presentation Protocol, on top of ASN.1, BER.
Frame format
-------------------------------------------------------------------------
Mode-selector -- 3 bytes
Normal-mode-parameters
Padding -- 1 byte
Protocol-version -- 1 byte, 80 = version-1
calling-presentation-selector -- 4 bytes
called-presentation-selector -- 4 bytes
presentation-contex-definition-list -- ??
Padding -- 1 byte
Presentation- requirement -- 1 byte
User-data -- ...
Protocol Structure - ISO-PP: OSI Presentation Layer Protocol (X.226, X.216, ISO 8823, 8822)
Connection Release Primitive Token Handling Primitive P-RELEASE request P-RELEASE indication P-RELEASE response P-RELEASE confirm P-TOKEN-GIVE request P-TOKEN-GIVE indication P-TOKEN-PLEASE request P-TOKEN-PLEASE indication P-CONTROL-GIVE request P-CONTROL-GIVE indication Presentation Exception Reporting Primitive Activity Management Primitive P-P-EXCEPTION-REPORT indication P-U-EXCEPTION-REPORT request P-U-EXCEPTION-REPORT indication P-ACTIVITY-START request P-ACTIVITY-START indication P-ACTIVITY-RESUME request P-ACTIVITY-RESUME indication P-ACTIVITY-INTERRUPT request P-ACTIVITY-INTERRUPT indication P-ACTIVITY-NTERRUPT response P-ACTIVITY-INTERRUPT confirm P-ACTIVITY-DISCARD request P-ACTIVITY-DISCARD indication P-ACTIVITY-DISCARD response P-ACTIVITY-DISCARD confirm P-ACTIVITY-END request P-ACTIVITY-END indication P-ACTIVITY-END response P-ACTIVITY-END confirm Synchronization Services Primitive P-SYNC-MINOR request P-SYNC-MINOR indication P-SYNC-MINOR response P-SYNC-MINOR confirm P-SYNC-MAJOR request P-SYNC-MAJOR indication P-SYNC-MAJOR response P-SYNC-MAJOR confirm
5. ISO 8650-1, ACSE-1
ISO Association Control Service Element (Layer 7)
The OSI method for establishing a call between two application programs. ACSE checks the identities and contexts of the application entities, and could apply an authentication security check.
ICCP uses the ISO Association Control Service element (ACSE) to establish logical associations. Multiple associations may be established from a client to multiple, different control center servers.
Application Association & network connection are different.
6. MMS
ISO 9506-2
发表评论
-
IEC60870-5-104集锦
2009-05-12 20:00 3209=============================== ... -
基于TCP/IP的IEC60870-5-104远动规约在电力系统中的应用
2009-05-12 15:45 2345摘 要 : ... -
基于TCP/IP的IEC60870-5-104远动通信协议
2009-05-12 15:36 4370介绍了国际电工委员会制定的基于TCP/IP网 络的调度主站和 ... -
Capture file header format
2009-04-21 16:44 1480截获包的文件头格式 (比如:wireshark, e ... -
TCP Socket类型
2009-04-20 20:19 1824对于许多初学者来说, ... -
ASN.1 of MMS related Protocol, totally 8 files
2009-04-17 12:56 1331Download Link: http://xu ... -
ACSE-1 (osi 8650-1)abstract syntax
2009-04-14 17:39 2319-- Module ACSE-1 (X.227:04/1995 ... -
MMS报文分析示例(三)
2009-04-14 10:43 3146Variable Management 1. ... -
MMS报文分析示例(二)
2009-04-14 10:39 3536VMD Management 1. Ident ... -
Triangle MicroWorks, Inc
2009-04-14 02:13 1495发现Triangle MicroWorks, Inc公司不愧为 ... -
ASN.1 -- MMS --ICCP ( TABSE2)
2009-04-14 02:04 2141MMS的ASN.1规定( 8825-1 BER 8825-2 ... -
MMS Syntax (ISO 9506-2:1999)
2009-04-13 13:27 1721Updated and fixed on 2006-08-11 ... -
MMS报文分析示例(一)
2009-04-13 12:08 3169Context Management 1. ... -
MMS abstract syntax (sisco)
2009-04-13 10:39 2256Get from http://www.sisconet. ... -
MMS->OSI MODEL
2009-04-12 22:36 1399Kema UniCA analyzer Provid ... -
MMS笔记(一)
2009-04-12 22:23 1861=============================== ... -
asn.1的ber编码
2009-04-12 22:06 4150ASN.1即抽象语法符号,用来定义应用程序数据和表示[wi ... -
MMS编码
2009-04-12 22:03 2378Telecontrol Application Service ... -
WireShark Lua Example
2009-04-11 16:42 2862From: http://wiki.wireshark.org ... -
使用lua编写Wireshark的dissector插件
2009-04-11 16:33 5725Dissector 插件可以用来对特定的协议内容进行分析展示 ...
相关推荐
C# -mms编码格式 /* 发送MMS的过程 1> 创建消息发送接口 2> 设置参数属性 ms.SetMMSC"http://mmsc.monternet.com"); ms.SetProxy("10.0.0.172:80"); 3> 创建消息 4> 设置消息内容 5> 发送消息 6> ...
standard, the division of protocol specification and encoding represents a different philosophy from many of the previous SCADA protocols. However, given all the required documentation, it still takes...
mms彩信mm1的实现方式,有兴趣的朋友可以来参考下
mms报文规范mms报文规范mms报文规范
MMS 架构,信息封装,Wireless Session Protocol Specification,Wireless Transaction Protocol 技术参考
MMS系统使用了图所示的协议栈结构在这种框架结构之内,MMS用户代理通过MMS中继器与MMS服务器通信。MMS中继器应该提供MMS 服务器与MMS用户代理之间功能的会聚,因而可以在不同的网络类型上实现不同类型服务器的集成。...
MMS制造报文规范的标准PDF文档。
PDU SMC&MMS数据协议解析分析.xls
根据WAP MMS Encapsulation Protocol相关协议规定, 举例解析一个彩信通知的pdu, 详细介绍了pdu里每个字段的含义。
MMS Ethereal软件的安装包。该软件用于对网络中所传输的数据包的抓取,并且进行解析。
华为MMS开发指南,mms开发必备。强烈推荐-Huawei华为MMS开发指南,mms开发必备。强烈推荐-Huawei
短信资料短信资料短信资料短信资料短信资料短信资料短信资料短信资料短信资料短信资料
一款用于变电站61850监控系统报文监视工具
MMS PDU由MMS头和消息体组成。MMS头具体的描述了PDU的特定信息,消息体是可选的 本文介绍了SMS,EMS,MMS在传输内容、传输机制上的区别。深入讨论了 MMS协议的消息格式,压缩编码技术。最后指出当前各主要手机生产...
此函数为修改的开源的libmms包,能够实现mms流媒体协议下载。希望能给大家的编程带来用处!
mms源码
使用排队论解决食堂排队问题的模拟,利用了MMS和MM1模型求得平均队长,和平均等待时间
android mms
MMS电台合集