THING DEVICE BASED ON THING SEARCHING BROWSER, AND MASHUP METHOD BETWEEN THINGS

• US 20150213138A1
• Filed: 01/23/2015
• Published: 07/30/2015
• Est. Priority Date: 01/24/2014
• Status: Abandoned Application

• Current Assignee: Electronics and Telecommunications Research Institute
• Original Assignee: Electronics and Telecommunications Research Institute
• Inventors: PYO, CHEOL SIG, LEE, BYUNG BOG
• Application Number:
  US14/604,095
• Publication Number:
  US 20150213138A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Abstract

A thing device based on a thing searching browser and a mashup method between the thing devices. The smart device according to an exemplary embodiment may include a thing searching browser to search and register a thing; a communications entity manager to provide, through the thing searching browser, an Open Application Programming Interface (Open API) that supports the thing to be searched and connected, and generate a communications entity and a communications entity profile based on the searched thing; and an entity communications channel manager to set a communications channel between the searched thing and the communications entity and transmit and receive data.

Claims

1. A thing device based on a thing searching browser, comprising:

a thing searching browser configured to search and register a thing;

s a communications entity manager configured to provide, through the thing searching browser, an Open Application Programming Interface (Open API) that supports the thing to be searched and connected, and generate a communications entity and a communications entity profile based on the searched thing; and

an entity communications channel manager configured to set a communications channel between the searched thing and the communications entity and transmit and receive data.

2. The thing device of claim 1, wherein the thing searching browser is configured to connect a thing app to the searched thing, wherein the thing app is configured to access the communications entity, set and activate or deactivate the communications path between the thing is and the communications entity, and be programmed using the Open API provided by the communications entity manager so as to acquire, from the communications entity, the data transmitted by the thing.

3. The thing device of claim 1, wherein the communications entity manager is configured to manage the communications entity that is registered after being virtualized and personalized in the thing device, and add an access pointer of the communications entity to a communications entity list, wherein the access pointer is accessible to the communications entity.

4. The thing device of claim 1, wherein the communications entity is an object acquired after a real-world thing is projected in virtual space of the thing device.

5. The thing device of claim 1, wherein the communications entity profile comprises at least one of, with respect to the registered thing:

a thing identifier, a thing name, a communications driver name, a type of communications media, a communications path setting state, a load label of a thing app associated with the thing, and a package name of the thing app.

6. The thing device of claim 1, wherein the entity communications channel manager is configured to add a device object with an identifier and name of the searched object to a list of discoverable device objects by searching surrounding things for each of communications media, wherein the device object is a P2P entity communicating with things, and add an access pointer of the device object to a device object list.

7. The thing device of claim 1, wherein the thing searching browser provides a user interface, which comprises a selection menu for selecting thing communications media by a user, a search menu for requiring a search of the communications entity included in the thing communications media selected by the user through the selection menu, and a list view showing a list of the searched communications entity of the communications entity.

8. A mashup method between things by a thing device, the mashup method comprising:

searching a thing around the thing device through a thing searching browser;

a communications entity manager generating and managing a communications entity and a communications entity profile, which correspond to the searched thing; and

an entity communications channel manager setting a communications channel between the searched thing and the communications entity and activating a communications path.

9. The mashup method of claim 8, wherein the generating and managing of the communications entity and the communications entity profile comprises:

the thing searching browser or a thing app of the thing device calling an Open API provided by the communications entity manager while transmitting, to the communications entity manager, a thing identifier and a communications media type parameter that the thing uses;

the communications entity manager requesting, to the entity communications channel manager, a confirmation of whether a device object of the thing exists in a list of discoverable devices by using the thing identifier and the communications media type;

is in response to the existence of the device object of the thing in the list of discoverable devices, the communications entity manager generating and registering the communications entity and generating an internal message queue with data, received from the thing, to be stored in the communications entity; and

the communications entity manager generating and storing the communications entity profile.

