KR20170127339A - Trust evaluation model and system in iot - Google Patents

Abstract

According to an embodiment of the present invention, a reliability analysis system comprises: a collecting unit for collecting internal data and external data; a calculating unit for calculating reputation and mutual reciprocity of an entity using the internal data or the external data, and calculating reliability of the entity based on the calculated reputation and mutual reciprocity; a processing unit for comparing the measured reliability of the entity with a threshold value, and determining a reliable state and an accessible state so as to notify a result to an owner of an IoT system; and an updating unit for updating the threshold value on the entity based on the result on the reliable state and the accessible state.

Description

[0001] TRUST EVALUATION MODEL AND SYSTEM IN IOT [0002]

The following description relates to a technique for analyzing reliability in the IoT environment.

Recently, IoT (Internet of Things) technology is emerging that connects all the objects through the Internet and shares information. In the IoT environment, all things in life (for example, household appliances, user terminals, sensors, etc.) are connected to the Internet to share and accumulate information. Based on accumulated big data, smart home, smart building, industrial automation, It enables smart services with intelligence such as telemedicine.

The development of IoT technology in a variety of industries and environments creates a super-connected society in which a number of IoT devices are connected via the IoT network. Accordingly, in the IoT environment that forms the massive connectivity, security and privacy problems become serious, and reliability problems of terminals, users, and the like may occur. In particular, unnecessary data may accumulate in the IoT system due to unreliable behavior of the terminal or the user, which may result in malfunction and quality degradation of the service. Therefore, reliability problems can not be solved with existing security solutions.

Therefore, many IoT devices accessing the IoT network control access to untrusted devices in the IoT system in order to provide smart services with correct behavior and useful information. In order to prevent the degradation of service quality, IoT device authentication and Control mechanism technology is needed.

In IoT systems, interaction with unknown entities often occurs, and there is a question of whether they can be trusted in online space, even if they are already known entities. Untrusted entities take actions that degrade service quality, such as data biasing, rather than lethal attacks such as virus attacks, which are difficult to address with existing security solutions.

Accordingly, there is a need for a reliability analysis system for accumulating data associated with IoT systems and systems to determine whether or not to trust unknown, suspicious, and known entities, and to determine whether to allow access to the system.

The present invention relates to a method for analyzing and controlling the reliability of real-time data collection and processing in an IoT system connected with a social network, and calculating reliability based on reputation and mutual reciprocity of an entity approaching the IoT system. Control method.

According to one embodiment, the reliability analysis system comprises: a collection unit for collecting internal data and external data; A calculation unit calculating the reputation and mutual reciprocity of the entity using the internal data or the external data, and calculating the reliability of the entity based on the calculated reputation and mutual reciprocity; A processing unit for comparing the reliability of the calculated entity with a threshold value to determine whether the entity is reliable or not, and notifying the owner of the IoT system of the result; And an update unit for updating a threshold value for the entity based on the result of the reliability and access permission.

The collecting unit may include an internal data collecting unit for collecting internal data based on the number of times that the IoT system is allowed to access, the number of permitted accesses of belonging entity entities, the total access attempted number of the entity, and the total permitted access count of the entity .

Wherein the collecting unit is configured to collect information on the basis of the total number of times of activity of the owner of the IoT system, the number of times of activity of the owner by entity of the entity, the number of messages transmitted by the owner to the entity, and the number of messages transmitted by the entity to the owner And an external data collection unit for collecting external data.

Wherein the calculation unit includes: a reputation calculation unit for calculating reputation of an entity to access the IoT system using the internal data and reputation of an affiliate of the entity; A reciprocal reciprocity calculation unit for calculating reciprocal reciprocity for entities that want to access the rights of the owner of the IoT system using the external data; And a reliability calculation unit for calculating reliability of the entity based on the calculated reputation and mutual reciprocity.

Wherein the processing unit comprises: a reliability determining unit that compares reliability of the calculated entity with a threshold value to determine reliability and accessibility; And a notification and response unit for informing the owner of the IoT system of the determination of the determined reliability and whether to permit the access, and receiving feedback on the determination.

