Interworking service for the restful internet of things
An interworking service entity receives server registration requests including indications of service layer protocols used by each server, maintains a repository of server information, and uses the repository for interworking requests of devices to servers of different protocols based on a server type provided in discovery requests. Other matching information may include, for example, server security protocol, supported services, service territory, availability, capacity, or loading, as device information or preferences, such a supported service, supported interface type, or a supported device type.
1. A first entity for a service providing service capabilities to applications through a set of Application Programming Interfaces (APIs), the first entity comprising circuitry configured to:
receive, from a second entity, the second entity being hosted by an IoT device, a first message comprising information regarding the second entity which is to be shared with an IoT server and being sent in a first protocol;
add, to a repository of device information, the information regarding the second entity, the information regarding the second entity being derived from the information of the first message received from the second entity;
select, based on a repository of server information, the repository of device information, and a policy, a third entity, wherein the third entity is compatible with the second entity and is IoT server-hosted;
send, to the third entity selected according to the policy, a second message, the second message being sent in a second protocol and requesting registration at the third entity of the second entity; and
receive, from the third entity, a response to the second message, the response being sent in the second protocol and indicating whether the second entity has been registered at the third entity.
2. The first entity of claim 1 , wherein the first protocol is associated with a first function of the service and the second protocol is associated with a second function of the service, wherein the service is defined as a middleware.
3. The first entity of claim 1 , wherein the first message comprises an indication of a server type.
4. The first entity of claim 1 , wherein the first message comprises an identifier of the third entity.
5. The first entity of claim 1 , wherein the first message comprises an indication of a supported service, a supported interface type, or a supported device type.
6. The first entity of claim 1 , wherein the circuitry further configured to:
receive, from the third entity, a server registration request; and
add, to the repository of server information, information provided in the server registration request.
7. The first entity of claim 6 , wherein the server registration request further comprises an indication of a security protocol, a supported service, or a service territory.
8. The first entity of claim 6 , wherein the server registration request further comprises an indication of an availability, a capacity, or a loading.
9. The first entity of claim 1 , wherein the circuitry further configured to send, to a fourth entity via the second protocol, a device registration request, the device registration request comprising an identifier of the second entity.
10. The first entity of claim 1 , wherein the circuitry further configured to:
receive, from the second entity via the first protocol, a third message, where the third message is intended for a fourth entity;
compose, based on the first message, a fourth message; and
send, to the fourth entity via the second protocol, the fourth message.
11. The first entity of claim 10 , wherein composing the fourth message comprises translating the first message using a mapping table.
12. The first entity of claim 11 , wherein the circuitry further configured to provide a web interface whereby a user may adjust the mapping table.
13. The first entity of claim 10 , wherein composing the fourth message comprises translating the third message using a protocol unit.
14. The first entity of claim 10 , wherein composing the fourth message comprises altering content in accordance with a rule or policy.
15. The first entity of claim 2 , wherein the middleware is defined by an IoT standards and each of the first protocol and the second protocol correspond to one of one M2M, OCF, IETF CORE RD, HyperCAT, W3C WOT and OMALWM2M.
16. A method for a first entity for a service providing service capabilities to applications through a set of Application Programming Interfaces (APIs), the method comprising:
receiving, from a second entity, the second entity being hosted by an IoT device, a first message comprising information regarding the second entity which is to be shared with an IoT server and being sent in a first protocol;
adding, to a repository of device information, the information regarding the second entity, the information regarding the second entity being derived from the information of the first message received from the second entity;
selecting, based on a repository of server information, the repository of device information, and a policy, a third entity, wherein the third entity is compatible with the second entity and is IoT server-hosted;
sending, to the third entity selected according to the policy, a second message, the second message being sent in a second protocol and requesting registration at the third entity of the second entity; and
receiving, from the third entity, a response to the second message, the response being sent in the second protocol and indicating whether the second entity has been registered at the third entity.
17. The method of claim 16 , wherein the first protocol is associated with a first function of the service and the second protocol is associated with a second function of the service, wherein the service is defined as a middleware.
18. The method of claim 17 , wherein the middleware is defined by an IoT standards and each of the first protocol and the second protocol correspond to one of one M2M, OCF, IETF CORE RD, HyperCAT, W3C WoT and OMALWM2M.
19. The method of claim 16 , wherein the method further comprising:
receiving, from the third entity, a server registration request; and
adding, to the repository of server information, information provided in the server registration request.
20. The method of claim 19 , wherein the server registration request further comprises an indication of a security protocol, a supported service, or a service territory.