The chunk definitions should contain the chunk number and duration, which you can use to calculate the start time to request. In the case of your example, the chunk number seems to be missing, though you can probably infer them by the order they appear in the manifest.
If you go to the Smooth Streaming Sample site and use fiddler to capture the requests, you'll be able to see the manifest it requests and the relationship between the manifest and the chunks that get downloaded.
In this case, the manifest url is http://mediadl.microsoft.com/mediadl/iisnet/smoothmedia/Experience/BigBuckBunny_720p.ism/Manifest
which gives a video stream containing 8 tracks of different qualities and the chunk definitions with a number and duration attached to each. The player calculates the start time of each consecutive chunk based on the aggregate duration of the previous chunks and requests it by appending the Url
attribute from the stream definition with the quality and start time substituted to the end of the .ism url.
In the case of this request http://mediadl.microsoft.com/mediadl/iisnet/smoothmedia/Experience/BigBuckBunny_720p.ism/QualityLevels(2040000)/Fragments(video=360000000)
we can determine the specific chunk that was requested by dividing the start time by the chunk durations (360000000/20000000=18)