DRAFT

Open Specifications for Wireless Grids

Technical Requirements

Version 0.2 approved: WiGiT Group Dr. Lee W. McKnight, Editor

Kauffman Professor of Entrepreneurship and Innovation School of Information Studies

Syracuse University

Prepared by Syracuse University, University of Arizona, Rochester Institute of Technology, Tufts University,

and WiGiT partners http://WiGiT.ischool.syr.edu

March 21st, 2013

2

Authors: Lee W. McKnight, Janet Marsden, Joe Treglia, Ed Nanno, Aashik Hameed and Ying Lu,

Syracuse University WiGiT Lab

Revision History: Name Date Reason For Changes Version

3

Table of Contents

Revision History

1. Introduction 1. Purpose

2. Project Scope

3. References to Related Documents

2. Overall Description 1. WiGiT v0.2 Technical Specification Overview

2. Features and Functionality

3. User Classes and Characteristics

4. Operating Environment

5. Design and Implementation Constraints

6. User Documentation

7. Assumptions and Dependencies

3. WiGiT v0.2 System Features and Components 1. System Logical Components Overview

2. Authentication and Authorization Component (AAC)

3. Billing, Accounting, and Charging Component (BAC)

4. Messaging and Presence Component (MPC)

5. Metadata Component (MC)

6. Resource Management Component (RMC)

7. Economic and Legal Policy Component (ELP)

7.1 Internet Rights and Principles

7.2 RFC 6852. Affirmation of the Modern Paradigm for Standards

8. Communication Protocols Component (CPC)

9. Security Component (SC)

4. External Interface Requirements 1. User Interfaces

2. Hardware Interfaces

3. Software Interfaces

4. Communications Interfaces

5. Data Interfaces

5. Other Nonfunctional Requirements 1. Performance Requirements

1.1 Guidelines for Web Accessibility

2. Safety Requirements

3. Security Requirements

4. Software Quality Attributes

6.0 Other Requirements

Appendix A: Glossary

Appendix B: Analysis Models

Appendix C: Issues List

Appendix D: References

4

1. Introduction

The Wireless Grid Innovation Testbed (WiGiT) and its Wireless Grid architecture and edgeware

have been developed under the auspices of the National Science Foundation Partnerships for

Innovation (PFI) grant #0227879. Syracuse University (SU) and Virginia Tech (VT) created the

first national WiGiT distributed experimental testbed in 2009. Working software prototypes were

first demonstrated at Syracuse University in 2003, and field tested since 2005. Hardware

implementations have been lab tested iteratively over the years, with initial field testing in

2008/9 and a new series of field trials begun again in 2011/2012. In August 2012 an enhanced

iDAWG (intelligent deployable augmented wireless gateway) was demonstrated, with additional

evaluations scheduled for 2013. Field tests of WiGiT specifications, applications, services, and

devices are ongoing in cooperation with WiGiT partner firms, schools, public agencies,

healthcare institutions, universities, and emergency managers. All are welcome to join WiGiT,