10. The mashup method of claim 9, wherein the generating and managing of the communications entity and the communications entity profile comprises:

in response to no existence of the device object of the thing in the list of discoverable devices, the communications entity manager requesting a search of surrounding things to the entity communications channel manager, updating the list of discoverable devices, and in response to no existence of the device object of the thing in the updated list of discoverable devices, handling a request for a thing personalization to failure.

11. The mashup method of claim 8, wherein the setting of the communications channel, and the activating of the communications path comprise:

a thing app calling an Open API for setting a communications channel for data exchange while transmitting a thing identifier and a communications media type parameter to the communications entity manager, wherein the Open API is provided by the communications entity manager;

the communications entity manager searching the communications entity with a is same as the transmitted thing identifier in a communications entity list that is managed by the communications entity manager;

the communications entity manager requesting a setting of the communications channel between the searched communications entity and the thing to the entity communications channel manager; and

the entity communications channel manager updating a communications path setting state of the communications entity profile into a ‘

connected’

state.

12. The mashup method of claim 8, wherein the setting of the communications channel, and the activating of the communications path comprise:

a thing app calling an Open API for commanding the communications path to be activated while transmitting a thing identifier and a data parameter to the communications entity manager, wherein the Open API is provided by the communications entity manager;

the communications entity manager searching the communications entity with a same as the transmitted thing identifier in a communications entity list managed by the communications entity manager;

the communications entity manager requesting activation of the communications path between the searched communications entity and the thing to the entity communications channel manager; and

in response to the communications path being activated by the entity communications channel manager, beginning to store data transmitted by the thing in an internal message queue of the communications entity.

13. The mashup method of claim 8, comprising:

receiving data from the thing corresponding to the generated communications entity.

14. The mashup method of claim 13, wherein the receiving of the data comprises:

a thing app calling an Open API for receiving data provided by the communications entity manager while transmitting a thing identifier and a data parameter to the communications entity manager;

the communications entity manager searching the communications entity with a same as the transmitted thing identifier in a communications entity list managed by the communications entity manager; and

the entity communications channel manager transferring data to a thing app from a message queue of the communications entity.

15. The mashup method of claim 8, comprising:

transmitting data to the thing corresponding to the generated communications entity.

16. The mashup method of claim 15, wherein the transmitting of the data comprises:

a thing app calling an Open API for transmitting data provided by the communications entity manager while transmitting a thing identifier and a data parameter to the communications entity manager;

the communications entity manager searching the communications entity with a same as the transmitted thing identifier in a communications entity list managed by the communications entity manager; and

transmitting the data to the thing through the entity communications channel manager used by the searched communications entity.

17. A thing mashup method between thing devices, comprising:

a first thing device searching a second thing device and generating a second communications entity and a second communications entity profile in the first thing device;

the first thing device setting and activating a communications path between a second communications entity, generated in the first thing device, and the second thing device; and

transmitting and receiving data through the activated communications path.

18. The thing mashup method of claim 17, wherein the transmitting and receiving of the data comprises:

in response to the first thing device requesting information of a communications entity profile to the second thing device in response to the activation of the communications path, wherein the information is regarding things personalized by the second thing device, the second thing device inputting the communications entity profile to a queue of the second communications entity in the first thing device, and the first thing device selecting, by a user, an interest thing from the communications entity profile that is read from the queue of the second communications entity; and

in response to the first thing device notifying the selected thing to the second thing device, the second thing device setting and activating the communications channel connected to the selected thing.

19. The thing mashup method of claim 18, wherein the transmitting and receiving of the data comprises:

in response to data being transferred from the thing selected by the user to a queue of a communications entity associated with the selected thing in the second thing device, the second thing device reading the data from the queue of the communications entity associated with the selected thing and inputting the data to the queue of the second communications entity in the first thing device; and

the first thing device reading the data from the queue of the second communications entity.