Application permission activation method, medium and electronic equipment

Abstract

The invention relates to the technical field of communication, and provides an application permission activation method, a medium and electronic equipment, which can activate permissions of applications or services in the applications in lightweight equipment through full-magnitude equipment, and promote the application ecology of intelligent wearable equipment and the like to be more prosperous. The method comprises the following steps: in response to an operation of opening a first application installed in first equipment, the first equipment determines a permission activation state of the first application; under the condition that the permission activation state is inactive, the first device sends a first message to the second device, and the first message comprises the device type of the first device and the permission activation state of the first application; when the second device determines that the device type is a preset type and the permission activation state is not activated, a second application in the second device is opened, and the second application and the first application have an association relationship; the second device uses the second application to activate the permission of the first application; and the second device sends a second message to the first device, wherein the second message is used for indicating that the permission of the first application is activated.

Description

Application permission activation method, medium and electronic device

[0001] This application claims priority to Chinese patent application number 202211523920.2, filed with the State Intellectual Property Office on November 30, 2022, entitled “A method and device for activating application permissions,” the entire contents of which are incorporated herein by reference. Furthermore, this application claims priority to Chinese patent application number 202211732378.1, filed with the State Intellectual Property Office on December 30, 2022, entitled “Method, medium, and electronic device for activating application permissions,” the entire contents of which are incorporated herein by reference. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to an application permission activation method, medium, and electronic device. Background Art

[0003] Some wearable devices, such as mobile phones and smart watches, have relatively rich hardware resources and can connect to the Internet independently. In order to attract more ecosystem developers, the manufacturers of these electronic devices support paid app downloads through the app market and support paid service activation through in-app payments and other methods, providing developers with more commercial monetization opportunities, thereby prompting ecosystem developers of mobile phones and the above-mentioned wearable devices to more actively participate in the prosperity of the ecosystem. However, other wearable devices, such as sports watch series, are based on real-time operating systems (RTOS) and have limited hardware resources. They cannot support independent networking, nor can they support independent watch-side application markets. They cannot realize the paid download function of applications and the in-app payment function, which has led to the slow development of the sports watch ecosystem of RTOS systems.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide an application permission activation method, medium, and electronic device, which can activate the permissions of applications or in-application services in lightweight devices through full-scale devices, promote a more prosperous application ecosystem for smart wearable devices, and attract more developers to develop more ecological applications on devices such as sports watches.

[0006] In a first aspect, an embodiment of the present application provides a method for activating application permissions, the method comprising:

[0007] In response to an operation of opening a first application installed in the first device, the first device determines a permission activation state of the first application;

[0008] When the permission activation state is inactive, the first device sends a first message to the second device, where the first message includes the device type of the first device and the permission activation state of the first application;

[0009] When the second device determines that the device type is a preset type and the permission activation state is inactivated, opening a second application in the second device, the second application having an associated relationship with the first application;

[0010] The second device activates the permission of the first application using the second application;

[0011] The second device sends a second message to the first device, where the second message is used to indicate that the permission of the first application has been activated.

[0012] It can be understood that the above-mentioned first device can be the sports watch 200 mentioned below, the second device can be the mobile phone 100 mentioned below, the above-mentioned first application can be the third-party application 2 mentioned below, the above-mentioned second application can be the third-party application 1 mentioned below, and the above-mentioned permission activation status refers to the service activation status mentioned below. The above-mentioned first message can be the device reporting message mentioned below, and the second message can be the activation completion message mentioned below. The operation can be the operation of the user opening the first application on the first device for the first time. In addition, the above-mentioned first application and the second application can be applications from the same manufacturer, for example, the application names of the first application and the second application are the same, or the functions of the first application and the second application are the same (that is, the services running in the first application and the second application are the same), but not limited to this.

[0013] In this way, the second device can use the second application to activate the associated first application or in-application service on the second device through the application market. Furthermore, the second device notifies the first device that the first application or service has been activated, allowing the first device to use the first application or service normally, thus achieving cross-device activation. Thus, even if the first device cannot connect to the Internet and cannot support an independent application market, it can still complete the activation of the installed first application.

[0014] In a possible implementation of the first aspect above, the method further includes: if the permission activation status is inactivated, the first device displays a first application interface, and the first application interface is used to prompt the user to download or open the second application in the second device.

[0015] The first application interface may be the prompt interface described below. Then, the user may be prompted to manually download or open the second application on the second device in a timely manner, so as to subsequently use the second application to activate the first application across devices.

[0016] In a possible implementation of the first aspect above, the method further includes: when the second device opens the second application, sending a third message to the first device, where the third message is used to obtain the device type of the first device and the permission activation status of the first application.

[0017] The third message may be a device query message mentioned below. At this time, the second device actively reports the third message so that the second device can activate the corresponding application in a timely manner.

[0018] In a possible implementation of the first aspect above, the method further includes: when the second device determines that the device type is a preset type and the permission activation state is not activated, displaying a second application interface, the second application interface is used to activate the permission of the first application.

[0019] The second application interface may be the activation interface mentioned below, and may interact with the application market used by the second device.

[0020] In a possible implementation of the first aspect above, the preset type is a lightweight device, such as a sports watch or a bracelet.

[0021] In a possible implementation of the first aspect, the method further includes:

[0022] The first device sends a fourth message to the second device, where the fourth message is used to obtain an installation status of a second application in the second device;

[0023] If the installation status is not installed, the first device sends a fifth message to the second device, where the fifth message is used to instruct the first device to automatically open a download interface of the second application;

[0024] If the installation status is installed, the first device sends a sixth message to the second device, where the sixth message is used to instruct the first device to automatically open the second application.

[0025] The fourth message may be an installation query message, and the fifth and sixth messages may be installation response messages described below. Thus, the second device may automatically open an interface for downloading the second application, or automatically open an interface for the second application, allowing the user to quickly and conveniently activate the first application.

[0026] In a possible implementation of the first aspect, the method further includes:

[0027] The first device displays a third application interface according to the second message, where the third application interface is a normal operating interface of the first application.

[0028] The third application interface may be the running interface mentioned below. Then, after the second device activates the first application across devices, the first device can use the first application normally, that is, use the entire business in the first application or a service in the first application.

[0029] In a possible implementation of the first aspect, the method further includes:

[0030] The first device modifies the permission activation status of the first application to activated according to the second message.

[0031] Therefore, when the first device opens the first application and finds that its permission activation status is activated, the first device can normally display the running interface of the first application and use the business or service in the first application normally.

[0032] In a possible implementation of the first aspect, the permission of the first application is permission to use the entire business of the first application or permission to use a service in the first application.

[0033] In one possible implementation of the first aspect, the activation method for the first application includes at least one of the following: payment activation, facial recognition, fingerprint recognition, and character password authentication. This facilitates authorization management of permissions for the first application, and the user is subsequently authorized to use the first application only after successful activation.

[0034] In one possible implementation of the first aspect, when the first application is activated using a paid activation method, the second device uses the second application to invoke an application market to make an in-app payment to activate the first application's permissions. This allows payment for the first application through the second device, even if the first device does not support payment, enabling cross-device payment and application activation.

[0035] In a possible implementation of the first aspect above, a first distributed communication SDK is deployed in the first device, a second distributed communication SDK is deployed in the second device, and messages between the first device and the second device are transmitted based on the first distributed communication SDK and the second distributed communication SDK.

[0036] Thus, distributed communication between the second application installed on the first device and the associated first application installed on the second device can be achieved, so as to realize the transmission of information such as the device type of the first device and the permission activation status of the first application installed on the first device.

[0037] In a possible implementation of the first aspect, the first message is sent by the first device using the first application to call the interface of the first distributed communication SDK to the interface of the second distributed communication SDK, and the first message is transmitted to the second application through the interface of the second distributed communication SDK;

[0038] The second message is sent by the second device using the second application to call the interface of the second distributed communication SDK to the interface of the first distributed communication SDK, and the second message is transmitted to the first application through the interface of the first distributed communication SDK.

[0039] In this way, information transmission between the first application and the second application can be achieved, thereby enabling the second device to activate the first application in the first device through the second application across devices.

[0040] In a second aspect, an embodiment of the present application provides an application permission activation method, applied to a first device, the method comprising:

[0041] In response to an operation of opening a first application installed in the first device, the first device determines a permission activation state of the first application;

[0042] When the permission activation state is inactive, the first device sends a first message to the second device, where the first message includes the device type of the first device and the permission activation state of the first application;

[0043] The first device receives a second message from the second device, where the second message is used to indicate that the permissions of the first application have been activated, wherein the permissions of the first application are activated by the second device using the second application when the second device determines that the device type is a preset type and the permission activation status is not activated, and the second application has an associated relationship with the first application.

[0044] In a possible implementation of the second aspect, the method further includes:

[0045] If the permission activation status is inactivated, the first device displays a first application interface, which is used to prompt the user to download or open the second application in the second device.

[0046] In a possible implementation of the second aspect, the preset type is a lightweight device.

[0047] In a possible implementation of the second aspect, the method further includes:

[0048] The first device sends a fourth message to the second device, where the fourth message is used to obtain an installation status of a second application installed on the second device;

[0049] If the installation status is not installed, the first device sends a fifth message to the second device, where the fifth message is used to instruct the second device to automatically open a download interface of the second application;

[0050] If the installation status is installed, the first device sends a sixth message to the second device, where the sixth message is used to instruct the second device to automatically open the second application.

[0051] In a possible implementation of the second aspect, the method further includes:

[0052] The first device displays a third application interface according to the second message, where the third application interface is a normal operating interface of the first application.

[0053] In a possible implementation of the second aspect, the method further includes:

[0054] The first device modifies the permission activation status of the first application to activated according to the second message.

[0055] In a possible implementation of the second aspect, the permission of the first application is permission to use the entire business of the first application or permission to use a service in the first application.

[0056] In a possible implementation of the second aspect above, the activation method of the first application includes at least one of the following: a payment activation method, a face recognition method, a fingerprint recognition method, and a character password authentication method.

[0057] In a possible implementation of the second aspect above, a first distributed communication SDK is deployed in the first device, a second distributed communication SDK is deployed in the second device, and messages between the first device and the second device are transmitted based on the first distributed communication SDK and the second distributed communication SDK.

[0058] In a possible implementation of the second aspect, the first message is sent by the first device using the first application to call the interface of the first distributed communication SDK to the interface of the second distributed communication SDK, and the first message is transmitted to the second application through the interface of the second distributed communication SDK.

[0059] The second message is sent by the second device using the second application to call the interface of the second distributed communication SDK to the interface of the first distributed communication SDK, and the second message is transmitted to the first application through the interface of the first distributed communication SDK.

[0060] In a third aspect, an embodiment of the present application provides an application permission activation method, applied to a second device, the method comprising:

[0061] The second device receives a first message from the first device, where the first message includes a device type of the first device and a permission activation status of a first application installed on the first device;

[0062] When the second device determines that the device type is a preset type and the permission activation state is inactivated, opening a second application in the second device, the second application having an associated relationship with the first application;

[0063] The second device activates the permission of the first application using the second application;

[0064] The second device sends a second message to the first device, where the second message is used to indicate that the permission of the first application has been activated.

[0065] In a possible implementation of the third aspect, the method further includes:

[0066] When the second device opens the second application, the second application sends a third message to the first device, where the third message is used to obtain the device type of the first device and the permission activation status of the first application.

[0067] In a possible implementation of the third aspect, the method further includes:

[0068] When the application installed on the second device determines that the device type is a preset type and the permission activation state is not activated, a second application interface is displayed, and the second application interface is used to activate the permission of the application.

[0069] In a possible implementation manner of the third aspect, the preset type is a lightweight device.

[0070] In a possible implementation of the third aspect, the permission of the first application is permission to use the entire business of the first application or permission to use a service in the first application.

[0071] In a possible implementation of the third aspect, the activation method of the first application includes at least one of the following: a payment activation method, a face recognition method, a fingerprint recognition method, and a character password authentication method.

[0072] In a possible implementation of the third aspect, when the activation mode of the first application is a paid activation mode, the second device uses the second application to call the application market to make an in-application payment to activate the permission of the first application.

[0073] In a possible implementation of the third aspect above, a first distributed communication SDK is deployed in the first device, a second distributed communication SDK is deployed in the second device, and messages between the first device and the second device are transmitted based on the first distributed communication SDK and the second distributed communication SDK.

[0074] In a possible implementation of the third aspect, the first message is sent by the first device using the first application to call the interface of the first distributed communication SDK to the interface of the second distributed communication SDK, and the first message is transmitted to the second application through the interface of the second distributed communication SDK;

[0075] The second message is sent by the second device using the second application to call the interface of the second distributed communication SDK to the interface of the first distributed communication SDK, and the second message is transmitted to the first application through the interface of the first distributed communication SDK.

[0076] In a fourth aspect, an embodiment of the present application provides a readable medium having instructions stored thereon, which, when executed on an electronic device, causes the electronic device to execute an application permission activation method such as the second aspect and any possible implementation thereof, or an application permission activation method such as the third aspect and any possible implementation thereof.

[0077] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising: a memory for storing instructions executed by one or more processors of the electronic device, and a processor, which is one of the processors of the electronic device, for executing the application permission activation method as in the second aspect and any possible implementation thereof, or, the application permission activation method as in the third aspect and any possible implementation thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] FIG1 is a schematic diagram showing a scenario in which a mobile phone or a smartwatch downloads an application through an application market according to some embodiments of the present application;

[0079] FIG2 shows a schematic diagram of an application download interface of an application market in a mobile phone according to some embodiments of the present application;

[0080] FIG3 shows a schematic diagram of an interface for paid application downloading in a smartwatch according to some embodiments of the present application;

[0081] FIG4 shows a schematic diagram of a scenario in which a mobile phone or smartwatch obtains services from a third-party application APP based on an application market according to some embodiments of the present application;

[0082] FIG5 is a schematic diagram showing interface changes of an in-app payment process in a smartwatch according to some embodiments of the present application;

[0083] FIG6 shows a software structure block diagram of a mobile phone according to some embodiments of the present application;

[0084] FIG7 shows a schematic diagram of an application permission activation scenario according to some embodiments of the present application;

[0085] FIG8 is a schematic diagram showing a flow chart of a method for activating application permissions according to some embodiments of the present application;

[0086] FIG9 shows a schematic diagram of an application permission activation scenario according to some embodiments of the present application;

[0087] FIG10 is a schematic diagram showing a flow chart of a method for activating application permissions according to some embodiments of the present application;

[0088] FIG11 shows a schematic diagram of an application permission activation scenario according to some embodiments of the present application;

[0089] FIG12 is a schematic diagram showing a flow chart of a method for activating application permissions according to some embodiments of the present application;

[0090] FIG13 is a flow chart showing a method for activating application permissions according to some embodiments of the present application;

[0091] FIG14 shows a schematic structural diagram of a mobile phone according to some embodiments of the present application;

[0092] FIG15 shows a schematic structural diagram of a sports watch according to some embodiments of the present application. DETAILED DESCRIPTION

[0093] The illustrative embodiments of the present application include, but are not limited to, an application permission activation method, apparatus, medium, and electronic device.

[0094] The application permission activation method provided in the embodiments of the present application can be applied to scenarios where an application (Application, App) is activated and / or an application's internal services are activated. For example, an application's internal services may be props, services, etc. It is understood that after an application or an application's internal services are activated, the permissions of the application or service are opened, and the user can use the application or service normally.

[0095] In some embodiments, the above-mentioned application permission activation scenarios include but are not limited to: activating an application when an application is first launched in an electronic device, or activating an application when an electronic device is restarted after updating an application, or activating an internal service when the service is used for the first time in an application of the electronic device.

[0096] In some embodiments, the above-mentioned application permission activation methods include but are not limited to: payment activation, face recognition activation, fingerprint authentication activation, character password activation, etc.

[0097] As an example, in the paid activation mode, a payment is made to activate an application to be activated when the application to be activated is used, or a payment is made to activate a service to be activated in the application when the service to be activated is used.

[0098] As an example, in other activation methods, authentication activation is performed when using the application to be activated in an electronic device or when using the service to be activated within the application, such as determining that the real-time collected facial image, fingerprint information, and character password are the same as the corresponding preset information, thereby activating the application or the service.

[0099] Next, we will introduce the technologies related to paid purchase of applications and in-app services.

[0100] In some related technologies, mobile phones and smart watches can independently pay to download applications through the application market. Referring to Figure 1, it is a schematic diagram of the scenario in which a mobile phone or smart watch downloads an application through the application market. Specifically, mobile phones and smart watches can log in to the device manufacturer's account in the device manufacturer's independent application market, and based on the account and the application's identity identification number (Identity document, ID) and the cloud application market server, complete the process of successful downloading after payment. That is, the mobile phone or smart watch uses the application market APP to interact with the application market server based on the account + APP ID + payment method and download the application indicated by the APP ID from the server. Then, when the mobile phone and smart watch pay to download the application, the application is activated and the user can use the application normally.

[0101] The app market, also known as an app store, is a software distribution channel through which ordinary users can browse and download various applications. The app market is the app distribution channel that connects app developers and users and is the foundation for building an ecosystem.

