METHOD FOR PROCESSING CONFIGURATION DATA OF A MULTIPLE ENTITIES, WORK AND DEVICES INTERACTING THEREW, AS WELL AS COMPUTER PROGRAM PRODUCT AND SIGNAL SEQUENCE

DE502021010071D1Active Publication Date: 2026-04-09GEZE GMBH
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
DE · DE
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-11-29
Publication Date
2026-04-09

AI Technical Summary

Technical Problem

Automated systems, such as automatic door and window systems, require time-consuming and expensive reconfiguration when control modules are replaced or systems are upgraded, leading to inefficiencies and potential misconfigurations.

Method used

A method utilizing a database with general configuration data and association data to create distinct profiles, allowing efficient and reliable configuration by sharing common data across different entities, reducing redundancies and enabling seamless updates.

Benefits of technology

Facilitates fast, error-free configuration and reconfiguration of systems by identifying similarities and differences in profiles, ensuring safe and reliable operation with minimal data volume and resource usage.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader
Need to check novelty before this filing date? Find Prior Art

Description

Title of the invention

[0001] Methods for processing configuration data of a multitude of entities, interacting methods and devices, as well as computer program product and signal sequence field of technology

[0002] The present invention relates to a method for processing configuration data of a plurality of entities, a method that can interact with it, devices configured to execute the methods, a computer program product and a signal sequence. State of the art

[0003] Automated systems, especially automatic door and window systems, typically offer a wide range of parameters for adjusting their function. However, reconfiguring such a system is time-consuming and expensive, for example, if its control module is replaced or the system is replaced with a different model and the settings change in the process.

[0004] US9470947B2 discloses a distributed control system for a plurality of windows, including electrochromic windows. Summary of the invention

[0005] It is therefore an object of the present invention to overcome the described disadvantages of the prior art and in particular to provide means by which the operation of an automatic system throughout its entire life cycle can be made cost-effective and, above all, safe and reliable.

[0006] The problem is solved by the invention according to a first aspect by providing a method for processing configuration data of a plurality of entities, wherein the method comprises: Providing at least one database comprising: a plurality of general configuration data and a plurality of general association data, wherein the individual general association data each describe relationships between two or more general configuration data and thereby define groups of general association data as distinct general configuration profiles, each with at least pairwise related general configuration data, wherein distinct general configuration profiles have at least partially distinct general configuration data; receiving at least one identifier that makes at least one distinguished configuration profile identifiable;Processing at least configuration data and / or association data related to the distinguished configuration profile, and generating a control signal based on at least one result of the processing;wherein the processing of the configuration or association data comprises receiving specific configuration data of a specific entity and storing it in the database together with specific association data, wherein the individual specific association data each describe relationships between one or more general configuration data of the distinguished configuration profile and / or one or more of the received specific configuration data, thereby defining a specific configuration profile that includes at least the distinguished configuration profile and the received specific configuration data related to one or more of the general configuration data of the distinguished profile; wherein the control signal is provided to at least one receiver, namely, sent to it;where the entities include and / or represent automatic door systems, automatic gate systems, automatic window systems and / or automatic lighting systems.

[0007] The invention is thus based on the surprising finding that a common basis of general configuration data enables a particularly simple and reliable configuration and reconfiguration of entities, such as automatic door and window systems, of different types, models, etc.

[0008] This allows different general configuration profiles to be created for different requirements based on shared general configuration data. This is achieved by using general association data to relate the relevant general configuration data for each profile. Therefore, the general configuration data shared by different general configuration profiles only needs to be entered and stored once in the database.

[0009] This avoids redundancies in general configuration data. The reduced data volume allows the process to be carried out very efficiently. This also enables the management and / or provision of general configuration data for a large number of entity types.

[0010] For example, the method can be used to manage and / or provide more than 2, more than 5, more than 10, more than 30, more than 50, more than 100, more than 300, more than 500, more than 1,000 or even more than 3,000 general configuration profiles.

[0011] Since different general configuration profiles are based on the same collection of general configuration data, similarities and differences between them can be easily and reliably identified. When a new general configuration profile is selected for an entity—for example, when updating an entity's control module to a new version or when changing the entity's model—the differing configuration data between the two general configuration profiles can be handled, while the remaining configuration data remains unchanged. This eliminates the need to create correspondence lists for the configuration data of each pair of different general configuration profiles. A complicated and error-prone transfer of configuration data is thus also rendered obsolete.

[0012] Thus, when the general configuration profile is changed, for example when updating the control unit of an entity to a new version, or when changing the model of the entity, all still relevant configuration data can remain unchanged, and only the configuration data that differs between the two general configuration profiles needs to be handled.

[0013] This not only makes the configuration process faster and therefore more efficient, but also reliably prevents misconfigurations and the associated need for troubleshooting. This ensures the safe and reliable operation of the entity.

[0014] The configuration data of each configuration profile can be hierarchically structured and relative to each other by means of association data and / or the assignment of configuration data to different groups. This allows a configuration profile to be represented, for example, as a tree structure. This can also be the case for a general configuration profile.

[0015] For example, each configuration profile can have a top-level element in its hierarchy, a so-called root element. Starting from this root element, all other configuration data associated with the respective configuration profile can be found in the database. It is then particularly easy to select a configuration profile, such as a general configuration profile, for an entity by selecting the configuration profile via a predefined or definable root element.

[0016] In one embodiment, the general configuration data of each general configuration profile can be found by means of at least one general configuration data element, in particular a root element, that is present in the general configuration profile in question.

[0017] General configuration data may include, for example, parameters with which an entity can be configured, allowed values ​​or value ranges from which values ​​for setting such parameters can be chosen, default values ​​for such parameters, and / or error and warning messages that may occur when configuring such parameters.

[0018] In one embodiment, several general configuration profiles are defined in the database, preferably more than 2, more than 5, more than 10, more than 30, more than 50, more than 100, more than 300, more than 500, more than 1,000, or more than 3,000, or can be defined. In one embodiment, an identifier is a general configuration data point.

[0019] In one embodiment, the general configuration data includes data from two or more general groups. In another embodiment, any two of the multiple general configuration profiles defined in the database have at least partially different general configuration data.

