KR20150032190A - Method and device for managing application data - Google Patents

Abstract

The present invention relates to a method and a device for managing application data. A device (115) may correspond to a physical access controller (115) in a distributed physical access control system (110). The device in a distributed system may include a logic (210) configured to detect a request from an application to access an application dataset, wherein the application dataset corresponds to a distributed dataset and determine whether the application dataset exists in the distributed system (110). The logic (210) may be further configured to generate the application dataset in the distributed system (110), in response to determining that the application dataset does not exist in the distributed system (110), and send, to other devices (115) in the distributed system, a request to join a dataset group that includes devices (115) associated with the application dataset, in response to determining that the application dataset exists in the distributed system (110).

Description

METHOD AND DEVICE FOR MANAGING APPLICATION DATA [0002]

The present invention relates to an access control system, and more particularly to application data management in an access control system.

A distributed system may include components that communicate and coordinate its operations to accomplish a series of tasks. For example, a computer in a distributed system can communicate over a network to perform coordination for algorithm resolution. Implementation of a distributed algorithm may be required to successfully coordinate operations on independent computers simultaneously, such as data and resource management or processing phase synchronization. Various distributed algorithms have been developed to coordinate the components of a distributed system.

An object of the present invention is to manage application data in an access control system.

According to an embodiment of the present invention, a method of managing application data performed by a device in a distributed system includes the step of the device detecting a request by an application accessing an application data set, ; Determining by the device whether the application data set is present in the distributed system; The device generating the application data set in the distributed system in response to determining that the application data set is present in the distributed system data set; And sending, in response to determining that the application data set is present in the distributed system, a request for participation in a data set group including a device associated with the application data set to the other device in the distributed system .

In addition, the step of the device determining if the application data set is present in the distributed system includes accessing an identifier list of the distributed data set in the distributed system data set; And determining whether the list of identifiers of the distributed data set includes an identifier for the requested application data set.

The method according to an embodiment of the present invention may further include adding information of the application to the generated application data set in response to generating the application data set.

Further, a method according to an embodiment of the present invention includes receiving a notification from another device in the distributed system that the device is added to the data set group; Receiving the application data set from the other device in the distributed system; And storing the received application data set in the device.

In addition, the received application data set includes a list of the devices that are members of the data set group, the method further comprising: providing the device with a suggestion to the device that is a member of the data set group to add application data to the application data set Transmitting; Obtaining an agreement to add the application data to the application data set in response to sending the suggestion; And adding the application data to the application data set in response to obtaining the agreement.

In addition, the method according to an embodiment of the present invention includes: receiving a request for participation from another device in the distributed system into a data set group of a device related to the generated application data set; Obtaining an agreement on adding the other device to a data set group of the device associated with the generated application data set; And in response to obtaining an agreement to add the other device to a data set group of the device associated with the generated application data set, And the like.

In addition, the step of acquiring an agreement on adding the other device to the data set group of the device related to the generated application data set may include acquiring the agreement of the device related to the created application data set Sending a suggestion for adding the other device to a data set group; And obtaining a quorum of voting for adding the other device to a data set group of the device associated with the generated application data set.

The step of adding the another device to a data set group of a device associated with the generated application data set may include: transmitting the application data set to the another device; And adjusting a quorum required for agreement on the data set group of the device associated with the generated application data set.

The method may further include receiving a change request for application data of the generated application data set from another device in the distributed system; And modifying the application data of the generated application data set in response to obtaining an agreement to change the application data of the generated application data set.

In addition, the method according to an embodiment of the present invention includes: receiving a removal request in a data set group of a device related to the generated application data set from another device in the distributed system; Obtaining an agreement to remove the other device from the data set group of the device associated with the generated application data set; And removing the other device from the data set group of the device associated with the generated application data set in response to obtaining an agreement to remove the other device from the data set group of the device associated with the generated application data set Step < / RTI >

Further, the distributed system includes a distributed physical access control system, and the device and the other device correspond to a physical access control unit.

A device for managing application data according to another embodiment of the present invention detects a request by an application accessing an application data set, wherein the application data set corresponds to a distributed data set; Determine whether the application data set is present in the distributed system; Generate the application data set in the distributed system in response to determining that the application data set is present in the distributed system data set; In response to determining that the application data set is present in the distributed system, sending a join request to a data set group that includes a device associated with the application data set to another device in the distributed system have.

In addition, if the logic determines that the application data set is present in the distributed system, the logic further accesses an identifier list of the distributed data set in the distributed system data set; And determine whether the list of distributed data sets includes an identifier for the requested application data set.

Additionally, the logic may add information of the application to the generated application data set in response to generating the application data set.

Additionally, the logic further receives a notification from another device in the distributed system that the device is being added to the data set group; Receive the application data set from the other device in the distributed system; The received application data set may be stored in the device.

In addition, the received application data set includes a list of the devices that are members of the data set group, and further wherein the logic is configured to provide the device with the application data set as a member of the data set group ; Obtain an agreement to add the application data to the application data set in response to sending the suggestion; In response to obtaining the agreement, the application data may be added to the application data set.

Additionally, the logic further receives a request for participation from another device in the distributed system into a data set group of the device associated with the generated application data set; Obtain an agreement on adding the other device to a data set group of the device associated with the generated application data set; In response to obtaining an agreement on adding the other device to the data set group of the device associated with the generated application data set, adding the other device to the data set group of the device related to the generated application data set can do.

Additionally, the logic further comprises receiving from another device in the distributed system a removal request in the data set group of the device associated with the generated application data set; Obtain an agreement to remove the other device from the data set group of the device associated with the generated application data set; In response to obtaining an agreement to remove the other device from the device data set group associated with the generated application data set, removing the other device from the data set group of the device associated with the generated application data set have.

Further, the distributed system includes a distributed physical access control system, and the device and the other device correspond to a physical access control unit.

A distributed system according to another embodiment of the present invention may include a plurality of physical access control devices, wherein a specific one of the plurality of physical access control devices detects a request by an application accessing an application data set, Wherein the application data set corresponds to a distributed data set; Determine whether the application data set is present in the distributed system; Generate the application data set in the distributed system in response to determining that the application data set is present in the distributed system data set; In response to determining that the application data set is present in the distributed system, sending a join request to a data set group that includes a device associated with the application data set to another device in the distributed system have.