The updating unit may update the threshold value for the entity if the determination as to whether or not the determined trustworthiness and the access permission is wrong is wrong.

According to one embodiment, a computer readable medium comprising instructions for a computer system to analyze reliability, the instructions comprising: collecting internal data and external data; Calculating the reputation and mutual reciprocity of the entity using the internal data or the external data, and calculating reliability of the entity based on the calculated reputation and mutual reciprocity; Comparing the reliability of the calculated entity with a threshold value to determine whether the entity is trustworthy and whether to allow access, and notifying the owner of the IoT system of the result; And updating the threshold for the entity based on the result of the trust and access permission.

According to one embodiment, a reliability analysis method includes: collecting internal data and external data; Calculating the reputation and mutual reciprocity of the entity using the internal data or the external data, and calculating reliability of the entity based on the calculated reputation and mutual reciprocity; Comparing the reliability of the calculated entity with a threshold value to determine whether the entity is trustworthy and whether to allow access, and notifying the owner of the IoT system of the result; And updating the threshold for the entity based on the result of the trustworthiness and accessibility.

The step of collecting the internal data and the external data may further comprise the step of collecting internal data based on the number of times that the IoT system is allowed to access, the access permitted number of belonging entity entities, the total access attempt number of the entity, And collecting the data.

The step of collecting the internal data and the external data further comprises the steps of: collecting information on the number of total activities of the owner of the IoT system, the number of activities of the owner by entity of the entity, the number of messages the owner has sent to the entity, And collecting external data based on the number of transmitted messages.

Calculating the reputation and mutual reciprocity of the entity using the internal data or the external data and calculating the reliability of the entity based on the calculated reputation and mutual reciprocity, Computing the reputation of the entities to access and the reputation of the entities of the entities and calculating mutual reciprocity for the entities wishing to access the rights of the owner of the IoT system using the external data, The reliability of the entity may be calculated based on the reliability of the entity.

Comparing the reliability of the calculated entity with a threshold to determine whether the entity is trustworthy and whether to allow access, and notifying the owner of the IoT system of the result of the comparison, comparing the reliability of the calculated entity with a threshold value, Determining whether or not access is permitted, notifying the owner of the IoT system of the determined reliability and whether or not the access is permitted, and receiving feedback on the determination.

Wherein updating the threshold for the entity based on the result of the trustworthiness and access permission comprises: if the determination of the determined trustworthiness and the access permission is incorrect, For example.

The present invention is applicable to all IoT services. In particular, it is possible to integrate smart home door locks, smart building doors, or IoT services in a shared economic environment.

In the IoT system based on Massive Connectivity, unnecessary data accumulates due to reliability problems of sensors, terminals, and users that can not be solved by a security solution alone, and malfunction and quality degradation of services may occur due to unreliable behavior And by analyzing the reliability based on reputation and mutual reciprocity, a reliable IoT ecosystem can be constructed.

1 is a diagram for explaining an IoT environment according to an embodiment.
2 is a block diagram illustrating a configuration of a reliability analysis system according to an embodiment.
3 is a flowchart illustrating a reliability analysis method of a reliability analysis system according to an exemplary embodiment of the present invention.
4 is a detailed flowchart for explaining a reliability analysis method of a reliability analysis system according to an embodiment.
FIG. 5 is an example of applying the reliability analysis system according to an embodiment.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings.

1 is a diagram for explaining an IoT environment according to an embodiment.

First, the structure of the Internet of Things (IoT) software platform in the reliability analysis system is described. For example, the components of the reliability analysis system may operate in the IoT environment using the D-platform, the P-platform, and the M-platform, depending on the object's Internet communication method.

The object Internet software platform may include, for example, a D-platform, a P-platform and an M-platform.

Here, the D-platform represents a software platform installed on the IoT device side, and the P-platform and M-platform may represent a software platform installed separately or together on the server computer side.

