KR102000234B1 - Apparatus for providing home network service and method thereof - Google Patents

Abstract

The present invention relates to an apparatus and a method for providing a home network service, and in particular, to an apparatus and method for providing a home network service. Receiving a first registration message for registering an electronic device from a proxy; Sending a second registration message for electronic device registration to the proxy; And receiving a third registration message for electronic device registration from the proxy.

Description

[0001] APPARATUS FOR PROVIDING HOME NETWORK SERVICE AND METHOD THEREOF [0002]

The present invention relates to an apparatus and a method for providing a home network service, and more particularly, to an apparatus and method for providing a home network service in which devices having a web interface are connected to the Internet to provide various services to users will be.

With the recent use of Wi-Fi technology, home electronic devices such as refrigerators, washing machines, and rice cookers are expected to provide various services to users through a Wi-Fi interface. It is a hypertext transfer protocol (HTTP) web protocol that is considered as an optimal solution for providing such services. Since it is based on transmission control protocol (TCP), it can not be used for general microcontroller unit (MCU) There is a group. To solve these problems, the IETF CORE (Constrained RESTful Environments) working group standardized the CoAP (constrained application protocol), a lightweight web-based protocol. However, since the CoAP protocol is based on UDP (user datagram protocol), there is a problem of reliability of message delivery in the Internet environment. To this end, IETF CORE proposes a model using CoAP in the local network and HTTP in the Internet network .

Meanwhile, efforts have been made to provide a network service to users by connecting various home electronic devices to the Internet, but it is not easy to initialize such as connecting and registering an electronic device to the Internet to a user who is not familiar with the Internet or an electronic device . To this end, middleware protocol technology for various device control and management has been developed, but there is a problem that its utilization is limited due to complexity of network environment and implementation complexity.

The present invention relates to an apparatus and a method for providing a home network service using a home electronic device.

The present invention also relates to an apparatus and method for providing a home network service based on a Restful Web service.

In addition, the present invention relates to an apparatus and method for providing a home network service that can easily configure a home electronic device based on a Restful Web service.

In order to accomplish the objects of the present invention as described above and achieve the characteristic effects of the present invention described below, the characteristic structure of the present invention is as follows.

According to an embodiment, a method for providing a home network service, the method comprising: transmitting an advertisement message to a proxy; Receiving a first registration message for registration of an electronic device from the proxy; Transmitting a second registration message for registering the electronic device to the proxy; And receiving a third registration message for registration of the electronic device from the proxy.

A method for providing a home network service, the method comprising: receiving an advertisement message from an electronic device; Transmitting a first registration message for registering the electronic device to the electronic device; Receiving a second registration message for registration of the electronic device from the electronic device; Transmitting a third registration message for registration of the electronic device to the electronic device; And transmitting a fourth registration message for registering the electronic device to the server.

A method for providing a home network service, according to an embodiment, comprising: receiving a fourth registration message for registration of an electronic device from a proxy; Transmitting a fifth registration message for registering the electronic device to the terminal; And transmitting a sixth registration message for registering the electronic device to the proxy.

A method for providing a home network service, the method comprising: receiving an advertisement message from an electronic device; Transmitting an advertisement message to the electronic device; And receiving a fifth registration message for registering the electronic device from the server.

According to another embodiment, there is provided a method for providing a home network service, wherein the advertisement message uses a binary protocol and includes at least one of a protocol version, a message type, a URI length, a URI of an electronic device, And may include at least one.

According to another embodiment of the present invention, there is provided a method for providing a home network service, the method comprising the steps of receiving an advertisement message, and transmitting an advertisement message informing the server that the advertisement message is received, Includes a URI for message delivery, a Restful message format (Method), and a request to be delivered, the request including an external URI mapping an electronic device at the proxy, And information regarding the presence of the user.

According to another embodiment of the present invention, there is provided a method for providing a home network service, the method including transmitting a request message for requesting discovery information to the server, the request message including a URI for message delivery, A response to the request, the response may include at least one of an external URI mapping the electronic device at the proxy, information about whether the electronic device is registered in the proxy, .

A method for providing a home network service according to another embodiment, wherein the first registration message, the second registration message, and the third registration message use a CoAP protocol, and the message type (Message Type), a Restful message format (Method), a URI relating to serial code and user information and registration status update, a payload including information about whether or not the electronic device is registered, a serial code and user information of the electronic device, And an ACK including information on the result of the execution.

A method for providing a home network service, according to another embodiment, wherein the fourth registration message includes at least one of a URI for message delivery, a response message format, and a response to the request message, An external URI mapping the electronic device, a unique code of the electronic device, a user ID, a user password, and a user telephone number.

According to another embodiment, a method for providing a home network service, wherein the fifth registration message uses a binary protocol and may include at least one of a protocol version, a message type, a URI length, and a URI of an electronic device .

According to another embodiment, there is provided a method for providing a home network service, the method further comprising transmitting to the electronic device an information message for requesting information about the electronic device, A Message Type, a Restful message format, a URI regarding the information of the electronic device, and an ACK including information about the electronic device.

According to another embodiment, there is provided a method for providing a home network service, comprising: transmitting an information message for requesting information about the electronic device to the proxy; Further comprising transmitting an information message for transmitting information on the electronic device to the terminal, wherein the information message includes at least one of a URI for message delivery, a Restful message format, a Request to be delivered, And a response.

A method for providing a home network service according to another embodiment, the method further comprising transmitting an event message to the proxy, wherein the event message uses a binary protocol and includes a protocol version, a message type, a URI length, And a URI related to an Internet address for managing event information.

