A device communication method, apparatus and electronic device

Abstract

An embodiment of the present application provides a device communication method, apparatus, and electronic device, which relate to the field of communication technologies. The method is applied to a client in a device communication system, and the communication system further includes: a communication platform and at least one communication device. The client displays the platform page of the communication platform, and when a click operation on a target device is detected, sends a page request for the target device to the communication platform, so that the communication platform feeds back a page file sent by the target device to the client; receives the page file and executes the page file to obtain the device page of the target device; calls the authentication function of the platform page through the device page; sends a parameter request for the target device carrying first authentication data to the communication platform through the device page; receives the device parameters and jumps to the device page displaying the device parameters. Compared with the prior art, by applying the solution provided by the embodiment of the present application, communication between the client and a device without a fixed IP can be realized.

Description

Technical Field

[0001] The present application relates to the field of communication technologies, and particularly to a device communication method, apparatus, and electronic device. Background Art

[0002] With the development of communication technologies, more and more electronic devices support remote operations, so that users can connect to the electronic device through a client installed on other devices and communicate with the electronic device.

[0003] In related technologies, when remotely operating an electronic device, a user can connect to the electronic device by entering the IP (Internet Protocol) of the electronic device in a client installed on another electronic device, thereby achieving communication with the electronic device. Further, remotely operate the electronic device on the operation interface of the client.

[0004] However, in the above-mentioned related technologies, for an electronic device without a fixed IP, the user cannot use the above method to achieve communication between the client and the electronic device, and thus cannot remotely operate the electronic device. Summary of the Invention

[0005] The purpose of the embodiments of the present application is to provide a device communication method, apparatus, and electronic device to achieve communication between a client and a device without a fixed IP. The specific technical solutions are as follows:

[0006] In a first aspect, the embodiments of the present application provide a device communication method, which is applied to a client in a device communication system. The system further includes: a communication platform and at least one communication device, and the at least one communication device is pre-registered in the communication platform; the method includes:

[0007] Display a platform page of the communication platform, and when a click operation on a target device is detected, send a page request about the target device to the communication platform, so that the communication platform, based on the registration information of the at least one communication device, sends the page request to the target device and feeds back a page file sent by the target device to the client; wherein the target device is any one of the at least one communication device;

[0008] Receive the page file and execute the page file to obtain a device page of the target device;

[0009] Call an authentication function of the platform page through the device page, so that the platform page generates first authentication data based on the authentication function and feeds back the first authentication data to the device page;

[0010] Send a parameter request for the target device carrying the first authentication data to the communication platform through the device page, so that when the communication platform successfully verifies the first authentication data, it sends the parameter request to the target device based on the registration information and feeds back the device parameters sent by the target device to the client;

[0011] Receive the device parameters and jump to the device page displaying the device parameters.

[0012] Optionally, in a specific implementation manner, the method further includes:

[0013] When detecting an update operation on the device parameters displayed on the device page, call the authentication function through the device page, so that the platform page generates second authentication data based on the authentication function and feeds back the second authentication data to the device page;

[0014] Send an update instruction for the update operation carrying the second authentication data to the communication platform through the device page, so that when the communication platform successfully verifies the second authentication data, it sends the update instruction to the target device based on the registration information and feeds back the response information sent by the target device after responding to the update instruction to the device page;

[0015] Receive the response information and update the device parameters displayed on the device page based on the response information.

[0016] Optionally, in a specific implementation manner, the sending a page request for the target device to the communication platform includes:

[0017] Open a preset window and determine the address of the device page for the target device; wherein, the platform page and the preset window are bound and set in the same network domain;

[0018] Send a page request for the target device carrying the address to the communication platform through the preset window;

[0019] The sending a parameter request for the target device carrying the first authentication data to the communication platform through the device page includes:

[0020] Generate a parameter request for the target device and splice the first authentication data with the parameter request;

[0021] Send the parameter request spliced with the first authentication data to the communication platform through the device page.

[0022] Second aspect, an embodiment of the present application provides a device communication method, which is applied to a communication platform in a device communication system. The system further includes a client and at least one communication device, and the at least one communication device is pre-registered with the communication platform; the method includes:

[0023] Receiving a page request for a target device sent by the client, and based on the registration information of the at least one communication device, sending the page request to the target device, so that the target device determines a page file based on the page request and sends the page file to the communication platform; wherein, the page request is sent by the client when displaying the platform page of the communication platform and detecting a click operation on the target device; the target device is any one of the at least one communication device;

[0024] Receiving the page file, and feeding back the page file to the client, so that the client receives the page file and executes the page file to obtain the device page of the target device;

[0025] Receiving a parameter request for the target device carried with first authentication data sent by the client, and verifying the first authentication data; wherein, the parameter request is sent by the client through the device page after receiving the first authentication data fed back by the platform page, and the first authentication data is generated by the platform page based on the authentication function when the client calls the authentication function of the platform page through the device page after obtaining the device page;

[0026] When the verification is successful, sending the parameter request to the target device based on the registration information, so that the target device determines device parameters based on the parameter request and feeds back the device parameters to the communication platform;

[0027] Receiving the device parameters, and feeding back the device parameters to the client, so that the client jumps to the device page displaying the device parameters after receiving the device parameters.

[0028] Optionally, in a specific implementation manner, the method further includes:

[0029] Receiving an update instruction carried with second authentication data sent by the client, and verifying the second authentication data; wherein, the update instruction is sent by the client through the device page after receiving the second authentication data fed back by the platform page, and the second authentication data is generated by the platform page based on the authentication function when the client calls the authentication function through the device page after detecting an update operation on the device parameters displayed on the device page;

[0030] When the verification is successful, send the update instruction to the target device based on the registration information, so that the target device responds to the update instruction and sends response information to the communication platform;

[0031] Receive the response information and feedback the response information to the client, so that the client updates the device parameters displayed on the device page based on the response information.

[0032] Optionally, in a specific implementation manner, the receiving the page request of the target device sent by the client includes:

[0033] Receive the page request of the target device carried with an address sent by the client through a preset window;

[0034] Wherein, the address is the address of the device page of the target device determined by the client when detecting the click operation, and the preset window is a window opened by the client when detecting the click operation and bound to the platform page and set in the same domain;

[0035] The receiving the parameter request of the target device sent by the client carried with the first authentication data includes:

[0036] Receive the parameter request of the target device sent by the client spliced with the first authentication data.

[0037] Optionally, in a specific implementation manner, the first authentication data includes: a first control session and a first token;

[0038] The verifying the first authentication data includes:

[0039] Judge whether the first control session to be verified stored preset is consistent with the first control session, and judge whether the first token is within the preset data range of the token;

[0040] If the first control session to be verified is consistent with the first control session and the first token is within the preset data range, the verification of the first authentication data is successful.

[0041] Optionally, in a specific implementation manner, the communication platform includes a proxy service module and a media relay service module;

[0042] The receiving the page request of the target device sent by the client and sending the page request to the target device based on the registration information of the at least one communication device includes:

[0043] The proxy service module receives a page request for a target device sent by the client; the proxy service module forwards the page request to the media transfer service module; the media transfer service module sends the page request to the target device based on the registration information of the at least one communication device;

[0044] Receiving the page file and feeding back the page file to the client includes:

[0045] The media transfer service module receives the page file; the media transfer service module sends the page file to the proxy service module; the proxy service module feeds back the page file to the client;

[0046] Receiving a parameter request for the target device carried with first authentication data sent by the client and verifying the first authentication data includes:

[0047] The proxy service module receives the parameter request for the target device carried with first authentication data sent by the client; the proxy service module sends the parameter request to the media transfer service module, and the media transfer service module verifies the first authentication data;

[0048] When the verification is successful, sending the parameter request to the target device based on the registration information includes:

[0049] When the verification is successful, the media transfer service module sends the parameter request to the target device based on the registration information;

[0050] Receiving the device parameters and feeding back the device parameters to the client includes:

[0051] The media transfer service module receives the device parameters; the media transfer service module sends the device parameters to the proxy service module; the proxy service module feeds back the device parameters to the client.

[0052] In a third aspect, an embodiment of the present application provides a device communication apparatus applied to a client in a device communication system, the system further including: a communication platform and at least one communication device, the communication platform having pre-registered the at least one communication device; the apparatus includes:

[0053] A page display module, configured to display the platform page of the communication platform, and when a click operation on a target device is detected, send a page request regarding the target device to the communication platform, so that the communication platform, based on the registration information of the at least one communication device, sends the page request to the target device and feeds back the page file sent by the target device to the client; wherein, the target device is any one of the at least one communication device;

[0054] A file receiving module, configured to receive the page file and execute the page file to obtain the device page of the target device;

[0055] An invocation module, configured to invoke the authentication function of the platform page through the device page, so that the platform page generates first authentication data based on the authentication function and feeds back the first authentication data to the device page;

[0056] A request sending module, configured to send a parameter request regarding the target device carrying the first authentication data to the communication platform through the device page, so that when the communication platform successfully verifies the first authentication data, it sends the parameter request to the target device based on the registration information and feeds back the device parameters sent by the target device to the client;

[0057] A parameter receiving module, configured to receive the device parameters and jump to the device page displaying the device parameters.

[0058] Optionally, in a specific implementation manner, the apparatus further includes:

[0059] A detection module, configured to, when a update operation on the device parameters displayed on the device page is detected, invoke the authentication function through the device page, so that the platform page generates second authentication data based on the authentication function and feeds back the second authentication data to the device page;

[0060] An instruction sending module, configured to send an update instruction regarding the update operation carrying the second authentication data to the communication platform through the device page, so that when the communication platform successfully verifies the second authentication data, it sends the update instruction to the target device based on the registration information and feeds back the response information sent by the target device after responding to the update instruction to the device page;

[0061] A parameter display module, configured to receive the response information and update the device parameters displayed on the device page based on the response information.

[0062] Optionally, in a specific implementation manner, the page display module is specifically configured to:

[0063] Open a preset window and determine the address of the device page for the target device; wherein, the platform page and the preset window are bound and set in the same domain;

[0064] Send a page request for the target device carrying the address to the communication platform through the preset window;

[0065] The request sending module includes:

[0066] Generate a parameter request for the target device and splice the first authentication data with the parameter request;

[0067] Send the parameter request spliced with the first authentication data to the communication platform through the device page.

