CN111932246B - Method and device for transmitting information - Google Patents
Method and device for transmitting information Download PDFInfo
- Publication number
- CN111932246B CN111932246B CN202010783381.0A CN202010783381A CN111932246B CN 111932246 B CN111932246 B CN 111932246B CN 202010783381 A CN202010783381 A CN 202010783381A CN 111932246 B CN111932246 B CN 111932246B
- Authority
- CN
- China
- Prior art keywords
- mobile phone
- cloud mobile
- phone application
- identifier
- information
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000015654 memory Effects 0.000 claims description 19
- 230000004044 response Effects 0.000 claims description 18
- 238000012545 processing Methods 0.000 claims description 4
- 238000004590 computer program Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000012795 verification Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
-
- A—HUMAN NECESSITIES
- A63—SPORTS; GAMES; AMUSEMENTS
- A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
- A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
- A63F13/70—Game security or game management aspects
- A63F13/79—Game security or game management aspects involving player-related data, e.g. identities, accounts, preferences or play histories
- A63F13/792—Game security or game management aspects involving player-related data, e.g. identities, accounts, preferences or play histories for payment purposes, e.g. monthly subscriptions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Multimedia (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- Information Transfer Between Computers (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application discloses a method and a device for sending information, and relates to the field of cloud computing. The specific implementation scheme is as follows: receiving first cloud mobile phone application starting information sent by a cloud mobile phone client, wherein the first cloud mobile phone application starting information comprises a user identifier, a first cloud mobile phone equipment identifier and a first cloud mobile phone application identifier; receiving second cloud mobile phone application starting information sent by a cloud mobile phone server, wherein the second cloud mobile phone application starting information comprises a second cloud mobile phone equipment identifier and a second cloud mobile phone application identifier; responding to the fact that the first cloud mobile phone application starting information is matched with the second cloud mobile phone application starting information, and acquiring prestored login information which corresponds to a user identifier and is used for logging in a cloud mobile phone application corresponding to the second cloud mobile phone application identifier; and sending the login information to the cloud mobile phone server so that the cloud mobile phone server can execute login operation according to the login information. According to the embodiment, the login efficiency of the cloud mobile phone application is improved.
Description
Technical Field
The disclosure relates to the field of computer technology, in particular to the field of cloud computing.
Background
With the development of communication technology, cloud operation has become a trend. Cloud handsets are one service that is introduced based on cloud computing, ARM (Advanced RISC Machines) processor virtualization, and the like. The cloud mobile phone is a mobile phone which applies a cloud computing technology to network terminal services and realizes cloud services through a cloud server. The cloud mobile phone has the capability of rapidly, efficiently and stably running an Application (App) at the cloud, and supports 24-hour online running without interruption. At present, some cloud mobile phones can be operated on terminal equipment such as mobile phones, televisions and the like. Because the cloud mobile phone runs on the remote cloud device, functions such as local end login and payment cannot be achieved. For example, logging in applications such as games on a cloud mobile phone requires a user to scan a two-dimensional code or manually input an account number and a password. If an application such as a game running on a cloud mobile phone initiates payment, the application generally needs to scan the payment through a two-dimensional code or needs to input a mobile phone number, then a payment provider such as a payment bank, a WeChat and the like returns a short message verification code, and a user receives the verification code and then manually inputs the verification code to complete the payment. Therefore, the cloud mobile phone is very complicated, low-efficient in login, payment and the like.
Disclosure of Invention
The present disclosure provides a method, apparatus, device, and storage medium for transmitting information.
According to a first aspect of the present disclosure, there is provided a method for transmitting information, comprising: receiving first cloud mobile phone application starting information sent by a cloud mobile phone client, wherein the first cloud mobile phone application starting information comprises a user identifier, a first cloud mobile phone equipment identifier and a first cloud mobile phone application identifier; receiving second cloud mobile phone application starting information sent by a cloud mobile phone server, wherein the second cloud mobile phone application starting information comprises a second cloud mobile phone equipment identifier and a second cloud mobile phone application identifier; responding to the fact that the first cloud mobile phone application starting information is matched with the second cloud mobile phone application starting information, and acquiring prestored login information which corresponds to the user identification and is used for logging in a cloud mobile phone application corresponding to the second cloud mobile phone application identification; and sending the login information to the cloud mobile phone server so that the cloud mobile phone server executes login operation according to the login information.
According to a second aspect of the present disclosure, there is provided an apparatus for transmitting information, comprising: the cloud mobile phone comprises a first receiving unit and a second receiving unit, wherein the first receiving unit is configured to receive first cloud mobile phone application starting information sent by a cloud mobile phone client, and the first cloud mobile phone application starting information comprises a user identifier, a first cloud mobile phone equipment identifier and a first cloud mobile phone application identifier; the second receiving unit is configured to receive second cloud mobile phone application starting information sent by the cloud mobile phone server, wherein the second cloud mobile phone application starting information comprises a second cloud mobile phone equipment identifier and a second cloud mobile phone application identifier; the acquiring unit is configured to acquire prestored login information, corresponding to the user identifier, for logging in a cloud mobile phone application corresponding to the second cloud mobile phone application identifier in response to determining that the first cloud mobile phone application starting information is matched with the second cloud mobile phone application starting information; and a transmitting unit configured to transmit the login information to the cloud mobile phone server, so that the cloud mobile phone server performs a login operation according to the login information.
According to a third aspect of the present disclosure, there is provided an electronic apparatus, characterized by comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of the first aspects.
According to a fourth aspect of the present disclosure, there is provided a non-transitory computer readable storage medium storing computer instructions for causing a computer as described above to perform the method as described in any one of the first aspects.
According to a fifth aspect of the present disclosure, embodiments of the present disclosure provide a computer program product comprising a computer program which, when executed by a processor, implements a method as described in any of the implementations of the first aspect.
According to the technology, after the server determines that the first cloud mobile phone application starting information sent by the cloud mobile phone client is matched with the second cloud mobile phone application starting information sent by the cloud mobile phone server, the pre-stored login information is directly obtained from the local and sent to the cloud mobile phone server, so that the login of the cloud mobile phone application is realized, a user does not need to manually login through operating terminal equipment where the cloud mobile phone client is located, login steps are simplified, and login efficiency is improved.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.
Drawings
The drawings are for better understanding of the present solution and do not constitute a limitation of the present application. Wherein:
FIG. 1 is a flow chart of one embodiment of a method for transmitting information according to the present application;
FIG. 2 is a schematic illustration of one application scenario of a method for transmitting information according to the present application;
FIG. 3 is a flow chart of yet another embodiment of a method for transmitting information according to the present application;
FIG. 4 is a schematic structural view of one embodiment of an apparatus for transmitting information according to the present application;
fig. 5 is a block diagram of an electronic device for implementing a method for transmitting information of an embodiment of the present application.
Detailed Description
Exemplary embodiments of the present application are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present application to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It should be noted that, without conflict, the embodiments of the present disclosure and features of the embodiments may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Referring to fig. 1, a flow 100 of one embodiment of a method for transmitting information according to the present disclosure is shown. The method for transmitting information includes the steps of:
s101, receiving first cloud mobile phone application starting information sent by a cloud mobile phone client.
In this embodiment, an execution body (e.g., a server) of the method for transmitting information may receive first cloud mobile application start information transmitted by the cloud mobile client. The first cloud mobile phone application starting information may include a user identifier, a first cloud mobile phone device identifier and a first cloud mobile phone application identifier.
Here, the cloud handset client may be an application that a user downloads to a used terminal device (e.g., a smart phone, a tablet, a smart television, a laptop, a desktop computer, etc.) in various ways. The cloud handset client may be a small thin client. After a user starts the cloud mobile phone client, the cloud mobile phone client can log in the cloud mobile phone server. The cloud handset server may include a plurality of cloud handsets on which various cloud handset applications, such as cloud games, may be installed. The cloud mobile phone application can be started by the user through the cloud mobile phone client, and the cloud mobile phone server can send the cloud mobile phone equipment identifier (for example, the cloud mobile phone equipment number) of the cloud mobile phone started at this time and the cloud mobile phone application identifier (for example, the application name of the cloud mobile phone application) of the cloud mobile phone application to the cloud mobile phone client. Here, the cloud mobile phone device identifier of the cloud mobile phone may refer to an identifier of a device (for example, a board card) running the cloud mobile phone in the cloud mobile phone server. And then, the cloud mobile phone client can take the cloud mobile phone equipment identifier as a first cloud mobile phone equipment identifier, take the cloud mobile phone application identifier as a first cloud mobile phone application identifier and send first cloud mobile phone application starting information to the server. Here, the first cloud mobile phone application start information may further include a user identifier. The user identification may be an identification used by the user when starting the cloud handset client, for example, a user name. Taking the user name of Zhang Sanu, the first cloud mobile phone device identifier of "Y" and the first cloud mobile phone application identifier of "X" as examples, the cloud mobile phone client may send the first cloud mobile phone application starting information of Zhang Sanu to the execution body to start the first cloud mobile phone application X, and the first cloud mobile phone device identifier of Y.
Here, the cloud mobile phone may rely on a cloud server technology and an ARM virtualization technology, and is an operating system instance (for example, an android instance) or an application instance (for example, an android APP instance) provided by a user/client at the cloud end. As an example, the user/client may remotely control the cloud handset in real time by way of a video stream. Typically, a user may initiate (or log in) a cloud handset client installed by a terminal device in a variety of ways, for example, by fingerprint login, or by registering and entering a user name and password, or by way of a third party application authorization, etc. Taking login through a user name and a password as an example, after a user opens a cloud mobile phone client installed in a terminal device, if the cloud mobile phone client is not logged in, a login interface for inputting the user name and the password is displayed. If the user has a user name and a password, directly inputting a login; if the user is not registered, the user registers first, and after the registration is completed, the registered user name and password are used for logging in.
It should be understood that, although the terms first, second, etc. may be used in this specification to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another.
S102, receiving second cloud mobile phone application starting information sent by a cloud mobile phone server.
In this embodiment, if a certain cloud mobile phone application of a certain cloud mobile phone on the cloud mobile phone server is started, the cloud mobile phone server may send a cloud mobile phone application identifier of the cloud mobile phone application and a cloud mobile phone device identifier of the cloud mobile phone to the execution subject. And sending second cloud mobile phone application starting information to the execution body. The second cloud mobile phone application starting information may include a second cloud mobile phone device identifier and a second cloud mobile phone application identifier. Taking the second cloud mobile phone device identifier as "Y" and the second cloud mobile phone application identifier as "X" as an example, the cloud mobile phone server may send second cloud mobile phone application start information "i are second cloud mobile phone applications X" to the execution body, and the second cloud mobile phone application start information is installed on a cloud mobile phone corresponding to the second cloud mobile phone device identifier Y.
S103, in response to determining that the first cloud mobile phone application starting information and the second cloud mobile phone application starting information are matched, acquiring pre-stored login information which corresponds to the user identifier and is used for logging in the cloud mobile phone application corresponding to the second cloud mobile phone application identifier.
In this embodiment, the executing body may match the first cloud mobile phone application starting information sent by the cloud mobile phone client with the second cloud mobile phone application starting information sent by the cloud mobile phone server, and if the first cloud mobile phone application starting information is matched with the second cloud mobile phone application starting information, the executing body may obtain login information, stored in advance, of a cloud mobile phone application corresponding to a user identifier in the first cloud mobile phone application starting information and used for logging in the cloud mobile phone application corresponding to the second cloud mobile phone application identifier. As an example, the first cloud mobile phone application starting information and the second cloud mobile phone application starting information being matched may mean that a first cloud mobile phone device identifier and a first cloud mobile phone application identifier in the first cloud mobile phone application starting information are respectively the same as a second cloud mobile phone device identifier and a second cloud mobile phone application identifier in the second cloud mobile phone application starting information.
In some optional implementations of this embodiment, before obtaining the login information for logging in the cloud mobile phone application corresponding to the second cloud mobile phone application identifier, where the login information is stored in advance and corresponds to the user identifier, the method for sending information may further include the following contents not shown in fig. 1:
first, in response to determining that login information for logging in a cloud mobile phone application corresponding to a second cloud mobile phone application identifier corresponding to a user identifier is not stored locally, login information is generated.
In this implementation manner, after determining that the first cloud mobile phone device identifier and the first cloud mobile phone application identifier are respectively the same as the second cloud mobile phone device identifier and the second cloud mobile phone application identifier, the execution body may further determine whether login information for logging in the cloud mobile phone application corresponding to the second cloud mobile phone application identifier, which corresponds to the user identifier in the first cloud mobile phone application starting information, is stored locally. If not stored locally, the executing body may generate registration information. As an example, the execution subject may generate the registration information according to a preset generation rule. Here, the generation rule may be set by a technician according to actual needs. For example, the generation rule may be: user identification-cloud mobile phone application identification-preset number of random numbers.
Then, the registration information is transmitted to the cloud mobile application.
In this implementation manner, the executing body may send the generated registration information to a cloud mobile phone application corresponding to a second cloud mobile phone application identifier in the cloud mobile phone corresponding to the second cloud mobile phone device identifier in the cloud mobile phone server, so that the cloud mobile phone application executes the registration operation according to the registration information. After the cloud mobile phone application completes registration, registration completion information may be sent to the execution body.
And finally, responding to receiving registration completion information fed back by the cloud mobile phone application, and storing the registration information serving as login information, the user identification and the second cloud mobile phone application identification in a local mode.
In this implementation manner, if the execution body receives the registration completion information fed back by the cloud mobile phone application, the execution body may store the registration information as registration information in association with the user identifier and the second cloud mobile phone application identifier locally. Thus, when the user corresponding to the user identifier starts the cloud mobile phone application corresponding to the second cloud mobile phone application identifier next time, the execution subject can query the login information locally. According to the implementation mode, the execution main body can determine the login information and store the login information locally when the login information for logging in the cloud mobile phone application corresponding to the second cloud mobile phone application identifier corresponding to the user identifier is not stored locally, so that the login information is obtained.
S104, the login information is sent to the cloud mobile phone server, so that the cloud mobile phone server can execute login operation according to the login information.
In this embodiment, the execution body may send the login information acquired in S103 to the cloud mobile phone server. As an example, the execution body may also send the second cloud mobile phone device identifier and the second cloud mobile phone application identifier together while sending the login information. And the cloud mobile phone server executes login operation of the cloud mobile phone application corresponding to the second cloud mobile phone application identifier in the cloud mobile phone corresponding to the second cloud mobile phone equipment identifier according to the login information.
With continued reference to fig. 2, fig. 2 is a schematic diagram of an application scenario of the method for transmitting information according to the present embodiment. In the application scenario of fig. 2, the server 201 receives first cloud mobile phone application starting information sent by a cloud mobile phone client installed on the terminal device 202, where the first cloud mobile phone application starting information includes a user identifier "Zhang san", a first cloud mobile phone device identifier Y and a first cloud mobile phone application identifier X. Then, the server 201 receives second cloud mobile phone application starting information sent by the cloud mobile phone server 203, where the second cloud mobile phone application starting information includes a second cloud mobile phone device identifier Y and a second cloud mobile phone application identifier X. Then, in response to determining that the first cloud mobile phone application starting information and the second cloud mobile phone application starting information are matched, the server 201 obtains pre-stored login information, corresponding to the user identifier Zhang Sanu, for logging in the cloud mobile phone application corresponding to the second cloud mobile phone application identifier X. Finally, the server 201 sends the login information to the cloud mobile phone server 203, so that the cloud mobile phone server 203 performs a login operation according to the login information.
According to the method provided by the embodiment of the disclosure, after the server determines that the first cloud mobile phone application starting information sent by the cloud mobile phone client is matched with the second cloud mobile phone application starting information sent by the cloud mobile phone server, the pre-stored login information is directly obtained from the local and sent to the cloud mobile phone server, so that the login of the cloud mobile phone application is realized, a user does not need to manually login by operating the terminal equipment where the cloud mobile phone client is located, login steps are simplified, and login efficiency is improved.
With further reference to fig. 3, a flow 300 of yet another embodiment of a method for transmitting information is shown. The flow 300 of the method for transmitting information comprises the steps of:
s301, receiving first cloud mobile phone application starting information sent by a cloud mobile phone client.
In this embodiment, S301 is similar to S101 of the embodiment shown in fig. 1, and will not be described here again.
S302, receiving second cloud mobile phone application starting information sent by a cloud mobile phone server.
In this embodiment, S302 is similar to S102 in the embodiment shown in fig. 1, and will not be described here again.
S303, in response to determining that the first cloud mobile phone application starting information and the second cloud mobile phone application starting information are matched, acquiring pre-stored login information, corresponding to the user identifier, for logging in the cloud mobile phone application corresponding to the second cloud mobile phone application identifier.
In this embodiment, S303 is similar to S103 in the embodiment shown in fig. 1, and will not be described here again.
S304, the login information is sent to the cloud mobile phone server, so that the cloud mobile phone server can execute login operation according to the login information.
In this embodiment, S304 is similar to S104 in the embodiment shown in fig. 1, and will not be described here again.
And S305, storing the user identification, the second cloud mobile phone equipment identification and the second cloud mobile phone application identification in an associated mode.
In this embodiment, if it is determined that the first cloud mobile phone application starting information and the second cloud mobile phone application starting information are matched, the execution body may further store the user identifier in the first cloud mobile phone application starting information, and the second cloud mobile phone device identifier and the second cloud mobile phone application identifier in the second cloud mobile phone application starting information in association to the local. As an example, the first cloud mobile phone application starting information and the second cloud mobile phone application starting information being matched may mean that a first cloud mobile phone device identifier and a first cloud mobile phone application identifier in the first cloud mobile phone application starting information are respectively the same as a second cloud mobile phone device identifier and a second cloud mobile phone application identifier in the second cloud mobile phone application starting information. Through the implementation manner, the association storage of the user identifier, the second cloud mobile phone equipment identifier and the second cloud mobile phone application identifier can be realized, so that the binding of the user identifier, the second cloud mobile phone equipment identifier and the second cloud mobile phone application identifier is realized.
S306, in response to receiving a payment request which is sent by the cloud mobile phone application and comprises a cloud mobile phone equipment identifier and a cloud mobile phone application identifier, determining a user identifier which is stored in association with the cloud mobile phone equipment identifier and the cloud mobile phone application identifier as a target user identifier.
In this embodiment, the execution body may receive a payment request sent by a cloud mobile application of a cloud mobile on a cloud mobile server. The payment request may include a cloud mobile device identifier and a cloud mobile application identifier. If a payment request sent by the cloud mobile phone application is received, the execution body can determine a user identifier stored in association with the cloud mobile phone equipment identifier and the cloud mobile phone application identifier in the payment request as a target user identifier.
During the process of running certain cloud mobile phone applications, a user can click to purchase a certain commodity in the cloud mobile phone applications. Taking cloud mobile phone application as an example of a cloud game, a user can click to purchase game equipment in the cloud game. At this time, the cloud mobile phone application may send a payment request to the execution body, where the payment request may include a cloud mobile phone application identifier of the cloud mobile phone application, and may further include a cloud mobile phone device identifier of a cloud mobile phone where the cloud mobile phone application is located. In addition, the payment request may also include payment-related information such as the amount to be paid.
S307, the payment request is forwarded to the target cloud mobile phone client corresponding to the target user identifier, so that the target cloud mobile phone client displays a payment interface to the user by calling the local payment support interface.
In this embodiment, the execution body may forward the payment request to the target cloud mobile phone client corresponding to the target user identifier, so that the target cloud mobile phone client may display the payment interface to the user by calling the local payment interface. At this time, similar to a general payment procedure, the user can pay by using fingerprint, face recognition, or the like. Here, the execution subject may store a correspondence between the user identifier and the cloud mobile phone client inside. The execution body can take the cloud mobile phone client corresponding to the target user identifier as a target cloud mobile phone client.
In some optional implementations of this embodiment, the method for sending information may further include the following steps: and in response to receiving the payment result information sent by the target cloud mobile phone client, sending the payment result information to a cloud mobile phone application corresponding to the cloud mobile phone equipment identifier and the cloud mobile phone application identifier in the payment request, so that the cloud mobile phone application executes preset operation according to the payment result information.
In this implementation manner, the execution body may receive payment result information sent by the target cloud mobile phone client. The payment result information may include, among other things, payment success and payment failure. After receiving the payment result information sent by the target cloud mobile phone client, the execution body can send the payment result information to the cloud mobile phone application corresponding to the cloud mobile phone equipment identifier and the cloud mobile phone application identifier in the payment request, so that the cloud mobile phone application can execute preset operation according to the payment result information. Here, the preset operation may be set according to actual needs. The cloud mobile phone application can pre-store the corresponding relation between the payment result information and the preset operation. In this way, the cloud mobile phone application can execute preset operation according to the payment result information. Taking the cloud mobile phone application as a cloud game, taking a payment request for purchasing game equipment as an example, and when the payment result information is that the payment is successful, the cloud mobile phone application can execute the game equipment issuing operation; when the payment result information is a payment failure, the cloud mobile application may not perform the game equipment issuing operation. According to the implementation mode, the execution body can forward the payment result information sent by the target cloud mobile phone client to the cloud mobile phone application corresponding to the cloud mobile phone equipment identifier and the cloud mobile phone application identifier in the payment request, so that the cloud mobile phone application can execute preset operation according to the payment result information.
In some optional implementations, the method for sending information may further include the following steps: and responding to the received payment result information sent by the target cloud mobile phone client, and generating transaction information according to the payment result information.
In this implementation manner, if the payment result information sent by the target cloud mobile phone client is received, the execution body may generate transaction information according to the payment result information. Here, the transaction information may include various information related to payment, such as a payment amount, a payment time, payment result information, and the like. As an example, transaction information may be used for settlement of funds. For example, after successful payment, funds enter the bank account of the cloud handset server operator, rather than the bank account of the cloud handset application developer. Every preset period, such as one week or one month, the cloud mobile phone server operator and the cloud mobile phone application developer can settle accounts according to the transaction information and transfer accounts to the cloud mobile phone application developer according to preset proportion. By the implementation mode, the execution body can generate transaction information according to the payment result information.
As can be seen from fig. 3, compared to the corresponding embodiment of fig. 1, the flow 300 of the method for sending information in this embodiment highlights the step of forwarding the payment request to the target cloud handset client. Therefore, the scheme described in the embodiment can enable the target cloud mobile phone client to display the payment interface to the user through calling the local payment interface so as to facilitate the payment of the user, so that the remote cloud mobile phone payment is performed in a mode of not needing to scan a two-dimensional code or inputting a mobile phone number, a verification code and the like, and the payment efficiency is improved.
With further reference to fig. 4, as an implementation of the method shown in the foregoing figures, the present disclosure provides an embodiment of an apparatus for transmitting information, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 1, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 4, the apparatus 400 for transmitting information of the present embodiment includes: a first receiving unit 401, a second receiving unit 402, an acquiring unit 403, and a transmitting unit 404. The first receiving unit 401 is configured to receive first cloud mobile phone application starting information sent by a cloud mobile phone client, where the first cloud mobile phone application starting information includes a user identifier, a first cloud mobile phone device identifier and a first cloud mobile phone application identifier; the second receiving unit 402 is configured to receive second cloud mobile phone application starting information sent by the cloud mobile phone server, where the second cloud mobile phone application starting information includes a second cloud mobile phone device identifier and a second cloud mobile phone application identifier; the obtaining unit 403 is configured to obtain, in response to determining that the first cloud mobile phone application starting information and the second cloud mobile phone application starting information match, pre-stored login information for logging in a cloud mobile phone application corresponding to the second cloud mobile phone application identifier, where the login information corresponds to the user identifier; the transmitting unit 404 is configured to transmit the login information to the cloud mobile server, so that the cloud mobile server performs a login operation according to the login information.
In this embodiment, the specific processes and the technical effects of the first receiving unit 401, the second receiving unit 402, the obtaining unit 403 and the sending unit 404 of the apparatus 400 for sending information may refer to the descriptions related to S101, S102, S103 and S104 in the corresponding embodiment of fig. 1, and are not repeated here.
In some optional implementations of this embodiment, the apparatus 400 further includes: and a storage unit (not shown in the figure) configured to store the user identifier, the second cloud mobile phone device identifier and the second cloud mobile phone application identifier in an associated manner.
In some optional implementations of this embodiment, the apparatus 400 further includes: a determining unit (not shown in the figure) configured to determine, as a target user identifier, a user identifier stored in association with the cloud mobile phone device identifier and the cloud mobile phone application identifier in response to receiving a payment request including the cloud mobile phone device identifier and the cloud mobile phone application identifier sent by the cloud mobile phone application; and the forwarding unit (not shown in the figure) is configured to forward the payment request to the target cloud mobile phone client corresponding to the target user identifier so that the target cloud mobile phone client can display a payment interface to a user by calling a local payment interface.
In some optional implementations of this embodiment, the apparatus 400 further includes: an information sending unit (not shown in the figure) is configured to send the payment result information to a cloud mobile phone application corresponding to the cloud mobile phone equipment identifier and the cloud mobile phone application identifier in the payment request in response to receiving the payment result information sent by the target cloud mobile phone client, so that the cloud mobile phone application performs a preset operation according to the payment result information.
In some optional implementations of this embodiment, the apparatus 400 further includes: and a generating unit (not shown in the figure) configured to generate transaction information according to the payment result information in response to receiving the payment result information sent by the target cloud mobile phone client.
In some optional implementations of this embodiment, the apparatus 400 further includes: a registration information generating unit (not shown in the figure) configured to generate registration information in response to determining that the registration information for registering the cloud mobile phone application corresponding to the second cloud mobile phone application identifier corresponding to the user identifier is not stored locally; a registration information transmitting unit (not shown) configured to transmit the registration information to the cloud mobile application; and an association storage unit (not shown in the figure) configured to store the registration information as registration information in association with the user identifier and the second cloud mobile phone application identifier locally in response to receiving registration completion information fed back by the cloud mobile phone application.
According to embodiments of the present application, there is also provided an electronic device, a readable storage medium and a computer program product.
As shown in fig. 5, is a block diagram of an electronic device for a method of transmitting information according to an embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the application described and/or claimed herein.
As shown in fig. 5, the electronic device includes: one or more processors 501, memory 502, and interfaces for connecting components, including high-speed interfaces and low-speed interfaces. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions executing within the electronic device, including instructions stored in or on memory to display graphical information of the GUI on an external input/output device, such as a display device coupled to the interface. In other embodiments, multiple processors and/or multiple buses may be used, if desired, along with multiple memories and multiple memories. Also, multiple electronic devices may be connected, each providing a portion of the necessary operations (e.g., as a server array, a set of blade servers, or a multiprocessor system). One processor 501 is illustrated in fig. 5.
The memory 502 is a non-transitory computer readable storage medium, and may be used to store a non-transitory software program, a non-transitory computer executable program, and modules, such as program instructions/modules (e.g., the first receiving unit 401, the second receiving unit 402, the acquiring unit 403, and the transmitting unit 404 shown in fig. 4) corresponding to the method for transmitting information in the embodiments of the present application. The processor 501 executes various functional applications of the server and data processing, i.e., implements the method for transmitting information in the above-described method embodiments, by running non-transitory software programs, instructions, and modules stored in the memory 502.
The electronic device for the method of transmitting information may further include: an input device 503 and an output device 504. The processor 501, memory 502, input devices 503 and output devices 504 may be connected by a bus or otherwise, for example in fig. 5.
The input device 503 may receive input numeric or character information and generate key signal inputs related to user settings and function controls of the electronic device used to transmit the information, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointer stick, one or more mouse buttons, a track ball, a joystick, and the like. The output devices 504 may include a display device, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibration motors), among others. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device may be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASIC (application specific integrated circuit), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
These computing programs (also referred to as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
According to the technical scheme of the embodiment of the application, after the server determines that the first cloud mobile phone application starting information sent by the cloud mobile phone client is matched with the second cloud mobile phone application starting information sent by the cloud mobile phone server, the pre-stored login information is directly obtained from the local and sent to the cloud mobile phone server, so that the login of the cloud mobile phone application is realized, a user does not need to manually login by operating terminal equipment where the cloud mobile phone client is located, login steps are simplified, and login efficiency is improved.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present application may be performed in parallel, sequentially, or in a different order, provided that the desired results of the technical solutions disclosed in the present application can be achieved, and are not limited herein.
The above embodiments do not limit the scope of the application. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application are intended to be included within the scope of the present application.
Claims (8)
1. A method for transmitting information, comprising:
receiving first cloud mobile phone application starting information sent by a cloud mobile phone client, wherein the first cloud mobile phone application starting information comprises a user identifier, a first cloud mobile phone equipment identifier and a first cloud mobile phone application identifier;
receiving second cloud mobile phone application starting information sent by a cloud mobile phone server, wherein the second cloud mobile phone application starting information comprises a second cloud mobile phone equipment identifier and a second cloud mobile phone application identifier;
responding to the fact that the first cloud mobile phone application starting information is matched with the second cloud mobile phone application starting information, and acquiring prestored login information which corresponds to the user identifier and is used for logging in a cloud mobile phone application corresponding to the second cloud mobile phone application identifier;
the login information is sent to the cloud mobile phone server so that the cloud mobile phone server can execute login operation according to the login information;
storing the user identification, the second cloud mobile phone equipment identification and the second cloud mobile phone application identification in an associated mode;
in response to receiving a payment request which is sent by a cloud mobile phone application and comprises a cloud mobile phone equipment identifier and a cloud mobile phone application identifier, determining a user identifier which is stored in association with the cloud mobile phone equipment identifier and the cloud mobile phone application identifier as a target user identifier;
forwarding the payment request to a target cloud mobile phone client corresponding to the target user identifier so that the target cloud mobile phone client displays a payment interface to a user by calling a local payment interface;
before the pre-stored login information, corresponding to the user identifier, for logging in the cloud mobile phone application corresponding to the second cloud mobile phone application identifier is obtained, the method further includes: generating registration information in response to determining that the login information of the cloud mobile phone application corresponding to the user identifier and used for logging in the second cloud mobile phone application identifier is not stored locally; transmitting the registration information to the cloud mobile phone application; and in response to receiving registration completion information fed back by the cloud mobile phone application, the registration information serving as registration information is stored locally in association with the user identifier and the second cloud mobile phone application identifier.
2. The method of claim 1, wherein the method further comprises:
and responding to the received payment result information sent by the target cloud mobile phone client, and sending the payment result information to a cloud mobile phone application corresponding to a cloud mobile phone equipment identifier and a cloud mobile phone application identifier in the payment request, so that the cloud mobile phone application can execute preset operation according to the payment result information.
3. The method of claim 2, wherein the method further comprises:
and responding to the received payment result information sent by the target cloud mobile phone client, and generating transaction information according to the payment result information.
4. An apparatus for transmitting information, comprising:
the cloud mobile phone comprises a first receiving unit and a second receiving unit, wherein the first receiving unit is configured to receive first cloud mobile phone application starting information sent by a cloud mobile phone client, and the first cloud mobile phone application starting information comprises a user identifier, a first cloud mobile phone equipment identifier and a first cloud mobile phone application identifier;
the cloud mobile phone server is configured to send first cloud mobile phone application starting information to the first receiving unit, wherein the first cloud mobile phone application starting information comprises a first cloud mobile phone equipment identifier and a first cloud mobile phone application identifier;
the acquisition unit is configured to respond to the fact that the first cloud mobile phone application starting information is matched with the second cloud mobile phone application starting information, and acquire pre-stored login information, corresponding to the user identifier, for logging in a cloud mobile phone application corresponding to the second cloud mobile phone application identifier;
a transmitting unit configured to transmit the login information to the cloud mobile phone server, so that the cloud mobile phone server performs a login operation according to the login information;
the storage unit is configured to store the user identifier, the second cloud mobile phone equipment identifier and the second cloud mobile phone application identifier in an associated mode;
the cloud mobile phone application comprises a determining unit, a processing unit and a processing unit, wherein the determining unit is configured to determine a user identifier stored in association with a cloud mobile phone equipment identifier and a cloud mobile phone application identifier as a target user identifier in response to receiving a payment request which is sent by a cloud mobile phone application and comprises the cloud mobile phone equipment identifier and the cloud mobile phone application identifier;
the forwarding unit is configured to forward the payment request to a target cloud mobile phone client corresponding to the target user identifier so that the target cloud mobile phone client can display a payment interface to a user by calling a local payment interface;
a registration information generating unit configured to generate registration information in response to determining that the login information of the cloud mobile phone application corresponding to the second cloud mobile phone application identifier and used for logging in corresponding to the user identifier is not stored locally;
a registration information transmitting unit configured to transmit the registration information to the cloud mobile phone application;
and the association storage unit is configured to respond to receiving registration completion information fed back by the cloud mobile phone application, and store the registration information serving as registration information to the local in association with the user identification and the second cloud mobile phone application identification.
5. The apparatus of claim 4, wherein the apparatus further comprises:
the information sending unit is configured to respond to receiving the payment result information sent by the target cloud mobile phone client, and send the payment result information to a cloud mobile phone application corresponding to a cloud mobile phone equipment identifier and a cloud mobile phone application identifier in the payment request, so that the cloud mobile phone application can execute preset operation according to the payment result information.
6. The apparatus of claim 5, wherein the apparatus further comprises:
and the generation unit is configured to respond to receiving the payment result information sent by the target cloud mobile phone client and generate transaction information according to the payment result information.
7. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-3.
8. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010783381.0A CN111932246B (en) | 2020-08-06 | 2020-08-06 | Method and device for transmitting information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010783381.0A CN111932246B (en) | 2020-08-06 | 2020-08-06 | Method and device for transmitting information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111932246A CN111932246A (en) | 2020-11-13 |
| CN111932246B true CN111932246B (en) | 2023-06-23 |
Family
ID=73307957
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010783381.0A Active CN111932246B (en) | 2020-08-06 | 2020-08-06 | Method and device for transmitting information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111932246B (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112968871B (en) * | 2021-01-29 | 2022-08-02 | 北京字节跳动网络技术有限公司 | Login method and device of application program, readable medium and electronic equipment |
| CN113242275B (en) * | 2021-04-12 | 2023-05-26 | 西安神鸟软件科技有限公司 | Cloud mobile phone control method and equipment |
| CN113691628B (en) * | 2021-08-25 | 2023-08-01 | 北京百度网讯科技有限公司 | Task switching method, device, system, electronic equipment and computer medium |
| CN113709151A (en) * | 2021-08-26 | 2021-11-26 | 北京百度网讯科技有限公司 | Method, apparatus, device, medium and product for logging in cloud application |
| CN113747423B (en) * | 2021-08-26 | 2024-03-19 | 北京百度网讯科技有限公司 | Cloud mobile phone state synchronization method, device, equipment, storage medium and program product |
| CN113722378B (en) * | 2021-08-31 | 2024-01-05 | 北京百度网讯科技有限公司 | Method, device, electronic equipment and medium for collecting information |
| CN113730919B (en) * | 2021-09-10 | 2024-01-09 | 北京百度网讯科技有限公司 | Cloud application pre-starting method, device, equipment, storage medium and program product |
| CN114710355B (en) * | 2022-04-11 | 2024-05-17 | 西安万像电子科技有限公司 | Login management method and system |
| CN115134348B (en) * | 2022-05-25 | 2024-05-03 | 阿里巴巴（中国）有限公司 | Sharing method of cloud application instance, system, equipment and storage medium thereof |
| CN115484346B (en) * | 2022-09-07 | 2023-08-01 | 中移互联网有限公司 | Cloud mobile phone management method and system and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103001975A (en) * | 2012-12-26 | 2013-03-27 | 百度在线网络技术（北京）有限公司 | Method, system and device used for controlling login and based on two-dimensional code |
| CN103152402A (en) * | 2013-02-07 | 2013-06-12 | 百度在线网络技术（北京）有限公司 | Method and system for logging in through mobile terminal and cloud server |
| WO2019242007A1 (en) * | 2018-06-22 | 2019-12-26 | 深圳前海达闼云端智能科技有限公司 | Device configuration method and apparatus, client terminal device, and cloud server |
| CN111221451A (en) * | 2020-01-06 | 2020-06-02 | 北京云派网络科技有限公司 | Cloud mobile phone shortcut creation method and system |
| CN111314452A (en) * | 2020-02-11 | 2020-06-19 | 安超云软件有限公司 | Shell access method, device, equipment and storage medium of cloud mobile phone |
-
2020
- 2020-08-06 CN CN202010783381.0A patent/CN111932246B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103001975A (en) * | 2012-12-26 | 2013-03-27 | 百度在线网络技术（北京）有限公司 | Method, system and device used for controlling login and based on two-dimensional code |
| CN103152402A (en) * | 2013-02-07 | 2013-06-12 | 百度在线网络技术（北京）有限公司 | Method and system for logging in through mobile terminal and cloud server |
| WO2019242007A1 (en) * | 2018-06-22 | 2019-12-26 | 深圳前海达闼云端智能科技有限公司 | Device configuration method and apparatus, client terminal device, and cloud server |
| CN111221451A (en) * | 2020-01-06 | 2020-06-02 | 北京云派网络科技有限公司 | Cloud mobile phone shortcut creation method and system |
| CN111314452A (en) * | 2020-02-11 | 2020-06-19 | 安超云软件有限公司 | Shell access method, device, equipment and storage medium of cloud mobile phone |
Non-Patent Citations (2)
| Title |
|---|
| New security login system using tap and gesture on smartphone touchscreen;Ki Hwan Kim等;《IEEE Xplore》;全文 * |
| 基于云服务器的手机即时通信软件设计;陈理;余涛;陈莹莹;毕春艳;;数码世界(06);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111932246A (en) | 2020-11-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111932246B (en) | Method and device for transmitting information | |
| US20210073761A1 (en) | Method, apparatus, and system for operating an electronic account in connection with an electronic transaction | |
| EP3079326B1 (en) | Network payment method, apparatus and system | |
| CN111080275B (en) | Cross-region resource transfer method, device, equipment and storage medium | |
| CN108064373B (en) | Resource transfer method and device | |
| CN112333239B (en) | Business audit notification method, gateway, electronic equipment and readable medium | |
| CN111666546B (en) | Application login method and device | |
| US20240029047A1 (en) | Sdk for dynamic workflow rendering on mobile devices | |
| US10147131B2 (en) | Merchant hosted checkout at a merchant server | |
| US20120173419A1 (en) | Visual transactions | |
| CN112069490B (en) | Method and device for providing applet capability, electronic equipment and storage medium | |
| WO2015175619A1 (en) | Method, apparatus, and system for operating an electronic account in connection with an electronic transaction | |
| US20230316245A1 (en) | Enabling user to user interactions in multi-user video conference applications | |
| US10645175B2 (en) | Proxy device for routing electronic messages | |
| CN112085491B (en) | Charging system access method, cloud platform, electronic equipment and computer readable medium | |
| US10438183B2 (en) | Merchant hosted checkout at a billing server | |
| CN111782445B (en) | Configuration method and device of equipment debugging environment | |
| CN114723367A (en) | Distribution method, system and device | |
| CN112967050A (en) | Payment method and device | |
| CN111177558A (en) | Channel service construction method and device | |
| CN112150135A (en) | Payment method and device | |
| CN110942309A (en) | Payment method and device, order processing method and device and payment server | |
| CN111210311B (en) | Order generation method and self-lifting cabinet | |
| US10943430B2 (en) | Registering a player account using third party user information, and related systems, devices, and methods | |
| CN116248781A (en) | Message processing method, device, equipment and storage medium based on transaction information |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |