A service execution method, apparatus, device, and computer readable medium

Abstract

The embodiment of the specification discloses a business execution method, device, equipment and computer readable medium. The scheme can include: obtaining a first business request for an Internet of Things device; the first business request carries a device identifier of the Internet of Things device; sending a second business request to a second server; the second business request carries the device identifier of the Internet of Things device; the second business request is used to indicate the Internet of Things device to execute target business to obtain business execution result information, use the device identifier of the Internet of Things device to sign the business execution result information to obtain signature result information; receiving the business execution result information and the signature result information sent by the Internet of Things device; based on the signature result information and the business execution result information, requesting the second server to perform transaction settlement.

Description

[0001] This application is a divisional application of “A business execution method, apparatus, device and computer-readable medium (Application date: June 8, 2022, Application No.: 202210643565.6)”. Technical Field

[0002] This application relates to the field of computer technology, and in particular to a business execution method, apparatus, device, and computer-readable medium. Background Technology

[0003] In the field of IoT technology, third-party companies providing business support services sometimes initiate incentive policies such as rebates to increase user numbers or acquire user traffic. For example, they may encourage manufacturers of equipment, merchants using IoT devices, or users to use their services through rebates. Specifically, a rebate may be given to the operator of a particular device after it has been used a certain number of times. In existing technologies, the device operator typically provides data on how they received rebates for using the device. Therefore, it is sometimes difficult for the third-party companies providing business support services to verify whether the transactions corresponding to this service actually occurred on that particular device.

[0004] Therefore, how to provide a method that can ensure the actual execution of business operations has become a pressing technical problem that needs to be solved. Summary of the Invention

[0005] This specification provides a business execution method, apparatus, device, and computer-readable medium to provide a business execution method that can ensure the actual occurrence of business operations.

[0006] To solve the above-mentioned technical problems, the embodiments in this specification are implemented as follows:

[0007] This specification provides an embodiment of a business execution method, including:

[0008] Obtain a first service request for an IoT device; the first service request carries the device identifier of the IoT device.

[0009] A second service request is sent to a second server; the second service request carries the device identifier of the IoT device; the second service request is used to instruct the IoT device to execute a target service to obtain service execution result information, and to sign the service execution result information using the device identifier of the IoT device to obtain signature result information.

[0010] Receive the signature result information and the business execution result information sent by the IoT device;

[0011] Based on the business execution result information and the signature result information, a request is made to the second server to perform transaction settlement.

[0012] This specification provides an embodiment of a business execution device applied to a first server, comprising:

[0013] The first service request acquisition module is used to acquire a first service request for an IoT device; the first service request carries the device identifier of the IoT device.

[0014] The second service request sending module is used to send a second service request to a second server; the second service request carries the device identifier of the IoT device; the second service request is used to instruct the IoT device to execute a target service to obtain service execution result information, and to sign the service execution result information using the device identifier of the IoT device to obtain signature result information.

[0015] The information receiving module is used to receive the business execution result information and the signature result information sent by the IoT device;

[0016] The transaction settlement request module is used to request the second server to perform transaction settlement based on the business execution result information and the signature result information.

[0017] This specification also provides a business execution apparatus, applied to a second server, comprising:

[0018] The second service request receiving module is used to receive a second service request for an IoT device sent by the first server; the second service request carries the device identifier of the IoT device.

[0019] The service execution instruction information sending module is used to send service execution instruction information to the IoT device according to the device identifier; the service execution instruction information is used to instruct the IoT device to execute the target service to obtain service execution result information, and to sign the service execution result information using the device identifier of the IoT device to obtain signature result information;

[0020] A transaction settlement request receiving module is used to receive a transaction settlement request sent by the first server; the transaction settlement request carries the signature result information sent by the IoT device to the first server, and transaction data information generated based on the business execution result information sent by the IoT device to the first server;

[0021] The transaction settlement module is used to respond to the transaction settlement request and perform transaction settlement based on the signature result information and the transaction data information.

[0022] This specification also provides a business execution system, including a first server, a second server, and an Internet of Things (IoT) device. Specifically,

[0023] The first server is configured to obtain a first service request for an IoT device, wherein the first service request carries the device identifier of the IoT device; and send a second service request to the second server, wherein the second service request carries the device identifier of the IoT device.

[0024] The second server is configured to send service execution instruction information to the IoT device based on the device identifier;

[0025] The IoT device is configured to execute a target business based on the business execution instruction information to obtain business execution result information, sign the business execution result information using the device identifier of the IoT device to obtain signature result information, and send the business execution result information and the signature result information to the first server.

[0026] The first server is further configured to send a transaction settlement request to the second server based on the business execution result information and the signature result information; the transaction settlement request carries the signature result information and transaction data information generated based on the business execution result information;

[0027] The second server is also configured to respond to the transaction settlement request by performing transaction settlement based on the signature result information and the transaction data information.

[0028] This specification provides an embodiment of a business execution server, comprising:

[0029] At least one processor; and,

[0030] A memory communicatively connected to the at least one processor; wherein,

[0031] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0032] At least one processor; and,

[0033] A memory communicatively connected to the at least one processor; wherein,

[0034] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0035] Obtain a first service request for an IoT device; the first service request carries the device identifier of the IoT device.

[0036] A second service request is sent to a second server; the second service request carries the device identifier of the IoT device; the second service request is used to instruct the IoT device to execute a target service to obtain service execution result information, and to sign the service execution result information using the device identifier of the IoT device to obtain signature result information.

[0037] Receive the business execution result information and the signature result information sent by the IoT device;

[0038] Based on the business execution result information and the signature result information, a request is made to the second server to perform transaction settlement.

[0039] This specification also provides a service execution server, including:

[0040] At least one processor; and,

[0041] A memory communicatively connected to the at least one processor; wherein,

[0042] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0043] Receive a second service request for an IoT device sent by a first server; the second service request carries the device identifier of the IoT device;

[0044] Based on the device identifier, a service execution instruction information is sent to the IoT device; the service execution instruction information is used to instruct the IoT device to execute a target service to obtain service execution result information, and the service execution result information is signed using the device identifier of the IoT device to obtain signature result information;

[0045] The system receives a transaction settlement request sent by the first server; the transaction settlement request carries the signature result information sent by the IoT device to the first server, and transaction data information generated based on the business execution result information sent by the IoT device to the first server.

