1) The document discusses 6LoWPAN (IPv6 over Low-Power Wireless Personal Area Networks), which allows IPv6 packets to be sent over IEEE 802.15.4 low-power networks.
2) A key challenge is that the large IPv6 address and header do not fit efficiently into the small 802.15.4 frames, so 6LoWPAN defines header compression methods.
3) 6LoWPAN defines a dispatch byte and optional headers for mesh routing, header compression, and fragmentation to optimize IPv6 packets for transmission over 802.15.4 networks.
Scaling the Web to Billions of Nodes: Towards the IPv6 “Internet of Things” b...gogo6
gogo6 IPv6 Video Series. Event, presentation and speaker details below:
EVENT
gogoNET LIVE! 4: IPv6 & The Internet of Things. http://gogonetlive.com
November 12 – 14, 201, Silicon Valley, California
Agenda: http://gogonetlive.com/gogonetlive4-agenda.asp
PRESENTATION
Scaling the Web to Billions of Nodes: Towards the IPv6 “Internet of Things”
Abstract: http://www.gogo6.com/profiles/blogs/scaling-the-web-to-billions-of-nodes-towards-the-ipv6-internet-of
Presentation video: http://www.gogo6.com/video/scaling-the-web-to-billions-of-nodes-by-carsten-bormann-at-gogone
Interview video: http://www.gogo6.com/video/interview-with-carsten-bormann-at-gogonet-live-4-ipv6-iot-confere
SPEAKER
Carsten Bormann - Universität Bremen TZI & IETF WG Chair
Bio/Profile: http://www.gogo6.com/profile/CarstenBormann
MORE
Learn more about IPv6 on the gogoNET social network and our online training courses
http://www.gogo6.com/main
Get free IPv6 connectivity with Freenet6
http://www.gogo6.com/Freenet6
Subscribe to the gogo6 IPv6 Channel on YouTube
http://www.youtube.com/subscription_center?add_user=gogo6videos
Follow gogo6 on Twitter
http://twitter.com/gogo6inc
Like gogo6 on Facebook
http://www.facebook.com/pages/IPv6-products-community-and-services-gogo6/161626696777
3 hours course on IEEE and IETF protocols introducing the 6TiSCH architecture and the RPL routing protocol. Course given at telecom Bretagne on Feb 12th 2014
Ein Anlass des www.swissipv6council.ch
Referentin: Nathalie Trenaman, RIPE NCC
Nathalie Trenaman von RIPE wird in ihrem Referat Best Practices zur Adressierung vermitteln und aufzeigen, wie Firmen zu ihrem IPv6 Range kommen. Die definitive Agenda wird so bald wie möglich bekannt gegeben.
Das Referat wird in Englisch gehalten.
18:00 Uhr
Begrüssung durch Silvia Hagen, Präsidentin Swiss IPv6 Council
18:05 Uhr
Nathalie Trenaman, RIPE
Inhalt:
1. Teil
IPv6 Adressierung
Wie muss ich ein IPv6 Netzwerk konzeptionell aufsetzen?
2. Teil
Policies
Vorstellung der Möglichkeiten für Unternehmen, sich die IPv6 Adressen zu sichern
Wer bekommt welche Ranges?
Wie muss man sich bewerben?
Q&A
Über RIPE NCC
RIPE NCC is the Regional Internet Registry responsible for IPv6 distribution in Europe, Middle East and Central Asia. We build awareness among all Internet stakeholders of the need to deploy IPv6. At this moment, RIPE NCC has over 10.000 members. 69% of these members have a block of IPv6 addresses. The first hurdle of an IPv6 deployment is building a scalable IPv6 addressing plan. Since there are so many addresses and distribution is done in subnets, a lot of engineers and architects see this phase of the deployment as one of the most challenging. Nathalie will shine a light on current best practices, taking into account different transitioning mechanisms and end users.
Many network operators still struggle with which type of data-plane encoding they should use for segment routing. The world is hyper-connected and we can’t afford to be late to deliver 5G. Using IPv4, IPv6 and MPLS data-plane encoding keeps us moving forward.
IoT Field Area Network Solutions & Integration of IPv6 Standards by Patrick G...gogo6
gogo6 IPv6 Video Series. Event, presentation and speaker details below:
EVENT
gogoNET LIVE! 4: IPv6 & The Internet of Things. http://gogonetlive.com
November 12 – 14, 201, Silicon Valley, California
Agenda: http://gogonetlive.com/gogonetlive4-agenda.asp
PRESENTATION
IoT Field Area Network Solutions & Integration of IPv6 Standards
Abstract: http://www.gogo6.com/profiles/blogs/my-presentation-at-gogolive-integration-of-ipv4-and-non-ip
Presentation video: http://www.gogo6.com/video/iot-field-area-network-solutions-integration-of-ipv6-standards-by
Interview video: http://www.gogo6.com/video/interview-with-carsten-bormann-at-gogonet-live-4-ipv6-iot-confere
SPEAKER
Patrick Grossetete - Technical Marketing Engineer (IoT), Cisco
Bio/Profile: http://www.gogo6.com/profile/PatrickGrossetete
MORE
Learn more about IPv6 on the gogoNET social network and our online training courses
http://www.gogo6.com/main
Get free IPv6 connectivity with Freenet6
http://www.gogo6.com/Freenet6
Subscribe to the gogo6 IPv6 Channel on YouTube
http://www.youtube.com/subscription_center?add_user=gogo6videos
Follow gogo6 on Twitter
http://twitter.com/gogo6inc
Like gogo6 on Facebook
http://www.facebook.com/pages/IPv6-products-community-and-services-gogo6/161626696777
Scaling the Web to Billions of Nodes: Towards the IPv6 “Internet of Things” b...gogo6
gogo6 IPv6 Video Series. Event, presentation and speaker details below:
EVENT
gogoNET LIVE! 4: IPv6 & The Internet of Things. http://gogonetlive.com
November 12 – 14, 201, Silicon Valley, California
Agenda: http://gogonetlive.com/gogonetlive4-agenda.asp
PRESENTATION
Scaling the Web to Billions of Nodes: Towards the IPv6 “Internet of Things”
Abstract: http://www.gogo6.com/profiles/blogs/scaling-the-web-to-billions-of-nodes-towards-the-ipv6-internet-of
Presentation video: http://www.gogo6.com/video/scaling-the-web-to-billions-of-nodes-by-carsten-bormann-at-gogone
Interview video: http://www.gogo6.com/video/interview-with-carsten-bormann-at-gogonet-live-4-ipv6-iot-confere
SPEAKER
Carsten Bormann - Universität Bremen TZI & IETF WG Chair
Bio/Profile: http://www.gogo6.com/profile/CarstenBormann
MORE
Learn more about IPv6 on the gogoNET social network and our online training courses
http://www.gogo6.com/main
Get free IPv6 connectivity with Freenet6
http://www.gogo6.com/Freenet6
Subscribe to the gogo6 IPv6 Channel on YouTube
http://www.youtube.com/subscription_center?add_user=gogo6videos
Follow gogo6 on Twitter
http://twitter.com/gogo6inc
Like gogo6 on Facebook
http://www.facebook.com/pages/IPv6-products-community-and-services-gogo6/161626696777
3 hours course on IEEE and IETF protocols introducing the 6TiSCH architecture and the RPL routing protocol. Course given at telecom Bretagne on Feb 12th 2014
Ein Anlass des www.swissipv6council.ch
Referentin: Nathalie Trenaman, RIPE NCC
Nathalie Trenaman von RIPE wird in ihrem Referat Best Practices zur Adressierung vermitteln und aufzeigen, wie Firmen zu ihrem IPv6 Range kommen. Die definitive Agenda wird so bald wie möglich bekannt gegeben.
Das Referat wird in Englisch gehalten.
18:00 Uhr
Begrüssung durch Silvia Hagen, Präsidentin Swiss IPv6 Council
18:05 Uhr
Nathalie Trenaman, RIPE
Inhalt:
1. Teil
IPv6 Adressierung
Wie muss ich ein IPv6 Netzwerk konzeptionell aufsetzen?
2. Teil
Policies
Vorstellung der Möglichkeiten für Unternehmen, sich die IPv6 Adressen zu sichern
Wer bekommt welche Ranges?
Wie muss man sich bewerben?
Q&A
Über RIPE NCC
RIPE NCC is the Regional Internet Registry responsible for IPv6 distribution in Europe, Middle East and Central Asia. We build awareness among all Internet stakeholders of the need to deploy IPv6. At this moment, RIPE NCC has over 10.000 members. 69% of these members have a block of IPv6 addresses. The first hurdle of an IPv6 deployment is building a scalable IPv6 addressing plan. Since there are so many addresses and distribution is done in subnets, a lot of engineers and architects see this phase of the deployment as one of the most challenging. Nathalie will shine a light on current best practices, taking into account different transitioning mechanisms and end users.
Many network operators still struggle with which type of data-plane encoding they should use for segment routing. The world is hyper-connected and we can’t afford to be late to deliver 5G. Using IPv4, IPv6 and MPLS data-plane encoding keeps us moving forward.
IoT Field Area Network Solutions & Integration of IPv6 Standards by Patrick G...gogo6
gogo6 IPv6 Video Series. Event, presentation and speaker details below:
EVENT
gogoNET LIVE! 4: IPv6 & The Internet of Things. http://gogonetlive.com
November 12 – 14, 201, Silicon Valley, California
Agenda: http://gogonetlive.com/gogonetlive4-agenda.asp
PRESENTATION
IoT Field Area Network Solutions & Integration of IPv6 Standards
Abstract: http://www.gogo6.com/profiles/blogs/my-presentation-at-gogolive-integration-of-ipv4-and-non-ip
Presentation video: http://www.gogo6.com/video/iot-field-area-network-solutions-integration-of-ipv6-standards-by
Interview video: http://www.gogo6.com/video/interview-with-carsten-bormann-at-gogonet-live-4-ipv6-iot-confere
SPEAKER
Patrick Grossetete - Technical Marketing Engineer (IoT), Cisco
Bio/Profile: http://www.gogo6.com/profile/PatrickGrossetete
MORE
Learn more about IPv6 on the gogoNET social network and our online training courses
http://www.gogo6.com/main
Get free IPv6 connectivity with Freenet6
http://www.gogo6.com/Freenet6
Subscribe to the gogo6 IPv6 Channel on YouTube
http://www.youtube.com/subscription_center?add_user=gogo6videos
Follow gogo6 on Twitter
http://twitter.com/gogo6inc
Like gogo6 on Facebook
http://www.facebook.com/pages/IPv6-products-community-and-services-gogo6/161626696777
You may have hoped to retire before IPv6 became a reality, but unfortunately the IPv4 address exhaustion came too fast. For the rest of us, we’re going to bite off a small piece of the 15-year old IPv6 pie and talk about how to get started!
• Address format refresher
• IPv4 and IPv6 protocol comparison
• IPv6 neighbor discovery and auto-configuration
• Current migration and coexistence strategies
• ICMPv6, DHCPv6, and DNSv6
• How to get started at home
Network State Awareness & Troubleshooting, by Faraz Shamim.
A presentation given at APRICOT 2016’s Network State Awareness and Troubleshooting tutorial on 25 February 2016.
TRUST BASED ROUTING METRIC FOR RPL ROUTING PROTOCOL IN THE INTERNET OF THINGSpijans
While smart factories are becoming widely recognized as a fundamental concept of Industry 4.0, their implementation has posed several challenges insofar that they generate and process vast amounts of security critical and privacy sensitive data, in addition to the fact that they deploy IoT heterogeneous and constrained devices communicating with each other and being accessed ubiquitously through lossy networks. In this scenario, the routing of data is a specific area of concern especially with the inherent constraints and limiting properties of such devices like processing resources, memory capacity and battery life. To suit these constraints and to provide the required connectivity, the IETF has developed several standards, among them the RPL routing protocol for Low powerand Lossy Networks (LLNs). However, and even though RPL provides support for integrity and confidentiality of messages, its security may be compromised by several threats and attacks. We propose in this work TRM-RPL, a Trust based Routing Metric for the RPL protocol in an IIoT based environments. TRM-RPL uses a trust management mechanism to detect malicious behaviors and resist routing attacks while providing QoS guarantees. In addition, our model addresses both node and link trust and follows a multidimensional approach to enable
an accurate trust assessment for IoT entities. TRM-RPL is implemented, successfully tested and compared with the standard RPL protocol where its effectiveniness and resilience to attacks has been proved to be better.
APNIC Chief Scientist Geoff Huston presented on the various approached used by root servers to deliver large DNS responses at the DNS-OARC 26 in Madrid from 15 to 16 May 2017.
Dr. Christos Kolias – Senior Research Scientist
Keynote Title: “NFV: Empowering the Network”
Keynote Abstract: Network Functions Virtualization (NFV) envisions and promises to change the service provider landscape and has emerged as one of one of today’s significant trends. Although less than two years old, NFV has garnered the industry’s full attention and support. Moving swiftly, a number of key accomplishments have already taken place, and a lot more work is currently under way within ETSI NFV while we are embarking on its future phase. Various proofs-of-concepts (ranging from vEPC to vCPE, vIMS and vCDN) are being developed while issues such as open source and SDN are becoming key ingredients as the can play a pivotal role.
Dr. Christos Kolias' Bio: Christos Kolias is a senior research scientist at Orange Silicon Valley (a subsidiary of Orange). Christos is a co-founder of the ETSI NFV group and had led the formation of ONF’s Wireless & Mobile working group. He has lectured on NFV and SDN at several events. Christos has more than 15 years of experience in networking, he is the originator of Virtual Output Queueing (VOQ) used in packet switching. He holds a Ph.D. in Computer Science from UCLA.
---------------------------------------------------
★ Resources ★
Zerista: http://lcu14.zerista.com/event/member/137765
Google Event: https://plus.google.com/u/0/events/cpeksim4hr4ghhuufv5ic4viirs
Video: https://www.youtube.com/watch?v=tFDnj_342n4&list=UUIVqQKxCyQLJS6xvSmfndLA
Etherpad: http://pad.linaro.org/p/lcu14-400a
---------------------------------------------------
★ Event Details ★
Linaro Connect USA - #LCU14
September 15-19th, 2014
Hyatt Regency San Francisco Airport
---------------------------------------------------
http://www.linaro.org
http://connect.linaro.org
Migration of corperate networks from ipv4 to ipv6 using dual stackpraveenReddy268
Migration of corperate networks from ipv4 to ipv6 using dual stack
in this you will be learning about internet protocols of version4 & 6.And also about OSI layers and their architecture and coding to the routers
Haystack XR Mode radically improves the range of IoT devices using Semtech's LoRa radio. Using the same error correction used in deep space probes along with other techniques, Haystack offers the longest range, lowest power, and lowest latency networking stack for LoRa today.
You may have hoped to retire before IPv6 became a reality, but unfortunately the IPv4 address exhaustion came too fast. For the rest of us, we’re going to bite off a small piece of the 15-year old IPv6 pie and talk about how to get started!
• Address format refresher
• IPv4 and IPv6 protocol comparison
• IPv6 neighbor discovery and auto-configuration
• Current migration and coexistence strategies
• ICMPv6, DHCPv6, and DNSv6
• How to get started at home
Network State Awareness & Troubleshooting, by Faraz Shamim.
A presentation given at APRICOT 2016’s Network State Awareness and Troubleshooting tutorial on 25 February 2016.
TRUST BASED ROUTING METRIC FOR RPL ROUTING PROTOCOL IN THE INTERNET OF THINGSpijans
While smart factories are becoming widely recognized as a fundamental concept of Industry 4.0, their implementation has posed several challenges insofar that they generate and process vast amounts of security critical and privacy sensitive data, in addition to the fact that they deploy IoT heterogeneous and constrained devices communicating with each other and being accessed ubiquitously through lossy networks. In this scenario, the routing of data is a specific area of concern especially with the inherent constraints and limiting properties of such devices like processing resources, memory capacity and battery life. To suit these constraints and to provide the required connectivity, the IETF has developed several standards, among them the RPL routing protocol for Low powerand Lossy Networks (LLNs). However, and even though RPL provides support for integrity and confidentiality of messages, its security may be compromised by several threats and attacks. We propose in this work TRM-RPL, a Trust based Routing Metric for the RPL protocol in an IIoT based environments. TRM-RPL uses a trust management mechanism to detect malicious behaviors and resist routing attacks while providing QoS guarantees. In addition, our model addresses both node and link trust and follows a multidimensional approach to enable
an accurate trust assessment for IoT entities. TRM-RPL is implemented, successfully tested and compared with the standard RPL protocol where its effectiveniness and resilience to attacks has been proved to be better.
APNIC Chief Scientist Geoff Huston presented on the various approached used by root servers to deliver large DNS responses at the DNS-OARC 26 in Madrid from 15 to 16 May 2017.
Dr. Christos Kolias – Senior Research Scientist
Keynote Title: “NFV: Empowering the Network”
Keynote Abstract: Network Functions Virtualization (NFV) envisions and promises to change the service provider landscape and has emerged as one of one of today’s significant trends. Although less than two years old, NFV has garnered the industry’s full attention and support. Moving swiftly, a number of key accomplishments have already taken place, and a lot more work is currently under way within ETSI NFV while we are embarking on its future phase. Various proofs-of-concepts (ranging from vEPC to vCPE, vIMS and vCDN) are being developed while issues such as open source and SDN are becoming key ingredients as the can play a pivotal role.
Dr. Christos Kolias' Bio: Christos Kolias is a senior research scientist at Orange Silicon Valley (a subsidiary of Orange). Christos is a co-founder of the ETSI NFV group and had led the formation of ONF’s Wireless & Mobile working group. He has lectured on NFV and SDN at several events. Christos has more than 15 years of experience in networking, he is the originator of Virtual Output Queueing (VOQ) used in packet switching. He holds a Ph.D. in Computer Science from UCLA.
---------------------------------------------------
★ Resources ★
Zerista: http://lcu14.zerista.com/event/member/137765
Google Event: https://plus.google.com/u/0/events/cpeksim4hr4ghhuufv5ic4viirs
Video: https://www.youtube.com/watch?v=tFDnj_342n4&list=UUIVqQKxCyQLJS6xvSmfndLA
Etherpad: http://pad.linaro.org/p/lcu14-400a
---------------------------------------------------
★ Event Details ★
Linaro Connect USA - #LCU14
September 15-19th, 2014
Hyatt Regency San Francisco Airport
---------------------------------------------------
http://www.linaro.org
http://connect.linaro.org
Migration of corperate networks from ipv4 to ipv6 using dual stackpraveenReddy268
Migration of corperate networks from ipv4 to ipv6 using dual stack
in this you will be learning about internet protocols of version4 & 6.And also about OSI layers and their architecture and coding to the routers
Haystack XR Mode radically improves the range of IoT devices using Semtech's LoRa radio. Using the same error correction used in deep space probes along with other techniques, Haystack offers the longest range, lowest power, and lowest latency networking stack for LoRa today.
Overview of Haystack's DASH7 technology, features, & applications. Includes information on real-time outdoor and indoor location. Discussion of Haystack support for Semtech's LoRa LPWAN radio.
A session in the DevNet Zone at Cisco Live, Berlin. Flare allows users with mobile devices to discover and interact with things in an environment. It combines multiple location technologies, such as iBeacon and CMX, with a realtime communications architecture to enable new kinds of user interactions. This session will introduce the Flare REST and Socket.IO API, server, client libraries and sample code, and introduce you to the resources available on DevNet and GitHub. Come visit us in the DevNet zone for a hands-on demonstration.
Hybrid optimization of pumped hydro system and solar- Engr. Abdul-Azeez.pdffxintegritypublishin
Advancements in technology unveil a myriad of electrical and electronic breakthroughs geared towards efficiently harnessing limited resources to meet human energy demands. The optimization of hybrid solar PV panels and pumped hydro energy supply systems plays a pivotal role in utilizing natural resources effectively. This initiative not only benefits humanity but also fosters environmental sustainability. The study investigated the design optimization of these hybrid systems, focusing on understanding solar radiation patterns, identifying geographical influences on solar radiation, formulating a mathematical model for system optimization, and determining the optimal configuration of PV panels and pumped hydro storage. Through a comparative analysis approach and eight weeks of data collection, the study addressed key research questions related to solar radiation patterns and optimal system design. The findings highlighted regions with heightened solar radiation levels, showcasing substantial potential for power generation and emphasizing the system's efficiency. Optimizing system design significantly boosted power generation, promoted renewable energy utilization, and enhanced energy storage capacity. The study underscored the benefits of optimizing hybrid solar PV panels and pumped hydro energy supply systems for sustainable energy usage. Optimizing the design of solar PV panels and pumped hydro energy supply systems as examined across diverse climatic conditions in a developing country, not only enhances power generation but also improves the integration of renewable energy sources and boosts energy storage capacities, particularly beneficial for less economically prosperous regions. Additionally, the study provides valuable insights for advancing energy research in economically viable areas. Recommendations included conducting site-specific assessments, utilizing advanced modeling tools, implementing regular maintenance protocols, and enhancing communication among system components.
Automobile Management System Project Report.pdfKamal Acharya
The proposed project is developed to manage the automobile in the automobile dealer company. The main module in this project is login, automobile management, customer management, sales, complaints and reports. The first module is the login. The automobile showroom owner should login to the project for usage. The username and password are verified and if it is correct, next form opens. If the username and password are not correct, it shows the error message.
When a customer search for a automobile, if the automobile is available, they will be taken to a page that shows the details of the automobile including automobile name, automobile ID, quantity, price etc. “Automobile Management System” is useful for maintaining automobiles, customers effectively and hence helps for establishing good relation between customer and automobile organization. It contains various customized modules for effectively maintaining automobiles and stock information accurately and safely.
When the automobile is sold to the customer, stock will be reduced automatically. When a new purchase is made, stock will be increased automatically. While selecting automobiles for sale, the proposed software will automatically check for total number of available stock of that particular item, if the total stock of that particular item is less than 5, software will notify the user to purchase the particular item.
Also when the user tries to sale items which are not in stock, the system will prompt the user that the stock is not enough. Customers of this system can search for a automobile; can purchase a automobile easily by selecting fast. On the other hand the stock of automobiles can be maintained perfectly by the automobile shop manager overcoming the drawbacks of existing system.
Welcome to WIPAC Monthly the magazine brought to you by the LinkedIn Group Water Industry Process Automation & Control.
In this month's edition, along with this month's industry news to celebrate the 13 years since the group was created we have articles including
A case study of the used of Advanced Process Control at the Wastewater Treatment works at Lleida in Spain
A look back on an article on smart wastewater networks in order to see how the industry has measured up in the interim around the adoption of Digital Transformation in the Water Industry.
CFD Simulation of By-pass Flow in a HRSG module by R&R Consult.pptxR&R Consult
CFD analysis is incredibly effective at solving mysteries and improving the performance of complex systems!
Here's a great example: At a large natural gas-fired power plant, where they use waste heat to generate steam and energy, they were puzzled that their boiler wasn't producing as much steam as expected.
R&R and Tetra Engineering Group Inc. were asked to solve the issue with reduced steam production.
An inspection had shown that a significant amount of hot flue gas was bypassing the boiler tubes, where the heat was supposed to be transferred.
R&R Consult conducted a CFD analysis, which revealed that 6.3% of the flue gas was bypassing the boiler tubes without transferring heat. The analysis also showed that the flue gas was instead being directed along the sides of the boiler and between the modules that were supposed to capture the heat. This was the cause of the reduced performance.
Based on our results, Tetra Engineering installed covering plates to reduce the bypass flow. This improved the boiler's performance and increased electricity production.
It is always satisfying when we can help solve complex challenges like this. Do your systems also need a check-up or optimization? Give us a call!
Work done in cooperation with James Malloy and David Moelling from Tetra Engineering.
More examples of our work https://www.r-r-consult.dk/en/cases-en/
Water scarcity is the lack of fresh water resources to meet the standard water demand. There are two type of water scarcity. One is physical. The other is economic water scarcity.
NO1 Uk best vashikaran specialist in delhi vashikaran baba near me online vas...Amil Baba Dawood bangali
Contact with Dawood Bhai Just call on +92322-6382012 and we'll help you. We'll solve all your problems within 12 to 24 hours and with 101% guarantee and with astrology systematic. If you want to take any personal or professional advice then also you can call us on +92322-6382012 , ONLINE LOVE PROBLEM & Other all types of Daily Life Problem's.Then CALL or WHATSAPP us on +92322-6382012 and Get all these problems solutions here by Amil Baba DAWOOD BANGALI
#vashikaranspecialist #astrologer #palmistry #amliyaat #taweez #manpasandshadi #horoscope #spiritual #lovelife #lovespell #marriagespell#aamilbabainpakistan #amilbabainkarachi #powerfullblackmagicspell #kalajadumantarspecialist #realamilbaba #AmilbabainPakistan #astrologerincanada #astrologerindubai #lovespellsmaster #kalajaduspecialist #lovespellsthatwork #aamilbabainlahore#blackmagicformarriage #aamilbaba #kalajadu #kalailam #taweez #wazifaexpert #jadumantar #vashikaranspecialist #astrologer #palmistry #amliyaat #taweez #manpasandshadi #horoscope #spiritual #lovelife #lovespell #marriagespell#aamilbabainpakistan #amilbabainkarachi #powerfullblackmagicspell #kalajadumantarspecialist #realamilbaba #AmilbabainPakistan #astrologerincanada #astrologerindubai #lovespellsmaster #kalajaduspecialist #lovespellsthatwork #aamilbabainlahore #blackmagicforlove #blackmagicformarriage #aamilbaba #kalajadu #kalailam #taweez #wazifaexpert #jadumantar #vashikaranspecialist #astrologer #palmistry #amliyaat #taweez #manpasandshadi #horoscope #spiritual #lovelife #lovespell #marriagespell#aamilbabainpakistan #amilbabainkarachi #powerfullblackmagicspell #kalajadumantarspecialist #realamilbaba #AmilbabainPakistan #astrologerincanada #astrologerindubai #lovespellsmaster #kalajaduspecialist #lovespellsthatwork #aamilbabainlahore #Amilbabainuk #amilbabainspain #amilbabaindubai #Amilbabainnorway #amilbabainkrachi #amilbabainlahore #amilbabaingujranwalan #amilbabainislamabad
Quality defects in TMT Bars, Possible causes and Potential Solutions.PrashantGoswami42
Maintaining high-quality standards in the production of TMT bars is crucial for ensuring structural integrity in construction. Addressing common defects through careful monitoring, standardized processes, and advanced technology can significantly improve the quality of TMT bars. Continuous training and adherence to quality control measures will also play a pivotal role in minimizing these defects.
Courier management system project report.pdfKamal Acharya
It is now-a-days very important for the people to send or receive articles like imported furniture, electronic items, gifts, business goods and the like. People depend vastly on different transport systems which mostly use the manual way of receiving and delivering the articles. There is no way to track the articles till they are received and there is no way to let the customer know what happened in transit, once he booked some articles. In such a situation, we need a system which completely computerizes the cargo activities including time to time tracking of the articles sent. This need is fulfilled by Courier Management System software which is online software for the cargo management people that enables them to receive the goods from a source and send them to a required destination and track their status from time to time.
COLLEGE BUS MANAGEMENT SYSTEM PROJECT REPORT.pdfKamal Acharya
The College Bus Management system is completely developed by Visual Basic .NET Version. The application is connect with most secured database language MS SQL Server. The application is develop by using best combination of front-end and back-end languages. The application is totally design like flat user interface. This flat user interface is more attractive user interface in 2017. The application is gives more important to the system functionality. The application is to manage the student’s details, driver’s details, bus details, bus route details, bus fees details and more. The application has only one unit for admin. The admin can manage the entire application. The admin can login into the application by using username and password of the admin. The application is develop for big and small colleges. It is more user friendly for non-computer person. Even they can easily learn how to manage the application within hours. The application is more secure by the admin. The system will give an effective output for the VB.Net and SQL Server given as input to the system. The compiled java program given as input to the system, after scanning the program will generate different reports. The application generates the report for users. The admin can view and download the report of the data. The application deliver the excel format reports. Because, excel formatted reports is very easy to understand the income and expense of the college bus. This application is mainly develop for windows operating system users. In 2017, 73% of people enterprises are using windows operating system. So the application will easily install for all the windows operating system users. The application-developed size is very low. The application consumes very low space in disk. Therefore, the user can allocate very minimum local disk space for this application.
2. 2
2007 - The IP/USN Arrives
IP/LoWPAN Router
IP/LoWPAN Sensor Router
IP Device
IP Network
(powered)
LoWPAN-Extended IP Network
IP/LoWPAN Router
IP/LoWPAN Sensor Router
IP Device
IP Network
(powered)
LoWPAN-Extended IP Network
4. 4
6LoWPAN …
what it means for sensors
• Low-Power Wireless Embedded devices can now be
connected using familiar networking technology,
– like ethernet (but even where wiring is not viable)
– and like WiFi (but even where power is not plentiful)
• all of these can interoperate in real applications
• Interoperate with traditional computing infrastructure
• Utilize modern security techniques
• Application Requirements and Capacity Plan dictate
how the network is organized,
– not artifacts of the underlying technology
5. 5
Internet – Networks of Networks
• Networks
– Ethernet
– WiFi
– Serial links
• connect hosts
and devices and
other networks
together
• Horizontally
integrated
• Peripheral
Interconnects
– USB, Firewire
– IDE / SCSI
– RS232,RS485
– IRDA
– BlueTooth
• connect one or more
devices to a host
computer
• Vertically integrated
– Physical link to
application
ethernet
wifi
LoWPAN
vs
6. 6
Which are sensors like?
WiFi
Ethernet
GPRS Controllers
Field
Units
Data
Analytics
Trending
Monitoring
Management
Operations
RS232
RS485
hartcomm.org
7. 7
802.5
Token Ring
Internet Concepts: Layering
802.3
Ethernet
802.11
WiFi802.3a
Ethernet
10b2
802.3i
Ethernet
10bT
802.3y
Ethernet
100bT
802.3ab
Ethernet
1000bT
802.3an
Ethernet
1G bT
802.11a
WiFi802.11b
WiFi802.11g
WiFi802.11n
WiFi
X3T9.5
FDDI
Serial
Modem
GPRS
ISDN
DSL
Sonet
Transport (UDP/IP, TCP/IP)
Application (Telnet, FTP, SMTP, SNMP, HTTP)
Diverse Object and Data Models (HTML, XML, …, BacNet, …)
802.15.4
LoWPAN
Network (IP)
Link2: link
3: net
4: xport
7: app
1: phy
6LoWPAN
8. 8
Making sensor nets make sense
802.15.4, …802.11Ethernet Sonet
XML / RPC / REST / SOAP / OSGI
IP
IETF 6lowpan
Web Services
TCP / UDP
HTTP / FTP / SNMP
Proxy/Gateway
LoWPAN – 802.15.4
• 1% of 802.11 power, easier to
embed, as easy to use.
• 8-16 bit MCUs with KBs, not
MBs.
• Off 99% of the time
9. 9
Many Advantages of IP
• Extensive interoperability
– Other wireless embedded 802.15.4 network devices
– Devices on any other IP network link (WiFi, Ethernet, GPRS, Serial lines, …)
• Established security
– Authentication, access control, and firewall mechanisms
– Network design and policy determines access, not the technology
• Established naming, addressing, translation, lookup, discovery
• Established proxy architectures for higher-level services
– NAT, load balancing, caching, mobility
• Established application level data model and services
– HTTP/HTML/XML/SOAP/REST, Application profiles
• Established network management tools
– Ping, Traceroute, SNMP, … OpenView, NetManager, Ganglia, …
• Transport protocols
– End-to-end reliability in addition to link reliability
• Most “industrial” (wired and wireless) standards support an IP option
10. 10
Leverage existing standards, rather than
“reinventing the wheel”
• RFC 768 UDP - User Datagram Protocol [1980]
• RFC 791 IPv4 – Internet Protocol [1981]
• RFC 792 ICMPv4 – Internet Control Message Protocol [1981]
• RFC 793 TCP – Transmission Control Protocol [1981]
• RFC 862 Echo Protocol [1983]
• RFC 1101 DNS
Encoding of Network Names and Other Types [1989]
• RFC 1191 IPv4 Path MTU Discovery [1990]
• RFC 1981 IPv6 Path MTU Discovery [1996]
• RFC 2131 DHCPv4 -
Dynamic Host Configuration Protocol [1997]
• RFC 2375 IPv6
Multicast Address Assignments [1998]
• RFC 2460 IPv6 [1998]
• RFC 2463 ICMPv6 - Internet Control Message Protocol for IPv6 [1998]
• RFC 2765 Stateless IP/ICMP Translation Algorithm (SIIT) [2000]
• RFC 3068 An Anycast Prefix for 6to4 Relay Routers [2001]
• RFC 3307 Allocation Guidelines for IPv6 Multicast Addresses [2002]
• RFC 3315 DHCPv6 - Dynamic Host Configuration Protocol for IPv6 [2003]
• RFC 3484 Default Address Selection for IPv6 [2003]
• RFC 3587 IPv6 Global Unicast Address Format [2003]
• RFC 3819 Advice for Internet Subnetwork Designers [2004]
• RFC 4007 IPv6 Scoped Address Architecture [2005]
• RFC 4193 Unique Local IPv6 Unicast Addresses [2005]
• RFC 4291 IPv6 Addressing Architecture [2006]
11. 11
IEEE 802.15.4 – The New IP Link
• http://tools.ietf.org/wg/6lowpan/
• Problem Statement: http://tools.ietf.org/html/rfc4919
• Format: http://tools.ietf.org/html/rfc4944
• Routable:
http://tools.ietf.org/id/draft-hui-6lowpan-hc-00.txt
• Interoperability
• Architecture
• 1% of 802.11 power, easier to embed, as easy to use.
13. 13
Key Factors for IP over 802.15.4
• Header
– Standard IPv6 header is 40 bytes [RFC 2460]
– Entire 802.15.4 MTU is 127 bytes [IEEE ]
– Often data payload is small
• Fragmentation
– Interoperability means that applications need not know the constraints of
physical links that might carry their packets
– IP packets may be large, compared to 802.15.4 max frame size
– IPv6 requires all links support 1280 byte packets [RFC 2460]
• Allow link-layer mesh routing under IP topology
– 802.15.4 subnets may utilize multiple radio hops per IP hop
– Similar to LAN switching within IP routing domain in Ethernet
• Allow IP routing over a mesh of 802.15.4 nodes
– Options and capabilities already well-defines
– Various protocols to establish routing tables
• Energy calculations and 6LoWPAN impact
14. 14
6LoWPAN Challenges
• Large IP Address & Header => 16 bit short address / 64 bit EUID
• Minimum Transfer Unit => Fragmentation
• Short range & Embedded => Multiple Hops
Link frame
ctrl src UIDlen chkdst UID link payload
Network packet
UDP datagram or
TCP stream segment
transport header application payload
…, modbus, BacNET/IP, … , HTML, XML, …, ZCL
128 Bytes MAX
40 B + options
1280 Bytes MIN
cls flow len hops src IP dst IP net payload
16 B16 B
NH
15. 15
6LoWPAN – IP Header Optimization
• Eliminate all fields in the IPv6 header that can be derived from the
802.15.4 header in the common case
– Source address : derived from link address
– Destination address : derived from link address
– Length : derived from link frame length
– Traffic Class & Flow Label : zero
– Next header : UDP, TCP, or ICMP
• Additional IPv6 options follow as options
Link frame
ctrl src UIDlen chkdst UID
Network packet
40 B
6LoWPAN adaptation header
hops
3 B
cls flow len hops src IP dst IP net payloadNH
16. 16
IEEE 802.15.4 Frame Format
• Low Bandwidth (250 kbps), low power (1 mW) radio
• Moderately spread spectrum (QPSK) provides robustness
• Simple MAC allows for general use
– Many TinyOS-based protocols (MintRoute, LQI, BVR, …), TinyAODV, Zigbee, SP100.11,
Wireless HART, …
– 6LoWPAN => IP
• Choice among many semiconductor suppliers
• Small Packets to keep packet error rate low and permit media
sharing
preamble
SFD
Len
FCF
DSN
Dst16 Src16
D pan Dst EUID 64 S pan Src EUID 64
Fchk
Network Header Application Data
Max 127 bytes
17. 17
RFC 3189 –
"Advice for Internet Sub-Network Designers"
• Total end-to-end interactive response time should not
exceed human perceivable delays
• Lack of broadcast capability impedes or, in some cases,
renders some protocols inoperable (e.g. DHCP). Broadcast
media can also allow efficient operation of multicast, a
core mechanism of IPv6
• Link-layer error recovery often increases end-to-end
performance. However, it should be lightweight and need
not be perfect, only good enough
• Sub-network designers should minimize delay, delay
variance, and packet loss as much as possible
• Sub-networks operating at low speeds or with small MTUs
should compress IP and transport-level headers (TCP and
UDP)
18. 18
dsp
mhop
HC1
frag
6LoWPAN Format Design
• Orthogonal stackable header format
• Almost no overhead for the ability to interoperate and scale.
• Pay for only what you use
IEEE 802.15.4 Frame Format
IETF 6LoWPAN Format
IP UDP
HC1
Header compression
dsp
Dispatch: coexistence
preamble
SFD
Len
FCF
DSN
Dst16 Src16
D pan Dst EUID 64 S pan Src EUID 64
Fchk
Network Header Application Data
Max 127 bytes
Mesh (L2) routing
HC1
mhop
dsp
HC1
dsp
frag
Message > Frame fragmentation
HC2
19. 19
6LoWPAN – The First Byte
• Coexistence with other network protocols over same link
• Header dispatch - understand what’s coming
IEEE 802.15.4 Frame Format
IETF 6LoWPAN Format
Not a LoWPAN frame00
LoWPAN IPv6 addressing header01
LoWPAN mesh header10
LoWPAN fragmentation header11
preamble
SFD
Len
FCF
DSN
Dst16 Src16
D pan Dst EUID 64 S pan Src EUID 64
Fchk
Network Header Application Data
20. 20
6LoWPAN – IPv6 Header
IEEE 802.15.4 Frame Format
IETF 6LoWPAN Format
dsp
01 1 Uncompressed IPv6 address [RFC2460]0 40 bytes0 0 0 0
01 010 0 0 0 HC1 Fully compressed: 1 byte
Source address : derived from link address
Destination address : derived from link address
Traffic Class & Flow Label : zero
Next header : UDP, TCP, or ICMP
preamble
SFD
Len
FCF
DSN
Dst16 Src16
D pan Dst EUID 64 S pan Src EUID 64
Fchk
Network Header Application Data
21. 21
IPv6 Header Compression
• http://www.visi.com/~mjb/Drawings/IP_Header_v6.pdf
v6 zero
Link local => derive from 802.15.4 header
Link local => derive from 802.15.4 header
In 802.15.4 header
in HC1 byte
uncompressed
22. 22
HC1 Compressed IPv6 Header
• IPv6 address <prefix64 || interface id> for nodes in 802.15.4
subnet derived from the link address.
– PAN ID maps to a unique IPv6 prefix
– Interface identifier generated from EUID64 or Pan ID & short address
• Hop Limit is the only incompressible IPv6 header field
• Source prefix compressed (to L2)
• Source interface identifier compressed (to L2)
• Destination prefix compressed (to L2)
• Destination interface identified compressed (to L2)
• Traffic and Flow Label zero (compressed)
• Next Header
• 00 uncompressed, 01 UDP, 10 TCP, 11 ICMP
• Additional HC2 compression header follows
0 7
HC1 Zero or more uncompressed fields follow in
order
23. 23
6LoWPAN: Compressed IPv6 Header
IEEE 802.15.4 Frame Format
IETF 6LoWPAN Format
dsp
01 010 0 0 0
“Com
pressed
IPv6”
uncompressed v6 fieldsHC1 HC1
“how
it is com
pressed”
preamble
SFD
Len
FCF
DSN
Dst16 Src16
D pan Dst EUID 64 S pan Src EUID 64
Fchk
Network Header Application Data
-Non 802.15.4 local addresses
-non-zero traffic & flow
- rare and optional
24. 24
6LoWPAN – Compressed / UDP
IEEE 802.15.4 Frame Format
UDPIETF 6LoWPAN Format IP
HC1
HC1: Source & Dest Local, next hdr=UDP
IP: Hop limit
UDP: 8-byte header (uncompressed)
dsp
Dispatch: Compressed IPv6
preamble
SFD
Len
FCF
DSN
Dst16 Src16
D pan Dst EUID 64 S pan Src EUID 64
Fchk
Network Header Application Data
25. 25
6LoWPAN – UDP/IP Optimization
• Transport length derived from link
• Subset of ports in compressed form
Link frame
ctrl src UIDlen chkdst UID
Network packet
40 B
6LoWPAN adaptation header
hops
cls flow len hops src IP dst IP appln payloadNH
8 B
UDP hdr
7 B
26. 26
IPv6 Header Compression
• http://www.visi.com/~mjb/Drawings/IP_Header_v6.pdf
v6 zero
derive from 802.15.4 header
derive from 802.15.4 header
In 802.15.4 header
in HC byte
uncompressed
27. 27
6LoWPAN – Compressed /
Compressed UDP
IEEE 802.15.4 Frame Format
IETF 6LoWPAN Format
HC1
HC1: Source & Dest Local, next hdr=UDP
IP: Hop limit
UDP: HC2+3-byte header (compressed)
source port = P + 4 bits, p = 61616 (0xF0B0)
destination port = P + 4 bits
dsp
Dispatch: Compressed IPv6
preamble
SFD
Len
FCF
DSN
Dst16 Src16
D pan Dst EUID 64 S pan Src EUID 64
Fchk
Network Header Application Data
IP UDP
HC2
28. 28
6LoWPAN / Zigbee Comparison
IEEE 802.15.4 Frame Format
IETF 6LoWPAN Format
HC1
dsp
preamble
SFD
Len
FCF
DSN
Dst16 Src16
D pan Dst EUID 64 S pan Src EUID 64
Fchk
Network Header Application Data
Zigbee APDU Frame Format
clstr
Dep
fctrl
prof
Sep
APS
fctrl: Frame Control bit fields
D ep: Destination Endpoint (like UDP port)
clstr: cluster identifier
prof: profile identifier
S ep: Source Endpoint
APS: APS counter (sequence to prevent duplicates)
*** Typical configuration. Larger and smaller alternative forms exist.
IP UDP
HC2
29. 29
6LoWPAN – Compressed / ICMP
IEEE 802.15.4 Frame Format
ICMPIETF 6LoWPAN Format IP
HC1
HC1: Source & Dest Local, next hdr=ICMP
IP: Hops Limit
ICMP: 8-byte header
dsp
Dispatch: Compressed IPv6
preamble
SFD
Len
FCF
DSN
Dst16 Src16
D pan Dst EUID 64 S pan Src EUID 64
Fchk
Network Header Application Data
31. 31
6LoWPAN – Compressed / TCP
IEEE 802.15.4 Frame Format
Application
DataTCPIETF 6LoWPAN Format IP
HC1
HC1: Source & Dest Local, next hdr=TCP
IP: Hops Limit
TCP: 20-byte header
dsp
Dispatch: Compressed IPv6
preamble
SFD
Len
FCF
DSN
Dst16 Src16
D pan Dst EUID 64 S pan Src EUID 64
Fchk
Network Header
Max 127 bytes
32. 32
Key Points for IP over 802.15.4
• Header overhead
– Standard IPv6 header is 40 bytes [RFC 2460]
– Entire 802.15.4 MTU is 127 bytes [IEEE std]
– Often data payload is small
• Fragmentation
– Interoperability means that applications need not know the constraints of
physical links that might carry their packets
– IP packets may be large, compared to 802.15.4 max frame size
– IPv6 requires all links support 1280 byte packets [RFC 2460]
• Allow link-layer mesh routing under IP topology
– 802.15.4 subnets may utilize multiple radio hops per IP hop
– Similar to LAN switching within IP routing domain in Ethernet
• Allow IP routing over a mesh of 802.15.4 nodes
– Localized internet of overlapping subnets
• Energy calculations and 6LoWPAN impact
33. 33
6LoWPAN Fragmentation
• IP interoperability over many links => users not limited by frame
size
• IP datagrams that are too large to fit in a 802.15.4 frame are
fragmented into multiple frames
– Self describing for reassembly
Multiple Link frames
net payload
Network packet
IP header
chk15.4 header IPF1
chk15.4 header IPF2
chk15.4 header IPFn
. . .. . .
netpayload
34. 34
Fragmentation
• All fragments of an IP packet carry the same “tag”
– Assigned sequentially at source of fragmentation
• Each specifies tag, size, and position
• Do not have to arrive in order
• Time limit for entire set of fragments (60s)
First fragment
Rest of the fragments
offset
11 0
size
0 0
tag
11 1
size
0 0
tag
35. 35
6LoWPAN – Example
Fragmented / Compressed / Compressed UDP
IEEE 802.15.4 Frame Format
Application
Data
IETF 6LoWPAN Format
HC1
HC1: Source & Dest Local, next hdr=UDP
IP: Hop limit
UDP: HC2+3-byte header (compressed)
Frag 1st
Dispatch: Fragmented, First Fragment, Tag, Size
Dispatch: Compressed IPv6 dsp
preamble
SFD
Len
FCF
DSN
Dst16 Src16
D pan Dst EUID 64 S pan Src EUID 64
Fchk
Network Header
IP UDP
HC2
36. 36
Key Points for IP over 802.15.4
• Header overhead
– Standard IPv6 header is 40 bytes [RFC 2460]
– Entire 802.15.4 MTU is 127 bytes [IEEE std]
– Often data payload is small
• Fragmentation
– Interoperability means that applications need not know the constraints of
physical links that might carry their packets
– IP packets may be large, compared to 802.15.4 max frame size
– IPv6 requires all links support 1280 byte packets [RFC 2460]
• Allow link-layer mesh routing under IP topology
– 802.15.4 subnets may utilize multiple radio hops per IP hop
– Similar to LAN switching within IP routing domain in Ethernet
• Allow IP routing over a mesh of 802.15.4 nodes
– Localized internet of overlapping subnets
• Energy calculations and 6LoWPAN impact
37. 37
Multi-Hop Communication
• Short-range radios & Obstructions => Multi-hop Communication
is often required
– i.e. Routing and Forwarding
– That is what IP does!
• “Mesh-under”: multi-hop communication at the link layer
– Still needs routing to other links or other PANs
• “Route-over”: IP routing within the PAN
• 6LoWPAN supports both
PAN
38. 38
IP-Based Multi-Hop
• IP has always done “multi-hop”
– Routers connect sub-networks to one another
– The sub-networks may be the same or different physical links
• Routers utilize routing tables to determine which node represents
the “next hop” toward the destination
• Routing protocols establish and maintain proper routing tables
– Routers exchange messages with neighboring routers
– Different routing protocols are used in different situations
– RIP, OSPF, IGP, BGP, AODV, OLSR, …
• IP routing over 15.4 links does not require additional header
information at 6LoWPAN layer
• Vast body of tools to support IP routing
– Diagnosis, visibility, tracing, management
– These need to be reinvented for meshing
• IP is widely used in isolated networks too
– Broad suite of security and management tools
39. 39
Meshing vs Routing
• Conventional IP link is a full broadcast domain
– Routing connects links (i.e, networks)
• Many IP links have evolved from a broadcast domain
to a link layer “mesh” with emulated broadcast
– ethernet => switched ethernet
– 802.11 => 802.11s
• Utilize high bandwidth on powered links to maintain
the illusion of a broadcast domain
• 802.15.4 networks are limited in bandwidth and
power so the emulation is quite visible.
• Routing at two different layers may be in conflict
• On-going IETF work in ROLL working group
– Routing Over Low-Power and Lossy networks
40. 40
“Mesh Under” Header
• Originating node and Final node specified by either
short (16 bit) or EUID (64 bit) 802.15.4 address
– In addition to IP source and destination
• Hops Left (up to 14 hops, then add byte)
• Mesh protocol determines node at each mesh hop
o f hops left
LoWPAN mesh header
10
originator short address
final short address
orig. addr (16/64) final. addr (16/64)
41. 41
6LoWPAN – Example
Mesh / Compressed / Compressed UDP
IEEE 802.15.4 Frame Format
Application
DataIETF 6LoWPAN Format
HC1
HC1: Source & Dest Local, next hdr=UDP
IP: Hop limit
UDP: HC2+3-byte header
M
Dispatch: Mesh under, orig short, final short
Dispatch: Compressed IPv6
dsp
o16 f16
Mesh: orig addr, final addr
preamble
SFD
Len
FCF
DSN
Dst16 Src16
D pan Dst EUID 64 S pan Src EUID 64
Fchk
Network Header
IP UDP
HC2
42. 42
6LoWPAN – Example
Mesh / Fragmented / Compressed / UDP
IEEE 802.15.4 Frame Format
Application
Data
IETF 6LoWPAN Format
HC1
HC1: Source & Dest Local, next hdr=UDP
IP: Hop limit
UDP: HC2 + 3-byte header
M
Dispatch: Mesh under, orig short, final short
Dispatch: Compressed IPv6
dsp
o16 f16
Mesh: orig addr, final addr
Frag 1st
Dispatch: Fragmented, First Fragment, Tag, Size
preamble
SFD
Len
FCF
DSN
Dst16 Src16
D pan Dst EUID 64 S pan Src EUID 64
Fchk
Network Header
IP UDP
HC2
43. 43
Key Points for IP over 802.15.4
• Header overhead
– Standard IPv6 header is 40 bytes [RFC 2460]
– Entire 802.15.4 MTU is 127 bytes [IEEE std]
– Often data payload is small
• Fragmentation
– Interoperability means that applications need not know the constraints of
physical links that might carry their packets
– IP packets may be large, compared to 802.15.4 max frame size
– IPv6 requires all links support 1280 byte packets [RFC 2460]
• Allow link-layer mesh routing under IP topology
– 802.15.4 subnets may utilize multiple radio hops per IP hop
– Similar to LAN switching within IP routing domain in Ethernet
• Allow IP routing over a mesh of 802.15.4 nodes
– Localized internet of overlapping subnets
• Energy calculations and 6LoWPAN impact
44. 44
IP-Based Multi-Hop Routing
• IP has always done “multi-hop”
– Routers connect sub-networks to one another
– The sub-networks may be the same or different physical links
• Routers utilize routing tables to determine which
node represents the “next hop” toward the
destination
• Routing protocols establish and maintain proper
routing tables
– Routers exchange messages using more basic
communication capabilities
– Different routing protocols are used in different situations
– RIP, OSPF, IGP, BGP, AODV, OLSR, …
• IP routing over 6LoWPAN links does not require
additional header information at 6LoWPAN layer
45. 45
IPv6 Address Auto-Configuration
64-bit Prefix
64-bit Suffix or
Interface Identifier
EUID - 64
00-FF-FE-00pan* short
PAN* - complement the “Universal/Local" (U/L) bit,
which is the next-to-lowest order bit of the first octet
802.15.4
AddressLink Local
46. 46
Compression of Routable Headers
• HC1 only defined header compression for Link
Local prefix
• HC1g defined header compression for Common
Global Routing Prefix, while preserving HC1
• HC (
http://tools.ietf.org/id/draft-hui-6lowpan-hc-00.txt
) subsumes both
48. 48
IP HC (draft-hui-6lowpan-hc-00.txt)
• Adds two new dispatch type IPHC – for
compressed IPv6 Header
– 0x03 (TBD) LOWPAN_IPHC with link-local addresses
– 0x04 (TBD) LOWPAN_IPHC with Common Routable Prefix
• All forms of header compression in same format
• Cleans up Next Header
• Cleans up L4 header compression
• Enables compression of multicast addresses
49. 49
IPHC
• VTF: Version, Traffic Class, and Flow Label (bit 0):
– 0: Full 4 bits for Version, 8 bits for Traffic Class, and 20 bits for Flow Label are carried in-line.
– 1: Version, Traffic Class, and Flow Label are elided. Version is 6. Traffic Class and Flow Label are 0.
• NH: Next Hop (bit 1):
– 0: Full 8 bits for Next Hop are carried in-line.
– 1: Next Hop is elided and the next header is compressed using LOWPAN_NHC
• HLIM: Hop Limit (bit 2):
– 0: All 8 bits of Hop Limit arecarried in-line.
– 1: All 8 bits of Hop Limit are elided.
» receiving interface => 1, otw 64 (TBD).
• SRC: Source Address (bits 3 and 4):
– 00: All 128 bits of Source Address are carried in-line.
– 01: 64-bit Compressed IPv6 address.
– 10: 16-bit Compressed IPv6 address.
– 11: All 128 bits of Source Address are elided.
• DST: Destination Address (bits 5 and 6):
Dispatch
50. 50
IPv6 Unicast Address Hdr Compression
• SRC/DST may be compressed to 64, 16, or 0 bits
– 64: CP elided, IID carried in line
– 16: CP and upper bits elided, last 16 bits carried in lin
– 0: determined entirely from L2 Header
• 16-bit compressed form is also used for IPv6
multicast address compression,
• the 16-bit address space is divided into multiple
ranges.
• For unicast addresses, the first bit carried in-line
must be zero.
51. 51
Multicast Address Compression
• Range (bits 0-2):
– set to '101' (TBD) - 6LoWPAN short address range for
compressed IPv6 multicast addresses.
– 0, 0xxxxxxxxxxxxxxx: As specified in RFC 4944.
– 1, 101xxxxxxxxxxxxx: The remaining 13 bits represent a
compressed IPv6 multicast address
– 2, 100xxxxxxxxxxxxx: As specified in RFC 4944.
• Scope (bits 3-6):
– 4-bit multicast scope as specified in RFC 4007
• Mapped Group ID (bits 7-15):
– 9-bit mapped multicast group identifier.
53. 53
L4 UDP Header Compression
• D: Identifier (bit 0):
• 0: IPv6 Next Header = 17, compressed
• 1: IPv6 Next Header != 17, uncompressed
• S: Source Port (bit 1):
• 0: All 16 bits of Source Port are carried in-line.
• 1: First 12 bits of Source Port are elided and the remaining 4
bits are carried in-line. The Source Port is recovered by: P +
short_port, where P is 61616 (0xF0B0).
• D: Destination Port (bit 2):
–
• C: Checksum (bit 3):
• 0: All 16 bits of Checksum are carried in-line. The Checksum
MUST be included if there are no other end-to-end integrity
checks that are stronger than what is provided by the UDP
checksum. Such an integrity check MUST be end-to-end and
cover the IPv6 pseudo-header, UDP header, and UDP payload.
• 1: All 16 bits of Checksum are elided. The Checksum is
recovered by recomputing it.
55. IEEE 802.15.4 Mesh Addressing Fragmentation Dispatch Compressed IP Payload…
1 0 O F Hops (4) Originator Addr (16-64)
Datagram Tag (16)
1 0 O F 0xF Hops (8)
1 1 0
1 1 1 Offset (8)
Final Addr (16-64)
Datagram Size (11)
Datagram Tag (16)Datagram Size (11)
Originator Addr (16-64) Final Addr (16-64)
Dispatch (6)0 1
0x3F0 1 Dispatch (8)
0 0
0 0
IEEE 802.15.4 Fragmentation Dispatch Compressed IP Payload…
IEEE 802.15.4 Dispatch Compressed IP Payload…Mesh Addressing
IEEE 802.15.4 Dispatch Compressed IP Payload…
Single Hop, No Fragmentation
Multihop, No Fragmentation
Single Hop, Fragmentation
Multi Hop, Fragmentation
Dispatch Header (1-2 bytes)
Mesh Addressing Header (5-18 bytes)
Fragmentation Header (4-5 bytes)
56. 56
Adaptation Summary
Efficient Transmission of IPv6 Datagrams
http://tools.ietf.org/html/rfc4944http://tools.ietf.org/html/rfc4944
IPv6 BaseIPv6 BaseIPv6 BaseIPv6 Base Hop-by-HopHop-by-HopHop-by-HopHop-by-Hop RoutingRoutingRoutingRouting FragmentFragmentFragmentFragment DestinationDestinationDestinationDestination
IPv6 Stacked Header Format
IPv6 Options
PayloadPayloadPayloadPayload
15.4 Header15.4 Header15.4 Header15.4 Header IPv6 HCIPv6 HCIPv6 HCIPv6 HC PayloadPayloadPayloadPayload
15.4 Header15.4 Header15.4 Header15.4 Header PayloadPayloadPayloadPayload
15.4 Header15.4 Header15.4 Header15.4 Header IPv6 HCIPv6 HCIPv6 HCIPv6 HC NH HCNH HCNH HCNH HC PayloadPayloadPayloadPayload
15.4 Header15.4 Header15.4 Header15.4 Header FragmentationFragmentationFragmentationFragmentation IPv6 HCIPv6 HCIPv6 HCIPv6 HC NH HCNH HCNH HCNH HC PayloadPayloadPayloadPayload
DispatchDispatchDispatchDispatch HeaderHeaderHeaderHeader
6LowPAN Stacked Adaptation Header Format
57. 57
Key Points for IP over 802.15.4
• Header overhead
– Standard IPv6 header is 40 bytes [RFC 2460]
– Entire 802.15.4 MTU is 127 bytes [IEEE std]
– Often data payload is small
• Fragmentation
– Interoperability means that applications need not know the constraints of
physical links that might carry their packets
– IP packets may be large, compared to 802.15.4 max frame size
– IPv6 requires all links support 1280 byte packets [RFC 2460]
• Allow link-layer mesh routing under IP topology
– 802.15.4 subnets may utilize multiple radio hops per IP hop
– Similar to LAN switching within IP routing domain in Ethernet
• Allow IP routing over a mesh of 802.15.4 nodes
– Localized internet of overlapping subnets
• Energy calculations and 6LoWPAN impact
58. 58
Energy Efficiency
• Battery capacity typically rated in Amp-hours
– Chemistry determines voltage
– AA Alkaline: ~2,000 mAh = 7,200,000 mAs
– D Alkaline: ~15,000 mAh = 54,000,000 mAs
• Unit of effort: mAs
– multiply by voltage to get energy (joules)
• Lifetime
– 1 year = 31,536,000 secs
⇒ 228 uA average current on AA
⇒ 72,000,000 packets TX or Rcv @ 100 uAs per TX or Rcv
⇒ 2 packets per second for 1 year if no other consumption
59. 59
Energy Profile of a Transmission
• Power up oscillator
& radio (CC2420)
• Configure radio
• Clear Channel
Assessment,
Encrypt and Load
TX buffer
• Transmit packet
• Switch to rcv mode,
listen, receive ACK
10mA
20mA
5 ms 10 ms
Datasheet
Analysis
61. 61
Rest of the Energy Story
• Energy cost of communication has four parts
– Transmission
– Receiving
– Listening (staying ready to receive)
– Overhearing (packets destined for others)
• The increase in header size to support IP over 802.15.4 results in a
small increase in transmit and receive costs
– Both infrequent in long term monitoring
• The dominant cost is listening! – regardless of format.
– Can only receive if transmission happens when radio is on, “listening”
– Critical factor is not collisions or contention, but when and how to listen
– Preamble sampling, low-power listening and related listen “all the time” in short
gulps and pay extra on transmission
– TDMA, FPS, TSMP and related communication scheduling listen only now and
then in long gulps. Transmission must wait for listen slot. Clocks must be
synchronized. Increase delay to reduce energy consumption.
62. 62
Conclusion
• 6LoWPAN turns IEEE 802.15.4 into the next IP-enabled link
• Provides open-systems based interoperability among low-power
devices over IEEE 802.15.4
• Provides interoperability between low-power devices and existing
IP devices, using standard routing techniques
• Paves the way for further standardization of communication
functions among low-power IEEE 802.15.4 devices
• Offers watershed leverage of a huge body of IP-based operations,
management and communication services and tools
• Great ability to work within the resource constraints of low-power,
low-memory, low-bandwidth devices like WSN
64. 64
How does 6LoWPAN compare to
Zigbee, SP100.11a, …?
• Zigbee
– only defines communication between 15.4 nodes (“layer 2” in IP terms), not the rest of the
network (other links, other nodes).
– defines new upper layers, all the way to the application, similar to IRDA, USB, and
Bluetooth, rather utilizing existing standards.
– Specification still in progress (Zigbee 2006 incompatible with Zigbee 1.0. Zigbee 2007 in
progress.) Lacks a transport layer.
• SP100.11a
– seeks to address a variety of links, including 15.4, 802.11, WiMax, and future “narrow
band frequency hoppers”.
– Specification is still in the early stages, but it would seem to need to redefine much of
what is already defined with IP.
– Much of the emphasis is on the low-level media arbitration using TDMA techniques (like
token ring) rather than CSMA (like ethernet and wifi). This issue is orthogonal to the
frame format.
• 6LoWPAN defines how established IP networking layers utilize the 15.4
link.
– it enables 15.4 15.4 and 15.4 non-15.4 communication
– It enables the use of a broad body of existing standards as well as higher level protocols,
software, and tools.
– It is a focused extension to the suite of IP technologies that enables the use of a new
class of devices in a familiar manner.
65. 65
Do I need IP for my stand-alone
network?
• Today, essentially all computing devices use IP
network stacks to communicate with other devices,
whether they form an isolated stand-alone network, a
privately accessible portion of a larger enterprise, or
publicly accessible hosts.
– When all the devices form a subnet, no routing is required, but
everything works in just the same way.
• The software, the tools, and the standards utilize IP
and the layers above it, not the particular physical link
underneath.
• The value of making it “all the same” far outweighs the
moderate overheads.
• 6LoWPAN eliminates the overhead where it matters
most.
66. 66
Will the “ease of access” with IP mean
less security?
• No.
• The most highly sensitive networks use IP
internally, but are completely disconnected from
all other computers.
• IP networks in all sorts of highly valued settings
are protected by establishing very narrow,
carefully managed points of interconnection.
– Firewalls, DMZs, access control lists, …
• Non-IP nodes behind a gateway that is on a
network are no more secure than the gateway
device. And those devices are typically
numerous, and use less than state-of-the-art
security technology.
• 802.15.4 provides built-in AES128 encryption
which is enabled beneath IP, much like WPA on
802.11.
67. 67
Does using 6LoWPAN mean giving up
deterministic timing behavior?
• No.
• Use of the 6LoWPAN format for carrying traffic
over 802.15.4 links is orthogonal to whether
those links are scheduled deterministically.
– Deterministic media access control (MAC) can be
implemented as easily with 6LoWPAN as with any other
format.
• There is a long history of such TDMA
mechanisms with IP, including Token Ring and
FDDI.
– MAC protocols, such as FPS and TSMP, extend this to a
mesh.
– Ultimately, determinacy requires load limits and sufficient
headroom to cover potential losses.
– Devices using different MACs on the same link (TDMA vs
CSMA) may not be able to communicate, even though the
packet formats are the same.
68. 68
Is 6LoWPAN less energy efficient than
proprietary protocols?
• No.
• Other protocols carry similar header information for
addressing and routing, but in a more ad hoc fashion.
• While IP requires that the general case must work, it
permits extensive optimization for specific cases.
• 6LoWPAN optimizes within the low-power 802.15.4
subnet
– More costly only when you go beyond that link.
– Other protocols must provide analogous information (at application
level) to instruct gateways.
• Ultimately, the performance is determined by the
quality the implementation.
– With IP’s open standards, companies must compete on performance
and efficiency, rather than proprietary “lock in”
69. 69
Do I need to run IPv6 instead of IPv4 on the
rest of my network to use 6LoWPAN?
• No.
• IPv6 and IPv4 work together throughout the world
using 4-6 translation.
• IPv6 is designed to support “billions” of non-
traditional networked devices and is a cleaner
design.
– Actually easier to support on small devices, despite the larger
addresses.
• The embedded 802.15.4 devices can speak IPv6 with
the routers to the rest of the network providing 4-6
translation.
– Such translation is already standardized and widely available.
Editor's Notes
Thank you
Tag team: software / tinyos part, Kris hardware/smart dust part
Hopefully let you play with the toys so you don’t get too anxious before lunch