[0102] 2 , a schematic diagram of the application download interface of the application market in the mobile phone is shown. The interface 20 includes information of multiple applications, such as the application's icon, name (i.e., APP ID), category, profile information, and installation button or paid installation button. For example, the interface 20 shown in FIG2 includes multiple applications such as applications A, B, and D. It can be understood that some applications are free applications that can be directly downloaded and installed by clicking the install button, while other applications are paid applications that can be downloaded and installed after clicking the paid installation button. For example, application A in the interface 20 is a free application, and the user can trigger the mobile phone to download application A from the application market server by clicking the "Install" button 21. Application B in the interface 20 is a paid application, and the user can trigger the mobile phone to pay and download application B from the application market server by clicking the "￥6" button (i.e., paid installation button) 22.

[0103] 3 shows a schematic diagram of the paid app download interface on a smartwatch. This interface 30 includes information about application B, such as a rating of 3.3 and a size of 20.28MB, as well as a "￥6" button (i.e., a pay-to-install button) 31. When a user clicks "￥6" button 31, the smartwatch pays and downloads application B from the app market server.

[0104] It is understandable that when performing payment operations on a mobile phone or smart watch, users are required to enter sensitive information such as payment passwords.

[0105] The aforementioned solution for mobile phones and smartwatches to independently download paid apps through the app market relies on the devices being able to connect to the internet, support an independent app market, and store sensitive information at a high security level. This places high demands on the device's hardware capabilities and computing power. Obviously, hardware-constrained devices like sports watches cannot independently complete paid app activation.

[0106] In other related technologies, when mobile phones and smart watches use a third-party application APP, they can independently pay and obtain services in the third-party application through the application market. Device manufacturers provide in-app payment (in app purchase, IAP) accessories (kit), and ecological applications (i.e., third-party application APPs provided in the application market) integrate IAP kits to provide in-app services, such as purchasing props. Then, the mobile phone or smart watch can interact with the cloud server through the IAP kit and the independent application market on the smart watch side to realize in-app payment. Referring to Figure 4, it is a schematic diagram of the scenario in which a mobile phone or smart watch obtains services in a third-party application APP based on the application market. Specifically, the third-party application APP can obtain the service information to be paid from the application market APP through the IAP kit, and then the application market APP interacts with the application market cloud server based on the account + APP ID + payment method. After the payment is completed, the application market APP notifies the third-party application APP through the IAP kit to allow the provision of services, that is, to allow the use of the corresponding services.

[0107] It can be understood that IAP kit is a middleware for cross-application communication between third-party applications and application markets, supporting in-app payment in third-party applications through communication between third-party applications and application markets to purchase props and other services in the third-party applications.

[0108] FIG5 illustrates a schematic diagram of the interface changes during the in-app payment process on a smartwatch. FIG5 shows an interface 51 of a third-party application M. This interface 51 includes items 511 and 512, some of which are pending payment, while others are already paid for or require no payment. For example, item 511 is a pending payment item. After a user clicks the icon for item 511, the smartwatch may be redirected to a purchase interface 52, which includes a prompt (e.g., "Coupon Item 1"), "￥3," and a purchase button 521. After the user clicks purchase button 521, the smartwatch may be redirected to a payment interface 53, which includes a prompt "In-App Payment" and a payment QR code 531. The user completes payment by scanning the payment QR code 531 on the smartwatch or using a mobile phone or other device. Once payment is complete, item 511 becomes active and the user can use it normally. At this time, the above-mentioned props 511 are services to be paid for within the application.

[0109] The aforementioned solution for mobile phones and smartwatches to independently pay to activate in-app services relies on the devices being able to connect to the internet, support an independent app market, and store sensitive information with a high level of security. Furthermore, the devices must provide an IAP kit for inter-app communication and support interface communication between third-party apps and the independent app market. This places high demands on the device's hardware capabilities and computing power. Obviously, hardware-constrained devices like sports watches cannot independently process in-app payments, nor can they independently activate in-app services.

[0110] It should be noted that mobile phones and smartwatches are typically full-scale devices with rich hardware resources. However, devices like sports watches are typically lightweight devices with limited hardware resources, lack internet connectivity, and lack independent app stores, making them unable to independently activate in-app purchases.

[0111] In order to overcome the above problems, an embodiment of the present application provides an application permission activation method. When a lightweight first device such as a sports watch cannot realize the paid activation function of the ecological application, the application or in-application service in the first device is activated across devices through a full-scale second device such as a mobile phone. Specifically, in this method, the second device can obtain the device type of the first device and the service activation status of the first application in the first device through the deployed distributed communication SDK. If it is not activated and the first device is a preset type such as a sports watch, the second device uses the second application to activate the first application or in-application service, for example, to complete the payment for the first application or in-application service. Among them, the second application is associated with the first application, such as an application from the same manufacturer. Furthermore, the second device notifies the first device through the above-mentioned distributed communication SDK that the first application or the corresponding in-application service has been activated, so that the first device can use the first application or in-application service normally to realize cross-device activation of the application. In this way, the application ecology of smart wearable devices is promoted to be more prosperous, and more developers are attracted to develop more ecological applications on the side of devices such as sports watches.

[0112] It is understood that the first application and the second application may be applications from the same manufacturer, for example, the first application and the second application may have the same application name, or the first application and the second application may have the same functions (i.e., the first application and the second application may run the same business), but the present invention is not limited thereto. As an example, the first application and the second application may be the mobile phone version and the watch version of the same application, respectively.

[0113] The first device provided in the embodiment of the present application includes but is not limited to the above-mentioned sports watch, and can also be a bracelet, an Internet of Things (IoT) device, etc. In some embodiments, the above-mentioned first device can be a lightweight device, generally using an ultra-low power consumption, long standby, low-cost microprocessor. In addition, the above-mentioned first device is limited by hardware and can run a real-time operating system (RTOS) system. Usually, the first device does not support networking and does not support an independent application market, so it is impossible to realize activation functions such as payment functions of ecological applications and in-app payment functions.

[0114] In some embodiments, the first device can obtain one or more application software packages from other electronic devices, thereby installing the one or more applications on the first device. For example, a sports watch can be pre-connected to a mobile phone or computer and obtain one or more application software packages from the mobile phone or computer. However, even if an application is installed on the first device, it cannot independently activate the application or the services within the application, such as being unable to complete activation operations for paid features.

[0115] The second device provided in the embodiments of the present application includes, but is not limited to, the aforementioned mobile phone, and may also be other devices such as a tablet computer and a laptop computer. In some embodiments, the aforementioned second device may be a full-scale device (or heavyweight device), typically having a large-capacity battery, not requiring ultra-low power consumption, and requiring high performance to ensure a good user experience. Furthermore, the second device typically supports networking and supports downloading and activating applications and in-application services through an application market or the like.

[0116] In some embodiments of the present application, the first device and the second device may be from the same manufacturer. In addition, a device management application is installed in the second device for managing applications in the first device.

[0117] As an example, in the embodiments of this application, the first device is a sports watch, and the second device is a mobile phone. Furthermore, the mobile phone has a management application installed, such as a sports health application, for managing the installation of applications on the sports watch connected to the mobile phone. It will be appreciated that in some embodiments, the sports health application can serve as an application market on the sports watch.

[0118] In the following embodiments of the present application, the interaction between the mobile phone 100 and the sports watch 200 will be taken as an example to illustrate the application permission activation method provided by the present application.

[0119] In some embodiments, both the mobile phone 100 and the sports watch 200 are deployed with a distributed communication software development kit (SDK), a type of middleware that provides a distributed interface to enable distributed communication between the mobile phone 100 and the sports watch 200. The distributed communication SDK can be deployed within the software architecture of the mobile phone and the sports watch. More specifically, the mobile phone 100 and the sports watch 200 utilize the distributed interface to transmit messages using communication technologies such as Bluetooth.

[0120] In some embodiments, the software system of the mobile phone 100 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. In the embodiment of the present invention, the Android system with a layered architecture is used as an example to illustrate the software structure of the mobile phone 100.

[0121] FIG6 is a block diagram of the software structure of the mobile phone 100 according to an embodiment of the present application.

[0122] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0123] The application layer can include a series of application packages.

[0124] As shown in Figure 6, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, application market, device management application (such as sports and health application), watch third-party application (such as the first application mentioned above, i.e., an ecological application), etc. Among them, the application market is used to download and install third-party applications on the mobile phone 100 side. The device management application is used to download third-party applications on the watch 200 side, i.e., watch-side third-party applications.

[0125] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0126] As shown in FIG6 , the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, an IAP kit, and a distributed communication SDK.

[0127] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, take screenshots, etc.

[0128] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0129] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0130] The phone manager is used to provide communication functions of the mobile phone 100, such as management of call status (including answering, hanging up, etc.).

[0131] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0132] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically without user interaction. For example, the Notification Manager is used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include displaying text messages in the status bar, emitting alert sounds, vibrating electronic devices, or flashing indicator lights.

[0133] The IAP kit is used to support the mobile phone 100 to communicate with the application market through the third-party application on the mobile phone side, thereby realizing the in-application payment function.

[0134] The distributed communication SDK is used to transmit information about applications or services to be activated in the sports watch 200 (such as service activation status or device type) to the mobile phone 100, and return information about the activation of the corresponding applications or services by the mobile phone 100 to the sports watch.

[0135] Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

[0136] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0137] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0138] The system library can include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0139] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0140] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0141] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0142] A 2D graphics engine is a drawing engine for 2D drawings.

[0143] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0144] The software system shown in Figure 6 involves application presentation using sharing capabilities (such as gallery and file management), a targeted sharing module that provides sharing capabilities, and an application framework layer that provides WLAN services and Bluetooth services, as well as the kernel and bottom layers that provide WLAN Bluetooth capabilities and basic communication protocols.

[0145] Next, referring to FIG. 7 , there is shown a schematic diagram of an application permission activation scenario provided in an embodiment of the present application.

[0146] As shown in FIG7 , the mobile phone 100 includes the following applications:

[0147] App Market: You can download and install third-party apps on your phone (referred to as third-party app 1, i.e., the second app).

[0148] Device management application: You can download and install third-party applications on the sports watch side (referred to as third-party application 2, i.e. the first application).

[0149] Third-party application 1: It can integrate the distributed communication SDK of the equipment manufacturer and realize distributed communication with the third-party application (i.e., third-party application 2) on the sports watch 200 side, obtain the device type on the sports watch 200 side and the activation status of the third-party application 2, and help the third-party application 2 on the sports watch 200 side to realize business activation and open application permissions through application permission activation methods such as download payment or in-app payment.

[0150] As shown in FIG7 , the watch 200 includes the following applications:

[0151] Third-party application 2: Through the interface of the distributed communication SDK on the sports watch 200 side, it communicates with the third-party application 1 on the mobile phone 100 side in a distributed manner, and reports the activation status of the third-party application 1 on the sports watch 200 side. After the third-party application 1 on the mobile phone 100 side completes the payment and other activation services, it modifies the service activation status on the sports watch 200 side, so that the user can use the services of the third-party application 2 normally.

[0152] It can be understood that the third-party application 1 on the mobile phone 100 side and the third-party application 2 on the sports watch 200 side are associated applications, such as the mobile phone version and watch version of the same application.

[0153] Specifically, as shown in the scenario of Figure 7, the mobile phone 100 can download the watch version of the above-mentioned third-party application (i.e., third-party application 2) through the device management application, connect to the sports watch 200 via Bluetooth, and then send the watch version of the third-party application 2 to the sports watch 200 for installation, thus realizing "1. Download and install" shown in Figure 7. The mobile phone version of the third-party application 1 on the mobile phone 100 side and the watch version of the third-party application 2 on the sports watch 200 side communicate through the distributed communication SDK to activate the third-party application 2 on the sports watch 200 side, thus realizing "2. Activate the watch-side application" shown in Figure 7. In addition, the mobile phone 100 side downloads and installs the third-party application 1 through the application market, thus realizing "3. Download and install" shown in Figure 7. Furthermore, the third-party application 1 on the mobile phone side 100 activates the service to be activated in the third-party application 1 through activation methods such as activation service payment in the application market, thus realizing "4. Activate service payment" shown in Figure 7.

[0154] Next, based on the scenario shown in Figure 7, a flow chart of an application permission activation method provided by an embodiment of the present application is shown with reference to Figure 8. Specifically, the application permission activation method shown in Figure 8 mainly uses the paid activation method as an example to illustrate the process of activating the in-application service of the third-party application 2.

[0155] Specifically, the method shown in FIG8 includes the following steps:

[0156] S0: The mobile phone 100 and the sports watch 200 interact to download a third-party application 2.

[0157] In some embodiments, in S0, the mobile phone 100 downloads the third-party application 2 on the sports watch side 100 for free through the device management application, and sends the third-party application 2 on the sports watch 200 to the sports watch 200 via Bluetooth, and the sports watch 200 installs the third-party application 2.

[0158] In some embodiments, in S0, the mobile phone 100 downloads the third-party application 2 on the sports watch side 100 for free and the sports watch 200 installs the third-party application 2, and the mobile phone 100 can also download the third-party application 1 on the mobile phone side from the application market for free.

[0159] For example, the device management application may be a sports health application that can manage the connected sports watch 200 .

[0160] S1: Launch a third-party application for the first time 2.

[0161] In some embodiments, the sports watch 200 may be installing and launching the third-party application 2 for the first time, or launching the third-party application 2 for the first time after an update.

[0162] S2: Determine the service activation status of the third-party application 2. If it is not activated, display a prompt message. Thus, the user is prompted to download the third-party application 1 on the mobile phone 100 side and activate the third-party application 2.

[0163] In some embodiments, the service activation state of the third-party application 2 corresponds to the permissions of the third-party application 2. The permissions can be opened only after the third-party application 2 is activated. In addition, the service activation state can also be called the permission activation state.

[0164] In some embodiments, the service activation status of third-party application 2 may refer to the activation status of the entire service of third-party application 2, that is, the permission for use of the entire service of third-party application 2 as determined by the service activation status. Therefore, if the service activation status of third-party application 2 is activated, it indicates that the permissions for the entire service of third-party application 2 are open and can be used; if the service activation status is inactivated, it indicates that the permissions for the entire service of third-party application 2 are not open and cannot be used normally.

[0165] In some embodiments, the service activation status of third-party application 2 may refer to the activation status of a service (denoted as service 1) within third-party application 2, i.e., the service activation status corresponds to the usage permission of service 1. Therefore, when the service activation status of third-party application 2 is activated, it indicates that the permission of service 1 in third-party application 2 is open and can be used; when the service activation status is inactivated, it indicates that the permission of service 1 in third-party application 2 is not open and cannot be used normally.

[0166] S3a: If the third-party application 1 on the mobile phone 100 side has not been downloaded, the mobile phone 100 jumps to the download interface; if it has been downloaded, the third-party application 1 on the mobile phone 100 side is started.

[0167] In some embodiments, the third-party application 2 on the sports watch 200 side obtains a distributed interface message, and through the distributed interface message, determines that the third-party application 1 on the mobile phone 100 side has not been downloaded, then sends a message to the application market on the mobile phone 100 side, and jumps to the download interface of the third-party application 1 on the mobile phone 100 side; if the third-party application 1 on the mobile phone 100 side has completed the download, then the third-party application 1 on the mobile phone 100 side is directly pulled up to start the activation process.

[0168] It is understood that the sports watch 200 is deployed with a distributed interface corresponding to the distributed communication SDK on the mobile phone 100. The third-party application 2 of the sports watch 200 can use the distributed interface to perform distributed communication with the distributed communication SDK in the mobile phone 100 to obtain distributed interface messages.

[0169] S3b: Start third-party application 1.

[0170] It is understandable that when the third-party application 1 is not currently downloaded on the mobile phone 100 , the user can manually download or start the third-party application 1 .

[0171] S4: The mobile phone 100 queries the device type and whether the third-party application 2 on the sports watch 200 has been activated.

[0172] It is understandable that the mobile phone 100 can query the device type of the currently connected device, such as watch information.

[0173] S5: If the device type is a sports watch and is not activated, the mobile phone 100 starts the activation service and completes the in-app payment.

[0174] In some embodiments, after downloading and launching third-party application 1 on the mobile phone 100, the third-party application 1 can be used to call the interface of the distributed communication SDK to obtain the device type of the connected sports watch 200 and the activation status of third-party application 2 on the sports watch 200. If the device type is a sports watch and third-party application 2 is inactive, the mobile phone 100 initiates the activation service and completes the in-app payment for third-party application 2 on the mobile phone 100, thus completing the commercial closed loop of third-party application 2 on the sports watch 200.

[0175] In some embodiments, for a third-party application 1 that can only be downloaded after payment, the mobile phone 100 first pays for the third-party application 1 in the application market, then downloads the third-party application 1, and then starts the third-party application 1 to activate the permission of the third-party application 2 using the third-party application 1.

[0176] In some embodiments, a device's information may include its type, such as sports watch or smartwatch. If sports watch 200 indicates a sports watch and third-party application 2 is not yet activated, mobile phone 100 may launch third-party application 1 to complete activation, thereby activating the services of third-party application 2 on sports watch 200 and obtaining access to the activated services of third-party application 2. If sports watch 200 indicates a smartwatch, mobile phone 100 will not perform any processing, for example, there is no need to download third-party application 1.

