KR20190061733A - Device management system and method - Google Patents

Abstract

The present invention relates to a device management system using a semantic descriptor to manage a device and to a method thereof. According to the present invention, a device management system comprises: a registration portal receiving user information, device information, and a device ID to transmit the same; a portal server generating a semantic descriptor in accordance with the user and device information received from the registration portal to store the semantic descriptor with the user and device information, and receiving an inquiry request to transmit the semantic descriptor; a device gateway receiving and adding the semantic descriptor to a device or a gateway after transmitting the inquiry request to the portal server, and transmitting a device resource with respect to the device or gateway addition of the semantic descriptor; and an interface server receiving the device ID transmitted from the registration portal and the device resource transmitted from the device gateway to register the device to a platform by using the semantic descriptor.

Description

[0001] The present invention relates to a device management system and method,

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a device management system and method, and more particularly, to a device management system and method implemented to manage a device using a semantic descriptor.

[0003] In the communication between a person and a person via a device, and communication between a person and a device, communication between devices has become possible by the development of Internet of Things technology. Here, the Internet technology refers to a technology in which a sensor and a communication function are embedded in various objects to connect to the Internet, and objects refer to various systems such as home appliances, mobile equipment, and wearable computers. This kind of internet technology enables not only household appliances and electronic devices to share information by connecting objects in various fields such as healthcare, remote meter reading, smart home, and smart car.

When developing a system that operates in an environment where objects are connected, it can take thousands to hundreds of thousands of devices to connect to the network. And the cost of maintaining the built test environment for months to years without fail. In this paper, we developed a remote assist system using virtual device simulation.

The technology related to the remote help system using the virtual device simulation is related to a helper service which does not know how to use the smart device or informs the virtual device by simulating the same function and environment as the smart device when a problem occurs. However, since this technique is not a technique for facilitating network device simulation, it is necessary to create a plurality of virtual devices having actual device attributes (operation characteristics) so as to perform almost the same function as that of an actual device operating in a network It is said that technology for product development and testing is required.

Korean Patent Registration No. 10-1784796 (registered on Sep. 27, 2017) discloses a method of simulating a network device, and it is a method of simulating a network device by using at least one of the type information of a virtual device for which an attribute is defined, the number information for each type, A virtual device information input step of inputting the virtual device information through the user interface unit, and the virtual device creating unit transmits at least one of the type information of the virtual device, the number information of each type, or the attribute information of each type to the virtual device creating unit, A plurality of virtual device creation steps for creating a plurality of virtual devices of the defined attributes based on the plurality of virtual devices; A network device operation step of connecting a plurality of network devices to a network to operate the functions, and a network device simulating a network device operation by driving the virtual device software generated by the virtual device creation device in the form of a processor or a thread of the terminal A device operation simulation step, and a simulation result display step for displaying the simulation result on the display unit of the server. According to the disclosed technology, a real device can function as if it is operating in a network, saving time for building a test environment, and reducing product development and testing costs.

Korean Registered Patent No. 10-1698184 (registered on Jan. 13, 2013) can make a device a virtual object based on a semantic ontology, a device or a sensor included in a home network, A home network virtualization apparatus and its method capable of realizing a virtual home network service in which devices and objects are virtualized and managed and controlled on the web are disclosed. According to the disclosed technology, ICT device information and ICT resource information are acquired from a connected device, a virtual object capable of forming a physical object based on the acquired information is generated, and a virtual object for executing and managing the generated virtual object Offering; A composite object providing unit that creates a composite object including a composite function of information based on the generated virtual object and information of the non-ICT device, and executes and manages the generated composite object; And a device management unit for receiving the composite object according to the device management policy selected by the user and inputting the received composite object as service information based on the semantic ontology, A user information input unit for inputting information necessary for confirming the user information; A service policy management unit for establishing a policy of a service to be provided based on the received user information and managing service policy creation and service policy by requesting and acquiring a composite object according to a determined policy; A user profile is managed, a composite object providing unit is controlled according to a service policy to process a requested service, and service information generated according to a service policy is created, registered and stored as a virtual home network service in accordance with the semantic ontology basis And a semantic ontology service management unit that manages the semantic ontology.

In the conventional technology as described above, a developer or a user must have a single function of configuring a new device at the time of registering a new device, and it is inconvenient that the configured functionality should be matched with the device control information In addition, there is a disadvantage that device registration is very complicated and difficult.

Korean Patent No. 10-1784796 Korean Patent No. 10-1698184

SUMMARY OF THE INVENTION The present invention provides a device management system and method for managing a device using a semantic descriptor in order to solve the above-mentioned disadvantages.

According to one aspect of the present invention, there is provided a means for solving the above problems, comprising: a registration portal for receiving and transmitting user information, device information and device ID; A portal server for generating a semantic descriptor according to user information and device information received from the registration portal, storing the semantic descriptor together with user information and device information, receiving a query request, and transmitting the semantic descriptor; A device gateway for receiving the semantic descriptor after transmitting the inquiry request to the portal server and adding the semantic descriptor to the device or gateway, and for transmitting the device resource for the device or gateway addition of the semantic descriptor; And an interface server for receiving a device ID transmitted from the registration portal and a device resource transmitted from the device gateway, and registering the device in the platform using the semantic descriptor.

In one embodiment, the registration portal includes a registration input for inputting basic information of a device ID, a label, a device type, and an installation location and registration information of a unit, an aspect, a function, an ON type, an OFF type, a SET type, And a window is provided.

In one embodiment, the registration portal inputs the value using the value input by the user in the case of the device ID, and inputs the value into the input field of the device ID.

In one embodiment, the registration portal inputs a value using a value input by a user in the case of a label, and inputs the value into a field of a device label.

In one embodiment, the registration portal is automatically input by the user's selection in the case of the device type, is displayed in the device type name, and the value is inputted to the device type ID.

In one embodiment, the registration portal is automatically input by the user's selection in the case of the installation location, is displayed in the installation location table name, the value is input to the input field of the deployment location ID, Thereby forming a script.

In one embodiment, the registration portal is automatically input by a user's selection in the case of a unit, is displayed in a unit name, and a value is input to a field of a device function command unit.

In one embodiment, the registration portal automatically inputs by the user's selection in the case of aspect, displays only the code aspect name whose code name is the aspect, and inputs the value into the input field of the device function effector URI .

In one embodiment, the registration portal is characterized in that, in the case of a function, only a function name that is automatically input by a user's selection is displayed as a code function name, and a value is input to a field of a device function URI .

In one embodiment, the registration portal inputs a check box or a value input by a user in the case of device control (ON type, OFF type, SET type, GET type), and OFF / ON / SET / The GET value is input to the input field of the device function command type, the control name is input to the input field of the device function command name, and the control value is input to the input field of the device function command value.

In one embodiment, the portal server includes: a device information processing unit for confirming and storing user information and device information received from the registration portal; A semantic descriptor processing unit for receiving user information and device information from the device information processing unit to generate and store a semantic descriptor; And a memory unit for registering user information and device information transferred from the device information processing unit and a semantic descriptor transmitted from the semantic descriptor processing unit.

In one embodiment, the device gateway inquires a new semantic descriptor from the portal server.

In one embodiment, the interface server organizes a table used for creating semantic data using a semantic descriptor.

In one embodiment, the interface server registers user information, device information, and device ID input by a user using the device in each table, and displays the table attribute and the application for each column as comments.

In one embodiment, the interface server organizes a table including a code table, a deployment table, a device table, a device function table, a device function command table, and a device type table using a semantic descriptor.

In one embodiment, the interface server is configured to provide the code table with code IDs, code names, code URIs, code URI names, availability, constructor, creation time, modifier, modification time, And an aspect definition table including a measurement function table, a measurement function table, and the like.

In one embodiment, the interface server stores, in the case of the deployment table, information about a device-specific installation location including a deployment ID, a deployment location ID, a location ID, a use status, a generator, a generation time, a modifier, .

In one embodiment, the interface server includes a URI, a device name, a label, a producer / manufacturer, a device type ID, a physical device type ID, a use status, a generator, a generation time, a modifier, And device information including the device information.

In one embodiment, the interface server may include a device function table in which a device function ID, a device function name, a resource location on a platform, a function description, an aspect, a function, a functionality, , And device basic information including a modification time.

In one embodiment, the interface server is device type information including a device type ID, a device type name, a description, a URI, a use state, a generator, a generation time, a modifier, and a modification time in the case of a device type table do.

In one embodiment, the interface server includes a device function ID, a command type (ON, OFF, SET, GET), a control value, a command name, an operation name, a service name, Device control information including a unit of a command, whether to use the service, whether to use the service discovery, a creator, a creation time, a modifier, and a modification time.

In one embodiment, the interface server changes a table and a column of a table later by using a semantic descriptor.

In one embodiment, the interface server is configured to construct a functionality using a function and an aspect using a semantic descriptor.

In one embodiment, the interface server combines functions and aspects to form a func- tivity, and is used as information for controlling a device with a configured fun- actility.

According to another aspect of the present invention, there is provided a means for solving the above problems, comprising: a registration portal receiving user information, device information and a device ID and transmitting the received information; The portal server receiving the user information and the device information to generate a semantic descriptor and storing the semantic descriptor together with user information and device information; The device gateway transmitting an inquiry request to the portal server; The portal server receiving the inquiry request and transmitting a semantic descriptor; Receiving the semantic descriptor from the device gateway and adding the semantic descriptor to the device or gateway, and transmitting a device resource for the device or gateway addition of the semantic descriptor; And an interface server receiving the device ID and the device resource, and registering the device with the platform using the semantic descriptor.

According to the effect of the present invention, a device management system and a method that are implemented to manage a device using a semantic descriptor enable registration of a new device to be performed more conveniently and easily, Function that is a specification of a function that can be understood by a person and an aspect that is an object to which the function can be operated and influences can be combined to easily configure the functionality. It can be used as information to control the device directly with the configured functionality.

1 is a diagram illustrating a device management system according to an embodiment of the present invention.
FIG. 2 is a view for explaining a registration input window provided by the registration portal in FIG. 1. FIG.
FIG. 3 is a view for explaining a code table summarized by the interface server shown in FIG. 1. FIG.
FIG. 4 is a diagram illustrating a deployment table summarized in the interface server of FIG. 1. FIG.
5 is a diagram for explaining a device table summarized in the interface server of FIG.
6 is a view for explaining a device function table summarized in the interface server of FIG.
7 is a diagram illustrating a device type table summarized in the interface server shown in FIG.
8 is a view for explaining a device function command table summarized by the interface server shown in Fig.
Figure 9 is a diagram illustrating the functionality configured in the interface server of Figure 1;
10 is a diagram for explaining a device management method according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily carry out the present invention. However, the description of the present invention is merely an example for structural or functional explanation, and the scope of the present invention should not be construed as being limited by the embodiments described in the text. That is, the embodiments are to be construed as being variously embodied and having various forms, so that the scope of the present invention should be understood to include equivalents capable of realizing technical ideas. Also, the purpose or effect of the present invention should not be construed as limiting the scope of the present invention, since it does not mean that a specific embodiment should include all or only such effect.

The meaning of the terms described in the present invention should be understood as follows.

The terms " first ", " second ", and the like are intended to distinguish one element from another, and the scope of the right should not be limited by these terms. For example, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. It is to be understood that when an element is referred to as being "connected" to another element, it may be directly connected to the other element, but there may be other elements in between. On the other hand, when an element is referred to as being "directly connected" to another element, it should be understood that there are no other elements in between. On the other hand, other expressions that describe the relationship between components, such as "between" and "between" or "neighboring to" and "directly adjacent to" should be interpreted as well.

