30 likes | 115 Views
Emergency Services Interconnection Forum (ESIF) Emergency Services Messaging Interfaces Task Force (“Task Force 34”) Contribution Title: ESNet Mediated and Non-Mediated Service Provisioning Diagram Contribution Number: EISI-024 Submission Date: 7/20/05
E N D
Emergency Services Interconnection Forum (ESIF) Emergency Services Messaging Interfaces Task Force (“Task Force 34”) Contribution Title: ESNet Mediated and Non-Mediated Service Provisioning Diagram Contribution Number: EISI-024 Submission Date: 7/20/05 Source: Emergency Services Interconnection Forum (ESIF) Technical Contact: Abstract: Diagram illustrating the concepts of mediated and non-mediated emergency service provisioning. Recommendation: Integrate in EISI baseline Content: Slide 1 – then diagram Slide 2 – accompanying text Note: A standalone scaled JPG image of the diagram is available from the author.
ESNet mediated and non-mediated emergency services Client configuration procedure registers CESE/ECES(s): UUID, credentials service subscription(s)… Service configuration procedure registers EPES(s): UUID, credentials… Admin Configuration ESNet Service host application Client Identity Session management Session management Identity Mgmt EPES Identity Service registration Identity info, RG Server URI, authorized services Identity info, UDDI Registry URI CESE Client Mediated services RG Server EPES Client Message Sets Identity info, UDDI Registry URI Non-mediated services UDDI Registry ECES Client Private Service Private services: out of ESNet scope Client host application
This diagram uses a sample ESNet implementation scheme to illustrate the concepts of mediated and non-mediated emergency services provisioning. In both cases, ESNet session authentication is required. For mediated services Service initiation is performed through an RG. Service interactions are defined by ESNet message sets and transit through an RG, although media streams can be made to bypass the RG via dynamically assigned communication channels. For non-mediated services Service initiation is performed directly with the target service. Service interactions are defined using WSDL and occur directly between the client and the service provider (EPES). The UDDI Registry houses the service definitions (WSDL) that are supplied on request to clients such as the RG, service providers (EPES) and non-mediated clients (ECES). The diagram also illustrates the need for some form of off-line administrative configuration process (part of which could be automated), that provides information the Identity Management sub-system about ESNet end-points.