uf:totam
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
uf:totam [2010/01/21 17:39] – elisag | uf:totam [2020/04/28 19:32] – elisag | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Tuples | + | ====== Scoped |
- | TOTAM is a communication abstraction to enable pervasive social interactivity: | + | TOTAM is tuple space model geared towards mobile ad hoc networks which provides |
- | The basic communications API of the framework provides means to address | + | TOTAM adopts features |
- | However, communicating | + | In TOTAM, tuple spaces are annotated |
- | Instead, we have designed | + | The novelty |
- | ==== Design | + | ===== Motivation ===== |
- | The original idea was to build a framework similar to [[http:// | + | [[http:// |
+ | These propagation rules are crucial to provide programmers with a flexible mechanism to achieve context-awareness based not only on connectivity but also on semantic information. | ||
- | However, in TOTA tuples are sent to all communication partners in range. Upon arrival at the receiver side, the tuple itself decides whether it has to be stored in that tuple space. By transmitting tuples potential malicious or non-intended users are provided with sensitive information. Not only does sending all tuples blindly to all communication partners in range raise privacy issues, it also creates a network traffic overhead. | + | However, in TOTA tuples are sent to all communication partners in range. Upon arrival at the receiver side, the tuple itself decides whether it has to be stored in that tuple space. As all devices can potentially access all information, |
- | To solve this issues, we extended TOTA with dynamically scoped tuples resulting in the TOTAM ("Tuples | + | ===== Scoped |
- | Another goal was to implement TOTAM as a general framework so that we can then instantiate our TOTAM with guanote objects for the [[: | + | TOTAM provides the programmer |
- | ==== API ==== | + | {{: |
- | Here comes the public interface | + | Figure above illustrates how a scoped tuple is propagated through |
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== API ===== | ||
+ | |||
+ | TOTAM has been implemented in AmbientTalk. The system library shipped with AmbientTalk contains the TOTAM implementation under at/ | ||
+ | |||
+ | |||
+ | In order to use TOTAM, you need to load the library and create a TOTAM tuple space as follows: | ||
< | < | ||
- | makeTupleSpace() | + | import / |
- | makeTuple(tupleID) | + | def myTupleSpace := makeTupleSpace(); |
- | extendTuple: tuple with: closure | + | </ |
+ | |||
+ | A description can be passed in the '' | ||
+ | < | ||
+ | // a “hallo” message tuple from wolf. | ||
+ | def halloTuple | ||
+ | // a template for message tuples from wolf. | ||
+ | def wolfTuples := tuple: [" | ||
+ | // a template for any message tuples. | ||
+ | def msgTuples := tuple: [" | ||
</ | </ | ||
- | A tuple space (ts) in AmbientTota basically consists of a local ts, an ambient ts (to inject | + | TOTAM provides operations |
< | < | ||
- | // tota operations | + | // add tuple to tuple space |
- | def add(tuple) | + | myTupleSpace.out(halloTuple); |
- | def delete(template) -> vector with the deleted | + | // get a Message tuple |
- | matching the template | + | def aMessageTuple := myTupleSpace.rdp(msgTuples); |
- | def read(template) -> vector with the matching tuples | + | // get all Message |
+ | def messageTuples := myTupleSpace.rdg(msgTuples); | ||
+ | </code> | ||
- | // | + | The '' |
- | def inject(tuple) | + | |
- | // places a listener on to the local TS ( ~ subscribe | + | In the original Linda model, read and in operations were provided |
- | // it returns a publication object | + | |
- | when: template matches:{ | tuple | | + | |
- | // code | + | |
- | } | + | |
- | //Templates are currently boolean expressions on tuples. | + | |
- | Example | + | |
- | { |guanote| | + | |
- | //methods belonging to the propagation protocol | + | < |
+ | def msgTuples := tuple: [Message, var: `from, var: `content]; | ||
+ | myTupleSpace.whenever: | ||
+ | system.println(“Got message: “ + content + “ from: ” + from); | ||
+ | }; | ||
- | // notifies the discovery of a remote ts | + | myTupleSpace.whenever: |
- | // and starts the propagation protocol | + | |
- | def notifyTSDiscovered(ts) | + | }; |
- | // notifies the arrival of tuples from a ts | + | |
- | // receive side of the propagation protocol | + | |
- | def receiveTyples(tuples) | + | |
</ | </ | ||
- | A tuple in our system | + | The '' |
+ | |||
+ | The '' | ||
< | < | ||
- | // called in every tuple at pass() | + | myTupleSpace.goOnline(); |
- | def decidePropagation() -> boolean | + | myTupleSpace.inject: halloTuple; |
- | // specifies operations on the local TS | + | |
- | def doAction | + | |
- | // specifies operations on the tuple itself | + | |
- | def changeTupleContent() -> tuple | + | |
- | // if true -> note gets added to local TS | + | |
- | def decideStore () -> boolean | + | |
- | // if true -> tuple gets unexported and deleted from local TS. | + | |
- | //new operation not in TOTA | + | |
- | def decideSleep() -> boolean | + | |
</ | </ | ||
- | Ideas: | + | Note that the network facilities are disabled by default, so before injecting something in the network, the '' |
+ | |||
+ | A tuple injected to the network carries the following default propagation protocol. | ||
+ | |||
+ | < | ||
+ | def defaultPropagationProtocol(){ | ||
+ | isolate: { | ||
+ | // | ||
+ | def decideEnter(ts) { true }; | ||
+ | def doAction(ts){}; | ||
+ | def changeTupleContent(ts){self}; | ||
+ | def decideStore(ts) {true}; | ||
+ | // | ||
+ | def inScope(senderDescriptor, | ||
+ | def decideDie(ts){false}; | ||
+ | }; | ||
+ | }; | ||
+ | </ | ||
+ | |||
+ | However, other propagation protocols can be created and attached to a tuple before being injected in the network as follows: | ||
+ | |||
+ | < | ||
+ | //define a new propagation protocol | ||
+ | def blueProtocol := propagationProtocol: | ||
+ | def inScope(senderDescriptor, | ||
+ | receiverDescriptor.team == " | ||
+ | }; | ||
+ | // attach the protocol to a tuple | ||
+ | def aBlueTuple := tuple: [" | ||
+ | withPropagationProtocol: | ||
+ | // inject the tuple to the network | ||
+ | def publication := inject: aBlueTuple; | ||
+ | </ | ||
+ | |||
+ | The '' | ||
+ | |||
+ | < | ||
+ | // sends an antituple to notify the removal of this tuple. | ||
+ | publication.retract(); | ||
+ | </ | ||
+ | |||
+ | In order to notify the removal of a tuple, TOTAM sends an antituple for the removed tuple. For every tuple there is (conceptually) a unique antituple with the same format and content, but with a different sign. All tuples injected by an application have positive sign while their antituples have a negative sign. Whenever a tuple and its antituple are stored in the same tuple space, they immediately annihilate one another, i.e. they both get removed from the tuple space. By means of antituples, TOTAM can “unsend” tuples injected to the network. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== Further Reading ===== | ||
- | TOTA could be combined with the RETE engine we built for the characteristic functions, in the future to reason about multiple tuples. | + | **TOTAM: Scoped Tuples |
+ | ([[ http:// | ||
- | decideSleep() is there for discontinuous decidePropagation functions. for example, tuples that should be only propagated every Tuesday could not implemented with TOTA because the propagation protocol only gets called once. We change | + | < |
+ | </ |
uf/totam.txt · Last modified: 2021/09/24 10:49 by elisag