Method for managing and controlling external IoT device and electronic device supporting the same

This application isbased on anda reissue divisional of U.S. application Ser. No. 17/587,085, filed Jan. 28, 2022, which is an application for reissue of U.S. application Ser. No. 15/935,472, filed Mar. 26, 2018 (now U.S. Pat. No. 10,547,731), whichclaims priority under 35 U.S.C. § 119 to Korean Patent Application No. 10-2017-0039912, filed on Mar. 29, 2017, in the Korean Intellectual Property Office, the disclosure of which is incorporated by reference herein its entirety.

Various embodiments of the present disclosure relate to a method for managing and controlling an external Internet-of-Things (IoT) device and an electronic device supporting the same.

Internet of Things (hereinafter, referred to as IoT) technology has been developed. Various types of things may include a wireless communication module and may transmit and receive data with another device in real time through the communication module. For example, various IoT devices may be present in a house. TV, an air conditioner, an air cleaner, a vacuum cleaner, a light, or the like to which IoT technology is applied may be present in a living room, and a refrigerator, an oven, a light, or the like to which IoT technology is applied may be present in a kitchen.

The IoT devices may transmit and receive data by using wireless communication technologies, such as ZigBee®, Z-Wave®, BT/BLE®, Wi-Fi®, a cellular network (e.g., 3G or LTE), or the like. Each of the wireless communication technologies may have various characteristics in configuring a usable frequency, a data rate, a transmission distance, power consumption, and network topology.

An electronic device (e.g., a smartphone) that integrally manages the IoT devices may establish communication with IoT devices within a specified range and may store information beneficial for control. For example, the electronic device may execute an application for managing IoT devices. The application may output a UI capable of registering or removing a new IoT device.

The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present disclosure.

In the related art, IoT devices existing in various spaces (e.g., a living room or a room in a house, an office, or the like) may be operated through operating devices (e.g., remote controllers) in conjunction with the respective spaces.

Alternatively, the IoT devices may be operated by an electronic device (e.g., a smartphone) in which applications operating in conjunction with the IoT devices are installed. In this case, another electronic device in which an application capable of managing and controlling an IoT device is not installed has to repeatedly install applications, search for a plurality of IoT devices, and establish connections to manage and control the plurality of IoT devices.

Aspects of the present disclosure are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present disclosure is to provide a method in which an electronic device managing a plurality of IoT devices shares setting information for managing the plurality of IoT devices with an external device, and an electronic device that supports the same.

In accordance with an aspect of the present disclosure, an electronic device includes a display, a wireless communication circuit, a processor, and a memory. The memory includes instructions executable by the processor to establish wireless communication with one or more IoT devices by using the wireless communication circuit, display a user interface for managing a plurality of including the one or more IoT devices through the display, receive a user input selecting a group of IoT devices from among the one or more IoT devices, transmit first information including user account data of the electronic device to a first external server using the wireless communication circuit, transmit second information to another electronic device using the wireless communication circuit, wherein the first information includes information indicating the selected group and the user account data of the electronic device, and wherein the second information causes the other electronic device to communicatively connect with the first external server and control one or more IoT devices included in the selected group.

In an aspect of the present disclosure, an electronic device is disclosed including a display, a wireless communication circuit, a processor and a memory. the memory stores instructions executable by the processor to: receive at least one of a push message through a first application for managing one or more Internet-of-Things (IoT) devices from a first external server and an SMS message related to the first application from a second external server, and when the first application is executed, receive, from the first external server, setting information for controlling the one or more IoT devices by another electronic device.

In an aspect of the present disclosure, an electronic device is disclosed including a display, a communication circuit, a memory and a processor. The processor establishes wireless communication with one or more Internet-of-Things (IoT) devices using the communication circuit, transmits setting information associated with the one or more IoT devices to an external server using the communication circuit, and transmits a request signal including first user account information and second user account information to the external server, wherein at least a portion of the transmitted setting information is included in the transmitted request signal and is further transmitted to another electronic device, wherein the first user account information indicates at least a first user registered to the electronic device, and wherein the second user account information indicates at least a second user registered to the other electronic device.

A device management method and an electronic device supporting the same, according to various embodiments of the present disclosure, may share setting information related to an IoT device with an external electronic device.

A device management method and an electronic device supporting the same, according to various embodiments of the present disclosure, may transmit an invitation message to an external electronic device by using a user account or a telephone number of an application that manages an IoT device.

A device management method and an electronic device supporting the same, according to various embodiments of the present disclosure, may safely share information and authority relating to control of an IoT device with an external electronic device through an authentication process.

Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the present disclosure.

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

Hereinafter, various embodiments of the present disclosure will be described with reference to the accompanying drawings. Accordingly, those of ordinary skill in the art will recognize that modification, equivalent, and/or alternative on the various embodiments described herein can be variously made without departing from the present disclosure. With regard to description of drawings, similar components may be marked by similar reference numerals.

In the disclosure disclosed herein, the expressions “have”, “may have”, “include” and “comprise”, or “may include” and “may comprise” used herein indicate existence of corresponding features (for example, elements such as numeric values, functions, operations, or components) but do not exclude presence of additional features.

1 2 3 In the disclosure disclosed herein, the expressions “A or B”, “at least one of A or/and B”, or “one or more of A or/and B”, and the like used herein may include any and all combinations of one or more of the associated listed items. For example, the term “A or B”, “at least one of A and B”, or “at least one of A or B” may refer to all of the case () where at least one A is included, the case () where at least one B is included, or the case () where both of at least one A and at least one B are included.

The terms, such as “first”, “second”, and the like used herein may refer to various elements of various embodiments of the present disclosure, but do not limit the elements. For example, such terms are used only to distinguish an element from another element and do not limit the order and/or priority of the elements. For example, a first user device and a second user device may represent different user devices irrespective of sequence or importance. For example, without departing the scope of the present disclosure, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element.

It will be understood that when an element (for example, a first element) is referred to as being “(operatively or communicatively) coupled with/to” or “connected to” another element (for example, a second element), it can be directly coupled with/to or connected to the other element or an intervening element (for example, a third element) may be present. In contrast, when an element (for example, a first element) is referred to as being “directly coupled with/to” or “directly connected to” another element (for example, a second element), it should be understood that there are no intervening element (for example, a third element).

According to the situation, the expression “configured to” used herein may be used as, for example, the expression “suitable for”, “having the capacity to”, “designed to”, “adapted to”, “made to”, or “capable of”. The term “configured to (or set to)” must not mean only “specifically designed to” in hardware. Instead, the expression “a device configured to” may mean that the device is “capable of” operating together with another device or other components. CPU, for example, a “processor configured to (or set to) perform A, B, and C” may mean a dedicated processor (for example, an embedded processor) for performing a corresponding operation or a generic-purpose processor (for example, a central processing unit (CPU) or an application processor) which may perform corresponding operations by executing one or more software programs which are stored in a memory device.

Terms used in this specification are used to describe specified embodiments of the present disclosure and are not intended to limit the scope of the present disclosure. The terms of a singular form may include plural forms unless otherwise specified. Unless otherwise defined herein, all the terms used herein, which include technical or scientific terms, may have the same meaning that is generally understood by a person skilled in the art. It will be further understood that terms, which are defined in a dictionary and commonly used, should also be interpreted as is customary in the relevant related art and not in an idealized or overly formal detect unless expressly so defined herein in various embodiments of the present disclosure. In some cases, even if terms are terms which are defined in the specification, they may not be interpreted to exclude embodiments of the present disclosure.

An electronic device according to various embodiments of the present disclosure may include at least one of smartphones, tablet personal computers (PCs), mobile phones, video telephones, electronic book readers, desktop PCs, laptop PCs, netbook computers, workstations, servers, personal digital assistants (PDAs), portable multimedia players (PMPs), MP3 players, mobile medical devices, cameras, and wearable devices. According to various embodiments of the present disclosure, the wearable devices may include accessories (for example, watches, rings, bracelets, ankle bracelets, glasses, contact lenses, or head-mounted devices (HMDs)), cloth-integrated types (for example, electronic clothes), body-attached types (for example, skin pads or tattoos), or implantable types (for example, implantable circuits).

In some embodiments of the present disclosure, the electronic device may be one of home appliances. The home appliances may include, for example, at least one of a digital video disk (DVD) player, an audio, a refrigerator, an air conditioner, a cleaner, an oven, a microwave oven, a washing machine, an air cleaner, a set-top box, a home automation control panel, a security control panel, a TV box (for example, Samsung HomeSync™, Apple TV™, or Google TV™), a game console (for example, Xbox™ or Play Station™), an electronic dictionary, an electronic key, a camcorder, or an electronic panel.

In another embodiment of the present disclosure, the electronic device may include at least one of various medical devices (for example, various portable medical measurement devices (a blood glucose meter, a heart rate measuring device, a blood pressure measuring device, and a body temperature measuring device), a magnetic resonance angiography (MRA), a magnetic resonance imaging (MRI) device, a computed tomography (CT) device, a photographing device, and an ultrasonic device), a navigation system, a global navigation satellite system (GNSS), an event data recorder (EDR), a flight data recorder (FDR), a vehicular infotainment device, electronic devices for vessels (for example, a navigation device for vessels and a gyro compass), avionics, a security device, a vehicular head unit, an industrial or home robot, an automatic teller's machine (ATM) of a financial company, a point of sales (POS) of a store, or an internet of things (for example, a bulb, various sensors, an electricity or gas meter, a spring cooler device, a fire alarm device, a thermostat, an electric pole, a toaster, a sporting apparatus, a hot water tank, a heater, and a boiler).

