Device linkage method, apparatus, system, electronic device, and storage medium

Abstract

The application provides a device linkage method, device, system, electronic device and storage medium, and relates to the technical field of Internet of Things. The method applied to a first server device comprises the following steps: receiving a linkage trigger request sent by a second server device; determining a device linkage rule to be triggered based on the linkage trigger request; determining at least one to-be-controlled device and a control instruction corresponding to each to-be-controlled device based on the device linkage rule, wherein any to-be-controlled device corresponds to at least one control instruction; and sending each control instruction to the corresponding to-be-controlled device. The application can trigger device linkage by user's active selection, improve user experience, and improve the accuracy of device linkage.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) technology, and in particular to a device linkage method, apparatus, system, electronic device, and storage medium. Background Technology

[0002] With the rapid development of IoT technology, more and more smart devices are engaging in device linkage. Device linkage refers to the coordinated response of multiple devices triggered by pre-defined rules, achieving interconnectedness and intelligent control. The device linkage process is crucial to user experience, therefore, it is necessary to optimize device linkage methods.

[0003] Currently, device linkage is controlled by changes in the state of IoT sensors, or by changes in factors such as time and weather. However, these methods are greatly affected by changes in the external environment, and the triggering conditions may cause misjudgments and false alarms, thereby reducing the accuracy of device linkage. Furthermore, the triggering conditions cannot be actively selected by the user, which affects the user experience. Summary of the Invention

[0004] This invention provides a device linkage method, apparatus, system, electronic device, and storage medium to address the deficiency in the prior art where device linkage modes cannot be actively selected and triggered by the user, thereby enabling the user to actively trigger device linkage rules and thus improving the user experience.

[0005] This invention provides a device linkage method applied to a first server device, the method comprising:

[0006] Receive the linkage trigger request sent by the second server device;

[0007] Based on the linkage trigger request, determine the device linkage rules to be triggered;

[0008] Based on the device linkage rules, at least one device to be controlled is determined, and control instructions corresponding to each device to be controlled are determined. Each device to be controlled corresponds to at least one control instruction.

[0009] Each of the aforementioned control commands is sent to the corresponding device to be controlled;

[0010] The generation method of the linkage trigger request includes at least one of the following:

[0011] The first client device stores the device linkage rules, and the linkage trigger request is generated by the second server device based on the first trigger request sent by the second client device. The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device.

[0012] The first server device stores the device linkage rules. The linkage trigger request is generated by the second server device based on the second trigger request sent by the first client device. The second trigger request is triggered based on the voice communication method between the first client device and the second server device.

[0013] The present invention also provides a device linkage method, applied to a second server device, the method comprising:

[0014] Receive a trigger request, the trigger request including a first trigger request sent by the second client device, or a second trigger request sent by the first client device;

[0015] Based on the aforementioned trigger request, a linkage trigger request is generated;

[0016] The linkage trigger request is sent to the first server device, so that the first server device can determine the device linkage rules to be triggered based on the linkage trigger request, and realize device linkage control based on the device linkage rules;

[0017] The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device;

[0018] The second trigger request is triggered based on the voice communication method between the first client device and the second server device.

[0019] The present invention also provides a device linkage method, applied to a first client device, the method comprising:

[0020] If a rule retrieval instruction is received from the second client device, the device linkage rules stored in the first client device are sent to the second client device, so that the second client device generates a first trigger request based on the device linkage rules, and sends the first trigger request to the second server device;

[0021] If the first client device and the second server device are in a voice communication state, the second trigger request is obtained and sent to the second server device so that the second server device can generate a linkage trigger request based on the second trigger request and send the linkage trigger request to the first server device.

[0022] The present invention also provides a device linkage method applied to a second client device, the method comprising:

[0023] Receive device linkage rules sent by the first client device;

[0024] Based on the device linkage rules, a first trigger request is generated so that the first trigger request indicates the device linkage rules;

[0025] The first trigger request is sent to the second server device, so that the second server device generates a linkage trigger request based on the first trigger request, and sends the linkage trigger request to the first server device.

[0026] The present invention also provides a device linkage apparatus, deployed on a first server device, the apparatus comprising:

[0027] The first receiving module is used to receive the linkage trigger request sent by the second server device;

[0028] The first determining module is used to determine the device linkage rules to be triggered based on the linkage triggering request;

[0029] The second determining module is used to determine at least one device to be controlled and control instructions corresponding to each device to be controlled based on the device linkage rules, wherein any device to be controlled corresponds to at least one control instruction.

[0030] The first sending module is used to send each of the control commands to the corresponding device to be controlled;

[0031] The generation method of the linkage trigger request includes at least one of the following:

[0032] The first client device stores the device linkage rules, and the linkage trigger request is generated by the second server device based on the first trigger request sent by the second client device. The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device.

[0033] The first server device stores the device linkage rules. The linkage trigger request is generated by the second server device based on the second trigger request sent by the first client device. The second trigger request is triggered based on the voice communication method between the first client device and the second server device.

[0034] The present invention also provides a device linkage apparatus deployed on a second server device, the apparatus comprising:

[0035] The second receiving module is used to receive trigger requests, the trigger requests including a first trigger request sent by the second client device, or a second trigger request sent by the first client device;

[0036] The first generation module is used to generate a linkage trigger request based on the trigger request;

[0037] The second sending module is used to send the linkage trigger request to the first server device, so that the first server device can determine the device linkage rules to be triggered based on the linkage trigger request, and realize device linkage control based on the device linkage rules;

[0038] The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device;

[0039] The second trigger request is triggered based on the voice communication method between the first client device and the second server device.

[0040] The present invention also provides a device linkage device, deployed on a first client device, the device comprising:

[0041] The third sending module is used to send the device linkage rules stored in the first client device to the second client device if a rule acquisition instruction is received from the second client device, so that the second client device generates a first trigger request based on the device linkage rules and sends the first trigger request to the second server device;

[0042] The fourth sending module is used to obtain a second trigger request if the first client device and the second server device are in a voice communication state, and send the second trigger request to the second server device so that the second server device can generate a linkage trigger request based on the second trigger request and send the linkage trigger request to the first server device.

[0043] The present invention also provides a device linkage device, deployed on a second client device, the device comprising:

[0044] The third receiving module is used to receive the device linkage rules sent by the first client device;

[0045] The second generation module is used to generate a first trigger request based on the device linkage rule, so that the first trigger request indicates the device linkage rule;

[0046] The fifth sending module is used to send the first trigger request to the second server device, so that the second server device generates a linkage trigger request based on the first trigger request and sends the linkage trigger request to the first server device.

[0047] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement any of the device linkage methods described above.

[0048] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the device linkage method as described above.

[0049] The device linkage method, apparatus, system, electronic device, and storage medium provided by this invention involve a first server device receiving a linkage trigger request sent by a second server device. Based on the linkage trigger request, the first server device determines the device linkage rules to be triggered, and then, based on the device linkage rules, determines at least one device to be controlled, as well as control instructions corresponding to each device to be controlled. The first server device then sends each control instruction to its corresponding device to be controlled, thus achieving a device linkage triggering method independent of a gateway device. Furthermore, the linkage trigger request is generated by the second server device based on a first trigger request sent by a second client device. This first trigger request is generated by the second client device based on the device linkage rules sent by the first client device. Therefore, when the first client and the second client are close together, i.e., when near-field communication is achieved, the second client device can obtain the device linkage information stored by the first client device. The invention provides two methods for triggering device linkage: a first method and a second method. The first method generates a linkage trigger request via a second server device based on a second trigger request sent by the first client device. This second trigger request is triggered by voice communication between the first client device and the second server device. Since the first client device and the second server device are in voice communication, the user can trigger the second trigger request on the first client device, enabling cloud-based device linkage via voice communication. This allows the user to actively choose to trigger device linkage, further enhancing the user experience. This method is also unaffected by external environments, improving the accuracy of device linkage. Furthermore, these two methods of generating linkage trigger requests allow for two triggering methods for device linkage: near-field communication and voice communication. This provides flexible and convenient device linkage, offering a more comprehensive and complete triggering experience, thus improving the user experience. In summary, this invention allows users to actively choose to trigger device linkage, improving the user experience and increasing the accuracy of device linkage. Attached Figure Description

