CN111737291A - Method, apparatus and database for querying equipment information - Google Patents

Abstract

The application relates to the technical field of information query and discloses a method for querying equipment information. The method for inquiring the equipment information comprises the following steps: the server obtains the device attribute and a pre-created query interface of the set data, and queries the device attribute value in the query interface of the set data according to the device attribute, wherein the set data is stored in a partial data table of a database, the partial data table corresponds to the authority of an authorized user, and the data table comprises the device attribute and the device attribute value corresponding to the device attribute. The method for inquiring the equipment information can reduce the time consumption of the inquiry process. The application also discloses a device for inquiring the equipment information and a database for storing the equipment information.

Description

Method, apparatus and database for querying equipment information

technical field

The present application relates to the technical field of information query, for example, to a method, apparatus and database for querying device information.

Background technique

At present, most data query products can query device data one-to-one, that is, only one type of data of one device can be queried at a time. However, in practical applications, it is often necessary to query a large amount of data. In order to realize the query of batch data, in the prior art, multiple query instructions are combined into a query form, and the query form is sent. After the server receives the query form, it splits the query form. Each query command is issued, the database is queried in turn according to each query command, and the query result is returned.

In the process of implementing the embodiments of the present disclosure, it is found that at least the following problems exist in the related art:

This method of querying device information takes a long time.

SUMMARY OF THE INVENTION

In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. This summary is not intended to be an extensive review, nor to identify key/critical elements or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.

The embodiments of the present disclosure provide a method, an apparatus and a database for querying device information, so as to solve the technical problems that the process of querying batch information is time-consuming and has poor real-time performance.

In some optional embodiments, a method for querying device information is applied to a server, and the method for querying device information includes:

A query interface for obtaining device properties and pre-created setting data;

Query the device attribute value in the query interface of the setting data according to the device attribute;

The setting data is stored in a partial data table in the database, the partial data table corresponds to the authority of the authorized user, and the data table includes the device attributes and their corresponding device attribute values.

Optionally, the query interface for the setting data is created in the following manner:

Access to authorized users;

Match the description information of each authority of the authorized user with the data structure, and determine the setting data;

Create a query interface;

establishing a mapping relationship between the query interface and the setting data;

A preset query rule of the query interface is set.

Optionally, obtaining the authority of the authorized user includes:

obtain user information;

Match the user information in the authorized user list, and determine whether the user information is authorized user information;

In the case that the user information is authorized user information, the authority of the authorized user is queried on the setting interface according to the user information.

Optionally, query the device attribute value on the query interface of the setting data according to the device attribute, including:

Adjusting the device attribute to a preset query structure; wherein, the preset query structure is adapted to the preset query rules of the query interface of the set data;

The device attribute value is queried on the query interface of the setting data according to the preset query structure.

Optionally, obtain device properties, including:

Obtain the device identification number (Identity document, ID);

The device attribute is read according to the device ID.

Optionally, reading the device attribute according to the device ID, including:

According to the device ID, read the device attribute in a remote dictionary service (Remote Dictionary Server, Redis);

In the case that the device attribute cannot be successfully read in the Redis, the device attribute is read in the database according to the device ID.

In some optional embodiments, the method for querying device information is applied to a terminal, and the method for querying device information includes:

Send a device ID to the server; wherein, the device ID is used to query device attributes;

Receive the device attribute value sent by the server; wherein, the device attribute value is queried in the query interface of the setting data according to the device attribute, and the setting data is stored in a part of the data table of the database, and the part of the data table Corresponding to the authority of the authorized user, the data table includes the device attribute and its corresponding device attribute value;

Displays the device property value.

Optionally, before receiving the device attribute value sent by the server, the method for querying device information further includes:

obtain user information;

Sending the user information to the server; wherein the user information is used to determine whether the current user has the right to access data.

In some optional embodiments, the database for storing device information includes:

a configuration structure module configured to generate a query interface for setting data;

The data structure module stores setting data, and the setting data includes device attributes and their corresponding device attribute values.

Optionally, the database for storing device information further includes:

The authorization structure module stores user rights and their corresponding authorization data structures;

The data structure module stores authorization data, and the authorization data structure has a mapping relationship with the authorization data;

The configuration structure module is further configured to determine all authorization data corresponding to a specific user authority as setting data.

In some optional embodiments, the apparatus for querying equipment information is applied to a server, and the apparatus for querying equipment information includes:

a first obtaining module, configured to obtain a query interface for device attributes and pre-created setting data;

a query module, configured to query the device attribute value at the query interface of the setting data according to the device attribute;

The setting data is stored in a partial data table in the database, the partial data table corresponds to the authority of the authorized user, and the data table includes the device attributes and their corresponding device attribute values.

Optionally, the first obtaining module includes:

a first obtaining unit, configured to obtain the authority of an authorized user;

a matching unit, configured to match each authority of the authorized user with the description information of the data structure, and determine the setting data;

a first creating unit, configured to create a query interface;

a second creating unit, configured to establish a mapping relationship between the query interface and the setting data;

a setting unit, configured to set a preset query rule of the query interface.

Optionally, the first obtaining unit is specifically configured as:

obtain user information;

Match the user information in the authorized user list, and determine whether the user information is authorized user information;

In the case that the user information is authorized user information, the authority of the authorized user is queried on the setting interface according to the user information.

Optionally, the query module includes:

an adjustment unit configured to adjust the device attribute to a preset query structure; wherein the preset query structure is adapted to a preset query rule of the query interface of the setting data;

The query unit is configured to query the device attribute value on the query interface of the setting data according to the preset query structure.

Optionally, the first obtaining module includes:

a second obtaining unit, configured to obtain the device ID;

a reading unit, configured to read the device attribute according to the device ID.

Optionally, the reading unit is specifically configured to:

Read the device attribute in Redis according to the device ID;

In the case that the device attribute cannot be successfully read in the Redis, the device attribute is read in the database according to the device ID.

In some optional embodiments, the device for querying device information is applied to a terminal, and the device for querying device information includes:

a first sending module, configured to send a device ID to the server; wherein, the device ID is used to query device attributes;

The first receiving module is configured to receive the device attribute value sent by the server; wherein, the device attribute value is queried in the query interface of the setting data according to the device attribute, and the setting data is stored in a part of the data table of the database , the part of the data table corresponds to the authority of the authorized user, and the data table includes the device attribute and its corresponding device attribute value;

A display module configured to display the device property value.

Optionally, the device for querying device information further includes:

The second obtaining module is configured to obtain user information before receiving the device attribute value sent by the server;

The second sending module is configured to send the user information to the server; wherein, the user information is used to determine whether the current user has the right to access data.

The method, device, and database for querying device information provided by the embodiments of the present disclosure can achieve the following technical effects:

When the device attribute value needs to be queried, according to the device attribute, the query interface of the set data can be queried, and the device attribute value can be obtained only by accessing the data table storing the set data, without accessing the entire database, which reduces the query process. time consuming.

The foregoing general description and the following description are exemplary and explanatory only and are not intended to limit the application.

Description of drawings

One or more embodiments are exemplified by the accompanying drawings, which do not constitute limitations of the embodiments, and elements with the same reference numerals in the drawings are shown as similar elements, and where:

FIG. 1 is an environmental schematic diagram of an actual environment involved in a method for querying device information provided by an embodiment of the present disclosure;

2 is a schematic diagram of a method for querying device information provided by an embodiment of the present disclosure;

3 is a schematic diagram of a query interface for creating setting data provided by an embodiment of the present disclosure;

FIG. 4 is a schematic diagram for obtaining the authority of an authorized user provided by an embodiment of the present disclosure;

5 is a schematic diagram of querying device attribute values on a query interface for setting data provided by an embodiment of the present disclosure;

6 is a schematic diagram of a method for querying device information provided by an embodiment of the present disclosure;

7 is a schematic diagram of a method for querying device information provided by an embodiment of the present disclosure;

8 is a schematic diagram of a method for querying device information provided by an embodiment of the present disclosure;

9 is a schematic diagram of a method for querying device information provided by an embodiment of the present disclosure;

10a is a schematic diagram of a database for storing device information provided by an embodiment of the present disclosure;

10b is a schematic diagram of a database for storing device information provided by an embodiment of the present disclosure;

11a is a schematic diagram of an apparatus for querying device information provided by an embodiment of the present disclosure;

11b is a schematic diagram of an apparatus for querying device information provided by an embodiment of the present disclosure;

11c is a schematic diagram of an apparatus for querying device information provided by an embodiment of the present disclosure;

11d is a schematic diagram of an apparatus for querying device information provided by an embodiment of the present disclosure;

12a is a schematic diagram of an apparatus for querying device information provided by an embodiment of the present disclosure;

12b is a schematic diagram of an apparatus for querying device information provided by an embodiment of the present disclosure;

FIG. 13 is a schematic diagram of an apparatus for querying device information provided by an embodiment of the present disclosure.

Detailed ways

In order to understand the features and technical contents of the embodiments of the present disclosure in more detail, the implementation of the embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings, which are for reference only and are not intended to limit the embodiments of the present disclosure. In the following technical description, for the convenience of explanation, numerous details are provided to provide a thorough understanding of the disclosed embodiments. However, one or more embodiments may be practiced without these details. In other instances, well-known structures and devices may be shown simplified in order to simplify the drawings.

The terms "first", "second" and the like in the description and claims of the embodiments of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data so used may be interchanged under appropriate circumstances for the purposes of implementing the embodiments of the disclosure described herein. Furthermore, the terms "comprising" and "having", and any variations thereof, are intended to cover non-exclusive inclusion.

Unless stated otherwise, the term "plurality" means two or more.

In the embodiment of the present disclosure, the character "/" indicates that the preceding and following objects are in an "or" relationship. For example, A/B means: A or B.

The term "and/or" is an associative relationship describing objects, indicating that three relationships can exist. For example, A and/or B, means: A or B, or, A and B three relationships.

At present, most data query products can query device data one-to-one, that is, only one type of data of one device can be queried at a time. In the embodiment of the present disclosure, in order to query the information of devices in batches, the terminal sends the device ID to the server, the server obtains the device attribute according to the device ID, and according to the device attribute, the device attribute is queried in batches in the query interface of the set data at one time. It only needs to execute the query command once to obtain multiple messages of the device without executing the query device attribute value one by one, which reduces the number of query commands executed, reduces the query time, and improves the real-time performance of the process of querying batch information.

With reference to FIG. 1 , an embodiment of the present disclosure provides an environmental schematic diagram of an actual environment involved in a method for querying device information. The implementation environment includes the terminal 110 and the server 120 .

