Device control method and apparatus, electronic device, readable storage medium, and program product

Abstract

The application relates to a device control method and device, electronic equipment, readable storage medium and program product, and relates to the technical field of Internet of Things. The application can improve the timeliness of video recording. The method comprises the following steps: in response to the event detected by an associated device belonging to a target event corresponding to the associated device in associated configuration information of a target device, controlling the target device to record a video to obtain an event video of the target event; wherein the associated device is a device associated with the target device, and the associated configuration information contains a target event corresponding to each associated device; and event videos of target events corresponding to different associated devices are displayed in a device page of the target device.

Description

Technical Field

[0001] This application relates to the field of Internet of Things (IoT) technology, and in particular to a device control method, apparatus, electronic device, readable storage medium, and program product. Background Technology

[0002] With the development of Internet of Things (IoT) technology, various devices are rapidly becoming widespread, such as smart home devices. Among these, users can control devices with recording capabilities to record videos via mobile phones and other user terminals.

[0003] In current technology, different devices are relatively independent. If it is necessary to record a video when a certain device detects a specific event, the user usually needs to control the recording device on the user terminal such as a mobile phone to record the video when the user discovers that a certain device has detected a specific event. This can easily lead to missing the recording opportunity and result in poor recording timeliness. Summary of the Invention

[0004] Therefore, it is necessary to provide a device control method, apparatus, electronic device, readable storage medium, and program product to address the aforementioned technical problems.

[0005] In a first aspect, this application provides a device control method, comprising:

[0006] In response to an event detected by an associated device belonging to a target event corresponding to the associated device in the association configuration information of the target device, the target device is controlled to record video to obtain an event recording of the target event; the associated device is a device associated with the target device; the association configuration information contains the target event corresponding to each associated device;

[0007] The device page of the target device displays event recordings of the target events corresponding to different associated devices.

[0008] Secondly, this application also provides a device control apparatus, comprising:

[0009] The recording trigger module is used to respond to an event detected by an associated device that belongs to a target event corresponding to the associated device in the association configuration information of the target device, and to control the target device to record the event to obtain an event recording of the target event; the associated device is a device associated with the target device; the association configuration information contains a target event corresponding to each associated device;

[0010] The video recording module is used to display event recordings of target events corresponding to different associated devices on the device page of the target device.

[0011] Thirdly, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method.

[0012] Fourthly, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps in the above-described method.

[0013] Fifthly, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method.

[0014] The aforementioned device control method, apparatus, electronic device, readable storage medium, and program product, in response to an event detected by an associated device belonging to a target event corresponding to an associated device in the associated configuration information of the target device, control the target device to record video to obtain an event recording of the target event. The associated device is a device associated with the target device, and the associated configuration information contains a target event corresponding to each associated device. The event recordings of the target events corresponding to different associated devices are displayed on the target device's device page. This solution, based on the target events corresponding to each associated device contained in the target device's associated configuration information, can control the target device to record video when an event detected by an associated device of the target device belongs to that associated device's target event, achieving a rapid response from event detection to device recording, ensuring timely recording initiation, eliminating the need for user manual control of the device to record, avoiding missed recording opportunities, improving recording timeliness, and displaying event recordings of the target events corresponding to different associated devices on the target device's device page, facilitates users' centralized review of the event recordings of each target event, providing a comprehensive understanding of each target event and contributing to improved area monitoring security. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 This is an application environment diagram of the device control method in one embodiment;

[0017] Figure 2 This is a flowchart illustrating a device control method in one embodiment;

[0018] Figure 3This is a flowchart illustrating the steps for obtaining associated configuration information in one embodiment;

[0019] Figure 4 This is a flowchart illustrating the steps for obtaining associated configuration information in another embodiment;

[0020] Figure 5 This is a schematic diagram illustrating the configuration of the entry point display in one embodiment;

[0021] Figure 6 This is a schematic diagram illustrating the configuration of the display page in one embodiment;

[0022] Figure 7 This is a schematic diagram illustrating the configuration of adding a page in one embodiment;

[0023] Figure 8 This is a schematic diagram of a device selection page in one embodiment;

[0024] Figure 9 This is a schematic diagram of an event selection page in one embodiment;

[0025] Figure 10(a) is a schematic diagram of the event recording identifier and event recording display in one embodiment;

[0026] Figure 10(b) is a schematic diagram of the event recording identifier and event recording display in another embodiment;

[0027] Figure 11 This is a schematic diagram of an event filtering page in one embodiment;

[0028] Figure 12 This is a schematic diagram of an associated event filtering page in one embodiment;

[0029] Figure 13 This is a schematic diagram of the associated configuration process in one embodiment;

[0030] Figure 14 This is a schematic diagram of the event triggering and recording process in one embodiment;

[0031] Figure 15 This is a schematic diagram of the video viewing process in one embodiment;

[0032] Figure 16 This is a structural block diagram of the device control apparatus in one embodiment;

[0033] Figure 17 This is a diagram of the internal structure of an electronic device in one embodiment. Detailed Implementation

[0034] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0035] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various objects, but these objects are not limited by these terms. These terms are only used to distinguish the first object from the second object. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the solutions, or any combination of multiple solutions.

[0036] The device control method provided in this application embodiment can be applied to, for example, Figure 1 The application environment shown can be a smart home system, which may include: a cloud / cloud server, a router, a gateway, user terminals (such as mobile phones and tablets), and multiple devices (such as cameras, door and window sensors, human body sensors, smart door locks, smart switches, smart sockets, etc.). In the smart home system, each device can connect to the gateway via ZigBee / Bluetooth, and the gateway and user terminals can connect to the router via WiFi. Additionally, user terminals can also establish network connections to the cloud / cloud server via 2G / 3G / 4G / 5G, WiFi, etc., thereby obtaining data sent by the cloud / cloud server.

[0037] For smart home systems, the configuration method is as follows: The user terminal has a corresponding application installed. First, at least one gateway device can be added to the application. When adding other devices (such as cameras, door / window sensors, human body sensors, smart locks, smart switches, smart sockets, etc.), the "Add Device" button in the application interface can be clicked. The gateway device to which the device needs to be connected can then be selected, adding the device to the Zigbee network corresponding to that gateway. This, along with other added devices and the gateway, forms a Zigbee local area network. When the application, router, and gateway are on the same local area network, the application can interact with the gateway and devices connected to it via the local area network. When the application, router, and gateway are not on the same local area network, the application can interact with the gateway and devices connected to it via the wide area network (WAN).

[0038] Based on such Figure 1The smart home system shown currently offers device control methods where users can control target devices such as cameras with recording functions via user terminals such as mobile phones to record. However, if recording is required when devices such as door and window sensors, human body sensors, or smart door locks detect specific events, users usually need to manually control the target devices such as cameras to record on their user terminals when they discover that the device has detected a specific event. This can easily lead to missed recording opportunities and results in poor recording timeliness.

[0039] In response, the device control method provided in this application, based on the target events corresponding to each associated device contained in the associated configuration information of the target device, can control the target device to record video when the event detected by the associated device of the target device belongs to the target event corresponding to that associated device. This achieves a rapid response from event detection to device recording, ensuring timely recording without requiring the user to manually control the device to record, avoiding missed recording opportunities, and improving recording timeliness. Furthermore, displaying the event recordings of target events corresponding to different associated devices on the device page of the target device facilitates users to centrally review the event recordings of each target event, comprehensively understand each target event that has occurred, and helps improve the security of area monitoring.

[0040] The device control method of this application will be described below with reference to various embodiments and corresponding drawings.

[0041] In one exemplary embodiment, such as Figure 2 As shown, a device control method is provided, which is applied to... Figure 1 Taking a user terminal as an example, the method may include the following steps:

[0042] Step S201: In response to the associated device detecting that the event belongs to the target event corresponding to the associated device in the associated configuration information of the target device, control the target device to record the event to obtain the event recording of the target event.

[0043] The target device can be a device with recording capabilities, such as a camera or a smart door lock with a camera. Associated devices refer to devices associated with the target device, such as door / window sensors, human body sensors, smart door locks, smart switches, and smart sockets. The target device can be associated with one or more associated devices.

[0044] Each associated device can detect events it supports. For example, a door and window sensor can detect events such as "door and window open" and "door and window closed". A human body sensor can detect events such as "human movement", "human body detected", and "human body not detected".

[0045] In this step, events supported by the associated devices of the target device can be configured as target events for that associated device. Taking a door / window sensor as an example, the "door / window open" event can be determined as the target event for the door / window sensor associated with the target device. It can be understood that one or more events supported by the associated devices of the target device can be used as target events for each associated device. For example, the "door / window open" event and the "door / window closed" event can be used as target events for the door / window sensor. In this way, corresponding target events can be configured for each associated device of the target device.

[0046] Therefore, each associated device of the target device and the corresponding target event for each associated device can be configured to obtain the associated configuration information of the target device. The associated configuration information is the configured information containing the target device, associated devices, and the target events corresponding to the associated devices. The associated configuration information includes the association relationship between the target device, associated devices, and the target events corresponding to the associated devices, and may contain the target events corresponding to each associated device of the target device.

[0047] In this step, the associated device can detect the events it supports in real time. When the user terminal detects an event that corresponds to a target event in the associated device's configuration information, it controls the target device to record the event. The recorded event can be the audio and video recording generated by the target device recording the entire process of the target event.

[0048] Step S202: Display the event recordings of the target events corresponding to different associated devices on the device page of the target device.

[0049] The target device's device page refers to an interactive page that can be used to display relevant data, information, and functions of the target device. Specifically, it can be used to display data and information such as event recordings of the target event, as well as to display functions of the target device such as screenshots and recordings, making it convenient for users to query data and information and use related functions.

[0050] In this step, the user terminal can display event recordings of the target events corresponding to different associated devices on the target device's device page. Specifically, a playback area can be set on the target device's device page to play the event recordings of the target events, allowing the user to view the event recordings corresponding to each associated device.

[0051] The device control method in this embodiment responds to an event detected by an associated device belonging to a target event corresponding to an associated device in the associated configuration information of the target device, and controls the target device to record video to obtain an event recording of the target event. The associated device is a device associated with the target device, and the associated configuration information contains a target event corresponding to each associated device. The device page of the target device displays the event recordings of the target events corresponding to different associated devices. This solution, based on the target events corresponding to each associated device contained in the associated configuration information of the target device, can control the target device to record video to obtain an event recording of the target event when an event detected by an associated device of the target device belongs to that associated device. This achieves a rapid response from event detection to device recording, ensuring timely recording without requiring user manual control of the device, avoiding missed recording opportunities, and improving recording timeliness. Furthermore, displaying the event recordings of the target events corresponding to different associated devices on the device page of the target device facilitates users' centralized review of the event recordings of each target event, providing a comprehensive understanding of all target events and contributing to improved area monitoring security.

[0052] In one exemplary embodiment, such as Figure 3 As shown, the above method may further include the following steps:

[0053] Step S301: Display the configuration entry for the associated configuration information of the target device on the device page.

[0054] The configuration entry point refers to the entry point used to configure the associated configuration information of the target device. In this step, the "Associated Events" icon can be displayed on the device page as the configuration entry point for the associated configuration information of the target device.

[0055] In step S302, in response to the trigger operation of the configuration entry, the configuration page with associated configuration information is displayed.

[0056] The triggering operation for the configuration entry can be a click or other similar action. In this step, the user can click or perform other triggering operations on the configuration entry displayed on the device page. The user terminal responds to this triggering operation by displaying a configuration page for the associated configuration information. The configuration page refers to the interactive page used by the user to configure the associated configuration information; the user can configure the associated configuration information by performing configuration operations on the configuration page.

[0057] The configuration page can include multiple pages, each used to configure different content in the associated configuration information. For example, one configuration page can be used to configure associated devices, while another can be used to configure target events corresponding to those devices. The configuration operations can be determined based on the interactive operations required to configure different content in the associated configuration information; for example, they can include clicks, long presses, etc., without specific limitations here.

[0058] Step S303: In response to the configuration operation of the associated device and / or target event in the configuration page, obtain the associated configuration information of the target device.

[0059] In this step, the user can trigger configuration operations on the associated devices and / or target events in the configuration page on the user terminal. The user terminal responds to the configuration operations on the associated devices and / or target events by obtaining the associated configuration information of the target device. For example, the user can configure the target event corresponding to an associated device. In this case, the user terminal responds to the configuration operation on the target event by obtaining the associated configuration information of the target device. This can be applied when a user modifies a target event corresponding to an associated device, meaning that only the target event corresponding to the associated device needs to be reconfigured without reconfiguring the associated device itself.

[0060] As an example, a user can configure only the associated device. In this case, the user terminal responds to the configuration operation of the associated device and obtains the associated configuration information of the target device. This can be applied to a user selecting an associated device for associated recording control. The user terminal configures the corresponding target event for the associated device by default according to one or more events supported by the associated device. Thus, the user terminal can obtain the associated configuration information of the target device based on the associated device selected by the user and the default configured target event.

[0061] As an example, users can also configure associated devices and target events corresponding to associated devices. In this case, the user terminal responds to the configuration operations of associated devices and target events and obtains the associated configuration information of the target device.

[0062] The solution in this embodiment can integrate the associated configuration entry into the device page of the target device, eliminating the need for users to search through multiple levels, simplifying the configuration operation steps, making it easier for users to quickly complete the configuration operation, lowering the user operation threshold, improving the convenience of configuration, and also allowing for customized configuration and association of associated devices and target events as needed, which can adapt to different usage scenarios and users' personalized linkage recording needs, and has a wider range of applications.

[0063] In an exemplary embodiment, step S303, in response to configuration operations on associated devices and / or target events in the configuration page, obtains associated configuration information for the target device, including:

[0064] In response to configuration operations on associated devices and / or target events in existing associated configuration information on the configuration page, obtain the associated configuration information of the target device; and / or, in response to configuration operations on associated devices and target events in the associated configuration information to be added on the configuration page, obtain the associated configuration information of the target device.

[0065] In this embodiment, the existing associated configuration information refers to the associated configuration information that has been configured in the configuration page. Users can reconfigure the associated devices and / or target events in the existing associated configuration information. Specifically, users can reconfigure the associated devices in the existing associated configuration information, reconfigure the target events in the existing associated configuration information, or reconfigure both the associated devices and target events in the existing associated configuration information.

[0066] In this system, the user terminal responds to configuration operations on associated devices and / or target events in existing associated configuration information on the configuration page, obtaining the associated configuration information of the target device. This obtained associated configuration information includes the reconfigured associated devices and / or target events. Therefore, associated devices and target events in existing associated configuration information can be directly edited and updated on the configuration page without recreating the entire configuration. This enables flexible editing and dynamic updating of existing configurations. Users can adjust associated devices or change corresponding target events individually according to actual usage needs, or adjust both associated devices and corresponding target events simultaneously to flexibly adapt to changes in different security and video recording scenarios.

[0067] In this embodiment, the associated configuration information to be added refers to the associated configuration information to be added and configured on the configuration page. That is, the user can add associated configuration information on the configuration page. When adding associated configuration information, the associated device and target event in the associated configuration information to be added can be configured. The user terminal responds to the configuration operation of the associated device and target event in the associated configuration information to be added on the configuration page and obtains the associated configuration information of the target device. The obtained associated configuration information includes the newly added associated device and the corresponding target event. Therefore, it supports the independent configuration of adding associated devices and corresponding target events on the configuration page, and can flexibly expand the associated configuration information of the target device as needed. Associated configuration information can be added at any time according to the actual usage scenario, exhibiting strong configuration scalability. At the same time, the newly added associated configuration information can be directly incorporated into the associated configuration information of the target device, taking effect quickly and subsequently used for event detection and video recording linkage control. This facilitates flexible adaptation to the linkage recording needs of multiple devices and multiple scenarios, improving its scalability and scenario adaptability.

[0068] In this embodiment, users can configure both existing associated configuration information and new associated configuration information on the configuration page. For example, they can edit and update associated devices and target events in existing associated configuration information on the configuration page, and also add new associated configuration information. Specifically, in response to configuration operations on associated devices and / or target events in existing associated configuration information on the configuration page, and in response to configuration operations on associated devices and target events in new associated configuration information on the configuration page, the user terminal obtains the associated configuration information of the target device. This associated configuration information includes newly added associated devices and corresponding target events, as well as reconfigured associated devices and / or target events. This allows for both updating existing associated configuration information and quickly adding new associated configuration information, improving the efficiency of editing and maintaining associated configuration information and enhancing the scalability and adaptability to different scenarios.

[0069] In one exemplary embodiment, such as Figure 4 As shown, the above response to the configuration operations of the associated device and target event in the configuration page to be added associated configuration information, obtaining the associated configuration information of the target device, may include:

[0070] Step S401: In response to the device addition operation on the configuration page, determine the added associated device.

[0071] The device addition operation refers to the operation used to add associated devices to the target device, which may include actions such as clicking. In this step, combined with... Figure 5 The configuration entry 510, which displays the associated configuration information of the target device, can be displayed in the real-time page 500 included in the device page of the target device. This configuration entry 510 can be represented by an "associated event" icon.

[0072] Combination Figure 6 In response to the triggering operation of the configuration entry 510, the user terminal can display the configuration page of the target device's associated configuration information, including the configuration display page 600. The configuration display page 600 can show the existing associated configuration information (including associated configuration 1, associated configuration 2, etc.). The user can enable or disable the existing associated configuration information such as associated configuration 1 and associated configuration 2 on the configuration display page 600. The configuration display page 600 can also display the associated configuration addition control 610 for adding associated configuration information of the target device.

[0073] Combination Figure 7The user terminal can respond to the triggering operation of the associated configuration addition control 610 to display the configuration addition page 700, which includes the configuration page. This configuration addition page 700 can display the newly added associated configuration control 710 and its color configuration control 720. The triggering operation of the associated configuration addition control 610 can be considered as one of the device addition operations on the configuration page. The newly added associated configuration control 710 is used to add associated devices and corresponding target events of the target device, while the color configuration control 720 is used to set the color of the target event displayed on the device page, which can be used to distinguish different events and other objects.

[0074] Furthermore, combined Figure 8 In response to a trigger operation on the newly added associated configuration control 710, the user terminal can display a device selection page 800 included in the configuration page. This device selection page 800 can be used to select a device to be associated with the target device. The device selection page 800 displays multiple devices (device 1, device 2, device 3, etc.) that can be associated with the target device. The user can trigger an operation on one of these devices on the device selection page 800, and the user terminal can confirm that device as the added associated device in response to the trigger operation. This trigger operation on the device can be considered one of the device addition operations in the configuration page.

[0075] Step S402: Display the event selection page for the added associated devices. The event selection page displays the various events supported by the added associated devices.

[0076] In this step, the event selection page refers to the page used to select the target events corresponding to the added associated devices. Combined with... Figure 8 and Figure 9 The user terminal can respond to the trigger operation on device 2 in the device selection page 800, confirming device 2 as an added associated device. The user terminal can then display the event selection page 900 for device 2, which displays various events supported by the added associated device, i.e., events supported by device 2 (such as event 1, event 2, event 3, etc.). These events can be used by the user to select the target event corresponding to device 2.

[0077] Step S403: In response to the event selection operation on the event selection page, determine the target event corresponding to the added associated device.

[0078] The event selection operation refers to the selection of events supported by the added associated devices, triggered on the event selection page. In this step, we combine... Figure 9Users can trigger a selection operation on the event selection page 900 for one of the events supported by device 2. The user terminal responds to the event selection operation and determines the selected event as the target event corresponding to the added associated device. For example, event 2 can be selected as the target event corresponding to device 2.

[0079] Step S404: Obtain the association configuration information of the target device based on the target event corresponding to the added associated device.

[0080] In this step, the user terminal can obtain the association configuration information of the target device based on the added associated device and its corresponding target event.

[0081] The solution in this embodiment allows users to quickly select the associated device to be added by performing a device addition operation on the configuration page. Then, it can jump to and display an event selection page that supports all events of the associated device, allowing users to intuitively view the available events and select the target event. Finally, the associated configuration information of the target device is automatically generated based on the selected associated device and its corresponding target event, without requiring users to manually input complex configuration parameters, thus improving configuration accuracy and operational efficiency. It can quickly complete the associated configuration of the target device, associated device and corresponding target event.

[0082] In an exemplary embodiment, step S201, controlling the target device to record video to obtain an event recording of the target event, may include: controlling the target device to record video to obtain video data; and obtaining an event recording of the target event based on the video data and the association relationship between the associated device, the target event, and the target device.

[0083] In this embodiment, the video recording data may include audio and video recording data obtained by the user terminal controlling the target device to record, as well as information such as the recording time. The video recording data may be uploaded by the target device to the server, and the server may associate and store the video recording data with the associated devices, target events, and target devices based on the video recording data and the association relationship between the associated devices, target events, and target devices.

[0084] This includes setting event recording identifiers for video data, setting associated device identifiers for associated devices, setting target event identifiers for target events, and setting target device identifiers for target devices. Based on the video data and the association between its event recording identifiers and associated device identifiers, as well as the relationship between the target event identifier and the target device identifier, the event recording of the target event can be obtained.

[0085] The event recording of the target event can be uniquely identified by an event recording identifier. The event recording may contain recording data and the association relationships between the event recording identifier and associated device identifiers, as well as between the target event identifier and the target device identifier. Therefore, by associating the recording data with associated devices, target events, and target devices, it is convenient to subsequently filter and view event recordings of various target events based on various dimensions.

[0086] In an exemplary embodiment, step S202, displaying event recordings of target events corresponding to different associated devices on the target device's device page, may include:

[0087] Display event recording identifiers for the target event on the timeline of the target device's device page, or display event recording identifiers for the target event on the event list of the target device's device page; in response to the selection of the event recording identifier for the target event, play the event recording corresponding to the target event.

[0088] In this embodiment, the event recording identifiers of target events corresponding to different associated devices can be displayed on the device page of the target device in the form of a timeline or an event list. The event recording identifier of the target event is used to trigger the playback of the event recording corresponding to the target event. The playback area corresponding to the target event can be set on the device page of the target device to play the event recording.

[0089] The timeline can be a visual display control arranged in chronological order on the device page of the target device. With time as the baseline, it sequentially arranges the event recording icons corresponding to the target events triggered by each associated device, which can intuitively present the sequence of occurrence of the target events in chronological order, allowing users to quickly browse and find the event recordings corresponding to each target event by time.

[0090] The event list can be a visual display control on the device page of the target device, arranged in the form of an item list. It can list the event recording identifiers of the target events corresponding to different associated devices, and display the event recording identifiers of each target event in a neat and orderly manner in an itemized way. The structure is clear and easy to browse and select item by item.

[0091] As an example, as shown in Figure 10(a), event recording identifiers 1011 corresponding to different associated devices for the target event can be displayed on the timeline 1010 of the playback page 1000 included in the device page of the target device. In response to the selection operation of the event recording identifier 1011 of the target event (such as clicking the event recording identifier 1011), the user terminal can play the event recording corresponding to the target event in the playback area of ​​the playback page 1000. The user can slide the timeline to a specified event recording identifier to play the event recording, and it supports full-screen playback, event recording download, sharing, and deletion functions.

[0092] As an example, as shown in Figure 10(b), the event recording identifiers 1021 corresponding to different associated devices for the target event can be displayed in the event list 1020 of the playback page 1000 included in the device page of the target device. The event recording identifiers 1021 displayed in the event list 1020 can include information such as the name of the target event, the name of the associated device, the time the target event occurred, and a preview image of the event recording corresponding to the target event. The preview image can be the first frame of the video data recorded in the event recording, or a thumbnail of the first frame. In response to the selection operation of the event recording identifier 1021 of the target event (such as clicking the event recording identifier 1021), the user terminal can play the event recording corresponding to the target event in the playback area of ​​the playback page 1000. Clicking any event recording identifier allows playback of the event recording, and supports full-screen playback, event recording download, sharing, and deletion functions.

[0093] The solution in this embodiment can provide two different display formats, timeline and event list, to present the event recording identifiers of the target events corresponding to each associated device. It can adapt to different user viewing habits and needs, and the operation is simple and intuitive, without the need for multi-level navigation, thus improving the efficiency of browsing, searching and playing back event recordings.

[0094] In some embodiments, further, taking FIG10(a) as an example, the playback page 1000 may display an identifier filtering control 1030, which can be used to filter the event recording identifiers displayed on the playback page 1000, and the user terminal can respond to the trigger operation of the identifier filtering control 1030.

[0095] Combination Figure 11 The user terminal can display the event filtering page 1040 of the target device. The event filtering page 1040 can be used to filter events supported by the target device itself and related events (i.e., target events corresponding to related devices of the target device). In this embodiment, the user terminal can respond to the triggering operation of the related event item (used to indicate filtering of related events) in the event filtering page 1040.

[0096] Combination Figure 12 The user terminal can display the associated event filtering page 1050 for the target device. This page allows filtering of target events corresponding to associated devices. For example, filtering can be done by location (device deployment location, such as a room) or device type (gateway control, camera, smoke alarm, etc.). Users can also configure the color of the event recording identifiers for the filtered target events. After filtering, users can click "Save and Return." The user terminal can display the event recording identifiers of the filtered target events on the playback page 1000 for targeted browsing and playback. Users no longer need to search for target events across all screens, thus easily obtaining information about the various target events that have occurred.

[0097] In one exemplary embodiment, the number of associated devices is multiple; the target event includes events detected simultaneously by multiple associated devices.

[0098] In this embodiment, the number of associated devices of the target device can be multiple. In this regard, the target events corresponding to the multiple associated devices of the target device include events detected simultaneously by the multiple associated devices. That is, the target events corresponding to the multiple associated devices of the target device can be composite target events. Composite target events contain events detected simultaneously by multiple associated devices. The events detected by each associated device can be different, the same, or partially the same.

[0099] As an example, the associated devices of the target device may include door and window sensors and human body sensors, and the target event may include the door and window sensor detecting "door and window open" and the human body sensor detecting "human body movement". That is, the composite target event may be "door and window open and human body movement".

[0100] This embodiment supports configuring multiple associated devices for a target device, and events detected simultaneously by multiple associated devices can be set as composite target events. The events detected by each associated device can be different from each other, completely the same, or partially the same. This breaks through the limitation of a single associated device triggering recording with a single event, and enables the linkage and combination triggering of multiple devices and multiple events. It can be used to simulate complex anomalies in real security scenarios, greatly enriching the configuration dimensions and triggering logic of target events, adapting to the differentiated needs of complex home and security monitoring scenarios, improving the accuracy and scenario adaptability of device linkage recording triggering, and effectively reducing the probability of false recording triggered by a single event.

[0101] In an exemplary embodiment, step S201, which responds to the associated device detecting an event that belongs to the target event corresponding to the associated device in the associated configuration information of the target device, and controls the target device to record video to obtain an event recording of the target event, may include:

[0102] In response to an event detected by an associated device that is a target event corresponding to the associated device in the associated configuration information of the target device, the target device is controlled to record video of the area where the associated device is located to obtain the event video of the target event.

[0103] The associated device area can be the area where the associated device is deployed. For example, if the door and window sensor is deployed in the living room, then the associated device area is the living room.

[0104] In this embodiment, in response to an event detected by an associated device that belongs to the target event corresponding to the associated device in the associated configuration information of the target device, the user terminal controls the target device to record video of the area where the associated device is located to obtain the event recording of the target event.

[0105] In this embodiment, when an event detected by an associated device matches the corresponding target event in the associated configuration information of the target device, the target device is controlled to record video specifically in the area where the associated device is located and generate event recordings. This eliminates the need for indiscriminate recording of the entire area covered by the target device, allowing for precise focus on the specific area where the event occurred. This effectively reduces the generation of invalid recording data, lowers the storage pressure and energy consumption of the target device, and ensures that the event recordings only include event-related content in the area where the associated device is located, avoiding interference from irrelevant areas. This improves the targeting and effectiveness of the event recordings, making it easier for users to quickly locate the location and process of the event, further optimizing the efficiency of reviewing event recordings, and enhancing the accuracy and resource utilization efficiency of the target device's linked recordings.

[0106] In an exemplary embodiment, the above method may further include the following steps: displaying the device control of the associated device corresponding to the target event on the device page of the target device.

[0107] In this embodiment, the device control of the associated device can be used to control the associated device. Specifically, the user terminal can respond to the triggering operation of the device control of the associated device corresponding to the target event displayed on the target device's device page, and control the associated device to perform the corresponding action.

[0108] This embodiment displays the device control of the associated device corresponding to the target event on the device page of the target device. The device control can directly control the associated device, thereby integrating the event recording viewing and associated device control functions into the same device page. Users can complete device management without switching to other operation interfaces, simplifying the operation process, reducing page jump steps, and allowing users to quickly locate and control the associated device at the time of the event while viewing the event recording. This realizes the linkage management of event viewing and device control, which is intuitive and convenient, and improves the response efficiency and overall user experience of associated device management.

[0109] In an exemplary embodiment, the device control method of this application is specifically described using a camera as the target device. The associated devices of the target device may include, but are not limited to, door and window sensors, human body sensors, smart door locks, smart switches, and smart sockets. The application scenarios of this method may include: Home security monitoring: The user associates the camera with the door and window sensor, sets "door and window opening" as the target event, and when the door or window is opened, the camera automatically records video, generating a "door and window opening event recording"; Elderly / child care: The camera is associated with the human body sensor, sets "human movement" as the target event, and recording begins when human movement is detected, recording the activity scene; Device operation monitoring: The camera is associated with the smart socket (connected to home appliances), sets "socket powered on" as the target event, and the camera records video when the home appliance is started, monitoring the device's operating status.

[0110] In terms of functionality, it supports users in selecting added devices, including but not limited to door and window sensors, human body sensors, smart door locks, smart switches, smart sockets, and cameras, and can associate multiple devices at the same time.

[0111] After linking devices, users can select the events supported by that device as the target event on the corresponding page (e.g., door and window sensors support "open" and "close" events, and human body sensors support "human body detected" and "human body not detected" events). When the linked device triggers the target event, the camera can immediately start recording. The recording duration can be determined by the linked device and can be dynamically extended based on the event's trigger status. All event recordings from the camera can be displayed on the user terminal in chronological order. Each event recording can be identified by the corresponding linked device name, target event type, and other information. Clicking the event recording icon will directly play the recording. Viewing, downloading, deleting, and sharing of event recordings are supported, and users can filter and search by linked device and event type.

[0112] From a hardware perspective, this can include camera equipment, associated devices, servers / cloud servers, and user terminals, among which:

[0113] The camera equipment is equipped with a network communication module (supporting Wi-Fi / Bluetooth), an image sensor, a storage module (local storage / cloud storage), and a processor, and supports receiving recording commands and starting recording.

[0114] The associated devices are equipped with sensor modules (such as magnetic sensors for door and window sensors, and infrared sensors for human body sensors) and network communication modules, which can support the detection of changes in their own status and the generation of event signals.

[0115] The server or cloud server is responsible for receiving event signals from associated devices, storing associated configuration information, sending recording instructions to cameras, and storing recording data.

[0116] The user terminal has a corresponding application installed, which supports user operation configuration and viewing of recordings.

[0117] In terms of implementation logic:

[0118] User terminal: Provides an interactive page for selecting associated devices and setting target events, and uploads associated configuration information to the server through the application programming interface;

[0119] Retrieve associated configuration information and event recording list data from the server and display them on the corresponding page of the application, supporting filtering and sorting functions;

[0120] The video playback component loads event recordings stored on the server and provides interfaces for playback, pause, download, and sharing.

[0121] For the server: Receive and store the camera association configuration information submitted by the user, which may include camera ID (identifier), a list of associated device IDs, target event IDs corresponding to each associated device, trigger time conditions, etc., and establish the association relationship between the camera and the associated devices;

[0122] It can receive event signals sent by associated devices in real time. The event signals may include associated device ID, event type ID, trigger timestamp, etc.

[0123] Based on the associated device ID in the received event signal, query the associated camera ID and the associated configuration information of the target event corresponding to the associated device, and determine whether the current event is a target event set by the user and whether the trigger time condition is met.

[0124] If the event is successfully matched, a recording instruction is sent to the corresponding camera. The recording instruction may include the target event ID and the associated device ID.

[0125] Receive video recording data uploaded by the camera, associate the video recording data with the associated device ID, event type, trigger time, and camera ID, and store the data to generate a unique recording ID for the event recording;

[0126] Synchronize the associated information of the event recording (recording ID, device name, event type, trigger time) to the user terminal for display.

[0127] The data processing flow can include a configuration flow, an event triggering and recording flow, and a recording viewing flow, among which:

[0128] For the associated configuration process:

[0129] like Figure 13 As shown, after the user completes the configuration, the user terminal can encapsulate the associated configuration information in JSON (JavaScript Object Notation) format. The user terminal can then upload the associated configuration information to the server via HTTPS protocol (TLS 1.3 encryption). The configuration storage module in the server can further perform double verification (authorization verification + legality verification) on the associated configuration information. After successful verification, the information is written to the MySQL database and synchronized to the Redis cache on the server, where an index is created. After the server verifies and stores the associated configuration information, it returns a "configuration successful" response (e.g., status code 200) to the user terminal. The user terminal's page then displays a prompt and updates the associated configuration information, showing the latest associated configuration information.

[0130] Regarding the event triggering and recording process:

[0131] like Figure 14 As shown, if an associated device (such as a door or window sensor) detects a change in status, it generates an event signal. This event signal can then be reported to the server via the MQTT (Message Queuing Telemetry Transport) protocol. Upon receiving the event signal from the associated device, the server parses it. This parsing process may include extracting the associated device ID, event type, timestamp, and filtering invalid events (such as duplicate reports or offline reports).

[0132] The server then queries the Redis cache for the association configuration information of the target device associated with the associated device, verifying whether the event type matches. Simultaneously, the Redis cached association configuration information can be synchronized with the MySQL database every preset interval (e.g., 5 minutes) to ensure that configuration changes take effect in real time. Once a match is found, the server generates a recording command, which can be sent to the camera using the TCP protocol.

[0133] After receiving a recording command, the camera can record video and generate an MP4 file as the recording data. The camera can then upload the recording data and its corresponding MD5 value to the server using the HTTPS protocol (Hypertext Transfer Protocol).

[0134] After receiving the video recordings uploaded by the camera, the server performs integrity verification and storage. This is done by extracting metadata (associated device ID, event type, timestamp, etc.) and building an inverted index for storage. The server can then push the recorded events to the user's terminal via WebSocket, allowing the user's terminal to update the event list and display unread red dots.

[0135] Regarding the video viewing process:

[0136] like Figure 15 As shown, after the user clicks the playback control on the camera page in the user terminal, the user terminal enters the playback page, and then the user terminal can send a recording query request (including the camera ID bound to the current account) to the server via WebSocket.

[0137] The server then queries the event recording table and uses an inverted index to filter all event recording data from cameras associated with the user's account. Specifically, the event recording data can be sorted in reverse order by trigger time. The server can then return the data used for event recording display (including thumbnail (first frame of video) URL, device name, event type, trigger time, and playback address) to the user's terminal.

[0138] After receiving the data, the user terminal can render an event list. Specifically, the core information of each event recording (such as thumbnail, device name, trigger time, etc.) can be displayed through event recording icons. When the user clicks on the corresponding event recording icon, the user terminal loads the recording data corresponding to the playback address through the video playback component to complete the playback operation.

[0139] This application provides a method for configuring a camera to be associated with multiple smart devices (such as door and window sensors, human body sensors, smart switches, etc.), and automatically starting the camera recording function based on specific events triggered by the associated devices, while providing a unified event recording viewing and management interface on the user terminal.

[0140] The camera's one-to-many association configuration mechanism with multiple associated devices allows for the independent setting of different recording trigger events for each associated device. Based on a server-side distributed event notification and processing architecture, it enables rapid response from device events to camera actions. The camera's device page can categorize and aggregate recordings triggered by different associated devices, and the server can associate and store information such as the triggering device, event type, and trigger time with the recording data.

[0141] The solution in this application supports the association of cameras with various types of devices, and the target events can be customized, covering diverse scenarios such as home security, device monitoring, and elderly and child care. It can avoid the problems of single linkage type and fixed events. The device page of the target device provides an entry point for association configuration and event recording association display. Users do not need to operate across modules and can quickly complete the configuration and view the recordings corresponding to the target events. Recording can be started only when the target event occurs, avoiding invalid recordings occupying storage resources. At the same time, the event recording is bound to the triggering event and associated device, and users can quickly locate key recordings.

[0142] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0143] Based on the same inventive concept, this application also provides a device control apparatus for implementing the device control method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more device control apparatus embodiments provided below can be found in the limitations of the device control method described above, and will not be repeated here.

[0144] In one exemplary embodiment, such as Figure 16 As shown, a device control apparatus is provided, the apparatus 1600 may include:

[0145] The recording trigger module 1601 is used to control the target device to record an event to obtain an event recording of the target event in response to an event detected by an associated device belonging to the associated device in the associated configuration information of the target device; the associated device is a device associated with the target device; the associated configuration information contains the target event corresponding to each associated device;

[0146] The video recording module 1602 is used to display event recordings of target events corresponding to different associated devices on the device page of the target device.

[0147] In an exemplary embodiment, the device 1600 may further include: an information configuration module, configured to display a configuration entry for associated configuration information of the target device on the device page; display a configuration page for the associated configuration information in response to a triggering operation of the configuration entry; and obtain the associated configuration information of the target device in response to a configuration operation of the associated device and / or target event on the configuration page.

[0148] In an exemplary embodiment, the information configuration module is configured to obtain the associated configuration information of the target device in response to a configuration operation on the associated device and / or target event in the existing associated configuration information on the configuration page; and / or, in response to a configuration operation on the associated device and target event in the associated configuration information to be added on the configuration page, obtain the associated configuration information of the target device.

[0149] In an exemplary embodiment, the information configuration module is configured to, in response to a device addition operation on the configuration page, determine the added associated device; display an event selection page for the added associated device; the event selection page displays various events supported by the added associated device; in response to an event selection operation on the event selection page, determine the target event corresponding to the added associated device; and obtain the associated configuration information of the target device based on the target event corresponding to the added associated device.

