WO2015093887A1 - Apparatus and method for registering home device in server in home network system - Google Patents

Apparatus and method for registering home device in server in home network system Download PDF

Info

Publication number
WO2015093887A1
WO2015093887A1 PCT/KR2014/012562 KR2014012562W WO2015093887A1 WO 2015093887 A1 WO2015093887 A1 WO 2015093887A1 KR 2014012562 W KR2014012562 W KR 2014012562W WO 2015093887 A1 WO2015093887 A1 WO 2015093887A1
Authority
WO
WIPO (PCT)
Prior art keywords
home device
home
server
device
connection
Prior art date
Application number
PCT/KR2014/012562
Other languages
French (fr)
Korean (ko)
Inventor
김준형
김세훈
공동건
천재익
손유미
윤강진
Original Assignee
삼성전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to KR10-2013-0160650 priority Critical
Priority to KR20130160650 priority
Priority to KR10-2014-0101259 priority
Priority to KR1020140101259A priority patent/KR20150073827A/en
Application filed by 삼성전자 주식회사 filed Critical 삼성전자 주식회사
Priority claimed from US15/106,028 external-priority patent/US9992677B2/en
Publication of WO2015093887A1 publication Critical patent/WO2015093887A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. local area networks [LAN], wide area networks [WAN]
    • H04L12/2803Home automation networks
    • H04L12/2807Exchanging configuration information on appliance services in a home automation network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements, e.g. access security or fraud detection; Authentication, e.g. verifying user identity or authorisation; Protecting privacy or anonymity ; Protecting confidentiality; Key management; Integrity; Mobile application security; Using identity modules; Secure pairing of devices; Context aware security; Lawful interception
    • H04W12/06Authentication
    • H04W12/0609Authentication using certificates or pre-shared keys

Abstract

The present invention relates to a method for registering a home device of a home network system in a server, the method comprising: receiving an access token from an account server managing an account for a control device; receiving a peer identifier (peer ID) identifying the home device and a peer group identifier (peer group ID) identifying a group of home devices from the control device; and logging into a connection server managing the connection between the home device and the control device on the basis of the access token, the peer ID, and the peer group ID.

Description

Apparatus and method for registering a home device with a server in a home network system

The present invention relates to an apparatus and method for registering a home device with a server in a home network system.

The home network system refers to a system that enables control of home devices by connecting home devices installed in a home to a wired or wireless network. An advanced home network system integrates home devices through a home gateway (HGW) and connects them to an external public data network, such as an Internet protocol (IP) network (ie, the Internet), thereby connecting more with the Internet. Provide various services. In such a home network system, home devices may be controlled according to a user's request to provide a service desired by the user.

In addition, in order to use the control service by connecting to home devices in the home, a separate device such as the home gateway must be used, which is different from the inside and outside the control methods and procedures even though the same control service is used. It causes the problem that usability is impaired.

Therefore, efforts are needed to use various control services according to the same method and procedure regardless of the house and the house.

On the other hand, the above information is only presented as background information to help the understanding of the present invention. No determination is made as to whether any of the above is applicable as the prior art concerning the present invention, and no claims are made.

An embodiment of the present invention proposes a method and apparatus for registering a home device with a server in a home network system.

In addition, an embodiment of the present invention proposes a method and apparatus for registering device information on a home device in a home network system through a controller.

In addition, an embodiment of the present invention proposes a method and apparatus for directly registering device information of a home device in a service server in a home network system.

In addition, an embodiment of the present invention proposes a method and apparatus for controlling a home device registered in a server in a home network system.

The method proposed in one embodiment of the present invention; A method of registering a home device with a server in a home network system, the method comprising: receiving an access token from an account server managing an account for a control device, and a peer identifier (ID) identifying the home device; (peerID) and a peer group ID (peergroupID) identifying a group of home devices from the control device, and between the home device and the control device based on the access token, peer ID, and peer group ID Logging in to the connection server that manages the connection.

In another embodiment of the present invention the method proposed; A method of registering a home device with a server in a home network system, the method comprising: receiving a peer identifier (ID) identifying a home device from a service server managing device information about the home device; And transmitting, to the home device, the peer ID and a peer group ID identifying a group of home devices.

In another embodiment of the present invention the method proposed; A method of registering a home device by a service server in a home network system, wherein the service server managing device information on the home device logs in to a connection server where the home device manages a connection between the home device and a control device. And transmitting a peer ID (peerID) to the control device, wherein the peer ID is an ID for identifying the home device.

In another embodiment of the present invention the method proposed; A method for registering an home device by an account server in a home network system, the method comprising: transmitting, by the account server managing an account for a controller, an authentication code to the control device, an authentication code and the control device from the home device. Receiving a user identifier (ID: identifier) for, and confirming that the authentication code received from the home device is the same as the authentication code sent to the control device, and if the two authentication codes are the same, the home device And transmitting a connection token to the home device to log in to the connection server managing the connection between the home device and the control device.

In another embodiment of the present invention the method proposed; A method for registering a home device by a connection server in a home network system, the connection server managing a connection between the home device and a control device includes a peer identifier (ID) identifying the home device; Receiving a login request from the home device using a peer group ID (peerGroupID) identifying a group of home devices and an access token used to authenticate a use right of the home device, and a login response corresponding to the login request; It includes the step of transmitting to the home device.

The apparatus proposed in one embodiment of the present invention; A home device registering with a server in a home network system, comprising: a peer identifier (ID) for receiving the access token from an account server managing an account for a control device and identifying the home device And a receiving unit receiving a peer group ID (peergroup ID) identifying a group of home devices from the controller, and controlling the receiving unit to log in to the connection server based on the access token, peer ID, and peer group ID. It includes a control unit.

The apparatus proposed in another embodiment of the present invention; A controller for registering a home device with a server in a home network system, the controller comprising: a receiver configured to receive a peer identifier (ID) from a service server managing device information of the home device; And a transmitter for transmitting a peer group ID (peerGroupID) identifying a group of home devices to the home device, and a controller for controlling the transmitter and the receiver.

The apparatus proposed in another embodiment of the present invention; A service server for registering a device in a home network system, the home device transmitting a peer identifier (peerID) to the controller for use in logging in to a connection server managing a connection between the home device and a control device. And a controller for controlling the transmitter, wherein the peer ID is an ID for identifying the home device.

The apparatus proposed in another embodiment of the present invention; An account server that registers a home device in a home network system, wherein the authentication code is transmitted to the control device, the authentication code received from the home device is identical to the authentication code sent to the control device, and the two authentication codes Is equal to, a transmitter for transmitting a connection token to the home device to be used when the home device logs in to a connection server managing a connection between the home device and the controller period, an authentication code and the control from the home device. And a receiver for receiving a user identifier (ID) for the device, and a controller for controlling the transmitter and the receiver.

The apparatus proposed in another embodiment of the present invention; A connection server that registers a home device in a home network system, comprising: a peer identifier (ID) identifying the home device, a peer group ID identifying a group of home devices, and a home device A receiving unit for receiving a login request from the home device using a connection token used to authenticate the usage right of the terminal, a transmitting unit for transmitting a login response corresponding to the login request to the home device, and a control unit for controlling the transmitting unit and the receiving unit It includes.

Other aspects, benefits, and key features of the present invention will be apparent to those skilled in the art from the following detailed description, taken in conjunction with the accompanying drawings, in which preferred embodiments of the present invention are published.

Before proceeding with the following detailed description of this publication, it may be effective to set definitions for specific words and phrases used throughout this patent document: the words “include” and “include”. "Comprise" and its derivatives mean unlimited inclusion; The term “or” is inclusive and means “and / or”; The phrases “associated with” and “associated therewith” and their derivatives include, be included within, and interconnected with (interconnect with), contain, be contained within, connect to or with, connect to or connect with or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, Something that is likely or be bound to or with, have, have a property of, etc .; The word “controller” means any device, system, or portion thereof that controls at least one operation, wherein the device is hardware, firmware or software, or some combination of at least two of the hardware, firmware or software. It can be implemented in It should be noted that the functionality associated with any particular controller may be centralized or distributed, and may be local or remote. Definitions for specific words and phrases are provided throughout this patent document, and those skilled in the art will, in many instances, if not most of the cases, define such definitions as well as conventional and such definitions. It should be understood that this also applies to future uses of the syntax.

