[smartpower-interest] XMPP messaging - smart grid

suhas aggarwal <suhasagg@gmail.com> Thu, 14 July 2011 16:57 UTC

Return-Path: <suhasagg@gmail.com>
X-Original-To: smartpower-interest@ietfa.amsl.com
Delivered-To: smartpower-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BF5911E808C for <smartpower-interest@ietfa.amsl.com>; Thu, 14 Jul 2011 09:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.317
X-Spam-Level:
X-Spam-Status: No, score=-1.317 tagged_above=-999 required=5 tests=[AWL=-0.119, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, J_CHICKENPOX_45=0.6, J_CHICKENPOX_51=0.6, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TfQGhUIAZaQL for <smartpower-interest@ietfa.amsl.com>; Thu, 14 Jul 2011 09:57:45 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 31C2811E807C for <smartpower-interest@ietf.org>; Thu, 14 Jul 2011 09:57:45 -0700 (PDT)
Received: by qwc23 with SMTP id 23so300836qwc.31 for <smartpower-interest@ietf.org>; Thu, 14 Jul 2011 09:57:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=4n1XHqmR/GHoCR3GKnPCccmOkOc5Jad3epOnW+qYiBc=; b=CSuCC41uoXlXK3Zxj+tj3rfeyGm6QeG8UgTraz1q7Dsxrh/BhVXZgB4tXIESYvI8oy QjGJtd6unqo1xORiVWPu4H/2d0vRJcfds8Hzzpc1YRGc9BKvw7y8XBKg4xizt5rNYT73 XcC8zW06KMuIzA/FgBNx+IbfkXDdswJjbg9xA=
MIME-Version: 1.0
Received: by 10.229.105.72 with SMTP id s8mr1887130qco.98.1310662664613; Thu, 14 Jul 2011 09:57:44 -0700 (PDT)
Received: by 10.229.98.140 with HTTP; Thu, 14 Jul 2011 09:57:44 -0700 (PDT)
In-Reply-To: <CACfHXG2m=g3GFRoMwkP3mLn2Oo=R_PpjwhJadu1cR_p4asTUGQ@mail.gmail.com>
References: <CACfHXG2m=g3GFRoMwkP3mLn2Oo=R_PpjwhJadu1cR_p4asTUGQ@mail.gmail.com>
Date: Thu, 14 Jul 2011 22:27:44 +0530
Message-ID: <CACfHXG0G=Dc+pHQvP6ES0dE9cS+8P2HTNez7xXEzxB3uWx-ibg@mail.gmail.com>
From: suhas aggarwal <suhasagg@gmail.com>
To: smartpower-interest@ietf.org
Content-Type: multipart/alternative; boundary=00235429ceec8b6fc404a80a6e31
Subject: [smartpower-interest] XMPP messaging - smart grid
X-BeenThere: smartpower-interest@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Smart Power Interest <smartpower-interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smartpower-interest>, <mailto:smartpower-interest-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smartpower-interest>
List-Post: <mailto:smartpower-interest@ietf.org>
List-Help: <mailto:smartpower-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smartpower-interest>, <mailto:smartpower-interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 16:57:46 -0000

Respected sir,

I did a deep study of XMPP messaging protocol in my last assignment.In my
study,I implemented an XMPP client server incorporating event node
terminology.Basic Architecture is Sensor Readings taken by Sensor are
converted into XML format by a Sensor Over XMPP (SOX)Library by an
adapter.Adapter publishes these values(Items) to event nodes present in XMPP
server.Event nodes are virtual locations inside XMPP servers where items are
collected.Different XMPP clients can subscribe to different event nodes and
retrieve individual items.
Some key questions I have is - Can we use this architecture in a substation?
Can this architecture meet real time requirements considering extra
latencies induced by data formatting? Various IEDs can act as publisher and
subscriber which publish values to XMPP servers.This will also include
incorporation of adapter servers which collect data from merge unit,relay
IEDs, convert sensor data to XML format.My question is - Is this conversion
dataformatting really needed for IEDs communicating within local area
network?Is it needed for Local HMI?Is it needed to send data to control
center?
Moreover,adapter can have added advantage of intelligently combining sensor
values from different IEDs ,so that monitoring applications which are
interested in seeing and analysing data from multiple IEDs can
retrieve/obtain this data in a single document.Adapter can publish this item
in corresponding event node from which different applications interested can
retrieve from.
I am providing link to a related paper which discusses Sensor Andrew
Architecture used for critical infrastructure monitoring.
http://www.ices.cmu.edu/censcir/resources/SensorAndrew-Tech-Report.pdf

Sincerely,
Suhas Aggarwal