[0050] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0051] Figure 1 This is one of the flowcharts illustrating the device linkage method provided by the present invention;

[0052] Figure 2 The second schematic diagram of the device linkage method provided by the present invention;

[0053] Figure 3 The third flowchart illustrating the device linkage method provided by the present invention;

[0054] Figure 4 The fourth flowchart illustrating the device linkage method provided by the present invention;

[0055] Figure 5 The fifth flowchart illustrating the device linkage method provided by the present invention;

[0056] Figure 6 The sixth flowchart illustrating the device linkage method provided by the present invention;

[0057] Figure 7 The seventh flowchart illustrating the device linkage method provided by the present invention;

[0058] Figure 8 This is one of the structural schematic diagrams of the equipment linkage device provided by the present invention;

[0059] Figure 9 This is the second schematic diagram of the structure of the equipment linkage device provided by the present invention;

[0060] Figure 10 The third schematic diagram of the equipment linkage device provided by the present invention;

[0061] Figure 11 The fourth schematic diagram of the equipment linkage device provided by the present invention;

[0062] Figure 12 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0063] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0064] With the rapid development of IoT technology, more and more smart devices are interconnecting. For example, in smart home applications, as smart home living becomes increasingly intelligent, smart home devices are no longer isolated entities, but rather form a cohesive whole within the home – a set of interconnected devices. Furthermore, with evolving user awareness and advancements in IoT technology, users desire smarter and more convenient ways to manage their devices. Therefore, centralized management and intelligent interconnection of smart home devices can lead to a more comfortable, safer, and energy-efficient home life.

[0065] Device linkage refers to the coordinated response of multiple devices triggered by pre-defined rules, enabling device linkage and intelligent control. The device linkage process is crucial for user experience, therefore, it is necessary to optimize the device linkage methods.

[0066] Currently, device linkage is controlled by changes in the state of IoT sensors or by changes in conditions such as time and weather. However, these methods are highly susceptible to changes in the external environment, and triggering conditions may lead to misjudgments and false alarms, thus reducing the accuracy of device linkage. Furthermore, the inability of users to actively choose triggers negatively impacts the user experience. In other words, existing technologies provide device linkage services to users through IoT sensors based on situational awareness technology or through inference linkage within the IoT system.

[0067] For example, smart home devices report status data. The protocol unit captures this data, converts it into parseable data, and determines whether trigger conditions are met to activate device linkage, thereby achieving intelligent linkage control of the devices (see CN113885348A - A Smart Home Device Intelligent Linkage Method). However, this method, which uses changes in the state of smart devices as trigger conditions, limits the overall device linkage to triggering conditions based on changes in the state of single or multiple devices. Furthermore, this device linkage mode cannot be actively selected by the user.

[0068] For example, by monitoring the environment of the application scenario in real time, including time conditions and / or weather changes, it can be determined whether the environmental parameters meet the triggering conditions. If the triggering conditions are met, the corresponding application scenario is triggered and the devices are linked. See CN111459043A - A method, device, and storage medium for triggering smart home application scenarios. However, this method uses changes in time and weather as triggering conditions. Due to the significant influence of external environmental factors, the triggering of device linkage may lead to misjudgments and false alarms. Moreover, users still cannot actively choose to trigger the system.

[0069] For example, QR code data writing technology can be used to trigger smart home appliance linkage. Users can configure corresponding linkage rules and generate corresponding QR codes. The linkage mechanism of smart devices is triggered by scanning the QR code, as detailed in CN107070759A - Method and System for Triggering Smart Home Appliance Linkage. However, while triggering preset device linkage rules by scanning QR codes can solve the problem of user-initiated linkage, scanning and parsing QR codes requires the support of an APP (Application Program). Changing phones requires downloading the APP again, which is not flexible enough.

[0070] For example, by storing the triggering conditions and execution instructions for linkage tasks on the server and gateway terminal, smart home services can continue even when the network is down, as detailed in CN114115069A - A Cloud-Local Combined Linkage Method and System. However, its local triggering is forcibly dependent on the matching local gateway; if the user does not have the corresponding gateway device, device linkage cannot be completed.

[0071] To address the above problems, the present invention proposes the following embodiments. Figure 1 This is one of the flowcharts illustrating the device linkage method provided by the present invention, such as... Figure 1 As shown, the device linkage method applied to the first server device includes:

[0072] Step 110: Receive the linkage trigger request sent by the second server device.

[0073] The generation method of the linkage trigger request includes at least one of the following:

[0074] The first client device stores the device linkage rules, and the linkage trigger request is generated by the second server device based on the first trigger request sent by the second client device. The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device.

[0075] The first server device stores the device linkage rules. The linkage trigger request is generated by the second server device based on the second trigger request sent by the first client device. The second trigger request is triggered based on the voice communication method between the first client device and the second server device.

[0076] Here, the first server device is the server for device linkage. This first server device is the main business platform that carries the device linkage function, that is, the linkage control platform for each device to be controlled.

[0077] Here, the second server device is a device that interacts with the first client device and the second client device, and it is used to forward the trigger requests from the first client device and the second client device to the first server device.

[0078] Here, the first client device is a user terminal device, which may include, but is not limited to, smartphones, tablets, etc. Furthermore, the first client device is a device that the user can carry with them.

[0079] Here, the second client device is a device bound to the second server device. This second client device is used by the user and is mainly used to trigger device linkage.

[0080] Here, the linkage trigger request is used to request the first server device to trigger device linkage. The first trigger request is used to request the first server device to trigger device linkage, but the first trigger request is not sent directly from the second client device to the first server device; instead, it is forwarded and processed by the second server device. The second trigger request is used to request the first server device to trigger device linkage, but the second trigger request is not sent directly from the first client device to the first server device; instead, it is forwarded and processed by the second server device.

[0081] Here, the device linkage rules refer to the linkage rules for each device to be controlled. For example, the device linkage rule is "turn on the living room light, set the room light brightness to 100, and turn on the air conditioner."

[0082] The first method for generating the linkage trigger request is as follows: For the second server device, before step 110 above, the second server device receives the first trigger request sent by the second client device and generates the linkage trigger request based on the first trigger request.

[0083] The first trigger request is generated as follows: For the second client device, the second client device receives the device linkage rule sent by the first client device, and generates the first trigger request based on the device linkage rule, so that the first trigger request indicates that there is a device linkage rule.

[0084] For the first client device, if it receives a rule retrieval command from the second client device, it will send the device linkage rules stored in the first client device to the second client device. In other words, when the first client and the second client are close together, i.e., when near-field communication is achieved, the second client device can retrieve the device linkage rules stored in the first client device, thereby realizing a local triggering device linkage method based on near-field communication.

[0085] The second method for generating the linkage trigger request is as follows: For the second server device, before step 110 above, the second server device receives the second trigger request sent by the first client device and generates the linkage trigger request based on the second trigger request.

[0086] For the first client device, if it is in a voice communication state with the second server device, the first client device obtains the second trigger request and sends it to the second server device. In other words, while the first client device and the second server device are in a voice communication state, the user can trigger the second trigger request on the first client device, thereby realizing a cloud-based device linkage method based on voice communication.

[0087] Understandably, by generating the two methods of linkage trigger requests described above, two triggering methods for device linkage can be achieved: near-field communication and voice communication. This allows users to actively choose the trigger, improving the user experience and enabling flexible and convenient device linkage. This provides a more comprehensive and complete triggering method, further enhancing the user experience. Moreover, both triggering methods are unaffected by the external environment, thus improving the accuracy of device linkage.

[0088] Step 120: Based on the linkage trigger request, determine the device linkage rules to be triggered.

[0089] Specifically, when the linkage trigger request is generated based on the first trigger request, the device linkage rules indicated by the linkage trigger request are obtained. When the linkage trigger request is generated based on the second trigger request, the device linkage rules stored by the first server device are obtained based on the linkage trigger request.

[0090] Step 130: Based on the device linkage rules, determine at least one device to be controlled and the control instructions corresponding to each device to be controlled.

[0091] Each of the devices to be controlled corresponds to at least one of the control commands.

[0092] Here, the device linkage rules include information about each device to be controlled, as well as the corresponding control command information for each device. For example, if the device linkage rule is "turn on the living room light, set the brightness of the room light to 100, and turn on the air conditioner," then the devices to be controlled include the living room light, the room light, and the air conditioner. The control command for the living room light is "turn on," the control command for the room light is "set the brightness to 100," and the control command for the air conditioner is "turn on."

[0093] Step 140: Send each of the control commands to the corresponding device to be controlled.

[0094] For example, if the device linkage rule is "turn on the living room light, set the brightness of the room light to 100, and turn on the air conditioner", then the control command corresponding to the living room light will be sent to the living room light, the control command corresponding to the room light will be sent to the room light, and the control command corresponding to the air conditioner will be sent to the air conditioner.

[0095] In one embodiment, prior to step 140 above, a connection is established between each device to be controlled and the first server device, that is, each device to be controlled is bound to the first server device, so that each device to be controlled and the first server device maintain a long connection, thereby ensuring the interaction between the two. Furthermore, the first server device can manage each device to be controlled under a username through the long connection.

[0096] The device linkage method provided in this embodiment of the invention involves a first server device receiving a linkage trigger request sent by a second server device. Based on the linkage trigger request, a device linkage rule to be triggered is determined. Then, based on the device linkage rule, at least one device to be controlled and corresponding control commands for each device to be controlled are determined. Each control command is then sent to its corresponding device to be controlled, thus achieving a device linkage triggering method that does not rely on a gateway device. Furthermore, the first generation method of the linkage trigger request is generated by the second server device based on a first trigger request sent by a second client device. The first trigger request is generated by the second client device based on the device linkage rule sent by the first client device. Therefore, when the first client and the second client are close together, i.e., when near-field communication is achieved, the second client device can obtain the device linkage rule stored by the first client device. This invention enables a local triggering method for device linkage based on near-field communication (NFC), allowing users to actively choose to trigger device linkage, thus improving user experience. This triggering method is unaffected by the external environment, thereby improving the accuracy of device linkage. Furthermore, the second method for generating linkage trigger requests involves a second server device generating a second trigger request sent by a first client device. This second trigger request is triggered by voice communication between the first client device and the second server device. While the first client device and the second server device are in voice communication, the user can trigger the second trigger request from the first client device, thus enabling a cloud-based triggering method for device linkage based on voice communication. This allows users to actively choose to trigger device linkage, further improving user experience. This triggering method is also unaffected by the external environment, thus improving the accuracy of device linkage. In addition, through these two methods of generating linkage trigger requests, two triggering methods for device linkage can be achieved: a dual triggering method using NFC and voice communication. This allows for flexible and convenient device linkage, providing a more comprehensive and complete triggering method, thereby improving user experience. In summary, this invention allows users to actively choose to trigger device linkage, improving user experience and increasing the accuracy of device linkage.

[0097] Based on any of the above embodiments, in this method, when the linkage trigger request is generated based on the second trigger request, step 120 includes:

[0098] Based on the rule identification information indicated by the linkage trigger request, the device linkage rules stored in the first server device are obtained.

[0099] Here, the rule identification information is used to uniquely identify the device linkage rule, for example, it is an ID.

[0100] Specifically, the linkage trigger request indicates rule identification information, so as to determine the device linkage rule corresponding to the rule identification information from at least one linkage rule stored in the first server device.

[0101] In one embodiment, the device linkage rule may include rule identification information to obtain the device linkage rule corresponding to the rule identification information. In another embodiment, the device linkage rule does not include rule identification information, so that the rule identification information is generated synchronously when the device linkage rule is stored in the first server device, and a mapping is formed.

[0102] The device linkage method provided in this embodiment of the invention accurately obtains the device linkage rules stored in the first server device based on the rule identification information of the linkage trigger request indication, thereby further improving the accuracy of device linkage.

[0103] Based on any of the above embodiments, the present invention also provides a device linkage method, which is applied to a second server device. Figure 2 This is a second schematic diagram of the device linkage method provided by the present invention, as shown below. Figure 2 As shown, the method includes:

[0104] Step 210: Receive a trigger request, the trigger request including a first trigger request sent by the second client device, or a second trigger request sent by the first client device.

[0105] The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device; the second trigger request is triggered based on the voice communication between the first client device and the second server device.

[0106] In the case where the trigger request includes a first trigger request, for the second client device, before step 210 above, the second client device receives the device linkage rule sent by the first client device, generates the first trigger request based on the device linkage rule, so that the first trigger request indicates that there is a device linkage rule.

[0107] For the first client device, if it receives a rule retrieval command from the second client device, it will send the device linkage rules stored in the first client device to the second client device. In other words, when the first client and the second client are close together, i.e., when near-field communication is achieved, the second client device can retrieve the device linkage rules stored in the first client device, thereby realizing a local triggering device linkage method based on near-field communication.

[0108] When the trigger request includes a second trigger request, if the first client device and the second server device are in a voice communication state, the first client device obtains the second trigger request and sends it to the second server device. In other words, when the first client device and the second server device are in a voice communication state, the user can trigger the second trigger request on the first client device, thereby realizing a cloud-based trigger device linkage method based on voice communication.

[0109] Step 220: Generate a linkage trigger request based on the trigger request.

[0110] In one embodiment, the trigger request is directly used as the linkage trigger request.

[0111] In another embodiment, the trigger request is further processed to obtain a linkage trigger request.

[0112] Step 230: Send the linkage trigger request to the first server device so that the first server device can determine the device linkage rules to be triggered based on the linkage trigger request, and realize device linkage control based on the device linkage rules;

[0113] For the first server device, after step 230 above, the first server device receives the linkage trigger request sent by the second server device, determines the device linkage rules to be triggered based on the linkage trigger request, determines at least one device to be controlled and the corresponding control instructions for each device to be controlled based on the device linkage rules, and sends each control instruction to the corresponding device to be controlled.

