Dynamic binding method and system, electronic device, and storage medium

Through the dynamic binding method, the wearable device downloads and loads the SDK resource package from the cloud server, calls the SDK using standard applications, solving the problems of limited memory and SDK occupancy, and realizing the support of multi-application functions and resource saving.

WO2024234678A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/070353
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-01-03
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Wearable devices such as smartwatches 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 storage resources, limiting the number of applications supported by the device.

Method used

Through dynamic binding method, wearable devices and mobile phones and other terminals download matching SDK resource packages from cloud servers, load them into memory based on user selection, and use preset standard applications to call SDK to realize the functions of multiple applications without causing any reason. Preset multiple SDKs and occupy too much memory space.

Benefits of technology

It effectively increases the number of applications supported by wearable devices, saves memory resources, and implements multi-function support by dynamically loading the SDK, avoiding storage waste caused by preset SDK.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024070353_21112024_PF_FP_ABST
    Figure CN2024070353_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Embodiments of the present application relate to the technical field of computers, and in particular to a dynamic binding method and system, an electronic device, and a storage medium. A first terminal device receives software development kit (SDK) resource packs sent by a second terminal device and stores the SDK resource packs in a storage, the SDK resource packs being obtained by the second terminal device from a cloud server; and in response to SDK configuration selection, the first terminal device loads an SDK selected by means of the SDK configuration selection into a memory, and displays, in a main interface, an icon corresponding to the SDK loaded into the memory, wherein each SDK resource pack and a standard application are developed on the basis of a pre-defined unified standard, so as to ensure that the standard application can successfully call the SDK loaded into the memory for binding and use. Different SDKs are dynamically loaded into a memory, functions of multiple applications can be realized by one standard application, and the occupancy of excessive memory space caused by presetting multiple SDKs in the memory is avoided.
Need to check novelty before this filing date? Find Prior Art

Description

Dynamic binding method, system, electronic device and storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on May 12, 2023, with application number 202310541141.3 and application name “Dynamic Binding Method, System, Electronic Device and Storage Medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] 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

[0003] Currently, wearable devices (such as smart watches and fitness trackers) are becoming increasingly versatile, encompassing multiple areas of daily life. For example, some wearable devices, once linked to a user, can perform access control recognition or scan code payment, making users' lives more convenient.

[0004] However, due to inherent hardware and software limitations, wearable devices cannot support the installation of third-party applications through app stores. To use an application, the software development kit (SDK) must be pre-loaded into the wearable device's memory. Wearable devices have limited memory resources and cannot pre-install a large number of SDKs, limiting the number of supported applications. Furthermore, pre-installed SDKs remain in memory at all times. Even if an application is not used for a long time, the corresponding SDK will still occupy memory, wasting storage resources.

[0005] Summary of the Invention

[0006] The present invention provides a dynamic binding method, system, electronic device, and storage medium. A wearable device uses a mobile phone or other terminal to download an SDK resource package that matches the SDK configuration information from a cloud server. Based on the user's selection, a standard application loads the selected SDK into memory, and the standard application calls the SDK to complete the binding and subsequent normal use. By loading different SDKs into memory based on different SDK configuration information, a single standard application can implement the functions of multiple applications without the excessive memory space occupied by pre-installing multiple SDKs in memory.

[0007] In the first aspect, an embodiment of the present application provides a dynamic binding system, which 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 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 of 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 predefined unified standard to ensure that the standard application can successfully call the SDK loaded into the memory for binding and use.

[0008] In one embodiment, the second terminal device is specifically configured 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.

[0009] In one embodiment, the second terminal device is specifically used to, 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 if 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.

[0010] In one embodiment, 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 the device information of the first terminal device.

[0011] 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, the SDK associated with the selected icon is called 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.

[0012] 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, and 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.

[0013] In one embodiment, before displaying the SDK configuration interface, it also includes: receiving a software development tool SDK resource package sent by the 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.

[0014] 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 icon corresponding to the SDK loaded into the memory on the main interface through a preset standard application, including: displaying the icon corresponding to each SDK loaded into the memory on the main interface through a preset standard application.

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

[0016] 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 usage process.

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

[0018] In one embodiment, before receiving the software development kit SDK sent by the second terminal device and storing the SDK in the memory, the method also includes: if it is detected that the second terminal device is different from the device connected last time, executing the 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.

[0019] In one embodiment, the method further includes: in response to the user's unbinding operation on the 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.

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

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

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

