A method and device for dynamically expanding a physical model, and a processing device

Abstract

The present application discloses a method and apparatus for dynamically expanding a physical model, and a processing device, the method comprising: a cloud platform acquiring extended information in a physical model of a first device, the extended information being used to describe an associated device having an associated relationship with the first device; the cloud platform monitoring, based on the extended information in the physical model of the first device, that a physical model file of the associated device is updated, and updating the extended information in the physical model of the first device based on the updated content of the physical model file of the associated device.

Description

Technical Field

[0001] The present application relates to the technical field of Internet of Things (IoT), and in particular to a method and device for dynamically expanding a thing model, and a processing device. Background Art

[0002] The current digital description method of physical devices only describes the logical relationship of a single device's capabilities. The description content is the stacking of the device's functional points, and does not describe the logical relationship when different devices are associated. In addition, the current method is a static description that only describes the current capabilities of the device and does not support the dynamic expansion of device capabilities. This means that in order to update the device's capabilities, the device needs to be re-described from scratch, which makes the operation complicated. Summary of the invention

[0003] In order to solve the above technical problems, the embodiments of the present invention provide a method and apparatus for dynamically expanding a physical model, a processing device, a chip, and a computer-readable storage medium.

[0004] The method for dynamically expanding a physical model provided in an embodiment of the present application includes:

[0005] The cloud platform obtains extended information in the object model of the first device, where the extended information is used to describe an associated device having an associated relationship with the first device;

[0006] The cloud platform monitors that the physical model file of the associated device is updated according to the extended information in the physical model of the first device, and updates the extended information in the physical model of the first device based on the updated content of the physical model file of the associated device.

[0007] The dynamic expansion device of the object model provided in the embodiment of the present application is applied to a cloud platform, and the device includes:

[0008] An acquiring unit, configured to acquire extended information in a thing model of a first device, wherein the extended information is used to describe an associated device having an associated relationship with the first device;

[0009] The updating unit is configured to monitor, according to the extended information in the physical model of the first device, that the physical model file of the associated device is updated, and update the extended information in the physical model of the first device based on the updated content of the physical model file of the associated device.

[0010] The processing device provided in the embodiment of the present application includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute any one of the above-mentioned dynamic expansion methods of the physical model.

[0011] The chip provided in the embodiment of the present application includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes any one of the above methods.

[0012] The core computer-readable storage medium provided in the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute any one of the above methods.

[0013] In the technical solution of the embodiment of the present application, considering the associated device that has an associated relationship with the first device, extended information is added to the physical model of the first device, and the associated device that has an associated relationship with the first device is described through the extended information. Then, the capability of the associated device can be dynamically associated with the first device through the extended information. When the physical model file of the associated device is updated (that is, when the functional point of the associated device changes), the physical model of the first device can be automatically updated, which reduces the complexity of the process, reduces labor costs, and facilitates equipment maintenance and updating. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 It is a schematic diagram of the ICA method of digitally describing physical devices;

[0015] Figure 2 It is a flow chart that expands the functionality of an entity-associated device;

[0016] Figure 3 It is a schematic diagram of a physical model when there is an entity association relationship between a gateway W and a lamp L;

[0017] Figure 4 It is a flow chart for extending the functions of a virtual associated device;

[0018] Figure 5 It is a schematic diagram of a physical model when there is a virtual association relationship between lamps L, SL, and SSL;

[0019] Figure 6 It is a schematic diagram of adding "reference" and "inheritance" methods in the function layer provided in the embodiment of the present application;

[0020] Figure 7 It is a flowchart of a method for dynamically expanding a physical model provided in an embodiment of the present application;

[0021] Figure 8 This is a flow chart of the dynamic expansion of entity association provided by an embodiment of the present application;

[0022] Fig. 9 It is a schematic diagram of a physical model when there is an entity association between a gateway W and a lamp L provided in an embodiment of the present application;

[0023] Fig.10is a flow chart of dynamic expansion of virtual associations provided by an embodiment of the present application;

[0024] Fig.11 It is a schematic diagram of a physical model when there is a virtual association between the lamps L, SL, and SSL provided in an embodiment of the present application;

[0025] Fig.12 It is a schematic diagram of the structure of a dynamic expansion device of a physical model provided in an embodiment of the present application;