The present invention has the advantage of providing a variety of home network services in the home network system according to the same method and procedure regardless of the home and home.

Further aspects, features and benefits as described above of certain preferred embodiments of the present invention will become more apparent from the following description taken in conjunction with the accompanying drawings:

1 is a diagram illustrating an example of a procedure of registering a home device with a server in a home network system according to an embodiment of the present invention;

2 is a diagram illustrating a flow of information exchanged for registering a home device with a server in a home network system according to an embodiment of the present invention;

3 illustrates a software structure for communication between devices included in a home network system according to an embodiment of the present invention;

4 is a diagram illustrating an example of a connection establishment and release procedure between a home device logged in a connection server and a controller device in a home network system according to an embodiment of the present invention;

5 is a flowchart illustrating an operation of registering a home device with a server in a home network system according to an embodiment of the present invention;

6 is a flowchart illustrating an operation in which a controller registers a home device with a server in a home network system according to an embodiment of the present invention;

7 is a flowchart illustrating an operation of registering a home device by a service server in a home network system according to an embodiment of the present invention;

8 is a flowchart illustrating an operation in which an account server registers a home device in a home network system according to an embodiment of the present invention;

9 is a flowchart illustrating an operation of registering a home device by a connection server in a home network system according to an embodiment of the present invention;

10 is a diagram illustrating a flow of information exchanged for registering a home device with a server in a home network system according to another embodiment of the present invention;

11 is a flowchart illustrating an operation of registering a home device with a server in a home network system according to another embodiment of the present invention;

12 is a flowchart illustrating an operation in which a controller registers a home device with a server in a home network system according to an embodiment of the present invention;

13 is a flowchart illustrating an operation of registering a home device by a service server in a home network system according to another embodiment of the present invention;

14 is an apparatus diagram showing an internal configuration of a home device registering with a server in a home network system according to an embodiment of the present invention;

15 is an apparatus diagram illustrating an internal configuration of a controller for registering a home device with a server in a home network system according to an embodiment of the present invention;

16 is an apparatus diagram illustrating an internal configuration of a service server that registers a home device in a home network system according to an embodiment of the present invention;

17 is an apparatus diagram illustrating an internal configuration of an account server that registers a home device in a home network system according to an embodiment of the present invention;

18 is a diagram illustrating an internal configuration of a connection server that registers a home device in a home network system according to an embodiment of the present invention.

Throughout the drawings, it should be noted that like reference numerals are used to depict the same or similar elements, features and structures.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In describing the present invention, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

As the inventive concept allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

In addition, it is to be understood that the singular forms “a” and “an”, including “an”, unless the context clearly indicates otherwise, include plural expressions. Thus, as an example, a “component surface” includes one or more component surfaces.

In addition, terms including ordinal numbers such as first and second may be used to describe various components, but the components are not limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term and / or includes a combination of a plurality of related items or any item of a plurality of related items.

In addition, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. As used herein, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof described on the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

In addition, in the embodiments of the present invention, unless otherwise defined, all terms used herein including technical or scientific terms are generally understood by those skilled in the art to which the present invention belongs. Has the same meaning as Terms such as those defined in the commonly used dictionaries should be interpreted as having meanings consistent with the meanings in the context of the related art, and ideally or excessively formal meanings, unless explicitly defined in the embodiments of the present invention. Not interpreted as

