CN115857981A - Cloud native desktop protocol client updating method - Google Patents
Cloud native desktop protocol client updating method Download PDFInfo
- Publication number
- CN115857981A CN115857981A CN202111134146.1A CN202111134146A CN115857981A CN 115857981 A CN115857981 A CN 115857981A CN 202111134146 A CN202111134146 A CN 202111134146A CN 115857981 A CN115857981 A CN 115857981A
- Authority
- CN
- China
- Prior art keywords
- version
- protocol
- information
- client
- protocol client
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Images
Landscapes
- Communication Control (AREA)
Abstract
The embodiment of the application provides a method and a device for updating a protocol client, wherein the method comprises the following steps: the protocol client sends first version information to the protocol server, wherein the first version information indicates the version information of the protocol client; when the protocol server determines that the first version information is not matched with the version information of the protocol server, the protocol server sends indication information to the protocol client, wherein the indication information is used for indicating the protocol client to obtain a second version, and the version information of the second version is matched with the version information of the server; the protocol client acquires the second version from a management library according to the indication information, wherein the management library comprises one or more versions of the protocol client; the protocol client loads the second version, so that the current version of the protocol client is updated to the second version. Based on the technical scheme, the protocol client does not need to be compatible with various protocol server versions, and the size of the protocol client is reduced.
Description
Technical Field
The embodiment of the application relates to the technical field of cloud computing software management, in particular to a method for updating a cloud native desktop protocol client.
Background
With the advent of the cloud era, office modes are gradually evolving. Traditional fixed PC office work and mobile PC office work gradually evolve into a cloud office work mode. The technical core of the existing cloud office desktop is that a virtual desktop on a cloud platform is delivered to a display of a terminal through a desktop protocol, and a peripheral on the terminal is mapped to the virtual desktop on the cloud platform through the desktop protocol, so that a user can use the virtual desktop.
The protocol server located in the virtual desktop and the protocol client located on the terminal need to cooperate to complete corresponding work. Specifically, the protocol server needs to respond to a virtual desktop connection request initiated by the protocol client, and process requests and response messages from a keyboard and a mouse, audio and video, peripheral input and output, and the like of the protocol client. The protocol client needs to receive and process the request and response messages of the protocol server. Only if the protocol server and the protocol client can cooperate with each other to receive and process the request and response messages of the two parties, the virtual desktop can be normally used by the user.
With the iterative update of the cloud office desktop, the functions of the product are increasingly improved and enriched, and the functions and the performances of the desktop protocol are also increasingly powerful. The new protocol server needs the new protocol client to cooperate with the new protocol server, so that the user can normally and smoothly use the virtual desktop. However, a scenario that the protocol server of the user virtual desktop is not upgraded or cannot be upgraded to a new version exists, and at this time, the protocol client is required to be compatible with both the protocol server of the new version and the protocol server of the old version.
However, one protocol client cannot be completely compatible with all versions of the protocol server, and when the versions of the protocol server are increased, the protocol client is thicker and larger.
Disclosure of Invention
The embodiment of the application provides an updating method and device for a cloud native desktop protocol, so that a protocol client can be flexibly matched with protocol servers of different versions, and various versions of the protocol client are stored in a management plane, so that the protocol client does not need to be compatible with various protocol server versions in a cross mode, and the size of the protocol client is reduced.
In a first aspect, a method for updating a protocol client is provided, where the method is applied to a cloud desktop system, the cloud desktop system includes a protocol server and a protocol client, and the method includes: the protocol client sends first version information to the protocol server, and the first version information indicates version information of the protocol client; when the protocol server determines that the first version information is not matched with the version information of the protocol server, the protocol server sends indication information to the protocol client, wherein the indication information is used for indicating the protocol client to acquire a second version, and the version information of the second version is matched with the version information of the server; the protocol client acquires the second version from a management library according to the indication information, wherein the management library comprises one or more versions of the protocol client; the protocol client loads the second version, so that the current version of the protocol client is updated to the second version.
Based on the technical scheme, when the protocol server determines that the first version information of the protocol client is not matched with the version information of the protocol server, the protocol server sends indication information to the protocol client, and the protocol client is indicated to acquire the second version matched with the version information of the protocol server. And the protocol client loads the second version, so that the current version of the protocol client is updated to the second version. Therefore, the protocol client can be flexibly matched with the protocol servers of different versions, and the protocol client does not need to be compatible with various protocol server versions in a cross mode, so that the size of the protocol client is reduced.
With reference to the first aspect, in certain implementations of the first aspect, the indication information includes version information of the second version. Based on the technical scheme, the protocol client can be flexibly matched with the protocol servers of different versions, and the protocol client does not need to be compatible with various protocol server versions in a cross mode, so that the size of the protocol client is reduced.
With reference to the first aspect, in certain implementations of the first aspect, the indication information includes version information of the protocol server. Based on the technical scheme, the protocol client can be flexibly matched with the protocol servers of different versions, and the protocol client does not need to be compatible with various protocol server versions in a cross mode, so that the size of the protocol client is reduced.
With reference to the first aspect, in some implementations of the first aspect, the acquiring, by the protocol client, the second version from the management repository according to the indication information includes: the protocol client sends the version information of the protocol server to the management library, and the management library comprises the matching relation between the version information of the protocol client and the protocol server; the protocol client receives the second version, and the second version is determined according to the version information of the protocol server and the matching relationship between the version information of the protocol client and the protocol server.
Based on the technical scheme, the protocol client can be flexibly matched with the protocol servers of different versions, and various versions of the protocol client are stored in the management plane, so that the protocol client does not need to be compatible with various protocol server versions in a cross mode, and the size of the protocol client is reduced.
With reference to the first aspect, in certain implementations of the first aspect, the second version is lower than the current version.
In a second aspect, a method for updating a protocol client is provided, and the method is applied to the protocol client, and includes: sending first version information to a protocol server, wherein the first version information indicates version information of the protocol client; receiving indication information sent by the protocol server, wherein the indication information is used for indicating the protocol client to acquire a second version, and the version information of the second version is matched with the version information of the protocol server; acquiring the second version from a management library, wherein the management library comprises one or more versions of the protocol client; and loading the acquired second version, so that the current version of the protocol client is updated to the second version.
Based on the technical scheme, the protocol client sends the first version information to the protocol server, and the protocol server determines that the first version information is not matched with the version information of the protocol server and indicates the protocol client to acquire the second version matched with the version information of the protocol server. And the protocol client loads the second version, so that the current version of the protocol client is updated to the second version. Therefore, the protocol client can be flexibly matched with the protocol servers of different versions, and various versions of the protocol client are stored in the management plane, so that the protocol client does not need to be compatible with various versions of the protocol servers in a cross mode, and the size of the protocol client is reduced.
With reference to the second aspect, in some implementations of the second aspect, the indication information includes version information of the second version. Based on the technical scheme, the protocol client can be flexibly matched with the protocol servers of different versions, and the protocol client does not need to be compatible with various protocol server versions in a cross mode, so that the size of the protocol client is reduced.
With reference to the second aspect, in some implementations of the second aspect, the indication information includes version information of the protocol server. Based on the technical scheme, the protocol client can be flexibly matched with the protocol servers of different versions, and the protocol client does not need to be compatible with various protocol server versions in a cross mode, so that the size of the protocol client is reduced.
With reference to the second aspect, in some implementations of the second aspect, the obtaining the second version from the management repository includes: sending the version information of the protocol server to the management library, wherein the management library comprises the matching relationship between the version information of the protocol client and the protocol server; and receiving the second version, wherein the second version is determined according to the version information of the protocol server and the matching relationship between the version information of the protocol client and the protocol server.
Based on the technical scheme, the protocol client can be flexibly matched with the protocol servers of different versions, and various versions of the protocol client are stored in the management plane, so that the protocol client does not need to be compatible with various protocol server versions in a cross mode, and the size of the protocol client is reduced.
With reference to the second aspect, in some implementations of the second aspect, the second version is lower than the current version.
In a third aspect, a cloud desktop system is provided, including: the protocol server is used for sending first version information to the protocol client, wherein the first version information indicates the version information of the protocol client; the protocol server is used for sending indication information to the protocol client when the protocol server determines that the first version information is not matched with the version information of the protocol server, wherein the indication information is used for indicating the protocol client to acquire a second version, and the version information of the second version is matched with the version information of the server; the protocol client is used for acquiring the second version from a management library according to the indication information, wherein the management library comprises one or more versions of the protocol client; the protocol client is used for loading the second version, so that the current version of the protocol client is updated to the second version.
With reference to the third aspect, in some implementations of the third aspect, the indication information includes version information of the second version.
With reference to the third aspect, in some implementations of the third aspect, the indication information includes version information of the protocol server.
With reference to the third aspect, in some implementations of the third aspect, the protocol client is specifically configured to: sending the version information of the protocol server to the management library, wherein the management library comprises the matching relation between the version information of the protocol client and the protocol server; and receiving the second version, wherein the second version is determined according to the version information of the protocol server and the matching relationship between the version information of the protocol client and the protocol server.
With reference to the third aspect, in some implementations of the third aspect, the second version is lower than the current version.
In a fourth aspect, a protocol client is provided, including: a sending unit, configured to send first version information to a protocol server, where the first version information indicates version information of the protocol client; a receiving unit, configured to receive indication information sent by the protocol server, where the indication information is used to indicate the protocol client to obtain a second version, and version information of the second version is matched with version information of the protocol server; the processing unit is used for acquiring the second version from a management library, and the management library comprises one or more versions of the protocol client; the processing unit is configured to load the obtained second version, so that the current version of the protocol client is updated to the second version.
In a fourth aspect, in some implementations of the fourth aspect, the indication information includes version information of the second version.
In a fourth aspect, in some implementations of the fourth aspect, the indication information includes version information of the protocol server.
In a fourth aspect, in some implementations of the fourth aspect, the processing unit is specifically configured to: sending the version information of the protocol server to the management library, wherein the management library comprises the matching relation between the version information of the protocol client and the protocol server; and receiving the second version, wherein the second version is determined according to the version information of the protocol server and the matching relationship between the version information of the protocol client and the protocol server.
With reference to the fourth aspect, in some implementations of the fourth aspect, the second version is lower than the current version.
In a fifth aspect, a computer-readable storage medium is provided, which is characterized by having stored thereon computer instructions, which, when run on a computer, cause the computer to perform the method of any of the possible implementations of the first aspect or to perform the method of any of the possible implementations of the second aspect.
In a sixth aspect, a chip system is provided, the chip system comprising: a processor coupled to a memory, the memory to store instructions; the processor is configured to call and execute the instructions from the memory, so that the communication device on which the chip system is installed executes the method in any possible implementation manner of the first aspect, or executes the method in any possible implementation manner of the second aspect.
Drawings
Fig. 1 is a schematic structural diagram of a cloud desktop system provided in an embodiment of the present application.
Fig. 2 is a schematic flow chart of a method for updating a protocol client provided in an embodiment of the present application.
Fig. 3 is a schematic flowchart of a method for updating a protocol client according to another embodiment of the present application.
Fig. 4 is a schematic block diagram of an apparatus provided in an embodiment of the present application.
Fig. 5 is a schematic view of another apparatus provided in the embodiments of the present application.
Fig. 6 is a schematic structural diagram of an apparatus provided in an embodiment of the present application.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
As used in this specification, the terms "component," "unit," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between 2 or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with another component in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).
Fig. 1 is a schematic structural diagram of a cloud desktop system provided in an embodiment of the present application, and as shown in fig. 1, a cloud desktop system 100 includes a cloud service end 110, at least one cloud client 120, and a management library 130. The cloud server 110 is a server installed in a virtual desktop, and is responsible for responding to a virtual desktop connection request initiated by the cloud client 120, and processing requests and response messages from a keyboard and a mouse, audio and video, peripheral input and output, and the like of the desktop cloud client 120. The access protocol by which the cloud client 120 can remotely access the virtual desktop is a cloud client installed in an access terminal, and is used for initiating a request for connecting the virtual desktop, receiving and processing a request and a response message for delivering a service. The cloud server 110 may be referred to as a protocol server, and the cloud client 120 may also be referred to as a protocol client, a cloud terminal, and the like. The management library 130 is used for communicating with the cloud client 120, and the management library 130 may also be referred to as a management plane, a management control plane, and the like. It should be understood that the embodiments of the present application are not limited thereto.
The technical solution of the embodiment of the present application includes but is not limited to be applied to a cloud desktop system, and may also be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, a future fifth generation (5g) System, or a New Radio Network (NR), etc.
The Cloud server 110 in this embodiment may be a device for communicating with the Cloud client 120, where the Cloud server 110 may be a Base Transceiver Station (BTS) in a Global System for Mobile communications (GSM) System or a Code Division Multiple Access (CDMA) System, may also be a Base Station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) System, may also be an evolved node b (eNB, eNodeB) in an LTE System, may also be a wireless controller in a Cloud Radio Access Network (CRAN) scenario, or the Network device may be a relay Station, an Access point, a vehicle-mounted device, a wearable device, a Network device in a future 5G Network, or a Network device in a future evolved PLMN Network, and the present embodiment is not limited.
Fig. 2 illustrates a protocol client updating method provided by an embodiment of the present application, which is applied to a cloud desktop system and includes at least the following steps.
S210, the protocol client sends first version information to the protocol server, correspondingly, the protocol server receives the first version information sent by the protocol client, and the first version information indicates the version information of the protocol client.
Specifically, the first version information may be current version information of the protocol client, and for example, the current version information may be a current version number, a generation date, a file name, a file size, and the like of the protocol client.
The first version information may be carried in the connection request message. Specifically, the protocol client sends a connection request message to the protocol server, the connection request message carries first version information of the protocol client, and the protocol client requests to establish communication connection with the protocol server. It should be understood that the first version information may also be carried in other messages, and the embodiment of the present application does not limit this.
It should be noted that the protocol client may be referred to as a client, a protocol client, a client, and the like, and the protocol server may be referred to as a server, and it should be understood that this is not limited in this embodiment of the present application. For the convenience of understanding, hereinafter, the embodiments of the present application are described by using a protocol client and a protocol server together.
S220, the protocol server checks the first version information, and if the protocol server determines that the current version information of the protocol client is not matched with the version information of the protocol server, the protocol server executes S230. And if the protocol server determines that the current version information of the protocol client is matched with the version information of the protocol server, the protocol server establishes communication connection with the protocol client and returns a connection response to the protocol client.
And S230, the protocol server sends indication information to the protocol client, wherein the indication information is used for indicating the protocol client to acquire the second version, and the version information of the second version is matched with the version information of the protocol server.
S240, the protocol client acquires the second version from the management library, wherein the management library stores the versions of one or more protocol clients.
Specifically, the protocol server determines that the current version information of the protocol client is not matched with the version information of the protocol server, at this time, the protocol server sends indication information to the protocol client, the indication information indicates the protocol client to acquire the second version, and the version information of the second version is matched with the version information of the server.
It should be noted that, in a possible implementation manner, the second version of the protocol client may be higher than the current version, that is, the protocol server determines that the current version of the protocol client is too low and is not matched with the version of the protocol server, at this time, the protocol server sends the indication information to indicate the protocol client to obtain the second version of the higher version, that is, indicate the protocol client to upgrade to the second version matched with the version of the protocol server.
In another possible implementation manner, the second version of the protocol client may also be lower than the current version, that is, the protocol server determines that the current version of the protocol client is too high and is not matched with the version of the protocol server, and at this time, the protocol server sends indication information to indicate the protocol client to obtain the second version of the lower version, that is, to indicate that the protocol client is degraded to the second version matched with the version of the protocol server.
It should be further noted that, in a possible implementation manner, the second version of the protocol client may also be a version that is newer than the current version, that is, the protocol server determines that the current version of the protocol client is an old version and is not matched with the version of the protocol server, at this time, the protocol server sends the indication information to indicate the protocol client to acquire the new second version, that is, indicate the protocol client to update to the new second version matched with the version of the protocol server.
In another possible implementation manner, the second version of the protocol client may also be an old version compared to the current version, that is, the protocol server determines that the current version of the protocol client is a new version and is not matched with the version of the protocol server, at this time, the protocol server sends the indication information to indicate the protocol client to acquire the old second version, that is, indicate the protocol client to update to the old second version matched with the version of the protocol server.
In one possible implementation, the indication information may include version information of the second version. Specifically, the protocol server determines that the current version information of the protocol client is not matched with the protocol server, determines a second version matched with the protocol server after the protocol server performs version negotiation, and returns the version information of the second version to the protocol client through the indication information.
In a possible implementation manner, the indication information includes version information of the protocol server, specifically, the indication information sent by the protocol server to the protocol client may also include version information of the protocol server, and the protocol client sends the received version information of the protocol server to the management library. It should be understood that the management library includes a matching relationship between at least one version information of the protocol client and at least one version information of the protocol server, and the management library returns a second version corresponding to the version of the protocol server to the protocol client according to the matching relationship.
Illustratively, if the version information of the protocol server is version 1 and the version information of the protocol client matched with the protocol server in the management library is version I, then the management library returns a second version of which the version information is version I to the protocol client according to the matching relationship.
It should be understood that the management library may be referred to as a management plane or may also be referred to as a management plane, which is not limited by the embodiment of the present application.
It should also be understood that the matching relationship may be a one-to-one matching relationship, a one-to-many matching relationship, or a many-to-one matching relationship, which is not limited in the embodiment of the present application.
In another possible implementation manner, specifically, the protocol server determines that the current version information of the protocol client matches the version information of the protocol server, at this time, the protocol server establishes a connection with the protocol client, and returns a response of connection establishment to the protocol client.
And S250, the protocol client loads the second version, so that the current version of the protocol client is updated to the second version.
The protocol client acquires the second version from the management library, loads the second version, and can install the second version only if the change of the second version relates to the drive state under a possible condition. In a possible case, if the change of the second version does not involve the drive state, the protocol client is directly updated to the protocol client of the second version without restarting the protocol client.
Fig. 3 illustrates a protocol client update method provided in an embodiment of the present application, which may include at least the following steps.
S310, the protocol client sends first version information to the protocol server, correspondingly, the protocol server receives the first version information sent by the protocol client, and the first version information indicates the version information of the protocol client. S310 is similar to S210, and for simplicity, the description is omitted here.
S320, the protocol server checks the first version information, and the protocol server determines that the current version information of the protocol client is not matched with the version information of the protocol server.
S330, the protocol server sends indication information to the protocol client, the indication information is used for indicating the protocol client to obtain the second version, and the version information of the second version is matched with the version information of the protocol server.
Specifically, the protocol server determines that the current version information of the protocol client is not matched with the version information of the protocol server, at this time, the protocol server sends indication information to the protocol client, the indication information indicates the protocol client to acquire the second version, and the version information of the second version is matched with the version information of the server.
It should be noted that, in a possible implementation manner, the second version of the protocol client may be higher than the current version, that is, the protocol server determines that the current version of the protocol client is too low and is not matched with the version of the protocol server, at this time, the protocol server sends the indication information to indicate the protocol client to obtain the second version of the higher version, that is, indicate the protocol client to upgrade to the second version matched with the version of the protocol server.
In another possible implementation manner, the second version of the protocol client may also be lower than the current version, that is, the protocol server determines that the current version of the protocol client is too high and is not matched with the version of the protocol server, at this time, the protocol server sends indication information to indicate the protocol client to acquire the second version of the lower version, that is, indicate that the protocol client is degraded to the second version matched with the version of the protocol server.
It should be further noted that, in a possible implementation manner, the second version of the protocol client may also be a version that is newer than the current version, that is, the protocol server determines that the current version of the protocol client is an old version and is not matched with the version of the protocol server, at this time, the protocol server sends the indication information to indicate the protocol client to acquire the new second version, that is, indicate the protocol client to update to the new second version matched with the version of the protocol server.
In another possible implementation manner, the second version of the protocol client may also be an old version compared with the current version, that is, the protocol server determines that the current version of the protocol client is a new version and is not matched with the version of the protocol server, at this time, the protocol server sends indication information to indicate the protocol client to acquire the old second version, that is, to indicate the protocol client to update to the old second version matched with the version of the protocol server.
In one possible implementation, the indication information may include version information of the second version. Specifically, the protocol server determines that the current version information of the protocol client is not matched with the protocol server, determines a second version matched with the protocol server after the protocol server performs version negotiation, and returns the version information of the second version to the protocol client through the indication information.
In a possible implementation manner, the indication information includes version information of the protocol server, specifically, the indication information sent by the protocol server to the protocol client may also include version information of the protocol server, and the protocol client sends the received version information of the protocol server to the management library. It should be understood that the management library includes a matching relationship between at least one version information of the protocol client and at least one version information of the protocol server, and the management library returns a second version corresponding to the version of the protocol server to the protocol client according to the matching relationship.
In a possible implementation manner, the indication information may further include version information of the protocol server, and specifically, the indication information sent by the protocol server to the protocol client includes the version information of the protocol server.
Optionally, the method may further include S340, sending, by the protocol client, request information to the management library, where the request information is used to request to obtain the second version from the management library, and it should be understood that at least one version of the protocol client is stored in the management library.
S350, the management library returns the second version to the protocol client.
In a possible implementation manner, the request information includes version information of the second version, and after the protocol client receives the indication information sent by the protocol server, the indication information includes the version information of the second version. And the protocol client sends request information to the management library, the request information carries the version information of the second version, and the management library returns the second version to the protocol client after receiving the version information of the second version.
In a possible implementation manner, the request information includes version information of the protocol server, and the protocol client receives indication information sent by the protocol server, where the indication information includes the version information of the protocol server. The protocol client sends request information to the management library, the request information carries version information of the protocol server, and after receiving the version information of the protocol server, the management library returns a second version matched with the version of the protocol server to the protocol client according to the matching relation between the version information of the protocol client and the version information of the protocol server in the management library.
It should be understood that the management library may be referred to as a management plane or may also be referred to as a management plane, which is not limited by the embodiment of the present application.
It should be understood that the matching relationship may be a one-to-one matching relationship, a one-to-many matching relationship, or a many-to-one matching relationship, which is not limited in the embodiment of the present application.
It should also be understood that, the fact that the management library returns the second version to the protocol client may be understood as returning the second version and version information of the second version, and may also be understood as returning only the second version, which is not limited in this embodiment of the present application.
In another possible implementation manner, specifically, the protocol server determines that the current version information of the protocol client matches the version information of the protocol server, at this time, the protocol server establishes a connection with the protocol client, and returns a response of connection establishment to the protocol client.
And S360, the protocol client loads the second version, so that the current version of the protocol client is updated to the second version. S360 is similar to S260, and for simplicity, the description is omitted here.
Optionally, the method may further include S370-S380, after the protocol client installs the second version, sending version information of the second version to the protocol server, and initiating a connection request to the protocol server to request to establish communication with the protocol server.
And S380, the protocol server checks the second version information sent by the protocol client, determines that the second version information is matched with the version information of the protocol server, and executes S390 to return a connection response to the protocol client.
By the technical scheme, the protocol client can be flexibly matched with the protocol servers of different versions, various versions of the protocol client are stored in the management plane, and the protocol client does not need to be compatible with various versions of the protocol servers in a cross mode, so that the size of the protocol client is reduced.
The various embodiments described herein may be implemented as stand-alone solutions or combined in accordance with inherent logic and are intended to fall within the scope of the present application.
It is to be understood that, in the above embodiments of the methods, the methods and operations implemented by each device may also be implemented by a component (e.g., a chip or a circuit) of the corresponding device.
The above description mainly introduces the scheme provided by the embodiments of the present application from various interaction perspectives. It is understood that each network element, for example, the transmitting end device or the receiving end device, includes a corresponding hardware structure and/or software module for performing each function in order to implement the above functions. Those of skill in the art would appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiment of the present application, the sending end device or the receiving end device may be divided into functional modules according to the above method examples, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a form of hardware or a form of a software functional module. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation. The following description will be given by taking an example in which each functional module is divided by using a corresponding function.
It should be understood that the specific examples in the embodiments of the present application are for the purpose of promoting a better understanding of the embodiments of the present application and are not intended to limit the scope of the embodiments of the present application.
It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
The method provided by the embodiment of the present application is described in detail above with reference to fig. 2 to 3. Hereinafter, the apparatus provided in the embodiment of the present application will be described in detail with reference to fig. 4 to 5. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments, and therefore, for brevity, details are not repeated here, since the details that are not described in detail may be referred to the above method embodiments.
Fig. 4 shows a schematic block diagram of a protocol client 400 of an embodiment of the application. It should be understood that the apparatus 400 includes a transmitting unit 410, a receiving unit 420, and a processing unit 430.
The sending unit 410 is configured to send first version information to a protocol server, where the first version information indicates version information of the protocol client; the receiving unit 420 is configured to receive indication information sent by the protocol server, where the indication information is used to indicate the protocol client to obtain a second version, and version information of the second version is matched with version information of the protocol server; the processing unit 430 is configured to obtain the second version from a management library, where the management library includes one or more versions of the protocol client; the processing unit 430 is configured to load the obtained second version, so that the current version of the protocol client is updated to the second version.
In one possible implementation, the indication information includes version information of the second version.
In one possible implementation, the indication information includes version information of the protocol server.
In a possible implementation manner, the processing unit 430 is specifically configured to: and sending the version information of the protocol server to the management library, wherein the management library comprises the matching relation between the version information of the protocol client and the protocol server.
In one possible implementation, the second version is lower than the current version.
Fig. 5 shows a schematic block diagram of a protocol server 500 according to an embodiment of the present application. It should be understood that the apparatus 500 includes a receiving unit 510 and a transmitting unit 520.
The receiving unit 510 is configured to receive first version information sent by a protocol client, where the first version information indicates version information of the protocol client; the sending unit 520 is configured to send, when it is determined that the first version information does not match the version information of the protocol server, indication information to the protocol client, where the indication information is used to indicate the protocol client to obtain a second version, and the version information of the second version matches the version information of the protocol server.
In one possible implementation, the indication information includes version information of the second version.
In one possible implementation, the indication information includes version information of the protocol server.
It should be understood that the above division of the modules in the communication device is only a division of logical functions, and the actual implementation may be wholly or partially integrated into one physical entity or may be physically separated. And the modules in the communication device can be realized in the form of software called by the processing element; or may be implemented entirely in hardware; and part of the modules can be realized in the form of software called by the processing element, and part of the modules can be realized in the form of hardware. For example, each module may be a processing element separately set up, or may be implemented by being integrated in a chip of the communication apparatus, or may be stored in a memory in the form of a program, and the function of the module may be called and executed by a processing element of the communication apparatus. In addition, all or part of the modules can be integrated together or can be independently realized. The processing element described herein may in turn be a processor, which may be an integrated circuit having signal processing capabilities. In the implementation process, the steps of the method or the modules above may be implemented by integrated logic circuits of hardware in a processor element or in a form called by software through the processor element.
In one example, the modules in any of the above communication devices may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), or a combination of at least two of these integrated circuit forms. As another example, when a module in a communication device may be implemented in the form of a processing element scheduler, the processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor that can invoke a program. As another example, these modules may be integrated together, implemented in the form of a system-on-a-chip (SOC).
Referring to fig. 6, a schematic diagram of a communication device provided in an embodiment of the present application is used to implement operations of a protocol client, a protocol server, and a management library in the above embodiments. As shown in fig. 6, the communication apparatus includes: a processor 610 and an interface 630, the processor 610 being coupled to the interface 630. The interface 630 is used to enable communication with other devices. The interface 630 may be a transceiver or an input-output interface. The interface 630 may be, for example, an interface circuit. Optionally, the communication device further comprises a memory 620 for storing instructions executed by the processor 610 or for storing input data required by the processor 610 to execute the instructions or for storing data generated by the processor 610 after executing the instructions.
The method executed by the protocol client, the protocol server, and the management library in the above embodiments may be implemented by the processor 610 calling a program stored in a memory (which may be the memory 620 in the protocol client, the protocol server, and the management library, or may be an external memory). That is, the protocol client, the protocol server and the management library may include the processor 610, and the processor 610 executes the method executed by the protocol client, the protocol server and the management library in the above method embodiments by calling the program in the memory. The processor here may be an integrated circuit with signal processing capabilities, such as a CPU. The protocol client, protocol server, management library may be implemented by one or more integrated circuits configured to implement the above methods. For example: one or more ASICs, or one or more microprocessors DSP, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Alternatively, the above implementations may be combined.
In particular, the functions/implementation processes of the units in fig. 4 to 5 can be implemented by the processor 610 in the communication device 600 shown in fig. 6 calling the computer executable instructions stored in the memory 620. Alternatively, the functions/implementation processes of the processing unit in fig. 4 to 5 may be implemented by the processor 610 in the communication apparatus 600 shown in fig. 6 calling a computer executing instruction stored in the memory 620, and the functions/implementation processes of the receiving unit or the transmitting unit in fig. 4 to 5 may be implemented by the interface 630 in the communication apparatus 600 shown in fig. 6.
It will be appreciated that the processing unit in the above-described apparatus comprises a processor coupled to a memory for storing computer programs or instructions or and/or data, the processor being configured to execute the computer programs or instructions and/or data stored by the memory such that the method in the above method embodiments is performed.
It should also be understood that the division of the units in the above apparatus is only a division of logical functions, and the actual implementation may be wholly or partially integrated into one physical entity, or may be physically separated. And the units in the device can be realized in the form of software called by the processing element; or may be implemented entirely in hardware; part of the units can also be implemented in the form of software invoked by a processing element and part of the units can be implemented in the form of hardware. For example, each unit may be a processing element separately set up, or may be implemented by being integrated into a chip of the apparatus, or may be stored in a memory in the form of a program, and a function of the unit may be called and executed by a processing element of the apparatus. The processing element, which may also be referred to herein as a processor, may be an integrated circuit having signal processing capabilities. In the implementation process, the steps of the method or the units above may be implemented by integrated logic circuits of hardware in a processor element or in a form called by software through the processor element.
An embodiment of the present application further provides a cloud desktop system, where the system includes: the protocol client, the protocol server and the management library.
The embodiment of the present application further provides a computer readable medium for storing a computer program code, where the computer program includes instructions for executing the communication method of the embodiment of the present application in the above-mentioned method. The readable medium may be a read-only memory (ROM) or a Random Access Memory (RAM), which is not limited in this embodiment of the present application.
The application also provides a computer program product, which comprises instructions that when executed cause the protocol client, the protocol server and the management library to execute the operations of the protocol client, the protocol server and the management library corresponding to the method.
An embodiment of the present application further provides a system chip, where the system chip includes: a processing unit, which may be, for example, a processor, and a communication unit, which may be, for example, an input/output interface, a pin or a circuit, etc. The processing unit can execute computer instructions to make a chip in the communication device execute any one of the above updating methods of the protocol client provided by the embodiments of the present application.
Optionally, the computer instructions are stored in a storage unit.
Alternatively, the storage unit is a storage unit in the chip, such as a register, a cache, and the like, and the storage unit may also be a storage unit located outside the chip in the terminal, such as a ROM or other types of static storage devices that can store static information and instructions, a RAM, and the like. The processor mentioned in any of the above may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of programs of the transmission method of the feedback information. The processing unit and the storage unit may be decoupled, and are respectively disposed on different physical devices, and are connected in a wired or wireless manner to implement respective functions of the processing unit and the storage unit, so as to support the system chip to implement various functions in the foregoing embodiments. Alternatively, the processing unit and the memory may be coupled to the same device.
It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a ROM, a Programmable Read Only Memory (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash memory. Volatile memory can be RAM, which acts as external cache memory. There are many different types of RAM, such as Static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synclink DRAM (SLDRAM), and direct bus RAM (DR RAM).
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (18)
1. A method for updating a protocol client is applied to a cloud desktop system, wherein the cloud desktop system comprises a protocol server and the protocol client, and the method comprises the following steps:
the protocol client sends first version information to the protocol server, wherein the first version information indicates the version information of the protocol client;
when the protocol server determines that the first version information is not matched with the version information of the protocol server, the protocol server sends indication information to the protocol client, wherein the indication information is used for indicating the protocol client to obtain a second version, and the version information of the second version is matched with the version information of the server;
the protocol client acquires the second version from a management library according to the indication information, wherein the management library comprises one or more versions of the protocol client;
and the protocol client loads the second version, so that the current version of the protocol client is updated to the second version.
2. The method of claim 1, wherein the indication information comprises version information of the second version.
3. The method of claim 1, wherein the indication information comprises version information of the protocol server.
4. The method of claim 3, wherein the protocol client obtains the second version from the management repository according to the indication information, and comprises:
the protocol client sends the version information of the protocol server to the management library, and the management library comprises the matching relation between the version information of the protocol client and the protocol server;
and the protocol client receives the second version, and the second version is determined according to the version information of the protocol server and the matching relationship between the version information of the protocol client and the protocol server.
5. A method for updating a protocol client, wherein the method is applied to the protocol client, and the method comprises:
sending first version information to a protocol server, wherein the first version information indicates version information of the protocol client;
receiving indication information sent by the protocol server, wherein the indication information is used for indicating the protocol client to acquire a second version, and the version information of the second version is matched with the version information of the protocol server;
obtaining the second version from a management library, wherein the management library comprises one or more versions of the protocol client;
and loading the acquired second version to update the current version of the protocol client to the second version.
6. The method of claim 5, wherein the indication information comprises version information of the second version.
7. The method of claim 5, wherein the indication information comprises version information of the protocol server.
8. The method of claim 7, wherein said obtaining the second version from the management repository comprises:
sending the version information of the protocol server to the management library, wherein the management library comprises the matching relation between the version information of the protocol client and the protocol server;
and receiving the second version, wherein the second version is determined according to the version information of the protocol server and the matching relationship between the version information of the protocol client and the protocol server.
9. A cloud desktop system, comprising:
the protocol client is used for sending first version information to the protocol server, and the first version information indicates the version information of the protocol client;
the protocol server is used for sending indication information to the protocol client when the protocol server determines that the first version information is not matched with the version information of the protocol server, wherein the indication information is used for indicating the protocol client to obtain a second version, and the version information of the second version is matched with the version information of the server;
the protocol client is used for acquiring the second version from a management library according to the indication information, wherein the management library comprises one or more versions of the protocol client;
the protocol client is used for loading the second version, so that the current version of the protocol client is updated to the second version.
10. The system of claim 9, wherein the indication information comprises version information of the second version.
11. The system according to claim 9, wherein the indication information includes version information of the protocol server.
12. The system of claim 11, wherein the protocol client is specifically configured to:
sending the version information of the protocol server to the management library, wherein the management library comprises the matching relationship between the version information of the protocol client and the protocol server;
and receiving the second version, wherein the second version is determined according to the version information of the protocol server and the matching relationship between the version information of the protocol client and the protocol server.
13. A protocol client, comprising:
a sending unit, configured to send first version information to a protocol server, where the first version information indicates version information of a protocol client;
a receiving unit, configured to receive indication information sent by the protocol server, where the indication information is used to indicate the protocol client to obtain a second version, and version information of the second version is matched with version information of the protocol server;
the processing unit is used for acquiring the second version from a management library, and the management library comprises one or more versions of the protocol client;
and the processing unit is used for loading the acquired second version so as to update the current version of the protocol client to the second version.
14. The apparatus of claim 13, wherein the indication information comprises version information of the second version.
15. The apparatus of claim 13, wherein the indication information comprises version information of the protocol server.
16. The apparatus according to claim 15, wherein the processing unit is specifically configured to:
sending the version information of the protocol server to the management library, wherein the management library comprises the matching relation between the version information of the protocol client and the protocol server;
and receiving the second version, wherein the second version is determined according to the version information of the protocol server and the matching relationship between the version information of the protocol client and the protocol server.
17. A computer-readable storage medium having stored thereon computer instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 8.
18. A chip system, comprising:
a processor coupled with a memory, the memory to store instructions;
the processor is used for calling and executing the instructions from the memory, so that the communication device provided with the chip system executes the method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111134146.1A CN115857981A (en) | 2021-09-27 | 2021-09-27 | Cloud native desktop protocol client updating method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111134146.1A CN115857981A (en) | 2021-09-27 | 2021-09-27 | Cloud native desktop protocol client updating method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115857981A true CN115857981A (en) | 2023-03-28 |
Family
ID=85652864
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111134146.1A Pending CN115857981A (en) | 2021-09-27 | 2021-09-27 | Cloud native desktop protocol client updating method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115857981A (en) |
-
2021
- 2021-09-27 CN CN202111134146.1A patent/CN115857981A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110032512B (en) | Debugging method of small program, related equipment and terminal | |
| US8589910B2 (en) | Coordinating firmware over-the-air updates for mobile devices utilizing presence information | |
| US7716661B2 (en) | Embedded device update service | |
| US8914793B2 (en) | Remote upgrade servers and load balancing methods thereof | |
| US11722880B2 (en) | Electronic subscriber identity module (eSIM) profile delivery and activation system and methods | |
| EP2919440A1 (en) | Advertisement processing method and device | |
| KR20210027400A (en) | Implementation of compliance settings by mobile devices to comply with configuration scenarios | |
| US20200120739A1 (en) | Method of switching connection to network, intelligent terminal, and apparatus having storage function | |
| US20210029759A1 (en) | Wireless communication method and network device | |
| US11678176B1 (en) | Electronic subscriber identity module (eSIM) transfer via activation code | |
| KR20200116519A (en) | Software update management method, server, terminal, device, and storage medium | |
| CN113360807B (en) | Page display method and device of mixed-mode mobile application and related equipment | |
| US11477751B2 (en) | Communication method, terminal device and medium | |
| US20140229550A1 (en) | Method and system for attaching scanned documents to email replies via a mobile communications device | |
| EP4145359A1 (en) | Method and apparatus for transferring machine learning model parameter | |
| CN113690981A (en) | Charging protocol determination method and device, electronic equipment and readable storage medium | |
| JP5462207B2 (en) | Device management method and apparatus | |
| US11006351B2 (en) | Wireless communication method and device | |
| CN105468706A (en) | Page display method and device | |
| CN115857981A (en) | Cloud native desktop protocol client updating method | |
| CN112084254A (en) | Data synchronization method and system | |
| WO2018121652A1 (en) | Method and device for connecting wireless access point through application in user equipment | |
| WO2019100344A1 (en) | Dual-registered terminal device wireless communication method, network device and terminal device | |
| CN115080068A (en) | Resource file transmission method, device, equipment and storage medium | |
| CN113779122B (en) | Method and device for exporting data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication |