1 / 2

ESNet instance (a)

RG (1:n). RG (1:n). RG (1:n). CESE (1:n). ENEN-001. Generic Architecture for ENEN Interface. Entities Providing Emergency Services (EPES). ESME. Functional Entities CESE Conforming Emergency Services Entity RG Response Gateway Reference Entities (for context purposes)

errin
Télécharger la présentation

ESNet instance (a)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. RG (1:n) RG (1:n) RG (1:n) CESE (1:n) ENEN-001 Generic Architecture for ENEN Interface Entities Providing Emergency Services (EPES) ESME • Functional Entities • CESE Conforming Emergency Services Entity • RG Response Gateway • Reference Entities (for context purposes) • ESNE Emergency Services Network Entity (a network element of TIA/EIA/J-STD-036-A) illustrates a specific case of the Emergency Request Sources logical entity • ESME Emergency Services Message Entity (a network element of TIA/EIA/J-STD-036-A) illustrates a specific case of an Emergency Information Service logical entity • EPES Entities Providing Emergency Services • Interfaces • A1 Emergency Services Messaging Interface • A2 Emergency Information Services Interface • A3 ESNet to ESNet (InterESNet) Messaging Interface • Remarks • The interfaces depicted as dotted lines linking entities are beyond the scope of this standard or are defined elsewhere • The (1:n) notation means “one or more” instances A2 A2 ESNet instance (b) (1:n) ESNet instance (a) (1:n) A3 A1 A1 A1 CESE (1:n) CESE (1:n) PSAP Other(s) … PSAP ESNE Emergency Request Sources ESNE

  2. Definitions - Functional Entities • Conforming Emergency Services Entity (CESE) • The client side of the Emergency Services Messaging Interface • It is thought of as residing on the premises of an agency such as a PSAP or participating organization. The design of a CESE is beyond the scope of this specification. • Response Gateway (RG) • The server side of the Emergency Services Messaging Interface • The RG operates as a proxy to “back net” functions provided by the Emergency Services Network. For example, the RG may provide inter-working to an ALI database to retrieve ALI. The design of the RG and “back net” functions is beyond the scope of this specification. • Emergency Services Network Entity (ESNE) • A network element defined in TIA/EIA/J-STD-036-A • The ESNE routes and processes the voice band portion of the emergency call. This is composed of selective routers (also known as Routing, Bridging and Transfer switches). The structure of the Emergency Services Network is beyond the scope of this standard, • Emergency Services Message Entity (ESME) • A network element defined in TIA/EIA/J-STD-036-A • The ESME routes and processes the out-of-band messages related to emergency calls. This may be incorporated into selective routers (also known as Routing, Bridging and Transfer switches) and Automatic Location Information (ALI) database engines. The structure of the Emergency Services Network is beyond the scope of this standard • Emergency Information Service (EIS) • A generic term representing a functional entity that provides data and/or services in support of emergency events. • For the purposes of the ESMI protocol, an EIS is a service that is coordinated via ESMI by either being invoked or otherwise made available to one or more CESEs. • EISs may be invoked and deliver services in ways beyond the scope of the ESMI. • Enhanced Service • A generic term representing a functional entity that provisions a service that is ancillary or complementary to Emergency Information Services. • For the purpose of the ESMI protocol, Enhanced Services are handled similarly to Emergency Information Services.

More Related