mfw_nrf9151-ntn release notes
-----------------------------

** Introduction to the mfw_nrf9151-ntn release notes **

These release notes describe the changes in the mfw_nrf9151-ntn firmware from version to version.
The release notes are intended to briefly list all relevant changes in each version.

Copyright (c) Nordic Semiconductor ASA. All rights reserved.

*** mfw_nrf9151-ntn_1.0.1
*************************

The mfw_nrf9151-ntn is Cellular IoT and Positioning firmware for the modem subsystem of the nRF9151
LACA A1. It supports 3GPP LTE Release 14 LTE-M and NB-IoT, with specific optional features from
Releases 14 and 15, and selected features of Release 17 Non-Terrestrial Network NTN-NB-IoT. The
firmware also supports GPS L1C/A and QZSS L1C/A positioning.

LTE-M operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 18, 19, 20, 25, 26, 28, 66,
85, and 106.

NB-IoT operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 17, 19, 20, 25, 26, 28, 65,
66, 85, and 106.

E-UTRA band 106 is supported by nRF9151 LACA A1.

NTN-NB-IoT operation is enabled on E-UTRA bands 23, 255, and 256, and is supported by nRF9151 LACA
A1.

This release aligns with v1.2 of the nRF91x1 NTN AT Commands Reference Guide.

It is advisable to use the latest versions of the nRF Connect and nRF Connect Programmer tools.

*** New functionality
*********************
- Introduced a new mechanism for scanning frequencies to identify and select the best quality NTN
  cell before camping. The feature can be controlled through AT%FEACONF configuration id value 8.
- Added support for configuring NB-IoT unicast transmission on a non-anchor carrier (NPDSCH and
  NPDCCH), as introduced in 3GPP Release 13, via the AT%FEACONF configuration id value 9.
- Added support for NTN non-anchor carrier operation with Release 18 based downlink frequency
  calculation, enabling improved NTN satellite connectivity in compliance with Skylo certification
  requirements.

*** Changes
***********
- Changed the %MDMEV: DETECTED COUNTRY modem event from an informational event to a regular event to
  reduce AT notification load.
- After a modem FW update, existing cellular profiles are now automatically deleted to prevent
  compatibility issues with the profile/context format. The application should always check that
  profiles exist before using them and re-create them if needed.

*** Bug fixes
*************
- Fixed an issue where the NTN attach context expired prematurely due to an incorrect time
  calculation during cellular profile de-serialization, causing unnecessary re-attach procedures.
- Fixed the AT%SQP command to include also valid EARFCN and Physical Cell ID (PCI) when modem is
  performing operations like cell reselection, and connections release.
- Fixed a modem instability that could occur during high-intensity network data transfer over a PPP
  connection.
- Fixed an issue where manual PLMN selection via AT+COPS could stall indefinitely when location
  information request was triggered simultaneously with the ongoing PLMN selection.
- Fixed an issue where a %MDMEV SEARCH STATUS 3 and 4 indications were missing during manual PLMN
  selection.
- Fixed a rare issue where the modem could become unresponsive or crash when receiving deactivation
  commands (AT+CFUN=0, 4, 45, or 46), preventing the deactivation process from completing.
- Fixed an issue where the AT%NCELLMEAS command could become blocked and eventually cause a modem
  instability during extremely long-duration continuous RRC connections.
- Fixed a rare issue that could cause a modem crash when a PDN was deactivated while data handling
  was in progress.
- Fixed a rare issue in measurement configuration handling that could cause a modem crash.
- Improved network search speed with certain SIM subscriptions when the device is roaming in another
  country.
- Fixed an issue where the modem could fail to respond to AT+CFUN activation when a SIM refresh, a
  GNSS request, and a CFUN functional mode change occurred at the same time.
- Fixed an issue where NTN NB-IoT uplink messages could be dropped when the modem was powered off
  immediately after data transmission.
  
*** Limitations
***************
- The AT%NCELLMEAS, AT%ENVEVAL, and AT%CONEVAL commands are not supported in NTN-NB-IoT mode.
- TLS and DTLS
    - Secure socket buffer size is 2kB.
    - Maximum length of DTLS datagram is 1kB.
    - One TLS handshake at a time is supported.
    - Concurrent secure connections
        - Maximum server certificate chain size has a limit of 4kB.
        - Two active connections are supported when serialized DTLS connection exists.
        - Two active connections are supported when any client certificate size is over 1kB.
        - Two active connections are supported when GNSS acquisition is active.
        - Three active connections are supported when client certificate sizes are 1kB or less.
        - Four serialized DTLS connections are supported.
    - Server certificate expiry time is not verified.
    - pkcs#8 is not supported.
    - Maximum number of supported credentials is 32. The actual amount depends on the size of
      credentials as the memory area reserved for credentials may be a limiting factor as well.
    - TLS is not supported when the socket is configured in TCP server mode.
    - The effective user DTLS payload is limited by the link MTU minus significant protocol overhead
      from IP, UDP, DTLS headers, ciphering, and Connection ID. This overhead can amount to several
      hundred bytes, so applications must be designed to manage their payload sizes accordingly to
      prevent data loss.
    - If the TLS socket option for maximum fragment length negotiation is used, the size of the
      DTLS payload in a socket send operation is limited to the negotiated fragment size.
- IP fragmentation and reassembly are not supported.
- It is recommended to free the modem resources by closing unused network sockets and by undefining
  unused PDN connections with AT+CGDCONT.
- Maximum number of raw sockets is 4.
- User plane data is supported in Cat M1 mode only.
- Non-IP Data Delivery (NIDD) feature is verified only for NB-IoT. NIDD for LTE-M is not supported.
- The number of ownership keys is restricted to one. Multiple instances are not allowed.

*** Known Issues
****************
-

*** MD5 checksums
*****************

21746FD.ipc_dfu.signed_2.1.0.ihex
53fd51225606f1c8f3d6e2650d3477a3 (MD5)

firmware.update.image.digest.txt
e7a04bd1bfab208e5f35486427cff856 (MD5)

firmware.update.image.segments.0.hex
340d6b1a8ec78295b97b3107c639867d (MD5)

firmware.update.image.segments.1.hex
a77c4b6e2259833f4b5d19e065e23c5f (MD5)

ipc-dfu_nrf91x1_2.1.0.ihex
53fd51225606f1c8f3d6e2650d3477a3 (MD5)

mfw_nrf9151-ntn_1.0.1-FOTA-TEST_trace-db.json
7c1f54b33f28c59b0bdf56f49ffcf81e (MD5)

mfw_nrf9151-ntn_1.0.1.cbor
f93683833a953ab995ae65205679927c (MD5)

mfw_nrf9151-ntn_1.0.1_trace-db.json
a4020275c0301172a236fea0f2b85d70 (MD5)

mfw_nrf9151-ntn_large_update_from_1.0.1-FOTA-TEST_to_1.0.1.bin
ad2d00c0656afd62d0ac6c6cf149e84e (MD5)

mfw_nrf9151-ntn_large_update_from_1.0.1_to_1.0.1-FOTA-TEST.bin
686562053793dfe30b7064ed101d51ac (MD5)

mfw_nrf9151-ntn_update_from_1.0.0_to_1.0.1.bin
b754ad56534315a4a471acaca6c9185e (MD5)

mfw_nrf9151-ntn_update_from_1.0.1-FOTA-TEST_to_1.0.1.bin
3d622fb5dd6ade5c1aca1783842a99bc (MD5)

mfw_nrf9151-ntn_update_from_1.0.1_to_1.0.1-FOTA-TEST.bin
043c56af6bf016b8f0978a0d4e608d20 (MD5)


*** mfw_nrf9151-ntn_1.0.0
*************************

The mfw_nrf9151-ntn is Cellular IoT and Positioning firmware for the modem subsystem of the nRF9151
LACA A1. It supports 3GPP LTE Release 14 LTE-M and NB-IoT, with specific optional features from
Releases 14 and 15, and selected features of Release 17 Non-Terrestrial Network NTN-NB-IoT. The
firmware also supports GPS L1C/A and QZSS L1C/A positioning.

LTE-M operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 18, 19, 20, 25, 26, 28, 66,
85, and 106.

NB-IoT operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 17, 19, 20, 25, 26, 28, 65,
66, 85, and 106.

E-UTRA band 106 is supported by nRF9151 LACA A1.

NTN-NB-IoT operation is enabled on E-UTRA bands 23, 255, and 256, and is supported by nRF9151 LACA
A1.

This release aligns with v1.0 of the nRF91x1 NTN AT Commands Reference Guide.

It is advisable to use the latest versions of the nRF Connect and nRF Connect Programmer tools.

*** New functionality
*********************
- Enhanced the asynchronous send() operation to provide an additional notification from the modem to
  the application for the actual data delivery result. This combines the existing send with
  MSG_WAITACK functionality with the new result notification.
- Added support for periodic search status start and stop indications using %MDMEV: SEARCH STATUS 3
  and %MDMEV: SEARCH STATUS 4.
- Enhanced the AT%SKYLO command with AT%FEACONF feature ID 7 to enable signal quality checks before
  connection establishment.

*** Changes
***********
- Added RSRQ parameter to the existing AT%XMONITOR command response.
- Removed the AT%CHSELECT command. This functionality is now fully provided by the AT%FREQRANGES
  command.
- Updated the AT%FREQRANGES command functionality.
- Added EUTRA channel (EARFCN) and Physical Cell ID (PCI) parameters to the existing AT%SQP command
  response.

*** Bug fixes
*************
- Implemented multiple fixes and general improvements for handling of cellular profiles used via
  AT%CELLULARPRFL command.
- Fixed an issue where System Information Block 32 (SIB32) data was occasionally not delivered from
  the modem to the application.
- Fixed instability when reading UICC data with the AT%CRSM command.
- Fixed an issue where the modem incorrectly reported a data transmission as successful even if the
  network rejected the Service Request.
- Fixed a modem instability that could occur when a manual NTN PLMN search was started from PSM
  sleep.
- Improved NPDSCH reception when an invalid downlink subframe bitmap is configured.
- Fixed Release Assistance Indication (RAI) to correctly handle the final TCP packet when UDP
  packets are simultaneously transmitted over multiple sockets.
- Fixed the handling of missing locations for blocking AT commands in cases where the application
  has not provided a location using AT%LOCATION, or if the location validity expires during the
  command execution.
- Fixed the handling of the AT%SKYLO configuration feature when cellular profiles are used and the
  system mode is changed to terrestrial LTE-M or NB-IoT.
- Fixed NTN downlink monitoring after an uplink transmission. The modem no longer unnecessarily
  waits for the Round Trip Time (RTT) to expire before resuming downlink monitoring.
- Fixed NVM configuration storage after %POFWARN notification to ensure the active warning is
  cleared when the voltage level is restored.
- Robustness improvements have been implemented to enhance overall stability. These changes address
  issues that could previously lead to unexpected behavior, such as rare modem resets. As a result,
  they contribute to improved service reliability.
- Improved NTN signal level parameter stability for RSRP, RSRQ, and SINR.

*** Limitations
***************
- The AT%NCELLMEAS, AT%ENVEVAL, and AT%CONEVAL commands are not supported in NTN-NB-IoT mode.
- TLS and DTLS
    - Secure socket buffer size is 2kB.
    - Maximum length of DTLS datagram is 1kB.
    - One TLS handshake at a time is supported.
    - Concurrent secure connections
        - Maximum server certificate chain size has a limit of 4kB.
        - Two active connections are supported when serialized DTLS connection exists.
        - Two active connections are supported when any client certificate size is over 1kB.
        - Two active connections are supported when GNSS acquisition is active.
        - Three active connections are supported when client certificate sizes are 1kB or less.
        - Four serialized DTLS connections are supported.
    - Server certificate expiry time is not verified.
    - pkcs#8 is not supported.
    - Maximum number of supported credentials is 32. The actual amount depends on the size of
      credentials as the memory area reserved for credentials may be a limiting factor as well.
    - TLS is not supported when the socket is configured in TCP server mode.
    - The effective user DTLS payload is limited by the link MTU minus significant protocol overhead
      from IP, UDP, DTLS headers, ciphering, and Connection ID. This overhead can amount to several
      hundred bytes, so applications must be designed to manage their payload sizes accordingly to
      prevent data loss.
    - If the TLS socket option for maximum fragment length negotiation is used, the size of the
      DTLS payload in a socket send operation is limited to the negotiated fragment size.
- IP fragmentation and reassembly are not supported.
- It is recommended to free the modem resources by closing unused network sockets and by undefining
  unused PDN connections with AT+CGDCONT.
- Maximum number of raw sockets is 4.
- User plane data is supported in Cat M1 mode only.
- Non-IP Data Delivery (NIDD) feature is verified only for NB-IoT. NIDD for LTE-M is not supported.
- The number of ownership keys is restricted to one. Multiple instances are not allowed.

*** Known Issues
****************
- Applications should ensure that a valid location exists with connected-mode accuracy and
  sufficient remaining validity time before sending the AT+COPS command.

*** MD5 checksums
*****************

21746FD.ipc_dfu.signed_2.1.0.ihex
fffc33ec947988dcffe3c181c0ae2490 (MD5)

firmware.update.image.digest.txt
93d8ab2abd94bbcdc7570692c22ffa30 (MD5)

firmware.update.image.segments.0.hex
c2160ede4c17243bc11a76aa66f46228 (MD5)

firmware.update.image.segments.1.hex
12d86953d693392bd3b225bee4e2f35a (MD5)

ipc-dfu_nrf91x1_2.1.0.ihex
fffc33ec947988dcffe3c181c0ae2490 (MD5)

mfw_nrf9151-ntn_1.0.0-FOTA-TEST_trace-db.json
fb001fe5ee04bc49a358bd52a56bfe6c (MD5)

