I want to compare MQTT and CoAP application layer protocols on reliability and power consumption in simulator: omnetpp.
Does Omnetpp support these two protocols?
Is there any existing open source project that I can check?
I watched a youtube video and found that the author just have a simple parameter in the omnetpp.ini file: IOT.*.protocol = "MQTT" or "COAP". This is not standard option right? I wonder what extra work has to be done.
Thanks in advance,
Alex
CoAP and MQTT models are not available for OMNeT++. In the video, the guy is definitely showing his own project.
You can create the MQTT simulation model by modifying the TCP applications given in INET and use your own message class with MQTT payload.
Related
Hi everyone I am new to OpenNMS and for now I am in learning phase. I have request from one of my client to done some research on the following two thing.
1- Can we do Industrial IOT with OpenNMS
2- Private LTE mobility and Monitoring of devices
I have very short time to conclude the result and give it back to the client. Although I searched myself for these points but I cannot conclude because I have not in depth understanding for OpenNMS for now. So my questions is can we do these features in OpenNMS. Its really helpful If someone with more experience in OpenNMS share his thoughts. Please don't consider the details about devices and their protocol I just want to know if OpenNMS is capable for doing industrial IOT for oil, gas and mining sectors.
Note: My client already have NMS build in OpenNMS that is why he is interested in OpenNMS for these features.
There is a MQTT Plugin developed which allows to consume event data and performance data over MQTT. Craig Gallen is the main author and gave a talk about OpenNMS and IoT capabilities at our conference. I personally gave it a try and got it work with Mosquitto MQTT broker and some sensor using Home Assistent. I've documented my findings here: https://pad.no42.org/uHN8csNkQB23rJsgt62SlQ.
The plugin is in early stage and need probably some more iterations. I hope the information help you to get more ideas where OpenNMS is heading. Feel free for more questions in our chat in channel opennms-discussion.
I've been involved with using OpenNMS for IoT data collection for years. Also a professional geologist having worked in O&G and mining. Short answer is yes.
Is there any way to implement MQTT protocol on Ingenico's POS devices? I am currently working on iCT220 on which I want to implement IOT project. In this project, I will be sending some bytes (may be 400-1000 bytes) of data to the broker (server).
There are lots of source codes for the library available in the internet, but all make use of Linux or Windows socket libraries, where as Ingenico's devices come with proprietary libraries.
Have anyone implemented similar project on the same devices? Can anyone guide me to the process of implementation?
Thanks in advance,
Pankaj
Surely, you will need to build it from source.
I had a look at several client libraries and it looks that dependencies come mostly from IP stack, so there's very little to be implemented to have it running.
You should expect the proprietary OS issues to be thing of the past in short time - newer terminal lines are based on linux.
I am starting a project for my university and starting to play around with the LoRa stuff, working through this pdf , filled with some examples.
I've used the code examples from page 47 (Client, Server). It's working fine but I don't understand how the node is registering at the gateway. I mean, where is the part in the code?
The links you have posted to Github appear to be using the RFM95 module in a peer to peer fashion rather than utilising LoRaWAN style communication. Can I suggest you try using the LoRa LMIC library instead, this has a full implementation of LoRaWAN and can be used with TheThingsNetwork & RFM95 modules - https://github.com/matthijskooijman/arduino-lmic.
As for the gateway I am unsure of the Dragino gateway hardware / software, however I believe they are capable of acting as a Single Channel Gateway / Packet Forwarder. There is a decent forum thread here discussing how to use the Dragino gateway with TTN, https://www.thethingsnetwork.org/forum/t/dragino-gateway/6154 and the Dragino wiki has a comprehensive how to guide http://wiki.dragino.com/index.php?title=Connect_to_TTN. However there are short comings with single channel gateways, and some do not support downstream messages, so depending on your use case this may or may not be so useful.
If you can describe more in depth your use case I'd be keen to offer up more advice / ideas, I use LoRa a fair bit, but I only have experience with the Arduino Dragino hats not their gateway.
The protocol is very simple and is developed on top of TCP. I need to analyze a big libpcap dump file to calculate the average value and standard deviation of the conversation time and of the number of packets per conversation.
Using Wireshark it's simple to analyze the TCP conversations between the endpoints, but the summary includes all of the TCP packets (lots of SYNs, ACKs and FINs), and this messes up the data.
Is there another tool to do this kind of analysis? Is there a way to EASILY extend Wireshark's functionality?
You can check out the Argos custom protocol analyzer.
It is a commercial tool and it has a powerful and easy to use XML protocol definition language.
Additionally it can monitor Ethernet and IP traffic as Wireshark does and open Libcap files
Not sure I understand exactly what you need, but if you're looking to analyze only the packets with application data in them you can ask Wireshark to display only those packets with the PSH ("push to application") flag set.
What exactly this protocol contains? Is there any specific header for its own usage? Wireshark provides many complex filtering options that you can explore.
If you want to do it using program, you can try PCAP or PF_SOCK. You may need to write your own filtering criteria then.
Is there another tool to do this kind of analysis? Is there a way to
EASILY extend Wireshark's functionality?
You can try Scapy ( http://www.secdev.org/projects/scapy/ ), with Scapy it is very easy to add new protocols: http://www.secdev.org/projects/scapy/doc/build_dissect.html .
Scapy is not as Wireshark, but I think it will solve your problem.
I've been looking for a good general purpose binary network protocol definition framework to provide a way to write real-time game servers and clients (think World Of Warcraft or Quake III) in multiple languages (e.g. Java backend server and iPhone front-end client written in Objective-C and Cocoa).
I want to support Java Flash clients, iPhone clients and C# clients on windows (and XNA clients on XBOX).
I'm looking for a way to efficiently send/receive messages over a TCP/IP or UDP socket stream connection. I'm not looking for something that can be sent over an HTTP Web Service, like JSON or XML marshalled Objects. Although Hessian's binary web service protocol is a very interesting solution
I want a network protocol format and client/server basic implementation that will allow a client to connect to a server and send any message in the defined protocol and receive any message in the protocol without having to bind to some kind of RPC endpoint. I want a generic stream of any message in my protocol incoming and outgoing. This is so that I can support things like the server sending all clients the positions of various entities in the game every 100 milliseconds.
The network protocol frameworks I've found are as follows:
Google's Protocol Buffer - but it lacks support for things like sending/receiving arbitrary messages from your given protocol.
Apache Thrift - an interesting option but it is geared mainly towards RPC instead of generic game client/server socket type connections where the client or server can send messages at any time and not just in response to a client RPC request.
Raknet Multiplayer - Raknet provides full multiplayer network library (it's free for indie development with revenue under $250k)
UPDATE : OculusVR Acquired RakNet and its Free/OpenSource now. U can find it on Github
Hessian Binary Web Service Protocol - is a HTTP web service binary protocol, it is well-suited to sending binary data without any need to extend the protocol with attachments.
Raknet provides a good game/simulation oriented multiplayer library.
Apache Thrift and Google's protocol buffers seem to be the simplest approaches to using in a game network protocol client/server architecture.
Hessian seems like a great fit if you want to create a web based game server with a Java or flash client using some type of server push technology like COMET. Hessian might provide a really interesting way to support real-time games on the web and even be able to host them on VM web solutions like Google's App engine or Amazon's EC2.
There's some discussion about using various protocol definition frameworks for games and other uses:
Comparison of Various Serialization Frameworks
Thrift vs Protocol Buffers - Thrift is declared the better framework because it has a fully supported RPC client/server implementation
Using Protocol Buffers for client server Game API determining what type of message to decode
Bi-Directional RPC using thrift
DIS
If you do go the route of writing your own protocol, you may want to read the answer I posted here.
In summary it discusses what you should think about when writing a protocol, and list a few tricks for versioning and maintaining backwards and forward compatibility.
If you are really concerned about multiple platforms and language, be sure to take into account endian issues. A binary protocol designed for this use must use network-byte-order, so it needs custom per-data-type serialization functions; you cannot just blindly push C structs into network buffers.
A common solution for this problem at game companies is to have protocol description language or specification in a simple format like XML or python or lua, and then have code generation for each target language that generated packet classes with both data structure and serialization. This specification could use a type system that starts with basic types, then extends to include game-specific types with semantic information, enumerations or more complex structures. For example a data file could look like:
Attack = {
source = 'objectId',
target = 'objectId',
weapon = 'weapon::WEAP_MAIN',
seed = 'int'
}
This could generate code like:
#define PT_ATTACK 10002
class PacketAttack : public Packet {
public:
PacketAttack () : m_packetType(PacketAttack::s_packetType) {}
ObjectId m_source;
ObjectId m_target;
WeaponType m_weapon;
int m_seed;
bool Write(Stream* outStream) {
Packet::Write(outStream);
outStream << m_source;
outStream << m_target;
outStream << m_weapon
outStream << m_seed;
}
bool Read(Stream* inStream);
static const int s_packetType;
};
This does require some more infrastructure.. streams, packet base classes, safe serialization functions..
I want to echo Bill K's suggestion. It's not hard to roll your own protocol.
For the iPhone side, have a look at AsyncSocket which support for delimiter based TCP packets built in, and it's not hard to build a solution which uses packet headers.
If you quickly want to have a testserver to play against AsyncSocket on the iPhone, you can look at Naga (for the java server part) which has ready made stuff both for delimiter based packets and packets with headers. Naga was partially written with networked games in mind.
I disagree with "roll your with simple delimited strings approach": question is, what exactly would be the benefit? Getting to write and maintain more code?
The only reasons I could see would be lack of tool support (writing for some odd platform), or specific (very) hard performance or message size constraints.
Or, sometimes, really wanting to write a format -- that's ok, but it must be an explicit reason.
Depending on exact needs I would suggest considering JSON, since it can read and write arbitrary messages; has good object binders for Java (just like xml), is easier to read than binary formats, and is all around "good enough" for many use cases.
If message size is very important, Protobuf can work well -- while its size is not always as small as gzipped alternatives (gzip+xml, gzip+json compress very well), it's usually close.
ASN.1 fits the definition of "good general purpose binary network protocol definition framework". It's also standardized by ITU-T, so there's a lot of existing tools and libraries for various languages.
The DER encoding is suitable for efficient network communications, the XER encoding for human-readable (and writable) permanent storage.
Because you want to use different languages and also because you want something clean/small, I suggest the protocol buffers of google. You need a pre-compile part for the RPC but I really think that's the best option when you begin to mix different languages.. Here's the link: http://code.google.com/apis/protocolbuffers/docs/overview.html
Why not implement UDP directly? Your question mostly mentions what you don't want.. What further form of abstration do you want on top of UDP?
Download the Quake III sourcecode and see how they frame game updates over UDP?
The IP protocol has been designed to support multiple devices/OSes in a uniform way, isn't this what you ask for?
What protocol has implementations across a huge range of systems, hmm, IP perhaps?