Internet of things platform access equipment adaptation fast indexing and interaction method

Abstract

The invention provides an internet of things platform access device adaptive fast indexing and interaction method, and relates to the technical field of internet of things, the method comprises the following steps: S100, a user initiates a request for accessing a target sub-platform or entity, and the request of the user is transmitted to a service layer; s200, the service layer directly indexes to the target sub-platform or entity according to the equipment main body ID of the target sub-platform or entity, and forwards the request to the target sub-platform or entity; wherein the equipment main body ID consists of an equipment ID of the sub-platform or the entity and system IDs of all upper platforms of the sub-platform or the entity. According to the method, the target sub-platform or entity can be directly indexed according to the unique main body definition of the sub-platform or entity without mapping query of the platform, so that the target can be quickly indexed, the indexing efficiency is improved, and the dependence on layer data is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of Internet of Things, and in particular to a method for rapid indexing and interaction of Internet of Things platform access equipment adaptation. Background Art

[0002] The Internet of Things connects all objects to the Internet through information sensing devices, exchanges information, and realizes the mutual understanding of things, thereby achieving the goal of intelligent identification and management. Therefore, in terms of lower-level system access, the system needs to integrate various security systems and third-party platforms, such as monitoring systems, access control systems, alarm systems, etc., to achieve the integration and interaction of multiple systems. On this basis, as the core subject, the device must have universal adaptability and be able to quickly achieve the indexing goal. The existing indexing method is based on the database to save the description of the association between the parent and child systems, use the platform's unique ID for indexing, and the interface is based on the platform's unique ID operation. However, it cannot achieve the purpose of fast indexing. In the case of a multi-layer system, it is necessary to query and operate layer by layer; the efficiency is low, and cross-layer transmission requires one more query; local dependencies increase, and cross-layer transmission depends on the parent-child description information, otherwise the business closed loop cannot be completed. Summary of the invention

[0003] The purpose of the present invention is to provide a method for rapid indexing and interaction of IoT platform access device adaptation, aiming to achieve rapid indexing of targets, improve indexing efficiency, and reduce dependence on layer data. The specific technical solution is as follows: A method for quickly indexing device adaptation for an Internet of Things platform access, the method comprising the following steps: S100, the user initiates a request to access the target sub-platform or entity, and the user's request is passed to the service layer; S200. The service layer directly indexes the target sub-platform or entity according to the device body ID of the target sub-platform or entity, and forwards the request to the target sub-platform or entity; wherein the device body ID is composed of the device ID of the sub-platform or entity and the system IDs of all upper-level platforms of the sub-platform or entity.

[0004] Furthermore, the system ID is defined and described by a triplet of [platform protocol, access protocol, routing ID].

[0005] Furthermore, the device body ID also includes a protocol version, the protocol version and the device ID are connected by a protocol separator, the device ID and the upper layer system ID are connected by a protocol separator, and each system ID is connected by a platform separator.

[0006] Furthermore, the protocol version is used to identify the version number of the current protocol to ensure compatibility between different versions, and is a single character.

[0007] Furthermore, the protocol separator is used to separate data in each field for ease of parsing and is a single character.

[0008] Furthermore, the device ID is an identifier that uniquely identifies a device and is used to distinguish different devices. The system uses long or uuid, and the number of characters is less than or equal to 36.

[0009] Furthermore, the platform protocol is a type of protocol used to describe the interaction between a device or system and a platform, the access protocol is a communication protocol or method used to describe the device accessing the platform, and the routing ID is used to identify the data transmission path or target route within the system.

[0010] Furthermore, the platform protocol is a single character, the access protocol is a single character, and the number of characters in the routing ID is less than 12.

[0011] Furthermore, the platform separator is used to separate different platform fields in a multi-layer system to facilitate identification of protocol content of each layer of the platform, and is a single character.

[0012] The present invention also provides an Internet of Things platform interaction method, the method comprising the following steps: S1000, the main platform sends a request to access the sub-platform or entity function, and the request is processed by the protocol adaptation layer; S2000, the protocol adaptation layer directly requests the sub-platform or entity according to the device subject ID of the sub-platform or entity, without the need for storage layer routing; wherein the device subject ID is composed of the device ID of the sub-platform or entity t and the system IDs of all upper-layer platforms of the sub-platform or entity t; S3000, sub-platform or entity returns a functional response; S4000, the protocol adaptation layer receives the functional response of the sub-platform or entity and directly returns it to the main platform.

[0013] The invention provides a method for quick indexing and interaction of IoT platform access device adaptation, which has the following beneficial effects: (1) The indexing method of the present invention directly indexes the target sub-platform or entity according to the device subject ID of the target sub-platform or entity through the service layer, and forwards the request to the target sub-platform or entity, wherein the device subject ID is composed of the device ID of the sub-platform or entity and the system ID of all upper-layer platforms of the sub-platform or entity. It does not require a platform mapping query, and directly indexes the target sub-platform or entity according to the unique subject definition of the sub-platform or entity, thereby achieving rapid indexing of the target, improving indexing efficiency, and reducing dependence on layer data.

[0014] (2) The interactive method of the present invention is of great significance in the transformation and efficiency improvement of the original system. Since the device main body ID entity identifier already contains the sub-platform identifier and the sub-platform entity identifier, the sub-platform routing and the acquisition of the sub-platform entity identifier can be performed without additional information query, which can improve the request response rate and support a larger throughput. In addition, since the protocol adaptation layer does not need to store routing relationships and entity mapping relationships, it has less dependence on external components and can run independently without storage components, so it can be deployed in a lightweight manner to reduce costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is a schematic diagram of the current IoT access platform index; Figure 2 It is a flowchart of a method for quick indexing of an Internet of Things platform access device adaptation according to an embodiment of the present invention; Figure 3 A schematic diagram of adapting a fast index to an Internet of Things platform access device according to an embodiment of the present invention; Figure 4 A schematic diagram of a device subject ID according to an embodiment of the present invention; Figure 5 This is a schematic diagram of the current IoT platform interaction; Figure 6 A schematic diagram of a flow chart of an Internet of Things platform interaction method according to an embodiment of the present invention; Figure 7 The figure is a schematic diagram of the interaction of the Internet of Things platform according to an embodiment of the present invention. DETAILED DESCRIPTION

[0016] The following will be combined with the accompanying drawings provided by the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. According to the following description, the advantages and features of the present invention will be more clear. It should be noted that the accompanying drawings are all in a very simplified form and are not in precise proportions, which are only used to conveniently and clearly assist in explaining the purpose of the embodiments of the present invention.

[0017] In the description of the present invention, unless otherwise clearly stipulated and limited, the terms "connection" and "connected" should be interpreted in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0018] In the description of the present invention, terms such as "up", "down", "left", "right", "front", "back", "center", "horizontal", "vertical", "top", "bottom", "inside" and "outside" and other orientations or positional relationships are based on the orientations or positional relationships shown in the accompanying drawings and are only for the convenience of description and simplification of operation, rather than indicating or implying that the referred device or element must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present invention.

[0019] In the existing IoT, when users interact with sub-platforms or entities, they initiate requests, targeting the functions of the sub-platform or entity. Users access the service layer through requests, and this process requires layer-by-layer indexing to find the correct sub-platform or entity. Figure 1 As shown, the current indexing method for IoT access platforms is as follows: Step 1: User u initiates a request to the service layer s: User u's request will first be passed to the service layer s, which acts as a transit node and is responsible for receiving and forwarding the user's request.

[0020] Step 2: The service layer s forwards the request to the platform p: The service layer determines to which platform p among multiple platforms p1, p2, and p3 the request should be forwarded through known service rules or information. The known service rules or information may be, for example, device entity information, platform protocol, and the like.

[0021] Step 3: Platform p indexes the next sub-platform or entity t and forwards the request to the next sub-platform or entity t: After the service layer s forwards the request to the platform (p1, p2 or p3), the platform further indexes the next entity or sub-platform based on the required functionality. The platform will query the internal index to find the sub-platform or entity that matches the user request. For example, platform p1 may find sub-platform or entity t1, platform p2 will find t2, and so on. The platform layer relies on a mapping table and internal query mechanism to make decisions. For example: based on the device entity information and platform protocol information, query the access protocol and routing information.

[0022] The user's request will be forwarded to the specific sub-platform or entity (t1, t2, t3 or t4) obtained by the index. The sub-platform or entity is the level that ultimately provides the actual function. At this level, the target of the index search is a specific function or resource, and the user's request is processed specifically. Here, the sub-platform or entity (t1, t2, t3 or t4) will further process or return the result to the user u according to the specific function. For example: according to the access protocol and routing information, the entity t1 is retrieved and returned to the user u.

[0023] According to the index relationship of the prior art, when user u requests a function of a sub-platform or entity t1, the index request path is u ->s ->p->t1. In the above index design, as the platform becomes larger and larger and more and more sub-platforms or entities are connected, the main bottleneck of the platform lies in requesting sub-platform entity functions. Therefore, reasonable index design is particularly important.

[0024] The embodiment of the present invention provides a method for quickly indexing the access device of an Internet of Things platform. Figure 2 , 3 As shown, the following steps are included: S100, user u initiates a request to access the target sub-platform or entity t, and the request of user u is passed to the service layer s.

[0025] The service layer s is the main body of the index and is responsible for receiving and forwarding requests from user u.

[0026] S200. The service layer s directly indexes the target sub-platform or entity t according to the device body ID of the target sub-platform or entity t, and forwards the request to the target sub-platform or entity t; wherein the device body ID is composed of the device ID of the sub-platform or entity t and the system IDs of all upper-level platforms of the sub-platform or entity t.

[0027] For example, if the user's request target is sub-platform or entity t1, the combined node of sub-platform or entity t1 and all its upper-level platforms, i.e. t1+p1+s, will be used as an index subject. The service layer does not need a mapping query for platform p, but can directly index the target sub-platform or entity t1 based on the unique subject definition of the sub-platform or entity.

[0028] In an embodiment of the present invention, the service layer s directly indexes the target sub-platform or entity t according to the device subject ID of the target sub-platform or entity t, and forwards the request to the target sub-platform or entity t, wherein the device subject ID is composed of the device ID of the sub-platform or entity t and the system IDs of all upper-level platforms of the sub-platform or entity t. The mapping query of the platform may not be required, and the target sub-platform or entity may be directly indexed according to the unique subject definition of the sub-platform or entity, thereby realizing rapid indexing of the target, improving indexing efficiency, and reducing dependence on layer data.

[0029] The device ID itself has the uniqueness characteristic within the subsystem. The system ID is used across systems as a unique description of the system. Therefore, the uniqueness of the device + system is used to describe the uniqueness of the device in the device body definition.

[0030] In one embodiment, the system ID is defined and described by a triplet of [platform protocol, access protocol, routing ID].

[0031] The use of the [platform protocol, access protocol, routing id] triple across systems is a unique description of the system. Combined with the uniqueness of the device entity ID defined above, the system's triple information not only describes the uniqueness of the system, but also has routing information, so it can achieve the purpose of fast indexing. When the service layer u requests the function of the sub-platform or entity t, its index request path is u ->s->t, and its time complexity is O(1), while reducing the dependence on layer data.

[0032] In a preferred embodiment, see Figure 4 As shown, the device body ID also includes a protocol version. The protocol version and the device ID are connected by a protocol separator. The device ID and the upper-layer system ID are connected by a protocol separator. The system IDs are connected by a platform separator.

[0033] Specifically, the protocol version is used to identify the version number of the current protocol to ensure compatibility between different versions. It is generally in the form of numbers or letters, usually a single character, such as 1 or a.

[0034] The protocol separator is used to separate the data of each field for easy parsing. Common separators include comma (,), semicolon (;), pipe (|), etc. It is usually a single character, such as (|) or ( / ).

[0035] The device ID is an identifier that uniquely identifies a device and is used to distinguish different devices. It is usually a string of numbers or letters. Generally, the system uses long or uuid (Universally Unique Identifier) ​​format, with less than or equal to 36 characters.

[0036] The platform protocol is a protocol type used when describing the interaction between a device or system and the platform. It is usually in the form of numbers or letters, usually a single character, such as 1 or a.

[0037] The access protocol is used to describe the communication protocol or method when a device accesses the platform. It is usually in the form of numbers or letters, usually a single character, such as 1 or a.

[0038] The route ID is used to identify the data transmission path or target route within the system. It is generally the unique identification ID of the platform system, which is customized by the platform and usually less than 12 characters.

[0039] The platform separator is used to separate different platform fields in a multi-layer system to facilitate identification of protocol content on each layer of the platform. It is usually a single character, using special characters such as @ or $.

[0040] According to the device entity ID defined above, in the case of a 5-layer subsystem, the total number of characters is less than 114 and less than 128 bytes, which has strong universality.

[0041] According to the current indexing method of IoT access platform, refer to Figure 5 As shown, the working process of the existing IoT platform interaction method is as follows: 1. The main platform sends a request to the sub-platform entity function, and the request is processed by the protocol adaptation layer; 2. The protocol adaptation layer requests the storage service to obtain the mapping relationship between the sub-platform routing and the entity; 3. The storage service returns the sub-platform routing and entity mapping relationship; 4. The protocol adaptation layer requests the sub-platform based on the sub-platform routing and entity mapping relationship, and indexes to the specific sub-platform and entity functions; 5. The sub-platform entity function returns response information; 6. The protocol adaptation layer queries the storage service to obtain entity relationships based on the sub-platform entity function information; 7. The service layer returns the entity mapping relationship; 8. The protocol adaptation layer assembles and modifies the sub-platform entity function response according to the returned entity mapping relationship and returns it to the main platform.

[0042] In the existing IoT platform interaction methods, the original protocol adaptation layer relies heavily on storage services. Each request and response requires the intervention of the storage service, which greatly reduces the performance of platform interaction.

[0043] The embodiment of the present invention provides an Internet of Things platform interaction method, referring to Figure 6 , 7 As shown, the following steps are included: S1000, the main platform sends a request to access the sub-platform or entity function, and the request is processed by the protocol adaptation layer; S2000, the protocol adaptation layer directly requests the sub-platform or entity according to the device subject ID of the sub-platform or entity, without the need for storage layer routing; wherein the device subject ID is composed of the device ID of the sub-platform or entity and the system IDs of all upper-layer platforms of the sub-platform or entity; S3000, sub-platform or entity returns a functional response; S4000, the protocol adaptation layer receives the functional response of the sub-platform or entity and directly returns it to the main platform.

[0044] The above-mentioned interaction method of the embodiment of the present invention is of great significance in the transformation and efficiency improvement of the original system. Since the device main body ID entity identifier already contains the sub-platform identifier and the sub-platform entity identifier, the sub-platform routing and the acquisition of the sub-platform entity identifier can be performed without additional information query, which can improve the request response rate and support a larger throughput. In addition, since the protocol adaptation layer does not need to store routing relationships and entity mapping relationships, it has less dependence on external components and can run independently without storage components, which can be deployed in a lightweight manner to reduce costs.

[0045] Those skilled in the art should understand that the present invention can be implemented in many other specific forms without departing from the spirit and scope of the present invention. Based on the embodiments of the present invention, any changes and modifications made by ordinary technicians in the field of the present invention according to the above disclosure are within the scope of protection of the claims.

Claims

1. A method for rapid indexing of IoT platform access equipment adaptation, characterized in that: The method comprises the following steps: S100, the user initiates a request to access the target sub-platform or entity, and the user's request is passed to the service layer; S200. The service layer directly indexes the target sub-platform or entity according to the device body ID of the target sub-platform or entity, and forwards the request to the target sub-platform or entity; wherein the device body ID is composed of the device ID of the sub-platform or entity and the system IDs of all upper-level platforms of the sub-platform or entity.

2. The method for rapid indexing of IoT platform access equipment adaptation according to claim 1, characterized in that: The system ID is defined and described by the triplet of [platform protocol, access protocol, routing ID].

3. The method for rapid indexing of IoT platform access equipment according to claim 2, characterized in that: The device body ID also includes a protocol version. The protocol version and the device ID are connected via a protocol separator. The device ID and the upper layer system ID are connected via a protocol separator. The system IDs are connected via a platform separator.

4. The method for rapid indexing of IoT platform access equipment according to claim 3, characterized in that: The protocol version is used to identify the version number of the current protocol to ensure compatibility between different versions, and is a single character.

5. The method for rapid indexing of IoT platform access equipment adaptation according to claim 3, characterized in that: The protocol separator is used to separate data in each field for easy parsing and is a single character.

6. The method for rapid indexing of IoT platform access equipment adaptation according to claim 3, characterized in that: The device ID is an identifier that uniquely identifies a device and is used to distinguish different devices. The system uses long or uuid, and the number of characters is less than or equal to 36.

7. The method for rapid indexing of IoT platform access equipment adaptation according to claim 3, characterized in that: The platform protocol is the type of protocol used to describe the interaction between a device or system and a platform. The access protocol is the communication protocol or method used to describe the device's access to the platform. The routing ID is used to identify the data transmission path or target route within the system.

8. The method for rapid indexing of IoT platform access equipment adaptation according to claim 7, characterized in that: The platform protocol is a single character, the access protocol is a single character, and the routing ID has less than 12 characters.

9. The method for rapid indexing of IoT platform access equipment adaptation according to claim 3, characterized in that: The platform separator is used to separate different platform fields in a multi-layer system to facilitate identification of the protocol content of each layer of the platform. It is a single character.

10. An Internet of Things platform interaction method, characterized in that: The method comprises the following steps: S1000, the main platform sends a request to access the sub-platform or entity function, and the request is processed by the protocol adaptation layer; S2000, the protocol adaptation layer directly requests the sub-platform or entity according to the device subject ID of the sub-platform or entity, without the need for storage layer routing; wherein the device subject ID is composed of the device ID of the sub-platform or entity and the system IDs of all upper-layer platforms of the sub-platform or entity; S3000, sub-platform or entity returns a functional response; S4000, the protocol adaptation layer receives the functional response of the sub-platform or entity and directly returns it to the main platform.

Images