The D-Platform is an abbreviation of Device Platform. It is installed in the IoT adapter installed directly on the IoT device or installed in the IoT device, and works in conjunction with the P-platform and M-platform, and the IoT application and the IoT website To interact with smart devices. Here, the IoT device can represent objects to which IoT is applied.

The IoT adapter is mounted on an IoT device, allowing things to use IoT communication. The IoT adapter includes a communication module capable of communicating via at least one of short-range wireless communication, Wi-fi, Ethernet, 3G and LTE, and the D- platform installed in the IoT adapter can perform IoT communication To provide a variety of functions.

P-platform is an abbreviation of "Planet platform" and can perform functions such as IoT device management, user management, IoT device monitoring, and IoT device search. Specifically, the P-platform receives information about the IoT device from the IoT service provider and registers the IoT device. In this case, the information about the IoT device includes, for example, a device ID, a device name, a model name, a manufacturer, a location information, and device status information, and an address (for example, IP address, MSISDN, etc.) necessary for connection to the IoT device .

The P-platform may then perform authentication for the user accessing to register and download the IoT application for the IoT service. To authenticate the user, the P-platform may have personal information such as the user's ID / PW, telephone number, etc.

In addition, the P-platform can perform service / developer authentication for authenticating a developer who develops and registers a mash-up service related to IoT, or a service user who uses a mashup service.

In addition, the P-platform can authenticate the IoT service user's access to the IoT service using an application of a smart device (e.g., smart phone, tablet, etc.) used as an IoT device.

The M-platform is an abbreviation of a mash-up platform, and can communicate with the D-platform to transmit control commands of the service user through the IoT application or the IoT web page to the IoT device.

In addition, the M-platform can register the IoT mashup service developed by the mashup service developer. That is, the mashup service developer develops the IoT mashup service and registers it on the M-platform. At this time, the mashup service developer can develop the IoT mashup service using the IoT open API provided from the open API server.

The IoT devices periodically transmit the data generated by the M-platform to the M-platform, and the M-platform can provide various IoT mashup services to the service user by collecting the data generated by the IoT device and storing the logs.

In addition, the M-platform performs billing based on the use of the IoT mashup service, and may store brief information (e.g., ID, IP address, etc.) about IoT devices.

The open API server can manage and provide the open API related to the IoT service. Specifically, the developer of the IoT device develops an open API for the corresponding IoT device when manufacturing the IoT device, registers the related open API in the open API server, and stores the open API. Then, the open API server registers and stores various open APIs for each IoT device developed by various developers.

The open API server can provide the stored open API to developers who want to develop IoT service related websites, mashup service sites and applications. Therefore, when developers develop web sites related to IoT service, mashup service sites and applications, they will be able to develop IoT services using the open APIs provided by receiving open APIs from the open API server.

For example, if an IoT device manufacturer registers an open API with an open API server that provides status information (for example, failure) for the IoT device, the developer can retrieve the open status API from the open API server A function of inquiring the status of the IoT device can be implemented in the IoT service related web site, the mashup service site, and the IoT application.

On the other hand, the IoT service user can directly access the IoT device and use the IoT service by using the IoT application downloaded to the smart device, which is a kind of mobile device. At this time, the IoT device can be connected through the intermediation of the smart device and the M-platform or directly through the peer-to-peer (P2P) communication to provide the IoT service. In this case, the D-platform of the IoT device communicates indirectly with the IoT application of the smart device through the relay of the M-platform or directly by using the P2P communication.

The IoT software platform with such a configuration can provide various IoT services by interworking with D-platform, P-platform, and M-platform.

In this way, in the IoT environment, since objects and people are connected and actors of objects are often people, not only trust in IoT devices but also reliability of people using IoT devices is very important.

Since the IoT system provides advanced services by interworking with various services such as social network services, it can utilize not only the data by the interaction between the IoT devices (IoT clients) but also the external data provided by the interlocked service.

In addition, trust in a person's relationship is due to the subjective belief of an individual expecting that an individual will perform a beneficial action to another person. Therefore, a single authentication node is required to perform a uniform authentication test on the client node (IoT device) Assigning a confidence level is problematic. This is because a node trusts the same client node, while another node may not trust it. Accordingly, the following description will describe a reliability analysis system and method that can express an individual subjective belief index.

