CN108848159A - A kind of internet of things equipment interoperability dispatching method - Google Patents

Abstract

The invention discloses a kind of internet of things equipment interoperability dispatching methods, it is related to the internet of things field based on virtual resource, it is incompatible to solve to be difficult to meet equipment isomery when the Internet of things system under the prior art realizes equipment interoperability, and existing equipment interoperates mostly to start with from top layer standard or vertical field and be difficult to aiming at the problem that realizing horizontal equipment interoperability, the present invention proposes a kind of unified resource representation structure to internet of things equipment and physical equipment is converted to corresponding virtual unit resource in logic, virtual unit resource based on formation, propose the interactive mode for the scheduling that interoperates between two kinds of resources, passive type interoperability scheduling is realized by the way that notice is subscribed to and received to specified asset creation, the active operation scheduling of response realization is requested and obtained by sending to specified resource, equipment interoperability is realized by the operation of resource level.

Description

A method for interoperating scheduling of Internet of Things devices

technical field

The invention relates to the field of the Internet of Things based on virtual resources, in particular to a method for scheduling interoperation of Internet of Things devices.

Background technique

The Internet of Things (IoT) is an ubiquitous network of physical objects, virtual objects, and sensing, computing, and communication capabilities. The initial vision of the Internet of Things is to establish a hyperlinked global ecosystem, through the deployment of physical devices, communication networks, etc., to achieve interactive communication between "things" and "things", so as to build an ecosystem of connected things. To provide people with a more convenient and intelligent production and living environment. Among them, in order to realize the communication between "things" and "things", the key part is to realize the interoperability scheduling between IoT devices, and provide interoperability solutions between devices that need to be interoperable in a reasonable and effective way. So as to support the realization of object interaction.

However, in view of the large number, incompatibility, and wide distribution of devices deployed in the IoT system, it is difficult to achieve interoperability among heterogeneous devices due to different data formats and communication protocols, and it is difficult to seamlessly integrate new devices. into existing IoT systems. At present, many IoT researchers and industry leaders have conducted relevant research on the interoperability of IoT devices. Generally speaking, the current research mainly focuses on the following aspects:

1. Start with standards and provide equipment interoperability solutions by formulating unified industry specifications, including standards such as the Open Connectivity Foundation (OCF), the OPC Foundation, and the Machine Automation and Control Organization (OMAC) from the early Open Interconnection Alliance organize.

2. Starting from the vertical field, realize device interoperability for a single or isolated application, which has the nature of "one type, one discussion", and solves device interoperability under limited application conditions.

3. Starting from the communication network and hardware, according to the different communication protocols used by heterogeneous devices, operators deploy multi-vendor infrastructure in their networks to support the realization of device interoperability from the communication level.

However, some problems can indeed be solved through standardization, but it takes a very long time for the standards to be implemented, solutions in the vertical field are not applicable, and the interoperability that focuses on communication and hardware compatibility will gradually shift to software compatibility. Therefore, through the analysis of existing research, it can be found that in order to realize the interoperability scheduling of IoT devices, there are the following requirements:

It can meet the heterogeneity of devices, without considering the different data structures used by different devices, and can also realize device interoperability;

Device interoperability in the horizontal field can be realized without being limited to the specified field;

It can provide solutions for data interoperability according to device interaction requirements.

Aiming at the problems and demands raised above, some solutions have been proposed, such as OCF IoT interoperability standard, and a mobile multi-technology gateway technology to realize IoT interoperability.

Among them, the OCF standard, through the combination of specification, open source implementation and certification, can integrate participants in all links of the Internet of Things industry chain into it, so as to build an open ecosystem and realize interoperability between devices. However, this top-level standard specification only provides the basic implementation architecture, without a more detailed design for the specific implementation of each part, and there is still a long way to go before the close integration of standard specifications and practical applications. In addition, although the OCF standard provides equipment certification specifications, in the current OCF certification test consisting of compliance testing and interoperability testing, only compliance testing is available, and interoperability testing, which is crucial to supporting the realization of equipment interoperability, does not Realization, and most of the test equipment currently uses a wired form, which is difficult to meet the wireless communication environment of the Internet of Things.

In the device interoperability solution with the IoT gateway as the core of the mobile multi-technology gateway that realizes the interoperability of the Internet of Things, all devices are centrally connected to the gateway through wireless WIFI, Bluetooth, H3G or other communication methods. Interoperability relies heavily on the data collection and processing capabilities of the central gateway. At the same time, since the IoT gateway implemented by this technology is based on a smartphone, it is limited by the battery capacity and service life of the phone itself, which will greatly affect the interoperability of devices. Only when the power of the mobile phone is sufficient and the effective use of different communication interfaces can be maintained normally, can the interoperability requirements of devices be better met.

Contents of the invention

The purpose of the present invention is: in order to solve the difficulty in satisfying the heterogeneous incompatibility of equipment when implementing equipment interoperability in the Internet of Things system in the prior art, and the existing equipment interoperability mostly starts from the top-level standard or vertical field, and it is difficult to achieve horizontal equipment interoperability. For the problem of operation, the present invention provides an interoperability scheduling method for Internet of Things devices, and proposes a unified resource representation structure for Internet of Things devices to convert physical devices into logically corresponding virtual device resources, based on the formed virtual device resources , and proposed two interaction modes for interoperable scheduling between resources. Passive interoperable scheduling is realized by creating subscriptions to specified resources and receiving notifications. Active scheduling is realized by sending requests to specified resources and obtaining responses. Device interoperability.

The technical scheme that the present invention adopts is as follows:

A method for scheduling interoperability of Internet of Things devices, comprising the following steps:

S1: Represent all devices that need to be connected to the IoT system in a resource form, and establish a resource representation structure model;

S2: Based on the resource representation structure model obtained in S1, through basic resource operations, interactive scheduling between resources is realized.

Further, the resource representation structure model is a tree structure, including root resource root, attribute resource attribute, data resource data, entity resource entity, instance resource instance and subscription resource subscription, and the root resource root in the tree structure is The root node, the instance resource attribute is a leaf node in the tree structure, the data resource data, the entity resource entity and the subscription resource subscription are child nodes in the tree structure, and the child nodes are mounted under the root node. Other types of child nodes and leaf nodes can be mounted under the child nodes, and the instance resource instance is mounted under the data resource data in the tree structure and directly acts as a leaf node.

The root resource root represents the root of the resource tree, for example, an intelligent community and an intelligent transportation platform can be the root resource;

Attribute resource attribute is used to describe the state of the resource, corresponding to the inherent attributes of the physical device including device name, model, technical parameters, etc., is a single attribute value, and belongs to the leaf node in the resource tree;

The data resource data is used to save the relevant data perceived by the resource or generated by the resource. It can include multiple data instances at different times, so it can be used to record the status and status changes of the resource system at different times. It is a resource Indicates an important part of the structure;

Entity resource entity, which means that this resource also includes sub-resources, which can include other types of resources above. For example, in an IoT system with the aircraft platform as the root resource, the various devices carried on the platform are physical resources;

The instance resource instance, mounted under the data resource, represents each specific resource instance in the data resource, and the instance resource can also be a leaf node in the resource tree;

Subscription resource subscription, which exists as a sub-resource of other resources, represents the subscription to this resource. By specifying the notification address notificationURI in it, it will be notified when the resource information changes.

Further, the basic resource operations in S2 include:

Resource creation Create: used to send creation requests to resources to create new resources;

Resource retrieval Retrieve: Used to query any attribute information of resources.

Further, the interaction scheduling between resources includes resource interaction based on subscription notification and resource interaction based on request response, and the resource interaction based on subscription notification implements subscription operation on resources by using subscription resource subscription.

Further, the subscription resource subscription also includes:

notificationURI attribute: used to record the URI that should be notified of the resource change result. The notificationURI attribute is a string list to ensure that one subscription request corresponds to multiple notification objects.

Further, the resource interaction based on subscription notification includes resource subscription and resource notification, and the process of resource subscription is as follows:

S211: the subscriber initiates a subscription request to create a subscription resource;

S212: Determine whether the resource can be subscribed, if not, the subscription fails, if so, enter the next step;

S213: Determine whether the subscriber has permission to access, if not, the subscription fails, if so, go to the next step;

S214: Determine whether the notificationURI attribute is consistent with the address of the subscriber. If they are consistent, enter the next step. If not, send a subscription confirmation request to the subscriber and wait for feedback. If the feedback result is confirmed to be inconsistent, the subscription fails. If the feedback result is If consistent, go to the next step;

S215: Call the resource creation method to create a subscription resource subscription under the subscribed resource. If the creation fails, the subscription fails. If the creation succeeds, the subscription succeeds.

Further, the resource notification method is as follows:

When the subscription resource changes, a message is sent to the subscription resource subscription, and when the subscription resource subscription receives the message, a notification is sent to the subscriber identified by the notificationURI attribute according to the subscription configuration policy.

Further, the request-response-based resource interaction process is as follows:

S221: The original resource initiates a resource retrieval Retrieve request to the target resource, and specifies the required resource information in the resource retrieval Retrieve request and forms a filter condition;

S222: After receiving the resource retrieval Retrieve request, the target resource obtains the filterUsage field, and judges whether the value of the filterUsage field is discovery, if not, the request fails, and if so, enters the next step;

S223: Determine whether the target resource has sub-resources, if not, the request fails, if so, compare all sub-resources with the filter conditions obtained in S221 in turn, if the filter conditions are met, add the resource information to the result list, If the filtering conditions are not met, continue to compare the next sub-resource until the comparison of all sub-resources is completed. After the comparison is completed, the final result list is formed, that is, a successful response to the resource request is formed.

Further, when the filter condition includes a limit on the number of response results, if the number of sub-resources satisfying the filter condition is greater than the limit, the filter will be stopped and the part of sub-resources that meet the condition will be returned, and the response result will be The tag response is incomplete.

In summary, owing to adopting above-mentioned technical scheme, the beneficial effect of the present invention is:

1. The present invention solves the problem of interoperability scheduling of a large number of heterogeneous devices in the Internet of Things system, organizes the information of Internet of Things devices according to a unified resource representation structure, can effectively shield the heterogeneity between devices, and supports the realization of horizontal device interoperability.

2. The present invention obtains virtual device resources corresponding to actual physical devices through a unified resource modeling method, and can form a virtual resource pool logically corresponding to the actual Internet of Things system, thereby realizing device scheduling by using basic operations among resources.

3. The present invention utilizes a resource interaction method based on subscription notifications, by creating subscriptions for specified resources and receiving notifications, and can implement passive interoperability scheduling between devices with data interaction requirements, thereby effectively realizing device interaction using resource operations.

4. Using the request-response-based resource interaction method, by sending a request to a specified resource and getting a response, it can meet the device interoperability scheduling with active data requirements, so as to effectively realize device interaction by resource operation.

5. The present invention overcomes the problem that the OCF standard can only design the basic structure at the top level and cannot combine each part in a more detailed manner, which is difficult for practical application, and realizes the purpose of horizontal device interoperability.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present invention more clearly, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention, and thus It should be regarded as a limitation on the scope, and those skilled in the art can also obtain other related drawings based on these drawings without creative work.

Fig. 1 is a block diagram of overall steps of the present invention;

Fig. 2 is a resource representation structure model diagram of the present invention;

Fig. 3 is a flowchart of resource subscription in the present invention;

Fig. 4 is a flow chart of resource notification in the present invention;

Fig. 5 is a flowchart of resource interaction based on request response in the present invention;

FIG. 6 is a description diagram of the device resource registration process of the present invention;

Fig. 7 is the device interoperation diagram based on request response between the access control switch of the present invention and the RFID card reader;

Fig. 8 is a device interoperation diagram based on subscription notification between smart lights and sensors in the present invention.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present invention, and are not intended to limit the present invention, that is, the described embodiments are only some of the embodiments of the present invention, but not all of the embodiments. The components of the embodiments of the invention generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations.

Accordingly, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely represents selected embodiments of the invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative efforts belong to the protection scope of the present invention.

It should be noted that relative terms such as the terms "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any relationship between these entities or operations. There is no such actual relationship or order between them. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements of or also include elements inherent in such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

As shown in Figure 1, a scheduling method for interoperability of IoT devices includes the following steps:

S1: Represent all devices that need to be connected to the IoT system in a resource form, and establish a resource representation structure model;

S2: Based on the resource representation structure model obtained in S1, through basic resource operations, interactive scheduling between resources is realized.

As shown in Figure 2, as a preferred implementation, the resource representation structure model is a tree structure, including root resource root, attribute resource attribute, data resource data, entity resource entity, instance resource instance and subscription resource subscription, The root resource root is the root node in the tree structure, the instance resource attribute is the leaf node in the tree structure, the data resource data, the entity resource entity and the subscription resource subscription are child nodes in the tree structure, and the Sub-nodes are mounted under the root node, and other types of sub-nodes and leaf nodes can be mounted under the sub-nodes, and the instance resource instance is mounted under the data resource data in the tree structure, directly acting as a leaf node.

The root resource root represents the root of the resource tree, for example, an intelligent community and an intelligent transportation platform can be the root resource;

Attribute resource attribute is used to describe the state of the resource, corresponding to the inherent attributes of the physical device including device name, model, technical parameters, etc., is a single attribute value, and belongs to the leaf node in the resource tree;

The data resource data is used to save the relevant data perceived by the resource or generated by the resource. It can include multiple data instances at different times, so it can be used to record the status and status changes of the resource system at different times. It is a resource Indicates an important part of the structure;

Entity resource entity, which means that this resource also includes sub-resources, which can include other types of resources above. For example, in an IoT system with the aircraft platform as the root resource, the various devices carried on the platform are physical resources;

The instance resource instance, mounted under the data resource, represents each specific resource instance in the data resource, and the instance resource can also be a leaf node in the resource tree;

Subscription resource subscription, which exists as a sub-resource of other resources, represents the subscription to this resource. By specifying the notification address notificationURI in it, it will be notified when the resource information changes.

The basic resource operations in S2 include:

Resource creation Create: used to send creation requests to resources to create new resources;

Resource retrieval Retrieve: Used to query any attribute information of resources.

As a preferred implementation manner, the basic resource operations may also include:

Resource update Update: used to update the attribute information of the resource;

Resource deletion Delete: Used to delete resources.

As a preferred implementation manner, the interaction scheduling between resources includes resource interaction based on subscription notification and resource interaction based on request response, and the resource interaction based on subscription notification implements subscription operation on resources by using subscription.

The resource interaction based on subscription notification is essentially a passive resource scheduling, which provides a mechanism for resource change monitoring and notification. One of the devices as a subscriber can subscribe to a certain (or some) device resources based on dependent data information, etc., the subscriber can tell the subscriber a notification address (URL), and tell the subscriber what to do by setting parameters In this case, a notification is initiated, and the status of the subscribed resource changes is carried in the notification information.

The subscription resource subscription includes various types of sub-resource attributes, including:

notificationURI attribute: used to record the URI that should be notified of the resource change result. The notificationURI attribute is a string list to ensure that one subscription request corresponds to multiple notification objects;

creationTime attribute: used to record the creation time of the subscription resource;

expirationTime attribute: used to record the longest time that the subscription resource exists, so as to control its timeliness;

rateLimit attribute: used to record the notification frequency, which is the notification interval or the event that triggers the notification.

As shown in Figure 3, as a preferred implementation, the resource interaction based on subscription notification includes resource subscription and resource notification, and the process of resource subscription is as follows:

S211: the subscriber initiates a subscription request to create a subscription resource;

S212: Determine whether the resource can be subscribed, if not, the subscription fails, if so, enter the next step;

S213: Determine whether the subscriber has permission to access, if not, the subscription fails, if so, go to the next step;

S214: Determine whether the notificationURI attribute is consistent with the address of the subscriber. If they are consistent, enter the next step. If not, send a subscription confirmation request to the subscriber and wait for feedback. If the feedback result is confirmed to be inconsistent, the subscription fails. If the feedback result is If consistent, go to the next step;

S215: Call the resource creation method to create a subscription resource subscription under the subscribed resource. If the creation fails, the subscription fails. If the creation succeeds, the subscription succeeds.

As shown in Figure 4, as a preferred implementation manner, the resource notification method is as follows:

When the subscription resource changes, a message is sent to the subscription resource subscription, and when the subscription resource subscription receives the message, a notification is sent to the subscriber identified by the notificationURI attribute according to the subscription configuration policy.

The resource interaction based on request/response is essentially a kind of proactive resource scheduling, in which a certain device resource actively initiates a resource request, searches for and obtains other required device resource information in the resource pool. The resource request needs to contain the address url of the target resource to be retrieved and the filter conditions. When the target resource receives the resource request, it searches its own attributes and sub-resources, returns resource information that meets the filter conditions, and successfully responds to the resource request.

As shown in Figure 5, as a preferred implementation manner, the request-response-based resource interaction process is as follows:

S221: The original resource initiates a resource retrieval Retrieve request to the target resource, and specifies the required resource information in the resource retrieval Retrieve request and forms a filter condition;

S222: After receiving the resource retrieval Retrieve request, the target resource obtains the filterUsage field, and judges whether the value of the filterUsage field is discovery, if not, the request fails, and if so, enters the next step;

S223: Determine whether the target resource has sub-resources, if not, the request fails, if so, compare all sub-resources with the filter conditions obtained in S221 in turn, if the filter conditions are met, add the resource information to the result list, If the filtering conditions are not met, continue to compare the next sub-resource until the comparison of all sub-resources is completed. After the comparison is completed, the final result list is formed, that is, a successful response to the resource request is formed.

As a preferred implementation, when the filter condition includes a limit on the number of response results, if the number of sub-resources meeting the filter condition is greater than the limit, then stop filtering and return this part of the sub-resources that meet the condition , while marking the response as incomplete in the response result.

The smart home is selected as an example below. Each device deployed in the environment will be registered to the smart home resource management system through resource creation, and a corresponding virtual device resource will be generated for each physical device. Among them, in order to provide users with a comfortable home life in an intelligent and convenient way, interactive scheduling will occur between some devices. Using the above two resource interaction methods can conveniently implement device interoperability scheduling. For example, by establishing a resource subscription relationship between the light sensor and the smart light, an effective light intensity basis can be provided for the switching operation of the smart light, thereby providing users with a suitable lighting environment. For another example, by establishing a resource request relationship between the access control switch and the RFID card reader, the access control switch can be opened when a qualified RFID code is read, thereby providing a safe home environment.

Example 1:

The description process of smart furniture device resource registration as shown in Figure 6:

1. The device deployed in the environment sends a resource creation request to the smart home resource management system;

2. After the system receives the creation request, it first judges whether the requesting device has the resource creation permission, and if it does not have the creation permission, it returns the creation failure to the device;

3. Otherwise, continue to judge whether the resource type specified in the resource request can be supported, and if the resource type is not supported, return creation failure;

4. Otherwise, execute the operation of creating a new resource, and assign a value to the corresponding type of read-only attribute according to the resource modeling method. If there is an error in the creation process, return resource creation failure;

5. Otherwise, after the resource creation operation is completed, add the parent resource ID, creation time and other information;

6. Finally, the device resource registration is returned successfully, and the resource instance corresponding to the device is obtained according to the resource structure defined in the device resource modeling;

7. Return the registration success to the device, and get the corresponding device resource.

Example 2:

As shown in Figure 7, the device interoperability between the access control switch and the RFID card reader based on the request response:

Between the devices that need active interoperability scheduling, according to the data information to be requested, resource requests are sent to the corresponding target resources, and responses are obtained, so as to obtain the required information. For example, after successfully registering through the device resource, there are access control switch resources and RFID card reader resources in the system, and the access control switch resource can obtain the RFID code of the RFID card reader resource by sending a resource request, and then execute the corresponding Switch operation, so as to realize the interoperability scheduling of access control switch and RFID card reader.

1. The access control switch resource sends a resource retrieval retrieve request to the RFID card reader resource, which specifies the RFID code attribute value for querying the RFID card reader resource. The request format is as follows:

Retrieve/smartHome/RFIDReader/? nm=RFIDCode&ty=instance&filterUsage=discovery

2. The RFID card reader resource receives the resource retrieval request, parses and obtains the filterUsage field, and its value is discovery, which requires a resource discovery operation;

3. Continue to parse the content contained in the request to obtain the RFIDReader resource under the root resource smartHome to be requested, and the instance resource named RFIDCode to be requested;

4. Since there are sub-resources under the RFIDReader resource, the resource whose name is RFIDCode is screened under its sub-resource;

5. Add the resource information found through screening and form a result list;

6. Return the result list containing the value of the corresponding instance of RFIDCode to the access control switch resource, so as to make a successful response to this request.

Example 3:

As shown in Figure 8, device interoperability between smart light resources and light sensor resources based on subscription and notification:

Between devices that require passive interoperability scheduling, according to the data information that needs to be subscribed between devices, create subscription-type resources to the corresponding target resources. When the data information changes, it will actively push it in the form of a message. For example, after the light sensor resources and smart light resources are formed through device registration, in order to autonomously and intelligently control the switch of the smart light according to the light intensity, there is an interoperable scheduling of devices between the light sensor and the smart light, and the smart light needs to be obtained in real time. The light intensity detected by the light sensor can intelligently control its own switch. Therefore, the smart light can subscribe to the light value of the light sensor, and when the indoor light change is captured by the light sensor, it will be pushed to the smart light in the form of a notification, thereby providing support for the intelligent control of the light.

1. The smart light resource sends a resource subscription request to the light sensor resource, that is, sends a create request to create a resource of subscription type under the light resource lightValue of the light sensor, and its name is smartLambLightValue, and the address of the notification is specified as the smart light resource;

The resource subscription request format is as follows:

Create/smartHome/lightSensor/lightValue? nm=smartLambLightValue&ty=subscription&notificationURI=/smartHome/smartLamb

2. After the light sensor resource receives the subscription request, it first judges that its lightValue resource can be subscribed and can only be accessed by the light resource;

3. Compare the address notificationURI to be notified in the subscription request, which is the smart light resource that sends the resource request. When the light value lightValue changes, it can be pushed correctly in the form of a notification;

4. Then execute the create operation, create a subresource of type subscription under the lightValue resource of the light sensor, and name it smartLambLightValue, indicating the subscription of the smart light to the lightValue resource instance;

5. When the external light changes and the instance value of the light intensity lightValue changes, send the changed light value to the smart light in the form of a notification;

6. The smart lamp resource receives the light change information from the light sensor and notifies success.

The above is only a preferred embodiment of the present invention. It should be pointed out that for those of ordinary skill in the art, some modifications and improvements can be made without departing from the concept of the present invention, and these all belong to the protection of the invention. scope.

Claims (9)

1. A dispatching method for interoperability of Internet of Things equipment, is characterized in that, comprises the following steps: S1: Represent all devices that need to be connected to the IoT system in a resource form, and establish a resource representation structure model; S2: Based on the resource representation structure model obtained in S1, through basic resource operations, interactive scheduling between resources is realized. 2. A method for scheduling interoperability between IoT devices according to claim 1, wherein the resource representation structure model is a tree structure, including a root resource root, an attribute resource attribute, a data resource data, and an entity resource entity , instance resource instance and subscription resource subscription, the root resource root is the root node in the tree structure, the instance resource attribute is the leaf node in the tree structure, data resource data, entity resource entity and subscription resource subscription are in the tree structure The child nodes in the tree structure are mounted under the root node. Other types of child nodes and leaf nodes can be mounted under the child nodes. The instance resource instance in the tree structure is mounted on the data Under the resource data, it directly acts as a leaf node. 3. A kind of Internet of Things device interoperability scheduling method according to claim 1, is characterized in that, the basic resource operation in the described S2 comprises: Resource creation Create: used to send creation requests to resources to create new resources; Resource retrieval Retrieve: Used to query any attribute information of resources. 4. A method for scheduling interoperability between IoT devices according to claim 2, wherein the interactive scheduling between resources includes resource interaction based on subscription notification and resource interaction based on request response, and the resource interaction based on subscription notification The resource interaction uses the subscription resource subscription to implement the resource subscription operation. 5. A method for scheduling interoperability between IoT devices according to claim 4, wherein the resource subscription further includes: notificationURI attribute: used to record the URI that should be notified of the resource change result. The notificationURI attribute is a string list to ensure that one subscription request corresponds to multiple notification objects. 6. A method for scheduling interoperability between IoT devices according to claim 5, wherein the resource interaction based on subscription notification includes resource subscription and resource notification, and the process of resource subscription is as follows: S211: the subscriber initiates a request to create a subscription resource subscription through resource creation Create; S212: Determine whether the resource can be subscribed, if not, the subscription fails, if so, enter the next step; S213: Determine whether the subscriber has permission to access, if not, the subscription fails, if so, go to the next step; S214: Determine whether the notificationURI attribute is consistent with the address of the subscriber. If they are consistent, enter the next step. If not, send a subscription confirmation request to the subscriber and wait for feedback. If the feedback result is confirmed to be inconsistent, the subscription fails. If the feedback result is If consistent, go to the next step; S215: Call the resource creation method to create a subscription resource subscription under the subscribed resource. If the creation fails, the subscription fails. If the creation succeeds, the subscription succeeds. 7. A method for scheduling interoperability between IoT devices according to claim 6, wherein the resource notification method is as follows: When the subscription resource changes, a message is sent to the subscription resource subscription, and when the subscription resource subscription receives the message, a notification is sent to the subscriber identified by the notificationURI attribute according to the subscription configuration policy. 8. A method for scheduling interoperability between IoT devices according to claim 4, wherein the resource interaction process based on request response is as follows: S221: The original resource initiates a resource retrieval Retrieve request to the target resource, and specifies the required resource information in the resource retrieval Retrieve request and forms a filter condition; S222: After receiving the resource retrieval Retrieve request, the target resource obtains the filterUsage field, and judges whether the value of the filterUsage field is discovery, if not, the request fails, and if so, enters the next step; S223: Determine whether the target resource has sub-resources, if not, the request fails, if so, compare all sub-resources with the filter conditions obtained in S221 in turn, if the filter conditions are met, add the resource information to the result list, If the filtering conditions are not met, continue to compare the next sub-resource until the comparison of all sub-resources is completed. After the comparison is completed, the final result list is formed, that is, a successful response to the resource request is formed. 9. A method for interoperating scheduling of IoT devices according to claim 8, wherein when the screening conditions include a limit on the number of response results, if the number of sub-resources meeting the screening conditions is greater than the number When the limit is reached, stop filtering and return the subresources that meet the conditions, and mark the response as incomplete in the response result.