Abstract: A method for an intermediary node to reduce a number of server-client sessions between a server (104) and a plurality of clients (102a, 102b, 102c) communicably connected to the server (104) over a network is disclosed. The intermediary node (106) intercepts a first request and a second request destined to the server (104) from a first client (102a; 102b; 102c) and a second client (102a; 102b; 102c). The intermediary node (106) establishes a server-client session, between the intermediary node (106) and the server (104), using the first request. If the first request overlaps in part with the second request and if a part of the second request is not overlapping with the first request, the intermediary node (106) updates the server-client session between the intermediary node (106) and the server (104) to include a part of the second request.

Abstract: A method for binding a first and second devices is disclosed. The method is implemented using the architectural principles of REST, which allows a binding initiator to directly contact the first device and instruct the device of actions to be taken. Specifically, the binding initiator may contact the first device by providing a first REST request to the device, the request specifying that the first device is to monitor a state of a particular REST resource identified by the request and is to trigger the second device to perform a specified action when the state of that REST resource satisfies a particular condition. Using REST further allows the first device to directly contact the second device and instruct the second device to perform the specified action. Since the first device is now able to directly contact the second device, these two devices may be considered to be bound.

Abstract: A method for enabling restoration of an operational state on a server node is disclosed. The method includes intercepting, by a state directory, traffic between the server node and a client communicably connected to the server node over a network to derive the operational state. At least a part of the traffic between the server node and the client leads to establishment of the operational state on the server node. The method further includes storing the operational state in the state directory, detecting, by the state directory, that the server node has lost the operational state, and providing, by the state directory, the operational state to the server node after detecting that the server node has lost the operational state.

Abstract: A method for creating a profile for accessing or manipulating resources across a plurality of nodes in a network is disclosed. An entity manager receives a request from a client to create a profile, and preferably validates the request. The entity manager generates said profile and the profile is addressable by a profile identifier. A client may use the profile to interact with the resources across the plurality of nodes using the profile identifier.

Abstract: A method for binding a first and second devices is disclosed. The method is implemented using the architectural principles of REST, which allows a binding initiator to directly contact the first device and instruct the device of actions to be taken. Specifically, the binding initiator may contact the first device by providing a first REST request to the device, the request specifying that the first device is to monitor a state of a particular REST resource identified by the request and is to trigger the second device to perform a specified action when the state of that REST resource satisfies a particular condition. Using REST further allows the first device to directly contact the second device and instruct the second device to perform the specified action. Since the first device is now able to directly contact the second device, these two devices may be considered to be bound.

Abstract: A method for binding a first and second devices is disclosed. The method is implemented using the architectural principles of REST, which allows a binding initiator to directly contact the first device and instruct the device of actions to be taken. Specifically, the binding initiator may contact the first device by providing a first REST request to the device, the request specifying that the first device is to monitor a state of a particular REST resource identified by the request and is to trigger the second device to perform a specified action when the state of that REST resource satisfies a particular condition. Using REST further allows the first device to directly contact the second device and instruct the second device to perform the specified action. Since the first device is now able to directly contact the second device, these two devices may be considered to be bound.

Abstract: A method for binding a first and second devices is disclosed. The method is implemented using the architectural principles of REST, which allows a binding initiator to directly contact the first device and instruct the device of actions to be taken. Specifically, the binding initiator may contact the first device by providing a first REST request to the device, the request specifying that the first device is to monitor a state of a particular REST resource identified by the request and is to trigger the second device to perform a specified action when the state of that REST resource satisfies a particular condition. Using REST further allows the first device to directly contact the second device and instruct the second device to perform the specified action. Since the first device is now able to directly contact the second device, these two devices may be considered to be bound.

Abstract: A method for enabling restoration of an operational state on a server node is disclosed. The method includes intercepting, by a state directory, traffic between the server node and a client communicably connected to the server node over a network to derive the operational state. At least a part of the traffic between the server node and the client leads to establishment of the operational state on the server node. The method further includes storing the operational state in the state directory, detecting, by the state directory, that the server node has lost the operational state, and providing, by the state directory, the operational state to the server node after detecting that the server node has lost the operational state.

Abstract: A method for an intermediary node to reduce a number of server-client sessions between a server (104) and a plurality of clients (102a, 102b, 102c) communicably connected to the server (104) over a network is disclosed. The intermediary node (106) intercepts a first request and a second request destined to the server (104) from a first client (102a; 102b; 102c) and a second client (102a; 102b; 102c). The intermediary node (106) establishes a server-client session, between the intermediary node (106) and the server (104), using the first request. If the first request overlaps in part with the second request and if a part of the second request is not overlapping with the first request, the intermediary node (106) updates the server-client session between the intermediary node (106) and the server (104) to include a part of the second request.

Abstract: To alleviate constrained nodes (102a-e) from implementing a functionality, a functionality is emulated by an intermediary node (110) for the constrained nodes (102a-e). The intermediary node is configured to intercept requests and process the requests on behalf of the node to fulfill a functionality. The functionality is typically not supported by the constrained node (102a-e). The support for the functionality is added to resource discovery responses, resource announcement messages, and/or resource registration messages to indicate to a client or a resource directory that the emulated functionality is supported by the node.

Abstract: A method for creating a profile for accessing or manipulating resources across a plurality of nodes in a network is disclosed. An entity manager receives a request from a client to create a profile, and preferably validates the request. The entity manager generates said profile and the profile is addressable by a profile identifier. A client may use the profile to interact with the resources across the plurality of nodes using the profile identifier.