270 likes | 455 Views
Chapter 6. Home Networks & Appliances. Introduction. Network Appliance (NA) Dedicated-function consumer device containing a networked processor aka Internet Appliance, network device, network consumer device This Chapter 3 example environments Challenges ahead Potential solutions.
E N D
Chapter 6 Home Networks & Appliances
Introduction • Network Appliance (NA) • Dedicated-function consumer device containing a networked processor • aka Internet Appliance, network device, network consumer device • This Chapter • 3 example environments • Challenges ahead • Potential solutions
Emergence of NA • Decreasing cost of network-capable electronics • Microcontrollers • Network cost negligible • Ease of integration • Increase in online data availability • Pc’s are inconvenient – want smaller • Consumer demand for seamless integration of network services into lifestyle • Want it & will pay for it
Emergence of NA 4. Continuously available network connectivity • Due to broadband & home network • DSL & cable modem allow for on-demand access 5. Emergence of mass market opportunities amenable to appliance technology • Many "things" require network connectivity • Pay-per-view, home power consumption, digital rights management, etc. • Always new things
NA Domains • Environment: bordered by security boundary; single domain under single authority • Different environment may have different constraints; different access technologies • 3 examples • Automobile • PAN • Home
Automotive Environment • Collection of nw separated by performance, safety, cost • Note: Smart Environment doesn't have to be wireless • Example devices: flasher module, stereo, engine sensor, burglar alarm, remote locks or ignition • Remote access: On Star via mobile phone network • User access to NW: not in past • Now Bluetooth • PAN • PDA with display? • Established - because many examples in current vehicles - but how will the expansion occur
PAN • Specific to an individual for personal NA's • PDA, headphone, phone, laptop, medical/body sensors • Individual is identified, access rights • Access to WAN defined by WAN devices present • Bandwidth shared with other PAN's present • Emergent - because established standards & market building • Bluetooth SIG claims > 1M units shipped per week
Home Environment • Collection of networks with inter-networking units between them - Figure 6.1, pg. 133 • Zones: areas serviced by each of the physical networks • WAN Home: Good - DSL, cable, etc. • Multiple users with different rights & responsibilities • Child, adult, visitor • Embryonic - products for network PC's, but few NA specific products & no clear consensus on standards
"Typical" NA's • Can't really predict • Extensions of current vs. new ones • Can identify some capabilities expected • NW will become 'built-in', standard • Driving Technologies • Bluetooth • Zig Bee • Bluejacking - new, unintended use
NA's Can Utilize … • On-demand data availability • Auto updates of firm ware, TV schedules, recipes • Decision making - turn on heat as you approach home, automatically slows your car if car ahead stops suddenly • Dynamic data & information exchange • Music from house to car stereo • Management of rights
NA's Can Utilize …. 3. Remote command & control • Current: garage door, car • Future: open door for repairman & watch via camera; start vacuum cleaner or washer 4. Remote reporting • Deliver status: pipe breaks, need oil change, elderly person hasn't opened refrigerator in 24 hours All require sensor functions + processing
Example Scenario Read about Dave in his Smart World on pages 135-136.
Core Issues of NA Adoption • Cost of network connectivity • Cost is dropping • For homes, still somewhat expensive, inconvenient, difficult to configure • Diversity of network structure • Typically multiple network - gateways between them - electricity, cable, phone • Each may have significant differences • Need homogenous access
Core Issues 3.Complexity - configuration & maintenance • More devices more complexity more maintenance • Security issues • Connect to neighbor's wireless network 4. Security requirements • Most home users do not have skill or understanding to provide own security • NA's need to include
Core Issues 5. Collaborative operation • Weather - monitoring alarm clock wakes you early when bad weather • Integrate with other NA's - collaborative • Start coffee early • Heat water for shower • Wakes early if car needs gas • Body sensor - wakes up if needs medical attention
Core Issues 6. Feature Interaction • Example: heating system 75°, cooling system 70° - goals conflict • The change in operation of one feature that can be wholly or partially attributed to the presence of another feature in the environment
Current State of NA Deployment Domain Dependant Automotive industry is most advanced • Single integration agency • Accepted standards • Safety critical environment demands thorough testing • Strong brand image must be protected • Must reduce cost • Good understanding of technology • Interface extension of older users Compare to PAN and Home!
2 Key Problems • Appliance Addressing & Access • Different devices have different standards • No standard addressing • How to access from outside • Feature Interaction (FI) • Occurs when multiple entities make assumptions about environment which are rendered invalid by other entities • May have no knowledge of other entities
Appliance Addressing & Access Requirements - both inside & outside house • Security • Authentication • Reliability • Scaling • Protocol independence • Naming & location
Addressing / AccessProposed Solution • Communication to NA usually brief • Combine location and message - single transmission • SIP (Session Initiation Protocol) • INVITE Process • Figure 6.2, pg. 141 • Message sent to proxy agents, forwarded • Developed for VOIP • Authors - SIPa is leading contender
SIP Advantages for NA • Proven for security, authentication, reliability, scaling • Independent of any particular naming or addressing scheme • Can register endpoints (appliances) then can move around house • SIP likely to be used in VOIP - good if used for various applications
Not currently deployed: development of infrastructure will take time Open issues remain DDP & DMP not fully defined Provisioning & configuration (others) not resolved SIP Disadvantages
Classification of FI ( p. 144) • Asynchronous Excitation • Service excites device - no feedback • e.g. TV remote control • Don't know service location • Notification followed by Excitation • Stimulus (service) known • e.g. dryer informs service the door closed & service tells dryer to start • Notification followed by Asynchronous Excitation • Stimulus from on device causes service to excite another device • 1st device doesn't know of second
Example FI's • Video recorder switches from TV to record security camera if burglar alarm • Recorded eight sequence for "away from home" sets off burglar alarm • Dueling cooling & heating system
Other Categories of Interactions • Shared action • 2+ services try to control same device • Shared trigger • One event passed to more than one service, which perform conflicting actions • Sequential action • Service to device to service • Can cause loop • Missed trigger • Existence of a service prevents a device from producing an event that causes a second service to operate
State of NA • Feature interaction - vital issue • Only is a problem when enough services deployed for interactions to start • Not a problem with automobile, controlled • Home - we can just keep adding "stuff" • FI is open issue • Slow rate of adoption allows work for solutions
Future of NAAuthor's Predictions • Interface will change beyond recognition • Sophisticated Techniques • Speech, direct eye, in ear loud speakers, throat microphones, direct electrical stimulation • Interfaces that hide computing devices • e.g. Anoto pen • Power delivery - from the human • Cybernetic enhancements • Who knows?!?