Method, device, electronic device and storage medium for determining an Internet of Things device

By breaking down IoT devices into a set of service functions and using object models to match target devices, the problems of resource waste and low configuration efficiency in device linkage are solved, achieving more efficient device resource utilization and stability.

CN116506494BActive Publication Date: 2025-09-30ALLIANZ QIZHI (ANHUI) TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310500415.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-05-04
Publication Date
2025-09-30
Estimated Expiration
2043-05-04

AI Technical Summary

Technical Problem

When existing IoT devices are configured in linkage, it is difficult to match the device service functions, resulting in resource waste and inefficient configuration.

Method used

By breaking down devices into a collection of service functions, using object models to obtain the service functions of each device, matching target devices according to service function requirements, and combining distance range and attribute optimization rules, we can improve device resource utilization and configuration efficiency.

Benefits of technology

It achieves more efficient equipment resource utilization and configuration, reduces resource waste, and improves the accuracy and stability of equipment linkage.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116506494B_ABST
    Figure CN116506494B_ABST
Patent Text Reader

Abstract

The present application provides a method, apparatus, electronic device and storage medium for determining an IoT device, the method comprising: obtaining device linkage rules; the device linkage rules including service function requirements; determining a device to be matched from an access device based on the service function requirements and the service functions of the access device; wherein the service functions of the access device are obtained based on the physical model corresponding to the device; and determining a target device from the device to be matched. The service functions of the access device are used as the granularity for determining the target device, that is, the service functions corresponding to each device are obtained in advance using the physical model, so that device linkage operations are performed based on the service functions of the device, making full use of the service capabilities of each device and improving the resource utilization rate of IoT devices. At the same time, since there is no need to manually manage the service functions of each device, the efficiency of device configuration is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of Internet of Things technology, and more specifically, to a method, apparatus, electronic device, and storage medium for determining an Internet of Things device. Background Art

[0002] The Internet of Things (IoT) refers to the use of various information sensing devices and technologies to collect real-time information about objects or processes, enabling ubiquitous connectivity between objects and people, and enabling intelligent perception, identification, and management of objects and processes. With the rapid development of IoT technology, it is increasingly being applied in various fields, including industry, agriculture, transportation, energy, and smart cities. An increasing number of devices, sensors, and positioning systems are connected to IoT platforms through the network, and configuration rules enable inter-device linkage and operation, providing users with the services they need. Existing IoT devices may have multiple functions, some of which may be the same or different. When configuring IoT device linkage, business managers must clearly understand the service capabilities of each device, a significant workload that leads to low efficiency. Summary of the Invention

[0003] The purpose of the embodiments of the present invention is to provide a method, apparatus, electronic device and storage medium for determining an IoT device, which breaks down a single device into a set of one or more service capabilities, determines a target device from among the devices to be matched that can provide services according to device linkage rules, and improves the efficiency of device configuration.

[0004] In a first aspect, an embodiment of the present application provides a method for determining an IoT device, comprising: obtaining device linkage rules; the device linkage rules include service function requirements; determining a device to be matched from an access device based on the service function requirements and the service functions of the access device; wherein the service functions of the access device are obtained based on a physical model corresponding to the device; and determining a target device from the device to be matched.

[0005] In the above implementation process, the service function of each access device is obtained based on the physical model corresponding to the device, and the device to be matched is determined from the access devices based on the service function requirements and the service function of the access device. The above solution uses the service function of the access device as the granularity for determining the target device, that is, the physical model is used in advance to obtain the service function corresponding to each device, and the device linkage operation is carried out according to the service function of the device, making full use of the service capabilities of each device and improving the resource utilization rate of the Internet of Things device. This improves the existing technology that uses a single device as the minimum granularity for Internet of Things service management. When performing Internet of Things device linkage, it is difficult to match the Internet of Things device with its service capability, resulting in a large amount of waste of device service function resources. At the same time, since there is no need to manually manage the service function of each device, the efficiency of device configuration is improved.

[0006] Optionally, in an embodiment of the present application, before determining the device to be matched from the access device based on the service function requirements and the service functions of the access device, the method also includes: formatting the service functions of the access device to obtain a physical model of the access device; the physical model includes a physical model identifier; based on the physical model of the access device, obtaining the service function corresponding to the access device; the service function includes a service function identifier; and the physical model identifier is associated with the corresponding service function identifier.

[0007] In this implementation, the object model describes the device's services, attributes, and commands in a unified format. By breaking down the service functions defined in the object model, the corresponding service functions of the connected device are obtained, improving resource utilization of IoT devices. This allows managers to fully utilize device capabilities without having to learn specialized device parameter knowledge, improving management efficiency and convenience.

[0008] Optionally, in an embodiment of the present application, before determining the device to be matched from the access device based on the service function requirements and the service functions of the access device, the method also includes: connecting the device to be accessed to the Internet of Things platform, and performing identity authentication and access configuration to obtain the access device; the access device includes an access device identifier; and the access device identifier is associated with the corresponding object model identifier.

[0009] In the above implementation process, the access device is obtained by connecting the device to be connected to the IoT platform. The access device includes an access device identifier. By associating the access device identifier with the corresponding object model identifier, and then associating the object model identifier with the corresponding service function identifier, the access device can be disassembled into a set of one or more corresponding service functions. Through more fine-grained device resource management, resource utilization and configuration efficiency are improved.

[0010] Optionally, in an embodiment of the present application, the device linkage rules also include distance range requirements and attribute preference rules; determining the target device from the devices to be matched includes: determining the device to be confirmed that meets the distance range requirements from the devices to be matched based on the distance range requirements; obtaining the matching degree of the device to be confirmed based on the attribute preference rules; and determining the target device from the devices to be confirmed based on the matching degree.

[0011] In the above implementation process, by flexibly configuring the distance range requirements and attribute optimization rules in the device linkage rules, the target device that meets the actual needs can be determined from the devices to be matched, the service needs can be met, the service functions of the device can be fully utilized, and the accuracy of determining the target device can be improved.

[0012] Optionally, in an embodiment of the present application, the matching degree of the device to be confirmed is obtained based on the attribute optimization rule, including: sending a parameter request to the device to be confirmed, and obtaining the business attribute parameters returned by the device to be confirmed; determining the weight of each business attribute based on the attribute optimization rule; and calculating the matching degree of the device to be confirmed based on the business attribute parameters and the weight corresponding to each business attribute.

[0013] In the above implementation process, the matching degree of each pending device is calculated using the service attribute parameters and the weight corresponding to each service attribute. Based on the matching degree of each pending device, the device with the highest matching degree is selected as the target device, fully utilizing the attribute resources of each pending device and improving resource utilization.

[0014] Optionally, in an embodiment of the present application, after determining the target device from the devices to be matched, the method further includes: sending an execution command to the target device so that the target device executes the execution command; receiving the execution result sent by the target device; if the execution result indicates that the service is not completed, re-determining the target device based on the matching degree.

[0015] In the aforementioned implementation process, if a traditional IoT device linkage strategy fails, there's usually no remedial action, requiring a re-implementation of the IoT device linkage strategy to determine the target device. By calculating the matching degree for the devices to be confirmed that meet the device linkage rules, we avoid having to recalculate the matching devices after a service failure. Instead, we can directly re-determine the target device based on the matching degree, improving service stability and the probability of successful execution.

[0016] Optionally, in an embodiment of the present application, obtaining the device linkage rule includes: determining whether the Internet of Things system meets a pre-configured rule triggering condition; if the rule triggering condition is met, obtaining the device linkage rule.

[0017] In the above implementation process, when the rule triggering conditions are met, the Internet of Things device determination method is executed to realize the linkage of Internet of Things devices and improve the stability of the device linkage rules.

[0018] In the second aspect, an embodiment of the present application also provides an Internet of Things device determination device, including: an acquisition module for obtaining device linkage rules; the device linkage rules include service function requirements; a matching module for determining a device to be matched from an access device based on the service function requirements and the service functions of the access device; wherein the service functions of the access device are obtained based on the physical model corresponding to the device; a determination module for determining a target device from the device to be matched.

[0019] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: a processor and a memory, wherein the memory stores machine-readable instructions executable by the processor, and when the machine-readable instructions are executed by the processor, the method described above is performed.

[0020] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the method described above is executed.

[0021] The present application provides a method, apparatus, electronic device and storage medium for determining an IoT device, which obtains the service function of each access device according to the physical model corresponding to the device, and determines the device to be matched from the access device according to the service function requirements and the service function of the access device. The above scheme uses the service function of the access device as the granularity for determining the target device, that is, the physical model is used in advance to obtain the service function corresponding to each device, and the device linkage operation is performed according to the service function of the device, making full use of the service capability of each device and improving the resource utilization rate of the IoT device. It improves the existing technology that uses a single device as the minimum granularity for IoT service management. When performing IoT device linkage, it is difficult to match the IoT device with its service capability, resulting in a large amount of waste of device service function resources. At the same time, since there is no need to manually manage the service function of each device, the efficiency of device configuration is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0023] Figure 1 A flowchart of a method for determining an IoT device provided in an embodiment of the present application;

[0024] Figure 2 A schematic diagram of the structure of the physical model provided in the embodiment of the present application;

[0025] Figure 3 A schematic diagram of the structure of the Internet of Things platform provided in an embodiment of the present application;

[0026] Figure 4 A schematic diagram of the business process provided in this application embodiment;

[0027] Figure 5 A physical model association diagram provided in an embodiment of the present application;

[0028] Figure 6 A schematic diagram of the hardware framework of the Internet of Things platform provided in an embodiment of the present application;

[0029] Figure 7 A schematic diagram of an Internet of Things service device provided in an embodiment of the present application;

[0030] Figure 8 A schematic diagram of the structure of an IoT device identification device provided in an embodiment of the present application;

[0031] Figure 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] The following embodiments of the technical solution of the present application will be described in detail with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present application and are therefore only examples and are not intended to limit the scope of protection of the present application.

[0033] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing specific embodiments and are not intended to limit this application.

[0034] In the description of the embodiments of this application, the technical terms "first" and "second" are used only to distinguish different objects and should not be understood to indicate or imply relative importance or implicitly specify the quantity, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, the meaning of "plurality" is two or more, unless otherwise specifically defined.

[0035] See Figure 1 The flowchart of a method for determining an IoT device provided by an embodiment of the present application is shown. The method for determining an IoT device provided by an embodiment of the present application can be applied to an electronic device, which is equipped with an IoT system that can be used to determine IoT devices. The electronic device may include a terminal and a server; the terminal may specifically be a smartphone, a tablet computer, a computer, a personal digital assistant (PDA), etc.; the server may specifically be an application server or a web server. The method for determining an IoT device may include the following steps:

[0036] Step S110: Obtain device linkage rules; the device linkage rules include service function requirements.

[0037] Step S120: Determine a device to be matched from the access devices according to the service function requirements and the service functions of the access devices; wherein the service functions of the access devices are obtained according to the physical model corresponding to the devices.

[0038] Step S130: Determine a target device from the devices to be matched.

[0039] In step S110, device linkage rules refer to the rules that users can configure for devices connected to the IoT platform. When the conditions of the set rules are met, the platform triggers the corresponding actions to call the device to meet the user's service needs. Device linkage rules include service function requirements, which are the service functions that the selected device must possess. Devices include smart home devices, sensors, smart cars, cameras, and robots. Service functions include collecting sensor data, collecting image data, and controlling smart homes. In one embodiment, device linkage rules can be implemented by a configuration rule engine.

[0040] For example, device linkage refers to triggering conditions based on preset rules, enabling individual devices that meet the rules to provide services to meet service needs. It can also trigger coordinated responses across multiple devices, achieving device linkage and intelligent control, where multiple devices work together to meet service needs. For example, if a temperature sensor reports that the temperature exceeds a preset threshold, an email or text message will be automatically sent, or the platform will automatically issue a command to the device to shut down.

[0041] In step S120, the object model is a digital description of the product, which defines the functions of the product. The object model abstracts and summarizes the product functions of different brands and categories to form a "standard object model", which makes it easier for all parties to describe, control and understand the product functions in a unified language.

[0042] Access devices are devices that connect to the IoT platform and have completed identity authentication and access configuration. The object model uses a unified format to describe the services, attributes, and commands of access devices. The service commands in the object model are extracted and concretely defined to generate the service functions of the access device. In other words, the object model breaks down an access device into its corresponding service function or a collection of multiple service functions.

[0043] According to the service function requirement, an access device that meets the service function requirement is matched from the access devices and is determined as a device to be matched.

[0044] In step S130, the device to be matched is an access device that can meet the service function requirements in the device linkage rules. If there is one device to be matched, it is used as the target device; if there are multiple devices to be matched, some optimal judgment rules can be used to determine a more preferred device from the multiple devices to be matched as the target device. The optimal judgment rules include distance range and service attributes.

