Device registration method and apparatus, electronic device, and storage medium

Abstract

The present disclosure relates to a device registration method and apparatus, an electronic device, and a storage medium. The method is applied to a cloud device, comprising: upon receiving a registration request from an edge device, obtaining device self-description information in the registration request, wherein the registration extension field of the device self-description information includes at least: a first version of the interface protocol between the edge device and the cloud device; when the first version and the second version are different, determining a corresponding registration response method based on the difference between the first version and the second version, wherein the second version is the version of the interface protocol between the cloud device and the edge device that is retained in the cloud device; and performing a registration response to the edge device based on the registration response method. The embodiments of the present disclosure can implement interface negotiation between the cloud and the edge.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a device registration method and apparatus, an electronic device, and a storage medium. Background Art

[0002] In IoT systems, there are a large number of edge devices / systems with data collection capabilities, providing data resources for the IoT system. In smart city-level IoT systems, the number of edge devices / systems may reach hundreds of thousands or even millions.

[0003] In related technologies, although a unified interface protocol can be developed for edge devices / systems, the data collected by edge devices often changes for businesses with large changes, newly connected businesses, or even completely new businesses and scenarios. The IoT system cannot perceive and adapt to these changes in a timely manner. Invalid collection of data by edge devices may occur, or the IoT system may be unable to recognize data and discard data, resulting in low efficiency of cloud-edge business collaboration and data collaboration. Summary of the Invention

[0004] The present disclosure proposes a technical solution for device registration.

[0005] According to one aspect of the present disclosure, a device registration method is provided, which is applied to a cloud device and includes:

[0006] Upon receiving a registration request from an edge device, obtain the device self-description information in the registration request, wherein the registration extension field of the device self-description information includes at least: a first version of the interface protocol between the edge device and the cloud device; in a case where the first version is different from the second version, determine a corresponding registration response method based on the difference between the first version and the second version, the second version being the interface protocol version between the cloud device and the edge device retained in the cloud device; and perform a registration response to the edge device based on the registration response method.

[0007] In one possible implementation, the version of the interface protocol includes a model version, and the corresponding registration response method is determined based on the difference between the first version and the second version, including: when the model version of the first version is lower than the model version of the second version, determining the registration response method includes: updating the model version of the edge device; wherein, the registration response to the edge device based on the registration response method includes: synchronizing the model version of the edge device so that the model version of the edge device is synchronized to the second version; and / or sending a registration response message to the edge device, and the response extension field of the registration response message includes: a field indicating that the model version of the edge device is to be updated.

[0008] In one possible implementation, the version of the interface protocol includes a model version, and the corresponding registration response method is determined based on the difference between the first version and the second version, including: when the model version of the first version is higher than the model version of the second version, determining the registration response method includes: the model version of the edge device to be confirmed; wherein, the registration response to the edge device based on the registration response method includes: creating a first processing flow for confirming the model version; in response to the rejection operation of the model version in the first processing flow, synchronizing the model version of the edge device so that the model version of the edge device is synchronized to the second version.

[0009] In a possible implementation, synchronizing the model version of the edge device includes: synchronizing the model version of the edge device through a preset business shadow synchronization interface.

[0010] In one possible implementation, the business shadow synchronization interface includes a configuration sending interface, a configuration response interface and a configuration status reporting interface, wherein the model version of the edge device is synchronized through the preset business shadow synchronization interface, including: sending the second version of the model in the model library of the cloud device to the edge device through the configuration sending interface; when the configuration response information of the edge device is received through the configuration response interface, determining that the edge device has received the second version of the model; when the configuration status information of the edge device is received through the configuration status reporting interface, determining that the model version of the edge device is synchronized to the second version.

[0011] In a possible implementation, the registration extension field further includes document information of the interface protocol, wherein the registering response to the edge device according to the registration response mode further includes:

[0012] In response to the acceptance operation of the model version in the first processing flow, the file synchronization interface is called according to the document information to obtain the description document of the interface protocol and the model corresponding to the first version from the edge device; based on the description document and the model corresponding to the first version, the model library of the cloud device is updated so that the model in the model library is updated to the first version.

[0013] In one possible implementation, the model library of the cloud device is updated based on the instruction document and the model corresponding to the first version, including: creating a second processing flow for developing and debugging the interface protocol based on the instruction document and the model corresponding to the first version; in response to the completion of debugging the second processing flow, updating the corresponding model in the model library to the model corresponding to the first version.

[0014] In a possible implementation, the registration extension field further includes a first data item list, and the version of the interface protocol includes a data item version, wherein determining the corresponding registration response mode according to the difference between the first version and the second version includes: when the data item version of the first version is different from the data item version of the second version, determining the registration response mode as: the data item list of the edge device to be confirmed;

[0015] Among them, the registration response to the edge device according to the registration response method includes: creating a third processing flow for confirming the first data item list; in response to the rejection operation of the first data item list in the third processing flow, sending a registration response message to the edge device, and the response extension field of the registration response message includes: a field indicating that the first data item list is rejected.

[0016] In one possible implementation, the registration response to the edge device according to the registration response method also includes: in response to the acceptance operation of the first data item list in the third processing flow, updating the data synchronization interface of the cloud device according to the first data item list, so that the cloud device obtains the data items corresponding to the first data item list through the updated data synchronization interface; and / or updating the database table of the cloud device according to the first data item list; and / or sending a registration response message to the edge device, and the response extension field of the registration response message includes: a field indicating that the first data item list is accepted.

[0017] In one possible implementation, updating the database table of the cloud device according to the first data item list includes: updating the database table of the cloud device through the library synchronization interface according to the first data item list, so that the corresponding data item version in the database table of the cloud device is updated to the first version.

[0018] In a possible implementation, the method further includes: upon receiving an alarm message regarding the interface protocol version of the edge device, calling a preset business shadow synchronization interface to synchronize the interface protocol version of the edge device.

[0019] In one possible implementation, the method further includes: when the first version is the same as the second version, sending a registration response message to the edge device, and the response extension field of the registration response message includes: a field indicating that the registration of the edge device is successful.

[0020] According to one aspect of the present disclosure, a device registration method is provided, which is applied to an edge device and includes:

[0021] When the registration conditions are met, a registration request is sent to the cloud device so that the cloud device responds with a registration, wherein the registration request includes device self-description information, and the registration extension field of the device self-description information includes: the first version of the interface protocol between the edge device and the cloud device, the first data item list and the document information of the interface protocol; when the registration response information of the cloud device is received, the response extension field of the registration response information is obtained; when the response extension field indicates that the registration is successful, a communication connection is established with the cloud device, wherein the registration conditions include any one of the following: the edge device is started, the edge device is restarted, the system of the edge device is updated, and the interface of the edge device is updated.

[0022] In a possible implementation, the version of the interface protocol includes a model version, and the method further includes:

[0023] When the response extension field indicates that the model version of the edge device is to be updated, a second version of the model is received from the cloud device from the preset business shadow synchronization interface; based on the second version of the model, the local model of the edge device is synchronized so that the model version of the edge device is synchronized to the second version.

[0024] According to one aspect of the present disclosure, a device registration apparatus is provided, which is applied to a cloud device and includes:

[0025] An information acquisition module is configured to, upon receiving a registration request from an edge device, acquire device self-description information in the registration request, wherein a registration extension field of the device self-description information includes at least: a first version of an interface protocol between the edge device and the cloud device;

[0026] a response mode determination module, configured to determine a corresponding registration response mode according to the difference between the first version and the second version when the first version and the second version are different, where the second version is the interface protocol version between the cloud device and the edge device retained in the cloud device;

[0027] The registration response module is used to perform a registration response to the edge device according to the registration response method.

[0028] In a possible implementation, the version of the interface protocol includes a model version, and the response mode determination module is configured to: when the model version of the first version is lower than the model version of the second version, determine the registration response mode including: updating the model version of the edge device;

[0029] Among them, the registration response module is used to: synchronize the model version of the edge device so that the model version of the edge device is synchronized to the second version; and / or send a registration response message to the edge device, and the response extension field of the registration response message includes: a field indicating that the model version of the edge device is to be updated.

[0030] In a possible implementation, the version of the interface protocol includes a model version, and the response mode determination module is configured to: when the model version of the first version is higher than the model version of the second version, determine the registration response mode including: to confirm the model version of the edge device;

[0031] Among them, the registration response module is used to: create a first processing flow for confirming the model version; in response to the rejection operation of the model version in the first processing flow, synchronize the model version of the edge device so that the model version of the edge device is synchronized to the second version.

[0032] In a possible implementation, the registration response module synchronizes the model version of the edge device, including: synchronizing the model version of the edge device through a preset business shadow synchronization interface.

[0033] In one possible implementation, the business shadow synchronization interface includes a configuration sending interface, a configuration response interface and a configuration status reporting interface, wherein the registration response module synchronizes the model version of the edge device through the preset business shadow synchronization interface, including: sending the second version of the model in the model library of the cloud device to the edge device through the configuration sending interface; when the configuration response information of the edge device is received through the configuration response interface, determining that the edge device has received the second version of the model; when the configuration status information of the edge device is received through the configuration status reporting interface, determining that the model version of the edge device is synchronized to the second version.

