1 / 2

Network Reference Model

Network Reference Model. Functional Entities (ESMI entities are in bold ) CESE Conforming Emergency Services Entity RG Response Gateway ESNE Emergency Services Network Entity (E2) is a specific case of the Emergency Information Sources logical entity (TIA J-STD-036 (E2)

elom
Télécharger la présentation

Network Reference Model

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. Network Reference Model • Functional Entities (ESMI entities are in bold) • CESE Conforming Emergency Services Entity • RG Response Gateway • ESNE Emergency Services Network Entity (E2) is a specific case of the Emergency Information Sources logical entity (TIA J-STD-036 (E2) • ESME Emergency Services Message Entity (E2) is a specific case of the Emergency Information Sources logical entity (TIA J-STD-036 (E2) • Interfaces (ESMI entities are in bold) • A1 Emergency Services 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 ESNet instance (1:n) RG RG CESE (1:n) CESE (1:n) ESMI-15-R1 ATIS-0500002 (Emergency Services Messaging Interface) Replacement or complement for Figure 6-1 Emergency Information Sources ------------- Enhanced Emergency Services ESME A1 A1 A1 Other(s) … PSAP ESNE Emergency Request Sources Pierre Desjardins Positron Inc.

  2. Definitions - Functional Entities • Conforming Emergency Services Entity (CESE) • The client side of the ES Messaging Interface • Any intelligent functional entity that adheres to the PSAP Messaging Interface as defined in this document. It is thought of as residing on the premises of an agency such as a PSAP or participating organization. For illustrative purposes it is shown as consisting of PSAP communications equipment and end point stations such as Call Takers. Specific design of the internals of a CESE is beyond the scope of this specification. • Response Gateway (RG) • The server side of the ES Messaging Interface • The ESNet server side functional entity that adheres to the PSAP Messaging Interface. • The RG provides interworking between the ES PSAP Messaging Interface and “back net” functions provided by the Emergency Services Network. For example, the RG may provide interworking to an ALI database to retrieve ALI. It may interwork to legacy interfaces such as PAM, E2 or other network interfaces to be defined. The design of the RG and “back net” functions is beyond the scope of this specification. • Emergency Services Network Entity (ESNE) – from J-STD-036 (E2) • 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) – from J-STD-036 (E2) • 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 Pierre Desjardins Positron Inc.

More Related