Next Generation ESNet Arch Requirements - ATIS

an EEcomplete message. It is also possible that both operators will elect to remainon the call until the event is completed.2. When the transferred-to CESE makes its information request, the sequence looks justlike the usual Emergency Event scenario except that the RG uses the previouslyassignedEEI .3. Both CESE-RG application connections remain active before, during, and after thetransfer, as each goes on to handle other events.4. A CESE transfer creates the possibility for an instant messaging exchange betweenthe operators.The flow of Figure 7-10 is as follows:.1. CESE 1 issues an Emergency Event2. The RG ACKs.3. The RG returns ALI information.4. The CESE ACKs.5. The CESE operator initiates a transfer of the emergency call and notifies the RG.The message may include local notes.6. The RG ACKs.7. CESE 2 issues an Emergency Event.8. The RG ACKs.9. The RG returns ALI information, the original EEI and local notes.10. THE RG ACKs.11. CESE 1 drops the call and notifies the RG.12. The RG ACKs.13. CESE 1 completes the Emergency Event and notifies the RG.14. The RG ACKs.15. CESE 2 drops the call and notifies the RG.16. The RG ACKs.17. At some point CESE 2 has handled the Emergency Event and issues anEmergency Event Complete.18. The RG ACKs.7.1.4.6 Broadcast Notification MessagesThe ESMI provides the capability to notify entities of emergency situations using BroadcastNotification messages. The Broadcast Notification Message may be issued by a CESE tonotify other CESEs of a global Emergency Event, for example, chemical spill, homelandsecurity notifications, etc. It also may be issued by an authorized agency behind theEmergency Services Network to inform individual users, a group of CESEs (e.g. a PSAP)or all CESEs within the ESNet instance of such an event.15 Version 1 9/23/04