Cross-platform interaction control method, electronic equipment, readable storage medium and program product

Abstract

The invention relates to a cross-platform interaction control method and device, electronic equipment, a readable storage medium and a program product, and relates to the technical field of Internet of Things. According to the invention, the control of the device control scheme on the intelligent device can be carried out in a cross-platform cooperation manner, and the cross-platform interaction operation experience is enriched. The method comprises the following steps: in response to a binding operation for a created device control scheme in a first application, binding the device control scheme to a network device as a virtual sub-device of the network device; the network equipment has a cross-platform interaction capability; and in response to a device binding operation for the network device in the second application, binding the network device and the virtual sub-device to the second application, so that the device control scheme of the virtual sub-device is controlled through the network device in the second application, and cross-platform control is performed on the corresponding intelligent device in the first application.

Description

Technical Field

[0001] The present application relates to the technical field of Internet of Things, and in particular to a cross-platform interactive control method, device, electronic device, readable storage medium and program product. Background Art

[0002] With the development of Internet of Things (IOT) technology, IoT devices are widely used in smart home and other fields. More and more platforms provide users with device maintenance and control functions in applications. For example, users can create automation solutions in applications for the maintenance and control of smart home devices.

[0003] In current technologies, the device control solutions provided by different platforms in their respective applications cannot be coordinated and have certain limitations. Summary of the invention

[0004] Based on this, it is necessary to provide a cross-platform interactive control method, device, electronic device, readable storage medium and program product to address the above technical problems.

[0005] In a first aspect, the present application provides a cross-platform interactive control method, comprising:

[0006] In response to a binding operation for the created device control scheme in the first application, the device control scheme is bound to the network device as a virtual sub-device of the network device; the network device is a network device with cross-platform interaction capability;

[0007] In response to a device binding operation for the network device in a second application, the network device and the virtual sub-device are bound to the second application, so that the device control scheme of the virtual sub-device is controlled by the network device in the second application, so as to perform cross-platform control on the corresponding smart device in the first application.

[0008] In a second aspect, the present application provides a cross-platform interactive control method, comprising:

[0009] Acquire a device control instruction triggered in a second application; the second application is bound to a network device with cross-platform interaction capability and a virtual sub-device of the network device; the virtual sub-device is created based on a device control solution corresponding to the smart device in the first application;

[0010] If the controlled device targeted by the device control instruction is the virtual sub-device, the corresponding intelligent device in the first application is controlled by the network device based on the device control solution of the virtual sub-device.

[0011] In a third aspect, the present application also provides a cross-platform interactive control device, including:

[0012] A first binding module, configured to respond to a binding operation on a created device control scheme in a first application, and bind the device control scheme as a virtual sub-device of a network device to the network device; the network device is a network device with cross-platform interaction capability;

[0013] A second binding module is used to bind the network device and the virtual sub-device to the second application in response to a device binding operation for the network device in the second application, so that the device control scheme of the virtual sub-device can be controlled by the network device in the second application to perform cross-platform control on the corresponding smart device in the first application.

[0014] In a fourth aspect, the present application also provides a cross-platform interactive control device, including:

[0015] An instruction acquisition module, used to acquire a device control instruction triggered in a second application; the second application is bound to a network device with cross-platform interaction capability and a virtual sub-device of the network device; the virtual sub-device is created based on a device control solution corresponding to the smart device in the first application;

[0016] The device control module is used to control the corresponding intelligent device in the first application through the network device based on the device control scheme of the virtual sub-device if the controlled device targeted by the device control instruction is the virtual sub-device.

[0017] In a fifth aspect, the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0018] In response to a binding operation for a created device control scheme in a first application, the device control scheme is bound to the network device as a virtual sub-device of the network device; the network device is a network device with cross-platform interaction capabilities; in response to a device binding operation for the network device in a second application, the network device and the virtual sub-device are bound to the second application, so that the device control scheme of the virtual sub-device is controlled by the network device in the second application, so as to perform cross-platform control on the corresponding smart device in the first application.

[0019] In a sixth aspect, the present application further provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0020] Obtain a device control instruction triggered in a second application; the second application is bound to a network device with cross-platform interaction capabilities and a virtual sub-device of the network device; the virtual sub-device is created based on a device control scheme corresponding to the smart device in the first application; if the controlled device targeted by the device control instruction is the virtual sub-device, the corresponding smart device in the first application is controlled by the network device based on the device control scheme of the virtual sub-device.

[0021] In a seventh aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0022] In response to a binding operation for a created device control scheme in a first application, the device control scheme is bound to the network device as a virtual sub-device of the network device; the network device is a network device with cross-platform interaction capabilities; in response to a device binding operation for the network device in a second application, the network device and the virtual sub-device are bound to the second application, so that the device control scheme of the virtual sub-device is controlled by the network device in the second application, so as to perform cross-platform control on the corresponding smart device in the first application.

[0023] In an eighth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0024] Obtain a device control instruction triggered in a second application; the second application is bound to a network device with cross-platform interaction capabilities and a virtual sub-device of the network device; the virtual sub-device is created based on a device control scheme corresponding to the smart device in the first application; if the controlled device targeted by the device control instruction is the virtual sub-device, the corresponding smart device in the first application is controlled by the network device based on the device control scheme of the virtual sub-device.

[0025] In a ninth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0026] In response to a binding operation for a created device control scheme in a first application, the device control scheme is bound to the network device as a virtual sub-device of the network device; the network device is a network device with cross-platform interaction capabilities; in response to a device binding operation for the network device in a second application, the network device and the virtual sub-device are bound to the second application, so that the device control scheme of the virtual sub-device is controlled by the network device in the second application, so as to perform cross-platform control on the corresponding smart device in the first application.

[0027] In a tenth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0028] Obtain a device control instruction triggered in a second application; the second application is bound to a network device with cross-platform interaction capabilities and a virtual sub-device of the network device; the virtual sub-device is created based on a device control scheme corresponding to the smart device in the first application; if the controlled device targeted by the device control instruction is the virtual sub-device, the corresponding smart device in the first application is controlled by the network device based on the device control scheme of the virtual sub-device.

[0029] The above-mentioned cross-platform interactive control method, apparatus, electronic device, readable storage medium and program product, in response to a binding operation for a created device control scheme in a first application, binds the device control scheme to the network device as a virtual sub-device of the network device; the network device is a network device with cross-platform interactive capabilities; in response to a device binding operation for the network device in a second application, binds the network device and the virtual sub-device to the second application, so that in the second application, the device control scheme of the virtual sub-device is controlled by the network device to perform cross-platform control on the corresponding smart device in the first application, thereby based on the created device control scheme in the first application, the device control scheme can be bound to the network device with cross-platform interactive capabilities in the form of a virtual sub-device in the first application, and the network device and the virtual sub-device are bound to the second application in the second application, thereby controlling the device control scheme of the virtual sub-device in the second application to perform cross-platform control on the corresponding smart device in the first application, so that the control of the smart device by the device control scheme can be carried out in a cross-platform collaborative manner, thereby enriching the cross-platform interactive operation experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0031] Figure 1 is an application environment diagram of a cross-platform interactive control method in an embodiment;

[0032] Figure 2 A schematic diagram of a cross-platform interaction scenario in an embodiment;

[0033] Figure 3 is a schematic diagram of cross-platform interaction of a smart home scenario in one embodiment;

[0034] Figure 4 is a schematic flow chart of a cross-platform interactive control method in one embodiment;

[0035] Figure 5(a) to Figure 5(c) A diagram of an interface for creating a solution based on a signal in one embodiment;

[0036] Figure 6 A diagram of an interface for creating a solution based on a scenario in an embodiment;

[0037] Figure 7(a) to Figure 7(c) A diagram of an interface for binding a virtual sub-device to a network device in one embodiment;

[0038] Figure 8(a) to Figure 8(f) A diagram of an interface for binding a network device and its virtual sub-devices in one embodiment;

[0039] Fig. 9 A schematic diagram of a process for configuring an automation solution in one embodiment;

[0040] Figure 10(a) to Figure 10(d) Related surface diagrams for configuring automation solutions;

[0041] Fig.11 A schematic diagram of a process for generating a target control scheme in one embodiment;

[0042] Fig.12 is a flow chart of a cross-platform interactive control method in another embodiment;

[0043] Fig.13 A schematic diagram of a process for obtaining a device control instruction in an embodiment;

[0044] Fig.14 is a structural block diagram of a cross-platform interactive control device in an embodiment;

[0045] Fig.15 is a structural block diagram of a cross-platform interactive control device in another embodiment;

[0046] Fig.16 FIG. 4 is a diagram showing the internal structure of an electronic device in one embodiment. DETAILED DESCRIPTION

[0047] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0048] The cross-platform interactive control method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. The application environment can be a smart home system, which may include: cloud / cloud servers, routers, gateways, user terminals (such as mobile phones, tablets), multiple devices (such as smart lamps, smart sockets, smart curtains, smart air conditioners, sensors, switches, smart door locks), etc. In the smart home system, each device can be connected to the gateway through the ZIGBEE / Bluetooth / matter network, and the gateway and user terminal can be connected to the router through WiFi respectively. In addition, the user terminal can also establish a network connection with the cloud / cloud server through 2G / 3G / 4G / 5G, WiFi, etc., so that it can obtain the data sent by the cloud / cloud server.

[0049] For the smart home system, the system configuration method can be: the user terminal is equipped with the corresponding application (application program), and at least one gateway device can be added to the application first. When adding other devices (such as smart door locks), you can click the Add Device button in the application interface and select the gateway device that the device needs to access in the Add interface. Then, the device can be added to the matter network corresponding to the gateway, and then form a matter local area network with other added devices and gateways. When the application, router, and gateway are in the same local area network, the application can interact with the gateway and the devices connected to the gateway through the local area network path; when the application, router, and gateway are not in the same local area network, the application can interact with the gateway and the devices connected to the gateway through the wide area network path.

[0050] like Figure 1In the smart home system shown, according to current technology, different platforms (or ecosystems) can provide their own applications on user terminals (such as mobile phones and tablets). For each platform's application, users can create device control plans in the application, but their device control plans can only be set under the platform where the application is located, and cannot be coordinated with other platforms or interact across platforms, which has certain limitations.

