Eventually our work will expand to emerging mobile devices such as drones, robots and other types of vehicles. Examples are high-definition map creation and distribution, intelligent driving, and remote diagnostic maintenance. The Consortium is creating use cases and requirements on networking and computing for connected services in automobiles. Because most diagnostic tools and logs can create more information management requirements and data storage demands, it can raise costs.Īutomotive Edge Computing Consortium (AECC) works with leaders across industries to drive the evolution of edge network architectures and computing infrastructures to support high volume data services in a smarter, more efficient connected-vehicle future. Without good remote diagnostics, it becomes very difficult to be conclusive about where in the service a failure has occurred, and without good diagnostics to prove a failure has occurred in a given part of the systems (endpoint, gateway, network, cloud), getting providers to assume responsibility will be very difficult and inflict delays.Ī significant operational requirement in the IoT will be defining sufficient diagnostics capabilities for all parts of the system with enough detail to manage interdependencies in the service efficiency without inflicting too much additional cost. In any complex system involving multiple providers, it is a well-known condition that service failures and degradations are first blamed on the interdependent service providers. This is a major risk to any IoT service: the effective and efficient diagnosis and tracking of system problems when there are multiple service providers and manufacturers. And nothing gets fixed because there is no consolidated reporting from all these systems and service providers rapidly understand to where the fault actually occurred.Īs often as not, the system fault is due to cascading and converging issues from multiple systems-to fix the problem you need to adjust two or more systems, neither of which in or of themselves actually appears to be failing! The platform guys blame the network guys. The application guys blame the server (platform) guys. Today in IT systems it is very common to encounter a system problem, and, in the course of trying to resolve the issue, the different service providers (both internal and external) will simply point fingers at each other as the clock runs. This is a major point of evolution in IoT requirements from traditional IT requirements, where disparate reporting from different service providers is the norm rather than the exception. Otherwise, tracing problems associated first and foremost with availability and reliability will be difficult, expensive, and time consuming. Access to diagnostic and reporting information from the many different parts and service providers in any IoT is a critical requirement, and this access should be built into agreements and SLAs by customers.
0 Comments
Leave a Reply. |