CN112965841A - H5-based cloud mobile phone payment method and device - Google Patents
H5-based cloud mobile phone payment method and device Download PDFInfo
- Publication number
- CN112965841A CN112965841A CN202110364491.8A CN202110364491A CN112965841A CN 112965841 A CN112965841 A CN 112965841A CN 202110364491 A CN202110364491 A CN 202110364491A CN 112965841 A CN112965841 A CN 112965841A
- Authority
- CN
- China
- Prior art keywords
- payment
- mobile phone
- page
- cloud
- cloud mobile
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- 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/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/544—Buffers; Shared memory; Pipes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- 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/451—Execution arrangements for user interfaces
- G06F9/452—Remote windowing, e.g. X-Window System, desktop virtualisation
-
- 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/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/545—Gui
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/549—Remote execution
Abstract
The application discloses a cloud mobile phone payment method and device based on H5, and relates to the field of internet, wherein the method comprises the steps of checking whether the operation environment of a current payment page is a cloud mobile phone environment if the payment page receives payment information of a user; if the current operating environment is the cloud mobile phone environment, the payment page transmits the payment link to the cloud desktop application program; the cloud desktop application program transmits the payment link to a set same-screen interaction H5 page through a WSS protocol, so that the set same-screen interaction H5 page of the user terminal jumps to a cash register address to pull up a payment system of the user terminal; according to the method and the device, message transmission between the user side equipment and the cloud mobile phone can be achieved, further the payment function can be achieved, the situation that a user downloads the cloud mobile phone APP in the mobile phone in advance in order to achieve message transmission between the user side equipment and the cloud mobile phone can be avoided, user experience is improved, and customer acquisition and operation cost can be reduced.
Description
Technical Field
The application relates to the technical field of internet and the field of cloud computing, in particular to a cloud mobile phone payment method and device based on H5.
Background
The Cloud Phone service (CPH) is a Cloud server which is virtualized based on a Cloud bare metal server, has a native android operating system, and has a virtual mobile Phone function, and as the coverage of 5G is wider and wider, scenes based on the Cloud Phone are applied more and more in the service industry, such as education, insurance, game and entertainment. In the prior art, a cloud mobile phone is mainly applied to the field of cloud computing, a scheme is mainly provided for a user to open a cloud mobile phone application program after downloading the cloud mobile phone application program in the mobile phone and to realize message transmission with the cloud mobile phone in the cloud mobile phone application program, and a payment realization scheme is mainly initiated at a cloud mobile phone application program end through the user, and when a game is purchased in the cloud mobile phone, the payment is initiated by forwarding the game to the cloud mobile phone application program end.
However, in these prior art, a user must download a cloud mobile phone application program to initiate a process, and in the current internet, the cost and difficulty of application program popularization are too high and user experience is greatly affected, so in view of this, how to implement a payment implementation scheme of a cloud mobile phone based on a user side H5 page is a problem to be solved urgently in the prior art.
Disclosure of Invention
The technical problem to be solved by the embodiment of the application is how to realize cloud mobile phone payment under a cloud mobile phone-based scene when a user side is an H5 page, so that a user can initiate payment in remote H5 page operation, and the payment of the H5-based cloud mobile phone can be really realized at the user side.
According to one aspect of the application, the application provides a cloud mobile phone payment method based on H5, which comprises the following steps: if the payment page receives the payment message of the user, checking whether the operation environment of the current payment page is the cloud mobile phone environment; if the current operating environment is the cloud mobile phone environment, the payment page transmits the payment link to the cloud desktop application program; the cloud desktop application transmits the payment link to the set same-screen interaction H5 page through the WSS protocol, so that the set same-screen interaction H5 page of the user terminal jumps to the cash register address to pull up the payment system of the user terminal.
Optionally, the checking whether the running environment of the current payment page is the cloud mobile phone environment includes: judging whether a preset JS object exists in the payment page or not;
if the JS object exists, determining that the current operation environment is a cloud mobile phone environment;
and if the JS object does not exist, determining that the current operating environment is not the cloud mobile phone environment.
Optionally, the method further includes:
the preset data structure of the JS object is CloudPhoneJSbridge; the function is defined as postData (callback); the JS object provides cloud desktop data forwarding capacity, and the H5 page of the cloud desktop calls the method to forward data from a cloud desktop end to a mobile phone end of a user;
the step of verifying whether the operation environment of the current payment page is the cloud mobile phone environment further comprises the following steps:
adding a preset JS object in the cloud mobile phone;
and the cloud desktop application program on the cloud mobile phone judges whether the JS object with the set data structure exists in the operating environment of the current payment page.
Optionally, the preset JS object includes: receiver: [ string ], data: [ character string ], callback: [ character string ];
wherein the content of the first and second substances,
receiver: [ character string ] indicates a receiving side, and the fixed value of the character string includes: "customer";
data: the [ character string ] represents the data content to be forwarded, including the payment link;
a callback: the character string represents the name of the callback function, and the parameter can be customized;
the callback function is defined as callback (resp), and the callback parameter resp is a json object, which is defined as follows:
{
"status": 200, 200 parameters indicate that data is successfully forwarded, and others are errors;
"message": "OK" represents detailed information describing an error when the status is wrong;
}。
optionally, after the payment page transmits the payment link to the cloud desktop application, the method further includes:
the cloud desktop application program transmits the payment link to the forwarding server through the WSS protocol;
the forwarding server will find the room and user to which the device is bound based on the device unique identifier and then pass the payment link to the co-screen interactive H5 page via the WSS protocol.
Optionally, after the user terminal performs a page jump to the cash register address in the same screen interaction H5, the method further includes:
the payment system of the user terminal pulls up the payment software of the user terminal to carry out payment;
payment software includes but is not limited to WeChat payments, Payment Pay, digital RMB;
the user pays by setting modes, wherein the setting modes include but are not limited to inputting a password, brushing the face, brushing the fingerprint, brushing the voiceprint and brushing the iris.
Optionally, the cloud mobile phone binding user process includes:
step 2, binding a set user to the room, distributing a specific cloud mobile phone, and determining the binding relationship between the set user and the specific cloud mobile phone according to the unique equipment identifier;
step 3, binding the room with a cloud mobile phone;
step 4, after the room is bound, the cloud desktop application program in the cloud mobile phone opens a specified H5 page;
after the cloud mobile phone is started, the WSS communication is used for communicating with the forwarding server to ensure that the forwarding server can be immediately informed after the cloud mobile phone is disconnected.
Optionally, before the cloud mobile phone is bound to the room, the method further includes: and installing the cloud desktop application program APK for the cloud desktop application program.
Optionally, the method further includes:
detecting whether the current operating environment is a cloud mobile phone environment;
and if the current operating environment is not the cloud mobile phone environment, calling a payment interface in the user terminal equipment and carrying out payment.
Optionally, before the payment page receives the payment message of the user, the method includes: payment information sent by the user on the same-screen interaction H5 page, and an H5 page opened by the user side of the same-screen interaction H5 page.
According to another aspect of the present application, the present application further provides a cloud mobile phone payment device based on H5, including: the verification module is used for verifying whether the operation environment of the current payment page is the cloud mobile phone environment or not if the payment page receives the payment message of the user; the payment page is used for transmitting the payment link to the cloud desktop application program if the current operating environment is the cloud mobile phone environment; and the processing module is used for transmitting the payment link to a set same-screen interaction H5 page by the cloud desktop application program through a WSS protocol so that the same-screen interaction H5 page of the user terminal jumps to a cash register address to pull up the payment system of the user terminal.
According to the cloud mobile phone payment method and device based on H5, message transmission between the user side equipment and the cloud mobile phone can be achieved, further the payment function can be achieved, the problem that a user downloads a cloud mobile phone APP in the mobile phone in advance in order to achieve message transmission between the user side equipment and the cloud mobile phone can be avoided, user experience is improved, and customer acquisition and operation cost can be reduced.
The technical solution of the present application is further described in detail by the accompanying drawings and examples.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description, serve to explain the principles of the application.
The present application may be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:
fig. 1 shows a flowchart of a cloud mobile payment method based on H5 according to an embodiment of the present application;
fig. 2 shows a flowchart of another H5-based cloud mobile payment method provided in an embodiment of the present application;
fig. 3 shows a flowchart of another cloud mobile payment method based on H5 according to an embodiment of the present application;
fig. 4 shows a structural block diagram of a cloud mobile phone payment device based on H5 according to an embodiment of the present application.
Detailed Description
Various exemplary embodiments of the present application will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present application unless specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the application, its application, or uses.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail, but are intended to be part of the specification where appropriate.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
Embodiments of the application are applicable to computer systems/servers that are operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the computer system/server include, but are not limited to: personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, microprocessor-based systems, set-top boxes, programmable consumer electronics, networked personal computers, minicomputer systems, mainframe computer systems, distributed cloud computing environments that include any of the above, and the like.
The computer system/server may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, etc. that perform particular tasks or implement particular abstract data types. The computer system/server may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.
Fig. 1 shows a flowchart of a cloud mobile payment method based on H5 according to an embodiment of the present application, and as shown in fig. 1, the method includes:
step S101, if the payment page receives the payment message of the user, checking whether the operation environment of the current payment page is the cloud mobile phone environment.
In one embodiment, the verifying whether the running environment of the current payment page is a cloud mobile phone environment comprises: judging whether a preset JS object exists in the payment page or not; if the JS object exists, determining that the current operation environment is a cloud mobile phone environment; and if the JS object does not exist, determining that the current operating environment is not the cloud mobile phone environment.
In one embodiment, the data structure of the JS object is preset to CloudPhoneJSBridge; the function is defined as postData (callback); the JS object provides cloud desktop data forwarding capability, and the H5 page of the cloud desktop calls the method to forward data from the cloud desktop end to the mobile phone end of the user.
In one embodiment, the step of checking whether the running environment of the current payment page is the cloud mobile phone environment further comprises the following steps: a preset JS object is added in the cloud mobile phone, and a cloud desktop application program on the cloud mobile phone judges whether the JS object exists in the running environment of the current payment page.
In one embodiment, the JS object includes:
receiver: [ string ], data: [ character string ], callback: [ character string ];
wherein, receiver: [ character string ] receiver, the fixed value includes: "customer";
data: [ string ] data content to be forwarded, including a payment link;
a callback: the name of the [ character string ] callback function, optional parameter;
the callback function is defined as callback (resp), and the callback parameter resp is a json object, which is defined as follows:
{
"status": 200, 200 parameters indicate that data is successfully forwarded, and others are errors;
"message": "OK" represents detailed information describing an error when the status is wrong;
}
step S102, if the current operation environment is the cloud mobile phone environment, the payment page transmits the payment link to the cloud desktop application program.
In one embodiment, if the current operating environment is detected to be a cloud mobile phone environment; and if the current operating environment is not the cloud mobile phone environment, calling a payment interface in the user terminal equipment and carrying out payment.
And step S103, the cloud desktop application program transmits the payment link to a set same-screen interaction H5 page through a WSS protocol, so that the user terminal same-screen interaction H5 page jumps to a cash register address to pull up the payment system of the user terminal.
In one embodiment, the H5 page and the on-screen interaction H5 page are large containers similar to web pages and can be used for storing files in basic streaming media formats such as text, pictures, audios and videos. The making of the H5 page is generally divided into code development and tool making; different from a common dragging type tool, the H5 page tool is high in flexibility, the realized function is not limited by height, the upper hand threshold is low, and the interface effect is somewhat similar to PPT.
In one embodiment, after the payment page passes the payment link to the cloud desktop application, the method further comprises: the cloud desktop application program transmits the payment link to the forwarding server through the WSS protocol; the forwarding server will find the room and user to which the device is bound based on the device unique identifier and then pass the payment link to the co-screen interactive H5 page via the WSS protocol.
In one embodiment, after the page jump of the user terminal co-screen interaction H5 to the cash register address, the method further comprises: the payment system of the user terminal pulls up the payment software of the user terminal to carry out payment; payment software includes, but is not limited to, WeChat payments, Payment Pay, digital RMB.
In one embodiment, the user pays by a set method including, but not limited to, entering a password, swiping a face, swiping a fingerprint, swiping a voiceprint, swiping an iris.
In an embodiment, the cloud mobile phone binding user process may specifically include:
and step 1, creating a room.
And 2, binding the room to a set user, distributing a specific cloud mobile phone, and determining the binding relationship between the set user and the specific cloud mobile phone according to the unique equipment identifier.
And 3, binding the room with the cloud mobile phone.
And 4, after the room is bound, the cloud desktop application program in the cloud mobile phone opens a specified H5 page.
After the cloud mobile phone is started, the WSS communication is used for communicating with the forwarding server to ensure that the forwarding server can be immediately informed after the cloud mobile phone is disconnected.
In one embodiment, before the room is bound to the cloud mobile phone, the method further comprises: and installing the cloud desktop application program APK for the cloud desktop application program.
In one embodiment, the payment page, prior to receiving the user's payment message, comprises: payment information sent by the user on the same-screen interaction H5 page, and an H5 page opened by the user side of the same-screen interaction H5 page.
The payment method provided by the embodiment of the application can be used for getting through payment in a cloud mobile phone environment, can realize various transaction scenes based on the cloud mobile phone, and compared with the mode that a user downloads the cloud mobile phone APP in the mobile phone at present, the method can realize message transmission between user side equipment and the cloud mobile phone, further realize the payment function, and can also avoid the problem that the user downloads the cloud mobile phone APP in the mobile phone in advance in order to realize the message transmission between the user side equipment and the cloud mobile phone, so that the user experience is improved, and the customer-obtaining cost and the operation cost can be reduced.
Fig. 2 shows a system diagram of another H5-based cloud mobile phone payment method provided by an embodiment of the present application; as shown in fig. 2, the system includes a service staff terminal, a cloud mobile phone, a user mobile phone, a payment system, a forwarding service, and a payment server. Wherein, the service personnel terminal mainly refers to the realization sale terminal; the cloud mobile phone can be mainly a Huazhiyun mobile phone or an Aliyun mobile phone; the same screen interaction (H5) page may refer to the client side open H5 page; the payment system may refer to a front-end system of payment; the forwarding service can be a system for websocket forwarding, and can be a cloud-based server; the cloud desktop app may be an apk for installation into a cloud handset.
Fig. 3 shows a flowchart of another cloud mobile payment method based on H5 according to an embodiment of the present application, and as shown in fig. 3, the flowchart includes:
step 301, the user operates the same-screen interaction H5 page 1, and after payment is paid, the payment information of the user is sent to a product payment page.
Step 302, after receiving a payment request of a user, checking whether the operation environment of the current page is a cloud mobile phone environment or not on a product payment page.
And 303, if the current operation environment is the cloud mobile phone environment, the product payment page transmits the payment link to the cloud desktop APP.
And step 304, the cloud desktop APP transmits the payment link to the forwarding service through the WSS protocol.
Step 305, the forwarding service finds the room and the user bound by the device according to the unique device identifier, and then transmits the payment link to the same-screen interactive H5 page through the WSS protocol.
Step 306, jump to the cashier's station address.
Step 307, the user terminal pulls up the WeChat payment or other payment methods.
Step 308, the customer enters a password payment.
In one embodiment, the payment message and the request message for WSS payment may be composed of REST API requests, and the Token of the acquiring user for calling IAM service may be used for authentication when calling other APIs.
In one embodiment, the request URI request of the payment message consists of:
{URI-scheme}：//{Endpoint}/{resource-path}？{query-string}
URI-scheme represents a protocol for transmitting requests, and all the current APIs adopt HTTPS protocols; the Endpoint specifies the server domain name or IP bearing the REST service Endpoint, and the endpoints of different services in different areas are different and can be obtained from regions and terminal nodes. For example, the Endpoint of the IAM service in the "north china-beijing one" region is "IAM. resource-path resource path, i.e., API access path. Obtaining from URI module of specific API, for example, "obtaining user Token" API resource-path is "/v 3/auth/tokens"; the query-string query parameter is an optional part, and not every API has a query parameter. Need to have one "? "in the form of" parameter name ═ parameter value ", for example," limit ═ 10 ", indicates that the query does not exceed 10 pieces of data.
For example, to obtain Token of IAM in the area of north-kyo one, we need to use Endpoint (IAM. cn-not-1. myhua weiciloud. com) in the area of north-kyo one, and find resource-path (/ v3/auth/tokens) in the URI portion of Token of user.
HTTP request method of the payment message, wherein, GET requests the server to return and appoints the resources; the PUT requests the server to update the specified resources; the POST requests a server to newly add resources or execute special operation; DELETE requests the server to DELETE a specified resource, such as a DELETE object; HEAD request server resource header; PATCH requests the server to update part of the content of the resource; when the resource does not exist, the PATCH may create a new resource.
The payment message request message header attaches request header fields such as the fields required for the specified URI and HTTP methods. Such as a request header "Content-Type" defining the Type of the message body, request authentication information, etc. The request message body is optional, and is usually sent in a structured format (such as JSON or XML) and corresponds to a Content-Type in the request message header, and delivers contents other than the request message header. If the parameters in the request message body support Chinese, then the Chinese characters must be UTF-8 encoded. The content of the request message body of each interface is different, and the request message body is not required for each interface (or the message body is empty), the message body is not required for the interfaces of the GET and DELETE operation types, and the specific content of the message body is determined according to the specific interface.
For the acquisition user Token interface, the required request parameters and parameter descriptions can be seen from the request part of the interface. username is the user name, domainname is the account name to which the user belongs, xxxxxxxxxxxxxx is the user login password, and xxxxxxxxxxxxxx is the name of project, such as "cn-normal-1", which can be obtained from the region and the terminal node.
The authentication calling interface has two authentication modes, and one of the two authentication modes can be selected for authentication. Token authentication: authenticating the generic request by Token; AK/SK authentication: the call request is encrypted by AK (Access Key ID)/SK (secret Access Key).
The Token authentication shows that the validity period of Token is 24 hours, and when one Token authentication is needed, the Token authentication can be cached first, so that frequent calling is avoided. Token represents the (temporary) meaning of a Token in a computer system, and possession of Token represents possession of a certain right. The Token authentication is to add Token to the header of the request message when calling API, so as to obtain the authority to operate API through identity authentication. The Token can be obtained by calling an obtaining user Token interface, the service API is called to require Token at project level, namely when the obtaining user Token interface is called, project is required to be selected when value of auth. scope in the body is requested, the AK/SK signature authentication mode only supports the message body size within 12MB, and requests above 12MB use Token authentication. AK/SK authentication is to sign a request by using AK/SK, and to add signature information to a message header when the request is made, so as to pass identity authentication. Ak (access Key id): the access key ID. A unique identifier associated with the private access key; the access key ID is used with the private access key to cryptographically sign the request. Sk (secret Access key): the key used in conjunction with the access key ID, cryptographically signing the request, may identify the sender, and prevent the request from being modified. When AK/SK authentication is used, the request can be signed by using AK/SK based on a signature algorithm, or the request can be signed by using a special signature SDK.
Fig. 4 shows a structural block diagram of a cloud mobile phone payment device based on H5 according to an embodiment of the present application; as shown in fig. 4, the apparatus 400 includes:
the verification module 401 is configured to verify whether the operating environment of the current payment page is a cloud mobile phone environment if the payment page receives a payment message of a user; the first processing module 402 is connected with the verification module and used for transmitting a payment link to a cloud desktop application program by the payment page if the current operation environment is a cloud mobile phone environment; and the second processing module 403 is connected with the first processing module, and is used for the cloud desktop application to transmit the payment link to the set same-screen interaction H5 page through the WSS protocol, so that the user terminal same-screen interaction H5 page jumps to the cash register address to pull up the payment system of the user terminal.
The functions of the apparatus are described in the above method partial flow, and are not described herein.
The payment device provided by the embodiment of the application can realize message transmission between the user end equipment and the cloud mobile phone, further can realize the payment function, can avoid the user to download the cloud mobile phone APP in the mobile phone in advance for realizing the message transmission between the user end equipment and the cloud mobile phone, improves user experience, and can reduce customer acquisition and operation cost.
In the present specification, the embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts in the embodiments are referred to each other. For the system embodiment, since it basically corresponds to the method embodiment, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The method and system of the present application may be implemented in a number of ways. For example, the methods and systems of the present application may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present application are not limited to the order specifically described above unless otherwise specifically indicated. Further, in some embodiments, the present application may also be embodied as a program recorded in a recording medium, the program including machine-readable instructions for implementing a method according to the present application. Thus, the present application also covers a recording medium storing a program for executing the method according to the present application.
The description of the present application has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the application in the form disclosed. Many modifications and variations will be apparent to practitioners skilled in this art. The embodiment was chosen and described in order to best explain the principles of the application and the practical application, and to enable others of ordinary skill in the art to understand the application for various embodiments with various modifications as are suited to the particular use contemplated.
Claims (10)
1. A cloud mobile phone payment method based on H5 is characterized by comprising the following steps:
if the payment page receives a payment message of a user, checking whether the operation environment of the current payment page is a cloud mobile phone environment;
if the current operating environment is the cloud mobile phone environment, the payment page transmits the payment link to the cloud desktop application program;
and the cloud desktop application program transmits the payment link to a set same-screen interaction H5 page through a WSS protocol, so that the set same-screen interaction H5 page of the user terminal jumps to a cash register address to pull up the payment system of the user terminal.
2. The method of claim 1, wherein the verifying whether the running environment of the current payment page is a cloud mobile phone environment comprises:
judging whether a preset JS object exists in the payment page or not;
if the JS object exists, determining that the current operating environment is a cloud mobile phone environment;
and if the JS object does not exist, determining that the current operating environment is not the cloud mobile phone environment.
3. The method of claim 2, further comprising:
the data structure of the preset JS object is CloudPhoneJSbridge; the function is defined as postData (callback); the JS object provides cloud desktop data forwarding capacity, and the H5 page of the cloud desktop calls the method to forward data from a cloud desktop end to a mobile phone end of a user;
the step of verifying whether the operation environment of the current payment page is a cloud mobile phone environment further comprises the following steps:
adding the preset JS object in the cloud mobile phone;
and the cloud desktop application program on the cloud mobile phone judges whether the JS object of the set data structure exists in the operating environment of the current payment page.
4. The method according to claim 3, wherein the preset JS object comprises: receiver: [ string ], data: [ character string ], callback: [ character string ];
wherein the content of the first and second substances,
receiver: [ character string ] indicates a receiving side, and the fixed value of the character string includes: "customer";
data: the [ character string ] represents the data content to be forwarded, including the payment link;
a callback: the character string represents the name of the callback function, and the parameter can be customized;
the callback function is defined as callback (resp), and the callback parameter resp is a json object, which is defined as follows:
{
"status": 200, 200 parameters indicate that data is successfully forwarded, and others are errors;
"message": "OK" represents detailed information describing an error when the status is wrong;
}。
5. the method of claim 1, wherein after the payment page passes the payment link to the cloud desktop application, further comprising:
the cloud desktop application program transmits the payment link to the forwarding server through the WSS protocol;
the forwarding server will find the room and user to which the device is bound based on the device unique identifier and then pass the payment link to the co-screen interactive H5 page via the WSS protocol.
6. The method of claim 1, wherein after the page jump of the H5 page interaction with the screen of the user terminal to the cashier's station, the method further comprises:
the payment system of the user terminal pulls up the payment software of the user terminal to carry out payment;
the payment software comprises but is not limited to WeChat payment, Payment Pay, Applepay, digital RMB;
the user pays by setting modes, wherein the setting modes include but are not limited to inputting passwords, brushing faces, brushing fingerprints, brushing voice prints and brushing irises.
7. The method according to claim 5, wherein the method further comprises a cloud mobile phone binding user process, specifically comprising:
creating a room;
binding the room with a set user, distributing a specific cloud mobile phone, and determining the binding relationship between the set user and the specific cloud mobile phone according to the unique equipment identifier;
binding the room to the cloud mobile phone;
after the room is bound, a cloud desktop application in the cloud mobile phone opens a specified H5 page;
after the cloud mobile phone is started, the WSS communication is used for communicating with the forwarding server to ensure that the forwarding server can be informed when the cloud mobile phone is disconnected.
8. The method of claim 7, wherein before binding the room to the cloud phone, further comprising: and installing the cloud desktop application program APK for the cloud desktop application program.
9. The method of claim 1, further comprising:
detecting whether the current operating environment is a cloud mobile phone environment;
if the current operating environment is not the cloud mobile phone environment, calling a payment interface in the user side equipment and carrying out payment;
and/or
Before the payment page receives the payment message of the user, the method comprises the following steps: the user sends a payment message on the same screen interaction H5 page, which is the H5 page opened by the user side of the same screen interaction H5 page.
10. A cloud mobile phone payment device based on H5, comprising:
the verification module is used for verifying whether the operation environment of the current payment page is a cloud mobile phone environment or not if the payment page receives the payment message of the user;
the first processing module is connected with the checking module and used for transmitting the payment link to the cloud desktop application program by the payment page if the current operating environment is the cloud mobile phone environment;
and the second processing module is connected with the first processing module and used for transmitting the payment link to a set same-screen interaction H5 page through a WSS (wireless sensor system) protocol by the cloud desktop application program so that the same-screen interaction H5 page of the user terminal jumps to a cash register address to pull up the payment system of the user terminal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110364491.8A CN112965841A (en) | 2021-04-05 | 2021-04-05 | H5-based cloud mobile phone payment method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110364491.8A CN112965841A (en) | 2021-04-05 | 2021-04-05 | H5-based cloud mobile phone payment method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112965841A true CN112965841A (en) | 2021-06-15 |
Family
ID=76281071
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110364491.8A Pending CN112965841A (en) | 2021-04-05 | 2021-04-05 | H5-based cloud mobile phone payment method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112965841A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113177787A (en) * | 2021-04-13 | 2021-07-27 | 北京健康之家科技有限公司 | Cloud mobile phone payment method and device, storage medium and computer equipment |
| CN115170117A (en) * | 2022-05-09 | 2022-10-11 | 中移互联网有限公司 | 5G message payment method, system, device and computer readable storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104951355A (en) * | 2015-07-03 | 2015-09-30 | 北京数字联盟网络科技有限公司 | Application program virtual operation environment recognition method and device |
| US20180081787A1 (en) * | 2016-09-16 | 2018-03-22 | Total Systems Services, Inc. | Virtual Payments Environment |
| CN109005245A (en) * | 2018-09-07 | 2018-12-14 | 广州微算互联信息技术有限公司 | The use management method and system of cloud mobile phone |
| CN109196535A (en) * | 2016-06-22 | 2019-01-11 | 印度国家支付公司 | Electronic fare payment system and its method |
| CN110430273A (en) * | 2019-08-09 | 2019-11-08 | 深圳市瑞云科技有限公司 | One kind being based on 5G real-time Transmission mobile phone cloud desktop system and method |
| CN111538985A (en) * | 2020-01-22 | 2020-08-14 | 中国银联股份有限公司 | Android application running environment detection method and device |
| CN111652604A (en) * | 2020-07-13 | 2020-09-11 | 腾讯科技（深圳）有限公司 | Order payment method, order payment device and order payment system |
| CN111861453A (en) * | 2020-07-01 | 2020-10-30 | 博泰车联网(南京)有限公司 | Method and system for generating payment page and vehicle-mounted terminal |
| CN112232794A (en) * | 2020-09-11 | 2021-01-15 | 微民保险代理有限公司 | Payment method and device, storage medium and electronic equipment |
-
2021
- 2021-04-05 CN CN202110364491.8A patent/CN112965841A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104951355A (en) * | 2015-07-03 | 2015-09-30 | 北京数字联盟网络科技有限公司 | Application program virtual operation environment recognition method and device |
| CN109196535A (en) * | 2016-06-22 | 2019-01-11 | 印度国家支付公司 | Electronic fare payment system and its method |
| US20180081787A1 (en) * | 2016-09-16 | 2018-03-22 | Total Systems Services, Inc. | Virtual Payments Environment |
| CN109005245A (en) * | 2018-09-07 | 2018-12-14 | 广州微算互联信息技术有限公司 | The use management method and system of cloud mobile phone |
| CN110430273A (en) * | 2019-08-09 | 2019-11-08 | 深圳市瑞云科技有限公司 | One kind being based on 5G real-time Transmission mobile phone cloud desktop system and method |
| CN111538985A (en) * | 2020-01-22 | 2020-08-14 | 中国银联股份有限公司 | Android application running environment detection method and device |
| CN111861453A (en) * | 2020-07-01 | 2020-10-30 | 博泰车联网(南京)有限公司 | Method and system for generating payment page and vehicle-mounted terminal |
| CN111652604A (en) * | 2020-07-13 | 2020-09-11 | 腾讯科技（深圳）有限公司 | Order payment method, order payment device and order payment system |
| CN112232794A (en) * | 2020-09-11 | 2021-01-15 | 微民保险代理有限公司 | Payment method and device, storage medium and electronic equipment |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113177787A (en) * | 2021-04-13 | 2021-07-27 | 北京健康之家科技有限公司 | Cloud mobile phone payment method and device, storage medium and computer equipment |
| CN115170117A (en) * | 2022-05-09 | 2022-10-11 | 中移互联网有限公司 | 5G message payment method, system, device and computer readable storage medium |
| CN115170117B (en) * | 2022-05-09 | 2024-03-19 | 中移互联网有限公司 | 5G message payment method, system, device and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3659295A1 (en) | Authentication token with client key | |
| EP3454504B1 (en) | Service provider certificate management | |
| US9648006B2 (en) | System and method for communicating with a client application | |
| CN105897668A (en) | Third party account authorization method, device, server and system | |
| WO2014190789A1 (en) | Method, device, client and server for interaction | |
| US11483155B2 (en) | Access control using proof-of-possession token | |
| CN112965841A (en) | H5-based cloud mobile phone payment method and device | |
| JP2020534751A (en) | Electronic Contract Proof Platforms and Methods for Electronic Identification and Credit Services (EIDAS) | |
| CN109861973A (en) | Information transferring method, device, electronic equipment and computer-readable medium | |
| US20230344821A1 (en) | Platform and method of certification of an electronic notice for electronic identification and trust services (eidas) | |
| CN112448930A (en) | Account registration method, device, server and computer readable storage medium | |
| CN110417724B (en) | Method, system, server and terminal for combined authentication of login states of application programs | |
| CN108768928A (en) | A kind of information acquisition method, terminal and server | |
| CN104506530B (en) | A kind of network data processing method and device, data transmission method for uplink and device | |
| CN103856454A (en) | Method for intercommunication between IP multimedia subsystem and internet services and service intercommunication gateway | |
| CN106709768B (en) | Method and system for asynchronously downloading invoice | |
| JP5142934B2 (en) | Authentication information processing apparatus, authentication information transmission method, and authentication method | |
| CN113132317B (en) | Identity authentication method, system and device | |
| CN110766388B (en) | Virtual card generation method and system and electronic equipment | |
| US20240089249A1 (en) | Method and system for verification of identify of a user | |
| CN101159759A (en) | User authentication method and system for packet management service | |
| CN109639435A (en) | It is a kind of based on terminal card to the authentication method and system of APP | |
| EP3547640B1 (en) | Method and system for moving customer data to trusted storage | |
| US20030140224A1 (en) | Procedure and system for transmission of data | |
| JP2010128651A (en) | Content providing system and personalizing method in content providing system |
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 |