Tags:
create new tag
, view all tags

MX-TCE Binary API

The API message format is shown below.

mxTceApiMsg.jpg

  • Message Body Length: The length of message body in number of octets and must be multiple of 4.
  • Universal Client ID (UCID): A 32-bit ID number to uniquely identify an API client.
  • Message Sequence Number: The number can be used to track the request/reply.
  • Check Sum: The arithmetic sum of the first three 32 bit words
  • Options: 32 bits for options/flags. Values TDB.
  • Message Tag: 32-bit word used associated with options to provide extra header information.
  • Message body contains TLVs, each a parameter that is defined in the ARCHSTONE NSI Resource Computation Service. All TLVs are 4-byte word aligned.

Request Message

  • Network Service ID (NSID) TLV
  • Session ID (SID) TLV
  • Reserved Constraint TLV
  • Optional Constraint TLV
  • Request Topology (RT) TLV

Reply Message

  • Network Service ID (NSID) TLV
  • Session ID (SID) TLV
  • Global Resource ID (GRI) TLV (optional)
  • Reserved Constraint TLV
  • Optional Constraint TLV
  • Service Topology (ST) TLV
  • Computation Status TLV
  • Error Message TLV
Topic revision: r2 - 2010-11-29 - XiYang
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback