A rechartering is proposed for rcXML TC.
A proposed rechatering name is psXML and this is for the smart grid.
a. Name
OASIS Power System XML (psXML) Technical Committee
b. Statement of purpose
The purpose of the proposed Technical Committee is to develop a framework–level protocol named psXML(Power System XML) forconsumer services related to consumer equipment and devices and ESP(Energy Service Provider).Between Device Portal in large energy consumer and Consumer Portal in ESP(Energy Service Provider) by monitoring and controlling a wide variety of electric devices in energy consumer’s premises.
In power consumer service system, Device Portal and Consumer Portal are bidirectional communication and service infrastructure between energy consumer and provider by combining hardware and software that intermediate bidirectional communication between ESP and consumer equipment and devices. It is a physical link and logical combination to connect in-building devices of consumer, Wide-area Access Network, and service application platform of ESP, and portals to handle data interchange and service trade between large energy consumer and provider.
The Consumer Portal has been being developed and promoted as a core technology of the future within the power infrastructure innovation program for digital society such as IntelliGrid Project of ERPI and Smart Grid Project of San Diego Gas & Electric (SDG&E) in USA and also as a part of Power IT Core Technology Development Project for the Future (Five Year Project from 2006 to 2010) through active investment by the Ministry of Commerce, Industry and Energy Knowledge Economy and Korea Power Corporation (KEPCO) in Korea.
This committee proposes a Service Oriented Open Standard Protocol, a XML-based standard for power systems and energy consumer services. For a Service Oriented Open Standard strategy with light weight and flexibility, a standard markup language system for XML-based power service system is desirable for various points of views. If the Device Portal and Consumer Portal is are built on the basis of XML, any service operator that wants to provide large energy consumerwith the value-added services of electric power will be able to easily make the desired services regardless to certain equipment, technology or any specific operator.
c. Architecture of psXML Standard
1) psXML Overview and Architecture
This section describes outlines on various kinds of elements and an architecture configuring the psXML standard and defines Device Portal, Device Gateway and Consumer Portal and their interactions.
2) psXML Device Modeling
The psXML Device Modeling specification is a document describing how to logically model the objective physical devices of psXML. The device consists of service and other meta data where the service consists of methods, properties, and events. The result of device modeling will be registered and managed by Repository Server that is a part of the Consumer Portal.
3) psXML-GD (psXSML between Gateway and Device)
The specification of psXML-GD is a communication protocol between device and device gateway. As the name implies, it has a form directly complying the device modeling specification of psXML, and additionally configures several communication methods requested between device and device gateway.
Because most of devices would not comply psXML, this specification is regarded to be used only for the smart devices to be newly manufactured. All devices without compliance with psXML will be translated into psXML by the device gateway.
4) psXML-GP (psXML between Gateway and Portal)
The specification of psXML-GP means a communication protocol between device gateway and device portal and it may become a core of psXML. It defines various kinds of standard methods, properties and events on the basis of the device modeling specification.
5) psXML-DC (psXML between Device Portal and Consumer Portal)
The specification of psXML-DC means a communication protocol between device portal and consumer portal, it is mainly used for requesting date sets.
6) SOAP-CS (SOAP between Consumer Portal and Service)
The specification of SOAP-CS is a communication protocol between services that are popularly called as consumer portal and Business Model (BM). This protocol is based on SOAP 1.2 and its practical aspects such as XML structure will be defined by SOAP-CS specification.
d. Requirements
1) Guaranteeing Independence on media. The psXML is defined mainly on the basis of HTTP so that it has independence to operate on low level protocol including UDP/TCP/RS-232 and communication media such as Ethernet/Wireless/RS-232/RS-485. That is, it does not include any characteristics of media or protocol into a standard.
2) Definition of Common Device Profile
The psXML has one principle to model device and has to describe all devices using it. The device of psXML has to be managed collectively in a single common repository.
3) Meta Information Provision
The psXML is a XML standard but it doesn't compose a specific function of device with one tag. Instead, it defines only the abstract Meta information into tags and degrades the specific function of device to the recommendation level. This makes it possible to handle all of properties, events and methods of device with program for programming to help system design or implementation.
4) Independence from OS and Development Language
The psXML shall be implemented regardless to operating system or development language. The psXML shall not have meaning other than a specified version of XML and allow to be developed in diverse environments.
5) Utilization of Internet-based Technology
The psXML shall utilize internet-based technologies being commonly used to allow reusing existing various types of internet tools and existing programmers to develop psXML-related systems leveraging the internet-based technologies.
6) Guaranteeing Scalability
In relation to the device portal and consumer portal, devices will continue to come out in various types. But the systems related to the psXML that operate the devices have to provide services with minimum changes. The psXML has to allow describing the new devices appeared without any change on the basic specifications.
In order to do this, it is required to progress standardization works considering this aspect in expectation of various types of devices in advance.
7) Ensuring Security and Reliability
The psXML has to include specifications related to security and reliability that were deficient in the existing SOAP. The psXML is a protocol to control the electric power facilities electric devices and equipment that play a very important role for the big large consumers and are controlled through internet.
Since the internet environment is a freely accessible network for anybody theoretically, it should permit access only for reliable operator or from reliable devices, and not allow its contents of communication to be translated with network packet interception by hacker.
e. Deliverables
The TC shall produce two deliverables,
1) the recommended syntax definition (with examples and clarifying notes) for psXML, and
2) the recommended procedure for extending it in the future as needed.
The delivery date for both shall be six months from the start date for the TC. The TC may also choose to define specific extensions after completing the first two deliverables
f. IPR Mode
RF on Limited Terms Mode (as specified in the OASIS IPR Policy)
g. Language
The TC will conduct its business in English. The TC may elect to form subcommittees that produce localized documentation of the TC's work in additional languages.
END