[0068] In a fourth aspect, an embodiment of the present application provides a device communication apparatus, which is applied to a communication platform in a device communication system. The system further includes a client and at least one communication device, and the at least one communication device is pre-registered in the communication platform; the apparatus includes:

[0069] A page request receiving module, configured to receive a page request for a target device sent by the client, and based on the registration information of the at least one communication device, send the page request to the target device, so that the target device determines a page file based on the page request and sends the page file to the communication platform; wherein, the page request is sent by the client when displaying the platform page of the communication platform and detecting a click operation on the target device; the target device is any one of the at least one communication device;

[0070] A page file receiving module, configured to receive the page file and feedback the page file to the client, so that the client receives the page file and executes the page file to obtain the device page of the target device;

[0071] A parameter request receiving module, configured to receive a parameter request for the target device carrying the first authentication data sent by the client, and verify the first authentication data; wherein, the parameter request is sent by the client through the device page after receiving the first authentication data fed back by the platform page, and the first authentication data is generated by the platform page based on an authentication function when the client calls the authentication function of the platform page through the device page after obtaining the device page;

[0072] A parameter sending module, configured to, when the verification is successful, send the parameter request to the target device based on the registration information, so that the target device determines device parameters based on the parameter request and feeds back the device parameters to the communication platform;

[0073] A parameter feedback module, configured to receive the device parameters and feed back the device parameters to the client, so that the client jumps to the device page displaying the device parameters after receiving the device parameters.

[0074] Optionally, in a specific implementation manner, the device further includes:

[0075] An update instruction receiving module, configured to receive an update instruction carrying second authentication data sent by the client and verify the second authentication data; wherein, the update instruction is sent by the client through the device page after receiving the second authentication data fed back by the platform page, and the second authentication data is generated by the platform page based on the authentication function when the client detects an update operation on the device parameters displayed on the device page and calls the authentication function through the device page;

[0076] An update instruction sending module, configured to, when the verification is successful, send the update instruction to the target device based on the registration information, so that the target device responds to the update instruction and sends response information to the communication platform;

[0077] A response information receiving module, configured to receive the response information and feed back the response information to the client, so that the client updates the device parameters displayed on the device page based on the response information.

[0078] Optionally, in a specific implementation manner, the page request receiving module is specifically configured to:

[0079] Receive a page request about the target device carrying an address sent by the client through a preset window;

[0080] wherein, the address is the address of the device page of the target device determined by the client when detecting the click operation, and the preset window is a window opened by the client when detecting the click operation and bound to the platform page and set in the same domain;

[0081] The parameter request receiving module is specifically configured to:

[0082] Receive a parameter request about the target device sent by the client and spliced with first authentication data.

[0083] Optionally, in a specific implementation, the first authentication data includes: a first control session and a first token;

[0084] The parameter request receiving module is specifically configured to:

[0085] Determine whether the first control session to be verified stored in advance is consistent with the first control session, and determine whether the first token is within the preset data range of the token;

[0086] If the first control session to be verified is consistent with the first control session and the first token is within the preset data range, the verification of the first authentication data is successful.

[0087] Optionally, in a specific implementation, the communication platform includes a proxy service module and a media relay service module;

[0088] The page request receiving module is specifically configured to:

[0089] The proxy service module receives a page request about the target device sent by the client; the proxy service module forwards the page request to the media relay service module; the media relay service module sends the page request to the target device based on the registration information of the at least one communication device;

[0090] The page file receiving module is specifically configured to:

[0091] The media relay service module receives the page file; the media relay service module sends the page file to the proxy service module; the proxy service module feeds back the page file to the client;

[0092] The parameter request receiving module is specifically configured to:

[0093] The proxy service module receives a parameter request about the target device carrying the first authentication data sent by the client; the proxy service module sends the parameter request to the media relay service module, and the media relay service module verifies the first authentication data;

[0094] The parameter sending module is specifically configured to:

[0095] When the verification is successful, the media relay service module sends the parameter request to the target device based on the registration information;

[0096] The parameter feedback module is specifically configured to:

[0097] The media relay service module receives the device parameters; the media relay service module sends the device parameters to the proxy service module; the proxy service module feeds back the device parameters to the client.

[0098] In a fifth aspect, an embodiment of the present application provides an electronic device, which is installed with a client, and the electronic device includes a processor and a memory;

[0099] The memory is used for storing a computer program;

[0100] The processor is configured to implement the method steps of any one of the above first aspects when executing the program stored in the memory.

[0101] In a sixth aspect, an embodiment of the present application provides an electronic device, including a processor and a memory;

[0102] The memory is used for storing a computer program;

[0103] The processor is configured to implement the method steps of any one of the above second aspects when executing the program stored in the memory.

[0104] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, it implements the method steps of any one of the above first aspects, or the method steps of any one of the above second aspects.

[0105] In an eighth aspect, an embodiment of the present application further provides a computer program product containing instructions, which when running on a computer, causes the computer to execute the method steps of any one of the above first aspects, or the method steps of any one of the above second aspects.

[0106] Beneficial effects of the embodiments of the present application:

[0107] As can be seen above, by applying the solution provided by the embodiments of the present application, the device communication system may include a client, a communication platform, and at least one communication device, and at least one communication device is pre-registered in the communication platform.

[0108] When establishing communication between a client and a target device in at least one communication device, the client may first display a platform page of the communication platform, and when a click operation for the target device is detected, send a page request about the target device to the communication platform. In this way, the communication platform can send a page request to the target device based on the registration information of at least one communication device. Afterwards, the target device can determine a page file based on the above page request, and send the determined page file to the communication platform, and then the communication platform can feed back the above page file to the client. Then, the client can receive the above page file, and execute the received page file to obtain the device page of the target device. Afterwards, the client can call the authentication function of the platform page of the communication platform, so that the platform page generates the first authentication data based on the above authentication function, and feeds back the above first authentication data to the above device page. Then, the client can send a parameter request about the target device carrying the above first authentication data to the communication platform, so that after receiving the above parameter request, the communication platform can verify the above first authentication data, and when the verification is successful, send the above parameter request to the target device based on the above registration information. Then, the target device can determine the device parameters based on the received parameter request and send the device parameters to the communication platform, and the communication platform can feed back the device parameters to the client. In this way, the client can jump to the device page displaying the received device parameters. At this point, the client can output the device page displaying the received device parameters.

[0109] Based on this, the scheme provided by the embodiment of the present application is applied. For each communication device without a fixed IP, each communication device can be pre-registered on the communication platform. In this way, when the client communicates with the target device in the above-mentioned communication devices, the platform page of the communication platform can be used to realize the transmission of the signaling about the device page of the target device between the client and the communication platform, and the platform page of the communication platform and the authentication function of the communication platform can be used to realize the transmission of the signaling about the device parameters of the target device between the client and the communication platform; further, based on the communication between the communication platform and the communication device, the transmission of the above-mentioned signaling between the communication platform and the target device can be realized, so that the communication between the client and the target device is realized with the communication platform as the signaling transmission medium. Since the IP of the target device is not required in the above process, for an electronic device without a fixed IP, when the electronic device without a fixed IP is remotely operated, the communication between the client located in other electronic devices and the electronic device can be realized without using the IP of the electronic device. BRIEF DESCRIPTION OF THE DRAWINGS

[0110] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other embodiments can also be obtained based on these drawings.

[0111] Figure 1 It is a flowchart of a device communication method for a client applied to a device communication system provided by an embodiment of the present application;

[0112] Figure 2 It is a schematic structural diagram of a device communication system provided by an embodiment of the present application;

[0113] Figure 3 It is another schematic structural diagram of a device communication system provided by an embodiment of the present application;

[0114] Figure 4 It is a specific example diagram of an Ehome communication system provided by an embodiment of the present application;

[0115] Figure 5 It is a flowchart of a device communication method for a communication platform applied to a device communication system provided by an embodiment of the present application;

[0116] Figure 6 It is a schematic structural diagram of a device communication device for a client applied to a device communication system provided by an embodiment of the present application;

[0117] Figure 7 It is a schematic structural diagram of a device communication device for a communication platform applied to a device communication system provided by an embodiment of the present application;

[0118] Figure 8 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application;

[0119] Figure 9 It is another schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0120] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, rather than all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art based on the present application belong to the scope protected by the present application.

[0121] In the related art, when remotely operating an electronic device, a user can connect to the electronic device by entering the IP of the electronic device in a client installed on another electronic device, thereby achieving communication with the electronic device. Further, remote operations on the electronic device are performed on the operation interface of the client.

[0122] However, in the above related art, for an electronic device without a fixed IP, the user cannot use the above method to achieve communication between the client and the electronic device, and further, cannot remotely operate the electronic device.

[0123] To solve the above technical problems, embodiments of the present application provide a device communication method for a client in a device communication system, and a device communication method for a communication platform in a device communication system.

[0124] Among them, the above device communication system may include: a client, a communication platform, and at least one communication device, and the above communication platform is pre-registered with the above at least one communication device. The above client can be installed in various electronic devices such as mobile phones, laptop computers, servers, etc. Among them, the above client can be various clients for opening the platform page of the communication platform and the device page of the communication device. For example, the client can be a browser client, etc.; the above communication platform can be an electronic device integrated with a device communication function module, or a cluster composed of multiple electronic devices.

[0125] In addition, the number of clients and communication devices in the above device communication system can be set according to actual needs. Thus, the system can include one client and one communication device, or multiple clients and one communication device, or multiple clients and multiple communication devices.

[0126] For example: when the client and the communication device are in one-to-one correspondence, the system can include one client and one communication device, and the client and the communication device are uniquely corresponding; when the client can correspond to multiple communication devices, the system can include one client and multiple communication devices; when multiple clients correspond to one communication device, the system can include multiple clients and one communication device, all of which are reasonable and not specifically limited in the embodiments of the present application.

[0127] For another example, the system may include multiple clients and multiple communication devices. Optionally, the above clients may correspond to the above communication devices one by one, so that the number of clients included in the system is the same as the number of communication devices; optionally, each of the above clients may also correspond to at least two of the multiple communication devices, and each communication device may correspond to one of the multiple clients; optionally, each of the above clients may respectively correspond to one of the multiple communication devices, and each communication device may correspond to at least two of the multiple clients; optionally, each of the above clients may respectively correspond to at least two of the multiple communication devices, and each communication device may correspond to at least two of the multiple clients.

[0128] The device communication method provided by the embodiments of the present application is applicable to various scenarios where a client communicates with a communication device. For example, a scenario where a client needs to remotely control an electronic device. Exemplarily, the client remotely operates an IPC (IP Camera) without a fixed IP; based on this, the embodiments of the present application do not specifically limit the application scenario of the system.

[0129] A device communication method for a client applied to a device communication system provided by the embodiments of the present application may include the following steps:

[0130] Display a platform page of the communication platform, and when a click operation on a target device is detected, send a page request about the target device to the communication platform, so that the communication platform sends the page request to the target device based on the registration information of the at least one communication device and feeds back a page file sent by the target device to the client; wherein, the target device is any one of the at least one communication device;

[0131] Receive the page file and execute the page file to obtain a device page of the target device;

[0132] Call an authentication function of the platform page through the device page, so that the platform page generates first authentication data based on the authentication function and feeds back the first authentication data to the device page;

[0133] Send a parameter request about the target device carrying the first authentication data to the communication platform through the device page, so that when the communication platform successfully verifies the first authentication data, it sends the parameter request to the target device based on the registration information and feeds back device parameters sent by the target device to the client;

[0134] Receive the device parameters and jump to the device page displaying the device parameters.

[0135] A device communication method for a communication platform applied to a device communication system provided by an embodiment of the present application may include the following steps:

[0136] Receive a page request for a target device sent by the client, and based on the registration information of the at least one communication device, send the page request to the target device, so that the target device determines a page file based on the page request and sends the page file to the communication platform; wherein, the page request is sent by the client when displaying the platform page of the communication platform and detecting a click operation on the target device; the target device is any one of the at least one communication device;

[0137] Receive the page file, and feedback the page file to the client, so that the client receives the page file and executes the page file to obtain the device page of the target device;

[0138] Receive a parameter request for the target device carried with first authentication data sent by the client, and verify the first authentication data; wherein, the parameter request is sent by the client through the device page after receiving the first authentication data fed back by the platform page, and the first authentication data is generated by the platform page based on the authentication function when the client calls the authentication function of the platform page through the device page after obtaining the device page;

[0139] When the verification is successful, send the parameter request to the target device based on the registration information, so that the target device determines device parameters based on the parameter request and feeds back the device parameters to the communication platform;

[0140] Receive the device parameters, and feedback the device parameters to the client, so that the client jumps to the device page displaying the device parameters after receiving the device parameters.

[0141] As can be seen above, by applying the solution provided in the embodiments of the present application, for each communication device without a fixed IP, each communication device can be pre-registered on the communication platform. In this way, when the client communicates with the target device among the above-mentioned communication devices, the signaling transmission of the device page of the target device between the client and the communication platform can be realized by means of the platform page of the communication platform, and the signaling transmission of the device parameters of the target device between the client and the communication platform can be realized by means of the platform page of the communication platform and the authentication function of the communication platform. Furthermore, based on the communication between the communication platform and the communication device, the above-mentioned signaling can be transmitted between the communication platform and the target device, so that the communication between the client and the target device can be realized with the communication platform as the signaling transmission medium. Since the IP of the target device is not involved in the above process, for an electronic device without a fixed IP, when remotely operating the electronic device without a fixed IP, the communication between the client located in another electronic device and the electronic device can be realized without using the IP of the electronic device.

[0142] Next, with reference to the accompanying drawings, a device communication method for a client applied in a device communication system provided in the embodiments of the present application will be specifically described.

[0143] Figure 1 FIG. is a schematic flowchart of a device communication method for a client applied in a device communication system provided in the embodiments of the present application. This method can be applied to a client 100 in a device communication system as shown in Figure 2 FIG. The device communication system may further include: a communication platform 200 and at least one communication device 300, wherein at least one communication device 300 is pre-registered on the communication platform 200.

[0144] Optionally, the communication platform in a device communication system provided by the present application may include a proxy service module and a media transfer service module. The proxy service module may also be a proxy server, and the media transfer service module may also be a media transfer server.

[0145] Optionally, the proxy service module may include: Nginx (proxy service module), the media transfer service module may include: Ehome SDK (Ehome Software Development Kit), and the communication device 300 may include: Ehome device.

[0146] Since each communication device 300 may go offline due to reasons such as network failures or device failures, however, the communication platform 200 can communicate with the communication device 300 only when the communication device 300 is online. Based on this, before communicating with each communication device 300, the communication platform 200 can first determine the online status of the communication device 300. Furthermore, when the online status of the communication device 300 is the online state, signaling interaction can be performed with the communication device 300.

[0147] The communication platform 200 can use various methods to determine the online status of the communication device 300. For example, the communication platform 200 can determine the online status of the communication device 300 through a heartbeat mechanism.

[0148] As a mechanism for ensuring the validity of a connection by sending heartbeat packets, the heartbeat mechanism can generally be used by either of the two communicating devices to notify the other party that it is still online, or to detect whether the other party is online.

[0149] Optionally, in a specific implementation, the communication platform 200 can receive an online notification sent by the target device 300, update the online status of the target device 300 to the online state, and send a preset heartbeat sending interval to the target device 300; if no heartbeat packet sent by the target device 300 is received within the preset heartbeat sending interval, update the online status of the target device 300 to the offline state; when determining the target device 300 with a device identifier, detect whether the target device 300 is online; when the target device 300 is not online, send a first feedback message about the target device being offline to the client;

[0150] In this specific implementation, for each communication device 300, when the communication device 300 goes online, the communication device 300 can send an online notification to the communication platform 200. The communication platform 200 receives the online notification sent by the communication device 300, updates the online status of the communication device 300 to the online state, and sends a preset heartbeat sending interval to the communication device 300. Among them, the above preset heartbeat sending interval can be set according to actual needs, it can be 5 seconds, or it can be 1 minute, both are reasonable, and the embodiments of the present application do not make specific limitations.

[0151] The communication device 300 receives the preset heartbeat sending interval sent by the communication platform 200 and sends a heartbeat packet to the communication platform 200 according to the above preset heartbeat sending interval. Among them, the above heartbeat packet can be set according to actual needs, it can be a device online message, or it can be a subscription update message, both are reasonable, and the embodiments of the present application do not make specific limitations.

[0152] The communication platform 200 receives the heartbeat message sent by the communication device 300, and determines the online status of the communication device 300 based on a preset heartbeat sending interval. If the communication platform 200 receives the heartbeat message sent by the communication device 300 according to the above preset heartbeat sending interval, it is considered that the online status of the communication device 300 is the online state; if the communication platform 200 does not receive the heartbeat message sent by the communication device 300 within the above preset heartbeat sending interval, the online status of the communication device 300 is updated to the offline state.

[0153] Exemplarily, the heartbeat sending interval is 5 seconds, and the heartbeat message is a subscription update message. The target device 300 sends a subscription update message to the communication platform 200 every 5 seconds. The communication platform 200 receives the subscription update message sent by the communication device 300 and determines that the online status of the communication device 300 is the online state.

[0154] In this way, when the communication platform 200 receives a file request sent by the client 100 and determines the target device 300 with the above device identifier among the pre-registered communication devices, it can first detect whether the target device 300 is online. Thus, when it is determined that the target device 300 is not online, the communication platform 200 can send a second feedback message about the offline status of the target device 300 to the client 100. In this way, the client 100 can receive the above second feedback message and display the above second feedback message to prompt the user that the target device 300 is offline and the request sending fails.

[0155] When it is determined that the target device 300 is online, the communication platform 200 can send the above file request to the target device 300.

[0156] Based on the same inventive concept, when the communication platform 200 receives a parameter request and / or an update instruction sent by the client 100 and determines the target device 300 with the above device identifier among the pre-registered communication devices, it can first detect whether the target device 300 is online. Thus, when it is determined that the target device 300 is not online, the communication platform 200 can send a third feedback message about the offline status of the target device 300 to the client 100. In this way, the client 100 can receive the above fourth notification message and display the above third feedback message to prompt the user that the target device 300 is offline and the request sending fails. When it is determined that the target device 300 is online, the communication platform 200 can send the above parameter request and / or update instruction to the target device 300.

[0157] As Figure 1 shown, a device communication method for a client applied to a device communication system provided by an embodiment of the present application may include the following steps S101 - S105:

[0158] S101: Display the platform page of the communication platform 200, and when a click operation on the target device 300 is detected, send a page request regarding the target device 300 to the communication platform 200, so that the communication platform 200 sends a page request to the target device 300 based on the registration information of at least one communication device 300 and feeds back the page file sent by the target device 300 to the client 100;

[0159] Wherein, the target device 300 is any one of at least one communication device 300;

[0160] When establishing communication between the client 100 and the communication device 300, the user can operate the client 100 to open the platform page of the communication platform 200 in the client 100, so that the client 100 displays the platform page of the communication platform 200.

[0161] For example, the user can enter the platform IP of the communication platform 200 in the client, so that the above-mentioned client 100 can jump from the current interface to the platform page of the communication platform 200.

[0162] Furthermore, when the client 100 displays the platform page of the communication platform 200, the client 100 can detect the user's operations on the platform page in real time. For each communication device 300 pre-registered in the communication platform 200, a click object for selecting each communication device 300 can be displayed on the platform page of the communication platform 200.

[0163] For example, multiple buttons that can be clicked by the user can be displayed on the platform page of the communication platform 200, and the identifier of the above-mentioned one communication device 300 is marked on each button; for another example, multiple links that can be clicked by the user can be displayed on the platform page of the communication platform 200, and the identifier of the above-mentioned one communication device 300 is marked in each link, etc.

[0164] The user can perform a click operation on the click object of the target device among the above-mentioned communication devices 300 on the platform page of the communication platform 200 according to their own communication needs.

[0165] For example, there is a selection box and a click button for confirming the selection on the above-mentioned platform page. In this way, the user can select the device identifier of the target device 300 from the drop-down menu in the above-mentioned selection box, and then click the click button;

[0166] For another example, there is a selection box and a click button for confirming the selection on the above-mentioned platform page. In this way, the user can enter the device identifier of the target device 300 in the above-mentioned input box, and then click the click button.

[0167] In this way, when the user operates on the target device 300 on the above platform page, the client 100 can detect the click operation on the target device 300. Thus, the client 100 can generate a page request for the device page of the target device 300 and send the page request to the communication platform 200 through the platform page.

[0168] Among them, when the client 100 detects the click operation on the target device 300, it can determine the device identifier of the target device 300. Thus, the page request for the device page of the target device 300 generated above can include the device identifier of the target device 300. And the above device identifier can be a device code or a device name, which is reasonable and not specifically limited in the embodiments of this application. Any device identifier that can be used to uniquely determine the above target device 300 is within the protection scope of this application.

[0169] For each communication device 300, the communication device 300 can send registration information including its own device identifier to the communication platform 200, so as to be pre-registered in the communication platform 200. In this way, the communication platform 200 can receive the registration information sent by the communication device 300, store the registration information of the communication device, and complete the registration of the communication device 300.

[0170] Optionally, when the communication platform 200 registers each communication device 300, the communication platform 200 can allocate communication information to each communication device 300 registered in the communication platform 200. After allocating the communication information, it can send the allocated communication information to each communication device 300, establish the corresponding relationship between the device identifier of each communication device 300 and the communication information allocated to the communication device 300, and store the above corresponding relationship. Among them, the above communication information is used to establish the communication relationship between the communication platform 200 and the communication device 300. Thus, using the above communication information, the communication platform 200 can perform signaling interaction with the communication device 300.

[0171] For example, after the communication device 300 is registered in the above communication platform 200, it can use the communication information allocated by the communication platform 200 for the communication device 300 to establish a communication link between the communication platform 200 and the communication device 300, and realize the communication between the communication platform 200 and the communication device 300 through the above communication link.

[0172] In this way, when the above communication platform 200 receives a page request sent by the client 100, it can obtain the device identifier in the page request. After that, based on the device identifiers in the registration information of each communication device 300 stored, it determines the above target device 300, and sends the above page request to the above target device 300. Then, the target device 300 can receive the above page request, determine the page file indicated by the above file request, and send the above page file to the communication platform 200. Thus, the communication platform 200 can receive the page file sent by the target device 300 and feedback the above page file to the client 100.

[0173] Optionally, when the communication platform 200 receives a page request about the target device 300 sent by the client 100, it can obtain the device identifier in the page request. After that, in the corresponding relationship between the device identifiers of the communication devices 300 recorded and the communication information assigned to the communication devices 300, it finds the communication information corresponding to the device identifier. Furthermore, it can use the above communication information to determine the communication link between the communication platform 200 and the target device 300 established based on the communication information. Thus, the above page request is sent to the target device 300 through this communication link. Since the target device 300 can receive the communication information assigned by the communication platform 200, the target device 300 can also determine the above communication link. In this way, the target device 300 can receive the page request sent by the communication platform 200, and after determining the page file indicated by the above file request, feedback the above page file to the communication platform 200 through this communication link.

[0174] Optionally, as Figure 3 shown, the communication platform 200 may include a proxy service module 210 and a media relay service module 220;

[0175] For example, the above proxy service module 210 may be Nginx, and the above media relay service module 220 may be Ehome SDK.

[0176] Among them, the above proxy service module 210 can receive the page request sent by the client 100 and send the above page request to the media relay service module 220; the media relay service module 220 can receive the page request sent by the above proxy service module 210; among the pre-registered communication devices 300, it determines the target device 300 with the above device identifier and sends the above page request to the target device 300.

[0177] After the target device 300 determines the page file corresponding to the above page request, it can send the above page file to the media transfer service module 220. In this way, the media transfer service module 220 can receive the page file sent by the target device 300 and send the above page file to the proxy service module 210; thus, the proxy service module 210 can receive the page file sent by the media transfer service module 220 and send the page file to the client 100.

[0178] S102: Receive a page file and execute the page file to obtain the device page of the target device;

[0179] The client 100 can receive the page file sent by the communication platform 200. Furthermore, it can execute the above page file to obtain the device page of the above target device 300.

[0180] That is to say, when the client 100 receives the above page file, it can parse the above page file and render the page data obtained by parsing, so as to obtain the device page of the target device 300.

[0181] S103: Invoke the authentication function of the platform page through the device page, so that the platform page generates first authentication data based on the authentication function and feeds back the first authentication data to the device page;

[0182] After the client 100 obtains the device page of the target device 300, in order to display the device parameters of the target device 300 on the device page, it can continue to obtain the device parameters of the target device 300 from the communication platform 200.

[0183] Generally, in order to protect the device parameters of each communication device 300 from being stolen and improve the security of the device parameters of the communication device 300, when the communication platform 200 receives a parameter request from the client 100 regarding the device parameters of each communication device 300, it can verify the parameter requests. Therefore, the authentication data of the communication platform 200 can be carried in each parameter request, and when the carried authentication function passes the verification of the communication platform 200, the communication platform 200 will feed back the device parameters of the communication device 300 requested by the client 100 that sent the parameter request.

[0184] Based on this, when the client 100 obtains the device parameters of the target device 300, it can first invoke the authentication function of the communication platform 200, that is, when the client 100 obtains the device parameters of the target device 300, it can first send a call request for invoking the authentication function of the communication platform 200 to the platform page of the communication platform 200.

[0185] In this way, when the client 100 calls the authentication function of the communication platform 200, the platform page of the communication platform 200 can receive the above call request. Thus, the platform page of the communication platform 200 can generate first authentication data based on the above authentication function and feedback the first authentication data to the device page. Thus, the client 100 can receive the first authentication data.

[0186] Optionally, the authentication function may include a control session and a token; the first authentication data may include: a first control session and a first token. For example, the control session may be session (control session), and the token may be token (mark).

[0187] Among them, the control session is stored in the communication platform. When the client 100 logs in to the communication platform 200 through a preset registered user account and displays the platform page of the communication platform 200, the communication platform 200 returns authentication information to the client 100. This authentication information is bound to the user account currently logged in by the client 100 and is used to judge the permissions of the user account and whether this login is legal, etc. And, the above control session is fixed and is data stored locally on the client 100; when the above control session needs to be used, it can be directly read from the data stored locally.

[0188] The above token is another authentication information between the client 100 and the communication platform 200. It is non-fixed. Each time the client 100 sends a data request to the communication platform 200, the token needs to be added to the above data request for authenticating the data request. And, each time the client 100 calls the token, the platform page can increment the value of the token by one to generate a new token and encrypt the token using the encryption key returned by the communication platform 200 to protect the token from being stolen. In this way, for each call of the authentication function of the platform page by the client 100, the tokens in the authentication data generated and feedback by the platform page are different. Thus, the authentication data obtained by the client 100 each time is different. And, the communication platform 200 stores the data range about the token, and the decrypted token needs to be within the above data range to pass the verification of the communication platform 200.

[0189] S104: Send a parameter request for the target device 300 carrying the first authentication data to the communication platform 200 through the device page, so that when the communication platform 200 successfully verifies the first authentication data, it sends a parameter request to the target device 300 based on the registration information and feedbacks the device parameters sent by the target device 300 to the client 100;

[0190] After that, the client 100 can generate a parameter request for the target device carrying the above-mentioned first authentication data, and send the parameter request to the communication platform 200 through the above-mentioned device page. Among them, the parameter request can carry the device identifier of the target device 300.

[0191] In this way, the communication platform 200 can receive the parameter request sent by the client 100, obtain the first authentication data in the parameter request, and verify the first authentication data.

[0192] Optionally, after receiving the parameter request, the communication platform 200 can authenticate the parameter request based on the control session and token in the first authentication data in the parameter request.

[0193] Optionally, when the first authentication data includes a first control session and a first token, the communication platform 200 determines whether the first control session to be verified stored preset is consistent with the first control session, and determines whether the first token is within the preset data range for the token; if the first control session to be verified is consistent with the first control session and the first token is within the preset data range, the verification of the first authentication data is successful.

[0194] In this specific implementation, for the client 100, the communication platform 200 can obtain the first control session to be verified for the communication platform 200 stored preset and the preset data range for the token; furthermore, the communication platform 200 can determine the first control session included in the first authentication data in the parameter request, and by decrypting the first authentication data in the parameter request, obtain the first token; furthermore, the communication platform 200 can then determine whether the calculated first data to be verified is the same as the first authentication data sent by the received client 100, and determine whether the parsed first token is within the above-mentioned preset data range. In this way, when the first control session to be verified is consistent with the first control session, and the first token is within the above-mentioned preset data range, it can be determined that the verification of the first authentication data is successful. Among them, the method for the platform page of the communication platform 200 to encrypt the first token is the same as the method for the communication platform 200 to decrypt the first token.

[0195] When the verification of the above first authentication data is successful, the communication platform 200 can obtain the device identifier in the parameter request. Then, based on the registration information of each communication device 300 stored in advance, it determines the target device 300 with the above device identifier, and sends the above parameter request to the above target device 300. Thus, the target device 300 can receive the above parameter request, determine the device parameters indicated by the above parameter request, and send the above device parameters to the communication platform 200. Furthermore, the communication platform 200 can receive the above device parameters and send the above device parameters to the client 100.

[0196] Optionally, when the verification of the above first authentication data fails, the communication platform 200 can send a first notification message to the client 100 to indicate that the authentication of the above parameter request fails. In this way, the client 100 can receive the above first notification message and display the above first notification message to prompt the user that the device parameter request of the above target device 300 fails.

[0197] Optionally, as Figure 3 shown, when the communication platform 200 includes a proxy service module 210 and a media relay service module 220, the media relay service module 220 can verify the parameter request sent by the client 100 based on the first authentication data. When the verification of the parameter request fails, it sends a first notification message to the proxy service module 210. When the verification of the parameter request is successful, the media relay service module can determine the target device 300 with the above device identifier among the pre-registered communication devices 300. In this way, the proxy service module 210 can receive the first notification message sent by the media relay service module 220 and send the above first notification message to the client 100.

[0198] Optionally, as Figure 3 shown, when the communication platform 200 includes a proxy service module 210 and a media relay service module 220, the proxy service module 210 can receive the parameter request sent by the client 100 and send the parameter request to the media relay service module 220. The media relay service module 220 can receive the parameter request sent by the proxy service module 210, determine the target device 300 with the above device identifier among the pre-registered communication devices 300 to be communicated, send the above parameter request to the target device 300, receive the device parameters sent by the target device 300, and send the above device parameters to the proxy service module 210. In this way, the proxy service module 210 can receive the above device parameters and send the above device parameters to the client 100.