[0114] The device linkage method provided in this embodiment of the invention involves a second server device receiving a trigger request, generating a linkage trigger request based on the trigger request, and then sending the linkage trigger request to a first server device. The first server device then determines the device linkage rules to be triggered based on the linkage trigger request and implements device linkage control based on the device linkage rules, achieving a device linkage triggering method independent of a gateway device. The trigger request includes either a first trigger request sent by a second client device or a second trigger request sent by a first client device. The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device. Therefore, when the first client and the second client are close together, i.e., when near-field communication is achieved, the second client device can acquire the first client's... The device linkage rules stored on the terminal device enable a local triggering method for device linkage based on near-field communication (NFC). This allows users to actively choose to trigger device linkage, thus improving the user experience. Furthermore, this triggering method is unaffected by the external environment, thereby improving the accuracy of device linkage. The second trigger request is based on voice communication between the first client device and the second server device. While the first client device and the second server device are in voice communication, the user can trigger the second trigger request on the first client device, enabling a cloud-based triggering method for device linkage based on voice communication. This allows users to actively choose to trigger device linkage, further improving the user experience. This triggering method is also unaffected by the external environment, thus improving the accuracy of device linkage. In addition, through these two triggering methods for device linkage—near-field communication and voice communication—device linkage can be implemented flexibly and conveniently, achieving a more comprehensive and complete triggering method, thereby improving the user experience. In summary, this invention allows users to actively choose to trigger device linkage, improving the user experience and increasing the accuracy of device linkage.

[0115] Based on any of the above embodiments, the first client device is equipped with a super SIM card, the second client device is a near-field communication (NFC) scanning device, and the second server device is a server device belonging to an operator.

[0116] Accordingly, if the triggering request includes the first triggering request, step 210 above includes:

[0117] Receive the first trigger request sent by the second client device.

[0118] The first trigger request is generated by the second client device based on the device linkage rules sent by the super SIM card, and the second client device obtains the device linkage rules stored in the super SIM card through the NFC scanning function.

[0119] Here, the Super SIM card refers to the operator's SIM card. This Super SIM card is the hardware carrier for operator authentication of user identity, providing more comprehensive security for terminal-side network access authentication. Furthermore, the Super SIM card provides multiple application spaces for partners to develop third-party applications, serving as a high-security, high-quality container for various application scenarios. In one embodiment, the Super SIM card is based on an NFC-USIM card security chip, featuring high security and openness, empowering various industries through a "one-card solution."

[0120] Understandably, the ease of use of the Super SIM card makes device linkage operations safer and faster, greatly reducing the threshold and learning cost for users to use smart devices. This makes it easier to boost the sales of smart devices in ordinary households, while the convenient linkage capability further increases users' intrinsic motivation to purchase smart devices in sets, thereby increasing the overall market share of smart devices.

[0121] Here, the NFC (Near Field Communication) scanning device has NFC scanning capabilities, allowing it to obtain the device linkage rules stored in the Super SIM card. It's worth noting that NFC is an emerging technology; devices using NFC can exchange data when they are close to each other, offering advantages such as high speed and high security.

[0122] For the second client device, before receiving the first trigger request sent by the second client device, the second client device obtains the device linkage rules stored in the Super SIM card through the NFC scanning function.

[0123] For the first client device, before receiving the first trigger request sent by the second client device, if the first client device obtains the rule retrieval instruction sent by the second client device, the first client device sends the device linkage rules stored in the Super SIM card to the second client device.

[0124] In one embodiment, the Super SIM card provides NFC interface capabilities for third-party applications. The third-party applications work with the Super SIM card through the SWP (Single Wire Protocol) interface to realize the near-field sensing card swiping function, so that users can trigger device linkage by scanning the first client device with the second client device.

[0125] For example, a third-party application will be pre-loaded in the Super SIM card. When the second client device scans the Super SIM card, the second client device obtains the device linkage rules and starts sending the first trigger request to the second server device.

[0126] In one embodiment, the second server device includes an operator's TSM (Trusted Service Manager) platform, enabling the second client device to send a first trigger request to the TSM platform. The TSM platform combines credibility and openness; it is an open platform for third-party applications and the foundation for NFC card-swiping applications. After applying for a third-party application on the TSM platform, remote invocation of the third-party platform by the TSM platform is possible. In this invention, after receiving the first trigger request, the TSM platform triggers the linked behavior by invoking the first server device.

[0127] For ease of understanding, a specific embodiment is described here. For example... Figure 3 As shown, the device linkage method includes:

[0128] Step 310: The second client device scans the Super SIM card.

[0129] Step 320: The second client device obtains the device linkage rules stored locally on the Super SIM card.

[0130] Step 330: The second client device generates a first trigger request based on the device linkage rules and sends the first trigger request to the second server device.

[0131] Step 340: The second server device generates a linkage trigger request based on the first trigger request and sends the linkage trigger request to the first server device.

[0132] The device linkage method provided in this invention involves a first trigger request generated by a second client device based on device linkage rules sent by a Super SIM card. The second client device obtains the device linkage rules stored in the Super SIM card via NFC scanning. When the first and second clients are close together (i.e., near-field communication is established), the second client device can obtain the device linkage rules stored in the Super SIM card, thereby achieving a local triggering device linkage method based on near-field communication. This allows users to actively choose to trigger device linkage, improving user experience. Furthermore, this triggering method is unaffected by the external environment, thus improving the accuracy of device linkage. Simultaneously, the Super SIM card's one-card solution provides the basic capabilities for device linkage. Therefore, in scenarios where users do not have third-party apps installed, or when changing phones, device linkage capabilities can be directly migrated using the Super SIM card, providing users with a more convenient device linkage method and further enhancing user experience. In other words, this invention allows device linkage functionality to be used without a specific app. Since the device linkage rules are stored in the Super SIM card's file system, once the device linkage rules are set, no specific app is required, thereby improving the flexibility of device linkage. Furthermore, since the device linkage rules are stored in the Super SIM card and do not change with the primary client device, the same device linkage function can be used immediately and completely when the SIM card is installed in a new primary client device. This ensures that changing the primary client device does not affect the device linkage function, thereby further improving the user experience. In addition, the device linkage triggering method can still be used when the primary client device has no network. Moreover, the Super SIM card's authentication capabilities can be used to verify the user's legitimacy, thereby improving the security of device linkage.

[0133] Based on any of the above embodiments, the second server-side device is a server-side device belonging to the operator. Accordingly, when the triggering request includes the second triggering request, step 210 includes:

[0134] During the voice communication between the first client device and the second server device, the second trigger request sent by the first client device is received. The second trigger request is triggered based on the quick trigger method of the dial pad.

[0135] It should be noted that the voice communication between the first client device and the second server device is based on the operator's voice service. Voice service is a traditional value-added service provided by operators.

[0136] For example, the first client device establishes voice telephone communication with the second server device by dialing a pre-approved customer service hotline, so that the user can generate a second trigger request through the shortcut of the dial pad keys on the first client device, and send the second trigger request to the second server device.

[0137] In one embodiment, the second server device includes a voice platform, to which the second trigger request is sent.

[0138] Furthermore, the second server device first verifies the user's legitimacy. If the user is legitimate, it receives the second trigger request sent by the first client device. For example, the second server device verifies the legitimacy of the first client device with which it is communicating via voice.

[0139] For the first client device, before receiving the second trigger request sent by the first client device, it obtains the key shortcut commands on the dial pad; and generates the second trigger request based on the key shortcut commands.

[0140] For ease of understanding, a specific embodiment is described here. For example... Figure 4 As shown, the device linkage method includes:

[0141] Step 410: The first client device dials a landline phone number to establish a voice communication connection with the second server device.

[0142] Step 420: The first client device sends a second trigger request to the second server device.

[0143] Step 430: The second server device generates a linkage trigger request based on the second trigger request and sends the linkage trigger request to the first server device.

[0144] Step 440: The first server device searches for the device linkage rules stored in the first server device based on the linkage trigger request.

[0145] The device linkage method provided in this invention receives a second trigger request from the first client device during voice communication between the first client device and the second server device. This second trigger request is triggered via a dial pad shortcut. While the first client device and the second server device are in voice communication, the user can trigger the second trigger request from the first client device, thus achieving cloud-based device linkage based on voice communication. This allows the user to actively choose to trigger device linkage, improving user experience. Furthermore, this triggering method is unaffected by external environmental factors, improving the accuracy of device linkage. Simultaneously, in scenarios where the user has not installed a third-party app or has changed phones, a voice call can be made directly, providing a more convenient device linkage method and further enhancing user experience. In other words, this invention allows device linkage functionality without a specific app. Since the device linkage rules are stored in the first server device, once the rules are set, no specific app is required, increasing the flexibility of device linkage. Moreover, because the device linkage rules are stored in the first server device and do not change with changes to the first client device, changing the first client device does not affect the device linkage function, further enhancing user experience. In addition, the device linkage triggering method can also be used when the first client device has no network.

[0146] Based on any of the above embodiments, the present invention also provides a device linkage method, which is applied to a first client device. Figure 5 The fifth flowchart illustrates the device linkage method provided by this invention. Figure 5 As shown, the method includes:

[0147] Step 510: If a rule retrieval instruction is received from the second client device, the device linkage rules stored in the first client device are sent to the second client device, so that the second client device generates a first trigger request based on the device linkage rules and sends the first trigger request to the second server device.

[0148] For the second client device, before step 510 above, the second client device sends a rule retrieval instruction to the first client device.

[0149] Step 520: If the first client device and the second server device are in a voice communication state, obtain the second trigger request and send the second trigger request to the second server device so that the second server device can generate a linkage trigger request based on the second trigger request and send the linkage trigger request to the first server device.

[0150] Here, voice communication between the first client device and the second server device can be implemented based on the operator's voice service or other voice communication methods. This second trigger request can be initiated by the user on the first client device.

[0151] Understandably, if the user is in a local scenario, they can use the first device linkage triggering method related to step 510; if the user is not in a local scenario, they can use the second device linkage triggering method related to step 520, which is a cloud-based device linkage triggering method. For example, in a local environment, the device linkage request can be forwarded by the operator's TSM platform through NFC near-field scanning of the Super SIM card; in a cloud environment, the device linkage request can be forwarded by the voice platform through making a voice call.

[0152] The device linkage method provided in this embodiment of the invention, if a rule acquisition instruction is received from a second client device, sends the device linkage rules stored in the first client device to the second client device; if the first client device and the second server device are in a voice communication state, a second trigger request is acquired and sent to the second server device, realizing a device linkage triggering method that does not rely on a gateway device; and the second client device generates a first trigger request based on the device linkage rules, so that when the first client and the second client are close to each other, that is, when near-field communication is achieved, the second client device can acquire the device linkage rules stored in the first client device, thereby realizing near-field communication-based linkage. The invention employs a local triggering method for device linkage, allowing users to actively choose to trigger device linkage, thus enhancing the user experience. This triggering method is unaffected by external environmental factors, improving the accuracy of device linkage. Furthermore, the first client device receives a second trigger request and sends it to a second server device, placing the first client device and the second server device in a voice communication state. The user can then trigger the second trigger request from the first client device, enabling a cloud-based device linkage triggering method based on voice communication. This allows users to actively choose to trigger device linkage, further enhancing the user experience. This triggering method is also unaffected by external environmental factors, improving the accuracy of device linkage. Moreover, by utilizing these two triggering methods—near-field communication and voice communication—device linkage can be implemented flexibly and conveniently, achieving a more comprehensive and complete triggering approach, thereby improving the user experience. In summary, this invention allows users to actively choose to trigger device linkage, enhancing the user experience and improving the accuracy of device linkage.

[0153] Based on any of the above embodiments, the first client device is equipped with a super SIM card, the second client device is a near-field communication (NFC) scanning device, and the second server device is a server device belonging to an operator. Accordingly, step 510 includes:

[0154] The device linkage rules stored in the Super SIM card are sent to the second client device.

[0155] The rule acquisition instruction is triggered by the NFC scanning function of the second client device.

[0156] For the second client device, the NFC scanning function is used to obtain the device linkage rules stored in the Super SIM card.

[0157] The device linkage method provided in this invention sends the device linkage rules stored in the Super SIM card to a second client device. The rule acquisition instruction is triggered by the NFC scanning function of the second client device. When the first and second clients are close together (i.e., when near-field communication is established), the second client device can acquire the device linkage rules stored in the Super SIM card, thereby realizing a local triggering device linkage method based on near-field communication. This allows users to actively choose to trigger device linkage, improving the user experience. Furthermore, this triggering method is unaffected by the external environment, thus improving the accuracy of device linkage. Simultaneously, utilizing the Super SIM card's one-card solution provides the basic capabilities for device linkage. Therefore, in scenarios where users do not have third-party apps installed, or when changing phones, the device linkage capability can be directly migrated using the Super SIM card, providing users with a more convenient device linkage method and further enhancing the user experience. In other words, this invention allows the device linkage function to be used without a specific app. Since the device linkage rules are stored in the Super SIM card's file system, once the device linkage rules are set, no specific app is required, thereby improving the flexibility of device linkage. Furthermore, since the device linkage rules are stored in the Super SIM card and do not change with the primary client device, the same device linkage function can be used immediately and completely when the SIM card is installed in a new primary client device. This ensures that changing the primary client device does not affect the device linkage function, thereby further improving the user experience. In addition, the device linkage triggering method can still be used when the primary client device has no network. Moreover, the Super SIM card's authentication capabilities can be used to verify the user's legitimacy, thereby improving the security of device linkage.

[0158] Based on any of the above embodiments, the second server-side device is a server-side device belonging to the operator. Accordingly, in step 520 above, obtaining the second trigger request includes:

[0159] Get shortcut commands for key presses on the dial pad;

[0160] A second trigger request is generated based on the key shortcut command.

[0161] It should be noted that the voice communication between the first client device and the second server device is based on the operator's voice service. Voice service is a traditional value-added service provided by operators.

[0162] For example, the first client device establishes voice telephone communication with the second server device by dialing a pre-approved customer service hotline, so that the user can generate a second trigger request through shortcut commands on the dial pad of the first client device.

[0163] The device linkage method provided in this invention obtains key shortcut commands on the dial pad, generates a second trigger request based on the key shortcut commands, and thus, when the first client device and the second server device are in voice communication, the user can trigger the second trigger request on the first client device. This enables cloud-based device linkage triggered by voice communication, allowing the user to actively choose to trigger device linkage, thereby improving the user experience. Furthermore, this triggering method is unaffected by the external environment, thus improving the accuracy of device linkage. Simultaneously, in scenarios where the user has not installed a third-party app, or when changing phones, a voice call can be made directly, providing a more convenient device linkage method and further enhancing the user experience. In other words, this invention allows the device linkage function to be used without a specific app. Since the device linkage rules are stored in the first server device, once the device linkage rules are set, no specific app is required, thus improving the flexibility of device linkage. Moreover, because the device linkage rules are stored in the first server device and do not change with changes in the first client device, changing the first client device does not affect the device linkage function, further enhancing the user experience. Additionally, the device linkage triggering method can also be used when the first client device has no network connection.