at no cost, and no obligation. (http://wigit.ischool.syr.edu/joinwigit)

The project is currently primarily supported by the National Science Foundation Partnership for

Innovation (NSF/PFI) program, NSF # 0917973. The WiGiT v0.2 Open Specifications presented

below have been developed in cooperation with Enterprise Cloud Leadership Council (ECLC) of

TM Forum. The ECLC ‘Workplace as a Service’ Whitepaper TR194, January 2013; and TR192,

October 2012, ‘Workplace as a Service Requirements.’ These are accessible at

www.tmforum.com. First, we explain the purpose for WiGiT open specifications. The

relationship between WiGiT v0.2 open specifications and Enterprise Cloud Leadership Council

Workplace as a Service is illustrated in Figure 1. Then we review functional requirements, and

components. Use Cases, such as for Workplace as a Service, are also elaborated on in separate

documents, such as WeJay, iDAWG (Intelligent Deployable Augmented Wireless Gateway),

NEERS (Networked Edgeware for Energy Resource Sharing).

1.1 Purpose

The purpose of this Version 0.2 initial release of open specification technical requirements is to

further define and describe the core components of the Wireless Grid Innovation Testbed

(WiGiT) first described in Version 0.1, released March 27, 2012. WiGiT is a wireless grid

network platform, and several edgeware applications associated with certain use cases for

WiGiT have been released (see WiGiT Group Use Cases). New use cases and implementable

software are in development and being prepared for testing. Edgeware is a new class of software

specifically designed for software applications deployed on wireless grids. Edgeware refers to

the software capability to deploy network ‘edge’ devices (aka nodes) as acting servers, hence the

‘serverless’ logic of the architecture. The WiGiT wireless grid architecture and platform enables

heterogeneous resource discovery and sharing through the formation of wireless grid virtual

networks. Wireless grids are dynamic virtual cognitive networks that exist only while they are in

use. Users are able to share and manage available and accessible hardware and software

5

resources through edgeware applications based on the WiGiT product’s core components.

WiGiT platform components and edgeware have built in security at multiple levels of the

network and are energy and bandwidth efficient by design. These open specifications further

define the WiGiT platform and the logical functions of the WiGiT core components in additional

detail based upon the 0.1 version.

Intended Audience and Reading Suggestions

The intended audience for these specifications includes entrepreneurs, executives, software

developers, network technicians and managers, computer programmers, project managers,

academics, students, and all global citizens that have an interest in new forms of application

development, network technology and wireless cognitive heterogeneous networks.

Because certain terms, such as ‘edgeware’, are new, and others are repurposed, a glossary of

terms is included in Appendix A.

Document Conventions

Terms that appear in the glossary are denoted by appearing in italics where they first are used in

the text.

1.2 Project Scope

Ultimately, WiGiT expects to be at the center of an emerging industry serving new markets

through its distributed incubation of wireless grid applications, training and workshops. By

incubating technology and teaching, both knowledge spillover and transfer between testbed

partners and their real/virtual communities flow, creating an entrepreneurial ecosystem that

encourages exploitation of opportunities to transform user practices and system designs into

novel tools and products. The WiGiT technology diffusion model could be one of several

artifacts produced by this project with wide applicability in other entrepreneurial ecosystems.

Please refer to the Open Specifications for Wireless Grids Vision and Scope Document for a full

discussion of the vision and scope.

Figure 1: Open Edgeware-Enabled Approach to WPaaS

6

(Source: McKnight, ed. WiGiT v0.2 in process.)

The Enterprise Cloud Leadership Council (ECLC) Catalyst Project is delivering end-user

computing, communications, and collaboration capabilities through a set of world-class services

that we call Workplace as a Service (WPaaS), in a context of everything as a service across an

internet of things within the enterprise. This Open Edgeware-Enabled Approach proposed a

flexible secure cloud service delivery framework for edge applications based on Bring Your

Own Devices (BYOD) for enterprise level services. (Source: Workplace as a Service

Requirements, TM Forum TR192, 2012)

Product Perspective

The WiGiT architecture and edgeware has been in development since the early 2000’s. Wireless

grids software applications were implemented in 2002-2005 within the Syracuse University (SU)

Wireless Grids Lab under the NSF PFI grant #0227879 [1]. As a proof of concept the team

developed a modest initial application that allowed devices with no prior knowledge of each

other to collectively record and mix an audio signal such as a concert, speech, lecture or

emergency event. The project demonstrated the potential of wireless grids and distributed ad-hoc

resource sharing to harness the combined abilities of mobile devices in social contexts [1]. Note,

in 2013 Syracuse University was awarded a patent related to that original work, for ‘Distributed

Audie Recording and Collaborative Mixing.’ A wireless grid application, WeJay, developed by

7

Wireless Grids Corporation, which spun out of the university lab, has been developed under

license to Syracuse University, and is undergoing current testing in several school systems and

potentially soon with other WiGiT partner organizations.

Building on prior research Syracuse University (SU) and Virginia Tech (VT) created the first

national WiGiT. The project is currently supported by the National Science Foundation

Partnership for Innovation (NSF/PFI) grants, NSF # 0917973.

The WiGiT allows researchers to experiment with grids available throughout the community,

with the objective that WiGiT would enable transformative technologies by bridging the gap

between wireless network middleware and grid application layers, creating new markets and

realigning existing ones. WiGiT serves industry needs for intra-system, or crossover work,

bridging grid or cloud computing on one platform and wireless Internet on another, and

contributing to open standards for application programming interfaces on wireless grids.

Product Features

The evolution of computing has lead to networks which are characterized by decentralization and

decreasing institutional control over resources. Wireless Grids, mobile ad-hoc resource sharing

networks, are challenging environments in which users strategic behaviors are crucial to system

performance. We discuss technical, social, legal and economic trends in their operation and

application within distributed, Grid, and cloud computing [2].

1.3 References to Related Documents

WiGiT Group Open Specifications for Wireless Grids Vision and Scope document

WiGiT Group Open Specifications for Wireless Grids Use Cases: Wejay, iDAWG, VT CROSS,

Workplace as a Service (WPaaS)

2. Overall Description

WiGiT technology creates wireless grids or infrastructure-less mobile ad hoc networks. Wireless

grids can intelligently and dynamically interconnect users and stakeholders at multiple sites,

transfer digital media, assume and respond to different equipment types, and adapt to low power

conditions and diminished communications capabilities.

Figure 2 shows the wireless grid framework. Wireless grids’ functionality can be viewed in

multiple ways: as a front-end/user interface to heterogeneous resources, a mesh network used for

sharing resources, as low-powered sensors networked together, or as ultra wideband, eg, or other

high-capability spectrum sharing technologies. Characteristics of wireless grids include small,

low powered devices that can address concerns about power efficiency. Wireless grids are

compatible with many device types, including mobile and nomadic devices, phones, tablets,

8

laptops, and network computers. The omnivorous intelligence of wireless grid edgeware offers

spontaneous, simultaneous access to telematics, eg. Onstar and capabilities of meshing groups of

devices together and pooling resources to enable new applications based on networks of wireless

sensors for environmental, health, security monitoring, and other potential applications.

Figure 2. WiGiT Open Framework

2.1 Overview There are two modes of wireless grid creation; user mode and node-based mode. Figure 2 and

Figure 3 and 4 show these two modes. Comparing a ‘human user’-centric grid with a ‘node-

based’ grid in purely conceptual terms, it is evident that in both cases the outermost frontier of

what is currently possible, i.e., engaging the full range of user types (with device heterogeneity

considered on an infinite axis) only goes so far. As of today the successful interoperability in an

entirely localized setting is difficult and not achievable without flash drives, uploads, downloads,

drivers, and ultimately wires. The promise of the wireless grid technology is the capability of

machine-to-machine communication via a virtual distributed operating system that enables the

‘internet of things’.

Figure3. User View Figure 4. Machine View

9

In contrast to today’s internet, the wireless grid or ‘Grid’ is software-driven, serverless and

infrastructureless (in the sense of dedicated infrastructure). The Grid is made possible by the

‘Grid Core’. This is a piece of software that is installed on any Grid-enabled device. It consists of

a common core library with binding for the local environment. It runs as a low level system

process and as a result is always available, though its function and capability is dictated by user

assertion. Users are allowed to share and manage the digital resources at their fingertips through

applications of the architecture’s eight core components: the Authentication and Authorization

Component (AAC), the Billing, Accounting and Charging Component (BAC), the Messaging

and Presence Component (MPC), the Metadata Component (MC), the Resource Management

Component (RMC), the Economic and Legal Policy Component (ELP), the Communication

Protocols Component (CPC), and the Security Component (SC).

2.2 Features and Functionality

Interacting with or using the Grid is dependent upon the key functionality of the resource

sharing protocol (RSP), which has the primary function of enabling service discovery for

nomadic ad hoc heterogeneous resource allocation through the following attributes:

○ Resource Advertisement/Discovery

○ Resource Identification

○ Resource Acquisition

○ Resource Description

○ Clearing Mechanisms

○ Coordination of Systems

○ Trust Establishment and Security

2.3 User Classes and Characteristics

Please refer to the illustrative use cases contained in the WiGiT Group Open Specifications for

Wireless Grids Use Cases: WeJay, iDAWG, NEERS and VT CROSS.

2.4 Operating Environment

The Wireless Grid operating environment is based on agnostic acquisition and utilization of

existing networked and network compatible devices, and other resources. In that sense, there is

only one operating environment – the Wireless Grid – but in another sense, there are limitless

potential operating environments.

2.5 Design and Implementation Constraints

10

As a preliminary specification for a technology that is still in development and exists mainly in

testbeds at this time, this is beyond the scope of this document. Suffice it to say, the security,

policy, privacy and cost considerations of this technology have been closely scrutinized, and will

continue to be evaluated as development continues. However, those applications that are now

public have met or surpassed every test or challenge that they have been subjected to, and in

every evaluation have been found to be superior to the standards now in use.

2.6 User Documentation

At this time, this document and the documents noted as ‘Related Documents’ in section 1.3 are

the only planned documentation. However, full user manuals, online help, and other academic

and professional documentation will be defined, produced and published appropriately in

conjunction with associated edgeware releases. The WiGiT Group expects to perform this

function for the wireless grid community of users and developers and will establish a library of

shared resources.

2.7 Assumptions and Dependencies

The Wireless Grid technology is based on known wired and wireless network protocols and

network architectures such as OSI and TCP/IP. The Wireless Grid is compatible with but not

dependent upon these networking models. The intent of the technology is to enable

interoperability between and among these and other existing networks, such as cellular

telephony, satellite communications, cognitive radio and more, the obvious assumption and

dependency is that these technologies will continue to exist. However, the flexibility of the

Wireless Grid is such that it will be adaptable to new and emerging systems and devices.

3. System Features and Components

The blue boxes in Figure 5 represent edgeware applications that sit on a user interface which in

turn sits on an API. These may represent dozens or hundreds of different sorts of mini-programs

that enable different kinds of resource sharing and functionality. Edgeware applications are

typically delivered as a service; and come in 2 primary varieties: gridlets, that is, proprietary

edgeware applications, and wiglets, that is, non-proprietary open edgeware applications. Not all

devices enabled on a wireless grid need to have an edgeware application sitting on them to be

accessible and active. The only thing that must be deployed for a wireless grid to work is for the

Grid Core to be on some intelligent machine, somewhere, with rights to control other ‘edge’

resources such as sensors that may not have the capability to have the core components installed;

which may be facilitated by one or more gridlets and/or wiglets. Other network hardware,

software, services, and content may be controlled and shared through the wireless grid

‘edgeware’. These may not be or cannot become self-aware devices on the grid. However, if

those ‘edge’ resources are in a relationship with other hardware, software, and services which are

part of the wireless grid, they may function as if they were fully cognitive. A further

11

differentiation in the varieties of edgeware applications may also be drawn between peer to peer

implementations, and cloud to edge applications which may appear at first glance to be a basic

client-server implementation. In both cases however, the edgeware application may be able to

interact dynamically with other types of edgeware applications. Meaning, the architecture and

open specifications presented here allow for ad hoc, peer to peer applications and services to

interact with cloud services.

The Core components are represented by the green box and embedded in certain devices or

sensors depending on their capability. This makes every device a node on the wireless grid.

This core is extremely ‘light’ and easy to embed on a wide range of different kinds of equipment.

Users are allowed to share and manage the digital resources at their fingertips through

applications of the architecture’s eight core components.

Figure 5 A Grid Core (courtesy of WiGiT Lab & WGC, 2013)

The wireless grid architecture core components handle four primary functions: management of

identification (ID) and presence, permissions management, data transfer ability, and

API/interfacing. These are the elements that make the grid-enabled ecosystem possible. The

layers above the core are comprised of the API which enables connections with other

applications and services, the User Interface (which may or may not be necessary depending on

the device upon which it sits), and finally the edgeware applications are shown in blue. Once a

grid is established then resources can be published or accessed across the grid, enabling the

infinite functional possibilities of the Grid technology.

There are three classes of wireless grid applications:

Class 1: Applications aggregating information from the range of input/output interfaces

found in nomadic and mobile devices.

Class 2: Applications utilizing the locational and contextual characteristics in which the

devices will be found.

Class 3: Applications leveraging the mesh network capabilities of groups of devices.

12

3.1 System Logical Components Overview

3.1.1 Everything as a Service and Bring Your Own Device

This new computing model allows people use their web browsers to access a wide range of

‘cloud services’ available on-demand over the Internet without installing packaged software

applications on end-users’ computers. In the future, the intelligent cloud service gives users a

seamless, consistent experience across all of the different devices the users own, and all of the

various on-demand services they care about. (Shane Robison, 2008)

Smarter devices and more intelligent networks help deliver this new category of services, and

software is the important element that powers these new services and shapes the quality of the

user experience. But Software as a Service is not the comprehensive solution; the future state is

everything will be delivered to users as a service, from the work life to entertainment to various

communities. Individuals and businesses will have full control to customize their computing

environments by dynamic cloud-based offerings and to shape the experiences they want to have.

(Shane Robison, 2008)

BYOD is a business policy of employees bringing personally owned mobile devices to their

work place and using those devices to access privileged company resources such as email, file

servers and database as well as their personal applications and data.

Business values include mainly the 3 following perspectives:

Productivity: Business people, especially for the financial services employees, have on-demand

access to more information and the tools to use it. Also they can more readily collaborate and

share information, expertise, and other resources. For IT staff, they can spend much less effort on

operations and management of everyday information systems and can focus more on technology-

enabled business improvement which can bring in more profit for the company.

Agility: With on-demand access to modular information assets, people can assemble new

business capabilities and bring innovations to market quickly. They can then scale those

innovations up and integrate them into business operations with minimal disruption.

Profitability: Commodity services like email and collaborative workspaces can be provisioned at

lower cost because of the scale economics of the public cloud. The cost of using and maintaining

business applications can be reduced. Additionally, with pay-by-usage, the ongoing cost of

applications and other services will decline and align with real business need. By optimizing the

distribution and management of workloads across public, private, and hybrid clouds, an

organization can obviously lower its total infrastructure and personnel IT spend. What is more,

the footprint and cost (including energy cost) of its physical infrastructure is reduced, and

traditional data center costs is declined significantly.

13

Other benefits contain manageability, information access, new capability deployment,

coordination and collaboration, business continuity and security, business invocation, growth,

and etc. (Source: Optimizing the journey to the cloud: balancing trust, economics, and

functionality, EMC perspective)

3.1.2 A Reference Architecture Comparison: VPC/WPaaS/CIaaS

Workplace as A Service (WPaaS), Compute Infrastructure as a Service (CIaaS) and Virtual

Private Cloud (VPC) are reference architectures that potentially can meet the unique

requirements to satisfy enterprise-grade customers. VPC fully implemented implies WPaaS and

CIaaS development for enterprise-grade operations. We define “enterprise-grade” as the ability

to deploy business critical services that match or exceed the level of security, quality, reliability,

and availability found in internal corporate data centers. VPC enterprise level requirements are

typically not cost effective or practical to implement for external public clouds and a general

purpose customer base. VPC requirements include:

High levels of automation, including automated provisioning and dynamic configuration of

diverse workloads and multi-tier application topologies including web servers, application

servers, database servers, security components (e.g. firewalls) and infrastructure

components (e.g. DHCP).

Unified workload management interface across all internal and external cloud providers.

A vendor agnostic solution that is not locked into a hardware vendor, software vendor, or

service provider.

Portability to move running workloads from one physical host to another in an automated

manner.

The ability to create and enforce automated workload management policies for stateless

computing architectures including:

Instance management (e.g. creating and deleting VMs, starting and stopping

VMs, etc.)

Storage configuration and management (e.g. creating and deleting storage

volumes, attaching volumes to VMs, initiating backups/snapshots, etc.)

Network configuration and management (e.g. VPN, NAT, VLANs, IP address

overlays, etc.)

Security configuration and management (e.g. creating and deleting security

zones, dynamically configuring firewalls in accordance with security zones,

etc.)

User account management (e.g. authentication and authorization)

Service level management (e.g. instance scalability limitations, automated

recovery, etc.)

Capacity management (e.g. auto-scaling, cloud-bursting, etc.)

14

Encryption services for data in transit and for data at rest.

Secure management of encryption keys (including private key certificates or pre-shared keys).

Flexible reporting including support for billing and accounting processes and the capture of historical data for predictive usage models and analytical efforts.

Integrated monitoring and metering of workloads, including monitoring of bandwidth, performance, latency, storage, etc., provided through a portal or an AP.

VPC is a modular, flexible design with minimal complexity. The VPC reference architecture has

four major components: workload lifecycle management, automated infrastructure as a

service, zoned security model, and optimized physical infrastructure.

Figure 6: VPC Reference Architecture Overview

(Source: TM Forum, TR174 Addendum C V0.1 Enterprise-Grade Virtual Private Cloud from a State-of-the-Art Implementation, 2012)

Based on results which were tested and validated in a lab environment, VPCs offer an agile and

less costly IT operating model for enterprise customers. These results show that VPCs can be

implemented rapidly and that they deliver high levels of automation and time savings. They

also operate VMs at costs up to 75% less than comparable public cloud offering. (TM Forum,

TR174 Addendum C V0.1 Enterprise-Grade Virtual Private Cloud from a State-of-the-Art

Implementation)

E d g e w a r e

15

The Resource Sharing Protocol (RSP) is the primary Grid function provided by the eight core

components.

Authentication and Authorization

Component (AAC)

Billing, Accounting, and Charging

Component (BAC)

Messaging and Presence Component

(MPC)

Metadata Component (MC)

Resource Management

Component (RMC)

Economic and Legal Policy Component

(ELP)

Communication Protocols Component

(CPC)

Security Component (SC)

Resource Sharing Protocol (RSP) Open API

External users, apps, devices, etc

Menu

Figure 7: Open API Map (Source: Lee McKnight & Ying Lu)

The RSP enables creating, joining and subscribing to a wireless grid through provision of the

following services:

○ Resource Identification

○ Resource Acquisition

○ Resource Advertisement/Discovery

○ Communication among wireless grids

○ Communication with the internet

○ Creating a wireless grid

○ Joining and subscribing to a wireless grid

The eight core components discussed in detail below are the functional elements and components

needed to create a wireless grid.

3.2 Authentication and Authorization Component (AAC)

The Authentication and Authorization Component (AAC) – This is the component that handles

the authentication of the user and the authorization of resources. In effect, the AAC provides the

protocols to identify the individual and understand that individual’s relationship to a resource,

i.e. what the individual can or can’t do with a resource. This component must also provide

protocols to manage multiple identities mapped to a given resource; possibly in later, more

advanced iterations of the core, in order to support the abstractions of multi-layered access that

16

the AAC should support. The AAC does not manage permissions. Permission management is

handled through the meta-data in the resource.

The AAC utilizes a Global Unique Identifier (GUID). Every grid creates with it a globally

unique identifier that is used by all grid members.

The AAC has an identity system that looks at users across all their devices and allows policies to

be made regarding the user’s grid profile – without the user having to think about all of their

user/device accounts. At the enterprise level, this identity system may look at users across their

office-related devices and accounts. A tremendous potential exists here for integration with

combined social network offerings that bring together services like Facebook and Twitter®, and

provides a way to access some subset of features from outside the consumer/home office through

a web browser and mobile phones.

The AAC incorporates a policy engine based on the notion of identity that allows users to make

simple statements such as “visitors cannot access my shared photos”, or “Kevin cannot use the

Internet after 8pm.”

3.3 Billing, Accounting, and Charging Component (BAC)

The BAC segment highlighted many benefits that are attractive to banks in particular. The

WiGiT can offer extraordinary improvements to service for many of the largest banks in the

world. The customers of these large banks will be able to securely access all of the information

regarding their accounts from any location they want so long as the customer has either internet

or 3G access at the time. The infrastructure will offer the customer an all-in-one experience as

they will be able to view all accounts and transactions from one interface. (Goldsmith, Kettel and

Chen, 2012) The technology can help banks save money from reduced overhead costs and

potentially provide better service to end users. Bank and other financial institution employees

will also see benefits from using the WiGiT platform. Employees who are preparing documents

for their clients will have instant access to all financial information they need from one place.

For instance, a mortgage officer preparing a mortgage for a client who is trying to buy a house

will be able to prepare the mortgage must faster than what has currently been possible in the past

with the use of the legacy systems that are not integrated. (Goldsmith, Kettel and Chen, 2012)

Assuming the WiGiT platform is integrated with the three major credit agencies; the mortgage

officer will be able to instantly view a person’s credit scores. This is currently a process that

takes days or even weeks as bank employees need to contact credit agencies and credit reports

are then individually sent to the banks in whatever timeframe the credit agency wishes to operate

at. Another benefit that bank employees will realize is the ability to access all of the before

mentioned information in a secure manner from any location that they wish to access the

information from. (Goldsmith, Kettel and Chen, 2012) Bring Your Own Device is becoming a

necessity as employees are working from remote locations. The banks and their employees will

see the greatest benefits from the adoption of the WiGiT platform and the efficiency that will

come from the use of the platform will be immense.

17

See also: McKnight, L. M. , J Howison. J. (2003), Towards a Sharing Protocol for Wireless

Grids. In Proceedings of the International Conference on Computer Communication and Control

Technologies. CCCT '03, Orlando, Florida, USA, July 31 - August 2, 2003.

See also: Term Paper from IST 456, Professor: McKnight; Team Member: Paul Goldsmith,

Kevin Kettel, Maggie Chen, 2012

3.4 Messaging and Presence Component (MPC) The Messaging and Presence Component (MPC) – This is a scalable messaging and presence

system. It manages the availability of a resource and the method or language of communication

with that resource. The messaging and presence component remains under development.

3.5 Metadata Component (MC) The Metadata Component (MC) – This component creates, edits, and generally manages the

metadata for a resource, i.e. it facilitates the creation of metadata around resources. For example,

this resource is a File with a name of “fall events calendar.pdf” that belongs to Dave, and is

accessible on his laptop. This metadata component from an interface perspective in later

iterations of the core can look like a dynamic, advanced search tool allowing for user-defined

tags to drive the process of identifying which resources need to be manipulated at any given

time.

3.6 Resource Management Component (RMC) The Resource Management Component (RMC) – This component is responsible for aggregating

and searching metadata about resources within the context of authentication, it therefore works

closely with the AAC and MPC. In actual fact this component may be considered extended

functionality of the MC, but defining its operation separately here is useful for clarity. The RMC

must be tied methodically to the function of the user interface to support the richness of the

search mechanisms supported by the MC.

The RMC has a scheduler to manage and coordinate resources, such as video recorders, network

access, lights, air conditioning, and security systems, and a virtual file system that seamlessly

integrates files from any of the multiple machines that a user has access to.

The RMC provides a search mechanism that allows a user to find files that may be on their

laptop, desktop, or on their mobile phone.

The RMC Grid advertising/discovery protocol allows for devices to be identified as being

available. A Grid “hello” packet is established

18

3.7 Economic Legal and Policy Component

Microsoft

Alcatel Lucent

W-Pass

UBS

P1P2

P3

Policy Governance Compliance

Proof Point 1

Proof Point 2

Proof Point 3

CLOUD OPERATING MODEL

Boundary

API

OS

Figure 8: Cloud Operating Model – Policy, Governance, Compliance

(Source: ECLC, New York, Sept. 25, 2012.)

Business Policy, Corporate Governance, and Compliance policies are necessary for

edgeware applications to provide service to large enterprises and other

organizations with stringent procedural reporting and legally mandated monitoring

obligations. While cloud services can be configured to maintain conformance to

economic, legal and policy conditions and reporting obligations, truly assuring

compliance – without use of wireless grids edgeware – can be challenging in a

19

cloud and especially multi-mobile cloud environment. WiGiT v0.2 is architected to

meet the cloud operating model conditions of policy, governance and compliance

assurance, that the Enterprise Cloud leadership Council envisions for Workplace as

a Service has established. See Figure 8 above. Admittedly, in time WiGiT could

run into many more problems in international policies rather than domestic. The

reason for this is because international economics deals more with the flow of

commodities, services, and capital across national boundaries. (Psatha and

Vavassoeur, 2012) Due to the fact that WiGiT works in a global economy,

understanding and implementing these policies would greatly help WiGiT’s

progress.

Areas that WiGiT open specification may eventually align with include exchange

rates, commercial policies, domestic policies, statistical data, productive factors,

and marketing considerations. For WiGiT operations to flow smoothly on an

international level, understanding each of these areas may be required to

effectively understand WiGiT’s needs. (Psatha and Vavassoeur, 2012)

Exchange rates dealt mainly with transactions within a country that are financed by

the country’s own currency, usually through the writing of checks. Due to the fact

that each country has its own currency, the price of one currency in terms of

another can vary greatly which is known as the exchange rate. Many of these

exchange rates vary from day to day due to supply and demand conditions in the

foreign exchange markets. Such international transactions require payments in

foreign currencies, which mean that the domestic currency needs to be converted.

This process introduces some risks and complications that don’t exist in domestic

trade which WiGiT needs to incorporate in order to avoid problems when buying

or selling products and services internationally. (Psatha and Vavassoeur, 2012)

Another and more complicated factor that WiGiT needs to pay attention to is

commercial policies. A national government may introduce new restrictions on

international transactions that cannot be imposed on domestic transactions. Such

restrictions can include tariffs, import quotas, voluntary export restraints which is a

negotiated quantitative limitation on the export of certain commodities between

countries, export subsidies, and exchange control which is a restriction that a

country places to not allow the conversion of currency. Such measures can have a

major effect on WiGiT and their operations when dealing with international

transactions. (Psatha and Vavassoeur, 2012) Other countries can consider some

transactions that WiGiT makes unlawful, which is why understanding the

commercial policy is so important.

20

Statistical data is also an aspect that WiGiT needs to pay attention to when only

dealing on an international basis. If WiGiT needed to move a product within the

US, there would be no problem, but when moving products in and out of the

country, WiGiT would need to fill out a declaration describing its weight, value,

destination, size, direction, and other characteristics. All countries require these

regulations. (Psatha and Vavassoeur, 2012) Understanding that WiGiT is an

organization that deals with numerous projects such as the iDAWG and wireless

grid technology, they need to understand the importance of relative immobility and

productive factors. Factors of production are obviously much more mobile

domestically than they are internationally. There are no restrictions that WiGiT

would need to face when moving workers or products domestically like there are

internationally. Immigration restrictions, language barriers, and different social

customs can halt mobility between countries for WiGiT employees.

The last area that we focused on was marketing considerations. Understanding this

concept is very important for WiGiT because differences in demand patterns, sales

techniques, market requirements and the overall “like factor” make international

transactions difficult to deal with (Psatha and Vavassoeur, 2012). What this means

is that WiGiT will need to make special adjustments on their product design if they

wish to enter the foreign market.

Source: Term Paper From IST 456, Professor: McKnight; Team Member: Anthony

Psatha & Gerren Vavassoeur

The Dynamic Coalition on Internet Rights and Principles of the UN Internet

Governance Forum developed a Charter of Internet Rights and Principles, which is

accessible at http://internetrightsandprinciples.org/campaign/. While expecting

WiGiT developer and user communities to uphold the entire Charter, the 10

Internet Rights and Principles summary is appended below, as a reference.

10 Internet Rights and Principles

1) Universality and Equality