It should be understood that the singular " include " or " have " are to be construed as including a stated feature, number, step, operation, component, It is to be understood that the combination is intended to specify that it does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

All terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs, unless otherwise defined. Commonly used predefined terms should be interpreted to be consistent with the meanings in the context of the related art and can not be interpreted as having ideal or overly formal meaning unless explicitly defined in the present invention.

Now, a device management system and method according to an embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a view for explaining a device management system according to an embodiment of the present invention. FIG. 2 is a view for explaining a registration input window provided by the registration portal in FIG. 1, 4 is a view for explaining a deployment table summarized in the interface server of FIG. 1, FIG. 5 is a view for explaining a device table summarized by the interface server of FIG. 1, and FIG. , FIG. 6 is a view for explaining the device function table summarized by the interface server in FIG. 1, FIG. 7 is a view for explaining the device type table summarized in the interface server in FIG. 1, and FIG. FIG. 9 is a diagram for explaining a device function command table organized by an interface server, and FIG. 9 is a diagram for explaining a function function command table ctionality.

1 to 9, the device management system 100 includes a plurality of registered portals 110, a portal server 120, a device gateway 130, and an interface server 140.

The registration portal 110 receives user information and device information through input means such as a keyboard and a touch pad and transmits the user information and the device information to the portal server 120. The registration portal 110 receives the device ID through the input means, .

In one embodiment, the registration portal 110 may provide a registration input window as shown in FIG. 2 as a device information registration portal or a developer portal. Here, the registration input window includes basic information (device ID, label, device type, installation location), registration information (unit, aspect, function, ON type, OFF type, SET type, GET type ) To be entered into the corresponding name field or to be automatically completed when selected.

In one embodiment, the registration portal 110 may cause the user to use a value entered by the user in an input manner in the case of a device ID, and may cause the value to be entered into the device ID (device.id).

In one embodiment, the registration portal 110 may cause the user to use a value that the user enters in an input manner in the case of a label, and may cause the value to be entered into a device label (Device.label).

In one embodiment, the enrollment portal 110 may be configured to automatically complete an input method in the case of a device type, without user input, by the user's choice, and is represented by a device type name (DeviceType.name) DeviceType.id) to the device type ID (Device.DeviceType.id).

In one embodiment, the registration portal 110 can be automatically entered by the user's choice without user input in the case of the installation location, and can be displayed in the installation location name (location.name) , A value (location.id) may be input to the deployment location ID (Deploy.location_id), and a script of the installation location table may be formed.

In one embodiment, the registration portal 110 may be configured to automatically complete an input method in the unit of a user's selection without user input, and is represented by a unit name (Unit.name). id) to the device function command unit (DeviceFunctionCmd.unit).

In one embodiment, the registration portal 110 may be configured to automatically complete an input method in the case of an aspect without user input, by the user's choice, and only the code name aspect (cname = 'aspect' (Code.vname), and the value (Code.vid) can be input to the device function applicator URI (DeviceFunction.aspecturi).

In one embodiment, the registration portal 110 may be configured to automatically complete an input method in the case of a function without user input, by the user's choice, and only the code name function (cname = 'function' , And the value (Code.vname) can be input to the device function URI (DeviceFunction, functionuri).

In one embodiment, the enrollment portal 110 may select a checkbox as an input method in the case of device control (ON type, OFF type, SET type, GET type), and the OFF / ON / SET / GET value Can be input to the device function command type (DeviceFunctionCmd.cmd_type), the control name can be input to the device function command name (DeviceFunctionCmd.cmd_name), and the control value can be input to the device function command value (DeviceFunctionCmd.cmd_value) . If the command type (cmd_type) is set to 'SET' or 'GET', the registration portal 110 can not input 'l' but input it to each row. 1 ~ 10 ',' ~ ', and so on.

The portal server 120 receives user information and device information transmitted from the registration portal 110, generates a semantic descriptor according to the received user information and device information, and transmits the generated semantic descriptor to the received user information And device information, and receives the inquiry request transmitted from the device gateway 130, and delivers the semantic descriptor to the device gateway 130 according to the received inquiry request.

In one embodiment, the portal server 120 may include a device information processing unit 121, a semantic descriptor processing unit 122, and a memory unit 123.

The device information processing unit 121 confirms the user information and the device information received from the registration portal 110 and transmits the confirmed user information and device information to the semantic descriptor processing unit 122. The device information processing unit 121 also transmits the identified user information and device information It stores information.

The semantic descriptor processing unit 122 generates a semantic descriptor according to user information and device information transmitted from the device information processing unit 121 and stores the generated semantic descriptor in the memory unit 123. [

The memory unit 123 registers the user information and the device information transmitted from the device information processing unit 121 and the semantic descriptor transmitted from the semantic descriptor processing unit 122. [

The device gateway 130 receives an inquiry request for the semantic descriptor to the portal server 120, receives the semantic descriptor transmitted from the portal server 120, adds the semantic descriptor to the device (or gateway) (Including the semantic descriptor) for the addition of the device (or gateway) of the descriptor to the interface server 140.

In one embodiment, the device gateway 130 can query the portal server 120 for a new semantic descriptor.

The interface server 140 receives the device ID transmitted from the registration portal 110 and the device resource (including the semantic descriptor) transmitted from the device gateway 130 and transmits the device to the platform 130 using the received semantic descriptor. (Platform).

In one embodiment, the interface server 140 may register the device on the platform (or IoT platform) using the device information (semantic descriptor) received from the device gateway 130 to automate device registration. You can organize the tables used to create semantic data (ontology) using descriptors, and you can register the information entered by the user who uses the device in each table. You can mark it as a comment, and you can attach some of your current data to the bottom of the table structure. Here, the table may include a code table, a Deploy table, a device table, a device function table, a device function command table, a device type table, and the like.

In one embodiment, the interface server 140 includes an aspect definition table (code ID (cid), code name (cname), code URI (vid), code URI name (vname), use_yn, constructor (cuser), creation time (cdate), modifier (uuser), modification time (udate), base functionality (control func- tivity, measurement func- tivity etc.) base_functionality), etc.).

4, in the case of the deployment table, the interface server 140 stores information (deployment ID (id), deployment location ID (device_id), location ID (location_id), use_yn, constructor (cuser), creation time (cdate), uuser, modification time (udate), etc.).

In one embodiment, the interface server 140 includes device information (URI (uri), device name, label, creator ), A device type ID (id), a physical device type ID (pdt_id), a use_yn, a cuser, a creation time (cdate), a uuser, a modification time (udate) Etc.).

6, in the case of the device function table, the interface server 140 includes a device function ID (id), a device function name (device_name), a resource location on the platform (functionResourceUri), a function description such as comment, aspecturi, functionuri, functionalityuri, use_yn, cuser, creation time (cdate), modifier (uuser), modification time (udate) And may include device basic information.

In one embodiment, the interface server 140 determines the device type ID (id), the device type name (name), the description (comment) ), A URI, a use_yn, a cuser, a creation time (cdate), a uuser, a modification time (udate), and the like).

8, in the case of the device function command table, the interface server 140 stores a device function ID (id), a command type (ON, OFF, SET, GET) (cmd_type) A service name, a service label, a service_label, a command unit, a use_yn, a service discovery status, and a discovery_yn. Device-specific control information on a device name, a cuser, a creation time (cdate), a modifier (uuser), a modification time (udate), and the like.

In one embodiment, the interface server 140 may change the columns of the table and the table at a later time using the semantic descriptor.

In one embodiment, the interface server 140 may configure the functionality as shown in FIG. 9 using the functions and aspects using the semantic descriptors. Here, the function may be a specification of a function that can be understood by a person, such as an adjustment, a measurement, etc., and an aspect may be an object to which a function can be operated and influence, for example, temperature, humidity, Broadly speaking, a device can be a unique feature specification.

In one embodiment, the interface server 140 may combine functions and aspects to form a func- tivity, and use the information to control the device with the configured fun- damility.

In one embodiment, the interface server 140 may provide driver information at the time of registering the device with the platform, thereby allowing the platform to dynamically control commands and control values for control. Here, the command may be ON, OFF, SET, GET and the like, and the control value means various values provided when the SET command is used.

In the device management system 100 having the above-described configuration, as described above, the device that has completed the automatic registration can transmit information about the sensor to the platform, and the platform collects the sensor information transmitted from the device So that it is possible to carry out smart control according to an emergency situation or user and space situations.

The device management system 100 having the above-described configuration implements management of a device using a semantic descriptor, so that registration of a new device can be performed more conveniently and easily, The function that is the specification of the function that can be operated and the aspect that is the object that can affect the function can be combined to easily form the functivity. The information for controlling the device directly by the configured functivity To be used.

10 is a diagram for explaining a device management method according to an embodiment of the present invention.

10, when a developer or a user inputs user information and device information through input means such as a keyboard or a touch pad, the registration portal 110 transmits user information and device information input through the input means to a portal And transmits it to the server 120. When the developer or the user inputs the device ID through the input means, the registration portal 110 transmits the device ID input through the input means to the interface server 140 (S901).

In transmitting the user information, the device information, and the device ID in step S901 described above, the registration portal 110 can provide a registration input window as shown in FIG. 2 to the developer or the user, You can enter basic information (device ID, label, device type, installation location), registration information (unit, aspect, function, ON type, OFF type, SET type, GET type) have. In the registration input window, basic information (device ID, label, device type, installation position), registration information (unit, aspect, function, ON type, OFF type, SET type, GET type) Etc., or to be automatically completed when selected.

In transmitting the user information, the device information, and the device ID in the above-described step S901, the registration portal 110 may input the device ID by using the value input by the user when inputting the device ID, device.id ") (for simplicity of explanation, the term " input field " is omitted and the same applies to the following description).

In transmitting the user information, the device information, and the device ID in the above-described step S901, the registration portal 110 may use the value input by the user when the label is input. At this time, the value can be input to the device label (Device.label).

In transmitting the user information, the device information, and the device ID in the above-described step S901, the registration portal 110 can automatically complete the device type input by the user without user input. At this time, the device type name (DeviceType.name) is displayed, and the value (DeviceType.id) can be input to the device type ID (Device.DeviceType.id).

In transmitting the user information, the device information, and the device ID in the above-described step S901, the registration portal 110 can automatically input the installation position when the user selects it without inputting the user. At this time, it can be displayed as the installation location table name (location.name), the value (location.id) can be inputted into the deployment location ID (Deploy.location_id), the table script Table Script).

In transmitting the user information, the device information, and the device ID in the above-described step S901, the registration portal 110 can automatically complete the unit input by the user's selection without inputting the user. At this time, it can be displayed as a unit name (Unit.name), and a value (Unit.id) can be inputted in a device function command unit (DeviceFunctionCmd.unit).

In transmitting the user information, the device information, and the device ID in the above-described step S901, the registration portal 110 can automatically complete the aspect by the user's selection without inputting the user. At this time, only the code name with the aspect name cname = 'aspect' can be displayed as the code aspect name Code.vname, and the value Code.vid can be input into the device function aspect URI (DeviceFunction.aspecturi) .

In transmitting the user information, the device information and the device ID in the above-described step S901, the registration portal 110 can automatically complete the function input by the user without inputting the user. At this time, only the code name having the function (cname = 'function') can be displayed as the code function name, and the value (Code.vname) can be inputted to the device function URI (DeviceFunction, functionuri).