[0034] In one possible implementation, the registration extension field also includes document information of the interface protocol, wherein the registration response module is further used to: in response to the acceptance operation of the model version in the first processing flow, call the file synchronization interface according to the document information, and obtain the description document of the interface protocol and the model corresponding to the first version from the edge device; based on the description document and the model corresponding to the first version, update the model library of the cloud device so that the model of the model library is updated to the first version.

[0035] In one possible implementation, the registration response module updates the model library of the cloud device based on the description document and the model corresponding to the first version, including: creating a second processing flow for developing and debugging the interface protocol based on the description document and the model corresponding to the first version; in response to the completion of debugging the second processing flow, updating the corresponding model in the model library to the model corresponding to the first version.

[0036] In one possible implementation, the registration extension field also includes a first data item list, and the version of the interface protocol includes a data item version, wherein the response method determination module is used to: when the data item version of the first version is different from the data item version of the second version, determine the registration response method as: the data item list of the edge device to be confirmed; wherein the registration response module is used to: create a third processing flow for confirming the first data item list; in response to the rejection operation of the first data item list in the third processing flow, send a registration response message to the edge device, and the response extension field of the registration response message includes: a field indicating that the first data item list is rejected.

[0037] In one possible implementation, the registration response module is also used to: in response to the acceptance operation of the first data item list in the third processing flow, update the data synchronization interface of the cloud device according to the first data item list, so that the cloud device obtains the data items corresponding to the first data item list through the updated data synchronization interface; and / or update the database table of the cloud device according to the first data item list; and / or send a registration response message to the edge device, and the response extension field of the registration response message includes: a field indicating that the first data item list is accepted.

[0038] In one possible implementation, the registration response module updates the database table of the cloud device based on the first data item list, including: updating the database table of the cloud device through the library synchronization interface based on the first data item list, so that the corresponding data item version in the database table of the cloud device is updated to the first version.

[0039] In one possible implementation, the device also includes: a version synchronization module, which is used to call a preset business shadow synchronization interface to synchronize the interface protocol version of the edge device when an alarm information about the interface protocol version of the edge device is received.

[0040] In one possible implementation, the device also includes: a registration pass module, which is used to send a registration response message to the edge device when the first version is the same as the second version, and the response extension field of the registration response message includes: a field indicating that the registration of the edge device is passed.

[0041] According to one aspect of the present disclosure, a device registration apparatus is provided, which is applied to an edge device and includes:

[0042] A request sending module, configured to send a registration request to a cloud device when a registration condition is met, so that the cloud device responds with a registration, wherein the registration request includes device self-description information, and a registration extension field of the device self-description information includes: a first version of an interface protocol between the edge device and the cloud device, a first data item list, and document information of the interface protocol;

[0043] A response information acquisition module, configured to, upon receiving a registration response message from the cloud device, acquire a response extension field of the registration response message;

[0044] A connection establishment module is used to establish a communication connection with the cloud device when the response extension field indicates that the registration is successful, wherein the registration condition includes any one of the following: the edge device is started, the edge device is restarted, the system of the edge device is updated, and the interface of the edge device is updated.

[0045] In a possible implementation, the version of the interface protocol includes a model version, and the apparatus further includes:

[0046] A model receiving module is used to receive the second version of the model from the cloud device from the preset business shadow synchronization interface when the response extension field indicates that the model version of the edge device is to be updated; a model synchronization module is used to synchronize the local model of the edge device according to the second version of the model, so that the model version of the edge device is synchronized to the second version.

[0047] According to one aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to call the instructions stored in the memory to execute the above method.

[0048] According to one aspect of the present disclosure, a computer-readable storage medium is provided, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the above method is implemented.

[0049] In the disclosed embodiment, the interface protocol version in the registration extension field of the device self-description information of the registration request can be obtained and compared with the version retained in the cloud; when the versions are different, the corresponding registration response method is determined according to the version difference, and a registration response is performed, thereby realizing interface negotiation between the cloud and the edge, which can not only adapt to changes in the edge interface protocol, but also update the interface protocol of the edge, thereby realizing collaboration between the cloud and the edge, and improving the cloud's ability to adapt to changes in edge scenarios.

[0050] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, rather than limiting the present disclosure. Other features and aspects of the present disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] The accompanying drawings herein are incorporated into and constitute a part of the specification. These drawings illustrate embodiments consistent with the present disclosure and, together with the specification, are used to explain the technical solutions of the present disclosure.

[0052] Figure 1 A flowchart of a device registration method according to an embodiment of the present disclosure is shown.

[0053] Figure 2 A flowchart of a device registration method according to an embodiment of the present disclosure is shown.

[0054] Figure 3 A schematic diagram illustrating an interface of a device registration method according to an embodiment of the present disclosure is shown.

[0055] Figure 4 A flowchart of a device registration method according to an embodiment of the present disclosure is shown.

[0056] Figure 5 A block diagram illustrating a device registration apparatus according to an embodiment of the present disclosure is shown.

[0057] Figure 6 A block diagram illustrating a device registration apparatus according to an embodiment of the present disclosure is shown.

[0058] Figure 7 A block diagram of an electronic device according to an embodiment of the present disclosure is shown.

[0059] Figure 8 A block diagram of an electronic device according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0060] Various exemplary embodiments, features, and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. The same reference numerals in the accompanying drawings represent elements with the same or similar functions. Although various aspects of the embodiments are shown in the accompanying drawings, the drawings are not necessarily drawn to scale unless otherwise indicated.

[0061] The word “exemplary” is used exclusively herein to mean “serving as an example, example, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0062] The term "and / or" herein simply describes an association relationship between associated objects, indicating that three relationships can exist. For example, "A and / or B" can represent the existence of three situations: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" herein refers to any combination of at least two of any one or more of a plurality of items. For example, "at least one of A, B, and C" can represent any one or more elements selected from the set consisting of A, B, and C.

[0063] In addition, numerous specific details are provided in the following detailed description to better illustrate the present disclosure. Those skilled in the art will appreciate that the present disclosure can be practiced without certain specific details. In some instances, methods, means, components, and circuits well known to those skilled in the art are not described in detail in order to highlight the main points of the present disclosure.

[0064] In IoT systems, edge devices and systems used for front-end data collection are heterogeneous, diverse, and subject to changing scenarios. On the one hand, changes in edge devices lead to changes in uploaded data, which cannot be achieved through universal interface protocols. On the other hand, changing scenario requirements require real-time changes to the business model of edge devices and systems.

[0065] In related technologies, the edge can transmit self-describing information to the cloud via a self-describing interface. The cloud then searches and compares the information in the self-describing library, sets an adaptive interface corresponding to the self-describing information, and interacts with the edge through the adaptive interface. This approach can lead to a large number of adaptive changes in the cloud, resulting in frequent system upgrades and significant processing pressure on the cloud.

[0066] The device registration method according to the disclosed embodiment provides an improved interface system that complies with a universal interface protocol. This system automatically adapts to changes in the edge-side data upload interface while ensuring normal connectivity between the cloud and the edge. Furthermore, it enables remote updates of the cloud-side to edge-side business logic after edge-side scenarios change. This enables cloud-edge business and data collaboration, improves the cloud's ability to adapt to changes in edge-side scenarios, implements a self-contained business loop, and improves the efficiency of remote operation and maintenance management.

[0067] Figure 1 A flow chart of a device registration method according to an embodiment of the present disclosure is shown. The device registration method can be applied to cloud devices, such as cloud servers, Internet of Things service platforms, etc., and can be implemented by a processor calling computer-readable instructions stored in a memory.

[0068] like Figure 1 As shown, the device registration method includes:

[0069] In step S11, upon receiving a registration request from an edge device, obtaining device self-description information in the registration request, wherein a registration extension field of the device self-description information includes at least: a first version of an interface protocol between the edge device and the cloud device;

[0070] In step S12, if the first version and the second version are different, a corresponding registration response mode is determined according to the difference between the first version and the second version, where the second version is the interface protocol version between the cloud device and the edge device that is retained in the cloud device;

[0071] In step S13, a registration response is performed on the edge device according to the registration response method.

[0072] In one possible implementation, the edge device may be any electronic device such as a terminal device or a server (e.g., a front-end server). The terminal device may be a user equipment (UE), a mobile device, a user terminal, a terminal, a cellular phone, a cordless phone, a personal digital assistant (PDA), a handheld device, a computing device, an in-vehicle device, a wearable device, an image acquisition device (e.g., a camera), etc. This disclosure does not limit the specific device type of the edge device.

[0073] In one possible implementation, the edge device can register for the first time or re-register with the cloud device when the device is started, restarted, the system is updated, the interface is updated, etc., so as to establish a communication connection with the cloud device, receive instructions issued by the cloud device, send collected data to the cloud device, etc., thereby realizing various functions of the Internet of Things system.

[0074] In one possible implementation, when the edge device wants to initiate registration with the cloud device, it can generate a registration request and send the registration request to the cloud device through a preset registration interface.

[0075] In one possible implementation, the registration request includes device self-description information, which is used to indicate various parameters of the edge device, such as the type of edge device, device identification ID, device functional description information, etc. This disclosure does not limit the content included in the device self-description information.