All humans are born free and equal in dignity and rights, which must be respected,

protected and fulfilled in the online environment.

2) Rights and Social Justice

21

The Internet is a space for the promotion, protection and fulfillment of human

rights and the advancement of social justice. Everyone has the duty to respect the

human rights of all others in the online environment.

3) Accessibility

Everyone has an equal right to access and use a secure and open Internet.

4) Expression and Association

Everyone has the right to seek, receive, and impart information freely on the

Internet without censorship or other interference. Everyone also has the right to

associate freely through and on the Internet, for social, political, cultural or other

purposes.

5) Privacy and Data Protection

Everyone has the right to privacy online. This includes freedom from surveillance,

the right to use encryption, and the right to online anonymity. Everyone also has

the right to data protection, including control over personal data collection,

retention, processing, disposal and disclosure.

6) Life, Liberty and Security

The rights to life, liberty, and security must be respected, protected and fulfilled

online. These rights must not be infringed upon, or used to infringe other rights, in

the online environment.

7) Diversity

Cultural and linguistic diversity on the Internet must be promoted, and technical

and policy innovation should be encouraged to facilitate plurality of expression.

8) Network Equality

Everyone shall have universal and open access to the Internet’s content, free from

discriminatory prioritization, filtering or traffic control on commercial, political or