According to some embodiments of the present disclosure, the electronic device may include at least one of a furniture or a part of a building/structure, an electronic board, an electronic signature receiving device, a projector, or various measurement devices (for example, a water service, electricity, gas, or electric wave measuring device). In various embodiments of the present disclosure, the electronic device may be one or a combination of the aforementioned devices. The electronic device according to some embodiments of the present disclosure may be a flexible electronic device. Further, the electronic device according to an embodiment of the present disclosure is not limited to the aforementioned devices, but may include new electronic devices produced due to the development of technologies.

Hereinafter, electronic devices according to an embodiment of the present disclosure will be described with reference to the accompanying drawings. The term “user” used herein may refer to a person who uses an electronic device or may refer to a device (for example, an artificial electronic device) that uses an electronic device.

1 1 FIGS.A andB illustrate an IoT device management system according to various embodiments.

1 1 FIGS.A andB 100 110 120 130 100 140 150 160 Referring to, an IoT device management systemmay include a first electronic device or host device, a second electronic device, and an IoT server. According to various embodiments, the IoT device management systemmay further include a message transfer server (e.g., an SMS server), an application market server, and an authentication server.

110 111 110 111 110 111 110 111 The first electronic device or host device(hereinafter, referred to as the ‘host device’) (e.g., a smartphone or a tablet PC) may manage various IoT devices. For example, the host devicemay discover the IoT devicesaround the host deviceand may establish communication with each of the IoT devices. The host devicemay display, on a display thereof, the IoT devicesthat are controllable.

110 111 111 150 110 120 The host devicemay execute an application (hereinafter, referred to as the IoT management app) that manages IoT devices. The IoT management app may check a communication status of each IoT deviceand may output a user interface for control of the IoT device. In an embodiment, the IoT management app may be downloaded through the application market server(e.g., Google Play Store or Apple App Store) and may be installed in the host deviceor the second electronic device or the invitee device(hereinafter, referred to as the ‘invitee device’) (e.g., a smartphone or a table PC).

110 111 110 1 1 1 2 2 1 According to various embodiments, the host devicemay manage the various IoT deviceslocated in a plurality of places, by using the IoT management app. For example, the host devicemay collectively manage a first group of IoT devices (e.g., TV, refrigerator, or air-conditioner) located in a first area (e.g., a user's home) and a second group of IoT devices (e.g., TV, air-conditioner, or air-cleaner) located in a second area (e.g., the user's office).

110 1 1 1 110 2 2 1 110 The IoT management app may manage the first group of IoT devices and the second group of IoT devices as separate things. For example, in the case where the user selects (e.g., through a touch input or a voice input) a place (e.g., a tab for managing the place) that corresponds to a first location (e.g., the user's home), the host devicemay display a list, status information, or controllable functions of the first group of IoT devices (e.g., TV, refrigerator, and air-conditioner). In the case where the user selects a place corresponding to a second location (e.g., the user's office), the host devicemay display a list, status information, or controllable functions of the second group of IoT devices (e.g., TV, air-conditioner, and air-cleaner). Alternatively, in the case where the user selects a tab corresponding to a full list, the host devicemay display a list, status information, or functions of all the IoT devices included in the first and second groups.

110 111 111 The host devicemay store setting information or control information (hereinafter, referred to as IoT environment information) about the plurality of IoT devices. For example, the IoT environment information may include identification information, device types, executable-function information, authority information, or control methods of the IoT devices.

110 120 110 1 1 1 120 120 1 1 1 According to various embodiments, the host device(used with an account of a first user) may share the stored IoT environment information with the invitee device(used with an account of a second user). For example, the host device(e.g., a smartphone) of the first user (e.g., father) may provide IoT environment information about TV, refrigerator, and air-conditionerlocated in the home to the invitee device(e.g., a smartphone) of the second user (e.g., spouse or child). In the case where the IoT environment information is shared according to a specified procedure, the invitee devicemay have control authority over TV, refrigerator, and air-conditioner.

110 110 120 According to various embodiments, the shared IoT environment information may be all or part of the IoT environment information stored in the host device. For example, information about all places (e.g., Home, Office, and Nearby), some places (Home), or some devices (e.g., TV or an air-conditioner registered in home) registered in the IoT environment information of the host devicemay be shared with the invitee device.

110 120 110 According to various embodiments, the host devicemay start a process of sharing the IoT environment information, by transmitting an invitation message (or a message for sharing) to the invitee device. The invitation message may include information about the host device, information about controllable IoT devices, information about the IoT management app, or information about places (or locations) where the IoT devices are located.

110 120 120 120 110 130 120 110 According to various embodiments, the host device(registered by the first user's account) may transmit the invitation message, based on the account information or the telephone number of the second user of the invitee device(registered by the second user's account). For example, in the case where an IoT management app is installed in the invitee deviceand the invitee deviceis logged in using the second user's account, the host devicemay transmit the invitation message through the IoT serverby a push message method. In another example, in the case where an IoT management app is not installed in the invitee device, the host devicemay transmit an SMS message including a URL for installation of an IoT management app as the invitation message.

110 110 120 110 130 110 110 110 2 3 3 FIGS.,A, andB According to various embodiments, the host devicemay create an invitation message, based on IoT device information, the first user's account registered in the host device, and information about the invitee device. For example, the host deviceor the IoT servermay create a hash code of the invitation message. In another example, the host devicemay create an invitation message, based on information (name and spatial information) of the host deviceand a URL for downloading an IoT management app. Additional information about a method of transmitting the invitation message by the host devicemay be provided through.

120 110 130 The invitee devicemay receive an invitation message from the host deviceor the IoT server. In an embodiment, the invitation message may be a message that is transmitted through a push message or a text message (e.g., SMS or MMS) of an IoT management app or short-range communication (e.g., NFC or BLE).

120 110 120 110 120 110 120 6 FIG. The invitee devicemay receive the IoT environment information stored in the host device, by using the invitation message. In this case, the invitee devicemay obtain control authority over at least one IoT device managed by the host device. The invitee devicemay operate as a separate host device that is distinguished from the host device. Additional information about a process of receiving the IoT environment information by the invitee devicemay be provided through.

130 110 120 130 110 120 The IoT servermay include a memory, a communication circuit, or a processor therein and may serve as an intermediary between the host deviceand the invitee devicein a process of sharing the IoT environment information. The IoT servermay receive, from the host device, information (hereinafter, referred to as sharing setting information) useful for sharing the IoT environment information. The sharing setting information may include first user account information, place information (or group information of IoT devices), IoT device information, or information about the invitee device(account information or a phone number of the second user).

130 120 130 The IoT servermay create a push message to be transmitted to the invitee device. The IoT servermay create a push message list, based on the sharing setting information.

130 120 120 120 130 120 120 120 130 120 120 120 In an embodiment, the IoT servermay transmit the push message in the case where an IoT management app is installed in the invitee deviceand the invitee deviceis logged in using the second user's account. In another embodiment, in the case where the invitee deviceis not logged in to an IoT management app by using the second user's account, the IoT servermay transmit accumulated push messages to the invitee devicewhen the invitee devicelogs in to the IoT management app by using the second user's account. In another embodiment, in the case where an IoT management app is not installed in the invitee device, the IoT servermay transmit, to the invitee device, a list of accumulated push messages based on the identification information (e.g., the telephone number) of the invitee devicewhen the invitee deviceinstalls an IoT management app, creates an account of the second user, and performs SMS authentication related to the account of the second user.

130 120 According to various embodiments, the IoT servermay remove the information (e.g., the telephone number) of the invitee devicewhen settings for sharing the IoT environment information are completed.

140 110 120 140 110 120 The message transfer servermay play an intermediary role in the transfer of a message between the host deviceand the invitee device. For example, the message transfer servermay serve as an intermediary to allow the host deviceand the invitee deviceto transmit and receive a message in an SMS or MMS form.

150 150 120 The application market servermay be a server capable of downloading various applications. The application market servermay provide an installation file for installing an IoT management app, in response to a request of the invitee device.

160 120 110 120 130 120 160 120 160 130 120 The authentication servermay perform authentication on a telephone number in response to a request of the invitee device. In various embodiments, in the case where the host devicetransmits an invitation message through the telephone number of the invitee device, authentication of a subject requesting the invitation message from the IoT servermay be utilized to enhance security. In this case, the invitee devicemay request the authentication serverto perform an authentication procedure on the telephone number of the invitee device. The authentication servermay transmit the authentication result to the IoT serverand the invitee device.

2 FIG. is a flowchart illustrating a device management method according to various embodiments.

2 FIG. 211 110 110 110 110 130 110 Referring to, in operation, the host devicemay establish wireless communication with one or more IoT devices using a communication circuit. For example, the host devicemay establish communication channels with IoT devices around the host deviceusing short-range communication, Wi-Fi communication (e.g., communication belonging to the same AP), and/or cellular communication. The host devicemay receive information useful for controlling the IoT devices (e.g., identification information or device types of the IoT devices, or information about controllable functions) from the IoT devices, or the IoT serverthrough the communication channels. According to various embodiments, the host devicemay establish the communication channels with the one or more IoT devices through separate authentication processes (e.g., such as input of a password, an identification number, or input of some biometric information).

212 110 110 110 110 1 2 In operation, the host devicemay output, through a display, a user interface including a list of the one or more IoT devices. The host devicemay execute an IoT management app to display a list of IoT devices that are capable of communication and/or otherwise controllable. According to various embodiments, the host devicemay manage the one or more IoT devices by dividing the IoT devices into groups. For example, the host devicemay group the plurality of IoT devices according to location (e.g., such as home, office, living room, room, room, etc.) indicating where the plurality of IoT devices are physically located within a locale, access points (APs) to which the plurality of IoT devices are connected, and/or any other criteria created or configured by a user.

213 110 1 2 In operation, the host devicemay receive, from a first user, a user input for selecting a group of IoT devices from among the one or more IoT devices. For example, as described above, the group may be classified according to the location where the IoT devices are located. The user input may therefore include an input selecting a tab corresponding to the particular group and adding another user in the IoT management app. For example, in the case where the user selects a “living-room” tab from among tabs including “living-room,” “room,” and “room” and further selects an “add member” button, processes executable to share IoT environment information may be initiated.

214 110 130 110 120 In operation, the host devicemay transmit first information including user account data of the first user to the IoT server(the first external server) using the communication circuit. The first information may also include information about the selected group, and the account of the first user associated with the host device. For example, the first information may include at least one or more of first user account information, place information (or group information of IoT devices), IoT device information, and information about the invitee device(i.e., referring to for example second user account information or a phone number associated with the invitee).

215 110 120 130 In operation, the host devicemay transmit the second information to another electronic device (e.g., referring to the invitee device) using the communication circuit. The second information may be information which facilitates the other electronic device to communicatively respond to the IoT serverto connect to and thus control the selected group. For example, the second information may include URL information for installing an IoT management app.

130 160 110 120 According to an embodiment, the second information may be delivered to the other electronic device through the IoT server, or may be transmitted to the other electronic device through the separate message transfer server. According to another embodiment, the host devicemay transmit the second information to the other electronic device (e.g., the invitee device) through short-range communication (e.g., Bluetooth).

3 FIG.A is a signal flow diagram illustrating a process of sharing IoT environment information using an account of a second user, according to various embodiments.

3 FIG.A 331 110 120 110 Referring to, in operation, the host devicemay create an invitation message (or a request signal) by receiving IoT environment information to be shared (e.g., a list of IoT devices or the location of the IoT devices) and the account of the second user of the invitee devicefrom a user through an IoT management app. For example, the second user's account information may be directly input by the user, or may be input through information of a contact stored in the host device.

332 110 130 In operation, the host devicemay transmit the created invitation message to the IoT server. For example, the invitation message may include first user account information, place information (or group information of IoT devices), IoT device information, or second user account information.

333 130 120 130 130 130 110 110 130 In operation, the IoT servermay search a database for the second user's account that was indicated or otherwise included in the invitation message. For example, in the case where an IoT management app is installed in the invitee devicea log-in history of the second user exists, the second user's account may be discoverable in the database of the IoT server. According to an embodiment, in the case where the second user's account is not discovered in the database of the IoT server, the IoT servermay determine that the second user's account included in the invitation message is invalid, and may transmit an error message to the host device. The host device, when receiving the error message from the IoT server, may display a notification (e.g., a pop-up message) to the user, or may provide a user interface of guide screen to prompt the user to reenter the second user's account.

130 130 334 130 In the case where the second user's account is discovered in the database of the IoT server, the IoT servermay, in operation, create a database table based on the received invitation message. For example, the IoT servermay create a database table that includes first user account information, second user account information, authority information, creation time information, or update time information.

335 130 120 In operation, the IoT servermay inform the invitee devicecorresponding to the second user that the invitation message has arrived, by using a push message.

130 120 120 120 130 120 120 130 120 120 According to an embodiment, the IoT servermay transmit the push message in real time when the invitee deviceis logged in to the IoT management app by using the discovered account of the second user, or when the invitee deviceallows the receipt of a push message. According to another embodiment, in the case where the invitee deviceis not logged in to the IoT management app by using the discovered account of the second user or does not allow the receipt of a push message, the IoT servermay transmit the push message after the invitee devicelogs in to the IoT management app by using the second user's account. According to another embodiment, in the case where an IoT management app is not installed in the invitee device, the IoT servermay transmit the push message after an IoT management app is installed in the invitee deviceand the invitee devicelogs in to the IoT management app by using the second user's account.

336 120 120 120 120 120 In operation, the invitee devicemay identify the invitation message. In the case where the invitee deviceis logged in to the IoT management app using the second user account, the invitee devicemay inform the second user of the reception or arrival of the invitation message in real time. In the case where the invitee deviceis not logged in to the IoT management app by using the second user account, the invitee devicemay inform the second user of the arrival of the invitation message after logging in to the IoT management app.

120 According to various embodiments, the invitee devicemay automatically execute the IoT management app when the second user identifies the invitation message.

337 120 130 In operation, the invitee devicemay log in to the IoT management app using the second user account, and may request the IoT environment information from the IoT server.

120 130 According to various embodiments, the invitee devicemay automatically log in using the second user account according to settings of the installed IoT management app and may request the IoT serverto provide the IoT environment information.

338 130 In operation, the IoT servermay identify the second user's account and the invitation message in the database table.

339 130 120 120 120 110 In operation, the IoT servermay transmit the IoT environment information to the invitee device. When the invitee devicereceives the IoT environment information, the invitee devicemay control at least some of the IoT devices managed by the host device.

3 FIG.B is a signal flow diagram illustrating a process of sharing IoT environment information using identification information of an invitee device, according to various embodiments.

3 FIG.B 351 110 120 Referring to, in operation, the host devicemay create an invitation message by entering IoT environment information to be shared (e.g., an IoT device list or locations of IoT devices) and identification information (e.g., a telephone number) of the invitee deviceinto an IoT management app.

352 110 130 In operation, the host devicemay transmit the created invitation message to the IoT server.

353 130 In operation, the IoT servermay create a database table based on the received invitation message.

354 354 1 110 140 140 120 110 1 FIG.B In operationsand_, the host devicemay transmit the created invitation message to a message transfer server (e.g., the message transfer serverof). The message transfer servermay transmit an SMS message corresponding to the invitation message to the invitee device. The invitation message may include identification information (e.g., a telephone number or a first user account) of the host device. The invitation message may include a URL for installing an IoT management app.

355 120 140 120 120 120 120 120 In operation, the invitee devicemay identify the invitation message transmitted through the message transfer server. The invitee devicemay determine whether an IoT management app is installed in the invitee device. For example, when the invitee devicereceives, from a user, an input selecting the URL included in the invitation message, the invitee devicemay determine whether an IoT management app is installed in the invitee device.

120 120 356 356 1 150 In the case where an IoT management app is not installed in the invitee device, the invitee devicemay, in operationsand_, connect to the application market serverand request data for installing an IoT management app.

357 120 150 In operation, the invitee devicemay receive, from the application market server, data for installing the IoT management app and may install the IoT management app using the received data.

358 120 In operation, the invitee devicemay log in to the IoT management app by using an account of a second user. According to an embodiment, the IoT management app may output a UI for creating an account.

359 120 160 120 120 358 120 1 FIG.B According to various embodiments, in operation, the invitee devicemay request an authentication server (e.g., the authentication serverof) to authenticate the identification information (e.g., the telephone number) of the invitee device. For example, in the case where the invitee devicelogs in to the IoT management app by using the second user's account in operation, the invitee devicemay perform an authentication operation through the identification information (e.g., the telephone number).

360 160 120 In operation, the authentication servermay perform authentication on the telephone number of the invitee device.

361 160 130 120 In operation, the authentication servermay transmit the authentication result to the IoT serverand the invitee device.

130 362 120 130 130 353 130 120 In the case where the authentication result is valid, the IoT servermay, in operation, search for the identification information (e.g., the telephone number) of the invitee deviceand update the DB table. The IoT servermay update the account information of the second user. According to an embodiment, the IoT servermay update the DB table created in operation, based on the second user's log-in information. The second user account information may have been newly recorded in the updated DB table, and accordingly, an update time may be modified. Also, the IoT servermay also enhance security by removing the identification information (e.g., the telephone number) of the invitee devicethat is stored in the DB table.

363 130 120 120 110 In operation, the IoT servermay transmit the IoT environment information to the invitee device. The invitee devicemay share control authority over at least some of the IoT devices managed by the host device, based on the received IoT environment information.

4 FIG. 4 FIG. illustrates a UI of an IoT management app according to various embodiments.is merely illustrative, and the present disclosure is not limited thereto.

4 FIG. 401 401 420 401 Referring to, an IoT management app may output a user interfacefor managing a plurality of IoT devices. The user interfacemay include a list of the plurality of IoT devices. The user interfacemay display identification information or device type of each IoT device, or status information thereof (e.g., whether the IoT device is driven or not, a scheduled routine, or settings).

401 420 4 FIG. According to various embodiments, the user interfacemay display the list of the IoT devicesby dividing the IoT devices into groups.illustrates an example in which the IoT devices are grouped based on places where the IoT devices are located. It is understood of course that the present disclosure is not limited to this kind of grouping.

401 410 420 440 According to various embodiments, the user interfacemay further include place tabs, an IoT device list, and/or a plus button.

410 110 The place tabsmay display place information (i.e., location information) set by the host deviceand may allow a user to select each place. IoT devices located in the same location may be simultaneously or separately controlled.

410 401 401 420 415 420 420 When the user selects one of the place tabs, IoT devices included in the selected group may be displayed. For example, in the case where a “home” tab is selected, a user interfacea related to IoT devices located in the home may be displayed. The user interfacea may include a sub-device lista and a menufor collectively controlling the group. The sub-device lista may correspond to at least some of the IoT devices included in the IoT device list.