[0046] In response to the transaction settlement request, transaction settlement is performed based on the signature result information and the transaction data information.

[0047] This specification provides an embodiment of a computer-readable medium storing computer-readable instructions that can be executed by a processor to implement a business execution method.

[0048] One embodiment of this specification can achieve at least the following beneficial effects:

[0049] After receiving a first business request carrying the device identifier of an IoT device, the first server sends a second business request to the second server, instructing the IoT device to sign the business execution result information using its device identifier. Thus, the second server participates in the business initiation process for the IoT device. Based on the business initiation details, the second server can understand the association between the settlement transaction and the IoT device, and thereby determine whether the settlement transaction sent by the first server truly occurred on a specific IoT device. In practical applications, this makes it difficult for the first server to cheat by tampering with the binding relationship between the settlement transaction and the IoT device, significantly increasing the difficulty for the first server to falsify the authenticity of the business transaction. Attached Figure Description

[0050] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0051] Figure 1 This is a flowchart of a business execution method provided in an embodiment of this specification;

[0052] Figure 2 This is a flowchart of another business execution method provided in the embodiments of this specification;

[0053] Figure 3 This is a signaling interaction diagram of a service execution method provided in the embodiments of this specification;

[0054] Figure 4 This is a flowchart of a business execution method at the overall level provided in the embodiments of this specification;

[0055] Figure 5 The embodiments provided in this specification correspond to Figure 1 A schematic diagram of the structure of a business execution device;

[0056] Figure 6 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of a business execution device;

[0057] Figure 7 This is a schematic diagram of the structure of a business execution system provided in an embodiment of this specification;

[0058] Figure 8 The embodiments provided in this specification correspond to Figure 1 A schematic diagram of the structure of a business execution server;

[0059] Figure 9 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of a business execution server. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of them. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the protection scope of one or more embodiments of this specification.

[0061] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another.

[0062] The technical solutions provided in the various embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0063] In the field of IoT technology, third-party companies providing business support services, such as payment service providers, sometimes initiate incentive policies such as rebates to increase user volume or acquire user traffic. For example, they may encourage manufacturers of equipment, merchants using IoT devices, or users to use their services through rebates. Specifically, a rebate may be given to the operator of a particular device after it has been used a certain number of times. In existing technologies, the device operator typically provides data on the use of the device to earn rebates. Due to information asymmetry, the third-party company providing business support services may sometimes find it difficult to confirm whether a transaction actually occurred on a particular IoT device. For instance, the operator of the IoT devices, in managing and operating them, might use technical means to link transactions from devices with low transaction volumes to other devices that do not meet the rebate criteria, thus making those other devices eligible for rebates. Alternatively, they might use technical means to distribute transactions from devices with excessive transaction volumes to other devices that do not meet the rebate criteria, thereby making those other devices eligible for rebates. Both of these practices can cause financial losses to the third-party company providing business support services. Therefore, in the existing technology, third-party companies that provide business support services and offer rebate incentive policies cannot accurately confirm the relationship between transactions occurring on IoT devices and the IoT devices that actually execute these transactions.

[0064] To address the shortcomings of existing technologies, this solution provides the following embodiments:

[0065] Figure 1 This is a schematic diagram of the overall scheme flow of a business execution method in the embodiments of this specification. From the perspective of program execution, it can be applied to a server.

[0066] Next, a business execution method provided in the embodiments of the specification will be described in detail with reference to the accompanying drawings:

[0067] Figure 1 This is a flowchart illustrating a business execution method provided in an embodiment of this specification, applied to a first server.

[0068] like Figure 1 As shown, the process may include the following steps:

[0069] Step 102: Obtain a first service request for the IoT device; the first service request carries the device identifier of the IoT device.

[0070] In the embodiments of this specification, an Internet of Things (IoT) device can refer to a hardware device that is connected to a network and capable of transmitting data. For users, IoT devices can provide corresponding services, such as automatic water vending machines providing water services and automatic claw machines providing entertainment services. In practical applications, from a software perspective, a server may be needed to manage several IoT devices, such as controlling the on / off state of a particular IoT device or controlling the on / off time of a particular IoT device based on the amount paid by the user.

[0071] The first server can refer to the device's server, such as the server that operates and manages the IoT device. In this solution, since the IoT device can be managed through the first server, when a user requests the IoT device to provide a certain service, they need to send a business request to the first server that manages the IoT device in some way. In turn, the first server issues an activation command to the IoT device or performs services such as service time statistics.

[0072] Since IoT devices can be managed through a first server, a first business request can refer to a business request sent to the first server to request a certain business based on the IoT device, such as sending a water vending service request to the server that manages the automatic water vending equipment.

[0073] It should be noted that, in the embodiments of this application, the specific method by which the first server obtains the first service request is not limited. Depending on the scenario, the first server can obtain the first service request in different ways. For example, if an application corresponding to the service provided by the IoT device is installed on the user's client, the user can send the first service request to the first server through the client after launching the application.

[0074] Device identifiers can refer to symbolic identifiers used to distinguish different IoT devices. The specific form of the symbol is not specifically limited in this embodiment; it can be a string of numbers, a string of letters, a mixed string of numbers and letters, or even an image. In this embodiment, since the first server needs to know which specific IoT device needs to provide services to the user, the first service request needs to carry the device identifier of the IoT device.

[0075] Step 104: Send a second service request to the second server; the second service request carries the device identifier of the IoT device; the second service request is used to instruct the IoT device to execute the target service to obtain service execution result information, and to sign the service execution result information using the device identifier of the IoT device to obtain signature result information.

[0076] In the embodiments of this specification, the second server can refer to a server that provides business support for services provided to IoT devices, such as a server providing service fee deduction services. In practical applications, for example, the operator of the second server can provide various services to users based on its own business needs, such as travel services, payment services, etc. Since the services provided by this operator are deeply involved in the user's daily life, the user can open an account on the second server to pay for daily consumption expenses. In this embodiment, after receiving the first business request for the IoT device, the first server sends a second business request carrying the device identifier of the IoT device to the second server. This allows the second server to know the device identifier of the IoT device before the IoT device executes the target business corresponding to the first business request, thereby enabling the second server to be deeply involved in the business initiation process for the IoT device.

[0077] The second service request can refer to a request from the first server to the second server to issue a service request to the IoT device to execute the target service corresponding to the first service request. Upon receiving this service request, the IoT device can then specifically execute the target service and obtain the service execution result information. In this process, the second server essentially routes the first service request from step 102. To ensure accurate routing, the second service request must carry the device identifier of the IoT device corresponding to the first service request from step 102. This allows the second server to know which specific IoT device to send the service execution instruction information to, which to a certain extent ensures that it is indeed the IoT device corresponding to this device identifier that executes the target service corresponding to the first service request. During this process, the second server can also require the IoT device corresponding to this device identifier to sign the service execution result information using its device identifier and obtain a signature result information. In the subsequent transaction settlement stage, the second server can parse the device identifier from the signature result information and compare this device identifier with the device identifier involved in the instruction command issued to the IoT device corresponding to the second service request, thereby confirming whether the IoT device executing the target service matches the IoT device receiving the instruction command corresponding to the second service request.

[0078] There are several ways for IoT devices to sign business execution result information using their device identifier. One method is to embed an Internet of Things Software Development Kit (IOTSDK) developed by the operator of the second server into the IoT device. The IOTSDK then uses the device identifier to sign the business execution result information, obtaining a signature result. Since the IOTSDK is developed by the operator of the second server, the signature result obtained by it using the device identifier is trustworthy to the operator of the second server. Another possible method is for the IoT device to send a signature request to the second server via a trusted link. This signature request contains the IoT device's device identifier and the business execution result information. The second server then uses the device identifier to sign the business execution result information and sends the signature result information back to the IoT device.

[0079] The target business can include the business of providing goods or services through IoT devices. For example, for an IoT device such as an automatic water vending machine, the target business can include controlling the water control switch to supply water; for an IoT device such as an automatic claw machine, the target business can include controlling the claw machine handle to execute user operation commands; and for an IoT device such as a smart washing machine, the target business can include controlling the smart washing machine to perform washing operations.

[0080] In this context, business execution result information refers to the outcome information provided by the IoT device regarding the process or outcome of executing the target business, which can then be used to calculate related costs. The types of business execution result information can vary depending on the specific target business provided by different IoT devices. For example, for an automated water vending machine, the business execution result information may include the volume of water provided to the user; for an automated claw machine, the business execution result information may include the number of times the user attempts to grab a prize.

[0081] It should be noted that due to equipment failure or other reasons, IoT devices may not be able to specifically execute the target service corresponding to the first service request. In this case, the service execution result information may also include information on whether the execution of this target service was successful or failed. If the included message is a failure message, no transaction settlement will be performed on the user's account.

[0082] Step 106: Receive the business execution result information and the signature result information sent by the IoT device.

[0083] In the embodiments of this specification, after the IoT device receives a second service request from the second server to execute a target service, the IoT device can specifically execute the target service and thus provide the corresponding service to the user. After the service is completed, the IoT device will send the signature result information of its device identifier and the service execution result information to the first server, so that the first server can perform related services such as business data registration.

[0084] Step 108: Based on the business execution result information and the signature result information, request the second server to perform transaction settlement.

[0085] In the embodiments of this specification, after the IoT device sends the business execution result information and signature result information to the first server, the first server can perform corresponding fee calculations based on the business execution result information, and then request the second server to settle the transaction, that is, request the settlement of the service fee for the target business corresponding to the first business request.

[0086] It should be understood that in the methods described in one or more embodiments of this specification, the order of some steps may be adjusted according to actual needs, or some steps may be omitted.

[0087] Figure 1 The method described involves a first server receiving a first business request for an IoT device, carrying the device identifier of that IoT device. The first server then sends a second business request to the second server, instructing the IoT device to sign the business execution result information using its device identifier. This allows the second server to participate in the business initiation chain for the IoT device. By understanding the business initiation details, the second server can determine the association between the settlement transaction and the IoT device, and thus verify whether the settlement transaction sent by the first server actually occurred on a specific IoT device. In practical applications, this makes it difficult for the first server to cheat by tampering with the binding relationship between the settlement transaction and the IoT device, significantly increasing the difficulty for the first server to falsify the authenticity of the business transaction.

[0088] based on Figure 1 In addition to the method described herein, this specification also provides some specific implementation methods of this method, which will be described below.

[0089] Since there are different types of IoT devices, and different IoT devices have different use cases, this specification provides various methods in which the first server can obtain the first service request for the IoT device in step 202, which may include:

[0090] The system receives the first service request sent by an IoT device or user terminal in response to a user's request to use the IoT device. From the perspective of communication media, due to the diversity of IoT device types, the communication methods for initiating the first service request can be diverse, such as 4G, WIFI, Bluetooth, serial port, and other communication methods used for service communication.

[0091] More specific examples, such as Method 1

[0092] In this approach, the IoT device sends a first service request to the first server. This can be achieved by a user triggering a service request to the IoT device via forward scanning. Upon sensing this service request, the IoT device sends a corresponding first service request to the first server that manages it. For example, on an IoT device equipped with an identity scanning device, a user scans their identity credentials on the device. Forward scanning refers to the IoT device identifying the user's identity by scanning their identity credentials.

[0093] Method 2

[0094] In this method, the user terminal sends a first service request to the first server. An application corresponding to the services provided by the IoT device can be installed on the user terminal. After obtaining the device identifier of the IoT device through reverse scanning via the user terminal, the user sends the device identifier to the first server managing the IoT device. Reverse scanning refers to the user scanning a unique digital object identifier displayed on the IoT device using their user terminal.

[0095] In some scenarios, users have accounts on payment and other services provided by the operator of a second server. These accounts are pre-loaded with funds, and users can sign agreements with the second server operator. The funds in these accounts can be used for daily expenses, thus facilitating the user's life. Therefore, in this embodiment, the first service request may also carry a user identifier of the user requesting the use of the IoT device. This identifier uniquely identifies the user, allowing for accurate identification of which user is requesting the target service corresponding to the first service request. The type of user identifier is not specifically limited here; it can be biometric information such as facial images, fingerprints, or iris scans, or character identifiers such as passwords.

[0096] In this embodiment of the specification, the second server is a payment deduction server; before sending the second business request to the second server, the method further includes:

[0097] Based on the user identifier, determine the deduction agreement number corresponding to the user identifier;

