CN111131522A

CN111131522A - Remote control method and system for terminal equipment

Info

Publication number: CN111131522A
Application number: CN202010035940.XA
Authority: CN
Inventors: 周清会; 刘成; 柳荣
Original assignee: Shanghai Manheng Digital Technology Co ltd
Current assignee: Shanghai Manheng Digital Technology Co ltd
Priority date: 2020-01-14
Filing date: 2020-01-14
Publication date: 2020-05-08

Abstract

The application relates to a remote control method and system for terminal equipment, and relates to a control technology. The method comprises the following steps: recording the client information into a server queue; a request server queue, which is used for inputting client information through a control terminal and acquiring a client IP list; sending control information to a client through a control end; and executing corresponding operation through the client according to the control information. According to the remote control method and system for the terminal device, the multicast is converted into the unicast through the starting protocol, the control operation is completed in sequence in a short time, one-key batch cross-network-segment remote control can be achieved, hardware cooperation is not needed, and user experience is comprehensively improved.

Description

Remote control method and system for terminal equipment

Technical Field

The present application relates to control technologies, and in particular, to a method and a system for remotely controlling a terminal device.

Background

With the development of internet application, remote control or sharing realized by a network is used as a new interaction mode, so that different users can interact with each other through different terminal devices. However, when a lot of devices are managed daily, a large number of devices are often required to be remotely controlled and managed, so that repetitive independent operations on a single device are reduced, and the burden of a device management worker is reduced.

At present, the existing remote control equipment is mainly manufactured by combining hardware, and has more functional limitations, for example, most of the existing remote control equipment needs an external network and the like. The power supply chronograph starts a power supply from the front-stage equipment to the rear-stage equipment in sequence, and when the power supply is closed, all kinds of electric equipment are closed from the rear stage to the front stage in sequence, so that all kinds of electric equipment are effectively managed and uniformly controlled. In some application scenarios, such as a college laboratory and other non-network environments, it is relatively complicated to implement one-key control of batch devices, and further, hardware devices such as a power supply timer need to be used in cooperation with the network segment.

Therefore, it is desirable to provide a method and a system for remote control of a terminal device, in which a start-up protocol is used to convert multicast into unicast, and control operations are sequentially completed in a short time, so that one-key batch cross-network-segment remote control can be realized, hardware cooperation is not required, and user experience is comprehensively improved.

Disclosure of Invention

According to a first aspect of some embodiments of the present application, there is provided a terminal device remote control method applied in a terminal (e.g., an electronic device, etc.), the method may include: recording the client information into a server queue; a request server queue, which is used for inputting client information through a control terminal and acquiring a client IP list; sending control information to a client through a control end; and executing corresponding operation through the client according to the control information.

In some embodiments, the control information sent to the client through the control end includes wake-up information and/or header information.

In some embodiments, the method may further comprise: according to the IP list, sequentially sending awakening information to the client through the control end; and sequentially starting the clients by using a WOL protocol according to the awakening information.

In some embodiments, the sequentially sending, by the control end, the wake-up information to the client further includes: and the control terminal sequentially sends the starting magic packets to the client according to the IP list.

In some embodiments, the method may further comprise: sending header information to the client through the control end by using UDP; and according to the header information, identifying a shutdown instruction through the client and executing shutdown.

In some embodiments, the identifying, by the client, the shutdown instruction further comprises: the client monitors UDP to acquire header information and identifies a shutdown instruction.

In some embodiments, the performing shutdown by the client further comprises: and the client executes the CMD command and executes the shutdown operation on the client.

In some embodiments, the entering of the client information through the control terminal further includes: and the control terminal requests the server queue and sequentially inputs the client information into the system.

In some embodiments, the obtaining, by the control end, the client IP list further includes: the client requests the server through the TCP to obtain the IP lists of all the clients.

According to a second aspect of some embodiments of the present application, there is provided a system comprising: a memory configured to store data and instructions; a processor in communication with the memory, wherein the processor, when executing instructions in the memory, is configured to: recording the client information into a server queue; a request server queue, which is used for inputting client information through a control terminal and acquiring a client IP list; sending control information to a client through a control end; and executing corresponding operation through the client according to the control information.

Therefore, according to the remote control method and system for the terminal device of some embodiments of the present application, the multicast is converted into the unicast through the boot protocol, and the control operation is sequentially completed in a short time, so that one-key batch cross-network-segment remote control can be realized, hardware cooperation is not required, and user experience is comprehensively improved.

Drawings

For a better understanding and appreciation of some embodiments of the present application, reference will now be made to the description of embodiments taken in conjunction with the accompanying drawings, in which like reference numerals designate corresponding parts in the figures.

Fig. 1 is an exemplary schematic diagram of a remote control system provided in accordance with some embodiments of the present application.

Fig. 2 is an exemplary flowchart of a terminal device remote control method provided according to some embodiments of the present application.

Fig. 3 is an exemplary flow chart of a specific terminal device remote control method provided according to some embodiments of the present application.

Detailed Description

The following description, with reference to the accompanying drawings, is provided to facilitate a comprehensive understanding of various embodiments of the application as defined by the claims and their equivalents. These embodiments include various specific details for ease of understanding, but these are to be considered exemplary only. Accordingly, those skilled in the art will appreciate that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present application. In addition, descriptions of well-known functions and constructions will be omitted herein for brevity and clarity.

The terms and phrases used in the following specification and claims are not to be limited to the literal meaning, but are merely for the clear and consistent understanding of the application. Accordingly, it will be appreciated by those skilled in the art that the description of the various embodiments of the present application is provided for illustration only and not for the purpose of limiting the application as defined by the appended claims and their equivalents.

The technical solutions in the embodiments of the present application will be described clearly and completely with reference to the accompanying drawings in some embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It is to be understood that the terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only, and is not intended to be limiting of the application. As used in the examples of this application and the appended claims, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. The expressions "first", "second", "the first" and "the second" are used for modifying the corresponding elements without regard to order or importance, and are used only for distinguishing one element from another element without limiting the corresponding elements.

A terminal according to some embodiments of the present application may be an electronic device, which may include one or a combination of several of a personal computer (PC, e.g., a tablet, a desktop, a notebook, a netbook, a PDA), a client device, a virtual reality device (VR), a renderer, a smartphone, a mobile phone, an e-book reader, a Portable Multimedia Player (PMP), an audio/video player (MP 3/MP 4), a camera, a wearable device, and the like. According to some embodiments of the present application, the wearable device may include an accessory type (e.g., watch, ring, bracelet, glasses, or Head Mounted Device (HMD)), an integrated type (e.g., electronic garment), a decorative type (e.g., skin pad, tattoo, or built-in electronic device), and the like, or a combination of several. In some embodiments of the present application, the electronic device may be flexible, not limited to the above devices, or may be a combination of one or more of the above devices. In this application, the term "user" may indicate a person using an electronic device or a device using an electronic device (e.g., an artificial intelligence electronic device).

The embodiment of the application provides a remote control method and system for terminal equipment. In order to facilitate understanding of the embodiments of the present application, the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

Fig. 1 is an exemplary schematic diagram of a remote control system provided in accordance with some embodiments of the present application. As shown in fig. 1, the remote control system 100 may include a network 110, a control end 120, a client 130, a server 140, and the like. Specifically, the control end 120 and the client 130 establish communication through a network, for example, the control end 120 and the client 130 may communicate in the same local area network (e.g., a network environment of the same router, etc.). Further, the control end 120 may be connected to the network 110 in a wired (e.g., network cable, etc.) or wireless manner, and the client 130 may establish a communication connection with the network 110 in a wired or wireless (e.g., WIFI, etc.) manner. In some embodiments, the client 130 may send request information to the control end 120, the server 140, and the like. Further, the control end 120 and the server 140 may feed back information to the client 130. Based on the feedback information, the client 130 may determine to enter the system and send the information to the server 140. In some embodiments, the control end 120 may send request information to the server 140 to obtain information sent by the client 130, and the like.

According to some embodiments of the present application, the control end 120 and the client 130 may be the same or different terminal devices, and the like. The terminal device may include, but is not limited to, a smart terminal, a mobile terminal, a computer, a rendering machine, and the like. In the teaching scenario, the control end 120 may comprise a teacher end, and the client 130 may comprise a student end, etc. In a conference scenario, the control peer 120 may comprise a host peer, the client 130 may comprise a report peer, and so on. In some embodiments, server 140 is one type of computer that has the advantages of running faster, being more heavily loaded, etc. than a normal computer, and the corresponding price is higher. In a network environment, a server may provide computing or application services to other clients (e.g., terminals such as PCs, smart phones, ATMs, and large devices such as transportation systems). The server has high-speed CPU computing capability, long-time reliable operation, strong I/O external data throughput capability and better expansibility. The services that the server may provide include, but are not limited to, the ability to undertake responding to service requests, undertake services, secure services, and the like. The server, as an electronic device, has an extremely complex internal structure, including an internal structure similar to that of a general computer, and the like, and the internal structure of the server may include a Central Processing Unit (CPU), a hard disk, a memory, a system bus, and the like, as an example.

In some embodiments of the present application, the remote control system 100 may omit one or more elements, or may further include one or more other elements. By way of example, the remote control system 100 may include a plurality of clients 130, such as a plurality of client computers, and the like. Also for example, the remote control system 100 may include a plurality of control terminals 120. As another example, the remote control system 100 may include a plurality of servers 140, and the like. The Network 110 may be any type of communication Network, which may include a computer Network (e.g., a Local Area Network (LAN) or Wide Area Network (WAN)), the internet and/or a telephone Network, etc., or a combination of several. In some embodiments, the network 110 may be other types of wireless communication networks. The wireless communication may include microwave communication and/or satellite communication, among others. The Wireless communication may include cellular communication, such as Global System for Mobile communications (GSM), Code Division Multiple Access (CDMA), third Generation Mobile communication (3G, The 3rd Generation communication), fourth Generation Mobile communication (4G), fifth Generation Mobile communication (5G), sixth Generation Mobile communication (6G), Long Term Evolution (LTE-a), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), Universal Mobile Telecommunications System (UMTS), Wireless Broadband (Broadband ), and The like, or a combination of several or more. In some embodiments, the client 130 may be other electronic devices with equivalent functional modules, and the electronic devices may include one or a combination of several of a virtual reality device (VR), a rendering machine, a personal computer (PC, such as a tablet computer, a desktop computer, a notebook, a netbook, a PDA), a smart phone, a mobile phone, an e-book reader, a Portable Multimedia Player (PMP), an audio/video player (MP 3/MP 4), a camera, and a wearable device.

In some embodiments, the WIFI may be other types of wireless communication technologies. According to some embodiments of the present application, the Wireless communication may include Wireless local Area Network (WiFi), Bluetooth Low Energy (BLE), ZigBee (ZigBee), Near Field Communication (NFC), magnetic security transmission, radio frequency and Body Area Network (BAN), or the like, or a combination of several. According to some embodiments of the present application, the wired communication may include a Global Navigation Satellite System (Global Navigation Satellite System), a Global Positioning System (GPS), a beidou Navigation Satellite System, galileo (european Global Satellite Navigation System), or the like. The wired communication may include a Universal Serial Bus (USB), a High-Definition multimedia interface (HDMI), a recommended Standard 232 (RS-232, recommended Standard 232), and/or Plain Old Telephone Service (POTS), or the like, or a combination of several.

It should be noted that the above description of the remote control system 100 is merely for convenience of description and is not intended to limit the scope of the present application. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the principles of the system, which may be combined in any manner or combined with other elements to form a subsystem for use in a field of application in which the method and system described above is practiced. Such variations are within the scope of the present application.

Fig. 2 is an exemplary flowchart of a terminal device remote control method provided according to some embodiments of the present application. As shown in fig. 2, the process 200 may be implemented by the remote control system 100. In some embodiments, the terminal device remote control method 200 may be initiated automatically or by command. The instructions may include system instructions, device instructions, user instructions, action instructions, and the like, or a combination of the several. At 201, client information is entered into a server queue. Operation 201 may be implemented by the client 130, server 140 of the remote control system 100. In some embodiments, the client 130 may send information to the server according to the HTTP protocol. Further, the client 130 information is entered into a Redis queue maintained by the server 140. The client information may include, but is not limited to, IP information, a Media Access Control Address (MAC Address), a machine user name, and the like. The Redis queue may include a list that records IP, MAC address, and current machine username, among other things.

