Mechanisms for semantics publishing and discovery

• US 9,792,323 B2
• Filed: 07/02/2014
• Issued: 10/17/2017
• Est. Priority Date: 07/02/2013
• Status: Active Grant

• Current Assignee: Convida Wireless LLC
• Original Assignee: Convida Wireless LLC
• Inventors: Dong, Lijun, Mladin, Catalina M., Seed, Dale N., Lu, Guang
• Primary Examiner(s): Le, Debbie
• Application Number:
  US14/322,509
• Publication Number:
  US 20150012551A1
• Time in Patent Office: 1,203 Days
• Field of Search: None
• CPC Class Codes: G06F 16/245 Query processing
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

Methods, devices, and systems may be used for semantics publishing and discovery. In an embodiment, a method for publishing semantics related resource identifiers may include adding a key word to an identifier of a semantics related resource and publishing the identifier to at least one of a sibling node and a child node. In another embodiment, a method may include using a Bloom filter to publish a semantics related resource. In another embodiment, a method may include publishing, by a semantics node, an identifier of a semantics related resource to a sibling node, while publishing a digest of the semantics node to a child node.

Claims

1. A device used for discovering semantics related resource identifiers, the device comprising:

a processor; and

a memory coupled with the processor, the memory comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising;

receiving a request for a semantics related resource from a requesting device, the request comprising a first keyword;

determining that the requested semantics related resource is not locally stored on the device;

responsive to determining that the requested semantics related resource is not locally stored on the device, matching the first keyword with a second keyword, the second keyword associated with an identifier of the semantics related resource; and

forwarding, to the requesting device, an address of a semantics node contained in the identifier based on the matching of the first keyword with the second keyword, wherein the address comprises URI or URL.

2. The device of claim 1, wherein the identifier further comprises a type.

3. The device of claim 1, wherein the request further comprises a first type associated with the first key word and the address associated with the first keyword.

4. The device of claim 3, further operations comprising:

matching the first type with a second type, the second type associated the second keyword; and

providing instructions to forward the address based on the matching of the first type with the second type and the first keyword with the second keyword.

5. The device of claim 1, further operations comprising:

retrieving the semantics related resource from the semantics node based on the matching of the first keyword with the second keyword.

6. A device comprising:

a processor; and

a memory coupled with the processor, the memory comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising;

sending, to a first semantics node, a request for a desired first semantics related resource, the request comprising a first keyword; and

receiving, from the first semantics node, a response comprising an identifier for a second semantics node that has a second semantics related resource that is associated with a second keyword that matches the first keyword for the desired first semantics related resource;

based on the response comprising the identifier, sending a second request to the second semantics node for the second semantics related resource; and

in response to the another request, receiving the second semantics related resource from the second semantics node.

7. The device of claim 6, wherein the request further comprises a type associated with the first keyword.

8. The device of claim 7, wherein the type is a class, relationship, or term.

9. The device of claim 6, further operations comprising:

validating that the second semantics related resource matches the desired first semantics related resource.

10. The device of claim 9, further operations comprising:

determining that the second semantics related resource does not match the desired first semantics related resource; and

sending a request to the second semantics node for a modification of the received second semantics related resource.

11. The device of claim 9, further operations comprising:

providing instructions to display a status of the request to the second semantics node for the second semantics related resource.

12. The device of claim 9, further operations comprising:

providing instructions to display a status of the validating of the second semantics related resource.