Project

General

Profile

Watched Prefix Insertion Protocol » History » Version 8

Weiqi Shi, 07/24/2014 03:00 PM

1 1 Weiqi Shi
Watched Prefix Insertion Protocol
2
=================================
3
Watched Prefix is a new protocol for repo insertion. By using this protocol, repo keep sending interests to request the data with same prefix. When a data packet is received, repo will update selectors (exclude selector in most cases) to exclude the received data and request new one. Repo will stop watching the prefix until a command interest in tell it to stop, the total amount of sent interests reaches a specific number or time out.
4
5
## Basic operations
6
7
### Keep requesting and inserting data with same prefix
8
9
Command verb: **watch**
10
11
The name semantics follows the format of the repo command. The <command verb> is defined as ``watch``.
12
For example, for ``<repo prefix>`` as ``/ucla/cs/repo``, the following is an example:
13
14
    /ucla/cs/repo/watch/<RepoCommandParameter>/<timestamp>/<random-value>/<SignatureInfo>/<SignatureValue>
15
16
### Watch status check
17
18
Command verb: **watch check**
19
20
During the watched prefix progress, requester could send watch status check command to check the status of the progress. This status check command is also signed interest. The semantics of watch status check command is shown as follows:
21
22
<command verb> equals to ``watchCheck``. For example:
23
24
    /ucla/cs/repo/watchCheck/<RepoCommandParameter>/<timestamp>/<random-value>/<SignatureInfo>/<SignatureValue>
25
26
## Formats
27
28 5 Alex Afanasyev
### [[Repo Command|RepoCommandParameter]]
29 1 Weiqi Shi
30
The following components are used in watch-prefix command
31
32 5 Alex Afanasyev
* ``Name`` (required)
33 7 Weiqi Shi
* ``InterestLifetime`` (optional)
34
* ``MaxInterestNum`` (optional)
35
* ``WatchTimeout`` (optional)
36
* ``WatchStatus`` (required)
37
* ``Selectors`` (optional)
38
* ``ProcessId`` (required only in watchCheck command)
39 1 Weiqi Shi
40 6 Weiqi Shi
41 1 Weiqi Shi
Name is the prefix that will be watched.
42
43 6 Weiqi Shi
InterestLifetime is the maximum latency between interest sent and data received. If the time duration is larger than interest timeout, the same interest will be resent. If data is received within the Interest timeout, the selectors of the interest will be updated and sent to request new data. If it is not specified, a default value(4000 millisecond) will be set. 
44 1 Weiqi Shi
45 6 Weiqi Shi
MaxInterestNum is the maximum of total interests that can be sent. The process will stop if the total number of interests reaches this limit. If it is not specified, MaxInterestNum will be set as -1, means infinity.
46 1 Weiqi Shi
47 6 Weiqi Shi
WatchTimeout is the time duration of this process. Repo will keep watching the prefix until it times out. If it is not specified, WatchTimeout will be set as 0, means this process will run forever.
48 1 Weiqi Shi
49 6 Weiqi Shi
WatchStatus is used to show whether repo is watching a prefix or not. 
50 1 Weiqi Shi
51
ProcessId shows the id number of this command interest, a random number generated by repo.
52
53
Selectors are used to exclude the received data and request new data.
54
55
For watchCheck command interest, only ProcessId is needed.
56
57
### RepoCommandResponse
58
59
This watch status data object could be the response data object of both watch command and watchCheck command. It will follow the format of repo command response.
60
61
Response has three part: ProcessId, indicates an ID of process;  InsertNumber, indicates how many data packets under the watched prefix has been inserted into repo; 
62 2 Weiqi Shi
StatusCode, indicates the status of the process.
63
64
StatusCode Definition:
65
66
``StatusCode`` | Description
67
-------------- | ----------------------------------------------
68
``100``        | The command is OK. Start to watch the prefix
69
``101``        | Watched Prefix Insertion is stop.
70
``300``        | This watched prefix Insertion is in progress
71
``401``        | This watch command or watchCheck command is invalidated
72
``402``        | BlockId present. BlockId is not supported in this protocol
73
``403``        | Malformed Command
74
``404``        | No such this process is in progress
75 3 Weiqi Shi
76
## Protocol Process
77
78
1. Start to validate the command. If it is validated, go to Step 3, otherwise go to Step 2.
79
80
2. Send a negative response indicating validation failure, and abort these steps, process ends (StatusCode: 401).
81
82
3. Check parameters. If it cannot be extracted from interest, send a negative response(StatusCode: 403) and stop process.
83
84
4. If it has BlockId, send a negative response(StatusCode: 402) and stop process.
85
86
5. Use parameter of the command interest to construct interest. Set the Rightmost Child Selector.
87
88
6. Send the interest and start timer. The number of sent interest plus 1(the initial value is 0).
89
90
7. If received a data, go to Step 8, if times out, go to Step 17.
91
92
8. If data is validated, go to Step 9, otherwise, go to Step 15.
93
94
9. Check whether the watched prefix insertion is still running. If it does not, process ends.
95
96
10. If the process times out(exceed watch timeout) or if total number of sent interest reaches limit, go to Step 11, otherwise go to Step 12.
97
98
11. Clear all the variables(the number of sent interest, watch timeout, interest lifetime), abort these steps, process ends.
99
100
12. Store the data into repo.
101
102
13. Update selectors, exclude from min to the received one and use the updated selectors construct new interest. 
103
104
14. Send new interest and the number of sent interest plus 1, and then go to Step 7.
105
106
15. Repeat Step 9 to 11 and skip Step 12.
107
108
16. Update selectors, only exclude the received data(since other data whose name is smaller may be satisfied), then go to Step 14.
109
110
17. Repeat Step 9 to 11 and skip Step 12.
111
112
18. Send the interest again and the number of sent interest plus 1, and then go to Step 7.
113 4 Weiqi Shi
114 8 Weiqi Shi
#### Repo watchCheck command process:
115 4 Weiqi Shi
116
1. Start to validate the check command. If it is validated, go to Step 3, otherwise, go to Step 2.
117
118
2. Send a negative response indicating validation failure, and abort these steps, process ends (StatusCode: 401).
119
120
3. Check parameter. If it cannot extracted from interest or if it does not have processId, send a negative reply(StatusCode: 403).
121
122
4. Check whether the processId is existed. If it does, go to Step 5, otherwise, send a negative reply(StatusCode: 404).
123
124
5. Use the processId to find the response and send the response back.