CN110753091A - Cloud platform management method and device - Google Patents
Cloud platform management method and deviceDownload PDFInfo
- Publication number
- CN110753091A CN110753091ACN201910900506.0ACN201910900506ACN110753091ACN 110753091 ACN110753091 ACN 110753091ACN 201910900506 ACN201910900506 ACN 201910900506ACN 110753091 ACN110753091 ACN 110753091A
- Authority
- CN
- China
- Prior art keywords
- user information
- cloud platform
- client
- user
- server
- 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
- 238000007726management methodMethods0.000titleclaimsabstractdescription26
- 238000004891communicationMethods0.000claimsabstractdescription37
- 238000000034methodMethods0.000claimsabstractdescription35
- 238000012217deletionMethods0.000description5
- 230000037430deletionEffects0.000description5
- 238000010586diagramMethods0.000description4
- 238000004590computer programMethods0.000description2
- 238000005516engineering processMethods0.000description1
- 230000006870functionEffects0.000description1
Images
Classifications
- 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/10—Protocols in which an application is distributed across nodes in the network
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
- 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/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
Technical Field
The invention relates to the technical field of cloud computing, in particular to a cloud platform management method and device.
Background
The cloud computing service is that a large number of hardware resources distributed in a physical space are integrated through a virtualization technology to form a computing resource pool, the computing resource pool is provided for terminal equipment distributed in a geographic space, and the terminal equipment acquires a certain amount of computing resources from the computing resource pool according to computing requirements to complete computing tasks.
In the prior art, different cloud platforms may respectively provide computing resources for a user, for example, different cloud platforms such as an aricloud, a hundredth cloud, and a huashanyun cloud may all provide computing resources for a user. During actual use, a user can register user information on a plurality of cloud platforms at the same time, and can log in different cloud platforms respectively through the user information to use computing resources provided by the different cloud platforms. When a user uses computing resources provided by different cloud platforms, the different cloud platforms are independent from each other, and the user needs to establish connection with each cloud platform through a client of each cloud platform respectively so as to use the computing resources provided by each cloud platform respectively. When a plurality of cloud platforms are used by a user, the client sides of the cloud platforms need to be switched frequently, so that the operation is complex, and the user is inconvenient to use.
Disclosure of Invention
In view of the above, the present invention is proposed to provide a cloud platform management method and apparatus that overcomes or at least partially solves the above problems.
In a first aspect of the embodiments of the present invention, a cloud platform management method, executed on a server, includes:
receiving a first login request sent by a client, wherein the first login request comprises first user information of a user;
responding to the first login request, and establishing a communication connection with the client;
determining the identification of a target cloud platform associated with the first user information according to at least one piece of stored user information and the identification of the cloud platform associated with each piece of user information;
and sending the first user information to the target cloud platform associated with the identification of the target cloud platform so as to log in the target cloud platform.
In a second aspect of the embodiments of the present invention, there is provided a cloud platform management apparatus, which is disposed in a server, and includes:
the system comprises a receiving module, a sending module and a sending module, wherein the receiving module is used for receiving a first login request sent by a client, and the first login request comprises first user information of a user;
the establishing module is used for responding to the first login request and establishing communication connection with the client;
the determining module is used for determining the identification of the target cloud platform associated with the first user information according to the stored at least one piece of user information and the identification of the cloud platform associated with each piece of user information;
and the sending module is used for sending the first user information to the target cloud platform associated with the identifier of the target cloud platform so as to log in the target cloud platform.
In the embodiment of the invention, a first login request sent by a client is received, wherein the first login request comprises first user information of a user; responding to the first login request, and establishing communication connection with the client; determining the identification of a target cloud platform associated with the first user information according to the stored at least one piece of user information and the identification of the cloud platform associated with each piece of user information; and sending first user information to the target cloud platform associated with the identification of the target cloud platform so as to log in the target cloud platform. The server is arranged between the client and the cloud platforms, different cloud platforms are logged in through the server, switching between different cloud platforms is achieved, users can be prevented from switching between the clients of different cloud platforms, user operation is simplified, and the users can manage the cloud platforms conveniently.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a flowchart of a cloud platform management method according to an exemplary embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a multi-cloud platform according to an exemplary embodiment of the present invention;
FIG. 3 is a flowchart of another cloud platform management method provided by an exemplary embodiment of the invention;
fig. 4 is a block diagram illustrating a structure of a cloud platform management apparatus according to an exemplary embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Referring to fig. 1, fig. 1 is a flowchart of a cloud platform management method, which is executed in a server and may be suitable for managing multiple cloud platforms of a user to simplify an operation of the user on the multiple cloud platforms, according to an exemplary embodiment of the present invention. The cloud platform management method provided in this embodiment may be executed by a cloud platform management apparatus, where the cloud platform management apparatus is usually implemented in a software and/or hardware manner, and the cloud platform management apparatus may be deployed in a server, and the method specifically may include the following steps:
The client can be a client installed in a terminal such as a mobile phone, a computer, a tablet computer and the like and used for a user to operate, and the client can respond to the operation of the user in a user interface of the client and send a first login request to the server. The method for sending the first login request from the client to the server may refer to a method for sending a login request from the client to the server in the prior art, which is not limited in this embodiment. The first user information may be one of a plurality of user information registered by the user in different cloud platforms, and the user may log in the corresponding cloud platform using the user information. The cloud platform can provide computing resources for the user, and the user completes computing tasks by using the computing resources provided by the cloud platform. For example, referring to fig. 2, fig. 2 is a schematic structural diagram of a multi-cloud platform according to an exemplary embodiment of the present invention, as shown in fig. 2, a user 1 may register user information a on a first cloud platform, register user information B on a second cloud platform, and register user information C on the first cloud platform and register user information D on the second cloud platform. At this time, the user 1 may log in the first cloud platform through the user information a, use the computing resources provided by the first cloud platform, log in the second cloud platform through the user information B, and use the computing resources provided by the second cloud platform. Similarly, the user 2 may log in the first cloud platform through the user information C, use the computing resources provided by the first cloud platform, log in the second cloud platform through the user information D, and use the computing resources provided by the second cloud platform. Specifically, the user information may include an account of the cloud platform registered in the corresponding cloud platform by the user and a password set for the account by the user. In actual use, data included in the user information can be set according to requirements, the number of the cloud platforms can also be set according to requirements, and this embodiment does not limit this.
In this embodiment, the server may receive the first login request sent by the client, analyze the first login request, and determine first user information of the user included in the first login request. The server receives the first login request sent by the client, and refers to a process of receiving and analyzing the login request by the server in the prior art, which is not limited in this embodiment.
In this embodiment, after the server receives the first login request sent by the client and determines the first user information of the user included in the first login request, the server may verify the first user information and determine whether the server stores the first user information, and if the server stores the first user information, the server establishes a communication connection with the client, and allows the client to log in the server through the first user information.
For example, instep 101, when the server receives a first login request sent by the client (the first login request is a login request sent by the client in response to an operation of the user 1 in the user interface of the client), and after determining that first user information included in the first login request is user information a, if the user information a is stored in the server, the server establishes a communication connection with the client, and allows the client to log in the server through the first user information (user information a).
The identification of the cloud platform is identification information which is stored in the server and is used for uniquely identifying the cloud platform, and the target cloud platform is a cloud platform which is associated with the first user information included in the first login request.
In this embodiment, the server may pre-store each piece of user information, set an identifier of each cloud platform, and store identifiers of cloud platforms associated with each piece of user information (in combination withstep 101, the user information is associated with the cloud platform, that is, the user information is user information registered by the user in the cloud platform). When the server receives the first login request and determines first user information included in the first login request, the server may search for an identifier of the cloud platform associated with the first user information and determine a target cloud platform.
For example, in combination withsteps 101 to 102, the server may preset an identifier X of the first cloud platform and an identifier Y of the second cloud platform, and may preset user information a and an identifier X of the first cloud platform associated with the user information a. Similarly, the server may store the user information B, the user information C, and the user information D, and the identifiers of the cloud platforms associated with the user information B, the user information C, and the user information D, respectively. After receiving the first login request, if the first user information included in the first login request is user information a, the server may determine that the target cloud platform is the first cloud platform and the identifier of the target cloud platform is X according to the pre-stored user information a and the identifier X of the first cloud platform associated with the user information a. The process of the first login request including the user information B, the user information C, and the user information D is the same as that of the user information a, which is not described herein again in this embodiment.
And 104, sending first user information to the target cloud platform associated with the identification of the target cloud platform so as to log in the target cloud platform.
In this embodiment, after the server determines the identifier of the target cloud platform associated with the first user information included in the first login request, the server may send the first user information to the target cloud platform corresponding to the identifier of the target cloud platform to log in the target cloud platform.
For example, with reference tosteps 101 to 103, when the first user information included in the first login request is user information a, and the server determines that the identifier of the target cloud platform associated with the user information a is X, the server may send the user information a to the first cloud platform associated with the identifier X according to the identifier X to log in the first cloud platform. Similarly, if the server determines that the identifier of the target cloud platform is Y, the server may send the user information B to the second cloud platform associated with the identifier Y to log in the second cloud platform. The process of the user 2 logging in the server using the client is the same as that of the user 1, and the description of this embodiment is omitted here.
In this embodiment, after receiving first user information sent by a server, a target cloud platform may verify the first user information, and when the first user information is user information registered by a user in the cloud platform, establish a communication connection with the server, and allow the server to log in the target cloud platform. For example, with reference tosteps 101 to 103, if the first cloud platform receives that the first user information sent by the server is the user information a, and at this time, the user information a is user information registered by the user 1 in the first cloud platform, the first cloud platform establishes a communication connection with the server, and allows the server to log in the first cloud platform. The target cloud platform verifies the first user information, and the process of establishing the communication connection with the server may refer to the prior art, which is not limited in this embodiment. The process of receiving the first user information sent by the server by the second cloud platform is the same as that of the first cloud platform, and details are not repeated here in this embodiment.
As shown in fig. 2, in the prior art, after a user 1 registers user information a and user information B in a first cloud platform and a second cloud platform respectively, the user 1 can only input the user information a in a client of the first cloud platform, log in the first cloud platform, and use computing resources provided by the first cloud platform; and inputting user information B at the client side of the second cloud platform, logging in the second cloud platform, and using the computing resources provided by the second cloud platform. The user 1 needs to switch between the client of the first cloud platform and the client of the second cloud platform, and when the number of the cloud platforms is large, the operation is complex, and the user is not convenient to manage the cloud platforms.
In this embodiment, as shown in fig. 2, a server is provided between a client and a cloud platform, the client logs in the server first, then logs in different cloud platforms through the server, and the server realizes switching between different cloud platforms. When a user logs in different cloud platforms, user information registered by the user in different cloud platforms can be input in the same client so as to log in the corresponding cloud platforms. For example, if the user 1 inputs the user information a at the client, the server logs in the first cloud platform to realize the login of the user 1 to the first cloud platform; and if the user 1 inputs the user information B at the client, the server logs in the second cloud platform, and the user 1 logs in the second cloud platform. When the number of the cloud platforms registered by the user 1 is large, different cloud platforms can be logged in through one client, switching between the clients of different cloud platforms is avoided, user operation is simplified, and the user can conveniently manage the cloud platforms.
In the embodiment, a first login request sent by a client is received, wherein the first login request comprises first user information of a user; responding to the first login request, and establishing communication connection with the client; determining the identification of a target cloud platform associated with the first user information according to the stored at least one piece of user information and the identification of the cloud platform associated with each piece of user information; and sending first user information to the target cloud platform associated with the identification of the target cloud platform so as to log in the target cloud platform. The server is arranged between the client and the cloud platforms, different cloud platforms are logged in through the server, switching between different cloud platforms is achieved, users can be prevented from switching between the clients of different cloud platforms, user operation is simplified, and the users can manage the cloud platforms conveniently.
Referring to fig. 3, fig. 3 is a flowchart of another cloud platform management method, which is executed on a server and may be adapted to manage multiple cloud platforms of a user to simplify an operation of the user on the multiple cloud platforms, according to an exemplary embodiment of the present invention. The cloud platform management method provided in this embodiment may be executed by a cloud platform management apparatus, where the cloud platform management apparatus is usually implemented in a software and/or hardware manner, and the cloud platform management apparatus may be deployed in a server, and the method specifically may include the following steps:
In this embodiment, the second user information is user information created in the server by the user, and the user can log in the server through the second user information. For example, in connection withstep 101, if the user 1 creates the second user information L in the server, the user 1 can log in the server through the second user information L. Similarly, if the user 2 creates the second user information M on the server, the user 2 can log in the server through the second user information M. Specifically, the second user information may include an account number created in the server by the user and a password set by the user for the account number. In actual use, the data included in the second user information may be set according to requirements, which is not limited in this embodiment. The process of sending the second login request to the server by the client is the same as the process of sending the first login request, which is not described herein in detail in this embodiment.
In this embodiment, the server may receive the second login request sent by the client, analyze the second login request, and determine the second user information included in the second login request. The server receives the second login request sent by the client, and analyzes the second login request, which may refer to the process of receiving and analyzing the login request by the server in the prior art, and this embodiment does not limit this.
In this embodiment, after receiving a second login request sent by a client and determining second user information included in the second login request, a server may verify the second user information, and if the second user information is user information created by a user in the server, the server establishes a communication connection with the client, and allows the client to log in the server through the second user information.
For example, in connection withstep 301, when the server receives a second login request sent by the client (the second login request is a login request sent by the client in response to an operation of the user 1 in the user interface of the client), and determines that second user information included in the second login request is second user information L, and the second user information L is user information created by the user 1 in the server, the server establishes a communication connection with the client, and allows the client to log in the server through the second user information L.
In this embodiment, after the server establishes a communication connection with the client according to the second user information included in the second login request, the server may receive at least one piece of user information sent by the client. Specifically, a user can operate a user interface in the client, input at least one piece of user information in the user interface of the client, click and send the user information, the client responds to the click and send operation and sends the at least one piece of user information to the server, and the server receives the at least one piece of user information sent by the client.
For example, in combination withsteps
In this embodiment, the server receives at least one piece of user information sent by the client, and stores each piece of received user information. The server receives and stores the user information sent by the client, which is not limited in this embodiment, referring to the prior art.
And step 304, storing the association relationship between the second user information and each user information.
In this embodiment, after the server responds to the second login request and establishes a communication connection with the client according to the second user information included in the second login request, the server may receive at least one piece of user information sent by the client, and establish and store an association relationship between the second user information and each piece of received user information.
For example, in combination withsteps 101 to 104, and steps 301 to 303, after receiving the user information a and the user information B sent by the client, the server may establish and store an association relationship between the second user information L and the user information a and the user information B, respectively. Specifically, the server may establish a list 1 for the second user information L, and add the user information a and the user information B to the list 1 to establish an association relationship between the second user information L and the user information a and the user information B, respectively. Similarly, list 2 may be established for user 2, and user information C and user information D may be added to list 2. In practical use, the user information a and the user information B may be sent simultaneously or separately, and the association between the second user information L and the user information a, the association between the second user information L and the user information B, or the association between the second user information L and the user information a and the user information B may be established simultaneously.
In this embodiment, after the user logs in the server through the second user information, the user information associated with the second user information may be managed. For example, after the user 1 logs in the server through the second user information L, the user information registered by the user 1 on another cloud platform may be added, or the already established association relationship between the second user information L and the user information a may be deleted.
Optionally, after receiving the at least one piece of user information sent by the client, the server may determine, according to the stored at least one piece of user information and the identifier of the cloud platform associated with each piece of user information, the identifier of the cloud platform associated with each piece of received user information, and establish and store the second user information of the user, the user information, and the association relationship between the identifiers of the cloud platforms corresponding to each piece of user information.
For example, in combination withsteps 101 to 104, and steps 301 to 303, when the server receives the user information a and the user information B, the server may establish and store an association relationship between the second user information L and the user information a, and an identifier X of the first cloud platform corresponding to the user information a, and establish and store an association relationship between the second user information L and the user information B, and an identifier of the second cloud platform Y corresponding to the user information B. Specifically, the server may establish a list 3 for the second user information L, add the user information a to the list 3, and add the identifier X associated with the user information a; similarly, the server may add user information B to list 3, add identifier Y associated with user information B, and store list 3. Similarly, a list 4 may be created for the user 2, and the user information C and the user information D may be added to the list 4, and the identifier X and the identifier Y associated with the user information C and the user information D, respectively. The server establishes and stores the second user information, the user information and the association relationship between the cloud platform identifications corresponding to each user information, so that the server can manage the user information associated with the second user information conveniently, and the server can search the cloud platform identifications associated with the user information conveniently according to the user information.
It should be noted that, the association relationship between the second user information and the identifier of the cloud platform corresponding to the user information may be any form of association relationship, which is not limited in this embodiment.
In this embodiment, after receiving the second login request and establishing the communication connection with the client, the server may receive a disconnection request sent by the client, disconnect the communication connection with the client, receive the first login request sent by the client, and establish the communication connection with the client again. The process of the server receiving the first login request sent by the client may refer to step 101, which is not described herein again in this embodiment.
In this embodiment, after receiving the first login request, the server may determine, according to an association relationship between the second user information and each piece of user information that is established in advance, whether the first user information included in the first login request is one piece of user information of all pieces of user information associated with the second user information, and if the first user information is the piece of user information associated with the second user information, establish a communication connection with the client.
For example, in combination withstep 304, when the first user information included in the first login request received by the server is user information a, the server may determine, according to the pre-established and stored association relationship between the second user information L and the user information a and the user information B, that the user information a is user information associated with the second user information L, and at this time, the server may establish a communication connection with the client, and allow the client to log in the server through the first user information (user information a). Specifically, the server may determine whether the user information a is stored in table 1, table 2, table 3, and table 4, and if the first user information (user information a) is stored in table 1, table 2, table 3, or table 4, the server establishes a communication connection with the client, and allows the client to log in the server through the first user information (user information a). The process of receiving the user information B, the user information C, and the user information D by the server is the same as that of the user information a, and is not described herein again.
This step is the same asstep 103, and reference may be made to step 103 for understanding thecomparison step 307, which is not described herein again.
And 308, sending first user information to the target cloud platform associated with the identification of the target cloud platform so as to log in the target cloud platform.
In this embodiment, the identifier of the cloud platform may be a domain name or an IP address of the cloud platform. For example, in connection withsteps 101 to 104, and steps 301 to 307, the identifier X of the first cloud platform may be the IP address of the first cloud platform. When the server determines that the identifier of the target cloud platform is the IP address of the first cloud platform (identifier of the first cloud platform), the server may directly send the first user information to the IP address to log in the first cloud platform. During actual use, the identification of the cloud platform can be in any form, and after the server determines the identification of the target cloud platform, the server can send first user information to the cloud platform corresponding to the identification so as to log in the target cloud platform.
Optionally, the method may further include: sending a data request to each cloud platform to acquire user information stored in each cloud platform; receiving user information sent by each cloud platform; and storing the user information sent by each cloud platform and the identification of the cloud platform respectively associated with each user information.
In this embodiment, the server may send a data request to each cloud platform to obtain the user information stored in each cloud platform. For example, in combination withsteps 101 to 104, and steps 301 to 308, the server may send a data request to the first cloud platform, and obtain the user information a and the user information C stored in the first cloud platform. Similarly, the server may send a data request to the second cloud platform to obtain the user information B and the user information D stored in the second cloud platform.
In this embodiment, after sending the data request to each cloud platform, the server may receive the user information sent by each cloud platform, store the received user information, and store the identifier of the cloud platform associated with each user information. For example, after sending a data request to the first cloud platform, the server receives user information a and user information C sent by the first cloud platform, stores the user information a and the user information C, and respectively stores an identifier X of the first cloud platform associated with the user information a and an identifier X of the first cloud platform associated with the user information C (the user information a and the user information C are sent by the first cloud platform, and the server may determine the identifier of the cloud platform associated with each user information according to the cloud platform sending the user information). Similarly, after sending the data request to the second cloud platform, the server may receive the user information B and the user information D sent by the second cloud platform, store the user information B and the user information D, and respectively store the identifiers Y of the second cloud platform, which are respectively associated with the user information B and the user information D. The server acquires the user information from the cloud platforms and determines the identification of the cloud platform associated with each user information, so that the user can be prevented from manually inputting the user information and the identification of the cloud platform associated with each user information through the client, and the user operation is simplified.
In this embodiment, the server may send data requests to different cloud platforms according to predetermined time, and obtain user information stored in each cloud platform. For example, the server may send data requests to the first cloud platform and the second cloud platform every 1 hour or 2 hours, and obtain the user information stored in the first cloud platform and the second cloud platform. In actual use, the predetermined time may be set according to requirements, and this embodiment does not limit this.
In this embodiment, the server may also send a data request to each cloud platform in response to an acquisition request sent by the client after receiving the acquisition request, so as to acquire the user information stored in each cloud platform. For example, with reference tosteps 101 to 104, and steps 301 to 308, after the server establishes a communication connection with the client according to the second user information L in the second login request, the server may receive an acquisition request sent by the client (the acquisition request is an acquisition request sent by the client in response to an operation of the user 1 in the user interface of the client), send a data request to the first cloud platform and the second cloud platform, and acquire the user information stored in the first cloud platform and the second cloud platform. Specifically, the user 1 may click an acquisition button in a user interface of the client, the client responds to the click operation of the user 1 and sends an acquisition request to the server, and the server receives the acquisition request and then sends a data request to the first cloud platform and the second cloud platform.
In this embodiment, the server sends the data request to the cloud platform according to a predetermined time or in response to an acquisition request sent by the client to acquire the user information, and can acquire the user information stored in each cloud platform in time and update the user information stored in the server, thereby avoiding that the operation of the user is affected when the user information does not exist in the server.
Optionally, after logging in the target cloud platform, the method further includes: receiving an operation request sent by a client, wherein the operation request is acquired by the client in response to the operation of a user on a user interface of the client; and sending an operation request to the target cloud platform so that the target cloud platform responds to the operation request and executes the operation corresponding to the operation request.
In this embodiment, the server sends the first user information of the user to the target cloud platform, and after logging in the target cloud platform, the server establishes communication connection with the client and the target cloud platform respectively. At this time, the server may receive an operation request sent by the client, and forward the operation request to the target cloud platform, so that the target cloud platform executes a corresponding operation after receiving the operation request. For example, in combination withsteps 301 to 308, after the server logs in the first cloud platform, the user 1 may select, in the user interface of the client, data stored in the first cloud platform by the user 1, and click a delete button. The client sends a deletion request to the server in response to the click deletion operation of the user 1. And after receiving the deletion request, the server sends the deletion request to the first cloud platform. The first cloud platform may delete the corresponding data stored by the user 1 in the first cloud platform in response to the deletion request. In actual use, the operation request sent by the client may be any operation request, such as a download request, a save request, a create request, and the like. The process that the client sends the operation request to the server, and the server receives the operation request and sends the operation request to the target server may refer to a process that the server receives and forwards the operation request in the prior art, which is not limited in this embodiment.
Optionally, after sending the operation request to the target cloud platform, the method further includes: receiving a response message sent by the target cloud platform, wherein the response message is returned after the target cloud platform executes the operation corresponding to the operation request; and sending a response message to the client.
In this embodiment, after sending the operation request to the target cloud platform, the server may receive a response message returned after the target cloud platform executes the operation request, and send the response message to the client. For example, in combination withsteps 301 to 308, after the server logs in the first cloud platform, the user 1 may select, in the user interface of the client, data stored in the first cloud platform by the user 1, and click a download button. The client side responds to the click downloading operation of the user 1 and sends a downloading request to the server, and the server receives the downloading request and sends the downloading request to the first cloud platform. The first cloud platform can respond to the downloading request and send data corresponding to the downloading request to the server. And after receiving the data sent by the first cloud platform, the server sends the data to the client. The process of the server receiving the response message sent by the cloud platform and sending the response message to the client may refer to a process of the server receiving and forwarding the response message in the prior art, which is not limited in this embodiment.
In this embodiment, the server receives a second login request sent by the client, establishes a communication connection with the client, receives at least one piece of user information sent by the client, and establishes and stores an association relationship between the second user information and each piece of user information. After a first login request sent by a client is received, establishing communication connection with the client, determining an identifier of a target cloud platform associated with first user information according to at least one piece of stored user information and identifiers of cloud platforms associated with each piece of user information, and sending the first user information to the target cloud platform associated with the identifier of the target cloud platform so as to login the target cloud platform. In the embodiment, the server is arranged between the client and the cloud platform, and different cloud platforms are logged in through the server, so that switching between different cloud platforms is realized, users can be prevented from switching between clients of different cloud platforms, user operation is simplified, and the users can manage the cloud platforms conveniently. Meanwhile, the second user information is used for managing the user information registered in the cloud platforms, so that the user can conveniently manage the cloud platforms. Meanwhile, after the server establishes communication connection with the client and the target cloud platform respectively, the server can forward data sent by the client to the target cloud platform and forward the data sent by the target cloud platform to the client, so that the communication connection between the client and the target cloud platform is realized, and a user can conveniently use computing resources provided by the cloud platform.
Referring to fig. 4, fig. 4 is a block diagram illustrating a structure of a cloud platform management apparatus according to an exemplary embodiment of the present invention, where the cloudplatform management apparatus 400 may be deployed in a server, and specifically may include the following modules: a receivingmodule 401, a establishingmodule 402, a determiningmodule 403 and a sendingmodule 404.
The receivingmodule 401 is configured to receive a first login request sent by a client, where the first login request includes first user information of a user.
The establishingmodule 402 is configured to establish a communication connection with a client in response to a first login request.
The determiningmodule 403 is configured to determine, according to the stored at least one piece of user information and the identifier of the cloud platform associated with each piece of user information, the identifier of the target cloud platform associated with the first piece of user information.
The sendingmodule 404 is configured to send the first user information to the target cloud platform associated with the identifier of the target cloud platform, so as to log in the target cloud platform.
In the embodiment, a first login request sent by a client is received, wherein the first login request comprises first user information of a user; responding to the first login request, and establishing communication connection with the client; determining the identification of a target cloud platform associated with the first user information according to the stored at least one piece of user information and the identification of the cloud platform associated with each piece of user information; and sending first user information to the target cloud platform associated with the identification of the target cloud platform so as to log in the target cloud platform. The server is arranged between the client and the cloud platforms, different cloud platforms are logged in through the server, switching between different cloud platforms is achieved, users can be prevented from switching between the clients of different cloud platforms, user operation is simplified, and the users can manage the cloud platforms conveniently.
Optionally, the receivingmodule 401 is further configured to receive a second login request sent by the client, where the second login request includes second user information of the user.
The establishingmodule 402 is further configured to establish a communication connection with the client in response to the second login request.
The receivingmodule 401 is further configured to receive at least one piece of user information sent by the client.
The apparatus may further include a storage module configured to store an association relationship between the second user information and each user information.
Optionally, the sendingmodule 404 is further configured to send a data request to each cloud platform to obtain the user information stored in each cloud platform.
The receivingmodule 401 is further configured to receive user information sent by each cloud platform.
The storage module is further used for storing the user information sent by each cloud platform and the identification of the cloud platform respectively associated with each user information.
Optionally, the receivingmodule 401 is further configured to receive an operation request sent by the client after logging in the target cloud platform, where the operation request is obtained by the client in response to an operation of the user on a user interface of the client.
The sendingmodule 404 is further configured to send an operation request to the target cloud platform, so that the target cloud platform performs an operation corresponding to the operation request in response to the operation request.
Optionally, the receivingmodule 401 is further configured to receive a response message sent by the target cloud platform after sending the operation request to the target cloud platform, where the response message is returned after the target cloud platform executes the operation corresponding to the operation request.
The sendingmodule 404 is further configured to send a response message to the client.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components in the cloud platform management method and apparatus device according to embodiments of the present invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
Claims (10)
1. A cloud platform management method is executed in a server and comprises the following steps:
receiving a first login request sent by a client, wherein the first login request comprises first user information of a user;
responding to the first login request, and establishing a communication connection with the client;
determining the identification of a target cloud platform associated with the first user information according to at least one piece of stored user information and the identification of the cloud platform associated with each piece of user information;
and sending the first user information to the target cloud platform associated with the identification of the target cloud platform so as to log in the target cloud platform.
2. The method of claim 1, further comprising:
receiving a second login request sent by the client, wherein the second login request comprises second user information of the user;
responding to the second login request, and establishing a communication connection with the client;
receiving at least one piece of user information sent by the client;
and storing the association relationship between the second user information and each user information.
3. The method of claim 1, further comprising:
sending a data request to each cloud platform to acquire the user information stored in each cloud platform;
receiving the user information sent by each cloud platform;
and storing the user information sent by each cloud platform and the identification of the cloud platform respectively associated with each user information.
4. The method of claim 1, further comprising, after said logging into said target cloud platform:
receiving an operation request sent by the client, wherein the operation request is obtained by the client in response to the operation of the user on a user interface of the client;
sending the operation request to the target cloud platform so that the target cloud platform responds to the operation request and executes the operation corresponding to the operation request.
5. The method of claim 4, further comprising, after the sending the operation request to the target cloud platform:
receiving a response message sent by the target cloud platform, wherein the response message is returned after the target cloud platform executes the operation corresponding to the operation request;
and sending the response message to the client.
6. The utility model provides a cloud platform management device which characterized in that sets up in the server, includes:
the system comprises a receiving module, a sending module and a sending module, wherein the receiving module is used for receiving a first login request sent by a client, and the first login request comprises first user information of a user;
the establishing module is used for responding to the first login request and establishing communication connection with the client;
the determining module is used for determining the identification of the target cloud platform associated with the first user information according to the stored at least one piece of user information and the identification of the cloud platform associated with each piece of user information;
and the sending module is used for sending the first user information to the target cloud platform associated with the identifier of the target cloud platform so as to log in the target cloud platform.
7. The apparatus of claim 6,
the receiving module is further configured to receive a second login request sent by the client, where the second login request includes second user information of the user;
the establishing module is further used for responding to the second login request and establishing communication connection with the client;
the receiving module is further configured to receive at least one piece of user information sent by the client;
the device further comprises a storage module used for storing the association relationship between the second user information and each user information.
8. The apparatus of claim 6,
the sending module is further configured to send a data request to each cloud platform to obtain the user information stored in each cloud platform;
the receiving module is further configured to receive the user information sent by each cloud platform;
the storage module is further configured to store the user information sent by each cloud platform and an identifier of the cloud platform associated with each user information.
9. The apparatus of claim 6,
the receiving module is further configured to receive an operation request sent by the client after the client logs in the target cloud platform, where the operation request is obtained by the client in response to an operation of the user on a user interface of the client;
the sending module is further configured to send the operation request to the target cloud platform, so that the target cloud platform responds to the operation request and executes an operation corresponding to the operation request.
10. The apparatus of claim 9,
the receiving module is further configured to receive a response message sent by the target cloud platform after the operation request is sent to the target cloud platform, where the response message is returned after the operation corresponding to the operation request is executed by the target cloud platform;
the sending module is further configured to send the response message to the client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910900506.0ACN110753091A (en) | 2019-09-23 | 2019-09-23 | Cloud platform management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910900506.0ACN110753091A (en) | 2019-09-23 | 2019-09-23 | Cloud platform management method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110753091Atrue CN110753091A (en) | 2020-02-04 |
Family
ID=69276941
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910900506.0APendingCN110753091A (en) | 2019-09-23 | 2019-09-23 | Cloud platform management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110753091A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111866091A (en)* | 2020-06-30 | 2020-10-30 | 海尔优家智能科技（北京）有限公司 | Method, device, server and system for information interaction of cloud platform |
| CN112034806A (en)* | 2020-09-11 | 2020-12-04 | 上海庆科信息技术有限公司 | Module burning authorization tracking system, module burning method and device |
| CN112034808A (en)* | 2020-09-11 | 2020-12-04 | 上海庆科信息技术有限公司 | Module burning authorization tracking system, module burning information adjusting method and device |
| CN112034807A (en)* | 2020-09-11 | 2020-12-04 | 上海庆科信息技术有限公司 | Module burning authorization tracking system, module burning method and device |
| CN112532723A (en)* | 2020-11-27 | 2021-03-19 | 北京浪潮数据技术有限公司 | Account management method, cloud management layer, equipment and medium |
| CN113835880A (en)* | 2021-09-03 | 2021-12-24 | 新奇点智能科技集团有限公司 | A data processing method and device |
| CN114598555A (en)* | 2022-05-09 | 2022-06-07 | 飞天诚信科技股份有限公司 | Broadcast implementation method and system with switchable different platforms |
| CN115396500A (en)* | 2022-08-26 | 2022-11-25 | 中国电信股份有限公司 | Service platform switching method and system based on private network and electronic equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105429929A (en)* | 2014-09-04 | 2016-03-23 | 腾讯科技（北京）有限公司 | Information processing method, client, server and information processing system |
| WO2017107956A1 (en)* | 2015-12-23 | 2017-06-29 | 北京奇虎科技有限公司 | Data processing method, client and server |
| CN107181808A (en)* | 2017-06-01 | 2017-09-19 | 安徽祥云科技有限公司 | A kind of privately owned cloud system and operation method |
| US20180270219A1 (en)* | 2017-03-17 | 2018-09-20 | Verizon Patent And Licensing Inc. | System and method for centralized authentication and authorization for cloud platform with multiple deployments |
| CN108965480A (en)* | 2018-09-07 | 2018-12-07 | 平安科技（深圳）有限公司 | Cloud desktop login management-control method, device and computer readable storage medium |
| CN109067712A (en)* | 2018-07-16 | 2018-12-21 | 成都亚信网络安全产业技术研究院有限公司 | A kind of user cloud data guard method and proxy server |
- 2019
- 2019-09-23CNCN201910900506.0Apatent/CN110753091A/enactivePending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105429929A (en)* | 2014-09-04 | 2016-03-23 | 腾讯科技（北京）有限公司 | Information processing method, client, server and information processing system |
| WO2017107956A1 (en)* | 2015-12-23 | 2017-06-29 | 北京奇虎科技有限公司 | Data processing method, client and server |
| US20180270219A1 (en)* | 2017-03-17 | 2018-09-20 | Verizon Patent And Licensing Inc. | System and method for centralized authentication and authorization for cloud platform with multiple deployments |
| CN107181808A (en)* | 2017-06-01 | 2017-09-19 | 安徽祥云科技有限公司 | A kind of privately owned cloud system and operation method |
| CN109067712A (en)* | 2018-07-16 | 2018-12-21 | 成都亚信网络安全产业技术研究院有限公司 | A kind of user cloud data guard method and proxy server |
| CN108965480A (en)* | 2018-09-07 | 2018-12-07 | 平安科技（深圳）有限公司 | Cloud desktop login management-control method, device and computer readable storage medium |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111866091A (en)* | 2020-06-30 | 2020-10-30 | 海尔优家智能科技（北京）有限公司 | Method, device, server and system for information interaction of cloud platform |
| CN111866091B (en)* | 2020-06-30 | 2023-10-31 | 海尔优家智能科技（北京）有限公司 | Method, device, server and system for cloud platform information interaction |
| CN112034806A (en)* | 2020-09-11 | 2020-12-04 | 上海庆科信息技术有限公司 | Module burning authorization tracking system, module burning method and device |
| CN112034808A (en)* | 2020-09-11 | 2020-12-04 | 上海庆科信息技术有限公司 | Module burning authorization tracking system, module burning information adjusting method and device |
| CN112034807A (en)* | 2020-09-11 | 2020-12-04 | 上海庆科信息技术有限公司 | Module burning authorization tracking system, module burning method and device |
| CN112532723A (en)* | 2020-11-27 | 2021-03-19 | 北京浪潮数据技术有限公司 | Account management method, cloud management layer, equipment and medium |
| CN113835880A (en)* | 2021-09-03 | 2021-12-24 | 新奇点智能科技集团有限公司 | A data processing method and device |
| CN114598555A (en)* | 2022-05-09 | 2022-06-07 | 飞天诚信科技股份有限公司 | Broadcast implementation method and system with switchable different platforms |
| CN115396500A (en)* | 2022-08-26 | 2022-11-25 | 中国电信股份有限公司 | Service platform switching method and system based on private network and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110753091A (en) | Cloud platform management method and device | |
| US10708390B2 (en) | Method, user equipment, server, and apparatus for implementing information sharing | |
| US10999721B2 (en) | Communication identifier binding processing method and terminal | |
| US20170230481A1 (en) | Method, Apparatus And Non-Transitory Computer Storage Medium For Migrating Application Data Between Terminals | |
| CN104253686B (en) | Method, equipment and the system that account logs in | |
| CN110855772B (en) | Cross-device data storage method, system, device, server and medium | |
| WO2016119631A1 (en) | Method for accessing cloud service and access device | |
| CN103298072A (en) | Method, system and mobile communication terminal for automatically connecting to WiFi access point | |
| CN104092596B (en) | A kind of management method, Apparatus and system of music groups of users | |
| CN110231965B (en) | Cloud device, application processing method and electronic device | |
| CN113014681A (en) | Network card binding method and device of multi-network card server, electronic equipment and storage medium | |
| CN111600772B (en) | Network distribution content detection processing device, method, system and electronic equipment | |
| CN110365692A (en) | A kind of server log method and system | |
| CN109274584A (en) | Cut-in method, device, client device and the storage medium of access server | |
| WO2017113359A1 (en) | Cloud operation interface sharing method, related device and system | |
| CN103902339A (en) | Application installation method, terminal and server | |
| CN112019366A (en) | Leasing method, device, cloud platform and readable storage medium of physical host | |
| CN103595782A (en) | Distributed storage system and method for downloading files thereof | |
| CN112333289A (en) | Reverse proxy access method, device, electronic equipment and storage medium | |
| CN104023055A (en) | Video sharing method and system, and terminal device | |
| CN110708360A (en) | An information processing method, system and electronic device | |
| CN112929224A (en) | Network distribution method and device of equipment, server and computer readable storage medium | |
| CN103716230A (en) | Message sending method, device and server | |
| CN112738019A (en) | Method and device for displaying device information, storage medium and electronic device | |
| CN104135503B (en) | Method, Apparatus and system that data are downloaded |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | Effective date of registration:20211026 Address after:Room 122, floor 1, building 1, No. 2, Jingyuan street, Beijing Economic and Technological Development Zone, Daxing District, Beijing 100176 Applicant after:Zhengtian Technology Co.,Ltd. Address before:Room 116, floor 7, No. 1, Suzhou street, Haidian District, Beijing 100080 Applicant before:BEIJING YUNHE SPACE-TIME TECHNOLOGY Co.,Ltd. | |
| TA01 | Transfer of patent application right | ||
| RJ01 | Rejection of invention patent application after publication | Application publication date:20200204 | |
| RJ01 | Rejection of invention patent application after publication |