A service processing method and device based on multi-modal communication

Abstract

The embodiment of the present specification provides a business processing method and device based on multi-modal communication. The scheme comprises: a first terminal acquires label information provided by a second terminal through near field communication; based on the label information, business confirmation information is generated; based on the Bluetooth broadcast mode, a business identity authentication request sent by the second terminal is received; business identity authentication information is sent to the second terminal; if the business identity authentication information is verified, Bluetooth connection is established with the second terminal; if the confirmation operation performed by the user for the business confirmation information is acquired, and Bluetooth connection with the second terminal has been established, the second business information for triggering the business process of the target business is sent to the second terminal through the Bluetooth communication mode, so that the second terminal executes the business process of the target business by using the second business information.

Description

Technical Field

[0001] This specification relates to one or more embodiments in the field of near-field communication technology, and particularly to a service processing method based on multimodal communication. This specification also relates to a service processing apparatus based on multimodal communication, a computing device, a computer-readable storage medium, and a computer program product. Background Technology

[0002] With the maturity of near-field communication (NFC) technology, mobile service processing solutions based on short-range wireless communication have been increasingly widely used in scenarios such as payment, identity verification, and ticketing verification. NFC, a short-range high-frequency wireless communication technology operating at 13.56MHz with an effective communication distance of less than ten centimeters, is widely used in credential interaction scenarios due to its inherent security distance limitations. How to conduct business processing more conveniently and reliably is a direction that those skilled in the art continue to explore. Summary of the Invention

[0003] In view of the above, one or more embodiments of this specification provide a method, apparatus, device, computer-readable medium, and computer program product for near-field communication to improve near-field communication performance.

[0004] According to a first aspect of one or more embodiments of this specification, a service processing method based on multimodal communication is provided, applied to a first terminal, comprising: acquiring tag information provided by a second terminal via near-field communication; the tag information including first service information related to a target service; generating service confirmation information based on the tag information; receiving a service authentication request sent by the second terminal via Bluetooth broadcast; in response to the service authentication request, sending service authentication information to the second terminal; the service authentication information including at least a portion of the information in the first service information; if the service authentication information is successfully verified, establishing a Bluetooth connection with the second terminal; if a confirmation operation performed by a user for the service confirmation information is obtained, and a Bluetooth connection has been established with the second terminal, sending second service information for triggering a service process of the target service to the second terminal via Bluetooth communication, so that the second terminal uses the second service information to execute the service process of the target service.

[0005] According to a second aspect of one or more embodiments of this specification, a service processing method based on multimodal communication is provided, applied to a second terminal, comprising: providing tag information to a first terminal via near-field communication, the tag information including first service information related to a target service; sending a service authentication request to the first terminal via Bluetooth broadcast; verifying the service authentication information sent by the first terminal in response to the service authentication request; the service authentication information including at least a portion of the first service information; if the verification passes, establishing a Bluetooth connection with the first terminal; receiving second service information sent by the first terminal via Bluetooth communication; the second service information being sent by the first terminal after obtaining a confirmation operation performed by a user for service confirmation information and establishing a Bluetooth connection with the second terminal; and executing the service process of the target service using the second service information.

[0006] According to a third aspect of one or more embodiments of this specification, a service processing apparatus based on multimodal communication is provided, comprising: The tag acquisition module is used to acquire tag information provided by a second terminal via near-field communication; the tag information includes first service information related to the target service. The confirmation information module is used to generate business confirmation information based on the tag information; The request acquisition module is used to receive the business authentication request sent by the second terminal via Bluetooth broadcast. The verification sending module is used to send business authentication information to the second terminal in response to the business authentication request; the business authentication information includes at least a portion of the information in the first business information; A Bluetooth connection module is used to establish a Bluetooth connection with the second terminal if the business authentication information is verified successfully. The information sending module is used to send second business information to the second terminal via Bluetooth communication if it obtains a confirmation operation performed by the user for the business confirmation information and a Bluetooth connection has been established with the second terminal, so that the second terminal can use the second business information to execute the business process of the target business.

[0007] According to a fourth aspect of one or more embodiments of this specification, a service processing apparatus based on multimodal communication is provided, comprising: An information providing module is used to provide tag information to a first terminal via near-field communication, wherein the tag information includes first service information related to the target service; The verification request module is used to send a business authentication request to the first terminal via Bluetooth broadcast. The verification module is used to verify the business authentication information sent by the first terminal in response to the business authentication request; the business authentication information includes at least a portion of the information in the first business information. A Bluetooth connection module is used to establish a Bluetooth connection with the first terminal if the verification passes. The information receiving module is used to receive second service information sent by the first terminal via Bluetooth communication; the second service information is sent by the first terminal after it has obtained the confirmation operation performed by the user for the service confirmation information and has established a Bluetooth connection with the second terminal. The business processing module is used to execute the business process of the target business using the second business information.

[0008] According to a fifth aspect of one or more embodiments of this specification, a computing device is provided, comprising: a memory and a processor; the memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, wherein the computer programs / instructions, when executed by the processor, implement the steps of the above-described service processing method based on multimodal communication.

[0009] According to a sixth aspect of one or more embodiments of this specification, a computer-readable storage medium is provided that stores computer instructions, which, when executed by a processor, implement the steps of the above-described service processing method based on multimodal communication.

[0010] According to a seventh aspect of the embodiments of this specification, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described service processing method based on multimodal communication.

[0011] One or more embodiments of this specification can achieve at least the following beneficial effects: Through the collaborative multimodal communication of near-field communication (NFC) and Bluetooth, the first terminal obtains tag information containing business information from the second terminal via NFC, establishes a Bluetooth connection channel with the second terminal via Bluetooth broadcast, and completes business authentication and data transmission using the Bluetooth connection. The architecture design, which automatically switches the Bluetooth link for subsequent data interaction after NFC is triggered, allows users to complete the entire business process without maintaining device contact for extended periods, improving the convenience of business processing and avoiding communication interruptions and business failures due to user disengagement. Furthermore, by including at least a portion of the business information obtained during the NFC phase in the business authentication information, the Bluetooth connection identity is made trustworthy, preventing man-in-the-middle attacks and broadcast sniffing. The fact that the first terminal only sends the second business information to the second terminal via Bluetooth after receiving user confirmation also enhances the security of business processing. Attached Figure Description

[0012] 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 specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 This diagram illustrates an application scenario of a service processing method based on multimodal communication, as provided in one embodiment of this specification. Figure 2 A flowchart illustrating a service processing method based on multimodal communication provided in one embodiment of this specification; Figure 3 A flowchart illustrating a service processing method based on multimodal communication provided in one embodiment of this specification; Figure 4 A swimlane diagram of a service processing method based on multimodal communication provided in one embodiment of this specification; Figure 5 The embodiment provided in this specification corresponds to Figure 2 A schematic diagram of the structure of a service processing device based on multimodal communication; Figure 6 The embodiment provided in this specification corresponds to Figure 3 A schematic diagram of the structure of a service processing device based on multimodal communication; Figure 7 This is a structural block diagram of a computing device provided in one embodiment of this specification. Detailed Implementation

[0014] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this specification.

[0015] This specification uses specific terms to describe embodiments thereof. Terms such as "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic associated with at least one embodiment of this specification. Therefore, it should be emphasized and noted that references to "an embodiment," "one embodiment," or "an alternative embodiment" in different locations throughout this specification do not necessarily refer to the same embodiment. Furthermore, those skilled in the art can combine and integrate the different embodiments or examples described herein, as well as the features of those different embodiments or examples, without contradiction.

[0016] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “an,” “an,” “the,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification includes any or all possible combinations of one or more associated listed items.

[0017] The terms “comprising,” “including,” or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, product, 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, product, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in the process, method, product, or apparatus that includes said elements is not excluded.

[0018] Although the terms "first," "second," etc., may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, "first" may also be referred to as "second," and similarly, "second" may also be referred to as "first," without departing from the scope of one or more embodiments of this specification. Ordinal numbers such as "first," "second," etc., do not necessarily indicate order; often they are used to facilitate the distinction of objects. For example, "first server" and "second server" usually refer to two servers. To distinguish these two servers, they are described as "first server" and "second server." Of course, sometimes these two servers may be the same server.

[0019] The word "if" can be interpreted as "when," "when," or "in response to a determination," depending on the context.

[0020] In this specification, unless explicitly stated otherwise, "receiving and sending data" does not necessarily mean direct receiving and sending; it can also mean indirect receiving and sending. For example, A receiving data sent by B can be understood as A directly receiving the data sent by B, or it can be understood as A indirectly receiving the data sent by B through other entities such as C. Similarly, B sending data to A can be understood as B sending the data directly to A, or it can be understood as B indirectly sending the data to A through other entities such as C. Here, C can be one entity, or it can be two or more entities.

[0021] In this specification, unless explicitly stated otherwise, the relationships between structures can be direct or indirect. For example, when describing "A is connected to B," unless it is explicitly stated that A and B are directly connected, it should be understood that A can be directly connected to B or indirectly connected to B. Similarly, when describing "A is on top of B," unless it is explicitly stated that A is directly above B (AB is adjacent and A is above B), it should be understood that A can be directly above B or indirectly above B (AB is separated by other elements, and A is above B). And so on.

[0022] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties. The collection, use and processing of related data shall comply with the relevant laws, regulations and standards of the relevant regions, and corresponding operation entry points shall be provided for users to choose to authorize or refuse.

[0023] The following explains the terms and concepts used in one or more embodiments of this specification.

[0024] NFC (Near Field Communication) is a short-range wireless communication technology that enables near-field communication between two devices, allowing for data transmission, writing, and reading. It typically operates at a high frequency of 13.56MHz. NFC is based on RFID (Radio Frequency Identification) technology and can be considered a subset of RFID, or a special form of RFID.

[0025] NFC technology mainly includes three communication modes: Reader / Writer Mode, Card Emulation Mode, and Peer-to-Peer Mode. to Peer Mode).

[0026] Reader / Writer Mode is a common operating mode, similar to barcode or QR code scanning. In this mode, NFC devices can read or write information to NFC tags or devices containing NFC tags. For example, in payment scenarios, a mobile phone can be in Reader / Writer Mode to obtain payment information from the payment device for payment. A device in this mode can be called a card reader or a master device.

[0027] In Card Emulation Mode, the NFC device can emulate a smart card, allowing it to be used as a payment card, access card, or other type of card. The device can interact with existing contactless infrastructure, such as POS machines or access control systems. For example, using a mobile phone as a bank card for payments in stores; as an access card in offices or residences; or as a transit card for public transportation. Devices in this mode can be called tag devices or slave devices.

[0028] Peer-to-peer mode to Peer Mode allows two NFC-enabled devices to exchange data. Both devices must be active and capable of sending and receiving data. It's primarily used for file transfer, social networking, and interactive games. For example, it enables quick pairing of Bluetooth or Wi-Fi devices via NFC. Connect via Fi and then transfer files or photos; or exchange business cards, contact information, or social media links by tapping two phones; or swap characters or share items in multiplayer games.

[0029] An NFC tag is a small electronic chip with a built-in antenna that enables short-range communication with NFC-enabled devices (such as smartphones) via radio waves. These tags are typically very thin and can be embedded in various items, such as posters, business cards, product packaging, and devices. Devices with NFC tags can also be called tag devices or slave devices.

[0030] BLE (Bluetooth Low Energy): Low power Bluetooth technology, operating in the 2.4GHz ISM band, with a maximum communication distance of 10-100 meters, far exceeding the short-range limitation of NFC, and featuring low power consumption and fast connection characteristics.

[0031] HCE (Host Card Emulation): Host card emulation technology allows mobile devices to emulate smart cards without requiring a security element (SE) to perform card emulation.

[0032] Payment Token: A temporary credential used to verify payment requests, containing information such as device identifier, timestamp, and payment amount.

[0033] MTU (Maximum Transmission Unit): The maximum number of bytes in a single data packet during Bluetooth communication.

[0034] GATT (Generic Attribute Profile): A standard protocol for data exchange between BLE devices.

[0035] CCCD (Client Characteristic Configuration Descriptor): A client characteristic configuration descriptor used to notify or indicate whether a characteristic value is enabled or disabled.

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

[0037] Figure 1 This diagram illustrates an application scenario of a service processing method based on multimodal communication, as provided in one embodiment of this specification. Figure 1As shown, the first terminal 102, acting as an NFC card reader device, can obtain NFC tag information provided by the second terminal 104 via near-field communication. The first terminal 102 can generate service confirmation information based on this tag information, and the user can perform a confirmation operation based on this information. For example, after obtaining the tag information, the first terminal can display a service confirmation page containing a "confirm" operation control, which the user can click. Both the first and second terminals can also have Bluetooth modules. The first terminal can activate its Bluetooth module after obtaining the tag information, or the Bluetooth module may be already activated before obtaining the tag information. If the first terminal 102 receives a service authentication request, it sends service authentication information to the second terminal 104. The second terminal 104 verifies whether the first terminal 102 is a device for the target service. If the verification is successful, the second terminal 104 establishes a Bluetooth connection with the first terminal 102; if the verification fails, the second terminal 104 does not establish a Bluetooth connection with the first terminal 102. After establishing a Bluetooth connection, the first terminal 102 can send second business information, used to trigger the target business process, to the second terminal 104 via Bluetooth communication. Upon receiving the second business information, the second terminal 104 can execute subsequent business processes. For example, in a payment scenario, the first terminal 102 can send payment identifier information representing the user's account to the second terminal 104 via Bluetooth, and the second terminal 104 can execute the payment process based on this payment identifier information. This multimodal communication method, combining NFC near-field communication and Bluetooth, improves user convenience. Furthermore, the Bluetooth connection between the first and second terminals is established only after successful business authentication, and the second business information is sent only after the first terminal receives the user's confirmation, ensuring the security of business execution. This approach combines user convenience with secure business processing.

[0038] The first terminal can be an electronic device worn or used on the user side. In some embodiments, the first terminal can be a wearable device, such as a smartwatch, smart bracelet, or smart glasses. In some embodiments, the first terminal can also be a device that is easy for the user to carry, such as a mobile terminal like a mobile phone or laptop.

[0039] The first terminal has near-field communication (NFC) and Bluetooth communication capabilities. The NFC function is used to exchange and acquire business information with the second terminal at a short distance (typically within ten centimeters), while the Bluetooth communication function is used to establish a stable data communication connection with the second terminal at a longer distance (up to several meters, tens of meters, or even hundreds of meters) to complete authentication and business data transmission. In some embodiments, the first terminal may also include various sensor components such as a display screen, touch sensor, accelerometer, gyroscope, and heart rate sensor to enable user interaction and device status detection.

[0040] The second terminal can be a device on the other side that interacts with the first terminal to complete the target business. For example, it can be a terminal device deployed on the business scenario side. In some embodiments, the second terminal is a business processing terminal on the merchant side, such as an NFC terminal in a payment scenario, an access control terminal in an identity verification scenario, or a turnstile device in a ticket verification scenario. The second terminal also has near-field communication (NFC) and Bluetooth communication functions. Its NFC function is used to provide tag information containing business information to the first terminal, and its Bluetooth communication function is used to establish a communication connection with the first terminal after leaving the NFC field to complete the interaction of business data. In some embodiments, the second terminal can also communicate with other business devices through wired or wireless networks. For example, in a payment scenario, the second terminal can connect to the cashier, and the second terminal can provide the second business information provided by the first terminal to the cashier, who will then submit a payment request to the server. Alternatively, in some embodiments, the second terminal can interact with the server, submitting business requests to the server or providing some business information to the server, which can be specifically set according to actual needs. Taking payment services as an example, the server can be a payment server, which can perform validity verification, risk control checks and other processing on information such as payment identification information, business tokens and transaction amounts, and can also return the result of payment success or failure.

[0041] This application provides a service processing method based on multimodal communication. This application also relates to a service processing apparatus based on multimodal communication, a computing device, a computer-readable storage medium, and a computer program product, which will be described in detail in the following embodiments.

[0042] Figure 2 This is a flowchart illustrating a service processing method based on multimodal communication, provided as an embodiment of this specification.

[0043] From a programming perspective, the entity executing the process can be a program mounted on the first terminal. From a hardware perspective, the entity executing the process can be the first terminal. It can be understood that this method can be executed by any device, equipment, platform, or cluster of devices with computing and processing capabilities.

[0044] like Figure 2 As shown, the process may include the following steps: Step 202: Obtain tag information provided by the second terminal through near-field communication; the tag information includes first service information related to the target service.

[0045] After the first terminal acts as an NFC card reader device and meets the requirements for near-field communication with the second terminal, such as when the first terminal touches the second terminal, it can obtain tag information from the second terminal. The second terminal, as a tag-side device, can provide the tag information.

[0046] The tag information can contain information related to the currently pending business. For example, the tag information can be an NDEF (NFC Data Exchange Format) message. The first business information can be data content related to the target business contained in the tag information, such as the payment amount, order token, merchant identifier, etc. in a payment scenario; or, in an access control scenario, the first business information can include identification information of the current access control scenario (such as the name of the service location where the access control is located), the application identifier of the terminal application to be used, etc. The tag information can be generated by the second terminal before the first terminal communicates with the second terminal in the near field, or obtained by the second terminal from a server or other entity.

[0047] In some embodiments, the tag information can be in the form of a link, such as a link starting with http or https. This facilitates identification by the terminal system of the first terminal and can be applied to various types of terminals.

[0048] Step 204: Generate business confirmation information based on the tag information.

[0049] Business confirmation information can refer to information interfaces or prompts generated by the first terminal based on tag information, specifically based on the first business information, used to present to the user and request the user's confirmation. For example, a "Confirm Payment" page displayed in a payment scenario, or prompting the user through vibration, voice, etc. The user can perform the confirmation operation by clicking to display the page, or by voice, gesture, facial expression, or specific actions.

[0050] In some embodiments, the tag information may also include application identification information for the terminal application performing the target service. After the first terminal obtains the tag information, its terminal system can launch the corresponding terminal application based on the application identification information. The terminal system can provide all or part of the tag information to the terminal application. The terminal application can generate service confirmation information based on the tag information, and can also provide subsequent second service information. If the first terminal's terminal system has the capability to process the target service, it can also execute the service.

[0051] Step 206: Receive the business authentication request sent by the second terminal via Bluetooth broadcast.

[0052] Step 208: In response to the business authentication request, send business authentication information to the second terminal; the business authentication information includes at least a portion of the information in the first business information.

[0053] The second terminal has a Bluetooth module and can send a business authentication request. After the first terminal receives the business authentication request sent by the second terminal, it can send business authentication information. After successful authentication, the first terminal and the second terminal can establish a Bluetooth connection.

[0054] Business authentication information can refer to information sent by the first terminal to the second terminal after receiving a business authentication request, used to prove its own legitimacy. This information includes at least some information from the first business information (such as a business token field), used to achieve identity association verification between the near-field communication phase and the Bluetooth phase.

[0055] In some embodiments, the Bluetooth module of the second terminal may be always operational, capable of detecting Bluetooth signals at any time. For example, the Bluetooth module of the second terminal may be operational before near-field communication occurs between the first and second terminals. The Bluetooth module of the second terminal can remain operational regardless of whether there is interaction between the first and second terminals.

[0056] In some embodiments, the Bluetooth module of the second terminal can be activated when business processing is detected. For example, after the second terminal receives a business processing operation, such as after a cashier or other user enters the product information to be settled, the second terminal can activate the Bluetooth module to detect or receive external Bluetooth signals. Alternatively, the second terminal can activate its Bluetooth module after detecting the first terminal. Thus, during non-business processing phases, the Bluetooth module of the second terminal can be in a non-working mode or a low-power working mode, reducing energy consumption.

[0057] Step 210: If the business authentication information is verified, a Bluetooth connection is established with the second terminal.

[0058] A Bluetooth connection represents a stable, two-way data communication channel established between a first and a second terminal via the BLE protocol. Unlike the one-way transmission of Bluetooth broadcasts, a Bluetooth connection supports bidirectional data exchange between the two parties.

[0059] The second terminal verifies the business authentication information provided by the first terminal. If the verification is successful, the step of establishing a Bluetooth connection is executed, and the two establish a Bluetooth connection.

[0060] If the second terminal fails to verify the business authentication information provided by the first terminal, the second terminal may choose not to perform the step of establishing a Bluetooth connection, and may also send back a message indicating failure to the first terminal via Bluetooth broadcast. In this case, the two cannot establish a Bluetooth connection.

[0061] Step 212: If a confirmation operation performed by the user for the business confirmation information is obtained, and a Bluetooth connection has been established with the second terminal, then send second business information to the second terminal via Bluetooth communication to trigger the business process of the target business, so that the second terminal can use the second business information to execute the business process of the target business.

[0062] A confirmation action can represent an action performed by a user in response to business confirmation information, indicating that the user agrees to execute the business process. It can be a confirmation behavior actively performed by the user.