[0177] In some embodiments, a device's device type can include lightweight or full-scale devices. Therefore, if the sports watch 200 is a lightweight device and third-party application 2 is not activated, the mobile phone 100 can launch third-party application 1 to complete the activation, thereby activating the services of third-party application 2 on the sports watch 200 side and obtaining permission to use the activated services of third-party application 2. If the sports watch 200 is a full-scale device, the mobile phone 100 will not process the request, for example, there is no need to download third-party application 1.

[0178] In some embodiments, the mobile phone 100 can call the IAP Kit middleware to complete the in-application payment for the in-application service (such as service 1) in the third-party application 1.

[0179] S6: After the in-app payment is completed, the mobile phone 100 and the sports watch 200 communicate to complete the activation.

[0180] It can be understood that the mobile phone 100 can use the third-party application 1 to call the interface of the distributed communication SDK to notify the sports watch 200 that the third-party application 2 has been activated.

[0181] S7: The sports watch 200 modifies the service activation status of the third-party application 2 to activated. In addition, the sports watch 200 may also prompt the user that the activation is complete and can be used normally. For example, the sports watch 200 may display a prompt message "Activation completed, can be used normally".

[0182] S8: The sports watch 200 starts the third-party application 2 again.

[0183] S9: The sports watch 200 determines that the service activation status is activated and uses the third-party application 2 normally.

[0184] Specifically, the sports watch 200 normally uses a certain in-application service of the third-party application 2, or the entire service of the third-party application 2.

[0185] In this way, based on the service activation status and device type of third-party application 2 on the sports watch 200, third-party application 1 on the phone 100 initiates in-app payment for the third-party application 2 on the sports watch 200 if the device type is a sports watch and third-party application 2 is not activated, completing the activation service for third-party application 2 on the watch. This allows sports watches to activate paid services within third-party applications without requiring a separate app store or internet connection.

[0186] Based on the method shown in FIG8 , FIG9 is a schematic diagram of an application permission activation scenario provided by an embodiment of the present application. FIG9 illustrates a scenario where the device management application is a sports and health application, third-party application 1 on the mobile phone 100 is third-party application 1, and third-party application 2 on the sports watch 200 is a third-party application 2 with a related relationship. The scenario is described as follows: a user manually operates the mobile phone 100 to open the application market and download the third-party application 1 on the mobile phone 100.

[0187] As shown in Figure 9, the third-party app 2 on the sports watch 200 is not activated. When it is opened for the first time, the user is prompted. The sports watch 200 displays a prompt interface 91 including a message such as "Please click to download / or open the mobile app to activate." Subsequently, based on the installation status of the third-party app 1 on the mobile phone 100, the user is redirected to the download interface 92 of the app market on the mobile phone 100 to download the third-party app 1. The third-party app 1 is then launched and the third-party app 1 interface 93 is displayed. If the mobile phone 100 determines that the connected sports watch 200 is a sports watch and that the third-party app 2 on the watch is not activated, the activation service payment is initiated and payment is made using the payment QR code 94. Upon successful payment, the third-party app 2 on the sports watch 200 is activated and the service activation status of the third-party app 2 on the watch is modified. Subsequently, when the sports watch 200 opens the third-party app 2 on the watch, the running interface 95 of the third-party app 2 on the watch is displayed normally, indicating that the user has permission to use the third-party app 2.

[0188] Next, the specific process of the application permission activation method in the scenario shown in Figure 9 is described in conjunction with Figure 10. Specifically, the method shown in Figure 10 includes the following steps:

[0189] S1001: The mobile phone 100 downloads the third-party application 2 and sends it to the watch 200 for installation.

[0190] Among them, the mobile phone 100 can use the third-party application 2 on the sports health application watch side, and send the third-party application 2 to the sports watch 200 via Bluetooth for installation.

[0191] S1002: When the sports watch 200 opens the watch-side third-party application 2 for the first time, a prompt message is displayed to remind the user to download / open the mobile phone-side third-party application.

[0192] At this time, the service activation status of the watch-side third-party application in the sports watch 200 is inactive.

[0193] In some embodiments, the sports watch 200 may display the prompt interface 91 shown in FIG. 9 .

[0194] S1003: The user manually downloads the third-party application 1 on the mobile phone 100. If the device type is a sports watch and the service activation status of the third-party application 2 is not activated, the IAP kit is called to make in-app payments; if it is a smart watch, no payment is made.

[0195] Among them, the mobile phone 100 downloads the mobile phone side third-party application 1 through the application market under manual operation of the user.

[0196] It can be understood that the mobile phone 100 can obtain the service activation status of the watch-side third-party application 2 in the sports watch 200 and the device type of the sports watch 200 through the interface of the distributed communication SDK.

[0197] In some embodiments, the mobile phone 100 can send a device query message to the sports watch 200 through the interface of the distributed communication SDK to obtain the device type of the sports watch 20 and the service activation status of the third-party application 2. In turn, the sports watch 200 sends a device reporting message to the mobile phone 100 through the distributed interface, and the device reporting message includes the device type of the sports watch 20 and the service activation status of the third-party application 2.

[0198] In some embodiments, when the sports watch 200 opens the watch-side third-party application 2 for the first time and is not activated, the sports watch 200 can actively report the above-mentioned device reporting message to the mobile phone 100 through the distributed communication SDK.

[0199] In some embodiments, the mobile phone 100 can obtain the device reporting message sent by the sports watch 200 according to the interface of the distributed communication SDK, and determine whether the device type of the sports watch 20 is a sports watch, and whether the service activation status of the third-party application 2 is inactivated.

[0200] In some other embodiments, if the third-party application 1 on the mobile phone side requires payment before downloading, then in S1003, the mobile phone 100 can first complete the payment for the third-party application 1 on the mobile phone side in the application market and then download it to activate the third-party application 2 on the mobile phone 100 side.

[0201] S1004: Payment is completed, the mobile phone 100 opens the third-party application 1 on the mobile phone side, and the watch side of the sports watch 200 jumps to the normal usage interface of the third-party application 2.

[0202] It is understandable that the mobile phone 100 can notify the sports watch 200 through the interface of the distributed communication SDK that the third-party application 2 has been activated and can be used normally.

[0203] In this way, in the scenario where the third-party application 2 of the sports watch 200 needs to be activated, the sports watch 200 provides a prompt message to prompt the user to manually download the mobile-side third-party application 2 in the mobile phone 100, thereby realizing the subsequent cross-device application activation process.

[0204] Based on the method shown in FIG8 , FIG11 is a schematic diagram of an application permission activation scenario provided by an embodiment of the present application. FIG11 illustrates a scenario in which the device management application is a sports and health application, and illustrates a solution in which the mobile phone 100 automatically jumps to the download interface of a third-party application 1 in the application market, or automatically opens the third-party application 1 on the mobile phone 100 side.

[0205] As shown in Figure 11, the third-party app 2 on the sports watch 200 is not activated. When it is opened for the first time, the user is prompted. The sports watch 200 prompt interface 111 includes the prompt message "Please click to download / or open the mobile app to activate." Subsequently, based on the installation status of the third-party app 1 on the mobile phone 100, the user is redirected to the third-party app 1 interface 112 on the mobile phone 100, indicating that the third-party app 1 is already installed on the mobile phone 100. The mobile phone 100 determines that the connected device type is a sports watch and that the third-party app 2 on the watch is not activated. It then initiates the activation service payment and proceeds to pay using the payment QR code 113. The payment is successful, activating the third-party app 2 on the sports watch 200 and modifying the service activation status of the third-party app 2 on the watch. When the sports watch 200 subsequently opens the third-party app 2 on the watch, the third-party app 2 interface 114 on the watch will display normally, and the user will have permission to use the third-party app 2 normally.

[0206] Next, the specific process of the application permission activation method in the scenario shown in Figure 11 is described in conjunction with Figure 12. Specifically, the method shown in Figure 12 includes the following steps:

[0207] S1201: The mobile phone 100 downloads the third-party application 2 and sends it to the sports watch 200 for installation.

[0208] Among them, the mobile phone 100 can download the third-party application 2 through the sports health application, and send the third-party application 2 on the sports watch side to the sports watch 200 via Bluetooth for installation.

[0209] S1202: The sports watch 200 opens the watch-side third-party application 2 for the first time and determines the installation status of the mobile phone-side third-party application 1 through the distributed interface.

[0210] In some embodiments, the sports watch 200 can send an installation query message to the interface of the distributed communication interface SDK in the mobile phone 100 through the distributed interface to request to query the installation status of the third-party application in the mobile phone 100. Then, the mobile phone 100 receives an installation response message returned by the distributed communication interface SDK, which is used to indicate whether the corresponding mobile-side third-party application is installed in the mobile phone 100.

