Applies to: NAS/C 5G r16.8.0 v8.3.1-8.3.5
What's New in NAS/C 5G r16.8.0 v8.3.5
- In the "QoS flow descriptions" information element, when the parameter identifier indicates "averaging window", the parameter contents field is two octets in length. Previously, the parameter contents field was three octets in length.
What's New in NAS/C 5G r16.8.0 v8.3.4
- The new ossNASFindUPULists() NAS/C helper API function is now available.
The function extracts into an output array the lengths and positions
of the encodings of the UE parameters update list(s) that are present in a
binary DL NAS transport message. Also, it allows you to calculate and
verify the checksum of the UE parameters update list after decoding a message
or to calculate and insert the checksum into a newly encoded message.
- The ossNASPrintPDU() function no longer reports an error on a NAS message
that contains an invalid READONLY field. The documentation says that the
values of READONLY fields do not matter. Such invalid values are indeed
irrelevant when a NAS message is handled by ossNASEncode(). Previously, an
invalid value could cause ossNASPrintPDU() to fail, for example, a value
of 0 in a READONLY field that is constrained to be in the range 1..5.
- The version 8.3.2 bug fix that made the QoS rule precedence and QoS flow
identifier fields optional was mistakenly missed in version 8.3.3. It is
- The sNSSAI and eapMessage fields of the
types are now mandatory as specified by the standard. Previously, to encode the
corresponding messages correctly the user had to mark both fields in the bitmask as present;
the decoder failed on valid messages.
What's New in NAS/C 5G r16.8.0 v8.3.3
The NAS LTE and NAS 5GS libraries can now be used at the same time in an application.
Previously, this was not possible due to name conflicts.
- A Routing Indicator field value with a length < 4 in a 5GS mobile identity
information element for a "SUCI" type of identity and an "IMSI" SUPI format will now
be encoded correctly.
Previously, to correctly encode such a short value, it had to be padded with spaces to make
it 4 in length.
Hexadecimal digits are now allowed in a
element. Previously, only decimal digits were allowed.
What's New in NAS/C 5G r16.8.0 v8.3.2
- For some of the QoS rule operations, table 126.96.36.199.1 (Chapter 188.8.131.52)
in TS 24.501 specifies the presence or absence of the QoS rule precedence
and QoS flow identifier fields. For other operations, the standard does not
explicitly specify whether these fields are absent or present.
In this version of the OSS NAS/C 5G Tools, the QoS rule precedence and QoS
flow identifier fields are optional. Previously, unless the standard
indicated otherwise, these fields were treated as mandatory.
NOTE: It is the responsibility of the application to make sure that when the
optional segregationAndQFI field is present in a NAS message passed to
ossNASEncode(), the antecedent optional qosRulePrecedence field is also present.
What's New in NAS/C 5G r16.8.0 v8.3.1
- The ossNASPrintPDU() API function now prints the value of a
read-only field "as is" and prefixes it with the <!--AUTO--> comment. Previously, read-only
fields were always printed as 0. Note that the application does not need to
set a read-only field because the ossNASEncode() function ignores
its value and sets the corresponding value in the encoded message as required by the
3GPP NAS technical specification. Therefore the values of read-only fields
in a NAS message printed by ossNASPrintPDU() are irrelevant if
the message will be passed to ossNASEncode().
- For consistency with other instances of the Mapped HPLMN Slice
Differentiator, the type of the NAS5GS1680_MappedSNSSAIContentEntry
structure's mappedHPLMNSD field is changed from ossOctetString to
NAS5GS1680_SD, which is OSS_UINT32.
This documentation applies to the OSS NAS Tools for C for 5G v8.3.1-8.3.5 for 3GPP Release 16.8.0.
Copyright © 2022 OSS Nokalva, Inc. All rights reserved.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means electronic, mechanical, photocopying, recording or otherwise, without the prior permission of OSS Nokalva, Inc.
Every distributed copy of the OSS NAS Tools for C for 5G is associated with a specific license and related unique license number. That license determines, among other things, what functions of the OSS NAS Tools for C for 5G are available to you.