The terminal 110 is an electronic device with a network access function and a human-computer interaction function. The terminal 110 may be a device such as a smart phone, a tablet computer, an Ultra-mobile Personal Computer (UMPC), a netbook, a Personal Digital Assistant (PDA), etc., but is not limited thereto. A specific application (Application, APP) is installed on the terminal. The terminal 110 can be set on the device, or can be set independently.

The server 120 may be one server, or a server cluster consisting of several servers, or a distributed server consisting of several servers.

In some practical applications, the server 120 is a distributed server, and the deployment of the server 120 complies with the principle of service concurrency, the principle of service classification, the principle of service-based authorization, and the principle of service expansion. Service nodes (Nodes) are distributed on the user side and the device side, and Nodes respond to real-time service requests through the reliable coordination system (ZooKeeper) of the distributed system.

With reference to FIG. 2 , an embodiment of the present disclosure provides a method for querying device information. In this embodiment, the method for querying device information is applied to the server shown in FIG. 1 as an example. Methods for querying device information include:

S201. Obtain a query interface for device attributes and pre-created setting data.

Among them, the device attribute refers to the attribute of the device that can be recorded data. For example, device properties include one or more of device details, device operating curves, device real-time status, and device failures.

The equipment details can include: equipment offline time, equipment installation time, first binding time, equipment installation address, equipment production factory, equipment online time, equipment startup time, equipment running time, equipment fault alarm times, user ID, One or more of the last login time of the user and the last login terminal name of the user.

A device operating curve is a curve of specific environmental variables that can be adjusted by the device over time. For example, if the air conditioner can adjust the indoor temperature, the equipment operation curve can include the curve of the indoor temperature changing with time; the refrigerator can adjust the temperature of the refrigerator compartment and the freezer compartment, then the equipment operation curve can include the curve of the temperature change of the refrigerator compartment or the freezer compartment with time. Curve of temperature versus time.

The real-time state of the device is the real-time running state of each actuator in the device, such as the real-time running state of the buzzer, or the real-time running state of the refrigerator/air conditioner compressor, or the opening and closing state of the device door.

Equipment faults can include fault codes, fault descriptions, and when the fault occurred.

The device properties can be directly received, for example, the terminal directly sends the device properties to the server, and the server directly obtains the device properties.

Or, obtain the device attribute indirectly, for example, obtain the device ID (the device ID sent by the receiving terminal), and read the device attribute according to the device ID. In this way, the terminal only needs to send the device ID to the server, that is, the user only needs to select/input the device ID in the terminal, and the service can obtain all device attribute values, which reduces user operations and improves user experience.

Optionally, reading the device properties according to the device ID includes: reading the device properties in Redis according to the device ID; if the device properties cannot be successfully read in Redis, reading the device properties in the database according to the device ID. Reading device attributes in Redis can improve the reading speed, further shorten the time-consuming of querying device batch information, and improve the real-time performance of querying batch information.

Correspondingly, when the device attribute changes, the server receives the new device attribute of the device, and updates the new device attribute of the device to Redis. for the next reading.

Optionally, the setting data includes one or more of equipment detail data, equipment operation curve data, equipment real-time status data and equipment failure data.

The query interface for setting data can be obtained in the following ways: a query interface for determining the setting data corresponding to the device ID according to the device ID; or, obtaining user information, and determining the query interface for setting data corresponding to the user information according to the user information interface.

In some practical applications, when a user logs in for the first time and queries device information for the first time, a query interface for setting data is created, and then a query interface for device attributes and setting data is obtained; attribute and directly query the query interface of the set data.

In some practical applications, when the authority of the authorized user changes, the query interface for setting data is re-created, and then the query interface for device attributes and setting data is obtained.

In some practical applications, the server is a distributed server, such as the Kaiyuan distributed service framework Dubbo server deployed on multiple machines, and the query interface for setting data can be a Remote Procedure Call (RPC) interface. Dubbo servers deployed on multiple machines can also achieve service concurrency.

S202 , query the device attribute value on the query interface of the setting data according to the device attribute.

Among them, the setting data is stored in some data tables in the database, and some data tables correspond to the permissions of authorized users, that is, some data tables are data tables in the database that authorized users have access rights, and the data tables include device attributes and their corresponding value of the device property.

The device attribute value is a concrete value corresponding to the device attribute. For example, the device attribute value includes one or more of the device detail value, the device operation curve value, the device real-time state value, and the device fault value.

The device details values can include: device offline time value, device installation time value, first binding time value, device installation address value, device production factory value, device cumulative online time value, device startup time value, device cumulative running time value, One or more of the value of the cumulative number of fault alarms of the device, the value of the user ID, the value of the last login time of the user, and the value of the last login terminal name of the user.

The device operating curve value is the time-varying value of a specific environmental variable that can be adjusted by the device. For example, if the air conditioner can adjust the indoor temperature, the equipment operation curve value can include the indoor temperature value that changes with time; the refrigerator can adjust the temperature of the refrigerator compartment and the freezer compartment, and the equipment operation curve can include the temperature value of the refrigerator compartment or the freezer temperature value that changes with time. room temperature value.

The real-time state value of the equipment includes the real-time running state value of the buzzer, or the real-time running state value of the refrigerator/air conditioner compressor, or the opening and closing state value of the device door.

The device fault value may include a fault code value, a fault description value, and a fault occurrence time value. Among them, the fault code value and the fault description value are predefined, and there is a one-to-one correspondence between the two. The fault description value can be an alarm for electricity failure, an alarm for an internal failure of the device, or an alarm for the environment where the device is located. Or, the fault description value can be power supply over-voltage/low-voltage protection alarm, leakage alarm; or abnormal compressor alarm, fan abnormal alarm; or high/low ambient temperature alarm, high ambient humidity alarm.

Send the query command of the preset query structure to the query interface of the set data, and the query interface can return the device attribute value. In some practical applications, the query interface can dynamically call setting data.

When the device attribute value needs to be queried, according to the device attribute, the query interface of the set data can be queried, and the device attribute value can be obtained only by accessing the data table storing the set data, without accessing the entire database, which reduces the query process. time consuming.

In some application scenarios, when multiple terminals send multiple query commands to the server, the server obtains the priority of each terminal and the priority of each query service, and provides the query service with high priority to the terminal with high priority .

As shown in Figure 3, the query interface for setting data is created in the following ways:

S301. Obtain the authority of an authorized user.

The authority here refers to the user's authority to access data (attribute values of each device). By setting the data access authority, data security is improved.

Permissions may include one or more of: a device that is allowed to access, a data attribute of the device that is allowed to access, and a time period for which access is allowed. For example, the first user is allowed to access device A and device B, the first user is not allowed to access device C, the second user is allowed to access device B and device C, and the second user is not allowed to access device A; or, the first user is allowed to access device A The device details of the device, the first user is not allowed to access the device running curve, device real-time status and device faults of the A device, the second user is allowed to access the device details and device faults of the A device, and the second user is not allowed to access the device operation of the A device curve and real-time status of the device; or, allow the first user to access the device attribute values of the A device for the past week, and allow the second user to access the device attribute values of the A device for the past half month.

The authority of the authorized user can be sent directly to the server through the terminal;

Alternatively, the terminal sends user information to the server, and in the server, an interface exposes the authority of a single user, and the server can query the authority of the authorized user through this interface.

S302 , match each authority of the authorized user with the description information of the data structure, and determine the setting data.

The description information of the data structure includes the information of the device that stores the data in the data table, the attribute information of the stored data, and the time information of the stored data.

Each authority of an authorized user is matched with one or more data structures, and one or more data structures can be matched by the authority of the authorized user. The data stored in the data table corresponding to one or more data structures is the authorization data. The authorization data is the setting data in the above steps.

In some practical applications, the server is a distributed server, such as a Dubbo server deployed on multiple machines. The metadata center of the Dubbo server deployed on multiple machines manages the description information of all open data internally, and exposes the open data structure RPC interface to the outside world. The description information of all data structures can be queried through the data structure RPC interface.

The server reads the device properties through the device ID, and can obtain all device properties. A user is usually only allowed to access the property values of some device properties, that is, the setting data includes some device properties and their corresponding device property values. The device attribute value obtained by querying the device attribute in the query interface of the setting data is only the device attribute value that the user is authorized to access (not the attribute value corresponding to all device attributes). In the process of obtaining the device attribute value, the terminal sends the device ID to the server, and the server can return the user-accessible device attribute value to the terminal. Obviously, network consumption is reduced; at the same time, the user only needs to provide the device ID to obtain the user-accessible device attribute value. Accessing device attribute values also improves user experience.

S303. Establish a query interface.

For example, create a variable to represent the query interface.

S304. Establish a mapping relationship between the query interface and the setting data.

For example, the Uniform Resource Locator (URL) of the setting data is bound to the aforementioned variable.

S305. Set a preset query rule of the query interface.

For example, set the request type, entry parameters and return parameters of the query interface. The request type includes GET or POST, the entry parameter includes one or more device attributes, and the return parameter includes the device attribute value corresponding to the above one or more device attributes (entry parameters).

In order to improve data security, access rights are usually set in the database. In the above steps, all the data tables that store the setting data are the setting data accessible to the authorized user, which facilitates the authorized users to read these setting data in batches, further reduces the time-consuming of querying batch information, and increases the batch size of querying. real-time information.

In some practical application scenarios, there are multiple device attributes, and different user requirements have different device attribute values. For example, the device attributes include a, b, and c, the first user only needs the a value, and the second user only needs the b value and the c value. In this case, the authority of the authorized user is user-defined, that is, the authority of the authorized user is a part of the maximum authority of the authorized user. For example, in theory, the first user can access a and b, but in the process of use, the first user can only access a, then, the first user's maximum authority can access a and b. In the actual application process, the first user's The permission is to be able to access a, but not to access b; in theory, the second user can access a, b, and c. In practical applications, the second user can only access b and c. Then, the maximum permission of the second user is to access a, b and c. b and c, in the actual application, the authority of the second user is to be able to access b and c. By setting the authority of the first user, the value returned to the first user only includes the a value (excluding the b value and the c value); similarly, by setting the authority of the second user, the value returned to the second user only includes b value and c value (excluding a value), it can be seen that setting user permissions can not only improve data security, but also configure query results that meet user needs for different users without transmitting all device attribute values. It improves the user experience; it also reduces network consumption.

As shown in Figure 4, the permissions of authorized users are obtained, including:

S401. Obtain user information.

The terminal reads the user information input by the user, and the terminal sends the user information to the server, so that the server can obtain the user information. Or, the query request sent by the terminal to the server includes user information, and the server parses out the user information after receiving the query request.