[0150] In an exemplary embodiment, the recording trigger module 1601 is used to control the target device to record video to obtain recording data; based on the recording data and the association relationship between the associated device, the target event and the target device, an event recording of the target event is obtained.

[0151] In an exemplary embodiment, the video recording display module 1602 is configured to display event recording identifiers of different associated devices corresponding to target events on the timeline of the device page of the target device, or to display event recording identifiers of different associated devices corresponding to target events in the event list of the device page of the target device; the event recording identifier of the target event is used to trigger the playback of the event recording corresponding to the target event; in response to the selection operation of the event recording identifier of the target event, the event recording corresponding to the target event is played.

[0152] In one exemplary embodiment, the number of associated devices is multiple; the target event includes events detected simultaneously by multiple associated devices.

[0153] In an exemplary embodiment, the recording trigger module 1601 is configured to, in response to an event detected by an associated device belonging to a target event corresponding to the associated device in the associated configuration information of the target device, control the target device to record the event in the area where the associated device is located to obtain the event recording of the target event.

[0154] In an exemplary embodiment, the device 1600 may further include: a control display module, configured to display a device control of the associated device corresponding to the target event on the device page of the target device; the device control is used to control the associated device.

[0155] Each module in the aforementioned equipment control device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of the electronic device in hardware form or independent of it, or stored in the memory of the electronic device in software form, so that the processor can call and execute the operations corresponding to each module.

[0156] In one exemplary embodiment, an electronic device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 17 As shown, this electronic device includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input / output interface is used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a device control method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the electronic device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the electronic device, or external keyboards, touchpads, or mice, etc.

[0157] Those skilled in the art will understand that Figure 17The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which 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 different component arrangements.

[0158] In one embodiment, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0159] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

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

[0161] 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, data stored, data displayed, 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 the relevant data must comply with relevant regulations.

[0162] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this 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. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0163] The technical features of the above embodiments can be combined in any way. For the sake of brevity, 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.

[0164] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A device control method, characterized in that, The method includes: In response to an event detected by an associated device belonging to a target event corresponding to the associated device in the association configuration information of the target device, the target device is controlled to record video to obtain an event recording of the target event; the associated device is a device associated with the target device; the association configuration information contains the target event corresponding to each associated device; The device page of the target device displays event recordings of the target events corresponding to different associated devices.

2. The method according to claim 1, characterized in that, The method further includes: The configuration entry point for displaying the associated configuration information of the target device is shown on the device page; In response to a trigger operation on the configuration entry, a configuration page displaying the associated configuration information is shown; In response to configuration operations on associated devices and / or target events on the configuration page, the associated configuration information of the target device is obtained.

3. The method according to claim 2, characterized in that, The step of responding to configuration operations on associated devices and / or target events on the configuration page to obtain associated configuration information of the target device includes: In response to configuration operations on associated devices and / or target events in existing associated configuration information on the configuration page, the associated configuration information of the target device is obtained; And / or, In response to the configuration operations of the associated device and target event in the configuration page to be added associated configuration information, the associated configuration information of the target device is obtained.

4. The method according to claim 3, characterized in that, In response to configuration operations on the associated device and target event in the configuration page for adding associated configuration information, the associated configuration information of the target device is obtained, including: In response to the device addition operation on the configuration page, the added associated devices are determined; The event selection page of the added associated device is displayed; the event selection page displays various events supported by the added associated device. In response to the event selection operation on the event selection page, the target event corresponding to the added associated device is determined; Based on the target event corresponding to the added associated device, the associated configuration information of the target device is obtained.

5. The method according to claim 1, characterized in that, The event recording obtained by controlling the target device to record the target event includes: Control the target device to record video and obtain video data; Based on the recorded data, as well as the associated devices, the target event, and the relationship between the target devices, the event recording of the target event is obtained.

6. The method according to claim 1, characterized in that, The display of event recordings corresponding to different associated devices on the device page of the target device includes: The event recording identifiers of different associated devices corresponding to the target events are displayed on the timeline of the device page of the target device, or the event recording identifiers of different associated devices corresponding to the target events are displayed in the event list of the device page of the target device; the event recording identifier of the target event is used to trigger the playback of the event recording corresponding to the target event; In response to the selection of the event recording identifier for the target event, the event recording corresponding to the target event is played.

7. The method according to any one of claims 1 to 6, characterized in that, The number of associated devices is multiple; the target event includes events detected simultaneously by multiple associated devices.

8. The method according to any one of claims 1 to 6, characterized in that, The step of responding to an event detected by an associated device belonging to a target event in the associated configuration information of the target device, and controlling the target device to record video to obtain an event recording of the target event, includes: In response to an event detected by an associated device belonging to a target event corresponding to the associated device in the associated configuration information of the target device, the target device is controlled to record video of the area where the associated device is located to obtain the event video of the target event.

9. The method according to any one of claims 1 to 6, characterized in that, The method further includes: The device control of the associated device corresponding to the target event is displayed on the device page of the target device; the device control is used to control the associated device.

10. A device control apparatus, characterized in that, The device includes: The recording trigger module is used to respond to an event detected by an associated device that belongs to a target event corresponding to the associated device in the association configuration information of the target device, and to control the target device to record the event to obtain an event recording of the target event; the associated device is a device associated with the target device; the association configuration information contains a target event corresponding to each associated device; The video recording module is used to display event recordings of target events corresponding to different associated devices on the device page of the target device.

11. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 9.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 9.

13. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 9.

Images