According to various embodiments of the present invention, an electronic device may include a communication function. For example, the electronic device may be a smart phone, a tablet personal computer (PC), a mobile phone, a video phone, an e-book reader, a desktop ( desktop PC, laptop PC, netbook PC, personal digital assistant (PDA), portable multimedia player (PMP), mp3 player (mp3 player) Mobile medical devices, cameras, wearable devices (e.g., head-mounted devices (HMDs), electronic clothing, electronic bracelets, electronic necklaces, electronic accessories) appcessory, electronic tattoo, or smart watch.

According to various embodiments of the present disclosure, the electronic device may be a smart home appliance having a communication function. For example, the smart home appliance includes a television, a digital video disk (DVD) player, audio, a refrigerator, an air conditioner, a vacuum cleaner, an oven, a microwave oven, a washer, a dryer. With an air cleaner, a set-top box, a TV box (e.g. Samsung HomeSyncTM, Apple TVTM, or Google TVTM), a gaming console, an electronic dictionary, a camcorder , Electronic photo frames and the like.

According to various embodiments of the present disclosure, an electronic device may include a medical device (eg, magnetic resonance angiography (MRA) device, magnetic resonance imaging (MRI), and computed tomography (MRI). Computed tomography (CT) devices, imaging devices or ultrasound devices), navigation devices, global positioning system (GPS) receivers, event recorders (EDRs), and flights Flight data recorder (FER), automotive infotainment device, navigational electronic device (e.g., navigational navigation device, gyroscope or compass), avionics device, security device And industrial or consumer robots.

According to various embodiments of the present invention, an electronic device includes a furniture, a part of a building / structure, an electronic board, an electronic signature receiving device, a projector, and various measurement devices (eg, Water, electricity, gas or electromagnetic wave measuring devices) and the like.

According to various embodiments of the present disclosure, the electronic device may be a combination of devices as described above. In addition, it will be apparent to those skilled in the art that the electronic device according to the preferred embodiments of the present invention is not limited to the device as described above.

According to various embodiments of the present disclosure, the user terminal may be an electronic device as an example.

In an embodiment of the present invention, a server for providing a service interworking between a home and a home in a home network system, for example, a service server, an account server, a connectivity server, and a push server. A method of registering a home device with a service server, an accounting server, and a connection server among a push server and firmware management servers will be described. In addition, in the embodiment of the present invention, a service server, an account server, and a connection server in a home network system will be described with respect to a method of transmitting and receiving a service signal with a home device in cooperation with each other.

1 is a diagram illustrating an example of a procedure of registering a home device with a server in a home network system according to an exemplary embodiment of the present invention.

Before describing FIG. 1, it is assumed that home devices installed in the home (or home) are already connected to the home network system. That is, a newly purchased home device performs a preliminary procedure of connecting to a home network system, for example, a controller, at the time of first installation in the home (or outside of the home), where the controller is connected to device information and peers for the newly purchased home device. Obtain and store information on a group identifier (ID: identifier) and a country code (countryCode). The device information for the home device may be, for example, a unique user identifier (UUID), which is a unique ID of the home device, and a type, name, description, manufacturer, and model. ID, serialNumber, salesLocation, versions, etc. In addition, peerGroup ID indicates a group of home devices registered in the service server using a specific user account, and countryCode indicates country information in which a user of a controller is located.

Referring to FIG. 1, the illustrated network system includes a home device 101, a controller 103, a service server 105, an account server 107, and a connection server 109.

The controller 103 is a device used by a user for checking a state of the home device 101 or controlling the home device 101. The controller 103 may be, for example, a mobile terminal such as a smartphone or a television (TV).

The home device 101 is located in the home (or outside the home) and is a device that can be controlled through the controller 103. The home device 101 includes a smart appliance, a security device, a lighting device, an energy device, and the like. For example, the home appliance may be a TV, an air conditioner, a refrigerator, a washing machine, a robot cleaner, a humidifier, and the like, and the security device may be a door lock, a security camera, a closed circuit television (CCTV), a security sensor, and the light fixture is an LED. (light emitting diode), a lamp, and the like, and the energy device may be a heating device, a power meter, a power socket, an electrical outlet, a power strip, or the like. Additionally, the home device 101 may include a personal computer (PC), an IP camera, an internet phone, a wired / wireless phone, an electrically controllable curtain, a blind, and the like.

The account server 107 is a server that manages an account for the user of the controller 103. The account server 107 provides a function that enables the user to connect to the service server 105 and the connection server 109 using single user login information when the user logs in to the account server 107.

The connection server 109 is a server that provides a service for establishing a communication channel for message transmission between the home device 101 and the controller 103. The connection server 109 provides presence information indicating whether a connection between the home device 101 and the controller 103 is possible, and allows a connection through a firewall even remotely. Network Address Translation (NAT) -T (NAT-Traversal) is provided.

The account server 107 and the connection server 109 are public servers that can be used for other services in addition to the services provided by the home network system. In contrast, the service server 105 operates only for home network system services. The service server 105 provides a function of storing and managing home device device information for circulating information of the home device 101 and all other information for control of the home device 101.

The user connects to the service server 105 using an application executed in the controller 103, for example, a smart home app. In addition, a user may register home device information in the service server 105 or circulate or delete pre-registered home device information, register control information for collective control of home devices, or circulate or delete pre-registered control information. have. Hereinafter, a procedure in which a user registers information about the home device 101 through the controller 103 will be described in more detail. In FIG. 1, the procedure of registering one home device 101 with the server will be described as an example. However, the procedure described with reference to FIG. 1 is the same with the procedure of registering each home device (or home) that can be installed in the server. Applicable

According to the user input, the controller 103 executes the smart home app, and at the same time as the execution of the smart home app, the controller 103 is automatically logged in to the account server 107 (step 102). Here, the case where the controller 103 is automatically logged in to the account server 107 through the pre-stored user ID and password has been described as an example. However, the controller 103 may optionally log in to the account server 107 by receiving a user ID and password from the user. In addition, since the login information is maintained for a predetermined time unless the user logs out at the request of the user, the login information does not have to be logged in to the account server 107 each time within the validity period of the login information. That is, the user can use a desired service without performing an additional login procedure within the validity period.

The controller 103 discovers home devices located in the home (or outside the home) and collects information on the found home devices and displays them on the screen. Among the home devices, a home device to be registered in the account server 107 is selected according to a user input, and it is assumed here that the home device selected according to the user input is the illustrated home device 101.

The controller 103 performs a device to device (D2D) authentication procedure with the home device 101 to transmit / receive mutual information (step 104). The discovery, information collection, and D2D authentication procedure of the home device are performed. The operation that must be performed before registering the home device 101 with the account server 107 is different from the contents to be described in an embodiment of the present invention, so the detailed description thereof will be omitted here.

The controller 103 transmits an authentication code request to the account server 107 to register the home device 101 with the service server 105 (step 106). In response to the request, the issuing authentication code is transmitted to the controller 103 (step 108). The authentication code is the home device 101 receives an access token from the account server 107. The connection token indicates a key value used, and the connection token indicates a key value used when the home device 101 connects to the connection server 109 so that the connection server 109 authenticates the use right of the home device 101.

An example of implementing the operation of the controller 103 transmitting an authentication code request and receiving an authentication code in response to the request is shown in Tables 1 and 2. That is, Table 1 shows an example of a message format for transmitting the authentication code request, and Table 2 shows an example of a message format for transmitting a response to the request.

Table 1

Figure PCTKR2014012562-appb-T000001

TABLE 2

Figure PCTKR2014012562-appb-T000002

Tables 1 and 2 are examples of implementations within the controller 103, and do not mean a procedure of exchanging a message with an actual account server 107. In addition, the controller 103 is equipped with a library-type interworking client, for example, an account server client, for communication with the account server 107. The controller 103 may transmit and receive a service signal with the account server 107 by using the coordinated client. That is, the smart home app of the controller 103 calls a function of the linked client and exchanges a message with the account server 107 through the linked client.

In addition, the controller 103 transmits an account server registration request to the home device 101 (step 110). The message for transmitting the account server registration request is used in step 102 with the authentication code received from the account server 107. User ID is included. In this case, the authentication code and the user ID are transferred to the home device 101 through a RESTful protocol based on HTTP (hyper text transfer protocol).

An example of a message format in which the controller 103 sends an account server registration request to the home device 101 using the RESTful protocol is shown in Table 3. Table 3 shows the message format using the user's email ID as an example of the user ID. However, the user ID may include a user's unique ID such as a nickname, social security number, and phone number. May be used. Since the RESTful protocol is a widely used general protocol, its detailed description will be omitted here.

TABLE 3

Figure PCTKR2014012562-appb-T000003

The home device 101 receives the authentication code and the user ID received from the controller 103 in order to receive a connection token, a refresh token, and a globally unique identifier (GUID). The account server 107 checks the received authentication code and the user ID, and verifies whether the received authentication code is an authentication code normally issued to the user indicated by the user ID. That is, the account server 107 checks whether the received authentication code is the same as the authentication code issued in step 108.

If the result of the check is that the received authentication code is the same as the authentication code issued in step 108, the account server 107 determines that the received authentication code is an authentication code normally issued to the user, the home device 101 The access token, the refresh token, and the GUID are transmitted (step 114). Here, the GUID means an identifier that the account server 107 separately allocates for the identification of the home device 101.

The access token has a validity period and will no longer be valid after a predetermined validity period has passed. Therefore, when the access token is to be used even after the validity period has elapsed, the access token must be renewed within the validity period. The refresh token is used to update this connection token. Since the procedure for updating the access token is far from what is described in the embodiment of the present invention, the detailed description thereof will be omitted here.

In addition, the procedure for receiving the access token from the account server 107 by using a specific key value such as the authentication code is described in detail in Request for Comment (RFC) 6749 specified by the Internet Engineering Task Force (IETF). To be omitted.

When the home device 101 receives the access token transmitted in step 114, the home device 101 transmits an account server registration response to the controller 103 in response to the account server registration request received in step 110. The account server registration response includes information indicating that the home device 101 is successfully registered with the account server 107. An example of a message format for transmitting the account server registration response is shown in Table 3.

In operation 114, the home device 101 may not receive the access token. In other words, the home device 101 transmits the authentication code and the user ID to the account server 107 and starts driving the preset timer, and the access token from the account server 107 until the preset timer expires. May not be received. In this case, the home device 101 transmits an account server registration response including the information indicating that the home device 101 has failed to register with the account server 107 to the controller 103 (step 116). The operation of determining whether the device 101 receives the access token by using the timer has been described as an example. However, whether or not to receive the access token may be determined by any other example.

The controller 103 transmits a home device registration request to the service server 105 in order to register the device information of the home device 101 obtained through a preliminary procedure with the home device 101 to the service server 105. In step 118, the message for transmitting the home device registration request includes a UUID which is a unique ID of the home device 101 and device information of the home device 101. An example of a message format for transmitting the home device registration request is shown in Table 4.

Table 4

Figure PCTKR2014012562-appb-T000004

The service server 105 transmits a home device registration response corresponding to the home device registration request to the controller 103 (step 120). The message for transmitting the home device registration response includes a peer ID (peerID). The peer ID refers to an identifier assigned by the service server 105 to allow the connection server 109 to identify the home device 101. The service server 105 assigns a unique ID to each home device located in the home (or home).

The controller 103 transmits a connection server registration request to the home device 101 (step 122), and the home device 101 transmits a connection server registration response corresponding to the request to the controller 103. The message for transmitting the connection server registration request includes a peer ID received from the service server 105, a peer group ID obtained through a preliminary procedure with the home device 101, and a country code. Here, the peer group ID indicates a group including home devices registered to the service server 105 using a specific user account. The controller 103 and the home device 101 registered using the specific user account are the same. It has a peer group ID. The country code indicates the country information where the user of the controller 103 is located.

An example of a message format for transmitting the connection server registration request and the connection server registration response is shown in Table 5.

Table 5

Figure PCTKR2014012562-appb-T000005

The home device 101 then logs in to the connection server 109 using the peer ID, peer group ID and country code received from the controller 103 and the access token received from the account server 107. )

In FIG. 1, a procedure of registering device information of the home device 101 with the service server 105 through the controller 103 has been described as an example. However, when the home device 101 has previously acquired the information for registration to the service server 105 from the controller 103, the device information of the home device 101 is not obtained through the controller 103. You can also register directly with 105. The procedure of directly registering the device information of the home device 101 with the service server 105 without using the controller 103 will be described in more detail through another embodiment of the present invention to be described later.

2 is a diagram illustrating a flow of information exchanged to register a home device with a server in a home network system according to an exemplary embodiment of the present invention.

Referring to FIG. 2, the illustrated home network system includes a home device 201, a controller 203, a service server 205, an account server 207, and a connection server 209.

Examples and functions of the home device 201, the controller 203, the service server 205, the account server 207, and the connection server 209 have been described in detail with reference to FIG. 1, so that detailed description thereof will be omitted herein. do.

The controller 203 executes the smart home app according to a user input, and at the same time as the execution of the smart home app, the controller 203 is automatically logged in to the account server 207 (step 202). Or home) are selected based on user input

When the account server 207 receives the authentication code request from the controller 203, the account server 207 issues an authentication code in response to the request and transmits the authentication code to the controller 203 (step 204). It is assumed that the home device selected in accordance with a user input among home devices located in the home (or outside the home). The authentication code is used to register the home device 101 with the service server 105, and in particular represents a key value used by the home device 201 to receive a connection token from the account server 207. The connection token represents a key value used when the home device 201 connects to the connection server 209, and the connection server 209 authenticates the use right of the home device 201.

In addition, the controller 203 transmits the authentication code and the user ID received in step 204 to the home device 101 through an account server registration request (step 206). Here, the user ID is an e-mail ID or nickname. Can be one of a social security number or a phone number.

In order to receive the access token, the refresh token, and the GUID, the home device 201 transmits the authentication code and the user ID received in step 206 to the account server 207 (step 208).

The account server 207 checks the authentication code and the user ID received in step 208, and verifies whether the received authentication code is an authentication code normally issued to the user indicated by the user ID. That is, the account server 207 checks whether the received authentication code is the same as the authentication code issued in step 204.

If it is determined that the received authentication code is the same as the authentication code issued in step 204, the account server 207 determines that the received authentication code is an authentication code normally issued to the user, and sends it to the home device 201. The access token, the refresh token, and the GUID are transmitted (step 210). Here, the GUID means an identifier that the account server 207 separately allocates for identification of the home device 201.

The controller 203 transmits the device information of the home device 201 and the UUID which is a unique ID of the home device 201 to the service server 205 through the home device registration request (step 212). The device information and the UUID of the device 201 are information obtained from the home device 201 through a preliminary procedure of connecting the home device 201 with the controller 203 when the home device 201 is initially installed in the home (or the home).

The service server 205 transmits a peer ID to the controller 203 through a home device registration response corresponding to the home device registration request (step 214). The peer ID is determined by the connection server 209 by the home device 201. ) Refers to an identifier assigned by the service server 205 so that it can be identified. The service server 205 assigns a unique ID of each peer to all home devices located in the home (or outside the home).

The controller 203 transmits the peer ID, other peer group ID, and country code received in step 214 to the home device 201 through a connection server registration request (step 216). Is information obtained from the home device 201 through a preliminary procedure of connecting the home device 201 with the controller 203 when the home device 201 is initially installed in the home (or the home).

Thereafter, the home device 201 logs in to the connection server 209 using the access token received in step 210, the peer ID, peer group ID, and country code received in step 216.

3 is a diagram illustrating a software structure for communication between devices included in a home network system according to an embodiment of the present invention.

Referring to FIG. 3, the illustrated home network system includes a plurality of devices, that is, a home device 301, a controller 303, a service server 305, an account server 307, and a connection server 309. .

The controller 303 has a connection server client 302 in the form of a library for communication with the connection server 309, an account service client 304 in the form of a library for communication with the account server 307, and a smart home app. 306 is mounted.

In the home device 301, a connection server client 308 in the form of a library for communication with the connection server 309 and an application executed in the home device 301, for example, a home device app 310. Is mounted, and the account service client 304 for communication with the account server 307 is not mounted. The home device 301 communicates with the account server 307 through the home device app 310.

The controller 303 also communicates with the service server 305 via the smart home app 306, and the home device 301 communicates with the service server 305 through the home device app 310.

For example, the controller 303 transmits and receives a message with the home device 301 according to a user input.

The controller 303 executes the smart home app 306 according to the user input, and when a control command for the home device is input from the user through the smart home app 306, the controller 303 controls the message according to the control command. The server transmits the data to the connection server 309 through the connection server client 302 mounted in step 303. (Steps 312 and 314).

The connection server client 308 mounted on the home device 301 receives a message transmitted from the controller 303 through the connection server 309 (step 316), and the connection server client 308 receives the received message. In step 318, the home device app 310 is transmitted to the home device app 310.

That is, the connection service clients 302 and 308 mounted on the controller 303 and the home device 301 each transmit and receive a message input from the user through the smart home app 306.

Meanwhile, in order to transmit and receive a message between the connection service clients 302 and 308, it is necessary to collect connection state information of the other connection service client. In FIG. 4, the connection server client 308 mounted on the home device 301 and the connection server client 302 mounted on the controller 303 collect connection state information from each other and generate a channel for message transmission. The operation of transmitting and receiving a message will be described.

4 is a diagram illustrating an example of a connection establishment and release procedure between a home device logged in a connection server and a controller device in a home network system according to an exemplary embodiment of the present invention.

Referring to FIG. 4, the illustrated home network system includes a home device 401, a controller 403, and a connection server 409. In addition, in FIG. 4, it is assumed that the controller 403 is logged in to the connection server 409.

The home device 401 transmits a login request to the connection server 409 by using the access token received from the accounting server, the peer ID, the peer group ID, and the country code received from the controller device (step 404). Attempt to log in to (409). The connection server 409 transmits a login response to the home device 401 indicating that the login is successful in response to the login request (step 406). Here, the case where the login attempted by the home device 401 succeeds will be described as an example. It was. However, if the login attempted by the home device 401 fails, the connection server 409 transmits a login response to the home device 401 indicating that the login failed in response to the login request.

When the home device 401 logs in to the connection server 409 (step 408), the connection server 409 notifies the controller 403 of the home device connection information including the presence information (step 410). The presence information indicates whether the connection between the home device 401 and the controller 403 is possible. For example, the presence information may be information indicating that the home device 401 is logged in to the connection server 409. The home device connection information includes not only the presence information but also information on an IP address and a port used by the home device 401, network type information used by the home device 401, and the like. The network type information may be, for example, information related to Wi-Fi, information related to 2G, information related to 3G, information related to 4G, and the like.

The controller 403 that is notified of the home device connection information may know whether the home device 401 is currently connectable. Although not shown, when the home device 401 logs out of the connection server 409, the connection server 409 may indicate that the home device 401 has logged out of the connection server 409. The controller 403 is notified of the home device connection information including information on the IP address and port used by the home device 401 and network type information used by the home device 401.

Steps 404, 406, 408, and 410 described in FIG. 4 are described in more detail by step 126 of FIG. 1, that is, a procedure in which the home device logs in to the connection server.

Thereafter, when the controller 403 receives a control command for the home device 401 from the user through the smart home app, in step 412, the controller 403 requests a connection for establishing a channel between the home device 401 and the controller 403. Is transmitted to the home device 401 (step 414). Here, the channel refers to a channel through which the controller device 403 and the home device 401 transmit and receive a message including the control command. In addition, the connection request is transmitted to the home device 401 through the connection server client mounted on the controller 403.

The home device 401 transmits a connection response to the controller 403 in response to the connection request (step 416). The controller 403 has successfully connected to the home device 401 through the smart home app. Notify the user of the instructed information (step 418), and establish a connection with the home device 401 (step 420).

The home device 401 which has completed the connection setting with the controller 403 waits to receive a message transmitted from the controller 403 (step 422), and the controller 403 includes a control command according to a user input. Message is transmitted to the home device 401. (Step 424) When the transmission of the message including the control command according to the user input is completed, the controller 403 requests to release the connection established in step 420. The connection release request is transmitted to the home device 401 (step 426), and then the connection between the home device 401 and the controller device 403 is released (step 428).

Messages transmitted and received between the home device 401 and the controller 403 are transmitted and received through a connection server client of a library type for communication with the connection server 409. That is, the messages transmitted and received in steps 414, 416, 424, and 426 are transmitted and received through the connection server client mounted on the home device 401 and the connection server client mounted on the controller 403.

5 is a flowchart illustrating an operation of registering a home device with a server in a home network system according to an embodiment of the present invention.

In FIG. 5, it is assumed that the home device is home devices located in the home (or outside the home). In FIG. 5, an operation after the D2D authentication procedure is completed between the home device and the controller device will be described. Since the D2D authentication procedure is far from the content to be described in an embodiment of the present invention, the detailed description thereof will be omitted.

In addition, in FIG. 5, an operation of registering one home device among home devices located in the home (or outside home) with the server will be described as an example. However, the operation described with reference to FIG. The same applies to the operation of registering the server with the server.

Referring to FIG. 5, in step 502, the home device receives, from the controller device, an authentication code used to receive an access token and a user ID for a user of the controller device. Here, the home device refers to a device located in the home (or outside the home) and can be controlled by the controller, and includes a home appliance, a security device, a lighting device, an energy device, and the like. For example, the home appliance may be a TV, an air conditioner, a refrigerator, a washing machine, a robot cleaner, a humidifier, and the like. The energy device may be a heating device, a power meter, a power socket, an electrical outlet, a power strip, or the like. Additionally, home devices may include PCs, IP cameras, Internet phones, wired / wireless phones, electrically controllable curtains, blinds, and the like. The connection token indicates a key value used when the home device connects to the connection server that manages the connection between the home device and the controller period, and the connection server is used to authenticate the use right of the home device.

In step 504, the home device transmits the received authentication code and user ID to an account server that manages an account for the user.

In step 506, the home device receives a connection token, a refresh token, and a GUID from the account server. The refresh token refers to a token used to renew the access token within the validity period so that the access token can be used even after a previously promised validity period has elapsed. The GUID means an ID assigned and managed by an accounting server and identifying the home device.

In step 508, the home device receives a peer ID, peer group ID and country code from the controller. The peer ID refers to an ID that is managed by a connection server and identifies the home device. The peer group ID refers to an ID that identifies a group of home devices registered to a service server that manages information about the home device. The country code means a code indicating the country information where the user is located.

In step 510, the home device logs in to the connection server using the access token received in step 506, the peer ID, peer group ID, and country code received in step 508.

6 is a flowchart illustrating an operation in which a controller registers a home device with a server in a home network system according to an exemplary embodiment of the present invention.

Referring to FIG. 6, in step 602, the controller receives an authentication code used by the home device to receive an access token from an account server managing a user account of the controller. The controller is a device used for the purpose of controlling the home device, and may be, for example, a mobile terminal such as a smartphone or a TV. The connection token indicates a key value used when the home device connects to the connection server that manages the connection between the home device and the controller period, and the connection server authenticates the use right of the home device.

In step 604, the controller transmits the received authentication code and the user ID for the user of the controller to the home device.

In step 606, the controller transmits the UUID and device information for the home device to the service server that manages the device information for the home device. Here, the UUID and device information are information acquired and managed by the controller through a preliminary procedure of connecting the controller to the controller when the home device is initially installed in the home (or outside the home). In addition, the device information includes, for example, the type, name, description, manufacturer, model ID, serial number, sales region, and version of the home device.

In step 608, the controller receives from the service server a peer ID that is managed at the connection server and identifies the home device.

In step 610, the controller transmits the received peer ID, the peer group ID, and the country code to the home device. The peer ID, peer group ID and country code are used when the home device logs in to the connection server. In addition, the peer group ID and country code are information acquired and managed by the controller through a preliminary procedure of connecting the controller to the controller when the home device is initially installed in the home (or outside the home).

7 is a flowchart illustrating an operation in which a service server registers a home device in a home network system according to an exemplary embodiment of the present invention.

In FIG. 7, the service server is a server operated only for a service provided by a home network system. The service server may store and manage home device device information for circulating information of a home device and other information for controlling the home device. to provide.

Referring to FIG. 7, in step 702, the service server receives and registers a UUID and device information about a home device from a controller. The device information includes, for example, the type, name, description, manufacturer, model ID, serial number, sales region, and version of the home device.

In step 704, the service server transmits a peer ID to be used by the home device to log in to the connection server that manages the connection between the home device and the controller. Here, the peer ID refers to an ID managed by the connection server and identifying the home device.

8 is a flowchart illustrating an operation in which an account server registers a home device in a home network system according to an embodiment of the present invention.

In FIG. 8, the account server is a server that manages an account for a user of a controller device. When the user logs in to the account server, the account server provides a function of connecting to a service server and a connection server using user login information. In addition, the account server is a public server that can be used for other services in addition to the services provided by the home network system.

Referring to FIG. 8, in step 802, the account server transmits an authentication code used for the home device to receive an access token to the controller. Here, the connection token indicates a key value used when the home device connects to the connection server that manages the connection between the home device and the controller period, and the connection server authenticates the use right of the home device.

In step 804, the account server receives the authentication code and the user ID for the user of the controller device from the home device.

In step 806, the account server checks whether the controller authentication code sent in step 802 and the home device authentication code received in step 804 are the same. If the controller device authentication code and the home device authentication code is the same as the result of step 806, the account server proceeds to step 808 and transmits an access token, a refresh token, and a GUID to the home device. The access token is used when the home device logs in to the connection server. The refresh token is also used to update the connection token within the validity period so that the connection token can be used even after a previously promised validity period has elapsed. The GUID means an ID assigned and managed by an accounting server and identifying the home device.

If the controller device authentication code is not the same as the home device authentication code in step 806, the account server proceeds to step 802 and transmits an authentication code used to receive the access token to the controller device.

9 is a flowchart illustrating an operation of registering a home device by a connection server in a home network system according to an exemplary embodiment of the present invention.

In FIG. 9, the connection server is a server providing a service for establishing a communication channel for transmitting a controller period message with a home device. Connection Server also provides presence information that indicates whether a connection can be made between a home device and a controller, and provides NAT-T functionality that allows remote connections across firewalls. Connection Server is also a common server that can be used for other services in addition to the services provided by home network systems.

In FIG. 9, it is assumed that the controller is logged in to the connection server.

Referring to FIG. 9, in operation 902, the connection server receives a login request using a peer ID, a peer group ID, a country code, and an access token from the home device. Here, the peer ID refers to an ID that is managed by a connection server and identifies the home device, and the peer group ID refers to an ID that identifies a group of home devices registered to a service server that manages information about the home device. The code refers to a code indicating the country information where the user is located, and the access token refers to a token used to authenticate the use right of the home device.

In step 904, the connection server transmits a login response to the home device indicating that the login is successful in response to the login request in step 902.

In step 906, the connection server notifies the controller of home device connection information including presence information indicating whether a connection between the home device and the controller device is possible. The presence information may be, for example, information indicating that the home device is logged in to the connection server. The home device connection information includes not only the presence information but also information on an IP address and a port used by the home device, network type information used by the home device, and the like. The network type information may be, for example, information related to Wi-Fi, information related to 2G, information related to 3G, information related to 4G, and the like.

In an embodiment of the present invention, an example of registering device information of a home device in a service server through a controller is described. In another embodiment of the present invention to be described below, an example of directly registering device information of a home device in a service server without using a controller device will be described.

FIG. 10 is a diagram illustrating a flow of information exchanged for registering a home device with a server in a home network system according to another exemplary embodiment of the present invention.

Referring to FIG. 10, the illustrated home network system includes a home device 1001, a controller 1003, a service server 1005, an account server 1007, and a connection server 1009.

Examples and functions of the home device 1001, the controller 1003, the service server 1005, the account server 1007, and the connection server 1009 have been described in detail with reference to FIG. 1, so that detailed description thereof will be omitted herein. do.

The controller 1003 executes the smart home app according to the user input and automatically logs in to the account server 1007 at the same time as the execution of the smart home app.

When the accounting server 1007 receives the authentication code request from the controller 1003, the accounting server 1007 issues an authentication code in response to the request and transmits the authentication code to the controller 1003 (step 1004). 101 is used to register with the service server 105, and in particular represents the key value used by the home device 1001 to receive a connection token from the account server 1007. The connection token indicates a key value used when the home device 1001 connects to the connection server 1009 so that the connection server 1009 authenticates the use authority of the home device 1001.

In addition, the controller 1003 transmits the authentication code and the user ID received in step 1004 to the home device 1001 through an account server registration request (step 1006). Here, the user ID is an e-mail ID, nickname, social security number, for example. It can be any one of the phone numbers.

In order to receive the access token and the refresh token, the home device 1001 transmits the authentication code and the user ID received in step 1006 to the account server 1007 (step 1008).