[0026] Fig.13 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0027] Fig.14 It is a schematic structural diagram of the chip of an embodiment of the present application. DETAILED DESCRIPTION

[0028] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0029] It should be noted that in the embodiments of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the embodiments of the present application, the character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0030] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.

[0031] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.

[0032] The current method of digitally describing physical devices only describes the logical relationship of a single device’s capabilities. The description content is a stack of the device’s functional points, and does not describe the logical relationship between different devices when they are associated. In addition, the current method is a static description that only describes the device’s current capabilities and does not support dynamic expansion of device capabilities. This means that in order to update device capabilities, the device needs to be re-described from scratch, which makes the operation complicated. Taking the IoT Connectivity Alliance (ICA), an organization currently at the forefront of research, as an example, the method it proposed to digitally describe physical devices describes the functional points of a device from three dimensions: attributes, services, and events. For example, Figure 1 As shown in the figure. Attributes describe the state of the device during operation, such as the power switch, the target temperature of the air conditioner, the brightness of the light, etc.; services describe the actions and instructions that the device performs when it is remotely called, such as device reset, restart, password change, etc.; events are information, alarms, fault notifications, etc. that the device actively reports. At present, other domestic methods for digitally describing devices are basically similar to ICA, such as the ODM object model description method proposed by OneDataModel, which also does not involve the associated logical description of the device.

[0033] The current method only describes the functional points of the device statically, but does not describe the association logic between devices, which includes both physical associations and virtual associations. This results in that when the capabilities of a device are updated, the capabilities of its associated devices cannot be updated synchronously. Specifically:

[0034] In terms of entity association, taking the downlink device and gateway as an example, the specific process of implementing the downlink device and gateway function expansion in the current method is as follows: Figure 2 shown.

[0035] 1. The downstream device adds function 1 and sends a request for object model update to the cloud platform;

[0036] 2. After receiving the update request, the cloud platform updates the object model of the downstream device according to the newly added function 1;

[0037] 3. The cloud platform sends the updated physical model file of the downstream device to the downstream device;

[0038] 4. The user sends instructions to the gateway through the cloud platform, requesting the gateway to send instructions to the downstream device and call function 1;

[0039] 5. The gateway calls the object model file and tries to send instructions to the connected device. At this time, because the object model file of the gateway is not updated accordingly, the function matching of the object model file fails;

[0040] 6. The gateway uploads the log of failed command sending to the cloud platform;

[0041] 7. After receiving the error log feedback from the gateway, the cloud platform updates the physical model file of the gateway;

[0042] 8. The cloud platform sends the updated gateway object model file to the gateway;

[0043] 9. The gateway calls the object model file again, and the object model file function matches successfully.

[0044] 10. The gateway sends control instructions to the connected devices;

[0045] 11. The downstream device executes the command to achieve function 1;

[0046] 12. The downstream device returns the execution result of function 1 to the cloud platform.

[0047] by Figure 3 For example, suppose that lamp L is a short-range communication device, which needs to be connected to the gateway W to achieve connection with the cloud platform, and has "on" and "off" attributes. When describing the function of gateway W, the current method will define that gateway W has the services of "calling lamp L'on' attribute" and "calling lamp L'off' attribute". When the input parameter received by gateway W is "turn on lamp L", the "on" attribute of lamp L will be called; when the input parameter is "turn off lamp L", gateway W will call the "off" attribute of lamp L. Suppose the manufacturer upgraded lamp L and added the "timing" service after the upgrade. At this time, since gateway W did not define "calling lamp L'timing' service" in advance, the user cannot control lamp L through the gateway to achieve timing. If you want to implement this operation, you need to manually re-describe gateway W digitally, and add a definition in the functional description of gateway W: when the input parameter received by gateway W is "timing lamp L", gateway W will call the "timing" service of lamp L. In general, the current method is a static description of the function of device W when describing gateway W. When the function of the hanging device lamp L is updated, it is necessary to manually modify the digital description of gateway W to adapt to the new function of lamp L, which is not easy for subsequent development.

[0048] In terms of virtual association, assuming that device A and device B have a virtual association, the specific process of implementing the function expansion of device A and device B in the current method is as follows: Figure 4 shown.

[0049] 1. Device A adds function 1 and sends a request for updating the object model to the cloud platform;

[0050] 2. The cloud platform updates the physical model of device A;

[0051] 3. The cloud platform sends the physical model file of device A with newly added function 1 to device A;

[0052] 4. Device B adds function 1 and sends a request for updating the object model to the cloud platform;

[0053] 5. The cloud platform updates the object model of device B;

[0054] 6. The cloud platform sends the device B object model file with newly added function 1 to device B.

[0055] by Figure 5 For example, suppose lamp L is a basic lamp with an "on / off" attribute. Based on lamp L, the manufacturer has developed two upgraded lamps, SL and SSL. Lamp SL inherits the "on" and "off" attributes of lamp L, and adds a "brightness" attribute, which can realize the three functions of turning on and off the light, and adjusting the brightness; lamp SSL inherits the "on" and "off" attributes of lamp L and the "brightness" attribute of lamp SL, and adds a "color temperature" attribute, which can realize the four functions of turning on and off the light, adjusting the brightness, and adjusting the color temperature. For this situation, the current method uses a digital description of lamp L, lamp SL, and lamp SSL, respectively, such as Figure 5 As shown, it can be seen that although there is a functional inheritance relationship between lamps L, SL, and SSL, the current method does not reflect this relationship when describing it. Taking lamp SSL as an example, the current method will have the following problems: First, for the inherited "on", "off" and "brightness" attributes, lamp SSL still needs to be defined repeatedly; second, when the "brightness" attribute of lamp SL is updated, the "brightness" attribute of lamp SSL will not be updated accordingly, and the developer needs to manually modify the "brightness" attribute of SSL; third, when lamp L adds a certain function (such as "timing" service), if lamp SSL also wants to have "timing" service, the developer needs to define it manually. In short, there is a lot of duplication of work in the current method, which increases the development and maintenance costs.

[0056] To this end, the following technical solutions of the embodiments of the present application are proposed. The technical solutions of the embodiments of the present application, in view of the problem that the current method lacks device association logic and cannot automatically synchronize the capabilities of associated devices, resulting in high development and maintenance costs, propose a new dynamic expansion method for digitally describing physical devices (that is, a dynamic expansion method for physical models): "reference" and "inheritance" are added to the functional layer, which are respectively used to describe the physical association logic and virtual association logic between devices, simplify the digital description of device capabilities, and realize the synchronous update of the capabilities of associated devices, thereby making device development and maintenance more efficient.

[0057] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0058] The technical solution of the embodiment of the present application proposes a new dynamic expansion method for digitally describing physical devices (that is, a dynamic expansion method for physical models), such as Figure 6 As shown, in addition to "attributes", "services" (also called "behaviors") and "events", "references" and "inheritance" are added to the functional layer. Among them, "attributes", "services" and "events" are used to describe the functional points of the device itself, "references" are used to describe devices that are physically associated with it, and "inheritance" is used to describe devices that are virtually associated with it. In order to realize the dynamic update of device capabilities in "references" and "inheritance", a one-to-one unique identifier is defined for each device, and the identifier can be corresponded to the digital description of the unique device. The identifiers of the referenced device and the inherited device are stored in "references" and "inheritance" respectively. When a certain capability of the referenced device (or inherited device) is needed, it is linked to the referenced device (or inherited device) through the unique identifier, and the relevant capabilities of the device are obtained from the "attributes", "services" and "events" of the device. Furthermore, the capabilities of the referenced (or inherited) device can also be obtained from the "reference" (or "inheritance") of the referenced device (or inherited device).

[0059] Figure 7 is a flow chart of a method for dynamically expanding a physical model provided in an embodiment of the present application, such as Figure 7 As shown, the dynamic expansion method of the object model includes the following steps:

[0060] Step 701: The cloud platform obtains extended information in a thing model of a first device, where the extended information is used to describe associated devices that have an associated relationship with the first device.

[0061] In the embodiment of the present application, a device that has an association relationship with the first device is referred to as an associated device.

[0062] In some optional implementations, the association relationship may be an entity association relationship, and accordingly, a device having an entity association relationship with the first device is referred to as a reference device.

[0063] In some optional implementations, the association relationship may be a virtual association relationship, and accordingly, the device having a virtual association relationship with the first device is referred to as an inheritance device.

