What's new in IBM IoT Connected Vehicle Insights
Learn about what is new and changed in the maintenance and feature updates for the IBM® IoT Connected Vehicle Insights offering.
Important: Before you agree to and plan a service release update together with the IBM Cloud team, review the Upgrade considerations section. To contact your IBM Cloud team, you can raise a request in the IBM Support Community. For more information, see Troubleshooting and support.
January 2021
The January 2021 release of IBM IoT Connected Vehicle Insights version V3.1.1 update provides the following enhancements:
- Asset Management component
- The underlying Maximo Asset Management software component is updated to version 7.6.1.2.
July 2020
The July 2020 release of IBM IoT Connected Vehicle Insights version V3.1 update provides the following enhancements:
-
Asset Management component
- The underlying Maximo Asset Management software component is updated to version 7.6.1.1.
-
Data archiver for HBase data
- The data archiver is a stand-alone tool that you use to archive IBM IoT Connected Vehicle Insights car-probe from HBase into an external data storage such as IBM Cloud Object Storage and Amazon S3. You can configure the data archiver to archive car-probe data in different intervals, such as on a daily, hourly, or weekly basis, and you can set up custom archiving rules.
-
Context mapping enhancements
-
Dynamic road data: The context map service is included in the IBM IoT Connected Vehicle Insights Route API to enable dynamic context changes to road data. Maps include road, or link, data that can have dynamic attributes such as speed. You can use the REST API to create, update, and delete dynamic road attributes, and you can retrieve aggregated road attributes that include both static map data and dynamic context data.
-
Traffic speed prediction: The IBM IoT Connected Vehicle Insights traffic speed predictor assists with the real-time transportation systems operation tasks, including route planning, route guidance, and on-demand mobility services. The traffic speed predictor adds geo-spatial and temporal traffic speed data to the context map. The speed predictor learns and builds models based on historical traffic speed data to predict the speed for a road and the traffic direction.
This feature includes the following API changes:
-
Route API
- POST /mapservice/route
The route API utilizes the predicted speed information if the traffic speed predictor is enabled to calculate fastest path of route.
-
Map Matching 2 API
- GET /mapservice/map/matching2
- POST /mapservice/map/matching2
The Map Matching 2 API provides the following new capabilities:
- Retrieving attributes of a road link
- Returning the reported point with the matched point
- Interpolation between matched points (only the POST API)
-
-
Driver Behavior datastore
- The Driver Behavior REST API datastore is redesigned. You can use the Driver Behavior REST API in IBM IoT Connected Vehicle Insights for online analyses of the driving behavior data that is collected.
-
Mutual TLS authentication
- IBM IoT Connected Vehicle Insights supports mutual SSL/TLS client certificate authentication. For example, you can use client certificate authentication to establish secure communication between IBM IoT Connected Vehicle Insights and the devices that send car probe data.
June 2019
The June release of the V3.0.1 update provides the following enhancements and fixes.
Enhancements
-
Context Mapping
-
The Context Mapping component now supports new API for map matching. Refer to Context Mapping REST API for details.
-
Map Matching 2 API
GET /mapservice/map/matching2
POST /mapservice/map/matching2
The Map Matching 2 API provides the following new capabilities:
- Clearing the trajectory history before or after performing map matching.
- Retrieving matching candidate points evaluated during calculation of best matched point.
-
-
Starter Apps The enhanced Fleet Management Starter Application for the IBM IoT Connected Vehicle Insights SaaS offering demonstrates how quickly you can build an app on IBM Cloud to manage and monitor a fleet of vehicles in real time. You can easily install the starter apps and use the starter apps to view vehicle data, which includes availability, location, health, and historical data. For more information about the starter apps, see Starter Apps and samples.
Fixes
The June release of the IBM IoT Connected Vehicle Insights V3.0.1 update provides the following fixes for known problems.
Component | Problem that is fixed |
---|---|
DataBus/Agent | Reconnecting logic of ZooKeeper client against network failure was improved. The correction includes to get region mapping information on a zookeeper node appropriately even after zookeeper session was disconnected/expired. |
December 2018
The December release of the IBM IoT Connected Vehicle Insights V3.0 update provides some new features and fixes.
Enhancements
-
Cognitive Routing
- The POI (Points-Of-Interest) data support which you can customize via and API.
- Integration with external data which is provided via a Data Crawler from a third party. Examples of third parties include: The Weather Company, TomTom traffic, The Weather Company weather.
- MPP&DP (Most Probable Path & Destination Prediction) with the machine learned model data from historical probe data.
- Enhanced route service in combination with the following data.
- Additional road link attribute data from map vendor such as average speed, road class and other data.
- The pattern data learned from historical probe data per vehicle, or per driver.
- The real-time traffic flow data from a third party. For example, The Weather Company and TomTom.
- The POI (Points-Of-Interest) data.
For more information, see Cognitive Routing.
-
Multi-tenancy enhancements
- New authentication mechanism enables restrictions to access specific tenant data.
- Support JWT-based authentication mechanism.
- Support to issue and revoke JWT and Basic. authentication credentials from Maximo Console/API with userid and password.
- Support to issue tenant-aware credential keys, JWT and Basic.
- Support full tenant (customer) aware data isolation in Maximo.
- Map management enhancements
- Commercial map data with standard based formats are supported, in addition to support for OpenStreetMap (OSM) and Zenrin Maps.
Fixes
The December release of the IBM IoT Connected Vehicle Insights V3.0 update provides the following fixes for several known problems:
Component | Problem that is fixed |
---|---|
Context Mapping | Cached data uses the available memory of the Dynamic Map Manager (DMM), which causes OutOfMemory errors. Automated cleaning up system has been introduced, which deletes obsoleted trip cache data for multi-point map matching. Threshold time for trips to be marked as obsoleted is configurable. |
Context Mapping | The CreateEvent DataBus API should skip the map matching operation when link ID is explicitly specified. |
Context Mapping | Incorrect detection of wrong way driving in map matching when useAltitude is enabled. |
Context Mapping | Some links within a radius of maxDistance are not returned by the map matching. |
August 2018
The release of the IBM IoT Connected Vehicle Insights August (V2.4.1.0) update provides some new features and fixes.
Enhancements
The following new enhancements are provided by the August (2.4.1.0) update:
Component | Enhancement | Description |
---|---|---|
Vehicle Data Hub | Background and on-demand asset loading | You can now load large volumes of vehicle and driver asset data into the VDH component in the background. This can reduce the startup time of the VDH component, especially when there are large volumes of asset data in the IBM IoT Connected Vehicle Insights service instance. To enable this feature, contact your IBM Cloud Representative. |
Vehicle Data Hub & System Manager | Multi-threaded asset loading | You can now reduce the time that it takes to load assets into your service by using a new multi-thread asset loading feature, which simultaneously loads asset data. Important: To use multi-threaded asset loading, your service must be running at least three Maximo Asset Management application nodes. To enable this feature, contact your IBM Cloud Representative. |
Fixes
The release of the IBM IoT Connected Vehicle Insights August (V2.4.1.0) update provides the following fixes for several known problems:
Component | Problem that is fixed |
---|---|
Context Mapping | Obsolete map data that is loaded in memory is not cleared until the Context Mapping component is restarted. |
Context Mapping | When a bulk map matching request contains multiple very near raw GPS points that do not match any road, only one matched point is returned. |
Context Mapping | Cached data uses the available memory of the Dynamic Map Manager (DMM), which causes OutOfMemory errors. Internal REST APIs are introduced to clear cache data in the DMM to prevent memory consumption errors. |
July 2018
- NEW! Service monitoring dashboard
If your service is running the June 2018 (2.4.0.0) update or later, and you are a service user with an IBMId that is authorized, you can now monitor the key components of your IBM IoT Connected Vehicle Insights service.
To check the health status of the key components of your IBM IoT Connected Vehicle Insights service instance, you can access your IBM® Cloud Dedicated SaaS Services Health Dashboard.
Important: To access the health dashboard for your service, you must sign in with a valid IBMid that is authorized to access information about your service. For more information or to request access to the dashboard, contact your IBM Cloud Representative.
For more information, see Monitoring your service.
June 2018
The release of the IBM IoT Connected Vehicle Insights June (V2.4.0.0) update provides new features, enhancements, and fixes.
Enhancements
The following new features and enhancements are provided by the June update:
-
NEW! Plug-in Deployment REST APIs
IBM Business Partners and entitled customers can now deploy custom plug-ins to the Vehicle Data Hub (VDH), Driver Behavior, and Agent system components of IBM IoT Connected Vehicle Insights Development Edition, by using a new public Plug-in Deployment REST API and documentation. For more information, contact your local IBM Representative.
-
Vehicle Data Hub
-
The customization capability of the HTTP interface is now more flexible than in previous versions. You can now plug HTTP servlets and JAX-RS resource classes into the VDH component through an HTTP interface.
-
As outlined in the previous features that are listed, if you are an entitled customer, you can also use the Plug-in Deployment REST API to deploy and test your custom plug-ins to a development edition instance.
-
-
Asset Management component
- New ways to refresh assets by using the IBM® Maximo® Asset Management API are introduced. To refresh asset data across all of the VDH and System Manager* nodes, you can now use the new asset refresh capabilities of the Maximo Asset Management REST API. For more information, see Registering assets programmatically.
- The HTTP asset refresh feature is now fully deprecated. The previously available HTTP asset reset feature, which was initially deprecated in V2.3, is replaced by the refresh support that is provided by the Maximo Asset Management REST API.
*
The System Manager node is applicable only to large and HA environments.
- Driver Behavior
-
The Driver Behavior component now supports the
gzip
content-encoding compression scheme for the following APIs, when the client HTTP request contains"Accept-Encoding: gzip
in the content encoding header.-
HBase Proxy REST API
GET /datastore/carProbe/dateList
GET /datastore/carProbe/dateList
GET /datastore/trip
GET /datastore/trip/carProbe
GET /datastore/trip/carProbe/count
GET /datastore/carProbe
GET /datastore/carProbe/count
-
Driver Behavior REST API
GET /jobcontrol/online/job/pertrip
GET /drbresult/trip
GET /drbresult/tripSummaryList
-
Trajectory Pattern REST API
GET /tpmresult/resultSummary
GET /tpmresult/odList
GET /tpmresult/odDetail
GET /tpmresult/routeGpsList
-
By default, gzip compression is not enabled. To enable gzip compression for your service, contact the IBM Cloud team.
-
Additionally, the Driver Behavior REST API also now supports the following requests:
-
Filtering of driving behavior data by using the following Driver Behavior REST API HBase proxy functions:
- Get car probe data:
/datastore/carProbe
- Get car probe data for a trip:
/datastore/trip/carProbe
- Get a list of trips:
/datastore/trip
- Get car probe data:
-
Specifying a time zone argument in the following operations:
- Delete car probe data list by date:
/datastore/carProbe
- Get trip list:
/datastore/trip
- Delete car probe data list by date:
-
Retrieving and updating the trajectory pattern analysis algorithm parameters:
/tpmjob/tpParameters
-
Specifying a moving object ID (mo_id) list during the analysis of offline driving behavior and trajectory pattern data.
-
-
The following Driver Behavior REST API operations are deprecated:
- The
/datastore/carProbe
HBaseProxy API operation to send car probe data. Use thecarProbe
VDH API request instead. -
All driver profiling APIs.
Note: No alternative API operations exist for the deprecated driver profiling operations. Use custom built client-side applications to calculate driving behavior statistics from the driving behavior analysis data and insights data that IBM IoT Connected Vehicle Insights generates.
- The
-
The map matching behavior in the Driver Behavior component is modified. The key of trajectory for the vehicle is changed from the internal IDs,
N_vehicle_id
andInternalTenantId
to the external IDsVehicle_id
andTenant_id
. -
Multi-tenancy support is now available. The Java™ API of the plug-in framework for driving behavior analytics is updated to support multi-tenants. The
tenant_id
field is added to each interface method. Any existing custom plug-ins that are not relating to multi-tenancy, should function as expected without change. -
The default time-to-live (TTL) value for the
CarProbe/Trajectory/Crash
tables is 100 days. To change the default TTL value to a custom value, contact the IBM Cloud team before the service is provisioned. -
Some enhancements and changes were made to the Driver Behavior
RowKey
feature in the HBase data store. In thegateway.properties
file,HBASE.useHashUid
is now set to true by default.Important: If your service is going to be upgraded from V2.3.x to 2.4.0.0, contact the IBM Cloud team in advance of the update to ensure that
HBASE.useHashUid
in thegateway.properties
file is set to false if required.
-
-
Context Mapping
-
Multi-point map matching is no longer required to be sorted in chronological order.
-
The Context Mapping component now supports multi-point map matching for event injection.
-
A function for querying lane information by one or more lane IDs is now supported. The following APIs are provided for this function:
- REST API operation -
Get Lane Information
- DataBus API operation -
Query Lane
- REST API operation -
-
The Context Mapping lifecycle management function component is enhanced to support the following capabilities:
- The
status
,confidence
,end_time
, andprops
attributes of an existing event can now be updated by usingUpdateEvent
REST API requests. - Events can also now be deleted automatically from the system when the TTL or end_time attribute values are reached and the event is expired.
- The
-
Agent system
- The VDH adapter can invoke vehicle action rules on the Agent system component without the transmission of car probe data (CarProbe). An agent gets invoked when a specific condition is met, for example, a condition might be specific links, areas, vehicle agent state values, or vehicle IDs.
Fixes
The following problems are resolved by the June update:
Component | Problem that is fixed |
---|---|
Driver Behavior (HBaseWriter) | A NullPointerException error condition occurs in the trajectory table when you use the HBase custom adapter that is in the VDH. |
Driver Behavior (HBaseproxy API) | Incorrect validation of the 'from' and 'to' values of parameters that are submitted in a GET /datastore/carProbe REST API query. During the validation, long numerical values are not rejected, as expected. Instead,
they are incorrectly parsed as the year value. |
Context Mapping | When a one-way road is in the reverse direction of the link shape, the function for searching for road links that might be affected by an event does not work as expected. When the problem occurs, the heading or distance fields of the event are incorrectly created. Any events that were created in an earlier version before the June update (V2.4.0.0), that exhibit this problem, must be deleted and reinjected. |
Context Mapping | In a HA or large environment where multiple Context Mapping servers are deployed, if you upload a map file by using the Map Upload REST API, the map is uploaded to only one of the server instances. |
Context Mapping | In some instances, the bulk map matching function does not return the correct link attributes. |
May 2018
The IBM® IoT for Automotive offering family is now renamed to IBM® IoT Connected Vehicle Insights. Some code samples, documentation, and other resources for the offering might still refer to the former name.
April 2018
IBM has simplified and refined the support experience so that you can quickly find the information that you need. For information on the new IBM Support Community and the support process, see the IBM support guide. The Troubleshooting and Support topics have been updated accordingly.
February 2018
The release of the IBM IoT Connected Vehicle Insights February (V2.3.1.1) update provides fixes to several reported problems in the Agent system and Context Mapping components of the service.
Fixes
The following problems are resolved when you upgrade your service to the IBM IoT Connected Vehicle Insights February V2.3.1.1 fix update:
Component | Problem fixed | More details |
---|---|---|
Agent system | Vehicle state data unrecoverable after Agent system server failure | When the Agent system server fails, depending on the timing of the disruption, some of the vehicle state data records might not be recovered. |
Context Mapping | The function for searching for road links that might be affected by an event does not work as expected | In some scenarios, the QueryAffectedLink API did not return all of the affected road links. As a result, the agent that ran on the Agent system server did not detect all of the events that might affect the position of the car
probe. |
Context Mapping | Poor performance of the Moving Object Map Analytics (MOMA) component when querying trip data that is in the HBase data store | The performance of a query that uses the '/datastore/trip' API was poor when a large volume of trip data was stored in the HBase system of IBM IoT Connected Vehicle Insights. |
Context Mapping | In the Databus interface, the results of the QueryAffectedLink API request are incorrect when your service uses a map that is deployed in staging mode |
The QueryAffectedLink API returned an incorrect result when the map for your service was deployed in staging mode, which was indicated by a map status value that was set to READY in the Databus interface. |
Context Mapping | Multi-point map matching is incorrectly used in QueryAffectedLink calculations |
In some scenarios, multi-point map matching was incorrectly used for QueryAffectedLink calculations instead of single-point map matching. |
Context Mapping | The RouteSearch REST API returns incorrect link_shapes or route_length |
In some scenarios where a specific type of map data was used, the RouteSearch API did not return the correct route path. |
December 2017
The release of the IBM IoT Connected Vehicle Insights December (V2.3.1.0) update provides enhancements and fixes to reported problems.
Enhancements
The following new features, fixes, and enhancements are provided:
-
Agent system
- The Agent system introduces a new agent timer feature for vehicle action type rules, which you can use to invoke vehicle actions by timer.
- Vehicle actions are now handled as a set of asynchronous tasks. A vehicle action rule can now submit asynchronous tasks that are invoked after the vehicle action is completed. Asynchronous tasks are suitable for vehicle action rules that require a message to be sent to an external system after a specific vehicle action is finished.
-
Vehicle Data Hub
- Trajectory map matching in bulk on the Dynamic Map Manager (DMM) adapter of the VDH component is now supported. A plug-in that can handle map matching operations for multiple points per vehicle simultaneously is now available.
Fixes
The following problems are fixed when you upgrade your service to the IBM IoT Connected Vehicle Insights December V2.3.1.0 update:
Component | Problem fixed | More details |
---|---|---|
Agent system | Timeout issue with the GetCarProbe request just after the Agent system process opens |
If a GetCarProbe request that includes a longitude and a latitude is called before the agent server initialization is done, the thread that is assigned to handle the GetCarProbe request goes into an infinite loop,
resulting in a timeout issue. |
Agent system | XSD files unexpectedly revise rules | The InitParameter element of a custom rule on the Agent system is not permitted under the MethodCondition element. |
Driver Behavior | Altitude is not handled properly by the HBase Proxy /datastore/carProbe REST API operation |
Both the altitude and matched altitude are not retrieved from the HBase Proxy API even if they are received by the sendCarProbe API and successfully stored in the VDH. |
General - all components | Incorrect evaluation results from a geofence condition | The first car probe result that is evaluated for a geofence condition is incorrectly set to true. This results in a vehicle being incorrectly flagged as meeting the geofence condition. |
November 2017
The release of the IBM IoT Connected Vehicle Insights November (V2.3.0.0) update provides the following enhancements:
-
Agent system
-
Vehicle and driver agents can now be persisted.
-
Improvements were added to make the connectivity between the Agent system and ZooKeeper Watcher more stable.
-
-
Asset Management component
- The underlying Maximo Asset Management software on the Asset Management component is updated to version 7.6.0.8.
- Enhancements and changes to asset data management to integrate Agent system rules with Maximo Asset Management. You can now update and refresh your IBM® IoT Connected Vehicle Insights asset data in Maximo Asset Management from the Agent system by using a new rule syntax.
-
General
- The underlying IBM® Open Platform (IOP) software is updated to version 4.2.5. For more information, see IBM Knowledge Center - Open-source technologies.
-
REST API
- From version 2.3, the
/vehicle/refresh
asset
operation in the VDH REST API for refreshing assets is now deprecated and is no longer supported for use with a service that is running 2.3 or later. Use either Maximo Asset Management or a custom API to refresh vehicle assets. - The HBase proxy
/datastore/carProbe/dateList
REST API request, which was available for use in non-production test environments to get car probe data listed by date is now deprecated and is no longer supported for use with a service that is running version 2.3 or later.
- From version 2.3, the
October 2017
The release of the IBM IoT Connected Vehicle Insights October (V2.2.2.2) update provides the following enhancements:
-
Driver Behavior
- Adds the ability to process trips that contain less than 10 car probe data points.
-
Context Mapping
- The startup order dependency of
EventInitRequest
is removed. - Map matching results now contain boundary information, which is based on the matched position.
- The startup order dependency of
August 2017
The IBM IoT Connected Vehicle Insights August update (V2.2.2.0) provides the following extra support, and enhancements:
- Vehicle Data Hub
- You can now retrieve and set the
State
value of an agent that is running on a VDH plug-in. - The VDH component is enhanced to support and process incoming crash data from connected vehicle devices. Crash data can also be stored in the IBM IoT Connected Vehicle Insights HBase storage component.
- You can now retrieve and set the
- Agent system
- The Agent system component introduces a new management policy, which you can use to specify whether to overwrite any car probe data property values with newer data values or to keep them.
- The real-time analytics of the Agent system now support calculation by rule. When you define a rule, you can add an equation to calculate the condition that must be met to trigger a rule. For example, a user can create a rule to trigger an alert when the VDH receives a specified number of car probe data updates.
- Asset Management component
- Device lifecycle management capabilities in the Asset Management component are enhanced as the vehicle data model supports more attributes. Delta asset data updates are also now supported between the VDH and the Asset Management component.
- Driver Behavior
- The Driver Behavior component is enhanced to support hybrid driving behavior data that is received from smart vehicle devices. Hybrid driving behavior data is car probe data that is already analyzed and filtered by the onboard vehicle device.
- New plug-ins are available to analyze threshold-based car probes and reports from smart devices into IBM IoT Connected Vehicle Insights.
- When you create rules that detect vehicle actions, there is more flexibility and Java™ support in the Agent system component. If you are developing
VehicleAction
rules, you can now embed customized logic that is developed in Java.
- Context Mapping
- Easier map administration with automated map source updates for Open Street Maps (OSM). The map administration tool is available on request.
- The map matching feature of the Context Mapping component now supports altitude data.
April 2017
The release of the IBM IoT Connected Vehicle Insights April (v2.2.0.0) update provides the following extra support and enhancements:
- General
- Deregistration workflow support.
- Support for Agent rules and Driver Behavior component plug-ins to use road link data.
- Enhancements and updates to the APIs.
- Several fixes to improve the overall service quality.
- Driver Behavior
- Instant driving behavior analysis results online as soon as a journey is completed.
- Driving behavior plug-in framework for modifying or extending the driving behavior analysis logic.
- Context Mapping
- Bulk map matching support for the Context Mapping component.
March 2017
The IBM IoT Connected Vehicle Insights Development Edition is now available for you to explore and test the connected car capabilities of IBM IoT Connected Vehicle Insights SaaS in a non-production environment. For more information, see IBM IoT Connected Vehicle Insights Development Edition.
Latest news
You can also keep up to date with IBM IoT Connected Vehicle Insights and other IBM IoT news by using the following social media channels:
Twitter | Facebook | IBM Community for IBM IoT Connected Vehicle Insights: Blogs and Forums
Upgrade considerations
- After your IBM IoT Connected Vehicle Insights service is updated, you must thoroughly test your customizations and custom plug-ins to be sure that everything continues to work as expected.
Important: In some instances, configuration properties and file names might be renamed or redefined between release updates. Therefore, whenever your service is upgraded, you must revert back to the default predefined file state for the latest release, and then reapply your customizations and configurations. Review the detailed release notes to confirm which files and properties work differently post-upgrade. When your newly upgraded service is operational, you can then reapply and test your customizations according to the instructions of the latest update.