[0051] In this regard, the cross-platform interactive control method provided by the present application is that the terminal can bind the device control scheme to a network device with cross-platform interactive capabilities in the form of a virtual sub-device in the first application based on the device control scheme created in the first application, and bind the network device and the virtual sub-device to the second application in the second application. In this way, the device control scheme of the virtual sub-device can be controlled through the network device in the second application to perform cross-platform control of the corresponding smart device in the first application, so that the control of the smart device by the device control scheme can be carried out in a cross-platform collaborative manner, thereby enriching the cross-platform interactive operation experience.

[0052] As an example, Figure 2 As shown, the gateway device can be used as a central device to assist in implementing the cross-platform interactive control method. The central device can have a multi-protocol gateway function. The central device can support multiple smart device protocols such as Matter, Zigbee and Bluetooth to achieve seamless connection of devices with different protocols. The device can access the Internet via WiFi or Ethernet and exchange data with the remote server to ensure the update of system configuration and the implementation of remote control. The central device can have efficient data processing and storage capabilities, and can perform smart home automation and scene control tasks locally. Users can create, modify and store automation scripts and control scenes through applications (Apps), and can save and execute them locally on the central device to optimize system response time and operational stability. The central device can also convert non-Matter-supported devices into Matter-supported devices, making them compatible with different applications on different smart platforms. This bridging function expands the application range of the device and the adaptability of the scene, which can enhance the overall interoperability of the smart home system.

[0053] As an example, Figure 3As shown, based on the cross-platform interactive control method provided by the present application, the scene of the smart home system can be synchronized to the interactive process of Matter in the form of a virtual sub-device. The scene list interface of the smart home control application is displayed in the application interface part of application B. Users can view and edit scenes on this interface and add execution actions of various smart devices (such as lamps, curtains, air purifiers, etc.) to the scene. In addition, the application interface can also provide device status and executable automation action lists, such as turning on the lights, closing the curtains, adjusting the temperature, etc. In the central device part, the gateway device can be used as a home control central device and Matter bridge, assuming the role of a multi-protocol gateway, and can connect and manage smart home devices of different protocols. It can be responsible for receiving control commands from the application interface and forwarding these control commands to the corresponding devices for execution. At the same time, it can also feedback the device status back to the application interface. The gateway device can have efficient data processing and storage capabilities, and can perform smart home automation and scene control tasks locally. Users can create, modify and store automation scripts and control scenes through applications (Apps), and they can all be saved and executed locally on the gateway device, optimizing system response time and operation stability. At the same time, the gateway device can also be a bridge (Matter Bridge) for Matter devices, so that non-Matter devices can also work in the Matter ecosystem, and can help applications create virtual sub-devices and synchronize them to the Matte ecosystem. In the virtual sub-device part, such as the plug-in Outlet, it can be a smart switch, which can be a virtual sub-device created by the gateway device, which enables non-physical entities to operate in the smart home platform and interact with other physical devices through the hub device. In the AIOT (Artificial Intelligence of Things) cloud platform part, the AIOT cloud platform can be a back-end service for remote access and data analysis. It can communicate with the hub device through the Internet to achieve synchronization of device status, issuance of remote control instructions, and data processing functions. For the Matter ecosystem part, it can include different ecological platforms. The ecological platform can be an open source smart home control platform for managing and controlling connected smart devices. The ecological platform can also support Matter's ecological platform, can connect Matter devices, and can include Matter bridges and Matter devices. Therefore, it can be used in conjunction with the above-mentioned hub devices to achieve more complex automation scenarios.For example, a central device can be added to applications A and B of the above-mentioned open source smart home control platform. In application B of the central device, a virtual sub-device can be bound to application A of the open source smart home control platform with the help of the central device with the Matter function. The virtual sub-device can correspond to the device control scheme of application B, such as turning on all the lights in the living room. Therefore, the device control scheme of the virtual sub-device can be controlled in application A through the central device according to the virtual sub-device, so as to perform cross-platform control of smart devices such as the corresponding smart lights in application B.

[0054] As an example, Figure 3 As shown, the overall interaction process can be as follows:

[0055] First, users can create device control schemes in the smart home application B, which may include turning on all bedroom lights, turning off all bedroom lights, turning on all living room lights, etc. These device control schemes can be transmitted to the central device through the network, and the central device can create or activate corresponding virtual sub-devices in the Matter network through the Matter bridge based on the device control scheme. In the application A of the third-party platform, the central device and the virtual sub-device can be bound to the application A, and the virtual sub-device can be applied in the automation scheme of the application A. For example, the virtual sub-device can be applied in the trigger condition of the automation scheme, so that when the living room lights in the aforementioned application B are fully turned on, the target action or scene of the automation scheme in the application A is executed, so that the corresponding smart devices in the application B can be controlled cross-platform through the central device in the application A, such as adjusting the lights, temperature, etc. The status of these smart devices and the execution status of the actions can be recorded in the signal logs (Signals Logs) of applications A and B for user monitoring and review. As a result, the scenarios of the smart home system can not only be used in its own ecosystem, but also can be expanded with the help of hub devices, cloud platforms, applications, etc. and other platforms in the Matter ecosystem to achieve more complex and personalized home automation solutions.

[0056] The cross-platform interactive control method of the present application is described below through various embodiments and corresponding drawings.

[0057] In an exemplary embodiment, Figure 4 As shown, a cross-platform interactive control method is provided, which can be applied to Figure 1 The user terminal shown in the figure may include the following steps:

[0058] Step S401, in response to a binding operation on a created device control scheme in a first application, the device control scheme is bound to a network device as a virtual sub-device of the network device. The network device is a network device with cross-platform interaction capability.

[0059] The first application may be an application for controlling smart devices in the space. The first application may provide a device control scheme to control the smart devices. As an example, the smart devices may include smart lamps, smart sockets, smart curtains, smart air conditioners, sensors, switches, smart door locks, etc.

[0060] The device control scheme is a scheme for controlling smart devices. The user can create a corresponding device control scheme for one or more smart devices in the space in the first application to control the one or more smart devices. The user can create one or more device control schemes in the first application.

[0061] The binding operation for the created device control scheme in the first application refers to an operation for binding the created device control scheme to the network device, which may be an operation such as clicking.

[0062] The user terminal may respond to the binding operation for the created device control scheme in the first application by binding the created device control scheme to the network device as a virtual sub-device of the network device. The first application may be as follows: Figure 3 Application B shown in .

[0063] Among them, the network device is a network device with cross-platform interaction capabilities, and the network device can serve as a hub device for each smart device in the target space. The network device can support multiple smart device protocols such as Matter, Zigbee and Bluetooth to achieve seamless connection of devices with different protocols. The network device can be a bridge (MatterBridge) for Matter devices, so that non-Matter devices can also work in the Matter ecosystem, and can convert non-Matter-supported smart devices into Matter-supported smart devices, so that they can be compatible with different applications on different platforms / ecosystems. This bridging function can expand the application scope of the device and the adaptability of the scene, and can enhance the overall interoperability of smart home systems, for example.

[0064] Among them, network devices can help applications create virtual sub-devices and synchronize them to the Matte ecosystem.

[0065] Among them, the Matter protocol is an emerging open source IP protocol connection standard. It is an application-level standard developed by the Connection Standards Alliance. It is based on the TCP and UDP protocols of IPv6, supports three underlying communication protocols: Ethernet, Wi-Fi, and Thread, and allows smart devices with different protocols to communicate with each other. The Matter protocol aims to create a unified smart device application standard to eliminate the fragmentation of smart devices of different brands and platforms, simplify manufacturers' development and improve consumer compatibility, so that devices of different brands and platforms can work together seamlessly, achieve interoperability between smart devices of different brands and platforms, and enable users to use one application or voice assistant to control a variety of smart devices of different brands. For example, the Matter protocol is compatible with multiple smart home platforms, including Aqara Home, Apple HomeKit, Google Assistant, Amazon Alexa, and more.

[0066] In this step, the user terminal can bind the created device control scheme to the network device as a virtual sub-device of the network device, and the network device can create a corresponding virtual sub-device according to the device control scheme to complete the binding of the device control scheme as a virtual sub-device of the network device. Thus, through the virtual sub-device created by the network device, non-physical entities can also operate on different platforms and interact with other physical devices through the network device.

[0067] Step S402, in response to the device binding operation for the network device in the second application, the network device and the virtual sub-device are bound to the second application, so that the device control scheme of the virtual sub-device is controlled by the network device in the second application to perform cross-platform control on the corresponding smart device in the first application.

[0068] The second application may be an application belonging to a different platform / ecosystem than the first application, and the first application and the second application may be used to maintain and control smart devices of their respective platforms. Figure 3 Application A shown in .

[0069] The second application may be bound to the network device, and the device binding operation for the network device refers to an operation for binding the network device in the second application, which may include operations such as clicking.

[0070] Among them, the user terminal can respond to the device binding operation for the network device in the second application, and the user terminal can obtain the network device and the virtual sub-device and bind them to the second application. As a result, the device control scheme of the virtual sub-device can be controlled by the network device in the second application, thereby realizing cross-platform control of the corresponding smart device in the first application. Among them, based on the device control scheme of the virtual sub-device, the corresponding smart lamps, smart sockets, smart curtains, smart air conditioners, sensors, switches, smart door locks, etc. in the first application can be controlled by the virtual sub-device, for example.

[0071] The cross-platform interactive control method of this embodiment, in response to a binding operation for a created device control scheme in a first application, binds the device control scheme to the network device as a virtual sub-device of the network device; the network device is a network device with cross-platform interactive capabilities; in response to a device binding operation for the network device in a second application, binds the network device and the virtual sub-device to the second application, so that in the second application, the device control scheme of the virtual sub-device is controlled by the network device to perform cross-platform control on the corresponding smart device in the first application, thereby, based on the created device control scheme in the first application, the device control scheme can be bound to the network device with cross-platform interactive capabilities in the form of a virtual sub-device in the first application, and the network device and the virtual sub-device can be bound to the second application in the second application, thereby, the device control scheme of the virtual sub-device can be controlled by the network device in the second application to perform cross-platform control on the corresponding smart device in the first application, so that the control of the smart device by the device control scheme can be performed collaboratively across platforms, thereby enriching the cross-platform interactive operation experience.

[0072] In one exemplary embodiment, in response to a binding operation for a created device control scheme in the first application in step S401, before binding the device control scheme as a virtual sub-device of the network device to the network device, the method of the present application may further create the device control scheme in the first application through the following steps, including:

[0073] A solution configuration page is displayed in the first application; the solution configuration page includes a smart device in the first application; in response to a solution configuration operation for a selected smart device in the solution configuration page, a device control solution is created based on device solution information for the selected smart device.

[0074] The solution configuration page refers to a page for configuring the device control solution in the first application. The solution configuration page may include smart devices in the first application. The number of smart devices displayed in the solution configuration page may be one or more, and the types of smart devices displayed may be one or more. As an example, the solution configuration page may include smart lamps, smart sockets, smart curtains, smart air conditioners, sensors, switches, smart door locks, etc. in the first application.

[0075] The user terminal can display the solution configuration page of multiple smart devices including the first application in the first application, so that the user can configure the device control solution.

[0076] The solution configuration operation for the selected smart device refers to the operation of configuring the device control solution for one or more smart devices selected by the user in the solution configuration page, which may include a series of click operations.

[0077] In response to the scheme configuration operation for the selected smart device in the scheme configuration page, the user terminal can obtain the device scheme information for the selected smart device. The device scheme information for the selected smart device refers to the control scheme information formed according to the device information of the selected smart device. The device information of the smart device may include the function, location, model, etc. of the smart device, and the control scheme information may include control conditions, control objects, execution actions, etc. Control mode information such as control conditions, control objects, execution actions, etc. can be formed according to the device information such as the function, location, model, etc. of the smart device.

[0078] After obtaining the device solution information for the selected smart device in the first application, the user terminal may create a device control solution in the first application according to the device solution information.

[0079] The solution of this embodiment can create a device control scheme in the first application, and select the smart devices in the first application that can be provided to the second application for cross-platform interactive control into the device control scheme, thereby facilitating the selection and management of smart devices for cross-platform interactive control.

[0080] In some embodiments, the solution configuration page includes a first solution configuration page; the device solution information includes an event signal reported by a smart device for configuring an automation solution and / or a device action performed by the smart device; in response to a solution configuration operation for a selected smart device in the solution configuration page, creating a device control solution according to the device solution information for the selected smart device in the above embodiments may include:

[0081] In response to a selection operation of a smart device corresponding to an event signal in a first solution configuration page, the event signal supported by the selected smart device is displayed; and / or, in response to a selection operation of a smart device corresponding to a device action in the first solution configuration page, the device action supported by the selected smart device is displayed; based on the event signal of the selected smart device and / or the device action of the smart device, a device control solution is created.

[0082] In this embodiment, the solution configuration page may include a first solution configuration page, which may be used as a page in the first application for creating / configuring one of the device control solutions. The device control solution may include an automation solution. The first solution configuration page may support the creation / configuration of the automation solution in the first application.

[0083] The automation scheme in the first application may include trigger conditions and target actions. The trigger conditions may be set according to the event signals reported by the smart device. The event signals may be determined according to the functions and types of the smart devices. For example, the event signal corresponding to the camera may include the recognition of a specific face; the event signal corresponding to the human body sensor may include the detection of a person in the target area; for example, the event signal corresponding to the smart light may include event signals corresponding to functions such as the smart light being turned on, the smart light being turned off, the brightness of the smart light being adjusted, the color temperature being adjusted, etc., such as the brightness reaching a certain value, the color temperature reaching a certain value, etc. can be used as its event signal. The event signal may also include turning on a preset automation scheme, turning off a preset automation scheme, and so on.

[0084] The target action can be set according to the executable functions and device actions of the smart device. The device action can also be determined according to the function and type of the smart device. For example, for a smart light, the device action may include device actions corresponding to functions such as turning on the smart light, turning off the smart light, adjusting the brightness of the smart light, and adjusting the color temperature. For example, adjusting the brightness to a certain value, adjusting the color temperature to a certain value, etc. can be used as its device action.

[0085] Thus, the user terminal can display the smart devices corresponding to the event signal in the first solution configuration page of the first application, and the user terminal can respond to the selection operation of the smart device corresponding to the event signal in the first solution configuration page, and then display the event signal supported by the selected smart device. The user terminal can also display the smart devices corresponding to the device action in the first solution configuration page of the first application, and the user terminal can respond to the selection operation of the smart device corresponding to the device action in the first solution configuration page, and then display the device action supported by the selected smart device.

[0086] Among them, the device control plan can be created through the above-mentioned event signal, the device control plan can be created through the above-mentioned device action, and the device control plan can also be created through event signals and device actions.

[0087] Thus, the user terminal can create a device control scheme based on the event signal of the selected smart device. The user terminal can also create a device control scheme based on the device action of the selected smart device. The user terminal can also create a device control scheme based on the event signal of the selected smart device and the device action of the smart device, wherein the smart device in the event signal of the selected smart device and the smart device in the device action of the selected smart device can be different smart devices or the same smart device.

[0088] As an application example, Figure 5(a) to Figure 5(c) As shown, you can enter the automation page in the first application, click the "+" in the upper right corner of the automation page, select "New Signal" to enter the "New Signal" editing page, and you can create a device control plan by creating a new signal. For example, you can create a device control plan based on the recognition of a specified face, tony, or you can batch check signals in the edit signal list and add them to Matter in batches to create a device control plan. In the edit signal list, you can mark the signals that have been used to create device control plans.

[0089] The solution of this embodiment can create a device control solution through event signals reported by smart devices used to configure the automation solution and / or device actions performed by smart devices. In the first application, the event signals and / or device actions of the smart devices can be provided to the second application in the form of virtual sub-devices for cross-platform interactive control. As a result, the event signals in the first application can be selected as trigger conditions for automation in the second application. The device actions performed by the smart devices in the first application can also be selected in the second application as target actions for automation, thereby improving the flexibility and convenience of virtual sub-device configuration and enhancing the richness of cross-platform interactive control.

[0090] In some other embodiments, the solution configuration page includes a second solution configuration page; the device solution information includes a device function corresponding to the scene; in response to the solution configuration operation for the selected smart device in the solution configuration page in the above embodiment, according to the device solution information for the selected smart device, creating a device control solution may include:

[0091] In response to a selection operation for a smart device in the second solution configuration page, device functions corresponding to the scenarios supported by the selected smart device are displayed; in response to a selection operation for a device function, a device control solution is created based on the selected device function.

[0092] In this embodiment, the scheme configuration page may include a second scheme configuration page, which can be used as a page in the first application for creating / configuring other device control schemes. The device control scheme may include a scheme for controlling the device in a scene. Among them, the scene can be a scene that can be executed in the first application, and specifically may include a scene control scheme and a device control scheme for one or more devices, and may also include a preset automation control scheme, etc. The second scheme configuration page can support the creation / configuration of a scheme for controlling the device in the scene in the first application. As an example, the scene can be configured to turn off all bedroom lights, and when executing this scene, some or all smart lights in a specified or all bedrooms can be turned off.

[0093] Thus, the user terminal can display one or more smart devices in the second solution configuration page of the first application, and the user terminal can respond to the selection operation for the smart device in the second solution configuration page, and then display the device function corresponding to the scene supported by the selected smart device. Among them, the device function can be determined according to information such as the type of the smart device, such as the device function corresponding to the scene supported by the smart light can include brightness adjustment, color temperature adjustment, etc. The device control solution can be created using one or more device functions corresponding to the scene supported by the smart device.

[0094] Thus, the user terminal can determine the selected device function in response to the selection operation for the device function, and create a device control scheme based on the selected device function. Among them, one or more device functions corresponding to the scenarios supported by the smart device can be selected to create a device control scheme.

[0095] As an application example, Figure 6 As shown, you can enter the scene page in the first application, long press the scene icon to enter the scene editing page, you can check one or more scenes of the first application in the scene editing page, and click "Add to Matter" to use the device function corresponding to the checked scene to create a device control solution. In the scene editing page, you can mark the scenes that have been used to create device control solutions.

[0096] The solution of this embodiment can utilize the scene in the first application to create a device control solution for cross-platform interactive control in the second application, thereby improving the reusability of the scene in the first application, and also improving the flexibility and convenience of forming virtual sub-device configurations, and enhancing the richness of cross-platform interactive control.

[0097] In one exemplary embodiment, in response to a binding operation on a created device control scheme in the first application, step S401 of binding the device control scheme to the network device as a virtual sub-device of the network device may include:

[0098] A binding entry for a created device control scheme is displayed in a first application; the binding entry includes a binding entry for binding the created device control scheme to a network device; in response to a binding operation on the binding entry, the device control scheme is bound to the network device as a virtual sub-device of the network device.

[0099] In this embodiment, after the device control scheme is created, the binding entry for the created device control scheme may be displayed in the first application.

[0100] The binding entry refers to an entry for binding the created device control solution to the network device in the form of a virtual sub-device in the first application. The binding entry may include a binding entry for binding the created device control solution to the network device.

[0101] The binding operation for the binding entry may include operations such as clicking.

[0102] The user terminal may bind the created device control solution to the network device as a virtual sub-device of the network device in response to the binding operation on the binding entry in the first application.

[0103] As an application example, Figure 7(a) to Figure 7(c) As shown, after creating a device control scheme in the first application, such as creating a device control scheme for "Tony detected" in FIG7(a), check "Add to matter" and click the binding entry to confirm. Referring to FIG7(b), you can also create a device control scheme for "Leaving home" and click the binding entry for "Add to matter". The first application jumps to the list page of network devices, such as FIG7(c). Then you can select network device 1 to bind the device control scheme to network device 1 as a virtual sub-device of network device 1.

[0104] In actual applications, if the user has not checked the record of a certain network device, the user can be guided to select the corresponding network device in the first application. If the user has checked the network device before, the network device can be selected by default when entering this page later. If the user has currently added multiple network devices, and the user wants to switch to other network devices as the network devices that need to be bound to the device control scheme, the user can be prompted to check the impact warning of other network devices, and the relevant impact information can be prompted in the impact warning. If there is currently no available network device or no network device, the user can be prompted that the binding function is not currently supported, and the user can be guided to add a network device.

[0105] The solution of this embodiment can guide the user to bind the device control solution to the network device as a virtual sub-device of the network device after creating the device control solution, thereby improving the convenience of the binding operation.

[0106] In one exemplary embodiment, after binding the device control solution as a virtual sub-device of the network device to the network device in step S401, the method of the present application may further include the following steps:

[0107] A device page for a network device is displayed in a first application; the device page includes a device binding entry for binding the network device to a second application; in response to a trigger operation on the device binding entry, at least one supported second application is displayed; in response to a binding operation triggered for a selected second application, the network device and the virtual sub-device are bound to the selected second application.

[0108] The device page is a page for the network device in the first application, and may include a device binding entry for binding the network device to the second application.

[0109] In the page shown in Figure 8(a), the "Connect" control can serve as a device binding entry for binding the network device to a second application. It can respond to a user trigger operation such as clicking on the device binding entry. As shown in Figure 8(b), at least one supported second application can be displayed. In response to a user triggering a binding operation such as clicking on the "Connect" control corresponding to the selected second application, the network device and the virtual sub-device can be bound to the selected second application.

[0110] This solution can facilitate accurate binding of network device virtual and pseudo sub-devices to the selected second application through the device binding entry of the network device and the step-by-step triggering display of the supported second application.

[0111] In one exemplary embodiment, in response to the device binding operation for the network device in the second application, binding the network device and the virtual sub-device to the second application in step S402 may include:

[0112] In response to a binding operation triggered for a selected second application in a first application, binding information for the selected second application is displayed; a device configuration page is displayed in the second application; in response to a binding operation on the acquired binding information in the device configuration page, the network device and the virtual sub-device are bound to the second application.

[0113] The selected second application may be a second application selected from at least one second application supported through a device page for the network device. As shown in FIG8(b), in response to a binding operation triggered for the selected second application in the first application, such as clicking a "connect" control corresponding to the selected second application, and then in response to clicking a "matter binding information" control, the binding information for the selected second application may be displayed.

[0114] As an example, as shown in Figure 8(c), the binding information may include a matching code, a QR code, etc., which is used to bind the network device and its virtual sub-device in the second application. The binding information may set an effective connection time to limit the effective duration of the binding information and improve device security.

[0115] Among them, the binding information can be obtained and shared through controls such as "Copy Matching Code" and "Save QR Code" for use in the second application.

[0116] Among them, the device configuration page is a page for configuring the device in the second application. FIG8(d) shows a device configuration page in the second application. The device configuration page is displayed in the second application, and then the control for adding a device can be triggered in the device configuration page, and the binding information input area shown in FIG8(e) can be displayed. The above binding information can be entered in the information input area, such as entering a matching code, scanning a QR code through a camera, etc. Thus, the binding information can be obtained in the second application. Then, the binding operation of the obtained binding information can be triggered by clicking Continue in the device configuration page, and the network device and the virtual sub-device can be bound to the second application.

[0117] The solution of this embodiment can bind the network device and the virtual sub-device authorized to be bound in the first application in the second application through the binding information.

[0118] In one exemplary embodiment, the virtual sub-device may include an event signal and / or a device action corresponding to the smart device in the first application; in response to the device binding operation for the network device in the second application in step S402, after the network device and the virtual sub-device are bound to the second application, such as Fig. 9 As shown, the method of the present application may also include the following steps:

[0119] Step S901: Display an automation configuration page in the second application. The automation configuration page may include configuration entries corresponding to trigger conditions and target actions of the automation solution.

[0120] The automation configuration page is a page for configuring the automation solution in the second application. The automation configuration page may include configuration entries corresponding to the trigger conditions of the automation solution, and also include configuration entries corresponding to the target actions of the automation solution. The configuration entries are used to configure the trigger conditions and target actions. As shown in FIG. 10(a), an automation configuration page in the second application can display configuration entries for various trigger conditions.

[0121] Step S902, in response to the trigger operation of the configuration entry for the trigger condition, the event signals corresponding to the supported smart devices and / or virtual sub-devices are displayed, and the event signal of the selected smart device is obtained as the trigger condition of the automation solution.

[0122] Among them, the trigger operation of the configuration entry for the trigger condition can be an operation such as clicking.

[0123] The event signal may be an event signal of a related device that can be used as a trigger condition for an automation solution. The related device may be a supported smart device and / or virtual sub-device. The smart device may be a smart device supported by the first and second applications, such as a smart light, an infrared sensor, etc., and the corresponding event signal may be a switch signal of the smart light, a detection signal of the infrared sensor, etc. The smart device may be a virtual sub-device, and the virtual sub-device may correspond to a smart device in the first application, and the event signal corresponding to the virtual sub-device may be a switch signal, a detection signal, etc. of the smart device in the first application.

[0124] In this step, as shown in FIG10(a), an automation configuration page in the second application can display the event signals corresponding to the supported smart devices and / or virtual sub-devices in response to the trigger operation of the configuration entry for the trigger condition "the sensor detects something", as shown in FIG10(b), the event signals corresponding to the virtual sub-devices can be displayed, and the event signals corresponding to the smart devices can also be displayed. Thus, the event signals of the selected smart devices can be obtained as the trigger conditions of the automation scheme.

[0125] Step S903, in response to the triggering operation of the configuration entry for the target action, display the device actions corresponding to the supported smart devices, and obtain the device action of the selected smart device as the target action of the automation solution.

[0126] In this step, as shown in FIG10(b), in response to a click operation on the "Next" control as a trigger operation for the configuration entry of the target action, the device action corresponding to the supported smart device can be displayed, and as shown in FIG10(c), the device action corresponding to the supported smart device such as air conditioner can be displayed, such as temperature control at 23 degrees, etc. The supported smart device can be a smart device supported by the first and second applications.

[0127] Step S904 , in response to the automation configuration operation on the automation configuration page, an automation solution is generated based on the selected trigger condition and target action.

[0128] The automation configuration operation on the automation configuration page may include configuration operations for the trigger conditions and target actions described above, and after the configuration operations are completed, an automation solution may be generated based on the selected trigger conditions and target actions. As shown in FIG10(c), an automation solution may be generated in response to a click operation on a "Finish" control.

[0129] Step S905: If the automation solution includes event signals and / or device actions corresponding to the smart device in the first application, cross-platform control is performed on the corresponding smart device in the first application through the network device in the second application based on the automation solution.

[0130] Among them, in the automation plan generated by the above steps, the smart device in the first application can be used in at least one of the trigger condition and the target action, the event signal corresponding to the smart device in the first application can be used in the trigger condition, or the device action corresponding to the smart device in the first application can be used in the target action.

[0131] In this step, if the automation plan includes event signals and / or device actions corresponding to the smart devices in the first application, then when executing the automation plan of the second application, the corresponding smart devices in the first application can be cross-platform controlled in the second application through the bound network devices based on the automation plan.

[0132] This embodiment uses the event signal and / or device action corresponding to the smart device in the first application in the automation solution of the second application, so as to realize cross-platform control based on the generated automation solution, thereby enriching the cross-platform control mode.

[0133] In one exemplary embodiment, Fig.11 As shown, in step S402, in response to the device binding operation for the network device in the second application, after the network device and the virtual sub-device are bound to the second application, the method of the present application may further include the following steps:

[0134] Step S1101: Display a device solution configuration page in the second application. The device solution configuration page includes a configuration entry for a device control solution corresponding to each smart device.

[0135] Among them, the device solution configuration page can be a page for configuring device solutions in the second application. The device solution configuration page may include configuration entries for device control solutions corresponding to various smart devices. Among them, the device control solution is a solution for controlling smart devices. Users can also create corresponding device control solutions for one or more smart devices in the space in the second application to control the one or more smart devices. In this step, the device solution configuration page can be displayed in the second application, and the configuration entry of the device control solution corresponding to each smart device in the device solution configuration page can be used to enter the configuration process of the control solution for the corresponding smart device.

[0136] Step S1102: In response to the trigger operation on the configuration entry, display the device functions corresponding to the supported smart devices and / or virtual sub-devices. The device functions corresponding to the virtual sub-devices include the device functions corresponding to the scenarios supported by the smart devices in the first application.

[0137] Among them, the trigger operation for the configuration entry can be a click operation.

[0138] The user terminal can display the device functions corresponding to the supported smart devices and / or virtual sub-devices in response to a click operation on the configuration entry. Among them, the supported smart devices may be smart devices supported in the first and second applications. The virtual sub-devices may correspond to the smart devices in the first application. Among them, the device functions may include device functions corresponding to the scenes supported by the smart devices, such as the device functions of the light-on scenes may be, for example, the light-on function of the smart lights in the living room, etc. As shown in FIG. 10(d), the device functions corresponding to the supported virtual sub-devices may be displayed, and the device functions corresponding to the virtual sub-devices include the device functions corresponding to the scenes supported by the smart devices in the first application, and the scene name may be "Living Room Open", and the device functions corresponding to the scenes supported by the smart devices in the first application, such as the smart lights, may be "Light On", etc.

[0139] Step S1103: In response to the selection operation for the device function of the selected virtual sub-device, a target control scheme is generated. The target control scheme is used to perform cross-platform control of the corresponding smart device in the first application through the network device in the second application.

[0140] Among them, the selection operation for the device function of the selected virtual sub-device is used to indicate the device function of the virtual sub-device to be selected, such as turning on the light. After selecting the device function of the selected virtual sub-device, as shown in Figure 10 (d), you can click the "Finish" control to trigger the second application to generate a target control scheme. Among them, the target control scheme can be used to control the device function of the selected virtual sub-device through a network device. The virtual sub-device corresponds to the smart device in the first application. Controlling the device function of the virtual sub-device can control the smart device in the first application to perform corresponding actions in the supported scenarios, so as to achieve the effect of cross-platform control of the corresponding smart device in the first application through the network device in the second application.