According to embodiments, the reliability analysis system can perform reliability analysis based on the reliability of a person (entity) that is an actor of the IoT device. In particular, reliability can be calculated by using external data and internal data of IoT system in IoT linked with external service. The reliability analysis system can express individual subjective belief indicators quickly and accurately by varying the threshold of reliability through real-time collection of external data and receiving feedback on the reliability system operation from a trusting subject.

2 is a block diagram illustrating a configuration of a reliability analysis system according to an embodiment.

The reliability analysis system may include a collection unit 210, a calculation unit 220, a processing unit 230, and an update unit 240.

The collecting unit 210 may collect the external data through the internal data collecting unit 211 and the external data collecting unit 212. In this case, the internal data may refer to historical data of a reliability analysis system operating in the IoT system, and the external data may refer to IoT user related data that can be acquired in a social network service interworking with the IoT system.

The internal data collection unit 211 may collect internal data based on the number of times that the IoT system is allowed to access, the number of permitted accesses of the belonging entity, the total number of access attempts of the entity, and the total permitted number of accesses of the entity.

The external data collecting unit 212 collects external data based on the total number of operations of the owner of the IOT system, the number of times of operation of the owner by the entity of the entity of the entity, the number of messages that the owner has sent to the entity, Can be collected.

The calculation unit 220 may calculate the reputation and mutual reciprocity of the entity using internal data or external data, and calculate the reliability of the entity based on the calculated reputation and mutual reciprocity.

 The calculation unit 220 includes a reputation calculation unit 221 for calculating a reputation of an entity to access the IoT system using internal data and a reputation of an affiliate of the entity, A mutual reciprocity calculation unit 222 for calculating reciprocal reciprocity with respect to the entity to be selected, and a reliability calculation unit 223 for calculating the reliability of the entity based on the calculated reputation and mutual reciprocity.

The reputation calculation unit 221 can calculate the reputation of the user based on the internal data (historical data of the IOT reliability analysis system) and can calculate the initial value of the reputation based on the external data if there is no historical data. At this time, since the reputation calculation unit 221 calculates the reputation using the internal data and the external data, the user's reputation in the IoT system is different from the reputation used in the existing data reliability technology. At this time, the term "reputation" refers to the preponderance of objectively defined entities within a group. If the individual's reputation is high, the probability of being trusted is high, but this is not necessarily the case.

The mutual reciprocity calculation unit 222 can calculate reciprocity between the owner and the entity using the external data. The mutual reciprocity calculation unit 222 can set the reciprocal reciprocity so that the reciprocal reciprocity can be increased so that the reciprocal reciprocity of the recipient is higher than that of the reciprocal reciprocity. Interactional reciprocity can mean the degree to which an individual interacts with another person.

The reliability calculation unit 223 can calculate the reliability based on reputation and mutual reciprocity. Suppose, for example, that an entity and an owner exchange messages with each other through an external service, each with a specific group or organization. When an entity tries to access the owner's IoT system, the extent to which the owner has acted on the external service, the extent to which the owner and entity have exchanged messages with each other, and how much the entity has accessed the IoT system prior to the pre- The reputation and reciprocal reciprocity are calculated based on whether or not the recipient has attempted the reciprocal reciprocal reciprocity. At this time, the formula may be changed according to the collected data and the weight.

The processing unit 230 may compare the reliability of the calculated entity with a threshold value to determine the reliability and access permission, and notify the owner of the IoT system of the result. The processing unit 230 compares the reliability of the calculated entity with a threshold value to determine whether the trust is possible and whether the access is permitted or not. And a notification and response unit 232 that receives feedback on the decision.

The update unit 240 may update the threshold value for the entity based on the result of the reliability and access permission. The updating unit 240 can update the threshold value for the entity if the determined reliability and the determination of the access permission are incorrect.

Even if the reliability value is subjective, the reliability analysis system can implement the subjective judgment of the owner.

3 is a flowchart illustrating a reliability analysis method of a reliability analysis system according to an exemplary embodiment of the present invention.

In step 301, the reliability analysis system may collect internal data and external data. At this time, the reliability analysis system can collect historical data on the operation of the reliability analysis system with internal data, and can collect user data from an external service linked with the IOT system as external data.

), 소유주가 엔티티에게 전송한 메시지의 수(

), 엔티티가 소유주에게 전송한 메시지의 수(

)에 기반하여 외부 데이터를 수집할 수 있다. 또한, 신뢰도 분석 시스템은 IoT 시스템에 총 접근 허용된 횟수(n), 소속 기관 엔티티들의 접근 허용 횟수(

), 소유주 j의 총 접근 시도 횟수(

), 소유주의 총 접근 횟수(

)에 기반하여 내부 데이터를 수집할 수 있다. 이때, 신뢰도 분석 시스템은 신뢰도에 대한 임계값(Threshold)을 아래와 같이, 설정할 수 있다. More specifically, referring to FIG. 4, in step 401, the reliability analysis system calculates the total number of activities (N) of the trustor, the number of activities of the owner

), The number of messages the owner sent to the entity (

), The number of messages that the entity sent to the owner (

) To collect external data. In addition, the reliability analysis system calculates the number of permitted accesses (n) to the IoT system, the allowable number of accesses of affiliate entities

), The total number of access attempts of owner j (

), The owner's total accesses (

). ≪ / RTI > At this time, the reliability analysis system can set a threshold value for reliability as follows.

In step 302, the reliability analysis system may sense accessing the IoT system from an entity (trusted party).

). 단계(402)에서 신뢰도 분석 시스템은 엔티티 j의 소속 기관에 대한 평판을 아래의 식을 통하여 계산할 수 있다. In step 303, the reliability analysis system may calculate the reputation of the group to which the entity belongs (

). In step 402, the reliability analysis system may calculate the reputation of entity j of entity j through the following equation.

At this time, if the entity of the entity has not accessed the IoT system, the initial value of the reputation is calculated based on the external data, and then an objective reputation can be calculated according to the allowed number of accesses.

). 단계(403)에서 신뢰도 분석 시스템은 엔티티 j의 평판을 아래의 식을 통하여 계산할 수 있다. In step 304, the reliability analysis system may calculate the reputation of the entity (

). In step 403, the reliability analysis system may calculate the reputation of entity j through the following equation.

At this time, the reputation of the entity can be calculated based on how much the entity is allowed to access the IoT system.

). 단계(404)에서 신뢰도 분석 시스템은 아래의 식을 통하여 엔티티 j와 소유주i 간의 상호 호혜성을 계산할 수 있다. In step 305, the reliability analysis system may calculate mutual reciprocity between the entity and the owner (

). In step 404, the reliability analysis system may calculate mutual reciprocity between entity j and owner i through the following equation.

는 n 시간까지 소유주가 엔티티에게 송신한 메시지의 수,

는 n-1 시간까지 소유주가 엔티티에게 송신한 메시지의 수,

는 n-1 시간까지 엔티티가 소유주에게 송신한 메시지의 수를 의미한다.At this time,

Is the number of messages that the owner sent to the entity until n hours,

Is the number of messages the owner has sent to the entity up to n-1 hours,

Means the number of messages sent by the entity to the owner by n-1 time.

The greater the number of messages sent to the entity by the owner, the greater the mutual reciprocity, and the greater the number of messages sent by the entity, the less mutual reciprocity. In other words, if the exchange of messages between the owner and the entity is balanced, or if the owner sends more messages to the entity, the owner of the IoT system may determine that the entity is reciprocal. Also, the greater the number of messages the owner has recently sent to the entity, the greater the mutual reciprocity.

). 단계(405)에서 신뢰도 분석 시스템은 소유주 i의 엔티티 j에 대한 신뢰도를 아래의 식을 통하여 계산할 수 있다. In step 306, the reliability analysis system may calculate the confidence for the entity of the owner

). In step 405, the reliability analysis system may calculate the confidence for entity j of owner i through the following equation.

). In step 307, the reliability analysis system may calculate a threshold value for the trustworthiness of the owner

).

In step 308, the reliability analysis system may compare the reliability of the threshold with the reliability of the entity (406). The reliability analysis system may allow (309, 407) access to the IoT system for an entity if the threshold is less than the reliability of the entity and if the threshold is greater than the reliability of the entity, Access may be disabled (310, 412).

In step 311, the reliability analysis system may inform the owner of this decision by allowing access to the IoT system for the entity, and may inform the owner of this decision by disabling access to the IoT system for the entity (408, 413).

In step 312, the reliability analysis system may determine 409 whether the determination of whether to allow or deny access of the IoT system to the entity is correct. At this time, the thread value of the corresponding entity may be changed depending on whether the decision of the reliability analysis system and the decision of the owner are the same. The reliability analysis system may update the internal data if the decision is correct (313, 410). The reliability analysis system allows the access but the owner can not access it, and the thread of the entity may increase (411). The reliability analysis system may adjust the threshold and update the internal data if the decision is incorrect (314, 415, 416).

FIG. 5 is an example of applying the reliability analysis system according to an embodiment.

The company often had access to the employees of the company, and the employees of the company were uncomfortable due to security problems. To solve this problem, let's assume that an in-house Smart Entrance is established.

Reliability analysis system can simplify access procedure by calculating mutual reciprocity and calculating reliability based on reputation of partner company and reputation of partner company, mailing interaction between company employee and partner company through constructed Smart Entrance.

In the reliability analysis system, the reliability value of attendee 1 is 0.7 and the threshold value of organizer 1 is 0.6 in Email network 1. Therefore, the reliability value of attendee 3 in email network 2 is 0.4 and the threshold value of organizer 2 is 0.5 Access may not be possible.

In e-mail network2, the reliability value of attendee 2 is 0.9, and the reliability value of attendee 2 is high because attendee 2 has been allowed to access in e-mail network 1, so reputation of attendee 2 has increased. It can be judged that the reliability for attendee 2 increases. However, even if the reputation of attendee 2 is high, reliability can be lowered if there is no mutual reciprocity between organizer 2 and attendee 2.

The apparatus described above may be implemented as a hardware component, a software component, and / or a combination of hardware components and software components. For example, the apparatus and components described in the embodiments may be implemented within a computer system, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA) , A programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For ease of understanding, the processing apparatus may be described as being used singly, but those skilled in the art will recognize that the processing apparatus may have a plurality of processing elements and / As shown in FIG. For example, the processing unit may comprise a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as a parallel processor.

The software may include a computer program, code, instructions, or a combination of one or more of the foregoing, and may be configured to configure the processing device to operate as desired or to process it collectively or collectively Device can be commanded. The software and / or data may be in the form of any type of machine, component, physical device, virtual equipment, computer storage media, or device , Or may be embodyed temporarily. The software may be distributed over a networked computer system and stored or executed in a distributed manner. The software and data may be stored on one or more computer readable recording media.

The method according to an embodiment may be implemented in the form of a program command that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions to be recorded on the medium may be those specially designed and configured for the embodiments or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

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. For example, it is to be understood that the techniques described may be performed in a different order than the described methods, and / or that components of the described systems, structures, devices, circuits, Lt; / RTI > or equivalents, even if it is replaced or replaced.

Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

Claims (13)