[0098] The second service request also carries a deduction agreement number corresponding to the user identifier.

[0099] Optionally, the device provider corresponding to the first server can sign a deduction agreement with the user and the payment deduction provider corresponding to the second server, and this deduction agreement has a deduction agreement number. Alternatively, a deduction agreement signed by the device provider corresponding to the first server, the user, and the payment deduction provider corresponding to the second server can be pre-stored. In this case, the pre-stored deduction agreement number corresponding to the user identifier can be retrieved.

[0100] In this embodiment of the specification, the signature result information is obtained by signing the device identifier of the IoT device and the deduction protocol number; the step of requesting the second server to perform transaction settlement based on the signature result information and the business execution result information specifically includes:

[0101] Based on the business execution result information, transaction data information is generated; the transaction data information includes at least transaction amount information;

[0102] The transaction data information and the signature result information are sent to the second server so that the second server can perform transaction settlement corresponding to the transaction data information for the account corresponding to the deduction agreement number based on the deduction agreement number carried in the signature result information.

[0103] In this embodiment, the business execution result information may specifically include business execution completion information, such as shipment quantity information, service frequency / duration information, etc. The transaction data information may specifically include transaction amount information (i.e., the amount requested for deduction), transaction time information (e.g., the time when the business execution result information is received or the actual time when the business execution is completed), transaction device information, transaction user information, etc.

[0104] Before the transaction is settled, the second server can also verify the signature result.

[0105] In the embodiments described in this specification, the IoT device is equipped with a device-side business application corresponding to the first server and a payment deduction-side business program corresponding to the second server;

[0106] The second business request is specifically used by the payment deduction party's business program to sign the information carried in the second business request to obtain the signature result information, and instruct the device party's business application to make the IoT device execute the target business to obtain the business execution result information.

[0107] In the embodiments described in this specification, the device-side service application enables the IoT device to execute a target service and obtain the service execution result information, specifically including:

[0108] The device's business application sends a business execution instruction to the business switch on the IoT device;

[0109] The service switch responds to the service execution command and controls the IoT device to execute the target service;

[0110] The service switch receives a service stop command based on a preset service stop rule;

[0111] The service switch responds to the service stop command and controls the IoT device to stop executing the target service;

[0112] The service switch sends a service execution completion notification to the device's service application;

[0113] The device's service application responds to the service execution completion notification by generating service execution result information.

[0114] IoT devices need to be able to provide corresponding business services to users under the control of relevant applications. As IoT device manufacturers or operators, they can develop device-side business applications to manage the hardware of IoT devices, thereby obtaining relevant business execution result information when IoT devices perform target businesses. IoT devices can be equipped with business switches, which receive instructions from the device-side business applications to control the opening and closing of IoT devices at the physical level. At the same time, after the business execution is completed, the device-side business applications generate some business execution result information about the execution of this business. Depending on the specific IoT device, the business execution result information may be the aforementioned shipment quantity information, service frequency / duration information, and other execution result information.

[0115] In this embodiment of the specification, after requesting the second server to perform transaction settlement based on the signature result information and the business execution result information, the method further includes:

[0116] The system receives transaction settlement result information sent by the second server; the transaction settlement result information carries at least transaction identifier information and transaction device information; the transaction device information is obtained by parsing the signature result information.

[0117] In this embodiment, the transaction fee for the business service corresponding to the first business request can be settled by the second server, or the specific transaction settlement task can be executed by other payment deduction applications managed by the operator of the second server, resulting in the final transaction settlement result and transaction identification information identifying this result. To enable the operator of the first server to know which IoT device executed the target task associated with this transaction, and to facilitate data collection and subsequent commission rebates, the second server can parse the corresponding transaction device information from the signature result information. Then, the second server can send the transaction settlement result information, carrying at least the transaction identification information and the transaction device information, to the first server.

[0118] The preceding text has described the technical solution of this invention from the perspective of the first server, which acts as the device provider. To more clearly illustrate the technical solution of this invention, a business execution method applied to a second server is provided below. The meaning of the second server has already been explained above and will not be repeated here. For example... Figure 2 As shown, Figure 2 This is a flowchart of another business execution method provided in the embodiments of this specification. Next, it will be discussed in conjunction with the attached... Figure 2 The embodiment of the specification provides a specific description of a business execution method, such as... Figure 2 As shown, this method may include:

[0119] Step 202: Receive a second service request for an IoT device sent by the first server; the second service request carries the device identifier of the IoT device.

[0120] The content of the first server and the second business request has been described above and will not be repeated here.

[0121] Step 204: Send service execution instruction information to the IoT device according to the device identifier; the service execution instruction information is used to instruct the IoT device to execute the target service to obtain service execution result information, and sign the service execution result information using the device identifier of the IoT device to obtain signature result information.

[0122] In this step, after receiving the device identifier carrying the IoT device, the second server can determine, at the physical entity level, which specific IoT device is involved in the second service request based on the device identifier. To achieve this, the second server can pre-store the correspondence between device identifiers and specific IoT devices at the physical entity level. Then, the second server sends service execution instruction information to the IoT device corresponding to the device identifier. Upon receiving this service execution instruction information, the IoT device can specifically execute the target service corresponding to the second service request. Simultaneously, to reliably confirm that it is indeed the IoT device corresponding to the device identifier that executed the corresponding target service, the service execution instruction information can also instruct the corresponding IoT device to sign the service execution result information using its device identifier. The method of IoT devices signing service execution result information using their device identifier has already been described above and will not be repeated here.

[0123] IoT devices can perform specific tasks based on the received business execution instructions. After completing the corresponding task, they can obtain the business execution result information. The content of the business execution result information has been described above and will not be repeated here.

[0124] Step 206: Receive a transaction settlement request sent by the first server; the transaction settlement request carries the signature result information sent by the IoT device to the first server, and transaction data information generated based on the business execution result information sent by the IoT device to the first server.

[0125] Step 208: In response to the transaction settlement request, perform transaction settlement based on the signature result information and the transaction data information.

[0126] In the embodiments described in this specification, the second service request also carries a deduction agreement number;

[0127] The deduction agreement number corresponds to the user identifier of the user requesting the execution of the target service;

[0128] The user identifier is carried in a first service request sent from the IoT device or the user terminal of the user requesting to perform the target service to the first server.