[0164] Based on any of the above embodiments, prior to step 510, the method further includes:

[0165] Obtain rule editing instructions, and generate the device linkage rules based on the rule editing instructions;

[0166] The device linkage rules are stored in the first client device and in the first server device.

[0167] Here, the rule editing command is triggered by the user. For example, the user uses a third-party proprietary business app to edit the device linkage rules, thereby causing the first client device to generate a rule editing command.

[0168] Furthermore, the device linkage rules are stored in the Super SIM card deployed on the first client device. This leverages the multi-application space capability provided by the Super SIM card to store user-defined device linkage rules.

[0169] In some embodiments, device linkage rules include two main elements: a unique user identifier (userId) and device linkage actions.

[0170] In one embodiment, the user unique identifier userId is a unique identifier for the user. 3GPP (3rd Generation Partnership Project) defines a general user authentication mechanism GBA (General Bootstrapping Architecture) to provide device identifiers to third parties in a consistent manner. Therefore, userId can be provided directly through the identity authentication service of the Super SIM card.

[0171] In one embodiment, device linkage actions are a collection of specific device linkage behaviors, which include the device unique identifier deviceId, device control instructions controlParameter, such as switch, brightness, mode, etc., and device control values ​​controlValue, such as on / off, brightness value 0-100, energy saving mode / auto mode, etc.

[0172] In one embodiment, while obtaining the rule editing instruction, a unique rule identifier (ruleId) corresponding to the device linkage rule is generated.

[0173] For example, the device linkage rules are as follows:

[0174]

[0175]

[0176] The device linkage method provided in this invention generates device linkage rules based on rule editing instructions, allowing users to customize these rules and thus improve the personalization of device linkage, thereby enhancing the user experience. Furthermore, storing the device linkage rules on both a first client device and a first server device enables two device linkage triggering methods: near-field communication and voice communication. This allows for flexible and convenient device linkage, providing a more comprehensive and complete triggering mechanism, further improving the user experience.

[0177] Based on any of the above embodiments, the present invention also provides a device linkage method, which is applied to a second client device. Figure 6 This is the sixth flowchart illustrating the device linkage method provided by the present invention, as shown below. Figure 6 As shown, the method includes:

[0178] Step 610: Receive the device linkage rules sent by the first client device.

[0179] For the first client device, if it receives a rule retrieval instruction from the second client device before step 610 above, it will send the device linkage rules stored in the first client device to the second client device.

[0180] Step 620: Based on the device linkage rule, generate a first trigger request so that the first trigger request indicates the existence of the device linkage rule.

[0181] Step 630: Send the first trigger request to the second server device, so that the second server device generates a linkage trigger request based on the first trigger request, and sends the linkage trigger request to the first server device.

[0182] Specifically, the second server device generates a linkage trigger request based on the first trigger request, so that the linkage trigger request indicates that the device has linkage rules.

[0183] The device linkage method provided in this embodiment of the invention receives device linkage rules sent by a first client device, generates a first trigger request based on the device linkage rules, so that the first trigger request indicates the existence of device linkage rules, and sends the first trigger request to a second server device, thereby realizing a device linkage triggering method that does not rely on a gateway device. The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device. Thus, when the first client and the second client are close to each other, that is, when near-field communication is achieved, the second client device can obtain the device linkage rules stored by the first client device, thereby realizing a local triggering device linkage method based on near-field communication. This allows the user to actively choose to trigger device linkage, thereby improving the user experience. Moreover, this triggering method is not affected by the external environment, thereby improving the accuracy of device linkage.

[0184] Based on any of the above embodiments, the first client device is equipped with a super SIM card, the second client device is a near-field communication (NFC) scanning device, and the second server device is a server device belonging to an operator. Accordingly, step 610 includes:

[0185] The device linkage rules stored in the Super SIM card are obtained through the NFC scanning function.

[0186] For the Super SIM card, if it receives a rule retrieval instruction from the second client device, it sends the device linkage rules stored in the Super SIM card to the second client device. In one embodiment, the device linkage rules are stored in the application space of the Super SIM card.

[0187] The device linkage method provided in this invention uses NFC scanning to obtain device linkage rules stored in a Super SIM card. When a first client and a second client are close together (i.e., when near-field communication is established), the second client device can obtain these rules and implement a local triggering method for device linkage based on near-field communication. This allows users to actively choose to trigger device linkage, improving user experience. Furthermore, this triggering method is unaffected by external environmental factors, thus improving the accuracy of device linkage. Simultaneously, the Super SIM card's single-card solution provides the foundation for device linkage capabilities. In scenarios where users do not have third-party apps installed or when changing phones, device linkage capabilities can be directly migrated using the Super SIM card, providing users with a more convenient device linkage method and further enhancing user experience. In other words, this invention allows device linkage functionality to be used without a specific app. Since the device linkage rules are stored in the Super SIM card's file system, once the rules are set, no specific app is required, thus improving the flexibility of device linkage. Furthermore, since the device linkage rules are stored in the Super SIM card and do not change with the primary client device, the same device linkage function can be used immediately and completely when the SIM card is installed in a new primary client device. This ensures that changing the primary client device does not affect the device linkage function, thereby further improving the user experience. In addition, the device linkage triggering method can still be used when the primary client device has no network. Moreover, the Super SIM card's authentication capabilities can be used to verify the user's legitimacy, thereby improving the security of device linkage.

[0188] To facilitate understanding of the above embodiments, a specific embodiment will be described here. For example... Figure 7 As shown, the device linkage method includes:

[0189] Step 710: Edit the device linkage rules.

[0190] Step 720: The storage device linkage rules are transmitted to the super SIM card installed in the first client device, and the storage device linkage rules are synchronized to the first server device.

[0191] If it is near-field communication, proceed to step 730; otherwise, proceed to step 750.

[0192] Step 730: The second client device scans the Super SIM card.

[0193] Step 740: The second client device sends a first trigger request to the second server device.

[0194] Step 750: The first client device dials a landline voice call.

[0195] Step 760: The first client device sends a second trigger request to the second server device.

[0196] Step 770: The second server device sends a linkage trigger request to the first server device.

[0197] Step 780: The first server device sends control commands to each device to be controlled.

[0198] Based on the above embodiments, this invention proposes a device linkage triggering method that combines cloud and local access. Furthermore, it authenticates user legitimacy through the identity authentication capability of the Super SIM card, stores device linkage rules through the file read / write capability of the SIM card, triggers preset device linkage rules through the NFC capability of the Super SIM card, and, in scenarios where NFC is unavailable, triggers cloud scenarios through the SIM card's ability to make voice calls. This comprehensively solves the problem of cloud-local linkage, enabling users to conveniently trigger device linkage whether in the cloud or locally.

[0199] The device linkage system provided by this invention is described below. The device linkage system described below can be referred to in correspondence with the device linkage method described above. This device linkage system includes: a first server device, a second server device, a first client device, and a second client device. When the processor in the first server device executes a program, it implements any of the device linkage methods described above for the first server device. When the processor in the second server device executes a program, it implements any of the device linkage methods described above for the second server device. When the processor in the first client device executes a program, it implements any of the device linkage methods described above for the first client device. When the processor in the second client device executes a program, it implements any of the device linkage methods described above for the second client device.

