Design the device messaging concept

There are three primary paradigms for retrieving messages from the system:

- Pull: The device explicitly requests its messages by providing the timestamp of the last received message. The system then returns all messages received after that timestamp.

- Push: The system actively sends messages to the device as they become available, without requiring a request from the device. This typically relies on mechanisms like WebSockets or Firebase Cloud Messaging (FCM).

- Poll: The device periodically checks for new messages at regular intervals, without specifying a timestamp. This approach reduces the need for a persistent connection but may introduce slight delays.

Implementation Considerations
- Messages should be stored in a dedicated table, including the deviceId of the associated device and other relevant message metadata.
- Clients should be able to retrieve messages for a specific deviceId using secure, well-defined API endpoints.
- The system should ensure proper authentication and authorization to prevent unauthorized access to messages.