WO2022156253A1 - 支付方法、网关设备、服务器及存储介质 - Google Patents

支付方法、网关设备、服务器及存储介质 Download PDF

Info

Publication number
WO2022156253A1
WO2022156253A1 PCT/CN2021/119364 CN2021119364W WO2022156253A1 WO 2022156253 A1 WO2022156253 A1 WO 2022156253A1 CN 2021119364 W CN2021119364 W CN 2021119364W WO 2022156253 A1 WO2022156253 A1 WO 2022156253A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
identification
payment
authorization
identification 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.)
Ceased
Application number
PCT/CN2021/119364
Other languages
English (en)
French (fr)
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.)
China Unionpay Co Ltd
Original Assignee
China Unionpay Co 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 China Unionpay Co Ltd filed Critical China Unionpay Co Ltd
Priority to US17/924,341 priority Critical patent/US20230186257A1/en
Publication of WO2022156253A1 publication Critical patent/WO2022156253A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102—Bill distribution or payments
    • 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/08—Payment architectures
    • G06Q20/085—Payment architectures involving remote charge determination or related payment systems
    • G06Q20/0855—Payment architectures involving remote charge determination or related payment systems involving a third party
    • 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/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G06Q20/027—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] involving a payment switch or gateway
    • 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/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing systems
    • G06Q20/145—Payments according to the detected use or quantity
    • 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/308—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using the Internet of Things
    • 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
    • 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

