CN105741103A - Method for providing request information and user terminal - Google Patents

Method for providing request information and user terminal Download PDF

Info

Publication number
CN105741103A
CN105741103A CN201410753538.XA CN201410753538A CN105741103A CN 105741103 A CN105741103 A CN 105741103A CN 201410753538 A CN201410753538 A CN 201410753538A CN 105741103 A CN105741103 A CN 105741103A
Authority
CN
China
Prior art keywords
request
information
user terminal
establishing
authentication 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.)
Pending
Application number
CN201410753538.XA
Other languages
Chinese (zh)
Inventor
马庆峰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to CN201410753538.XA priority Critical patent/CN105741103A/en
Priority to PCT/CN2015/096246 priority patent/WO2016091115A1/en
Publication of CN105741103A publication Critical patent/CN105741103A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/42Confirmation, e.g. check or permission by the legal debtor of payment
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/326Payment applications installed on the mobile devices

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The application provides a method for providing request information and a user terminal. The method comprises: a first user terminal obtains an instruction for establishing request information; the first user terminal obtains an instruction for establishing request authentication information; the first user terminal establishes request information attached with the request authentication information; and the first user terminal sends the request information attached with the request authentication information to a second user terminal, wherein the request authentication information is provided for the second user terminal to confirm correctness of the request information. According to the embodiment of the application, the request authentication information is not limited; and when the request authentication information with various modes is provided for a requested side, reliability of the request authentication information can be guaranteed, so that the requested side can understand the request content visually.

Description