[0063] In some embodiments, the confirmation operation includes at least one of the following: touch operation, gesture operation, and voice operation. Touch operation can refer to an operation performed by a user touching the touchscreen or physical button of the first terminal, such as clicking the "Confirm" button on the screen. Gesture operation can refer to an operation triggered by a user through specific body movements (such as shaking the wrist, clenching a fist, or flipping the palm), and the first terminal can detect and recognize the gesture movements through built-in motion sensors (such as accelerometers and gyroscopes) or cameras. Voice operation can refer to an operation triggered by a user through voice commands, and the first terminal collects voice signals through a microphone and recognizes them using a voice recognition algorithm.

[0064] The target business can refer to the business to be completed in this interaction, including but not limited to payment, authentication, ticket verification, and data acquisition. Payment can refer to the act of making or receiving payment, such as paying for purchased goods. Authentication can refer to the business that requires verifying the user's identity to grant specific permissions, such as access control or attendance tracking. Ticket verification can refer to the business that requires verifying the validity of a user's ticket, such as subway gate access or scenic spot ticket verification. Data acquisition can refer to the business of exchanging data between the first and second terminals, such as exchanging electronic business cards or sharing data or files.

[0065] The second business information can refer to the data sent by the first terminal to the second terminal via Bluetooth connection after user confirmation and Bluetooth connection establishment, which is used to trigger the execution of business processes.

[0066] For example, in a payment scenario, the second business information can be payment identification information representing the user account of the first terminal. This payment identification information can be a string that triggers the POS device to send a payment processing request to the server and execute the acquiring process. For instance, the payment identification information can be a payment code number or a string with a similar string structure to the payment code number, capable of triggering the POS device to execute subsequent processes. To ensure the accuracy of business processing, the second business information can also include a monogram identifier, encrypted credentials, etc. The second terminal can verify the second business information or request the server to verify it. If the verification is successful, subsequent business processing can be executed based on the second business information.

[0067] For example, in an access control scenario, the second service information can be the card number information of the access control card held by the first terminal. The second terminal can use the second service information to determine whether to allow the user of the first terminal to pass.

[0068] For example, in a ticketing scenario, the second business information may be the number information of the electronic ticket held by the first terminal or the user identity information corresponding to the ticket purchased by the first terminal. The second terminal or other devices associated with the second terminal verify the second business information to determine whether the ticketing information provided by the first terminal is available in the current scenario.

[0069] While one or more embodiments of this specification provide method steps as described in the embodiments or flowcharts, it is understood that the order of steps listed in the embodiments or flowcharts is merely one possible execution order among many steps and does not represent the only execution order. The order of some steps can be adjusted according to actual needs, or some steps can be omitted. When the claims involve method steps, adjustments to the order of such steps, or parallel execution between steps, are also within the scope of protection of the claims. For example, steps 204 and 206 can be executed in parallel, or step 206 can be executed first and then step 204. As another example, if the first terminal has already authorized or the first terminal repeatedly executes preset services with the same second terminal within a short period of time, the user confirmation steps in steps 204 and 212 can be omitted. As yet another example, step 206 can be executed first and then step 202, and so on.

[0070] Figure 2The proposed method utilizes near-field communication (NFC) to trigger business operations and Bluetooth communication to handle authentication and data transmission after the user leaves the NFC area. This collaborative approach ensures the integrity of the business processing flow. Furthermore, it reduces the time the user on the first terminal needs to be close to the second terminal, with subsequent authentication and data transmission automatically completed via Bluetooth, resulting in a smoother and more natural overall interaction. Moreover, by establishing an information association between the first business information and the business authentication information, cross-communication mode identity consistency verification is achieved, effectively preventing security threats such as man-in-the-middle attacks or broadcast sniffing, and ensuring the security of business processing. Additionally, establishing a Bluetooth connection between the first and second terminals, and sending the second business information to the second terminal after receiving user confirmation, further enhances the security of business processing.

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

[0072] In some embodiments, to reduce the standby power consumption of the first terminal and improve the accuracy of wake-up, in one or more embodiments of this specification, the first terminal may activate relevant communication modules in response to a proximity event. Optionally, the method in one or more embodiments of this specification may further include: activating a near-field communication card reader module and a Bluetooth broadcast module in response to a proximity event with the second terminal.

[0073] A proximity event can refer to an event in which the distance between the first terminal and the second terminal is reduced to within a specific threshold. This event can be triggered by the establishment of the NFC radio frequency field, by a preset carrier signal sent by the second terminal, or by other proximity detection mechanisms, such as distance detection.

[0074] In some embodiments, the first terminal may be in a screen-off or locked state when it is near the second terminal or before it is near the second terminal. The first terminal is in a screen-on state after launching the terminal application or when a confirmation page needs to be displayed. For example, at this time, the first terminal may be in a locked state, and the user can perform a confirmation operation for the current business or a cancellation operation. Other businesses cannot be performed. After the user performs a confirmation operation or a cancellation operation, the first terminal may return to a screen-off state or display a screen-on but locked page.

[0075] A near-field communication (NFC) reader module can refer to a collection of hardware and software components in a first terminal used to read NFC tag information from a second terminal in reader mode during near-field communication. Once the reader module is activated, the first terminal can obtain tag information from the NFC radio frequency field of the second terminal.

[0076] A Bluetooth broadcast module can refer to a collection of hardware and software components in a first terminal used to send broadcast data packets to surrounding devices via the Bluetooth BLE protocol. Once the Bluetooth broadcast module is enabled, the first terminal begins sending BLE broadcast packets.

[0077] The near-field communication (NFC) reader module and the Bluetooth broadcast module can be triggered and started simultaneously. Alternatively, the NFC reader module can be started first, followed by the Bluetooth broadcast module. For example, the NFC reader module can be started first, acquiring tag information and launching the target application, before starting the Bluetooth broadcast module. Or, the NFC reader module can be started first, acquiring tag information and obtaining user confirmation, before starting the Bluetooth broadcast module. Alternatively, the Bluetooth broadcast module can be started first, followed by the NFC reader module. No specific limitations are imposed here.

[0078] In some embodiments, if the Bluetooth broadcast module of the first terminal is already enabled, after detecting a proximity event, the first terminal can enable the near-field communication (NFC) reader module, without needing to repeatedly enable the Bluetooth broadcast module. If the NFC reader module of the first terminal is already enabled, after detecting a proximity event, the first terminal can enable the Bluetooth broadcast module, without needing to repeatedly enable the NFC reader module. If the NFC reader module and Bluetooth broadcast module of the first device are in a disabled state by default, both in a dormant or power-off state, they can be enabled after a proximity event occurs. A proximity event can trigger the activation of one or both modules. The specific activation can be configured according to the state of each module.

[0079] Proximity events can be detected in different ways. As one implementation, the first terminal can continuously or periodically monitor its surroundings using its built-in detection sensors (such as infrared sensors, capacitive sensors, etc.). When a second terminal is detected nearby, the NFC reader module and the BLE broadcast module are activated.

[0080] In another implementation, the first terminal is in a low-power listening state by default, maintaining a low-frequency signal detection circuit in operation. When the first terminal enters the NFC radio frequency field range of the second terminal, the electromagnetic energy of the NFC radio frequency field is received by the antenna of the first terminal. This electromagnetic energy is sufficient to trigger the wake-up circuit of the first terminal, indicating the presence of a proximity event, and can activate the NFC reader module and the BLE broadcast module.

[0081] As another implementation, the second terminal can send a specific carrier signal. After detecting the specific carrier signal, the first terminal can activate the NFC reader module and the BLE broadcast module. Optionally, the method in one or more embodiments of this specification may further include: acquiring a preset carrier signal sent by the second terminal; the preset carrier signal is a carrier signal sent by the second terminal after detecting the proximity of an entity, and the preset carrier signal has different characteristics from the electromagnetic waves of near-field communication; if the preset carrier signal meets the preset characteristics, then it is determined that there is a proximity event between the second terminal processing the target service and the second terminal.

[0082] A preset carrier signal can be a specific electromagnetic signal actively sent by a second terminal after detecting an entity approaching its sensing area. The waveform characteristics, modulation method, or frequency characteristics of the preset carrier signal differ from those of conventional near-field communication electromagnetic waves, thus allowing it to be clearly distinguished by the first terminal. In some embodiments, the radiation range of the preset carrier signal can be greater than that of conventional near-field communication electromagnetic waves; for example, the radiation range of the preset carrier signal can be 20 cm, greater than the 10 cm of conventional NFC communication. This allows the first terminal to activate the reader module and / or Bluetooth broadcast module before entering the NFC communication range, preparing for communication in advance and shortening the overall business processing response time. In some embodiments, the radiation range of the preset carrier signal can be less than or equal to that of conventional near-field communication electromagnetic waves; for example, the radiation range of the preset carrier signal can be 7 cm, less than the 10 cm of conventional NFC communication. This allows the first terminal to activate the reader module and / or Bluetooth broadcast module before entering the NFC communication range, reducing the probability of false activation and minimizing the power consumption of the first terminal.

[0083] An entity can represent an object that is close to the sensing area of ​​the second terminal, such as the first terminal that is close to the second terminal.

[0084] The preset features can refer to waveform features or frequency feature parameters that are pre-stored in the first terminal to identify preset carrier signals. Only when the detected signal features match the preset features is it determined to be a valid proximity event.

[0085] For example, the second terminal is equipped with an infrared proximity sensor. When the infrared proximity sensor detects an object entering its detection range (e.g., within 20 cm), the control circuit of the second terminal drives the NFC front-end chip to send a preset carrier signal with a specific frequency offset (e.g., deviating from the standard 13.56MHz carrier frequency by a certain amount). The first terminal continuously monitors electromagnetic signals in the environment through its broadband signal detection circuit. When it detects a carrier signal with frequency characteristics matching the preset characteristics, it determines that a proximity event has occurred.

[0086] For example, the second terminal is equipped with a capacitive sensing electrode. When a conductive object (such as a smartwatch) approaches, the capacitance of the capacitive sensing electrode changes. After detecting this change, the control circuit sends a preset carrier signal. The preset carrier signal uses a modulation method different from the standard NFC protocol (such as amplitude modulation instead of standard ASK modulation). The first terminal distinguishes the preset carrier signal from the regular NFC signal by recognizing the difference in modulation method.

[0087] To ensure timely activation of the target application for processing the target service after a proximity event occurs, embodiments of this specification further provide two flexible strategies for activating the target application. Optionally, the method in one or more embodiments of this specification may further include: if, in response to a proximity event with the second terminal, it is determined that the second terminal is the terminal processing the target service, then the target application for processing the target service in the first terminal is activated simultaneously with the activation of the near-field communication card reader module; or, after obtaining the tag information, the target application for processing the target service in the first terminal is activated based on the tag information.

[0088] As one implementation, if the terminal system of the first terminal has the ability to identify a second terminal engaged in the target service, and if it can determine, based on a proximity event, that the second terminal approaching the first terminal is the terminal handling the target service, then the target application can be launched. This can be done before obtaining the tag information provided by the second terminal. In this way, after obtaining the tag information, the launched target application can more promptly determine the second service information and send it to the second terminal via Bluetooth. For example, after detecting a proximity event and confirming that the second terminal is the terminal handling the target service, the first terminal can execute two processes in parallel: first, it can activate the NFC reader module to read the tag information; second, it can launch the target application. These two processes can run concurrently. When the target application has finished loading and the NFC tag information has been read, the target application can use the acquired tag information to display a service confirmation page or provide service confirmation information to the user through other means.

[0089] As another implementation, after detecting a proximity event, the first terminal can first activate the NFC reader module to read the tag information. After obtaining the tag information, it parses the service type identifier field in the tag information, matches and launches the corresponding target application based on the service type identifier, or parses the application identifier field in the tag information and launches the corresponding terminal application based on the application identifier field.

[0090] The target application can refer to the application installed on the first terminal that is used to handle the current target business, such as a payment application in a payment scenario (such as a mobile client application of a payment platform) or an access control application in an authentication scenario.

[0091] Determining that the second terminal is the terminal processing the target service can mean that, when a proximity event occurs, the first terminal can determine that the approaching second terminal is a legitimate terminal used to process the target service, and not some other unrelated NFC device. For example, in the aforementioned embodiments, the second terminal can send a specific carrier signal, and the first terminal can determine whether the second terminal is the terminal performing the target service based on the characteristics of the carrier signal.

[0092] To further ensure the accuracy of business processing, optionally, the first terminal can broadcast device authentication information via Bluetooth broadcast; the device authentication information includes the terminal identification information of the first terminal; the second terminal can verify the device authentication information of the first terminal. If the device authentication information is verified successfully, it indicates that the first terminal is a terminal capable of processing the target business, and the second terminal can send a business authentication request, and the first terminal can receive the business authentication request initiated by the second terminal.

[0093] The device authentication information refers to the information carried by the first terminal in the BLE broadcast packet, used to indicate its identity or device type to the second terminal. Device authentication information differs from the aforementioned service authentication information. Device authentication information is used to verify whether the first terminal is a legitimate device type before the BLE connection is established, while service authentication information is used to verify whether the first terminal is a terminal participating in the current service during the BLE connection establishment process.

[0094] Terminal identification information can refer to information that can uniquely identify or classify a first terminal. Optionally, terminal identification information may include a universally unique identifier (UUID) and / or preset fixed marker information. Alternatively, terminal identification information may include the terminal's model information, serial number (SN), etc.

[0095] A Universally Unique Identifier (UUID) is a pre-defined identifier in the BLE protocol used to identify the identity of a device or service. A UUID can be used to identify the user or device identity of a first terminal, enabling a second terminal to recognize a specific first terminal.

[0096] The preset fixed tag information can refer to a fixed tag set in the BLE broadcast packet to identify the type of the first terminal device. It can be used to indicate that the first terminal is a terminal of the target type capable of processing the target service. For example, the tag can indicate that the first terminal is a wearable device that supports payment services, or it can indicate that the first terminal is a smartwatch that supports authentication services, etc.

[0097] Successful verification can mean that the second terminal, after parsing and comparing the device authentication information, confirms that the first terminal is a legitimate business processing terminal. For example, the second terminal may have a whitelist to determine whether the device authentication information is on the whitelist. Alternatively, the second terminal may have the ability to determine whether the device authentication information meets preset rules, such as whether the number of bytes in the string is a preset number, or whether the first one or more characters of the string are preset characters, etc.

[0098] For example, the first terminal enters its UUID and preset fixed marker information into the Manufacturer Specific Data field of the BLE broadcast packet. The UUID is a unique identifier assigned to the user when registering on a payment platform, and the preset fixed marker information is a fixed value "0x01" (indicating a wearable device that supports payment services). During the BLE scan, the second terminal parses the Manufacturer Specific Data field in the broadcast packet, extracts the UUID and fixed marker information, compares the UUID with a preset whitelist, and compares the fixed marker information with a list of target service types. If the UUID exists in the whitelist and the fixed marker information matches the target service type, the verification is successful.

[0099] For example, the first terminal fills in preset fixed marker information in the Service Data field of the BLE broadcast packet and fills in the string representation of the UUID in the Device Name field of the broadcast packet. During the BLE scan, the second terminal first quickly filters out devices whose names conform to the UUID specification through the Device Name field, and then performs type verification through the fixed marker information in the Service Data field.

[0100] Given that BLE broadcasts are public wireless signals, any device in the vicinity with BLE scanning enabled can receive them. Establishing connections indiscriminately with all devices that receive the broadcast could lead to security vulnerabilities and wasted resources. In some embodiments of this specification, by including device authentication information in the BLE broadcast packet of the first terminal, the second terminal can pre-screen the scanned devices, establishing BLE connections only with verified legitimate terminals, thereby improving communication security and efficiency.

[0101] To ensure authentication security across communication modes, some embodiments of this specification also provide a scheme for generating service authentication information. Optionally, the method in one or more embodiments of this specification may further include: extracting the service token field from the first service information; and performing an encrypted fusion operation between the service token field and the current system timestamp to obtain the service authentication information.

[0102] The business token field (Token) can refer to token data in the first business information used to uniquely identify this business transaction. The business token can be created by the second terminal (or business server) when generating tag information, and it is unique and unpredictable, used to associate the near-field communication stage and the Bluetooth stage in the subsequent authentication process.

[0103] The current system timestamp can refer to the current system time value obtained by the first terminal. Specifically, it can be the moment when the first terminal obtains or begins to obtain tag information, or it can be the moment when business authentication information is generated or begins to be generated.

[0104] Encryption fusion computation refers to combining a business token field and a timestamp using an encryption algorithm to generate verifiable signature data that contains both token and time information. Encryption fusion computation can include, but is not limited to, hash operations, HMAC (Hash-based Message Authentication Code) operations, symmetric encryption operations, and other methods.

[0105] In cross-communication modality authentication, the second terminal needs to verify that the first terminal currently communicating via BLE is indeed the same terminal that previously obtained tag information through NFC interaction. By incorporating a service token obtained from the NFC tag into the service authentication information, the second terminal can compare the token received in the BLE phase with the original token issued in the NFC phase, thereby verifying the identity association. Simultaneously, by incorporating a timestamp factor into the service authentication information, each generated service authentication message has a time limit; even if an attacker intercepts the service authentication information once, it cannot be reused within a subsequent period (because the timestamp has expired).

[0106] By encrypting and fusing business tokens with timestamps to generate business authentication information, the authentication information has both identity association and timeliness as security guarantees, effectively preventing identity impersonation and replay attacks, and improving the security of cross-communication modality business processing.

[0107] To balance data transmission efficiency and the user's ultimate control over service execution, some embodiments of this specification further provide a scheme combining segmented transmission strategy and user confirmation detection. Optionally, sending the second service information for triggering the target service process to the second terminal via Bluetooth communication may include: dividing the second service information into multiple data segments; and sequentially sending the multiple data segments to the second terminal via Bluetooth communication. Correspondingly, if a confirmation operation performed by the user for the service confirmation information is obtained, and a Bluetooth connection has been established with the second terminal, then sending the second service information to the second terminal via Bluetooth communication may include: starting to send partial data segments of the second service information to the second terminal after a Bluetooth connection has been established; detecting the confirmation operation before sending the remaining data segments, which at least include the last data segment of the multiple data segments; if the confirmation operation is detected, sending the remaining data segments; if the confirmation operation is not detected, terminating the sending of the remaining data segments.

[0108] A partial data segment can refer to the data segment that is sent before the user confirms the operation, among multiple data segments. For example, it can be the first N-1 data segments (where N is the total number of data segments).

[0109] The remaining data segment can refer to the data segment that is yet to be sent after some data segments have been sent, and can at least include the last data segment among multiple data segments. For example, the remaining data segment can be the last data segment among multiple data segments; or it can be the last two data segments, and so on. Since the second terminal needs to receive complete data to execute the business process, whether or not the last data segment is sent determines whether the business process is executed.

[0110] The detection of the confirmation operation may refer to continuously or periodically checking whether the user has performed the confirmation operation on the first terminal within a time window before sending the remaining data segments.

[0111] Terminating transmission can refer to the action of stopping the transmission of remaining data segments when it is detected that the user has not performed an acknowledgment operation. After termination of transmission, the second terminal will not execute the business process because it has not received complete data.

[0112] For example, the first terminal divides the second service information into N data fragments (N≥2), and immediately starts sequentially transmitting the first N-1 data fragments after the BLE connection is established, without detecting the user's confirmation operation at this time. When preparing to transmit the Nth (last) data fragment, the first terminal pauses transmission and detects whether the user has performed a confirmation operation. If the confirmation operation is detected, the Nth data fragment is transmitted; if a cancellation operation is detected (e.g., the user clicks the "cancel" button) or no operation is detected within a preset time window (e.g., 30 seconds), the transmission may be terminated, and the BLE connection may also be disconnected.

[0113] For example, the first terminal divides the second service information into N data fragments, sequentially transmits the first K data fragments (K<N-1) after the BLE connection is established, and detects the user's confirmation operation before transmitting the (K+1)th data fragment. If the confirmation is obtained, all the remaining data fragments (the (K+1)th to the Nth) are transmitted at one time; if the confirmation is not obtained, the (K+1)th data fragment continues to be transmitted and then the detection is performed again, until a final detection is performed before transmitting the Nth data fragment.

[0114] By dividing the second service information into a plurality of data fragments, part of the data fragments starts to be transmitted immediately after the Bluetooth connection is established, data transmission can be performed without waiting for user confirmation, and the user's confirmation operation is detected before transmitting the remaining fragments including the last data fragment, so that parallel processing of data transmission and user confirmation is realized, and both transmission efficiency and security are considered.

[0115] In order to enable the second terminal to obtain the second service information accurately and efficiently, as an implementation, the second service information may be divided according to the maximum transmission unit negotiated by the first terminal and the second terminal. Optionally, in one or more embodiments of this specification, the above-mentioned establishing a Bluetooth connection with the second terminal may include: establishing a Bluetooth Generic Attribute Profile connection channel with the second terminal; after the Generic Attribute Profile connection channel is established, performing maximum transmission unit negotiation. The above-mentioned dividing the second service information into a plurality of data fragments may include: dividing the second service information into a plurality of data fragments based on the negotiated maximum transmission unit.

[0116] The Bluetooth Generic Attribute Profile (GATT) may be a protocol defining data transmission rules in the BLE protocol stack, which specifies a model for data exchange between a server and a client through Attributes. The GATT connection channel is a logical channel for bidirectional data exchange in a BLE connection.

[0117] The Maximum Transmission Unit (MTU) refers to the maximum number of payload bytes that a single ATT (Attribute Protocol) data packet can carry in a single BLE data exchange. The size of the MTU affects the amount of data transmitted in a single transmission; the larger the MTU, the more data is transmitted in a single transmission, and the fewer exchanges are required for the transmission.

[0118] MTU negotiation refers to the process by which, after a GATT connection is established, the two communicating parties exchange MTU request and response messages to determine the MTU value supported by both parties in this communication. For example, the default MTU value of the BLE protocol is 23 bytes (20 bytes of payload), which can be increased to a higher value (such as 512 bytes) through MTU negotiation.

[0119] A data segment can refer to a data block after the second service information is divided according to the maximum transmission unit (MTU) size. The length of each data segment does not exceed the negotiated maximum transmission unit (MTU) limit and can be equal to or close to the length of the maximum transmission unit (MCU).

[0120] For example, after a GATT connection is established, the first terminal sends an MTU request message to the second terminal, requesting that the MTU be set to 512 bytes. If the second terminal supports a 512-byte MTU, it replies with an MTU response message confirming the 512-byte MTU. After both parties confirm the MTU is 512 bytes, the first terminal divides the second service information, which has a total length of 2048 bytes, into four data segments of 512 bytes each, and sends them sequentially.

[0121] For example, after a GATT connection is established, the first terminal sends an MTU request message to the second terminal, requesting that the MTU be set to 1024 bytes. If the second terminal only supports a maximum MTU of 512 bytes, it replies with an MTU response message confirming that the MTU is 512 bytes. After both parties confirm that the MTU is 512 bytes, the first terminal divides the data into segments accordingly.

[0122] After the MTU is negotiated through the GATT connection, the transmission unit size supported by both parties is determined. Data is segmented based on the negotiated MTU to ensure that the size of each data segment matches the effective payload of the communication link. This avoids secondary fragmentation of data at the link layer and improves the efficiency and reliability of data transmission.

[0123] In some embodiments, the length of data segments can be preset in the first terminal, and the data is divided according to this preset length. This preset length can be a length set by statistically analyzing the data length that can be transmitted at one time by various models or commonly used first terminals and second terminals via Bluetooth connection, such as taking the minimum value, median, average value, etc. If the preset length is used to divide the second service information, the first terminal and the second terminal may not need to perform the MTU negotiation step.

[0124] In some embodiments, the first terminal may not have network connectivity and may not be able to interact with the server. In order to improve the user experience, the second terminal may send business execution result information to the first terminal via Bluetooth connection. The first terminal may be able to obtain the business execution result information sent by the second terminal via Bluetooth connection.

[0125] Business execution result information can refer to the processing result obtained by the second terminal after executing the business process using the second business information, including but not limited to the identifier of business execution success or failure, transaction serial number, execution time, error code and other information.

[0126] For example, after receiving the processing result returned by the service server, the second terminal encapsulates the result information into a BLE notification message and actively pushes it to the first terminal through the established GATT connection channel. After receiving the notification message, the first terminal parses the result information and displays it on the screen.

[0127] For example, the second terminal writes the service execution result into a specific characteristic value in the GATT connection, and the first terminal obtains the service execution result by reading this characteristic value.

[0128] Taking a payment scenario as an example, the user's smartwatch is the first terminal, and the near-field communication (NFC) device associated with the checkout is the second terminal. The NFC device establishes a Bluetooth connection with the smartwatch, obtains payment identification information (second business information) representing the user's account from the smartwatch, and provides this payment identification information to the checkout. The checkout can then trigger the payment processing flow, requesting deduction from the server. After executing the deduction process, the server can send the result back to both the checkout and the NFC device. The NFC device can then send the result information to the smartwatch via Bluetooth, and the smartwatch displays the text or symbol "Payment Successful" on its screen. Alternatively, if the payment is unsuccessful, it can display the text or symbol "Payment Failed".

[0129] In some embodiments, if the first terminal does not receive the result information within a preset time after sending the second business information, it may display a prompt message to the user to confirm the payment result with the user of the second terminal, such as "Please confirm the payment result with the merchant".

[0130] By using BLE connection, the business execution results are sent back to the first terminal, allowing users to view the business processing results on the first terminal without having to pay attention to the display screen of the second terminal, which can improve the user experience and the convenience of interaction.

[0131] In some embodiments, to further improve the security of business processing, a security control scheme based on the terminal unlock status is provided. Optionally, the method in one or more embodiments of this specification may further include: detecting whether the first terminal is in an unlocked state; if the first terminal is in a locked state, presenting an unlock prompt message; after obtaining the unlock information input by the user and successfully unlocking, presenting the business confirmation message; if the first terminal is in an unlocked state, skipping the unlock prompt process and presenting the business confirmation message.

[0132] The unlocked state refers to whether the first terminal is currently in a state where the user can use its full functionality. In the unlocked state (such as locked screen or sleep mode), the terminal's display screen does not directly present (e.g., through display, vibration, voice broadcast, etc.) the service confirmation information; the user needs to complete identity verification before it can be presented.

[0133] Unlock prompts refer to the content displayed to the user by the terminal when it is locked. These prompts can be presented through text display, voice announcement, terminal vibration, or other means, guiding the user to enter unlock information. Unlock prompts can include text prompts such as "Please enter your password," a password input field, or voice prompts to unlock.

[0134] Unlock information can refer to verification data entered by the user to prove their identity, such as passwords, PINs (Personal Identification Numbers), pattern lock unlock paths, fingerprint information, facial features, gestures, iris information, etc. This unlock information can be used to unlock the terminal, such as a screen unlock password. In some embodiments, this unlock information can be a password set by the user to perform a specific service using the target application, such as a payment password. For example, if a user can enable a password-free function in the target application, and the first terminal has password-free processing permissions, then the unlock information can be used to unlock the terminal. After unlocking the terminal, the user no longer needs to enter the password for performing the specific service in the target application.

[0135] In some embodiments, before the first terminal interacts with the second terminal in the near field, such as before the first terminal touches the second terminal or before the first terminal obtains the tag information of the second terminal, the first terminal may be in a black screen state or a screen-off state, or it may also be referred to as an unlocked state. When the first terminal interacts with the second terminal in the near field, for example, after the first terminal touches the interaction area of ​​its screen with the second terminal's screen, and the first terminal obtains the tag information, if the first terminal is in an unlocked state, it may first display an unlock prompt page. After the user enters unlock information, the first terminal then displays service confirmation information. The user can then perform a confirmation operation based on the service confirmation information.

[0136] For example, before displaying the service confirmation information, the first terminal queries the system's current lock screen status flag. If the flag indicates "locked," a password input interface is displayed on the screen, waiting for the user to enter the password. After the user enters the correct password, the terminal unlocks and then displays the service confirmation information. If the flag indicates "unlocked," the service confirmation information is displayed directly.

[0137] Taking a payment scenario as an example, when a user's smartwatch is in standby mode (unlocked or screen off) and is brought close to a near-field communication (NFC) payment device, the watch reads the NFC tag information, detects that it is currently locked, and displays an unlock prompt interface on the screen with prompts such as "Please enter password" or "Please unlock." After the user enters their password or fingerprint, the watch unlocks and displays a transaction confirmation message "Confirm payment of 28.50 yuan." After the user confirms the payment, the watch completes subsequent data transmission via BLE connection. If the watch is already unlocked, the unlock prompt interface may not be displayed on the watch screen; the watch can directly display the transaction confirmation message after touching the payment device. After the user performs the confirmation operation, the first terminal can also display a message indicating that the transaction is being processed, such as a "Payment in progress" page.

[0138] By detecting the terminal's unlock status before presenting business confirmation information, and requiring the user to authenticate if the terminal is not unlocked, the business confirmation operation is ensured to be performed only when a legitimate user actively uses the terminal. This further reduces the risk of unauthorized execution of business and improves the security of terminal use.

[0139] To achieve a better balance between security and user experience, embodiments of this specification further provide a dual judgment scheme based on wearing status and unlocking history. Optionally, the method in one or more embodiments of this specification may further include: obtaining the wearing status of the first terminal; if the first terminal is in an unworn state, or if the first terminal has not entered successful unlocking information during the current wearing period, then displaying an unlocking prompt message; after obtaining the unlocking information entered by the user and successfully unlocking, displaying the service confirmation information; if the first terminal is in a worn state, and the first terminal has already entered successful unlocking information during the current wearing period, then skipping the unlocking process and displaying the service confirmation information.

[0140] Wearing status refers to whether the first terminal is currently being worn by the user on their body. The determination of wearing status can be based on the detection results of sensors, such as a heart rate sensor detecting a heartbeat signal, or a capacitive sensor detecting contact with the skin.

[0141] The current wearing period can refer to the continuous time period from when the first terminal was worn by the user to the current moment. If the terminal is removed and then worn again, it is considered a new wearing period.

[0142] The condition that "unlock information has been successfully entered during the current wearing period" means that the user has successfully entered unlock information and completed the unlocking operation during this current wearing period. This condition can be used to determine whether the terminal has been consistently used by the same user in a trusted state.

[0143] If the wearable device is already worn and the user has entered unlock information during this wearing period, it means the device has been worn by a legitimate user, and the possibility of it being maliciously used by others is low. Therefore, the unlocking process can be skipped and the business confirmation information can be displayed directly, improving interaction efficiency. If the wearable device is not worn (it may have been removed by someone else), or although it is worn but has never been unlocked during this wearing period (it may have just been put on by someone else), the user needs to be required to re-unlock and verify to ensure security.

[0144] Taking a payment scenario as an example, a user puts their smartwatch on their wrist after waking up in the morning and enters a password to unlock it. Throughout the day, the watch remains worn, and the user doesn't need to enter a password again each time they use it to make a payment, as the watch detects that it's been worn and unlocked during this period, allowing it to skip the unlocking process and directly display the payment confirmation page. In the evening, the user removes the watch and places it on a table. The watch detects that it's not being worn using its heart rate and capacitive sensors. The next morning, when the user puts the watch back on, since this is a new wearing period, the watch will prompt the user to re-enter their password before payment confirmation can proceed.

[0145] By combining the wearing status and the unlocking history during the current wearing period for dual judgment, the cumbersome operation of repeated unlocking is eliminated when the terminal is always worn and used by a legitimate user. When the terminal may be removed or the wearer may be changed, identity re-verification is required, thus achieving a good balance between security and user experience.

[0146] In some embodiments, if the first terminal fails to obtain the tag information or fails to parse the business information contained in the tag information due to unstable near-field communication or short communication duration, the first terminal may also display a prompt message to prompt the user to process again. For example, the first terminal may display a prompt message such as "No payment information detected. Please ensure that the screen is close to the cash register and pay again."