[0141] The solution of this embodiment can achieve cross-platform control of the corresponding smart device in the first application through the network device in the second application by generating a target control solution based on the device function corresponding to the scenario supported by the smart device in the first application corresponding to the virtual sub-device, thereby enriching the cross-platform control method.

[0142] In an exemplary embodiment, Fig.12 As shown, a cross-platform interactive control method is provided, which can be applied to Figure 1 The user terminal, network device (such as a gateway) and server shown in the figure, the method may include the following steps:

[0143] Step S1201, obtaining a device control instruction triggered in a second application, wherein the second application is bound with a network device with cross-platform interaction capability and a virtual sub-device of the network device, which is created based on a device control solution corresponding to the smart device in the first application.

[0144] Among them, device control instructions refer to instructions used to control smart devices, which can be triggered manually by the user or automatically triggered when the trigger conditions of the automation solution are met.

[0145] The second application can be bound to a network device with cross-platform interaction capability and its virtual sub-device, which is created based on the device control scheme corresponding to the smart device in the first application. The manner in which the virtual sub-device is bound to the network device, and the manner in which the network device and its virtual sub-device are bound to the second application can be referred to the contents disclosed in the aforementioned method embodiment.

[0146] Step S1202: If the controlled device targeted by the device control instruction is a virtual sub-device, the corresponding smart device in the first application is controlled through the network device based on the device control solution of the virtual sub-device.

[0147] The device control instruction may be directed to one or more controlled devices, that is, used to control the one or more controlled devices.

[0148] If one or more controlled devices targeted by the device control instruction are the aforementioned virtual sub-devices, the user terminal controls the corresponding smart devices in the first application through the network device based on the device control scheme of the corresponding virtual sub-device.

[0149] The solution of this embodiment can control the corresponding smart device in the first application through the network device in the second application when the controlled device targeted by the device control instruction triggered in the second application is a virtual sub-device, based on the device control solution of the virtual sub-device, to achieve cross-platform control of the corresponding smart device in the first application in the second application, so that the control of the smart device can be carried out collaboratively across platforms, enriching the cross-platform interactive operation experience.

[0150] In an exemplary embodiment, obtaining the device control instruction triggered in the second application in step S1201 may include:

[0151] Display a device control page in the second application; the device control page includes control items of the smart device in the second application and control items of the virtual sub-device in the first application; obtain a device control instruction triggered by the device control page in the second application.

[0152] The device control page may be a page in the second application for controlling the smart device. The device control page may include control items for each smart device in the second application and control items for the virtual sub-device in the first application. The control items may be used to trigger device control instructions for the corresponding device.

[0153] In this embodiment, a click or other operation can be triggered on a control item of a smart device in a device control page displayed in the second application or a control item of a virtual sub-device in the first application, so that the user terminal can obtain a device control instruction triggered by the device control page in the second application, and according to the control item of the click or other operation, it can be determined which smart device or which virtual sub-device in the first application the device control instruction is for. The solution of this embodiment can provide a method for a user to manually trigger a device control instruction, and can trigger a device control instruction for a smart device in the second application or a virtual sub-device in the first application.

[0154] In an exemplary embodiment, Fig.13 As shown, obtaining the device control instruction triggered in the second application in step S1201 may also include:

[0155] Step S1301: Obtain device data reported by the smart device corresponding to each virtual sub-device in the first application, and synchronize the device data to the corresponding virtual sub-device in the second application.

[0156] The device data reported by the smart device corresponding to each virtual sub-device in the first application may include data detected by the smart device, data on the state of the smart device itself, and the like.

[0157] In this step, the device data reported by the smart devices corresponding to each virtual sub-device in the first application can be obtained through the network device, and the device data reported by the smart devices corresponding to each virtual sub-device in the first application can be received from the network device, and the device data can be synchronized to the corresponding virtual sub-device in the second application.

[0158] Step S1302: Obtain the created automation plan in the second application. The automation plan includes a trigger condition and a target action for the controlled device.

[0159] One or more automation schemes may be created in the second application. Each automation scheme may include a trigger condition and a target action. The target action may be a target action for a controlled device or a target action for one or more controlled devices.

[0160] Step S1303, if the trigger condition of the automation solution includes a trigger condition for a virtual sub-device, determine whether the trigger condition is met based on the device data corresponding to the virtual sub-device; if the trigger condition is met, execute the device control instruction corresponding to the automation solution to instruct the corresponding controlled device to perform the target action.

[0161] The trigger conditions of the created automation scheme in the second application may include trigger conditions for the virtual sub-device in the first application. In this case, it is possible to determine whether the trigger condition is met based on the device data corresponding to the virtual sub-device, such as whether a person is detected, whether the light is turned off, etc. If the trigger condition is not met, the reported data may continue to be obtained and the trigger condition may continue to be determined. If the trigger condition is met, the device control instruction corresponding to the automation scheme is executed, and the device control instruction may be used to instruct the corresponding controlled device to perform a target action, such as controlling a smart light to turn off the light.

[0162] The solution of this embodiment can apply the virtual sub-device of the first application to the trigger condition of the automation solution of the second application, and judge whether the trigger condition is met through the device data reported by the smart device corresponding to the virtual sub-device in the first application, and execute the device control instructions corresponding to the automation solution accordingly, so as to achieve the effect of cross-platform interactive control.

[0163] In an exemplary embodiment, obtaining the device control instruction triggered in the second application in step S1201 may include:

[0164] Obtaining a created automation scheme in the second application. The automation scheme includes a trigger condition and a target action for a controlled device. When the trigger condition is met, if the controlled device targeted by the target action includes a virtual sub-device, executing a device control instruction corresponding to the automation scheme to control the intelligent device in the first application corresponding to the virtual sub-device to perform the target action through the network device.

[0165] In this embodiment, it is possible to detect whether the trigger condition of the automation scheme is met. The trigger condition of the automation can be a trigger condition of the virtual sub-device in the first application, or a trigger condition of the smart device in the second application, which is not limited here. When the trigger condition of the automation scheme is met, it can be determined whether the controlled device targeted by the target action of the automation scheme includes the virtual sub-device in the first application. If not, the controlled device can be controlled in the second application to perform the target action. If so, the device control instruction corresponding to the automation scheme is executed to control the smart device in the first application corresponding to the virtual sub-device through the network device to perform the target action.

[0166] The solution of this embodiment can apply the virtual sub-device of the first application in the target action of the automation solution. When the trigger condition is met, the device control instruction corresponding to the automation solution is executed to control the smart device in the first application corresponding to the virtual sub-device through the network device to perform the target action, thereby achieving the effect of cross-platform interactive control.

[0167] In some embodiments, the trigger conditions in the above-mentioned automation scheme include trigger conditions for virtual sub-devices, and the controlled devices targeted by the target actions in the automation scheme include virtual sub-devices, that is, the trigger conditions and target actions in the automation scheme can be configured according to the virtual sub-devices in the first application, so that the trigger conditions and target actions in the automation scheme of the second application can be used for the virtual sub-devices in the first application at the same time, further enriching the cross-platform interactive control method. Therefore, it is possible to determine whether the trigger conditions are met based on the device data corresponding to the virtual sub-device. If the trigger conditions are met, the device control instructions corresponding to the automation scheme are executed to control the smart device in the first application corresponding to the virtual sub-device through the network device to perform the target action.

[0168] In one exemplary embodiment, before obtaining the device control instruction triggered in the second application in step S1201, the following steps may also be included: obtaining the device control scheme created in the first application; the device control scheme includes the event signal supported by the smart device; based on the event signal supported by the smart device, the device control scheme is bound to the network device as a virtual sub-device of the sensor type; the state of the virtual sub-device corresponds to the trigger state of the event signal corresponding to the smart device;

[0169] Step S1201 may include: obtaining device data reported by the smart device corresponding to each virtual sub-device in the first application, and synchronizing the device data to the corresponding virtual sub-device in the second application; if the event signal in the device data meets the triggering condition of the device control instruction, the device control instruction is triggered in the second application.

[0170] In this embodiment, the device control scheme may include event signals supported by the smart device in the first application, such as a human body sensor in the first application, and the event signals supported by the human body sensor may include event signals such as detecting movement of a person, not detecting movement of a person, etc.

[0171] The sub-device type of the virtual sub-device bound to the network device can be a sensor type. Based on the event signal supported by the smart device, the device control scheme is bound to the network device as a virtual sub-device of the sensor type, that is, the device control scheme containing the event signal supported by the smart device can be virtualized as a virtual sub-device of the sensor type and bound to the network device. The virtual sub-device of the sensor type can be an occupancy sensor.

[0172] The state of the sensor-type virtual sub-device may be an occupation state of the virtual sub-device, which may include occupied or unoccupied.

[0173] The trigger state of the event signal corresponding to the smart device may indicate whether the event signal corresponding to the smart device is triggered, and the trigger state may include being triggered or not being triggered.

[0174] Among them, the occupied state of the sensor type virtual sub-device can correspond to the triggered state of the event signal, and the unoccupied state of the sensor type virtual sub-device can correspond to the untriggered state of the event signal. Taking the human body sensor device as an example, when the human body sensor device detects that there is a person in the target space, the state of the device can be determined as an occupied state, and the device also triggers an event signal that there is a person in the target space.

[0175] Based on this, the second application can obtain the device data reported by the smart devices corresponding to each virtual sub-device in the first application through the network device, and synchronize the device data to the corresponding virtual sub-device in the second application. In this way, it can be judged according to the state of the virtual sub-device of the sensor type whether the event signal in the device data meets the triggering conditions of the device control instruction, such as whether the event signal corresponding to the smart device is triggered, etc. If the event signal in the device data meets the triggering conditions of the device control instruction, such as the event signal corresponding to the smart device is triggered, the device control instruction can be triggered in the second application.

[0176] This embodiment can utilize a sensor-type virtual sub-device to bind a device control scheme including event signals supported by an intelligent device to a network device. The state of the sensor-type virtual sub-device corresponds to the trigger state of the event signal corresponding to the intelligent device. Thus, it is possible to accurately and conveniently determine whether the trigger conditions of the device control instruction are met based on the state of the sensor-type virtual sub-device.

