The Landscape of Pervasive & Mobile Computing Standards Sumi Helal Synthesis Lectures on Mobile and Pervasive Computing Preface



Download 0.57 Mb.
Page1/45
Date25.06.2017
Size0.57 Mb.
#21767
  1   2   3   4   5   6   7   8   9   ...   45







The Landscape of Pervasive & Mobile Computing Standards

Sumi Helal

Synthesis Lectures on

Mobile and Pervasive Computing

Preface

This lecture presents established or emerging standards that are driving the technological evolution of mobile and pervasive computing systems. The lecture explains the role of each of the covered standards and provides an architecture-oriented taxonomy that explains the relationship and interplay among these standards. Hopefully, the lecture will help piece together the various standards into a sensible and clear landscape.

The lecture is mainly a digest and a compilation of over 15 department articles that have been published in the “Standards and Emerging Tecnologies” column of the IEEE Pervasive Compting magazine. The articles are heavily edited to provide the necessary focus and uniform coverage in this lecture.
Audience who may benefit from this lecture includes: (1) academic and industrial researchers; (2) practitioners from the telecommunication industry especially those concerned with mobile devices and location based services; (3) system integrators (e.g., IBM, GE, Accenture, Telcordia) especially those concerened with integrating sensors and actuators to their enterprise data bus, or those concerned with mobilizing enterprise business processes and supporting mobile workforce in sales and customer relations; (4) device, smart chips, and sensor manufacturers (e.g., Intel, ARM, Marvel, TI); (5) government agencies (e.g., US departments of defense and home land security); (6) the HealthCare IT industry; (7) as well as other industries such as logistics, manufacturing, and the emerging smart power grid and power efficiency industry.

Contents


chapter 1 8

1.1 INTEGRATED ENVIRONMENTS AND THEIR LIMITATIONS 9

1.1.1 Nonscalable integration 9

1.1.2 Closed-world assumptions 10

1.1.3 Fixed-point concepts 11



1.2 THE NEED FOR MIDDLEWARE AND STANDARDS 11

1.2.1 Self-integration 12

1.2.2 Semantic exploitation 14

1.3 PROGRAMMABILITY 15

1.3.1 Who should program a pervasive space? 16

1.3.2 Programming models 17

1.3.3 Integrated Development Environments? 18



Chapter2 20

2.1 JAVA 2 PLATFORM, MICRO EDITION 21

2.1.1 KVM 24

2.1.2 CLDC 27

2.1.3 MIDP 28

2.1.4 Hello World MIDlet 29

2.2 J2ME PLATFORMS 32

2.2.1 Java-enabled phones 33

2.2.2 Java-enabled PDAs 36

2.3 J2ME DEVELOPMENT TOOLKITS 37

2.3.1 CodeWarrior 6.0 39

2.3.2 Zucotto Wireless Whiteboard SDK 39

2.3.3 Sun Forte for Java 42

2.3.4 Borland’s JBuilder 5.0 Personal and Mobileset 42

2.3.5 IBM VisualAge Micro Edition 43

2.3.6 Sun’s wireless toolkit 44

2.3.7 Nokia toolkit (beta) 45

2.3.8 Siemens Mobility Toolkit (beta) 45

2.4 NUTS AND BOLTS 50

2.5 CHOOSING THE RIGHT PROGRAMMING LANGUAGE 52

2.6 BRINGING BIG FEATURES TO SMALL DEVICES 53

2.6.1 The foundation: Execution and memory management 54

2.6.2 The building blocks: The .NET compact framework libraries 55

2.6.3 Making connections: Networking and XML Web services 56

2.6.4 Data is power: Data access 56

2.7 CHALLENGES AHEAD 57

2.8 THE WAP ARCHITECTURE 60

2.9 WAP SUPPORTING COMPONENTS 61

REFERENCE 64

2.10 WAP ADVANTAGES 65

2.11 WAP CRITIQUES 66

2.11.1 WAP as a band-aid 67

2.11.2 Wrong bearer services 67

2.11.3 Weak link 67

2.11.4 WAP designer’s nightmare 67

2.11.5 User experience 68

2.11.6 Killer applications 68

2.11.7 Pricing 69



2.12 THIN VERSUS FAT CLIENTS 69

2.13 DEVELOPING JAVA APPLICATIONS FOR MOBILE DEVICES 72

2.13.1 Games for J2ME devices 73

2.13.2 Optimizing standalone J2ME applications 74

2.13.3 Portability issues 77



2.14 NETWORK APPLICATIONS FOR THE J2ME PLATFORM 79

2.14.1 Distributing information between the client and server 80

2.14.2 Sending information between the client and server 81

2.14.3 Protecting sensitive information on mobile devices 83

2.14.5 User interface issues 85

2.15 J2ME NETWORK APPLICATION CONSTRAINTS 86

chapter 3 89



3.1 Historical perspective 89

3.2 The evolution of LBS features 91

3.2.1 From reactive to proactive 92

3.2.2 From self- to cross-referencing 92

3.2.3 From single- to multitarget 93

3.2.4 From content- to application-oriented 93

3.3 Toward user centricity 94

3.4 Middleware for opening LBS participation 96

3.5 Middleware for avoiding LBS spam 97

3.6 Middleware for privacy preservation 99

Chapter 4 103

4.1 THE STANDARDS 103

4.2 TARGETS AND URCS 105

