首页|Patent Issued for Automatic code reconfiguration based on function and subfuncti on analysis (USPTO 11941380)
Patent Issued for Automatic code reconfiguration based on function and subfuncti on analysis (USPTO 11941380)
扫码查看
点击上方二维码区域，可以放大扫码查看
原文链接
NETL
NSTL
The following quote was obtained by the news editors from the background informa tion supplied bythe inventors: “Modern vehicles and other Internet of Things (I oT) systems often utilize many differentcontrollers, which may need software ch anges from time to time. These software changes can presentmany technical and s ecurity challenges. For example, as software is updated over time, its content a ndstructure may become increasingly complex and disorganized, not only increasi ng difficulty for softwaredevelopers, but also increasing code length (i.e., a number of lines of code), software file size, and softwarere-configuration and verification time. In some cases, large software update files may result, which may becostly or infeasible for over-the air-updates and difficult for devices t o implement, especially controllers,which often have limited processing and/or storage resources. Also, even when a device can run such aprogram, this can str ain processing or storage resources as well as degrade system performance. In so mesituations, a function or group of functions may be long or complex and the c hange in the function maybe small and simple. This can result in unnecessarily lengthy delta files (or other software change files) andheavy uses of computing resources to implement or verify software changes when aspects of these long orcomplex functions are changed. As software often requires extremely thorough te sts, the approval processfor every single change is very lengthy and costly, th us creating a need for the ability to determine the truesubstantive impact of s oftware changes, which can be smaller than, and are often obfuscated by, morele ngthy-appearing non-substantive changes. Moreover, as individual symbols may hav e respective objectfiles that are compiled into a binary file, a small change t o a few symbols can lead to drastic changes tothe size and complexity of a soft ware update file. In some scenarios, low-substance changes may be madeto aspect s of code, such as changing a symbol name, with little or no functional change b eing effectedto the code. However, current systems lack vision into these kinds of changes, leading to unnecessaryadditions of code, further exacerbating the issues described above.
NETL
NSTL