[0177] In one exemplary embodiment, before obtaining the device control instruction triggered in the second application in step S1201, the method of the present application may further include:

[0178] Obtain a device control scheme created in the first application; the device control scheme includes device functions supported by the smart device; based on the device functions supported by the smart device, bind the device control scheme to the network device as a virtual sub-device of the controlled device type; the device functions of the virtual sub-device correspond to the device functions corresponding to the smart device.

[0179] In this embodiment, the device control scheme may include device functions supported by the smart device, and may include device functions corresponding to the scenes supported by the smart device in the first application, such as turning on and off smart lights in the home and leaving home scenes.

[0180] Among them, the sub-device type of the virtual sub-device bound to the network device can adopt the controlled device type. Based on the device functions supported by the smart device, the device control scheme is bound to the network device as a virtual sub-device of the controlled device type, that is, the device control scheme containing the device functions supported by the smart device can be virtualized as a virtual sub-device of the controlled device type and bound to the network device. Among them, the virtual sub-device of the controlled device type can adopt an on / off plug-in unit (On / OffPlug-in Unit) compatible with the Matter protocol.

[0181] The device function of the virtual sub-device may be an on / off function of the virtual sub-device. The device function corresponding to the smart device may include an on / off function of the smart device. Thus, the on / off function of the virtual sub-device may correspond to the on / off function of the smart device.

[0182] The solution of this embodiment can use a virtual sub-device of the controlled device type to bind the device control solution including the device functions supported by the smart device to the network device. The device functions of the virtual sub-device correspond to the device functions of the smart device. Therefore, the purpose of controlling the smart device can be achieved by controlling the virtual sub-device based on the device functions of the virtual sub-device.

[0183] As an application example of the cross-platform interactive control method of the present application, the process of virtual sub-device binding and application may include:

[0184] 1. The user configures the device control scheme in the first application of the current platform, which may include one or more of the event signals reported by the smart device used to configure the automation scheme, the device actions performed by the smart device, and the device functions corresponding to the scenes supported by the smart device. For example, the user defines the scene name (such as "Goodnight Mode") and selects the relevant execution action (for example, turn off all lights, turn on the air conditioner, open the curtains, etc.), and then uses the device function corresponding to the scene as the configured device control scheme. For another example, the user defines the event signal name (such as "Face Detected") and selects the relevant event signal, such as camera-detected a specified face.

[0185] 2. Bind the configured device control scheme to the network device as a virtual sub-device of the network device, and bind it to the central device of the Matter ecosystem. The user-configured device control scheme can be sent to the network device as a virtual sub-device of the network device in the application interface of the first application on the current platform in the form of a command for binding.

[0186] 3. Parsing and processing instructions

[0187] After receiving the above instructions, the network device can parse the content of the event signal in the user-defined device control scheme, which may include: signal ID, signal name, ecosystem type, whether to create a virtual sub-device, etc. Alternatively, the scene information content in the user-defined device control scheme can be parsed, including: scene ID, scene name, ecosystem type, whether to create a virtual sub-device, etc. The network device can check whether there is a corresponding physical or virtual sub-device, and whether a new virtual sub-device needs to be created to meet the event signal or scene requirements in the device control scheme.

[0188] 4. Creation of virtual sub-devices

[0189] If a virtual sub-device needs to be created, the network device can create a new virtual sub-device in its local system.

[0190] As an example, for event signals, the network device can configure the event signal as a Matter protocol-compatible occupancy sensor, or other sensors that support event reporting of Boolean or enumerated values, such as human sensors (detection of human movement, no detection of human movement events), door and window sensors (door and window open, door and window closed events), programmable wireless switches (single-click, double-click, long-press events), etc., allowing it to be identified and operated in the Matter ecosystem. The name setting of the virtual sub-device can be a user-defined signal name for easy identification. The initialization of the virtual sub-device can include setting state variables and possible control interfaces.

[0191] As an example, for a scene, a network device can configure the scene as a Matter protocol-compatible on / off plug-in unit, or other control devices that support Boolean or enumeration value output, such as switches (switch on, switch off actions), lights (light on, light off, light brightness adjusted to a specific brightness value, etc.), curtains (curtains open, curtains closed, curtains opened to a specific opening degree, etc.), air conditioners (air conditioners on, air conditioners off, air conditioners adjusted to cooling or heating mode, air conditioners adjusted to a specified temperature, etc.), etc., allowing it to be identified and operated in the Matter ecosystem. The name setting of the virtual sub-device can be a user-defined scene name for easy identification. Initialization of the virtual sub-device can include setting state variables and possible control interfaces.

[0192] 5. Register the virtual sub-device and bind it to the first application with Matter function

[0193] Network devices can register newly created virtual sub-devices to the Matter applications they manage through the Matter bridge. The device registration process can include assigning a network address and device ID, as well as defining the device's functions and features in the Matter controller.

[0194] 6. Signal / Scenario and Device Association

[0195] Associate virtual sub-devices with user-defined, e.g., event signals / scenario.

[0196] When the trigger condition is met, the state of the virtual sub-device will be automatically updated according to the trigger state change / scene action of the event signal. The scene action may include turning on or off; the trigger state of the event signal may include 1 "occupancy detected" and 0 "no occupancy detected", etc.

[0197] 7. State Synchronization and Feedback

[0198] Changes to the state of virtual sub-devices can be synchronized to the control application and other Matter-compatible devices.

[0199] Users can monitor the state changes of this virtual sub-device through the application interface to obtain, for example, the trigger status of an event signal. Users can use this status to create automation solutions on the Matter ecosystem platform to trigger other devices in the ecosystem, such as turning on the lights when the signal is 1 (occupancy detected).

[0200] Among them, for the configuration of the event signal / scenario in the first application:

[0201] Signals can refer to status information or event trigger information transmitted by a device, which can be used to notify other devices or systems of the occurrence of an event. For example, a door or window sensor sends a signal when it detects that a door is opened, and a temperature sensor sends a signal when it detects a temperature change. Signals can be used as conditions for automation solutions in the first application. When creating an automation solution through the first application, users can select an event signal as a condition for the automation solution.

[0202] As an example, combining Figure 5(a) to Figure 5(c) , the basic steps to create a signal:

[0203] 1. Open the first application, enter the automation page, click "+" in the upper right corner, select "New Signal", enter the "New Signal" editing page, create a new signal to be created, or enter the edit signal list to batch check the signals and add them to Matter in batches. After entering the editing state, it can be displayed whether the signal has been synchronized to Matter.

[0204] 2. When you click Save / Done, as shown in Figure 7(a), "Add to Matter" may be checked by default.

[0205] 3. As shown in Figure 7(c), jump to the network device list interface of the current home. At this time, it can be divided into three situations:

[0206] (1) If the user does not select a record of a certain network device, guide the user to select the corresponding network device.

[0207] (2) If the user has previously selected a network device, the network device will be selected by default when the user enters this page later. If the user's current home has added two or more network devices, and the user wants to switch to another network device to use as a network device, the user can be prompted to check the impact warning of other network devices.

[0208] (3) If there is no network device in the current home, the user may be prompted that there is no network device in the current home, and the user may be guided to add the network device of the first application.

[0209] 4. After clicking Save, the signal information, including signal ID, signal name (the maximum name length can be 32 bytes), ecosystem type, whether to create a virtual sub-device, and other fields, can be sent to the selected network device.

[0210] 5. The network device may generate a virtual Matter bridge sub-device locally according to the information sent, and the device type of the sub-device may be a sensor type, for example, an occupancy sensor type, and the device name may be the signal name;

[0211] 6. When the occupancy status of the generated occupancy sensor is occupied, it means that the signal is triggered. When it becomes unoccupied, it means that the signal is not triggered. Users can control other devices in the Matter ecosystem by triggering the occupancy status.

[0212] 7. The user can manually remove the signal association through the first application, that is, after the user removes the signal association, the network device also needs to remove the corresponding Matter virtual sub-device.

[0213] 8. Users can view and set the functions shown in Table 1 in the signal more settings:

[0214] Table 1

[0215] Serial number Function Remark 1 Signal Identification Users can map the signal identifier with the serial number generated by Matter to facilitate troubleshooting and locating the signal 2 Add to Matter status You can check whether the current scene has been added to Matter 3 <![CDATA[Added to Matte r Operation]]> You can add Matter, add scenes to Matter, and generate virtual objects 4 Execution Gateway local, local area network, cloud 5 Signal Type Transient, State, Transient & State

[0216] As an example, combining Figure 6 , the basic steps to create a scene:

[0217] 1. Open the first app and enter the scene page. Long press the scene icon to enter the scene editing page. Check one or more scenes of the first app and click "Add to Matter". At the same time, the upper left corner of the scene list can show whether the current scene has been synchronized to Matter.

[0218] 2. Jump to the network device list interface under the current home of the first application, which can also be divided into three situations, please refer to the above instructions.

[0219] 3. After clicking Save, the scene information, as shown in Table 2 below, including: scene ID, scene name (the maximum length of the scene name can be 32 bytes), ecosystem type, whether to create a virtual sub-device, and other fields, can be sent to the selected network device.

[0220] Table 2

[0221]

[0222] 4. Based on the information sent, the network device generates a virtual Matter virtual sub-device locally, such as a virtual socket. The device type of the sub-device can be a controlled device type, such as an on / off plug-in unit (On / OffPlug-in Unit) type, and the device name can be the scene name (based on the scene selected by the user).

[0223] 5. The generated virtual sub-device - the On and Off states of the socket both correspond to the execution of the scene. The user implements the control solution corresponding to the scene in the first application by turning on or off the socket.

[0224] 6. The user can manually remove the scene association of the first application through the first application, that is, after the user removes the scene association of the first application, the network device can remove the corresponding Matter virtual sub-device.

[0225] 7. Users can view and set the functions in Table 3 below in the scene more settings:

[0226] Table 3

[0227]

[0228] Among them, for synchronizing the configured signals / scenes to the network devices in the Matter ecosystem:

[0229] The signal synchronization to Matter function allows users to synchronize the signal created in the first application of the current platform to the second application in the Matter ecosystem. With this function, users can generate a virtual sub-device (occupancy sensor) in the first application and synchronize it to the second application in the Matter ecosystem.

[0230] In this way, even if the signal of the current platform does not support the Matter protocol, the corresponding smart devices can be controlled through a third-party platform. For example, signals such as face recognition, gesture recognition, sleep detection, and whether there is anyone in the area can be virtualized into a virtual sub-device of the Matter occupancy sensor type, or other sensors that support event reporting of Boolean or enumeration values, such as human body sensors (detection of movement, no detection of movement events), door and window sensors (door and window open, door and window closed events), programmable wireless switches (single click, double click, long press events), etc., so that in the second application under the Matter ecosystem, these signals can be used to trigger other smart home devices in the current platform, thereby realizing a cross-ecosystem and cross-platform interactive operation experience.

[0231] The scene synchronization to Matter function allows users to synchronize the scenes created in the first application of the current platform to the second application in the Matter ecosystem. With this function, users can generate a virtual Matter socket, and users can execute the scenes in the current platform by opening the virtual socket in the second application of the third-party platform. Even if the devices in the scene of the current platform do not support the Matter protocol, the corresponding smart devices can be controlled through the third-party platform. For example, the user can create a "leave home" scene in the first application of the current platform, which includes a series of actions such as turning off all lights, turning off the air conditioner, and locking the door. By setting Matter scenes and syncing them to third-party platforms, users can trigger these scenes through the second application of the Matter ecosystem, thereby conveniently controlling various smart home devices across ecosystems and platforms.

[0232] Among them, for registering virtual devices and binding to third-party platform applications with Matter functions, Figure 8(a) to Figure 8(f) :

[0233] 1. In the first application of the current platform, enter the network device page, which can display the third-party ecosystem (third-party platform) that supports Matter. By clicking the "Connect" control corresponding to the corresponding third-party platform, the network device and its virtual sub-devices can be connected to the third-party ecosystem that supports Matter to achieve cross-ecosystem interconnection.

[0234] 2. Users can choose to share with the corresponding Matter. After the user clicks "Matter Binding Information", the generated Matter matching code or QR code will be displayed. Users can directly copy the generated Matter matching code or download the QR code.

[0235] 3. Then, the user opens the second application of the third-party Matter, selects Add Device in the second application of the third-party Matter, and enters the copied Matter matching code, or scans the Matte QR code to add the network device and its virtual sub-devices to the second application of the third-party Matter. After successful addition, the network device and its virtual sub-devices are added to the second application of the third-party Matter (i.e., the network device and its virtual sub-devices are bound).

[0236] 4. The user can also continue to add signals / scenes of virtual sub-devices in the first application. After the addition is completed, a virtual sub-device under the network device will be automatically generated in the second application of the corresponding third-party Matter. The virtual sub-device can be the virtual sub-device corresponding to the configured signal / scene.

[0237] For an example of creating an automation scenario in a second app in Matter, combine Figure 10(a) to Figure 10(d): Enter the creation automation page of the second application of the third-party Matter, and you can select the sensor to detect certain things. You can select the virtual sub-device that you just registered, such as the signal name and device name can be called "Living Room Someone" (that is, the signal corresponding to the smart device under the current platform). Select the execution action of the automation to turn on the air conditioner or execute a scene (for example, the living room is turned on).

[0238] The solution of the present application, by generating virtual sub-devices such as virtual sockets and occupancy sensors in the first application, allows users to incorporate devices that do not support the Matter protocol into the Matter ecosystem, greatly expanding the functions of existing devices without replacing or upgrading hardware. It also supports virtualizing advanced functions such as face recognition, gesture recognition, sleep detection and other signals into Matter occupancy sensors. This allows users to trigger different smart home actions based on these advanced signals, for example, automatically turning off appliances when the system detects that no one is at home, or adjusting indoor lighting and temperature after detecting that the user has fallen asleep, enhancing the automation and personalization functions of the smart home system. As a result, not only the device compatibility problem is solved, but also the intelligence level of the entire smart home system is improved through advanced scene triggering and cross-platform operation, providing users with a more flexible, intelligent and interconnected home environment.

[0239] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0240] Based on the same inventive concept, the embodiment of the present application also provides a virtual object processing device for implementing the virtual object processing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more virtual object processing device embodiments provided below can refer to the limitations of the virtual object processing method above, and will not be repeated here.

[0241] In an exemplary embodiment, Fig.14 As shown, a cross-platform interactive control device is provided, and the device 1400 may include:

[0242] A first binding module 1401 is used for responding to a binding operation on a created device control scheme in a first application, binding the device control scheme as a virtual sub-device of a network device to the network device; the network device is a network device with cross-platform interaction capability;

[0243] The second binding module 1402 is used to respond to the device binding operation for the network device in the second application, bind the network device and the virtual sub-device to the second application, so that the device control scheme of the virtual sub-device is controlled by the network device in the second application, so as to perform cross-platform control on the corresponding smart device in the first application.

[0244] In an exemplary embodiment, the first binding module 1401 is also used to display a solution configuration page in the first application; the solution configuration page includes smart devices in the first application; in response to the solution configuration operation for the selected smart device in the solution configuration page, the device control solution is created according to the device solution information for the selected smart device.

[0245] In an exemplary embodiment, the scheme configuration page includes a first scheme configuration page; the device scheme information includes event signals reported by smart devices for configuring the automation scheme and / or device actions performed by smart devices; the first binding module 1401 is also used to display the event signals supported by the selected smart device in response to the selection operation of the smart device corresponding to the event signal in the first scheme configuration page; and / or, in response to the selection operation of the smart device corresponding to the device action in the first scheme configuration page, display the device actions supported by the selected smart device; based on the event signal of the selected smart device and / or the device action of the smart device, the device control scheme is created.

[0246] In an exemplary embodiment, the solution configuration page includes a second solution configuration page; the device solution information includes device functions corresponding to the scene; the first binding module 1401 is also used to respond to a selection operation on a smart device in the second solution configuration page, display the device functions corresponding to the scene supported by the selected smart device; in response to a selection operation on a device function, create the device control solution based on the selected device function.

[0247] In an exemplary embodiment, the first binding module 1401 is used to display a binding entry for the created device control scheme in the first application; the binding entry includes a binding entry for binding the created device control scheme to the network device; in response to a binding operation on the binding entry, the device control scheme is bound to the network device as a virtual sub-device of the network device.

[0248] In an exemplary embodiment, the first binding module 1401 is also used to display a device page for the network device in the first application; the device page includes a device binding entry for binding the network device to a second application; in response to a trigger operation on the device binding entry, at least one supported second application is displayed; in response to a binding operation triggered for a selected second application, the network device and the virtual sub-device are bound to the selected second application.

[0249] In an exemplary embodiment, the second binding module 1402 is used to display binding information for a selected second application in response to a binding operation triggered for a selected second application in the first application; display a device configuration page in the second application; and bind the network device and the virtual sub-device to the second application in response to a binding operation on the acquired binding information in the device configuration page.

[0250] In an exemplary embodiment, the virtual sub-device includes an event signal and / or device action corresponding to the smart device in the first application; the second binding module 1402 is further used to display an automation configuration page in the second application; the automation configuration page includes configuration entries corresponding to the trigger conditions and target actions of the automation solution respectively; in response to a trigger operation of the configuration entry for the trigger condition, the event signal corresponding to the supported smart device and / or virtual sub-device is displayed, and the event signal of the selected smart device is obtained as the trigger condition of the automation solution; in response to a trigger operation of the configuration entry for the target action, the device action corresponding to the supported smart device is displayed, and the device action of the selected smart device is obtained as the target action of the automation solution; in response to the automation configuration operation on the automation configuration page, an automation solution is generated based on the selected trigger condition and target action; if the automation solution includes the event signal and / or device action corresponding to the smart device in the first application, then based on the automation solution, the corresponding smart device in the first application is cross-platform controlled in the second application through the network device.

[0251] In an exemplary embodiment, the second binding module 1402 is also used to display a device solution configuration page in the second application; the device solution configuration page includes a configuration entry for a device control solution corresponding to each smart device; in response to a trigger operation on the configuration entry, the device functions corresponding to the supported smart devices and / or virtual sub-devices are displayed; the device functions corresponding to the virtual sub-devices include device functions corresponding to the scenarios supported by the smart devices in the first application; in response to a selection operation on the device functions of the selected virtual sub-device, a target control solution is generated; the target control solution is used to perform cross-platform control of the corresponding smart devices in the first application through the network device in the second application.

[0252] In an exemplary embodiment, Fig.15 As shown, a cross-platform interactive control device is provided, and the device 1500 may include:

[0253] Instruction acquisition module 1501, used to acquire device control instructions triggered in a second application; the second application is bound to a network device with cross-platform interaction capability and a virtual sub-device of the network device; the virtual sub-device is created based on the device control solution corresponding to the smart device in the first application;

[0254] The device control module 1502 is used to control the corresponding intelligent device in the first application through the network device based on the device control solution of the virtual sub-device if the controlled device targeted by the device control instruction is the virtual sub-device.

[0255] In an exemplary embodiment, the instruction acquisition module 1501 is used to display a device control page in the second application; the device control page includes control items of the smart device in the second application and control items of the virtual sub-device in the first application; and obtain device control instructions triggered by the device control page in the second application.

[0256] In an exemplary embodiment, the instruction acquisition module 1501 is used to obtain the device data reported by the smart device corresponding to each of the virtual sub-devices in the first application, and synchronize the device data to the corresponding virtual sub-device in the second application; obtain the created automation plan in the second application; the automation plan includes trigger conditions and target actions for the controlled devices; if the trigger conditions of the automation plan include trigger conditions for the virtual sub-device, determine whether the trigger conditions are met based on the device data corresponding to the virtual sub-device; if the trigger conditions are met, execute the device control instructions corresponding to the automation plan to instruct the corresponding controlled device to perform the target action.

