Question: Upon receiving a floor request from a constituent MCPTT (Mission Critical Push To Talk) group, what actions does the floor control arbitration logic take regarding its state and the received request?
Option 1: It transitions to 'G: Granted' state and discards the application/vnd.3gpp.mcptt-floor-request+xml MIME body.
Option 2: It remains in the 'G: Initialising' state but does not cache the application/vnd.3gpp.mcptt-floor-request+xml MIME body.
Option 3: It transitions to 'G: Rejecting' state and caches the application/vnd.3gpp.mcptt-floor-request+xml MIME body for further analysis.
Option 4: It remains in the 'G: Initialising' state and caches the application/vnd.3gpp.mcptt-floor-request+xml MIME body.
Explanation: This is correct because, upon receiving a floor request from a constituent MCPTT group, the floor control arbitration logic should both maintain its current state ('G: Initialising') and store (cache) the received application/vnd.3gpp.mcptt-floor-request+xml MIME body for further processing or evaluation.