Method for providing request information and user terminal
Technical Field
The present application relates to the field of mobile internet, and in particular, to a method for providing request information and a user terminal.
Background
With the rapid development of mobile internet technology, mobile communication is changing the lifestyle of people. For example, in the field of financial payment, mobile payment has been widely used. The mobile payment can enable a user to pay accounts for consumed goods or services through mobile terminal equipment (such as a mobile phone, a PDA and the like), and a convenient and quick payment environment is provided for the user.
In mobile payment, a consumption mode of 'AA payment' is popular at present. The consumption mode of "AA payment" can be understood as: a group of users consume a certain commodity or service together, one user can pay the commodity or service in full amount for payment convenience, and then the user can initiate a payment collection request to other users, so that the aim that each user pays the commodity or service is fulfilled.
"AA Payment" is actually understood to be a consumption model that allows one user to make advance payments and then allow other users to make repayment. In such a consumption mode, a user making a pre-payment may be referred to as a payee, and a user making a payment may be referred to as a payer. The payee, when initiating a collect request to the payer, typically notes only the amount of the collection or includes simple text remark information.
From the above "AA payment" example, it can be seen that in the prior art, the requester often can only make remarks or explanations in the content of the request with simple words when initiating the request.
In the course of carrying out the present application, the inventors have found that the prior art has at least the following disadvantages:
in the prior art, when a request is initiated, a true and credible certificate cannot be provided to a requested party to confirm the request content.
Disclosure of Invention
The embodiment of the application aims to provide a method for providing request information and a user terminal, which can provide a true and credible certificate to confirm request contents for a requested party.
The method for providing the request information and the user terminal are realized as follows:
a method of providing request information, comprising:
a first user terminal acquires an instruction for establishing request information;
a first user terminal acquires an instruction for establishing request authentication information;
the first user terminal establishes request information with request authentication information;
the first user terminal sends the request information with the request authentication information to the second user terminal;
the request authentication information is used for providing the second user terminal with confirmation of correctness of the request information.
A user terminal for providing request information, comprising: the system comprises a first instruction acquisition unit, a second instruction acquisition unit, a request information establishment unit, a request authentication information establishment unit, an addition unit and a sending unit, wherein:
the first instruction acquisition unit is used for acquiring an instruction for establishing request information;
the second instruction acquisition unit is used for acquiring an instruction for establishing the request authentication information;
the request information establishing unit is used for establishing request information;
the request authentication information establishing unit is used for establishing request authentication information;
the adding unit is used for adding the request authentication information into the request information;
the sending unit is used for sending request information with request authentication information.
As can be seen from the foregoing embodiments of the present application, the embodiments of the present application do not limit the request authentication information. By providing more forms of request authentication information to the requested party, the reliability of the request authentication information can be ensured, and the requested party can know the request content more intuitively.
Drawings
Fig. 1 is a flowchart of a method for providing request information according to an embodiment of the present application;
FIG. 2 is a diagram of a task window for establishing receipt information, such as a smart phone;
fig. 3 is a functional block diagram of a user terminal for providing request information according to an embodiment of the present application;
fig. 4 is a functional block diagram of a first instruction obtaining unit in a user terminal for providing request information according to an embodiment of the present application;
fig. 5 is a functional block diagram of a second instruction obtaining unit in a user terminal for providing request information according to an embodiment of the present application;
fig. 6 is a functional block diagram of a request information creating unit in a user terminal for providing request information according to an embodiment of the present application;
fig. 7 is a functional block diagram of a request authentication information creating unit in a user terminal for providing request information according to an embodiment of the present application;
fig. 8 is a functional block diagram of a user terminal for providing request information according to an embodiment of the present application.
Detailed Description
The embodiment of the application provides a method for providing request information and a user terminal.
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
For convenience of understanding, the following embodiments of the present application all use "AA payment" in mobile payment technology as an example to describe the technical solution of the present application. The request information in the embodiment of the application may be collection information, correspondingly, the request authentication information may be collection authentication information, the requesting party may be a collection party, the requested party may be a paying party, and the request content may be collection information.
Fig. 1 is a flowchart of a method for providing request information according to an embodiment of the present application. As shown in fig. 1, the method includes:
s1: the first user terminal obtains an instruction of establishing request information.
The first user terminal can acquire an instruction for establishing the payment information through a function key or a voice prompt. When the function key for establishing the collection information is pressed down, the first user terminal can open a task window for establishing the collection information to establish the collection information. When the voice prompt key is pressed, the first user terminal can receive external voice prompts through a microphone and other devices. The first user terminal may recognize a voice prompt to "establish payment information". After the first user terminal receives the voice prompt of 'establishing the collection information', a task window for establishing the collection information can be opened to establish the collection information.
S2: the first user terminal obtains an instruction for establishing the authentication request information.
The first user terminal may be a terminal of a payee, and after the commodity or the service is paid in advance, the first user terminal may obtain a consumption certificate of the commodity or the service, where the consumption certificate may be a specific consumption bill detail document, a consumption detail picture, an electronic consumption invoice, or a link, and the specific consumption detail may be queried through the link. The form of the consumption certificate is not limited in the embodiment of the application. The consumption certificate can be the payment authentication information used for providing payment confirmation for the payer. The first user terminal can be classified and stored according to the form of the payment receiving authentication information. For example: the consumption bill detail document may be stored in a document class store; the consumption detail picture and the electronic consumption invoice can be stored in a picture memory; the links may be stored in a link class store.
The first user terminal can obtain an instruction for establishing the collection authentication information through the function key. The function key for establishing the collection authentication information can comprise: at least one of a picture function key, a document function key, a picture taking function key and a link function key. The first user terminal can access the corresponding memory port by calling the picture function key, the document function key or the link function key, and call the picture, the document or the link in the memory according to the instruction. The first user terminal can also directly call a camera application program to take a picture as collection authentication information through a picture taking function key.
In addition, the first user terminal can also obtain an instruction for establishing the collection authentication information through voice prompt. When the voice prompt key is pressed, the first user terminal can receive external voice prompts through a microphone and other devices. The first user terminal may recognize a voice prompt including at least one of "call picture", "call document", "take picture", and "call link". After the first user terminal recognizes the voice prompt of calling the picture, calling the document or calling the link, the first user terminal can correspondingly access the picture memory, the document memory or the link memory and call the picture, the document or the link in the memory according to the instruction. When the first user terminal recognizes the voice prompt of 'picture taking', the first user terminal can directly call a camera application program to take a picture as the collection authentication information.
S3: the first user terminal establishes request information with request authentication information attached.
The first user terminal establishes the request information with the request authentication information through the following three steps:
s301: and the first user terminal opens a task window for establishing the request information according to the acquired instruction for establishing the request information, wherein the task window comprises a function key or/and a voice prompt key for establishing the request authentication information.
In step S1, after the first user terminal obtains the instruction to establish the collection information through the function key or the voice prompt, the first user terminal may open a task window for establishing the collection information, and establish the collection information. Fig. 2 is a schematic diagram of a task window for establishing collection information, for example, using a smart phone. As shown in fig. 2, the task window for establishing the collection information may include a series of information frames, such as a payee account information frame, a payer account information frame, and a payment amount frame, for entering corresponding payee account information, payer account information, and payment amount. In addition, the task window for establishing the collection information can also comprise a function key or/and a voice prompt key for establishing collection authentication information. The function key for establishing the payment receiving authentication information may include: a picture function key, a document function key, a picture taking function key and a link function key.
S302: and the first user terminal adds request content, requesting party account information and requested party account information in the task window of the request information.
After the first user terminal opens the task window for establishing the collection information, the first user terminal can add the collection party account information, the payment party account information and the payment amount. The adding method comprises the following steps: the first user terminal can directly input the account information of the payee, the account information of the payer and the payment amount according to the instruction. In addition, after the first user terminal inputs the account information of the payee and the payment amount according to the instruction, the first user terminal can call the stored user address book and select the account information of the payer according to the instruction.
S303: the first user terminal establishes the request authentication information according to the acquired instruction for establishing the request authentication information, and adds the request authentication information into the request information.
The first user terminal can acquire an instruction for establishing the collection authentication information through a function key or/and a voice prompt key for establishing the collection authentication information contained in the task window, and establishes the collection authentication information. By calling the picture function key, the document function key or the link function key, the first user terminal can access the corresponding memory port and call the picture, the document or the link in the memory according to the instruction. The first user terminal can also directly call a camera application program to take a picture as collection authentication information through a picture taking function key. In addition, when the voice guidance key is pressed, the first user terminal may recognize voice guidance including "call picture", "call document", "take picture", and "call link". After the first user terminal recognizes the voice prompt of calling the picture, calling the document or calling the link, the first user terminal can correspondingly access the picture memory, the document memory or the link memory and call the picture, the document or the link in the memory according to the instruction. When the first user terminal recognizes the voice prompt of 'picture taking', the first user terminal can directly call a camera application program to take a picture as the collection authentication information. After the first user terminal establishes the collection authentication information, the collection authentication information can be directly added into a task window of the collection information.
In another embodiment of the present application, step S3 can also be implemented by the following four steps:
s311: and the first user terminal opens a task window for establishing the request information according to the acquired instruction for establishing the request information, wherein the task window comprises a function key or/and a voice prompt key for establishing the request authentication information.
In step S1, after the first user terminal obtains the instruction to establish the collection information through the function key or the voice prompt, the first user terminal may open a task window for establishing the collection information, and establish the collection information. The task window for establishing the collection information can comprise a series of information frames, namely a collector account information frame, a payer account information frame and a payment amount frame, and is used for inputting corresponding collector account information, payer account information and payment amount. In addition, the task window for establishing the collection information can also comprise a function key or/and a voice prompt key for establishing collection authentication information. Wherein, the function key for establishing the collection authentication information comprises: the function key of the picture is called, the function key of the document is called, and the function key of the picture is shot.
S312: the first user terminal establishes the request authentication information according to the acquired instruction for establishing the request authentication information, and adds the request authentication information into the request information.
The first user terminal can acquire an instruction for establishing the collection authentication information through a function key or/and a voice prompt key for establishing the collection authentication information contained in the task window, and establishes the collection authentication information. By calling the picture function key, the document function key or the link function key, the first user terminal can access the corresponding memory port and call the picture, the document or the link in the memory according to the instruction. The first user terminal can also directly call a camera application program to take a picture as collection authentication information through a picture taking function key. In addition, when the voice guidance key is pressed, the first user terminal may recognize voice guidance including "call picture", "call document", "take picture", and "call link". After the first user terminal recognizes the voice prompt of calling the picture, calling the document or calling the link, the first user terminal can correspondingly access the picture memory, the document memory or the link memory and call the picture, the document or the link in the memory according to the instruction. When the first user terminal recognizes the voice prompt of 'picture taking', the first user terminal can directly call a camera application program to take a picture as the collection authentication information. After the first user terminal establishes the collection authentication information, the collection authentication information can be directly added into a task window of the collection information.
S313: the first user terminal scans the request authentication information to obtain requesting party account information, requested party account information and request content in the request authentication information.
The first user terminal can scan the established collection authentication information through the image character recognition application program to obtain the collection party account information, the payer account information and the payment amount in the collection authentication information. Specifically, if the receipt authentication information is stored in the form of a picture or a document, the first user terminal may scan and identify the picture or the document, and obtain the payee account information, the payer account information, and the payment amount in the picture or the document; if the collection authentication information is stored in a link form, the first user terminal can access the specific consumption information through the link, scan and identify the specific consumption information, and acquire the payee account information, the payer account information and the payment amount.
S314: and the first user terminal adds the acquired requesting party account information, the acquired requested party account information and the request content into the request information.
After the first user terminal identifies the account information of the payee, the account information of the payer and the payment amount, the information can be automatically added into a corresponding information frame in a task window for establishing the payment information so as to perfect the payment information.
S4: and the first user terminal sends the request information with the request authentication information to the second user terminal.
The first user terminal can send the collection information with the collection authentication information to the second user terminal where the payer is located according to the account information of the payer in the collection information.
As can be seen from the foregoing embodiments of the present application, the request authentication information in the embodiments of the present application may be provided to the second user terminal to confirm the correctness of the request information.
The application also provides a user terminal for providing the request information. Fig. 3 is a functional block diagram of a user terminal for providing request information according to an embodiment of the present application. As shown in fig. 3, the user terminal includes:
a first instruction obtaining unit 100 for obtaining an instruction to establish request information;
a second instruction obtaining unit 200, configured to obtain an instruction for establishing the request authentication information;
a request information creating unit 300 for creating request information;
a request authentication information creating unit 400 for creating request authentication information;
an adding unit 500 for adding request authentication information to the request information;
a sending unit 600, configured to send request information with request authentication information attached.
Fig. 4 is a functional block diagram of a first instruction obtaining unit in a user terminal for providing request information according to an embodiment of the present application. As shown in fig. 4, the first instruction fetch unit 100 includes: a first key recognition module 101 and/or a first speech recognition module 102, wherein:
the first key identification module 101 is used for acquiring an instruction of establishing request information generated by a function key;
the first speech recognition module 102 is configured to obtain an instruction of creating request information generated by a speech prompt.
The user terminal can receive an external instruction according to the first key identification module and/or the first voice identification module. For example, when a function key of the user terminal for establishing the request information is pressed, the first key identification module can receive the instruction of the establishment request information and perform subsequent processing; similarly, when the voice prompt key is pressed, the first voice recognition module can receive an external voice prompt instruction through a microphone and other devices and perform subsequent processing.
Fig. 5 is a functional block diagram of a second instruction obtaining unit in a user terminal for providing request information according to an embodiment of the present application. As shown in fig. 5, the second instruction obtaining unit 200 includes: a second key recognition module 201 and/or a second speech recognition module 202, wherein:
the second key identification module 201 is configured to obtain an instruction for establishing request authentication information generated by function keys, where the function keys include at least one of a picture call function key, a document call function key, a picture taking function key, and a link call function key;
the second voice recognition module 202 is configured to obtain an instruction for establishing the request authentication information, where the instruction is generated by a voice prompt, and the voice prompt includes at least one of a call picture, a call document, a picture taking, and a call link.
The user terminal can obtain an instruction for establishing the collection authentication information through the function key. The function key for establishing the collection authentication information can comprise: at least one of the picture function key, the document function key, the picture taking function key and the link function key is called. When the function key for establishing the collection authentication information is pressed, the second key identification module can acquire a corresponding instruction according to the pressed function key. For example, when the function key for calling the picture is pressed, the second key identification module can acquire an instruction for calling the picture.
In addition, the user terminal can also obtain an instruction for establishing the collection authentication information through voice prompt. When the voice prompt key is pressed down, the second voice recognition module can receive external voice prompts through a microphone and other devices. The second speech recognition module may recognize at least one speech prompt including "call picture", "call document", "take picture", and "call link". After the second voice recognition module recognizes the voice prompt, a corresponding instruction for establishing the collection authentication information is obtained.
Fig. 6 is a functional block diagram of a request information creating unit in a user terminal for providing request information according to an embodiment of the present application. As shown in fig. 6, the request information creating unit 300 includes:
the task window opening module 301 is configured to open a task window for establishing the request information according to the obtained instruction for establishing the request information, where the task window may include a series of information frames, such as a requester account information frame, a requested party account information frame, and a request content frame, and is used to enter corresponding requester account information, requested party account information, and request content. In addition, the task window can also comprise a function key for establishing a request for authentication information or/and a voice prompt key. Wherein, the function key for establishing the request authentication information comprises the following steps: a picture function key, a document function key, a picture taking function key and a link function key.
The request information adding module 302 is configured to add the request content, the requested account information, and the requesting account information to corresponding information frames in the task window.
Fig. 7 is a functional block diagram of a request authentication information creating unit in a user terminal for providing request information according to an embodiment of the present application. As shown in fig. 7, the request authentication information creating unit 400 includes:
the calling module 401 is configured to call a picture or a document or a link as the request authentication information according to the calling instruction acquired by the second instruction acquiring unit;
a shooting module 402, configured to take a picture as the authentication information according to the shooting instruction obtained by the second instruction obtaining unit.
Fig. 8 is a functional block diagram of a user terminal for providing request information according to an embodiment of the present application. As shown in fig. 8, the user terminal includes:
a first instruction obtaining unit 110, configured to obtain an instruction for establishing request information;
a second instruction obtaining unit 210 configured to obtain an instruction for establishing the request authentication information;
a request authentication information establishing unit 310 for establishing request authentication information;
a scanning and identifying unit 410, configured to scan and identify the request authentication information in response to a user instruction, and obtain requesting party account information, requested party account information, and request content in the request authentication information through the identified request authentication information;
a request information creating unit 510 for creating request information;
an adding unit 610 for adding the request authentication information to the request information;
a sending unit 710, configured to send request information with request authentication information attached.
In an embodiment, the information of the payee account information, the payer account information and the payment amount is obtained by scanning the established receipt authentication information through a scanning and identifying unit. Specifically, if the receipt authentication information is stored in the form of a picture or a document, the scanning and identifying unit may scan and identify the picture or the document, and obtain the payee account information, the payer account information, and the payment amount in the picture or the document; if the collection authentication information is stored in a link form, the scanning and identifying unit can access the specific consumption information through the link, scan and identify the specific consumption information, and acquire the payee account information, the payer account information and the payment amount. Accordingly, the request information creating unit 510 in this embodiment includes: a task window opening module and a request information adding module, wherein:
the task window opening module 511 is configured to open a task window for establishing the request information according to the obtained instruction for establishing the request information, where the task window includes a function key or/and a voice prompt key for establishing the request authentication information;
the request information adding module 512 is configured to add the request content, the requesting party account information, and the requested party account information to the task window.
The embodiment of the application can find that the embodiment of the application does not limit the request authentication information, and the reliability of the request authentication information can be ensured by providing more forms of request authentication information to the requested party, so that the requested party can know the request content more intuitively.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose logic functions are determined by programming the device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate a dedicated integrated circuit chip 2. Furthermore, nowadays, instead of manually making integrated circuit chips, such programming is often implemented by "logic compiler" (software), which is similar to the software compiler used in program development and writing, but the original code before compiling is also written in a specific programming language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced library expression language), ahdl (alternate language description language), traffic, pl (kernel universal programming language), HDCal cu, jhdardeddescriptionlanguage, langva, Lola, HDL, pamm, hardsdyd (hardware description language), vhigh language (vhardscript description language), and the like, which are currently used in the world-language (vheregdivisdensionlanguage). It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC625D, atmel at91SAM, microchip pic18F26K20, and silicon labsc8051F320, the memory controller may also be implemented as part of the control logic of the memory.
Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments of the present application.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The application is operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
While the present application has been described with examples, those of ordinary skill in the art will appreciate that there are numerous variations and permutations of the present application without departing from the spirit of the application, and it is intended that the appended claims encompass such variations and permutations without departing from the spirit of the application.