[0199] Optionally, in a specific implementation, sending a parameter request about the target device 300 carrying the first authentication data to the communication platform 200 through the device page may include steps 11-12:

[0200] Step 11: Generate a parameter request for the target device 300, and splice the first authentication data with the parameter request.

[0201] Step 12: Send the parameter request spliced with the first authentication data to the communication platform 200 through the device page.

[0202] The client 100 can generate a parameter request for the target device 300, and when receiving the above-mentioned first authentication data, splice the obtained first authentication data with the generated parameter request. That is to say, after receiving the first authentication data, the above-mentioned first authentication data can be spliced onto the already generated parameter request to obtain the parameter request after splicing the parameter request and the first authentication data. Among them, when splicing, the splicing order and splicing method of the above-mentioned parameter request and the first authentication data can be set according to actual needs.

[0203] For example, if the above-mentioned parameter request is A and the first authentication data is B, then the first authentication data B can be spliced behind the parameter request A to obtain the spliced parameter request A + B. Then, the parameter request spliced with the first authentication data can be sent to the communication platform 200 through the device page.

[0204] S105: Receive device parameters and jump to the device page displaying the device parameters.

[0205] The client 100 can receive the device parameters sent by the communication platform 200, parse the above-mentioned device parameters, and render the above-mentioned device parameters onto the device page of the target device 300. Then, jump the currently displayed platform page to the device page displaying the device parameters.

[0206] In this way, the client 100 can display the device page of the above-mentioned target device 300 so that the user can obtain the device data of the target device 300 or perform remote operations on the target device 300 through the above-mentioned device page.

[0207] Proxy service module Among them, the device page of the target device 300 displayed by the client 100 can be the parameter page of the target device 300 or the control page of the target device 300, which are both reasonable and not specifically limited in the embodiments of the present application.

[0208] Since in the above process, the signaling interaction between the client 100 and the target device 300 does not require the participation of the IP of the target device, for the communication device 300 without a fixed IP, when the client 100 remotely operates the communication device 300 without a fixed IP, it can communicate between the client 100 in another electronic device and the communication device 300 without using the IP of the communication device.

[0209] As can be seen above, by applying the solution provided in the embodiments of the present application, for each communication device without a fixed IP, each communication device can be pre-registered on the communication platform. In this way, when the client communicates with the target device among the above-mentioned communication devices, the signaling transmission of the device page of the target device between the client and the communication platform can be realized by means of the platform page of the communication platform, and the signaling transmission of the device parameters of the target device between the client and the communication platform can be realized by means of the platform page of the communication platform and the authentication function of the communication platform. Furthermore, based on the communication between the communication platform and the communication device, the above-mentioned signaling can be transmitted between the communication platform and the target device, so that the communication between the client and the target device can be realized with the communication platform as the signaling transmission medium. Since the IP of the target device is not involved in the above process, for an electronic device without a fixed IP, when remotely operating the electronic device without a fixed IP, the communication between the client in another electronic device and the electronic device can be realized without using the IP of the electronic device.

[0210] Generally, when the client 100 detects a click operation on any communication device 300, it can jump to the device page of the communication device 300. Since the device page of the communication device 300 needs to be obtained from the communication platform 200, a preset window can be set in advance. When the client 100 detects a click operation on any communication device 300, the preset window can be opened first, and then, when the device page of the communication device 300 is obtained, the device page can be rendered on the preset window.

[0211] Based on this, optionally, in a specific implementation manner, the above step S101 of sending a page request about the target device 300 to the communication platform 200 may include the following steps 21-22:

[0212] Step 21: Open the preset window and determine the address of the device page of the target device 300; wherein, the platform page and the preset window are bound and set in the same network domain;

[0213] Step 22: Send a page request about the target device 300 carrying the address to the communication platform 200 through the preset window;

[0214] In this specific implementation, when the client 100 detects a click operation on the target device 300, it can open a preset window and determine the address of the device page of the target device 300 among the addresses of the device pages of each communication device 300 stored in itself.

[0215] For each communication device 300, the address of the device page of the communication device 300 can be determined in advance. Thus, the addresses of the device pages of each communication device can be pre-written in the client 100. Therefore, when the client 100 detects a click operation on the target device 300, it can determine the address of the device page of the target device 300.

[0216] After that, the client 100 can generate a page request for the target device 300 carrying the above address and send the page request to the communication platform 200 through the above preset window. Thus, the communication platform can send the above page request to the target device based on the registration information of at least one communication device and feedback the page file determined based on the above address sent by the target device to the client.

[0217] In order to enable the client 100 to call the authentication function of the communication platform 200 through the above preset window to send subsequent parameter requests, the above platform page and the preset window can be bound and set in the same domain.

[0218] Optionally, the platform page of the communication platform 200 can be bound to the preset window by using the binding method in window (window). In this way, when the client 100 displays the platform page of the communication platform 200, it can open the preset window as a new browser window in the platform page of the communication platform 200 based on the user's click operation, and the address of the preset window is an address with the same domain name as the platform page of the communication platform 200. Based on this, since the preset window and the platform page of the communication platform 200 are bound in the same domain, when the page request for the target device 300 is sent to the communication platform 200 through the above preset window, the above page request and the requested page file can be transmitted through the communication platform 200. Thus, the transparent transmission of the page request and the page file between the client 100 and the target device 300 is realized.

[0219] Moreover, since the preset window and the platform page are in the same domain, the preset window and the platform page of the communication platform 200 can share the authentication function of the communication platform 200. In this way, when the client 100 conducts signaling interaction with the communication platform 200 through the above preset window, the preset window can directly call the authentication function of the communication platform 200.

[0220] Since the platform page and the preset window share the authentication function of the communication platform 200, when the client 100 receives a signaling message from the user regarding the target device 300, it can call the above authentication function to generate a signaling message supported by the communication platform 200 that includes the device identifier of the target device 300, and send the above signaling message to the communication platform 200.

[0221] Generally, to achieve remote control of the target device 300, the user can perform an update operation on the device parameters of the target device 300 through the device page displayed by the client 100. For example, the user can perform various operations such as adding and modifying the device parameters of the target device 300 on the device page of the target device 300. After the client 100 detects various update operations of the user, it can generate update instructions corresponding to the operations and send the above update instructions to the target device 300, so that the target device 300 can modify the stored device parameters accordingly.

[0222] Optionally, in a specific implementation, a device communication method provided by an embodiment of the present application may further include the following steps 31-33:

[0223] Step 31: When detecting an update operation on the device parameters displayed on the device page, call the authentication function through the device page, so that the platform page generates second authentication data based on the authentication function and feeds back the second authentication data to the device page;

[0224] Step 32: Send an update instruction regarding the update operation carrying the second authentication data to the communication platform through the device page, so that when the communication platform 200 successfully verifies the second authentication data, it sends an update instruction to the target device 300 based on the registration information and feeds back the response information sent by the target device 300 after responding to the update instruction to the device page;

[0225] Step 33: Receive the response information and update the device parameters displayed on the device page based on the response information.

[0226] In this specific implementation, the user can perform an update operation on the device parameters displayed on the device page.

[0227] For example, in the device page of the above target device 300, there is a data box and a confirmation button for confirming the operation. The user can enter new data in the above data box or select new data from the drop-down menu in the data box. After that, click the confirmation button to confirm the update operation on the device parameters of the target device 300;

[0228] For another example, the user can enter an instruction code for data update of the target device 300 in the above device page.

[0229] When the client 100 detects an update operation on the device parameters displayed on the device page, it can call the authentication function of the platform page through the above-mentioned device page. In this way, the platform page can generate second authentication data based on the above-mentioned authentication function and feedback the second authentication data to the above-mentioned device page. Among them, the above-mentioned second authentication function is an authentication function generated for this call and is only valid for the first use after generation.

[0230] Among them, the above-mentioned update operation can include various operations such as addition and modification.

[0231] Optionally, the above-mentioned second authentication data can include: a second control session and a second token.

[0232] The client 100 can receive the above-mentioned second authentication function, generate an update instruction regarding the update operation carrying the above-mentioned second authentication data, and send the update instruction to the communication platform 200 through the above-mentioned device page. Among them, the above-mentioned update instruction can carry the device identifier of the target device 300.

[0233] Optionally, when detecting an update operation on the device parameters displayed on the device page, an update instruction regarding the update operation can be generated, and the second authentication data can be spliced with the update instruction; the update instruction spliced with the second authentication data is sent to the communication platform through the device page.

[0234] When the client detects an update operation on the device parameters displayed on the device page, it can generate an update instruction regarding the update operation. Furthermore, when the client receives the second authentication data, it can splice the above-mentioned second authentication data onto the above-mentioned update instruction to obtain an update instruction spliced with the second authentication data. After that, the client can send the update instruction spliced with the second authentication data to the above-mentioned communication platform through the device page.

[0235] In this way, the communication platform 200 can receive the above-mentioned update instruction, obtain the second authentication data in the update instruction, and verify the above-mentioned second authentication data.

[0236] Optionally, in the case where the above-mentioned second authentication data includes a second control session and a second token, the communication platform 200 determines whether the first control session to be verified stored preset is consistent with the first control session, and determines whether the first token is within the preset data range regarding the token; if the first control session to be verified is consistent with the first control session and the first token is within the preset data range, the first authentication data verification is successful.

[0237] In this specific implementation, for the client 100, the communication platform 200 can obtain the second control session to be verified regarding the communication platform 200 and the preset data range regarding the token stored in advance; furthermore, the communication platform 200 can determine the second control session included in the second authentication data in the above update instruction, and decrypt the second authentication data in the above update instruction to obtain the second token; furthermore, the communication platform 200 can then determine whether the calculated second data to be verified is the same as the second authentication data sent by the received client 100, and determine whether the parsed second token is within the above preset data range. In this way, when the above second control session to be verified is consistent with the second control session, and the above second token is within the above preset data range, it can be determined that the verification of the above second authentication data is successful. Among them, the method for encrypting the above second token on the platform page of the above communication platform 200 is the same as the method for decrypting the above second token by the above communication platform 200.

[0238] Thus, when the verification of the above second authentication data is successful, obtain the device identifier in the above update instruction, and then, based on the registration information of each communication device stored in advance, determine the target device with the above device identifier, and send the above update instruction to the above target device 300.

