On Mon, Mar 10, 2008 at 6:47 AM, jiwen zhang <[EMAIL PROTECTED]> wrote: > Hello all : > There is a words "The collection infrastructure can be multiplexed among > independent applications, by means of a collection identifier. It is > important to note that the data traffic in the protocol is multiplexed, > while the control traffic is not" in TEP 119. what does it mean ? can > someone explain it detailedly ?what is "multiplexed" mean ? why "data > traffic" is multiplexed and "control traffic" is not ? what is function of > collection id in Collection ?
You can use multiple components (or multiple instances of collection sender within the same component) to send packets using collection. If you do that, you need a way to distinguish between the packets originated by different components or instances of collection sender. You would do that using different collection id's. Multiple collection traffic generated with different collection id's are serviced by a single collection component and translated into packets with a single AM type but different collection id's - hence multiplexed data traffic. Because you have a single collection component, there is only one source of control traffic, which is why you don't need to multiplex the control traffic. > what does it mean ? what is the meaning of "different protocal" ? if two > application using different collection_id or am_id_t,do they can communicate > with each other ? (i can't understand the function of collection_id and > am_id_t) You should read the section on am id in TEP 116. > > what is the relation between Collection and CTP ? Collection is a service that helps you collection data from the nodes in the network to a sink. Collection has a well-defined interface that describes how to use it as an application. CTP is one protocol that provides the collection service. LQI is another protocol that provides the collection service. - om_p _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