[0023] In one embodiment, the method further includes: when 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.

[0024] In a fourth aspect, an embodiment of the present application provides an electronic device, including:

[0025] at least one processor; and

[0026] at least one memory in communication with the processor, wherein:

[0027] The memory stores program instructions, and the processor calls the program instructions to execute the method provided by the first aspect.

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

[0029] In an embodiment of the present application, a first terminal device receives a software development tool SDK resource package sent by a second terminal device and stores the SDK resource package in a memory. The SDK resource package is obtained by the second terminal device from a cloud server. In response to an SDK configuration selection, the SDK selected in 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 through a preset standard application to generate SDK binding information. 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 a standard application, and excessive memory space will not be occupied due to pre-setting multiple SDKs in the memory. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] FIG1 is a flow chart of a dynamic binding method provided in an embodiment of the present application;

[0031] FIG2A is a schematic diagram of a dynamic binding method provided in an embodiment of the present application;

[0032] FIG2B is a schematic diagram of another dynamic binding method provided in an embodiment of the present application;

[0033] FIG2C is a schematic diagram of another dynamic binding method provided in an embodiment of the present application;

[0034] FIG2D is a schematic diagram of another dynamic binding method provided in an embodiment of the present application;

[0035] FIG2E is a schematic diagram of another dynamic binding method provided in an embodiment of the present application;

[0036] FIG2F is a schematic diagram of another dynamic binding method provided in an embodiment of the present application;

[0037] FIG3 is a schematic diagram of another dynamic binding method provided in an embodiment of the present application;

[0038] FIG4 is a flow chart of another dynamic binding method provided in an embodiment of the present application;

[0039] FIG5 is a flow chart of another dynamic binding method provided in an embodiment of the present application;

[0040] FIG6 is a schematic structural diagram of a dynamic binding device provided in an embodiment of the present application;

[0041] FIG7 is a schematic structural diagram of another dynamic binding device provided in an embodiment of the present application;

[0042] FIG8 is a schematic structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0043] In order to better understand the technical solutions of this specification, the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0044] It should be clear that the embodiments described 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 making creative work are within the scope of protection of this specification.

[0045] The terms used in the examples of this application are for the purpose of describing specific embodiments only and are not intended to limit this specification. The singular forms "a," "an," "the," and "the" used in the examples of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0046] 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 their limited memory capacity makes it impossible to 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. By dynamically loading different SDKs into the memory and calling the SDKs in the memory based on preset standard applications, the functions of multiple terminal applications can be realized without taking up too much memory space.

[0047] FIG1 is a flow chart of a dynamic binding method provided in an embodiment of the present application. A smartwatch 110 and a smartphone 120 may serve as a first terminal device and a second terminal device, respectively, in an embodiment of the present application. The method is applied to a dynamic binding system, which includes the smartwatch 110, the smartphone 120, and a cloud server. As shown in FIG1 , the method may include:

[0048] 101. The smartwatch 110 establishes a wireless connection with the smartphone 120.

[0049] In the embodiment of the present application, the smartwatch 110 can establish a wireless connection with the smartphone 120, such as a Bluetooth connection, near-field communication, etc. Taking Bluetooth connection as an example, the smartphone 120 scans for connectable devices in the current environment, and after the smartwatch 110 responds, the smartphone 120 sends a connection request to the smartwatch 110 to establish the Bluetooth connection.

[0050] In one embodiment, the smart watch 110 can also establish a connection with the smart phone 120 via a data cable.

[0051] 102. The smartphone 120 sends SDK configuration information to the cloud server 130.

[0052] In the embodiment of the present application, the purpose of the wireless connection between the smart watch 110 and the smartphone 120 is to download the SDK resource package from the cloud server 130 through the smartphone 120. In addition to the general SDK resource content, the SDK resource package also has information associated with the SDK. The user can use this information to determine the SDK function corresponding to the SDK resource package, so that the user can select the one they need from multiple SDK resource packages based on this information. After the smartphone 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 smartphone 120 and the smart watch 110 can be used as a trigger for itself to send the 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 with the SDK configuration information at the time of 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.