[0064] In the embodiment of the present application, the object model of the first device has extended information, and the extended information is used to describe an associated device that has an associated relationship with the first device.

[0065] In some optional embodiments, the extended information includes reference information and / or inheritance information, wherein the reference information is used to describe a first associated device that has an entity association relationship with the first device, and the first associated device refers to a reference device; and the inheritance information is used to describe a second associated device that has a virtual association relationship with the first device, and the second associated device refers to an inheritance device.

[0066] In some optional implementations, the extended information is located at a functional layer of the first device. Figure 6 As shown, "reference" and "inheritance" are introduced in the functional layer, where "reference" represents reference information and "inheritance" represents inheritance information.

[0067] Step 702: The cloud platform monitors that the physical model file of the associated device is updated according to the extended information in the physical model of the first device, and updates the extended information in the physical model of the first device based on the updated content of the physical model file of the associated device.

[0068] In the embodiment of the present application, a one-to-one unique identifier is defined for each device, and the identifier can correspond to a digital description of the unique device (ie, a physical model).

[0069] In an embodiment of the present application, for reference information in the object model of the first device, the reference information includes an identifier of the first associated device; for inheritance information in the object model of the first device, the inheritance information includes an identifier of the second associated device.

[0070] In the embodiment of the present application, the cloud platform monitors that the physical model file of the associated device is updated according to the extended information in the physical model of the first device, which can be achieved in the following ways:

[0071] The cloud platform links to the physical model file of the first associated device based on the identifier in the reference information in the physical model of the first device, and monitors the update of the physical model file of the first associated device; and / or, the cloud platform links to the physical model file of the second associated device based on the identifier in the inheritance information in the physical model of the first device, and monitors the update of the physical model file of the second associated device.

[0072] In the above solution, the physical model file of the first associated device is updated, and the physical model file of the second associated device is updated, which can be achieved by:

[0073] After receiving the physical model update request sent by the first associated device, the cloud platform updates the physical model of the first associated device, and sends the updated physical model file of the first associated device to the first associated device;

[0074] After receiving the object model update request sent by the second associated device, the cloud platform updates the object model of the second associated device and sends the updated object model file of the second associated device to the second associated device.

[0075] In the embodiment of the present application, after the extended information in the physical model of the first device is updated, the cloud platform sends the physical model file of the first device with updated reference information and / or inheritance information to the first device.

[0076] It should be noted that in the above-mentioned scheme of the embodiment of the present application, the object model of the first device, in addition to including extended information (such as reference information, inheritance information), also includes at least one of the following information: attribute information, event information, and service information; wherein the attribute information is used to describe the state of the first device during operation; the event information is used to describe the action performed by the first device when it is remotely called; and the service information is used to describe the information actively reported by the first device.

[0077] The above scheme of the embodiment of the present application, on the one hand, adds "reference" on the basis of the current method, dynamically associates the capability of the associated device (such as the hanging device) to the first device (such as the upper-layer device such as the gateway) according to the unique identifier, and when the functional point of the associated device changes, the physical model of the first device can be automatically updated, which reduces the complexity of the process, reduces the labor cost, and facilitates the maintenance of the equipment. On the other hand, on the basis of the current method, adds "inheritance", dynamically associates the capability of the associated device (such as device A) to the first device (such as device B) with which it has a virtual association relationship (that is, an inheritance relationship) according to the unique identifier, and when the functional point description of the associated device changes, the physical model of the first device (that is, the description information related to the first device) can be automatically updated synchronously, which reduces the labor cost and facilitates the maintenance and update of the equipment.

[0078] The technical solution of the embodiment of the present application is illustrated below with reference to specific application examples.

[0079] Application Example 1

[0080] For entity association, "reference" is used to describe the entity association relationship (that is, entity association logic). In this application example, the first device is a gateway, and the associated device is a downstream device. There is an entity association relationship between the downstream device and the gateway. The specific process of extending the downstream device and gateway functions is as follows: Figure 8 As shown, the following steps are included:

[0081] 1. The downstream device adds function 1 and sends a request for object model update to the cloud platform;

[0082] 2. After receiving the update request, the cloud platform updates the physical model of the downstream device according to the newly added function 1;