According to another embodiment of the present invention, there is provided a method for providing a home network service, the method including transmitting an event message to the electronic device, wherein the event message uses a binary protocol or a CoAP protocol, At least one of an ACK including a length, a URI relating to an intuitive address for managing event information, a message type relating to whether or not the message is a confirmation message, a Restful message format (Method) . ≪ / RTI >

According to another embodiment, there is provided a method for providing a home network service, the method comprising: receiving an event message from the procedure; The method of claim 1, further comprising the step of receiving an event message from the terminal, wherein the event message includes at least one of a URI related to an Internet address, a Restful message format, a request to be delivered, and a response to a request message And the request and the method may include an event name and an event value.

According to another embodiment of the present invention, there is provided a method for providing a home network service, the method comprising: receiving an application message for performing a function of the electronic device from the terminal; And transmitting an application message for performing the function of the electronic device to the proxy, wherein the application message includes a URI related to an Internet address, a Restful message format, a request to be delivered, and a request message The response includes at least one of a URI for downloading the firmware, a firmware version to be rolled back, an SSID to be connected, a password for the SSID to be connected, One can be included.

According to another embodiment of the present invention, there is provided a method for providing a home network service, the method including the step of transmitting an application message for performing a function to the electronic device, the application message using a CoAP protocol, A Message Type, a Restful message format, a URI regarding the Internet address of the application, a payload including information on the applied function, and an ACK for a response.

According to another embodiment, there is provided a method for providing a home network service, the method including receiving an application message for performing a function from the electronic device, the application message using a binary protocol, Type, URI length, URI of the application's Internet address, and information about the application result.

The present invention can easily configure a home electronic device based on a Restful Web service in providing a home network service. Accordingly, convenience for the user can be provided, and the manufacturers of the home electronic device can easily perform the technology development.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a diagram showing a configuration of a home network system according to an embodiment of the present invention; FIG.
2 is a diagram for explaining a message type used in a home network system according to an embodiment of the present invention;
3 is a flowchart illustrating an initial setting method of a home network system according to an embodiment of the present invention.
4A to 4D illustrate a message structure used in a home network system according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

1 is a diagram illustrating a configuration of a home network system according to an embodiment of the present invention.

Referring to FIG. 1, the home network system of the present invention includes a WoT consumer appliance 100, a WoT proxy 110, a cloud server 120, and a smart terminal 130.

A web of things (hereinafter referred to as " web of things ") 100 (hereinafter referred to as an electronic apparatus) may be a refrigerator, a washing machine, a rice cooker, or the like. The electronic device 100 may include a web software (CoAP) 156 for supporting web connectivity and a middleware 153 and an application 150 for device control and management. have.

The middleware 153 may include a lightweight protocol called Binary to overcome the shortcomings of the web software (CoAP) 156, which is a unidirectional message delivery of the server / client architecture. The middleware 153 and the web application software 156 may be located on an embedded OS (RTOS) 159 including a wireless LAN standard 802.11 and a UDP stack for transmitting data based on IP.

The WoT proxy 110 (hereinafter referred to as a proxy) is a gateway for connecting a home network and a home Internet network. The proxy 110 includes a CoAP library 169 for communication with the electronic device 100, a middleware 163 for device management, and an HTTP based micro web server / client (MWS / C) < / RTI > In addition, the WoT proxy module 160 may include a WoT proxy module 160 for delivering a HTTP-based message to the electronic device 100 using the CoAP protocol. And forwarding the message to the external service node based on HTTP. At this time, the proxy platform can use any operating system that can accommodate UDP and TCP protocols for transmitting data based on IP.

The cloud server 120 (hereinafter referred to as a server) communicates with the proxy 110 and can provide an open application program interface (API). A Web server / client 173 and an application service (WoT service) 173 that can monitor and manage the electronic device 100 based on HTTP through the Internet network and can provide the function as an open API, (Not shown). The server platform can use any operating system that can accommodate the TCP protocol based on the IP, and HTTP, which is a general Web communication protocol, must be available to the upper layer of the TCP protocol.

The smart terminal 130 (hereinafter referred to as a terminal) allows a user to monitor and control the electronic device 100 using an open API. The terminal 130 monitors and controls the CoAP library 190 for communication of the electronic device 100 and the middleware 189 and the electronic device 100 for supporting the initial setting and access control functions of the electronic device 100, And a Web client 183 for open API support. The Smart Device Platform can use any operating system that can accommodate UDP and TCP protocols that transmit data based on IP, and use HTTP (186), a general communication protocol on the TCP protocol stack. Above the UDP protocol stack, Web software (CoAP) 190 and middleware 189 can be located.

2 is a diagram for explaining a message type used in a home network system according to an embodiment of the present invention.

2, a CoAP-based binary type message is used between the electronic device 100 and the proxy 110, and HTTP is used between the proxy 110 and the server 120 and the terminal 130 You can use messages in the form of Json (javascript standard object notation).

The middleware protocol used in the present invention defines a URI, a method (Get, Put, Delete, Post) and a Payload using a Restful-based CoAP protocol and an HTTP protocol. The server 120 actively A simple binary protocol for UDP broadcasting can be included to solve the constraint of the CoAP protocol of the server / client structure that can not be delivered. In this case, the method is used for discovery, advertisement, authentication, etc., and get is used for discovery, registration, information, event, and the like in the case of advertisement, discovery, registration, information, event, control and authentication. In WoT CE 100, various protocols such as MQ Telet Transport For Sensors (MQTT-S), which is a protocol for inter-machine communication, may be used.