[0053] In one embodiment, the SDK configuration information may include the device information of the smartwatch 110 and the region information of the smartphone 120. After establishing a wireless connection with the smartwatch 110, the smartphone 120 can obtain the device information of the smartwatch 110 and the region information of the smartphone 120. The smartphone 120 can obtain the region information in a variety of ways. For example, the smartphone 120 can obtain its current IP address and determine the region information based on the IP address; the smartphone 120 can also determine the region information based on the user's pre-configured settings; the smartphone 120 can also determine the region information through its own positioning function. The smartphone 120 can obtain its own location information and use this to determine the region information where the smartphone 120 is located. This embodiment of the application does not limit the form in which the region information is presented; for example, the name of a country can be used to represent the region information. The device information of the smartwatch 110 can be sent to the smartphone 120 when the wireless connection is established between the smartphone 120 and the smartwatch 110 or after the wireless connection is established. The device information can be the model of the device.

[0054] 103. The cloud server 130 sends the SDK resource package to the smartphone 120.

[0055] In an embodiment of the present application, the cloud server 130 pre-stores multiple SDK resource packages and an SDK resource package association table. 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 an SDK resource package for a smartwatch in region A, an SDK resource package for smart glasses in region A, an SDK resource package for a smartwatch in region B, and an SDK resource package for smart glasses in region B. If the device information in the current SDK configuration information is a smartwatch and the region information is region B, then 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 smartwatch 110 in the current region B to the smartphone 120. In other words, the cloud server 130 filters out the SDK resource package associated with the received SDK configuration information from the multiple pre-stored SDK resource packages and sends the filtered SDK resource package to the smartphone 120.

[0056] 104. The smartphone 120 sends the SDK resource package to the smart watch 110.

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

[0058] 105. The smart watch 110 stores the SDK resource package in the memory.

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

[0060] 106. The smart watch 110 parses the SDK resource package through a preset standard application and generates an SDK configuration list.

[0061] Smartwatch 110 is pre-installed with standard applications. These standard applications and the SDK resource packages stored in cloud server 130 are all developed according to pre-defined unified standards. Specifically, the developers of various terminal applications develop SDK resource packages based on this unified standard, and the manufacturers of terminal devices such as smartwatch 110 pre-install standard applications within their devices based on this unified standard.

[0062] Step 106 can be triggered at different times, which is not limited in this embodiment of the present application. For example, after the smartwatch 110 stores the SDK resource package in the memory, step 106 is automatically triggered. For another example, after the smartwatch 110 stores the SDK resource package in the memory, if the user clicks the SDK configuration option in the system settings menu on the smartwatch 110, step 106 is triggered.

[0063] In an embodiment of the present application, a user can configure the SDK in the system management section of the smartwatch 110. As shown in Figure 2A, the user can enter the system management section by selecting the settings indicated by arrow 201. The system management section includes options such as SDK configuration and application management. The user can select the SDK configuration section indicated by arrow 202 to start the SDK-related configuration process. After the smartwatch 110 detects that the user has initiated SDK configuration, it parses all SDK resource packages in the memory using a pre-set standard application, obtains the SDK in each SDK resource package, and obtains SDK information associated with each SDK. Based on the obtained SDK information, the smartwatch 110 can generate an SDK configuration list and display the SDK configuration list on the SDK configuration interface for the user to select. As shown in Figure 2B, the current SDK configuration interface includes the SDK configuration list. The SDK configuration list contains at least one option. For example, Figure 2B illustrates three options. Each option has information associated with the SDK, which may include an icon, SDK name, etc., to enable the user to distinguish between different SDKs. The current SDK configuration list displays the information associated with the SDK of each SDK resource package in the memory. Users can select one or more SDKs for subsequent SDK configuration according to their needs.

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

[0065] In an embodiment of the present application, after the smart watch 110 detects that the user has selected an option corresponding to an 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. Taking Figures 2B and 2C as an example, the SDK configuration interface contains 3 options, that is, there are 3 SDK resource packages in the memory. The user selects two of the options, that is, selects 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.

[0066] 108. The smart watch 110 calls the SDK through a standard application to perform SDK binding.

[0067] In the embodiment of the present application, the user can select the icons on the main interface in sequence to perform SDK binding. After the smart watch 110 detects that any icon in the main interface has been 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 and realize the user's authorization of the SDK. Since standard applications and SDK resource packages are developed according to unified standards, standard applications can call various SDKs to implement different application functions. Before normal use, the smart watch 110 must first complete the SDK binding. Calling the SDK through the standard application can generate the corresponding SDK binding information. The user can complete the binding process by processing the SDK binding information through the smartphone 120.

