Segment ID issue

Continuing the discussion from Regarding AT+CIPBUFSTATUS Response:

Hi Team,

Can you please respond to the above attached Segment ID Issue.

Thanks,
Padmini

Sometimes, we see the discrepancy in the segment ID sent Bytes .

63676,64328,63675,15360,10

Due to the below condition, we are not able to reset the segment ID when segment ID reaches its maximum limit (65535/ 2 Bytes)

*Only when next segment ID - segment ID sent = 1, can AT+CIPBUFRESET be called to reset *
the counting.

In this type of situations, what should be the expected action to reset the Segment ID count ?