[0020] A general configuration profile can thus provide all the relevant settings for a specific entity type. For example, an input form can be created based on the general configuration profile, through which the data necessary for the relevant settings can be requested. The entity can then be configured based on this data.

[0021] The excellent configuration profile can, for example, represent any configuration profile stored in or defined in the database.

[0022] The control signal allows information regarding the data situation in the database to be provided. This control signal can be effectively used to influence other technical systems. Thus, the proposed method enables a technical system to be influenced depending on specific data conditions. This allows the method to be seamlessly integrated into an existing infrastructure, making it particularly versatile.

[0023] In one embodiment, the control signal is provided to a receiver, in particular sent to it. The receiver of the control signal can be the same entity that executes the method, and / or a different one.

[0024] In one embodiment, the control signal comprises an analog signal and / or a digital signal.

[0025] The control signal is therefore preferably designed in such a way that data and thus information can be communicated to other participants, such as other modules, and / or transmitted via the Internet.

[0026] In one embodiment, each general configuration datum is related to at least one other configuration datum.

[0027] In one embodiment, for each association data, particularly a general association data, the type of relationship described by it between the configuration data can be selected from the group of relationships comprising: 1:1, 1:N, and M:N relationships. This also means that preferably different association data can describe different relationship types.

[0028] A relationship or association between two or more dates can mean that one date can be found in the database using the other date.

[0029] Preferably, the entities involved are all of the same type (for example, all in the form of automatic door systems) or the entities involved are all or partly of a different type.

[0030] In one embodiment, an automatic door system includes or represents an automatic sliding door, an automatic revolving door and / or an automatic carousel door.

[0031] In one embodiment, an automatic lighting system includes or represents an automatic skylight system.

[0032] In one embodiment, the method is computer-implemented.

[0033] In one embodiment, the method is executed by at least one server and / or by a cloud system. Alternatively or additionally, the method can be executed by an embedded system and / or by an operating system.

[0034] The proposed method therefore allows for the management of different settings. These can, for example, relate to settings that differ across product models, variants, and versions. The settings can include parameters that can or may be set, default values, permissible values ​​or value ranges for these parameters, possible error and warning messages, as well as the values ​​actually set for the parameters. Furthermore, compatibility information regarding firmware versions can also be maintained.

[0035] All these product variant properties of the possible entity types can thus be maintained and stored centrally in an "asset variant" database. This allows the different settings across entities to be described, implemented, and tracked uniformly. This makes the automatic processing of information very simple and efficient. For example, this enables the comparison of settings (e.g., parameters and values), their transfer between different products and entity variants, and their transfer between the same entity in different versions. Furthermore, errors can be described uniformly.

[0036] This information can be provided to recipients, be it the entity to be configured itself, or a client, such as a smartphone, that configures the entity. The precise entity, and thus the relevant configuration profile, can be identified based on defined or definable characteristics of the entity's plant control system and thus provided as an identifier.

[0037] A local copy of the respective configuration profile can also be stored in a local cache on the recipient. This ensures that the most up-to-date version is maintained even without a connection to a backend. When changes or new entries are made, the local version can then be updated, especially as soon as a connection can be re-established.

[0038] This eliminates the need for this information to be stored locally in user systems or provided by a plant controller. As a result, the most up-to-date and relevant settings for an entity are always available. This is particularly useful when new control software is introduced, as this often involves describing partially new data. For example, new parameters can be set, or different values ​​or value ranges can be permitted. By ensuring that the current configuration data is always available, reliable and secure operation of the entities is guaranteed.

[0039] There is no longer any active effort required to update service software. The configuration profiles provide all the current information. Even new types of entities can easily be supplied with configuration profiles. Centralized data maintenance is simple and allows for a high-quality database with a single source of truth, which improves quality.

[0040] The proposed method is therefore particularly well suited for use in connection with entities in the form of automatic door systems, for example revolving doors, swing doors and / or sliding doors, automatic gate systems, automatic window systems and / or automatic lighting systems.

[0041] In a preferred embodiment, it may be provided that (i) the processing of the data takes place after an evaluation of a control signal and a determination of a first value of the control signal and / or by means of a first module which is preferably selected and / or executed upon determination of the first value of the control signal, and / or (ii) the control signal has a state of the result of the data processing.

[0042] It turns out that entity-specific configuration profiles can be created and processed particularly easily by relating general configuration profiles with specific configuration data.

[0043] For this to work, it suffices that specific configuration data of a specific entity is available, for example, received, and that this data is related to general configuration data of a recorded configuration profile using specific association data. This allows all or some general configuration data of the distinguished configuration profile to be associated with specific configuration data valid for a specific entity.

[0044] For example, the excellent configuration profile in this case can represent a general or specific configuration profile.

[0045] Then, a general configuration profile that can be used for multiple entities of roughly the same type can be associated with specific configuration data of a specific entity of that type, thereby obtaining a specific configuration profile that applies only to that specific entity.

[0046] For example, a parameter represented by a general configuration data (such as the "rotational speed" of a revolving door) can be assigned a value (such as "5 RPM") for a specific entity, also represented by a specific configuration data. Other specific entities can then assign this general configuration data a value chosen individually and potentially differently for themselves using corresponding specific configuration data. This allows for the creation of multiple specific configuration profiles, all of which can also use the same general configuration profile.

[0047] This makes it particularly easy and efficient to centrally store the individual settings of each entity using the proposed method. Despite this, the additional data volume is minimal, as a specific configuration profile only contains the specific configuration data and the necessary specific association data. This allows the general configuration data to be used multiple times: in various general configuration profiles and in various specific configuration profiles, each of which is partially based on the same general configuration profiles.

[0048] A specific configuration profile can thus provide all relevant settings and values ​​for a particular entity. Based on this, the configuration of the specific entity can be carried out completely or partially. Optionally, no user input or other interaction is required. Therefore, the configuration can also be performed automatically.

[0049] This method allows, for example, an entity to be provided with a complete configuration. This is very useful, for instance, to enable the recovery of configuration data after data loss or the replacement of a control module.

[0050] In one embodiment, several specific configuration profiles are defined in the database, preferably more than 2, more than 5, more than 10, more than 30, more than 50, more than 100, more than 300, more than 500, more than 1,000, or more than 3,000, or can be defined. In one embodiment, an identifier is a specific configuration data point.

