If you choose such a url structure, it means you have some sort of hierarchy structure.
For example mysite.com/vehicle/car/mercedes/classc/details/engine could show or return details of the engine of a class C mercedes.
It goes without saying that not transmitting the brand or the car model doesn't make sense.
If you want to keep this hierarchical structure, you must expose an url that permits you to mention the category "undefined" in the structure like: mysite.com/vehicle/car/brandlesscars/mybrandlessmodel/details/engine
If the segments of your url represent a parameter of a query but not a path sequence to access to a more detailed section, it is way better to have a url with parameters like this: mysite.com/vehicle/details/engine?type=car&brand=mercedes&model=classc.
"sampleurl///param3"this seems like bad design though, or i might be misunderstanding your question.