1 is a block diagram illustrating an exemplary environment in accordance with an embodiment of the present invention.
2 is a block diagram illustrating exemplary components of the distributed system unit shown in FIG.
Figs. 3A and 3B are block diagrams illustrating exemplary functional components of the distributed system unit shown in Fig. 1. Fig.
FIG. 4A is a diagram illustrating exemplary information that may be stored in the system data set shown in FIG. 3B.
FIG. 4B is a diagram illustrating exemplary information that may be stored in the application data set shown in FIG. 3B.
5 is a flow diagram illustrating accessing or participating in a data set group of a distributed control system in accordance with one or more embodiments of the present invention.
6 is a flow diagram illustrating adding application data to an application data set of a distributed control system in accordance with one or more embodiments of the present invention.
7 is a flow diagram illustrating processing a request to add a system unit to a data set group associated with an application data set of a distributed control system in accordance with one or more embodiments of the present invention.
8 is a plan view showing an exemplary physical layout of the distributed control system shown in Fig.
9 is a plan view showing an exemplary physical layout of the distributed system shown in FIG.
Figures 10A-10C illustrate scenarios of an exemplary application data set in accordance with one or more embodiments of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Like reference symbols in different drawings designate the same or similar elements.

The distributed control system may include a distributed physical access control system. The physical access control system may include one or more access control units, each access control unit controlling physical access to the area of the facility. For example, the access control unit may obtain a certificate from the user and unlock the door if the user's certificate is authentic. According to another embodiment, the distributed control system may include a distributed building management system, a distributed monitoring system, a distributed security system, and / or other types of distributed control systems.

The distributed control system can perform distributed computing operations using a distributed algorithm. For example, a distributed control system can manage a distributed database. The distributed algorithm may be a consensus-based. The consensus algorithm is used to achieve agreement between nodes in the distributed system before the operation is performed. For example, in one embodiment, in order to update a distributed data set, the nodes in the distributed system must agree to perform the update. The agreement corresponds to a node that agrees with the proposed action (e.g., a change to the distributed database) (e.g., by a quorum). If a quorum for the proposed action is obtained, it can reach agreement. A consensus can be reached if the majority of the nodes agree with the proposed operation. Upon requesting a majority of nodes agreeing to a change, for example, when two conflicting proposed changes are considered, at least one node receives two proposed changes, first selects a proposed change to be received, . According to another embodiment, the node may select one of the proposed changes and use other criteria in agreeing (rather than according to a previously received proposal change).

The distributed data set may be used by at least some of the nodes in the distributed system. For example, an application may use an application distributed data set, and an application may be installed in at least some of the nodes in the distributed system. At least some of the nodes using the specific application data set are referred to as data set groups hereinafter. Implementations presented in the present invention are directed to managing distributed data sets associated with a particular application. A device in the distributed system may detect a request from an application accessing an application data set corresponding to a distributed data set associated with the application and determine whether the application data set is present in the distributed system. If there is no application data set, an application data set can be created. If an application data set is present, a request to join a data set group containing a device associated with the application data set may be sent to another device in the distributed system.

Another device in the distributed system may receive a request from a requesting device to be added to the data set group and generate a suggestion to add the requesting device to the data set group. Other devices in the data set group can agree on the proposal, and when the agreement is reached, the request device can be added to the data set group. Thus, the requesting device may suggest receiving an application data set associated with a data set group, and / or adding an application to the application data set associated with the data set group and / or other changes to be reflected.

1 is a block diagram illustrating an exemplary environment in which the systems and / or methods described below are implemented. The environment 100 may include a distributed control system 100 (e.g., a distributed physical access control system), a network 120, and a management device 130, as shown in FIG.

Distributed control system (DCS) 110 includes system units 115-A to 115-N (collectively referred to as "system units 115" and individually referred to as "system units 115" And a distributed computing system including the distributed computing system. The system unit 115 may be implemented as an embedded system. In some implementations, the system unit 115 may include a physical access control device. For example, the system unit 115 may include an access controller that controls access to a secure area, such as a room or a group of rooms. The system unit 115 may receive a certificate (e.g., an access card certificate) via the reader device and determine whether the certificate is authentic and authorized to access the secure area. If so, the access controller may issue a command to unlock the door or perform other actions to allow access to the secure area. According to another embodiment, the system unit 115 may comprise a different kind of secure device, such as a monitoring device, a device that controls the operation of the machine. According to another embodiment, the system unit 115 may include another type of embedded system.

The distributed control system 110 may include one or more distributed data sets. A distributed data set includes a data set associated with a plurality of devices. According to one embodiment, multiple devices communicate and coordinate with each other for changes to the data set. In some implementations, the distributed data set is maintained by each device associated with the distributed data set, and changes to the distributed data set are applied by each device if there is a change agreement by the devices. According to another embodiment, not all devices associated with a distributed data set store actual distributed data sets.

According to some embodiments, an agreement is reached to effect a change to a distributed data set (e. G., A consensus-based distributed database). According to another embodiment, changes to the distributed data set may be performed without consensus. The distributed data set may be associated with all system units 115 or with a subset of system units 115. The system unit 115 may propose a change of the distributed data set based on the agreement. Once a change is accepted by the quorum of the system units 115 associated with the distributed data set, an agreement can be reached and the change propagated to the distributed data set of each associated system unit 115. Thus, if the quorum of the associated system units 115 agrees with the change, it is possible to reach an agreement on the change of the distributed data set. A quorum may correspond to a smallest majority of the associated system units 115. Thus, if the distributed data set is associated with N system units 115, then N / 2 + 1 associated system units 115 will agree with the change and N is even, or (N-1) / 2 + If the associated system units 115 agree to a change and N is odd, then a quorum is satisfied. As a minimum number of quorums is required to satisfy the quorum, at least one system unit 115 receives two proposals when two conflicting proposals are considered and is able to select one of the proposals as agreed upon. According to some embodiments, the system unit 115 selects the first received proposal. According to another embodiment, the proposal may be selected using different criteria.

According to some embodiments, all system units 115 associated with a distributed data set may store a distributed data set. For example, a distributed data set may include access rules, which may be valid for all system units associated with a distributed data set. Thus, according to one embodiment, the distributed control system 110 may correspond to a decentralized system other than a central control device such as a server device, depending on the result of one or more distributed data sets. According to another embodiment, the distributed control system 110 may include both a decentralized system and a central control device (such as a server device). According to one embodiment, changes to the distributed data set may be set by any system unit 115 and propagated to other system units 115 associated with the distributed data set. Also, as errors at a single point can be prevented, the distributed control system 110 can exhibit robustness to device errors. For example, if a particular system unit 115 malfunctions, other system units 115 may continue to operate without loss of data (or with minimal data loss). In addition, the distributed control system 110 may be dynamically changed. For example, an application may be added at any time, and a new data set may be stored in the system units 115 as needed. According to another embodiment, not all system units 115 associated with a distributed data set store a distributed data set.

The distributed data system 110 may also include non-distributed data sets. By way of example, the first system unit 115 may include a local data set that is not included anywhere else in the other system units 115. As another example, the first system unit 115 may comprise a local data set replicated in a second system unit 115 in a non-distributed form, such as mirroring. As another example, the first system unit 115 may comprise a first version of the local data set and the second system unit 115 may comprise a second version of the local data set, 1 system unit 115 stores the first version of the local data set and the second system unit 115 stores the second version of the local data set. As another example, the first system unit 115 may extract a first set of local data from a set of distributed data and the second system unit 115 may extract a second set of local data from the set of distributed data, Wherein the first local data set is different from the second local data set.

The network 120 allows the system units 115 to communicate with each other and the management device 130 to communicate with specific system units 115. The network 120 may include one or more circuit-switched networks and / or a packet-switched network. For example, the network 120 may be a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a public switched telephone network (PSTN) ), An ad hoc network, an intranet, the Internet, a fiber optic based network, a wireless network, and / or a combination of such networks or other networks.

