WO2010000139A1 - 用于通信数据的tlv格式处理方法 - Google Patents
用于通信数据的tlv格式处理方法 Download PDFInfo
- Publication number
- WO2010000139A1 WO2010000139A1 PCT/CN2009/070391 CN2009070391W WO2010000139A1 WO 2010000139 A1 WO2010000139 A1 WO 2010000139A1 CN 2009070391 W CN2009070391 W CN 2009070391W WO 2010000139 A1 WO2010000139 A1 WO 2010000139A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- function
- type
- code stream
- decoding
- value
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
Definitions
- ASN.1 BACKGROUND OF THE INVENTION Abstract Syntax Notation 1
- ITU International Telecommunications Union
- Each node only needs to know the data format translated or translated from ASN.1 into ASN.1, without having to know the format in which the data exists anywhere else on the network.
- ASN.1 has two parts: The first part (ISO 8824/ITU X.208) describes the data, data type and sequence format within the information, ie the syntax of the data; the second part (ISO 8825/ITU X.209) describes how The rules for composing each part of the data into a message, that is, the basic encoding rules of the data.
- ASN.1 was originally developed as part of X.409 and later became a standard independently.
- the first public key infrastructure (PKI) standard is mainly based on ASN.1.
- SNMP Simple Network Management Protocol
- ASN.1 is used to define The format of SNMP data units and objects.
- ASN.1 is widely used in other fields such as communication and computer.
- ASN.1 has the following special characteristics: 1.
- the message is in a tree structure, and more levels of message nesting can be defined as needed.
- the data type of the node in the message it may be a simple data type, such as INTEGER, GRAPHICSTRING, ENUM, etc.; or it may be a composite data type SET, SEQUENCE, SET OF, SEQUENCE OF containing the subordinate node.
- a node may not exist, because the corresponding node is allowed to be set to OPTIONAL, indicating that it is optional.
- ASN.1 file first define the ASN.1 type in the ASN.1 file, then compile the ASN.1 type through the compiler, making it a type of intermediate programming language such as Java or C++, and then by using The type of programming language should be used to achieve the purpose of communication.
- ASN.1 supports BER, DER, VAL and other encodings.
- the intermediate language type instance can be encoded as a code stream, which can be decoded from the code stream to an instance of the corresponding intermediate language type.
- UserNameList-T is an array of UserName-T elements.
- C/S Client/Server Server
- the sender of the message fills in the ASN.1 header and the body of the message.
- the header includes the command code.
- the body of the message is of the AsnAny type. The actual data type varies according to the command code.
- 4 ⁇ sender code 4 The text is the code stream and is sent to the 4 text recipients;
- the receiver of the message receives the message stream, decodes the header, and then decodes the file with a specific data type according to the command code therein;
- TLV format data type, data length, data body
- Type (Type), Length (Length), Value (Value) referred to as TLV format.
- Organizing data in TLV format is very convenient and efficient, especially for variable-length data.
- the organization of the content in the application layer data body generally adopts this format, and the BER encoding in ASN.1 is actually a TLV encoding.
- the data type T in the TLV encoding is not customizable by the user, and if the same name type is not completely defined in different versions, the Client and the Server may not be able to communicate.
- a TLV format processing method for communication data including the following steps:: defining an integer type T in an ASN.1 format; and sending a message in an ASN.1 format,
- the packet includes an instance of the data structure.
- the sender encodes the packet into a code stream.
- the code stream of the data structure instance in the packet includes the value V, or includes the integer type of V and the length L of V.
- the TLV format processing method further comprises: processing an integer type function for a compiler of the ASN.1 format.
- the TLV format processing method further comprises: obtaining an integer type by a function in a C++ type of the ASN.1 format.
- the sender encodes the message into the code stream, including: calling the value encoding function, the length encoding function, and the integer type encoding function through the overall encoding function, or calling only the value encoding function by the overall encoding function to encode the message into a code
- An integer type encoding function is used to obtain an integer type in a code stream according to data encoding in a data structure instance; for a data structure instance of a simple data type, a value encoding function is used to encode a simple data in a data structure instance into a code stream.
- V in the case of a data structure of the SEQUEENSE or SET type, the value encoding function is used to sequentially call the overall encoding function of each member in the data structure instance; for the data structure instance of the SEQUEENSE OF or SET OF type, the value encoding function is used for Invoke the entire element of the array in the data structure instance in turn a body coding function; for a CHOICE type data structure instance, a value encoding function is used to encode selected members of the data structure instance into V in the code stream, where V includes the serial number and selected member of the selected member in CHOICE .
- the TLV format processing method further includes: the receiver decoding the code stream.
- decoding the code stream specifically comprises: calling a value decoding function, a length decoding function, and an integer type decoding function by an overall decoding function, or only calling a value decoding function by an overall decoding function to decode the code stream; and using an integer type decoding function Decoding the code stream according to the integer type in the code stream; for the data structure instance of the simple data type, the value decoding function is used to decompose the V in the code stream into simple data in the data structure instance; for the data structure of the SEQUEENSE or SET type For example, the value decoding function is used to sequentially decode V in the code stream into each member data in the data structure instance; for the data structure instance of the SEQUEENSE OF or SET OF type, the value decoding function is used for the V in the ⁇ 1 code 3 ⁇ 4 ⁇ Decompose into each element of the array in the data structure instance; determine whether the length of the decoded stream in the structure is less than L in the process of decoding V, and continue decoding if less than
- the value decoding function, the length decoding function, and the integer type decoding function are called by the global decoding function, or only the value decoding function is called by the global decoding function to decode the code stream.
- the integer decoding function determines whether the integer type is 0. Or whether it exists; if it is not 0 or exists, the value decoding function, the length decoding function, and the integer type decoding function are called, wherein the value decoding function is called to decode the integer type in the code stream, and whether the obtained integer type and its own are verified The integer types are consistent. If they are inconsistent, the decoding is considered abnormal.
- the method for processing the TLV format in the foregoing embodiment of the present invention is capable of interworking between different versions of ASN.1 because the method of extending the T is added to the ASN.1 format, so that the different versions of the monthly protocol can not communicate with each other. And can implement the object-oriented approach of TLV.
- FIG. 1 is a flowchart of a TLV format processing method for communication data according to an embodiment of the present invention
- FIG. 2 is a diagram of a client and a server sharing the same development locale according to a preferred embodiment of the present invention.
- FIG. 3 is a development process when different development language environments are used according to a preferred embodiment of the present invention;
- FIG. 4 is a diagram showing different development language environments and protocol versions used by a client and a server according to a preferred embodiment of the present invention.
- FIG. 5 is a schematic diagram of an ESNACC C++ basic class type inheritance system according to a preferred embodiment of the present invention;
- FIG. 6 is a flow chart of a TLV overall decoding function according to a preferred embodiment of the present invention.
- the embodiment of the present invention provides a TLV format processing method for communication data, in which the function of the client and the server is inconsistent when the versions of the client and the server are inconsistent.
- the method of extending the T is added to the ASN.1 format, and the packet is filled in the extended ASN.1 format, which can overcome the defect that different versions of the protocol cannot be interworked, and can implement different versions of ASN.1. Interoperability, and an object-oriented approach to implementing TLV.
- the invention will be described in detail below with reference to the drawings in conjunction with the embodiments. The features of the embodiments of the present invention and the embodiments may be combined with each other if they do not conflict.
- Step S10 defining an integer type T in an ASN.1 format
- Step S20 the sender fills in In the ASN.1 format message, the message includes an instance of the data structure.
- step S30 the sender encodes the 4 ⁇ file into a code stream, and the code stream of the data structure instance in the message includes the value V, or includes an integer type of V.
- the TLV format processing method adopts the method of extending the T in the ASN.1 format, so it can overcome the defect that different versions of the protocol cannot be intercommunicated, can realize the interworking of different versions of ASN.1, and can implement an object-oriented method of TLV.
- the above processing will be described in detail below.
- the structure of an integer type is of the SEQUENCE, SET or CHOICE type of the same type name. It is stipulated that if the member is to be modified, only the net boost port or the net decrease member is allowed, and only the last member can be changed. .
- the old and new compatibility of protocol messages can be achieved.
- the extended member can only be at the end of the parent type, but not reduced.
- the function of the integer type can be set for the compiler of the ASN.1 format.
- the integer type is obtained by a function in the C+ ten type of the ASN.1 format.
- Step S20 The operation of the sender to encode the message into the code stream specifically includes: calling the value encoding function, the length encoding function, and the integer type encoding function through the overall encoding function, or calling only the value encoding function through the overall encoding function to
- the message is encoded as a code stream; the integer type encoding function is used to obtain an integer type in the code stream according to the data in the data structure instance; specifically, for a data structure instance of a simple data type, the value encoding function is used to implement the data structure instance
- the simple data in the code is encoded into V in the code stream; for the data structure instance of the SEQUEENSE or SET type, the value encoding function is used to sequentially call the overall encoding function of each member in the data structure instance; for the data of the SEQUEENSE OF or SET OF type
- the value encoding function is used to sequentially call the overall encoding function of each element of the array in the data structure instance; for the CHOICE type data structure
- the value encoding function, the length encoding function, and the integer type encoding function are called by the overall encoding function, that is, the code stream includes V, V length L, and integer type.
- the TLV format processing method further includes: the receiver decodes the code stream.
- the operation of decoding the code stream specifically includes: calling a value decoding function, a length decoding function, and an integer type decoding function by an overall decoding function, or performing only a value decoding function by using an overall decoding function to perform code stream decoding; integer type decoding
- the function is used to decode the code stream according to the integer type in the code stream; for the data structure instance of the simple data type, the value decoding function is used to resolve the V in the code stream into simple data in the data structure instance; for the SEQUEENSE or SET type
- the value decoding function is used to sequentially decode the V in the code stream into each member data in the data structure instance; for the data structure instance of the SEQUEENSE OF or SET OF type, the value decoding function is used in the code stream V is sequentially solved into each element of the array in the data structure instance; in the process of decoding V, it is judged whether the length of the decoding stream in the structure is less than L, if it is less than L, the decoding is
- the foregoing operation of calling the value decoding function, the length decoding function, and the integer type decoding function by the overall decoding function, or only calling the value decoding function by the global decoding function to decode the code stream specifically includes: determining the integer type by the overall decoding function Whether it is 0 or exists; if it is not 0 or exists, the value decoding function, the length decoding function, and the integer type decoding function are called, wherein the value decoding function is called to decode the integer type in the code stream, and whether the obtained integer type is verified It is consistent with its own integer type.
- the length decoding function is called to decode L in the code stream, and then the value encoding function is called to decode the V in the code stream. If the length VL obtained by decoding V is less than L, Then skip the L-vL byte; if it is 0 or does not exist, only the value decoding function is called.
- the overall decoding function first determines if its own T is zero. If not 0, decode T, verify
- T is consistent with its own T. If it is inconsistent, it is considered that the decoding is abnormal, and then L is decoded, and then V is decoded. If the length vL of the decoded V is less than L, the L-vL byte is skipped, and the length in the type is balanced; if it is 0, Directly press V to decode.
- the virtual functions required by the above encoding function and decoding function may be added to the ASN.1 base class in the ASN.1 C ten-base module; and the classes required by the above encoding function and decoding function in the ASN.1 C++ compiler and Its member function.
- the above preferred embodiment includes two functional modules: a base module, a compiler.
- the base module implements the base class and some support functions that support the TLV.
- the compiler implements the analysis of the ASN.1 file and generates the classes corresponding to each ASN.1 type and their member functions.
- the four-text defined by the TLV protocol can not only interact with the version protocol, but also allow the client and server of the new and old protocols to interact with each other.
- the encoding rules provided by the /S interaction are guaranteed.
- Embodiments of the present invention may be implemented independently or extended on any existing ASN.1 compiler platform.
- FIG. 2 shows a development process when the client and the server share the same development language environment according to a preferred embodiment of the present invention. Both Client and Server are developed in C++. Including: A.
- Interface developers define ASN.1 interface files, and use Asn.1 C++ compiler to generate interface files. h and interface files. cpp; B. Server developers write Server 4 weights, and interface files.h, interfaces File. cpp - compiled into an executable server program; C. Client developers write Client code, and interface file .h, interface file. cpp - compiled into an executable client program; D. executable Client program and The executable Server program uses the Asn. l C++ base module to communicate interactively during execution.
- Figure 3 illustrates the use of different development locales in accordance with a preferred embodiment of the present invention.
- the development process, the client uses java development
- Server uses C++ development. Including: A.
- the interface developer defines the ASN.1 interface file, and generates the interface file for the C++ developer using the Asn.l C++ compiler. h, the interface file. cpp, for the java developer to generate the interface file with the Asn. l java compiler .java; B. Server developers write Server «code, and interface file.h, interface file. cpp - compiled into an executable server program; C. Client developers write Client code, and interface file .j ava compile The executable client program; D. The executable Client program and the executable Server program communicate with each other using the Asn.l base module of the respective language during execution. FIG.
- the server is an old version
- the client is developed by java
- the server is developed by C++.
- both Client and Server are developed in C++ in the implementation steps.
- the process includes:
- A. Interface creator The version of the interface file defined in the old version, l.asn, defines the interface file version 2.asn when developing the new version. Compile the C++ and Java interface implementation files for the two versions respectively;
- B. Server developers write the Server code in the old version, and compile the executable file execution with the interface file version 1.h and the interface file version l.cpp. Document
- the C. Client developer writes the Client code in the new version, and compiles the executable client executable file into the interface file 2.java.
- FIG. 5 illustrates an ESNACC C++ base class type inheritance system in accordance with a preferred embodiment of the present invention.
- ESNACC basic class inheritance relationship hierarchy diagram, ESNACC basic base class is AsnType, AsnType is abstract base class.
- Asnlnt is also derived from PERGgeneral
- AsnEnum is derived from Asnlnt
- AsnOid is derived from AsnRelativeOid.
- AsnList is an intermediate type that implements other Asn.
- l classes, AsnSetOf, and AsnSeqOf are derived from AsnList; std::string, std::list using the standard template library to further support SEQUENCE OF, SET OF, and so on.
- Some application string types such as VisibleString, GraphicString, Ia5 String, PrintableString, NumericString are derived from the base string type AsnString. Its MediumizedTime, UTCTime is derived from VisibleString. 6 shows a flow chart of the overall TLV decoding function in accordance with a preferred embodiment of the present invention.
- the present invention can be applied to any object-oriented programming language implementation, this article mainly in conjunction with C + + discussion, can also use other object-oriented The programming language, such as the JAVA language implementation.
- the source of the demand is in the network management system.
- a network management system often needs to manage various device network elements. Different devices have different versions.
- the network management system also has different versions.
- the network management and device software need to exchange packets.
- the version between the device and the device software is relatively small. You need a management NE that is compatible with the NMS. This requires a protocol rule to support this requirement.
- ESNACC is an open source ASN.1 compiler that supports BER, PER encoding, and ASN.1 base modules provided by the compiler:
- the ASN.1 compiler usually provides a compiler and base support module, and the compiler compiles the ASN.1 file.
- Specific programming language code such as C++, Java, compiles the types of ASN.1 into classes of programming languages.
- the base support module provides support for generated code execution.
- the TLV codec rules are implemented by tampering with the compiler and the underlying support module.
- T uses 2 bytes
- L uses 4 bytes.
- the format is in network order. Other formats may be used in the implementation to store T and L, such as the representation format of the length in the BER.
- T can be expressed in various formats, such as decimal, hexadecimal. The syntax is optional, and the absence of the representation ⁇ is 0.
- the old version of the 4 ⁇ code stream to the new version 4 ⁇ d3, d4 uses the default value, and the c3 code stream is ignored.
- the new version of the 4 ⁇ code stream to the old version • t ⁇ text d3, d4 code stream is ignored, and the value of c3 uses the default value.
- Other data is old and new The version is consistent.
- V-encoding function virtual AsnLen TlvEncContent ( AsnBuf &_b ); Overall decoding code function: virtual AsnLen TlvDec ( AsnBuf &-b, AsnLen &bytesDecoded ); Value decoding function: virtual AsnLen TlvDecContent ( AsnBuf &-b, short iT,
- AsnLen iL, AsnLen & bytesDecoded where - b is the stream parameter, byteDecoded is the cumulative number of bytes decoded by a message stream, iT is the T in the stream, iL is the L in the stream, TlvEnc, TlvEncContent The return value is the length of the encoded stream.
- the TlvDec and TlvDecContext return values are the number of bytes decoded in the function. According to the implementation mode function prototype can be changed according to needs.
- step S10 develop a new/old version interface file. asn, generate interface 4 ⁇ .h, interface 4 ⁇ . cpp, client and server are written in C+10, which is similar to Figure 3. In this way, it is possible to implement interactive communication between different versions of client and server.
- various possible changes or substitutions may be made in accordance with the description and specific embodiments of the technical solutions of the present invention, such as the location and format of T, the format of L, and possibly Compressed and encrypted formats, the implementation of the function methods may be different, even without the use of member functions and the use of coding operators. From the above description, it can be seen that the present invention achieves the following technical effects:
- the type can be converted to a code stream by an encoding method. 2. It can be decoded into a class instance by the decoding method 4 bar code stream.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Communication Control (AREA)
- Devices For Executing Special Programs (AREA)
- Compression, Expansion, Code Conversion, And Decoders (AREA)
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BRPI0915217-2A BRPI0915217B1 (pt) | 2008-07-02 | 2009-02-10 | Método para processar um formato tlv de dados de comunicação |
EP09771909.0A EP2302864B1 (en) | 2008-07-02 | 2009-02-10 | Method for processing tlv format of communication data |
RU2011103630/08A RU2473180C2 (ru) | 2008-07-02 | 2009-02-10 | Способ обработки данных связи tlv-формата |
US13/001,978 US20110134939A1 (en) | 2008-07-02 | 2009-02-10 | Method for processing tlv format of communication data |
ES09771909.0T ES2659396T3 (es) | 2008-07-02 | 2009-02-10 | Método para procesar formato TLV de datos de comunicación |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2008101376473A CN101316241B (zh) | 2008-07-02 | 2008-07-02 | 用于通信数据的tlv格式处理方法 |
CN200810137647.3 | 2008-07-02 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010000139A1 true WO2010000139A1 (zh) | 2010-01-07 |
Family
ID=40107085
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/070391 WO2010000139A1 (zh) | 2008-07-02 | 2009-02-10 | 用于通信数据的tlv格式处理方法 |
Country Status (7)
Country | Link |
---|---|
US (1) | US20110134939A1 (zh) |
EP (1) | EP2302864B1 (zh) |
CN (1) | CN101316241B (zh) |
BR (1) | BRPI0915217B1 (zh) |
ES (1) | ES2659396T3 (zh) |
RU (1) | RU2473180C2 (zh) |
WO (1) | WO2010000139A1 (zh) |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101316241B (zh) * | 2008-07-02 | 2013-05-01 | 中兴通讯股份有限公司 | 用于通信数据的tlv格式处理方法 |
CN103246671A (zh) * | 2012-02-09 | 2013-08-14 | 中兴通讯股份有限公司 | 抽象语法标记文件的处理方法及装置 |
CN103036877A (zh) * | 2012-12-10 | 2013-04-10 | 北京中创信测科技股份有限公司 | 一种基于tlv格式协议的编解码代码生成装置及方法 |
US10109983B2 (en) | 2016-04-28 | 2018-10-23 | Hewlett Packard Enterprise Development Lp | Devices with quantum dots |
US10566765B2 (en) | 2016-10-27 | 2020-02-18 | Hewlett Packard Enterprise Development Lp | Multi-wavelength semiconductor lasers |
US10680407B2 (en) | 2017-04-10 | 2020-06-09 | Hewlett Packard Enterprise Development Lp | Multi-wavelength semiconductor comb lasers |
US10396521B2 (en) | 2017-09-29 | 2019-08-27 | Hewlett Packard Enterprise Development Lp | Laser |
EA201800181A1 (ru) * | 2018-03-30 | 2019-10-31 | Система управления сетью pos-терминалов | |
CN109298866A (zh) * | 2018-09-26 | 2019-02-01 | 杭州米加科技股份有限公司 | 基于c语言的tlv格式协议快速解析方法 |
US11271792B2 (en) * | 2019-01-18 | 2022-03-08 | Hewlett Packard Enterprise Development Lp | Using a recursive parser tree to implement a smaller code segment for an embedded simple network management protocol agent |
CN113742294A (zh) * | 2021-08-23 | 2021-12-03 | 宜通世纪科技股份有限公司 | 一种asn.1-per信令消息解码方法、系统、装置及介质 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1359065A (zh) * | 2000-12-15 | 2002-07-17 | 国际商业机器公司 | 将抽象句法表示法1数据模型化成对象模型的方法及系统 |
CN1627757A (zh) * | 2003-12-12 | 2005-06-15 | 华为技术有限公司 | 通用消息解释器的实现方法 |
CN101149753A (zh) * | 2007-10-25 | 2008-03-26 | 中兴通讯股份有限公司 | 复杂抽象语法标识对象的存储方法 |
CN101316241A (zh) * | 2008-07-02 | 2008-12-03 | 中兴通讯股份有限公司 | 用于通信数据的tlv格式处理方法 |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5473691A (en) * | 1993-11-05 | 1995-12-05 | Microsoft Corporation | System and method for computer data transmission |
US5649189A (en) * | 1995-11-29 | 1997-07-15 | 3Com Corporation | Method and apparatus for single pass data encoding of binary words using a stack for writing in reverse order |
US6356955B1 (en) * | 1996-02-15 | 2002-03-12 | International Business Machines Corporation | Method of mapping GDMO templates and ASN.1 defined types into C++ classes using an object-oriented programming interface |
JP3531536B2 (ja) * | 1999-05-28 | 2004-05-31 | 日本電気株式会社 | 抽象構文記法を用いたデータ構造定義における型情報の動的割り当て方法 |
FI20002720A (fi) * | 2000-12-12 | 2002-06-13 | Nokia Corp | Menetelmä konversioiden suorittamiseksi |
EP1400784A1 (de) * | 2002-09-14 | 2004-03-24 | Leica Geosystems AG | Verfahren und Vorrichtungen zur Nutzung von Daten in nicht direkt verarbeitbaren Datenformaten |
US20050181787A1 (en) * | 2004-02-18 | 2005-08-18 | Judd Tom D. | Systems and methods for encoding and decoding data messages |
US6999010B2 (en) * | 2004-04-16 | 2006-02-14 | Ares International Corporaton | Table look-up method for abstract syntax notation encoding/decoding system |
CN101197818A (zh) * | 2006-12-08 | 2008-06-11 | 中兴通讯股份有限公司 | 一种asn.1报文面向对象的处理方法 |
CN101159743B (zh) * | 2007-10-22 | 2010-06-23 | 中兴通讯股份有限公司 | Asn.1编解码函数自动生成中的数据类型选择方法 |
US7996523B2 (en) * | 2008-01-17 | 2011-08-09 | Fluke Corporation | Free string match encoding and preview |
-
2008
- 2008-07-02 CN CN2008101376473A patent/CN101316241B/zh active Active
-
2009
- 2009-02-10 BR BRPI0915217-2A patent/BRPI0915217B1/pt active IP Right Grant
- 2009-02-10 EP EP09771909.0A patent/EP2302864B1/en active Active
- 2009-02-10 US US13/001,978 patent/US20110134939A1/en not_active Abandoned
- 2009-02-10 RU RU2011103630/08A patent/RU2473180C2/ru active
- 2009-02-10 WO PCT/CN2009/070391 patent/WO2010000139A1/zh active Application Filing
- 2009-02-10 ES ES09771909.0T patent/ES2659396T3/es active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1359065A (zh) * | 2000-12-15 | 2002-07-17 | 国际商业机器公司 | 将抽象句法表示法1数据模型化成对象模型的方法及系统 |
CN1627757A (zh) * | 2003-12-12 | 2005-06-15 | 华为技术有限公司 | 通用消息解释器的实现方法 |
CN101149753A (zh) * | 2007-10-25 | 2008-03-26 | 中兴通讯股份有限公司 | 复杂抽象语法标识对象的存储方法 |
CN101316241A (zh) * | 2008-07-02 | 2008-12-03 | 中兴通讯股份有限公司 | 用于通信数据的tlv格式处理方法 |
Also Published As
Publication number | Publication date |
---|---|
BRPI0915217A2 (pt) | 2016-09-13 |
ES2659396T3 (es) | 2018-03-15 |
RU2473180C2 (ru) | 2013-01-20 |
US20110134939A1 (en) | 2011-06-09 |
EP2302864A1 (en) | 2011-03-30 |
EP2302864B1 (en) | 2017-11-15 |
EP2302864A4 (en) | 2013-11-20 |
RU2011103630A (ru) | 2012-08-10 |
CN101316241B (zh) | 2013-05-01 |
CN101316241A (zh) | 2008-12-03 |
BRPI0915217B1 (pt) | 2020-10-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2010000139A1 (zh) | 用于通信数据的tlv格式处理方法 | |
EP2124419B1 (en) | An object oriented management device for asn.1 message | |
Neira‐Ayuso et al. | Communicating between the kernel and user‐space in Linux using Netlink sockets | |
US7814211B2 (en) | Varying of message encoding | |
US9124466B2 (en) | System and method for exposing distributed transaction services as web services | |
WO2017054531A1 (zh) | 一种基于yang模型的编译方法、及对应的接口、组件和系统 | |
US7593994B2 (en) | Generating a dynamic web service and dynamic service surrogate for legacy application components | |
Käbisch et al. | Efficient and flexible XML-based data-exchange in microcontroller-based sensor actor networks | |
WO2006014766A2 (en) | Method and apparatus for converting network management protocol to markup language | |
US6976263B2 (en) | Mechanism for encoding and decoding upgradeable RPC/XDR structures | |
WO2005057873A1 (fr) | Procede de mise en oeuvre d'un dispositif universel expliquant les messages | |
KR100751449B1 (ko) | OSGi 서비스 플랫폼 기반의 스텁 번들 생성 방법 | |
JP2004234405A (ja) | プロトコル符号化/復号化装置 | |
Qiang et al. | ASN. 1 application in parsing ISUP PDUs | |
KR100660057B1 (ko) | 패스트 인포셋을 이용한 이진 엑스엠엘 저장 방법 및 복원방법 | |
Alliance | Network Device: Gateway Specification | |
KR100737686B1 (ko) | 브-엠 기반의 기업용 애플리케이션 전송보안 시스템 및방법 | |
Lu | A CORBA-based Interface-centric Approach to Signaling for IP-based Telephony Services | |
Andriescu | Dynamic Data Adaptation for the Synthesis and Deployment of Protocol Mediators | |
Selic | Extending the Unified Modeling Language for Large-Scale Highly-Dependable Distributed Systems | |
Konovalov et al. | with Symbolic Computation Software Composability Protocol | |
Layka et al. | Web Services | |
US20060248108A1 (en) | Apparatus and method for efficient encoding of application definition using contiguous arrays | |
Carrilho et al. | Policy-based Management of DiffServ using XML Technologies. | |
Taylor et al. | Web Services Protocols |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09771909 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 141/MUMNP/2011 Country of ref document: IN |
|
REEP | Request for entry into the european phase |
Ref document number: 2009771909 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2009771909 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011103630 Country of ref document: RU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13001978 Country of ref document: US |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01E Ref document number: PI0915217 Country of ref document: BR Free format text: SOLICITA-SE A REGULARIZACAO DA PAGINA DE RESUMO, POR ESTA NAO APRESENTAR TITULO. |
|
ENP | Entry into the national phase |
Ref document number: PI0915217 Country of ref document: BR Kind code of ref document: A2 Effective date: 20110103 |