3 is a flowchart illustrating an initial setting method of a home network system according to an embodiment of the present invention.

3, the user creates an account (300) in the server 120 using the terminal 130. At this time, the user downloads the application using the QR code or the NFC function in the electronic device 100 The user ID (ID), password, user telephone number information, and the like can be registered in the server 120.

In addition, the electronic device 100 generates a unique SSID (Service Set Identifier) when the initial power is turned on, and operates in a software AP (access point) mode (303). The terminal 130 receives the SSID of the electronic device 100 and connects to the electronic device 100. At this time, the electronic device 100 transmits the advertisement message to the terminal 130 (305) The advertisement message is transmitted to the electronic device 100 (310). The terminal 130 can know the SSID of the electronic device 100 in advance, and can use the password as needed.

After the terminal 130 and the electronic device 100 have connected to each other, information for initial setting is transmitted and received (315, 320). For example, the information for the initial setting includes the unique code of the electronic device 100, the SSID of the proxy 110, A password, an ID and password registered in the server 120 by the terminal 130, and the terminal 130 information. The SSID and the password of the proxy 110 are transmitted to the electronic device 100 by the terminal 130. For example, the user can input the SSID and the password of the proxy 110 through the application of the terminal 130 The input information may be transmitted to the middleware of the electronic device 100 through the middleware of the terminal 130. [

When the terminal 130 and the electronic device 100 transmit and receive the initial setting information, the terminal 130 and the electronic device 100 access the proxy 110 using the SSID and the password of the proxy 110 (325, 330) The terminal 130 accesses the server 120 through the proxy 110 (333). At this time, when the proxy 110 transmits an advertisement message to the electronic device 100 (335), the electronic device 100 transmits the advertisement message to the proxy 110 (340).

The proxy 110 checks whether the electronic device 100 is registered with the proxy 110. If the electronic device 100 is not registered, the proxy 110 requests the electronic device 100 for registration information 343, When information for registration is transmitted (345), the electronic device 100 is registered (347). In this case, for example, the registration information includes an ID and a password registered in the server 120 by the terminal 130, information of the terminal 130, and a unique code of the electronic device 100.

The proxy 110 registers the electronic device 100 and sends 350 a registration status update message to the electronic device 100 and the electronic device 100 sends a response message to the proxy 110 ). The proxy 110 also requests registration of the electronic device 100 to the server 120 and sends 360 the information for registration and the server 120 completes the registration of the electronic device 100 The server 120 may send a message regarding the registration of the new device informing the terminal 130 that the electronic device 100 is registered with the server 120. In this case, (365). Upon receiving the registration completion message from the server 120, the proxy 110 requests the electronic device 100 to update the registration status 375, and the electronic device 100 transmits a response message to the proxy 110 (380). When the proxy 110 receives the response to the registration status update from the electronic device 100, the proxy 110 transmits a message regarding the registration of the new device informing the terminal 120 that the electronic device 100 is registered to the server 120 , Which can be used when the server 120 has not transmitted a message regarding the registration of a new device to the terminal 130.

Meanwhile, the terminal 130 transmits information for user authentication to the server 120 (step 385), and the server 120 completes the server authentication using the information for user authentication received from the terminal 130 391). The server 120 transmits the information for user authentication received from the terminal 130 to the proxy 110 in step 390 and the proxy 110 completes the authentication in step 393 and sends an authentication completion message The server 120 transmits the authentication completion message to the terminal 130 (399), and the server 120 transmits the authentication completion message to the terminal 130 (399). At this time, the information for user authentication is, for example, a unique code of the electronic device 100, a user ID and a password.

4A and 4B are views for explaining a message structure used in a home network system according to an embodiment of the present invention.

 The middleware protocol used in the present invention may include a CoAP protocol and a binary protocol. Referring to FIG. 4A, a binary protocol includes a protocol version 400, a message type 405, ) 410, a URI 415, and a payload 445, and a description thereof is shown in Table 1.

Field Name Field Size (Byte) Description Version One - Protocol version
0x01 Message Type One - Message function
· 0x01: Advertisement
0x02: Discovery
0x03: Event Notification
0x04: Apply Complete
0x05: New Device Added
0x06: Authentication Complete URI Length 2 - Size of URI string (Byte) URI N - Different technologies for different devices and functions Payload One - Different technology for each message type

The ADVERTISEMENT message is a message informing the proxy 110 or other device connected to the network of its URI information or registration information when a predetermined device is connected to the network for the first time or powered on.

In one example, between the electronic device 100 and the proxy 110, the advertisement message uses only the binary protocol without using the CoAP protocol, wherein the advertisement message structure includes a version 425, a message type 430 ), A URI length 435, a URI 440, and a Registration 445.

Field Name Field Size (Byte) Description Version One - Protocol version: 0x01 Message Type One - Advertisement: 0x01 URI Length 2 - Size of URI string (Byte) URI N - the electronic device or proxy or the terminal's own URI (IP Address) Registration One - Whether the proxy and the server have electronic devices registered or not
0x00: Not Registered
0x01: Registered in Proxy
0x11: Registered in Cloud Server
0x12: Registered in Cloud Server but IP
address Changed

The middleware of the electronic device 100 has IP information and updates the value of v {1} / config / registration to 0x12 when its IP changes at boot time. The registration field of the binary message at the time of advertisement is broadcasted at 0x12 and the proxy 110 middleware reads the serial code from the electronic device 100 when the registration field value is 0x12 ), The proxy 110 middleware changes the device's v {1} / config / registration value back to 0x11 (put v {1} / config / registration).