[0045] In the above implementation process, the service function of each access device is obtained based on the physical model corresponding to the device, and the device to be matched is determined from the access devices based on the service function requirements and the service function of the access device. The above solution uses the service function of the access device as the granularity for determining the target device, that is, the physical model is used in advance to obtain the service function corresponding to each device, and the device linkage operation is carried out according to the service function of the device, making full use of the service capabilities of each device and improving the resource utilization rate of the Internet of Things device. This improves the existing technology that uses a single device as the minimum granularity for Internet of Things service management. When performing Internet of Things device linkage, it is difficult to match the Internet of Things device with its service capability, resulting in a large amount of waste of device service function resources. At the same time, since there is no need to manually manage the service function of each device, the efficiency of device configuration is improved.

[0046] See Figure 2 The schematic diagram of the structure of the physical model provided by the embodiment of the present application is shown.

[0047] Optionally, in an embodiment of the present application, before determining the device to be matched from the access device based on the service function requirements and the service functions of the access device, the method also includes: formatting the service functions of the access device to obtain a physical model of the access device; the physical model includes a physical model identifier; based on the physical model of the access device, obtaining the service function corresponding to the access device; the service function includes a service function identifier; and the physical model identifier is associated with the corresponding service function identifier.

[0048] In practical implementation, the Internet of Things (IoT) can be understood as a data model that defines devices for cloud platforms. Its role is to provide standardized interfaces and digitize devices. The object model includes three functional elements: attributes, events, and commands. Each attribute, event, and command can correspond to a service function.

[0049] Attributes describe a device's operational state and are both readable and writable, such as the temperature and humidity attributes of environmental monitoring equipment. Events are information, alarms, and faults generated by a device during operation. An event can contain multiple output parameters. Unlike attributes, events cannot be set. Commands, also known as actions, are capabilities or methods that can be invoked on a device. In specific implementations, service functions can be formatted using different data types, including Boolean, integer, string, and floating-point types.

[0050] It is understandable that devices with the same service functions or features may correspond to the same object model, and each object model has a unique object model identifier.

[0051] After obtaining the object model corresponding to the access device, the service functions corresponding to the access device are obtained based on the object model of the access device. Specifically, for example, the parameters representing the formatted representation of device attributes, events, and commands in the object model are marked and defined as common service names in user business applications, such as parameter reading, opening and closing, service actions, etc. That is, the service commands in the object model are extracted and concretely defined as parameters corresponding to the service functions that can be recognized by the user. The same service function will be assigned a unique and non-repetitive service function identifier, and the object model identifier will be associated with the corresponding service function identifier. After the association, the service function defined in the object model can be found through the object model identifier.

[0052] In this implementation, the object model describes the device's services, attributes, and commands in a unified format. By decomposing the service functions defined in the object model, the corresponding service functions of the connected device are obtained, improving resource utilization of IoT devices. This allows managers to fully utilize device capabilities without having to learn specialized device parameter knowledge, improving management efficiency and convenience.

[0053] See Figure 3 The diagram shows the structure of the Internet of Things platform provided by the embodiment of the present application.

[0054] Optionally, in an embodiment of the present application, before determining the device to be matched from the access device based on the service function requirements and the service functions of the access device, the method also includes: connecting the device to be accessed to the Internet of Things platform, and performing identity authentication and access configuration to obtain the access device; the access device includes an access device identifier; and the access device identifier is associated with the corresponding object model identifier.

[0055] In practical implementation, the IoT platform maps physical devices in the physical world to the digital world. For a specific IoT device to be digitized, it must first be able to connect to the cloud, either directly or indirectly. In traditional internet scenarios, this access is primarily through apps (applications) and the web (World Wide Web).

[0056] Connect the device to the IoT platform and complete the device's identity authentication and IoT access configuration. This configuration includes the IoT and network configuration for the device. Specifically, the device data is uploaded through the gateway's channel. Using a pre-defined network protocol, the device data is sent to the cloud as the payload of the gateway's report. The server then subscribes to receive the data.

[0057] The access device connected to the Internet of Things platform has a unique access device identifier. By associating the access device identifier with the corresponding object model identifier, and associating the object model identifier with the corresponding service function identifier, the access device can be disassembled into a set of one or more corresponding service functions.

[0058] In the above implementation process, the access device is obtained by connecting the device to be connected to the IoT platform. The access device includes an access device identifier. By associating the access device identifier with the corresponding object model identifier, and then associating the object model identifier with the corresponding service function identifier, the access device can be disassembled into a set of one or more corresponding service functions. Through more fine-grained device resource management, resource utilization and configuration efficiency are improved.

[0059] like Figure 3 As shown, the access device identifier is associated with the corresponding object model identifier, and the object model identifier is associated with the corresponding service function identifier. Based on the device linkage policy configuration, service functions, and the business attributes of the device, devices that meet the service functions are screened, and the matching degree of these devices is calculated to determine the target device. The target device is then called through the IoT service device to provide the corresponding service.

[0060] Optionally, in an embodiment of the present application, the device linkage rules also include distance range requirements and attribute preference rules; determining the target device from the devices to be matched includes: determining the device to be confirmed that meets the distance range requirements from the devices to be matched based on the distance range requirements; obtaining the matching degree of the device to be confirmed based on the attribute preference rules; and determining the target device from the devices to be confirmed based on the matching degree.

[0061] In the specific implementation process, the matching device is the device that meets the service function requirements among the access devices. The device that meets the distance range requirements and attribute preference rules can be further selected as the target device from the matching device. The attribute preference rules include distance priority, parameter accuracy, upper-level device priority, fixed location priority, and / or device idle priority.

[0062] When a device is connected to the IoT and configured, each device's service attributes are configured, including its geographic location, service cascade relationship, fixed / mobile nature, and whether it is platform-shared. Users configure device linkage rules based on actual business needs. This allows the IoT platform to select target devices based on the service function requirements, distance range requirements, and attribute optimization rules in the device linkage rules, and then drive the target devices to provide services.

[0063] For example, after obtaining a device to be matched, the system identifies a device from the list of devices that meets the distance range requirement based on the device's geographic location parameters and the distance range requirement in the device linkage rules. A parameter request is sent to the device to be matched, and service attribute parameters sent by the device are received. Based on the service attribute parameters and the attribute preference rules, a matching degree for the device to be matched is obtained. The matching degree can be, for example, a matching score or a matching ranking. Based on the matching degree, a target device is identified from the list of devices to be matched, for example, the device with the highest matching score or the highest matching ranking is selected as the target device.

[0064] In one possible implementation, device linkage rules can be configured through a rule engine. A rule engine (BRMS) is a business rule management system that separates device linkage rules from applications, uses predefined semantic modules to write device linkage rules, and configures and manages them when needed.

[0065] In the above implementation process, by flexibly configuring the distance range requirements and attribute optimization rules in the device linkage rules, the target device that meets the actual needs can be determined from the devices to be matched, the service needs can be met, the service functions of the device can be fully utilized, and the accuracy of determining the target device can be improved.

[0066] Optionally, in an embodiment of the present application, the matching degree of the device to be confirmed is obtained based on the attribute optimization rule, including: sending a parameter request to the device to be confirmed, and obtaining the business attribute parameters returned by the device to be confirmed; determining the weight of each business attribute based on the attribute optimization rule; and calculating the matching degree of the device to be confirmed based on the business attribute parameters and the weight corresponding to each business attribute.

[0067] In the specific implementation process, the attribute preference rule includes at least one service attribute from the group consisting of distance priority, parameter accuracy, upper-level device priority, fixed location priority, and device idle priority. If the attribute preference rule includes multiple service attributes, each service attribute needs to be ranked according to its importance. The ranking of the multiple service attributes is then used to determine the weight of each service attribute. If the attribute preference rule includes a single service attribute, the weight of that service attribute is set to 1.

[0068] For example, if the attribute preference rule includes a fixed location priority, the device with a fixed location is selected as the target device, and the location parameter is set to 1. The service attribute parameters returned by the device to be confirmed are obtained, and the device with the location parameter in the fixed location is selected as the target device.

[0069] If the attribute preference rule includes multiple business attributes listed above, the multiple business attributes can be ranked according to their importance. For example, if the attribute preference rule includes device idle priority, fixed location priority, and parameter accuracy, where device idle priority is ranked first, fixed location priority is ranked second, and parameter accuracy is ranked third, a weighting algorithm is used to determine the weights of the three business attributes: device idle priority, fixed location priority, and parameter accuracy.

[0070] As an implementation method, the Hua Luogeng optimization method can be used to obtain the weight of each business attribute according to the ranking of the business attributes. For details, see the following formula:

[0071] When x = 1, F(x) = 0.618;

[0072] When 1>x>n, F(x)=0.618*(1-sum(F1:F(x-1)));

[0073] When x=n, F(x)=1-sum(F1:F(x-1)

[0074] Where x is the ranking of the business attributes; F(x) is the weight of the business attributes.

[0075] According to the formula, the weight of device idle priority is 0.618, the weight of fixed position priority is 0.2361, and the weight of parameter accuracy is 0.1459.

[0076] Obtain the device idle parameter, location parameter, and accuracy parameter from the service attribute parameters returned by the device to be confirmed. Multiply the service attribute parameters by the weight of the service attribute corresponding to the service attribute parameter, and add the products to obtain the matching degree of the device to be confirmed.

[0077] For example, the devices to be confirmed include device A, device B, and device C. Device A's idle parameter, location parameter, and precision parameter are A1, A2, and A2, respectively. Device B's idle parameter, location parameter, and precision parameter are B1, B2, and B2, respectively. Device C's idle parameter, location parameter, and precision parameter are C1, C2, and C2, respectively. Device A's matching degree = A1*0.618 + A2*0.2361 + A3*0.1459. Device B's matching degree = B1*0.618 + B2*0.2361 + B3*0.1459. Device C's matching degree = C1*0.618 + C2*0.2361 + C3*0.1459.

[0078] It should be noted that if the business attribute parameters returned by the device to be confirmed are non-numeric parameters, they will be converted into calculable numerical values; for business attributes that cannot be quantified, they will be mapped through data dictionary parameters, for example, converting "yes" to 1 and "no" to 0, to obtain the corresponding numerical values ​​of the business attribute parameters.

[0079] In the above implementation process, the matching degree of each pending device is calculated using the service attribute parameters and the weight corresponding to each service attribute. Based on the matching degree of each pending device, the device with the highest matching degree is selected as the target device, fully utilizing the attribute resources of each pending device and improving resource utilization.

[0080] Optionally, in an embodiment of the present application, after determining the target device from the devices to be matched, the method further includes: sending an execution command to the target device so that the target device executes the execution command; receiving the execution result sent by the target device; if the execution result indicates that the service is not completed, re-determining the target device based on the matching degree.

[0081] In the specific implementation process: After determining the target device, send an execution command to the target device. After receiving the execution command, the target device executes the command and generates an execution result. The execution result sent by the target device is received, and the execution result can include execution success, execution failure, or execution timeout.

[0082] If the execution result indicates an incomplete service, such as an execution failure or execution timeout, the target device is re-determined based on the matching degree. For example, if the execution result indicates an execution failure, the target device is re-determined based on the matching degree, such as selecting the second-highest matching device as the target device, and sending the execution command to the re-determined target device. If the execution result indicates an execution timeout, the execution command can be re-sent to the target device, or a new target device can be determined and the execution command sent to it.

[0083] It is understandable that if the execution result returned by the re-determined target device still indicates an uncompleted service, the target device is re-determined based on the matching degree until the execution result indicates a completed service.

[0084] In the aforementioned implementation process, if a traditional IoT device linkage strategy fails, there's usually no remedial action, requiring a re-implementation of the IoT device linkage strategy to determine the target device. By calculating the matching degree for the devices to be confirmed that meet the device linkage rules, we avoid having to recalculate the matching devices after a service failure. Instead, we can directly re-determine the target device based on the matching degree, improving service stability and the probability of successful execution.

[0085] Optionally, in an embodiment of the present application, obtaining the device linkage rule includes: determining whether the Internet of Things system meets a pre-configured rule triggering condition; if the rule triggering condition is met, obtaining the device linkage rule.

[0086] In the specific implementation process: Continuing with the above embodiment, the rule engine can also configure rule trigger conditions corresponding to device linkage rules. Rule trigger conditions are used to determine whether to execute the action determined by the IoT device. Rule trigger conditions can include object model parameters, device parameters, timer triggers, and business trigger rules.

[0087] In the above implementation process, when the rule triggering conditions are met, the Internet of Things device determination method is executed to realize the linkage of Internet of Things devices and improve the stability of the device linkage rules.

[0088] See Figure 4 The business process diagram provided by the embodiment of the present application is shown.

[0089] In an optional embodiment, after a linkage rule is triggered, available devices (i.e., devices to be matched) are screened based on the service function requirements. The IoT service device queries the location of each device to be matched. The device to be matched transmits its location back to the IoT service device, which then returns the location to the device linkage rule engine.

[0090] Based on the distance range requirements, the device linkage rules engine identifies the devices to be confirmed that meet the distance range requirements from the matching devices. It then queries the service attribute parameters of the devices to be confirmed through the IoT service device. Based on the service attribute parameters and the attribute optimization rules, it determines the matching degree of the devices to be confirmed and generates a device service queue, which contains the ranking of each device to be confirmed.

[0091] The IoT service device drives the first-ranked device to complete the service and obtain the completion result and status. Based on the completion result and status, it is determined whether the service is completed. If it is completed, the task is terminated. If the service is not completed, other devices in the queue are driven until the task is completed.

[0092] See Figure 5 The physical model association diagram provided by the embodiment of the present application is shown.

[0093] The object model extracts the service capabilities of IoT devices and obtains the corresponding service function library. Configure trigger conditions, required service capabilities, and regional scopes in device linkage rules. Configure the associated object model and corresponding business attributes for IoT devices. Configure business attribute priority conditions based on the business attribute library and device linkage rules.

[0094] See Figure 6The schematic diagram of the hardware framework of the Internet of Things platform provided by the embodiment of the present application is shown. The Internet of Things service device is connected to the Internet of Things platform through the network and a certain network protocol, and the Internet of Things service device is used to manage multiple Internet of Things devices.

[0095] See Figure 7 FIG2 is a schematic diagram of an Internet of Things service device provided by an embodiment of the present application. The Internet of Things service device includes a network communication device, a processor, and a driving device.

[0096] See Figure 8 The schematic diagram of the structure of the device for determining an IoT device provided in an embodiment of the present application is shown; the embodiment of the present application provides an IoT device determination device 200, comprising:

[0097] Acquisition module 210, for obtaining device linkage rules; device linkage rules include service function requirements;

[0098] Matching module 220, configured to determine a device to be matched from the access devices based on the service function requirements and the service functions of the access devices; wherein the service functions of the access devices are obtained based on the physical model corresponding to the devices;

[0099] The determination module 230 is configured to determine a target device from the devices to be matched.

[0100] Optionally, in an embodiment of the present application, the Internet of Things device determination device also includes: a service function splitting module, which is used to format the service function of the access device and obtain the physical model of the access device; the physical model includes a physical model identifier; according to the physical model of the access device, the service function corresponding to the access device is obtained; the service function includes a service function identifier; the physical model identifier is associated with the corresponding service function identifier.

[0101] Optionally, in an embodiment of the present application, the Internet of Things device determination device and the access platform module are used to connect the device to be accessed to the Internet of Things platform, and perform identity authentication and access configuration to obtain the access device; the access device includes an access device identifier; the access device identifier is associated with the corresponding object model identifier.

[0102] Optionally, in an embodiment of the present application, the device linkage rules also include distance range requirements and attribute preference rules; the Internet of Things device determination device, determination module 230, is specifically used to determine, based on the distance range requirements, the device to be confirmed that meets the distance range requirements from the devices to be matched; based on the attribute preference rules, obtain the matching degree of the device to be confirmed; and based on the matching degree, determine the target device from the device to be confirmed.

[0103] Optionally, in an embodiment of the present application, the IoT device determination device, determination module 230, is further used to send a parameter request to the device to be confirmed to obtain the business attribute parameters returned by the device to be confirmed; based on the attribute preference rule, determine the weight of each business attribute; and calculate the matching degree of the device to be confirmed based on the business attribute parameters and the weight corresponding to each of the business attributes.

[0104] Optionally, in an embodiment of the present application, the IoT device determination device and the execution processing module are used to send an execution command to the target device so that the target device executes the execution command; receive the execution result sent by the target device; if the execution result indicates that the service is not completed, the target device is re-determined according to the matching degree.

[0105] Optionally, in an embodiment of the present application, the IoT device determination device, the acquisition module 210, is further used to determine whether the IoT system meets a pre-configured rule triggering condition; if the rule triggering condition is met, the device linkage rule is obtained.

[0106] It should be understood that the device corresponds to the above-mentioned embodiment of the method for determining an IoT device and can perform each step involved in the above-mentioned method embodiment. The specific functions of the device can be found in the description above. To avoid repetition, a detailed description is omitted here. The device includes at least one software function module that can be stored in a memory in the form of software or firmware or fixed in the operating system (OS) of the device.

[0107] See Figure 9 The electronic device 300 provided in the embodiment of the present application includes a processor 310 and a memory 320, wherein the memory 320 stores machine-readable instructions executable by the processor 310, and when the machine-readable instructions are executed by the processor 310, the method described above is performed.

[0108] An embodiment of the present application further provides a storage medium, on which a computer program is stored. When the computer program is run by a processor, the above method is executed.

[0109] Among them, the storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0110] In the several embodiments provided in the embodiments of the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architectures, functions, and operations of the devices, methods, and computer program products according to the multiple embodiments of the embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment, or a portion of code, and the module, program segment, or a portion of code contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions marked in the boxes can also occur in a different order than the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or can be implemented using a combination of dedicated hardware and computer instructions.

[0111] In addition, the functional modules in each embodiment of the present application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0112] The above description is only an optional implementation method of the embodiment of the present application, but the protection scope of the embodiment of the present application is not limited to this. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in the embodiment of the present application, and they should all be covered by the protection scope of the embodiment of the present application.

Claims

1. A method for determining an Internet of Things device, characterized in that: include: Obtaining device linkage rules; the device linkage rules include service function requirements; Determine a device to be matched from the access device according to the service function requirements and the service functions of the access device; wherein the service functions of the access device are obtained according to the physical model corresponding to the device; and decompose the access device into a corresponding service function or a set of multiple service functions through the physical model; Determine a target device from the devices to be matched; The device linkage rule also includes a distance range requirement and an attribute preference rule; determining a target device from the devices to be matched includes: determining a device to be confirmed that meets the distance range requirement from the devices to be matched based on the distance range requirement; obtaining a matching degree of the device to be confirmed based on the attribute preference rule; and determining a target device from the devices to be confirmed based on the matching degree; the attribute preference rule includes at least one service attribute of distance priority, parameter accuracy, upper-level device priority, fixed location priority, and device idle priority; Based on the attribute optimization rule, the matching degree of the device to be confirmed is obtained, including: sending a parameter request to the device to be confirmed to obtain the business attribute parameters returned by the device to be confirmed; based on the attribute optimization rule, determining the weight of each business attribute; and calculating the matching degree of the device to be confirmed according to the business attribute parameters and the weight corresponding to each of the business attributes.

2. The method according to claim 1, characterized in that Before determining a device to be matched from the access device according to the service function requirement and the service function of the access device, the method further includes: Formatting the service function of the access device to obtain a physical model of the access device; the physical model includes a physical model identifier; According to the object model of the access device, a service function corresponding to the access device is obtained; the service function includes a service function identifier; the object model identifier is associated with the corresponding service function identifier.

3. The method according to claim 2, characterized in that Before determining a device to be matched from the access device according to the service function requirement and the service function of the access device, the method further includes: The device to be accessed is connected to the Internet of Things platform, and identity authentication and access configuration are performed to obtain the access device; the access device includes an access device identifier; the access device identifier is associated with the corresponding object model identifier.

4. The method according to claim 1, wherein After determining the target device from the devices to be matched, the method further includes: Sending an execution command to the target device so that the target device executes the execution command; receiving an execution result sent by the target device; If the execution result indicates that the service is not completed, the target device is re-determined based on the matching degree.

5. The method according to any one of claims 1 to 4, characterized in that: The obtaining of the device linkage rules includes: Determine whether the IoT system meets the pre-configured rule triggering conditions; If the rule triggering condition is met, the device linkage rule is obtained.

6. An IoT device identification device, characterized in that: include: An acquisition module, configured to obtain device linkage rules, wherein the device linkage rules include service function requirements; a matching module, configured to determine a device to be matched from the access device according to the service function requirement and the service function of the access device; wherein the service function of the access device is obtained according to the physical model corresponding to the device; A determination module, configured to determine a target device from the devices to be matched; The device linkage rules also include a distance range requirement and an attribute preference rule; the determination module is configured to determine, from the devices to be matched, a device that meets the distance range requirement based on the distance range requirement; obtain a matching degree of the device to be matched based on the attribute preference rule; and determine a target device from the devices to be matched based on the matching degree; the attribute preference rule includes at least one service attribute selected from the group consisting of distance priority, parameter accuracy, upper-level device priority, fixed location priority, and device idle priority; Send a parameter request to the device to be confirmed to obtain the service attribute parameters returned by the device to be confirmed; determine the weight of each service attribute based on the attribute optimization rule; and calculate the matching degree of the device to be confirmed based on the service attribute parameters and the weight corresponding to each service attribute.

7. An electronic device, characterized in that: include: A processor and a memory, wherein the memory stores machine-readable instructions executable by the processor, and when the machine-readable instructions are executed by the processor, the method according to any one of claims 1 to 5 is performed.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is executed.