ABSTRACT

CoAP is being standardized as an application layer protocol for the IoT. CoAP proposes to use DTLS to provide end-to-end security to protect the IoT. DTLS is a heavyweight protocol and its headers are too long to fit in a single IEEE 802.15.4 MTU(The Maximum Transmission Unit(MTU) for 802.15.4 is 127 bytes)

.

 

-> 6LoWPAN provides header compression mechanisms to reduce the size of upper layer headers.

-> 6LoWPAN header compression mechanisms can be used to compress the security headers as well.

 

We propose 6LoWPAN header compression for DTLS. We link our compressed DTLS with the 6LoWPAN standard using standardized mechanisms. We show that our proposed DTLS compression significantly reduces the number of additional security bits.

 

6LoWPAN = IPv6 over Low-power Wireless Personal Area Network

-> Enables the use of IP in IEEE 802.15.4 low power and loosy wireless networks such as wireless sensor network (WSN)

 

Security is particularly important for the things as they are connected to the untrusted and unreliable Internet.

 

UDP is mostly used and a new connection-less lightweight Constrained Application Protocol (CoAP) is proposed

-> CoAP proposes to use Datagram Transport Layer Security(DTLS) as a security protocol for automatic key management and data encryption and authentication.

->CoAP with DTLS support is termed as secure-CoAP (CoAPs)


 

System model

IoT setup having 6LoWPAN that consists of CoAPs enabled nodes and a border router; messages within 6LoWPAN travel in compressed form. The 6LoWPAN border router acts as a bridge between 6LoWPAN and the conventional Internet.

CoAPs enabled devices can securely communicate with Internet hosts such as laptops, smartphones, etc that support DTLS.

 

* DTLS was designed for the Internet and not for resource constrained IoT devices

  -> We can exploit 6LoWPAN compression capabilities to compress the DTLS headers and messages

 

DTLS and 6LoWPAN

DTLS is a protocol used to secure datagram traffic for client/server applications.

 -> It is composed of a Record Protocol that carries other protocols such as Handshake, Alert, and application data.

 -> The initial Handshake authenticates the server and optionally the client using a Public Key Infrastructure.

6LoWPAN standard defines IP header Compression(IPHC) for the IP header and next header Compression(NHC) for the IP extension headers and the UDP header.

 -> also defines fragmentation schemes for the packets that do not fit in 127 bytes MTU

 -> apply 6LoWPAN header compression mechanisms in DTLS that contained heavyweight protocol

 

Integrating compressed DTLS into 6LoWPAN

6LoWPAN standard does not provide ways to compress the UDP payload and the layers above

 -> Recently, 6LoWPAN-GHC has been proposed as a plug-in for 6LoWPAN which can be used to compress the UDP payload

 -> DTLS is being part of the UDP payload can be compressed via 6LoWPAN-GHC

 

The proposed ID bits in the NHC for UDP-GHC are used to differentiate NHC for UDP from NHC for UDP-GHC.

 -> The ID bit 11010 in the NHC for UDP-GHC indicates that the UDP payload is compressed with 6LoWPAN-GHC

 -> UDP-GHC is defined >> we can compress DTLS by providing GHC for the DTLS messages.

 -> When the 6LoWPAN-GHC for DTLS is completed we use the STOP code, set to 10010000 in the 6LoWPAN-GHC draft, to indicate that the DTLS header compression is completed

 

6LoWPAN-GHC for the DTLS Record and handshake

Proposal of 6LoWPAN-GHC for compressing the Record and handshake header indicated in two cases in this thesis.

First, Compressing both the Record header and the Handshake header using a single encoding byte

 ->6LoWPAN-GHC for Record + Handshake byte defines an encoding for both the Record header and the Handshake header.

Second, in order to complete the Handshake protocol, we define 6LoWPAN-GHC for the Record header (6LoWPAN-GHC-R)

 -> the fragment field in the Record header is an application data rather than a Handshake header as in the first case.

 

 


 

  1. The first four bits in the 6LoWPAN-GHC-RHS represent the ID field.
    1. set these bits to 1000.
  2. Being needed to comply with 6LoWPAN-GHC encodings
    1. Set these bits to 1001
  3. Version
    1. If 0 - the version will be DTLS latest version and field is elided(생략)
    2. If 1 - the version field is carried inline(즉시처리)
  4. Epoch
    1. If 0 - an 8 bit epoch is used and the left most 8 bits are elided
    2. If 1 - all 16 bits of the epoch are carried inline
  5. Sequence Number
    1. If 0 - a 16 bit sequence number is used and the left most 32 bits are elided.
    2. If 1 - all 48 bits of the sequence number are carried inline
    3. The case of 6LoWPAN-GHC-R
      1. If 00 - 1 16 bit sequence number is used and the left most 32 bits are elided
      2. If 01 - a 32 bit sequence number is used and the left most 16 bits are elided
      3. If 11 - all 48 bits of the sequence number are carried inline
      4. If 10 - sequence number is reserved and are not used
  6. Fragment
    1. If 0 - the handshake message is not fragmented and the fields fragment_offset and fragment_length are elided
      1. This is common case when the handshake message is not bigger than maximum record size
    2. If 1 - the fields fragment_offset and fragment_length are carried inline.

 

In the Record header, content_type field is always carried inline; also, msg_type and message_seq fields in the Handshake header are always carried inline.

The length filed in the Record and Handshake headers are always elided as they can be inferred from the lower layer: either from the 6LoWPAN fragmentation header or the IEEE 802.15.4 header

 

6LoWPAN-GHC for ClientHello

The proposal of 6LoWPAN for the ClientHello message (6LoWPAN-GHC-CH) is that ClientHello message is sent twice during the handshake process -- with cookie and without cookie

 


 

  1. The first four bits in the 6LoWPAN-GHC-CH represent the ID field.
    1. set these bits to 1010.
  2. Session ID
    1. If 0 - the seesion_id is not available and this field and 8 bits of prefixed length field are elided
      1. The actual session_id field in the ClientHello contains 0 to 255 bits;
      2. It is always prefixed with an 8 bit field that contains the size of the session_id
      3. The ClientHello message uses seesion_id only if the DTLS client wants to resume the old seesion.
    2. If 1 - the session_id filed is carried inline.
  3. Cookie
    1. If 0 - The cookie field is not available and this field and its prefixed 8 bits length field are elided.
      1. The actual cookie field in the ClientHello contains 0 to 255 bits;
      2. It always has an 8 bit length field that contains the size of the cookie.
    2. If 1 - the cookie field is carried inline.
  4. Cipher Suits
    1. If 0 - the default cipher-suites for the CoAP that supports automatic key management is used and this field and the prefixed 16 bits length field are elided
      1. 16 bits and is always prefixed with a 16 bit field that contains the size of the cipher_suites
    2. If 1 - the cipher_suites field is carried inline.
  5. Compression Method
    1. If 0 - the default compression method -> COMPRESSION_NULL is used and this field and the prefixed 8 bit length field are elided.
      1. The actual compression_methods field contains 8 to 2^8 - 8 bits;
      2. It is always prefixed with an 8 bits field that contains the size of the compression_methods
    2. If 1 - the compression_methods field is carried inline.

 

The random field in the ClientHello is always carried inline whereas the version field is always elided. In the normal case, when using 6LoWPAM-GHC-CH, we only send random field in the ClientHello message and all other field are elided.

 

6LoWPAN-GHC for ServerHello

The proposal of 6LoWPAN for the ServerHello message(6LoWPAN-GHC-SH)

 


 

  1. The first four bits in the 6LoWPAN-GHC-SH represent the ID field.
    1. set these bits to 1011.
  2. Server Version
    1. If 0 - the version will be DTLS 1.0 and the field is elided.
      1. The DTLS 1.2 standard suggests that the server implementation should use DTLS version 1.0 due to avoiding negotiation in the initial handshake
      2. The DTLS clients must not assume that the server does not support higher versions
    2. If 1 - the version field is carried inline.
  3. Session ID
    1. If 0 - the session_id is not available and this field and 8 bits of the prefixed length field are elided
    2. If 1- the session_id field is carried inline
  4. Cipher Suits
    1. If 0 - the default cipher_suites for CoAP that supports automatic key management is used and this field is elided.
    2. If 1 - the cipher_suites field is carried inline.
  5. Compression Method
    1. If 0 - the default compression method -> COMPRESSION_NULL is used and this field is elided
    2. If 1 - the compression_methods field is carried inline.

 

Size Reduction Using 6LoWPAN-GHC

Using 6LoWPAN-GHC compression mechanisms we can significantly reduce DTLS headers sizes.

 


 

In this poster abstract we only provide 6LoWPAN-GHC for the Record, Handshake, ClientHello, and ServerHello.

Table I shows

 -> The number of additional bits we send during DTLS message exchanges with and without 6LoWPAN-GHC compression.

 -> Using DTLS compression we can save a significant number of bit. The Record header that is included in all messages when the DTLS is enabled can be compressed by 64 bits (62% of the Record header) for each message.

 

Conclusions and Future Work

CoAP enabled hosts will be an integral part of the Internet of Things. DTLS is a standard protocol to secure CoAP messages. DTLS can be compressed using 6LoWPAN standardized mechanisms.


더 많은 이야기는 다음 URL에서 참고하세요!

http://hunift.blogspot.kr/2017/04/research-paper-review-6lowpan.html

Problem

This paper is focused on the Internet of Things (IoT), which has rapidly grown in IT market, and give clear information to readers what is IoT. The new era of IoT has come. Beyond the age of IoT, i.e. transferring data between object to object, object to person, and person to person, IoT now connects every devices that are anythings. Once object such as embedded device is connected, the connection itself directly impacts human behaviors. As a result, creating a connected market rooted in industrial manufacturing and supplying a business model based on the IoT service are now the main success factor of the internet/mobile/social media business. This paper addresses different visions of the IoT paradigm, enabling technologies, and potentialities offering such as Healthcare, Smart environment, etc, by the IoT

 

Solution

It is not easy to understand what the IoT really means. This paper described IoT with three terms such as Internet oriented, Things oriented, and Semantic oriented, to understand what IoT means. According to the Auto-ID Labs[4], "Things oriented" perspective considers very simple things such as Radio-Frequency Identification (RFID) tags. It stands at the hot technologies driving the vision of IoT, but has to be low cost, strong support from the business community. Because of RFID, ITU vision of the IoT is "from anytime, anyplace connectivity for anyone, we will now have connectivity for anything". "Internet oriented" perspective considers very lightweight-based internet such as 6LoWPAN. IoT protocol has to be fit to any devices for communication, but it is designed to route "IP over anything". "Semantic oriented" perspective considers how to represent, store, interconnect, search, and organize information generated by the IoT. This paper addresses that the IoT semantically means "a world-wide network of interconnected objects uniquely addressable, based on standard communication protocols"
 

Because of the IoT perspective, "Anytime, anywhere, anymedia", enabling Technologies for IoT have requirements: Identification, sensing and communication technologies, middleware.

For Identification, sensing and communication technologies, RFID tags is hot technology for the IoT. It is the wireless use to transfer data for identifying and tracking tags attached to things. It has been developed with dimensions 0.4mm x 0.4mm x 0.15 mm which is small enough for any IoT devices. RFID tags usually are passive, but semi-passive and active. The strength of the passive tags is that the passive RFID tags do not have power supplies and has simple design. Semi-passive tags operates similarly to the passive tag; however, it uses the reader signal and the power supplies when cause a response from the tag. The active tags contain a battery and do not depend on the reader signal to generate a response. Sensor networks will also play a crucial role in the IoT. Wireless Sensor Network (WSN) consists of sensing nodes communicating in a wireless area such as environmental monitoring, E-health, intelligent transportation systems, military, and industrial plant monitoring and Its design proposed, for the high radio coverage, that are energy efficiency, scalability, reliability, and robustness. The Middleware, which is software layer, follows the Service Oriented Architecture (SOA) approach. The SOA consists of an ecosystem of simpler and well-defined components. This paper addresses three functions of the SOA; Service composition, Service management, and Object abstraction. The SOA approach is recognized in most studies on middleware solution for IoT.

 

The IoT concept has broadly spread to the world with many potentialities offered in many domains such as transportation and logistics, Healthcare, Smart environment, and Personal and social. For transportation and logistics domain, the paper introduces this domain, which contained advanced cars, trains, and buses with sensors, actuators, and processing power, into five different fields: Logistics, Assisted driving, Mobile ticketing, Environment monitoring, and Augmented maps. For Healthcare domain, there are many benefits provided by the IoT technologies and this applications can be used into Tracking, Identifcation, Authentication, and Sensing fields...etc

 

There are many issues including Standardization Activity that several contributions to the Standardization of the IoT paradigm. For The IoT standardization, many groups such as ITU challenges and organized in conjunction with several related meetings of the IoT standard groups and alliances. Another issue is that IoT will include an world-wide connected with high number of nodes. One of solutions for an incredible network is 6LoWPAN which is lightweight protocol for IPv6 that its addresses are expressed by means of 128 bits and defined 10^38 addresses, which means infinite addresses. Finally, IoT must solve security and privacy issue. Because of IoT devices that are characterized by low capabilities in terms of energy and computing resources such as hash operation, they can't implement complex operations.

 

In this paper, they have surveyed the most important issues in the IoT and provided to researcher and IoT-related people for further research.

 

Critique

After read this paper, I consider distribution and many industries to be the most suitable business types to utilize IoT service. Because, it is the service to supply interconnection of goods, media, service, benefit, and analysis under the subject of “Business platform service to create ecosystem to generate, supply, and consume goods and services” While offline customers have moved to mobile and internet based market through the spread of internet and mobile, mobile’s mobility and beacon analysis based real time benefit will expand local firsthand commerce and offer local based real time offer utilizing customers paths of traffic data, domestic and foreign tourism and marketing business will be expanded. Marketing business for specific customers based on location, time, age, favor, and intention, not DB based random multitude customers will grow. In addition, the service with IoT will provide information and service in demand for customers. Furthermore, by providing real time information exchange between customers mediating same beacons, the service aids customers  to offer and make optimal means and decisions.

 

It is also important to have a partnership with leading IoT vision and technology. To secure a global IoT leadership, Global companies such as Cisco, providing computing platform, and the platform enables to provide precise information to customers by analyzing specialized data based on regional or customers characteristics filtering data collected through computing. I believe that through global network, I can inform successful case of IoT in use and to acquire suitable partnership with foreign adaptability.

Second, I consider device integrated chip-design technology to be necessary to spread IoT service across the global community. As part of the effort to expand service, I might able to design service specialized device and to utilize production specialized, extreme environment, such as high temperature/high moisture/low temperature, adaptable, eco-friendly solar charge as a part of effort to save energy, and wifi-connected devices.


더 많은 자료는 다음 URL로 오세요!

http://hunift.blogspot.kr/2017/05/reseach-paper-review-internet-of-things.html



Fluorescent sorting could light up recycling rates

재활용률을 높여줄 형광 물질을 이용한 분류



Most of us dutifully separate our plastic packaging from the rest of our rubbish. But less than 30 percent of the UK's plastic ends up being recycled.

번역: 우리들 대부분은 플라스틱 포장지를 쓰레기에서 분리합니다. 그러나 영국의 플라스틱 중 30 퍼센트도 되지 않는 양이 재활용되고 있습니다.


"Current recycling technologies look at the NIR (near infrared) signature of plastics and so we can sort plastics by polymer type. But one of the limitations is that we can't identify what the products have been used for in the past. So we can't tell the difference between a bleach bottle and a milk bottle."

번역: "현재 재활용기술은 플라스틱의 NIR (근적외선) 특징을 보이기 때문에 플라스틱을 고분자 유형에 따라 분류할 수 있습니다. 그러나 그 한계들 중 하나는 플라스틱 제품들이 과거에 어떤 목적으로 사용되었는지를 확인할 수 없다는 것입니다. 그래서 표백제 병과 우유 병의 차이를 구별할 수 없습니다."


Researchers at Brunel University London and industry partners Nextek say their new fluorescent light technique can change this.

번역: 브루넬 유니버시티 런던과 업계 동업자인 넥스텍의 연구자들은 그들의 새로운 형광 기술이 이것을 바꿀 수 있다고 말합니다.


"This technology that we've been working on will be able to tell us whether something was previously food grade, so we can then recycle it back into food grade applications. And the big implication here is that we can close the circle on packaging for the first time."

번역: "우리가 작업해 온 이 기술은 무엇이 이전에 식품용이었는지를 알려줄 수 있을 것이며, 그것을 다시 식품용 적용방식으로 재활용할 수 있습니다. 그리고 큰 의미를 갖는 것은 처음으로 포장에 대한 사이클을 끝맺을 수 있다는 것입니다."



The system works by adding phosphors, the luminescent materials that give strip lights their glow, to plastic labels or packaging. "When the plastic bottles are sent to the recycling plant, if they have our labels on, then they'll go up the conveyor belt in the normal way. There's a system for reading the bottles currently with our labels on - that system can be changed quite easily to then recognize a bottle we want to sort, either positive or negative. And then the conveyor belt system puts a jet of air that separates the bottle into another bin." The system can be retrofitted to existing high-speed sorting systems. So it's cheap - and should make plastic recycling more financially attractive to businesses. "It doesn't have to be confined to plastics. It could be any kind of recycling that might be interesting - in the automotive industry, in the electronics industry, in fact in the building industry." In initial full-scale tests the system sorted up to 98 percent of labeled plastics with 100 percent accuracy.


나머지 번역은 아래 주소로 가시면 있어요!

http://hunift.blogspot.kr/2017/05/reuters-fluorescent-sorting-could-light.html


+ Recent posts