[0051] In one embodiment, the configuration data of each specific configuration profile can be found by means of at least one configuration data element, in particular a root element, that is present in the specific configuration profile in question.

[0052] A specific configuration profile can contain specific configuration data, specific association data, and data exhibited by related general configuration profiles.

[0053] In one embodiment, the method involves receiving and / or evaluating the control signal. Depending on its value, further actions can then be taken.

[0054] The control signal allows for precise monitoring and control of when specific data processing occurs. This is a particularly efficient way to make the process controllable from the outside. As a result, the proposed method can be easily integrated into existing systems, making it universally applicable.

[0055] In one embodiment, the control signal comprises an analog signal, a digital signal, the result of a selection decision, the result of an evaluation of a flag that can be assigned different values, and / or the result of an evaluation of a date that can be assigned different values.

[0056] For example, in one embodiment, the control signal can indicate a detected data loss by a specific value, and the provision of specific configuration profiles can then be triggered.

[0057] In one embodiment, each specific configuration data point of a specific entity is associated with at least one general configuration data point. Optionally, at least some of these specific configuration data points are associated with the same specific configuration data point of the specific entity.

[0058] In one embodiment, at least one of the specific configuration data of a specific entity is associated with all other specific configuration data of that specific entity. This makes all specific configuration data belonging to a specific entity findable. Optionally, this single specific configuration data is also associated with at least one general configuration data.

[0059] This means that both a general configuration profile and the specific configuration data of a specific entity can be found via a specific configuration date, and thus a specific configuration profile can be found overall.

[0060] In one embodiment, several specific configuration profiles are defined in the database. In another embodiment, the database also contains a plurality of specific configuration data. In another embodiment, an identifier is a specific configuration data.

[0061] If an identifier makes a specific configuration profile identifiable, then a general configuration profile can also be identified through it.

[0062] Thanks to its modular design, a tailored and therefore targeted measure can be applied to different values ​​of the control signal. In particular, the modular design proves to be especially effective in flexibly expanding or reducing the process. New measures can be easily implemented by simply integrating a corresponding module into the process, which can then be selected and executed based on a specific value of the control signal. Even a very fine-grained differentiation between individual measures is thus easily and efficiently achievable.

[0063] Furthermore, particularly high efficiency is possible in electronic data processing, especially when the process is implemented using computers, because the processing system's resources are used sparingly. This is because, in this case, it is not necessary to load and store all conceivable modules in memory at the outset. Instead, system resources for a module only need to be reserved and used when and to the extent that a module is selected and utilized, for example, based on a corresponding value of the control signal.

[0064] A "module" within the meaning of the present invention can be implemented, for example, in software, in hardware, or a combination of both. A "module" within the meaning of the present invention can alternatively or additionally comprise a memory, a processor, a receiving device, a transmitting device, or any combination thereof. A "module" within the meaning of the present invention can alternatively or additionally provide and / or make available everything it comprises, such as, in particular, all necessary resources, for example, in the form of software and / or hardware resources, for the process. A "module" within the meaning of the present invention can alternatively or additionally represent and / or comprise a purely logical or actual grouping of instructions within a program or a process flow.A "module" within the meaning of the present invention may alternatively or additionally be and / or comprise a class, a function, a file and / or a program library that is selectable, callable, executable, loadable into memory and / or permanently or temporarily retainable in memory.

[0065] It is preferred that each available module is independently configured. However, in other preferred embodiments, two or more modules can also be configured within or comprised of a common module.

[0066] In one embodiment, the first module is selected or executed at least once. That is, at this first point in time, the configuration data is received and stored in the database.

[0067] In one embodiment, different values ​​of the control signal are detected at different times. Optionally, at least partially different identifiers are received in each instance. These can make at least partially different configuration profiles identifiable.

[0068] In a preferred embodiment, it can be provided that the general association data (i) each first general configuration date of a first general group is related to at least one, preferably several, second general configuration date of a second general group, and / or (ii) each second general configuration date of the second general group is related to at least one, preferably several, third general configuration date of a third general group, preferably every second general configuration data of the second general group is related to several third general configuration data of several third general groups, in particular every second general configuration data of the second general group is related to at least one, preferably several, first third general configuration data of a first third general group, to at least one, preferably several, second third general configuration data of a second third general group and / or to at least one, preferably several, third third general configuration data of a third third general group, and / or by the specific association data (i) each first specific configuration date of a first specific group is related to at least one, preferably exactly one or more, first general configuration date of the first general group, and / or (ii) each second specific configuration date of a second specific group is related to at least one, preferably exactly one or more, second general configuration date of the second general group, to at least one, preferably exactly one or more, first specific configuration date of the first specific group and / or to at least one, preferably exactly one or more, third, in particular first third, general configuration date of the third general group.

[0069] It is particularly efficient when the configuration data belongs to different groups. This makes it especially easy to define a hierarchical structure of the data exhibited by a general or specific configuration profile and to represent their dependencies. Each hierarchical structure can contain general configuration data, specific configuration data, or a combination of both.

[0070] In one embodiment, the general configuration data is divided or can be divided into two or more general groups. In another embodiment, the specific configuration data is divided or can be divided into two or more specific groups.

[0071] In one embodiment, the individual general association data describe relationships between two or more general configuration data of at least two groups.

[0072] In one embodiment, the individual specific association data describe relationships between at least two specific configuration data and / or between at least one general configuration data and at least one specific configuration data.

[0073] In one embodiment, the entity types available for the general configuration profiles are each grouped as the first general configuration data in the database. For example, there can be different types of entities, such as models, variants, versions, etc. For example, an entity of model A in variant X and version 1 is one type, and an entity of model A in variant X and version 2 is another type.

[0074] In one embodiment, the parameters available for the general configuration profiles are each grouped as a second general configuration data entry in the database. For example, there can be different parameter entities, such as rotational speed, travel speed, etc.

[0075] In one embodiment, the permissible values ​​or value ranges available for the general configuration profiles, or their parameters, are grouped as the first third general configuration data in the database.

