1 / 96

Enabling the Internet of Things

Enabling the Internet of Things. Short Range Wireless and M2M. Our Expertise. Intelligent Embedded Wireless Communications. Bluetooth, 802.11, 802.15.4 (ZigBee), Wibree . Wireless agnostic scripting language. Middleware and Data Synchronisation. Low Power, High Efficiency Modules.

ruby
Télécharger la présentation

Enabling the Internet of Things

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Enabling the Internet of Things Short Range Wireless and M2M

  2. Our Expertise Intelligent Embedded Wireless Communications Bluetooth, 802.11, 802.15.4 (ZigBee), Wibree Wireless agnostic scripting language Middleware and Data Synchronisation Low Power, High Efficiency Modules

  3. Serving an embedded market Fast time to market Integrated Protocol stacks and protocol conversion Built in internet connectivity Expertise in Automotive, Medical and Retail Enabling over 5 million credit card transactions daily

  4. Things just want to connect… My temperature is… Your Blood Pressure is… I’ve just driven… I can see… I’ve copied… I’ve sold… Now there’s an easy, wireless way to do it.

  5. The Internet of Things Internet + “Thing” + = M2M Welcome to the world of Cellular-Free communications.

  6. “Things” are “Host-free” • Most machines have very limited host processing capability. • Using External Processors mean more power, more cost, greater time-to-market and the need for expensive programming resource. • The Internet of Things need wireless processors that do everything. • EZURiO provides everything you need in one module.

  7. What Designers Ask These are the Key Features for “Time to Market”

  8. All you need in one package EZURiO modules are pin compatible with Siemens GPRS MC55/56

  9. Enabling your “Thing” RS-232 Data & Commands RF Serial In >>> Wireless Out • No host processing requirements – just send simple commands • Integrated 802.11 driver gives silicon independence • Integrated Bluetooth or TCP/IP stack • Access to I/O and ADC • AT Interface (Bluetooth) • Interpreter (802.11) to run scripts for data acquisition and wireless attachment

  10. What’s in an EZURiO Module? Flash RAM ARM Processor + UW UART 802.11 b/g Connection Scripting Event Handling I/O Power Management

  11. Our Module Architecture ADC DAC GPIO High Speed UART Non-volatile Memory I/O Controller UNIVERSAL WIRELESS Scripting Interpreter Program Memory UWScripts Flash Filing System Wireless Protocol Stack (TCP/IP + Driver) Web Server 128 bit Encryption Baseband AES WEP / WPA Compare “Standard” Wireless Module Radio Everything you need is in one module – it really is “Serial In >>> Wireless Out”

  12. 802.11 Basics Nick Hunn - CTO

  13. US 11 channels EU 13 channels Japan 14 channels Channel Spacing – 5MHz 11 1 1 6 11 11 1 6 802.11b & g channels • 802.11 b & g operate at 2.4GHz – the same frequency band as Bluetooth and ZigBee. • The spectrum is divided into multiple channels, spaced 5MHz apart. • Access Points operate on a fixed, selected channel using DSSS. They do not frequency hop. • There is NO channel width specified, but a spectral mask of -30dm @ + 11MHz Cells (access points) can overlap as long as the transmitter in one does not result in overload in the adjacent cell. This means the channels selected should be 25MHz apart.

  14. 802.11 Architecture - Infrastructure Infrastructure Mode • BSSID - Unique Name – MAC Address • SSID – Access Point Name • BSS Type – Infrastructure Mode Access Point Clients “Clients” ASSOCIATE with Access Points. All 802.11 devices have a unique 48 bit MAC address. If Access Points have the same SSID and are connected to a backbone, then clients can ROAM between them.

  15. 802.11 Architecture – Ad-hoc Ad-hoc Mode First Client Clients The Client starting the ad-hoc network acts as the “Access Point” to which other clients connect. Devices can either connect in Infrastructure or ad-hoc mode. They cannot do both simultaneously. Ad-hoc mode does not support Power Saving modes. Ad-hoc is also known as IBSS (Independent Basic Service Set)

  16. Data Packets Simplified 802.11 packet Only a relatively small part of each transmitted packet contains data. A lot of the transmitted information is concerned with routing information, protocols and integrity checking. The data rate is shared between all connected clients. Real Data throughputs never match symbol rates.

  17. 802.11 Range and Throughput Symbol Rate Symbol Rate Range (m) Throughput (Mbps) Range and throughput are closely linked – the more complex the coding scheme, the shorter the range.

  18. Throughput & Latency • Throughput and latency are not related. They rarely go together • Decide what is important: • Latency • Reliability (QoS) • Raw Data Rate • Quoted data rates rarely reflect reality • They are symbol rates • They include packet overheads • They are relevant at short range in a lab environment • The wireless industry loves “go-faster stripes”. Real applications rarely need high data rates. Don’t be sucked into the hype. • Most M2M applications can only handle rates of around 115kbps at their interfaces. However, the data may travel over the air at a much higher rate, reducing the power consumption.

  19. Universal WirelessThe Wireless Development Platform Tim Wheatley - VP Engineering

  20. What is Universal Wireless? A complete wireless application development platform Enables rapid application prototyping and demonstration Allows HOSTLESS application development Not just a wireless module! Sophisticated web server integration allows machines to have a web presence Compatibility across Ezurio modules

  21. Universal WirelessIn Action

  22. Basic Use of the Module • The WISM Development Platform • The WISM file system • Immediate mode commands • at i 3 • at+dir • at+del • at+run • Using the !function_name() syntax • !_flashdel() • Using the UWTerminal Application • Downloading new scripts • Downloading web pages

  23. OBD - Basic Operation

  24. OBD - Cable Replacement

  25. Wireless OBD Interface Cable replacement……. Application complete! WLAN Module programmed to automatically attach to AP and PC and transfer data Uses a commercial OBD scan tool (Gendan) with unmodified Gendan EngineCheck firmware No additional microcontroller is needed to manage the application – UW does it all. Based on examples, the complete application takes only a few hours to complete!

  26. OBD – Intelligent Cable Replacement

  27. Wireless OBD Interface Intelligent cable replacement…… Application complete! WLAN Module retrieves the data from the machine, processes it and only reports key information WISM module actively participates in the data gathering and display No additional microcontroller is needed to manage the application – UW does it all. Based on examples, the complete application takes only a few hours to complete!

  28. SMTP Client Interface Implementation of a protocol in UWScript Also shows the use of a custom command interface WLAN module is programmed with comms related applications to remove the load from the host processor Demonstrates the ability of the module to act as a ‘communication co-processor’ Command interface is tailored to the application – high and low level functions Module could be made to emulate legacy solutions

  29. Powersaving • Powersave Mode 0 • No power saving enabled • Powersave Mode 1 • IEEE powersaving enabled • Powersave Mode 5 • WLAN disabled, CPU active • Powersave Mode 6 • WLAN disabled, CPU sleeping

  30. Firmware Upload • Uploading firmware is managed by the UWLoad.exe executable. • UWLoad.exe executable and sectormap.ini file must exist in same directory • Set up correct port number for UWLoad (using command line parameter com=n) • Reset the module when prompted. • Select the firmware file to load. • Firmware update will happen automatically.

  31. Firmware Upload Tutorial • Unzip the firmware and UWLoad tool from the UW_rash_2 0 1 1_Full_Delivery.zip and UWLoad.zip file respectively. • Setup a shortcut to the UWLoad.exe file. Right click on the shortcut and set the command line parameter com=n from the ‘properties’. • Run UWLoad.exe • Select ‘Load’ • Reset the module • Select the UW_rash_2.0.1.1.s file • Firmware upgrade should complete automatically.

  32. The Internet Protocols

  33. The Internet Protocol Family

  34. Peer to Peer Protocols

  35. Routers

  36. Internet Addressing • Each node on the network has an IP address • E.g 192.168.1.1, 213.246.148.49 • Statically or dynamically allocated (DHCP) • IP packets contain source address and destination address. • Destination addresses ensure that packets reach the final destination • Source address ensure that responses reach the originator • IP addresses can change many times as a packet passes across the network • This is transparent to the user!

  37. Physical Addressing • Each physical device on the network has a hardware address (MAC address) • The MAC address is used either by the hardware interface or by the driver to identify ‘interesting’ packets • Interesting packets are passed up the stack for further processing. • Packets are addressed by both physical and IP addresses. • Mapping between physical / IP addresses is handled by ARP protocol.

  38. Ports • Many applications can be implemented that use the underlying TCP/IP stack structure. • Applications are identified by port numbers • There are many pre-allocated port numbers for well known applications • 80 – HTTP • 21 – FTP • 25 – SMTP • ‘User’ port numbers can lie in the range 1024 – 65535

  39. Data Encapsulation

  40. Internet Protocol (IP) • Deals with delivery of a payload to the destination • Supplies source and destination addresses • Specifies type of service – which defines how the packet is routed • Packet delivery is not guaranteed • Works packet by packet – no concept of a connection • Packet ordering is not guaranteed • Higher layer protocols must deal with this…..

  41. Transmission Control Protocol (TCP) • Provides • Reliable stream delivery of ordered data • Virtual circuit connections • Full duplex connections • A connection is defined by a pair of end points • An endpoint is a (host, port) pair • eg 145.23.4.3., 1876 154.23.5.6, 345 • Connection establishment is by three way handshake • Connection terminates by a modified three way handshake • Asymmetric release • Symmetric release

  42. Address Resolution Protocol • IP address must map onto physical address • Host must somehow discover the physical address of a target host on the same network given the target’s IP address • ARP • Host broadcast ARP request containing target IP address • Target responds with ARP reply containing physical address • Machines cache IP to physical address bindings • Broadcast is expensive • A cache prevents frequent broadcast • Entries must be removed after a fixed time to enable replacement of hardware

  43. Dynamic Host Configuration Protocol (DHCP) • Main application of DHCP is distribution of IP addresses • Used by the module to request and obtain a dynamic IP address from the router (access point). • Also used to provide gateway mask, gateway IP address and primary and secondary DNS IP addresses. • Typically runs immediately after physical connection is established with the router (i.e after attaching to the AP).

  44. An Overview of Sockets

  45. Client Server Model • TCP/IP networking operates on a client server model. • One end operates as a server • Offers a service to clients • Example is a web server • One or more clients makes contact with the server and uses the service.

  46. Sockets (1) • A socket is used to establish a data connection between two devices. • Uses the client / server model • Analagous to making a telephone call to a business • Client calls the switchboard number for the business • Switchboard operator answers the call • Call is put through to an extension for the call to be handled • Switchboard returns to listening out for more clients to call in. • The ‘telephone number’ of the server is the IP address and the port number • 192.168.1.1:1056 • Typically the server will hand the connection to another port for the remainder of the call

  47. Sockets (2)

  48. Sockets (3)

  49. Sockets (4) • Stages in creating socket: • Server: • Create socket • Bind socket to the listening port number • Listen on the socket • Accept incoming connections from clients • Client: • Create socket • Connect socket to server

  50. Universal WirelessBasics and Concepts

More Related