[0076] According to an embodiment of the present disclosure, a registration extension field is set in the device self-description information, and the registration extension field includes: the version of the interface protocol between the edge device and the cloud device, a data item list, document information of the interface protocol, etc.

[0077] In one possible implementation, the version of the interface protocol is used to indicate the version of the interface protocol used by the edge device, including the model version of the business model, algorithm model, etc., the version of the data item that the edge device intends to report to the cloud device, etc. If the edge device has a customized business model, algorithm model, etc., the customized content and version information (such as the version date "ZDY_YYYYMMDD") can be attached to the first version of the interface protocol. This disclosure does not limit this.

[0078] In one possible implementation, the algorithm model may include algorithms for implementing various functions, such as object recognition algorithms, face recognition algorithms, and body recognition algorithms. The business model may include business logic in edge devices, such as camera image acquisition modes, linkage between devices and switches (such as access control devices), and alarms for abnormal situations. This disclosure does not limit the specific categories of algorithm models and business models.

[0079] In one possible implementation, the data item list is used to indicate the definition of each data item field to be reported by the edge device. For example, the data item list includes: [0:7] is the destination address; [8:31] is the recognition result, etc. This data item list can be included in the registration extension field only when the data item to be reported by the edge device has changed. Alternatively, the data item list can be included in the registration extension field regardless of whether the data item to be reported by the edge device has changed. This disclosure does not limit this.

[0080] In one possible implementation, the document information of the interface protocol is used to indicate the attribute information of the description document of the interface protocol, such as the file name, format, size, etc. of the description document, so that the cloud device can obtain the description document of the interface protocol according to the document information when needed, thereby improving the convenience of use.

[0081] In a possible implementation, in step S11, when the cloud device receives the registration request from the edge device, it can obtain the device self-description information in the registration request, and the registration extension field of the device self-description information includes at least the first version of the interface protocol.

[0082] In one possible implementation, the cloud device may store information about the interface protocol between the cloud device and the edge device, and the version of the interface protocol may be recorded as version 2. In this case, the cloud device may compare the first version of the interface protocol with the second version to determine whether the first version and the second version are the same.

[0083] In one possible implementation, if the first and second versions of the interface protocol are the same, the interface protocol of the edge device is consistent with that of the cloud. The cloud device can then send a registration response message to the edge device. The response extension field of the registration response message includes a field indicating that the edge device registration has passed, such as "Version Update - None, Data Item Update - None," and / or "Registration Passed." Thus, the cloud-edge interface negotiation is complete, and a communication connection is established between the cloud device and the edge device, enabling normal interaction.

[0084] In one possible implementation, if the first version of the interface protocol is different from the second version, it indicates that the interface protocol of the edge device is inconsistent with that of the cloud. In step S12, a corresponding registration response method can be determined based on the difference between the first version and the second version.

[0085] In one possible implementation, when the model versions (business model, algorithm model, etc.) in the interface protocol are different, processing can be performed based on the version level. If the model version of the edge device is lower, that is, the model version of the first version is lower than the model version of the second version, it can be determined that the registration response method includes: updating the model version of the edge device. In step S13, a registration response is performed according to the registration response method, and the model version of the edge device is synchronized with the model version of the cloud device.

[0086] In one possible implementation, if the model version of the edge device is higher, i.e., the first model version is higher than the second model version, then the registration response method may include: the model version of the edge device to be confirmed. In step S13, a registration response is performed according to the registration response method, and a process for confirming the model version is established for manual confirmation.

[0087] In one possible implementation, if the higher first version is rejected in the processing flow, the model version of the edge device can be synchronized back to the model version of the cloud device; if the higher first version is accepted in the processing flow, the new version can be developed and debugged on the cloud device; after the debugging is completed, the model version of the cloud device is updated to the first version.

[0088] In one possible implementation, when the data item versions in the interface protocol are different, the registration response method may be determined to be: a list of data items of the edge device to be confirmed. In step S13, a registration response is performed according to the registration response method, and a process for confirming the data item list is created for manual confirmation.

[0089] In one possible implementation, if a data item list on an edge device is rejected during the processing flow, a registration response message may be sent to the edge device. The response extension field of the registration response message includes a field indicating that the first data item list was rejected. Furthermore, a corresponding business process may be initiated to enable relevant personnel (e.g., operations and maintenance personnel) to adjust the data item list on the edge device.

[0090] In one possible implementation, if the data item list of the edge device in the processing flow is accepted, the database table of the cloud device can be updated, and a registration response message can be sent to the edge device. The response extension field of the registration response message includes: a field indicating that the first data item list is accepted.

[0091] According to the embodiments of the present disclosure, the interface protocol version in the registration extension field of the device self-description information of the registration request can be obtained and compared with the version retained in the cloud; when the versions are different, the corresponding registration response method is determined according to the version difference, and a registration response is performed, thereby realizing interface negotiation between the cloud and the edge, which can not only adapt to changes in the edge interface protocol, but also update the interface protocol of the edge, thereby realizing collaboration between the cloud and the edge, and improving the cloud's ability to adapt to changes in edge scenarios.

[0092] The device registration method according to an embodiment of the present disclosure is described below.

[0093] As mentioned above, when the cloud device receives a registration request from the edge device, it can obtain the device self-description information in the registration request in step S11. The registration extension field of the device self-description information includes at least: the first version of the interface protocol between the edge device and the cloud device, and may also include a list of data items, document information of the interface protocol, etc.

[0094] In one possible implementation, the cloud device may compare the first version with the second version stored in the cloud device to determine whether the first version is identical to the second version.

[0095] In one possible implementation, the device registration method according to an embodiment of the present disclosure may further include:

[0096] In the case that the first version is the same as the second version, a registration response message is sent to the edge device, and the response extension field of the registration response message includes: a field indicating that the registration of the edge device is successful.

[0097] In other words, if the first and second versions of the interface protocol are the same, the interface protocol of the edge device is consistent with that of the cloud device. The cloud device can then send a registration response message to the edge device. The response extension field of the registration response message includes a field indicating that the edge device registration has passed, such as "Version Update - None, Data Item Update - None," or "Registration Passed." This completes the cloud-edge interface negotiation process, the edge device completes registration, and a communication connection is established between the cloud and edge devices, enabling normal interaction.

[0098] In this way, the registration process can be implemented under the same interface protocol version, improving the efficiency of edge device registration.

[0099] In one possible implementation, if the first version of the interface protocol differs from the second version, it indicates that the interface protocol version of the edge device is inconsistent with the version stored in the cloud. In step S12, a corresponding registration response method can be determined based on the difference between the first version and the second version.

[0100] In one possible implementation, the version of the interface protocol includes model versions of the business model, algorithm model, etc., and versions of data items that the edge device intends to report to the cloud device. Accordingly, the differences between the first version and the second version include different model versions and / or different data item versions.

[0101] In a possible implementation, with respect to the model version of the interface protocol, step S12 may include: if the model version of the first version is lower than the model version of the second version, determining the registration response method includes: updating the model version of the edge device;

[0102] Accordingly, step S13 may include: synchronizing the model version of the edge device so that the model version of the edge device is synchronized to the second version; and / or, sending a registration response message to the edge device, and the response extension field of the registration response message includes: a field indicating that the model version of the edge device is to be updated.

[0103] For example, if the model version of the edge device is lower than the model version retained by the cloud device, for example, the model version of the first version is 2.1, and the model version of the second version is 2.2, it can be determined that the model version of the edge device needs to be updated to the cloud version. The corresponding registration response method includes: updating the model version of the edge device.

[0104] In this case, the cloud device performs a registration response according to the registration response method in step S13, and synchronizes the model version of the edge device to the second version of the cloud device, that is, sends the second version of the model to the edge device so that the edge device can install or save the model.

[0105] In one possible implementation, the cloud device may also send a registration response message to the edge device, and the response extension field of the registration response message includes a field indicating that the model version of the edge device needs to be updated, such as "Model version needs to be updated", so that the edge device can determine the current registration status.

[0106] In a possible implementation, the step of synchronizing the model version of the edge device may include: synchronizing the model version of the edge device through a preset business shadow synchronization interface.

[0107] In other words, a business shadow synchronization interface can be preset, which is used for the persistent configuration of the business of the edge device, ensuring the timeliness and eventual consistency of business-related information between the cloud and the edge, and realizing version synchronization between the cloud and the edge.

[0108] In a possible implementation, the service shadow synchronization interface may include a configuration delivery interface, a configuration response interface, and a configuration status reporting interface. It should be understood that the service shadow synchronization interface may also include other interfaces, which are not limited in this disclosure.

[0109] In one possible implementation, the step of synchronizing the model version of the edge device through a preset business shadow synchronization interface may include:

[0110] Sending the second version of the model in the model library of the cloud device to the edge device through the configuration sending interface;

[0111] In a case where configuration response information of the edge device is received through the configuration response interface, determining that the edge device has received the second version of the model;

[0112] When the configuration status information of the edge device is received through the configuration status reporting interface, it is determined that the model version of the edge device is synchronized to the second version.

[0113] For example, the second version of the model can be saved in the model library of the cloud device. When the model version of the edge device is synchronized through the business shadow synchronization interface, the cloud device can read the file of the second version of the model from the model library and send the model file to the edge device by configuring the sending interface.