The management device 130 may allow the administrator to establish a distributed control system 110 by connecting to a particular system unit 115 and to change the settings of the distributed control system 110 and receive information from the distributed control system 110 And / or to manage the distributed control system 110. The management device 130 may include any device configured for communication with one or more system units 115. For example, the management device 130 may be a portable communication device (e.g., a cell phone, a smart phone, a phablet device, a Global Positioning System (GPS) device, and / or other types of wireless devices); A personal computer or workstation; Server device; laptop; Tablet, or other type of portable computer; And / or certain types of devices with communication capabilities.

Although FIG. 1 illustrates exemplary components of environment 100, according to another embodiment, environment 100 may include fewer components, different components, differently arranged components, or different components, Additional components may be included. Additionally or alternatively, a device included in the environment 100 (or group of devices) may perform the specified function to be performed by one or more other devices within the environment 100. For example, according to some embodiments, the system units 115 include input and / or output devices (e.g., keyboard / keypad and display, touch screen, etc.) .

FIG. 2 is a block diagram illustrating exemplary components of the system unit 115. FIG. As shown in FIG. 2, the system unit 115 may include a controller 210 and one or more peripheral devices 230. The controller 210 may control the operation of the system unit 115 and may communicate with other system units 115, communicate with the management device 130 and / or control the peripheral device 230. The controller 210 may include a bus 212, a processor 214, a memory 216, a network interface 218, a peripheral interface 220 and a housing 222.

The bus 212 may include a path that enables communication between the components of the controller 210. The processor 214 may be any type of single-core processor, a multicore processor, a microprocessor, a latch-based processor, and / or processing logic (or a processor, / RTI > and / or a family of processing logic). According to another embodiment, the processor 214 may include an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and / or other types of integrated circuit or processing logic.

The memory 216 may include any type of dynamic storage device that stores information and / or instructions executed by the processor 214 and / or a non-volatile storage device that stores information used by the processor 214 have. For example, the memory 216 may be a random access memory (RAM) or other dynamic storage device, a ROM (Read-Only Memory) device or other type of static storage device, , A Content Addressable Memory), a magnetic and / or optical storage memory device and its corresponding drive (e.g., hard disk drive, optical drive, etc.), and / .

The network interface 218 may be any type of communication device such as a wired communication link (e.g., a conductive wire, a twisted pair cable, a coaxial cable, a transmission line, a fiber optic cable and / (E.g., a wireless transceiver) that allows the controller 210 to communicate with other devices and / or systems through a combination of wireless and wired communication links, such as radio frequency (RF), infrared, and / or visual optics, For example, a transmitter and / or a receiver. The network interface 218 may include a transmitter that converts the baseband signal to a radio frequency signal and / or a receiver that converts the radio frequency signal to a baseband signal. The network interface 218 may be coupled with the antenna to transmit and receive radio frequency signals.

Network interface 218 may include input and / or output ports for performing data transmission to other devices, logical components comprised of input and / or output systems, and / or other input and output components. For example, the network interface 218 may include a network interface card (e.g., an Ethernet card) for wired communication and / or a wireless network interface (e.g., WiFi) card for wireless communication. The network interface 218 includes a universal serial bus (USB) port for communicating over a cable to convert data from one form to another, and includes a Bluetooth wireless interface, a Radio-Frequency Identification (RFID) , A near-field communications (NFC) interface, and / or other types of interfaces.

The peripheral interface 220 may be configured to communicate with one or more peripheral devices 230. For example, the peripheral interface 220 may include one or more logic components (not shown) configured as input and / or output ports, input and / or output systems and / or other input and output components for performing data transmission to the peripheral device 230 . ≪ / RTI > By way of example, the peripheral interface 220 may be connected to a peripheral device (not shown) using a Serial Peripheral Interface Bus protocol, such as the Wiegand protocol and / or the RS-485 protocol and / 230). As another example, the peripheral interface 220 may use a different kind of protocol. According to one embodiment, the network interface 218 may also operate as a peripheral interface that couples the peripheral device 230 to the controller 210.