[0068] In one embodiment, SDK binding information is implemented through a binding interface. The binding interface includes a binding QR code. When binding any SDK, the user launches the terminal application corresponding to the SDK to be bound on the second terminal device and scans the binding QR code to complete the SDK binding operation. As shown in Figure 2D, 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. This interface first prompts the user to launch terminal application 1 on the smartphone 120 side to complete the binding. 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 a preset standard application, it displays a binding QR code. The user scans the binding QR code through 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 smart phone 120 has been bound to the user account. By scanning the binding QR code through the terminal application 1, the binding relationship between the SDK and the user account can be uploaded to the network side to achieve the purpose of binding authorization.

[0069] In another embodiment, the SDK binding information can be a binding data packet. After the smartwatch 110 generates the binding data packet through a pre-installed standard application, it sends it to the smartphone 120. The smartphone 120 launches 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 smartwatch 110 to the user account and complete the authorization. In addition to the two methods described above, other feasible binding methods can also be used to complete the binding process.

[0070] In one embodiment, for SDKs already loaded into memory, users can select the corresponding icons in sequence to complete the binding process. Successfully bound SDKs are persistently stored in memory, allowing standard applications to call the SDKs to implement corresponding application functions. Furthermore, the icon corresponding to the successfully bound SDK is permanently displayed on the main interface. If multiple SDKs are successfully bound, multiple icons will be displayed on the main interface.

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

[0072] Taking the payment function as an example, in a real-world scenario, in the SDK configuration interface shown in Figure 2B, 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; and 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, the user is redirected to the main interface shown in Figure 2C, which displays Icon 1 corresponding to payment provider 1 and Icon 2 corresponding to payment provider 2. After the user clicks Icon 1 for the first time, the binding interface corresponding to payment provider 1 is displayed, as shown in Figure 2D. After the user clicks "Bind Now" to display the binding QR code, the user scans the binding QR code using the payment app corresponding to payment provider 1 on their smartphone. The smartwatch then enters the binding interface and prompts the user to perform operations on the phone. After scanning the binding QR code, the smartphone enters the binding process, and the binding is completed based on the user's operation. After the binding is completed, in the main interface shown in Figure 2C, 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, as shown in Figure 2E. Since the SDK has been successfully bound and the authorization is completed, the user can complete the payment normally.

[0073] In another actual scenario, if the user selects icon 2, the smartwatch 110 will call the corresponding SDK2 in the memory through the standard application to generate another payment QR code 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.

[0074] 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 barcodes.

[0075] Typically, the cloud server 130 distributes all SDK resource packages supported by the smartwatch 110 in the current region. Users then select and load SDKs into memory based on their needs and complete the binding process. Consequently, the number of SDK resource packages in memory is greater than the number of SDKs in memory. Users can also unbind successfully bound SDKs and then load other SDKs from the SDK resource packages in memory into memory to complete the binding process. The smartwatch 110 has limited memory space and cannot pre-install a large number of SDKs. By parsing SDK resource packages from memory and dynamically binding SDKs, the number of supported functions can be effectively increased.

[0076] In one embodiment, the SDK unbinding process can be executed on the smartwatch 110 or the smartphone 120. Specifically, the user can select the unbinding operation on the operation interface generated after the standard application calls the SDK. In response to the unbinding request, the smartwatch 110 sends an unbinding instruction to the smartphone via a preset standard application, deletes the unbound SDK from the content of the smartwatch via the preset standard application, and deletes the icon corresponding to the unbound SDK from the main interface via the preset standard application. After receiving the unbinding instruction, the smartphone triggers the corresponding SDK unbinding process.

[0077] Alternatively, SDK unbinding requires user confirmation within a specific terminal application on smartphone 120. Based on the user's selection, smartphone 120 can send an SDK unbinding request to smartwatch 110. Upon receipt, smartwatch 110 unbinds the designated SDK. For unbound SDKs, smartwatch 110 deletes them from memory and the corresponding icon from the main interface. For example, as shown in Figure 2F, if a user wishes to unbind SDK1, smartwatch 110 prompts the user to configure and manage the unbinding process within terminal application 1 on smartphone 120.

[0078] 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 based on the regional information. The smart watch 110 then selects the SDK based on the user's selection and loads it into the memory for dynamic binding. This not only enables payment functions in different regions, but also eliminates the need to pre-install the SDKs of payment applications in each region into the memory in advance, thus saving memory resources. Secondly, each payment provider develops an SDK resource package based on a unified standard. The SDK loaded into the memory is called through a standard application. Manufacturers of terminal devices such as the smart watch 110 do not need to customize and develop their own user interfaces for each payment provider. Instead, they only need to develop the user interface of the standard application based on pre-defined standards, reducing the workload of customized development and version maintenance.

