CoAP request-response model in IOT Protocols - Time & Space Complexity

Time Complexity: CoAP request-response model

O(n)

Understanding Time Complexity

We want to understand how the time to complete a CoAP request-response interaction changes as the number of messages or retries grows.

How does the communication time increase when more messages are sent or retransmitted?

Scenario Under Consideration

Analyze the time complexity of the following CoAP request-response exchange with retransmissions.

// Send a CoAP Confirmable request
send_confirmable_request() {
  send_message();
  wait_for_ack(timeout);
  if (!ack_received) {
    retransmit_message();
  }
}

This code sends a confirmable CoAP message and waits for an acknowledgment. If no ack arrives within a timeout, it retransmits once.

Identify Repeating Operations

Look for repeated actions that affect time.

• Primary operation: Sending messages and waiting for acknowledgments.
• How many times: Up to two times (initial send plus one retransmission if needed).

How Execution Grows With Input

As the number of messages to send increases, the total time grows roughly in direct proportion.

Input Size (n messages)	Approx. Operations (send + wait)
10	Up to 20 (each message may be sent twice)
100	Up to 200
1000	Up to 2000

Pattern observation: The time grows linearly with the number of messages, doubling if retransmissions occur.

Final Time Complexity

Time Complexity: O(n)

This means the total communication time grows in a straight line as the number of messages increases.

Common Mistake

[X] Wrong: "Retransmissions cause the time to grow exponentially with messages."

[OK] Correct: Each message is retransmitted at most a fixed number of times, so time grows linearly, not exponentially.

Interview Connect

Understanding how communication time scales with message count helps you design efficient IoT protocols and troubleshoot delays.

Self-Check

What if we allowed unlimited retransmissions until acknowledgment? How would the time complexity change?

Practice

1. What is the main purpose of the CoAP request-response model?

easy

A. To create user interfaces for IoT devices

B. To store data permanently on a server

C. To send a request and receive a response between devices

D. To encrypt messages between devices

Solution

1. Step 1: Understand CoAP communication basics

   CoAP is designed to allow devices to send requests and get responses, similar to asking a question and getting an answer.

2. Step 2: Identify the purpose of request-response

   The request-response model is about communication, not storage, encryption, or UI creation.

3. Final Answer:

   To send a request and receive a response between devices -> Option C

4. Quick Check:

   Request-response = send and receive [OK]

Hint: Request-response means ask and answer communication [OK]

Common Mistakes:

• Confusing request-response with data storage
• Thinking CoAP handles encryption by default
• Assuming CoAP creates user interfaces

2. Which CoAP method is used to retrieve data from a device?

easy

A. GET

B. POST

C. DELETE

D. PUT

Solution

1. Step 1: Recall CoAP methods

   CoAP uses methods similar to HTTP: GET, POST, PUT, DELETE.

2. Step 2: Identify method for retrieving data

   GET is used to request and retrieve data from a device.

3. Final Answer:

   GET -> Option A

4. Quick Check:

   GET = retrieve data [OK]

Hint: GET method always fetches data [OK]

Common Mistakes:

• Using POST to retrieve data instead of send
• Confusing PUT with GET
• Thinking DELETE retrieves data

3. Given a CoAP GET request to a sensor, what is the expected response code if the data is successfully retrieved?

medium

A. 2.05 Content

B. 4.04 Not Found

C. 5.00 Internal Server Error

D. 3.01 Moved Permanently

Solution

1. Step 1: Understand CoAP response codes

   CoAP uses numeric codes similar to HTTP. 2.xx codes mean success, 4.xx client error, 5.xx server error.

2. Step 2: Identify success code for GET response

   2.05 Content means the request succeeded and the content is returned.

3. Final Answer:

   2.05 Content -> Option A

4. Quick Check:

   Success code for GET = 2.05 Content [OK]

Hint: 2.xx codes mean success in CoAP [OK]

Common Mistakes:

• Choosing 4.04 which means resource not found
• Confusing 5.00 server error with success
• Thinking 3.01 means success instead of redirect

4. A CoAP client sends a POST request but receives no response. What is the most likely cause?

medium

A. The server does not support POST method

B. The request was sent as non-confirmable and got lost

C. The client used an invalid URI format

D. The server returned a 2.05 Content response

Solution

1. Step 1: Understand CoAP message types

   CoAP supports confirmable (CON) and non-confirmable (NON) messages. NON messages may be lost without retry.

2. Step 2: Analyze no response scenario

   If a POST is sent as NON and network drops it, no response is received.

3. Final Answer:

   The request was sent as non-confirmable and got lost -> Option B

4. Quick Check:

   NON messages can be lost without response [OK]

Hint: Non-confirmable messages may get lost silently [OK]

Common Mistakes:

• Assuming server always supports POST
• Confusing invalid URI with no response
• Thinking 2.05 Content means no response

5. You want to update a device's configuration using CoAP. Which method should you use and what response code indicates success?

hard

A. DELETE method with 2.02 Deleted response

B. POST method with 4.00 Bad Request response

C. GET method with 2.05 Content response

D. PUT method with 2.04 Changed response

Solution

1. Step 1: Identify method for updating data

   PUT is used to update or replace a resource on the device.

2. Step 2: Find success response code for update

   2.04 Changed means the update was successful.

3. Final Answer:

   PUT method with 2.04 Changed response -> Option D

4. Quick Check:

   Update = PUT + 2.04 Changed [OK]

Hint: PUT updates; 2.04 means update success [OK]

Common Mistakes:

• Using GET to update data
• Confusing 4.00 error as success
• Mixing DELETE with update operation