The account server 1007 checks the authentication code and the user ID received in step 1008 and verifies whether the received authentication code is an authentication code normally issued to the user indicated by the user ID. That is, the account server 1007 checks whether the received authentication code is the same as the authentication code issued in step 1004. If the received authentication code is the same as the authentication code issued in step 1004, the account server 1007 determines that the received authentication code is the authentication code normally issued to the user and accesses the home device 1001. The token, the refresh token, and the GUID are transmitted (step 1010). Here, the GUID refers to an identifier separately assigned by the accounting server 1007 for identification of the home device 1001.

The controller 1003 receives, from the service server 1005, server information including information related to the connection to the service server 1005. (Step 1012) The server information is, for example, a service server 1005. It may be address information for accessing the network. In addition, the controller 1003 transmits the server information and the country code received from the service server 1005 to the home device 1001. (Step 1016) The country code transmits the home device 1001 to the home (or home). In addition, information obtained from the home device 1001 through a preliminary procedure of connecting to the controller 1003 at the time of initial installation.

The home device 1001 accesses the service server 1005 using information related to the connection to the service server 1005 included in the server information received in step 1016, and accesses the device information of the home device 1001 to the service server ( The home device 1001 receives a peer ID and a peer group ID from the service server 1005. (Step 1018) The device information of the home device 1001 is registered. And the peer group ID is information obtained from the home device 1001 through a preliminary procedure of connecting the home device 1001 with the controller 1003 when the home device 1001 is initially installed in the home (or the home). The peer ID refers to an identifier assigned by the service server 1005 so that the connection server 1009 can identify the home device 1001. At this time, the service server 1005 allocates a unique ID to each home device located in the home (or outside the home).

Thereafter, the home device 1001 logs in to the connection server 1009 using the access token received in step 1010, the country code received in step 1016, and the peer ID and peer group ID received in step 1018. 1020 steps)

11 is a flowchart illustrating an operation of registering a home device with a server in a home network system according to another exemplary embodiment of the present invention.

In FIG. 11, it is assumed that the home device is home devices located in the home (or out of home), and in FIG. 11, operation after completion of the D2D authentication procedure between the home device and the controller device will be described. Since the D2D authentication procedure is far from the content to be described in another embodiment of the present invention, a detailed description thereof will be omitted.

In addition, in FIG. 11, an operation of registering one home device among home devices located in a home (or outside home) with a server is described as an example. However, the operation described in FIG. The same applies to the operation of registering the server with the server.

Referring to FIG. 11, in step 1102, the home device receives, from the controller device, an authentication code used to receive an access token and a user ID for a user of the controller device. Here, the home device means a device located in the home (or outside the home) and can be controlled through the controller, and is a home appliance, a security device, a lighting device, an energy device, a PC, an IP camera, an internet phone, a wired / wireless Telephones, electrically controllable curtains, blinds and the like. The connection token indicates a key value used when the home device connects to the connection server that manages the connection between the home device and the controller period, and the connection server is used to authenticate the use right of the home device.

In step 1104, the home device transmits the received authentication code and the user ID to an account server that manages the account for the user.

In step 1106, the home device receives a connection token, a refresh token and a GUID from the account server. The refresh token refers to a token used to renew the access token within the validity period so that the access token can be used even after a previously promised validity period has elapsed. The GUID means an ID assigned and managed by an accounting server and identifying the home device.

In step 1108, the home device receives the server information and the country code from the controller. The server information includes information related to a connection to a service server, and the server information may be, for example, address information for access to a service server. The country code means a code indicating the country information where the user is located.

In step 1110, the home device accesses a service server using information related to the connection to the service server, and receives a peer ID and a peer group ID from the service server. The peer ID refers to an ID that is managed by a connection server and identifies the home device, and the peer group ID refers to an ID that identifies a group of home devices registered to a service server that manages information about the home device.

In step 1112, the home device logs in to the connection server using the access token received in step 1106, the peer ID and peer group ID received in step 1110, and the country code received in step 1108.

12 is a flowchart illustrating an operation in which a controller registers a home device with a server in a home network system according to an embodiment of the present invention.

Referring to FIG. 12, in step 1202, the controller receives an authentication code used by the home device to receive an access token from an account server managing a user account of the controller. The controller is a device used for the purpose of controlling the home device, and may be, for example, a mobile terminal such as a smartphone or a TV. The connection token indicates a key value used when the home device connects to the connection server that manages the connection between the home device and the controller period, and the connection server authenticates the use right of the home device.

In step 1204, the controller transmits the received authentication code and the user ID for the user of the controller to the home device.

In step 1206, the controller receives server information from the service server. The server information includes information related to a connection to a service server, and the server information may be, for example, address information for access to a service server.

In step 1208, the controller transmits the server information and the country code to the home device. The country code means a code indicating the country information where the user is located.

13 is a flowchart illustrating an operation of registering a home device by a service server in a home network system according to another exemplary embodiment of the present invention.

In FIG. 13, the service server is a server operated only for a service provided by a home network system. The service server stores and manages home device device information for circulating information of a home device and other information for controlling the home device. to provide.

Referring to FIG. 13, in step 1302, the service server transmits server information to a control device. The server information includes information related to a connection to a service server, and the server information may be, for example, address information for access to a service server.

In operation 1304, the service server receives and registers device information of the home device from the home device. The device information includes, for example, the type, name, description, manufacturer, model ID, serial number, sales region, and version of the home device.

In operation 1306, the service server transmits a peer ID and a peer group ID to the home device. The peer ID refers to an ID that is managed by a connection server and identifies the home device, and the peer group ID refers to an ID that identifies a group of home devices that a user registers with a service server that manages device information about the home device. it means.

FIG. 14 is an apparatus diagram illustrating an internal configuration of a home device registering with a server in a home network system according to an exemplary embodiment of the present invention.

Referring to FIG. 14, the illustrated home device 1400 includes a transmitter 1410, a receiver 1420, a controller 1430, and a storage 1440.

The receiving unit 1420 of the home device 1400 receives an authentication code used to receive the access token transmitted from the controller device and a user ID of the user of the controller device. Here, the access token indicates a key value used when the home device 1400 connects to the connection server that manages the connection between the home device 1400 and the controller period, and the connection server authenticates the use right of the home device.

The transmitter 1410 of the home device 1400 transmits the authentication code and the user ID received through the receiver 1420 to an account server that manages an account for the user.

The receiver 1420 of the home device 1400 receives an access token, a refresh token, and a GUID transmitted from an account server, and a peer ID, a peer group ID, and a country code transmitted from a controller. Here, the refresh token means a token used to update the access token within the validity period so that the access token can be used even after a predetermined validity period has elapsed, and a GUID is assigned and managed by an account server and the home device is assigned. ID to identify. In addition, the peer ID refers to an ID that is managed by a connection server and identifies the home device, and the peer group ID refers to an ID that identifies a group of home devices registered to a service server that manages information about the home device, and a country The code means a code indicating the country information where the user is located.

Meanwhile, the receiver 1420 of the home device 1400 may receive server information transmitted from the controller device. In this case, the peer ID and the peer group ID may be received from the service server rather than the controller device. The server information includes information related to a connection to a service server, and the server information may be, for example, address information for access to a service server.

The home device 1400 logs in to the connection server using the access token, the peer ID, the peer group ID, and the country code received through the receiver 1420. At this time, the control unit 1430 of the home device controls the transmitter 1410 and the receiver 1420 so that the home device can log in to the connection server, and the information transmitted and received through the transmitter 1410 and the receiver 1420 It is stored in the storage unit 1440.

FIG. 15 is an apparatus diagram illustrating an internal configuration of a controller for registering a home device with a server in a home network system according to an exemplary embodiment of the present invention.

Referring to FIG. 15, the illustrated controller 1500 includes a transmitter 1510, a receiver 1520, a controller 1530, and a storage 1540.

The receiver 1520 of the controller 1500 receives an authentication code transmitted from an account server that manages an account for the user of the controller 1500. The authentication code refers to a code used by a home device to receive a connection token, wherein the connection token is a home device when the home device connects to a connection server that manages a connection between the home device and a controller period. Represents a key value used to authenticate the permissions of a.

