Transport component acceptance

Abstract

An example operation includes one or more of receiving a notification of an available software update configured to alter functionality of a transport, enabling the altered functionality for an amount of time, and responsive to the altered functionality not being utilized during the amount of time, sending a notification indicating a negative outcome.

What is claimed is: 
     
         1 . A method, comprising:
 receiving a software update, configured to alter functionality of a transport, in a memory of a transport;   enabling a timer for monitoring use of the altered functionality by the transport for an amount of time based on one or more profile characteristics comprising a driving history of a transport occupant and selected to accommodate amount of use opportunities by the transport occupant of the altered functionality; and   responsive to the altered functionality not being utilized by the transport during operation for the amount of time, sending a notification indicating a negative outcome to a server.   
     
     
         2 . The method of  claim 1 , wherein the notification indicating the negative outcome comprises one or more of a number of other transports that rejected the update, an outcome of a rejection over a period of time, a number of other transports that accepted the update, and an outcome of an acceptance over a period of time. 
     
     
         3 . The method of  claim 1 , wherein the amount of time is based on an average time that other transports engaged the software update. 
     
     
         4 . The method of  claim 1 , comprising:
 providing, by the transport, a delta indicating a difference experienced during transport operation between a pre download result of the software update and a post download result of the software update.   
     
     
         5 . The method of  claim 1 , comprising:
 providing an indication of a level of satisfaction before the amount of time ends; and   permanently enabling the altered functionality in the transport.   
     
     
         6 . The method of  claim 1 , comprising:
 providing an indication of a level of dissatisfaction before the amount of time ends;   requesting a change to the altered functionality; and   utilizing a level of functionality prior to the altered functionality.   
     
     
         7 . The method of  claim 1 , comprising:
 receiving a notification from a number of transports above a threshold indicating satisfaction with tested altered functionality within the amount of time; and   incorporating the altered functionality into a baseline software release for newly manufactured or updated transports.   
     
     
         8 . A system, comprising:
 a processor, and   a memory, coupled to the processor, comprising instructions that when executed by the processor are configured to:
 receive a software update, configured to alter functionality of a transport, in a memory of a transport; 
 enable a timer to monitor use of the altered functionality by the transport for an amount of time based on one or more profile characteristics comprising a driving history of a transport occupant and selected to accommodate amount of use opportunities by the transport occupant of the altered functionality; and 
 responsive to the altered functionality not being utilized by the transport in operation for the amount of time, send a notification that indicates a negative outcome to a server. 
   
     
     
         9 . The system of  claim 8 , wherein the notification that indicates the negative outcome comprises one or more of a number of other transports that rejected the update, an outcome of a rejection over a period of time, a number of other transports that accepted the update, and an outcome of an acceptance over a period of time. 
     
     
         10 . The system of  claim 8 , wherein the amount of time is based on an average time that other transports engaged the software update. 
     
     
         11 . The system of  claim 8 , wherein the instructions are configured to:
 provide, by the transport, a delta indicating a difference experienced during transport operation between a pre download result of the software update and a post download result of the software update.   
     
     
         12 . The system of  claim 8 , wherein the instructions are configured to:
 provide an indication of a level of satisfaction before the amount of time ends; and   permanently enable the altered functionality in the transport.   
     
     
         13 . The system of  claim 8 , wherein the instructions are configured to:
 provide an indication of a level of dissatisfaction before the amount of time ends;   request a change to the altered functionality; and   utilize a level of functionality prior to the altered functionality.   
     
     
         14 . The system of  claim 8 , wherein the instructions are configured to:
 receive a notification from a number of transports above a threshold that indicates satisfaction with tested altered functionality within the amount of time; and   incorporate the altered functionality into a baseline software release for newly manufactured or updated transports.   
     
     
         15 . A non-transitory computer readable medium comprising instructions, that when read by a processor, cause the processor to perform:
 receiving a software update, configured to alter functionality of a transport, in a memory of a transport;   enabling a timer for monitoring use of the altered functionality by the transport for an amount of time based on one or more profile characteristics comprising a driving history of a transport occupant and selected to accommodate amount of use opportunities by the transport occupant of the altered functionality; and   responsive to the altered functionality not being utilized by the transport during operation for the amount of time, sending a notification indicating a negative outcome to a server.   
     
     
         16 . The non-transitory computer readable medium of  claim 15 , wherein the notification indicating the negative outcome comprises one or more of a number of other transports that rejected the update, an outcome of a rejection over a period of time, a number of other transports that accepted the update, and an outcome of an acceptance over a period of time. 
     
     
         17 . The non-transitory computer readable medium of  claim 15 , wherein the amount of time is based on an average time that other transports engaged the software update. 
     
     
         18 . The non-transitory computer readable medium of  claim 15 , wherein the instructions cause the processor to perform:
 providing, by the transport, a delta indicating a difference experience during transport operation between a pre download result of the software update and a post download result of the software update.   
     
     
         19 . The non-transitory computer readable medium of  claim 15 , wherein the instructions cause the processor to perform:
 providing an indication of a level of satisfaction before the amount of time; and   permanently enabling the altered functionality in the transport.   
     
     
         20 . The non-transitory computer readable medium of  claim 15 , wherein the instructions further cause the processor to perform:
 providing an indication of a level of dissatisfaction before the amount of time ends;   requesting a change to the altered functionality; and   utilizing a level of functionality prior to the altered functionality.