http://knowledgewithoutlimitation.blogspot.com 2014-11-09 ~ Ilmu Tanpa Sempadan

Open Source, Delay Tolerant Network, Internet of Things

Knowledge Without Boundary

Thursday, November 13, 2014

2.2.2 Architecture of DTN

The DTN architecture implements store and forward message switching by overlaying the bundle layer on top of heterogeneous regional networks. Bundles also called messages (message switched). The bundle layer stores and forward bundle fragments between nodes. A single bundle layer protocol is used in all regional networks and make up a DTN.
DTN designed to use storage within the network to support the store and forward operation over a networking path as shown in Figure 2.8. IP end to end communication in between the source and destination must wait for complete path while DTN store and forward delivery did not need to wait for a complete path. DTN store and forward delivery will perform incremental progress without end to end path. 


Figure 2.8: Store and forward delivery
Application Data Units (ADUs) are a DTN-enabled application that sends messages of arbitrary length.  The bundle layer transformed the ADUs into "bundles" which is a one or more protocol data unit. Bundles are forwarded by DTN nodes and have two or more "blocks" of data as shown in Figure 2.9. 

Figure 2.9: Bundles
Application data or other information in each block used to deliver the containing bundle to its destinations.  Blocks used to hold information in the header or payload portion of protocol data units in other protocol architectures.  It is called "block" instead of "header" because blocks may not appear at the beginning of a bundle due to particular processing requirements [8].
Bundle layer as shown in Figure 2.10 support end to end transfer across heterogeneous network protocol stacks. An essential element of the bundle-based style of forwarding is that bundles have a place to wait in a queue until a communication contact is available.  Size of storage used in this operation is depending on the system requirement. The assumptions for this operation as follows:
i.                    Storage is available and well-distributed throughout the network.
ii.                  Storage is sufficiently persistent and robust to store bundles until forwarding can occur.
iii.                This "store-and-forward" model is a better choice than attempting to effect continuous connectivity or other alternatives.

Figure 2.10: Bundle Space
Bundle Protocol nodes and endpoints are identified by name. Bundle Protocol names are used Uniform Resource Identifier (URI). Each URI begins with a scheme name followed by a series of characters where the syntax is defined by the scheme. This is examples of Bundle Protocol name:
i.                    dtn://thismachine/ping
ii.                  dtn:pop:mailto:myemail@gmail.com
The bundle protocol is designed with a Primary Bundle Block, payload block which contains the ADU data itself and a set of other blocks. The following fields are all present in the primary bundle block [3]:
i.        Creation Timestamp - a concatenation of the bundle is creation time and a monotonically increasing sequence number such that the creation timestamp is guaranteed to be unique for each ADU originating from the same source.  The creation timestamp is based on the time-of-day an application requested an ADU to be sent (not when the corresponding bundle(s) are sent into the network).  DTN nodes are assumed to have a basic time synchronization capability.
ii.      Lifespan - the time-of-day at which the message is no longer useful.  If a bundle is stored in the network (including the source is DTN node) when its lifespan is reached, it may be discarded.  The lifespan of a bundle is expressed as an offset relative to its creation time.
iii.    Class of Service Flags - indicates the delivery options and priority class for the bundle.
iv.    Source EID - EID of the source.
v.      Destination EID - EID of the destination.
vi.    Report-To Endpoint ID - an EID identifying where should be sent.  This may or may not identify the same endpoint as the Source EID.
vii.  Custodian EID - EID of the current custodian of a bundle.
The lifespan field is very useful in an attempt to keep the email data in this offline email system for a longer period of time until it transferred to another device. Another block such as metadata block is used to identify the content. It could be used to implement ‘network as a database’ and can be encrypted separately from the payload. The payload block indicates information about the contained payload and the payload itself.
Binding interprets an endpoint identifier (EID) to select the next hop or next region specific layer the bundle can be forwarded toward its destination. Figure 2.11 shows the bundle layer through every region specific layer. Late binding means that the binding of a bundle is a destination to a particular set of destination identifiers or addresses does not necessarily happen at the bundle source. Binding might occur at the source, during transit or at the destination. DTN nodes use some form of persistence storage and stored bundles can maintain even if the system restarts. Persistence assumes that storage is available, distributed well through the network and store bundles sufficiently until forwarding can occur [9].

Figure 2.11: Bundle Overlay
DTN can store bundles at intermediate nodes. It can still route even there is a waiting time. Primarily the route will be forwarded to the nodes that will have connectivity later on. In Figure 2.12, data can be transferred directly between user computer A (PC A) and user computer B (PC B) when both are connected. When the PC B is disconnected, DTN routes data to Temporary Data Storage and deliver it later to the PC B. When the PC B is reconnected, data stored in the Temporary Data Storage is delivered even if PC A is disconnected. 