[0083] 3. The cloud platform sends the updated physical model file of the downstream device to the downstream device and updates the reference in the gateway physical model at the same time;

[0084] 4. The cloud platform sends the updated referenced gateway object model file to the gateway;

[0085] 5. The user sends instructions to the gateway through the cloud platform, requesting the gateway to send instructions to the downstream device and call function 1;

[0086] 6. The gateway calls the object model file, and the object model file function matches successfully;

[0087] 7. The gateway sends control instructions to the connected devices;

[0088] 8. The downstream device executes the command to achieve function 1;

[0089] 9. The downstream device returns the execution result of function 1 to the cloud platform.

[0090] As an example, Fig. 9 As shown in the figure, lamp L is a device hanging down from gateway W, and is connected to the cloud platform through gateway W. To describe this entity association logic, the unique identifier of lamp L is stored in the "reference" of gateway W, and is linked to the digital description of lamp L through the identifier. Assuming that when lamp L needs to be "turned off", the platform will query the identifier of L from the "reference" of gateway W, and directly call the "off" attribute of L through the identifier to turn off lamp L. When the capability of lamp L is updated, such as adding a "timing" service, the unique identifier of lamp L remains unchanged, so gateway W can still directly call the "timing" service of lamp L through the identifier in the "reference", which greatly reduces the update cost.

[0091] In the above application examples of the present application, for devices with entity association relationships, "references" are added to the method of digitally describing physical devices. After the physical model of the downstream device is updated, on the one hand, the cloud platform will issue the physical model file of the new referenced device, and on the other hand, the cloud platform will monitor the updated content of the physical model file of the downstream device based on the unique identifier, and automatically update the "reference" in the gateway physical model. The technical advantages of adding "references" include at least the following three points: First, when the capabilities of the downstream device are updated, the user can synchronously link to the updated downstream device through the identifier in the "reference", that is, the user can always obtain the latest device capabilities, which is convenient for development; second, this proposal "isolates" the capabilities of the downstream device from the upper-level device by adding "references". When the downstream device is increased, it is only necessary to add the device identifier in the "reference" of the upper-level device, which is simple to operate and easy to maintain; third, the list of devices with entity associations can be intuitively obtained from the "reference", which is convenient for query management.

[0092] Application Example 2

[0093] For virtual association, the virtual association relationship (i.e., virtual association logic) is described by "inheritance". In this application example, the first device is device B, and the associated device is device A. There is a virtual association relationship between device A and device B. The specific process of function expansion of device A and device B is as follows: Fig.10 As shown, the following steps are included:

[0094] 1. Device A adds function 1 and sends a request for updating the object model to the cloud platform;

[0095] 2. The cloud platform updates the physical model of device A;

[0096] 3. The cloud platform sends the device A object model file with newly added function 1 to device A, and updates the inheritance of device B object model at the same time;

[0097] 4. The cloud platform sends the updated inherited device B object model file to device B.

[0098] As an example, Fig.11As shown in the figure, the lamp SL inherits the "on" and "off" attributes of the lamp L, so the unique identifier of the lamp L is stored in the "inheritance" of the lamp SL, and it is linked to L through the identifier to realize the call of the "on" and "off" attributes of L; the lamp SSL inherits the "on" and "off" attributes of the lamp L and the "brightness" attribute of the lamp SL, so the unique identifiers of the lamp L and the lamp SL are stored in the "inheritance" of the lamp SSL, and they are linked to L and SL respectively to realize the call of the "on" and "off" attributes of L and the "brightness" attribute of SL. When the function of the lamp L is increased, such as adding a "timing" service, the lamp SL and SSL can also obtain the newly added "timing" service from L through "inheritance" without repeated development. It should be noted that "inheritance" has the characteristics of synchronous update and forward compatibility, that is, when the lamp L is updated or the function is increased, the lamp SL and SSL can still support the previous version. For the lamp L and the gateway W, it is assumed here that they have not inherited other devices, so the "inheritance" stores a null value, which is represented by a dotted line in the figure.

[0099] In the above application examples of this application, for devices with virtual association relationships, "inheritance" is added to the method of digitally describing physical devices. After the physical model of device A is updated, on the one hand, the cloud platform will issue the new physical model file of device A, and on the other hand, the cloud platform will monitor the updated content of the physical model of device A based on the unique identifier, and automatically update the physical model of device B that has an "inheritance" relationship with device A. The technical advantages of adding "inheritance" are at least the following two points: first, manufacturers can quickly reuse the capabilities of basic devices through "inheritance" to accelerate the development of new devices; second, upper-level devices can add device identifiers in "inheritance" to enable upper-level devices to "inherit" new capabilities, which is simple to operate and easy to upgrade and maintain.

[0100] Fig.12 Schematic diagram of the structure of the dynamic expansion device of the object model provided in the embodiment of the present application, which is applied to terminal equipment, such as Fig.12 As shown, the dynamic expansion device of the object model includes:

[0101] An acquiring unit 1201 is configured to acquire extended information in a thing model of a first device, where the extended information is used to describe an associated device having an associated relationship with the first device;

[0102] The updating unit 1202 is configured to monitor, according to the extended information in the physical model of the first device, that the physical model file of the associated device is updated, and update the extended information in the physical model of the first device based on the updated content of the physical model file of the associated device.

[0103] In some optional embodiments, the extended information includes reference information and / or inheritance information, wherein the reference information is used to describe a first associated device that has an entity association relationship with the first device, and the first associated device refers to a reference device; and the inheritance information is used to describe a second associated device that has a virtual association relationship with the first device, and the second associated device refers to an inheritance device.

[0104] In some optional implementations, the reference information includes an identifier of the first associated device, and the inheritance information includes an identifier of the second associated device.

[0105] In some optional implementations, the updating unit 1202 is specifically configured to:

[0106] Based on the identifier in the reference information in the physical model of the first device, link to the physical model file of the first associated device, and monitor the physical model file of the first associated device to be updated; and / or, based on the identifier in the inheritance information in the physical model of the first device, link to the physical model file of the second associated device, and monitor the physical model file of the second associated device to be updated.

[0107] In some optional implementations, the apparatus further includes: a receiving unit 1203;

[0108] The updating unit 1202 is further used to update the physical model of the first associated device and send the updated physical model file of the first associated device to the first associated device after the receiving unit 1203 receives the physical model update request sent by the first associated device; and / or, after the receiving unit 1203 receives the physical model update request sent by the second associated device, update the physical model of the second associated device and send the updated physical model file of the second associated device to the second associated device.

[0109] In some optional implementations, the apparatus further includes: a sending unit 1204, configured to send the object model file of the first device after the reference information and / or inheritance information is updated to the first device.

[0110] In some optional implementations, the object model of the first device further includes at least one of the following information: attribute information, event information, and service information; wherein:

[0111] The attribute information is used to describe the state of the first device during operation;

[0112] The event information is used to describe the action performed by the first device when it is remotely called;

[0113] The service information is used to describe information actively reported by the first device.

[0114] In some optional implementations, the extended information is located in a functional layer of the first device.

[0115] Those skilled in the art should understand that Fig.12 The implementation functions of each unit in the dynamic expansion device of the physical model shown can be understood by referring to the relevant description of the aforementioned method. Fig.12 The functions of each unit in the dynamic expansion device of the physical model shown can be implemented by a program running on a processor, or by a specific logic circuit.

[0116] Fig.13 It is a schematic structural diagram of a processing device 1300 provided in an embodiment of the present application. Fig.13 The processing device 1300 shown includes a processor 1310, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0117] Alternatively, if Fig.13 As shown, the processing device 1300 may further include a memory 1320. The processor 1310 may call and run a computer program from the memory 1320 to implement the method in the embodiment of the present application.

[0118] The memory 1320 may be a separate device independent of the processor 1310 , or may be integrated into the processor 1310 .

[0119] Alternatively, if Fig.13 As shown, the processing device 1300 may further include a transceiver 1330, and the processor 1310 may control the transceiver 1330 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0120] The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include an antenna, and the number of antennas may be one or more.

[0121] The processing device 1300 may specifically be a cloud platform of an embodiment of the present application, and the processing device 1300 may implement the corresponding processes implemented by the cloud platform in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0122] Fig.14 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig.14The chip 1400 shown includes a processor 1410, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0123] Alternatively, if Fig.14 As shown, the chip 1400 may further include a memory 1420. The processor 1410 may call and run a computer program from the memory 1420 to implement the method in the embodiment of the present application.

