WO2016131386A1 - 一种业务管理方法和装置 - Google Patents
一种业务管理方法和装置 Download PDFInfo
- Publication number
- WO2016131386A1 WO2016131386A1 PCT/CN2016/073446 CN2016073446W WO2016131386A1 WO 2016131386 A1 WO2016131386 A1 WO 2016131386A1 CN 2016073446 W CN2016073446 W CN 2016073446W WO 2016131386 A1 WO2016131386 A1 WO 2016131386A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- electronic device
- service
- user account
- wearable electronic
- request
- 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.)
- Ceased
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
- G06Q20/321—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wearable devices
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3821—Electronic credentials
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4012—Verifying personal identification numbers [PIN]
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for transactions
- G06Q20/40145—Biometric identity checks
Definitions
- the present application relates to the field of information management, and in particular, to a service management method and apparatus.
- the purpose of the application is to provide a service management method and apparatus to solve the problem that the existing service processing is inefficient and the security is poor.
- a business management method that includes:
- the wearable electronic device receives a service use request
- the wearable electronic device presents the verification code.
- the wearable electronic device further includes: before receiving the service use request:
- the wearable electronic device acquires the attribute information of the user account from the user information management system by using any one of the communication connection manners, and establishes an association with the user account locally based on the attribute information.
- the wearable electronic device receives the service use request, and specifically includes:
- the wearable electronic device receives the voice sent by the user, and performs keyword matching or voiceprint matching on the voice sample with the preset voice sample, and determines that the service use request is received when determining that the match is successful; or
- the wearable electronic device receives the fingerprint input by the user, and determines that the business use request is received when it is determined that the fingerprint and the preset account call fingerprint template match successfully; or
- the wearable electronic device receives the operation behavior input by the user, and determines that the operation behavior matches the preset account calling behavior, and determines that the service use request is received.
- the wearable electronic device determines, according to the service usage request, a corresponding user account, including:
- the wearable electronic device After receiving the service use request, the wearable electronic device determines a service type of the service use request based on the service use request, and determines a corresponding user account based on the service type.
- the method further includes:
- the wearable electronic device determines that the service type involved in the service use request exceeds the use right of the user account, the wearable electronic device connects to the third-party electronic device by using any one of the communication connection manners;
- the wearable electronic device sends the attribute information of the user account and the service use request to a third-party electronic device for verification, and receives a test result fed back by the third-party electronic device;
- the wearable electronic device determines to perform a subsequent operation when it is determined that the verification is successful based on the verification result.
- the method further includes:
- the wearable electronic device determines that the service type involved in the service use request exceeds the use right of the user account, the wearable electronic device determines that communication exists with the bound third-party electronic device by any one of the communication connection manners. After connecting, be sure to perform subsequent operations.
- the service can be continuously completed when the service type involved in the service use request exceeds the usage right of the user account, thereby improving the security and reliability of the service.
- the wearable electronic device presents the verification code, specifically:
- the wearable electronic device presents a barcode
- the wearable electronic device presents a two-dimensional code if the service type of the service usage request is a request for collection of the user account.
- the wearable electronic device presents the verification code, specifically:
- the wearable electronic device presents the verification code in a screen, or sends the verification code to the service using device in a setting manner.
- the method further includes:
- the wearable electronic device causes the service using device to trigger a corresponding business process after passing the security verification based on the verification code
- the wearable electronic device After confirming that the business process is completed, acquires key information related to the service request of the user account, and presents the information.
- the communication connection manner includes at least a Bluetooth connection, a WIFI connection, a wireless network card connection, and a contactless radio frequency identification connection.
- a service management device comprising:
- a receiving unit configured to receive a service usage request
- a generating unit configured to determine a corresponding user account based on the service usage request, and obtain a verification code corresponding to the user account, where the verification code is generated based on user verification information of the user account;
- a processing unit configured to present the verification code.
- the receiving unit before receiving the service usage request, the receiving unit is further configured to:
- the attribute information of the user account is obtained from the user information management system by any one of the communication connection methods, and the association is established locally with the user account based on the attribute information.
- the receiving unit when receiving a service usage request, is specifically configured to:
- the generating unit is specifically configured to:
- the generating unit is further configured to:
- the wearable electronic device When it is determined that the service type involved in the service use request exceeds the usage right of the user account, the wearable electronic device connects to the third-party electronic device by using any one of the communication connection manners;
- the generating unit is further configured to:
- the wearable electronic device determines that the communication connection is established with the bound third-party electronic device by any one of the communication connection manners, and then determines to perform Follow-up actions.
- the service can be continuously completed when the service type involved in the service use request exceeds the usage right of the user account, thereby improving the security and reliability of the service.
- the processing unit is specifically configured to:
- the service type of the service use request is a request for charging the user account, a two-dimensional code is presented.
- the processing unit is specifically configured to:
- the verification code is presented in a screen, or the verification code is sent to the service using device in a setting manner.
- the processing unit is further configured to:
- the key information related to the service request of the user account is obtained and presented.
- the communication connection mode adopted by the receiving unit includes at least a Bluetooth connection, a WIFI connection, a wireless network card connection, and a contactless radio frequency identification connection.
- FIG. 1 is a schematic flowchart of a service management method in an embodiment of the present application
- FIG. 2 is a schematic diagram of a payment display interface generated by a wearable electronic device invoking a third party payment account in the embodiment of the present application;
- FIG. 3 is a schematic diagram of message push after a wearable electronic device invokes a third-party payment account to complete payment in the embodiment of the present application;
- FIG. 4 is a schematic structural diagram of a service management apparatus according to an embodiment of the present application.
- a service management method is provided in the embodiment of the present application, and the specific process is as follows:
- Step 100 The wearable electronic device receives a service use request.
- the wearable electronic device receiving the service use request may adopt the following initiation manner:
- the wearable electronic device receives the voice sent by the user, and performs keyword matching or voiceprint matching with the preset voice sample, and determines that the service use request is received when it is determined that the matching is successful.
- the wearable electronic device detects the voice sent by the user in the power-on state, performs keyword matching based on the voice, and determines that the service use request is received if the voice includes “payment”.
- the wearable electronic device detects the voice sent by the user in the power-on state, performs voiceprint matching based on the voice, and determines to receive the service use request if it is determined that the voice is the same as the preset voice and is from the same user.
- the wearable electronic device receives the fingerprint input by the user, and determines that the business use request is received when it is determined that the fingerprint and the preset account call fingerprint template match successfully.
- the wearable electronic device receives the operation behavior input by the user, and determines that the operation behavior matches the preset account calling behavior, and determines that the service use request is received.
- the wearable electronic device detects the user's operation behavior in the power-on state, such as shaking, flipping the wrist, tapping the screen, double-clicking the screen, or clicking a physical button, and determining the operation behavior and the preset account.
- the calling behavior is matched successfully, and it is determined that the service usage request is received.
- Step 101 The wearable electronic device determines a corresponding user account based on the service usage request, and obtains a verification code corresponding to the user account, where the verification code is generated based on user verification information of the user account.
- the verification code may be generated by the user verification information of the user account, or may be obtained from the management system of the user account. That is, the verification code of the user account is pre-stored in the management system of the user account.
- the wearable electronic device acquires the attribute information of the user account from the user information management system by using any one of the communication connection manners, and establishes an association with the user account locally based on the attribute information.
- the operation is to obtain the attribute information of the user account accurately.
- a plurality of user accounts of different service types can be set.
- the user account can be a third-party payment account, a student account, or a resident ID card account.
- the wearable electronic device connects to a terminal (such as a smart electronic device such as a computer or a mobile phone) to obtain various attribute information of the third-party payment account in the management system of the third-party payment account that the terminal logs in, including the payment.
- a terminal such as a smart electronic device such as a computer or a mobile phone
- the wearable electronic device is connected to the terminal (for example, a smart electronic device such as a computer or a mobile phone) to obtain various attribute information of the first student account in the management system of the student account registered by the terminal, including the name and gender of the student account. , student number, book borrowing information and other attribute information;
- the terminal for example, a smart electronic device such as a computer or a mobile phone
- the wearable electronic device is connected to the terminal (for example, an intelligent electronic device such as a computer or a mobile phone) to obtain various attribute information of the resident identity account in the household registration management system registered by the terminal, including the name of the resident identity card account. , ID number, residential address, portrait and other attribute information.
- the terminal for example, an intelligent electronic device such as a computer or a mobile phone
- the communication connection mode includes at least a Bluetooth connection, a WIFI connection, a wireless network card connection, and a contactless radio frequency identification connection.
- the wearable electronic device determines the corresponding user account based on the service use request, and the specific process is: after the wearable electronic device receives the service use request, determining, according to the service use request, the service type of the service use request, and calling the service type based on the service type The corresponding user account.
- the wearable electronic device After the service usage request received by the electronic device is received, it is analyzed whether the service usage request can be successfully matched with the preset user account calling mode of a certain service type, and after confirming that the matching is successful, the user account corresponding to the service type is invoked. If the wearable electronic device is provided with two types of service accounts, respectively, a third-party payment account and a student account, wherein the third-party payment account is invoked in a fingerprint mode, and the student account is called a voice. Student ID", if the wearable electronic device receives the fingerprint input by the user in the power-on state, and the fingerprint template is successfully matched with the preset third-party account, Call the corresponding third party account.
- any one of the following two operation actions may be selected to be performed.
- the first operation behavior when the wearable electronic device determines that the type of service involved in the service use request exceeds the use right of the user account, the wearable electronic device connects to the third-party electronic device by using any one of the communication connection manners; The electronic device sends the attribute information of the user account and the service use request to the third-party electronic device for verification, and receives the verification result fed back by the third-party electronic device; when the wearable electronic device determines that the verification is successful based on the verification result, It is determined that the subsequent operation is performed, that is, the verification code corresponding to the user account is obtained.
- the user account invoked by the wearable electronic device based on the service use request is a third party payment account
- the service request is a currency that spends a large amount of money from the third party payment account (the payment quota authority of the wearable electronic device that has exceeded the third party payment account setting)
- the wearable electronic device is connected to the third-party electronic device (ie, the terminal)
- the wearable electronic device detecting the information security of the third-party payment account in the wearable electronic device, and confirming the security of the payment environment, obtaining the verification code of the third-party account.
- the second operation behavior is: when the wearable electronic device determines that the service type involved in the service use request exceeds the use right of the user account, the wearable electronic device determines that the service type involved in the service use request exceeds the use right of the user account, the wearable After the electronic device determines that there is a communication connection with the bound third-party electronic device by using any one of the communication connection manners, it is determined that the subsequent operation is performed, that is, the verification code corresponding to the user account is obtained.
- the user account invoked by the wearable electronic device based on the service use request is a third party payment account
- the service request is a currency that spends a large amount of money from the third party payment account (the payment quota authority of the wearable electronic device that has exceeded the third party payment account setting)
- the wearable electronic device obtains a verification code of the third-party account after establishing a communication connection with the bound third-party electronic device by connecting with the third-party electronic device (ie, the terminal).
- the service can be completed when the service type involved in the service use request exceeds the usage right of the user account, thereby improving the security and reliability of the service.
- Step 102 The wearable electronic device presents the verification code.
- the specific wearable electronic device presents the verification code.
- the specific process is: if the service type requested by the service is an expense request corresponding to the user account, the wearable electronic device presents the barcode; if the service type requested by the service is the corresponding user account When requested, the wearable electronic device presents a two-dimensional code.
- the verification code may be a barcode or a two-dimensional code.
- the verification code is not limited to one verification code according to different service types, for example, for the same third party payment account, A barcode and a two-dimensional code are generated, wherein the barcode is used for payment and the two-dimensional code is used for payment.
- the wearable electronic device presents the verification code, and the following two methods are available:
- the first way is: the wearable electronic device presents the above verification code on the screen.
- the second way is: the wearable electronic device sends the verification code to the service using device by setting mode.
- the wearable electronic device After the wearable electronic device generates the verification code by using the user verification information set by the corresponding user account or obtains the verification code of the user account by other means, the wearable code needs to be presented to the service using device, for example, in a shopping mall.
- the presentation here may be directly presented on the screen of the wearable electronic device or transmitted to the service using device in the case of a Bluetooth connection, which can further improve the security of the service.
- the wearable electronic device After the wearable electronic device presents the verification code, the wearable electronic device causes the service use device to trigger the corresponding service process after the security verification is performed based on the verification code; and the wearable electronic device acquires the user account after confirming that the service process is completed. Key information related to the above business request and presented.
- a wearable electronic device is a watch
- the property information of the user account is obtained when the watch is connected to the terminal for the first time
- the specific connection mode of the watch and the terminal may be a Bluetooth connection
- the WIFI connection may be connected when the watch supports the wireless connection. It can also be a wireless network card connection or a contactless radio frequency identification connection. It is not limited to one connection method.
- three types of user accounts are set up, including a third-party payment account, a student account, and an ID card account of a resident.
- a setting manner of displaying various display interfaces for displaying the verification code for example, setting a payment display interface of the third party payment account, a student information display interface of the student account, and a calling mode of the identity information display interface of the ID card account are set.
- the display mode of the display interface of different types of user accounts supports the customization of the system, for example, setting the operation behavior "flip the wrist” to call up the payment display interface, setting the voice “student” to call up the student information display interface, and setting the operation behavior "Tap the screen” to call up the identity information display interface;
- the display mode of the verification code display interface is not unique, as long as the different callout modes can be distinguished from the display interface of the user account of different service types, and can be set by itself, for example Set the voice “payment” to call up the payment display interface, set the voice “student” to call up the student information display interface, and set the voice “ID card” to call up the identity information display interface as an example for explanation.
- the watch receives the user voice including "payment"
- the watch invokes the attribute information of the third-party payment account to generate a payment display interface including the verification code, where the verification code may be a barcode or a two-dimensional code, and a barcode is generated for the third-party payment account at the top of the payment display interface for payment.
- the bottom of the payment display interface generates a two-dimensional code for collecting money.
- the bar code occupies 1/3 of the payment display interface, and the two-dimensional code occupies 2/3 of the payment display interface.
- FIG. 2 The specific effect is shown in FIG. 2 .
- the store POS machine scans the barcode of the payment display interface to complete the payment. It should be noted that, during the payment process, the watch does not need to be connected with the terminal moment, and the payment is simple and the security is high. Further, after the payment is completed, after the watch and the terminal are successfully connected, the watch can obtain key information about the business transaction of the third payment account, for example, obtaining payment amount, payment details, etc., and the specific effect can be seen in FIG. 3 Shown.
- the watch when a student carries the watch and needs to read the book in the library, the student needs to pass the security check of the student identity to enter the library.
- the watch receives the user voice containing the “student”, the watch invokes the attribute information generation of the student account.
- a student information display interface including a verification code, where the verification code can be a barcode or a two-dimensional code, assuming a barcode, and generating a bar on the student information display interface for the student account
- the security device scans the barcode on the student information display interface to complete the identity verification. It should be noted that during the security check, the watch does not need to be connected to the terminal at the moment, and the operation is simple and the security is high.
- the watch receives the user.
- the watch invokes the attribute information of the identity account of Zhang to generate an identity information display interface including the verification code, where the verification code can be a barcode or a two-dimensional code, assuming a barcode, for the Zhang ID card account
- the verification code can be a barcode or a two-dimensional code, assuming a barcode, for the Zhang ID card account
- a barcode is generated on the identity information display interface, and after the identity information display interface is displayed on the watch, the ID card verification device scans the barcode on the identity information display interface to complete the identity verification.
- an embodiment of the present invention provides a service management apparatus.
- the method includes a receiving unit 40, a generating unit 41 and a processing unit 42, wherein:
- the receiving unit 40 is configured to receive a service usage request.
- a generating unit 41 configured to determine a corresponding user account based on the service usage request, and obtain a verification code corresponding to the user account, where the verification code is generated based on user verification information of the user account;
- the processing unit 42 is configured to present the verification code.
- the receiving unit 40 before receiving the service usage request, the receiving unit 40 is further configured to:
- the attribute information of the user account is obtained from the user information management system by any one of the communication connection methods, and the user account is locally associated with the user account based on the attribute information.
- the receiving unit 40 when receiving the service usage request, is specifically configured to:
- the generating unit 41 is specifically configured to:
- the generating unit 41 is further configured to:
- the wearable electronic device When it is determined that the service type involved in the service use request exceeds the usage right of the user account, the wearable electronic device connects to the third-party electronic device by using any one of the communication connection manners;
- the generating unit 41 is further configured to:
- the wearable electronic device determines that the communication operation is connected to the bound third-party electronic device by any one of the communication connection manners, and then determines to perform the subsequent operation. .
- the service can be continuously completed when the service type involved in the service use request exceeds the usage right of the user account, thereby improving the security and reliability of the service.
- the processing unit 42 is specifically configured to:
- a two-dimensional code is presented if the service type of the service request is a request for charging the user account.
- the processing unit 42 is specifically configured to:
- the verification code is presented on the screen, or the verification code is sent to the service using device by setting.
- the processing unit 42 is further configured to:
- the key information related to the business request of the user account is obtained and presented.
- the communication connection mode adopted by the receiving unit 40 includes at least a Bluetooth connection, a WIFI connection, a wireless network card connection, and a contactless radio frequency identification connection.
- the wearable electronic device receives a service use request, determines a corresponding user account based on the service use request, and obtains a verification code corresponding to the user account, where the verification code is a user based on the user account.
- the verification information is generated; finally, the wearable electronic device presents the verification code, so that the business process can be greatly reduced, and the business completion efficiency can be further improved to ensure the security of the service and improve the user experience.
- embodiments of the present application can be provided as a method, system, or computer program product.
- the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
- the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Telephone Function (AREA)
Abstract
一种业务管理方法和装置,用以解决现有业务处理效率低下且安全性差的问题。该方法为,首先穿戴电子设备接收业务使用请求(100);然后该穿戴电子设备基于该业务使用请求确定对应的用户账户,并获取该用户账户对应的验证码,其中,该验证码是基于该用户账户的用户验证信息生成的(101);最后该穿戴电子设备呈现该验证码(102)。这样,能够大大减少业务流程,提高业务完成效率的基础上进一步还能保证业务的安全性。
Description
本申请涉及信息管理领域,尤其涉及一种业务管理方法和装置。
随着电子信息技术的蓬勃发展,需要完成的业务种类越来越多,涉及的用户账户种类也越来越多,在业务的执行过程中,需要输入用户账户的各种信息,随之而来的问题是人们需要记住各种账户的口令和密码,这无疑降低了业务完成的效率,此外人们还需要时刻提防各种克隆与盗密的发生。
基于这种缺陷与不便,通过运行终端(包括电脑和手机)来完成各种业务,但是如何应对运行环境中的各种盗号病毒、木马的威胁成为安全保障的关键问题。尽管如此,随着各种钓鱼网站与新型盗号技术的兴起,也令用户防不胜防,各类盗号案例时有发生,经常见诸报端,安全性较低。
再例如,对于学生在校内进行的任何活动一般都需要出示学生本人的学生证,若学生证丢失或暂时不能应用如遗忘在宿舍或外地,假设此时急需借阅图书馆资料,导致不能正常实现针对学生账户图书借阅这一业务,影响业务完成。
有鉴于此,急需一种简单,易行的业务管理方法来实现账户的安全管理,在快速实现账户间的各种业务的基础上保证账户的安全。
申请内容
本申请的目的是提供一种业务管理方法和装置,以解决现有业务处理效率低下且安全性差的问题。
本申请的目的是通过以下技术方案实现的:
一种业务管理方法,包括:
穿戴电子设备接收业务使用请求;
所述穿戴电子设备基于所述业务使用请求确定对应的用户账户,并获取所述用户账户对应的验证码,其中,所述验证码是基于所述用户账户的用户验证信息
生成的;
所述穿戴电子设备呈现所述验证码。
这样,能够大大减少业务流程,提高业务完成效率的基础上进一步还能保证业务的安全性,提升用户的体验效果。
可选的,穿戴电子设备在接收业务使用请求之前,进一步包括:
穿戴电子设备通过通信连接方式中的任何一种方式,从用户信息管理系统获取所述用户账户的属性信息,并基于所述属性信息在本地与所述用户账户建立关联。
可选的,穿戴电子设备接收业务使用请求,具体包括:
穿戴电子设备接收用户发出的语音,并将所述语音与预设的语音样本进行关键字匹配或声纹匹配,在确定匹配成功时,判定接收到业务使用请求;或者,
穿戴电子设备接收用户输入的指纹,并在确定所述指纹与预设的账户调出指纹模本匹配成功时,确定接收到业务使用请求;或者,
穿戴电子设备接收用户输入的操作行为,并在确定所述操作行为与预设的账户调用行为匹配成功,确定接收到业务使用请求。
可选的,所述穿戴电子设备基于所述业务使用请求确定对应的用户账户,包括:
穿戴电子设备接收到业务使用请求之后,基于所述业务使用请求,确定所述业务使用请求的业务类型,基于所述业务类型确定对应的用户账户。
可选的,所述穿戴电子设备基于所述业务使用请求确定对应的用户账户之后,获取所述用户账户对应的验证码之前,进一步包括:
所述穿戴电子设备确定所述业务使用请求中涉及的业务类型超过用户账户的使用权限时,所述穿戴电子设备通过所述通信连接方式中的任何一种方式与第三方电子设备进行连接;
所述穿戴电子设备将所述用户账户的属性信息及所述业务使用请求发送到第三方电子设备进行校验,并接收所述第三方电子设备反馈的检验结果;
所述穿戴电子设备基于所述检验结果确定校验成功时,确定执行后续操作。
可选的,所述穿戴电子设备基于所述业务使用请求确定对应的用户账户之后,获取所述用户账户对应的验证码之前,进一步包括:
所述穿戴电子设备确定所述业务使用请求中涉及的业务类型超过用户账户的使用权限时,所述穿戴电子设备确定通过通信连接方式中的任何一种方式与绑定的第三方电子设备存在通信连接后,确定执行后续操作。
这样,能够在业务使用请求中涉及的业务类型超过用户账户的使用权限时继续完成该业务,提高业务的安全性、可靠性。
可选的,所述穿戴电子设备呈现所述验证码,具体包括:
若所述业务使用请求的业务类型为所述用户账户的支出请求时,所述穿戴电子设备呈现条形码;
若所述业务使用请求的业务类型为所述用户账户的收取请求时,所述穿戴电子设备呈现二维码。
可选的,所述穿戴电子设备呈现所述验证码,具体包括:
所述穿戴电子设备将所述验证码呈现在屏幕中,或者,将所述验证码通过设定方式发送至所述业务使用装置。
可选的,所述穿戴电子设备呈现所述验证码之后,进一步包括:
所述穿戴电子设备令业务使用装置基于所述验证码通过安全验证后,触发相应的业务流程;
所述穿戴电子设备在确认所述业务流程执行完毕后,获取用户账户与所述业务请求相关的关键信息,并进行呈现。
可选的,所述通信连接方式至少包括蓝牙连接,WIFI连接,无线网卡连接和非接触式射频识别连接。
一种业务管理装置,包括:
接收单元,用于接收业务使用请求;
生成单元,用于基于所述业务使用请求确定对应的用户账户,并获取所述用户账户对应的验证码,其中,所述验证码是基于所述用户账户的用户验证信息生成的;
处理单元,用于呈现所述验证码。
这样,能够大大减少业务流程,提高业务完成效率的基础上进一步还能保证业务的安全性,提升用户的体验效果。
可选的,在接收业务使用请求之前,所述接收单元进一步用于:
通过通信连接方式中的任何一种方式,从用户信息管理系统获取所述用户账户的属性信息,并基于所述属性信息在本地与所述用户账户建立关联。
可选的,接收业务使用请求时,所述接收单元具体用于:
接收用户发出的语音,并将所述语音与预设的语音样本进行关键字匹配或声纹匹配,在确定匹配成功时,判定接收到业务使用请求;或者,
接收用户输入的指纹,并在确定所述指纹与预设的账户调出指纹模本匹配成功时,确定接收到业务使用请求;或者,
接收用户输入的操作行为,并在确定所述操作行为与预设的账户调用行为匹配成功,确定接收到业务使用请求。
可选的,基于所述业务使用请求确定对应的用户账户时,所述生成单元具体用于:
接收到业务使用请求之后,基于所述业务使用请求,确定所述业务使用请求的业务类型,基于所述业务类型确定对应的用户账户。
可选的,基于所述业务使用请求确定对应的用户账户之后,获取所述用户账户对应的验证码之前,所述生成单元进一步用于:
确定所述业务使用请求中涉及的业务类型超过用户账户的使用权限时,所述穿戴电子设备通过所述通信连接方式中的任何一种方式与第三方电子设备进行连接;
将所述用户账户的属性信息及所述业务使用请求发送到第三方电子设备进行校验,并接收所述第三方电子设备反馈的检验结果;
基于所述检验结果确定校验成功时,确定执行后续操作。
可选的,基于所述业务使用请求确定对应的用户账户之后,获取所述用户账户对应的验证码之前,所述生成单元进一步用于:
确定所述业务使用请求中涉及的业务类型超过用户账户的使用权限时,所述穿戴电子设备确定通过通信连接方式中的任何一种方式与绑定的第三方电子设备存在通信连接后,确定执行后续操作。
这样,能够在业务使用请求中涉及的业务类型超过用户账户的使用权限时继续完成该业务,提高业务的安全性、可靠性。
可选的,呈现所述验证码时,所述处理单元具体用于:
若所述业务使用请求的业务类型为所述用户账户的支出请求时,呈现条形码;
若所述业务使用请求的业务类型为所述用户账户的收取请求时,呈现二维码。
可选的,呈现所述验证码时,所述处理单元具体用于:
将所述验证码呈现在屏幕中,或者,将所述验证码通过设定方式发送至所述业务使用装置。
可选的,呈现所述验证码之后,所述处理单元进一步用于:
令业务使用装置基于所述验证码通过安全验证后,触发相应的业务流程;
在确认所述业务流程执行完毕后,获取用户账户与所述业务请求相关的关键信息,并进行呈现。
可选的,所述接收单元采用的所述通信连接方式至少包括蓝牙连接,WIFI连接,无线网卡连接和非接触式射频识别连接。
图1为本申请实施例中业务管理方法流程示意图;
图2为本申请实施例中穿戴电子设备调用第三方支付账户生成的支付显示界面示意图;
图3为本申请实施例中穿戴电子设备调用第三方支付账户完成支付后消息推送的示意图;
图4为本申请实施例中业务管理装置结构示意图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本申请一部分实施例,并不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
参阅图1所示,本申请实施例中提供一种业务管理方法,具体流程如下:
步骤100:穿戴电子设备接收业务使用请求;
具体的,穿戴电子设备接收业务使用请求可以采用以下发起方式:
穿戴电子设备接收用户发出的语音,并将所述语音与预设的语音样本进行关键字匹配或声纹匹配,在确定匹配成功时,判定接收到业务使用请求。
例如,穿戴电子设备在开机状态下检测到用户发出的语音,基于该语音进行关键字匹配,若该语音中包括“支付”时,确定接收到业务使用请求。
又例如,穿戴电子设备在开机状态下检测到用户发出的语音,基于该语音进行声纹匹配,若确定语音中与预设的语音相同且来自同一个用户时,确定接收到业务使用请求。
穿戴电子设备接收用户输入的指纹,并在确定该指纹与预设的账户调出指纹模本匹配成功时,确定接收到业务使用请求。
穿戴电子设备接收用户输入的操作行为,并在确定该操作行为与预设的账户调用行为匹配成功,确定接收到业务使用请求。
例如,穿戴电子设备在开机状态下检测到用户的操作行为,例如摇一摇,翻转手腕、轻敲屏幕、双击屏幕、或者点击物理按键等操作行为,并在确定该操作行为与预设的账户调用行为匹配成功,确定接收到业务使用请求
步骤101:穿戴电子设备基于上述业务使用请求确定对应的用户账户,并获取该用户账户对应的验证码,其中,该验证码是基于该用户账户的用户验证信息生成的。
需要说明的是穿戴电子设备在获取用户账户对应的验证码时,该验证码可以是用户账户的用户验证信息生成的,也可以是从该用户账户的管理系统中获取的,
即该该用户账户的管理系统中预存有该用户账户的验证码。
进一步的,在预处理阶段,穿戴电子设备通过通信连接方式中的任何一种方式,从用户信息管理系统获取该用户账户的属性信息,并基于该属性信息在本地与该用户账户建立关联。
这样操作是为了能够准确获取用户账户的属性信息,这里可以设置多种不同业务类型的用户账户,例如,用户账户可以是第三方支付账户,也可以是学生账户,也可以是居民身份证账户。
针对第三方支付账户,穿戴电子设备通过与终端(例如电脑、手机等智能电子设备)连接,获取终端登录的第三方支付账户的管理系统中该第三方支付账户的各种属性信息,包括该支付账户的户名,支付密码、可用余额等各种属性信息;
针对学生账户,穿戴电子设备通过与终端(例如电脑、手机等智能电子设备)连接,获取终端登录的学生账户的管理系统中该第学生账户的各种属性信息,包括该学生账户的姓名,性别、学号,图书借阅信息等各种属性信息;
针对居民身份证账户,穿戴电子设备通过与终端(例如电脑、手机等智能电子设备)连接,获取终端登录的户籍管理系统中该居民身份账户的各种属性信息,包括该居民身份证账户的姓名,身份证号、居住地址、肖像等各种属性信息。
具体的,通信连接方式至少包括蓝牙连接,WIFI连接,无线网卡连接和非接触式射频识别连接。
具体的,穿戴电子设备基于业务使用请求确定对应的用户账户,具体过程为:穿戴电子设备接收到业务使用请求之后,基于该业务使用请求,确定该业务使用请求的业务类型,基于该业务类型调用对应的用户账户。
例如,穿戴电子设备接收到的业务使用请求后,分析该业务使用请求是否能够与预设的某一业务类型的用户账户调用方式匹配成功,在确认匹配成功,调用该业务类型对应的用户账户。假如,该穿戴电子设备中设置有两种业务类型的用户账户,分别为第三方支付账户和学生账户,其中第三方支付账户的调用方式为指纹调出方式,学生账户的调出方式为语音“学生证”,若该穿戴电子设备在开机状态下接收到用户输入的指纹,且与预设的第三方账户调出指纹模本匹配成功时,
调用对应的第三方账户。
进一步的,穿戴电子设备基于业务使用请求调用对应的用户账户之后,确定该业务使用请求中涉及的业务类型超过用户账户的使用权限时,进一步的,可以选择执行以下两种操作行为的任意一种。
第一种操作行为:穿戴电子设备确定业务使用请求中涉及的业务类型超过用户账户的使用权限时,该穿戴电子设备通过通信连接方式中的任何一种方式与第三方电子设备进行连接;该穿戴电子设备将该用户账户的属性信息及该业务使用请求发送到第三方电子设备进行校验,并接收该第三方电子设备反馈的检验结果;该穿戴电子设备基于该检验结果确定校验成功时,确定执行后续操作,即获取该用户账户对应的验证码。
例如,穿戴电子设备基于业务使用请求调用的用户账户为第三方支付账户,该业务请求为从第三方支付账户中支出大量金额的货币(已超过第三方支付账户设置的穿戴电子设备的支付额度权限时)时,穿戴电子设备通过与第三方电子设备(即终端)进行连接,检测该穿戴电子设备内第三方支付账户的信息安全,确认支付环境安全时,获取该第三方账户的验证码。
第二种操作行为:穿戴电子设备确定业务使用请求中涉及的业务类型超过用户账户的使用权限时,该穿戴电子设备确定该业务使用请求中涉及的业务类型超过用户账户的使用权限时,该穿戴电子设备确定通过通信连接方式中的任何一种方式与绑定的第三方电子设备存在通信连接后,确定执行后续操作,即获取该用户账户对应的验证码。
例如,穿戴电子设备基于业务使用请求调用的用户账户为第三方支付账户,该业务请求为从第三方支付账户中支出大量金额的货币(已超过第三方支付账户设置的穿戴电子设备的支付额度权限时)时,穿戴电子设备通过与第三方电子设备(即终端)进行连接,确定通与绑定的第三方电子设备存在通信连接后,获取该第三方账户的验证码。
这样,能够在业务使用请求中涉及的业务类型超过用户账户的使用权限时完成该业务,提高业务的安全性、可靠性。
步骤102:穿戴电子设备呈现上述验证码。
具体的穿戴电子设备呈现上述验证码,具体过程为:若业务使用请求的业务类型为对应用户账户的支出请求时,该穿戴电子设备呈现条形码;若业务使用请求的业务类型为对应用户账户的收取请求时,该穿戴电子设备呈现二维码。
进一步的,验证码可以是条形码,也可以是二维码,针对同一个用户账户生成验证码时,根据不同的业务类型不局限于一种验证码,例如针对同一个第三方支付账户,可以同时生成条形码和二维码,其中,条形码用于支付,二维码用于收款。
具体的,穿戴电子设备呈现上述验证码,可以采用以下两种方式:
第一种方式为:穿戴电子设备将上述验证码呈现在屏幕中。
第二种方式为:穿戴电子设备将所述验证码通过设定方式发送至业务使用装置。
需要说明的是,该穿戴电子设备在调用对应用户账户设置的用户验证信息生成验证码或者通过其他方式获取到用户账户的验证码后,需要将该验证码呈现至业务使用装置,例如商场中的POS机,这里的呈现可以是直接在该穿戴电子设备的屏幕中呈现也可以在有蓝牙连接的情况下,传输至业务使用装置,这样能够进一步提高业务的安全性。
进一步的,穿戴电子设备呈现验证码之后,该穿戴电子设备令业务使用装置基于该验证码通过安全验证后,触发相应的业务流程;该穿戴电子设备在确认该业务流程执行完毕后,获取用户账户与上述业务请求相关的关键信息,并进行呈现。
下面以具体的应用场景来说明上述方法。
某一穿戴电子设备假如为手表,在该手表第一次与终端连接时获取用户账户的属性信息,手表与终端的具体连接方式可以为蓝牙连接,在该手表支持无线连接情况下可以为WIFI连接也可以为无线网卡连接或者为非接触式射频识别连接,不局限于一种连接方式,这里设置三种业务类型的用户账户,包括第三方支付账户、学生账户、某一居民的身份证账户,获取支付名为“AAA”的第三方支付账
户的属性信息,获取姓名为“小明”的学生账户的属性信息,获取姓名为“小明”的身份证账户信息,与这三个用户账户进行关联设置。
进一步的,设置用于显示验证码的各种显示界面的调出方式,例如设置第三方支付账户的支付显示界面、学生账户的学生信息显示界面和身份证账户的身份信息显示界面的调出方式,不同类型的用户账户的显示界面的调出方式支持系统的自定义设置,例如,设置操作行为“翻转手腕”调出支付显示界面,设置语音“学生”调出学生信息显示界面,设置操作行为“轻敲屏幕”调出身份信息显示界面;这种验证码的显示界面的调出方式不唯一,只要保证不同调出方式能够区别不同业务类型用户账户的显示界面调出即可自行设置,例如设置语音“支付”调出支付显示界面,设置语音“学生”调出学生信息显示界面,设置语音“身份证”调出身份信息显示界面为例进行说明。
例如,某用户携带该手表在超市购物需要付款时,若此时需支付金额为33.5元小于第三方支付账户的最大额度,假设最大额度为100000元,该手表接收到用户语音包含“支付”时,该手表调用第三方支付账户的属性信息生成包含验证码的支付显示界面,这里的验证码可以为条形码或二维码,针对第三方支付账户在支付显示界面的顶部生成条形码用于支付,在支付显示界面的底部生成二维码用于收款,较佳的,可以设置条形码占用支付显示界面的1/3,二维码占用支付显示界面的2/3,具体效果参阅图2所示,支付显示界面在该手表上显示后,令商场的POS机扫描支付显示界面的条形码,完成支付。需要说明的是,该用户在支付过程中,该手表不需要与终端时刻保持连接,且支付简单,安全性高。进一步的,在支付完成后,该手表与终端连接成功后,该手表能够获取该第三支付账户有关此次业务交易的关键信息,例如,获取付款金额,付款明细等,具体效果可参阅图3所示。
例如,某学生携带该手表需要在图书馆阅览图书时,此时需要经过学生身份的安全检查才能进入图书馆,该手表接收到用户语音包含“学生”时,该手表调用学生账户的属性信息生成包含验证码的学生信息显示界面,这里的验证码可以为条形码或二维码,假设为条形码,针对学生账户在学生信息显示界面上生成条
形码,在学生信息显示界面在该手表上显示后,令安检装置扫描该学生信息显示界面上的条形码,完成身份验证。需要说明的是,该学生在安检过程中,该手表不需要与终端时刻保持连接,且操作简单,安全性高。
例如,某用户张某携带该手表去某一旅游景点观光时,若此时需凭借身份证才能购买此景点的门票,此时张某为了安全考虑游玩时没有携带身份证,该手表接收到用户语音包含“身份证”时,该手表调用张某身份账户的属性信息生成包含验证码的身份信息显示界面,这里的验证码可以为条形码或二维码,假设为条形码,针对张某身份证账户在身份信息显示界面上生成条形码,在身份信息显示界面在该手表上显示后,令安身份证验证装置扫描该身份信息显示界面上的条形码,完成身份验证。
基于上述技术方案,参阅图4所示,本发明实施例提供一种业务管理装置,
包括:接收单元40,生成单元41和处理单元42,其中:
接收单元40,用于接收业务使用请求。
生成单元41,用于基于业务使用请求确定对应的用户账户,并获取该用户账户对应的验证码,其中,该验证码是基于该用户账户的用户验证信息生成的;
处理单元42,用于呈现该验证码。
这样,能够大大减少业务流程,提高业务完成效率的基础上进一步还能保证业务的安全性,提升用户的体验效果。
可选的,在接收业务使用请求之前,接收单元40进一步用于:
通过通信连接方式中的任何一种方式,从用户信息管理系统获取该用户账户的属性信息,并基于该属性信息在本地与该用户账户建立关联。
可选的,接收业务使用请求时,接收单元40具体用于:
接收用户发出的语音,并将该语音与预设的语音样本进行关键字匹配或声纹匹配,在确定匹配成功时,判定接收到业务使用请求;或者,
接收用户输入的指纹,并在确定该指纹与预设的账户调出指纹模本匹配成功时,确定接收到业务使用请求;或者,
接收用户输入的操作行为,并在确定该操作行为与预设的账户调用行为匹配
成功,确定接收到业务使用请求。
可选的,基于该业务使用请求确定对应的用户账户时,该生成单元41具体用于:
接收到业务使用请求之后,基于该业务使用请求,确定该业务使用请求的业务类型,基于该业务类型确定对应的用户账户。
可选的,基于该业务使用请求确定对应的用户账户之后,获取该用户账户对应的验证码之前,生成单元41进一步用于:
确定该业务使用请求中涉及的业务类型超过用户账户的使用权限时,该穿戴电子设备通过该通信连接方式中的任何一种方式与第三方电子设备进行连接;
将该用户账户的属性信息及该业务使用请求发送到第三方电子设备进行校验,并接收该第三方电子设备反馈的检验结果;
基于该检验结果确定校验成功时,确定执行后续操作。
可选的,基于业务使用请求确定对应的用户账户之后,获取该用户账户对应的验证码之前,生成单元41进一步用于:
确定该业务使用请求中涉及的业务类型超过用户账户的使用权限时,该穿戴电子设备确定通过通信连接方式中的任何一种方式与绑定的第三方电子设备存在通信连接后,确定执行后续操作。
这样,能够在业务使用请求中涉及的业务类型超过用户账户的使用权限时继续完成该业务,提高业务的安全性、可靠性。
可选的,呈现该验证码时,处理单元42具体用于:
若该业务使用请求的业务类型为该用户账户的支出请求时,呈现条形码;
若该业务使用请求的业务类型为该用户账户的收取请求时,呈现二维码。
可选的,呈现验证码时,处理单元42具体用于:
将该验证码呈现在屏幕中,或者,将该验证码通过设定方式发送至该业务使用装置。
可选的,呈现验证码之后,处理单元42进一步用于:
令业务使用装置基于该验证码通过安全验证后,触发相应的业务流程;
在确认该业务流程执行完毕后,获取用户账户与该业务请求相关的关键信息,并进行呈现。
可选的,接收单元40采用的该通信连接方式至少包括蓝牙连接,WIFI连接,无线网卡连接和非接触式射频识别连接。
综上该,本申请实施中,穿戴电子设备接收业务使用请求;基于该业务使用请求确定对应的用户账户,并获取该用户账户对应的验证码,其中,该验证码是基于该用户账户的用户验证信息生成的;最后该穿戴电子设备呈现该验证码,这样,能够大大减少业务流程,提高业务完成效率的基础上进一步还能保证业务的安全性,提升用户的体验效果。
本领域内的技术人员应明白,本申请的实施例可提供为方法、系统、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从
而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例,但本领域内的技术人员一旦得知了基本创造性概念,则可对这些实施例作出另外的变更和修改。所以,所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然,本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样,倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。
Claims (20)
- 一种业务管理方法,其特征在于,包括:穿戴电子设备接收业务使用请求;所述穿戴电子设备基于所述业务使用请求确定对应的用户账户,并获取所述用户账户对应的验证码,其中,所述验证码是基于所述用户账户的用户验证信息生成的;所述穿戴电子设备呈现所述验证码。
- 如权利要求1所述的方法,其特征在于,穿戴电子设备在接收业务使用请求之前,进一步包括:穿戴电子设备通过通信连接方式中的任何一种方式,从用户信息管理系统获取所述用户账户的属性信息,并基于所述属性信息在本地与所述用户账户建立关联。
- 如权利要求1所述的方法,其特征在于,穿戴电子设备接收业务使用请求,具体包括:穿戴电子设备接收用户发出的语音,并将所述语音与预设的语音样本进行关键字匹配或声纹匹配,在确定匹配成功时,判定接收到业务使用请求;或者,穿戴电子设备接收用户输入的指纹,并在确定所述指纹与预设的账户调出指纹模本匹配成功时,确定接收到业务使用请求;或者,穿戴电子设备接收用户输入的操作行为,并在确定所述操作行为与预设的账户调用行为匹配成功,确定接收到业务使用请求。
- 如权利要求1所述的方法,其特征在于,所述穿戴电子设备基于所述业务使用请求确定对应的用户账户,包括:穿戴电子设备接收到业务使用请求之后,基于所述业务使用请求,确定所述业务使用请求的业务类型,基于所述业务类型确定对应的用户账户。
- 如权利要求1所述的方法,其特征在于,所述穿戴电子设备基于所述业务使用请求确定对应的用户账户之后,获取所述用户账户对应的验证码之前,进一 步包括:所述穿戴电子设备确定所述业务使用请求中涉及的业务类型超过用户账户的使用权限时,所述穿戴电子设备通过所述通信连接方式中的任何一种方式与第三方电子设备进行连接;所述穿戴电子设备将所述用户账户的属性信息及所述业务使用请求发送到第三方电子设备进行校验,并接收所述第三方电子设备反馈的检验结果;所述穿戴电子设备基于所述检验结果确定校验成功时,确定执行后续操作。
- 如权利要求1所述的方法,其特征在于,所述穿戴电子设备基于所述业务使用请求确定对应的用户账户之后,获取所述用户账户对应的验证码之前,进一步包括:所述穿戴电子设备确定所述业务使用请求中涉及的业务类型超过用户账户的使用权限时,所述穿戴电子设备确定通过通信连接方式中的任何一种方式与绑定的第三方电子设备存在通信连接后,确定执行后续操作。
- 如权利要求1-6任一项所述的方法,其特征在于,所述穿戴电子设备呈现所述验证码,具体包括:若所述业务使用请求的业务类型为所述用户账户的支出请求时,所述穿戴电子设备呈现条形码;若所述业务使用请求的业务类型为所述用户账户的收取请求时,所述穿戴电子设备呈现二维码。
- 如权利要求7所述的方法,其特征在于,所述穿戴电子设备呈现所述验证码,具体包括:所述穿戴电子设备将所述验证码呈现在屏幕中,或者,将所述验证码通过设定方式发送至所述业务使用装置。
- 如权利要求8所述的方法,其特征在于,所述穿戴电子设备呈现所述验证码之后,进一步包括:所述穿戴电子设备令业务使用装置基于所述验证码通过安全验证后,触发相应的业务流程;所述穿戴电子设备在确认所述业务流程执行完毕后,获取用户账户与所述业务请求相关的关键信息,并进行呈现。
- 如权利要求2、5或6所述的方法,且特征在于,所述通信连接方式至少包括蓝牙连接,WIFI连接,无线网卡连接和非接触式射频识别连接。
- 一种业务管理装置,其特征在于,包括:接收单元,用于接收业务使用请求;生成单元,用于基于所述业务使用请求确定对应的用户账户,并获取所述用户账户对应的验证码,其中,所述验证码是基于所述用户账户的用户验证信息生成的;处理单元,用于呈现所述验证码。
- 如权利要求11所述的装置,其特征在于,在接收业务使用请求之前,所述接收单元进一步用于:通过通信连接方式中的任何一种方式,从用户信息管理系统获取所述用户账户的属性信息,并基于所述属性信息在本地与所述用户账户建立关联。
- 如权利要求11所述的装置,其特征在于,接收业务使用请求时,所述接收单元具体用于:接收用户发出的语音,并将所述语音与预设的语音样本进行关键字匹配或声纹匹配,在确定匹配成功时,判定接收到业务使用请求;或者,接收用户输入的指纹,并在确定所述指纹与预设的账户调出指纹模本匹配成功时,确定接收到业务使用请求;或者,接收用户输入的操作行为,并在确定所述操作行为与预设的账户调用行为匹配成功,确定接收到业务使用请求。
- 如权利要求11所述的装置,其特征在于,基于所述业务使用请求确定对应的用户账户时,所述生成单元具体用于:接收到业务使用请求之后,基于所述业务使用请求,确定所述业务使用请求的业务类型,基于所述业务类型确定对应的用户账户。
- 如权利要求11所述的装置,其特征在于,基于所述业务使用请求确定对 应的用户账户之后,获取所述用户账户对应的验证码之前,所述生成单元进一步用于:确定所述业务使用请求中涉及的业务类型超过用户账户的使用权限时,所述穿戴电子设备通过所述通信连接方式中的任何一种方式与第三方电子设备进行连接;将所述用户账户的属性信息及所述业务使用请求发送到第三方电子设备进行校验,并接收所述第三方电子设备反馈的检验结果;基于所述检验结果确定校验成功时,确定执行后续操作。
- 如权利要求11所述的装置,其特征在于,基于所述业务使用请求确定对应的用户账户之后,获取所述用户账户对应的验证码之前,所述生成单元进一步用于:确定所述业务使用请求中涉及的业务类型超过用户账户的使用权限时,所述穿戴电子设备确定通过通信连接方式中的任何一种方式与绑定的第三方电子设备存在通信连接后,确定执行后续操作。
- 如权利要求11-16任一项所述的装置,其特征在于,呈现所述验证码时,所述处理单元具体用于:若所述业务使用请求的业务类型为所述用户账户的支出请求时,呈现条形码;若所述业务使用请求的业务类型为所述用户账户的收取请求时,呈现二维码。
- 如权利要求17所述的装置,其特征在于,呈现所述验证码时,所述处理单元具体用于:将所述验证码呈现在屏幕中,或者,将所述验证码通过设定方式发送至所述业务使用装置。
- 如权利要求18所述的装置,其特征在于,呈现所述验证码之后,所述处理单元进一步用于:令业务使用装置基于所述验证码通过安全验证后,触发相应的业务流程;在确认所述业务流程执行完毕后,获取用户账户与所述业务请求相关的关键信息,并进行呈现。
- 如权利要求12、15或16所述的装置,其特征在于,所述接收单元采用的所述通信连接方式至少包括蓝牙连接,WIFI连接,无线网卡连接和非接触式射频识别连接。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510085271.6A CN105989485B (zh) | 2015-02-16 | 2015-02-16 | 一种业务管理方法和装置 |
| CN201510085271.6 | 2015-02-16 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016131386A1 true WO2016131386A1 (zh) | 2016-08-25 |
Family
ID=56692152
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2016/073446 Ceased WO2016131386A1 (zh) | 2015-02-16 | 2016-02-04 | 一种业务管理方法和装置 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105989485B (zh) |
| WO (1) | WO2016131386A1 (zh) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108694578A (zh) * | 2018-08-02 | 2018-10-23 | 广东小天才科技有限公司 | 支付方法、支付装置、终端设备及计算机可读存储介质 |
| US10902233B2 (en) | 2016-12-08 | 2021-01-26 | Advanced New Technologies Co., Ltd. | Service processing using a digital object identifier |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108234695B (zh) * | 2017-12-28 | 2020-12-01 | 努比亚技术有限公司 | 一种支付操作方法、移动终端和计算机可读存储介质 |
| CN108335101A (zh) * | 2018-02-28 | 2018-07-27 | 深圳分云智能科技有限公司 | 一种基于智能手表的按键操作快捷支付的使用方法、系统 |
| CN108364179A (zh) * | 2018-02-28 | 2018-08-03 | 深圳分云智能科技有限公司 | 一种基于智能手表的麦克风操作快捷支付的使用方法、系统 |
| CN108416586A (zh) * | 2018-02-28 | 2018-08-17 | 深圳分云智能科技有限公司 | 基于智能手表的触摸屏操作快捷支付的使用方法、系统 |
| CN108335100A (zh) * | 2018-02-28 | 2018-07-27 | 深圳分云智能科技有限公司 | 基于智能手表的传感器振动检测快捷支付的使用方法、系统 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040225613A1 (en) * | 2003-05-05 | 2004-11-11 | International Business Machines Corporation | Portable intelligent shopping device |
| US20120030043A1 (en) * | 2010-07-29 | 2012-02-02 | Bank Of America Corporation | Wearable financial indicator |
| CN103927651A (zh) * | 2014-04-23 | 2014-07-16 | 百度在线网络技术(北京)有限公司 | 交易方法、系统以及服务器 |
| CN104331796A (zh) * | 2014-11-04 | 2015-02-04 | 北京握奇智能科技有限公司 | 一种可穿戴设备及其工作方法 |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2724297C (en) * | 2010-12-14 | 2013-11-12 | Xtreme Mobility Inc. | System and method for authenticating transactions through a mobile device |
| CN102546770B (zh) * | 2011-12-26 | 2015-05-27 | 中兴通讯股份有限公司 | 一种统一管理账户的方法及第三方账户管理系统 |
| CN103309618A (zh) * | 2013-07-02 | 2013-09-18 | 姜洪明 | 移动操作系统 |
| CN103955823A (zh) * | 2014-05-14 | 2014-07-30 | 金陵科技学院 | 一种高安全性便携式收付款方法 |
-
2015
- 2015-02-16 CN CN201510085271.6A patent/CN105989485B/zh active Active
-
2016
- 2016-02-04 WO PCT/CN2016/073446 patent/WO2016131386A1/zh not_active Ceased
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040225613A1 (en) * | 2003-05-05 | 2004-11-11 | International Business Machines Corporation | Portable intelligent shopping device |
| US20120030043A1 (en) * | 2010-07-29 | 2012-02-02 | Bank Of America Corporation | Wearable financial indicator |
| CN103927651A (zh) * | 2014-04-23 | 2014-07-16 | 百度在线网络技术(北京)有限公司 | 交易方法、系统以及服务器 |
| CN104331796A (zh) * | 2014-11-04 | 2015-02-04 | 北京握奇智能科技有限公司 | 一种可穿戴设备及其工作方法 |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10902233B2 (en) | 2016-12-08 | 2021-01-26 | Advanced New Technologies Co., Ltd. | Service processing using a digital object identifier |
| US10977464B2 (en) | 2016-12-08 | 2021-04-13 | Advanced New Technologies Co., Ltd. | Service processing using a digital object identifier |
| US10977465B2 (en) | 2016-12-08 | 2021-04-13 | Advanced New Technologies Co., Ltd. | Service processing using a digital object identifier |
| CN108694578A (zh) * | 2018-08-02 | 2018-10-23 | 广东小天才科技有限公司 | 支付方法、支付装置、终端设备及计算机可读存储介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105989485B (zh) | 2020-06-05 |
| CN105989485A (zh) | 2016-10-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2016131386A1 (zh) | 一种业务管理方法和装置 | |
| US10037082B2 (en) | Physical interaction dependent transactions | |
| US10861000B2 (en) | Method, system, and apparatus for application loading | |
| US9390442B2 (en) | Capturing of unique identifier in M-commerce transaction | |
| US20160275486A1 (en) | Device, system, and method for creating virtual credit card | |
| US20160132866A1 (en) | Device, system, and method for creating virtual credit card | |
| CN109754515B (zh) | 一种排队系统及排队的数据处理方法 | |
| US11113684B2 (en) | Device, system, and method for creating virtual credit card | |
| EP3543938A1 (en) | Authentication of a transaction card using a multimedia file | |
| WO2019047148A1 (zh) | 一种密码验证方法、终端、计算机可读存储介质 | |
| US20230083220A1 (en) | Provisioning of secure application | |
| EP3678081A1 (en) | Payment system, payment method, and program | |
| CN109426961B (zh) | 一种绑卡风险控制方法及装置 | |
| CN105354459A (zh) | 一种信息处理方法、装置及电子设备 | |
| US20170032353A1 (en) | Methods and systems for financial account access management | |
| CN113726943A (zh) | 控制方法及电子设备 | |
| CN106685945B (zh) | 业务请求处理方法、业务办理号码的验证方法及其终端 | |
| CN105468947A (zh) | 一种信息处理方法、装置及电子设备 | |
| CN106201153B (zh) | 一种操作入口展示方法及装置 | |
| CN106851613A (zh) | 业务请求方法、业务办理号码的验证方法及其终端 | |
| US11005882B1 (en) | Reputation-based transaction security | |
| HK1229499B (zh) | 一种业务管理方法和装置 | |
| CN113922967B (zh) | 区块链密钥的管理方法、装置及计算机设备 | |
| HK1229499A (zh) | 一種業務管理方法和裝置 | |
| HK1229499A1 (zh) | 一种业务管理方法和装置 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16751917 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 16751917 Country of ref document: EP Kind code of ref document: A1 |