[0114] In one possible implementation, after receiving the second version of the model file, the edge device can confirm whether the model file is complete. If the model file is complete, a configuration response message can be sent to the cloud device via the configuration response interface to inform the cloud device that the second version of the model has been received. If the model file is incomplete, a resend message can be sent to the cloud device via the configuration response interface to request that the cloud device resend the model file.

[0115] In one possible implementation, the edge device can install or save the second version of the model based on the model file. After the installation / saving is complete, the edge device sends configuration status information to the cloud device through the configuration status reporting interface, informing the cloud device that the model version of the edge device has been synchronized to the second version. After receiving the configuration status information, the cloud device can determine that the synchronization process of the model version of the edge device is complete.

[0116] In one possible implementation, after the model version of the edge device is synchronized, it can send a registration request to the cloud device again. In this case, the interface protocol of the edge device is consistent with that of the cloud device. The cloud device sends a registration response message to the edge device, indicating that the edge device registration is successful, completing the cloud-edge interface negotiation process. The edge device completes registration, and a communication connection is established between the cloud device and the edge device, enabling normal interaction.

[0117] In this way, when the model version of the edge device is lower, the interface protocol of the edge can be updated to achieve version synchronization between the cloud and the edge.

[0118] In a possible implementation, for the model version of the interface protocol, step S12 may include: if the model version of the first version is higher than the model version of the second version, determining the registration response mode includes: waiting to confirm the model version of the edge device;

[0119] Accordingly, step S13 may include: creating a first processing flow for confirming the model version;

[0120] In response to the rejection operation on the model version in the first processing flow, the model version of the edge device is synchronized so that the model version of the edge device is synchronized to the second version.

[0121] For example, if the model version of the edge device is higher than the model version retained by the cloud device, for example, the model version of the first version is 2.3, and the model version of the second version is 2.2, it is impossible to directly determine whether to accept the new version of the edge device. The registration response method can be determined to include: the model version of the edge device to be confirmed.

[0122] In this case, the cloud device performs a registration response according to the registration response method in step S13. A processing flow (which may be referred to as a first processing flow) for confirming the model version may be created for manual confirmation by relevant personnel (eg, management personnel).

[0123] In addition, the cloud device can also send a registration response message to the edge device. The response extension field of the registration response message includes a field indicating that the model version of the edge device is to be confirmed, such as "Model version update-to be confirmed", so that the edge device can determine the current registration status and wait for the next step of the process.

[0124] In one possible implementation, while waiting for confirmation of the model version of the edge device, the cloud device may also discard the uploaded data of the edge device and / or list the edge device in a state awaiting network access confirmation, etc. This disclosure does not impose any restrictions on this.

[0125] In a possible implementation, the cloud device may send a notification to relevant personnel to process the first processing flow. After receiving the notification, the relevant personnel may log in to the cloud device through the client to process the process.

[0126] In one possible implementation, if the relevant personnel do not accept the new version of the edge device, they can reject the model version in the first process. In response to the rejection of the model version in the first process, the cloud device can synchronize the model version of the edge device to the second version in the cloud, for example, rolling back from version 2.3 to version 2.2.

[0127] Similarly, cloud devices can synchronize the model version of edge devices through the above-mentioned business shadow synchronization interface. The model synchronization process is consistent with the synchronization process described above and will not be repeated here.

[0128] In one possible implementation, after the model version of the edge device is synchronized, it can send a registration request to the cloud device again. In this case, the interface protocol of the edge device is consistent with that of the cloud device. The cloud device sends a registration response message to the edge device, indicating that the edge device registration is successful, completing the cloud-edge interface negotiation process. The edge device completes registration, and a communication connection is established between the cloud device and the edge device, enabling normal interaction.

[0129] In this way, when the model version of the edge device is higher, manual confirmation can be performed by creating a processing flow; when the new version of the edge is rejected, version synchronization between the cloud and the edge can be achieved.

[0130] In a possible implementation, the cloud device performs a registration response according to the above registration response method in step S13, which may also include:

[0131] In response to the acceptance operation of the model version in the first processing flow, calling a file synchronization interface according to the document information to obtain a description document of the interface protocol and a model corresponding to the first version from the edge device;

[0132] Based on the description document and the model corresponding to the first version, the model library of the cloud device is updated so that the model in the model library is updated to the first version.

[0133] For example, in the first process, if the relevant personnel accept the new version of the edge device, the model version can be accepted in the first process. In this case, the relevant personnel can develop and debug the new version on the cloud device.

[0134] In one possible implementation, in response to the acceptance of the model version in the first processing flow, the cloud device may call a preset file synchronization interface based on the document information of the interface protocol in the registration extension field (the file name, format, size, etc. of the description document) to obtain the description document of the interface protocol from the edge device for reading, understanding, and interface development by relevant personnel of the cloud device (e.g., developers). Furthermore, the file synchronization interface may be called to obtain the model file corresponding to the first version from the edge device to update the model library of the cloud device.

[0135] In one possible implementation, a file synchronization interface is used to send files from the cloud to edge devices, and for edge devices to transfer files back to the cloud. The file synchronization interface includes large and small file upload and download interfaces. This disclosure does not limit the specific interface settings of the file synchronization interface.

[0136] In one possible implementation, the step of updating the model library of the cloud device based on the instruction document and the model corresponding to the first version may include:

[0137] Based on the description document and the model corresponding to the first version, a second processing flow is created for developing and debugging the interface protocol; in response to the completion of debugging the second processing flow, the corresponding model in the model library is updated to the model corresponding to the first version.

[0138] That is, after obtaining the instruction document and the first version of the model, the cloud device can create a process flow (referred to as a second process flow) for developing and debugging the interface protocol. In the second process flow, relevant personnel can develop and debug the cloud interface protocol based on the instruction document and the first version of the model file. This disclosure does not limit the specific method for developing and debugging the cloud interface protocol.

[0139] In one possible implementation, after the relevant personnel successfully debug the model, the debugging can be completed in the second process. In response to the completion of the debugging of the second process, the cloud device can update the corresponding model in the model library to the model corresponding to the first version, completing the cloud version update process.

[0140] In one possible implementation, the cloud device may also send a registration response message to the edge device. The response extension field of the registration response message includes a field indicating that the model version update is completed, such as "Model Version Update-Completed", indicating that the edge device registration is successful, the cloud-edge interface negotiation process is completed, and the edge device completes the registration.

[0141] In this way, when the model version of the edge device is higher and accepted, development and debugging can be carried out by creating a processing flow; after debugging is completed, the model in the cloud is updated to achieve version synchronization between the cloud and the edge.

[0142] As previously mentioned, the version of the interface protocol includes the model version of the business model, algorithm model, etc., the version of the data item that the edge device intends to report to the cloud device, etc. Accordingly, the difference between the first version and the second version includes different model versions and / or different data item versions.

[0143] In a possible implementation, for the data item version of the interface protocol, step S12 may include: if the data item version of the first version is different from the data item version of the second version, determining the registration response mode as: a data item list of the edge device to be confirmed;

[0144] Accordingly, step S13 may include: creating a third processing flow for confirming the first data item list;

[0145] In response to the rejection operation on the first data item list in the third processing flow, a registration response message is sent to the edge device, and the response extension field of the registration response message includes: a field indicating that the first data item list is rejected.

[0146] For example, if the first version of the data item version is different from the second version of the data item version stored in the cloud, that is, the edge device requests an update to the uploaded data item list, it is impossible to directly determine whether to accept the new version of the data item. The registration response method can be determined to include: the data item version of the edge device to be confirmed.

[0147] In this case, the cloud device performs a registration response according to the registration response method in step S13. A processing flow (which may be called a third processing flow) for confirming the first data item list may be created for manual confirmation by relevant personnel (eg, management personnel).

[0148] In addition, the cloud device can also send a registration response message to the edge device. The response extension field of the registration response message includes a field indicating that the data item version of the edge device is to be confirmed, such as "Data item update-to be confirmed", so that the edge device can determine the current registration status and wait for the next step of the process.

[0149] In one possible implementation, while waiting for confirmation of the data item list of the edge device, the cloud device may also discard the uploaded data of the edge device and / or list the edge device in a state of pending network access confirmation, etc. This disclosure does not impose any restrictions on this.

[0150] In one possible implementation, the cloud device may send a notification to relevant personnel to process the third processing flow. After receiving the notification, the relevant personnel can log in to the cloud device through the client to process the process. If the relevant personnel manually evaluate and do not accept the first data item list of the edge device, they can reject the first data item list in the third processing flow.

[0151] In one possible implementation, the cloud device sends a registration response message to the edge device in response to the rejection operation of the first data item list in the third processing flow, and the response extension field of the registration response message includes: a field indicating that the first data item list is rejected, such as "Data Item Update-Reject".

[0152] In this case, the edge device registration fails. The corresponding business process can be initiated to enable relevant personnel (such as operation and maintenance personnel) to adjust the uploaded data items of the edge device. This disclosure does not limit the handling method when the edge device registration fails.

[0153] In this way, when there is an update to the uploaded data items of the edge device, manual confirmation can be performed by creating a processing flow; when the data item is rejected, the data item update of the edge device is rejected, thereby avoiding unreasonable data item updates and improving the security and processing efficiency of the entire system.

[0154] In a possible implementation, the cloud device performs a registration response according to the above registration response method in step S13, which may also include:

[0155] In response to the acceptance operation of the first data item list in the third processing flow, updating the data synchronization interface of the cloud device according to the first data item list, so that the cloud device obtains the data items corresponding to the first data item list through the updated data synchronization interface; and / or

[0156] updating the database table of the cloud device according to the first data item list; and / or

[0157] A registration response message is sent to the edge device, where the response extension field of the registration response message includes: a field indicating that the first data item list is accepted.

[0158] For example, in the third processing flow, if the relevant personnel accept the first data item list of the edge device after manual evaluation, the first data item list can be accepted in the third processing flow.

[0159] In one possible implementation, the cloud device may update the data synchronization interface of the cloud device based on the first data item list in response to the acceptance operation of the first data item list in the third processing flow, so that the cloud device can obtain the data items corresponding to the first data item list through the updated data synchronization interface.

[0160] The data synchronization interface is used to send business data from the cloud to edge devices, and for edge devices to transmit business data back to the cloud. It is typically used in scenarios where data consistency and timeliness are not critical, such as business data logs collected by edge devices and device operation logs. The data synchronization interface may include a data sending interface and a data transmission interface. This disclosure does not limit the type or number of interfaces included in the data synchronization interface.

[0161] In one possible implementation, after the update is completed, the edge device can upload the business data collected / reported by the edge through the data synchronization interface, and the cloud device can send business feedback data through the data synchronization interface, thereby realizing data interaction between the cloud and the edge.

[0162] In one possible implementation, the cloud device may also update the database table of the cloud device based on the first data item list, such as adding data items to the cloud database table or creating a new key-value pair database, so that the cloud retains the updated data item list.

[0163] In one possible implementation, the step of updating the database table of the cloud device according to the first data item list may include:

[0164] According to the first data item list, the database table of the cloud device is updated through the library synchronization interface, so that the corresponding data item version in the database table of the cloud device is updated to the first version.

[0165] That is, if the data items in the first data item list are data stored in the form of a library, they can be updated through the library synchronization interface. It is possible that the edge device is a front-end server or other device, which is provided with an edge database table.

[0166] Among them, the library synchronization interface is used to obtain the library list and the business data contained therein, including the portrait library, feature library, voice library or other image library. The library synchronization interface can achieve full and incremental data synchronization between the cloud and the edge through the library synchronization interface to maintain data consistency between the cloud and the edge. The library synchronization interface may include a library list subscription interface, a library metadata subscription interface, a full data acquisition interface, a specified range data subscription interface, an incremental data subscription interface, etc., which are not limited in this disclosure.

[0167] In one possible implementation, the library synchronization interface may be called based on the first data item list to update the database table of the cloud device so that the updated data item list is retained in the cloud.

[0168] In this way, it is possible to adapt to processing in various situations and improve the flexibility of cloud database table updates.

[0169] In one possible implementation, the cloud device may also send a registration response message to the edge device again, and the response extension field of the registration response message includes: a field indicating that the first data item list is accepted, such as "Data Item Update-Accept", indicating that the edge device registration is successful, completing the cloud-edge interface negotiation process, and the edge device completes the registration.

[0170] In this way, when the uploaded data items of the edge device are updated and accepted, the data interface and database table in the cloud can be updated, so that the cloud and edge can interact according to the updated data items, realizing data collaboration between the cloud and the edge.

[0171] After the cloud device updates at least one of the model version, model library, data synchronization interface, and database table of the interface protocol in accordance with the above-mentioned cloud-edge collaboration method, the edge device that is adapted to the same type of interface protocol can be updated.

[0172] Among them, the cloud device can passively wait for the edge device to register again, or require the edge device to re-register after the update, and update the interface protocol version of the edge device during the re-registration or re-registration process; it can also actively check the interface protocol version of each edge device, and update the interface protocol version of the edge device when different versions are found.

[0173] In a possible implementation, the device registration method according to an embodiment of the present disclosure may further include:

[0174] When an alarm message about the interface protocol version of the edge device is received, a preset service shadow synchronization interface is called to synchronize the interface protocol version of the edge device.

[0175] For example, the cloud device can check the interface protocol version of the edge device regularly (for example, daily or weekly) through the operation and maintenance system. If the operation and maintenance system finds that the edge device is running under an older version of the interface protocol, it will issue an alarm and send an alarm message to the cloud device.

[0176] In one possible implementation, if a cloud device receives an alert about the interface protocol version of an edge device, it can directly call an interface such as the business shadow synchronization interface to synchronize the interface protocol version of the edge device, enabling remote updates of the edge device and batch interface updates. This synchronization process is consistent with the synchronization process described above and will not be repeated here.

[0177] In this way, the lower version of the interface protocol can be updated proactively, thereby improving the system's update speed and efficiency.

[0178] According to one aspect of an embodiment of the present disclosure, a device registration method is provided, which is applied to an edge device. The edge device can be any terminal device or electronic device such as a server (e.g., a front-end server). The terminal device can be a user equipment (UE), a mobile device, a user terminal, a terminal, a cellular phone, a cordless phone, a personal digital assistant (PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, an image acquisition device (e.g., a camera), etc. The present disclosure does not limit the specific device type of the edge device.

[0179] Figure 2 FIG. 1 is a flow chart showing a device registration method according to an embodiment of the present disclosure. Figure 2 As shown, the method includes:

[0180] In step S21, if the registration conditions are met, a registration request is sent to the cloud device, so that the cloud device responds with a registration, wherein the registration request includes device self-description information, and the registration extension field of the device self-description information includes: a first version of the interface protocol between the edge device and the cloud device, a first data item list, and document information of the interface protocol;

[0181] In step S22, upon receiving the registration response information from the cloud device, obtaining a response extension field of the registration response information;

[0182] In step S23, if the response extension field indicates that the registration is successful, a communication connection is established with the cloud device.

[0183] Among them, the registration conditions include any one of the following: the edge device is started, the edge device is restarted, the system of the edge device is updated, and the interface of the edge device is updated.

[0184] For example, if the edge device meets the registration conditions, it can initiate a registration request to the cloud device. The registration conditions may include any one of the following: edge device startup, edge device restart, edge device system update, and edge device interface update, which are not limited in this disclosure.

[0185] In one possible implementation, if the registration conditions are met, the edge device may generate and send a registration request to the cloud device in step S21. The registration request includes device self-description information, which is used to indicate various parameters of the edge device, such as the type of edge device, device identification ID, and device function description information. This disclosure does not limit the content included in the device self-description information.

[0186] According to an embodiment of the present disclosure, a registration extension field is set in the device self-description information, and the registration extension field includes: the version of the interface protocol between the edge device and the cloud device, a data item list, document information of the interface protocol, etc.

[0187] In one possible implementation, upon receiving a registration request from an edge device, the cloud device may obtain the registration extension field of the device's self-description information in the registration request. The cloud device may compare the first version of the interface protocol in the registration extension field with the second version of the interface protocol stored in the cloud device to determine whether the first and second versions are identical.

[0188] In one possible implementation, if the first version and the second version of the interface protocol are the same, it means that the interface protocol of the edge device is consistent with that of the cloud. The cloud device can send a registration response message to the edge device. The response extension field of the registration response message includes a field indicating that the registration of the edge device is successful, such as "version update-none, data item update-none" and / or "registration successful".

[0189] In one possible implementation, when the model versions of the first version and the second version of the interface protocol are different and the model version of the edge device is lower, the cloud can send a registration response message to indicate that the model version of the edge device needs to be updated; and the cloud will synchronize the model version of the edge device through the business shadow synchronization interface and update it to the new version of the cloud.

[0190] In one possible implementation, when the model versions of the first and second versions of the interface protocol are different and the model version of the edge device is higher, the cloud may accept or reject the model version of the edge device. The cloud will first send a registration response message to instruct the edge device to wait for confirmation, such as "Version update-pending confirmation".

[0191] In one possible implementation, if the model version of the edge device is rejected, a registration response message may be sent to indicate that the model version of the edge device is rejected; and the cloud will synchronize the model version of the edge device through the business shadow synchronization interface and update it back to the old version on the cloud; if the model version of the edge device is accepted, the cloud may develop and debug the new version, and after the development and debugging of the new version is completed, a registration response message may be sent again to indicate that the model version of the edge device is accepted and the cloud update is completed, such as "Model version update-completed".

[0192] In one possible implementation, when the data item versions of the first and second versions of the interface protocol differ, the cloud may accept or reject the data item list of the edge device. If the data item list of the edge device is rejected, a registration response message is sent to indicate that the data item list is rejected, such as "Data Item Update-Rejected." If the data item list of the edge device is accepted, the data synchronization interface and database table of the cloud device are updated, and a registration response message is sent to indicate that the data item list is accepted, such as "Data Item Update-Accepted."

[0193] In one possible implementation, when the edge device receives the registration response information from the cloud device, it can obtain the response extension field of the registration response information in step S22 and perform corresponding processing according to the response extension field.

[0194] In one possible implementation, in step S23, if the response extension field indicates that the registration is successful, possible situations include: directly passing "version update-none, data item update-none" or "registration passed", the model version is accepted "model version update-completed", the data item update is accepted "data item update-accepted", etc., then the edge device completes the registration, and can establish a communication connection with the cloud device and conduct data interaction normally.

[0195] In this way, the registration extension field of the device's self-description information can be used to achieve interface negotiation with the cloud and complete the registration process of the edge device, thereby achieving collaboration between the cloud and the edge and improving the cloud's adaptability to changes in edge scenarios.

[0196] In a possible implementation, the method may further include:

[0197] When the response extension field indicates that the model version of the edge device is to be updated, receiving a second version of the model from the cloud device through a preset business shadow synchronization interface;

[0198] According to the second version of the model, the local model of the edge device is synchronized so that the model version of the edge device is synchronized to the second version.

[0199] For example, the response extension field of the registration response information can be obtained in step S22. If the model version of the edge device is indicated to be updated, for example, the model version of the edge device is lower, indicating that the model version is to be updated; or the model version of the edge device is higher, but the model version is rejected, the edge device can receive the second version of the model from the cloud device through the business shadow synchronization interface. The business shadow synchronization interface includes a configuration delivery interface, a configuration response interface, and a configuration status reporting interface.

[0200] In one possible implementation, the edge device can receive the second version of the model file through the configuration delivery interface. If the received model file is complete, it can send a configuration response message to the cloud device through the configuration response interface to inform the cloud device that the second version of the model has been received.

[0201] In one possible implementation, the edge device can install or save the second version of the model based on the second version of the model file. After the installation / saving is complete, the edge device sends configuration status information to the cloud device through the configuration status reporting interface, informing the cloud device that the model version of the edge device has been synchronized to the second version. After receiving the configuration status information, the cloud device can determine that the synchronization process of the model version of the edge device is complete.

[0202] In this way, the interface protocol at the edge can be updated to achieve model version synchronization between the cloud and the edge.

[0203] Figure 3 FIG. 1 shows an interface diagram of a device registration method according to an embodiment of the present disclosure. Figure 3 As shown, a registration interface, a business shadow synchronization interface, a library synchronization interface, a data synchronization interface and a file synchronization interface are set between the cloud device and the edge device.

[0204] In the example, the registration interface is used to register the edge device. The edge device sends a registration request to the cloud device through the registration interface; the cloud device sends a registration response message to the edge device through the registration interface.

[0205] In the example, the business shadow synchronization interface is used for the persistent configuration of the business of the edge device, ensuring the timeliness and eventual consistency of business-related information between the cloud and the edge, and realizing version synchronization between the cloud and the edge. The business shadow synchronization interface includes a configuration delivery interface, a configuration response interface, and a configuration status reporting interface. It should be understood that the business shadow synchronization interface may also include other interfaces, which are not limited by this disclosure.

[0206] In this example, the data synchronization interface is used to send business data from the cloud to edge devices, and for edge devices to transmit business data back to the cloud. It is typically used in scenarios where data consistency and timeliness are not critical, such as business data logs collected by edge devices and device operation logs. Data synchronization interfaces may include data sending interfaces and data transmission interfaces. This disclosure does not limit the type or number of interfaces included in data synchronization interfaces.

[0207] In this example, the file synchronization interface is used to send files from the cloud to the edge device, and the edge device to transfer files back to the cloud. The file synchronization interface includes large and small file upload and download interfaces. This disclosure does not limit the specific interface settings of the file synchronization interface.

[0208] In the example, the library synchronization interface is used to obtain the library list and the business data contained therein, including the portrait library, feature library, voice library, or other image library. The library synchronization interface can be used between the cloud and the edge to achieve full and incremental data synchronization, maintaining data consistency between the cloud and the edge. The library synchronization interface may include a library list subscription interface, a library metadata subscription interface, a full data acquisition interface, a specified range data subscription interface, an incremental data subscription interface, etc., which are not limited in this disclosure.

[0209] Figure 4 FIG. 1 is a flow chart showing a device registration method according to an embodiment of the present disclosure. Figure 4 As shown, if the interface protocol version of the edge device changes, it sends a registration request to the cloud device through the registration interface. After receiving the registration request, the cloud device extracts the registration extension field in the device's self-description information to determine whether the interface protocol version is consistent. If the interface protocol version is consistent, it issues a registration response, indicating that the edge device registration has succeeded, such as "Version Update - No, Data Item Update - No" or "Registration Successful."

[0210] In the example, if the versions of the interface protocols are inconsistent, the version difference of the interface protocols is determined; if the model versions are different, a version comparison is performed; if the model version of the edge device is old (low version), the model version should be updated, and a registration response is performed to instruct the edge device to update the model.

[0211] In the example, if the model version of the edge device is new (higher version), a processing flow is created to perform manual confirmation of the model; if the model is confirmed to be unacceptable in the processing flow, the model version should be updated and a registration response is made to instruct the edge device to update the model.

[0212] In the example, when the registration response instructs the edge device to update the model, the model version in the cloud is sent to the edge device through the business shadow synchronization interface, so that the edge device can update the model version; after the edge device update is completed, the device can be restarted, and the registration process can be started again after the restart.

[0213] In the example, if the model acceptance is confirmed in the processing flow, after development and debugging, the model library is updated / added and a registration response is made to indicate that the edge device model is accepted.

[0214] In this example, during the step of determining interface protocol version differences, if the reported data item versions are different, a processing flow is created to manually confirm the data item list. If the processing flow confirms that the data item list is not acceptable, a registration response is issued to indicate that the data item list is rejected, such as "Data Item Update - Rejected." If the processing flow confirms that the data item list is accepted, the cloud database table is updated. After the update is complete, a registration response is issued to indicate that the data item list is accepted.

[0215] In this way, device registration in various situations can be achieved, and cloud-edge business collaboration and data collaboration can be realized.

[0216] According to the device registration method of the embodiment of the present disclosure, the version of the interface protocol is described by registering an extended field, so that interface changes of edge devices under the universal interface standard can be realized through interface interaction, and the interface protocol can be updated through interface negotiation. This method can send business models and algorithm models through the business shadow synchronization interface when the model versions are different, realize remote definition of the business model and algorithm model of the edge device, realize model version synchronization between the cloud and the edge, and realize reliable synchronization of data after interface changes.

[0217] In scenarios such as smart cities, when a large number of edge devices are connected, many edge devices can be connected through a unified universal interface. However, due to changes in scenario requirements, corresponding changes in business models, algorithm models, and business data are required.

[0218] The device registration method according to the disclosed embodiments enables updates to edge device interfaces, business models, and algorithm models, as well as changes to interactive business data. This enables cloud-edge business and data collaboration, improves the cloud's ability to adapt to changes in edge scenarios, implements a self-closed business loop, and improves the efficiency of remote operation and maintenance management. This enables cloud-edge business and data collaboration.

[0219] It is understood that the above-mentioned various method embodiments mentioned in this disclosure can be combined with each other to form combined embodiments without violating the principle logic. Due to space limitations, this disclosure will not go into details. It is understood by those skilled in the art that in the above-mentioned methods of specific implementation, the specific execution order of each step should be determined by its function and possible internal logic.

[0220] In addition, the present disclosure also provides a device registration device, an electronic device, a computer-readable storage medium, and a program, all of which can be used to implement any device registration method provided by the present disclosure. The corresponding technical solutions and descriptions are referred to the corresponding records in the method section and will not be repeated here.

[0221] Figure 5 A block diagram of a device registration apparatus according to an embodiment of the present disclosure is shown, which is applied to a cloud device, such as Figure 5 As shown, the device includes:

[0222] An information acquisition module 51 is configured to, upon receiving a registration request from an edge device, acquire device self-description information in the registration request, wherein a registration extension field of the device self-description information includes at least a first version of an interface protocol between the edge device and the cloud device;

[0223] a response mode determination module 52 for determining a corresponding registration response mode based on the difference between the first version and the second version when the first version and the second version are different, where the second version is the interface protocol version between the cloud device and the edge device, which is retained in the cloud device;

[0224] The registration response module 53 is used to perform a registration response to the edge device according to the registration response method.

[0225] In a possible implementation, the version of the interface protocol includes a model version, and the response mode determination module is configured to: when the model version of the first version is lower than the model version of the second version, determine the registration response mode including: updating the model version of the edge device;

[0226] Among them, the registration response module is used to: synchronize the model version of the edge device so that the model version of the edge device is synchronized to the second version; and / or send a registration response message to the edge device, and the response extension field of the registration response message includes: a field indicating that the model version of the edge device is to be updated.

[0227] In a possible implementation, the version of the interface protocol includes a model version, and the response mode determination module is configured to: when the model version of the first version is higher than the model version of the second version, determine the registration response mode including: to confirm the model version of the edge device;

[0228] Among them, the registration response module is used to: create a first processing flow for confirming the model version; in response to the rejection operation of the model version in the first processing flow, synchronize the model version of the edge device so that the model version of the edge device is synchronized to the second version.

[0229] In a possible implementation, the registration response module synchronizes the model version of the edge device, including: synchronizing the model version of the edge device through a preset business shadow synchronization interface.

[0230] In one possible implementation, the business shadow synchronization interface includes a configuration sending interface, a configuration response interface and a configuration status reporting interface, wherein the registration response module synchronizes the model version of the edge device through the preset business shadow synchronization interface, including: sending the second version of the model in the model library of the cloud device to the edge device through the configuration sending interface; when the configuration response information of the edge device is received through the configuration response interface, determining that the edge device has received the second version of the model; when the configuration status information of the edge device is received through the configuration status reporting interface, determining that the model version of the edge device is synchronized to the second version.

[0231] In one possible implementation, the registration extension field also includes document information of the interface protocol, wherein the registration response module is further used to: in response to the acceptance operation of the model version in the first processing flow, call the file synchronization interface according to the document information, and obtain the description document of the interface protocol and the model corresponding to the first version from the edge device; based on the description document and the model corresponding to the first version, update the model library of the cloud device so that the model of the model library is updated to the first version.

[0232] In one possible implementation, the registration response module updates the model library of the cloud device based on the description document and the model corresponding to the first version, including: creating a second processing flow for developing and debugging the interface protocol based on the description document and the model corresponding to the first version; in response to the completion of debugging the second processing flow, updating the corresponding model in the model library to the model corresponding to the first version.

[0233] In one possible implementation, the registration extension field also includes a first data item list, and the version of the interface protocol includes a data item version, wherein the response method determination module is used to: when the data item version of the first version is different from the data item version of the second version, determine the registration response method as: the data item list of the edge device to be confirmed; wherein the registration response module is used to: create a third processing flow for confirming the first data item list; in response to the rejection operation of the first data item list in the third processing flow, send a registration response message to the edge device, and the response extension field of the registration response message includes: a field indicating that the first data item list is rejected.

[0234] In one possible implementation, the registration response module is also used to: in response to the acceptance operation of the first data item list in the third processing flow, update the data synchronization interface of the cloud device according to the first data item list, so that the cloud device obtains the data items corresponding to the first data item list through the updated data synchronization interface; and / or update the database table of the cloud device according to the first data item list; and / or send a registration response message to the edge device, and the response extension field of the registration response message includes: a field indicating that the first data item list is accepted.

[0235] In one possible implementation, the registration response module updates the database table of the cloud device based on the first data item list, including: updating the database table of the cloud device through the library synchronization interface based on the first data item list, so that the corresponding data item version in the database table of the cloud device is updated to the first version.

[0236] In one possible implementation, the device also includes: a version synchronization module, which is used to call a preset business shadow synchronization interface to synchronize the interface protocol version of the edge device when an alarm information about the interface protocol version of the edge device is received.

[0237] In one possible implementation, the device also includes: a registration pass module, which is used to send a registration response message to the edge device when the first version is the same as the second version, and the response extension field of the registration response message includes: a field indicating that the registration of the edge device is passed.

[0238] Figure 6 A block diagram of a device registration apparatus according to an embodiment of the present disclosure is shown, which is applied to edge devices, such as Figure 6 As shown, the device includes:

[0239] A request sending module 61 is configured to send a registration request to a cloud device when registration conditions are met, so that the cloud device responds with a registration request, wherein the registration request includes device self-description information, and a registration extension field of the device self-description information includes: a first version of an interface protocol between the edge device and the cloud device, a first data item list, and document information of the interface protocol;

[0240] A response information acquisition module 62 is configured to acquire a response extension field of the registration response information upon receiving the registration response information of the cloud device;

[0241] The connection establishment module 63 is used to establish a communication connection with the cloud device when the response extension field indicates that the registration is successful, wherein the registration condition includes any one of the following: the edge device is started, the edge device is restarted, the system of the edge device is updated, and the interface of the edge device is updated.

[0242] In a possible implementation, the version of the interface protocol includes a model version, and the apparatus further includes:

[0243] A model receiving module is used to receive the second version of the model from the cloud device from the preset business shadow synchronization interface when the response extension field indicates that the model version of the edge device is to be updated; a model synchronization module is used to synchronize the local model of the edge device according to the second version of the model, so that the model version of the edge device is synchronized to the second version.

[0244] In some embodiments, the functions or modules included in the device provided by the embodiments of the present disclosure can be used to execute the method described in the above method embodiments. The specific implementation can refer to the description of the above method embodiments. For the sake of brevity, it will not be repeated here.

[0245] The present disclosure also provides a computer-readable storage medium having computer program instructions stored thereon, wherein the computer program instructions implement the above method when executed by a processor. The computer-readable storage medium may be a volatile or non-volatile computer-readable storage medium.

[0246] An embodiment of the present disclosure further proposes an electronic device, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to call the instructions stored in the memory to execute the above method.

[0247] An embodiment of the present disclosure also provides a computer program product, including computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code. When the computer-readable code runs in a processor of an electronic device, the processor in the electronic device executes the above method.

[0248] The electronic device may be provided as a terminal, a server, or other forms of devices.

[0249] Figure 7 The block diagram of an electronic device 800 according to an embodiment of the present disclosure is shown. For example, the electronic device 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, or the like.

[0250] Reference Figure 7 , the electronic device 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input / output (I / O) interface 812 , a sensor component 814 , and a communication component 816 .

[0251] The processing component 802 generally controls the overall operation of the electronic device 800, such as operations associated with display, phone calls, data communications, camera operation, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the above-described method. In addition, the processing component 802 may include one or more modules to facilitate interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.

[0252] The memory 804 is configured to store various types of data to support operations on the electronic device 800. Examples of such data include instructions for any application or method operating on the electronic device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 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.

[0253] The power supply component 806 provides power to the various components of the electronic device 800. The power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device 800.

[0254] The multimedia component 808 includes a screen that provides an output interface between the electronic device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor can not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the electronic device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have a focal length and optical zoom capability.

[0255] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), which is configured to receive external audio signals when the electronic device 800 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

[0256] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as a keyboard, click wheel, buttons, etc. These buttons may include but are not limited to: a home button, volume buttons, a start button, and a lock button.

[0257] The sensor assembly 814 includes one or more sensors for providing various aspects of status assessment for the electronic device 800. For example, the sensor assembly 814 can detect the open / closed state of the electronic device 800, the relative positioning of components, such as the display and keypad of the electronic device 800. The sensor assembly 814 can also detect changes in the position of the electronic device 800 or a component of the electronic device 800, the presence or absence of user contact with the electronic device 800, the orientation or acceleration / deceleration of the electronic device 800, and the temperature change of the electronic device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include a light sensor, such as a complementary metal oxide semiconductor (CMOS) or charge coupled device (CCD) image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0258] The communication component 816 is configured to facilitate wired or wireless communication between the electronic device 800 and other devices. The electronic device 800 can access a wireless network based on a communication standard, such as a wireless network (WiFi), a second generation mobile communication technology (2G) or a third generation mobile communication technology (3G), or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0259] In an exemplary embodiment, the electronic device 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above methods.

[0260] In an exemplary embodiment, a non-volatile computer-readable storage medium is also provided, such as a memory 804 including computer program instructions. The computer program instructions can be executed by the processor 820 of the electronic device 800 to perform the above method.

[0261] Figure 8 FIG1 shows a block diagram of an electronic device 1900 according to an embodiment of the present disclosure. For example, the electronic device 1900 may be provided as a server. Figure 8 The electronic device 1900 includes a processing component 1922, which further includes one or more processors, and a memory resource represented by a memory 1932 for storing instructions executable by the processing component 1922, such as an application. The application stored in the memory 1932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 1922 is configured to execute the instructions to perform the above-described method.

[0262] The electronic device 1900 may further include a power supply component 1926 configured to perform power management of the electronic device 1900, a wired or wireless network interface 1950 configured to connect the electronic device 1900 to a network, and an input / output (I / O) interface 1958. The electronic device 1900 may operate based on an operating system stored in the memory 1932, such as a Microsoft Server operating system (Windows Server 2003). TM ), a graphical user interface operating system launched by Apple (Mac OSX TM ), a multi-user, multi-process computer operating system (Unix TM ), a free and open source Unix-like operating system (Linux TM ), an open-source Unix-like operating system (FreeBSD TM ) or similar.

[0263] In an exemplary embodiment, a non-volatile computer-readable storage medium is also provided, such as a memory 1932 including computer program instructions that can be executed by the processing component 1922 of the electronic device 1900 to perform the above method.

[0264] The present disclosure may be a system, method and / or computer program product. The computer program product may include a computer-readable storage medium carrying computer-readable program instructions for causing a processor to implement various aspects of the present disclosure.

[0265] Computer-readable storage media can be a tangible device that can hold and store the instructions used by the instruction execution device. Computer-readable storage media can be, for example, (but not limited to) an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. More specific examples (non-exhaustive list) of computer-readable storage media include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, for example, a punch card or a convex structure in a groove on which instructions are stored, and any suitable combination thereof. Computer-readable storage media used herein is not interpreted as a transient signal itself, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagated by waveguides or other transmission media (for example, light pulses by fiber optic cables), or electrical signals transmitted by wires.

[0266] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in the computer-readable storage medium in each computing / processing device.

[0267] The computer program instructions for performing the operations of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages such as Smalltalk, C++, and conventional procedural programming languages such as "C" language or similar programming languages. Computer-readable program instructions may be executed entirely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer, partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., utilizing an Internet service provider to connect via the Internet). In some embodiments, an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may be personalized by utilizing the state information of the computer-readable program instructions. The electronic circuit may execute the computer-readable program instructions, thereby realizing various aspects of the present disclosure.

[0268] Various aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0269] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processor of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0270] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0271] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems, methods and computer program products according to multiple embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and the part of the module, program segment or instruction contains one or more executable instructions for realizing the prescribed logical function. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that 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 flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented by a dedicated hardware-based system that performs the prescribed function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0272] The computer program product may be implemented in hardware, software, or a combination thereof. In one embodiment, the computer program product is implemented as a computer storage medium. In another embodiment, the computer program product is implemented as a software product, such as a software development kit (SDK).

[0273] While various embodiments of the present disclosure have been described above, the above descriptions are illustrative, non-exhaustive, and not intended to be limiting of the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, their practical applications, or improvements to existing technologies, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A device registration method, characterized in that: Applied to cloud devices, including: Upon receiving a registration request from an edge device, obtaining device self-description information in the registration request, wherein a registration extension field of the device self-description information includes at least: a first version of an interface protocol between the edge device and the cloud device; In the case where the first version and the second version are different, determining the corresponding registration response method according to the difference between the first version and the second version, where the second version is the interface protocol version between the cloud device and the edge device retained in the cloud device; Performing a registration response on the edge device according to the registration response method; The version of the interface protocol includes a model version, and the registration extension field also includes document information of the interface protocol; The determining of the corresponding registration response method according to the difference between the first version and the second version includes: when the model version of the first version is higher than the model version of the second version, determining the registration response method includes: waiting to confirm the model version of the edge device; wherein, performing a registration response to the edge device according to the registration response method includes: creating a first processing flow for confirming the model version; in response to the acceptance operation of the model version in the first processing flow, calling the file synchronization interface according to the document information, obtaining the description document of the interface protocol and the model corresponding to the first version from the edge device; based on the description document and the model corresponding to the first version, updating the model library of the cloud device so that the model of the model library is updated to the first version; performing a registration response to the edge device according to the registration response method also includes: in response to the rejection operation of the model version in the first processing flow, synchronizing the model version of the edge device so that the model version of the edge device is synchronized to the second version; The corresponding registration response method is determined based on the difference between the first version and the second version, including: when the model version of the first version is lower than the model version of the second version, determining the registration response method includes: updating the model version of the edge device; wherein, the registration response to the edge device based on the registration response method includes: synchronizing the model version of the edge device so that the model version of the edge device is synchronized to the second version; and / or sending a registration response message to the edge device, and the response extension field of the registration response message includes: a field indicating that the model version of the edge device is to be updated.

2. The method according to claim 1, characterized in that The synchronizing the model version of the edge device includes: The model version of the edge device is synchronized through a preset business shadow synchronization interface.

3. The method according to claim 2, characterized in that The service shadow synchronization interface includes a configuration delivery interface, a configuration response interface, and a configuration status reporting interface. The step of synchronizing the model version of the edge device through a preset business shadow synchronization interface includes: Sending the second version of the model in the model library of the cloud device to the edge device through the configuration sending interface; In a case where configuration response information of the edge device is received through the configuration response interface, determining that the edge device has received the second version of the model; When the configuration status information of the edge device is received through the configuration status reporting interface, it is determined that the model version of the edge device is synchronized to the second version.

4. The method according to claim 1, wherein The updating of the model library of the cloud device based on the instruction document and the model corresponding to the first version includes: Creating a second process flow for developing and debugging the interface protocol based on the instruction document and the model corresponding to the first version; In response to completion of debugging the second processing flow, the corresponding model in the model library is updated to a model corresponding to the first version.

5. The method according to any one of claims 1 to 4, characterized in that The registration extension field also includes a first data item list, and the version of the interface protocol includes a data item version. The determining of the corresponding registration response mode according to the difference between the first version and the second version includes: In a case where the data item version of the first version is different from the data item version of the second version, determining the registration response mode is: waiting to confirm the data item list of the edge device; The step of performing a registration response on the edge device according to the registration response method includes: creating a third processing flow for confirming the first list of data items; In response to the rejection operation on the first data item list in the third processing flow, a registration response message is sent to the edge device, and the response extension field of the registration response message includes: a field indicating that the first data item list is rejected.

6. The method according to claim 5, characterized in that The step of performing a registration response on the edge device according to the registration response method further includes: In response to the acceptance operation of the first data item list in the third processing flow, updating the data synchronization interface of the cloud device according to the first data item list, so that the cloud device obtains the data items corresponding to the first data item list through the updated data synchronization interface; and / or updating the database table of the cloud device according to the first data item list; and / or A registration response message is sent to the edge device, where the response extension field of the registration response message includes: a field indicating that the first data item list is accepted.

7. The method according to claim 6, characterized in that The updating of the database table of the cloud device according to the first data item list includes: According to the first data item list, the database table of the cloud device is updated through the library synchronization interface, so that the corresponding data item version in the database table of the cloud device is updated to the first version.

8. The method according to any one of claims 1 to 4, characterized in that The method further comprises: When an alarm message about the interface protocol version of the edge device is received, a preset service shadow synchronization interface is called to synchronize the interface protocol version of the edge device.

9. The method according to any one of claims 1 to 4, characterized in that The method further comprises: In the case that the first version is the same as the second version, a registration response message is sent to the edge device, and the response extension field of the registration response message includes: a field indicating that the registration of the edge device is successful.

10. A device registration method, characterized in that: Applied to edge devices, including: When the registration conditions are met, a registration request is sent to the cloud device, so that the cloud device responds with a registration, wherein the registration request includes device self-description information, and the registration extension field of the device self-description information includes: a first version of the interface protocol between the edge device and the cloud device, a first data item list, and document information of the interface protocol; Upon receiving the registration response information of the cloud device, obtaining a response extension field of the registration response information; If the response extension field indicates that the registration is successful, a communication connection is established with the cloud device. The registration condition includes any one of the following: the edge device is started, the edge device is restarted, the system of the edge device is updated, and the interface of the edge device is updated; The version of the interface protocol includes a model version, and the method further includes: In a case where the response extension field indicates that the model version of the edge device is to be confirmed, in response to the acceptance operation of the model version in the first processing flow for confirming the model version in the cloud device, the file synchronization interface is called according to the document information, and the description document of the interface protocol and the model corresponding to the first version are sent to the cloud device, so that the cloud device updates the model of the model library of the cloud device to the first version based on the description document and the model corresponding to the first version; in response to the rejection operation of the model version in the first processing flow in the cloud device, the model version of the edge device is synchronized so that the model version of the edge device is synchronized to the second version, wherein the second version is the interface protocol version between the cloud device and the edge device retained in the cloud device; When the response extension field includes: a field indicating that the model version of the edge device is to be updated, the model version of the edge device is synchronized according to the field indicating that the model version of the edge device is to be updated, so that the model version of the edge device is synchronized to the second version.

11. The method according to claim 10, characterized in that The method further comprises: When the response extension field indicates that the model version of the edge device is to be updated, receiving a second version of the model from the cloud device through a preset business shadow synchronization interface; According to the second version of the model, the local model of the edge device is synchronized so that the model version of the edge device is synchronized to the second version.

12. A device registration apparatus, characterized in that: Applied to cloud devices, including: An information acquisition module is configured to, upon receiving a registration request from an edge device, acquire device self-description information in the registration request, wherein a registration extension field of the device self-description information includes at least: a first version of an interface protocol between the edge device and the cloud device; a response mode determination module, configured to determine a corresponding registration response mode according to the difference between the first version and the second version when the first version and the second version are different, where the second version is the interface protocol version between the cloud device and the edge device retained in the cloud device; A registration response module, configured to perform a registration response on the edge device according to the registration response method; The version of the interface protocol includes a model version, and the registration extension field also includes document information of the interface protocol; The response mode determination module is used to determine the registration response mode when the model version of the first version is higher than the model version of the second version, including: the model version of the edge device to be confirmed; the registration response module is used to create a first processing flow for confirming the model version; in response to the acceptance operation of the model version in the first processing flow, calling the file synchronization interface according to the document information, obtaining the description document of the interface protocol and the model corresponding to the first version from the edge device; based on the description document and the model corresponding to the first version, updating the model library of the cloud device so that the model of the model library is updated to the first version; in response to the rejection operation of the model version in the first processing flow, synchronizing the model version of the edge device so that the model version of the edge device is synchronized to the second version; The response mode determination module is also used to determine the registration response mode when the model version of the first version is lower than the model version of the second version, including: updating the model version of the edge device; the registration response module is also used to synchronize the model version of the edge device so that the model version of the edge device is synchronized to the second version; and / or send a registration response message to the edge device, and the response extension field of the registration response message includes: a field indicating that the model version of the edge device is to be updated.

13. An electronic device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to call the instructions stored in the memory to execute the method according to any one of claims 1 to 11.

14. A computer-readable storage medium having computer program instructions stored thereon, characterized in that: When the computer program instructions are executed by a processor, the method according to any one of claims 1 to 11 is implemented.

Images