mfw_nrf9151-ntn_1.0.0.cbor
deb40f132ed6d3ac957f61bc415d8dbd (MD5)

mfw_nrf9151-ntn_1.0.0_trace-db.json
4e138ff7c1cc673df0842b3557552502 (MD5)

mfw_nrf9151-ntn_large_update_from_1.0.0-FOTA-TEST_to_1.0.0.bin
e8e9f3f18b7988cc89ac8202ea3e0148 (MD5)

mfw_nrf9151-ntn_large_update_from_1.0.0_to_1.0.0-FOTA-TEST.bin
7c6a63fb2246e746bdf581a091721acf (MD5)

mfw_nrf9151-ntn_update_from_1.0.0-FOTA-TEST_to_1.0.0.bin
f85f86d026f5214fa204859ca9c455f6 (MD5)

mfw_nrf9151-ntn_update_from_1.0.0_to_1.0.0-FOTA-TEST.bin
71d15ff5e25d85e11bac340a238afc61 (MD5)


*** mfw_nrf9151-ntn_1.0.0-1.alpha
*********************************

The mfw_nrf9151-ntn is Cellular IoT and Positioning firmware for the modem subsystem of the nRF9151
LACA A1. It supports 3GPP LTE Release 14 LTE-M and NB-IoT, with selected optional features from
Releases 14 and 15. It also supports 3GPP Release 17 Non-Terrestrial Network NTN-NB-IoT, as well as
GPS L1C/A and QZSS L1C/A positioning.

LTE-M operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 18, 19, 20, 25, 26, 28, 66,
85, and 106.

NB-IoT operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 17, 19, 20, 25, 26, 28, 65,
66, 85, and 106.

E-UTRA band 106 is supported by nRF9151 LACA A1.

NTN-NB-IoT operation is enabled on E-UTRA bands 23, 255, and 256, and is supported by nRF9151 LACA
A1.

This release aligns with v0.7 of the mfw_nrf9151-ntn AT Commands Reference Guide.

It is advisable to use the latest versions of the nRF Connect and nRF Connect Programmer tools.

*** New functionality
*********************
- Support for non-blocking send and notify type of data transmission with send timeout. Send and
  notify option can be used to monitor socket information when and if user data is transmitted over
  the air interface.
- Support for new socket option for enabling TLS extension maximum fragment length negotiation. This
  extension allows the client to indicate to the server the fragment size it can handle. Maximum
  fragment length extension is available for DTLS. Supported fragment sizes are 512 and 1024 bytes.
  This feature requires corresponding support in the nRF Connect SDK.
- Capability to configure Skylo specific requirements with AT%SKYLO command.
- Enhanced +CEREG notifications for out of service detection. +CEREG: 91 notification may be used by
  applications to identify the situation that no suitable cells are available for normal service.
- Support for applications to configure and receive specific System Information Blocks (SIBs) from
  the cellular network through a standardized AT command interface. This allows applications to
  access network configuration parameters that are broadcast by cell towers. Applications may
  implement NTN discontinuous coverage feature with the information received from this command. This
  feature can be used throufg AT%SIBREQ and AT%SIBCONFIG.
- Added the RSRQ parameter to the AT%XMONITOR command.
- New feature to prevent the modem from staying connected to cells that lack usable connectivity.
  Can be enabled with AT%FEACONF to reduce power consumption.
- Added support for improved Radio Link Failure (RLF) control in NTN-NB-IoT mode, which uses backoff
  timers to prevent unnecessary reconnection attempts and optimize power consumption.
- Added APDU trace support in the public trace database.

*** Changes
***********
- The AT commands AT%XMIPIRFFECTRL, AT%XMIPIRFFECTRL2, AT%MAGPIO, and AT%COEX0 can now be configured
  using E-UTRA band numbers in addition to frequencies.
- Enhanced the AT%LOCATION command to predict the accuracy and timing of the next location update
  required by the modem. This allows the application to implement proactive power-saving strategies,
  such as deactivating GNSS or extending the validity of the current location.

*** Bug fixes
*************
- Enhanced power management resilience to voltage ripple during temperature and supply‑voltage
  extremes, lowering the likelihood of rare modem instability and improving manufacturing yield.
- Resolved an issue where the modem coredump trace service was generating incomplete dump files.
- Fixed a modem instability that could occur when a TCP server connection was reset by the client at
  the exact moment it was being accepted by the application.
- Improved the reliability of switching between terrestrial and non-terrestrial cellular profiles
  using AT%CELLULARPRFL. This fix addresses operational failures that could occur during the
  transition, ensuring the command executes consistently.
- Corrected the AT%XRFTEST command, which no longer fails with an ERROR when testing band 18.

*** Limitations
***************
- The AT%NCELLMEAS, AT%ENVEVAL, and AT%CONEVAL commands are not supported in NTN-NB-IoT mode.
- TLS and DTLS
    - Secure socket buffer size is 2kB.
    - Maximum length of DTLS datagram is 1kB.
    - One TLS handshake at a time is supported.
    - Concurrent secure connections
        - Maximum server certificate chain size has a limit of 4kB.
        - Two active connections are supported when serialized DTLS connection exists.
        - Two active connections are supported when any client certificate size is over 1kB.
        - Two active connections are supported when GNSS acquisition is active.
        - Three active connections are supported when client certificate sizes are 1kB or less.
        - Four serialized DTLS connections are supported.
    - Server certificate expiry time is not verified.
    - pkcs#8 is not supported.
    - Maximum number of supported credentials is 32. The actual amount depends on the size of
      credentials as the memory area reserved for credentials may be a limiting factor as well.
    - TLS is not supported when the socket is configured in TCP server mode.
    - The effective user DTLS payload is limited by the link MTU minus significant protocol overhead
      from IP, UDP, DTLS headers, ciphering, and Connection ID. This overhead can amount to several
      hundred bytes, so applications must be designed to manage their payload sizes accordingly to
      prevent data loss.
    - If the TLS socket option for maximum fragment length negotiation is used, the size of the
      DTLS payload in a socket send operation is limited to the negotiated fragment size.
- IP fragmentation and reassembly are not supported.
- It is recommended to free the modem resources by closing unused network sockets and by undefining
  unused PDN connections with AT+CGDCONT.
- Maximum number of raw sockets is 4.
- User plane data is supported in Cat M1 mode only.
- Non-IP Data Delivery (NIDD) feature is verified only for NB-IoT. NIDD for LTE-M is not supported.
- The number of ownership keys is restricted to one. Multiple instances are not allowed.

*** Known Issues
****************
-

*** MD5 checksums
*****************

21746FD.ipc_dfu.signed_2.1.0.ihex
dc224b551a3049e9ec41ce63fdf90561 (MD5)

firmware.update.image.digest.txt
2c51b0da0f514a8d34d1771e18edc09d (MD5)

firmware.update.image.segments.0.hex
6cd6cf55aaec5800fcf76a54cb48a0b4 (MD5)

firmware.update.image.segments.1.hex
96649a8fd85387c1932f98422befcff9 (MD5)