[0079] In one embodiment, after the smartwatch 110 establishes a wireless connection with the smartphone 120, if it is determined that the currently connected smartphone 120 is different from the device previously connected, an SDK initialization process may be executed to delete the existing SDK in the memory of the smartwatch 110 and the existing SDK resource package in the memory of the smartwatch 110. Such operations can effectively protect the privacy or property of each user from being infringed.

[0080] In one embodiment, if smartwatch 110 also supports network functionality and can establish a network connection with cloud server 130, smartwatch 110 can directly send its own device information and region information to cloud server 130. Cloud server 130 then directly sends the associated SDK resource package to smartwatch 110 without intermediary through smartphone 120. After receiving the SDK resource package, smartwatch 110 also stores it in memory. The subsequent binding, use, and unbinding processes can be the same as described above.

[0081] In one embodiment, the smart watch 110 may pre-set multiple standard applications for different application types. For example, a first standard application corresponding to a payment application may be pre-set, and a second standard application corresponding to a communication application may be pre-set. When the cloud server 130 sends the SDK resource package, in addition to the device information and the region 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. The smart watch 120 sends the device information, the region information, and the application type to the cloud server 130. The cloud server 130 then sends the payment-related SDK supported by the smart watch 110 in the current region.

[0082] In one embodiment, after the smartphone 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 smartphone 120 side. After receiving the SDK resource package, the smart watch 110 can load all SDKs into the memory. For example, if the cloud server 130 sends 10 SDK resource packages to the smartphone 120, and the user only wants to perform the configuration and binding process on two of the SDK resource packages, then the smartphone 120 can select these two SDK resource packages and send them to the smart watch 110 without sending all 10 SDK resource packages. Specifically, after the smartphone 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, using Bluetooth connection as an example, the user can click the Configure Watch option indicated by arrow 301 to enter the corresponding Configure Watch interface. In the Configure Watch interface, select the SDK Management option indicated by arrow 302 to view the SDK information corresponding to the SDK resource package issued by cloud server 130. After selecting the required SDK resource package, the user can click Apply to manually select the required SDK resource package from all SDK resource packages issued by cloud server 130. The selected SDK resource package can then be transmitted to smart watch 110 via, for example, Bluetooth. Sending only the currently required SDK resource package to smart watch 110 can reduce power consumption of smart watch 110 and extend standby time.

[0083] FIG4 is a flowchart of another dynamic binding method provided in an embodiment of the present application. This method can be applied to a first terminal device, which includes a lightweight wearable device such as a smartwatch or a sports bracelet, or a terminal device such as a smartphone. As shown in FIG4 , the method may include:

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

[0085] Before this step, the 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, and the second terminal device can establish a connection with the cloud server through the network to interact with 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 can 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.

[0086] In one embodiment, if the first terminal device supports wireless network communication function, it can directly establish a network connection with the cloud server and obtain the SDK resource package from the cloud server without forwarding it through the second terminal device.

[0087] 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 to obtain the SDK corresponding to each resource package and SDK-related SDK information. 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. 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.

[0088] In one embodiment, when a user selects an SDK configuration, he or she may select one or more SDK configuration information 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.

[0089] Step 402: When it is detected that 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 execute a binding process.

[0090] After the first terminal device loads the SDK selected by the user into memory, the main interface will display the corresponding icon for each SDK. 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. The standard application calls the SDK icon corresponding to the selected SDK to generate SDK binding information. The user processes the SDK binding information on the second terminal device to complete the relevant binding process.

[0091] 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 and send them to the second terminal device according to the region 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 based on 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 for 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.

[0092] In an embodiment of the present application, after the first terminal device is connected to the second terminal device, the 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 a standard application, and excessive memory space will not be occupied due to pre-installing multiple SDKs in the memory.

[0093] FIG5 is a flowchart of another dynamic binding method provided in an embodiment of the present application. The method can be applied to a second terminal device. As shown in FIG5 , the method may specifically include:

[0094] Step 501: After establishing a wireless connection with a first terminal device, determine the SDK configuration information of the first terminal device.

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

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

[0097] Step 503: Receive the SDK resource package sent by the cloud server.

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

[0099] For other details, please refer to the description in the other flow charts above.

[0100] Figure 6 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. As shown in Figure 6, the device may include: a receiving module 610, a loading module 620 and a processing module 630.

[0101] The receiving module 610 is configured to receive the SDK resource package sent by the second terminal device and store the SDK resource package in a memory.

[0102] The loading module 620 is used to 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.

[0103] 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 through 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.

[0104] Figure 7 is a schematic diagram of the structure of a dynamic binding device provided in an embodiment of the present application. The device is deployed on a second terminal device to implement the dynamic binding method provided in an embodiment of the present application. As shown in Figure 7, the device may include: a determination module 710, a sending module 720, and a receiving module 730.

[0105] The determination module 710 is configured to determine the SDK configuration information of the first terminal device after establishing a wireless connection with the first terminal device.

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

[0107] The receiving module 730 is used to receive the SDK resource package sent by the cloud server.

[0108] The sending module 720 is further configured 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.

[0109] The specific execution steps of each of the above modules can refer to the description of the method flowchart.

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

[0111] It should be understood that the structure illustrated in the embodiments 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, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

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

[0114] Processor 810 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 810 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 810. If processor 810 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 810 latency, and thus improves system efficiency.

[0115] 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).

[0116] It is understood that the interface connection relationship between the modules illustrated in the embodiment of the present application is merely an illustrative 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 a different interface connection method from the above embodiment, or a combination of multiple interface connection methods.

[0117] 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 provides power to the processor 810 and the internal memory 821.

[0118] The internal memory 821 can be used to store computer executable program code, which includes instructions. The internal memory 821 may include a program storage area and a data storage area. The program storage area may store an operating system, at least one application required for a function, and the like. The data storage area may store data created during the use of the electronic device 800, and the like. 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.

[0119] The processor 810 can execute various functional applications and data processing by running programs stored in the internal memory 821, such as implementing the dynamic binding method provided in the embodiment of the present application.

[0120] An embodiment of the present application also provides a non-transitory computer-readable storage medium, which stores computer instructions. The computer instructions enable the computer to execute the dynamic binding method provided in the embodiment of the present application.

[0121] 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 (Erasable Programmable 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 that can be used by or in combination with an instruction execution system, device or device.

[0122] A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device.

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

[0124] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" 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 can be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art can combine and combine different embodiments or examples described in this specification and features of different embodiments or examples without contradiction.

[0125] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of the technical features being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of such features. Throughout the description of this application, "plurality" means at least two, for example, two, three, etc., unless otherwise specifically defined.

[0126] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment 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 be performed out of 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 those skilled in the art 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 configured to filter out an SDK resource package associated with the SDK configuration information from pre-stored SDK resource packages, and send the filtered SDK resource package to the second terminal device; The second terminal device is further configured to send the SDK resource package sent by the cloud server to the first terminal device; The first terminal device is configured to store the SDK resource package sent by the second terminal device in a memory, and in response to a user selecting an 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, wherein: 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, when a connection is established between the first terminal device and the second terminal device, send software development tool SDK configuration information to the cloud server if this is the first time the first terminal device establishes a connection with the second terminal device, or if current region information of the second terminal device has changed compared to the region information when the second terminal device last established a connection with the first terminal device; The SDK configuration information includes region information.

4. The system according to claim 2, wherein: 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: 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; 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 option 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 a 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 following steps are also included: 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 a preset standard application includes: Use the preset standard application to add one or more options selected by the user in the SDK configuration interface to each SDK resource package. The SDK is loaded into memory; 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 icon corresponding to each SDK loaded into the memory is displayed on the main interface through the preset standard application.

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 usage process.

11. The method according to claim 5, characterized in that After the binding process is completed, the method further includes: Receive 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, including: 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; Determining the SDK configuration information includes: Obtaining device information of the first terminal device; Obtain the current IP address of the second terminal device, and determine the region information 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 includes a stored program, wherein when the program is executed by a processor, the method according to any one of claims 5 to 17 is implemented.

Citation Information

Patent Citations

  • Dynamic binding method and system, electronic equipment and storage medium

    CN118939333A

  • Signature verification method and device of application and electronic device

    CN109934016A

  • Method and system for installing function card on RTOS platform intelligent wearable device

    CN114610336A

  • Model file management method and device, wearable equipment and storage medium

    CN115756508A

  • Optimizing memory for a wearable device

    US20150355800A1