other grounds.

9) Standards and Regulation

22

The Internet’s architecture, communication systems, and document and data

formats shall be based on open standards that ensure complete interoperability,

inclusion and equal opportunity for all.

10) Governance

Human rights and social justice must form the legal and normative foundations

upon which the Internet operates and is governed. This shall happen in a

transparent and multilateral manner, based on principles of openness, inclusive

participation and accountability.

(Source: Dynamic Coalition on Internet Rights and Principles,

http://internetrightsandprinciples.org/campaign/)

Affirmation of the Modern Paradigm for Standards

On 29 August 2012, the leaders of the IEEE Standards Association, the IAB, the

IETF, the Internet Society, and the W3C signed a statement affirming the

importance of a jointly developed set of principles establishing a modern paradigm

for global, open standards. These principles have become known as the

OpenStand" principles. This document contains the text of the affirmation that was

signed.

Status of This Memo

This document is not an Internet Standards Track specification; it is published for

informational purposes.

This document is a product of the Internet Architecture Board (IAB) and represents

information that the IAB has deemed valuable to provide for permanent record. It

represents the consensus of the Internet Architecture Board (IAB). Documents

approved for publication by the IAB are not a candidate for any level of Internet

Standard; see Section 2 of RFC 5741.

Information about the current status of this document, any errata, and how to

provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6852.

RFC 6852 Modern Paradigm for Standards January 2013

Copyright Notice

23

Copyright (c) 2013 IETF Trust and the persons identified as the document

authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions

Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the

date of publication of this document. Please review these documents carefully, as

they describe your rights and restrictions with respect to this document.

1. Introduction

On 29 August 2012, the leaders of the IEEE Standards Association, the IAB, the

IETF, the Internet Society, and the W3C signed a statement affirming the

importance of a jointly developed set of principles establishing a modern paradigm

for global, open standards. These principles have become known as the

"OpenStand" principles.

Section 2 of this document describes the five OpenStand principles. Section 3 of

this document contains the text of the signed affirmation of the five OpenStand

principles. Section 4 contains a call for others to support the five OpenStand

principles.

2. Modern Paradigm for Standards

Over the past several decades, the global economy has realized a huge bounty due

to the Internet and the World Wide Web. These could not have been possible

without the innovations and standardization of many underlying

technologies. This standardization occurred with great speed and effectiveness

only because of key characteristics of a modern global standards paradigm. The

affirmation below characterizes the principles that have led to this success as a

means to ensure acceptance of standards activities that adhere to the principles.

We embrace a modern paradigm for standards where the economics of global

markets, fueled by technological advancements, drive global deployment of

standards regardless of their formal status.

In this paradigm standards support interoperability, foster global competition and

collaboration, are developed through an open participatory process, and

are voluntarily adopted globally.

24

These voluntary standards serve as building blocks for products and services

targeted at meeting the needs of the market and consumer, citizens and the public

interest thereby driving innovation. Innovation in turn contributes to the creation of

new products and services including those presented in the marketplace and those

provided in the public interest and towards the development of the Internet as a

global public good.

Participation in the modern paradigm demands:

1. Cooperation. Respectful cooperation between standards organizations, whereby

each respects the autonomy, integrity, processes, and intellectual property rules of

the others.

2. Adherence to principles. Adherence to the five fundamental principles of

standards development:

* Due process. Decisions are made with equity and fairness among

participants. No one party dominates or guides standards development. Standards

processes are transparent and opportunities exist to appeal decisions. Processes for

periodic standards review and updating are well defined.

* Broad consensus. Processes allow for all views to be considered and addressed,

such that agreement can be found across a range of interests.

* Transparency. Standards organizations provide advance public notice of

proposed standards development activities, the scope of work to be undertaken,

and conditions for participation. Easily accessible records of decisions and the

materials used in reaching those decisions are provided. Public comment periods

are provided before final standards approval and adoption.

* Balance. Standards activities are not exclusively dominated by any particular

person, company or interest group.

* Openness. Standards processes are open to all interested and informed parties.

3. Collective empowerment. Commitment by affirming standards organizations

and their participants to collective empowerment by striving for standards that are

chosen and defined based on technical merit, as judged by the contributed expertise

of each participant; provide global interoperability, scalability, stability, and

resiliency; enable global competition and collaboration serve as building blocks

25

for further innovation; are inclusive and are directed to support the broadest base

of inclusion including for those with disabilities, those in rural and remote

locations, and those of modest economic means contribute to the creation of global

communities, benefiting humanity.

MG: WHAT ABOUT CONTRIBUTING TO THE PUBLIC INTEREST AND TO ENABLING THE DEVELOPMENT OF THE INTERNET AS A GLOBAL PUBLIC GOOD?

4. Availability. Standards specifications are made accessible to all for

implementation and deployment. Affirming standards organizations have defined

procedures to develop specifications that can be implemented under fair

terms. Given market diversity, fair terms may vary from royalty-free to fair,

reasonable, and non-discriminatory terms (FRAND) and including those which are

non-market based

5. Voluntary adoption. Standards are voluntarily adopted and success is

determined by the market, their contribution to the public good among other

criteria.

3. Affirmation

We embrace a modern paradigm for standards where the economics of global

markets, support for the public good at national and global levels, fueled by

technological advancements, drive global deployment of standards regardless of

their formal status.

In this paradigm standards support interoperability, foster global competition and

collaboration, are developed through an open participatory process, and are

voluntarily adopted globally. These voluntary standards serve as building blocks

for products and services targeted at meeting the needs of the market and

consumer, citizens and the public interest thereby driving innovation.

Innovation in turn contributes to the creation of new markets and public benefits

and the growth and expansion of existing markets and realization of public

developments in the public interest.

Affirmation of the Modern Paradigm for Standards

draft-iab-modern-paradigm-01, Housley, et. al.

Expires: 20 April 2013 INTERNET DRAFT 6 September 2012

26

Over the past several decades, the global economy has realized a huge bounty due

to the Internet and the World Wide Web. These could not have been possible

without the innovations and standardization of many underlying technologies. This

standardization occurred with great speed and effectiveness only because of key

characteristics of a modern global standards paradigm. The affirmation below

characterizes the principles that have led to this success as a means to ensure

acceptance of standards activities that adhere to the principles.

We embrace a modern paradigm for standards where the economics of global

markets, fueled by technological advancements, drive global deployment of

standards regardless of their formal status.

In this paradigm standards support interoperability, foster global competition, are

developed through an open participatory process, and are voluntarily adopted

globally. These voluntary standards serve as building blocks for products and

services targeted at meeting the needs of the market and consumer, thereby

driving innovation. Innovation in turn contributes to the creation of new markets

and the growth and expansion of existing markets.

Participation in the modern paradigm demands:

1. Cooperation. Respectful cooperation between standards organizations, whereby

each respects the autonomy, integrity, processes, and intellectual property rules of

the others.

2. Adherence to principles. Adherence to the five fundamental principles of

standards development:

* Due process. Decisions are made with equity and fairness among

participants. No one party dominates or guides standards development. Standards

processes are transparent and opportunities exist to appeal decisions. Processes for

periodic standards review and updating are well defined.

* Broad consensus. Processes allow for all views to be considered and addressed,

such that agreement can be found across a range of interests.

* Transparency. Standards organizations provide advance public notice of

proposed standards development activities, the scope of work to be undertaken,

and conditions for participation. Easily accessible records of decisions and the

27

materials used in reaching those decisions are provided. Public comment periods

are provided before final standards approval and adoption.

* Balance. Standards activities are not exclusively dominated by any particular

person, company or interest group.

* Openness. Standards processes are open to all interested and informed parties.

3. Collective empowerment. Commitment by affirming standards organizations

and their participants to collective empowerment by striving for standards that:

* are chosen and defined based on technical merit, as judged by the contributed

expertise of each participant; provide global interoperability, scalability, stability,

and resiliency; enable global competition; serve as building blocks for further

innovation; and contribute to the creation of global communities, benefiting

humanity.

4. Availability. Standards specifications are made accessible to all for

implementation and deployment. Affirming standards organizations have defined

procedures to develop specifications that can be implemented under fair terms.

Given market diversity, fair terms may vary from royalty-free to fair, reasonable,

and non-discriminatory terms (FRAND).

5. Voluntary adoption. Standards are voluntarily adopted and success is determined

by the market.

http://tools.ietf.org/html/draft-iab-modern-paradigm-01

<Note for v0.3: Need to Modify Open Standards doc to meet Michael Gurstein’s

criticisms>

3.8 Communication Protocols Component (CPC) The Communication Protocols Component (CPC) – This is a sub-system that manages the

communication protocols needed to interact with specific types of resources, such as Printers,

Files, Service Accounts, etc. The CPC Manages the communications protocol needed to interact

within a wireless grid, and identifies and manages network and internetwork communications.

The CPC includes IP and other protocols (eg Bluetooth), providing connections with other

wireless grids and across the internet. The Communication Protocols Component is still under

development. Note however that the framework has been expanded since v0.1 to include Zigbee

and 802.22; and explicitly assumes IPv6. See Figure

28

3.9 Security Component (SC) Security Component (SC) – Security component is built of five sub components of each of the

listed core components above; AAC, MPC, MC, RMC and CPC. Security has three levels: grid

owner, user access control, and guest. The security capabilities for each core component are

listed below.

AAC: three levels of authentication: simple, crowd, centralized authentication and three levels of

authorization: open (minimum security, maximum accessibility), restricted (uses locally defined

access control list) and managed (uses grid defined policy-based access control).

MPC: Security is derived from resource metadata

MC: Metadata component uses a distributed database describing resource and user profile.

RMC: Security component includes scheduled authorization monitoring and access verification,

resource denial of service protection:

○ End-to-end security and trust

○ Content Monitoring vs Privacy

○ Distribution Volume Tracking Systems

CPC: denial of service protection for network communication, protection mechanisms for

resources and metadata

While many of the attacks are common across wireless environments, the highly distributed and

collaborative nature of the wireless cloud will have to take on increased security protocols to

protect against threats from the wireless grid environment, the cloud environment and the data

transported from the cloud to the grid (see Figure 9, Wireless Cloud Threat Model). While

threats focus on specific attacks to computing environments, the model below takes into

consideration that threats should consider the skill of the attacker, their propensity to actually

launch an attack, their concern for risk of detection or attribution and the likelihood of success.

The assumption is that the most highly skilled, motivated hackers would attack organizations that

implement a wireless cloud within its environment. [5]

29

Figure 9 : Wireless Cloud Threat Model

Therefore, in a secure wireless cloud environment, organizations will need to shift their focus

from perimeter-based security models to a service-level view of security, with emphasis not so

much on ownership and control, but on network identities, trust, and authorization of both users

and applications. The architectural construct of a secure wireless cloud computing environment

is identified in Figure 10 [9] identifies the wireless cloud as a natural extension of the wireless

grid, which provides seamless access to the internet, networked devices and computing

capabilities. The wireless cloud is a kind of next-generation wireless grid, an emerging

technology and the publication on it is limited [9].

Figure 10. A Future Wireless Cloud Security Architecture

The wireless cloud security architecture is purposely kept technology-agnostic: there is no

mention of any specific wire protocols, interfaces, or data models, except that everything will be

web services based since the WiGLET interfaces directly with the cloud. Over time, the security

30

standards will evolve and new standards will continue to emerge and the conceptual architecture

will not be inherently stable and may not remain the same. For this architecture, data exchanges

will be transmitted through the use of encrypted data via a secure tunnel EAP-TLS/TTLS [10,

11]. This secure tunnel provides a secure interaction amongst the WiGLET and the Cloud

software. A security token-based authentication (e.g. x.509 certificates) model could be used

before invoking any secure web services. A cloud client needs to explicitly authenticate itself to

a security token service which is one of the services offered by the WiGLET. After successful

authentication, the client will be given a one-time security token, which is then passed in the

regular web service request message to invoke a target service. The token essentially establishes

a session whose duration is the lifespan of the token. During the session, the client can use the

same token to invoke any services (subjecting to the local access control policy of course) and

doesn‟t have to be authenticated again, thereby achieving service-level Single Sign-On (SSO).

Compared with the direct authentication model specified in the WS-Security [WSS] standard

[12], this approach improves performance by eliminating per-message authentication overhead,

which is quite significant when asymmetric key exchange is involved.

4.1 Hardware Requirements

The radio components support the connectivity for wireless grid, and also carry the information

exchanging functionalities among heterogeneous nodes.

4.1.1 Connectivity

Each node shall have at least one radio. This radio provides the connectivity between the service

request node and service nodes, or between the service request node and one access point to

wired networks, which connects the service nodes. The radio components may have capabilities

to access multiple wireless standards. A radio combo module may include multiple standard

radio interfaces, such as WiFi and Bluetooth. It may be one ultra wideband software defined

radio supporting those commercial wireless standards. The radio may have capabilities to hand

over among different wireless access networks. The radio may maintain connections to two

different wireless systems while executing this hand over process. The radio components may

support both remote access and local access. Remote access may be supported with cellular

networks or WiFi networks. Local access may be supported with shorter-range wireless

standards, such as Bluetooth and Zigbee. Ad-hoc or mesh networks are an option for

connectivity when hierarchical systems are not available or a different option is preferred. Co-

existence mechanisms among multiple radios may be defined by each system.

4.1.2 Protocol

Service access and service provision may map to different physical channels in terms of

frequency, time, or code. The protocols and interfaces of Wireless Grids run within the

31

application layer, which may be carried by commercial wireless standards, such as WiFi and

cellular. TCP and UDP may be used as data communication protocol.

4.1.3 Power Consumption

Battery life reduction should be less than 25% for nodes joining wireless grids compared their

free-run mode. Power efficient platforms may be introduced in order to reduce power

consumption. Resource management may be introduced in order to improve the power

efficiency.

4.1.4 Platforms

The devices joined into a wireless grid include but are not limited to sensors, mobile devices,

personal computers, and high performance servers.

4.2 Software Requirements

Software components allow wireless grids to dynamically interconnect cell phones, Macs and

PC’s based on multiple software platforms such as droid OS, Mac, IOS, or Android. Specified

software modules that account for these and other devices/applications are based on the logical

components outlined in section 3.0.

4.3 Data Interfaces

(AUDIO, VIDEO (files, documents, unstructured data, streams), IMAGING, DOCUMENTS

(text files, etc.) AUDIO

This section describes interfaces for wireless grids. More details for general grid systems can be

found in reference [3]. Figure 5 shows the transactions for an example of the resource sharing

protocol described in section 3.0. This process can be divided into two phases. The first phase is

the service access phase and the second is the service provision phase.

32

Figure 11 Resource Sharing Protocol (RSP)

Service access phase

Service request node sends out resource discovery and issue service request once received

response from service nodes. Service nodes response to service request node with their resource

reservations. Service request node responses with a resource reservation acknowledgment. Then

service request node gets access to the resource.

Service provision phase

Service nodes share their resource with service request node. Both service request and service

nodes monitor the usage and exceptions of resource. When service is done, the resource will be

released or recycled.

33

There are several types of interfaces dedicated to wireless grids systems. Each interface can be

included into one frame with several control domains.

Resource Discovery: Resource discovery can be used for a service request node to search for its

desired resource. Broadcasting protocol should be used.

Source ID (SID):

Definition: ID used to identify the node that issues resource discovery.

Value: IP address

Example: 192.168.1.1

Description: the node has an ip address of 192.168.1.1

Resource Type(RTP):

Definition: description of resource type.

Value: 0-255. 0-127 for software; 128 -255 for hardware.

Example: 0

Description: the node has type 0 resource (software, hardware)

Methods (MET)

Definition: Methods for resource discovery.

Value: 0-31: 0-15 for time based, 16-31 for propagation based.

Example: 16

Description: Flooding method.

Timestamp (TIM):

Definition: time when resource discovery issued.

Value: GMT

Example: 06:00AM 02/01/2012

Description: Resource discovery issued on 06:00AM 02/01/2012

Expire Time (EXP)

Definition: The period after which the receiver can ignore the discovery.

Value: 0-24hrs.

Example: 2 hours

Description: resource discovery can be ignored after two hours from its issued time.

Restrictions (RES)

Definition: policies of restrictions.

Value: 0-16.

Example: 0

Description: resource discovery cannot go beyond 10 hops.

Resource Description: resource description can be used by service node to broadcast its

available resource.

34

Node ID (NID):

Definition: ID used to identify the node that the resource attached to.

Value: IP address

Example: 192.168.1.1

Description: the node has an ip address of 192.168.1.1

Resource Type(RTP):

Definition: description of resource type.

Value: 0-255. 0-127 for software; 128 -255 for hardware.

Example: 0

Description: the node has type 0 resource (software, hardware)

Availability_T (AVT):

Definition: The period when the resource is available

Value: GMT

Example: 01:00AM 02/01/2012- 01:00AM 02/02/2012

Definition: The resource will be available for 24 hours.

Availability_A (AVA):

Definition: The area where the resource is available

Value: IP on Gateway

Example: 192.168.XXX.XXX

Description: all the nodes within 192.168.XXX.XXX domain can share this resource.

Restriction (RES)

Definition: rules for restrictions

Value: 0-16

Example: 0

Description: This resource has a restriction rule type 0.

Resource Reservation: resource reservation provides an interface for the reservation of resource

along with an authorization.

Source ID (SID):

Definition: ID used to identify source node.

Value: IP address

Example: 192.168.1.1

Description: the service request node has an ip address of 192.168.1.1

Destination ID (DID):

Definition: ID used to identify destination node.

Value: IP address

Example: 192.168.1.2

Description: the service node has an ip address of 192.168.1.2

Resource Type(RTP):

Definition: description of resource type.

35

Value: 0-255. 0-127 for software; 128 -255 for hardware.

Example: 0

Description: the node has type 0 resource (software, hardware)

Method (MET):

Definition: resource request methods.

Value: 0-16

Example: 0/1

Description: 0 Request for one server, 1 request for more than one server.

Timestamp (TIM):

Definition: Length for reservation.

Value: GMT

Example: 06:00AM 02/12/2012

Description: time when a resource request/ack is issued.

Reservation_T (RST):

Value: 0-24hrs.

Example: 2 hours

Description: resource need to be available at least for 2 hours.

Restrictions (RES)

Definition: policies of restrictions.

Value: 0-16.

Example: 0/1

Description: 0 for Preemptive; 1 for non-Preemptive.

TYPE (TYP)

Definition: interface types.

Value: (0,1).

Example: 0/1

Description: 0 for request; 1 for Acknowledgment.

Resource Monitoring: resource monitoring provides a method to monitor the status of the

desired resource. Point-to-point protocol can be used.

Source ID (SID):

Definition: ID used to identify source node.

Value: IP address

Example: 192.168.1.1

Description: the service request node has an ip address of 192.168.1.1

Destination ID (DID):

Definition: ID used to identify destination node.

Value: IP address

Example: 192.168.1.2

Description: the service node has an ip address of 192.168.1.2

Resource Type (RTP):

Definition: description of resource type.

36

Value: 0-255. 0-127 for software; 128 -255 for hardware.

Example: 0

Description: the node has type 0 resource (software, hardware)

Resource Status(RSS)

Definition: status of resource.

Value: 0/1.

Example: 0

Description: 0 for idle; 1 for busy

Method (MET):

Definition: resource monitoring methods.

Value: 0-16

Example: 0/1

Description: 0 for polling, 1 for reporting.

Timestamp (TIM):

Definition: time when resource discovery issued or responsed.

Value: GMT

Example: 06:00AM 02/01/2012

Description: Resource discovery issued on 06:00AM 02/01/2012

TYPE (TYP)

Definition: interface type

Value: (0,1).

Example: 0/1

Description: 0 for monitoring interface; 1 for its ack.

Resource Recycle: resource recycle interface can be used to predict the future resource status. It

can also be used to request release a resource immediately.

This interface provides an exit for resource occupation. Both point-to-point and broadcast

protocol can be used.

Source ID (SID):

Definition: node id that the resource attached to.

Value: IP address

Example: 192.168.1.1

Description: the service request node has an ip address of 192.168.1.1

Resource Type (RTP):

Definition: description of resource type.

Value: 0-255. 0-127 for software; 128 -255 for hardware.

Example: 0

Description: the node has type 0 resource (software, hardware)

Resource Status(RSS)

Definition: status of resource.

Value: 0/1.

Example: 0

Description: 0 for idle; 1 for busy

37

Timestamp (TIM):

Definition: time when the resource recycle is issued.

Value: GMT

Example: 06:00AM 02/01/2012

Description: Resource discovery issued on 06:00AM 02/01/2012

Length (LEN)

Definition: length for resource to be occupied in the future.

Value: hours

Example: 2 hours

Description: the indicated resource will be released in 2 hours

Expiration (EXP)

Definition: Expiration time

Value: hours

Example: 3 hours

Description: The resource recycle can not be guaranteed after 3 hours.

5 Other Requirements

5.1 Performance Requirements

<14 Guidelines for Web Accessibility>

1. Provide equivalent alternatives to auditory and visual content

2. Do not rely on color alone

3. Use markup and style sheets and do so properly

4. Clarify natural language usage

5. Create tables that transform gracefully

6. Ensure that pages featuring new technologies transform gracefully

7. Ensure user control of time-sensitive content changes

8. Ensure direct accessibility of embedded user interfaces

9. Design for device-independence

10. Use interim solutions

11. Use W3C technologies and guidelines

12. Provide context and orientation information

13. Provide clear navigation mechanisms

14. Ensure that documents are clear and simple

(cite + link

http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/#themes

38

Universal Access - Disability studies (COTELCO, BBI, CDL) to be included.

(Minimum required level of service and response and quality)

39

Appendix A: Glossary

Ad- hoc UDDI (Universal Description Discovery and Integration): UDDI is a

directory where web service descriptions that follow WSDL (Web Service

Description Language) are registered. Ad- hoc UDDI allows broadcasting of the

services. It has methods to list all its services to a client that does not know what

services are available.

Ad- hoc Environment for Wireless grid: It demands a combination of distributed

(because connection to centralized control cannot be guaranteed) and centralized

architecture (to be scalable, and allow efficient provision of services).

Computing Capability: different platforms may need different computing

capabilities.

Cloud Computing: while there are many different definitions of Cloud computing,

we prefer the following NIST definition as the basis for our understanding of

Cloud Computing: (http://csrc.nist.gov/groups/SNS/cloud-computing/cloud-def-

v15.doc)

“Cloud Computing is a model for enabling convenient, on-demand network access

to a shared pool of configurable computing resources (e.g., network, servers,

storage, applications, and services) that can be rapidly provisioned and released

with minimal management effort or service provider interaction.”

Demand and supply Aggregation: Allowance of wireless device access to near-by

computing devices or wireless systems for proxy-resources (like cached files and

storages). Aggregation of shared processing power provides the availability of

extensive computing and storage power by sharing unused resource of many

personal computers.

The existing concepts of Dialogue Independence and UIMS are extended to

provide users a wide range of different access and interaction mechanisms to the

same underlying data and functionality:

Dialogue Independence: It refers to the separation of user interface-related code

from the rest of the application code. It therefore supports the development of

alternative user interfaces for the same application (semantics).

40

Edgeware: a new class of software that operates at the edges of networks (hence

‘edgeware’) in order to take advantage of the capabilities of grid architecture. The

Wireless Grids Corporation, a corporate sponsor of WiGiT, has developed

commercial applications including WeJay, a social networking applications that

allows music and other file sharing, and several other edgeware application

products that are currently in beta test.

Edge Node (EN): Service node in charge of inter-cluster or remote access

communication.

Grid Architecture: a network architecture that enables resource discovery and

sharing through the formation of virtual wireless grids.

Grid: A grid is a collection of distributed resources that are shared among a group

of users. It schedules and coordinates resources to offer a diverse collection of

services over a network of connected devices. It defines methods to define, create,

discover, and manage distributed services.

Leader Node (LN): Service node in charge of resource allocation and monitoring

within a service cluster.

IaaS or (Cloud) Infrastructure as a Service: A generic term for the provision of

core IT infrastructure technology components as a service, with defined service

levels and flexible billing.

There is also an explicit demarcation of responsibility, with the service provider

taking responsibility for the provision of the underlying cloud service, including

data centers, communication, hardware, virtualization, orchestration, and

management up to the virtual machine, and the consumer taking responsibility for

the OS, databases, middleware, and applications hosted on the IaaS service.

Note that IaaS can be provided internally or externally to an enterprise’s data

centers and by the enterprise’s own IT team (acting as an internal service partner)

or provided by an external service partner. In casual language, IaaS is generally

accepted to refer to externally-hosted, externally-provided services from the view

of the enterprise.

Marshalling: Refers to the process of converting native programming language

data types to a format suitable for transmission across a network; the term

41

"unmarshalling" is the conversion of data received over a network from its on-the-

wire representation to data types appropriate to the receiving application.

Nomadic Devices: Refers to devices with the emphasis not on connectivity while

literally in motion, but rather when the user is at various fixed but possibly varying

locations. For example using a notebook computer at a wi-fi hotspot could be seen

as use of a nomadic device.

Network Peering: A form of barter exchange in which interconnecting carriers

agree to exchange traffic at no charge.

Operating Systems: a list of operating systems can be found in [3].

Service Clusters (SC): Clusters formed with multiple service nodes

Service Nodes (SN): nodes response to service requests with desired

hardware/software resources.

Service Process: A typical service process may be divided into two phases:

a.) Service access: SRN send service request to SN through LN. SNs response to

the request based on their own status and observation. LN forms a table

representing the map between service demands and supply.

b.) Service provision: LN makes decisions about resource allocation based on

resource utilization and channel status. SNs start processing service request.

Service Request Nodes (SRN): nodes send out service requests

Sharing Level Agreement: One of the main operations of virtual market that

describes protocols, which define the responsibility of participants within a

wireless communications grid. It not only encompasses the roles and

responsibilities of the users within the grid, but also governs the attainment and

fulfillment of requested resources.

Trusted Computing: Controlling end node behavior by allowing network clients to

ascertain that a peer is running application code without detrimental behaviors like

injecting corrupted content and flooding networks and it excludes misbehaving

clients from the network.

42

Peer-to-Peer (P2P) Networks: These are properly called overlay networks to

emphasize that they run over the existing institutionally owned and managed

infrastructure.

UIMS (User Interface Management System): A software component that is

separate from the application program that performs the underlying task and

supports the concept of dialogue independence.

Virtualization: three types of virtualization methods may be used for wireless

grids: hypervisor, emulator, and OS-level virtualization.

Wireless Grid: a human centric open access gateway to shared resources for

mobile and wireless electronic devices interconnecting at least one device to at

least one other device or resource. A device can establish a grid and become an

member of one or more wireless grids.

WPaaS (Workplace as a Service): Enterprises need a flexible, secure, cloud

services delivery framework for edge applications. The solution described here

delivers end-user computing, communications and collaboration capabilities. We

call that set of world-class services WPaaS.

Appendix B: Analysis Models

V0.3 incorporates and emphasizes standards, including IEEE P2030.4 (Smart Grid

Interoperability Working Group), NIST (Smart Grid Interoperability Panel),

CABA (Continental Automated Building Association), and etc. Also IPV6

Compatible issue is considered.

43

Figure 12. WiGiT V0.3 Open Spec -- Virtual Energy, SmartGrid, Smart Building

Appendix C: Issues List

A listing of issues raised and supported operating systems will be included in the future.

Appendix D: References

[1] Fitzek, F. and Katz, M. “Cellular Controlled Peer to Peer Communications: Overview and Potentials”, Chapter 2 in Cognitive Wireless Networks, Springer, 2007. [2] McKnight, L. W., Lehr, W., & Howison, J. (2003). “Coordinating User and Device Behavior in Wireless Grids, in Inventing the Communications Future”. MIT Media Lab Workshop, 2003. [3] OGF194 from open grid forum: http://www.gridforum.org/ [4] www.cornet.wireless.vt.edu

44

[5] Tyson Brooks, Jerry Robinson, Lee McKnight, “Conceptualizing a Secure Wireless Cloud,”

International Journal of Cloud Computing and Services Science (IJ-CLOSER) Vol.1, No.3, August

2012, pp. 89-114. Journal homepage: http://iaesjournal.com/online/index.php/IJ-CLOSER

[6] Ian Foster, Carl Kesselman, and Steve Teuke, “The Anatomy of the Grid: Enabling Scalable Virtual

Organizations,” International Journal of High Performance Computing Applications, Volume 15

Issue 3, August 2001, Pages 200 – 222. http://dl.acm.org/citation.cfm?id=1080667

[7] H. Luthria and F.A. Rabhi. “Service-Oriented Architectures: Myth or Reality?” IEEE Software, volume

29, issue 4, July/August 2012, pages 46-52.

http://ieeexplore.ieee.org/xpl/articleDetails.jsp?tp=&arnumber=6086531&contentType=Journa

ls+%26+Magazines&sortType%3Dasc_p_Sequence%26filter%3DAND%28p_IS_Number%3A6265

068%29

[8] Dr. Lee W. McKnight, Editor, “Open Specifications for Wireless Grids: Technical Requirements,”

Version 0.2 in process. To appear on http://WiGiT.ischool.syr.edu/index.php/news/96-WiGiTs-idawg-communications-elements-progressing-to-field-test-

[9] Tyson, Brooks., Lee, McKnight. "Securing Wireless Grids: Architecture Designs for Secure WiGLET-to-WiGLET Interfaces", International Journal of Information & Network Security (IJINS), Vol.2, No.1, February 2013, pp. 336-351 [10] J. Chen and Y. Wang, “Extensible Authentication Protocol (EAP) and IEEE 802.1x: Tutorial and Empirical Experience,” IEEE Communications Magazine, vol. 43 (12), pp. 26 – 32, 2005 [11] P. Funk and S. Blake-Wilson, “Extensible Authentication Protocol Tunneled Transport Layer Security Authenticated Protocol Version 0 (EAP-TTLSv0) RFC 5281, 2008 [online], Internet Engineering Task Force, available: http://www.ietf.org/ [Accessed: February 5, 2012 [12] OASIS Open Standards, "Web Services Security (WSS) 1.1," OASIS, 2005 [online] available: http://www.oasis-open.org/standards#samlv2.0 [Accessed: June 15, 2011 [13] Term Paper from IST 456, Professor: McKnight; Team Member: Paul Goldsmith, Kevin Kettel, Maggie Chen, 2012 [14] Term Paper From IST 456, Professor: McKnight; Team Member: Anthony Psatha & Gerren Vavassoeur [15]Dynamic Coalition on Internet Rights and Principles, http://internetrightsandprinciples.org/campaign/ [16] Affirmation of the Modern Paradigm for Standards, http://www.rfc-editor.org/info/rfc6852; http://tools.ietf.org/html/draft-iab-modern-paradigm-01

45

[17] TR174 Addendum C, Version 0.1, Enterprise-Grade Virtual Private Cloud from a State-of-the-Art Reference Implementation, 2012 [18] TR172 - TM Forum Security Management Model, 2013 [19] TR192, Workplace as a Service Requirements, Version 0.3, 2013 [20] TR194, Version 8.3, Multi-Cloud Service Management Accelerator Pack Introduction, 2012 [21] Marco Di Renzo, Luis Alonso, and Frank H. P. Fitzek. “GREENET – An Early Stage Training Network in Enabling Technologies for Green Radio”, IEEE VTC 2011, Budapest : Hungary, 2011, DOI: 10.1109/VETECS.2011.5956211 [22] Shane Robison, Chief strategy and technology officer, HP, The Next Wave: Everything as a Service, 2008, http://www.hp.com/hpinfo/execteam/articles/robison/08eaas.html [23] http://www.pcworld.com/article/246760/pros_and_cons_of_byod_bring_your_own_device_.html [24] Aberdeen Group, “Enterprise-Grade BYOD Strategies: Flexible, Compliant, Secure”, Analyst Insight, 2011, pp. 1-4