Data resumption is used when an application requests to restore data used in the previous ignition cycle after an unexpected disconnect. Resumption starts during the
RegisterAppInterface request message processing. The application must include the hashID parameter in the request for SDL Core to recognize a previous connection and attempt to restore as much of the previous HMI state as possible. If the hashID received from mobile is correct, SDL Core will restore the following data to the HMI.
For data resumption purposes, SDL Core must store application-related data such as menu commands, application global properties, voice recognition data, and subscriptions for previous ignition cycles after an unexpected disconnect or ignition off.
If your SDL Core integration is configured to use a resumption data base, on every fourth ignition cycle, SDL clears all corresponding application-related data used for resumption.
; Resumption ctrl uses JSON if UseDBForResumption=false for store data otherwise uses DB UseDBForResumption = false
This does not apply to the default configuration to use the app_info.dat JSON resumption file.
HMI must store the VR grammars compiled for applications that are unregistered by an unexpected disconnect or ignition off. During data resumption, the HMI may also have to resume the previous audio source. Refer to
If the application resumes data successfully:
resumeVrGrammars = trueto notify the HMI that
VRGrammarsmust be resumed. On this event, the HMI must restore the application related VR grammars for the appID received via an
subscribe = true
If the application does NOT resume data successfully:
resumeVrGrammars = falseor no resume parameter at all.
VRGrammarsfor the application.