[0147] The various technical features in the above embodiments can be combined arbitrarily, as long as there is no conflict or contradiction between the combinations of features. However, due to space limitations, they have not been described one by one. Therefore, the arbitrary combination of various technical features in the above embodiments is also within the scope of this specification.

[0148] Based on the same approach, some embodiments of this specification also provide embodiments of a processing method with a second terminal as the execution subject. From a program perspective, the execution subject of the process can be a program mounted on the second terminal. From a hardware perspective, the execution subject of the process can be the second terminal. It is understood that this method can be executed by any device, equipment, platform, or device cluster with computing and processing capabilities.

[0149] like Figure 3 As shown, the process may include the following steps: Step 302: Provide tag information to the first terminal via near-field communication, wherein the tag information contains first service information related to the target service.

[0150] Step 304: Send a business authentication request to the first terminal via Bluetooth broadcast.

[0151] Step 306: Verify the business authentication information sent by the first terminal in response to the business authentication request; the business authentication information includes at least a portion of the information in the first business information.

[0152] Step 308: If the verification passes, establish a Bluetooth connection with the first terminal.

[0153] Step 310: Receive the second service information sent by the first terminal via Bluetooth communication; the second service information is sent by the first terminal after it has received the confirmation operation performed by the user for the service confirmation information and established a Bluetooth connection with the second terminal.

[0154] Step 312: Execute the business process of the target business using the second business information.

[0155] The meanings of the nouns and verbs involved in the above steps are as described in the section above regarding the method applied to the first terminal. Based on this, supplementary explanations are provided for some operations on the second terminal side.

[0156] Providing tag information can refer to the second terminal setting and maintaining an NFC tag within the NFC radio frequency field through its NFC front-end chip. When the first terminal enters the radio frequency field range, the first terminal's NFC reader can read the information in the tag.

[0157] Sending a service authentication request can refer to a second terminal proactively sending a request to the first terminal to obtain service identity information after discovering the first terminal's broadcast through BLE scanning or verifying its device identity. This request is used to determine whether the first terminal is the terminal that interacts with the second terminal to process the service that the second terminal is currently processing, and to determine whether the first terminal and the second terminal are processing the same service.

[0158] Verification refers to the process by which the second terminal verifies the business authentication information sent by the first terminal. For example, this could include comparing business tokens, checking the validity of timestamps, etc. Specific verification rules can be set according to actual needs. If verification passes, the second terminal can establish a Bluetooth connection with the first terminal. For instance, the second terminal can initiate a BLE connection to the first terminal to establish a GATT connection channel. After successful connection, the second terminal sequentially performs service discovery and MTU negotiation steps.

[0159] The business process of executing the target business can refer to the process in which the second terminal uses the second business information obtained from the first terminal to initiate a business request to the business server and obtain a processing result, or it can refer to the second terminal sending the obtained second business information to other devices that interact with the business server, and the devices then initiating a request to the server.

[0160] The process flow on the second terminal side forms a symmetrical cooperative relationship with that on the first terminal side. The second terminal provides tag information via NFC, establishes a trusted connection through BLE scanning and verification, and receives business data and executes business processes after user confirmation. Throughout the entire process, the second terminal undertakes tasks such as providing initial business information, identity verification, and triggering business processes.

[0161] The second terminal provides tag information containing business information through near-field communication, establishes a trusted connection with the first terminal through Bluetooth scanning and authentication, and receives business data provided by the first terminal after user confirmation to execute business processes. This realizes multimodal communication collaborative business processing, which can improve the efficiency and security of business processing.

[0162] To achieve efficient and secure device identification on the second terminal side, the embodiments of this specification further provide triggering strategies for device authentication and Bluetooth scanning. Optionally, before the second terminal sends a service authentication request to the first terminal, it may further include: obtaining device authentication information broadcast by the first terminal via Bluetooth broadcast; the device authentication information includes the terminal identification information of the first terminal; verifying the device authentication information; and if the verification is successful, sending a service authentication request to the first terminal.

[0163] For an explanation of the device authentication information, please refer to the description in the foregoing embodiments, which will not be repeated here.

[0164] Before the second terminal initiates a BLE connection request to the first terminal, it can first obtain and pre-verify the device authentication information broadcast by the first terminal, and then send a service authentication request to the first terminal. The first terminal can then provide service authentication information, which the second terminal verifies. If the verification passes, the second terminal initiates a Bluetooth connection to the first terminal. This avoids the second terminal mistakenly establishing a connection with non-target devices (such as other ordinary BLE devices) and also prevents unauthorized devices from impersonating legitimate terminals to access the service process.

[0165] In one implementation, the device identification information may include a Universally Unique Identifier (UUID) and / or preset fixed marker information. For specific meanings, please refer to the descriptions in the foregoing embodiments.

[0166] Correspondingly, the device authentication information can be verified by parsing the UUID and / or preset fixed tag information, comparing it with a preset whitelist or target business type list, and verifying if they match.

[0167] A pre-defined whitelist can be a list of registered or authorized first-terminal UUIDs stored locally on the second terminal or synchronized from a server. The UUIDs in the whitelist correspond to the legitimate first-terminal users. Only UUIDs present in the whitelist are considered legitimate terminal identities.

[0168] The target service type list can refer to a list storing terminal identifiers that support the current target service type. Unlike a whitelist, which records the identity of a specific device, the target service type list records the identifier of the device type. For example, in a payment scenario, the target service type list could record the identifier values ​​of all wearable device types that support NFC+BLE payment functionality.

[0169] Comparison refers to the operation of matching the parsed UUID and / or preset fixed tag information with records in a preset whitelist or target business type list. The comparison method can be exact matching (e.g., UUIDs are exactly the same) or pattern matching (e.g., fixed tags belong to a certain type in the list).

[0170] Taking a payment scenario as an example, a near-field communication (NFC) device (second terminal) at a cashier captures a BLE broadcast packet during BLE scanning. From this packet, the UUID "11223344" and a preset fixed marker "AAbb" are parsed. The NFC device first compares the fixed marker "AAbb" with a list of target service types. This list records the identifiers of wearable device types that support payment services, and "AAbb" happens to be in the list, indicating a successful type match. Subsequently, the NFC device compares the UUID with an authorized device whitelist synchronized from the bank's back-end system, confirming that the UUID belongs to a registered payment user of the target application. If both comparisons pass, the NFC device initiates a BLE connection request to the wearable device. If the fixed marker comparison fails, the UUID lookup is not performed.

[0171] By verifying the identity information, the second terminal can accurately and efficiently identify legitimate target business terminals in an open environment, providing security for subsequent business processing.

[0172] In some embodiments, the timing of the second terminal initiating Bluetooth scanning may include two strategies: the first is to initiate Bluetooth scanning immediately upon receiving the trigger command from the target service; the second is to initiate Bluetooth scanning only after detecting a proximity event with the first terminal. The second terminal can obtain device authentication information broadcast by the first terminal via Bluetooth broadcast through Bluetooth scanning. After successfully verifying the device authentication information, the second terminal can initiate a service authentication request to the first terminal.

[0173] A trigger instruction can be an instruction initiated by an operator or the system to begin a business process, such as the instruction generated when a cashier clicks the "Checkout" button at the checkout counter.

[0174] A proximity event can refer to an event where a second terminal detects that a first terminal has entered a preset distance range using its built-in sensors (such as NFC radio frequency field changes, infrared proximity sensors, capacitive sensors, etc.). Examples include detecting that the distance between the first and second terminals is less than or equal to a preset detection distance, or the second terminal sensing a touch from the first terminal. The detection distance for a proximity event can be greater than the effective distance of NFC communication, for example, it could be the effective distance of BLE communication, or close to the effective distance of BLE communication. This distance can be set based on the commonly used BLE communication distance, such as 0.5 meters. Alternatively, the detection distance can be equal to, close to, or slightly greater than or slightly less than the effective distance of NFC communication, such as 8 centimeters, 15 centimeters, etc.

[0175] For example, in scenarios with high response speed requirements (such as cashier during peak hours), the BLE scanning module can be activated after receiving the trigger command for the target service. By employing a pre-scanning strategy, the target device can be detected as early as possible, shortening the service processing time. In scenarios sensitive to power consumption (such as battery-powered access control devices), the BLE scanning module can be activated after the second terminal detects an approach event to the first terminal, which can reduce the idle time of the BLE scanning module and extend the device's battery life.

[0176] In some embodiments, the first terminal may employ a segmented transmission strategy, starting to send partial data segments immediately after the BLE connection is established, and the second terminal may correspondingly implement segmented reception and buffering mechanisms. Optionally, receiving the second service information sent by the first terminal via Bluetooth communication may include: receiving partial data segments of the second service information sent by the first terminal after the Bluetooth connection is established; and receiving the remaining data segments sent by the first terminal after the first terminal receives user confirmation, wherein the remaining data segments at least include the last data segment of the second service information.

[0177] After receiving partial data segments, the second terminal buffers them and waits for the last data segment to arrive before reassembling all the data segments into complete second service information. Since the transmission of the last data segment requires user confirmation, the second terminal can determine that the user has completed the confirmation and can execute the service process after receiving the complete data.

[0178] For example, after establishing a BLE connection with the first terminal, the second terminal begins receiving data segments sent by the first terminal. Upon receiving each data segment, the second terminal stores it in a memory buffer and sorts it according to the sequence number within the data segment. After receiving all the data, including the last data segment, the second terminal reads each data segment sequentially from the buffer according to its sequence number and reassembles it into complete second service information.

[0179] For example, the second terminal performs integrity verification (such as CRC check) on each data segment while receiving it. If the verification of a data segment fails, the second terminal sends a retransmission request to the first terminal, requesting that the data segment be retransmitted. After all data segments have passed verification, the data is reassembled.

[0180] In some embodiments of this specification, a scheme is further provided in which a second terminal sends a preset carrier signal to wake up a first terminal. Optionally, the method in one or more embodiments of this specification may further include: sending a preset carrier signal when an entity is detected to be nearby, so that the first terminal responds to the carrier signal to activate the near-field communication card reader module and the Bluetooth broadcast module.

[0181] For a detailed explanation of the preset carrier signal, please refer to the description in the foregoing embodiments. The second terminal can detect whether an entity is approaching through a built-in proximity detection sensor (such as an infrared sensor, a capacitive sensor, etc.). When an entity is detected approaching, the second terminal actively sends a preset carrier signal, which is used to wake up the first terminal, causing the first terminal to activate the NFC reader module and the BLE broadcast module.

