Next Generation ESNet Arch Requirements - ATIS

5. At some time later additional information becomes available and the RG forwards itto the CESE.6. The CESE ACKs the message.7. The caller hangs up the call at the CESE and the CESE notifies the RG.8. The RG acknowledges the hang up9. The CESE completes the event and issues an Emergency Event complete.10. The RG acknowledges the event complete.7.1.4.3 Emergency Event—Information Discrepancy MessageAn Emergency Event Information Discrepancy report can occur for any subscribinginformation source that resulted in an Emergency Event information message to the CESE.The message must identify the service, return the information packet and can provide textindicating the problem or issue identified with the information. This message is only valid ifthe service provider was identified as supporting this feature as indicated by an indicatorflag in the Emergency Event Information message.A particular example related to ALI follows: An Emergency Event is underway and locationdata have been retrieved and displayed at the PSAP call taker position. During theconversation between the PSAP operator and the caller, a discrepancy is detected, e.g.,the location information displayed on the operator’s screen differs from the verbalconfirmation provided by the caller. This scenario is possible during any Emergency Eventor outside the context of an Emergency Event. The message exchange is shown in Figure7-9.CESE Sends: EEinfoDiscrepancy message containing the EEI + incorrect data + ceseid +Authentication Session Identifier + any text entered by the PSAP operatordescribing the problem.CESE Receives: Discrepancy ACKNote: Future versions of the ESMI message set should support a mechanism for theinformation provider to return a change tracking ticket identifier to the CESE to facilitateinquires regarding the status of the information update.11 Version 1 9/23/04