This document discusses implementing a low-power wireless microserver with a small form factor that can be connected to mobile devices using Bluetooth technology. It explores two implementation options - embedding the server directly into a device, or using a pluggable server that can be retrofitted to different devices via a standard connector. It also describes distributing the user interface for the server by either preloading it onto the server, or downloading it from a network when the server is plugged into a device.
IBM MessageSight for mobile and the internet of thingsJohn Samuel
This document introduces IBM MessageSight, a product for connecting mobile devices and internet of things devices. It is designed to handle high volumes of messages from millions of connected devices using less bandwidth than HTTP. Key features include massive scale to support over 1 million devices, optimized connectivity for wireless clients using MQTT protocol, security as a hardened appliance, and integration with other IBM products. Use cases discussed include connected vehicles, homes and cities.
Web Application Protocol (WAP) is a specification for communication protocols to standardize how wireless devices access the internet for email, web, newsgroups and messaging. A web page consists of objects like HTML files and images addressed by URLs. Hypertext Transfer Protocol (HTTP) is the most widely used protocol, seen as "http://" in browser addresses. HTTP uses GET, HEAD, POST, PUT and DELETE requests. HTTPS combines HTTP with SSL/TLS encryption to securely transmit personal information on ecommerce sites. WAP is suitable for mobile learning by optimizing for handheld devices and handling design challenges.
WLAN allows devices to connect to the internet and each other wirelessly using radio waves or infrared signals. It provides flexibility, portability, mobility, and ease of installation compared to wired networks. Common applications of WLAN include use in medical, education, temporary situations, airlines, and emergency centers. WLANs operate in either ad hoc mode for direct peer-to-peer connections or infrastructure mode which uses an access point to connect to other networks. Technologies used include infrared, radio waves that comply with FCC regulations, and microwaves. WAP allows access to internet content and services on mobile devices by compressing web pages for smaller screens.
WAP (Wireless Application Protocol) is a protocol that allows users to access information and services on the internet using handheld wireless devices like mobile phones. It uses a layered architecture and protocols like WSP, WTP, and WTLS to enable wireless internet access via technologies like GSM, CDMA, and UMTS networks. WAP was designed to work with microbrowsers and uses the markup language WML instead of HTML to optimize content for small screens and low bandwidth connections.
The document discusses wireless communication technologies and protocols, including Wi-Fi, Bluetooth, and Wireless Application Protocol (WAP). It defines key terms like wireless clients and describes common wireless devices like smartphones, laptops, and smartwatches. The document also summarizes the WAP architecture and its layered design. It explains that WAP allows limited internet access from devices with low bandwidth and processing power, like early mobile phones, using protocols like WML and WSP.
The document describes a proposed Wi-Fi calling system called Wi-Call that allows voice and data communication between Wi-Fi enabled devices on a local area network (LAN) without using an internet or cellular connection. It works by converting voice signals to IP packets and transmitting them over the LAN. The system uses a web application to register users and map their IP addresses so calls can be routed properly within the dynamic IP environment of a LAN. It aims to reduce communication costs for organizations by providing free calling and data transmission within the LAN.
Mobile IP allows mobile devices to stay connected to the internet as they move between networks. It uses a home agent and foreign agent to associate a device's permanent home IP address with its changing care-of address on visited networks. When a mobile node moves, it registers its new care-of address with its home agent so that packets can be forwarded to its current location. This process enables seamless internet connectivity regardless of location.
IBM MessageSight for mobile and the internet of thingsJohn Samuel
This document introduces IBM MessageSight, a product for connecting mobile devices and internet of things devices. It is designed to handle high volumes of messages from millions of connected devices using less bandwidth than HTTP. Key features include massive scale to support over 1 million devices, optimized connectivity for wireless clients using MQTT protocol, security as a hardened appliance, and integration with other IBM products. Use cases discussed include connected vehicles, homes and cities.
Web Application Protocol (WAP) is a specification for communication protocols to standardize how wireless devices access the internet for email, web, newsgroups and messaging. A web page consists of objects like HTML files and images addressed by URLs. Hypertext Transfer Protocol (HTTP) is the most widely used protocol, seen as "http://" in browser addresses. HTTP uses GET, HEAD, POST, PUT and DELETE requests. HTTPS combines HTTP with SSL/TLS encryption to securely transmit personal information on ecommerce sites. WAP is suitable for mobile learning by optimizing for handheld devices and handling design challenges.
WLAN allows devices to connect to the internet and each other wirelessly using radio waves or infrared signals. It provides flexibility, portability, mobility, and ease of installation compared to wired networks. Common applications of WLAN include use in medical, education, temporary situations, airlines, and emergency centers. WLANs operate in either ad hoc mode for direct peer-to-peer connections or infrastructure mode which uses an access point to connect to other networks. Technologies used include infrared, radio waves that comply with FCC regulations, and microwaves. WAP allows access to internet content and services on mobile devices by compressing web pages for smaller screens.
WAP (Wireless Application Protocol) is a protocol that allows users to access information and services on the internet using handheld wireless devices like mobile phones. It uses a layered architecture and protocols like WSP, WTP, and WTLS to enable wireless internet access via technologies like GSM, CDMA, and UMTS networks. WAP was designed to work with microbrowsers and uses the markup language WML instead of HTML to optimize content for small screens and low bandwidth connections.
The document discusses wireless communication technologies and protocols, including Wi-Fi, Bluetooth, and Wireless Application Protocol (WAP). It defines key terms like wireless clients and describes common wireless devices like smartphones, laptops, and smartwatches. The document also summarizes the WAP architecture and its layered design. It explains that WAP allows limited internet access from devices with low bandwidth and processing power, like early mobile phones, using protocols like WML and WSP.
The document describes a proposed Wi-Fi calling system called Wi-Call that allows voice and data communication between Wi-Fi enabled devices on a local area network (LAN) without using an internet or cellular connection. It works by converting voice signals to IP packets and transmitting them over the LAN. The system uses a web application to register users and map their IP addresses so calls can be routed properly within the dynamic IP environment of a LAN. It aims to reduce communication costs for organizations by providing free calling and data transmission within the LAN.
Mobile IP allows mobile devices to stay connected to the internet as they move between networks. It uses a home agent and foreign agent to associate a device's permanent home IP address with its changing care-of address on visited networks. When a mobile node moves, it registers its new care-of address with its home agent so that packets can be forwarded to its current location. This process enables seamless internet connectivity regardless of location.
WAP (Wireless Application Protocol) allows users to access the internet from mobile devices like phones. It uses a layered protocol stack including WDP, WTP, WSP, and WTLS to transport data securely and reliably over wireless networks. The WAP architecture includes WAP clients, gateways that encode/decode content, and origin servers hosting applications. WAP browsers interpret WML, a markup language optimized for small screens to provide web-like experiences on mobile. While enabling mobility, WAP also has limitations like slow speeds, small screens, and higher power consumption. [/SUMMARY]
Realtime mobile&iot solutions using mqtt and message sightfloridawusergroup
This document discusses realtime mobile and IoT solutions using MQTT and IBM MessageSight. It describes MQTT as a publish/subscribe messaging protocol designed for mobile and telemetry devices that allows for decoupled applications and reliable message delivery. IBM MessageSight is presented as an appliance that can handle millions of connections and events with high performance, reliability, and security for mobile, IoT, and M2M applications. Use cases discussed include connected vehicles, cities, devices, and more.
Convergence of Wired and Wireless networks.
From the technology and business perspective, the differentiation between Mobile Networks and Fixed phone network is slowly diminishing. Voice, Mobile Data / Internet characteristics in Mobile systems are similar to these in Fixed Networks. Differences are the access type, bandwidth limitations and device characteristics. Therefore, it is necessary to focus on the convergence of Fixed and Mobile networking so to provide Universal mode of Telecommunication for all.
1. Limitations of current Mobile Telecom system. In a detail analysis, it can be seen that with higher data rates, the differentiations of Fixed Network and Mobile Network narrow down to ‘the type of end link’ and the ‘terminal device’. This is because, networking of enormously large number of small coverage’ area cell sites that are required for High Data rate Service delivery with Wireless connectivity becomes impractical. In practice, the topology of the high data service mobile network becomes same as that of fixed network made up of Optical Cable back bone and WiFi / WiMax based wireless end link. Higher Mobility of the Mobile terminal also have impact on the data rates that can be realized without compromising quality of service.
2. Product utility in Mobile situation: Higher data rates of 2 Mbps and above, is required only for quick down loading of high volume contents such as a lengthy digital movie etc. The utility of such services will be rare in a mobile situation and therefore, cannot become a major revenue earning product. Such high volume data files can be easily carried in plug and play storage devices.
It can be seen that an assured data rate of 384 to 512 Kbps, is more than adequate for good quality user intensive 'real time' video plus voice products such as, TV news, digital movie display, Multi-media transactions over internet etc. With 384 to 512 Kbps data rate, the data service can be delivered to the mobile device in a vehicle moving at its normal speed without compromising quality of service.
3. The business viability of high data service: Higher data rates of 2Mbps and above inMobile network any time, anywhere is near to impractical in terms of business viability. It could be realized only in limited hot spots and the Mobile device in more or less stationery situation identical to Wired phone.
4. Limitation in current Wired Line devices. Though very high data rate products could be made available in a fixed network system, the fixed network provides only limited mobility within a short coverage area. High data rate need of the user can be realized if the user can plug in his device to a fixed network socket or get serviced through a PON connectivity as the end link at the premises.
Please see link http://wp.me/p1ZsI2-26
The document provides specifications for India's Public Open Wi-Fi framework, including a high-level architecture with various players (PDOs, hardware/software providers, user app providers, and a central provider registry). It describes one-time and usage flows, and provides technical specifications for the provider registry, user signup/authentication, access point discovery, and connecting to access points. The goal is to establish an open architecture for anyone to easily set up paid public Wi-Fi access points, and for users to easily discover, authenticate, and connect to access points.
The document discusses the Wireless Application Protocol (WAP), which was developed to allow mobile devices like phones to access the internet. WAP defines a set of communication protocols to standardize how internet content can be adapted for narrowband mobile bearers. It enables applications and services to be accessed from any wireless terminal, including cell phones, pagers, two-way radios and smart phones. WAP uses Wireless Markup Language (WML) instead of HTML to optimize content for mobile screens.
Mobile IP allows devices to change networks while maintaining the same IP address, enabling continuous internet connectivity regardless of location. It works by assigning devices a permanent home IP address and registering a care-of address with a foreign agent when not in the home network, allowing the foreign agent to forward packets to the device's current location. Mobile IP supports security through authentication and aims to optimize routing efficiency.
This document provides an overview of the requirements for developing a mobile application called "Free Park" to help disabled users locate parking spaces. The application will allow users to view available parking locations, prices, and reserve spaces for a chosen duration. It will connect to a SQLite database to store user data and parking information. The application will be created in Java using Android SDK and will integrate with Google Maps and the Liverpool government website for additional parking details. Security measures like WPA2 encryption will also be implemented once the basic application functionality is established. The goal is to create a user-friendly mobile solution to help disabled individuals more easily find and reserve accessible parking spots.
This document discusses speed adaptive mobile IP over wireless LAN. It first analyzes the relationship between performance and moving speed for mobile IP over wireless LAN, showing that current mobile IP is not suitable for rapid movement. It then proposes a speed adaptive mobile IP protocol that extends registration messages with speed information to allow the network behavior to automatically adapt based on node speed, improving performance for rapid movement without high resource costs. The protocol is emulated and shown to greatly improve mobile IP performance for rapid movement over wireless LAN.
Introduction to MessageSight - gateway to the internet of things and mobile m...Bernard Kufluk
The document introduces IBM MessageSight, an appliance that provides secure connectivity between Internet of Things (IoT) devices, mobile applications, and enterprise systems. MessageSight uses the MQTT protocol which is optimized for low bandwidth and unreliable networks. It can handle large volumes of messages and connections from IoT devices and mobile apps. The document discusses use cases and how MessageSight can integrate with other IBM products and be deployed quickly and easily.
An introduction to IBM MessagSight, IBM's gateway to the Internet of Things and Mobile Messaging. As the Internet of Things and M2M become more pervasive are you ready to engage and get the benefits? Do you want to get the benefits of rapid, reliable messaging in the mobile world? This session will cover an introduction to MessageSight, latest updates and an introduction to MQTT.
The document outlines standards and best practices for mobile web development, covering topics like markup languages (XHTML), presentation (CSS), scripting, and standardization bodies. It provides an introduction to mobile web standards and discusses XHTML, CSS, JavaScript, MIME types, and groups that govern standards.
Management information system chapter 7 telecommuniications the internet and ...Leng Kimlieng
1. The document discusses telecommunications, internet, and wireless technology. It covers the principal components of telecommunications networks, key networking technologies, types of networks, and principal wireless technologies and standards.
2. Specific topics covered include local area networks, wide area networks, internet protocols, internet architecture, internet services like email and web browsing, wireless standards like Bluetooth and Wi-Fi, and mobile technologies like 3G and 4G networks.
3. The document provides information on key digital networking technologies like client/server computing and packet switching as well as transmission media, internet protocols, wireless standards, and mobile cellular systems.
This document provides a summary of integrating IP telephony into the public switched telephone network (PSTN) environment. It discusses the evolution of PSTN from analog to digital networks and the emergence of time division switching. It then outlines the architecture of a soft switch solution for integration, including edge, core, control, and application layers. Finally, it discusses existing practices for integration, such as replacing tandem exchanges, and considers the specific context of integrating IP networks in Bangladesh.
This document discusses softswitches, which are central devices that connect phone calls entirely through software running on computer systems, replacing physical switchboards. It provides background on softswitches and their advantages over hardware switches, noting they can reduce costs, improve services, and facilitate migration to IP networks. Key elements of a softswitch architecture are described, including media gateways and call agents. Benefits of softswitch architecture for wireless networks are outlined, such as enabling distributed switching to reduce costs compared to centralized hardware switches.
M2M Stategy of the Open Mobile Alliance - Fraunhofer FUSECO Forum 2011Musa Unmehopa
OMA's strategy focuses on extending its Device Management (DM) technology to support M2M devices and heterogeneous networks through a gateway. It is developing a Gateway Management Object and Lightweight M2M protocol for constrained devices. OMA is also defining APIs to standardize access to network and device resources for M2M applications. This will help realize significant growth in the number of connected M2M devices.
Www ccnav5 net_ccna_1_chapter_1_v5_0_exam_answers_2014Đồng Quốc Vương
This document contains 21 multiple choice questions and answers from the CCNA 1 Chapter 1 v5.0 exam. The questions cover topics like internet connection types, network devices, security goals, and network congestion. Answers are provided for each question about concepts addressed in the CCNA curriculum.
This document contains questions and answers about networking concepts. It covers topics like internet connectivity types, network functions, security goals, and characteristics of networks. For example, it states that cable and DSL provide always-on high-bandwidth internet connections, and that routers determine the path that messages take through internetworks. It also addresses concepts like BYOD, cloud computing, and wireless LAN redesign due to increased use of personal devices on networks.
mumble: Framework for Seamless Message Transfer on SmartphonesAnand Bhojan
This work explores the possibility of transferring data between mobile devices that are nearby each other without the need of pairing, authentication, superuser access and Internet connectivity. Such technology can be used for emergency broadcast, traffic congestion avoidance, IoT, smart city, social and dating systems and games. Except Bluetooth Low Energy technology, there is no other protocol or technology available that allows pairing-free data transfer without Internet connectivity. Bluetooth Low Energy is capable of doing so but at a relatively short range. Using Wi-Fi Direct's Service Broadcast and Discovery, a simple yet novel method is developed which allows for seamless long range (Wi-Fi range) data transfer without Internet connectivity.
The design details of FATS-mumble can be found in the paper (http://www.comp.nus.edu.sg/~bhojan/papers/mumble15.pdf) published in ACM Mobicom 2015 SmartObjects. Please use it for all the references of this mumble project.
The project is open sourced (Github Link): https://github.com/FatsGW/FATS-Mumble.
Demo: http://youtu.be/ACmNYLd2NlI
The document discusses various uses of the internet including communication, information sharing, commerce, and entertainment. It describes how individual networks connect to form the internet, and how clients and servers allow for requesting and transmitting data. Common applications like email, file transfer, and voice/video chat are mentioned as well as how businesses utilize online marketing, e-commerce, and electronic newspapers.
The document discusses a wireless microserver based on Bluetooth technology that was developed with NASA sponsorship. It captures and distributes geographical image data from harsh environments using a wireless sensor network. The microserver was used to photograph an ash plume from an erupting volcano in 2006. Microservers have advantages of flexible design, power management capabilities, and no fundamental limits on what they can be used for or where.
This document discusses implementing a low-power wireless microserver with Bluetooth technology to allow mobile devices to remotely control electronic devices. Key points:
1) The microserver would be small, low-cost and pluggable, allowing it to be added to existing devices via a standard connector. This is preferable to embedding full servers directly into devices.
2) The microserver would run a simplified embedded WAP server over Bluetooth, allowing control of devices via a mobile phone browser interface.
3) User interfaces could either be pre-programmed or downloaded dynamically to plugged-in microservers from the Internet or device. This allows remote updating of interface content.
This document discusses using a HP MicroServer with an InfiniHost III SDR InfiniBand adapter connected to an 8-port QDR InfiniBand switch to build a network storage system with OpenIndiana and ZFS. Disks are configured in redundant RAID-Z arrays providing over 100MB/s transfers over InfiniBand. Virtual machines running on ESXi can access the storage using IP-over-IB while OpenIndiana acts as an iSCSI and NFS target using IP-over-IB and SRP. Performance of sequential transfers approaches 1GB/s using InfiniBand and ZFS.
WAP (Wireless Application Protocol) allows users to access the internet from mobile devices like phones. It uses a layered protocol stack including WDP, WTP, WSP, and WTLS to transport data securely and reliably over wireless networks. The WAP architecture includes WAP clients, gateways that encode/decode content, and origin servers hosting applications. WAP browsers interpret WML, a markup language optimized for small screens to provide web-like experiences on mobile. While enabling mobility, WAP also has limitations like slow speeds, small screens, and higher power consumption. [/SUMMARY]
Realtime mobile&iot solutions using mqtt and message sightfloridawusergroup
This document discusses realtime mobile and IoT solutions using MQTT and IBM MessageSight. It describes MQTT as a publish/subscribe messaging protocol designed for mobile and telemetry devices that allows for decoupled applications and reliable message delivery. IBM MessageSight is presented as an appliance that can handle millions of connections and events with high performance, reliability, and security for mobile, IoT, and M2M applications. Use cases discussed include connected vehicles, cities, devices, and more.
Convergence of Wired and Wireless networks.
From the technology and business perspective, the differentiation between Mobile Networks and Fixed phone network is slowly diminishing. Voice, Mobile Data / Internet characteristics in Mobile systems are similar to these in Fixed Networks. Differences are the access type, bandwidth limitations and device characteristics. Therefore, it is necessary to focus on the convergence of Fixed and Mobile networking so to provide Universal mode of Telecommunication for all.
1. Limitations of current Mobile Telecom system. In a detail analysis, it can be seen that with higher data rates, the differentiations of Fixed Network and Mobile Network narrow down to ‘the type of end link’ and the ‘terminal device’. This is because, networking of enormously large number of small coverage’ area cell sites that are required for High Data rate Service delivery with Wireless connectivity becomes impractical. In practice, the topology of the high data service mobile network becomes same as that of fixed network made up of Optical Cable back bone and WiFi / WiMax based wireless end link. Higher Mobility of the Mobile terminal also have impact on the data rates that can be realized without compromising quality of service.
2. Product utility in Mobile situation: Higher data rates of 2 Mbps and above, is required only for quick down loading of high volume contents such as a lengthy digital movie etc. The utility of such services will be rare in a mobile situation and therefore, cannot become a major revenue earning product. Such high volume data files can be easily carried in plug and play storage devices.
It can be seen that an assured data rate of 384 to 512 Kbps, is more than adequate for good quality user intensive 'real time' video plus voice products such as, TV news, digital movie display, Multi-media transactions over internet etc. With 384 to 512 Kbps data rate, the data service can be delivered to the mobile device in a vehicle moving at its normal speed without compromising quality of service.
3. The business viability of high data service: Higher data rates of 2Mbps and above inMobile network any time, anywhere is near to impractical in terms of business viability. It could be realized only in limited hot spots and the Mobile device in more or less stationery situation identical to Wired phone.
4. Limitation in current Wired Line devices. Though very high data rate products could be made available in a fixed network system, the fixed network provides only limited mobility within a short coverage area. High data rate need of the user can be realized if the user can plug in his device to a fixed network socket or get serviced through a PON connectivity as the end link at the premises.
Please see link http://wp.me/p1ZsI2-26
The document provides specifications for India's Public Open Wi-Fi framework, including a high-level architecture with various players (PDOs, hardware/software providers, user app providers, and a central provider registry). It describes one-time and usage flows, and provides technical specifications for the provider registry, user signup/authentication, access point discovery, and connecting to access points. The goal is to establish an open architecture for anyone to easily set up paid public Wi-Fi access points, and for users to easily discover, authenticate, and connect to access points.
The document discusses the Wireless Application Protocol (WAP), which was developed to allow mobile devices like phones to access the internet. WAP defines a set of communication protocols to standardize how internet content can be adapted for narrowband mobile bearers. It enables applications and services to be accessed from any wireless terminal, including cell phones, pagers, two-way radios and smart phones. WAP uses Wireless Markup Language (WML) instead of HTML to optimize content for mobile screens.
Mobile IP allows devices to change networks while maintaining the same IP address, enabling continuous internet connectivity regardless of location. It works by assigning devices a permanent home IP address and registering a care-of address with a foreign agent when not in the home network, allowing the foreign agent to forward packets to the device's current location. Mobile IP supports security through authentication and aims to optimize routing efficiency.
This document provides an overview of the requirements for developing a mobile application called "Free Park" to help disabled users locate parking spaces. The application will allow users to view available parking locations, prices, and reserve spaces for a chosen duration. It will connect to a SQLite database to store user data and parking information. The application will be created in Java using Android SDK and will integrate with Google Maps and the Liverpool government website for additional parking details. Security measures like WPA2 encryption will also be implemented once the basic application functionality is established. The goal is to create a user-friendly mobile solution to help disabled individuals more easily find and reserve accessible parking spots.
This document discusses speed adaptive mobile IP over wireless LAN. It first analyzes the relationship between performance and moving speed for mobile IP over wireless LAN, showing that current mobile IP is not suitable for rapid movement. It then proposes a speed adaptive mobile IP protocol that extends registration messages with speed information to allow the network behavior to automatically adapt based on node speed, improving performance for rapid movement without high resource costs. The protocol is emulated and shown to greatly improve mobile IP performance for rapid movement over wireless LAN.
Introduction to MessageSight - gateway to the internet of things and mobile m...Bernard Kufluk
The document introduces IBM MessageSight, an appliance that provides secure connectivity between Internet of Things (IoT) devices, mobile applications, and enterprise systems. MessageSight uses the MQTT protocol which is optimized for low bandwidth and unreliable networks. It can handle large volumes of messages and connections from IoT devices and mobile apps. The document discusses use cases and how MessageSight can integrate with other IBM products and be deployed quickly and easily.
An introduction to IBM MessagSight, IBM's gateway to the Internet of Things and Mobile Messaging. As the Internet of Things and M2M become more pervasive are you ready to engage and get the benefits? Do you want to get the benefits of rapid, reliable messaging in the mobile world? This session will cover an introduction to MessageSight, latest updates and an introduction to MQTT.
The document outlines standards and best practices for mobile web development, covering topics like markup languages (XHTML), presentation (CSS), scripting, and standardization bodies. It provides an introduction to mobile web standards and discusses XHTML, CSS, JavaScript, MIME types, and groups that govern standards.
Management information system chapter 7 telecommuniications the internet and ...Leng Kimlieng
1. The document discusses telecommunications, internet, and wireless technology. It covers the principal components of telecommunications networks, key networking technologies, types of networks, and principal wireless technologies and standards.
2. Specific topics covered include local area networks, wide area networks, internet protocols, internet architecture, internet services like email and web browsing, wireless standards like Bluetooth and Wi-Fi, and mobile technologies like 3G and 4G networks.
3. The document provides information on key digital networking technologies like client/server computing and packet switching as well as transmission media, internet protocols, wireless standards, and mobile cellular systems.
This document provides a summary of integrating IP telephony into the public switched telephone network (PSTN) environment. It discusses the evolution of PSTN from analog to digital networks and the emergence of time division switching. It then outlines the architecture of a soft switch solution for integration, including edge, core, control, and application layers. Finally, it discusses existing practices for integration, such as replacing tandem exchanges, and considers the specific context of integrating IP networks in Bangladesh.
This document discusses softswitches, which are central devices that connect phone calls entirely through software running on computer systems, replacing physical switchboards. It provides background on softswitches and their advantages over hardware switches, noting they can reduce costs, improve services, and facilitate migration to IP networks. Key elements of a softswitch architecture are described, including media gateways and call agents. Benefits of softswitch architecture for wireless networks are outlined, such as enabling distributed switching to reduce costs compared to centralized hardware switches.
M2M Stategy of the Open Mobile Alliance - Fraunhofer FUSECO Forum 2011Musa Unmehopa
OMA's strategy focuses on extending its Device Management (DM) technology to support M2M devices and heterogeneous networks through a gateway. It is developing a Gateway Management Object and Lightweight M2M protocol for constrained devices. OMA is also defining APIs to standardize access to network and device resources for M2M applications. This will help realize significant growth in the number of connected M2M devices.
Www ccnav5 net_ccna_1_chapter_1_v5_0_exam_answers_2014Đồng Quốc Vương
This document contains 21 multiple choice questions and answers from the CCNA 1 Chapter 1 v5.0 exam. The questions cover topics like internet connection types, network devices, security goals, and network congestion. Answers are provided for each question about concepts addressed in the CCNA curriculum.
This document contains questions and answers about networking concepts. It covers topics like internet connectivity types, network functions, security goals, and characteristics of networks. For example, it states that cable and DSL provide always-on high-bandwidth internet connections, and that routers determine the path that messages take through internetworks. It also addresses concepts like BYOD, cloud computing, and wireless LAN redesign due to increased use of personal devices on networks.
mumble: Framework for Seamless Message Transfer on SmartphonesAnand Bhojan
This work explores the possibility of transferring data between mobile devices that are nearby each other without the need of pairing, authentication, superuser access and Internet connectivity. Such technology can be used for emergency broadcast, traffic congestion avoidance, IoT, smart city, social and dating systems and games. Except Bluetooth Low Energy technology, there is no other protocol or technology available that allows pairing-free data transfer without Internet connectivity. Bluetooth Low Energy is capable of doing so but at a relatively short range. Using Wi-Fi Direct's Service Broadcast and Discovery, a simple yet novel method is developed which allows for seamless long range (Wi-Fi range) data transfer without Internet connectivity.
The design details of FATS-mumble can be found in the paper (http://www.comp.nus.edu.sg/~bhojan/papers/mumble15.pdf) published in ACM Mobicom 2015 SmartObjects. Please use it for all the references of this mumble project.
The project is open sourced (Github Link): https://github.com/FatsGW/FATS-Mumble.
Demo: http://youtu.be/ACmNYLd2NlI
The document discusses various uses of the internet including communication, information sharing, commerce, and entertainment. It describes how individual networks connect to form the internet, and how clients and servers allow for requesting and transmitting data. Common applications like email, file transfer, and voice/video chat are mentioned as well as how businesses utilize online marketing, e-commerce, and electronic newspapers.
The document discusses a wireless microserver based on Bluetooth technology that was developed with NASA sponsorship. It captures and distributes geographical image data from harsh environments using a wireless sensor network. The microserver was used to photograph an ash plume from an erupting volcano in 2006. Microservers have advantages of flexible design, power management capabilities, and no fundamental limits on what they can be used for or where.
This document discusses implementing a low-power wireless microserver with Bluetooth technology to allow mobile devices to remotely control electronic devices. Key points:
1) The microserver would be small, low-cost and pluggable, allowing it to be added to existing devices via a standard connector. This is preferable to embedding full servers directly into devices.
2) The microserver would run a simplified embedded WAP server over Bluetooth, allowing control of devices via a mobile phone browser interface.
3) User interfaces could either be pre-programmed or downloaded dynamically to plugged-in microservers from the Internet or device. This allows remote updating of interface content.
This document discusses using a HP MicroServer with an InfiniHost III SDR InfiniBand adapter connected to an 8-port QDR InfiniBand switch to build a network storage system with OpenIndiana and ZFS. Disks are configured in redundant RAID-Z arrays providing over 100MB/s transfers over InfiniBand. Virtual machines running on ESXi can access the storage using IP-over-IB while OpenIndiana acts as an iSCSI and NFS target using IP-over-IB and SRP. Performance of sequential transfers approaches 1GB/s using InfiniBand and ZFS.
MICRO servers in BIG Data
Most of the optimization in Big Data solutions today happens in software because the available hardware choices are too similar. This status quo changes with Microservers. New and differentiated hardware platforms are emerging and the number of server vendors is increasing. These varied designs offer an unprecedented opportunity to increase performance and lower costs at the same time. However, it requires a deeper understanding of the application, the hardware, and rigorous analysis tools. In this talk, I will talk through some of the trends in microservers, and present a simple framework for choosing the best hardware for your deployment. Disclaimer: The views are my own, and do not reflect the views of my current or past employers.
IBM and ASTRON 64-Bit Microserver Prototype Prepares for Big Bang's Big Data,...IBM Research
The document summarizes the IBM/ASTRON DOME 64-bit μServer Demonstrator project. It discusses the motivation to create a highly dense 64-bit microserver module for applications like radio astronomy and business analytics. The project aims to integrate an entire server node onto a single microchip, excluding memory and power components. It provides status updates on the development of the compute node boards using PowerPC and ARM processors, as well as the cooling and packaging design to integrate over 1,000 cores into a dense 2U chassis.
The iMouse system combines wireless sensor networks and mobile surveillance to provide advanced monitoring services at a lower cost than traditional systems. Static sensors form a wireless sensor network to detect events like changes in light, sound or temperature. Mobile sensors can then move to the event locations to take photos and transmit information to the server. The iMouse architecture uses static and mobile sensors on an experimental 6x6 grid to detect simulated events and test the system's real-time monitoring, event-driven response and scalability.
This document discusses barcode technology. It provides definitions of barcodes as automatic identification technologies that encode information in dark bars and white spaces. Barcodes are used to accurately track and identify items. Common uses of barcodes include tracking inventory in warehouses and retail stores. There are two main types of barcodes: linear barcodes and 2D barcodes. Barcode scanners are used to read barcodes and input the encoded data into computer systems. Benefits of barcodes include increased accuracy, automation, and productivity. Potential disadvantages include system failures causing delays and issues reading damaged or poor quality barcodes.
Heliodisplay is a mid-air video display technology developed by IO2 Technologies that projects images into clear open air without the need for a screen. It works by using a heat pump to cool air below its dew point, forming a cloud of micro-droplets that act as an invisible screen for projected images. Models range from 30-inch desktop displays to 100-inch life-size projections. While expensive now, proponents argue heliodisplay has applications in advertising, collaboration, simulation, consumer electronics, and more. It provides a unique hologram-like projection experience without requiring special glasses or backgrounds.
Peer To Peer Content Sharing On Wi-Fi Network For Smart PhonesIOSR Journals
This document summarizes a research paper on peer-to-peer content sharing on Wi-Fi networks for smart phones. It discusses using a peer-to-peer model to allow smart phones to share content like videos and photos over Wi-Fi networks without using cellular data or requiring a central server. The proposed system would allow phones to discover each other on the local network, search for files, and download content directly from other peers. This approach aims to reduce costs and bandwidth usage compared to uploading content through cellular networks or wired connections.
This document discusses the history and development of accessing the internet from mobile devices. It begins with an overview of how mobile phones and tablets have become integral to modern life. It then discusses early protocols like WAP, i-Mode, and smartphones that helped bring web browsing and other internet features to mobile. The document focuses on major mobile network operators and services available in Hong Kong, including 3 Hong Kong, CSL, and SmarTone-Vodafone. It provides details on services and devices offered by each like the iPhone and BlackBerry.
1. The document discusses the features of mobile and wireless devices, including less powerful CPUs, less memory, smaller displays, and different input devices compared to desktop computers. It also discusses the constrained communication environment of wireless networks, including less bandwidth, more latency, less connection stability, and less predictable availability compared to wired networks.
2. It describes the Wireless Application Environment (WAE) micro-browser environment, which includes the Wireless Markup Language (WML), WMLScript scripting language, Wireless Telephony Application (WTA) for telephony services, and content formats like images and phone book records.
3. The main elements of the WAE model are WAE user agents that interpret network content
Today, mobile phone and tablet seems like fashion accessories in our lives. Huge popularity of mobile phones and tablets, those drives mobile technology developed in very fast speed. Actually, it has made a great impact on business world. This kind easy and connective device also extended to our social life, lots of innovative mobile apps it makes life easier and efficient.
This document discusses the development of an embedded web server using an ARM processor to monitor and control systems remotely. It provides background on the growing use of embedded web servers and Internet of Things applications. The paper then describes implementing TCP/IP networking on an ARM processor to enable Ethernet connectivity and allow the device to function as a web server. This allows various devices to connect and be controlled over the Internet through a standardized web interface using only a browser. The embedded web server provides a uniform interface for accessing traditional devices remotely. The rest of the paper details the hardware, web server implementation, and software concepts to realize this embedded web server functionality.
International Journal of Modern Engineering Research (IJMER) is Peer reviewed, online Journal. It serves as an international archival forum of scholarly research related to engineering and science education.
International Journal of Modern Engineering Research (IJMER) covers all the fields of engineering and science: Electrical Engineering, Mechanical Engineering, Civil Engineering, Chemical Engineering, Computer Engineering, Agricultural Engineering, Aerospace Engineering, Thermodynamics, Structural Engineering, Control Engineering, Robotics, Mechatronics, Fluid Mechanics, Nanotechnology, Simulators, Web-based Learning, Remote Laboratories, Engineering Design Methods, Education Research, Students' Satisfaction and Motivation, Global Projects, and Assessment…. And many more.
Performance of Web Services on Smart Phone PlatformsIOSR Journals
This document discusses and compares the performance of Web Services on smart phone platforms using SOAP and REST. It begins with an introduction to Web Services and the problems with using SOAP on mobile devices due to its limitations in processing power, bandwidth usage, and flexibility. It then proposes using RESTful Web Services as an alternative as they avoid XML parsing and are based on the lightweight HTTP protocol. The document analyzes the performance of SOAP versus REST Web Services on a mobile device to determine which is more efficient for smart phones.
The document provides an overview of the Wireless Application Protocol (WAP), which enables access to the internet and advanced services from wireless devices independently of manufacturer, vendor, or technology. WAP defines a set of protocols that bridge the gap between mobile devices and the internet/intranets by allowing access to the same information on small wireless devices as desktop computers. It also defines an application environment for developing advanced services and applications for operators, manufacturers, and content developers.
Examination of Technologies(Bluetooth, WiFi &WiMax) related to data streaming...Vivek Garhewal
Examination of Technologies(Bluetooth, WiFi &WiMax) related to data streaming and applying it to perform for the same using RPC, RMI and various Mobile Agents and hence comparing different Mobile Agent systems
This document summarizes a research paper that proposes a middleware architecture to enable efficient access to web services from smartphones. The key issues addressed are loss of connection, limited bandwidth, limited smartphone resources, and security. The proposed solution involves transforming SOAP web services to RESTful services, optimizing responses through JSON to XML conversion, and using cryptographic algorithms for security. A mediation framework sits between web service clients and mobile hosts, allowing access to services over a peer-to-peer network. This improves scalability, reliability, and allows external clients to access mobile web services through the mediation framework.
A XMLRPC Approach to the Management of Cloud Infrastructureiosrjce
IOSR Journal of Computer Engineering (IOSR-JCE) is a double blind peer reviewed International Journal that provides rapid publication (within a month) of articles in all areas of computer engineering and its applications. The journal welcomes publications of high quality papers on theoretical developments and practical applications in computer technology. Original research papers, state-of-the-art reviews, and high quality technical notes are invited for publications.
WAP, HTTP and HTML5 Web Socket Architecture Analysis in Contemporary Mobile A...Editor IJCATR
This document analyzes WAP, HTTP, and HTML5 technologies for developing mobile applications. It discusses the features of WAP and HTTP, including how WAP addresses constraints of mobile devices and wireless networks through standards like WML. It also describes the HTTP client-server model. Finally, it analyzes HTML5 and how its new features improved the experience of building mobile apps that can connect to cloud services, compared to older technologies like WAP that required separate protocols and gateways for mobile devices.
WAP, HTTP and HTML5 Web Socket Architecture Analysis in Contemporary Mobile A...Editor IJCATR
Accessing current and accurate information anywhere and at anytime is becoming a growing interest nowadays. Wireless Application Protocol (WAP) is an application protocol that creates an opportunity to access information of any interest from WAP servers using mobile phones. WAP is an enabling technology based on the Internet client server architecture model, for developing client application for handheld devices or other wireless terminal which usually have less powerful CPU’s, less memory, very restricted power consumption, smaller and variant displays, phone keypads etc. This paper analyses the features of WAP in relation to the well established HyperText Transfer Protocol (HTTP) technology, the web socket API innovations introduced in HTML5, the recent improvements in mobile devices processing capacity by connecting to cloud services and how application can be developed on them using modern tools. The features that are more adapted to client development of micro-devices are used for the technology application test.
WAP, HTTP and HTML5 Web Socket Architecture Analysis in Contemporary Mobile A...Editor IJCATR
Accessing current and accurate information anywhere and at anytime is becoming a growing interest nowadays. Wireless
Application Protocol (WAP) is an application protocol that creates an opportunity to access information of any interest from WAP
servers using mobile phones. WAP is an enabling technology based on the Internet client server architecture model, for developing
client application for handheld devices or other wireless terminal which usually have less powerful CPU’s, less memory, very
restricted power consumption, smaller and variant displays, phone keypads etc. This paper analyses the features of WAP in relation to
the well established HyperText Transfer Protocol (HTTP) technology, the web socket API innovations introduced in HTML5, the
recent improvements in mobile devices processing capacity by connecting to cloud services and how application can be developed on
them using modern tools. The features that are more adapted to client development of micro-devices are used for the technology
application test.
This document discusses enabling open markets for services in the Web of Things by using open standards. It notes that most value will come from services, not just sensors, and that standards are key to breaking down product silos and allowing third parties to add value. The document outlines several technologies relevant to the Web of Things and Internet of Things, and proposes establishing a W3C Web of Things Interest Group to further standards efforts in areas like security, data models, and service composition.
Embedded Server Based Remote Industrial Automation Control
This document describes an embedded server project for remote industrial automation and control using a dsPIC33FJ64GP802 microcontroller. Key aspects include:
- The microcontroller runs a web server from an SD card to allow remote monitoring and control of up to 4 digital outputs via a web browser.
- An Ethernet interface connects the system to the internet to enable remote access and file transfer capabilities.
- Relays are controlled through a ULN2803 driver circuit connected to digital ports on the microcontroller.
- The system provides capabilities for remote monitoring, control, data logging and updating via a built-in web server without requiring a separate computer.
The document discusses Bluetooth technology. It provides an overview of Bluetooth, including its history and development. The key points are:
- Bluetooth was developed in 1994 as a wireless standard to replace wired cables and enable communication between nearby electronic devices.
- It uses short-range radio transmissions in the 2.4GHz spectrum for data transfer between devices within about 10 meters of each other.
- The Bluetooth standard defines protocols and procedures for device discovery, connection establishment, and data and voice transfer between paired devices.
- Common applications of Bluetooth include wireless headphones, medical devices, sports sensors, and connecting computers, phones and other consumer electronics without cables.
- The technology aims to provide secure, low
1) The document proposes an integrated wireless network architecture using proxy servers to support mobility management and reduce web traffic.
2) The architecture uses proxy servers and mobility-aware routers to maintain active data connections for mobile hosts as they handoff between different networks like cellular networks and wireless local area networks.
3) By deploying multiple proxy-router pairs and dynamically assigning mobile hosts to proxies, the approach provides efficient mobility support and is scalable.
This document summarizes an embedded web server designed for remote monitoring and control of wireless sensor networks. The web server allows authorized Internet users to monitor sensor data, download collected data, and change the operation mode of the wireless sensor network. It can generate email alerts, securely control sensor nodes, and log data to on-board flash memory. The web server is implemented on a RabbitCore module for its processing power and memory compared to sensor network nodes. It communicates with a sensor network node using a custom protocol to retrieve and send sensor data and commands. The web server operates in snapshot, monitoring, or log modes to provide sensor data to remote users.
Web Server for Remote Monitoring and Controliosrjce
IOSR Journal of Computer Engineering (IOSR-JCE) is a double blind peer reviewed International Journal that provides rapid publication (within a month) of articles in all areas of computer engineering and its applications. The journal welcomes publications of high quality papers on theoretical developments and practical applications in computer technology. Original research papers, state-of-the-art reviews, and high quality technical notes are invited for publications.
Similar to Wirelessmicroservers 111212193716-phpapp02(1) (20)
1. 1
1. INTRODUCTION:
With Bluetooth components getting smaller and cheaper, we might soon integrate
wireless Microservers into all kinds of electronic devices. The authors explore applying a
general-purpose, pluggable microserver, based on wireless application protocol and Bluetooth
technology, for remote control purposes.
Since the early days of the Web, server-side executable content has been an important
ingredient of server technology. It has turned simple hypertext retrieval into real applications.
Not surprisingly, the idea of remotely controlling devices through the Web1,2 has always
seemed near at hand. Because hypertext user interfaces can run on any Web browser, UI
development boils down to Web content creation. Furthermore, thanks to the HTTP standard’s
smart and scalable nature, we can fit embedded servers into simple 8-bit microcontrollers with
only a few Kbytes of RAM and ROM (see the “Embedding Servers into Devices” sidebar).3
Ever since we started integrating hypertext browsers into mobile phones, people have proposed
using mobile phones as remote controls. Now, with the provision of short-range wireless
connectivity— for example, through Bluetooth— mobile phones and other handhelds might
substantially change the way people interact with electronic devices. Here, we report on our
effort to create a low-power wireless microserver with a very small form factor and connect it to
mobile devices using standard consumer technology.
2. 2
2. CANDIDATE APPLICATIONS AND TECHNOLOGIES:
Consumer electronics have used wireless lowcostremote controls for decades. Adding
embedded servers to devices will create a new range of use cases beyond the limited capabilities
of infrared
Remotes:
• Browsers could then allow real interaction instead of just sending one-way commands such as
Infrared remotes.
• We could harmonize similar operations in terms of a Web UI, even if the built-in UIs of the
particular devices differ.4 A good example is setting a device’s clock, which is a common
operation in many consumer devices but always requires a unique—and often error-prone—
Implementation.
• We could distribute the UI among the device’s built-in UI and the handheld’s UI.4 For
example, we could export parental control functions—such as “edit play-time budget or game
type”—of game consoles to a mobile phone.
• A server with memory could personalize its UI and service by collecting and interpreting its
own usage patterns and those of adjacent servers.
• Devices that lack a UI, have a restricted UI, or are purposely hidden could export a UI to a
handheld.
• While the handheld is connected to the device, the device could connect to the Internet, in case
the handheld supports cellular data calls.
Eventually, we could turn each compatible handheld into a general-purpose remote
control. In a joint project, Nokia and the University of
3. 3
3. EMBEDDING SERVERS INTO DEVICES:
There are several ways to make things visible on the Web. In the simplest case, a server
hosts an item’s Web presence without a physical connection to the item. A handheld device reads
links between the item and its Web presence, connects to the respective URL, and retrieves
information about the item. A well-known example for this approach is the Cooltown Museum,1
where small infrared transceivers are located close to the pictures. When coming close, the
visitor’s PDAs receive Web links that point to the information pages for the particular picture.
Unfortunately, interacting with the item itself is impossible.
Interaction with a device would be possible if the device had a wireless control interface
to its internal logic. For example, the mobile terminal could download a device-specific user
interface application from the Web and use it to control the device through a device-dependent
protocol (see Figure A1). This approach might become feasible when we can download Java
applications into mobile terminals with access to Bluetooth APIs. Accessing the device
immediately and locally without an Internet connection would be possible only if the device
contained an embedded Web server (see Figure A2). An execution environment, such as server
side scripting, would be required to interact with the device’s logic. Short-range connectivity
seems to be an obstacle, but it empowers location-aware applications through the wireless link’s
limited reach. If a user wants to adjust a microserver-equipped TV’s volume, he or she does not
want to accidentally interact with somebody else’s TV. Therefore, short-range wireless radio
links, preferably using unlicensed bands, are well suited for networking things and people.
4. 4
Figure A. (1) UI application (such as Java Midlet) is downloaded and controls the device by a
control protocol. The internal and wireless link for the control protocol must be bridged. (2) The
device hosts the server comprising UI and execution environment
Dortmund created a low-power wireless microserver. (We use the term microserver to
refer to small and cost-efficient embedded Web server implementations that are either integrated
or plugged directly into the device.) Because mobile phones have a much higher population than
PDAs and will likely be the first truly ubiquitous computing devices, we chose to connect the
microserver to a mobile phone.
Although there are many technologies available for embedded middleware for distributed
computing and service discovery, such as Java, Jini, and UPnP,5 we decided not to use such
middleware components. For our project, these technologies have two important drawbacks: they
are not widely applied today and their implementation takes more processing resources then we
were willing to spend.
5. 5
For example, a small implementation of Jini that doesn’t even use Java-RMI would
require approximately 100 Kbytes of ROM and 50 Kbytes of RAM plus another 100 Kbytes of
RAM and 70 Kbytes of ROM for a lean Java virtual machine that includes basic packages. We
chose to use Bluetooth because it is the only short-range radio technology currently deployed in
mobile phones. Our implementation fit into the free memory of a commercial Bluetooth module,
which was about 40 Kbytes of ROM and 4 Kbytes of RAM. For the phone, we used existing
implementations of the browser and Bluetooth software without adding a new middleware
component. For remote method invocation, we based our solution (discussed later) on the
popular yet old-fashioned common gateway interface.
6. 6
4. WAP AND BLUETOOTH
The wireless application protocol is an industry-wide standard to connect mobile
Phones to the Web. It is designed especially for the mobile phone environment and its limited
battery power and memory, small display, and low transmission rates. Similar to the Japanese I-
mode, WAP provides Web access for mobile devices. Usually, browsers directly request HTML
content from a Web server using HTTP. A typical WAP infrastructure also needs HTTP (see
Figure 1), but the WAP protocol stack (see Figure 2) and the WML (Wireless Markup Language)
are tailored for the limited transmission capacity and resources of mobile devices. In addition,
unlike HTTP, WAP allows server push operation, so the server can send a WML page to a
browser without a request.
Figure 1. A wireless application protocol request and response model. A WAP request is directed
to a WAP gateway. The gateway decodes the request and transforms it into an HTTP request for
an ordinary Web server. The gateway then encodes the Wireless Markup Language page
response from the HTTP server and sends it as a WAP response back to the requesting WAP
device.
The WAP standard also specifies different levels of security that enable data encryption
and trusted communication—for example, for electronic payments or banking applications.
7. 7
Because future mobile phones will have larger screens and more processing power, the
next-generation WAP standard (WAP 2.0) will support the HTTP protocol and XHTML as a
markup language. Another reason for this support is the general trend toward all-Internet
protocol (IP) infrastructures. Currently, most Web browsers available in Europe are based on
WAP 1.1, which we selected for our implementation. However, you could apply our concept to
other mobile Web technologies, such as I-mode and WAP 2.0 without a substantial change in
complexity. Bluetooth is an industry standard for short-range, low-power, wireless
communications and networking. com/dev/specifications.asp). It uses radio transmission in the
license-free band of 2.4 GHz and can transmit voice and data with bit rates up to 720 kbits/sec
within approximately 10 meters. Bluetooth technology supports pointto- point and point-to-
multipoint connections. We can actively connect a Bluetooth device to seven devices
simultaneously. These devices build a so-called piconet, and every piconet contains up to seven
slaves and is controlled by a master. Several piconets can be linked together to form a scatternet.
Bluetooth was not envisaged to just replace cables with interconnecting mobile phones, PCs, and
peripheral devices such as headsets or printers. It aims to let arbitrary electronic devices form ad
hoc networks to jointly advertise and use each other’s services. It specifies its own service
discovery protocol, and every Bluetooth device usually implements its own service discovery
server and client.
GLOSSARY:
API: Application programmers’ interface BCU: Bus Coupling Unit
CDMA: Code Division Multiple Access DUN: Dial-up networking
EIB: European Installation Bus GPP: General purpose port
GPRS: General packet radio service IP: Internet protocol
LAP: LAN access profiles PAN: Personal area networking
PEI: Physical external interface UI: User interface
WDP: Wireless datagram protocol WAP: Wireless application protocol
WML: Wireless Markup Language WSP: Wireless session protocol
UART: Universal asynchronous receiver transmitter
8. 8
Figure 2. A WAP-over-Bluetooth protocol stack. Either the LAN access profile or the personal
area networking profile is used for Internet protocol adaptation
.
Figure 3. Consecutive screenshots of a mobile phone (a) while a user actively connects to a
vending machine and (b) when the server initiates connection (the connection request—“Connect
to MP3 player?”—comes without user interaction).
9. 9
The Bluetooth community has identified many application areas for Bluetooth. To assure
application-level interoperability between devices of different manufacturers, it is not sufficient
to specify the Bluetooth technology; we also need to agree on the technology’s use by higher-
level protocols and applications. Bluetooth profiles address these aspects.
4.1 WAP over Bluetooth:
The WAP protocol stack includes at the lowest level the wireless datagram protocol
(WDP). This layer implements the bearer adaptation and is defined for a variety of bearers, such
as GSM, Code Division Multiple Access, and the general packet radio service. The WDP doesn’t
cover Bluetooth but it does cover IP. In fact, WDP is identical to the well-known user datagram
protocol, in case IP is the bearer. So the challenge is to define an IP encapsulation protocol for
Bluetooth, which has been done in both the LAN access profile and the personal area networking
(PAN) profile (see Figure 2). The LAP makes Bluetooth behave like a standard serial port that
legacy software and devices can use. Consequently, the LAP uses the same mechanisms as a
terminal that accesses a network over a serial connection, namely point-topoint protocol and IP.
When using the PAN profile, Bluetooth behaves like a direct LAN connection: the Bluetooth
Network Encapsulation Protocol makes Bluetooth behave similar to Ethernet using the Bluetooth
device address as a hardware address. The PAN profile implements a lighter stack than the LAP.
The LAP is already approved in the Bluetooth 1.1 specification, but future implementations
might favor PAN, because it doesn’t require serial port emulation and point-to-point protocol.
4.2 WAP-over-Bluetooth user experience:
At first glance, Bluetooth is just another bearer for an existing service. After we
established the Bluetooth and WAP connection between the client and server, browser operation
is the same. However, there are some major differences in the WAP user experience between
cellular and Bluetooth connections. The first difference concerns location awareness. Bluetooth’s
limited range is not necessarily a disadvantage. A WAP-over- Bluetooth server knows that once
a user connects, he or she is close. Thus, it can offer location-aware services, and servers in
different places can reuse the same URLs.
10. 10
A second difference is that bandwidth is typically higher in Bluetooth than in cellular
systems, allowing richer content and better performance. Finally, there are two scenarios for
establishing a connection. In the first scenario, the user (WAP client) initiates the connection (see
Figure 3a). Upon user request, the WAP client searches for all Bluetooth devices in the user’s
proximity, then creates a WAP connection to the selected WAP service. The user might select a
function such as “search for Bluetooth devices.” Subsequently, the phone displays the Bluetooth
devices found. The user selects the desired WAP service and the phone displays this server’s
starting page. In the second scenario, the WAP gateway initiates the connection (see Figure 3b).
In this case, we assume the WAP client is in “discoverable” mode—that is, other Bluetooth
devices can find it. Once the user terminal comes into the gateway’s proximity, the WAP
gateway actively connects and displays its starting page on the user’s phone. It is either an
implementation choice or a user option whether to confirm the connection. In both examples, we
assume that neither the client nor server require authentication.
11. 11
5. IMPLEMENTATION OPTIONS FOR EMBEDDED WAP SERVERS:
If we leave out the WAP standard’s optional features and merge the server with
Figure 4. (a) An embedded WAP server versus (b) a pluggable server composed of a standard
connector and a standard control interface.
Figure 5. (a) A preprogrammed UI versus (b) a UI downloaded from the device.
the gateway, we can implement an embedded WAP-over-Bluetooth server in an 8-bit
microcontroller using a few Kbytes of RAM and Flash, provided that Bluetooth (including the
stack) is running on a dedicated component. Such optional features mainly include the WAP
security layer and the transaction layer (see Figure 2).
12. 12
Bluetooth implements flow control, retransmission of lost packets, authentication, and
encryption—thus replacing some of the sacrificed WAP features. Because the embedded server
does not require an internal separation between the WAP gateway and HTTP server, we can
directly store the content in the final WAPencoded message format, thus making WAP encoding
and decoding obsolete. Figure 4a depicts a simple model of such an embedded WAP server.
Typically, the WAPserver would either run on the baseband processor inside a Bluetooth module
or on a host processor connected to the Bluetooth module. The interfaces include general-
purpose ports, a universal asynchronous receiver transmitter (UART), and the like. Logically,
part of the WAP UI would be implemented as server-side scripts, triggering actions on user
interaction. The concept of embedded WAP servers is appealing at first glance. Any mobile
phone can act as a remote control for Bluetooth devices, which simply export their UIs in a
standard hypertext language. However, once these servers are embedded in low-cost devices,
they can unduly increase the devices’ costs. The server’s cost amounts to at least the cost of the
Bluetooth module, including external circuitry.
This can be 10 Euros and more, and will remain so at least until mid 2003. Customers
using the embedded server feature might be willing to pay more, but many people might end up
paying for a feature they never use. Moreover, Bluetooth technology and hypertext UI
development is clearly outside the core competence of many device manufacturers. Instead of
embedding the server into the device, we could provide a robust and cheap standard connector
where a pluggable server can be retrofitted (see Figure 4b).6 Such a connector would, for
example, provide several general-purpose ports and a UART option. Unlike embedded servers,
we could cost-efficiently manufacture general-purpose pluggable servers in large quantities.
Moreover, if we could separate the UI content from the corresponding devices and pluggable
servers, then independent marketplaces for UIs, servers, and devices could emerge. We could
move pluggable servers from one device to another—for example, if a device is not used for
some time, we could remove the server and plug it into some other device. This concept could,
for instance, be interesting for toy construction kits (such as Lego), which increasingly use
digital technology to construct sophisticated machines, vehicles, and robots.
13. 13
Because these kits consist entirely of pluggable components, a pluggable server would be
a natural extension. Eventually, we’ll have to decide whether to use an embedded or pluggable
server on a case-by-case basis. However, the question remains, “How do we get the UIinto the
server if we purchased the server independent of the device?”
Figure 6. Downloading a UI over a network.
Figure 7. Downloading a UI over a network (method 4).
5.1 Distributing the UI:
We must either preload general-purpose, pluggable servers when selecting a candidate UI
or externally load the UI when we first plug it in. In addition, for built-in servers, we’ll want to
be able to remotely update UI content. Here, we present four methods for provisioning UIs.
14. 14
We borrow our first method, which applies to pluggable servers, from generalpurpose IR
remote controls: Every server can be preprogrammed for many devices. Once the server is
plugged into a device, the device identifies itself to the server (either on startup or on the
device’s request) and the server selects the corresponding UI from several available UIs (see
Figure 5a). This method is not very flexible and adds undue cost to the server because it reserves
memory for UIs that a particular customer might never use. More desirable are servers that
download the desired UI from some source. This method assumes that the device simply stores
its UI in memory (for example, ROM) and uploads it to the server once it is plugged in (see
Figure 5b).6 Compared to the previous method, the total cost is lower, because only the required
UI must be stored in memory. However, it makes the device slightly more expensive, and the
server—but not the UI—is provided separately from the device. Moreover, we can’t easily
update the UI. Obviously, the most flexible method is to download the UI over a network (see
Figure 6). One simple implementation is to connect the server to a PC that is connected to the
Internet. The PC downloads the UI file from the manufacturer’s Web site and then stores it in the
pluggable or built-in server.
The fourth and most convenient method assumes that the server creates a Bluetooth dial-
up network connection to the UI server through a Bluetooth phone. Advantageously, this phone
would be the same phone that is used to access the server.
This method consists of several steps (see Figure 7):
1. The user plugs the server into the device and creates a Bluetooth connection to it.
2. The server retrieves the device ID and manufacturer URL from the device.
3. The server discovers that the UI is not in memory. It creates a dial-up network connection to
an ISP and downloads the UI from the manufacturer or som service provider. Alternatively, the
pluggable server directly dials up the manufacturer. Dial-up networkingover Bluetooth is
supported by the dial-up networking profile.
4. After the server has downloaded the UI, it presents the UI starting page to the user.
15. 15
Clearly, the UI does not have to be prestored in the server, and no other devices (such as
a PC) are needed for the download. This procedure could also be useful for regularly updating
the UI or downloading informative pages into the server (perhaps to advertise the device’s new
model). Only when the server is plugged into a device for the first time will the user have to wait
until the download completes. However, the server could cache the UIs of recently connected
devices to avoid delays when being moved from one device to another. Typical WML pages
occupy only a few hundred bytes of memory. A simple method invocation procedure through
CGI scripts We cannot realize remote control applications without server-side scripting, because
user interaction must trigger I/O operations on the server’s interface to the device’s logic. The
challenge is to achieve some basic means for invoking device functions without using distributed
computing middleware such as Jini or UPnP.
Figure 8. (a) Microserver prototype implementation and (b) the most important blocks of the
software architecture.
16. 16
would set Port1 to one, read a string from the serial port, store the string into the browser
variable my String, and load URL myURL.wmlc. (The actual syntax of the implemented script is
different. This example just explains the idea.) Besides reading and writing to the interfaces, the
implemented script can also increase and decrease counters and read and write string tokens (like
cookies) to the server’s flash memory. This approach is rather primitive, but it works fine for
many applications without requiring custom server scripts. We implemented the script in native
code as part of the server and did not require any script engine for execution. The ROM usage
was 3 Kbytes.
5.2 WAP-OVER-BLUETOOTH DEMONSTRATOR IMPLEMENTATIONS:
We developed two working implementations of the WAP-over-Bluetooth server—a PC
reference implementation using a Bluetooth PC card and an embedded implementation. Figure 8
shows the server hardware (the dimensions are 32 × 40 mm), with the server implemented inside
a Bluetooth module. The server’s total footprint is about 4 or 5 Kbytes of RAM and 35 or 40
Kbytes of ROM, depending on the profile used (LAP or PAN). This includes a connectionless
WAP stack without WAP security. The connector implements two UARTS, several I/O ports,
and a power supply. We can update the server’s content and software through a PC application
but not yet over server-initiated dial-up networking. We also modified a commercial Bluetooth
phone’s software to support WAP-over-Bluetooth. The first ideas many people had were about
remote-controlled PC applications, even though these are not embedded applications. We
implemented a WAP application to control PowerPoint presentations using a Bluetooth phone.
Another interesting demo application we did was to jointly edit an MP3 player’s play list
(running on a Bluetooth-equipped laptop) for clubs and private parties. Interestingly, these kinds
of demos were rather easy to implement once the server platform was available. Two students
were able to do both the PowerPoint and MP3 demos in just a few days. However, the
implementations that used the embedded microserver hardware were the most interesting.
17. 17
6. APPLICTIONS:
6.1 THE TOY CRANE DEMONSTRATOR:
The toy crane demonstrator is a typical candidate for a pluggable server. We bought a toy
crane and removed the cable remote to connect the motors to relays. We then connected these
relays to a Microservers general- purpose ports, including the corresponding UI.
Figure 9. The toy crane demonstrator.The server is located in the driver’s cab and connected
through relays to the crane’s motors. The (a) current WAP menu displayed is used to (b) lift and
lower the crane’s boom.
18. 18
Figure 10. (a) The installation bus provides a network between devices and controls; (b) all
devices and controls are connected via a Bus Coupling Unit (BCU).
We purposely selected the toy crane to see whether a WAP UI could sufficiently replace
the powerful joystick operation. We showed the crane at trade shows and to the Bluetooth
congress. Users familiar with WAP browsers could operate the crane intuitively without major
instructions. We displayed the links as small icons representing individual control options. The
phone UI didn’t allow any proportional control (similar to a joystick), but we implemented the
WAP content (see Figure 9) such that users could repeatedly start and stop a selected movement
(for example, “lower the boom”) by pressing the same button. The delay between key presses
and motor activation was negligible.
19. 19
6.2 HOME AUTOMATION:
For the next demonstrator, we connected a bluetooth server to a home bus. The goal was
to operate and control devices on the home bus via Bluetooth phones. We implemented a
working version of the demo using the PC reference implementation. The most widely deployed
installation bus for home automation in Europe is the European Installation Bus.
An installation bus system aims to decouple network control and AC power distribution.
This is achieved by providing two logically independent networks: first, the 110/220V power
distribution network, and second, a low-voltage network for control purposes. Alternatively, the
control information could be transmitted through the power distribution network using
modulation techniques, which saves extra wiring (a “power line EIB”). The advantage of
separating power distribution and control is that the connection between control points (switches,
dimmers, and control pads) and devices is not hardwired but can be configured. Similar to a
computer network, datagrams are sent between control points and devices to trigger the desired
actions in the devices—like switching a light on and off. Every control point (switch, button,
control pad, and so forth) can be set up to control every device or clusters of devices (see Figure
10a). In the simplest case, a light switch is configured to switch a particular lamp on or off. A PC
or a dedicated EIB device connected to the installation bus configures the network. EIB control
points usually consist of two components. The main part, normally not visible to the user, is the
Bus Coupling Unit (see Figure 10b). The second part, the application module, contains the UI
and the control logic. This could be a simple light switch but also a heating regulator. The
application unit is plugged directly into the BCU’s physical external interface (PEI) and thus
hides the BCU in the wall. EIB bus systems are widely deployed, mainly in office buildings and
hospitals but also in houses. Although these systems provide some convenience, they still suffer
from the fact that the UI to the home network is largely unchanged compared to plain old
installations: switches, dimmers, and so forth.
Here the idea of the pluggable server comes into play: Every BCU can send control
datagrams to any device connected to the installation bus. Logically, we could go into an EIB
20. 20
networked building, unplug an arbitrary application module, and plug a WAP-over-Bluetooth
microserver into the BCU using the PEI interface (see Figure 11). Once the microserver is loaded
with the correct content, a user can control any device connected to the installation bus through
his or her Bluetooth phone’s WAP browser. For our demonstrator, we connected a Bluetooth-
equipped laptop to the BCU. In Cooltown terms, this could be called a placeManager, 7 because
it provides a Web presence for the devices and organizes them in its Web presentation.
Figure 11. Controlling the home network via a plugged-in WAP-over- Bluetooth server.
To ease content creation, we created a software tool that automatically converts the
network configuration data into server content. The configuration data is available as a binary
file, which is created by the commercial EIB software tool used to configure the installation bus.
The most interesting lesson learned from this demonstrator is that, in some areas, deploying
pervasive computing applications does not suffer from the famous henand- egg problem. These
installation busses, for example, are deployed today and a small additional investment for the
pluggable server turns such a building into an attentive environment. Typical installation busses
also contain sensors such as light meters and thermometers that might provide useful context
information. It would be interesting to study how to make the WAP UI context aware, also
taking into account personal usage patterns.
21. 21
7. CONCLUSION:
Future implementations of both mobile and embedded servers will be more powerful and
thus will use true distributed computing middleware. However, for now, we have shown that
connecting electronic devices to the Web with inexpensive standard technolog is possible and is
sufficient for many applications. A major challenge will be to identify application areas where
we can deploy pervasive computing technology in consumer domains without major investments
in infrastructure. One possibility is to determine where we can add value to legacy systems by
adding embedded server technology, like we did with the EIB implementation. Finally, we have
to give device manufacturers a cost efficient option for making their products ready for
integration into a pervasive computing environment without committing to a particular pervasive
computing technology or middleware. A simple—yet to be standardized—control interface is
such an option.
22. 22
8. BIBILIOGRAPHY:
1. US Patent 5,956,487, “Embedding Web Access Mechanisms in an Appliance for User
Interface Functions Including a Web Server and Web Browser,”1996, document US 5956487;
www.depatisnet.de.
2. S. Hartwig et al., “WAP over Bluetooth: Technology and Applications,” IEEE Int’l Conf.
Consumer Electronics, IEEE Press, Piscataway, N.J., 2001.
3. J. Bentham, TCP/IP Lean, CMP Books, 2000.
4. B.A. Myers, “Using Hand-Held Devices and PCs Together,” Comm. ACM, vol. 44, no. 11,
Nov. 2001, pp. 34–41.
5. J. Burkhardt et al., Pervasive Computing, Addison Wesley, Reading, Mass., 2002.
6. Patent Application WO 01/41408 01 A1, “A Device and a Method for Operating an Electronic
Utility Device from a Portable Telecommunication Apparatus,” document W0200141408;
www.depatisnet.de.
7. T. Kindberg et al., “People, Places, Things: Web Presence for the Real World,” Proc. 3rd IEEE
Workshop Mobile Computing Systems and Applications (WMCSA’00), IEEE CS Press, Los
Alamitos, Calif., 2000, pp. 19–21.