Before the user obtains authorization, the user information includes a user password, or a user password and a user ID. The terminal sends the user information to the server, and the server receives the user information. Optionally, the terminal sends the user information to the server through an authentication interface. For example, in a distributed server, the terminal sends user information to the server through an authentication RPC interface.

After the user obtains authorization, the user information includes a user password, or a user ID, or a user password and a user ID. The server reads the query request sent by the terminal, and parses the user information in the query request.

S402. Match user information in the authorized user list, and determine whether the user information is authorized user information.

Authorized user information is stored in the authorized user list. If the user information is successfully matched in the authorized user list, the user information is authorized user information; if the user information cannot be matched in the authorized user list, the user information is unauthorized user information. .

S403 , in the case that the user information is the authorized user information, query the authority of the authorized user on the setting interface according to the user information.

The setting interface exposes the authority of a single user, and the authority of the authorized user can be queried through the setting interface.

Through the above steps, the authority of the authorized user can be obtained.

With reference to Figure 5, according to the device attribute, the device attribute value is queried in the query interface of the set data, including:

S501. Adjust the device attribute to a preset query structure.

The preset query structure is adapted to the preset query rules of the query interface of the set data.

The preset query structure includes one or more conditions, and each data in the query result satisfies these conditions.

In some specific applications, the preset query structure includes query methods, table names, query conditions, etc., wherein the query method can be a fuzzy query or a sorted query, and the query conditions can be time filtering or upper and lower limit filtering.

S502 , query the device attribute value on the query interface of the setting data according to the preset query structure.

After receiving the query command of the preset query structure, the setting data query interface returns a query result corresponding to the query command.

Through the above steps, multiple pieces of information corresponding to device attributes can be obtained.

With reference to FIG. 6 , an embodiment of the present disclosure provides a method for querying device information. In this embodiment, the method for querying device information is applied to the terminal shown in FIG. 1 as an example for illustration. The method for querying device information includes:

S601. Send a device ID to a server, where the device ID is used to query device attributes.

The device ID includes a device number or a device media access control address (Media Access Control Address, MAC). In practical applications, the device ID may be all or part of the device number, or the device ID may be all or part of the device MAC.

After receiving the device ID, the server can read the device attribute in Redis according to the device ID; if the device attribute cannot be successfully read in Redis, the device attribute can be read in the database according to the device ID.

Device properties refer to properties of a device that can be recorded with data. For example, device properties include one or more of device details, device operating curves, device real-time status, and device failures.

S602. Receive the device attribute value sent by the server.

The device attribute value is queried in the query interface of the setting data according to the device attribute, and the setting data is stored in a part of the data table in the database, and the setting data includes the device attribute and its corresponding device attribute value.

Device properties refer to properties of a device that can be recorded with data. For example, device properties include one or more of device details, device operating curves, device real-time status, and device failures.

The equipment details can include: equipment offline time, equipment installation time, first binding time, equipment installation address, equipment production factory, equipment online time, equipment startup time, equipment running time, equipment fault alarm times, user ID, One or more of the last login time of the user and the last login terminal name of the user.

A device operating curve is a curve of specific environmental variables that can be adjusted by the device over time. For example, if the air conditioner can adjust the indoor temperature, the equipment operation curve can include the curve of the indoor temperature changing with time; the refrigerator can adjust the temperature of the refrigerator compartment and the freezer compartment, then the equipment operation curve can include the curve of the temperature change of the refrigerator compartment or the freezer compartment with time. Curve of temperature versus time.

The real-time state of the device is the real-time running state of each actuator in the device, such as the real-time running state of the buzzer, or the real-time running state of the refrigerator/air conditioner compressor, or the opening and closing state of the device door.

Equipment faults can include fault codes, fault descriptions, and when the fault occurred.

The device attribute value is a concrete value corresponding to the device attribute. For example, the device attribute value includes one or more of the device detail value, the device operation curve value, the device real-time state value, and the device fault value.

The device details values can include: device offline time value, device installation time value, first binding time value, device installation address value, device production factory value, device cumulative online time value, device startup time value, device cumulative running time value, One or more of the value of the cumulative number of fault alarms of the device, the value of the user ID, the value of the last login time of the user, and the value of the last login terminal name of the user.

The device operating curve value is the time-varying value of a specific environmental variable that can be adjusted by the device. For example, if the air conditioner can adjust the indoor temperature, the equipment operation curve value can include the indoor temperature value that changes with time; the refrigerator can adjust the temperature of the refrigerator compartment and the freezer compartment, and the equipment operation curve can include the temperature value of the refrigerator compartment or the freezer temperature value that changes with time. room temperature value.

The real-time state value of the equipment includes the real-time running state value of the buzzer, or the real-time running state value of the refrigerator/air conditioner compressor, or the opening and closing state value of the device door.

The device fault value may include a fault code value, a fault description value, and a fault occurrence time value. Among them, the fault code value and the fault description value are predefined, and there is a one-to-one correspondence between the two. The fault description value can be an alarm for electricity failure, an alarm for an internal failure of the device, or an alarm for the environment where the device is located. Or, the fault description value can be power supply over-voltage/low-voltage protection alarm, leakage alarm; or abnormal compressor alarm, fan abnormal alarm; or high/low ambient temperature alarm, high ambient humidity alarm.

Optionally, before receiving the device attribute value sent by the server, the method for querying device information further includes: obtaining a screening time period, and sending the screening time period to the server.

In some application scenarios, the terminal includes a touch screen, the user inputs the screening time period on the touch screen, and the terminal reads the user's operation on the touch screen to obtain the screening time period.

In other practical application scenarios, the terminal includes a display screen and an input device (such as a keyboard or a mechanical operation panel), the user inputs the screening time period through the input device, and the terminal reads the user's operation on the input device to obtain the screening time period.

S603. Display the device attribute value.

The terminal displays device attribute values in tabular form, for example, the terminal displays device details, device implementation status information, and device faults in tabular form.

Or, the terminal displays the device property value in the form of a curve, for example, the terminal displays the device running curve.

When the device attribute value needs to be queried, according to the device attribute, the query interface of the set data can be queried, and the device attribute value can be obtained only by accessing the data table storing the set data, without accessing the entire database, which reduces the query process. time consuming.

With reference to Figure 7, before receiving the device attribute value sent by the server, the method for querying device information further includes:

S701. Obtain user information.

The terminal reads the user information input by the user, and the terminal sends the user information to the server, so that the server can obtain the user information. User information includes user password, or, user password and user ID.

In some practical application scenarios, the terminal includes a touch screen, the user inputs user information on the touch screen, and the terminal reads the user's operation on the touch screen to obtain the user information.

In other practical application scenarios, the terminal includes a display screen and an input device (such as a keyboard or a mechanical operation panel), the user inputs user information through the input device, and the terminal reads the user's operation on the input device to obtain the user information.

S702. Send user information to the server.

The server can determine whether the current user has the right to access the data according to the user information. Improved data security.

With reference to FIG. 8 , an embodiment of the present disclosure provides a method for querying device information. In this embodiment, the method for querying device information is described by way of example from the perspective of information interaction between the terminal and the server. Methods for querying device information include:

S801, the terminal sends the device ID to the server;

S802, the server obtains the device attribute according to the device ID;

S803, the server obtains a query interface for setting data;

S804, the server queries the device attribute value on the query interface of the set data according to the device attribute;

S805, the terminal receives the device attribute value sent by the server;

S806, the terminal displays the device attribute value.

With reference to FIG. 9 , an embodiment of the present disclosure provides a method for querying device information. In this embodiment, the method for querying device information is described by way of example from the perspective of information interaction between the terminal and the server. Methods for querying device information include:

S901. The terminal obtains user information;

S902, the terminal sends user information to the server;

S903, the server matches the user information in the authorized user list, and determines whether the user information is authorized user information;

S904, in the case that the user information is authorized user information, the terminal sends the device ID to the server;

S905, the server obtains the device attribute according to the device ID;

S906, the server obtains a query interface for setting data;

S907, the server queries the device attribute value on the query interface of the set data according to the device attribute;

S908, the terminal receives the device attribute value sent by the server;

S909, the terminal displays the device attribute value.

In some practical application scenarios, the user logs in on the login interface, the user selects the device ID and time period on the selection interface, the user clicks confirm, and the interface displays one or more of the device details, running curve, real-time status, and fault push.

With reference to Fig. 10a, an embodiment of the present disclosure provides a database for storing device information. The database for storing device information includes a configuration structure module 1001 and a data structure module 1002, wherein the configuration structure module 1001 is configured to generate a query interface for setting data; the data structure module 1002 stores setting data, and the setting data includes Device properties and their corresponding device property values.

In the above database, the device attributes and their corresponding device attribute values are used as independent modules with a query interface, which facilitates independent access to the setting data. The device property value can be obtained by simply accessing the data table storing the setting data, without accessing the entire database, reducing the time-consuming of the query process.

As shown in FIG. 10 b , the database for storing device information further includes an authorization structure module 1003 . The authorization structure module 1003 stores the user authority and its corresponding authorization data structure; the data structure module 1002 stores authorization data, and the authorization data structure and the authorization data have a mapping relationship; the configuration structure module 1001 is also configured to determine all authorizations corresponding to the specific user authority The data is the setting data.

Each model of the above database can be set on the same service or on different servers.

The configuration structure module 1001 may store data through a relational table, for example, using a KeyValue structure or a Json structure to store data. The configuration fabric module 1001 may also include Redis.

The data structure module 1002 can store data through a relational table, for example, using a KeyValue structure or a Json structure to store data. The data structure module 1002 may also include Redis.

The authorization structure module 1003 can store data through a relational table, for example, using a KeyValue structure or a Json structure to store data. The authorization structure module 1003 may also include Redis.

In some embodiments, the database for storing device information further includes an effective management module, in which the effective management module stores interface access records, authorization monitoring, and invocation delays.

Optionally, the database for storing device information further includes a cache memory (Cache) module, which is connected with the configuration structure module 1001 and the effective management module. After the configuration structure module 1001 or the effective management module changes the data, the changed data is synchronized to the Cache module, which can reduce the pressure on the database.

With reference to Fig. 11a, an embodiment of the present disclosure provides an apparatus for querying device information. The apparatus for querying device information can be implemented as all or a part of the server shown in FIG. 1 through software, hardware or a combination of the two. The apparatus for querying device information includes a first obtaining module 1110 and a querying module 1120, wherein the first obtaining module 1110 is configured to obtain a query interface for device attributes and pre-created setting data; the querying module 1120 is configured to The device attribute queries the device attribute value in the query interface of the setting data. The setting data is stored in some data tables of the database, and some data tables correspond to the authority of the authorized user. The data table includes the device attributes and their corresponding device attribute values.

11b, the first obtaining module 1110 includes a first obtaining unit 1111, a matching unit 1112, a first creating unit 1113, a second creating unit 1114 and a setting unit 1115, wherein the first obtaining unit 1111 is configured to obtain authorization the user's authority; the matching unit 1112 is configured to match each authority of the authorized user with the description information of the data structure, and determine the setting data; the first creating unit 1113 is configured to create a query interface; the second creating unit 1114 is configured to create The mapping relationship between the query interface and the setting data; the setting unit 1115 is configured to set a preset query rule of the query interface.

Optionally, the first obtaining unit is specifically configured as:

obtain user information;

Match the user information in the authorized user list to determine whether the user information is authorized user information;

In the case that the user information is the authorized user information, the authority of the authorized user is queried in the setting interface according to the user information.

11c, the query module 1120 includes an adjustment unit 1121 and a query unit 1122, wherein the adjustment unit 1121 is configured to adjust the device attributes to a preset query structure, the preset query structure and the preset data query interface preset The query rule is adapted; the query unit 1122 is configured to query the device attribute value in the query interface of the setting data according to the preset query structure.

As shown in FIG. 11d, the first obtaining module 1110 includes a second obtaining unit 1114 and a reading unit 1115, wherein the second obtaining unit 1114 is configured to obtain the device ID; the reading unit 1115 is configured to read the device according to the device ID Attributes.

Optionally, the reading unit is specifically configured to: read the device attribute in Redis according to the device ID; if the device attribute cannot be successfully read in Redis, read the device attribute in the database according to the device ID.

With reference to Fig. 12a, an embodiment of the present disclosure provides an apparatus for querying device information. The apparatus for querying device information may implement all or a part of the terminal shown in FIG. 1 through software, hardware or a combination of the two. The apparatus for querying device information includes a first sending module 1210, a first receiving module 1220 and a display module 1230, wherein the first sending module 1210 is configured to send a device ID to a server; wherein the device ID is used to query device attributes The first receiving module 1220 is configured to receive the device attribute value sent by the server; wherein, the device attribute value is queried according to the device attribute in the query interface of the set data, and the set data is stored in the partial data table of the database, and the partial data The table corresponds to the authority of the authorized user, and the data table includes device attributes and their corresponding device attribute values; the display module 1230 is configured to display the device attribute values.

12b, the apparatus for querying device information further includes a second obtaining module 1240 and a second sending module 1250, wherein the second obtaining module 1240 is configured to obtain user information before receiving the device attribute value sent by the server ; The second sending module 1250 is configured to send user information to the server; wherein, the user information is used to determine whether the current user has the right to access data.

Optionally, the second obtaining module 1240 is further configured to obtain a screening time period; the second sending module 1250 is further configured to send the screening time period to the server.

In some embodiments, the apparatus for querying device information includes a processor and a memory storing program instructions, and the processor is configured to execute the method for querying device information provided by the foregoing embodiments when executing the program instructions.

With reference to FIG. 13 , an embodiment of the present disclosure provides an apparatus for querying device information. The device for querying device information includes:

A processor (processor) 131 and a memory (memory) 132 may also include a communication interface (Communication Interface) 133 and a bus 134 . The processor 131 , the communication interface 133 , and the memory 132 can communicate with each other through the bus 134 . The communication interface 133 may be used for information transfer. The processor 131 may invoke the logic instructions in the memory 132 to execute the method for querying device information provided by the foregoing embodiments.

In addition, the above-mentioned logic instructions in the memory 132 can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product.

As a computer-readable storage medium, the memory 132 may be used to store software programs and computer-executable programs, such as program instructions/modules corresponding to the methods in the embodiments of the present disclosure. The processor 131 executes functional applications and data processing by running the software programs, instructions, and modules stored in the memory 132 , that is, to implement the methods in the above method embodiments.

The memory 132 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the terminal device, and the like. Additionally, memory 132 may include high-speed random access memory, and may also include non-volatile memory.

Embodiments of the present disclosure provide a storage medium storing computer-executable instructions, where the computer-executable instructions are configured to execute the method for querying device information provided by the foregoing embodiments.

Embodiments of the present disclosure provide a computer program product. The computer program product includes a computer program stored on a computer-readable storage medium. The computer program includes program instructions. When the program instructions are executed by a computer, the computer is made to execute the program provided by the foregoing embodiments. The method used to query device information.

The above-mentioned computer-readable storage medium may be a transient computer-readable storage medium, and may also be a non-transitory computer-readable storage medium.

The technical solutions of the embodiments of the present disclosure may be embodied in the form of software products, and the computer software products are stored in a storage medium and include one or more instructions to enable a computer device (which may be a personal computer, a server, or a network equipment, etc.) to execute all or part of the steps of the methods in the embodiments of the present disclosure. The aforementioned storage medium may be a non-transitory storage medium, including: U disk, removable hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc. A medium that can store program codes, and can also be a transient storage medium.

The foregoing description and drawings sufficiently illustrate the embodiments of the present disclosure to enable those skilled in the art to practice them. Other embodiments may include structural, logical, electrical, process, and other changes. The examples are only representative of possible variations. Unless expressly required, individual components and functions are optional and the order of operations may vary. Portions and features of some embodiments may be included in or substituted for those of other embodiments. Also, the terms used in this application are used to describe the embodiments only and not to limit the claims. As used in the description of the embodiments and the claims, the singular forms "a" (a), "an" (an) and "the" (the) are intended to include the plural forms as well, unless the context clearly dictates otherwise. . Similarly, the term "and/or" as used in this application is meant to include any and all possible combinations of one or more of the associated listings. Additionally, when used in this application, the term "comprise" and its variations "comprises" and/or including and/or the like refer to stated features, integers, steps, operations, elements, and/or The presence of a component does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and/or groupings of these. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, or device that includes the element. Herein, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the various embodiments may refer to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method section disclosed in the embodiments, reference may be made to the description of the method section for relevant parts.

Those skilled in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software may depend on the specific application and design constraints of the technical solution. Skilled artisans may use different methods for implementing the described functionality for each particular application, but such implementations should not be considered beyond the scope of the disclosed embodiments. A skilled person can clearly understand that, for the convenience and brevity of description, for the specific working process of the above-described systems, devices and units, reference may be made to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the embodiments disclosed herein, the disclosed methods and products (including but not limited to apparatuses, devices, etc.) may be implemented in other ways. For example, the apparatus embodiments described above are only illustrative. For example, the division of units may only be a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or may be Integration into another system, or some features can be ignored, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms. Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. This embodiment may be implemented by selecting some or all of the units according to actual needs. In addition, each functional unit in the embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executables for implementing the specified logical function(s) instruction. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented in special purpose hardware-based systems that perform the specified functions or actions, or special purpose hardware implemented in combination with computer instructions.

Claims (11)

1. A method for inquiring equipment information is applied to a server, and is characterized in that the method comprises the following steps:

obtaining the equipment attribute and a query interface of pre-created setting data;

inquiring the attribute value of the equipment in an inquiry interface of the set data according to the attribute of the equipment;

the setting data is stored in a partial data table of a database, the partial data table corresponds to the authority of an authorized user, and the data table comprises the device attribute and the device attribute value corresponding to the device attribute.

2. The method of claim 1, wherein the query interface for the provisioning data is created by:

obtaining the authority of an authorized user;

matching each authority of the authorized user with the description information of a data structure, and determining the set data;

establishing a query interface;

establishing a mapping relation between the query interface and the set data;

and setting a preset inquiry rule of the inquiry interface.

3. The method of claim 2, wherein obtaining the rights of the authorized user comprises:

obtaining user information;

matching the user information in an authorized user list, and judging whether the user information is authorized user information;

and under the condition that the user information is authorized user information, inquiring the authority of the authorized user in a setting interface according to the user information.

4. The method of claim 1, wherein querying the device attribute value in a query interface of the setting data according to the device attribute comprises:

adjusting the device attribute to a preset query structure; the preset query structure is matched with a preset query rule of a query interface of the set data;

and inquiring the equipment attribute value at the inquiry interface of the set data according to the preset inquiry structure.

5. The method of any of claims 1 to 4, wherein obtaining device attributes comprises:

obtaining a device ID;

and reading the device attribute according to the device ID.

6. The method of claim 5, wherein reading the device attribute according to the device ID comprises:

reading the device attribute in Redis according to the device ID;

and under the condition that the device attribute cannot be successfully read in the Redis, reading the device attribute in a database according to the device ID.

7. A method for inquiring equipment information is applied to a terminal, and is characterized in that the method comprises the following steps:

sending the device ID to a server; wherein the device ID is used for inquiring device attributes;

receiving a device attribute value sent by a server; the device attribute value is inquired in an inquiry interface of set data according to the device attribute, the set data is stored in a partial data table of a database, the partial data table corresponds to the authority of an authorized user, and the data table comprises the device attribute and the device attribute value corresponding to the device attribute;

and displaying the equipment attribute value.

8. A database for storing device information, comprising:

a configuration structure module configured to generate a query interface of the setting data;

and the data structure module stores setting data, and the setting data comprises equipment attributes and corresponding equipment attribute values.

9. The database of claim 8, further comprising:

the authorization structure module stores the user authority and an authorization data structure corresponding to the user authority;

the data structure module stores authorization data, and the authorization data structure and the authorization data have a mapping relation;

the configuration structure module is also configured to determine all authorization data corresponding to the specific user authority as setting data.

10. An apparatus for querying device information, applied to a server, the apparatus comprising:

a first obtaining module configured to obtain a device attribute and a query interface of pre-created setting data;

the query module is configured to query the device attribute value at the query interface of the set data according to the device attribute;

the setting data is stored in a partial data table of a database, the partial data table corresponds to the authority of an authorized user, and the data table comprises the device attribute and the device attribute value corresponding to the device attribute.

11. An apparatus for querying device information, applied to a terminal, the apparatus comprising:

a first transmitting module configured to transmit the device ID to the server; wherein, the device ID is used for inquiring the device attribute;

the first receiving module is configured to receive the device attribute value sent by the server; the device attribute value is inquired in an inquiry interface of set data according to the device attribute, the set data is stored in a partial data table of a database, the partial data table corresponds to the authority of an authorized user, and the data table comprises the device attribute and the device attribute value corresponding to the device attribute;

a display module configured to display the device attribute values.

Images