Avoiding re-attack without using a timestamp

Question

I am developing a mobile application that sends some encrypted data to the Bluetooth device , and this Bluetooth device sends data to the server. My question is that in this case I can prevent re-attacks. Someone might use a fake Bluetooth device to receive signals and send them to the server.

• The mobile application works offline and does not have a connection to the server. Therefore, using a synchronized nonce or counter does not help.

• I also can not use the timestamp to narrow the attack window, because the time of the mobile phone may be incorrect (synchronized with the time server).

• The connection between my mobile application and the Bluetooth device is one-way, and my mobile application can only send data to the device.

Answer 1

- , . , , A, 123, - 156, , - [124, 1000123] (1000000 ).

, , , . MAC ( , ).

, , ( A , A), . , , , , .