[0129] In this embodiment of the specification, the business execution instruction information is specifically used to sign the device identifier of the IoT device and the deduction agreement number to obtain signature result information; the step of responding to the transaction settlement request and performing transaction settlement based on the signature result information and the transaction data information specifically includes:

[0130] The signature result information is parsed to obtain the deduction agreement number;

[0131] Execute transaction settlement corresponding to the transaction data information for the account corresponding to the deduction agreement number.

[0132] In this embodiment of the specification, the step of performing transaction settlement based on the signature result information and the transaction data information in response to the transaction settlement request further includes:

[0133] Generate transaction settlement result information; the transaction settlement result information carries at least transaction identifier information and transaction device information; the transaction device information is obtained by parsing the signature result information.

[0134] In this embodiment of the specification, after generating the transaction settlement result information, the method further includes:

[0135] The transaction settlement result information is sent to at least one of the first server and the user terminal that requested the target service.

[0136] In this embodiment of the specification, after sending service execution instruction information to the IoT device based on the device identifier, the method further includes:

[0137] Record the first association between the business execution instruction information and the IoT device;

[0138] After responding to the transaction settlement request and performing transaction settlement based on the signature result information and the transaction data information, the method further includes:

[0139] Record the second association between the transaction identifier information and the transaction device information;

[0140] The first association and the second association are used to determine whether the transaction corresponding to the transaction identifier information occurred on the IoT device.

[0141] In this scheme, after the second server sends service execution instruction information to the IoT device, it records the first association between the service execution instruction information and the IoT device. This is equivalent to the second server recording which specific IoT device received the service execution instruction. Thus, the second server participates in the service initiation process for the IoT device and records relevant information. After a specific IoT device executes the service execution instruction, the first server of the IoT device operator initiates a transaction settlement request to the second server. At this time, after the second server performs transaction settlement based on the signature result information and the transaction data information, it also records the second association between the transaction identifier information and the transaction device information. This is equivalent to the second server recording which specific IoT device is being used for transaction settlement of the target service. By comparing the first and second associations, it can be determined whether the transaction corresponding to the transaction identifier information occurred on the IoT device, i.e., whether the IoT device that specifically executed the service execution instruction and the IoT device that performed the transaction settlement are the same IoT device.

[0142] The embodiments in this specification also include:

[0143] Obtain a request to determine the authenticity of the business transaction for the IoT device;

[0144] According to the preset business authenticity judgment rules, based on the first association relationship and the second association relationship, a business authenticity judgment result is obtained; the business authenticity judgment result is used to indicate whether the transaction corresponding to the transaction data information occurred on the IoT device.

[0145] In this step, after receiving the business authenticity judgment request, the second server can determine whether the transaction corresponding to the transaction data information occurred on the IoT device based on the first association relationship and the second association relationship. The reason for being able to perform business authenticity judgment has been explained above and will not be repeated here.

[0146] In the embodiments described in this specification, the IoT device is equipped with a device-side business application corresponding to the first server and a payment deduction-side business program corresponding to the second server;

[0147] The business execution instruction information is specifically used by the payment deduction party's business program to sign the information carried in the business execution instruction information to obtain the signature result information, and then instruct the device party's business application to make the IoT device execute the target business to obtain the business execution result information.

[0148] In the embodiments described in this specification, the device-side service application enables the IoT device to execute a target service and obtain the service execution result information, specifically including:

[0149] The device's business application sends a business execution instruction to the business switch on the IoT device;

[0150] The service switch responds to the service execution command and controls the IoT device to execute the target service;

[0151] The service switch receives a service stop command based on a preset service stop rule;

[0152] The service switch responds to the service stop command and controls the IoT device to stop executing the target service;

[0153] The service switch sends a service execution completion notification to the device's service application;

[0154] The device's service application responds to the service execution completion notification by generating service execution result information.

[0155] The above content involves some steps in the specific working process of IoT devices, such as the control of IoT devices to turn on and off by the device provider's business applications. These have been described in the previous text and will not be elaborated on here.

[0156] According to the above explanation, such as Figure 3 As shown in the embodiments of this specification, a signaling interaction diagram of a service execution method in a practical application scenario is also provided, including:

[0157] Step 302: The user initiates a service request to the device's server. The service request is used to request the IoT device to process the target service.

[0158] As stated above, users can trigger a business request to process the target business to an IoT device through forward scanning, and then the IoT device can send the business request to the server that manages it. Alternatively, users can obtain the device identifier of the IoT device through a user terminal through reverse scanning, and then send the device identifier to the device server that manages the IoT device (the device server can be understood as a specific implementation of the first server described above), thereby initiating a business request to the device server.

[0159] Step 304: The device server sends the business request data to the payment deduction server.

[0160] In this step, the device server forwards the business request data to the payment deduction server, so that the payment deduction server can participate in the business initiation process for IoT devices. The business request data may include the device identifier of the IoT device.

[0161] Step 306: The payment deduction server sends the business request data to the payment deduction business program.

[0162] For IoT devices, one implementation of the payment deduction process in this step can be an IoT software development kit (SDK) developed by the operator of the payment deduction server described earlier and embedded in the IoT device. Since the payment deduction server operator is trustworthy, they can use this SSD to sign the IoT device's identifier, obtaining a signature result, which in turn enables the IoT device to execute the target business and obtain the business execution result information.

[0163] Step 308: The payment deduction party's business program sends business request data and transaction signature result information to the device party's business application;

[0164] Step 310: The device side's business application controls the IoT device to execute the target business.

[0165] Step 312: The IoT device sends the business execution result information and transaction signature result information to the device's server;

[0166] Step 314: The device server initiates a payment deduction request to the payment deduction server.

[0167] Step 316: The payment deduction server sends the deduction result information to the user.

[0168] Step 318: The payment deduction server sends the deduction result information back to the device server.

[0169] In addition, the embodiments of this specification also provide a business execution method at the overall level, such as Figure 4 As shown, Figure 4 This is a flowchart of a business execution method at the overall level provided in the embodiments of this specification, including:

[0170] Step 402: The first server obtains a first service request for the IoT device; the first service request carries the device identifier of the IoT device.

[0171] Step 404: The first server sends a second service request to the second server; the second service request carries the device identifier of the IoT device.

[0172] Step 406: The second server sends service execution instruction information to the IoT device based on the device identifier.