Figure 2.12: Bundle Routing
Security also can be provided to protect against unauthorized use. Bundle Authentication Block (BAB) as shown in Figure 2.13 [7], provides hop-by-hop authentication and integrity protection for the bundle between adjacent bundle nodes. Unauthorized resource utilization can be prevented by enabling modified bundles to be detected and discarded at the first node at the destination receiver.


Figure 2.13: Bundle Authentication Block (BAB)

Wednesday, November 12, 2014

Fix samsung error: E:failed to mount / efs (Invalid argument)

I got a Samsung Galaxy Note 8 GT-N5100 with error E:failed to mount / efs (Invalid argument) whenever I run a wipe cache or wipe factory in recovery. I did stuck in a samsung logo. This looping is a common nightmare for a Samsung devices.

There is a fix for this error. Follow this steps:

Ready a ROM(I use Pac Man ROM) in your microSD and insert into device.

1) Download and flash official firmware for your phone using Odin.
2) Root and flash custom recovery(I use TWRP) using Odin
3) Install ADB on your computer(Usually by installing Samsung USB driver)
4) Boot into recovery mode(hold up+power button)
5) Connect phone to PC via USB Cable
6) In recovery mode Choose “mount and storage > mount /system”(In TWRP, just tick the 'system')
7) At PC, open ADB command window and type :

adb shell
su
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img
mke2fs /dev/block/mmcblk0p3
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p3 /efs

DON'T REBOOT YET, Now /efs is mounted don't unmount it.

Do a factory reset

Install your new rom, It should install without any errors

Boot your phone,  After it boots your signal notification most likely will be gray and internet or calls may not work. To fix just install gapps and it will be fixed.

If you don't have phone, try this:

Go back into recovery and get adb access. Then run this command:


sumke2fs /dev/block/mmcblk0p3mkdir /efsmount -t ext4 /dev/block/mmcblk0p3 /efsdd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096reboot

This command will create a generic EFS files on your device.
Now normally your device will reboot and it should pass Samsung logo.
Your device might display a screen with a yellow text (FactoryMode)

If your device display a annoying transparency black background which contains some info about your device (PDA, Phone, CSC, H/W, Camera, …) in yellow text … and lock screen is not working, mean that your device is in factory mode.

“Factory Mode” is enabled if the EFS partition is corrupted because of installing custom ROMs, bad Mods or downgrading your current system version or after you succeeded in fixing the EFS partition.

Follow this step to exit FactoryMode:

1) Install root browser
2) Go to Local > / Device > efs > FactoryApp and open factorymode as text in “ES Note Editor”
3) Change it from OFF to ON and save it
4) Open keystr as text in “ES Note Editor”, change it from OFF to ON and save it
5) Reboot

Alternative solution by using Terminal Emulator.
1) Install “Terminal Emulator“
2) Type :

su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot


References:
http://forum.xda-developers.com/showthread.php?t=2430202
http://zidroid.com/how-to-fix-failed-to-mount-efs-for-galaxy-s3-gt-i9300/
http://zidroid.com/how-to-exit-factory-mode-for-samsung-galaxy-devices/
http://www.digitalreborn.com/fix-samsung-galaxy-unable-mount-efs/

Tuesday, November 11, 2014

2.2.1 Reason to use DTN

Internet Protocols (IP) required end-to-end connectivity. It operates poorly in an environment with a very long delay path and frequent network partitions which causes by severe power or memory constraints by end nodes which make the network infrastructure lacking ‘always-on’ environment. Delay and disruption can be caused by long distance and time. There are some fundamental assumptions in the internet architecture that can cause a break in the network under long delays and intermittent connectivity such as [7] [3]:
i.                    There is always an end-to-end path between source and destination exists.
ii.                  Need to establish at least one round-trip or transmission and response before any application data can flow. This means that there is a requirement of the sender and receiver negotiate a connection to regulate the flow of data.
iii.                Retransmissions from the source are good way to provide reliable communication.
iv.                End-to-end loss is relatively small.
v.                  Endpoint-based security is sufficient to meet most security concerns.
DTN is used to tolerate long delays and intermittent connectivity which is a weakness in Internet Protocols. DTN is able to enable a connection when there is no end-to-end path between the source and destination, the round-trip is not needed to regulate the flow of data, retransmission from data receivers is not in use for repairing errors because there is no end-to-end path and unlike IP, DTN is ignoring the end-to-end dependency such as in IP fundamental assumptions (iv) and (v). There are environments that exhibiting some of these characteristics which are:
i.                    Space communications where there are high latencies, intermittent connectivity due to antenna schedule.
ii.                  Sensor networks when nodes need to power down to conserve energy.
iii.                Line of sight radios especially for urban area with wooded/hill environments.

iv.                Mobile networks