[0239] When the verification of the above second authentication data fails, the communication platform 200 can send a second notification message to the client 100 to indicate that the verification of the above second authentication data fails. In this way, the client 100 can receive the above second notification message and display the above second notification message to prompt the user that the update instruction for the device parameters of the target device 300 fails.

[0240] Furthermore, the target device 300 can receive the above update instruction, parse the update instruction, and respond to the update instruction, that is, perform the update operation indicated by the update instruction on the device parameters indicated by the update instruction. And after the response is completed, the target device can send response information indicating successful response to the communication platform 200. After that, the above communication platform 200 can receive the above response information and send the above response information to the client 100.

[0241] In this way, the client 100 can receive the above response information and update the device parameters displayed on the device page based on the above response information so that the user can view the latest status of the device parameters of the target device 300.

[0242] Generally, when the target device 300 updates its own device parameters according to the above update instruction, it may succeed or fail. Therefore, when the target device 300 completes the response to the above update instruction, it can feedback different response information to the communication platform 200 according to the update result.

[0243] Optionally, when the parameter to be updated indicated by the above update instruction is successfully updated in the target device 300, the target device 300 sends a first response message indicating successful update to the communication platform 200; when the parameter to be updated indicated by the above update instruction fails to be updated, the target device 300 sends a second response message indicating failed update to the communication platform 200; the communication platform 200 can receive the first response message or the second response message and send the first response message or the second response message to the client 100; the client 100 can receive the first response message or the second response message.

[0244] In this specific implementation manner, when the parameter to be updated indicated by the above update instruction is successfully updated, the target device 300 can send a first response message indicating that the parameter to be updated is successfully updated to the communication platform 200. In this way, the communication platform 200 can receive the first response message sent by the target device 300 and send the first response message to the client 100. The client 100 can receive the first response message and update the device parameters displayed on the device page based on the first response message.

[0245] When the parameter to be updated indicated by the above update instruction fails to be updated, the target device 300 can send a second response message indicating that the parameter to be updated fails to be updated to the communication platform 200. In this way, the communication platform 200 can receive the second response message sent by the target device 300 and send the second response message to the client 100. The client 100 can receive the second response message, display the second response message, and update the device parameters displayed on the device page based on the second response message.

[0246] Optionally, as Figure 3 shown, when the communication platform 200 includes a proxy service module 210 and a media relay service module 220, the proxy service module 210 can receive an update instruction for the device parameters of the target device 300 sent by the client 100 and send the update instruction to the media relay service module 220. The media relay service module 220 can receive the update instruction sent by the proxy service module 210, determine the target device 300 with the above device identifier among the pre-registered communication devices 300, and send the update instruction to the target device 300. After that, the media relay service module 220 can receive the response message sent by the target device 300 and send the response message to the proxy service module 210. In this way, the proxy service module 210 can receive the response message sent by the media relay service module 220 and send the response message to the client 100.

[0247] Optionally, as Figure 3As shown in the figure, when the communication platform 200 includes a proxy service module 210 and a media relay service module 220, the media relay service module 220 can verify the second authentication data; when the verification of the second authentication data fails, the media relay service module 220 can send a second notification message to the proxy service module 210. In this way, the proxy service module 210 can receive the second notification message sent by the media relay service module 220 and send the second notification message to the client 100; when the update instruction authentication is successful, the media relay service module 220 can determine the target device 300 with a device identifier among the pre-registered communication devices 300.

[0248] To facilitate the understanding of the interaction process among the client, the communication platform, and at least one communication device in the above device communication system, taking the Ehome communication system as an example, combined with Figure 4 the interaction process among the above client, communication platform, and at least one communication device will be described. As Figure 4 shown in the figure, the communication platform in the figure includes a proxy service module and a media relay service module. Among them, Nginx is the proxy service module, and Ehome SDK is the media relay service module.

[0249] The client can display the platform page of the communication platform. When a click operation on the target device is detected, a preset window is opened. The above platform page and the preset window are in the same domain, bound to each other, and share the authentication function of the communication platform.

[0250] When the client opens the above preset window, a page request for the target device is generated. Then, the client sends the page request for the target device to Nginx. Nginx can receive the page request for the target device sent by the client and send the page request to the Ehome SDK. The Ehome SDK can receive the page request sent by Nginx, obtain the device identifier in the above file request, determine the target device with the above device identifier among the pre-registered communication devices, and send the page request to the target device.

[0251] After receiving the above page file request, the target device determines the page file indicated by the above page request and sends the page file to the Ehome SDK. Then, the Ehome SDK can receive the above page file and send the above page file to Nginx.

[0252] Furthermore, Nginx receives the above page file and sends the above page file to the client. The client receives the above page file and executes the above page file to obtain the device page of the target device.

[0253] After that, the client can receive a parameter instruction regarding the device parameters of the target device sent by the user. The client can call the authentication function of the above platform page through a preset window to generate a parameter request regarding the target device carrying the first authentication data. Among them, the above data request can include the device identifier of the target device. The client can send the above parameter request to Nginx. Nginx can receive the above parameter request and send the above parameter request to the Ehome SDK. Then, the Ehome SDK can receive the parameter request sent by Nginx, obtain the first session and the first token in the above parameter request. Furthermore, based on the session and the token, the above parameter request is verified.

[0254] After that, when the above parameter request verification fails, the Ehome SDK can send a first notification message indicating verification failure to Nginx, so that Nginx receives the above first notification message and sends the above first notification message to the client;

[0255] When the above parameter request verification is successful, the Ehome SDK can determine the target device with the above device identifier among the pre-registered communication devices and send the above parameter request to the target device.

[0256] In this way, after receiving the above parameter request, the target device can determine the device parameters indicated by the above parameter request and send the above device parameters to the Ehome SDK, so that the Ehome SDK receives the above device parameters and sends the above device parameters to Nginx.

[0257] Furthermore, Nginx receives the above device parameters and sends the above device parameters to the client, so that the client receives the above device parameters.

[0258] Figure 5 A device communication method for a communication platform applied to a device communication system provided by an embodiment of the present application. This method can be applied to a communication platform in a device communication system. The system can also include: a client and at least one communication device. Among them, the communication platform pre-registers at least one communication device, as Figure 5 shown, this method can include the following steps S501 - S505:

[0259] S501: Receive a page request regarding the target device sent by the client, and based on the registration information of at least one communication device, send a page request to the target device, so that the target device determines a page file based on the page request and sends the page file to the communication platform; among them, the page request is sent by the client when displaying the platform page of the communication platform and detecting a click operation on the target device; the target device is any one of at least one communication device;

[0260] S502: Receive the page file and feedback the page file to the client, so that the client receives the page file and executes the page file to obtain the device page of the target device;

[0261] S503: Receive the parameter request about the target device carried with the first authentication data sent by the client, and verify the first authentication data; wherein, the parameter request is sent by the device page after the client receives the first authentication data fed back by the platform page, and the first authentication data is generated by the platform page based on the authentication function when the client calls the authentication function of the platform page through the device page after obtaining the device page.

[0262] S504: When the verification is successful, send the parameter request to the target device based on the registration information, so that the target device determines the device parameters based on the parameter request and feeds back the device parameters to the communication platform;

[0263] S505: Receive the device parameters and feedback the device parameters to the client, so that the client jumps to the device page displaying the device parameters after receiving the device parameters.

[0264] As can be seen above, by applying the solution provided in the embodiment of the present application, for each communication device without a fixed IP, each communication device can be pre-registered on the communication platform. In this way, when the client communicates with the target device among the above-mentioned communication devices, the signaling transmission of the device page of the target device between the client and the communication platform can be realized by means of the platform page of the communication platform, and the signaling transmission of the device parameters of the target device between the client and the communication platform can be realized by means of the platform page of the communication platform and the authentication function of the communication platform; furthermore, based on the communication between the communication platform and the communication device, the above-mentioned signaling can be transmitted between the communication platform and the target device, thereby realizing the communication between the client and the target device with the communication platform as the signaling transmission medium. Since the IP of the target device is not involved in the above process, for an electronic device without a fixed IP, when remotely operating the electronic device without a fixed IP, the communication between the client located in other electronic devices and the electronic device can be realized without using the IP of the electronic device.

[0265] Optionally, in a specific implementation manner, the method further includes:

[0266] Receive the update instruction carrying the second authentication data sent by the client, and verify the second authentication data; wherein, the update instruction is sent through the device page after the client receives the second authentication data fed back by the platform page, and the second authentication data is generated by the platform page based on the authentication function when the client calls the authentication function through the device page after detecting an update operation on the device parameters displayed on the device page.

[0267] When the verification is successful, send the update instruction to the target device based on the registration information, so that the target device responds to the update instruction and sends a response message to the communication platform.

[0268] Receive the response message and feed back the response message to the client, so that the client updates the device parameters displayed on the device page based on the response message.

[0269] Optionally, in a specific implementation manner, the receiving the page request of the target device sent by the client includes:

[0270] Receive the page request of the target device carrying the address sent by the client through a preset window.

[0271] Wherein, the address is the address of the device page of the target device determined by the client when detecting the click operation, and the preset window is a window opened by the client when detecting the click operation and bound to the platform page and set in the same domain.

[0272] The receiving the parameter request of the target device sent by the client carrying the first authentication data includes:

[0273] Receive the parameter request of the target device concatenated with the first authentication data sent by the client.

[0274] Optionally, in a specific implementation manner, the first authentication data includes: a first control session and a first token.

[0275] The verifying the first authentication data includes:

[0276] Judge whether the first control session to be verified stored preset is consistent with the first control session, and judge whether the first token is within the preset data range of the token.

[0277] If the first control session to be verified is consistent with the first control session and the first token is within the preset data range, the verification of the first authentication data is successful.

[0278] Optionally, in a specific implementation, the communication platform includes a proxy service module and a media relay service module;

[0279] Receiving the page request for the target device sent by the client and sending the page request to the target device based on the registration information of the at least one communication device includes:

[0280] The proxy service module receives the page request for the target device sent by the client; the proxy service module forwards the page request to the media relay service module; the media relay service module sends the page request to the target device based on the registration information of the at least one communication device;

[0281] Receiving the page file and feeding back the page file to the client includes:

[0282] The media relay service module receives the page file; the media relay service module sends the page file to the proxy service module; the proxy service module feeds back the page file to the client;