At 202, a server queue is requested, client information is entered through a control terminal and a client IP list is obtained. Operation 202 may be implemented by the control end 120 of the remote control system 100, the server 140. In some embodiments, the control end 120 may request the server queue and, in turn, enter client 130 information into the system. And the information is sequentially input according to a first-in first-out principle. The system may include a Nginx service or the like that is started by a Linux server in a local area network. As an example, the client program before entry may be displayed in the list only when it is started, and when the client information is entered first and then the client IP list is obtained, the client may be displayed in the list without starting, and may send a boot instruction to the client in the list, and the like. In some embodiments, the control end 120 may request the server 140 through a transmission control protocol tcp (transmission control protocol) to obtain an IP list of all the clients. The TCP can be a connection-oriented, reliable transport layer communication protocol based on byte streams, and aims to adapt to a layered protocol hierarchy supporting multi-network application; reliable communication services are provided by means of TCP between pairs of processes in host computers connected to different but interconnected computer communication networks.

According to some embodiments of the present application, operation 201 and operation 202 of the process 200 are networking, and by means of power-on networking, remote control of subsequent batch devices such as one-key power-off and/or one-key power-on can be achieved.

At 203, control information is sent to the client through the control end. Operation 203 may be implemented by control end 120 of remote control system 100. In some embodiments, the control end 120 may send control information to the client 130. The control information may include wake-up information, header information, and the like.

At 204, corresponding operations are performed by the client according to the control information. Operation 204 may be implemented by client 130 of remote control system 100. In some embodiments, the client 130 may perform corresponding operations according to the control information sent by the control end 120. As an example, the client 130 may perform a corresponding booting operation according to the wake-up information. For another example, the client 130 may perform a corresponding shutdown operation according to the header information.

According to some embodiments of the present application, operation 203 of flow 200 may include sending wake up information or sending header information, or the like. Operation 204 of flow 200 may include starting the client based on the wake up information, or shutting down the client based on the header information, etc. As shown in fig. 3, fig. 3 is an exemplary flowchart of a specific terminal device remote control method provided according to some embodiments of the present application. The process 300 is a specific remote control method for a terminal device, and operations 301 to 302 are the same as operations 201 to 202 in the process 200, and are not described herein again.

In some embodiments, operation 302 may further proceed to operation 303, and at 303, the control end sequentially sends the wake-up information to the client according to the IP list. Operation 303 may be performed by the control terminal 120 of the remote control system 100. As an example, the control end 120 may sequentially send the wake-up information to the client according to the IP list. For example, the control end 120 may sequentially send a Magic Packet (Magic Packet) to the client 130 according to the IP list. The Magic Packet may be a wake-on-lan protocol, i.e., a remote wake-up Packet.

At 304, the clients are sequentially started using the WOL protocol according to the wake-up information. Operation 304 may be implemented by client 130 of remote control system 100. As an example, the client 130 may start sequentially according to the wake-up information and using a wol (wakeon lan) protocol. The WOL may be woken up for a local area network, and the WOL has set a network card, for example, when the terminal device is in a shutdown or sleep state, the WOL further implements remote control startup of the device by sending a specific data Packet (e.g., a Magic Packet) to the network card to instruct the network card to send a startup instruction to the motherboard. After the WOL in the network card is started, the client 130 may execute cold boot via the WOL protocol according to the magic packet sent by the control end.

In some embodiments, operation 302 may further proceed to operation 305, and at 305, the header information is sent to the client through the control end using UDP. Operation 305 may be implemented by control end 120 of remote control system 100. As an example, the control end 120 may transmit header information and the like to the client 130 using udp (user data program). The UDP may be a user datagram protocol and provides a way for applications to send encapsulated IP datagrams without establishing a connection. The header information may be a fixed 5-bit header of (instruction length + instruction content + content length), which exists in the first 5 fixed bits of the entire UDP message.