[0076] In one embodiment, the standard values ​​available for the general configuration profiles, or their parameters, are grouped as second, third, and so on in the database.

[0077] In one embodiment, the error and warning messages available for the general configuration profiles are each grouped as the third general configuration data in the database.

[0078] In one embodiment, identifiers of the specific entities are grouped as the first specific configuration data in the database. Each identifier can then be used to select a distinguished configuration profile, in particular in the form of a specific or general configuration profile.

[0079] In one embodiment, the values ​​chosen for a specific entity for individual general configuration data, in particular second general configuration data, are each grouped as second specific configuration data in the database.

[0080] In one embodiment, by establishing a relationship between a first general and at least a second general configuration datum, certain parameters that can be configured for a particular entity type within a general configuration profile can be assigned to that entity type.

[0081] In one embodiment, by establishing a relationship between a second general and at least one first third general configuration datum, a specific permissible value or range of values ​​can be assigned to a specific parameter, from which values ​​for this parameter can be set within a general configuration profile.

[0082] In one embodiment, by establishing a relationship between a second general and at least a second third general configuration data point, a specific default value, which is specified for that parameter within a general configuration profile, can be assigned to a specific parameter.

[0083] In one embodiment, by establishing a relationship between a second general and at least a third general configuration data point, an error message that can be issued for a specific parameter within a general configuration profile can be assigned to that parameter.

[0084] In one embodiment, by establishing a relationship between a first specific and at least one first general configuration data point, a specific entity within a specific configuration profile can be assigned a particular type. This first general configuration data point can represent a root element within a general configuration profile. This allows for easy definition of the specific configuration profile. All further general and specific configuration data points of the specific configuration profile can be determined via the first specific configuration data point.

[0085] In one embodiment, by establishing a relationship between a second specific and a second general configuration date and the first specific configuration date, a specific value (defined by the second specific configuration date) can be assigned within a specific configuration profile to a particular parameter (defined by a second general configuration date) that is available for configuration by the specific entity (defined by the first specific configuration date). This makes it possible to assign unique values ​​to a particular, identical parameter to many different specific entities.

[0086] For example, by relating a second specific configuration data point to a third general configuration data point, a specific entity can be assigned a different range of values, such as a smaller or larger one, than is provided for by a corresponding, distinguished general configuration profile.

[0087] In one embodiment, alternatively or additionally, a fourth set of general configuration data can be provided, and in particular, each fourth set of general configuration data can be related to at least one, preferably several, first set of general configuration data. This allows additional features, which are managed separately from the second set of general configuration data, to be related to the data of the first set of general data. This facilitates efficient data management. For example, fourth set of general configuration data can contain or display error messages that are the same for every type of entity. This additional category of data can thus save memory resources.

[0088] In one embodiment, values ​​such as "active" and / or "inactive" can be related to third general configuration data and / or fourth general configuration data.

[0089] In a preferred embodiment, the processing of the configuration or association data may include retrieving the configuration data of the distinguished configuration profile from the database, preferably (i) the retrieved configuration data includes at least general configuration data, in particular of the second general group and / or the third general group, in particular of the first third, second third and / or third third general group, and / or specific configuration data, in particular of the second specific group; (ii) at least the retrieved configuration data is structured within a data structure that is at least partially based on or represented by the association data that associates the retrieved configuration data with each other; (iii) this processing of the data takes place after an evaluation of the control signal and a determination of a second value of the control signal and / or by means of a second module that is selected and / or executed, preferably based on the determination of the second value of the control signal.and / or (iv) the control signal contains the data structure and / or the retrieved configuration data.

[0090] This method reliably enables the provision of general or specific configuration profiles based on an identifier, allowing them to be made available to a particular type of entity or a specific entity. For example, the identifier corresponds to a root element of the general configuration profile to be selected.

[0091] In one embodiment, the identifier corresponds to a general and / or specific configuration data.

[0092] For example, the excellent configuration profile in this case can represent a general or specific configuration profile.

[0093] The use of a data structure allows for the efficient provision of information for further processing of this data, in addition to the raw data itself. Different types of data can be identified using the data structure. For example, parameters (e.g., "rotational speed") and their values ​​(e.g., "5 rpm") can be assigned to each other and / or presented in a distinguishable manner. This enables a technical system receiving the data structure to operate effectively based on it. Furthermore, the data structure allows for the compact transmission of all information, thus requiring minimal system resources.

[0094] If the control signal contains the configuration data, a technical system receiving the control signal can obtain the configuration data particularly easily and reliably.

[0095] The advantages and options described above regarding control signals and modular design apply here as well. In fact, it is preferable to receive and / or evaluate only a single control signal, so that further actions can be determined based on the value of this single control signal.

[0096] In one embodiment, the second module is selected or executed at at least a second time point. That is, at this second time point, the configuration data is retrieved from the database. Optionally, this second time point occurs before or after the first.

[0097] In a preferred embodiment, the processing of the configuration or association data may include comparing the distinguished configuration profile with another selected configuration profile, and in particular determining at least some of the common and / or different general configuration data of the two configuration profiles. and wherein the control signal is indicative of a result of this comparison, in particular of the similarities or differences between the two configuration profiles, wherein a difference is preferably characterized at least in that the two configuration profiles contain at least partially different second general configuration data and / or if the same second general configuration data is associated with different third general configuration data in the two configuration profiles, wherein preferably this processing of the data takes place after an evaluation of the control signal and a determination of a third value of the control signal and / or is carried out by means of a third module which is selected and / or executed, preferably based on the determination of the third value of the control signal.

[0098] Comparing the two configuration profiles is highly efficient due to the shared database. There is no need to maintain reference lists for the corresponding data of different configuration profiles from different entity types.

[0099] For example, the excellent configuration profile in this case can represent a general or specific configuration profile.

[0100] The advantages and options described above regarding control signals and modular design apply here as well. In fact, it is preferable to receive and / or evaluate only a single control signal, so that further actions can be determined based on the value of this single control signal.

[0101] In one embodiment, the third module is selected or executed at at least a third time point. That is, the comparison is performed at the third time point. Optionally, the third time point is before or after the second time point.