[0124] The memory 1420 may be a separate device independent of the processor 1410 , or may be integrated into the processor 1410 .

[0125] Optionally, the chip 1400 may further include an input interface 1430. The processor 1410 may control the input interface 1430 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0126] Optionally, the chip 1400 may further include an output interface 1440. The processor 1410 may control the output interface 1440 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0127] The chip can be applied to the cloud platform in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the cloud platform in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0128] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0129] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0130] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0131] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0132] The embodiment of the present application also provides a computer-readable storage medium for storing a computer program. The computer-readable storage medium can be applied to the cloud platform in the embodiment of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the cloud platform in each method of the embodiment of the present application, which will not be described here for the sake of brevity.

[0133] The present application also provides a computer program product, including computer program instructions. The computer program product can be applied to the cloud platform in the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the cloud platform in each method of the present application, which will not be described here for brevity.

[0134] The present application also provides a computer program. The computer program can be applied to the cloud platform in the present application, and when the computer program is run on a computer, the computer executes the corresponding process implemented by the cloud platform in each method of the present application, which will not be described in detail for the sake of brevity.

[0135] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0136] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0137] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0138] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0139] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0140] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0141] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for dynamically expanding a physical model, characterized in that: The method comprises: The cloud platform obtains extended information in the object model of the first device, where the extended information is used to describe an associated device having an associated relationship with the first device; the extended information includes reference information and / or inheritance information, where the reference information is used to describe a first associated device having an entity associated relationship with the first device, and the first associated device refers to a reference device; and the inheritance information is used to describe a second associated device having a virtual associated relationship with the first device, and the second associated device refers to an inheritance device; The cloud platform monitors that the physical model file of the associated device is updated according to the extended information in the physical model of the first device, and updates the extended information in the physical model of the first device based on the updated content of the physical model file of the associated device.

2. The method according to claim 1, characterized in that The reference information includes an identifier of the first associated device, and the inheritance information includes an identifier of the second associated device.

3. The method according to claim 2, characterized in that The cloud platform monitors, according to the extended information in the physical model of the first device, that the physical model file of the associated device is updated, including: The cloud platform links to the physical model file of the first associated device according to the identifier in the reference information in the physical model of the first device, and monitors that the physical model file of the first associated device is updated; and / or, The cloud platform links to the physical model file of the second associated device according to the identifier in the inheritance information in the physical model of the first device, and monitors that the physical model file of the second associated device is updated.

4. The method according to claim 3, characterized in that The method further comprises: After receiving the physical model update request sent by the first associated device, the cloud platform updates the physical model of the first associated device and sends the updated physical model file of the first associated device to the first associated device; and / or, After receiving the object model update request sent by the second associated device, the cloud platform updates the object model of the second associated device and sends the updated object model file of the second associated device to the second associated device.

5. The method according to any one of claims 1 to 4, characterized in that After updating the extended information in the object model of the first device, the method further includes: The cloud platform sends the physical model file of the first device after the reference information and / or inheritance information is updated to the first device.

6. The method according to any one of claims 1 to 4, characterized in that The object model of the first device also includes at least one of the following information: attribute information, event information, and service information; wherein: The attribute information is used to describe the state of the first device during operation; The event information is used to describe the action performed by the first device when it is remotely called; The service information is used to describe information actively reported by the first device.

7. The method according to any one of claims 1 to 4, characterized in that The extended information is located at a function layer of the first device.

8. A dynamic expansion device for a physical model, characterized in that: Applied to a cloud platform, the device comprises: an acquisition unit, configured to acquire extended information in a thing model of a first device, wherein the extended information is used to describe an associated device having an associated relationship with the first device; the extended information includes reference information and / or inheritance information, wherein the reference information is used to describe a first associated device having an actual associated relationship with the first device, and the first associated device is referred to as a reference device; and the inheritance information is used to describe a second associated device having a virtual associated relationship with the first device, and the second associated device is referred to as an inheritance device; The updating unit is configured to monitor, according to the extended information in the physical model of the first device, that the physical model file of the associated device is updated, and update the extended information in the physical model of the first device based on the updated content of the physical model file of the associated device.

9. A processing device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 7.

10. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 7.

11. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 7.

Images