Service processing method, apparatus and device for smart watch

Abstract

Disclosed in the embodiments of the present description are a service processing method, apparatus and device for a smart watch, which are applied to a watch end on the smart watch. The solution comprises: acquiring socket communication trigger data; on the basis of the socket communication trigger data, performing encapsulation by using a short-range wireless communication protocol supported by a smart watch, so as to obtain a first data packet; sending the first data packet to a mobile phone end on a smart mobile phone by means of performing short-range wireless communication with the smart mobile phone, such that the mobile phone end parses the first data packet to obtain the socket communication trigger data, performs socket communication with a corresponding server end accordingly, and performs encapsulation on the basis of socket communication response data returned by the server end and by using the short-range wireless communication protocol, so as to obtain a second data packet; and receiving the second data packet returned from the mobile phone end by means of performing short-range wireless communication with the smart mobile phone, and parsing the second data packet to obtain the socket communication response data.

Description

A business processing method, device and equipment for smart watches Technical Field

[0001] This specification relates to the field of Internet of Things technology, and in particular to a service processing method, device, and equipment for smart watches. Background Art

[0002] With the popularity of smartphones, more and more people are using them for electronic payments. In recent years, smartwatches have also gradually emerged and their user base is expanding. Compared with smartphones, smartwatches are more convenient in some payment scenarios. Based on this, some smartwatches have drawn on the experience and achievements of mobile payment in terms of technology. By integrating QR code payment and ride code functions into smartwatches, users can easily and conveniently complete some payment operations in their lives by raising their wrists and using smartwatches without having to take out their smartphones.

[0003] Smartwatches currently on the market offer a variety of communication methods, including Bluetooth, Wi-Fi, and eSIM. Many smartwatches rely on real-time operating systems (RTOS) and only have Bluetooth communication modules. This significantly limits the payment experience. Typically, after making a payment, the user only sees a brief confirmation on the smartwatch. Due to the lack of communication with the payment server, the user cannot directly access detailed payment results from the payment server on the smartwatch.

[0004] Based on this, there is a need for a solution that can enhance the communication capabilities of such smart watches that only have Bluetooth communication modules, thereby improving the payment experience of smart watches.

[0005] Summary of the Invention

[0006] One or more embodiments of the present specification provide a business processing method for a smart watch, which is applied to a watch end on the smart watch, and the method includes: obtaining Socket communication trigger data; using the short-range wireless communication protocol supported by the smart watch to encapsulate according to the Socket communication trigger data to obtain a first data packet; sending the first data packet to the mobile end on the smart phone through short-range wireless communication with the smart phone, so that the mobile end parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with the corresponding server based on the data packet, and encapsulates the Socket communication response data returned by the server using the short-range wireless communication protocol to obtain a second data packet; receiving the second data packet returned from the mobile end through short-range wireless communication with the smart phone, and parsing the second data packet to obtain Socket communication response data.

[0007] One or more embodiments of the present specification provide a business processing device for a smart watch, which is applied to a watch end on the smart watch, and the device includes: a trigger data acquisition module, which acquires Socket communication trigger data; a trigger data encapsulation module, which uses the short-range wireless communication protocol supported by the smart watch to encapsulate according to the Socket communication trigger data to obtain a first data packet; a data packet sending module, which sends the first data packet to the mobile phone end on the smart phone through short-range wireless communication with the smart phone, so that the mobile phone end parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with the corresponding server end accordingly, and encapsulates the Socket communication response data returned by the server end using the short-range wireless communication protocol to obtain a second data packet; a response data acquisition module, which receives the second data packet returned from the mobile phone end through short-range wireless communication with the smart phone, and parses the second data packet to obtain Socket communication response data.

[0008] One or more embodiments of the present specification provide a business processing device for a smart watch, which is applied to a watch end on the smart watch, and the device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can: obtain Socket communication trigger data; use the short-range wireless communication protocol supported by the smart watch to encapsulate according to the Socket communication trigger data to obtain a first data packet; send the first data packet to the mobile phone end on the smart phone through short-range wireless communication with the smart phone, so that the mobile phone end parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with the corresponding server accordingly, and encapsulates the Socket communication response data returned by the server using the short-range wireless communication protocol to obtain a second data packet; receive the second data packet returned from the mobile phone end through short-range wireless communication with the smart phone, and parse the second data packet to obtain Socket communication response data.

[0009] One or more embodiments of the present specification provide a non-volatile computer storage medium, which is applied to a watch end on the smart watch, and the medium stores computer-executable instructions, and the computer-executable instructions are configured to: obtain Socket communication trigger data; utilize the short-range wireless communication protocol supported by the smart watch to encapsulate according to the Socket communication trigger data to obtain a first data packet; send the first data packet to a mobile phone end on the smart phone through short-range wireless communication with the smart phone, so that the mobile phone end parses the first data packet to obtain Socket communication trigger data, and thereby performs Socket communication with the corresponding server end, and encapsulates the Socket communication response data returned by the server end using the short-range wireless communication protocol to obtain a second data packet; receive the second data packet returned from the mobile phone end through short-range wireless communication with the smart phone, and parse the second data packet to obtain Socket communication response data.

[0010] At least one of the above-mentioned technical solutions adopted in one or more embodiments of this specification can achieve the following beneficial effects: adopting the Socket communication solution as the basic Internet communication protocol of the smart watch, using the smart phone near the smart watch as the agent, utilizing the short-range wireless communication capability (taking Bluetooth communication as an example) between the watch end and the mobile phone end, and the long-distance communication capability between the mobile phone end and the server end, based on the cooperation of the three parties, encapsulating, parsing and intermediately transmitting the Socket communication-related data involved in the watch end and the server end, indirectly realizing the Socket communication between the watch end on the smart watch and the server end, thereby enhancing the communication capability of the smart watch, enabling the watch end and the server end to flexibly exchange business data, and helping to improve the payment experience of smart watches with only Bluetooth communication modules. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of this specification, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0012] FIG1 is a flow chart of a service processing method for a smart watch provided in one or more embodiments of this specification.

[0013] FIG2 is a schematic diagram of a proxy link for completing Socket communication between a watch and a server using a mobile phone as a proxy in a scenario provided by one or more embodiments of this specification.

[0014] FIG3 is a flow chart illustrating a process of completing proxy link processing of a single Socket API in a scenario provided by one or more embodiments of this specification.

[0015] FIG4 is a schematic diagram of customizing parameters related to a Socket() function provided by one or more embodiments of this specification.

[0016] FIG5 is a flowchart of an additional task processing solution on a mobile phone involved in a watch proxy link in an application scenario provided by one or more embodiments of this specification.

[0017] FIG6 is a flowchart of a dynamic selection solution for a proxy mobile phone in an application scenario provided by one or more embodiments of this specification.

[0018] FIG7 is a schematic diagram of the structure of a service processing device for a smart watch provided by one or more embodiments of this specification.

[0019] FIG8 is a schematic structural diagram of a service processing device for a smart watch provided by one or more embodiments of this specification. DETAILED DESCRIPTION

[0020] The embodiments of this specification provide a service processing method, apparatus, device, and storage medium for a smart watch.

[0021] In order 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 in conjunction with the drawings in the embodiments of this specification. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0022] In order to improve the communication capabilities of smart watches, the applicant has made some attempts, such as maintaining communication with the help of the watch manufacturer's sports application keep-alive, and encapsulating HTTP protocol proxy communication on the mobile phone side. However, these attempts still have some problems. For example, the first attempt listed is still not flexible enough for the watch side. It can only receive messages and does not have the ability to actively obtain information. In addition, sports applications need to be kept alive to maintain real-time information transmission, and the resource cost is slightly high. The HTTP message format of the second attempt listed is unified and fixed, and the message is complicated and lengthy, which is not friendly to Bluetooth communication. In addition, HTTP protocol communication does not have the function of two-way communication.

[0023] In this application, the applicant proposed that the smart watch use the mobile phone as a proxy to complete Internet communication, and selected Socket communication as the basic Internet communication protocol for the smart watch.

[0024] Compared to the previously attempted HTTP communication, Socket communication is a lower-level, connection-oriented transport layer communication method. It typically establishes a connection via the TCP protocol (this method is primarily used as an example), but can also employ the connectionless UDP protocol. Socket communication does not stipulate a specific data format; the format and structure of data can be freely defined. Therefore, both communicating parties can negotiate and parse data independently. The overall protocol is simple, and the encapsulated content is concise, making the messages more suitable for Bluetooth communication. Furthermore, Socket communication enables direct data transmission once a connection is established, supporting bidirectional communication and enabling proactive information push during the connection, without the client having to send requests to the server each time.

[0025] Most RTOS smart watches cannot connect to the Internet directly, so they use their own existing Bluetooth-related protocols to encapsulate the parameters of Socket communication and then forward them to the mobile phone for analysis to complete the proxy Internet access.

[0026] Based on this general idea, the solution of this application will be described in detail below.

[0027] Figure 1 is a flowchart of a business processing method for smart watches provided by one or more embodiments of this specification. The process can be applied to the watch side of a smart watch, especially for smart watches that only support short-range wireless communication methods such as Bluetooth communication, but do not support network remote communication methods. The advantages are more obvious. The process uses the watch side as the execution subject. In addition, it also involves the mobile side on the smartphone and the server side on the server. The watch side and the mobile side can be the clients of the corresponding applications, or embedded applications (such as mini-programs) embedded in other application clients. In particular, the watch side can be more lightweight (simplified functions, etc.) compared to the mobile side.

[0028] The process in FIG1 includes steps S102 to S108 .

[0029] S102: Acquire Socket communication trigger data.

[0030] In one or more embodiments of this specification, Socket communication trigger data may include data required for indirect Socket communication between the watch and the server, using the phone as a proxy, primarily including Socket communication parameters. Socket communication trigger data can be used to trigger the establishment of a Socket communication connection, or, after the connection is established, to trigger an active request for server-side data based on the connection. In the absence of a connection, it can be used to trigger the active sending of data to the server.

[0031] In one or more embodiments of this specification, for example, a Socket API parameter structure may be pre-designed to trigger connection establishment. This structure may then be used to encapsulate Socket API parameters to obtain a Socket API structure object. This Socket API structure object is then serialized to obtain Socket communication trigger data. The Socket API is primarily represented by one or more functions, such as Socket(), Connect(), Send(), and Receive().

[0032] In different specific uses, you can flexibly customize appropriate Socket API parameters for the currently involved functions and assign values ​​accordingly.

[0033] S104: Using the short-range wireless communication protocol supported by the smart watch, encapsulate according to the socket communication trigger data to obtain a first data packet.

[0034] In one or more embodiments of this specification, the smartwatch does not support direct network remote communication, but only supports one or more short-range wireless communications. A typical example is the case where only Bluetooth communication is supported as mentioned in the background technology. In this case, the short-range wireless communication protocol supported by the smartwatch can be the Bluetooth protocol or the Bluetooth Low Energy (BLE) protocol, preferably the BLE protocol, which is more friendly to the solution of this application and helps to ensure the battery life of the smartwatch.

[0035] The smartwatch uses a nearby smartphone (e.g., the smartphone held by the user wearing the smartwatch) as a proxy, and needs to transmit the Socket communication trigger data to the smartphone. The smartwatch is capable of short-range wireless communication with the smartphone, so the Socket communication trigger data is packaged accordingly to meet the needs of short-range wireless communication data transmission. For example, the watch can use the BLE protocol to sub-packetize and encapsulate the Socket communication trigger data to obtain multiple data packets. For ease of distinction, such data packets are referred to as first data packets.

[0036] S106: By performing short-range wireless communication with a smartphone, the first data packet is sent to the mobile terminal on the smartphone, so that the mobile terminal parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with the corresponding server accordingly, and encapsulates the Socket communication response data returned by the server using the short-range wireless communication protocol to obtain a second data packet.

[0037] In one or more embodiments of this specification, the watch side and the mobile phone side may belong to the same application or different applications. In the latter case, authorization between the applications may be performed in advance to enable normal interaction.

[0038] The mobile phone uses the above-mentioned short-range wireless communication protocol to parse the first data packet, and can at least completely obtain the Socket communication trigger data previously encapsulated by the watch side (called original data for distinction). The mobile phone can directly perform Socket communication with the corresponding server based on the original data, or the mobile phone can perform more complex processing on the original data as needed to obtain different new data, and use the new data as the obtained Socket communication trigger data, and perform Socket communication with the corresponding server accordingly.

[0039] In one or more embodiments of this specification, the watch end and the corresponding server end may belong to the same application or different applications with a cooperative relationship.

[0040] In the payment scenario mentioned in the background technology, the watch side and the server side are payment applications or payment channel applications. The payment application is, for example, a third-party payment application, and the payment channel application is, for example, the application of a bank that the third-party payment application cooperates with. When making a third-party payment, the payment can be completed by deducting the money from the bank card issued by the bank. The watch side and the server side may belong to the same third-party payment application; or the watch side may belong to the third-party payment application, and the server side may belong to the application of a cooperating bank; and so on.

[0041] In one or more embodiments of this specification, the server's response depends on the purpose of the Socket communication trigger data. If the mobile phone and server have not yet responded to establish a connection, a connection can be established based on the Socket communication trigger data. If a connection has already been established, the server can perform corresponding business processing based on the business involved in the Socket communication trigger data, obtain the business processing results, and return them to the mobile phone via the connection in the form of Socket communication response data.

[0042] S108: Receive the second data packet returned from the mobile phone through short-range wireless communication with the smart phone, and parse the second data packet to obtain Socket communication response data.

[0043] In one or more embodiments of this specification, after the mobile phone side obtains the Socket communication response data returned by the server side, similarly, the Socket communication response data can be completely encapsulated and further returned to the watch side, or more complex processing can be performed to encapsulate data that is not exactly the same as the original response data and return it to the watch side. Of course, no matter which method is used, it is sufficient to ensure that the Socket communication response data obtained by the watch side based on parsing the second data packet is sufficient to meet the business needs of the watch side this time. The latter more complex processing method can also help the mobile phone side to meet its own business needs in addition, which will be explained with examples later.

[0044] Based on this short-range communication process and the Socket communication process indirectly completed through the proxy, in the payment scenario, even for a smart watch with only a Bluetooth communication module, the watch end is able to conveniently and promptly obtain payment result details from the payment server end and display them to the user.

[0045] Through the method of Figure 1, the Socket communication solution is adopted as the basic Internet communication protocol of the smart watch, and the smart phone near the smart watch is used as the agent. The short-range wireless communication capability (taking Bluetooth communication as an example) between the watch end and the mobile phone end, as well as the long-distance communication capability between the mobile phone end and the server end are utilized. Based on the cooperation of the three parties, the Socket communication-related data involved in the watch end and the server end are encapsulated, parsed and intermediately transmitted, and the Socket communication between the watch end on the smart watch and the server end is indirectly realized, thereby enhancing the communication capability of the smart watch, enabling the watch end and the server end to flexibly exchange business data, which helps to improve the payment experience of the smart watch with only a Bluetooth communication module.

[0046] Based on the method of FIG1 , this specification also provides some specific implementation plans and extension plans of the method, which will be described below.

[0047] In one or more embodiments of this specification, the watch side can actively obtain information from the server side by actively triggering and returning a response. Similarly, the watch side can also actively send information to the server side in this way. Of course, two-way communication can also be achieved based on Socket communication, and the watch side does not necessarily need to actively initiate the interaction.

[0048] The designated connection used for the aforementioned Socket communication between the phone and the server, acting as a proxy, is called a watch proxy connection. As previously explained, this watch proxy connection is triggered by near-field wireless communication between the watch and phone. Once the watch proxy connection is established, the phone can passively receive information sent by the phone and pushed by the server via the watch proxy connection, without actively requesting the server. Instead, it can communicate with the smartphone through near-field wireless communication, passively receiving information sent by the phone and pushed by the server via the watch proxy connection.

[0049] For example, watch payment can be made through the watch end, which can be completed through QR code scanning interaction or near-field wireless communication between the smartphone and the target cash register device. After the deduction is successful, the server actively pushes the payment result details corresponding to the watch payment through the watch proxy connection, and the mobile phone end on the smartphone sends the payment result details to the watch end through near-field wireless communication. The payment result details may include the actual payment amount and / or the account balance after payment, so that the user can understand the changes involved in the payment more clearly.

[0050] As can be seen from the previous description, this application provides a proxy link that uses the mobile phone as a proxy to complete Socket communication between the watch and the server. For a more intuitive example, see Figure 2. Figure 2 is a schematic diagram of this proxy link in a scenario provided by one or more embodiments of this specification. In this scenario, the server is specifically a payment server, and the smart watch may only have a Bluetooth communication module. Its watch end is referred to as the Bluetooth smart watch end.

[0051] In the link shown in Figure 2, the Bluetooth smartwatch and phone communicate using the BLE protocol. The phone, acting as a proxy for the Bluetooth smartwatch, communicates with the server using TCP-based sockets. This intuitively illustrates the design of a logical link for converting network protocols (e.g., TCP / IP) to Bluetooth-related protocols (e.g., Bluetooth / BLE).

[0052] This link shows the protocol hierarchy position and purpose of each function involved in Socket communication on each end. In this link, the spatial dimension shows the flow of data between the three ends based on different protocols, and the temporal dimension shows the establishment of a Socket communication connection. Then, based on the connection, data continues to be exchanged by sending requests and returning responses, and the connection can be closed as needed. For example, for the Bluetooth smart watch and mobile phone, in the stage of establishing the Socket communication connection, functions such as Socket() and Connect() may be involved, and in the subsequent stages, functions such as Send(), Receive(), and Close() may be involved; for the payment service end, in the stage of establishing the Socket communication connection, functions such as Socket(), Bind(), Listen(), and Accept() may be involved, and in the subsequent stages, functions such as Receive(), Send(), and Close() may be involved.

[0053] One or more embodiments of this specification also provide a flow chart of completing proxy link processing of a single Socket API in one scenario, see Figure 3, which can be understood in combination with the previous description and the following examples, and some contents will not be repeated here.

[0054] The process in Figure 3 mainly includes the serialization and deserialization of socket parameters, sub-packaging and assembly based on BLE protocol encapsulation, etc. Intuitively, taking a specific customized socket() function as an example, Figure 4 shows the definition of the relevant parameters of the socket() function.

[0055] In Figure 4, three parameter fields are defined for the socket() function, including a 4-byte "domain" (indicating the protocol domain) field, an 8-byte "type" (indicating the socket type) field, and a 4-byte "protocol" (indicating the transmission protocol) field. In addition, a data structure "RetSocket" is defined to return response data to the watch.

[0056] Based on these definitions, the socket() function used in the process of Figure 3 is defined as follows:

[0057] "int socket(int domain,int type,int protocol)".

[0058] The process specifically includes the following steps: Taking the socket() function as an example, the first step to open a communication connection is that the watch, as the client, needs to send basic information such as the protocol domain, socket type, and transmission protocol to the server. The server creates a socket object based on the parameter information provided by the watch, establishing a communication infrastructure for both parties. Therefore, the parameter information of the socket() function needs to be correctly transmitted across platforms to the mobile phone, which then initiates a connection to the server. The mobile phone then transmits the result of the socket() function call across platforms to the watch, thus completing a complete data transmission process.

[0059] Available serialization protocols include Protocol Buffers, JSON, and Thrift. For example, Protocol Buffers is an efficient binary serialization protocol that provides a convenient way to serialize and deserialize structured data. Its design goal is to enable error-free data transmission across different platforms and languages. Using this protocol, complex data structures can be converted into a compact and efficient binary format, enabling efficient data transmission and storage.

[0060] Based on this, an exemplary serialization and deserialization process is as follows.

[0061] 1. On the watch, complete the following steps: First, define the message structure and field Socket, and compile to generate code in the target language. Then, use the generated class or structure to set the message field values. Once the message field values ​​are set, call the serialization method to convert the message data into binary format. This allows the data to be transmitted and stored in binary format between different platforms.

[0062] 2. Using the BLE protocol on the watch, the serialized binary data is packetized and sent to the phone. After the phone reassembles the data, it deserializes it back into a message object. The deserialization process converts the binary data into a message object with corresponding field values ​​based on the message structure Socket and field order defined on the watch. The socket() function is then called on the watch to send the request to the server.

[0063] 3. After receiving the socket request from the watch, the server performs a series of processing and returns the result to the phone. The phone then sets the result into the defined data structure RetSocket; then serializes the data and sends it to the watch through the BLE protocol.

[0064] 4. The watch side parses the result according to the defined data structure RetSocket. At this point, the watch side has completed the first step of Socket communication and can proceed to establish subsequent connections.

[0065] The use of other functions involved later can also be handled in a similar way.

[0066] Through the schemes of Figures 2 and 3, it is possible to establish BLE Internet access specifications and improve the process system for Bluetooth watches, thereby improving the user experience. By adopting the Socket communication scheme as the basic Internet communication protocol for smart watches, the communicating parties can negotiate and parse data on their own. The overall protocol is simple and the encapsulated content is concise. Moreover, Socket communication can directly transmit data after the two parties establish a connection. When connected, information can also be actively pushed without the need for the watch to send a request to the server each time. Therefore, it can solve the problems of the background technology and the above-mentioned experimental schemes.

[0067] In one or more embodiments of this specification, the mobile phone needs to pay additional processing resources as an agent. In order to make full use of these processing resources, the mobile phone can use its own communication needs with the server to complete the agent work. In this case, the mobile phone has more active control rights and avoids bringing additional burden to itself. Not only that, the watch also has more choices for the mobile phone on the smartphone, which helps to optimize the allocation of global resources.

[0068] Based on this idea, the mobile phone is considering not simply forwarding the data from the other two ends during the proxy process as is, but performing the more complex processing mentioned above on this data to achieve its own original communication needs. Specifically, one or more embodiments of this specification provide a flowchart of the additional task processing scheme on the mobile phone involved in the watch proxy link in an application scenario, see Figure 5.

[0069] The process in FIG5 includes steps S502 to S508.

[0070] S502: The watch side sends the first data packet indicating the first business task of the watch side to the mobile phone side on the smart phone.

[0071] The first business task is the business task that the watch side currently needs to complete, such as establishing a connection with the server side and transmitting corresponding business data (such as payment business data, etc.) based on the connection.

[0072] S504: The mobile phone parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with the corresponding server according to the Socket communication trigger data and the data indicating the second business task of the mobile phone.

[0073] In one or more embodiments of this specification, the second business task is a business task on the mobile phone itself, which may be unrelated to the watch and may not be directly related to the first business task. The first and second business tasks may belong to different services (for example, the first business task may belong to the payment service, the second business task may belong to the instant messaging service, etc.), and the watch and mobile phone may even belong to different applications. In short, even if the second business task is not executed, the first business task can still be executed normally based on the proxy link described above, completing the above-mentioned socket communication.

[0074] In this case, the purpose of the mobile phone is actually to complete its second business task, and by the way, act as an agent to help the watch side complete its first business task.

[0075] S506: The mobile phone receives the Socket communication response data returned by the server, wherein the Socket communication response data includes first task result data obtained by the server executing the first business task and second task result data obtained by executing the second business task.

[0076] In one or more embodiments of this specification, the server is responsible for executing these two types of tasks, and there is no need to clearly distinguish which end specifically needs these two types of tasks. Therefore, the task result data of these two types of tasks can be uniformly placed in the Socket communication response data and returned to the mobile phone end through a message (i.e., Socket communication response data).

[0077] S508: After intercepting the second task result data from the Socket communication response data, the mobile phone encapsulates the second data packet and returns it to the watch, so that the watch obtains the remaining first task result data.

[0078] For the mobile phone side, it is mainly necessary to obtain the second task result data in the Socket communication response data, and this part of the data is preferably not exposed to the watch side, especially when the two ends do not belong to the same application. Similarly, the watch side can also ensure, based on a predetermined security policy, that although the first business task and / or the first task result data need to be transmitted through the watch side, the corresponding plaintext will not be exposed to the watch side. Based on this, the mobile phone side can intercept the second task result data from the Socket communication response data, and encapsulate the remaining data after interception to obtain a second data packet and return it to the watch side, so that the watch side can obtain the first task result data without obtaining the second task result data.

[0079] In some embodiments, to enable more timely response to the watch terminal, the watch terminal that is currently more suitable as a proxy can be dynamically selected from these watch terminals based on the dynamic task requirements of different watch terminals on the smartphone. Based on this, one or more embodiments of this specification also provide a flow diagram of a dynamic proxy mobile terminal selection scheme in an application scenario, see Figure 6.

[0080] The process in FIG6 includes steps S602 to S608.

[0081] S602: The watch receives asynchronous communication demand information sent by the smartphone via near-field wireless communication, where the asynchronous communication demand information reflects the asynchronous communication currently being performed or the predicted asynchronous communication to be performed between the corresponding smartphone and the server.

[0082] In one or more embodiments of this specification, at least one of multiple different mobile terminals on a smartphone that currently has a business task that can be deferred (meaning, can be executed after the current time) can be identified as the target mobile terminal. In this case, the deferred business task can be determined as the aforementioned second business task. This can motivate the target mobile terminal to accept the proxy identity while also expediting the execution of the deferred business task.

[0083] S604: The watch terminal determines a target mobile terminal from a plurality of different mobile terminals corresponding to the smart phone according to the received asynchronous communication demand information.

[0084] This process uses asynchronous communication as an example. The business tasks executed via asynchronous communication are considered deferred. It should be noted that other scenarios may also include deferred business tasks, such as scheduled tasks or polling tasks that have not yet been executed. Similar methods can be used to determine the target mobile device.

[0085] S606: The watch sends the first data packet to the target mobile phone on the smart phone by performing short-range wireless communication with the smart phone.

[0086] S608: The target mobile phone determines the service task of the target mobile phone corresponding to the asynchronous communication requirement information as the second service task.

[0087] The target mobile phone can use its own business task that can be delayed as the second business task.

[0088] Through the solutions of Figures 5 and 6, the cooperation value between the watch and the mobile phone is further enhanced, and from a global perspective, it helps to improve task execution efficiency and resource utilization.

[0089] Based on the same idea, one or more embodiments of this specification also provide apparatuses and devices corresponding to the above method, as shown in Figures 7 and 8. The apparatuses and devices can execute the above method and related optional solutions accordingly.

[0090] Figure 7 is a structural diagram of a business processing device for a smart watch provided by one or more embodiments of this specification, which is applied to the watch end of the smart watch, and the device includes: a trigger data acquisition module 702, which acquires Socket communication trigger data; a trigger data encapsulation module 704, which uses the short-range wireless communication protocol supported by the smart watch to encapsulate according to the Socket communication trigger data to obtain a first data packet; a data packet sending module 706, which sends the first data packet to the mobile phone end on the smart phone through short-range wireless communication with the smart phone, so that the mobile phone end parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with the corresponding server end accordingly, and encapsulates the Socket communication response data returned by the server end using the short-range wireless communication protocol to obtain a second data packet; a response data acquisition module 708, which receives the second data packet returned from the mobile phone end through short-range wireless communication with the smart phone, and parses the second data packet to obtain Socket communication response data.

[0091] In some embodiments, the trigger data acquisition module 702 encapsulates Socket API parameters according to a pre-designed Socket API parameter structure to obtain a Socket API structure object; and obtains Socket communication trigger data by serializing the Socket API structure object.

[0092] In some embodiments, the trigger data encapsulation module 704 encapsulates the Socket communication trigger data into packets to obtain multiple first data packets, so that after the mobile phone obtains the multiple first data packets, it can assemble and parse the packets accordingly to obtain the Socket communication trigger data.

[0093] In some embodiments, after the designated watch proxy connection is established between the mobile phone and the server, the response data acquisition module 708 receives information sent by the mobile phone and actively pushed by the server through the watch proxy connection through short-range wireless communication with the smart phone; wherein, the watch proxy connection is triggered and established based on the short-range wireless communication between the watch and the mobile phone.

[0094] In some embodiments, the watch end and the server end belong to payment applications or payment channel applications; the device also includes: a watch end payment module 710, which performs watch payment through the watch end before receiving the information sent by the mobile phone end and actively pushed by the server end through the watch proxy connection. The watch payment is completed through QR code scanning interaction or short-range wireless communication between the smartphone and the target cash register device; the response data acquisition module 708 receives the payment result details corresponding to the watch payment sent by the mobile phone end and actively pushed by the server end through the watch proxy connection. The payment result details include at least the actual payment amount and the account balance after payment.

[0095] In some embodiments, the data packet sending module 706 sends the first data packet indicating the first business task of the watch end to the mobile phone end on the smart phone, so that the mobile phone end parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with the corresponding server end based on the Socket communication trigger data and the data indicating the second business task of the mobile phone end; wherein, the second data packet is obtained by the mobile phone end after intercepting the second task result data obtained by the server end executing the second business task from the Socket communication response data and encapsulating it, so that the watch end obtains the remaining first task result data obtained by the server end executing the first business task.

[0096] In some embodiments, the watch end and the mobile phone end belong to different applications, or the first business task and the second business task belong to different businesses.

[0097] In some embodiments, the data packet sending module 706 determines at least one of the multiple different mobile terminals on the smartphone that currently has a business task that can be delayed as the target mobile terminal; and sends the first data packet to the target mobile terminal on the smartphone through short-range wireless communication with the smartphone, so that the target mobile terminal uses the business task that can be delayed as the second business task.

[0098] In some embodiments, the data packet sending module 706 receives asynchronous communication demand information sent by a smartphone via near-field wireless communication, wherein the asynchronous communication demand information reflects the asynchronous communication currently being executed or the predicted asynchronous communication to be executed between the corresponding mobile terminal on the smartphone and the server terminal; and based on the received asynchronous communication demand information, the target mobile terminal is determined among the multiple different mobile terminals corresponding to the smartphone.

[0099] In some embodiments, the short-range wireless communication protocol is a Bluetooth protocol or a BLE protocol.

[0100] Figure 8 is a structural diagram of a business processing device for a smart watch provided by one or more embodiments of this specification, which is applied to the watch end of the smart watch, and the device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can: obtain Socket communication trigger data; use the short-range wireless communication protocol supported by the smart watch to encapsulate according to the Socket communication trigger data to obtain a first data packet; send the first data packet to the mobile phone end on the smart phone through short-range wireless communication with the smart phone, so that the mobile phone end parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with the corresponding server accordingly, and encapsulates the Socket communication response data returned by the server using the short-range wireless communication protocol to obtain a second data packet; receive the second data packet returned from the mobile phone end through short-range wireless communication with the smart phone, and parse the second data packet to obtain Socket communication response data.

[0101] Based on the same idea, one or more embodiments of this specification also provide a non-volatile computer storage medium, which is applied to the watch end on the smart watch, and the medium stores computer executable instructions, and the computer executable instructions are set to: obtain Socket communication trigger data; use the short-range wireless communication protocol supported by the smart watch to encapsulate according to the Socket communication trigger data to obtain a first data packet; send the first data packet to the mobile phone end on the smart phone through short-range wireless communication with the smart phone, so that the mobile phone end parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with the corresponding server end accordingly, and uses the short-range wireless communication protocol to encapsulate the Socket communication response data returned by the server to obtain a second data packet; receive the second data packet returned from the mobile phone end through short-range wireless communication with the smart phone, and parse the second data packet to obtain Socket communication response data.

[0102] In the 1990s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly done using "logic compiler" software. This is similar to the software compiler used when developing programs. Before compilation, the original code must also be written in a specific programming language, called a hardware description language (HDL). There is not just one HDL, but many, 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, RHDL (Ruby Hardware Description Language), etc. The most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that by simply programming the method flow in one of these hardware description languages ​​and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

[0103] The controller can be implemented in any suitable manner. For example, the controller 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 Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that in addition to implementing the controller in a purely computer-readable program code format, the controller can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules that implement the method and structures within the hardware component.

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

[0105] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0106] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0107] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0108] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0109] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

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

[0111] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0112] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules 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 technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0113] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0114] This specification may be described in the general context of computer-executable instructions, such as program modules, executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media, including storage devices.

[0115] The various embodiments in this specification are described in a progressive manner. Similar portions between the various embodiments can be referenced to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the device, apparatus, and non-volatile computer storage medium embodiments are generally similar to the method embodiments, so their descriptions are relatively simplified. For relevant details, refer to the descriptions of the method embodiments.

[0116] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0117] The foregoing is one or more embodiments of this specification and is not intended to limit this specification. It will be apparent to those skilled in the art that various modifications and variations may be made to one or more embodiments of this specification. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of one or more embodiments of this specification are intended to be within the scope of the claims of this specification.

Claims

1. A service processing method for a smart watch, applied to a watch end on the smart watch, the method comprising: Get Socket communication trigger data; Using the short-range wireless communication protocol supported by the smart watch, encapsulating according to the Socket communication trigger data to obtain a first data packet; By performing short-distance wireless communication with a smart phone, the first data packet is sent to a mobile terminal on the smart phone, so that the mobile terminal parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with a corresponding server based on the data packet, and encapsulates the Socket communication response data returned by the server using the short-distance wireless communication protocol to obtain a second data packet; The second data packet returned from the mobile phone through short-range wireless communication with the smart phone is received, and the second data packet is parsed to obtain Socket communication response data.

2. The method of claim 1, wherein: The obtaining of Socket communication trigger data includes: Encapsulate the Socket API parameters according to the pre-designed Socket API parameter structure to obtain the Socket API structure object; Socket communication trigger data is obtained by serializing the Socket API structure object.

3. The method of claim 1, wherein: The step of encapsulating the Socket communication trigger data to obtain a first data packet includes: The Socket communication trigger data is sub-packetized and encapsulated to obtain a plurality of first data packets, so that after the mobile phone end obtains the plurality of first data packets, it can assemble and parse the packets accordingly to obtain the Socket communication trigger data.

4. The method of claim 1, further comprising: After the designated watch proxy connection between the mobile phone and the server is established, the mobile phone receives information actively pushed by the server through the watch proxy connection by performing short-range wireless communication with the smart phone; The watch proxy connection is triggered and established based on the short-range wireless communication between the watch and the mobile phone.

5. The method of claim 4, wherein: The watch end and the server end are payment applications or payment channel applications; Before receiving the information sent by the mobile phone and actively pushed by the server through the watch proxy connection, the method further includes: Performing watch payment through the watch terminal, wherein the watch payment is completed through QR code scanning interaction or short-range wireless communication between the smart phone and the target cash register device; The receiving of information sent by the mobile phone and actively pushed by the server through the watch proxy connection includes: Receive payment result detail information corresponding to the watch payment sent by the mobile phone and actively pushed by the server through the watch proxy connection, wherein the payment result detail information at least includes the actual payment amount and the account balance after payment.

6. The method of claim 1, wherein: The sending the first data packet to the mobile terminal on the smart phone includes: Sending the first data packet indicating the first business task of the watch end to the mobile end on the smart phone, so that the mobile end parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with the corresponding server end according to the Socket communication trigger data and the data indicating the second business task of the mobile end; Among them, the second data packet is obtained by the mobile phone end packaging the second task result data obtained by the server end executing the second business task from the Socket communication response data, so that the watch end obtains the remaining first task result data obtained by the server end executing the first business task.

7. The method of claim 6, wherein: The watch end and the mobile phone end belong to different applications respectively, or the first business task and the second business task belong to different businesses.

8. The method of claim 6, wherein: The step of sending the first data packet to a mobile terminal on the smart phone by performing short-range wireless communication with the smart phone comprises: Determine at least one mobile terminal among a plurality of different mobile terminals on the smart phone that currently has a business task that can be executed deferred, as a target mobile terminal; The first data packet is sent to the target mobile terminal on the smart phone by performing short-range wireless communication with the smart phone, so that the target mobile terminal uses the business task that can be deferred as the second business task.

9. The method of claim 8, wherein: The step of determining at least one mobile terminal among the multiple different mobile terminals on the smart phone that currently has a business task that can be executed deferred as the target mobile terminal includes: Receiving asynchronous communication demand information sent by a smart phone through short-range wireless communication, wherein the asynchronous communication demand information reflects asynchronous communication currently being performed or asynchronous communication predicted to be performed between a corresponding mobile phone end on the smart phone and the server end; According to each of the received asynchronous communication demand information, a target mobile terminal is determined from a plurality of different mobile terminals corresponding to the smart phone.

10. The method according to any one of claims 1 to 9, wherein: The short-range wireless communication protocol is a Bluetooth protocol or a Bluetooth low energy protocol.

11. A service processing device for a smart watch, applied to a watch end on the smart watch, the device comprising: Trigger data acquisition module to obtain Socket communication trigger data; A trigger data encapsulation module is used to encapsulate the Socket communication trigger data using the short-range wireless communication protocol supported by the smart watch to obtain a first data packet; The data packet sending module sends the first data packet to the mobile terminal on the smart phone by performing short-distance wireless communication with the smart phone, so that the mobile terminal parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with the corresponding server accordingly, and obtains a second data packet by encapsulating the Socket communication response data returned by the server using the short-distance wireless communication protocol; The response data acquisition module receives the second data packet returned from the mobile phone through short-range wireless communication with the smart phone, and parses the second data packet to obtain Socket communication response data.

12. The device of claim 11, wherein: The trigger data acquisition module encapsulates the Socket API parameters according to the pre-designed Socket API parameter structure to obtain the Socket API structure object; Socket communication trigger data is obtained by serializing the Socket API structure object.

13. The device of claim 11, wherein: The trigger data encapsulation module encapsulates the Socket communication trigger data into packets to obtain a plurality of first data packets, so that after obtaining the plurality of first data packets, the mobile phone terminal can assemble and parse the packets accordingly to obtain the Socket communication trigger data.

14. The device of claim 11, wherein: The response data acquisition module receives information sent by the mobile phone terminal and actively pushed by the server terminal through the watch proxy connection by performing short-range wireless communication with the smart phone after the designated watch proxy connection between the mobile phone terminal and the server terminal is established; The watch proxy connection is triggered and established based on the short-range wireless communication between the watch and the mobile phone.

15. The device of claim 14, wherein: The watch end and the server end are payment applications or payment channel applications; The device also includes: A watch-side payment module, before receiving the information sent by the mobile phone and actively pushed by the server through the watch proxy connection, performs watch payment through the watch side, wherein the watch payment is completed through QR code scanning interaction or short-range wireless communication between the smart phone and the target cash register device; The response data acquisition module receives payment result details corresponding to the watch payment sent by the mobile phone and actively pushed by the server through the watch proxy connection, and the payment result details at least include the actual payment amount and the account balance after payment.

16. The device of claim 11, wherein: The data packet sending module sends the first data packet indicating the first business task of the watch end to the mobile end on the smart phone, so that the mobile end parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with the corresponding server according to the Socket communication trigger data and the data indicating the second business task of the mobile end; Among them, the second data packet is obtained by the mobile phone end packaging the second task result data obtained by the server end executing the second business task from the Socket communication response data, so that the watch end obtains the remaining first task result data obtained by the server end executing the first business task.

17. The device of claim 16, wherein: The watch end and the mobile phone end belong to different applications respectively, or the first business task and the second business task belong to different businesses.

18. The device of claim 16, wherein: The data packet sending module determines at least one mobile terminal among the multiple different mobile terminals on the smart phone that currently has a business task that can be executed deferred as the target mobile terminal; By performing short-range wireless communication with a smart phone, the first data packet is sent to the target mobile terminal on the smart phone, so that the target mobile terminal uses the deferred execution business task as the second business task. Task.

19. The device of claim 18, wherein: The data packet sending module receives asynchronous communication demand information sent by the smart phone through short-range wireless communication, wherein the asynchronous communication demand information reflects the asynchronous communication currently being performed or the asynchronous communication predicted to be performed between the corresponding mobile phone end on the smart phone and the server end; According to each of the received asynchronous communication demand information, a target mobile terminal is determined from a plurality of different mobile terminals corresponding to the smart phone.

20. The device according to any one of claims 11 to 19, wherein: The short-range wireless communication protocol is a Bluetooth protocol or a Bluetooth low energy protocol.

21. A service processing device for a smart watch, applied to a watch end on the smart watch, the device comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute: Get Socket communication trigger data; Using the short-range wireless communication protocol supported by the smart watch, encapsulating according to the Socket communication trigger data to obtain a first data packet; By performing short-distance wireless communication with a smart phone, the first data packet is sent to a mobile terminal on the smart phone, so that the mobile terminal parses the first data packet to obtain Socket communication trigger data, and performs Socket communication with a corresponding server based on the data packet, and encapsulates the Socket communication response data returned by the server using the short-distance wireless communication protocol to obtain a second data packet; The second data packet returned from the mobile phone through short-range wireless communication with the smart phone is received, and the second data packet is parsed to obtain Socket communication response data.

Images