- 浏览: 175818 次
- 性别:
- 来自: 成都
文章分类
最新评论
-
行动与思考:
你好!请问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
-- Module ACSE-1 (X.227:04/1995)
-- See also the README file
-- See also the index of all ASN.1 assignments needed in this document
ACSE-1 {joint-iso-itu-t association-control(2) modules(0) apdus(0) version1(1)}
-- ACSE-1 refers to ACSE version 1
DEFINITIONS ::=
BEGIN
EXPORTS
acse-as-id, ACSE-apdu, aCSE-id, Application-context-name, AP-title,
AE-qualifier, AE-title, AP-invocation-identifier, AE-invocation-identifier,
Mechanism-name, Authentication-value, ACSE-requirements, ObjectSet;
IMPORTS
Name, RelativeDistinguishedName
FROM InformationFramework {joint-iso-itu-t ds(5) module(1)
informationFramework(1) 3};
-- The data types Name and RelativeDistinguishedName are imported from ISO/IEC 9594-2.
-- object identifier assignments
acse-as-id OBJECT IDENTIFIER ::=
{joint-iso-itu-t association-control(2) abstract-syntax(1) apdus(0)
version1(1)}
-- may be used to reference the abstract syntax of the ACSE APDUs
aCSE-id OBJECT IDENTIFIER ::=
{joint-iso-itu-t association-control(2) ase-id(3) acse-ase(1) version(1)}
-- may be used to identify the Association Control ASE.
-- top level CHOICE
ACSE-apdu ::= CHOICE {
aarq AARQ-apdu,
aare AARE-apdu,
rlrq RLRQ-apdu,
rlre RLRE-apdu,
abrt ABRT-apdu,
...
}
AARQ-apdu ::= [APPLICATION 0] IMPLICIT SEQUENCE {
protocol-version
[0] IMPLICIT BIT STRING {version1(0)} DEFAULT {version1},
application-context-name [1] Application-context-name,
called-AP-title [2] AP-title OPTIONAL,
called-AE-qualifier [3] AE-qualifier OPTIONAL,
called-AP-invocation-identifier [4] AP-invocation-identifier OPTIONAL,
called-AE-invocation-identifier [5] AE-invocation-identifier OPTIONAL,
calling-AP-title [6] AP-title OPTIONAL,
calling-AE-qualifier [7] AE-qualifier OPTIONAL,
calling-AP-invocation-identifier [8] AP-invocation-identifier OPTIONAL,
calling-AE-invocation-identifier [9] AE-invocation-identifier OPTIONAL,
-- The following field shall not be present if only the Kernel is used.
sender-acse-requirements [10] IMPLICIT ACSE-requirements OPTIONAL,
-- The following field shall only be present if the Authentication functional unit is selected.
mechanism-name [11] IMPLICIT Mechanism-name OPTIONAL,
-- The following field shall only be present if the Authentication functional unit is selected.
calling-authentication-value [12] EXPLICIT Authentication-value OPTIONAL,
application-context-name-list
[13] IMPLICIT Application-context-name-list OPTIONAL,
-- The above field shall only be present if the Application Context Negotiation functional unit is selected
implementation-information [29] IMPLICIT Implementation-data OPTIONAL,
...,
...,
user-information
[30] IMPLICIT Association-information OPTIONAL
}
AARE-apdu ::= [APPLICATION 1] IMPLICIT SEQUENCE {
protocol-version
[0] IMPLICIT BIT STRING {version1(0)} DEFAULT {version1},
application-context-name [1] Application-context-name,
result [2] Associate-result,
result-source-diagnostic [3] Associate-source-diagnostic,
responding-AP-title [4] AP-title OPTIONAL,
responding-AE-qualifier [5] AE-qualifier OPTIONAL,
responding-AP-invocation-identifier [6] AP-invocation-identifier OPTIONAL,
responding-AE-invocation-identifier [7] AE-invocation-identifier OPTIONAL,
-- The following field shall not be present if only the Kernel is used.
responder-acse-requirements [8] IMPLICIT ACSE-requirements OPTIONAL,
-- The following field shall only be present if the Authentication functional unit is selected.
mechanism-name [9] IMPLICIT Mechanism-name OPTIONAL,
-- This following field shall only be present if the Authentication functional unit is selected.
responding-authentication-value
[10] EXPLICIT Authentication-value OPTIONAL,
application-context-name-list
[11] IMPLICIT Application-context-name-list OPTIONAL,
-- The above field shall only be present if the Application Context Negotiation functional unit is selected
implementation-information
[29] IMPLICIT Implementation-data OPTIONAL,
...,
...,
user-information
[30] IMPLICIT Association-information OPTIONAL
}
RLRQ-apdu ::= [APPLICATION 2] IMPLICIT SEQUENCE {
reason [0] IMPLICIT Release-request-reason OPTIONAL,
...,
...,
user-information [30] IMPLICIT Association-information OPTIONAL
}
RLRE-apdu ::= [APPLICATION 3] IMPLICIT SEQUENCE {
reason [0] IMPLICIT Release-response-reason OPTIONAL,
...,
...,
user-information [30] IMPLICIT Association-information OPTIONAL
}
ABRT-apdu ::= [APPLICATION 4] IMPLICIT SEQUENCE {
abort-source [0] IMPLICIT ABRT-source,
abort-diagnostic [1] IMPLICIT ABRT-diagnostic OPTIONAL,
-- This field shall not be present if only the Kernel is used.
...,
...,
user-information [30] IMPLICIT Association-information OPTIONAL
}
ABRT-diagnostic ::= ENUMERATED {
no-reason-given(1), protocol-error(2),
authentication-mechanism-name-not-recognized(3),
authentication-mechanism-name-required(4), authentication-failure(5),
authentication-required(6), ...
}
ABRT-source ::= INTEGER {acse-service-user(0), acse-service-provider(1)
}(0..1, ...)
ACSE-requirements ::= BIT STRING {
authentication(0), application-context-negotiation(1)}
Application-context-name-list ::= SEQUENCE OF Application-context-name
Application-context-name ::= OBJECT IDENTIFIER
-- Application-entity title productions follow (not in alphabetical order)
AP-title ::= CHOICE {
ap-title-form1 AP-title-form1,
ap-title-form2 AP-title-form2,
...
}
AE-qualifier ::= CHOICE {
ae-qualifier-form1 AE-qualifier-form1,
ae-qualifier-form2 AE-qualifier-form2,
...
}
-- When both AP-title and AE-qualifier data values are present in an AARQ or AARE APDU, both must
-- have the same form to allow the construction of an AE-title as discussed in CCITT Rec. X.665 |
-- ISO/IEC 9834-6.
AP-title-form1 ::=
Name
-- The value assigned to AP-title-form1 is The Directory Name of an application-process title.
AE-qualifier-form1 ::=
RelativeDistinguishedName
-- The value assigned to AE-qualifier-form1 is the relative distinguished name of a particular
-- application-entity of the application-process identified by AP-title-form1.
AP-title-form2 ::= OBJECT IDENTIFIER
AE-qualifier-form2 ::= INTEGER
AE-title ::= CHOICE {
ae-title-form1 AE-title-form1,
ae-title-form2 AE-title-form2,
...
}
-- As defined in CCITT Rec. X.650 | ISO 7498-3, an application-entity title is composed of an application-
-- process title and an application-entity qualifier. The ACSE protocol provides for the transfer of an
-- application-entity title value by the transfer of its component values. However, the following data type
-- is provided for International Standards that reference a single syntactic structure for AE titles.
AE-title-form1 ::=
Name
-- For access to The Directory (ITU-T Rec. X.500-Series | ISO/IEC 9594), an AE title has AE-title-form1.
-- This value can be constructed from AP-title-form1 and AE-qualifier-form1 values contained in an
-- AARQ or AARE APDU. A discussion of forming an AE-title-form1 from AP-title-form1 and AE-qualifier-
-- form1 may be found in CCITT Rec. X.665 | ISO/IEC 9834-6.
AE-title-form2 ::= OBJECT IDENTIFIER
-- A discussion of forming an AE-title-form2 from AP-title-form2 and AE-qualifier-form2 may be
-- found in CCITT Rec. X.665 | ISO/IEC 9834-6.
AE-invocation-identifier ::= INTEGER
AP-invocation-identifier ::= INTEGER
-- End of Application-entity title productions
Associate-result ::= INTEGER {
accepted(0), rejected-permanent(1), rejected-transient(2)}(0..2, ...)
Associate-source-diagnostic ::= CHOICE {
acse-service-user
[1] INTEGER {null(0), no-reason-given(1),
application-context-name-not-supported(2),
calling-AP-title-not-recognized(3),
calling-AP-invocation-identifier-not-recognized(4),
calling-AE-qualifier-not-recognized(5),
calling-AE-invocation-identifier-not-recognized(6),
called-AP-title-not-recognized(7),
called-AP-invocation-identifier-not-recognized(8),
called-AE-qualifier-not-recognized(9),
called-AE-invocation-identifier-not-recognized(10),
authentication-mechanism-name-not-recognized(11),
authentication-mechanism-name-required(12),
authentication-failure(13), authentication-required(14)}
(0..14, ...),
acse-service-provider
[2] INTEGER {null(0), no-reason-given(1), no-common-acse-version(2)}
(0..2, ...)
}
Association-information ::= SEQUENCE SIZE (1, ..., 0 | 2..MAX) OF EXTERNAL
Authentication-value ::= CHOICE {
charstring [0] IMPLICIT GraphicString,
bitstring [1] IMPLICIT BIT STRING,
external [2] IMPLICIT EXTERNAL,
other
[3] IMPLICIT SEQUENCE {other-mechanism-name
MECHANISM-NAME.&id({ObjectSet}),
other-mechanism-value
MECHANISM-NAME.&Type
({ObjectSet}{@.other-mechanism-name})}
}
-- The abstract syntax of (calling/responding) authentication-value is determined by the authentication
-- mechanism used during association establishment. The authentication mechanism is either explicitly
-- denoted by the &id field (of type OBJECT IDENTIFIER) for a mechanism belonging to the class
-- MECHANISM-NAME, or it is known implicitly by
-- prior agreement between the communicating partners. If the "other" component is chosen, then
-- the "mechanism-name" component must be present in accordance with
-- ITU-T Rec. X.680 | ISO/IEC 8824. If the value "mechanism-name" occurs in the AARQ-apdu or the
-- AARE-apdu, then that value must be the same as the value for "other-mechanism-name"
Implementation-data ::= GraphicString
Mechanism-name ::= OBJECT IDENTIFIER
MECHANISM-NAME ::= TYPE-IDENTIFIER
ObjectSet MECHANISM-NAME ::=
{...}
Release-request-reason ::= INTEGER {normal(0), urgent(1), user-defined(30)
}(0 | 1 | 30, ...)
Release-response-reason ::= INTEGER {
normal(0), not-finished(1), user-defined(30)}(0 | 1 | 30, ...)
END
发表评论
-
IEC60870-5-104集锦
2009-05-12 20:00 3218=============================== ... -
基于TCP/IP的IEC60870-5-104远动规约在电力系统中的应用
2009-05-12 15:45 2355摘 要 : ... -
基于TCP/IP的IEC60870-5-104远动通信协议
2009-05-12 15:36 4389介绍了国际电工委员会制定的基于TCP/IP网 络的调度主站和 ... -
Capture file header format
2009-04-21 16:44 1488截获包的文件头格式 (比如:wireshark, e ... -
TCP Socket类型
2009-04-20 20:19 1828对于许多初学者来说, ... -
ASN.1 of MMS related Protocol, totally 8 files
2009-04-17 12:56 1340Download Link: http://xu ... -
MMS related Protocol structure & frame format
2009-04-14 12:19 4402Get from http://wiki.wireshark. ... -
MMS报文分析示例(三)
2009-04-14 10:43 3162Variable Management 1. ... -
MMS报文分析示例(二)
2009-04-14 10:39 3547VMD Management 1. Ident ... -
Triangle MicroWorks, Inc
2009-04-14 02:13 1504发现Triangle MicroWorks, Inc公司不愧为 ... -
ASN.1 -- MMS --ICCP ( TABSE2)
2009-04-14 02:04 2149MMS的ASN.1规定( 8825-1 BER 8825-2 ... -
MMS Syntax (ISO 9506-2:1999)
2009-04-13 13:27 1731Updated and fixed on 2006-08-11 ... -
MMS报文分析示例(一)
2009-04-13 12:08 3185Context Management 1. ... -
MMS abstract syntax (sisco)
2009-04-13 10:39 2308Get from http://www.sisconet. ... -
MMS->OSI MODEL
2009-04-12 22:36 1405Kema UniCA analyzer Provid ... -
MMS笔记(一)
2009-04-12 22:23 1870=============================== ... -
asn.1的ber编码
2009-04-12 22:06 4160ASN.1即抽象语法符号,用来定义应用程序数据和表示[wi ... -
MMS编码
2009-04-12 22:03 2386Telecontrol Application Service ... -
WireShark Lua Example
2009-04-11 16:42 2871From: http://wiki.wireshark.org ... -
使用lua编写Wireshark的dissector插件
2009-04-11 16:33 5729Dissector 插件可以用来对特定的协议内容进行分析展示 ...
相关推荐
environment_acse1 ACSE-1环境示例存储库
基于SOAP的Web服务的示例项目 这些简单的项目显示了最少的功能集。 运行SOAP项目 要运行SOAP项目,请执行以下操作。 将此存储库克隆到一个临时文件夹。 按照中的描述导入项目。 将SoapService项目发布到应用程序...
降雨数据处理 在此存储库中,我们使用了Pandas和Docker...为了能够运行此工具,您需要将其克隆到计算机中git clone https://github.com/acse-2020/acse-1-assessment-2-acse-va220.git 该工具仅在Python 3.0上构建,因
ACSE_Recordings ACSE20的录制链接 ACSE6 L14(MPI L8)-26 / Feb (课程介绍) ACSE6 L13(MPI L7)-25 / Feb (并行通信体系结构和并行性能) ACSE6 L12(MPI L6)-24 / Feb (并行分解) ACSE6 L11(MPI ...
Hill代码acse-5-assignment-nan 小组成员 Sokratis Anagnostopoulos 朱林高娜 浩路 BLAS先决条件 OpenBLAS 为了确保它可以编译,需要首先导出已安装的OpenBLAS的路径(以下是macOS中使用的示例) brew install ...
standards (e.g., Presentation, ASN.1, and ACSE). Besides not being a self-contained standard, the division of protocol specification and encoding represents a different philosophy from many of the ...
ci_acse1 虚拟课堂回购CI讲座
再谈电气火灾监控系统(ACSE)的设置.doc
再谈电气火灾监控系统(ACSE)的设置.doc
亚信 安全 TDA综合试题 ACSE考试,试题,含答案含答案.zip
TD-LTE培训试题(含答案),用于LTE水平测试。
2020年accss亚信云安全专家华三版本2019,本人亲测,一次通过。
亚信面试笔试纸质试题扫描件,PDF文档。内容包括智力题、基础题。
通信工程师最新大纲定制课程,根据教材每个章节讲解资料,让你在快速掌握新大纲的重点考点。帮助你通过考试。 适合人群:期望在最短的时间内通过中级通信工程师考试的行业从业人员;通信工程师备考人员
ACSE 4.4-机器学习小型项目 识别游戏 此处提供所有信息: : 该项目旨在将具有3个RGB通道的64 * 64图片分类为200个类别。 当提供10000张未标记的图片作为测试数据时,提供了100000张带有标签的训练图片。 尝试在...
亚信 安全 TDA综合试题 ACSE考试,试题,含答案含答案
开放式色彩转换器 生成状态: 用于将调色板信息转换为开放颜色格式的脚本。 阿科 第一个示例演示了将Material Palette.aco转换为oco文件的过程。 较少的 萨斯 CSS JSON格式 Swift ... 制作命令行工具
为了估计稀疏MIMO信道,将稀疏不变步长归一化最小均方(ISS-NLMS)算法应用于自适应稀疏信道估计(ACSE)。 众所周知,步长是控制三个方面的关键参数:算法稳定性,估计性能和计算成本。 但是,传统方法很容易造成...
1. Scope and Field of Application ............................................................................................................................. 35 2. Normative References ................