The transmitter 1510 of the controller 1500 transmits the authentication code received through the receiver 1520 and the user ID of the user of the controller 1500 to the home device, and the UUID and device information for the home device. To the service server managing the device information for the home device. Here, the UUID and the device information are information acquired and managed by the controller 1500 through a preliminary procedure of connecting the controller 1500 when the home device is initially installed in the home (or outside the home). That is, the controller 1500 obtains UUID and device information about the home device and stores the information in the storage unit 1540. In addition, the device information includes, for example, the type, name, description, manufacturer, model ID, serial number, sales region, and version of the home device. The receiver 1520 of the controller 1500 receives a peer ID transmitted from the service server. Here, the peer ID means an ID managed by the connection server and identifying the home device.

The transmitter 1510 of the controller 1500 transmits the peer ID received through the receiver 1520 and the peer group ID and the country code to the home device. The peer group ID and country code are information acquired and managed by the controller 1500 through a preliminary procedure of connecting with the controller 1500 when the home device is initially installed in the home (or outside the home). . That is, the controller 1500 obtains a peer group ID and a country code and stores the information in the storage unit 1540.

Meanwhile, the controller 1500 may receive server information other than the peer ID through the receiver 1520. In this case, the transmitter 1110 of the controller 1500 transmits the server information and the country code to the home device. . The server information includes information related to a connection to a service server, and the server information may be, for example, address information for access to a service server.

The controller 1530 of the controller 1500 controls operations of the transmitter 1510 and the receiver 1520, and the information transmitted and received by the transmitter 1510 and the receiver 1520 is stored in the storage 1540.

16 is an apparatus diagram illustrating an internal configuration of a service server that registers a home device in a home network system according to an embodiment of the present invention.

Referring to FIG. 16, the illustrated service server 1600 includes a transmitter 1610, a receiver 1620, a controller 1630, and a storage 1640.

The receiver 1620 of the service server 1600 receives a UUID and device information about a home device transmitted from a controller. The device information includes, for example, the type, name, description, manufacturer, model ID, serial number, sales region, and version of the home device.

The transmitter 1610 of the service server 1600 transmits a peer ID to be used by the home device to log in to the connection server that manages the connection between the home device and the controller. Here, the peer ID refers to an ID managed by the connection server and identifying the home device.

Meanwhile, the transmitter 1610 of the service server 1600 may transmit server information other than the peer ID. In this case, the receiving unit 1620 of the service server 1600 receives the device information of the home device from the home device and registers the information in the storage unit 1640, and the transmitting unit 1610 of the service server 1600 is a peer ID and a peer group. Send the ID to the home device. The server information includes information related to a connection to a service server, and the server information may be, for example, address information for access to a service server. The device information includes, for example, the type, name, description, manufacturer, model ID, serial number, sales region, and version of the home device. The peer group ID refers to an ID for identifying a group of home devices registered in the storage 1640 of the service server 1600.

The controller 1630 of the service server 1600 controls operations of the transmitter 1610 and the receiver 1620, and the information transmitted and received by the transmitter 1610 and the receiver 1620 is stored in the storage 1640.

17 is an apparatus diagram illustrating an internal configuration of an account server that registers a home device in a home network system according to an embodiment of the present invention.

Referring to FIG. 17, the illustrated account server 1700 includes a transmitter 1710, a receiver 1720, a controller 1730, and a storage 1740.

The transmitter 1710 of the account server 1700 transmits an authentication code used by the home device to receive the access token to the controller. Here, the connection token indicates a key value used when the home device connects to the connection server that manages the connection between the home device and the controller period, and the connection server authenticates the use right of the home device.

The receiver 1720 of the account server 1700 receives an authentication code transmitted from a home device and a user ID of a user of the controller device.

The controller 1730 of the account server 1700 checks whether the controller authentication code transmitted from the transmitter 1710 and the home device authentication code received from the receiver 1720 are the same. If the controller device authentication code and the home device authentication code is the same, the controller 1730 controls the transmitter 1710 to transmit the access token, the refresh token, and the GUID. That is, the transmitter 1710 of the account server 1700 transmits the access token, the refresh token, and the GUID to the home device under the control of the controller 1730. The access token is used when the home device logs in to the connection server. In addition, the refresh token refers to a token used to renew the access token within the validity period so that the access token can be used even after a predetermined validity period has elapsed. The GUID means an ID assigned and managed by an accounting server and identifying the home device.

The controller 1730 of the account server 1700 controls the operations of the transmitter 1710 and the receiver 1720, and information transmitted and received through the transmitter 1710 and the receiver 1720 is stored in the storage 1740. .

18 is an apparatus diagram illustrating an internal configuration of a connection server that registers a home device in a home network system according to an embodiment of the present invention.

Referring to FIG. 18, the illustrated connection server 1800 includes a transmitter 1810, a receiver 1820, a controller 1830, and a storage 1840.

The receiving unit 1820 of the connection server 1800 receives a login request transmitted from a home device using a peer ID, a peer group ID, a country code, and a connection token. Here, the peer ID refers to an ID that is managed by the connection server and identifies the home device, and the peer group ID identifies a group of home devices registered by a user of a controller device to a service server that manages device information about the home device. An ID means a country code, a code indicating a country information where the user is located, and an access token means a token used for authenticating a use right of the home device.

The receiver 1820 of the connection server 1800 receives a login request. The transmitting unit 1810 of the connection server 1800 transmits a login response indicating that the login is successful in response to the login request to the home device, and includes a home device including information indicating whether a connection between the home device and the controller device is possible. Notify the controller to the connection information. The information indicating whether the connection between the home device and the controller device is possible may be, for example, information indicating that the home device is logged in to the connection server. The home device connection information includes not only information indicating that the home device is logged in to the connection server, but also information on an IP address and port used by the home device, network type information used by the home device, and the like. The network type information may be, for example, information related to Wi-Fi, information related to 2G, information related to 3G, information related to 4G, and the like.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications may be made without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the scope of the following claims, but also by the equivalents of the claims.

In addition, it will be appreciated that an apparatus and method for registering a home device according to an embodiment of the present invention may be realized in the form of hardware, software, or a combination of hardware and software. Any such software may be, for example, volatile or nonvolatile storage, such as a storage device such as a ROM, whether or not removable or rewritable, or a memory such as, for example, a RAM, a memory chip, a device or an integrated circuit. Or, for example, CD or DVD, magnetic disk or magnetic tape and the like can be stored in a storage medium that is optically or magnetically recordable and simultaneously readable by a machine (eg computer). The graphic screen updating method of the present invention may be implemented by a computer or a portable terminal including a control unit and a memory, wherein the memory is a machine suitable for storing a program or programs including instructions for implementing embodiments of the present invention. It will be appreciated that this is an example of a readable storage medium.

Accordingly, the present invention includes a program comprising code for implementing the apparatus or method described in any claim herein and a storage medium readable by a machine (such as a computer) storing such a program. In addition, such a program can be transferred electronically through any medium, such as a communication signal transmitted over a wired or wireless connection, and the invention suitably includes equivalents thereof.

In addition, the apparatus for registering a home device according to an embodiment of the present invention to a server may receive and store the program from a program providing apparatus connected by wire or wirelessly. The program providing apparatus may perform a wired or wireless communication with a program for storing a program including instructions for causing the graphic processing apparatus to perform a preset content protection method, information necessary for the content protection method, and the like. And a controller for transmitting the program to the transceiver device automatically or at the request of the graphic processing device.