[0173] Step 408: The IoT device executes the target business based on the business execution instruction information to obtain business execution result information, and signs the business execution result information using the device identifier of the IoT device to obtain signature result information.

[0174] Step 410: The IoT device sends the signature result information and the business execution result information to the first server.

[0175] Step 412: The first server sends a transaction settlement request to the second server based on the signature result information and the business execution result information; the transaction settlement request carries the signature result information and transaction data information generated based on the business execution result information.

[0176] Step 414: The second server responds to the transaction settlement request and performs transaction settlement based on the signature result information and the transaction data information.

[0177] Based on the same idea, the embodiments of this specification also provide a business execution device corresponding to the above method. Figure 5 The embodiments provided in this specification correspond to Figure 1 A schematic diagram of the structure of a business execution device, applied to a first server, such as... Figure 5 As shown, the device may include:

[0178] The first service request acquisition module 502 is used to acquire a first service request for an IoT device; the first service request carries the device identifier of the IoT device.

[0179] The second service request sending module 504 is used to send a second service request to a second server; the second service request carries the device identifier of the IoT device; the second service request is used to instruct the IoT device to execute a target service to obtain service execution result information, and to sign the service execution result information using the device identifier of the IoT device to obtain signature result information.

[0180] Information receiving module 506 is used to receive the business execution result information and the signature result information sent by the Internet of Things device;

[0181] The transaction settlement request module 508 is used to request the second server to perform transaction settlement based on the business execution result information and the signature result information.

[0182] It is understood that the modules mentioned above refer to computer programs or program segments used to perform one or more specific functions. Furthermore, the distinction between these modules does not imply that the actual program code must also be separate.

[0183] Additionally, this specification also provides another business execution device in its embodiments. Figure 6 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of a business execution device, applied to a second server, such as... Figure 6 As shown, the device may include:

[0184] The second service request receiving module 602 is used to receive a second service request for an IoT device sent by the first server; the second service request carries the device identifier of the IoT device;

[0185] The service execution instruction information sending module 604 is used to send service execution instruction information to the IoT device according to the device identifier; the service execution instruction information is used to instruct the IoT device to execute the target service to obtain service execution result information, and to sign the service execution result information using the device identifier of the IoT device to obtain signature result information;

[0186] The transaction settlement request receiving module 606 is used to receive a transaction settlement request sent by the first server; the transaction settlement request carries the signature result information sent by the IoT device to the first server, and transaction data information generated based on the business execution result information sent by the IoT device to the first server;

[0187] The transaction settlement module 608 is used to respond to the transaction settlement request and perform transaction settlement based on the signature result information and the transaction data information.

[0188] Similarly, it can be understood that the modules mentioned above refer to computer programs or program segments used to perform one or more specific functions. Furthermore, the distinction between these modules does not mean that the actual program code must also be separate.

[0189] In addition, the embodiments of this specification also provide a business execution system, such as Figure 7 As shown, Figure 7 A schematic diagram of a business execution system provided in this specification embodiment includes a first server, a second server, and an Internet of Things (IoT) device; wherein,

[0190] The first server is configured to obtain a first service request for an IoT device, wherein the first service request carries the device identifier of the IoT device; and send a second service request to the second server, wherein the second service request carries the device identifier of the IoT device.

[0191] The second server is configured to send service execution instruction information to the IoT device based on the device identifier;

[0192] The IoT device is configured to execute a target business based on the business execution instruction information to obtain business execution result information, sign the business execution result information using the device identifier of the IoT device to obtain signature result information, and send the business execution result information and the signature result information to the first server.

[0193] The first server is further configured to send a transaction settlement request to the second server based on the business execution result information and the signature result information; the transaction settlement request carries the signature result information and transaction data information generated based on the business execution result information;

[0194] The second server is also configured to respond to the transaction settlement request by performing transaction settlement based on the signature result information and the transaction data information.

[0195] Based on the same idea, this specification also provides devices corresponding to the above methods in its embodiments.

[0196] Figure 8 The embodiments provided in this specification correspond to Figure 1 A schematic diagram of the structure of a business execution server. For example... Figure 8 As shown, server 800 may include:

[0197] At least one processor 810; and,

[0198] Memory 830 communicatively connected to the at least one processor; wherein,

[0199] The memory 830 stores instructions 820 that can be executed by the at least one processor 810, the instructions being executed by the at least one processor 810 to enable the at least one processor 810 to:

[0200] Obtain a first service request for an IoT device; the first service request carries the device identifier of the IoT device.

[0201] A second service request is sent to a second server; the second service request carries the device identifier of the IoT device; the second service request is used to instruct the IoT device to execute a target service to obtain service execution result information, and to sign the service execution result information using the device identifier of the IoT device to obtain signature result information.

[0202] Receive the business execution result information and the signature result information sent by the IoT device;

[0203] Based on the business execution result information and the signature result information, a request is made to the second server to perform transaction settlement.

[0204] Figure 9 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of a business execution server. For example... Figure 9 As shown, server 900 may include:

[0205] At least one processor 910; and,

[0206] Memory 930 communicatively connected to the at least one processor; wherein,

[0207] The memory 930 stores instructions 920 that can be executed by the at least one processor 910, the instructions being executed by the at least one processor 910 to enable the at least one processor 910 to:

[0208] Receive a second service request for an IoT device sent by a first server; the second service request carries the device identifier of the IoT device;

[0209] Based on the device identifier, a service execution instruction information is sent to the IoT device; the service execution instruction information is used to instruct the IoT device to execute a target service to obtain service execution result information, and the service execution result information is signed using the device identifier of the IoT device to obtain signature result information;

[0210] The system receives a transaction settlement request sent by the first server; the transaction settlement request carries the signature result information sent by the IoT device to the first server, and transaction data information generated based on the business execution result information sent by the IoT device to the first server.

[0211] In response to the transaction settlement request, transaction settlement is performed based on the signature result information and the transaction data information.

[0212] Based on the same idea, the embodiments in this specification also provide Figure 1The method described herein corresponds to a computer-readable medium. The computer-readable medium stores computer-readable instructions that can be executed by a processor to implement the following method:

[0213] Obtain a first service request for an IoT device; the first service request carries the device identifier of the IoT device.

[0214] A second service request is sent to a second server; the second service request carries the device identifier of the IoT device; the second service request is used to instruct the IoT device to execute the target service and obtain service execution result information.

