WO2017080487A1 - 云桌面的调用方法及装置 - Google Patents

云桌面的调用方法及装置 Download PDF

Info

Publication number
WO2017080487A1
WO2017080487A1 PCT/CN2016/105321 CN2016105321W WO2017080487A1 WO 2017080487 A1 WO2017080487 A1 WO 2017080487A1 CN 2016105321 W CN2016105321 W CN 2016105321W WO 2017080487 A1 WO2017080487 A1 WO 2017080487A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
cloud desktop
specified
executable program
browser
Prior art date
Application number
PCT/CN2016/105321
Other languages
English (en)
French (fr)
Inventor
潘志刚
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017080487A1 publication Critical patent/WO2017080487A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/08—Protocols specially adapted for terminal emulation, e.g. Telnet

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and apparatus for invoking a cloud desktop.
  • Java platform Java 2 Platform, Enterprise Edition, J2EE for short
  • J2EE Java 2 Platform, Enterprise Edition
  • the applet is downloaded to the user's computer for execution, but only if the user is using a Java-enabled web browser. Since the applet is executed on the user's computer, its execution speed is not limited by the network bandwidth or modem access speed.
  • ActiveX is an open, integrated platform that provides developers, users and Internet (Web) manufacturers with a quick and easy way to create program integration and content over the Internet and intranet. With ActiveX, you can easily insert multimedia effects, interactive objects, and complex programs into your Web pages to create a high-quality Compact Disc Read-Only Memory (CD-ROM).
  • CD-ROM Compact Disc Read-Only Memory
  • the first method above can support cross-browser or even cross-platform, but because it is limited by browser security, it may cause the user to confirm each load, because the browser is Java-enabled.
  • a web browser thus requiring a Java Runtime Environment (JRE) to be installed on the user's operating system.
  • JRE Java Runtime Environment
  • the program under the window can be called quickly and easily, but it only supports the IE browser and cannot support other browsers.
  • the embodiment of the invention provides a method and a device for invoking a cloud desktop, so as to solve at least the problem that only the IE browser cannot support other browsers when the cloud desktop is invoked in the related art.
  • a method for invoking a cloud desktop including: receiving a trigger signal, where the trigger signal is used to trigger a server to establish a connection with a cloud desktop corresponding to the browser; and calling the registration with the cloud desktop
  • the specified executable program in the table specifies the protocol binding, and the connection parameter of the cloud desktop and the server is invoked to the server by specifying the executable program, wherein the specified protocol is a protocol supported by multiple browsers.
  • the method before the connection parameter of the cloud desktop and the server is invoked to the server, the method further includes: receiving The identity identifier of the cloud desktop and the server that is sent by the server.
  • the receiving server determines the connection parameters of the cloud desktop and the server when the IP address of the terminal where the received browser is the same as the IP address bound by the ID.
  • the specified executable program bound to the specified protocol in the registry of the cloud desktop is invoked, and the connection parameters of the cloud desktop and the server are invoked to the server by specifying the executable program, including: calling the registry of the cloud desktop
  • the specified executable program bound to the protocol is specified, and the connection parameter of the cloud desktop and the server is invoked in the cache of the server by specifying the executable program, wherein after the connection parameter of the cloud desktop and the server is invoked in the cache of the server, the connection parameter is Failed in the cache.
  • a method for invoking another cloud desktop including: receiving, by the server, first request information sent by a browser; wherein the first request information is used to instruct the browser to request the server The cloud desktop connection corresponding to the browser; the server returns the connection parameters of the cloud desktop and the server to the specified executable program bound to the specified protocol in the registry of the cloud desktop, wherein the specified protocol is supported by multiple browsers. protocol.
  • the method before the server returns the connection parameters of the cloud desktop and the server to the specified executable program bound to the specified protocol in the registry of the cloud desktop, the method further includes: the server sends the browser corresponding to the cloud desktop to the browser.
  • the identity ID of the identifier after the specified executable program is invoked by the specified protocol, the server receives the second request information sent by the specified executable program through the specified interface, where the second request information is used to indicate that the specified executable program requests the cloud desktop and The connection parameter of the server, and the second request information carries the identity ID.
  • the server returns the connection parameters of the cloud desktop and the server to the specified executable program bound to the specified protocol in the registry of the cloud desktop, including: the server determines the IP address of the terminal where the browser is received by the server. Whether the IP address bound to the ID is consistent; in the case of consistency, the server returns the connection parameters of the cloud desktop and the server in the cache of the server to the specified executable by specifying the interface.
  • the server after the server returns the connection parameters of the cloud desktop and the server to the specified executable program, the server sets the connection parameter of the cloud desktop and the server in the cache of the server to be invalid.
  • a cloud desktop calling device which is applied to a terminal, and includes: a first receiving module, configured to receive a trigger signal, where the trigger signal is used to trigger the server to correspond to the browser
  • the cloud desktop establishes a connection; the calling module is set to invoke a specified executable program bound to a specified protocol in the registry of the cloud desktop, and the connection parameter of the cloud desktop and the server is invoked to the server by specifying the executable program, wherein the specified protocol A protocol supported by multiple browsers.
  • the device further includes: a second receiving module, configured to receive an identity ID corresponding to the cloud desktop sent by the server; and a third receiving module, where the receiving server determines the IP of the terminal where the received browser is located The connection parameters of the returned cloud desktop and server when the address and the IP address bound to the ID are the same.
  • the calling module is further configured to invoke a specified executable program bound to a specified protocol in a registry of the cloud desktop, and invoke a connection parameter of the cloud desktop and the server to the cache of the server by specifying the executable program,
  • the connection parameter is invalidated in the cache after the connection parameters of the cloud desktop and the server are invoked in the cache of the server.
  • another cloud desktop calling device which is applied to a server, and includes: The first receiving module is configured to receive the first request information sent by the browser, where the first request information is used to instruct the browser to request the cloud desktop connection corresponding to the browser and the browser; the first sending module is set to The specified executable program of the specified protocol binding in the registry of the cloud desktop returns the connection parameters of the cloud desktop and the server, wherein the specified protocol is a protocol supported by multiple browsers.
  • the device further includes: a second sending module, configured to send an identifier ID corresponding to the cloud desktop to the browser; and the second receiving module is configured to: after the specified executable program is invoked by the specified protocol, The specified interface receives the second request information sent by the specified executable program, where the second request information is used to indicate that the specified executable program requests the connection parameter of the cloud desktop and the server, and the second request information carries the identity identifier.
  • a second sending module configured to send an identifier ID corresponding to the cloud desktop to the browser
  • the second receiving module is configured to: after the specified executable program is invoked by the specified protocol, The specified interface receives the second request information sent by the specified executable program, where the second request information is used to indicate that the specified executable program requests the connection parameter of the cloud desktop and the server, and the second request information carries the identity identifier.
  • the first sending module the determining unit is configured to determine whether the IP address of the terminal where the browser is received by the server is consistent with the IP address bound by the ID; and the sending unit is set to be consistent. Returns the connection parameters of the cloud desktop and server in the cache of the server to the specified executable by specifying the interface.
  • the device further includes: a setting module, configured to set the connection parameter of the cloud desktop and the server in the cache of the server to be invalid.
  • a storage medium is also provided.
  • the storage medium is configured to store program code for performing the following steps: receiving a trigger signal, wherein the trigger signal is used to trigger the server to establish a connection with a cloud desktop corresponding to the browser; and calling the specified protocol binding in the registry of the cloud desktop
  • the specified executable program calls the cloud desktop and server connection parameters to the server by specifying the executable program, wherein the specified protocol is a protocol supported by multiple browsers.
  • a storage medium is also provided.
  • the storage medium is configured to store program code for performing the following steps: the server receives the first request information sent by the browser, where the first request information is used to instruct the browser to request the cloud desktop connection corresponding to the browser and the browser.
  • the server returns the connection parameters of the cloud desktop and the server to the specified executable program bound to the specified protocol in the registry of the cloud desktop, wherein the specified protocol is a protocol supported by multiple browsers.
  • the specified executable program bound to the specified protocol in the registry of the cloud desktop is invoked, and then the connection parameters of the cloud desktop and the server are invoked to the server by specifying the executable program, wherein the specified protocol is more
  • the protocol supported by the browser which enables multiple browsers to support the call of the cloud desktop, and solves the problem that only the IE browser can support other browsers when the cloud desktop call in the related technology exists, thereby expanding the cloud.
  • FIG. 1 is a flowchart 1 of a method for invoking a cloud desktop according to an embodiment of the present invention
  • FIG. 2 is a second flowchart of a method for invoking a cloud desktop according to an embodiment of the present invention
  • FIG. 3 is a third flowchart of a method for invoking a cloud desktop according to an embodiment of the present invention.
  • FIG. 4 is a flowchart 4 of a method for calling a cloud desktop according to an embodiment of the present invention
  • FIG. 5 is a flowchart 5 of a method for invoking a cloud desktop according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of a manner of reminding a user in accordance with a preferred embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a method for invoking a cloud desktop according to a preferred embodiment of the present invention.
  • FIG. 8 is a structural block diagram 1 of a calling device of a cloud desktop according to an embodiment of the present invention.
  • FIG. 9 is a structural block diagram 2 of a calling device of a cloud desktop according to an embodiment of the present invention.
  • FIG. 10 is a structural block diagram 3 of a calling device of a cloud desktop according to an embodiment of the present invention.
  • FIG. 11 is a structural block diagram 4 of a calling device of a cloud desktop according to an embodiment of the present invention.
  • FIG. 12 is a structural block diagram 5 of a calling device of a cloud desktop according to an embodiment of the present invention.
  • FIG. 1 is a flowchart 1 of a method for calling a cloud desktop according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps:
  • Step S102 receiving a trigger signal, where the trigger signal is used to trigger the server to establish a connection with a cloud desktop corresponding to the browser;
  • step S104 the specified executable program bound to the specified protocol in the registry of the cloud desktop is invoked, and the connection parameters of the cloud desktop and the server are invoked to the server by specifying the executable program, wherein the specified protocol is supported by multiple browsers. Agreement.
  • the specified executable program bound to the specified protocol in the registry of the cloud desktop is invoked, and then the connection parameters of the cloud desktop and the server are invoked to the server by specifying the executable program, wherein the specified protocol is more
  • the protocol supported by the browser which enables multiple browsers to support the call of the cloud desktop, and solves the problem that only the IE browser can support other browsers when the cloud desktop call in the related technology exists, thereby expanding the cloud.
  • the foregoing specified protocol may be supported by multiple browsers, and the specified protocol may also be a customized protocol, that is, the user may customize the protocol as needed, but is not limited thereto.
  • the above browser can be chrome, Firefox, IE browser, etc., but not limited to, such as: 360 security browser, QQ browser, Sogou browser, etc.
  • the binding of the specified protocol to the specified executable program may be performed by binding the path of the specified protocol to the specified executable program.
  • the specified protocol is triggered, according to the specified protocol and the specified executable program.
  • the binding relationship between the paths, find the path of the specified executable program, and the executable program under the path is the specified executable program.
  • the connection parameters of the cloud desktop and the server are invoked to the server through the specified executable program.
  • the above method can be applied to a windows system, but is not limited thereto, such as a Linux system.
  • FIG. 2 is a flowchart 2 of a method for invoking a cloud desktop according to an embodiment of the present invention, as shown in FIG. 2, in the embodiment of the present invention, in order to protect the security of the cloud desktop information.
  • the method further includes:
  • Step S202 receiving an identity (Identity, referred to as ID) corresponding to the cloud desktop sent by the server;
  • step S204 the receiving server determines the connection parameters of the cloud desktop and the server when the network protocol (Internet Protocol, IP address) of the terminal where the received browser is the same as the IP address bound by the ID.
  • IP address Internet Protocol
  • the server does not directly return the connection parameters of the cloud desktop and the server, but the browser receives the identity ID returned by the server, and the ID is bound to the IP address of the terminal where the browser is located, so that even after being intercepted by the third party, Unusable, which increases the security of cloud desktop information.
  • the foregoing step S104 may be performed by: calling a specified executable program bound to a specified protocol in a registry of the cloud desktop, and calling the connection parameter of the cloud desktop and the server by specifying the executable program to the cache of the server.
  • the connection parameter is invalidated in the cache after the connection parameters of the cloud desktop and the server are invoked in the cache of the server. After the connection parameters of the cloud desktop and the server are obtained from the cache, the connection parameters of the cloud desktop and the server in the cache are invalid, thereby preventing the connection parameters of the cloud desktop and the server from being called multiple times.
  • the method may further include: starting the cloud desktop client according to the connection parameter of the invoked cloud desktop and the server.
  • the execution body of the method may be a browser, or may be another execution body such as a terminal, but is not limited thereto.
  • FIG. 3 is a flowchart 3 of a method for calling a cloud desktop according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps:
  • step S302 the server receives the first request information sent by the browser, where the first request information is used to instruct the browser to request the cloud desktop connection corresponding to the browser by the server;
  • Step S304 the server returns the connection parameters of the cloud desktop and the server to the specified executable program bound to the specified protocol in the registry of the cloud desktop, wherein the specified protocol is a protocol supported by multiple browsers.
  • the method for returning the connection parameters of the cloud desktop and the server to the specified executable program bound to the specified protocol in the registry of the cloud desktop is adopted, wherein the specified protocol is a protocol supported by multiple browsers, thereby Multiple
  • the browser can support the call of the cloud desktop, and solves the problem that only the IE browser can not support other browsers when the cloud desktop call in the related technology exists, thereby expanding the way the cloud desktop is started and the flexibility of the cloud desktop startup. Sex.
  • the foregoing specified protocol may be supported by multiple browsers, and the specified protocol may also be a customized protocol, that is, the user may customize the protocol as needed, but is not limited thereto.
  • the above browser may be chrome, Firefox, IE browser, etc., but is not limited thereto, such as: 360 security browser, QQ browser, Sogou browser, and the like.
  • the binding of the specified protocol to the specified executable program may be performed by binding the path specified by the specified protocol to the specified executable program.
  • the specified protocol may be triggered according to the specified protocol and the specified executable.
  • the binding relationship between the paths of the program, find the path of the specified executable program, and the executable program under the path is the specified executable program.
  • the server returns the connection parameters of the cloud desktop and the server to the specified executable.
  • the above method can be applied to a windows system, but is not limited thereto, such as a Linux system.
  • FIG. 4 is a flowchart 4 of the method for calling the cloud desktop according to the embodiment of the present invention, as shown in FIG. Before the step S304, the method further includes:
  • Step S402 the server sends an identity ID corresponding to the cloud desktop to the browser.
  • Step S404 after the specified executable program is invoked by the specified protocol, the server receives the second request information sent by the specified executable program by using the specified interface, where the second request information is used to indicate that the specified executable program requests the cloud desktop and the server.
  • the connection parameter carries the identity ID in the second request information.
  • step S304 may include:
  • Step S406 the server determines whether the IP address of the terminal where the browser is received by the server is consistent with the IP address bound by the ID;
  • Step S408 in the case of consistency, the server returns the connection parameters of the cloud desktop and the server in the cache of the server to the specified executable by specifying the interface.
  • the server does not directly return the connection parameters of the cloud desktop and the server, but returns an identity ID, which is bound to the IP address of the terminal where the browser is located, and the IP address received by the server is bound to the ID.
  • the IP address is compared, the connection parameters of the cloud desktop and the server in the cache of the server are returned in a consistent manner, so that even after being intercepted by the third party, the connection cannot be used, thereby increasing the security of the cloud desktop information.
  • FIG. 5 is a flowchart of a method for invoking a cloud desktop according to an embodiment of the present invention. As shown in FIG. 5, after the step S304, the method further includes:
  • Step S502 the server sets the connection parameter of the cloud desktop and the server in the cache of the server to be invalid.
  • connection parameters of the cloud desktop and the server are obtained from the cache, the connection parameters of the cloud desktop and the server in the cache are set to be invalid, and the connection parameters of the cloud desktop and the server can be prevented from being called multiple times.
  • the invention provides a preferred method for supporting a cloud desktop client call by a multi-browser under windows, comprising the following steps:
  • Step 1 When the client is installed, a custom protocol (equivalent to the specified protocol in the embodiment shown in FIG. 1) is written in the registry, and the corresponding client program is bound (corresponding to the embodiment shown in FIG. 1) Specifies the executable program) an absolute path (corresponding to the path of the specified executable program in the embodiment shown in Figure 1 above);
  • Step 2 The server does not directly return the connection parameter, and invokes the windows client through the custom protocol to obtain the corresponding connection parameter to the server (corresponding to the connection parameters of the cloud desktop and the server in the embodiment shown in FIG. 1);
  • Step 3 According to the response message body returned by the server, start a real cloud desktop client, and set parameters related to the corresponding cloud desktop.
  • the preferred embodiment can behave in the following manner:
  • Step S1 adding a custom protocol (corresponding to the specified protocol of the embodiment shown in FIG. 1) in HKEY_CLASSES_ROOT, and saving the following content, the suffix is reg:
  • command (command) key value is set to "C: ⁇ Program Files ⁇ A ⁇ startclient.exe ⁇ ”"%1", as long as the identifier "%1" is included, the application can The path of the custom protocol gets the corresponding parameters. It should be noted that A here is used to identify the custom protocol in the preferred embodiment.
  • step S2 the server returns a connection parameter browser connected to the cloud desktop, and the browser invokes a startup client (startclient.exe) program in a form of a custom protocol (equivalent to the specified executable program in the embodiment shown in FIG. 1).
  • startclient.exe a startup client
  • the start of the virtual cloud desktop launcher is set by the startclient.exe program and the corresponding cloud desktop parameters (ip, port, cloud desktop startup policy, etc.) are set.
  • FIG. 7 is a schematic diagram of a method for calling the cloud desktop according to a preferred embodiment of the present invention. As shown in FIG. 7, the above preferred method may be:
  • Step S702 the browser requests the server to connect with the cloud desktop
  • Step S704 the server does not directly return the connection parameter, but returns a unique identifier ID, and the corresponding map (Map) object is saved in the server.
  • the key of the Map object is the ID, and the value is the cloud desktop.
  • the connection object in order to prevent the ID from being acquired by the third party, the cloud desktop object bound by the ID needs to be bound to the IP of the terminal where the browser is located; (corresponding to step S402 in the embodiment shown in FIG. 4);
  • Step S706, the startclient.exe program is called by the custom protocol A;
  • Step S708 the cloud interface connection parameter is requested by the interface agreed by the server, and the ID attribute is carried in the request; (corresponding to step S404 in the embodiment shown in FIG. 4);
  • step S710 the server determines whether the IP address of the received browser (ie, the requester IP) is consistent with the IP bound to the ID (corresponding to step S406 in the embodiment shown in FIG. 4), and returns an error message if the inconsistency is inconsistent. Otherwise, the corresponding cloud desktop connection parameter information is returned (corresponding to step S408 in the embodiment shown in FIG. 4), and after the connection parameter is obtained from the cache through the interface, the data in the cache is invalid (corresponding to FIG. 5). Step S502) in the embodiment, preventing the cloud desktop connection parameter from being called multiple times;
  • step S712 the startclient.exe program calls the cloud desktop client and passes the startup parameters.
  • Multi-browser support Chrome, FireFox, IE all support custom protocol mode, 360 security browser, QQ browser, Sogou browser because the internal use of IE and chrome dual-core, so the measured are also supported; 2. Security. Even if the browser displays the content of the protocol to the user, it is not understandable to the user; in addition, since the ID is bound to the IP, it cannot be used after being intercepted by the third party.
  • the technical solution of the present invention which is essential or contributes to the prior art, can be embodied in the form of a software product stored in a storage medium such as a read only memory/random memory ( Read Only Memory/Random Access Memory (ROM/RAM), disk, CD-ROM includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform various implementations of the present invention.
  • a terminal device which may be a mobile phone, a computer, a server, or a network device, etc.
  • a cloud desktop calling device is also provided, which is used to implement the foregoing embodiments and preferred embodiments, and has not been described again.
  • the term “module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 8 is a structural block diagram of a calling device of a cloud desktop according to an embodiment of the present invention. As shown in FIG. 8, the device is applied to a terminal, and includes:
  • the first receiving module 82 is configured to receive a trigger signal, where the trigger signal is used to trigger the server to establish a connection with a cloud desktop corresponding to the browser;
  • the calling module 84 is connected to the first receiving module 82, and is configured to invoke a specified executable program bound to a specified protocol in a registry of the cloud desktop, and invokes a connection parameter of the cloud desktop and the server to the server by specifying the executable program, wherein
  • the specified protocol is a protocol supported by multiple browsers.
  • the specified executable program bound to the specified protocol in the registry of the cloud desktop is called by the calling module 84, and then the connection parameter of the cloud desktop and the server is invoked to the server by specifying the executable program, wherein the protocol is specified.
  • the cloud desktop call in the related technology only supports the problem that the IE browser cannot support other browsers, and thus expands. The way cloud desktops are launched and the flexibility of cloud desktop startup.
  • the foregoing specified protocol may be supported by multiple browsers, and the specified protocol may also be a customized protocol, that is, the user may customize the protocol as needed, but is not limited thereto.
  • the above browser may be chrome, Firefox, IE browser, etc., but is not limited thereto, such as: 360 security browser, QQ browser, Sogou browser, and the like.
  • the binding of the specified protocol to the specified executable program may be represented by the path binding of the specified protocol to the specified executable program.
  • the first receiving module 82 receives the trigger signal
  • the specified protocol is triggered, and the calling module 84 is used according to the data.
  • the binding relationship between the specified protocol and the path of the specified executable program finds the path of the specified executable program, and the executable program under the path is the specified executable program.
  • the connection parameters of the cloud desktop and the server are invoked to the server through the specified executable program.
  • the above terminal can be installed in the windows system, but is not limited thereto, such as the linux system, that is, the above device can work in the windows system.
  • FIG. 9 is a structural block diagram 2 of the calling device of the cloud desktop according to the embodiment of the present invention, as shown in FIG.
  • the device further includes:
  • the second receiving module 92 is configured to receive an identity ID corresponding to the cloud desktop sent by the server;
  • the third receiving module 94 is connected to the second receiving template 92, and is configured to receive the connection between the returned cloud desktop and the server when the receiving server determines that the IP address of the terminal where the received browser is the same as the IP address bound by the ID. parameter.
  • the server does not directly return the connection parameters of the cloud desktop and the server, but receives the identity ID returned by the server through the second receiving module 92, and the ID is bound to the IP address of the terminal where the browser is located, so that even if it is After the three parties intercepted, they could not be used, which increased the security of cloud desktop information.
  • the calling module 84 is further configured to invoke a specified executable program bound to a specified protocol in a registry of the cloud desktop, and invoke the connection between the cloud desktop and the server by specifying the executable program to the cache of the server.
  • the foregoing apparatus may further include a startup module, configured to connect according to the invoked cloud desktop and the server. Connect the parameters to start the above cloud desktop client.
  • FIG. 10 is a structural block diagram 3 of a cloud desktop calling device according to an embodiment of the present invention. As shown in FIG. 10, the device is applied to a server, and the device is applied to the server. include:
  • the first receiving module 1002 is configured to receive the first request information sent by the browser, where the first request information is used to instruct the browser to request the cloud desktop connection corresponding to the browser by the server;
  • the first sending module 1004 is connected to the first receiving module 1002, and is configured to return a connection parameter of the cloud desktop and the server to the specified executable program bound to the specified protocol in the registry of the cloud desktop, where the specified protocol is multiple A protocol supported by the browser.
  • the first sending module 1004 is used to return the connection parameters of the cloud desktop and the server to the specified executable program bound to the specified protocol in the registry of the cloud desktop, wherein the specified protocol is supported by multiple browsers.
  • the protocol enables multiple browsers to support the call of the cloud desktop.
  • the cloud desktop call in the related technology only supports the problem that the IE browser cannot support other browsers, thereby expanding the way the cloud desktop is started and improved. The flexibility of cloud desktop startup.
  • the foregoing specified protocol may be supported by multiple browsers, and the specified protocol may also be a customized protocol, that is, the user may customize the protocol as needed, but is not limited thereto.
  • the above browser may be chrome, Firefox, IE browser, etc., but is not limited thereto, such as: 360 security browser, QQ browser, Sogou browser, and the like.
  • the binding of the specified protocol to the specified executable program may be performed by binding the path specified by the specified protocol to the specified executable program.
  • the specified protocol may be triggered according to the specified protocol and the specified executable.
  • the binding relationship between the paths of the program, find the path of the specified executable program, and the executable program under the path is the specified executable program.
  • the server returns the connection parameters of the cloud desktop and the server to the specified executable.
  • the above method can be applied to a windows system, but is not limited thereto, such as a Linux system.
  • FIG. 11 is a structural block diagram 4 of the calling device of the cloud desktop according to the embodiment of the present invention, as shown in FIG.
  • the above apparatus further includes:
  • the second sending module 1102 is configured to send an identifier ID corresponding to the cloud desktop to the browser;
  • the second receiving module 1104 is connected to the second sending module 1102, and is configured to receive the second request information sent by the specified executable program through the designated interface after the specified executable program is called by the specified protocol, where the second request information is used by the second request information. Instructing the specified executable program to request the connection parameters of the cloud desktop and the server, and the second request information carries the identity ID.
  • the first sending module 1004 may include: a determining unit 1106, configured to determine whether the IP address of the terminal where the browser is received by the server is consistent with the IP address bound by the ID; the sending unit 1108, and the foregoing The judging unit 1106 is connected, and is configured to return, to the specified executable program, the connection parameters of the cloud desktop and the server in the cache of the server by the specified interface.
  • the server does not directly return the connection parameters of the cloud desktop and the server, but returns an identity.
  • ID which is bound to the IP address of the terminal where the browser is located.
  • the IP address received by the server is compared with the IP address bound by the ID.
  • the cloud desktop and the server in the cache of the server are returned. Connection parameters, so that even after being intercepted by a third party, they can not be used, thereby increasing the security of cloud desktop information.
  • FIG. 12 is a structural block diagram 5 of a calling device of a cloud desktop according to an embodiment of the present invention. As shown in FIG. 12, the device further includes:
  • the setting module 1202 is connected to the first sending module 1004, and is configured to set the connection parameter of the cloud desktop and the server in the cache of the server to be invalid.
  • the setting module 1202 sets the connection parameter of the cloud desktop and the server in the cache to be invalid, and can prevent the connection parameters of the cloud desktop and the server from being called multiple times.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above technical solution provided by the embodiment of the present invention by calling a specified executable program bound to a specified protocol in a registry of the cloud desktop, and then calling the connection parameter of the cloud desktop and the server to the server by specifying the executable program, where
  • the specified protocol is a protocol supported by multiple browsers, which enables multiple browsers to support the call of the cloud desktop, and solves the problem that only the IE browser cannot support other browsers when the cloud desktop call in the related art exists. This expands the way cloud desktops are launched and increases the flexibility of cloud desktop launches.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本发明提供了一种云桌面的调用方法及装置，其中，该方法包括：接收触发信号，其中，触发信号用于触发服务端与浏览器对应的云桌面建立连接；调用与云桌面的注册表中指定协议绑定的指定可执行程序，通过指定可执行程序向服务端调用云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议。通过本发明，解决了相关技术中的云桌面调用时存在的只支持IE浏览器无法支持其他浏览器的问题，进而扩展了云桌面启动的方式以及提高了云桌面启动的灵活性。

Description

云桌面的调用方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种云桌面的调用方法及装置。
背景技术
Java平台(Java 2 Platform，Enterprise Edition，简称J2EE)的应用开发，需要调用本地客户端，而相关技术中，主要有如下两种方式：
第一种，使用java applet技术，小应用程序(Applet)被下载到用户的计算机上执行，但前提是用户使用的是支持Java的网络浏览器。由于Applet是在用户的计算机上执行的，所以它的执行速度不受网络带宽或者调制解调器(Modem)存取速度的限制。
第二种，只支持网络探索者(Internet Explorer，简称IE)浏览器，使用IE浏览器特有的ActiveX技术。ActiveX是一个开放的集成平台，为开发人员、用户和互联网(Web)生产商提供了一个快速而简便的在互联网(Internet)和内联网(Intranet)创建程序集成和内容的方法。使用ActiveX,可轻松方便的在Web页中插入多媒体效果、交互式对象、以及复杂程序，创建用户体验相当的高质量多媒体只读光盘(Compact Disc Read-Only Memory，简称CD-ROM)。
但是，对于上述第一种方式可以支持跨浏览器，甚至跨平台，但是由于其会受到浏览器安全的限制，因而可能导致每次加载都需要用户进行确认，由于采用的浏览器为支持Java的网络浏览器，因而需要在用户的操作系统上安装Java运行环境(Java Runtime Environment，简称JRE)。而对于第二种方式能够方便快捷地调用窗口(windows)下的程序，但是，其仅仅支持IE浏览器，无法支持其他浏览器。
针对相关技术中的云桌面调用时存在的只支持IE浏览器无法支持其他浏览器的问题，目前尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种云桌面的调用方法及装置，以至少解决相关技术中的云桌面调用时存在的只支持IE浏览器无法支持其他浏览器的问题。
根据本发明实施例的一个方面，提供了一种云桌面的调用方法，包括：接收触发信号，其中，触发信号用于触发服务端与浏览器对应的云桌面建立连接；调用与云桌面的注册表中指定协议绑定的指定可执行程序，通过指定可执行程序向服务端调用云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议。
在本发明实施例中，向服务端调用云桌面与服务端的连接参数之前，方法还包括：接收 服务端发送的与云桌面对应的身份标识ID；接收服务端在确定接收的浏览器所在终端的IP地址与ID绑定的IP地址一致的情况下，返回的云桌面与服务端的连接参数。
在本发明实施例中，调用与云桌面的注册表中指定协议绑定的指定可执行程序，通过指定可执行程序向服务端调用云桌面与服务端的连接参数包括：调用与云桌面的注册表中指定协议绑定的指定可执行程序，通过指定可执行程序向服务端的缓存中调用云桌面与服务端的连接参数，其中，在向服务端的缓存中调用云桌面与服务端的连接参数之后，连接参数在缓存中失效。
根据本发明实施例的另一方面，提供了另一种云桌面的调用方法，包括：服务端接收浏览器发送的第一请求信息；其中，第一请求信息，用于指示浏览器请求服务端与浏览器对应的云桌面连接；服务端向与云桌面的注册表中指定协议绑定的指定可执行程序返回云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议。
在本发明实施例中，服务端向与云桌面的注册表中指定协议绑定的指定可执行程序返回云桌面与服务端的连接参数之前，方法还包括：服务端向浏览器发送与云桌面对应的身份标识ID；在指定可执行程序被指定协议调用后，服务端通过指定接口接收指定可执行程序发送的第二请求信息，其中，第二请求信息用于指示指定可执行程序请求云桌面与服务端的连接参数，第二请求信息中携带身份标识ID。
在本发明实施例中，服务端向与云桌面的注册表中指定协议绑定的指定可执行程序返回云桌面与服务端的连接参数包括：服务端判断服务端接收的浏览器所在终端的IP地址是否与ID绑定的IP地址一致；在一致的情况下，服务端通过指定接口，向指定可执行程序返回服务端的缓存中的云桌面与服务端的连接参数。
在本发明实施例中，在服务端向指定可执行程序返回云桌面与服务端的连接参数之后，服务端将服务端的缓存中的云桌面与服务端的连接参数设置为失效。
根据本发明实施例的另一方面，提供了一种云桌面的调用装置，应用于终端，包括：第一接收模块，设置为接收触发信号，其中，触发信号用于触发服务端与浏览器对应的云桌面建立连接；调用模块，设置为调用与云桌面的注册表中指定协议绑定的指定可执行程序，通过指定可执行程序向服务端调用云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议。
在本发明实施例中，装置还包括：第二接收模块，设置为接收服务端发送的与云桌面对应的身份标识ID；第三接收模块，接收服务端在确定接收的浏览器所在终端的IP地址与ID绑定的IP地址一致的情况下，返回的云桌面与服务端的连接参数。
在本发明实施例中，调用模块，还设置为调用与云桌面的注册表中指定协议绑定的指定可执行程序，通过指定可执行程序向服务端的缓存中调用云桌面与服务端的连接参数，其中，在向服务端的缓存中调用云桌面与服务端的连接参数之后，连接参数在缓存中失效。
根据本发明实施例的另一方面，提供了另一种云桌面的调用装置，应用于服务端，包括： 第一接收模块，设置为接收浏览器发送的第一请求信息；其中，第一请求信息，用于指示浏览器请求服务端与浏览器对应的云桌面连接；第一发送模块，设置为向与云桌面的注册表中指定协议绑定的指定可执行程序返回云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议。
在本发明实施例中，装置还包括：第二发送模块，设置为向浏览器发送与云桌面对应的身份标识ID；第二接收模块，设置为在指定可执行程序被指定协议调用后，通过指定接口接收指定可执行程序发送的第二请求信息，其中，第二请求信息用于指示指定可执行程序请求云桌面与服务端的连接参数，第二请求信息中携带身份标识ID。
在本发明实施例中，第一发送模块：判断单元，设置为判断服务端接收的浏览器所在终端的IP地址是否与ID绑定的IP地址一致；发送单元，设置为在一致的情况下，通过指定接口，向指定可执行程序返回服务端的缓存中的云桌面与服务端的连接参数。
在本发明实施例中，装置还包括：设置模块，设置为将服务端的缓存中的云桌面与服务端的连接参数设置为失效。
根据本发明的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：接收触发信号，其中，触发信号用于触发服务端与浏览器对应的云桌面建立连接；调用与云桌面的注册表中指定协议绑定的指定可执行程序，通过指定可执行程序向服务端调用云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议。
根据本发明的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：服务端接收浏览器发送的第一请求信息；其中，第一请求信息，用于指示浏览器请求服务端与浏览器对应的云桌面连接；服务端向与云桌面的注册表中指定协议绑定的指定可执行程序返回云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议。
通过本发明实施例，通过调用与云桌面的注册表中指定协议绑定的指定可执行程序，然后通过指定可执行程序向服务端调用云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议，进而使得多个浏览器能够支持云桌面的调用，解决了相关技术中的云桌面调用时存在的只支持IE浏览器无法支持其他浏览器的问题，进而扩展了云桌面启动的方式以及提高了云桌面启动的灵活性。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的云桌面的调用方法的流程图一；
图2是根据本发明实施例的云桌面的调用方法的流程图二；
图3是根据本发明实施例的云桌面的调用方法的流程图三；
图4是根据本发明实施例的云桌面的调用方法的流程图四；
图5是根据本发明实施例的云桌面的调用方法的流程图五；
图6是根据本发明优选实施例的提醒用户的方式的示意图；
图7是根据本发明优选实施例的云桌面的调用方法的示意图；
图8是根据本发明实施例的云桌面的调用装置的结构框图一；
图9是根据本发明实施例的云桌面的调用装置的结构框图二；
图10是根据本发明实施例的云桌面的调用装置的结构框图三；
图11是根据本发明实施例的云桌面的调用装置的结构框图四；
图12是根据本发明实施例的云桌面的调用装置的结构框图五。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种云桌面的调用方法，图1是根据本发明实施例的云桌面的调用方法的流程图一，如图1所示，该流程包括如下步骤：
步骤S102，接收触发信号，其中，触发信号用于触发服务端与浏览器对应的云桌面建立连接；
步骤S104，调用与云桌面的注册表中指定协议绑定的指定可执行程序，通过指定可执行程序向服务端调用云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议。
通过上述步骤，采用调用与云桌面的注册表中指定协议绑定的指定可执行程序，然后通过指定可执行程序向服务端调用云桌面与服务端的连接参数的方式，其中，指定协议为被多个浏览器所支持的协议，进而使得多个浏览器能够支持云桌面的调用，解决了相关技术中的云桌面调用时存在的只支持IE浏览器无法支持其他浏览器的问题，进而扩展了云桌面启动的方式以及提高了云桌面启动的灵活性。
需要说明的是，上述指定协议可以被多个浏览器所支持，上述指定协议也可以是自定义的协议，即用户可以根据需要对协议进行自定义，但并不限于此。上述浏览器可以是chrome、 Firefox、IE浏览器等，但不限于此，比如：360安全浏览器，QQ浏览器，搜狗浏览器等。
上述指定协议与指定可执行程序绑定可以表现为上述指定协议与指定可执行程序的路径绑定，当接收到上述触发信号后，会触发上述指定协议，根据该指定协议与指定可执行程序的路径之间的绑定关系，找到该指定可执行程序的路径，在该路径下的可执行程序即为指定可执行程序。通过该指定可执行程序向服务端调用云桌面与服务端的连接参数。
上述方法可以应用于windows系统中，但不限于此，比如linux系统。
为了保护云桌面信息的安全，避免云桌面的相关信息的泄露，在本发明实施例中，图2是根据本发明实施例的云桌面的调用方法的流程图二，如图2所示，在步骤S104之前，上述方法还包括：
步骤S202，接收服务端发送的与云桌面对应的身份标识(Identity，简称ID)；
步骤S204，接收服务端在确定接收的浏览器所在终端的网络协议(Internet Protocol，简称IP)地址与ID绑定的IP地址一致的情况下，返回的云桌面与服务端的连接参数。
通过上述步骤，服务器不直接返回云桌面与服务端的连接参数，而是浏览器接收服务器返回的身份标识ID，该ID与浏览器所在终端的IP地址绑定，这样即使被第三方截取后，也无法使用，进而增加了云桌面信息的安全性。
在本发明实施例中，上述步骤S104可以表现为：调用与云桌面的注册表中指定协议绑定的指定可执行程序，通过指定可执行程序向服务端的缓存中调用云桌面与服务端的连接参数，其中，在向服务端的缓存中调用云桌面与服务端的连接参数之后，连接参数在缓存中失效。通过在从缓存中获取到云桌面与服务端的连接参数之后，缓存中的云桌面与服务端的连接参数则失效，进而能够防止该云桌面与服务端的连接参数被多次调用。
在本发明一个可选的实施例中，在步骤S104之后，上述方法还可以包括：根据调用的云桌面与服务端的连接参数，启动上述云桌面客户端。
需要说明的是，在本发明实施例中，该方法的执行主体可以是浏览器，也可以是其他的执行主体比如终端，但并不限于此。
在本实施例中提供了另一种云桌面的调用方法，图3是根据本发明实施例的云桌面的调用方法的流程图三，如图3所示，该流程包括如下步骤：
步骤S302，服务端接收浏览器发送的第一请求信息；其中，第一请求信息，用于指示浏览器请求服务端与浏览器对应的云桌面连接；
步骤S304，服务端向与云桌面的注册表中指定协议绑定的指定可执行程序返回云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议。
通过上述步骤，采用向与云桌面的注册表中指定协议绑定的指定可执行程序返回云桌面与服务端的连接参数的方式，其中，指定协议为被多个浏览器所支持的协议，进而使得多个 浏览器能够支持云桌面的调用，解决了相关技术中的云桌面调用时存在的只支持IE浏览器无法支持其他浏览器的问题，进而扩展了云桌面启动的方式以及提高了云桌面启动的灵活性。
需要说明的是，上述指定协议可以被多个浏览器所支持，上述指定协议也可以是自定义的协议，即用户可以根据需要对协议进行自定义，但并不限于此。上述浏览器可以是chrome、Firefox、IE浏览器等，但不限于此，比如：360安全浏览器，QQ浏览器，搜狗浏览器等。
上述指定协议与指定可执行程序绑定可以表现为上述指定协议与指定可执行程序的路径绑定，当浏览器接收到上述触发信号后，会触发上述指定协议，根据该指定协议与指定可执行程序的路径之间的绑定关系，找到该指定可执行程序的路径，在该路径下的可执行程序即为指定可执行程序。服务端则将云桌面与服务端的连接参数返回给该指定可执行程序。
上述方法可以应用于windows系统中，但不限于此，比如linux系统。
为了保护云桌面信息的安全，避免云桌面的相关信息的泄露，在本发明实施例中，图4是根据本发明实施例的云桌面的调用方法的流程图四，如图4所示，在步骤S304之前，上述方法还包括：
步骤S402，服务端向浏览器发送与云桌面对应的身份标识ID；
步骤S404，在指定可执行程序被指定协议调用后，服务端通过指定接口接收指定可执行程序发送的第二请求信息，其中，第二请求信息用于指示指定可执行程序请求云桌面与服务端的连接参数，第二请求信息中携带身份标识ID。
在本发明的一个实施例中，上述步骤S304可以包括：
步骤S406，服务端判断服务端接收的浏览器所在终端的IP地址是否与ID绑定的IP地址一致；
步骤S408，在一致的情况下，服务端通过指定接口，向指定可执行程序返回服务端的缓存中的云桌面与服务端的连接参数。
通过上述步骤，服务器不直接返回云桌面与服务端的连接参数，而是返回一个身份标识ID，该ID与浏览器所在终端的IP地址绑定，通过服务端接收到的IP地址与ID绑定的IP地址比较，在一致的情况下，才返回服务端的缓存中的云桌面与服务端的连接参数，这样即使被第三方截取后，也无法使用，进而增加了云桌面信息的安全性。
在本发明的一个实施例中，图5是根据本发明实施例的云桌面的调用方法的流程图五，如图5所示，在步骤S304之后，上述方法还包括：
步骤S502，服务端将服务端的缓存中的云桌面与服务端的连接参数设置为失效。
通过在从缓存中获取到云桌面与服务端的连接参数之后，将缓存中的云桌面与服务端的连接参数设置为失效，能够防止该云桌面与服务端的连接参数被多次调用。
为了更好的理解本发明，以下结合优选的实施例对本发明作进一步地解释。
本发明提供了一种优选的windows下多浏览器支持云桌面客户端调用的方法，包括以下步骤：
步骤1，客户端安装时，在注册表中写入自定义协议(相当于图1所示实施例中的指定协议)，以及绑定相应的客户端程序(相当于图1所示实施例中的指定可执行程序)绝对路径(相当于上述图1所示实施例中的指定可执行程序的路径)；
步骤2，服务端不直接返回连接参数，通过自定义协议调用windows客户端，使其到服务端获取对应的连接参数(相当于图1所示实施例中的云桌面与服务端的连接参数)；
步骤3，根据服务端返回的响应消息体，启动真正云桌面客户端，并设置传入对应的云桌面相关参数。
具体地，该优选实施例可以表现为以下方式：
步骤S1，在HKEY_CLASSES_ROOT中添加自定义协议(相当于图1所示实施例的指定协议)，保存下面的内容，后缀名为reg：
窗口注册编辑版本(Windows Registry Editor Version)5.00
[HKEY_CLASSES_ROOT\A]
"URL Protocol"＝""
[HKEY_CLASSES_ROOT\A\shell]
[HKEY_CLASSES_ROOT\A\shell\open]
[HKEY_CLASSES_ROOT\A\shell\open\command]
@＝"\"C:\\Program Files\\A\\startclient.exe\"％1"
[HKEY_CLASSES_ROOT\A\URL Protocol]
需要说明的是，把命令(command)键值设置为"C:\\Program Files\\A\\startclient.exe\""％1"，只要当中包含标示符“％1”，应用程序可以根据自定义协议的路径获取对应的参数。需要说明的是，此处A用于标识本优选实施例中的自定义协议。
步骤S2，服务端返回连接云桌面的连接参数浏览器，浏览器会通过自定义协议的形式，调用启动客户端(startclient.exe)程序(相当于图1所示实施例的指定可执行程序)，由startclient.exe程序完成调用真正云桌面启动程序并设置对应云桌面参数(ip、端口、云桌面启动策略等)。
为了保证安全性，在浏览器(谷歌(Chrome)、火狐(FireFox)、IE)中调用外部协议时，会将完整连接参数展示给用户，可采用图6所示的方式提醒用户将会执行可能的非安全操作。
为了保护云桌面信息的安全，避免云桌面的相关信息泄漏，图7是根据本发明优选实施例的云桌面的调用方法的示意图，如图7所示，上述优选的方法可以表现为：
步骤S702，浏览器请求服务器与云桌面连接；
步骤S704，服务端不直接返回连接参数，而是返回一个能唯一区分的身份标识ID，服务器里面保存对应的映射(Map)对象，Map对象的key即为该ID，值(value)为云桌面连接对象，为了防止ID被第三方获取，此ID绑定的云桌面对象需要绑定该浏览器所在终端的IP；(相当于图4所示实施例中的步骤S402)；
步骤S706，startclient.exe程序被自定义协议A调用；
步骤S708，向服务器约定好的接口请求云桌面连接参数，请求中带上ID属性；(相当于图4所示实施例中的步骤S404)；
步骤S710，服务端判断接收到的浏览器所在的IP(即请求方IP)，是否与此ID绑定的IP一致(相当于图4所示实施例中的步骤S406)，不一致则返回失败信息；否则返回对应的云桌面连接参数信息(相当于图4所示实施例中的步骤S408)，同时通过此接口从缓存中获取连接参数后，缓存中的数据即失效(相当于图5所示实施例中的步骤S502)，防止云桌面连接参数被多次调用；
步骤S712，startclient.exe程序自调用云桌面客户端，并传递启动参数。
通过该优选的实施例能够实现以下优点：1.多浏览器支持。chrome、FireFox、IE均支持自定义协议方式，360安全浏览器、QQ浏览器、搜狗浏览器因为内部使用的是IE和chrome双内核，所以实测也均支持；2.安全。即使浏览器将协议内容展示给用户，对于用户而言也是看不懂；此外由于ID绑定了IP，因而被第三方截取后，也无法使用。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如只读存储器/随机存储器(Read Only Memory/Random Access Memory，简称ROM/RAM)、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
在本实施例中还提供了一种云桌面的调用装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图8是根据本发明实施例的云桌面的调用装置的结构框图一，如图8所示，该装置应用于终端中，包括：
第一接收模块82，设置为接收触发信号，其中，触发信号用于触发服务端与浏览器对应的云桌面建立连接；
调用模块84，与第一接收模块82连接，设置为调用与云桌面的注册表中指定协议绑定的指定可执行程序，通过指定可执行程序向服务端调用云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议。
通过上述装置，通过调用模块84调用与云桌面的注册表中指定协议绑定的指定可执行程序，然后通过指定可执行程序向服务端调用云桌面与服务端的连接参数的方式，其中，指定协议为被多个浏览器所支持的协议，进而使得多个浏览器能够支持云桌面的调用，相关技术中的云桌面调用时存在的只支持IE浏览器无法支持其他浏览器的问题，进而扩展了云桌面启动的方式以及提高了云桌面启动的灵活性。
需要说明的是，上述指定协议可以被多个浏览器所支持，上述指定协议也可以是自定义的协议，即用户可以根据需要对协议进行自定义，但并不限于此。上述浏览器可以是chrome、Firefox、IE浏览器等，但不限于此，比如：360安全浏览器，QQ浏览器，搜狗浏览器等。
上述指定协议与指定可执行程序绑定可以表现为上述指定协议与指定可执行程序的路径绑定，当第一接收模块82接收到上述触发信号后，会触发上述指定协议，调用模块84跟据该指定协议与指定可执行程序的路径之间的绑定关系，找到该指定可执行程序的路径，在该路径下的可执行程序即为指定可执行程序。通过该指定可执行程序向服务端调用云桌面与服务端的连接参数。
上述终端可以安装windows系统中，但不限于此，比如linux系统，即上述装置可以在windows系统中工作。
为了保护云桌面信息的安全，避免云桌面的相关信息的泄露，在本发明实施例中，图9是根据本发明实施例的云桌面的调用装置的结构框图二，如图9所示，该装置除包括图8所示的所有模块外，上述装置还包括：
第二接收模块92，设置为接收服务端发送的与云桌面对应的身份标识ID；
第三接收模块94，与第二接收模板92连接，设置为接收服务端在确定接收的浏览器所在终端的IP地址与ID绑定的IP地址一致的情况下，返回的云桌面与服务端的连接参数。
通过上述模块，服务端不直接返回云桌面与服务端的连接参数，而是通过第二接收模块92接收服务器返回的身份标识ID，该ID与浏览器所在终端的IP地址绑定，这样即使被第三方截取后，也无法使用，进而增加了云桌面信息的安全性。
在本发明实施例中，上述调用模块84，还设置为调用与云桌面的注册表中指定协议绑定的指定可执行程序，通过指定可执行程序向服务端的缓存中调用云桌面与服务端的连接参数，其中，在向服务端的缓存中调用云桌面与服务端的连接参数之后，连接参数在缓存中失效。通过在从缓存中获取到云桌面与服务端的连接参数之后，缓存中的云桌面与服务端的连接参数则失效，进而能够防止该云桌面与服务端的连接参数被多次调用。
需要说明的是，上述装置可以还包括启动模块，设置为根据调用的云桌面与服务端的连 接参数，启动上述云桌面客户端。
在本实施例中还提供了一种云桌面的调用装置，图10是根据本发明实施例的云桌面的调用装置的结构框图三，如图10所示，该装置应用于服务端，上述装置包括：
第一接收模块1002，设置为接收浏览器发送的第一请求信息；其中，第一请求信息，用于指示浏览器请求服务端与浏览器对应的云桌面连接；
第一发送模块1004，与上述第一接收模块1002连接，设置为向与云桌面的注册表中指定协议绑定的指定可执行程序返回云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议。
通过上述装置，采用第一发送模块1004向与云桌面的注册表中指定协议绑定的指定可执行程序返回云桌面与服务端的连接参数的方式，其中，指定协议为被多个浏览器所支持的协议，进而使得多个浏览器能够支持云桌面的调用，相关技术中的云桌面调用时存在的只支持IE浏览器无法支持其他浏览器的问题，进而扩展了云桌面启动的方式以及提高了云桌面启动的灵活性。
需要说明的是，上述指定协议可以被多个浏览器所支持，上述指定协议也可以是自定义的协议，即用户可以根据需要对协议进行自定义，但并不限于此。上述浏览器可以是chrome、Firefox、IE浏览器等，但不限于此，比如：360安全浏览器，QQ浏览器，搜狗浏览器等。
上述指定协议与指定可执行程序绑定可以表现为上述指定协议与指定可执行程序的路径绑定，当浏览器接收到上述触发信号后，会触发上述指定协议，根据该指定协议与指定可执行程序的路径之间的绑定关系，找到该指定可执行程序的路径，在该路径下的可执行程序即为指定可执行程序。服务端则将云桌面与服务端的连接参数返回给该指定可执行程序。
上述方法可以应用于windows系统中，但不限于此，比如linux系统。
为了保护云桌面信息的安全，避免云桌面的相关信息的泄露，在本发明实施例中，图11是根据本发明实施例的云桌面的调用装置的结构框图四，如图11所示，上述装置除了图10所示的所有模块外，上述装置还包括：
第二发送模块1102，设置为向浏览器发送与云桌面对应的身份标识ID；
第二接收模块1104，与上述第二发送模块1102连接，设置为在指定可执行程序被指定协议调用后，通过指定接口接收指定可执行程序发送的第二请求信息，其中，第二请求信息用于指示指定可执行程序请求云桌面与服务端的连接参数，第二请求信息中携带身份标识ID。
在本发明实施例中，上述第一发送模块1004可以包括：判断单元1106，设置为判断服务端接收的浏览器所在终端的IP地址是否与ID绑定的IP地址一致；发送单元1108，与上述判断单元1106连接，设置为在一致的情况下，通过指定接口，向指定可执行程序返回服务端的缓存中的云桌面与服务端的连接参数。
通过上述模块，服务器不直接返回云桌面与服务端的连接参数，而是返回一个身份标识 ID，该ID与浏览器所在终端的IP地址绑定，通过服务端接收到的IP地址与ID绑定的IP地址比较，在一致的情况下，才返回服务端的缓存中的云桌面与服务端的连接参数，这样即使被第三方截取后，也无法使用，进而增加了云桌面信息的安全性。
在本发明实施例中，图12是根据本发明实施例的云桌面的调用装置的结构框图五，如图12所示，上述装置还包括：
设置模块1202，与上述第一发送模块1004连接，设置为将服务端的缓存中的云桌面与服务端的连接参数设置为失效。
通过在从缓存中获取到云桌面与服务端的连接参数之后，上述设置模块1202将缓存中的云桌面与服务端的连接参数设置为失效，能够防止该云桌面与服务端的连接参数被多次调用。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述模块分别位于多个处理器中。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，接收触发信号，其中，触发信号用于触发服务端与浏览器对应的云桌面建立连接；
S2，调用与云桌面的注册表中指定协议绑定的指定可执行程序，通过指定可执行程序向服务端调用云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
基于本发明实施例提供的上述技术方案，通过调用与云桌面的注册表中指定协议绑定的指定可执行程序，然后通过指定可执行程序向服务端调用云桌面与服务端的连接参数，其中，指定协议为被多个浏览器所支持的协议，进而使得多个浏览器能够支持云桌面的调用，解决了相关技术中的云桌面调用时存在的只支持IE浏览器无法支持其他浏览器的问题，进而扩展了云桌面启动的方式以及提高了云桌面启动的灵活性。

Claims (14)

  1. 一种云桌面的调用方法，包括：
    接收触发信号，其中，所述触发信号用于触发服务端与浏览器对应的云桌面建立连接；
    调用与所述云桌面的注册表中指定协议绑定的指定可执行程序，通过所述指定可执行程序向所述服务端调用所述云桌面与所述服务端的连接参数，其中，所述指定协议为被多个浏览器所支持的协议。
  2. 根据权利要求1所述的方法，其中，向所述服务端调用所述云桌面与所述服务端的连接参数之前，所述方法还包括：
    接收所述服务端发送的与所述云桌面对应的身份标识ID；
    接收所述服务端在确定接收的所述浏览器所在终端的IP地址与所述ID绑定的IP地址一致的情况下，返回的所述云桌面与所述服务端的连接参数。
  3. 根据权利要求1或2所述的方法，其中，调用与所述云桌面的注册表中指定协议绑定的指定可执行程序，通过所述指定可执行程序向所述服务端调用所述云桌面与所述服务端的连接参数包括：调用与所述云桌面的注册表中指定协议绑定的指定可执行程序，通过所述指定可执行程序向所述服务端的缓存中调用所述云桌面与所述服务端的连接参数，其中，在向所述服务端的缓存中调用所述云桌面与所述服务端的连接参数之后，所述连接参数在缓存中失效。
  4. 一种云桌面的调用方法，包括：
    服务端接收浏览器发送的第一请求信息；其中，所述第一请求信息，用于指示所述浏览器请求所述服务端与所述浏览器对应的云桌面连接；
    所述服务端向与所述云桌面的注册表中指定协议绑定的指定可执行程序返回所述云桌面与所述服务端的连接参数，其中，所述指定协议为被多个浏览器所支持的协议。
  5. 根据权利要求4所述的方法，其中，所述服务端向与所述云桌面的注册表中指定协议绑定的指定可执行程序返回所述云桌面与所述服务端的连接参数之前，所述方法还包括：
    所述服务端向所述浏览器发送与所述云桌面对应的身份标识ID；
    在所述指定可执行程序被所述指定协议调用后，所述服务端通过指定接口接收所述指定可执行程序发送的第二请求信息，其中，所述第二请求信息用于指示所述指定可执行程序请求所述云桌面与所述服务端的连接参数，所述第二请求信息中携带所述身份标识ID。
  6. 根据权利要求5所述的方法，其中，所述服务端向与所述云桌面的注册表中指定协议绑定的指定可执行程序返回所述云桌面与所述服务端的连接参数包括：
    所述服务端判断所述服务端接收的所述浏览器所在终端的IP地址是否与所述ID绑定的IP地址一致；
    在一致的情况下，所述服务端通过所述指定接口，向所述指定可执行程序返回所述服务端的缓存中的所述云桌面与所述服务端的连接参数。
  7. 根据权利要求4至6中任一项所述的方法，其中，在所述服务端向指定可执行程序返回所述云桌面与所述服务端的连接参数之后，所述服务端将所述服务端的缓存中的所述云桌面与所述服务端的连接参数设置为失效。
  8. 一种云桌面的调用装置，应用于终端，包括：
    第一接收模块，设置为接收触发信号，其中，所述触发信号用于触发服务端与浏览器对应的云桌面建立连接；
    调用模块，设置为调用与所述云桌面的注册表中指定协议绑定的指定可执行程序，通过所述指定可执行程序向所述服务端调用所述云桌面与所述服务端的连接参数，其中，所述指定协议为被多个浏览器所支持的协议。
  9. 根据权利要求8所述的装置，其中，所述装置还包括：
    第二接收模块，设置为接收所述服务端发送的与所述云桌面对应的身份标识ID；
    第三接收模块，设置为接收所述服务端在确定接收的所述浏览器所在终端的IP地址与所述ID绑定的IP地址一致的情况下，返回的所述云桌面与所述服务端的连接参数。
  10. 根据权利要求8或9所述的装置，其中，所述调用模块，还设置为调用与所述云桌面的注册表中指定协议绑定的指定可执行程序，通过所述指定可执行程序向所述服务端的缓存中调用所述云桌面与所述服务端的连接参数，其中，在向所述服务端的缓存中调用所述云桌面与所述服务端的连接参数之后，所述连接参数在缓存中失效。
  11. 一种云桌面的调用装置，应用于服务端，包括：
    第一接收模块，设置为接收浏览器发送的第一请求信息；其中，所述第一请求信息，用于指示所述浏览器请求所述服务端与所述浏览器对应的云桌面连接；
    第一发送模块，设置为向与所述云桌面的注册表中指定协议绑定的指定可执行程序返回所述云桌面与所述服务端的连接参数，其中，所述指定协议为被多个浏览器所支持的协议。
  12. 根据权利要求11所述的装置，其中，所述装置还包括：
    第二发送模块，设置为向所述浏览器发送与所述云桌面对应的身份标识ID；
    第二接收模块，设置为在所述指定可执行程序被所述指定协议调用后，通过指定接口接收所述指定可执行程序发送的第二请求信息，其中，所述第二请求信息用于指示所 述指定可执行程序请求所述云桌面与所述服务端的连接参数，所述第二请求信息中携带所述身份标识ID。
  13. 根据权利要求12所述的装置，其中，所述第一发送模块包括：
    判断单元，设置为判断所述服务端接收的所述浏览器所在终端的IP地址是否与所述ID绑定的IP地址一致；
    发送单元，设置为在一致的情况下，通过所述指定接口，向所述指定可执行程序返回所述服务端的缓存中的所述云桌面与所述服务端的连接参数。
  14. 根据权利要求11至13中任一项所述的装置，其中，所述装置还包括：
    设置模块，设置为将所述服务端的缓存中的所述云桌面与所述服务端的连接参数设置为失效。
PCT/CN2016/105321 2015-11-10 2016-11-10 云桌面的调用方法及装置 WO2017080487A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510763059.0 2015-11-10
CN201510763059.0A CN106686038A (zh) 2015-11-10 2015-11-10 云桌面的调用方法及装置

Publications (1)

Publication Number Publication Date
WO2017080487A1 true WO2017080487A1 (zh) 2017-05-18

Family

ID=58694526

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/105321 WO2017080487A1 (zh) 2015-11-10 2016-11-10 云桌面的调用方法及装置

Country Status (2)

Country Link
CN (1) CN106686038A (zh)
WO (1) WO2017080487A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111416853A (zh) * 2020-03-16 2020-07-14 西安雷风电子科技有限公司 一种idv云桌面远程开机的方法及系统
CN113472866A (zh) * 2021-06-23 2021-10-01 北京理工大学珠海学院 基于tcp协议的云端神经网络数据接口方法

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107608763A (zh) * 2017-09-26 2018-01-19 中国科学院声学研究所 一种通过Web浏览器进入Docker容器操作的方法
CN108366103B (zh) * 2018-01-29 2021-03-02 广州杰赛科技股份有限公司 远程连接方法、装置、计算机设备和存储介质
CN110138817A (zh) * 2018-02-08 2019-08-16 中兴通讯股份有限公司 流媒体播放方法、装置、设备及计算机可读存储介质
CN109639749B (zh) * 2018-10-16 2021-09-21 平安科技（深圳）有限公司 云桌面的访问方法、装置、设备及存储介质
CN110191158A (zh) * 2019-05-09 2019-08-30 厦门网宿有限公司 一种云桌面服务实现方法和系统
CN111371881A (zh) * 2020-02-28 2020-07-03 北京字节跳动网络技术有限公司 服务调用方法及设备
CN111880946B (zh) * 2020-07-14 2024-04-19 杭州海康威视数字技术股份有限公司 本地服务提供方法、装置及设备、存储介质
CN114840287B (zh) * 2022-03-25 2024-04-16 阿里巴巴（中国）有限公司 一种跨云桌面的任务交互方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103582510A (zh) * 2010-12-10 2014-02-12 韦斯技术有限公司 用于利用转码服务器经由HTTP API通过客户端设备处的Web浏览器实时地访问和控制远程机器的远程桌面的方法和系统
CN104394226A (zh) * 2014-12-04 2015-03-04 英业达科技有限公司 通过网页实现远程桌面控制的系统及方法
US20150120807A1 (en) * 2013-10-29 2015-04-30 Srinivas Bharadwaj Integrated viewing of local and remote applications in various multiplatform environments
CN104702624A (zh) * 2015-03-27 2015-06-10 深圳市研唐科技有限公司 基于CloudStack平台虚拟机登录方法及系统
CN104735108A (zh) * 2013-12-20 2015-06-24 中国移动通信集团公司 一种使用云桌面的方法、装置和云桌面系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103582510A (zh) * 2010-12-10 2014-02-12 韦斯技术有限公司 用于利用转码服务器经由HTTP API通过客户端设备处的Web浏览器实时地访问和控制远程机器的远程桌面的方法和系统
US20150120807A1 (en) * 2013-10-29 2015-04-30 Srinivas Bharadwaj Integrated viewing of local and remote applications in various multiplatform environments
CN104735108A (zh) * 2013-12-20 2015-06-24 中国移动通信集团公司 一种使用云桌面的方法、装置和云桌面系统
CN104394226A (zh) * 2014-12-04 2015-03-04 英业达科技有限公司 通过网页实现远程桌面控制的系统及方法
CN104702624A (zh) * 2015-03-27 2015-06-10 深圳市研唐科技有限公司 基于CloudStack平台虚拟机登录方法及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LU , KANG: "Research of Virtualized Desktop Transmission Protocol", ELECTRONIC TECHNOLOGY & INFORMATION SCIENCE , CHINA MASTER'S THESES FULL-TEXT DATABASE, 15 June 2014 (2014-06-15) *
WANG, DAOPING ET AL.: "Research on Virtual Desktop Management Based on Cloud Computing", LOGISTICS, INFORMATICS AND SERVICE SCIENCES (LISS, 29 July 2015 (2015-07-29), XP032839843 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111416853A (zh) * 2020-03-16 2020-07-14 西安雷风电子科技有限公司 一种idv云桌面远程开机的方法及系统
CN111416853B (zh) * 2020-03-16 2022-10-21 西安雷风电子科技有限公司 一种idv云桌面远程开机的方法及系统
CN113472866A (zh) * 2021-06-23 2021-10-01 北京理工大学珠海学院 基于tcp协议的云端神经网络数据接口方法

Also Published As

Publication number Publication date
CN106686038A (zh) 2017-05-17

Similar Documents

Publication Publication Date Title
WO2017080487A1 (zh) 云桌面的调用方法及装置
US20210216360A1 (en) Virtual machine migration method and apparatus
WO2017185253A1 (zh) 基于补丁升级的文件处理方法、装置、终端以及存储介质
WO2019104975A1 (zh) 基于dubbo框架的远程调用方法、服务器及存储介质
US9436822B2 (en) Virtual browsing environment
US7779409B2 (en) Device-to-device software distribution
JP5830102B2 (ja) 取得ファイルの評判チェック
JP6945782B2 (ja) ウェブページとネイティブアプリケーションの間の通信を実現する方法及び装置並びに電子装置
TWI626593B (zh) 一種軟體升級的方法及裝置
US9342333B2 (en) Backend custom code extensibility
EP2722754A1 (en) Software Appliance Installation Systems And Methods
EP3748500B1 (en) Inversion-of-control component service models for virtual environments
US8261261B2 (en) Installing a computer program
JP6182160B2 (ja) 実行中のプロセスへのコードの動的挿入
CN108768957B (zh) 一种应用的用户信息管理的方法、设备及系统
WO2014193530A1 (en) Dynamic registration of an application with an enterprise system
TW201606648A (zh) 應用的處理方法及裝置
KR20160054474A (ko) 클라이언트를 다운로드 및 인스톨하는 방법 및 장치
US10506400B2 (en) Data download method and apparatus
US20180121224A1 (en) Isolating a redirected smart card reader to a remote session
WO2020248727A1 (zh) 一种软件模块的管理方法、装置及服务器
CN112527669B (zh) 本地服务的自测方法及系统
US10997269B1 (en) Using web application components with different web application frameworks in a web application
US10452838B2 (en) Providing joint access to an isolated computer object by both an isolated computer application and a non-isolated computer application
US9609080B2 (en) Systems and methods for device identity delegation for application software

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16863663

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16863663

Country of ref document: EP

Kind code of ref document: A1