[0182] Taking a payment scenario as an example, the infrared sensor built into the near-field communication device (second terminal) detects the presence of a human body when the user approaches the cashier at approximately 20 centimeters, and then sends a preset carrier signal. After the user's smartwatch detects this signal, it activates the NFC reader and BLE broadcast. When the user continues to move the watch to the NFC sensing area (approximately 3 to 5 centimeters), the watch's NFC reader is ready and can begin reading tag information.

[0183] In some embodiments, a scheme for the second terminal to verify the business authentication information is further provided. Optionally, the verification of the business authentication information may include: extracting the business token field and timestamp parameter from the business authentication information; verifying whether the business token field is correct; and verifying whether the timestamp is within a valid time range.

[0184] For details regarding the business token field and timestamp, please refer to the description in the aforementioned embodiments.

[0185] The valid time range can refer to a preset time window used to determine whether a timestamp is valid. For example, the valid time range can be set to 5 seconds, 10 seconds, or 30 seconds, or it can be set to a time range in milliseconds or microseconds, depending on actual needs. If the difference between the timestamp and the current system time exceeds the valid time range, the timestamp is considered expired and cannot pass the verification.

[0186] For example, the second terminal extracts the business token field from the business authentication information and compares it with the original token previously issued via the NFC tag. If they match, the token verification passes. Simultaneously, or after the token verification passes, the timestamp parameter is extracted, and the difference between the timestamp and the current system time is calculated. If the difference is within 2 seconds, the timestamp verification passes. Once both pass, the business authentication information verification is deemed successful.

[0187] For example, the second terminal uses a pre-shared key to perform HMAC verification on the business authentication information. After successful verification, the token and timestamp information are extracted and the token is compared and the timestamp validity is checked respectively.

[0188] By verifying the service token field, the second terminal can confirm that the first terminal sending the service authentication information is indeed the same terminal that previously obtained legitimate tag information through NFC interaction (because the service token originates from NFC tag information). By verifying the timestamp parameter, the second terminal can confirm that the authentication information was recently generated, rather than a replay of historical information. The combination of these two verification methods provides dual protection for both identity consistency and timeliness.

[0189] In some embodiments, the second terminal can also obtain the service execution results fed back by the server; and send the service execution results to the first terminal via Bluetooth connection.

[0190] Taking a payment scenario as an example, a near-field communication (NFC) device (second terminal) submits payment data, including identification information representing the user's payment account, sent by a smartwatch (first terminal) to the server of a payment platform. Alternatively, the data can be sent to the server by another device associated with the second terminal. After completing steps such as token validity verification, payment identifier verification, amount verification, risk control checks, and resource transfer, the server can return a "payment successful" result, or it can also return a transaction serial number. The NFC device can push the payment result to the smartwatch via BLE notification, and the smartwatch can display a "payment successful" message on its screen.

[0191] It is understood that the above-mentioned technical solutions with the first terminal or the second terminal as the execution subject belong to the same concept, and details not described in detail in any embodiment can be referred to the relevant descriptions in other embodiments.

[0192] Based on the above description, the swimlane diagram of a service processing method based on multimodal communication provided in the embodiments of this specification is illustrated here, taking a payment scenario as an example, with the first terminal being a wearable device and the second terminal being a payment terminal.

[0193] like Figure 4As shown, the scheme may include the NFC initial communication phase, the BLE communication trigger phase, the identity verification phase, the BLE connection establishment phase, the payment data transmission and verification phase, and the payment result return and connection disconnection phase.

[0194] During the initial NFC communication phase, the user brings the wearable device (first terminal) close to the payment terminal (second terminal). When the second terminal senses the proximity of a physical entity, it sends a preset carrier signal. Upon detecting this carrier signal, the wearable device activates its NFC reader. When the user brings the wearable device close to the NFC sensing area of ​​the payment terminal, the wearable device can read NFC tag information containing the payment amount, order token, and other primary business information from the payment terminal. After acquiring the tag information or sensing the preset carrier signal, the first terminal can launch the payment application, displaying a payment confirmation page, such as an operation page containing the words "Confirm Payment".

[0195] During the BLE communication triggering phase, after displaying the payment confirmation page, if the wearable device receives a confirmation operation from the user on that page, it can initiate a BLE broadcast. The broadcast packet can carry a service UUID and preset fixed identifier information. A second terminal can then initiate a BLE scan to discover the target wearable device based on the UUID and preset fixed identifier information. In some embodiments, the payment device can filter signals from numerous broadcast signals to determine the target wearable device. For example, it can perform service UUID matching or fixed identifier information matching.

[0196] During the identity verification phase, after discovering the target wearable device, the payment device can initiate a business identity verification request to the wearable device. The wearable device can return business identity verification information generated by encrypting and fusing an order token and a timestamp. The payment device verifies this information. If the verification passes, the scanning can be stopped and a BLE connection can be initiated by sending a Bluetooth connection request to the identified wearable device. If the verification fails, the acquired signal can be ignored, and the scanning can continue to acquire new signals and verify them until the verification passes or the scanning time is reached. In some embodiments, the payment device can filter signals that meet the conditions from the numerous acquired signals, such as by matching the device with the session identifier, verifying the validity of the signature or token, verifying the validity of the timestamp, etc., to perform identity verification on the acquired signals, filter signals that meet the conditions, and thus determine the wearable device that handles the same business. In some embodiments, the service UUID and fixed tag information can also be verified during the identity verification phase. When all verification conditions are met, the payment device can establish a Bluetooth connection with the wearable device.

[0197] In some embodiments, the payment device may not send a business identity verification request to the wearable device. Instead, the wearable device, after obtaining the tag information and activating the Bluetooth module, sends device authentication information and business identity verification information via Bluetooth broadcast. This includes verification information such as the service UUID, fixed identifier information, order token, and timestamp. The device authentication information and business identity verification information can be collectively referred to as identity verification information. The payment device scans for and obtains the broadcast information, and verifies it. If the verification passes, the scanning stops and a Bluetooth connection is established; if the verification fails, the scanning and verification continue.

[0198] The device authentication information and business identity verification information sent by wearable devices can be sent together or separately. This can be configured according to requirements.

[0199] During the BLE connection establishment phase, after the payment device verifies the wearable device, it can initiate a BLE connection, establish a GATT connection channel, perform service discovery and MTU negotiation, and the wearable device and payment device will successfully connect via BLE.

[0200] During the payment data transmission and verification phase, the wearable device sends payment data to the payment device in segments via BLE. This payment data may include the payment amount, payment identification information representing the user's payment account (such as payment code numbers), session ID, timestamp, and the token for the current payment. Before sending the last data segment, the wearable device can detect the user's confirmation action. After confirming that the user has performed the confirmation action, the last data segment is sent to the payment device.

[0201] Payment devices can send payment data, including data provided by the wearable device, to the server and submit a payment verification request. The server can then perform steps such as token validity verification, payment identifier verification, amount verification, and risk control checks. For details on the server-side processing flow, please refer to the relevant technical documentation; it will not be elaborated upon here.

[0202] During the payment result return and connection disconnection phase, after completing the current transaction, the server can return the payment result to the payment device. The payment device can notify the wearable device via BLE, and the wearable device can display the result to the user. After sending the payment result, the payment device can actively disconnect the BLE connection. After that, the payment device and the wearable device disconnect the BLE connection, and the interaction is complete.

[0203] In some embodiments, if the payment device and the wearable device also support other short-range communication methods, such as sound waves, RFID, etc., the payment device can also send payment result information to the wearable device through other short-range communication methods.

[0204] Based on the same idea, embodiments of this specification also provide apparatus corresponding to the above methods.

[0205] Figure 5 The embodiment provided in this specification corresponds to Figure 2 This is a schematic diagram of a service processing device based on multimodal communication. This device can be used as a first terminal.

[0206] like Figure 5 As shown, the device may include: The tag acquisition module 502 is used to acquire tag information provided by the second terminal through near-field communication; the tag information includes first service information related to the target service.

[0207] The confirmation information module 504 is used to generate business confirmation information based on the tag information.

[0208] The request acquisition module 506 is used to receive the business authentication request sent by the second terminal via Bluetooth broadcast.

[0209] The verification sending module 508 is used to send business authentication information to the second terminal in response to the business authentication request; the business authentication information includes at least a portion of the information in the first business information.

[0210] The Bluetooth connection module 510 is used to establish a Bluetooth connection with the second terminal if the business authentication information is verified.

[0211] The information sending module 512 is used to send second business information to the second terminal via Bluetooth communication if it obtains a confirmation operation performed by the user for the business confirmation information and a Bluetooth connection has been established with the second terminal, so that the second terminal can use the second business information to execute the business process of the target business.

[0212] Figure 6 The embodiment provided in this specification corresponds to Figure 3 This is a schematic diagram of a service processing device based on multimodal communication. This device can be used as a second terminal.

[0213] like Figure 6 As shown, the device may include: The information providing module 602 is used to provide tag information to the first terminal via near-field communication, wherein the tag information includes first service information related to the target service.

[0214] The verification request module 604 is used to send a business authentication request to the first terminal via Bluetooth broadcast.

[0215] The verification module 606 is used to verify the business authentication information sent by the first terminal in response to the business authentication request; the business authentication information includes at least a portion of the information in the first business information.

[0216] The Bluetooth connection module 608 is used to establish a Bluetooth connection with the first terminal if the verification is successful.

[0217] The information receiving module 610 is used to receive second service information sent by the first terminal via Bluetooth communication; the second service information is sent by the first terminal after it obtains the confirmation operation performed by the user for service confirmation information and establishes a Bluetooth connection with the second terminal.

[0218] The business processing module 612 is used to execute the business process of the target business using the second business information.

[0219] 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.

[0220] For ease of description, the above devices are described by dividing them into various modules or units based on their functions. Of course, when implementing one or more of these specifications, the functions of each module or unit can be implemented in the same or different software and / or hardware, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0221] The above is an illustrative scheme of a service processing device based on multimodal communication according to this embodiment. It should be noted that the technical solution of this service processing device based on multimodal communication and the technical solution of the service processing method based on multimodal communication described above belong to the same concept. For details not described in detail in the technical solution of the service processing device based on multimodal communication, please refer to the description of the technical solution of the service processing method based on multimodal communication described above.

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

[0223] Figure 7 A structural block diagram of a computing device 700 provided according to an embodiment of this specification is shown.

[0224] The computing device 700 includes: Memory 710 and processor 720; The memory 710 is used to store computer programs / instructions, and the processor 720 is used to execute the computer programs / instructions. When the computer programs / instructions are executed by the processor 720, they implement the steps of the above-described service processing method based on multimodal communication.

[0225] Specifically, the components of the computing device 700 include, but are not limited to, a memory 710 and a processor 720. The processor 720 is connected to the memory 710 via a bus 730, and the database 750 is used to store data.