440 5 FIG. The plus buttonmay be used to add an IoT device, a location, a user having new control authority, or a control mode. Additional information about adding a user having new control authority are illustrated in more detail below, in.

410 410 410 According to various embodiments, setting menus may be output differently, depending on a type of a selected place tab from among the tabs. For example, in the case where an “All devices” tab is selected from the place tabs, a list of “Add place,” “Add function execution rule,” and “Delete device” may be included in a setting menu. In the case where the “home” tab is selected from the place tabs, a list of “Add editing mode,” “Add place,” “Add member,” and “Add function execution rule” may be included in a setting menu.

110 110 120 According to an embodiment, a tab created based on IoT environment information received from another device may not include a device addition item. Alternatively, at least some functions may be limited in the created tab. For example, a tab (e.g., Home of the host device) created based on IoT environment information received from the host deviceby an IoT management app of the invitee devicemay not have or be denied authority to perform more secure functions, such as editing a routine or register a routine.

401 110 110 According to various embodiments, the user interfacemay further include a routine dash board (not illustrated). The routine dash board may be updated in the case where the host deviceregisters a routine. For example, the host devicemay configure an air-conditioner to be turned on in the morning, and may configure a specific device to perform an operation, by identifying whether an event occurs.

401 According to various embodiments, the user interfacemay further include a device dash board (not illustrated). The device dash board may display the name of a registered IoT device, information about the owner of the device, and an operation performed in the device.

5 FIG. 5 FIG. illustrates a UI through which a host device transmits an invitation message, according to various embodiments.is merely illustrative, and the present disclosure is not limited thereto.

5 FIG. 4 FIG. 110 501 440 Referring to, the host devicemay display an invitation message creation screenwhen an input is detected requesting addition of a new user occurs (e.g., when a user selects “Add member” by selecting the plus buttonof).

501 501 510 520 The invitation message creation screenmay include a UI for selecting a method of transmitting an invitation message. For example, the invitation message creation screenmay include a first fieldinto which a second user's account is entered, and a buttonfor selectable to request usage of an SMS message.

510 511 130 1 FIG.A In the case where a first user desires to permit issuance of control authority to the second user using the second user's account, the first user may enter the second user's account into the first fieldand select a confirmation icon or element. The second user's account may be responsively transmitted to an IoT server (e.g., the IoT serverof).

130 130 120 The IoT servermay check validity of the second user's account input. In the case where data matching the second user's account is included in a database table, the IoT servermay transmit a push message to the invitee deviceby using the matched data.

130 In the case where there is no data matching the second user's account in the database table, the IoT servermay notify, through a displayed pop-up window, the first user of the fact that the requested user (having no log-in history) is not registered in an IoT management app.

510 510 110 In an embodiment, in the case where the first user's account is entered into the first fieldor the account of the second user having control authority is entered into the first field, the host devicemay display an error message.

510 510 511 130 In an embodiment, a plurality of pieces of second user account information may be entered into the first fieldthrough separators (e.g., “,” or “;”). For example, in the case where a plurality of pieces of second user account information separated from one another by specified separators are entered into the first fieldand the user selects the okay button, the plurality of pieces of second user account information may be transmitted to the IoT server.

520 520 110 502 The first user may use the message use buttonin the case where the first user wants to transmit an invitation message by using an SMS message. In the case where the first user selects the message use button, the host devicemay output an address book screen. The first user may select the second user's telephone number from the address book, or may directly enter the second user's telephone number.

110 503 503 550 550 110 The host devicemay display a message editor screen, based on the second user's telephone number input. The message editor screenmay include an invitation message. For example, the invitation messagemay include the name of the host device, the first user's account, information about places where IoT devices are located, and URL information for downloading an IoT management app or a related guide. According to an embodiment, the URL information may be created by the IoT management app or the IoT server and may be encrypted information.

550 120 140 1 FIG.B In the case where the user selects a send button, the invitation messagemay be transmitted to the invitee devicethrough a message transfer server (e.g., the message transfer serverof).

110 120 130 130 According to various embodiments, the host devicemay transmit sharing setting information (e.g., the first user account information, place information (or group information of IoT devices), IoT device information, the telephone number of the invitee device, or the time at which the invitation message was transmitted) to the IoT serverin the background. The IoT servermay create a database table, based on the received sharing setting information.

6 FIG. is a flowchart in the case where an invitee device receives an invitation message in an SMS form, according to various embodiments.

