Dynamic binding method and system, electronic equipment and storage medium
By downloading and dynamically loading the SDK resource package from the cloud server, the wearable device realizes the support of multiple application functions, solving the problems of memory limitations and resource waste, and improving the device's function expansion capabilities.
Patent Information
- Application Number
- CN202310541141.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2043-05-12
AI Technical Summary
Wearable devices such as smart watches and sports bracelets cannot support the installation of third-party applications due to limited memory resources, and the pre-installed SDK will occupy a large amount of memory resources, resulting in limited application number and waste of storage resources.
By downloading matching SDK resource packages from cloud servers with terminal devices such as mobile phones, dynamically loading the required SDK to memory based on the user's selection, and binding and use preset standard applications to achieve support for multiple application functions without taking up any use Too much memory space.
It effectively increases the number of applications supported by wearable devices, optimizes the utilization of memory resources, avoids the waste of storage resources caused by SDK presets, and achieves flexible functional expansion.
Smart Images

Figure CN118939333A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a dynamic binding method, system, electronic device and storage medium. Background Art
[0002] At present, the functions of wearable devices (smart watches, sports bracelets, etc.) are gradually increasing, involving multiple areas of life. For example, after binding with users, some wearable devices can perform access control recognition or scan code payment, making users' lives more convenient.
[0003] However, due to the limitations of their own hardware and software, wearable devices cannot support the installation of third-party applications in the application market. To use an application, the software development kit (SDK) of the application must be loaded into the memory of the wearable device in advance. The memory resources of wearable devices are small and cannot pre-install a large number of SDKs, which limits the number of applications supported by wearable devices. In addition, the pre-installed SDK will always exist in the memory. Even if some applications are not used for a long time, the corresponding SDK will occupy memory, wasting storage resources. Summary of the invention
[0004] The embodiment of the present application provides a dynamic binding method, system, electronic device and storage medium. The wearable device downloads the SDK resource package matching the SDK configuration information from the cloud server through a terminal such as a mobile phone. Based on the user's selection, the selected SDK is loaded into the memory through a standard application, and the SDK is called through the standard application to complete the binding and subsequent normal use. By loading different SDKs into the memory based on different SDK configuration information, the functions of multiple applications can be realized through one standard application, and the memory space will not be occupied too much due to pre-installing multiple SDKs in the memory.
[0005] In a first aspect, an embodiment of the present application provides a dynamic binding system, the system comprising a first terminal device, a second terminal device and a cloud server; the second terminal device is used to send software development tool SDK configuration information to the cloud server; the cloud server is used to filter out SDK resource packages associated with the SDK configuration information from pre-stored SDK resource packages, and send the filtered SDK resource packages to the second terminal device; the second terminal device is also used to send the SDK resource packages sent by the cloud server to the first terminal device; the first terminal device is used to store the SDK resource packages sent by the second terminal device in a memory, and in response to a user's selection operation on the SDK resource package in the memory, load the SDK in the SDK resource package selected by the user into the memory through a preset standard application; wherein each SDK resource package and standard application are developed based on a pre-defined unified standard to ensure that the standard application can successfully call the SDK loaded into the memory for binding and use.
[0006] In one embodiment, the second terminal device is specifically used to send software development tool SDK configuration information to the cloud server when or after a connection is established between the first terminal device and the second terminal device.
[0007] In one embodiment, the second terminal device is specifically used to send software development tool SDK configuration information to the cloud server after a connection is established between the first terminal device and the second terminal device, if it is the first time that the first terminal device establishes a connection with the second terminal device, or the current region information of the second terminal has changed compared to the region information when the second terminal last established a connection with the first terminal device; the SDK configuration information includes region information.
[0008] In one embodiment, the first terminal device is further used to send device information to the second terminal device after establishing a connection with the second terminal device; the SDK configuration information also includes the device information of the first terminal device.
[0009] In the second aspect, an embodiment of the present application provides a dynamic binding method, which is applied to a first terminal device, and the method includes: loading the SDK in the SDK resource package selected by the user into the memory through a preset standard application, and displaying the icon corresponding to the SDK loaded into the memory on the main interface through the preset standard application; when any icon in the main interface is selected, calling the SDK associated with the selected icon through the preset standard application to execute the binding process; wherein, each SDK resource package and standard application are developed based on a predefined unified standard to ensure that the standard application can successfully call the SDK loaded into the memory for binding and use.
[0010] In one embodiment, before loading the SDK in the SDK resource package selected by the user into the memory through a preset standard application, it also includes: displaying the SDK configuration interface, the SDK configuration interface having options corresponding to each SDK resource package, each option having information associated with the SDK; loading the SDK in the SDK resource package selected by the user into the memory through the preset standard application includes: loading the SDK in the SDK resource package corresponding to the option selected by the user in the SDK configuration interface into the memory through the preset standard application.
[0011] In one embodiment, before displaying the SDK configuration interface, it also includes: receiving a software development tool SDK resource package sent by a second terminal device and storing the SDK resource package in a memory; parsing each SDK resource package stored in the memory through a preset standard application to obtain the SDK in each SDK resource package and information associated with the SDK.
[0012] In one embodiment, the SDK in the SDK resource package corresponding to the option selected by the user in the SDK configuration interface is loaded into the memory through a preset standard application, including: loading the SDK in each SDK resource package corresponding to one or more options selected by the user in the SDK configuration interface into the memory through a preset standard application; displaying the icons corresponding to the SDK loaded into the memory on the main interface through the preset standard application, including: displaying the icons corresponding to each SDK loaded into the memory on the main interface through the preset standard application.
[0013] In one embodiment, the above information includes at least one or any combination of the following: icon; SDK name; storage space occupied by the SDK.
[0014] In one embodiment, after the binding process is completed, the method further includes: when any icon in the main interface is selected, calling the SDK corresponding to the selected icon through a standard application to execute the use process.
[0015] In one embodiment, after the binding process is completed, the method further includes: receiving an SDK unbinding request sent by the second terminal device; and unbinding the corresponding SDK and deleting it from the memory according to the SDK unbinding request.
[0016] In one embodiment, before receiving a software development kit SDK sent by a second terminal device and storing the SDK in a memory, the method also includes: if it is detected that the second terminal device is different from the device connected last time, executing an SDK initialization process, the SDK initialization process is used to delete the original SDK in the memory and delete the original SDK resource package in the memory.
[0017] In one embodiment, the method further includes: in response to a user's unbinding operation on a bound SDK, sending an unbinding instruction to the second terminal device, deleting the corresponding SDK from the memory, and deleting the corresponding icon from the main interface.
[0018] In a third aspect, an embodiment of the present application provides a dynamic binding method, which is applied to a second terminal device, including: after establishing a connection with the first terminal device, determining the SDK configuration information; sending the SDK configuration information to a cloud server, so that the cloud server determines the SDK resource package associated with the first terminal device based on the SDK configuration information; receiving the SDK resource package sent by the cloud server; sending at least part of the SDK resource package to the first terminal device, so that the first terminal device obtains the SDK from the SDK resource package, loads it into the memory, and completes the binding process by calling the SDK through a preset standard application.
[0019] In one embodiment, the SDK configuration information includes at least device information and region information of the first terminal device; determining the SDK configuration information includes: obtaining the device information of the first terminal device; obtaining the current IP address of the second terminal device, and determining the region information based on the IP address.
[0020] In one embodiment, sending at least part of the SDK resource package to the first terminal device includes: sending at least part of the SDK resource package selected by the user from the SDK resource package received from the cloud server to the first terminal device.
[0021] In one embodiment, the method further includes: upon detecting that an unbinding operation is performed on any successfully bound SDK, sending an SDK unbinding request to the first terminal device so that the first terminal device unbinds the SDK bound to the terminal application and deletes it from the memory.
[0022] In a fourth aspect, an embodiment of the present application provides an electronic device, including:
[0023] at least one processor; and
[0024] at least one memory in communication with the processor, wherein:
[0025] The memory stores program instructions, and the processor calls the program instructions to execute the method provided by the first aspect.
[0026] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed by a processor, the method provided in the first aspect is implemented.
[0027] In the embodiment of the present application, the first terminal device receives the software development tool SDK resource package sent by the second terminal device and stores the SDK resource package in the memory, and the SDK resource package is obtained by the second terminal device from the cloud server; in response to the SDK configuration selection, the SDK selected by the SDK configuration selection is loaded into the memory, and the icon corresponding to the SDK loaded into the memory is displayed on the main interface; when it is detected that the icon corresponding to any SDK loaded into the memory is selected, the SDK associated with the selected icon is called by the preset standard application to generate SDK binding information, and the SDK binding information is used to support the second terminal device to execute the binding process. By dynamically loading different SDKs into the memory, the functions of multiple applications can be realized through one standard application, and excessive memory space will not be occupied due to presetting multiple SDKs in the memory. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] Figure 1 A flow chart of a dynamic binding method provided in an embodiment of the present application;
[0029] Figure 2A A schematic diagram of a dynamic binding method provided in an embodiment of the present application;
[0030] Figure 2B A schematic diagram of another dynamic binding method provided in an embodiment of the present application;
[0031] Figure 2C A schematic diagram of another dynamic binding method provided in an embodiment of the present application;
[0032] Figure 2D A schematic diagram of another dynamic binding method provided in an embodiment of the present application;
[0033] Figure 2E A schematic diagram of another dynamic binding method provided in an embodiment of the present application;
[0034] Figure 2F A schematic diagram of another dynamic binding method provided in an embodiment of the present application;
[0035] Figure 3 A schematic diagram of another dynamic binding method provided in an embodiment of the present application;
[0036] Figure 4 A flowchart of another dynamic binding method provided in an embodiment of the present application;
[0037] Figure 5 A flowchart of another dynamic binding method provided in an embodiment of the present application;
[0038] Figure 6 A schematic diagram of the structure of a dynamic binding device provided in an embodiment of the present application;
[0039] Figure 7 A schematic diagram of the structure of another dynamic binding device provided in an embodiment of the present application;
[0040] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0041] In order to better understand the technical solution of this specification, the embodiments of the present application are described in detail below with reference to the accompanying drawings.
[0042] It should be clear that the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.
[0043] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit this specification. The singular forms of "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.
[0044] In order to address the problem that wearable devices such as smart watches and sports bracelets cannot install third-party applications due to their own software and hardware limitations, and have limited memory capacity and cannot pre-install a large number of SDKs in the memory, resulting in fewer applications on their own devices, an embodiment of the present application provides a dynamic binding method, which realizes the functions of multiple terminal applications by dynamically loading different SDKs into the memory and calling the SDK located in the memory based on preset standard applications, without taking up too much memory space.
[0045] Figure 1 A process of a dynamic binding method provided in an embodiment of the present application, a smart watch 110 and a smart phone 120 can be respectively used as a first terminal device and a second terminal device in an embodiment of the present application, and the method is applied to a dynamic binding system, which includes a smart watch 110, a smart phone 120 and a cloud server, such as Figure 1 As shown, the method may include:
[0046] 101. The smart watch 110 establishes a wireless connection with the smart phone 120.
[0047] In the embodiment of the present application, the smart watch 110 can establish a wireless connection with the smart phone 120, such as a Bluetooth connection, a near field communication, etc. Taking the Bluetooth connection as an example, the smart phone 120 scans the connectable devices in the current environment, and after the smart watch 110 responds, the smart phone 120 sends a connection request to the smart watch 110 to establish a Bluetooth connection.
[0048] In one embodiment, the smart watch 110 can also establish a connection with the smart phone 120 via a data cable.
[0049] 102. The smartphone 120 sends SDK configuration information to the cloud server 130.
[0050] In the embodiment of the present application, the purpose of the wireless connection between the smart watch 110 and the smart phone 120 is to download the SDK resource package from the cloud server 130 through the smart phone 120. In addition to the general SDK resource content, the SDK resource package also has information associated with the SDK. The user can determine the SDK function corresponding to the SDK resource package through the information, so that the user can select what he needs from multiple SDK resource packages according to the information. After the smart phone 120 detects that the wireless connection with the smart watch 110 is established, it can send SDK configuration information to the cloud server 130 to trigger the cloud server 130 to send the corresponding SDK resource package. Specifically, the first pairing connection between the smart phone 120 and the smart watch 110 can be used as an action to trigger itself to send SDK configuration information to the cloud server 130. In addition, if the smartphone 120 is disconnected from the smart watch 110 and then connected again, that is, it is not the first time that the smartphone 120 is connected to the smart watch 110, the smartphone 120 can determine whether the current SDK configuration information is updated compared to the SDK configuration information at the last connection. If there is an update, it will trigger itself to send the updated SDK configuration information to the cloud server 130. If there is no update, there is no need to repeatedly send the SDK configuration information to the cloud server 130.
[0051] In one embodiment, the SDK configuration information may include the device information of the smart watch 110 and the regional information of the smart phone 120. After the smart phone 120 establishes a wireless connection with the smart watch 110, it can obtain the device information of the smart watch 110 and the regional information of the smart phone 120. There are many ways to obtain the regional information of the smart phone 120. For example, the smart phone 120 can obtain its current IP address and determine the regional information according to the IP address; the smart phone 120 can also determine the regional information according to the user's pre-configuration; the smart phone 120 can also determine the regional information through its own positioning function. The smart phone 120 can obtain its own location information and use it to determine the regional information where the smart phone 120 is located. The embodiment of the present application does not limit the form of expression of the regional information. For example, the name of the country can be used to represent the regional information. The device information of the smart watch 110 can be sent to the smart phone 120 when the wireless connection is established between the smart phone 120 and the smart watch 110 or after the wireless connection is established. The device information can be the model of the device.
[0052] 103. The cloud server 130 sends the SDK resource package to the smart phone 120.
[0053] In the embodiment of the present application, the cloud server 130 pre-stores a plurality of SDK resource packages and an SDK resource package association table, and the SDK resource package association table records the SDK resource packages corresponding to different devices in different regions. For example, the cloud server 130 stores the SDK resource package for smart watches in region A, the SDK resource package for smart glasses in region A, the SDK resource package for smart watches in region B, and the SDK resource package for smart glasses in region B, and the device information in the current SDK configuration information is a smart watch, and the region information is region B. Based on the SDK resource package association table and the received SDK configuration information, the cloud server 130 sends the SDK resource package required by the smart watch 110 in the current region B to the smart phone 120. That is, the cloud server 130 selects the SDK resource package associated with the received SDK configuration information from the pre-stored plurality of SDK resource packages, and sends the selected SDK resource package to the smart phone 120.
[0054] 104. The smartphone 120 sends the SDK resource package to the smart watch 110.
[0055] In the embodiment of the present application, the smart phone 120 can establish a network connection with the cloud server 130 to obtain the SDK resource package, and then send the SDK resource package to the smart watch 110 via a short-range wireless communication connection such as Bluetooth.
[0056] 105. The smart watch 110 stores the SDK resource package in the memory.
[0057] After receiving the SDK resource package, the smart watch 110 first stores it in a memory, such as a hard disk, and waits for the user to make a configuration selection.
[0058] 106. The smart watch 110 parses the SDK resource package through the preset standard application and generates an SDK configuration list.
[0059] The smart watch 110 will have standard applications pre-set, and the standard applications and the SDK resource packages pre-stored in the cloud server 130 are all developed according to a pre-defined unified standard. Specifically, the developers of each terminal application develop SDK resource packages according to the unified standard, and the manufacturers of terminal devices such as the smart watch 110 pre-set standard applications in the device according to the unified standard.
[0060] Step 106 may be triggered at different times, and the present application embodiment does not limit this. For example, after the smart watch 110 stores the SDK resource package in the memory, step 106 is automatically triggered; for another example, after the smart watch 110 stores the SDK resource package in the memory, if the user clicks the SDK configuration option in the system setting menu on the smart watch 110, step 106 is triggered.
[0061] In the embodiment of the present application, the user can configure the SDK in the system management of the smart watch 110. Figure 2A As shown, the user can enter the system management by selecting the setting indicated by arrow 201. The system management includes options such as SDK configuration and application management. The user can select the SDK configuration indicated by arrow 202 to start the SDK-related configuration process. After the smart watch 110 detects that the user has started the SDK configuration, it parses all SDK resource packages in the memory through the preset standard application to obtain the SDK in each SDK resource package and the SDK information associated with the SDK. The smart watch 110 can generate an SDK configuration list based on the obtained SDK information and display the SDK configuration list on the SDK configuration interface for the user to select. Figure 2B As shown, the current SDK configuration interface includes an SDK configuration list. The SDK configuration list contains at least one option, such as Figure 2B Three options are shown, each of which has information associated with the SDK, which may include an icon, SDK name, etc., so that the user can distinguish different SDKs. The current SDK configuration list displays the information associated with the SDK of each SDK resource package in the memory, and the user can select one or more SDKs for subsequent SDK configuration according to their needs.
[0062] 107. The smart watch 110 loads the SDK selected by the user into the memory through a preset standard application, and displays the icon corresponding to the SDK loaded into the memory on the main interface.
[0063] In the embodiment of the present application, after the smart watch 110 detects the user's selection of an option corresponding to the SDK resource package in the SDK configuration interface, the SDK of the SDK resource package corresponding to the selected option is loaded into the memory through a preset standard application. The current user interface jumps from the current SDK configuration interface to the main interface, and the smart watch 110 adds the icon corresponding to the SDK loaded into the memory to the main interface through a preset standard application. Figure 2B and Figure 2C For example, the SDK configuration interface includes 3 options, that is, there are 3 SDK resource packages in the memory. The user selects two of the options, that is, 2 SDK resource packages in the memory. The smart watch 110 loads the SDKs of the corresponding two SDK resource packages into the memory through the preset standard application, and adds icons 1 and icon 2 corresponding to the two SDKs to the main interface through the preset standard application.
[0064] 108. The smart watch 110 calls the SDK through a standard application to perform SDK binding.
[0065] In the embodiment of the present application, the user can select the icons located in the main interface in turn to perform SDK binding. After the smart watch 110 detects that any icon in the main interface is selected, it calls the SDK corresponding to the icon through its own preset standard application to execute the binding process. SDK binding is used to bind the SDK to the user account to realize the user's authorization of the SDK. Since the standard application and the SDK resource package are developed according to the unified standard, the standard application can call each SDK to realize different application functions. Before normal use, the smart watch 110 must first complete the SDK binding. The corresponding SDK binding information can be generated by calling the SDK through the standard application. The user can complete the binding process by processing the SDK binding information through the smart phone 120.
[0066] In one embodiment, the SDK binding information is implemented through a binding interface, which includes a binding QR code. When binding any SDK, the user starts the terminal application corresponding to the SDK to be bound in the second terminal device and scans the binding QR code to implement the SDK binding operation. Figure 2D As shown, after the smart watch 110 detects that the user selects any icon (such as icon 1) on the main interface, the user interface jumps to the SDK binding interface, in which the user is first prompted to start the terminal application 1 on the smartphone 120 side to complete the binding. Among them, the terminal application 1 is the terminal application corresponding to the SDK to be bound. After the smart watch 110 detects that "Bind Now" is selected through the preset standard application, it displays the binding QR code. The user can scan the binding QR code through the terminal application 1 to enter the relevant interface. At the same time, the smart watch 110 displays the message "Bind in progress, please complete the operation on the smartphone side" through the preset standard application. The user can perform the final binding confirmation on the interface entered by scanning the binding QR code on the smartphone 120. It can be understood that the terminal application 1 in the smartphone 120 has been bound to the user account. The binding relationship between the SDK and the user account can be uploaded to the network side by scanning the binding QR code through the terminal application 1, so as to achieve the purpose of binding authorization.
[0067] In another embodiment, the SDK binding information may be a binding data packet. After the smart watch 110 generates the binding data packet through a preset standard application, it sends it to the smart phone 120. The smart phone 120 starts the terminal application corresponding to the SDK to be bound to process the binding data packet, obtains the information required for SDK binding and completes the binding operation. The purpose of the binding process is to bind the SDK in the smart watch 110 to the user account and complete the authorization. In addition to the above two methods, other feasible binding methods can also be used to complete the binding process.
[0068] In one embodiment, for the SDK loaded into the memory, the user can select the corresponding icon in turn to complete the binding process. The successfully bound SDK will be continuously stored in the memory so that the standard application can call the SDK to implement the corresponding application function. In addition, the icon corresponding to the successfully bound SDK will be fixedly displayed on the main interface. If multiple SDKs are successfully bound, multiple icons will be displayed on the main interface.
[0069] After the binding is completed, the user can select any icon on the main interface to execute the normal usage process through the preset standard application. After the smart watch 110 detects that the icon is selected through the preset standard application, it calls the SDK corresponding to the icon in the memory through the standard application to implement the corresponding function.
[0070] Taking the payment function as an example, in a real scenario, Figure 2B In the SDK configuration interface shown, icon 1 and SDK name 1 belong to the first option, corresponding to the payment function SDK of payment provider 1; icon 2 and SDK name 2 belong to the second option, corresponding to the payment function SDK of payment provider 2; icon 3 and SDK name 3 belong to the third option, corresponding to the payment function SDK of payment provider 3. After the user selects the first and second options in the SDK configuration interface and clicks OK, it jumps to Figure 2C The main interface shown in FIG. 1 shows an icon 1 corresponding to payment provider 1 and an icon 2 corresponding to payment provider 2. When the user clicks icon 1 for the first time, the following will be displayed: Figure 2D The binding interface corresponding to payment provider 1 shown in the figure, after the user clicks "Bind Now" to display the binding QR code, the user uses the payment APP corresponding to payment provider 1 on the smartphone to scan the binding QR code, the smartwatch enters the binding interface and prompts the user to operate on the phone side. After scanning the binding QR code, the smartphone enters the binding process, and the binding can be completed based on the user's operation. After the binding is completed, Figure 2C In the main interface shown, if the user clicks icon 1 again, since the SDK corresponding to icon 1 has been bound, the smart watch 110 calls the corresponding SDK1 in the memory through the standard application to generate a payment QR code, such as Figure 2E As shown, since the SDK has been successfully bound and authorized, the user can complete the payment normally.
[0071] In another actual scenario, if the user selects icon 2, the smart watch 110 will generate another payment QR code through a standard application call corresponding SDK2 in the memory for the user to complete the payment. The specific process is similar to the process corresponding to icon 1, and will not be repeated here.
[0072] It should also be noted that the binding QR code and payment QR code in the embodiments of the present application are only examples, and there is no limitation on the types of the binding code and payment code, for example, they can also be bar codes.
[0073] Normally, the cloud server 130 will send all SDK resource packages supported by the smart watch 110 in the current region, and the user will select some SDKs according to their needs and load them into the memory and complete the binding. Therefore, the number of SDK resource packages in the memory is greater than the number of SDKs in the memory. For the SDK that has been successfully bound, the user can also perform the unbinding operation, and then load other SDKs from the SDK resource package in the memory to the memory to complete the binding. The memory space of the smart watch 110 is small and a large number of SDKs cannot be pre-set. By parsing the SDK resource package from the memory and then dynamically binding the SDK, the number of functions supported by the smart watch 110 can be effectively increased.
[0074] In one embodiment, the SDK unbinding process can be executed on the smart watch 110 side or the smart phone 120 side. Specifically, the user can select the unbinding operation in the running interface generated after the standard application calls the SDK. In response to the unbinding request, the smart watch 110 sends an unbinding instruction to the smart phone through a preset standard application, deletes the unbinding SDK from the content of the smart watch through the preset standard application, and deletes the icon corresponding to the unbinding SDK from the main interface through the preset standard application. After the smart phone receives the unbinding instruction, it triggers the corresponding SDK unbinding process.
[0075] Alternatively, SDK unbinding requires the user to confirm in the specific terminal application on the smartphone 120 side. The smartphone 120 can send an SDK unbinding request to the smart watch 110 according to the user's choice. After receiving the request, the smart watch 110 will unbind the specified SDK. For the unbound SDK, the smart watch 110 deletes it from the memory and deletes the corresponding icon in the main interface. For example, Figure 2F As shown, when the user wants to unbind SDK1, the smart watch 110 prompts the user to set and manage in the terminal application 1 on the smart phone 120 side to achieve unbinding.
[0076] In the embodiment of the present application, taking the payment function as an example, different regions may be accustomed to using different payment applications. The cloud server 130 sends the corresponding SDK resource package according to the regional information, and the smart watch 110 selects the SDK according to the user's choice and loads it into the memory for dynamic binding. It can realize the payment function in different regions, and there is no need to pre-set the SDK of the payment application in each region in the memory in advance, saving memory resources. Secondly, each payment provider develops the SDK resource package through unified standards, and the SDK loaded into the memory is called through the standard application. The manufacturers of terminal devices such as the smart watch 110 do not need to customize and develop their own user interface for each payment provider, but only need to develop the user interface of the standard application according to the pre-defined standards, reducing the workload of customized development and version maintenance.
[0077] In one embodiment, after the smart watch 110 establishes a wireless connection with the smart phone 120, if it is determined that the currently connected smart phone 120 is different from the device that established the connection last time, the SDK initialization process can be executed to delete the original SDK in the memory of the smart watch 110, and delete the original SDK resource package in the memory of the smart watch 110. The above operations can effectively ensure that the privacy or property of each user is not infringed.
[0078] In one embodiment, if the smart watch 110 also supports network functions and can establish a network connection with the cloud server 130, the smart watch 110 can directly send its own device information and region information to the cloud server 130, and the cloud server 130 directly sends the associated SDK resource package to the smart watch 110 without the need for the smart phone 120 as a transfer. After receiving the SDK resource package, the smart watch 110 also stores it in the memory, and the subsequent binding, use and unbinding processes can be the same as described above.
[0079] In one embodiment, a plurality of standard applications may be preset in the smart watch 110 for different application types, for example, a corresponding first standard application may be preset for a payment application, and a corresponding second standard application may be preset for a communication application. When the cloud server 130 sends down the SDK resource package, in addition to the device information and the regional information, the corresponding SDK resource package may also be filtered according to the application type. Specifically, when the user wants to configure the SDK for the first standard application, the smart watch 110 may send the corresponding application type to the smart watch 120, and the smart watch 120 may send the device information, the regional information and the application type to the cloud server 130, and the cloud server 130 may send down the payment-related SDK supported by the smart watch 110 in the current region.
[0080] In one embodiment, after the smart phone 120 receives the SDK resource package sent by the cloud server, the user can send the SDK resource package that needs to be SDK-bound to the smart watch 110 on the smart phone 120 side, and the smart watch 110 can load all SDKs into the memory after receiving the SDK resource package. For example, the cloud server 130 sends 10 SDK resource packages to the smart phone 120, and the user only wants to perform the configuration and binding process on two of the SDK resource packages. In this case, the two SDK resource packages can be selected on the smart phone 120 side and sent to the smart watch 110, without sending all 10 SDK resource packages. Specifically, after the smart phone 120 receives the SDK resource package sent by the cloud server 130, it can also store it in its own memory and parse the SDK resource package to obtain the SDK information corresponding to each SDK resource package. As shown in the figure, taking Bluetooth connection as an example, the user can click the configuration watch option indicated by arrow 301 to enter the corresponding configuration watch interface, and select the SDK management option indicated by arrow 302 in the configuration watch interface to view the SDK information corresponding to the SDK resource package issued by the cloud server 130. After the user selects the required SDK resource package, he can click Apply, which allows the user to manually select the required SDK resource package from all SDK resource packages issued by the cloud server 130. The SDK resource package selected by the user can be transmitted to the smart watch 110, for example, via Bluetooth. Sending only the currently required SDK resource package to the smart watch 110 can reduce the power consumption of the smart watch 110 and extend the standby time.
[0081] Figure 4 A flowchart of another dynamic binding method provided in an embodiment of the present application. The method can be applied to a first terminal device, which includes a lightweight wearable device such as a smart watch or a sports bracelet, and can also include a terminal device such as a smart phone. Figure 4 As shown, the method may include:
[0082] Step 401 : Load the SDK in the SDK resource package selected by the user into the memory through a preset standard application, and display the icon corresponding to the SDK loaded into the memory on the main interface through the preset standard application.
[0083] Before this step, a software development tool SDK resource package sent by the second terminal device can be received and the SDK resource package can be stored in the memory. The second terminal device in the embodiment of the present application mainly refers to a device that supports wireless network functions, such as a smart phone. The second terminal device can establish a connection with the cloud server through the network to exchange data. Due to the limitations of its own software and hardware, the first terminal device may not support wireless network communication functions. By pairing and connecting with the second terminal device (such as a Bluetooth connection), it is possible to obtain the SDK resource package from the cloud server. Specifically, after establishing a wireless connection with the first terminal device, the second terminal device can obtain the SDK resource package at the cloud server and send the SDK resource package to the first terminal device.
[0084] In one embodiment, if the first terminal device supports a wireless network communication function, it can directly establish a network connection with a cloud server and obtain an SDK resource package from the cloud server without forwarding it through a second terminal device.
[0085] When the user configures the SDK through the "Settings" application, the first terminal device responds to the SDK configuration request and parses each SDK resource package stored in the memory through a preset standard application, and obtains the SDK corresponding to each resource package and SDK-related SDK information, wherein the SDK information is used to distinguish different SDKs, and may specifically include: icons, SDK names, and the space occupied by the SDK in the memory, etc. The first terminal device can generate an SDK configuration list based on the obtained SDK information, and display the SDK configuration list on the user interface for user selection. The user can manually select the SDK configuration in the SDK configuration list. In response to the user's SDK configuration selection, the first terminal device will load the SDK selected by the user into the memory and display the corresponding icon on the main interface.
[0086] In one embodiment, when the user makes an SDK configuration selection, one or more SDK configuration information can be selected in the SDK configuration list. When any one or more configuration information is detected to be selected, the first terminal device will load the SDK associated with the selected SDK configuration information into the memory and display the corresponding icon on the main interface.
[0087] Step 402: When it is detected that any icon corresponding to the SDK loaded in the memory in the main interface is selected, the SDK associated with the selected icon is called by a preset standard application to execute a binding process.
[0088] After the first terminal device loads the SDK selected by the user into the memory, the main interface will display the icon corresponding to each SDK, and the user can start the corresponding SDK binding process by selecting the icon corresponding to any SDK. Specifically, the first terminal device has a standard application pre-installed inside, and the SDK binding information can be generated by calling the SDK icon corresponding to the selected SDK through the standard application. The user can complete the relevant binding process by processing the SDK binding information through the second terminal device.
[0089] In one embodiment, there may be differences in terminal applications commonly used in different regions. For the same first terminal device, the cloud server can select different SDK resource packages to send to the second terminal device according to the different regions where it is located. The memory of the first terminal device is larger than the internal memory capacity, but the number of SDK resource packages that can be stored is still limited. The cloud server sends the SDK resource packages commonly used in the current region according to the regional information, which can effectively increase the number of SDKs that can be called by the first terminal device, and bind the SDK in a targeted manner to achieve the necessary functions in the current region. For example, the cloud server stores 20 SDK resource packages. When the first terminal device is in region A, 6 SDK resource packages can be downloaded from the cloud server and stored in the memory, and 2 SDKs can be loaded into the memory to complete the binding. The number of SDKs available to the first terminal device is 20, but only 2 SDKs actually occupy the memory. When the first terminal device switches to other regions, the SDK resource packages in the memory can be updated.
[0090] In an embodiment of the present application, after the first terminal device is connected to the second terminal device, an SDK resource package is obtained from the cloud server and stored in the memory, and different SDKs are dynamically loaded into the memory. The functions of multiple applications can be realized through one standard application, and excessive memory space will not be occupied due to pre-installing multiple SDKs in the memory.
[0091] Figure 5 A flowchart of another dynamic binding method provided in an embodiment of the present application, which can be applied to a second terminal device, such as Figure 5 As shown, it may specifically include:
[0092] Step 501: After establishing a wireless connection with a first terminal device, determine the SDK configuration information of the first terminal device.
[0093] After the second terminal device establishes a wireless connection with the first terminal device, it can obtain the device information of the first terminal device, and the second terminal device can determine the region information where it is located based on its own positioning function. Since the first terminal device and the second terminal device are located in the same region, the region information can be used to characterize the region where the first terminal device is located.
[0094] Step 502: Send the SDK configuration information to the cloud server, so that the cloud server determines the SDK resource package associated with the first terminal device according to the SDK configuration information.
[0095] Step 503: Receive the SDK resource package sent by the cloud server.
[0096] Step 504: Send the SDK resource package to the first terminal device, so that the first terminal device obtains the SDK from the SDK resource package, loads it into the memory, and calls the SDK through a preset standard application to complete the binding process.
[0097] For other details, please refer to the description in the other flow charts above.
[0098] Figure 6 This is a schematic diagram of the structure of a dynamic binding device provided in an embodiment of the present application. The device is deployed in a first terminal device to implement the dynamic binding method provided in an embodiment of the present application, such as Figure 6 As shown, the device may include: a receiving module 610 , a loading module 620 and a processing module 630 .
[0099] The receiving module 610 is used to receive the SDK resource package sent by the second terminal device and store the SDK resource package in the memory.
[0100] The loading module 620 is used to load the SDK in the SDK resource package selected by the user into the memory through the preset standard application, and display the icon corresponding to the SDK loaded into the memory on the main interface through the preset standard application.
[0101] Processing module 630 is used to detect that when any icon corresponding to the SDK loaded in the memory is selected in the main interface, the SDK associated with the selected icon is called by a preset standard application to generate SDK binding information, and the SDK binding information is used to support the second terminal device to execute the binding process.
[0102] Figure 7 This is a schematic diagram of the structure of a dynamic binding device provided in an embodiment of the present application. The device is deployed in a second terminal device to implement the dynamic binding method provided in an embodiment of the present application, such as Figure 7 As shown, the device may include: a determining module 710 , a sending module 720 and a receiving module 730 .
[0103] The determination module 710 is used to determine the SDK configuration information of the first terminal device after establishing a wireless connection with the first terminal device.
[0104] The sending module 720 is used to send the SDK configuration information to the cloud server, so that the cloud server determines the SDK resource package associated with the first terminal device according to the SDK configuration information.
[0105] The receiving module 730 is used to receive the SDK resource package sent by the cloud server.
[0106] The sending module 720 is further used to send the SDK resource package to the first terminal device, so that the first terminal device obtains the SDK from the SDK resource package, loads it into the memory, and calls the SDK through a preset standard application to complete the binding process.
[0107] The specific execution steps of each of the above modules can refer to the description of the method flowchart.
[0108] The electronic device 800 can be used as a specific device to implement the above-mentioned first terminal device, second terminal device or cloud server, and execute the dynamic binding method of the embodiment of the present application. The electronic device 800 may include a processor 810, an internal memory 821, a power management module 831 and a battery 832, etc.
[0109] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 800. In other embodiments of the present application, the electronic device 800 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.
[0110] The processor 810 may include one or more processing units. For example, the processor 810 may include an application processor (AP), a modem processor, etc. Different processing units may be independent devices or integrated into one or more processors.
[0111] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.
[0112] The processor 810 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 810 is a cache memory. The memory may store instructions or data that the processor 810 has just used or cyclically used. If the processor 810 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 810, and thus improves the efficiency of the system.
[0113] In some embodiments, the processor 810 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, which is a bidirectional synchronous serial bus including a serial data line (SDA) and a serial clock line (SCL).
[0114] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the electronic device 800. In other embodiments of the present application, the electronic device 800 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.
[0115] The power management module 831 is used to connect the battery 832 and the processor 810. The power management module 831 receives input from the battery 832 and supplies power to the processor 810 and the internal memory 821.
[0116] The internal memory 821 can be used to store computer executable program codes, which include instructions. The internal memory 821 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function, etc. The data storage area may store data created during the use of the electronic device 800, etc. In addition, the internal memory 821 may include a high-speed random access memory and may also include a non-volatile memory. The processor 810 executes various functional applications and data processing of the electronic device 800 by running instructions stored in the internal memory 821 and / or instructions stored in a memory provided in the processor.
[0117] The processor 810 can execute various functional applications and data processing by running the programs stored in the internal memory 821, such as implementing the dynamic binding method provided in the embodiment of the present application.
[0118] The embodiment of the present application also provides a non-temporary computer-readable storage medium, which stores computer instructions, and the computer instructions enable the computer to execute the dynamic binding method provided by the embodiment of the present application.
[0119] The above-mentioned non-temporary computer-readable storage medium can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (Read Only Memory; hereinafter referred to as: ROM), an erasable programmable read-only memory (ErasableProgrammable Read Only Memory; hereinafter referred to as: EPROM) or flash memory, optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.
[0120] Computer-readable signal media may include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.
[0121] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
[0122] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.
[0123] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.
[0124] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.
Claims
1. A dynamic binding system, characterized in that: The system includes a first terminal device, a second terminal device and a cloud server; The second terminal device is used to send software development tool SDK configuration information to the cloud server; The cloud server is used to filter out the SDK resource package associated with the SDK configuration information from the pre-stored SDK resource packages, and send the filtered SDK resource package to the second terminal device; The second terminal device is further used to send the SDK resource package sent by the cloud server to the first terminal device; The first terminal device is used to store the SDK resource package sent by the second terminal device into a memory, and in response to a user's selection operation on the SDK resource package in the memory, load the SDK in the SDK resource package selected by the user into the memory through a preset standard application; Each SDK resource package and the standard application are developed based on a predefined unified standard to ensure that the standard application can successfully call the SDK loaded into the memory for binding and use.
2. The system according to claim 1, characterized in that The second terminal device is specifically used to send software development tool SDK configuration information to the cloud server when a connection is established between the first terminal device and the second terminal device or after the connection is established.
3. The system according to claim 2, characterized in that The second terminal device is specifically configured to, after the first terminal device is connected to the second terminal device, send software development tool SDK configuration information to the cloud server if the first terminal device is connected to the second terminal device for the first time, or if the current region information of the second terminal device is changed compared to the region information when the second terminal device was connected to the first terminal device last time; The SDK configuration information includes region information.
4. The system according to claim 2, characterized in that The first terminal device is further configured to send device information to the second terminal device after establishing a connection with the second terminal device; The SDK configuration information also includes device information of the first terminal device.
5. A dynamic binding method, characterized in that: Applied to a first terminal device, the method includes: Loading the SDK in the SDK resource package selected by the user into the memory through the preset standard application, and displaying the icon corresponding to the SDK loaded into the memory on the main interface through the preset standard application; When any of the icons in the main interface is selected, the SDK associated with the selected icon is called by the preset standard application to execute a binding process; Each SDK resource package and the standard application are developed based on a predefined unified standard to ensure that the standard application can successfully call the SDK loaded into the memory for binding and use.
6. The method according to claim 5, characterized in that Before the SDK in the SDK resource package selected by the user is loaded into the memory through the preset standard application, the method further includes: Displaying an SDK configuration interface, wherein the SDK configuration interface has options corresponding to each SDK resource package, and each of the options has information associated with the SDK; The step of loading the SDK in the SDK resource package selected by the user into the memory through the preset standard application includes: The SDK in the SDK resource package corresponding to the option selected by the user in the SDK configuration interface is loaded into the memory through a preset standard application.
7. The method according to claim 6, characterized in that Before displaying the SDK configuration interface, the method further includes: Receiving a software development tool SDK resource package sent by the second terminal device and storing the SDK resource package in a memory; Each SDK resource package stored in the memory is parsed through a preset standard application to obtain the SDK in each SDK resource package and the information associated with the SDK.
8. The method according to claim 7, characterized in that The step of loading the SDK in the SDK resource package corresponding to the option selected by the user in the SDK configuration interface into the memory through the preset standard application includes: Loading the SDK in each SDK resource package corresponding to one or more options selected by the user in the SDK configuration interface into the memory through a preset standard application; The method of displaying the icon corresponding to the SDK loaded into the memory on the main interface through the preset standard application includes: The icons corresponding to each SDK loaded into the memory are displayed on the main interface through the preset standard applications.
9. The method according to claim 7, characterized in that: The information includes at least one or any combination of the following: icon; SDK name; Storage space occupied by the SDK.
10. The method according to claim 5, characterized in that After the binding process is completed, the method further includes: When any of the icons in the main interface is selected, the SDK corresponding to the selected icon is called through the standard application to execute the use process.
11. The method according to claim 5, characterized in that After the binding process is completed, the method further includes: Receiving an SDK unbinding request sent by the second terminal device; The corresponding SDK is unbound and deleted from the memory according to the SDK unbinding request.
12. The method according to claim 7, characterized in that Before receiving the software development kit SDK sent by the second terminal device and storing the SDK in the memory, the method further includes: If it is detected that the second terminal device is different from the device connected last time, the SDK initialization process is executed, and the SDK initialization process is used to delete the original SDK in the memory and delete the original SDK resource package in the storage.
13. The method according to claim 5, characterized in that Also includes: In response to the user's unbinding operation on the bound SDK, an unbinding instruction is sent to the second terminal device, the corresponding SDK is deleted from the memory, and the corresponding icon is deleted from the main interface.
14. A dynamic binding method, characterized in that: The method is applied to a second terminal device, comprising: After establishing a connection with the first terminal device, determining SDK configuration information; Sending the SDK configuration information to a cloud server, so that the cloud server determines an SDK resource package associated with the first terminal device according to the SDK configuration information; Receive the SDK resource package sent by the cloud server; At least part of the SDK resource package is sent to the first terminal device, so that the first terminal device obtains the SDK from the SDK resource package, loads it into the memory, and calls the SDK through a preset standard application to complete the binding process.
15. The method according to claim 14, characterized in that The SDK configuration information includes at least device information and region information of the first terminal device; The determining of SDK configuration information includes: Acquire device information of the first terminal device; The current IP address of the second terminal device is obtained, and the region information is determined according to the IP address.
16. The method according to claim 14, characterized in that The sending at least part of the SDK resource package to the first terminal device includes: At least part of the SDK resource package selected by the user from the SDK resource package received from the cloud server is sent to the first terminal device.
17. The method according to claim 15, characterized in that The method further comprises: When it is detected that an unbinding operation is performed on any successfully bound SDK, an SDK unbinding request is sent to the first terminal device, so that the first terminal device unbinds the SDK bound to the terminal application and deletes it from the memory.
18. An electronic device, characterized in that: include: at least one processor; as well as at least one memory in communication with the processor, wherein: The memory stores program instructions, and the processor calls the program instructions to execute the method according to any one of claims 5 to 17.
19. A computer-readable storage medium, characterized in that: The computer-readable storage medium comprises a stored program, wherein the program, when executed by a processor, implements the method according to any one of claims 5 to 17.
Citation Information
Patent Citations
Pushing method and device, apparatus, and computer storage medium
CN109218393A
Application starting method and device, terminal equipment and storage medium
CN112162796A
Equipment cooperation method, device and system, electronic equipment and storage medium
CN112286618A
Method and system for installing function card on RTOS platform intelligent wearable device
CN114610336A
Off-line payment method and device, electronic equipment and readable storage medium
CN115330379A
Cited By
Dynamic binding method and system, electronic device, and storage medium
EP4647902A1
Dynamic binding method and system, electronic device, and storage medium
WO2024234678A1