ipc-dfu_nrf91x1_2.1.0.ihex
dc224b551a3049e9ec41ce63fdf90561 (MD5)

mfw_nrf9151-ntn_1.0.0-1.alpha.cbor
a6a27f55f29ab47ed781eff280c69b2d (MD5)

mfw_nrf9151-ntn_1.0.0-1.alpha_trace-db.json
499f9ea4f229e4d01d75efe6a1e9a814 (MD5)


*** mfw_nrf9151-ntn_0.5.1
*************************

The mfw_nrf9151-ntn is Cellular IoT and Positioning firmware for the modem subsystem of the nRF9151
LACA A1. It supports 3GPP LTE Release 14 LTE-M and NB-IoT, with selected optional features from
Releases 14 and 15. It also supports 3GPP Release 17 Non-Terrestrial Network NTN-NB-IoT, as well as
GPS L1C/A and QZSS L1C/A positioning.

LTE-M operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 18, 19, 20, 25, 26, 28, 66,
85, and 106.

NB-IoT operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 17, 19, 20, 25, 26, 28, 65,
66, 85, and 106.

E-UTRA band 106 is supported by nRF9151 LACA A1.

NTN-NB-IoT operation is enabled on E-UTRA bands 23, 255, and 256, and is supported by nRF9151 LACA
A1.

This release aligns with v0.5 of the mfw_nrf9151-ntn AT Commands Reference Guide.

It is advisable to use the latest versions of the nRF Connect and nRF Connect Programmer tools.

*** New functionality
*********************
-

*** Changes
***********
-

*** Bug fixes
*************
- Fixed SIM readiness reporting during transition from RX-only to normal mode. Previously, readiness
  could be reported prematurely, causing the system to treat the SIM as unavailable and preventing
  procedures from starting.

*** Limitations
***************
- The AT%NCELLMEAS, AT%ENVEVAL, and AT%CONEVAL commands are not supported in NTN mode.
- TLS and DTLS
    - Secure socket buffer size is 2kB.
    - Maximum length of DTLS datagram is 1kB.
    - One TLS handshake at a time is supported.
    - Concurrent secure connections
        - Maximum server certificate chain size has a limit of 4kB.
        - Two active connections are supported when serialized DTLS connection exists.
        - Two active connections are supported when any client certificate size is over 1kB.
        - Two active connections are supported when GNSS acquisition is active.
        - Three active connections are supported when client certificate sizes are 1kB or less.
        - Four serialized DTLS connections are supported.
    - Server certificate expiry time is not verified.
    - pkcs#8 is not supported.
    - Maximum number of supported credentials is 32. The actual amount depends on the size of
      credentials as the memory area reserved for credentials may be a limiting factor as well.
    - TLS is not supported when the socket is configured in TCP server mode.
- IP fragmentation and reassembly are not supported.
- It is recommended to free the modem resources by closing unused network sockets and by undefining
  unused PDN connections with AT+CGDCONT.
- Maximum number of raw sockets is 4.
- User plane data is supported in Cat M1 mode only.
- Non-IP Data Delivery (NIDD) feature is verified only for NB-IoT. NIDD for LTE-M is not supported.
- The number of ownership keys is restricted to one. Multiple instances are not allowed.

*** Known Issues
****************
-

*** MD5 checksums
*****************

21746FD.ipc_dfu.signed_2.1.0.ihex
addf6dc7315a32a9830a4b6ac555de29 (MD5)

firmware.update.image.digest.txt
3ef9051642f8f8389d349b95adfe6ea3 (MD5)

firmware.update.image.segments.0.hex
4568e432ba671b9531be227a2f1098f2 (MD5)

firmware.update.image.segments.1.hex
a0dcc332ab08ac65ac2c0460015b37b0 (MD5)

ipc-dfu_nrf91x1_2.1.0.ihex
addf6dc7315a32a9830a4b6ac555de29 (MD5)

mfw_nrf9151-ntn_0.5.1.cbor
c7f4555fcae7a88234a7c586950f3b35 (MD5)

mfw_nrf9151-ntn_0.5.1_trace-db.json
29ef8ca63159c3d5838506ffb92b787d (MD5)


*** mfw_nrf9151-ntn_0.5.0
*************************

The mfw_nrf9151-ntn is Cellular IoT and Positioning firmware for the modem subsystem of the nRF9151
LACA A1. It supports 3GPP LTE Release 14 LTE-M and NB-IoT, with selected optional features from
Releases 14 and 15. It also supports 3GPP Release 17 Non-Terrestrial Network NTN-NB-IoT, as well as
GPS L1C/A and QZSS L1C/A positioning.

LTE-M operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 18, 19, 20, 25, 26, 28, 66,
85, and 106.

NB-IoT operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 17, 19, 20, 25, 26, 28, 65,
66, 85, and 106.

E-UTRA band 106 is supported by nRF9151 LACA A1.

NTN-NB-IoT operation is enabled on E-UTRA bands 23, 255, and 256, and is supported by nRF9151 LACA
A1.

This release aligns with v0.5 of the mfw_nrf9151-ntn AT Commands Reference Guide.

It is advisable to use the latest versions of the nRF Connect and nRF Connect Programmer tools.

*** New functionality
*********************
- Added the AT%IMEIWRITE command to allow updating the IMEI during device production. IMEI updates
  are disabled after the modem is first activated with AT+CFUN=1 or AT+CFUN=21.
- Added support for creating cellular profiles with AT%CELLULARPRFL, enabling fast, power-efficient
  switching between terrestrial and non-terrestrial networks.
- Added support for EUTRAN LTE-M and NB-IoT band 106.
- A new AT command, AT%ENVEVAL, has been introduced to support evaluation of specific Public Land
  Mobile Networks (PLMNs). When a list of PLMN IDs is provided as a parameter, the modem scans for
  the specified networks, evaluates their presence and signal quality, and reports the results via
  the AT interface for further analysis or decision-making. Feature is not supported in NTN mode.
- Added support for handling the SoftSIM null command (null procedure byte), ensuring reliable
  communication when the SoftSIM signals a processing delay.
- Added support for simplified AT%XRFTEST TX test mode which enables reduced transmitter (TX)
  testing. Full test capabilities remain available in the production test firmware
  (mfw-pti_nrf91x1).
- The TRACE_SYSTEM_WARNING trace event has been added to the public trace database. This indicator
  signals when trace data may be lost due to congestion. In such cases, some trace entries might be
  missing from the resulting PCAP file.
- New feature to prevent the modem from staying connected to cells that lack usable connectivity.
  Can be enabled with %FEACONF to reduce power consumption.

*** Changes
***********
- Added support for a second external MIPI RFFE device.
- Updated configurations for mobile network carrier-specific features and functionalities to enhance
  compatibility.
- Updated the underlying TLS implementation with security improvements.
- Improved Rx-only mode AT+CFUN=2. Supports network search, selection and appropriate notifications
  +CEREG and %MDMEV SEARCH STATUSes, while Rx-only mode is active. Adds support for all
  functionalities and AT commands that do not require transmission capability. Newly adds support
  for AT%NCELLMEAS, and improves performance of AT%CONEVAL in this mode, for example.
