ThingPark Enterprise SaaS changelog
This page references all the changes included in ThingPark Enterprise SaaS release 8.1, split per maintenance release version.
It includes new features, technical improvements and issues (bugs) resolved. More details about new features and technical improvements are also available in New features and Other technical improvements sections.
Release 8.1.8
New features
| ID | Summary |
|---|---|
| RDTP-25551 | Support the LRC-OSS interface in TPE-SaaS (over kafka) |
| RDTP-25947 | Allow deactivating IoT-Flow at subscription level |
Other technical improvements
| ID | Summary |
|---|---|
| RDTP-25956 | Integrate the Senet gateway agent with ThingPark (PHASE1) |
| RDTP-26014 | MIC computation adaptation for specific devices |
| RDTP-26050 | Support UL JSON formatters for Senet and LoRaWAN Portal |
| RDTP-26133 | Report the VendorID in Usage Details Records (UDRs) |
| RDTP-26127 | Report the ISM Band over the tunnel interface |
| RDTP-26158 | Allow running multiple instances of the LNS BRIDGE |
| RDTP-26045 | Add a trace gauge in LRC metrics |
| RDTP-26042 | Logging LRC trace events |
Resolved issues
| ID | Summary |
|---|---|
| RDTP-26141 | DESC: A latency at message processing could be observed (especially in Roaming context). FIX: Performance optimizations at Network Server level |
| RDTP-26053 | DESC: (Sagemcom and Semtech packet forwarder) RFRegion update is not taken into account by the LNS FIX: Bug fixed |
| RDTP-26052 | DESC: (Sagemcom and Semtech packet forwarder) With asymmetric RFRegions (like US915), the LNS uses the same frequency as uplink instead of the RFRegion DLFrequency FIX: Bug fixed |
| RDTP-26246 | DESC: A device tag association is not completely removed with a GUI mass-import. FIX: Tag could be fully removed through GUI mass-import. |
| RDTP-26171 | DESC: The User Action Logs calendar use is not user friendly. FIX: UI experience enhanced |
Known issues and limitations
None
Release 8.1.7
New features
| ID | Summary |
|---|---|
| RDTP-25954 | Support basic MQTT connections over the tunnel interface |
| RDTP-26039/26095 | Enrichment of the device administrative information |
Other technical improvements
| ID | Summary |
|---|---|
| RDTP-25955 | Support UL JSON formatters for Everynet LNS |
Resolved issues
| ID | Summary |
|---|---|
| RDTP-25916 | DESC: Subscriber UAL export fails when two filters are used. FIX: Allow to use multiple filters when exporting Subscriber UAL. |
| RDTP-26067 | DESC: No altitude reported in OSS API for base station. FIX: Report altitude in OSS API for base station. |
| RDTP-23725 | DESC: Special characters in email address prevent from creating subscriber in smp user interface. FIX: Update of the regex for checking allowed characters. |
Known issues and limitations
None
Release 8.1.6
New features
Other technical improvements
| ID | Summary |
|---|---|
| RDTP-25925 | Support SessionKeyID to integrate with external Join Servers |
Resolved issues
| ID | Summary |
|---|---|
| RDTP-25873 | DESC: Remaining translation issues. FIX: Correct the last occurrences on spanish, italian, and also japanese. |
| RDTP-25738 | DESC: Hexadecimal MAC value 0x4401ffffffff is wrongly detected as malformed. FIX: Hexadecimal mac value 0x4401ffffffff is now accepted and decoded. |
| RDTP-25553 | DESC: AccessCode returned in plain text in error message after an http get request using oss api. FIX: Remove AccessCode token in plain text from error message. |
Known issues and limitations
None
Release 8.1.5
New features
| ID | Summary |
|---|---|
| RDTP-25924 | Support Semtech UDP packet forwarder (restricted to migrating legacy gateways to ThingPark) |
Other technical improvements
| ID | Summary |
|---|---|
| RDTP-25734 | [LoRaWAN Relays] Add serving relay to the packet metadata even in direct link |
| RDTP-26031 | System host upgrade (CVE fixes) |
| RDTP-25848 | Update of some images to incorporate their latest security patches |
Resolved issues
| ID | Summary |
|---|---|
| RDTP-25835 | DESC: Devices stop communicating after AS modification after mass update operation. FIX: Prevent LRC device context from being cleared. |
| RDTP-25885 | DESC: Consumer lag on twa prevents LRR report from being processed quickly. FIX: Twa-ran does not process the malformed message and directly continues with the next one. |
| RDTP-25942 | DESC: Basics Station remote ssh issue on close session. FIX: Web socket is now correctly handled. |
| RDTP-25865 | DESC: XML parsing issue on device provisioning. FIX: Field that may contain a & character are correctly escaped. |
| RDTP-25803 | DESC: RFRegion download on Basics Station fails. FIX: Parsing issue has been corrected. |
| RDTP-25778 | DESC: Username label should not be present on TPE SaaS login screen. FIX: Username label has been removed. |
| RDTP-25737 | DESC: Translation issue on unified portal. FIX: Drivers is used instead of Chauffeurs. |
| RDTP-25722 | DESC: During mass import, the ignored csv lines are added in UALs with error code. FIX: The ignored csv lines are no more added in UALs. |
| RDTP-25714 | DESC: Warning in twa-dev logs when processing RF probe messages. FIX: Twa-dev does not check mongoDB anymore when processing RF probe messages. |
| RDTP-25691 | DESC: SQL concurrent access when creating gateways through API. FIX: Concurrent access is now coorectly handled. |
| RDTP-25649 | DESC: Exception is raised when we try to ack all alarms of a base station using API. FIX: API has been corrected and no more exception is raised. |
| RDTP-25503 | DESC: Cannot filter radio metrics like ESP/RSSI per base station. FIX: Base station that receive RF probe messages are now available. |
| RDTP-25740 | DESC: Exception occurred on the Keycloak server while retrieving the access code. FIX: Exception is catched and an error message is presented accordingly. |
Known issues and limitations
None
Release 8.1.4
New features
| ID | Summary |
|---|---|
| RDTP-23900 | [LoRaWAN Relays] Implement ExtendedNotifyNewEndDeviceReq/Ans MAC commands to mitigate DevAddr collision |
Other technical improvements
None
Resolved issues
| ID | Summary |
|---|---|
| RDTP-25664 | DESC: [Basics Station] Downlink towards class B device are rejected by LRC. FIX: Downlink are no more rejected in that case. |
| RDTP-25636 | DESC: [Basics Station] Gateway remains connected to LRC whereas it has been stopped. FIX: Keep-alive mechanism has been implemented to detect such case. |
| RDTP-25562 | DESC: For class C device, applicative downlink is sent before the completion of the join procedure. FIX: LRC wait for join procedure completion, applicative downlink are rejected if not ready. |
| RDTP-25564 | DESC: Device alarm on "No uplink activity" disappears after upgrade to TP v8.1.2. FIX: Device alarm is now present. |
| RDTP-25271 | DESC: BS connection status alarm doesn’t support delay values superior to 900 seconds. FIX: Extend the maximum allowed delay to 24h. |
| RDTP-24281 | DESC: Create device endpoint is triggered with async method even if we try to deactivate it. FIX: Create device endpoint can now be used in sync or async method inline with the documentation. |
| RDTP-25105 | DESC: Exporting the Packet History from UI does not include the encoded payload field. FIX: Encoded payload field is now available in the CSV export. |
| RDTP-25565 | DESC: EUI_Location messages are dropped when LAT/LONG values are invalid. FIX: A post check is executed on lat/lon field to adapt in a correct value if needed. |
| RDTP-25694 | DESC: WLogger does not decode correctly RelayConfReq MAC command. FIX: RelayConfReq MAC command is now correctly decoded in WLogger. |
| RDTP-25552 | DESC: Sorting the base Station list by RF Region displays a persistent error. FIX: The sort option has been removed for the column RF Region. |
| RDTP-25484 | DESC: Using the RF scan tool, the allowed frequency limits are not aligned between GUI and LRR. FIX: The range is now correctly aligned. |
Known issues and limitations
None
Release 8.1.3
New features
| ID | Summary |
|---|---|
| RDTP-22222 | Bulk update of devices via csv import |
| RDTP-18798 | Allow associating devices with tags & domains during bulk provisioning |
| RDTP-23703 | Seamless device migration from other platforms |
Other technical improvements
| ID | Summary |
|---|---|
| RDTP-25290 | Cursor-based pagination is now available when using OSS-API to retrieve the base station list, as well as device and base station alarms. This pagination mode is more scalable and efficient than offset-based pagination. To learn more, see Control plane API. |
| RDTP-25177 | Report the aggregated downtime duration when the base station alarm 102 (BS connection loss) is cleared. The downtime is added in the additional info: addInfo provides the downtime in minutes, whereas addInfo2 provides the downtime in seconds. |
| RDTP-24650 | Enhanced interaction between flow control of late uplink packets and passive roaming |
| RDTP-24853 | Enhance the UI with classification (excellent, good, fair, poor) about cellular & WiFi statistics for the backhaul interface of each base station |
| RDTP-24968 | Add the BS coordinates when exporting the base station list from the user interface |
| RDTP-23938 | Quick scan of the csv import file to report syntax errors before creating the new devices |
| RDTP-18798 | Allow associating a device with tags during unitary provisioning |
Resolved issues
| ID | Summary |
|---|---|
| RDTP-25372 | DESC: LRR fine timestamps are not corrected by the LRC when they are in the future or too old. FIX: LRC corrects the wrong LRR fine timestamps, in the same way as coarse timestamps. |
| RDTP-25283 | DESC: [LoRaWAN relays] The same downlink counter may be wrongly used across several packets in relay mode. FIX: Fix the LRC behavior when a device is served by relays + direct base stations, to avoid wrong DL FCnt management. |
| RDTP-23489 | DESC: [LoRaWAN relays] Endless Request/Answer loops in case of command rejection FIX: Extend the retransmission optimization behavior to relay-specific MAC commands, in the same way as other commands. |
| RDTP-25468 | DESC: [LoRaWAN relays] Second WOR channel may be activated while EndDeviceConfReqMAC command is not yet supported. FIX: Update the user interface to prevent activating the second WOR channel. |
| RDTP-25308 | DESC: Device tag removal could take time to complete. FIX: Optimization of the associated SQL slow query. |
| RDTP-25268 | DESC: The clearing condition of old base station alarms 104 and 105 is never fulfilled due to low traffic volume. FIX: Old alarms raised before the activation of anti-flapping mechanism (see RDTP-18707 are automatically deleted when upgrading to TPE-SaaS 8.1.3. |
| RDTP-25536 | DESC: 3G RSCP, 4G RSRP and WiFi RSSI bar icons and stats are not homogeneous. FIX: Use same classification rules in bar icons and backhaul stats for 3G RSCP, 4G RSRP and WiFi RSSI. |
| RDTP-25219 | DESC: An error is raised when upgrading base station with OSS-API. FIX: Make optional the guilty parameter ossContext in OSS-API related endpoint. |
| RDTP-25147 | DESC: WLogger filtering using date/time sometimes fails. FIX: Prevent filtering by date/time when there is no filter applied for the device or the LRR. |
| RDTP-25104 | DESC: Translation issues may appear in the user portal. FIX: Improve translation mechanism to avoid such occurrences. |
| RDTP-24969 | DESC: Time zone inconsistency is present in the portal at base station traffic history graph level. FIX: Make it homogeneous by showing time zone at browser time. |
| RDTP-24939 | DESC: A user with domain restrictions can delete a device not matching his domain restrictions using mass import. FIX: Domain restriction apply now correctly when using mass import. |
| RDTP-24938 | DESC: Notifications are not filtered according to domain restrictions. FIX: Apply domain restrictions to the notifications when using web socket. |
| RDTP-24309 | DESC: Hourly scale prevents showing anything on statistic chart. FIX: Fix the time zone management. |
| RDTP-25266 | DESC: A 204 code is returned when deleting a BS that does not exist instead of a 404 " does not exist." FIX: Use the correct error code 404. |
| RDTP-25388 | DESC: A base station may receive the uplinks of its own RF probe. FIX: Even if a BS reports uplink packets corresponding to its own RF probe, they are filtered out by the network server and do not disturb the Packet Error Rate (PER) statistics of this probe. |
| RDTP-25095 | DESC: Device Model list is incomplete. FIX: Pagination has been implemented with a default value of 100. |
| RDTP-25451 | DESC: Use of deprecated API endpoint when trying to activate class B on Basics Station and bad timesync message management. FIX: OSS API documentation has been modified accordingly and timesync message is now correctly handled. |
Known issues and limitations
None
Release 8.1.2
New features
Other technical improvements
| ID | Summary |
|---|---|
| RDTP-23884 | Allow disabling tag suggestions for users having domain restrictions |
Resolved issues
| ID | Summary |
|---|---|
| RDTP-25103 | DESC: Custom CA certificate is missing since LRC is running in a container. FIX: Allow to customize CA certificate at host level for HTTP AS. |
| RDTP-25176 | DESC: Service profile used for RF probes should support geolocation. FIX: Activate geolocation in the service profile by default. |
| RDTP-25099 | DESC: [Relay] MAC command CtrUplinkListAns is shown empty in WLogger. FIX: CtrUplinkListAns is now correctly reported by LRC and displayed in WLogger |
| RDTP-25046 | DESC: Downlink with MAC command is not displayed in packets history / last MAC commands. FIX: Update the downlink details sent by the LRC to correctly report the mac command availability. |
| RDTP-24891 | DESC: Basics station connection terminated by LNS bridge. FIX: IEC connection management has been strengthened to avoid such behavior. |
| RDTP-24717 | DESC: Base Station disconnection / reconnection timestamps are not accurate for alarm 102. FIX: Time management around alarm creation and clearing has been improved. |
| RDTP-25125 | DESC: Weak security when changing support password. FIX: Security enforcement at WebUI and API levels. |
| RDTP-25092 | DESC: Redirecting to WLogger does not allow filtering by packet type. FIX: Filtering by packet type is now possible. |
| RDTP-25082 | DESC: [Multicast group] the base station tag selection widget validate empty tag. FIX: Only existing multicast tags are authorized. |
| RDTP-25011 | DESC: Multicast downlinks do not work when frequency has more than 3 decimals. FIX: Support of six digits after the decimal point for channel frequency. |
| RDTP-25185 | DESC: String definition missing in gateway alarm configuration when trying to update “Connection status alarm” to 0 for a base station. FIX: The following definition has been added “Value must be at least 1 second”. |
| RDTP-24715 | DESC: Unable to update an existing custom device profile. FIX: Information in the description of profile is presented if non-authorized HTML tags are used and would prevent from saving it. |
Known issues and limitations
| ID | Summary |
|---|---|
| RDTP-23489 | [LoRaWAN relays] Endless Request/Answer loops in case of command rejection |
Release 8.1.1
New features
| ID | Summary |
|---|---|
| RDTP-24685 | Ability to download user action logs from the user interface |
Other technical improvements
| ID | Summary |
|---|---|
| RDTP-24409 | Swagger UI with try-it-out for the Tunnel Interface Downlink API |
| RDTP-24725 | Migrate Google Maps V3 integration to handle deprecated APIs |
| RDTP-25014 | Third-party component upgrade (Kafka, MongoDB and MariaDB) to incorporate the latest security patches |
Resolved issues
| ID | Summary |
|---|---|
| RDTP-24545 | DESC: The result of asynchronous operations is not logged in user action logs. FIX: Enrich the user action logs with the result of all the asynchronous write actions such as bulk addition of devices via csv import. |
| RDTP-24692 | DESC: Packet history is not reset upon resuming a suspended device. FIX: When a suspended device is resumed, the packet history is reset to avoid taking wrong decisions or triggering ADR_RECOVERY mode. |
| RDTP-24808 | DESC: The device alarm #016 may lead to false alerts. FIX: The Device alarm 016 is deactivated, as it is no longer needed. |
| RDTP-25106 | DESC: The UAL export with email in objectID filter return no result. FIX: The result now correctly returned. |
| RDTP-24984 | DESC: For RF probes (RDTP-3399), the payload is ASCII encoded. FIX: For compactness the payload is now binary encoded (4 bytes for the LRR-ID + 1 bytes for the AntennaID), using big indian encoding. |
| RDTP-24980 | DESC: For RF probes (RDTP-3399), the default value of the probeTxPower must be the maxEIRP of the RF Region (and therefore the default value must not be 1.FIX: The default value of the probeTxPower is the maxEIRP of the RF Region. |
| RDTP-24905 | DESC: LRC could lead to a crash. FIX: Lock added in LRC to ensure thread safety. |
| RDTP-24888 | DESC: MongoDB system configuration must be optimized. FIX: MongoDB “Transparent Huge Pages“ has been disabled and vm.mac_map_count has been set to at least 131060. |
| RDTP-24880 | DESC: Internal LnsBridge component could return the error Invalid memory address. FIX: Additional checks have been added when closing an IEC104 connection. |
| RDTP-24831 | DESC: In LRC component, the current default setting of maxDevEUIPerDevAddr is 20. FIX: the default setting has been increased to 100. |
| RDTP-24696 | DESC: Possible SQL connection timeout on device vendors sorting. FIX: SQL index added for optimization. |
Known issues and limitations
| ID | Summary |
|---|---|
| RDTP-23489 | [LoRaWAN relays] Endless Request/Answer loops in case of command rejection |
Release 8.1.0
New features
Other technical improvements
| ID | Summary |
|---|---|
| RDTP-24621 | Upgrade of third-party components to incorporate their latest security patches: ProxySQL, EJBCA, NGINX, MariaDB, MongoDB and Kafka |
| RDTP-23748 | Improve user experience while scanning QR codes during device provisioning: - Enhanced zooming capabilities to allow scanning small QR codes (7x7mm), - Automatic detection of the DevEUI in non-standard QR codes |
| RDTP-23727 | Enhanced scalability of the core network with Basics Station packet forwarder, allowing up to 20K Basics Station connections to ThingPark SaaS |
| RDTP-23655 | Enhanced representation of Connections associated to devices, using badges instead of lists |
Resolved issues
None
Known issues and limitations
| ID | Summary |
|---|---|
| RDTP-24545 | The result of asynchronous operations is not logged in user action logs. This limitation is lifted in release 8.1.1 |
| RDTP-23489 | [LoRaWAN relays] Endless Request/Answer loops in case of command rejection |