[0102] In a preferred embodiment, it can be provided that the identifier is received from a first source; the specific configuration data is received from the first and / or a second source; the control signal is received from the first, second and / or a third source; and / or the receiver is identical to the first, second and / or third source.

[0103] If the identifier is received from the first source, and the control signal is also provided to it, communication can proceed particularly efficiently. For example, the connection to the first source can be maintained between receiving and sending. This eliminates resource-intensive processes for establishing and terminating a communication link between the participants.

[0104] The problem is solved by the invention according to a second aspect by proposing a device which is configured to carry out a method according to the first aspect of the invention, wherein the device preferably comprises or represents at least one server and / or at least one cloud system.

[0105] This allows the method according to the first aspect of the invention to be carried out particularly simply. For example, the device can be coupled with a specific entity or client, at least temporarily, during the execution of the method. For example, the device and the entity or client can be connected to each other via a radio interface, such as wireless LAN, RFID or Bluetooth, a wired connection, such as LAN or USB, or via the internet, so that both can exchange data.

[0106] Preferably, the device represents or includes a computer, in particular a server, or a computer network. Preferably, the device includes a processor and / or memory. The processor can, for example, be configured to execute the method. The memory can, for example, include at least one database. In one embodiment, the device includes at least one database.

[0107] The problem is solved by the invention according to a third aspect in that a method which interacts with a method according to the first aspect of the invention is: Sending an identifier of at least one configuration profile; receiving the control signal, wherein preferably the received control signal contains the configuration data of an entity as indicated by the configuration profile, and configuring the entity based on the received control signal, in particular based on the configuration data, wherein preferably the control signal is indicative for one or more configuration data and for these configuration data a configuration of the entity is only carried out at least after a received confirmation.

[0108] Preferably, the received control signal contains the configuration data specified by the configuration profile.

[0109] In one embodiment, the method is computer-implemented.

[0110] In one embodiment, the method is executed by at least one client, in particular a smartphone and / or an entity. Alternatively or additionally, the method can be executed by an embedded system and / or an operating system.

[0111] In a preferred embodiment, it may be provided that the configuration data is structured within a data structure which describes or makes describable the relationships between the individual configuration data; the method further comprises: sending configuration data, in particular comprising the specific configuration data of the entity received and stored in the database according to the first aspect of the invention; and / or the method further comprises: configuring the entity based on the received control signal, in particular based on the configuration data, wherein preferably the control signal is indicative for one or more configuration data, and for these configuration data a configuration of the entity is carried out only after at least one confirmation has been received.

[0112] Configuring the entity may involve storing configuration data in a memory within the entity.

[0113] The problem is solved by the invention according to a fourth aspect by proposing a device which is configured to carry out a method according to the third aspect of the invention, wherein the device preferably comprises or represents a part of an entity, such as a control module, and / or a smartphone.

[0114] This allows the method according to the third aspect of the invention to be carried out particularly easily. For example, the device can be coupled with a server and / or the entity, at least temporarily, during the execution of the method. For example, the device and the server or the entity can be connected to each other via a radio interface, such as wireless LAN, RFID or Bluetooth, a wired connection, such as LAN or USB, or via the internet, so that both can exchange data with each other.

[0115] Preferably, the device includes a processor and / or memory. The processor can, for example, be configured to execute the method.

[0116] Optionally, the entity is an automated system, such as an automatic door, gate, window, and / or lighting system. The device can alternatively or additionally include or represent an embedded system.

[0117] The problem is solved by the invention according to a fifth aspect by proposing a computer program product comprising instructions which, when the program is executed by a data processing device, in particular the device according to the second aspect of the invention and / or according to the fourth aspect of the invention, cause it to execute the method according to the first aspect of the invention and / or according to the third aspect of the invention.

[0118] A computer program product can be designed, for example, as a CD, DVD, ROM / RAM, Blu-ray disc, USB storage device, SSD storage device, magnetic hard drive, and / or the like. Alternatively or additionally, a computer program product can also be designed as a file, preferably stored or storable on a computer-readable medium. The file can then be executable, for example, particularly on a data processing device, in order to execute the process.

[0119] Preferably, the method according to the first aspect of the invention is carried out by the device according to the second aspect of the invention and / or the method according to the third aspect of the invention is carried out by the device according to the fourth aspect of the invention.

[0120] The problem is solved by the invention according to a sixth aspect by proposing a sequence of signals representing commands which, when executed on a data processing device, in particular the device according to the second aspect of the invention and / or according to the fourth aspect of the invention, cause the device to execute the method according to the first aspect of the invention and / or according to the third aspect of the invention.

[0121] The signal sequence can be transmitted, for example, via a computer network such as the internet. For instance, the signal sequence can represent the computer program product, particularly as a file downloadable from the computer network.

[0122] Preferably, the method according to the first aspect of the invention is carried out by the device according to the second aspect of the invention and / or the method according to the third aspect of the invention is carried out by the device according to the fourth aspect of the invention. Brief description of the drawings

[0123] Further features and advantages of the invention will become apparent from the following description, in which preferred embodiments of the invention are explained with reference to schematic drawings.

[0124] This shows: Fig. 1 a flowchart of a method according to the first aspect of the invention in a first embodiment; Fig. 2 a device configured to carry out the method according to the first aspect of the invention in the first embodiment; Fig. 3a first general configuration data; Fig. 3b second general configuration data; Fig. 3c third general configuration data; Fig. 4 general association data; Fig. 5 a flowchart of a method according to the first aspect of the invention in a second embodiment; Fig. 6 a flowchart of a method according to the first aspect of the invention in a third embodiment; Fig. 7a first specific configuration data; Fig. 7b second specific configuration data; Fig. 8a specific association data; and Fig. 8b specific association data. Description of the embodiments

[0125] The method according to the first aspect of the invention makes it possible to manage the configuration data of different entities of different types. In this case, the data of three types of entities can be managed: First: An automatic revolving door system, model "T1". For this system, a "rotation speed" parameter can be selected within a range of "1" to "5". Second: An automatic revolving door system, model "T2". For this system, a "rotation speed" parameter can be selected within a range of "1" to "7", and also an "operating mode" parameter, which can be set to "1" or "2", depending on whether the door should rotate continuously or only when a person is detected in the doorway. Third: An automatic window system, model "F1". For this system, an "opening speed" parameter can be selected within a range of "1" to "5".