Also, between the proxy 110 and the server 120, when the proxy 110 receives the advertisement message from the electronic device 100, the proxy 110 notifies the server 120 of an advertisement Message can be transmitted. For example, the structure and related contents of the advertisement message are shown in [Table 3] and [Table 4].

URI Method Request Response
(200 OK) Error Members Value Required Members Value Required {serverId} / v {1} / advertisement PUT advertisement AdvInfo
(Object Array) true 400,500 Note the error message

'URI' is the Internet address for message delivery, 'Method' is the format of the Restful message, 'Requst' is the message to deliver, 'Members' is the details of the message to be delivered, 'Value' Is an actual value, and 'Required' indicates whether or not it is a mandatory item. '{ServerId} / v {1} / advertisement' is the address of the cloud server to which the advertisement message is transmitted, 'AdvInfo (Object Array)' is the contents necessary for the advertisement, and 'true' If 'put' is described in 'Method', the related content is described in 'Request'.

Object Name Members Type Description AdvInfo uri string The external URI (deviceId) that is mapping the electronic device in the proxy.
ex) 129.254.86.142/a registration hex Whether an electronic device is registered with the proxy
0x00: Not Registered
0x01: Registered in Proxy
0x11: Registered in Proxy and
CloudServer

'Object' is the name of the 'Request Value', 'Members' is the details of the 'Object Name', 'type' is the data type of 'Member' values, 'AdvInfo' is the request value for the advertisement, 'Is a string, and' hex 'is hexadecimal notation.

The Json type advertisement message is as follows.

{

"advertisement": [

{

"uri": "129.254.86.142/a/",

"Registration": 00

                },

{

"uri": "129.254.86.142/b/",

"Registration": 01

                }

                ]

}

On the other hand, the DISCOVERY message is for confirming the existence of a predetermined device connected to the network, and the device receiving the discovery message can reply by transmitting an advertisement message. The terminal 130 periodically polls and the server 120 stores advertisement message information. For example, between the terminal 130 and the server 120, the terminal 130 can read the discovery information from the server 120, and in order to do so, the server 120 must store the device advertisement information. For example, the discovery message structure and related contents are shown in [Table 5] and [Table 6].

URI Method Request Response
(200 OK) Error Members Value Required Members Value Required {serverId} / v {1} / {userId} / discovery
(Request Discovery Information) GET discovery DisInfo
(Object Array) true 400,500 Note the error message

'URI' is the Internet address for message delivery, 'Method' is the format of the Restful message, 'Response' is the response to the request message, 'Members' is the details of the response message, 'Value' 'Required' is a required value. 'DisInfo (Object Array)' is necessary for discovery and 'true' is a mandatory item. 'Discovery' is the address of the cloud server to request discovery message. to be. If 'GET' is listed in 'Method', the related content is described in 'Response'.

Object Name Members Type Description disInfo uri string An external URI (deviceId) that maps proxy-managed electronic device URIs in the cloud. registration hex Whether an electronic device is registered with the proxy
0x00: Not Registered
0x01: Registered in Proxy
0x11: Registered in Proxy and Cloud Server

'Type' is a data type of 'Member' values, 'disInfo' is a response value to a discovery request, 'string' is a string value of 'response' 'Is a string, and' hex 'is hexadecimal notation.

The Json type discovery message is as follows.

{

"discovery": [

{

"uri": "111.245.11.10/v1/129.254.86.142/a/",

"Registration": 11

},

{

"uri": "111.245.11.10/v1/129.254.86.142/b/",

"Registration": 11

}

            ]

}

Between the server 120 and the proxy 110, the proxy 110 may send an advertisement message to the server 120, and after receiving the advertisement message, the server 120 receives v {1} / {userId} / discovery Update the information. Refer to [Table 3] and [Table 4] for the structure and related explanation of the discovery message at this time.

Further, between the proxy 110 and the electronic device 100, the proxy 110 may send a discovery message to the electronic device 100, and the electronic device 100 responds with an advertisement message upon receipt of the discovery message. At this time, the discovery message does not use the CoAP protocol but uses only the binary protocol. Referring to FIG. 4C, the discovery message comprises a version 450, a message type 455, a URI length 460, and a URI 465, the description of which is shown in Table 7.

Field Name Field Size Description Version One - Protocol version: 0x01 Message Type One - Device Discovery: 0x02 URI Length 2 - Size of URI string (Byte) URI N - URI of device requesting discovery (IP address of Proxy)

On the other hand, the REGISTRATION message is a message for registering the electronic device 100 with the proxy 110 and the server 120.