[0215] Receive the business execution result information and the signature result information sent by the IoT device;

[0216] Based on the business execution result information and the signature result information, a request is made to the second server to perform transaction settlement.

[0217] Accordingly, embodiments of this specification also provide Figure 2 The method described herein corresponds to a computer-readable medium. The computer-readable medium stores computer-readable instructions that can be executed by a processor to implement the following method:

[0218] Receive a second service request for an IoT device sent by a first server; the second service request carries the device identifier of the IoT device;

[0219] Based on the device identifier, a service execution instruction information is sent to the IoT device; the service execution instruction information is used to instruct the IoT device to execute a target service to obtain service execution result information, and the service execution result information is signed using the device identifier of the IoT device to obtain signature result information;

[0220] The system receives a transaction settlement request sent by the first server; the transaction settlement request carries the signature result information sent by the IoT device to the first server, and transaction data information generated based on the business execution result information sent by the IoT device to the first server.

[0221] In response to the transaction settlement request, transaction settlement is performed based on the signature result information and the transaction data information.

[0222] The foregoing has described specific embodiments of this specification. In some cases, the actions or steps described in the claims may be performed in a different order than those shown in the embodiments and may still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired results. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0223] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other.

[0224] The apparatus, devices and methods provided in the embodiments of this specification are corresponding. Therefore, the apparatus and devices also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the corresponding apparatus and devices will not be repeated here.

[0225] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0226] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0227] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0228] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0229] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention 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.) containing computer-usable program code.

[0230] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0231] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0232] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0233] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0234] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0235] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital character versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0236] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0237] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0238] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A service execution method applied to a first server, comprising: obtaining a first service request for an Internet of Things (IoT) device; the first service request carrying a device identifier of the IoT device; sending a second service request to a second server; the second service request carrying the device identifier of the IoT device; the second service request being used for the second server to instruct the IoT device to execute a target service to obtain service execution result information; the second service request also being used for the second server to instruct the IoT device to obtain signature result information; the signature result information being obtained by signing the service execution result information with the device identifier of the IoT device; receiving the service execution result information and the signature result information sent by the IoT device; based on the service execution result information and the signature result information, requesting the second server to perform transaction settlement. 2.The method of claim 1, wherein the obtaining a first service request for an Internet of Things (IoT) device comprises: receiving a first service request sent by an IoT device or a user terminal in response to a user's request for using the IoT device. 3.The method of claim 1, wherein the first service request further carries a user identifier of a user who requests to use the IoT device.

4. The method of claim 3, the second server being a pay-with-deduction server. Before the sending a second service request to a second server, the method further comprises: based on the user identifier, determining a withholding agreement number corresponding to the user identifier; the second service request further carries the withholding agreement number corresponding to the user identifier. 5.The method of claim 4, wherein the signature result information is obtained by signing the device identifier of the IoT device and the withholding agreement number; and the based on the service execution result information and the signature result information, requesting the second server to perform transaction settlement comprises: based on the service execution result information, generating transaction data information; the transaction data information at least containing transaction amount information; sending the transaction data information and the signature result information to the second server, so that the second server performs transaction settlement corresponding to the transaction data information on an account corresponding to the withholding agreement number based on the withholding agreement number carried in the signature result information. 6.The method of claim 1, wherein the signature result information is obtained by at least one of the following ways: the IoT device signs the service execution result information with the device identifier of the IoT device to obtain the signature result information; or, the IoT device sends the device identifier of the IoT device and the service execution result information to the second server; the second server signs the service execution result information with the device identifier of the IoT device to obtain the signature result information; the second server sends the signature result information to the IoT device. 7.The method of claim 1, wherein the based on the service execution result information and the signature result information, requesting the second server to perform transaction settlement comprises: generate transaction data information based on the service execution result information; send the transaction data information and the signature result information to the second server to request the second server to perform transaction settlement. 8.The method of claim 1, wherein the Internet of Things device is installed with a device-side service application corresponding to the first server and a payment withholding-side service program corresponding to the second server. The second service request is used to, after being received by the payment withholding-side service program, sign information carried in the second service request to obtain the signature result information, and instruct the device-side service application to cause the Internet of Things device to perform a target service to obtain the service execution result information. 9.The method of claim 8, wherein the device-side service application causes the Internet of Things device to perform a target service to obtain the service execution result information, specifically comprising: The device-side service application sends a service execution instruction to a service switch on the Internet of Things device. The service switch controls the Internet of Things device to perform the target service in response to the service execution instruction. The service switch receives a service stop instruction issued based on a preset service stop rule. The service switch controls the Internet of Things device to end the execution of the target service in response to the service stop instruction. The service switch sends a service execution end notification to the device-side service application. The device-side service application generates service execution result information in response to the service execution end notification. 10.The method of claim 1, after the second server is requested to perform transaction settlement based on the service execution result information and the signature result information, further comprising: receiving transaction settlement result information sent by the second server; The transaction settlement result information at least carries transaction identifier information and transaction device information. The transaction device information is parsed from the signature result information. 11.A service execution method applied to a second server, comprising: receiving a second service request for an Internet of Things device sent by a first server; The second service request carries a device identifier of the Internet of Things device. According to the device identifier and the correspondence between the device identifier and the Internet of Things device, the second server sends service execution instruction information to the Internet of Things device corresponding to the device identifier; The service execution instruction information is used to instruct the Internet of Things device to perform a target service to obtain service execution result information; The service execution instruction information is also used to instruct the Internet of Things device to obtain signature result information; The signature result information is obtained by signing the service execution result information with the device identifier of the Internet of Things device; receiving a transaction settlement request sent by the first server; the transaction settlement request carries the signature result information sent by the Internet of Things device to the first server, and transaction data information generated based on the service execution result information sent by the Internet of Things device to the first server; In response to the transaction settlement request, transaction settlement is performed based on the signature result information and the transaction data information. 12.The method of claim 11, wherein the second service request further carries a withholding agreement number. The withholding agreement number corresponds to a user identifier of a user requesting to execute the target service. The user identifier is carried in a first service request sent by the IoT device or a user terminal of the user requesting to execute the target service to the first server. 13.The method of claim 12, wherein the service execution indication information is specifically used for signing the device identification of the IoT device and the withholding agreement number to obtain signature result information. The transaction settlement is performed based on the signature result information and the transaction data information in response to the transaction settlement request, and specifically includes: The withholding agreement number is parsed from the signature result information. The transaction settlement corresponding to the transaction data information is performed on an account corresponding to the withholding agreement number. 14.The method of claim 13, wherein after the transaction settlement is performed based on the signature result information and the transaction data information in response to the transaction settlement request, the method further includes: generating transaction settlement result information; The transaction settlement result information at least carries transaction identifier information and transaction device information. The transaction device information is parsed from the signature result information. 15.The method of claim 14, wherein after the transaction settlement result information is generated, the method further includes: sending the transaction settlement result information to at least one of the first server and a user terminal requesting the target service. 16.The method of claim 14, wherein after the service execution instruction information is sent to the IoT device according to the device identifier, the method further includes: recording a first association relationship between the service execution instruction information and the IoT device; After the transaction settlement is performed based on the signature result information and the transaction data information in response to the transaction settlement request, the method further includes: recording a second association relationship between the transaction identifier information and the transaction device information; The first association relationship and the second association relationship are used to determine whether the transaction corresponding to the transaction identifier information occurs on the IoT device. 17.The method of claim 16, further comprising: obtaining a service authenticity judgment request for the IoT device; obtaining a service authenticity judgment result based on the first association relationship and the second association relationship according to a preset service authenticity judgment rule; The service authenticity judgment result is used to indicate whether the transaction corresponding to the transaction data information occurs on the IoT device. 18.The method of claim 11, wherein the IoT device is installed with a device-side service application corresponding to the first server and a payment withholding-side service program corresponding to the second server. The service execution instruction information is specifically used to be received by the payment withholding-side service program, and the information carried in the service execution instruction information is signed to obtain the signature result information, and the device-side service application is instructed to execute the target service to obtain the service execution result information. 19.The method of claim 18, wherein the device-side service application instructs the IoT device to execute the target service to obtain the service execution result information, and specifically includes: The device-side service application sends a service execution instruction to a service switch on the IoT device; The service switch controls the IoT device to execute the target service in response to the service execution instruction; The service switch receives a service stop instruction issued based on a preset service stop rule; The service switch controls the IoT device to end the execution of the target service in response to the service stop instruction; The service switch sends a service execution end notification to the device-side service application; The device-side service application generates service execution result information in response to the service execution end notification.