[0126] Fig. 1 shows a flowchart 100 of a method according to the first aspect of the invention in a first embodiment.

[0127] Fig. 2 Figure 1 shows a device 1 configured as a server according to the second aspect of the invention. The device 1 is configured to carry out the method according to the first aspect of the invention in the first embodiment and includes a database 3.

[0128] Database 3 contains a number of general configuration data sets. These general configuration data sets are all those configuration data sets that are relevant for the different entity types being managed.

[0129] The general configuration data is in the Figures 3a to 3cThe data is displayed in a table. Each general configuration data entry shown in a row has an ID and a value. This means that the respective value of the general configuration data entry can be accessed via the ID.

[0130] Figure 3a This shows the initial general configuration data from database 3. This initial general configuration data represents the type designations of the possible entities, namely the respective model. As described above, these are the three entity types "T1", "T2", and "F1".

[0131] Figure 3bThis shows the second set of general configuration data from database 3. This second set of general configuration data represents the parameters available for the possible entities, which can be configured. As described above, the parameters "rotational speed," "operating mode," and "opening speed" are available for the three possible entity types. Although the rotational speed parameter is relevant for several entities (namely those of type T1 and T2), it only needs to be provided once in database 3.

[0132] Figure 3cThis shows the third general configuration data displayed by database 3. The third general configuration data represents the permissible values ​​or value ranges (Z-values) that may be set for the parameters of the respective entities. As described above, there are a total of three different permissible values ​​or value ranges for the three possible parameters: 1-5 for the parameter "Rotation speed" for door system "T1" and for the parameter "Opening speed" for window system "F1", 1-7 for the parameter "Rotation speed" for door system "T2", and 1 or 2 for the parameter "Operating mode" of door system "T2".

[0133] Although the permissible value range ʺ1-5" is used for both the "rotation speed" parameter of the door system "T1" and the "opening speed" parameter of the window system "F1", it only needs to be provided once in database 3.

[0134] Database 3 also contains a plurality of general association data. Each general association data entry describes relationships between several, in this case three, general configuration data entries.

[0135] The general association data are in the Figure 4 The data is presented in tabular form. Each general association data entry shown in each row describes a relationship between the general configuration data entries represented by their IDs in that row. In this case, a relationship is described between an entity type (first general configuration data entry), a parameter (second general configuration data entry), and a valid value or range of values ​​(third general configuration data entry).

[0136] The first line describes a relationship between the entity type with ID "1", the parameter with ID "1", and the allowed value or value range with ID "1". This is further defined by the respective general configuration data ( Fig. 3a-3c ) this can be resolved into a relationship between the entity type "T1" and the parameter "rotational speed" and the permissible value or value range "1-5".

[0137] Similarly, the second line describes a relationship between the entity type with ID "2" and the parameter with ID "1" and the permissible value or value range with ID "2". This is further defined by the respective general configuration data ( Fig. 3a-3c ) this can be resolved into a relationship between the entity type "T2" and the parameter "rotational speed" and the permissible value or value range "1-7".

[0138] The same can be done for the third and fourth lines, thus obtaining the two remaining parameters and their permissible values ​​or value ranges.

[0139] Thus, for each entity type (T1, T2 and F1), the general association data can be accessed using the respective type_ID ( Fig. 4 ) the parameters available for this entity type, including permissible values ​​or value ranges, are determined by considering the association data that describes a relationship for the corresponding type_ID.

[0140] This allows a general configuration profile to be provided for each entity type.

[0141] Or, put another way, through groups of general association data (row 1 in Fig. 4 , lines 2+3 in Fig. 4 and line 4 in Fig. 4) different general configuration profiles (for T1, T2 and F1) are defined, each with at least pairwise related general configuration data (type, parameter, Z-value), whereby different general configuration profiles have at least partially different general configuration data (because none of the configuration profiles for T1, T2 and F1 has only the same parameters and Z-values).

[0142] The aim here is to put a specific entity of type "T1" into operation. For this purpose, the general configuration profile relevant for this entity type should be provided.

[0143] In section 101, database 3 is provided. As just discussed, database 3 contains different data.

[0144] In 103, an identifier is received that makes a distinguished configuration profile identifiable. This identifier corresponds precisely to the first general configuration data point "T1" and thus makes the general configuration profile relevant for this entity type identifiable as a distinguished configuration profile (so that the data in Fig. 3a the type_ID "1" and the association data in Fig. 4 the general configuration data associated with this ID are determined).

[0145] In section 105, the general configuration data of the general configuration profile for entity type "T1" is retrieved from database 3. This includes general configuration data of the second and third general groups, i.e., the parameters and their respective associated permissible values ​​or value ranges.

[0146] This is done by evaluating a received control signal, during which a second value for the control signal was determined, and within the framework of a second module 5. This second module 5 was selected and executed based on the determined second value.

[0147] In section 107, a control signal is generated that displays the retrieved general configuration data of the distinguished configuration profile. The retrieved general configuration data is the result of the data processing.

[0148] In 109, the control signal is sent to the specific entity or to a client, such as a smartphone, that can communicate with the specific entity, so that the specific entity can be configured with the excellent configuration profile.

[0149] Fig. 5Figure 200 shows a flowchart of a method according to the first aspect of the invention in a second embodiment. The device 1 can alternatively or additionally also implement this embodiment of the method and has the database 3 as described above.

[0150] The aim here is to upgrade a specific entity of type "T1" to an entity of type "T2". To this end, the new general configuration profile for the new entity type should be provided, and differences between the old and new configuration profiles should be identified so that the configuration only needs to be performed for the changed parameters.

[0151] Database 3 is provided in 201. As discussed above, database 3 contains different data.

[0152] In 203, an identifier is received that makes a distinguished configuration profile identifiable. This identifier corresponds precisely to the first general configuration data point "T2" and thus makes the general configuration profile relevant for the new entity type identifiable as a distinguished configuration profile (so that the data in Fig. 3a the type_ID "2" and via the association data in Fig. 4 the general configuration data associated with this ID are determined).

