What's New

What's New in NAS/C LTE/EPC r15.8.0 v7.2.1

New Features

• The new ossNASJSON2Binary and ossNASXML2Binary functions that convert textual JSON or XML NAS messages to binary encoded form.
• The new ossNASDecodeJSON and ossNASDecodeXML that decode JSON or XML encoded NAS messages. The decoded messages, which can be optionally modified, can then be re-encoded to binary NAS messages using the ossNASEncode() function.
• NAS applications can use the following functions to retrieve the corresponding IE values of a binary NAS message even when the message decoding fails with an unrecoverable error, provided these values are present in the message; otherwise, the functions will return a value of 0XFFFFF. These functions are useful when preparing an error response as specified in Section 7 of 3GPP TS 24.301.
  • ossNASGetEpsBearerIdentity
  • ossNASHasEpsBearerIdentity
  • ossNASGetProcedureTransactionIdentity
  • ossNASHasProcedureTransactionIdentity
  • ossNASGetProtocolDiscriminator
  • ossNASHasProtocolDiscriminator
  • ossNASGetMessageType
  • ossNASHasMessageType

Improvements

• The ossNASDecode() API function now always ignores a truncated optional Information Element at the end of a message. Previously, it could return a non-zero error code in this case.
• The ossNASDecode() API function now returns the new error code 71 and the "Too short message" error message when, according to 3GPP TS 24.301 v7.2.1, the input message should be ignored because it is too short to contain a message type Information Element. Previously, other error codes were returned in this case.
• A few defects in mapping NAS messages to the annotated ASN.1 specification are fixed. Some of the modifications result in changes to the NAS1580.h header file.