[0257] In an exemplary embodiment, the instruction acquisition module 1501 is used to obtain the created automation plan in the second application; the automation plan includes a trigger condition and a target action for the controlled device; when the trigger condition is met, if the controlled device targeted by the target action includes the virtual sub-device, the device control instruction corresponding to the automation plan is executed to control the smart device in the first application corresponding to the virtual sub-device through the network device to perform the target action.

[0258] In an exemplary embodiment, the instruction acquisition module 1501 is also used to acquire a device control scheme created in the first application; the device control scheme includes an event signal supported by an intelligent device; based on the event signal supported by the intelligent device, the device control scheme is bound to the network device as a virtual sub-device of a sensor type; the state of the virtual sub-device corresponds to the trigger state of the event signal corresponding to the intelligent device; the device data reported by the intelligent device corresponding to each of the virtual sub-devices in the first application is acquired, and the device data is synchronized to the corresponding virtual sub-device in the second application; if the event signal in the device data meets the trigger condition of the device control instruction, the device control instruction is triggered in the second application.

[0259] In an exemplary embodiment, the instruction acquisition module 1501 is also used to obtain a device control scheme created in the first application; the device control scheme includes device functions supported by the smart device; based on the device functions supported by the smart device, the device control scheme is bound to the network device as a virtual sub-device of the controlled device type; the device functions of the virtual sub-device correspond to the device functions corresponding to the smart device.

[0260] Each module in the above virtual object processing device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in an electronic device in the form of hardware, or can be stored in a memory in an electronic device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0261] In an exemplary embodiment, an electronic device is provided. The electronic device may be a terminal, and its internal structure diagram may be as shown in FIG. Fig.16As shown. The electronic device may include a processor, a memory, an input / output interface, and a communication interface. The processor, the memory, and the input / output interface are connected via a system bus, and the communication interface is connected to the system bus via the input / output interface. The processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the electronic device is used to exchange information between the processor and an external device. The communication interface of the electronic device is used to communicate with an external device in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, a near field communication (NearField Communication, NFC) or other technologies. When the computer program is executed by the processor, a cross-platform interactive control method is implemented.

[0262] Those skilled in the art will understand that Fig.16 The structure shown in the figure is merely a block diagram of a partial structure related to the scheme of the present application, and does not constitute a limitation on the electronic device to which the scheme of the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0263] In one embodiment, an electronic device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0264] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0265] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0266] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0267] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0268] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0269] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A cross-platform interactive control method, characterized in that: The method comprises: In response to a binding operation for the created device control scheme in the first application, the device control scheme is bound to the network device as a virtual sub-device of the network device; the network device is a network device with cross-platform interaction capability; In response to a device binding operation for the network device in a second application, the network device and the virtual sub-device are bound to the second application, so that the device control scheme of the virtual sub-device is controlled by the network device in the second application, so as to perform cross-platform control on the corresponding smart device in the first application.

2. The method according to claim 1, characterized in that Before binding the device control scheme as a virtual sub-device of the network device to the network device in response to the binding operation for the created device control scheme in the first application, the method further includes: Displaying a solution configuration page in the first application; the solution configuration page includes a smart device for the first application; In response to a solution configuration operation for a selected smart device in the solution configuration page, the device control solution is created according to device solution information for the selected smart device.

3. The method according to claim 2, characterized in that The scheme configuration page includes a first scheme configuration page; the device scheme information includes event signals reported by smart devices and / or device actions performed by smart devices for configuring the automation scheme; In response to the scheme configuration operation for the selected smart device in the scheme configuration page, creating the device control scheme according to the device scheme information for the selected smart device, including: In response to a selection operation of a smart device corresponding to the event signal in the first solution configuration page, displaying event signals supported by the selected smart device; and / or, In response to a selection operation of a smart device corresponding to the device action in the first solution configuration page, displaying device actions supported by the selected smart device; The device control plan is created based on the event signal of the selected smart device and / or the device action of the smart device.

4. The method according to claim 2, characterized in that: The solution configuration page includes a second solution configuration page; the device solution information includes a device function corresponding to the scenario; In response to the scheme configuration operation for the selected smart device in the scheme configuration page, creating the device control scheme according to the device scheme information for the selected smart device, including: In response to a selection operation on a smart device in the second solution configuration page, displaying device functions corresponding to the scenarios supported by the selected smart device; In response to a selection operation on a device function, the device control scheme is created based on the selected device function.

5. The method according to claim 1, characterized in that In response to the binding operation on the created device control scheme in the first application, binding the device control scheme as a virtual sub-device of the network device to the network device includes: Displaying a binding entry for the created device control scheme in the first application; the binding entry includes a binding entry for binding the created device control scheme to the network device; In response to a binding operation on the binding entry, the device control solution is bound to the network device as a virtual sub-device of the network device.

6. The method according to claim 1, characterized in that After binding the device control scheme as a virtual sub-device of the network device to the network device, the method further includes: Displaying a device page for the network device in the first application; the device page includes a device binding entry for binding the network device to the second application; In response to a trigger operation on the device binding entry, displaying at least one second application supported; In response to a binding operation triggered for the selected second application, the network device and the virtual sub-device are bound to the selected second application.

7. The method according to claim 6, characterized in that In response to the device binding operation for the network device in the second application, binding the network device and the virtual sub-device to the second application includes: In response to a binding operation triggered in the first application for a selected second application, displaying binding information for the selected second application; Displaying a device configuration page in the second application; In response to a binding operation on the acquired binding information in the device configuration page, the network device and the virtual sub-device are bound to the second application.

8. The method according to any one of claims 1 to 7, characterized in that The virtual sub-device includes an event signal and / or a device action corresponding to the smart device in the first application; After the network device and the virtual sub-device are bound to the second application in response to the device binding operation for the network device in the second application, the method further includes: Displaying an automation configuration page in the second application; the automation configuration page includes configuration entries corresponding to trigger conditions and target actions of the automation solution; In response to a trigger operation of a configuration entry for the trigger condition, an event signal corresponding to the supported smart device and / or virtual sub-device is displayed, and an event signal of the selected smart device is obtained as a trigger condition of the automation solution; In response to a trigger operation of a configuration entry for the target action, display device actions corresponding to supported smart devices, and obtain the device action of the selected smart device as a target action of the automation solution; In response to the automation configuration operation on the automation configuration page, generating an automation solution based on the selected trigger condition and target action; If the automation scheme includes event signals and / or device actions corresponding to the smart device in the first application, cross-platform control is performed on the corresponding smart device in the first application through the network device in the second application based on the automation scheme.

9. The method according to any one of claims 1 to 7, characterized in that After the network device and the virtual sub-device are bound to the second application in response to the device binding operation for the network device in the second application, the method further includes: Displaying a device solution configuration page in the second application; the device solution configuration page includes a configuration entry for a device control solution corresponding to each smart device; In response to a trigger operation on the configuration entry, display device functions corresponding to supported smart devices and / or virtual sub-devices; the device functions corresponding to the virtual sub-devices include device functions corresponding to scenarios supported by the smart devices in the first application; In response to a selection operation for a device function of a selected virtual sub-device, a target control scheme is generated; the target control scheme is used to perform cross-platform control of a corresponding smart device in the first application through the network device in the second application.

10. A cross-platform interactive control method, characterized in that: The method comprises: Acquire a device control instruction triggered in a second application; the second application is bound to a network device with cross-platform interaction capability and a virtual sub-device of the network device; the virtual sub-device is created based on a device control solution corresponding to the smart device in the first application; If the controlled device targeted by the device control instruction is the virtual sub-device, the corresponding intelligent device in the first application is controlled by the network device based on the device control solution of the virtual sub-device.

11. The method according to claim 10, characterized in that The acquiring of the device control instruction triggered in the second application includes: Displaying a device control page in the second application; the device control page includes control items of the smart device in the second application and control items of the virtual sub-device in the first application; Obtain a device control instruction triggered by a device control page in the second application.

12. The method according to claim 10, characterized in that The acquiring of the device control instruction triggered in the second application includes: Acquire device data reported by the smart device corresponding to each of the virtual sub-devices in the first application, and synchronize the device data to the corresponding virtual sub-device in the second application; Acquire a created automation scheme in the second application; the automation scheme includes a trigger condition and a target action for a controlled device; If the trigger condition of the automation solution includes a trigger condition for the virtual sub-device, determining whether the trigger condition is satisfied based on the device data corresponding to the virtual sub-device; If the trigger condition is met, the device control instruction corresponding to the automation solution is executed to instruct the corresponding controlled device to perform the target action.

13. The method according to claim 10, characterized in that The acquiring of the device control instruction triggered in the second application includes: Acquire a created automation scheme in the second application; the automation scheme includes a trigger condition and a target action for a controlled device; When the trigger condition is met, if the controlled device targeted by the target action includes the virtual sub-device, the device control instruction corresponding to the automation solution is executed to control the smart device in the first application corresponding to the virtual sub-device through the network device to perform the target action.

14. The method according to claim 10, characterized in that Before acquiring the device control instruction triggered in the second application, the method further includes: Acquire a device control scheme created in the first application; the device control scheme includes event signals supported by the smart device; Based on the event signal supported by the smart device, the device control scheme is bound to the network device as a virtual sub-device of a sensor type; the state of the virtual sub-device corresponds to the trigger state of the event signal corresponding to the smart device; The acquiring of the device control instruction triggered in the second application includes: Acquire device data reported by the smart device corresponding to each of the virtual sub-devices in the first application, and synchronize the device data to the corresponding virtual sub-device in the second application; If the event signal in the device data meets the triggering condition of the device control instruction, the device control instruction is triggered in the second application.

15. The method according to claim 10, characterized in that Before acquiring the device control instruction triggered in the second application, the method further includes: Acquire a device control scheme created in the first application; the device control scheme includes device functions supported by the smart device; Based on the device functions supported by the smart device, the device control scheme is bound to the network device as a virtual sub-device of the controlled device type; the device functions of the virtual sub-device correspond to the device functions corresponding to the smart device.

16. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 9 or the steps of the method according to any one of claims 10 to 15 are implemented.

17. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 or the steps of the method according to any one of claims 10 to 15 are implemented.

18. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 or the steps of the method according to any one of claims 10 to 15 are implemented.

Images