[0153] In section 205, the general configuration data of the general configuration profile for entity type "T2" is retrieved from database 3. This data includes general configuration data for the second and third general groups, i.e., the parameters and their respective associated permissible values ​​or value ranges.

[0154] Furthermore, the general configuration profile for entity type "T1" is retrieved from database 3 as another selected configuration profile, i.e., for the old entity type. A corresponding additional identifier may have been received for this purpose.

[0155] These two profiles are then compared. The differences lie in the existence of different second general configuration data; specifically, the parameter "Operating Mode" is only present in entity type "T2". Furthermore, the same second general configuration data is associated with different third general configuration data. While both entity types have a "Rotational Speed" parameter, they have different permissible value ranges: "1-5" and "1-7", respectively.

[0156] This is done by evaluating a received control signal, during which a second and third value for the control signal were determined, and within the framework of a second and third module. These modules are implemented here as a single, shared module 7, but could also be implemented separately. Module 7 was selected and executed based on the determined second and third values.

[0157] In section 207, a control signal is generated that displays the retrieved general configuration data of the selected configuration profile. The control signal also indicates the differences between the two general configuration profiles.

[0158] In section 209, the control signal is sent to the specific entity or to a client, such as a smartphone, that can communicate with the specific entity, so that the specific entity can be configured with the specified configuration profile, insofar as this differs from the previous profile. Thus, the sent control signal allows the configuration to be performed only for the different parameters, while the same parameters do not need to be reconfigured as long as they remain within the permissible ranges. This is the case here, since only the rotation speed could be configured for entity type "T1", and its permissible value range is even larger for entity type "T2".

[0159] Fig. 6Figure 300 shows a flowchart of a method according to the first aspect of the invention in a third embodiment. The device 1 can alternatively or additionally also implement this embodiment of the method and has the database 3 as described above.

[0160] The specific configuration data of a specific entity of type "T1" is to be stored in database 3 together with the general configuration profile relevant for this type as a specific configuration profile.

[0161] In section 301, database 3 is provided. As just discussed, database 3 contains different data.

[0162] In response 303, an identifier is received that makes a distinguished configuration profile identifiable. This identifier corresponds precisely to the first general configuration data point "T1," thus identifying the general configuration profile relevant to this entity type as a distinguished configuration profile. The identifier could also identify a specific configuration profile for the respective entity, which in turn would allow the identification of the general configuration profile. This can be advantageous, for example, if specific configuration data has already been stored and needs to be updated.

[0163] In 305, the specific configuration data of the specific entity is received and stored in database 3 along with specific association data.

[0164] Two different specific configuration data points are received and stored. Firstly, an entity identifier, representing a serial number of the specific entity and corresponding to a first specific configuration date, is processed. Secondly, the value of the (single) parameter chosen for the specific entity of type "T1" is processed, corresponding to a second specific configuration date.

[0165] Database 3 will then (at the latest) contain a plurality of specific configuration data. The specific configuration data are all those configuration data that are relevant for specific entities.

[0166] The specific configuration data of the specific entity under consideration here are in the Figures 7a to 7bThe data is displayed in a table. Each specific configuration data entry shown in a row has an ID and a value. This means that the respective value of the specific configuration data entry can be accessed via the ID.

[0167] Database 3 then contains (at the latest) a plurality of specific association data. The specific association data each describe relationships between a general configuration data of the distinguished configuration profile and one of the received specific configuration data, or relationships between a general configuration data of the distinguished configuration profile and two of the received specific configuration data.

[0168] The specific association data are in the Figures 8a-8bPresented in tabular form. Each general association data entry displayed per row describes a relationship between the configuration data represented by its ID in the row from the Figs. 3a-3c and Figs. 7a-7b .

[0169] Figure 8a shows 3 specific association data identified by the database, each association data describing a relationship between an entity type (first general configuration data) and an entity identifier (first specific configuration data).

[0170] Figure 8b shows 3 specific association data identified by the database, each association data describing a relationship between an entity identifier (first specific configuration data) and a parameter (second general configuration data) and a value (second specific configuration data).

[0171] Through a specific association date ( Fig. 8a) the specific entity (or its identifier) ​​is identified via the associated entity_ID "1" ( Fig. 7a ) with a specific entity type based on its type_ID "1" ( Fig. 3a ) related. Only the association date exists, which links the entity_ID "1" for the identifier "12345" with the type_ID "1" and thus with the entity type "T1" ( Fig. 3a ) associated.

[0172] Through another specific association date ( Fig. 8b ) the specific entity (or its identifier) ​​is identified via the associated entity_ID "1" ( Fig. 7a ), the parameter with parameter_ID "1" ( Fig. 3b ) and the value "2" ( Fig. 7b ) is associated with it. In other words, for the entity with the identifier "12345", the value "2" is defined for the parameter with parameter_ID "1".

[0173] This defines a specific configuration profile for the specific entity, which includes the distinguished configuration profile and the received initial specific configuration data that is at least partially related to the parameter exhibited by the distinguished configuration profile.

[0174] This is done by evaluating a received control signal, during which a first value for the control signal was determined, and within the framework of a first module 9. This first module 9 was selected and executed based on the determined first value.

[0175] In section 307, a control signal is generated that indicates the state of the data processing result. For example, the state can represent successful data processing.

[0176] In 309, the control signal is sent to the specific entity or to a client, such as a smartphone, that can communicate with the specific entity.