At 306, a shutdown instruction is recognized by the client and shutdown is performed according to the header information. Operation 306 may be implemented by client 130 of remote control system 100. As an example, the client 130 may recognize a shutdown instruction according to the header information and perform shutdown. For example, the client 130 may listen to UDP get header information to identify a shutdown instruction. Further, the client 130 may execute the CMD command to perform a shutdown operation on itself. The CMD can be a command prompt, and prompts a work prompt for command input in an operating system; command hints vary from one operating system environment to another. As an example, the client 130 may divide the received UDP information into an instruction (Control) and a content (TurnOff), and perform a shutdown operation.

It should be noted that, the

operations

305 and 306 may be executed sequentially or circularly, and the operations 306 may be executed first and then the operations 305 are executed, etc., which is not limited in this application, that is, the operations do not have a sequential order in the execution timing, and the above description of the operations of the flow 300 is only an exemplary description of the embodiments of the present application.

It should be noted that the above descriptions of the

processes

200 and 300 are only for convenience of description, and should not limit the present application to the scope of the illustrated embodiments. It will be understood by those skilled in the art that various modifications and changes in form and detail may be made in the functions implementing the above-described processes and operations based on the principles of the present system, in any combination of operations or in combination with other operations constituting sub-processes without departing from the principles. For example, the process 200 may specifically include operations such as sending wake-up information or header information. Such variations are within the scope of the present application.

It should be noted that, a general method for remotely controlling on/off in the prior art is a UDP Multicast (Multicast) protocol, and Multicast itself can only communicate in the same network segment. The remote control method converts multicast into Unicast (Unicast), and realizes cross-network-segment remote control on/off. The unicast may be a point-to-point connection between the client and the server. The point-to-point may receive a remote stream from the server for each client, sending a unicast stream only when the client makes a request.

In summary, according to the remote control method and system for the terminal device in the embodiments of the present application, the multicast is converted into the unicast through the boot protocol, and the control operation is sequentially completed in a short time, so that one-key batch cross-network-segment remote control can be realized, hardware cooperation is not required, and user experience is comprehensively improved.

It is to be noted that the above-described embodiments are merely examples, and the present application is not limited to such examples, but various changes may be made.

It should be noted that, in the present specification, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

Finally, it should be noted that the series of processes described above includes not only processes performed in time series in the order described herein, but also processes performed in parallel or individually, rather than in time series.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware associated with computer program instructions, and the program can be stored in a computer readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.

While the invention has been described with reference to a number of illustrative embodiments, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.

Claims

1. A remote control method for terminal equipment is characterized by comprising the following steps:

recording the client information into a server queue;

a request server queue, which is used for inputting client information through a control terminal and acquiring a client IP list;

sending control information to a client through a control end;

and executing corresponding operation through the client according to the control information.

2. The method according to claim 1, wherein the control information sent to the client through the control end comprises wake-up information and/or header information.

3. The method of claim 2, further comprising:

according to the IP list, sequentially sending awakening information to the client through the control end;

and sequentially starting the clients by using a WOL protocol according to the awakening information.

4. The method of claim 3, wherein the sending the wake-up information to the client in sequence by the control end further comprises:

and the control terminal sequentially sends the starting magic packets to the client according to the IP list.

5. The method of claim 2, further comprising:

sending header information to the client through the control end by using UDP;

and according to the header information, identifying a shutdown instruction through the client and executing shutdown.

6. The method of claim 5, wherein identifying, by the client, the shutdown instruction further comprises:

the client monitors UDP to acquire header information and identifies a shutdown instruction.

7. The method of claim 5, wherein the performing shutdown by the client further comprises:

and the client executes the CMD command and executes the shutdown operation on the client.

8. The method according to claim 1, wherein the entering of the client information through the control terminal further comprises:

and the control terminal requests the server queue and sequentially inputs the client information into the system.

9. The method of claim 1, wherein the obtaining, by the control end, the client IP list further comprises:

the client requests the server through the TCP to obtain the IP lists of all the clients.

10. A system, comprising:

a memory configured to store data and instructions;

a processor in communication with the memory, wherein the processor, when executing instructions in the memory, is configured to:

recording the client information into a server queue;

sending control information to a client through a control end;