For example, when receiving the advertisement message of the electronic device 100 at the proxy 110 between the electronic device 100 and the proxy 110, if the Registration field value of the payload is 0x00, the proxy 110 transmits a CoAP Message, and updates the registration state of the electronic device 100 when the registration is completed in the proxy 110. [ At this time, the registration message uses the CoAP protocol, and the message structure and related contents are shown in [Table 8].

Field Name Field Size Description Client (Proxy) Message Type Use CON, confirmable message Method - Use GET to read serial code and user information
- Use PUT to update the registration status of electronic devices URI Serial code v {1} / config / serial User information v {1} / config / user Update registration status v {1} / config / registration Payload Renew your registration - When registering with proxy (when using PUT method) "0x01" is used
- When registering with the server (when using the PUT method), use "0x11" Server (Device) ACK - Serial code: Device specific serial code (32Bytes text) - User information: User information received from application etc. (48 bytes text)
- ID (16 bytes)
- Password (16Bytes)
- Phone Number (16Bytes) - renewal of registration
· 200 (OK) response SHOULD be returned
If no resource exists then the server MAY create a new resource with that URI, resulting in a 201 (Created) response
If the resource could not be created or modified, then an appropriate error response code SHOULD be sent.

'ACK (acknowledge)' indicates that the proxy 110 transmits a 'GET' message to the proxy 110, 'Server (Device)' is a message used by the electronic device 100, 'Client (Proxy)' is a message used by the proxy 110, Or a " PUT " request to the electronic device 100. [

Also, between the proxy 110 and the server 120, when the electronic device 100 is registered with the proxy 110, the proxy 110 registers the external URI (ID) with the 'URI' of the electronic device 100, 'And transmits the inherent code and' URI 'information of the electronic device 100 to the service node. The structure of the registration message and related contents are shown in [Table 9] and [Table 10]. In Table 10, 'RegReqInfo' is a value for registration request.

URI Method Request Response
(200 OK) Error Members Value Required Members Value Required {serverId} / v {1} / config /
registration
(registration request) PUT registrationReq RegReqInfo
(Object) true 400,500 Note the error message

Object Name Members Type Description RegReqInfo uri string The external URI (deviceId) mapping the internal device in the proxy serialCode string Unique code of WoT device id string User ID password string User Password phone string User phone number

The Json-type registration message is as follows.

# Registration Request

{

"registrationReq": {

"uri": "129.554.55.12/a",

"serialCode": "56543dswdfs-0ri0",

"id": "etri",

"password": "123456",

"phone": "01111112222"

}

}

Between the proxy 110 and the terminal 130, when the registration of the electronic device 100 to the server 120 is completed and the registration result is transmitted to the electronic device 100, the proxy 110 transmits a broadcast message The terminal 130 can be notified that the registration of the electronic device 100 is completed. At this time, the registration message uses only the binary protocol. Referring to FIG. 4C, the registration message is composed of a version 450, a message type 455, a URI length 460, and a URI 465, and a description thereof is shown in [Table 11].

Field Name Field Size Description Version One - Protocol version: 0x01 Message Type One - New Device Added: 0x05 URI Length 2 - Size of URI string (Byte) URI N - URI of the registered device (URI managed by the proxy)

When the server 120 directly informs the terminal 130 that registration of the electronic device 100 is completed, a Json-type message can be used. In this case, uri is the external URI (external URI) of the registered electronic device 100, serialCode is the serial code of the registered electronic device 100, id is the user ID registered with the registered electronic device 100, The password is a user password for registering the registered electronic device 100.

The Json-type registration message is as follows.

{

"NewDevice": {

"uri": "129.254.86.142/device0",

"serialCode": "1234r3-r3r3klnff",

"id": "test",

"password": "test" /

}

}

On the other hand, an INFORMATION message is used to request information about the electronic device 100, and the information about the electronic device 100 includes a name, a type, a model name, a manufacturer name, a hardware (H / W) And a firmware version.

For example, between the terminal 130 and the server 120, the terminal 130 can request information about the electronic device 100 from the server 120 and receive information by 'Ack' (120) registers information on the electronic device (100). At this time, the structure of the information message and the description thereof are shown in [Table 12] and [Table 13]. In Table 12, 'informationRes' is the response value for the device information request.

URI Method Request Response
(200 OK) Error Members Value Required Members Value Required {serverId} / v {1} / {deviceId} / info GET informationRes DeviceInfo
(Object
Array) true 400,500 Note the error message

Object Name Members Type Description DeviceInfo deviceName string Device Name deviceType hex Device type modelName string Model name manufacturer string Manufacturer name serverURI string Service server URI hwVersion string H / W version firmwareVersion string Firmware version

The Json type information message is as follows.

# Information Response

{

"informationRes": [

{

"deviceName": "test",

"deviceType": 1600,

"modelName": "test",

"manufacturer": "test",

"serverURI": "122.11.5.5",

"hwVersion": "1.1.1",

"firmwareVersion": "1.1.2"

}

]

}

Also, between the server 120 and the proxy 110, the server 120 may send an information message requesting information to the proxy 110, wherein the information message uses the HTTP protocol. The structure of the information message and the description thereof are shown in [Table 14] and [Table 15].

URI Method Request Response
(200 OK) Error Members Value Required Members Value Required {serverId} / v {1} / {deviceId} / info PUT informationRes DeviceInfo
(Object
Array) true 400,500 Note the error message

Object Name Members Type Description DeviceInfo deviceName string Device Name deviceType hex Device type (see Annex A) modelName string Model name manufacturer string Manufacturer name serverURI string Service server URI hwVersion string H / W version firmwareVersion string Firmware version

The Json type information message is as follows.

# Information Response

{

"informationRes": [

{

"deviceName": "test",

"deviceType": 1600,

"modelName": "test",

"manufacturer": "test",

"serverURI": "122.11.5.5",

"hwVersion": "1.1.1",

"firmwareVersion": "1.1.2"

}

]

}

Between the proxy 110 and the electronic device 100, the proxy 110 may request information from the electronic device 100, and upon receiving an information message requesting information from the server 120, To the electronic device (100). The information message used between the proxy 110 and the electronic device 100 uses the CoAP protocol, and the structure of the information message and the description thereof are shown in Table 16. In Table 16, the message type relates to whether it is a 'CON' message requiring a response or a 'NON' message not requiring a response.

Field Name Field Size Description Client (Proxy) Message Type - Use CON, confirmable message Method - Use GET to read electronic device information URI - Device name: IP address / device / info / name
- Device type: IP address / device / info / type
- Model name: IP address / device / info / model
- Manufacturer name: IP address / device / info / manufacturer
- Service server URI: IP address / device / info / serveruri
- H / W version: IP address / device / info / hwversion
- Firmware version: IP address / device / info / fwversion Server (Device) ACK - Device name: 16Bytes String
- Device type: 2 Bytes Hexcode (see Annex A)
- Model Name: 16Bytes String
- Manufacturer name: 16Bytes String
- Service server URI: 32Bytes String
- H / W version: 16Bytes String
- Firmware version: 16Bytes String

Meanwhile, the EVENT_NOTIFICATION message is used to transmit related information when a specific event such as a sensor is periodically generated.

For example, when an event occurs in the electronic device 100 between the electronic device 100 and the proxy 110, the proxy 110 notifies the proxy 110 of the occurrence of the event through a broadcast, The event value can be known from the event URI. At this time, the event notification message uses a binary protocol or a CoAP protocol, and the message structure and description thereof are shown in FIG. 4C, Table 17, and Table 18. FIG.

Field Name Field Size Description Version One - Protocol version: 0x01 Message Type One - Event Notification: 0x03 URI Length 2 - Size of URI string (Byte) URI N - Describe a URI that manages Event information
- Describe the description method of URI as / v {1} / event / {event_name}, and event_name refers to device-specific profile.

Field Name Field Size Description Client (Proxy) Message Type - Use CON, confirmable message Method - Use GET to read URI values URI - EVENT_NOTIFICATION Use the URI contained in the binary message (EVENT URI) Server (Device) ACK - Pass the updated URI content value as ACK to client
- Refer to the device-specific profile for ACK value.

Between the proxy 110 and the server 120, when the proxy 110 receives an event notification message from the electronic device 100, the proxy 110 transmits an event notification message to the server 120. [ At this time, the structure of the event notification message and the description thereof are shown in [Table 19] and [Table 20]. In Table 19, 'event' is a request message for event delivery, and 'EventInfo (Object Array)' is an event detail value.

URI Method Request Response
(200 OK) Error Members Value Required Members Value Required {serverId} / v {1} / event PUT event EventInfo
(Object Array) true 400,500 Note the error message

Object Name Members Type Description EventInfo eventName string Event name eventValue string Event value

The Json event notification message is as follows.

# Event

{

"event": [

{

"eventName": "a",

"eventValue": "1"

},

{

"eventName": "b",

"eventValue": "2"

}

]

}

Also, when the server 120 receives the event notification message between the server 120 and the terminal 130, the terminal 130 can know the event information if necessary. At this time, the structure and description of the event notification message Are shown in [Table 21] and [Table 22].

URI Method Request Response
(200 OK) Error Members Value Required Members Value Required {serverId} / v {1} / {deviceId} / event GET event EventInfo
(Object Array) true 400,500 Note the error message

Object Name Members Type Description EventInfo eventName hex Event name eventValue string Event value

The Json event notification message is as follows.

# Event

{

"event": [

{

"eventName": "a",

"eventValue": "1"

},

{

"eventName": "b",

"eventValue": "2"

}

]

}

On the other hand, the CONTROL message is used for device control, and the terminal 130 can control the electronic device 100 remotely.

For example, between the terminal 130 and the server 120, the server 120 receives a control message requesting control from the terminal 130, and the control uri and the message per device refer to a predetermined WoT profile per device can do.

Between the server 120 and the proxy 110, when the server 120 receives a control message requesting control from the terminal 130, the server 120 transmits the control message to the proxy 110. At this time, And the device-specific control uri and the message can refer to the predetermined device-specific WoT profile. For example, predetermined device-specific WoT profiles can be configured as shown in [Table 23] and [Table 24], and [Table 23] and [Table 24] are related to light.

URI Method Request Response
(200 OK) Error Members Value Required Members Value Required / v1 / lights
(Full status inquiry, setting, deletion) GET ControlReq Object true 400,500 Note the error message PUT ControlReq Object true DELETE

Object Name Members Type Description ControlReq proxyId String Proxy ID lights Array [Light] Array of Light light Object error Object Light deviceId String Light ID onOff Int On, Off dimming Int 0 to 10, Dimming level color Int 0 to 3 Error Status String 401, 404, 501, etc. Message String Error message errorCode int Error code

Also, between the proxy 110 and the electronic device 100, when the proxy 110 receives a message requesting control from the server 120, the proxy 110 transmits the message to the electronic device 100, And the structure of the control message and a description thereof are shown in Table 25.

Field Name Field Size Description Client (Proxy) Message Type - Use CON, confirmable message Method - Use PUT to transfer (update) the control code URI - Described as IP / v {1} / {controlName} Payload - Describe differently according to the controlName and refer to the profile of the electronic device. Server (Device) ACK - 200 (OK) response SHOULD be returned
- If no resource exists then the server MAY create a new resource with that URI, resulting in a 201 (Created) response
- If the resource could not be created or modified, then an appropriate error response code SHOULD be sent.

On the other hand, the APPLY message is a message for performing system related functions such as updating and Wi-Fi connection.

For example, between the server 120 and the terminal 130, the server 120 may receive an application message requesting application from the terminal 130, and the application message is composed of Request, Response, and Result messages. The structure of the application message and its description are shown in [Table 26] and [Table 27].

URI Method Request Response
(200 OK) Error Members Value Required Members Value Required {serverId} / v {1} / {deviceId} / apply / update
(Update request) PUT firmwareUri string true 400,500 Note the error message {serverId} / v {1} / {deviceId} / apply / rollBack
(RollBack request) PUT rollback
(object) RollBackInfo true 400,500 Note the error message {serverId} / v {1} / {deviceId} / apply / apConnection
(Connection request) PUT apConnection
(object) ConnectionInfo true 400,500 Note the error message {serverId} / v {1} / {deviceId} / apply / {applyName} / result
(Apply result) GET result hex true 400,500 Note the error message

'FirmwareUri' is an address where firmware can be downloaded, 'rollback (object)' is a message for a system rollback request, and 'apConnection (object)' is a message for requesting an AP access.

Object Name Members Type Description - firmwareUri string URI where firmware can be downloaded RollBackInfo firmwareVersion string Firmware version you want to rollback firmwareUri string URI where firmware can be downloaded ConnectionInfo ssid string The SSID you want to connect to password string The password of the SSID you want to connect to - result hex 0x01: Success
0x00: Fail

The application message of Json type is as follows.

# ApplyRequest

{

"apConnection": {

"ssid": "test",

"password": "test"

}

}

#Apply Result

{

  "result": 01

}

Also, between the server 120 and the proxy 110, when the server 120 receives a message requesting application from the terminal 130, the server 120 transmits the message to the proxy 110. In this case, the application message uses the HTTP protocol , The structure of the application message and the description thereof are shown in [Table 28] and [Table 29].

URI Method Request Response
(200 OK) Error Members Value Required Members Value Required {deviceId} / v {1} / apply / update
(Apply request) PUT firmwareUri string true 400,500 Note the error message {deviceId} / v {1} / apply / rollBack
(Apply request) PUT rollback
(object) RollBackInfo true 400,500 Note the error message {deviceId} / v {1} / apply / apConnection
(Apply request) PUT apConnection
(object) ConnectionInfo true 400,500 Note the error message {serverId} / v {1} / {deviceId} / apply / {applyName} / result
(Apply result) PUT result hex true 400,500 Note the error message

Object Name Members Type Description - firmwareUri string URI where firmware can be downloaded RollBackInfo firmwareVersion string Firmware version you want to rollback firmwareUri string URI where firmware can be downloaded ConnectionInfo ssid string The SSID you want to connect to password string The password of the SSID you want to connect to - result hex 0x01: Success
0x00: Fail

The application message of Json type is as follows.

# ApplyRequest

{

"apConnection": {

"ssid": "test",

"password": "test"

}

}

#Apply Result

{

  "result": 01

}

Further, between the proxy 110 and the electronic device 100, when the proxy 110 receives the application request message from the server 120, it requests application to the electronic device 100 via the CoAP message, and the electronic device 100 Informs the proxy 110 of the result using the binary protocol when the application operation is completed. The application message between the proxy 110 and the electronic device 100 uses a binary protocol and a CoAP protocol together. Referring to FIG. 4D, the structure of the binary protocol includes a version 470, a message type 475, a URI length (480), URI (485) and Apply Result (490_), and a description thereof and a description of the CoAP protocol are shown in [Table 30] and [Table 31].

Field Name Field Size Description Version One - Protocol version: 0x01 Message Type One - Apply Complete: 0x04 URI Length 2 - Size of URI string (Byte) URI N - v {1} / apply / {applyName} Apply Result One - Whether or not the application result is normally well done.
0x01: Success
· 0x00: Fail

The data that can be described in the payload is an updateable file in the case of an update request, a rollback file in a desired time in case of a rollback request, and an SSID and a password of the AP in the case of an AP connection request. Ack uses the usual Web Ack.

The AUTHENTICATION message is for requesting the terminal 130 to approve the access right to the proxy 110 in order to control and manage the electronic device 100. Upon receiving the message that the new device is registered from the proxy 110, the terminal 130 transmits a unique code of the electronic device 100 to the proxy 110 for requesting access to the device.

For example, the authentication message is composed of a 'Request' message and a 'Response' message between the terminal 130 and the server 120. When authentication is completed, the device information of 'v {1} / {userId} / discovery' . The structure of the authentication message and the description thereof are shown in [Table 32] and [Table 33].

URI Method Request Response
(200 OK) Error Members Value Required Members Value Required {serverId} / v {1} / {userId} / authen
(Authentication request) PUT authenticationReq AuthenCode
(object) true 400,500 Note the error message

Object Name Members Type Description AuthenCode uri string The URI of the device connected to the proxy managed by the cloud serialCode string Unique code of electronic device id string User ID password string User Password type hex 0x01: Master Add
0x02: Master Delete
0x11: Sub Add
0x12: Sub Delete

The Json type authentication message is as follows.

#Authentication Request

{

"authenticationReq": {

"uri": "111.25.51.10/129.254.86.10/a",

"serialCode": "1234r3-r3r3klnff",

"id": "test",

"password": "test",

"Type": 00

}

}

Between the server 120 and the proxy 110, the authentication message includes a 'Request' message and a 'Response' message. The structure and description of the authentication message are shown in Table 34 and Table 35 Respectively.

URI Method Request Response
(200 OK) Error Members Value Required Members Value Required {deviceId} / v {1} / authen
(Authentication request) PUT authenticationReq AuthenCode
(object) true 400,500 Note the error message

Object Name Members Type Description AuthenCode serialCode string Unique code of electronic device id string User ID password string User Password type hex 0x01: Master Add
0x02: Master Delete
0x11: Sub Add
0x12: Sub Delete

The Json type authentication message is as follows.

#Authentication Request

{

"authenticationReq": {

"serialCode": "1234r3-r3r3klnff",

"id": "test",

"password": "test",

"Type": 00

}

}

While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention.

Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined by the scope of the appended claims, and equivalents thereof.

100: WoT Appliances 110: WoT Proxy
120: Cloud server 130: Smart terminal

Claims (18)

A method for providing a home network service performed by an electronic device,
Transmitting an advertisement message to the proxy;
Receiving a first registration message requesting information for registration of the electronic device from the proxy;
Transmitting a second registration message including information for registration of the electronic device to the proxy;
And receiving a third registration message requesting a registration status update of the electronic device from the proxy,
Wherein the information for registration includes an ID and a password of the terminal registered in the server, the terminal information, and a unique code of the electronic device,
Wherein the message transmitted between the electronic device and the proxy is a CoAP-based binary form. A method for providing a home network service performed by a proxy,
Receiving an advertisement message from an electronic device;
Sending a first registration message to the electronic device to request information for registration of the electronic device;
Receiving a second registration message including information for registration of the electronic device from the electronic device;
Transmitting a third registration message requesting the electronic device to update the registration status of the electronic device;
And transmitting a fourth registration message including information for registration to request registration of the electronic device to the server,
Wherein the information for registration includes an ID and a password of the terminal registered in the server, the terminal information, and a unique code of the electronic device,
Wherein the message transmitted between the electronic device and the proxy is in a CoAP based binary form and the message transmitted between the server and the proxy is in an HTTP based Json form. A method for providing a home network service performed by a server,
Receiving a fourth registration message including information for registration to request registration of an electronic device from a proxy;
Transmitting a fifth registration message to the terminal indicating that the electronic device is registered in the server;
And transmitting a sixth registration message to the proxy indicating completion of registration of the electronic device,
Wherein the information for registration includes an ID and a password of the terminal registered in the server, the terminal information, and a unique code of the electronic device,
Wherein the message transmitted between the server, the proxy, and the terminal is of the HTTP-based Json type. delete 3. The method according to claim 1 or 2,
Wherein the advertisement message uses a binary protocol and comprises at least one of a protocol version, a message type, a URI length, a URI of the electronic device, and information on whether or not the electronic device is registered. 3. The method of claim 2,
The receiving of the advertisement message comprises:
And transmitting a notification message informing the server that the advertisement message is received,
The notification message includes at least one of a URI for message delivery, a Restful message format, and a request to be delivered,
Wherein the request comprises at least one of an external URI mapping the electronic device at the proxy, and information about whether the electronic device is registered with the proxy. delete 3. The method according to claim 1 or 2,
The first registration message, the second registration message, and the third registration message use a CoAP protocol and include a message type related to whether the message is a confirmation type message, a Restful message format, a serial code, And an ACK including information about a URI relating to the registration status update, a payload including information about whether or not the electronic device is registered, a serial code and user information of the electronic device, and a result of performing the registration update. The method according to claim 2 or 3,
Wherein the fourth registration message includes at least one of a URI for message delivery, a message format for a Restful message, and a response to a request message,
Wherein the request comprises at least one of an external URI mapping an electronic device to a proxy, a unique code of the electronic device, a user ID, a user password, and a user telephone number. The method of claim 3,
Wherein the fifth registration message uses a binary protocol,
Protocol version, message type, URI length, and URI of the electronic device. 3. The method of claim 2,
Further comprising the step of transmitting an information message for requesting information on the electronic device to the electronic device,
Wherein the information message comprises at least one of a message type relating to whether the message is an acknowledgment type message, a Restful message type, a URI relating to information of the electronic device, and an ACK including information about the electronic device. The method of claim 3,
Sending an information message to the proxy to request information about the electronic device;
And transmitting an information message for transmitting information on the electronic device to the terminal,
Wherein the information message includes at least one of a URI for message delivery, a Restful message format, a Request to be delivered, and a response to a request message. The method according to claim 1,
And transmitting an event message to the proxy,
Wherein the event message includes at least one of a protocol version, a message type, a URI length, and a URI related to an Internet address that manages event information. 3. The method of claim 2,
Further comprising transmitting an event message to the electronic device,
The event message uses a binary protocol or a CoAP protocol, and the event message includes a URI length, a URI regarding an intuitive address for managing event information, a message type related to whether the message is a confirmation type message, Method) and an ACK containing information about the updated URI content value. The method of claim 3,
Receiving an event message from the proxy;
Further comprising the step of receiving an event message from the terminal,
Wherein the event message includes at least one of a URI relating to an Internet address for message delivery, a Restful message format, a request to be delivered, and a response to a request message. The method of claim 3,
Receiving an application message for performing a function of the electronic device from the terminal;
And transmitting an application message for performing the function of the electronic device to the proxy,
The application message includes at least one of a URI regarding an Internet address for message delivery, a Restful message format, a request to be delivered, and a response to a request message,
Wherein the request includes at least one of a URI capable of downloading firmware, a firmware version to be rolled back, an SSID to be connected, a password of an SSID to be connected, and information on a result of application. 3. The method of claim 2,
And transmitting an application message for performing a function to the electronic device,
The application message uses the CoAP protocol and includes a message type (Message Type) related to whether the message is a confirmation type message, a Restful message format (Method), a URI related to the Internet address of the application, , And an ACK for a response. 3. The method of claim 2,
Further comprising receiving an application message for performing a function from the electronic device,
Wherein the application message uses a binary protocol and comprises at least one of a protocol version, a message type, a URI length, a URI related to an Internet address of application, and information on an application result.

Images