Method for transferring information

Translation of description of equivalent WO 9849806 A2

p0001Method for transmission of information

p0002The invention relates to a method for transmitting information, the structure by using Abstract Syntax Notation One (ASN.l) Marked formal language for defining data structures defined.

p0003Reference is made to the following literature:

p0004[NMFTR107] Network Management Forum

p0005Forum Tr107: ISO / CCITT and Internet Management: Coexistence and Interworking Strategy Issue 1.0 September 1992

p0006[M.3010] ITU-T Recommendation M.3010

p0007Maintenance: Telecommunications Management

p0008Network

p0009Principles for a Telecommunications Management

p0010Network 10/92

p0011[X.160] ITU-T Recommendation X.160

p0012Data Networks and Open System Communications Public Data Networks - Maintenance Architecture for Customer Network Management Service for Public Data Networks 7/94 [X.200] Data Networks and Open System Communications Open System Interconnection - Model and Notation Information Technology - Open Systems Interconnection Basic Reference Model Geneva, 1994

p0013[X.208] ITU-T Recommendation X.208

p0014Specification of abstract syntax notation one

(ASN.1)

p0016information technology

p0017Open System Interconnection 1988

p0018[X.209] ITU-T Recommendation X.209

p0019Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)

p0020[X.710] ITU-T Recommendation X.710 Data Communication Networks Open Systems Interconnection

p0021Common Management Information Service Definition for CCITT Applications Geneva, 1991

p0022[X.711] ITU-T Recommendation X.711 Data Communication Networks Open Systems Interconnection Common Management Information Protocol Specification for CCITT Applications Geneva, 1991

p0023[X.722] ITU-T Recommendation X.722 Data Communication Networks Open Systems Interconnection Structure of Management Information Guidelines for the Definition of Managed Objects Geneva 1992

p0024[RFC1157] Network Working Group RFC 1157

p0025Simple Network Management Protocol (SNMP)

p0026[RFC1085] Network Working Group RFC 1085

p0027ISO Presentation Services on top of TCP / lP-based internets

p0028M. Rose, Performance Systems International

p0029K. McCloghrie, Hughes LAN Systems

p0030December 1988

p0031[RFC1189] Network Working Group RFC 1189

p0032Common Management Information Services and

p0033Protocols for the Internet (CMOT and CMIP).

p0034US Warrier, L. Besaw, L. LaBarre, BD

p0035Hand Picker. historic protocol, not recommended status

p0036Oct-01-1990.

p0037[RFC1214] Network Working Group RFC 1214

p0038OSI Internet Management: Management Information

p0039base

p0040L. Labarre historic protocol, not recommended status

p0041April 1991

p0042[RFC0793] Network Working Group RFC 0793 Transmission Control Protocol J. Postel. September 1981

p0043OSI Abstract Data Manipulation API (XOM)

p0044CAE Specification

p0045Issue 3 x / Open Company Ltd. ISBN 1 85912 175 6

p0046Furthermore, the following abbreviations are used:

p0047ASN.1 Abstract Syntax Notation One [X.208]

p0048BER Basic Encoding Rules [X.209]

p0049CMIP Common Management Information Protocol [X.711] CMIPDU Common Management Information Protocol Data Unit

p0050[X.711] CMIS Common Management Information Service [X.710] CNM Customer Network Management [X.160]

p0051DCF Data Communication Function DCN Data Communication Network GDMO Guidelines for the Definition of Managed Objects

p0052[X.722] OSI Open System Interconnection [X.200]

p0053SNMP Simple Network Management Protocol [RFC1157]

p0054TCP / IP Transmission Control Protocol / Internet Protocol

p0055[RFC0793] TMN Telecommunication Management Network [M.3010] XOM X-OPEN, interface for handling ASN.1

p0056The Abstract Syntax Notation One (Abstract Syntax Notation 1 (ASN.1) [X.208] is used for formal specification of data types. It is inter alia for platform-independent definition of different services and protocols of the OSI 7-layer model (Open System Interconnection [ X.200]) used. Thus, the stored information, the structure of which is defined by ASN.1, can be transmitted, there are a number of methods, such as the Basic encoding Rules (BER) [X.209], for encoding ASN.1 values. the BER-encoded information can then be transmitted in binary form by any method. In general, this transmission protocols from the TCP / IP or OSI family are used. Currently the transfer of various Protocol defined in ASN.1 Data Units (PDU) of the layer 7 of the OSI 7-layer model is considered by means of a pure OSI based protocol stacks to be very expensive. For this reason, is often dispensed either on the use of these protocols, or the lower layers of the OSI protocol stack are replaced by an established TCP / IP protocol. CMIP over TCP / lP As an example, for a number of these methods therefor (CMOT) [RFC1189] mentioned.

p0057Object of the invention is to avoid these disadvantages in the binary transmission of information, the structure of which is defined by ASN.1.

p0058The object is achieved in that the transmission takes place in a text encoded form. It is preferably provided that a clear text encoding is performed, in which the encoded content is readable without aids.

p0059The advantages of the process according to the invention is based essentially on the fact that text-based

p0060Transmission protocols usually very widespread and are therefore correspondingly cheaper than binary transfer method. Additionally, debugging is much easier to implement in plain text encoding, so that the implementation costs for a specific application be significantly lower. The advantages are as follows:

p0061- The spread of text-based communication protocols, such as email, the number of computers that can be achieved with this protocol, significantly larger than the case of binary transmission method.

p0062- So-called firewalls for distinguishing between a company's internal network are often only for text-based Transmission protocols open.

p0063- For troubleshooting in the encoded ASN.1 -Information no additional tools are needed, because the encoding is not available in human readable form.

p0064- By using very simple protocols are provided no major specific needs! To the time required for encoding and transmission processing power, resulting in simple PCs for this purpose are.

p0065- Sending and receiving devices need to include any complex protocol stack. The software required for text-based transmission method is in many operating systems already exist.

p0066In contrast to the BER encoding, it is possible in the inventive method to decode the received data, without requiring access to a apllikationsinterne reference ASN.1 definition.

p0067A particularly advantageous development of the method is that for each of information to be transmitted, the name of each defined by ASN.1 data type is transmitted, which is preferably provided by a predetermined separator, in particular an equal sign, of preceded by the name and the information is separated.

p0068This development, a particularly advantageous for the user handling of the process is made possible in that the encoded as textual information using a standard file output device is displayed. Likewise, an input by the user as well as a permanent storage is possible as text coded information in a simple manner. The protocol for the management of public telecommunications networks - referred to hereinafter as networks - will be used in future mainly CMIP [X.711]. Telecommunications networks may be networks for voice, data and image transmission in this context. The structure of the CMIPDU has been formally defined using ASN.1. The transmitted via CMIPDUs management information is coded according to the Basic Encoding Rules. Especially at long distances or due to high quality requirements can based on the benefits of the OSI protocol stack for transmitting the CMIP management information not be waived. But there are also applications for which a much simpler and more cost-effective solution for the transmission of management information is sufficient. technically simpler TCP / lP a currently practiced way - In addition to the implementation of CMIP to the widespread in local networks SNMP is also the transfer of CMIP over the - over the OSI protocols of the lower protocol layers.

p0069In another development of the inventive method is therefore provided that the means of CMIP to the transmitted information relating to the management of public telecommunications networks. In this development, it is ultimately irrelevant whether the purpose plain text encoding used is based on the fact that the CMIP has been defined in ASN.1, or whether the text-based coding rules were created, regardless of this fact.

p0070Besides those already enumerated advantages of the inventive method is through this training, namely the textual transmission of the CMIP, possible to use the CMIP also where the costly transmission over an OSI protocol stack for cost reasons is not reasonable. Public network operators are facing in the future to its customers a management interface available via which customers can management operations relating to the part of the of them rented public network cause. then can be transferred via this interface all the data that want to exchange the customer with the network operator.

p0071An example of this is to request a dedicated line between location A and B of a customer's own network. Both locations are to be interconnected via the public network. For this purpose, it is provided in another development of the inventive method that the information between a subscriber and a public network or its management systems are transmitted and address a to be implemented by the subscriber management of the network.

p0072The invention can be particularly configured such that an email interface for text-coded information is formed. This development Customers are offered a low-cost, yet reliable interface to the network operator. It must not be dispensed with the advantages of CMIP as management protocol.

p0073Such an interface between customer-own management system and the management system of the network operator, it is the customer allows to perform management operations not only on its local network is limited, but also involve the used of him part of the public network. This is known as Customer Network Management. A typical application for this is for instance in the customized configuration of the network. Furthermore, the immediate Log belong detected error to the customer and the available position certain statistical data on the topic of the CNM.

p0074A further embodiment of the invention is that a simple and flexible adaptation to the limited character set of the transmission system is possible through the use of character tables for encoding and decoding of the information. For example, when a transmission protocol is not capable of the "{" - and "}" to transmit characters, so another characteristic sign can be used instead without the encoding rules must be fundamentally changed. The parallel use of different character maps, it is possible without additional technical effort to support multiple transmission media with different character sets within an application.

p0075Another development of the method is that the coding and sending the management information as well as receiving and decoding done the same automatically.

p0076In the area of ​​the network provider at any time an automatic conversion of text-based transmission on an OSI protocol stack is then possible. Advantage of this architecture is that not every customer needs to administer its own OSI stack, but that the operators offering the service center for all customers.

p0077Embodiments of the invention are shown in the drawing using several figures and explained in more detail in the following description. It shows:

p0078Fig. 1 shows a first embodiment of a device for performing the method according to the invention, Fig. 2 shows a second embodiment, also as a block diagram,

p0079Fig. 3 is a schematic illustration of the management of a used portion by a subscriber of a public telecommunication network, and

p0080Fig. 4 is a schematic representation of a text-based transmission CMIP-based management information between CNM and network operator.

p0081In the embodiment of FIG. 1 two management systems 1 and 2 to the exchange of information on a text-based transmission system 3 are interconnected. The payload to be transmitted, within the transmitting and receiving application 4, 5 present in the management systems 1, 2 in different proprietary data formats. The structure of these data formats is determined by the tools that are used in the preparation of applications. At 6, 7, this useful information is encoded and decoded according to ASN.1 and addition process of the invention.

p0082Fig. Figure 2 shows a possible implementation of the architecture shown in FIG. 1. From present in a first management system 11 at 13 C data structures information is transmitted to the management system 12, where she worked as C / C ++ - are stored data types at 18th

p0083The present case 13 First, information is fed to a XOM interface 14 and there encoded as XOM objects, so they must be handled in accordance with ASN.1. These objects are then converted by the inventive process in text-based communication protocols, which are transmitted as someone 19 and received by the management system 12th There they are first decoded at 16 and in Objects and then converted at 18 as C / C ++ - - ++ stored C data types.

p0084Fig. 3 shows a scenario in which a customer request to the public network operators, two sites A, B to be connected to a dedicated line. The customer uses this on its management system 21 at site A a corresponding request 24 to the management system 22 of the network operator from N. This checks the request for feasibility in its own network and then outputs it to the management system 23 at location B of customers (25). Once from there the message 26 arrives that the associated part of the leased line was successfully established, the associated through-connection in the public network is created and the result is "established line" Site A notified (27).

p0085Fig. 4 illustrates the textual transmission CMIP-based management information between a CNM-customer and the network operator. The management system 21 at location A and the management system 23 at location B of the customers are a CNM interface 36, 37, are transmitted via the respective process of the invention clear text-coded information to the management system 22 of the network operator N on each.

p0086The management systems 21, 23 of the customers have access to the network elements 34, 35 of each customer. This takes place for example at location A using CMIP over TCP / lP, while using the Site B SNMP. The management system 22 of the network operator N, whose domain is indicated in Fig. 4 by the dashed lines, has access to the network elements 31 to 33 of the public network. This is done with CMIP via a 7-layer OSI protocol stack. The network operator N offers customers a CNM service, which the customer can use their own or provided by the network operator management application to forward its management requirements to the management system 22 of the public network. The information to be transmitted management information is at the customer within its management application automatically clear text-encoded and transmitted via a text-based protocol to the management system 22 of the network operator. Either this message is automatically received by the management system 22 of the network operator or CNM services provider and further processed or there is a reaction to an OSI protocol stack and an OSI-based transmission to the management system of the network operator in 36 and 37 instead.

p0087Also the transmission of management information to the management systems 21, 23 of the customers can be carried out advantageously with the inventive method. This will automatically be coded in text form message to the customer by the network operator N. The CNM of customer management application receives and decodes this text message automatically to route the transmitted management information.

p0088The invention ASN.1 encoding is performed according to a fixed procedure. For each ASN.1 types of the day in the form of a speaking style similar to the ASN.1 norm name (eg "INTEGER" for the Universal Day 2) is basically coded first, then a "=" - character inserted as a separator. Subsequently, the value in the manner established for this type is encoded. If an ASN.1 data type is in turn composed of other data types, the tags and values ​​of the data types contained encoded in its value-coding. There are two variants for Codierrregeln defined, both of which are the subject of this claim. The standard version is enough to encode the ASN.1 version from perfect and is correspondingly easy to implement. In the extended version of the code text is supplemented with additional information that is taken from the ASN.1 -Typendefinition. This troubleshooting is both compared to the standard version of the plain text encoding as well as to the binary-coded form much easier. However, the use of more advanced solution increases the implementation complexity in application development. Therefore, it is also permissible to use only individual parts of the extended encoding, if this is done consistently in the transmitter and receiver. As far as the extended encodable is provided for the coding of a specific data type, this is explained in the following for the associated data types.

p0089The following sections describe the associated ASN.1 definition and one or more examples of the encoding are given together with the description of the encoding rules for each data type.

BOOLEAN

p0091The coding is done of a Boolean data type, by the type of the text "BOOLEAN", and for the value of either the lyrics "TRUEj." or "FALSE #" are coded:

p0092ASN.1 definition encoding (more examples) Bol:: = BOOLEAN BOOLEAN = TRUE #

p0093BOOLEAN = FALSE #

INTEGER

p0095An integer value is indicated by the text "INTEGER" and encodes the associated value in the format of a decimal number. Here are just negative numbers with a sign to provide. The encoding of the value is a "^" - ended character.

p0096ASN.1 definition encoding (more examples) Int:: = INTEGER INTEGER = 123 #

p0097INTEGER = -123 #

BIT STRING

p0099A bit string encoded by the text "BIT STRING". The value encoding is performed by a binary list that starts with "{}" - included characters and by the prefix "B" for binary and the number of encoded elements is marked. A hexadecimal coding instead of the binary coding will be marked in a "H". If the number of bits is not an integral multiple of four, the low-order bits are undefined (these are the right) with the binary value to be coded "0". Both in the binary and in the hexadecimal encoding is according to the ASN.1 definition possible to dispense with the coding elements standing at the end, when they are coded with the value "0".

p0100In the extended coding, the identifier of the elements to be enumerated, the binary value of "1". Here the beginning of the list by the "{" sign and the end with the "}" character is marked. As the separator, within this list is a "/" - used characters.

p0101ASN.1 definition encoding (several versions)

p0102Bitstr :: = BIT STRING {BIT STRING = B5 {01100} ele (0), BIT STRING = B3 {011} ele (1), BIT STRING = H2 {70} ele (2), BIT STRING = H1 {7} ele (3), ele (4)} Advanced Coding:

p0103BIT STRING = {ele (1) / ele (2)} BIT STRING = B5 {00000} BIT STRING = B1 {0} BIT STRING = H1 {0}

p0104Advanced encoding: BIT STRING = {}

OCTET STRING

p0106An octet string is encoded by the text "OCTET STRING". The value encoding is performed by a binary list that starts with "{}" - is enclosed characters and by the prefix "B" for binary and the number of encoded elements is marked. Optionally, also a hexadecimal encoding are used, which is in accordance with an "H". As separator between each octet values ​​is a "/" - character.

p0107ASN.1 definition encoding

p0108OctStr :: = OCTET STRING OCTET STRING = B2 {11100001 /

p010911111111} OCTET STRING = H2 {E1 / FF}

ZERO

p0111The encoding of the ASN.1 data type zero by the

p0112Text "NULL = NULL #".

p0113ASN.1 definition encoding

p0114Zero = NULL NULL = NULL #

OBJECT IDENTIFIER

p0116The ASN.1 data type Object Identifier is encoded by the text "OBJECT IDENTIFIER". The value is preceded by at coding the text "NUMERIC" by listing the serial numbers of nodes in Registration tree coded starting from the root element to the registered member. Separately, the numerical values ​​of this listing are by periods. The encoding of the value is a "^" - ended character.

p0117With advanced coding indicated by the text "Symbolic" a unique mnemonic identifier is used instead of the not very meaningful number sequence. Of course, a unique bijective tabular association between Bezeicher and Object Identifier must be created. A combination of mnemonic identifiers and sequence of digits is not allowed. The encoding of the value is terminated by a "" "mark.

p0118ASN.1 definition encoding

p0119Obj :: = OBJECT IDENTIFIER OBJECT IDENTIFIER = Numeric,

p01201.2.2.1.4 #

p0121Advanced coding OBJECT IDENTIFIER = Symbθlic, systemld #

EXTERNAL

p0123The date of data type External encoded by the text "EXTERNAL". The value encoding this data type is derived from the encoding rules for the following SEQUENCE:

SEQUENCE

p0125{Direct-reference OBJECT IDENTIFIER OPTIONAL, indirect-reference INTEGER OPTIONAL, data-value-descriptor ObjectDescriptor OPTIONAL, encoding CHOICE

p0126{Single-ASN1-type [0] IMPLICIT ANY, octet-aligned [1] IMPLICIT OCTET STRING, arbitrary [2] IMPLICIT BIT STRING

REAL

p0128Numbers in real format are encoded in scientific notation. The encoding of the value is a "^" - ended character.

p0129ASN.1 definition encoding Real:: = REAL REAL = 1.23E45 #

ENUMERATED

p0131The day a Enumerated type is encoded by the text "ENUMERATED". The value coding is done by specifying the page associated with the element integer. The encoding of the value is terminated by a "" "mark. With advanced encoding the item is coded identically to its definition text.

p0132ASN.1 definition encoding Enum:: = {ENUMERATED ENUMERATED = 1 # a (0), b (1), Advanced Encryption: c (2)} ENUMERATED = b (1) #

SEQUENCE

p0134The day of a sequence encoded by the text "SEQUENCE". The coding of the value of a Sequence starts with the number of coded elements followed by a

p0135"{" Character and ends with a "}" character. In the further specification of the value must lie between two coding

p0136Types of Sequence can be distinguished:

p0137In simple Sequence ASN.1 types contained in the sequence are in order of appearance encoded in the definition. For this, the item numbers are preceded by separated with a comma. As separator between these types is each a "/" - inserted characters. Unused optional elements of the sequence are simply omitted in coding, so that then also the "/" in this case - is not coded character as a separator.

p0138ASN.1 definition encoding (more examples) Seq:: = SEQUENCE {SEQUENCE = 2 {1, INTEGER = 123 # /

p01393, INTEGER = 456 #} a INTEGER, SEQUENCE 3 = {1, INTEGER = 1 # / 2,

p0140BOOLEAN = FALSE # / 3,

p0141INTEGER = 3} # b BOOLEAN OPTIONAL, c INTEGER}

p0142The value of a sequence of defined by the included data type often preceded by item number and by a "/" accordingly - character is encoded separately from each other.

p0143AS .1 definition encoding (more examples)

p0144Seq:: = SEQUENCE OF INTEGER SEQUENCE OF = 3 {1, INTEGER = 1 # / 2, INTEGER = 2 # / 3, INTEGER = 3 #}

p0145SEQUENCE = 0 {}

SET

p0147The day of the type set is encoded by the text "SET". The

p0148Coding of the value begins with the number of coded

p0149Elements followed by a "{" - character and ends with a

p0150"}"-Character. In the further specification of the

p0151Value coding is necessary to distinguish between two types of set data type:

p0152In the simple set-type in the definition are contained ASN.1 types in the order they appear in the definition encoding. For this, the item numbers are preceded by separated with a comma. As separator between these types is each a "/" - inserted characters. Unused optional elements of the set are simply omitted in coding, so that in this case the "/" - will mark not coded as a separator.

p0153ASN.1 definition encoding (more examples)

p0154Set:: = SET {SET = 2 {1, INTEGER = 123 # / 2, BOOLEAN = TRUE #} a INTEGER, b BOOLEAN, c optional OBJECT IDENTIFIER}

p0155The value for the type of set is defined by the included data type often preceded by item number and by a "/" accordingly - character is encoded separately from each other.

p0156ASN.1 definition encoding (more examples) Set :: = SET OF INTEGER SET = 3 {1, INTEGER = 1 # / 2, INTEGER = 2 # /

p01573, INTEGER = 3 #}

p0158SET = {}

p0159Character strings

p0160The coding for the different string types and subtypes derived therefrom is identical. The type is according to the data type either by the text "NumericString" "Printable String", "TeletexString", "VideotexString", "Visible String", "lA5String", "Graphic String", "General String", "ObjectDescriptor", "UTCTime" or GeneralizedTi e "coded. As long as no special characters and not encodable characters are included, the simple value encoding can be used. This is "simple" initiated by the text and with a '/' -.. Separated characters is the number of characters The text itself follows uncoded in braces included Once the encoding process with the simple value coding is no longer possible, carried out the . Advanced coding, which is initiated with "complex" is followed by a "/" - character separated the coding of the number of characters followed by "{" character. Thereafter, the code of each character by a "/" are - character encoding of each other separated hexadecimal. the coding is terminated by a "}" character.

p0161ASN.1 definition encoding (more examples) Str :: = General String Graphic String = simple, 3 {xyz}

p0162General string = complex, 3 {78/79 / 7A}

CHOICE

p0164The type of Choice is encoded by the text "CHOICE". The coding of the value of a CHOICE is similar to the encoding of a sequence, starting with the number "1" for the number of coded in this Choice elements. The coding of the element contained begins with a "{" sign and ends with a "}" character. whose position is encoded separated with a comma before the coding of the type.

p0165ASN.1 definition encoding (more examples)

p0166Ex :: = CHOICE {CH0ICE = 1 {2, GraphicString- simple.3 {A}} type I INTEGER, CH0ICE = 1 {1, INTEGER = 123 #} type2 GraphicString} ANY DEFINED BY

p0167The type ANY DEFINED BY is defined by the string "ANY". The value of ANY Typens encoded opposed to BER encoding as a separate type. Because the ANY DEFINED BY type is permitted only in a SEQUENCE or SET, the example shows the corresponding definition within a sequence definition. For encoding first is the text "{1" coded and then encodes the laid down for ANY types Type. The definition is completed by the "}" character.

p0168ASN.1 definition encoding Seq:: = SEQUENCE {SEQUENCE = 2 {1, INTEGER = 1 # / 2, ANY = {INTEGER = 5 #}} i INTEGER; a ANY DEFINED BY i}

p0169reference information model

p0170Contrary to the clear text encoding that can decode even without knowledge of the information model, a stored in metadata format reference the information model is necessary for a BER encoding. To encode the inforamtion about-to-use metadata within the plain text encoding, each type coding can optionally precede the metadata to be used. This metadata is then only valid for this and the types contained therein.

p0171ASN.1 definition encoding Ex:: = INTEGER setMetadata = filename, INTEGER = 123 #