Claims (17)

1. A method for providing requested information, comprising:
a first user terminal acquires an instruction for establishing request information;
a first user terminal acquires an instruction for establishing request authentication information;
the first user terminal establishes request information with request authentication information;
the first user terminal sends the request information with the request authentication information to the second user terminal;
the request authentication information is used for providing the second user terminal with confirmation of correctness of the request information.
2. The method as claimed in claim 1, wherein the request message includes payment receipt information, and accordingly, the request authentication message includes payment receipt authentication information.
3. The method of claim 2, wherein the payment authentication information comprises at least one of a consumption bill detail document, a consumption detail picture, an electronic consumption invoice, and a link for querying consumption details.
4. The method of claim 1, wherein the instruction for the first user terminal to obtain the request information comprises:
the first user terminal acquires an instruction for establishing request information through a function key;
or,
the first user terminal obtains the instruction of establishing the request information through voice prompt.
5. The method of claim 1, wherein the obtaining of the request for authentication information from the first user terminal comprises:
the first user terminal acquires an instruction for establishing request authentication information through a function key;
or,
the first user terminal obtains an instruction for establishing the authentication request information through voice prompt.
6. The method of claim 5, wherein the function key includes at least one of a call picture function key, a call document function key, a take picture function key, and a call link function key.
7. The method of claim 5, wherein the voice prompt comprises at least one of a call to a picture, a call to a document, a picture taken, a call to a link.
8. The method for providing request information according to claim 1, wherein the establishing, by the first user terminal, the request information with the request authentication information specifically includes:
the first user terminal opens a task window for establishing the request information according to the acquired instruction for establishing the request information, wherein the task window comprises a function key or/and a voice prompt key for establishing the request authentication information;
the first user terminal adds request content, requesting party account information and requested party account information in the task window of the request information;
the first user terminal establishes the request authentication information according to the acquired instruction for establishing the request authentication information, and adds the request authentication information into the request information.
9. The method for providing request information according to claim 1, wherein the establishing, by the first user terminal, the request information with the request authentication information specifically includes:
the first user terminal opens a task window for establishing the request information according to the acquired instruction for establishing the request information, wherein the task window comprises a function key or/and a voice prompt key for establishing the request authentication information;
the first user terminal establishes request authentication information according to the acquired instruction for establishing the request authentication information, and adds the request authentication information into the request information;
the first user terminal responds to a user instruction to scan and identify the request authentication information, and acquires requesting party account information, requested party account information and request content in the request authentication information through the identified request authentication information;
and the first user terminal adds the acquired requesting party account information, the acquired requested party account information and the request content into the request information.
10. The method according to claim 8 or 9, wherein the sending, by the first user terminal, the request message with the request authentication information attached thereto to the second user terminal specifically includes:
and the first user terminal sends the request information with the request authentication information to a second user terminal where the requested party is located according to the account information of the requested party in the request information.
11. A user terminal for providing requested information, comprising: the system comprises a first instruction acquisition unit, a second instruction acquisition unit, a request information establishment unit, a request authentication information establishment unit, an addition unit and a sending unit, wherein:
the first instruction acquisition unit is used for acquiring an instruction for establishing request information;
the second instruction acquisition unit is used for acquiring an instruction for establishing the request authentication information;
the request information establishing unit is used for establishing request information;
the request authentication information establishing unit is used for establishing request authentication information;
the adding unit is used for adding the request authentication information into the request information;
the sending unit is used for sending request information with request authentication information.
12. The user terminal according to claim 11, wherein the first instruction obtaining unit comprises a first key recognition module and/or a first voice recognition module, and wherein:
the first key identification module is used for acquiring an instruction of establishing request information generated by a functional key;
the first voice recognition module is used for acquiring an instruction of establishing request information generated through voice prompt.
13. The user terminal of claim 11, wherein the second instruction obtaining unit comprises a second key recognition module and/or a second voice recognition module, and wherein:
the second key identification module is used for acquiring an instruction for establishing request authentication information generated by function keys, wherein the function keys comprise at least one of a picture calling function key, a document calling function key, a picture taking function key and a link calling function key;
the second voice recognition module is used for acquiring an instruction for establishing request authentication information generated through voice prompt, wherein the voice prompt comprises at least one voice prompt of calling a picture, calling a document, shooting a picture and calling a link.
14. The ue according to claim 11, wherein the request information creating unit specifically includes: a task window opening module and a request information adding module, wherein:
the task window opening module is used for opening a task window for establishing the request information according to the acquired instruction for establishing the request information, and the task window comprises a function key or/and a voice prompt key for establishing the request authentication information;
and the request information adding module is used for adding the request content, the requesting party account information and the requested party account information into the task window.
15. The ue according to claim 13, wherein the request authentication information creating unit specifically includes:
the calling module is used for calling a picture or a document or a link as request authentication information according to the calling instruction acquired by the second instruction acquisition unit;
and the shooting module is used for shooting pictures as the request authentication information according to the shooting instruction acquired by the second instruction acquisition unit.
16. The user terminal of claim 11, further comprising: and the scanning and identifying unit is used for scanning and identifying the request authentication information in response to a user instruction, and acquiring requesting party account information, requested party account information and request content in the request authentication information through the identified request authentication information.
17. The ue according to claim 16, wherein the request information creating unit comprises: a task window opening module and a request information adding module, wherein:
the task window opening module is used for opening a task window for establishing the request information according to the acquired instruction for establishing the request information, and the task window comprises a function key or/and a voice prompt key for establishing the request authentication information;
and the request information adding module is used for adding the request content, the requesting party account information and the requested party account information into the task window.
CN201410753538.XA 2014-12-10 2014-12-10 Method for providing request information and user terminal Pending CN105741103A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201410753538.XA CN105741103A (en) 2014-12-10 2014-12-10 Method for providing request information and user terminal
PCT/CN2015/096246 WO2016091115A1 (en) 2014-12-10 2015-12-03 Method for providing request information and user terminals

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201410753538.XA CN105741103A (en) 2014-12-10 2014-12-10 Method for providing request information and user terminal