[0200] The device linkage device provided by the present invention is described below. The device linkage device described below and the device linkage method described above can be referred to in correspondence.

[0201] Figure 8 This is one of the structural schematic diagrams of the equipment linkage device provided by the present invention, such as... Figure 8 As shown, the device linkage device deployed on the first server-side device includes:

[0202] The first receiving module 810 is used to receive the linkage trigger request sent by the second server device;

[0203] The first determining module 820 is used to determine the device linkage rules to be triggered based on the linkage triggering request;

[0204] The second determining module 830 is used to determine at least one device to be controlled and control instructions corresponding to each device to be controlled based on the device linkage rules, wherein any device to be controlled corresponds to at least one control instruction.

[0205] The first sending module 840 is used to send each of the control commands to the corresponding device to be controlled;

[0206] The generation method of the linkage trigger request includes at least one of the following:

[0207] The first client device stores the device linkage rules, and the linkage trigger request is generated by the second server device based on the first trigger request sent by the second client device. The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device.

[0208] The first server device stores the device linkage rules. The linkage trigger request is generated by the second server device based on the second trigger request sent by the first client device. The second trigger request is triggered based on the voice communication method between the first client device and the second server device.

[0209] Figure 9 This is a second structural schematic diagram of the equipment linkage device provided by the present invention, as shown below. Figure 9 As shown, the device linkage device deployed on the second server-side device includes:

[0210] The second receiving module 910 is used to receive a trigger request, the trigger request including a first trigger request sent by the second client device, or a second trigger request sent by the first client device;

[0211] The first generation module 920 is used to generate a linkage trigger request based on the trigger request;

[0212] The second sending module 930 is used to send the linkage trigger request to the first server device, so that the first server device can determine the device linkage rule to be triggered based on the linkage trigger request, and realize device linkage control based on the device linkage rule.

[0213] The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device;

[0214] The second trigger request is triggered based on the voice communication method between the first client device and the second server device.

[0215] Figure 10This is the third structural schematic diagram of the equipment linkage device provided by the present invention, as shown below. Figure 10 As shown, the device linkage device deployed on the first client device includes:

[0216] The third sending module 1010 is used to send the device linkage rules stored in the first client device to the second client device if a rule acquisition instruction is received from the second client device, so that the second client device generates a first trigger request based on the device linkage rules and sends the first trigger request to the second server device.

[0217] The fourth sending module 1020 is used to obtain a second trigger request if the first client device and the second server device are in a voice communication state, and send the second trigger request to the second server device so that the second server device can generate a linkage trigger request based on the second trigger request and send the linkage trigger request to the first server device.

[0218] Figure 11 The fourth schematic diagram of the device linkage device provided by the present invention is shown below. Figure 11 As shown, the device linkage device deployed on the second client device includes:

[0219] The third receiving module 1110 is used to receive the device linkage rules sent by the first client device;

[0220] The second generation module 1120 is used to generate a first trigger request based on the device linkage rule, so that the first trigger request indicates the device linkage rule;

[0221] The fifth sending module 1130 is used to send the first trigger request to the second server device, so that the second server device generates a linkage trigger request based on the first trigger request and sends the linkage trigger request to the first server device.

[0222] Figure 12 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 12As shown, the electronic device may include: a processor 1210, a communications interface 1220, a memory 1230, and a communications bus 1240, wherein the processor 1210, the communications interface 1220, and the memory 1230 communicate with each other through the communications bus 1240. The processor 1210 can call logic instructions in the memory 1230 to execute a device linkage method applied to a first server device. The method includes: receiving a linkage trigger request sent by a second server device; determining a device linkage rule to be triggered based on the linkage trigger request; determining at least one device to be controlled and control instructions corresponding to each device to be controlled, with each device to be controlled corresponding to at least one control instruction; and sending each control instruction to its corresponding device to be controlled. The linkage trigger request is generated in at least one of the following ways: a first client device stores the device linkage rule, and the linkage trigger request is generated by the second server device based on a first trigger request sent by the second client device, wherein the first trigger request is generated by the second client device based on the device linkage rule sent by the first client device; or the first server device stores the device linkage rule, and the linkage trigger request is generated by the second server device based on a second trigger request sent by the first client device, wherein the second trigger request is triggered based on a voice communication method between the first client device and the second server device. Alternatively, a device linkage method applied to a second server device can be executed. This method includes: receiving a trigger request, the trigger request including a first trigger request sent by a second client device, or a second trigger request sent by a first client device; generating a linkage trigger request based on the trigger request; and sending the linkage trigger request to a first server device, so that the first server device can determine the device linkage rules to be triggered based on the linkage trigger request, and implement device linkage control based on the device linkage rules; wherein the first trigger request is generated by the second client device based on the device linkage rules sent by the first client device; and the second trigger request is triggered based on a voice communication method between the first client device and the second server device.Alternatively, a device linkage method applied to a first client device can be executed. This method includes: if a rule retrieval instruction is received from a second client device, sending the device linkage rules stored in the first client device to the second client device, so that the second client device generates a first trigger request based on the device linkage rules, and sends the first trigger request to a second server device; if the first client device and the second server device are in a voice communication state, acquiring a second trigger request, and sending the second trigger request to the second server device, so that the second server device generates a linkage trigger request based on the second trigger request, and sends the linkage trigger request to the first server device. Alternatively, a device linkage method applied to a second client device can be executed. This method includes: receiving a device linkage rule sent by a first client device; generating a first trigger request based on the device linkage rule, so that the first trigger request indicates the device linkage rule; sending the first trigger request to the second server device, so that the second server device generates a linkage trigger request based on the first trigger request, and sends the linkage trigger request to the first server device.

[0223] Furthermore, the logical instructions in the aforementioned memory 1230 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, essentially, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0224] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program implements the device linkage method applied to a first server device provided by the above methods. The method includes: receiving a linkage trigger request sent by a second server device; determining a device linkage rule to be triggered based on the linkage trigger request; determining at least one device to be controlled and control instructions corresponding to each device to be controlled based on the device linkage rule, wherein each device to be controlled corresponds to at least one control instruction; and sending each control instruction to the corresponding device to be controlled. The generation method of the linkage trigger request includes at least one of the following: a first client device stores the device linkage rule, and the linkage trigger request is generated by the second server device based on a first trigger request sent by the second client device, wherein the first trigger request is generated by the second client device based on the device linkage rule sent by the first client device; or the first server device stores the device linkage rule, and the linkage trigger request is generated by the second server device based on a second trigger request sent by the first client device, wherein the second trigger request is triggered based on a voice communication method between the first client device and the second server device. Alternatively, when a computer program is executed by a processor, it implements the device linkage method for a second server device provided by the above methods. This method includes: receiving a trigger request, the trigger request including a first trigger request sent by a second client device, or a second trigger request sent by a first client device; generating a linkage trigger request based on the trigger request; and sending the linkage trigger request to a first server device, so that the first server device can determine a device linkage rule to be triggered based on the linkage trigger request, and implement device linkage control based on the device linkage rule; wherein the first trigger request is generated by the second client device based on the device linkage rule sent by the first client device; and the second trigger request is triggered based on a voice communication method between the first client device and the second server device. Alternatively, when a computer program is executed by a processor, it implements the device linkage method applied to a first client device provided by the above methods. This method includes: if a rule retrieval instruction is received from a second client device, sending the device linkage rules stored in the first client device to the second client device, so that the second client device generates a first trigger request based on the device linkage rules, and sends the first trigger request to a second server device; if the first client device and the second server device are in a voice communication state, acquiring a second trigger request, and sending the second trigger request to the second server device, so that the second server device generates a linkage trigger request based on the second trigger request, and sends the linkage trigger request to the first server device.Alternatively, when a computer program is executed by a processor, it implements a device linkage method for a second client device provided by the above methods, the method comprising: receiving a device linkage rule sent by a first client device; generating a first trigger request based on the device linkage rule, such that the first trigger request indicates the device linkage rule; and sending the first trigger request to a second server device, such that the second server device generates a linkage trigger request based on the first trigger request, and sends the linkage trigger request to the first server device.