The housing 222 may receive the components of the controller 210 and may protect the components of the controller 210 from the environment. According to one embodiment, the housing 222 may include one or more peripheral devices 230. According to another embodiment, the housing 222 may include a management device 130. [ The housing 222 may include a plurality of system units 115 and / or one system unit 115 for the controller 210 and / or other system units 115 in a system comprised of a plurality of controllers 210. [ And / or the boundaries of the controller 210.

As described below, the controller 210 may perform certain operations associated with application data sets and / or data set groups in the distributed system. The controller 210 can perform this operation through hardwired logic of the ASIC. The controller 210 may also (or alternatively) perform such operations in response to the processor 214 executing software instructions recorded on a computer readable medium, such as the memory 216. Computer readable media include non-transitory memory devices. The memory device may be implemented in a single physical memory device or in a plurality of expanded physical memory devices. The software instructions may be read from another computer readable medium or other device and input into memory 216. [ The processor 214 may perform the processing described in this document by the software instructions recorded in the memory 216. [ Thus, the implementations described herein are not limited to any particular combination of hardware circuitry and software.

The peripheral device 230 may include one or more devices that provide information to the controller 210, are controlled by the controller 210, and / or communicate with the controller 210. For example, the peripheral device 230 may include a reader device 240, a locking device 250, a sensor 260, and / or an actuator 270. Figure 2 illustrates one reader device 240, one locking device 9250, one sensor 260 and one actuator 270, but this is illustrative only, and in fact the peripheral device 230 may include multiple A reader device 240, a plurality of locking devices 250, a plurality of sensors 260, and / or a plurality of actuators 270. According to some embodiments, the peripheral device 230 may not include one or more devices as shown in FIG. Additionally or alternatively, the peripheral device 230 may include other types of secure devices not shown in FIG.

The reader device 240 may include a device that reads the certificate from the user and provides the certificate to the controller 210. For example, the reader device 240 may include a keypad or keyboard configured to receive alphanumeric Personal Identification Numbers (PINs) from a user. A card reader configured to read a card storing codes in a magnetic strip or other type of storage device such as an RFID tag; A fingerprint reader configured to read a fingerprint of a user; A iris reader configured to read a user's iris; A microphone and a voice signature identifier configured to record a user's voice signature; NFC reader; And / or other types of reader devices. Reader device 240 includes some type of secure device that provides a certificate, and may include one or more sensor devices, such as sensor 260, described below. For example, the reader device 240 may include a camera used for face recognition and / or a microphone used for speech recognition.

The locking device 250 may include locking means controlled by the controller 210. The locking device 250 may lock other types of access to doors, windows, Heating, Ventilating, and Air Conditioning (HVAC), and / or entrances to the security area (e.g., preventing doors from opening or closing can do). For example, the locking device 250 may include electromagnetic locking means; A mechanical locking means provided with a motor controlled by the controller 210; Electromechanical locking means; And / or other types of locking means. The locking device 250 may also perform locking / unlocking operations on the machine, the vehicle, the elevator, and / or the electrical device.

The sensor 260 may comprise a sensor device. By way of example, the sensor 260 may include a door sensor that senses whether the door is open or closed; Visible light monitoring camera; Infrared monitoring cameras, thermal sensing monitoring cameras, and / or other types of monitoring devices; Alarm sensors such as motion sensors, thermal sensors, pressure sensors, and / or other types of alarm sensors; An audio recording device (e. G., A microphone); A tamper sensor, such as a position sensor, provided within the system unit 115; And / or a "redemption request" button located within a security zone associated with the system unit 115; And / or other types of sensor devices.

Actuator 270 may include an actuator device. By way of example, the actuator 270 may control the lighting device. As another example, the actuator 270 may include a stolen alarm operator; A speaker for reproducing a message or generating an alarm signal; A display device; A motor for moving the sensor 260 (e.g., for field of view of a camera or other monitoring device); A door, window, motor for opening / closing another entrance associated with the HVAC and / or security area; A motor for protecting the locking device 250 in a locked or unlocked position; A fire extinguishing device; And / or other types of actuator devices.

2 shows an exemplary component of the system unit 115, the system unit 115, as an alternative embodiment, may have fewer components, other components, additional components, or different arrangements RTI ID = 0.0 > components. ≪ / RTI > Additionally or alternatively, a component (or group of components) of the system unit 115 may perform specified tasks or tasks to be performed by one or more other components of the system unit 115. For example, according to some embodiments, peripheral interface 220 may correspond to a network interface. As another example, in some embodiments, the peripheral device 230 may be connected to the controller 210 via the network interface 218 rather than the peripheral interface 220.

Also, while the distributed control system 110 includes physical access to the distributed control system, as another example, the system may be controlled in a manner other than physical access. On the other hand, the distributed control system 110 may provide a certain type of physical access control system (e.g., within an operating environment), such as a control system that opens and / or closes a door or controls physical access to a building or facility, . The distributed control system 110 may also control a fan (e.g., start or stop operation), initiate an alarm of the building management system (e.g., failure authentication, success authentication, etc.) And a system for controlling the robot arm in an automated system.

FIGS. 3A and 3B are block diagrams illustrating exemplary functional components of the system unit 115. FIG. The functional components of the system unit 115 may be implemented through circuitry, for example, by wiring one or more ASICs. Additionally or alternatively, the functional components of the system unit 115 may be implemented by the processor 214 executing instructions of the memory 216. FIG. 3A shows a functional hierarchy of the system unit 115. FIG. 3A, the system unit 115 may include an application programming interface (API) layer 310, an application layer 320, a distribution layer 340, and a storage layer 350 have.

The API layer 310 includes APIs configured to communicate with, for example, the management device 310. For example, when an administrator logs in to the system unit 115 using the management device 130, the API layer 310 can communicate with the management device 130 to authenticate the administrator. As another example, the API layer 310 may communicate with the management device 130 to change the settings of the system unit 115. The API layer 310 may receive data from the management device 130 and provide the data to the distribution layer 340 and / or the storage layer 350. The API layer 310 may also communicate with the management device 130 to install applications in the application layer 320. API layer 310 may be configured to handle different manager types. For example, the API layer 310 may include a web service manager, a Linux administrator, an API that handles ONVIF (Open Network Video Interface Forum), and / or other types of APIs.

The application layer 320 may include one or more applications installed in the system unit 115. 3B shows an application according to an embodiment. 3B, the application layer 320 may include an access control logic application 322, a door control application 324, a reader control application 326, an event processing application 328, and / or an application 332 .

The access control logic application 322 may determine whether access is allowed based on the received certificate and stored access rules. The door control application 324 may control one or more doors and / or associated locking devices 250. For example, the door control application 324 may determine whether the door is open, closed, and / or locked and not locked, and one or more devices may operate to open, close, and / or lock or unlock the door. The reader control application 326 may control one or more reader devices 240 and may obtain and process certificates received from one or more reader devices 240. [ The event processing application 328 may be recorded or created by the system unit 115 or may store a log of events recorded by other system units 115. [ The event processing application 328 may be configured to cause events recorded or generated locally to be stored in all (or at least a portion of) the system units 115 to be stored in the distributed system event logs by other system units 115 on the distributed control system 110. [ As shown in Fig. Thus, logged events can be extracted from any system unit 115 associated with the system event log. The schedule processing application 330 may manage one or more schedules associated with the system unit 115. For example, the access rules for a particular group of users may be changed based on a specific time of day.

The application 332 may correspond to a specific application installed in the application layer 320 of the system unit 115, which uses a distributed data set. For example, the application 332 may be an application associated with a specific sensor 260, such as a camera controlling an application; Applications associated with specific actuators 270, such as door motor applications; An application that performs information processing such as a number counting application; An application that provides a platform for a third party application that controls the peripheral device 230; An application for establishing communication with a remote device over a network; And / or other types of applications.

Other types of applications (not shown in FIG. 3B) may be included in the application layer 320. By way of example, an alarm application may generate reports and / or alarms to send reports and / or alarms to the management device 130 (and / or other designated devices) and / or one or more other system units 115 have. As another example, task-specific control applications may process events related to the system unit 115, such as door open events, sensor events, actuator events, and / or other types of events.

The distribution layer 340 may manage one or more distribution data sets associated with the system units 115. For example, the distribution layer 340 may maintain a secure connection (e.g., Transport Layer Security (TLS) connection) with other system units 115 via the network 120. In addition, the distribution layer 340 may connect the controllers 210 of the peer-to-peer network for distribution of the data set. The distribution layer 340 may implement an agreement on the modification of a particular aggregation-based distributed data set using a protocol (e.g., the PAXOS protocol). By way of example, the distribution layer 340 may send a suggestion for a change to other system units 115 associated with the distributed data set, and may receive a quorum for the change from the other system units 115. As another example, the distribution layer 340 may agree to a proposal received from another system unit 115. [ As another example, the distribution layer 340 may receive a notification indicating that an agreement for the change has been made without consent to the change. When a consent notice for the change is received, the distribution layer 340 may apply the changes to the distributed data set in the storage layer 350. The distribution layer 340 may receive the request from the application 332 that wants to access the application data set and may determine the system data set to determine if the application data set is present. If an application data set is present, the distribution layer 340 may request participation in the data set group of the device associated with the application data set by sending a request to the other system units 115 in the distributed control system 110 . If an application data set does not exist, then the distribution layer 340 may generate an application data set on behalf of the application 332.

The storage layer 350 may store one or more data sets associated with the unit 115. The storage layer stored in the storage layer 350 may correspond to a local data set or correspond to a distributed data set. The local data set may store information related (and / or relevant) to the particular unit 115 storing the local data set. The distributed data set may store information associated with other system units 115 associated with the distributed data set.

Information according to an embodiment that may be included in the storage layer 350 is shown in FIG. 3B, the storage layer 350 includes configuration data 352, certificate data 354, access rule data 356, a system data set 358, and an application data set 360 . The configuration data 352 may be stored in a specific system unit 115 such as a hardware configuration of the controller 210, a peripheral device 230 connected to the controller 210, an application installed in the application layer 320, and / ) Can be stored. The certificate data 354 may store a certificate associated with the system unit 115. Access rules 356 may store access rules associated with system unit 115.

System data set 358 may correspond to a set of distributed data associated with system units 115 (e.g., all system units 115). Thus, the system data set 358 may be stored in each system unit 115 in the distributed control system 110. Information according to an embodiment that may be stored in the system data set 358 will be described later with reference to FIG. 4A.

Application data set 360 may correspond to a distributed data set associated with a particular application, such as application 332. [ Information according to an embodiment that can be stored in the application data set 360 will be described later with reference to FIG. 4B.

3A and 3B illustrate exemplary functional components of the system unit 115, but according to another embodiment, the system unit 115 may include fewer functional components than the one shown in FIGS. 3A and 3B, A functional component, a functional component, a functional component, a functional component, or a functional component. For example, one application 332 and one application data set 360 are shown in FIG. 3B, but this is exemplary and in practice the application layer 320 may include multiple applications 332 , The storage layer 350 may include a plurality of application data sets 360. Additionally, any of the components of the system unit 115 (or any group of components) may perform the specified function to be performed by one or more other functional components included in the system unit 115.

FIG. 4A is a diagram of exemplary information that may be stored in the system data set 358. FIG. As shown in FIG. 4A, the system data set 358 may include a system unit list 410 and one or more distribution data set identifier (ID) fields 420. The system unit list 410 may store a list of system units 115 including the distributed control system 110.

The distributed data set identifier field 420 may store information for identifying a distributed data set present in the distributed control system 110. [ The distributed data set field 420 may include one or more distributed data set entries. Each distributed data set identifier field 420 may include one or more identifiers associated with a particular distributed data set of the distributed control system 110. The one or more identifiers may include a name of a data set group; A description of the identifier, name, and / or application associated with the distributed data set; Metadata describing the contents of the data set; And / or other information that may be used to identify a particular distributed data set. The distributed data set identifier may be used by the distribution layer 340 to identify a particular application when the application 332 requests access to the application data set.

Although FIG. 4A illustrates an exemplary component that may be stored in the system data set 358, according to another embodiment, the system data set 358 may include fewer components than the one shown in FIG. 4A, , ≪ / RTI > otherwise disposed components, or additional components.

4B is a drawing of exemplary information that may be stored in the application data set 360. FIG. 4B, the application data set 360 includes a distributed data set identifier field 430, one or more system unit fields 440-A through 440-N, a quorum field 450 and an application data field 460 ). The distributed data set identifier 430 may correspond to the distributed data set identifier stored in the distributed data set identifier field 420 of the system data set 358,

The system unit field 440 may store information that allows the system units 115 in the data set group associated with the application data set 360 to be identified. The quorum field 450 allows verification of the number of consent tables required by the system units 115 in the data set group in voting for proposed changes to the application data set 360 to arrive at an agreement Information can be stored. The application data field 640 may store application data associated with the application data set 360.

Although FIG. 4B illustrates exemplary components that may be stored in the application data set 360, according to another embodiment, the application data set 360 may include fewer functional components than the one shown in FIG. 4B, Components, other functional components, or additional functional components.

Figure 5 is a flow diagram of joining into a data set group or accessing an application data set in a distributed control system in accordance with one or more embodiments of the present invention. According to some embodiments, the process of FIG. 5 may be performed by the controller 210. According to another embodiment, some or all of the process of FIG. 5 may be performed by another device or group of devices that are separate from and / or included in the controller 210.

The process of FIG. 5 may include joining a data set group or connecting to an application data set (block 510). For example, the administrator can use the management device 130 to log in to the specific system unit 115 and install the application 332 in the corresponding system unit 115. The application 332 may be configured to store data in a distributed data set, and / or to extract data in a distributed data set. Thus, after the application 332 is installed, the application 332 may send a request to the distribution layer 340 to access the distributed data set associated with the application 332. A determination may be made whether the application data set identifier is present in the system data set (block 515). As described above, the system data set 358 includes a distributed data set identifier field 420 that stores an identifier of a distributed data set included in the distributed control system 110. The distribution layer 340 may connect to the distributed data set identifier field 420 to determine if the identifier for the application 332 is listed in the distributed data set identifier field 420.

If it is determined that the application data set identifier is not present in the system data set (block 515 -No), an application data set entry may be created and distributed in the system data set (block 520). Since the system data set 358 is a distributed data set in the distributed control system 110, the system unit 115 is configured to perform a change to the system data set 358, To obtain an agreement to perform the change of the identifier field 420. The controller 210 of the system unit 115 may send a suggestion for the change to the other system units 115 in the distributed control system 110 so that the other system units 115 An application data set entry may be added to the distributed data set identifier field 420 of the system data set 358. [

An application data set may be created (block 530) and application data may be added to the application data set (block 540). For example, the distribution layer 340 may generate an application data set 360 in the storage layer 350, receive application data from the application 332, add the received application data to the application data set 360 can do. It should also be noted that the particular system unit 115 that created the application data set entry in the distributed data set identifier field 420 of the system data set 358 is the first system unit 115 associated with the application data set, The distribution layer 340 may set the quorum requirement to 1 for the data set group associated with the application data set 360 if the application layer 115 does not belong to the data set group associated with the application data set. Thus, it is not necessary to acquire a consent table from the other system units 115 to add application data to the application data set 360.

Again, block 515 illustrates that if the application data set identifier is determined to be present in the system data set (block 515 - Yes), the distribution control system 110 may request to add to the data set group associated with the application data set, A request may be sent to other system units 115 in the network (block 550). Since the distributed data set identifier field 420 may not contain information indicating which system units 115 are associated with a particular distributed data set, It may be necessary to send another request to the other system units 115 (e.g., all other system units 115) to the data set group.

A notification that the requesting system unit has been added to the distributed data set may be received from another system unit (block 560). For example, in the distributed control system 110, one or more other system units 115 in the data set group associated with the application data set may process the request to add the requesting system unit 115 to the data set group . The processing of adding the system unit 115 to an existing data set group will be described later with reference to FIG. Once the requesting system unit 115 is added to the data set group, the particular system unit 115 that has added the requesting system unit 115 can send a notification to the requesting system unit 115. [

In response to receiving the notification that it has been added to the data set group, an application data set is received from another system unit (block 570) and the received application data set may be added to the storage layer (block 580). For example, the distribution layer 340 may receive an application data set from another system unit 115 and store the received application data set in the storage layer 350. The application data set may be associated with a data set group and may include a list of system units 115 associated with a quorum requirement in performing operations on the application data set.

6 is a flow diagram of a change in application data present in an application data set of a distributed control system in accordance with one or more embodiments of the present invention. According to some embodiments, some or all of the process of FIG. 6 may be performed by another device or group of devices that are separate from, and / or included in, the controller 210.

The process of FIG. 6 may include detecting a change request for application data in the application data set (block 610). As an illustrative example, application 332 may be generated by application data such as data reception from a particular peripheral device 230, command recording sent to a specific peripheral device 230, result recording of an operation, and / or application 332 It is possible to generate other kinds of application data. As another example, application 332 may choose to modify, update, delete, and / or modify application data residing in application data set 360. The application 332 may provide application data changes to the distribution layer 340.

Other system units in the data set group associated with the application data set may be identified (block 620) and a suggestion may be sent to other system units identified to modify the application data of the application data set (block 630) . For example, the distribution layer 340 may access the application data set 360, determine whether the system units 115 have been identified in the system unit field 440, Units 115 to change the application data.

An agreement may be obtained to modify the application data in the application data set (block 640), and the proposed change in response to the obtained agreement may be applied to the application data set (block 650). The system unit 115 may receive a quorum consent table indicating that the proposed change is agreed to. For example, if ten system units 115 are associated with a data set group, then the requesting system unit 115 may be associated with six associated system units 115 to modify the application data of the application data set 360. For example, ≪ / RTI > Once six consent tables are received, an agreement on the proposed changes is reached, and the proposed changes are performed. In response to obtaining an agreement on the proposed changes, the distribution layer 340 may be configured to update the application data in the application data set 360 in the add, change, update, delete, and / Can be performed.

7 is a flow diagram illustrating processing a request to add a system unit to a data set group associated with an application data set of a distributed control system in accordance with one or more embodiments of the present invention. According to some embodiments, the process of FIG. 7 may be performed by the controller 210. According to another embodiment, some or all of the process of FIG. 7 may be performed by another device or group of devices that are separate from and / or included in the controller 210.

The process of FIG. 7 may include receiving a request (block 710) from another system unit to be added to the data set group associated with the application data set. For example, the controller 210 of the system unit 115 may receive a request from a requesting system unit that is to be added as a data set group associated with the application data set. The system unit 115 may receive the request and may determine if the request is appropriate if the system unit 115 is associated with a data set group. For example, the system unit 115 may determine whether the application data set 360 associated with the application 332 identified by the request exists in the storage layer 350. [

Other system units in the data set group may be identified (block 720) and a suggestion may be sent to other system units identified to add the request system unit to the data set group (block 730). For example, the distribution layer 340 may access the application data set 360, determine whether the system units 115 have been identified in the system unit field 440, The proposal may be sent to the system units 115 identified in the system unit field 440.

An agreement may be obtained to add the requesting system unit to the data set group (block 740), and the requesting system unit may be added to the data set group in response to the obtained agreement (block 750). Also, the quorum requirement for the data set group may be adjusted (block 760). The system unit 115 may receive a quorum consent table stating that it agrees with the proposed changes to add the requesting system unit 115. For example, if ten system units 115 are in a data set group, then the proposal system unit 115 may send the request system unit 115 to the data set group from the associated six system units 115 You may need to receive a consent form. Once six consensus tables have been received, an agreement on the proposed addition is reached, and the requesting system unit 115 is allowed to be added to the data set group associated with the application data set 360. For example, the distribution layer 340 may generate a system unit field 440 for the requesting system unit 115 of the application data set 360. The distribution layer 340 may also adjust the quorum requirement in the quorum field 450 of the application data set 360. For example, if ten system units 110 were associated with a dataset group, and the current eleven system units 115 are associated with a dataset group, the quorum requirement of six may not change. However, if another system unit 115 is added to the data set group to become a total of 12 system units, the quorum requirement may be changed from 6 to 7.

According to some embodiments, a deletion process may be performed if a particular system unit 115 requests deletion in a data set group associated with an application data set. For example, the application 332 may be uninstalled at a particular system unit 115. As part of the removal process, the application 332 may request that the particular system unit 115 be deleted from the application data set 360. Thus, the particular system unit 115 may send suggestions for the other system units 115 in the data set group associated with the application data set 360 to be deleted. Once a consensus on the proposal is obtained, the particular system unit 115 may be deleted from the data set group, and the application data set 360 may be removed from the storage layer 350.

According to some embodiments, the installation of application 332 may be automated. Therefore, rather than using the management device 130 by the administrator to install the application 332 in each system unit 115 once at a time, the application 332 is installed in one system unit 115, An instruction may be installed in the system unit 115. [ The installation command may be included as part of the application 332 or as a separate program, application and / or script file. The install command may include one or more criteria for installing the application 332 and if the particular system unit 115 meets one or more criteria an instruction to install the application 332 may be sent to another May be transmitted to the system units (115). Thus, if one or more criteria are met by the particular system unit 115, the corresponding system unit 115 may install the application 332. [ After the application 332 is installed in the corresponding system unit 115, the corresponding system unit 115 associates with the application 332 and adds the process of Figure 5 to be added to the data set group associated with the application data set 360 Can be performed. One or more criteria for installing an application 332 in a particular system unit 115 may include hardware settings associated with that system unit 115; A specific type of peripheral device connected to the system unit 115; A location type associated with the system unit 115; An event type recorded by the corresponding system unit 115; A specific application installed in the corresponding system unit 115; And / or other types of criteria.

8 is a plan view showing an exemplary physical layout 800 of the system unit 115. As shown in FIG. 8, the physical layout 800 includes a wall 810, a door 820, a controller 210, a reader device 240, a lock device 250, a sensor 260, and an actuator 270, . ≪ / RTI >

The wall 810 accommodates a secure area 830 such as a room of a building. The door 820 provides access to the secure area 830 to the user. According to one embodiment, the controller 210 is installed inside the secure area 830. According to another embodiment, the controller 210 may be installed outside the secure area 830. The reader device 240 is installed outside the security area 830 and the locking device 250 is installed in the wall 810 and the door 820 inside the security area 440. According to such an example, the sensor 260 is a monitoring device mounted outside of the secure area 830. Actuator 270 includes a motor used to control the field of view of the monitoring device according to this example.

When the user enters a certificate into the reader device 240 (for example, by entering a PIN number, access card scanning, iris scanning, etc.), the controller 210 uses the certificate to verify the identity of the user, The rule table can be searched to determine whether or not the user can allow access based on the user's identity and access rules. If the controller 210 determines that access is allowed, the controller 210 operates the locking device 250 to unlock the door 820 to allow access to the security area 830 by the user.

8 illustrates exemplary components of a physical layout 800, it is appreciated that, according to other embodiments, the physical layout 800 may include a small number of components, other components, additional components, But may include otherwise disposed components. Additionally or alternatively, any component (or group of components) of the physical layout 800 may perform one or more operations specified to be performed by one or more other components included in the physical layout 800 .

9 is a top view of an exemplary physical layout 900 of the distributed control system 110. In FIG. As shown in FIG. 9, the physical layout 900 may include a building 910 comprised of rooms 920-A through 920-F. A local network 930, such as an Ethernet network, may be interconnected between the system units 115-A through 115F. According to this example, the system unit 115-A controls the two doors toward the room 920-A; The system unit 115-B controls the external door to face the room 920-B; The system unit 115-C controls one door from the room 920-B to the room 920-C and the system unit 115-D controls one door from the room 920- To face room 920-D; The system unit 115-E controls one door from the room 920-D to the room 920-E; The system unit 115-F controls the external door to face the room 920-F.

According to this example, the system units 115-A through 115-F do not include a central control device (e.g., a server) and may include one or more distributed data sets. For example, the system units 115-A through 115-F may store a distributed authentication table, a distributed access rules table, and / or a distributed event log. Suppose an administrator logs in to the system unit 115-A using the management device 130, adds a user and adds a certificate associated with the user. This added certificate can be distributed to other system units 115 that control the door of the room that the user wishes to access. For example, if the system unit 115-B fails, the data collected by the system unit 115-B by the distributed event log included in the other system units may continue to be valid.

Although FIG. 9 illustrates exemplary components of a physical layout 900, according to another embodiment, the physical layout 900 may include a small number of components, other components, additional components, or otherwise And may include deployed components. For example, according to another embodiment, a central control device (e.g., a server) may be used with one or more distributed data sets. Additionally or alternatively, one or more components of the physical layout 900 may perform one or more operations specified to be performed by one or more other components included in the physical layout 900.

Figures 10A-10C illustrate scenarios of an exemplary application data set in accordance with one or more embodiments of the present invention. For example, suppose that a room counting application is needed in room 920-C of FIG. In order to count the number of people in the room (920-C), it is necessary to count the number of people going to and from the room (920-C) through any door. Thus, the number counting application must be installed in the controller 210 of the system units 115-A, 115-C and 115-D.

10A shows a signal flow scenario 1000 after the counting application 1010-A is installed in the system unit 115-A. After the counting application 1010-A is installed in the system unit 115-A, the counting application 1010-A sends the distributed application data set associated with the counting application 1010-A via the distribution layer 340- (Signal 1012). The distribution layer 340-A may verify that the application data set entry for the counting application 1010 is not present in the system data set 358. [ The distribution layer 340-A may then distribute further suggestions of entries for the counting application data set in the system data set 358 (signal 1014). After an agreement on the proposed change is obtained, the distribution layer 340-A may create a new entry in the system data set 358 to generate the counting application data set identifier entry 1017. [ An update to the system data set 358 may be distributed to the other system units 115-B to 115-F through the accepted proposal after reaching consensus. The distribution layer 340-A may perform the generation of the counting application data set 1020-A in the storage layer 350 (signal 1018). The counting application 1010-A is then enabled to use the counting application data set 1020-A via the distribution layer 340-A.

Figure 10B shows a signal flow scenario 1030 after the counting application 1010-C has been installed in the system unit 115-C. After the counting application 1010-C is installed in the system unit 115-C, the counting application 1010-C is connected to the distributed application data set associated with the counting application 1010-C via the distribution layer 340- (Signal 1031). Distribution layer 340-C may determine that application data set entry 1017 is present in system data set 358. [ The system unit 115-C then sends a request (signal 1032-A) to the system unit 115-A to be added to the data set group associated with the counting application data set 1020, B (signal 1032-B), sends it to system unit 115-D (signal 1032-D), sends it to system unit 115-E (signal 1032-E) -F) (signal 1032-F). Only system unit 115-A responds to the request because only system unit 115-A is included in the data set group associated with counting application data set 1020. [

Any proposed changes to the counting application data set 1020 are automatically received in agreement because the system unit 115-A is the only system unit in the data set associated with the counting application data set 1020. [ Thus, the system unit 115-A will have an agreement to accept the request and add the system unit 115-C to the data set group associated with the counting application data set 1020. [ The system unit 115-A adds a system unit 115-C to the data set group associated with the counting application data set 1020-A (signal 1034), and the system unit 115- (Signal 1036) to the system unit 115-C that it has been added to the system unit 115-C. The system unit 115-C receives the counting application data set 1020 (signal 1038) and the system unit 115-C stores the received counting application data set 1020 in the storage layer 350 .

Thereafter, the counting application 1010-C may generate application data. For example, if a person leaves room 920-C through the door associated with system unit 115-C, the sensor device associated with system unit 115-C senses the person leaving. The counting application 1010-C may propose to add the generated application data to the application data set 1020-C via the distribution layer 340-C (signal 1040). Since the only other system unit in the data set group associated with the counting application data set 1020 is the system unit 115-A, a proposal for data addition is sent to the system unit 115-A (signal 1042). The system unit 115-A can agree to the change so that the system unit 115-C can obtain agreement (by automatically agreeing with the changes proposed by itself) by satisfying the required quorum number 2 . As a result, the proposed change becomes applicable to the system unit 115-A and the system unit 115-C (signal 1044).

Figure 10C shows the signal flow scenario 1050 after the counting application 1010-D is installed in the system unit 115-D. After the counting application 1010-D is installed in the system unit 115-D, the counting application 1010-D is connected to the counting application 1010-D via the distribution layer 340- (Signal 1051). The distribution layer 340-D may determine that the counting application data set identifier entry 1017 is present in the system data set 358. [ The system unit 115-C then sends (signal 1052-A) a request to the system unit 115-A to be added to the data set group associated with the counting application data set 1020, B (signal 1052-B), transmits it to the system unit 115-C (signal 1052-C), transmits it to the system unit 115-E (signal 1052-E) -F) (signal 1052-F). Only system units 115-A and 115-C respond to the request because only system units 115-A and 115-C are associated with counting application data set 1020. [

The system unit 115-A and the system unit 115-C send the system unit 115-D to the counting application data set < RTI ID = 0.0 > 1020 < / RTI > Assume that before the system unit 115-C, the system unit 115-A receives the request and operates according to the received request. The system unit 115-A will send (signal 1054) to the system unit 115-C and send to itself a suggestion to add the system unit 115-D. The system unit 115-C will send a suggestion to add the system unit 115-D to the system unit 115-A and transmit it to itself (not shown in Fig. 10C). Subsequent proposals from the system unit 115-C are rejected because the proposal sent by the system unit 115-A has been received first. Thus, the system unit 115-C agrees with the proposal from the system unit 115-A, rejects its own proposal (signal 1056), and the system unit 115- And rejects the proposal from the system unit 115-C (not shown in Fig. 10C). The system unit 115-A is brought to an agreement on the proposal and the system unit 115-D is added to the data set group associated with the counting application data set 1020 (signal 1058) The changes are distributed according to the results.

The system unit 115-A sends a notification to the system unit 115-D that the system unit 115-D has been added to the data set group associated with the counting application data set 1020 (signal 1060) And provides application data set 1020 to system unit 115-D (signal 1062). The distribution layer 340-D may store the received counting application data set 1020 in the storage layer 350 (signal 1064). In this case, the quorum requirement for the data set group associated with the counting application data set 1020 need not be changed.

As described above, various embodiments have been described with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto without departing from the scope of the invention as set forth in the claims set forth below, and additional embodiments may be implemented. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.

For example, although a series of blocks is illustrated in Figures 5-7, the order of blocks and / or signals may be modified in accordance with another embodiment. Also, non-dependent blocks and / or signal flow may be performed in parallel.

It will be apparent that the system and / or method described above may be implemented in various forms of software, firmware, and hardware, such as the forms shown in the figures. The actual software codes or specialized control hardware used to implement such systems and methods are not limited to the embodiments. Thus, the operations and behaviors of systems and methods are described without reference to particular software codes-software and control hardware may be understood as being designed to implement the systems and methods based on what has been described herein.

In addition, certain portions of the above may be implemented as components that perform one or more functions. The components used herein may include hardware such as a processor, ASIC or FPGA, or a combination of hardware and software (e.g., processor running software).

As used herein, terms such as " comprises "and" comprising " mean the presence of stated features, integers, steps or components but may include the presence or absence of one or more other features, integers, It does not deny the existence or addition of the group.

Any of the elements, operations, or commands used herein may not be understood to be significant or essential to the embodiment unless explicitly described as such. Also, as used herein, "one" may be understood to include more than one item. Also, "based on" can be understood to mean "based on at least a portion" unless otherwise stated.

Claims (15)

A method performed by a device in a distributed system,
The device detecting a request by an application accessing an application data set, the application data set corresponding to a distributed data set;
Determining by the device whether an identifier for the application data set is listed in the distributed system data set of the distributed system;
Generating, by the device, an entry of an identifier for the application data set of the distributed system data set in response to determining that an identifier for the application data set is not listed in the distributed system data set; And
In response to determining that an identifier for the application data set is present in the distributed system data set, transmits a request for participation in a data set group including a device associated with the application data set to the other device The method comprising the steps of: The method according to claim 1,
Wherein the step of determining whether an identifier for the application data set is listed in the distributed system data set of the distributed system
Accessing an identifier list of distributed data sets in the distributed system data set; And
And determining whether the list of identifiers of the distributed data set includes an identifier for the requested application data set. 3. The method according to claim 1 or 2,
Generating the application data set in a storage layer of the device in response to generating an identifier entry for the application data set of the distributed system data set; And
Further comprising the step of adding information of the application to the generated application data set in response to generating the application data set. 4. The method according to any one of claims 1 to 3,
Receiving a notification from another device in the distributed system that the device is added to the data set group;
Receiving the application data set from the other device in the distributed system; And
And storing the received application data set in the device. 5. The method of claim 4,
Wherein the received application data set includes a list of the devices that are members of the data set group,
Sending a suggestion to the device that is a member of the data set group to add application data to the application data set;
Obtaining an agreement to add the application data to the application data set in response to sending the suggestion;
And adding the application data to the application data set in response to obtaining the agreement. 6. The method according to any one of claims 1 to 5,
Receiving a request for participation from another device in the distributed system into a data set group of a device associated with the generated application data set;
Obtaining an agreement on adding the other device to a data set group of the device associated with the generated application data set; And
In response to obtaining an agreement on adding the other device to the data set group of the device associated with the generated application data set, adding the other device to the data set group of the device related to the generated application data set The method further comprising the steps of: The method according to claim 6,
Obtaining an agreement on adding the other device to a data set group of the device associated with the generated application data set
Transmitting a suggestion to the device associated with the generated application data set to add the other device to a data set group of the device associated with the generated application data set; And
And obtaining a quorum of voting for adding the other device to a data set group of the device associated with the generated application data set. The method according to claim 6,
Wherein the step of adding the other device to a data set group of a device associated with the generated application data set includes:
Transmitting the application data set to the another device; And
And adjusting a quorum required for an agreement on a data set group of devices associated with the generated application data set. 9. The method according to any one of claims 1 to 8,
Wherein the distributed system comprises a distributed physical access control system, the device and the other device managing application data corresponding to a physical access control unit. As a device 115 in the distributed system 110,
Detecting a request by an application accessing an application data set, wherein the application data set corresponds to a distributed data set;
Determine whether an identifier for the application data set is listed in the distributed system data set of the distributed system (110);
Generate an entry of an identifier for the application data set of the distributed system data set in response to determining that an identifier for the application data set is not listed in the distributed system data set;
In response to determining that an identifier for the application data set is present in the distributed system data set, requests a participation in a data set group including a device (115) associated with the application data set to the distributed system To the other device (115), the logic (210). 11. The method of claim 10,
Wherein the logic further generates the application data set in a storage layer of the device in response to generating an entry of an identifier for the application data set of the distributed system data set;
And managing application data that adds information of the application to the generated application data set in response to generating the application data set. The method according to claim 10 or 11,
Wherein the logic further receives a notification from another device in the distributed system that the device is being added to the data set group;
Receive the application data set from the other device in the distributed system;
And managing the application data to store the received application data set in the device. 13. The method of claim 12,
Wherein the received application data set includes a list of the devices that are members of the data set group,
Send a suggestion to the device that is a member of the data set group to add application data to the application data set;
Obtain an agreement to add the application data to the application data set in response to sending the suggestion;
And managing application data that adds the application data to the application data set in response to obtaining the agreement. 14. The method according to any one of claims 10 to 13,
Wherein the logic further receives a request from another device in the distributed system to join a data set group of the device associated with the generated application data set;
Obtain an agreement on adding the other device to a data set group of the device associated with the generated application data set;
In response to obtaining an agreement on adding the other device to the data set group of the device associated with the generated application data set, adding the other device to the data set group of the device related to the generated application data set A device that manages application data. 15. The method according to any one of claims 10 to 14,
Wherein the distributed system comprises a distributed physical access control system, wherein the device and the other device manage application data corresponding to a physical access control unit.

Images