The Abstract Syntax Notation One (ASN.1) is a specification language to the definition of data structures as well as definitions to the conversion of data structures and elements into a net-uniform format. It is common standard of the ITU-T (international Telecommunication union - Telecommunication Standardization second gate) and the ISO (International Organization for Standardization).
The standard serves the abstract description of data types, without dealing with the computer-internal representation. The notation is defined in the International Telecommunication Union T standards X.680ff. The associated standards X.690ff define different Encoding Rules like the ASN.1-Datenwerte on bit level to be coded. By ASN.1 and a common Encoding Rule can systems with different internal data presentations messages exchange.
ASN.1 is a possible and common possibility, to describe which message elements of minutes of the OSI model clearly and by OSI conformal technologies such as X.500 and X.509, in addition, used by Internet minutes such as SNMP. Broad application finds ASN.1 also in the telecommunications, e.g. with the standards GSM for the account of in TAP3-Dateien and UMTS.
Usually in ASN.1 specified data with that basic Encoding Rules (BER), which can be handled simply, are coded. Within ranges, with which a space-saving coding is desired (for example portable radio), becomes the Packed Encoding Rules (BY) preferentially. Further the injektiven Canonical Encoding Rules (CERIUM) and Distinguished Encoding Rules () exists, whereby the latters are common further. The Distinguished Encoding Rules is a subset of the BER (basic Encoding Rules) and is a coding of ASN.1-Datenbeschreibungen, which is completely clear on bit level. There is in thus in contrast to the BER for each ASN.1-Wert only a possible coding. Thus they are suitable for cases, in which ASN.1-Daten digitally to be marked to have and/or platform-spreading to be exchanged be supposed, for example in digital certificates (see X.509).
ASN.1 is described BNF similar representation in an easily understandable, e.g.:
Record:: = SEQUENCE {head header, data DATA OPTIONAL} headers:: = IA5String DATA:: = SET OF INTEGER
In the next example a module is agreed upon. Possible this module is to be found also by means of a Object Identifier. Happening by one the module a Object Reference puts on, e.g.:
Module name {1} DEFINITION:: = BEGIN {data structure:: = SEQUENCE {part to INTEGER, fragment IA5String}} END
Before the term DEFINITION by means of the swung clips a Objektrefernz is as evident in this example, an ID is thus put on. The object reference refers the correct object in a tree of references and/or agreements to find. The ID from this example refers to the first root in the first level of the chaining structure modules, thus a module like it above agreed upon is, is necessarily around an agreement to be met like data to be transferred is. Data like the example shows to be defined, are as follows transferred: {2, "Teil2"}.
ASN.1 knows in addition
We found here 6 articles.
A» A choice knot» Abstract Syntax Notation One » Adaptive Routing » Air Gap » Arbitrator algorithm » Asynchronous Transfer Mode |
We found here 4 related websites.
Index | Privacy | Terms Of Use | Sitemap | Feedback