CoAP Whitepaper

download CoAP Whitepaper

of 17

Transcript of CoAP Whitepaper

  • 7/31/2019 CoAP Whitepaper

    1/17

  • 7/31/2019 CoAP Whitepaper

    2/17

    CoAP White Paper

    PROBE-IT Page 2/16

    Table of Content

    1. INTRODUCTION 41.1.

    Internet of Things Vision .................................................................................. 4

    1.2. Need for interoperability testing event in IoT ......................................................... 4 1.3. What is CoAp? ............................................................................................... 51.4. Objective of 1st CoAp plugtest ............................................................................ 52. TEST PROGRAMS 62.1. What do you test? ........................................................................................... 62.2. Test specification process ................................................................................. 62.3. Test bed architecture ...................................................................................... 82.4. Test suite structure ........................................................................................ 92.5. Test tools used ............................................................................................. 113. TEST TOOL SUPPORTERS 123.1. IRISA ......................................................................................................... 123.2. BUPT ......................................................................................................... 134. TEST CAMPAIGN 135. EVENT ORGANIZERS 145.1. PROBE-IT .................................................................................................... 155.2. ETSI .......................................................................................................... 155.3. IPSO ALLIANCE .............................................................................................. 156. CONCLUSION 16

  • 7/31/2019 CoAP Whitepaper

    3/17

    CoAP White Paper

    PROBE-IT Page 3/16

    Executive summaryThis interoperability event, organised in joint co-operation between the Probe-IT project, the IPSO

    Alliance and ETSI (European Telecommunication Standards Institute) was held in Paris, France 24-25th

    March and co-located with IETF#83.

    CoAP is a lightweight application-protocol for devices that are constrained in their resources such as

    computing power, RF range, memory, bandwidth, or network packet sizes. CoAP is an integral part of the

    ETSI M2M architecture, where global interoperability is a key issue. This landmark event allowed vendors

    to evaluate the interoperability of their products and to validate their understanding of the base

    specifications. It also provided useful feedback to enhance the ongoing ETSI and IETF standardisation.

    The features tested included the base CoAP specification, CoAP Block Transfer, CoAP Observation and the

    the CoRE Link Format. The interoperability test cases were jointly developed by IRISA/Universit de

    Rennes 1 (France), BUPT (China) on behalf of the Probe-IT project, IPSO Alliance and ETSI.

    This event was attended by 18 companies testing the worlds first CoAP client and server implementations

    from China, EU, Japan and Korea Tools used to execute test cases, to analyse test results and logs

    provided by IRISA/Universit de Rennes 1 and BUPT on behalf of the Probe-IT project were considered

    very useful for all participants.

    In the end, this event turned to be a successful first CoAp plugtest event by demonstrating need for

    Interoperability testing in IoT and need for such event in future which was proven by the number of

    companies participated for this event.

  • 7/31/2019 CoAP Whitepaper

    4/17

    CoAP White Paper

    PROBE-IT Page 4/16

    1.Introduction1.1. Internet of Things Vision

    The challenges for Internet of Things

    "The Internet of Things has the potential to change the world, just as the Internet did. Maybe even

    more so." - Kevin Ashton, the inventor of the term Internet of Things ,2009

    Internet of Things (IoT) is a vision towards Future Internet where things have enough intelligent to

    communicate with other things without intervention of human based on interoperable communication

    protocols. In near future, these things are expected to be active part in business, information technology,

    environmental studies, automotive etc. As the number of things interacting using IoT is expected to grow

    substantially, the heterogeneous nature of implementations demands the need for interoperability

    testing. The effective testing of IoT ensures proper deployment, interoperability and reliability of the IoT

    network infrastructure which will be a key factor for vendors to successfully launch their product in the

    market.

    1.2. Need for interoperability testing event in IoT

    The objective of interoperability testing is that independent implementations of the same standard

    interoperate. It is a well-known fact that, even following the same standard, two different

    implementations might not be interoperable. The heterogonous nature of IoT technologies requires

    interoperability issues to be solved before the deployment of the product. Having a simple view on

    interoperability for different technologies may not be possible at this point of time. Since it is a complex

    topic and needs more research activities to face the challenges raised. To efficiently address this

    problem, it is necessary to see the interoperability addressing all components within the complete

    development chain (standards, products, tests, tests tool, etc) with different tools.

    Interoperability testing events are important and pragmatic tools to validate standards improveimplementation and finally improve interoperability.

    Figure 1: Need for interoperability testing

    Component #BComponent #A

    Standard/Specification

    Design/developement # A Design/Development #B

    Interoperability

    issues

    VendorVendor

    Human Error (Programming,

    interpretation of standards)

    Errors & ambiguities

  • 7/31/2019 CoAP Whitepaper

    5/17

    CoAP White Paper

    PROBE-IT Page 5/16

    1.3. What is CoAp?

    Constrained Application Protocol (CoAp) is a specialized web transfer protocol which is

    designed by CORE working group of IETF keeping in mind the various issues of

    constrained environment to realize interoperations with constrained networks andnodes for machine to machine (M2M) applications like smart energy, building

    automation, smart home etc.CoAP is one IoT (young) protocol of the Internet of Thingsas identified important by

    PROBE-IT and where useful activities such as interoperability can help to validate, to

    mature the specifications while helping on validating its implantation in

    interoperable products

    There are many important features defined by CORE working group for resource constrained devices like

    Constrained application protocol, web linking for constrained web servers, implementation of datagram

    transport layer security, communication between sleepy node and intermediate proxy node, groupcommunication (multi-cast in resource constrained networks) etc.

    For this CoAP plugtest interoperability event, four main features were selected from CORE:

    CoAP: CoAP can be seen as a complementary to HTTP which has a client/serverinteraction model similar to HTTP. Unlike HTTP, CoAP targets for resource constrainedand lossy networks such as Wireless sensor networks. In the protocol stack CoAp lies overunreliable UDP layer. CoAP defines four types of messages: Confirmable, Non-Confirmable, Acknowledgement, Reset. Like HTTP, method codes and response codesincluded in some of these messages make them carry requests or responses. Ref:http://tools.ietf.org/html/draft-ietf-core-coap-09

    CoRE Link format: In this specification Web Linking is extended with specific constrainedM2M attributes, links are carried as a message payload rather than in an HTTP LinkHeader, and a default interface is defined to discover resources hosted by a server.This specification also defines a new relation type "hosts", which indicates that theresource is hosted by the server from which the link document was requested. Ref:http://tools.ietf.org/html/draft-ietf-core-link-format-11

    Observing Resources in CoAP: The protocol specified in this document extends the CoAPcore protocol with a mechanism to push resource representations from servers tointerested clients, while still keeping the properties of REST. Ref:http://tools.ietf.org/html/draft-ietf-core-observe-05

    Block wise Transfers in CoAP: This feature is a complementary to CoAp base specification

    which defines a pair of CoAP options to enable block-wise access to resourcerepresentations. The Block options provide a means to transfer large resource from aserver to client by fragmenting into smaller blocks. Ref: http://tools.ietf.org/html/draft-ietf-core-block-08

    1.4. Objective of 1st CoAp plugtest

    Plugtest is the place where vendors have opportunity to identify potential issues related to their

    product/implementation effectively. It also provides a means to improve the features of a technology

    standard for technology consortium and standardisation bodies.This CoAP plugtest was a two days long event carried out during IETF#83 meeting in Paris to motivate

    vendors to verify the interoperability of their equipment with others. Equipment is considered

    Figure 2:

    Protocol stack

    of CoAP

    CoAp

    UDP

    6LowPan

  • 7/31/2019 CoAP Whitepaper

    6/17

    CoAP White Paper

    PROBE-IT Page 6/16

    interoperable once they have successfully showed that their implementation is able to communicate with

    implementation of other vendors without any issues. Before the testing session, participants must agree

    on a set of configurations to test their equipment/implementations. In all tests, at least two different

    vendor products must be available to conduct a suite of selected interoperability testing scenarios.

    The main objectives of this event are

    First opportunity to test their CoAP implementations/equipment in one place with testsuites provided by worlds best test labs

    Verify the interoperability of your product with other major actors in the market

    Identify the issues and improve your CoAP implementation effectively with test suitesprovided by worlds best test labs (ETSI and IRISA)

    Share experience and improve interoperability of your product2.Test programs

    2.1. What do you test?The idea of conducting first IoT CoAP plugtest is proposed by ETSI and PROBE-IT consortium to get-

    together industry people to share their experiences, test their equipment in order to make their

    product successful in multi-vendor environment by achieving interoperability. The technical aspects of

    this program are managed mainly by Probe-IT consortium (IRISA and BUPT), ETSI and IPSO alliance. This

    test program contains four different groups which covers the following features of CoAp:

    CORE (Constrained Application Protocol (CoAP)): This group of test contains 15 testswhich covers the basic transaction of the CoAp request/response model with or withoutoptions. All four message types and method codes were covered.

    LINK (CoRE Link Format): This group contains 2 tests which cover the basic functionality

    of web link format for constrained nodes.

    OBS (Observing Resources in CoAP): It contains 5 tests to check the main functionalitiesof CoRE observe specification.

    BLOCK (Blockwise transfers in CoAP): This group contains 4 tests which checks the mainmethods of CoAp to block-wise transfer of large resource.

    A total of 26 tests were defined, in that CORE group which contains 15 tests which were considered as

    mandatory tests and other groups which contains 11 tests [LINK (2 tests), OBS (4 tests), BLOCK (5 tests)]

    were taken as optional. These tests cover maximum functionalities of CoAp features which are selected

    for the plugtest.

    Here in this test program, instead of injecting stimuli actively in the network for testing which disturbs

    the normal operation of System Under Test (SUT), a method of observing the network transactions andpost-analysing it for interoperability issues was chosen. This technique is called Passive interoperability

    testing

    The following part of this document introduces test specification process steps, test event methodology,

    test architecture, test suite structure.

    2.2. Test specification process

    Test methodology and Test event organisation

    In order to derive the test cases which have maximum coverage of CoAp features, the methodology shown

    in the figure 3 was adopted. ETSI, IRISA and BUPT were involved in defining the objective and it wasreviewed with help of Zach Shelby from IPSO alliance. Once test purposes were defined, the test scenarios

  • 7/31/2019 CoAP Whitepaper

    7/17

    CoAP White Paper

    PROBE-IT Page 7/16

    were described and reviewed with IPSO alliance. Finally test specification draft was made available for

    eventual comments from all participants of this event.

    Figure 3: Test development cycle methodology

    Figure 4: Test event methodology

    The procedures followed during the testing event were demonstrated using the figure 4. Every session inthe event includes test arrangement and plan of tests to be conducted. During test arrangements, the test

    Definition oftest

    objective

    Validation oftest

    objective

    Descriptionsof test

    scenerios

    Validation oftest

    scenerios

    Test tooldevelopment

    CoAp

    s ecifications

    Review

    Testpurposes

    Review

    Test

    descri tions

    Tools

    Arrangements

    for tests

    Test sessions

    Packet

    analyse and

    Verdict

    logging Test

    specifications

    Captured

    packet

    Test report

    ONLINE

  • 7/31/2019 CoAP Whitepaper

    8/17

    CoAP White Paper

    PROBE-IT Page 8/16

    architecture setup and initial configurations are made to start the tests. During the execution of each test

    suite, packets exchanged are captured using wireshark and pcap files were produced. In the end of test

    sessions, participants need to submit the pcap files in the web interface provided by IRISA to know the

    test reports/logs/verdicts.

    2.3. Test bed architectureTwo test configurations are defined and adopted in the IoT CoAp plugtest. Here, a System Under Test

    (SUT) is a network consisting of a server and a client with or without a gateway. Two test

    configurations/architectures were defined. The 1st configuration includes a client and server with packet

    sniffer and test operator represents an ideal situation whereas the second configuration represents a real

    scenario by simulating a lossy environment (replicates lossy environment of the constrained nodes in the

    network) by adding a gateway in-between client and server.

    SUT1: A client and a server with packet sniffer and test operator

    SUT2: A client and a server including lossy gateway with packet sniffer and test operator

    Devices in each SUT were connected with wired means.

    2.3.1. SUT1: Basic face to face configurationFigure 5 below shows the test configuration in which, a

    client is connected to a server by means of wire. Client and

    server might from the same vendor or different. Generally,

    the initial configuration comes under test arrangement

    before engaging in interoperability testing session. Test

    operator provides preamble for the test suite before its

    execution. Since, it is a passive testing activity; the packet

    sniffer is used to capture the exchange between client and

    server to have a test report from the tool developed by

    IRISA.

    2.3.2. SUT2: Basic face to face configuration in lossy contextFigure 4 below shows the test configuration in

    which, a client is indirectly connected to a server

    by a gateway. This gateway was used to emulate a

    lossy medium. It does not implement the CoAP

    protocol itself (in other terms it is not a CoAPproxy), but works at the transport layer. It drops

    the packet randomly between Client and the server

    which goes nearly to 80 % packet loss as demanded

    by the participants. Like the SUT1, it also adopts

    the passive interoperability technique.

    Server

    Client

    Packet Sniffer

    Figure 5: SUT configuration 1

    Test operator

    Client Server

    Packet Sniffer

    Figure 6: SUT configuration 2

  • 7/31/2019 CoAP Whitepaper

    9/17

    2.4. Test sui

    Figure 7 shows the structure of the

    testing event. Test cases were de

    interoperability among different v

    were considered as mandatory and

    to determine conformance against

    called Check and Verify. The s

    case.

    Example Test case # 1:

    There are four types of messag

    Confirmable (NON), Acknowledge

    defined in the specification: GET, P

    This example demonstrates the ex

    with SUT configuration 1. Both the

    condition as server accepts creati

    sequence starts by sending a POST

    CoRE

    Test cases

    PROBE-IT Page 9/16

    e structure

    Figure 7: Test suite structure

    test suites found in the test descriptions docu

    eloped to test different important functional

    endors equipment. A total 27 test cases wer

    11 were considered as optional tests. These sc

    a standard and interoperability against other i

    teps in the test cases can be clearly seen in th

    s found in the CoAp core specification: Co

    ent (ACK) and Reset (RST). Like HTTP, four

    UT, POST, DELETE.

    cution of POST transaction in CON mode betwe

    e devices could be from the same vendor or di

    on of new resource on /test (resource does n

    equest from client to server

    Test suites

    LINK

    Test cases

    OBS

    Test cases Te

    CoAP White Paper

    ent provided during the

    ties needed to achieve

    developed, in that 16

    enarios were developed

    plementation by steps

    following example test

    nfirmable (CON), Non-

    different methods are

    en a Client and a Server

    fferent. With a pre-test

    ot exists yet), the test

    LOCK

    t cases

  • 7/31/2019 CoAP Whitepaper

    10/17

    CoAP White Paper

    PROBE-IT Page 10/16

    Interoperability Test DescriptionIdentifier: TD_COAP_CORE_02Objective: Perform POST transaction (CON mode)Configuration: CoAP_CFG_01References: [1] 4.4.1, 4.4.3, 5.8.2

    Pre-testconditions:

    Server accepts creation of new resource on /test (resource does not exists yet)Test Sequence: Step Type Description

    1 stimulus Client is requested to send a POST request with:Type = 0(CON)Code = 2(POST)An arbitrary payload

    2 check Sent request contains Type value indicating 0 and Codevalue indicating 2

    3 verify Server displays received information

    4 check Server sends response containing:

    Code = 65(2.01 Created)The same Message ID as that of the previous request

    5 verify Client displays the received response

    Check :Type = 0 (CON)Code = 2 POST

    Check :Code = 65 (2.01created

    Client Server

    Sent POST request

    Response

    Client displays the received

    PASS/FAIL

    PASS/FAIL

    PASS/FAIL

    Figure 8: Message sequence chart

  • 7/31/2019 CoAP Whitepaper

    11/17

    2.5. Test too

    2.5.1. Packet sWireshark was used as a tool to c

    which contains the transactions fou

    2.5.2. GatewayThe Gateway emulates a lossy med

    protocol itself (in other terms it i

    features:

    It performs NAT-style UDPgateway and is transparentl

    It randomly drops packets t

    The idea of developing this tool

    where random packet loss occurs. I

    2.5.3. Post anaIRISA team with support of PROBE-I

    tool is based on the CoAP Test spe

    the test tool working methodology

    information on results. As shown in

    the vendors after the testing sessio

    submitted, a UPD/CoAP filtering w

    the conversation made between

    isolated (or grouped as CoAp conv

    executed.

    Figure

    Such Passive Validation Tool For C

    http://www.irisa.fr/tipi/wiki/doku

    Figure 10 demonstrates the structu

    visually seen from different point

    frame, each transaction, and each

    INCONCLUSIVE. The best thing ab

    conversation anytime through the

    PROBE-IT Page 11/16

    ls used

    iffer

    pture the packets exchange in the network. It

    nd in the network during the test session.

    for lossy context

    ium between the client and the server. It does

    not a CoAP proxy), but works at the transpor

    port redirections towards the server (thusy redirected towards the server)

    hat are forwarded between the client and the s

    as proposed by IRISA to verify the interopera

    t was developed by BUPT.

    lysis of pcap files

    T project provides a passive validation tool for

    cification edited for the interoperability event

    adopted and tool developed by IRISA to prov

    the figure 9, a web interface was developed t

    n to provide test log on interoperability testing.

    s made using source IP address and destination

    particular implementations under test. Whe

    rsation), then test cases found in the test de

    9: Passive Test tool working methodology

    oAP can be downloaded here:

    .php/Passive_validation_tool_for_CoAP

    re of result presentation in the end of the event

    f view. For example, It allows to see the verdi

    test case. Three types of verdicts given in the

    out this passive validation tool is that it allo

    TTP interface.

    CoAP White Paper

    produces the pcap file

    ot implement the CoAP

    t layer. It provides two

    he client contacts the

    erver

    ility in a real scenario

    he CoAP plugtests. This

    . Figure 9 demonstrates

    de testing verdicts and

    accept pcap files from

    Once the pcap file was

    IP address to filter only

    n the transactions are

    cription documents are

    . These results could be

    cts corresponds to each

    nd were PASS, FAIL and

    s validating the CoAP

  • 7/31/2019 CoAP Whitepaper

    12/17

    CoAP White Paper

    PROBE-IT Page 12/16

    The figure 11 shows the web interface where pcap files should be updated, the test results found after

    updating the pcap files of the test session and information on the results obtained. It embeds the result

    presentation methodology shown in the figure 10.

    Figure 11: Web interface of Passive test tool

    3.Test tool supporters3.1. IRISA

    IRISA is a research institute in which Inria (the French National Institute for

    Research in Computer Science and Control), CNRS (the French National Center for Scientific Research),

    The University of Rennes I and INSA (the National Institute of Applied Science, an engineering school in

    Rennes) are partners. IRISA's activities are at the heart of Information and Communication Science and

    Technology (ICST) and contribute to achieve scientific and technological breakthroughs in

    telecommunications, multimedia information processing, software engineering, medicine and particularly

    bioinformatics. IRISA participates in many technology transfer activities with major industrial partners,

    and the participation in numerous European projects. IRISA's activities are at the heart of Information and

    Test case #2

    Test case #1

    Test case #3

    IUT 1 vs IUT3

    IUT 1 vs IUT2

    IUT 1 vs IUT4 Test case #5Test case #4

    Test case #6

    Conversation2

    Conversation1 Frame#1Match :: PASS

    Mismatch :: FAIL/INCON

    Figure 10: Result presentation methodology

  • 7/31/2019 CoAP Whitepaper

    13/17

    Communication Science and Tech

    breakthroughs in telecommunicatio

    and particularly bioinformatics.

    IRISAs Dionysos team is dedicated

    performance evaluation, security,

    Interoperability Testing. The Dion

    involved in several IPv6 related pro

    the IPv6 Ready Logo program, stan

    Since 2000, our engineers bring ex

    sessions of interoperability organiz

    3.2. BUPTBeijing University o

    universities in Chin

    the field of Inform

    focus and multidis

    Science as its mainBUPT is one of the leading resear

    promote IoT technologies, BUPT se

    in Wuxi City in Dec. 2009, with the

    platform to convert advanced new

    a Chinese National funded project

    4.Test campaignA total of 16 test slots were alloc

    ETSI. A test tool to analyse the Coweeks before the event to have

    successful. Thanks to ETSI for the

    development which made the ev

    participated and components they

    C

    ACTILITY/W

    ETH Zurich

    Hitachi

    Huawei

    IntecsKoanLogic Sr

    Patavina tec

    ROSAND Tec

    Sensinode lt

    Toyota ITC U

    TZI Uni brem

    Vitaverna

    Watteco

    Uni Rostock

    RTX

    IBBT

    Consorzio Fe

    PROBE-IT Page 13/16

    nology (ICST) and contribute to achieve scie

    ns, multimedia information processing, softwar

    to Computer Networks (Internet protocols and

    raffic engineering, pricing, QoS, multicast, etc.

    ysos team has a critical activity in the depl

    grams (test generation, methodology and tools,

    ardization, participation to working-groups of

    pertise to ETSI Plugtest service and take part s

    d by Japanese project TAHI.

    f Posts and Telecommunications (BUPT) is on

    a.BUPT has distinguished itself by its excellent

    tion Technology and Telecommunications, with

    ciplinary combination of Engineering, Manag

    pursuit.ch and development centre in the field of Io

    t up a new organization, Institute of Sensing T

    registered capital of 20 million Yuan, which pr

    IoT technological achievements into productivi

    n 6lowpan tests and tool.

    ted for two days event and the network setup

    P transaction for verdict logging was made aveview from participants with a motivation of

    dynamic hosting and IRISA for pragmatic app

    nt successful. The table below shows the n

    rought for the event.

    mpany name Client Server

    tteco X

    X X

    X X

    X X

    X Xl X X

    nologies X X

    nologies X

    X X

    SA X

    en X X

    X

    X

    X X

    X X

    X X

    rrara Ricerche X X

    CoAP White Paper

    tific and technological

    e engineering, medicine

    architectures, wireless,

    ) and Conformance and

    oyment of IPv6 and is

    interoperability events,

    he IETF, training, etc.).

    ince 2001 in the annual

    of the 73 national key

    eaching and research in

    engineering as its main

    ment, Humanities and

    in China. In order to

    echnology and Industry,

    vides a common service

    ty. BUPT will soon start

    was made available by

    ilable online by IRISA 2making the test event

    roach for the test tool

    ame of the companies

  • 7/31/2019 CoAP Whitepaper

    14/17

    CoAP White Paper

    PROBE-IT Page 14/16

    5.Overall tests resultsA total of 3141 tests were executed during the test event and 94% of executed tests gave pass verdict.

    ETSI and PROBE-IT test experts say that getting 90% and above of pass verdict in a first Plugtests event for

    a new technology is a success showing that the tested components are almost near to be fully compliant

    and interoperable. There were a total number of 234 test sessions during this two days event. In eachsession 27 tests were executed and 388 tests were not executed due to time constraints and/or because

    some CoAP features (mostly from BLOCK and OBSERVE) were not yet implemented in tested components.

    Figure 12 shows the overall results obtained during the event. Figure 13 shows the result obtained for the

    CORE group of tests, in other words it is the overall results for mandatory tests. In a total of 2843 tests

    executed, 2679 (94.2%) of the tests passed. This confirms that most of tested components support

    necessary features of CoAP base specification.

    Fig 12 : Overall results for executed tests Fig 13 : Overall results for CORE group

    Figure 14 shows the overall results of optional tests that are also near 91% of pass verdict, showing that

    most of implementations successfully support optional features. Even though there is not much difference

    in the optional test results, BLOCK group (86.3% of pass verdict) seems to have a little bit more remainingimplementation issues.

    Fig 14 : Overall results for LINK, BLOCK and OBSERVE respectively

    To conclude, this first CoAP Plugtests event was a success as 93% of tests executed were pass, which

    reveals that almost all implementations from the participants are almost mature enough to be

    interoperable with each other. These results also show the need for more such events in the future to

    improve both CoAP protocol specification and corresponding implementations paving by this way the road

    for successful deployment of this technology.

  • 7/31/2019 CoAP Whitepaper

    15/17

    6.Event organizers6.1. PROBE-I

    PROBE-I

    China,research

    interope

    avoid un

    analysin

    perspect

    providers and users.

    PROBE-IT is addressing three differ

    benchmarkingidentifying the

    Guidelines for s testing roadm

    technologies co

    For each area, implementation is

    frameworks, the second one focuse

    of testing and provide lesson learn

    The work is supported by organizin

    it.eu.

    6.2. ETSI

    ETSI, iproduce

    nearly 7

    network

    bodies and users providing a for

    currently examining how CoAP a

    Capabilities that can support mul

    www.etsi.org

    As a

    runnin

    Internevents are open to all companies,

    information about ETSI Plugtests

    6.3. IPSO AL

    Th

    in e

    a n

    com

    PROBE-IT Page 15/16

    is a two years European project with inte

    razil and Africa that aims at supporting exadvances in IoT deployments. It is inde

    rability and acceptance of validated IoT solutio

    necessary competitions and overlaps. For tha

    existing and on-going worldwide depl

    ives filling the needs of policy makers, deploym

    nt areas:

    f IoT deployments to provide stakeholders withbest options when deploying or using IoT

    takeholders to plan IoT roll-out

    p and solutions to provide stakeholders witnformance and interoperability.

    done in three phases: the first one focuses

    s on testing the tools and the third one focuses

    t from existing deployments and final version o

    regular workshops and interoperability test ev

    s an independent, non- for-profit organizatiInformation and Communication Technologies

    00 Members from five continents, and brings t

    operators, service providers, administration

    um in which all the key players can contribu

    d the RESTful interfaces can be used to d

    iple M2M applications over multiple core and

    complement to its core standards-making t

    interoperability test events for a wide range

    t, broadcasting and multimedia convergingorganizations, working and study groups imple

    nd upcoming events, please visit: www.etsi.org

    IANCE

    IPSO Alliance is the primary advocate for IP f

    nergy, consumer, healthcare and industrial ap

    on-profit organization whose members inclu

    munications and energy companies, is providi

    CoAP White Paper

    national partners from

    ploitation of Europeaned needed to ensure

    s in a global context to

    t, PROBE-IT focuses on

    oyments in different

    ents drivers, technology

    decision tools aimed at

    elements to validate

    n developing tools and

    on analysing the results

    f frameworks and tools.

    ents. Visit: www.probe-

    n whose mission is tostandards. ETSI unites

    ogether manufacturers,

    s, regulators, research

    e. The ETSI TC M2M is

    fine horizontal Service

    access networks. visit:

    sk, ETSI specializes in

    of telecommunication,

    standards. Plugtestsenting a standard. For

    /plugtests.

    r smart objects for use

    lications. The Alliance,

    e leading technology,

    g the foundation for a

  • 7/31/2019 CoAP Whitepaper

    16/17

    CoAP White Paper

    PROBE-IT Page 16/16

    network that will allow any sensor-enabled physical object to communicate to another as individuals do

    over the Internet. The IPSO Alliance membership is open to any organization supporting an IP-based

    approach to connecting smart objects. For more information, visit: www.ipso-alliance.org.

    7.ConclusionThis edition of white paper describes about the first successful CoAP plugtest which organised by Probe-IT,

    ETSI and IPSO Alliance. The success of this event motivates to conduct more such events in near future to

    help the products to be successfully launched in the market. The participants were quite interested in the

    event right from the announcement of this event and made it a successful event.

    Future events are now scheduled also expanding to 6lowpan protocol. Probe-IT is planning to organise

    another event in October 2012 in China , Wuxi collocated with the www.iot2012.org

  • 7/31/2019 CoAP Whitepaper

    17/17