Hi, all experts:
I would like to use TI MAC for my application, but I wonder if it could meet my requirements:
1. There are about 2000 ED (End Device, RFD in the spec) in one PAN. There might be more than one PAN in the system, and different PAN might need to use different channels to avoid interference to each other. Let’s call PAN coordinator as AP in the following.
2. When AP wants to send some data to an ED (the data size is about several k bytes, let’s suppose it is 5K), it is expected to complete the transit within 1 or 2 minutes. So I think it has to be a beacon-enabled PAN, otherwise it would not be possible for so many ED to query data from AP within so short time. The length of the superframe should be about 1 or 2 minutes. The max length of superframe that 802.15.4 supports is about 4 minutes (when Superframe Order is 14).
3. When AP needs to send data to many ED (Let’s say all 2000 ED), it should be completed within 30 minutes. So the average effective data rate is (2000 * 5k bytes)/(30*60) = 5.6Kbytes/s = 45 kbps.
Of course the actual data size is larger, taking the confirmation frame and other overhead into consideration. But anyway this seems not a problem, because the effective data rate could be 100kbps according to TI MAC introduction (www.ti.com/.../timac
However, I think the data should be sent in CFP period. There are two things to consider here:
(a) CFP can’t occupy all slots in a superframe. There is a minimum requirements for CAP slots. So not all slots could be used by AP to transfer data to ED.
(b) There could be up to 7 GTS in one superframe. So AP could sends data to up to 7 ED in one superframe.
Considering the above two restrictions, I am afraid the throughput might not be able to meet my requirements (45 kbps pure downlink data). If it could not , I think this requirement item could be loosened.
If CAP is used to transfer data from AP to ED, each ED needs to query from AP to check if there is data for it in each superframe, and I think there will be a lot of conflicts and failures.
4. When some events happens in the ED, such a key press by the user, ED needs to send the event notification to AP immediately within 1 second.
Suppose the superframe length is 1 minute and many of the slots are used for CFP, the ED could only send data to ED in the CAP slots of next superframe. That is, the maximum delay time might be 1 minute (or at least several tens of seconds) in worst cases. So How to send it within 1 second?
5. Each ED needs to send a heart beat message to AP indicating it is still alive. The period is around 10 minutes. I think this should not be a problem.
6. Using two CR2450 (supposing the total battery volume is 1000mAH), and one ED needs to receive 5k bytes 10 time per day, ED could work for more than 3 years. I think this might be quite rigorous. The following aspects may need consideration:
(a) Each ED needs to monitor each beacon slot to see if there is data for it.
(b) There might be a lot of conflicts when ED tries to transmit, since there are so many EDs in an AP.
(c) When frequency hopping or other anti-interference mechanism is adopted, ED may need to resync with AP. Do ED need to start searching AP from scratch when AP uses a new channel? Considering there might be a lot of interference in 2.4G, I think this also need be taken into consideration.