6 FIG. 1 FIG.B 1 FIG.B 1 FIG.B 610 120 110 140 110 Referring to, in operation, an invitee device (e.g., the invitee deviceof) may receive an invitation message in an SMS form from a host device (e.g., the host deviceof). For example, the invitation message may be transmitted through a message transfer server (e.g., the message transfer serverof). In an embodiment, the invitation message may be in a text or image format. The invitation message may include information associated with a first user or the host devicethat initiated the invitation (e.g., a telephone number or the first user's account ID) or URL information for installing an IoT management app.

620 120 120 120 120 120 In operation, the invitee devicemay determine whether the IoT management app specified in the invitation message is installed in the invitee device, based on an operation identifying the invitation message by a user. For example, in the case where a second user (e.g., the user of the invitee device) selects the URL information for installing the IoT management app, the invitee devicemay determine whether the IoT management app is installed. In another example, the invitee device, when receiving the invitation message in an SMS form, may analyze text included in the SMS and may determine whether the IoT management app is installed.

120 120 625 150 In the case where the specified IoT management app is not installed in the invitee device, the invitee devicemay, in operation, connect to the app market server(e.g., Google Play Store or Apple App Store) according to an input of the second user (e.g., execution of a URL shortcut) to download and install the specified IoT management app.

630 120 120 In operation, the invitee devicemay determine whether the invitee deviceis logged in to the IoT management app by using the second user's account.

120 120 635 In the case where the invitee deviceis not logged in to the IoT management app, the invitee devicemay, in operation, output a user interface for log-in (e.g., a screen including a UI for entering account information or a UI for signing up for a membership).

120 120 According to an embodiment, in the case where the user identifies (or selects) the received invitation message in an SMS form in the state in which the invitee devicelogs in to the IoT management app by using the second user's account, the invitee devicemay automatically execute the IoT management app.

120 120 640 130 In the case where the invitee deviceis logged in to the IoT management app, the invitee devicemay, in operation, receive an invitation message in a push message form from the IoT server.

650 120 120 110 120 130 130 According to various embodiments, in operation, the invitee devicemay determine whether the second user has generated an input approving the invitation. In the case where the second user rejects the invitation, the invitee devicemay not obtain authority to control IoT devices managed by the host device. According to an embodiment, in the case where the invitee devicetransmits rejection information to the IoT server, the IoT servermay remove information related to the invitation message from a database.

120 655 130 120 110 120 110 In the case where the second user generates an input approving the invitation, the invitee devicemay, in operation, receive IoT environment information from the IoT server. The invitee devicemay share at least a part of control authority of the host deviceover the IoT devices. For example, the invitee devicemay obtain control authority over at least one IoT device belonging to a group shared by the host device.

7 FIG. 7 FIG. illustrates a user interface of an invitee device that receives an SMS message as an invitation message, according to various embodiments.is merely illustrative, and the present disclosure is not limited thereto.

7 FIG. 1 FIG.B 1 FIG.B 701 120 710 710 110 710 711 710 Referring to, on a screen, an invitee device (e.g., the invitee deviceof) may receive an invitation message. The invitation messagemay include information (e.g., a telephone number or an account ID) of a first user or a host device (e.g., the host deviceof) that initiated the invitation. Also, the invitation messagemay include URL informationfor downloading an IoT management app. In an embodiment, the invitation messagemay be implemented using text or an image.

702 120 711 710 720 On a screen, the invitee devicemay display a page for downloading the IoT management app in the case where a user selects the information (e.g., the URL information) of the invitation message. The page may include display of an icon or elementselectable to imitate the download.

703 120 120 On a screen, the invitee devicemay output a user interface for log-in (e.g., a UI for signing up for a membership) in the case where the invitee deviceis not logged in to the IoT management app after the IoT management app has completed installation.

120 702 703 According to various embodiments, in the case where the IoT management app is installed in the invitee devicein advance, the processes corresponding to the screensandmay be omitted.

704 120 On a screen, the invitee devicemay output a user interface for receiving a user log-in. A second user may log in by entering a second user account and a password into the respective entry fields.

705 120 120 130 120 120 On a screen, the invitee devicemay create an account to perform an SMS personal identification number or “PIN” authentication process in the case where the invitee devicelogs in to the IoT management app for the first time. Based on the SMS PIN authentication result, the IoT servermay match and store, in a DB table, the telephone number of the invitee deviceand the second user account of the IoT management app. According to various embodiments, the telephone number of the invitee devicemay be removed from the DB table later. According to an embodiment, the information (e.g., the telephone number) of the second user that is used for the SMS PIN authentication process may be input by the second user or a system (e.g., an OS). For example, in the case where the information of the second user is input by the system, the information of the second user may be automatically input.

120 705 According to various embodiments, in the case where the invitee devicehas previously logged in using the second user account, the process corresponding to the screenmay be omitted.

706 120 120 761 762 120 On a screen, the invitee devicemay determine whether the second user approves the invitation. For example, the invitee devicemay output a screen that includes a rejection buttonand an approval buttoneach selectable to determine whether to approve sharing of IoT environment information. According to an embodiment, in the case where the second user receives a plurality of invitation messages from the first user or receives invitation messages from a plurality of users, the invitee devicemay output the plurality of invitation messages sequentially (e.g., in the order that the invitation messages are received or with respect to the first user).

762 706 120 130 707 120 110 In the case where the second user selects the approval buttonon the screen, the invitee devicemay receive IoT environment information from the IoT serverand may provide a screenfor controlling IoT devices, based on the received information. The invitee devicemay share at least a part of control authority of the host deviceover the IoT devices.

761 706 120 130 130 130 In the case where the second user selects the rejection buttonon the screen, the invitee devicemay transmit an invitation rejection message (or signal) to the IoT server. The IoT servermay remove the invitation message from a database of the IoT server, based on the invitation rejection message.

8 FIG. 8 FIG. illustrates a user interface for identifying an invitation message, according to various embodiments.is merely illustrative, and the present disclosure is not limited thereto.

8 FIG. 7 FIG. 801 810 820 830 840 801 706 Referring to, an invitation messagemay include first user information, an invitation guide, an approval button, and a rejection button. For example, the invitation messagemay be output on the screenof.

810 110 The first user informationmay include information about a first user having transmitted the invitation message (e.g., an account ID, the name, or a profile picture of the first user) and information about the host device(e.g., the telephone number).

820 820 The invitation guidemay include a simple introduction to a function, a greeting, or the like. The invitation guidemay include descriptions of a place of invitation, a device range, and the like.

830 840 The approval buttonand the rejection buttonmay be selectable buttons for indicating whether to approve sharing of IoT environment information.

830 802 802 In the case where a second user selects the approval button, a user interfacefor controlling IoT devices may be output. The second user may control the IoT devices displayed on the user interface.

840 803 120 110 130 120 110 In the case where the second user selects the rejection button, an additional dialoguefor confirming the rejection may be output. In the case where the rejection is selected once more, the invitee devicemay not obtain authority to control the IoT devices managed by the host device. Information about the second user's selection of rejection may be transmitted to the IoT server. In an embodiment, the invitee devicemay transmit, to the host device, an SMS message about the selection of rejection.

120 120 According to various embodiments, in the case where the invitee devicereceives a plurality of invitation messages, the plurality of invitation messages may be displayed in a card form on a dashboard. For example, in the case where the invitee devicereceives an invitation message of office and home from John and an invitation message of home from Paul, Office, Home, and Home tabs may be created on a dashboard, and the second user may approve or reject each invitation message.

120 110 120 The second user may create places in an IoT management app, may add various IoT devices to the created places (e.g., place tabs), and may manage the IoT devices. In various embodiments, the invitee devicemay differently display (e.g., color, text, or icon) an IoT environment (e.g., a place tab) shared with the host deviceand an IoT environment (e.g., a place tab) created by the invitee device.

9 FIG. illustrates a DB table stored in an IoT server, according to various embodiments.

9 FIG. 130 110 120 130 901 Referring to, the IoT servermay receive sharing setting information from the host device. The sharing setting information may include first user account information, place information (or group information of IoT devices), IoT device information, or information about the invitee device(second user account information or a phone number). The IoT servermay create a DB tablebased on the sharing setting information.

901 910 920 930 940 950 960 970 980 990 According to various embodiments, the DB tablemay include a DB identifier, a second user account, a first user account, token information, authentication information, authority information, creation time, update time, and status information.

910 The DB identifiermay be identification information uniquely created for each invitation message.

920 120 920 120 The second user accountmay be information that a second user of the invitee devicereceiving the invitation message uses to log in to an IoT management app. According to an embodiment, the second user accountmay have null information in the case where the invitation message is transmitted based on the telephone number of the invitee device.

930 110 The first user accountmay be information that a first user of the host devicetransmitting the invitation message uses to log in to the IoT management app.

940 120 940 120 The token informationmay be identification information (e.g., a telephone number) used to identify the invitee device. For example, the token informationmay be a field used to invite the invitee deviceto the telephone number.

950 The authentication informationmay be information related to authentication of the first user or the second user.

960 110 120 960 960 960 110 The authority informationmay represent a range in which the host deviceor the invitee deviceis capable of managing or controlling IoT devices. For example, when the authority informationis set to “1”, this may mean authority to control all registered IoT devices. When the authority informationis set to “2”, this may mean authority to control IoT devices located in a specified place, among the registered IoT devices. According to an embodiment, the authority informationmay include authority to edit (e.g., remove, add, or collectively control) an IoT device group shared by the host device.

970 901 130 980 901 The creation timemay be time when the DB tablewas stored in the IoT server. The update timemay be time when the DB tablewas updated last.

990 901 The status informationmay be information representing whether the DB tableis available or not.

120 130 901 930 940 980 902 930 930 130 120 940 According to various embodiments, when the invitee devicelogs in using the second user account, the IoT servermay update the DB table, based on the log-in information of the second user. The second user account, the token information, or the update timemay be modified in an updated DB table. According to an embodiment, in the case where data is stored in the second user account(in the case where the second user accountis not Null), the IoT servermay remove the telephone number of the invitee devicefrom the token informationlater (a Null status).

9 FIG. 110 110 920 940 is merely illustrative, and the present disclosure is not limited thereto. For example, in the case where the host devicetransmits an invitation message by using a second user ID, the second user ID received from the host devicemay be stored in the second user account. In this case, the token informationmay have null information.

130 110 130 110 According to various embodiments, the IoT servermay store a separate database related to an IoT environment of the host device. For example, the IoT servermay store a database related to information about IoT devices registered in the host device, group information (e.g., place information) to which each of the IoT devices belongs, and the like.

10 FIG. is a signal flow diagram illustrating a process in which an invitee device makes a request to add a device, according to various embodiments.

10 FIG. 1010 120 120 120 120 120 120 Referring to, in operation, the invitee devicemay receive a user input for adding at least one IoT device to control the IoT device. For example, the invitee devicemay search for a nearby device through short-range communication (e.g., Bluetooth or Wi-Fi) and perform an operation registering the discovered device. According to an embodiment, the invitee devicemay already have the IoT management app installed in the invitee deviceand be logged in to the IoT management app using a second user account. For example, in the case where an edit button (a button for adding or removing a device) is selected in one screen (e.g., home) of the IoT management app of the invitee device, the invitee devicemay initiate an operation of adding a nearby IoT device.

1020 120 130 In operation, the invitee devicemay transmit a device addition request to the IoT serverto register the discovered device. The device addition request may include identification information of the IoT device to be added and the second user account information.

1040 130 130 130 130 1045 130 130 120 In operation, the IoT servermay search a database for the identification information of the IoT device. According to an embodiment, in the case where the IoT serverreceives the request for registering the IoT device, the IoT servermay determine whether the IoT device is registered to a different user account. For example, the IoT servermay allow one user to have top-level control authority over one IoT device. Accordingly, in the case where another user requests control authority over the same registered IoT device, the user obtains approval of the higher priority user registered in advance. In operation, the IoT servermay register the IoT device in the second user account in the case where the IoT device is not registered in a different user account. The IoT servermay update information (e.g., identification information, device type, or group information (e.g., place information) about the newly added IoT device to a database related to IoT devices registered in the invitee device.

1046 130 120 120 120 120 130 In operation, the IoT servermay notify the invitee deviceof the registration result. The invitee devicemay control the corresponding IoT device using the IoT management app. According to an embodiment, a function of controlling the corresponding IoT device may be enabled in the IoT management app of the invitee device, or the invitee devicemay download controllable data from the IoT server.

1050 130 110 120 110 110 120 In operation, the IoT servermay transmit a join request to the host devicein the case where the IoT device for which the invitee devicehas requested registration is registered in a different user account (e.g., in a first user account of the host device). The join request may allow IoT environment information registered in the host deviceto be shared with the invitee deviceassociated with the second user account.

1060 110 110 110 120 In operation, the host devicemay identify the join request. For example, the host devicemay identify, through a pop-up or a push message, a request for the host deviceto share IoT environment information related to the corresponding IoT device with the invitee devicein which the second user account is registered.

1070 110 In operation, the host devicemay determine whether approval of a first user is detected.

1075 110 110 1030 110 130 110 130 120 In operation, the host devicemay create and transmit an invitation message using the second user account in the case where there is an approval of the first user. For example, the host devicemay create the invitation message based on the second user account and may transmit the invitation message to the IoT server. In another example, the host devicemay transmit, to the IoT server, a response message indicating that the host devicehas approved the sharing request, and the IoT servermay provide authority to the invitee device, based on the response message.

130 110 120 110 According to various embodiments, the IoT servermay update the database related to the IoT devices registered in the host deviceor the invitee device, based on the invitation message or the response message of the host device.

1080 110 130 In operation, the host devicemay transmit a rejection message to the IoT serverin the case where no approval of the first user is detected.

1085 130 120 In operation, the IoT servermay transmit the rejection result to the invitee device.

11 FIG. 12 FIG. is a signal flow diagram illustrating a process of sharing IoT environment information using a security code, according to various embodiments.illustrates a UI showing a process of sharing IoT environment information using a security code, according to various embodiments.

11 12 FIGS.and 110 120 110 130 120 110 130 120 Referring to, the host devicemay transmit an invitation message to the invitee devicewithin a close distance by which short-range communication (e.g., BLE communication, NFC communication, or the like) is possible, by using short-range communication. The host device, the IoT server, and the invitee devicemay perform an invitation operation based on the same security code (e.g., PIN code). The host devicemay receive a security code (e.g., a PIN code) from the IoT serverand may share IoT environment information with the invitee deviceby using the received security code. Although the following description will be focused on a case where a security code is PIN information, the present disclosure is not limited thereto.

1110 110 120 1201 In operation, the host devicemay receive a user input for adding a second user (or the invitee device) (Screen).

1120 110 130 In operation, the host devicemay request a PIN code from the IoT server.

1130 130 130 In operation, the IoT servermay create a PIN code. In an embodiment, the IoT servermay create a PIN code having a preset number of digits (e.g., eight digits) or a PIN code valid for a specified period of time (e.g., three minutes) to enhance security.

130 110 According to various embodiments, the IoT servermay create a PIN code based on sharing setting information received from the host device. The sharing setting information may include first user account information, place information (or group information of IoT devices), or IoT device information.

1140 130 110 1202 In operation, the IoT servermay transmit the created PIN code to the host device(Screen).

1150 110 120 1211 110 120 In operation, the host devicemay share the received PIN code with the invitee device(Screen). For example, the host devicemay transmit the PIN code to the invitee devicethrough short-range communication, such as Bluetooth Low Energy or “BLE”. According to an embodiment, a first user may show the PIN code to the second user and may allow the second user to directly input the PIN code.

110 120 According to various embodiments, the host devicemay add a separate dummy code to the received PIN code and may share the PIN code having the dummy code added thereto with the invitee devicethrough short-range communication, such as BLE.

1160 120 In operation, the invitee devicemay log in to an IoT management app.

1170 120 130 1212 In operation, the invitee devicemay request an invitation message from the IoT serverby using the PIN code (Screen).

1180 130 110 In operation, the IoT servermay request the host deviceto confirm the invitation.

1190 110 130 In operation, the host devicemay transmit the confirmation result to the IoT server.

1180 1190 130 According to various embodiments, operationsandmay be omitted. For example, in the case where the PIN code is valid, the IoT servermay transmit an invitation message without a separate confirmation process.

1195 130 120 120 110 120 1213 In operation, the IoT servermay transmit an invitation message to the invitee device. The invitee devicemay share IoT environment information with the host device. The invitee devicemay control various IoT devices according to the IoT environment information (Screen).

13 FIG. illustrates a UI showing a process in which a host device and an invitee device share a security code, according to various embodiments.

13 FIG. 110 120 1301 1310 1320 1302 1320 Referring to, the host devicemay receive a user input for adding a second user (or the invitee device) (Screen). In the case where a first user selects a code creation button, a security codemay be created depending on a specified algorithm (Screen). According to an embodiment, the security codemay be valid for a predetermined period of time (e.g., about one minute), or may be valid a predetermined number of times (e.g., once).

120 1330 1311 The invitee devicemay receive a user input to press a buttonfor performing a join request through a code input (Screen).

120 1340 1312 1340 The invitee devicemay output a user interface including a code input field(Screen). The second user may enter, into the code input field, a security code provided by the first user.

120 130 1340 120 130 110 110 130 1303 110 110 120 130 According to an embodiment, the invitee devicemay request the IoT serverto check validity of the security code entered into the code input fieldby the invitee device. In the case where the input security code is valid, the IoT servermay transmit, to the host device, a message to request an approval input of the first user. The host devicemay display a screen for the approval request received from the IoT server(Screen). In the case where the approval input of the first user occurs in the host device, the host devicemay share IoT environment information with invitee devicethrough the IoT server.

110 1340 120 1303 110 1340 120 110 110 120 130 According to an embodiment, the host devicemay check validity of the security code entered into the code input fieldof the invitee device, by using short-range communication (Screen). For example, the host devicemay receive, through BLE communication, the security code entered into the code input fieldof the invitee device. In the case where the received security code matches a security code stored in the host deviceand the approval input of the first user occurs, the host devicemay share IoT environment information with invitee devicethrough the IoT server.

120 130 1313 The invitee devicemay control various IoT devices, based on the IoT environment information received through the IoT server(Screen).

110 120 130 120 110 According to various embodiments, in the case where the host devicestarts the process of sharing the IoT environment information with the invitee devicein the state in which a specified place (e.g., home) is selected, IoT environment information related to the corresponding place may be shared, and IoT environment information related to a different place (e.g., office) may not be shared. For example, the IoT servermay transmit, to the invitee device, information (e.g., a place, group information, or IoT device information) to be shared, based on information (e.g., a place, a group, or IoT device information) on the basis of which the host devicecreates the security code.

14 FIG. illustrates an invitation UI using a quick response or “QR” code, according to various embodiments.

14 FIG. 110 1401 110 120 Referring to, the host devicemay output a member addition screenin the case where the host devicereceives a user input related to addition of a member (e.g., an input for sharing, with a second user (or the invitee device), authority over IoT devices being managed).

1401 1401 The member addition screenmay include various methods for adding a member. For example, the member addition screenmay include a method of adding a member by inputting a second user account or a method of adding a member by creating a QR code.

1410 110 1420 1402 120 1420 110 1420 110 110 110 130 110 130 110 According to an embodiment, in the case where a user selects a QR code creation button, the host devicemay output a QR coderelated to IoT environment information (Screen). The invitee devicemay share the IoT environment information by recognizing the QR codeoutput by the host device. According to an embodiment, the QR codemay be created by the host device, based on information of the host deviceand an IoT device group (or location) to be shared. According to another embodiment, the host devicemay receive, from the IoT server, a QR code created based on the information of the host deviceand the IoT device group (or location) to be shared, and may output the QR code. The IoT servermay create a QR code based on sharing setting information received from the host device. The sharing setting information may include first user account information, place information (or group information of IoT devices), or IoT device information.

120 120 1420 110 The invitee devicemay output a UI capable of recognizing a QR code. For example, the invitee devicemay recognize the QR codedisplayed on a display of the host device, by using a camera.

120 130 120 In the case where the invitee devicerecognizes the QR code, information about the QR code may be automatically shared with the IoT server, and an invitation message related to the corresponding QR code may be transmitted to the invitee device.

15 FIG. illustrates a join UI using a QR code, according to various embodiments.

15 FIG. 14 FIG. 120 1501 1420 110 120 1510 Referring to, the invitee devicemay output a user interfacefor recognizing a QR code (e.g., the QR codeof) that is output on a display of the host device. The invitee devicemay output a recognition areafor recognizing a QR code by using a camera module.

120 1501 120 110 120 110 1501 1510 According to various embodiments, the invitee devicemay automatically output the user interfaceaccording to a specified condition. For example, in the case where the invitee deviceand the host deviceare located in the same space (e.g., within a distance by which short-range communication is possible), the invitee devicemay recognize the host devicethrough short-range communication and may automatically output the user interfaceincluding the recognition area. A first user and a second user may simply and conveniently share IoT environment information by using a QR code.

120 1501 According to various embodiments, the invitee devicemay output the user interfacefor recognizing a QR code, based on the second user's selection.

16 FIG. illustrates a UI for setting authority, according to various embodiments.

16 FIG. 130 Referring to, the IoT servermay allow one user to have top-level control authority over one IoT device. Accordingly, in the case where another user wants to have control authority over a registered IoT device, the user may have to obtain an approval of a user registered in advance.

130 120 110 130 1601 130 1610 110 120 110 110 120 According to an embodiment, in the case where the IoT serverreceives, from the invitee device, a registration request for an IoT device in which a first user (e.g., a user of the host device) is already registered, the IoT servermay send the first user a notification message (e.g., a push message) for requesting authority. For example, as shown on a screen, the IoT servermay inform, through a notification message, the host devicethat the invitee devicerequests (e.g., join request) authority over the IoT device registered in the host device. The request may be a request for allowing setting information related to the IoT device registered in the host deviceto be shared with the invitee deviceassociated with a second user account.

1610 110 120 1602 In the case where a user selects the notification message, the host devicemay output a user interface for determining whether to share IoT environment information with the invitee deviceas seen in screen.

110 130 110 130 120 In the case where the user generates an input for approving the sharing, the host devicemay transmit, to the IoT server, a response message that the host deviceapproves the sharing request, and the IoT servermay provide authority to the invitee device, based on the response message.

110 130 110 130 120 120 In the case where the user generates an input for rejecting the sharing, the host devicemay transmit, to the IoT server, a response message that the host devicerejects the sharing request, and the IoT servermay inform the invitee devicethat authority cannot be assigned to the invitee device, based on the response message.

17 FIG. is a block diagram illustrating an electronic device according to an embodiment of the present disclosure.

17 FIG. 1 FIG.A 1701 110 1701 1710 1720 1729 1730 1740 1750 1760 1770 1780 1791 1795 1796 1797 1798 Referring to, an electronic devicemay include, for example, a part or the entirety of the host deviceillustrated in. The electronic devicemay include at least one processor (e.g., AP), a communication module, a subscriber identification module (SIM), a memory, a sensor module, an input device, a display, an interface, an audio module, a camera module, a power management module, a battery, an indicator, and a motor.

1710 1710 1710 1710 1710 1721 1710 17 FIG. The processormay run an operating system or an application program so as to control a plurality of hardware or software elements connected to the processor, and may process various data and perform operations. The processormay be implemented with, for example, a system on chip (SoC). According to an embodiment of the present disclosure, the processormay further include a graphic processing unit (GPU) and/or an image signal processor. The processormay include at least a portion (e.g., a cellular module) of the elements illustrated in. The processormay load, on a volatile memory, an instruction or data received from at least one of other elements (e.g., a nonvolatile memory) to process the instruction or data, and may store various data in a nonvolatile memory.

1720 170 1720 1721 1722 1723 1724 1725 1726 1727 1 FIG. The communication modulemay have a configuration that is the same as or similar to that of the communication interfaceof. The communication modulemay include, for example, a cellular module, a Wi-Fi module, a Bluetooth (BT) module, a GNSS module(e.g., a GPS module, a GLONASS module, a BeiDou module, or a Galileo module), a NFC module, MST moduleand a radio frequency (RF) module.

1721 1721 1701 1729 1721 1710 1721 The cellular modulemay provide, for example, a voice call service, a video call service, a text message service, or an Internet service through a communication network. The cellular modulemay identify and authenticate the electronic devicein the communication network using the subscriber identification module(e.g., a SIM card). The cellular modulemay perform at least a part of functions that may be provided by the processor. The cellular modulemay include a communication processor (CP).

1722 1723 1724 1725 1721 1722 1723 1724 1725 Each of the Wi-Fi module, the Bluetooth module, the GNSS moduleand the NFC modulemay include, for example, a processor for processing data transmitted/received through the modules. According to some various embodiments of the present disclosure, at least a part (e.g., two or more) of the cellular module, the Wi-Fi module, the Bluetooth module, the GNSS module, and the NFC modulemay be included in a single integrated chip (IC) or IC package.

1727 1727 1721 1722 1723 1724 1725 The RF modulemay transmit/receive, for example, communication signals (e.g., RF signals). The RF modulemay include, for example, a transceiver, a power amp module (PAM), a frequency filter, a low noise amplifier (LNA), an antenna, or the like. According to another embodiment of the present disclosure, at least one of the cellular module, the Wi-Fi module, the Bluetooth module, the GNSS module, or the NFC modulemay transmit/receive RF signals through a separate RF module.

1729 The SIMmay include, for example, an embedded SIM and/or a card containing the subscriber identity module, and may include unique identification information (e.g., an integrated circuit card identifier (ICCID)) or subscriber information (e.g., international mobile subscriber identity (IMSI)).

1730 1732 1734 1732 The memorymay include, for example, an internal memoryor an external memory. The internal memorymay include at least one of a volatile memory (e.g., a dynamic RAM (DRAM), a static RAM (SRAM), a synchronous dynamic RAM (SDRAM), or the like), a nonvolatile memory (e.g., a one-time programmable ROM (OTPROM), a programmable ROM (PROM), an erasable and programmable ROM (EPROM), an electrically erasable and programmable ROM (EEPROM), a mask ROM, a flash ROM, a flash memory (e.g., a NAND flash memory, a NOR flash memory, or the like)), a hard drive, or a solid state drive (SSD).

1734 1734 1701 The external memorymay include a flash drive such as a compact flash (CF), a secure digital (SD), a Micro-SD, a Mini-SD, an extreme digital (xD), a MultiMediaCard (MMC), a memory stick, or the like. The external memorymay be operatively and/or physically connected to the electronic devicethrough various interfaces.

1740 1701 1740 1740 1740 1740 1740 1740 1740 1740 1740 1740 1740 1740 1740 1740 1740 1701 1740 1710 1740 1710 The sensor modulemay, for example, measure physical quantity or detect an operation state of the electronic deviceso as to convert measured or detected information into an electrical signal. The sensor modulemay include, for example, at least one of a gesture sensorA, a gyro sensorB, a barometric pressure sensorC, a magnetic sensorD, an acceleration sensorE, a grip sensorF, a proximity sensorG, a color sensorH (e.g., a red/green/blue (RGB) sensor), a biometric sensorI, a temperature/humidity sensorJ, an illumination sensorK, or an ultraviolet (UV) sensorM. Additionally or alternatively, the sensor modulemay include, for example, an olfactory sensor (E-nose sensor), an electromyography (EMG) sensor, an electroencephalogram (EEG) sensor, an electrocardiogram (ECG) sensor, an infrared (IR) sensor, an iris recognition sensor, and/or a fingerprint sensor. The sensor modulemay further include a control circuit for controlling at least one sensor included therein. In some various embodiments of the present disclosure, the electronic devicemay further include a processor configured to control the sensor moduleas a part of the processoror separately, so that the sensor moduleis controlled while the processoris in a sleep state.

1750 1752 1754 1756 1758 1752 1752 1752 The input devicemay include, for example, a touch panel, a (digital) pen sensor, a key, or an ultrasonic input device. The touch panelmay employ at least one of capacitive, resistive, infrared, and ultraviolet sensing methods. The touch panelmay further include a control circuit. The touch panelmay further include a tactile layer so as to provide a haptic feedback to a user.

1754 1756 1758 1788 The (digital) pen sensormay include, for example, a sheet for recognition which is a part of a touch panel or is separate. The keymay include, for example, a physical button, an optical button, or a keypad. The ultrasonic input devicemay sense ultrasonic waves generated by an input tool through a microphoneso as to identify data corresponding to the ultrasonic waves sensed.

1760 1762 1764 1766 1762 1762 1752 1764 1766 1701 1760 1762 1764 1766 The displaymay include a panel, a hologram device, or a projector. The panelmay be, for example, flexible, transparent, or wearable. The paneland the touch panelmay be integrated into a single module. The hologram devicemay display a stereoscopic image in a space using a light interference phenomenon. The projectormay project light onto a screen so as to display an image. The screen may be disposed in the inside or the outside of the electronic device. According to an embodiment of the present disclosure, the displaymay further include a control circuit for controlling the panel, the hologram device, or the projector.

1770 1772 1774 1776 1778 1770 The interfacemay include, for example, an HDMI, a USB, an optical interface, or a D-subminiature (D-sub). Additionally or alternatively, the interfacemay include, for example, a mobile high-definition link (MHL) interface, an SD card/multi-media card (MMC) interface, or an infrared data association (IrDA) interface.

1780 1780 1782 1784 1786 1788 The audio modulemay convert, for example, a sound into an electrical signal or vice versa. The audio modulemay process sound information input or output through a speaker, a receiver, an earphone, or the microphone.

1791 1791 The camera moduleis, for example, a device for shooting a still image or a video. According to an embodiment of the present disclosure, the camera modulemay include at least one image sensor (e.g., a front sensor or a rear sensor), a lens, an image signal processor (ISP), or a flash (e.g., an LED or a xenon lamp).

1795 1701 1795 1796 1796 The power management modulemay manage power of the electronic device. According to an embodiment of the present disclosure, the power management modulemay include a power management integrated circuit (PMIC), a charger integrated circuit (IC), or a battery or gauge. The PMIC may employ a wired and/or wireless charging method. The wireless charging method may include, for example, a magnetic resonance method, a magnetic induction method, an electromagnetic method, or the like. An additional circuit for wireless charging, such as a coil loop, a resonant circuit, a rectifier, or the like, may be further included. The battery gauge may measure, for example, a remaining capacity of the batteryand a voltage, current or temperature thereof while the battery is charged. The batterymay include, for example, a rechargeable battery and/or a solar battery.

1797 1701 1710 1798 1701 The indicatormay display a specific state of the electronic deviceor a part thereof (e.g., the processor), such as a booting state, a message state, a charging state, or the like. The motormay convert an electrical signal into a mechanical vibration, and may generate a vibration or haptic effect. Although not illustrated, a processing device (e.g., a GPU) for supporting a mobile TV may be included in the electronic device. The processing device for supporting a mobile TV may process media data according to the standards of digital multimedia broadcasting (DMB), digital video broadcasting (DVB), MediaFLO™, or the like.

Each of the elements described herein may be configured with one or more components, and the names of the elements may be changed according to the type of an electronic device. In various embodiments of the present disclosure, an electronic device may include at least one of the elements described herein, and some elements may be omitted or other additional elements may be added. Furthermore, some of the elements of the electronic device may be combined with each other so as to form one entity, so that the functions of the elements may be performed in the same manner as before the combination.

According to various embodiments, an electronic device includes a display, a wireless communication circuit, a processor, and a memory, wherein the memory stores an application program, and the application program includes a user interface configured to manage a plurality of Internet-of-Things (IoT) devices, wherein the memory stores instructions that cause the processor to establish wireless communication with one or more IoT devices by using the wireless communication circuit, output the user interface including the one or more IoT devices through the display, receive a user input for selecting a group from the one or more IoT devices, transmit first information including user account data to a first external server by using the wireless communication circuit, and transmit second information to another electronic device by using the wireless communication circuit, wherein the first information includes information about the group and the user account related to the electronic device, and wherein the second information is information that causes the other electronic device to communicate with the first external server to connect to and control one or more IoT devices included in the group.

According to various embodiments, the instructions cause the processor to transmit the second information by using account information or a telephone number that is associated with the other electronic device.

According to various embodiments, the first information further includes account information or a telephone number that is associated with the other electronic device.

According to various embodiments, the instructions cause the processor to transmit the second information through a short message service (SMS).

According to various embodiments, the instructions cause the processor to manage the plurality of IoT devices by dividing the plurality of IoT devices into a plurality of groups. The instructions cause the processor to divide the plurality of IoT devices into the plurality of groups, based on places where the plurality of IoT devices are located.

According to various embodiments, an electronic device includes a display, a wireless communication circuit, a processor, and a memory, wherein the memory stores instructions that cause the processor to receive a push message through a first application for managing one or more Internet-of-Things (IoT) devices from a first external server, or receive an SMS message related to the first application from a second external server, and when the first application is executed, receive, from the first external server, setting information for controlling the one or more IoT devices by another electronic device.

According to various embodiments, the instructions cause the processor to receive the setting information for controlling the one or more IoT devices included in a specified place.

According to various embodiments, the instructions cause the processor to determine whether the first application is installed, and install the first application through a URL included in the SMS message when it is determined that the first application is not installed.

According to various embodiments, the instructions cause the processor to transmit a user account applied to the first application to the first external server when the SMS message is received and the first application is executed.

According to various embodiments, the instructions cause the processor to control at least some of the one or more IoT devices, based on the setting information received from the first external server.

According to various embodiments, the one or more IoT devices are configured to be controllable by the other electronic device.

According to various embodiments, the instructions cause the processor to have management authority equal to or less than authority of the other electronic device over the one or more IoT devices.

According to various embodiments, the instructions cause the processor to request authentication of identification information of the other electronic device from a third external server through the wireless communication circuit, and receive an authentication result from the third external server.

According to various embodiments, the identification information is a telephone number of the other electronic device.

According to various embodiments, a server device includes a memory, a communication circuit, and a processor, wherein the memory stores instructions that cause the processor to receive, from a first electronic device registered by first user account information, at least one of second user account information and identification information of a second electronic device, the first user account information, and setting information for controlling a plurality of Internet-of-Things (IoT) devices, create a database based on the second user account information or the identification information, receive, from the second electronic device, the second user account information or the identification information of the second electronic device, and transmit at least a portion of the setting information to the second electronic device when the information received from the second electronic device matches the information stored in the database.

According to various embodiments, an electronic device includes a display, a wireless communication circuit, a processor, and a memory, wherein the memory stores an application program, and the application program includes a user interface configured to manage a plurality of Internet-of-Things (IoT) devices, and wherein the memory stores instructions that cause the processor to establish wireless communication with one or more IoT devices by using the wireless communication circuit, output the user interface including the one or more IoT devices through the display, receive a user input for selecting a group from the one or more IoT devices, share a security code created in the electronic device or a first external server with another electronic device, and transmit first information including user account data to the first external server by using the wireless communication circuit.

According to various embodiments, the security code is a PIN code or a QR code.

According to various embodiments, the instructions cause the processor to share the security code with the other electronic device through short-range communication.

According to various embodiments, the instructions cause the processor to when the security code is created in the first external server, add a separate dummy code to the created security code and share the security code having the dummy code added thereto with the other electronic device.

According to various embodiments, an electronic device includes a display, a communication circuit, a memory, and a processor, wherein the processor establishes wireless communication with one or more Internet-of-Things (IoT) devices by using the communication circuit, transmits setting information of the one or more IoT devices to an external server by using the communication circuit, and transmits a request signal including first user account information and second user account information to the external server, wherein the request signal is a signal for transmitting at least a portion of the setting information to another device, wherein the first user account information is information about a first user registered in the electronic device, and wherein the second user account information is information about a second user registered in the other device.

According to various embodiments, an Internet-of-Things (IoT) device management method performed in an electronic device. The method includes establishing wireless communication with one or more IoT devices by using a communication circuit, outputting a user interface including the one or more IoT devices through a display, receiving a user input for selecting a group from the one or more IoT devices, transmitting first information including user account data to a first external server by using the communication circuit, wherein the first information includes information about the group and the user account related to the electronic device, and transmitting second information to another electronic device by using the communication circuit, wherein the second information includes information that causes the other electronic device to communicate with the first external server to connect to and control one or more IoT devices included in the group.

18 FIG. is a block diagram illustrating a program module according to an embodiment of the present disclosure.

18 FIG. 1810 110 147 Referring to, a program modulemay include an operating system (OS) for controlling a resource related to an electronic device (e.g., the host device) and/or various applications (e.g., the application program) running on the OS. The operating system may be, for example, Android, iOS, Windows, Symbian, Tizen, or the like.

1810 1820 1830 1860 1870 1810 The program modulemay include a kernel, a middleware, an API, and/or an application. At least a part of the program modulemay be preloaded on an electronic device or may be downloaded from an external electronic device.

1820 1821 1823 1821 1821 1823 The kernelmay include, for example, a system resource manageror a device driver. The system resource managermay perform control, allocation, or retrieval of a system resource. According to an embodiment of the present disclosure, the system resource managermay include a process management unit, a memory management unit, a file system management unit, or the like. The device drivermay include, for example, a display driver, a camera driver, a Bluetooth driver, a shared memory driver, a USB driver, a keypad driver, a Wi-Fi driver, an audio driver, or an inter-process communication (IPC) driver.

1830 1870 1870 1860 1870 1830 1835 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 The middleware, for example, may provide a function that the applicationsutilize in common, or may provide various functions to the applicationsthrough the APIso that the applicationsmay efficiently use limited system resources in the electronic device. According to an embodiment of the present disclosure, the middlewaremay include at least one of a runtime library, an application manager, a window manager, a multimedia manager, a resource manager, a power manager, a database manager, a package manager, a connectivity manager, a notification manager, a location manager, a graphic manager, and a security manager.

1835 1870 1835 The runtime librarymay include, for example, a library module that a complier uses to add a new function through a programming language while the applicationis running. The runtime librarymay perform a function for input/output management, memory management, or an arithmetic function.

1841 1870 1842 1843 1844 1870 The application managermay mange, for example, a life cycle of at least one of the applications. The window managermay manage a GUI resource used in a screen. The multimedia managermay recognize a format utilized for playing various media files and may encode or decode a media file using a codec matched to the format. The resource managermay manage a resource such as a source code, a memory, or a storage space of at least one of the applications.

1845 1846 1870 1847 The power manager, for example, may operate together with a basic input/output system (BIOS) to manage a battery or power and may provide power information utilized for operating the electronic device. The database managermay generate, search, or utilize a database to be used in at least one of the applications. The package managermay manage installation or update of an application distributed in a package file format.

1848 1849 1850 1851 1852 110 1830 The connectivity mangermay manage wireless connection of Wi-Fi, Bluetooth, or the like. The notification managermay display or notify an event such as message arrival, appointments, and proximity alerts in such a manner as not to disturb a user. The location managermay manage location information of the electronic device. The graphic managermay manage a graphic effect to be provided to a user or a user interface related thereto. The security managermay provide various security functions utilized for system security or user authentication. According to an embodiment of the present disclosure, in the case in which an electronic device (e.g., the host device) includes a phone function, the middlewaremay further include a telephony manager for managing a voice or video call function of the electronic device.

1830 1830 1830 The middlewaremay include a middleware module for forming a combination of various functions of the above-mentioned elements. The middlewaremay provide a module specialized for each type of an operating system to provide differentiated functions. Furthermore, the middlewaremay delete a part of existing elements or may add new elements dynamically.

1860 The APIwhich is, for example, a set of API programming functions may be provided in different configurations according to an operating system. For example, in the case of Android or iOS, one API set may be provided for each platform, and, in the case of Tizen, at least two API sets may be provided for each platform.

1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 The application, for example, may include at least one application capable of performing functions such as a home, a dialer, an SMS/MMS, an instant message (IM), a browser, a camera, an alarm, a contact, a voice dial, an e-mail, a calendar, a media player, an album, a clock, health care (e.g., measure an exercise amount or blood sugar), or environmental information provision (e.g., provide air pressure, humidity, or temperature information).

1870 110 According to an embodiment of the present disclosure, the applicationmay include an information exchange application for supporting information exchange between the electronic device (e.g., the host device) and an external electronic device. The information exchange application may include, for example, a notification relay application for relaying specific information to the external electronic device or a device management application for managing the external electronic device.

For example, the notification relay application may have a function for relaying, to an external electronic device, notification information generated in another application (e.g., an SMS/MMS application, an e-mail application, a health care application, an environmental information application, or the like) of the electronic device. Furthermore, the notification relay application may receive notification information from the external electronic device and may provide the received notification information to the user.

The device management application, for example, may manage (e.g., install, delete, or update) at least one function (e.g., turn-on/turn off of the external electronic device itself (or some elements) or the brightness (or resolution) adjustment of a display) of the external electronic device communicating with the electronic device, an application running in the external electronic device, or a service (e.g., a call service, a message service, or the like) provided from the external electronic device.

1870 1870 1870 1810 According to an embodiment of the present disclosure, the applicationmay include a specified application (e.g., a healthcare application of a mobile medical device) according to an attribute of the external electronic device. The applicationmay include an application received from an external electronic device. The applicationmay include a preloaded application or a third-party application downloadable from a server. The names of the elements of the program moduleillustrated may vary with the type of an operating system.

1810 1810 1710 1810 According to various embodiments of the present disclosure, at least a part of the program modulemay be implemented with software, firmware, hardware, or a combination thereof. At least a part of the program module, for example, may be implemented (e.g., executed) by a processor (e.g., the processor). At least a part of the program modulemay include, for example, a module, a program, a routine, sets of instructions, or a process for performing at least one function.

A computer-readable recording medium may include a hard disk, a floppy disk, a magnetic medium (e.g., a magnetic tape), an optical medium (e.g., CD-ROM, digital versatile disc (DVD)), a magneto-optical medium (e.g., a floptical disk), or a hardware device (e.g., a ROM, a RAM, a flash memory, or the like). The program instructions may include machine language codes generated by compilers and high-level language codes that can be executed by computers using interpreters. The above-mentioned hardware device may be configured to be operated as one or more software modules for performing operations of various embodiments of the present disclosure and vice versa.

A module or a program module according to various embodiments of the present disclosure may include at least one of the above-mentioned elements, or some elements may be omitted or other additional elements may be added. Operations performed by the module, the program module or other elements according to various embodiments of the present disclosure may be performed in a sequential, parallel, iterative or heuristic way. Furthermore, some operations may be performed in another order or may be omitted, or other operations may be added.

While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the present disclosure as defined by the appended claims and their equivalents.