[0226] The computing device 700 also includes an access device 740, which enables the computing device 700 to communicate via one or more networks 760. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 740 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0227] In one embodiment of this specification, the above-described components of the computing device 700 and Figure 7 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 7 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this application. Those skilled in the art can add or replace other components as needed.

[0228] The computing device 700 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 700 can also be a mobile or stationary server.

[0229] The processor 720 executes the computer instructions to implement the steps of the above-mentioned service processing method based on multimodal communication.

[0230] The above is an illustrative scheme of a computing device according to this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the service processing method based on multimodal communication described above belong to the same concept. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the service processing method based on multimodal communication described above.

[0231] An embodiment of this specification also provides a computer-readable storage medium storing computer instructions that, when executed by a processor, implement the steps of the service processing method based on multimodal communication as described above.

[0232] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium belongs to the same concept as the technical solution of the service processing method based on multimodal communication described above. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the service processing method based on multimodal communication described above.

[0233] An embodiment of this specification also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described service processing method based on multimodal communication.

[0234] The above is an illustrative scheme of a computer program product according to this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the above-described service processing method based on multimodal communication belong to the same concept. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solution of the above-described service processing method based on multimodal communication.

[0235] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for the embodiments of apparatus, devices, media, and products, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiments. The apparatus, devices, media, and products provided in the embodiments of this specification correspond to the methods, and therefore the apparatus, devices, media, and products 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, devices, media, and products will not be repeated here.

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

[0237] 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 methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to hardware circuit structures. 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.

[0238] 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.

[0239] 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.

[0240] 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.

[0241] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, the invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the 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.

[0242] 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.

[0243] 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.

[0244] 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.

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

[0246] 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.

[0247] 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.

[0248] 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.

[0249] 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 processing method based on multimodal communication, applied to a first terminal, comprising: The tag information provided by the second terminal is obtained through near-field communication. The tag information includes first business information related to the target business; Based on the tag information, generate business confirmation information; The system receives business authentication requests sent by the second terminal via Bluetooth broadcast. In response to the business authentication request, business authentication information is sent to the second terminal; the business authentication information includes at least a portion of the information in the first business information. If the business authentication information is verified, a Bluetooth connection is established with the second terminal; If a confirmation operation is obtained from the user regarding the service confirmation information, and a Bluetooth connection has been established with the second terminal, then second service information for triggering the service process of the target service is sent to the second terminal via Bluetooth communication, so that the second terminal can use the second service information to execute the service process of the target service.

2. The method according to claim 1, further comprising: In response to a proximity event with the second terminal, the near-field communication card reader module and the Bluetooth broadcast module are activated.

3. The method according to claim 2, further comprising: If, in response to a proximity event with the second terminal, it is determined that the second terminal is the terminal processing the target service, then the target application for processing the target service in the first terminal is started simultaneously with the activation of the near-field communication card reader module. Alternatively, after obtaining the tag information, the target application in the first terminal for processing the target service can be launched based on the tag information.

4. The method according to claim 2, further comprising: Acquire a preset carrier signal sent by the second terminal; the preset carrier signal is a carrier signal sent by the second terminal after detecting the presence of an entity approaching, and the preset carrier signal has different characteristics from the electromagnetic waves of near-field communication; If the preset carrier signal meets the preset characteristics, then it is determined that there is a proximity event between the second terminal processing the target service and the carrier signal.

5. The method according to claim 1, wherein receiving the service authentication request sent by the second terminal via Bluetooth broadcast includes: The device authentication information of the first terminal is broadcast via Bluetooth. The device authentication information includes the terminal identification information of the first terminal; If the device authentication information is verified, the service authentication request sent by the second terminal is received.

6. The method according to claim 5, wherein the device authentication information includes a universally unique identifier (UUID) and / or preset fixed marker information; the preset fixed marker information indicates that the first terminal is a target type terminal capable of processing the target service.

7. The method according to claim 1, further comprising: Extract the business token field from the first business information; The business token field is encrypted and fused with the current system timestamp to obtain the business authentication information.

8. The method according to claim 1, wherein sending second service information for triggering the service process of the target service to the second terminal via the Bluetooth communication method includes: The second business information is divided into multiple data segments; The multiple data segments are sequentially sent to the second terminal via Bluetooth communication connection; If a confirmation operation performed by the user for the service confirmation information is obtained, and a Bluetooth connection has been established with the second terminal, then the second service information is sent to the second terminal via Bluetooth communication, including: After establishing a Bluetooth connection with the second terminal, the system begins sending partial data segments of the second service information to the second terminal. The confirmation operation is detected before sending the remaining data segments, which include at least the last data segment of the plurality of data segments; If the confirmation operation is detected, the remaining data fragment is sent; If the confirmation operation is not detected, the transmission of the remaining data segments will be terminated.

9. The method according to claim 8, wherein establishing a Bluetooth connection with the second terminal comprises: Establish a Bluetooth Universal Attribute Specification connection channel with the second terminal; After the general attribute specification connection channel is established, maximum transmission unit negotiation is performed; The step of dividing the second business information into multiple data segments includes: Based on the negotiated maximum transmission unit, the second service information is divided into multiple data segments.

10. The method according to any one of claims 1 to 9, further comprising: Obtain the service execution result information sent by the second terminal via Bluetooth connection.

11. The method according to any one of claims 1 to 9, wherein the confirmation operation includes at least one form of operation selected from touch operation, gesture operation, and voice operation; And / or, the target business includes at least one of payment business, authentication business, ticket verification business, and data acquisition business; And / or, the first terminal includes a wearable device.

12. The method according to any one of claims 1 to 9, further comprising: Detect whether the first terminal is in an unlocked state; If the first terminal is in an unlocked state, an unlock prompt message will be displayed; After obtaining the unlock information input by the user and successfully unlocking, the service confirmation information is displayed; If the first terminal is in an unlocked state, the unlock prompt process is skipped, and the service confirmation information is presented.

13. The method according to any one of claims 1 to 9, further comprising: Obtain the wearing status of the first terminal; If the first terminal is not being worn, or if the first terminal has not entered successful unlocking information during the current wearing period, an unlocking prompt message will be displayed; after obtaining the unlocking information entered by the user and unlocking successfully, the service confirmation message will be displayed. If the first terminal is already in a worn state, and the first terminal has already entered successful unlocking information during the current wearing period, then the unlocking process is skipped, and the service confirmation information is displayed.

14. A service processing method based on multimodal communication, applied to a second terminal, comprising: Tag information is provided to a first terminal via near-field communication, and the tag information includes first service information related to the target service. A business authentication request is sent to the first terminal via Bluetooth broadcast. The business authentication information sent by the first terminal in response to the business authentication request is verified; the business authentication information contains at least a portion of the information in the first business information. If the verification passes, a Bluetooth connection is established with the first terminal; The second service information is received from the first terminal via Bluetooth communication; the second service information is sent by the first terminal after it has received the confirmation operation performed by the user for the service confirmation information and has established a Bluetooth connection with the second terminal. Using the second business information, execute the business process of the target business.

15. The method according to claim 14, further comprising, before sending the service authentication request to the first terminal: Obtain the device authentication information broadcast by the first terminal via Bluetooth broadcast; The device authentication information includes the terminal identification information of the first terminal; Verify the device authentication information; Sending the service authentication request to the first terminal includes: If the verification is successful, a business authentication request is sent to the first terminal.

16. The method of claim 15, further comprising: Upon receiving the trigger command from the target service, initiate Bluetooth scanning; Alternatively, Bluetooth scanning can be initiated after detecting a proximity event to the first terminal; The step of obtaining the device authentication information broadcast by the first terminal via Bluetooth broadcast includes: The device authentication information broadcast by the first terminal via Bluetooth is obtained through Bluetooth scanning.

17. The method according to claim 15, wherein verifying the device authentication information includes: Parse the Universal Unique Identifier (UUID) and / or preset fixed marker information in the device authentication information; The UUID and / or preset fixed tag information are compared with a preset whitelist or a target service type list; If the comparison matches, the verification is successful.

18. The method according to claim 14, wherein receiving the second service information sent by the first terminal via Bluetooth communication includes: After the Bluetooth connection is established, a partial data segment of the second service information sent by the first terminal is received; After the first terminal receives the user's confirmation operation, it receives the remaining data fragment sent by the first terminal, wherein the remaining data fragment contains at least the last data fragment of the second service information.

19. The method of claim 14, further comprising: When an entity is detected approaching, a preset carrier signal is sent so that the first terminal can activate the near-field communication card reader module and the Bluetooth broadcast module in response to the carrier signal.

20. The method according to claim 14, wherein verifying the business authentication information includes: Extract the business token field and timestamp parameter from the business authentication information; Verify that the business token field is correct and that the timestamp is within a valid time range.

21. The method of claim 14, further comprising: Obtain the business execution results returned by the server; The service execution result is sent to the first terminal via Bluetooth connection.

22. A service processing apparatus based on multimodal communication, comprising: The tag acquisition module is used to acquire tag information provided by the second terminal via near-field communication. The tag information includes first business information related to the target business; The confirmation information module is used to generate business confirmation information based on the tag information; The request acquisition module is used to receive the business authentication request sent by the second terminal via Bluetooth broadcast. The verification sending module is used to send business authentication information to the second terminal in response to the business authentication request; the business authentication information includes at least a portion of the information in the first business information; A Bluetooth connection module is used to establish a Bluetooth connection with the second terminal if the business authentication information is verified successfully. The information sending module is used to send second business information to the second terminal via Bluetooth communication if it obtains a confirmation operation performed by the user for the business confirmation information and has established a Bluetooth connection with the second terminal, so that the second terminal can use the second business information to execute the business process of the target business.

23. A service processing apparatus based on multimodal communication, comprising: An information providing module is used to provide tag information to a first terminal via near-field communication, wherein the tag information includes first service information related to the target service; The verification request module is used to send a business authentication request to the first terminal via Bluetooth broadcast. The verification module is used to verify the business authentication information sent by the first terminal in response to the business authentication request; the business authentication information includes at least a portion of the information in the first business information. A Bluetooth connection module is used to establish a Bluetooth connection with the first terminal if the verification passes. The information receiving module is used to receive second service information sent by the first terminal via Bluetooth communication; the second service information is sent by the first terminal after obtaining the confirmation operation performed by the user for the service confirmation information and establishing a Bluetooth connection. The business processing module is used to execute the business process of the target business using the second business information.

24. A computing device, comprising: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, which, when executed by the processor, implement the steps of the method according to any one of claims 1 to 21.

25. A computer-readable storage medium storing computer instructions that, when executed by a processor, implement the steps of the method according to any one of claims 1 to 21.

26. A computer program product comprising a computer program / instructions that, when executed by a processor, implement the steps of the method according to any one of claims 1 to 21.

Images