When the device control (ON type, OFF type, SET type, GET type) is inputted in the above-described step S901 in transmitting the user information, device information and device ID, in the registration portal 110, Can be used. At this time, the OFF / ON / SET / GET value can be input to the device function command type (DeviceFunctionCmd.cmd_type), the control name can be input to the device function command name (DeviceFunctionCmd.cmd_name) Value (DeviceFunctionCmd.cmd_value). When the command type (cmd_type) is 'SET' or 'GET', the registration portal 110 can input '1' to each row without connecting 'l' ~ 10 ',' ~ ', and so on.

When the user information, the device information, and the device ID are transmitted in the above-described step S901, when the user information and the device information transmitted from the registration portal 110 are received, the portal server 120 transmits the received user information, The semantic descriptor is generated according to the device information, and the generated semantic descriptor is stored together with the received user information and device information (S902).

The device information processing unit 121 of the portal server 120 checks the user information and device information received from the registration portal 110 and confirms the corresponding information And transmits the user information and the device information to the semantic descriptor processing unit 122 of the portal server 120. The semantic descriptor processing unit 122 generates a semantic descriptor according to the user information and the device information transmitted from the device information processing unit 121 and transmits the generated semantic descriptor to the memory unit 123 of the portal server 120 And stores it. In addition, the device information processing unit 121 stores the confirmed user information and device information in the memory unit 123.

In the case where the semantic descriptor, the user information and the device information are stored in the above-described step S902 and then the device ID transmitted from the registration portal 110 is received, the interface server 140 stores the received device ID (S903).

After storing the device ID in the above-described step S903, the device gateway 130 transmits an inquiry request for the semantic descriptor to the portal server 120 (S904).

When the portal server 120 receives the inquiry request transmitted from the device gateway 130 in step S904, the portal server 120 transmits the semantic descriptor to the device gateway 130 according to the received inquiry request, (S905).

When the semantic descriptor is transmitted in step S905, when receiving the semantic descriptor transmitted from the portal server 120, the device gateway 130 adds the received semantic descriptor to the device (or gateway) (S906).

After adding the semantic descriptor to the device (or the gateway) in the above-described step S906, the device gateway 130 acquires the device resource (including the semantic descriptor) for the device (or gateway) addition of the semantic descriptor To the interface server 140 (S907).

When receiving the device resource (including the semantic descriptor) transmitted from the device gateway 130 when the device resource is transmitted in the above-described step S907, in the interface server 140, the received device resource (the semantic descriptor To automatically register the device with the platform (S908).

In registering the device in the above-described step S908, the interface server 140 can organize the tables used for creating the semantic data (ontology) using the semantic descriptor. At this time, the interface server 140 can register information (for example, user information, device information, device ID) input by a user using the device in each table, and displays the table attribute and the application for each column as comments And attach some of the data currently in use to the bottom of the table structure.

In registering the device in the above-described step S908, the interface server 140 registers information (for example, user information, device information, device ID) input by the user by using the semantic descriptor as a code table, a deployment table, , Device function table, device type table, and the like.

In registering the device in the above-described step S908, the interface server 140 registers the code ID (cid), the code name (cname), the code URI (vid), the code URI name (vname) , Use_yn, constructor (cuser), creation time (cdate), modifier (uuser), modification time (udate), base functionality (control functality, measurement functivity etc) (base_functionality) Can be registered in the aspect definition table as shown in FIG.

When registering the device in the above-described step S908, in the case where the registration is made in the deployment table, the interface server 140 acquires the information (installation ID (id), deployment location ID (device_id) A location ID, a use_yn, a cuser, a creation time (cdate), a uuser, a modification time (udate), etc.) are registered in a deployment table as shown in Fig. You can give.

When registering the device in the above-described step S908, the interface server 140 registers the device information (URI (uri), the device name (name), the label, the producer / manufacturer creator), a device type ID (id), a physical device type ID (pdt_id), a use_yn, a cuser, a creation time (cdate), a uuser, a modification time (udate) It is possible to register in the device table as shown in FIG.

When registering the device in the above-described step S908, the interface server 140 registers the device function ID (id), the device function name (device_name), the resource location on the platform (functionResourceUri) It is possible to use comments, aspecturi, functionuri, functionalityuri, use_yn, cuser, cdate, uuser, udate, And the like can be registered in the device function table as shown in Fig.

In registering the device in the above-described step S908, when registering the device in the device type table, the interface server 140 acquires information on the device type (device type ID (id), device type name comment), a URI, a use_yn, a cuser, a creation time (cdate), a uuser, a modification time (udate), etc.) .