20. A service execution method, comprising: A first server acquires a first service request for an IoT device; The first service request carries a device identifier of the IoT device; The first server sends a second service request to a second server; the second service request carries the device identifier of the IoT device; The second server sends service execution instruction information to the IoT device corresponding to the device identifier according to the device identifier and the correspondence between the device identifier and the IoT device; The IoT device executes a target service based on the service execution instruction information to obtain service execution result information; The IoT device also acquires signature result information based on the service execution instruction information; The signature result information is obtained by signing the service execution result information with the device identifier of the IoT device; The IoT device sends the service execution result information and the signature result information to the first server; The first server sends a transaction settlement request to the second server based on the service execution result information and the signature result information; The transaction settlement request carries the signature result information and transaction data information generated based on the service execution result information; The second server performs transaction settlement based on the signature result information and the transaction data information in response to the transaction settlement request.

21. A service execution apparatus applied to a first server, comprising: A first service request acquisition module for acquiring a first service request for an IoT device; The first service request carries a device identifier of the IoT device; A second service request sending module for sending a second service request to a second server; the second service request carries the device identifier of the IoT device, so that the second server sends service execution instruction information to the IoT device corresponding to the device identifier according to the device identifier and the correspondence between the device identifier and the IoT device; the second service request is used for the second server to instruct the IoT device to execute a target service to obtain service execution result information; the second service request is also used for the second server to instruct the IoT device to acquire signature result information; The signature result information is obtained by signing the service execution result information with the device identifier of the IoT device; An information receiving module for receiving the service execution result information and the signature result information sent by the IoT device; The transaction settlement request module is configured to request the second server to perform transaction settlement based on the business execution result information and the signature result information, including: sending the signature result information to the second server.

22. A business execution apparatus applied to a second server, comprising: A second business request receiving module configured to receive a second business request for an Internet of Things device sent by a first server; The second business request carries a device identifier of the Internet of Things device; A business execution instruction information sending module configured to send business execution instruction information to an Internet of Things device corresponding to the device identifier according to the device identifier and a corresponding relationship between the device identifier and the Internet of Things device; the business execution instruction information is used to instruct the Internet of Things device to execute a target business to obtain business execution result information; The business execution instruction information is also used to instruct the Internet of Things device to obtain signature result information; The signature result information is obtained by signing the business execution result information with the device identifier of the Internet of Things device; A transaction settlement request receiving module configured to receive a transaction settlement request sent by the first server; the transaction settlement request carries the signature result information sent by the Internet of Things device to the first server and transaction data information generated based on the business execution result information sent by the Internet of Things device to the first server; A transaction settlement module configured to perform transaction settlement based on the signature result information and the transaction data information in response to the transaction settlement request.

23. A business execution system comprising a first server, a second server and an Internet of Things device; The first server is configured to obtain a first business request for an Internet of Things device; the first business request carries a device identifier of the Internet of Things device; Send a second business request to the second server; the second business request carries the device identifier of the Internet of Things device; The second server is configured to send business execution instruction information to an Internet of Things device corresponding to the device identifier according to the device identifier and a corresponding relationship between the device identifier and the Internet of Things device; The Internet of Things device is configured to execute a target business to obtain business execution result information based on the business execution instruction information; Obtain signature result information, which is obtained by signing the business execution result information with the device identifier of the Internet of Things device; send the business execution result information and the signature result information to the first server; The first server is also configured to send a transaction settlement request to the second server based on the business execution result information and the signature result information; the transaction settlement request carries the signature result information and transaction data information generated based on the business execution result information; The second server is also configured to perform transaction settlement based on the signature result information and the transaction data information in response to the transaction settlement request.

24. A business execution server, comprising: At least one processor; And A memory connected with the at least one processor in communication; wherein The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to implement the business execution method of any one of claims 1 to 20.

25. A computer readable medium having stored thereon computer readable instructions executable by a processor to implement the business execution method of any one of claims 1 to 20.

Images