[0225] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0226] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0227] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for linking equipment, characterized in that, Applied to a first server device, the method includes: Receive the linkage trigger request sent by the second server device; Based on the linkage trigger request, determine the device linkage rules to be triggered; Based on the device linkage rules, at least one device to be controlled is determined, and control instructions corresponding to each device to be controlled are determined. Each device to be controlled corresponds to at least one control instruction. Each of the aforementioned control commands is sent to the corresponding device to be controlled; The generation method of the linkage trigger request includes at least one of the following: The first client device stores the device linkage rules, and the linkage trigger request is generated by the second server device based on the first trigger request sent by the second client device. The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device. The first server device stores the device linkage rules, and the linkage trigger request is generated by the second server device based on the second trigger request sent by the first client device. The second trigger request is triggered based on the voice communication method between the first client device and the second server device. The first client device is a user terminal device.

2. A device linkage method, characterized by, Applied to a second server device, the method includes: Receive a trigger request, the trigger request including a first trigger request sent by a second client device, or a second trigger request sent by a first client device; the first client device is a user terminal device; Based on the aforementioned trigger request, a linkage trigger request is generated; The linkage trigger request is sent to the first server device, so that the first server device can determine the device linkage rules to be triggered based on the linkage trigger request, and realize device linkage control based on the device linkage rules; The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device; The second trigger request is triggered based on the voice communication method between the first client device and the second server device.

3. The apparatus linkage method according to claim 2, characterized by, The first client device is equipped with a Super SIM card, the second client device is a near-field communication (NFC) scanning device, and the second server device is a server device belonging to an operator. When the trigger request includes the first trigger request, receiving the trigger request includes: Receive the first trigger request sent by the second client device; The first trigger request is generated by the second client device based on the device linkage rules sent by the super SIM card, and the second client device obtains the device linkage rules stored in the super SIM card through the NFC scanning function.

4. An apparatus linkage method characterized by, The method is applied to a first client device, which is a user terminal device; the method includes: If a rule retrieval instruction is received from the second client device, the device linkage rules stored in the first client device are sent to the second client device, so that the second client device generates a first trigger request based on the device linkage rules, and sends the first trigger request to the second server device; If the first client device and the second server device are in a voice communication state, the second trigger request is obtained and sent to the second server device so that the second server device can generate a linkage trigger request based on the second trigger request and send the linkage trigger request to the first server device.

5. The apparatus linkage method according to claim 4, characterized by, The second server-side device is a server-side device belonging to the operator; The process of obtaining the second trigger request includes: Get shortcut commands for key presses on the dial pad; A second trigger request is generated based on the key shortcut command.

6. The apparatus linkage method according to claim 4, wherein, If a rule retrieval instruction is received from the second client device, the device linkage rules stored in the first client device are sent to the second client device. Prior to this, the process also includes: Obtain rule editing instructions, and generate the device linkage rules based on the rule editing instructions; The device linkage rules are stored in the first client device and in the first server device.

7. An apparatus linkage method characterized by comprising: Applied to a second client device, the method includes: Receive device linkage rules sent by a first client device; the first client device is a user terminal device. Based on the device linkage rules, a first trigger request is generated so that the first trigger request indicates the device linkage rules; The first trigger request is sent to the second server device, so that the second server device generates a linkage trigger request based on the first trigger request, and sends the linkage trigger request to the first server device.

8. The apparatus linkage method according to claim 7, wherein, The first client device is equipped with a Super SIM card, the second client device is a near-field communication (NFC) scanning device, and the second server device is a server device belonging to an operator. The device linkage rules received from the first client device include: The device linkage rules stored in the Super SIM card are obtained through the NFC scanning function.

9. An apparatus linkage, characterized by Deployed on the first server-side device, the device includes: The first receiving module is used to receive the linkage trigger request sent by the second server device; The first determining module is used to determine the device linkage rules to be triggered based on the linkage triggering request; The second determining module is used to determine at least one device to be controlled and control instructions corresponding to each device to be controlled based on the device linkage rules, wherein any device to be controlled corresponds to at least one control instruction. The first sending module is used to send each of the control commands to the corresponding device to be controlled; The generation method of the linkage trigger request includes at least one of the following: The first client device stores the device linkage rules, and the linkage trigger request is generated by the second server device based on the first trigger request sent by the second client device. The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device. The first server device stores the device linkage rules, and the linkage trigger request is generated by the second server device based on the second trigger request sent by the first client device. The second trigger request is triggered based on the voice communication method between the first client device and the second server device. The first client device is a user terminal device.

10. An apparatus linkage, characterized by Deployed on a second server device, the device includes: The second receiving module is used to receive trigger requests, the trigger requests including a first trigger request sent by a second client device, or a second trigger request sent by a first client device; the first client device is a user terminal device; The first generation module is used to generate a linkage trigger request based on the trigger request; The second sending module is used to send the linkage trigger request to the first server device, so that the first server device can determine the device linkage rules to be triggered based on the linkage trigger request, and realize device linkage control based on the device linkage rules; The first trigger request is generated by the second client device based on the device linkage rules sent by the first client device; The second trigger request is triggered based on the voice communication method between the first client device and the second server device.

11. An apparatus linkage, characterized by Deployed on a first client device, wherein the first client device is a user terminal device; the device includes: The third sending module is used to send the device linkage rules stored in the first client device to the second client device if a rule acquisition instruction is received from the second client device, so that the second client device generates a first trigger request based on the device linkage rules and sends the first trigger request to the second server device; The fourth sending module is used to obtain a second trigger request if the first client device and the second server device are in a voice communication state, and send the second trigger request to the second server device so that the second server device can generate a linkage trigger request based on the second trigger request and send the linkage trigger request to the first server device.

12. An apparatus linkage, characterized by Deployed on a second client device, the device includes: The third receiving module is used to receive device linkage rules sent by the first client device; the first client device is a user terminal device. The second generation module is used to generate a first trigger request based on the device linkage rule, so that the first trigger request indicates the device linkage rule; The fifth sending module is used to send the first trigger request to the second server device, so that the second server device generates a linkage trigger request based on the first trigger request and sends the linkage trigger request to the first server device.

13. An apparatus linkage system characterized by, include: First server device, second server device, first client device, second client device; When the processor in the first server device executes the program, it implements the device linkage method as described in claim 1. When the processor in the second server device executes the program, it implements the device linkage method as described in claim 2 or 3; When the processor in the first client device executes the program, it implements the device linkage method as described in any one of claims 4 to 6; When the processor in the second client device executes the program, it implements the device linkage method as described in claim 7 or 8.

14. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the device linkage method as described in any one of claims 1 to 8.

15. A non-transitory computer-readable storage medium having stored thereon a computer program, characterized in that, When the computer program is executed by the processor, it implements the device linkage method as described in any one of claims 1 to 8.

Images