- Improved connection reliability when receiving SIB14, the system information block used for access
  barring, from the serving cell.
- Enabled +CMMS visibility in AT+CLAC response.

*** Bug fixes
*************
- Fixed support for the t-Reordering field in the RLC configuration during NB-IoT connection
  reestablishment, enabling NB-IoT Dual HARQ in NTN.
- Fix for a scenario where cell selection was ongoing in secondary access technology and %NCELLMEAS
  was requested at the same time. With unfavorable timing it was possible that modem was stuck after
  executing the %NCELLMEAS.
- Fix for a scenario where network assigned a long T3412 value for device (for example due to a long
  PSM period) and modem did not correctly take it into use. Due to this modem woke up from long PSMs
  too soon.
- Fixed a rare issue where DTLS data packets were not forwarded to the application when more than
  eight DTLS downlink packets were received in a burst.
- Updated the definition of Supported Radio Access Technologies in the PROVIDE LOCAL INFORMATION
  command, aligning with ETSI TS 102.223 Release 14 (previously Release 13).
- Improved robustness of GNSS and LTE interoperability. In some cases with non-optimal application
  behavior, the modem could enter an unrecoverable state.
- Fixed an issue in the Radio Policy Manager where configuration values from the SIM card were not
  always read correctly.
- Fixed an issue that prevented the last TCP packet from being downloaded over BIP connections on
  some UICCs.
- Fixed an issue where, in some cases, the registration status in location status events was not
  reported correctly to the UICC.
- Fixed an issue where earlier failures blocked the UICC OPEN CHANNEL command.
- Fixed an issue that occasionally prevented RAI reporting after TCP closure.
- Improved downlink reception performance for Idle DRX and eDRX through better sleep handling.
- Fixed AT%XRFTEST RSSI result reporting on the GPS band (24).
- Robustness improvements have been implemented to enhance overall stability. These changes address
  issues that could previously lead to unexpected behavior, such as rare modem resets. As a result,
  they contribute to improved service reliability.
- Fixed an issue preventing large SIM profile downloads over a BIP connection.
- Resolved an issue where EPS update type in TAU request was incorrectly periodic updating instead
  of TA updating.
- Improved cell search and Idle eDRX reception performance in certain time-synchronous network
  deployments.
- Improved handling of AT%CONEVAL following AT%NCELLMEAS during PSM, enabling more robust support
  for issuing both commands in parallel.

*** Limitations
***************
- The AT%NCELLMEAS, AT%ENVEVAL, and AT%CONEVAL commands are not supported in NTN mode.
- TLS and DTLS
    - Secure socket buffer size is 2kB.
    - Maximum length of DTLS datagram is 1kB.
    - One TLS handshake at a time is supported.
    - Concurrent secure connections
        - Maximum server certificate chain size has a limit of 4kB.
        - Two active connections are supported when serialized DTLS connection exists.
        - Two active connections are supported when any client certificate size is over 1kB.
        - Two active connections are supported when GNSS acquisition is active.
        - Three active connections are supported when client certificate sizes are 1kB or less.
        - Four serialized DTLS connections are supported.
    - Server certificate expiry time is not verified.
    - pkcs#8 is not supported.
    - Maximum number of supported credentials is 32. The actual amount depends on the size of
      credentials as the memory area reserved for credentials may be a limiting factor as well.
    - TLS is not supported when the socket is configured in TCP server mode.
- IP fragmentation and reassembly are not supported.
- It is recommended to free the modem resources by closing unused network sockets and by undefining
  unused PDN connections with AT+CGDCONT.
- Maximum number of raw sockets is 4.
- User plane data is supported in Cat M1 mode only.
- Non-IP Data Delivery (NIDD) feature is verified only for NB-IoT. NIDD for LTE-M is not supported.
- The number of ownership keys is restricted to one. Multiple instances are not allowed.

*** Known Issues
****************
-

*** MD5 checksums
*****************

21746FD.ipc_dfu.signed_2.1.0.ihex
5217aaa183f7ade8b8879d00da2a3842 (MD5)

firmware.update.image.digest.txt
cd2cbc9183df8b28196eafa617e3eac5 (MD5)

firmware.update.image.segments.0.hex
dcea6738e4ee244f84e9aa60ce2dbfc0 (MD5)

firmware.update.image.segments.1.hex
5c29c0fe7ec75ce05a0d55129f4a271d (MD5)

ipc-dfu_nrf91x1_2.1.0.ihex
5217aaa183f7ade8b8879d00da2a3842 (MD5)

mfw_nrf9151-ntn_0.5.0.cbor
bf8212fd93c831671c4d09979d1cfb66 (MD5)

mfw_nrf9151-ntn_0.5.0_trace-db.json
5574b281056053ea04bbc1c555790fa2 (MD5)


*** mfw_nrf9151-ntn_0.4.2-prealpha
**********************************

The mfw_nrf9151-ntn is Cellular IoT and Positioning firmware for the modem subsystem of the nRF9151
LACA A1. It supports 3GPP LTE Release 14 LTE-M and NB-IoT, with selected optional features from
Releases 14 and 15. It also supports 3GPP Release 17 Non-Terrestrial Network NTN-NB-IoT, as well as
GPS L1C/A and QZSS L1C/A positioning.

LTE-M operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 18, 19, 20, 25, 26, 28, 66,
85, and 106.

NB-IoT operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 17, 19, 20, 25, 26, 28, 65,
66, 85, and 106.

NTN-NB-IoT operation is enabled on E-UTRA bands 23, 255, and 256.

This release aligns with v0.4 of the mfw_nrf9151-ntn AT Commands Reference Guide.

It is advisable to use the latest versions of the nRF Connect and nRF Connect Programmer tools.

*** New functionality
*********************
- Added new options to the AT%XANTCFG command for configuring the nRF9151 antenna input pin with a
  50 ohm termination.

*** Changes
***********
- Improved NTN receiver sensitivity performance.

*** Bug fixes
*************
- Fixed the AT%LOCATION read response, which previously returned invalid data.

*** Limitations
***************
- Dual HARQ is not supported in NTN mode.
- The AT%NCELLMEAS and AT%CONEVAL commands are not supported in NTN mode.
- TLS and DTLS
    - Secure socket buffer size is 2kB.
    - Maximum length of DTLS datagram is 1kB.
    - One TLS handshake at a time is supported.
    - Concurrent secure connections
        - Maximum server certificate chain size has a limit of 4kB.
        - Two active connections are supported when serialized DTLS connection exists.
        - Two active connections are supported when any client certificate size is over 1kB.
        - Two active connections are supported when GNSS acquisition is active.
        - Three active connections are supported when client certificate sizes are 1kB or less.
        - Four serialized DTLS connections are supported.
    - Server certificate expiry time is not verified.
    - pkcs#8 is not supported.
    - Maximum number of supported credentials is 32. The actual amount depends on the size of
      credentials as the memory area reserved for credentials may be a limiting factor as well.
    - TLS is not supported when the socket is configured in TCP server mode.
- IP fragmentation and reassembly are not supported.
- It is recommended to free the modem resources by closing unused network sockets and by undefining
  unused PDN connections with AT+CGDCONT.
- Maximum number of raw sockets is 4.
- User plane data is supported in Cat M1 mode only.
- Non-IP Data Delivery (NIDD) feature is verified only for NB-IoT. NIDD for LTE-M is not supported.
- The number of ownership keys is restricted to one. Multiple instances are not allowed.

*** Known Issues
****************
-

*** MD5 checksums
*****************

21746FD.ipc_dfu.signed_2.1.0.ihex
790f1592779c1b8f7814e92613d5f01d (MD5)

firmware.update.image.digest.txt
62d415190d6a356f6f3f2954fcf4dbb2 (MD5)

firmware.update.image.segments.0.hex
e884954377ae5d81f554c061accf3688 (MD5)

firmware.update.image.segments.1.hex
2b7073059205ba6ce4361a4ae0e5cf6f (MD5)

ipc-dfu_nrf91x1_2.1.0.ihex
790f1592779c1b8f7814e92613d5f01d (MD5)

mfw_nrf9151-ntn_0.4.2-prealpha.cbor
28556117d649102f8f1cd49b7b5f8111 (MD5)

mfw_nrf9151-ntn_0.4.2-prealpha_trace-db.json
2d8e35c8e413f1814795373d1ad4fdd1 (MD5)


*** mfw_nrf9151-ntn_0.4.1-prealpha
**********************************

The mfw_nrf9151-ntn is Cellular IoT and Positioning firmware for the modem subsystem of the nRF9151
LACA A1. It supports 3GPP LTE Release 14 LTE-M and NB-IoT, with selected optional features from
Releases 14 and 15. It also supports 3GPP Release 17 Non-Terrestrial Network NTN-NB-IoT, as well as
GPS L1C/A and QZSS L1C/A positioning.

LTE-M operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 18, 19, 20, 25, 26, 28, 66,
85, and 106.

NB-IoT operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 17, 19, 20, 25, 26, 28, 65,
66, 85, and 106.

NTN-NB-IoT operation is enabled on E-UTRA bands 23, 255, and 256.

This release aligns with v0.4 of the mfw_nrf9151-ntn AT Commands Reference Guide.

It is advisable to use the latest versions of the nRF Connect and nRF Connect Programmer tools.

*** New functionality
*********************
-

*** Changes
***********
-

*** Bug fixes
*************
- Fine-tuned the Qout limit handling for Non-Terrestrial Network (NTN) connections to improve
  connection stability and prevent premature link degradation under specific signal conditions.
- Resolved an issue that could cause unexpected connection breaks during Connected-mode DRX. The fix
  improves overall connection reliability by preventing internal process conflicts.

*** Limitations
***************
- Dual HARQ is not supported in NTN mode.
- The AT%NCELLMEAS and AT%CONEVAL commands are not supported in NTN mode.
- TLS and DTLS
    - Secure socket buffer size is 2kB.
    - Maximum length of DTLS datagram is 1kB.
    - One TLS handshake at a time is supported.
    - Concurrent secure connections
        - Maximum server certificate chain size has a limit of 4kB.
        - Two active connections are supported when serialized DTLS connection exists.
        - Two active connections are supported when any client certificate size is over 1kB.
        - Two active connections are supported when GNSS acquisition is active.
        - Three active connections are supported when client certificate sizes are 1kB or less.
        - Four serialized DTLS connections are supported.
    - Server certificate expiry time is not verified.
    - pkcs#8 is not supported.
    - Maximum number of supported credentials is 32. The actual amount depends on the size of
      credentials as the memory area reserved for credentials may be a limiting factor as well.
    - TLS is not supported when the socket is configured in TCP server mode.
- IP fragmentation and reassembly are not supported.
- It is recommended to free the modem resources by closing unused network sockets and by undefining
  unused PDN connections with AT+CGDCONT.
- Maximum number of raw sockets is 4.
- User plane data is supported in Cat M1 mode only.
- Non-IP Data Delivery (NIDD) feature is verified only for NB-IoT. NIDD for LTE-M is not supported.
- The number of ownership keys is restricted to one. Multiple instances are not allowed.

*** Known Issues
****************
-

*** MD5 checksums
*****************

21746FD.ipc_dfu.signed_2.1.0.ihex
9935fc080ae8f3c006eaa8d417c65fcd (MD5)

firmware.update.image.digest.txt
e72c8bbfdd1a1c2777158b06dd1aab6a (MD5)

firmware.update.image.segments.0.hex
a143fd1c1e2410edd0289e52a146cb74 (MD5)

firmware.update.image.segments.1.hex
275c306b3f6cc8a2dc2a529ac9956186 (MD5)

ipc-dfu_nrf91x1_2.1.0.ihex
9935fc080ae8f3c006eaa8d417c65fcd (MD5)

mfw_nrf9151-ntn_0.4.1-prealpha.cbor
b608e388660472c6e0e7fa7fec4e9374 (MD5)

mfw_nrf9151-ntn_0.4.1-prealpha_trace-db.json
b2f9782db0d497bcb7856cbed44a6e54 (MD5)


*** mfw_nrf9151-ntn_0.4.0-prealpha
**********************************

The mfw_nrf9151-ntn is Cellular IoT and Positioning firmware for the modem subsystem of the nRF9151
LACA A1. It supports 3GPP LTE Release 14 LTE-M and NB-IoT, with selected optional features from
Releases 14 and 15. It also supports 3GPP Release 17 Non-Terrestrial Network NTN-NB-IoT, as well as
GPS L1C/A and QZSS L1C/A positioning.

LTE-M operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 18, 19, 20, 25, 26, 28, 66,
85, and 106.

NB-IoT operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 17, 19, 20, 25, 26, 28, 65,
66, 85, and 106.

NTN-NB-IoT operation is enabled on E-UTRA bands 23, 255, and 256.

This release aligns with v0.4 of the mfw_nrf9151-ntn AT Commands Reference Guide.

It is advisable to use the latest versions of the nRF Connect and nRF Connect Programmer tools.

*** New functionality
*********************
- Added RF operation support for Non-Terrestrial Network (NTN) bands 23, 255, and 256.
- Introduced preliminary support for NB-IoT over NTN, enabling connectivity via satellite-based
  infrastructure.
- Added support for EUTRAN LTE-M and NB-IoT band 106.
- Introduced a new %MDMEV: DETECTED COUNTRY <MCC> notification to provide additional information
  about the device’s current location, enhancing coarse location awareness based on the detected
  MCC.
- Introduced a new +CEREG <stat> value 91, indicating that no suitable cell is available in the
  current system mode. This can be used to trigger a switch between terrestrial and non-terrestrial
  service.
- Added support for reading signal quality parameters and transmission statistics using the AT%SQP
  and AT%DATASTAT commands.
- Added support for handling network rejection with cause #78 ("PLMN not allowed to operate at the
  present UE location") in NTN mode.
- Introduced the AT%LOCATION command to set the device’s geographical location for the NTN modem.
- Added the AT%CHSELECT command to allow selection of a specific frequency or a specific cell on a
  given frequency.
- Introduced a new option in AT%FEACONF to configure the device for operation where all transactions
  are expected to be initiated by the device.
- Added support for simplified AT%XRFTEST TX test mode which enables transmitter (TX) testing. Full
  test capabilities remain available in the production test firmware (mfw-pti_nrf91x1).
- Introduced Skylo-specific proprietary optimizations.
- Added support for downlink channel quality reporting in Msg3 for the anchor carrier.
- Added support for serving cell idle mode measurement reporting.
- Added support for handling the SoftSIM null command (null procedure byte), ensuring reliable
  communication when the SoftSIM signals a processing delay.

*** Changes
***********
- Improved PLMN search and selection for NTN.
- Replaced AT%XCOUNTRYDATA with AT%FREQRANGES. When configured, this feature enables faster network
  search.
- Improved Rx-only mode AT+CFUN=2. Supports network search, selection and appropriate notifications
  +CEREG and %MDMEV SEARCH STATUSes, while Rx-only mode is active. Adds support for all
  functionalities and AT commands that do not require transmission capability. Newly adds support
  for AT%NCELLMEAS, and improves performance of AT%CONEVAL in this mode, for example.
- Improved performance and accuracy of Doppler shift calculation.
- Updated %MDMEV: INVALID BAND CONFIGURATION notification with a new NTN-specific parameter.
- Updated AT+COPS, AT+CEDRXS, +CEREG, and %XMONITOR to support NTN.
- Updated AT%XBANDLOCK with a new parameter to support band numbers above 88.
- Updated AT%XSYSTEMMODE with a new parameter to support NTN mode.
- Improved connection reliability when receiving SIB14, the system information block used for access
  barring, from the serving cell.
- Improved cell search and Idle eDRX reception performance in certain time-synchronous network
  deployments.
- Updated underlying TLS implementation to include security and stability improvements.

*** Bug fixes
*************
- Various fixes to improve NTN service reliability and performance.
- Corrected NTN uplink timing advance adjustment.
- Improved stability when handling simultaneous AT%NCELLMEAS and AT%CONEVAL AT commands.
- Fixed an issue with HFXO clock control in sleep modes. Improves clock accuracy during very short
  sleep periods.
- Fixed an issue with UICC clock stop behavior.
- Fixed an issue with %XRFTEST RX GPS band RSSI measurements, which previously reported invalid
  values.
- Fixed an issue preventing large SIM profile downloads over a BIP connection.

*** Limitations
***************
- Dual HARQ is not supported in NTN mode.
- The AT%NCELLMEAS and AT%CONEVAL commands are not supported in NTN mode.
- TLS and DTLS
    - Secure socket buffer size is 2kB.
    - Maximum length of DTLS datagram is 1kB.
    - One TLS handshake at a time is supported.
    - Concurrent secure connections
        - Maximum server certificate chain size has a limit of 4kB.
        - Two active connections are supported when serialized DTLS connection exists.
        - Two active connections are supported when any client certificate size is over 1kB.
        - Two active connections are supported when GNSS acquisition is active.
        - Three active connections are supported when client certificate sizes are 1kB or less.
        - Four serialized DTLS connections are supported.
    - Server certificate expiry time is not verified.
    - pkcs#8 is not supported.
    - Maximum number of supported credentials is 32. The actual amount depends on the size of
      credentials as the memory area reserved for credentials may be a limiting factor as well.
    - TLS is not supported when the socket is configured in TCP server mode.
- IP fragmentation and reassembly are not supported.
- It is recommended to free the modem resources by closing unused network sockets and by undefining
  unused PDN connections with AT+CGDCONT.
- Maximum number of raw sockets is 4.
- User plane data is supported in Cat M1 mode only.
- Non-IP Data Delivery (NIDD) feature is verified only for NB-IoT. NIDD for LTE-M is not supported.
- The number of ownership keys is restricted to one. Multiple instances are not allowed.

*** Known Issues
****************
-

*** MD5 checksums
*****************

21746FD.ipc_dfu.signed_2.1.0.ihex
8a09eeda37db7f5caf9a2ad38afe2434 (MD5)

firmware.update.image.digest.txt
7627f0ec1d5bda8f067774caeeec0837 (MD5)

firmware.update.image.segments.0.hex
2e9d741ce1fec5774d82c02855221426 (MD5)

firmware.update.image.segments.1.hex
4bbe4fb161fd30c65d1b1fbe8a50c4d9 (MD5)

ipc-dfu_nrf91x1_2.1.0.ihex
8a09eeda37db7f5caf9a2ad38afe2434 (MD5)

mfw_nrf9151-ntn_0.4.0-prealpha.cbor
abc1c913f827959d96dffa2350318fc5 (MD5)

mfw_nrf9151-ntn_0.4.0-prealpha_trace-db.json
85e3e16cf52470ceef19c711eb2f6db7 (MD5)


*** mfw_nrf91x1_2.0.2
*********************

The mfw_nrf91x1 is Cellular IoT and Positioning firmware for modem subsystem of nRF9131 LACA A0,
nRF9151 LACA A0, and nRF9161 LACA A0 SiP modules. It supports 3GPP LTE release 14 LTE-M and NB-IoT
standards, selected optional 3GPP LTE release 14 and 15 features, GPS L1C/A and QZSS L1C/A
positioning.

LTE-M operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 18, 19, 20, 25, 26, 28, 66
and 85.

NB-IoT operation is enabled on E-UTRA bands 1, 2, 3, 4, 5, 8, 12, 13, 17, 19, 20, 25, 26, 28, 65, 66
and 85.

This release aligns with v1.2 of the nRF91x1 Cellular AT Commands Reference Guide.

It is advisable to use the latest versions of the nRF Connect and nRF Connect Programmer tools.

*** New functionality
*********************
- Added a socket option to postpone IPv6 refresh until the completion of Power Saving Mode (PSM),
  enhancing power consumption efficiency. This feature requires support from the nRF Connect SDK.
- Introduced new UICC power-saving options, configurable through the AT%UICCPOWERSAVE command, to
  improve power efficiency.
- New feature allowing applications to define permitted or restricted networks for modem
  connections, providing greater control over connectivity. Configurable through the AT%PALL
  command.
- Added the %RAI unsolicited notification to indicate when RAI is possible for the ongoing cellular
  connection.
- The AT%POWERCLASS command now supports both read and write options, allowing updates to the device
  power class. Additionally, support has been added for locking the power class after production.
- Added support for the TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 cipher suite, enabling stronger
  encryption for secure communications.
- Enabled the creation of self-signed client certificates and private keys using the AT%KEYGEN
  command.