4.3 HOW THE STANDARDS WORK TOGETHER 107

4.4 ARCHITECTURE 109

4.5 CONFORMITY 110

4.6 MEETING A GROWING MARKET’S NEEDS 111

4.6.1 Challenges 112

4.6.2 Toward solutions 113

4.7 THE UNIFIED WEB 115

4.8 DESKTOP BROWSING ON MOBILE DEVICES 116

4.9 RICH MEDIA 116

4.10 THE BROWSER UI: DYNAMIC MENU TECHNOLOGY 118

4.10.1 Benefits 119

4.10.2 Implementation 122

4.11 UNIVERSAL INTERACTION TECHNOLOGIES 126

4.12 UNIVERSAL UI LANGUAGES 128

4.12.1 W3C XForms 128

4.12.2 INCITS/V2 URC standards 130

4.12.3 UIML, XIML, and PUC 133



4.13 UI REMOTING 134

4.13.1 UPnP RUI 135

4.13.2 Jini Proxy Architecture 136

Chapter 5 140

5.1 SERVICE DISCOVERY PROTOCOLS 141

5.2 JINI 143

5.2.1 Leasing in Jini 145

5.2.2 Distributed programming in Jini 145

5.3 UNIVERSAL PLUG AND PLAY 146

5.3.1 Joining and discovery in UPnP 146

5.3.2 UPnP service description 148

5.3.3 Automatic configuration of IP 148



5.4 SALUTATION 149

5.4.1 Service registration 151

5.4.2 Service availability 151

5.4.3 Service session management 151

5.4.4 Salutation-Lite 152

5.5 SERVICE LOCATION PROTOCOL 152

5.6 BLUETOOTH SDP 154

5.7 MARKET ACCEPTABILITY 155

Chapter 6 159

6.1 THE FRAMEWORK 160

6.2 SPECIFICATIONS 163

6.3 DEVELOPMENT TOOLKITS 164

6.3.1 ProSyst mBedded Builder 164

6.3.2 Java Embedded Server 165

6.3.3 IBM SMF Bundle Developer 165



6.4 ADOPTION AND PRODUCTS 167

6.5 CASE STUDY: MATILDA’S SMART HOUSE 169

Chapter 7 174

7.1 MODELING DEVICES AS SERVICES 175

7.2 HOW A SERVICE-ORIENTED ARCHITECTURE CAN HELP 177

7.3 THE ARCHITECTURE 181

chapter 8 184

chapter 9 185

9.1 Different standards 186

9.1.1 ECHONET 186

9.1.2 IEEE 1451 186

9.1.3 SensorML 187

9.1.4 Device Kit 188

9.1.5 DDL 188



9.2 From plaintext to markup language 189

9.3 Bridging the physical and digital world 190

9.4 Different scopes for different standards 192

9.5 Dissecting Devices 195

9.5.1 Object-oriented perspective 195

9.5.2 Data-oriented perspective 195

9.5.3 Modular perspective 196



chapter 10 198

10.1 INTEROPERABILITY THROUGH INDUSTRY STANDARDS 198

10.2 THE REFERENCE ARCHITECTURE 201

10.3 THE BIG PICTURE 205

chapter 11 208

chapter 12 209

chapter 13 210

13.1 The Birth of the Mote 210

13.2 Berkeley Motes 212

13.3 Smart-Its 214

13.4 Moving into Smart Spaces 216



13.5 Phidgets 219

13.6 Atlas Platform 221

13.7 Re aching into People’s Pockets 223

13.8 Health and Fitness Monitoring 225

13.9 Crisis and Emergency Response 226

13.10 Mobile Environmental Sensing 227

chapter 14 229

14.1 Introduction 229

14.6 Conclusions 238

Appendix I: Contributor Bios 240

chapter 3 242

Chapter 4 243

Chapter 5 245

Chapter 6 245

Chapter 7 246

Chapter 8 246

chapter 9 247

chapter 10 247

Chapter 11 248

Chapter 12 248

NO Chapter 248

References 252

Credit & Acknowledgements 259

Author Biography 260

chapter 1

INTRODUCTION

Programming Pervasive Spaces

Like it or not, tens of billions of lines of Cobol code are still in use today. Invented in 1959 by a group of com­puter professionals, Cobol empowered developers worldwide to program the mainframe and create applications still in existence today. Undoubtedly, Cobol owes much of its success to its standardization, which started with the American National Standard in 1968.

Yet these days, standards alone won’t lead to success. With the invention of the PC and emergence of the network, we realized we also need new concepts and capabilities to program networks of computers. Standards such as TCP/IP and IEEE 802 played a major role in transforming the first computer net­work concept (Arpanet) to the Internet we know today. However, we also had to invent new computing models such as the client-server model, transactions, distributed objects, Web services, dis­connected operation, and computing grids. Furthermore, we had to invent various middleware to support these emerging models, hiding the underly­ing system’s complexity and presenting a more programmable view to software and application developers.

Today, with the advent of sensor net­works and pinhead-size computers, we’re moving much closer to realizing the vision of ubiquitous and pervasive computing. However, as we create per­vasive spaces, we must think ahead to consider how we’ll program them—just as we successfully programmed the mainframe and, later on, the Internet.



Download 0.57 Mb.

Share with your friends:
  1   2   3   4   5   6   7   8   9   ...   45




The database is protected by copyright ©ininet.org 2024
send message

    Main page