[0283] Receiving the parameter request for the target device carried with the first authentication data sent by the client and verifying the first authentication data includes:

[0284] The proxy service module receives the parameter request for the target device carried with the first authentication data sent by the client; the proxy service module sends the parameter request to the media relay service module, and the media relay service module verifies the first authentication data;

[0285] When the verification is successful, sending the parameter request to the target device based on the registration information includes:

[0286] When the verification is successful, the media relay service module sends the parameter request to the target device based on the registration information;

[0287] Receiving the device parameters and feeding back the device parameters to the client includes:

[0288] The media relay service module receives the device parameters; the media relay service module sends the device parameters to the proxy service module; the proxy service module feeds back the device parameters to the client.

[0289] Since the specific implementation of this application is the same as the above communication method applied to the client, the specific implementation of this application will not be elaborated here.

[0290] Based on the same inventive concept, an embodiment of the present application further provides a device communication system, as Figure 2 shown. The device communication system may include a client 100, a communication platform 200, and at least one communication device 300; at least one communication device 300 is pre-registered in the communication platform 200.

[0291] Among them, the client 100 may execute a device communication method for the client 100 provided in the present application above;

[0292] The communication platform may execute a device communication method for the communication platform 200 provided in the present application above.

[0293] Based on the same inventive concept, corresponding to the Figure 1 shown device communication method for the client in the device communication system provided in the embodiment of the present application, the embodiment of the present application further provides a device communication device for the client in the device communication system. Applied to the client in the device communication system, the system further includes: a communication platform and at least one communication device, and the at least one communication device is pre-registered in the communication platform.

[0294] Figure 6 It is a schematic structural diagram of a device communication device provided in the embodiment of the present application. As Figure 6 shown, the device may include the following modules:

[0295] A page display module 610, configured to display the platform page of the communication platform, and when detecting a click operation on a target device, send a page request about the target device to the communication platform, so that the communication platform, based on the registration information of the at least one communication device, sends the page request to the target device and feeds back a page file sent by the target device to the client; wherein, the target device is any one of the at least one communication device;

[0296] A file receiving module 620, configured to receive the page file and execute the page file to obtain the device page of the target device;

[0297] An invocation module 630, configured to invoke an authentication function of the platform page through the device page, so that the platform page generates first authentication data based on the authentication function and feeds back the first authentication data to the device page;

[0298] A request sending module 640, configured to send a parameter request for the target device carrying the first authentication data to the communication platform through the device page, so that when the communication platform successfully verifies the first authentication data, the communication platform sends the parameter request to the target device based on the registration information and feeds back the device parameters sent by the target device to the client;

[0299] A parameter receiving module 650, configured to receive the device parameters and jump to the device page displaying the device parameters.

[0300] As can be seen above, by applying the solution provided in the embodiment of the present application, for each communication device without a fixed IP, the communication platform can pre-register each communication device. In this way, when the client communicates with the target device among the above-mentioned communication devices, the signaling transmission of the device page of the target device between the client and the communication platform can be realized by means of the platform page of the communication platform, and the signaling transmission of the device parameters of the target device between the client and the communication platform can be realized by means of the platform page of the communication platform and the authentication function of the communication platform; furthermore, based on the communication between the communication platform and the communication device, the above-mentioned signaling can be transmitted between the communication platform and the target device, so that the communication between the client and the target device is realized with the communication platform as the signaling transmission medium. Since the IP of the target device is not involved in the above process, for an electronic device without a fixed IP, when remotely operating the electronic device without a fixed IP, the communication between the client located in another electronic device and the electronic device can be realized without using the IP of the electronic device.

[0301] Optionally, in a specific implementation manner, the device further includes:

[0302] A detection module, configured to, when detecting an update operation on the device parameters displayed on the device page, call the authentication function through the device page, so that the platform page generates second authentication data based on the authentication function and feeds back the second authentication data to the device page;

[0303] An instruction sending module, configured to send an update instruction for the update operation carrying the second authentication data to the communication platform through the device page, so that when the communication platform successfully verifies the second authentication data, the communication platform sends the update instruction to the target device based on the registration information and feeds back the response information sent by the target device after responding to the update instruction to the device page;

[0304] A parameter display module, configured to receive the response information and update the device parameters displayed on the device page based on the response information.

[0305] Optionally, in a specific implementation, the page display module 610 is specifically configured to:

[0306] Open a preset window and determine the address of the device page of the target device; wherein, the platform page and the preset window are bound and set in the same network domain;

[0307] Send a page request for the target device carrying the address to the communication platform through the preset window;

[0308] The request sending module 640 is specifically configured to:

[0309] Generate a parameter request for the target device and splice the first authentication data with the parameter request;

[0310] Send the parameter request spliced with the first authentication data to the communication platform through the device page.

[0311] Based on the same inventive concept, corresponding to the device communication method of the communication platform in the device communication system provided in the foregoing embodiments of the present application Figure 5 shown, the embodiments of the present application further provide a device communication device of the communication platform in the device communication system. Applied to the communication platform in the device communication system, the system further includes a client and at least one communication device, and the at least one communication device is pre-registered in the communication platform.

[0312] Figure 7 It is a schematic structural diagram of a device communication device provided by an embodiment of the present application. As Figure 7 shown, the device may include the following modules:

[0313] The page request receiving module 710 is configured to receive a page request for a target device sent by the client, and send the page request to the target device based on the registration information of the at least one communication device, so that the target device determines a page file based on the page request and sends the page file to the communication platform; wherein, the page request is sent by the client when displaying the platform page of the communication platform and detecting a click operation on the target device; the target device is any one of the at least one communication device;

[0314] The page file receiving module 720 is configured to receive the page file and feedback the page file to the client, so that the client receives the page file and executes the page file to obtain the device page of the target device;

[0315] A parameter request receiving module 730, configured to receive a parameter request for the target device carried with first authentication data sent by the client, and verify the first authentication data; wherein, the parameter request is sent by the client through the device page after receiving the first authentication data fed back by the platform page, and the first authentication data is generated by the platform page based on an authentication function when the client calls the authentication function of the platform page through the device page after obtaining the device page;

[0316] A parameter sending module 740, configured to, when the verification is successful, send the parameter request to the target device based on the registration information, so that the target device determines device parameters based on the parameter request and feeds back the device parameters to the communication platform;

[0317] A parameter feedback module 750, configured to receive the device parameters and feed back the device parameters to the client, so that the client jumps to the device page displaying the device parameters after receiving the device parameters.

[0318] As can be seen above, by applying the solution provided in the embodiment of the present application, for each communication device without a fixed IP, each communication device can be pre-registered on the communication platform. In this way, when the client communicates with the target device among the above-mentioned communication devices, the signaling transmission of the device page of the target device between the client and the communication platform can be realized by means of the platform page of the communication platform, and the signaling transmission of the device parameters of the target device between the client and the communication platform can be realized by means of the platform page of the communication platform and the authentication function of the communication platform; furthermore, based on the communication between the communication platform and the communication device, the above-mentioned various signaling transmissions between the communication platform and the target device can be realized, so that the communication between the client and the target device can be realized with the communication platform as the signaling transmission medium. Since the IP of the target device is not involved in the above process, for an electronic device without a fixed IP, when remotely operating the electronic device without a fixed IP, the communication between the client located in another electronic device and the electronic device can be realized without using the IP of the electronic device.

[0319] Optionally, in a specific implementation manner, the apparatus further includes:

[0320] An update instruction receiving module, configured to receive an update instruction carrying second authentication data sent by the client, and verify the second authentication data; wherein, the update instruction is sent by the client through the device page after receiving the second authentication data fed back by the platform page, and the first authentication data is generated by the platform page based on the authentication function when the client calls the authentication function through the device page after detecting an update operation on the device parameters displayed on the device page;

[0321] An update instruction sending module, configured to, when the verification is successful, send the update instruction to the target device based on the registration information, so that the target device responds to the update instruction and sends a response message to the communication platform;

[0322] A response message receiving module, configured to receive the response message and feed back the response message to the client, so that the client updates the device parameters displayed on the device page based on the response message.

[0323] Optionally, in a specific implementation manner, the page request receiving module 710 is specifically configured to:

[0324] Receive a page request about the target device carrying an address sent by the client through a preset window;

[0325] Wherein, the address is the address of the device page of the target device determined by the client when detecting the click operation, and the preset window is a window opened by the client when detecting the click operation and bound to the platform page and set in the same domain;

[0326] The parameter request receiving module 730 is specifically configured to:

[0327] Receive a parameter request about the target device sent by the client and spliced with first authentication data.

[0328] Optionally, in a specific implementation manner, the first authentication data includes: a first control session and a first token;

[0329] The parameter request receiving module 730 is specifically configured to:

[0330] Judge whether a first to-be-verified control session stored preset is consistent with the first control session, and judge whether the first token is within a preset data range regarding the token;

[0331] If the first to-be-verified control session is consistent with the first control session and the first token is within the preset data range, the verification of the first authentication data is successful.

[0332] Optionally, in a specific implementation, the communication platform includes a proxy service module and a media relay service module;

[0333] The page request receiving module 710 is specifically configured to:

[0334] The proxy service module receives a page request about a target device sent by the client; the proxy service module forwards the page request to the media relay service module; the media relay service module sends the page request to the target device based on the registration information of the at least one communication device;

[0335] The page file receiving module 720 is specifically configured to:

[0336] The media relay service module receives the page file; the media relay service module sends the page file to the proxy service module; the proxy service module feeds back the page file to the client;

[0337] The parameter request receiving module 730 is specifically configured to:

[0338] The proxy service module receives a parameter request about the target device carrying first authentication data sent by the client; the proxy service module sends the parameter request to the media relay service module, and the media relay service module verifies the first authentication data;

[0339] The parameter sending module 740 is specifically configured to:

[0340] When the verification is successful, the media relay service module sends the parameter request to the target device based on the registration information;

[0341] The parameter feedback module 750 is specifically configured to:

[0342] The media relay service module receives the device parameters; the media relay service module sends the device parameters to the proxy service module; the proxy service module feeds back the device parameters to the client.

[0343] An embodiment of the present application further provides an electronic device, which is installed with a client, as Figure 8 shown. The electronic device includes: a memory 801 and a processor 802;

[0344] The memory 801 is used for storing a computer program;