- Added a new option in AT%FEACONF to deactivate the UICC when no cells are found in the most recent
  network scan. This option resolves an issue where the modem repeatedly initiated unnecessary PLMN
  searches following a SIM profile change through SIM refresh, resulting in more frequent searches
  than specified by the periodic search configuration. Recommended for enhancing power consumption
  efficiency.

*** Changes
***********
- Reading of certificates longer than 4096 bytes is prevented.
- Improved the +CGEV: RESTR notification to include the remaining restriction duration, providing
  better application awareness of network restrictions.
- In addition to existing recovery to re-try attach procedure with IMSI, the modem now temporarily
  excludes unresponsive networks for increasing durations if initial recovery fails, improving
  connection stability and power consumption efficiency.
- Updated configurations for mobile network carrier-specific features and functionalities to enhance
  compatibility and performance.
- Implemented minor improvements to reduce current consumption in NB-IoT eDRX mode.

*** Bug fixes
*************
- Resolved an issue where the injection order of QZSS assistance data elements affected QZSS
  assistance ephemeris usage.
- Improved detection and mitigation of GNSS location outliers, enhancing positional accuracy.
- Increased GNSS receiver tolerance for time assistance errors greater than three seconds.
- Improved reliability for DTLS connection setup when PDN connection is deactivated during DTLS
  handshake.
- Fixed an issue where SIM refresh was not performed due to missing local time.
- Fixed a rare issue where simultaneous mobile-originated and mobile-terminated SMS could cause the
  modem to become unresponsive.
- Fixed an issue where issuing the AT+CFUN=4 command alongside mobile-terminated SMS blocked
  subsequent mobile-terminated SMS reception.
- Improved validation of certificates stored using the AT%CMNG command.
- Enhanced reliability in modem socket API messaging.
- Resolved an issue where the +CGEV: NW DEACT event was not sent when the network deactivated an
  additional PDN.
- Fixed an issue where the channel status "Link dropped" event was not sent to the UICC.
- Updated the content of terminal profile concerning Provide Local Information (NMR) support.
- Improved processing of EF-LOCI and EF-EPSLOCI during SIM refresh.
- Fixed an issue where concurrent system synchronization and GNSS activation caused subsequent TLS
  connections to fail.
- Resolved a scenario where the modem selected the incorrect system (LTE-M/NB-IoT) after FOTA or
  high-priority GNSS usage.
- Resolved an issue where primary system searches failed to resume as expected after receiving a
  network rejection.
- Ensured accurate registration status reporting in +CEREG when the device is in limited service
  within a forbidden tracking area.
- Fixed an issue where the modem could not register on a cell due to rare conflicts between LTE and
  GNSS operations.
- Resolved an issue where PLMN selection, triggered by a change in network selection mode (AT+COPS),
  sometimes failed to complete as expected.
- Fixed an issue where manual network selection with AT+COPS caused the modem to halt in certain
  situations.
- Fixed an issue where PLMN selection did not complete successfully in both systems even when both
  LTE systems were active.
- Fixed instability in AT%CONEVAL. In rare cases, the AT%CONEVAL report was missing.
- Improved PDN handling for non-IP data types.
- Resolved issue with CP data handling when changing system modes.
- Resolved an issue with System Information (SI) validity verification before RRC connection
  establishment when the eDRX cycle length exceeds the modification period.
- Reduced stopping time for the AT%NCELLMEAS operation to address occasional delays observed.
- Fixed handling of DL-CCCH and DL-CCCH-NB message reception, enhancing stability.
- Fixed handling of received DL-BCCH-SCH messages carrying SIB1 or SI information, enhancing
  stability.
- Improved packet reception performance with NB-IoT NB2.
- Fixed an issue where cells were incorrectly excluded when fractional nB Paging parameters were
  used.

*** Limitations
***************
- TLS and DTLS
    - Secure socket buffer size is 2kB.
    - Maximum length of DTLS datagram is 1kB.
    - One TLS handshake at a time is supported.
    - Concurrent secure connections
        - Maximum server certificate chain size has a limit of 4kB.
        - Two active connections are supported when serialized DTLS connection exists.
        - Two active connections are supported when any client certificate size is over 1kB.
        - Two active connections are supported when GNSS acquisition is active.
        - Three active connections are supported when client certificate sizes are 1kB or less.
        - Four serialized DTLS connections are supported.
    - Server certificate expiry time is not verified.
    - pkcs#8 is not supported.
    - Maximum number of supported credentials is 32. The actual amount depends on the size of
      credentials as the memory area reserved for credentials may be a limiting factor as well.
    - TLS is not supported when the socket is configured in TCP server mode.
- IP fragmentation and reassembly are not supported.
- It is recommended to free the modem resources by closing unused network sockets and by undefining
  unused PDN connections with AT+CGDCONT.
- Maximum number of raw sockets is 4.
- User plane data is supported in Cat M1 mode only.
- Non-IP Data Delivery (NIDD) feature is verified only for NB-IoT. NIDD for LTE-M is not supported.
- The number of ownership keys is restricted to one. Multiple instances are not allowed.

*** Known Issues
****************
-

*** MD5 checksums
*****************

21746FD.ipc_dfu.signed_2.1.0.ihex
f456c26dc7e657566c0db5a5338b983b (MD5)

firmware.update.image.cbor
023397f2d80ffd82b37254410904fd8f (MD5)

firmware.update.image.digest.txt
d2663ac01e95ebe0371e4b729d153877 (MD5)

firmware.update.image.segments.0.hex
eb290bbb668d2211793989251ebeb7b3 (MD5)

firmware.update.image.segments.1.hex
5f21abbf42a8be84ad33c9b599e4dc36 (MD5)

ipc-dfu_nrf91x1_2.1.0.ihex
f456c26dc7e657566c0db5a5338b983b (MD5)

mfw_nrf91x1_2.0.2.cbor
023397f2d80ffd82b37254410904fd8f (MD5)

mfw_nrf91x1_2.0.2-FOTA-TEST_trace-db.json
e023428753c7e9d199733cb3f3be6766 (MD5)

mfw_nrf91x1_2.0.2_trace-db.json
a334bcb8b62b10281e6f4b4e78e4b8fc (MD5)

mfw_nrf91x1_large_update_from_2.0.2-FOTA-TEST_to_2.0.2.bin
37e35327f876b9f97815ab7b62e4d89f (MD5)

mfw_nrf91x1_large_update_from_2.0.2_to_2.0.2-FOTA-TEST.bin
829fbb2c4fc159c061b2af930f1d6c08 (MD5)

mfw_nrf91x1_update_from_2.0.1_to_2.0.2.bin
185502b7e9e19c999797416238293a2a (MD5)

mfw_nrf91x1_update_from_2.0.2-FOTA-TEST_to_2.0.2.bin
79245db014fd96b91bd58bc7156f9580 (MD5)

mfw_nrf91x1_update_from_2.0.2_to_2.0.2-FOTA-TEST.bin
5ef92bf03344dbdb484a3eb56f5491ec (MD5)