In a reliability analysis system,
A collection unit for collecting internal data and external data;
A calculation unit calculating the reputation and mutual reciprocity of the entity using the internal data or the external data, and calculating the reliability of the entity based on the calculated reputation and mutual reciprocity;
A processing unit for comparing the reliability of the calculated entity with a threshold value to determine whether the entity is reliable or not, and notifying the owner of the IoT system of the result; And
An update unit for updating a threshold value for the entity based on the result of the reliability and access permission;
The reliability analysis system comprising: The method according to claim 1,
Wherein,
An internal data collecting unit for collecting internal data based on the number of times that the IoT system is allowed to access, the number of permitted accesses of belonging entity entities, the total access attempted number of the entity,
The reliability analysis system comprising: The method according to claim 1,
Wherein,
Collects external data based on the total number of activities of the owner of the IoT system, the number of times of activity of the owner by entity of the entity, the number of messages the owner has sent to the entity, and the number of messages transmitted by the entity to the owner An external data collecting unit
The reliability analysis system comprising: The method according to claim 1,
The calculation unit may calculate,
A reputation calculation unit for calculating a reputation of an entity to access the IoT system using the internal data and a reputation of an affiliate of the entity;
A reciprocal reciprocity calculation unit for calculating reciprocal reciprocity for entities that want to access the rights of the owner of the IoT system using the external data; And
A reliability calculation unit for calculating reliability of the entity based on the calculated reputation and mutual reciprocity,
The reliability analysis system comprising: The method according to claim 1,
Wherein,
A trust determining unit for comparing the reliability of the calculated entity with a threshold value to determine whether the trusted entity is accessible or not; And
Notifying the owner of the IoT system of the determination of the determined trustworthiness and access permission or not, and a notification and response section
The reliability analysis system comprising: The method according to claim 1,
Wherein,
If the determination as to whether or not the determined trustworthiness and the access permission is wrong is made, the threshold for the entity is updated
Wherein the reliability analysis system comprises: 21. A computer readable medium comprising instructions for a computer system to analyze reliability,
The command includes:
Collecting internal data and external data;
Calculating the reputation and mutual reciprocity of the entity using the internal data or the external data, and calculating reliability of the entity based on the calculated reputation and mutual reciprocity;
Comparing the reliability of the calculated entity with a threshold value to determine whether the entity is trustworthy and whether to allow access, and notifying the owner of the IoT system of the result; And
Updating a threshold for the entity based on the result of the trustworthiness and accessibility
≪ / RTI > wherein the computer system controls the computer system. In the reliability analysis method,
Collecting internal data and external data;
Calculating the reputation and mutual reciprocity of the entity using the internal data or the external data, and calculating reliability of the entity based on the calculated reputation and mutual reciprocity;
Comparing the reliability of the calculated entity with a threshold value to determine whether the entity is trustworthy and whether to allow access, and notifying the owner of the IoT system of the result; And
Updating a threshold for the entity based on the result of the trustworthiness and accessibility
Lt; / RTI > 9. The method of claim 8,
Wherein the collecting of the internal data and external data comprises:
Collecting internal data based on the number of times that the IoT system is allowed to access, the number of permitted accesses of affiliated entity entities, the total access attempted number of the entity, and the total allowed access count of the entity
Lt; / RTI > 9. The method of claim 8,
Wherein the collecting of the internal data and external data comprises:
Collects external data based on the total number of activities of the owner of the IoT system, the number of times of activity of the owner by entity of the entity, the number of messages the owner has sent to the entity, and the number of messages transmitted by the entity to the owner Step
Lt; / RTI > 9. The method of claim 8,
Calculating the reputation and mutual reciprocity of the entity using the internal data or the external data and calculating the reliability of the entity based on the calculated reputation and mutual reciprocity,
The reputation of the entity that wants to access the IoT system and the reputation of the entity belonging to the entity are calculated using the internal data and the mutual reciprocity of entities that want to access the owner's authority of the IoT system using the external data Calculating reliability of the entity based on the calculated reputation and mutual reciprocity
Lt; / RTI > 9. The method of claim 8,
Comparing the reliability of the calculated entity with a threshold to determine whether the entity is trustworthy and whether to allow access, and notifying the owner of the IoT system of the result,
Comparing the reliability of the calculated entity with a threshold value to determine whether or not it is reliable and whether to allow access, notify the owner of the IoT system about the determined reliability and whether to allow the access, Step of receiving feedback
Lt; / RTI > 9. The method of claim 8,
Wherein updating the threshold value for the entity based on the result of the trustworthiness and access permission comprises:
Updating the threshold for the entity if the determined trustworthiness and the determination of whether to grant access are incorrect,
Lt; / RTI >

Images