[0211] S1203: If the third-party application 1 on the mobile phone side is not installed, the sports watch 100 prompts the user to install it, such as displaying a prompt message to remind the user: Please click to download the third-party application on the mobile phone side to activate the third-party application on the watch side.

[0212] In some embodiments, the sports watch 200 can send a download redirect message to the distributed communication interface SDK in the mobile phone 100 via the distributed interface, requesting the mobile phone 100 to open the download interface of the mobile-side third-party application 1 in the application market. The download redirect message includes the ID (e.g., name) of the third-party application 1. The mobile phone 100 can then automatically jump to the download interface of the mobile-side third-party application 1 in the application market based on the download redirect message. Furthermore, the user can click a control such as "Download" in the download interface to trigger the mobile phone 100 to start downloading the mobile-side third-party application 1.

[0213] S1204: If the mobile phone side third-party application 1 has been installed, the sports watch 20 prompts to start, such as reminding the user: Please click to open the mobile phone side third-party application 1 to activate it. The user clicks to open the mobile phone side third-party application 1 in the mobile phone 100, and the mobile phone 100 jumps to open the mobile phone third-party application 1.

[0214] In some embodiments, the sports watch 200 can send a start jump message to the distributed communication interface SDK in the mobile phone 100 through the distributed interface to request the mobile phone 100 to open the mobile-side third-party application 1. The start jump message includes the ID (such as the name) of the third-party application 1. Then, the mobile phone 100 can open the third-party application 1 according to the start jump message and automatically jump to the interface of the third-party application 1.

[0215] S1205: The mobile phone 100 installs / opens the third-party application 1 on the mobile phone side under the user's operation. When the device type of the sports watch 200 is a sports watch and the third-party application 2 is not activated, the IAP kit is called for in-app payment; if the device type is a smart watch, no payment is made.

[0216] S1206: The user downloads the third-party application 1 on the mobile phone 100, and then opens the third-party application 1. The sports watch 200 jumps to the normal usage interface of the third-party application 2.

[0217] It is understandable that the mobile phone 100 can send an activation completion message through the interface of the distributed communication SDK to notify the sports watch 200 that the third-party application 2 has been activated and can be used normally.

[0218] In this way, in the scenario where the third-party application 2 of the sports watch 200 needs to be activated, the sports watch 200 triggers the mobile phone 100 to automatically open the download interface of the third-party application 1 on the mobile phone side or automatically open the running interface of the third-party application 1 on the mobile phone side, thereby facilitating the subsequent cross-device activation process of the third-party application 2.

[0219] Next, the application permission activation method provided in the embodiment of the present application is described in detail without being limited to paid activation methods or other activation methods.

[0220] 13 , a method for activating application permissions provided in an embodiment of the present application includes the following steps:

[0221] S1301: The sports watch 200 opens a third-party application 2.

[0222] For example, the user clicks the icon of the third-party application 2 on the interface of the sports watch 200 to trigger the sports watch 200 to open the third-party application 2. Usually, the sports phone 100 opens the third-party application 2 for the first time.

[0223] In some embodiments, the sports watch 200 may obtain the third-party application 2 from the mobile phone 100 in advance, and the mobile phone 100 may download the third-party application 2 from the sports health application and then send it to the sports watch 200.

[0224] S1302: The sports watch 200 determines the service activation status of the third-party application 2.

[0225] The service activation status may be the permission activation status of the entire service of the third-party application 2 and the permission activation status of an in-application service in the third-party application 2, such as service 1.

[0226] In some embodiments, the sports watch 200 can record the service activation status of the third-party application 2 and update the service activation status information in a timely manner when the service activation status changes.

[0227] If it is not activated, the process proceeds to S1303 . If it is activated, the sports watch 200 continues to display the interface of the third-party application 2 and is used normally.

[0228] S1303 : The sports watch 200 displays a prompt interface, which is used to prompt the user to open or download the third-party application 1 on the mobile phone 100 .

[0229] As an example, the prompt interface displayed by the sports watch 200 may be the prompt interface 91 in FIG. 9 or the prompt interface 111 in FIG. 11 .

[0230] S1304: If the mobile phone 100 has not installed the third-party application 1, the mobile phone 100 opens the download interface of the mobile phone-side third-party application 1 in the application market.

[0231] In some embodiments, before S1306, the sports watch 200 sends an installation query message to the mobile phone 100 via the distributed interface, requesting to inquire about the installation status of the third-party application 1 on the mobile phone 100. Subsequently, the sports watch 200 receives an installation response message from the mobile phone 100. The mobile phone 100 can use the installation response message returned by the distributed communication interface SDK to indicate whether the corresponding mobile-side third-party application 1 is installed on the mobile phone 100. In S1306, if the mobile phone 100 does not have the third-party application 1 installed, the sports watch 200 sends a download redirect message to the mobile phone 100, instructing the mobile phone 100 to automatically open the download interface of the mobile-side third-party application 1 in the application market. The download redirect message includes the ID (e.g., name) of the third-party application 1. Based on the download redirect message, the mobile phone 100 automatically redirects to the download interface of the mobile-side third-party application 1 in the application market. Furthermore, the user can click a control such as "Download" in the download interface to trigger the mobile phone 100 to begin downloading the mobile-side third-party application 1.

[0232] In other embodiments, the sports watch 200 may display a prompt message to prompt the user to manually download or open the third-party application 1.

[0233] In some other embodiments, the sports watch 200 can display a QR code corresponding to the interface for downloading the third-party application on the mobile phone side, and the mobile phone 100 can scan the QR code to open the download interface. After scanning the QR code, the mobile phone 100 can also determine whether the application is installed. If the application is installed, the corresponding third-party application can be opened.

[0234] S1305 : If the mobile phone 100 has installed the third-party application 1 , the mobile phone 100 opens the third-party application 1 .

[0235] It is understandable that the mobile phone 100 can open the third-party application 1 automatically or manually.

[0236] S1306: The third-party application 1 in the mobile phone 100 sends a device query message to the third-party application 2 in the sports watch 200 to request the device type of the sports watch 20 and the service activation status of the third-party application 2.

[0237] S1307 : The third-party application 1 in the mobile phone 100 receives a device reporting message from the third-party application 2 in the sports watch 200 . The device reporting message includes the device type of the sports watch 20 and the service activation status of the third-party application 2 .

[0238] S1308: When the third-party application 1 in the mobile phone 100 determines that the device type and service activation status of the sports watch 200 meet predetermined conditions, the mobile phone 100 displays an activation interface for activating application permissions.

[0239] The above-mentioned predetermined conditions may include that the device type is a lightweight device such as a sports watch and the service activation status of the third-party application 2 is inactivated.

[0240] In some embodiments, the mobile phone 100 can activate the third-party application 1 by using payment activation (such as in-app payment), face recognition, etc. The activation interface is the interface of any application activation method.

[0241] In some other embodiments, after connecting to the sports watch 200, the mobile phone 100 has already stored the device type of the sports watch 200. Therefore, the mobile phone 100 exchanges information with the sports watch 200 via the distributed communication SDK to determine the service activation status of the third-party application on the sports watch 200. Based on the stored device type of the sports watch 200 and the service activation status information obtained from the sports watch 200, the mobile phone determines whether application activation is necessary on the mobile phone 100 side.

[0242] S1309: The mobile phone 100 activates the third-party application 2 on the activation interface.

[0243] For example, when the activation interface is a payment interface, the user needs to enter a payment password and other payment operations to complete the activation operation.

[0244] For example, when the activation interface is a face authentication interface, the user needs to capture a face image according to the prompts to complete the activation operation.

[0245] It can be understood that the third-party application 1 and the third-party application 2 are different versions of the same application, so the activation of the third-party application 1 means the activation of the third-party application 2.

[0246] S1310: The mobile phone 100 sends an activation completion message to the sports watch 200. The activation completion message is used to indicate that the application permissions of the third-party application 2 are activated.

[0247] In some embodiments, the sports watch 200 may update the service activation status information according to the received activation completion message.

[0248] S1311: The sports watch 200 displays an operating interface, which is a normal operating interface of the third-party application 2.

[0249] In some embodiments, the sports watch 200 queries the recorded service activation status information in real time to determine that the current service activation status of the third-party application is activated, that is, the permissions of the third-party application 2 are activated, thereby updating the display interface to the normal operating interface of the third-party application to use the third-party application 2 normally.

[0250] In some other embodiments, the sports watch 200 can reopen the third-party application 2 and determine that the current service activation status of the third-party application is activated, that is, the permissions of the third-party application 2 are activated, so that the display interface is the normal operation interface of the third-party application, so that the third-party application 2 can be used normally.

[0251] In this way, the application permission activation method provided in the embodiment of the present application does not require lightweight devices such as sports watches to be connected to the Internet or support an independent application market. The same application can also be activated through full-scale devices such as mobile phones. The mobile phone then notifies the sports watch through the distributed communication SDK that the application has been activated, thereby realizing cross-device application activation.

[0252] FIG14 is a schematic diagram of the hardware structure of the mobile phone 100 .

[0253] The mobile phone 100 may include a processor 110, a power module 140, a memory 180, a mobile communication module 130, a wireless communication module 120, a sensor module 190, an audio module 150, a camera 170, an interface module 160, a button 101 and a display screen 102, etc.

[0254] It should be understood that the illustrated structure of the embodiment of the present invention does not constitute a specific limitation on the mobile phone 100. In other embodiments of the present application, the mobile phone 100 may include more or fewer components than shown, or some components may be combined or separated, or arranged differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0255] The processor 110 may include one or more processing units, for example, a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), a microprocessor (MCU), an AI (Artificial Intelligence) processor, or a processing module or processing circuit such as a programmable logic device (FPGA). Different processing units may be independent devices or integrated into one or more processors. A storage unit may be provided in the processor 110 for storing instructions and data. In some embodiments, the storage unit in the processor 110 is a cache memory 180. For example, the processor 110 is used to determine whether the device type of the sports watch 200 connected to the mobile phone 100 and the service activation status of the third-party application 2 on the sports watch 200 side meet predetermined conditions.

[0256] The power module 140 may include a power supply, a power management component, and the like. The power supply may be a battery. The power management component manages the charging of the power supply and the supply of power to other modules. In some embodiments, the power management component includes a charging management module and a power management module. The charging management module receives charging input from a charger; the power management module connects the power supply, the charging management module, and the processor 110. The power management module receives input from the power supply and / or the charging management module to power the processor 110, the display 102, the camera 170, and the wireless communication module 120.

[0257] The mobile communication module 130 may include but is not limited to an antenna, a power amplifier, a filter, an LNA (Low noise amplify, low noise amplifier), etc. The mobile communication module 130 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the mobile phone 100. The mobile communication module 130 can receive electromagnetic waves through the antenna, and filter, amplify and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 130 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna. In some embodiments, at least some of the functional modules of the mobile communication module 130 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 130 can be set in the same device as at least some of the modules of the processor 110. Wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), Bluetooth (BT), global navigation satellite system (GNSS), wireless local area networks (WLAN), near field communication (NFC), frequency modulation (FM) and / or field communication (NFC), infrared technology (IR), etc.The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0258] The wireless communication module 120 may include an antenna and realize the transmission and reception of electromagnetic waves via the antenna. The wireless communication module 120 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication technology (NFC), infrared technology (IR), etc. applied to the mobile phone 100. The mobile phone 100 can communicate with the network and other devices through wireless communication technology.

[0259] In some embodiments, the mobile communication module 130 and the wireless communication module 120 of the mobile phone 100 may also be located in the same module.

[0260] Display screen 102 is used to display human-computer interaction interfaces, images, videos, etc. Display screen 102 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-oLed, or a quantum dot light-emitting diode (QLED). For example, display screen 102 can display a setup interface or access interface for a DRM-protected file.

[0261] The sensor module 190 may include a proximity sensor, a pressure sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

[0262] The audio module 150 is used to convert digital audio information into analog audio signal output, or convert analog audio input into digital audio signal. The audio module 150 can also be used to encode and decode audio signals. In some embodiments, the audio module 150 can be provided in the processor 110, or some functional modules of the audio module 150 can be provided in the processor 110. In some embodiments, the audio module 150 can include a speaker, an earpiece, a microphone, and a headphone jack.

[0263] Camera 170 is used to capture still images or videos. The lens generates an optical image of an object and projects it onto a photosensitive element. The photosensitive element converts the optical signal into an electrical signal, which is then passed to the Image Signal Processing (ISP) for conversion into a digital image signal. Mobile phone 100 implements its camera function through the ISP, camera 170, video codec, GPU (Graphics Processing Unit), display 102, and application processor.

[0264] The interface module 160 includes an external memory interface, a universal serial bus (USB) interface, and a subscriber identification module (SIM) card interface. The external memory interface can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone 100. The external memory card communicates with the processor 110 via the external memory interface to implement data storage. The USB interface is used for the mobile phone 100 to communicate with other electronic devices. The subscriber identification module card interface is used to communicate with the SIM card installed in the mobile phone 100, for example, to read the phone number stored in the SIM card or write the phone number to the SIM card.

[0265] In some embodiments, the mobile phone 100 further includes buttons 101, a motor, and an indicator. The buttons 101 may include a volume button, an on / off button, and the like. The motor is used to vibrate the mobile phone 100, for example, when the user's mobile phone 100 is called, to prompt the user to answer the call. The indicator may include a laser pointer, a radio frequency indicator, an LED indicator, and the like.

[0266] FIG15 is a schematic diagram of the hardware structure of a sports watch 200 provided in an embodiment of the present application. The smart watch may include a watch body. In one embodiment of the present application, the body of the sports watch 200 may include a touch screen 101 (also known as a touch panel), a display screen 102, a housing (the housing includes a front housing (not shown in FIG15 ) and a bottom housing (not shown in FIG15 )), a processor 103, a micro control unit (MCU) 104, a memory 105, a wireless communication unit 106, a motion sensor 107, a power supply 108, a power management system 109, and the like.

[0267] The following describes the functional components of the sports watch 200:

[0268] The touch screen 101, which may also be called a touch panel, may collect touch operations performed by the watch user on the touch screen 101. For example, the touch screen 101 may be used to collect single-click gestures or double-click gestures performed by the user on the touch screen 101.

[0269] The display screen 102 can be used to display information input by the user or prompt information provided to the user, as well as various menus on the watch. Furthermore, the touch screen 101 can cover the display screen 102. When the touch screen 101 detects a touch operation on or near it, it transmits the information to the processor 103 to determine the type of touch event. The processor 103 then provides corresponding visual output on the display screen 102 based on the type of touch event. For example, in some embodiments of the present application, the sports watch 200 can display an audio playback interface or an interface for controlling the playback of an audio device or audio.

[0270] The processor 103 is used to perform system scheduling, control the touch screen 101 and display screen 102, and support processing of the wireless communication unit 106. The microcontroller unit 104 is used to control sensors, perform operations on sensor data, and communicate with the processor 103. The sensors may include a motion sensor 107 or other sensors.

[0271] The memory 105 is used to store software programs and various data (such as various detection data of the sports watch 200, such as information on the activation status of third-party applications, and the device type). The processor 103 executes various functional applications and data processing of the sports watch 200 by running the software programs and data stored in the memory 105.

[0272] The wireless communication unit 106 is used by the sports watch 200 to communicate with other electronic devices (such as mobile phones, tablet computers, etc.) wirelessly. For example, wireless communication solutions such as Bluetooth (BT), near field communication (NFC), and infrared (IR) can be used. For example, in the embodiment of the present application, the sports watch 200 can establish a communication connection with the mobile phone 100 via Bluetooth.

[0273] The power management system 109 is used to connect to the power supply 108 to provide power to the touch screen 101, the display screen 102, the processor 103, the micro control unit 104, the memory 105, the wireless communication unit 106, the motion sensor 107, etc.

[0274] It can be understood that the structure shown in Figure 15 is only a specific structure for realizing the functions of the sports watch 200 in the technical solution of this application. Sports watches 200 with other structures and capable of realizing similar functions are also applicable to the technical solution of this application, and no limitation is made here.

[0275] The various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or a combination of these implementation methods. The embodiments of the present application can be implemented as a computer program or program code executed on a programmable system, which includes at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0276] Program code can be applied to input instructions to perform the functions described herein and generate output information. The output information can be applied to one or more output devices in a known manner. For purposes of this application, a processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

[0277] Program code can be implemented with a high-level programming language or an object-oriented programming language to communicate with the processing system. Where necessary, program code can also be implemented in assembly language or machine language. In fact, the mechanism described in this application is not limited to the scope of any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0278] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed over a network or through other computer-readable media. Therefore, a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including but not limited to floppy disks, optical disks, optical discs, read-only memories (CD-ROMs), magneto-optical disks, read-only memories (ROMs), random access memories (RAMs), erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, flash memory, or a tangible machine-readable memory for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet in electrical, optical, acoustic, or other forms of propagation signals. Therefore, a machine-readable medium includes any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[0279] In the accompanying drawings, some structural or method features may be shown in a particular arrangement and / or order. However, it should be understood that such a particular arrangement and / or order may not be required. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. In addition, the inclusion of a structural or method feature in a particular figure does not imply that such feature is required in all embodiments, and in some embodiments, such features may not be included or may be combined with other features.

[0280] It should be noted that the units / modules mentioned in the various device embodiments of the present application are all logical units / modules. Physically, a logical unit / module can be a physical unit / module, or a part of a physical unit / module, or can be implemented as a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important. The combination of functions implemented by these logical units / modules is the key to solving the technical problems raised by this application. In addition, in order to highlight the innovative part of this application, the above-mentioned device embodiments of this application do not introduce units / modules that are not closely related to solving the technical problems raised by this application. This does not mean that other units / modules do not exist in the above-mentioned device embodiments.

[0281] It should be noted that in the examples and description of this patent, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "including a" does not exclude the presence of other identical elements in the process, method, article or device that includes the element.

[0282] Although the present application has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the application.

Claims

1. A method for activating application permissions, characterized in that: The method comprises: In response to an operation of opening a first application installed in a first device, the first device determines a permission activation state of the first application; When the permission activation state is inactive, the first device sends a first message to the second device, where the first message includes a device type of the first device and the permission activation state of the first application; When the second device determines that the device type is a preset type and the permission activation state is inactivated, opening a second application in the second device, where the second application is associated with the first application; The second device activates the permission of the first application using the second application; The second device sends a second message to the first device, where the second message is used to indicate that the permission of the first application has been activated.

2. The method according to claim 1, characterized in that The method further comprises: If the permission activation status is inactivated, the first device displays a first application interface, where the first application interface is used to prompt the user to download or open the second application in the second device.

3. The method according to claim 1, characterized in that The method further comprises: When the second device opens the second application, it sends a third message to the first device, where the third message is used to obtain the device type of the first device and the permission activation status of the first application.

4. The method according to claim 1, wherein The method further comprises: When the second device determines that the device type is a preset type and the permission activation state is not activated, a second application interface is displayed, where the second application interface is used to activate the permission of the first application.

5. The method according to claim 1, wherein The preset type is lightweight device.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The first device sends a fourth message to the second device, where the fourth message is used to obtain an installation status of the second application in the second device; If the installation status is not installed, the first device sends a fifth message to the second device, where the fifth message is used to instruct the first device to automatically open a download interface of the second application; If the installation status is installed, the first device sends a sixth message to the second device, where the sixth message is used to instruct the first device to automatically open the second application.

7. The method according to claim 1, characterized in that The method further comprises: The first device displays a third application interface according to the second message, where the third application interface is a normal operating interface of the first application.

8. The method according to claim 1, characterized in that The method further comprises: The first device modifies the permission activation status of the first application to activated according to the second message.

9. The method according to claim 1, characterized in that The permission of the first application is the permission to use the entire business of the first application or the permission to use a service in the first application.

10. The method according to claim 1, characterized in that The activation method of the first application includes at least one of the following: a payment activation method, a face recognition method, a fingerprint recognition method, and a character password recognition method.

11. The method according to claim 1, characterized in that When the activation mode of the first application is a paid activation mode, the second device uses the second application to call the application market to make an in-application payment to activate the permission of the first application.

12. The method according to claim 1, characterized in that A first distributed communication SDK is deployed in the first device, a second distributed communication SDK is deployed in the second device, and messages between the first device and the second device are transmitted based on the first distributed communication SDK and the second distributed communication SDK.

13. The method according to claim 12, characterized in that The first message is sent by the first device using the first application to call the interface of the first distributed communication SDK to the interface of the second distributed communication SDK, and the first message is transmitted to the second application through the interface of the second distributed communication SDK; The second message is sent by the second device using the second application to call the interface of the second distributed communication SDK to the interface of the first distributed communication SDK, and the second message is transmitted to the first application through the interface of the first distributed communication SDK.

14. A method for activating application permissions, characterized in that: Applied to a first device, the method includes: In response to an operation of opening a first application installed in the first device, the first device determines a permission activation state of the first application; When the permission activation state is inactive, the first device sends a first message to the second device, where the first message includes a device type of the first device and the permission activation state of the first application; The first device receives a second message from the second device, where the second message is used to indicate that the permissions of the first application have been activated, wherein the permissions of the first application are activated by the second device using the second application when the second device determines that the device type is a preset type and the permission activation status is not activated, and the second application has an associated relationship with the first application.

15. The method according to claim 14, characterized in that The method further comprises: If the permission activation status is inactivated, the first device displays a first application interface, where the first application interface is used to prompt the user to download or open the second application in the second device.

16. The method according to claim 14, characterized in that The preset type is lightweight device.

17. The method according to any one of claims 14 to 16, characterized in that The method further comprises: The first device sends a fourth message to the second device, where the fourth message is used to obtain an installation status of the second application installed by the second device; If the installation status is not installed, the first device sends a fifth message to the second device, where the fifth message is used to instruct the second device to automatically open a download interface of the second application; If the installation status is installed, the first device sends a sixth message to the second device, where the sixth message is used to instruct the second device to automatically open the second application.

18. The method according to any one of claims 14 to 17, characterized in that The method further comprises: The first device displays a third application interface according to the second message, where the third application interface is a normal operating interface of the first application.

19. The method according to claim 14, wherein The method further comprises: The first device modifies the permission activation status of the first application to activated according to the second message.

20. The method according to claim 14, wherein The permission of the first application is the permission to use the entire business of the first application or the permission to use a service in the first application.

21. The method according to claim 14, wherein The activation method of the first application includes at least one of the following: a payment activation method, a face recognition method, a fingerprint recognition method, and a character password recognition method.

22. The method according to claim 14, wherein A first distributed communication SDK is deployed in the first device, a second distributed communication SDK is deployed in the second device, and messages between the first device and the second device are transmitted based on the first distributed communication SDK and the second distributed communication SDK.

23. The method according to claim 22, characterized in that The first message is sent by the first device using the first application to call the interface of the first distributed communication SDK to the interface of the second distributed communication SDK, and the first message is transmitted to the second application through the interface of the second distributed communication SDK; The second message is sent by the second device using the second application to call the interface of the second distributed communication SDK to the interface of the first distributed communication SDK, and the second message is transmitted to the first application through the interface of the first distributed communication SDK.

24. A method for activating application permissions, characterized in that: Applied to the second device, the method includes: The second device receives a first message from the first device, where the first message includes a device type of the first device and a permission activation status of a first application installed on the first device; When the second device determines that the device type is a preset type and the permission activation state is inactivated, opening a second application in the second device, where the second application is associated with the first application; The second device activates the permission of the first application using the second application; The second device sends a second message to the first device, where the second message is used to indicate that the permission of the first application has been activated.

25. The method according to claim 24, characterized in that The method further comprises: When the second device opens the second application, the second application sends a third message to the first device, where the third message is used to obtain the device type of the first device and the permission activation status of the first application.

26. The method according to claim 24, characterized in that The method further comprises: When the second device determines that the device type is the preset type and the permission activation state is not activated, the second application interface is displayed. The second application interface is used to activate the permissions of the first application.

27. The method according to claim 24, characterized in that The preset type is lightweight device.

28. The method according to claim 24, characterized in that The permission of the first application is the permission to use the entire business of the first application or the permission to use a service in the first application.

29. The method according to claim 24, wherein The activation method of the first application includes at least one of the following: a payment activation method, a face recognition method, a fingerprint recognition method, and a character password recognition method.

30. The method according to claim 24, wherein When the activation mode of the first application is a paid activation mode, the second device uses the second application to call the application market to make an in-application payment to activate the permission of the first application.

31. The method according to claim 24, wherein A first distributed communication SDK is deployed in the first device, a second distributed communication SDK is deployed in the second device, and messages between the first device and the second device are transmitted based on the first distributed communication SDK and the second distributed communication SDK.

32. The method according to claim 31, characterized in that The first message is sent by the first device using the first application to call the interface of the first distributed communication SDK to the interface of the second distributed communication SDK, and the first message is transmitted to the second application through the interface of the second distributed communication SDK; The second message is sent by the second device using the second application to call the interface of the second distributed communication SDK to the interface of the first distributed communication SDK, and the second message is transmitted to the first application through the interface of the first distributed communication SDK.

33. A readable medium, characterized in that The readable medium stores instructions, which, when executed on an electronic device, enable the electronic device to execute the application permission activation method according to any one of claims 14 to 23, or the application permission activation method according to any one of claims 24 to 32.

34. An electronic device, characterized in that: include: A memory for storing instructions executed by one or more processors of an electronic device, and a processor, which is one of the processors of the electronic device, for executing the application permission activation method according to any one of claims 14 to 23, or the application permission activation method according to any one of claims 24 to 32.

Images