Claims (15)

  1. In the method of registering a home device with a server in a home network system,
    Receiving an access token from an account server managing an account for the control device,
    Receiving a peer identifier (peerID) identifying the home device and a peer group ID (peergroupID) identifying a group of home devices from the control device;
    Logging in to a connection server managing a connection between the home device and the control device based on the access token, peer ID, and peer group ID.
  2. The method of claim 1,
    Receiving, from the control device, server information including information related to a connection to the service server;
    Receiving the peer group ID and the peer ID from the service server,
    The peer group ID and the peer ID received from the service server are used instead of the peer group ID and the peer ID received from the control device.
  3. The method of claim 1,
    Receiving a refresh token used to update the access token, and a globally unique ID (GUID) assigned and managed by the account server and identifying the home device from the account server. How to include.
  4. In the home network system, the control device registers the home device to the server,
    Receiving a peer identifier (ID) identifying a home device from a service server managing device information on the home device;
    Transmitting the peer ID and a peer group ID identifying a group of home devices to the home device.
  5. The method of claim 4, wherein
    Receiving server information including information related to a connection from the service server to the service server;
    Transmitting the server information to the home device instead of the peer ID and the peer group ID.
  6. The method of claim 4, wherein
    Transmitting a unique user ID (UUID) for the home device and the device information to the service server;
    The UUID, the device information and the peer group ID for the home device are obtained and managed through a preliminary procedure of connecting to the control device when the home device is initially installed in or outside the home.
  7. The method of claim 4, wherein
    Receiving, by the home device, an authentication code used to receive an access token from an account server managing an account for the control device, and transmitting the authentication code to the home device;
    And wherein the access token includes a key value used when the home device connects to the connection server, the connection server used to authenticate the use right of the home device.
  8. In the home network system, the service server registers a home device,
    The service device managing the device information for the home device, the control device to the peer ID (peerID) to be used when the home device to log in to the connection server that manages the connection between the home device and the control device To send to
    The peer ID is an ID for identifying the home device.
  9. The method of claim 8,
    Transmitting server information including information related to a connection to the service server instead of transmitting the peer ID to the control device, to the control device;
    And receiving the device information on the home device from the home device.
  10. In the method for the account server to register the home device in a home network system,
    Transmitting, by the accounting server managing the account for the controller device, an authentication code to the control device;
    Receiving an authentication code and a user identifier (ID) for the control device from the home device;
    Check whether the authentication code received from the home device is the same as the authentication code transmitted to the control device, and if the two authentication codes are the same, the home device manages the connection between the home device and the control device. And transmitting an access token to be used at login to the home device.
  11. The method of claim 10,
    And transmitting a refresh token used to update the access token, and a globally unique identifier (GUID) that is assigned and managed by the accounting server and identifies the home device to the home device. How to.
  12. The method according to claim 1 or 10.
    And wherein the access token includes a key value used when the home device connects to the connection server, the connection server used to authenticate the use right of the home device.
  13. A method for registering a home device by a connection server in a home network system, the method comprising:
    The connection server managing the connection between the home device and the control device includes a peer identifier (ID) identifying the home device, a peer group ID identifying a group of home devices, and Receiving a login request from the home device using a connection token used to authenticate a home device's usage rights,
    And transmitting a login response corresponding to the login request to the home device.
  14. The method of claim 13,
    If the home device is logged in to the connection server, further comprising notifying the control device of home device connection information including information indicating whether a connection between the home device and the control device is possible;
    The information indicating whether the connection between the home device and the control device is possible includes the information indicating whether the home device is logged in to the connection server.
  15. An apparatus adapted for carrying out the method of claim 1.
PCT/KR2014/012562 2013-12-20 2014-12-19 Apparatus and method for registering home device in server in home network system WO2015093887A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR10-2013-0160650 2013-12-20
KR20130160650 2013-12-20
KR10-2014-0101259 2014-08-06
KR1020140101259A KR20150073827A (en) 2013-12-20 2014-08-06 Apparatus and method for registrating a home device to a server in a home network system

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US15/106,028 US9992677B2 (en) 2013-12-20 2014-12-19 Apparatus and method for registering home device in server in home network system
CN201480069653.3A CN105850076B (en) 2013-12-20 2014-12-19 The device and method of household equipment are registered in server in domestic network system
EP14872138.4A EP3086506B1 (en) 2013-12-20 2014-12-19 Apparatus and method for registering home device in server in home network system

Publications (1)

Publication Number Publication Date
WO2015093887A1 true WO2015093887A1 (en) 2015-06-25

Family

ID=53403140

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2014/012562 WO2015093887A1 (en) 2013-12-20 2014-12-19 Apparatus and method for registering home device in server in home network system

Country Status (1)

Country Link
WO (1) WO2015093887A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018190637A1 (en) * 2017-04-11 2018-10-18 삼성전자주식회사 Method for establishing communication connection of device and apparatus therefor
US10567381B1 (en) * 2015-12-17 2020-02-18 Amazon Technologies, Inc. Refresh token for credential renewal

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030177271A1 (en) * 2002-03-12 2003-09-18 Samsung Electronics Co., Ltd. Apparatus for providing device information via network and a method thereof
US20050149758A1 (en) * 2004-01-06 2005-07-07 Samsung Electronics Co., Ltd. Authentication apparatus and method for home network devices
KR20080068587A (en) * 2007-01-19 2008-07-23 소니 가부시끼 가이샤 Network system, access management server, event notification method, network appliance and computer program
US20100125652A1 (en) * 2008-11-14 2010-05-20 Olli Rantapuska Method, Apparatus, and Computer Program for Binding Local Devices to User Accounts
US20130227660A1 (en) * 2010-11-05 2013-08-29 Telefonaktiebolaget L M Ericsson (Publ) Registration server, gateway apparatus and method for providing a secret value to devices

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030177271A1 (en) * 2002-03-12 2003-09-18 Samsung Electronics Co., Ltd. Apparatus for providing device information via network and a method thereof
US20050149758A1 (en) * 2004-01-06 2005-07-07 Samsung Electronics Co., Ltd. Authentication apparatus and method for home network devices
KR20080068587A (en) * 2007-01-19 2008-07-23 소니 가부시끼 가이샤 Network system, access management server, event notification method, network appliance and computer program
US20100125652A1 (en) * 2008-11-14 2010-05-20 Olli Rantapuska Method, Apparatus, and Computer Program for Binding Local Devices to User Accounts
US20130227660A1 (en) * 2010-11-05 2013-08-29 Telefonaktiebolaget L M Ericsson (Publ) Registration server, gateway apparatus and method for providing a secret value to devices

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
None
See also references of EP3086506A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10567381B1 (en) * 2015-12-17 2020-02-18 Amazon Technologies, Inc. Refresh token for credential renewal
WO2018190637A1 (en) * 2017-04-11 2018-10-18 삼성전자주식회사 Method for establishing communication connection of device and apparatus therefor

Similar Documents

Publication Publication Date Title
WO2016076586A1 (en) Mobile terminal and controlling method thereof
US9503896B2 (en) Processing method of wireless network device, wireless network device, and processor of wireless network device
WO2018052251A1 (en) Method, apparatus, and system for sharing virtual reality viewport
WO2014119889A1 (en) Method of displaying user interface on device, and device
WO2014088236A1 (en) Method and mobile terminal for controlling screen lock
WO2015119394A1 (en) Home appliance, network connection system for home appliance and network connection method of home appliance
WO2014092486A1 (en) Device and method for reproducing content in home network system
WO2014007516A1 (en) Single certificate service system and operational method thereof
WO2014157886A1 (en) Method and device for executing application
WO2016024695A1 (en) Method and apparatus for profile download of group devices
WO2013042803A1 (en) Electronic device and method for controlling the same
WO2012112011A2 (en) Method and apparatus for the seamless playback of content
WO2014175689A1 (en) Communication service in communication modes
WO2013065915A1 (en) Method for interworking trust between a trusted region and an untrusted region, method, server, and terminal for controlling the downloading of trusted applications, and control system applying same
WO2017142386A1 (en) Antenna and electronic device including the same
WO2013151374A1 (en) Method and system for transfering data between plurality of devices
US9426118B2 (en) Remote grant of network access
WO2016013827A1 (en) Method and device for embedded sim provisioning
EP3235182A1 (en) Method and apparatus for controlling device using a service rule
EP3420706A1 (en) Server and method of controlling user environment by server
WO2014104752A1 (en) Service providing terminal connection method and apparatus
WO2013048024A1 (en) Method and apparatus for communication connection service
WO2015034163A1 (en) Method of providing notification and electronic device thereof
US8244212B2 (en) Communication method, communication apparatus, cell phone terminal, and communication system for performing connection via a network
WO2016060370A1 (en) Terminal for internet of things and operation method of the same

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14872138

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15106028

Country of ref document: US

NENP Non-entry into the national phase in:

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014872138

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014872138

Country of ref document: EP