[0177] Subsequently, a method according to the first aspect of the invention in its first embodiment could be used ( Fig. 2 The specific configuration profile, which also contains the specific configuration data of the specific entity, is also provided. For this purpose, the entity identifier "12345" could be received as an identifier in 103, by which the specific configuration profile can be identified.

[0178] It is possible that the individual modules 5, 7, and 9 are selected and executed at different times. For example, the control signal could then have the corresponding values ​​at the respective times. Reference symbol list

[0179] 1 Device 3 Database 5 Module 7 Module 9 Module 100 Flowchart 101 Provisioning a database 103 Receiving an identifier 105 Retrieving configuration data from the database 107 Generating a control signal 109 Sending the control signal 200 Flowchart 201 Provisioning a database 203 Receiving an identifier 205 Retrieving configuration data of two configuration profiles from the database and comparing the data 207 Generating a control signal 209 Sending the control signal 300 Flowchart 301 Provisioning a database 303 Receiving an identifier 305 Receiving specific configuration data and storing it in the database 307 Generating a control signal 309 Sending the control signal

Claims

1. Method for processing configuration data items for a multiplicity of entities, wherein the method comprises: providing (101, 201, 301) at least one database (3) comprising: a plurality of general configuration data items and a plurality of general association data items, wherein the individual general association data items each describe relationships between two or more general configuration data items and as a result groups of general association data items define different general configuration profiles with general configuration data items each related at least in pairs, wherein different general configuration profiles at least partially have different general configuration data items; receiving (103, 203, 303) at least one identifier that makes at least one excellent configuration profile identifiable; processing at least configuration data items and / or association data items in connection with the excellent configuration profile and generating (107, 207, 307) a monitoring signal based on at least one result of the processing; wherein the processing of the configuration and / or association data items comprises receiving specific configuration data items for a specific entity and storing them together with specific association data items in the database (305), wherein the individual specific association data items each describe relationships between one or more general configuration data items of the excellent configuration profile and / or one or more of the received specific configuration data items and thereby define a specific configuration profile comprising at least the excellent configuration profile and the received specific configuration data items related to one or more general configuration data items included in said excellent configuration profile; wherein the monitoring signal is made available, namely sent, to at least one receiver; wherein the entities have and / or represent automatic door systems, automatic gate systems, automatic window systems and / or automatic lighting systems.

2. Method according to Claim 1, wherein (i) the data items are processed after evaluating a control signal and determining a first value of the control signal and / or by means of a first module (9) which is selected and / or executed, preferably in response to the determination of the first value of the control signal, and / or (ii) the monitoring signal has a state of the result of the data processing.

3. Method according to one of the preceding claims, wherein the general association data items (i) relate each first general configuration data item in a first general group to at least one, preferably to a plurality of, second general configuration data item(s) in a second general group, and / or (ii) relate each second general configuration data item in the second general group to at least one, preferably to a plurality of, third general configuration data item(s) in a third general group, preferably relate each second general configuration data item in the second general group to a plurality of third general configuration data items in a plurality of third general groups, in particular relate each second general configuration data item in the second general group to at least one, preferably to a plurality of, first third general configuration data item(s) in a first third general group, to at least one, preferably to a plurality of, second third general configuration data item(s) in a second third general group and / or to at least one, preferably to a plurality of, third third general configuration data item(s) in a third third general group, and / or the specific association data items (i) relate each first specific configuration data item in a first specific group to at least one, preferably to precisely one or to a plurality of, first general configuration data item(s) in the first general group, and / or (ii) relate each second specific configuration data item in a second specific group to at least one, preferably to precisely one or to a plurality of, second general configuration data item(s) in the second general group, to at least one, preferably to precisely one or to a plurality of, first specific configuration data item(s) in the first specific group and / or to at least one, preferably to precisely one or to a plurality of, third, in particular first third, general configuration data item(s) in the third general group.

4. Method according to one of the preceding claims, wherein the processing of the configuration and / or association data items comprises retrieving (105, 205) the configuration data items of the excellent configuration profile from the database (3), wherein preferably (i) the retrieved configuration data items comprise at least general configuration data items, in particular in the second general group and / or the third general group, in particular the first third, second third and / or third third general group, and / or specific configuration data items, in particular in the second specific group, (ii) at least the retrieved configuration data items are structured within a data structure that is at least partially based on or represented by the association data items associating the retrieved configuration data items with one another, (iii) this processing of the data items is carried out after evaluating the control signal and determining a second value of the control signal and / or by means of a second module (5) which is selected and / or executed, preferably in response to the determination of the second value of the control signal, and / or (iv) the monitoring signal has the data structure and / or the retrieved configuration data items.

5. Method according to one of the preceding claims, wherein the processing of the configuration and / or association data items comprises comparing the excellent configuration profile with a further selected configuration profile, and in particular determining at least some of the common and / or different general configuration data items of the two configuration profiles, and wherein the monitoring signal is indicative of a result of this comparison, in particular of the similarities or differences between the two configuration profiles, wherein preferably a difference is at least characterized in that there are at least partially different second general configuration data items in the two configuration profiles and / or if the same second general configuration data items are associated with different third general configuration data items in the two configuration profiles, wherein preferably this processing of the data items is carried out after evaluating the control signal and determining a third value of the control signal and / or by means of a third module (7) which is selected and / or executed, preferably in response to the determination of the third value of the control signal.

6. Method according to one of the preceding claims, wherein the identifier is received from a first source; the specific configuration data items are received from the first and / or a second source; the control signal is received from the first, second and / or a third source; and / or the receiver is identical to the first, second and / or third source.

7. Device (1) which is configured to carry out a method according to one of Claims 1 to 6, wherein the device preferably comprises or represents at least one server and / or at least one cloud system.

8. Method which cooperates with a method according to one of Claims 1 to 6, the method comprising: sending an identifier of at least one configuration profile; receiving the monitoring signal, wherein preferably the received monitoring signal comprises the configuration data items for an entity that are included in the configuration profile, and configuring the entity on the basis of the received monitoring signal, in particular on the basis of the configuration data items, wherein the monitoring signal is preferably indicative of one or more configuration data items, and, for these configuration data items, the entity is configured only at least after a received confirmation.

9. Method according to Claim 8, wherein the configuration data items are structured within a data structure that describes or makes it possible to describe the relationships between the individual configuration data items; the method also comprises: sending configuration data items, in particular comprising the specific configuration data items for the entity that are received in claim 2 and stored in the database.

10. Device which is configured to carry out a method according to one of Claims 8 to 9, wherein the device preferably has or represents a part of an entity, such as a control module, and / or a smartphone.

11. Computer program product comprising instructions which, when the program is executed by a data processing device, in particular the device according to Claim 7 and / or according to Claim 10, cause this device to carry out the method according to one of Claims 1-6 and / or according to one of Claims 8-9.

12. Signal sequence representing instructions which, when executed on a data processing device, in particular the device according to Claim 7 and / or according to Claim 10, cause the device to carry out the method according to one of Claims 1-6 and / or according to one of Claims 8-9.