Changes between Version 7 and Version 8 of ZigbeeGateway

Timestamp:

Sep 19, 2010, 6:40:55 PM (14 years ago)

Author:

Sensei

Comment:

--

ZigbeeGateway

@@ -153 +153 @@
 Zigbee gateway resolves the mobility of a node between several gateways. In the case of Zigbee there is no possibility of storing information in nodes that helps to the mobility. So gateways need to resolve the problem by themselves.
 Figure shows how mobility is resolved by Zigbee gateways. 
-
-**Put figure**
-
-Resource identification formed by the gateway is always the same as depend on node parameters only as MAC address. 
-In that way Resource Directory can be used for knowing if this resource was previously attached to other gateway, and the old URL. 
-No replication of the same resource is found in the Resource Directory. If it exists, it is updated.
-The all gateway is informed about the new location of the resource. In the response, the all gateway sends all the subscription information that these resource had, and these are implemented by the new gateway.
-The all gateway in addition will redirect access this resource to the new URL using the http redirect response. This redirection is transparent to applications.
-The result is that applications do not notice if they do not want that a resource has been moved.
-For optimization, mobility commands interchanged between gateways are not resource by resource, but for all the resources of a node.
+[[Image(zb2senseigw_mobility.jpg, 25%, center)]]
+
+ 
+
+
+1. (and 4.) Resource identification formed by the gateway is always the same independently of the gateway. The identification depends only on node parameters. In our case it is used the MAC address and the sensor number position. When the node connects to a new island, the gateway forms the Resource End Point of the nodes resources.
+2. (and 5.) Previously to publish in the Resource Directory, it discovers if the resource already is present using RLI interface.
+3. If the resource does not exist, it is published into the Resource Directory  … 
+4. see 1
+5. see 2
+6. But if it exists, it is updated. No replication of the same resource is found in the Resource Directory.
+7. The new gateway informs the old gateway about the new location (URL) of the resource. The URL of the old gateway is obtained when getting resource parameters from the Resource Directory (5.) In the response, the old gateway sends all the subscriptions information that this resource has, and these are implemented by the new gateway.
+8. The old gateway in addition will redirect whatever access to this resource to the new URL using the http redirect response. This redirection is transparent to applications.
+The result is that applications do not notice at all (if they do not want) that a resource has been moved.
+
+For optimization, mobility commands interchanged between gateways are not sent resource by resource, but only once for all the resources of a node.
 === Mobility format interchanged between gateways===
 The new gateway informs the all gateway with a PUT http method addressing node id (not resource id) with the following xml content
@@ -208 +214 @@
 A POST http method over the resource URL is used for adding a new subscription. In this case it should be add at the end of the resource URL the subscription identity:  
 "//**BASE_URL/nodeMAC/X/number/SubscriptionID**//"
-* SubscriptionID is whatever text allowed in the URL names. The xml format for a subscription is **(PUT A LINK TO XML SUBSCRIPTION FORMAT)** 
+* SubscriptionID is whatever text allowed in the URL names. The xml format for a subscription is **PUT A LINK TO XML SUBSCRIPTION FORMAT** 
 
 A PUT http method over this subscription URL is used for modify it.