In registering the device in the device function command table in step S908 described above, the interface server 140 registers the device function ID (id), the command type (ON, OFF, SET, GET) (cmd_type) A service name (service_name), a label (service_label) for a service, a unit of a command, a use_yn, and whether or not a service discovery (discovery_yn), a command value (cmd_name), an operation name Device-specific control information on the device name, cuser, creation time (cdate), modifier (uuser), modification time (udate), and the like can be registered in the device function command table as shown in Fig.

In registering the device in the above-described step S908, the interface server 140 may change the columns of the table and the table later using the semantic descriptor.

In registering the device in the above-described step S908, the interface server 140 can construct the functionality as shown in FIG. 9 using the function and the aspect by using the semantic descriptor.

In registering the device in the above-described step S908, the interface server 140 can configure the functionality by combining the function and the aspect, and can use the information for controlling the device with the configured functionality have.

As described above, the embodiment of the present invention is not limited to the above-described apparatus and / or method, but may be implemented by a program for realizing a function corresponding to the configuration of the embodiment of the present invention and a recording medium on which the program is recorded And the present invention can be easily implemented by those skilled in the art from the description of the embodiments described above. While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, It belongs to the scope of right.

100: Device Management System
110: Registration Portal
120: Portal Server
121: Device information processor
122: Semantic descriptor processing unit
123:
130: Device gateway
140: interface server

Claims (5)

A registration portal for receiving and transmitting user information, device information and device ID;
A portal server for generating a semantic descriptor according to user information and device information received from the registration portal, storing the semantic descriptor together with user information and device information, receiving a query request, and transmitting the semantic descriptor;
A device gateway for receiving the semantic descriptor after transmitting the inquiry request to the portal server and adding the semantic descriptor to the device or gateway, and for transmitting the device resource for the device or gateway addition of the semantic descriptor; And
And an interface server for receiving a device ID transmitted from the registration portal and a device resource transmitted from the device gateway, and registering the device with the platform using the semantic descriptor.
The terminal according to claim 1,
A registration input window for inputting a resource location, a label, a device type, a device control, a unit, an aspect, a function, a service name, a discovery, an installation location, and a creator is provided.
The terminal according to claim 1,
A user ID, and a current date are input to the device management system.
2. The portal server according to claim 1,
A device information processing unit for confirming and storing user information and device information received from the registration portal;
A semantic descriptor processing unit for receiving user information and device information from the device information processing unit to generate and store a semantic descriptor; And
And a memory unit for registering user information and device information transmitted from the device information processing unit and a semantic descriptor transmitted from the semantic descriptor processing unit.
Receiving and transmitting user information, device information, and device ID from a registration portal;
The portal server receiving the user information and the device information to generate a semantic descriptor and storing the semantic descriptor together with user information and device information;
The device gateway transmitting an inquiry request to the portal server;
The portal server receiving the inquiry request and transmitting a semantic descriptor;
Receiving the semantic descriptor from the device gateway and adding the semantic descriptor to the device or gateway, and transmitting a device resource for the device or gateway addition of the semantic descriptor; And
The interface server receiving the device ID and the device resource, and registering the device with the platform using the semantic descriptor.

Images