[0345] When the processor 802 executes the program stored in the memory 801, it implements the device communication method of the client applied to the device communication system described in any one of the above.

[0346] And optionally, the above electronic device may further include a communication bus and / or a communication interface, and the processor 802, the communication interface, and the memory 801 complete communication with each other through the communication bus.

[0347] The embodiment of the present application further provides another electronic device, as Figure 9 shown, the electronic device includes: a memory 901 and a processor 902;

[0348] The memory 901 is used to store a computer program;

[0349] The processor 902, when executing the program stored on the memory 901, implements any of the above-mentioned device communication methods for the client applied to the device communication system.

[0350] And optionally, the above electronic device may further include a communication bus and / or a communication interface, and the processor 902, the communication interface, and the memory 901 complete communication with each other through the communication bus.

[0351] The communication bus mentioned in the above electronic device may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, only a thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0352] The communication interface is used for communication between the above electronic device and other devices.

[0353] The memory may include a Random Access Memory (RAM), or may also include a Non-Volatile Memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located far from the aforementioned processor.

[0354] The above-mentioned processor may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0355] In another embodiment provided by the present application, there is also provided a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the steps of any of the above device communication methods are implemented.

[0356] In another embodiment provided by the present application, there is also provided a computer program product containing instructions, and when it runs on a computer, it causes the computer to execute any of the device communication methods in the above embodiments.

[0357] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or a wireless manner (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or data center that includes one or more integrated available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a Solid State Disk (SSD)).

[0358] It should be noted that in this text, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprising", "including" or any other variant thereof are intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or device comprising the said element.

[0359] Each embodiment in this specification is described in a related manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for system embodiments, device embodiments, electronic device embodiments, and computer-readable storage medium embodiments, since they are basically similar to method embodiments, the description is relatively simple, and reference can be made to the corresponding parts of the method embodiments for the relevant content.

[0360] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A device communication method, characterized in that, A client applied to a device communication system, the system further comprising: a communication platform and at least one communication device, the at least one communication device being pre-registered with the communication platform; the method comprising: Display a platform page of the communication platform, and when a click operation on a target device is detected, send a page request regarding the target device to the communication platform, so that the communication platform, based on the registration information of the at least one communication device, sends the page request to the target device and feeds back a page file sent by the target device to the client; wherein, the target device is any one of the at least one communication device; Receive the page file and execute the page file to obtain a device page of the target device; Call an authentication function of the platform page through the device page, so that the platform page generates first authentication data based on the authentication function and feeds back the first authentication data to the device page; Send a parameter request regarding the target device carrying the first authentication data to the communication platform through the device page, so that when the communication platform successfully verifies the first authentication data, it sends the parameter request to the target device based on the registration information and feeds back device parameters sent by the target device to the client; Receive the device parameters and jump to the device page displaying the device parameters.

2. The method according to claim 1, characterized in that, The method further comprises: When an update operation on the device parameters displayed on the device page is detected, call the authentication function through the device page, so that the platform page generates second authentication data based on the authentication function and feeds back the second authentication data to the device page; Send an update instruction regarding the update operation carrying the second authentication data to the communication platform through the device page, so that when the communication platform successfully verifies the second authentication data, it sends the update instruction to the target device based on the registration information and feeds back response information sent by the target device after responding to the update instruction to the device page; Receive the response information and update the device parameters displayed on the device page based on the response information.

3. The method according to claim 1 or 2, characterized in that, The sending the page request regarding the target device to the communication platform includes: Open a preset window and determine the address of the device page regarding the target device; wherein, the platform page and the preset window are bound and set in the same network domain; Send a page request regarding the target device carrying the address to the communication platform through the preset window; The sending the parameter request regarding the target device carrying the first authentication data to the communication platform through the device page includes: Generate a parameter request regarding the target device and splice the first authentication data with the parameter request; Send the parameter request spliced with the first authentication data to the communication platform through the device page.

4. A device communication method, characterized in that, A communication platform applied to a device communication system, the system further comprising a client and at least one communication device, and the communication platform being pre-registered with the at least one communication device; the method comprising: Receiving a page request for a target device sent by the client, and based on the registration information of the at least one communication device, sending the page request to the target device, so that the target device determines a page file based on the page request and sends the page file to the communication platform; wherein, the page request is sent by the client when displaying the platform page of the communication platform and detecting a click operation on the target device; the target device is any one of the at least one communication device; Receiving the page file and feeding back the page file to the client, so that the client receives the page file and executes the page file to obtain the device page of the target device; Receiving a parameter request for the target device sent by the client and carrying first authentication data, and verifying the first authentication data; wherein, the parameter request is sent by the client through the device page after receiving the first authentication data fed back by the platform page, and the first authentication data is generated by the platform page based on the authentication function when the client calls the authentication function of the platform page through the device page after obtaining the device page; When the verification is successful, sending the parameter request to the target device based on the registration information, so that the target device determines device parameters based on the parameter request and feeds back the device parameters to the communication platform; Receiving the device parameters and feeding back the device parameters to the client, so that the client jumps to the device page displaying the device parameters after receiving the device parameters.

5. The method according to claim 4, characterized in that, The method further comprises: Receiving an update instruction sent by the client and carrying second authentication data, and verifying the second authentication data; wherein, the update instruction is sent by the client through the device page after receiving the second authentication data fed back by the platform page, and the second authentication data is generated by the platform page based on the authentication function when the client calls the authentication function through the device page after detecting an update operation on the device parameters displayed on the device page; When the verification is successful, sending the update instruction to the target device based on the registration information, so that the target device responds to the update instruction and sends response information to the communication platform; Receiving the response information and feeding back the response information to the client, so that the client updates the device parameters displayed on the device page based on the response information.

6. The method according to claim 4, characterized in that, The receiving the page request for the target device sent by the client includes: Receiving the page request for the target device sent by the client through a preset window and carrying an address; Wherein, the address is the address of the device page of the target device determined by the client when detecting the click operation, and the preset window is a window opened by the client when detecting the click operation and bound to the platform page and set in the same domain; Receiving the parameter request for the target device carried with the first authentication data sent by the client, including: Receiving the parameter request for the target device with the first authentication data spliced thereto sent by the client.

7. The method according to claim 4, wherein The first authentication data includes: a first control session and a first token; Verifying the first authentication data includes: Judging whether the first control session to be verified stored preset is consistent with the first control session, and judging whether the first token is within the preset data range of the token; If the first control session to be verified is consistent with the first control session and the first token is within the preset data range, the verification of the first authentication data is successful.

8. The method according to any one of claims 4-7, characterized in that The communication platform includes a proxy service module and a media transfer service module; Receiving the page request for the target device sent by the client, and based on the registration information of the at least one communication device, sending the page request to the target device, including: The proxy service module receives the page request for the target device sent by the client; the proxy service module forwards the page request to the media transfer service module; the media transfer service module sends the page request to the target device based on the registration information of the at least one communication device; Receiving the page file and feeding back the page file to the client, including: The media transfer service module receives the page file; the media transfer service module sends the page file to the proxy service module; the proxy service module feeds back the page file to the client; Receiving the parameter request for the target device carried with the first authentication data sent by the client and verifying the first authentication data, including: The proxy service module receives the parameter request for the target device carried with the first authentication data sent by the client; the proxy service module sends the parameter request to the media transfer service module, and the media transfer service module verifies the first authentication data; When the verification is successful, sending the parameter request to the target device based on the registration information, including: The media transfer service module sends the parameter request to the target device based on the registration information when the verification is successful; Receiving the device parameters and feeding back the device parameters to the client, including: The media transfer service module receives the device parameters; the media transfer service module sends the device parameters to the proxy service module; the proxy service module feeds back the device parameters to the client.

9. A device communication apparatus, characterized in that, Applied to a client in a device communication system, the system further includes: a communication platform and at least one communication device, and the communication platform has pre-registered the at least one communication device; the device includes: A page display module, configured to display the platform page of the communication platform, and when a click operation on a target device is detected, send a page request regarding the target device to the communication platform, so that the communication platform, based on the registration information of the at least one communication device, sends the page request to the target device and feeds back the page file sent by the target device to the client; wherein, the target device is any one of the at least one communication device; A file receiving module, configured to receive the page file and execute the page file to obtain the device page of the target device; An invocation module, configured to invoke the authentication function of the platform page through the device page, so that the platform page generates first authentication data based on the authentication function and feeds back the first authentication data to the device page; A request sending module, configured to send a parameter request regarding the target device carrying the first authentication data to the communication platform through the device page, so that when the communication platform successfully verifies the first authentication data, it sends the parameter request to the target device based on the registration information and feeds back the device parameters sent by the target device to the client; A parameter receiving module, configured to receive the device parameters and jump to the device page displaying the device parameters; 10. A device communication apparatus, characterized in that, A communication platform applied to a device communication system, the system further includes a client and at least one communication device, and the communication platform has pre-registered the at least one communication device; the device includes: A page request receiving module, configured to receive the page request regarding the target device sent by the client, and based on the registration information of the at least one communication device, send the page request to the target device, so that the target device determines a page file based on the page request and sends the page file to the communication platform; wherein, the page request is sent by the client when displaying the platform page of the communication platform and detecting a click operation on the target device; the target device is any one of the at least one communication device; A page file receiving module, configured to receive the page file and feed back the page file to the client, so that the client receives the page file and executes the page file to obtain the device page of the target device; A parameter request receiving module, configured to receive the parameter request regarding the target device carrying the first authentication data sent by the client, and verify the first authentication data; wherein, the parameter request is sent by the client through the device page after receiving the first authentication data fed back by the platform page, and the first authentication data is generated by the platform page based on the authentication function when the client, after obtaining the device page, invokes the authentication function of the platform page through the device page; A parameter sending module, configured to, when the verification is successful, send the parameter request to the target device based on the registration information, so that the target device determines device parameters based on the parameter request and feeds back the device parameters to the communication platform; A parameter feedback module, configured to receive the device parameters and feed back the device parameters to the client, so that the client jumps to the device page displaying the device parameters after receiving the device parameters.

11. An electronic device, characterized in that, The electronic device is installed with a client, and the electronic device includes a processor and a memory; The memory is used for storing computer programs; The processor is configured to, when executing the programs stored on the memory, implement the steps of the method according to any one of claims 1-3 or 4-8.

Images