Publications (1)

Publication Number Publication Date
CN105741103A true CN105741103A (en) 2016-07-06

Family

ID=56106701

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201410753538.XA Pending CN105741103A (en) 2014-12-10 2014-12-10 Method for providing request information and user terminal

Country Status (2)

Country Link
CN (1) CN105741103A (en)
WO (1) WO2016091115A1 (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040172361A1 (en) * 2003-02-28 2004-09-02 Hitachi, Ltd. Dutch account settlement method
JP2006252243A (en) * 2005-03-11 2006-09-21 Fujitsu Ltd Expense splitting information processing program, expense splitting information processing method and expense splitting information processor
CN103001970A (en) * 2012-12-20 2013-03-27 中国工商银行股份有限公司 Safety authentication method and safety authentication system
US20130317893A1 (en) * 2012-05-24 2013-11-28 Softech, Inc. System and method for coordinating event participation and payment
CN103824190A (en) * 2013-12-26 2014-05-28 深圳光启创新技术有限公司 Payment method, client, receiving end and system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101571939A (en) * 2008-04-30 2009-11-04 中国移动通信集团公司 Method, device and system for using electronic checks for business transaction
CN102663586B (en) * 2012-03-21 2016-07-06 华为技术有限公司 A kind of method completing to pay by two mobile terminals
CN103457913B (en) * 2012-05-30 2017-10-13 阿里巴巴集团控股有限公司 Data processing method, communication terminal, server and system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040172361A1 (en) * 2003-02-28 2004-09-02 Hitachi, Ltd. Dutch account settlement method
JP2006252243A (en) * 2005-03-11 2006-09-21 Fujitsu Ltd Expense splitting information processing program, expense splitting information processing method and expense splitting information processor
US20130317893A1 (en) * 2012-05-24 2013-11-28 Softech, Inc. System and method for coordinating event participation and payment
CN103001970A (en) * 2012-12-20 2013-03-27 中国工商银行股份有限公司 Safety authentication method and safety authentication system
CN103824190A (en) * 2013-12-26 2014-05-28 深圳光启创新技术有限公司 Payment method, client, receiving end and system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
张薇: ""万能"的支付宝", 《电脑知识与技术-经验技巧》 *

Also Published As

Publication number Publication date
WO2016091115A1 (en) 2016-06-16

Similar Documents

Publication Publication Date Title
WO2021103694A1 (en) Payment system and method, server device, medium and apparatus
US10380237B2 (en) Smart optical input/output (I/O) extension for context-dependent workflows
US20180197170A1 (en) Method and device for implementing service function
US12045802B2 (en) Method and apparatus for information exchange
WO2016145992A1 (en) Method and corresponding device for starting service through voice in communication software
US20150149925A1 (en) Emoticon generation using user images and gestures
US20200402040A1 (en) Data processing method, terminal device and data processing system
WO2021169529A1 (en) Method, apparatus and device for identifying risk in code image
US20230359687A1 (en) Browser-based mobile image capture
US11651350B2 (en) Lens depiction profile technology
US11526872B2 (en) Smart-card with built-in object resolution and direct network interface
CN205068626U (en) Self -service terminal of internet bar's intelligence
US11308317B2 (en) Electronic device and method for recognizing characters
CN109034808B (en) Operation method and device of payment application program and terminal equipment
US11580528B2 (en) Device with built-in bill capture, analysis, and execution
CN105741103A (en) Method for providing request information and user terminal
JP2017514225A (en) Smart optical input / output (I / O) extension for context-sensitive workflows
CN112837053A (en) Payment processing method and device
US20220398656A1 (en) Voice Enabled Flash Briefing of Banking Information
WO2023045702A1 (en) Information recommendation method and electronic device
CN116521637A (en) Method and device for processing variable data, electronic equipment and storage medium
CN117273949A (en) Account type conversion method and device of fund pool and storage medium
CN117075857A (en) Processing method, device, equipment and storage medium of internet banking system
CN115208437A (en) Virtual card calling method and related equipment
CN116643678A (en) Data processing method, device, server and medium based on public service

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1226182

Country of ref document: HK

RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20160706

REG Reference to a national code

Ref country code: HK

Ref legal event code: WD

Ref document number: 1226182

Country of ref document: HK