Can cellular SIM be part of a LoRa network? - iot

I am doing my FYP and for this I need some information:
Is it possible to connect a mobile with a LoRa Network via cellular SIM?
Actually, I want to build a mobile software that will operate with a local LoRa network, and the user can connect to the network using this app via cellular network.

No, LTE/GSM/EDGE/Mobile network is a different transmission method than LoRa and thus can not connect to LoRaWAN networks.

No I don't think you can . But I think you need another module to include in your project to handle the SIM part and that way you can switch between the Lora and SIM

Related

Is possible to use ESP8266 as a network adapter?

I have a IoT solution based on Freescale/NXP FRDM-K64 board and the MQX operating system, communicating to the Internet with Ethernet. Now I would like to change from Ethernet to Wi-Fi.
The ESP8266 (or another module under $10) can provide a mechanism to operate as a network adapter, ignoring the internal IP stack and sending the "low-level packages" to the Ethernet/IP stack already implemented in the current solution (something like a "totally transparent and bidirecional bridge")?
Furthermore, this Wi-Fi module can listen multiple ports simultaneously, for example: 80/443 for HTTP/S and 161 for SNMP?
If this requires a custom ESP firmware or some MQX modifications, can you provide some guidelines?
With the Espressif SDK 1.5.2 for the ESP8266 it's not possible to send "low-level packages". You can send UDP packets or can establish TCP connections. But unfortunaly there is no API for sending only packets.

Disable WiFi assist UDP transfer on iOS 9

I want to send UDP packages in a local network using GCDAsyncUdpSocket.
My fear is that at some point UDP packages will be sent via LTE because of the newly introduced "WiFi assist" from iOS 9.
Is there some way I can pretend iOS 9 from passing my traffic to cellular network, and instead require it to always use WiFi?
Thanks a lot for any ideas!
I think you can use "Reachability" to detect if the phone is connected to a wi-fi or to cellular data and then avoid to send message or manage the that particular condition. You can also ask to the user to disable the wi-fi assistant with a popup just to be sure to avoi the problem.

Is there a way to programmatically change network routes on an iOS device?

Scenario: I want to have an iOS device connect to a LAN that has no upstream Internet connection, yet still retain and use its cellular data connection.
Theoretically, it strikes me that the iOS wifi NIC and the cellular data NIC are similar enough to dual NICs in a PC that I should be able to set up routing such that any request to, say, 192.168.. goes through the wifi connection, and any other request goes through the cellular data connection.
I did a test to see if both NICs are active when the iOS device is connected to wifi by the following steps.
Ensure that my iPhone's wifi is off and that I have a good cellular data connection.
Disconnect my wifi router's Ethernet cable to my cable modem.
Connect my iPhone to the wifi router.
Use another iPhone that's connected only via cellular data to create a game of Words with Friends.
As soon as the other iPhone completed the first move, my iPhone received a notification that there was a new game to play.
This confirmed that the cellular data connection was indeed alive and well enough to receive push notifications despite the wifi NIC's being connected.
The question becomes, then, can an app programmatically connect to a given wifi network, set the cellular data network to be the default route, and route any requests to, say, 192.168.. to go through the wifi network?
I know this post is old, but I happen to have done some work on using multiple network interfaces on iOS.
My experiments showed that accessing via hostname results in iOS choosing the network interface it wants to use, and not trying any further interfaces if the host cannot be resolved.
If you know the DNS Server IP address for any Ethernet/WiFi based network, you can send a DNS request yourself, convert the hostname into an IP address and access via IP address. iOS will then use the correct interface.
My guess is, that if you have the private class IP address space accessible over both connections, there's probably nothing you can do to specify which network interface should be used.

RSSI through Multipeer Connectivity Framework

Is it possible to detect the signal strength of a connection between two iOS devices by using Multipeer Connectivity Framework?
Unfortunately, it's not possible. I think there is a good reason for this. As you can read in the docs:
The Multipeer Connectivity framework provides support for discovering
services provided by nearby iOS devices using infrastructure Wi-Fi
networks, peer-to-peer Wi-Fi, and Bluetooth personal area networks and
subsequently communicating with those services by sending
message-based data, streaming data, and resources (such as files).
In case of infrastructure Wi-Fi network, there is no direct connection between two iOS devices as they communicate through an access point. Therefore you can't get the signal strength of a connection, because it simply doesn't exist.
If you want to get RSSI, you can use Core Bluetooth framework instead.

Communication between ZigBee and Bluetooth

Bluetooth and ZigBee devices are working or pairing within its own family devices based on parameters such as network layers, security algorithms, etc... I want to write an application to make a communication between ZigBee and Bluetooth device. Is it possible?
You would need to create a gateway between the two networks. Your application would need to interface with a ZigBee radio and a Bluetooth radio, join each network, and then proxy communications between devices on the networks.
What devices do you plan to bridge? Your application will need to appear as device X on the ZigBee network, and device Y on the Bluetooth network and convert data received to the correct format to send out on the other network.
If it were kept simple, something like this could work. A module that is a Zigbee presence, with a pairable bluetooth node. If a bluetooth-paired device comes near, the Zigbee announces itself as 'present'. When the bluuue tooth paired device is no longer around, the Zigbee device becomes "not present".

Resources