Next Generation ESNet Arch Requirements - ATIS

More documents

Recommendations

Info

4. If no specific EEI attached, all active events are reported, including active IMsessions.7.1.5.3 Event Activity ReportThe CESE may request an activity report from the ESNet (Refer to Figure 7-4). This mayinclude events segmented by class of service, events received over a reporting window(day, week, etc), and other such selection criteria. The information returned will includeactive Emergency Events and IM sessions by Emergency Event Identifer. In addition thismessage may return a complete transcript of an IM session up to the time of the request.CESE Sends: GetEventActivity request + report typeDepending on report type, there could also be a date-range fieldCESE Receives: ACKCESE Receives: EventActivityReport ceseid + Authentication Session Identifier +reportCESE Sends: ACKErrors: Data unavailable, range not valid, service unavailableNotes:1. Specific reports will be defined based on customer requirements.2. This is intended as an MIS message to enable an administrative CESE to obtaininformation about a specific PSAP.7.1.5.4 Configuration ReportThe RG may request configuration parameters related to the CESE (Refer to Figure Figure7-5). This may include network connections, number of positions supported by CESE, andother such configuration-related information.CESE Receives: GetConfiguration requestCESE Sends: ACKCESE Sends: Configuration Report ceseid + Authentication Session Identifier +configuration information, format TBDCESE Receives: ACKErrors:Data unavailable, service unavailableNotes:1. This data is intended for use in troubleshooting, e.g., hung connections, resourceexhaustion, etc.20 Version 1 9/23/04
7.2 Connection Negotiation MessagesConnection Negotiation messages facilitate the connection of a given CESE to anappropriate RG. In doing this they facilitate authentication of both the CESE and RG andcreate a relationship between the two that is persistent for some period of time. ConnectionNegotiation messages verify, at the application level, that the CESE and RG are availableand able to submit or service application requests. They also manage the relationshipbetween the CESE and the RG such that the dynamic nature of the Emergency ServicesNetwork can be gracefully accommodated. Specifically, ESNet endpoints may be placedinto service, leave service for maintenance reasons, etc. without impact to the network as awhole and without impacting the service provided to CESEs.7.2.1 Connection Set UpA persistent, managed connection between the CESE and an ESNet gateway (i.e. an RG)is crucial. Accordingly, a CESE will use some resource discovery technique (e.g., DNS)and a connection determination mechanism embedded in the ESNet to find an appropriateResource Gateway to connect to. The CESE negotiates with the Connection Manager,including an exchange of credentials to guarantee that the application session is properlyauthenticated and authorized, for a connection to a Resource Gateway. The CESE andthe RG negotiate appropriate application connection parameters and establish anadministrable time period based persistent connection over a TCP/IP socket. Once theapplication session is established, the CESE and the RG begin exchanging applicationmessages.As a result of the authentication, the ESNet gives the CESE an “Authentication SessionIdentifier” to be included in messages from the CESE to the RG. The AuthenticationSession Identifier is used as a surrogate for the authentication process on a message bymessage basis, but it’s most important role comes when rotating connections, as in theacquiescence scenario discussed below. Instead of the entire re-authentication process,which entails presenting certificates and obtaining further credentials (e.g., some fob value)directly from a PSAP operator, the Authentication Session Identifier can be used to set up anew connection without direct operator intervention. This saves the operator the oneroustask of personal authentication every time a connection is acquiesced.Figure 7-12 illustrates this connectivity.21 Version 1 9/23/04
Page 1 and 2: Emergency Services Interconnection
Page 3 and 4: 7.1.1 Application Management and Ma
Page 5 and 6: CESERGApplication Session1. Logout
Page 7 and 8: Figure 7-5 illustrates ESNet initia
Page 9 and 10: Figure 7-7: Inclusion of Emergency
Page 11 and 12: 5. At some time later additional in
Page 13 and 14: 7.1.4.5 CESE Transfer MessageThe Tr
Page 15 and 16: an EEcomplete message. It is also p
Page 17 and 18: The RG forwards the message to CESE
Page 19: 7.1.4.8 Administrative Monitoring o
Page 23 and 24: 7.2.2 Application Connection Acquie
Page 25: 2. The CESE Client ACKs the request

Next Generation ESNet Arch Requirements - ATIS

Create successful ePaper yourself

Delete template?

Save as template?