Definitions

  • the present application relates to the technical field of the Internet of Things, and in particular, to a payment method, a gateway device, a server and a storage medium.
  • the traditional payment solution is usually to bind the payment account to the gateway device, and use the gateway device to uniformly process the payment tasks of all IoT devices connected to the gateway.
  • any device connected to the gateway device can make payment.
  • the traditional payment scheme is prone to the problem of malicious access to the device for stealing, and the security is not high.
  • the embodiments of the present application provide a payment method, a gateway device, a server, and a storage medium, which can realize deduction from a target payment account in which the target identification information of the target Internet of Things device and the second device identification of the gateway device are simultaneously associated, thereby improving the Payment security.
  • an embodiment of the present application provides a payment method, which is applied to a gateway device, including:
  • target identification information includes the first device identification of the target IoT device and/or the characteristics of the physical layer between the target IoT device and the gateway device identification;
  • the server Send a first payment request to the server, wherein the first payment request includes the target identification information, the second device identification of the gateway device and the payment amount, and the first payment request is used to instruct the server to query the target identification information and the second device identification.
  • Target payment account and debit the target payment account according to the payment amount.
  • an embodiment of the present application provides a payment method, which is applied to a server, including:
  • the gateway device Receive a first payment request sent by the gateway device, where the first payment request includes target identification information and payment amount of the target IoT device, and a second device identification of the gateway device, where the target identification information includes the first device of the target IoT device Identification and/or feature identification of the physical layer between the target IoT device and the gateway device;
  • the payment is debited from the target payment account according to the payment amount.
  • an embodiment of the present application provides a gateway device, where the gateway device includes:
  • an acquisition module configured to acquire the target identification information and payment amount of the target IoT device connected to the gateway device, wherein the target identification information includes the first device identification of the target IoT device and/or the relationship between the target IoT device and the gateway device The characteristic identification of the physical layer;
  • the sending module is configured to send a first payment request to the server, wherein the first payment request includes the target identification information, the second device identification of the gateway device and the payment amount, and the first payment request is used to instruct the server to inquire about the target identification information and the first payment amount.
  • the second device identifies the associated target payment account, and debits the target payment account according to the payment amount.
  • an embodiment of the present application provides a server, where the server includes:
  • a receiving module configured to receive a first payment request sent by the gateway device, wherein the first payment request includes target identification information and payment amount of the target Internet of Things device, and a second device identification of the gateway device, and the target identification information includes the target Internet of Things device
  • a query module for querying the target payment account associated with the target identification information and the second device identification
  • the deduction module is used to debit the target payment account according to the payment amount.
  • an embodiment of the present application provides a payment device, the device comprising: a processor and a memory storing computer program instructions; the processor implements the payment method described in the first aspect when the processor executes the computer program instructions, or the processor The payment method of the second aspect is implemented when the computer program instructions are executed.
  • embodiments of the present application provide a computer-readable storage medium, where computer program instructions are stored on the computer-readable storage medium, and when the computer program instructions are executed by a processor, the payment method described in the first aspect is implemented, or a computer The program instructions implement the payment method of the second aspect when executed by the processor.
  • a payment method, a gateway device, a server, and a storage medium are provided in the embodiments of the present application.
  • the gateway device can obtain target identification information and payment amount of a target IoT device connected to the gateway device, wherein the target identification information includes the target IoT device.
  • the first device identifier and/or the feature identifier of the physical layer between the target IoT device and the gateway device.
  • a first payment request is sent to the server, wherein the first payment request includes target identification information, the second device identification of the gateway device and the payment amount.
  • the server queries the target payment account associated with the target identification information and the second device identification, and debits the target payment account according to the payment amount.
  • the target payment account in which the target identification information of the target Internet of Things device and the second device identification of the gateway device are simultaneously associated can be debited, thereby improving payment security.
  • different target IoT devices can be debited from different payment accounts.
  • 1 is a schematic diagram of the architecture of the payment system involved in the application
  • FIG. 2 is a schematic flowchart of an embodiment of a payment method involved in the present application
  • FIG. 3 is a schematic structural diagram of an embodiment of a gateway device involved in the present application.
  • FIG. 4 is a schematic structural diagram of an embodiment of a server involved in the present application.
  • FIG. 5 is a schematic structural diagram of an embodiment of a payment device involved in the present application.
  • the embodiments of the present application provide a payment method, a gateway device, a server, and a storage medium.
  • the gateway device can obtain target identification information and payment amount of the target IoT device connected to the gateway device, wherein the target identification information includes the first device identification of the target IoT device and/or the physical physical relationship between the target IoT device and the gateway device.
  • the feature identifier of the layer is sent to the server, wherein the first payment request includes target identification information, the second device identification of the gateway device and the payment amount.
  • the server queries the target payment account associated with the target identification information and the second device identification, and debits the target payment account according to the payment amount.
  • the target payment account in which the target identification information of the target Internet of Things device and the second device identification of the gateway device are simultaneously associated can be debited, thereby improving payment security.
  • different target IoT devices can be debited from different payment accounts.
  • the payment method can be applied to IoT scenarios such as smart homes, smart factories, or smart hospitals, which are not limited here.
  • FIG. 1 is a schematic structural diagram of a payment system involved in the present application.
  • the payment system may include an IoT device 110 , a gateway device 120 , an authorization device 130 and a server 140 .
  • the Internet of Things device 110 may be an Internet of Things device with payment requirements, such as a TV set-top box, a smart socket, or a webcam.
  • the gateway device 120 may be a gateway device that communicates with the public network, such as a router or a base station, and the base station may be a 4G or 5G base station.
  • the authorization device 130 may be a device to which a payment account has been bound, or a device to which an installed APP has been bound to a payment account, such as a mobile phone, a tablet computer, or a laptop computer, and so on.
  • Server 140 may be a high performance electronic computing device for storing and processing data.
  • the IoT device 110 and the gateway device 120, the gateway device 120 and the authorization device 130, and the server 140 can use Bluetooth, Ultra Wide Band (UWB), Universal Serial Bus (Universal Serial Bus, USB), serial , network cable, WiFi, or via other devices to communicate.
  • UWB Ultra Wide Band
  • USB Universal Serial Bus
  • the gateway device 120 may acquire target identification information and payment amount of the target IoT device.
  • the target IoT device is the IoT device 110 participating in the payment.
  • the target identification information includes the first device identification of the target IoT device and/or the feature identification of the physical layer between the target IoT device and the gateway device 120 .
  • a first payment request is sent to the server 140, wherein the first payment request includes the target identification information, the second device identification of the gateway device 120 and the payment amount.
  • the server 140 may query the target payment account associated with the target identification information and the second device identification, and debit the target payment account according to the payment amount.
  • the gateway device 120 may acquire the identification information of at least one IoT device 110 .
  • at least one IoT device 110 includes a target IoT device
  • the identification information includes a device identifier of the IoT device and/or a feature identifier of a physical layer between the IoT device and the gateway device.
  • a first authorization request is sent to the authorization device 130 .
  • the first authorization request includes identification information.
  • the authorization device 130 may generate an authorization identifier according to the identification information, and send the authorization identifier to the gateway device 120 .
  • the authorization identifier corresponds to the payment account of the authorization device 130 .
  • the gateway device 120 may send the second authorization request to the server 140 .
  • the second authorization request includes identification information, a second device identification and an authorization identification.
  • the server 140 associates and stores the identification information, the second device identification and the payment account corresponding to the authorization identification to realize payment authorization.
  • FIG. 2 is a schematic flowchart of an embodiment of a payment method involved in the present application. As shown in Figure 2, the payment method may include the following steps:
  • the gateway device acquires target identification information and payment amount of the target IoT device connected to the gateway device.
  • the target IoT device is an IoT device participating in payment, and the target identification information includes the first device identification of the target IoT device and/or the feature identification of the physical layer between the target IoT device and the gateway device.
  • the first device identifier may be preset when the target IoT device leaves the factory, or may be encrypted and pushed subsequently, and may uniquely represent the identity of the target IoT device.
  • the feature identifier of the physical layer between the target IoT device and the gateway device can uniquely represent the communication link between the target IoT device and the gateway device, is not easy to leak, and has high security.
  • the payment amount can be the charges incurred when the target IoT device is used, such as electricity charges incurred when the smart socket is used for a period of time.
  • the gateway device may receive a second payment request sent by the target Internet of Things device, where the second payment request includes target identification information and payment amount.
  • the target identification information includes the feature identification
  • the target IoT device may acquire the feature information of the physical layer between the target IoT device and the gateway device.
  • the feature information may include at least one of channel features, radio frequency fingerprints and radio frequency watermarks.
  • the feature identification is generated according to the feature information. Specifically, information conversion can be performed on the feature information to obtain the feature identifier.
  • a second payment request is sent to the gateway device, wherein the second payment request includes the feature identifier and the payment amount. In this way, the computing resources of the target Internet of Things device can be fully utilized to obtain the feature identifier, which is convenient for subsequent processing by the gateway device.
  • the gateway device may receive a third payment request sent by the target Internet of Things device. Wherein, the third payment request includes the payment amount.
  • the gateway device obtains characteristic information of the physical layer between the target IoT device and the gateway device. A feature identifier is generated according to the feature information. In this way, the computing resources of the gateway device can be fully utilized to obtain the feature identification, the computing pressure of the target IoT device can be reduced, the weight of the IoT device can be realized, and the equipment cost can be reduced.
  • the payment method may further include: S220, the gateway device sends a first payment request to the server.
  • the first payment request includes target identification information and payment amount, and the second device identification of the gateway device.
  • the second device identifier may be preset when the gateway device leaves the factory, or may be encrypted and pushed subsequently, and may uniquely represent the identity of the gateway device.
  • the payment method may further include: S230, the server queries the target payment account associated with the target identification information and the second device identification.
  • the server may receive the first payment request, and perform legality authentication, that is, identity authentication, on the second device identifier in the first payment request. In the case of passing the authentication, query the target payment account associated with the target identification information and the second device identification. In this way, the security of payment can be further improved.
  • the server may query the target association relationship between the target identification information and the second device identification from a preset registry, and the registry includes at least one association relationship.
  • the association relationship represents the association between the identification information of the IoT device, the second device identification of the gateway device and the payment account.
  • the target association relationship represents the association between the target identification information, the second device identification and the target payment account. Further, according to the target association relationship, the target payment account is determined.
  • the payment method may further include: S240, the server debits the target payment account according to the payment amount.
  • the server may deduct the payment amount from the target payment account, generate a transaction result, and then send the transaction result to the gateway device.
  • the gateway device receives the transaction result and sends the transaction result to the target IoT device.
  • the gateway device may acquire target identification information and payment amount of the target IoT device connected to the gateway device, where the target identification information includes the first device identification of the target IoT device and/or the target IoT device Characteristic identification of the physical layer with the gateway device. Then, a first payment request is sent to the server, wherein the first payment request includes target identification information, the second device identification of the gateway device and the payment amount. The server queries the target payment account associated with the target identification information and the second device identification, and debits the target payment account according to the payment amount. In this way, the target payment account in which the target identification information of the target Internet of Things device and the second device identification of the gateway device are simultaneously associated can be debited, thereby improving payment security. At the same time, it can also realize the deduction of different target IoT devices in different payment accounts, to meet the needs of different IoT devices in dormitory, shared apartment and other scenarios to deduct money from different payment accounts.
  • payment authorization can be performed by manually entering the card number or scanning the code across the screen.
  • the manual card number input method requires the user to memorize a lengthy card number, which leads to inconvenience; the cross-screen scanning method is not suitable for non-screen devices.
  • the gateway device may acquire identification information of at least one IoT device connected to the gateway device.
  • at least one IoT device includes a target IoT device
  • the identification information includes a device identification of the IoT device and/or a feature identification of the physical layer between the IoT device and the gateway device.
  • a first authorization request is then sent to the authorization device.
  • the first authorization request includes identification information.
  • the gateway device can obtain its identification information. Specifically, the gateway device may also receive the identification information sent by the target IoT device. Alternatively, when the identification information includes a feature identification, the gateway device may acquire feature information of the physical layer between the IoT device and the gateway device, and generate the feature identification according to the feature information. The specific details are similar to those of S210, and are not repeated here. Then, using the Trusted Execution Environment module (Trusted Execution Environment, TEE) or security chip in the IoT device, etc., the feature identifier is stored in the designated storage area in the gateway device.
  • TEE Trusted Execution Environment
  • the authorization device accesses the gateway device, a first authorization request is sent to the authorization device. Alternatively, an acquisition request sent by the authorization device is received, and a first authorization request is sent to the authorization device in response to the acquisition request.
  • the authorization device may receive the first authorization request, generate an authorization identifier according to the identification information in the first authorization request, and then send the authorization identifier to the gateway device, where the authorization identifier corresponds to the payment account of the authorization device.
  • the authorization device may display the identification information so that the user can view it, and the user may determine whether to authorize the IoT device corresponding to the identification information according to the identification information. If the user confirms the authorization, confirmation information may be input to the authorization device, for example, by clicking a target control in the display interface of the authorization device. In response to the confirmation information input by the user, the authorization device may generate an authorization identification and send the authorization identification to the gateway device. If the user denies authorization, denial information may be input to the authorization device, or the identification information may be ignored. At this point, the authorization device cannot generate an authorization identifier.
  • the gateway device may receive the authorization identifier and send the second authorization request to the server.
  • the second authorization request includes identification information, a second device identification and an authorization identification.
  • the server may receive the second authorization request, and associate and store the identification information, the second device identification and the payment account corresponding to the authorization identification.
  • the authorization device may perform legality authentication, that is, identity authentication, on the second device identifier and the authorization identifier.
  • legality authentication that is, identity authentication
  • the identification information, the second device identification and the payment account corresponding to the authorization identification are stored in association to realize payment authorization. In this way, the reliability of payment authorization can be further improved through legality authentication.
  • the server may associate the payment account corresponding to the identification information, the second device identification and the authorization identification to obtain the association relationship, store the association relationship in the association table under the file directory specified by the server, and send an authorization success notification to the gateway device.
  • the identification information of the IoT device and the second device identification of the gateway device can be associated with the payment account of the authorized device, so as to quickly realize payment authorization, reduce the time required for payment authorization, and avoid leakage of private information.
  • different target IoT devices can be associated with different payment accounts.
  • the gateway device may acquire identification information of at least one IoT device connected to the gateway device.
  • a third authorization request is then sent to the authorization device.
  • the third authorization request includes identification information and a second device identification.
  • the authorization device may receive the third authorization request, generate an authorization identifier according to the identification information in the third authorization request, and then send the fourth authorization request to the server.
  • the fourth authorization request includes identification information, a second device identification and an authorization identification.
  • the server may receive the fourth authorization request, and associate and store the identification information, the second device identification, and the payment account corresponding to the authorization identification.
  • the embodiment of the present application further provides a gateway device.
  • the gateway device 300 may include: an obtaining module 310 and a sending module 320 .
  • the obtaining module 310 is configured to obtain target identification information and payment amount of the target IoT device connected to the gateway device, wherein the target identification information includes the first device identification of the target IoT device and/or the target IoT device and the gateway device Characteristic identification of the physical layer in between.
  • the sending module 320 is configured to send the first payment request to the server.
  • the first payment request includes target identification information, the second device identification of the gateway device, and the payment amount, and the first payment request is used to instruct the server to query the target payment account associated with the target identification information and the second device identification, and pay according to the payment amount. Debit the target payment account.
  • the obtaining module 310 includes:
  • the first receiving unit is configured to receive a second payment request sent by the target Internet of Things device, wherein the second payment request includes target identification information and payment amount.
  • the obtaining module 310 includes:
  • a second receiving unit configured to receive a third payment request sent by the target Internet of Things device when the target identification information includes a feature identification, wherein the third payment request includes a payment amount;
  • an acquisition unit used to acquire feature information of the physical layer between the target Internet of Things device and the gateway device;
  • the generating unit is used for generating the feature identification according to the feature information.
  • the feature information includes at least one of channel features, radio frequency fingerprints, and radio frequency watermarks.
  • the obtaining module 310 is further configured to obtain the identification information of at least one IoT device connected to the gateway device before obtaining the target identification information and the payment amount of the target IoT device connected to the gateway device, wherein at least one An IoT device includes a target IoT device, and the identification information includes the device identification of the IoT device and/or the feature identification of the physical layer between the IoT device and the gateway device.
  • the sending module 320 may also be configured to send a first authorization request to the authorization device, wherein the first authorization request includes identification information, and the first authorization request is used to instruct the authorization device to generate an authorization identifier according to the identification information, and the authorization identifier corresponds to the payment account of the authorization device. .
  • the gateway device 300 may further include: a receiving module, configured to receive the authorization identifier sent by the authorization device.
  • the sending module 320 may also be configured to send a second authorization request to the server, wherein the second authorization request includes identification information, a second device identification and an authorization identification, and the second authorization request is used to instruct the server to send the identification information, the second device identification and the authorization identification. Identifies the associated storage of the corresponding payment account.
  • each module/unit in the gateway device 300 shown in FIG. 3 has the function of realizing each step performed by the gateway device in FIG. 2 and can achieve its corresponding technical effect. For brevity, it is not repeated here. .
  • the embodiment of the present application further provides a server.
  • the server 400 may include: a receiving module 410 , a query module 420 and a debiting module 430 .
  • the receiving module 410 is configured to receive the first payment request sent by the gateway device.
  • the first payment request includes the target identification information and payment amount of the target IoT device, and the second device identification of the gateway device
  • the target identification information includes the first device identification of the target IoT device and/or the target IoT device and the gateway. Characteristic identification of the physical layer between devices.
  • the query module 420 is configured to query the target payment account associated with the target identification information and the second device identification.
  • the debiting module 430 is used to debit the target payment account according to the payment amount.
  • query module 420 includes:
  • a first authentication unit configured to authenticate the legitimacy of the second device identifier
  • the query unit is configured to query the target payment account associated with the target identification information and the second device identification when the authentication is passed.
  • the receiving module 410 is further configured to receive a second authorization request sent by the gateway device before receiving the first payment request sent by the gateway device, wherein the second authorization request includes identification information of the IoT device, the second authorization request Device identification and authorization identification.
  • the identification information includes the device identification of the IoT device and/or the feature identification of the physical layer between the IoT device and the gateway device.
  • the authorization identification is generated by the authorized device according to the identification information. corresponding to the payment account.
  • the server 400 may further include: a storage module configured to associate and store the identification information, the second device identification and the payment account corresponding to the authorization identification.
  • the storage module includes:
  • a second authentication unit configured to perform legality authentication on the second device identifier and the authorization identifier
  • the storage unit is configured to associate and store the payment account corresponding to the identification information, the second device identification and the authorization identification when the authentication is passed.
  • each module/unit in the server 400 shown in FIG. 4 has the function of implementing each step performed by the server in FIG. 2 and can achieve its corresponding technical effect, which is not repeated here for brevity.
  • FIG. 5 is a schematic structural diagram of an embodiment of a payment device involved in the present application.
  • the payment device 500 in this embodiment includes an input device 501 , an input interface 502 , a central processing unit 503 , a memory 504 , an output interface 505 , and an output device 506 .
  • the input interface 502, the central processing unit 503, the memory 504, and the output interface 505 are connected to each other through the bus 510, and the input device 501 and the output device 506 are respectively connected to the bus 510 through the input interface 502 and the output interface 505, and then to the payment device 500. connections to other components.
  • the input device 501 receives input information from the outside, and transmits the input information to the central processing unit 503 through the input interface 502; the central processing unit 503 processes the input information based on the computer-executable instructions stored in the memory 504 to generate output information, temporarily or permanently store the output information in the memory 504, and then transmit the output information to the output device 506 through the output interface 505; the output device 506 outputs the output information to the outside of the payment device 500 for the user to use.
  • the payment device 500 shown in FIG. 5 includes: a memory 504 for storing a program; and a processor 503 for running the program stored in the memory to implement the payment method provided by the embodiment of the present application.
  • Embodiments of the present application further provide a computer-readable storage medium, where computer program instructions are stored thereon; when the computer program instructions are executed by a processor, the payment method provided by the embodiments of the present application is implemented.
  • Examples of computer-readable storage media include non-transitory computer-readable storage media, such as read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disk, or optical disk, and the like.
  • the functional blocks shown in the above-described structural block diagrams may be implemented as hardware, software, firmware, or a combination thereof.
  • it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), suitable firmware, a plug-in, a function card, and the like.
  • ASIC application specific integrated circuit
  • elements of the present application are programs or code segments used to perform the required tasks.
  • the program or code segments may be stored in a machine-readable medium or transmitted over a transmission medium or communication link by a data signal carried in a carrier wave.
  • a "machine-readable medium” may include any medium that can store or transmit information.
  • machine-readable media examples include electronic circuits, semiconductor memory devices, Read-Only Memory (ROM), flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (Radio Frequency, RF) link, etc.
  • the code segments may be downloaded via a computer network such as the Internet, an intranet, or the like.
  • processors may be, but are not limited to, general purpose processors, special purpose processors, application specific processors, or field programmable logic circuits. It will also be understood that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can also be implemented by special purpose hardware for performing the specified functions or actions, or by special purpose hardware and/or A combination of computer instructions is implemented.

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 Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computing Systems (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Telephonic Communication Services (AREA)
  • Computer And Data Communications (AREA)

Abstract

一种支付方法、网关设备、服务器及存储介质，该方法应用于网关设备，包括：获取与网关设备连接的目标物联网设备的目标标识信息和支付金额（S210），其中，目标标识信息包括目标物联网设备的第一设备标识和/或目标物联网设备与网关设备之间的物理层的特征标识；向服务器发送第一支付请求，其中，第一支付请求包括目标标识信息、网关设备的第二设备标识和支付金额（S220），第一支付请求用于指示服务器查询与目标标识信息和第二设备标识关联的目标支付账户，并根据支付金额在目标支付账户中进行扣款。

Description

支付方法、网关设备、服务器及存储介质
相关申请的交叉引用
本申请要求享有于2021年01月22日提交的名称为“支付方法、网关设备、服务器及存储介质”的中国专利申请202110091231.8的优先权，该申请的全部内容通过引用并入本文中。
技术领域
本申请涉及物联网技术领域，尤其涉及一种支付方法、网关设备、服务器及存储介质。
背景技术
随着物联网技术的快速发展，物联网设备的支付场景越来越常见。传统的支付方案通常是将支付账户与网关设备进行绑定，利用网关设备统一处理连接该网关所有物联网设备的支付任务。
但是，由于支付账户与网关设备具有强绑定关系，任何接入网关设备的设备都可以进行支付，传统的支付方案容易出现恶意接入设备进行盗刷的问题，安全性不高。
发明内容
本申请实施例提供了一种支付方法、网关设备、服务器及存储介质，可以实现在目标物联网设备的目标标识信息与网关设备的第二设备标识同时关联的目标支付账户中扣款，提高了支付安全性。
第一方面，本申请实施例提供一种支付方法，该方法应用于网关设备，包括：
获取与网关设备连接的目标物联网设备的目标标识信息和支付金额，其中，目标标识信息包括目标物联网设备的第一设备标识和/或目标物联网 设备与网关设备之间的物理层的特征标识；
向服务器发送第一支付请求，其中，第一支付请求包括目标标识信息、网关设备的第二设备标识和支付金额，第一支付请求用于指示服务器查询与目标标识信息和第二设备标识关联的目标支付账户，并根据支付金额在目标支付账户中进行扣款。
第二方面，本申请实施例提供一种支付方法，该方法应用于服务器，包括：
接收网关设备发送的第一支付请求，其中，第一支付请求包括目标物联网设备的目标标识信息和支付金额，以及网关设备的第二设备标识，目标标识信息包括目标物联网设备的第一设备标识和/或目标物联网设备与网关设备之间的物理层的特征标识；
查询与目标标识信息和第二设备标识关联的目标支付账户；
根据支付金额在目标支付账户中进行扣款。
第三方面，本申请实施例提供一种网关设备，该网关设备包括：
获取模块，用于获取与网关设备连接的目标物联网设备的目标标识信息和支付金额，其中，目标标识信息包括目标物联网设备的第一设备标识和/或目标物联网设备与网关设备之间的物理层的特征标识；
发送模块，用于向服务器发送第一支付请求，其中，第一支付请求包括目标标识信息、网关设备的第二设备标识和支付金额，第一支付请求用于指示服务器查询与目标标识信息和第二设备标识关联的目标支付账户，并根据支付金额在目标支付账户中进行扣款。
第四方面，本申请实施例提供一种服务器，该服务器包括：
接收模块，用于接收网关设备发送的第一支付请求，其中，第一支付请求包括目标物联网设备的目标标识信息和支付金额，以及网关设备的第二设备标识，目标标识信息包括目标物联网设备的第一设备标识和/或目标物联网设备与网关设备之间的物理层的特征标识；
查询模块，用于查询与目标标识信息和第二设备标识关联的目标支付账户；
扣款模块，用于根据支付金额在目标支付账户中进行扣款。
第五方面，本申请实施例提供一种支付设备，该设备包括：处理器以及存储有计算机程序指令的存储器；处理器执行计算机程序指令时实现第一方面所述的支付方法，或者，处理器执行计算机程序指令时实现第二方面所述的支付方法。
第六方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序指令，计算机程序指令被处理器执行时实现第一方面所述的支付方法，或者，计算机程序指令被处理器执行时实现第二方面所述的支付方法。
本申请实施例提供的一种支付方法、网关设备、服务器及存储介质，网关设备可以获取与网关设备连接的目标物联网设备的目标标识信息和支付金额，其中，目标标识信息包括目标物联网设备的第一设备标识和/或目标物联网设备与网关设备之间的物理层的特征标识。然后向服务器发送第一支付请求，其中，第一支付请求包括目标标识信息、网关设备的第二设备标识和支付金额。服务器查询与目标标识信息和第二设备标识关联的目标支付账户，并根据支付金额在目标支付账户中进行扣款。如此可以实现在目标物联网设备的目标标识信息与网关设备的第二设备标识同时关联的目标支付账户中扣款，提高了支付安全性。同时还可以实现不同的目标物联网设备在不同的支付账户中扣款。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对本申请实施例中所需要使用的附图作简单地介绍，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请涉及的支付系统的架构示意图；
图2是本申请涉及的支付方法的实施例的流程示意图；
图3是本申请涉及的网关设备的实施例的结构示意图；
图4是本申请涉及的服务器的实施例的结构示意图；
图5是本申请涉及的支付设备的实施例的结构示意图。
具体实施方式
下面将详细描述本申请的各个方面的特征和示例性实施例，为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细描述。应理解，此处所描述的具体实施例仅解释本申请，而不是限定本申请。对于本领域技术人员来说，本申请可以在不需要这些具体细节中的一些细节的情况下实施。下面对实施例的描述仅仅是为了通过示出本申请的示例来提供对本申请更好的理解。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
为了解决现有技术问题，本申请实施例提供了一种支付方法、网关设备、服务器及存储介质。网关设备可以获取与网关设备连接的目标物联网设备的目标标识信息和支付金额，其中，目标标识信息包括目标物联网设备的第一设备标识和/或目标物联网设备与网关设备之间的物理层的特征标识。然后向服务器发送第一支付请求，其中，第一支付请求包括目标标识信息、网关设备的第二设备标识和支付金额。服务器查询与目标标识信息和第二设备标识关联的目标支付账户，并根据支付金额在目标支付账户中进行扣款。如此可以实现在目标物联网设备的目标标识信息与网关设备的第二设备标识同时关联的目标支付账户中扣款，提高了支付安全性。同时还可以实现不同的目标物联网设备在不同的支付账户中扣款。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的支付方法、网关设备、服务器及存储介质进行详细地说明。
作为一个示例，该支付方法可以应用于例如智能家居、智能工厂、或 者智能医院等物联网场景，在此不做限制。
图1是本申请涉及的支付系统的架构示意图。如图1所示，该支付系统可以包括物联网设备110、网关设备120、授权设备130和服务器140。其中，物联网设备110可以是存在支付需求的物联网设备，例如电视机顶盒、智能插座或者网络摄像头等。网关设备120可以是与公网通信的网关设备，例如路由器或者基站等等，基站可以是4G或5G基站。授权设备130可以是已绑定支付账户的设备，也可以是安装的APP已经绑定支付账户的设备，例如手机、平板电脑或者笔记本电脑等等。服务器140可以是高性能的电子计算设备，用于存储和处理数据。可选地，物联网设备110与网关设备120、网关设备120与授权设备130和服务器140可以通过蓝牙、超宽带(Ultra Wide Band，UWB)、通用串行总线(Universal Serial Bus，USB)、串口、网线、WiFi或者经由其他设备转接等方式进行通信。
参见图1，在物联网设备110存在至少一个时，网关设备120可以获取目标物联网设备的目标标识信息和支付金额。其中，目标物联网设备是参与支付的物联网设备110。其中，目标标识信息包括目标物联网设备的第一设备标识和/或目标物联网设备与网关设备120之间的物理层的特征标识。然后向服务器140发送第一支付请求，其中，第一支付请求包括目标标识信息、网关设备120的第二设备标识和支付金额。服务器140可以查询与目标标识信息和第二设备标识关联的目标支付账户，并根据支付金额在目标支付账户中进行扣款。
示例性地，在获取目标物联网设备的目标标识信息和支付金额之前，网关设备120可以获取至少一个物联网设备110的标识信息。其中，至少一个物联网设备110包括目标物联网设备，标识信息包括物联网设备的设备标识和/或物联网设备与网关设备之间的物理层的特征标识。向授权设备130发送第一授权请求。其中，第一授权请求包括标识信息。授权设备130可以根据标识信息生成授权标识，并向网关设备120发送授权标识。其中，授权标识与授权设备130的支付账户对应。网关设备120可以向服务器140发送第二授权请求。其中，第二授权请求包括标识信息、第二设备 标识和授权标识。服务器140将标识信息、第二设备标识和授权标识对应的支付账户关联存储，实现支付授权。
下面将详细介绍本申请实施例提供的支付方法。其中，该支付方法可以应用于图1所示的支付系统。
图2是本申请涉及的支付方法的实施例的流程示意图。如图2所示，该支付方法可以包括以下步骤：
S210，网关设备获取与网关设备连接的目标物联网设备的目标标识信息和支付金额。
其中，目标物联网设备是参与支付的物联网设备，目标标识信息包括目标物联网设备的第一设备标识和/或目标物联网设备与网关设备之间的物理层的特征标识。可选地，第一设备标识可以是目标物联网设备出厂时预置的，也可以是后续加密推送的，可以唯一表示目标物联网设备的身份。目标物联网设备与网关设备之间的物理层的特征标识可以唯一表示目标物联网设备与网关设备之间的通信链路，不易泄露，安全性高。支付金额可以是目标物联网设备使用时产生的费用，例如智能插座使用一段时间产生的电费。
可选地，网关设备可以接收目标物联网设备发送的第二支付请求，其中，第二支付请求包括目标标识信息和支付金额。示例性地，在目标标识信息包括特征标识的情况下，目标物联网设备可以获取目标物联网设备与网关设备之间的物理层的特征信息。其中，特征信息可以包括信道特征、射频指纹和射频水印中至少一项。然后根据特征信息生成特征标识。具体地，可以对特征信息进行信息转换，得到特征标识。接着向网关设备发送第二支付请求，其中，第二支付请求包括特征标识与支付金额。如此可以充分利用目标物联网设备的计算资源获得特征标识，便于后续网关设备处理。
可选地，在目标标识信息包括特征标识的情况下，网关设备可以接收目标物联网设备发送的第三支付请求。其中，第三支付请求包括支付金额。响应于第三支付请求，网关设备获取目标物联网设备与网关设备之间的物理层的特征信息。根据特征信息生成特征标识。如此可以充分利用网 关设备的计算资源获得特征标识，减少目标物联网设备的计算压力，实现物联网设备的轻量化，降低设备成本。
如图2所示，该支付方法还可以包括：S220，网关设备向服务器发送第一支付请求。
其中，第一支付请求包括目标标识信息和支付金额、网关设备的第二设备标识。可选地，第二设备标识可以是网关设备出厂时预置的，也可以是后续加密推送的，可以唯一表示网关设备的身份。
如图2所示，该支付方法还可以包括：S230，服务器查询与目标标识信息和第二设备标识关联的目标支付账户。
具体地，服务器可以接收第一支付请求，对第一支付请求中的第二设备标识进行合法性认证即身份认证。在认证通过的情况下，查询与目标标识信息和第二设备标识关联的目标支付账户。如此可以进一步提高支付的安全性。
示例性地，服务器可以从预设的注册表中查询目标标识信息和第二设备标识对应的目标关联关系，注册表中包括至少一个关联关系。其中，关联关系表征物联网设备的标识信息、网关设备的第二设备标识和支付账户的关联。目标关联关系表征目标标识信息、第二设备标识和目标支付账户的关联。进而根据目标关联关系，确定目标支付账户。
如图2所示，该支付方法还可以包括：S240，服务器根据支付金额在目标支付账户中进行扣款。
具体地，服务器可以在目标支付账户中扣除支付金额，生成交易结果，然后向网关设备发送交易结果。网关设备接收交易结果，并向目标物联网设备发送交易结果。
在本申请实施例中，网关设备可以获取与网关设备连接的目标物联网设备的目标标识信息和支付金额，其中，目标标识信息包括目标物联网设备的第一设备标识和/或目标物联网设备与网关设备之间的物理层的特征标识。然后向服务器发送第一支付请求，其中，第一支付请求包括目标标识信息、网关设备的第二设备标识和支付金额。服务器查询与目标标识信息和第二设备标识关联的目标支付账户，并根据支付金额在目标支付账户中 进行扣款。如此可以实现在目标物联网设备的目标标识信息与网关设备的第二设备标识同时关联的目标支付账户中扣款，提高了支付安全性。同时还可以实现不同的目标物联网设备在不同的支付账户中扣款，满足宿舍、合租公寓等场景中出现的不同物联网设备在不同支付账户中扣款的需求。
目前可以通过手输卡号或跨屏扫码进行支付授权。其中，手输卡号方式需要用户记忆冗长的卡号，导致使用不便；跨屏扫码方式不适用于无屏设备。
因此在一个实施例中，在获取与网关设备连接的目标物联网设备的目标标识信息和支付金额之前，网关设备可以获取至少一个与网关设备连接的物联网设备的标识信息。其中，至少一个物联网设备包括目标物联网设备，标识信息包括物联网设备的设备标识和/或物联网设备与网关设备之间的物理层的特征标识。然后向授权设备发送第一授权请求。其中，第一授权请求包括标识信息。
示例性地，当物联网设备首次接入网关设备时，网关设备可以获取其标识信息。具体地，网关设备也可以接收目标物联网设备发送的标识信息。或者，在标识信息包括特征标识的情况下，网关设备可以获取物联网设备与网关设备之间的物理层的特征信息，根据特征信息生成特征标识。具体细节与S210类似，在此不做赘述。然后利用物联网设备中的可信执行环境模块(Trusted Execution Environment，TEE)或者安全芯片等等，将特征标识存储在网关设备中的指定存储区域。在授权设备接入网关设备时，向授权设备发送第一授权请求。或者，接收授权设备发送的获取请求，响应于该获取请求向授权设备发送第一授权请求。
授权设备可以接收第一授权请求，并根据第一授权请求中的标识信息生成授权标识，然后向网关设备发送授权标识，该授权标识与授权设备的支付账户对应。
示例性地，授权设备可以显示标识信息，以使用户进行查看，用户可以根据标识信息，确定是否为标识信息对应的物联网设备授权。若用户确定授权，则可以向授权设备输入确认信息，例如点击授权设备的显示界面中的目标控件。响应于用户输入的确认信息，授权设备可以生成授权标 识，并向网关设备发送授权标识。若用户拒绝授权，则可以向授权设备输入拒绝信息，或者忽略该标识信息。此时，授权设备不能生成授权标识。
网关设备可以接收授权标识，并向服务器发送第二授权请求。其中，第二授权请求包括标识信息、第二设备标识和授权标识。
服务器可以接收第二授权请求，将标识信息、第二设备标识和授权标识对应的支付账户关联存储。具体地，授权设备可以对第二设备标识和授权标识进行合法性认证即身份认证。在认证通过的情况下，将标识信息、第二设备标识和授权标识对应的支付账户关联存储，实现支付授权。如此可以通过合法性认证进一步提高支付授权的可靠性。
示例性地，服务器可以关联标识信息、第二设备标识和授权标识对应的支付账户，得到关联关系，将关联关系存储在服务器指定文件目录下的关联表中，并向网关设备发送授权成功通知。
如此可以将物联网设备的标识信息、网关设备的第二设备标识与授权设备的支付账户关联，快速实现支付授权，减少支付授权所需时间，避免私密信息的泄露。同时可以实现不同的目标物联网设备关联不同的支付账户。
可选地，在获取与网关设备连接的目标物联网设备的目标标识信息和支付金额之前，网关设备可以获取至少一个与网关设备连接的物联网设备的标识信息。然后向授权设备发送第三授权请求。其中，第三授权请求包括标识信息和第二设备标识。
授权设备可以接收第三授权请求，并根据第三授权请求中的标识信息生成授权标识，然后向服务器发送第四授权请求。其中，第四授权请求包括标识信息、第二设备标识和授权标识。
服务器可以接收第四授权请求，将标识信息、第二设备标识和授权标识对应的支付账户关联存储。
基于本申请实施例提供的支付方法，本申请实施例还提供了一种网关设备。如图3所示，网关设备300可以包括：获取模块310和发送模块320。
其中，获取模块310用于获取与网关设备连接的目标物联网设备的目 标标识信息和支付金额，其中，目标标识信息包括目标物联网设备的第一设备标识和/或目标物联网设备与网关设备之间的物理层的特征标识。
发送模块320用于向服务器发送第一支付请求。其中，第一支付请求包括目标标识信息、网关设备的第二设备标识和支付金额，第一支付请求用于指示服务器查询与目标标识信息和第二设备标识关联的目标支付账户，并根据支付金额在目标支付账户中进行扣款。
在一个实施例中，获取模块310包括：
第一接收单元，用于接收目标物联网设备发送的第二支付请求，其中，第二支付请求包括目标标识信息和支付金额。
在一个实施例中，获取模块310包括：
第二接收单元，用于在目标标识信息包括特征标识的情况下，接收目标物联网设备发送的第三支付请求，其中，第三支付请求包括支付金额；
获取单元，用于获取目标物联网设备与网关设备之间的物理层的特征信息；
生成单元，用于根据特征信息生成特征标识。
在一个实施例中，特征信息包括信道特征、射频指纹和射频水印中至少一项。
在一个实施例中，获取模块310还用于在获取与网关设备连接的目标物联网设备的目标标识信息和支付金额之前，获取至少一个与网关设备连接的物联网设备的标识信息，其中，至少一个物联网设备包括目标物联网设备，标识信息包括物联网设备的设备标识和/或物联网设备与网关设备之间的物理层的特征标识。
发送模块320还可用于向授权设备发送第一授权请求，其中，第一授权请求包括标识信息，第一授权请求用于指示授权设备根据标识信息生成授权标识，授权标识与授权设备的支付账户对应。
网关设备300还可包括：接收模块，用于接收授权设备发送的授权标识。
发送模块320还可用于向服务器发送第二授权请求，其中，第二授权请求包括标识信息、第二设备标识和授权标识，第二授权请求用于指示服 务器将标识信息、第二设备标识和授权标识对应的支付账户关联存储。
可以理解的是，图3所示网关设备300中的各个模块/单元具有实现图2中网关设备所执行的各个步骤的功能，并能达到其相应的技术效果，为简洁，在此不再赘述。
基于本申请实施例提供的支付方法，本申请实施例还提供了一种服务器。如图4所示，服务器400可以包括：接收模块410、查询模块420和扣款模块430。
其中，接收模块410用于接收网关设备发送的第一支付请求。其中，第一支付请求包括目标物联网设备的目标标识信息和支付金额，以及网关设备的第二设备标识，目标标识信息包括目标物联网设备的第一设备标识和/或目标物联网设备与网关设备之间的物理层的特征标识。
查询模块420用于查询与目标标识信息和第二设备标识关联的目标支付账户。
扣款模块430用于根据支付金额在目标支付账户中进行扣款。
在一个实施例中，查询模块420包括：
第一认证单元，用于对第二设备标识进行合法性认证；
查询单元，用于在认证通过的情况下，查询与目标标识信息和第二设备标识关联的目标支付账户。
在一个实施例中，接收模块410还用于在接收网关设备发送的第一支付请求之前，接收网关设备发送的第二授权请求，其中，第二授权请求包括物联网设备的标识信息、第二设备标识和授权标识，标识信息包括物联网设备的设备标识和/或物联网设备与网关设备之间的物理层的特征标识，授权标识是由授权设备根据标识信息生成，授权标识与授权设备的支付账户对应。
服务器400还可包括：存储模块，用于将标识信息、第二设备标识和授权标识对应的支付账户关联存储。
在一个实施例中，存储模块包括：
第二认证单元，用于对第二设备标识和授权标识进行合法性认证；
存储单元，用于在认证通过的情况下，将标识信息、第二设备标识和 授权标识对应的支付账户关联存储。
可以理解的是，图4所示服务器400中的各个模块/单元具有实现图2中服务器所执行的各个步骤的功能，并能达到其相应的技术效果，为简洁，在此不再赘述。
图5是本申请涉及的支付设备的实施例的结构示意图。
如图5所示，本实施例中的支付设备500包括输入设备501、输入接口502、中央处理器503、存储器504、输出接口505、以及输出设备506。其中，输入接口502、中央处理器503、存储器504、以及输出接口505通过总线510相互连接，输入设备501和输出设备506分别通过输入接口502和输出接口505与总线510连接，进而与支付设备500的其他组件连接。
具体地，输入设备501接收来自外部的输入信息，并通过输入接口502将输入信息传送到中央处理器503；中央处理器503基于存储器504中存储的计算机可执行指令对输入信息进行处理以生成输出信息，将输出信息临时或者永久地存储在存储器504中，然后通过输出接口505将输出信息传送到输出设备506；输出设备506将输出信息输出到支付设备500的外部供用户使用。
在一个实施例中，图5所示的支付设备500包括：存储器504，用于存储程序；处理器503，用于运行存储器中存储的程序，以实现本申请实施例提供的支付方法。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序指令；该计算机程序指令被处理器执行时实现本申请实施例提供的支付方法。计算机可读存储介质的示例包括非暂态计算机可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
需要明确的是，本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同或相似的部分互相参见即可，为了简洁，不再赘述。本申请并不局限于上文所描述并在图中示出的特定配置和处理。为了简明起见，这里省略了对已知方法的详细描述。在上述实施例中，描述和示出了若干具体的步骤作为示例。但是，本申请的方法过程并不限于所描述和示 出的具体步骤，本领域的技术人员可以在领会本申请的精神后，做出各种改变、修改和添加，或者改变步骤之间的顺序。
以上所述的结构框图中所示的功能块可以实现为硬件、软件、固件或者它们的组合。当以硬件方式实现时，其可以例如是电子电路、专用集成电路(Application Specific Integrated Circuit，ASIC)、适当的固件、插件、功能卡等等。当以软件方式实现时，本申请的元素是被用于执行所需任务的程序或者代码段。程序或者代码段可以存储在机器可读介质中，或者通过载波中携带的数据信号在传输介质或者通信链路上传送。“机器可读介质”可以包括能够存储或传输信息的任何介质。机器可读介质的例子包括电子电路、半导体存储器设备、只读存储器(Read-Only Memory，ROM)、闪存、可擦除ROM(EROM)、软盘、CD-ROM、光盘、硬盘、光纤介质、射频(Radio Frequency，RF)链路，等等。代码段可以经由诸如因特网、内联网等的计算机网络被下载。
还需要说明的是，本申请中提及的示例性实施例，基于一系列的步骤或者装置描述一些方法或系统。但是，本申请不局限于上述步骤的顺序，也就是说，可以按照实施例中提及的顺序执行步骤，也可以不同于实施例中的顺序，或者若干步骤同时执行。
上面参考根据本公开的实施例的方法、装置(系统)和计算机程序产品的流程图和/或框图描述了本公开的各方面。应当理解，流程图和/或框图中的每个方框以及流程图和/或框图中各方框的组合可以由计算机程序指令实现。这些计算机程序指令可被提供给通用计算机、专用计算机、或其它可编程数据处理装置的处理器，以产生一种机器，使得经由计算机或其它可编程数据处理装置的处理器执行的这些指令使能对流程图和/或框图的一个或多个方框中指定的功能/动作的实现。这种处理器可以是但不限于是通用处理器、专用处理器、特殊应用处理器或者现场可编程逻辑电路。还可理解，框图和/或流程图中的每个方框以及框图和/或流程图中的方框的组合，也可以由执行指定的功能或动作的专用硬件来实现，或可由专用硬件和计算机指令的组合来实现。
以上所述，仅为本申请的具体实施方式，所属领域的技术人员可以清 楚地了解到，为了描述的方便和简洁，上述描述的系统、模块和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。应理解，本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。

Claims (20)

  1. 一种支付方法，所述方法应用于网关设备，包括：
    获取与所述网关设备连接的目标物联网设备的目标标识信息和支付金额，其中，所述目标标识信息包括所述目标物联网设备的第一设备标识和/或所述目标物联网设备与所述网关设备之间的物理层的特征标识；
    向服务器发送第一支付请求，其中，所述第一支付请求包括所述目标标识信息、所述网关设备的第二设备标识和所述支付金额，所述第一支付请求用于指示所述服务器查询与所述目标标识信息和所述第二设备标识关联的目标支付账户，并根据所述支付金额在所述目标支付账户中进行扣款。
  2. 根据权利要求1所述的方法，其中，所述获取与所述网关设备连接的目标物联网设备的目标标识信息和支付金额，包括：
    接收所述目标物联网设备发送的第二支付请求，其中，所述第二支付请求包括所述目标标识信息和所述支付金额。
  3. 根据权利要求1所述的方法，其中，在所述目标标识信息包括所述特征标识的情况下，所述获取与所述网关设备连接的目标物联网设备的目标标识信息和支付金额，包括：
    接收所述目标物联网设备发送的第三支付请求，其中，所述第三支付请求包括所述支付金额；
    获取所述目标物联网设备与所述网关设备之间的物理层的特征信息；
    根据所述特征信息生成所述特征标识。
  4. 根据权利要求3所述的方法，其中，所述特征信息包括信道特征、射频指纹和射频水印中至少一项。
  5. 根据权利要求1-4任意一项所述的方法，其中，在所述获取与所述网关设备连接的目标物联网设备的目标标识信息和支付金额之前，所述方法还包括：
    获取至少一个与所述网关设备连接的物联网设备的标识信息，其中，至少一个物联网设备包括所述目标物联网设备，所述标识信息包括所述物 联网设备的设备标识和/或所述物联网设备与所述网关设备之间的物理层的特征标识；
    向授权设备发送第一授权请求，其中，所述第一授权请求包括所述标识信息，所述第一授权请求用于指示所述授权设备根据所述标识信息生成授权标识，所述授权标识与所述授权设备的支付账户对应；
    接收所述授权设备发送的所述授权标识；
    向所述服务器发送第二授权请求，其中，所述第二授权请求包括所述标识信息、所述第二设备标识和所述授权标识，所述第二授权请求用于指示所述服务器将所述标识信息、所述第二设备标识和所述授权标识对应的支付账户关联存储。
  6. 一种支付方法，所述方法应用于服务器，包括：
    接收网关设备发送的第一支付请求，其中，所述第一支付请求包括目标物联网设备的目标标识信息和支付金额，以及所述网关设备的第二设备标识，所述目标标识信息包括目标物联网设备的第一设备标识和/或所述目标物联网设备与所述网关设备之间的物理层的特征标识；
    查询与所述目标标识信息和所述第二设备标识关联的目标支付账户；
    根据所述支付金额在所述目标支付账户中进行扣款。
  7. 根据权利要求6所述的方法，其中，所述查询与所述目标标识信息和所述第二设备标识关联的目标支付账户，包括：
    对所述第二设备标识进行合法性认证；
    在认证通过的情况下，查询与所述目标标识信息和所述第二设备标识关联的目标支付账户。
  8. 根据权利要求6所述的方法，其中，在所述接收网关设备发送的第一支付请求之前，所述方法还包括：
    接收所述网关设备发送的第二授权请求，其中，所述第二授权请求包括物联网设备的标识信息、所述第二设备标识和授权标识，所述标识信息包括所述物联网设备的设备标识和/或所述物联网设备与所述网关设备之间的物理层的特征标识，所述授权标识是由授权设备根据所述标识信息生成，所述授权标识与所述授权设备的支付账户对应；
    将所述标识信息、所述第二设备标识和所述授权标识对应的支付账户关联存储。
  9. 根据权利要求8所述的方法，其中，所述将所述标识信息、所述第二设备标识和所述授权标识对应的目标支付账户关联存储，包括：
    对所述第二设备标识和所述授权标识进行合法性认证；
    在认证通过的情况下，将所述标识信息、所述第二设备标识和所述授权标识对应的支付账户关联存储。
  10. 一种网关设备，所述网关设备包括：
    获取模块，用于获取与所述网关设备连接的目标物联网设备的目标标识信息和支付金额，其中，所述目标标识信息包括所述目标物联网设备的第一设备标识和/或所述目标物联网设备与所述网关设备之间的物理层的特征标识；
    发送模块，用于向服务器发送第一支付请求，其中，所述第一支付请求包括所述目标标识信息、所述网关设备的第二设备标识和所述支付金额，所述第一支付请求用于指示所述服务器查询与所述目标标识信息和所述第二设备标识关联的目标支付账户，并根据所述支付金额在所述目标支付账户中进行扣款。
  11. 根据权利要求10所述的网关设备，其中，所述获取模块包括：
    第一接收单元，用于接收所述目标物联网设备发送的第二支付请求，其中，所述第二支付请求包括所述目标标识信息和所述支付金额。
  12. 根据权利要求10所述的网关设备，其中，所述获取模块包括：
    第二接收单元，用于在所述目标标识信息包括所述特征标识的情况下，接收所述目标物联网设备发送的第三支付请求，其中，所述第三支付请求包括所述支付金额；
    获取单元，用于获取所述目标物联网设备与所述网关设备之间的物理层的特征信息；
    生成单元，用于根据所述特征信息生成所述特征标识。
  13. 根据权利要求12所述的网关设备，其中，所述特征信息包括信道特征、射频指纹和射频水印中至少一项。
  14. 根据权利要求10-13任意一项所述的网关设备，其中，所述获取模块还用于在所述获取与所述网关设备连接的目标物联网设备的目标标识信息和支付金额之前，获取至少一个与所述网关设备连接的物联网设备的标识信息，其中，至少一个物联网设备包括所述目标物联网设备，所述标识信息包括所述物联网设备的设备标识和/或所述物联网设备与所述网关设备之间的物理层的特征标识；
    所述发送模块还用于向授权设备发送第一授权请求，其中，所述第一授权请求包括所述标识信息，所述第一授权请求用于指示所述授权设备根据所述标识信息生成授权标识，所述授权标识与所述授权设备的支付账户对应；
    所述网关设备还包括：接收模块，用于接收所述授权设备发送的所述授权标识；
    所述发送模块还用于向所述服务器发送第二授权请求，其中，所述第二授权请求包括所述标识信息、所述第二设备标识和所述授权标识，所述第二授权请求用于指示所述服务器将所述标识信息、所述第二设备标识和所述授权标识对应的支付账户关联存储。
  15. 一种服务器，包括：
    接收模块，用于接收网关设备发送的第一支付请求，其中，所述第一支付请求包括目标物联网设备的目标标识信息和支付金额，以及所述网关设备的第二设备标识，所述目标标识信息包括目标物联网设备的第一设备标识和/或所述目标物联网设备与所述网关设备之间的物理层的特征标识；
    查询模块，用于查询与所述目标标识信息和所述第二设备标识关联的目标支付账户；
    扣款模块，用于根据所述支付金额在所述目标支付账户中进行扣款。
  16. 根据权利要求15所述的服务器，其中，所述查询模块包括：
    第一认证单元，用于对所述第二设备标识进行合法性认证；
    查询单元，用于在认证通过的情况下，查询与所述目标标识信息和所述第二设备标识关联的目标支付账户。
  17. 根据权利要求15所述的服务器，其中，所述接收模块还用于在所 述接收网关设备发送的第一支付请求之前，接收所述网关设备发送的第二授权请求，其中，所述第二授权请求包括物联网设备的标识信息、所述第二设备标识和授权标识，所述标识信息包括所述物联网设备的设备标识和/或所述物联网设备与所述网关设备之间的物理层的特征标识，所述授权标识是由授权设备根据所述标识信息生成，所述授权标识与所述授权设备的支付账户对应；
    所述服务器还包括：存储模块，用于将所述标识信息、所述第二设备标识和所述授权标识对应的支付账户关联存储。
  18. 根据权利要求17所述的服务器，其中，所述存储模块包括：
    第二认证单元，用于对所述第二设备标识和所述授权标识进行合法性认证；
    存储单元，用于在认证通过的情况下，将所述标识信息、所述第二设备标识和所述授权标识对应的支付账户关联存储。
  19. 一种支付设备，包括：处理器以及存储有计算机程序指令的存储器；所述处理器执行所述计算机程序指令时实现如权利要求1-9任意一项所述的支付方法的步骤。
  20. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序指令，所述计算机程序指令被处理器执行时实现如权利要求1-9任意一项所述的支付方法的步骤。
PCT/CN2021/119364 2021-01-22 2021-09-18 支付方法、网关设备、服务器及存储介质 Ceased WO2022156253A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/924,341 US20230186257A1 (en) 2021-01-22 2021-09-18 Payment method, gateway device, server and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110091231.8A CN112819454B (zh) 2021-01-22 2021-01-22 支付方法、网关设备、服务器及存储介质
CN202110091231.8 2021-01-22

Publications (1)

Publication Number Publication Date
WO2022156253A1 true WO2022156253A1 (zh) 2022-07-28

Family

ID=75858992

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/119364 Ceased WO2022156253A1 (zh) 2021-01-22 2021-09-18 支付方法、网关设备、服务器及存储介质

Country Status (4)

Country Link
US (1) US20230186257A1 (zh)
CN (1) CN112819454B (zh)
TW (1) TWI789994B (zh)
WO (1) WO2022156253A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112819454B (zh) * 2021-01-22 2023-11-21 中国银联股份有限公司 支付方法、网关设备、服务器及存储介质
CN114463012B (zh) * 2022-01-26 2025-12-16 中国银联股份有限公司 认证方法、支付方法、装置及设备
CN115049378B (zh) * 2022-06-08 2024-10-15 支付宝(杭州)信息技术有限公司 一种业务执行方法、装置、设备和计算机可读介质
CN115392888A (zh) * 2022-09-26 2022-11-25 中国建设银行股份有限公司 一种支付方法、系统、装置、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106204025A (zh) * 2016-07-21 2016-12-07 广东欧珀移动通信有限公司 一种基于sim卡的支付方法和装置
WO2017091431A1 (en) * 2015-11-24 2017-06-01 Live Nation Entertainment, Inc. Short-range device communications for secured resource access
CN109087109A (zh) * 2018-08-17 2018-12-25 惠龙易通国际物流股份有限公司 一种移动支付确认方法、装置、系统和存储介质
CN111553667A (zh) * 2020-04-02 2020-08-18 中国银联股份有限公司 交易方法、网关设备、支付平台、商户设备和交易系统
CN111738729A (zh) * 2017-06-26 2020-10-02 创新先进技术有限公司 一种业务处理方法、设备及系统
CN112819454A (zh) * 2021-01-22 2021-05-18 中国银联股份有限公司 支付方法、网关设备、服务器及存储介质

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI502525B (zh) * 2012-04-17 2015-10-01 Taiwan Dev & Construction Co 電子標籤及用於確保電子標籤的認證系統與方法
US20160283933A1 (en) * 2015-03-25 2016-09-29 Fit Pay, Inc. Systems and methods for providing an internet of things payment platform (iotpp)
TWI647633B (zh) * 2017-01-26 2019-01-11 財金資訊股份有限公司 Method for inductive financial card payment by using mobile device
US10291714B2 (en) * 2017-07-13 2019-05-14 American Megatrends, Inc. System and method for using general software to control internet of things (IOT) system
US11551195B2 (en) * 2017-07-18 2023-01-10 Tata Consultancy Services Limited Systems and methods for providing services to smart devices connected in an IoT platform
CN110298652B (zh) * 2018-03-22 2023-09-29 中国银联股份有限公司 基于nfc标签的数据处理方法及其系统、服务器
CN108764919A (zh) * 2018-05-15 2018-11-06 惠龙易通国际物流股份有限公司 电子支付确认方法、装置、系统和存储介质
EP3672159A1 (en) * 2018-12-19 2020-06-24 Orange Internet of things connectivity device and method
EP3779826A1 (en) * 2019-08-16 2021-02-17 Mastercard International Incorporated Iot devices

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017091431A1 (en) * 2015-11-24 2017-06-01 Live Nation Entertainment, Inc. Short-range device communications for secured resource access
CN106204025A (zh) * 2016-07-21 2016-12-07 广东欧珀移动通信有限公司 一种基于sim卡的支付方法和装置
CN111738729A (zh) * 2017-06-26 2020-10-02 创新先进技术有限公司 一种业务处理方法、设备及系统
CN109087109A (zh) * 2018-08-17 2018-12-25 惠龙易通国际物流股份有限公司 一种移动支付确认方法、装置、系统和存储介质
CN111553667A (zh) * 2020-04-02 2020-08-18 中国银联股份有限公司 交易方法、网关设备、支付平台、商户设备和交易系统
CN112819454A (zh) * 2021-01-22 2021-05-18 中国银联股份有限公司 支付方法、网关设备、服务器及存储介质

Also Published As

Publication number Publication date
CN112819454A (zh) 2021-05-18
US20230186257A1 (en) 2023-06-15
TWI789994B (zh) 2023-01-11
CN112819454B (zh) 2023-11-21
TW202230243A (zh) 2022-08-01

Similar Documents

Publication Publication Date Title
US12323807B2 (en) Method for mutual recognition or mutual trust between bluetooth devices
WO2022156253A1 (zh) 支付方法、网关设备、服务器及存储介质
CN111639319B (zh) 用户资源授权方法、装置及计算机可读存储介质
CN108476223B (zh) 用于非sim设备的基于sim的认证的方法和装置
CN115915492B (zh) 分布式设备间的通信方法、系统及相关设备
US11475139B2 (en) System and method for providing secure data access
US20160328714A1 (en) Method and apparatus for authenticating payment related information in mobile communication system
CN105007274A (zh) 一种基于移动终端的身份认证系统和方法
KR101358346B1 (ko) 자동 로그인 방법 및 자동 로그인 시스템
JP2018517367A (ja) サービスプロバイダ証明書管理
US11832348B2 (en) Data downloading method, data management method, and terminal
CN114710524B (zh) 车内局域网的数据交互方法、装置、设备及存储介质
CN115065703B (zh) 物联网系统及其认证与通信方法、相关设备
CN110798836B (zh) eSIM卡终端设备切换方法和装置
CN115362700B (zh) 用于管理智能安全平台的事件的方法和装置
CN110022552A (zh) 用户身份识别模块数据写入方法、设备、平台及存储介质
CN114510178B (zh) 一种共享数据分发方法及电子设备
CN114040411A (zh) 一种设备绑定方法、装置、电子设备及存储介质
CN119856447A (zh) 接入令牌验证
CN114979170A (zh) 智能频谱共享系统、方法、装置、电子设备及存储介质
WO2019000421A1 (zh) 鉴权方法、鉴权设备和鉴权系统
CN117879814A (zh) 车钥匙分享方法、装置及存储介质
HK40050114A (zh) 支付方法、网关设备、服务器及存储介质
CN117097509A (zh) 一种授权登录方法及装置
HK40050114B (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: 21920631

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: 21920631

Country of ref document: EP

Kind code of ref document: A1